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.081 | Line Identification supplementary services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.081/22081-900.zip | |
22.082 | Call Forwarding (CF) Supplementary Services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.082/22082-900.zip | |
22.083 | Call Waiting (CW) and Call Holding (HOLD); Supplementary Services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.083/22083-900.zip | |
21.902 | Evolution of 3GPP system | TR | 9.0.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.902/21902-900.zip | The present document describes a long term, high level roadmap, intended to guide the future work of 3GPP. It is focussed on items pertinent to the evolution of 3GPP specifications, and identifies concepts and trends to be considered by 3GPP when defining future work items. It does not contain details of proposed technologies, rather it contains pointers to direct the activities of the appropriate TSGs in elaborating future releases of the 3GPP standard. As a result, not all of the topics covered herein are within the remit of 3GPP to discuss, and description of such items will not be extensively developed. E.g. Spectrum is an ITU-R/WRC issue and therefore outside the scope of 3GPP. The document is designed to be a "living document" and will be updated accordingly over its lifetime in order to reflect future developments and innovations. |
22.086 | Advice of Charge (AoC) supplementary services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.086/22086-900.zip | |
22.087 | User-to-User Signalling (UUS); Service description; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.087/22087-900.zip | |
22.085 | Closed User Group (CUG) supplementary services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.085/22085-900.zip | |
22.084 | MultiParty (MPTY) supplementary service; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.084/22084-900.zip | |
21.900 | Technical Specification Group working methods | TR | 9.1.0 | SP | https://www.3gpp.org/ftp/Specs/archive/21_series/21.900/21900-910.zip | |
22.090 | Unstructured Supplementary Service Data (USSD); Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.090/22090-900.zip | |
22.094 | Follow Me service description; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.094/22094-900.zip | |
22.076 | Noise suppression for the AMR codec; Service description; Stage 1 | TS | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.076/22076-900.zip | |
22.096 | Name identification supplementary services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.096/22096-900.zip | |
22.097 | Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.097/22097-900.zip | |
22.101 | Service aspects; Service principles | TS | 9.13.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.101/22101-9d0.zip | This Technical Specification (TS) describes the Service Principles for PLMNs specified by 3GPP. Principles and requirements for interworking with WLAN are covered in TS 22.234 [35].
3GPP specifications provide integrated personal communications services. The system will support different applications ranging from narrow-band to wide-band communications capability with integrated personal and terminal mobility to meet the user and service requirements of the 21st century.
3GPP specifications allow the realisation of a new generation of mobile communications technology for a world in which personal communications services should allow person-to-person calling, independent of location, the terminal used, the means of transmission (wired or wireless) and the choice of technology. Personal communication services should be based on a combination of fixed and wireless/mobile services to form a seamless end-to-end service for the user.
3GPP specifications should be in compliance with the following objectives:
a) to provide a single integrated system in which the user can access services in an easy to use and uniform way in all environments;
b) to allow differentiation between service offerings of various serving networks and home environments;
c) to provide a wide range of telecommunications services including those provided by fixed networks and requiring user bit rates of up to 100 Mbit/s as well as services special to mobile communications. These services should be supported in residential, public and office environments and in areas of diverse population densities. These services are provided with a quality comparable with that provided by fixed networks such as ISDN and fixed broadband Internet access;
d) to provide services via hand held, portable, vehicular mounted, movable and fixed terminals (including those which normally operate connected to fixed networks), in all environments (in different service environments - residential, private domestic and different radio environments) provided that the terminal has the necessary capabilities;
e) to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming.
f) to provide audio, data, video and particularly multimedia services;
g) to provide for the flexible introduction of telecommunication services;
h) to provide within the residential environment the capability to enable a pedestrian user to access all services normally provided by fixed networks;
i) to provide within the office environment the capability to enable a pedestrian user to access all services normally provided by PBXs and LANs;
j) to provide a substitute for fixed networks in areas of diverse population densities, under conditions approved by the appropriate national or regional regulatory authority.
k) to provide support for interfaces which allow the use of terminals normally connected to fixed networks. |
22.105 | Services and service capabilities | TS | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.105/22105-910.zip | |
22.115 | Service aspects; Charging and billing | TS | 9.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.115/22115-920.zip | The present document describes the Service Aspects of charging and billing of the 3GPP System.
The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The present document will elaborate on the charging requirements described in the Charging Principles in 3GPP TS 22.101 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned. |
22.127 | Service requirement for the Open Services Access (OSA); Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.127/22127-900.zip | This document specifies the stage 1 requirements for realisation of an Open Service Access (OSA).
OSA enables applications to make use of network functionality through an open standardised interface (the OSA API). OSA provides the glue between applications and network functionality. In this way applications implementing the services become independent from the underlying network technology.
Applications which make use of network functionality offered through the OSA interface are not standardised by 3GPP.
The network functionality offered through the OSA interface may or may not be standardised by 3GPP.
OSA is one toolkit, amongst others, that enables certain aspects of the requirements of the Virtual Home Environment (VHE) concept to be realised. |
22.129 | Service aspects; Handover requirements between UTRAN and GERAN or other radio systems | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.129/22129-900.zip | |
22.135 | Multicall; Service description; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.135/22135-900.zip | |
22.140 | Multimedia Messaging Service (MMS); Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.140/22140-900.zip | |
22.141 | Presence service; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.141/22141-900.zip | |
22.142 | Value Added Services (VAS) for Short Message Service (SMS) requirements | TS | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.142/22142-910.zip | |
22.146 | Multimedia Broadcast/Multicast Service (MBMS); Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.146/22146-900.zip | |
22.153 | Multimedia priority service | TS | 9.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.153/22153-920.zip | The present document specifies the service requirements for Multimedia Priority Service (MPS).
The scope of this document is to specify those requirements of MPS necessary to provide an end-to-end service and to interwork with external networks where needed. Service interactions with external networks are considered within the scope of this document although these interactions may be specified in other standards. |
22.173 | IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 | TS | 9.7.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.173/22173-970.zip | |
22.174 | Push Service; Service aspects; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.174/22174-900.zip | |
22.182 | Customized Alerting Tones (CAT) requirements; Stage 1 | TS | 9.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.182/22182-920.zip | |
22.183 | Customized Ringing Signal (CRS) requirements; Stage 1 | TS | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.183/22183-910.zip | |
22.220 | Service requirements for Home Node B (HNB) and Home eNode B (HeNB) | TS | 9.10.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.220/22220-9a0.zip | |
22.088 | Call Barring (CB) supplementary services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.088/22088-900.zip | |
22.091 | Explicit Call Transfer (ECT) supplementary service; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.091/22091-900.zip | |
22.233 | Transparent end-to-end packet-switched streaming service; Stage 1 | TS | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.233/22233-910.zip | |
22.234 | Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.234/22234-900.zip | This document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLANs).
Maintenance of the I-WLAN feature is discontinued as of Release 12. No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications. |
22.240 | Service requirements for 3GPP Generic User Profile (GUP); Stage 1 | TS | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.240/22240-910.zip | |
22.093 | Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.093/22093-900.zip | |
22.228 | Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1 | TS | 9.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.228/22228-940.zip | |
22.226 | Global Text Telephony (GTT); Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.226/22226-900.zip | |
22.242 | Digital Rights Management (DRM); Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.242/22242-900.zip | |
22.246 | Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.246/22246-900.zip | |
22.243 | Speech recognition framework for automated voice services; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.243/22243-900.zip | |
22.259 | Service requirements for Personal Network Management (PNM); Stage 1 | TS | 9.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.259/22259-920.zip | |
22.278 | Service requirements for the Evolved Packet System (EPS) | TS | 9.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.278/22278-960.zip | |
22.250 | IP Multimedia Subsystem (IMS) Group Management; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.250/22250-900.zip | |
22.340 | IP Multimedia Subsystem (IMS) messaging; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.340/22340-900.zip | |
22.903 | Study on Videotelephony teleservice | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-900.zip | |
22.908 | Study on Paging Permission with Access Control (PPAC) | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-900.zip | |
22.912 | Study into network selection requirements for non-3GPP access | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-900.zip | |
22.934 | Feasibility study on 3GPP system to Wireless Local Area Network (WLAN) interworking | TR | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.934/22934-910.zip | This document studies the feasibility of interworking between 3GPP systems and Wireless Local Area Networks (WLANs). This document identifies and describes:
- Scenarios for 3GPP - WLAN Interworking
- 3GPP - WLAN interworking service requirements
- Guidelines for standardisation of 3GPP-WLAN interworking
The document includes a number of different scenarios of 3GPP-WLAN interworking ranging from common billing to the provision of services seamlessly between the WLAN and the 3GPP system. In addition, 3GPP-WLAN interworking feasibility study includes the analysis of a number of environments where both the 3GPP system and WLAN may be deployed. Finally, this report outlines some of the different WLAN technologies that may be interworked with 3GPP systems.
It is beyond the scope of 3GPP to develop new system functionalities for WLANs that are not interworking with any 3GPP system functionality. |
22.279 | Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1 | TS | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.279/22279-900.zip | |
22.936 | Multi-system terminals | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-900.zip | |
22.935 | Feasibility study on Location Services (LCS) for Wireless Local Area Network (WLAN) interworking | TR | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.935/22935-910.zip | The 3GPP has developed and continues to develop Location Services (LCS) requirements and standards for GSM and UMTS. To further the advancement of LCS within the 3GPP, LCS requirements and standards may be extended for 3GPP WLAN interworking to support the same location-based services that have been deployed today for GSM and UMTS. LCS with 3GPP WLAN Interworking system is considered to enlarge the area of location services.
The purpose of the feasibility study is to study a generic interworking functionality for LCS between 3GPP system and WLAN systems (e.g. IEEE 802.11 family, HIPERLAN/2, …). Specifically, the feasibility study aims to:
- Study the LCS requirements for 3GPP WLAN Interworking scenarios.
- Study the different possible LCS architectures for interworking.
Also, the feasibility study will:
- Assess the service requirements for support of LCS over I-WLAN
- Define the MMI aspects, i.e., the minimum set of functions to support LCS when the choice of access system by the user and/or terminal for when both access systems is available.
- Assess the charging requirements and architecture impacts. In particular, consider whether or not WLAN charging for LCS should be integrated with the architecture for UMTS charging for LCS.
- Assess the security requirements, given the prerequisite that a) the security level of the UMTS platform itself is not impacted, b) the security level provided to users in the WLAN mode is comparable to the one of UMTS. |
22.268 | Public Warning System (PWS) requirements | TS | 9.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.268/22268-950.zip | |
22.942 | Study on Value Added Services (VAS) for Short Message Service (SMS) | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-900.zip | |
22.940 | IP Multimedia Subsystem (IMS) messaging | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-900.zip | |
22.950 | Priority service feasibility study | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-900.zip | |
22.944 | Report on service requirements for UE functionality split | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-900.zip | |
22.949 | Study on a generalized privacy capability | TR | 9.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-910.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-900.zip | |
22.937 | Requirements for service continuity between mobile and Wireless Local Area Network (WLAN) networks | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.937/22937-900.zip | The present document develops the use cases and requirements for service continuity between a 3GPP network and another network, which can be:
- a TISPAN NGN with an IMS, accessed by a WLAN.
- an ISP accessed via a WLAN
Each access network has its own separate security system and the NOs have a commercial agreement for roaming and handover.
The present document considers use cases whereby:
Editors Note: Text to be added when use cases are agreed
The present document also examines the requirements and implications of:
- service aspects: maintaining service quality and service continuity, while roaming between a 3GPP PLMN and an independently-owned WLAN;
- security aspects: while roaming between a 3GPP PLMN and a WLAN, in particular when networks may be independently authenticated.
- UICC aspects, including NAA types, personalisation and ownership.
The present document is related to ongoing standardisation efforts in the following areas:
- where the WLAN is an I-WLAN , requirements for which are described in [3];
- methods for selecting the 3GPP or the non-3GPP access network, requirements for which are described in [2]. |
22.948 | Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-900.zip | |
22.968 | Study for requirements for a Public Warning System (PWS) service | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-900.zip | |
22.973 | IMS Multimedia Telephony service; and supplementary services | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-900.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-900.zip | |
22.978 | All-IP network (AIPN) feasibility study | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-900.zip | |
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-900.zip | |
22.980 | Network composition feasibility study | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-900.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-900.zip | |
22.983 | Services alignment and migration | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-900.zip | |
22.985 | Service requirements for the User Data Convergence (UDC) | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-900.zip | |
22.986 | Study on Service Specific Access Control | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-900.zip | |
23.002 | Network architecture | TS | 9.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-960.zip | |
23.003 | Numbering, addressing and identification | TS | 9.15.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-9f0.zip | |
23.007 | Restoration procedures | TS | 9.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-9a0.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 | 9.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-970.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 | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-900.zip | |
22.953 | Multimedia priority service feasibility study | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-900.zip | |
22.967 | Transferring of emergency call data | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-900.zip | |
23.012 | Location management procedures | TS | 9.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-910.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-900.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-900.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 | 9.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-910.zip | |
23.018 | Basic call handling; Technical realization | TS | 9.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-940.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 9.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-900.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-900.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-900.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 9.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-900.zip | |
22.952 | Priority service guide | TR | 9.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-900.zip | |
23.009 | Handover procedures | TS | 9.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-940.zip | |
23.038 | Alphabets and language-specific information | TS | 9.1.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-911.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 9.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-900.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-900.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 9.14.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-9e0.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 9.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-930.zip | |
23.042 | Compression algorithm for text messaging services | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-900.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 9.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-930.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-900.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-900.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-900.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-900.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.