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 |
|---|---|---|---|---|---|---|
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-900.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-900.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 9.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-9b0.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-900.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-900.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-900.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-900.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-900.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-900.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-900.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-900.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-900.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-900.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-900.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-900.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-900.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-900.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-900.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-900.zip | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 9.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-960.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-900.zip | |
23.142 | Value-added Services for SMS (VAS4SMS); Interface and signalling flow | TS | 9.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-901.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 9.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-930.zip | |
23.146 | Technical realization of facsimile Group 3 non-transparent | TS | 9.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-900.zip | |
23.141 | Presence service; Architecture and functional description | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-900.zip | |
23.153 | Out of band transcoder control; Stage 2 | TS | 9.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-930.zip | |
23.167 | IP Multimedia Subsystem (IMS) emergency sessions | TS | 9.14.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-9e0.zip | |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 9.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-900.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-900.zip | |
23.198 | Open Service Access (OSA); Stage 2 | TS | 9.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/23_series/23.198/23198-900.zip | The present document specifies the stage 2 of the Open Service Access (OSA). |
23.202 | Circuit switched data bearer services | TS | 9.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-910.zip | |
23.204 | Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 | TS | 9.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-910.zip | The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228 [9]). These include (but are not limited) to:
1 Enhancements to the HSS;
2 Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
3 Authentication of service usage and registration;
4 Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
5 Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
6 Mechanisms to handle MT-SMS without MSISDN to IMS UE, and SMS between IMS UEs that support MSISDN-less SMS operation.
The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 [2] and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0 [12]. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.
NOTE: The page-mode immediate message as defined in TS 24.247[14] is considered as a subset of OMA-TS-SIMPLE-IM-V1_0 [12].
The document also specifies the capabilities and enhancements needed to support service level interworking for the Short Message service, as defined in the TS 23.040 [2] and in this specification and the OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. The features supported from the CPM specification are the exchange of short or large immediate messages in pager mode, as well as session-based messaging.
The service requirements are described in TS 22.340 [18]. |
23.205 | Bearer-independent circuit-switched core network; Stage 2 | TS | 9.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-940.zip | |
23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | TS | 9.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-920.zip | |
23.203 | Policy and charging control architecture | TS | 9.14.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-9e0.zip | The present document specifies the overall stage 2 level functionality for Policy and Charging Control that encompasses the following high level functions for IP‑CANs (e.g. GPRS, Fixed Broadband, EPC, etc.):
- Flow Based Charging for network usage, including charging control and online credit control, for service data flows and application traffic;
- Policy control (e.g. gating control, QoS control, QoS signalling, etc.).
The present document specifies the Policy and Charging Control functionality for Evolved 3GPP Packet Switched domain, including both 3GPP accesses GERAN/UTRAN/E-UTRAN and Non-3GPP accesses, according to TS 23.401 [17] and TS 23.402 [18].
The present document specifies functionality for unicast bearers. Broadcast and multicast bearers, such as MBMS contexts for GPRS, are out of scope of the present document.
NOTE: For E-UTRAN access, the usage of functionalities covered in this specification for features such as MBMS, CIoT and V2X is described in TS 23.246 [6], TS 23.682 [42] and TS 23.285 [48], respectively. |
23.216 | Single Radio Voice Call Continuity (SRVCC); Stage 2 | TS | 9.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-990.zip | |
23.221 | Architectural requirements | TS | 9.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-950.zip | |
23.226 | Global text telephony (GTT); Stage 2 | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-900.zip | |
23.228 | IP Multimedia Subsystem (IMS); Stage 2 | TS | 9.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-940.zip | |
23.231 | SIP-I based circuit-switched core network; Stage 2 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-900.zip | |
23.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; System description | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.234/23234-900.zip | This document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLANs).
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. |
23.236 | Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-900.zip | |
23.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | TS | 9.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.237/23237-9a0.zip | |
23.240 | 3GPP Generic User Profile (GUP); Architecture (Stage 2) | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-900.zip | |
23.246 | Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description | TS | 9.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-960.zip | |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-900.zip | |
23.259 | Personal Network Management (PNM); Procedures and information flows; Stage 2 | TS | 9.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-940.zip | |
23.251 | Network sharing; Architecture and functional description | TS | 9.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-950.zip | |
23.272 | Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 | TS | 9.15.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.272/23272-9f0.zip | This document defines the Stage 2 architecture and specification for the CS Fallback and for SMS over SGs for EPS or CS Fallback and SMS over S102. The scope of this document includes the architecture enhancements for functionality to enable fallback from E-UTRAN access to UTRAN/GERAN CS domain access and to CDMA 1x RTT CS domain access, and functionality to reuse of voice and other CS-domain services (e.g. CS UDI video / LCS / USSD) by reuse of the CS domain. The functionality specified to support SMS over SGs does not trigger any CS Fallback to UTRAN/GERAN. The functionality specified to support SMS over S102 does not trigger any CS Fallback to CDMA 1xRTT CS domain.
In addition this specification includes an SMS in MME architecture option for SMS services only. This functionality does not trigger any CS Fallback and does not require SGs.
The architecture enhancements to support CS fallback to CDMA 1x RTT CS domain access for UEs with single and dual receiver configurations are specified in Annex B.
In this Release of the specification no mechanisms are specified to support CS Fallback to both UTRAN/GERAN and CDMA 1xRTT in the same PLMN. So, even when a UE has the capability to support both CS Fallback to UTRAN/GERAN CS domain and CS Fallback to CDMA 1xRTT CS domain in a given PLMN, the PLMN implements only one of the two. |
23.271 | Functional stage 2 description of Location Services (LCS) | TS | 9.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-980.zip | |
23.278 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-900.zip | |
23.327 | Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.327/23327-900.zip | This document specifies the stage 2 system description for providing mobility between 3GPP Wireless Local Area Network Interworking (I‑WLAN) and 3GPP Systems. The I-WLAN feature defined in TS 23.234 [2] has been discontinued since Release 13 and it is removed from this specification. |
23.279 | Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2 | TS | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.279/23279-900.zip | |
23.334 | IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions | TS | 9.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.334/23334-930.zip | |
23.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.333/23333-900.zip | |
23.380 | IMS Restoration Procedures | TS | 9.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.380/23380-960.zip | |
23.335 | User Data Convergence (UDC); Technical realization and information flows; Stage 2 | TS | 9.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.335/23335-930.zip | |
23.292 | IP Multimedia Subsystem (IMS) centralized services; Stage 2 | TS | 9.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.292/23292-980.zip | |
23.402 | Architecture enhancements for non-3GPP accesses | TS | 9.13.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.402/23402-9d0.zip | |
23.826 | Feasibility study on Voice Call Continuity (VCC) support for emergency calls | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.826/23826-900.zip | This document contains the results of the feasibility study into the architectural requirements and alternatives for the support of active voice call continuity between Circuit Switched (CS) domain and the IP Multimedia Subsystem (IMS) for emergency calls. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The Feasibility Study considers different solutions for offering voice call continuity for emergency calls when users move between the GSM/UMTS CS Domain and the IP Connectivity Access Network (e.g., WLAN interworking) with home IMS functionality. The objective is to identify an architectural solution that allows completely automatic connectivity to the correct PSAP (from the end-user point of view) as specified in TS 23.167 [4], and allow for the possibility of a domain transfer as specified in TS 23.206 [3]. The study will also identify configuration impacts upon existing networks in order to realize the desired functionality.
Existing solutions developed by the 3GPP (e.g. 3GPP system to Wireless Local Area Network Interworking (I-WLAN)) should be reused as much as possible. |
23.830 | Architecture aspects of Home Node B (HNB) / Home enhanced Node B (HeNB) | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.830/23830-900.zip | This Technical Report describes the architectural aspects of specific UTRAN and E-UTRAN base stations, known as Home NodeBs and Home eNodeBs, which provide services in e.g. residential or enterprise deployments.
NOTE: This feasibility study has led to normative modifications of various specifications; the contents of this technical report should therefore be considered out of date.
To achieve this, the objectives are to (a) document the architectural assumptions taken by other working groups as part of their previous and ongoing work on Home Node B/Home eNodeB and Closed Subscriber Groups (CSG), and to (b) identify any outstanding issues not properly addressed in Rel-8.
Starting from the resulting architectural baseline, the intention is to derive architectural requirements arising from the outstanding Rel-8 issues and the Rel-9 requirements on Home NodeB and Home eNodeB as laid down by SA WG1 in TS 22.220 [2]. Based on this, the objective is to discuss and conclude on solutions for the architectural issues arising from those requirements. |
23.868 | Feasibility study on extension of support for IP Multimedia Subsystem (IMS) emergency calls | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.868/23868-900.zip | The present document provides a study investigating possible limitations of the solution for IMS emergency calls defined for Rel-7 in TS 23.167 [2], as well as possible extensions of that solution to reduce or eliminate some or all of the identified limitations.
The study item is expected mainly to concern IMS although some aspects of IP-CAN support may also be included. The study item has the following objectives
- Evaluate the feasibility of supporting IMS emergency calls for combinations of IP access network A and IMS core network B not supported in Rel-7 including but not limited to the following cases:
- A is any IP access network and B is the home 3GPP compliant IMS network for any emergency calling UE with adequate security credentials
- A is any IP access network and B is a visited 3GPP compliant IMS network for any emergency calling roaming UE with adequate security credentials
Additional user cases may also be proposed and evaluated during the SI if deemed applicable.
- Evaluate other enhancements to the solution for IMS emergency calls in Release 7 that may improve performance and/or reduce complexity
- Evaluate the feasibility of better aligning the solution in TS 23.167 [2] with applicable IETF standards and draft standards (e.g. from the Ecrit and Geopriv working groups)
- Any enhancement to the support of IMS emergency calls shall remain backward compatible to the solution in Rel-7 from the perspective of the UE and any 3GPP network element. Furthermore, any enhancement should be based on the solution in Rel-7 and should avoid unnecessarily adding new network entities, protocols and interfaces and moving existing functions from one entity to another.
The study item is expected to enable SA WG2 to decide which of the above objectives if any may be worth supporting in Rel-8 and which extensions to the current solution would then be appropriate. |
23.869 | Support for Internet Protocol (IP) based IP Multimedia Subsystem (IMS) Emergency calls over General Packet Radio Service (GPRS) and Evolved Packet Service (EPS) | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.869/23869-900.zip | |
23.870 | Single Radio Voice Call Continuity (SR-VCC) support for IMS Emergency Calls | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.870/23870-900.zip | SRVCC as specified in TS 23.216 [3], provides handover of voice calls from E-UTRAN/HSPA to UTRAN/GERAN or from E-UTRAN to CDMA2000 1x. SRVCC of IMS emergency calls is not supported in TS 23.216 [3], and thus handover of such calls will have unpredictable effects, in the worst case causing the call to fail. This is a serious concern for operators and their subscribers, and may cause regulatory violations in some parts of the world.
Therefore, the objective of this document is to study both the EPS and IMS aspects of how to best support the handover of ongoing emergency calls for the following scenarios:
- E-UTRAN to UTRAN/GERAN CS.
- HSPA to UTRAN/GERAN CS.
- E-UTRAN to CDMA2000 1x CS. |
23.879 | Study on Circuit Switched (CS) domain services over evolved Packet Switched (PS) access | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.879/23879-900.zip | The present document contains the results of the study of the architectural requirements of CS Domain Services over evolved PS access and concludes with a way forward. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The objective is to describe an architecture that is capable of extending the 'traditional' MSC-Server based set of CS voice, supplementary and value-adding services and business principles (e.g. for roaming and interconnect) to the evolved PS access. The intention is also to give a CS handover-like user experience for voice calls when changing between evolved PS and legacy CS accesses. The architecture will however not be limited to the provision of speech services over evolved PS accesses; on the contrary, through the exploitation of the Combinational services, it will be possible to harness the capabilities of IMS to provide new, innovative services to the end user. Handover of the parallel PS session towards legacy 3GPP access will be considered as well, but may be limited by the capabilities of the legacy system and operator preferences.
Co-existence with IMS centric Single Radio VCC solutions shall be studied as well. |
23.883 | Study on enhancements to IMS Centralized Services (ICS) | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.883/23883-900.zip | The following aspects of IMS Centralized Services (ICS), though studied in Release 8 (and to some extent documented in TR 23.892 [2]), required further study and are herein documented:
- ICS supplementary service data management (e.g. Supplementary Services data synchronization).
- Management of Telephony Application Server (TAS) user configuration for an ICS UE when PS access cannot be used.
Consideration shall be given to attaining a consistent user experience, and managing and enforcing operator policies as well as user preferences. Heterogeneous access technologies over which the IMS service is provided shall also be taken into account. |
23.891 | Evaluation of LCS Control Plane Solutions for EPS | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.891/23891-900.zip | This TR studies various alternatives for the stage 2 control plane LCS Reference Architecture for Evolved Packet Core.
This document does not document the radio signal measure and/or position methods for the E-UTRAN. Those are addressed in RAN specifications. |
23.820 | Study of IMS restoration procedures | TR | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.820/23820-900.zip | The present document identifies the changes required in the 3GPP IMS specifications so that a consistent state is restored in the IMS Core Network, after, or during a planned, or unplanned stop of a network element. The study will go through the following steps:
• Establish the requirements that should be covered with these procedures. That is which are the impacts to the end user service that are acceptable and which are not, after a network failure.
• List the service interruption scenarios that need to be studied.
• Provide solutions, so that in all the service interruption scenarios listed, the impacts to the end user service comply with the requirements. These solutions provide procedures for the automatic restoration to a consistent state in the network and indicate how to trigger these procedures.
• Analyze the impacts of the solutions in the current specifications.
• Conclusion and recommended way forward.
It is important to realise that these procedures are meant to be operational procedures for restoration and so care must be taken with what is existing and will exist with OA&M procedures to avoid overlap which could cause clashes. |
23.903 | Redial solution for voice-video switching | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-900.zip | |
23.838 | IP Multimedia Subsystem (IMS) service continuity enhancements; Service, policy and interaction; Stage 2 | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.838/23838-900.zip | This technical report intends to develop enhancements for Rel-8 IMS Service Continuity and solutions for mobility of media flows and control of a session between different devices under the same subscription (i.e. Inter-UE Transfer) to a state where they can be transferred to normative specifications, focusing on the following aspects:
For Inter-UE transfer:
- Inter-UE Transfer scenarios for transferring/retrieval/addition/deletion of media flows in a Collaborative Session;
- Inter-UE Transfer scenarios for establishment or continuation of a Collaborative Session while transferring control;
- Transferring media flows to the target UE whilst keeping the Collaborative Session control in the source UE.
For IMS Service Continuity Enhancement:
- Management of operator policy and user preferences;
- Interaction and coexistence with underlying mobility mechanisms and corresponding policies;
- Further capabilities for the support of mid-call services during session transfer, in addition to those defined in TS 23.292 [6], TS 23.237 [5] and TS 23.216 [6];
- Session Continuity for speech and video over CS.
IMS Service Continuity will be restricted to service continuity using IMS procedures, i.e. mobility mechanisms on the IP-CAN level are not within the scope of this document This document does not overlap with the underlying EPC and SRVCC features, even though there could be cross-references between the corresponding Technical Specifications. |
23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | TS | 9.16.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-9g0.zip | |
23.979 | 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-900.zip | |
23.977 | Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-900.zip | |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-900.zip | |
23.976 | Push architecture | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-900.zip | |
23.919 | Direct tunnel deployment guideline | TR | 9.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-900.zip | |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-900.zip | |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 9.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-900.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-900.zip | |
24.011 | Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface | TS | 9.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-901.zip | |
24.022 | Radio Link Protocol (RLP) for circuit switched bearer and teleservices | TS | 9.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-900.zip | |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-900.zip | |
24.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-900.zip | |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-900.zip | |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 9.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-920.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.082 | Call Forwarding (CF) supplementary services; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-900.zip | |
24.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-900.zip | |
24.084 | Multi Party (MPTY) supplementary service; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-900.zip | |
24.085 | Closed User Group (CUG) supplementary service; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-900.zip | |
24.087 | User-to-User Signalling (UUS) Supplementary Service; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.087/24087-900.zip | |
24.086 | Advice of Charge (AoC) supplementary services; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.086/24086-900.zip | |
24.088 | Call Barring (CB) supplementary service; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.088/24088-900.zip | |
24.090 | Unstructured Supplementary Service Data (USSD); Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.090/24090-900.zip | |
24.081 | Line Identification supplementary services; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-900.zip | |
24.093 | Completion of Calls to Busy Subscriber (CCBS); Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.093/24093-900.zip | |
24.096 | Name Identification supplementary services; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.096/24096-900.zip | |
24.091 | Explicit Call Transfer (ECT) supplementary service; Stage 3 | TS | 9.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.091/24091-900.zip | |
24.109 | Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details | TS | 9.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.109/24109-930.zip | |
24.141 | Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 9.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.141/24141-920.zip | |
24.167 | 3GPP IMS Management Object (MO); Stage 3 | TS | 9.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.167/24167-920.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.