id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
23.700-80
|
Study on 5G system support for AI/ML-based services
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-80/23700-80-i00.zip
|
This Technical Report will study, based on requirements as specified in clauses 6.40 and 7.10 of TS 22.261 [2], 5GS assistance to support Artificial Intelligence (AI) / Machine Learning (ML) model distribution, transfer, training for various applications, e.g. video/speech recognition, robot control, automotive, etc.
The scope of this study is on how the AI/ML service providers could leverage 5GS as the platform to provide the intelligent transmission support for application layer AI/ML operation based on the following objectives.
1. Study the possible architectural and functional extensions to support the Application layer AI/ML operations defined in TS 22.261 [2], more specifically:
a. Support monitoring of network resource utilization in the 5G system relevant to the UE in order to support Application AI/ML operation.
b. Whether and how to extend 5GS information exposure for 5GC NF(s) to expose UE and/or network conditions and performance prediction (e.g. location, QoS, load, congestion, etc.) to the UE and/or to the authorized 3rd party to assist the Application AI/ML operation.
c. Enhancements of external parameter provisioning to 5GC (e.g. expected UE activity behaviours, expected UE mobility, etc.) based on Application AI/ML operation.
d. Investigate the enhancements of other 5GC features that could be used to assist the Application AI/ML operations as described in clause 6.40 of TS 22.261 [2].
2. Study possible QoS, Policy enhancements to support Application AI/ML operational traffic while supporting regular (non Application-AI/ML) 5GS user traffic.
3. Study whether and how 5GS provides assistance to AF and the UE for the AF and UE to manage the Federated Learning (FL) operation and model distribution/redistribution (i.e. FL members selection, group performance monitoring, adequate network resources allocation and guarantee) to facilitate collaborative Application AI/ML based Federated Learning operation between the application clients running on the UEs and the Application Servers.
|
23.700-81
|
Study of Enablers for Network Automation for the 5G System (5GS); Phase 3
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-81/23700-81-i00.zip
|
This study focuses on key issue description, solution and evaluation/conclusion on further enhancement for network automation, as documented in TS 23.288 [5], by covering the following objectives:
- Study possible mechanisms for improved correctness of NWDAF analytics;
- Investigate whether and how NWDAF can assist application detection;
- Investigate whether and how to support data and analytics exchange in roaming case;
- Investigate data collection and data storage enhancements (including DCCF and ADRF enhancements, e.g. DCCF relocation, ADRF selection, ML model storage);
- Study whether and how to enhance trained ML Model sharing for different vendors;
- Study whether and how interactions between NWDAF can leverage MDAS/MDAF functionality for data collection and analytics;
- Investigate NWDAF-assisted URSP;
- Study whether and how to enhance the QoS sustainability analytics with finer granularity and additional input data;
- Study whether and how to enhance architecture to support federated learning in the 5GC; and
- Study NWDAF enhancements considering the finer granularity of location information than TA and cell level.
|
23.700-85
|
Study on enhancement of 5G User Equipment (UE) policy
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-85/23700-85-i00.zip
|
This study focuses on key issue description, solution and conclusion on the enhancement of 5G UE Policy aspect by covering following objectives:
- URSP rule provisioning and updating procedures for home-routed and LBO roaming scenario, while keeping the existing framework of policy control based on HPLMN.
- Investigate whether and how the network can be made aware when the UE enforces URSP rule and investigate whether and what actions the 5G network can perform.
- Investigate if enhancements are needed for provisioning UE with consistent URSP across 5GC and EPC, and study the mechanism if needed.
- Investigate how to support standardized and operator-specific traffic categories in the traffic descriptor of URSP.
|
23.700-86
|
Study on Architecture Enhancement to support Ranging based services and sidelink positioning
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-86/23700-86-i00.zip
|
The present document is to study 5GC architecture enhancements to enable Ranging-based services and sidelink positioning for commercial, V2X and public safety use cases in in-coverage, partial coverage, and out-of-coverage of 5G network, which include:
- Authorization and policy/parameter provisioning for a UE or a group of UEs;
- Ranging device discovery and service operation procedures between two UEs, between one UE and multiple UEs or via the assistance of another UE;
- Ranging and sidelink positioning service exposure to a UE or an Application Server who has requested the service.
|
23.700-87
|
Study on system architecture enhancement for next generation real time communication
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-87/23700-87-i00.zip
|
The scope of this document is to study IMS architecture enhancements to support new real time communication services based on requirements of e.g. eMMTEL and 5G_MEDIA_MTSI_ext.
The study in this document includes the following aspects:
1) Study the enhancement of IMS architecture and procedures to support Data Channel usage in IMS network, including whether and which functionalities are defined in IMS architecture for Data Channel server, with separate control plane and media plane, and Data Channel application repository, which procedures are needed between Data channel server and IMS AS to support call event notifications.
2) Study whether and how IMS architecture and functions are supported for the requirements from SA WG1 Rel-18 eMMTEL WID impacts:
- to support AR telephony communication.
- to support 3rd party to verify via operator network that the caller is authorized to use or reference specific identity information which can be securely signalled to the callee when placing a call.
3) Study whether and which IMS media control interfaces can be potentially applied for service based architecture, supporting both existing capabilities and new capabilities for possible new applications and efficient media processing.
|
23.700-88
|
Study on architecture enhancements for Personal IoT Network (PIN)
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-88/23700-88-i00.zip
|
The scope of this Technical Report is to study the enhancement of 5G System to support Personal IoT Network (PIN). The study addresses the service requirements documented in TS 22.261 [5] for the Personal IoT Networks. The following aspects needs to be studied:
- Architecture enhancement:
- To study the potential architectural enhancements for supporting management of PIN, access of PIN via PIN Element with Gateway Capability (PEGC), and communication of PIN (e.g. PIN Element communicates with other PIN Elements directly or via PEGC or via PEGC and 5GS).
- To study the potential architecture enhancements for supporting identifying PIN and the PIN Elements.
- Security related:
NOTE: The study may need cooperation with SA3. If solutions are related to security impact, they will be studied in SA WG3.
- To study how to identify PIN and the PIN Elements in the PIN at 5GC level to serve for authentication/authorization.
- Management as well as policy and routing control enforcement:
- To study the management of a PIN.
- To study the procedures for PIN discovery, PIN Element discovery.
|
23.700-89
|
Study on 5G AM Policy
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-89/23700-89-i00.zip
|
The aim of this Technical Report is to study and evaluation of potential enhancements for Access and Mobility Policy Management with the following objective(s):
- To study the mechanisms to provide AM policy control on RFSP Index consistency when UE moves from 5GC to EPC, and define enhancements in R17 mechanism if needed.
|
23.700-90
|
Study on interconnection and migration aspects for railways
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-90/23700-90-i00.zip
|
The present document studies solutions to satisfy interconnection and migration needs for railways. It identifies enhancements to be included in the technical specifications for MCPTT (3GPP TS 23.379 [2]), MCVideo (3GPP TS 23.281 [3]), MCData (3GPP TS 23.282 [4]) and in the common functional architecture (3GPP TS 23.280 [5]) to support mission critical communications.
|
23.700-95
|
Study on application enablement aspects for subscriber-aware northbound API access
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-95/23700-95-i10.zip
|
The present document studies the potential enhancements in CAPIF and application enablement frameworks (e.g. SEAL, EDGEAPP, vertical enabler layers) to support the subscriber-aware northbound API access (SNA), whose requirements are specified in TS 22.261 [2].
This study takes into consideration the existing works for CAPIF (3GPP TS 23.222 [3]), SEAL (3GPP TS 23.434 [4]), and EDGEAPP (3GPP TS 23.558 [5]).
Any potential enhancements to security procedures related to CAPIF and application enablement frameworks (e.g. EDGEAPP, SEAL, vertical enabler layers) to support SNA are not in the scope of this study.
|
23.700-96
|
Study on 5G-enabled fused location service capability
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-96/23700-96-i00.zip
|
The present document studies and evaluates the application architecture aspects and solutions to address potential new and enhanced location capabilities for vertical application enabler, including the following aspects:
- Enabling location performance (accuracy, availability and latency) enhancements through combined use and fusion of 3GPP and non-3GPP location technologies at the application layer;
- Identification and classification of location related requirements (including location QoS) for vertical application services;
- Architecture enhancement leveraging 5G positioning and location services;
- Enabling location sources and positioning methods selection based on the requested location QoS;
- Initialization and configuration for fused location service;
- Enabling value-added location service capabilities exposure to vertical applications;
- Enhancements on SEAL location management addressing the aspects above.
NOTE: This study will not duplicate solutions already available in Core Network and RAN.
|
23.700-97
|
Study on Application Capability Exposure for IoT Platforms
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-97/23700-97-i10.zip
|
The present document is a technical report which identifies SEAL functionality to support application capability exposure to general purpose servers or 3rd party IoT applications via IoT Platforms. Key issues and corresponding solutions necessary to ensure efficient use and deployment of IoT Platforms in the 5G network are included.
The study takes into consideration the existing work for Core Network exposure in 3GPP TS 23.502 [2] and provides recommendations for normative work.
|
23.700-98
|
Study on enhanced Architecture for enabling Edge Applications
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-98/23700-98-i10.zip
|
The present document is a technical report capturing the study on enhanced architecture for enabling edge applications over 3GPP networks. The study bases the enhancements on the work done in 3GPP TS 23.558 [2] and takes into consideration other related work done within and outside 3GPP i.e. ETSI MEC [3] and GSMA OP [4].
The aspects of the study include identifying new key issues, architecture requirements, related architecture enhancements and solutions, cardinality rules, deployment options, and involved entities and relationships to enhance the Rel-17 architecture for enabling edge applications.
|
23.700-99
|
Study on Network Slice Capability Exposure for Application Layer Enablement
|
TR
|
18.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-99/23700-99-i20.zip
|
The study identifies the SA1 requirements and potential vertical requirements of network slice capability exposure that have yet to be realized, and proposes application architecture aspects solutions and enhancements to SEAL. Based on any gaps found between requirements and existing capabilities, the present document includes: identification of key issues, solutions, corresponding evaluations and conclusions to ensure the efficient network slice capability exposure.
The study takes into consideration the SEAL architecture specified in 3GPP TS 23.434 [2], network slicing related architecture and services(such as services of NEF) specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4], network slicing management capability provisioning and architecture specified in 3GPP TS 28.531 [5] and 3GPP TS 28.533 [6], requirements specified in TS 22.261 [7].
|
23.783
|
Study on Mission Critical services support over 5G System
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.783/23783-i00.zip
|
The present document analyses how to ensure that the set of Mission Critical services is supported over the 5GS. Key issues are derived and solutions are developed for the impacts on existing or new Stage 2 Mission Critical specifications.
|
23.903
|
Redial solution for voice-video switching
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-i00.zip
|
The present document describes the idle mode redial mechanism which 3GPP based systems can use to enhance switching between circuit switched voice and video services.
|
23.919
|
Direct tunnel deployment guideline
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-i00.zip
|
The present document contains deployment guidelines for the use of direct tunnelling of user plane data between the RNC and the GGSN (earlier known as the One Tunnel approach).
This report highlights the impacts of the 3GPP Release 7 Direct Tunnel solution to the current UMTS system in order to guide equipment development and network deployment.
|
23.924
|
Feasibility study on Non-Access Stratum (NAS) node selection function above Base Station Controller (BSC) / Radio Network Controller (RNC)
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.924/23924-i00.zip
|
This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications.
|
23.946
|
Guidelines for CAPIF Usage
|
TR
|
18.2.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.946/23946-i20.zip
|
This TR provides guidelines for CAPIF usage for the benefit of the Application developer and API provider communities. This document also describes the usage and deployment options in CAPIF.
The work takes into consideration the work done for CAPIF in 3GPP TS 23.222 [2] and 3GPP TS 29.222 [3] and 3GPP TS 33.122 [4], and other related work outside 3GPP.
|
23.958
|
Edge Application Standards in 3GPP and alignment with External Organizations
|
TR
|
18.3.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.958/23958-i30.zip
|
This TR provides the recommendations for the alignment of EDGEAPP architecture with ETSI MEC reference architecture and GSMA Operator Platform (OP) for the industry stakeholders.
This document provides recommendations of using specifications from 3GPP, ETSI ISG MEC and GSMA OPG to deploy an aligned edge system.
The present document is based on 3GPP TS 23.558 [2].
|
23.973
|
User data interworking, coexistence and migration
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.973/23973-i00.zip
| |
23.975
|
IPv6 migration guidelines
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-i00.zip
|
The technical report identifies various scenarios of transition to IPv6 and co-existence of IPv4 and IPv6, deployment options and impacts on 3GPP network elements. In particular:
- Identify the transition and co-existence scenarios of interest for operators and the respective assumptions and requirements.
- Analyze existing IP address allocation mechanism for IPv6 migration if necessary.
- Investigate IPv6 transition mechanisms for the scenarios identified during the study and investigate their applicability for 3GPP network, and identify the compatibility among applicable transition mechanisms.
- Identify any impact on 3GPP network elements.
- Provide recommendations on IPv6 transition and co-existence of IPv4 and IPv6 and identify if any normative work is needed.
|
23.976
|
Push architecture
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-i00.zip
|
The purpose of this technical report is to analyse the service requirements for push services as defined in TS 22.174 "Push service; Stage 1". It continues the work of TR 23.875 (3GPP internal report).
This technical report describes methods for supporting push services by 3GPP delivery networks. The mechanisms described apply to existing delivery networks for the 3GPP Packet Switched (PS) domain, Circuit Switched (CS) domain, IP Multimedia Core Network Subsystem (IMS), Multimedia Broadcast / Multicast Service (MBMS), and Wireless Local Area Network (WLAN). Any necessary changes identified during this work will be introduced by means of change requests to the appropriate specifications.
The definition of Push Functionality that applies to push Application Servers is outside the scope of this work. The definition of Push Functionality that is best implemented in push Application Servers such as a Push Proxy and Push Initiator will be undertaken by other standards bodies and industry forums.
|
23.977
|
Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-i00.zip
|
The objective of this technical report is to identify the full set of requirements for bandwidth and resource savings and improved speech quality, with specific consideration to networks supporting A/Gb mode and the bearer independent circuit-switched core network (BICN). The different architectural solutions to meet these requirements will be assessed.
Consideration shall be made to existing architectures and solutions to provide harmony between 2G nodes, UMTS nodes and external networks (PSTN/ISDN). Backward compatibility to existing solutions and ease of network introduction/upgrade shall be given high importance.
|
23.979
|
3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-i00.zip
|
The present document studies the architectural requirements in order to enable services like PoC over 3GPP systems. The report looks into aspects of using 3GPP PS domain and radio access technologies (GERAN, UTRAN) for bearer services and IMS for reachability and connectivity for applications like PoC.
|
23.981
|
Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-i00.zip
|
The present document studies study interworking and migration scenarios related to IPv4 based IMS implementations. The study provides guidelines for operators and vendors on interworking aspects of IPv4 based IMS implementations, and provides guidelines on migrating to 3GPP IMS using IPv6.
|
24.002
|
GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-i00.zip
|
The present document describes the reference configuration for access to a PLMN.
A user accesses a PLMN via a number of interfaces, including the MS-BS (in A/Gb mode and GERAN Iu mode), UE-UTRAN (in UTRAN Iu mode), UE-E-UTRAN, and UE-5G-AN interface. The purpose of this document is to indicate the possible access arrangements that may be used in conjunction with the MS-BS (in A/Gb mode and GERAN Iu mode), UE-UTRAN (in UTRAN Iu mode), UE-E-UTRAN, and UE-5G-AN interface.
|
24.010
|
Mobile radio interface layer 3; Supplementary services specification; General aspects
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-i00.zip
|
The present document gives the general aspects of the specification of supplementary services at the layer 3 radio interface.
3GPP TS 24.08x and 24.09x‑series specify the procedures used at the radio interface (reference point Um as defined in 3GPP 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
3GPP TS 24.008 [48] and 3GPP TS 24.080 [27] specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 22.09x‑series.
Technical realization of supplementary services is described in 3GPP TS 23.011 and GSM 23.08x and 23.09x‑series.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 [49] and 3GPP TS 24.008 [48].
|
24.011
|
Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-i00.zip
|
The present document specifies the procedures used across the mobile radio interface by the signalling layer 3 function Short Message Control (SMC) and Short Message Relay function (SM‑RL) for circuit switched in A/Gb mode, GPRS, EPS, and 5GS.
|
24.022
|
Radio Link Protocol (RLP) for circuit switched bearer and teleservices
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-i00.zip
|
The present document specifies the Radio Link Protocol (RLP) for circuit switched data transmission within a PLMN. RLP covers the Layer 2 functionality of the ISO OSI Reference Model (ISO/IEC 7498 [22]). It is based on ideas contained in ISO/IEC 3309 [21], ISO/IEC 4335 [20] and ISO/IEC 7809 [26] (HDLC of ISO) as well as ITU-T Recommendation X.25 [30] and Q.92x (LAP-B and LAP-D of ITU, respectively.) RLP has been tailored to the special needs of digital radio transmission. RLP provides to its users the OSI Data Link Service (ISO/IEC 8886 [24]).
RLP is intended for use with non-transparent data-transfer. Protocol conversion may be provided for a variety of protocol configurations. Those foreseen immediately are:
- character-mode protocols using start-stop transmission (IA5);
- X.25 LAP-B.
For reasons of better presentation, material about protocol conversion has been placed within those Specifications concerned with the relevant Terminal Adapters, i.e. 3GPP TS 27.002 [10] for the asynchronous case and 3GPP TS 27.003 [11] for the synchronous case. Care must be taken that that material also applies to Interworking Functions; see 3GPP TS 29.007 [13].
The present document is valid for a PLMN in A/Gb mode as well as in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". Please note, that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
|
24.030
|
Location Services (LCS); Supplementary service operations; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-i00.zip
|
The present document gives the stage 3 description of the Location Service (LCS) operations for mobile station. These operations shall apply to both CS and PS domain.
The group of location services operations is divided into two different classes:
‑ Network initiated location services operations (clause 4);
‑ Mobile initiated location services operations (clause 5).
|
24.067
|
Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-i00.zip
|
The present document specifies the procedures used at the radio interface (Reference point Um for GSM and Reference point Uu for UMTS as defined in TS 24.002) for normal operation, invocation, registration and interrogation of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP) supplementary service. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and22.09x -series. TS 22.067 is related specially to eMLPP.
Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and 23.09x -series.
TS 23.067 is related specially to eMLPP.
The procedures for Call Control, Mobility Management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
The procedure for Radio Resource management at layer 3 radio interface is defined in 3GPP TS 44.018 and TS 25.331.
|
24.072
|
Call Deflection (CD) supplementary service; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-i00.zip
|
This Global System for Mobile communications Technical Specification specifies the procedures used at the radio interface (reference point Um as defined in 3GPP TS 24.002) for normal operation of Call Deflection (CD) supplementary service. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
|
24.081
|
Line Identification supplementary services; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-i00.zip
|
The present document specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of line identification supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x‑series. 3GPP TS 22.081 is related specially to line identification supplementary services.
Technical realization of supplementary services is described in 3GPP TS 23.011 and 3GPP TS 23.08x and 3GPP TS 23.09x‑series. 3GPP TS 23.081 is related specially to line identification supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the line identification supplementary services and are described in the present document:
- Calling line identification presentation (CLIP) (clause 1);
- Calling line identification restriction (CLIR) (clause 2);
- Connected line identification presentation (COLP) (clause 3);
- Connected line identification restriction (COLR) (clause 4).
|
24.082
|
Call Forwarding (CF) supplementary services; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-i00.zip
|
This European Standard (EN) specifies the procedures used at the radio interface (reference point Um as defined in 3GPP TS 24.002) for normal operation, registration, erasure, activation, deactivation, interrogation and network invocation of call offering supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x‑series. 3GPP TS 22.082 is related specially to call offering supplementary services.
Technical realization of supplementary services is described in 3GPP TS 23.011 and 3GPP TS 23.08x and 3GPP TS 23.09x‑series. 3GPP TS 23.082 is related specially to call offering supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the call offering supplementary services and are described in the present document:
- Call forwarding unconditional (CFU) (clause 1);
- Call forwarding on mobile subscriber busy (CFB) (clause 2);
- Call forwarding on no reply (CFNRy) (clause 3);
- Call forwarding on mobile subscriber not reachable (CFNRc) (clause 4).
|
24.083
|
Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-i00.zip
|
The present document specifies the procedures used at the radio interface (Reference point Um as defined in 3GPP TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call completion supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x‑series. 3GPP TS 22.083 is related specially to call completion supplementary services.
Technical realization of supplementary services is described in 3GPP TS 23.011 and GSM 03.8x and GSM 03.9x‑series.
3GPP TS 23.083 is related specially to call completion supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the call completion supplementary services and are described in the present document:
‑ Call waiting (CW) (clause 1);
‑ Call hold (HOLD) (clause 2).
|
24.084
|
Multi Party (MPTY) supplementary service; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-i00.zip
|
The present document specifies the procedures used at the radio interface (Reference point Um as defined in 3GPP TS 24.002) for normal operation and invocation of MultiParty supplementary services.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and the 3GPP TS 22.08x and 3GPP TS 22.09x‑series.
3GPP TS 22.084 is related specially to MultiParty supplementary services.
Technical realization of supplementary services is described in 3GPP TS 23.011 and the 3GPP TS 23.08x and 3GPP TS 23.09x‑series.
3GPP TS 23.084 is related specially to MultiParty supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary service belongs to the MultiParty supplementary services and is described in the present document:
- MultiParty service (MPTY) (clause 1).
|
24.085
|
Closed User Group (CUG) supplementary service; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-i00.zip
|
This Technical Specification (TS) for Mobile communications specifies the procedures used at the radio interface (reference point Um as defined in 3GPP TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of community of interest supplementary services. The provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
In 3GPP TS 24.010, the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x-series. 3GPP TS 22.085 is related to the community of interest supplementary services.
Technical realization of supplementary services is described in technical specifications 3GPP TS 23.011 and 3GPP TS TS 23.08x and 3GPP TS 23.09x-series. 3GPP TS 23.085 is related to the community of interest supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
Signalling interworking for supplementary services between 3GPP TS 29.002 and 3GPP TS 24.008 and between 3GPP TS 29.002 and 3GPP TS 24.080 is defined in 3GPP TS 29.011.
The following supplementary services belong to the community of interest supplementary services and are described in this TS:
‑ Closed User Group (CUG) clause 1.
|
24.086
|
Advice of Charge (AoC) supplementary services; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.086/24086-i00.zip
|
The present document specifies the procedures used at the radio interface (reference point Um as defined in 3GPP TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of charging supplementary services. The provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x‑series. 3GPP TS 22.024 and 02.86 are related to the charging supplementary services.
Technical realization of supplementary services is described in 3GPP TS 23.011 and 3GPP TS 23.08x and 3GPP TS 23.09x‑series. 3GPP TS 23.086 is related to the charging supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the charging supplementary services and are described in the present document:
- Advice of Charge (Information) (AoCI) (clause 1);
- Advice of Charge (Charging) (AoCC) (clause 2).
|
24.087
|
User-to-User Signalling (UUS) Supplementary Service; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.087/24087-i00.zip
|
This Technical Specification gives the stage 3 description of the User-to-User signalling supplementary services.
The User-to-user supplementary service is divided into 3 different services:
- Service 1 (UUS1)
- Service 2 (UUS2)
- Service 3 (UUS3)
|
24.088
|
Call Barring (CB) supplementary service; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.088/24088-i00.zip
|
This Technical Specification (TS) specifies the procedures used at the radio interface (reference point Um as defined in 3GPP TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call barring supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004, GSM 02.8x and GSM 02.9x‑series.
Technical realization of supplementary services is described in 3GPP TS 23.011, GSM 03.8x and GSM 03.9x‑series.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the call restriction supplementary services and are described in this specification:
- Barring of outgoing calls (clause 1):
- Barring of all outgoing calls (BAOC) (Barring program 1);
- Barring of outgoing international calls (BOIC) (Barring program 2);
- Barring of outgoing international calls EXCEPT those directed to the home PLMN country
(BOIC-exHC) (Barring program 3).
- Barring of incoming calls (clause 2):
- Barring of all incoming calls (BAIC) (Barring program 1);
- Barring of incoming calls when roaming outside the home PLMN country
(BIC-Roam) (Barring program 2);
- Anonymous Call Rejection (ACR) (Barring program 3).
|
24.090
|
Unstructured Supplementary Service Data (USSD); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.090/24090-i00.zip
|
The present document gives the stage 3 description of the Unstructured Supplementary Service Data (USSD) operations.
The group of unstructured supplementary service data operations is divided into two different classes:
‑ Network initiated unstructured supplementary service data operations (clause 5);
‑ Mobile initiated unstructured supplementary service data operations (clause 6).
|
24.091
|
Explicit Call Transfer (ECT) supplementary service; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.091/24091-i00.zip
|
The present document gives the stage 3 description of the call transfer supplementary services.
The present document specifies the procedures used at the radio interface (Reference point Um as defined in 3GPP TS 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of call transfer supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004, 3GPP TS 22.08x and 3GPP TS 22.09x‑series. 3GPP TS 22.091 is related specifically to call transfer supplementary services.
The technical realization of supplementary services is described in 3GPP TS 23.011, 3GPP TS 23.08x and 3GPP TS 23.09x‑series. 3GPP TS 23.091 is related specifically to call transfer supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the call transfer supplementary services and are described in the present document:
‑ Explicit Call Transfer (ECT) (see clause 4).
|
24.093
|
Completion of Calls to Busy Subscriber (CCBS); Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.093/24093-i00.zip
|
The present dcoument gives the stage 3 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service. The present document specifies the procedures used at the radio interface (Reference point Um as defined in 3GPP TS 24.002) for normal operation, activation, deactivation, invocation and interrogation of the completion of calls to busy subscriber supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004, 3GPP TS 22.08x and 3GPP TS 22.09x-series. Technical specification 3GPP TS 22.093 is related specifically to the Completion of Calls to Busy Subscriber supplementary service.
The technical realization of supplementary services is described in technical specifications 3GPP TS 23.011, 3GPP TS 23.08x and 3GPP TS 23.09x-series. 3GPP TS 23.093 is related specifically to Completion of Calls to Busy Subscriber supplementary service.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the call completion supplementary services and are described in the present document:
- Completion of Calls to Busy Subscriber (CCBS) (see clause 4).
|
24.096
|
Name Identification supplementary services; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.096/24096-i00.zip
|
This Technical Specification (TS ) specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of name identification supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given. 3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x‑series. 3GPP TS 22.096 is related specially to name identification supplementary services.
Technical realization of supplementary services is described in 3GPP TS 23.011 and 3GPP TS 23.08x and 3GPP TS 23.09x‑series. Technical specification 3GPP TS 23.096 is related specially to name identification supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the name identification supplementary services and are described in this TS:
- Calling name presentation (CNAP);
|
24.103
|
Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.103/24103-i00.zip
|
The present document provides the protocol details for telepresence using the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), the Session Description Protocol (SDP), the Binary Floor Control Protocol (BFCP) and the ControLling mUltiple streams for tElepresence (CLUE) controlling multiple streams for telepresence based on service requirements.
The present document addresses the areas of describing and negotiating IM session with multiple media streams based on the IM CN subsystem, including point to point calls as specified in 3GPP TS 24.229 [2] and multiparty conferences as specified in 3GPP TS 24.147 [3], to facilitate the support of telepresence.
The functionalities for conference policy control and the signalling between a MRFC and a MRFP are not specified in this document.
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, CLUE and BFCP, either directly, or as modified by 3GPP TS 24.229 [2].
The present document is applicable to Application Servers (ASs), Multimedia Resource Function Controllers (MRFCs), Multimedia Resource Function Processors (MRFP) and User Equipment (UE) providing IM session supporting telepresence capabilities.
|
24.105
|
Application specific Congestion control for Data Communication (ACDC) Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.105/24105-i00.zip
|
The present document defines Management Object (MO) that is used to configure the UE with parameters related to Application specific Congestion control for Data Communication (ACDC) functionality.
The MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [3].
The MO consists of relevant parameters for provisioning of ACDC at a UE.
|
24.109
|
Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.109/24109-i00.zip
|
The present document defines stage 3 for the HTTP Digest AKA as specified in RFC 3310 [6] based implementation of Ub interface (UE-BSF), the Disposable-Ks model based implementation of Upa interface (NAF-UE) and the HTTP Digest as specified in RFC 7616 [36] and the PSK TLS based implementation of bootstrapped security association usage over Ua interface (UE-NAF) in Generic Authentication Architecture (GAA) as specified in 3GPP TS 33.220 [1]. The purpose of the Ub interface is to create a security association between UE and BSF for further usage in GAA applications. The purpose of the Upa interface is to provide a push mechanism to created a bootstrapped security association between the UE and NAF for secure communication of pushed messages. The purpose of the Ua interface is to use the so created bootstrapped security association between UE and NAF for secure communication.
The present document also defines stage 3 for the Authentication Proxy usage as specified in 3GPP TS 33.222 [5].
The present document also defines stage 3 for the subscriber certificate enrolment as specified in 3GPP TS 33.221 [4] which is one realization of the Ua interface. The subscriber certificate enrolment uses the HTTP Digest based implementation of bootstrapped security association usage to enrol a subscriber certificate and the delivery of a CA certificate.
The present document also defines stage 3 for TLS using AKMA (Authentication and Key Management for Applications) keys over the Ua* interface (AKMA AF-UE) as described in 3GPP TS 33.535 [38].
|
24.116
|
Stage 3 aspects of system architecture enhancements for TV services
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.116/24116-i00.zip
|
The present document defines the stage 3 aspects of the architecture enhancements for broadcast TV service (see 3GPP TS 23.246 [2]).
The present document specifies:
- the requirements on the device in Receive only mode;
- the procedure for selecting a network to receive broadcast TV service; and
- the usage of the information configured in the TV service configuration.
The clause 4 applies to a device in Receive only mode only. The remaining clauses are applicable to:
- a 3GPP UE wishing to receive broadcast TV service; and
- a device in Receive only mode.
|
24.117
|
TV service configuration Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.117/24117-i00.zip
|
The present document defines a Management Object (MO) that can be used to configure the parameters related to TV service provided via a PLMN.
The MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [2].
The MO consists of nodes and leaves conveying configuration parameters used for selecting and receiving TV service from a PLMN, according to the procedures described in 3GPP TS 23.246 [3] and 3GPP TS 24.116 [8].
|
24.135
|
Multicall supplementary service; Stage 3
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.135/24135-i00.zip
|
The present document gives the stage 3 description of the Multicall (MC) supplementary service. The present document specifies the procedures used by the radio interface for normal operation, registration and interrogation of the Multicall supplementary service. Provision, withdrawal, erasure, activation and deactivation of supplementary services is an administrative matter between the mobile subscriber and the service provider and causes no signalling on the radio interface.
3GPP TS 24.010 describes the general aspects of the specification of supplementary services at the layer 3 radio interface.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004, 3GPP TS 22.072, 3GPP TS 22.08x, 3GPP TS 22.09x-series and 3GPP TS 22.135. 3GPP TS 22.135 is related specifically to the Multicall supplementary service.
The technical realisation of supplementary services are described in 3GPP TS 23.011, 3GPP TS 23.072, 3GPP TS 23.08x, 23.09x-series and 3GPP TS 23.135. 3GPP TS 23.135 is related specifically to the Multicall supplementary service.
The procedures for Call Control and Mobility Management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services are described in the present document:
- Multicall (MC) (see clause 4).
|
24.139
|
3GPP system - fixed broadband access network interworking; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.139/24139-i00.zip
|
The present document specifies the UE – EPC procedures for accessing 3GPP Evolved Packet Core (EPC) via a Fixed Broadband Access network.
The specification covers the Support of QoS, Tunnel management procedures including the support of NAT traversal, and non-seamless offloading impacts.
The present document is applicable to the UE and the network. In this technical specification the network is the 3GPP EPC.
|
24.141
|
Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.141/24141-i00.zip
|
The present document provides the protocol details for the presence service within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in 3GPP TS 24.229 [9].
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by 3GPP TS 24.229 [9].
Requirements for manipulation of presence data are defined by use of a protocol at the Ut reference point based on XML Configuration Access Protocol (XCAP) (RFC 4825 [33]).
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing presence functionality.
|
24.147
|
Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.147/24147-i00.zip
|
The present document provides the protocol details for conferencing within the IP Multimedia Core Network subsystem (IMS) based on the Session Initiation Protocol (SIP), SIP Events, the Session Description Protocol (SDP) and the Binary Floor Control Protocol (BFCP).
The functionalities for conference policy control (with respective standardised protocols) are felt to be essential for a complete IMS conferencing service but are not specified in this version of IMS conferencing and are for further study.
The present document does not cover the signalling between a MRFC and a MRFP.
Where possible, the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SIP Events, SDP and BFCP, either directly, or as modified by 3GPP TS 24.229. Where this is not possible, extensions to SIP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
The present document is applicable to Application Servers (ASs), Multimedia Resource Function Controllers (MRFCs), Multimedia Resource Function Processors (MRFP), Media Gateway Control Functions (MGCFs) and to User Equipment (UE) providing conferencing capabilities.
|
24.161
|
Network-Based IP Flow Mobility (NBIFOM); Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.161/24161-i00.zip
|
The present document specifies the procedures of network-based IP flow mobility (NBIFOM). NBIFOM is based on network mobility protocols (i.e. GTP or PMIP) which is performed between 3GPP access and WLAN access network as specified in 3GPP TS 23.161 [2].
NOTE: IP flow mobility based on PMIP is not supported in this release of the specification.
|
24.166
|
3GPP IP Multimedia Subsystem (IMS) conferencing Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.166/24166-i00.zip
|
This document defines the IMS conferencing management object. 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 [3].
The IMS conferencing management object consists of relevant parameters that can be managed for IMS conferencing capabilities.
|
24.167
|
3GPP IMS Management Object (MO); Stage 3
|
TS
|
18.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.167/24167-i10.zip
|
This document defines a mobile device 3GPP IMS Management Object. 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 [12].
The 3GPP IMS Management Object consists of relevant parameters that can be managed for the IM CN Subsystem. This includes the basic framework defined in 3GPP TS 23.228 [4] and 3GPP TS 24.229 [5], and early IMS as defined in 3GPP TS 23.221 [3]. This also includes relevant parameters that can be managed for the application of SMS over IP networks defined in 3GPP TS 24.341 [5a].
The IMS Management Object defines a repository of data into the ME including parameters that are provisioned from the ISIM application (i.e. 3GPP TS 31.103 [11]) or, after derivation, from the USIM application (i.e. 3GPP TS 31.102 [10]).
|
24.171
|
Control Plane Location Services (LCS) procedures in the Evolved Packet System (EPS)
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.171/24171-i00.zip
|
The present document specifies the operations and information coding for the Non-access Stratum (NAS) layer protocol for supporting the Location Services (LCS) in the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The present document is applicable to the User Equipment (UE) and to the Mobility Management Entity (MME) in the Evolved Packet System (EPS).
The present document is developed in accordance to the general principles stated in 3GPP TS 23.271 [1].
|
24.173
|
IMS Multimedia telephony communication service and supplementary services; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.173/24173-i00.zip
|
The present document provides the protocol details for multimedia telephony communication service and associated supplementary services in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.173 [2].
Multimedia telephony and supplementary services allow users to establish communications between them and enrich that by enabling supplementary services.
|
24.174
|
Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.174/24174-i00.zip
|
The present document provides the protocol details for the multi-device and multi-identity aspects in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.173 [2].
The present document is applicable to user equipment (UE) and application servers (AS) which are intended to support multi-device and multi-identity aspects in the IMS.
|
24.175
|
Management Object (MO) for multi-device and multi-identity in the IP Multimedia Subsystem (IMS)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.175/24175-i00.zip
|
The present document defines the management object (MO) for Multi-Device and Multi-Identity in IMS.
The MO for Multi-Device (MuD) and Multi-Identity (MiD) in IMS 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 MO for Multi-Device and Multi-Identity in IMS consists of relevant configuration parameters that can be managed for a UE supporting the UE role specified in 3GPP TS 24.174 [3].
|
24.182
|
IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.182/24182-i00.zip
|
The present document provides the protocol details for the Customized Alerting Tones (CAT) service in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.182 [2].
The CAT service is an operator specific service by which an operator enables the subscriber to customize the media which is played to the calling party during alerting of the called party.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CAT service.
|
24.183
|
IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.183/24183-i00.zip
|
The present document provides the protocol details for the Customized Ringing Signal (CRS) service in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.183 [2].
The CRS service is an operator specific service by which an operator enables the subscriber to customize the media which is played to the called party as an incoming communication indication during establishment of a communication.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CRS service.
|
24.196
|
Enhanced Calling Name (eCNAM)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.196/24196-i00.zip
|
The present document specifies the stage three (protocol description) of the Enhanced Calling Name (eCNAM) supplementary service based on stage one description in 3GPP TS 22.173 [1]. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem (see 3GPP TS 24.229 [2]) based on the Session Initiation Protocol (SIP) (see RFC 3261 [3]) where the eCNAM data is retrieved by the terminating network from trusted data sources.
|
24.216
|
Communication Continuity Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.216/24216-i00.zip
|
This document defines the Communication Continuity Management Object. 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 [4].
The Communication Continuity Management Object consists of relevant parameters that can be managed for Communication Continuity capabilities.
|
24.237
|
IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.237/24237-i00.zip
|
IP Multimedia (IM) Core Network (CN) subsystem Service Continuity (SC) provides the capability of continuing ongoing communication sessions with multiple media across different access networks.
The present document provides the protocol details for enabling IMS SC based on the Session Initiation protocol (SIP) and the Session Description Protocol (SDP) and the protocols of the 3GPP Circuit-Switched (CS) domain (e.g. CAP, MAP, ISUP, BICC and the NAS call control protocol for the CS access).
The present document is applicable to User Equipment (UEs), Application Servers (AS), MSC Servers providing IMS Service Continuity capabilities, Emergency Access Transfer Function (EATF), Access Transfer Control Function (ATCF).
|
24.238
|
Session Initiation Protocol (SIP) based user configuration; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.238/24238-i00.zip
|
The present document provides a Session Initiation Protocol (SIP) based protocol framework that serves as a means of user configuration of supplementary services in the IP Multimedia (IM) Core Network (CN) subsystem. The protocol framework relies upon the contents of the Request-URI in a SIP INVITE request to enable basic configuration of services without requiring use of the Ut interface.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support user configuration of supplementary services.
|
24.239
|
Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.239/24239-i00.zip
|
The present document provides the protocol details for the Flexible Alerting supplementary service in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.173 [2].
Flexible Alerting (FA) causes a call to a pilot identity to branch the call into several legs to alert several termination addresses (group members) simultaneously. The first leg to be answered is connected to the calling party. The other call legs are abandoned.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the FA supplementary service.
|
24.244
|
Wireless LAN control plane protocol for trusted WLAN access to EPC; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.244/24244-i00.zip
|
The present document specifies the procedures of the Wireless LAN control plane protocol (WLCP) for trusted WLAN access to EPC which is used between User Equipment (UE) and Trusted WLAN Access Gateway (TWAG) for multi-connection mode as specified in 3GPP TS 23.402 [2].
This document also defines the message format, information elements coding, error handling and system parameters applied by the WLCP protocol.
|
24.259
|
Personal Network Management (PNM); Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.259/24259-i00.zip
|
Personal Network Management (PNM) is a home network-based application and provides the home network-based management of Personal Network (PN) consisting of multiple devices belonging to a single user, as described in 3GPP TS 22.259 [2] and 3GPP TS 23.259 [15].
The present document provides the protocol details for enabling Personal Network management (PNM) services in the IP Multimedia (IM) Core Network (CN) subsystem based on the protocols of XML Configuration Access Protocol (XCAP), Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The present document provides the protocol details for enabling Personal Network management (PNM) services in Circuit Switched (CS) domain based on the protocols of CAP, MAP, ISUP, USSD and BICC.
The present document is applicable to User Equipment (UEs) and Application Servers (AS) providing PNM capabilities.
The present document makes no PNM specific enhancements to SIP, SIP events or SDP specified in 3GPP TS 24.229 [3].
The present document makes no PNM specific enhancements to CAP, MAP, ISUP, USSD and BICC.
|
24.279
|
Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.279/24279-i00.zip
|
The present document provides the technical realisation for the combination of Circuit Switched calls and IM sessions when using them simultaneously between the same two users.
The present document describes the use of CS and IM services in combination, using the existing procedures that have been defined for CS and IMS. It includes the necessary function as adding an IM session to an ongoing CS call, adding a CS call to an ongoing IM session, supplementary services as they relate to CSICS and supporting capability exchange.
The present document is applicable to UE and Application Servers providing for the combination of Circuit Switched calls and IM sessions.
|
24.285
|
Allowed Closed Subscriber Group (CSG) list; Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.285/24285-i00.zip
|
The present document specifies an Allowed Closed Subscriber Group (CSG) List Management Object (MO).
The Allowed CSG List MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [5].
The Allowed CSG List MO consists of relevant parameters for that can be used by the UE to select the appropriate CSG cell based on its subscription.
The Allowed CSG List MO defines the relevant parameters related to the Allowed CSG List and to the Operator CSG List.
The usage of the Allowed CSG List for in the idle mode process and the mobility management procedure is defined in 3GPP TS 23.122 [2], 3GPP TS 24.008 [3] and 3GPP TS 24.301 [4].
|
24.286
|
IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.286/24286-i00.zip
|
This document defines the IMS Centralised Services Management Object (MO). 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 [4].
The IMS Centralised Services Management Object consists of relevant parameters that can be managed for ICS.
|
24.292
|
IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.292/24292-i00.zip
|
IP Multimedia (IM) Core Network (CN) subsystem centralized services (ICS) allow for the delivery of consistent IMS services to the user regardless of the attached access type (e.g. CS domain access or IP-CAN).
The present document provides the protocol details for the realization of ICS based on the Session Initiation protocol (SIP), the Session Description Protocol (SDP), the I1 protocol, and the protocols of the 3GPP Circuit-Switched (CS) domain (e.g. CAP, MAP, ISUP, BICC and the NAS call control protocol for the CS access).
This document makes no ICS specific enhancements to SIP or SDP beyond those specified in 3GPP TS 24.229 [11].
The present document is applicable to User Equipment (UEs), MSC Servers and Application Servers (AS) providing ICS capabilities.
|
24.304
|
Mobility management based on Mobile IPv4; User Equipment (UE) - foreign agent interface; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.304/24304-i00.zip
|
The present document describes the stage 3 aspects of mobility management for User Equipment (UE) using IETF Mobile IPv4 foreign agent mode to access the Evolved Packet Core Network (EPC) through trusted non-3GPP access networks and for mobility management of UE between the 3GPP access network and trusted non-3GPP access networks.
In particular, the present document describes the UE – Mobile IPv4 Foreign Agent (FA) interface stage 3 aspects, where the FA functionality is located within the access network in the non-3GPP access domain.
The present document is applicable to the User Equipment (UE) and the network node implementing the FA functionality.
|
24.305
|
Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.305/24305-i00.zip
|
The present document specifies a mobile device Selective Disabling of 3GPP UE Capabilities (SDoUE) Management Object (MO) and the rules and corresponding behaviour of the UE with regard to the selective disabling of 3GPP UE capabilities, for example, when services or functions are disabled/enabled.
The SDoUE MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [8].
The SDoUE MO consists of the relevant parameters that can be managed for selective disabling of 3GPP UE capabilities.
The SDoUE MO defines a repository of data into the ME.
The service requirements for selective disabling of 3GPP UE capabilities are defined in 3GPP TS 22.011 [2].
|
24.312
|
Access Network Discovery and Selection Function (ANDSF) Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.312/24312-i00.zip
|
The present document defines management objects that can be used by the Access Network Discovery and Selection Function (ANDSF) and the UE.
The Management Objects (MO) are compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and are defined using the OMA DM Device Description Framework (DDF) as described in the enabler release definition OMA-ERELD-DM-V1_2 [5].
The MOs consist of relevant parameters:
- for access network discovery;
- for access network selection;
- for traffic steering; and
- for ePDG selection;
that can be managed by the ANDSF.
The service requirements and the functional requirements for the access network discovery and access network selection are described in 3GPP TS 22.278 [2] and in 3GPP TS 23.402 [4] respectively.
|
24.315
|
IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB); Stage 3: protocol specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.315/24315-i00.zip
|
The present document specifies the stage three, Protocol Description of the network feature Operator Determined Barring (ODB) of IMS Multimedia Telephony Services. It is based on the requirements described in 3GPP TS 22.041 [11]. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). ). In addition, it provides protocol details for XCAP for barring of supplementary services configuration.
The present document is applicable to:
- the Application Server (AS) intended to support Operator Determined Barring for communications;
- the AS that provides the XCAP based interface for manipulation of the settings for a supplementary service as defined in 3GPP TS 24.623 [9]; and
- the AS that supports the SIP based configuration for a supplementary service as defined in 3GPP TS 24.238 [8].
|
24.323
|
3GPP IP Multimedia Subsystem (IMS) service level tracing Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.323/24323-i00.zip
|
This document defines the IMS service level tracing management object. 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 [3].
The IMS service level tracing management object consists of relevant parameters that can be managed for IMS service level tracing capabilities specified in 3GPP TS 24.229 [5].
|
24.333
|
Proximity-services (ProSe) Management Objects (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.333/24333-i00.zip
|
The present document defines Management Objects (MO) that are used to configure the ProSe-enabled UE.
The MOs are compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and are defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [3].
The MOs consist of relevant parameters for provisioning and authorisation of ProSe at the ProSe-enabled UE.
The protocol aspects for ProSe are described in 3GPP TS 24.334 [4].
|
24.334
|
Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.334/24334-i00.zip
|
The present document specifies the protocols for Proximity-based Services (ProSe) between:
- the ProSe-enabled UE and the ProSe Function (over the PC3 interface); and
- two ProSe-enabled UEs (over the PC5 interface).
The present document defines the associated procedures for ProSe service authorisation, ProSe direct discovery (using E-UTRA or WLAN technology), EPC-level ProSe discovery and ProSe direct communication.
The present document also defines the message format, message contents, error handling and system parameters applied by the protocols for ProSe.
The present document is applicable to:
- the ProSe-enabled UE; and
- the ProSe Function.
|
24.337
|
IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transfer; Stage 3
|
TS
|
18.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.337/24337-i10.zip
|
IP Multimedia (IM) Core Network (CN) subsystem inter-UE transfer (IUT) provides the capability of continuing ongoing communication sessions with multiple media across different user equipments (UEs) under the control of the same or different subscribers, and as part of Service Continuity (SC).
The present document provides the protocol details for enabling IMS inter-UE transfer based on the Session Initiation protocol (SIP) and the Session Description Protocol (SDP).
The present document is applicable to User Equipment (UEs) and Application Servers (AS).
|
24.341
|
Support of SMS over IP networks; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.341/24341-i00.zip
|
The present document provides the protocol details for SMS over IP within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in 3GPP TS 24.229 [10].
The present document provides the protocol details for SMS over IP within the IP Multimedia (IM) Core Network (CN) subsystem based on the SMS layer as defined in 3GPP TS 24.011 [8].
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by 3GPP TS 24.229 [10].
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing SMS over IP functionality.
|
24.371
|
Web Real-Time Communications (WebRTC) access to the IP Multimedia (IM) Core Network (CN) subsystem (IMS); Stage 3; Protocol specification
|
TS
|
18.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.371/24371-i10.zip
|
The present document provides the details for allowing Web Real-Time Communication (WebRTC) IMS Clients (WIC) to access the IP Multimedia (IM) Core Network (CN) subsystem.
The present document is applicable to WebRTC IMS client (WIC), eP-CSCF, eIMS-AGW, WebRTC Web Server Function (WWSF) and WebRTC Authorization Function (WAF).
|
24.385
|
V2X services Management Object (MO)
|
TS
|
18.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.385/24385-i10.zip
|
The present document defines Management Object (MO) that is used to configure the UE for V2X services.
The MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [3].
The MO consists of relevant parameters for provisioning and authorization of V2X communication at the UE.
The protocol aspects for V2X are described in 3GPP TS 24.386 [4].
|
24.386
|
User Equipment (UE) to V2X control function; protocol aspects; Stage 3
|
TS
|
18.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.386/24386-i20.zip
|
The present document specifies the protocols:
- for V2X authorization between the UE and the V2X control function (over the V3 interface);
- for V2X communication among the UEs (over the LTE-PC5 interface, and over the NR-PC5 interface as described in 3GPP TS 24.587 [27] and 3GPP TS 38.331 [25]); and
- for V2X communication between the UE and the V2X application server (over the LTE-Uu interface).
The present document defines the associated procedures for V2X authorization and V2X communication.
The present document also defines the message format, message contents, error handling and system parameters applied by the protocols for V2X.
The present document is applicable to:
- the UE;
- the V2X control function; and
- the V2X application server.
|
24.390
|
Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.390/24390-i00.zip
|
The present document describes the procedures for using Unstructured Supplementary Service Data (USSD) operations for mobile initiated MMI mode over IP Multimedia Core Network Subsystem (IMS) and for network initiated MMI mode over IP Multimedia Core Network Subsystem (IMS). MMI mode is for the transparent transport of MMI strings entered by the user to the Application Servers (AS) and for the transparent transport of text strings back to the User Equipment (UE) to be displayed for user information. Support of either mode of USSD service is optional and only applicable for an operator's Public Land Mobile Network (PLMN).
The current version of the document describes procedures for USSD operation over IMS where the USSD application in the network resides on an AS. Signalling from the AS to other core network functional entities is left out of scope.
The present document is applicable to UE and AS which are intended to support USSD operations over IMS in mobile initiated MMI mode and network initiated MMI mode.
|
24.391
|
Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem (IMS) Management Object (MO)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.391/24391-i00.zip
|
The present document defines the unstructured supplementary service data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem (IMS) management object (MO). The MO 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 USSD using IMS (USSI) MO consists of relevant configuration parameters that can be managed for the UE's USSI capabilities specified in 3GPP TS 24.390 [3].
|
24.417
|
Management Object (MO) for Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.417/24417-i00.zip
|
The present document defines a Management Object (MO) for Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR). 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 OIP/OIR MO consists of relevant parameters that can be managed for the UE configuration related to the Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) service defined in 3GPP TS 24.607 [3].
|
24.424
|
Management Object (MO) for Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services (SS)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.424/24424-i00.zip
|
The present document defines the management object (MO) for extensible markup language (XML) configuration access protocol (XCAP) over the Ut interface for manipulating supplementary services (SS).
The MO for XCAP over Ut interface for manipulating SS 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 MO for XCAP over Ut interface for manipulating SS consists of relevant configuration parameters that can be managed for a UE supporting the UE role specified in 3GPP TS 24.623 [3].
|
24.486
|
Vehicle-to-Everything (V2X) Application Enabler (VAE) layer; Protocol aspects; Stage 3
|
TS
|
18.5.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.486/24486-i50.zip
|
The present document specifies the protocols for application layer support for V2X services as specified in 3GPP TS 23.286 [4] for:
a) V2X application communication among UEs (over the V5-AE interface); and
b) V2X application communication between the UE and the V2X application server (over the V1-AE interface).
The present specification defines the associated procedures for V2X application communication between the UE and the V2X application server and among UEs.
The present specification defines the usage and interactions of the VAE layer with SEAL services.
The present specification also defines the message format, message contents, error handling and system parameters applied by the protocols for the VAE layer.
|
24.523
|
Core and enterprise Next Generation Network (NGN) interaction scenarios; Architecture and functional description
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.523/24523-i00.zip
|
The present document provides the possible scenarios for:
- the interconnection of an Next Generation Corporate Network (NGCN) with a Next Generation
Network (NGN); and
- the support of NGCN capabilities within an NGN, either towards a User Equipment (UE) or to an NGCN.
Unless otherwise specified by reference to other documents, all requirements relating to architecture and functional requirements are contained within the present document.
|
24.524
|
Hosted enterprise services; Architecture, functional description and signalling
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.524/24524-i00.zip
|
The present document describes the architecture and functionality required to support enterprise and corporate services as IMS applications hosted in the NGN operator's network on behalf of an enterprise (Hosted Enterprise Services).
The present document also specifies the protocol requirements for the UE to attach to the NGN (in particular the IMS) and also any protocol requirements related to application servers provided in support of hosted enterprise services.
|
24.525
|
Business trunking; Architecture and functional description
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.525/24525-i00.zip
|
The present document provides architecture and functional requirements for business trunking for the Next Generation Network (NGN).
The present document also specifies the protocol requirements for the Next Generation Corporate Networks (NGCNs) to attach to the NGN (in particular the IM CN subsystem) and also any protocol requirements relation to application servers provided in support of business trunking.
Business trunking is a set of NGN capabilities that may be applied to communications between NGCNs using the NGN as a transit.
|
24.535
|
5G System (5GS); Device-Side Time Sensitive Networking (TSN) Translator (DS-TT) to Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.535/24535-i00.zip
|
The present document specifies the protocols of communication between a DS-TT and a NW-TT as specified in 3GPP TS 23.501 [2] for:
a) (g)PTP message delivery.
|
24.542
|
Notification management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification;
|
TS
|
18.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.542/24542-i20.zip
|
The present document specifies the protocol aspects for the notification management capability of SEAL to support vertical applications (e.g. V2X) over the 3GPP system for NM-UU reference point.
The present document is applicable to the User Equipment (UE) supporting the notification management client functionality as described in 3GPP TS 23.434 [2], to the application server supporting the notification management server functionality as described in 3GPP TS 23.434 [2] and to the application server supporting the vertical application server (VAL server) functionality as defined in specific vertical application service (VAL service) specification.
NOTE: The specification of the VAL server for a specific VAL service is out of scope of the present document.
|
24.544
|
Group Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification
|
TS
|
18.5.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.544/24544-i51.zip
|
The present document specifies the protocol aspects for the group management capability of SEAL to support vertical applications (e.g. V2X) over the 3GPP system.
The present document is applicable to the User Equipment (UE) supporting the group management client functionality as described in3GPP TS 23.434 [2], to the application server supporting the group management server functionality as described in 3GPP TS 23.434 [2] and to the application server supporting the vertical application server (VAL server) functionality as defined in specific vertical application service (VAL service) specification.
NOTE: The specification of the VAL server for a specific VAL service is out of scope for present document.
|
24.547
|
Identity management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.547/24547-i00.zip
|
The present document specifies the protocol aspects for the identity management capability of SEAL to support vertical applications (e.g. V2X) over the 3GPP system.
The present document is applicable to the User Equipment (UE) supporting the identity management client functionality as described in 3GPP TS 23.434 [2], to the application server supporting the identity management server functionality as described in 3GPP TS 23.434 [2] and to the application server supporting the vertical application server (VAL server) functionality as defined in specific vertical application service (VAL service) specifications.
NOTE: The specification of the VAL server for a specific VAL service is out of scope of the present document.
|
24.548
|
Network Resource Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification
|
TS
|
18.7.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.548/24548-i71.zip
|
The present document specifies the protocol aspects for the network resource management capability of SEAL to support vertical applications (e.g. V2X) over the 3GPP system.
The present document is applicable to the user equipment (UE) supporting the network resource management client functionality as described in 3GPP TS 23.434 [2], to the application server supporting the network resource management server functionality as described in 3GPP TS 23.434 [2] and to the application server supporting the vertical application server (VAL server) functionality as defined in the specific vertical application service (VAL service) specifications.
NOTE: The specification of the VAL server for a specific VAL service is out of scope of present document.
|
24.549
|
Network slice capability enablement- Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; Stage 3
|
TS
|
18.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.549/24549-i40.zip
|
The present document specifies the protocol aspects of the SEAL service for the network slice capability enablement to support identifying network slices with capabilities for vertical applications in the 3GPP system based on 5GS management system services and 5GS network services. The protocol aspects specify the User Equipment (UE) supporting the client functionality of this SEAL service and the network supporting the server functionality of this SEAL service, where the client functionality and server functionality are specified in 3GPP TS 23.434 [2] and 3GPP TS 23.435 [13].
The present document is applicable to the application servers supporting the Vertical Application Layer server (VAL server) functionality for a specific Vertical Application Layer service (VAL service). The specification for the VAL server for a specific VAL service is out of scope of the present document.
|
24.575
|
5G System; Multicast/Broadcast UE pre-configuration Management Object (MO)
|
TS
|
18.3.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.575/24575-i30.zip
|
The present document specifies UE pre-configuration for multicast/broadcast services (MBS) in order to receive the data of multicast communication services and broadcast communication services as specified in 3GPP TS 23.247 [3].
The present document defines a management object (MO) that can be used to configure the UE with parameters related to reception of data of multicast communication services and broadcast communication services.
The MO is compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and is defined using the OMA DM device description framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [8].
The MO consists of nodes and leaves conveying UE pre-configuration parameters used for multicast communication service and broadcast communication service selection and data reception.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.