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 |
|---|---|---|---|---|---|---|
22.259 | Service requirements for Personal Network Management (PNM); Stage 1 | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.259/22259-g00.zip | |
22.261 | Service requirements for the 5G system | TS | 16.18.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.261/22261-gi0.zip | |
22.262 | Message service within the 5G System (5GS); Stage 1 | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.262/22262-g00.zip | |
22.268 | Public Warning System (PWS) requirements | TS | 16.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.268/22268-g40.zip | |
22.278 | Service requirements for the Evolved Packet System (EPS) | TS | 16.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.278/22278-g30.zip | |
22.279 | Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1 | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.279/22279-g00.zip | |
22.280 | Mission Critical Services Common Requirements (MCCoRe); Stage 1 | TS | 16.8.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.280/22280-g80.zip | |
22.281 | Mission Critical (MC) video | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.281/22281-g00.zip | |
22.282 | Mission Critical (MC) data | TS | 16.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.282/22282-g40.zip | |
22.289 | Mobile communication system for railways | TS | 16.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.289/22289-g10.zip | |
22.340 | IP Multimedia Subsystem (IMS) messaging; Stage 1 | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.340/22340-g00.zip | |
22.346 | Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1 | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.346/22346-g00.zip | |
22.368 | Service requirements for Machine-Type Communications (MTC); Stage 1 | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.368/22368-g00.zip | |
22.468 | Group Communication System Enablers (GCSE) | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.468/22468-g00.zip | |
22.519 | Business communication requirements | TS | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.519/22519-g00.zip | |
22.804 | Study on Communication for Automation in Vertical domains (CAV) | TR | 16.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.804/22804-g30.zip | The present document focuses on 5G communication for automation in vertical domains. This is communication that is involved in the production of and working on work pieces and goods, and/or the delivery of services in the physical world. Such communication often necessitates low latency, high reliability, and high communication service availability. Nevertheless, other types of communication are also possible in this area. Moreover, communications with low latency, high reliability, and high communication service availability, and other, not so demanding communication services, may run in parallel on the same 5G infrastructure.
The present document identifies stage 1 potential requirements for 5G communication for automation in vertical domains. The potential requirements are derived from different sources:
- existing work on dependable communication as used in vertical domains; see, for instance, IEC 61907 [2];
- use cases describing network operation in vertical domains with, for instance, common usage of the network (multi-tenancy) and network monitoring for assurance of service level agreements;
- security mechanisms already used in vertical domains; supporting the specific security requirements of vertical domains;
- new (additional to already existing stage-1 work), representative use cases in different vertical domains based on input from relevant vertical interest organisations and other stakeholders.
Furthermore, the present document provides an overview of relevant communication concepts for automation in vertical domains from the point of view of 5G systems. This overview is provided in order to facilitate the mapping between communication for automation in vertical domains and communication in 5G systems. |
22.819 | Feasibility Study on Maritime Communication Services over 3GPP system | TR | 16.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.819/22819-g20.zip | The present document aims to support the maritime communication services between users ashore and at sea or between vessels at sea over 3GPP system that are targeted to improve maritime safety, protect the maritime environment and promote the efficiency of shipping by reducing maritime casualty caused by human error, in particular, involving small ships and fishing vessels. In addition, the outcome of the technical report is expected to narrow the information gap between mobile users on land and shipboard users on vessels at sea by making it possible to provide the mobile broadband services.
The document describes use cases and potential requirements for services between shore-based users such as authorities and shipboard users in the maritime radio communication environment over 3GPP system. In addition, it deals with use cases to support Mission Critical Services between authorities on land and authorities at sea (e.g. maritime police) as well as use cases to support the interworking between 3GPP system and the existing/future maritime radio communication system for the seamless service of voice communication and data communication between users ashore and at sea or between vessels at sea.
Analysis is also made on which legacy services and requirements from the existing 3GPP system need to be included and which potential requirements need additional work for new functions to support maritime communication services over 3GPP system. |
22.821 | Feasibility Study on LAN Support in 5G | TR | 16.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.821/22821-g10.zip | The present document describes new use cases and potential requirements applicable to the 5G system for a 3GPP network operator to support 5G LAN-type services over the 5G system (i.e. UE, RAN, Core Network, and potential application to manage the LAN-style service). In this context, 5G LAN-type services with 5G capabilities (e.g. performance, long distance access, mobility, security) allow a restricted set of UEs to communicate amongst each other. |
22.822 | Study on using satellite access in 5G | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.822/22822-g00.zip | TS 22.261 (Service requirements for next generation new services and markets) requires that the 5G system shall be able to provide services using satellite access. It further specifies that the 5G system shall support service continuity between land based 5G access and satellite based access networks owned by the same operator or by an agreement between operators.
The present document presents the results of a study on using satellite access in 5G. Use cases for the provision of services when considering the integration of 5G satellite-based access components in the 5G system are identified. This leads to the associated identification of existing / planned, as well for new, services and the corresponding modified or new requirements. The requirements on set-up / configuration / maintenance of the features of UE’s when using satellite components combined with other components from the 5G system are addressed as well as regulatory requirements when moving to (or from) satellite from (or to) terrestrial networks |
22.823 | Study on enhancements to IMS for new real time communication services | TR | 16.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.823/22823-g10.zip | The present document aims to develop high-level use cases and identify the related potential requirements to enable IMS to support new real time communication services.
IMS enhancements for the following scenarios are studied in this document:
• one to many communication (e.g. live broadcast video service in a stadium, concert, etc.) with efficient media negotiation;
• interworking for a UE to communicate with non-sip devices (e.g. camera), and delivery of information to control functions of the non-sip devices (e.g. PTZ);
• fast IMS call setup time for Group Communication;
• enhancements on voice & video communications for supporting AR/VR;
• network slicing for IMS;
• service visibility and usage;.
• services using AI (voiceprint) in RTC. |
22.824 | Study on 5G message service for MIoT | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.824/22824-g00.zip | The present document develops use cases of message communication for MIoT, identifies 5G Message (5GMSG) service potential requirements, and identifies potential requirements on 5G system. The use cases include the following scenarios:
- Efficient message communication
- Low delay message communication
- Group message communication
- Multicast and broadcast message communication
- High density of UEs message communication
It also provides a gap analysis between the new requirements of message communication for MIoT and the existing operator’s message services/3GPP network capabilities, and recommends the future work for the standardization of 5GMSG service for MIoT. |
22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.825/22825-g00.zip | The present document identifies the use cases and documents the derived potential requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription. |
22.830 | Study on business role models for network slicing | TR | 16.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.830/22830-g10.zip | The present document examines the business role models for network slicing in order to identify potential requirements that will enable a 3GPP system to adequately support those models, including:
Business role models for network slicing,
Trust relationships between MNOs and 3rd parties under various business role models,
Security relationships based on business role models,
Relationship of business role models with slice characteristics (e.g., slice scalability, slice flexibility), and
3GPP enhancements needed to support the business role models for slices. |
22.833 | Study on Enhancement of LTE for Efficient delivery of Streaming Service | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.833/22833-g00.zip | The present document describes the use cases and provides gap analysis for identifying potential requirements for optimization of both Over-The-Top and operator managed streaming service considering new business models and existing well-known technologies e.g. caching (UE caching, in-network caching, internet CDN caching), content-aware service delivery, hybrid broadcast and unicast delivery, delay tolerate delivery (using the spare resource and/or delivery in non-busy time/hour), enhanced network sharing which covers the case that the streaming content is provided by shared RAN. |
22.854 | Feasibility Study on Multimedia Priority Service (MPS) Phase 2 | TR | 0.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.854/22854-050.zip | The present document studies voice, data transport, and video use cases and identifies potential requirements for Multimedia Priority Service (MPS). It identifies where updates are needed to TR 22.953[3] and TS 22.153 [2] to account for current and anticipated MPS User needs for priority voice, data, and video communication capabilities.
The present document provides use cases and the associated potential new stage 1 requirements beyond those documented in TR 22.953 [3]. Example use cases include:
• MPS for Voice: MPS for MMTEL voice and voice teleconferencing invoked from a subscribed UE, and MPS for MMTEL voice teleconferencing invoked from a voice server by the host,
• MPS for Data Transport Service (DTS): MPS DTS communications invoked from a subscribed UE, a subscribed IoT device, and from an enterprise network, and
• MPS for Video: MPS for MMTEL video, MMTEL video conferencing, and streaming video invoked from a subscribed UE and MPS for video teleconferencing invoked from a video server by the host.
The present document also include security considerations.
NOTE: Both MPS users and Mission Critical users can use common mechanisms defined in MCData and MCVideo for group-based communication with priority. However, both MPS and Mission Critical users have some unique requirements to also use an operator’s individual subscription-based commercial services (voice, video, data) with priority. |
22.866 | Enhanced relays for energy efficiency and extensive coverage | TR | 0.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.866/22866-030.zip | The present document examines several use cases with respective KPIs in different domains (e.g. inHome, SmartCities, SmartFarming, SmartFactories, Smart Energy, Public Safety, Logistics) and identifies new potential requirements for relays for energy efficiency and extensive coverage. |
22.869 | Feasibility study on enhancements of Public Warning System (PWS) | TR | 16.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.869/22869-g10.zip | The present document describes new use cases and potential requirements applicable to Public Warning Services for
- UEs with diverse form-factors whose user interface is different from the conventional mobile phones; and
- UEs that are defined by applying 3GPP system to non-ICT industry businesses (e.g. vehicles or machines such as IoT devices or robots) and have the different UE role from what 3GPP has traditionally assumed.
In addition, it considers the improvement of the understandability of the PWS message e.g. displaying language independent or graphical content to users, especially foreigners who might not understand the language used in the text or people with physical disability who may be sight impaired and unable to read the text. So it deals with user interface related potential requirements to address the presentation of the warning message considering circumstances such as language being used (e.g. international roaming scenario where the user does not understand the local language) or users with disability (e.g. people with vision impairment).
The present document does not cover use cases or potential requirements for US WEA and Japan ETWS so the results of this document are not applicable for US and Japan. This document considers national variants of EU-Alert and KPAS related service scenarios and potential requirements. |
22.872 | Study on positioning use cases | TR | 16.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.872/22872-g10.zip | This technical report relates to a study on positioning use cases for both outdoor and indoor environments. It analyses positioning use cases and complements existing work on 5G use cases involving positioning needs in order to identify potential requirements for 5G positioning services.
This document also identifies new use cases, their scope and environment of use along with the related KPIs. For use cases already addressed (fully or partially) in other 3GPP studies, it consolidates and validates the KPI and assumptions.
The document further develops the identified use cases by providing some considerations on the suitability of positioning technologies to these use cases. These considerations support the identification of potential requirements that can be achieved with 3GPP positioning technologies or with a combination of 3GPP and non-3GPP positioning technologies. The use cases and performance targets are independent of specific solutions even though, in order to support these considerations, the report provides some illustrative allocation between existing positioning technologies and 3GPP new positioning technologies (e.g. NR-based). |
22.886 | Study on enhancement of 3GPP support for 5G V2X services | TR | 16.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.886/22886-g20.zip | The objective of this document is to identify use cases and potential service requirements to enhance 3GPP support for V2X service in the following areas:
- Support for non-safety V2X services (also, referred to as "comfort service") (e.g. connected vehicle, mobile high data rate entertainment, mobile hot-spot/office/home, dynamic digital map update)
- Support for safety-related V2X services (e.g. autonomous driving, car platooning, priority handling between safety-related V2X services and other services)
- Support for V2X services in multiple 3GPP RATs (e.g. LTE, New RAT (NR)) and networks environment, including aspects such as interoperability with non-3GPP V2X technology (e.g. ITS-G5, DSRC, ITS-Connect)
In this document, V2X-related use cases and potential requirements already included in TR 22.891 are considered and new ones are introduced.
The identification of use cases and potential requirements covers both evolved LTE RAT and new 3GPP RAT (e.g. NR) and also covers V2X operation using 3GPP RATs where there are non-3GPP V2X technologies (e.g. ITS-G5, DSRC, ITS-Connect) in use. |
22.889 | Study on Future Railway Mobile Communication System (FRMCS) | TR | 16.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.889/22889-g60.zip | The present document analyses FRMCS Use cases, system principles of FRMCS and Interworking between GSM-R and FRMCS in order to derive potential requirements. |
22.903 | Study on Videotelephony teleservice | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-g00.zip | |
22.904 | Study on user-centric identifiers and authentication | TR | 16.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.904/22904-g10.zip | |
22.906 | Study on IMS based peer-to-peer content distribution services | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.906/22906-g00.zip | |
22.908 | Study on Paging Permission with Access Control (PPAC) | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-g00.zip | |
22.912 | Study into network selection requirements for non-3GPP access | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-g00.zip | |
22.936 | Multi-system terminals | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-g00.zip | |
22.940 | IP Multimedia Subsystem (IMS) messaging | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-g00.zip | |
22.942 | Study on Value Added Services (VAS) for Short Message Service (SMS) | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-g00.zip | |
22.944 | Report on service requirements for UE functionality split | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-g00.zip | |
22.947 | Study on Personal Broadcast Service (PBS) | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-g00.zip | |
22.948 | Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-g00.zip | |
22.949 | Study on a generalized privacy capability | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-g00.zip | |
22.950 | Priority service feasibility study | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-g00.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-g00.zip | |
22.952 | Priority service guide | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-g00.zip | |
22.953 | Multimedia priority service feasibility study | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-g00.zip | |
22.967 | Transferring of emergency call data | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-g00.zip | |
22.968 | Study for requirements for a Public Warning System (PWS) service | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-g00.zip | |
22.973 | IMS Multimedia Telephony service; and supplementary services | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-g00.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-g00.zip | |
22.978 | All-IP network (AIPN) feasibility study | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-g00.zip | |
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-g00.zip | |
22.980 | Network composition feasibility study | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-g00.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-g00.zip | |
22.983 | Services alignment and migration | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-g00.zip | |
22.985 | Service requirements for the User Data Convergence (UDC) | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-g00.zip | |
22.986 | Study on Service Specific Access Control | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-g00.zip | |
22.987 | Study of haptic services requirements | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.987/22987-g00.zip | |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 16.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-g00.zip | |
23.002 | Network architecture | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-g00.zip | |
23.003 | Numbering, addressing and identification | TS | 16.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-gc0.zip | |
23.007 | Restoration procedures | TS | 16.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-g10.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 | 16.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-g30.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.009 | Handover procedures | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-g00.zip | |
23.011 | Technical realization of Supplementary Services | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-g00.zip | |
23.012 | Location management procedures | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-g00.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-g00.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 16.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-g20.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.016 | Subscriber data management; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-g00.zip | |
23.018 | Basic call handling; Technical realization | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-g00.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 16.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-g00.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 16.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-g10.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-g00.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 16.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-g00.zip | |
23.038 | Alphabets and language-specific information | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-g00.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-g00.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 16.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-g40.zip | |
23.042 | Compression algorithm for text messaging services | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-g00.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 16.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-g00.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-g00.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-g00.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-g00.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-g00.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-g00.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-g00.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-g00.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-g00.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-g00.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-g00.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-g00.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-g00.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-g00.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-g00.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-g00.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-g00.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-g00.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-g00.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-g00.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-g00.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-g00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.