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.042 | Compression algorithm for text messaging services | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-a00.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-a00.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-a00.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-a00.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 10.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-a10.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-a00.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-a00.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-a00.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-a00.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-a00.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-a00.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 10.14.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-ae0.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-a00.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-a00.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-a00.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-a00.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-a00.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 10.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-a01.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-a00.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-a00.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-a00.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-a00.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 10.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-a20.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-a00.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-a00.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 10.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-a10.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-a00.zip | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 10.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-a50.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-a00.zip | |
23.141 | Presence service; Architecture and functional description | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-a00.zip | |
23.142 | Value-added Services for SMS (VAS4SMS); Interface and signalling flow | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-a00.zip | |
23.153 | Out of band transcoder control; Stage 2 | TS | 10.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-a10.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-a00.zip | |
23.167 | IP Multimedia Subsystem (IMS) emergency sessions | TS | 10.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-ab0.zip | |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 10.0.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-a01.zip | |
23.202 | Circuit switched data bearer services | TS | 10.0.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-a01.zip | |
23.204 | Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 | TS | 10.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-a20.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.203 | Policy and charging control architecture | TS | 10.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-aa0.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.146 | Technical realization of facsimile Group 3 non-transparent | TS | 10.0.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-a01.zip | |
23.216 | Single Radio Voice Call Continuity (SRVCC); Stage 2 | TS | 10.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-a60.zip | |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-a00.zip | |
23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-a00.zip | |
23.226 | Global text telephony (GTT); Stage 2 | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-a00.zip | |
23.205 | Bearer-independent circuit-switched core network; Stage 2 | TS | 10.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-a20.zip | |
23.221 | Architectural requirements | TS | 10.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-a30.zip | |
23.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; System description | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.234/23234-a00.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.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | TS | 10.13.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.237/23237-ad0.zip | |
23.228 | IP Multimedia Subsystem (IMS); Stage 2 | TS | 10.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-a90.zip | |
23.240 | 3GPP Generic User Profile (GUP); Architecture (Stage 2) | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-a00.zip | |
23.246 | Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description | TS | 10.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-a30.zip | |
23.251 | Network sharing; Architecture and functional description | TS | 10.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-a60.zip | |
23.259 | Personal Network Management (PNM); Procedures and information flows; Stage 2 | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-a00.zip | |
23.261 | IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2 | TS | 10.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.261/23261-a20.zip | |
23.271 | Functional stage 2 description of Location Services (LCS) | TS | 10.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-a40.zip | |
23.272 | Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 | TS | 10.15.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.272/23272-af0.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.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-a00.zip | |
23.279 | Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2 | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.279/23279-a00.zip | |
23.231 | SIP-I based circuit-switched core network; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-a00.zip | |
23.236 | Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes | TS | 10.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-a30.zip | |
23.327 | Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems | TS | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.327/23327-a00.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.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions | TS | 10.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.333/23333-a50.zip | |
23.278 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-a00.zip | |
23.334 | IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions | TS | 10.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.334/23334-a50.zip | |
23.292 | IP Multimedia Subsystem (IMS) centralized services; Stage 2 | TS | 10.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.292/23292-a60.zip | |
23.284 | Local Call Local Switch (LCLS); Stage 2 | TS | 10.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.284/23284-a50.zip | |
23.335 | User Data Convergence (UDC); Technical realization and information flows; Stage 2 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.335/23335-a00.zip | |
23.380 | IMS Restoration Procedures | TS | 10.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.380/23380-a30.zip | |
23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | TS | 10.13.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-ad0.zip | |
23.402 | Architecture enhancements for non-3GPP accesses | TS | 10.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.402/23402-aa0.zip | |
23.824 | IP-Short-Message-Gateway (IP-SM-GW) enhancements for interworking with Open Mobile Alliance (OMA) Converged IP Messaging (CPM) | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.824/23824-a00.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.
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-20070816-C [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-20070816-C [12].
The service requirements are described in TS 22.340 [18]. |
23.829 | Local IP Access and Selected IP Traffic Offload (LIPA-SIPTO) | TR | 10.0.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.829/23829-a01.zip | Support of Local IP access for the Home (e)NodeB Subsystem and of Selected IP traffic offload for the Home (e)NodeB Subsystem and for the macro layer network is required in TS 22.220 [3] and TS 22.101 [2].
This Technical Report describes the following functionalities:
- Local IP access – LIPA – to residential/corporate local network for Home (e)NodeB Subsystem;
- Selected IP traffic offload – SIPTO – (e.g. Internet traffic) for Home (e)NodeB Subsystem;
- Selected IP traffic offload (e.g. Internet traffic, corporate traffic) for the macro network (3G and LTE only).
The report is intended to analyse the architectural aspects to achieve these objectives and to gather the technical content until it can be included in the relevant technical specifications. |
23.854 | Enhancements for Multimedia Priority Service (MPS) | TR | 1.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.854/23854-140.zip | MPS will enable National Security/Emergency Preparedness (NS/EP) users (herein called Service Users) to make priority calls/sessions using the public networks. This service needs to be ensured also under special conditions such as network congestion. Service Users are the government-authorized personnel, emergency management officials and/or other authorized users. Effective disaster response and management rely on the Service User's ability to communicate during congestion conditions. Service Users are expected to receive priority treatment, in support of mission critical multimedia communications.
The enhancements for MPS evaluated in this document are priority aspects of EPS packet bearer services and priority related interworking between IMS and EPS packet bearer services. These enhancements enable the network to support end-to-end priority treatment for MPS call/session origination/termination, including the Non Access Stratum (NAS) and Access Stratum (AS) signalling establishment procedures at originating/terminating network side as well as resource allocation in the core and radio networks for bearers. Priority treatment will be applicable to IMS based multimedia services, priority EPS bearer services and CS Fallback.
This document clarifies the architectural requirements for MPS, considers the priority service scenarios, and evaluates solution alternatives. Solutions will be proposed and evaluated based on the following three service categories: IMS based multimedia service (voice, video etc), priority EPS bearer services (PS data without IMS interaction) and CS Fallback. Common issues for multiple service categories should be resolved by single solution to limit the amount of overall functionality and to avoid complexity.
The basic eMPS, i.e. priority handling of IMS based multimedia service, EPS bearer services and CS Fallback have completed in Rel‑10. In Rel‑11, Single Radio Voice Call Continuity (SRVCC) from LTE to UTRAN/GERAN/1xCS will be investigated based on Rel‑10 SRVCC specification.
The result of the analysis should be suitable as a basis for normative MPS specification work.
The scope of the MPS part is to further investigate:
- The signalling and procedures for identifying priority and authorizing the usage of priority service.
- The required priority attributes used in enabling end-to-end priority marking and priority treatment during establishment, modification and release of an IMS based priority voice/video/data session.
- The scenarios and capabilities for supporting priority EPS bearer data services.
- The potential impacts on existing and relevant standard procedures in order to provide preferential treatment for MPS requests in the event of congestion.
- Inter-working with other IMS and CS networks to provide an end-to-end priority service. |
23.845 | Study on User Data Convergence (UDC) evolution | TR | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.845/23845-a00.zip | The present document is addressing a number of topics regarding User Data Convergence evolution. Some of these topics were identified in the Rel9 work but have been delayed, others are new.
These topics are largely independent of each other and are studied separately in this document.
They will be normally addressed through the following steps:
- a description of the topic to be addressed with its interest, the associated requirements to cover or issues to be solved
- a description of the alternative solutions including their impact on 3GPP specifications
- a comparison of the solutions
- a conclusion with recommendations. |
23.856 | Single Radio Voice Call Continuity (SRVCC) enhancements; Stage 2 | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.856/23856-a00.zip | SR-VCC has been standardized in Release 8 TS 23.216 [3] to provide seamless continuity when UE handovers from E-UTRAN to UTRAN/GERAN.
This document contains the results of feasibility study of the requirements and the alternative solutions to improve the handover performance of SRVCC.
The objective of this study is as follows:
- Evaluating the performance of current Rel‑8 SRVCC solution;
- Enhancing the performance of the SR-VCC Flow Break with regard to the roaming and non-roaming case;
- Enhancing SR-VCC handover performance while minimizing the impacts on the network architecture for the directions
- from EUTRAN to UTRAN/GERAN; and
- from UTRAN to UTRAN/GERAN. |
23.832 | IP Multimedia Subsystem (IMS) aspects of architecture for Home Node B (HNB); Stage 2 | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.832/23832-a00.zip | This Technical Report describes an IMS capable HNB SubSystem (the HNB and the HNB Gateway) as an optional capability of HNB that allows e.g. an operator to offload CS traffic to the IMS. The HNB and HNB Gateway are described in TR 23.830 [5], and the capabilities of these network elements are assumed by this TR.
To achieve this and to satisfy the related requirements and use cases captured in TS 22.220 [2], the objective is to investigate the following:
• an architecture to enable IMS capable HNB Subsystem to use the IMS for CS terminals using a corresponding equivalent IMS services (voice service in IMS Multimedia Telephony);
• the impacts of the IMS capable HNB Subsystem to idle mode mobility for all supported UE types (e.g. IMS registration/de-registration);
• service continuity at least in the direction from IMS capable HNB Subsystem to macro network;
• support for pre-Rel‑9 CS and IMS UEs when using IMS capable HNB Subsystem.
The TR will analyze solutions for the related architectural issues and capture the conclusions. |
23.860 | Enabling coder selection and rate adaptation for UTRAN and E-UTRAN for load adaptive applications; Stage 2 | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.860/23860-a00.zip | The system enhancements to enable codec rate adaptation at voice call setup over E-UTRA was standardized in Rel-9 in TS 23.401 [2].
The scope of this document is to study and specify enhancements to existing codec selection and codec rate adaptation based on network loading conditions and operator policies over UTRA and E-UTRA. Potential enhancements are definition of the signalling and interfaces enabling:
- To perform codec selection based on network loading conditions and operator policies during call establishment phase over both UTRA and E-UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) based on network loading conditions during call establishment phase over UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) for non-voice RTP-based services based on network loading conditions at call setup over E-UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) based on network loading indications during an on-going call over both UTRA and E-UTRA;
- Support of codec rate adaptation by IMS Core Network entities (e.g., MGCF/MGW, IBCF/TrGW, etc.);
- Setting of Maximum Bit Rate (MBR) to be greater than the Guaranteed Bit Rate (GBR) over E-UTRA.
The solutions can be moved to normative specifications independently of each other once the study on the particular solution has been concluded. |
23.834 | Study on General Packet Radio Service (GPRS) Tunelling Protocol (GTP) based S2b; Stage 2 | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.834/23834-a00.zip | The objective of this feasibility study is to investigate solutions and benefits for supporting a new GTP option for S2b network based mobility.
The study will develop the stage 2 message flows necessary to support S2b based on GTP and mobility between S5/S8 based on GTP and S2b based on GTP. |
23.894 | System enhancements for the use of IP Multimedia Subsystem (IMS) services in local breakout and optimal routeing of media | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.894/23894-a00.zip | This study intends to investigate the general problem of system enhancements for the use of IMS services in local breakout and optimal routeing of media.
In particular the above issues will be addressed identifying
- solutions for the home operator to control
- whether the IMS user may connect to a PDN in the visited network, and
- whether connections to PDNs provided from the home and visited network may exist in parallel;
- solutions to enable the IMS network to be aware of whether local breakout can be invoked or not;
- solutions to allow the home operator to determine which of the IMS sessions (for a given UE) can be handled in local breakout and which in home routed mode, and what information (e.g. operator's policies, customer's subscription profile, UE connectivity, and location of the remote end terminal/service) is needed for the decision;
- solutions to allow the UE to concurrently use IMS services through local breakout and other IMS services through home routeing;
- the feasibility of having the local breakout option in IMS service nodes:
- is there a need for a P-CSCF at both PDN accesses?
- if one P-CSCF is enough, what requirements are there for connectivity between the PDNs?
- if methods are necessary to discover an additional P-CSCF in the visited network after the UE has moved to the visited network, even if the network-layer mobility mechanisms can sustain IP connectivity to the previously discovered P-CSCF in the home network;
- the exact location of the decision point in the home network whether to use local breakout (application or delegated to IP-CAN);
- solutions for SIP/SDP signalling related to the use of IMS services through local breakout.
- interactions with network entities such as NAT (as specified in TS 23.228 [8]) when providing IMS services through local breakout;
- interactions with and support of PCC to provide IMS services through local breakout;
- security implications if there is need for multiple P-CSCFs per UE.
Moreover:
- describing a set of scenarios where the selection of an alternative media path (i.e., different to the signalling path) provides benefits to IMS operators by reducing the number of network entities in the media path;
- providing requirements for suitable mechanisms to achieve optimal media routeing;
- analysing the potential solution(s) to solve those scenarios in line with IMS procedures, while taking into account any impact of extensions required to existing functions/procedures (e.g., NAT, transcoding, Security, PCC, BCF, LI, etc.);
- reducing the number of options for solving the same requirement and agree on a preferred solution.
In the end this study will provide conclusions with respects to what further specification work is required in order to fulfil the requirements for the use of IMS services through local breakout and achieve optimal routeing of media. |
23.889 | Local Call Local Switch (LCLS) system impacts; Feasibility study | TR | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.889/23889-a00.zip | The present document provides a study into the Core Network impacts for providing a solution for Local Call Local Switching. The document analyses and evaluates different solutions to determine the benefits provided compared to the identified impacts.
Specific considerations are given to the following areas:-
- Sending of correlation information between the two legs of the call to the BSS
- Triggering to enable/release Local Call Local Switch (e.g. based on activation of Supplementary Services, etc.)
- Support of existing Supplementary Services
- Support of existing Lawful Intercept functionality
- Impacts to the user plane handling on the A-interface
- Impacts to the MSC-S – MGW Interface (Mc Interface)
- Impacts to the MSC-S – MSC-S Interface (Nc Interface)
The solution(s) considered for local call local switch should keep the core network impacts to a minimum, e.g. the impacts on the nodal functions, existing call flows, call establishment and call release.
The contents of this report when stable shall determine the modifications to existing core network specifications. |
23.831 | IP Multimedia Subsystem (IMS) service continuity; Inter-UE transfer enhancements; Stage 2 | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.831/23831-a00.zip | This technical report intends to develop enhancements to Rel-9 IMS Service Continuity in TS 23.237 [2], specifically in the functional area of Inter-UE Transfer. The main objective is to provide enhancements to mobility of media flows of a session between different UEs (Inter-UE Transfer) with respect to the following aspects:
- Extension of Inter-UE Transfer and Collaborative Session capabilities specified in Rel-09 to multiple UEs belonging to different IMS subscriptions under the same operator.
- Establishment of a Collaborative Session at session setup.
- Support for control of media components of a Collaborative Session by more than one UE simultaneously.
- Transfer of control of a Collaborative Session.
- Controller initiated media modification on a Controllee UE (e.g. video resolution).
- Discovery of ongoing IMS multimedia sessions on different UEs.
- Inter-UE Transfer initiated by the target UE when:
- the target UE belongs to the Collaborative Session but it is not a Controller UE;
- the target UE does not belong to the Collaborative Session and wants to join;
- Inter-UE Transfer is performed without establishing a Collaborative Session.
- Replication of an ongoing multimedia session from one UE on another UE.
- Inter-UE Transfer between UEs connected to the IMS via an IP-CAN and ICS entities that provide interworking with UEs in the CS Domain.
- Execution of MMTEL services for Collaborative Sessions.
This document contains the results of an assessment of alternative architectures to support Inter-UE Transfer enhancements. |
23.886 | Feasibility Study of Single Radio Video Call Continuity (vSRVCC); Stage 2 | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.886/23886-a00.zip | The objective of the feasibility study is to investigate a solution for supporting single radio the video call continuity from E-UTRAN/HSPA to UTRAN-CS based on the Rel-8/9 Single Radio Voice Call Continuity (SRVCC) architecture as specified in TS 23.216 [2] and TS 23.237 [3], and study the mechanisms to resolve the key issues. It is not expected that the SRVCC architecture will be modified unless any of the key issues cannot be resolved with the current architecture.
The study will be performed to the scenarios where IMS session using bidirectional voice and synchronised video such as defined in TS 22.173 [4], originated in E-UTRAN/HSPA and the UE moves to UTRAN and continues the service over UTRAN in the CS domain.
The video call continuity from E-UTRAN/HSPA to GERAN is not supported. |
23.976 | Push architecture | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-a00.zip | |
23.977 | Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-a00.zip | |
23.903 | Redial solution for voice-video switching | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-a00.zip | |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-a00.zip | |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-a00.zip | |
23.924 | Feasibility study on Non-Access Stratum (NAS) node selection function above Base Station Controller (BSC) / Radio Network Controller (RNC) | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.924/23924-a00.zip | |
23.919 | Direct tunnel deployment guideline | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-a00.zip | |
23.979 | 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 | TR | 10.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-a00.zip | |
24.022 | Radio Link Protocol (RLP) for circuit switched bearer and teleservices | TS | 10.0.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-a01.zip | |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-a00.zip | |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-a00.zip | |
24.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-a00.zip | |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-a00.zip | |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-a00.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.081 | Line Identification supplementary services; Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-a00.zip | |
24.082 | Call Forwarding (CF) supplementary services; Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-a00.zip | |
24.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-a00.zip | |
24.084 | Multi Party (MPTY) supplementary service; Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-a00.zip | |
24.085 | Closed User Group (CUG) supplementary service; Stage 3 | TS | 10.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-a00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.