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.280 | Mission Critical Services Common Requirements (MCCoRe); Stage 1 | TS | 17.7.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.280/22280-h70.zip | |
22.281 | Mission Critical (MC) video | TS | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.281/22281-h00.zip | |
22.282 | Mission Critical (MC) data | TS | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.282/22282-h00.zip | |
22.289 | Mobile communication system for railways | TS | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.289/22289-h00.zip | |
22.340 | IP Multimedia Subsystem (IMS) messaging; Stage 1 | TS | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.340/22340-h00.zip | |
22.346 | Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1 | TS | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.346/22346-h00.zip | |
22.368 | Service requirements for Machine-Type Communications (MTC); Stage 1 | TS | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.368/22368-h00.zip | |
22.468 | Group Communication System Enablers (GCSE) | TS | 17.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.468/22468-h01.zip | |
22.519 | Business communication requirements | TS | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.519/22519-h00.zip | |
22.826 | Study on communication services for critical medical applications | TR | 17.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.826/22826-h20.zip | The present document focuses on 5G communication services targeting the critical medical applications and enabling wireless connectivity between those applications and medical devices.
Those communication services are often submitted to (but not limited to) very low latency, high reliability, and high availability requirements and may be operated on a shared network infrastructure that also provides resources to other less demanding communication services. |
22.827 | Study on Audio-Visual Service Production | TR | 17.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.827/22827-h10.zip | This Technical Report describes relevant use-cases and proposes respective potential service requirements for 5G systems to support production of audio-visual (AV) content and services.
Previous work assessed certain aspects for local applications (e.g. ultra-reliable low-latency and time synchronization demands.) This study addresses implications for 3GPP from wide-area media production and additional local applications. Topics to be studied include demanding locally-distributed production scenarios or ad-hoc deployments of high-bandwidth networks providing increased mobility and coverage and lowest streaming latencies.
Investigation is considered for example:
- provision of pre-defined bandwidth capacity, end-to-end latency and other QoS requirements for e.g. larger live music events or high-quality cinematic video production;
- time synchronisation among all devices (cameras, microphones, in-ear monitors etc.), optionally using a production-based master clock or time code generator, which is broadcasted;
- coverage-related issues dealing with nomadic and ad-hoc production deployments, future ways for electronic news gathering, usage of airborne equipment and support for higher ground speeds of up to 400 km/h;
- interoperability issues related to existing audio-visual production standards and protocols;
- dependability assurance and related topics (network isolation, QoS monitoring etc.). |
22.829 | Enhancement for Unmaned Aerial Vehicles (UAVs) | TR | 17.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.829/22829-h10.zip | The present document provides use cases and analysis of UAV capabilities that may require enhanced 3GPP support. |
22.831 | Study on Support for Minimization of service Interruption | TR | 17.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.831/22831-h10.zip | The present document concerns the possibility of minimizing service interruption when it occurs. This technical report gathers and analyses scenarios in which interruption to communication service arises to derive potential service requirements out of these scenarios. The study will address applicable local regulatory requirements. Gaps between what can be supported by the 3GPP system and the derived potential service requirements will be identified. |
22.832 | Study on enhancements for cyber-physical control applications in vertical domains | TR | 17.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.832/22832-h40.zip | The present document identifies further Stage 1 potential 5G service requirements for cyber-physical control applications in vertical domains.
The present document provides specific use cases to provide clarity and to motivate the additional service requirements. Relative to the Rel-16 baseline, there are more specific requirements or additional requirements for closely-related additional functionality in order to improve the applicability of 5G systems to vertical domains.
The aspects addressed are:
- Industrial Ethernet integration, which includes time synchronization, different time domains, integration scenarios, and support for time-sensitive networking (TSN);
- Non-public networks, non-public networks as private slices, and further implications on security for non-public networks;
- Network operation and Maintenance in 5G non-public networks for cyber-physical control applications in vertical domains; Enhanced QoS monitoring, communication service and networks diagnostics; Communication service interface between application and 5G systems, e.g. information to the network for setting up communication services for cyber-physical control applications and corresponding monitoring;
- Network performance requirements for cyber-physical control applications in vertical domains;
- Positioning with focus on the vertical dimension for Industrial IoT;
- Device-to-device/ProSe communication for cyber-physical applications in vertical domains. |
22.834 | Study on support for devices with multiple Universal Subscriber Identity Modules (USIMs) | TR | 17.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.834/22834-h20.zip | The present document examines several use cases in support of UE with multiple USIMs (MUSIM UE) provided by same or different MNOs and identifies new potential service requirements for emergency services and normal services among USIMs. |
22.836 | Study on asset tracking use cases | TR | 17.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.836/22836-h10.zip | The present document describes asset tracking use cases and identifies new potential service requirements as well as new KPIs to be supported by 5G communication services for asset tracking. |
22.842 | Study on Network Controlled Interactive Service (NCIS) in the 5G System (5GS) | TR | 17.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.842/22842-h20.zip | With the expectation that 5G consumer UEs, existing or some new form devices (e.g. VR/AR devices, robot, etc.) being used for different use cases in a number of different environments, e.g. entertainment in home party or bar, or education in office, becomes interested for supporting data sharing and data exchanging between users, thus, it is necessary to investigate new use cases and requirements, like lower latency, higher throughput, higher reliability, higher resource/power efficiency etc, for such interactive services.
The objective of this TR is to study the use cases and to derive potential service requirements to provide users with interactive services, including:
- New use cases and new requirements for Interactive Services
- Gap Analyses between requirements and existing eMBB service requirements / existing ProSe requirements
- After the use cases have been identified, service requirements and KPIs will be studied including QoS, operator control, charging, etc. |
22.854 | Feasibility Study on Multimedia Priority Service (MPS) Phase 2 | TR | 17.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.854/22854-h10.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 | 17.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.866/22866-h10.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.873 | Study on evolution of the IP Multimedia Subsystem (IMS) multimedia telephony service | TR | 0.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.873/22873-060.zip | The present document studies new scenarios (e.g. AR/VR communication) for IMS Multimedia Telephony service, identifies potential service requirements, and identifies additional potential requirements on 5G system.
This document also does a gap analysis to existing requirements in 3GPP to identify potential requirements for introduction into 3GPP.
NOTE: Use cases in this document have references to those already specified in 3GPP TR26.918 [2] and TR26.928[3]. This allows an easier breakdown of these use cases to existing features and potential new requirements as well as relevant performance figures. New use cases in this TR are highlighted if they are not covered in 3GPP SA4 work. |
22.881 | Study on sharing administrative configuration information between interconnected Mission Critical (MCX) service systems | TR | 0.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.881/22881-050.zip | The present document studies use cases that assess under which circumstances interconnected MCX Service Systems exchange administrative and security relevant data and information.
Its objective is to identify new potential requirements related to the use cases and new high-level security requirements related to interconnection of MCX Service Systems and migration of MCX Users and MCX Service Groups. |
22.889 | Study on Future Railway Mobile Communication System (FRMCS) | TR | 17.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.889/22889-h40.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 | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-h00.zip | |
22.904 | Study on user-centric identifiers and authentication | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.904/22904-h00.zip | |
22.906 | Study on IMS based peer-to-peer content distribution services | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.906/22906-h00.zip | |
22.908 | Study on Paging Permission with Access Control (PPAC) | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-h00.zip | |
22.912 | Study into network selection requirements for non-3GPP access | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-h00.zip | |
22.936 | Multi-system terminals | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-h00.zip | |
22.940 | IP Multimedia Subsystem (IMS) messaging | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-h00.zip | |
22.942 | Study on Value Added Services (VAS) for Short Message Service (SMS) | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-h00.zip | |
22.944 | Report on service requirements for UE functionality split | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-h00.zip | |
22.947 | Study on Personal Broadcast Service (PBS) | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-h00.zip | |
22.948 | Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-h00.zip | |
22.949 | Study on a generalized privacy capability | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-h00.zip | |
22.950 | Priority service feasibility study | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-h00.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-h00.zip | |
22.952 | Priority service guide | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-h00.zip | |
22.953 | Multimedia priority service feasibility study | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-h00.zip | |
22.967 | Transferring of emergency call data | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-h00.zip | |
22.968 | Study for requirements for a Public Warning System (PWS) service | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-h00.zip | |
22.973 | IMS Multimedia Telephony service; and supplementary services | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-h00.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-h00.zip | |
22.978 | All-IP network (AIPN) feasibility study | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-h00.zip | |
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-h00.zip | |
22.980 | Network composition feasibility study | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-h00.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-h00.zip | |
22.983 | Services alignment and migration | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-h00.zip | |
22.985 | Service requirements for the User Data Convergence (UDC) | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-h00.zip | |
22.986 | Study on Service Specific Access Control | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-h00.zip | |
22.987 | Study of haptic services requirements | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.987/22987-h00.zip | |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 17.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-h00.zip | |
23.002 | Network architecture | TS | 17.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-h00.zip | |
23.003 | Numbering, addressing and identification | TS | 17.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-ha0.zip | |
23.007 | Restoration procedures | TS | 17.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-h70.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 | 17.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-h10.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 | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-h00.zip | |
23.011 | Technical realization of Supplementary Services | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-h00.zip | |
23.012 | Location management procedures | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-h00.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 17.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-h00.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 17.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-h10.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 | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-h00.zip | |
23.018 | Basic call handling; Technical realization | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-h00.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-h00.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 17.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-h20.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 17.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-h00.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 17.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-h00.zip | |
23.038 | Alphabets and language-specific information | TS | 17.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-h00.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 17.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-h30.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 17.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-h50.zip | |
23.042 | Compression algorithm for text messaging services | TS | 17.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-h00.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 17.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-h00.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 17.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-h00.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 17.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-h00.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-h00.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-h00.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-h00.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-h00.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-h00.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-h00.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-h00.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-h00.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-h00.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-h00.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-h00.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-h00.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-h00.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-h00.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-h00.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-h00.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-h00.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-h00.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-h00.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 17.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-h00.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 17.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-h00.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 17.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-h00.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 17.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-h00.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-h00.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-h00.zip | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 17.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-ha0.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 17.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-h00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.