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
|
|---|---|---|---|---|---|---|
23.700-20
|
Study on enhanced support of Industrial Internet of Things (IIoT) in the 5G System (5GS)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-20/23700-20-h00.zip
|
Study enhancements to the 5G System that would enable enhanced support of IEEE TSN Time Sensitive Communication to support deterministic applications.
|
23.700-24
|
Study on support of the 5G MSG (Message) Service
|
TR
|
17.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-24/23700-24-h10.zip
|
The present document studies solutions to satisfy the requirements for MSGin5G Service (message service for MIoT over 5G System). This TR will study the application architecture needed to support MSGin5G service over 5G system, based on the stage 1 requirements specified in 3GPP TS 22.262 [2].
|
23.700-40
|
Study on enhancement of network slicing; Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-40/23700-40-h00.zip
|
GSMA 5GJA has introduced in document NG.116 [3] the concept of Generic Network Slice Template (GST) from which several Network Slice Types (NESTs) can be derived by assigning values to applicable attributes defined in the GST.
This study aims at identifying the gaps that need to be filled in providing support in the specifications owned by SA WG2 for the Generic Network Slice Template (GST) attributes.
|
23.700-91
|
Study on enablers for network automation for the 5G System (5GS); Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-91/23700-91-h00.zip
|
The purpose of this Technical Report is to study enhancements for analytics and NWDAF for the following objectives:
- Remaining key issues from Release 16: UE driven analytics; How to ensure that slice SLA is guaranteed; Which data from UPF can be used by NWDAF (e.g. applications, other user data characteristics);
- NWDAF architecture enhancements: Multiple NWDAF Instances in one PLMN including hierarchies, roles and inter-NWDAF instance cooperation;
- NWDAF features enhancement: Enabling real-time or near real-time NWDAF communication, including mechanism for data collection; Service MOS based NWDAF-Assisted UP Optimization; Minimization of the load generated by NWDAF data collection;
- New Use Cases/key issues: Interaction between NWDAF and ML Model & Training Service owned by the operator.
|
23.700-93
|
Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture; Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-93/23700-93-h00.zip
|
This Technical Report investigates following aspects for UEs that can establish a MA PDU Session to 5GC over both 3GPP and non-3GPP accesses:
- Whether and how to support additional steering mode(s), with potential PMF extensions if needed.
- Whether and how to support additional steering functionality(ies). Proposed solutions shall be based on IETF protocols or extension of such protocols (i.e. QUIC/MP-QUIC).
- Whether and how to support multi-access PDU session with one 3GPP access leg over EPC and the other access leg over non-3GPP access 5GS.
|
23.737
|
Study on architecture aspects for using satellite access in 5G
|
TR
|
17.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.737/23737-h20.zip
|
The scope of this Technical Report is to study:
- The identification of impact areas of satellite integration in the 5GS, when considering TR 22.822 [2] use cases.
- The identification of solutions to adjust the 5G system for the impact impacts areas for the reference use cases:
- Roaming between terrestrial and satellite networks.
- 5G Fixed Backhaul between Satellite Enabled NR-RAN and the 5G Core.
- The resolution of RAN & CN inter-related issues.
|
23.744
|
Study on location enhancements for mission critical services
|
TR
|
17.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.744/23744-h10.zip
|
The present document identifies the impact of location requirements from stage 1 that have yet to be realized within the stage 2 MC services architecture, and to propose solutions and enhancements where needed to fulfil these requirements.
Based on any gaps found between stage 1 service level requirements and existing MC location architecture, the present document consists of a technical report that includes: identification of key issues and gaps with the existing location architecture as specified in 3GPP TS 23.379 [6], 3GPP TS 23.280 [7], 3GPP TS 23.281 [8], and 3GPP TS 23.282 [9]; associated solutions for enhancements to existing MC location architecture; and corresponding evaluations and conclusions.
The location enhancements considered in the present document are limited to MC services over EPS.
|
23.745
|
Study on application layer support for Factories of the Future in 5G network
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.745/23745-h00.zip
|
The present document is a technical report which identifies the application architecture aspects to support Factories of the Future in 5G network, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of application layer support for Factories of the Future in 5G network.
The study takes into consideration the existing work including stage 1 requirements in 3GPP TS 22.261 [2] and 3GPP TS 22.104 [3], and provides recommendation for normative work.
|
23.748
|
Study on enhancement of support for Edge Computing in 5G Core network (5GC)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.748/23748-h00.zip
|
The Technical Report studies and performs evaluations of potential architecture enhancements to support Edge Computing (EC) in the 5G Core network (5GC). Specifically, two objectives are included:
Objective 1: To study the potential system enhancements for enhanced Edge Computing support, including:
- Discovery of IP address of application server deployed in Edge Computing environment;
NOTE 1: This study will not consider application layer solutions.
- 5GC enhancements to support for seamless change of application server serving the UE;
- How to efficiently (with a low delay) provide local application servers with information on e.g. the QoS condition of the data path;
- Supporting for traffic steering in N6-LAN deployed in Edge Computing environment, including support for end-user traffic sent to the central N6 interface to the DN after having been processed by local application server(s);
NOTE 2: The output of the traffic steering related study should cover common N6-LAN deployment, considering the additional features for N6-LAN deployed in Edge Computing environment.
- Supporting PSA change when the application server does not support notifications of UE IP address change;
- Supporting I-SMF insertion or reselection based on AF request to route the traffic to application server deployed in Edge Computing environment.
Objective 2: To provide deployment guidelines for typical Edge Computing use cases, e.g. URLLC, V2X, AR/VR/XR, UAS, 5GSAT, and CDN etc, including:
- Deployment guidelines based on the existing Rel-15/16 Edge Computing enablers, such as LADN, in TS 23.501 [2] and TS 23.502 [3];
- Additional deployment guidelines related to any 5GS Edge Computing enhancements defined as part of the first objective.
|
23.752
|
Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.752/23752-h00.zip
|
The objective of this Technical Report is to identify and evaluate architecture enhancements of 5G System design needed to support proximity based services based on SA WG1 requirements defined in TS 22.278 [2], TS 22.261 [3] and TS 22.115 [4] and determine which of the solutions can proceed to normative specifications.
|
23.754
|
Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking
|
TR
|
17.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.754/23754-h10.zip
|
This study item shall address the following system enablers for supporting Unmanned Aerial Systems Connectivity, Identification, and Tracking:
- a mechanism for Unmanned Aerial Vehicles (UAV) controller and UAV(s) identification and tracking in the 3GPP system;
- this includes how the 3GPP system can provide support for UAV to ground identification (e.g. to authorized third parties such as police devices);
- a mechanism to support UAV controller and UAV(s) authorization and authentication by UTM;
- a mechanism to handle unauthorized UAVs and revocation of authorization (e.g. lack of connectivity to carry the UAV command and control messages, denied registration, etc.) that enables the system to keep track of and control UAV(s).
|
23.755
|
Study on application layer support for Unmanned Aerial Systems (UAS)
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.755/23755-h00.zip
|
The present document is a technical report which identifies the application architecture aspects to support UAS, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of UAS services and applications over 3GPP systems.
The study takes into consideration the existing stage 1 work within 3GPP related to UAS in 3GPP TS 22.125 [3], 3GPP TS 22.281 [5] and 3GPP TS 22.282 [6]. The study also takes into consideration the related system architecture developed by SA2 in 3GPP TR 23.754 [16]. The recommendations from the study include architecture solutions that may be considered for normative work.
|
23.757
|
Study on architectural enhancements for 5G multicast-broadcast services
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.757/23757-h00.zip
|
This Technical Report studies and evaluates architectural enhancements to the 5G System to address the following objective.
Objective A: Enabling general MBS services over 5GS.
Support general multicast and broadcast communication services, e.g. transparent IPv4/IPv6 multicast delivery, IPTV, software delivery over wireless, group communications and IoT applications, V2X applications, public safety.
|
23.758
|
Study on application architecture for enabling Edge Applications
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.758/23758-h00.zip
|
The present document is a technical report capturing the study on application architecture for enabling edge applications over 3GPP networks. The aspects of the study include identifying architecture requirements (e.g. discovery of edge services, authentication of the clients), supporting application layer functional model and corresponding solutions to enable the deployment of applications on the edge of 3GPP networks, with no impact to edge-unaware applications on the UE and minimal impact to edge-aware applications on the UE.
The study takes into consideration the work done for edge computing in 3GPP TS 23.501 [2] and other related work outside 3GPP.
|
23.761
|
Study on system enablers for devices having multiple Universal Subscriber Identity Modules (USIM)
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.761/23761-h00.zip
|
Editor's note: This clause will describe the scope for this study item.
With the growing usage of Multi-USIM devices in the market 3GPP is considering system enhancements that would allow better support of such devices.
This study item will address the objectives listed in the WID (SP-190248).
|
23.764
|
Study on enhancements to application layer support for V2X services
|
TR
|
17.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.764/23764-h10.zip
|
The present document is a technical report which identifies the enhancements to the application architecture to support V2X services specified in 3GPP TS 23.286 [7].
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to V2X enhancements in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3], 3GPP TS 23.285 [6] and 3GPP TS 23.287 [8], as well as V2X application requirements defined outside 3GPP.
This document will provide recommendations for normative work.
|
23.774
|
Study on mission critical services over 5G multicast broadcast system
|
TR
|
17.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.774/23774-h00.zip
|
The present document is a study of potential new/enhanced capabilities for mission critical communication services utilizing MBMS, to be provided in 5G, and points out key issues, identifies use cases, evaluates potential solutions, proposes enhancements and optimizations and identify requirements applicable to the work in SA6 and/or in other groups.
|
23.776
|
Study on architecture enhancements for 3GPP support of advanced Vehicle-to-Everything (V2X) services; Phase 2
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.776/23776-h00.zip
|
The objective of this Technical Report is to investigate 5G System enhancements based on what has been specified in Rel-16, for enhanced support of V2X operation for pedestrian UEs (i.e. UEs for Vulnerable Road Users), e.g. V2X communication with power efficiency, according to vehicular services requirements defined in TS 22.185 [2] and TS 22.186 [3].
|
23.794
|
Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration
|
TR
|
17.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.794/23794-h00.zip
|
The aim of this Technical Report is to study and specify potential enhancements to the IMS architecture to enable IMS FE to integrate with the 5GC network functions to enable IMS applications to directly leverage the features and capabilities of 5GC.
The specific capabilities of 5GC included in this study:
- In regard to 5GC network slicing; what enhancements (if any) are necessary for IMS to efficiently support devices and networks with multiple slices and different IMS services per slice?
- Should (and How does) IMS leverage the 5GC's support for localized routing of traffic and placement of IMS elements? How do such optimizations impact IMS media bearers, IMS signalling bearers, and IMS functions? How is service continuity provided in presence of localized routing?
- Whether and how can IMS applications and network functions utilize the service based capabilities and service based interfaces of the 5GC (for interactions between the IMS and the 5GC)? Which 5GC functions should be interfaced with IMS using service based interfaces?
|
24.811
|
Study on the support for minimization of service interruption
|
TR
|
17.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.811/24811-h10.zip
|
The present document is to study the stage 2 and the stage 3 aspects for service requirements defined by SA WG1 under SA1 work item MINT (Minimization of Service Interruption), as specified in 3GPP TS 22.011 [2] and 3GPP TS 22.261 [3].
|
24.821
|
Study on PLMN selection for satellite access
|
TR
|
17.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.821/24821-h00.zip
|
This technical report studies the key issues and the respective solutions related to the support for network selection procedure that accommodates 5G systems using satellite radio access networks. The objective is to:
- identify the specifics of the satellite access networks with respect to the legacy 3GPP access networks that are relevant to the PLMN selection procedure; and
- consider the need to modify the legacy PLMN selection procedure to address the identified specifics.
|
26.803
|
Study on 5G Media Streaming Extensions for Edge Processing
|
TR
|
17.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.803/26803-h00.zip
|
The present document is a study of use cases for multimedia processing in the edge and the potential 5G media streaming architecture extensions to enable them.
|
26.805
|
Study on Media Production over 5G NPN Systems
|
TR
|
17.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.805/26805-h01.zip
|
The present document identifies standardization needs and potential standards gaps when using 5G Systems for media production. More specifically the following aspects are addressed in this document:
- To identify the relevant media production use cases (professional, semi-professional, production, contribution), based on existing use-cases from TR 22.827 as well as requirements from TS 22.263, that may benefit from 5G System functionalities. This includes collaboration use cases between media producers and 5G System operators.
- To develop one or several reference media production architectures and to map the variety of different media and control flows (such as uplink video, return video, tally, etc) involved in media production onto 5G System delivery components.
- To identify relevant QoS requirements for media production workflows, including required bit rates, loss rates, formats, latencies and jitter, and to identify their impact on the relevant KPIs for media production workflows (reliability, mean-time-between failure, service-level agreements, etc.).
- To identify relevant 5G System features like NPNs, Network Slicing, QoS classes, network event reporting and assistance, etc. that are useful for media production, and to clarify their usage for media production.
- To identify the suitability of existing media production content delivery protocols, codecs and service layers for 5G System usage, evaluate benefits and gaps, and recommend profiles or extensions in collaboration with organizations that develop and deploy existing protocols and codecs.
- To study media device and network orchestration solutions (such as AMWA NMOS), and their integration/interactions with the 5G exposure framework.
- To collaborate with relevant other 3GPP groups and external organizations (VSF, 5G-MAG, EBU, etc.) on media-related aspects of Media Production use cases.
- To identify potential normative work on media level for media production use cases in 5G Systems.
The document primarily focuses on the usage of 5G Systems including NPNs (both Standalone NPN and Public Network Integrated NPN).
|
26.862
|
Immersive Teleconferencing and Telepresence for Remote Terminals (ITT4RT) Use Cases, Requirements and Potential Solutions
|
TR
|
17.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.862/26862-h00.zip
|
The present document collects information regarding the “support of Immersive Teleconferencing and Telepresence for Remote Terminals” (ITT4RT) in 3GPP MTSI. The primary scope of the present document is the documentation of the following aspects:
- Core use cases and requirements for ITT4RT
- Architectures for ITT4RT
- Potential Solutions for ITT4RT not specified in TS 26.114 or TS 26.223
- Example Signalling flows for ITT4RT
- Selected Solutions as pointer to the TS 26.114 or TS 26.223
|
28.545
|
Management and orchestration; Fault Supervision (FS)
|
TS
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.545/28545-h00.zip
|
The present document specifies use cases and requirements for fault supervision of 5G networks and network slicing.
|
28.807
|
Study on management of Non-Public Networks (NPN)
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.807/28807-h00.zip
|
The present document describes use cases, potential requirements and solutions (from the perspective of services based management architecture) for the management aspects of non-public networks. The present document provides conclusions and recommendations on the next steps for the standardization.
|
28.808
|
Study on management and orchestration aspects of integrated satellite components in a 5G network
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.808/28808-h00.zip
|
The scope of the present document is:
- to identify the main key issues associated with business roles, service and network management and orchestration of a 5G network with integrated satellite component(s) (whether as NG-RAN or non-3GPP access, or for transport), and
- to study the associated solutions.
The present document aims at minimising the impacts and complexity of satellite integration in the existing business models and in management and orchestration aspects of the current 5G networks.
|
28.809
|
Study on enhancement of management data analytics
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.809/28809-h00.zip
|
The present document studies the enhancements of MDA (Management Data Analytics).
In this TR, the MDA use cases and the corresponding potential requirements are identified and documented, and their possible solutions with analytics input and output (report) are developed and evaluated.
The study also captures the MDA functionality and service framework, MDA process, MDA role in management loop and management aspects of MDA.
Moreover, the TR provides recommendations for the normative specifications work in full alignment with SA5 5G Services Based Management Architecture (SBMA).
|
28.810
|
Study on concept, requirements and solutions for levels of autonomous network
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.810/28810-h00.zip
|
The present document describes the background, concept, definition and classification of network autonomy levels, typical scenarios for managing network and service which need autonomous support, the potential requirement and solutions and recommendation for the way forward in normative work.
|
28.811
|
Management and orchestration; Study on Network Slice Management Enhancement
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.811/28811-h00.zip
|
The present document considers the following issues:
- The potential network slice information model and management service enhancements to support cross-operator network slice management use case.
- The potential new management capabilities to support end to end network slicing.
- The potential new management capabilities to support security management of network slice.
|
28.812
|
Telecommunication management; Study on scenarios for Intent driven management services for mobile networks
|
TR
|
17.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.812/28812-h10.zip
|
The present document describes, intent driven management concept, intent driven management scenarios, and recommendation for the way forward on standardization expression of the intent in normative phase. The relation with other automation mechanisms is also addressed in this study.
The present document considers below dimensions when studying Intent driven management. For each dimension the scope is narrowed down to a certain aspect:
1) Users; The study covers the Technical (NOP, NEP) and Techno-Business (CSP)
2) Networks; The study covers the 5G and 4G
3) Operated System; The study covers the Co-ordinated and Complex systems
4) Infrastructure Automation; The study covers more Autonomous and less Automatic
5) Language; The scope covers more declarative and less Imperative
|
28.813
|
Management and orchestration; Study on new aspects of Energy Efficiency (EE) for 5G
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.813/28813-h00.zip
|
The present document investigates the opportunities for defining new Energy Efficiency (EE) KPIs and new Energy Saving (ES) solutions. It identifies and documents key issues related to energy efficiency and energy saving, documents and evaluates potential solutions, and provides recommendations for the normative work.
|
28.814
|
Management and orchestration; Study on enhancements of edge computing management
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.814/28814-h00.zip
|
The present document studies the potential use cases, requirements, and solutions for the management of edge computing architecture and requirement defined by TS 23.558 [2] and TS 23.501 [4]. The document provides conclusions and recommendations on the next steps in the standardization.
|
28.815
|
Study on charging aspects of edge computing
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.815/28815-h00.zip
|
The present document studies the charging aspects of Edge Computing based on:
- architecture, procedures and information flows for enabling Edge Applications over 3GPP network specified in TS 23.558 [4].
- capabilities for 5GS to support edge computing specified in TS 23.501 [3], TS 23.502 [9] and TS 23.503 [10] incorporating enhancements from TR 23.748 [11] conclusions.
The ETSI ISG MEC framework is also considered.
The charging aspects encompasses:
- End user charging when accessing edge applications enabled over 3GPP networks.
- Inter-Provider charging by considering the different business roles (i.e. ASP, ECSP and MNO).
The investigation includes different charging scenarios with potential business requirements, alternative solutions with potential impact on charging architecture, charging functions and charging procedures.
|
28.816
|
Charging management; Study on charging aspects of Cellular Internet Of Things in the 5G System (5GS CIoT)
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.816/28816-h00.zip
|
The present document investigates charging enhancements on 5G data connectivity domain charging, control plane data transfer domain charging and Monitoring Events charging for 5GS CIoT for the corresponding functionalities based on TS 23.501 [3], TS 32.251 [4], TS 32.255 [6], TS 32.253 [7] and TS 32.278 [8]:
- Control Plane CIoT 5GS Optimisation
- Non-IP Data Delivery (NIDD)
- Support for Monitoring Events
- Support of rate control of user data, including small data rate control
- Category M UEs differentiation
- Exception report
|
28.817
|
Management and orchestration; Study on access control for management service
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.817/28817-h00.zip
|
The present document studies access control for management services produced by 3GPP management system.
The document investigates use cases related to access control, proposed requirements on 3GPP management system and possible solutions to support access control.
The document also provides recommendation for the normative specifications work.
|
28.818
|
Study on YANG PUSH
|
TR
|
0.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.818/28818-010.zip
|
This document investigates the possibility, the possible advantages and possible drawbacks of introducing YANG-Push [2],[3] as a 3GPP protocol for CM, FM, PM and Heartbeat.
|
28.822
|
Charging management; Study on charging aspect of 5G LAN-type services
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.822/28822-h00.zip
|
The present document studies the charging aspects of 5G LAN-type service based on TS 23.501 [6] and TS 23.502 [7] specifications:
- Charging scenarios and potential requirements for 5G LAN-type service.
- The possible charging aspects for 5G VN group management and 5G VN group communication, including the impact on charging architecture, charging functions and charging procedures.
The stage 1 charging requirements from TS 22.261 [5] Release 16 on 5G LAN-type service topic are considered in this study.
|
28.825
|
Management and orchestration; Study on management aspects of 5G network sharing
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.825/28825-h00.zip
|
The present document studies on concept, use cases and potential requirements related to the management aspects of MOCN network sharing, and the potential solutions for 5G network sharing management architecture.
|
29.820
|
Study on Best Practice of PFCP
|
TR
|
17.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.820/29820-h00.zip
|
The present document identifies the scenarios where the PFCP interoperability needs to be further enhanced for existing function and specifies the corresponding requirements, identifies the key issues which impact the PFCP interoperability, analyses potential solutions to address the key issues.
PFCP used in 4G (e.g. on Sxa, Sxb, Sxc interfaces) and 5G (e.g. on N4, N16a interfaces) are both within scope of the study.
|
29.821
|
Study on restoration of profiles related to UDR
|
TR
|
17.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.821/29821-h00.zip
|
The present document identifies impacts to services offered to subscribers served by 5GC in case profiles at UDR are corrupted, lost, or became inconsistent, and addresses how the impact can be minimized. The document will focus on the following aspects:
- Clarify the necessity on defining procedures for 5GC to allow NFs, e.g. AMF, SMF, SMSF, NEF, PCF, AUSF to trigger correction and synchronization of temporary data within the UDR in case any corruption, loss, or inconsistency of data in UDR takes place, along with how NFs detect such case;
- Whether similar issue needs to be addressed between other NFs;
- Provide candidate solution(s) to solve the issue; and
- Evaluate the candidate solution(s) and recommend any changes to specifications if identified.
|
29.829
|
Service-based support for SMS in 5GC
|
TR
|
17.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.829/29829-h10.zip
|
The present document identifies the SMS transfer in 5G network based on service-based interfaces, which allow SMSF and UDM to only support the SBI based interfaces in 5GC and avoid resorting to legacy MAP and Diameter interfaces within the PLMN and across PLMNs including roaming scenarios, identifies the key issues that are related to support of Service-based interfaces in 5GC, analyses potential solutions to address the key issues.
|
29.835
|
Study on Port Allocation Alternatives for New 3GPP Interfaces
|
TR
|
17.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.835/29835-h10.zip
|
The present document studies alternative proposals for the port number allocations to the new 3GPP interfaces and applications. The study will focus on, but is not limited to following three alternatives:
- 3GPP allocating port numbers from the Dynamic/Private Port number range [49152 - 65535]. See clause 6 in IETF RFC 6335 [2];
- Operators allocating port numbers from either the User Port number range [1024-49151] or the Dynamic/Private Port number range [49152 - 65535]. See clause 6 in IETF RFC 6335 [2];
- DNS based solution, where port numbers are allocated from the User Port number range [1024-49151] or the Dynamic/Private Port number range [49152 - 65535]. See clause 6 in IETF RFC 6335 [2].
The primary focus of this study is on protocols only used for network internal services, i.e. when the protocol is only used in a single network with no interconnection with other networks or the public Internet. The solutions proposed in the study however could also be used in scenarios in which the protocol is used across multiple networks, e.g. in roaming case or between the RAN and the core network supported by different operator networks.
|
32.846
|
Charging management; Study on charging aspects of Proximity-based Services (ProSe) in 5GS
|
TR
|
17.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.846/32846-h00.zip
|
The present document studies on charging aspects of Proximity-based Services in 5GS based on TS 23.304 [11].
The charging aspects related to the Proximity-based Services in 5GS are covered within the scope:
- Charging architecture, for supporting charging of ProSe Direct Discovery and Direct Communication related to Public Safety and commercial proximity service.
- Charging principles, scenarios and potential requirements related to the ProSe service in 5GS.
- Potential charging solutions for the Proximity-based Services in 5GS.
|
33.818
|
Security Assurance Methodology (SECAM) and Security Assurance Specification (SCAS) for 3GPP virtualized network products
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.818/33818-h10.zip
|
The present document studies the SECAM (Security Assurance Methodology) and SCAS (Security Assurance Specification) for 3GPP virtualised network products based on SECAM and SCAS defined in TR 33.916 [2]. It makes thorough gap analysis between current SECAM/SCAS work in TR 33.916 [2] and SECAM/SCAS work for 3GPP virtualised network products. It also identifies, defines ToE and roles of SECAM/SCAS for 3GPP virtualised network products according to deployment scenarios and decoupling ways. Based on the identified ToE and roles, the present document details the needed change or additional work to current security assurance methodology for the creation, evaluation procedure of related SCAS documents, etc. It studies new threats of the identified ToE and identifies the additional security requirements of the ToE, or/and identifies existing relevant/supporting requirements specified in ETSI NFV specifications or the equivalent. The present document also provides potential new SECAM/SCAS proposals and points out the impact to existing SECAM/SCAS documents (including TR 33.916 [2], TR 33.926 [3], TS 33.117 [4], etc.).
NOTE: SECAM/SCAS of 3GPP virtualised network products in the present document considers only the scenario that 3GPP VNF deployed in the virtual machines.
|
33.824
|
Study on Security for Next Radio (NR) Integrated Access and Backhaul (IAB)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.824/33824-h00.zip
|
The present document:
- Describes potential security threats and vulnerabilities that are applicable to the enhanced IAB architecture specified in the TS 38.300 [3], TS 38.331 [8], TS 38.321 [9] and TS 38.340 [10].
- Identifies potential security requirements for those potential security threats and vulnerabilities.
- Proposes candidate solutions to ensure that the enhanced IAB architecture specified in the 3GPP TS 38.300 [3], TS 38.331 [8], TS 38.321 [9] and TS 38.340 [10] does not introduce security vulnerabilities in the 5G system providing a secure connection for the UEs connecting to the NR through IAB node(s).
- Concludes with the solutions that should be included in a future normative phase.
|
33.839
|
Study on security aspects of enhancement of support for edge computing in the 5G Core (5GC)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.839/33839-h10.zip
|
The present document studies the security enhancements on the support for Edge Computing in the 5G Core network define in TR 23.748 [3], and application architecture for enabling Edge Applications defined in TR 23.758 [4] and TS 23.558 [2].
Potential security requirements are provided and possible security enhancements to 5GS and edge application architecture are proposed that meet these security requirements.
NOTE: The user consent for exposure of information to Edge Applications is addressed in TR 33.867 [20].
|
33.845
|
Study on storage and transport of 5G Core (5GC) security parameters for Authentication Credential Repository Processing Function (ARPF) authentication
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.845/33845-h00.zip
|
The present document details the following:
- The security assumptions relating to security communication in 5G.
- The security assumptions related to protecting subscriber privacy.
- The home network parameters that are relevant to securing the communication in 5G and protecting subscriber privacy.
- Key Issues, threats and requirements relevant to securing the communication in 5G and protecting subscriber privacy.
- Solutions that potentially resolve the key issues described.
The present document does not describe the storage of security parameters in the UE or the serving network or the transportation of secure information between the home network and the serving network.
|
33.846
|
Study on authentication enhancements in the 5G System (5GS)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.846/33846-h00.zip
|
The scope of the present document is the following:
- key issues, potential security requirements and solutions of how to enhance the authentication process to ensure the security of session anchor keys in case the long-term key is leaked.
- key issues, potential security requirements and solutions of how to mitigate the linkability attacks.
- key issues, potential security requirements and solutions of how to mitigate the impacts of potential DDoS threats due to concealing the SUPI.
- key issues, potential security requirements and solution of how to mitigate the leaking of SQN values during AKA re-synchronisation.
|
33.847
|
Study on security aspects of enhancement for proximity based services in the 5G System (5GS)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.847/33847-h10.zip
|
The present document studies the security and privacy aspects of proximity based services (including public safety and commercial proximity services) in the 5G system. It ensures that the security solutions are aligned with the work in TR 23.752 [2], TS 22.278 [3] and TS 22.261 [4]. The present document covers the following issues:
- Security and privacy key issues, threats and potential requirements of proximity based services in 5G system.
- Potential security solutions to cover these potential requirements.
Both roaming and non-roaming scenarios are considered.
|
33.850
|
Study on security aspects of enhancements for 5G Multicast-Broadcast Services (MBS)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.850/33850-h00.zip
|
The present document studies the security of 5G multicast-broadcast services based on FS_5MBS study in TR 23.757 [2]. Potential security requirements are identified and possible security solutions are proposed to address these security requirements.
|
33.851
|
Study on security for enhanced support of Industrial Internet of Things (IIoT)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.851/33851-h10.zip
|
The present document studies the security impact of time sensitive communication aspects in Industrial IoT based on FS_IIoT study in TR 23.700-20 [4] and the architecture described in 3GPP TS 23.501 [3].
|
33.853
|
Study on key issues and potential solutions for integrity protection of the User Plane (UP)
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.853/33853-h00.zip
|
The present document studies the key issues and potential solutions for integrity protecting the user plane, including potential enhancements needed to support UP IP up to the full data rate, in the following combinations as defined in 3GPP TR 38.801 [2] (clause 7.2):
- Option 1 - eUTRA with EPC
- Option 2 - NR standalone with 5G Core
- Option 3 - EPC based Dual Connectivity of eUTRA and NR RAT
- Option 4 - 5G Core based Dual Connectivity (NR master - eUTRA secondary)
- Option 5 - 5G Core with eUTRA
- Option 7 - 5G Core based Dual Connectivity (eUTRA master - NR secondary)
The present document does not detail key issues, solutions, evaluations, conclusions and recommendations for GERAN and UTRAN.
|
33.854
|
Study on security aspects of Uncrewed Aerial Systems (UAS)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.854/33854-h10.zip
|
The present document contains a study on the security aspects of Uncrewed Aerial Systems (UASs). TS 22.125 [2] contains the service requirements for UAS while TR 23.754 [3] is studying aspects like the UAS connectivity, identification and tracking and TR 23.755 [4] studies UAV services and application layer features. The security study of the present document provides key issue including security threat and potential requirements related to the work in these other specifications and develops and analyses solutions to these key issues. Finally the study provides some conclusions for potential normative work.
|
33.857
|
Study on enhanced security support for Non-Public Networks (NPN)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.857/33857-h10.zip
|
The aim of the present document is to study the security aspects for any potential enhancements based on the outcome of the study in TR 23.700-07 [3]. For each of the objectives in the scope of the study in TR 23.700-07 [3], the security aspects that are to be covered in the present document are as follows:
- Enhancements to Support SNPN along with credentials owned by an entity separate from the SNPN
- Study potential solutions for authentication using credentials owned by an entity separate from the SNPN
- UE Onboarding and remote provisioning of non-USIM credentials
- Identify security Key Issues relating to UE Onboarding and remote provisioning with non-USIM credentials
- Identify methods by which the UE can be verified as "uniquely identifiable and verifiably secure"
- Critically review the security aspects of the proposed solutions in TR 23.700-07 [3] and make recommendations for security improvements where required.
- Study potential solutions for the secure provisioning of non-USIM credentials taking into account different deployment scenarios.
NOTE 1: The term USIM in this context denotes the IMSI accompanied by AKA credentials (i.e. for primary authentication with the PLMN).
- Support of IMS voice and emergency services for SNPN:
- Analyse potential security impacts from supporting IMS voice and IMS services in SNPNs. In Rel-16 SNPNs do not support IMS emergency services but for Rel-17 its expected that the enabling of IMS and IMS services for SNPNs is to be studied.
NOTE 2: Key issue 2 in TR 23.700-07 [3] is assumed to not require any study from a security perspective.
|
33.862
|
Study on security aspects of the Message Service for MIoT over the 5G System (MSGin5G)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.862/33862-h10.zip
|
The present document studies the security aspects on the support of the 5GMSG Service defined in TR 23.700-24 [2], determines key issues of potential security requirements and proposed possible security solutions to meet these security requirements.
|
33.864
|
Study on the security of Access and Mobility Management Function (AMF) re-allocation
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.864/33864-h00.zip
|
The present document aims at addressing the case for the indirect reroute procedure for UE registration. The intention is to enable deployment scenarios with stricter slice isolation requirements on the core network, for example where the AMFs are unable to communicate with each other.
The aim of the present document is to:
- Collect the potential requirements related to the AMF re-allocation procedure.
- Study the potential enhancements to the security mechanisms in order to fulfil the requirements for the AMF re-allocation.
|
33.866
|
Study on security aspects of enablers for Network Automation (eNA) for the 5G system (5GS) Phase 2
|
TR
|
17.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.866/33866-h00.zip
|
The present document studies the security aspects of enablers for network automation for the 5G system based on the outcome of TR 23.700-91 [1]. More specifically, the present document identifies security issues, requirements and corresponding potential security solutions related to the following objectives:
- UE data collection protection to fulfil the NWDAF functionalities including privacy consideration, data authenticity, data integrity, and accessibility aspects requirements.
- Detection of cyber-attacks and anomaly events supported by NWDAF and its related functions, specifically to identify parameters provided by UE and NFs, which can help to detect attacks and abnormal behaviours;
- Protection of data transferring (e.g. privacy consideration) in the inter-NWDAF/NWDAF instances.
NOTE: The user consent for UE data collection is not addressed in the present document, it will be discussed in TR 33.867 [2].
|
33.867
|
Study on user consent for 3GPP services
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.867/33867-h10.zip
|
The scope of present document is to identify and evaluate the requirements and solutions to support user consent for 3GPP services while complying with user privacy considerations.
The details are as follows:
- Review TR 33.849 [3] with regards to the concept of user consent for 3GPP users, and identify what types of data collection and conditions under which the support of the user consent is required; then update them if needed.
- Identify target usage scenarios and trust domains.
- Analyse potential security threats and requirements for conditions under which user sensitive data are collected without user consent, and when user consent indication is not protected.
- Identify potential solutions to address the above security requirements.
NOTE 1: Principles, regulations, and definitions related to privacy, which are recognized differently in each different country or area, are taken into account when deriving the concept of user consent for 3GPP users.
NOTE 2: Even where solutions exist to obtain user consent, collection and exposure of user sensitive data should be minimized and only be allowed where critical to the operation of the related feature.
|
33.873
|
Study on the security of the system enablers for devices having Multiple Universal Subscriber Identity Modules (MUSIM)
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.873/33873-h10.zip
|
The present document contains the study of system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) in the EPS and 5G system architecture are studied in 3GPP TR 23.761 [2]. The present document provides the security and privacy issues related to MUSIM architecture and lists potential solutions for identified key issues including.
- Security and privacy issues exposing the Paging Cause in clear text in paging message.
- Security aspects of the communication between UE and Paging Server and exposing Paging server address.
- Security and Privacy implications if a Multi-USIM device needs to explicitly indicate to the MNO owning one USIM and that UE is also registered via another USIM at the same or different PLMNs.
- Security aspects of Paging Response with cause value busy indication.
Finally, the present document provides some conclusions for potential normative work.
|
33.881
|
Study on Non-Seamless WLAN Offload (NSWO) in 5G System (5GS) using 3GPP credentials
|
TR
|
17.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.881/33881-h10.zip
|
The scope of the present document is to support Non-seamless WLAN Offload (NSWO) in 5GS. The following will be studied in this document:
1) Solutions to support NSWO in 5GS.
2) Procedures to support authentication methods for the respective solutions in objective.
3) Maintain privacy of subscription identifier similar to 3GPP/non-3GPP access to 5GC, even for NSWO authentication from WLAN.
|
36.509
|
Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE)
|
TS
|
17.4.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.509/36509-h40.zip
|
The present document defines for User Equipment (UE) in E-UTRA FDD or TDD mode those special functions and their activation/deactivation methods that are required in UE for conformance testing purposes.
This document also describes the operation of these special functions for UEs supporting E-UTRA FDD or TDD mode, when operating in UTRA FDD and TDD mode, in GSM/GPRS mode, and in CDMA2000 mode.
|
36.717-02-01
|
Rel-17 LTE inter-band Carrier Aggregation for 2 bands DL with 1 band UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.717-02-01/36717-02-01-h00.zip
|
The present document is a technical report for 2B DL/1B UL Inter-band Carrier Aggregation under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address 2B DL/1B UL Inter-band Carrier Aggregation requirements for the Rel-17 band combinations in Table 1-1.
Table 1-1: Release 17 2BDL/1BUL inter-band carrier aggregation combinations
CA combination
REL-independent from
CA_48A_53A
Table 3A.2-2 in TS 36.307 [2]
CA_7A-25A
CA_7A-7A-25A
CA_7C-25A
CA_7A-25A-25A
CA_7A-7A-25A-25A
CA_7C-25A-25A
CA_25A-66A
CA_25A-25A-66A
CA_2A-8A
CA_46A_53A
CA_46C_53A
CA_46D_53A
CA_46E_53A
CA_3A-3A-38A
CA_32A-38A
CA_38A-66A
CA_38C-66A
CA_26A-38A
CA_26A-38C
CA_26A-38A
CA_26A-38C
CA_30A_48A
This TR contains a band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.717-02-02
|
Rel-17 LTE inter-band Carrier Aggregation for 2 bands DL with 2 bands UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.717-02-02/36717-02-02-h00.zip
|
The present document is a technical report on LTE inter-band CA for 2 bands DL with 2 bands UL under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address 2 bands DL/2 band UL Inter-band Carrier Aggregation requirements for the Rel-16 band combinations in Table 1-1.
Table 1-1: Release 17 2 bands DL/2 bands UL inter-band carrier aggregation combinations
CA configuration
Uplink configuration
BCS
CA_8A-20A
CA_8A-20A
0, 1, 2
CA_8A-28A
CA_8A-28A
0
CA_3A-38A
CA_3A-38A
0
CA_30A-48A
CA_30A-48A
0
CA_1A-40A
CA_1A-40A
0
CA_1A-40A-40A
CA_1A-40A
0
CA_1A-40C
CA_1A-40A
0
CA_1A-40D
CA_1A-40A
0
CA_28A-40A
CA_28A-40A
0
CA_28A-40A-40A
CA_28A-40A
0
CA_28A-40C
CA_28A-40A
0
CA_28A-40D
CA_28A-40A
0
This TR contains a band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.717-03-01
|
Rel-17 LTE inter-band Carrier Aggregation for 3 bands DL with 1 band UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.717-03-01/36717-03-01-h00.zip
|
The present document is a technical report on inter-band CA for 3 bands DL with 1 band UL under Rel-17 timeframe. The purpose is to gather the relevant background information and studies in order to address 3 bands DL/1 band UL Inter-band Carrier Aggregation requirements for the Rel-17 band combinations in Table 1-1.
Table 1-1: Release 17 3 bands DL/1 band UL inter-band carrier aggregation combinations
CA configuration
Uplink configuration
BCS
This TR contains a band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.717-03-02
|
Rel-17 LTE inter-band Carrier Aggregation for x bands DL (x= 3, 4, 5) with 2 bands UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.717-03-02/36717-03-02-h00.zip
|
The present document is a technical report for LTE-Advanced inter-band carrier aggregation for x bands DL (x=3, 4, 5) with 2 bands UL under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Rel-17 band combinations that are related to x bands (x=3, 4, 5) DL with 2 bands UL CA requirements in Table 1-1, 1-2, and 1-3.
Table 1-1: 3 bands DL/2 bands UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Uplink CA
configuration
E-UTRA Bands
1.4MHz
3
MHz
5
MHz
10 MH
z
15 MHz
20 MHz
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
CA_3C-7A-8A
CA_3A-8A
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
70
0
7
Yes
Yes
Yes
Yes
8
Yes
Yes
CA_1A-3C-38A
CA_1A-3A
1
Yes
Yes
Yes
Yes
80
0
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
38
Yes
Yes
Yes
Yes
CA_3C-8A-38A
CA_3A-8A
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
70
0
8
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_1A-3C-20A
CA_1A-3A
1
Yes
Yes
Yes
Yes
80
0
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
20
Yes
Yes
Yes
Yes
CA_3C-8A-20A
CA_3A-8A
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
70
0
8
Yes
Yes
20
Yes
Yes
Yes
Yes
CA_1A-8A-20A
CA_1A-8A
1
Yes
Yes
Yes
Yes
50
0
8
Yes
Yes
20
Yes
Yes
Yes
Yes
CA_3A-8A-20A
CA_3A-8A
3
Yes
Yes
Yes
Yes
50
0
8
Yes
Yes
20
Yes
Yes
Yes
Yes
CA_1A-8A-38A
CA_1A-8A
1
Yes
Yes
Yes
Yes
50
0
8
Yes
Yes
38
Yes
Yes
Yes
Yes
Table 1-2: 4 bands DL/2 bands UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Uplink CA
configuration
E-UTRA Bands
1.4MHz
3
MHz
5
MH
z
10 MH
z
15 MHz
20 MHz
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
CA_1A-3C-7A-8A
CA_1A-3A
CA_1A-8A
CA_3A-8A
1
Yes
Yes
Yes
Yes
90
0
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
7
Yes
Yes
Yes
Yes
8
Yes
Yes
CA_1A-3C-8A-38A
CA_1A-3A
CA_1A-8A
CA_3A-8A
1
Yes
Yes
Yes
Yes
90
0
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
8
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_1A-3A-8A-20A
CA_1A-3A
CA_1A-8A
CA_3A-8A
1
Yes
Yes
Yes
Yes
70
0
3
Yes
Yes
Yes
Yes
8
Yes
Yes
20
Yes
Yes
Yes
Yes
CA_1A-3C-8A-20A
CA_1A-3A
CA_1A-8A
CA_3A-8A
1
Yes
Yes
Yes
Yes
90
0
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
8
Yes
Yes
20
Yes
Yes
Yes
Yes
CA_1A-3A-20A-38A
CA_1A-3A
1
Yes
Yes
Yes
Yes
80
0
3
Yes
Yes
Yes
Yes
20
Yes
Yes
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_1A-3C-20A-38A
CA_1A-3A
1
Yes
Yes
Yes
Yes
100
0
3
See CA_3C Bandwidth combination set 0 in Table 5.6A.1-1
20
Yes
Yes
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_1A-3A-7A-38A
CA_1A-3A
1
Yes
Yes
Yes
Yes
80
0
3
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_1A-7A-8A-38A
CA_1A-8A
1
Yes
Yes
Yes
Yes
70
0
7
Yes
Yes
Yes
Yes
8
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_3A-7A-8A-38A
CA_3A-8A
3
Yes
Yes
Yes
Yes
70
0
7
Yes
Yes
Yes
Yes
8
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_1A-8A-20A-38A
CA_1A-8A
1
Yes
Yes
Yes
Yes
70
0
8
Yes
Yes
20
Yes
Yes
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_3A-8A-20A-38A
CA_3A-8A
3
Yes
Yes
Yes
Yes
70
0
8
Yes
Yes
20
Yes
Yes
Yes
Yes
38
Yes
Yes
Yes
Yes
Table 1-3: 5 bands DL/2 bands UL CA configurations part of the WI
E-UTRA CA configuration / Bandwidth combination set
E-UTRA CA configuration
Uplink CA
configuration
E-UTRA Bands
1.4MHz
3
MHz
5
MH
z
10 MH
z
15 MHz
20 MHz
Maximum aggregated
bandwidth [MHz]
Bandwidth combination set
CA_1A_3A_7A_8A_38A
CA_1A-3A
CA_1A-8A
CA_3A-8A
1
Yes
Yes
Yes
Yes
90
0
3
Yes
Yes
Yes
Yes
7
Yes
Yes
Yes
8
Yes
Yes
38
Yes
Yes
Yes
Yes
CA_1A_3A_8A_20A_38A
CA_1A-3A
CA_1A-8A
CA_3A-8A
1
Yes
Yes
Yes
Yes
90
0
3
Yes
Yes
Yes
Yes
8
Yes
Yes
20
Yes
Yes
Yes
Yes
38
Yes
Yes
Yes
Yes
This TR contains a general part and band specific combination part and the actual requirements are added to the corresponding technical specifications.
|
36.717-04-01
|
Rel-17 LTE inter-band Carrier Aggregation for x bands DL (x=4, 5) with 1 band UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.717-04-01/36717-04-01-h00.zip
|
The present document is a technical report on inter-band CA for x bands DL (x=4, 5) with 1 band UL under Rel-17 timeframe. The purpose is to gather the relevant background information and studies in order to address 4 or 5 bands DL/1 band UL Inter-band Carrier Aggregation requirements for the Rel-17 band combinations in Table 1-1 and 1-2.
Table 1-1: Release 17 4 bands DL/1 band UL inter-band carrier aggregation combinations
CA configuration
Uplink configuration
BCS
CA_1A-3C-7A-8A
CA_3C
0
CA_1A-3C-7C-20A
CA_7C
0
CA_1A-3C-7A-32A
-
0
CA_1A-3A-7A-40A-40A
-
0
CA_1A-3C-8A-20A
-
0
CA_1A-3C-8A-20A
CA_3C
0
CA_1A-3C-8A-38A
-
0
CA_1A-3C-8A-38A
CA_3C
0
CA_1A-3A-3A-8A-38A
-
0
CA_1A-3A-8A-40C
-
0
CA_1A-3A-8A-41A
-
0
CA_1A-3C-20A-32A
-
0
CA_1A-3A-20A-38A
-
0
CA_1A-3C-20A-38A
-
0
CA_1A-3C-20A-38A
CA_3C
0
CA_1A-3A-28A-32A
-
0
CA_1A-3A-28A-38A
-
0
CA_1A-3A-40A-41A
-
0
CA_1A-5A-7A-7A-28A
-
0
CA_1A-7A-8A-28A
-
0
CA_1A-7A-8A-32A
-
0
CA_1A-7A-8A-38A
-
0
CA_1A-7A-20A-38A
-
0
CA_1A-7A-28A-32A
-
0
CA_1A-7A-28A-38A
-
0
CA_1A-7A-28A-40A-40A
-
0
CA_1A-7A-32A-38A
-
0
CA_1A-8A-20A-32A
-
0
CA_1A-8A-20A-38A
-
0
CA_1A-8A-28A-32A
-
0
CA_1A-8A-32A-38A
-
0
CA_1A-20A-28A-32A
-
0
CA_1A-20A-28A-38A
-
0
CA_1A-20A-32A-38A
-
0
CA_2A-2A-5A-7A-66A
-
0
CA_2A-5A-7A-66A
-
0
CA_2A-5A-7A-7A-66A
-
0
CA_2A-5A-7A-66A-66A
-
0
CA_2A-5A-7C-66A
-
0
CA_2A-7A-12A-66A-66A
-
0
CA_2A-7C-13A-66A
-
0
CA_2A-7A-7A-13A-66A
-
0
CA_2A-7A-28A-66A
-
0
CA_2A-7C-28A-66A
-
0
CA_3A-5A-7A-7A-28A
-
0
CA_3A-7A-8A-28A
-
0
CA_3A-7A-20A-38A
-
0
CA_3A-7A-28A-40A-40A
-
0
CA_3A-8A-20A-38A
-
0
CA_3A-8A-40A-41A
-
0
CA_3A-20A-28A-38A
-
0
CA_7A-8A-20A-28A
-
0
CA_7A-8A-20A-32A
-
0
CA_7A-8A-20A-38A
-
0
CA_7A-8A-28A-32A
-
0
CA_7A-8A-32A-38A
-
0
CA_7A-20A-28A-32A
-
0
CA_7A-20A-28A-38A
-
0
CA_7A-20A-32A-38A
-
0
CA_8A-20A-28A-32A
-
0
CA_8A-20A-32A-38A
-
0
Table 1-2: Release 17 5 bands DL/1 band UL inter-band carrier aggregation combinations
CA configuration
Uplink configuration
BCS
CA_1A-3A-5A-7A-7A-28A
-
0
CA_1A-3A-7A-8A-28A
-
0
CA_1A-3A-7A-8A-38A
-
0
CA_1A-3A-7A-8A-40A
-
0
CA_1A-3A-7A-8A-40C
-
0
CA_1A-3A-7A-20A-38A
-
0
CA_1A-3A-7A-28A-38A
-
0
CA_1A-3A-7A-28A-40A
-
0
CA_1A-3A-8A-20A-28A
-
0
CA_1A-3A-8A-20A-38A
-
0
CA_1A-3A-20A-28A-38A
-
0
CA_1A-7A-8A-20A-28A
-
0
CA_1A-7A-8A-20A-32A
-
0
CA_1A-7A-8A-20A-38A
-
0
CA_1A-7A-8A-28A-32A
-
0
CA_1A-7A-8A-32A-38A
-
0
CA_1A-7A-20A-28A-32A
-
0
CA_1A-7A-20A-28A-38A
-
0
CA_1A-7A-20A-32A-38A
-
0
CA_1A-8A-20A-32A-38A
-
0
CA_2A-2A-29A-30A-66A
-
0
CA_3A-7A-8A-20A-28A
-
0
CA_3A-7A-8A-20A-38A
-
0
CA_3A-7A-20A-28A-38A
-
0
CA_7A-8A-20A-28A-32A
-
0
CA_7A-8A-20A-32A-38A
-
0
Table 1-3: Release 17 6 bands DL/1 band UL inter-band carrier aggregation combinations
CA configuration
Uplink configuration
BCS
CA_1A-3A-7A-8A-20A-28A
-
0
CA_1A-3A-7A-20A-28A-38A
-
0
CA_1A-3A-7C-20A-28A-38A
-
0
CA_1A-7A-8A-20A-28A-32A
-
0
CA_1A-7A-8A-20A-32A-38A
-
0
This TR contains a band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.763
|
Study on Narrow-Band Internet of Things (NB-IoT) / enhanced Machine Type Communication (eMTC) support for Non-Terrestrial Networks (NTN)
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.763/36763-h00.zip
|
At the RAN#86 meeting, a new Study Item was approved for Internet of Things Non Terrestrial Network (IoT NTN) and revised in RAN#91 [4]. There was an email discussion on [91E][42][NTN_IoT_Roadmap] In RAN#91 with moderator summary and final proposal for GTW input in [5].
In RAN#91-e GTW session, the Chairman endorsed a Way Forward Proposal in [6] on email discussion on [50][New_proposals_approval]. This included guidance from RAN Chairman for NTN NR and NTN IoT as follows
- RAN#92E (June) to finalize the scope and project plan to deliver the essential minimum functionality of both NTN NR and NTN IoT (both NB-IoT and eMTC) within the existing TU allocations
- Detailed scoping exercise (NTN NR WID revision, NTN IoT WID approval) to be undertaken at RAN#92E (June)
The objectives for this document are, based on the outcomes of the Release-17 NR NTN WI [7] and Release-16 TR 38.821 [8], to study a set of necessary features/adaptations enabling the operation of the IoT NTN for 3GPP Release 17 with a priority on satellite access.
The first objective of this Study is to identify scenarios applicable to NB-IoT/eMTC [RAN1, RAN2], including:
- Bands of interest in sub 6 GHz
- Device type with PC3 or PC5 (LEO and GEO)
- Satellite constellation orbit LEO and GEO
- Transparent payload.
- Link budget
NOTE 1: This first objective will be based on the scenarios documented in TR 38.821.
NOTE 2: UE mobility assumptions follow terrestrial NB-IoT/eMTC assumptions.
The second objective is, for the above identified scenarios, to study and recommend necessary changes to support NB-IoT and eMTC over satellite, reusing as much as possible the conclusions of the studies performed for NR NTN in TR38.821. This objective will address the following items:
- Aspects related to random access procedure/signals [RAN1, RAN2]
- Mechanisms for time/frequency adjustment including Timing Advance, and UL frequency compensation indication [RAN1, RAN2]
- Timing offset related to scheduling and HARQ-ACK feedback [RAN1, RAN2]
- Aspects related to HARQ operation [RAN2, RAN1]
- General aspects related to timers (e.g. SR, DRX, etc.) [RAN2]
- RAN2 aspects related to idle mode and connected mode mobility [RAN2]
- RLF-based for NB-IoT
- Handover-based for eMTC
- System information enhancements [RAN2]
- Tracking area enhancements [RAN2]
NOTE 3: GNSS capability in the UE is taken as a working assumption in this study for both NB-IoT and eMTC devices. With this assumption, UE can estimate and pre-compensate timing and frequency offset with sufficient accuracy for UL transmission. Simultaneous GNSS and NTN NB-IoT/eMTC operation is not assumed.
Recommendations for NB-IoT and recommendations for eMTC will be documented in the conclusions.
|
36.779
|
Introduction of upper 700MHz A block E-UTRA band for the US
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.779/36779-h00.zip
|
The present document is a technical report for the work item of Introduction of upper 700MHz A block E-UTRA band for the US.
|
37.717-00-00
|
Rel-17 band combinations for SA NR supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-00-00/37717-00-00-h00.zip
|
The present document is a technical report for SA NR Supplementary uplink (SUL), NSA NR SUL and NSA NR SUL with UL sharing from the UE perspective (ULSUP) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address NR SUL for the Rel-17 bands/band combinations in Table 1-1 to Table 1-4.
Table 1-1: Release 17 SUL bands
Band number
UL
DL
Duplex mode
n97
2300 MHz – 2400 MHz
N/A
SUL
n98
1880 MHz – 1920 MHz
N/A
SUL
n99
1626.5 MHz – 1660.5 MHz
N/A
SUL
Table 1-2: Release 17 SA SUL band combinations
SA SUL band combination
REL independent from
SUL_n41-n83
Rel-15
SUL_n79-n83
Rel-15
CA_n28_SUL_n41-n83
Rel-15
CA_n28_SUL_n79-n83
Rel-15
CA_n1_SUL_n78-n80
Rel-15
CA_n1_SUL_n78-n84
Rel-15
CA_n41_SUL_n79-n80
Rel-15
CA_n79_SUL_n41-n80
Rel-15
CA_n3_SUL_n78-n80
Rel-15
CA_n41_SUL_n79-n83
Rel-15
CA_n79_SUL_n41-n83
Rel-15
SUL_n79-n97
Rel-15
SUL_n41-n98
Rel-15
SUL_n79-n98
Rel-15
SUL_n41-n99
Rel-15
SUL_n48-n99
Rel-15
SUL_n77-n99
Rel-15
SUL_n41-n97
Rel-15
SUL_n24-n99
Rel-15
CA_n3_SUL_n41-n80
Rel-15
CA_n3_SUL_n79-n80
Rel-15
CA_n28-n79_SUL_n41-n83
Rel-15
CA_n28-n41_SUL_n79-n83
Rel-15
CA_n79_SUL_n41-n97
Rel-15
CA_n41_SUL_n79-n97
Rel-15
Table 1-3: Release 17 NSA SUL band combinations
NSA SUL band combination
REL independent from
Table 1-4: Release 17 NSA SUL with ULSUP band combinations
NSA SUL with ULSUP band combination
REL independent from
DC_28_SUL_n41-n83
Rel-15
This TR contains a general part and specific band combination part. The actual requirements are added to the corresponding technical specifications.
|
37.717-11-11
|
Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-11/37717-11-11-h00.zip
|
The present document is a technical report for Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame.
The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations in Table 1-1, 1-2, 1-3 and 1-4, including EN-DC and NE-DC combinations. The actual requirements are added to the corresponding technical specifications.
Table 1-1: Release 17 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) within FR1
DC combination
Uplink EN-DC configuration
DC_8A_n7A
DC_8A_n7A
DC_66A_n77A
DC_66A-66A_n77A
DC_66A-66A-66A_n77A
DC_66A_n77A
DC_13A_n77A
DC_13A_n77A
DC_5A_n77A
DC_5A_n77A
DC_2A_n77A
DC_2A-2A_n77A
DC_2A_n77A
DC_19A_n1A
DC_19A_n1A
DC_21A_n1A
DC_21A_n1A
DC_42A_n1A
DC_42C_n1A
DC_42A_n1A
DC_48A_n25A
DC_48C_n25A
DC_48D_n25A
DC_48A_n25A
DC_28A_n2A
DC_28A_n2A
DC_2A_n28A
DC_2A_n28A
DC_4A_n2A
DC_4A_n2A
DC_4A_n5A
DC_4A_n5A
DC_4A_n7A
DC_4A_n7A
DC_28A_n66A
DC_28A_n66A
DC_4A_n28A
DC_4A_n28A
DC_66A_n28A
DC_66A_n28A
DC_28A_n1A
DC_28A_n1A
DC_42A_n3A
DC_42A_n3A
DC_42C_n3A
DC_42A_n3A
DC_42C_n3A
DC_8A_n2A
DC_8A_n2A
DC_18A_n28A
DC_18A_n28A
DC_18A_n41A
DC_18A_n41A
DC_7A_n2A
DC_7C_n2A
DC_7A_n2A
DC_71A_n71A
DC_71A_n71A1
DC_25A_n77A
DC_25A_n77A
DC_25A-25A_n77A
DC_25A_n77A
DC_25A_n78A
DC_25A_n78A
DC_25A-25A_n78A
DC_25A_n78A
DC_21A_n28A2
DC_21A_n28A
DC_12A_n71A
DC_12A_n71A3,4
DC_71A_n41A
DC_71A_n41A
DC_71A_n2A
DC_71A_n2A
DC_2A_n30A
DC_2A_n30A
DC_5A_n30A
DC_5A_n30A
DC_12A_n30A
DC_12A_n30A
DC_66A_n30A
DC_66A_n30A
DC_11A_n41A
DC_11A_n41A
DC_66A_n66A
DC_66A_n66A1
DC_38A_n28A
DC_38A_n28A
DC_12A_n77A
DC_12A_n77A
DC_14A_n77A
DC_14A_n77A
DC_30A_n77A
DC_30A_n77A
DC_14A_n30A
DC_14A_n30A
DC_7A_n25A
DC_7A_n25A
DC_7A-7A_n25A
DC_7A_n25A
DC_7C_n25A
DC_7A_n25A
DC_13A_n25A
DC_13A_n25A
DC_3A-3A_n8A
DC_3A_n8A
DC_7A-7A_n8A
DC_7A_n8A
DC_48A_n77A5. 6. 7, 8
N/A
DC_38A_n3A
DC_38A_n3A
DC_(n)66AA
DC_(n)66AA1
DC_38A_n1A
DC_38A_n1A
DC_38A_n8A
DC_38A_n8A
DC_(n)3AA
DC_(n)3AA1
DC_14A_n5A
DC_14A_n5A
DC_11A_n1A
DC_11A_n1A
DC_41A_n1A
DC_41C_n1A
DC_41A_n1A
DC_41C_n1A
DC_7A_n79A
DC_7A_n79C
DC_7A_n79A
DC_38A_n79A
DC_38A_n79C
DC_38A_n79A
DC_5A_n1A
DC_5A_n1A
DC_5A_n3A
DC_5A_n3A
DC_2A_n25A9. 10. 11
N/A
DC_(n)7AA
DC_(n)7AA1
DC_71A_n77A
DC_71A_n77A
DC_48A_n2A
DC_48A_n2A
NOTE 1: Only single switched UL is supported.
NOTE 2: The frequency range in band n28 is restricted for this band combination to 728 - 738 MHz for the UL and 783 - 793 MHz for the DL. This restriction applies also for these band combinations when applicable EN-DC configuration is part of a higher order EN-DC configuration.
NOTE 3: Only single switched UL is supported.
NOTE 4: The implementation with 4 antennas is targeted for FWA form factor for this band combination.
NOTE 5: The minimum requirements apply only when there is non-simultaneous Tx/Rx operation between E-UTRA and NR carriers. This restriction applies also for these carriers when applicable EN-DC configuration is part of a higher order EN-DC configuration.
NOTE 6: The minimum requirements for intra-band non-contiguous EN-DC apply. When UE capability interBandContiguousMRDC is indicated, the minimum requirements for intra-band-contiguous EN-DC also should be met in addtion to intra-band non-contiguous EN-DC. The intra-band requirements also apply for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
NOTE 7: The combination is not used alone as fall back mode of other band combinations in which UL in Band 42 or Band 48 is not used.
NOTE 8: The minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers is within 6 dB. The power spectral density imbalance condition also applies for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
NOTE 9: The combination is not used alone as fallback mode of other band combinations in which UL in Band 2 is not used.
NOTE 10: The minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers is within 6 dB. The power spectral density imbalance condition also applies for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
NOTE 11: The minimum requirements apply for synchronized DL carriers with a maximum receive time difference ≤ 3 usec. The requirements also apply for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
Table 1-2: Release 17 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) including FR2
DC combination
Uplink EN-DC configuration
DC_66A_n261(A-L)
DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I
DC_66A_66A_n261(A-L)
DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I
DC_48A_n261(A-L)
DC_48A_n261A
DC_48A_n261G
DC_48A_n261H
DC_48A_n261I
DC_13A_n261(A-L)
DC_13A_n261A
DC_13A_n261G
DC_13A_n261H
DC_13A_n261I
DC_5A_n261(A-J)
DC_5A_n261A
DC_5A_n261G
DC_5A_n261H
DC_5A_n261I
DC_5A_n261(A-L)
DC_5A_n261A
DC_5A_n261G
DC_5A_n261H
DC_5A_n261I
DC_2A_n261(A-L)
DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A-2A_n261A
DC_2A_n261A
DC_2A-2A_n261I
DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A-2A_n261M
DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_20A_n257A
DC_20A_n257B
DC_20A_n257C
DC_20A_n257D
DC_20A_n257E
DC_20A_n257F
DC_20A_n257G
DC_20A_n257H
DC_20A_n257I
DC_20A_n257J
DC_20A_n257K
DC_20A_n257L
DC_20A_n257M
DC_20A_n257A
DC_3A-3A_n257G
DC_3A-3A_n257H
DC_3A-3A_n257I
DC_3A-3A_n257J
DC_3A-3A_n257K
DC_3A-3A_n257L
DC_3A-3A_n257M
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_3A_n257J
DC_3A_n257K
DC_7A-7A_n257J
DC_7A-7A_n257K
DC_7A-7A_n257L
DC_7A-7A_n257M
DC_7A_n257J
DC_7A_n257K
DC_7A_n257J
DC_7A_n257K
DC_7A_n257L
DC_7A_n257M
DC_7A_n257J
DC_7A_n257K
Table 1-3: Release 17 NE-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) within FR1
DC combination
Uplink NE-DC configuration
DC_n28A_3A
DC_n28A_3C
DC_n28A_3A
DC_n28A_8A
DC_n28A_8B
DC_n28A_8A
DC_n28A_40A
DC_n28A_40C
DC_n28A_40A
DC_n41A_3A
DC_n41A_3C
DC_n41C_3A
DC_n41A_3A
DC_n41A_8A
DC_n41A_8B
DC_n41C_8A
DC_n41A_8A
DC_n41A_34A1
DC_n41A_34A
DC_n41A_39A1
DC_n41A_39C1
DC_n41C_39A1
DC_n41A_39A
DC_n41A_40A1
DC_n41A_40C1
DC_n41C_40A1
DC_n41A_40A
DC_n3A_1A
DC_n3A_1A
DC_n8A_1A
DC_n8A_1A
DC_n77A_1A
DC_n77(2A)_1A
DC_n77A_1A
DC_n77A_3A
DC_n77(2A)_3A
DC_n77A_3A
DC_n3A_8A
DC_n3A_8A
DC_n8A_3A
DC_n8A_3A
DC_n77A_8A
DC_n77(2A)_8A
DC_n77A_8A
DC_n28A_34A
DC_n28A_34A
DC_n28A_39A
DC_n28A_39C
DC_n28A_39A
NOTE 1: The minimum requirements apply only when there is non-simultaneous Tx/Rx operation between E-UTRA and NR carriers. This restriction applies also for these carriers when applicable EN-DC configuration is part of a higher order EN-DC configuration.
Table 1-4: Release 17 NE-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) including FR2
DC combination
Uplink NE-DC configuration
|
37.717-11-21
|
Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3,4) LTE inter-band CA (xDL/1UL) and 2 bands NR inter-band CA (2DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-21/37717-11-21-h00.zip
|
The present document is a technical report for Dual connectivity (DC) band combinations of LTE xDL/1UL (x=1,2,3,4) + inter-band NR 2DL/1UL under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address DC band combinations of LTE xDL/1UL (x=1,2,3,4) + inter-band NR 2DL/1UL in Rel-17 as shown in the WID for Rel-17.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
37.717-11-31
|
Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-31/37717-11-31-h00.zip
|
The present document is a technical report for DC of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) under Rel-17 time frame, including EN-DC and NE-DC. The purpose is to gather the relevant background information and studies in order to address DC of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) in Rel-17 as .
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
37.717-11-41
|
Rel-17 Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/1UL) and 4 bands NR inter-band CA (4DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-41/37717-11-41-h00.zip
|
The present document is a technical report for DC of x bands (x=1,2) LTE inter-band CA (xDL/1UL) and 4 bands NR inter-band CA (4DL/1UL) under Rel-17 time frame, including EN-DC and NE-DC. The purpose is to gather the relevant background information and studies in order to address DC of x bands (x=1,2) LTE inter-band CA (xDL/1UL) and 4 bands NR inter-band CA (4DL/1UL) in Rel-17 as .
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
37.717-21-11
|
Rel-17 Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-21-11/37717-21-11-h00.zip
|
The present document is a technical report for Dual Connectivity of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual connectivity (DC) band combinations of 3 different bands DL with 2 different bands UL (2 different LTE bands and 1 NR band) for the Rel-17 band combinations. The actual requirements are added to the corresponding technical specification.
|
37.717-21-22
|
Rel-17 Dual Connectivity (DC) of x bands (x=2,3,4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-21-22/37717-21-22-h00.zip
|
The present document is a technical report for Dual Connectivity (DC) of x bands (x=2, 3, 4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of x bands (x=2, 3, 4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification.
|
37.717-31-11
|
Rel-17 Dual Connectivity (DC) of 3 bands LTE inter-band CA (3DL/1UL) and 1 NR band (1DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-31-11/37717-31-11-h00.zip
|
The present document is a technical report for Dual Connectivity (DC) of 3 LTE bands (3DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 3 LTE band (3DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification.
|
37.717-33
|
Rel-17 Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA (yDL/yUL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-33/37717-33-h00.zip
|
The present document is a technical report for Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA (yDL/yUL) under Rel-17 time frame, including EN-DC and NE-DC. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA (yDL/yUL) for the Rel-17 band combinations, where:
- For only 1 NR band included (i.e. x=2 and y=1), only NR FR2 band is applied
- For only 2 NR bands included (i.e. x=1 and y=2), 1 NR FR1 band and 1 NR FR2 band are included and operated as inter-band CA
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
37.717-41-11
|
Rel-17 Dual Connectivity (DC) of 4 bands LTE inter-band CA (4DL/1UL) and 1 NR band (1DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-41-11/37717-41-11-h00.zip
|
The present document is a technical report for Dual Connectivity (DC) of 4 LTE bands (4DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 4 LTE band (4DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification.
|
37.717-51-11
|
Rel-17 Dual Connectivity (DC) of 5 bands LTE inter-band CA (5DL/1UL) and 1 NR band (1DL/1UL)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-51-11/37717-51-11-h00.zip
|
The present document is a technical report for Dual Connectivity (DC) of 5 LTE bands (5DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 5 LTE band (5DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification.
|
37.817
|
Study on enhancement for data collection for NR and ENDC
|
TR
|
17.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.817/37817-h00.zip
|
The present document provides descriptions of principles for RAN intelligence enabled by AI, the functional framework (e.g., the AI functionality and the input/output of the component for AI enabled optimization) and use cases and solutions of AI enabled RAN.
The study is based on the current architecture and interfaces.
|
37.826
|
High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.826/37826-h00.zip
|
The present document is a technical report for High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band within FR1 under Rel-17 timeframe, including both FDD+TDD and TDD+TDD EN-DC band combinations. FDD+TDD band combinations could support LTE 23dBm + NR 23dBm and LTE 23dBm + NR 26dBm, while TDD+TDD band combinations support only LTE 23dBm + NR 23dBm. Completion of PC3 for particular EN-DC combination is the prerequisite for introducing PC2 for that combination. All the PC2 EN-DC combinations are release-independent from Rel-15.
The purpose is to gather the relevant background information and studies in order to address Power Class 2 EN-DC of 1 LTE band and 1 NR TDD band for the Rel-17 band combinations in Table 1-1. The actual requirements are added to the corresponding technical specifications.
|
37.827
|
Rel-17 Power Class 2 for EN-DC with xLTE band + yNR DL with 1LTE+1(TDD) NR UL band (x= 2, 3, y=1; x=1, 2, y=2)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.827/37827-h00.zip
|
The present document is a technical report Power Class 2 for EN-DC with xLTE band + yNR DL with 1LTE+1(TDD) NR UL band (x= 2, 3, 4, y=1; x=1, 2, y=2) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address relevant requirements for the Rel-17 EN-DC band combinations with Power Class 2 requested by proponents and captured in the WID...
|
37.828
|
High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands and NR bands
|
TR
|
17.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.828/37828-h20.zip
|
The present document is a technical report for release 17 basket WI High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands and NR bands.
|
37.867
|
Downlink interruption for band combinations to conduct dynamic Tx Switching
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.867/37867-h00.zip
|
The present document is a technical report for WI “downlink interruption for band combinations to conduct dynamic Tx Switching” under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address the band combinations requested for mandating no DL interruption to conduct dynamic Tx switching listed in Table 1-1.
Table 1-1: Band combinations requested for mandating no DL interruption
Configuration
Uplink configuration
Company
CA_n5-n78, DC_5_n78
CA_n5-n78, DC_5_n78
China Telecom
CA_n1-n3-n78
CA_n1-n78, CA_n3-n78
China Telecom, China Unicom
CA_n3-n40-n41
CA n3-n40, CA n3-n41
CMCC
CA_n3-n41-n79
CA n3-n41, CA n3-n79, CA n41-n49
CMCC
CA_n39-n41-n79
CA n39-n79, CA n41-n79, CA n39-n41
CMCC
CA_n40-n41-n79
CA n40-n79, CA n41-n79
CMCC
CA_n8-n39-n41
CA n8-n39, CA n8-n41, CA n39-n41
CMCC
CA_n8-n41-n79
CA n8-n41, CA n8-n79, CA n41-n79
CMCC
|
37.875
|
Band combinations for Uu and V2X con-current operation
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.875/37875-h00.zip
|
The present document is the Technical Report on TR on band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band.
The purpose of the present document is to study the extension of the band combinations for V2X service to grow the NR V2X ecosystem. Operators propose new band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band. Whether to specify con-current operation of LTE/NR CA/DC band combinations and V2X band depends on requests in Rel-17. Specifically, the self-desensitization problem of con-current operation band combinations will be analysed including harmonics, IMD problem, etc.. Also the candidate solutions will be studied to solve the self-desensitization problem.
Table 1-1: Release 17 NR V2X band combinations
V2X Band combination
REL independent from
V2X_n39-n47
Rel-16
V2X_n40-n47
Rel-16
V2X_n41-n47
Rel-16
V2X_n78-n47
Rel-16
V2X_n79-n47
Rel-16
V2X_n39_47
Rel-16
V2X_n40_47
Rel-16
V2X_n41_47
Rel-16
V2X_n78_47
Rel-16
V2X_n79_47
Rel-16
V2X_3_n47
Rel-16
V2X_39_n47
Rel-16
V2X_40_n47
Rel-16
V2X_41_n47
Rel-16
Note: All band combinations in table 1-1 that are release independent from Rel-16 are optional
|
37.880
|
Study on high-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands 5 and 12 and NR band n71
|
TR
|
17.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.880/37880-h20.zip
|
The present document captures the findings from the study item "Study on High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71".
|
38.717-01-01
|
Rel-17 NR intra band Carrier Aggregation for xCC DL/yCC UL including contiguous and non-contiguous spectrum (x>=y)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.717-01-01/38717-01-01-h00.zip
|
The present document is a technical report for NR Intra-band Carrier Aggregation Rel-17 for xDL/yUL including contiguous and non-contiguous spectrum under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address NR Intra-band Carrier Aggregation requirements for the Rel-17 band combinations requested by proponents and captured in the WID..
|
38.717-02-01
|
Rel-17 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.717-02-01/38717-02-01-h00.zip
|
The present document is a technical report for power class 3 NR inter-band CA and DC for 2 bands DL with up to 2 bands UL under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address NR inter-band CA and DC for 2 bands DL with up to 2 bands UL for the Rel-17 band combinations.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.717-03-01
|
Rel-17 NR inter-band Carrier Aggregation for 3 bands DL with 1 band UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.717-03-01/38717-03-01-h00.zip
|
The present document is a technical report for Rel-17 NR 3DL/1UL Inter-band Carrier Aggregation. The purpose is to gather the relevant background information and studies in order to address 3DL/1UL Inter-band Carrier Aggregation requirements for the Rel-17 band combinations in Table 1-1. UL carrier is supported in each of the 3 bands being aggregated unless otherwise specified.
Table 1-1: Release 17 3DL/1UL inter-band carrier aggregation combinations
CA combination
REL independent from
CA_x1A-yA-zA
The present document contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.717-03-02
|
Rel-17 NR inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with 2 bands UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.717-03-02/38717-03-02-h00.zip
|
The present document is a technical report for NR inter-band CA and DC for 3 bands DL with 2 bands UL under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address NR inter-band CA and DC for 3 bands DL with 2 bands UL for the Rel-17 band combinations.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.717-04-01
|
Rel-17 NR inter-band Carrier Aggregation for 4 bands DL with 1 band UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.717-04-01/38717-04-01-h00.zip
|
The present document is a technical report on inter-band CA for 4 bands DL with 1 band UL under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address 4 bands DL/1 band UL Inter-band Carrier Aggregation requirements for the Rel-17 band combinations requested by proponents and captured in the WID...
|
38.717-04-02
|
Rel-17 NR inter-band Carrier Aggregation/Dual connectivity for DL 4 bands and 2UL bands
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.717-04-02/38717-04-02-h00.zip
|
The present document is a technical report for NR inter-band Carrier Aggregation (CA) and/or Dual Connectivity (DC) of 4DL NR bands and 2UL NR bands under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address NR inter-band CA and/or DC for the Rel-17 band combinations in Table 1-1.
This TR contains a band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.717-05-01
|
Rel-17 NR inter-band Carrier Aggregation for 5 bands DL with x bands UL (x=1, 2)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.717-05-01/38717-05-01-h00.zip
|
The present document is a technical report on inter-band CA for 5 bands DL with x bands UL (x=1, 2) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address 5 bands DL/ x bands UL (x=1, 2) Inter-band Carrier Aggregation requirements for the Rel-17 band combinations in Table 1-1 and Table 1-2.
Table 1-1: Release 17 5 bands DL/ x bands UL (x=1, 2) inter-band carrier aggregation combinations involving FR1
CA combinations
CA_n1-n3-n7-n28-n78
CA_n1-n3-n5-n7-n78
Table 1-2: Release 17 5 bands DL/ x bands UL (x=1, 2) inter-band carrier aggregation combinations between FR1 and FR2
CA combinations
CA_n1-n3-n8-n77-n257
This TR contains a general part and specific band combination part. The actual requirements are added to the corresponding technical specifications.
|
38.785
|
User Equipment (UE) radio transmission and reception for enhanced NR sidelink
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.785/38785-h00.zip
|
The present document is a technical report for NR sidelink enhancement services in Rel-17. The purpose is to specify radio solutions that are necessary for NR to support sidelink enhancement services based on the study outcome captured in TR 38.840 and TR 37.885. Based on merged motivations from interested companies, the following justification and objectives of this work item decided in session 4.1 and session 4.2.
|
38.808
|
Study on supporting NR from 52.6 GHz to 71 GHz
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.808/38808-h00.zip
|
In order to support wide range of services, 5G NR system aims to be flexible enough to meet the connectivity requirements of a range of existing and future (yet unknown) services to be deployable in an efficient manner. NR considers supporting potential use of frequency range up to 100 GHz [1].
NR specifications that have been developed in Rel-15 and Rel-16 define operation for frequencies up to 52.6 GHz, where all physical layer channels, signals, procedures, and protocols are designed to be optimized for uses under 52.6 GHz.
However, frequencies above 52.6 GHz are faced with more difficult challenges, such as higher phase noise, larger propagation loss due to high atmospheric absorption, lower power amplifier efficiency, and strong power spectral density regulatory requirements in unlicensed bands, compared to lower frequency bands. Additionally, the frequency ranges above 52.6 GHz potentially contain larger spectrum allocations and larger bandwidths that are not available for bands lower than 52.6 GHz.
As an initial effort to enable and optimize 3GPP NR system for operation in above 52.6 GHz, 3GPP RAN has studied requirements for NR beyond 52.6GHz up to 114.25GHz including global spectrum availability and regulatory requirements (including channelization and licensing regimes), potential use cases and deployment scenarios, and NR system design requirements and considerations on top of regulatory requirements [2]. The potential use cases identified in the study include high data rate eMBB, mobile data offloading, short range high-data rate D2D communications, broadband distribution networks, integrated access backhaul (IAB), factory automation, industrial IoT (IIoT), wireless display transfer, augmented reality (AR)/virtual reality (VR) wearables, intelligent transport systems (ITS) and V2X, data center inter-rack connectivity, smart grid automation, private networks, and support of high positioning accuracy. The use cases span over several deployment scenarios identified in the study. The deployment scenarios include, but not limited to, indoor hotspot, dense urban, urban micro, urban macro, rural, factor hall, and indoor D2D scenarios. The study also identified several system design requirements around waveform, MIMO operation, device power consumption, channelization, bandwidth, range, availability, connectivity, spectrum regime considerations, and others.
Among the frequencies of interest, frequencies between 52.6 GHz and 71 GHz are especially interesting relatively in the short term because of their proximity to sub-52.6 GHz for which the current NR system is optimized and the imminent commercial opportunities for high data rate communications, e.g., unlicensed spectrum but also licensed spectrum between 57 GHz and 71 GHz. Therefore, it would be beneficial to make a study focused on feasibility of using existing waveforms and required changes for frequencies between 52.6 GHz and 71 GHz, so as to take advantage of imminent commercial opportunities for the specific frequency regime by minimizing the specification burden and maximizing the leverage of FR2 based implementations.
|
38.830
|
Study on NR coverage enhancements
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.830/38830-h00.zip
|
The present document captures the results and findings from the study item "New SID on NR coverage enhancement" [2]. The purpose of this TR is to document the baseline coverage performance for both FR1 and FR2 considering the scenarios and services identified in [2], and to document the evaluation and findings of the potential enhancements for the identified scenarios and services.
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.
This document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
38.832
|
NR; Study on enhancement of Radio Access Network (RAN) slicing
|
TR
|
17.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.832/38832-h00.zip
|
The present document provides descriptions of use cases and solutions with regard to enhancement of Radio Access Network (RAN) slicing for NR.
|
38.833
|
Further enhancement on NR demodulation performance
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.833/38833-h00.zip
|
The present technical report documents the Phase I study outcome on inter-user interference suppression for NR MU-MIMO and techniques to cope with LTE CRS interference for NR UE, with the detailed objectives as follows:、
• MMSE-IRC receiver for suppressing intra-cell inter-user interference
- Phase I: Evaluate the performance under practical MU-MIMO interference profile for the candidate reference receiver.
∘ Identify practical MU-MIMO interference modelling methodology
∘ Reference receiver: MMSE-IRC receiver. Use the DMRS-based interference covariance estimation method as a starting point
∘ Prioritize slot-based transmission scenario
• Evaluate techniques to cope with CRS interference in scenarios with overlapping spectrum for LTE and NR
- Candidate reference receiver to enable neighboring cell CRS-IM
∘ The performance benefit of neighboring cell LTE CRS-IM over the existing rate matching solutions specified in Rel-15 and Rel-16 shall be evaluated.
∘ Feasibility of the considered solution regarding NR PDSCH processing timeline need to be checked.
∘ Priority will be given to solutions not having RAN1 specification impact.
- Synchronous network scenario is prioritized. As second priority, RAN4 could evaluate the feasibility and usefulness of the asynchronous network scenario and specify if feasible and useful.
- 15 kHz SCS for NR is prioritized. RAN4 should evaluate the feasibility and usefulness of 30 kHz SCS for scenarios with LTE and NR deployed in neighboring BSs/areas and specify if feasible and useful.
|
38.834
|
Measurements of User Equipment (UE) Over-the-Air (OTA) performance for NR FR1; Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology
|
TR
|
17.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.834/38834-h20.zip
|
The present document is a technical report for FR1 Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology, for NR standalone (SA) and NR non-standalone (NSA) operation mode.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.