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.001 | Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN) | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.001/22001-600.zip | |
22.002 | Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.002/22002-600.zip | |
22.003 | Circuit Teleservices supported by a Public Land Mobile Network (PLMN) | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.003/22003-600.zip | |
22.004 | General on supplementary services | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.004/22004-600.zip | |
22.011 | Service accessibility | TS | 6.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.011/22011-640.zip | |
22.016 | International Mobile station Equipment Identities (IMEI) | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.016/22016-600.zip | |
22.022 | Personalisation of Mobile Equipment (ME); Mobile functionality specification | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.022/22022-600.zip | |
22.024 | Description of Charge Advice Information (CAI) | TS | 6.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.024/22024-610.zip | |
22.030 | Man-Machine Interface (MMI) of the User Equipment (UE) | TS | 6.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.030/22030-601.zip | |
22.031 | 3G Security; Fraud Information Gathering System (FIGS); Service description; Stage 1 | TS | 6.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.031/22031-600.zip | |
22.032 | Immediate Service Termination (IST); Service description; Stage 1 | TS | 6.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.032/22032-600.zip | |
22.034 | High Speed Circuit Switched Data (HSCSD); Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.034/22034-600.zip | |
22.038 | (U)SIM Application Toolkit (USAT); Service description; Stage 1 | TS | 6.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.038/22038-650.zip | |
22.041 | Operator Determined Barring (ODB) | TS | 6.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.041/22041-620.zip | |
22.042 | Network Identity and TimeZone (NITZ); Service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.042/22042-600.zip | |
22.053 | Tandem Free Operation (TFO); Service description; Stage 1 | TS | 6.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.053/22053-600.zip | |
22.057 | Mobile Execution Environment (MExE); Service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.057/22057-600.zip | |
22.060 | General Packet Radio Service (GPRS); Service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.060/22060-600.zip | |
22.066 | Support of Mobile Number Portability (MNP); Service description; Stage 1 | TS | 6.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.066/22066-610.zip | |
22.067 | enhanced Multi Level Precedence and Pre-emption service (eMLPP); Stage 1 | TS | 6.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.067/22067-610.zip | |
22.071 | Location Services (LCS); Service description; Stage 1 | TS | 6.7.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.071/22071-670.zip | |
22.072 | Call Deflection (CD) service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.072/22072-600.zip | |
22.076 | Noise suppression for the AMR codec; Service description; Stage 1 | TS | 6.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.076/22076-600.zip | |
22.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description; Stage 1 | TS | 6.9.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.078/22078-690.zip | |
46.020 | Half rate speech; Half rate speech transcoding | TS | 7.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/46_series/46.020/46020-700.zip | |
43.246 | Multimedia Broadcast/Multicast Service (MBMS) in the GERAN; Stage 2 | TS | 7.3.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.246/43246-730.zip | |
22.081 | Line Identification supplementary services; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.081/22081-600.zip | |
22.082 | Call Forwarding (CF) Supplementary Services; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.082/22082-600.zip | |
43.059 | Functional stage 2 description of Location Services (LCS) in GERAN | TS | 7.3.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.059/43059-730.zip | |
22.085 | Closed User Group (CUG) supplementary services; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.085/22085-600.zip | |
22.086 | Advice of Charge (AoC) supplementary services; Stage 1 | TS | 6.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.086/22086-610.zip | |
22.087 | User-to-User Signalling (UUS); Service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.087/22087-600.zip | |
22.088 | Call Barring (CB) supplementary services; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.088/22088-600.zip | |
22.079 | Support of Optimal Routeing (SOR); Service definition; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.079/22079-600.zip | |
43.318 | Generic Access Network (GAN); Stage 2 | TS | 7.5.0 | RP | https://www.3gpp.org/ftp/Specs/archive/43_series/43.318/43318-750.zip | |
22.084 | MultiParty (MPTY) supplementary service; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.084/22084-600.zip | |
22.094 | Follow Me service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.094/22094-600.zip | |
22.091 | Explicit Call Transfer (ECT) supplementary service; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.091/22091-600.zip | |
22.097 | Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.097/22097-600.zip | |
22.093 | Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.093/22093-600.zip | |
22.105 | Services and service capabilities | TS | 6.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.105/22105-640.zip | |
22.112 | USIM Application Toolkit (USAT) Interpreter; Stage 1 | TS | 6.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.112/22112-600.zip | The present document specifies a system to make Mobile Operator services, based on USAT functionality and USIM based security functionality, available to an internet environment. This is achieved by specifying the necessary components and protocols for a secure narrow band channel between the internet application and an USAT Interpreter on the USIM. The actual application could be developed using the application language of choice. Two types of applications interfaces are used as examples, i.e., mark-up language based on WML and Remote Procedure Call (RPC).
The interpreter and the secure narrow band channel form a core platform to enable services like:
- Advanced security functionality, e.g., digital signatures in m-commerce applications
- Value added services based on position and roaming
- Controlled activation and management of other applications, e.g. multimedia and payment type of applications.
The secure narrow band channel is achieved by specifying the following:
- specific application and content related functionalities of the interface between the application system and the USAT Gateway;
- specific functionalities and protocols of the interface between the USAT Gateway and the USAT Interpreter associated with a USIM, achieved by defining a low level command set for interpretation by the USAT Interpreter;
- defined level of functionality available to the application server for the implementation of USIM based services such as PKI, location services, push and broadcast services, event based services, etc..
The present document does not specify any elements of the protocol stack between the application server and the USAT Gateway, the mark-up language definition, and the transport protocols between the USAT Gateway and the USAT Interpreter. |
22.115 | Service aspects; Charging and billing | TS | 6.8.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.115/22115-680.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 | 6.8.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.127/22127-680.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 | 6.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.129/22129-610.zip | |
22.135 | Multicall; Service description; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.135/22135-600.zip | |
22.140 | Multimedia Messaging Service (MMS); Stage 1 | TS | 6.7.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.140/22140-670.zip | |
22.096 | Name identification supplementary services; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.096/22096-600.zip | |
22.101 | Service aspects; Service principles | TS | 6.12.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.101/22101-6c0.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.090 | Unstructured Supplementary Service Data (USSD); Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.090/22090-600.zip | |
22.141 | Presence service; Stage 1 | TS | 6.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.141/22141-650.zip | |
22.146 | Multimedia Broadcast/Multicast Service (MBMS); Stage 1 | TS | 6.8.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.146/22146-680.zip | |
22.083 | Call Waiting (CW) and Call Holding (HOLD); Supplementary Services; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.083/22083-600.zip | |
22.174 | Push Service; Service aspects; Stage 1 | TS | 6.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.174/22174-620.zip | |
22.228 | Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1 | TS | 6.11.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.228/22228-6b0.zip | |
22.226 | Global Text Telephony (GTT); Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.226/22226-600.zip | |
22.234 | Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking | TS | 6.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.234/22234-640.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.242 | Digital Rights Management (DRM); Stage 1 | TS | 6.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.242/22242-630.zip | |
22.233 | Transparent end-to-end packet-switched streaming service; Stage 1 | TS | 6.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.233/22233-630.zip | |
22.243 | Speech recognition framework for automated voice services; Stage 1 | TS | 6.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.243/22243-640.zip | |
22.240 | Service requirements for 3GPP Generic User Profile (GUP); Stage 1 | TS | 6.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.240/22240-650.zip | |
22.250 | IP Multimedia Subsystem (IMS) Group Management; Stage 1 | TS | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.250/22250-600.zip | |
22.246 | Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1 | TS | 6.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.246/22246-630.zip | |
22.800 | IP Multimedia Subsystem (IMS) subscription and access scenarios | TR | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.800/22800-600.zip | This document studies scenarios between subscribers and operators, mainly from IMS subscriptions point of view and verifies the compatibility of the possible scenarios within 3GPP Scope. Release 6 includes several work items like IMS enhancements, WLAN interworking that needs to be better understood so that clear requirement can be agreed and relevant technical specifications can be developed in time.
The document will identify the requirements arising from the following issues:
• Identification of requirements for 3GPP operators to implement only some of 3GPP system domains? (For example an IMS system separated from the PS domain and access network. What is the relationship between the AN/CN/IMS networks in this case? Are there conflicts in privacy issues due to several subscriptions?)
• Operator control of networks used to access / provide IMS services. For example operator may want to limit the subscriber to access the IMS via a specific 3GPP access network.
• Non-3GPP access network implications.
• Simultaneously access to IMS by one user with multiple devices. .
• UE functionality split (if any implications).
• Deployment of UICC with several USIM and ISIM applications from different parties.
• Analyse aspects of user interaction when activating USIM and ISIM applications on the UICC (e.g. manually, automatically, PIN, NON-PIN).
Below issues need to be described in scenarios :
• Generic issues
• Security
• Charging
• Privacy
• Roaming
• Regulatory (e.g lawful interception) etc.
• Quality of service
• User experience
Further TR needs to translate the scenarios, which fit in the scope of the 3GPP system to 3GPP service requirements.
Criteria for requirements to be included:
1. In scope with 3GPP access (UTRAN, GERAN) or access that 3GPP has specified interworking with (WLAN).
2. In scope with 3GPP core network(s).
3. In scope with 3GPP enabling technologies.
4. Scope of this work is limited to identify service requirements derived from scenarios capturing various business requirements. No architectural solutions will be considered in this TR.
Note: 3GPP should not place requirements, which would prohibit the possibility to use non-3GPP defined access for IMS.
Note: The SA2 within its own documentation shall look into technical feasibility and architecture implications of scenarios and requirements defined by SA1 and contact SA3 and SA5 for deeper technical understanding if necessary. Overall architecture implications shall consider also UICC implications (e.g. if it is appropriate to have several ISIMs on one UICC and possibility of having empty field for either ISIM or USIM in a UICC.?) and accordingly contact T3 for deeper technical understanding if necessary. |
22.934 | Feasibility study on 3GPP system to Wireless Local Area Network (WLAN) interworking | TR | 6.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.934/22934-620.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.940 | IP Multimedia Subsystem (IMS) messaging | TR | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-600.zip | |
22.857 | Run-time independent framework feasibility study | TR | 6.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.857/22857-600.zip | The present document is a technical report consisting of a benefits analysis and a feasibility study on the creation of a framework enabling the application of MExE to arbitrary runtime environments. |
22.944 | Report on service requirements for UE functionality split | TR | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-600.zip | |
22.949 | Study on a generalized privacy capability | TR | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-600.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 6.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-610.zip | |
22.340 | IP Multimedia Subsystem (IMS) messaging; Stage 1 | TS | 6.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.340/22340-620.zip | |
22.950 | Priority service feasibility study | TR | 6.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-640.zip | |
23.002 | Network architecture | TS | 6.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-6a0.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 6.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-600.zip | |
23.003 | Numbering, addressing and identification | TS | 6.17.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-6h0.zip | |
22.952 | Priority service guide | TR | 6.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-640.zip | |
23.008 | Organization of subscriber data | TS | 6.15.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-6f0.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 | 6.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-650.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-600.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.012 | Location management procedures | TS | 6.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-640.zip | |
23.007 | Restoration procedures | TS | 6.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-620.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.011 | Technical realization of Supplementary Services | TS | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-600.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 6.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-600.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 6.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-600.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 6.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-600.zip | |
23.018 | Basic call handling; Technical realization | TS | 6.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-660.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 6.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-600.zip | |
23.016 | Subscriber data management; Stage 2 | TS | 6.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-610.zip | |
23.038 | Alphabets and language-specific information | TS | 6.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-610.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 6.9.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-690.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 6.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-600.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 6.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-620.zip | |
23.042 | Compression algorithm for text messaging services | TS | 6.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-600.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-600.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 6.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-600.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 6.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-6a0.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-600.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 6.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-610.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 6.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-620.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 6.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-600.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.