id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
37.466 | Iuant interface: Application part | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.466/37466-h00.zip | |
37.470 | W1 interface; General aspects and principles | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.470/37470-h00.zip | |
37.471 | W1 interface; Layer 1 | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.471/37471-h00.zip | |
37.472 | W1 interface; Signalling transport | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.472/37472-h00.zip | |
37.473 | W1 interface; Application Protocol (W1AP) | TS | 17.2.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.473/37473-h20.zip | |
37.480 | E1 general aspects and principles | TS | 17.2.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.480/37480-h20.zip | |
37.481 | E1 layer 1 | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.481/37481-h00.zip | |
37.482 | E1 signalling transport | TS | 17.4.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.482/37482-h40.zip | |
37.483 | E1 Application Protocol (E1AP) | TS | 17.10.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.483/37483-ha0.zip | |
37.571-1 | User Equipment (UE) conformance specification for UE positioning; Part 1: Conformance test specification | TS | 17.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.571-1/37571-1-h70.zip | |
37.571-2 | User Equipment (UE) conformance specification for UE positioning; Part 2: Protocol conformance | TS | 17.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.571-2/37571-2-h40.zip | |
37.571-3 | User Equipment (UE) conformance specification for UE positioning; Part 3: Implementation Conformance Statement (ICS) | TS | 17.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.571-3/37571-3-h60.zip | |
37.571-4 | User Equipment (UE) conformance specification for UE positioning; Part 4: Test suites | TS | 17.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.571-4/37571-4-h60.zip | |
37.571-5 | User Equipment (UE) conformance specification for UE positioning; Part 5: Test scenarios and assistance data | TS | 17.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.571-5/37571-5-h70.zip | |
37.579-1 | Mission Critical (MC) services; Part 1: Common test environment | TS | 17.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-1/37579-1-h20.zip | The present document defines the common test environment required for testing Client and Server implementations for compliance to the Mission Critical Services protocol requirements defined by 3GPP.
It contains definitions of reference conditions and test signals, default messages and other parameters, generic procedures, and, common requirements for test equipment with the goal for facilitating testing in general and test procedures specification in particular. Various parts of its content are referred to from other parts of the Mission Critical Services protocol conformance testing specification e.g. TS 37.579-2 [2], 3GPP TS 37.579-6 [84], 3GPP TS 37.579-7 [85].
The present document does not define the common test environment required for testing the implementation of the underlying RRC/NAS protocols, i.e. the bearers used for transport of the Mission Critical Services signalling and media. This is defined in TS 36.508 [6] and referred to from the present document whenever needed.
In regard to default messages or other information elements contents, the present document refers to content defined in requirements specifications specified by 3GPP or other organisations. |
37.579-2 | Mission Critical (MC) services; Part 2: Mission Critical Push To Talk (MCPTT) User Equipment (UE) Protocol conformance specification | TS | 17.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-2/37579-2-h20.zip | The present document specifies the protocol conformance testing for testing a MCPTT Client for compliance to the Mission Critical Push To Talk (MCPTT) protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCPTT Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 37.579-1 [2];
- Implementation Conformance Statement (ICS) TS 37.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 37.579-5 [5];
- the applicability of each test case TS 37.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the 3GPP bearers which carry the MCPTT data sent or received by the MCPTT Client and which are required to be supported by the UE in which the MCPTT Client is installed. This is defined in TS 36.523-1 [6] for EPS (LTE) or TS 38.523-1 [39] for NR/5GC. |
37.579-4 | Mission Critical (MC) services; Part 4: Test Applicability and Implementation Conformance Statement (ICS) proforma specification | TS | 17.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-4/37579-4-h20.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for testing Client implementations for compliance to the Mission Critical Services protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [7] and ISO/IEC 9646-7 [8].
The present document specifies the recommended applicability statement for the test cases included in 3GPP TS 37.579-2 [3], as well as, TS 37.579-6 [3] and 3GPP TS 37.579-7 [12]. These applicability statements are based on the features implemented in the Client.
The present document is valid for Mission Critical Services Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The present document is valid for Mission Critical Video (MCVideo) and Mission Critical Data (MCData) Clients implemented according to 3GPP releases starting from Release 14 up to the Release indicated on the cover page of the present document.
The present document does not specify applicability or ICS for protocol conformance testing for the 3GPP bearers which carry the Mission Critical Services data sent or received by the Client. These are defined in TS 36.523-2 [6] for EPS (LTE) or TS 38.523-2 [20] for NR/5GC. |
37.579-5 | Mission Critical (MC) services; Part 5: Abstract test suite (ATS) | TS | 17.1.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-5/37579-5-h10.zip | |
37.579-6 | Mission Critical (MC) services; Part 6: Mission Critical Video (MCVideo) User Equipment (UE) Protocol conformance specification | TS | 17.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-6/37579-6-h20.zip | The present document specifies the protocol conformance testing for testing a MCVideo Client for compliance to the Mission Critical Video (MCVideo) protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCVideo Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 37.579-1 [2];
- Implementation Conformance Statement (ICS) TS 37.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 37.579-5 [5];
- the applicability of each test case TS 37.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the 3GPP bearers which carry the MCVideo data sent or received by the MCVideo Client and which are required to be supported by the UE in which the MCVideo Client is installed. This is defined in TS 36.523-1 [6] for EPS (LTE) or TS 38.523-1 [37] for NR/5GC. |
37.579-7 | Mission Critical (MC) services; Part 7: Mission Critical Data (MCData) User Equipment (UE) Protocol conformance specification | TS | 17.2.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.579-7/37579-7-h20.zip | The present document specifies the protocol conformance testing for testing a MCData Client for compliance to the Mission Critical Data (MCData) protocol requirements defined by 3GPP.
In particular the present document contains:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- a brief description of the test procedure, the specific test requirements and short message exchange table.
The present document is valid for MCData Clients implemented according to 3GPP releases starting from Release 13 up to the Release indicated on the cover page of the present document.
The following information relevant to testing specified in the present document could be found in accompanying specifications:
- default setting of the test parameters TS 37.579-1 [2];
- Implementation Conformance Statement (ICS) TS 37.579-4 [4] and Implementation eXtra Information for Testing (IXIT) TS 37.579-5 [5];
- the applicability of each test case TS 37.579-4 [4].
The test cases are expected to be executed through the 3GPP radio interface. The present document does not specify the protocol conformance testing for the 3GPP bearers which carry the MCData data sent or received by the MCData Client and which are required to be supported by the UE in which the MCData Client is installed. This is defined in TS 36.523-1 [6] for EPS (LTE) or TS 38.523-1 [45] for NR/5GC.
According to 3GPP drafting rules, the references clause shall list only documents that are explicitly mentioned in the deliverable. This reference is not used within the document and thus shall be removed from references clause. |
37.717-00-00 | Rel-17 band combinations for SA NR supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-00-00/37717-00-00-h00.zip | The present document is a technical report for SA NR Supplementary uplink (SUL), NSA NR SUL and NSA NR SUL with UL sharing from the UE perspective (ULSUP) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address NR SUL for the Rel-17 bands/band combinations in Table 1-1 to Table 1-4.
Table 1-1: Release 17 SUL bands
Band number
UL
DL
Duplex mode
n97
2300 MHz – 2400 MHz
N/A
SUL
n98
1880 MHz – 1920 MHz
N/A
SUL
n99
1626.5 MHz – 1660.5 MHz
N/A
SUL
Table 1-2: Release 17 SA SUL band combinations
SA SUL band combination
REL independent from
SUL_n41-n83
Rel-15
SUL_n79-n83
Rel-15
CA_n28_SUL_n41-n83
Rel-15
CA_n28_SUL_n79-n83
Rel-15
CA_n1_SUL_n78-n80
Rel-15
CA_n1_SUL_n78-n84
Rel-15
CA_n41_SUL_n79-n80
Rel-15
CA_n79_SUL_n41-n80
Rel-15
CA_n3_SUL_n78-n80
Rel-15
CA_n41_SUL_n79-n83
Rel-15
CA_n79_SUL_n41-n83
Rel-15
SUL_n79-n97
Rel-15
SUL_n41-n98
Rel-15
SUL_n79-n98
Rel-15
SUL_n41-n99
Rel-15
SUL_n48-n99
Rel-15
SUL_n77-n99
Rel-15
SUL_n41-n97
Rel-15
SUL_n24-n99
Rel-15
CA_n3_SUL_n41-n80
Rel-15
CA_n3_SUL_n79-n80
Rel-15
CA_n28-n79_SUL_n41-n83
Rel-15
CA_n28-n41_SUL_n79-n83
Rel-15
CA_n79_SUL_n41-n97
Rel-15
CA_n41_SUL_n79-n97
Rel-15
Table 1-3: Release 17 NSA SUL band combinations
NSA SUL band combination
REL independent from
Table 1-4: Release 17 NSA SUL with ULSUP band combinations
NSA SUL with ULSUP band combination
REL independent from
DC_28_SUL_n41-n83
Rel-15
This TR contains a general part and specific band combination part. The actual requirements are added to the corresponding technical specifications. |
37.717-11-11 | Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-11/37717-11-11-h00.zip | The present document is a technical report for Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame.
The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations in Table 1-1, 1-2, 1-3 and 1-4, including EN-DC and NE-DC combinations. The actual requirements are added to the corresponding technical specifications.
Table 1-1: Release 17 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) within FR1
DC combination
Uplink EN-DC configuration
DC_8A_n7A
DC_8A_n7A
DC_66A_n77A
DC_66A-66A_n77A
DC_66A-66A-66A_n77A
DC_66A_n77A
DC_13A_n77A
DC_13A_n77A
DC_5A_n77A
DC_5A_n77A
DC_2A_n77A
DC_2A-2A_n77A
DC_2A_n77A
DC_19A_n1A
DC_19A_n1A
DC_21A_n1A
DC_21A_n1A
DC_42A_n1A
DC_42C_n1A
DC_42A_n1A
DC_48A_n25A
DC_48C_n25A
DC_48D_n25A
DC_48A_n25A
DC_28A_n2A
DC_28A_n2A
DC_2A_n28A
DC_2A_n28A
DC_4A_n2A
DC_4A_n2A
DC_4A_n5A
DC_4A_n5A
DC_4A_n7A
DC_4A_n7A
DC_28A_n66A
DC_28A_n66A
DC_4A_n28A
DC_4A_n28A
DC_66A_n28A
DC_66A_n28A
DC_28A_n1A
DC_28A_n1A
DC_42A_n3A
DC_42A_n3A
DC_42C_n3A
DC_42A_n3A
DC_42C_n3A
DC_8A_n2A
DC_8A_n2A
DC_18A_n28A
DC_18A_n28A
DC_18A_n41A
DC_18A_n41A
DC_7A_n2A
DC_7C_n2A
DC_7A_n2A
DC_71A_n71A
DC_71A_n71A1
DC_25A_n77A
DC_25A_n77A
DC_25A-25A_n77A
DC_25A_n77A
DC_25A_n78A
DC_25A_n78A
DC_25A-25A_n78A
DC_25A_n78A
DC_21A_n28A2
DC_21A_n28A
DC_12A_n71A
DC_12A_n71A3,4
DC_71A_n41A
DC_71A_n41A
DC_71A_n2A
DC_71A_n2A
DC_2A_n30A
DC_2A_n30A
DC_5A_n30A
DC_5A_n30A
DC_12A_n30A
DC_12A_n30A
DC_66A_n30A
DC_66A_n30A
DC_11A_n41A
DC_11A_n41A
DC_66A_n66A
DC_66A_n66A1
DC_38A_n28A
DC_38A_n28A
DC_12A_n77A
DC_12A_n77A
DC_14A_n77A
DC_14A_n77A
DC_30A_n77A
DC_30A_n77A
DC_14A_n30A
DC_14A_n30A
DC_7A_n25A
DC_7A_n25A
DC_7A-7A_n25A
DC_7A_n25A
DC_7C_n25A
DC_7A_n25A
DC_13A_n25A
DC_13A_n25A
DC_3A-3A_n8A
DC_3A_n8A
DC_7A-7A_n8A
DC_7A_n8A
DC_48A_n77A5. 6. 7, 8
N/A
DC_38A_n3A
DC_38A_n3A
DC_(n)66AA
DC_(n)66AA1
DC_38A_n1A
DC_38A_n1A
DC_38A_n8A
DC_38A_n8A
DC_(n)3AA
DC_(n)3AA1
DC_14A_n5A
DC_14A_n5A
DC_11A_n1A
DC_11A_n1A
DC_41A_n1A
DC_41C_n1A
DC_41A_n1A
DC_41C_n1A
DC_7A_n79A
DC_7A_n79C
DC_7A_n79A
DC_38A_n79A
DC_38A_n79C
DC_38A_n79A
DC_5A_n1A
DC_5A_n1A
DC_5A_n3A
DC_5A_n3A
DC_2A_n25A9. 10. 11
N/A
DC_(n)7AA
DC_(n)7AA1
DC_71A_n77A
DC_71A_n77A
DC_48A_n2A
DC_48A_n2A
NOTE 1: Only single switched UL is supported.
NOTE 2: The frequency range in band n28 is restricted for this band combination to 728 - 738 MHz for the UL and 783 - 793 MHz for the DL. This restriction applies also for these band combinations when applicable EN-DC configuration is part of a higher order EN-DC configuration.
NOTE 3: Only single switched UL is supported.
NOTE 4: The implementation with 4 antennas is targeted for FWA form factor for this band combination.
NOTE 5: The minimum requirements apply only when there is non-simultaneous Tx/Rx operation between E-UTRA and NR carriers. This restriction applies also for these carriers when applicable EN-DC configuration is part of a higher order EN-DC configuration.
NOTE 6: The minimum requirements for intra-band non-contiguous EN-DC apply. When UE capability interBandContiguousMRDC is indicated, the minimum requirements for intra-band-contiguous EN-DC also should be met in addtion to intra-band non-contiguous EN-DC. The intra-band requirements also apply for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
NOTE 7: The combination is not used alone as fall back mode of other band combinations in which UL in Band 42 or Band 48 is not used.
NOTE 8: The minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers is within 6 dB. The power spectral density imbalance condition also applies for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
NOTE 9: The combination is not used alone as fallback mode of other band combinations in which UL in Band 2 is not used.
NOTE 10: The minimum requirements for inter-band EN-DC apply when the maximum power spectral density imbalance between downlink carriers is within 6 dB. The power spectral density imbalance condition also applies for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
NOTE 11: The minimum requirements apply for synchronized DL carriers with a maximum receive time difference ≤ 3 usec. The requirements also apply for these carriers when applicable EN-DC configuration is a subset of a higher order EN-DC configuration.
Table 1-2: Release 17 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) including FR2
DC combination
Uplink EN-DC configuration
DC_66A_n261(A-L)
DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I
DC_66A_66A_n261(A-L)
DC_66A_n261A
DC_66A_n261G
DC_66A_n261H
DC_66A_n261I
DC_48A_n261(A-L)
DC_48A_n261A
DC_48A_n261G
DC_48A_n261H
DC_48A_n261I
DC_13A_n261(A-L)
DC_13A_n261A
DC_13A_n261G
DC_13A_n261H
DC_13A_n261I
DC_5A_n261(A-J)
DC_5A_n261A
DC_5A_n261G
DC_5A_n261H
DC_5A_n261I
DC_5A_n261(A-L)
DC_5A_n261A
DC_5A_n261G
DC_5A_n261H
DC_5A_n261I
DC_2A_n261(A-L)
DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A-2A_n261A
DC_2A_n261A
DC_2A-2A_n261I
DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_2A-2A_n261M
DC_2A_n261A
DC_2A_n261G
DC_2A_n261H
DC_2A_n261I
DC_20A_n257A
DC_20A_n257B
DC_20A_n257C
DC_20A_n257D
DC_20A_n257E
DC_20A_n257F
DC_20A_n257G
DC_20A_n257H
DC_20A_n257I
DC_20A_n257J
DC_20A_n257K
DC_20A_n257L
DC_20A_n257M
DC_20A_n257A
DC_3A-3A_n257G
DC_3A-3A_n257H
DC_3A-3A_n257I
DC_3A-3A_n257J
DC_3A-3A_n257K
DC_3A-3A_n257L
DC_3A-3A_n257M
DC_3A_n257G
DC_3A_n257H
DC_3A_n257I
DC_3A_n257J
DC_3A_n257K
DC_7A-7A_n257J
DC_7A-7A_n257K
DC_7A-7A_n257L
DC_7A-7A_n257M
DC_7A_n257J
DC_7A_n257K
DC_7A_n257J
DC_7A_n257K
DC_7A_n257L
DC_7A_n257M
DC_7A_n257J
DC_7A_n257K
Table 1-3: Release 17 NE-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) within FR1
DC combination
Uplink NE-DC configuration
DC_n28A_3A
DC_n28A_3C
DC_n28A_3A
DC_n28A_8A
DC_n28A_8B
DC_n28A_8A
DC_n28A_40A
DC_n28A_40C
DC_n28A_40A
DC_n41A_3A
DC_n41A_3C
DC_n41C_3A
DC_n41A_3A
DC_n41A_8A
DC_n41A_8B
DC_n41C_8A
DC_n41A_8A
DC_n41A_34A1
DC_n41A_34A
DC_n41A_39A1
DC_n41A_39C1
DC_n41C_39A1
DC_n41A_39A
DC_n41A_40A1
DC_n41A_40C1
DC_n41C_40A1
DC_n41A_40A
DC_n3A_1A
DC_n3A_1A
DC_n8A_1A
DC_n8A_1A
DC_n77A_1A
DC_n77(2A)_1A
DC_n77A_1A
DC_n77A_3A
DC_n77(2A)_3A
DC_n77A_3A
DC_n3A_8A
DC_n3A_8A
DC_n8A_3A
DC_n8A_3A
DC_n77A_8A
DC_n77(2A)_8A
DC_n77A_8A
DC_n28A_34A
DC_n28A_34A
DC_n28A_39A
DC_n28A_39C
DC_n28A_39A
NOTE 1: The minimum requirements apply only when there is non-simultaneous Tx/Rx operation between E-UTRA and NR carriers. This restriction applies also for these carriers when applicable EN-DC configuration is part of a higher order EN-DC configuration.
Table 1-4: Release 17 NE-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) including FR2
DC combination
Uplink NE-DC configuration |
37.717-11-21 | Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3,4) LTE inter-band CA (xDL/1UL) and 2 bands NR inter-band CA (2DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-21/37717-11-21-h00.zip | The present document is a technical report for Dual connectivity (DC) band combinations of LTE xDL/1UL (x=1,2,3,4) + inter-band NR 2DL/1UL under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address DC band combinations of LTE xDL/1UL (x=1,2,3,4) + inter-band NR 2DL/1UL in Rel-17 as shown in the WID for Rel-17.
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
37.717-11-31 | Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-31/37717-11-31-h00.zip | The present document is a technical report for DC of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) under Rel-17 time frame, including EN-DC and NE-DC. The purpose is to gather the relevant background information and studies in order to address DC of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and 3 bands NR inter-band CA (3DL/1UL) in Rel-17 as .
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
37.717-11-41 | Rel-17 Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/1UL) and 4 bands NR inter-band CA (4DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-11-41/37717-11-41-h00.zip | The present document is a technical report for DC of x bands (x=1,2) LTE inter-band CA (xDL/1UL) and 4 bands NR inter-band CA (4DL/1UL) under Rel-17 time frame, including EN-DC and NE-DC. The purpose is to gather the relevant background information and studies in order to address DC of x bands (x=1,2) LTE inter-band CA (xDL/1UL) and 4 bands NR inter-band CA (4DL/1UL) in Rel-17 as .
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
37.717-21-11 | Rel-17 Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-21-11/37717-21-11-h00.zip | The present document is a technical report for Dual Connectivity of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual connectivity (DC) band combinations of 3 different bands DL with 2 different bands UL (2 different LTE bands and 1 NR band) for the Rel-17 band combinations. The actual requirements are added to the corresponding technical specification. |
37.717-21-22 | Rel-17 Dual Connectivity (DC) of x bands (x=2,3,4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-21-22/37717-21-22-h00.zip | The present document is a technical report for Dual Connectivity (DC) of x bands (x=2, 3, 4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of x bands (x=2, 3, 4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification. |
37.717-31-11 | Rel-17 Dual Connectivity (DC) of 3 bands LTE inter-band CA (3DL/1UL) and 1 NR band (1DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-31-11/37717-31-11-h00.zip | The present document is a technical report for Dual Connectivity (DC) of 3 LTE bands (3DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 3 LTE band (3DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification. |
37.717-33 | Rel-17 Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA (yDL/yUL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-33/37717-33-h00.zip | The present document is a technical report for Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA (yDL/yUL) under Rel-17 time frame, including EN-DC and NE-DC. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA (yDL/yUL) for the Rel-17 band combinations, where:
- For only 1 NR band included (i.e. x=2 and y=1), only NR FR2 band is applied
- For only 2 NR bands included (i.e. x=1 and y=2), 1 NR FR1 band and 1 NR FR2 band are included and operated as inter-band CA
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
37.717-41-11 | Rel-17 Dual Connectivity (DC) of 4 bands LTE inter-band CA (4DL/1UL) and 1 NR band (1DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-41-11/37717-41-11-h00.zip | The present document is a technical report for Dual Connectivity (DC) of 4 LTE bands (4DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 4 LTE band (4DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification. |
37.717-51-11 | Rel-17 Dual Connectivity (DC) of 5 bands LTE inter-band CA (5DL/1UL) and 1 NR band (1DL/1UL) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.717-51-11/37717-51-11-h00.zip | The present document is a technical report for Dual Connectivity (DC) of 5 LTE bands (5DL/1UL) and 1 NR band (1DL/1UL) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (DC) of 5 LTE band (5DL/1UL) and 1 NR band (1DL/1UL) for the Rel-17 band combinations. The co-existence analysis and RF front end requirements such as ΔRIB,c and ΔTIB,c are described based on the band combination basis since such information have no difference between the DC configurations consisting with the same E-UTRA band and the same NR band. The actual requirements are added to the corresponding technical specification. |
37.817 | Study on enhancement for data collection for NR and ENDC | TR | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.817/37817-h00.zip | The present document provides descriptions of principles for RAN intelligence enabled by AI, the functional framework (e.g., the AI functionality and the input/output of the component for AI enabled optimization) and use cases and solutions of AI enabled RAN.
The study is based on the current architecture and interfaces. |
37.826 | High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.826/37826-h00.zip | The present document is a technical report for High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band within FR1 under Rel-17 timeframe, including both FDD+TDD and TDD+TDD EN-DC band combinations. FDD+TDD band combinations could support LTE 23dBm + NR 23dBm and LTE 23dBm + NR 26dBm, while TDD+TDD band combinations support only LTE 23dBm + NR 23dBm. Completion of PC3 for particular EN-DC combination is the prerequisite for introducing PC2 for that combination. All the PC2 EN-DC combinations are release-independent from Rel-15.
The purpose is to gather the relevant background information and studies in order to address Power Class 2 EN-DC of 1 LTE band and 1 NR TDD band for the Rel-17 band combinations in Table 1-1. The actual requirements are added to the corresponding technical specifications. |
37.827 | Rel-17 Power Class 2 for EN-DC with xLTE band + yNR DL with 1LTE+1(TDD) NR UL band (x= 2, 3, y=1; x=1, 2, y=2) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.827/37827-h00.zip | The present document is a technical report Power Class 2 for EN-DC with xLTE band + yNR DL with 1LTE+1(TDD) NR UL band (x= 2, 3, 4, y=1; x=1, 2, y=2) under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address relevant requirements for the Rel-17 EN-DC band combinations with Power Class 2 requested by proponents and captured in the WID... |
37.828 | High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands and NR bands | TR | 17.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.828/37828-h20.zip | The present document is a technical report for release 17 basket WI High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands and NR bands. |
37.867 | Downlink interruption for band combinations to conduct dynamic Tx Switching | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.867/37867-h00.zip | The present document is a technical report for WI “downlink interruption for band combinations to conduct dynamic Tx Switching” under Rel-17 time frame. The purpose is to gather the relevant background information and studies in order to address the band combinations requested for mandating no DL interruption to conduct dynamic Tx switching listed in Table 1-1.
Table 1-1: Band combinations requested for mandating no DL interruption
Configuration
Uplink configuration
Company
CA_n5-n78, DC_5_n78
CA_n5-n78, DC_5_n78
China Telecom
CA_n1-n3-n78
CA_n1-n78, CA_n3-n78
China Telecom, China Unicom
CA_n3-n40-n41
CA n3-n40, CA n3-n41
CMCC
CA_n3-n41-n79
CA n3-n41, CA n3-n79, CA n41-n49
CMCC
CA_n39-n41-n79
CA n39-n79, CA n41-n79, CA n39-n41
CMCC
CA_n40-n41-n79
CA n40-n79, CA n41-n79
CMCC
CA_n8-n39-n41
CA n8-n39, CA n8-n41, CA n39-n41
CMCC
CA_n8-n41-n79
CA n8-n41, CA n8-n79, CA n41-n79
CMCC |
37.875 | Band combinations for Uu and V2X con-current operation | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.875/37875-h00.zip | The present document is the Technical Report on TR on band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band.
The purpose of the present document is to study the extension of the band combinations for V2X service to grow the NR V2X ecosystem. Operators propose new band combinations for con-current operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X band. Whether to specify con-current operation of LTE/NR CA/DC band combinations and V2X band depends on requests in Rel-17. Specifically, the self-desensitization problem of con-current operation band combinations will be analysed including harmonics, IMD problem, etc.. Also the candidate solutions will be studied to solve the self-desensitization problem.
Table 1-1: Release 17 NR V2X band combinations
V2X Band combination
REL independent from
V2X_n39-n47
Rel-16
V2X_n40-n47
Rel-16
V2X_n41-n47
Rel-16
V2X_n78-n47
Rel-16
V2X_n79-n47
Rel-16
V2X_n39_47
Rel-16
V2X_n40_47
Rel-16
V2X_n41_47
Rel-16
V2X_n78_47
Rel-16
V2X_n79_47
Rel-16
V2X_3_n47
Rel-16
V2X_39_n47
Rel-16
V2X_40_n47
Rel-16
V2X_41_n47
Rel-16
Note: All band combinations in table 1-1 that are release independent from Rel-16 are optional |
37.880 | Study on high-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands 5 and 12 and NR band n71 | TR | 17.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.880/37880-h20.zip | The present document captures the findings from the study item "Study on High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71". |
37.900 | Radio Frequency (RF) requirements for Multicarrier and Multiple Radio Access Technology (Multi-RAT) Base Station (BS) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.900/37900-h00.zip | |
37.902 | Measurements of User Equipment (UE) radio performances for LTE/UMTS terminals; Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology | TR | 17.1.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.902/37902-h10.zip | |
37.910 | Study on self evaluation towards IMT-2020 submission | TR | 17.0.0 | RP | https://www.3gpp.org/ftp/Specs/archive/37_series/37.910/37910-h00.zip | |
37.941 | Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements | TR | 17.6.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.941/37941-h60.zip | |
37.976 | Measurement of radiated performance for Multiple Input Multiple Output (MIMO) and multi-antenna reception for High Speed Packet Access (HSPA) and LTE terminals | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.976/37976-h00.zip | |
37.977 | Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Verification of radiated multi-antenna reception performance of User Equipment (UE) | TR | 17.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.977/37977-h00.zip | |
37.985 | Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR | TR | 17.2.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/37_series/37.985/37985-h20.zip | |
38.101-1 | NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone | TS | 17.18.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-1/38101-1-hi0.zip | |
38.101-2 | NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone | TS | 17.18.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-2/38101-2-hi0.zip | |
38.101-3 | NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios | TS | 17.18.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-3/38101-3-hi0.zip | |
38.101-4 | NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements | TS | 17.17.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-4/38101-4-hh0.zip | |
38.101-5 | NR; User Equipment (UE) radio transmission and reception; Part 5: Satellite access Radio Frequency (RF) and performance requirements | TS | 17.12.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.101-5/38101-5-hc0.zip | |
38.104 | NR; Base Station (BS) radio transmission and reception | TS | 17.18.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.104/38104-hi0.zip | |
38.106 | NR repeater radio transmission and reception | TS | 17.11.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.106/38106-hb0.zip | |
38.108 | NR; Satellite Access Node radio transmission and reception | TS | 17.11.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.108/38108-hb0.zip | |
38.113 | NR; Base Station (BS) ElectroMagnetic Compatibility (EMC) | TS | 17.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.113/38113-h70.zip | |
38.114 | NR; Repeaters ElectroMagnetic Compatibility (EMC) | TS | 17.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.114/38114-h70.zip | |
38.115-1 | NR; Repeater conformance testing - Part 1: Conducted conformance testing | TS | 17.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.115-1/38115-1-h70.zip | |
38.115-2 | NR; Repeater conformance testing - Part 2: Radiated conformance testing | TS | 17.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.115-2/38115-2-h70.zip | |
38.124 | NR; Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 17.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.124/38124-h20.zip | |
38.133 | NR; Requirements for support of radio resource management | TS | 17.18.1 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.133/38133-hi1.zip | |
38.141-1 | NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing | TS | 17.18.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.141-1/38141-1-hi0.zip | |
38.141-2 | NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing | TS | 17.18.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.141-2/38141-2-hi0.zip | |
38.151 | NR; User Equipment (UE) Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance requirements | TS | 17.11.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.151/38151-hb0.zip | |
38.174 | NR; Integrated Access and Backhaul (IAB) radio transmission and reception | TS | 17.10.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.174/38174-ha0.zip | |
38.171 | NR; Requirements for support of Assisted Global Navigation Satellite System (A-GNSS) | TS | 17.4.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.171/38171-h40.zip | |
38.161 | NR; User Equipment (UE) TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements; Range 1 Standalone and Range 1 Interworking operation with other radios | TS | 17.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.161/38161-h50.zip | |
38.175 | NR; Integrated Access and Backhaul (IAB) Electromagnetic Compatibility (EMC) | TS | 17.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.175/38175-h50.zip | |
38.176-1 | NR; Integrated Access and Backhaul (IAB) conformance testing; Part 1: Conducted conformance testing | TS | 17.12.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.176-1/38176-1-hc0.zip | |
38.176-2 | NR; Integrated Access and Backhaul (IAB) conformance testing; Part 2: Radiated conformance testing | TS | 17.12.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.176-2/38176-2-hc0.zip | |
38.181 | NR; Satellite Access Node conformance testing | TS | 17.8.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.181/38181-h80.zip | |
38.201 | NR; Physical layer; General description | TS | 17.0.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.201/38201-h00.zip | |
38.202 | NR; Services provided by the physical layer | TS | 17.5.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.202/38202-h50.zip | |
38.211 | NR; Physical channels and modulation | TS | 17.10.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.211/38211-ha0.zip | |
38.212 | NR; Multiplexing and channel coding | TS | 17.12.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.212/38212-hc0.zip | |
38.213 | NR; Physical layer procedures for control | TS | 17.13.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.213/38213-hd0.zip | |
38.214 | NR; Physical layer procedures for data | TS | 17.14.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.214/38214-he0.zip | |
38.215 | NR; Physical layer measurements | TS | 17.5.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.215/38215-h50.zip | |
38.300 | NR; NR and NG-RAN Overall description; Stage-2 | TS | 17.13.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.300/38300-hd0.zip | |
38.304 | NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state | TS | 17.10.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.304/38304-ha0.zip | |
38.305 | NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN | TS | 17.8.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.305/38305-h80.zip | |
38.306 | NR; User Equipment (UE) radio access capabilities | TS | 17.13.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.306/38306-hd0.zip | |
38.307 | NR; Requirements on User Equipments (UEs) supporting a release-independent frequency band | TS | 17.13.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.307/38307-hd0.zip | |
38.314 | NR; Layer 2 measurements | TS | 17.5.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.314/38314-h50.zip | |
38.321 | NR; Medium Access Control (MAC) protocol specification | TS | 17.13.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.321/38321-hd0.zip | |
38.322 | NR; Radio Link Control (RLC) protocol specification | TS | 17.4.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.322/38322-h40.zip | |
38.323 | NR; Packet Data Convergence Protocol (PDCP) specification | TS | 17.5.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.323/38323-h50.zip | |
38.331 | NR; Radio Resource Control (RRC); Protocol specification | TS | 17.13.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.331/38331-hd0.zip | |
38.340 | NR; Backhaul Adaptation Protocol (BAP) specification | TS | 17.5.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.340/38340-h50.zip | |
38.351 | NR; Sidelink Relay Adaptation Protocol (SRAP) Specification | TS | 17.8.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.351/38351-h80.zip | |
38.401 | NG-RAN; Architecture description | TS | 17.10.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.401/38401-ha0.zip | |
38.410 | NG-RAN; NG general aspects and principles | TS | 17.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.410/38410-h10.zip | |
38.411 | NG-RAN; NG layer 1 | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.411/38411-h00.zip | |
38.412 | NG-RAN; NG signalling transport | TS | 17.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.412/38412-h10.zip | |
38.413 | NG-RAN; NG Application Protocol (NGAP) | TS | 17.12.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.413/38413-hc0.zip | |
38.414 | NG-RAN; NG data transport | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.414/38414-h00.zip | |
38.415 | NG-RAN; PDU session user plane protocol | TS | 17.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.415/38415-h10.zip | |
38.420 | NG-RAN; Xn general aspects and principles | TS | 17.2.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.420/38420-h20.zip | |
38.421 | NG-RAN; Xn layer 1 | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.421/38421-h00.zip | |
38.422 | NG-RAN; Xn signalling transport | TS | 17.1.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.422/38422-h10.zip | |
38.423 | NG-RAN; Xn Application Protocol (XnAP) | TS | 17.13.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.423/38423-hd0.zip | |
38.424 | NG-RAN; Xn data transport | TS | 17.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.424/38424-h00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.