id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
31.110
|
Numbering system for telecommunication IC card applications
|
TS
|
4.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/31_series/31.110/31110-410.zip
|
The present document describes the numbering system for Application IDentifiers (AID) for 3G telecommunication Integrated Circuits (IC) card applications.
The numbering system described in the present document provides a means for an application and related services offered by a provider to identify if a given card contains the elements required by its application and related services.
An AID is used to address an application in the card. It consists of a Registered application provider IDentifier (RID) and a Proprietary application Identifier eXtension (PIX).
The present document describes the coding of the PIX.
|
33.103
|
3G security; Integration guidelines
|
TS
|
4.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.103/33103-420.zip
|
This technical specification defines how elements of the 3G-security architecture are to be integrated into the following entities of the system architecture.
- Home Environment Authentication Centre (HE/AuC)
- Serving Network Visited Location Register (VLR/SGSN)
- Radio Network Controller (RNC)
- Mobile station User Identity Module (UIM)
- Mobile Equipment (ME)
This specification is derived from 3G "Security architecture". [1]
The structure of this technical specification is a series of tables, which describe the security information and cryptographic functions to be stored in the above entities of the 3G system.
For security information, this is in terms of multiplicity, lifetime, parameter length and whether mandatory or optional.
For the cryptographic functions, the tables also include an indication of whether the implementation needs to be standardised or can be proprietary.
The equivalent information for the alternative Temporary Key proposal is included in an appendix to this document.
|
33.120
|
Security Objectives and Principles
|
TS
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.120/33120-400.zip
|
The present document gives the objectives and principles of 3GPP security.
The principles state what is to be provided by 3G security as compared to the security of second generation systems. The principles will also ensure that 3G security can secure the new services and new service environments offered by 3G systems.
The objectives give general, high level requirements for 3GPP security which will be expanded upon in 3G TS 21.133 [1].
The priorities for the implementation of 3GPP security are also given.
|
33.901
|
Criteria for cryptographic Algorithm design process
|
TR
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.901/33901-400.zip
|
This report discusses the possibilities for acquisition of the cryptographic algorithms that has to be standardised in UMTS. The focus is on the encryption function used in the data confidentiality mechanism and the message authentication function used in the signalling data integrity mechanism.
First certain aspects of the process and desired results for an algorithm specification and their pro's and cons will be given. These aspects will include the possible design strategies, the evaluation strategies, the possibilities for distribution of the algorithms and the options for the liability and responsibility for the algorithm.
Then a number of the most realistic scenarios for the algorithm specification will be presented. These scenarios will be used as a basis to make a final choice for the specification process for cryptographic algorithms in third generation mobile systems. Finally, a preferred procedure will be described.
|
33.902
|
Formal Analysis of the 3G Authentication Protocol
|
TR
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.902/33902-400.zip
|
This report contains formal analyses of the authentication and key agreement (AKA) protocol specified in 3G TS 33.102. These analyses are carried out using various means of formal logic suitable for demonstrating security and correctness properties of the AKA protocol.
The structure of this technical specification is as follows:
clause 2 lists the references used in this specification;
clause 3 lists the definitions and abbreviations used in this specification;
clause 4 refers to the main body of this report. The main body is only referred to because it is not available in Word-, but only in pdf-format. The corresponding .pdf-documents are attached to this document.
|
33.908
|
3G Security; General report on the design, specification and evaluation of 3GPP standard confidentiality and integrity algorithms
|
TR
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.908/33908-400.zip
|
This technical report is a description of the work undertaken by SAGE Task Force for the design of the standard 3GPP Confidentiality and Integrity Algorithms (SAGE TF 3GPP), and to formally approve the release of these algorithms to 3GPP.
With regard to the design of the algorithms, the scope of the present document is confined to a description of the design criteria, the design methodology and an outline of the content and structure of the specification and test data documents.
The standard 3GPP Confidentiality and Integrity Algorithms are based on a Block Cipher named KASUMI. The algorithms specification and associated test data are documented in the Specification of the 3GPP Confidentiality and Integrity Algorithms which consists of the following four documents:
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 1: f8 and f9 specifications (TS 35.201).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 2: KASUMI algorithm specification (TS 35.202).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 3: Implementors' test data (TS 35.203).
- Specification of the 3GPP Confidentiality and Integrity Algorithms; Document 4: Design conformance test data (TS 35.204).
With regard to the evaluation of the algorithm, the scope of this report is restricted to a description of the evaluation criteria, the method of evaluation and the main conclusions from the evaluation that led to the Task Force approving the specification. A detailed summary of conclusions of the evaluation is provided in a public evaluation report [3] produced by the Task Force.
|
33.909
|
3G Security; Report on the design and evaluation of the MILENAGE algorithm set; Deliverable 5: An example algorithm for the 3GPP authentication and key generation functions
|
TR
|
4.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.909/33909-401.zip
|
This public report contains a detailed summary of the work performed during the design and evaluation of the 3GPP Authentication Functions denoted as the MILENAGE algorithm set. It contains all results and findings from this work and should be read as a supplement to the specifications of the algorithms in ref. [3] and the general project report, ref. [4].
|
41.061
|
General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements
|
TS
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/41_series/41.061/41061-400.zip
|
This TS constitutes a requirements specification for a cryptographic algorithm which is used to protect General Packet Radio Services (GPRS) as specified by GSM 02.60.
This TS is intended to provide the ETSI Security Algorithms Group of Experts (SAGE) with the information it requires in order to design and deliver a technical specification for such an algorithm.
The specification covers the intended use of the algorithm and use of the algorithm specification, technical requirements on the algorithm, requirements on the algorithm specification and test data, and quality assurance requirements on both the algorithm and its documentation. The specification also outlines the background to the production of this specification.
|
42.009
|
Security aspects
|
TS
|
4.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.009/42009-410.zip
|
Bearer and Teleservices, as respectively defined in GSM 02.02 and GSM 02.03, are the objects which the GSM PLMN operators offer to their customers. Besides these basic telecommunications services, features which aim at up‑grading these basic services need also to be offered. Due to the use of radiocommunications in a PLMN, which are of a special nature compared to classical distribution transmission techniques used in the fixed networks, such a category of features is related to security aspects.
In a GSM PLMN, both the users and the network operator have to be protected against undesirable intrusion of third parties. However, measures should be provided for in order to insure maximum protection of the rights of the individuals concerns. As a consequence, a security feature is either a supplementary service to Tele or Bearer services, which can be selected by the subscriber, or a network function involved in the provision of one or several telecommunication services.
The purpose of the present document is to define the security features which are to be available in a GSM PLMN, together with the associated levels of protection. The present document is only concerned with those security features which aim at the up‑grading of the security in a GSM PLMN. In particular, end‑to‑end security is outside the scope of the present document.
The implementation aspects of security features are described in GSM 03.20.
|
42.017
|
Subscriber Identity Module (SIM); Functional characteristics
|
TS
|
4.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.017/42017-400.zip
|
The present document defines the functional characteristics and requirements of the Subscriber Identity Module (SIM) for use in Digital Cellular Telecommunications System (GSM) applications. All references to GSM shall apply equally to any band specified for GSM unless otherwise stated.
The SIM is the entity that contains the identity of the subscriber. When placed in a Mobile Equipment (ME), together they become a Mobile Station (MS) which may then register onto a GSM network.
The primary function of the SIM in conjunction with a GSM network is to authenticate the validity of an MS when accessing the network. In addition it provides a means to authenticate the user and may also store other subscriber-related information or applications. Subscription entitlements are stored not in the SIM, but in the network.
If the SIM functionality is incorporated into a multi-application card, the GSM application may be used in other telecommunication applications.
In addition, SIMs are permitted to contain non-GSM functionality. In the case of multi-application cards, the present document defines just the GSM application.
|
50.059
|
Enhanced Data rates for GSM Evolution (EDGE); Project scheduling and open issues for EDGE
|
TR
|
4.0.1
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/50_series/50.059/50059-401.zip
|
The purpose of the present document is to describe the schedules of the Enhanced Data rate for GSM Evolution (EDGE) standardisation process and to view it's current state and open issues that are still under discussion. It also lists the new standards and necessary amendments to the GSM/DCS phase 2+ specifications for the technical realisation of the function.
|
51.011
|
Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface
|
TS
|
4.15.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.011/51011-4f0.zip
|
The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME) for use during the network operation phase of GSM as well as those aspects of the internal organization of the SIM which are related to the network operation phase. This is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in the 3GPP TS 42.017 [6]. The requirements for the physical characteristics of the SIM, the electrical signals and the transmission protocols are all defined in accordance with the 3GPP TS 31.101 [55] except when stated otherwise in the present document.
The present document defines:
‑ the model which shall be used as a basis for the design of the logical structure of the SIM;
‑ the security features;
‑ the interface functions;
‑ the commands;
‑ the contents of the files required for the GSM application;
‑ the application protocol.
The present document does not specify any aspects related to the administrative management phase. Any internal technical reallocation of either the SIM or the ME are only specified where these reflect over the interface. It does not specify any of the security algorithms which may be used.
The present document defines the SIM/ME interface for GSM Phase 2. While all attempts have been made to maintain phase compatibility, any issues that specifically relate to Phase 1 should be referenced from within the relevant Phase 1 specification.
|
51.014
|
Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface
|
TS
|
4.5.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.014/51014-450.zip
|
The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME), and mandatory ME procedures, specifically for "SIM Application Toolkit".
The present document refers in its majority to the ETSI TS 102 223 [37] "Card Application Toolkit", which describes the generic aspects of application toolkits within the SIM.SIM Application Toolkit is a set of commands and procedures for use during the network operation phase of GSM, in addition to those defined in TS 51.011 [20].
Specifying the interface is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in TS 42.017 [3].
The present document defines:
- the commands;
- the application protocol;
- the mandatory requirements on the SIMand ME for each procedure.
Unless otherwise stated, references to GSM also apply to DCS 1800.
The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the SIMor the ME are only specified where these reflect over the interface. This standard does not specify any of the security algorithms which may be used.
Within the context of this document, the term "terminal" used in TS 102 223 [37] refers to the Mobile Equipment (ME).
Within the context of this document, the term "UICC" used in TS 102 223 [37] refers to the SIM card.
Within the context of this document, the term "NAA" used in TS 102 223 [37] refers to the SIM application.
|
51.017
|
Subscriber Identity Module (SIM) test specification
|
TS
|
4.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.017/51017-420.zip
|
The present document provides the Conformance Test Specification for the Subscriber Identity Module defined in 3GPP TS 51.011 [1], TS 11.012[8] and TS 11.018[9].
|
01.01
|
Technical Specifications and Technical Reports for a GERAN-based 3GPP system
|
TS
|
8.20.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.01/0101-8k0.zip
|
The present document identifies the 3GPP system specifications for Release 1999. The specifications and reports of 3GPP Release 1999 have a major version number 3 (i.e. 3.x.y). The listed Specifications are required to build a system based on GERAN radio technology.
|
01.04
|
Abbreviations and acronyms
|
TR
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.04/0104-800.zip
|
This ETSI Technical Report (TR) provides the abbreviations and acronyms to be used throughout the GSM specifications.
All abbreviations are presented in the singular, but are equally applicable to the plural.
|
01.31
|
Fraud Information Gathering System (FIGS); Service requirements; Stage 0
|
TR
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.31/0131-800.zip
| |
01.33
|
Lawful Interception requirements for GSM
|
TR
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.33/0133-800.zip
| |
01.61
|
General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements
|
TS
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.61/0161-800.zip
| |
02.09
|
Security aspects
|
TS
|
8.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.09/0209-810.zip
|
Bearer and Teleservices, as respectively defined in GSM 02.02 and GSM 02.03, are the objects which the GSM PLMN operators offer to their customers. Besides these basic telecommunications services, features which aim at up‑grading these basic services need also to be offered. Due to the use of radiocommunications in a PLMN, which are of a special nature compared to classical distribution transmission techniques used in the fixed networks, such a category of features is related to security aspects.
In a GSM PLMN, both the users and the network operator have to be protected against undesirable intrusion of third parties. However, measures should be provided for in order to insure maximum protection of the rights of the individuals concerns. As a consequence, a security feature is either a supplementary service to Tele or Bearer services, which can be selected by the subscriber, or a network function involved in the provision of one or several telecommunication services.
The purpose of the present document is to define the security features which are to be available in a GSM PLMN, together with the associated levels of protection. The present document is only concerned with those security features which aim at the up‑grading of the security in a GSM PLMN. In particular, end‑to‑end security is outside the scope of the present document.
The implementation aspects of security features are described in GSM 03.20.
|
02.17
|
Subscriber Identity Module (SIM); Functional characteristics
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.17/0217-800.zip
|
The present document defines the functional characteristics and requirements of the Subscriber Identity Module (SIM) for use in Digital Cellular Telecommunications System (GSM) applications. All references to GSM shall apply equally to any band specified for GSM unless otherwise stated.
The SIM is the entity that contains the identity of the subscriber. When placed in a Mobile Equipment (ME), together they become a Mobile Station (MS) which may then register onto a GSM network.
The primary function of the SIM in conjunction with a GSM network is to authenticate the validity of an MS when accessing the network. In addition it provides a means to authenticate the user and may also store other subscriber-related information or applications. Subscription entitlements are stored not in the SIM, but in the network.
If the SIM functionality is incorporated into a multi-application card, the GSM application may be used in other telecommunication applications.
In addition, SIMs are permitted to contain non-GSM functionality. In the case of multi-application cards, the present document defines just the GSM application.
|
02.19
|
Subscriber Identity Module Application Programming Interface (SIM API); Stage 1
|
TS
|
8.1.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.19/0219-810.zip
|
This Technical Specification defines the stage one description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM. Stage one is an overall service description, and does not deal with the implementation details of the API.
This TS includes information applicable to network operators, service providers and terminal, SIM, switch and database manufacturers.
This TS contains the core requirements which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a SIM API should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this TS may implement requirements which are considered outside the scope of this TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
|
02.33
|
Lawful Interception (LI); Stage 1
|
TS
|
8.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.33/0233-801.zip
|
The present document provides the stage 1 description for a lawful interception function to be implemented in a given GSM PLMN in order for a network operator to be able to fulfil national lawful requirements. It shall be noted that national variation may exist but it is not the intention for the present document to encompass all of them. The purpose of the present document is to cover the options which may be selectable according to national regulations or as required by the GSM PLMN operator in co-operation with their suppliers.
In the preparation of the present document general reference was made to the European Union Council Resolution, January 1995: "International Requirements for the Lawful Interception of Telecommunications".
|
02.43
|
Support of Localised Service Area (SoLSA); Service description; Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.43/0243-800.zip
|
This technical specification, specifies a mechanism, which can be used as a platform for providing special tariffs and/or special set of service features for certain subscribers within a regionally restricted area or areas.
The motivation for this concept is to create means for network operators to build new service and tariff packages, which take into account subscriber groups and their needs.
The localised service area is both an optional network feature and an optional UE feature. Usage and implementation of the different SoLSA service features may vary according to operator's service packages.
This feature is not intended to replace the existing method of cell selection, cell indication and handover.
“Support of Localised service area (SoLSA)” is renamed Phase 2+ item “Support of Home Area Priority”
Note: The present document covers description for GERAN support only. UTRAN support will be added in latter releases.
|
02.48
|
Security mechanisms for the SIM Application Toolkit; Stage 1
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.48/0248-800.zip
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a GSM PLMN Entity and a SIM.
The security mechanisms which are specified are independent of applications.
The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (GSM 03.48).
The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
|
02.53
|
Tandem Free Operation (TFO); Service description; Stage 1
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.53/0253-801.zip
|
The present document specifies the stage 1 description for the Tandem Free Operation (TFO) feature which provides the capability to avoid using two GSM speech codecs in mobile to mobile speech calls. The primary aim is to realise improvements in speech quality. The TFO mode of operation could also be used to reduce inter-Mobile services Switching Center (MSC) transmission bandwidth requirements.
In analogy with ITU-T Recommendations I.130 [1], Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
|
02.56
|
GSM Cordless Telephony System (CTS), Phase 1; Service description; Stage 1
|
TS
|
8.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.56/0256-801.zip
|
The scope of the present document is to describe the Service aspects of a GSM Cordless Telephony System (CTS), which provides the possibility for users of GSM terminals to have cordless access to a fixed network, such as PSTN/ISDN or a radio network such as GSM.
Due to the time constraints to have a first specification ready for market needs, a phased approach is necessary. The first phase aims primarily at an application supporting the speech teleservice (including DTMF support) in a residential single cell environment. The focus is on the requirements necessary to elaborate the radio interface and the security aspects for such an application.
To not prevent or impede the evolution of CTS to additional services and functions, later phases may have to be considered when now defining the means to fulfil the above mentioned requirements for the first phase of CTS. Therefore, additional support on the CTS radio interface for later phase services (e.g. SMS, subscriber authentication and GSM supplementary services), is included already in CTS Phase 1, provided that such services are clearly defined. Other expected services and functions in later phases are included in annex A.
The standardisation of the physical layers of the GSM-CTS fixed network interface is not in the scope of the present document. However, consideration may need to be given to communication of application data between CTS and PLMN via the fixed network.
|
02.68
|
Voice Group Call Service (VGCS); Stage 1
|
TS
|
8.2.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.68/0268-821.zip
|
The present document specifies the stage one description of the Voice Group Call Service (VGCS) which allows speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple mobile service subscribers involved in the VGCS call per cell.
The VGCS is applicable to all mobile stations in a certain network and area which have the technical capability and the corresponding subscription, respectively, to participate in a VGCS call.
NOTE: It is not considered as requirement that normal GSM phase 2+ mobile stations will be able to be used for this service.
The service is described from the service subscriber's and user's point of view; in particular:
- the procedure for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM services and features.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile Communications (GSM) specifications.
The present document defines a teleservice of the digital cellular telecommunications system GSM. Any interaction with other services and/or networks not dealt with in clauses 7 or 8 are outside the scope of the present document.
|
02.69
|
Voice Broadcast Service (VBS); Stage 1
|
TS
|
8.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.69/0269-820.zip
|
The present document specifies the stage one description of the Voice Broadcast Service (VBS) which allows the distribution of speech (or other signals which can be transmitted via the speech codec), generated by a service subscriber, into a predefined geographical area to all or a group of service subscribers located in this area.
The Voice Broadcast Service (VBS) is applicable to all mobile stations in a certain network and area which have the technical capability and the respective subscription to receive a VBS call.
NOTE: It is not considered as requirement that normal GSM Phase 2+ mobile stations will be able to be used for this service.
The service is described from the service subscriber's and user's point of view; in particular:
- the procedure for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM services and features.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile communications (GSM) specifications.
The present document defines a teleservice of the digital cellular telecommunication system GSM. Any interaction with other services and/or networks not dealt within clauses 8 or 9 are outside the scope of the present document.
|
02.76
|
Noise Suppression for the AMR
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.76/0276-801.zip
|
The present document specifies the stage 1 description for the Noise Suppression feature for the AMR codec which enhances the input speech signal corrupted by acoustic noise. In analogy with CCITT Recommendations I.130†[1], Stage 1 is an overall service description, from the service subscriber’s and user’s standpoints, that views the network as a single entity which provides services to the user.
|
03.05
|
Technical performance objectives
|
TR
|
8.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.05/0305-800.zip
|
The present document contains technical performance objectives that should be met for the fixed infrastructure of GSM PLMNs. Concerning transmission delay for the PLMN in clause 4, the requirements should also be met by GSM Mobile Stations (MS)s.
These performance design objectives are applicable to all implementations at all points in the growth cycle up to the maximum size. These reference loads and performance objectives may be used by manufacturers in designing GSM PLMNs and by Administrations or Recognised Private Operating Agencies (RPOA)s in evaluating a specific design or for comparing different designs for potential use in the Administration's or RPOA's intended implementation.
|
03.10
|
GSM Public Land Mobile Network (PLMN) Connection Types
|
TS
|
8.3.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.10/0310-830.zip
|
A GSM PLMN may be described by a limited set of access interfaces (refer to 3GPP TS 04.02 and 02.01) and a limited set of GSM PLMN connection types to support the telecommunication services described in the 3GPP 02-series of specifications. This Global System for Mobile communications Technical Specification (TS) identifies and defines these connection types in so far as they relate to the particular network capabilities for a GSM PLMN.
The basic lower layer capabilities of a GSM PLMN are represented by a set of GSM PLMN connection types. The definition of a set of GSM PLMN connection types provides the necessary input to identify network capabilities of a GSM PLMN. In addition to describing network capabilities of a GSM PLMN, the identification of connection types facilitates the specification of network-to-network interfaces. It may also assist in the allocation of network performance parameters.
This specification should be considered in conjunction with other 3GPP specifications with particular reference to 3GPP TS 01.02, 02.01, 22.002, 02.03, 03.01, 23.002, 04.02 and 04.03.
This specification provides a bridge between the service specification in the 3GPP TS 02 and 22-series of specifications and the more detailed specifications such as the 3GPP TS 03, 04, 23, 24, 27 and 29 series. As such, it establishes a framework for the specification and understanding of the more detailed specifications. It is therefore not a specification against which detailed conformance testing can be performed. However, it shall be considered mandatory for the understanding of the more detailed specifications and used to resolve issues of conflict in these specifications.
From GSM R99 onwards the following services are no more required to be provided by a GSM PLMN:
• the dual Bearer Services “alternate speech/data” and “speech followed by data”
• the dedicated services for PAD and Packet access
• the single asynchronous and synchronous Bearer Services (BS 21..26, BS 31..34)
If a PLMN network still provides these services it has to fulfil the specification of GSM R98.
|
03.13
|
Discontinuous Reception (DRX) in the GSM System
|
TS
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.13/0313-800.zip
|
The present document provides a system wide view of the operation of discontinuous reception on the GSM system.
The support of DRX is mandatory in GSM PLMNs.
The detailed coding and procedural details are defined in the relevant Technical Specifications dealing with the specific interfaces that are involved, for instance GSM 08.08 and GSM 04.08. Reference is also made to the framing on the air interface which is defined in Technical Specification GSM 05.02.
The present document gives an overview of the implementation of discontinuous reception DRX within the GSM system, the actions required at MSC, BSS, and MS, the support of the facility via the air interface, and some operational aspects of the facility.
|
03.19
|
Subscriber Identity Module Application Programming Interface (SIM API) for Java Card
|
TS
|
8.5.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.19/0319-850.zip
|
The present document defines the stage two description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM.
This stage two describes the functional capabilities and the information flow for the SIM API implemented on the Java Card 2.1 API specification [6].
The present document includes information applicable to network operators, service providers and SIM, server and database manufacturers.
|
03.20
|
Security-related network functions
|
TS
|
8.6.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.20/0320-860.zip
|
This Technical Specification specifies the network functions needed to provide the security related service and functions specified in GSM 02.09.
This specification does not address the cryptological algorithms that are needed to provide different security related features. This topic is addressed in annex C. Wherever a cryptological algorithm or mechanism is needed, this is signalled with a reference to annex C. The references refers only to functionalities, and some algorithms may be identical or use common hardware.
|
03.22
|
Functions related to Mobile Station (MS) in idle mode and group receive mode
|
TS
|
8.7.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.22/0322-870.zip
|
The present document gives an overview of the tasks undertaken by a GSM Mobile Station (MS) when in idle mode, that is, switched on but not having a dedicated channel allocated, e.g. not making or receiving a call, or when in group receive mode, that is, receiving a group call or broadcast call but not having a dedicated connection. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The idle mode functions are also performed by a CTS MS as long as the CTS MS is in manual mode GSM only or in automatic mode under PLMN coverage.
NOTE: The term GSM MS is used for any type of MS supporting one, or combinations, of the frequency bands specified in GSM 05.05.
The present document outlines how the requirements of the GSM 02 series Technical Specifications (especially GSM 02.11) on idle mode operation shall be implemented. Further details are given in GSM 04.08 and GSM 05.08.
Clause 2 of the present document gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses. Clause 5 describes the cell change procedures for a MS in group receive mode.
1a 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] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
[2] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunications services supported by a GSM Public Land Mobile Network (PLMN)".
[3] GSM 02.02: "Digital cellular telecommunication system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)".
[4] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)".
[5] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services".
[6] GSM 02.06: "Digital cellular telecommunications system (Phase 2+); Types of Mobile Stations (MS)".
[7] GSM 02.07: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) features".
[8] GSM 02.09: "Digital cellular telecommunications system (Phase 2+); Security aspects".
[9] GSM 02.11: "Digital cellular telecommunications system (Phase 2+); Service accessibility".
[10] GSM 02.16: "Digital cellular telecommunications system (Phase 2+); International Mobile station Equipment Identities (IMEI)".
[11] GSM 02.17: "Digital cellular telecommunications system (Phase 2+); Subscriber identity modules Functional characteristics".
[12] GSM 02.24: "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)".
[13] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man‑Machine Interface (MMI) of the Mobile Station (MS)".
[14] GSM 02.40: "Digital cellular telecommunications system (Phase 2+); Procedures for call progress indications".
[15] GSM 02.41: "Digital cellular telecommunications system (Phase 2+); Operator determined barring".
[16] GSM 02.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services ‑ Stage 1".
[17] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services ‑ Stage 1".
[18] GSM 02.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1".
[19] GSM 02.84: "Digital cellular telecommunications system (Phase 2+); MultiParty (MPTY) supplementary services ‑ Stage 1".
[20] GSM 02.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services ‑ Stage 1".
[21] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services ‑ Stage 1".
[22] GSM 02.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services ‑ Stage 1".
[23] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
[24] GSM 05.02: "Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path".
[25] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
[26] GSM 02.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description Stage 1".
[27] GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Service description Stage 2".
[28] GSM 03.64: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Overall description of the GPRS Radio Interface; Stage 2".
[29] GSM 02.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); Service Description; Stage 1.
[30] GSM 03.56: "Digital cellular telecommunications system (Phase 2+); GSM Cordless Telephony System (CTS); CTS Architecture Description; Stage 2.
[31] 3GPP TS 23.122: " Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[32] 3GPP TS 24.008: " Mobile radio interface layer 3 specification; Core Network Protocols - Stage 3".
1b Definitions and abbreviations
Abbreviations used in the present document are listed in GSM 01.04.
Selected PLMN This is the PLMN that has been selected according to subclause 3.1, either manually or automatically.
Available PLMN This is a PLMN where the MS has found a cell that satisfies conditions (ii) and (iv) of subclause 3.2.1.
Home PLMN (HPLMN) See 3GPP TS 23.122.
Registered PLMN (RPLMN) This is the PLMN on which certain LR outcomes have occurred (see 3GPP TS 23.122).
Equivalent PLMN A PLMN contained in the stored list of equivalent PLMNs. These PLMNs are considered equivalent to the selected PLMN regarding PLMN selection, cell selection, cell re-selection and handover (see 3GPP TS 23.122).
Registration This is the process of camping on a cell of the PLMN and doing any necessary LRs.
Camped on a cell The MS (ME if there is no SIM) has completed the cell selection/reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN may not be aware of the existence of the MS (ME) within the chosen cell.
Current serving cell This is the cell on which the MS is camped.
Suitable Cell This is a cell on which an MS may camp. It must satisfy criteria defined in subclause 3.2.1. For an MS in group receive mode, the suitable cell is determined by the criteria defined in subclause 5.2.3.
Acceptable Cell This is a cell that the MS may camp on to make emergency calls. It must satisfy criteria defined in sub clause 3.2.2.
Group call A communication in which several MSs can receive, but at most one may be allowed to transmit on a radio channel. Examples of group calls are those established for the voice group call service (VGCS, see GSM 03.68).
Broadcast call A communication in which several MSs can receive, but only the originator of the call is allowed to transmit on the radio channel. Examples of the broadcast call are those established for the voice broadcast service (VBS, see GSM 03.69).
Group receive mode State of the MS when it is engaged in a group or broadcast call as a listener.
GPRS MS An MS capable of GPRS services is a GPRS MS.
CTS MS An MS capable of CTS services is a CTS MS.
Location Registration (LR) An MS which is IMSI attached to non-GPRS services only performs location registration by the Location Updating procedure. A GPRS MS which is IMSI attached to GPRS services or to GPRS and non-GPRS services performs location registration by the Routing Area Update procedure only when in a network of network operation mode I. Both procedures are performed independently by the GPRS MS when it is IMSI attached to GPRS and non-GPRS services in a network of network operation mode II or III (see GSM 03.60).
Localised Service Area (LSA) A localised service area consists of a cell or a number of cells. The cells constituting a LSA may not necessarily provide contiguous coverage.
SoLSA exclusive access Cells on which normal camping is allowed only for MS with Localised Service Area (LSA) subscription.
Registration Area A registration area is an area in which mobile stations may roam without a need to perform location registration. The registration area corresponds to location area (LA) for performing location updating procedure and it corresponds to routing area for performing the routing area update procedure.
The PLMN to which a cell belongs (PLMN identity) is given in the system information transmitted on the BCCH (MCC + MNC part of LAI).
|
03.26
|
Multiband operation of GSM/DCS 1800 by a single operator
|
TR
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.26/0326-800.zip
|
The purpose of the present document is to describe the functionality of a Multiband GSM/DCS Network operated by a single operator and the Multiband GSM/DCS Mobile Station (MS). It also describes the necessary amendments to the GSM/DCS phase 2 specifications for the technical realization of the function.
The resulting Amendment Requests (AR) and Change Requests (CR) necessary for Multiband Operation are listed in annex A.
|
03.30
|
Radio Network Planning Aspects
|
TR
|
8.4.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.30/0330-840.zip
|
This 3GPP Technical Report (3GPP TR) is a descriptive recommendation to be helpful in cell planning.
|
03.33
|
3G Security; Lawful Interception; Stage 2
|
TS
|
8.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.33/0333-810.zip
|
The present document gives the stage 2 description of Lawful Interception within a PLMN for circuit switched systems and GPRS. It does not address the interface between the PLMN and the LEA lawful intercepted product and related information collection functions. This is outside the scope of the GSM standard.
The structure of the present document is as follows:
- clause 4 covers the architecture of the interception system;
- clause 5 describes how interception is activated, deactivated and interrogated within the interception system;
- clause 6 describes how the system is provisioned, defines events at which interception takes place and what kind of information is generated at each event;
- clause 7 provides brief descriptions of various intercept cases;
- clause 8 reviews security requirements for access to the interception system;
- annex A provides information flows to illustrate when intercepted traffic and related data is generated;
- annex B describes an interception system for GPRS. The annex is subdivided into 5 sections that are identical in structure to clauses 4 through 8, but applicable to a GPRS clause rather than a GSM circuit switched system.
|
03.45
|
Technical Realization of Facsimile Group 3 Service - transparent
|
TS
|
8.0.1
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.45/0345-801.zip
|
The present document deals with the procedures allowing the technical realization of the Group 3 facsimile Service within the GSM PLMN using transparent Network support, according to the definition of Teleservice 61 and 62 specified in the GSM 02.03 [2].
|
03.46
|
Technical Realization of Facsimile Group 3 Service - non transparent
|
TS
|
8.0.1
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.46/0346-801.zip
|
The present document deals with the procedures allowing the technical realization of the real time end‑to‑end facsimile group 3 service within the GSM PLMN using non‑transparent network support according to the definition of the Teleservices 61 and 62 specified in GSM 02.03. Within the present document particular attention is given to Teleservice "Alternate speech/facsimile group 3" (Teleservice 61). However, the definitions apply also to Teleservice "Automatic facsimile group 3" (Teleservice 62) with the exception of all actions concerned with the speech phase. Consequently, in the following descriptions the term "Teleservice" denotes both Teleservice 61 and Teleservice 62 as appropriate.
NOTE: Some facilities associated with alternate speech/ facsimile group 3 may not be available with version 1 of MAP. In particular, the in‑call modification procedure following an inter MSC handover is not supported by this version. This imposes the limitation that for all calls it will not be possible to change between speech and facsimile following an inter MSC handover.
|
03.48
|
Security mechanisms for SIM application toolkit; Stage 2
|
TS
|
8.9.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.48/0348-890.zip
|
The present document specifies the structure of the Secured Packets in a general format and in implementations using Short Message Service Point to Point (SMS-PP) and Short Message Service Cell Broadcast (SMS-CB).
Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in TS 11.11 [5] and allows remote management of files on the Subscriber Identity Module (SIM) in conjunction with SMS and the SIM Data Download feature of TS 11.14 [6].
For SIM cards based on TS 03.19 [15], the set of commands used in the remote applet management is defined in the present document. This is based on the Open Platform card management specification [14]. For SIM cards based on other technologies, other loading mechanisms may be used.
The present document is applicable to the exchange of secured packets between an entity in a GSM PLMN and an entity in the SIM.
Secured Packets contain application messages to which certain mechanisms according to TS 02.48 [2] have been applied. Application messages are commands or data exchanged between an application resident in or behind the GSM PLMN and on the SIM. The Sending/Receiving Entity in the GSM PLMN and the SIM are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
03.50
|
Transmission Planning Aspects of the Speech Service in the GSM Public Land Mobile Network (PLMN) System
|
TS
|
8.1.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.50/0350-811.zip
|
The present document describes the transmission planning aspects pertaining to the speech service in the GSM PLMN system. Due to technical and economic factors, there cannot be full compliance with the general characteristics of international telephone connections and circuits recommended by the ITU‑T.
The present document gives guidance as to the precautions, measures and minimum requirements needed for successful interworking of the PLMN with the national and international PSTN. The present document identifies a number of routeing and network configurations. The objective is to reach a quality as close as possible to ITU‑T standards in order to safeguard the performance seen by PSTN customers.
|
03.52
|
Lower layers of the GSM Cordless Telephony System (CTS) radio interface; Stage 2
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.52/0352-801.zip
|
The present document gives an overall description of the lower layers of the radio interface for GSM based Cordless Telephony Systems (GSM-CTS).
The GSM-CTS system is intended to provide a cordless connection between the fixed network and GSM-based CTS Mobile Stations (CTS-MS) via a private CTS Fixed Part (CTS-FP).
Stage 1 is an overall description, from the service subscribers and user's standpoint, that view the network as a single entity which provides service to the user. GSM 02.56 contains the CTS Stage 1 service description.
GSM 03.56 is a Stage 2 document that describes the system architecture of the GSM Cordless Telephone Systems (GSM-CTS), i.e. the system elements, the system interfaces and the functional capabilities.
|
03.53
|
Tandem Free Operation (TFO); Service description; Stage 2
|
TS
|
8.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.53/0353-800.zip
|
The present document defines the stage 2 service description for Tandem Free Operation (TFO) in GSM. Tandem Free Operation applies only to speech calls.
Note: the TFO principles are built so that they could be used as well by other systems other than GSM.
In analogy with CCITT Recommendations I.130 [2] and with reference to CCITT Recommendations VI.1 Q.65 (Stage 2 of the method for the characterisation of services supported by an ISDN), the second stage of the following three-level structure is derived from a stage 1 service description.
Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
Stage 3 defines the signalling system protocols and switching functions needed to implement the service described in stage 2.
|
03.55
|
Dual Transfer Mode (DTM); Stage 2
|
TS
|
8.4.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.55/0355-840.zip
|
The present document is a description of the practical implementation of GSM-GPRS class A mobiles and a basis for discussion on the changes and additions to the current specifications.
This work is part of the Release 99 Work Item "BSS co-ordination of Radio Resource allocation for class A GPRS services - GSM Radio Access (R99)" for which M Mouly of Nortel Networks is rapporteur. This work item was supported by Nortel, Motorola, Vodafone and Lucent.
In the following, GPRS refers to both EGPRS and GPRS unless explicitly stated otherwise.
|
03.58
|
Characterisation, test methods and quality assessment for handsfree Mobile Stations (MSs)
|
TR
|
8.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.58/0358-800.zip
|
The present document gives some guidelines to implement test methods and to evaluate the transmission quality of handsfree Mobile Stations (MSs). The normative characteristics and test methods for handsfree Mobile Stations (MSs are defined in GSM 03.50). The present document gives additional data.
It includes summaries of texts or contributions presented and discussed during the meetings of ad hoc group SMG2/03.50 on environmental conditions, speech processing and quality assessment for handsfree Mobile Station.
The items covered by this report are mainly
- Environmental conditions for handsfree Mobile Stations.
- Speech processing techniques and consequences on delay.
- Speech quality assessment for handsfree implementing acoustic echo cancellation and noise reduction.
|
03.64
|
General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2
|
TS
|
8.12.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.64/0364-8c0.zip
|
The present document provides the overall description for lower-layer functions of the General Packet Radio Service (GPRS and EGPRS)) radio interface (Um). ). Within this TS the term GPRS refers to GPRS and EGPRS unless explicitly stated otherwise.
The overall description provides the following information:
- The services offered to higher-layer functions,
- The distribution of required functions into functional groups,
- A definition of the capabilities of each functional group,
- Service primitives for each functional group, including a description of what services and information flows are to be provided, and
- A model of operation for information flows within and between the functions.
The present document is applicable to the following GPRS Um functional layers:
- Radio Link Control functions,
- Medium Access Control functions, and
- Physical Link Control functions.
The present document describes the information transfer and control functions to be used across the radio (Um) interface for communication between the MS and the Network, see Figure 1.
3GPP TS 03.60 [3] describes the overall GPRS logical architecture and the GPRS functional layers above the Radio Link Control and Medium Access Control layer.
3GPP TS 04.07 [5] contains a description in general terms of the structured functions and procedures of this protocol and the relationship of this protocol with other layers and entities.
3GPP TS 04.08 [6] contains the definition of GPRS RLC/MAC procedures when operating on the Common Control Channel (CCCH).
3GPP TS 04.60 [7] contains the definition of RLC/MAC functions when operating on a Packet Data Channel (PDCH).
3GPP TS 04.64 [8] contains functional procedures for the Logical Link Control (LLC) layer above the RLC/MAC.
3GPP TS 05 series defines the Physical Link layer and Physical RF layer.
Figure 1: Scope of GPRS Logical Radio Interface Architecture
|
03.68
|
Voice Group Call Service (VGCS); Stage 2
|
TS
|
8.6.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.68/0368-860.zip
|
The present document specifies the stage two description of the Voice Group Call Service (VGCS) which allows speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple subscribers involved in the group call per cell.
|
03.69
|
Voice Broadcast Service (VBS); Stage 2
|
TS
|
8.5.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.69/0369-850.zip
|
The present document specifies the stage 2 description of the Voice Broadcast Service (VBS) which allows the distribution of speech (or other signals which can be transmitted via the speech codec), generated by a service subscriber, into a predefined geographical area to all or a group of service subscribers located in this area.
|
03.71
|
Location Services (LCS); Functional description; Stage 2
|
TS
|
8.9.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.71/0371-890.zip
|
The present document defines the stage-2 service description for the LoCation Services (LCS) feature on GSM, which provides the mechanisms to support mobile location services of operators, which are not covered by standardized GSM services. CCITT I.130 [4] describes a three-stage method for characterization of telecommunication services, and CCITT Q.65 [5]defines stage 2 of the method.
The LCS feature is a network feature and not a supplementary service. This version of the stage 2 service description covers aspects of LCS e.g., the functional model, architecture, positioning methods, message flows etc.
|
03.73
|
Support of Localised Service Area (SoLSA); Stage 2
|
TS
|
8.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.73/0373-800.zip
|
The present document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43.
|
04.01
|
Mobile Station - Base Station System (MS - BSS) Interface General Aspects and Principles
|
TS
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.01/0401-800.zip
|
The present document describes the general aspects and principles relating to the Technical Specifications for the GSM MS-BSS interface.
|
02.95
|
Support of Private Numbering Plan (SPNP); Service description; Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.95/0295-800.zip
|
The present document specifies the stage 1 description of Support of Private Numbering Plan (SPNP), which enables a subscriber to use a Private Numbering Plan (PNP) for communication across one or more networks with mobile and fixed users. The subscriber may belong to one or more (up to 9 maximum) Private Numbering Plans. The subscriber may also, subject to subscription, have access to the Public Numbering Plan. The structure and content of each PNP are defined by a PNP Manager, although these are out of the scope of the present document.
The service is described from the service subscriber's and user's points of view; in particular:
- the procedures for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other GSM supplementary services.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Global System for Mobile communications (GSM) specifications.
The charging principles applied to Support of Private Numbering Plan (SPNP) are outside of the scope of the present document.
Any interactions with other services and/or networks not dealt with in subclause 4.1 and clauses11 to 13 are outside the scope of the present document.
|
04.03
|
Mobile Station - Base Station System (MS - BSS) Interface Channel Structures and Access Capabilities
|
TS
|
8.0.2
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.03/0403-802.zip
|
The present document defines limited sets of channel types, access capabilities and channel configurations at reference point Um (radio interface).
|
04.04
|
Layer 1 - General Requirements
|
TS
|
8.1.2
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.04/0404-812.zip
|
The present document defines the service offered by the physical layer (3GPP TS 05‑series of Technical Specifications) of the MS‑BS interface (3GPP TS 05‑ and 04‑series of Technical Specifications). Its main objective is to be a guidance for the interface between the 3GPP Technical Specifications in the 05‑series and the 04‑series. It also specifies the format of signalling channels and the order of bit transmission.
As far as possible, the present document makes use of the layering principles of the Reference Model for Open System Interconnection (OSI) as contained in ITU-T Recommendations X.200 and X.210.
|
04.05
|
Data Link (DL) Layer General Aspects
|
TS
|
8.0.2
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.05/0405-802.zip
|
The present document describes in general terms the Link Access Procedures on the Dm channel, LAPDm. The application of this protocol to other channel types is for further study. Details are provided in 3GPP TS 04.06.
The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface (MS to network interface) using the Dm channel.
NOTE 1: The term Dm channel is used for convenience to designate the collection of all the various signalling channels required in the GSM system. See also 3GPP TS 04.03.
The definition of LAPDm is based on the principles and terminology of:
‑ CCITT Recommendations X.200 and X.210: the reference model for Open Systems Interconnection (OSI);
‑ CCITT Recommendations Q.920 and Q.921: the specification of LAPD for the user‑network interface in ISDN;
‑ CCITT Recommendation X.25 LAPB: user‑network interface for packet mode terminals; and
‑ ISO 3309 and ISO 4335: High‑level Data Link Control (HDLC) standards for frame structure and elements of procedures.
LAPDm is a protocol that operates at the data link layer of the OSI architecture. The relationship between the data link layer and other protocol layers is defined below.
NOTE 2: The interface between the mobile station and external terminal equipment/terminal adapters is defined in the Technical Specifications of the 3GPP TS 07‑series.
NOTE 3: The physical layer on the radio interface is defined in 3GPP TS 04.04 and layer 3 is defined in 3GPP TS 04.07, 04.08, 04.10 and 04.11. Reference should be made to these Technical Specifications for the complete definitions of the protocols and procedures across the GSM PLMN radio interface.
NOTE 4: The term "data link layer" is used in the main text of the present document. However, mainly in figures and tables, the terms "layer 2" and "L2" are used abbreviations. Furthermore, in accordance with 3GPP TS 04.07 and 04.08 the term "layer 3" is used to indicate the layer above the data link layer.
LAPDm is independent of the transmission bit rate. It requires physical channels with characteristics as defined in 3GPP TS 04.03.
Section 2 below describes basic concepts used in the present document and 3GPP TS 04.06.
Section 3 gives an overview description of LAPDm functions and procedures.
Section 4 summarizes the services that the data link layer provides to layer 3 and the services that the data link layer requires from the physical layer.
Section 5 provides an overview of the data link layer structure.
|
04.06
|
Mobile Station - Base Stations System (MS - BSS) Interface Data Link (DL) Layer Specification
|
TS
|
8.4.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.06/0406-840.zip
|
The present document defines a data link layer protocol to be used for signalling, and possibly also for other applications, on the MS‑BS interface.
|
04.08
|
Mobile radio interface layer 3 specification
|
TS
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.08/0408-800.zip
|
This EN specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for Call Control (CC), Mobility Management (MM), Radio Resource (RR) management and Session Management (SM). The detailed descriptions of the protocols and the related procedures are described in GSM 04.18, TS 23.108 and TS 24.008.
When the notations for "further study" or "FS" or "FFS" are present in this ETS they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in GSM 04.03.
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.
|
04.12
|
Short Message Service Cell Broadcast (SMSCB) Support on the Mobile Radio Interface
|
TS
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.12/0412-800.zip
| |
04.13
|
Performance Requirements on Mobile Radio Interface
|
TS
|
8.0.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.13/0413-801.zip
|
The present document specifies measurable performance requirements for signalling aspects of Mobile Stations (MS)s. To allow implementation flexibility it has been chosen to specify requirements on the whole Mobile Station rather than to specify requirements on each "OSI layer". As a consequence the performance requirements do not fit conveniently in specifications such as GSM 04.08 [4] (layer 3 only) or GSM 04.06 [3] (layer 2 only).
The main aim of the present document is to provide the justification for testing of requirements that are not included in other GSM specifications. Where specific requirements are included in other GSM specifications they are not duplicated here.
MSs have to perform a wide variety of functions. As a consequence most performance measurements have to be made under a set of defined conditions: where necessary, these are included in the present document.
Where necessary certain assumptions are made about the interaction times between the mobile equipment and the SIM. If the (test) SIM does not respond within the assumed time then appropriate allowances shall be made.
Additionally, it is intended that the present document should contain sufficient requirements to enable some undefined network timers in GSM 04.08 [4] to be calculated.
|
04.14
|
Individual equipment type requirements and interworking; Special conformance testing functions
|
TS
|
8.6.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.14/0414-860.zip
|
The present document specifies for Mobile Stations (MS), for the digital cellular communications system and Personal Communication Systems (PCS) operating in the 900 MHz and 1800 MHz band (GSM900 and DCS1800), standardized by ETSI SMG, those ME functions which are required for conformance testing purposes only. However, except for the Electrical Man Machine Interface (EMMI) and the Multi-slot TCH Loops, they are required for every mobile station.
For conformance tests, functions are activated via the radio interface, test SIM or dedicated pins. These functions must be capable of being activated when a test SIM is present but must not function with any other (e.g. network) SIM present except where otherwise stated within the present document. In this state, the MS must be able to perform all functions specified in the present document; in addition however, the special conformance testing functions must be operational.
The special conformance testing functions of the ME are enabled by use of a dedicated Subscriber Identity Module (test SIM, see 3GPP TS 11.10-1 Annex 4). SIM, in general, is described in 3GPP TS 11.11. The ME recognizes the test SIM by the Administrative Data Field.
The present document applies to the public land mobile radio service in the GSM900 and DCS1800 systems, using constant envelope modulation and operating on radio frequencies in the 900 and 1800 MHz bands respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle.
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 TS, nor is it created to provide full understanding of (or parts of) the GSM900 and DCS1800 systems.
The present document applies to the unit which includes the hardware to establish a connection across the radio interface.
|
04.18
|
Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol
|
TS
|
8.27.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.18/0418-8r0.zip
|
The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 04.02) for Radio Resource (RR) management.
Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts.
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 control channels are described in 3GPP TS 04.03.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007.
|
04.31
|
Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP)
|
TS
|
8.18.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.31/0431-8i0.zip
|
The present document contains the definition of the Radio Resource LCS Protocol (RRLP) to be used between the Mobile Station (MS) and the Serving Mobile Location Centre (SMLC).
Clause 2 defines the functionality of the protocol. Clause 3 describes the message structure, and clause 4 the structure of components. Clause 5 contains the ASN.1 description of the components.
|
04.21
|
Rate Adaption on the Mobile Station - Base Station System (MS-BSS) Interface
|
TS
|
8.3.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.21/0421-830.zip
|
The present document defines the rate adaptation functions to be used in GSM PLMN Mobile Stations (MS)s for adapting terminal interface data rates to the Mobile Station - Base Station System (MS-BSS) interface data rates in accordance with 3GPP TS 03.10 [3].
The provision of these functions will depend on the services a particular station is designed to support.
NOTE: This ETS should be considered together with 3GPP TS 08.20 [9] (Rate Adaptation on the BSS-MSC Interface) to give a complete description of PLMN rate adaptation.
|
04.35
|
Location Services (LCS); Broadcast network assistance for Enhanced Observed Time Difference (E-OTD) and Global Positioning System (GPS) positioning methods
|
TS
|
8.4.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.35/0435-841.zip
|
The present document contains the content of messages necessary for support of MS Based location service operation on the mobile radio interface layer 3.
|
04.56
|
GSM Cordless Telephony System (CTS), (Phase 1) CTS Radio Interface Layer 3 Specification
|
TS
|
8.0.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.56/0456-801.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.
|
04.57
|
GSM Cordless Telephony System (CTS), (Phase 1) CTS CTS supervising system Layer 3 Specification
|
TS
|
8.0.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.57/0457-801.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.
|
04.60
|
General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC) protocol
|
TS
|
8.27.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.60/0460-8r0.zip
|
The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 04.02) for the General Packet Radio Service (GPRS) Medium Access Control /Radio Link Control (MAC/RLC) layer.
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 present document is applicable to the following GPRS Um functional layers:
- Radio Link Control functions,
- Medium Access Control functions, and
- Physical Link Control functions.
The procedures described in the present document are for the RLC/MAC functions of the GPRS radio interface (Um) when operating on a Packet Data Channel (PDCH).
The present document provides the overall description for RLC/MAC layer functions of the general Packet Radio Service (GPRS and EGPRS) radio interface Um. Within this TS the term GPRS refers to GPRS and EGPRS unless explicitly stated otherwise.
3GPP TS 03.64 contains an overview of the GPRS radio interface (Um).
3GPP TS 04.03 and 3GPP TS 04.04 contains the definition of the control channels used in the present document.
3GPP TS 04.07 contains a description in general terms of the structured functions and procedures of this protocol and the relationship of this protocol with other layers and entities.
3GPP TS 04.08 contains the definition of GPRS RLC/MAC procedures when operating on the Common Control Channel (CCCH).
3GPP TS 04.64 contains functional procedures for the Logical Link Control (LLC) layer.
Application to interface structure
The RLC/MAC procedures apply to the interface structures defined in 3GPP TS 04.03. They use the functions and services provided by layer 1 defined in 3GPP TS 04.04. 3GPP TS 04.07 gives the general description of layer 3 including procedures, messages format and error handling.
Test procedures
Test procedures of the GSM radio interface signalling are described in 3GPP TS 11.10 and 3GPP TS 11.2x series.
Use of logical control channels
The logical control channels are defined in 3GPP TS 05.02. Three similar sets of logical channels are defined. The first set consists of the logical channels:
- Broadcast Control Channel (BCCH): downlink only, used to broadcast Cell specific information;
- Paging Channel (PCH): downlink only, used to send page requests to Mobile Stations (MSs);
- Random Access Channel (RACH): uplink only, used to request GPRS resources or a Dedicated Control Channel;
- Access Grant Channel (AGCH): downlink only, used to allocate GPRS resources or a Dedicated Control Channel;
- The second set consists of the logical channels:
- Packet Broadcast Control Channel (PBCCH): downlink only, used to broadcast Cell specific information;
- Packet Paging Channel (PPCH): downlink only, used to send page requests to Mobile Stations (MSs);
- Packet Random Access Channel (PRACH): uplink only, used to request GPRS resources;
- Packet Access Grant Channel (PAGCH): downlink only, used to allocate GPRS resources;
- Packet Associated Control Channel (PACCH): bi-directional, associated with a Temporary Block Flow (TBF);
- Packet Timing advance control channel uplink (PTCCH/U): used to transmit random access bursts to allow estimation of the timing advance for one MS in transfer state;
• Packet Timing advance control channel downlink (PTCCH/D): used to transmit timing advance updates for several MS. One PTCCH/D is paired with several PTCCH/U's.
- The third set consists of the logical channels (COMPACT control channels):
- COMPACT Packet Broadcast Control Channel (CPBCCH): downlink only, used to broadcast Cell specific information; This channel is used to broadcast the same pieces of information as the PBCCH, but has a different physical structure (see 3GPP TS 05.02); In the remainder of this specification PBCCH shall be interpreted as PBCCH and CPBCCH unless specifically mentioned to be otherwise;
- COMPACT Packet Paging Channel (CPPCH): downlink only, used to send page requests to Mobile Stations (MSs) on a COMPACT control channel; In the remainder of this specification PPCH shall be interpreted as PPCH and CPPCH unless specifically mentioned to be otherwise;
- COMPACT Packet Random Access Channel (CPRACH): uplink only, used to request GPRS resources on a COMPACT control channel; In the remainder of this specification PRACH shall be interpreted as PRACH and CPRACH unless specifically mentioned to be otherwise;
- COMPACT Packet Access Grant Channel (CPAGCH): downlink only, used to allocate GPRS resources on a COMPACT control channel; In the remainder of this specification PAGCH shall be interpreted as PAGCH and CPAGCH unless specifically mentioned to be otherwise;
- Packet Associated Control Channel (PACCH): see above;
- Packet Timing advance control channel uplink (PTCCH/U): see above;
- Packet Timing advance control channel downlink (PTCCH/D): see above.
|
04.64
|
General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification
|
TS
|
8.7.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.64/0464-870.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 03.60 [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.
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.
|
04.65
|
General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)
|
TS
|
8.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.65/0465-820.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 04.65 is applicable to GPRS MS and SGSN.
|
04.68
|
Group Call Control (GCC) Protocol
|
TS
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.68/0468-810.zip
|
The present document specifies the Group Call Control (GCC) protocol used by the Voice Group Call Service (VGCS) on the radio interface.
|
04.69
|
Broadcast Call Control (BCC) protocol
|
TS
|
8.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.69/0469-810.zip
|
The present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface.
|
04.71
|
Location Services (LCS); Mobile radio interface layer 3 specification
|
TS
|
8.4.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.71/0471-840.zip
|
The present document contains the coding of information necessary for support of location service operation on the mobile radio interface layer 3.
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 between the LMU and MSC. Clause 6 gives the general 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.
|
05.01
|
Physical layer on the radio path; General description
|
TS
|
8.9.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.01/0501-890.zip
|
The present document is an introduction to the 05 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.
|
05.02
|
Multiplexing and Multiple Access on the Radio Path
|
TS
|
8.11.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.02/0502-8b0.zip
|
The present document defines the physical channels of the radio sub‑system required to support the logical channels. It includes a description of the logical channels and the definition of frequency hopping, TDMA frames, timeslots and bursts.
|
05.03
|
Channel coding
|
TS
|
8.9.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.03/0503-890.zip
|
A reference configuration of the transmission chain is shown in GSM 05.01 [4]. 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 GSM 05.02 [5], a summary is in annex A.
|
05.04
|
Modulation
|
TS
|
8.4.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.04/0504-840.zip
|
The modulator receives the bits from the encryption unit, see GSM 05.01 [1], 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 GSM 05.05 [4].
1a 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] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
[2] GSM 05.01: "Digital cellular telecommunication system (Phase 2+); Physical layer on the radio path General description".
[3] GSM 05.02: "Digital cellular telecommunication system (Phase 2+); Multiplexing and multiple access on the radio path".
[4] GSM 05.05: "Digital cellular telecommunication system (Phase 2+); Radio transmission and reception".
1b Abbreviations
Abbreviations used in this specification are listed in GSM 01.04 [1]
|
05.05
|
Radio Transmission and Reception
|
TS
|
8.20.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.05/0505-8k0.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.
This EN 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 11.10 and 3GPP TS 11.21.
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 relaxation's are introduced for GSM 400 MSs, GSM 900 MSs and GSM 850 MSs which pertain to power class 4 or 5 (see subclause 4.1.1). In the present document these Mobile Stations are referred to as "small MS".
MSs may operate on more than one of the frequency bands specified in clause 2. These MSs, defined in 3GPP TS 02.06, 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 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.
This 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.
|
05.08
|
Radio subsystem link control
|
TS
|
8.23.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.08/0508-8n0.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 band.
|
05.09
|
Link adaptation
|
TS
|
8.6.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.09/0509-860.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.
|
05.10
|
Radio subsystem synchronization
|
TS
|
8.12.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.10/0510-8c0.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.
|
05.15
|
Release independent Downlink Advanced Receiver Performance (DARP); Implementation guidelines
|
TS
|
8.1.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.15/0515-810.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 is contained in the Release 6 specifications. In order to implement an MS conforming to Release 99 but supporting DARP, it is necessary for the MS to additionally conform to some parts of the Release 6 specifications, such as the radio frequency requirements for DARP and some signalling extensions relating to the MS Classmark and radio access capabilities.
|
05.22
|
Radio link management in hierarchical networks
|
TR
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.22/0522-800.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.
|
05.50
|
Background for RF Requirements
|
TR
|
8.2.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.50/0550-820.zip
|
The present document gives background information on how the RF requirements of GSM 400, GSM 900 and DCS 1800 systems have been derived.
|
05.56
|
GSM Cordless Telephony System (CTS), Phase 1; CTS-Fixed Part (FP) radio subsystem
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/05_series/05.56/0556-801.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).
|
06.01
|
Full Rate Speech Processing Functions
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.01/0601-801.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.
|
06.02
|
Half Rate Speech Processing Functions
|
TS
|
8.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.02/0602-800.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.
|
06.06
|
Half Rate Speech: ANSI-C Code for GSM Half Rate Speech Codec
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.06/0606-801.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]).
|
06.07
|
Half Rate Speech: Test Sequence for GSM Half Rate Speech Codec
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.07/0607-801.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]).
|
06.08
|
Half Rate Speech; Performance Characterization of the GSM Half Rate speech codec
|
TR
|
8.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.08/0608-800.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.
|
06.10
|
Full Rate Speech Transcoding
|
TS
|
8.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.10/0610-820.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.
|
06.11
|
Substitution and Muting of Lost Frames for Full Rate Speech Channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.11/0611-801.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).
|
06.12
|
Comfort Noise Aspects for Full Rate Speech Traffic Channels
|
TS
|
8.1.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.12/0612-810.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.
|
06.20
|
Half Rate Speech Transcoding
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.20/0620-801.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.
|
06.21
|
Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.21/0621-801.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.
|
06.22
|
Comfort Noise Aspects for Half Rate Speech Traffic Channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.22/0622-801.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.
|
06.31
|
Discontinuous Transmission (DTX) for Full Rate Speech Traffic Channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.31/0631-801.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.
|
06.32
|
Voice Activity Detection (VAD)
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.32/0632-801.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.
|
06.41
|
Discontinuous Transmission (DTX) for Half Rate Speech Traffic Channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.41/0641-801.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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.