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.284 | Local Call Local Switch (LCLS); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.284/23284-i00.zip | The present document defines the Stage 2 description for the Local Call Local Switch feature. Local Call Local Switch may be implemented in both BICC based CS core networks as defined in 3GPP TS 23.205 [2] and SIP-I based CS core networks as defined in 3GPP TS 23.231 [3], with a GSM/EDGE Radio Access Network supporting either TDM based or IP based A interface.
This stage 2 shall cover the information flows between the GMSC server, MSC server and media gateways that are required to support Local Call Local Switching highlighting the specific requirements in addition to those defined for BICC based CS core networks 3GPP TS 23.205 [2] and SIP-I based CS core networks 3GPP TS 23.231 [3]. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW. The present document shall show the CS core network termination of the A interface, and the information flows between the BSS and the MSC server, in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities.
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. |
23.285 | Architecture enhancements for V2X services | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.285/23285-i00.zip | The present document specifies architecture enhancements to facilitate vehicular communications for Vehicle-to-Everything (V2X) services, which includes Vehicle-to-Vehicle (V2V), Vehicle-to-Pedestrian (V2P), Vehicle-to-Infrastructure (V2I), and Vehicle-to-Network (V2N), according to the use cases and service requirements defined in TS 22.185 [2] and TS 22.186 [28].
The following vehicular communications for V2X services are specified:
- V2X communication over PC5 reference point.
- V2X communication over LTE-Uu reference point.
V2X communication over NR PC5 reference point specified in TS 23.287 [30] is supported. |
23.286 | Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows | TS | 18.6.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.286/23286-i60.zip | The present document specifies the functional architecture, procedures and information flows for V2X application enabler layer. This specification includes the capabilities of the application layer support for V2X services that are necessary to ensure efficient use and deployment of V2X services over 3GPP systems. The VAE capabilities applies to EPS and 5GS. |
23.287 | Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services | TS | 18.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.287/23287-i40.zip | The present document specifies architecture enhancements to the 5G System to facilitate vehicular communications for Vehicle-to-Everything (V2X) services, over the following reference points, based on service requirements defined in TS 22.185 [2] and TS 22.186 [3]:
- PC5 reference point: NR PC5 RAT, LTE PC5 RAT.
- Uu reference point: NR, E-UTRA.
This specification also covers interworking with EPS. |
23.288 | Architecture enhancements for 5G System (5GS) to support network data analytics services | TS | 18.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.288/23288-ia0.zip | |
23.289 | Mission Critical services over 5G System; Stage 2 | TS | 18.10.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.289/23289-ia0.zip | |
23.292 | IP Multimedia Subsystem (IMS) centralized services; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.292/23292-i00.zip | This document specifies the architectural requirements for delivery of consistent services to the user regardless of the attached access type (e.g. CS domain access, or IP-CAN). This is achieved by implementing the services in the IP Multimedia Subsystem (IMS).
Consideration is given to how to access specified IMS-based services (see clause 22.4 of TS 22.101 [9]) whilst still allowing other, bespoke services to be offered by the home operator.
IMS control of services related to those defined in clause 22.4 of TS 22.101 [9] are part of the present scope of this specification.
The scope of the specification includes:
- Session establishment when using CS access for media transmission for an IMS service.
- Support of Service Continuity as specified in TS 23.237 [12].
- Support of Single Radio Voice Call Continuity as specified in TS 23.216 [36].
- Access Domain Selection (ADS).
- IMS control of services where the media is transported via the CS network (e.g. managing of mid-call services).
- Service data management.
The solution is applicable for UEs with or without ICS functionality, and is applicable for the following deployment scenarios:
- An operator who supports for their subscribers only UEs that have ICS functionality.
- An operator who supports for their subscribers only UEs that do not have ICS functionality.
- An operator who supports for their subscribers UEs which do and do not have ICS functionality (to different subscribers and the same subscribers) ensuring the coexistence of UEs that have and do not have ICS functionality.
- Inbound roaming subscribers on an operator's network that supports either the same or different ICS functionality that the inbound roaming subscriber is using, ensuring the coexistence of UEs that have and do not have ICS functionality. |
23.303 | Proximity-based services (ProSe); Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.303/23303-i00.zip | The present document specifies the Stage 2 of the Proximity Services (ProSe) features in EPS. ProSe features consist of: ProSe discovery (direct or EPC-level) and ProSe Direct Communication.
ProSe discovery identifies that ProSe-enabled UEs are in proximity, using E-UTRAN (with or without E-UTRAN), WLAN technology or EPC. The details of WLAN-based ProSe Direct Discovery are described in clause 5.3.1.3 and Annex C.
ProSe Direct Communication enables establishment of communication paths between two or more ProSe-enabled UEs that are in direct communication range. The ProSe Direct Communication path could use E-UTRAN or WLAN.
For Public Safety specific usage:
- ProSe-enabled Public Safety UEs can establish the communication path directly between two or more ProSe-enabled Public Safety UEs, regardless of whether the ProSe-enabled Public Safety UE is served by E-UTRAN.
- ProSe Direct Communication is also facilitated by the use of a ProSe UE-to-Network Relay, which acts as a relay between E-UTRAN and UEs.
Security aspects of ProSe are defined in TS 33.303 [29]. |
23.304 | Proximity based Services (ProSe) in the 5G System (5GS) | TS | 18.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.304/23304-i80.zip | |
23.316 | Wireless and wireline convergence access support for the 5G System (5GS) | TS | 18.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.316/23316-i70.zip | |
23.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.333/23333-i10.zip | This specification describes the functional requirements and information flows that generate procedures between the Multimedia Resource Function Controller (MRFC) and the Multimedia Resource Function Processor (MRFP), the Mp Interface.
This specification is limited to information flows relevant to the Mp Interface; in order to define these procedures and make the functional requirements clear some triggers from an external interface may be described; these may be specified within the Mr interface for example or within an AS in which the MRFC function resides. However for the overall stage 2 procedures of IMS see 3GPP TS 23.228 [1].
The protocol on the Mp interface is defined to comply with ITU-T H.248.1 Gateway Control Protocol; see [3].The goal of this specification is to provide the input to defining a formal Profile within the H.248 protocol toolbox specifically for the Mp application. |
23.334 | IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.334/23334-i10.zip | Annex G of 3GPP TS 23.228 [2] gives out an IMS Application Level Gateway (IMS-ALG) and IMS Access Media Gateway (IMS-AGW) based reference model to support NAPT-PT, gate control and traffic policing between IP-CAN and IMS domain.
Figure 1.1: Scope of the specification
Figure 1.1 illustrates the reference model for Iq:
- the dashed line represents the IP signalling-path with SIP (at Gm) as call/session control protocol between the UE and the P-CSCF (IMS-ALG);
- the bold, horizontal line represents the IP media-path (also known as (IP) bearer-path or (IP) data-path; the notion 'media' is used as generic term for "IP application data"); and
- the vertical line represents the Iq control-path with H.248 as gateway/policy control protocol between the IMS-ALG and the IMS-AGW (H.248 messages are transported over IP).
The Iq reference point is between the P-CSCF (IMS-ALG) and the IMS-AGW. It conveys the necessary information that is needed to allocate, modify and release (IP) transport addresses.
The present document defines the stage 2 description for the Iq reference point. The stage 2 shall cover the information flow between the P-CSCF (IMS-ALG) and IMS-AGW. The protocol used over the Iq interface is the gateway control protocol according ITU-T Recommendation H.248 (which is specified for Iq by an H.248 profile according 3GPP TS 29.334 [3]). |
23.335 | User Data Convergence (UDC); Technical realization and information flows; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.335/23335-i00.zip | The present document describes the procedures and signalling flows associated to the technical realization of the 3GPP User Data Convergence (UDC). It furthermore indicates some requirements for the stage 3 specifications.
Special consideration is put in the following areas:
- reference architecture for the UDC concept
- general description of procedures for the user data manipulation (e.g. create, delete, update, etc.)
- identification of the requirements on the UDC for the applicability of the mechanisms described in this document.
User data convergence is an optional concept to ensure data consistency and simplify creation of new services by providing easy access to the user data, as well as to ensure the consistency of storage and data models and to have minimum impact on traffic mechanisms, reference points and protocols of network elements.
Standization of the Data Model for the Ud interface between Front-Ends and the UDR is out of the scope of 3GPP. |
23.379 | Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2 | TS | 18.13.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.379/23379-id0.zip | |
23.380 | IMS Restoration Procedures | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.380/23380-i10.zip | |
23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | TS | 18.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-i80.zip | |
23.402 | Architecture enhancements for non-3GPP accesses | TS | 18.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.402/23402-i30.zip | This document specifies the stage 2 service description for providing IP connectivity using non-3GPP accesses to the Evolved 3GPP Packet Switched domain. In addition, for E-UTRAN and non-3GPP accesses, the specification describes the Evolved 3GPP PS Domain where the protocols between its Core Network elements are IETF-based.
ITU-T Recommendation I.130 [2] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [3] defines stage 2 of the method.
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between 3GPP and non 3GPP accesses, policy control and charging, and authentication, related to the usage of non-3GPP accesses.
TS 23.401 [4] covers architecture aspects common to the Evolved 3GPP Packet Switched domain.
The procedures defined in the present document for WLAN access selection and PLMN selection replace the corresponding I-WLAN procedures specified in TS 23.234 [5].
Interworking with 5GS is only supported for untrusted non-3GPP access using GTP-based S2b. Enhancements to support interworking with 5GS are captured in TS 23.501 [87] and TS 23.502 [88].
The WLAN Selection Policy specified in clause 4.8.2.1.6 also covers UEs operating in SNPN access mode as defined in TS 23.501 [87]. |
23.433 | Service Enabler Architecture Layer for Verticals (SEAL); Data Delivery enabler for vertical applications | TS | 18.7.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.433/23433-i70.zip | |
23.434 | Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows | TS | 18.12.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.434/23434-ic0.zip | |
23.435 | Procedures for Network Slice Capability Exposure for Application Layer Enablement Service | TS | 18.4.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.435/23435-i40.zip | |
23.436 | Functional architecture and information flows for Application Data Analytics Enablement Service | TS | 18.6.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.436/23436-i60.zip | |
23.468 | Group Communication System Enablers for LTE (GCSE_LTE); Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.468/23468-i00.zip | The present document provides the stage 2 description for the 3GPP system provided enablers to support group communication services using EUTRAN access. The corresponding stage 1 requirements are defined in TS 22.468 [2].
The group communication system is represented by an Application Server (GCS AS) using the 3GPP system provided enablers for transferring its application signalling and for delivering application data, e.g. media data, to a group of UEs either (i) over MBMS Bearer Services using the Broadcast Mode of MBMS (TS 23.246 [3]); or (ii) over EPS Bearers; or (iii) over both MBMS and EPS bearer services.
The specification covers both roaming and non-roaming scenarios and also includes support for service continuity, i.e. support for continuous reception of application data when a UE changes between reception of application data via EPS and MBMS Bearer Services.
Application level interactions between the UE and the GCS Application Server are out of scope of this specification. |
23.479 | Technical Specification Group Services and System Aspects; UE MBMS APIs for Mission Critical Services; | TS | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.479/23479-i00.zip | The present document defines the application programming interface on the UE for mission critical applications to access mission critical services over MBMS.
This document identifies system architecture and functional model for the definition of the MBMS API for mission critical services. |
23.501 | System architecture for the 5G System (5GS) | TS | 18.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.501/23501-ia0.zip | |
23.502 | Procedures for the 5G System (5GS) | TS | 18.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.502/23502-ia0.zip | |
23.503 | Policy and charging control framework for the 5G System (5GS); Stage 2 | TS | 18.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.503/23503-ia0.zip | |
23.527 | 5G System; Restoration procedures | TS | 18.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.527/23527-i50.zip | |
23.540 | 5G System: Technical realization of Service Based Short Message Service; Stage 2 | TS | 18.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.540/23540-i40.zip | |
23.542 | Application layer support for Personal IoT Network | TS | 18.6.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.542/23542-i60.zip | |
23.545 | Application layer support for Factories of the Future (FF) | TS | 1.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.545/23545-100.zip | |
23.548 | 5G System Enhancements for Edge Computing; Stage 2 | TS | 18.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.548/23548-ia0.zip | |
23.554 | Application architecture for MSGin5G Service; Stage 2 | TS | 18.9.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.554/23554-i90.zip | |
23.558 | Architecture for enabling Edge Applications | TS | 18.11.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.558/23558-ib0.zip | |
23.586 | Architectural Enhancements to support Ranging based services and Sidelink Positioning | TS | 18.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.586/23586-i70.zip | The present document specifies the stage 2 of the Ranging based services and Sidelink positioning in 5G System for commercial, V2X and public safety use cases in in-coverage, partial coverage, and out-of-coverage of 5G network using 5G NR PC5 RAT.
Radio aspects of Ranging based services and Sidelink positioning in 5GS are defined in TS 38.355 [12] and TS 38.305 [5].
Security aspects of Ranging based services and Sidelink positioning in 5GS are defined in TS 33.533 [13]. |
23.632 | User data interworking, coexistence and migration; Stage 2 | TS | 18.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.632/23632-i60.zip | |
23.682 | Architecture enhancements to facilitate communications with packet data networks and applications | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.682/23682-i00.zip | |
23.700-05 | Study on architecture enhancements for vehicle-mounted relays | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-05/23700-05-i00.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 base station relays mounted on vehicles, using NR for wireless access toward the UE and for wireless access through an IAB-donor toward the 5GC, i.e. in this release only IAB type relays based on the IAB architecture and functionalities specified in TS 23.501 [2] are studied. The study addresses the service requirements documented in TS 22.261 [3] for the mobile base station relays, and focuses on the following aspects:
- efficient mobility and service continuity for UE or a group of UEs to efficiently deliver data during different mobility scenarios (including mobility of the mobile base station relays);
- provisioning, policies and mechanisms to e.g. manage relay configuration, geographic restrictions, QoS, authorization and control of UEs' access via the mobile base station relay, etc.;
- support for roaming of mobile base station relay (including the roaming of the IAB-UE and gNB-DU in IAB-node), support for regulatory requirements (e.g. emergency, priority services, public safety), and support for location services for UEs accessing a mobile base station relay. |
23.700-08 | Study on enhanced support of Non-Public Networks; Phase 2 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-08/23700-08-i00.zip | The scope of this Technical Report is to study further enhancements of the 5GS to support Non-Public Networks including the following aspects:
1. Support for enhanced mobility by enabling support for idle and connected mode mobility between SNPNs without new network selection.
2. Support for non-3GPP access for SNPN.
3. Address SA WG1 requirements in TS 22.261 [2] related to support for Providing Access to Localized Services.
NOTE: The TS 22.261 [2] requirements for Providing Access to Local Services related to Multicast/Broadcast are not part of the scope. |
23.700-17 | Study on Wireless and Wireline Convergence for the 5G System (5GS) (5WWC); Phase 2 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-17/23700-17-i00.zip | The Technical Report studies and performs evaluations of potential architecture enhancements to enhance the support of Wireline-Wireless convergence in the 5G Core network (5GC). Specifically, two objectives are included:
- Work task #2: Whether and how to improve the support of devices connecting behind 5G-RG including:
Providing differentiated service (e.g. QoS and charging) for UE and Non-3GPP devices connected behind a 5G RG. This may imply s studying ways for 5GC to identify Non-3GPP devices connected behind a 5G RG and/or their traffic. Conclusions may differ for UE and for Non-3GPP devices.
- Work task #3: Trusted/untrusted Non-3GPP access network: How to select a TNGF/N3IWF that supports the S-NSSAI(s) needed by the UE. |
23.700-18 | Study on system enabler for service function chaining | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-18/23700-18-i00.zip | The Technical Report studies and performs evaluations of potential architecture enhancements to enhance the support of service function chaining in the 5G Core network (5GC). Specifically, two objectives are included:
WT#2: Investigate whether traffic steering policy is sufficient to support SA WG1 requirements in TS 22.101 [5], TS 22.261 [6] and TS 22.115 [7], study whether and how to define Service Function Chaining (SFC) policies, and investigate solutions and procedures for the 5G network with SFC capabilities to identify/detect/classify user plane traffic and steer the traffic to a chain of ordered service functions for SFC processing in non-roaming and home routed roaming scenarios.
WT#3: Depending on the outcome of WT#2, specify possible enhancement to northbound APIs for allowing an AF to request network capability exposure functionalities, e.g. request a service function chain for a certain traffic flow, etc. based on service level agreement with the third party.
NOTE 1: This study considers only traffic handled over N6 by PSA UPF(s) in 5G network.
NOTE 2: The definition of terms in RFC 7665 [8] may be re-used when applicable. The study targets the use of traffic steering concept, e.g. defined by 3GPP (FMSS) and SFC mechanisms defined in IETF when applicable. Especially the study aims at reusing user plane mechanisms (e.g. VXLAN, NSH, GENEVE, GRE, VLAN, etc.) defined at IETF to support SFC, as applicable.
NOTE 3: The study for SFC will ensure that existing (per 3GPP Rel-17) deployments flexibility can be preserved in deployments of SFC in 5G network.
NOTE 4: The study assumes a Home Routed roaming PDU Session does not have an offloading point in a VPLMN. |
23.700-25 | Study on timing resiliency and TSC and URLLC enhancements | TR | 18.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-25/23700-25-i10.zip | The objective of this Technical Report is to study and perform an evaluation of potential architecture enhancements for supporting 5G Timing Resiliency and TSC & URLLC enhancements for 5G System (5GS). The following aspects are covered:
- Study how to report 5GS network timing synchronization status (such as divergence from UTC and 5GS network timing source degradation) to UEs and 3rd party applications (AFs):
- Study how RAN and 5GC learn about network 5GS network timing synchronization status to be able to inform UEs and AFs.
- Study if additional information needs to be provided to UEs and AFs to inform about 5GS network timing synchronization status.
- Study how to enable AFs to request time synchronization service in a specific coverage area and how to enforce the coverage area.
- Study how to control 5G time synchronization service based on subscription (i.e. introducing subscription parameter for time synchronization and enforcing it).
- Study how to enable an AF to explicitly provide PER to NEF/PCF.
- Study mechanisms for interworking with TSN transport networks. Study interworking mechanisms with TSN networks deployed in the transport network in order to support of E2E determinism and low latency communication and efficient N3 transmission.
- Study if there is a need for applications to adapt downstream scheduling in order for 5GS to meet really low latency (e.g. 2 msecs) requirement and if there is a need to have feedback from RAN (e.g. for application to consider DL packet transmission time slots to avoid buffering in the RAN) for this purpose. |
23.700-27 | Study on 5G System with Satellite Backhaul | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-27/23700-27-i00.zip | The scope of this Technical Report is to study the following aspects of 5GS with satellite backhaul:
1: Architecture enhancements for support of a backhaul with changing delay (e.g. brought by ISL in satellite networks or changed satellite backhaul on the UP path), and possibly limited bandwidth in case of a gNB with satellite backhaul only (e.g. restricted by the maximum data rate of a satellite beam):
- Policy/QoS control enhancements based on the detected packet delivery latency and/or bandwidth of the satellite backhaul on the UP path;
- Exposure of backhaul information to AFs.
2: Architecture enhancements for support of UPF deployed on GEO satellite with gNB on the ground:
- Whether and how to enable satellite edge computing services via UPF on-board e.g. to reduce the latency for data transmission, and minimize the backhaul resources consumption.
- How to enhance local switch for UEs in a communication when they are served by UPF on-board, e.g. to reduce end to end delay comparing with existing 5G LAN local switch at PSA on the ground. |
23.700-28 | Study on Integration of satellite components in the 5G architecture; Phase 2 | TR | 18.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-28/23700-28-i10.zip | The scope of the TR is to investigate further 5GC/EPC enhancements to support satellite access using the work done in Release 17 as baseline with the following 5GC/EPC areas for study:
- Possible enhancements to support of Discontinuous coverage with the following areas of focus:
- Architectural enhancements to support discontinuous coverage for mobility enhancement (e.g. paging enhancement).
- Architectural enhancements considering prediction, awareness and notification of UE wake-up time, power saving optimizations. |
23.700-33 | Study on System enhancement for Proximity based Services (ProSe) in the 5G System (5GS); Phase 2 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-33/23700-33-i00.zip | The scope of this Technical Report is to study and evaluate the possible architecture enhancements to the 5G Proximity-based Services (5G ProSe) system defined in TS 23.304 [3], based on the relevant Stage 1 requirements defined in TS 22.261 [4], TS 22.278 [5] and TS 22.115 [6] and determine which of the solutions can proceed to normative specifications.
This study will consider architecture enhancements in the following areas:
- Support of single NR PC5 hop UE-to-UE Relay for unicast.
- Enhancement of 5G ProSe UE-to-Network Relay functionality.
- Support of path switching between direct NR Uu communication path and direct NR PC5 communication path (i.e. non-relay case). |
23.700-34 | Study on SEAL data delivery enabler for vertical applications | TR | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-34/23700-34-i10.zip | The present document is a technical report which identifies the application enabling layer platform architecture, capabilities and services to efficiently support distribution, storage and delivery for the application content/data for vertical applications.
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to data delivery and 3GPP system user plane aspects specified in 3GPP TS 22.261 [2], 3GPP TS 23.501 [6] and 3GPP TS 23.247 [4].
This document will provide recommendations for normative work. |
23.700-36 | Study on Application Data Analytics Enablement Service | TR | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-36/23700-36-i10.zip | The present document is a technical report which identifies the application enabling layer platform architecture, capabilities, and services to support data analytics enablement at the application layer.
The aspects of the study include the investigation of application data analytics services to optimize the application service operation, edge/cloud analytics enablement, data collection aspects per identified application data analytics service, coordination of data collection from multiple sources and unified exposure of data analytics to the vertical/ASP. This study will also identify potential enhancements to existing enablement layer entities (SEAL, eEDGEAPP, vertical specific enablers) to consume application data analytics enablement services.
The study takes into consideration the work done for data analytics in 3GPP TS 23.288 [2] and 3GPP TS 28.104 [3] and other related work outside 3GPP. |
23.700-38 | Study on sharing of administrative configuration between interconnected MC service systems | TR | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-38/23700-38-i00.zip | The present document studies sharing of administrative configuration between interconnected MC service systems, based on stage 1 requirements specified in 3GPP TS 22.280 [2].
This study investigates related use cases and identifies solutions to support exchange administrative configuration, security relevant data and information between interconnected MC service systems. |
23.700-41 | Study on enhancement of network slicing; Phase 3 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-41/23700-41-i00.zip | The Technical Report studies the gaps and performs evaluations of potential architecture enhancements to support Network Slicing with the following objectives:
1. Study whether and how to address the following scenario in order to provide service continuity: if an existing network slice or network slice instance cannot serve the PDU session, or if the existing network slice instance cannot meet the performance requirements of the applications. The study should investigate whether deployment optimization is sufficient. Minimized system optimisations can be considered if valuable.
2. Study whether and how to initiate a registration for a rejected S-NSSAI that was rejected in a first TA of the RA but may be available in another TA of the RA.
3. Study whether and how to support the following stage one Rel-18 EASNS requirements related to roaming specified in TS 22.261 clause 6.1.2.1, i.e. Requirement on enhancement the information available to the UE in roaming scenarios regarding the availability of network slices in VPLMNs available in the roaming country, in order to allow the UE to select and obtain services from the VPLMN supporting the network slices which UE may wish to use.
4. Study whether and how to enhance the system to ensure network controlled behaviour of network slice usage including UE registration and PDU Session establishment (e.g. so that when performing NSAC the network slice can serve UEs/PDU Sessions with actual activity).
5 Study deployment considerations when a service provided has an area of service that does not overlap with the already deployed Tracking Areas and/or have a limited lifetime and how existing mechanisms including network slicing can help support such scenarios. If existing mechanisms are concluded to be not sufficient to achieve the scenarios, study whether and how additional mechanisms can resolve the analysed gap.
6. Study whether and how to enhance the support of NSAC when more than one NSACF is involved in enforcing a shared maximum allowed number of the UEs or PDU Sessions for a network slice in one PLMN or in roaming, in order to avoid fragmentation of the shared maximum allowed number. This item depends on the outcome of corresponding Rel-17 CRs. |
23.700-46 | Study on 5GS Deterministic Networking (DetNet) interworking | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-46/23700-46-i00.zip | The objective of this Technical Report is to study whether and how to enable 3GPP support for DetNet such that a mapping is provided between the central DetNet controller entity (as defined in IETF) and the 5G system. Mapping involves translation of DetNet traffic profile and flow specification to 5GS QoS parameters and TSCAI. The study also considers which information needs to be exposed from the 5G system to the DetNet controller.
The study scope assumes the following:
- Only IP based DetNet is in the scope of the work; MPLS based DetNet is out of scope.
- DetNet over Ethernet TSN is not in the scope of the work as it can be supported based on existing 3GPP and IETF standards.
- It is out of scope to support for edge DetNet node functions in the 3GPP network. |
23.700-47 | Study on architectural enhancements for 5G multicast-broadcast services; Phase 2 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-47/23700-47-i00.zip | This Technical Report studies and evaluates further enhancements to the 5G Multicast/Broadcast Architecture in order to provide the following features.
- Enabling UE's receiving Multicast MBS Session data in RRC Inactive state.
- Study feasible and efficient resource utilization for the same broadcast content to be provided to 5G MOCN network sharing scenarios (i.e. multiple CNs are connected to the same NG-RAN).
- Study whether and how to support on demand multicast MBS session triggered by AF, and efficient resource utilization via 5GC choosing multicast and/or unicast delivery for a certain service.
- Study whether and how to support group message delivery for capability-limited devices, including NEF enhancement, coexistence of existing power saving mechanisms and MBS.
- Study whether there are any identified performance issues for high number of public safety UEs, and if yes study necessary enhancements to 5MBS for that scenario. |
23.700-48 | 5G System Enhancements for Edge Computing; Phase 2 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-48/23700-48-i00.zip | The present document describes key issues and solutions for the phase 2 of the system enhancements for Edge Computing in 5GS.
Edge Computing is supported in 5GS since Rel-15. During Rel-17 FS_enh_EC study described in TR 23.748 [4] , further enhancements for supporting Edge Computing have been studied, including discovery and re-discovery of EAS, edge relocation etc. 4 key issues from FS_enh_EC study have been concluded and progressed in TS 23.548 [3]. Some other issues were raised during the Rel-17 study but not studied due to the time limitation in Rel-17.
This technical report will document the study of potential system enhancements for enhanced edge computing support, including:
- improvements to roaming, to support access to EHE in a VPLMN (WT#1);
- defining use cases that may benefit from exposure of additional data via the Local UPF/NEF including describing (on a high level) the characteristics of the data and data delivery to fulfil the use cases; investigating the solutions and their feasibility and suitability for improved network exposure of UE traffic related information to common Edge Application Server via Local UPF/NEF, such as network congestion status (WT#3);
NOTE 1: XR/media and AI/ML services specific QoS information exposure are to be studied in corresponding study items with considering the same exposure framework as defined by this study.
NOTE 2: This objective will look at the use cases and the data to be exposed but not at the actual UPF exposure mechanism or UPF-originated data, if/when already covered by FS_UPEAS.
- investigating the potential need and solutions for supporting offload policies to match more granular sets of UE(s) without exposing operator-internal configurations to 3rd party AFs (WT#5);
- investigating the potential need and solutions to influence of PSA-UPF and EAS (re)location for collection of UEs, e.g. in scenarios when UE(s) should use the same EAS and are not members of a pre-defined group (WT#6);
- investigating potential impacts related to the GSMA Operator Platform Group work, and potential improvements related with 5GC and EHE being operated by different organizations (WT#7);
- investigating the potential need and solutions to avoid the UE to switch the EC traffic away from the EC PDU Session and 5GS altogether, due to conflicting connectivity preferences in the device (e.g. via means outside of 3GPP connectivity, e.g. non-integrated Wifi) (WT#8);
- investigating the potential solutions for the AF to be able to obtain/determine the DNAI that is associated to a certain selected EAS, for subsequent use with already defined services provided to the AF (WT#9). |
23.700-53 | Study on access traffic steering, switching and splitting support in the 5G system architecture; Phase 3 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-53/23700-53-i00.zip | The purpose of this Technical Report is to enhance the ATSSS feature by investigating solutions that can support the following capabilities:
1) Support new steering functionalities that can steer/switch/split non-TCP traffic flows (e.g. UDP traffic flows and IP traffic flows). Two types of such steering functionalities are studied: (i) a steering functionality based on the QUIC protocol and its multipath extensions, and (ii) a steering functionality based on the DCCP protocol and its multipath extensions.
2) Support redundant traffic steering for both GBR and non-GBR traffic flows. With redundant traffic steering, a traffic flow (GBR or non-GBR) can be replicated on multiple access paths and, therefore, can improve transmission reliability and reduce packet latency.
3) Support traffic switching between one non-3GPP access path, from a UE to a N3IWF in a PLMN, and another non-3GPP access path, from the UE to a TNGF in the same PLMN.
4) Support the establishment of a MA PDU Session with one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC. This is to complement the existing ATSSS capability that supports the establishment of a MA PDU Session with one non-3GPP access path via 5GC and one 3GPP access path via EPC.
For each of the above capabilities, the conclusions of the study identify whether a solution is required for the normative phase and, if required, which solution to consider in the normative phase. |
23.700-55 | Study on enhanced Application Architecture for UAS applications | TR | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-55/23700-55-i00.zip | The present document analyze requirements and identify key issues and develop potential enhancements to the UAS application architecture. The study includes identification of potential enhancements to the UAS architecture, potential enhancements to the Service Enabler Architecture Layer (SEAL) and corresponding application requirements.
The study bases its work on the existing stage 1 work within 3GPP related to UAS as specified in 3GPP TS 22.125 [2].
The conclusions of the study will be aligned with 3GPP TR 23.700-58 [6]. The recommendations from the study include solutions for the UAS architecture and SEAL that will be considered for normative work. |
23.700-58 | Study of further architecture enhancements for uncrewed aerial systems and urban air mobility | TR | 18.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-58/23700-58-i10.zip | This study item shall address the following system enablers for 5GS and EPS to support additional scenarios and requirements for UAV (Uncrewed Aerial Vehicles) and UAM (Urban Air Mobility) by identifying how and whether existing mechanisms can be re-used, and identifying architectural and functional modifications required:
- a mechanism to transport Broadcast Remote Identification and C2 communications via the 3GPP system;
- a mechanism to support aviation applications such as Detect And Avoid (DAA). |
23.700-60 | Study on XR (Extended Reality) and media services | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-60/23700-60-i00.zip | The Technical Report studies key issues, solutions and conclusions on the support of advanced media services, e.g. High Data Rate Low Latency (HDRLL) services, AR/VR/XR services, and tactile/multi-modality communication services. The objectives include:
Enhancements for supporting multi-modality service:
- Study whether and how to enable delivery of related tactile and multi-modal data (e.g. audio, video and haptic data related to a specific time) with an application to the user at a similar time, focusing on the need for policy control enhancements (e.g. QoS policy coordination).
Enhancements of network exposure to support interaction between 5GS and application:
- Study whether and how interaction between AF and 5GS is needed for application synchronization and QoS policy coordination among multiple UEs or between multiple QoS flows per UE.
- Study exposure of 5GS QoS information (e.g. QoS capabilities) and network conditions to the Application to enable quick codec/rate adaptation help to provide desired QoE (e.g. such as assist in alleviating 5GS congestion).
Study whether and how the following QoS and policy enhancements for XR service and media service transmission are performed:
- Study the traffic characteristics of media service enabling improved network resources usage and QoE.
- Enhance QoS framework to support PDU Set granularity (e.g. video/audio frame/tile, Application Data Unit, control information), where a PDU Set consists of PDUs that have the same QoS requirements.
- Support differentiated QoS handling considering different importance of PDU Sets. e.g. eligible drop packets belong to a less important PDU Set to reduce the resource wasting.
- Whether and how to support uplink-downlink transmission coordination to meet RTT (Round-Trip Time) latency requirements between UE and N6 termination point at the UPF.
- Potential policy enhancements to minimize the jitter, focusing on i.e. requirement provisioning from AF, extension of PCC rule.
Study potential enhancements of power management considering traffic pattern of media services:
- Power saving enhancement e.g. support trade-off of throughput/latency/reliability considering device battery life, whether and how to enhance CDRX, considering XR/media traffic pattern.
NOTE: Whether to define a network slice type supporting media services can be determined during normative phase. |
23.700-61 | Study on Seamless UE context recovery | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-61/23700-61-i00.zip | This study will focus on the mechanism to determine the "unavailability period" in the 5G system for the UE. |
23.700-62 | Study on UPF enhancement for Exposure And SBA | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-62/23700-62-i00.zip | The Technical Report studies on key issue description, solution and conclusion on the support of better integration of UPF into the 5GC SBA. The objectives include:
- Study UPF event exposure service(s) registration/deregistration, and discovery via the NRF.
- Study UPF event exposure service(s) that would support, e.g.:
- Consumption of UPF exposure services by the PCF, NWDAF, CHF, NEF, Trusted AF and other NFs (if needed).
- (To support the UPF exposure service, if needed) Use of SMF services, PCF services, NWDAF services, CHF services, NEF services, Trusted AF services by the UPF.
NOTE 1: This will not define solutions where UPF exposes information that it is not originator of, i.e. not re-expose information owned and exposed by other NFs.
- Relevant Event IDs.
- Evaluate usage of UPF event exposure service(s) as defined in WT#2 also considering the architectural impacts.
NOTE 2: SMF is responsible for controlling UPF packet processing.
NOTE 3: The performance of UP traffic handling shall not be degraded due to mechanisms defined in this study.
NOTE 4: The study shall address generic UPF data exposure mechanisms via SBA based mechanisms, and the coordination with other SIDs for this aspect may be needed in study phase.
This study shall maintain the Rel‑17 backward compatibility on the N3, N6, N9, N4 interfaces. |
23.700-64 | Study on enhancements to application layer support for V2X services; Phase 2 | TR | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-64/23700-64-i10.zip | The present document is a technical report which identifies the enhancements to the application architecture to support V2X services specified in 3GPP TS 23.286 [6] considering advanced V2X services like V2P, ToD, etc and edge computing deployments for V2X services.
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to advanced V2X services and edge computing in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3], 3GPP TS 23.285 [5], 3GPP TS 23.287 [7], 3GPP TS 23.548 [10] and 3GPP TS 23.558 [11].
The study also takes into consideration the V2X application specific services and recommendations specified by automotive industry bodies (5GAA, ETSI ITS and AECC) related to advanced V2X services for VRU, Haptics/ToD and edge deployments for V2X services.
This document will provide recommendations for normative work. |
23.700-68 | Study on Support of reduced capability NR devices; Phase 2 | TR | 18.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-68/23700-68-i10.zip | The scope of the present document is to investigate solutions to support of RRC INACTIVE state with extended DRX cycle longer than 10.24s to enrich the power saving function as studied in TR 38.875 [5].
This study will address the following objective:
Support for enabling of eDRX cycle that is longer than 10.24s in RRC_INACTIVE state with following two aspects:
1) Study the support of the eDRX cycle that is longer than 10.24s and up to 10485.76s for RRC_INACTIVE state for RAN paging (e.g. PTW and eDRX cycle values).
2) Study the MT signalling and data handling for UE with long eDRX cycle in RRC_INACTIVE state. |
23.700-71 | Study on enhancement to the 5GC LoCation Services (LCS); Phase 3 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-71/23700-71-i00.zip | The scope of this Technical Report is to study further enhancements to the to the 5GC LoCation Services including the following aspects:
- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. support Positioning Signalling via user plane.
- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. reduction of location service latency, signalling overhead and location estimate exposure.
- Study how the location services can benefit from NWDAF reporting and how the NWDAF use cases can benefit from location services, e.g. enhanced accuracy in certain UE location or population flow statistics data that require UE locations smaller than TA/cell
- Study enhancements to support low power positioning (e.g. for RedCap) including the requirements related to low power high accuracy positioning described in TS 22.104 [7].
- Study necessary enhancement to support regulatory requirement i.e. the network should not notify the UE by any means during the LCS session.
- Study enhancement to support the Flexible and Efficient Periodic and Triggered Location for UE power saving purpose.
- In collaboration with RAN, study specific network functionality related to use of Positioning Reference Units (PRUs) as defined by RAN WGs and study how 5GS to support a specific UE (i.e. Reference UE) to improve the accuracy of positioning, and reduce the signalling:
- Study enhancements to support the location service continuity for UE mobility, i.e. between EPS and 5GS;
- For 5G with satellite access, in collaboration with RAN, study LCS architectural enhancement to support network verified UE location, and to meet location services related requirements defined in TS 22.261 [8]. |
23.700-74 | Study on generic group management, exposure and communication enhancements | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-74/23700-74-i00.zip | The scope of this Technical Report is to study potential enhancements on generic group management, exposure and communication. Specifically, the following aspects are in the scope of the study:
- Enhance group attribute management and group status event reporting:
- set/modify the group attributes: provisioning of service area or QoS applicable to each UE of a given group;
- subscribe to group status event reporting for the event "newly registered or (de)-registered group member".
- Study whether and how to enhance NEF exposure framework to enable capability exposure for provisioning of traffic characteristics and monitoring of performance characteristics applicable to each UE of a given group.
- Support group communication for a 5G VN, which supports multiple SMFs, including support of SMF redundancy for reliability of the 5G VN group communication.
- Whether additional mechanism or enhancement is needed and how to support group communication allowing UE to simultaneously send data to different groups, where each group has a different QoS policy (requirement regarding 5SEI as indicated in clause 6.13.2 of TS 22.261 [6]). |
23.700-76 | Study on ad hoc group communication support for mission critical services | TR | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-76/23700-76-i00.zip | The present document studies solutions to satisfy the requirements identified to support Ad hoc group communication for MCX services. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support Ad hoc group communications. Requirements for this study are taken from 3GPP TS 22.280 [3]. |
23.700-78 | Study on Application layer support for Personal IoT Network | TR | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-78/23700-78-i10.zip | The present document is a technical report capturing the study on application layer support for Personal IoT networks (PIN). The aspects of the study include analyzing application layer architecture requirements of PIN, identifying key issues and supporting PIN application layer functional model. The study also includes information and support from 3GPP network to PIN, service or applications discovery within a PIN or by the UE outside of a PIN via 3GPP network.
The study takes into consideration the work done for PIN in 3GPP TS 23.700-88 [4] and other related work in 3GPP. |
23.700-79 | Study of gateway User Equipment (UE) function for Mission Critical (MC) communications | TR | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-79/23700-79-i00.zip | The present document studies solutions to satisfy the requirements for a Gateway UE function. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical communications. Requirements for this study are taken from stage 1 requirements, including 3GPP TS 22.179 [2] and 3GPP TS 22.280 [3]. |
23.700-80 | Study on 5G system support for AI/ML-based services | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-80/23700-80-i00.zip | This Technical Report will study, based on requirements as specified in clauses 6.40 and 7.10 of TS 22.261 [2], 5GS assistance to support Artificial Intelligence (AI) / Machine Learning (ML) model distribution, transfer, training for various applications, e.g. video/speech recognition, robot control, automotive, etc.
The scope of this study is on how the AI/ML service providers could leverage 5GS as the platform to provide the intelligent transmission support for application layer AI/ML operation based on the following objectives.
1. Study the possible architectural and functional extensions to support the Application layer AI/ML operations defined in TS 22.261 [2], more specifically:
a. Support monitoring of network resource utilization in the 5G system relevant to the UE in order to support Application AI/ML operation.
b. Whether and how to extend 5GS information exposure for 5GC NF(s) to expose UE and/or network conditions and performance prediction (e.g. location, QoS, load, congestion, etc.) to the UE and/or to the authorized 3rd party to assist the Application AI/ML operation.
c. Enhancements of external parameter provisioning to 5GC (e.g. expected UE activity behaviours, expected UE mobility, etc.) based on Application AI/ML operation.
d. Investigate the enhancements of other 5GC features that could be used to assist the Application AI/ML operations as described in clause 6.40 of TS 22.261 [2].
2. Study possible QoS, Policy enhancements to support Application AI/ML operational traffic while supporting regular (non Application-AI/ML) 5GS user traffic.
3. Study whether and how 5GS provides assistance to AF and the UE for the AF and UE to manage the Federated Learning (FL) operation and model distribution/redistribution (i.e. FL members selection, group performance monitoring, adequate network resources allocation and guarantee) to facilitate collaborative Application AI/ML based Federated Learning operation between the application clients running on the UEs and the Application Servers. |
23.700-81 | Study of Enablers for Network Automation for the 5G System (5GS); Phase 3 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-81/23700-81-i00.zip | This study focuses on key issue description, solution and evaluation/conclusion on further enhancement for network automation, as documented in TS 23.288 [5], by covering the following objectives:
- Study possible mechanisms for improved correctness of NWDAF analytics;
- Investigate whether and how NWDAF can assist application detection;
- Investigate whether and how to support data and analytics exchange in roaming case;
- Investigate data collection and data storage enhancements (including DCCF and ADRF enhancements, e.g. DCCF relocation, ADRF selection, ML model storage);
- Study whether and how to enhance trained ML Model sharing for different vendors;
- Study whether and how interactions between NWDAF can leverage MDAS/MDAF functionality for data collection and analytics;
- Investigate NWDAF-assisted URSP;
- Study whether and how to enhance the QoS sustainability analytics with finer granularity and additional input data;
- Study whether and how to enhance architecture to support federated learning in the 5GC; and
- Study NWDAF enhancements considering the finer granularity of location information than TA and cell level. |
23.700-85 | Study on enhancement of 5G User Equipment (UE) policy | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-85/23700-85-i00.zip | This study focuses on key issue description, solution and conclusion on the enhancement of 5G UE Policy aspect by covering following objectives:
- URSP rule provisioning and updating procedures for home-routed and LBO roaming scenario, while keeping the existing framework of policy control based on HPLMN.
- Investigate whether and how the network can be made aware when the UE enforces URSP rule and investigate whether and what actions the 5G network can perform.
- Investigate if enhancements are needed for provisioning UE with consistent URSP across 5GC and EPC, and study the mechanism if needed.
- Investigate how to support standardized and operator-specific traffic categories in the traffic descriptor of URSP. |
23.700-86 | Study on Architecture Enhancement to support Ranging based services and sidelink positioning | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-86/23700-86-i00.zip | The present document is to study 5GC architecture enhancements to enable Ranging-based services and sidelink positioning for commercial, V2X and public safety use cases in in-coverage, partial coverage, and out-of-coverage of 5G network, which include:
- Authorization and policy/parameter provisioning for a UE or a group of UEs;
- Ranging device discovery and service operation procedures between two UEs, between one UE and multiple UEs or via the assistance of another UE;
- Ranging and sidelink positioning service exposure to a UE or an Application Server who has requested the service. |
23.700-87 | Study on system architecture enhancement for next generation real time communication | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-87/23700-87-i00.zip | The scope of this document is to study IMS architecture enhancements to support new real time communication services based on requirements of e.g. eMMTEL and 5G_MEDIA_MTSI_ext.
The study in this document includes the following aspects:
1) Study the enhancement of IMS architecture and procedures to support Data Channel usage in IMS network, including whether and which functionalities are defined in IMS architecture for Data Channel server, with separate control plane and media plane, and Data Channel application repository, which procedures are needed between Data channel server and IMS AS to support call event notifications.
2) Study whether and how IMS architecture and functions are supported for the requirements from SA WG1 Rel-18 eMMTEL WID impacts:
- to support AR telephony communication.
- to support 3rd party to verify via operator network that the caller is authorized to use or reference specific identity information which can be securely signalled to the callee when placing a call.
3) Study whether and which IMS media control interfaces can be potentially applied for service based architecture, supporting both existing capabilities and new capabilities for possible new applications and efficient media processing. |
23.700-88 | Study on architecture enhancements for Personal IoT Network (PIN) | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-88/23700-88-i00.zip | The scope of this Technical Report is to study the enhancement of 5G System to support Personal IoT Network (PIN). The study addresses the service requirements documented in TS 22.261 [5] for the Personal IoT Networks. The following aspects needs to be studied:
- Architecture enhancement:
- To study the potential architectural enhancements for supporting management of PIN, access of PIN via PIN Element with Gateway Capability (PEGC), and communication of PIN (e.g. PIN Element communicates with other PIN Elements directly or via PEGC or via PEGC and 5GS).
- To study the potential architecture enhancements for supporting identifying PIN and the PIN Elements.
- Security related:
NOTE: The study may need cooperation with SA3. If solutions are related to security impact, they will be studied in SA WG3.
- To study how to identify PIN and the PIN Elements in the PIN at 5GC level to serve for authentication/authorization.
- Management as well as policy and routing control enforcement:
- To study the management of a PIN.
- To study the procedures for PIN discovery, PIN Element discovery. |
23.700-96 | Study on 5G-enabled fused location service capability | TR | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-96/23700-96-i00.zip | The present document studies and evaluates the application architecture aspects and solutions to address potential new and enhanced location capabilities for vertical application enabler, including the following aspects:
- Enabling location performance (accuracy, availability and latency) enhancements through combined use and fusion of 3GPP and non-3GPP location technologies at the application layer;
- Identification and classification of location related requirements (including location QoS) for vertical application services;
- Architecture enhancement leveraging 5G positioning and location services;
- Enabling location sources and positioning methods selection based on the requested location QoS;
- Initialization and configuration for fused location service;
- Enabling value-added location service capabilities exposure to vertical applications;
- Enhancements on SEAL location management addressing the aspects above.
NOTE: This study will not duplicate solutions already available in Core Network and RAN. |
23.700-90 | Study on interconnection and migration aspects for railways | TR | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-90/23700-90-i00.zip | The present document studies solutions to satisfy interconnection and migration needs for railways. It identifies enhancements to be included in the technical specifications for MCPTT (3GPP TS 23.379 [2]), MCVideo (3GPP TS 23.281 [3]), MCData (3GPP TS 23.282 [4]) and in the common functional architecture (3GPP TS 23.280 [5]) to support mission critical communications. |
23.700-89 | Study on 5G AM Policy | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-89/23700-89-i00.zip | The aim of this Technical Report is to study and evaluation of potential enhancements for Access and Mobility Policy Management with the following objective(s):
- To study the mechanisms to provide AM policy control on RFSP Index consistency when UE moves from 5GC to EPC, and define enhancements in R17 mechanism if needed. |
23.700-97 | Study on Application Capability Exposure for IoT Platforms | TR | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-97/23700-97-i10.zip | The present document is a technical report which identifies SEAL functionality to support application capability exposure to general purpose servers or 3rd party IoT applications via IoT Platforms. Key issues and corresponding solutions necessary to ensure efficient use and deployment of IoT Platforms in the 5G network are included.
The study takes into consideration the existing work for Core Network exposure in 3GPP TS 23.502 [2] and provides recommendations for normative work. |
23.700-95 | Study on application enablement aspects for subscriber-aware northbound API access | TR | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-95/23700-95-i10.zip | The present document studies the potential enhancements in CAPIF and application enablement frameworks (e.g. SEAL, EDGEAPP, vertical enabler layers) to support the subscriber-aware northbound API access (SNA), whose requirements are specified in TS 22.261 [2].
This study takes into consideration the existing works for CAPIF (3GPP TS 23.222 [3]), SEAL (3GPP TS 23.434 [4]), and EDGEAPP (3GPP TS 23.558 [5]).
Any potential enhancements to security procedures related to CAPIF and application enablement frameworks (e.g. EDGEAPP, SEAL, vertical enabler layers) to support SNA are not in the scope of this study. |
23.700-98 | Study on enhanced Architecture for enabling Edge Applications | TR | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-98/23700-98-i10.zip | The present document is a technical report capturing the study on enhanced architecture for enabling edge applications over 3GPP networks. The study bases the enhancements on the work done in 3GPP TS 23.558 [2] and takes into consideration other related work done within and outside 3GPP i.e. ETSI MEC [3] and GSMA OP [4].
The aspects of the study include identifying new key issues, architecture requirements, related architecture enhancements and solutions, cardinality rules, deployment options, and involved entities and relationships to enhance the Rel-17 architecture for enabling edge applications. |
23.700-99 | Study on Network Slice Capability Exposure for Application Layer Enablement | TR | 18.2.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-99/23700-99-i20.zip | The study identifies the SA1 requirements and potential vertical requirements of network slice capability exposure that have yet to be realized, and proposes application architecture aspects solutions and enhancements to SEAL. Based on any gaps found between requirements and existing capabilities, the present document includes: identification of key issues, solutions, corresponding evaluations and conclusions to ensure the efficient network slice capability exposure.
The study takes into consideration the SEAL architecture specified in 3GPP TS 23.434 [2], network slicing related architecture and services(such as services of NEF) specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4], network slicing management capability provisioning and architecture specified in 3GPP TS 28.531 [5] and 3GPP TS 28.533 [6], requirements specified in TS 22.261 [7]. |
23.783 | Study on Mission Critical services support over 5G System | TR | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.783/23783-i00.zip | The present document analyses how to ensure that the set of Mission Critical services is supported over the 5GS. Key issues are derived and solutions are developed for the impacts on existing or new Stage 2 Mission Critical specifications. |
23.903 | Redial solution for voice-video switching | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-i00.zip | The present document describes the idle mode redial mechanism which 3GPP based systems can use to enhance switching between circuit switched voice and video services. |
23.919 | Direct tunnel deployment guideline | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-i00.zip | The present document contains deployment guidelines for the use of direct tunnelling of user plane data between the RNC and the GGSN (earlier known as the One Tunnel approach).
This report highlights the impacts of the 3GPP Release 7 Direct Tunnel solution to the current UMTS system in order to guide equipment development and network deployment. |
23.924 | Feasibility study on Non-Access Stratum (NAS) node selection function above Base Station Controller (BSC) / Radio Network Controller (RNC) | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.924/23924-i00.zip | This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications. |
23.946 | Guidelines for CAPIF Usage | TR | 18.2.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.946/23946-i20.zip | This TR provides guidelines for CAPIF usage for the benefit of the Application developer and API provider communities. This document also describes the usage and deployment options in CAPIF.
The work takes into consideration the work done for CAPIF in 3GPP TS 23.222 [2] and 3GPP TS 29.222 [3] and 3GPP TS 33.122 [4], and other related work outside 3GPP. |
23.958 | Edge Application Standards in 3GPP and alignment with External Organizations | TR | 18.3.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.958/23958-i30.zip | This TR provides the recommendations for the alignment of EDGEAPP architecture with ETSI MEC reference architecture and GSMA Operator Platform (OP) for the industry stakeholders.
This document provides recommendations of using specifications from 3GPP, ETSI ISG MEC and GSMA OPG to deploy an aligned edge system.
The present document is based on 3GPP TS 23.558 [2]. |
23.973 | User data interworking, coexistence and migration | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.973/23973-i00.zip | |
23.975 | IPv6 migration guidelines | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-i00.zip | The technical report identifies various scenarios of transition to IPv6 and co-existence of IPv4 and IPv6, deployment options and impacts on 3GPP network elements. In particular:
- Identify the transition and co-existence scenarios of interest for operators and the respective assumptions and requirements.
- Analyze existing IP address allocation mechanism for IPv6 migration if necessary.
- Investigate IPv6 transition mechanisms for the scenarios identified during the study and investigate their applicability for 3GPP network, and identify the compatibility among applicable transition mechanisms.
- Identify any impact on 3GPP network elements.
- Provide recommendations on IPv6 transition and co-existence of IPv4 and IPv6 and identify if any normative work is needed. |
23.976 | Push architecture | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-i00.zip | The purpose of this technical report is to analyse the service requirements for push services as defined in TS 22.174 "Push service; Stage 1". It continues the work of TR 23.875 (3GPP internal report).
This technical report describes methods for supporting push services by 3GPP delivery networks. The mechanisms described apply to existing delivery networks for the 3GPP Packet Switched (PS) domain, Circuit Switched (CS) domain, IP Multimedia Core Network Subsystem (IMS), Multimedia Broadcast / Multicast Service (MBMS), and Wireless Local Area Network (WLAN). Any necessary changes identified during this work will be introduced by means of change requests to the appropriate specifications.
The definition of Push Functionality that applies to push Application Servers is outside the scope of this work. The definition of Push Functionality that is best implemented in push Application Servers such as a Push Proxy and Push Initiator will be undertaken by other standards bodies and industry forums. |
23.977 | Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-i00.zip | The objective of this technical report is to identify the full set of requirements for bandwidth and resource savings and improved speech quality, with specific consideration to networks supporting A/Gb mode and the bearer independent circuit-switched core network (BICN). The different architectural solutions to meet these requirements will be assessed.
Consideration shall be made to existing architectures and solutions to provide harmony between 2G nodes, UMTS nodes and external networks (PSTN/ISDN). Backward compatibility to existing solutions and ease of network introduction/upgrade shall be given high importance. |
23.979 | 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-i00.zip | The present document studies the architectural requirements in order to enable services like PoC over 3GPP systems. The report looks into aspects of using 3GPP PS domain and radio access technologies (GERAN, UTRAN) for bearer services and IMS for reachability and connectivity for applications like PoC. |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-i00.zip | The present document studies study interworking and migration scenarios related to IPv4 based IMS implementations. The study provides guidelines for operators and vendors on interworking aspects of IPv4 based IMS implementations, and provides guidelines on migrating to 3GPP IMS using IPv6. |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-i00.zip | The present document describes the reference configuration for access to a PLMN.
A user accesses a PLMN via a number of interfaces, including the MS-BS (in A/Gb mode and GERAN Iu mode), UE-UTRAN (in UTRAN Iu mode), UE-E-UTRAN, and UE-5G-AN interface. The purpose of this document is to indicate the possible access arrangements that may be used in conjunction with the MS-BS (in A/Gb mode and GERAN Iu mode), UE-UTRAN (in UTRAN Iu mode), UE-E-UTRAN, and UE-5G-AN interface. |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 18.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-i30.zip | |
24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | TS | 18.8.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.008/24008-i80.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-i00.zip | The present document gives the general aspects of the specification of supplementary services at the layer 3 radio interface.
3GPP TS 24.08x and 24.09x‑series specify the procedures used at the radio interface (reference point Um as defined in 3GPP 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
3GPP TS 24.008 [48] and 3GPP TS 24.080 [27] specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 22.09x‑series.
Technical realization of supplementary services is described in 3GPP TS 23.011 and GSM 23.08x and 23.09x‑series.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 [49] and 3GPP TS 24.008 [48]. |
24.011 | Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-i00.zip | The present document specifies the procedures used across the mobile radio interface by the signalling layer 3 function Short Message Control (SMC) and Short Message Relay function (SM‑RL) for circuit switched in A/Gb mode, GPRS, EPS, and 5GS. |
24.022 | Radio Link Protocol (RLP) for circuit switched bearer and teleservices | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-i00.zip | The present document specifies the Radio Link Protocol (RLP) for circuit switched data transmission within a PLMN. RLP covers the Layer 2 functionality of the ISO OSI Reference Model (ISO/IEC 7498 [22]). It is based on ideas contained in ISO/IEC 3309 [21], ISO/IEC 4335 [20] and ISO/IEC 7809 [26] (HDLC of ISO) as well as ITU-T Recommendation X.25 [30] and Q.92x (LAP-B and LAP-D of ITU, respectively.) RLP has been tailored to the special needs of digital radio transmission. RLP provides to its users the OSI Data Link Service (ISO/IEC 8886 [24]).
RLP is intended for use with non-transparent data-transfer. Protocol conversion may be provided for a variety of protocol configurations. Those foreseen immediately are:
- character-mode protocols using start-stop transmission (IA5);
- X.25 LAP-B.
For reasons of better presentation, material about protocol conversion has been placed within those Specifications concerned with the relevant Terminal Adapters, i.e. 3GPP TS 27.002 [10] for the asynchronous case and 3GPP TS 27.003 [11] for the synchronous case. Care must be taken that that material also applies to Interworking Functions; see 3GPP TS 29.007 [13].
The present document is valid for a PLMN in A/Gb mode as well as in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". Please note, that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-i00.zip | The present document gives the stage 3 description of the Location Service (LCS) operations for mobile station. These operations shall apply to both CS and PS domain.
The group of location services operations is divided into two different classes:
‑ Network initiated location services operations (clause 4);
‑ Mobile initiated location services operations (clause 5). |
24.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-i00.zip | The present document specifies the procedures used at the radio interface (Reference point Um for GSM and Reference point Uu for UMTS as defined in TS 24.002) for normal operation, invocation, registration and interrogation of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP) supplementary service. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in TS 22.004 and TS 22.08x and22.09x -series. TS 22.067 is related specially to eMLPP.
Technical realization of supplementary services is described in TS 23.011 and TS 23.08x and 23.09x -series.
TS 23.067 is related specially to eMLPP.
The procedures for Call Control, Mobility Management at the layer 3 radio interface are defined in TS 24.007 and TS 24.008.
The procedure for Radio Resource management at layer 3 radio interface is defined in 3GPP TS 44.018 and TS 25.331. |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-i00.zip | This Global System for Mobile communications Technical Specification specifies the procedures used at the radio interface (reference point Um as defined in 3GPP TS 24.002) for normal operation of Call Deflection (CD) supplementary service. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface. |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 18.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-i70.zip | |
24.081 | Line Identification supplementary services; Stage 3 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-i00.zip | The present document specifies the procedures used at the radio interface for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of line identification supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the mobile subscriber and the service provider and cause no signalling on the radio interface.
In 3GPP TS 24.010 the general aspects of the specification of supplementary services at the layer 3 radio interface are given.
3GPP TS 24.080 specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x‑series. 3GPP TS 22.081 is related specially to line identification supplementary services.
Technical realization of supplementary services is described in 3GPP TS 23.011 and 3GPP TS 23.08x and 3GPP TS 23.09x‑series. 3GPP TS 23.081 is related specially to line identification supplementary services.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface are defined in 3GPP TS 24.007 and 3GPP TS 24.008.
The following supplementary services belong to the line identification supplementary services and are described in the present document:
- Calling line identification presentation (CLIP) (clause 1);
- Calling line identification restriction (CLIR) (clause 2);
- Connected line identification presentation (COLP) (clause 3);
- Connected line identification restriction (COLR) (clause 4). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.