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.468 | Group Communication System Enablers for LTE (GCSE_LTE); Stage 2 | TS | 13.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.468/23468-d30.zip | |
23.705 | Study on system enhancements for user plane congestion management | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.705/23705-d00.zip | The present document studies and defines system enhancements for user plane congestion management based on the Stage-1 normative requirements defined in TS 22.101 [3].
Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
Normative specifications will be developed based on the conclusions of the present document. |
23.706 | Study on enhancements to Web Real Time Communication (WebRTC) access to IP Multimedia Subsystem (IMS); Stage 2 | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.706/23706-d00.zip | This document studies enhancements to the IMS architecture and stage 2 procedures in order to support the requirements defined by SA1 as part of eWebRTCi (Enhancements to WEBRTC interoperability).
The output of this work will not require changes to existing WebRTC enabled web browsers. |
23.707 | Architecture enhancements for dedicated core networks; Stage 2 | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.707/23707-d00.zip | An operator may choose to deploy one (or more) dedicated core networks within a PLMN with each core network dedicated for specific type(s) of subscriber. The present document studies and evaluates architectural enhancements required to support dedicated core networks. The specific dedicated core network that serves a UE is selected based on subscription information and operator configuration, without requiring the UEs to be modified.
The technical report covers both assignment of dedicated core network nodes and maintaining the association during mobility. Roaming and network sharing aspects of dedicated core network, and impacts on procedures such as CSFB, SRVCC and rSRVCC will be studied.
Dedicated core networks may be in the PS domain or CS domain or both. |
23.708 | Architecture enhancements for service capability exposure | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.708/23708-d00.zip | The present document studies and evaluates architecture enhancements for a service capability exposure framework wherein 3GPP system provided service capabilities are exposed via one or more standardized APIs, e.g. the OMA-API(s). As part of this work it will be identified how the APIs and the 3GPP system functionality act together to expose 3GPP service capabilities. The definition of APIs is out of scope of this work item.
The present document will also define the architectural enhancements for new service capabilities and services (based on the Stage 1 normative requirements) that are exposed via the service capability exposure framework. |
23.709 | Study on optimizations to support high latency communications; Stage 2 | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.709/23709-d00.zip | This document captures the study result of possible system enhancements to support applications that communicate with devices that are not reachable for a long period over the 3GPP IP connectivity and being able to support large number of such devices in the system without negatively affecting the system performance.
In addressing the above, the following problem is studied:
- Downlink access for devices that are not reachable for a long period and the problems associated with such devices (e.g. packet discard when the UE sleeps, frequent retransmissions, load on the CN network, waste of radio resources and UE power when the network unnecessarily conveys retransmit packets, etc.). This study may propose and evaluate enhancements to the 3GPP system. Depending on conclusions, the study may also propose 3GPP enablers to be used by the service layer e.g. defined by other SDOs for downlink access to devices that are not reachable for a long period.
Different application layer protocols used within the M2M ecosystem have different requirements and characteristics with respect to acceptable end-to-end delay, round trip time, persistence in retransmissions, etc. The result of this study may include general recommendations for application layers how to use the 3GPP accesses for better application performance and optimal core and radio network efficiency thereof. |
23.712 | Study on warning status reporting | TR | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.712/23712-d00.zip | The present document investigates possible enhancements to the Warning Status Reporting mechanisms specified up to release 12 in 3GPP TS 23.041 [2].
The study will cover:
- identification of requirements for Warning Status reporting;
- identification and evaluation of alternatives for Warning Status reporting;
- analysis on their potential interactions with the existing mechanisms; and
- recommendations on the alternatives.
The result of this study will be used to identify the changes possibly required in the 3GPP specifications to support enhanced Warning Status reporting mechanisms. |
23.713 | Study on extended architecture support for proximity-based services | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.713/23713-d00.zip | The scope of this Technical Report is to study and evaluate the possible architecture enhancements to the Proximity-based Services (ProSe) system defined in TS 23.303 [3], based on the relevant Stage 1 requirements defined in TS 22.278 [4] and TS 22.115 [5].
The present Technical Report documents the analysis and general principles agreed regarding these objectives, and collects the solution details developed based on these agreements, in order to progress them to the relevant specifications. |
23.682 | Architecture enhancements to facilitate communications with packet data networks and applications | TS | 13.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.682/23682-db0.zip | |
23.704 | Study on Circuit Switched (CS) / Packet Switched (PS) coordination in shared network; Stage 2 | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.704/23704-d00.zip | The present document investigates relevant scenarios and possible solutions to enhance the CS/PS Coordination in a shared UTRAN/GERAN network as currently specified in TS 23.251 [2].
Within this technical report relevant mobility scenarios shall be investigated and it shall be evaluated per scenario if any issues with CS/PS Coordination can be expected. The investigation shall be done for non-supporting UEs and for any UE in shared networks where no Multiple PLMN list is broadcasted. Solutions to solve found issues shall be evaluated and agreed for subsequent normative specification.
The scenarios that need to be handled will at least include:
- CS handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- PS Handover to UTRAN/GERAN (DTM/non-DTM for GERAN);
- Redirection;
- Cell reselection;
- CSFB;
- rSRVCC and SRVCC;
- PLMN selection at handover based on UE capability;
- Registration to PS domain in a shared network after CS only registration has been performed. |
23.769 | Group based enhancements | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.769/23769-d00.zip | The present document studies and evaluates architectural enhancements required for Group based features which include the following aspects:
- Fulfil the general group based requirements (TS 22.368 [2] clause 7.2.14.1)
- Fulfil the group based policing requirements (TS 22.368 [2] clause 7.2.14.2)
- Fulfil the group based addressing requirements (TS 22.368 [2] clause 7.2.14.3)
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. |
23.770 | Study on system impacts of extended Discontinuous Reception (DRX) cycle for power consumption optimization | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.770/23770-d00.zip | The present document studies the core network and NAS impacts in UE of extending DRX cycle for both idle mode and connected mode, solutions in the core network to support it, and interactions between GERAN/RAN and Core Network. Also, basic assumptions may be done for each solution on GERAN/RAN aspects of extending DRX cycle.
The main goal is to identify which open issues remained from the Rel‑12 study for extended Idle and Connected mode DRX as described in TR 23.887 [4] (as documented in clause 7.1.3.1 and 7.1.3.6 of TR 23.887), document potential solutions and conclude on which feasible solutions would be adopted in core network (pending work in RAN regarding extension of DRX cycle).
No connected mode mobility enhancements for extended C-DRX are considered in this work, i.e., if a UE using extended C-DRX moves to a different cell, current connected mode mobility procedures apply. |
23.771 | Study on system impacts of IP Multimedia Subsystem (IMS) emergency sessions over Wireless Local Area Network (WLAN) | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.771/23771-d00.zip | The present document studies the mechanisms needed to support IMS Emergency sessions over WLAN (both in the Trusted -S2a - and in the untrusted -S2b- cases)
The study is split up into 2 phases corresponding to 2 SID (FS_SEW1 and FS_SEW2).
Topics to be studied in phase 1 (FS_SEW1) are:
- Providing access to EPC over WLAN in order to support an emergency session only in case of "Valid" UEs as in the case 1 in clause 4.3.12.1 of TS 23.401 [3]: the support of emergency session is only studied for UEs which (a) have valid credentials to access EPC over WLAN and (b) are authorized to connect to EPC over WLAN in the location where they initiate an emergency session.
- Providing Location information (in particular for untrusted WLAN). Only existing location determination mechanisms are considered i.e. location determination mechanisms that should not require standard effort. No location accuracy requirements are considered in phase 1.
Phase 1(FS_SEW1) will not consider solutions that imply specification activities in other SDO(s).
Topics to be studied in phase 2 (FS_SEW2) correspond to all the features not covered by phase 1, e.g.:
- Support of other cases for the access to EPC over WLAN (e.g. the UE is authenticated but is in a location where it is restricted from regular service, or is unauthenticated or has no USIM).
- Roaming cases (user not in his / her home country).
- Support of session continuity of emergency sessions at inter-access mobility.
- TWAN access. |
23.772 | Enhanced Circuit Switched (CS) fallback | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.772/23772-100.zip | Editor's note: This clause will describe the work scope of the work item.
The present document studies enhancements for CSFB in the interest of shortening the call setup time. Based on the technical analysis, any needed enhancements/updates to 3GPP functions and interfaces are identified.
There shall be no UE impact.
Normative specifications may be developed based on the conclusions of the present document. |
23.779 | Study on application architecture to support Mission Critical Push To Talk over LTE (MCPTT) services | TR | 13.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.779/23779-d00.zip | This Technical Report contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for the Mission Critical Push To Talk over LTE (MCPTT) application. This TR will identify the architecture needed to support MCPTT services based on the Stage 1 requirements, including TS 22.179 [2]. This Technical Report depends on functionality specified in 3GPP specifications. |
23.789 | Monitoring Enhancements | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.789/23789-d00.zip | The present document studies and evaluates architectural enhancements required for 3GPP systems to provide monitoring service capability as per the service requirements defined in TS 22.368 [2], clause 7.2.8 and TS 22.101 [10], clause 29.2.
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. |
23.797 | Study on architecture enhancements to support isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.797/23797-d00.zip | This Technical Report contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for architectural enhancements needed to support Isolated E-UTRAN operation for public safety based on the Stage 1 requirements in TS 22.346 [3]. |
23.858 | Usage Monitoring Control PCC Enhancement | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.858/23858-d00.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.861 | Network based IP flow mobility | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.861/23861-d00.zip | Release 8 EPS introduced a multi access 3GPP system where different heterogeneous access systems are connected to a common core network. However, in Release 8 EPS, the subscriber cannot communicate using multiple accesses simultaneously. The subscriber can establish a single PDN connection or multiple simultaneous PDN connections in Release 8 EPS, but all the traffic exchanged by the subscriber, regardless of the PDN connection it belongs to, is routed through the same access system. Similarly, Release 8 introduced mobility enhancements to the I-WLAN architecture to support session continuity for any application between 3GPP and I-WLAN accesses, but this will not be further developed in Rel‑13.
Devices with multiple wireless interfaces (e.g. 3GPP , WLAN, etc.) are becoming commonly available and the set of applications running in the mobile devices is diversifying with some applications suited to run over 3GPP access systems and other applications well suited to run over some other - complementary - access systems (e.g. ftp transfer via WiFi in parallel to VoIP over LTE).
The scope of this document is to study the scenarios, requirements and solutions for UEs with multiple interfaces which will simultaneously connect to 3GPP access and one, and only one, non-3GPP WLAN access.
The clause 7.1 refer to the study for the support of IP flow mobility for s2c completed in Rel‑10 and the results have been transferred in TS 23.261. This clause will not be modified nor maintained during Rel‑13 work. Solutions which was studied includes the possibility of dynamically routeing to specific accesses individual flows generated by the same or different applications belonging to the same PDN connection. The study of solutions to support routing of different PDN connections through different access systems is also in the scope of this TR. This study item also investigates the mechanisms for provisioning the UE with operator's policies for multi access PDN connectivity and flow mobility.
The scope of Rel‑13 work is to identify the requirements and solutions for UEs with multiple interfaces which are simultaneously connected to 3GPP access and a WLAN access using a network-based mobility protocol, PMIP and GTP based S2a and S2b access to EPS.
The solutions studied from Rel‑13 consider the following aspects:
- The support of a PDN Connection active over multiple accesses simultaneously.
- The association of one or multiple IP flows belonging to a PDN connection to an access system.
- The movement of one or multiple IP flows belonging to a PDN connection between different access systems.
- The triggers for IP flow mobility in the UE and the network.
- UE-initiated and network-initiated NBIFOM.
- The impact and the relationship to 3GPP related policies (e.g. PCC, ANDSF, ISRP, ISMP, RAN policy with no ANDSF etc.), if any, to support NBIFOM.
This work item doesn't include the scenario where the same IP flow is routed via different access system simultaneously.
Scenarios and solutions described in this document are applicable independently of whether IMS or non-IMS applications are used. |
23.718 | Architecture enhancement for flexible mobile service steering | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.718/23718-d00.zip | The present document studies and evaluates architectural enhancements required for 3GPP systems to provide flexible mobile service steering policies as per the service requirements defined in TS 22.101 [2], clause 30.
NOTE: Service enablers supported within the (S)Gi-LAN and the routing of traffic between those service enablers are not in the scope. The scope of the work is restricted to providing policies for traffic steering through interfaces defined by 3GPP. |
23.720 | Study on architecture enhancements for Cellular Internet of Things (CIoT) | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.720/23720-d00.zip | The present document studies and evaluates the architecture enhancement to support ultra-low complexity, power constrained, and low data-rate 'Internet of Things' devices.
The study will consider architecture enhancements/simplifications in the following areas:
- Support of highly efficient handling of frequent and infrequent small data transmissions (e.g. based on the traffic model in TR 45.820 [4]) with minimised overhead for system signalling without compromising e.g. security.
- Support of power consumption optimisations and/or using existing ones that have been developed for EPS or GPRS.
- Assessing simplification of Mobility Management and Session Management procedures.
- Support of paging optimisations for UEs requiring coverage enhancements.
The present document will also consider system architecture alternatives to address the points above. |
23.741 | Study on enhancements to Multimedia Broadcast/Multicast Service (MBMS) for LTE | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.741/23741-d00.zip | The objective of this Technical Report is to study and specify potential modifications to the MBMS/GCSE_LTE architectures and/or procedures as specified in TS 23.246 [2] and TS 23.468 [3] to enable the following improvements and enhancements:
1. to allow the establishment of MBMS bearers using target area information, as distinct from using an MBMS Service Area;
2. to MBMS congestion handling;
3. if seen to be needed, to possible MBMS roaming scenarios;
4. as required by the MCPTT application work. |
23.975 | IPv6 migration guidelines | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-d00.zip | |
23.976 | Push architecture | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-d00.zip | |
23.977 | Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-d00.zip | |
23.903 | Redial solution for voice-video switching | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-d00.zip | |
23.919 | Direct tunnel deployment guideline | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-d00.zip | |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-d00.zip | |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-d00.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-d00.zip | |
24.011 | Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface | TS | 13.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-d50.zip | |
24.022 | Radio Link Protocol (RLP) for circuit switched bearer and teleservices | TS | 13.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-d00.zip | |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-d00.zip | |
24.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-d00.zip | |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-d00.zip | |
23.924 | Feasibility study on Non-Access Stratum (NAS) node selection function above Base Station Controller (BSC) / Radio Network Controller (RNC) | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.924/23924-d00.zip | |
24.081 | Line Identification supplementary services; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-d00.zip | |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-d00.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.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-d00.zip | |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-d00.zip | |
24.082 | Call Forwarding (CF) supplementary services; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-d00.zip | |
24.084 | Multi Party (MPTY) supplementary service; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-d00.zip | |
24.086 | Advice of Charge (AoC) supplementary services; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.086/24086-d00.zip | |
24.085 | Closed User Group (CUG) supplementary service; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-d00.zip | |
23.979 | 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 | TR | 13.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-d00.zip | |
24.090 | Unstructured Supplementary Service Data (USSD); Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.090/24090-d00.zip | |
24.096 | Name Identification supplementary services; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.096/24096-d00.zip | |
24.087 | User-to-User Signalling (UUS) Supplementary Service; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.087/24087-d00.zip | |
24.103 | Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3 | TS | 13.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.103/24103-d30.zip | |
24.105 | Application specific Congestion control for Data Communication (ACDC) Management Object (MO) | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.105/24105-d10.zip | |
24.109 | Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.109/24109-d10.zip | |
24.135 | Multicall supplementary service; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.135/24135-d00.zip | |
24.139 | 3GPP system - fixed broadband access network interworking; Stage 3 | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.139/24139-d10.zip | |
24.141 | Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.141/24141-d00.zip | |
24.147 | Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 13.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.147/24147-d20.zip | |
24.161 | Network-Based IP Flow Mobility (NBIFOM); Stage 3 | TS | 13.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.161/24161-d30.zip | |
24.166 | 3GPP IP Multimedia Subsystem (IMS) conferencing Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.166/24166-d00.zip | |
24.167 | 3GPP IMS Management Object (MO); Stage 3 | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.167/24167-d10.zip | |
24.171 | Control Plane Location Services (LCS) procedures in the Evolved Packet System (EPS) | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.171/24171-d00.zip | |
24.173 | IMS Multimedia telephony communication service and supplementary services; Stage 3 | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.173/24173-d10.zip | |
24.091 | Explicit Call Transfer (ECT) supplementary service; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.091/24091-d00.zip | |
24.183 | IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification | TS | 13.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.183/24183-d20.zip | |
24.216 | Communication Continuity Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.216/24216-d00.zip | |
24.237 | IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 | TS | 13.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.237/24237-d60.zip | |
24.238 | Session Initiation Protocol (SIP) based user configuration; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.238/24238-d00.zip | |
24.239 | Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.239/24239-d00.zip | |
24.244 | Wireless LAN control plane protocol for trusted WLAN access to EPC; Stage 3 | TS | 13.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.244/24244-d40.zip | |
24.182 | IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification | TS | 13.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.182/24182-d20.zip | |
24.088 | Call Barring (CB) supplementary service; Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.088/24088-d00.zip | |
24.259 | Personal Network Management (PNM); Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.259/24259-d00.zip | |
24.093 | Completion of Calls to Busy Subscriber (CCBS); Stage 3 | TS | 13.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.093/24093-d00.zip | |
24.247 | Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.247/24247-d00.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.285 | Allowed Closed Subscriber Group (CSG) list; Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.285/24285-d00.zip | |
24.286 | IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.286/24286-d00.zip | |
24.302 | Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 | TS | 13.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.302/24302-da0.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.294 | IP Multimedia Subsystem (IMS) Centralized Services (ICS) protocol via I1 interface | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.294/24294-d00.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.304 | Mobility management based on Mobile IPv4; User Equipment (UE) - foreign agent interface; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.304/24304-d00.zip | |
24.305 | Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.305/24305-d00.zip | |
24.292 | IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3 | TS | 13.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.292/24292-d40.zip | |
24.279 | Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 3 | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.279/24279-d10.zip | |
24.312 | Access Network Discovery and Selection Function (ANDSF) Management Object (MO) | TS | 13.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.312/24312-d40.zip | |
24.333 | Proximity-services (ProSe) Management Objects (MO) | TS | 13.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.333/24333-d60.zip | |
24.303 | Mobility management based on Dual-Stack Mobile IPv6; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.303/24303-d00.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.322 | Tunnelling of IP Multimedia Subsystem (IMS) services over restrictive access networks; Stage 3 | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.322/24322-d00.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.341 | Support of SMS over IP networks; Stage 3 | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.341/24341-d10.zip | |
24.315 | IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3: protocol specification | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.315/24315-d00.zip | |
24.337 | IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transfer; Stage 3 | TS | 13.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.337/24337-d20.zip | |
24.368 | Non-Access Stratum (NAS) configuration Management Object (MO) | TS | 13.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.368/24368-d30.zip | |
24.381 | Mission Critical Push To Talk (MCPTT) group management; Protocol specification | TS | 13.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.381/24381-d40.zip | The present document specifies the group management protocols needed to support Mission Critical Push To Talk (MCPTT). Group management applies only when the UE operates on the network.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting the group management client (GMC) functionality, to application server supporting the group management server (GMS) functionality, and to application server supporting the MCPTT server functionality. |
24.334 | Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3 | TS | 13.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.334/24334-d70.zip | |
24.383 | Mission Critical Push To Talk (MCPTT) Management Object (MO) | TS | 13.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.383/24383-d40.zip | The present document defines a number of Mission Critical Push To Talk (MCPTT) Management Objects (MO) that are configured for the MCPTT UE for the operation of the MCPTT Service. The management objects are 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 OMA-ERELD_DM-V1_2 [2].
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an MCPTT UE supporting on-line, off-line or both on-line and off-line configuration of the configuration management client.
The present document is applicable to an MCPTT UE supporting off-line configuration of the group management client.
The parameters defined by the management objects in the present document are configured in the MCPTT UE using on-line configuration over the CSC-4 reference point and using off-line configuration over the CSC-11 and CSC-12 reference points. Other specifications define how these parameters are used in the operation of MCPTT, and whether they are applicable to on-network operation or off-network operation, or both:
- 3GPP TS 24.379 [7]
- 3GPP TS 24.380 [8]
- 3GPP TS 24.381 [9]
- 3GPP TS 24.382 [11]
- 3GPP TS 24.384 [12]
The common network operation means both on-network operation and off-network operation in the present document.
The following management objects are defined in the present document:
- MCPTT UE configuration MO
- MCPTT user profile MO
- MCPTT group configuration MO
- MCPTT service configuration MO
- MCPTT UE initial configuration MO
The MOs listed above define repositories of data in the ME. |
24.384 | Mission Critical Push To Talk (MCPTT) configuration management; Protocol specification | TS | 13.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.384/24384-d40.zip | The present document specifies the configuration management documents and protocols needed to support Mission Critical Push To Talk (MCPTT) online configuration over the CSC-4 and CSC-5 reference points and the procedures to support Mission Critical Push To Talk (MCPTT) offline configuration over the CSC-11and CSC-12 reference points. Configuration management documents defined in the present document includes:
MCPTT UE initial configuration document;
MCPTT UE configuration document;
MCPTT user profile configuration document; and
MCPTT service configuration document.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an MCPTT UE supporting the configuration management client functionality, to application server supporting the configuration management server functionality, and to application server supporting the MCPTT server functionality. |
24.390 | Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS; Stage 3 | TS | 13.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.390/24390-d30.zip | |
24.391 | Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem (IMS) Management Object (MO) | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.391/24391-d00.zip | |
24.481 | Mission Critical Services (MCS) group management; Protocol specification | TS | 13.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.481/24481-d70.zip | |
24.482 | Mission Critical Services (MCS) identity management; Protocol specification | TS | 13.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.482/24482-d30.zip | This document specifies the identity management and authentication protocols needed to support Mission Critical Services (MCSs). Identity management applies only to on-network operation.
MCSs are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
MCSs can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
This document is applicable to User Equipment (UE) supporting the identity management client functionality, and to application servers supporting the identity management server functionality. |
24.483 | Mission Critical Services (MCS) Management Object (MO) | TS | 13.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.483/24483-da0.zip | |
24.484 | Mission Critical Services (MCS) configuration management; Protocol specification | TS | 13.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.484/24484-db0.zip | |
24.523 | Core and enterprise Next Generation Network (NGN) interaction scenarios; Architecture and functional description | TS | 13.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.523/24523-d00.zip | |
24.524 | Hosted enterprise services; Architecture, functional description and signalling | TS | 13.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.524/24524-d10.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.