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 |
|---|---|---|---|---|---|---|
22.840 | Study on Ambient power-enabled Internet of Things | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.840/22840-j00.zip | The present document provides Stage 1 potential 5G service requirements for ambient power-enabled Internet of Things (i.e., Ambient IoT). In the context of the present document, an Ambient power-enabled IoT device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor) and the energy is provided through the harvesting of radio waves, light, motion, heat, or any other suitable power source. An ambient IoT device is expected to have lower complexity, smaller size and reduced capabilities and lower power consumption than previously defined 3GPP IoT devices (e.g., NB-IoT/eMTC devices). Ambient IoT devices can be maintenance free and can have long life span (e.g., more than 10 years).
The aspects addressed in the present document include:
• Study use cases of ambient power-enabled IoT and identify potential service requirements, including:
▪ Security aspects, e.g., authentication and authorization, etc.
▪ Network selection, access control, connection, mobility and identification management
▪ Charging (e.g., per data volume, per message)
▪ Aspects related to stakeholder models (e.g., involving interactions in PLMNs, NPNs or other parties)
▪ Positioning
▪ Aspects on device life cycle management related to 3GPP system.
• Study traffic scenarios, device constraints (e.g., power consumption) and identify potential performance requirements and KPIs
• Gap analysis between the identified requirements for ambient power-enabled IoT and what is already defined by existing 3GPP requirements.
Note: How Ambient IoT device performs energy harvesting is out of scope of this technical report. |
22.841 | Study on Upper layer traffic steering, switching and split over dual 3GPP access | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.841/22841-j00.zip | The scope of this TR is to document use cases, gap analysis and potential service requirements related to 5GS support of enhanced mechanisms for steering, splitting and switching of user data, pertaining to a UE data session, across two 3GPP networks. The following scenarios are covered, where only one single PLMN subscription is assumed:
• Single PLMN;
• PLMN and NPN;
• two PLMNs.
The two 3GPP networks may use same or different RAT, i.e. NR plus NR or E-UTRA, where NR RAT can be terrestrial or satellite NR access (including different staellite orbits, e.g., GEO/MEO/LEO).
For the PLMN plus PLMN / NPN scenarios, the two networks can be managed by the same operator or by different operators (assumed to have a business agreement among them). In both cases, it is assumed that a single PLMN subscription is used to access both networks (including the NPN).
Simultaneous connectivity over two 3GPP networks presumes UE support of proper capabilities (e.g., dual radio).
It is assumed that there are no impacts to normal inter-PLMN roaming scenarios.
Dual subscription scenarios are not in scope of this TR. |
22.843 | Study on on Additional capabilities of mobile networks for drone operations and managements | TR | 19.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.843/22843-j20.zip | The present document provides additional use cases of UAV and identifies potential requirements to improve 5G system’s support of UAV applications, UAV operations and management, including:
• Provide additional information to the UAV operator/USS to execute pre-flight preparations and inflight operation (e.g, flight mission application, flight path recommendation, flight monitoring and control);
• Use 5G system to support enhancing the UAV flight/route management based on network capacity and QoS information along the planned route;
• Use 5G system to further enhance the safety and security of UAV operations, e.g. supporting UTM in UAV detection and DAA (Detect and Avoid);
• Identify potential new security, charging and regulatory requirements on 5GS, when used for UAS operation;
• Identify potential new requirements related to redundancy and reliability of command and control (C2) traffic for UAV.
For the identified use cases, a gap analysis is performed between potential new service requirements and existing 3GPP requirements and functionalities.
NOTE: This study investigates requirements for additional 5GS capabilities to assist UTM, with the assumption that liability and responsibility for UAV operation remain under the domain of the UTM/UAV operator.
NOTE: Potential overlaps with ongoing stage-2 work (on UAS), and other SA1 studies (e.g. FS_Sensing) have been considered and avoided. |
22.848 | Feasibility Study on Interconnect of SNPN | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.848/22848-j00.zip | The present document describes use cases and aspects related to interconnect of SNPNs as well as Scalable SNPN Interconnect with dynamic connections.
Potential service requirements are derived for these use cases and are consolidated in a dedicated chapter.
The report ends with recommendations regarding the continuation of the work.
NOTE: There is no requirement for a PLMN to enhance their interconnect with SNPNs or operate an identity provider. |
22.850 | Study on 3GPP AI/ML Consistency Alignment | TR | 19.0.0 | SP | https://www.3gpp.org/ftp/Specs/archive/22_series/22.850/22850-j00.zip | |
22.851 | Study on Network Sharing Aspects | TR | 19.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.851/22851-j10.zip | The present document investigates use cases and potential new requirements related to 3GPP system enhanced support of specific 5G network sharing deployment scenarios, in particular where there is no direct interconnection between the shared NG-RAN and participating operators’ core networks. It includes the following aspects:
- Mobility and service continuity, e.g., when moving from a non-shared 4G/5G network to a shared 5G network and vice versa, with focus on CN aspects.
- Potential security requirements.
- Charging requirements (e.g., based on traffic differentiation in specific network sharing geographical areas).
- User/service experience (e.g., maintain the communication latency for voice, and SMS) when accessing the shared network, including scenarios of home-routed traffic or local breakout.
- Other aspects, e.g., regulatory requirements, emergency services, PWS support. |
22.856 | Study on Localized Mobile Metaverse Services | TR | 19.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.856/22856-j20.zip | The present document investigates specific use cases and service requirements for 5GS support of enhanced XR-based services, (as XR-based services are an essential part of "Metaverse" services considered in this study,) as well as potentially other functionality, to offer shared and interactive user experience of local content and services, accessed either by users in the proximity or remotely. In particular, the following areas are studied:
- Support of interactive XR media shared among multiple users in a single location, including:
- performance (KPI) aspects; e.g. latency, throughput, connection density
- efficiency and scalability aspects, for large numbers of users in a single location.
- the combination of haptics type of XR media and other non-haptics types of XR media.
- Identification of users and other digital representations of entities interacting within the Metaverse service.
- Acquisition, use and exposure of local (physical and digital) information to enable Metaverse services, including:
- acquiring local spatial/environmental information and user/UE(s) information (including viewing angle, position and direction);
- exposing local acquired spatial, environmental and user/UE information to 3rd parties to enable Metaverse services.
- Other aspects, such as privacy, charging, public safety and security requirements.
The study also investigates gaps between the identified new potential requirements and the requirements already specified for the 5G system.
It is acknowledged that there are activities related to the topic Metaverse outside of 3GPP, such as the W3C Open Metaverse Interoperability Group (OMI). These activities may be considered in the form of use cases and related contributions to this study, but there is no specific objective for this study to consider or align with external standardization activities.
A difference between this study and TR 22.847 " Study on supporting tactile and multi-modality communication services" is that Metaverse services would involve coordination of input data from different devices/sensors from different users and coordination of output data to different devices at different destinations to support the same task or application. |
22.865 | Study on satellite access - Phase 3 | TR | 19.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.865/22865-j20.zip | The present document describes use cases and aspects related to enhancements of the 5G system over satellite, including:
• Store and Forward (S&F) Satellite operation for delay-tolerant communication service
• UE-Satellite-UE communication
• GNSS independent operation
• Positioning enhancements for satellite access
Potential service requirements are derived for these use cases and are consolidated in a dedicated chapter.
The report ends with recommendations regarding the continuation of the work. |
22.876 | Study on AI/ML Model Transfer Phase2 | TR | 19.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.876/22876-j10.zip | The objective of this document is to study the use cases with potential functional and performance requirements to support efficient AI/ML operations using direct device connection for various applications e.g. auto-driving, robot remote control, video recognition, etc.
The aspects addressed in the document includes:
- Identify the use cases for distributed AI inference;
- Identify the use cases for distributed/decentralized model training;
- Gap analysis to existing 5GS mechanism to support the distributed AI inference and model training. |
22.877 | Study on roaming value added services | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.877/22877-j00.zip | The present document describes use cases related to the following three Roaming Value-Added Services (RVAS) that are enabled by the PLMN for 5GS roaming:
• Welcome SMS
• Steering of Roaming (SoR) during the registration procedure
• Subscription-based routing to a particular core network (e.g., in a different country)
Potential requirements are derived for these three services and consolidated in a dedicated chapter. The report ends with recommendation regarding the continuation of the work.
NOTE: This document is not expected to introduce any changes to the security mechanisms between operators, and responsible groups will verify that 5GS security mechanisms are not negatively impacted by these requirements. |
22.882 | Study on Energy Efficiency as service criteria | TR | 19.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.882/22882-j30.zip | The present document provides stage 1 use cases and potential 5G requirements on the following aspects regarding enhancements to Energy Efficiency of 5G network and application service enabler aspects:
- Defining and supporting energy efficiency criteria as part of communication service to user and application services;
- Supporting information exposure of systematic energy consumption or level of energy efficiency to vertical customers;
- Gap analysis between the identified potential requirements and existing 5GS requirements or functionalities;
- Potential requirements on security, charging and privacy aspects. |
22.890 | Study on supporting railway smart station services | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.890/22890-j00.zip | The present document analyses use cases of smart railway station such as station operation monitoring and control, passenger supporting services and evolution use cases of business and performance applications currently included in TR22.989 in order to derive potential requirements. |
22.903 | Study on Videotelephony teleservice | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-j00.zip | |
22.904 | Study on user-centric identifiers and authentication | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.904/22904-j00.zip | |
22.906 | Study on IMS based peer-to-peer content distribution services | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.906/22906-j00.zip | |
22.908 | Study on Paging Permission with Access Control (PPAC) | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-j00.zip | |
22.912 | Study into network selection requirements for non-3GPP access | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-j00.zip | |
22.916 | Study on Network of Service Robots with Ambient Intelligence | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.916/22916-j00.zip | The present document describes use cases and aspects related to efficient communications service and cooperative operation for a group of service robots including:
◦ exposure of information between application layer and communications layer;
◦ support of on-demand high priority communications;
◦ KPIs for large-scale group operation scenarios;
◦ support of scalable and efficient use of communication resources;
◦ requirements related to media applications specific for service robots; and
◦ aspects related to security, privacy and charging
that are relevant to support stable operation of service robots. This document also describes the existing service requirements and potential correlation with other studies. |
22.926 | Guidelines for extraterritorial 5G Systems (5GS) | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.926/22926-j00.zip | |
22.936 | Multi-system terminals | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-j00.zip | |
22.940 | IP Multimedia Subsystem (IMS) messaging | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-j00.zip | |
22.942 | Study on Value Added Services (VAS) for Short Message Service (SMS) | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-j00.zip | |
22.944 | Report on service requirements for UE functionality split | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-j00.zip | |
22.948 | Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-j00.zip | |
22.947 | Study on Personal Broadcast Service (PBS) | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-j00.zip | |
22.949 | Study on a generalized privacy capability | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-j00.zip | |
22.950 | Priority service feasibility study | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-j00.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-j00.zip | |
22.952 | Priority service guide | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-j00.zip | |
22.953 | Multimedia priority service feasibility study | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-j00.zip | |
22.967 | Transferring of emergency call data | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-j00.zip | |
22.968 | Study for requirements for a Public Warning System (PWS) service | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-j00.zip | |
22.973 | IMS Multimedia Telephony service; and supplementary services | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-j00.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-j00.zip | |
22.978 | All-IP network (AIPN) feasibility study | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-j00.zip | |
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-j00.zip | |
22.980 | Network composition feasibility study | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-j00.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-j00.zip | |
22.983 | Services alignment and migration | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-j00.zip | |
22.985 | Service requirements for the User Data Convergence (UDC) | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-j00.zip | |
22.986 | Study on Service Specific Access Control | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-j00.zip | |
22.987 | Study of haptic services requirements | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.987/22987-j00.zip | |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-j00.zip | |
22.989 | Study on Future Railway Mobile Communication System | TR | 19.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.989/22989-j40.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.990 | Study on off-network for rail | TR | 19.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.990/22990-j00.zip | |
23.002 | Network architecture | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-j00.zip | |
23.003 | Numbering, addressing and identification | TS | 19.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-j50.zip | |
23.007 | Restoration procedures | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-j20.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 | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-j00.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 | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-j00.zip | |
23.011 | Technical realization of Supplementary Services | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-j00.zip | |
23.012 | Location management procedures | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-j00.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-j00.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-j00.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 | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-j00.zip | |
23.018 | Basic call handling; Technical realization | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-j00.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 19.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-j00.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-j00.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-j00.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 19.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-j00.zip | |
23.038 | Alphabets and language-specific information | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-j00.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-j00.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-j30.zip | |
23.042 | Compression algorithm for text messaging services | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-j00.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-j00.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-j00.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-j00.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-j00.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-j00.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-j00.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-j00.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-j00.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-j00.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-j00.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-j00.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-j00.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-j00.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-j00.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-j00.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-j00.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-j00.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-j00.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-j00.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-j00.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-j00.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-j00.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-j00.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-j00.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-j00.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-j00.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-j00.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-j00.zip | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 19.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-j50.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-j00.zip | |
23.139 | 3GPP system - fixed broadband access network interworking; Stage 2 | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.139/23139-j00.zip | |
23.141 | Presence service; Architecture and functional description | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-j00.zip | |
23.142 | Value-added Services for SMS (VAS4SMS); Interface and signalling flow | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-j00.zip | |
23.146 | Technical realization of facsimile Group 3 non-transparent | TS | 19.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-j00.zip | |
23.153 | Out of band transcoder control; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-j00.zip | |
23.161 | Network-Based IP Flow Mobility (NBIFOM); Stage 2 | TS | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.161/23161-j00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.