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.240 | Service requirements for 3GPP Generic User Profile (GUP); Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.240/22240-e00.zip | |
22.233 | Transparent end-to-end packet-switched streaming service; Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.233/22233-e00.zip | |
22.246 | Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.246/22246-e00.zip | |
22.242 | Digital Rights Management (DRM); Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.242/22242-e00.zip | |
22.243 | Speech recognition framework for automated voice services; Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.243/22243-e00.zip | |
22.250 | IP Multimedia Subsystem (IMS) Group Management; Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.250/22250-e00.zip | |
22.268 | Public Warning System (PWS) requirements | TS | 14.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.268/22268-e10.zip | |
22.259 | Service requirements for Personal Network Management (PNM); Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.259/22259-e00.zip | |
22.278 | Service requirements for the Evolved Packet System (EPS) | TS | 14.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.278/22278-e60.zip | |
22.279 | Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.279/22279-e00.zip | |
22.280 | Mission Critical Services Common Requirements (MCCoRe); Stage 1 | TS | 14.3.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.280/22280-e31.zip | |
22.281 | Mission Critical (MC) video | TS | 14.4.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.281/22281-e41.zip | |
22.282 | Mission Critical (MC) data | TS | 14.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.282/22282-e30.zip | |
22.340 | IP Multimedia Subsystem (IMS) messaging; Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.340/22340-e00.zip | |
22.468 | Group Communication System Enablers (GCSE) | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.468/22468-e00.zip | |
22.519 | Business communication requirements | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.519/22519-e00.zip | |
22.802 | Study on scenarios where multiple APNs are needed | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.802/22802-e00.zip | The scope of this study is:
- to provide details about the use cases where there is a need of control of APNs;
- to identify potential new requirements to fulfil the use cases;
- to identify potential solutions to fulfil the use cases;
The scope of the study is focussed on Machine-To-Machine UEs but can take into account a more generic set of UEs.
This study will identify what connectivity use-cases that are needed to be fulfilled, and study if multiple APN or a multi-purpose APN per subscription (IMSI) combined with other 3GPP specified features can support those connectivity use-cases. The study will also analyse the impacts in scenarios where the service provider decides to change the MNO. |
22.808 | Study on Flexible Mobile Service Steering (FMSS) | TR | 14.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.808/22808-e10.zip | The objective is to study use cases and propose potential requirements for supporting traffic classification and service chain selection capabilities per operator's policy (e.g. based on user's profile, application type, RAN type, RAN status and flow direction) in order to realize efficient and flexible mobile service steering in the (S)Gi-LAN network. |
22.815 | Study on Multimedia Broadcast Supplement for Public Warning System (MBSP) | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.815/22815-e00.zip | This TR considers enhancements to 3GPP PWS via the addition of multimedia broadcast capability. The use cases for this capability are documented and derived requirements are gathered and consolidated. This TR does not cover use cases or potential requirements for specific PWS based systems (i.e. ETWS, CMAS, EU-ALERT, and Korean Public Alert System).
This TR covers:
- Scenarios and use cases to provide multi-media information supplemental to PWS;
- UE awareness of, and ability to receive, multi-media information via PWS;
- Handling of UEs in limited service mode;
- Priority of multimedia information |
22.816 | 3GPP enhancement for TV service | TR | 14.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.816/22816-e10.zip | This Technical Report describes use cases, proposes assumptions and potential requirements and analyzes the gap in order to enhance 3GPP system for TV service support. The supported TV service includes linear TV, Live, Video on Demand, smart TV, and Over The Top (OTT) content. |
22.368 | Service requirements for Machine-Type Communications (MTC); Stage 1 | TS | 14.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.368/22368-e01.zip | |
22.818 | Feasibility Study on Control of Applications when Third party Servers encounter difficulties | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.818/22818-e00.zip | With the spread of applications on UEs (also known as "smart phones"), coupled with the rapidly growing number of UEs designed for usage with little or no human involvement (machine type communications), the potential for issues to occur in the overall "system" involving these applications and the third party entities they interact with increases. When these third party entities experience difficulties, they may be able to manage their problems without undue impact on operator networks, but there will be times when they are not able to do so.
When a third party server becomes congested or fails, the communication by the UE applications that make use of that server need to be controlled so that excessive use of 3GPP network resources is avoided while not affecting other applications and their associated servers that are functioning normally.
The 3GPP network needs to be able to detect or receive an indication from a third party server of its congestion status or failure status and control UE applications (or their traffic in the 3GPP network) that make use of a third party server that has encountered difficulties. HTTP and other third party (possibly proprietary) protocols can have status codes but these can be insufficient as they cannot provide a suitable indication to the UE application of the nature of the issue and therefore could result in frequent retries even when these will fail, thus burdening the network with connection attempts that will fail.
The present document identifies potential requirements that will enable the 3GPP network to detect or receive an indication from a third party server of its congestion status or failure status and control the traffic of individual UE applications (or their traffic in the 3GPP network) when the 3GPP network becomes aware that a third party server has run into difficulties. This will make it possible to
- Reduce or avoid unproductive traffic in 3GPP network (i.e., traffic that the 3rd party server is not able to receive) by blocking it either in the UE or in the 3GPP network (primary objective)
- Allow 3GPP network to help 3rd party servers to handle overload and recover from failures (secondary objective) |
22.861 | Massive Internet of Things | TR | 14.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.861/22861-e10.zip | Emerging from the FS_SMARTER work [2], the present document aims to identify and document the key families of use cases and their consolidated potential requirements, and to capture desired system requirements and capabilities to support the needs of new services and markets related to massive Internet of Things.
The focus of this work is on the use cases and requirements that cannot be met with EPS. |
22.838 | Paging policy enhancements and procedure optimizations in LTE | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.838/22838-e00.zip | The objective is to study use cases and propose potential requirements to enhance the information set (e.g., user’s subscription, application characteristics) upon which paging policies may be based to allow optimization of the paging procedures in LTE. |
22.862 | Feasibility study on new services and markets technology enablers for critical communications; Stage 1 | TR | 14.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.862/22862-e10.zip | The present document covers Critical Communications. The main areas where the 3GPP system falls short in meeting the requirements of Critical Communications is latency, reliability, and availability. These requirements can be met with an improved radio interface, optimised architecture, and dedicated core and radio resources. Other requirements having emerged in 3GPP TR 22.891 [2], such, as, high bandwidth, high connection density, low complexity, low power consumption, and massive number of devices, are often irrelevant for Critical Communications. |
22.346 | Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1 | TS | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.346/22346-e00.zip | |
22.863 | Feasibility study on new services and markets technology enablers for enhanced mobile broadband; Stage 1 | TR | 14.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.863/22863-e10.zip | Emerging from the FS_SMARTER work [2], the present document aims to identify and document the use cases and consolidated potential requirements, and to capture desired system requirements and capabilities to enable 3GPP network operators to support the needs of enhanced mobile Broadband.
The focus of this work is on the use cases and requirements that cannot be met with EPS. |
22.820 | Study on Provision of Local Operator Services | TR | 0.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.820/22820-010.zip | The present document describes the use cases and potential requirements for an optional capability allowing an operator to provide access to restricted local operator services. Based on operator policy, access to these restricted local operator services is allowed for unauthenticated UEs. In such cases, the unauthenticated UE is restricted to only accessing a restricted local operator service. Any other access attempts by the UE are subject to normal 3GPP processing, including authentication. |
22.864 | Feasibility study on new services and markets technology enablers for network operation; Stage 1 | TR | 14.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.864/22864-e10.zip | Emerging from the FS_SMARTER work [2], the present document aims to identify and document the key families of use cases and their consolidated potential requirements, and to capture desired system requirements and capabilities to enable 3GPP network operators to support the needs of new scenarios and markets related to network operation.
The focus of this work is on the use cases and requirements that cannot be met with EPS. |
22.880 | Feasibility study on Mission Critical (MC) data communications | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.880/22880-e00.zip | The present document studies use cases and identifies potential requirements for operation of the MCData service. MCData makes use of capabilities included in Group Communications System Enablers for LTE (GCSE_LTE), Proximity based Services (ProSe), and Isolated E-UTRAN Operation for Public Safety (IOPS) with additional requirements specific to the MCData Service. The MCData Service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
As far as possible, the MCData service will reuse applicable elements from the MCPTT service. |
22.885 | Study on LTE support for Vehicle-to-Everything (V2X) services | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.885/22885-e00.zip | The objective of this TR is to identify use cases and associated potential requirements for LTE support of V2X services taking into account V2X Services and parameters defined in other SDOs (e.g. GSMA Connected Living, ETSI ITS (Intelligent Transportation System), US SAE) or related governmental agency (e.g. C-ITS project in Korean Ministry of Land, Infrastructure and Transport). The essential use cases for LTE V2X (V2V, V2I, and V2P) to be studied and requirements identified are as follows;
- V2V: covering LTE-based communication between vehicles.
- V2P: covering LTE-based communication between a vehicle and a device carried by an individual (e.g. handheld terminal carried by a pedestrian, cyclist, driver or passenger).
- V2I: covering LTE-based communication between a vehicle and a roadside unit.
This TR includes safety and non-safety aspects. |
22.879 | Feasibility study on Mission Critical (MC) video services over LTE | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.879/22879-e00.zip | The present document studies use cases and identifies potential requirements for operation of the MCVideo Service. MCVideo makes use of capabilities included in Group Communications System Enablers for LTE (GCSE_LTE), Proximity based Services (ProSe), and Isolated E-UTRAN operation for Public Safety, with additional requirements specific to the MCVideo Service. The MCVideo Service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
As far as possible, the MCVideo service will reuse applicable elements from MCPTT service. |
22.898 | Study on user control dver spoofed calls | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.898/22898-e00.zip | The present document studies new service capabilities and enhancements to existing service capabilities needed to allow the called user to control:
- How spoofed calls are reported to the called user.
- The treatment given to the spoofed call and calling user.
- Provide the called user the ability to review the results of spoofed call detection.
- Allow the called user to provide feedback to the network of incorrect detection decisions (false positive and false negative).
New service network capabilities and enhancements to existing network capabilities needed to support network operator policies regarding treatment of spoofed calls are also covered including:
- Support for law enforcement and network operator fraud investigations into originators of spoofed calls.
- Setting default or limiting spoofed call controls the user is able to access.
The present document also studies the interaction between spoofed call control capabilities available to users using MTSI voice services. |
22.891 | Study on new services and markets technology enablers | TR | 14.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.891/22891-e20.zip | |
22.903 | Study on Videotelephony teleservice | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-e00.zip | |
22.906 | Study on IMS based peer-to-peer content distribution services | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.906/22906-e00.zip | |
22.936 | Multi-system terminals | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-e00.zip | |
22.940 | IP Multimedia Subsystem (IMS) messaging | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-e00.zip | |
22.942 | Study on Value Added Services (VAS) for Short Message Service (SMS) | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-e00.zip | |
22.944 | Report on service requirements for UE functionality split | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-e00.zip | |
22.947 | Study on Personal Broadcast Service (PBS) | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-e00.zip | |
22.899 | Study on enhancements to user location reporting support | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.899/22899-e00.zip | |
22.912 | Study into network selection requirements for non-3GPP access | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-e00.zip | |
22.950 | Priority service feasibility study | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-e00.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-e00.zip | |
22.952 | Priority service guide | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-e00.zip | |
22.953 | Multimedia priority service feasibility study | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-e00.zip | |
22.967 | Transferring of emergency call data | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-e00.zip | |
22.968 | Study for requirements for a Public Warning System (PWS) service | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-e00.zip | |
22.973 | IMS Multimedia Telephony service; and supplementary services | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-e00.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-e00.zip | |
22.948 | Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-e00.zip | |
22.978 | All-IP network (AIPN) feasibility study | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-e00.zip | |
22.949 | Study on a generalized privacy capability | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-e00.zip | |
22.980 | Network composition feasibility study | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-e00.zip | |
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-e00.zip | |
22.908 | Study on Paging Permission with Access Control (PPAC) | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-e00.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-e00.zip | |
22.983 | Services alignment and migration | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-e00.zip | |
22.987 | Study of haptic services requirements | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.987/22987-e00.zip | |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-e00.zip | |
22.986 | Study on Service Specific Access Control | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-e00.zip | |
23.002 | Network architecture | TS | 14.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-e10.zip | |
22.985 | Service requirements for the User Data Convergence (UDC) | TR | 14.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-e00.zip | |
23.003 | Numbering, addressing and identification | TS | 14.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-e70.zip | |
23.007 | Restoration procedures | TS | 14.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-e60.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.009 | Handover procedures | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-e00.zip | |
23.008 | Organization of subscriber data | TS | 14.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-e40.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.011 | Technical realization of Supplementary Services | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-e00.zip | |
23.012 | Location management procedures | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-e00.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-e00.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 | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-e00.zip | |
23.018 | Basic call handling; Technical realization | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-e00.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-e00.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 14.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-e00.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 14.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-e10.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 14.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-e00.zip | |
23.038 | Alphabets and language-specific information | TS | 14.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-e00.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 14.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-e10.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 14.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-e20.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 14.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-e00.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 14.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-e00.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 14.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-e00.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 14.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-e80.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-e00.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-e00.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-e00.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-e00.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-e00.zip | |
23.042 | Compression algorithm for text messaging services | TS | 14.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-e00.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-e00.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-e00.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-e00.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-e00.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-e00.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-e00.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-e00.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-e00.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-e00.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 14.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-e00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.