id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
23.503 | Policy and charging control framework for the 5G System (5GS); Stage 2 | TS | 19.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.503/23503-j40.zip | The present document defines the Stage 2 policy and charging control framework for the 5G System specified in TS 23.501 [2] and TS 23.502 [3].
The policy and charging control framework encompasses the following high level functions:
- Flow Based Charging for network usage, including charging control and online credit control, for service data flows;
- Policy control for session management and service data flows (e.g. gating control, QoS control, etc.);
- Management for access and mobility related policies;
- Management of UE policy information.
Interworking with E-UTRAN connected to EPC is described in TS 23.501 [2].
TS 23.502 [3] contains the stage 2 procedures and flows for the policy and charging control framework and it is a companion specification to this specification.
TS 32.255 [21] contains the functional description of the converged offline and online charging functionality for the 5G System. |
23.527 | 5G System; Restoration procedures | TS | 19.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.527/23527-j30.zip | The present document defines the restoration procedures in the 5G System. |
23.540 | 5G System: Technical realization of Service Based Short Message Service; Stage 2 | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.540/23540-j20.zip | The present document defines the Stage 2 architecture, procedures and services to support service based short message service (SMS) in 5G system (5GS). |
23.542 | Application layer support for Personal IoT Network | TS | 19.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.542/23542-j10.zip | The present document specifies the application enabler layer architecture, procedures and information flows necessary for enabling PIN applications over 3GPP networks. The specification includes the capabilities (e.g. PIN management, discovery of elements, capabilities and services related to PIN) at the application enablement layer that fulfil the deployment and operational requirements of PIN applications over 3GPP networks. The PIN enabler capabilities applies to 5GS. |
23.548 | 5G System Enhancements for Edge Computing; Stage 2 | TS | 19.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.548/23548-j30.zip | The present document defines the Stage 2 specifications for enhancements of 5G System to support Edge Computing. |
23.554 | Application architecture for MSGin5G Service; Stage 2 | TS | 19.6.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.554/23554-j60.zip | The present document specifies the functional architecture, procedures, information flows and APIs for MSGin5G Service. MSGin5G Service provides messaging communication capability in 5GS especially for Massive Internet of Things (MIoT).
MSGin5G Service includes the following message communication models:
- Point-to-Point message;
- Application-to-Point message/ Point-to-Application message;
- Group message;
- Broadcast message.
The corresponding service requirements are defined in 3GPP TS 22.262 [2].
MSGin5G Service provides the following capabilities to enhance the message delivery for all message communication models:
- MSGin5G Store and Forward;
- Message communication based on Messaging Topic;
- Message Aggregation;
- Message Segmentation and Reassembly;
- Message Gateway to interwork with non MSGin5G messaging services;
- Usage of Network Capabilities including UE reachability status monitoring and MSGin5G device triggering.
The present specification also defines the usage and interactions of the MSGin5G Service with SEAL services and the utilizing of SEAL functionalities in MSGin5G service. |
23.558 | Architecture for enabling Edge Applications | TS | 19.6.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.558/23558-j60.zip | The present document specifies the application layer architecture, procedures and information flows necessary for enabling edge applications over 3GPP networks. It includes architectural requirements for enabling edge applications, application layer architecture fulfilling the architecture requirements and procedures to enable the deployment of edge applications. |
23.632 | User data interworking, coexistence and migration; Stage 2 | TS | 19.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.632/23632-j00.zip | The present document defines the Stage 2 architecture, procedures, flows and Network Function Services for User Data Interworking, Coexistence and Migration within the 5G System. |
23.682 | Architecture enhancements to facilitate communications with packet data networks and applications | TS | 19.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.682/23682-j20.zip | The present document specifies architecture enhancements to facilitate communications with packet data networks and applications (e.g. Machine Type Communication (MTC) applications on the (external) network/MTC servers) according to the use cases and service requirements defined in TS 22.368 [2], TS 22.101 [3], and related 3GPP requirements specifications. Both roaming and non-roaming scenarios are covered.
The present document also specifies transmission of non-IP data via SCEF for the CIoT EPS Optimization.
The present document also specifies the interface between the SCEF and the SCS/AS.
The present document also specifies provisioning of UCMF with RACS information. |
23.700-01 | Study on application enablement for Satellite access enabled 5G Services | TR | 19.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-01/23700-01-j00.zip | The present document is a technical report capturing the study on application enablement for Satellite access enabled 5G Services over 3GPP networks. The aspects of the study include identifying architecture requirements, supporting architecture for satellite access enabled 3GPP services and application enablers (either by defining new functional model or by enhancing existing functional model), and corresponding solutions.
The study is based on the requirements as defined in 3GPP TS 22.261 [2] and related use cases (for e.g. in 3GPP TR 22.822 [3] and 3GPP TR 22.865 [4]). The study is dependent on 3GPP TS 23.501 [5] (5GC architecture for satellite access for NR), 3GPP TS 23.502 [6] (procedures for NR satellite access), 3GPP TS 23.503 [7] (PCF for Satellite backhaul), 3GPP TS 23.401 [8] (EPC architecture for satellite access for IoT), 3GPP TS 23.682 [9] (EPC architecture enhancements to facilitate communications with packet data networks and applications). |
23.700-03 | Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS); Phase 3 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-03/23700-03-j00.zip | The present document will study and identify potential enhancements to the 5G Proximity-based Services (5G ProSe) system defined in TS 23.304 [4] (beyond what has been specified in Rel-17 and Rel-18) considering the services requirements defined in TS 22.278 [5], TS 22.261 [6] and TS 22.115 [7].
The study will investigate potential 5GS enhancements in the following areas:
- Enhance ProSe to support multi-hop over NR PC5 reference point for UE-to-Network Relay for Layer-2 and Layer-3 Relays.
- Enhance ProSe to support multi-hop over NR PC5 reference point for UE-UE Relay for Layer-3 Relays. |
23.700-06 | Study on architecture enhancements for vehicle-mounted relays - Phase 2 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-06/23700-06-j00.zip | The scope of this Technical Report is to study and identify potential architecture and system level enhancements for the 5G system to support the operation of a mobile gNB mounted on vehicles, using NR for wireless access toward the UE and for wireless backhaul access toward the 5GC. The study addresses the service requirements documented in TS 22.261 [3] for the mobile base station relays, and focuses on the following aspects:
- architecture enhancements for the support of the wireless backhauling of the mobile gNB and its CN/OAM (e.g. N2/N3) interfaces, including e.g. UE access control, mobility aspects;
- the architecture to enable authorization and configuration of the mobile gNB;
- support of UE location services and emergency services via the mobile gNB.
The wireless backhauling of mobile gNB and CN/OAM (e.g. N2/N3) interfaces may use the existing TN or NTN technology.
NOTE 1: The mobile gNB configuration aspect needs synchronization with RAN working group.
NOTE 2: No enhancement is aimed to the existing QoS mechanisms for the wireless backhaul. |
23.700-09 | Study on Mission critical services support in the Isolated Operation for Public Safety (IOPS) mode of operations | TR | 19.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-09/23700-09-j00.zip | This technical report is a study of mission critical service in the Isolated Operation for Public Safety (IOPS) mode of operation. The present document identifies architecture enhancements needed to support mission critical services delivered over IOPS, based on the stage 1 requirements, including 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.261 [4], and 3GPP TS 22.346 [5].
A previous technical report focused on EUTRAN in 3GPP TR23.778 [6] and associated normative work in 3GPP TS23.180 [7] have also been completed.
This document provides recommendations for normative work. |
23.700-13 | Study on Architecture support of Ambient power-enabled Internet of Things | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-13/23700-13-j00.zip | The present document studies the architecture support of Ambient IoT Devices, based on the services requirements defined in TS 22.369 [2] applicable to the Device types, traffic types, use cases and connectivity topologies defined in TR 38.769 [8]. |
23.700-21 | Study on Application enablement architecture for mobile metaverse services | TR | 19.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-21/23700-21-j10.zip | The present document is a technical report capturing the study on application enablement architecture for mobile metaverse services over 3GPP networks. The aspects of the study include defining key issues and their related solutions to identify architecture requirements, application layer functional model (either by defining new functional model or by enhancing existing functional model) to support identified architectural requirements and corresponding solutions to provide enablement layer support to metaverse applications.
The study is based on the requirements as defined in 3GPP TS 22.156 [2] and related use cases in 3GPP TR 22.856 [3]. The study takes into consideration the work done in other 3GPP working groups (like SA2, SA4). |
23.700-22 | Study on CAPIF Phase 3 | TR | 19.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-22/23700-22-j00.zip | The present document studies the potential enhancements to CAPIF (as specified in 3GPP TS 23.222[2]) to support: a) authentication and authorization interactions between Resource Owner and Authorization Functionality, b) UE-deployed API invoker accessing resources not owned by that UE, c) more granular access control (e.g., at the level of service operations or resources), d) CAPIF with further enhancements to service API status and AEF status, e) CAPIF enhancements identified or originated from other WGs or SDOs/industry forums and f) more CAPIF interconnection services. |
23.700-23 | Study on Application enabler for XR Services | TR | 19.2.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-23/23700-23-j20.zip | The present document studies application enabling layer architecture requirements, key issues, and solution recommendations to support XR services.
The study is based on the requirements defined in 3GPP TS 22.261 [2] and is dependent on the 5GC architecture supporting XRM services as specified in 3GPP TS 23.501 [3], 23.502 [4], and 23.503 [5]. |
23.700-29 | Study on integration of satellite components in the 5G architecture; Phase 3 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-29/23700-29-j00.zip | The scope of this Technical Report is to study the following aspects of 5GS/EPS integrating of satellite component in Release 19, including:
- Regenerative payload generic architecture:
- Impact to 5GS and EPS to support gNB/eNB onboard the satellite.
- Store and Forward Satellite operation for delay tolerant services:
- The control plane and user plane enhancements if applicable, including the minimum necessary set of Core Network elements to be embedded in the satellite, to support S&F Satellite operation, both for IoT NTN (EPS) and NR NTN (5GS);
- The parameters needed to characterize and support S&F Satellite operation from a delay tolerant services perspective if applicable, both for IoT NTN (EPS) and NR NTN (5GS).
NOTE: S&F for IoT NTN will be studied first and if there is remaining time available NR NTN can then be studied.
- UE-Satellite-UE communication enhancements for 5GS, supporting NR NTN NGSO constellation with and without ISL, with feeder link always available:
- Following SA1 requirements, study how IMS enablers including mission critical can be supported;
- Minimum necessary set of 5GS network functions onboard the satellite(s) to support such UE-Satellite-UE communication. |
23.700-32 | Study on User Identities and Authentication Architecture | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-32/23700-32-j00.zip | The present document studies how to enhance the 5G System to allow for the creation and utilization of user-specific identities in order to provide enhanced user experience, optimized performance, and offer services to non-3GPP devices and human users. For example, network settings can be adapted, and services can be offered to users according to users' needs, which may be different from the subscription identifier that is used by the user to establish the connection.
In this study, the user to be identified could be an individual human user using a UE with a certain subscription or a device behind a gateway UE or 5G-RG.
Use cases are discussed in clause 26a of TS 22.101 [2] and include:
- an individual human user, using a UE with a certain subscription; and
- a device ("thing") behind a gateway UE.
Requirements related to the collection of charging information for users are specified in clause 5.2.17 of TS 22.115 [3].
NOTE: Charging is in the remit of SA WG5. |
23.700-45 | Study on System aspects of 5G NR Femto | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-45/23700-45-j00.zip | The present document will study and identify potential enhancements for supporting 5G NR Femto deployment. The study will investigate potential enhancements in the following areas:
- How to enable interworking between CAG and CSG cells.
- Study whether and how to support enabling the provisioning of subscribers allowed to access CAG cell and to manage access control by the CAG owner or an authorized administrator.
NOTE 1: Based on RAN WG3 outcome, the overall architecture and enable the required functional and procedural changes can be enhanced for supporting 5G NR Femto deployment during normative work. |
23.700-49 | Study on Enhancement of support for Edge Computing in 5G Core network; Phase 3 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-49/23700-49-j00.zip | The present document describes key issues and solutions for the phase 3 of the system enhancements for Edge Computing in 5GS.
This technical report will document the study of potential system enhancements for enhanced edge computing support, including:
- Whether and how to support more efficient Edge Hosting Environment information management and related EAS Discovery:
- Handle the edge network and EAS related information (e.g. UPF and EAS deployment information, DNAIs) locally with less impact to 5GC central NFs (e.g. central SMF) to address more flexible EAS (re)discovery/(re)selection, local UPF (re)selection.
- Whether and how to take into account N6 Delay between the local PSA and EAS for local UPF and EAS (re)selection.
- Whether and how to support traffic sent to/from PSA after being processed by Edge Hosting Environment, e.g. when there is no communication possibility between the local part of the DN and central part of the DN (e.g. due to usage of private IP address, lack of secure tunnel); whether and how to support traffic being routed between two EASs located in two different Edge Environments when there is no pre-established communication path between the two local part of the DNs. |
23.700-54 | Study on Multi-Access (DualSteer and ATSSS_Ph4) | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-54/23700-54-j00.zip | The scope of this Technical Report is to:
- study and identify potential architecture and system level enhancements for the 5G system to support the operation of the DualSteer Device that is capable of traffic steering and switching of user data for different services across two 3GPP access networks. The study addresses the service requirements documented in TS 22.261 [2] and focuses on various aspects of architecture and functional enhancements including:
- impacts on subscription;
- impacts on registration procedure; and
- impacts on session management procedure and policies.
- study how the MPQUIC steering functionality defined in Rel-18 ATSSS can be extended to be able to steer, switch, and split non-UDP traffic (TCP, IP, Ethernet traffic); and
- study whether and how an alternative architecture and system level enhancements for ATSSS that does not require the existing non-3GPP interworking/gateway function, i.e. N3IWF, TNGF. |
23.700-59 | Study on architecture enhancements of UAS, UAV and UAM; Phase 3 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-59/23700-59-j00.zip | The present document is to investigate and identify potential architecture and system level enhancements to support additional scenarios and requirements for UAV (Uncrewed Aerial Vehicle) and UAM (Urban Air Mobility) including:
- Enhancement of NEF services to support service exposure and interactions between MNOs and UTM functions for i.e. pre-mission flight planning, in-mission flight monitoring, C2 communication reliability, interfacing with UTM (e.g. supporting the scenario of multiple USS serving the geographical areas corresponding to UAV flight path).
- Support of network-assisted/ground-based mechanism for DAA (Detect And Avoid).
- Support of no-transmit zones for UAVs. |
23.700-63 | Study on UPF enhancement for Exposure and SBA; Phase 2 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-63/23700-63-j00.zip | This Technical Report continues the study on key issue description, solution and conclusion on UPF enhancement for Exposure and SBA Phase 2.
The scopes include the following aspects:
- Study potential enhancements on UPF selection to discover UPF with specific user plane functionalities, e.g. NAT, Packet inspection, etc.;
- Study potential enhancements on UPF event exposure service to optimize the procedures related to UPF data collection, e.g. direct/indirect subscription of the UPF via control plane from application;
- Study potential enhancements to support the AF instruction via 5GC to UPF for packet inspection (e.g. UPF detection of certain IP header, HTTP header, etc.) for UL/DL traffic, as well as report collection of the indicated packet inspection from UPF. |
23.700-66 | Study on Energy Efficiency and Energy Saving | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-66/23700-66-j00.zip | This Technical Report will study and identify potential enhancements on 5GS (e.g. including network energy related information exposure, enhancement for subscription and policy control to enable energy efficiency as service criteria) to improve energy efficiency and to support energy saving in the network, taking the EnergyServ requirements in TS 22.261 [8] into consideration.
Potential enhancements on 5GS to take into account the availability of renewable energy may also be considered as part of this study. |
23.700-70 | Study on architecture enhancement for Extended Reality and Media service (XRM); Phase 2 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-70/23700-70-j00.zip | The Technical Report studies key issues, solutions and conclusions for support of advanced media services, e.g. High Data Rate Low Latency (HDRLL) services, AR/VR/XR services. The objectives include study of whether and how to:
- Enhance PDU Set based QoS handling.
- Enhance QoS handling for XR services.
- Enhance support of XR based on non-3GPP access.
- Expose XR related network capability/information towards the application layer. |
23.700-72 | Study on enhanced application layer support for location services | TR | 19.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-72/23700-72-j00.zip | The present document is a technical report which identifies the SA1 requirements and the potential vertical requirements for location services and proposes the application architecture requirements, key issues, and solutions to address the enhanced location capabilities based on the current vertical application enabler (e.g. SEAL).
The study takes into consideration the existing SEAL architecture specified in 3GPP TS 23.434 [9], the Core Network exposure specified in 3GPP TS 23.501[6] and 3GPP TS 23.502 [7], the 5GS location services as defined in TS 23.273[5], etc. to investigate how to support the enhanced location services in application layer.
Furthermore, the study also provides recommendations for the normative work. |
23.700-75 | Study on Multimedia Priority Service (MPS) for IMS Messaging and SMS services | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-75/23700-75-j00.zip | The scope of this Technical Report is to study solutions addressing MPS priority for SMS and MPS priority for messaging services based on IMS within the 3GPP system. For IMS, the scope is limited to MPS priority by the 3GPP system when SIP is used to support the messaging service.
The study will investigate the following aspects:
- Solutions addressing how MPS for messaging services is requested and authorized using a UE with a subscription for MPS.
- Solutions addressing gaps for MPS priority treatment for messaging services using TS 23.228 [4] specified SIP MESSAGE and SIP sessions in EPC and 5GC.
- Solutions addressing gaps for MPS priority treatment in EPC and 5GC for messaging services using MO/MT SMS over IP, and MO/MT SMS over NAS. For SMS, only subscription-based priority treatment is in scope. |
23.700-77 | Study on system architecture for next generation real time communication services; Phase 2 | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-77/23700-77-j00.zip | Editor's note: This clause will describe the scope for this study item.
This technical report studies further enhancements to the IMS network architecture, interfaces and procedures to support the next generation real time communication services requirements on the following aspects:
1. Study on the enhancements to framework for exposure of IMS capability in the context of IMS data channel session, including:
- enhancing the IMS architecture to define an event subscription mechanism to enable subscription to various IMS events of IMS data channel services;
- how to enhance NF services of IMS and 5GC to expose existing IMS services (e.g. IMS voice/video call, message) in the context of an IMS data channel session, i.e. when DC is established.
2. Study how to provide IMS data channel applications to the subscriber who is using a MTSI UE where it is appropriate depending on the applications.
3. Study how IMS architecture and procedures are enhanced to support verified OIP service for 3rd party in IMS session using SA WG3 work on third party identity authentication as basis.
4. Study on the enhancements to IMS data channel related services and operational aspects, including:
- whether and how to support standalone IMS data channel without accompanying audio/video/messaging media in an IMS session;
- how to support 3GPP PS Data Off for IMS data channel and applications over IMS data channel;
- study enhancements of IMS DC architecture and procedure to support multiplexing a SCTP connection for multiple DC applications.
5. Study whether and how to enhance IMS architecture, procedures, interfaces for supporting avatar call (including multi-party communication) and communication with accessibility as specified in clause 5.2.2 of TS 22.156 [9]. |
23.700-82 | Study on application layer support for AI/ML services | TR | 19.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-82/23700-82-j10.zip | The present document is a technical report which identifies the application enabling layer architecture, capabilities, and services to support AI/ML services at the application layer.
The aspects of the study include the investigation of application enablement impacts, the application enablement layer architecture enhancements and solutions needed to provide assistance in AI/ML operations (model distribution, transfer and training) at the VAL layer as well as at the application enablement layer (e.g., SEAL ADAES, EDGEAPP).
The study takes into consideration the work done for AI/ML in 3GPP TS 23.288 [2] and Rel-18 AIMLsys (3GPP TS 23.501 [5] and 3GPP TS 23.502 [6]), 3GPP TS 28.104 [3] and may consider other related work outside 3GPP. |
23.700-84 | Study on Core Network Enhanced Support for Artificial Intelligence (AI) / Machine Learning (ML) | TR | 19.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-84/23700-84-j00.zip | This study will focus on the following objectives:
- AI/ML cross-domain coordination aspects on whether and how to consider 5GC enhancements to LCS to support AI/ML based Positioning considering conclusions of the RAN study in TR 38.843 [6].
NOTE 1: UE data collection, model delivery and transfer to the UE and model identification/management are not within the scope of the study.
NOTE 2: Whether and how the scope could be extended in the future with additional AI/ML cross-domain coordination aspects will be decided based on expected future SA plenary decisions considering the outcome of the related work in the involved RAN WGs(s).
- Whether and what 5GC enhancements are needed to enable 5G system, including the AF, to assist in collaborative AI/ML operations involving NWDAF for Vertical Federated Learning (VFL).
NOTE 3: For Vertical Federated Learning, RAN and UE aspects are out of scope.
- Whether and how to enhance 5GC to support NWDAF-assisted policy & QoS control.
- Whether and how to enhance 5GC to address network abnormal behaviour, i.e. signalling storm, with the assistance of NWDAF. |
23.700-92 | Study on service aspects for supporting the eMMTel Service | TR | 19.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-92/23700-92-j00.zip | The present document studies the following aspects:
1) service aspects for supporting the eMMTel service based on requirements from stage 1, e.g. eMMTel specified in 3GPP TS 22.261 [2] and SA WG1 Rel-18 eMMTEL WID;
2) the service enabler layer capabilities exposure based on architecture and procedures specified in Annex AC.2 of 3GPP TS 23.228 [3] and SA WG2 Rel-18 NG_RTC WID; and
3) the necessary application layer architecture and procedures for enabling MMTel service enhanced with Data Channel usage in IMS network. |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-j20.zip | The present document defines the principal architecture of layer 3 and its sublayers on the GSM Um interface, i.e. the interface between Mobile Station (MS) and network; for the CM sublayer, the description is restricted to paradigmatic examples, call control, supplementary services, and short message services for non-GPRS services. It also defines the basic message format and error handling applied by the layer 3 protocols.
For CTS services, the present document defines the principal architecture of layer 3 on the GSM Um* interface, i.e. the interface between a CTS capable Mobile Station (CTS-MS) and a Fixed Part (FP).
The corresponding protocols are defined in other Technical Specifications, see clause 4.3.4.
For non-GPRS services the communication between sublayers and adjacent layers and the services provided by the sublayers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by the present document.
For GPRS services in addition the local information transfer and stimuli sent between sublayers is informatively included within Annex C of in the present document.
This document also defines the principal architecture of the EPS NAS and 5GS NAS layer 3 protocol and their sublayers, including the message format applied by layer 3.
In the present document MS is also used as a synonym for UE.
Descriptions in clauses 6 to 10 are not maintained actively. |
24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.008/24008-j30.zip | The present document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and the digital cellular telecommunications system.
It specifies the procedures used at the radio interface (Reference Point Um or Uu, see 3GPP TS 24.002 [15] or 3GPP TS 23.002 [127]) for Call Control (CC), Mobility Management (MM), and Session Management (SM).
When the notations for "further study" or "FS" or "FFS" are present in this TS they mean that the indicated text is not a normative portion of the present document.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPP TS 44.003 [16] and 3GPP TS 25.301 [128].
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007 [20].
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 19.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-j20.zip | The present document contains the coding of information necessary for support of supplementary service operation on the mobile radio interface layer 3.
Clause 2 gives the functional definitions and contents of messages for call independent supplementary service operations. Messages necessary for support of call related supplementary service operations are defined in TS 24.008.
Clause 3 gives the general format and coding for messages used for call independent supplementary service and the format and coding of information elements used for both call related and call independent supplementary service operations.
Clause 4 gives the specification of the call related and call independent supplementary service operations. |
24.186 | IMS Data Channel applications; Protocol specification | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.186/24186-j30.zip | The present document provides the protocol details for enhancements to IMS multimedia telephony communication services enabled by supporting the IMS data channel and for AR communication which is one of the applications based on IMS data channel capability, based on stage 1 requirements in 3GPP TS 22.261 [2] and stage 2 requirements in 3GPP TS 23.228 [3].
The present document is applicable to User Equipment (UE), Application Servers (AS)and IP Multimedia (IM) Core Network (CN) subsystem which are intended to support IMS multimedia telephony communication services supporting the IMS data channel and AR communication which is one of the applications based on IMS data channel capability. |
24.193 | 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.193/24193-j30.zip | The present document specifies the procedures for access traffic steering, switching and splitting (ATSSS) between the UE and the network across one 3GPP access network and one non-3GPP access network as specified in 3GPP TS 23.501 [2], 3GPP 23.502 [3], and 3GPP TS 23.316 [4].
The ATSSS can be supported over the access network where an MA PDU session can be established. The type of access network includes NG-RAN and untrusted non-3GPP access network as specified in 3GPP TS 23.501 [2], trusted non-3GPP access network, wireline access network and as specified in 3GPP TS 23.316 [4]. An MA PDU session established by the UE can also simultaneously use one 3GPP access network connected to EPC and one non-3GPP access network connected to 5GCN as specified in 3GPP TS 23.502 [3]. |
24.229 | IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.229/24229-j30.zip | The present document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
The present document is applicable to:
- the interface between the User Equipment (UE) and the Call Session Control Function (CSCF);
- the interface between the CSCF and any other CSCF;
- the interface between the CSCF and an Application Server (AS);
- the interface between the CSCF and an ISC gateway function;
- the interface between the ISC gateway function and an Application Server (AS);
- the interface between the CSCF and the Media Gateway Control Function (MGCF);
- the interface between the S-CSCF and the Multimedia Resource Function Controller (MRFC);
- the interface between the Application Server (AS) and the Multimedia Resource Function Controller (MRFC);
- the interface between the S-CSCF and the Media Resource Broker (MRB);
- the interface between the AS and the MRB;
- the interface between the MRB and the MRFC;
- the interface between the CSCF and the Breakout Gateway Control Function (BGCF);
- the interface between the BGCF and the MGCF;
- the interface between the CSCF and an IBCF;
- the interface between the IBCF and AS, MRFC or MRB;
- the interface between the E-CSCF and the Location Retrieval Function (LRF);
- the interface between the BGCF and any other BGCF;
- the interface between the CSCF and an external Multimedia IP network;
- the interface between the E-CSCF and the EATF;
- the interface between the E-CSCF and the terminating IMS network;
- the interface between the P-CSCF and the ATCF;
- the interface between the ATCF and the I-CSCF;
- the interface between the ATCF and the IBCF; and
- the interface between the transit function and the AS.
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 SDP. Where this is not possible, extensions to SIP and SDP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
As the IM CN subsystem is designed to interwork with different IP-Connectivity Access Networks (IP-CANs), the IP-CAN independent aspects of the IM CN subsystem are described in the main body and annex A of this specification. Aspects for connecting a UE to the IM CN subsystem through specific types of IP-CANs are documented separately in the annexes or in separate documents.
The document also specificies:
- HTTP for use by an AS and by an MRB in support of the provision of media resources; and
- HTTP for use by an IBCF and by an AS in support of the invocation of attestation and verification functions.
The document also specifies media-related requirements for the NAT traversal mechanisms defined in this specification.
NOTE: The present document covers only the usage of SIP and SDP to communicate with the enitities of the IM CN subsystem. It is possible, and not precluded, to use the capabilities of IP-CAN to allow a terminal containing a SIP UA to communicate with SIP servers or SIP UAs outside the IM CN subsystem, and therefore utilise the services provided by those SIP servers. The usage of SIP and SDP for communicating with SIP servers or SIP UAs outside the IM CN subsystem is outside the scope of the present document. |
24.247 | Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 | TS | 19.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.247/24247-j10.zip | The present document provides the protocol details for the messaging service within the IP Multimedia CN Subsystem (IMS) based on the Session Initiation Protocol (SIP), the Session Description Protocol (SDP) and, the Message Session Relay Protocol (MSRP) . The document covers immediate messaging, session based messaging and session-based messaging conferences, as described in 3GPP TS 22.340 [11].
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP, SDP and, MSRP, either directly, or as modified by 3GPP TS 24.229 [5].
The present document is applicable to Application Servers (ASs) , Media Resource Function Controllers (MRFCs), Media Resource Function Processors (MRFPs) and to User Equipment (UE) providing messaging capabilities.
This document does not cover the signalling between a MRFC and a MRFP. |
24.250 | Protocol for Reliable Data Service; Stage 3 | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.250/24250-j00.zip | The present document specifies a Reliable Data Service (RDS) protocol.
The present document defines the frame structure, format of fields and procedures for operation of the RDS protocol. RDS is mainly intended to be used for acknowledged data transfer, but it also supports unacknowledged data transfer.
The present document is applicable to the UE, the SCEF and to the P-GW in the Evolved Packet System (EPS) and to the UE, the SMF, NEF and to the UPF in the 5G System (5GS). |
24.257 | Uncrewed Aerial System (UAS) Application Enabler (UAE) layer; Protocol aspects; Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.257/24257-j30.zip | The present document specifies the protocols for application layer support for UAS services as specified in 3GPP TS 23.255 [2] for:
a) UAS application communication between the UE and the UAE server (over the U1-AE interface); and
b) UAS application communication among UEs (over the U1-AE interface using unicast Uu).
The present specification defines the associated procedures for UAS application communication between the UE and the UAE server and among UEs.
The present specification defines the usage and interactions of the UAE 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 UAE layer. |
24.275 | Management Object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony (MMTEL) communication service | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.275/24275-j00.zip | The present document defines the management object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony (MMTEL) communication service.
The MO for BCP of MMTEL communication service 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 BCP of MMTEL communication service consists of relevant configuration parameter that can be managed for a UE supporting the timer RequestTimeout specified in 3GPP TS 24.173 [3]. |
24.281 | Mission Critical Video (MCVideo) signalling control; Protocol specification | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.281/24281-j20.zip | The present document specifies the signalling control needed to support Mission Critical Video (MCVideo) service.
The MCVideo service and its associated media plane control protocols can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting MCVideo client, and MCVideo server. |
24.282 | Mission Critical Data (MCData) signalling control; Protocol specification | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.282/24282-j30.zip | The present document specifies the signalling control protocols needed to support Mission Critical Data (MCData) communications as specified by 3GPP TS 23.282 [2]. The present document specifies both on-network and off-network protocols.
The present document utilises the common functional architecture to support mission critical services as specified in 3GPP TS 23.280 [3], in support of MCData communications.
The MCData service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways.
The present document is applicable to User Equipment (UE) supporting the MCData client functionality, and to application servers supporting the MCData server functionality. |
24.283 | Mission Critical Location Management (MCLoc); Protocol Specification | TS | 1.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.283/24283-100.zip | The present document specifies the protocols needed to support the Mission Critical Location Management service (MCLoc).
Mission critical services are services that require particular features and preferential handling compared to normal telecommunication services, e.g., in support of police or fire brigade.
The MCLoc service can be used for public safety applications as well as for some specialized commercial applications (e.g., utility companies and railways).
In the 3GPP systems, the Mission Critical Location Management service described in this document is instantiated at the application layer and involves interactions between MCLoc application clients on UEs and MCLoc application servers. |
24.294 | IP Multimedia Subsystem (IMS) Centralized Services (ICS) protocol via I1 interface | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.294/24294-j00.zip | The present document describes the I1 interface between IMS Centralized Services (ICS) UE and Service Centralization and Continuity (SCC) Application Server (AS).
This specification defines a new application layer protocol over I1 interface, specifies the interaction between the ICS UE and the SCC AS including session control procedures and supplementary services control procedures.
The protocol is intended to be independent of the transport-layer protocol used so it can be applied to a number of technologies that need different transport-layer protocols.
The overall ICS architecture is specified in 3GPP TS 23.292 [2].
The procedures for delivery of IMS Service Continuity that do not use the I1 protocol are specified in the document 3GPP TS 24.237 [13].
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the IMS centralized services. |
24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.301/24301-j30.zip | The present document specifies the procedures used by the protocols for mobility management and session management between User Equipment (UE) and Mobility Management Entity (MME) in the Evolved Packet System (EPS). These protocols belong to the non-access stratum (NAS).
The EPS Mobility Management (EMM) protocol defined in the present document provides procedures for the control of mobility when the User Equipment (UE) is using the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN). The EMM protocol also provides control of security for the NAS protocols.
The EPS Session Management (ESM) protocol defined in the present document provides procedures for the handling of EPS bearer contexts. Together with the bearer control provided by the access stratum, this protocol is used for the control of user plane bearers.
For both NAS protocols the present document specifies procedures for the support of inter-system mobility between E‑UTRAN and other 3GPP or non-3GPP access networks:
- For inter-system mobility between E-UTRAN and GERAN, UTRAN or NG-RAN, this includes rules for a mapping between parameters and procedures used by the NAS protocols defined in the present document and the NAS protocols specified in 3GPP TS 24.008 [13] for GERAN and UTRAN, and 3GPP TS 24.501 [54] for NG-RAN.
- For inter-system mobility between E-UTRAN and generic non-3GPP access networks, this includes specific NAS procedures to maintain IP connectivity to the PDN Gateway and to provide parameters needed by the UE when using mobility management based on Dual-Stack Mobile IPv6 (see 3GPP TS 24.303 [14]) or MIPv4 (see 3GPP TS 24.304 [15]).
The present document is applicable to the UE and to the Mobility Management Entity (MME) in the EPS.
The present document is also applicable to the relay node in the EPS (see 3GPP TS 23.401 [10]).
The present document also specifies NAS signalling enhancement for the support of efficient transport of IP, non-IP, Ethernet and SMS data of CIoT capable devices. |
24.302 | Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.302/24302-j00.zip | The present document specifies the discovery and network selection procedures for access to 3GPP Evolved Packet Core (EPC) via non-3GPP access networks and includes Authentication and Access Authorization using Authentication, Authorization and Accounting (AAA) procedures used for the interworking of the 3GPP EPC and the non-3GPP access networks.
The present document also specifies the Tunnel management procedures used for establishing an end-to-end tunnel from the UE to the ePDG to the point of obtaining IP connectivity and includes the selection of the IP mobility mode.
The non-3GPP access networks considered in this present document are cdma2000® HRPD and Worldwide Interoperability for Microwave Access (WiMAX), and any access technologies covered in 3GPP TS 23.402 [6]. The present document also specifies UE access to PLMN IP-based services via restrictive non-3GPP access networks covered in 3GPP TS 33.402 [15]. These non-3GPP access networks can be trusted or untrusted access networks.
The present document is applicable to the UE and the network. In this technical specification the network is the 3GPP EPC.
NOTE: cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA). |
24.303 | Mobility management based on Dual-Stack Mobile IPv6; Stage 3 | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.303/24303-j00.zip | The present document specifies the signalling procedures for accessing the 3GPP Evolved Packet Core network and handling the mobility between 3GPP and non-3GPP accesses via the S2c reference point defined in 3GPP TS 23.402 [3].
The present document is applicable to the User Equipment (UE) and the network node implementing the Home Agent functionality.
In addition the present document specifies the procedures used for the DSMIPv6 Home Agent discovery, for bootstrapping the DSMIPv6 security association between the UE and the Home Agent and for managing the DSMIPv6 tunnel. The specification of these procedures is compliant to IETF RFCs.
DSMIPv6 procedures can be used independently of the underlying access technology. |
24.322 | Tunnelling of IP Multimedia Subsystem (IMS) services over restrictive access networks; Stage 3 | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.322/24322-j00.zip | The present document specifies procedures and protocol elements for tunnelling of IMS traffic over restrictive access networks, specifically procedures and protocol elements for establishing, maintaining, and sending traffic via a firewall traversal tunnel between the UE and an enhanced firewall traversal function (EFTF) in the network. The present document is applicable to UE and EFTF.
The present document applies only to the case when the IMS traffic is not routed via EPC of a PLMN. Procedures for tunnelling of IMS traffic that is routed via EPC are specified in 3GPP TS 24.302 [3] annex F. |
24.368 | Non-Access Stratum (NAS) configuration Management Object (MO) | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.368/24368-j20.zip | The present document defines a Management Object (MO) that can be used to configure the UE with parameters related to Non-Access Stratum (NAS) 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 [2].
The MO consists of relevant parameters for NAS related configuration of a UE. |
24.369 | Ambient IoT Non-Access-Stratum (AIoT NAS) protocol for 5G System (5GS); Stage 3 | TS | 0.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.369/24369-010.zip | The present document specifies the ambient internet of things (AIoT) non-access-stratum (NAS) protocol to support the transport of signalling and AIoT data between AIoT device and the AIoT function (AIOTF) in the 5G system (5GS) as specified in 3GPP TS 23.369 [2].
Editor’sEditor's note: The scope should be aligned with the naming of the protocol and is FFS. |
24.379 | Mission Critical Push To Talk (MCPTT) call control; Protocol specification | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.379/24379-j30.zip | The present document specifies the session control protocols needed to support Mission Critical Push To Talk (MCPTT). The present document specifies both on-network and off-network protocols.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The MCPTT service can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting the MCPTT client functionality, and to application servers supporting the MCPTT server functionality. |
24.380 | Mission Critical Push To Talk (MCPTT) media plane control; Protocol specification | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.380/24380-j00.zip | The present document specifies the media plane control protocols and interactions with the media needed to support Mission Critical Push To Talk (MCPTT).
The present document specifies protocol for using pre-established session to setup calls, floor control and managing MBMS subchannels over MBMS bearers on-network and off-network protocols for floor control.
Mission critical communication services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade. Floor control provides a mechanism for managing the right to transmit at a point in time during an MCPTT call.
The MCPTT service and its associated media plane control protocols can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting the floor participant functionality, setting up calls using pre-established SIP sessions and using MBMS bearers for group communication and to floor control servers supporting these functions in the MCPTT system. |
24.392 | Application enablement aspects for MMTel; Protocol specification | TS | 0.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.392/24392-020.zip | The present document specifies the protocols aspects for supporting application layer procedures to enable download and update of the data channel application profiles on UE between the MMTel enabler client on UE and the MMTel enabler server over the MMTel-1 interfaces as specified in 3GPP TS 23.392 [2]. |
24.481 | Mission Critical Services (MCS) group management; Protocol specification | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.481/24481-j00.zip | The present document specifies the group management protocols needed to support Mission Critical Services (MCSs).
Group management applies only when the UE operates on the network.
MCSs are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
MCSs can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to User Equipment (UE) supporting the group management client (GMC) functionality, to application servers supporting the group management server (GMS) functionality, and to application servers supporting the Mission Critical Push To Talk (MCPTT), the Mission Critical Video (MCVideo) and Mission Critical Data (MCData) server functionality. |
24.482 | Mission Critical Services (MCS) identity management; Protocol specification | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.482/24482-j00.zip | This document specifies the identity management and authentication protocols needed to support Mission Critical Services (MCSs). Identity management applies only to on-network operation.
MCSs are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
MCSs can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
This document is applicable to User Equipment (UE) supporting the identity management client functionality, and to application servers supporting the identity management server functionality. |
24.483 | Mission Critical Services (MCS) Management Object (MO) | TS | 19.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.483/24483-j10.zip | The present document defines a number of Mission Critical Services (MCSs) Management Objects (MO) that are configured for the UE for the operation of MCSs. The management objects are compatible with OMA Device Management protocol specifications, version 1.2 and upwards, and is defined using the OMA DM Device Description Framework as described in the Enabler Release Definition OMA OMA-ERELD_DM-V1_2 [2].
MCSs are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
MCSs can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an UE supporting on-line, off-line or both on-line and off-line configuration of the configuration management client.
The present document is applicable to an UE supporting off-line configuration of the group management client.
The parameters defined by the management objects in the present document are configured in the UE using on-line configuration over the CSC-4 reference point and using off-line configuration over the CSC-11 and CSC-12 reference points. Other specifications define how these parameters are used in the operation of MCSs, and whether they are applicable to on-network operation or off-network operation, or both:
- 3GPP TS 24.379 [7];
- 3GPP TS 24.380 [8];
- 3GPP TS 24.481 [9];
- 3GPP TS 24.482 [11];
- 3GPP TS 24.484 [12];
- 3GPP TS 24.282 [16];
- 3GPP TS 24.582 [17];
- 3GPP TS 24.281 [18]; and
- 3GPP TS 24.581 [19].
The common network operation means both on-network operation and off-network operation in the present document.
The following management objects are defined in the present document:
- MCPTT UE configuration MO;
- MCPTT user profile MO;
- MCS group configuration MO;
- MCPTT service configuration MO;
- MCS UE initial configuration MO;
- MCData UE configuration MO;
- MCData user profile MO;
- MCData service configuration MO;
- MCVideo UE configuration MO;
- MCVideo user profile MO; and
- MCVideo service configuration MO.
The MOs listed above define repositories of data in the ME. |
24.484 | Mission Critical Services (MCS) configuration management; Protocol specification | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.484/24484-j20.zip | The present document specifies the configuration management documents and protocols needed to support Mission critical service online configuration over the CSC-4 and CSC-5 reference points and the procedures to support Mission critical service offline configuration over the CSC-11 and CSC-12 reference points.
Mission critical services include:
- Mission Critical Push To Talk (MCPTT);
- Mission Critical Video (MCVideo); and
- Mission Critical Data (MCData).
Configuration management documents defined in the present document includes:
- MCS UE initial configuration document;
- MCPTT UE configuration document;
- MCPTT user profile configuration document;
- MCPTT service configuration document;
- MCVideo UE configuration document;
- MCVideo user profile configuration document;
- MCVideo service configuration document;
- MCData UE configuration document;
- MCData user profile configuration document; and
- MCData service configuration document.
Mission critical services are services that require preferential handling compared to normal telecommunication services, e.g. in support of police or fire brigade.
The Mission critical services can be used for public safety applications and also for general commercial applications (e.g., utility companies and railways).
The present document is applicable to an MCS UE supporting the configuration management client functionality, to application servers supporting the configuration management server functionality, and to application servers supporting the:
- MCPTT server functionality;
- MCVideo server functionality; or
- MCData server functionality. |
24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.501/24501-j30.zip | The present document specifies the non-access stratum (NAS) procedures in the 5G system (5GS) used by the protocols for:
- mobility management between the user equipment (UE) and the access and mobility management function (AMF) for both 3GPP access and non-3GPP access; and
- session management between the user equipment (UE) and the session management function (SMF) for both 3GPP access and non-3GPP access.
The 5GS mobility management (5GMM) protocol defined in the present document provides procedures for the control of mobility when the user equipment (UE) is using the NG radio access network (NG-RAN), non-3GPP access network, or both. The 5GMM protocol also provides control of security for the NAS protocols.
The 5GS session management (5GSM) protocol defined in the present document provides procedures for the handling of 5GS PDU sessions. Together with the bearer control provided by the access stratum, this protocol is used for the control of user-plane resources.
For both NAS protocols the present document specifies procedures for the support of inter-system mobility between the NG-RAN and the evolved universal terrestrial radio access (E-UTRAN), between the NG-RAN and the non-3GPP access network connected to the EPC, and between the non-3GPP access network connected to the 5G core network (5GCN) and the E-UTRAN.
For both NAS protocols the present document specifies procedures for the support of mobility between the NG-RAN and the non-3GPP access network connected to the 5GCN.
In addition, the present document specifies the procedures in the 5GS for UE policy delivery service between the UE and the policy control function (PCF) for both 3GPP access and non-3GPP access.
The present document is applicable to the UE, the access and mobility management function (AMF), the session management function (SMF), and the PCF in the 5GS.
The clauses and subclauses in the present document are common for both 3GPP access and non-3GPP access unless it is explicitly stated that they apply to 3GPP access only or non-3GPP access only. |
24.502 | Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.502/24502-j20.zip | The present document specifies non-3GPP access network discovery and selection procedures, the access authorization procedure used for accessing non-3GPP access networks. These non-3GPP access networks can be trusted non-3GPP access networks, untrusted non-3GPP access networks or wireline access networks.
The present document also specifies the security association management procedures used for establishing IKEv2 and IPsec security associations:
- between the UE and the N3IWF and the procedures for transporting messages between the UE and the N3IWF over the non-3GPP access networks; and
- between the UE and the TNGF and the procedures for transporting messages between the UE and the TNGF over the non-3GPP access networks.
The present document also specifies the EAP-5G procedures used for exchange of NAS messages via trusted non-3GPP access before the UE is authenticated and authorized to use the trusted non-3GPP access.
The present document is applicable to the UE, the 5G-RG, the W-AGF acting on behalf of the FN-RG or the W-AGF acting on behalf of the N5GC device and the network. In this technical specification the network refers to the 3GPP 5GCN and the trusted non-3GPP access, untrusted non-3GPP access, or wireline access network.
NOTE 1: The present document is not applicable to the FN-RG.
NOTE 2: The W-AGF acting on behalf of the FN-BRG, accessing an SNPN is not defined in the present version of the present document. |
24.514 | Ranging based services and sidelink positioning in 5G system(5GS); Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.514/24514-j30.zip | The present document specifies the protocols for ranging based service and sidelink positioning in 5G system as specified in 3GPP TS 23.586 [2] for the following aspects:
a) provisioning of configuration information for ranging and sidelink positioning service;
b) ranging and sidelink positioning UE discovery; and
c) ranging and sidelink positioning communication, including the communication among UEs and the communication between UE and LMF. The support of ranging and sidelink positioning protocol (RSPP) transport is defined as part of the ranging and sidelink positioning communication.
The present document defines the associated procedures for the aspects listed above, and also defines the message format, message contents, error handling and system parameters applied by the protocols for ranging based service and sidelink positioning in 5GS. |
24.526 | User Equipment (UE) policies for 5G System (5GS); Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.526/24526-j30.zip | The present document defines UE policies for 5G System (5GS) as specified in 3GPP TS 23.503 [2] including:
- UE route selection policy; and
- Access network discovery and selection policy. |
24.538 | Enabling MSGin5G Service; Protocol specification | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.538/24538-j20.zip | The present document specifies the protocol aspects for supporting MSGin5G services as specified in 3GPP TS 23.554 [2] for:
1. communication between the MSGin5G UE and the MSGin5G Server over the MSGin5G-1 interface;
2. communication between the Application Client and the MSGin5G Client over the MSGin5G-5 interfaces; and
3. communication between the MSGin5G Client residing on the Constrained UE and the MSGin5G Gateway Client over the MSGin5G-6 interfaces.
The present specification defines the usage and interactions of the MSGin5G Service with SEAL services.
The present specification also defines the message format, message contents, error handling and system parameters applied by the protocols for the MSGin5G Service. |
24.539 | 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.539/24539-j30.zip | The present document specifies the protocols of communication between:
a) a DS-TT and a TSN AF;
b) a NW-TT and a TSN AF;
c) a DS-TT and a TSCTSF; and
d) a NW-TT and a TSCTSF;
as specified in 3GPP TS 23.501 [2] for:
a) port management regarding Ethernet ports or PTP ports; and
b) user plane node management. |
24.543 | Data delivery management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol Specification; | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.543/24543-j20.zip | The present document specifies the protocol aspects for the data delivery management capability of SEAL for the application content/data for vertical applications (e.g. V2X) over the 3GPP system as part of SEAL services specified in 3GPP TS 23.434 [3] and 3GPP TS 23.433 [2].
The present document is applicable to the user equipment (UE) supporting the data delivery management client functionality as described in 3GPP TS 23.433 [2], to the application server supporting the data delivery management server functionality as described in 3GPP TS 23.433 [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.545 | Location Management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.545/24545-j20.zip | The present document specifies the protocol aspects for the location 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 location management client functionality as described in 3GPP TS 23.434 [4], to the application server supporting the location management server functionality as described in 3GPP TS 23.434 [4] 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 1: The specification of the VAL server for a specific VAL service is out of scope of present document.
NOTE 2: Non-3GPP access used by the UE is out of scope of the present document. |
24.546 | Configuration management - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification | TS | 19.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.546/24546-j00.zip | The present document specifies the protocol aspects for the configuration 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 configuration management client functionality as described in 3GPP TS 23.434 [2], to the application server supporting the configuration 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.550 | Digital asset, Spatial mapping and Spatial anchors server - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; | TS | 1.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.550/24550-100.zip | The present document specifies the protocol aspects and APIs for the metaverse application over the 3GPP network for SAn-UU, SM-UU, and DA-UU reference points. The APIs are specified as RESTful APIs except for custom operations wherever required.
The present document is applicable to the user equipment (UE) supporting the digital asset as described in 3GPP TS 23.438 [3], spatial mapping and spatial anchor client functionalities as described in 3GPP TS 23.437 [2], to the application server supporting the digital asset as described in 3GPP TS 23.438 [3], spatial mapping and spatial anchor server functionalities as described in 3GPP TS 23.437 [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.554 | Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.554/24554-j20.zip | The present document specifies the protocols for Proximity-based Services (ProSe) in 5G system as specified in 3GPP TS 23.304 [2] for:
a) 5G ProSe direct discovery;
b) 5G ProSe communication over the PC5 interface;
c) 5G ProSe-enabled UE-to-network relay; and
d) 5G ProSe-enabled UE-to-UE relay.
The present document defines the associated procedures for 5G ProSe service authorization, 5G ProSe direct discovery (e.g. the procedures between 5G ProSe-enabled UE and 5G Direct Discovery Name Management Function (DDNMF) over the PC3a interface, the procedures over the PC5 interface), 5G ProSe UE-to-network relay discovery, 5G ProSe UE-to-UE relay discovery and 5G ProSe direct communication.
The present document also defines the message format, message contents, error handling and system parameters applied by the protocols for ProSe in 5GS. |
24.555 | Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3 | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.555/24555-j20.zip | The present document defines User Equipment (UE) policies that are used to configure the UE for Proximity-based Services (ProSe) in 5G System (5GS) based on the architectural requirements defined in 3GPP TS 23.304 [2].
The protocol aspects for 5G ProSe are described in 3GPP TS 24.554 [3]. |
24.558 | Enabling Edge Applications; Protocol specification | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.558/24558-j30.zip | The present document specifies the stage-3 protocol and data model for services. It provides stage-3 protocol definitions and message flows, and specifies the APIs for services offered by the Edge Enabler Server and the Edge Configuration Server.
The stage 2 architecture and procedures are specified in 3GPP TS 23.558 [2].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [6]. |
24.559 | Application Data Analytics Enablement Service (ADAES); Stage 3 | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.559/24559-j20.zip | The present document specifies the stage 3 protocol and data model for the Application Data Analytics Enablement (ADAE) Services. It provides stage 3 protocol definitions and message flows, and specifies the APIs for services offered by the ADAE Server.
The stage 2 architecture and procedures are specified in 3GPP TS 23.436 [3].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [6]. |
24.560 | Artificial Intelligence Machine Learning (AIML) Services - Service Enabler Architecture Layer for Verticals (SEAL); Protocol Specification; Stage 3 | TS | 1.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.560/24560-100.zip | The present document specifies the stage 3 protocol and data model for the AIML enabling SEAL services. It provides stage 3 protocol definitions and message flows and specifies the API for each service offered by the AIML server.
The stage 2 architecture and procedures are specified in 3GPP TS 23.482 [4].
The common protocol and interface aspects for API definition are specified in clause 5.2 of 3GPP TS 29.122 [5].
The present document is applicable to the user equipment (UE) supporting AIML enabling SEAL services functionalities as described in 3GPP TS 23.482 [4], to the application server supporting AIML enabling SEAL services functionalities as described in 3GPP TS 23.482 [4], 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 the scope of the present document. |
24.571 | 5G System (5GS); Control plane Location Services (LCS) procedures; Stage 3 | TS | 19.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.571/24571-j10.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 NG-RAN.
The present document is applicable to the User Equipment (UE) and to the Access and Mobility Management Function (AMF) or Location Management Function (LMF) in the 5G System (5GS).
The present document is developed in accordance to the general principles stated in 3GPP TS 23.273 [2]. |
24.572 | 5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3 | TS | 19.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.572/24572-j30.zip | The present document specifies the LCS user plane protocol (LCS-UPP) to support the Location Services in the 5G System (5GS) as specified in 3GPP TS 23.273 [2] for user plane positioning between the UE and the LMF.
The present document also specifies the user plane positioning connection management (UPP-CM) protocol to support the LCS secured user plane connection between the UE and the LMF.
The present document also specifies the LCS user plane protocol (LCS-UPP) to support location event reporting over an LCS secured user plane connection between the UE and the LCS client or the AF.
The present document also defines the message format, message contents, error handling and system parameters applied by the LCS-UPP and the UPP-CM protocol for supporting Location Services in 5GS. |
24.577 | Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 | TS | 19.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.577/24577-j10.zip | The present document specifies the protocols for aircraft-to-everything (A2X) communication as specified in 3GPP TS 23.256 [3] for A2X services among the UEs over the PC5 interface and over Uu. |
24.587 | Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 | TS | 19.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.587/24587-j20.zip | The present document specifies the protocols for vehicle-to-everything (V2X) services network as specified in 3GPP TS 23.287 [3] for:
a) V2X communication among the UEs over the PC5 interface; and
b) V2X communication between the UE and the V2X application server over the Uu interface.
This specification also covers interworking with EPS for V2X services in 5GS. |
24.812 | Study on MINT support in EPS for 5G-only national roaming UE | TR | 19.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.812/24812-j10.zip | The present document is to study the stage 2 aspect for service requirements defined by SA WG1 under SA1 work item MINT_Ph2 (Minimization of Service Interruption Phase 2), as specified in 3GPP TS 22.011 [2] and 3GPP TS 22.261 [3] clause 6.31. |
26.113 | Real-Time Media Communication; Protocols and APIs | TS | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.113/26113-j00.zip | The present document specifies the set of stage-3 procedures, APIs, and protocols for the reference points defined in Real-Time Media Communication (RTC) architecture. While TS 26.510 defines the common set of APIs and interactions, this document refers to TS 26.510 for the general aspects and primarily deals with RTC-specific aspects to support WebRTC-based real-time media transport over 5G. |
26.114 | IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction | TS | 19.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.114/26114-j10.zip | The present document specifies a client for the Multimedia Telephony Service for IMS (MTSI) supporting conversational speech (including DTMF), video and text transported over RTP, and flexible data channel handling, with the scope to deliver a user experience equivalent to or better than that of Circuit Switched (CS) conversational services using the same amount of network resources. It defines media handling (e.g. signalling, transport, jitter buffer management, packet-loss handling, adaptation), as well as interactivity (e.g. adding or dropping media during a call). The focus is to ensure a reliable and interoperable service with a predictable media quality, while allowing for flexibility in the service offerings.
The present document describes two client types:
- An MTSI client in terminal which uses a 3GPP access (NR, LTE, HSPA, or EGPRS) to connect to the IMS. These clients are described in Clauses 5 – 17 and Annexes A – M.
- An MTSI client in terminal which uses a fixed access (corded interface, fixed-wireless interface, e.g. Wi-Fi, Bluetooth or DECT/NG DECT) to connect to the IMS. These clients are described in Clause 18.
MTSI clients using 3GPP access and MTSI clients using fixed access have many common procedures for the media handling. This specification aligns the media handling by using cross references whenever possible. This does not mean that 3GPP terminals must support fixed access, nor does it mean that fixed terminals must support 3GPP access.
The scope includes maintaining backward compatibility in order to ensure seamless inter-working with existing services available in the CS domain, such as CS speech and video telephony, as well as with terminals of earlier 3GPP releases. In addition, inter-working with other IMS and non-IMS IP networks as well as traditional PSTN is covered.
The client may also support the IMS Messaging service and Group 3 facsimile transmission. The scope therefore also includes media handling for non-conversational media using MSRP and UDPTL-based Facsimile over IP (FoIP).
The specification is written in a forward-compatible way in order to allow additions of media components and functionality in releases after Release 7.
NOTE 1: MTSI clients can support more than conversational speech, video and text, which is the scope of the present document. See TS 22.173 [2] for the definition of the Multimedia Telephony Service for IMS.
NOTE 2: TS 26.235 [3] and TS 26.236 [4] do not include the specification of an MTSI client, although they include conversational multimedia applications. Only those parts of TS 26.235 [3] and TS 26.236 [4] that are specifically referenced by the present document apply to Multimedia Telephony Service for IMS.
NOTE 3: The present document was started as a conclusion from the study in TR 26.914 [5] on optimization opportunities in Multimedia Telephony for IMS (TR 22.973 [6]).
NOTE 4: For ECN, the present specification assumes that an interface enables the MTSI client to read and write the ECN field. This interface is outside the scope of this specification. |
26.265 | Media Delivery: Video Capabilities and Operating Points | TS | 1.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.265/26265-120.zip | [Video codecs, encoders, and decoders are core components of 3GPP services. At the same time, video encoders and decoders, residing on 3GPP User Equipment (UE) and defined in 3GPP specifications, also provide interoperability points for third-party services. Video capabilities are predominantly independent of the service in use. This specification addresses the definition of video capabilities and operating points such that 3GPP service specifications as well as third-party service providers can refer to the interoperability points defined in this specification. |
26.346 | Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs | TS | 19.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.346/26346-j10.zip | The present document defines a set of media codecs, formats and transport/application protocols to enable the deployment of MBMS user services either over the MBMS bearer service or other UMTS Bearer Services within the 3GPP system.
In this version of the specification, only MBMS download and streaming delivery methods are specified. The present document does not preclude the use of other delivery methods.
The present document includes information applicable to network operators, service providers and manufacturers. |
26.501 | 5G Media Streaming (5GMS); General description and architecture | TS | 19.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.501/26501-j10.zip | The present document specifies the 5G Media Streaming (5GMS) architecture. The 5GMS supported services include MNO and third-party Downlink Media Streaming Services, and MNO and third-party Uplink Media Streaming Services. The 5GMS architecture supports related network and UE functions and APIs, backwards compatible functions for EUTRAN deployments (with and without MBMS) and 5G specific features.
NOTE: Support of 5G Media Streaming over MBMS with 5GC is not considered in the current version of the present document.
The 5GMS architecture is functionally divided into independent components enabling different deployments with various degrees of integration between 5G MNOs and Content Providers. It is specified as a set of extensions to TS 23.501 "System Architecture for the 5G System".
Many of the features defined in this document are motivated by the conclusions of TR 26.804 [36]. |
26.502 | 5G multicast-broadcast services; User service architecture | TS | 19.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.502/26502-j10.zip | The present document defines an architecture and high-level procedures for User Services conveyed using the 5G multicast–broadcast capabilities of the 5G System defined in TS 23.501 [2], TS 23.502 [3] and TS 23.247 [5].
The design of the system is primarily motivated by the conclusions of TR 26.802 [23]. |
26.565 | Split Rendering Media Service Enabler | TS | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.565/26565-j00.zip | The present document defines a Media Service Enabler for Split Rendering according to the guidelines of TR26.857 [1]. The Split Rendering MSE covers functionality on the UE and on the Media AS. It also defines an API that is exposed to application developers on the UE to start and manage split rendering sessions. |
26.506 | 5G Real-time Media Communication Architecture (Stage 2) | TS | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.506/26506-j00.zip | The present document specifies an architecture for real-time media communication integrated into the 5G System. To support Mobile Network Operator (MNO) and third-party services for real-time media, essential functionalities and interfaces are specified. The primary scope of this Technical Specification is the documentation of the following aspects:
- The definition of a real-time media communication architecture mapped to the 5GS architecture, with relevant core building blocks, reference point, and interfaces to support modern operator and third-party media services, based on the 5GMS architecture.
- Definition of all relevant reference points and interfaces to support different collaboration scenarios between 5G System operator and third-party media communication service provider, including but not limited to an Augmented Reality (AR) media communication service provider.
- Call flows and procedures for different real-time communication service types.
- Specification to support functionalities relevant to AR such as split-rendering or spatial computing on top of a 5G System based on this architecture. |
26.522 | 5G Real-time Media Transport Protocol Configurations | TS | 19.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.522/26522-j10.zip | The present document focuses on RTP [4] over UDP [9] for eXtended Reality in 5G.
RTP Header Extensions and RTCP Feedback Reporting are introduced for real-time immersive media and associated metadata for use in 5G Systems. |
26.567 | Split rendering over IMS | TS | 1.2.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.567/26567-121.zip | The present document specifies functional entities, reference points and protocols for IMS-based split rendering. It also provides codecs for delivery of split-render media and metadata of split rendered content for both uplink and downlink. The present document also contains procedures of split rendering session establishment, session management, adaptation, as well as other procedures to support split rendering process based on network support functions.
Key use cases enabled by this specification include XR services incorporating real-time and non-real-time media in industrial (e.g., for monitoring, maintenance, collaboration, and tele-operation), enterprise and educational environments; entertainment use-cases, including cloud-gaming, and shared and collaborative entertainment and productivity XR services. |
26.802 | Multicast Architecture Enhancement for 5G Media Streaming | TR | 19.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.802/26802-j20.zip | The present document identifies and evaluates potential enhancements to the 5G Media Streaming (5GMS) [1] in order to provide multicast-broadcast media streaming services. It has the following objectives:
- Define scenarios where multicast ingestion or multicast distribution might be used, including potential IGMP termination options [2], [3], and [4]. Examples for such collaboration scenarios are transparent multicast delivery, multicast linear IPTV delivery, hybrid unicast/multicast (e.g. MooD or service continuity), and multicast Adaptive Bit Rate (ABR) for Over the Top (OTT) live streaming.
- Identify the relevant key issues and gaps in 5GMS to support the above scenarios based on the existing 5GS multicast architecture.
- Document architecture extensions and procedures to support the above-defined scenarios.
- Identify protocols to support the above extensions and procedures in 5GMS.
- Identify Procedures for managing downlink multicast streaming and session lifecycle.
- Select a subset of relevant scenarios that should be supported in extensions to 5G Media Streaming.
A revision of the present document identifies and evaluates a set of potential improvements and extensions, referred to as Key Issues:
- In-session Unicast Repair for MBS Object Distribution.
- MBS User Service and Delivery Protocols for eMBMS.
- Selected MBMS Functionalities not supported in MBS.
For each of the above key topics, the following objectives are identified:
1. Document the key topics in more detail, in particular how they relate to the 3GPP Media Delivery architecture and/or the MBS User Service architecture.
2. Study collaboration scenarios between the Application Service Provider and the 5G System and for each of the key topics.
3. Based on existing architectures, develop one or more deployment architectures that address the key topics and the collaboration models.
4. Map the key topics to basic functions and develop high-level call flows.
5. Identify the issues that need to be solved.
6. Provide candidate solutions including call flows, protocols and APIs for each of the identified issues.
7. Coordinate work with other 3GPP groups e.g. SA2, SA3, SA5, SA6 and others as needed.
8. Coordinate work with external organizations such as DASH-IF, CTA WAVE, ISO/IEC JTC29 WG3 (MPEG Systems), 5G-MAG, DVB or IETF, as needed.
9. Identify gaps and recommend potential normative work for stage-2 and stage-3, including which existing specifications would be impacted and/or if any new specifications would preferably be developed. |
26.804 | Study on 5G media streaming extensions | TR | 19.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.804/26804-j10.zip | This Technical Report identifies and evaluates a set of potential improvements and extensions, referred to as key topics. The initial set of key topics were:
- Content Preparation
- Traffic Identification
- Use of HTTP/3 in the Media Delivery System
- Additional / New transport protocols
- Uplink media streaming
- Background traffic
- Content Aware Streaming
- Network Event usage
- Per-application-authorization
- Support for encrypted and high-value content
- Scalable distribution of unicast Live Services
- Network Slicing Extensions for 5G Media Streaming
- 3GPP Service Handler and URLs
- 5GMS Application Server configuration and management.
In an extension, a second set of key topics were collected as follows:
- Media Delivery Specification.
- Common Client Metadata.
- Common Server-and Network-Assisted Streaming.
- Multi-Access Media Delivery.
- Media Delivery from multiple service endpoints/location.
- Modem Usage Optimized Media Streaming.
- DASH/HLS Interoperability.
- Further harmonization of RTC and Streaming for Advanced Media Delivery.
- Improved QoS support for Media Streaming services.
- QUIC-based segmented media delivery.
- In-band signalling of QoS for 5G Media Streaming.
- Dynamic content generation from multiple sources.
For each of the above key topics, the following objectives are identified:
1. Document the above key topics in more detail, in particular how they relate to the 5GMS Architecture and protocols.
2. Study collaboration scenarios between the 5G System and Application Provider for each of the key topics.
3. Based on the 5GMS Architecture, develop one or more deployment architectures that address the key topics and the collaboration models.
4. Map the key topics to basic functions and develop high-level call flows.
5. Identify the issues that need to be solved.
6. Provide candidate solutions (including call flows) for each of the identified issues.
7. Coordinate work with other 3GPP groups e.g. SA2, SA3, SA5, and others as needed.
8. Coordinate work with external organizations such as SVTA (in particular DASH-IF WG), CTA WAVE, ISO/IEC JTC29 WG3 (MPEG Systems), or IETF, as needed.
9. Identify gaps and recommend potential normative work for stage-2 call flows and possibly stage-3. |
26.813 | Avatar Representation and Communication | TR | 19.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.813/26813-j10.zip | The present document documents formats for representing and animating Avatars. It also provides recommendations on the integration of Avatars in 3GPP services and enablers for immersive communications and the Metaverse. |
26.819 | Spatial Computing for AR Services | TR | 1.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.819/26819-100.zip | The present document … |
26.822 | Study on 5G Real-time Transport Protocol Configurations, Phase 2 | TR | 19.2.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.822/26822-j20.zip | The Technical Report focuses on optimizing the use of RTP for the transport of real-time XR media (including conversational media) and associated metadata. The use of the IMS Data Channel is supported by existing services such as MTSI but is outside the scope of this report. Aspects related to QUIC are outside the scope of this report. |
26.830 | Study on the enhancement for Immersive Real-Time communication for WebRTC; Phase 2 | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.830/26830-j00.zip | The present document identifies possible enhancements of specifications for WebRTC-based real time media communication, to better support of immersive Real-Time Communication (RTC) services. Especially, the following key topics are addressed.
- Media capabilities, profiles and codecs for RTC
- Signalling and metadata to support immersive media capabilities
- Support of tethered cases in RTC system |
26.841 | Study on Media Messaging | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.841/26841-j00.zip | The Technical Report discusses enhancements for Media Messaging as defined in TS 26.143 [26143].
TS 26.143 defines capabilities and profiles for messaging services. The profiles in TS 26.143 are aligned with TS 26.140. The container format is based on IETF RFC 2045 [RFC2045] as the format for the MMBPs. In addition, the profiles permits to encapsulate encapsulation of real-time video into the 3GP file format using the baseline profile. The container does not support external bodies, i.e. the MMBP is expected to be delivered as a single message. The media types for the player address basic text, audio/speech, images, video, text/subtitle, 3D scenes including AR as well as simple HTML-5 presentations. For the content generator, the supported media types in this profile are basic text, audio/speech, images, video, and text.
GSMA is currently working RCS and IETF MIMI will continue the work to develop More Instant Messaging Interoperability (MIMI). MPEG Systems has initiated a project referred to as "Messaging Media Application Format (MeMAF)." The considered scope of this project is the definition of a Media Application Format that primarily can be used for Messaging Services. To support basic interoperability, a baseline profile with minimum options would be defined. Beyond the baseline profile, additional profiles are expected to be defined that enable richer experiences. MeMAF is expected to be a profile of ISOBMFF and it would not directly define any new functions or boxes. MeMAF would support different entry points that enable composition and rendering of different messaging experiences.
Note that none of the efforts in GSMA or IETF MIMI address messaging multimedia formats for messaging services, but content interoperability is considered an important aspect. A collaboration between MPEG and 3GPP for this purpose, similar as it was done for DASH, may be beneficial.
Based on the content in TS 26.143 elaborated above, it is obvious that several aspects are not addressed in the Rel-18 version of TS 26.143, among others:
A) Integration of TS 26.143 Capabilities and Profiles into IETF MIMI: TS 26.143 only provides containers based on Multi-part MIME. MIMI defines a similar framework, but a mapping of the MMBP data model from TS 26.143 needs to be completed. For this the progress of IETF MIMI needs to be monitored, and integration of TS 26.143 profiles and capabilities need to be studied.
B) Support of advanced file format: TS 26.143 only provides 3GP Rel-9 baseline profile encapsulation. This format lacks support for advanced features, such as multi-track formats, proper definition metadata for different media types and so on. MeMAF as defined in MPEG is expected to provide latest file format functionalities to address all needs of a modern message service, in particular also to restrict the ISO Base Media File Format (ISO BMFF) for improved interoperability. A collaboration between MPEG and 3GPP for defining this advanced messaging format, similar as it was done for DASH, is expected to be beneficial.
C) Support of external body content and late binding: MIMI as an example requires clients to support the external body content that can be accessed with http and https URLs. The functionality is clearly of relevance. However, in context of 3GPP and MPEG, additional options exist, for example using media/external media type, using external data references in file formats, usage of HTML-5 presentations, glTF scenes or streaming manifests with inline references. A study of suitable support of different options is relevant.
D) DRM and encrypted content: While typical messaging services including IETF MIMI support end-to-end encryption of the messages, in some cases the content itself needs to be content protected, for example if high-value content is shared in messaging services, if copying of the content needs to be prevented and so on. In this case, the content may be encrypted, and the service needs to be integrated in a key management environment. Providing proper functionality for this purpose needs to be studied.
E) Additional media experiences: In 3GPP, advanced media experiences are added to different services, in particular immersive media, new image formats, interactive content, etc. The proper integration of new media experiences should be studied.
F) Additional industry requirements: Messaging services are gaining more and more popularity and interoperability requirements are for example developed by GSMA. These industry requirements may result in additional functionalities that need further study. Communication with the industry should continuously happen such that 3GPP can address those.
G) Media Service Enabler: In TR 26.857, Media Service Enablers had been introduced. Clearly, the MMBP Generator and MMBP Player in TS 26.143 are aligned with the Media Service Enabler concept, for example APIs to access player and generator may be further specified to support third party applications.
The present document is in the context of the above potential improvements and extensions, referred to as key topics. |
26.847 | Evaluation of Artificial Intelligence and Machine learning in 5G media services | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.847/26847-j00.zip | The present document provides details on feasibility evaluations for a given set of scenarios related to AI/ML in media services. In particular, aspects related the feasibility of split inferencing between different entities and the characteristics of the subsequent intermediate data are documented. A set of anchors and related metrics are defined to evaluate the feasibility and characteristics of such scenarios in terms of service requirements (such as service latency, inference accuracy, network bandwidth etc.). The transmission of relevant data in AI/ML media services is also considered, with evaluations on the compression technologies of data components such as AI/ML models. The functional aspects related to the AI/ML media services given in this document are presented in TR 26.927 [3]. |
26.854 | Study on Haptics in 5G Media Services | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.854/26854-j00.zip | The present technical report documents relevant use-cases, interoperability requirements, performance characteristics of haptics formats and codecs to enable haptics enhanced media streaming and communication services. This report documents the integration of haptics media in 3GPP media streaming and communication services to support the addition of a Haptics media type at the same level than audio and video in 3GPP media services.
- Clause 4 provides some background information on haptics systems as wells as a definition of haptics media and media pipeline.
- Clause 5 lists use cases illustrating the added value of haptics in 3GPP scenarios, identifies haptics characteristics and introduces interoperability considerations.
- Clause 6 presents the different types of haptics signals, the existing media formats and categorizes the different types of devices and their haptics specificities.
- Clause 7 documents the candidate technologies, in particular codecs, storage formats and transport protocols.
- Clause 8 focuses on the integration of haptics into 3GPP services and architectures including IMS, RTC, Messaging and XR device.
- Clause 9 summarizes the typical traffic characteristics of haptics media depending on the use cases and formats under consideration.
- Clause 10 addresses the QoS and QoE aspects.
- Clause 11 summarizes the identified characteristics, gaps and potential requirements
- Finally, clause 12 provides a conclusion and addresses the potential next steps. |
26.855 | Study on Film Grain Synthesis | TS | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.855/26855-j00.zip | The present document attempts to evaluate the performance and to justify any potential benefits of film grain synthesis technologies for video compression, a qualitative and quantitative analysis on what would be the costs and benefits of using such technologies would be needed.
Clause 4 documents new content that could be used for the purpose of evaluating film grain synthesis technologies and provides some information on the content characteristics. Clause 5 describes a film grain synthesis tool named as the "FGC SEI message designer", which focuses on one particular film grain synthesis technology, i.e. the film grain characteristics (FGC) SEI message and the underlying film grain synthesis technologies it supports and permits the design and visualization of film grain synthesis parameters in the context of that technology. Clause 6 provides some suggestions on how to achieve interoperability using the FGC SEI message while Clause 7 proposes new scenarios that could be added in 3GPP TR 26.955 [2] for the evaluation of film grain synthesis technologies and provides some preliminary results not validated yet. Finally, Clause 8 introduces some initial considerations on UE requirements. |
26.858 | Study on APIs for 3GPP Speech and Audio Codecs | TR | 0.5.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.858/26858-050.zip | This clause shall start on a new page.
The present document … |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.