id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
44.056 | GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.056/44056-i00.zip | The present document specifies the procedures used at the CTS radio interface (Reference Point Um*, see GSM 03.56) for Call Control (CC), Mobility Management (MM), Radio Resource (RR).
When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The CTS control channels are described in GSM 03.52.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07. |
44.057 | GSM Cordless Telephony System (CTS), Phase 1; CTS supervising system layer 3 specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.057/44057-i00.zip | The present document specifies the procedures used at the CTS system interface with the supervision part i.e. the interface between the CTS-FP and the CTS-SN.
Only CTS regular supervising procedures are described; FMC management is not intended to be standardised.
The present document does not specify the transmission layer but only the layer 3.
When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07. |
44.060 | General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.060/44060-i00.zip | |
44.064 | Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.064/44064-i00.zip | The present document defines the Logical Link Control (LLC) layer protocol to be used for packet data transfer between the Mobile Station (MS) and Serving GPRS Support Node (SGSN).
It defines the frame structure, elements of procedure, format of fields, and procedures for the proper operation of the logical link control layer. It is based on ideas contained in IS-130 [21], ISO 3309 [16], ISO 4335 [17], and ISO 7809 [18, 19, 20] (HDLC of ISO), as well ITU-T Q.920 [13] and Q.921 [14] (LAPD). The concepts, the overview description of LLC layer functions and procedures, and the relationship with other Technical Specifications are described in general terms in 3GPP TS 23.060 [5].
LLC spans from the Mobile Station (MS) to the Serving GPRS Support Node (SGSN). LLC is intended for use with both acknowledged and unacknowledged data transfer.
The frame formats defined for LLC are based on those defined for LAPD and RLP. However, there are important differences between LLC and other protocols, in particular with regard to frame delimitation methods and transparency mechanisms. These differences are necessary for independence from the radio path.
The LLC procedures are modelled upon the concepts of HDLC as outlined in ISO 4335. Data sequence integrity between the data source and data sink is effected by means of a cyclic numbering scheme. An independent numbering scheme is used for each logical data link, as identified by the a data link connection identifier. LLC supports two modes of operation:
- Unacknowledged peer-to-peer operation:
A logical link entity may initiate transmissions to a peer entity without prior establishment of a logical connection with the peer entity. LLC does not guarantee in-order delivery. LLC can detect errors in a received frame, and, depending on whether the frame is sent in protected mode or not, either discard or deliver the erroneous frame. No error recovery procedures are defined at the LLC layer. Higher-layer protocols can be used to provide reliability, if needed. This mode of operation is known as Asynchronous Disconnected Mode (ADM).
- Acknowledged peer-to-peer operation:
A balanced data link involves two participating entities, and each entity assumes responsibility for the organisation of its data flow and for error recovery procedures associated with the transmissions that it originates. Each entity operates as both a data source and data sink in a balanced link, allowing information to flow in both directions. This mode of operation is known as Asynchronous Balanced Mode (ABM), and provides a reliable service with in-order delivery.
In unacknowledged operation, LLC can provide integrity protection.
The present document is organised as follows:
- An overview of the LLC layer functions is given in clause 4.
- The frame structure for peer-to-peer communication is given in clause 5.
- The elements of procedure and formats of fields are given in clause 6.
- The elements of layer-to-layer communication are contained in clause 7.
- The details of the peer-to-peer ABM procedures are given in clause 8.
- The details of LLC frame ciphering are given in annex A.
- The details of the TOM protocol layer are contained in annex B.
- An overview of the LLC layer states is provided in annex C. |
44.065 | Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.065/44065-i00.zip | The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS).
The user of the services provided by SNDCP is a packet data protocol (PDP) at the mobile Station (MS) or the Relay at the Serving GPRS Support Node (SGSN). Additionally, a control entity, e.g. AT command interpreter, may be an SNDCP user. SNDCP uses the services provided by the Logical Link Control (LLC) layer 4 and the Session Management (SM) sub-layer 2.
The main functions of SNDCP are:
- Multiplexing of several PDPs.
- Compression / decompression of user data.
- Compression / decompression of protocol control information.
- Segmentation of a network protocol data unit (N‑PDU) into Logical Link Control Protocol Data Units (LL‑PDUs) and re-assembly of LL‑PDUs into an N‑PDU.
3GPP TS 44.065 is applicable to GPRS MS and SGSN. |
44.068 | Group Call Control (GCC) protocol | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.068/44068-i00.zip | The present document specifies the Group Call Control (GCC) protocol used by the Voice Group Call Service (VGCS) on the radio interface. |
44.069 | Broadcast Call Control (BCC) protocol | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/44_series/44.069/44069-i00.zip | The present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface. |
44.071 | GSM/EDGE Location Services (LCS); Mobile radio interface layer 3 LCS specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.071/44071-i00.zip | The present document contains the coding of information necessary for support of location service operation on the mobile radio interface layer 3 between the LMU and SMLC.
Clause 4 defines generic procedures for the control of location services. In clause 5 location service support procedures are defined. Clause 6 gives the functional definitions and contents of messages for location service operations. Clause 7 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations. Clause 6 gives the detailed message format and information elements coding between the LMU and SMLC.
Clause 8 gives the specification of the LMU LCS Protocol (LLP) operations. In clause 9 LMU - SMLC messages, data types and identifiers are given.
This version does not support segmentation of messages. |
45.002 | GSM/EDGE Multiplexing and multiple access on the radio path | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.002/45002-i00.zip | The present document defines the physical channels of the radio sub‑system required to support the logical channels. For the Flexible Layer One, it defines the physical channels of the radio sub‑system required to support the transport channels. It includes a description of the logical channels, transport channels and the definition of frequency hopping, TDMA frames, timeslots and bursts. |
44.901 | GSM/EDGE External Network Assisted Cell Change (NACC) | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.901/44901-i00.zip | This Technical Report provides background information, motivations, concepts and requirements regarding an extended Network Assisted Cell Change (NACC) feature for external cell change support. Cell change between GERAN and UTRAN cells is outside the scope of this report, although consideration has been taken in order to allow an easier extensibility to that case. The extension is based on the Release 4 version of the NACC feature where the mobile station is only supported by the NACC when performing internal cell re-selection, i.e. within a BSC. The extension of the feature is for GERAN just affecting BSS and for the core network the SGSN and signalling links between these network nodes. To support cell changes between GERAN and UTRAN, also the Um and the Uu interfaces are affected.
The evolved Release 4 NACC proposal as described in this TR provides the basis for the detailed Stage 2 and stage 3 specification work. The feature will be developed in a phased approach and a longer-term vision is presented in the report.
The focus of the TR is to:
- Define the requirements on different nodes
- Specify the requirements for the interfaces
- Propose a plan for the work item project
- Evaluation of what does and does not need to be standardised |
45.001 | GSM/EDGE Physical layer on the radio path; General description | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.001/45001-i00.zip | The present document is an introduction to the 45 series of the digital cellular telecommunications systems GSM technical specifications. It is not of a mandatory nature, but consists of a general description of the organization of the physical layer with reference to the technical specifications where each part is specified in detail. It introduces furthermore, the reference configuration that will be used throughout this series of technical specifications. |
45.003 | GSM/EDGE Channel coding | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.003/45003-i00.zip | A reference configuration of the transmission chain is shown in 3GPP TS 45.001. According to this reference configuration, the present document specifies the data blocks given to the encryption unit.
It includes the specification of encoding, reordering, interleaving and the stealing flag. It does not specify the channel decoding method.
The definition is given for each kind of logical channel, starting from the data provided to the channel encoder by the speech coder, the data terminal equipment, or the controller of the Mobile Station (MS) or Base Transceiver Station (BTS). The definitions of the logical channel types used in this technical specification are given in 3GPP TS 45.002, a summary is in annex A.
Additionally, the present document describes the characteristics of the coding/multiplexing unit for the Flexible Layer One (FLO) starting from the transport blocks provided by higher layers. An overview of FLO is given in 3GPP TR 45.902. |
44.318 | Generic Access Network (GAN); Mobile GAN interface layer 3 specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/44_series/44.318/44318-i00.zip | The present document describes the procedures used over the Generic Access Network (GAN) interface (i.e., the Up interface). The procedures are defined in terms of messages exchanged over the Up interface.
A building block method is used to describe the procedures.
The basic building blocks are "elementary procedures" provided by the Generic Access (GA) protocol control entities.
Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences. |
45.004 | GSM/EDGE Modulation | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.004/45004-i00.zip | The modulator receives the bits from the encryption unit, see 3GPP TS 45.001, and produces an RF signal. The filtering of the Radio Frequency (RF) signal necessary to obtain the spectral purity is not defined, neither are the tolerances associated with the theoretical filter requirements specified. These are contained in 3GPP TS 45.005. |
45.005 | GSM/EDGE Radio transmission and reception | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.005/45005-i00.zip | The present document defines the requirements for the transceiver of the pan‑European digital cellular telecommunications systems GSM.
Requirements are defined for two categories of parameters:
- those that are required to provide compatibility between the radio channels, connected either to separate or common antennas, that are used in the system. This category also includes parameters providing compatibility with existing systems in the same or adjacent frequency bands;
- those that define the transmission quality of the system.
The present document defines RF characteristics for the Mobile Station (MS) and Base Station System (BSS). The BSS will contain Base Transceiver Stations (BTS), which can be normal BTS,micro‑BTS or pico-BTS. The precise measurement methods are specified in 3GPP TS 51.010 and 3GPP TS 51.021.
Unless otherwise stated, the requirements defined in this EN apply to the full range of environmental conditions specified for the equipment (see annex D).
In the present document some relaxations are introduced for GSM 400 MSs, GSM 900 MSs, GSM 700 MSs and GSM 850 MSs which pertain to power class 4, 5 or 6 (see subclause 4.1.1). In the present document these Mobile Stations are referred to as "small MS".
In the present document some relaxations to receiver requirements are introduced for a MS indicating support for Downlink Multi Carrier (DLMC), see 3GPP TS 24.008, when in DLMC configuration. DLMC configurations are specified for only GSM 850, GSM 900, DCS 1800 and PCS 1900.
MSs may operate on more than one of the frequency bands specified in clause 2. These MSs are referred to as "Multi band MSs" in this EN. Multi band MSs shall meet all requirements for each of the bands supported. The relaxation on GSM 400 MSs, GSM 900 MSs, GSM 700 MSs and GSM 850 MSs for a "small MS" are also valid for a multi band MS if it complies with the definition of a small MS.
The RF characteristics of repeaters are defined in annex E of this EN. Annexes D and E are the only clauses of this EN applicable to repeaters. Annex E does not apply to the MS or BSS. The precise measurement methods for repeaters are specified in 3GPP TS 51.026 [35].
The present document also includes specification information for mixed mode operation at 850 MHz and 1900 MHz (MXM 850 and MXM 1900). 850 MHz and 1900 MHz mixed-mode is defined as a network that deploys both 30 kHz RF carriers and 200 kHz RF carriers in geographic regions where the Federal Communications Commission (FCC) regulations are applied or adopted.
The requirements for a MS in a mixed-mode system, MXM 850 and MXM 1900, correspond to the requirements for GSM 850 MS and PCS 1900 MS respectively.
Annex M defines the minimum performance requirements for A-GPS for MSs that support A-GPS. Annex M does not apply to the BSS.
The present document also includes specific requirements for multicarrier BTS, wherever explicitly stated in the text, that apply for all classes of multicarrier BTS (Wide Area, Medium Range and Local Area) if nothing else is stated. All other requirements designated for BTS and normal BTS apply if not otherwise stated. The multicarrier BTS classes have relaxed requirements in the areas of Tx spurious emissions, intermodulation attenuation and, when multicarrier receiver is included, Rx blocking. Usage of multicarrier BTSs in some geographical regions might be subject to regulatory restrictions to protect other radio systems operating in bands of adjacent frequency assignments, in particular for all safety related applications like railway applications. In areas where such systems coexist with multicarrier BTSs, the received interference power originating from multicarrier BTSs might have to be limited.
The document also includes entry points in some tables for the multicarrier BTS requirements to which TS 37.104 [33] for Multi-Standard Radio Base Stations (MSR BS) is referring to as specific GSM/EDGE single-RAT requirements not covered by the general requirements. These entry points are marked with M) and, as described in a note in each applicable table, identify the relevant column(s) that are applicable as MSR BS requirements. In general the requirements for multicarrier BTS equipped with multicarrier receiver also apply to Multi-Standard Radio Base Stations. The GSM requirements for Multi-Standard Radio Base Stations are defined for GSM 850, GSM 900, DCS 1800 and PCS 1900 only. Requirements for other frequency bands and MXM base stations are excluded. Annex P defines the minimum performance for the receiver in MSR BS.
For equipment not declared as MSR BS the M) indications can be ignored.
The present document defines requirements for the usage of the ER-GSM band. The national implementation might be subject to regulatory coordination agreements to avoid system impacts (RF scenarios for ER-GSM introduction are given in 3GPP TR 45.050).
The present document defines requirements for supporting a low-complexity, low data throughput service in environments experiencing high propagation attenuation as indoors in basements etc. This service, based on EGPRS, with extended coverage is called EC-GSM-IoT. For EC-GSM-IoT, in case no specific requirement is explicitly stated, the requirements for EGPRS apply. |
45.008 | GSM/EDGE Radio subsystem link control | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.008/45008-i00.zip | The present document specifies the Radio sub‑system link control implemented in the Mobile Station (MS), Base Station System (BSS) and Mobile Switching Centre (MSC) of the digital cellular telecommunications systems GSM.
Unless otherwise specified, references to GSM also include operation in any supported band (see TS 45.005). |
45.009 | GSM/EDGE Link adaptation | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.009/45009-i00.zip | The requirements described in the present document are mandatory for implementation in all GSM MSs and BSSs capable of supporting the Adaptive Multi-Rate speech traffic channel, unless otherwise stated.
Unless otherwise specified, references to GSM include GSM at any frequency band. |
45.010 | GSM/EDGE Radio subsystem synchronization | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.010/45010-i00.zip | The present document defines the requirements for synchronization on the radio sub-system of the digital cellular telecommunications systems GSM. However, it does not define the synchronization algorithms to be used in the Base Transceiver Station (BTS), CTS Fixed Part (CTS-FP) and Mobile Station (MS). These are up to the manufacturer to specify. |
45.015 | GSM/EDGE Release independent Downlink Advanced Receiver Performance (DARP); Implementation guidelines | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.015/45015-i00.zip | The present document specifies requirements on MSs supporting Downlink Advanced Receiver Performance (DARP) that are independent of release. TSG GERAN has agreed that the standardisation of DARP be independent of a release. However, in order to implement an MS that conforms to a particular release but supports DARP, which is specified in a later release, it is necessary to specify some extra requirements.
DARP - phase II is contained in the Release 7 specifications. In order to implement an MS conforming to Release 5 but supporting DARP – phase II, it is necessary for the MS to additionally conform to some parts of the Release 7 specifications, such as the radio frequency requirements for DARP and some signalling extensions relating to the MS Classmark and radio access capabilities. |
45.022 | GSM/EDGE Radio link management in hierarchical networks | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.022/45022-i00.zip | The present document gives examples for the Radio sub-system link control to be implemented in the Base Station System (BSS) and Mobile Switching Centre (MSC) of the GSM and DCS 1 800 systems in case hierarchical cell structures are employed.
Unless otherwise specified, references to GSM also include DCS 1 800, and multiband systems if operated by a single operator. |
45.050 | GSM/EDGE Background for Radio Frequency (RF) requirements | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.050/45050-i00.zip | |
45.056 | GSM Cordless Telephony System (CTS), Phase 1; CTS-FP Radio subsystem | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.056/45056-i00.zip | The present document specifies the requirements for the CTS-Fixed Part (CTS-FP) transceiver of the digital mobile cellular and personal communication systems operating in the 900 MHz (P-GSM and E-GSM) and 1 800 MHz band (GSM 900 and DCS 1 800), and specifies the Radio subsystem frequency control implemented in the CTS-Fixed Part.
Unless otherwise stated, the requirements defined in the present document apply to the full range of environmental conditions specified for the CTS-FP equipment (see annex C). |
45.902 | GSM/EDGE Flexible Layer One (FLO) | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.902/45902-i00.zip | The present document provides an overview of the flexible layer one, its architecture and studies the impacts it has on the GERAN radio protocol stack.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
45.903 | Feasibility study on Single Antenna Interference Cancellation (SAIC) for GSM networks | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.903/45903-i00.zip | |
45.912 | Feasibility study for evolved GSM/EDGE Radio Access Network (GERAN) | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.912/45912-i00.zip | The present document is an output of the 3GPP work item "Future GERAN Evolution" [1].
The scope of this document is to capture the results of the feasibility study on the GERAN, the objectives of which are to: increase capacity, coverage and data rates; reduce latency; and enhance service continuity with other RATs; while minimising impacts to infrastructure. |
45.913 | Optimized transmit pulse shape for downlink Enhanced General Packet Radio Service (EGPRS2-B) | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.913/45913-i00.zip | The present document is an output of the 3GPP study item "Optimized Transmit Pulse Shape for Downlink EGPRS2-B" ("WIDER") [2], the objective of which is to optimise pulse shapes based on optimization criteria to be agreed by TSG GERAN WG1, and provide an evaluation of the optimized pulse shapes in a similar manner as was used in the SAIC feasibility study TR 45.903 [3]. |
45.914 | Circuit switched voice capacity evolution for GSM/EDGE Radio Access Network (GERAN) | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.914/45914-i00.zip | The present document is an output of the 3GPP study item "Multi-User Reusing-One-Slot" (MUROS) [11].
It contains a section describing the objectives of the Circuit Switched Voice Capacity Evolution, and further sections presenting candidate techniques, which are evaluated according to their potential related to voice capacity improvement in GERAN. For this the design of a new set of training sequences with improved cross correlation properties to the existing set of training sequences is foreseen and expected to be evaluated. The study will also include the investigation of different optimised pulse shapes for MUROS for both the uplink and the downlink. |
45.926 | Solutions for GSM/EDGE Base Transceiver Station (BTS) energy saving | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/45_series/45.926/45926-i00.zip | The present document provides a study into BTS energy saving solutions. The present document analyses and evaluates different solutions to determine the benefits provided compared to the legacy BTS energy consumption.
In the scope of this study there are following solutions:
- Reduction of Power on the BCCH carrier (potentially enabling dynamic adjustment of BCCH power)
- Reduction of power on DL common control channels
- Reduction of power on DL channels in dedicated mode, DTM and packet transfer mode
- Deactivation of cells (e.g. Cell Power Down and Cell DTX like concepts as discussed in RAN [4])
- Deactivation of other RATs in areas with multi-RAT deployments, for example, where the mobile station could assist the network to suspend/minimize specific in-use RATs at specific times of day
- And any other radio interface impacted power reduction solutions
The solutions will also consider the following aspects:
- Impacts on the time for legacy and new mobile stations to gain access to service from the BTS
- Impacts on legacy and new mobile stations to keep the ongoing service (without increasing drop rate)
- Impacts on legacy and new mobile stations implementation and power consumption, e.g. due to reduction in DL power, cell (re-)selection performance, handover performance, etc.
- Impacts on UL/DL coverage balance, especially to CS voice
Solutions will be considered for both BTS energy saving non-supporting and supporting mobile stations (i.e. solutions that are non-backwards compatible towards legacy mobile stations will be out of the scope of this study).
The contents of the present document when stable will determine the modifications to existing GERAN specifications. |
46.001 | Full rate speech; Processing functions | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.001/46001-i00.zip | The present document is an introduction to the 06 series of the GSM technical specifications dealing with the Full rate speech processing functions in the GSM system. A general overview of the speech processing parts is given with reference to the technical specifications where each part is specified in detail. |
46.002 | Half rate speech; Half rate speech processing functions | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.002/46002-i00.zip | The present document is an introduction to GSM 06.20 [4], GSM 06.21 [5], GSM 06.22 [6], GSM 06.41 [7] and GSM 06.42 [8] TSs dealing with the speech processing functions in the half‑rate channel of the GSM system. A general overview of the speech processing functions is given, with reference to the TSs where each function is specified in detail. |
46.006 | Half rate speech; ANSI-C code for the GSM half rate speech codec | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.006/46006-i00.zip | The present document contains an electronic copy of the ANSI‑C code for the GSM half rate codec. The ANSI‑C code is necessary for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]), Discontinuous Transmission (GSM 06.41 [5]) and example solutions for substituting and muting of lost frames (GSM 06.21 [3]). |
46.007 | Half rate speech; Test sequences for the GSM half rate speech codec | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.007/46007-i00.zip | The present document specifies the digital test sequences for the GSM half rate speech codec. These sequences test for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]). |
46.008 | Half Rate Speech; Performance Characterization of the GSM Half Rate speech codec | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.008/46008-i00.zip | The present document gives background information on the performance of the GSM half rate speech codec. Experimental results from the characterization and verification tests carried out during the selection process by the Traffic CHannel Half rate Speech (TCH-HS) expert group are reported to give a more detailed picture of the behaviour of the GSM half rate speech codec under different conditions of operation. |
46.010 | Full rate speech; Transcoding | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.010/46010-i00.zip | The transcoding procedure specified in the present document is applicable for the full‑rate Traffic Channel (TCH) in the digital cellular telecommunications system. The use of this transcoding scheme for other applications has not been considered.
In GSM 06.01, a reference configuration for the speech transmission chain of the digital cellular telecommunications system is shown. According to this reference configuration, the speech encoder takes its input as a 13 bit uniform PCM signal either from the audio part of the mobile station or on the network side, from the PSTN via an 8 bit/A‑ or -law (PCS 1900) to 13 bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to a channel encoder unit which is specified in GSM 05.03. In the receive direction, the inverse operations take place.
The present document describes the detailed mapping between input blocks of 160 speech samples in 13 bit uniform PCM format to encoded blocks of 260 bits and from encoded blocks of 260 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8000 sample/s leading to an average bit rate for the encoded bit stream of 13 kbit/s. The coding scheme is the so‑called Regular Pulse Excitation ‑ Long Term prediction ‑ Linear Predictive Coder, here‑after referred to as RPE‑LTP.
The present document also specifies the conversion between A‑ and -law (PCS 1900) PCM and 13 bit uniform PCM. Performance requirements for the audio input and output parts are included only to the extent that they affect the transcoder performance. The present document also describes the codec down to the bit level, thus enabling the verification of compliance to the present document to a high degree of confidence by use of a set of digital test sequences. These test sequences are described and are contained in archive en_300961v080101p0.ZIP which accompanies the present document. |
46.011 | Full rate speech; Substitution and muting of lost frames for full rate speech channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.011/46011-i00.zip | The present document defines a frame substitution and muting procedure which shall be used by the RX DTX handler when one or more lost speech or SID frames are received from the radio subsystem.
The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS) and Mobile Stations (MS). |
46.012 | Full rate speech; Comfort noise aspect for full rate speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.012/46012-i00.zip | The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX) on full rate speech traffic channels.
The requirements described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. |
46.020 | Half rate speech; Half rate speech transcoding | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.020/46020-i00.zip | The present document specifies the speech codec to be used for the GSM half rate channel. It also specifies the test methods to be used to verify that the codec implementation complies with the present document.
The requirements are mandatory for the codec to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the half rate GSM speech traffic channel. |
46.021 | Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.021/46021-i00.zip | The present document defines a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost or unreliable speech or SIlence Descriptor (SID) frames are received from the Radio Sub System (RSS).
The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS)s and Mobile Stations (MS)s capable of supporting the half rate speech traffic channel. |
46.022 | Half rate speech; Comfort noise aspects for the half rate speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.022/46022-i00.zip | The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX) on half rate speech traffic channels.
The requirements described in the present document are mandatory for implementation in all GSM MSs capable of supporting the half rate speech traffic channel.
The receiver requirements are mandatory for implementation in all GSM BSSs capable of supporting the half rate speech traffic channel, the transmitter requirements are only for those where downlink DTX will be used. |
46.031 | Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.031/46031-i00.zip | The present document gives a description of the general baseband operation of full rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX).
For clarity, the description is structured according the block diagrams in figures 1 and 4. Except in the case described next, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same.
In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX Handlers and the Radio Subsystem (RSS) as described in the present document together with all their flags is mandatory, being a part of the A‑bis‑ interface as described in GSM 08.60. In this case the various flags also serve to avoid additional delays.
The DTX functions described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used.
DTX shall be in operation in GSM MSs if commanded so by the network, see GSM 04.08. |
46.032 | Full rate speech; Voice Activity Detector (VAD) for full rate speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.032/46032-i00.zip | The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.31. It also specifies the test methods to be used to verify that a VAD complies with the technical specification.
The requirements are mandatory on any VAD to be used either in the GSM Mobile Stations (MS)s or Base Station Systems (BSS)s. |
46.041 | Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.041/46041-i00.zip | The present document gives a description of the general baseband operation of half rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX).
For clarity, the description is structured according to the block diagrams in figures 1 and 4. Except in the case described below, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same.
In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX Handlers and the Radio Sub System (RSS) as described in the present document together with all their flags is mandatory, being a part of the A-bis interface as described in GSM 08.61 [10].
The DTX functions described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. |
46.042 | Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.042/46042-i00.zip | The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.41 [4]. It also specifies the test methods to be used to verify that a VAD implementation complies with the present document.
The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the half‑rate GSM speech traffic channel. |
46.051 | Enhanced Full Rate (EFR) speech processing functions; General description | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.051/46051-i00.zip | The present document is an introduction to GSM 06.60 [6], GSM 06.61 [7], GSM 06.62 [8], GSM 06.81 [9] and GSM 06.82 [10] ENs dealing with the speech processing functions in the Enhanced Full Rate channel of the GSM system. A general overview of the speech processing functions is given, with reference to the ENs where each function is specified in detail. |
46.053 | ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.053/46053-i00.zip | The present document contains an electronic copy of the ANSI‑C code for the GSM Enhanced Full Rate codec. The ANSI‑C code is necessary for a bit exact implementation of the Enhanced Full Rate speech transcoder (GSM 06.60 [3]), Voice Activity Detection (GSM 06.82 [7]), comfort noise (GSM 06.62 [5]), Discontinuous Transmission (GSM 06.81 [6]) and example solutions for substituting and muting of lost frames (GSM 06.61 [4]). |
46.054 | Test sequences for the GSM Enhanced Full Rate (EFR) speech codec | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.054/46054-i00.zip | The present document specifies the digital test sequences for the GSM enhanced full rate speech codec. These sequences test for a bit exact implementation of the enhanced full rate speech transcoder (GSM 06.60 [2]), Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]). |
46.055 | Performance characterization of the GSM Enhanced Full Rate (EFR) speech codec | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.055/46055-i00.zip | The present document gives background information on the performance of the GSM enhanced full rate speech codec. Experimental results from the Pre-selection and Verification tests carried out during the standardization process by the SEG (Speech Expert Group) are reported to give a more detailed picture of the behaviour of the GSM enhanced full rate speech codec under different conditions of operation. |
46.060 | Enhanced Full Rate (EFR) speech transcoding | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.060/46060-i00.zip | The present document describes the detailed mapping between input blocks of 160 speech samples in 13‑bit uniform PCM format to encoded blocks of 244 bits and from encoded blocks of 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to a bit rate for the encoded bit stream of 12,2 kbit/s. The coding scheme is the so‑called Algebraic Code Excited Linear Prediction Coder, hereafter referred to as ACELP.
The present document also specifies the conversion between A‑law or -law (PCS 1900) PCM and 13‑bit uniform PCM. Performance requirements for the audio input and output parts are included only to the extent that they affect the transcoder performance. This part also describes the codec down to the bit level, thus enabling the verification of compliance to the part to a high degree of confidence by use of a set of digital test sequences. These test sequences are described in GSM 06.54 [7] and are available on disks.
In case of discrepancy between the requirements described in the present document and the fixed point computational description (ANSI‑C code) of these requirements contained in GSM 06.53 [6], the description in GSM 06.53 [6] will prevail.
The transcoding procedure specified in the present document is applicable for the enhanced full rate speech traffic channel (TCH) in the GSM system.
In GSM 06.51 [5], a reference configuration for the speech transmission chain of the GSM enhanced full rate (EFR) system is shown. According to this reference configuration, the speech encoder takes its input as a 13‑bit uniform PCM signal either from the audio part of the Mobile Station or on the network side, from the PSTN via an 8‑bit/A‑law or -law (PCS 1900) to 13‑bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to a channel encoder unit which is specified in GSM 05.03 [3]. In the receive direction, the inverse operations take place. |
46.061 | Substitution and muting of lost frames for Enhanced Full Rate (EFR) speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.061/46061-i00.zip | The present document defines a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS).
The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS)s and Mobile Stations (MS)s capable of supporting the enhanced Full Rate speech traffic channel. It is not mandatory to follow the bit exact implementation outlined in the present document and the corresponding C‑source code. |
46.062 | Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.062/46062-i00.zip | The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in Mobile Stations (MSs) and Base Station Systems (BSSs) during Discontinuous Transmission (DTX) on Enhanced Full Rate speech traffic channels.
The requirements described in the present document are mandatory for implementation in all GSM MSs capable of supporting the Enhanced Full Rate speech traffic channel.
The receiver requirements are mandatory for implementation in all GSM BSSs capable of supporting the Enhanced Full Rate speech traffic channel, the transmitter requirements only for those where downlink DTX will be used.
In case of discrepancy between the requirements described in the present document and the fixed point computational description of these requirements contained in GSM 06.53 [2], the description in GSM 06.53 [2] will prevail. |
46.076 | Adaptive Multi-Rate (AMR) speech codec; Study phase report | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.076/46076-i00.zip | The present document presents the outcome of the Study Phase initiated at SMG#20 on the concept of the Adaptive Multi-Rate (AMR) codec. The AMR concept represents a new approach to achieving consistent high quality speech combined with efficient spectrum usage. It was recognized at SMG#20 that this would require novel techniques whose feasibility should first be assessed before proceeding with a full development of the AMR system and its control.
Clauses 1 to 4 provide an overview and background to the AMR concept. Clause 5 provides a basic description of the AMR system functionality including working assumptions that have been agreed during the Study Phase. Feasibility aspects are considered in clause 6. The requirement specification, which will form the basis for the development phase, is contained in clause 7. Clause 8 gives an indication of the MS and network upgrades needed to support AMR. Clause 9 outlines how the AMR codec will be developed, tested and selected including the proposed time-plan. Clauses 10 and 11 conclude with a summary of the risks and recommendations. |
46.081 | Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.081/46081-i00.zip | The present document gives a description of the general baseband operation of Enhanced Full Rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX).
For clarity, the description is structured according to the block diagrams in figures 1 and 4. Except in the case described next, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same.
In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX handlers and the Radio Sub System (RSS) as described in the present document together with all their flags is mandatory, being part of the A‑bis interface as described in GSM 08.60 [13].
The DTX functions described in the present document are mandatory for implementation in the GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used. |
46.082 | Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.082/46082-i00.zip | The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.81 [5] Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels.
The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the enhanced full-rate speech traffic channel. |
46.085 | Subjective tests on the interoperability of the Half Rate / Full Rate / Enhanced Full Rate (HR/FR/EFR) speech codecs, single, tandem and tandem free operation | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.085/46085-i00.zip | The present document contains the results obtained from an internationally co-ordinated subjective evaluation conducted by four laboratories to estimate the performance in mobile-to-mobile connections of the GSM half, full, and enhanced full rate speech codecs (including the expected advantages of the Tandem Free Operation), in case of inter-operability in the digital cellular telecommunications system. These (listening-only) tests did not include the effects of Voice Activity Detector, Comfort Noise Insertion and the Discontinuous Transmission. |
48.001 | Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; General aspects | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.001/48001-i00.zip | The present document is an introduction to the 3GPP TS 48.0xx series of Technical Specifications and deals with the definition of the base station system (BSS) to mobile switching centre (MSC) (referred to as the A-interface) defined for the GSM system.
It also introduces Technical Specifications in the 3GPP TS 48.020 series, dealing with the support of data services on this interface.
The present document gives an overview of the content of the 3GPP TS 48.0xx and 3GPP TS 48.020 series of Technical Specifications explaining how the detailed content of the Technical Specifications is partitioned and how the Technical Specifications can be used to support a full BSS-MSC interface. |
48.002 | Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Interface principles | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.002/48002-i00.zip | The present document gives the principles on which the detailed interface specifications in the rest of the 3GPP TS 48.0xx series of Technical Specifications are based.
The set of fixed equipment accessed from the MSC through one particular instance of the interface will be later referred to as a Base Station System (BSS). A BSS ensures the coverage of n cells, where n can be 1 or more.
The function of a BSS may be further subdivided into a control function, performed by one Base Station Controller (BSC) and a transceiving function, performed by "n" Base Transceiver Station equipments (BTS), one for each cell. However, the study of such a split is outside the scope of the 48.0xx series of Technical Specifications, where the BSS will be considered as a whole.
The BSS-MSC interface defined in the 3GPP TS 48 series of Technical Specifications is designed to support a wide range of possible architectures on both sides. Characteristics like location of the transcoders/rate adaptation to the MSS or inside the BSS (either physically integrated into the transceivers or very near to the MSC) or the use of traffic or signalling concentration at either side are left to the operators' choice. Annex A to the present document contains guidance information concerning the use of remote mobile switching units, which for the purposes of the present document are considered as part of the MSC.
The BSS-MSC interface is commonly called "A-Interface". It is subdivided into the Control Plane (signalling) and the User Plane (traffic). Throughout this document the term "MSC" is used to reflect both planes of the Mobile Core Network, although in some architecture the Mobile Core Network is split into MSC-Server (MSC-S) and Media Gateway (MGW).
Direct connection between two BSSs is not supported by this A-Interface.
This A-Interface may be based on
- TDM using 1 or more 2 048 kbit/s digital transmission system interfaces. Each 2 048 kbit/s interface provides 31*64 kbit/s channels which can be used for traffic (User Plane) or signalling (Control Plane) as the operator requires, and/or
- IP supporting User Plane and/or Control Plane (SIGTRAN).The signalling is layered, terminology similar to that in the OSI reference model is used in this series, however the layers referred to are not identical to the equivalently named layer in the OSI model.
This A-Interface User Plane is defined at the boundary of the MSC and
- in case of TDM, it has a per channel bit rate of 64 kbit/s, but the net radio path traffic channel is at a rate of less than 16 kbit/s. A speech transcoder or data rate adapter function is thus needed for the rate conversion. The interface is designed such that the transcoding or rate adaptation function may be geographically situated at either the MSC site or the BSS site, however the transcoder is considered to be part of the BSS
- in case of IP, it has a flexible channel bit rate, adapted to the payload size. The speech transcoding function can be part of either the BSS or the Core Network or can be omitted (transcoding free operation), allowing e.g. for use of both, PCM encoded speech and compressed speech, over the A-Interface. The data rate adapter function is always located inside the BSS, using a 64kbit/s unrestricted digital interface (Clearmode) over IP.
The A-Interface has been designed around the aims of 3GPP TS 48.001 allowing each component and the system as a whole to evolve. |
48.004 | Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Layer 1 specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.004/48004-i00.zip | The present document defines the structure of the physical layer (layer 1) of the BSS-MSC interface for supporting traffic channels. Use of the physical layer for supporting Signalling System No.7 signalling links is covered in Technical Specification 3GPP TS 48.006.
The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium.
For the present document only digital transmission will be considered, the use of analogue transmission is a national concern. |
48.006 | Signalling transport mechanism Specification for the Base Station System - Mobile Services Switching Centre (BSS - MSC) interface | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.006/48006-i00.zip | The present document is split into four parts, clauses 4 to 6 dealing with the MTP, clause 6a dealing with M3UA/SCTP, clause 7 dealing with interface functions towards higher layers and clauses 8 to 10 dealing with the SCCP and its use.
The MTP provides a mechanism giving reliable transfer of signalling messages. Clauses 4 to 7 of the present document deal with the subset of the MTP that can be used between an BSS and an MSC, which is compatible with a full MTP.
The M3UA/SCTP provides a mechanism giving reliable transfer of signalling messages over an IP network.
The SCCP is used to provide a referencing mechanism to identify a particular transaction relating to for instance a particular call. Clauses 8 to 10 identify the SCCP subset that should be used between a BSS and an MSC. The SCCP can also be used to enhance the message routing for (for instance) operations and maintenance information. |
48.008 | Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.008/48008-i00.zip | The present document specifies the layer 3 procedures used on the Base Station System (BSS) to Mobile-services Switching Centre (MSC) interface for control of GSM services.
For the purposes of call control and mobility management, messages are not interpreted at the Base Station System (BSS) which acts as a relay function. These messages and procedures are documented in 3GPP TS 24.008, the only relevant issues covering these messages in the present document are those concerned with error conditions at the interface, and the headers that are required for the correct addressing of the messages. This is specified in more detail in 3GPP TS 48.002.
The functional split between MSC and BSS is defined in 3GPP TS 48.002 and states that the BSS is responsible for local radio resource allocation and in order to support this the required procedures between BSS and MSC are defined in detail in the present document.
3GPP TS 48.002 also states that the BSS is responsible for the scheduling of all CCCH/BCCH messages and therefore some procedures for providing the BSS with the necessary information to be passed on these channels for individual calls (i.e. paging) are defined in the present document, but the scheduling is not discussed.
This interface and consequently these layer 3 procedures are designed to support BSSs providing one or more cells. |
48.014 | General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Gb interface Layer 1 | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.014/48014-i00.zip | The present document specifies the physical layer on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface) and references layer 1 standards to be used on this interface.
The protocol stack on the Gb interface is defined in the stage 2 3GPP TS 23.060. |
48.016 | General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Network service | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.016/48016-i00.zip | The present document specifies the Network Service used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface).
The protocol stack on the Gb interface is defined in the stage 2 Technical Specification 3GPP TS 43.060.
The Network Service entity provides network services to the BSSGP entity specified in 3GPP TS 48.018.
The layer 1 of the Gb interface is specified in 3GPP TS 48.014.
In the present document, the communication between adjacent layers and the services provided by the layers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by the present document.
The service primitive model used in the present document is based on the concepts developed in ITU-T Recommendation X.200. |
48.018 | General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.018/48018-i00.zip | The present document specifies or references procedures used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface for control of GSM packet data services.
The functional split between BSS and SGSN is defined in 3GPP TS 23.060 which states that a BSS is responsible for local radio resource allocation. The required procedures between BSS and SGSN are defined in detail in the present document. |
48.020 | Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/48_series/48.020/48020-i00.zip | The present document defines rate adaptation functions to be used in PLMN Base Station Systems (BSS) transcoders and IWF
- for adapting radio interface data rates to the 64 kbit/s used at the A-interface in A/Gb mode and
- for adapting radio interface data rates to the Iu interface in GERAN Iu mode in accordance with 3GPP TS 43.010.
The number of Base Station System - Mobile-services Switching Centre (BSS - MSC) traffic channels supporting data rate adaptation may be limited. In this case some channels may not support data rate adaptation. Those that do, shall conform to this specification.
NOTE: This specification should be considered together with 3GPP TS 44.021 to give a complete description of PLMN rate adaptation. |
48.031 | Location Services (LCS); Serving Mobile Location Centre - Serving Mobile Location Centre (SMLC - SMLC); SMLCPP specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.031/48031-i00.zip | The present document contains the definition of the SMLCPP protocol to be used between two Serving Mobile Location Centres (SMLC).
The LCS architecture is described in 3GPP TS 43.059. The following aspects of it are relevant to the issue:
- each SMLC controls a number of LMUs, and a given LMU is under the direct control of a single SMLC;
- there is a direct communication path, independent of SMLCPP, between a LMU and the SMLC that controls it;
- deciphering keys are controlled by one SMLC in the location area and sent to other SMLCs in the same location area.
SMLCPP runs between two SMLC functions in the same PLMN. Transport is outside the scope of the present document. It assumes a transport service between these functions, as provided by BSSAP-LE. The present document assumes that the underlying transport (e.g., as described by BSSAP-LE specifications) provides for transport and routing for any two pairs of SMLCs which need to run SMLCPP exchanges.
The main functions of SMLCPP are described in [5]. The key aspects are:
a) allowing an SMLC to ask for and obtain information about Radio Interface Timing (RIT), as known from measurements done by LMUs not under its direct control;
c) allowing an SMLC, that controls deciphering keys in the location area, to sent them to other SMLCs in the same location area. |
48.049 | Base Station Controller - Cell Broadcast Centre (BSC-CBC) interface specification; Cell Broadcast Service Protocol (CBSP) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.049/48049-i00.zip | The present document specifies the Cell Broadcast Service Protocol (CBSP) between the Cell Broadcast Centre (CBC) and the Base Station Controller (BSC). |
48.051 | Base Station Controller - Base Transceiver Station (BSC - BTS) interface; General aspects | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.051/48051-i00.zip | The present document is an introduction to the 48.5xx - 48.6xx series of 3GPP Technical Specifications and deals with the definition of the Base Station Controller (BSC) to Base Transceiver Station (BTS) interface defined inside the Base Station System (BSS) for the GSM system. These Technical Specifications define the basic interface with some identified options requiring further elaboration. The BSC-BTS interface is mandatory within GSM only if the BSC and the BTS are not colocated. |
48.052 | Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Interface principles | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.052/48052-i00.zip | The use and general aspects of the A-bis interface are given in 3GPP TS 48.051.
The present document gives the principle basis for the rest of the specifications specifying the interface between the Base Station Controller, BSC, and the Base Transceiver Station, BTS, with its transceivers, TRX. These components together form the Base Station System, BSS. (The interface between MSC and the BSS is specified in 3GPP TS 48.001 and 3GPP TS 48.020).
The intention with this interface is to get a unified way of connecting remotely located BTSs/TRXs to a BSC allowing for the interconnection of BSCs and BTSs/TRXs from different manufacturers.
In order to keep the BTS as simple as possible, BTS contains only those functions which have to recide close to the radio interface. |
48.054 | Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 1 structure of physical circuits | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.054/48054-i00.zip | The use and general aspects of the A-bis interface are given in 3GPP TS 48.051.
The present document defines the structure of the physical layer (layer 1) of the BSC - BTS/TRX interface for supporting traffic channels and control channels. Use of the physical layer for supporting link protocol is covered in 3GPP TS 48.056.
The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium. |
48.056 | Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.056/48056-i00.zip | The present document specifies the link layer used for signalling on the A-bis interface between BSC and BTS. The use and general aspects of the A-bis interface are described in 3GPP TS 48.051 and the interface aspects in 3GPP TS 48.052.
The Link Access Procedure on the D-channel (LAPD) specification used on the A-bis interface in the GSM PLMN is a subset of the EN 300 125 which in turn has less options than the CCITT Recommendation Q.921.
This description contains first the protocol definitions and second the services provided by the layer 2 to the layer 3. |
48.058 | Base Station Controller - Base Transceiver Station (BSC - BTS) Interface; Layer 3 specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.058/48058-i00.zip | The present document specifies the general structure of layer 3 and traffic management procedures and messages used on the A-bis interface to support signalling procedures as defined in 3GPP TS 24.008 and 3GPP TS 44.018. Support for Location Services (LCS) related signalling, as defined in 3GPP TS 23.071, is also included. 3GPP TS 23.071 identifies new A-bis signalling to support BTS-embedded Type B LMUs as well as standalone, Type B LMUs. The standalone Type B LMU supports the layer 1 and 2 signalling for the A-bis as well as the Location Service message defined in the present document.
The use and general aspects of the Base Station Controller (BSC) to Base Station Transceiver (BTS) interface (the A-bis interface) are given in 3GPP TS 48.051.
Network management procedures and messages for the A-bis interface are defined in 3GPP TS 08.59.
The functional split between BSC and BTS is defined in 3GPP TS 48.052. The procedures and messages required to support this split are defined in detail in the present document. |
48.060 | In-band control of remote transcoders and rate adaptors for full rate traffic channels | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.060/48060-i00.zip | When 64 kbit/s traffic channels are used on the Abis interface, the speech shall be coded according to CCITT Recommendation G.711 and the data rate adaptation shall be as specified in 3GPP TS 44.021 and 3GPP TS 48.020.
In the case where 16 kbit/s traffic channels are used for full rate speech, enhanced full rate speech, Adaptive Multi-Rate speech, Adaptive Multi-Rate Wideband speech or full rate data service, then the present document shall apply for frame structure and for control of remote transcoders and additional rate adaptors.
For Adaptive Multi-Rate speech the present document specifies the 16 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS, TCH/AHS, TCH/WFS and O-TCH/WHS). The specification for 8 kBit/s submultiplexing is given in 3GPP TS 48.061, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS).
Additionally, the present document specifies the 32 kBit/s submultiplexing for Adaptive Multi-Rate Wideband speech. However it reuses the frame structure of the 16 kBit/s submultiplexing for Adaptive Multi-Rate speech.
The use and general aspects of the Abis interface are given in 3GPP TS 48.051.
NOTE: The present document should be considered together with the 3GPP TS 06 series of specifications, 3GPP TS 44.021 (Rate Adaptation on the MS-BSS Interface) and 3GPP TS 48.020 (Rate Adaptation on the BS/MSC Interface). |
48.061 | In-band control of remote transcoders and rate adaptors for half rate traffic channels | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.061/48061-i00.zip | The present document describes the protocol between the Base Transceiver Station (BTS) and the remote Transcoder/Rate Adaption Unit (TRAU) for speech and data on half rate traffic channel (TCH/H).
For Half Rate speech and half rate data the protocol is specified for 8 kbit/s and 16 kbit/s submultiplexing scheme.
For Adaptive Multi-Rate speech the present document specifies the 8 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). The specification for 16 kBit/s submultiplexing is given in Rec 3GPP TS 48.060, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS).
The present document should be considered together with the 3GPP TS 46 series, 3GPP TS 44.021 (Rate Adaption on the MS‑BSS Interface) and 3GPP TS 48.020 (Rate Adaption on the BTS/MSC Interface). |
48.071 | Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC-BSS) interface; Layer 3 specification | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.071/48071-i00.zip | The present document contains the coding of information necessary for support of location service operation on the SMLC-BSS interface layer 3.
Clause 2 gives the functional definitions and contents of messages for location service operations. Clause 3 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations. |
48.103 | Base Station System - Media GateWay (BSS-MGW) interface; User plane transport mechanism | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.103/48103-i00.zip | The present document specifies the User Plane data transport protocols used between BSSs and the Core Network (MGWs) across the A interface. The main purpose of the present document is the AoIP description, however for the sake of completeness the AoTDM case is described as well.
Figure 1.1: CS core network logical architecture
Note that the present document does not preclude any Core Network Session Control Protocol implementation (BICC or SIP-I). |
49.008 | Application of the Base Station System Application Part (BSSAP) on the E interface | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/49_series/49.008/49008-i00.zip | The present document describes the subset of Base Station System Application Part (BSSAP) messages and procedures, defined in 3GPP TS 48.006 and 3GPP TS 48.008, which is used on the E‑interface. A general description can be found in 3GPP TS 23.002 and 3GPP TS 23.009.
For the initiation and execution of handover between MSCs a subset of BSSMAP procedures are used. For the subsequent control of resources allocated to the Mobile Station (MS) BSSMAP procedures are used. DTAP is used for the transfer of connection management and mobility management messages between the MS and the controlling MSC. |
49.031 | Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE) | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/49_series/49.031/49031-i00.zip | The present document specifies procedures and information coding that are needed to define and support the BSSAP LCS Extension (BSSAP-LE). The BSSAP-LE message set is applicable to the following GSM interfaces defined in 3GPP TS 43.059:
- Lb interface (BSC-SMLC).
- Lp interface (SMLC-SMLC).
The present document defines message formats and encoding for BSSAP-LE and the particular subsets of it that are applicable to each of the above interfaces. The present document also defines the support for BSSAP-LE message transfer on each of these interfaces using either ITU-T and ANSI versions of SS7 MTP or IETF M3UA/SCTP and SCCP. Additional requirements for the above interfaces that are applicable to BSSAP-LE are also defined – e.g. usage of BSSAP (as defined in 3GPP TS 24.008 and 48.008) on the Lb interface. |
49.995 | General Packet Radio Service (GPRS); Interworking between modified Public Land Mobile Network (PLMN) supporting GPRS and legacy GPRS mobiles | TR | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/49_series/49.995/49995-i00.zip | This report describes issues relating to the GPRS specifications, which lead to the specifications being modified after the placement of GPRS compliant mobiles into the market place.
Where possible the present report clarifies any recommended measures which may be adopted by the GPRS infrastructure to enable interworking to be obtained between the GPRS infrastructure and legacy Mobile Station (MS) implementations of the GPRS specifications.
For each issue this report also defines the time after which all new GPRS mobiles are required to meet the modified specifications.
The lifetime of the herein described measures together with their potential impact on optimal network performance is out of the scope of the present document. |
51.010-4 | Mobile Station (MS) conformance specification; Part 4: Subscriber Identity Module (SIM) application toolkit conformance test specification | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-4/51010-4-i00.zip | The present document describes the technical characteristics and methods of test for testing the SIM Application Toolkit implemented in Mobile Stations (MS) for the Pan European digital cellular communications system and Personal Communication Systems (PCS) operating in the 450 MHz, 480 MHz, 700 MHz, 750 MHz, 850 MHz, 900 MHz, 1 800 MHz and 1 900 MHz frequency band (GSM 400, GSM 700, GSM 750, GSM 850, GSM 900, DCS 1 800 and PCS 1 900) within the European digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [19] and ETS 300 406 [20].
The present document is valid for MS implemented according to GSM Phase2+ R96, or R97, or R98, or R99.
The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
The present document is part of the GSM-series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related ETSs or ENs, nor is it created to provide full understanding of (or parts of) the GSM 400, GSM 700, GSM 850, GSM 900, DCS1800 and PCS1900 systems . The present document lists the requirements, and provides the methods of test for testing the SIM Application Toolkit implemented in a MS for conformance to the GSM standard.
For a full description of the system, reference should be made to all the GSM technical specifications or GSM related ETSs or ENs. Clause 2 provides a complete list of the GSM technical specifications, GSM related ETSs, ENs, and ETRs, on which this conformance test specifications is based.
If there is a difference between this present conformance document, and any other GSM technical specification or GSM related ETS or EN, or 3GPP TS, then the other GSM technical specification or GSM related ETS or EN or 3GPP TS shall prevail.
Normative requirements for the SIM and SIM Application Toolkit are only specified up to Rel-4. The present document is only available in this release for allowing maintenance of test cases. The core features related to those test cases remain applicable only to the releases in which they have been specified. |
51.013 | Test specification for Subscriber Identity Module (SIM) Application Programming Interface (API) for Java Card | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.013/51013-i00.zip | The present document covers the minimum characteristics considered necessary in order to provide compliance to 3GPP TS 43.019 [7].
The present document describes the technical characteristics and methods of test for testing the SIM API for Java CardTM (3GPP TS 43.019 [7]) implemented in the Subscriber Identity Modules (SIMs) for GSM. It specifies the following parts:
- test applicability;
- test environment description;
- tests format;
- test area reference;
- conformance requirements;
- test auite files;
- test procedure;
- test coverage; and
- a description of the associated testing tools that shall be used. |
51.021 | Base Station System (BSS) equipment specification; Radio aspects | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/51_series/51.021/51021-i00.zip | The present document specifies the Radio Frequency (RF) test methods and conformance requirements for GSM 400, GSM 700, T-GSM 810, GSM 900, ER-GSM 900 and DCS 1800, PCS 1900, GSM 850, MXM 850 and MXM 1900 Base Station Systems (BSS)s. These have been derived from, and are consistent with, the core GSM specifications specified in the requirements reference subclause of each test with the exception that requirements expressed as a reference to regulatory documents (e.g. FCC) have not been included in the present document.
The present document is applicable to BSS meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to BSS meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support.
Conformance requirements may be tested to verify all aspects of the performance of a BSS. These minimum requirements are intended to be used by manufacturers and operators to allow conformance and acceptance testing to be performed in a consistent manner; the tests to be performed should be agreed between the parties.
In some tests there are separate requirements for micro‑BTS and BTS. If there is no separate requirement for a micro‑BTS, the requirements for the BTS apply to a micro‑BTS.
In Rel-7, higher symbol rate is introduced for EGPRS2-B. EGPRS2-A and all other channels use normal symbol rate. For definition of normal and higher symbol rate see 3GPP TS 45.004. All tests and requirements apply to both symbol rates except otherwise stated in the test.
In some tests there are separate requirements for multicarrier BTS, that apply for all classes of multicarrier BTS (Wide Area, Medium Range and Local Area, cf. [22]) unless otherwise stated. If there is no separate requirement for a multicarrier BTS class, the requirement designated for BTS and normal BTS apply to that multicarrier BTS class.
In Rel-12, BTS operating in the ER-GSM 900 band is introduced. In some tests there are separate requirements for BTS operating in the ER-GSM 900 band. If there is no separate requirement, the requirements for normal BTS apply.
In Rel-13, BTS support of a low-complexity, low data throughput service in environments experiencing high propagation attenuation as indoors in basements etc. is introduced. This service, based on EGPRS, with extended coverage is called EC-GSM-IoT. The requirements for EGPRS apply in case no specific requirement is explicitly stated for EC-GSM-IoT.
In the present document, the reference point for RF connections (except for the measurement of mean transmitted RF carrier power) is the antenna connector, as defined by the manufacturer. The present document does not apply to repeaters or RF devices which may be connected to an antenna connector of a BSS, except as specified in subclause 4.10. |
51.026 | Base Station System (BSS) equipment specification; Part 4: Repeaters | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/51_series/51.026/51026-i00.zip | The present document describes the Radio Frequency (RF) tests for GSM repeaters (frequency bands according to clause 4.1) which receive, amplify, and retransmit a received Mobile Station (MS) signal in the GSM MS transmit band and simultaneously receive, amplify and retransmit a received Base Transceiver Station (BTS) RF signal in the GSM BTS transmit band.
The present document is applicable to repeaters meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to repeaters meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support. |
52.008 | Telecommunication management; GSM subscriber and equipment trace | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/52_series/52.008/52008-i00.zip | The present document specifies the Trace facility for GSM where it refers to:
- subscriber tracing (tracing of International Mobile Subscriber Identity (IMSI));
- equipment tracing (tracing of International Mobile station Equipment Identity (IMEI)).
It does not cover:
- types of trace which relate more to network elements than to individual subscribers e.g. tracing events within a Base Station System (BSS), and so on;
- tracing of all possible parties in e.g. a multi-party call, (although multiple calls related to the IMSI specified in the trace type field are traceable).
It also refers only to tracing activated from the OSF and not to that activated by means of local Man Machine Interface (MMI). |
55.216 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 1: A5/3 and GEA3 specifications | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.216/55216-i00.zip | The present document specifies the A5/3 and GEA3 specification. 0A References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [2] 3GPP Task Force Specification: "Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 1: A5/3 and GEA3 specification" version 1.1, 2002-05-30 Note: Reference [2] is available via http://portal.etsi.org/dvbandca/home.asp and is subject to licensing conditions described at this site. 0B Definitions, symbols and abbreviations 0B.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. A term defined in the latter document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. 0B.2 Symbols For the purposes of the present document, the symbols defined in the 3GPP Task Force Specification [2] apply. 0B.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the 3GPP Task Force Specification [2] apply. An abbreviation defined in the latter document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. 0C Technical provisions The technical provisons of the current document are contained in the 3GPP Task Force Specification [2]. Annex D (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2002-05 - - - - ETSI SAGE first publication SAGE V1.0 2002-07 - - - - Agreed at SA WG3 #24 for presentation to TSG SA #17 for approval. Converted into 3GPP TS format as TS 55.216 (Technically equivalent to SAGE V1.0) SAGE V1.0 1.0.0 2002-09 SP-17 SP-020506 - - Approved for Release 6 - version 6.0.0 1.0.0 6.0.0 2002-12 SP-18 SP-020721 001 - EGPRS algoritm 6.0.0 6.1.0 2003-09 SP-19 SP-030490 002 - Clarification on the usage of the Key length 6.1.0 6.2.0 2007-12 SP-38 SP-070776 003 - Conversion to pointer to export controlled document Note: Version 7.0.0 is a "readme" file placeholder with no technical content. 6.2.0 7.1.0 2008-12 SP-42 - - Ugrade to Release 8 7.1.0 8.0.0 2009-12 - - - - Update to Rel-9 version (MCC) 8.0.0 9.0.0 2011-03 - - - - Update to Rel-10 version (MCC) 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 2020-07 - - - - Update to Rel-16 version (MCC) 15.0.0 16.0.0 2022-03 - - - - Update to Rel-17 version (MCC) 16.0.0 17.0.0 2024-03 - - - - Update to Rel-18 version (MCC) 17.0.0 18.0.0 |
52.402 | Telecommunication management; Performance Management (PM); Performance measurements - GSM | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/52_series/52.402/52402-i00.zip | The present document describes the TMN model for the administration of measurements and the collection of measurement result data in a GSM system. It also includes the measurement definitions for GSM. The concept and functional requirements for performance management in wireless GSM and UMTS systems is set out in TS 32.401 [31]. |
55.205 | Specification of the GSM-MILENAGE algorithms: An example algorithm set for the GSM Authentication and Key Generation Functions A3 and A8 | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.205/55205-i00.zip | The present document contains an example set of algorithms which may be used as the GSM authentication and key generation functions A3 and A8. (It is not mandatory that the particular algorithms specified in this document are used - the A3 and A8 functions are operator-specifiable rather than being fully standardised).
Section 3 (normative) introduces the algorithms and describes their input and output parameters. Section 4 (normative) defines the algorithms. Section 5 (informative) describes an alternative algorithm that some operators may prefer. Section 6 (informative) provides test data. |
55.217 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 2: Implementors' test data | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.217/55217-i00.zip | The present document specifies mplementors' test data for the A5/3 and GEA3 specification. 0A References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [2] 3GPP Task Force Specification: "Specification of the A5/3 encryption algorithms for GSM and EDGE, and the GEA3 encryption algorithm for GPRS; Document 2: Implementors' test data". Note: Reference [2] is available via http://portal.etsi.org/dvbandca/home.asp and is subject to licensing conditions described at this site. 0B Definitions, symbols and abbreviations 0B.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. A term defined in the latter document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. 0B.2 Symbols For the purposes of the present document, the symbols defined in the 3GPP Task Force Specification [2] apply. 0B.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [2] and in the 3GPP Task Force Specification [2] apply. An abbreviation defined in the latter document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. 0C Technical provisions The technical provisons of the current document are contained in the 3GPP Task Force Specification [2]. Annex A: Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2002-05 - - - - ETSI SAGE first publication SAGE V1.0 2002-07 - - - - Agreed at SA WG3 #24 for presentation to TSG SA #17 for approval. Converted into 3GPP TS format (TS 55.217) (Technically equivalent to SAGE V1.0) SAGE V1.0 1.0.0 2002-09 SP-17 SP-020506 - - Approved for Release 6 - version 6.0.0 1.0.0 6.0.0 2002-12 SP-18 SP-020721 001 - EGPRS algoritm 6.0.0 6.1.0 2007-12 SP-38 SP-070776 002 - Conversion to pointer to export controlled document 6.1.0 7.1.0 2008-12 SP-42 - - - Upgrade to Release 8 7.1.0 8.0.0 2009-12 SP-46 - - - Upgrade to Release 9 8.0.0 9.0.0 Note: Version 7.0.0 is a "readme" file placeholder with no technical content. 2011-03 SP-51 -- -- -- Upgrade to Release 10 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 2020-07 - - - - Update to Rel-16 version (MCC) 15.0.0 16.0.0 2022-03 - - - - Update to Rel-17 version (MCC) 16.0.0 17.0.0 2024-03 - - - - Update to Rel-18 version (MCC) 17.0.0 18.0.0 |
52.021 | Network Management (NM) procedures and messages on the A-bis interface | TS | 18.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/52_series/52.021/52021-i00.zip | The present document addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities.
There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. The present document addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to the present document it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality.
It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document. |
55.218 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 3: Design conformance test data | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.218/55218-i00.zip | The present document specifies the A5/3 and GEA3 specification. 0A References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". [2] 3GPP Task Force Specification: "Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 3: Design and conformance test data". Note: Reference [2] is available via http://portal.etsi.org/dvbandca/home.asp and is subject to licensing conditions described at this site. 0B Definitions, symbols and abbreviations 0B.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. A term defined in the latter document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. 0B.2 Symbols For the purposes of the present document, the symbols defined in the 3GPP Task Force Specification [2] apply. 0B.3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [1] and in the 3GPP Task Force Specification [2] apply. An abbreviation defined in the latter document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. 0C Technical provisions The technical provisons of the current document are contained in the 3GPP Task Force Specification [2]. Annex A: (informative) Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 2002-05 - - - - ETSI SAGE first publication SAGE V1.0 2002-07 - - - - Agreed at SA WG3 #24 for presentation to TSG SA #17 for approval. Converted into 3GPP TS format (TS 55.218) (Technically equivalent to SAGE V1.0) SAGE V1.0 1.0.0 2002-09 SP-17 SP-020506 - - Approved for Release 6 - version 6.0.0 1.0.0 6.0.0 2002-12 SP-18 SP-020721 001 - EGPRS algoritm 6.0.0 6.1.0 2007-12 SP-38 SP-070776 002 - Conversion to pointer to export controlled document 6.1.0 7.1.0 2008-12 SP-42 - - - Upgrade to Release 8 7.1.0 8.0.0 2009-12 SP-46 - - - Upgrade to Release 9 8.0.0 9.0.0 Note: Version 7.0.0 is a "readme" file placeholder with no technical content. 2011-03 - - - - Update to Rel-10 version (MCC) 9.0.0 10.0.0 2012-09 - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2016-01 - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 2017-03 SA#75 - - - Promotion to Release 14 without technical change 13.0.0 14.0.0 2018-06 - - - - Update to Rel-15 version (MCC) 14.0.0 15.0.0 2020-07 - - - - Update to Rel-16 version (MCC) 15.0.0 16.0.0 2022-03 - - - - Update to Rel-17 version (MCC) 16.0.0 17.0.0 2024-03 - - - - Update to Rel-18 version (MCC) 17.0.0 18.0.0 |
55.226 | 3G Security; Specification of the A5/4 Encryption Algorithms for GSM and ECSD, and the GEA4 Encryption Algorithm for GPRS | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.226/55226-i00.zip | This specification of the A5/4 encryption algorithms for GSM and ECSD, and of the GEA4 encryption algorithm for GPRS has been derived from TS 55.516 [1]: Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. The only essential change is the change of external key length input from 64 bits to 128 bits.
This document should be read in conjunction with the entire specification of the A5/3 and GEA3 algorithms:
- Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. Document 1: A5/3 and GEA3 Specifications.
- Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. Document 2: Implementors’ Test Data.
- Specification of the A5/3 Encryption Algorithms for GSM and ECSD, and the GEA3 Encryption Algorithm for GPRS. Document 3: Design Conformance Test Data.
The normative part of the specification of the block cipher (KASUMI) on which the A5/3, A5/4, GEA3 and GEA4 algorithms are based can be found in TS 35.202 [5]. |
55.236 | Specification of A8_V MILENAGE Algorithm: An example algorithm for the key generation function A8_V | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.236/55236-i00.zip | The present document contains an example algorithm which may be used as the VSTK key generation function A8_V as described in TS 43.020 [4]. (It is not mandatory that the particular algorithm specified in this document is used - the A8_V function is operator-specifiable rather than being fully standardised.)
Clause 4 introduces the algorithm and describes the input and output parameters. Clause 5 defines the algorithm. Clause 6 provides test data. |
55.241 | Specification of the GIA4 integrity algorithm for General Packet Radio Service (GPRS); GIA4 specification | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.241/55241-i00.zip | The present document defines the technical details of the 3GPP integrity algorithm GIA4. |
55.242 | Specification of the GIA4 integrity algorithm for General Packet Radio Service (GPRS); Implementers' test data | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.242/55242-i00.zip | The present document defines the implementers test data of the 3GPP integrity algorithm GIA4. |
55.243 | Specification of the GIA4 integrity algorithm for General Packet Radio Service (GPRS); Design conformance test data | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.243/55243-i00.zip | The present document defines the Design conformance test data for the 3GPP integrity algorithm GIA4. |
55.251 | Specification of the GEA5 and GIA5 encryption algorithms for General Packet Radio Service (GPRS); GEA5 and GIA5 algorithm specification | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.251/55251-i00.zip | The present document defines the technical details of the 3GPP confidential algorithm GEA5 and the 3GPP integrity algorithm GIA5. |
55.252 | Specification of the GEA5 encryption and GIA5 integrity algorithms for General Packet Radio Service (GPRS); Implementers' test data | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.252/55252-i00.zip | The present document defines the implementers test data of the 3 GPP encryption algorithm GEA5 and integrity algorithm GIA5. |
55.253 | Specification of the GEA5 encryption and GIA5 integrity algorithms for General Packet Radio Service (GPRS); Design conformance test data | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.253/55253-i00.zip | The present document defines the design conformance test data of the 3GPP encryption algorithm GEA5 and integrity algorithm GIA5. |
55.919 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 4: Design and evaluation report | TR | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.919/55919-i00.zip | This Technical Report has been prepared by the ETSI SAGE GSM A5/3 Task Force, and gives a detailed report on the design and evaluation of the A5/3 encryption algorithms for GSM and ECSD, and of the GEA3 encryption algorithm for GPRS (including EGPRS). |
21.101 | Technical Specifications and Technical Reports for a UTRAN-based 3GPP system | TS | 17.2.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.101/21101-h20.zip | |
21.111 | USIM and IC card requirements | TS | 17.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.111/21111-h00.zip | |
21.201 | Technical Specifications and Technical Reports for an Evolved Packet System (EPS) based 3GPP system | TS | 17.1.1 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.201/21201-h11.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.