id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
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.579-1
|
Mission Critical (MC) services; Part 1: Common test environment
|
TS
|
17.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-1/37579-1-h20.zip
|
The present document defines the common test environment required for testing Client and Server implementations for compliance to the Mission Critical Services protocol requirements defined by 3GPP.
It contains definitions of reference conditions and test signals, default messages and other parameters, generic procedures, and, common requirements for test equipment with the goal for facilitating testing in general and test procedures specification in particular. Various parts of its content are referred to from other parts of the Mission Critical Services protocol conformance testing specification e.g. TS 37.579-2 [2], 3GPP TS 37.579-6 [84], 3GPP TS 37.579-7 [85].
The present document does not define the common test environment required for testing the implementation of the underlying RRC/NAS protocols, i.e. the bearers used for transport of the Mission Critical Services signalling and media. This is defined in TS 36.508 [6] and referred to from the present document whenever needed.
In regard to default messages or other information elements contents, the present document refers to content defined in requirements specifications specified by 3GPP or other organisations.
|
37.579-2
|
Mission Critical (MC) services; Part 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specification
|
TS
|
17.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-2/37579-2-h20.zip
|
The present document specifies the protocol conformance testing for testing a MCPTT Client for compliance to the Mission Critical Push To Talk (MCPTT) protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCPTT Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 37.579-1 [2];
- Implementation Conformance Statement (ICS) TS 37.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 37.579-5 [5];
- the applicability of each test case TS 37.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the 3GPP bearers which carry the MCPTT data sent or received by the MCPTT Client and which are required to be supported by the UE in which the MCPTT Client is installed. This is defined in TS 36.523-1 [6] for EPS (LTE) or TS 38.523-1 [39] for NR/5GC.
|
37.579-4
|
Mission Critical (MC) services; Part 4: Test Applicability and Implementation Conformance Statement (ICS) proforma specification
|
TS
|
17.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-4/37579-4-h20.zip
|
The present document provides the Implementation Conformance Statement (ICS) proforma for testing Client implementations for compliance to the Mission Critical Services protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [7] and ISO/IEC 9646-7 [8].
The present document specifies the recommended applicability statement for the test cases included in 3GPP TS 37.579-2 [3], as well as, TS 37.579-6 [3] and 3GPP TS 37.579-7 [12]. These applicability statements are based on the features implemented in the Client.
The present document is valid for Mission Critical Services Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The present document is valid for Mission Critical Video (MCVideo) and Mission Critical Data (MCData) Clients implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document.
The present document does not specify applicability or ICS for protocol conformance testing for the 3GPP bearers which carry the Mission Critical Services data sent or received by the Client. These are defined in TS 36.523-2 [6] for EPS (LTE) or TS 38.523-2 [20] for NR/5GC.
|
37.579-6
|
Mission Critical (MC) services; Part 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specification
|
TS
|
17.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-6/37579-6-h20.zip
|
The present document specifies the protocol conformance testing for testing a MCVideo Client for compliance to the Mission Critical Video (MCVideo) protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCVideo Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 37.579-1 [2];
- Implementation Conformance Statement (ICS) TS 37.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 37.579-5 [5];
- the applicability of each test case TS 37.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the 3GPP bearers which carry the MCVideo data sent or received by the MCVideo Client and which are required to be supported by the UE in which the MCVideo Client is installed. This is defined in TS 36.523-1 [6] for EPS (LTE) or TS 38.523-1 [37] for NR/5GC.
|
37.579-7
|
Mission Critical (MC) services; Part 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specification
|
TS
|
17.2.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-7/37579-7-h20.zip
|
The present document specifies the protocol conformance testing for testing a MCData Client for compliance to the Mission Critical Data (MCData) protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCData Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 37.579-1 [2];
- Implementation Conformance Statement (ICS) TS 37.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 37.579-5 [5];
- the applicability of each test case TS 37.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the 3GPP bearers which carry the MCData data sent or received by the MCData Client and which are required to be supported by the UE in which the MCData Client is installed. This is defined in TS 36.523-1 [6] for EPS (LTE) or TS 38.523-1 [45] for NR/5GC.
According to 3GPP drafting rules, the references clause shall list only documents that are explicitly mentioned in the deliverable. This reference is not used within the document and thus shall be removed from references clause.
|
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.
|
38.836
|
Study on NR sidelink relay
|
TR
|
17.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.836/38836-h00.zip
|
The present document is related to Study on NR Sidelink Relay with a scope as defined in [2].
The document describes NR enhancements to support sidelink relay, which were analyzed as part of the study such as sidelink-based UE-to-Network and UE-to-UE Relay, and discovery model/procedure for sidelink relaying.
|
38.837
|
UE RF Requirements for Transparent Tx Diversity (TxD) for NR
|
TR
|
17.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.837/38837-h30.zip
|
The present document is a technical report for NR UE RF requirements for Transparent Tx Diversity (TxD).
|
38.838
|
Study on XR (Extended Reality) evaluations for NR
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.838/38838-h00.zip
|
The present document captures the results and findings from the study item "Study on XR Evaluation for NR"[2].
The purpose of this TR is
- to document the evaluation methodology for XR evaluation including XR applications, simulation scenarios, traffic models, KPIs, simulation parameters, etc,
- to document the performance evaluation results of XR applications in NR for both FR1 and FR2 considering the scenarios and services of interest,
- to document the identified problems/challenges in supporting XR applications of interest in various scenarios.
This activity involves the Radio Access work area of the 3GPP studies and has potential impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
|
38.839
|
Principles and requirements for simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.839/38839-h00.zip
|
The present document is a technical report for simultaneous Rx/Tx band combinations. The TR includes principles to decide mandatory/optional capability for FDD-TDD, TDD-TDD band combinations in different cases, identify case by case issues and align the specification treatment for CA/DC/SUL band combinations.
|
38.841
|
High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x =1,2)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.841/38841-h00.zip
|
The present document is a technical report for high power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address power class 2 NR inter-band CA for 2 bands DL with 2 bands UL in Table 1-1.
Table 1-1 Rel-17 power class 2 NR 2BDL/2BUL inter-band CA
NR CA
configuration
Uplink CA
configuration
Power class 2 cases
Release independent from
CA_nXA-nYA
CA_nXA-nYA
The allowed maximum output power by each of carrier for power class 2 cases is listed in table 1-2.
Table 1-2 Maximum output power for power class 2 cases
Power class 2 cases for CA_nXA-nYA
CA power class
Carrier X power class
Carrier Y power class
Case a
26dBm
23dBm
23dBm
Case b
26dBm
23dBm
26dBm
Case c
26dBm
26dBm
23dBm
Case d
26dBm
26dBm
26dBm
NOTE: The Carrier X and Y are one-by-one corresponding to carriers in CA configuration of CA_nXA-nYA
|
38.842
|
High power User Equipment (UE) (power class 2) for NR inter-band Carrier Aggregation (CA) and Supplementary Uplink (SUL) configurations with x (x>2) bands DL and y (y=1, 2) bands UL
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.842/38842-h00.zip
|
The present document is a technical report for high power UE (power class 2) for NR inter-band Carrier Aggregation or NR-NR DC with and without SUL with x (6≥x>2) bands downlink and y (y=1, 2) bands uplink under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address power class 2 NR inter-band CA/DC with and without SUL for more than 2 bands DL and with up to 2 bands UL in Table 1-1.
Table 1-1 Rel-17 power class 2 NR xBDL/yBUL inter-band CA and SUL
NR CA
configuration
Uplink CA
configuration
Power class 2 cases
Release independent from
CA_nV1-nV2-…-nVx
- (Note 1)
CA_nV1-nV2-…-nVx
CA_nVi-nVj (Note 2)
CA_nV1-nV2-…-SUL_nVx-nVx+1
SUL_nVx-nVx+1
Note 1: The UL carrier supports power class 2.
Note 2: The integers i and j satisfy: 1 ≤ i ≤ x, 1 ≤ j ≤ x, i ≠ j.
The allowed maximum output power by each of carrier for power class 2 cases is listed in table 1-2.
Table 1-2 Maximum output power for power class 2 cases
Power class 2 cases for UL CA_nVi-nVj
CA power class
Carrier Vi power class
Carrier Vj power class
Case a
26dBm
23dBm
23dBm
Case b
26dBm
23dBm
26dBm
Case c
26dBm
26dBm
23dBm
Case d
26dBm
26dBm
26dBm
NOTE: The Carrier Vi and Vj are one-by-one corresponding to carriers in UL CA configuration of CA_nVi-nVj.
|
38.845
|
Study on scenarios and requirements of in-coverage, partial coverage, and out-of-coverage NR positioning use cases
|
TR
|
17.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.845/38845-h00.zip
|
The present document captures the findings of the study item, "Study on scenarios and requirements of in-coverage, partial coverage, and out-of-coverage positioning use cases" [2]. The purpose of this TR is to facilitate future 3GPP work by identifying the requirements and deployment/operation scenarios for V2X and public safety use cases. In particular, this study considers positioning for the UEs in in-coverage, partial coverage, and out-of-coverage as per the network coverage definition in the current specifications.
This document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings until it is approved.
|
38.847
|
New frequency range for NR (47.2 – 48.2 GHz)
|
TR
|
17.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.847/38847-h20.zip
|
The present document is a technical report for Work Item on New Radio (NR) Access Technology, covering the new frequency range between 47.2- 48.2 GHz for NR.
|
38.851
|
User Equipment (UE) Further enhancements of NR RF requirements for frequency range 2 (FR2)
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.851/38851-h00.zip
|
The present document is a technical report for Rel-17 WI Further enhancements of NR RF requirements for frequency range 2 (FR2).
|
38.852
|
Introduction of 1900MHz NR band for Europe for Rail Mobile Radio (RMR)
|
TR
|
17.5.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.852/38852-h50.zip
|
The present document is a technical report deals with the use of the Rail Mobile Radio spectrum in the 1900MHz frequency band in CEPT countries which are subject to the ECC Decision (20)02 [1] for the use by the railways. The purpose is to gather the relevant background information and studies in order to address all the necessary precautions to make the unpaired spectrum of 1900-1910MHz usable for 5G NR.
|
38.853
|
Introduction of 900MHz NR band for Europe for Rail Mobile Radio (RMR)
|
TR
|
17.5.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.853/38853-h50.zip
|
The present document is a technical report deals with the use of the Rail Mobile Radio spectrum in the 900 MHz frequency band in CEPT countries which are subject to the ECC Decision (20)02 [1] for the use by the railways. The purpose is to gather the relevant background information and studies in order to address all the necessary precautions to make the paired spectrum of 874.6-800/919.4-925 MHz usable for 5G NR.
|
38.857
|
Study on NR positioning enhancements
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.857/38857-h00.zip
|
The present document captures the findings of the study item "Study on NR positioning enhancements" [2]. The purpose of this technical report is to document the requirements, additional scenarios, evaluations and technical proposals treated during the study and provide a way forward toward enhancements to NR positioning in TSG RAN WGs.
|
38.860
|
Study on extended 600MHz NR band
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.860/38860-h00.zip
|
The present document is a technical report for the study item of APT 600 MHz NR FDD band.
|
38.861
|
Study on high power UE (power class 2) for one NR FDD band
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.861/38861-h00.zip
|
The present document is a technical report for Study on high power UE (power class 2) for one NR FDD band. The study includes the SAR scheme(s), interference issues, UE implementation issues, and system performance evaluations.
The example bands used for the study are NR band n1 and n3.
|
38.862
|
Study on band combination handling in RAN4
|
TR
|
17.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.862/38862-h20.zip
|
The present document is a technical report on band combination handling and rule collection for RAN4 specifications. The purpose is to create a document to collect the rules of band combinations, which can be widely known not only by RAN4 but also by other 3GPP working groups or even by other industrial partners outside 3GPP. It aims to improve the band combination in the current RAN4 specifications and collect the rules what RAN4 has been achieved during the timescale of Rel-17.
This TR contains a band combination specific part. The agreements on the rules of specifying band combinations, and facilitate understanding of the complex notations of CA/DC combinations are provided.
|
38.868
|
Study on optimizations of pi/2 BPSK uplink power in NR
|
TR
|
17.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.868/38868-h00.zip
|
This document is a technical report for optimization of pi/2 BPSK NR uplink power in Rel-17. The purpose is to evaluate the feasibility of increasing the UE’s uplink power in TDD bands for pi/2 BPSK modulation assuming use of existing UE power classes as indicated per band or band combination. The objectives are applicable to FR1 TDD bands n34, n39, n40, n41, n77, n78 and n79. The justification and objectives of this work item are outlined in section 4.1 and section 4.2.
|
38.875
|
Study on support of reduced capability NR devices
|
TR
|
17.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.875/38875-h00.zip
|
This document captures the findings from the study item "Study on support of reduced capability NR devices" [2].
The study includes identification and study of potential UE complexity reduction techniques and UE power saving and battery lifetime enhancements for reduced capability UEs in applicable use cases, functionality that will enable the performance degradation of such complexity reduction to be mitigated or limited, principles for how to define and constrain such reduced capabilities, and functionality that will allow devices with reduced capabilities to be explicitly identifiable to networks and networks operators and allow operators to restrict their access if desired.
The scope of the study includes support for all FR1/FR2 bands for FDD and TDD and coexistence with Rel-15/16 UEs. This study focuses on SA mode and single connectivity. The scope of the study does not include LPWA use cases.
|
38.890
|
Study on NR QoE (Quality of Experience) management and optimizations for diverse services
|
TR
|
17.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.890/38890-h00.zip
|
The present document captures the results of study on NR QoE management and optimizations for diverse services in RP-193256 [2]. It identifies to study the framework for triggering, configuring, collection and reporting of NR QoE measurement and study the potential impact on the related interface (e.g. F1, NG, Xn interface).
|
21.916
|
Release 16 Description; Summary of Rel-16 Work Items
|
TR
|
16.2.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.916/21916-g20.zip
|
The present document provides a summary of each Release 16 Feature or, whenever needed, of each significant Work Item.
The information provided in the present document is limited to an overview of each Feature, explaining briefly its purpose and the main lines of the system's behaviour to execute the Feature.
More information is available by consulting the 3GPP Portal web site, as explained in "Annex C: Process to get further information" and in the introduction section.
|
22.804
|
Study on Communication for Automation in Vertical domains (CAV)
|
TR
|
16.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.804/22804-g30.zip
|
The present document focuses on 5G communication for automation in vertical domains. This is communication that is involved in the production of and working on work pieces and goods, and/or the delivery of services in the physical world. Such communication often necessitates low latency, high reliability, and high communication service availability. Nevertheless, other types of communication are also possible in this area. Moreover, communications with low latency, high reliability, and high communication service availability, and other, not so demanding communication services, may run in parallel on the same 5G infrastructure.
The present document identifies stage 1 potential requirements for 5G communication for automation in vertical domains. The potential requirements are derived from different sources:
- existing work on dependable communication as used in vertical domains; see, for instance, IEC 61907 [2];
- use cases describing network operation in vertical domains with, for instance, common usage of the network (multi-tenancy) and network monitoring for assurance of service level agreements;
- security mechanisms already used in vertical domains; supporting the specific security requirements of vertical domains;
- new (additional to already existing stage-1 work), representative use cases in different vertical domains based on input from relevant vertical interest organisations and other stakeholders.
Furthermore, the present document provides an overview of relevant communication concepts for automation in vertical domains from the point of view of 5G systems. This overview is provided in order to facilitate the mapping between communication for automation in vertical domains and communication in 5G systems.
|
22.819
|
Feasibility Study on Maritime Communication Services over 3GPP system
|
TR
|
16.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.819/22819-g20.zip
|
The present document aims to support the maritime communication services between users ashore and at sea or between vessels at sea over 3GPP system that are targeted to improve maritime safety, protect the maritime environment and promote the efficiency of shipping by reducing maritime casualty caused by human error, in particular, involving small ships and fishing vessels. In addition, the outcome of the technical report is expected to narrow the information gap between mobile users on land and shipboard users on vessels at sea by making it possible to provide the mobile broadband services.
The document describes use cases and potential requirements for services between shore-based users such as authorities and shipboard users in the maritime radio communication environment over 3GPP system. In addition, it deals with use cases to support Mission Critical Services between authorities on land and authorities at sea (e.g. maritime police) as well as use cases to support the interworking between 3GPP system and the existing/future maritime radio communication system for the seamless service of voice communication and data communication between users ashore and at sea or between vessels at sea.
Analysis is also made on which legacy services and requirements from the existing 3GPP system need to be included and which potential requirements need additional work for new functions to support maritime communication services over 3GPP system.
|
22.821
|
Feasibility Study on LAN Support in 5G
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.821/22821-g10.zip
|
The present document describes new use cases and potential requirements applicable to the 5G system for a 3GPP network operator to support 5G LAN-type services over the 5G system (i.e. UE, RAN, Core Network, and potential application to manage the LAN-style service). In this context, 5G LAN-type services with 5G capabilities (e.g. performance, long distance access, mobility, security) allow a restricted set of UEs to communicate amongst each other.
|
22.822
|
Study on using satellite access in 5G
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.822/22822-g00.zip
|
TS 22.261 (Service requirements for next generation new services and markets) requires that the 5G system shall be able to provide services using satellite access. It further specifies that the 5G system shall support service continuity between land based 5G access and satellite based access networks owned by the same operator or by an agreement between operators.
The present document presents the results of a study on using satellite access in 5G. Use cases for the provision of services when considering the integration of 5G satellite-based access components in the 5G system are identified. This leads to the associated identification of existing / planned, as well for new, services and the corresponding modified or new requirements. The requirements on set-up / configuration / maintenance of the features of UE’s when using satellite components combined with other components from the 5G system are addressed as well as regulatory requirements when moving to (or from) satellite from (or to) terrestrial networks
|
22.823
|
Study on enhancements to IMS for new real time communication services
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.823/22823-g10.zip
|
The present document aims to develop high-level use cases and identify the related potential requirements to enable IMS to support new real time communication services.
IMS enhancements for the following scenarios are studied in this document:
• one to many communication (e.g. live broadcast video service in a stadium, concert, etc.) with efficient media negotiation;
• interworking for a UE to communicate with non-sip devices (e.g. camera), and delivery of information to control functions of the non-sip devices (e.g. PTZ);
• fast IMS call setup time for Group Communication;
• enhancements on voice & video communications for supporting AR/VR;
• network slicing for IMS;
• service visibility and usage;.
• services using AI (voiceprint) in RTC.
|
22.824
|
Study on 5G message service for MIoT
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.824/22824-g00.zip
|
The present document develops use cases of message communication for MIoT, identifies 5G Message (5GMSG) service potential requirements, and identifies potential requirements on 5G system. The use cases include the following scenarios:
- Efficient message communication
- Low delay message communication
- Group message communication
- Multicast and broadcast message communication
- High density of UEs message communication
It also provides a gap analysis between the new requirements of message communication for MIoT and the existing operator’s message services/3GPP network capabilities, and recommends the future work for the standardization of 5GMSG service for MIoT.
|
22.825
|
Study on Remote Identification of Unmanned Aerial Systems (UAS)
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.825/22825-g00.zip
|
The present document identifies the use cases and documents the derived potential requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription.
|
22.830
|
Study on business role models for network slicing
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.830/22830-g10.zip
|
The present document examines the business role models for network slicing in order to identify potential requirements that will enable a 3GPP system to adequately support those models, including:
Business role models for network slicing,
Trust relationships between MNOs and 3rd parties under various business role models,
Security relationships based on business role models,
Relationship of business role models with slice characteristics (e.g., slice scalability, slice flexibility), and
3GPP enhancements needed to support the business role models for slices.
|
22.833
|
Study on Enhancement of LTE for Efficient delivery of Streaming Service
|
TR
|
16.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.833/22833-g00.zip
|
The present document describes the use cases and provides gap analysis for identifying potential requirements for optimization of both Over-The-Top and operator managed streaming service considering new business models and existing well-known technologies e.g. caching (UE caching, in-network caching, internet CDN caching), content-aware service delivery, hybrid broadcast and unicast delivery, delay tolerate delivery (using the spare resource and/or delivery in non-busy time/hour), enhanced network sharing which covers the case that the streaming content is provided by shared RAN.
|
22.869
|
Feasibility study on enhancements of Public Warning System (PWS)
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.869/22869-g10.zip
|
The present document describes new use cases and potential requirements applicable to Public Warning Services for
- UEs with diverse form-factors whose user interface is different from the conventional mobile phones; and
- UEs that are defined by applying 3GPP system to non-ICT industry businesses (e.g. vehicles or machines such as IoT devices or robots) and have the different UE role from what 3GPP has traditionally assumed.
In addition, it considers the improvement of the understandability of the PWS message e.g. displaying language independent or graphical content to users, especially foreigners who might not understand the language used in the text or people with physical disability who may be sight impaired and unable to read the text. So it deals with user interface related potential requirements to address the presentation of the warning message considering circumstances such as language being used (e.g. international roaming scenario where the user does not understand the local language) or users with disability (e.g. people with vision impairment).
The present document does not cover use cases or potential requirements for US WEA and Japan ETWS so the results of this document are not applicable for US and Japan. This document considers national variants of EU-Alert and KPAS related service scenarios and potential requirements.
|
22.872
|
Study on positioning use cases
|
TR
|
16.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.872/22872-g10.zip
|
This technical report relates to a study on positioning use cases for both outdoor and indoor environments. It analyses positioning use cases and complements existing work on 5G use cases involving positioning needs in order to identify potential requirements for 5G positioning services.
This document also identifies new use cases, their scope and environment of use along with the related KPIs. For use cases already addressed (fully or partially) in other 3GPP studies, it consolidates and validates the KPI and assumptions.
The document further develops the identified use cases by providing some considerations on the suitability of positioning technologies to these use cases. These considerations support the identification of potential requirements that can be achieved with 3GPP positioning technologies or with a combination of 3GPP and non-3GPP positioning technologies. The use cases and performance targets are independent of specific solutions even though, in order to support these considerations, the report provides some illustrative allocation between existing positioning technologies and 3GPP new positioning technologies (e.g. NR-based).
|
22.886
|
Study on enhancement of 3GPP support for 5G V2X services
|
TR
|
16.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.886/22886-g20.zip
|
The objective of this document is to identify use cases and potential service requirements to enhance 3GPP support for V2X service in the following areas:
- Support for non-safety V2X services (also, referred to as "comfort service") (e.g. connected vehicle, mobile high data rate entertainment, mobile hot-spot/office/home, dynamic digital map update)
- Support for safety-related V2X services (e.g. autonomous driving, car platooning, priority handling between safety-related V2X services and other services)
- Support for V2X services in multiple 3GPP RATs (e.g. LTE, New RAT (NR)) and networks environment, including aspects such as interoperability with non-3GPP V2X technology (e.g. ITS-G5, DSRC, ITS-Connect)
In this document, V2X-related use cases and potential requirements already included in TR 22.891 are considered and new ones are introduced.
The identification of use cases and potential requirements covers both evolved LTE RAT and new 3GPP RAT (e.g. NR) and also covers V2X operation using 3GPP RATs where there are non-3GPP V2X technologies (e.g. ITS-G5, DSRC, ITS-Connect) in use.
|
23.715
|
Study on system enhancements for provision of access to restricted local operator services by an unauthenticated User Equipment (UE)
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.715/23715-g00.zip
|
The objective of this Technical Report is to identify and evaluate potential architecture enhancements of EPS and IMS needed to support Provision of Access to Restricted Local Operator Services by Unauthenticated UEs as identified in TS 22.101 [2], TS 22.115 [3] and TS 22.228 [4], and determine which of the solutions can proceed to normative specifications.
This feature is only applicable to EPS 3GPP access. Access to local operator services does not affect the UICC.
|
23.716
|
Study on the wireless and wireline convergence for the 5G System (5GS) architecture
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.716/23716-g00.zip
|
The objective of this study is to enhance the common 5G core network defined in TS 23.501 [2] and TS 23.502 [3] in order to support wireline access networks and Trusted N3GPP.
The key areas of the investigation are:
- Support of wireline access networks:
- Definition of the 5G Core network (5GC) with respect to wireline access functional split;
- Investigation on whether enhancements are needed to interfaces (e.g. N1, N2 and N3) used to connect wireline customer devices (CPE/Residential Gateway) and wireline access network to the converged 5GC;
- Study the impact of the common framework for authentication and security, policy and QoS, Network Slicing and investigation on whether enhancements are needed;
NOTE 1: The area of investigation for authentication and security will be limited to the part relevant to SA WG2 scope and responsibility.
- Study on how to support CPE/Residential Gateway (RG) capable of connecting via wireline and/or wireless access to the 5G CN;
- Study on how to support end user devices, with or without UICC, connected to the convergent 5GC from behind a CPE/RG;
- Identification of the impacts on mobility, session management and interaction with Access Traffic Steering, Switching and Splitting for UEs accessing the 5G convergent network studied in TR 23.793 [4] and investigation on whether enhancements are needed;
- Study on how to support CPE/RG capable of connecting simultaneously via both NG RAN and wireline access to 5GC.
NOTE 2: The above scenario is referred as Hybrid Access in Broadband Forum (BBF TR-348 [5]).
- Definition of architecture for the Trusted N3GPP scenario applicable not only to wireline accesses.
- Support of Trusted access networks:
- Requirements for the Trusted Non-3GPP access in 5G system;
- Architecture definition for the Trusted Non-3GPP access in 5G System;
- Investigation on whether enhancements are needed to interfaces (e.g. N1, N2 and N3) used to connect the trusted non-3GPP access network to converged 5GC;
- study the impact of the common framework for authentication and security, policy and QoS, Network Slicing and investigation on whether enhancements are needed.
NOTE 3: The study will consider whether "Trusted" terminology or a different terminology would be more suitable for representing the scenario where there is a more tight relationship compared to Untrusted case between the WLAN Access Network and the 5GC.
This study will follow the high level principles, agreements, and conclusions of the normative work agreed in TS 22.261 [7], TS 23.501 [1] and TS 23.502 [2].
The study will take into account information provided by the BBF on wireless and wireline convergence.
|
23.724
|
Study on Cellular Internet of Things (CIoT) support and evolution for the 5G System (5GS)
|
TR
|
16.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.724/23724-g10.zip
|
This technical report studies and evaluates architecture enhancements to address the following objectives:
Objective I: Enable CIoT/MTC functionalities in 5G CN.
The objective is to study how to support identified CioT/MTC functionalities in 5G CN with potential connectivity to WB-EUTRA (eMTC) and/or NB-IoT for 5GS capable devices.
The following CIoT/MTC functionalities need to be evaluated and studied how to enable them in 5G CN, if needed:
- Equivalent overall functionalities as provided by SCEF for CIoT/MTC.
- Monitoring.
- Small data transmission (infrequent and frequent small data transmission including frequent small data transmission from tracking devices).
- Additional power saving functions unless those are supported for 5G system in Rel-15.
- Non-IP Data Delivery.
- Overload control (as relevant in 5G CN).
- Support of Coverage enhancement including adaptations in 5G CN required to support latencies.
- Equivalent to Group communication and messaging.
- Reliable communication via functionality equivalent to SCEF.
- Inter-RAT mobility support to/from NB-IoT.
- High latency communication.
- Include location services procedures for IoT in 5G location services.
NOTE: Attach without PDN connection and non-IP PDN Connection type is already supported in 5G CN (TS 23.501 [5]).
Ensure that regulatory requirements can be fulfilled at the same level as in EPC.
Objective II: Co-existence and migration from EPC based eMTC/NB-IoT to 5GCN.
Study solutions for coexistence and migration from EPC towards 5G CN for eMTC/NB-IoT.
This objective will study solutions where the same service is offered to some UEs connected to EPC and some UEs connected to 5G CN e.g. using SCEF and equivalent functionalities in 5GCN. Solutions that assume that 5G CN needs to support EPC NAS signaling for legacy IoT devices access are not considered.
Any modifications in the EPC-5GC interworking "baseline" specific to CIOT will also be discussed as part of Objective II.
Objective III: 5G System enhancements to address 5G service requirements (based on TS 22.261 [2] and TR 38.913 [3]).
To study system architecture enhancements to address related service requirements defined in TS 22.261 [2] and RAN requirements defined in TR 38.913 [3] and how to enable them in 5G CN, if needed. At least the following service requirements have been identified:
- Enable the change of association between subscription and address/number of an IoT device within same operator and in between different operators.
- Restricted Registration procedure to allow IoT device provisioning.
Any system implications for the RAN will be coordinated with RAN WGs.
This study is not going to study enhancements to EPC.
|
23.725
|
Study on enhancement of Ultra-Reliable Low-Latency Communication (URLLC) support in the 5G Core network (5GC)
|
TR
|
16.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.725/23725-g20.zip
|
The objective of this Technical Report is to study and perform an evaluation of potential architecture enhancements for supporting URLLC services in 5G System (5GS). Specifically, the following aspects are covered:
- Investigate the key issues for meeting the URLLC requirements on latency, jitter and reliability in 5G System as defined in TS 22.261 [5].
- Study how to minimize the impacts of UE mobility to the latency and jitter between AN and CN, and within CN.
- Study how to realize transmission with reliability higher than the reliabilities of single user plane tunnel of N3 and N9 and NFs in the user plane path.
- Study how to monitor the QoS of the QoS flow with URLLC requirement.
- Study potential impacts to charging and policy control.
|
23.726
|
Study on enhancing topology of the Service Management Function (SMF) and the User Plane Function (UPF) in 5G networks
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.726/23726-g00.zip
|
The objective of this Technical Report is to study enhancements of 5GS architecture that has been defined in Rel-15 about the topology of SMF and UPF, and:
1. investigate mechanisms to enable the 3GPP system to support deployments where a SMF is not able / allowed to control UPF(s) throughout the same PLMN.
2. Study whether it is needed to enhance the capability of 5GS architecture for a UPF to be controlled by multiple SMF's (and many UPF's to be controlled by many SMFs) and, if yes, define such enhancements.
For these objectives, use cases will be defined.
|
23.727
|
Study on application awareness interworking between LTE and NR
|
TR
|
0.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.727/23727-020.zip
|
The scope is to study the mechanisms to address use cases dealing with policy driven selection of E-UTRA or NR based on certain criteria (e.g. for a given DNN or a QoS flow) associated with user applications by the core network.
Scenario 1: The E-UTRA access node and NG-RAN access node are connected to EPC and 5GC respectively.
Scenario 2: The E-UTRA access node and NR access node are connected to 5GC in a dual connectivity mode.
Potential area of study includes evaluating the mechanism available in 5G system as well as any potential enhancements that may improve the potential shortcomings identified by the study use cases.
RAN, while making use of the operator provided policies, is assumed to make final decision regarding handover/redirection/switching as RAN has the responsibility into radio and load conditions which govern the success of such a decision.
|
23.731
|
Study on enhancement to the 5GC LoCation Services (LCS)
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.731/23731-g00.zip
|
The objectives of this Technical Report are to enhance the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs) and procedures, to meet the service requirements defined in, SA WG1 (e.g. TS 22.261 [2] and TS 22.071 [3]), including the consideration of roaming and non-roaming scenarios, and access via 3GPP as well as non-3GPP access technologies (un-trusted, and trusted in TR 23.716 [9]). Of particular consideration is how to support location services in 5GS and EPS interworking scenarios, and in non-3GPP access and 3GPP access interworking scenarios.
This Technical Report will need to consider related architectures and functions developed in RAN, and implications if any.
|
23.732
|
Study on user data interworking, coexistence and migration
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.732/23732-g00.zip
|
The objective of this Technical Report is to investigate scenarios for co-existence of subscription data pertaining to legacy system (EPS) with data pertaining to the 5G system, when the HSS+UDM defined in Rel-15 is separated and both UDM and HSS are independent, and will propose solutions to support this deployment where necessary.
NOTE 1: The subscription data referred to by this Technical Report comprises both static as well as dynamic data, including IMS, LCS, SMS data.
- study diverse scenarios related to the storage of subscription data including, but not limited to, those of common repository for subscription data from EPS and 5GS, as well as separate repositories for EPS and 5GS subscription data,
- investigate the relevant procedures in TS 23.502 [2] (for e.g. authentication, mobility, handover and procedures for IMS and SMS handling in interworking between 5G system and EPS),
- determine if there is a need for interaction between the consumers of EPS and 5GS data, in the different interworking cases and deployment scenarios.
Existing procedures in TS 23.502 [2] shall not be impacted.
Provisioning aspects are outside this study.
Direct interactions between the EPS UDR and the 5GS UDR are out of the scope of this TR (i.e. it is assumed that there is no direct interaction between these two repositories).
|
23.734
|
Study on enhancement of 5G System (5GS) for vertical and Local Area Network (LAN) services
|
TR
|
16.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.734/23734-g20.zip
|
The objective and scope of this TR is to study enhancements to 5GS that are required to fulfil Stage-1 service requirements in vertical domains defined in TS 22.261 [2] and TS 22.104 [13]:
- Enablers (e.g. time synchronization of packet delivery in each hop) to support Time Sensitive Networking, and industrial control use cases specified by Stage 1.
- Architecture enhancements required to support security requirements.
NOTE 1: Security aspects will be studied in cooperation with SA WG3.
- Enhancements to the 5G system to support 5GLAN service.
- Enhancements to service exposure via APIs for 3rd party use of functionalities e.g. for information regarding the geographic location of coverage area of non-public network;
- Enablers to support new KPIs (e.g. 5QI) to meet service requirements of vertical;
- Support for non-public networks:
- Support for UEs being registered in non-public network and a PLMN when the UE supports credentials required for non-public network and credentials required for a PLMN and is able to maintain both registrations independently.
- Support for roaming, mobility and service continuity between PLMN and non-public networks (e.g. for mobility from non-public networks to PLMN) with direct interaction between non-publicnetworks and PLMN.
NOTE 2: While support for stand-alone operation of non-public network and interworking between PLMN and non-public networks is one of the objectives of the study, there is no assumption that either are required in all deployment scenarios.
NOTE 3: The objectives are subject to alignment with the corresponding normative work of TS 22.261 [2] and TS 22.104 [13] that is still ongoing in SA WG1.
|
23.735
|
Study on enhancements of Public Warning System
|
TR
|
16.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.735/23735-g00.zip
|
The present document studies and evaluates possible enhancements of Public Warning System(ePWS) to address the following objectives:
- to develop stage 2 specifications to support stage 1 requirements on ePWS as follows
1) Specify how to support the language-independent contents (e.g. non-text based icon or image mapping to a disaster). In detail, this is to specify how to map the disaster by using symbols or images so that users can recognize the disaster in their screens. (It is a useful scenario for foreigners who do not know languages.)
2) Specify how to support UEs with no user interface or UEs with a user interface that is incapable of displaying text based warning notification. In detail, there is a specific requirement on UEs with no user interface or UEs with a user interface that can not display a text based warning notification. UEs with no user interface can be IoT device and it was intended that the device performs some dedicated actions when the warning notification is received.
3) Specify how to support relay functionality for providing warning notification.
- to develop stage 3 specifications to support stage 1 requirements on ePWS.
No new functionality for US WEA and Japan ETWS will be introduced.
|
23.736
|
Study on enhancement of systems using Evolved Packet System (EPS) for Ultra Reliability and Availability using commodity equipment
|
TR
|
0.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.736/23736-020.zip
|
The objective of this Technical Report is to study the solutions and potential enhancements needed for systems using EPS to enable data services (UE to Data Network, and, UE to UE via Data Network) with one or more the following requirements:
1. Availability greater than that of a single pre-Release 16, EPC based 3GPP system with a traditional arrangement of base stations, power supplies, transmission links and core network entities.
2. Providing reliable (e.g. better than 1*10-9 undetected bit error rate) 3GPP data services with low latency (e.g. less than 15 ms between UE and application server).
Editor's note: exact requirements are still under development in SA WG1.
3. Providing prompt, deterministic recovery mechanisms following periods where the required connectivity quality of the EPS bearer was not achieved.
4. Investigating the end to end provision of 3GPP data services with low jitter, e.g. less than 100µs between UE and Data Network.
Editor's note: Exact requirements are still under development in SA WG1.
|
23.739
|
Study on enhancement of EPC for low latency communication including device mobility
|
TR
|
1.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.739/23739-100.zip
|
Low latency user plane radio links are substantially enhanced by 3GPP's NR and E-UTRAN radio technologies in Release 15. Mobility remains one of the key differentiators between 3GPP's technologies and other systems (e.g. systems that use unlicensed radio, or fixed networks). Hence it is important to network operators that mobility is effectively supported for the enhanced, low latency radio features.
As the Release 15 RAN enhancements are targeted at around 1 ms one-way radio interface latencies, this TR looks at architectural enhancements and solutions for networks where the transmission latency between the radio base station site and SGi can be around 0.1 ms to 1 ms latency (c.f. 20-200km of speed of light delay in optic fibre).
This Technical Report investigates the enhancement of EPC for low latency communication including device mobility, using the CUPS architecture (TS 23.214 [2]) and by identifying solutions based on EPC functionality (TS 23.401 [3]) in the following area:
- improvements to enable low latency following UE mobility and, possibly, following the activation of a service requiring low latency.
The aim is to retain the single SGW-C per UE concept but utilise SGW-C's "independent SGW-U per PDN connection" concept and expect to base on a "make before break" PDN connection mobility concept (with UE IP address change). To deliver low latency it is anticipated (but not mandated) that most solutions will use a combined S/PGW(-U). Anticipated investigations include:
- whether to initiate "make before break" from e.g. MME or PCRF,
- the need for e.g. PGW-C to PCRF interface extensions to support "make before break" PDN connection mobility (and if needed to support this, e.g. MME-SGW-PGW interface extensions).
Possible intermediate versions of the solutions may be maintained in this Technical Report.
|
23.740
|
Study on enhancement of network slicing
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.740/23740-g00.zip
|
The scope of this Technical Report is:
- Identify, prioritize and study the practical non-roaming and roaming deployment scenarios and system impacts when the 5GS is not able to support all possible combination of S-NSSAIs for the UE, and the aspects of mutually exclusive access to Network Slices.
- Study the possible enhancement for the Network Slicing interworking with EPC for Connected and Idle modes.
- Study how to provide Network Slice Access authentication and authorization specific for the Network Slice Access authorization that uses User Identities and Credentials different from the 3GPP SUPI and that takes place after the primary authentication which is still required between the UE and the 5GS for PLMN access authorization and authentication.
|
23.742
|
Study on Enhancements to the Service-Based Architecture
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.742/23742-g00.zip
|
This technical report studies and evaluates architecture enhancements on potential optimizations to the Release 15 Service-Based Architecture (SBA) in order to provide higher flexibility and better modularization of the 5G System for the easier definition of different network slices and to enable better re-use of the defined services. Moreover, the technical report considers mechanisms in order to better support automation and high reliability of network function service(s). The following aspects are covered:
- Optimizing the modularization of the system to improve its agility.
- Extending the service concept from 5GC control plane to the user plane function(s).
- Further improvements to service framework related aspects.
- Architectural support for highly reliable deployments, considering.
- Study backward and forward compatibility implications resulting from the above bullets.
|
23.743
|
Study on optimisations on UE radio capability signalling
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.743/23743-g00.zip
|
With the increase of the size of UE radio capabilities driven by additional bands supported by RAN specifications and UE support of significantly more band combinations, the size of the UE Radio Capabilities has and will significantly grow from Rel-15 onwards, an efficient approach to signal UE Radio Capability information is therefore needed.
This study item shall address two issues:
- Optimizations of system procedures pertaining to the transfer UE Radio Capabilities related information to RAN.
- Optimizations of system procedures related to transfer UE Radio Capabilities impacting the Core Network.
The overall goal is to study mechanisms to reduce the signalling over Uu, CN-RAN, CN-CN and RAN-RAN interfaces as well as the processing load in core and RAN (taking into account how frequently those message transfers and corresponding processing occurs) working in collaboration with RAN WGs for the related RAN interfaces and CT WG4 for the CN interfaces and NFs.
At minimum, the study shall consider the UE Radio Capabilities related aspects and any other optimisation which is deemed necessary in collaboration with RAN WGs. The study also considers scenarios where the UE radio capabilities change based on various events triggered in NAS (e.g. when certain services are not supported in one system/access and the UE wants to stay registered in another system/access, the UE may disable the radio capability for accessing the first system).
As part of the study and in coordination with other WGs especially RAN WGs it should be concluded whether to proceed with normative work.
|
23.756
|
Study for single radio voice continuity from 5G to 3G
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.756/23756-g00.zip
|
The scope of the present document is to investigate solutions from architecture point of view to support single radio voice call continuity (SRVCC) from NG-RAN to UTRAN.
Issues to be resolved will be collected and documented in the TR with a possible resolution.
|
23.778
|
Study on Mission Critical services access aspects
|
TR
|
16.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.778/23778-g00.zip
|
This technical report is a study of mission critical service access aspects. The present document identifies architecture enhancements needed to support mission critical services delivered over IOPS, based on the stage 1 requirements, including 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4], 3GPP TS 22.282 [5] and 3GPP TS 22.346 [6].
This document provides recommendations for normative work.
|
23.784
|
Study on discreet listening and logging for mission critical services
|
TR
|
16.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.784/23784-g00.zip
|
The present document studies solutions to satisfy the requirements for discreet listening and logging for mission critical services. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical services. Requirements for this study are taken from the Stage 1 requirements, including 3GPP TS 22.280 [2], and 3GPP TS 22.281 [3].
|
23.786
|
Study on architecture enhancements for the Evolved Packet System (EPS) and the 5G System (5GS) to support advanced V2X services
|
TR
|
16.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.786/23786-g10.zip
|
The objective of this Technical Report is to identify and evaluate potential architecture enhancements of EPS and 5G System design needed to support advanced V2X services identified in TR 22.886 [2], based on vehicular services requirements defined in TS 22.185 [3] and TS 22.186 [4] and determine which of the solutions can proceed to normative specifications.
In Rel-15, the study focuses on EPS.
|
23.787
|
Study on encrypted traffic detection and verification
|
TR
|
0.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.787/23787-040.zip
|
The scope is to study encrypted traffic detection and verification, including:
- Solutions for encrypted traffic detection and verification.
- Solutions for how to manage the information for encrypted traffic detection and verification.
|
23.791
|
Study of enablers for Network Automation for 5G
|
TR
|
16.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.791/23791-g20.zip
|
The aim of this Technical Report is to study and specify how to collect data and how to feedback data analytics to the network functions.
|
23.792
|
Study on MBMS APIs for Mission Critical Services
|
TR
|
16.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.792/23792-g00.zip
|
The present document is a technical report that identifies the MBMS API solutions on the UE for mission critical applications to access MBMS bearer service for the usage of mission critical services. The aspects of the study include identifying functional requirements, methods and message flows, client reference model, potential impacts to MC system architecture, and the review of existing and new MBMS capabilities for use by MC services.
|
23.793
|
Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture
|
TR
|
16.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.793/23793-g00.zip
|
The purpose of this document is to study how the 5G System (5GS) can be extended in order to support Access Traffic Steering, Switching and Splitting (ATSSS) between 3GPP and non-3GPP access networks. In particular, this document considers solutions that specify the following:
- How the 5GC and the 5G UE can support multi-access traffic steering (as defined in clause 3.1) between 3GPP and non-3GPP accesses.
- How the 5G Core network and the 5G UE can support multi-access traffic switching (as defined in clause 3.1) between 3GPP and non-3GPP accesses. This includes the conditions that can trigger the switching of data traffic to a new access type.
- How the 5G Core network and the 5G UE can support multi-access traffic splitting (as defined in clause 3.1) between 3GPP and non-3GPP accesses (multi access PDU session). This includes the conditions that can trigger the splitting of data traffic across multiple accesses.
- How the multi-access traffic steering, switching and splitting (ATSSS) can be taken into account by the charging framework in order e.g. to enable the network operator to differentiate charging for data traffic that is switched and/or split between 3GPP and non-3GPP accesses.
- How the policy framework can be extended in order to support the requirements for ATSSS.
- How ATSSS can be supported by using multi-access PDU sessions (as defined in clause 3.1). ATSSS solutions not requiring multi-access PDU sessions can also be considered.
- How to handle issues related to ATSSS that may occur when the UE moves between EPC and 5GC.
The scope of this document excludes the following aspects:
- Changes to the charging framework are not considered. However, it may be considered what information needs to be provided to the charging framework in order to charge traffic that is switched and/or split between 3GPP and non-3GPP accesses.
- ATSSS procedures that may be applied in the NG-RAN are not considered. The study is restricted only to ATSSS procedures applied in the 5G core network.
- 5GS enhancements to support trusted non-3GPP access networks are not considered.
- 5GS enhancements to support wireline access networks are not considered.
All solutions in this document should be based on and aligned with the 5GS Phase-1 normative work including work on policy management, as documented in TS 23.501 [5], TS 23.502 [6] and TS 23.503 [7].
The study in this document is organized into two phases:
- Initially, the study considers ATSSS solutions that enable traffic selection, switching and splitting between NG-RAN and untrusted non-3GPP access networks.
- Subsequently, after the 5GS architecture is enhanced to support trusted non-3GPP access networks, the study will also consider ATSSS solutions that enable traffic selection, switching and splitting between NG-RAN and trusted non-3GPP access networks.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.