id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
33.898
|
Study on security and privacy of Artificial Intelligence/Machine Learning (AI/ML)-based services and applications in 5G
|
TR
|
18.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.898/33898-i01.zip
|
The present document will study, based on requirements as specified in clauses 6.40 and 7.10 of TS 22.261 [2] and architecture and key issues captured in TR 23.700-80 [3], 5GS assistance to support Artificial Intelligence (AI) / Machine Learning (ML) model distribution, transfer, training for various applications, e.g. video/speech recognition, robot control, automotive, etc.
The scope of this study is on how to provide security and privacy to the AI/ML-based service and applications in 5G based on the following objectives of identifying key issues, potential threats, requirements, and solutions to enable:
1. 5G system assistance for the security management which requires data transmission support for application layer AI/ML operation over the 5G system.
2. The authentication and authorization involving data collection and sharing among UE, AF and the network to take part in application layer AI/ML operation, i.e., UE and network privacy protections to support application AI/ML services over 5G system.
3. UE and 5G system to secure AI/ML based services and operations.
4. Secure provisioning of the external parameter required for AI/ML (e.g., expected UE activity behaviors, expected UE mobility, etc.)
|
35.240
|
Specification of the Snow 5G based 256-bits algorithm set: specification of the 256-NEA4 encryption, the 256-NIA4 integrity, and the 256-NCA4 authenticated encryption algorithm for 5G; Document 1: algorithm specification
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.240/35240-i00.zip
|
The present document contains the algorithm specification which could be used as the encryption and integrity protection function 256-NEA4, 256-NIA4 and the combined authenticated encryption 256-NCA4 protection function for 3GPP systems.
|
35.241
|
Specification of the Snow 5G based 256-bits algorithm set: Specification of the 256-NEA4 encryption, the 256-NIA4 integrity algorithm, and the 256-NCA4 authenticated encryption algorithm for 5G; Document 2: implementation test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.241/35241-i00.zip
|
The present document contains the implementation test data of the encryption and integrity protection function 256-NEA4, 256-NIA4 and the combined authenticated encryption 256-NCA4 protection function for 3GPP systems.
|
35.242
|
Specification of the Snow 5G based 256-bits algorithm set: Specification of the 256-NEA4 encryption, the 256-NIA4 integrity, and the 256-NCA4 authenticated encryption algorithm for 5G; Document 3: design conformance test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.242/35242-i00.zip
|
The present document contains the design conformance test data of the encryption and integrity protection function 256-NEA1, 256-NIA1 and the combined authenticated encryption 256-NCA1 protection function for 3GPP systems.
|
35.243
|
Specification of the AES based 256-bits algorithm set: Specification of the 256-NEA5 encryption, the 256-NIA5 integrity, and the 256-NCA5 authenticated encryption algorithm for 5G; Document 1: algorithm specification
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.243/35243-i00.zip
|
The present document contains the algorithm specification which could be used as the encryption and integrity protection function 256-NEA5, 256-NIA5 and the combined authenticated encryption 256-NCA5 protection function for 3GPP systems.
|
35.244
|
Specification of the AES based 256-bits algorithm set: Specification of the 256-NEA5 encryption, the 256-NIA5 integrity, and the 256-NCA5 authenticated encryption algorithm for 5G; Document 2: implementation test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.244/35244-i00.zip
|
The present document contains the implementation test data of the encryption and integrity protection function 256-NEA5, 256-NIA5 and the combined authenticated encryption 256-NCA5 protection function for 3GPP systems.
|
35.245
|
Specification of the AES based 256-bits algorithm set: Specification of the 256-NEA5 encryption, the 256-NIA5 integrity, and the 256-NCA5 authenticated encryption algorithm for 5G; Document 3: design conformance test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.245/35245-i00.zip
|
The present document contains the design conformance test data of the encryption and integrity protection function 256-NEA5, 256-NIA5 and the combined authenticated encryption 256-NCA5 protection function for 3GPP systems.
|
35.247
|
Specification of the ZUC based 256-bits algorithm set: Specification of the 256-NEA6 encryption, the 256-NIA6 integrity, and the 256-NCA6 authenticated encryption algorithm for 5G; Document 2: implementation test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.247/35247-i00.zip
|
The present document contains the implementers’ test data of the encryption and integrity protection function 256-NEA6, 256-NIA6 and the combined authenticated encryption 256-NCA6 protection function for 3GPP systems.
|
35.248
|
Specification of the ZUC based 256-bits algorithm set: Specification of the 256-NEA6 encryption, the 256-NIA6 integrity, and the 256-NCA6 authenticated encryption algorithm for 5G; Document 3: design conformance test data
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.248/35248-i00.zip
|
The present document contains the design conformance test data of the encryption and integrity protection function 256-NEA6, 256-NIA6 and the combined authenticated encryption 256-NCA6 protection function for 3GPP systems.
|
36.579-5
|
Mission Critical (MC) services over LTE; Part 5: Abstract test suite (ATS)
|
TS
|
18.3.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.579-5/36579-5-i30.zip
|
The present document specifies the protocol and signalling conformance testing in TTCN-3 for the Mission Critical services over LTE signalling and protocol requirements defined by 3GPP.
The following TTCN test specification and design considerations can be found in the present document:
- the test system architecture;
- the overall test suite structure;
- the test models and ASP definitions;
- the test methods and usage of communication ports definitions;
- the test configurations;
- the design principles and assumptions;
- TTCN styles and conventions;
- the partial Implementation eXtra Information for Testing (IXIT) proforma;
- the test suites.
The Abstract Test Suites designed in the document are based on the test cases specified in 3GPP TS 36.579-2 [3], TS 36.579-6 [59] and TS 36.579-7 [60]. The test cases specified in 3GPP TS 36.579-3 [4] are out of scope of the present document.
The applicability of the individual test cases is specified in the test ICS proforma specification in 3GPP TS 36.579-4 [5]). Where appropriate the Abstract Test Suites belonging to the present specification may refer to other Abstract Test Suites e.g. 3GPP TS 36.523-3 [27] for test requirements related to the EPS (LTE) bearers which carry the Mission Critical services data.
The present document is valid for TTCN development for Mission Critical services clients' conformance tests according to 3GPP Releases starting from Release 14 up to the Release indicated on the cover page of the present document.
|
36.718-02-01
|
Rel-18 LTE Advanced Carrier Aggregation for x bands (1<= x<=6) DL with y bands (y=1,2) UL
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.718-02-01/36718-02-01-i00.zip
|
The present document is a technical report on intra-band CA and inter-band CA for x bands DL (2≤x≤6) with y bands UL (y=1,2) under Rel-18 timeframe.
The purpose is to gather the relevant background information and studies, in order to address Rel-18 band combinations that are related to x bands (1≤x≤6) DL with y bands UL (y=1,2) bands UL CA requirements. The band combinations are requested in the Excel file of the WID [2] or its revisions.
|
36.770
|
High Power UE (Power Class 2) for LTE FDD Band 14
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.770/36770-i00.zip
|
The present document is a technical report for High Power UE (power class 2) for LTE FDD Band 14. The purpose is to gather the relevant background information and outcome of evaluations to complete the band specific requirements.
|
36.792
|
Summary of regulatory requirements on unwanted emissions for transmission over broadcast bands in UHF spectrum
|
TR
|
18.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.792/36792-i10.zip
|
This Technical Report provides specific spectrum limit masks for digital terrestrial television broadcasting systems specified in Recommendation ITU-R BT.1206 [2]. While Recommendation ITU-R SM.1541 [9] provides out-of-band domain emission limits that should be regarded as generic spectrum limit masks, specific spectrum limit masks might be required for specific environments to enhance compatibility with other radiocommunication services.
|
36.903
|
Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test tolerances for Radio Resource Management (RRM) conformance tests
|
TR
|
18.5.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.903/36903-i50.zip
|
The present document specifies a general method used to derive Test Tolerances for Radio Resource Management tests, and establishes a system for relating the Test Tolerances to the measurement uncertainties of the Test System.
The test cases which have been analysed to determine Test Tolerances are included as .zip files.
The present document is applicable from Release 8 up to the release indicated on the front page of the present Terminal conformance specifications.
|
36.904
|
Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Derivation of test tolerances for User Equipment (UE) radio reception conformance tests
|
TR
|
18.1.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.904/36904-i10.zip
|
The present document specifies a general method used to derive Test Tolerances for UE radio reception conformance tests in 3GPP TS 36.521-1 [2] and TS 36.521-4 [4] and establishes a system for relating the Test Tolerances to the measurement uncertainties of the Test System.
The test cases which have been analysed to determine Test Tolerances are included as .zip files.
The present document is applicable from Release 10 up to the release indicated on the front page of the present Terminal conformance specifications.
|
37.718-00-00
|
Rel-18 SUL Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP)
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.718-00-00/37718-00-00-i00.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-18 time frame. The purpose is to gather the relevant background information and studies in order to address NR SUL for the Rel-18 bands/band combinations in Table 1-1 to Table 1-4.
Table 1-1: Release 18 SUL bands
Band number
UL
DL
Duplex mode
Table 1-2: Release 18 SA SUL band combinations
SA SUL band combination
REL independent from
CA_n1_SUL_n78-n81
Rel-15
CA_n3_SUL_n41-n80
Rel-15
CA_n41_SUL_n79-n98
Rel-15
CA_n79_SUL_n41-n98
Rel-15
CA_n41_SUL_n79-n95
Rel-15
CA_n79_SUL_n41-n95
Rel-15
CA_n8_SUL_n78-n81
Rel-15
SUL_n1-n81
Rel-15
SUL_n3-n84
Rel-15
SUL_n1-n89
Rel-15
SUL_n1-n80
Rel-15
SUL_n78-n89
Rel-15
CA_n78_SUL_n1-n81
Rel-15
CA_n78_SUL_n3-n84
Rel-15
CA_n78_SUL_n1-n89
Rel-15
CA_n78_SUL_n1-n80
Rel-15
SUL_n5-n84
Rel-15
SUL_n8-n84
Rel-15
CA_n5_n78-n84
Rel-15
CA_n78_n5-n84
Rel-15
CA_n1_n78-n89
Rel-15
CA_n3_n78-n84
Rel-15
CA_n8_n78-n84
Rel-15
CA_n78_n8-n84
Rel-15
Table 1-3: Release 18 NSA SUL band combinations
NSA SUL band combination
REL independent from
Table 1-4: Release 18 NSA SUL with ULSUP band combinations
NSA SUL with ULSUP band combination
REL independent from
This TR contains a general part and specific band combination part. The actual requirements are added to the corresponding technical specifications.
|
37.718-11-11
|
Rel-18 Dual Connectivity (DC) of 1 band LTE (1DL/1UL) and 1 NR band (1DL/1UL)
|
TR
|
18.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.718-11-11/37718-11-11-i10.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-18 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-18 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 18 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) within FR1
DC combination
Uplink EN-DC configuration
DC_3(n)AA
DC_3(n)AA1
DC_8B_n78A
DC_8A_n78A
DC_8B_n78A
DC_3C_n28A
DC_3C_n28A
DC_1A_n26A
DC_1A_n26A
DC_3A_n26A
DC_3A_n26A
DC_3C_n26A
DC_3A_n26A
DC_3C_n26A
DC_7A_n26A
DC_7A_n26A
DC_7C_n26A
DC_7A_n26A
DC_7C_n26A
DC_28A_n20A
DC_28A_n20A
DC_1A_n1A
DC_1A_n1A1
DC_28A_n38A
DC_28A_n38A
DC_8A_n38A
DC_8A_n38A
DC_5A_n25A
DC_5A_n25A
DC_5A_n41A
DC_5A_n41A
DC_71A_n25A
DC_71A_n25A
DC_7A_n12A
DC_7A_n12A
DC_71A_n7A
DC_71A_n7A
DC_1A_n105A
DC_1A_n105A
DC_3A_n105A
DC_3A_n105A
DC_7A_n105A
DC_7A_n105A
DC_71A_n12A
DC_71A_n12A1
DC_5A_n28A
DC_5A_n28A
DC_14A_n41A
DC_14A_n41A
DC_40A_n3A
DC_40A_n3A
DC_40A_n7A
DC_40A_n7A
DC_20A_n40A
DC_20A_n40A
DC_8B_n1A
DC_8B_n1A
DC_41A_n79C
DC_41A_n79C
DC_28A_n105A
DC_28A_n105A1
NOTE 1: Only single switched UL is supported
Table 1-2: Release 18 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) including FR2
DC combination
Uplink EN-DC configuration
Table 1-3: Release 18 NE-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) within FR1
DC combination
Uplink NE-DC configuration
DC_n40A_42A
DC_n40A_42C
DC_n40A_42D
DC_n40A_42A
Table 1-4: Release 18 NE-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) including FR2
DC combination
Uplink NE-DC configuration
|
37.718-11-21
|
Rel-18 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
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.718-11-21/37718-11-21-i00.zip
|
The present document is a technical report for Rel-18 DC of x bands (x=1,2,3,4) LTE inter-band CA (xDL/1UL) and 2 bands NR inter-band CA (2DL/1UL) under Rel-18 time frame. The purpose is to gather the relevant background information and studies to address DC band combinations of inter-band CA for LTE xDL/1UL (x=1,2,3,4) and inter-band CA for NR 2DL/1UL in Rel-18 as shown in Table 1-1.
Table 1-1: Release 18 Dual Connectivity band combination of LTE xDL/1UL (x=1,2,3,4) + inter-band NR 2DL/1UL
Combination
LTE X Bands (x=1,2,3,4) Combinations
NR 2 Bands Combinations
LTE 1 Band
Band x
CA_nY-nZ
LTE 2 Bands
CA_w-x
CA_nY-nZ
LTE 3 Band
CA_v-w-x
CA_nY-nZ
LTE 4 Bands
CA_u-v-w-x
CA_nY-nZ
This TR contains a general part and band-specific combination part. The actual requirements are added to the corresponding technical specifications.
|
37.718-21-11
|
Dual Connectivity of 2 bands LTE inter-band CA and 1 NR band
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.718-21-11/37718-21-11-i00.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-18 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-18 band combinations. The actual requirements are added to the corresponding technical specification.
|
37.829
|
High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands and NR bands for Rel-18
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.829/37829-i00.zip
|
The present document is a technical report for release 17 and release 18 basket WI High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands and NR bands, based on WID in [9].
|
37.877
|
Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx switching
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.877/37877-i00.zip
|
The present document is a technical report for WI “Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink” under Rel-18 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 in uplink listed in Table 1-1.
Table 1-1: Band combinations requested for mandating no DL interruption
Configuration
Uplink configuration
CA_n1-n5-n78
CA_n1-n78, CA_n5-n78
CA_n3-n5-n78
CA_n3-n78, CA_n5-n78
|
37.878
|
Rel-18 Band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.878/37878-i00.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 in Release 18.
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-18. 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 18 NR V2X band combinations
V2X Band combination
REL independent from
V2X_n3-n47
Rel-16
V2X_n34-n47
Rel-16
V2X_n3_47
Rel-16
V2X_n34_47
Rel-16
V2X_34_n47
Rel-16
Note: All band combinations in table 1-1 that are release independent from Rel-16 are optional
|
37.900
|
Radio Frequency (RF) requirements for Multicarrier and Multiple Radio Access Technology (Multi-RAT) Base Station (BS)
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.900/37900-i00.zip
|
The present document is the technical report for the work item on Multi-Standard Radio (MSR), which was approved at TSG RAN#41. The objective of the WI is to first identify relevant scenarios and then write an RF requirements specification that is applicable to Multi-Standard Radio (MSR) Base Station with multiple carriers and/or multiple 3GPP Radio Access Technologies (RAT).
|
37.941
|
Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements
|
TR
|
18.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.941/37941-i30.zip
|
The present document is the Technical Report for the Work Item on Over The Air (OTA) Base Station (BS) testing.
This Technical Report covers background information of OTA testing methods, measurement uncertainty and test tolerance values derivation for the radiated conformance testing requirements. This Technical Report covers radiated conformance testing requirements for the following BS types:
- Hybrid AAS BS as specified in AAS BS radiated testing specification TS 37.145-2 [4] for the following radio technologies:
- Hybrid AAS BS in single RAT UTRA operation, TDD
- Hybrid AAS BS in single RAT UTRA operation, FDD
- Hybrid AAS BS in single RAT E-UTRA operation
- Hybrid AAS BS in MSR operation implementing any of the above RATs, including NR operation.
- OTA AAS BS as specified in AAS BS radiated testing specification TS 37.145-2 [4] for the following radio technologies:
- OTA AAS BS in single RAT UTRA operation, FDD
- OTA AAS BS in single RAT E-UTRA operation
- OTA AAS BS in MSR operation implementing any of the above RATs, and/or NR.
- BS type 1-H in single RAT NR operation in FR1, as specified in NR BS radiated testing specification TS 38.141-2 [6],
- BS type 1-O in single RAT NR operation in FR1, as specified in NR BS radiated testing specification TS 38.141-2 [6],
- BS type 2-O in single RAT NR operation in FR2, as specified in NR BS radiated testing specification TS 38.141-2 [6].
Generic term "BS" is used to refer to any of these BS types, unless otherwise stated.
This 3GPP external Technical Report consolidates the OTA measurement related information originating from multiple AAS BS and NR BS internal technical reports. This information is needed to supplement the BS radiated testing specifications as a single, 3GPP external technical report, such that the information can be referred to from external specifications and bodies.
The NR BS specification refers to two frequency ranges, FR1 and FR2. The AAS BS specification is only applicable for operating bands within FR1. Thus, sections in this report referring to FR2 should be considered as applicable to NR only.
|
38.423
|
NG-RAN; Xn Application Protocol (XnAP)
|
TS
|
18.6.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.423/38423-i60.zip
|
The present document specifies the radio network layer signalling procedures of the control plane between NG-RAN nodes in NG-RAN. XnAP supports the functions of the Xn interface by signalling procedures defined in this document. XnAP is developed in accordance to the general principles stated in TS 38.401 [2] and TS 38.420 [3].
|
38.509
|
5GS; Special conformance testing functions for User Equipment (UE)
|
TS
|
18.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.509/38509-i00.zip
|
The present document defines for User Equipment (UE) those special functions and their activation/deactivation methods that are required in the UE for conformance testing purposes when the UE is connected to the 5G System (5GS) via its radio interface(s).
The document also describes the operation of these special functions when the 5GS capable UEs are connected via a non-5GS system e.g. E-UTRA FDD or TDD system.
Depending on the 5GS system's architecture some relevant for the UE for conformance testing special functions may be defined in TS 36.509 [6].
|
38.561
|
NR; User Equipment (UE) conformance specification; UE TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements and test methodologies for FR1 (NR SA and EN-DC)
|
TS
|
18.3.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.561/38561-i30.zip
|
The present document specifies details of conformance testing of UE TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements and test methodologies for FR1 (NR SA and EN-DC).
|
38.718-00-02
|
NR Carrier Aggregation band combinations with two SUL cells
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-00-02/38718-00-02-i00.zip
|
The present document is a technical report on NR carrier aggregation band combinations with two SUL cells under Rel-18 timeframe. The purpose is to gather the relevant background information and studies in order to address carrier aggregation band combinations with two SUL cells for the Rel-18 band combinations in Table 1-1 and Table 1-2.
|
38.718-01-01
|
Rel-18 NR intra band Carrier Aggregation for xCC DL/yCC UL including contiguous and non-contiguous spectrum (x>=y)
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-01-01/38718-01-01-i00.zip
|
The present document is a technical report for NR Intra-band Carrier Aggregation Rel-18 for xDL/yUL including contiguous and non-contiguous spectrum under Rel-18 time frame. The purpose is to gather the relevant background information and studies to address NR Intra-band Carrier Aggregation requirements for the Rel-18 band combinations in Table 1-1, Table 1-2, Table 1-3 and Table 1-4.
|
38.718-02-01
|
NR inter-band Carrier Aggregation/Dual connectivity for 2 bands DL with x bands UL (x=1,2)
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-02-01/38718-02-01-i00.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-18 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-18 band combinations.
This TR contains the RF requirements of band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.718-03-01
|
NR inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with x bands UL(x=1,2)
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.718-03-01/38718-03-01-i00.zip
|
The present document is a technical report for power class 3 NR inter-band CA and DC for 3 bands DL with up to 2 bands UL under Rel-18 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 up to 2 bands UL for the Rel-18 band combinations.
This TR contains the RF requirements of band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
38.751
|
UE RF requirement for NR frequency range 2 (FR2) multi-Rx chain DL reception
|
TR
|
18.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.751/38751-i30.zip
|
The objectives for NR frequency range 2 (FR2) multi-Rx chain DL reception from RF perspective are as follows.
- Introduce necessary requirement(s) for enhanced FR2-1 UEs with simultaneous DL reception with two different QCL TypeD RSs on single component carrier with up to 4 layer DL MIMO
- Enhanced RF requirements:
- Specify RF requirements, mainly spherical coverage requirements, for devices with simultaneous reception from different directions with different QCL TypeD RSs
- The legacy spherical coverage requirement for reception from a single direction will be kept
- PC3 will be prioritized, other power classes should be considered after the PC3 requirements framework is finalized
|
38.761
|
Measurements of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of User Equipment (UE)
|
TR
|
18.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.761/38761-i30.zip
|
The present document is a Technique Report for Measurements of Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance of User Equipment (UE). It includes analysis and measurement results of MIMO OTA in Frequency Range 1 and Frequency Range 2, such as verification of channel models, lab alignment activities, etc..
|
38.786
|
User Equipment (UE) radio transmission and reception for NR sidelink evolution
|
TR
|
18.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.786/38786-i20.zip
|
The present document is a technical report for NR sidelink evolution services in Rel-18. The purpose is to specify radio solutions that are necessary for NR to support sidelink services working on unlicensed spectrums.
|
38.822
|
NR; User Equipment (UE) feature list
|
TR
|
18.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.822/38822-i00.zip
|
The present document provides the list of UE features for NR. For each NR UE feature, the corresponding field name of UE capability, as specified in TS 38.331 [2], TS 37.355 [9] and TS 38.355 [23] is also captured in this document. The Release 15 UE feature list described in clause 4 reflects the status of Release 15 in June 2019 and has not been maintained after this date. The Release 16 UE feature list described in clause 5 reflects the status of Release 16 in December 2022 and has not been maintained after this date. The Release 17 UE feature list described in clause 6 reflects the status of Release 17 in June 2023 and has not been maintained after this date. The Release 18 UE feature list described in clause 7 reflects the status of Release 18 in March 2025 and has not been maintained after this date.
|
38.835
|
Study on XR enhancements for NR
|
TR
|
18.0.1
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.835/38835-i01.zip
|
The present document is intended to capture the output of the study item on XR Enhancements for NR [10], which aims at investigating power saving and capacity enhancements techniques tailored for XR services, as well as means to provide XR-awareness in RAN.
This study follows a series of earlier studies conducted in 3GPP by SA1 [2], SA4 [5] [6] [7] and RAN1 [8]. It is complemented by work in SA2 [12], SA4 [11] and SA6 [4].
|
38.844
|
Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidth
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.844/38844-i00.zip
|
The present document is the Technical Report of the Study Item on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths, approved at TSG RAN #89-e [2]. The purpose of this document is to capture and document the outcome of the objectives stated in the SID.
|
38.846
|
Study on simplification of band combination specification
|
TR
|
18.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.846/38846-i10.zip
|
The present document is a technical report for simplification of band combination specification for NR and LTE. The purpose of this TR is to further optimize and improve the working procedure for specifying band combination. A technical report will be created to collect the rules of band combination during the timescale of Rel-18 so as to improve the efficiency of band combination specifying and the quality of specifications. The dependency and applicability for RF requirements among different features for the same spectrum combination to reduce the redundant tests will also be investigated in the TR. The valid rules and valuable guidelines for requesting and specifying band combinations in Rel-17 TR 38.862 [7] are captured in the TR.
|
38.848
|
Study on Ambient IoT (Internet of Things) in RAN
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.848/38848-i00.zip
|
The present document reports on the feasibility of meeting the design targets for relevant use cases of a new 3GPP IoT technology, on the basis of suitable deployment scenarios in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for very-low end IoT applications. It intends to provide a clear differentiation, i.e. addressing use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP LPWA IoT technology.
In terms of energy storage, the study considers the following device characteristics:
- Pure batteryless devices with no energy storage capability at all, and completely dependent on the availability of an external source of energy.
- Devices with limited energy storage capability that do not need to be replaced or recharged manually.
|
38.849
|
Introduction of 6GHz NR unlicensed operation
|
TR
|
18.5.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.849/38849-i50.zip
|
The present document is a technical report for Work Item on New Radio (NR) Access Technology, covering introduction of lower 6GHz NR unlicensed operation for Europe (NR_6GHz_unlic_EU) and in the 5925-7125 MHz range for other regions (NR_6GHz_unlic_full).
|
38.850
|
Rel-18 High power UE (power class 2) for FR1 NR FDD band in UL of NR inter-band CA/DC combinations with y bands downlink (y=2,3,4,5,6) and x bands uplink (x=1)
|
TR
|
18.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.850/38850-i10.zip
|
The present document is a technical report for Rel-18 High power UE (power class 2) for FR1 NR FDD band in UL of NR inter-band CA/DC combinations with y bands downlink (y=2,3,4,5,6) and x bands uplink (x=1) under Rel-18 time-frame. The purpose is to gather the relevant background information and studies in order to complete the band combination specific requirements for the newly requested band combinations.
|
38.854
|
NR support for high speed train scenario in frequency range 2 (FR2)
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.854/38854-i00.zip
|
The present document is a technical report for Rel-17 NR support for high speed train scenario in FR2.
|
38.858
|
Study on evolution of NR duplex operation
|
TR
|
18.2.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.858/38858-i20.zip
|
The present document captures the results and findings from the study item "Study on Evolution of NR Duplex Operation " [2]. The purpose of this TR is to document the follows for evolution of NR duplex operation:
- applicable and relevant deployment scenarios.
- evaluation methodology and assumptions.
- possible schemes/enhancements, feasibility and performance evaluation results of subband non-overlapping full duplex and dynamic/flexible TDD.
- summary of the regulatory aspects that have to be considered for deploying the identified duplex enhancements in TDD unpaired spectrum.
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.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] RP-213591, New SI: Study on evolution of NR duplex operation.
[3] 3GPP TR 38.901: "Study on channel model for frequencies from 0.5 to 100 GHz".
[4] 3GPP TR 36.843: "Study on LTE Device to Device Proximity Services; Radio Aspects".
[5] 3GPP TR 38.802: "Study on New Radio Access Technology Physical Layer Aspects".
[6] 3GPP TR 36.873: "3D channel model for LTE".
[7] 3GPP TR 36.814: "Further advancements for E-UTRA physical layer aspects".
[8] 3GPP TR 36.889: "Study on Licensed-Assisted Access to Unlicensed Spectrum".
[9] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
[10] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone".
[11] Report ITU-R M.2412: "Guidelines for evaluation of radio interface technologies for IMT-2020".
[12] RP-180524, Summary of calibration results for IMT-2020 self evaluation.
[13] 3GPP TR 38.830: "Study on NR coverage enhancements".
[14] R1-2304212, Summary on SLS calibration results for NR duplex evolution
[15] R1-2307274, On evaluations for NR duplex evolution, Apple
[16] R1-2307083, SBFD evaluation results, CATT
[17] R1-2307192, Evaluation on NR duplex evolution, CMCC
[18] R1-2307324, Evaluation of NR duplex evolution, Ericsson
[19] R1-2308336, Discussion on evaluation and methodologies on evolution of NR duplex operation, Huawei, HiSilicon
[20] R1-2306695, Discussion on evaluations on NR duplex evolution, InterDigital, Inc.
[21] R1-2306885, Study on Evaluation for NR duplex evolution, LG Electronics
[22] R1-2306814, Discussion on evaluation of NR duplex evolution, MediaTek Inc.
[23] R1-2306400, Discussion for Evaluation on NR duplex evolution, New H3C Technologies Co., Ltd.
[24] R1-2306874, On the evaluation methodology for NR duplexing enhancements, Nokia, Nokia Shanghai Bell
[25] R1-2307571, Discussion on evaluation on NR duplex evolution, OPPO
[26] R1-2307922, On Deployment scenarios and evaluation Methodology for NR duplex evolution, Qualcomm Incorporated
[27] R1-2306642, Discussion on evaluation on NR duplex evolution, Spreadtrum Communications, BUPT, New H3C
[28] R1-2307674, Discussion on evaluation for NR duplex evolution, Samsung
[29] R1-2307817, Evaluation of NR duplex evolution, Sharp
[30] R1-2306906, SBFD System Level Simulation Results, Sony
[31] R1-2307381, Discussion on evaluation on NR duplex evolution, Xiaomi
[32] R1-2306981, Prototype and Simulation Results for SBFD, ZTE
[33] R1-2306746, Evaluation on NR duplex evolution, vivo
[34] R1-2308001, LLS for evaluation of coverage performance in TDD and SBFD systems, CEWiT
[35] R1-2308101, Evaluation on NR duplex operation, China Unicom, Huawei, HiSilicon
[36] R1-2307471, Discussion on evaluation on NR duplex evolution, NTT DOCOMO, INC.
[37] R1-2307330, Discussion on evaluation on NR duplex evolution, Panasonic
[38] R1-2307159, Evaluation on NR duplex evolution, Fujitsu
[39] R1-2306835, Evaluations on NR Duplex Evolution, Intel Corporation
[40] R1-2307084, Discussion on subband non-overlapping full duplex, CATT
[41] R1-2307325, Subband non-overlapping full duplex, Ericsson
[42] R1-2307619, Field test for dynamic/flexible TDD, China Telecom, ZTE
[43] R1-2306983, Discussion of enhancements on dynamic/flexible TDD, ZTE, China Telecom
[44] R1-2307326, Potential enhancements of dynamic TDD, Ericsson
[45] R1-2305035, SBFD System Level Simulation Results, Sony
[46] R4-2214376, Reply LS on interference modelling for duplex evolution, Samsung, CMCC, Qualcomm
[47] R4-2220244, WF for the feasibility from BS aspect, Samsung
[48] R4-2300690, Further considerations on SBFD BS RF aspects, Nokia, Nokia Shanghai Bell
[49] R4-2305917, WF on implementation feasibility of SBFD: Co-channel Co-site/inter-site interference, Ericsson
[50] R4-2219633, BS RF feasibility considerations, Ericsson
[51] ECC Report 281, Analysis of the suitability of the regulatory technical conditions for 5G MFCN operation in the 3400-3800 MHz band, approved 6 July 2018. Online available: https://docdb.cept.org/download/3419
[52] ECC Recommendation(20)03, Frame structures to facilitate cross-border coordination of TDD MFCN in the frequency band 3400-3800 MHz, approved 23 October 2020. Online available: https://docdb.cept.org/download/1738
[53] ECC Report 331, Efficient usage of the spectrum at the border of CEPT countries between TDD MFCN in the frequency band 3400- 3800 MHz, approved 05 November 2021. Online available: https://docdb.cept.org/download/3515
[54] ECC Decision(11)06, Harmonised frequency arrangements and least restrictive technical conditions (LRTC) for mobile/fixed communications networks (MFCN) operating in the band 3400-3800 MHz, amended 26 October 2018. Online available: https://docdb.cept.org/download/1531
[55] FCC-21-32, "FCC Opens 100 Megahertz of Mid-Band Spectrum for 5G," March 2021. Online available: https://www.fcc.gov/document/fcc-opens-100-megahertz-mid-band-spectrum-5g-0
[56] FCC, "Part 27 – Miscellaneous Wireless Communications Services," last amended on August 7, 2023. Online available: https://www.ecfr.gov/current/title-47/chapter-I/subchapter-B/part-27
[57] FCC, "Part 96 – Citizens Broadband Radio Service," last amended on August 7, 2023. Online available: https://www.ecfr.gov/current/title-47/chapter-I/subchapter-D/part-96
[58] FCC-20-22, "Expanding Flexible Use of the 3.7 to 4.2 GHz Band," March 3, 2020. Online available: https://www.fcc.gov/document/fcc-expands-flexible-use-c-band-5g-0
[59] OnGo Alliance, "CBRS Coexistence Technical Specifications," OnGo-TS-2001 V4.1.0, March 8, 2022. Online available: https://ongoalliance.org/wp-content/uploads/2022/03/OnGo-TS-2001_v4.1.0_-Published-March-08-2022.pdf
[60] ISED, "Decision on the Technical and Policy Framework for the 3650-4200 MHz Band and Changes to the Frequency Allocation of the 3500-3650 MHz Band," May 2021. Online available: https://ised-isde.canada.ca/site/spectrum-management-telecommunications/en/spectrum-allocation/3650-4200-mhz/decision-technical-and-policy-framework-3650-4200-mhz-band-and-changes-frequency-allocation-3500
[61] MSIT, "Ministry of Science and ICT Announcement No. 2018-235," May 4, 2018. Online available: https://www.msit.go.kr/bbs/view.do?sCode=user&mId=123&mPid=122&bbsSeqNo=96&nttSeqNo=1381869
[62] MSIT, "Enforcement Decree Of The Radio Waves Act," June 7, 2023. Online available: https://www.law.go.kr/lsSc.do?section=&menuId=1&subMenuId=15&tabMenuId=81&eventGubun=060101&query=%EC%A0%84%ED%8C%8C%EB%B2%95+%EC%8B%9C%ED%96%89%EB%A0%B9#undefined
[63] Radio Spectrum Management, “Technical Arrangement of the 3.5 GHz Band,” June 2019. Online available: https://www.rsm.govt.nz/assets/Uploads/documents/consultations/2019-technical-arrangements-of-the-3-5-ghz-band/2babbb72ec/technical-arrangements-of-the-3-5-ghz-band-discussion-document.pdf
[64] 3GPP TR 36.942: "Radio Frequency (RF) system scenarios".
[65] 3GPP TS 38.213: "NR;Physical layer procedures for control".
[66] 3GPP TR 38.803: "Study on new radio access technology: Radio Frequency (RF) and co-existence aspects".
[67] R4-2216404, SBFD gNB Radio and antenna considerations, Ericsson
[68] R4-2301885, BS RF feasibility considerations, Ericsson
[69] R4-2321079, Simulation results for SBFD coexistence, CMCC
|
38.859
|
Study on expanded and improved NR positioning
|
TR
|
18.1.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.859/38859-i10.zip
|
The present document captures the findings of the study item "Study on Expanded and Improved NR Positioning" [7]. 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 normative work on expanded enhancements to NR positioning in TSG RAN WGs.
|
38.864
|
Study on network energy savings for NR
|
TR
|
18.1.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.864/38864-i10.zip
|
The present document captures the findings from the study item of "Study on network energy savings for NR" [2].
The study includes how to model network energy consumption especially for a base station, and evaluations of network energy saving gains as well as impact to network and user performance, by reusing existing KPI whenever applicable or new KPIs as needed. The study is also to identify techniques on gNB and UE side that can improve the network energy savings in various domains, potentially with UE feedback/assistance information and information exchange over network interfaces.
The study prioritizes idle/empty and low/medium load scenarios, allow different loads among carriers and neighbor cells, allows legacy UEs to be able to continue accessing a network implementing Rel-18 network energy savings techniques, with the possible exception of techniques developed specifically for greenfield deployments. The study does not include aspects related to IAB.
|
38.865
|
Study on further NR RedCap UE complexity reduction
|
TR
|
18.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.865/38865-i00.zip
|
This document captures the findings from the study item "Study on further NR RedCap UE complexity reduction" [2].
The study concerns potential solutions for reducing UE complexity further compared to the RedCap UE type introduced in Rel-17 [3], providing NR support for low-tier devices between existing LPWA UEs and Rel-17 RedCap UEs to further expand the market for RedCap use cases with relatively low cost, low energy consumption, and low data rate requirements, targeting 10 Mbps peak rate.
The study focuses on UE bandwidth reduction to 5 MHz and/or UE peak rate reduction to 10 Mbps, possibly in combination with relaxed UE processing timeline. The scope of the study includes support for FR1 bands for FDD and TDD and coexistence with Rel-15/16/17 UEs. The scope of the study does not include LPWA use cases.
|
38.867
|
Study on NR Network-controlled Repeaters
|
TR
|
18.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.867/38867-i00.zip
|
The present document captures the findings from the study item "Study on NR Network-controlled Repeaters" [2].
The SI includes the study and identification of side control information (i.e., beamforming information, Timing information, information on UL-DL TDD configuration, ON-OFF information and power control information) for network-controlled repeaters and corresponding L1/L2 signaling (including its configuration) to carry the side control information. The scope of the study also includes the study on the aspects (i.e., identification and authorization) of network-controlled repeater management
The study on NR network-controlled repeaters is to focus on the following scenarios and assumptions:
- Network-controlled repeaters are inband RF repeaters used for extension of network coverage on FR1 and FR2 bands, while during the study FR2 deployments may be prioritized for both outdoor and O2I scenarios.
- For only single hop stationary network-controlled repeaters
- Network-controlled repeaters are transparent to UEs
- Network-controlled repeater can maintain the gNB-repeater link and repeater-UE link simultaneously
NOTE1: Cost efficiency is a key consideration point for network-controlled repeaters.
|
38.869
|
Study on low-power Wake-up Signal and Receiver for NR
|
TR
|
18.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.869/38869-i00.zip
|
The present document is intended to capture the output of study item for " Study on low-power wake up signal and receiver for NR" [2].
The study includes investigations to
- the impact of low-power wake-up signal and receiver , including power saving benefit, coverage, system overhead impact, network energy impact and other related aspects.
- the receiver architecture for low-power wake-up receiver and provide analysis for power consumption, noise figure and etc.
- L1 designs and procedures changes needed to support the wake-up signal and evaluations for the link performances.
- higher layer protocol changes needed to support the wake-up signals
- related RAN4 impacts
|
38.871
|
Study on NR frequency range 2 (FR2) Over-the-Air (OTA) testing enhancements
|
TR
|
18.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.871/38871-i20.zip
|
The objectives for FR2-1 OTA testing for UEs with multi-panel reception and 4DL layer are as follows.
- Define a test methodology for RF/RRM/Demodulation requirements testing for devices that can receive simultaneously from multiple Angle of Arrival (AoA)
- The multiple AoA test setup should enable testing of up to 2 DL Layers with dual polarization for each angle
- For RRM, the target should be to allow testing of 4 AoAs with 2 simultaneously active AoAs
- Define a test methodology for up to 4 DL MIMO layer demodulation testing
- Smartphone form factor should be the first priority, other UE types should also be discussed as 2nd priority
- Develop the related preliminary uncertainty assessments for the test methodologies
- The tests shall take the test system reuse, test system complexity and test time into account to keep the whole test costs within a reasonable level.
|
38.872
|
Study on enhancement for 700/800/900MHz band combinations
|
TR
|
18.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.872/38872-i40.zip
|
The present document is the technical report for the study on enhancement for 700/800/900MHz band combinations [2] and sub-1GHz NR band combinations [5] under R18 time frame. The purpose is to gather the relevant background information and studies in order to address the study on enhancement for 600/700/800/900MHz band combinations in Table 1-1.
Table 1-1: Band combinations in the SI
Configuration
Uplink configuration
CA_n8-n20-n28
CA_n8-n20, CA_n8-n28, CA_n20-n28
CA_n5-n8
CA_n5-n8
CA_n5-n28
CA_n5-n28
CA_n5A-n105A
CA_n5A-n105A
CA_n28A-n105A
single UL in either n28 or n105
CA_n26A-n28A
CA_n26A-n28A
CA_n5A-n28A-n105A
CA_n5A-n28A
CA_n5A-n28A-n105A
CA_n5A-n105A
CA_n5A-n28A-n105A
single UL in either n28 or n105
|
38.876
|
Air-to-ground network for NR
|
TR
|
18.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.876/38876-i20.zip
|
The present document covers the RF, RRM and co-existence aspects of the work item “Air-to-ground network for NR” [2]
The objectives for the study are the following:
- Study and evaluate adjacent channel co-existence for ATG scenarios.
- Study and specify RF core requirements for ATG network and the ATG UE such that ATG deployment are well supported.
- Study and specify RRM requirement supporting ATG network deployment and ATG UE mobility
|
38.877
|
Study on NR mmWave MB-BS
|
TR
|
18.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.877/38877-i10.zip
|
The present document is the Technical Report for the Study Item on BS RF requirement evolution dealing with FR2 multi-band BS deployments.
|
38.878
|
NR demodulation performance evolution
|
TR
|
18.4.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.878/38878-i40.zip
|
The present technical report documents the Phase I study outcome on the advanced receiver to cancel inter-user interference for MU-MIMO, with the detailed objectives as follows:
- Evaluate and specify advanced receiver to cancel inter-user interference for MU-MIMO
- Phase I: Study the performance gain, reference receiver assumption, interference modeling, testability, required signalling overhead, as well as impact on other WGs
- Further discuss reference receiver assumption with below candidates
- E-MMSE-IRC
- R-ML
- Target scenario: Focus on slot based transmission
|
38.879
|
Study on enhancement for Resiliency of gNB-CU-CP
|
TR
|
18.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.879/38879-i00.zip
|
The present document provides descriptions of failure scenarios associated with the gNB-CU-CP based on current architecture for the NG-RAN.
|
38.880
|
UE requirements for 3Tx inter-band UL CA and EN-DC
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.880/38880-i00.zip
|
The present document is a technical report for UE requirements for 3Tx inter-band UL CA and EN-DC under Rel-18 time-frame. The purpose is to gather the relevant background information and studies of these 3Tx band combinations.
This TR contains the RF requirements of band combination specific part. The actual requirements are added to the corresponding technical specifications.
|
38.881
|
Lower MSD for inter-band CA/EN-DC/DC combinations
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.881/38881-i00.zip
|
The present document is a technical report for study of lower MSD for inter-band CA/EN-DC/DC combinations.
|
38.882
|
Study on requirements and use cases for network verified UE location for Non-Terrestrial-Networks (NTN) in NR
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.882/38882-i00.zip
|
The present document analyses the regulatory requirements (e.g. accuracy, privacy, reliability, latency) in terms of UE location service for a set of use cases/services (i.e. emergency call, lawful intercept, public warning, charging/billing). It identifies the possible need for network-verified UE location specification support in Rel-18.
|
38.884
|
Study on enhanced test methods for Frequency Range 2 (FR2) NR User Equipment (UE)
|
TR
|
18.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.884/38884-i20.zip
|
The objectives of this study are to enhance the FR2 RF testing methodology and to quantify the impact of the enhancements on the UE performance, as related to the polarization basis mismatch between the test equipment and UE and to add support for testing under extreme temperature conditions.
The development of testing methodology enhancements proceeds within the following scope:
- In general
- Target the testing and calibration aspects of the permitted methods for FR2 UE RF testing and the preliminary assessment of measurement uncertainty (Clause 5.2 and Annex B of TR38.810)
- The test methodologies and procedures shall be applicable for different device types and power classes with DUT size defined in the TR 38.810. Prioritize the study to PC3 for aspects related to DUT size, and limit the study to free space conditions
- The study item outcomes shall capture the efficacy of the enhancements
- Objectives related to regulatory test cases shall be prioritized
The detailed objectives are:
1. Define test methodology for high DL power and low UL power test cases
- Considering path loss reduction, measurement antenna gain improvement, DUT positioning improvement, and MU improvement
- Considering NFTF (defined in Clause 5.2 of TR38.810) and direct near field test methodologies as possible alternative methods
- Other approaches are not precluded
- Study preliminary assessment of measurement uncertainty of new alternative methods
2. Define solutions to minimize the impact of polarization basis mismatch between the TE and DUT on the RF testing
- Considering polarization basis mismatch between the test equipment and UE and UE implementations which may be impacted by this mismatch
- Study EIS test metric which can apply to different UE RF implementations considering downlink polarization sweep enhancement
- Limit the study of this objective to the permitted UE RF methods defined in Clause 5.2 of TR38.810
- Possible enhancements may be described as
- Downlink polarization sweeping by the test equipment (i.e. introducing an additional degree of freedom for polarization alignment of the measurement antenna)
- The use of circular polarization to perform measurements
- Coherent combining and demodulation of orthogonally polarized received signals in the test equipment
- Uplink polarization sweeping by the test equipment to search for the optimal polarization angle to receive and demodulate the signal transmitted by the UE
- Considering NFTF (defined in Clause 5.2 of TR38.810) test methodology for EIS measurement
- TPMI side condition method, where TPMI side conditions are applicable to Rel-16 (and higher) UEs
- Test mode to trigger TX diversity
- Other approaches are not precluded
3. Study testability enhancements to support the verification of RF requirements for inter-band (FR2+FR2) CA
- Work on inter-band DL CA is prioritized
- Whether the test setup shall be restricted to emulating the signal from the same direction for the aggregated bands shall be aligned with the UE RF architecture assumption taken in the work item on NR RF Requirement Enhancements for FR2 [UID 830189]
4. Support extreme temperature conditions for all applicable FR2 UE RF test cases
- Considering beam peak search, spherical coverage, and total radiated power procedures
- Limit the study of this objective to the permitted UE RF methods defined in Clause 5.2 of TR38.810
- Study preliminary impacts on system measurement uncertainty under extreme temperature conditions
5. Study testability enhancements to reduce test time
- Including RF test method enhancement with reduced test time, and possible test time saving approach for UE Demodulation test and RRM test
6. Study testability aspects for the introduction of the new band n262
- Considering the extension of frequency applicability of the permitted methods in TR38.810 from 43.5 GHz up to at least 48.2 GHz
- Considering the extension of frequency applicability of the test methodology enhancements in Objectives 1 through 5 above
|
38.891
|
User Equipment (UE) Further enhancements of NR RF requirements for frequency range 2 (FR2) for Rel-18
|
TR
|
18.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.891/38891-i10.zip
|
The present document captures finding of the study on FR2 UL 256QAM and beam correspondence for RRC_INACTIVE and initial access. The purpose of this TR is to study the performance gain and implementation aspects for FR2 UL 256QAM and to ensure good UE RACH msg1 performance and UL coverage in FR2 deployments by specifying the beam correspondence requirements for RRC_INACTIVE and initial access as defined in Work Item “NR RF requirements enhancement for frequency range 2 (FR2), Phase 3” [2].
|
38.892
|
APT 600 MHz NR band
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.892/38892-i00.zip
|
The present document is a technical report for the work item of APT 600 MHz NR band.
|
38.893
|
Study on UE support of regionally-defined subsets of an NR band
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.893/38893-i00.zip
|
The present document captures the study on UE support of regionally-defined subsets of an NR band. In accordance with 3GPP specifications, a UE is required to support the entire frequency range of a band as defined by [2], [3], or [4]. However, it was found that for some bands, there may be regional regulatory restrictions to this frequency range in some countries. The scope of this study is to investigate the root causes that may require 3GPP specification changes to accommodate as well as to consider possible general solutions if needed.
|
38.894
|
Requirements for simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.894/38894-i00.zip
|
The present document is a technical report for requirements on simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC.
Requested FDD-TDD, TDD-TDD CA, SUL, MR-DC and NR-DC band combinations for evaluation of supporting simultaneous Rx/Tx capability/operation are provided in the table below.
Table 1: Band combinations for evaluation of simultaneous Rx/Tx
Band combination
Power Class
CA_n34A-n41A
PC3
CA_n39A-n41A
PC3
CA_n40A-n41A
PC3, PC2
CA_n7A-n40A
PC3
|
38.895
|
High power UE (power class 1.5) for NR FR1 TDD single band
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.895/38895-i00.zip
|
The present document is a technical report for release 18 basket WI High power UE (power class 1.5) for NR FR1 TDD single band. The purpose is to gather the relevant background information and studies in order to complete the band specific requirements for the newly requested bands for power class 1.5 UE under TDD mode.
|
38.896
|
High power for FR1 for FDD single band(s) with power class 2
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.896/38896-i00.zip
|
The present document is a technical report for High power UE (power class 2) for NR FR1 FDD single band under Rel-18 time-frame. The purpose is to gather the relevant background information and studies in order to complete the band specific requirements for the newly requested band combinations for power class 2 UE under FDD mode.
|
38.897
|
High power UE for NR TDD intra-band carrier aggregation in frequency range FR1
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.897/38897-i00.zip
|
The present document is a technical report for release 18 basket WI High power UE (power class 1.5 or 2) for intra-band Carrier Aggregation combinations of a single NR FR1 TDD band.
|
38.898
|
High power UE for FR1 for DC_R18_xBLTE_yBNR_zDLnUL with power class m (x= 1, 2, 3, 4; y=1, 2; m<3)
|
TR
|
18.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.898/38898-i00.zip
|
The present document is a technical report for High power UE (power class m with 1<m<3) for a single FR1 band in UL of Dual Connectivity (DC) combinations of x bands (x=1,2,3, 4 for y=1 or x=1, 2 for y=2) LTE inter-band CA (xDL/1UL) and y bands NR inter-band CA (yDL/1UL) in the Rel-18 time frame. The purpose is to gather the relevant background information and studies to address relevant requirements for the Rel-18 EN-DC HPUE band combinations requested by proponents and captured in the WID.
|
38.918
|
Study on 5G NR User Equipment (UE) full stack testing for Network Slicing
|
TR
|
18.4.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.918/38918-i40.zip
|
The present document contains the findings of the Study on 5G NR UE full stack testing of network slicing and the proposed test procedures.
|
43.064
|
General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.064/43064-i00.zip
|
The present document provides the overall description for lower-layer functions of the General Packet Radio Service (GPRS and EGPRS)) radio interface (Um). ). Within this TS the term GPRS refers to GPRS and EGPRS unless explicitly stated otherwise.
The overall description provides the following information:
- The services offered to higher-layer functions,
- The distribution of required functions into functional groups,
- A definition of the capabilities of each functional group,
- Service primitives for each functional group, including a description of what services and information flows are to be provided, and
- A model of operation for information flows within and between the functions.
The present document is applicable to the following GPRS Um functional layers:
- Radio Link Control functions,
- Medium Access Control functions, and
- Physical Link Control functions.
The present document describes the information transfer and control functions to be used across the radio (Um) interface for communication between the MS and the Network, see Figure 1.
3GPP TS 23.060 [3] describes the overall GPRS logical architecture and the GPRS functional layers above the Radio Link Control and Medium Access Control layer.
3GPP TS 24.007 [5] contains a description in general terms of the structured functions and procedures of this protocol and the relationship of this protocol with other layers and entities.
3GPP TS 44.018 [6] contains the definition of GPRS RLC/MAC procedures when operating on the Common Control Channel (CCCH).
3GPP TS 44.060 [7] contains the definition of RLC/MAC functions when operating on a Packet Data Channel (PDCH).
3GPP TS 44.064 [8] contains functional procedures for the Logical Link Control (LLC) layer above the RLC/MAC.
3GPP TS 45 series defines the Physical Link layer and Physical RF layer.
Figure 1: Scope of GPRS Logical Radio Interface Architecture
|
43.068
|
Voice Group Call Service (VGCS); Stage 2
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.068/43068-i00.zip
|
The present document specifies the stage two description of the Voice Group Call Service (VGCS) which allows speech conversation of a predefined group of service subscribers in half duplex mode on the radio link taking into account multiple subscribers involved in the group call per cell.
|
43.069
|
Voice Broadcast Service (VBS); Stage 2
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.069/43069-i00.zip
|
The present document specifies the stage 2 description of the Voice Broadcast Service (VBS) which allows the distribution of speech (or other signals which can be transmitted via the speech codec), generated by a service subscriber, into a predefined geographical area to all or a group of service subscribers located in this area.
|
43.129
|
Packet-switched handover for GERAN A/Gb mode; Stage 2
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.129/43129-i00.zip
|
The present document defines the stage‑2 service description for packet switched handover in GERAN A/Gb mode and GAN mode. ITU-T Recommendation I.130 [8] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [9] defines stage 2 of the method. The present document refers to packet switched handover in GERAN A/Gb mode/GAN mode, and therefore focuses on the corresponding radio protocol enhancements to the packet switched domain only i.e. when services are provided through the Gb interface.
|
43.318
|
Generic Access Network (GAN); Stage 2
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.318/43318-i00.zip
|
The present document defines the stage 2 service description for a Generic Access Network (GAN) . It describes the GAN system concepts, documents the reference architecture, functional entities, network interfaces, and high-level procedures.
GAN supports two modes of operation:
- GAN A/Gb mode
- GAN Iu mode
GAN A/Gb mode supports an extension of GSM/GPRS mobile services that is achieved by tunnelling Non Access Stratum (NAS) protocols between the MS and the Core Network over an IP network and the A and Gb interfaces to the MSC and SGSN, respectively.
GAN Iu mode supports an extension of UMTS mobile services that is achieved by tunnelling Non Access Stratum (NAS) protocols between the user equipment (MS) and the Core Network over an IP network and the Iu-cs and Iu-ps interfaces to the MSC and SGSN, respectively.
Both GAN modes are complements to traditional GERAN/UTRAN/E-UTRAN radio access network coverage.
|
43.901
|
Feasibility Study on generic access to A/Gb interface
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.901/43901-i00.zip
|
This document studies the feasibility of generic access to A/Gb interface. Specific areas of study are:
- Architecture to enable generic access.
- Access interface protocols required to provide connectivity to A/Gb interface and GSM/GPRS services.
- Security mechanisms to support generic access architecture.
- Determining feasibility for support of services currently supported through GERAN.
The focus of the study shall be on establishing the feasibility for supporting generic access in the home network case, while also identifying issues with extending the solution to the roaming scenarios.
|
43.902
|
Enhanced Generic Access Networks (EGAN) study
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.902/43902-i00.zip
|
The present document contains the results of the feasibility study into the enhancements to Generic Access Networks or GAN. Considerations include overall requirements for enhancements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The objective is to identify an architectural solution that best meets the requirements as specified in first section. The feasibility study shall also investigate mechanisms for selecting the most appropriate network domain to serve the user.
Existing solutions developed by the 3GPP should be reused as much as possible.
|
43.903
|
A-interface over IP study (AINTIP)
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.903/43903-i00.zip
|
The present document contains the result from the study of introduction of support for A-interface over IP. High level areas that are studied are e.g. potential placement of transcoders in the core network, effective bandwidth utilisation at the A-interface, impact on call related messages, payload formats.
The following items shall be covered in the study:
- In the target solution it is wanted to transfer compressed speech as far as possible end-to-end to achieve efficient transport and speech quality. The possibility to free GERAN from handling all kind of transcoders shall be studied, and the architecture might place Codecs in the core network.
- Impacts/changes on current A-interface procedures resulting from placing transcoders in the core network as well as in the BSS shall be studied, e.g. impacts on the assignment and handover procedures.
- In addition to allow compressed speech over the A-interface the study shall provide further solution for effective bandwidth utilisation at the A interface, which means it shall describe multiplexing of RTP flows and how this will be negotiated between the BSS and CN nodes.
- The study shall describe a solution for "true end-to-end Codec negotiation", which considers on a call basis the preference/situation of the radio network.
- It shall be studied how call related messages have to be adapted, e.g. transfer of Codec related information, identification of calls/sessions.
- The study shall describe the wanted payload formats and other relevant user plane parameters like packetization time etc.
|
44.001
|
Mobile Station - Base Station System (MS - BSS) interface; General aspects and principles
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.001/44001-i00.zip
| |
44.003
|
Mobile Station - Base Station System (MS - BSS) Interface Channel Structures and Access Capabilities
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.003/44003-i00.zip
|
The present document defines limited sets of channel types, access capabilities and channel configurations at reference point Um (radio interface).
|
44.004
|
GSM/EDGE Layer 1; General Requirements
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.004/44004-i00.zip
|
The present document defines the service offered by the physical layer (3GPP TS 45‑series of Technical Specifications) of the MS‑BS interface (3GPP TS 45‑ and 44‑series of Technical Specifications). Its main objective is to be a guidance for the interface between the 3GPP Technical Specifications in the 45‑series and the 44‑series. It also specifies the format of signalling channels and the order of bit transmission.
As far as possible, the present document makes use of the layering principles of the Reference Model for Open System Interconnection (OSI) as contained in ITU-T Recommendations X.200 and X.210.
1a References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.011: "Service accessibility".
[3] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM System".
[4] 3GPP TS 43.020: "Security-related network functions".
[5] Void.
[6] Void.
[7] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities".
[8] 3GPP TS 44.005: "Data Link (DL) layer; General aspects".
[9] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification".
[10] Void.
[11] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[12] Void.
[13] Void.
[14] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".
[15] Void.
[16] Void.
[17] Void.
[17a] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".
[18] Void.
[19] Void.
[20] Void.
[21] Void.
[22] Void.
[23] Void.
[24] Void.
[25] Void.
[26] Void.
[26a] Void.
[26b] Void.
[27] 3GPP TS 45.001: "Physical Layer on the Radio Path (General Description)".
[28] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[29] 3GPP TS 45.003: "Channel coding".
[30] Void.
[31] 3GPP TS 45.005: "Radio transmission and reception".
[32] 3GPP TS 45.008: "Radio subsystem link control".
[33] 3GPP TS 45.010: "Radio subsystem synchronization".
[34] Void.
[35] ITU-T Recommendation X.200: "Information technology; Open Systems Interconnection; Basic Reference Model: The basic model".
[36] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic Reference Model: Conventions for the definition of OSI services".
[37] 3GPP TS 48.058: "Base Station Controler - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification".
[38] 3GPP TR 45.902: "Flexible Layer One".
[39] 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2".
|
44.005
|
GSM/EDGE Data Link (DL) Layer; General aspects
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.005/44005-i00.zip
|
The present document describes in general terms the Link Access Procedures on the Dm channel, LAPDm. The application of this protocol to other channel types is for further study. Details are provided in 3GPP TS 44.006.
The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface (MS to network interface) using the Dm channel.
NOTE 1: The term Dm channel is used for convenience to designate the collection of all the various signalling channels required in the GSM system. See also 3GPP TS 44.003.
The definition of LAPDm is based on the principles and terminology of:
‑ ITU-T Recommendations X.200 and X.210: the reference model for Open Systems Interconnection (OSI);
‑ ITU-T Recommendations Q.920 and Q.921: the specification of LAPD for the user‑network interface in ISDN;
‑ ITU-T Recommendation X.25 LAPB: user‑network interface for packet mode terminals; and
‑ ISO/IEC 3309 and ISO 4335: High‑level Data Link Control (HDLC) standards for frame structure and elements of procedures.
LAPDm is a protocol that operates at the data link layer of the OSI architecture. The relationship between the data link layer and other protocol layers is defined below.
NOTE 2: The interface between the mobile station and external terminal equipment/terminal adapters is defined in the Technical Specifications of the GSM 07‑series.
NOTE 3: The physical layer on the radio interface is defined in 3GPP TS 44.004 and layer 3 is defined in 3GPP TS 24.007, 3GPP TS 44.018, 3GPP TS 24.010 and 3GPP TS 24.011. Reference should be made to these Technical Specifications for the complete definitions of the protocols and procedures across the GSM PLMN radio interface.
NOTE 4: The term "data link layer" is used in the main text of the present document. However, mainly in figures and tables, the terms "layer 2" and "L2" are used abbreviations. Furthermore, in accordance with 3GPP TS 24.007 and 3GPP TS 44.018 the term "layer 3" is used to indicate the layer above the data link layer.
LAPDm is independent of the transmission bit rate. It requires physical channels with characteristics as defined in 3GPP TS 44.003.
Clause 2 below describes basic concepts used in the present document and 3GPP TS 44.006.
Clause 3 gives an overview description of LAPDm functions and procedures.
Clause 4 summarizes the services that the data link layer provides to layer 3 and the services that the data link layer requires from the physical layer.
Clause 5 provides an overview of the data link layer structure.
|
44.006
|
Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.006/44006-i00.zip
|
The present document defines a data link layer protocol to be used for signalling, and possibly also for other applications, on the MS‑BS interface.
|
44.012
|
Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.012/44012-i00.zip
| |
44.013
|
Performance requirements on the mobile radio interface
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.013/44013-i00.zip
|
The present document specifies measurable performance requirements for signalling aspects of Mobile Stations (MS)s. To allow implementation flexibility it has been chosen to specify requirements on the whole Mobile Station rather than to specify requirements on each "OSI layer". As a consequence the performance requirements do not fit conveniently in specifications such as 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] (layer 3 only) or 3GPP TS 44.006 [3] (layer 2 only).
The main aim of the present document is to provide the justification for testing of requirements that are not included in other GSM specifications. Where specific requirements are included in other GSM specifications they are not duplicated here.
MSs have to perform a wide variety of functions. As a consequence most performance measurements have to be made under a set of defined conditions: where necessary, these are included in the present document.
Where necessary certain assumptions are made about the interaction times between the mobile equipment and the SIM. If the (test) SIM does not respond within the assumed time then appropriate allowances shall be made.
Additionally, it is intended that the present document should contain sufficient requirements to enable some undefined network timers in 3GPP TS 24.008 [4] and 3GPP TS 44.018 [4a] to be calculated.
|
44.014
|
Individual equipment type requirements and interworking; Special GSM/EDGE conformance testing functions
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.014/44014-i00.zip
|
The present document specifies for Mobile Stations (MS), for the digital cellular communications system and Personal Communication Systems (PCS) operating in the 900 MHz and 1800 MHz band (GSM900 and DCS1800), standardized by 3rd Generation Partnership Project (3GPP), those ME functions which are required for conformance testing purposes only. However, except for the Electrical Man Machine Interface (EMMI) and the Multi-slot TCH Loops, they are required for every mobile station.
For conformance tests, functions are activated via the radio interface, test SIM or dedicated pins. These functions must be capable of being activated when a test SIM is present but must not function with any other (e.g. network) SIM present except where otherwise stated within the present document. In this state, the MS must be able to perform all functions specified in the present document; in addition however, the special conformance testing functions must be operational.
The special conformance testing functions of the ME are enabled by use of a dedicated Subscriber Identity Module (test SIM, see 3GPP TS 51.010-1 Annex 4). SIM, in general, is described in 3GPP TS 51.011. The ME recognizes the test SIM by the Administrative Data Field.
The present document applies to the public land mobile radio service in the GSM900 and DCS1800 systems, using constant envelope modulation and operating on radio frequencies in the 900 and 1800 MHz bands respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle.
The present document is part of the 3GPP TS series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related TS, nor is it created to provide full understanding of (or parts of) the GSM900 and DCS1800 systems.
The present document applies to the unit which includes the hardware to establish a connection across the radio interface.
|
44.018
|
Mobile radio interface layer 3 specification; GSM/EDGE Radio Resource Control (RRC) protocol
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.018/44018-i00.zip
|
The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002) for Radio Resource (RR) management.
Notation "Reserved sub-clause number" is used to indicate which sub-clauses of the specification were moved from this part of the standard to the other part when this standard was split between RAN and CN parts.
When the notations for "further study" or "FS" or "FFS" are present in this specification they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPP TS 44.003.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007.
|
44.021
|
Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.021/44021-i00.zip
|
The present document defines the rate adaptation functions to be used in PLMN Mobile Stations (MS)s for adapting terminal interface data rates to the Mobile Station - Base Station System (MS-BSS) interface data rates in accordance with 3GPP TS 43.010 [3].
The provision of these functions will depend on the services a particular station is designed to support.
NOTE 1: The present document should be considered together with 3GPP TS 48.020 [9] (Rate Adaptation on the BSS-MSC Interface) to give a complete description of PLMN rate adaptation.
NOTE 2: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
|
44.031
|
Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP)
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.031/44031-i00.zip
|
The present document contains the definition of the Radio Resource LCS Protocol (RRLP) to be used between the Mobile Station (MS) and the Serving Mobile Location Centre (SMLC).
Clause 2 defines the functionality of the protocol. Clause 3 describes the message structure, and Clause 4 the structure of components. Clause 5 contains the ASN.1 description of the components.
|
44.035
|
GSM/EDGE Location Services (LCS); Broadcast network assistance for Enhanced Observed Time Difference (E-OTD) and Global Positioning System (GPS) positioning methods
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.035/44035-i00.zip
|
The present document contains the content of messages necessary for support of MS Based location service operation on the mobile radio interface layer 3.
|
44.056
|
GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.056/44056-i00.zip
|
The present document specifies the procedures used at the CTS radio interface (Reference Point Um*, see GSM 03.56) for Call Control (CC), Mobility Management (MM), Radio Resource (RR).
When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The CTS control channels are described in GSM 03.52.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07.
|
44.057
|
GSM Cordless Telephony System (CTS), Phase 1; CTS supervising system layer 3 specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.057/44057-i00.zip
|
The present document specifies the procedures used at the CTS system interface with the supervision part i.e. the interface between the CTS-FP and the CTS-SN.
Only CTS regular supervising procedures are described; FMC management is not intended to be standardised.
The present document does not specify the transmission layer but only the layer 3.
When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of the present document.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07.
|
44.060
|
General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.060/44060-i00.zip
| |
44.064
|
Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.064/44064-i00.zip
|
The present document defines the Logical Link Control (LLC) layer protocol to be used for packet data transfer between the Mobile Station (MS) and Serving GPRS Support Node (SGSN).
It defines the frame structure, elements of procedure, format of fields, and procedures for the proper operation of the logical link control layer. It is based on ideas contained in IS-130 [21], ISO 3309 [16], ISO 4335 [17], and ISO 7809 [18, 19, 20] (HDLC of ISO), as well ITU-T Q.920 [13] and Q.921 [14] (LAPD). The concepts, the overview description of LLC layer functions and procedures, and the relationship with other Technical Specifications are described in general terms in 3GPP TS 23.060 [5].
LLC spans from the Mobile Station (MS) to the Serving GPRS Support Node (SGSN). LLC is intended for use with both acknowledged and unacknowledged data transfer.
The frame formats defined for LLC are based on those defined for LAPD and RLP. However, there are important differences between LLC and other protocols, in particular with regard to frame delimitation methods and transparency mechanisms. These differences are necessary for independence from the radio path.
The LLC procedures are modelled upon the concepts of HDLC as outlined in ISO 4335. Data sequence integrity between the data source and data sink is effected by means of a cyclic numbering scheme. An independent numbering scheme is used for each logical data link, as identified by the a data link connection identifier. LLC supports two modes of operation:
- Unacknowledged peer-to-peer operation:
A logical link entity may initiate transmissions to a peer entity without prior establishment of a logical connection with the peer entity. LLC does not guarantee in-order delivery. LLC can detect errors in a received frame, and, depending on whether the frame is sent in protected mode or not, either discard or deliver the erroneous frame. No error recovery procedures are defined at the LLC layer. Higher-layer protocols can be used to provide reliability, if needed. This mode of operation is known as Asynchronous Disconnected Mode (ADM).
- Acknowledged peer-to-peer operation:
A balanced data link involves two participating entities, and each entity assumes responsibility for the organisation of its data flow and for error recovery procedures associated with the transmissions that it originates. Each entity operates as both a data source and data sink in a balanced link, allowing information to flow in both directions. This mode of operation is known as Asynchronous Balanced Mode (ABM), and provides a reliable service with in-order delivery.
In unacknowledged operation, LLC can provide integrity protection.
The present document is organised as follows:
- An overview of the LLC layer functions is given in clause 4.
- The frame structure for peer-to-peer communication is given in clause 5.
- The elements of procedure and formats of fields are given in clause 6.
- The elements of layer-to-layer communication are contained in clause 7.
- The details of the peer-to-peer ABM procedures are given in clause 8.
- The details of LLC frame ciphering are given in annex A.
- The details of the TOM protocol layer are contained in annex B.
- An overview of the LLC layer states is provided in annex C.
|
44.065
|
Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.065/44065-i00.zip
|
The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS).
The user of the services provided by SNDCP is a packet data protocol (PDP) at the mobile Station (MS) or the Relay at the Serving GPRS Support Node (SGSN). Additionally, a control entity, e.g. AT command interpreter, may be an SNDCP user. SNDCP uses the services provided by the Logical Link Control (LLC) layer 4 and the Session Management (SM) sub-layer 2.
The main functions of SNDCP are:
- Multiplexing of several PDPs.
- Compression / decompression of user data.
- Compression / decompression of protocol control information.
- Segmentation of a network protocol data unit (N‑PDU) into Logical Link Control Protocol Data Units (LL‑PDUs) and re-assembly of LL‑PDUs into an N‑PDU.
3GPP TS 44.065 is applicable to GPRS MS and SGSN.
|
44.068
|
Group Call Control (GCC) protocol
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.068/44068-i00.zip
|
The present document specifies the Group Call Control (GCC) protocol used by the Voice Group Call Service (VGCS) on the radio interface.
|
44.069
|
Broadcast Call Control (BCC) protocol
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.069/44069-i00.zip
|
The present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface.
|
44.071
|
GSM/EDGE Location Services (LCS); Mobile radio interface layer 3 LCS specification
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.071/44071-i00.zip
|
The present document contains the coding of information necessary for support of location service operation on the mobile radio interface layer 3 between the LMU and SMLC.
Clause 4 defines generic procedures for the control of location services. In clause 5 location service support procedures are defined. Clause 6 gives the functional definitions and contents of messages for location service operations. Clause 7 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations. Clause 6 gives the detailed message format and information elements coding between the LMU and SMLC.
Clause 8 gives the specification of the LMU LCS Protocol (LLP) operations. In clause 9 LMU - SMLC messages, data types and identifiers are given.
This version does not support segmentation of messages.
|
44.318
|
Generic Access Network (GAN); Mobile GAN interface layer 3 specification
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.318/44318-i00.zip
|
The present document describes the procedures used over the Generic Access Network (GAN) interface (i.e., the Up interface). The procedures are defined in terms of messages exchanged over the Up interface.
A building block method is used to describe the procedures.
The basic building blocks are "elementary procedures" provided by the Generic Access (GA) protocol control entities.
Complete layer 3 transactions consist of specific sequences of elementary procedures. The term "structured procedure" is used for these sequences.
|
44.901
|
GSM/EDGE External Network Assisted Cell Change (NACC)
|
TR
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.901/44901-i00.zip
|
This Technical Report provides background information, motivations, concepts and requirements regarding an extended Network Assisted Cell Change (NACC) feature for external cell change support. Cell change between GERAN and UTRAN cells is outside the scope of this report, although consideration has been taken in order to allow an easier extensibility to that case. The extension is based on the Release 4 version of the NACC feature where the mobile station is only supported by the NACC when performing internal cell re-selection, i.e. within a BSC. The extension of the feature is for GERAN just affecting BSS and for the core network the SGSN and signalling links between these network nodes. To support cell changes between GERAN and UTRAN, also the Um and the Uu interfaces are affected.
The evolved Release 4 NACC proposal as described in this TR provides the basis for the detailed Stage 2 and stage 3 specification work. The feature will be developed in a phased approach and a longer-term vision is presented in the report.
The focus of the TR is to:
- Define the requirements on different nodes
- Specify the requirements for the interfaces
- Propose a plan for the work item project
- Evaluation of what does and does not need to be standardised
|
45.001
|
GSM/EDGE Physical layer on the radio path; General description
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.001/45001-i00.zip
|
The present document is an introduction to the 45 series of the digital cellular telecommunications systems GSM technical specifications. It is not of a mandatory nature, but consists of a general description of the organization of the physical layer with reference to the technical specifications where each part is specified in detail. It introduces furthermore, the reference configuration that will be used throughout this series of technical specifications.
|
45.002
|
GSM/EDGE Multiplexing and multiple access on the radio path
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.002/45002-i00.zip
|
The present document defines the physical channels of the radio sub‑system required to support the logical channels. For the Flexible Layer One, it defines the physical channels of the radio sub‑system required to support the transport channels. It includes a description of the logical channels, transport channels and the definition of frequency hopping, TDMA frames, timeslots and bursts.
|
45.003
|
GSM/EDGE Channel coding
|
TS
|
18.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.003/45003-i00.zip
|
A reference configuration of the transmission chain is shown in 3GPP TS 45.001. According to this reference configuration, the present document specifies the data blocks given to the encryption unit.
It includes the specification of encoding, reordering, interleaving and the stealing flag. It does not specify the channel decoding method.
The definition is given for each kind of logical channel, starting from the data provided to the channel encoder by the speech coder, the data terminal equipment, or the controller of the Mobile Station (MS) or Base Transceiver Station (BTS). The definitions of the logical channel types used in this technical specification are given in 3GPP TS 45.002, a summary is in annex A.
Additionally, the present document describes the characteristics of the coding/multiplexing unit for the Flexible Layer One (FLO) starting from the transport blocks provided by higher layers. An overview of FLO is given in 3GPP TR 45.902.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.