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.161 | Network-Based IP Flow Mobility (NBIFOM); Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.161/23161-g00.zip | |
23.167 | IP Multimedia Subsystem (IMS) emergency sessions | TS | 16.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-g40.zip | |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 16.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-g00.zip | |
23.202 | Circuit switched data bearer services | TS | 16.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-g00.zip | |
23.203 | Policy and charging control architecture | TS | 16.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-g30.zip | |
23.204 | Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-g00.zip | |
23.205 | Bearer-independent circuit-switched core network; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-g00.zip | |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-g00.zip | |
23.214 | Architecture enhancements for control and user plane separation of EPC nodes | TS | 16.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.214/23214-g20.zip | |
23.216 | Single Radio Voice Call Continuity (SRVCC); Stage 2 | TS | 16.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-g70.zip | |
23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-g00.zip | |
23.221 | Architectural requirements | TS | 16.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-g20.zip | |
23.222 | Common API Framework for 3GPP Northbound APIs | TS | 16.13.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.222/23222-gd0.zip | |
23.226 | Global text telephony (GTT); Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-g00.zip | |
23.228 | IP Multimedia Subsystem (IMS); Stage 2 | TS | 16.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-g70.zip | |
23.231 | SIP-I based circuit-switched core network; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-g00.zip | |
23.236 | Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-g00.zip | |
23.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | TS | 16.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.237/23237-g40.zip | |
23.240 | 3GPP Generic User Profile (GUP); Architecture (Stage 2) | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-g00.zip | |
23.246 | Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description | TS | 16.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-g10.zip | |
23.251 | Network sharing; Architecture and functional description | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-g00.zip | |
23.259 | Personal Network Management (PNM); Procedures and information flows; Stage 2 | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-g00.zip | |
23.261 | IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.261/23261-g00.zip | |
23.271 | Functional stage 2 description of Location Services (LCS) | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-g00.zip | |
23.272 | Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.272/23272-g00.zip | |
23.273 | 5G System (5GS) Location Services (LCS); Stage 2 | TS | 16.13.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.273/23273-gd0.zip | |
23.278 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-g00.zip | |
23.279 | Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.279/23279-g00.zip | |
23.280 | Common functional architecture to support mission critical services; Stage 2 | TS | 16.7.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.280/23280-g70.zip | |
23.281 | Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2 | TS | 16.4.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.281/23281-g40.zip | |
23.282 | Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2 | TS | 16.8.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.282/23282-g80.zip | |
23.283 | Mission Critical Communication Interworking with Land Mobile Radio Systems | TS | 16.8.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.283/23283-g80.zip | |
23.284 | Local Call Local Switch (LCLS); Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.284/23284-g00.zip | |
23.285 | Architecture enhancements for V2X services | TS | 16.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.285/23285-g40.zip | |
23.286 | Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows | TS | 16.6.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.286/23286-g60.zip | |
23.287 | Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services | TS | 16.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.287/23287-g70.zip | |
23.288 | Architecture enhancements for 5G System (5GS) to support network data analytics services | TS | 16.12.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.288/23288-gc0.zip | |
23.292 | IP Multimedia Subsystem (IMS) centralized services; Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.292/23292-g00.zip | |
23.303 | Proximity-based services (ProSe); Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.303/23303-g00.zip | |
23.316 | Wireless and wireline convergence access support for the 5G System (5GS) | TS | 16.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.316/23316-g90.zip | |
23.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions | TS | 16.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.333/23333-g20.zip | |
23.334 | IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions | TS | 16.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.334/23334-g40.zip | |
23.335 | User Data Convergence (UDC); Technical realization and information flows; Stage 2 | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.335/23335-g00.zip | |
23.379 | Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2 | TS | 16.6.1 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.379/23379-g61.zip | |
23.380 | IMS Restoration Procedures | TS | 16.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.380/23380-g50.zip | |
23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | TS | 16.14.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-ge0.zip | |
23.402 | Architecture enhancements for non-3GPP accesses | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.402/23402-g00.zip | |
23.434 | Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows | TS | 16.9.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.434/23434-g90.zip | |
23.468 | Group Communication System Enablers for LTE (GCSE_LTE); Stage 2 | TS | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.468/23468-g00.zip | |
23.479 | Technical Specification Group Services and System Aspects; UE MBMS APIs for Mission Critical Services; | TS | 16.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.479/23479-g00.zip | |
23.501 | System architecture for the 5G System (5GS) | TS | 16.20.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.501/23501-gk0.zip | |
23.502 | Procedures for the 5G System (5GS) | TS | 16.19.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.502/23502-gj0.zip | |
23.503 | Policy and charging control framework for the 5G System (5GS); Stage 2 | TS | 16.15.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.503/23503-gf0.zip | |
23.527 | 5G System; Restoration procedures | TS | 16.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.527/23527-g70.zip | |
23.632 | User data interworking, coexistence and migration; Stage 2 | TS | 16.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.632/23632-g60.zip | |
23.682 | Architecture enhancements to facilitate communications with packet data networks and applications | TS | 16.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.682/23682-ga0.zip | |
23.715 | Study on system enhancements for provision of access to restricted local operator services by an unauthenticated User Equipment (UE) | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.715/23715-g00.zip | The objective of this Technical Report is to identify and evaluate potential architecture enhancements of EPS and IMS needed to support Provision of Access to Restricted Local Operator Services by Unauthenticated UEs as identified in TS 22.101 [2], TS 22.115 [3] and TS 22.228 [4], and determine which of the solutions can proceed to normative specifications.
This feature is only applicable to EPS 3GPP access. Access to local operator services does not affect the UICC. |
23.716 | Study on the wireless and wireline convergence for the 5G System (5GS) architecture | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.716/23716-g00.zip | The objective of this study is to enhance the common 5G core network defined in TS 23.501 [2] and TS 23.502 [3] in order to support wireline access networks and Trusted N3GPP.
The key areas of the investigation are:
- Support of wireline access networks:
- Definition of the 5G Core network (5GC) with respect to wireline access functional split;
- Investigation on whether enhancements are needed to interfaces (e.g. N1, N2 and N3) used to connect wireline customer devices (CPE/Residential Gateway) and wireline access network to the converged 5GC;
- Study the impact of the common framework for authentication and security, policy and QoS, Network Slicing and investigation on whether enhancements are needed;
NOTE 1: The area of investigation for authentication and security will be limited to the part relevant to SA WG2 scope and responsibility.
- Study on how to support CPE/Residential Gateway (RG) capable of connecting via wireline and/or wireless access to the 5G CN;
- Study on how to support end user devices, with or without UICC, connected to the convergent 5GC from behind a CPE/RG;
- Identification of the impacts on mobility, session management and interaction with Access Traffic Steering, Switching and Splitting for UEs accessing the 5G convergent network studied in TR 23.793 [4] and investigation on whether enhancements are needed;
- Study on how to support CPE/RG capable of connecting simultaneously via both NG RAN and wireline access to 5GC.
NOTE 2: The above scenario is referred as Hybrid Access in Broadband Forum (BBF TR-348 [5]).
- Definition of architecture for the Trusted N3GPP scenario applicable not only to wireline accesses.
- Support of Trusted access networks:
- Requirements for the Trusted Non-3GPP access in 5G system;
- Architecture definition for the Trusted Non-3GPP access in 5G System;
- Investigation on whether enhancements are needed to interfaces (e.g. N1, N2 and N3) used to connect the trusted non-3GPP access network to converged 5GC;
- study the impact of the common framework for authentication and security, policy and QoS, Network Slicing and investigation on whether enhancements are needed.
NOTE 3: The study will consider whether "Trusted" terminology or a different terminology would be more suitable for representing the scenario where there is a more tight relationship compared to Untrusted case between the WLAN Access Network and the 5GC.
This study will follow the high level principles, agreements, and conclusions of the normative work agreed in TS 22.261 [7], TS 23.501 [1] and TS 23.502 [2].
The study will take into account information provided by the BBF on wireless and wireline convergence. |
23.724 | Study on Cellular Internet of Things (CIoT) support and evolution for the 5G System (5GS) | TR | 16.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.724/23724-g10.zip | This technical report studies and evaluates architecture enhancements to address the following objectives:
Objective I: Enable CIoT/MTC functionalities in 5G CN.
The objective is to study how to support identified CioT/MTC functionalities in 5G CN with potential connectivity to WB-EUTRA (eMTC) and/or NB-IoT for 5GS capable devices.
The following CIoT/MTC functionalities need to be evaluated and studied how to enable them in 5G CN, if needed:
- Equivalent overall functionalities as provided by SCEF for CIoT/MTC.
- Monitoring.
- Small data transmission (infrequent and frequent small data transmission including frequent small data transmission from tracking devices).
- Additional power saving functions unless those are supported for 5G system in Rel-15.
- Non-IP Data Delivery.
- Overload control (as relevant in 5G CN).
- Support of Coverage enhancement including adaptations in 5G CN required to support latencies.
- Equivalent to Group communication and messaging.
- Reliable communication via functionality equivalent to SCEF.
- Inter-RAT mobility support to/from NB-IoT.
- High latency communication.
- Include location services procedures for IoT in 5G location services.
NOTE: Attach without PDN connection and non-IP PDN Connection type is already supported in 5G CN (TS 23.501 [5]).
Ensure that regulatory requirements can be fulfilled at the same level as in EPC.
Objective II: Co-existence and migration from EPC based eMTC/NB-IoT to 5GCN.
Study solutions for coexistence and migration from EPC towards 5G CN for eMTC/NB-IoT.
This objective will study solutions where the same service is offered to some UEs connected to EPC and some UEs connected to 5G CN e.g. using SCEF and equivalent functionalities in 5GCN. Solutions that assume that 5G CN needs to support EPC NAS signaling for legacy IoT devices access are not considered.
Any modifications in the EPC-5GC interworking "baseline" specific to CIOT will also be discussed as part of Objective II.
Objective III: 5G System enhancements to address 5G service requirements (based on TS 22.261 [2] and TR 38.913 [3]).
To study system architecture enhancements to address related service requirements defined in TS 22.261 [2] and RAN requirements defined in TR 38.913 [3] and how to enable them in 5G CN, if needed. At least the following service requirements have been identified:
- Enable the change of association between subscription and address/number of an IoT device within same operator and in between different operators.
- Restricted Registration procedure to allow IoT device provisioning.
Any system implications for the RAN will be coordinated with RAN WGs.
This study is not going to study enhancements to EPC. |
23.725 | Study on enhancement of Ultra-Reliable Low-Latency Communication (URLLC) support in the 5G Core network (5GC) | TR | 16.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.725/23725-g20.zip | The objective of this Technical Report is to study and perform an evaluation of potential architecture enhancements for supporting URLLC services in 5G System (5GS). Specifically, the following aspects are covered:
- Investigate the key issues for meeting the URLLC requirements on latency, jitter and reliability in 5G System as defined in TS 22.261 [5].
- Study how to minimize the impacts of UE mobility to the latency and jitter between AN and CN, and within CN.
- Study how to realize transmission with reliability higher than the reliabilities of single user plane tunnel of N3 and N9 and NFs in the user plane path.
- Study how to monitor the QoS of the QoS flow with URLLC requirement.
- Study potential impacts to charging and policy control. |
23.726 | Study on enhancing topology of the Service Management Function (SMF) and the User Plane Function (UPF) in 5G networks | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.726/23726-g00.zip | The objective of this Technical Report is to study enhancements of 5GS architecture that has been defined in Rel-15 about the topology of SMF and UPF, and:
1. investigate mechanisms to enable the 3GPP system to support deployments where a SMF is not able / allowed to control UPF(s) throughout the same PLMN.
2. Study whether it is needed to enhance the capability of 5GS architecture for a UPF to be controlled by multiple SMF's (and many UPF's to be controlled by many SMFs) and, if yes, define such enhancements.
For these objectives, use cases will be defined. |
23.727 | Study on application awareness interworking between LTE and NR | TR | 0.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.727/23727-020.zip | The scope is to study the mechanisms to address use cases dealing with policy driven selection of E-UTRA or NR based on certain criteria (e.g. for a given DNN or a QoS flow) associated with user applications by the core network.
Scenario 1: The E-UTRA access node and NG-RAN access node are connected to EPC and 5GC respectively.
Scenario 2: The E-UTRA access node and NR access node are connected to 5GC in a dual connectivity mode.
Potential area of study includes evaluating the mechanism available in 5G system as well as any potential enhancements that may improve the potential shortcomings identified by the study use cases.
RAN, while making use of the operator provided policies, is assumed to make final decision regarding handover/redirection/switching as RAN has the responsibility into radio and load conditions which govern the success of such a decision. |
23.728 | Study on system architecture enhancement for next generation real time communication | TR | 0.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.728/23728-000.zip | |
23.731 | Study on enhancement to the 5GC LoCation Services (LCS) | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.731/23731-g00.zip | The objectives of this Technical Report are to enhance the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs) and procedures, to meet the service requirements defined in, SA WG1 (e.g. TS 22.261 [2] and TS 22.071 [3]), including the consideration of roaming and non-roaming scenarios, and access via 3GPP as well as non-3GPP access technologies (un-trusted, and trusted in TR 23.716 [9]). Of particular consideration is how to support location services in 5GS and EPS interworking scenarios, and in non-3GPP access and 3GPP access interworking scenarios.
This Technical Report will need to consider related architectures and functions developed in RAN, and implications if any. |
23.732 | Study on user data interworking, coexistence and migration | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.732/23732-g00.zip | The objective of this Technical Report is to investigate scenarios for co-existence of subscription data pertaining to legacy system (EPS) with data pertaining to the 5G system, when the HSS+UDM defined in Rel-15 is separated and both UDM and HSS are independent, and will propose solutions to support this deployment where necessary.
NOTE 1: The subscription data referred to by this Technical Report comprises both static as well as dynamic data, including IMS, LCS, SMS data.
- study diverse scenarios related to the storage of subscription data including, but not limited to, those of common repository for subscription data from EPS and 5GS, as well as separate repositories for EPS and 5GS subscription data,
- investigate the relevant procedures in TS 23.502 [2] (for e.g. authentication, mobility, handover and procedures for IMS and SMS handling in interworking between 5G system and EPS),
- determine if there is a need for interaction between the consumers of EPS and 5GS data, in the different interworking cases and deployment scenarios.
Existing procedures in TS 23.502 [2] shall not be impacted.
Provisioning aspects are outside this study.
Direct interactions between the EPS UDR and the 5GS UDR are out of the scope of this TR (i.e. it is assumed that there is no direct interaction between these two repositories). |
23.734 | Study on enhancement of 5G System (5GS) for vertical and Local Area Network (LAN) services | TR | 16.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.734/23734-g20.zip | The objective and scope of this TR is to study enhancements to 5GS that are required to fulfil Stage-1 service requirements in vertical domains defined in TS 22.261 [2] and TS 22.104 [13]:
- Enablers (e.g. time synchronization of packet delivery in each hop) to support Time Sensitive Networking, and industrial control use cases specified by Stage 1.
- Architecture enhancements required to support security requirements.
NOTE 1: Security aspects will be studied in cooperation with SA WG3.
- Enhancements to the 5G system to support 5GLAN service.
- Enhancements to service exposure via APIs for 3rd party use of functionalities e.g. for information regarding the geographic location of coverage area of non-public network;
- Enablers to support new KPIs (e.g. 5QI) to meet service requirements of vertical;
- Support for non-public networks:
- Support for UEs being registered in non-public network and a PLMN when the UE supports credentials required for non-public network and credentials required for a PLMN and is able to maintain both registrations independently.
- Support for roaming, mobility and service continuity between PLMN and non-public networks (e.g. for mobility from non-public networks to PLMN) with direct interaction between non-publicnetworks and PLMN.
NOTE 2: While support for stand-alone operation of non-public network and interworking between PLMN and non-public networks is one of the objectives of the study, there is no assumption that either are required in all deployment scenarios.
NOTE 3: The objectives are subject to alignment with the corresponding normative work of TS 22.261 [2] and TS 22.104 [13] that is still ongoing in SA WG1. |
23.735 | Study on enhancements of Public Warning System | TR | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.735/23735-g00.zip | The present document studies and evaluates possible enhancements of Public Warning System(ePWS) to address the following objectives:
- to develop stage 2 specifications to support stage 1 requirements on ePWS as follows
1) Specify how to support the language-independent contents (e.g. non-text based icon or image mapping to a disaster). In detail, this is to specify how to map the disaster by using symbols or images so that users can recognize the disaster in their screens. (It is a useful scenario for foreigners who do not know languages.)
2) Specify how to support UEs with no user interface or UEs with a user interface that is incapable of displaying text based warning notification. In detail, there is a specific requirement on UEs with no user interface or UEs with a user interface that can not display a text based warning notification. UEs with no user interface can be IoT device and it was intended that the device performs some dedicated actions when the warning notification is received.
3) Specify how to support relay functionality for providing warning notification.
- to develop stage 3 specifications to support stage 1 requirements on ePWS.
No new functionality for US WEA and Japan ETWS will be introduced. |
23.736 | Study on enhancement of systems using Evolved Packet System (EPS) for Ultra Reliability and Availability using commodity equipment | TR | 0.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.736/23736-020.zip | The objective of this Technical Report is to study the solutions and potential enhancements needed for systems using EPS to enable data services (UE to Data Network, and, UE to UE via Data Network) with one or more the following requirements:
1. Availability greater than that of a single pre-Release 16, EPC based 3GPP system with a traditional arrangement of base stations, power supplies, transmission links and core network entities.
2. Providing reliable (e.g. better than 1*10-9 undetected bit error rate) 3GPP data services with low latency (e.g. less than 15 ms between UE and application server).
Editor's note: exact requirements are still under development in SA WG1.
3. Providing prompt, deterministic recovery mechanisms following periods where the required connectivity quality of the EPS bearer was not achieved.
4. Investigating the end to end provision of 3GPP data services with low jitter, e.g. less than 100µs between UE and Data Network.
Editor's note: Exact requirements are still under development in SA WG1. |
23.737 | Study on architecture aspects for using satellite access in 5G | TR | 1.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.737/23737-120.zip | |
23.738 | Study on supporting Flexible Local Area Data Network | TR | 0.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.738/23738-000.zip | |
23.739 | Study on enhancement of EPC for low latency communication including device mobility | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.739/23739-100.zip | Low latency user plane radio links are substantially enhanced by 3GPP's NR and E-UTRAN radio technologies in Release 15. Mobility remains one of the key differentiators between 3GPP's technologies and other systems (e.g. systems that use unlicensed radio, or fixed networks). Hence it is important to network operators that mobility is effectively supported for the enhanced, low latency radio features.
As the Release 15 RAN enhancements are targeted at around 1 ms one-way radio interface latencies, this TR looks at architectural enhancements and solutions for networks where the transmission latency between the radio base station site and SGi can be around 0.1 ms to 1 ms latency (c.f. 20-200km of speed of light delay in optic fibre).
This Technical Report investigates the enhancement of EPC for low latency communication including device mobility, using the CUPS architecture (TS 23.214 [2]) and by identifying solutions based on EPC functionality (TS 23.401 [3]) in the following area:
- improvements to enable low latency following UE mobility and, possibly, following the activation of a service requiring low latency.
The aim is to retain the single SGW-C per UE concept but utilise SGW-C's "independent SGW-U per PDN connection" concept and expect to base on a "make before break" PDN connection mobility concept (with UE IP address change). To deliver low latency it is anticipated (but not mandated) that most solutions will use a combined S/PGW(-U). Anticipated investigations include:
- whether to initiate "make before break" from e.g. MME or PCRF,
- the need for e.g. PGW-C to PCRF interface extensions to support "make before break" PDN connection mobility (and if needed to support this, e.g. MME-SGW-PGW interface extensions).
Possible intermediate versions of the solutions may be maintained in this Technical Report. |
23.740 | Study on enhancement of network slicing | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.740/23740-g00.zip | The scope of this Technical Report is:
- Identify, prioritize and study the practical non-roaming and roaming deployment scenarios and system impacts when the 5GS is not able to support all possible combination of S-NSSAIs for the UE, and the aspects of mutually exclusive access to Network Slices.
- Study the possible enhancement for the Network Slicing interworking with EPC for Connected and Idle modes.
- Study how to provide Network Slice Access authentication and authorization specific for the Network Slice Access authorization that uses User Identities and Credentials different from the 3GPP SUPI and that takes place after the primary authentication which is still required between the UE and the 5GS for PLMN access authorization and authentication. |
23.742 | Study on Enhancements to the Service-Based Architecture | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.742/23742-g00.zip | This technical report studies and evaluates architecture enhancements on potential optimizations to the Release 15 Service-Based Architecture (SBA) in order to provide higher flexibility and better modularization of the 5G System for the easier definition of different network slices and to enable better re-use of the defined services. Moreover, the technical report considers mechanisms in order to better support automation and high reliability of network function service(s). The following aspects are covered:
- Optimizing the modularization of the system to improve its agility.
- Extending the service concept from 5GC control plane to the user plane function(s).
- Further improvements to service framework related aspects.
- Architectural support for highly reliable deployments, considering.
- Study backward and forward compatibility implications resulting from the above bullets. |
23.743 | Study on optimisations on UE radio capability signalling | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.743/23743-g00.zip | With the increase of the size of UE radio capabilities driven by additional bands supported by RAN specifications and UE support of significantly more band combinations, the size of the UE Radio Capabilities has and will significantly grow from Rel-15 onwards, an efficient approach to signal UE Radio Capability information is therefore needed.
This study item shall address two issues:
- Optimizations of system procedures pertaining to the transfer UE Radio Capabilities related information to RAN.
- Optimizations of system procedures related to transfer UE Radio Capabilities impacting the Core Network.
The overall goal is to study mechanisms to reduce the signalling over Uu, CN-RAN, CN-CN and RAN-RAN interfaces as well as the processing load in core and RAN (taking into account how frequently those message transfers and corresponding processing occurs) working in collaboration with RAN WGs for the related RAN interfaces and CT WG4 for the CN interfaces and NFs.
At minimum, the study shall consider the UE Radio Capabilities related aspects and any other optimisation which is deemed necessary in collaboration with RAN WGs. The study also considers scenarios where the UE radio capabilities change based on various events triggered in NAS (e.g. when certain services are not supported in one system/access and the UE wants to stay registered in another system/access, the UE may disable the radio capability for accessing the first system).
As part of the study and in coordination with other WGs especially RAN WGs it should be concluded whether to proceed with normative work. |
23.744 | Study on location enhancements for mission critical services | TR | 1.5.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.744/23744-150.zip | |
23.756 | Study for single radio voice continuity from 5G to 3G | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.756/23756-g00.zip | The scope of the present document is to investigate solutions from architecture point of view to support single radio voice call continuity (SRVCC) from NG-RAN to UTRAN.
Issues to be resolved will be collected and documented in the TR with a possible resolution. |
23.778 | Study on Mission Critical services access aspects | TR | 16.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.778/23778-g00.zip | This technical report is a study of mission critical service access aspects. 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.281 [4], 3GPP TS 22.282 [5] and 3GPP TS 22.346 [6].
This document provides recommendations for normative work. |
23.783 | Study on Mission Critical services support over 5G System | TR | 0.13.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.783/23783-0d0.zip | |
23.784 | Study on discreet listening and logging for mission critical services | TR | 16.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.784/23784-g00.zip | The present document studies solutions to satisfy the requirements for discreet listening and logging for mission critical services. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical services. Requirements for this study are taken from the Stage 1 requirements, including 3GPP TS 22.280 [2], and 3GPP TS 22.281 [3]. |
23.786 | Study on architecture enhancements for the Evolved Packet System (EPS) and the 5G System (5GS) to support advanced V2X services | TR | 16.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.786/23786-g10.zip | The objective of this Technical Report is to identify and evaluate potential architecture enhancements of EPS and 5G System design needed to support advanced V2X services identified in TR 22.886 [2], based on vehicular services requirements defined in TS 22.185 [3] and TS 22.186 [4] and determine which of the solutions can proceed to normative specifications.
In Rel-15, the study focuses on EPS. |
23.787 | Study on encrypted traffic detection and verification | TR | 0.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.787/23787-040.zip | The scope is to study encrypted traffic detection and verification, including:
- Solutions for encrypted traffic detection and verification.
- Solutions for how to manage the information for encrypted traffic detection and verification. |
23.791 | Study of enablers for Network Automation for 5G | TR | 16.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.791/23791-g20.zip | The aim of this Technical Report is to study and specify how to collect data and how to feedback data analytics to the network functions. |
23.792 | Study on MBMS APIs for Mission Critical Services | TR | 16.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.792/23792-g00.zip | The present document is a technical report that identifies the MBMS API solutions on the UE for mission critical applications to access MBMS bearer service for the usage of mission critical services. The aspects of the study include identifying functional requirements, methods and message flows, client reference model, potential impacts to MC system architecture, and the review of existing and new MBMS capabilities for use by MC services. |
23.793 | Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.793/23793-g00.zip | The purpose of this document is to study how the 5G System (5GS) can be extended in order to support Access Traffic Steering, Switching and Splitting (ATSSS) between 3GPP and non-3GPP access networks. In particular, this document considers solutions that specify the following:
- How the 5GC and the 5G UE can support multi-access traffic steering (as defined in clause 3.1) between 3GPP and non-3GPP accesses.
- How the 5G Core network and the 5G UE can support multi-access traffic switching (as defined in clause 3.1) between 3GPP and non-3GPP accesses. This includes the conditions that can trigger the switching of data traffic to a new access type.
- How the 5G Core network and the 5G UE can support multi-access traffic splitting (as defined in clause 3.1) between 3GPP and non-3GPP accesses (multi access PDU session). This includes the conditions that can trigger the splitting of data traffic across multiple accesses.
- How the multi-access traffic steering, switching and splitting (ATSSS) can be taken into account by the charging framework in order e.g. to enable the network operator to differentiate charging for data traffic that is switched and/or split between 3GPP and non-3GPP accesses.
- How the policy framework can be extended in order to support the requirements for ATSSS.
- How ATSSS can be supported by using multi-access PDU sessions (as defined in clause 3.1). ATSSS solutions not requiring multi-access PDU sessions can also be considered.
- How to handle issues related to ATSSS that may occur when the UE moves between EPC and 5GC.
The scope of this document excludes the following aspects:
- Changes to the charging framework are not considered. However, it may be considered what information needs to be provided to the charging framework in order to charge traffic that is switched and/or split between 3GPP and non-3GPP accesses.
- ATSSS procedures that may be applied in the NG-RAN are not considered. The study is restricted only to ATSSS procedures applied in the 5G core network.
- 5GS enhancements to support trusted non-3GPP access networks are not considered.
- 5GS enhancements to support wireline access networks are not considered.
All solutions in this document should be based on and aligned with the 5GS Phase-1 normative work including work on policy management, as documented in TS 23.501 [5], TS 23.502 [6] and TS 23.503 [7].
The study in this document is organized into two phases:
- Initially, the study considers ATSSS solutions that enable traffic selection, switching and splitting between NG-RAN and untrusted non-3GPP access networks.
- Subsequently, after the 5GS architecture is enhanced to support trusted non-3GPP access networks, the study will also consider ATSSS solutions that enable traffic selection, switching and splitting between NG-RAN and trusted non-3GPP access networks. |
23.794 | Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration | TR | 1.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.794/23794-110.zip | |
23.795 | Study on application layer support for V2X services | TR | 16.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.795/23795-g10.zip | The present document is a technical report which identifies the application architecture aspects to support V2X services, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of V2X services over 3GPP systems.
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to V2X in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3] and 3GPP TS 23.285 [8], as well as V2X application standards defined outside 3GPP.
This document will provide recommendations for normative work. |
23.796 | Study on application architecture for the Future Railway Mobile Communication System (FRMCS) Phase 2 | TR | 16.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.796/23796-g00.zip | The present document captures architectural requirements to develop solutions for the Future Railway Mobile Communication System (FRMCS) to meet Rel-16 normative Stage 1 requirements.
The normative Stage 1 requirements are specified in 3GPP TS 22.280 [2], 3GPP TS 22.179 [3], 3GPP TS 22.281 [4], 3GPP TS 22.282 [5] and 3GPP TS 22.289 [6].
The study uses existing 3GPP functionality and those specified for Mission Critical Communication in normative specifications 3GPP TS 23.379 [7], 3GPP TS 23.280 [8], 3GPP TS 23.281 [9], 3GPP TS 23.282 [10] and 3GPP TS 23.283 [11] as working basis.
This document will provide recommendations for normative work. |
23.903 | Redial solution for voice-video switching | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-g00.zip | |
23.919 | Direct tunnel deployment guideline | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-g00.zip | |
23.924 | Feasibility study on Non-Access Stratum (NAS) node selection function above Base Station Controller (BSC) / Radio Network Controller (RNC) | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.924/23924-g00.zip | |
23.973 | User data interworking, coexistence and migration | TR | 16.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.973/23973-g10.zip | |
23.975 | IPv6 migration guidelines | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-g00.zip | |
23.976 | Push architecture | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-g00.zip | |
23.977 | Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-g00.zip | |
23.979 | 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-g00.zip | |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 16.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-g00.zip | |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 16.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-g00.zip | |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 16.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-g50.zip | |
24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | TS | 16.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.008/24008-g70.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 16.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-g00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.