4 General
38.521-33GPPNRPart 3: Range 1 and Range 2 Interworking operation with other radiosRadio transmission and receptionRelease 17TSUser Equipment (UE) conformance specification
4.1 Relationship between minimum requirements and test requirements
TS 38.101-3 [4] is interwork specification for NR UE, covering RF characteristics and minimum performance requirements. Conformance to TS 38.101-3 [4] is demonstrated by fulfilling the test requirements specified in the present document.
The Minimum Requirements given in TS 38.101-3 [4] make no allowance for measurement uncertainty (MU). The present document defines test tolerances (TT). These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in TS 38.101-3 [4] to create test requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero.
The measurement results returned by the test system are compared – without any modification – against the test requirements as defined by various levels of "Shared Risk" principle as described below.
a) Core specification value is not relaxed by any relaxation value (TT=0). For each single measurement, the probability of a borderline good UE being judged as FAIL equals the probability of a borderline bad UE being judged as PASS.
– Test tolerances equal to 0 (TT=0) are considered in this specification.
b) Core specification value is relaxed by a relaxation value (TT>0). For each single measurement, the probability of a borderline bad UE being judged as PASS is greater than the probability of a borderline good UE being judged as FAIL.
– Test tolerances lower than measurement uncertainty and greater than 0 (0 < TT < MU) are considered in this specification.
– Test tolerances high up to measurement uncertainty (TT = MU) are considered in this specification which is also known as "Never fail a good DUT" principle.
c) Core specification value is tightened by a stringent value (TT<0). For each single measurement, the probability of a borderline good UE being judged as FAIL is greater than the probability of a borderline bad UE being judged as PASS.
– Test tolerances lower than 0 (TT<0) are not considered in this specification.
The "Never fail a good DUT" and the "Shared Risk" principles are defined in Recommendation ITU‑R M.1545 [21].
4.2 Applicability of minimum requirements
a) In TS 38.101-3 [4] the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios
b) For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements.
c) The spurious emissions power requirements are for the long-term average of the power. For the purpose of reducing measurement uncertainty, it is acceptable to average the measured power over a period of time sufficient to reduce the uncertainty due to the statistical nature of the signal.
d) Terminal that supports EN-DC configuration shall meet E-UTRA requirements as specified in TS 36.101 [5] and NR requirements as in TS 38.101-1 [2] and TS 38.101-2 [3] unless otherwise specified in TS 38.101-3 [4].
e) All the requirements for intra-band contiguous and non-contiguous EN-DC or NE-DC apply under the assumption of the same uplink-downlink and special subframe configurations in the E-UTRA and slot format indicated by UL-DL-configurationCommon and UL-DL-configurationDedicated in the NR for the EN-DC or NE-DC.
f) For EN-DC or NE-DC combinations with CA configurations for E-UTRA and/or NR, all the requirements for E-UTRA and/or NR all the requirements for E-UTRA and/or NR intra-band contiguous and non-contiguous CA apply under the assumption of the same slot format indicated by UL-DL-configurationCommon and UL-DL-configurationDedicated in the PSCell and SCells for NR and the same uplink-downlink and special subframe configurations in PCell and SCells for E-UTRA.
A terminal which supports an EN-DC or NE-DC configuration shall support:
– If any subsets of the EN-DC or NE-DC configuration do not specify its own bandwidth combination sets in 5.3B, then the terminal shall support the same E-UTRA bandwidth combination sets it signals the support for in E-UTRA CA configuration part of E-UTRA – NR DC and shall support the same NR bandwidth combination sets it signals the support for in NR CA configuration part of E-UTRA – NR DC.
– Else if one of the subsets of the EN-DC or NE-DC configuration specify its own bandwidth combination sets in 5.3B, then the terminal shall support a product set of channel bandwidth for each band specified by E-UTRA bandwidth combination sets, NR bandwidth combination sets, and EN-DC or NE-DC bandwidth combination sets it signals the support.
A terminal which supports an inter-band EN-DC or NE-DC configuration with a certain UL configuration shall support the all lower order DL configurations of the lower order EN-DC or NE-DC combinations, which have this certain UL configuration and the fallbacks of this UL configuration.
A terminal which supports NE-DC configurations shall meet the minimum requirements for corresponding EN-DC configuration, unless otherwise specified.
For CA or DC configurations, which include FR2 intra-band CA combinations with multiple FR2 subblocks, where at least one of the subblocks is contiguous CA combination.
– if the field partialFR2-FallbackRX-Req is not present, the UE shall meet all applicable UE RF requirements for the highest order CA configuration and all associated fallback CA configurations;
– if the field partialFR2-FallbackRX-Req is present, for each FR2 intra-band CA configuration with multiple sub-blocks that the UE indicates support for explicitly in UE capability signalling: the in-gap UE RF requirements in clauses 7.5A, 7.5B, 7.6A, 7.6B apply as the equivalent requirements for the associated fallback FR2 intra-band CA configurations with the same number of sub-blocks, where at least one of the sub-blocks consists of a contiguous CA configuration. The UE shall meet all applicable UE RF requirements for fallback CA configurations with a lesser number of sub-blocks;
– regardless of the field partialFR2-FallbackRX-Req, the UE shall meet all DL out-of-gap requirements for all lower order fallback CA configurations.
Terminal that supports inter-band NR-DC between FR1 and FR2 configuration shall meet the requirements for corresponding CA configuration (suffix A), unless otherwise specified.
4.3 Specification suffix information
Unless stated otherwise the following suffixes are used for indicating at 2nd level clause, shown in Table 4.3-1.
Table 4.3-1: Definition of suffixes
|
Clause suffix |
Variant |
|
None |
Single Carrier |
|
A |
Carrier Aggregation (CA) between FR1 and FR2 |
|
B |
Dual-Connectivity (DC) with and without SUL including UL sharing from UE perspective, inter-band NR DC between FR1 and FR2 |
|
D |
UL MIMO |
|
E |
V2X |
|
F |
Shared spectrum channel access |
4.4 Test points analysis
The information on test point analysis and test point selection including number of test points for each test case is shown in TR 38.905 [7] clause 4.3.
4.5 Applicability and test coverage rules
4.5.0 General
(1) The applicability and test coverage rules for Non-Standalone (NSA) only capable devices shall include the following:
a) For each NR band in a device; test all the EN-DC or NE-DC exception test requirements as per test procedures in this specification.
b) Test all the EN-DC or NE-DC FR2 non-exception test requirements in this specification with test procedures which refer appropriately back to TS 38.521-2 [9] for each NR band. Test only one EN-DC or NE-DC combination per FR2 band for each EN-DC or NE-DC configuration as defined in clause 5.5B of TS 38.101-3 [4] using LTE anchor agnostic approach.
c) Test all the EN-DC or NE-DC FR1 non-exception test requirements in this specification with test procedures which refer appropriately back to TS 38.521-1 [8] for each NR band. Test only one EN-DC or NE-DC combination per FR1 band for each EN-DC or NE-DC configuration as defined in clause 5.5B of 38.101-3 [4] using LTE anchor agnostic approach.
(2) The applicability and test coverage rules for Standalone (SA) and NSA capable devices shall include the following:
a) For each NR band in a device, test all the EN-DC or NE-DC exception test requirements as per test procedures in this specification.
b) Test all the Standalone FR2 test requirements as per test procedures in TS 38.521-2 [9] for each NR band. This also fulfils coverage for all non-exception EN-DC or NE-DC FR2 test requirements for that NR band and need not be retested. If Standalone FR2 cannot be tested (due to test case not being complete), then test in EN-DC or NE-DC mode following (1)(b) above.
c) Test all the Standalone FR1 test requirements as per test procedures in TS 38.521-1 [8] for each NR band. This also fulfils coverage for all non-exception EN-DC or NE-DC FR1 test requirements for that NR band and need not be retested. If Standalone FR1 cannot be tested (due to test case not being complete or if the UE does not support the band in SA mode), then test in EN-DC or NE-DC mode following (1)(c) above.
4.5.1 Test coverage across 5G NR connectivity options
The test cases in this specification cover both NR/5GC (including FR1+FR2 CA or FR1+FR2 NR-DC) as well as EN-DC, NE-DC and NGEN-DC testing. Below shall be the understanding with respect to coverage across 5G NR connectivity options:
1) Unless otherwise stated within the test case, it shall be understood that test requirements are agnostic of the EN-DC, NE-DC and NGEN-DC connectivity options configured within the test. The test coverage across the EN-DC, NE-DC and NGEN-DC connectivity options shall be considered fulfilled by executing the test case in one of these connectivity options. In the case of non-exception requirements, test coverage of NE-DC is fulfilled by execution of NR/5GC connectivity option test cases.
2) EN-DC is the default connectivity option used for EN-DC, NE-DC and NGEN-DC test cases.
3) If a UE does not support EN-DC, any other supported connectivity option of NE-DC or NGEN-DC can be configured to execute the test. The leverage rule detailed in (1) would apply.
Table 4.5.1-1: Void
Table 4.5.1-2: Void
4.6 E-UTRA configuration for EN-DC FR1 tests applying the E-UTRA anchor-agnostic approach
This clause applies to EN-DC test cases where E-UTRA anchor needs to be configured as per the anchor-agnostic approach outlined in clauses 6.1 and 7.1 of TS 38.101-3 [4].The LTE anchor-agnostic approach is defined as measurements on the NR carrier under conditions where the LTE anchor resources do not interfere with NR operation. The configuration defined in this clause ensures establishment of such conditions.
For baseline configuration, the E-UTRA carrier will be configured for each test case in clauses 6 and 7 as defined in the equivalent standalone E-UTRA test in TS 36.521-1 [10]. However, the below exceptions defined in Table 4.6-1, 4.6-2, 4.6-3, 4.6-4 and 4.6-5 are applied to ensure that the E-UTRA anchor resources do not interfere with NR operation.
For EN-DC within FR1 band combinations with multiple E-UTRA component carriers, it is sufficient to configure any one E-UTRA carrier from the carrier group whenever it is determined that anchor agnostic approach can be applied. Unless otherwise stated, the number of component carriers (CCs) listed in the test case titles of Clause 6 and clause 7 shall refer to the number of component carriers configured within the test case.
Table 4.6-1: E-UTRA configuration for EN-DC FR1 tests applying anchor agnostic approach
|
Parameter |
Value |
Comments |
|
Test Frequency during and after connection setup |
Mid (See Table 4.6-2) |
As defined in TS 36.508 for the LTE band under test |
|
Bandwidth during and after connection setup |
5 MHz (See Table 4.6-2) |
Supported by all LTE bands. |
|
DL signal levels during connection setup |
RS EPRE -85.0 dBm/15kHz |
DL physical channels as defined in Annex C0, C.1, C.2 and Annex C.3 of TS 36.521-1 [10]. TS 36.521-1 [10] annex C.0 defines the default DL power level of RS EPRE to be -85dBm/15kHz. |
|
UL Signal levels during connection setup |
PUSCH Power |
Attained by enabling open loop power control and setting up UL signal levels according to Annex H.0, H.2 and H.3 of TS 36.521-1 [10]. |
|
DL/UL RMC after connection setup |
0 RB allocation on both DL and UL (see Table 4.6-2) |
Once the LTE link is established, then LTE Tx can be restricted by configuring 0 RB allocation on DL and UL. TimeAlignmentTimerDedicated IE to be set to infinity to ensure UE doesn’t look for TA adjustments (See Table 4.6-5) |
|
CQI Reports and SRS after connection setup |
Disabled (See Table 4.6-3 and 4.6-4) |
Disable periodic and aperiodic CQI reports to ensure none of these transmissions occur on the LTE uplink. Since LTE transmissions could easily exceed spurious emissions limits, tests that are intended to measure RF parameters on the NR should simply avoid LTE transmit altogether. |
|
Number of OFDM symbols for PDCCH |
3 |
The PCFICH carries information about the number of OFDM symbols used for transmission of PDCCHs in a subframe, as specified in TS 36.211 [8] clause 6.7 |
Table 4.6-2: E-UTRA Test Configuration Table
|
E-UTRA Test Parameters |
|||||
|
E-UTRA Channel Bandwidth |
E-UTRA Test Frequency |
Downlink |
Uplink |
||
|
Modulation |
RB allocation |
Modulation |
RB allocation |
||
|
5 MHz2 |
MidRange1 |
N/A |
0 |
N/A |
0 |
|
NOTE 1: E-UTRA Test Frequency as specified in TS 36.508 [11] clause 4.3.1. NOTE 2: For EN-DC Intra-band tests that need to apply E-UTRA anchor agnostic approach, refer to and pick applicable E-UTRA channel bandwidth from clause 5.3B.1 and indicate within test case if it is different than 5 MHz. |
|||||
Table 4.6-3: CQI-ReportConfig-DEFAULT: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.6.3, Table 4.6.3-2 CQI-ReportConfig-DEFAULT |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CQI-ReportConfig-DEFAULT ::= SEQUENCE { |
||||
|
cqi-ReportModeAperiodic |
NOT PRESENT |
|||
|
cqi-ReportPeriodic |
NOT PRESENT |
|||
|
} |
||||
Table 4.6-4: PhysicalConfigDedicated-DEFAULT: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.8.2, Table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
||||
|
soundingRS-UL-ConfigDedicated |
Not present |
RBC |
||
|
} |
||||
Table 4.6-5: MAC-MainConfig-RBC: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.8.2.1.5, Table 4.8.2.1.5-1 MAC-MainConfig-RBC |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
timeAlignmentTimerDedicated |
Infinity |
|||
4.7 E-UTRA configuration for EN-DC FR2 tests applying the E-UTRA anchor-agnostic approach
This clause applies to EN-DC test cases where E-UTRA anchor needs to be configured as per the anchor-agnostic approach outlined in clauses 6.1 and 7.1 of TS 38.101-3 [4].The LTE anchor-agnostic approach is defined as measurements on the NR carrier under conditions where the LTE anchor resources do not interfere with NR operation. The configuration defined in this clause ensures establishment of such conditions.
For baseline configuration, the E-UTRA carrier will be configured for each test case in clauses 6 and 7 as defined in the equivalent standalone E-UTRA test in TS 36.521-1 [10]. However, the below exceptions defined in Table 4.7-1 to 4.7-7 are applied to ensure that the E-UTRA anchor resources do not interfere with NR operation.
Since the E-UTRA link is always a functional link when testing EN-DC including FR2 band combinations, it is sufficient to configure any one E-UTRA carrier from the carrier group, irrespective of the number of E-UTRA carriers in the EN-DC combination under test. Unless otherwise stated, the number of component carriers (CCs) listed in the test case titles of Clause 6 and clause 7 shall refer to the number of component carriers configured within the test case.
Table 4.7-1: E-UTRA configuration for EN-DC FR2 tests applying anchor agnostic approach
|
Parameter |
Value |
Comments |
|
Test Frequency during and after connection setup |
Mid (See Table 4.7-2) |
As defined in TS 36.508 for the LTE band under test |
|
Bandwidth during and after connection setup |
5 MHz (See Table 4.7-2) |
Supported by all LTE bands. |
|
DL signal levels |
See table 4.7-3 |
DL physical channels as defined in Annex C0, C.1, C.2 and Annex C.3 of TS 36.521-1 [10]. |
|
UL Signal levels for connection setup and UBF transmission |
PUSCH Power |
Attained by enabling open loop power control and setting up UL signal levels according to Annex H.0, H.2 and H.3 of TS 36.521-1 [10] with the exception for power control message exception defined in Table 4.7-5 |
|
DL/UL RMC after connection setup except for UBF transmission |
0 RB allocation on both DL and UL (see Table 4.7-2) |
Once the LTE link is established, then LTE Tx can be restricted by configuring 0 RB allocation on DL and UL. TimeAlignmentTimerDedicated IE to be set to infinity to ensure UE doesn’t look for TA adjustments (See Table 4.7-7) |
|
CQI Reports and SRS after connection setup |
Disabled (See Table 4.7-4 and 4.7-6) |
Disable periodic and aperiodic CQI reports to ensure none of these transmissions occur on the LTE uplink. Since LTE transmissions could easily exceed spurious emissions limits, tests that are intended to measure RF parametrics on the NR should simply avoid LTE transmit altogether. |
|
Number of OFDM symbols for PDCCH |
3 |
The PCFICH carries information about the number of OFDM symbols used for transmission of PDCCHs in a subframe, as specified in TS 36.211 [8] clause 6.7 |
Table 4.7-2: E-UTRA Test Configuration Table
|
E-UTRA Test Parameters |
|||||
|
E-UTRA Channel Bandwidth |
E-UTRA Test Frequency |
Downlink |
Uplink |
||
|
Modulation |
RB allocation |
Modulation |
RB allocation |
||
|
5 MHz2 |
MidRange1 |
N/A |
0 |
N/A |
0 |
|
NOTE 1: E-UTRA Test Frequency as specified in TS 36.508 [11] clause 4.3.1 NOTE 2: For EN-DC Intra-band tests that need to apply E-UTRA anchor agnostic approach, refer to and pick applicable E-UTRA channel bandwidth from clause 5.3B.1 and indicate within test case if it is different than 5 MHz. |
|||||
Table 4.7-3: Default Downlink power levels for E-UTRA anchor
|
Unit |
Band Group |
Channel Bandwidth |
||||||
|
1.4 MHz |
3 MHz |
5MHz |
10MHz |
15 MHz |
20 MHz |
|||
|
RS EPRE |
dBm/15kHz |
FDD_A, TDD_A |
N/A |
N/A |
≥ -120.0 |
N/A |
N/A |
N/A |
|
FDD_B1, TDD_B1 |
N/A |
N/A |
≥ -119.5 |
N/A |
N/A |
N/A |
||
|
FDD_C, TDD_C |
N/A |
N/A |
≥ -119.0 |
N/A |
N/A |
N/A |
||
|
FDD_D, TDD_D |
N/A |
N/A |
≥ -118.5 |
N/A |
N/A |
N/A |
||
|
FDD_E, TDD_E |
N/A |
N/A |
≥ -118.0 |
N/A |
N/A |
N/A |
||
|
FDD_G, TDD_G |
N/A |
N/A |
≥ -117.0 |
N/A |
N/A |
N/A |
||
|
FDD_H, TDD_H |
N/A |
N/A |
≥ -116.5 |
N/A |
N/A |
N/A |
||
|
FDD_N, TDD_N |
N/A |
N/A |
≥ -113.5 |
N/A |
N/A |
N/A |
||
|
NOTE 1: The power level is specified at RSRP reference point as defined in TS 36.214 [24] NOTE 2: E-UTRA Band groups are defined in TS 36.133 [12] clause 3.5.1. |
||||||||
Table 4.7-4: CQI-ReportConfig-DEFAULT: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.6.3, Table 4.6.3-2 CQI-ReportConfig-DEFAULT |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CQI-ReportConfig-DEFAULT ::= SEQUENCE { |
||||
|
cqi-ReportModeAperiodic |
NOT PRESENT |
|||
|
cqi-ReportPeriodic |
NOT PRESENT |
|||
|
} |
||||
Table 4.7-5: UplinkPowerControlCommon-DEFAULT : Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.6.3, UplinkPowerControlCommon-DEFAULT |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UplinkPowerControlCommon-DEFAULT ::= SEQUENCE { |
|||
|
p0-NominalPUSCH |
-60 (-60 dBm) |
To attain maximum power from the DUT |
|
|
} |
|||
Table 4.7-6: PhysicalConfigDedicated-DEFAULT: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.8.2, Table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
||||
|
soundingRS-UL-ConfigDedicated |
Not present |
RBC |
||
|
} |
||||
Table 4.7-7: MAC-MainConfig-RBC: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.8.2.1.5, Table 4.8.2.1.5-1 MAC-MainConfig-RBC |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
timeAlignmentTimerDedicated |
Infinity |
|||
4.8 E-UTRA configuration for EN-DC FR1 tests not applying the E-UTRA anchor-agnostic approach
Unless otherwise stated, the following message exception defined in tables 4.8-1, 4.8-2 and 4.8-3 apply for EN-DC FR1 tests not applying the E-UTRA anchor-agnostic approach.
Table 4.8-1: CQI-ReportConfig-DEFAULT: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.6.3, Table 4.6.3-2 CQI-ReportConfig-DEFAULT |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
CQI-ReportConfig-DEFAULT ::= SEQUENCE { |
||||
|
cqi-ReportModeAperiodic |
NOT PRESENT |
|||
|
cqi-ReportPeriodic |
NOT PRESENT |
|||
|
} |
||||
Table 4.8-2: PhysicalConfigDedicated-DEFAULT: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.8.2, Table 4.8.2.1.6-1 PhysicalConfigDedicated-DEFAULT |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
||||
|
soundingRS-UL-ConfigDedicated |
Not present |
RBC |
||
|
} |
||||
Table 4.8-3: MAC-MainConfig-RBC: Additional E-UTRA Anchor Configuration
|
Derivation Path: TS 36.508 [7] clause 4.8.2.1.5, Table 4.8.2.1.5-1 MAC-MainConfig-RBC |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
timeAlignmentTimerDedicated |
Infinity |
|||