id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2 values | version stringclasses 560 values | working_group stringclasses 30 values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
49.008 | Application of the Base Station System Application Part (BSSAP) on the E interface | TS | 5.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/49_series/49.008/49008-510.zip | |
48.058 | Base Station Controller - Base Transceiver Station (BSC - BTS) Interface; Layer 3 specification | TS | 5.6.0 | RP | https://www.3gpp.org/ftp/Specs/archive/48_series/48.058/48058-560.zip | |
51.013 | Test specification for Subscriber Identity Module (SIM) Application Programming Interface (API) for Java Card | TS | 5.7.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.013/51013-570.zip | |
51.010-3 | Mobile Station (MS) conformance specification; Part 3: Layer3 (L3) Abstract Test Suite (ATS) | TS | 5.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-3/51010-3-540.zip | The present document specifies the Abstract Test Suites (ATS) and partial IXIT proforma for the Network Layer (Layer 3) at the mobile radio interface of the GSM/3GPP mobile stations (MS) conforming to the TSs for Layer 3, cell selection, Enhanced Full Rate Speech, Multi-band, GSM-R band (R-GSM) and ASCI (the voice group call service (VGCS), voice broadcast service (VBS), enhanced Multi-Level Precedence and Pre-emption service (eMLPP), User-to-user Signalling (UUS) service and the Follow Me service) for the digital cellular telecommunications systems.
The present document is valid for MS implemented according GSM Phase2 or Phase2+ R96, or R97, or R98, or R99, or 3GPP Release 4, or Release 5.
The test suite in the current document is an example of TTCN implementation, and is not intended for direct use in formal conformance testing.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications. |
51.026 | Base Station System (BSS) equipment specification; Part 4: Repeaters | TS | 5.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/51_series/51.026/51026-500.zip | |
52.021 | Network Management (NM) procedures and messages on the A-bis interface | TS | 5.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/52_series/52.021/52021-500.zip | |
52.402 | Telecommunication management; Performance Management (PM); Performance measurements - GSM | TS | 5.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/52_series/52.402/52402-500.zip | |
51.010-2 | Mobile Station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification | TS | 5.11.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-2/51010-2-5b0.zip | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for Global System for Mobile Stations (MSs), 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, R-GSM 900, ER-GSM 900, 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 [3] and ETS 300 406 [1].
The present document is valid for MS implemented according to GSM Phase2 or Phase2+ R96, or R97, or R98, or R99 or 3GPP Release 4 or 3GPP Release 5 or 3GPP Release 6 or 3GPP Release 7 or 3GPP Release 8, 3GPP Release 9 or 3GPP Release 10 or 3GPP Release 11 or 3GPP Release 12. |
55.217 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 2: Implementors' test data | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.217/55217-500.zip | |
55.919 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 4: Design and evaluation report | TR | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.919/55919-500.zip | |
55.216 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 1: A5/3 and GEA3 specifications | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.216/55216-500.zip | |
21.111 | USIM and IC card requirements | TS | 4.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.111/21111-420.zip | |
21.101 | Technical Specifications and Technical Reports for a UTRAN-based 3GPP system | TS | 4.15.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.101/21101-4f0.zip | |
21.133 | 3G security; Security threats and requirements | TS | 4.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.133/21133-410.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.801 | Specification drafting rules | TR | 4.4.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.801/21801-440.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. |
55.218 | 3G Security; Specification of the A5/3 encryption algorithms for GSM and ECSD, and the GEA3 encryption algorithm for GPRS; Document 3: Design conformance test data | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/55_series/55.218/55218-500.zip | |
21.900 | Technical Specification Group working methods | TR | 4.1.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.900/21900-410.zip | |
22.002 | Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) | TS | 4.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.002/22002-420.zip | |
22.001 | Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) | TS | 4.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.001/22001-430.zip | |
22.016 | International Mobile station Equipment Identities (IMEI) | TS | 4.2.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.016/22016-421.zip | |
22.003 | Circuit Teleservices supported by a Public Land Mobile Network (PLMN) | TS | 4.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.003/22003-430.zip | |
22.011 | Service accessibility | TS | 4.8.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.011/22011-480.zip | |
21.905 | Vocabulary for 3GPP Specifications | TR | 4.5.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.905/21905-450.zip | |
22.024 | Description of Charge Advice Information (CAI) | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.024/22024-400.zip | |
22.004 | General on supplementary services | TS | 4.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.004/22004-430.zip | |
22.022 | Personalisation of Mobile Equipment (ME); Mobile functionality specification | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.022/22022-410.zip | |
22.030 | Man-Machine Interface (MMI) of the User Equipment (UE) | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.030/22030-410.zip | |
22.031 | 3G Security; Fraud Information Gathering System (FIGS); Service description; Stage 1 | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.031/22031-400.zip | |
22.038 | (U)SIM Application Toolkit (USAT); Service description; Stage 1 | TS | 4.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.038/22038-430.zip | |
22.034 | High Speed Circuit Switched Data (HSCSD); Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.034/22034-410.zip | |
22.032 | Immediate Service Termination (IST); Service description; Stage 1 | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.032/22032-400.zip | |
22.041 | Operator Determined Barring (ODB) | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.041/22041-410.zip | |
22.053 | Tandem Free Operation (TFO); Service description; Stage 1 | TS | 4.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.053/22053-401.zip | |
22.057 | Mobile Execution Environment (MExE); Service description; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.057/22057-410.zip | |
22.042 | Network Identity and TimeZone (NITZ); Service description; Stage 1 | TS | 4.2.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.042/22042-421.zip | |
22.071 | Location Services (LCS); Service description; Stage 1 | TS | 4.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.071/22071-460.zip | |
22.072 | Call Deflection (CD) service description; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.072/22072-400.zip | |
22.076 | Noise suppression for the AMR codec; Service description; Stage 1 | TS | 4.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.076/22076-401.zip | |
22.060 | General Packet Radio Service (GPRS); Service description; Stage 1 | TS | 4.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.060/22060-440.zip | |
22.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description; Stage 1 | TS | 4.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.078/22078-450.zip | |
22.066 | Support of Mobile Number Portability (MNP); Service description; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.066/22066-400.zip | |
22.079 | Support of Optimal Routeing (SOR); Service definition; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.079/22079-400.zip | |
22.067 | enhanced Multi Level Precedence and Pre-emption service (eMLPP); Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.067/22067-410.zip | |
22.048 | Security mechanisms for the (U)SIM application toolkit; Stage 1 | TS | 4.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.048/22048-400.zip | The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a 3G or GSM PLMN Entity and a UICC.
The security mechanisms which are specified are independent of applications.
The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (TS 23.048).
The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
Within the scope of this document, the UICC refers here to a ICC which support at least one application in order to access a cellular network.
The ICC is considered as a platform, which is either based on TS 31.101 [13], here called "3G platform", or TS 51.011 [23], here called "2G platform". |
22.082 | Call Forwarding (CF) Supplementary Services; Stage 1 | TS | 4.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.082/22082-420.zip | |
22.084 | MultiParty (MPTY) supplementary service; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.084/22084-410.zip | |
22.081 | Line Identification supplementary services; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.081/22081-410.zip | |
22.086 | Advice of Charge (AoC) supplementary services; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.086/22086-400.zip | |
22.090 | Unstructured Supplementary Service Data (USSD); Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.090/22090-400.zip | |
22.091 | Explicit Call Transfer (ECT) supplementary service; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.091/22091-400.zip | |
22.093 | Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.093/22093-400.zip | |
22.094 | Follow Me service description; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.094/22094-410.zip | |
22.096 | Name identification supplementary services; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.096/22096-400.zip | |
22.085 | Closed User Group (CUG) supplementary services; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.085/22085-410.zip | |
22.097 | Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.097/22097-410.zip | |
22.087 | User-to-User Signalling (UUS); Service description; Stage 1 | TS | 4.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.087/22087-400.zip | |
22.083 | Call Waiting (CW) and Call Holding (HOLD); Supplementary Services; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.083/22083-410.zip | |
22.105 | Services and service capabilities | TS | 4.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.105/22105-430.zip | |
22.115 | Service aspects; Charging and billing | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.115/22115-410.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 | 4.1.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.121/22121-411.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.101 | Service aspects; Service principles | TS | 4.10.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.101/22101-4a0.zip | This Technical Specification (TS) describes the Service Principles for PLMNs specified by 3GPP. Principles and requirements for interworking with WLAN are covered in TS 22.234 [35].
3GPP specifications provide integrated personal communications services. The system will support different applications ranging from narrow-band to wide-band communications capability with integrated personal and terminal mobility to meet the user and service requirements of the 21st century.
3GPP specifications allow the realisation of a new generation of mobile communications technology for a world in which personal communications services should allow person-to-person calling, independent of location, the terminal used, the means of transmission (wired or wireless) and the choice of technology. Personal communication services should be based on a combination of fixed and wireless/mobile services to form a seamless end-to-end service for the user.
3GPP specifications should be in compliance with the following objectives:
a) to provide a single integrated system in which the user can access services in an easy to use and uniform way in all environments;
b) to allow differentiation between service offerings of various serving networks and home environments;
c) to provide a wide range of telecommunications services including those provided by fixed networks and requiring user bit rates of up to 100 Mbit/s as well as services special to mobile communications. These services should be supported in residential, public and office environments and in areas of diverse population densities. These services are provided with a quality comparable with that provided by fixed networks such as ISDN and fixed broadband Internet access;
d) to provide services via hand held, portable, vehicular mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments - residential, private domestic and different radio environments) provided that the terminal has the necessary capabilities;
e) to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming.
f) to provide audio, data, video and particularly multimedia services;
g) to provide for the flexible introduction of telecommunication services;
h) to provide within the residential environment the capability to enable a pedestrian user to access all services normally provided by fixed networks;
i) to provide within the office environment the capability to enable a pedestrian user to access all services normally provided by PBXs and LANs;
j) to provide a substitute for fixed networks in areas of diverse population densities, under conditions approved by the appropriate national or regional regulatory authority.
k) to provide support for interfaces which allow the use of terminals normally connected to fixed networks. |
22.129 | Service aspects; Handover requirements between UTRAN and GERAN or other radio systems | TS | 4.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.129/22129-440.zip | |
22.135 | Multicall; Service description; Stage 1 | TS | 4.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.135/22135-420.zip | |
22.088 | Call Barring (CB) supplementary services; Stage 1 | TS | 4.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.088/22088-410.zip | |
23.002 | Network architecture | TS | 4.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-480.zip | |
22.127 | Service requirement for the Open Services Access (OSA); Stage 1 | TS | 4.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.127/22127-440.zip | This document specifies the stage 1 requirements for realisation of an Open Service Access (OSA).
OSA enables applications to make use of network functionality through an open standardised interface (the OSA API). OSA provides the glue between applications and network functionality. In this way applications implementing the services become independent from the underlying network technology.
Applications which make use of network functionality offered through the OSA interface are not standardised by 3GPP.
The network functionality offered through the OSA interface may or may not be standardised by 3GPP.
OSA is one toolkit, amongst others, that enables certain aspects of the requirements of the Virtual Home Environment (VHE) concept to be realised. |
23.007 | Restoration procedures | TS | 4.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-420.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. |
23.008 | Organization of subscriber data | TS | 4.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-430.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. |
22.140 | Multimedia Messaging Service (MMS); Stage 1 | TS | 4.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.140/22140-430.zip | |
23.011 | Technical realization of Supplementary Services | TS | 4.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-401.zip | |
23.012 | Location management procedures | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-400.zip | |
23.009 | Handover procedures | TS | 4.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-490.zip | |
23.003 | Numbering, addressing and identification | TS | 4.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-490.zip | |
23.016 | Subscriber data management; Stage 2 | TS | 4.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-440.zip | |
23.018 | Basic call handling; Technical realization | TS | 4.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-470.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 4.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-400.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 4.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-401.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.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 4.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-410.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 4.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-410.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 4.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-400.zip | |
23.039 | Interface Protocols for the connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs) | TR | 4.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.039/23039-400.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.038 | Alphabets and language-specific information | TS | 4.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-450.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 4.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-4a0.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 4.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-440.zip | |
23.042 | Compression algorithm for text messaging services | TS | 4.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-401.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 4.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-450.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 4.1.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-411.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 4.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-401.zip | |
23.048 | Security mechanisms for the (U)SIM application toolkit; Stage 2 | TS | 4.5.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.048/23048-450.zip | The present document specifies the structure of the Secured Packets in a general format and in implementations using Short Message Service Point to Point (SMS-PP) and Short Message Service Cell Broadcast (SMS-CB).
Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in 3GPP TS 51.011 [5] and allows remote management of files on the UICC in conjunction with SMS and the Data Download to UICC feature of 3GPP TS 31.111.
For UICCs based on 3GPP TS 43.019 [15], the set of commands used in the remote applet management is defined in the present document. This is based on the Open Platform card management specification [14]. For UICCs based on other technologies, other loading mechanisms may be used.
The present document is applicable to the exchange of secured packets between an entity in a 3G or GSM PLMN and an entity in the UICC.
Secured Packets contain application messages to which certain mechanisms according to 3GPP TS 22.048 have been applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or GSM PLMN and on the UICC. The Sending/Receiving Entity in the 3G or GSM PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets. |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 4.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-4b0.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 4.1.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-411.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 4.11.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-4b1.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 4.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-420.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 4.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-430.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-400.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-400.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-400.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-400.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 4.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-400.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 4.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-410.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.