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.327 | Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems | TS | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.327/23327-c00.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 | 12.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.333/23333-cc0.zip | |
23.259 | Personal Network Management (PNM); Procedures and information flows; Stage 2 | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-c00.zip | |
23.246 | Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description | TS | 12.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-c60.zip | |
23.335 | User Data Convergence (UDC); Technical realization and information flows; Stage 2 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.335/23335-c00.zip | |
23.380 | IMS Restoration Procedures | TS | 12.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.380/23380-c50.zip | |
23.292 | IP Multimedia Subsystem (IMS) centralized services; Stage 2 | TS | 12.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.292/23292-c50.zip | |
23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | TS | 12.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-cb0.zip | |
23.284 | Local Call Local Switch (LCLS); Stage 2 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.284/23284-c00.zip | |
23.468 | Group Communication System Enablers for LTE (GCSE_LTE); Stage 2 | TS | 12.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.468/23468-c70.zip | |
23.402 | Architecture enhancements for non-3GPP accesses | TS | 12.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.402/23402-ca0.zip | |
23.703 | Study on architecture enhancements to support Proximity-based Services (ProSe) | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.703/23703-c00.zip | The present document is limited to the Stage 2 study and evaluation of possible 3GPP technical system solutions for architectural enhancements needed to support Proximity-based Services (ProSe) based on the relevant Stage 1 requirements as defined in TS 22.278 [3] and TS 22.115 [4].
NOTE: Some aspects in this feasibility study have led into normative specification in TS 23.303 [26].The text of the present document was not updated to align with normative specifications. |
23.334 | IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions | TS | 12.13.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.334/23334-cd0.zip | |
23.701 | Study on Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS); Stage 2 | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.701/23701-c00.zip | The present document contains a study on the potential modifications of the IMS architecture and stage 2 procedures as required by the support of Web Real Time Communication (WebRTC) clients access to IMS.
For this purpose the present document addresses (non exhaustive list):
- Architectural impacts for the support of different kinds of clients (operator / Third party) in different scenarios.
- The architecture (including the support of WebRTC clients access to IMS for clients on a 3GPP UE that are roaming at access level) for following scenarios:
- when 3GPP or non-3GPP access is used (common IMS).
- when the UE is not roaming at access level or when home-routed access is used (these scenarios have priority for the work).
- evaluate/study whether IMS roaming architecture is used in case of 3GPP LBO.
- Media plane aspects e.g.:
- architectural impacts related to the use of specific codecs: the study addresses transcoding aspects but also the case where the use of 3GPP codecs is possible from the UE.
NOTE: How a WebRTC client / the browser can access to 3GPP codecs on the UE is out of the SA WG2 study scope.
- architectural impacts related to media plane security interworking.
- Authentication and Control plane security related aspects.
- Charging.
- PCC aspects.
- Usage of the 3GPP Packet Core Network to support WebRTC clients access to IMS.
For example the following points had been studied: the PDN connection / PDP context to be used by WebRTC traffic especially in roaming cases and the QoS control, e.g. how a WebRTC client can use the QoS supported / delivered by the 3GPP Packet Core. |
23.839 | Study on support of Broadband Forum (BBF) access Interworking | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.839/23839-c00.zip | Based on requirements documented in the stage 1 specifications, this technical report addresses system architecture impacts to support BBF Access Interworking. The study includes multiple phases and covers aspects such as basic connectivity, mobility, authentication and authorisation, policy and QoS aspects, IP Flow mobility, traffic offload, convergence etc.
In each Building Block, the TR describes what changes are expected to normative TSs, e.g. TS 23.402 [3] and TS 23.203 [4].
The work is divided into three separate Building Blocks. See clause 4 for an outline of the content of each building block. |
23.843 | Study on Core Network Overload (CNO) solutions | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.843/23843-c00.zip | The present document investigates core network signalling overload scenarios and potential general handling solutions, in particular:
1. Identify and document events that have occurred and caused network disturbances due to signalling overload. In addition, identify and document scenarios that have high probability of occurrence in the 3GPP network, which may result in signalling overload for core network entities. Such scenarios/events may include HLR/HSS overload by RNC restart, denial of service attacks, and misbehaving/3GPP-non-compliant mobiles causing unpredictable system response;
2. Analyse the criticality of the scenarios and determine whether it is required to take actions for the identified scenarios;
3. Study ways to mitigate and/or eliminate the impact on the core network from signalling overload scenarios that are identified to be critical.
The information provided about the HSS/HLR overload will serve as a starting basis for the study. All currently deployed 3GPP networks should be covered in the study, including LTE
The study should avoid overlap with other parallel activities within 3GPP, and work in close cooperation with the specific WG needs to be maintained.
During the study, if potential security threats such as denial of service attack scenarios are identified, SA WG3 must then be informed to take appropriate measures. |
23.844 | Feasibility study on IP Multimedia Subsystem (IMS) based peer-to-peer content distribution services; Stage 2 | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.844/23844-c00.zip | This study focuses on the enhancement of IMS to support Peer-to-Peer Content Distribution Services in respect of GPRS, EPC and other underlying access network technologies but not intend to modify GPRS or EPC for P2P mechanism.
The objectives are to study IMS based Peer-to-Peer Content Distribution Services on the architectural level with the following aspects:
- Creating solutions in order to fulfil the use cases and requirements as defined by SA WG1 while avoiding duplicate work in other SDOs, such as IETF [e.g., PPSP, P2PSIP, ALTO, and DECADE], and re-using their work. The solutions should:
- Apply the same IMS user management/registration procedure as other IMS services;
- Be able to provide the UE with the appropriate AS to obtain the addresses of other Peers, from which the UE can retrieve the requested content;
- Re-use ISC interface for service triggering;
- Be able to select qualified User Peers among available UEs according to the policies preconfigured in the network.
- Elaborate alternative solutions, which support the following network access technologies:
- Mobile access only (e.g. UTRAN, E-UTRAN, I-WLAN);
- Fixed access only (e.g. xDSL, LAN);
- Fixed and mobile convergence scenarios.
- Evaluate possible impacts and improvements on network when IMS based Peer-to-Peer Content Distribution Services are deployed, such as the interactions that are needed to adapt the peer-to-peer overlay properties to the configuration and the resources of the network.
- Identify QoS, mobility, charging and security related requirements in the case of Peer-to-Peer Content Distribution Services on IMS.
The assessment on alternative solutions and the final conclusion of this study should not only take TR 22.906 [2] into consideration but also comply with the related normative work in SA WG1. |
23.852 | Study on S2a Mobility based on GPRS Tunnelling Protocol (GTP) and Wireless Local Area Network (WLAN) access to the Enhanced Packet Core (EPC) network (SaMOG); Stage 2 | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.852/23852-c00.zip | This Study item is to study:
1. The addition of a S2a based on GTP option. In particular this SID will develop the necessary stage 2 message flows to support S2a based on GTP and mobility between GTP-S5/S8 and GTP-S2a.
2. Supporting WLAN access to EPC through S2a via mechanisms:
2.1 with no impact to the UE;
2.2 with impact to the UE.
Solutions requiring modifications to non 3GPP link-layers will not be considered. It is expected that the result of this Study Item may be used by 3GPP-BBF interworking activities (BBAI). |
23.853 | Operator Policies for IP Interface Selection (OPIIS) | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.853/23853-c00.zip | This Technical Report describes solutions that define:
- operator policies for selecting an IP interface in the UE for routing of IP flows among a choice of available interfaces in both 3GPP and non-3GPP accesses;
- system architecture for distribution of these policies to the UE.
Editor's note: The working assumption is that the ANDSF architecture is used for distribution of the operator policies defined in this TR.
The solutions described in this TR shall clarify how the operator policies defined in this TR relate with the ANDSF policies.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to select a solution and include it in the relevant technical specifications. |
23.858 | Usage Monitoring Control PCC Enhancement | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.858/23858-120.zip | The scope of this technical report is to capture the results of a study that investigates if enhancements to the existing policy control architecture are needed in the area of usage monitoring control. The goals of the study are to derive possible requirements and architecture enhancements for:
1. Monitoring of service (s) / application (s) in more than one usage monitoring group;
2. Disabling a service (s) / application (s) from the existing usage monitoring group of services/group of applications;
3. Excluding the usage of a particular service (s) / application (s) from the accumulated usage for the IP-CAN session/TDF session;
4. Usage control for a subscriber group, e.g. the members of a family or a company subscriber, or a group of devices belonging to subscribers that share the same usage allowance threshold.
In addition, study the different proposed solutions for effective time based usage monitoring and how associated start and end of usage is defined. |
23.859 | Local IP access (LIPA) mobility and Selected IP Traffic Offload (SIPTO) at the local network | TR | 12.0.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.859/23859-c01.zip | This Technical Report describes the solutions to implement the architectural aspects based on the requirements from TS 22.220 [3], clauses 5.7 and 5.9, and TS 22.101 [2], clause 4.3.5, for LIPA and SIPTO at the local network.
This includes:
- the support of mobility for LIPA between the H(e)NBs located in the local IP network;
- functionality to support Selected IP Traffic Offload requirements at the local network, including mobility.
The report is intended to document the analysis of the architectural aspects to achieve these objectives in order to include the solutions in the relevant technical specifications. |
23.862 | Evolved Packet Core (EPC) enhancements to support interworking with data application providers; Stage 2 | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.862/23862-c00.zip | This Technical Report describes solutions for interworking between mobile operators and data application providers. The solutions developed will describe a framework for authentication, authorization, policy and charging for various interworking scenarios.
Solutions developed as part of this work item will cover the following different relationships between mobile operators and data application providers for both roaming and non-roaming cases when
- mobile operator owns all the application layer entities;
- mobile operator does not own all the application layer entities.
The technical report will investigate charging, policy and group addressing capabilities for interworking between mobile operators and data application providers. Updates to 3GPP functions and interfaces will be specified for solutions based on IMS and/or EPC.
On-going work for authentication and other aspects in other 3GPP work items will not be duplicated. It will be investigated whether changes to 3GPP specifications are needed and if so which ones. The work item will focus on impacts to IMS and EPC. |
23.863 | Support of Short Message Service (SMS) in IP Multimedia Subsystem (IMS) without Mobile Station International ISDN Number (MSISDN); Stage 2 | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.863/23863-c00.zip | This Technical Report is to specify architecture enhancement toward SMS submit/delivery mechanism in IMS to allow IMS registered UE to:
- Receive and send SMS without requiring an MSISDN associated as part of their IMS subscription record in HSS and
- any possible enhancements towards the related storing and forwarding mechanism if the UE is out of reach.
There are three potential aspects for these IMS UEs without MSISDN that need to be investigated:
1) Server - IMS UE communication via SMS (e.g. for M2M).
2) IMS UE to IMS UE communication via SMS for person to person communications. Both UEs do not have MSISDN.
3) SMS Interworking between IMS UE without MSISDN and traditional UE (e.g. CS) with MSISDN.
Normative specification work (if needed or feasible) for each of these areas can be started independently. |
23.865 | Study on Wireless Local Area Network (WLAN) network selection for 3GPP terminals; Stage 2 | TR | 12.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.865/23865-c10.zip | This Technical Report describes enhancements to solutions for WLAN network selection. The solutions are based on architectures as specified in TS 23.402 [9] and will take into account Hotspot 2.0 specifications developed by the WFA. 3GPP operator's policies for WLAN network selection will be provisioned on 3GPP terminals via pre-configuration or using the ANDSF server for their delivery. The scope of the technical report will be as follows:
1. Evaluate existing 3GPP WLAN PLMN and access network selection procedures for 3GPP terminals which use Hotspot 2.0 procedures and provisioned network operator policy (e.g. mechanisms based on WLAN and ANDSF) for any needed changes to current specifications. This may require enhancements to the ANDSF framework. The established 3GPP PLMN network selection (according to TS 23.122) shall not be impacted. The work must ensure there are no conflicts between existing 3GPP PLMN network selection and the 3GPP WLAN PLMN access network selection procedures defined by this WID.
2. Ensure that the content in the Management Object related to 3GPP operator policy provisioning for WLAN network selection procedures and the operator policy provisioning in WFA MO for WLAN network selection are consistent.
3. Identify solutions to resolve potential conflicts between policies provided by non-3GPP providers via Hotspot 2.0 mechanisms and policies provided by 3GPP operators using ANDSF.
This work applies to non-seamless WLAN offload as well as to trusted and untrusted WLAN access to EPC with/without seamless offload. It will be investigated whether changes to 3GPP specifications are needed and if so which ones. |
23.866 | Study on system improvements for energy efficiency | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.866/23866-c00.zip | The present document is for investigating deployment aspects that relate to energy efficiency, including potential system enhancements that support energy efficient deployments. System enhancements may be anticipated in the area of functions that have major influence on deployment like functions that support pools of CN nodes or functions that enable multiple CN nodes to serve the same or overlapping areas. The initial focus is on PS domain. This study should avoid any overlap with the work by RAN/CT/SA5 by taking into account the work that has been and is going on in these WGs. Proposals have to be well justified to be considered in this document. |
23.887 | Study on Machine-Type Communications (MTC) and other mobile data applications communications enhancements | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.887/23887-c00.zip | The present document studies and evaluates architectural enhancements for Machine-Type and other mobile data applications Communications.
Specifically, the following system improvements are considered:
- Small Data Transmission (SDT) which includes the following aspects:
- SDT as per the service requirements (TS 22.368, clause 7.2.5); and
- Efficient handling of frequent SDT as per the service requirement (TS 22.101, clause 4.3.1).
- Triggering enhancements which includes the following aspects:
- Device triggering enhancements including T5 based device trigger and other triggering efficiency optimizations.
- Monitoring enhancements which includes the following aspect:
- Monitoring as per the service requirements (TS 22.368, clause 7.2.8).
- UE Power optimizations which includes the following aspects:
- Optimizations to prevent battery drain (that may come from e.g. frequent changes between idle and connected mode or too long periods in connected mode); and
- Lower UE power consumption as per the service requirements (TS 22.368, clause 7.1.1).
- Group based features which include the following aspects:
- Fulfil the group based policing requirements (TS 22.368 clause 7.2.14.2);
- Fulfil the group based addressing requirements (TS 22.368 clause 7.2.14.3); and
- Fulfil the group based charging requirements (TS 22.368 clause 7.1.5).
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services as provided by the 3GPP system and the related optimizations are considered in this study.
The present document analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications. |
23.890 | Optimized offloading to Wireless Local Area Network (WLAN) in 3GPP Radio Access Technology (RAT) mobility | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.890/23890-c00.zip | This technical report describes key issues and solutions for optimized offloading of traffic to WLAN access when PS mobility between 3GPP RAT takes place. The technical report analyzes the user and service impact due to mobility between 3GPP RATs. The technical report analyzes the key issues and solutions in order to identify whether current mechanisms documented in SA2 specifications are sufficient, identify potential inefficiencies, and identify whether additional solutions are needed to address the key issues.
The technical report also describes proposed extensions to ANDSF in order to enable policy differentiation for 3GPP RATs (e.g. E-UTRAN versus UTRAN, GERAN versus UTRAN) with respect to WLAN, in order to enable a UE to distinguish preferences of WLAN with respect to specific 3GPP RATs upon acquiring connectivity (e.g. PDN creation in a 3GPP RAT or WLAN, or establishing NSWO connectivity) or upon mobility. |
23.897 | Feasibility study on IP Multimedia Subsystem (IMS) business trunking for Internet Protocol Private Branch Exchange (IP-PBX) in Static Mode of Operation | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.897/23897-c00.zip | During the production of the 3GPP Release 7 specifications it was recognized that the IP Multimedia Subsystem was suitable for serving both mobile and fixed installations and a number of specifications developed by ETSI TISPAN were therefore embedded in the 3GPP specifications to form the Common IMS. Among other aspects, Common IMS requires that the IMS is able to connect with Next Generation Corporate Networks (NGCN), also known as IP-PBXs (see ETSI TS 181 019 [3]).
Managing the connection to IP-PBXs which do not use registration procedures when connecting to the IMS and operate in a static mode that is to enable the IMS to receive and send traffic to an IP-PBX, is realized by means of configuration within the network. The static mode of operation can be used in 2 scenarios, peering based business trunking and subscription based business trunking. The static mode of operation for both of the above mentioned scenarios can be studied in this TR.
It was however observed that the number of implementations of IP-PBXs that are operated in a static mode (e.g. based on the SIPConnect specifications recently released by the SIP Forum) increases.
The purpose of this study is to enable the IMS to manage connections to a large number of IP-PBXs that are operated in a static mode, with minimized configuration in the network. |
23.903 | Redial solution for voice-video switching | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-c00.zip | |
23.919 | Direct tunnel deployment guideline | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-c00.zip | |
23.924 | Feasibility study on Non-Access Stratum (NAS) node selection function above Base Station Controller (BSC) / Radio Network Controller (RNC) | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.924/23924-c00.zip | |
23.975 | IPv6 migration guidelines | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-c00.zip | |
23.976 | Push architecture | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-c00.zip | |
23.977 | Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-c00.zip | |
23.979 | 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-c00.zip | |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-c00.zip | |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-c00.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-c00.zip | |
23.800 | Study on Application Based Charging (ABC); Stage 2 | TR | 12.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.800/23800-c00.zip | This Technical Report defines key issues and studies PCEF/TDF charging solutions for the network usage of services and applications when TDF performs application detection and control. Both online and offline charging aspects will be considered. The work will be based on the Rel‑11 Policy and charging control architecture, including the specification for application detection and control and the corresponding TDF functionality definition, as defined in TS 23.203 [3].
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces will be identified.
The agreed solutions will be evaluated for subsequent normative specification. |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-c00.zip | |
23.768 | Study on architecture enhancements to support Group Communication System Enablers for LTE (GCSE_LTE) | TR | 12.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.768/23768-c10.zip | The present document captures the results of the study and evaluation of possible solutions for architectural enhancements to support Group Communication System Enablers for LTE (GCSE_LTE). The Stage 1 requirements for GCSE_LTE are defined in TS 22.468 [3].
Specifically, GCSE_LTE covers the following aspects:
- Group Communication (GC) among entitled group members via E-UTRAN;
- Group Communication (GC) among entitled group members using E-UTRAN and members of the same group using ProSe communication paths via a ProSe UE-to-Network Relay;
- The relationship between ProSe and GCSE for GCs.
The functional descriptions of "ProSe communication paths via ProSe UE-to-Network Relay" and "ProSe GCs" have been defined in TR 23.703 [4]. |
23.682 | Architecture enhancements to facilitate communications with packet data networks and applications | TS | 12.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.682/23682-c40.zip | |
24.022 | Radio Link Protocol (RLP) for circuit switched bearer and teleservices | TS | 12.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-c00.zip | |
24.011 | Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-c00.zip | |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-c00.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.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-c00.zip | |
24.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-c00.zip | |
24.084 | Multi Party (MPTY) supplementary service; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-c00.zip | |
24.085 | Closed User Group (CUG) supplementary service; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-c00.zip | |
24.086 | Advice of Charge (AoC) supplementary services; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.086/24086-c00.zip | |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-c00.zip | |
24.088 | Call Barring (CB) supplementary service; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.088/24088-c00.zip | |
24.081 | Line Identification supplementary services; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-c00.zip | |
24.091 | Explicit Call Transfer (ECT) supplementary service; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.091/24091-c00.zip | |
24.093 | Completion of Calls to Busy Subscriber (CCBS); Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.093/24093-c00.zip | |
24.082 | Call Forwarding (CF) supplementary services; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-c00.zip | |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-c00.zip | |
24.090 | Unstructured Supplementary Service Data (USSD); Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.090/24090-c00.zip | |
24.135 | Multicall supplementary service; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.135/24135-c00.zip | |
24.096 | Name Identification supplementary services; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.096/24096-c00.zip | |
24.087 | User-to-User Signalling (UUS) Supplementary Service; Stage 3 | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.087/24087-c00.zip | |
24.141 | Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 12.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.141/24141-c10.zip | |
24.109 | Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details | TS | 12.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.109/24109-c30.zip | |
24.147 | Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 12.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.147/24147-c70.zip | |
24.166 | 3GPP IP Multimedia Subsystem (IMS) conferencing Management Object (MO) | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.166/24166-c00.zip | |
24.167 | 3GPP IMS Management Object (MO); Stage 3 | TS | 12.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.167/24167-c30.zip | |
24.171 | Control Plane Location Services (LCS) procedures in the Evolved Packet System (EPS) | TS | 12.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.171/24171-c00.zip | |
24.173 | IMS Multimedia telephony communication service and supplementary services; Stage 3 | TS | 12.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.173/24173-c30.zip | |
24.182 | IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification | TS | 12.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.182/24182-c20.zip | |
24.183 | IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification | TS | 12.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.183/24183-c20.zip | |
24.216 | Communication Continuity Management Object (MO) | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.216/24216-c00.zip | |
24.103 | Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3 | TS | 12.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.103/24103-c60.zip | |
24.237 | IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 | TS | 12.14.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.237/24237-ce0.zip | |
24.139 | 3GPP system - fixed broadband access network interworking; Stage 3 | TS | 12.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.139/24139-c10.zip | |
24.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 | TS | 12.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.234/24234-c20.zip | The present document specifies the network selection, including authentication and access authorization using authentication, authorization and accounting (AAA) procedures used for the interworking of the 3GPP system and WLANs. In addition to these, the present document also specifies the tunnel management procedures used for establishing an end-to-end tunnel from the WLAN UE to the 3GPP network via the Wu reference point.
The present document is applicable to the WLAN user equipment (UE) and the network. In this technical specification the network includes the WLAN and 3GPP network.
Tunnel management signalling is carried between WLAN-UE and WLAN by WLAN access technology specific protocols, however this signalling is transparent to the WLAN.
Tunnel management procedures are defined to be independent of the underlying WLAN access technology and as such can be reused independently of the underlying technology.
The present document specifies procedures within I-WLAN necessary in order for IMS emergency calls to be supported when I-WLAN is used as the underlying access network. These involve both network selection as well as tunnel management procedures.
WLAN Network Selection supersedes I-WLAN for UE WLAN selection as specified in 3GPP TS 24.302 [28] from Rel-12 onwards.
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. |
24.235 | 3GPP System to Wireless Local Area Network (WLAN) interworking Management Object (MO) | TS | 12.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.235/24235-c10.zip | This document defines the 3GPP System to Wireless Local Area Network interworking Management Object (MO) for I-WLAN PLMN selection as specified in 3GPP TS 24.234 [3]. The management object is compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA-ERELD_DM-V1_2 [2].
The 3GPP System to Wireless Local Area Network interworking Management Object consists of relevant parameters that can be managed for WLAN UE as specified in 3GPP TS 24.234 [3].
The Access Network Discovery and Selection Function MO as specified in 3GPP TS 24.312 [13] supercedes the Wireless Local Area Network interworking MO for I-WLAN PLMN selection from Rel-12 onwards.
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. |
24.244 | Wireless LAN control plane protocol for trusted WLAN access to EPC; Stage 3 | TS | 12.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.244/24244-c30.zip | |
24.239 | Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.239/24239-c00.zip | |
24.247 | Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.247/24247-c00.zip | The present document provides the protocol details for the messaging service within the IP Multimedia CN Subsystem (IMS) based on the Session Initiation Protocol (SIP), the Session Description Protocol (SDP) and, the Message Session Relay Protocol (MSRP) . The document covers immediate messaging, session based messaging and session-based messaging conferences, as described in 3GPP TS 22.340 [11].
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SDP and, MSRP, either directly, or as modified by 3GPP TS 24.229 [5].
The present document is applicable to Application Servers (ASs) , Media Resource Function Controllers (MRFCs), Media Resource Function Processors (MRFPs) and to User Equipment (UE) providing messaging capabilities.
This document does not cover the signalling between a MRFC and a MRFP. |
24.286 | IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Management Object (MO) | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.286/24286-c00.zip | |
24.259 | Personal Network Management (PNM); Stage 3 | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.259/24259-c00.zip | |
24.294 | IP Multimedia Subsystem (IMS) Centralized Services (ICS) protocol via I1 interface | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.294/24294-c00.zip | The present document describes the I1 interface between IMS Centralized Services (ICS) UE and Service Centralization and Continuity (SCC) Application Server (AS).
This specification defines a new application layer protocol over I1 interface, specifies the interaction between the ICS UE and the SCC AS including session control procedures and supplementary services control procedures.
The protocol is intended to be independent of the transport-layer protocol used so it can be applied to a number of technologies that need different transport-layer protocols.
The overall ICS architecture is specified in 3GPP TS 23.292 [2].
The procedures for delivery of IMS Service Continuity that do not use the I1 protocol are specified in the document 3GPP TS 24.237 [13].
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the IMS centralized services. |
24.302 | Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 | TS | 12.12.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.302/24302-cc0.zip | The present document specifies the discovery and network selection procedures for access to 3GPP Evolved Packet Core (EPC) via non-3GPP access networks and includes Authentication and Access Authorization using Authentication, Authorization and Accounting (AAA) procedures used for the interworking of the 3GPP EPC and the non-3GPP access networks.
The present document also specifies the Tunnel management procedures used for establishing an end-to-end tunnel from the UE to the ePDG to the point of obtaining IP connectivity and includes the selection of the IP mobility mode.
The non-3GPP access networks considered in this present document are cdma2000® HRPD and Worldwide Interoperability for Microwave Access (WiMAX), and any access technologies covered in 3GPP TS 23.402 [6]. The present document also specifies UE access to PLMN IP-based services via restrictive non-3GPP access networks covered in 3GPP TS 33.402 [15]. These non-3GPP access networks can be trusted or untrusted access networks.
The present document is applicable to the UE and the network. In this technical specification the network is the 3GPP EPC.
NOTE: cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA). |
24.285 | Allowed Closed Subscriber Group (CSG) list; Management Object (MO) | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.285/24285-c00.zip | |
24.292 | IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3 | TS | 12.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.292/24292-ca0.zip | |
24.279 | Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 3 | TS | 12.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.279/24279-c10.zip | |
24.305 | Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO) | TS | 12.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.305/24305-c20.zip | |
24.238 | Session Initiation Protocol (SIP) based user configuration; Stage 3 | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.238/24238-c00.zip | |
24.315 | IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3: protocol specification | TS | 12.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.315/24315-c10.zip | |
24.322 | Tunnelling of IP Multimedia Subsystem (IMS) services over restrictive access networks; Stage 3 | TS | 12.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.322/24322-c10.zip | The present document specifies procedures and protocol elements for tunnelling of IMS traffic over restrictive access networks, specifically procedures and protocol elements for establishing, maintaining, and sending traffic via a firewall traversal tunnel between the UE and an enhanced firewall traversal function (EFTF) in the network. The present document is applicable to UE and EFTF.
The present document applies only to the case when the IMS traffic is not routed via EPC of a PLMN. Procedures for tunnelling of IMS traffic that is routed via EPC are specified in 3GPP TS 24.302 [3] annex F. |
24.327 | Mobility between 3GPP Wireless Local Area Network (WLAN) interworking (I-WLAN) and 3GPP systems; General Packet Radio System (GPRS) and 3GPP I-WLAN aspects; Stage 3 | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.327/24327-c00.zip | This document specifies the signalling procedures for handling the mobility of a UE between 3GPP Wireless Local Area Network Interworking (I-WLAN) and GPRS systems.
The present document is applicable to the User Equipment (UE) and the network nodes supporting mobility between 3GPP I-WLAN and GPRS systems.
In addition, the present document specifies the procedures used between the UE and the network nodes for the attach and the detach cases. It also specifies how the UE performs handover when moving from 3GPP I-WLAN to GPRS systems and vice-versa.
This document is based on DSMIPv6 procedures specified in 3GPP TS 24.303 [3] and will specify additional details specific to the 3GPP I-WLAN and GPRS systems in the context of mobility. |
24.304 | Mobility management based on Mobile IPv4; User Equipment (UE) - foreign agent interface; Stage 3 | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.304/24304-c00.zip | |
24.303 | Mobility management based on Dual-Stack Mobile IPv6; Stage 3 | TS | 12.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.303/24303-c00.zip | The present document specifies the signalling procedures for accessing the 3GPP Evolved Packet Core network and handling the mobility between 3GPP and non-3GPP accesses via the S2c reference point defined in 3GPP TS 23.402 [3].
The present document is applicable to the User Equipment (UE) and the network node implementing the Home Agent functionality.
In addition the present document specifies the procedures used for the DSMIPv6 Home Agent discovery, for bootstrapping the DSMIPv6 security association between the UE and the Home Agent and for managing the DSMIPv6 tunnel. The specification of these procedures is compliant to IETF RFCs.
DSMIPv6 procedures can be used independently of the underlying access technology. |
24.312 | Access Network Discovery and Selection Function (ANDSF) Management Object (MO) | TS | 12.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.312/24312-cb0.zip | |
24.368 | Non-Access Stratum (NAS) configuration Management Object (MO) | TS | 12.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.368/24368-c40.zip | |
24.371 | Web Real-Time Communications (WebRTC) access to the IP Multimedia (IM) Core Network (CN) subsystem (IMS); Stage 3; Protocol specification | TS | 12.12.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.371/24371-cc0.zip | |
24.334 | Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3 | TS | 12.6.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.334/24334-c61.zip | |
24.391 | Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem (IMS) Management Object (MO) | TS | 12.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.391/24391-c20.zip | |
24.333 | Proximity-services (ProSe) Management Objects (MO) | TS | 12.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.333/24333-c50.zip | |
24.337 | IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transfer; Stage 3 | TS | 12.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.337/24337-c30.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.