id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
38.836
|
Study on NR sidelink relay
|
TR
|
17.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.836/38836-h00.zip
|
The present document is related to Study on NR Sidelink Relay with a scope as defined in [2].
The document describes NR enhancements to support sidelink relay, which were analyzed as part of the study such as sidelink-based UE-to-Network and UE-to-UE Relay, and discovery model/procedure for sidelink relaying.
|
38.837
|
UE RF Requirements for Transparent Tx Diversity (TxD) for NR
|
TR
|
17.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.837/38837-h30.zip
|
The present document is a technical report for NR UE RF requirements for Transparent Tx Diversity (TxD).
|
38.838
|
Study on XR (Extended Reality) evaluations for NR
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.838/38838-h00.zip
|
The present document captures the results and findings from the study item "Study on XR Evaluation for NR"[2].
The purpose of this TR is
- to document the evaluation methodology for XR evaluation including XR applications, simulation scenarios, traffic models, KPIs, simulation parameters, etc,
- to document the performance evaluation results of XR applications in NR for both FR1 and FR2 considering the scenarios and services of interest,
- to document the identified problems/challenges in supporting XR applications of interest in various scenarios.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
|
38.839
|
Principles and requirements for simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.839/38839-h00.zip
|
The present document is a technical report for simultaneous Rx/Tx band combinations. The TR includes principles to decide mandatory/optional capability for FDD-TDD, TDD-TDD band combinations in different cases, identify case by case issues and align the specification treatment for CA/DC/SUL band combinations.
|
38.841
|
High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x =1,2)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.841/38841-h00.zip
|
The present document is a technical report for high power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address power class 2 NR inter-band CA for 2 bands DL with 2 bands UL in Table 1-1.
Table 1-1 Rel-17 power class 2 NR 2BDL/2BUL inter-band CA
NR CA
configuration
Uplink CA
configuration
Power class 2 cases
Release independent from
CA_nXA-nYA
CA_nXA-nYA
The allowed maximum output power by each of carrier for power class 2 cases is listed in table 1-2.
Table 1-2 Maximum output power for power class 2 cases
Power class 2 cases for CA_nXA-nYA
CA power class
Carrier X power class
Carrier Y power class
Case a
26dBm
23dBm
23dBm
Case b
26dBm
23dBm
26dBm
Case c
26dBm
26dBm
23dBm
Case d
26dBm
26dBm
26dBm
NOTE: The Carrier X and Y are one-by-one corresponding to carriers in CA configuration of CA_nXA-nYA
|
38.842
|
High power User Equipment (UE) (power class 2) for NR inter-band Carrier Aggregation (CA) and Supplementary Uplink (SUL) configurations with x (x>2) bands DL and y (y=1, 2) bands UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.842/38842-h00.zip
|
The present document is a technical report for high power UE (power class 2) for NR inter-band Carrier Aggregation or NR-NR DC with and without SUL with x (6≥x>2) bands downlink and y (y=1, 2) bands uplink under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address power class 2 NR inter-band CA/DC with and without SUL for more than 2 bands DL and with up to 2 bands UL in Table 1-1.
Table 1-1 Rel-17 power class 2 NR xBDL/yBUL inter-band CA and SUL
NR CA
configuration
Uplink CA
configuration
Power class 2 cases
Release independent from
CA_nV1-nV2-…-nVx
- (Note 1)
CA_nV1-nV2-…-nVx
CA_nVi-nVj (Note 2)
CA_nV1-nV2-…-SUL_nVx-nVx+1
SUL_nVx-nVx+1
Note 1: The UL carrier supports power class 2.
Note 2: The integers i and j satisfy: 1 ≤ i ≤ x, 1 ≤ j ≤ x, i ≠ j.
The allowed maximum output power by each of carrier for power class 2 cases is listed in table 1-2.
Table 1-2 Maximum output power for power class 2 cases
Power class 2 cases for UL CA_nVi-nVj
CA power class
Carrier Vi power class
Carrier Vj power class
Case a
26dBm
23dBm
23dBm
Case b
26dBm
23dBm
26dBm
Case c
26dBm
26dBm
23dBm
Case d
26dBm
26dBm
26dBm
NOTE: The Carrier Vi and Vj are one-by-one corresponding to carriers in UL CA configuration of CA_nVi-nVj.
|
38.845
|
Study on scenarios and requirements of in-coverage, partial coverage, and out-of-coverage NR positioning use cases
|
TR
|
17.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.845/38845-h00.zip
|
The present document captures the findings of the study item, "Study on scenarios and requirements of in-coverage, partial coverage, and out-of-coverage positioning use cases" [2]. The purpose of this TR is to facilitate future 3GPP work by identifying the requirements and deployment/operation scenarios for V2X and public safety use cases. In particular, this study considers positioning for the UEs in in-coverage, partial coverage, and out-of-coverage as per the network coverage definition in the current specifications.
This document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings until it is approved.
|
38.847
|
New frequency range for NR (47.2 – 48.2 GHz)
|
TR
|
17.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.847/38847-h20.zip
|
The present document is a technical report for Work Item on New Radio (NR) Access Technology, covering the new frequency range between 47.2- 48.2 GHz for NR.
|
38.851
|
User Equipment (UE) Further enhancements of NR RF requirements for frequency range 2 (FR2)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.851/38851-h00.zip
|
The present document is a technical report for Rel-17 WI Further enhancements of NR RF requirements for frequency range 2 (FR2).
|
38.852
|
Introduction of 1900MHz NR band for Europe for Rail Mobile Radio (RMR)
|
TR
|
17.5.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.852/38852-h50.zip
|
The present document is a technical report deals with the use of the Rail Mobile Radio spectrum in the 1900MHz frequency band in CEPT countries which are subject to the ECC Decision (20)02 [1] for the use by the railways. The purpose is to gather the relevant background information and studies in order to address all the necessary precautions to make the unpaired spectrum of 1900-1910MHz usable for 5G NR.
|
38.853
|
Introduction of 900MHz NR band for Europe for Rail Mobile Radio (RMR)
|
TR
|
17.5.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.853/38853-h50.zip
|
The present document is a technical report deals with the use of the Rail Mobile Radio spectrum in the 900 MHz frequency band in CEPT countries which are subject to the ECC Decision (20)02 [1] for the use by the railways. The purpose is to gather the relevant background information and studies in order to address all the necessary precautions to make the paired spectrum of 874.6-800/919.4-925 MHz usable for 5G NR.
|
38.857
|
Study on NR positioning enhancements
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.857/38857-h00.zip
|
The present document captures the findings of the study item "Study on NR positioning enhancements" [2]. The purpose of this technical report is to document the requirements, additional scenarios, evaluations and technical proposals treated during the study and provide a way forward toward enhancements to NR positioning in TSG RAN WGs.
|
38.860
|
Study on extended 600MHz NR band
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.860/38860-h00.zip
|
The present document is a technical report for the study item of APT 600 MHz NR FDD band.
|
38.861
|
Study on high power UE (power class 2) for one NR FDD band
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.861/38861-h00.zip
|
The present document is a technical report for Study on high power UE (power class 2) for one NR FDD band. The study includes the SAR scheme(s), interference issues, UE implementation issues, and system performance evaluations.
The example bands used for the study are NR band n1 and n3.
|
38.862
|
Study on band combination handling in RAN4
|
TR
|
17.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.862/38862-h20.zip
|
The present document is a technical report on band combination handling and rule collection for RAN4 specifications. The purpose is to create a document to collect the rules of band combinations, which can be widely known not only by RAN4 but also by other 3GPP working groups or even by other industrial partners outside 3GPP. It aims to improve the band combination in the current RAN4 specifications and collect the rules what RAN4 has been achieved during the timescale of Rel-17.
This TR contains a band combination specific part. The agreements on the rules of specifying band combinations, and facilitate understanding of the complex notations of CA/DC combinations are provided.
|
38.868
|
Study on optimizations of pi/2 BPSK uplink power in NR
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.868/38868-h00.zip
|
This document is a technical report for optimization of pi/2 BPSK NR uplink power in Rel-17. The purpose is to evaluate the feasibility of increasing the UE’s uplink power in TDD bands for pi/2 BPSK modulation assuming use of existing UE power classes as indicated per band or band combination. The objectives are applicable to FR1 TDD bands n34, n39, n40, n41, n77, n78 and n79. The justification and objectives of this work item are outlined in section 4.1 and section 4.2.
|
38.875
|
Study on support of reduced capability NR devices
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.875/38875-h00.zip
|
This document captures the findings from the study item "Study on support of reduced capability NR devices" [2].
The study includes identification and study of potential UE complexity reduction techniques and UE power saving and battery lifetime enhancements for reduced capability UEs in applicable use cases, functionality that will enable the performance degradation of such complexity reduction to be mitigated or limited, principles for how to define and constrain such reduced capabilities, and functionality that will allow devices with reduced capabilities to be explicitly identifiable to networks and networks operators and allow operators to restrict their access if desired.
The scope of the study includes support for all FR1/FR2 bands for FDD and TDD and coexistence with Rel-15/16 UEs. This study focuses on SA mode and single connectivity. The scope of the study does not include LPWA use cases.
|
38.890
|
Study on NR QoE (Quality of Experience) management and optimizations for diverse services
|
TR
|
17.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.890/38890-h00.zip
|
The present document captures the results of study on NR QoE management and optimizations for diverse services in RP-193256 [2]. It identifies to study the framework for triggering, configuring, collection and reporting of NR QoE measurement and study the potential impact on the related interface (e.g. F1, NG, Xn interface).
|
21.916
|
Release 16 Description; Summary of Rel-16 Work Items
|
TR
|
16.2.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.916/21916-g20.zip
|
The present document provides a summary of each Release 16 Feature or, whenever needed, of each significant Work Item.
The information provided in the present document is limited to an overview of each Feature, explaining briefly its purpose and the main lines of the system's behaviour to execute the Feature.
More information is available by consulting the 3GPP Portal web site, as explained in "Annex C: Process to get further information" and in the introduction section.
|
22.804
|
Study on Communication for Automation in Vertical domains (CAV)
|
TR
|
16.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.804/22804-g30.zip
|
The present document focuses on 5G communication for automation in vertical domains. This is communication that is involved in the production of and working on work pieces and goods, and/or the delivery of services in the physical world. Such communication often necessitates low latency, high reliability, and high communication service availability. Nevertheless, other types of communication are also possible in this area. Moreover, communications with low latency, high reliability, and high communication service availability, and other, not so demanding communication services, may run in parallel on the same 5G infrastructure.
The present document identifies stage 1 potential requirements for 5G communication for automation in vertical domains. The potential requirements are derived from different sources:
- existing work on dependable communication as used in vertical domains; see, for instance, IEC 61907 [2];
- use cases describing network operation in vertical domains with, for instance, common usage of the network (multi-tenancy) and network monitoring for assurance of service level agreements;
- security mechanisms already used in vertical domains; supporting the specific security requirements of vertical domains;
- new (additional to already existing stage-1 work), representative use cases in different vertical domains based on input from relevant vertical interest organisations and other stakeholders.
Furthermore, the present document provides an overview of relevant communication concepts for automation in vertical domains from the point of view of 5G systems. This overview is provided in order to facilitate the mapping between communication for automation in vertical domains and communication in 5G systems.
|
22.819
|
Feasibility Study on Maritime Communication Services over 3GPP system
|
TR
|
16.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.819/22819-g20.zip
|
The present document aims to support the maritime communication services between users ashore and at sea or between vessels at sea over 3GPP system that are targeted to improve maritime safety, protect the maritime environment and promote the efficiency of shipping by reducing maritime casualty caused by human error, in particular, involving small ships and fishing vessels. In addition, the outcome of the technical report is expected to narrow the information gap between mobile users on land and shipboard users on vessels at sea by making it possible to provide the mobile broadband services.
The document describes use cases and potential requirements for services between shore-based users such as authorities and shipboard users in the maritime radio communication environment over 3GPP system. In addition, it deals with use cases to support Mission Critical Services between authorities on land and authorities at sea (e.g. maritime police) as well as use cases to support the interworking between 3GPP system and the existing/future maritime radio communication system for the seamless service of voice communication and data communication between users ashore and at sea or between vessels at sea.
Analysis is also made on which legacy services and requirements from the existing 3GPP system need to be included and which potential requirements need additional work for new functions to support maritime communication services over 3GPP system.
|
22.821
|
Feasibility Study on LAN Support in 5G
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.821/22821-g10.zip
|
The present document describes new use cases and potential requirements applicable to the 5G system for a 3GPP network operator to support 5G LAN-type services over the 5G system (i.e. UE, RAN, Core Network, and potential application to manage the LAN-style service). In this context, 5G LAN-type services with 5G capabilities (e.g. performance, long distance access, mobility, security) allow a restricted set of UEs to communicate amongst each other.
|
22.822
|
Study on using satellite access in 5G
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.822/22822-g00.zip
|
TS 22.261 (Service requirements for next generation new services and markets) requires that the 5G system shall be able to provide services using satellite access. It further specifies that the 5G system shall support service continuity between land based 5G access and satellite based access networks owned by the same operator or by an agreement between operators.
The present document presents the results of a study on using satellite access in 5G. Use cases for the provision of services when considering the integration of 5G satellite-based access components in the 5G system are identified. This leads to the associated identification of existing / planned, as well for new, services and the corresponding modified or new requirements. The requirements on set-up / configuration / maintenance of the features of UE’s when using satellite components combined with other components from the 5G system are addressed as well as regulatory requirements when moving to (or from) satellite from (or to) terrestrial networks
|
22.823
|
Study on enhancements to IMS for new real time communication services
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.823/22823-g10.zip
|
The present document aims to develop high-level use cases and identify the related potential requirements to enable IMS to support new real time communication services.
IMS enhancements for the following scenarios are studied in this document:
• one to many communication (e.g. live broadcast video service in a stadium, concert, etc.) with efficient media negotiation;
• interworking for a UE to communicate with non-sip devices (e.g. camera), and delivery of information to control functions of the non-sip devices (e.g. PTZ);
• fast IMS call setup time for Group Communication;
• enhancements on voice & video communications for supporting AR/VR;
• network slicing for IMS;
• service visibility and usage;.
• services using AI (voiceprint) in RTC.
|
22.824
|
Study on 5G message service for MIoT
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.824/22824-g00.zip
|
The present document develops use cases of message communication for MIoT, identifies 5G Message (5GMSG) service potential requirements, and identifies potential requirements on 5G system. The use cases include the following scenarios:
- Efficient message communication
- Low delay message communication
- Group message communication
- Multicast and broadcast message communication
- High density of UEs message communication
It also provides a gap analysis between the new requirements of message communication for MIoT and the existing operator’s message services/3GPP network capabilities, and recommends the future work for the standardization of 5GMSG service for MIoT.
|
22.825
|
Study on Remote Identification of Unmanned Aerial Systems (UAS)
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.825/22825-g00.zip
|
The present document identifies the use cases and documents the derived potential requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription.
|
22.830
|
Study on business role models for network slicing
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.830/22830-g10.zip
|
The present document examines the business role models for network slicing in order to identify potential requirements that will enable a 3GPP system to adequately support those models, including:
Business role models for network slicing,
Trust relationships between MNOs and 3rd parties under various business role models,
Security relationships based on business role models,
Relationship of business role models with slice characteristics (e.g., slice scalability, slice flexibility), and
3GPP enhancements needed to support the business role models for slices.
|
22.833
|
Study on Enhancement of LTE for Efficient delivery of Streaming Service
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.833/22833-g00.zip
|
The present document describes the use cases and provides gap analysis for identifying potential requirements for optimization of both Over-The-Top and operator managed streaming service considering new business models and existing well-known technologies e.g. caching (UE caching, in-network caching, internet CDN caching), content-aware service delivery, hybrid broadcast and unicast delivery, delay tolerate delivery (using the spare resource and/or delivery in non-busy time/hour), enhanced network sharing which covers the case that the streaming content is provided by shared RAN.
|
22.869
|
Feasibility study on enhancements of Public Warning System (PWS)
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.869/22869-g10.zip
|
The present document describes new use cases and potential requirements applicable to Public Warning Services for
- UEs with diverse form-factors whose user interface is different from the conventional mobile phones; and
- UEs that are defined by applying 3GPP system to non-ICT industry businesses (e.g. vehicles or machines such as IoT devices or robots) and have the different UE role from what 3GPP has traditionally assumed.
In addition, it considers the improvement of the understandability of the PWS message e.g. displaying language independent or graphical content to users, especially foreigners who might not understand the language used in the text or people with physical disability who may be sight impaired and unable to read the text. So it deals with user interface related potential requirements to address the presentation of the warning message considering circumstances such as language being used (e.g. international roaming scenario where the user does not understand the local language) or users with disability (e.g. people with vision impairment).
The present document does not cover use cases or potential requirements for US WEA and Japan ETWS so the results of this document are not applicable for US and Japan. This document considers national variants of EU-Alert and KPAS related service scenarios and potential requirements.
|
22.872
|
Study on positioning use cases
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.872/22872-g10.zip
|
This technical report relates to a study on positioning use cases for both outdoor and indoor environments. It analyses positioning use cases and complements existing work on 5G use cases involving positioning needs in order to identify potential requirements for 5G positioning services.
This document also identifies new use cases, their scope and environment of use along with the related KPIs. For use cases already addressed (fully or partially) in other 3GPP studies, it consolidates and validates the KPI and assumptions.
The document further develops the identified use cases by providing some considerations on the suitability of positioning technologies to these use cases. These considerations support the identification of potential requirements that can be achieved with 3GPP positioning technologies or with a combination of 3GPP and non-3GPP positioning technologies. The use cases and performance targets are independent of specific solutions even though, in order to support these considerations, the report provides some illustrative allocation between existing positioning technologies and 3GPP new positioning technologies (e.g. NR-based).
|
22.886
|
Study on enhancement of 3GPP support for 5G V2X services
|
TR
|
16.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.886/22886-g20.zip
|
The objective of this document is to identify use cases and potential service requirements to enhance 3GPP support for V2X service in the following areas:
- Support for non-safety V2X services (also, referred to as "comfort service") (e.g. connected vehicle, mobile high data rate entertainment, mobile hot-spot/office/home, dynamic digital map update)
- Support for safety-related V2X services (e.g. autonomous driving, car platooning, priority handling between safety-related V2X services and other services)
- Support for V2X services in multiple 3GPP RATs (e.g. LTE, New RAT (NR)) and networks environment, including aspects such as interoperability with non-3GPP V2X technology (e.g. ITS-G5, DSRC, ITS-Connect)
In this document, V2X-related use cases and potential requirements already included in TR 22.891 are considered and new ones are introduced.
The identification of use cases and potential requirements covers both evolved LTE RAT and new 3GPP RAT (e.g. NR) and also covers V2X operation using 3GPP RATs where there are non-3GPP V2X technologies (e.g. ITS-G5, DSRC, ITS-Connect) in use.
|
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.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.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.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.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.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.
|
24.519
|
5G System (5GS); Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3
|
TS
|
16.11.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.519/24519-gb0.zip
|
The present document specifies the protocols of communication between a DS-TT and a TSN AF or a NW-TT and a TSN AF as specified in 3GPP TS 23.501 [2] for:
a) Ethernet port management; and
b) Bridge management.
|
24.883
|
Mission Critical (MC) systems connection to Land Mobile Radio (LMR) systems; Stage-3
|
TR
|
16.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.883/24883-g00.zip
|
The present document provides the protocol details for connecting MCPTT systems to Land Mobile Radio (LMR) systems according to the architectural procedures specified in 3GPP TS 23.283 [80].
The functional entity that provides connection of MCPTT systems to LMR systems over the external interface is the IWF. The IWF is expected to behave as a peer MCPTT system, as further detailed in clause 5 of the present document. The internal function of the IWF is out of scope of 3GPP.
NOTE: The present document will no longer be updated after its approval by plenary. All updates are being done directly to the corresponding technical specifications.
|
24.980
|
Minimum requirements for support of MCPTT service over the Gm reference point
|
TR
|
16.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.980/24980-g00.zip
|
The present document describes a minimum IMS profile of the Gm reference point for SIP core implementation to guide interoperable implementation of MCPTT solutions. In order to support procedures over the SIP-1 reference point defined in 3GPP TS 23.179 [2] and 3GPP TS 24.379 [3], and which exists between the MCPTT UE Signaling User Agent and the SIP core for obtaining access to MCPTT service and supporting MCPTT sessions, the Gm reference point is profiled to meet the minimum requirements to support MCPTT.
The Gm reference point contains many options which are not necessarily applicable for support of MCPTT or options which are alternative mechanisms (e.g. P-CSCF discovery) where if the same option is not supported by both the MCPTT UE and the network interoperability cannot be achieved.
The present document describes the following:
- Where options exist in 3GPP TS 24.229 [4] related to provision of IMS based services over the Gm reference point, those options which need to be supported to ensure interoperable MCPTT service will be identified.
- Where options exist in 3GPP TS 24.301 [5] and stage 2 functionality that are needed to provide MCPTT service over IMS, those options which need to be supported to ensure interoperable MCPTT service will be identified.
- Where optional features of MCPTT are defined that require additional options on the Gm reference point to be supported, these options will also be identified as recommended to be supported to ensure interoperability of the optional feature.
The present document will only cover on-network unicast operation.
The present document covers EPC aspects that are required by MCPTT to establish MCPTT sessions.
|
26.843
|
Codec for Enhanced Voice Services (EVS); Study on non-bit-exact conformance criteria and tools for floating-point EVS codec
|
TR
|
16.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.843/26843-g00.zip
|
The present document provides a study on the Conformance of Non Bit Exact implementation for EVS floating point standard in TS. 26.443. The study focuses on:
- To investigate the behaviour of different implementations of the floating-point reference code (TS 26.443), for example, those built with different versions / settings of various compilers and running on various floating-point architectures.
- To do the investigation using different test material, including clean speech, noisy speech, mixed/music content and taking into account interoperability aspects including floating-point - fixed-point and among various floating-point implementations.
- To identify and propose reliable conformance criteria and methodologies that would be able to reject any undesirable deviation, i.e. bad implementation.
- To develop one or more tools, in the form of scripts or executables, that could be used for determining acceptance/rejection based on the provided conformance criteria.
- To develop any potential additional test vectors that would be needed.
- To propose recommendation(s) on the suitability of the potential new non bit-exact conformance process for 3GPP services (e.g., gives carrier-grade quality).
|
26.850
|
MBMS for Internet of Things (IoT)
|
TR
|
16.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.850/26850-g00.zip
|
The present document studies and evaluates the enhancements at the service layer to support massive file delivery for IoT devices. Devices and network entities operating in the typically constrained environment associated with IoT communications (e.g., processing power, storage, battery life, bandwidth) might support the simplified mechanisms and protocols for MBMS and associated unicast procedures as described in the present document, as opposed to the regular MBMS operations as defined in 3GPP TS 26.346. An IoT device described in the present document could be for instance a NB-IoT device or an eMTC device.
The study considers the enhancements/simplifications in the following areas:
- Define the requirements and constraints for different IoT device categories.
- Review the existing multicast/broadcast service architecture in support of MBMS delivery to IoT devices.
|
26.891
|
5G enhanced mobile broadband; Media distribution
|
TR
|
16.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.891/26891-g00.zip
|
The present document studies the evolution of media distribution with the development of 5G. It addresses the networking and the API aspects that effect the integration in the 5G System.
|
28.803
|
Telecommunication management;Study on management aspects of edge computing
|
TR
|
16.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.803/28803-g01.zip
|
The present document studies how the 3GPP management system can support the management of edge computing management that includes the following aspects:
- The use cases and requirements for 3GPP management system to support the deployment and management of edge computing.
- The solutions for 3GPP management system to support the deployment and management of edge computing.
|
28.804
|
Telecommunication management; Study on tenancy concept in 5G networks and network slicing management
|
TR
|
16.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.804/28804-g01.zip
|
The present document explores how 3GPP management system can provide management capabilities for fulfilling requirements derived from tenancy concepts and use cases, and it also explores how to those management capabilities are exposed to individual tenancy concepts consumers.
The present document investigates the evolution of management features and capabilities due to the identified potential requirements and solutions for tenancy concept.
|
28.805
|
Telecommunication management; Study on management aspects of communication services
|
TR
|
16.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.805/28805-g10.zip
|
The present document specifies potential use cases, requirements and solutions (from the perspective of services based management architecture) for the management of communication services. The document provides conclusions and recommendations on the next steps in the standardization.
|
28.806
|
Study on non-file-based trace reporting
|
TR
|
16.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.806/28806-g10.zip
|
The present document investigates the opportunities for new trace reporting methods. It identifies and documents use cases and potential requirements for non-file-based trace reporting, documents and evaluates potential solutions, and provides recommendations for the normative work aligned with 5G Services Based Management Architecture (SBMA).
|
28.861
|
Telecommunication management; Study on the Self-Organizing Networks (SON) for 5G networks
|
TR
|
16.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.861/28861-g00.zip
|
The present document comprises management use cases, potential requirements and potential solutions of SON for 5G mobile networks.
|
28.890
|
Management and orchestration; Study on integration of Open Network Automation Platform (ONAP) and 3GPP management for 5G networks
|
TR
|
16.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.890/28890-g00.zip
|
The present document studies compatibility of the ONAP management platform architecture and functionality with that of the 5G service-based management architecture being defined in 3GPP TS 28.53x, 28.54x and 28.55x series specifications. The present document is based on ONAP releases up to and including R3 ("Casablanca") and the corresponding APIs and related interfaces.
The scope of the present document includes:
- analysis and comparison of 3GPP and ONAP configuration management mechanisms.
- analysis of how ONAP configuration management mechanisms can be supported in 3GPP.
- analysis and comparison of 3GPP and ONAP alarm management and performance management mechanisms, concentrating on DCAE (Data Collection, Analytics and Events) / Collection Framework event stream and batch data collection on the ONAP side.
- study how notify mechanisms are handled by ONAP DCAE and 3GPP management services.
- study if any gaps exist between the semantics and format of data collected by DCAE and the semantics and format of data produced by both alarm supervision and performance management services.
- analysis of ONAP/3GPP protocol compatibility.
|
29.808
|
Study on the Nudsf Service Based Interface
|
TR
|
16.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.808/29808-g00.zip
|
The present document provides a study of a service based interface to the UDSF. It also evaluates the latency/performance of an SBI based Nudsf and non-SBI based alternatives (if any).
|
29.827
|
Study on Policy and Charging for Volume Based Charging
|
TR
|
16.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.827/29827-g00.zip
|
The present document provides the study on Policy and Charging for Volume Based Charging, which is used to investigate and evaluate possible functional enhancements.
The study shall investigate how to separate the volume usage between different IMS based services (e.g. CAT and voice calls, 3PTY conference, Call waiting, Call Hold).
|
29.843
|
Study on Load and Overload Control of 5GC Service Based Interface
|
TR
|
16.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.843/29843-g00.zip
|
The present document identifies key requirements for the load and overload control on the service based interfaces, identifies the deployment topologies to consider for analysing the solutions for the load and overload control, analyses the 3GPP Release 15 overload control mechanism for the service based interfaces and identifies solutions for addressing the requirements for load and overload control on the service based interfaces.
|
29.890
|
CT WG3 aspects of 5G System Phase 1
|
TR
|
16.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.890/29890-g00.zip
|
The present document discusses and describes requirements, procedures, service interfaces (for service-based architecture) and protocols from CT3 aspects of 5G System as specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [66].
These CT3 aspects include:
- the 5G Policy Framework definition (including new functionalities such as access and mobility management policy support, UE policy support or applicable functionality related to network slicing). Support for non-3GPP access network, handover between non-3GPP access and 3GPP access, roaming aspects and 5G QoS aspects in the scope of the 5G Policy Framework will be part of the study;
- Inter-working with external networks; and
- Network Capability Exposure scenarios (e.g. monitoring and Policy/Charging Capabilities exposure).
The present document is used as a placeholder for CT3 5G System materials to be moved to appropriate 3GPP technical specifications when it is sufficiently stable. As such, neither all the discussions within this document are finished nor the procedures need to be completed. This TR may also contain some empty clauses. This TR will no longer be updated on a systematic manner and therefore contains information may become outdated.
|
29.891
|
5G System - Phase 1 CT WG4 Aspects
|
TR
|
16.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.891/29891-g00.zip
|
The present document analyses the CT4 aspects of the 5G System (5GS) – Phase 1, based on the service requirements defined in 3GPP TS 22.261 [5], the stage 2 system architecture requirements defined in 3GPP TS 23.501 [2] and the stage 2 procedures and flows defined in 3GPP TS 23.502 [3].
These CT4 aspects include the study and selection of the protocols and the definition of the procedures and services that will be used in the 5GS, including:
- the protocol and procedures for User Plane interfaces;
- the protocols, procedures and services for Control Plane interfaces (excluding PCC interfaces);
- the User Plane management procedures over N4;
- the interworking with E-UTRAN connected to EPC;
- specific services in the 5GS (SMS, PWS, LCS, IMS, Emergency Services, MPS, PEI checking);
- numbering, addressing and identification in the 5GS;
- subscriber data in 5GS;
- Network slicing impacts;
- Impacts due to Virtualization.
The present document also helps assessing the appropriate CT4 specifications structure for documenting the CT4 impacts for the 5GS. It is used as a place holder for CT4 5GS materials to be moved to appropriate 3GPP technical specifications when the TR is sufficiently stable.
SA2 or SA3 status is added as a note when unstable topics in SA2 or SA3 are described in this document.
|
29.892
|
Study on User Plane Protocol in 5GC
|
TR
|
16.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.892/29892-g00.zip
|
The present document studies possible candidate protocols for the user plane in 5GC based on Rel-16 stage 2 requirements.
This technical report covers the following analysis:
- List architectural requirements and key issues;
- Identify the possible candidate protocols for user-plane including GTP-U as existing protocol, specified for Rel-15;
- Define a list of evaluation criteria based on Rel-16 stage 2 architecture and procedures to evaluate the candidate protocols;
- Evaluate the candidate solutions against the list of requirements and the potential benefits against the existing user plane solution in 5GS.
The N3 and N6 user plane interfaces are out of the scope of this study. N3 uses GTP-U (see clause 4.3.1 of 3GPP TS 38.300 [12]).
|
32.508
|
Telecommunication management; Procedure flows for multi-vendor plug-and-play eNode B connection to the network
|
TS
|
16.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.508/32508-g00.zip
|
The present document describes the procedure flows between network entities involved in the
multi-vendor plug-and-play eNB connection to network.
These procedures are based on requirements and use cases specified in 3GPP TS 32.501 [4].
The format of the data exchanged in these procedures is defined in 3GPP TS 32.509 [5].
|
32.509
|
Telecommunication management; Data formats for multi-vendor plug and play eNode B connection to the network
|
TS
|
16.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.509/32509-g00.zip
|
The present document describes the data formats used between network entities involved in the multi-vendor plug and play eNB connection to network.
These data formats are based on requirements and use cases specified in 3GPP TS 32.501 [4].
The procedure flows where these data exchanged are defined in 3GPP TS 32.508 [5].
|
32.845
|
Charging management; Study on charging aspects of network slicing
|
TR
|
16.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.845/32845-g00.zip
|
The present document studies the charging aspects of network slicing based on TS 23.501 [201], TS 23.502 [202], TS 28.541 [221], TS 28.530 [203] and TS 28.531 [204] Release15 specifications:
- Charging scenarios and potential requirements for different business and service model (e.g. B2B Services, NSaaS) using network slice.
- The possible charging aspects for network slice management, including the impact on charging architecture charging function and charging procedures.
The stage 1 requirements from TS 22.261 [102] Release 15 and the open issues on network slicing topic that are for further study in TR 32.899 [60] also are considered in this study.
|
33.807
|
Study on the security of the wireless and wireline convergence for the 5G system architecture
|
TR
|
16.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.807/33807-g01.zip
|
The scope of the present document is:
- Study for security between a 5G-RG and 5GC.
- Study for security for a 3GPP UE and non 3GPP UE behind a 5G-RG or a FN RG.
- Study for security for supporting legacy RG. The scope is limited based on the conclusion of the study in TR 23.716 [2].
- Study for security for trusted non-3GPP access.
- The privacy issues in the convergence architecture, if any.
|
33.808
|
KDF negotiation for 5GS security – phase2
|
TR
|
0.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.808/33808-030.zip
|
The scope of this document is the following:
• Study security for allowing KDF negotiation between UE and 5GS network entities
◦ Study the need for KDF negotiation between UE and 5GS network functions, e.g., UE and 5G RAN, UE and SEAF, etc.
◦ Security for potential KDF negotiation procedures between UE and 5GS network functions, e.g., 5G RAN, AMF, SEAF, AUSF, and UDM.
|
33.813
|
Study on security aspects of network slicing enhancement
|
TR
|
16.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.813/33813-g00.zip
| |
33.814
|
Study on the security of the enhancement to the 5G Core (5GC) location services
|
TR
|
16.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.814/33814-g01.zip
|
The scope of the present document is to analyse the security aspects of location service in 5G system and ensure the security solutions are aligned with the work in SA1 (i.e. in TS 22.261 [2] and TR 22.872 [3]) and SA2 (i.e. in TR 23.731 [4]). The work is comprised of the following parts:
- Study the security key issues, threats and requirements of location service in 5G system.
- Elaborate on the potential security solutions to cover these requirements.
Both non-roaming and roaming scenarios will be considered.
|
33.815
|
Study on security aspects of Provision of Access to Restricted Local Operator Services by Unauthenticated UEs (PARLOS)
|
TR
|
16.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.815/33815-g01.zip
|
The present document will examine potential security and privacy threat scenarios enabled by PARLOS, evaluate whether solutions need to be found for these and, if required, identify security solutions and approaches which can mitigate the identified security and privacy threat scenarios while meeting the US regulatory obligations spelled out in the referenced regulations. The present document will make recommendations on the solutions considered.
The present document will consider user notification regarding security and privacy risks when using PARLOS.
The present document will consider the applicability of external security and privacy standards (e.g. Payment Card Industry Data Security Standard) to PARLOS.
|
33.819
|
Study on security enhancements of 5G System (5GS) for vertical and Local Area Network (LAN) services
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.819/33819-g10.zip
|
The present document studies security enhancements to 5GS that are required to fulfil Stage-1 service requirements in vertical domains defined in TS 22.261 [1] and TS 22.104 [2] and addresses the solutions described by TR 23.734 [3] and TR 23.725 [4] studies.
Potential security requirements are provided and possible security architecture enhancements to 5GS in vertical domains are proposed that support these security requirements.
|
33.825
|
Study on the security of Ultra-Reliable Low-Latency Communication (URLLC) for the 5G System (5GS)
|
TR
|
16.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.825/33825-g01.zip
|
The present document:
- Investigates and identifies the security key issues for meeting the low latency requirement.
- Investigates and identifies the security key issues for meeting the ultra-high reliability requirement.
- Provides potential security requirements to address the identified security issues.
- Provides the potential security solutions to support URLLC services.
|
33.834
|
Study on Long Term Key Update Procedures (LTKUP)
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.834/33834-g10.zip
|
The present document is a study on the remote update of 3GPP long term secret keys held in a SIM / USIM.
It:
- Identifies which Long Term Keys should be updatable within this proposed feature.
- Identifies the 3GPP/non 3GPP elements that would be affected by the update of these keys.
- Identifies the Key Issues relating to the updating of long term keys.
- Identifies potential requirements for the updating of long term keys.
- Identifies the applicability of Long Term Key Updating to GSM, UMTS, LTE and 5G and how the requirements may change across these technologies.
- Identifies solutions for the updating of long term keys.
- Evaluates solutions for the updating of long term keys.
- Concludes on the best solutions(s) for the updating of long term keys.
- Makes recommendations for further work.
This study will consider existing and new solutions that can be used for the update of 3GPP Long Term Keys.
The management of subscriptions is out of scope for the present document.
|
33.835
|
Study on authentication and key management for applications based on 3GPP credential in 5G
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.835/33835-g10.zip
|
The present document specifies key issues, derived requirements and potential solutions to support authentication and key management aspects for applications and 3GPP services based on 3GPP credentials in 5G, including the IoT use case. It analyses issues and requirements for:
- providing authentication and key management procedures to applications and 3GPP services in 5G scenarios which allow the UE to securely exchange data with an application server;
- decoupling these procedures from the transport protocol, in order to allow for the adaption to different application layer protocols.
The present document takes into account new solutions as well as potential adaptations to existing ones such as GBA described in TS 33.220 and BEST described in TS 33.163, in order to support the above mentioned requirements with procedures and protocols defined in SBA.
|
33.836
|
Study on security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.836/33836-g10.zip
|
The scope of the present document is to provide security and privacy analysis of eV2X system architecture, derive potential security and privacy requirements, and evaluate security and privacy solutions for protection of it. The security aspects to be considered are as follows:
- Security and privacy for new interfaces in 5G eV2X system architecture, compared to TS 23.285 [2]
- Security and privacy for eV2X unicast over PC5
- Security and privacy for eV2X group communication over PC5
- Other security and privacy issues related to eV2X services, if there is any
|
33.841
|
Study on the support of 256-bit algorithms for 5G
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.841/33841-g10.zip
|
The present document details the following:
- An assessment of threats and potential countermeasures posed due to quantum computing and a resulting assessment of relevant countermeasures in the 5G system.
- An assessment of the timelines for the introduction of any countermeasures, in particular the increase of key lengths to 256 bits. This includes an alignment with the timeline for strengthening asymmetric cryptographic algorithms used in 5G systems.
- An assessment of which parts of the 5G system will be affected and in which way.
- A Study of full entropy 256 bit keys in the 5G key hierarchy, beginning with the permanent pre-shared key. Including a study into modifying the derivation algorithms in order to derive child keys from the 256-bit master key instead of the 128-bit key.
- A study to determine whether a longer MAC is appropriate for 5G.
- A study of the coexistence of different size keys. In 3GPP networks, 256-bit keys in 5G will need to coexist with 128-bit keys in legacy networks or earlier 5G phases. This includes storage of keys and separate key derivation algorithms both on the UE and in the core network.
- A study into the desired number of 256-bit algorithms, e.g. if two 256-bit AKA key generation algorithm sets are needed.
- A study of the desired performance aspects for the new 256-bit algorithms taking into account software and hardware aspects.
- A study of key size negotiation.
- A study into whether the current methods for distribution and refresh of security keys are equally applicable to larger key sizes and can remain the same.
- A study into the Encryption and integrity algorithms that could be needed. This includes 256-bit session/intermediate keys in 5G, may, in some cases, simply entail using larger-key versions of current algorithms, while in other cases new algorithms may need to be chosen altogether.
- Recommendations for suitable requirements for the needed algorithms for use with 256-bit keys and ask ETSI SAGE to provide those algorithms.
|
33.855
|
Study on security aspects of the 5G Service Based Architecture (SBA)
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.855/33855-g10.zip
|
3GPP TS 23.501 [2] defines 5G services with a new service based architecture (SBA) approach.
The present document reviews the interactions in this new architecture, determines key issues relating to the security of SBA elements and interfaces, details potential solutions and recommends normative work .
|
33.856
|
Study on security aspects of single radio voice continuity from 5G to UTRAN
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.856/33856-g10.zip
|
The present document studies the security aspects of single radio voice continuity from 5G to UTRAN CS. In particular, the goal of the present document is to study the impacts on 3GPP security architecture which may result from 5GS to UTRAN CS voice continuity, e.g. security context mapping from 5G and UTRAN, security procedure for the emergency call, etc.
|
33.861
|
Study on evolution of Cellular Internet of Things (CIoT) security for the 5G System
|
TR
|
16.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.861/33861-g10.zip
|
The present document studies the following:
- Capture massive MTC related 5G requirements in other 3GPP documents and further analyse them from security point of view.
- Study security for supporting EPS CIoT/MTC functionalities in 5GS, e.g.:
- security for infrequent and frequent small data transmission
- security for inter-RAT mobility to/from NB-IoT or modifications in the EPC-5GC interworking security specific to CIoT.
- Study security enhancements based on the architectural study in TR 23.724 [2], e.g.:
- security for transport of user plane over 5G NAS; or
- termination of user plane security in 5GC.
- Study the security aspects of the architectural enhancements addressing the 5G service requirements in TS 22.261 [3] and TR 38.913 [4].
- Study the need for additional mechanisms to improve protection of the network from maliciously behaving IoT devices
|
34.121-1
|
User Equipment (UE) conformance specification; Radio transmission and reception (FDD); Part 1: Conformance specification
|
TS
|
16.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.121-1/34121-1-g20.zip
|
The present document specifies the UTRA measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode. In addition it specifies conformance testing of RRM requirements for support of E-UTRA when the UE operates in UTRA mode.
NOTE: Conformance testing of RRM requirements for support of UTRA when the UE operates in E-UTRA mode are specified in TS 36.521-3 [38].
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "definition and applicability" part of the test.
For example only Release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself.
|
36.579-1
|
Mission Critical (MC) services over LTE; Part 1: Common test environment
|
TS
|
16.8.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-1/36579-1-g80.zip
|
The present document defines the common test environment required for testing Client and Server implementations for compliance to the Mission Critical Services protocol requirements defined by 3GPP.
It contains definitions of reference conditions and test signals, default messages and other parameters, generic procedures, and, common requirements for test equipment with the goal for facilitating testing in general and test procedures specification in particular. Various parts of its content are referred to from other parts of the Mission Critical Services protocol conformance testing specification e.g. TS 36.579-2 [2] , TS 36.579-3 [3], 3GPP TS 36.579-6 [84], 3GPP TS 36.579-7 [85].
The present document does not define the common test environment required for testing the implementation of the underlying RRC/NAS protocols, i.e. the bearers used for transport of the Mission Critical Services signalling and media. This is defined in TS 36.508 [6] and referred to from the present document whenever needed.
In regard to default messages or other information elements contents, the present document refers to content defined in requirements specifications specified by 3GPP or other organisations.
|
36.579-2
|
Mission Critical (MC) services over LTE; Part 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specification
|
TS
|
16.8.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-2/36579-2-g80.zip
|
The present document specifies the protocol conformance testing for testing a MCPTT Client for compliance to the Mission Critical Push To Talk (MCPTT) over LTE protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCPTT Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 36.579-1 [2];
- Implementation Conformance Statement (ICS) TS 36.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 36.579-5 [5];
- the applicability of each test case TS 36.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCPTT data sent or received by the MCPTT Client and which are required to be supported by the UE in which the MCPTT Client is installed. This is defined in TS 36.523-1 [6].
|
36.579-4
|
Mission Critical (MC) services over LTE; Part 4: Test Applicability and Implementation Conformance Statement (ICS) proforma specification
|
TS
|
16.8.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-4/36579-4-g80.zip
|
The present document provides the Implementation Conformance Statement (ICS) proforma for testing Client or Server implementations for compliance to the Mission Critical Services over LTE protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [7] and ISO/IEC 9646-7 [8].
The present document specifies the recommended applicability statement for the test cases included in 3GPP TS 36.579-2 [3] and 3GPP TS 36.579-3 [4], as well as, TS 36.579-6 [3] and 3GPP TS 36.579-7 [4]. These applicability statements are based on the features implemented in the Client or the Server respectively.
The present document is valid for Mission Critical Services Servers and Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The present document is valid for Mission Critical Video (MCVideo) and Mission Critical Data (MCData) Clients implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document.
The present document does not specify applicability or ICS for protocol conformance testing for the EPS (LTE) bearers which carry the Mission Critical Services data sent or received by the Client and/or the Server. These are defined in TS 36.523-2 [6].
|
36.579-6
|
Mission Critical (MC) services over LTE; Part 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specification
|
TS
|
16.6.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-6/36579-6-g60.zip
|
The present document specifies the protocol conformance testing for testing a MCVideo Client for compliance to the Mission Critical Video (MCVideo) over LTE protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCVideo Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 36.579-1 [2];
- Implementation Conformance Statement (ICS) TS 36.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 36.579-5 [5];
- the applicability of each test case TS 36.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCVideo data sent or received by the MCVideo Client and which are required to be supported by the UE in which the MCVideo Client is installed. This is defined in TS 36.523-1 [6].
|
36.579-7
|
Mission Critical (MC) services over LTE; Part 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specification
|
TS
|
16.7.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-7/36579-7-g70.zip
|
The present document specifies the protocol conformance testing for testing a MCData Client for compliance to the Mission Critical Data (MCData) over LTE protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCData Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 36.579-1 [2];
- Implementation Conformance Statement (ICS) TS 36.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 36.579-5 [5];
- the applicability of each test case TS 36.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCData data sent or received by the MCData Client and which are required to be supported by the UE in which the MCData Client is installed. This is defined in TS 36.523-1 [6].
According to 3GPP drafting rules, the references clause shall list only documents that are explicitly mentioned in the deliverable. This reference is not used within the document and thus shall be removed from references clause.
|
36.579-8
|
Mission Critical (MC) services over LTE; Part 8: Mission Critical Video (MCVideo) Server Application conformance specification
|
TS
|
0.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-8/36579-8-010.zip
|
The present document specifies the protocol conformance testing for testing a MCVideo Server for compliance to the Mission Critical Video (MCVideo) over LTE protocol requirements defined by 3GPP. The present document addresses only MCVideo Server-Client, and, MCVideo Server-Server communication scenarios. It does not cover e.g. MCVideo Server-EPS, MCVideo Server-SIP Core, etc. scenarios which involve interfaces which implementation may widely vary.
In particular the present specification contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCVideo Servers implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 36.579-1 [2];
- Implementation Conformance Statement (ICS) TS 36.579-4 [5] and Implementation eXtra Information for Testing (IXIT) TS 36.579-5 [6];
- the applicability of each test case TS 36.579-4 [5].
The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCVideo data sent or received by the MCVideo Server. The specification of such testing is out of the scope of RAN5.
|
36.579-9
|
Mission Critical (MC) services over LTE; Part 9: Mission Critical Data (MCData) Server Application conformance specification
|
TS
|
0.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-9/36579-9-010.zip
|
The present document specifies the protocol conformance testing for testing a MCData Server for compliance to the Mission Critical Data (MCData) over LTE protocol requirements defined by 3GPP. The present document addresses only MCData Server-Client, and, MCData Server-Server communication scenarios. It does not cover e.g. MCData Server-EPS, MCData Server-SIP Core, etc. scenarios which involve interfaces which implementation may widely vary.
In particular the present specification contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCData Servers implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 36.579-1 [2];
- Implementation Conformance Statement (ICS) TS 36.579-4 [5] and Implementation eXtra Information for Testing (IXIT) TS 36.579-5 [6];
- the applicability of each test case TS 36.579-4 [5].
The present document does not specify the protocol conformance testing for the EPS (LTE) bearers which carry the MCData data sent or received by the MCData Server. The specification of such testing is out of the scope of RAN5.
|
36.716-01-01
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Advanced intra-band Carrier Aggregation (CA) Rel-16 for x CC Down Link (DL) / y CC Up Link (UL) including contiguous and non-contiguous spectrum (x >= y)
|
TR
|
16.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.716-01-01/36716-01-01-g00.zip
|
The present document is a technical report for Intra-band Carrier Aggregation Rel-16 for xDL/yUL including contiguous and non-contiguous spectrum under Rel-16 time frame. The purpose is to gather the relevant background information and studies in order to address Intra-band Carrier Aggregation requirements for the Rel-16 band combinations in Table 1-1 and Table 1-2.
Table 1-1: Release 16 Intra-band carrier contiguous aggregation combinations
CA combination
CA_3DL_41D_3UL_41D_BCS0
CA_4DL_41E_3UL_41D_BCS0
CA_5DL_41F_3UL_41D_BCS0
CA_2DL_48C_2UL_48C_BCS0
CA_3DL_48D_2UL_48C_BCS0
CA_4DL_48E_2UL_48C_BCS0
CA_2DL_48B_1UL_48A_BCS0
CA_2DL_48B_1UL_48B_BCS0
Table 1-2: Release 16 Intra-band carrier non-contiguous aggregation combinations
CA combination
CA_3DL_48A-48C_2UL_48C_BCS0
CA_4DL_48C-48C_2UL_48C_BCS0
48C-48A-48A_1UL_48A_BCS0
42A-42A_BCS1
42A-42C_BCS1
42C-42C_BCS1
42A-42C_UL_42C_BCS1
42C-42C_UL_42C_BCS1
CA_66A-66B_UL_66B
CA_2DL_48A-48B_1UL_48A_BCS0
CA_2DL_48B-48B_1UL_48A_BCS0
CA_2DL_48B-48C_1UL_48A_BCS0
CA_2DL_48B-48D_1UL_48A_BCS0
CA_2DL_48B-48E_1UL_48A_BCS0
CA_2DL_48A-48B_1UL_48B_BCS0
CA_2DL_48B-48B_1UL_48B_BCS0
CA_2DL_48B-48C_1UL_48B_BCS0
CA_2DL_48B-48D_1UL_48B_BCS0
CA_2DL_48B-48E_1UL_48B_BCS0
This TR contains a band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.