id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2 values | version stringclasses 561 values | working_group stringclasses 30 values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
08.14 | General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Gb Interface Layer 1 | TS | 8.0.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.14/0814-801.zip | The present document specifies the physical layer on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface) and references layer 1 standards to be used on this interface.
The protocol stack on the Gb interface is defined in the stage 2 3GPP TS 03.60 [3]. |
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. |
08.16 | General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) Interface; Network Service | TS | 8.0.1 | R6 | https://www.3gpp.org/ftp/Specs/archive/08_series/08.16/0816-801.zip | The present document specifies the Network Service used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface).
The protocol stack on the Gb interface is defined in the stage 2 Technical Specification 3GPP TS 03.60 [1].
The Network Service entity provides network services to the BSSGP entity specified in 3GPP TS 08.18 [2].
The layer 1 of the Gb interface is specified in 3GPP TS 08.14 [3].
In the present document, the communication between adjacent layers and the services provided by the layers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by the present document.
The service primitive model used in the present document is based on the concepts developed in CCITT Recommendation X.200 [4]. |
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 | |
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. |
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. |
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.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.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. |
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. |
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. |
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]. |
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.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.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 | |
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 | |
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. |
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.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 | |
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 | |
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 | |
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 | This specification takes notice of the Security Principles and Objectives as set out in [1]. It contains an evaluation of perceived threats to 3GPP and produces subsequently a list of security requirements to address these threats.
As teleservices and applications will not, in general, be standardised, it is difficult to predict their exact nature. Therefore, this specification considers all security threats and aims at listing generic security requirements that shall be applicable irrespective of the actual services offered. The list of threats and requirements may however need to be updated as the 3GPP system evolves.
The threat analysis performed relies to a large extent on previous experiences with 2G systems, in particular GSM, and takes into account known problems from that area.
The security requirements listed in this specification shall be used as input for the choice of security features and the design of the 3GPP security architecture as specified in [2].
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 contains a reference to the general objectives for 3G security;
clause 5 contains an overview of the context in which the security architecture of 3G is designed;
clause 6 contains a list of identified security threats to 3G, and gives some results from the threat analyses that have been performed;
clause 7 contains an overview of the risk assessment resulting from the threat analyses performed
clause 8 contains the resulting list of security requirements for 3G and indicates how these requirements relate to the threats and the security objectives .
Finally, Annex A gives some more detailed information on threats and risks connected to so called false base station attacks. |
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.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.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.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.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.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.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 | |
21.801 | Specification drafting rules | TR | 3.0.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.801/21801-300.zip | The present document specifies rules for the structure and drafting of documents intended to become a 3GPP Technical Specification or Technical Report. These rules are intended to ensure that such documents are drafted in as uniform a manner as is practicable, irrespective of the technical content.
The present document is based on the ISO/IEC Directives, Part 3, but is a self-contained document that will be maintained as such.
These drafting rules complement the 3GPP Working Procedures. |
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.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.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 | The present document describes the Service Aspects of charging and billing of the 3GPP System.
The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The present document will elaborate on the charging requirements described in the Charging Principles in 3GPP TS 22.101 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned. |
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 | The present document specifies the content of the Stage 1 requirement for realisation of VHE.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located. |
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.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.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. |
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 | |
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 | The data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station and the subscriber data required to handle traffic for each mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers; it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the location register data automatically. The present document defines the necessary procedures.
The basic principle is that restoration should be based on radio contact to avoid faulty data being spread in the system.
Subscriber data for supplementary services must also be correctly restored, although the impact on service of corruption of supplementary service data is less severe.
Procedures for supporting these functions are defined in 3GPP TS 29.002 [6] and 3GPP TS 29.060 [8].
The MAP operation "IMSI Attach" is used only in MAP version 1; in MAP version 2 the same function is performed by the MAP operation "Update Location Area". References in this specification to IMSI attach apply only to MAP version 1 network entities.
If the restoration of subscriber data in the VLR is triggered by Location Updating or IMSI Attach, the VLR retrieves subscriber data from the HLR by sending an "Update Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Update Location" request may also be used to send the LMSI to the HLR.
If the restoration of subscriber data in the VLR is triggered by a "Provide Roaming Number" request, the behaviour of the VLR depends on whether it is implemented according to MAP version 1 or MAP version 2. For MAP version 2, the VLR retrieves subscriber data from the HLR by sending a "Restore Data" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Restore Data" request is also used to send the LMSI to the HLR. For MAP version 1, the VLR retrieves subscriber data from the HLR by sending a "Send Parameters" request with parameter type "Subscriber Data", which cannot be used to send the LMSI to the HLR.
The VLR number and MSC number in the subscriber data in the HLR are updated by the "Update Location" procedure.
The GGSN (Gateway GPRS Support Node) is the point of PDN interconnection with the GSM PLMN supporting GPRS. The GGSN contains routing information for GPRS users with a PDP context active. The necessary procedures needed to restore GGSN data information after a restart are described in this document.
The SGSN (Serving GPRS Support Node) is the node that is serving the MS. The SGSN stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this SGSN information after a restart are described in this document.
The MME (Mobility Management Entity) is the node that is serving the UE when attached to E-UTRAN. The MME stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this MME information after a restart are described in this document.
A Type A LMU (Location Measurement Unit) is a network node, accessed over the GSM air interface, that is functionally similar to an MS. All requirements associated with a non-GPRS MS in this specification apply also to a Type A LMU except where specified otherwise. |
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. |
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 | The network feature Operator Determined Barring (ODB) allows a network operator or service provider to regulate access by subscribers to services (Circuit/Packet Oriented and Interworking WLAN), by the barring of certain categories of incoming or outgoing calls/ Packet Oriented Services or of roaming. Operator Determined Barring applies to all bearer services and teleservices except the Emergency Call teleservice and Emergency Bearer Services; the teleservice Short Message Point-to-Point is therefore subject to Operator Determined Barring in the same way as circuit-switched calls.
The application of specific categories of Operator Determined Barring to a subscription is controlled by the network operator or service provider, using administrative interaction at the HLR; this interface is not standardised. |
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 | The present document provides details concerning information to be stored in the different entities storing data within a 3GPP network concerning mobile subscriber. A list of entities storing subscriber data is provided in clause 1.
Clause 2 contains all details concerning the definition of the parameters, often given by reference to other specifications, and where the parameter is to be stored.
Table 1 in clause 3 gives a summary overview and clause 4 identifies the reference information required for accessing the information.
In this specification, if there is no specific indication, the following principles apply:
- "SGSN" refers to an SGSN which may support the Gn and Gp interfaces or the S4 interface or both.
- "S4-SGSN" refers to an SGSN which only supports the S4 interface.
- "Gn/Gp-SGSN" refers to an SGSN which only supports the Gn and Gp interfaces. |
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.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.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 | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 3.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-330.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 3.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-310.zip | |
23.038 | Alphabets and language-specific information | TS | 3.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-330.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.040 | Technical realization of the Short Message Service (SMS) | TS | 3.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-3b0.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 3.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-350.zip | |
23.042 | Compression algorithm for text messaging services | TS | 3.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-310.zip | |
23.039 | Interface Protocols for the connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs) | TR | 3.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.039/23039-320.zip | The present document describes a range of alternative interfaces which may be utilised by Short Message Service Centre (SMSC), and Short Message Entity (SME), developers for the connection of SMEs to SMSCs.
The purpose of the present document is to provide a single document within which the various proprietary SMSC to SME interface standards may be accommodated as optional implementations.
As stated in 3GPP TS 23.040 [1], the functionality of the SMSC is outside of the scope of the 3GPP Technical Specifications. As a result, no standardised interfaces have been specified for the connection of SMEs to the SMSC. In the absence of a prevailing standard, SC (Service Centre), developers have devised their own protocols which have not necessarily been based on any existing standards and are therefore largely incompatible with one another.
This document by referring to the various de-facto protocols will limit the further proliferation of proprietary standards and will benefit new SC/SME developers who may then adopt one or more of the existing protocols outlined in the present document.
This document does not provide recommendations, as to the preferred protocol implementation as all are regarded as being of equal merit. SC/SME implementors should therefore adopt the protocol most suited to their particular implementation, application or market. |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 3.17.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-3h0.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 3.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-340.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-330.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-330.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 3.19.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-3j0.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 3.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-380.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-320.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 3.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-370.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-320.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.