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.129 | Service aspects; Handover requirements between UTRAN and GERAN or other radio systems | TS | 5.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.129/22129-520.zip | |
23.007 | Restoration procedures | TS | 5.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-510.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.003 | Numbering, addressing and identification | TS | 5.11.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-5b0.zip | |
23.002 | Network architecture | TS | 5.12.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-5c0.zip | |
23.008 | Organization of subscriber data | TS | 5.14.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-5e0.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 | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-500.zip | |
23.012 | Location management procedures | TS | 5.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-520.zip | |
23.009 | Handover procedures | TS | 5.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-5c0.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 5.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-510.zip | |
23.016 | Subscriber data management; Stage 2 | TS | 5.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-530.zip | |
23.018 | Basic call handling; Technical realization | TS | 5.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-5a0.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-500.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.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 5.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-500.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 5.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-500.zip | |
23.038 | Alphabets and language-specific information | TS | 5.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-510.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 5.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-510.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 5.9.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-590.zip | |
23.039 | Interface Protocols for the connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs) | TR | 5.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.039/23039-500.zip | The present document describes a range of alternative interfaces which may be utilised by Short Message Service Centre (SMSC), and Short Message Entity (SME), developers for the connection of SMEs to SMSCs.
The purpose of the present document is to provide a single document within which the various proprietary SMSC to SME interface standards may be accommodated as optional implementations.
As stated in 3GPP TS 23.040 [1], the functionality of the SMSC is outside of the scope of the 3GPP Technical Specifications. As a result, no standardised interfaces have been specified for the connection of SMEs to the SMSC. In the absence of a prevailing standard, SC (Service Centre), developers have devised their own protocols which have not necessarily been based on any existing standards and are therefore largely incompatible with one another.
This document by referring to the various de-facto protocols will limit the further proliferation of proprietary standards and will benefit new SC/SME developers who may then adopt one or more of the existing protocols outlined in the present document.
This document does not provide recommendations, as to the preferred protocol implementation as all are regarded as being of equal merit. SC/SME implementors should therefore adopt the protocol most suited to their particular implementation, application or market. |
23.042 | Compression algorithm for text messaging services | TS | 5.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-500.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 5.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-520.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 5.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-520.zip | |
23.048 | Security mechanisms for the (U)SIM application toolkit; Stage 2 | TS | 5.9.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.048/23048-590.zip | The present document specifies the structure of the Secured Packets in a general format and in implementations using Short Message Service Point to Point (SMS-PP) and Short Message Service Cell Broadcast (SMS-CB).
Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in 3GPP TS 51.011 [5] and allows remote management of files on the UICC in conjunction with SMS and the Data Download to UICC feature of 3GPP TS 31.111.
For UICCs based on 3GPP TS 43.019 [15], the set of commands used in the remote applet management is defined in the present document. This is based on the Open Platform card management specification [14]. For UICCs based on other technologies, other loading mechanisms may be used.
The present document is applicable to the exchange of secured packets between an entity in a 3G or GSM PLMN and an entity in the UICC.
Secured Packets contain application messages to which certain mechanisms according to 3GPP TS 22.048 have been applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or GSM PLMN and on the UICC. The Sending/Receiving Entity in the 3G or GSM PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets. |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 5.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-500.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 5.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-530.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 5.13.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-5d0.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 5.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-510.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 5.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-5c0.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 5.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-560.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 5.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-520.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-500.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 5.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-510.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-500.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-500.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-500.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-500.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-500.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-500.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 5.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-510.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-500.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-500.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-500.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-500.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-500.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 5.13.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-5d0.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 5.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-500.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 5.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-500.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 5.0.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-501.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-500.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-500.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 5.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-501.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-500.zip | |
23.127 | Virtual Home Environment (VHE) / Open Service Access (OSA) | TS | 5.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.127/23127-520.zip | The present document specifies the stage 2 of the Virtual Home Environment.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located.
For Release 5, e.g. CAMEL, MExE, OSA and USAT are considered the mechanisms supporting the VHE concept.
Stage 2 specifications for CAMEL, MExE and USAT are addressed in other documents [1], [2], [3]. However, there is no separate stage 2 specification document for OSA. Therefore, the present document addresses stage 2 aspects for OSA. |
23.146 | Technical realization of facsimile Group 3 non-transparent | TS | 5.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-500.zip | |
23.153 | Out of band transcoder control; Stage 2 | TS | 5.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-5c0.zip | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 5.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-530.zip | |
23.140 | Multimedia Messaging Service (MMS); Functional description; Stage 2 | TS | 5.11.0 | CP | https://www.3gpp.org/ftp/Specs/archive/23_series/23.140/23140-5b0.zip | The present document defines the stage 2 and stage 3 description of the non-realtime Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1.
The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
The present document contains the core functions for a non realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service.
MMS uses a number of technologies to realise the requirements of the stage 1 description (3G TS 22.140) [1]. The present document describes how the service requirements are realised with the selected technologies. As far as possible existing protocols (e.g. WAP, SMTP, ESMTP as transfer protocols; lower layers to provide push, pull, notification) and existing message formats (e.g. SMIL, MIME) shall be used for the realisation of the Multimedia Messaging Service.
The present document serves as a foundation for the development of MMS. It describes a new service which has no direct equivalent in the previous ETSI/GSM world or in the fixed network world. In consequence readers may find that certain aspects are not clearly defined or open to misinterpretation. Where any such case is encountered it is essential that the issue is brought to the 3GPP TSG T2 standards body (see page 2 for contact information) for discussion and resolution in order to provide interoperable implementations. |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 5.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-560.zip | |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 5.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-5a0.zip | |
23.226 | Global text telephony (GTT); Stage 2 | TS | 5.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-520.zip | |
23.195 | Provision of User Equipment Specific Behaviour Information (UESBI) to network entities | TS | 5.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.195/23195-540.zip | The present document defines the stage-2 description of the mechanism to provide the 3GPP network entities with UE Specific Behaviour Information (UESBI). UESBI may be used by correcting mechanisms to overcome some of the issues that have been recognized by 3GPP in TR 25.994 (Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults) [13], and other such documents. The description of these correcting mechanisms is out of the scope of this TS.
ITU-T Recommendation I.130 [1] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [2] defines stage 2 of the method. |
23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | TS | 5.9.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-590.zip | |
23.227 | Application and user interaction in the User Equipment (UE); Principles and specific requirements | TS | 5.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.227/23227-510.zip | The present document defines the principles for scheduling UE resources and controlling UE interactions and resolving conflicts between independently running applications in different application execution environment (e.g. MExE, USAT etc.) and internal and external peripherals (e.g. infra-red, Bluetooth, USIM, radio interface, MMI, memory etc.).
The present document is divided in two parts: clause 4 defines a framework for event handling. Clause 5 addresses some specific issues.
Annex A contains an informative background to the problem area. |
23.228 | IP Multimedia Subsystem (IMS); Stage 2 | TS | 5.15.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-5f0.zip | |
23.236 | Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes | TS | 5.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-540.zip | |
23.271 | Functional stage 2 description of Location Services (LCS) | TS | 5.13.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-5d0.zip | |
23.278 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking | TS | 5.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-560.zip | |
23.221 | Architectural requirements | TS | 5.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-5b0.zip | |
23.205 | Bearer-independent circuit-switched core network; Stage 2 | TS | 5.16.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-5g0.zip | |
23.815 | Charging implications of IMS architecture | TR | 5.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.815/23815-500.zip | The present document identifies the charging implications of the IMS architecture, which is described in 23.002 [5] and 23.228 [4].
It is expected that the content of this TR will act as a basis for:
- change requests against the architecture specifications [4, 5] of SA2, clarifying the architecture implications on charging;
- change requests against the Charging Principles specification [3] of SA5, which contains the charging architecture and mechanisms;
- detailed specification of Charging Data Description [6] in SA5. |
23.875 | Support of Push service | TR | 5.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.875/23875-510.zip | The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope. |
23.910 | Circuit switched data bearer services | TR | 5.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.910/23910-550.zip | The present document provides an overview of the architecture and issues related to the provision of Circuit Switched Bearer Services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 5.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-500.zip | |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 5.1.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-511.zip | |
23.871 | Enhanced support for user privacy in Location Services (LCS) | TR | 5.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.871/23871-500.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-500.zip | |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 5.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-540.zip | |
23.873 | Feasibility study for transport and control separation in the PS CN domain | TR | 2.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.873/23873-200.zip | The scope of this Technical Report (TR) is to capture the results of a feasibility study on how to introduce a clear separation of transport and control functions in the PS CN domain, with minimum impacts on the reference logical architecture for R’00.
With this separation in view, functional elements of the PS CN domain that provide both significant control and transport functions may be decomposed into two separate functional entities: one entity taking care of the control functionality and an other entity handling the payload transport. An exact distribution of the functions currently supported by a single functional entity between new functional entities and other network entities will be defined as the result of this feasibility study, if necessary.
A standard control protocol should be used between the control and transport entities, if applicable, e.g. H.248. The required functionality, e.g. extensions to H.248 or any other protocol which may be chosen for this task, would have to be defined and standardised within 3GPP. This TR will identify and define these extensions, and extensions to other interfaces if applicable.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the PS CN domain. At the end of the feasibility study, the remaining open issues will be reported and their importance will be assessed. An analysis of the benefits and drawbacks of separating the control and transport functions in the PS CN domain will also be performed. |
24.022 | Radio Link Protocol (RLP) for circuit switched bearer and teleservices | TS | 5.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-550.zip | |
24.011 | Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface | TS | 5.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-520.zip | |
24.081 | Line Identification supplementary services; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-500.zip | |
24.082 | Call Forwarding (CF) supplementary services; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-500.zip | |
24.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-500.zip | |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 5.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-550.zip | The present document contains the coding of information necessary for support of supplementary service operation on the mobile radio interface layer 3.
Clause 2 gives the functional definitions and contents of messages for call independent supplementary service operations. Messages necessary for support of call related supplementary service operations are defined in TS 24.008.
Clause 3 gives the general format and coding for messages used for call independent supplementary service and the format and coding of information elements used for both call related and call independent supplementary service operations.
Clause 4 gives the specification of the call related and call independent supplementary service operations. |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 5.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-510.zip | |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-500.zip | |
24.085 | Closed User Group (CUG) supplementary service; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-500.zip | |
24.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-500.zip | |
24.090 | Unstructured Supplementary Service Data (USSD); Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.090/24090-500.zip | |
24.084 | Multi Party (MPTY) supplementary service; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-500.zip | |
24.086 | Advice of Charge (AoC) supplementary services; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.086/24086-500.zip | |
24.091 | Explicit Call Transfer (ECT) supplementary service; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.091/24091-500.zip | |
24.087 | User-to-User Signalling (UUS) Supplementary Service; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.087/24087-500.zip | |
24.096 | Name Identification supplementary services; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.096/24096-500.zip | |
24.135 | Multicall supplementary service; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.135/24135-500.zip | |
24.088 | Call Barring (CB) supplementary service; Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.088/24088-500.zip | |
24.093 | Completion of Calls to Busy Subscriber (CCBS); Stage 3 | TS | 5.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.093/24093-500.zip | |
24.228 | Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 | TS | 5.15.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.228/24228-5f0.zip | The present document gives examples of signalling flows for the IP multimedia call control based on SIP and SDP.
These signalling flows demonstrate the interaction with the IP-connectivity network (GPRS), and with the protocol provided at the Cx interface.
These signalling flows provide detailed signalling flows, which expand on the overview information flows provided in 3GPP TS 23.228 [2].
NOTE: The detailed signalling flows in the present document can be referenced, but the specification will not be further maintained. The example flows can contain errors and can only be regarded as guidelines for persons wanting an overview of how SIP messages with detailed header information could in some example cases look like within 3GPP. Other not documented signalling flows can be as relevant and compliant as the ones that are outlined in this specification. |
25.101 | User Equipment (UE) radio transmission and reception (FDD) | TS | 5.20.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.101/25101-5k0.zip | |
25.104 | Base Station (BS) radio transmission and reception (FDD) | TS | 5.13.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.104/25104-5d0.zip | |
25.106 | UTRA repeater radio transmission and reception | TS | 5.13.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.106/25106-5d0.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.