id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
08.31 | Location Services (LCS): Serving Mobile Location Centre - Serving Mobile Location Centre (SMLC - SMLC); SMLCPP specification | TS | 8.1.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.31/0831-811.zip | The present document contains the definition of the SMLCPP protocol to be used between two Serving Mobile Location Centres (SMLC).
The LCS architecture is described in 03.71. The following aspects of it are relevant to the issue:
- each SMLC controls a number of LMUs, and a given LMU is under the direct control of a single SMLC;
- there is a direct communication path, independent of SMLCPP, between a LMU and the SMLC that controls it;
- deciphering keys are controlled by one SMLC in the location area and sent to other SMLCs in the same location area.
SMLCPP runs between two SMLC functions in the same PLMN. Transport is outside the scope of the present document. It assumes a transport service between these functions, as provided by BSSAP-LE. The present document assumes that the underlying transport (e.g., as described by BSSMAP-LE specifications) provides for transport and routing for any two pairs of SMLCs which need to run SMLCPP exchanges, whatever the implementation options for each of the SMLCs (BSS based or NSS based).
The main functions of SMLCPP are described in [5]. The key aspects are:
a) allowing an SMLC to ask for and obtain measurements on specific MSs performed by LMUs not under its direct control (e.g., for TOA);
b) allowing an SMLC to ask for and obtain information about Radio Interface Timing (RIT), as known from measurements done by LMUs not under its direct control;
c) allowing an SMLC, that controls deciphering keys in the location area, to sent them to other SMLCs in the same location area. |
08.51 | Base Station Controller - Base Tranceiver Station (BSC-BTS) Interface General Aspects | TS | 8.0.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.51/0851-801.zip | The present document is an introduction to the 08.5x - 08.6x series of 3GPP Technical Specifications and deals with the definition of the base station controller (BSC) to base transceiver station (BTS) interface defined inside the base station system (BSS) for the GSM system. These Technical Specifications define the basic interface with some identified options requiring further elaboration. The BSC-BTS interface is mandatory within GSM only if the BSC and the BTS are not colocated. |
08.52 | Base Station Controller - Base Tranceiver Station (BSC-BTS) Interface - Interface Principles | TS | 8.0.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.52/0852-801.zip | The use and general aspects of the A-bis interface are given in Technical Specification 3GPP TS 08.51.
The present document gives the principle basis for the rest of the specifications specifying the interface between the Base Station Controller, BSC, and the Base Transceiver Station, BTS, with its transceivers, TRX. These components together form the Base Station System, BSS. (The interface between MSC and the BSS is specified in Technical Specifications 3GPP TS 08.01 - 08.20).
The intention with this interface is to get a unified way of connecting remotely located BTSs/TRXs to a BSC allowing for the interconnection of BSCs and BTSs/TRXs from different manufacturers.
In order to keep the BTS as simple as possible, BTS contains only those functions which have to recide close to the radio interface. |
08.54 | BSC-BTS Layer 1; Structure of Physical Circuits | TS | 8.0.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.54/0854-801.zip | The use and general aspects of the A-bis interface are given in Technical Specification 3GPP TS 08.51.
The present document defines the structure of the physical layer (layer 1) of the BSC - BTS/TRX interface for supporting traffic channels and control channels. Use of the physical layer for supporting link protocol is covered in Technical Specification 3GPP TS 08.56.
The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium.
For the present document only digital transmission will be considered, the use of analogue transmission is a national concern. |
08.56 | BSC-BTS Layer 2; Specification | TS | 8.0.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.56/0856-801.zip | The present document specifies the link layer used for signalling on the A-bis interface between BSC and BTS. The use and general aspects of the A-bis interface are described in 3GPP TS 08.51 and the interface aspects in 3GPP TS 08.52.
The Link Access Procedure on the D-channel (LAPD) specification used on the A-bis interface in the GSM PLMN is a subset of the ETS 300 125 which in turn has less options than the CCITT Recommendation Q.921.
This description contains first the protocol definitions and second the services provided by the layer 2 to the layer 3. |
08.58 | Base Station Controler - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification | TS | 8.6.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.58/0858-860.zip | The use and general aspects of the Base Station Controller (BSC) to Base Station Transceiver (BTS) interface (the A-bis interface) are given in 3GPP TS 08.51.
This Technical Specification (TS) specifies the general structure of layer 3 and traffic management procedures and messages used on the A-bis interface to support signalling procedures as defined in 3GPP TS 04.08. Support for Location Services (LCS) related signalling, as defined in 3GPP TS 03.71, is also included. 3GPP TS 03.71 identifies new A-bis signalling to support BTS-embedded Type B LMUs as well as standalone, Type B LMUs. The standalone Type B LMU supports the layer 1 and 2 signalling for the A-bis as well as the Location Service message defined in this specification.
Network management procedures and messages for the A-bis interface are defined in 3GPP TS 08.59.
The functional split between BSC and BTS is defined in 3GPP TS 08.52. The procedures and messages required to support this split are defined in detail in this TS. |
08.60 | In-band control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels | TS | 8.2.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.60/0860-821.zip | When 64 kbit/s traffic channels are used on the Abis interface, the speech shall be coded according to ITU-T Recommendation G.711 and the data rate adaptation shall be as specified in GSM 04.21 and GSM 08.20.
In the case where 16 kbit/s traffic channels are used for full rate speech, enhanced full rate speech, Adaptive Multi-Rate speech or full rate data service, then the present document shall apply for frame structure and for control of remote transcoders and additional rate adaptors.
For Adaptive Multi-Rate speech the present document specifies the 16 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). The specification for 8 kBit/s submultiplexing is given in GSM 08.61, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS).
The use and general aspects of the Abis interface are given in GSM 08.51.
NOTE: The present document should be considered together with the GSM 06 series of specifications, GSM 04.21 (Rate Adaptation on the MS-BSS Interface) and GSM 08.20 (Rate Adaptation on the BS/MSC Interface). |
08.61 | In-band control of remote transcoders and rate adaptors for half rate traffic channels | TS | 8.1.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.61/0861-810.zip | The present document describes the protocol between the Base Transceiver Station (BTS) and the remote Transcoder/Rate Adaption Unit (TRAU) for speech and data on half rate traffic channel (TCH/H).
For Half Rate speech and half rate data the protocol is specified for 8 kbit/s and 16 kbit/s submultiplexing scheme.
For Adaptive Multi-Rate speech the present document specifies the 8 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). The specification for 16 kBit/s submultiplexing is given in Rec GSM 08.60, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS).
The present document should be considered together with the GSM 06 series, GSM 04.21 (Rate Adaption on the MS‑BSS Interface) and GSM 08.20 (Rate Adaption on the BTS/MSC Interface). |
08.62 | Inband Tandem Free Operation (TFO) of Speech Codecs; Service Description; Stage 3 | TS | 8.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.62/0862-801.zip | This service description document details the Inband Signalling Protocol between Transcoder/Rate Adaptor Units for speech traffic channels for the Tandem Free Operation (TFO) of Speech Codecs.
This service description should be considered together with GSM 08.60 (Inband control of remote transcoders and rate adaptors for Enhanced Full Rate and Full Rate traffic channels) and GSM 08.61 (Inband control of remote transcoders and rate adaptors for Half Rate traffic channels).
Annex A is mandatory and describes the general Inband Signalling (IS) Principle.
Annex B is informative and gives the rules for In Path Equipment (IPE).
Annex C is the formal SDL description of the TFO Protocol as given in clause 10. Clause 10 has precedence in case of ambiguities. A part of Annex C is in electronic format. Annex C is informative. It supports the formal verification of the TFO Protocol. |
08.71 | Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC-BSS) interface; Layer 3 | TS | 8.6.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.71/0871-860.zip | The present document contains the coding of information necessary for support of location service operation on the SMLC-BSS interface layer 3.
Clause 2 gives the functional definitions and contents of messages for location service operations. Clause 3 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations. |
09.01 | General Network Interworking Scenarios | TR | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/09_series/09.01/0901-800.zip | The present document serves as an introduction to the GSM 09.xx‑series.
In clause 4, the technical requirements for Public Land Mobile Network (PLMN) interworking are introduced, and in clause 5 there is a summary of the contents of the GSM 09.xx‑series. |
09.08 | Application of the Base Station System Application Part (BSSAP) on the E-Interface | TS | 8.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/09_series/09.08/0908-820.zip | The present document describes the subset of Base Station System Application Part (BSSAP) messages and procedures, defined in 3GPP TS 08.06 and 3GPP TS 08.08, which is used on the E‑interface. A general description can be found in 3GPP TS 03.02 and 3GPP TS 03.09.
For the initiation and execution of handover between MSCs a subset of BSSMAP procedures are used. For the subsequent control of resources allocated to the Mobile Station (MS) BSSMAP procedures are used. DTAP is used for the transfer of connection management and mobility management messages between the MS and the controlling MSC. |
09.31 | Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE) | TS | 8.7.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/09_series/09.31/0931-871.zip | The present document specifies procedures and information coding that are needed to define and support the BSSAP LCS Extension (BSSAP-LE). The BSSAP-LE message set is applicable to the following GSM interfaces defined in 3GPP TS 03.71:
Lb interface (BSC-SMLC).
Ls interface (MSC-SMLC).
Lp interface (SMLC-SMLC).
The present document defines message formats and encoding for BSSAP-LE and the particular subsets of it that are applicable to each of the above interfaces. The present document also defines the support for BSSAP-LE message transfer on each of these interfaces using CCITT and ANSI versions of SS7 MTP and SCCP. Additional requirements for the above interfaces that are applicable to BSSAP-LE are also defined – e.g. usage of BSSAP (as defined in 3GPP TS 04.08 and 08.08) on the Lb interface. |
09.95 | General Packet Radio Service (GPRS); Interworking between modified Public Land Mobile Network (PLMN) supporting GPRS and legacy GPRS mobiles | TR | 8.0.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/09_series/09.95/0995-800.zip | This report describes issues relating to the GPRS specifications, which lead to the specifications being modified after the placement of GPRS compliant mobiles into the market place.
Where possible the present report clarifies any recommended measures which may be adopted by the GPRS infrastructure to enable interworking to be obtained between the GPRS infrastructure and legacy Mobile Station (MS) implementations of the GPRS specifications.
For each issue this report also defines the time after which all new GPRS mobiles are required to meet the modified specifications.
The lifetime of the herein described measures together with their potential impact on optimal network performance is out of the scope of the present document. |
10.56 | Project scheduling and open issues: GSM Cordless Telephony System CTS, Phase 1 | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/10_series/10.56/1056-800.zip | |
10.59 | Project scheduling and open issues for EDGE | TR | 8.0.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/10_series/10.59/1059-800.zip | |
10.68 | Introduction to the services: enhanced Multi-Level Precedence and Pre-emption (eMLPP), Voice Group Call Service (VGCS), Voice Broadcast Service (VBS) | TR | 1.22.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/10_series/10.68/1068-1m0.zip | |
11.10-1 | Mobile station (MS) conformance specification; Part 1: Conformance specification | TS | 8.3.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-1/1110-1-830.zip | The present document describes the technical characteristics and methods of test for Mobile Stations (MS), for the Pan European digital cellular communications system and Personal Communication Systems (PCS) operating in the 400 MHz, 900 MHz and 1 800 MHz band (GSM 400, GSM 900 and DCS 1 800), standardized by ETSI Special Mobile Group (SMG).
The present document is valid for MS implemented according Phase2 or Phase2+ R96, or R97, or R98 or R99.
A subset of the tests is referenced in the GSM Common Technical Regulations (CTRs) and is used for regulatory conformance testing according to the EEC procedures for Telecommunications Terminal Equipment (TTE) type approval (EC Directive 91/263/EEC; also known as the "Terminal Directive" or "Second Phase Directive"). The remaining tests can be used to verify conformance with the GSM core technical specifications for those requirements that are not considered "essential" in the sense of the EC Directive 91/263/EEC (Article 4).
The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
It applies to the public land mobile radio service in the GSM 400, GSM 900 and DCS 1 800 systems, using constant envelope modulation and operating on radio frequencies in the 400, 900 and 1 800 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. This EN neither replaces any of the other GSM technical specifications or GSM related TSs, nor is it created to provide full understanding of (or parts of) the GSM 400, GSM 900 and DCS 1 800 systems. The present document lists the requirements, and provides the methods of test for testing a MS for conformance to the GSM standard.
For a full description of the system, reference should be made to all the GSM technical specifications. Clause 2 provides a complete list of the GSM technical specifications, GSM related TSs, and TRs, on which this conformance test specifications is based.
The present document applies to the unit which includes the hardware to establish a connection across the radio interface.
If there is a difference between this conformance test TS, and any other GSM technical specification, then the other GSM technical specification shall prevail. |
11.10-4 | Mobile Station (MS) conformance specification; Part 4: Subscriber Identity Module (SIM) application toolkit conformance test specification | TS | 8.15.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-4/1110-4-8f0.zip | The present document describes the technical characteristics and methods of test for testing the SIM Application Toolkit implemented in Mobile Stations (MS) for the Pan European digital cellular communications system and Personal Communication Systems (PCS) operating in the 450 MHz, 480 MHz, 700 MHz, 750 MHz, 850 MHz, 900 MHz, 1 800 MHz and 1 900 MHz frequency band (GSM 400, GSM 700, GSM 750, GSM 850, GSM 900, DCS 1 800 and PCS 1 900) within the European digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [19] and ETS 300 406 [20].
The present document is valid for MS implemented according to GSM Phase2+ R96, or R97, or R98, or R99.
The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
The present document is part of the GSM-series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related ETSs or ENs, nor is it created to provide full understanding of (or parts of) the GSM 400, GSM 700, GSM 850, GSM 900, DCS1800 and PCS1900 systems . The present document lists the requirements, and provides the methods of test for testing the SIM Application Toolkit implemented in a MS for conformance to the GSM standard.
For a full description of the system, reference should be made to all the GSM technical specifications or GSM related ETSs or ENs. Clause 2 provides a complete list of the GSM technical specifications, GSM related ETSs, ENs, and ETRs, on which this conformance test specifications is based.
If there is a difference between this present conformance document, and any other GSM technical specification or GSM related ETS or EN, or 3GPP TS, then the other GSM technical specification or GSM related ETS or EN or 3GPP TS shall prevail. |
11.11 | Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) Interface | TS | 8.14.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.11/1111-8e0.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 TS 02.17 [6].
The present document defines:
‑ the requirements for the physical characteristics of the SIM, the electrical signals and the transmission protocols;
‑ 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.
Unless otherwise stated, references to GSM also apply to DCS 1800 and PCS 1900.
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. |
11.13 | Test specification for Subscriber Interface Module (SIM) Application Programme Interface (API) for Java card | TS | 8.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.13/1113-830.zip | The present document covers the minimum characteristics considered necessary in order to provide compliance to GSM 03.19 [7].
The present document describes the technical characteristics and methods of test for testing the SIM API for Java CardTM [7] implemented in the subscriber identity modules (SIMs) for GSM. It specifies the following parts:
- test applicability;
- test environment description;
- tests format;
- test area reference;
- conformance requirements;
- test suite files;
- test procedure;
- test coverage; and
- a description of the associated testing tools that shall be used. |
11.14 | Specification of the SIM Application Toolkit (SAT) for the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface | TS | 8.18.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.14/1114-8i0.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".
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 11.11 [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 02.17 [3].
The present document defines:
- the commands;
- the application protocol;
- the mandatory requirements on the SIM and 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 SIM or 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.
The present document defines an enhancement for GSM Phase 2+ of 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. |
11.17 | Subscriber Identity Module (SIM) test specification | TS | 8.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.17/1117-820.zip | The present document provides the Conformance Test Specification for the Subscriber Identity Module defined in GSM 11.11 [1], GSM 11.12 [8] and GSM 11.18 [9]. |
11.21 | Base Station System (BSS) equipment specification; Radio aspects | TS | 8.11.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.21/1121-8b0.zip | The present document specifies the Radio Frequency (RF) test methods and conformance requirements for GSM 400, GSM 900 and DCS 1800, PCS 1900, GSM 850, MXM 850 and MXM 1900 Base Station Systems (BSS)s. These have been derived from, and are consistent with, the core GSM specifications specified in the requirements reference subclause of each test with the exception that requirements expressed as a reference to regulatory documents (e.g. FCC) have not been included in the present document.
The present document is applicable to BSS meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to BSS meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support.
For each test, two conformance requirements are specified:
‑ essential conformance requirements;
‑ complete conformance requirements.
Essential conformance requirements are those which are required:
a) to ensure compatibility between the radio channels in the same cell;
b) to ensure compatibility between cells, both co‑ordinated and unco‑ordinated;
c) to ensure compatibility with existing systems in the same or adjacent frequency bands;
d) to verify the important aspects of the transmission quality of the system.
Essential conformance requirements are sufficient to verify the performance of the equipment for radio type approval purposes, in countries where this is applicable. For GSM 850, MXM 850, PCS 1900 and MXM 1900 only the complete conformance requirements are applicable.
Complete conformance requirements may be tested to verify all aspects of the performance of a BSS. These requirements are intended to be used by manufacturers and operators to allow conformance and acceptance testing to be performed in a consistent manner; the tests to be performed should be agreed between the parties.
In some tests there are separate requirements for micro‑BTS and BTS. If there is no separate requirement for a micro‑BTS, the requirements for the BTS apply to a micro‑BTS.
In the present document, the reference point for RF connections (except for the measurement of mean transmitted RF carrier power) is the antenna connector, as defined by the manufacturer. The present document does not apply to repeaters or RF devices which may be connected to an antenna connector of a BSS, except as specified in subclause 4.10.
NOTE: The present document contains both essential conformance requirements and complete conformance requirements. Essential conformance requirements are those requirements which may be deemed sufficient for radio type approval purposes, complete conformance requirements cover all conformance aspects. |
11.26 | Base Station System (BSS) equipment specification; Part 4: Repeaters | TS | 8.0.2 | R6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.26/1126-802.zip | The present document describes the Radio Frequency (RF) tests for GSM 450, GSM 480, GSM 900 and DCS 1800 repeaters which receive, amplify, and retransmit a received Mobile Station (MS) signal in the GSM MS transmit band and simultaneously receive, amplify and retransmit a received Base Transceiver Station (BTS) RF signal in the GSM BTS transmit band.
The present document is applicable to repeaters meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to repeaters meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support. |
12.03 | Security Management | TS | 8.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/12_series/12.03/1203-800.zip | The present document describes the management of the security related aspects in the GSM/DCS PLMN. The management of the relevant security services is addressed with respect to the following aspects:
Overview of the security features;
Description of the relevant management procedures;
Modeling using the object oriented paradigm.
The definitions and descriptions of the security features and mechanisms are contained in the specifications of the underlying procedures and are not defined in the present document. References to appropriate GSM/DCS specifications have been made throughout the present document where necessary. Issues relating to the security of management (e.g. file transfer security, database security, inter‑operator security, etc.) are not covered in the present document. |
12.04 | Performance data measurements | TS | 8.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/12_series/12.04/1204-810.zip | The present document describes the requirements for the management of performance measurements and the collection of performance measurement data across a Public Land Mobile Network (PLMN). It defines the administration of measurement schedules, the generation of measurement results in the Network Elements (NEs) and the transfer of these results to the Operations System (OS). It also describes how the various requirements can be modelled as part of the generic PLMN information model.
A set of measurements available for collection by NEs are described in annex B, effort has been made to ensure consistency in the definition of measurements between different NEs.
The following is beyond the scope the present document:
- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
- the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate.
The objective of the present document is: to normalise the description of each measurement; and to produce a common description of the management technique for result accumulation and transmission across a management interface. The normalisation is intended to result in comparability of measurement data produced in a multi-vendor PLMN.
As far as possible, existing standardisation in the area of performance management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised.
Field of application
The present document considers all aspects of performance management for a PLMN and its NEs defined in the GSM core Technical Specifications. However, only those aspects, which are GSM specific and particular to PLMN operation are included in the present document. Other performance measurement aspects of described NEs and performance measurement aspects of NEs not described by the GSM core Technical Specifications are included for information purposes in annex E or may be found in referenced documents. |
12.21 | Network Management (NM) procedures and messages on the A-bis interface | TS | 8.0.0 | R6 | https://www.3gpp.org/ftp/Specs/archive/12_series/12.21/1221-800.zip | The present document addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities.
There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. The present document addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to the present document it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality.
It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document. |
12.71 | Location Services (LCS); Location services management | TS | 8.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/12_series/12.71/1271-801.zip | The present document addresses the network management architecture, functions, and protocol for LCS operations and maintenance. The information model included here defines the managed entities and how they are addressed for purposes of operations and maintenance activities.
There is a requirement for the network management interface to be open to allow interoperation between LMUs and GMLCs of different manufacturers working to the same SMLC. The present document addresses this requirement from an operations and maintenance point of view, which allows this interworking to take place. It shows the split of network management functions between GMLC, SMLC and LMU. The procedures and coding of the messages are specified in detail. In practice, in addition to the present document, it is necessary that the content of manufacturer-dependent information fields be specified to fulfil the functionality.
It is essential for operation that a SMLC can handle the functions used by all its LMUs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document.
NOTE: This version contains only the SMLC-LMU interface. Other work will be undertaken in the future. |
13.21 | Base station systems and repeater equipment covering essential requirements under article 3.2 of the R&TTE directive | TS | 8.1.2 | - | https://www.3gpp.org/ftp/Specs/archive/13_series/13.21/1321-812.zip | |
21.101 | Technical Specifications and Technical Reports for a UTRAN-based 3GPP system | TS | 3.18.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.101/21101-3i0.zip | |
21.111 | USIM and IC card requirements | TS | 3.5.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.111/21111-350.zip | |
21.133 | 3G security; Security threats and requirements | TS | 3.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.133/21133-320.zip | |
21.801 | Specification drafting rules | TR | 3.0.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.801/21801-300.zip | |
21.900 | Technical Specification Group working methods | TR | 3.7.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.900/21900-370.zip | |
21.904 | User Equipment (UE) capability requirements | TR | 3.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.904/21904-350.zip | The present document’s scope is the Release 99 of the 3GPP specifications to which it refers. This document is not currently planned to be kept updated beyond December 2000.
The present document defines a baseline set of capability requirements that enable all UEs to "register" with all applicable 3GPP networks (depending on the availability of a appropriate subscription). It describes all the functions that a UE has to perform in order to "exist" within a 3GPP network. These functions are used to derive requirements for all aspects of UE baseline capability. The present document also identifies different UE Service Capabilities and the functions that a UE must perform in order to access a service. The actual capabilities that a UE must posses to meet these requirements are identified in the report and in some instances listed in the Annexes to the present document, as well as being described in the referenced implementation specifications.
The present document introduces the concept of "service-less UE" which can exist in the network but provides no user service. Although this is not a marketable UE type it describes from the standardisation viewpoint a baseline set of capabilities to which specific service-related UE capabilities can then be added.
The present document should not be used as the sole basis for UE design, only as an informative indication of capabilities required to support a given functionality, and as a pointer to the location of text describing said functionality, in the core specifications.
UE capability requirements may include some regulatory requirements (mandatory requirements). However, it is not intended to identify them as such in this report. Some of the requirements identified in this document as essential, may therefore also be “mandatory” according to the definition of that term appearing herein. |
21.905 | Vocabulary for 3GPP Specifications | TR | 3.3.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.905/21905-330.zip | |
21.910 | Multi-mode UE issues; categories, principles and procedures | TR | 3.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.910/21910-300.zip | This 3GPP Technical Report identifies multi-mode User Equipments categories. This technical report also describes the general principles and procedures for the multi-mode operation standardised in the 3GPP specifications. In particular, this TR is focused on a type 2 UE, as defined in Clause 4 in the present report. This type of UE can when utilising one mode, perform monitoring of another mode and report it utilising the current mode. This type of UE does not support simultaneous reception or transmission through different modes.
The scope of this TR is the type of terminal implemented with at least the following modes:
- UTRA FDD and/or TDD mode
- GSM mode
Regarding the GSM mode, it encompasses the capabilities offered by the GSM technical specifications, e.g, Circuit Switched and Packet Switched services using either GMSK or 8-PSK modulation in the frequency bands specified in the GSM specifications.
The present report is built on and references specifications/reports being produced in 3GPP or within other relevant foras e.g. ETSI SMG. |
21.978 | Feasibility Technical Report; CAMEL Control of VoIP Services | TR | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.978/21978-300.zip | The purpose of this Technical Report is to study the feasibility of a core network CAMEL server controlling voice services carried by VoIP within a GPRS PDP Context using:
1) An architecture based on ITU-T, H.323 family of recommendations.
2) An architecture based on IETF SIP specifications. |
22.001 | Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) | TS | 3.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.001/22001-320.zip | |
22.002 | Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) | TS | 3.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.002/22002-360.zip | |
22.003 | Circuit Teleservices supported by a Public Land Mobile Network (PLMN) | TS | 3.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.003/22003-330.zip | |
22.004 | General on supplementary services | TS | 3.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.004/22004-330.zip | |
22.011 | Service accessibility | TS | 3.8.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.011/22011-380.zip | |
22.016 | International Mobile station Equipment Identities (IMEI) | TS | 3.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.016/22016-330.zip | |
22.022 | Personalisation of Mobile Equipment (ME); Mobile functionality specification | TS | 3.2.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.022/22022-321.zip | |
22.024 | Description of Charge Advice Information (CAI) | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.024/22024-301.zip | |
22.030 | Man-Machine Interface (MMI) of the User Equipment (UE) | TS | 3.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.030/22030-340.zip | |
22.031 | 3G Security; Fraud Information Gathering System (FIGS); Service description; Stage 1 | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.031/22031-300.zip | |
22.032 | Immediate Service Termination (IST); Service description; Stage 1 | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.032/22032-300.zip | |
22.034 | High Speed Circuit Switched Data (HSCSD); Stage 1 | TS | 3.2.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.034/22034-321.zip | |
22.038 | (U)SIM Application Toolkit (USAT); Service description; Stage 1 | TS | 3.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.038/22038-340.zip | |
22.041 | Operator Determined Barring (ODB) | TS | 3.3.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.041/22041-331.zip | |
22.042 | Network Identity and TimeZone (NITZ); Service description; Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.042/22042-301.zip | |
22.057 | Mobile Execution Environment (MExE); Service description; Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.057/22057-301.zip | |
22.060 | General Packet Radio Service (GPRS); Service description; Stage 1 | TS | 3.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.060/22060-350.zip | |
22.066 | Support of Mobile Number Portability (MNP); Service description; Stage 1 | TS | 3.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.066/22066-320.zip | |
22.067 | enhanced Multi Level Precedence and Pre-emption service (eMLPP); Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.067/22067-301.zip | |
22.071 | Location Services (LCS); Service description; Stage 1 | TS | 3.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.071/22071-350.zip | |
22.072 | Call Deflection (CD) service description; Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.072/22072-301.zip | |
22.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description; Stage 1 | TS | 3.9.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.078/22078-390.zip | |
22.079 | Support of Optimal Routeing (SOR); Service definition; Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.079/22079-301.zip | |
22.081 | Line Identification supplementary services; Stage 1 | TS | 3.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.081/22081-320.zip | |
22.082 | Call Forwarding (CF) Supplementary Services; Stage 1 | TS | 3.0.2 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.082/22082-302.zip | |
22.083 | Call Waiting (CW) and Call Holding (HOLD); Supplementary Services; Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.083/22083-301.zip | |
22.084 | MultiParty (MPTY) supplementary service; Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.084/22084-301.zip | |
22.085 | Closed User Group (CUG) supplementary services; Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.085/22085-310.zip | |
22.086 | Advice of Charge (AoC) supplementary services; Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.086/22086-310.zip | |
22.087 | User-to-User Signalling (UUS); Service description; Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.087/22087-310.zip | |
22.088 | Call Barring (CB) supplementary services; Stage 1 | TS | 3.0.2 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.088/22088-302.zip | |
22.090 | Unstructured Supplementary Service Data (USSD); Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.090/22090-310.zip | |
22.091 | Explicit Call Transfer (ECT) supplementary service; Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.091/22091-310.zip | |
22.093 | Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.093/22093-301.zip | |
22.094 | Follow Me service description; Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.094/22094-310.zip | |
22.096 | Name identification supplementary services; Stage 1 | TS | 3.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.096/22096-301.zip | |
22.097 | Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1 | TS | 3.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.097/22097-320.zip | |
22.100 | UMTS Phase 1 | TS | 3.7.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.100/22100-370.zip | The UMTS system will be defined in a phased approach. The present document specifies the requirements for Release '99 of UMTS. Some requirements which are necessary to ensure a smooth transition to later releases are also indicated. The present document should, however, be read in conjunction with the other 22.000 series documents which provide a complete description of the requirements for UMTS Release '99. |
22.101 | Service aspects; Service principles | TS | 3.17.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.101/22101-3h0.zip | |
22.105 | Services and service capabilities | TS | 3.10.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.105/22105-3a0.zip | |
22.115 | Service aspects; Charging and billing | TS | 3.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.115/22115-340.zip | |
22.121 | Service aspects; The Virtual Home Environment (VHE); Stage 1 | TR | 3.3.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.121/22121-331.zip | |
22.129 | Service aspects; Handover requirements between UTRAN and GERAN or other radio systems | TS | 3.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.129/22129-360.zip | |
22.135 | Multicall; Service description; Stage 1 | TS | 3.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.135/22135-340.zip | |
22.140 | Multimedia Messaging Service (MMS); Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.140/22140-310.zip | |
22.945 | Study of provision of fax service in GSM and UMTS | TR | 3.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.945/22945-300.zip | |
22.971 | Automatic establishment of roaming relationships | TR | 3.1.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.971/22971-311.zip | This document outlines a proposed framework for commercial and technical interworking between UMTS Home Environments and Serving Networks who have no direct prior commercial agreements with each other.
This document is applicable to UMTS standardisation within ETSI, and is produced with the intent to clarify the concepts involved, and identify those areas which require standardisation. |
22.975 | Advanced addressing | TR | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.975/22975-310.zip | This document defines the requirements for numbering and addressing for UMTS. This technical report is aimed at generating discussion and should agreed with ETSI WG NA2. The responsibility for developing of Numbering and Addressing schemes for all networks being in ETSI NA2. |
23.002 | Network architecture | TS | 3.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-360.zip | |
23.003 | Numbering, addressing and identification | TS | 3.15.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-3f0.zip | |
23.007 | Restoration procedures | TS | 3.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-360.zip | |
23.008 | Organization of subscriber data | TS | 3.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-380.zip | |
23.009 | Handover procedures | TS | 3.14.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-3e0.zip | |
23.011 | Technical realization of Supplementary Services | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-310.zip | |
23.012 | Location management procedures | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-330.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 3.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-320.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-310.zip | |
23.016 | Subscriber data management; Stage 2 | TS | 3.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-3a0.zip | |
23.018 | Basic call handling; Technical realization | TS | 3.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-3c0.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-300.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 3.2.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-321.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.