5.5 Sustained downlink data rate provided by lower layers
38.521-43GPPNRPart 4: PerformanceRadio transmission and receptionRelease 17TSUser Equipment (UE) conformance specification
5.5.1 FR1 Sustained downlink data rate performance for single carrier
5.5.1.1 Test Purpose
The purpose of the test is to verify that the Layer 1 and Layer 2 correctly process in a sustained manner the received packets corresponding to the maximum data rate indicated by UE capabilities. The sustained downlink data rate shall be verified in terms of the success rate of delivered PDCP SDU(s) by Layer 2. The test case below specifies the RF conditions and the required success rate of delivered TB by Layer 1 to meet the sustained data rate requirement
5.5.1.2 Test Applicability
This test applies to all types of NR UE release 15 and forward.
5.5.1.3 Minimum conformance requirements
The requirements in this clause are applicable to the FR1 single carrier case.
The TB success rate shall be higher than 85% when PDSCH is scheduled with MCS defined for the channel bandwidth with the downlink physical channel setup according to Annex C.3.1.
The TB success rate is defined as 100%*NDL_correct_rx / (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks.
The common test parameters are specified in Table 5.5.1.3-1. The parameters specified in Table 5.5.1.3-2 are applicable for tests on FDD bands and parameters specified in Table 5.5.1.3-3 are applicable for tests on TDD bands.
Unless otherwise stated, no user data is scheduled on slot #0, 10 and 11 within 20 ms for SCS 15 kHz.
Unless otherwise stated, no user data is scheduled on slot #0, 20 and 21 within 20 ms for SCS 30 kHz.
Table 5.5.1.3-1: Common test parameters for FDD and TDD bands
|
Parameter |
Unit |
Value |
||
|
PDSCH transmission scheme |
Transmission scheme 1 |
|||
|
EPRE ratio of PTRS to PDSCH |
dB |
N/A |
||
|
Channel bandwidth |
MHz |
Channel bandwidth from selected CA bandwidth combination |
||
|
Common serving cell parameters |
Physical Cell ID |
0 |
||
|
SSB position in burst |
First SSB in Slot #0 |
|||
|
SSB periodicity |
ms |
20 |
||
|
First DMRS position for Type A PDSCH mapping |
2 |
|||
|
Cross carrier scheduling |
Not configured |
|||
|
Active DL BWP index |
1 |
|||
|
Actual carrier configuration |
Offset between Point A and the lowest usable subcarrier on this carrier (Note 2) |
RBs |
0 |
|
|
Subcarrier spacing |
kHz |
15 or 30 |
||
|
DL BWP configuration #1 |
RB offset |
RBs |
0 |
|
|
Number of contiguous PRB |
Maximum transmission bandwidth configuration as specified in clause 5.3.2 of TS 38.101-1 [2] for tested channel bandwidth and subcarrier spacing |
|||
|
Subcarrier spacing |
kHz |
15 or 30 |
||
|
Cyclic prefix |
Normal |
|||
|
PDCCH configuration |
Slots for PDCCH monitoring |
Each slot |
||
|
Symbols with PDCCH |
Symbols #0 |
|||
|
Number of PRBs in CORESET |
Table 5.5.1.3-4 |
|||
|
Number of PDCCH candidates and aggregation levels |
2/AL2 for 15 kHz / 5 MHz and 30 kHz / 15 MHz 2/AL4 for 15 kHz / 10 MHz, 30 kHz / 10 MHz and 30 kHz / 20 MHz 2/AL8 for other greater combinations |
|||
|
CCE-to-REG mapping type |
Non-interleaved |
|||
|
DCI format |
1_1 |
|||
|
TCI State |
TCI state #1 |
|||
|
PDCCH & PDCCH DMRS Precoding configuration |
For 2Tx: Single Panel Type I, Random precoder chosen from precoder index 0 and 2, selection updated per slot For 4Tx: Single Panel Type I, Random precoder chosen from precoders with i_1,1 in {1,2,3,5,6,7} and i_2 in {0,2}, selection updated per slot |
|||
|
PDSCH configuration |
Mapping type |
Type A |
||
|
k0 |
0 |
|||
|
PDSCH aggregation factor |
1 |
|||
|
PRB bundling type |
Static |
|||
|
PRB bundling size |
WB |
|||
|
Resource allocation type |
Type 0 |
|||
|
VRB-to-PRB mapping type |
Non-interleaved |
|||
|
VRB-to-PRB mapping interleaver bundle size |
N/A |
|||
|
PDSCH DMRS configuration |
DMRS Type |
Type 1 |
||
|
Number of additional DMRS |
1 |
|||
|
Length |
1 |
|||
|
Antenna ports indexes |
{1000} for 1 Layer CCs {1000 – 1003} for 4 Layers CCs |
|||
|
Number of PDSCH DMRS CDM group(s) without data |
1 for 1 layer and 2 layers CCs 2 for 4 Layers CCs |
|||
|
PTRS configuration |
PTRS is not configured |
|||
|
CSI-RS for tracking |
Subcarrier indexes in the PRB used for CSI-RS |
k0 = 3 for CSI-RS resource 1,2,3,4 |
||
|
OFDM symbols in the PRB used for CSI-RS |
l0 = 6 for CSI-RS resource 1 and 3 l0 = 10 for CSI-RS resource 2 and 4 |
|||
|
Number of CSI-RS ports (X) |
1 for CSI-RS resource 1,2,3,4 |
|||
|
CDM Type |
‘No CDM’ for CSI-RS resource 1,2,3,4 |
|||
|
Density (ρ) |
3 for CSI-RS resource 1,2,3,4 |
|||
|
CSI-RS periodicity |
Slots |
15 kHz SCS: 20 for CSI-RS resource 1,2,3,4 30 kHz SCS: 40 for CSI-RS resource 1,2,3,4 |
||
|
CSI-RS offset |
Slots |
15 kHz SCS: 10 for CSI-RS resource 1 and 2 11 for CSI-RS resource 3 and 4 30 kHz SCS: 20 for CSI-RS resource 1 and 2 21 for CSI-RS resource 3 and 4 |
||
|
Frequency Occupation |
Start PRB 0 Number of PRB = BWP size |
|||
|
QCL info |
TCI state #0 |
|||
|
NZP CSI-RS for CSI acquisition |
Subcarrier indexes in the PRB used for CSI-RS |
k0 = 4 |
||
|
OFDM symbols in the PRB used for CSI-RS |
l0 = 12 |
|||
|
Number of CSI-RS ports (X) |
Same as number of transmit antenna |
|||
|
CDM Type |
‘FD-CDM2’ |
|||
|
Density (ρ) |
1 |
|||
|
CSI-RS periodicity |
15 kHz SCS: 20 30 kHz SCS: 40 |
|||
|
CSI-RS offset |
0 |
|||
|
Frequency Occupation |
Start PRB 0 Number of PRB = BWP size |
|||
|
QCL info |
TCI state #1 |
|||
|
ZP CSI-RS for CSI acquisition |
Subcarrier indexes in the PRB used for CSI-RS |
k0 = 0 |
||
|
OFDM symbols in the PRB used for CSI-RS |
l0 = 12 |
|||
|
Number of CSI-RS ports (X) |
4 |
|||
|
CDM Type |
‘FD-CDM2’ |
|||
|
Density (ρ) |
1 |
|||
|
CSI-RS periodicity |
15 kHz SCS: 20 30 kHz SCS: 40 |
|||
|
CSI-RS offset |
0 |
|||
|
Frequency Occupation |
Start PRB 0 Number of PRB = BWP size |
|||
|
TCI state #0 |
Type 1 QCL information |
SSB index |
SSB #0 |
|
|
QCL Type |
Type C |
|||
|
Type 2 QCL information |
SSB index |
N/A |
||
|
QCL Type |
N/A |
|||
|
TCI state #1 |
Type 1 QCL information |
CSI-RS resource |
CSI-RS resource 1 from ‘CSI-RS for tracking’ configuration |
|
|
QCL Type |
Type A |
|||
|
Type 2 QCL information |
CSI-RS resource |
N/A |
||
|
QCL Type |
N/A |
|||
|
Maximum number of code block groups for ACK/NACK feedback |
1 |
|||
|
Maximum number of HARQ transmission |
4 |
|||
|
HARQ ACK/NACK bundling |
Multiplexed |
|||
|
Redundancy version coding sequence |
{0,2,3,1} |
|||
|
PDSCH & PDSCH DMRS Precoding configuration |
Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable i1, i2 combination with PRB bundling granularity |
|||
|
Symbols for all unused REs |
OCNG Annex A.5 |
|||
|
Propagation condition |
Static propagation condition No external noise sources are applied |
|||
|
Antenna configuration |
1 layer CCs |
1×2 or 1×4 |
||
|
2 layers CCs |
2×2 or 2×4 |
|||
|
4 layers CCs |
4×4 |
|||
|
Physical signals, channels mapping and precoding |
As specified in Annex B.4.1 |
|||
|
Note 1: UE assumes that the TCI state for the PDSCH is identical to the TCI state applied for the PDCCH transmission Note 2: Point A coincides with minimum guard band as specified in Table 5.3.3-1 from TS 38.101-1 [2] for tested channel bandwidth and subcarrier spacing |
||||
Table 5.5.1.3-2: Additional test parameters for FDD band
|
Parameter |
Unit |
Value |
|
|
Duplex mode |
FDD |
||
|
PDSCH configuration |
Starting symbol (S) |
1 |
|
|
Length (L) |
13 |
||
|
Number of HARQ Processes |
4 |
||
|
K1 value |
2 |
||
Table 5.5.1.3-3: Additional test parameters for TDD band
|
Parameter |
Unit |
Value |
|
|
Duplex mode |
TDD |
||
|
PDSCH configuration |
Starting symbol (S) |
1 |
|
|
Length (L) |
13 |
||
|
Number of HARQ Processes |
8 |
||
|
K1 value |
Specific to each UL-DL pattern |
||
|
TDD UL-DL pattern |
15 kHz SCS: FR1.15-1 30 kHz SCS: FR1.30-1 |
||
|
Note 1: PDSCH is scheduled only on full DL slots |
|||
Table 5.5.1.3-4: Number of PRBs in CORESET
|
SCS (kHz) |
5MHz |
10MHz |
15MHz |
20 MHz |
25 MHz |
30 MHz |
40 MHz |
50MHz |
60 MHz |
80 MHz |
100 MHz |
|
15 |
24 |
48 |
78 |
102 |
132 |
156 |
216 |
270 |
N/A |
N/A |
N/A |
|
30 |
6 |
24 |
36 |
48 |
60 |
78 |
102 |
132 |
162 |
216 |
270 |
Table 5.5.1.3-5: MCS indexes for indicated UE capabilities
|
Maximum number of PDSCH MIMO layers |
Maximum modulation format |
Scaling factor |
MCS |
|
1 |
8 |
1 |
26 |
|
1 |
8 |
0.8 |
21 |
|
1 |
8 |
0.75 |
20 |
|
1 |
8 |
0.4 |
11 |
|
1 |
6 |
1 |
27 |
|
1 |
6 |
0.8 |
23 |
|
1 |
6 |
0.75 |
22 |
|
1 |
6 |
0.4 |
14 |
|
1 |
4 |
1 |
16 |
|
1 |
4 |
0.8 |
16 |
|
1 |
4 |
0.75 |
16 |
|
1 |
4 |
0.4 |
10 |
|
1 |
2 |
1 |
9 |
|
1 |
2 |
0.8 |
9 |
|
1 |
2 |
0.75 |
9 |
|
1 |
2 |
0.4 |
4 |
|
2 |
8 |
1 |
26 |
|
2 |
8 |
0.8 |
21 |
|
2 |
8 |
0.75 |
20 |
|
2 |
8 |
0.4 |
11 |
|
2 |
6 |
1 |
27 |
|
2 |
6 |
0.8 |
23 |
|
2 |
6 |
0.75 |
22 |
|
2 |
6 |
0.4 |
14 |
|
2 |
4 |
1 |
16 |
|
2 |
4 |
0.8 |
16 |
|
2 |
4 |
0.75 |
16 |
|
2 |
4 |
0.4 |
10 |
|
2 |
2 |
1 |
9 |
|
2 |
2 |
0.8 |
9 |
|
2 |
2 |
0.75 |
9 |
|
2 |
2 |
0.4 |
4 |
|
4 |
8 |
1 |
26 |
|
4 |
8 |
0.8 |
23 |
|
4 |
8 |
0.75 |
22 |
|
4 |
8 |
0.4 |
12 |
|
4 |
6 |
1 |
27 |
|
4 |
6 |
0.8 |
24 |
|
4 |
6 |
0.75 |
23 |
|
4 |
6 |
0.4 |
14 |
|
4 |
4 |
1 |
16 |
|
4 |
4 |
0.8 |
16 |
|
4 |
4 |
0.75 |
16 |
|
4 |
4 |
0.4 |
11 |
|
4 |
2 |
1 |
9 |
|
4 |
2 |
0.8 |
9 |
|
4 |
2 |
0.75 |
9 |
|
4 |
2 |
0.4 |
5 |
|
Note 1: MCS Index for maximum modulation format 2,4 and 6 is based on MCS index table 1 defined in clause 5.1.3.1 of TS 38.214 [12] Note 2: MCS Index for maximum modulation format 8 is based on MCS index table 2 defined in clause 5.1.3.1 of TS 38.214 [12] |
|||
5.5.1.3.1 Procedure for test parameter selection
Below test parameter selection procedure is from 38.101-4 [5] by replacing CA configuration with operating band, and bandwidth instead of bandwidth combination.
The test parameters are determined by the following procedure:
– Select one operating band among all supported operating bands and set of per band UE capabilities among all supported UE capabilities that provides the largest data rate [TS 38.306 [14, Section 4.1.2]].
– Set of per band UE capabilities includes channel bandwidth, subcarrier spacing, number of PDSCH MIMO layers, modulation format and scaling factor [TS 38.306 [14, Section 4.1.2]].
– When there are multiple sets of bandwidths and UE capabilities (channel bandwidth, subcarrier spacing, number of MIMO layer, modulation format, scaling factor) with same largest data rate, select one among sets with the smallest channel bandwidth.
– For each operating band, use Table 5.5.1.3-5 to determine MCS based on test parameters and indicated UE capabilities
Pasting relevant portion of max data rate equation from TS 38.306 [14] section 4.1
For NR, the approximate data rate for a given number of aggregated carriers in a band or band combination is computed as follows.
wherein
J is the number of aggregated component carriers in a band or band combination
Rmax = 948/1024
For the j-th CC,
is the maximum number of supported layers given by higher layer parameter maxNumberMIMO-LayersPDSCH for downlink and maximum of higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for uplink.
is the maximum supported modulation order given by higher layer parameter supportedModulationOrderDL for downlink and higher layer parameter supportedModulationOrderUL for uplink.
is the scaling factor given by higher layer parameter scalingFactor and can take the values 1, 0.8, 0.75, and 0.4.
is the numerology (as defined in TS 38.211 [6])
is the average OFDM symbol duration in a subframe for numerology 
, i.e. 
. Note that normal cyclic prefix is assumed.
is the maximum RB allocation in bandwidth 
with numerology 
, as defined in 5.3 TS 38.101-1 [2] and 5.3 TS 38.101-2 [3], where 
is the UE supported maximum bandwidth in the given band or band combination.
is the overhead and takes the following values
0.14, for frequency range FR1 for DL
0.18, for frequency range FR2 for DL
0.08, for frequency range FR1 for UL
0.10, for frequency range FR2 for UL
NOTE: Only one of the UL or SUL carriers (the one with the higher data rate) is counted for a cell operating SUL.
The approximate maximum data rate can be computed as the maximum of the approximate data rates computed using the above formula for each of the supported band or band combinations.
The normative reference for this requirement is TS 38.101-4 [5], clause 5.5.1.
5.5.1.4 Test description
5.5.1.4.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1 of TS 38.521-1.
Configurations of PDSCH and PDCCH before measurement are specified in Annex C.
Test Environment: Normal, as defined in TS 38.508-1 [6] clause 4.1.
Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [6] clause 5.2.2.
1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, in Figure A.3.1.7.1 for TE diagram (without fader and AWGN) and clause A.3.2.2 for UE diagram.
2. The parameter settings for the NR cell are initially set up according to Table 5.5.1.3-1 as appropriate.
3. Downlink signals for the NR cell are initially set up according to Annexes C.0, C.1, C.2, C.3.1, and uplink signals according to Annexes G.0, G.1, G.2, G.3.1 of TS 38.521-1 [7].
4. Propagation conditions for the NR cell are set according to Annex B.0.
5. Ensure the UE is in state RRC_CONNECTED with generic procedure parameters Connectivity NR with Connected without release On, Test Loop Function On with UE Test Loop Mode A with UL_PDCP_SDU_SIZE = 0 according to TS 38.508-1 [6] clause 4.5.4. Message content are defined in clause 5.5.1.4.3.
6. SS shall transmit UECapabilityEnquiry message.
7. The UE shall transmit UECapabilityInformation message.
8. Using the UE capabilities advertised in the UE-CapabilityRAT-Container of the type UE-NR-Capability, and the procedure outlined in 5.5.1.3.1 determine one set of parameters that would provide the largest data rate.
9. Setup up the NR cell using these parameters for the test.
10. Configure the TBsize, DL RMC, UL RMC, PDCP size from Annex A.3.2_1 and Annex A.2.2 for UL as appropriate.
5.5.1.4.2 Test procedure
1. SS configures T-reordering timer to be infinity.
2. SS sends a PDCP reestablishment via RRC Reconfiguration message requesting for PDCP Status Report.
3. SS sets the counters NDL_newtx NDL_retx to 0.
4. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs (max PDCP SDU size and minimum number of consecutive PDCP SDUs) to fill up the TB in accordance with Annex A.3.2_1. The SS ciphers the PDCP SDUs, concatenates the resultant PDCP PDUs to form an RLC PDU and then a MAC PDU. The SS transmits the MAC PDU. The SS increments then NDL_newtx by one
5. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.
6. Steps 5 to 6 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.
7. SS sends a PDCP reestablishment via RRC Reconfiguration message requesting for PDCP Status Report.
8. The SS calculates the TB success rate as A = 100%* NDL_correct_rx / (NDL_newtx + NDL_retx).
10. SS computes the PDCP SDU loss by looking into the FMC and Bitmap field in the PDCP Status Report. PDCP SDU loss B = COUNT reported in the Bitmap field of PDCP Stata Report.
11. The UE passes the test if A ≥ 85% TB success rates and B = 0.
Note 1: In case of RLC PDU retransmission, the number of new required PDCP SDUs is as many as to fill the rest of TB.
5.5.1.4.3 Message contents
Message contents are according to TS 38.508-1 [6] clause 5.4.2 with the following exceptions
Table 5.5.1.4.3-0: CLOSE UE TEST LOOP (in the preamble)
|
Derivation Path: 38.509 clause 6.3.1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
1 1 1 1 |
|||
|
Skip indicator |
0 0 0 0 |
|||
|
Message type |
1 0 0 0 0 0 0 0 |
|||
|
UE test loop mode |
0 0 0 0 0 0 0 0 |
UE test loop mode A |
||
|
UE test loop mode A LB setup |
||||
|
Length of UE test loop mode A LB setup list in bytes |
0 0 0 0 0 0 1 1 |
Length of one LB setup DRB (3 bytes) |
||
|
LB setup DRB |
0 0 0 0 0 0 0 0, 0 0 0 0 0 0 0 0, 0 0 Q5 Q4 Q3 Q2 Q1 Q0 |
UL PDCP SDU size = 0 Q5 = 1 (for NR Data Radio Bearers) Q4..Q0 = Data Radio Bearer identity number -1 for the radio bearer. See 38.509 clause 6.3.1 |
||
|
UE test loop mode B LB setup |
Not present |
|||
Table 5.5.1.4.3-1 to -6: Void
Table 5.5.1.4.3-7: RadioBearerConfig
|
Derivation Path: TS 38.508-1 [6], clause 4.6.3-132 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE { |
1 entry |
DRB1 |
|
|
cnAssociation CHOICE { |
|||
|
sdap-Config |
SDAP-Config |
||
|
} |
|||
|
drb-Identity |
DRB-Identity using condition DRB1 |
||
|
reestablishPDCP |
true |
DRB1 AND Re-establish_PDCP |
|
|
pdcp-Config |
PDCP-Config |
||
|
} |
|||
Table 5.5.1.4.3-8: PDCP-Config
|
Derivation Path: TS 38.508-1 [6], Table 4.6.3-99 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDCP-Config ::= SEQUENCE { |
|||
|
drb SEQUENCE { |
|||
|
discardTimer |
infinity |
||
|
pdcp-SN-Size-UL |
len18bits |
||
|
pdcp-SN-Size-DL |
len18bits |
||
|
headerCompression CHOICE { |
|||
|
notUsed |
Null |
||
|
} |
|||
|
integrityProtection |
Not present |
||
|
statusReportRequired |
true |
||
|
outOfOrderDelivery |
Not present |
||
|
} |
|||
|
t-Reordering |
Not present |
||
|
} |
|||
5.5.1.5 Test requirement
The PDCP SDU success rate of greater than 85% shall be sustained during at least 300 frames.
5.5A.1 FR1 Sustained downlink data rate performance for carrier aggregation
5.5A.1.1 FR1 SDR performance for CA (2DLCA)
5.5A.1.1.1 Test Purpose
The purpose of the test is to verify that the Layer 1 and Layer 2 correctly process in a sustained manner the received packets corresponding to the maximum data rate indicated by UE capabilities. The sustained downlink data rate shall be verified in terms of the success rate of delivered PDCP SDU(s) by Layer 2. The test case below specifies the RF conditions and the required success rate of delivered TB by Layer 1 to meet the sustained data rate requirement.
5.5A.1.1.2 Test applicability
This test applies to all types of NR UE release 15 and forward that supports 2DL CA
5.5A.1.1.3 Minimum conformance requirements
The Sustained Data Rate (SDR) requirements in this clause are applicable to the FR1 CA.
The TB success rate shall be higher than 85% when PDSCH is scheduled with MCS defined for the selected CA bandwidth combination and with the downlink physical channel setup according to Annex C.2.1.
The TB success rate is defined as 100%*NDL_correct_rx / (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks.
The common test parameters are specified in Table 5.5A.1.1.3-1. The parameters specified in Table 5.5A.1.1.3-2 are applicable for tests on FDD CCs and parameters specified in Table 5.5A.1.1.3-3 are applicable for tests on TDD CCs.
Unless otherwise stated, no user data is scheduled on slot #0, 10 and 11 within 20 ms for SCS 15 kHz.
Unless otherwise stated, no user data is scheduled on slot #0, 20 and 21 within 20 ms for SCS 30 kHz.
Table 5.5A.1.1.3-1: Common test parameters for FDD and TDD component carriers
|
Parameter |
Unit |
Value |
||
|
PDSCH transmission scheme |
Transmission scheme 1 |
|||
|
EPRE ratio of PTRS to PDSCH |
dB |
N/A |
||
|
Channel bandwidth |
MHz |
Channel bandwidth from selected CA bandwidth combination |
||
|
Common serving cell parameters |
Physical Cell ID |
0 |
||
|
SSB position in burst |
First SSB in Slot #0 |
|||
|
SSB periodicity |
ms |
20 |
||
|
First DMRS position for Type A PDSCH mapping |
2 |
|||
|
Cross carrier scheduling |
Not configured |
|||
|
Active DL BWP index |
1 |
|||
|
Actual carrier configuration |
Offset between Point A and the lowest usable subcarrier on this carrier (Note 2) |
RBs |
0 |
|
|
Subcarrier spacing |
kHz |
15 or 30 |
||
|
DL BWP configuration #1 |
RB offset |
RBs |
0 |
|
|
Number of contiguous PRB |
Maximum transmission bandwidth configuration as specified in clause 5.3.2 of TS 38.101-1 [2] for tested channel bandwidth and subcarrier spacing |
|||
|
Subcarrier spacing |
kHz |
15 or 30 |
||
|
Cyclic prefix |
Normal |
|||
|
PDCCH configuration |
Slots for PDCCH monitoring |
Each slot |
||
|
Symbols with PDCCH |
Symbols #0 |
|||
|
Number of PRBs in CORESET |
Table 5.5A-4 |
|||
|
Number of PDCCH candidates and aggregation levels |
1/AL 1 for 30 kHz / 5 MHz 1/AL4 for 15 kHz / 5 MHz, 30 kHz / 10 MHz and 30 kHz / 15 MHz 1/AL 8 for other combinations |
|||
|
CCE-to-REG mapping type |
Non-interleaved |
|||
|
DCI format |
1_1 |
|||
|
TCI State |
TCI state #1 |
|||
|
PDCCH & PDCCH DMRS Precoding configuration |
For 2Tx: Single Panel Type I, Random precoder chosen from precoder index 0 and 2, selection updated per slot For 4Tx: Single Panel Type I, Random precoder chosen from precoders with i_1,1 in {1,2,3,5,6,7} and i_2 in {0,2}, selection updated per slot |
|||
|
PDSCH configuration |
Mapping type |
Type A |
||
|
k0 |
0 |
|||
|
PDSCH aggregation factor |
1 |
|||
|
PRB bundling type |
Static |
|||
|
PRB bundling size |
wideband |
|||
|
Resource allocation type |
Type 0 |
|||
|
VRB-to-PRB mapping type |
Non-interleaved |
|||
|
VRB-to-PRB mapping interleaver bundle size |
N/A |
|||
|
PDSCH DMRS configuration |
DMRS Type |
Type 1 |
||
|
Number of additional DMRS |
1 |
|||
|
Length |
1 |
|||
|
Antenna ports indexes |
{1000} for 1 Layer CCs {1000 – 1003} for 4 Layers CCs |
|||
|
Number of PDSCH DMRS CDM group(s) without data |
1 for 1 layer and 2 layers CCs 2 for 4 Layers CCs |
|||
|
PTRS configuration |
PTRS is not configured |
|||
|
CSI-RS for tracking |
Subcarrier indexes in the PRB used for CSI-RS |
k0 = 3 for CSI-RS resource 1,2,3,4 |
||
|
OFDM symbols in the PRB used for CSI-RS |
l0 = 6 for CSI-RS resource 1 and 3 l0 = 10 for CSI-RS resource 2 and 4 |
|||
|
Number of CSI-RS ports (X) |
1 for CSI-RS resource 1,2,3,4 |
|||
|
CDM Type |
‘No CDM’ for CSI-RS resource 1,2,3,4 |
|||
|
Density (ρ) |
3 for CSI-RS resource 1,2,3,4 |
|||
|
CSI-RS periodicity |
Slots |
15 kHz SCS: 20 for CSI-RS resource 1,2,3,4 30 kHz SCS: 40 for CSI-RS resource 1,2,3,4 |
||
|
CSI-RS offset |
Slots |
15 kHz SCS: 10 for CSI-RS resource 1 and 2 11 for CSI-RS resource 3 and 4 30 kHz SCS: 20 for CSI-RS resource 1 and 2 21 for CSI-RS resource 3 and 4 |
||
|
Frequency Occupation |
Start PRB 0 Number of PRB = ceil(BWP size /4)*4 |
|||
|
QCL info |
TCI state #0 |
|||
|
NZP CSI-RS for CSI acquisition |
Subcarrier indexes in the PRB used for CSI-RS |
k0 = 4 |
||
|
OFDM symbols in the PRB used for CSI-RS |
l0 = 12 |
|||
|
Number of CSI-RS ports (X) |
Same as number of transmit antenna |
|||
|
CDM Type |
‘FD-CDM2’ |
|||
|
Density (ρ) |
1 |
|||
|
CSI-RS periodicity |
15 kHz SCS: 20 30 kHz SCS: 40 |
|||
|
CSI-RS offset |
0 |
|||
|
Frequency Occupation |
Start PRB 0 Number of PRB = ceil(BWP size /4)*4 |
|||
|
QCL info |
TCI state #1 |
|||
|
ZP CSI-RS for CSI acquisition |
Subcarrier indexes in the PRB used for CSI-RS |
k0 = 0 |
||
|
OFDM symbols in the PRB used for CSI-RS |
l0 = 12 |
|||
|
Number of CSI-RS ports (X) |
4 |
|||
|
CDM Type |
‘FD-CDM2’ |
|||
|
Density (ρ) |
1 |
|||
|
CSI-RS periodicity |
15 kHz SCS: 20 30 kHz SCS: 40 |
|||
|
CSI-RS offset |
0 |
|||
|
Frequency Occupation |
Start PRB 0 Number of PRB = ceil(BWP size/4)*4 |
|||
|
TCI state #0 |
Type 1 QCL information |
SSB index |
SSB #0 |
|
|
QCL Type |
Type C |
|||
|
Type 2 QCL information |
SSB index |
N/A |
||
|
QCL Type |
N/A |
|||
|
TCI state #1 |
Type 1 QCL information |
CSI-RS resource |
CSI-RS resource 1 from ‘CSI-RS for tracking’ configuration |
|
|
QCL Type |
Type A |
|||
|
Type 2 QCL information |
CSI-RS resource |
N/A |
||
|
QCL Type |
N/A |
|||
|
Maximum number of code block groups for ACK/NACK feedback |
1 |
|||
|
Maximum number of HARQ transmission |
4 |
|||
|
HARQ ACK/NACK bundling |
Multiplexed |
|||
|
Redundancy version coding sequence |
{0,2,3,1} |
|||
|
PDSCH & PDSCH DMRS Precoding configuration |
Single Panel Type I, Random precoder selection updated per slot, with equal probability of each applicable i1, i2 combination with PRB bundling granularity |
|||
|
Symbols for all unused REs |
OP.1 FDD as defined in Annex A.5.1.1 OP.1 TDD as defined in Annex A.5.2.1 |
|||
|
Propagation condition |
Static propagation condition No external noise sources are applied |
|||
|
Antenna configuration |
1 layer CCs |
1×2 or 1×4 |
||
|
2 layers CCs |
2×2 or 2×4 |
|||
|
4 layers CCs |
4×4 |
|||
|
Physical signals, channels mapping and precoding |
As specified in Annex B.4.1 |
|||
|
Note 1: UE assumes that the TCI state for the PDSCH is identical to the TCI state applied for the PDCCH transmission Note 2: Point A coincides with minimum guard band as specified in Table 5.3.3-1 from TS 38.101-1 [2] for tested channel bandwidth and subcarrier spacing |
||||
Table 5.5A.1.1.3-2: Additional test parameters for FDD CC
|
Parameter |
Unit |
Value |
|
|
Duplex mode |
FDD |
||
|
PDSCH configuration |
Starting symbol (S) |
1 |
|
|
Length (L) |
13 |
||
|
Number of HARQ Processes |
4 |
||
|
K1 value |
2 |
||
Table 5.5A.1.1.3-3: Additional test parameters for TDD CC
|
Parameter |
Unit |
Value |
|
|
Duplex mode |
TDD |
||
|
PDSCH configuration |
Starting symbol (S) |
1 |
|
|
Length (L) |
13 |
||
|
Number of HARQ Processes |
8 |
||
|
K1 value |
Specific to each UL-DL pattern |
||
|
TDD UL-DL pattern |
15 kHz SCS: FR1.15-1 30 kHz SCS: FR1.30-1 |
||
|
Note 1: PDSCH is scheduled only on full DL slots |
|||
Table 5.5A.1.1.3-4: Number of PRBs in CORESET
|
SCS (kHz) |
5 MHz |
10 MHz |
15 MHz |
20 MHz |
25 MHz |
30 MHz |
35 MHz |
40 MHz |
45 MHz |
50 MHz |
60 MHz |
80 MHz |
100 MHz |
|
15 |
24 |
48 |
78 |
102 |
132 |
156 |
186 |
216 |
240 |
270 |
N/A |
N/A |
N/A |
|
30 |
6 |
24 |
36 |
48 |
60 |
78 |
90 |
102 |
114 |
132 |
162 |
216 |
270 |
Table 5.5A.1.1.3-5: MCS indexes for indicated UE capabilities
|
Maximum number of PDSCH MIMO layers |
Maximum modulation format |
Scaling factor |
MCS |
|
1 |
8 |
1 |
26 |
|
1 |
8 |
0.8 |
21 |
|
1 |
8 |
0.75 |
20 |
|
1 |
8 |
0.4 |
11 |
|
1 |
6 |
1 |
27 |
|
1 |
6 |
0.8 |
23 |
|
1 |
6 |
0.75 |
22 |
|
1 |
6 |
0.4 |
14 |
|
1 |
4 |
1 |
16 |
|
1 |
4 |
0.8 |
16 |
|
1 |
4 |
0.75 |
16 |
|
1 |
4 |
0.4 |
10 |
|
1 |
2 |
1 |
9 |
|
1 |
2 |
0.8 |
9 |
|
1 |
2 |
0.75 |
9 |
|
1 |
2 |
0.4 |
4 |
|
2 |
8 |
1 |
26 |
|
2 |
8 |
0.8 |
21 |
|
2 |
8 |
0.75 |
20 |
|
2 |
8 |
0.4 |
11 |
|
2 |
6 |
1 |
27 |
|
2 |
6 |
0.8 |
23 |
|
2 |
6 |
0.75 |
22 |
|
2 |
6 |
0.4 |
14 |
|
2 |
4 |
1 |
16 |
|
2 |
4 |
0.8 |
16 |
|
2 |
4 |
0.75 |
16 |
|
2 |
4 |
0.4 |
10 |
|
2 |
2 |
1 |
9 |
|
2 |
2 |
0.8 |
9 |
|
2 |
2 |
0.75 |
9 |
|
2 |
2 |
0.4 |
4 |
|
4 |
8 |
1 |
26 |
|
4 |
8 |
0.8 |
23 |
|
4 |
8 |
0.75 |
22 |
|
4 |
8 |
0.4 |
12 |
|
4 |
6 |
1 |
27 |
|
4 |
6 |
0.8 |
24 |
|
4 |
6 |
0.75 |
23 |
|
4 |
6 |
0.4 |
14 |
|
4 |
4 |
1 |
16 |
|
4 |
4 |
0.8 |
16 |
|
4 |
4 |
0.75 |
16 |
|
4 |
4 |
0.4 |
11 |
|
4 |
2 |
1 |
9 |
|
4 |
2 |
0.8 |
9 |
|
4 |
2 |
0.75 |
9 |
|
4 |
2 |
0.4 |
5 |
|
Note 1: MCS Index for maximum modulation format 2,4 and 6 is based on MCS index Table 1 defined in clause 5.1.3.1 of TS 38.214 [12] Note 2: MCS Index for maximum modulation format 8 is based on MCS index Table 2 defined in clause 5.1.3.1 of TS 38.214 [12] |
|||
5.5A.1.1.3.1 Procedure for test parameter selection
The test parameters are determined by the following procedure:
– Select one CA bandwidth combination among all supported CA configurations and set of per component carrier (CC) UE capabilities among all supported UE capabilities that provides the largest data rate in accordance with clause 4.1.2 of TS 38.306 [14].
– Set of per CC UE capabilities includes channel bandwidth, subcarrier spacing, number of PDSCH MIMO layers, modulation format and scaling factor in accordance with clause 4.1.2 of TS 38.306 [14].
– When there are multiple sets of CA bandwidth combinations and UE capabilities (channel bandwidth, subcarrier spacing, number of MIMO layer, modulation format, scaling factor) with same largest data rate, select one among sets with the smallest aggregated channel bandwidth.
– For each CC in CA bandwidth combination, use Table 5.5A.1.1.3-5 to determine MCS based on test parameters and indicated UE capabilities.
The normative reference for this requirement is TS 38.101-4 [5], clause 5.5A.1.
5.5A.1.1.4 Test description
5.5A.1.1.4.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
The initial test configurations consist of environmental conditions, test frequencies, test channel bandwidths and sub-carrier spacing based on NR operating bands specified in Table 5.3.5-1 of TS 38.521-1.
Configurations of PDSCH and PDCCH before measurement are specified in Annex C.
Test Environment: Normal, as defined in TS 38.508-1 [6] clause 5.2.2.
Frequencies to be tested: Mid Range, as defined in TS 38.508-1 [6] clause 4.3.1.1.
1. Connect the SS to the UE antenna connectors as shown in TS 38.508-1 [6] Annex A, in Figure A.3.1.7.2A, A.3.1.7.6, and A.3.1.7.7 for TE diagram (without fader and AWGN) for 2Rx and 4Rx CC respectively and clause A.3.2.6 for UE diagram.
2. The parameter settings for the NR cell are initially set up according to Table 5.5.1.3-1 as appropriate.
3. Downlink signals for the NR cell are initially set up according to Annexes C.0, C.1, C.2 and uplink signals according to Annexes G.0, G.1, G.2, G.3.1 of TS 38.521-1 [7].
4. Propagation conditions for the NR cell are set according to Annex B.1.
5. Ensure the UE is in state RRC_CONNECTED with generic procedure parameters Connectivity NR with Connected without release On, Test Loop Function On with UE Test Loop Mode A with UL_PDCP_SDU_SIZE = 0 according to TS 38.508-1 [6] clause 4.5.4. Message content are defined in clause 5.5 A.1.1.4.3.
6. Configure SCC according to Annex C.0, C.1 and C.2 for all downlink physical channels.
7. The SS shall configure SCC as per TS 38.508-1 [6] clause 5.5.1.
8. SS activates SCC by sending the activation MAC-CE (Refer TS 38.321 [24], clauses 5.9, 6.1.3.10). Wait for at least 1 second (Refer TS 38.133[25], clause9.3).
9. SS shall transmit UECapabilityEnquiry message.
10. The UE shall transmit UECapabilityInformation message.
11. Using the UE capabilities advertised in the UE-CapabilityRAT-Container of the type UE-NR-Capability, and the procedure outlined in 5.5A.1.1.3.1 determine one set of parameters that would provide the largest data rate.
12. Setup up the NR cells using these parameters for the test.
13. Configure the TBsize, DL RMC, UL RMC, PDCP size from Annex A.3.2_1 and Annex A.2.2 for UL as appropriate.
5.5A.1.1.4.2 Test procedure
1. SS configures T-reordering timer to be infinity.
2. SS sends a PDCP reestablishment via RRC Reconfiguration message requesting for PDCP Status Report.
3. SS sets the counters NDL_newtx NDL_retx to 0.
4. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs (max PDCP SDU size and minimum number of consecutive PDCP SDUs) to fill up the TB on both PCC and SCC in accordance with Annex A.3.2_1. The SS ciphers the PDCP SDUs, concatenates the resultant PDCP PDUs to form an RLC PDU and then a MAC PDU. The SS transmits the MAC PDU. The SS increments then NDL_newtx by one
5. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.
6. Steps 5 to 6 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.
7. SS sends a PDCP reestablishment via RRC Reconfiguration message requesting for PDCP Status Report.
8. The SS calculates the TB success rate as A = 100%* NDL_correct_rx / (NDL_newtx + NDL_retx).
9. SS computes the PDCP SDU loss by looking into the FMC and Bitmap field in the PDCP Status Report. PDCP SDU loss B = COUNT reported in the Bitmap field of PDCP Stata Report.
10. The UE passes the test if A ≥ 85% TB success rate on both PCC and SCC and B = 0.
Note 1: In case of RLC PDU retransmission, the number of new required PDCP SDUs is as many as to fill the rest of TB.
5.5A.1.1.4.3 Message contents
Message contents are according to TS 38.508-1 [6] clause 5.4.2 with the following exceptions:
Table 5.5A.1.1.4.3-1: CLOSE UE TEST LOOP (in the preamble)
|
Derivation Path: TS 38.509 [9] clause 6.3.1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
1 1 1 1 |
|||
|
Skip indicator |
0 0 0 0 |
|||
|
Message type |
1 0 0 0 0 0 0 0 |
|||
|
UE test loop mode |
0 0 0 0 0 0 0 0 |
UE test loop mode A |
||
|
UE test loop mode A LB setup |
||||
|
Length of UE test loop mode A LB setup list in bytes |
0 0 0 0 0 0 1 1 |
Length of one LB setup DRB (3 bytes) |
||
|
LB setup DRB |
0 0 0 0 0 0 0 0, 0 0 0 0 0 0 0 0, 0 0 Q5 Q4 Q3 Q2 Q1 Q0 |
UL PDCP SDU size = 0 Q5 = 1 (for NR Data Radio Bearers) Q4..Q0 = Data Radio Bearer identity number -1 for the radio bearer. See 38.509 clause 6.3.1 |
||
|
UE test loop mode B LB setup |
Not present |
|||
Table 5.5A.1.1.4.3-2: RadioBearerConfig
|
Derivation Path: TS 38.508-1 [6], clause 4.6.3-132 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioBearerConfig ::= SEQUENCE { |
|||
|
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE { |
1 entry |
DRB1 |
|
|
cnAssociation CHOICE { |
|||
|
sdap-Config |
SDAP-Config |
||
|
} |
|||
|
drb-Identity |
DRB-Identity using condition DRB1 |
||
|
reestablishPDCP |
true |
DRB1 AND Re-establish_PDCP |
|
|
pdcp-Config |
PDCP-Config |
||
|
} |
|||
Table 5.5A.1.1.4.3-3: PDCP-Config
|
Derivation Path: TS 38.508-1 [6], Table 4.6.3-99 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PDCP-Config ::= SEQUENCE { |
|||
|
drb SEQUENCE { |
|||
|
discardTimer |
infinity |
||
|
pdcp-SN-Size-UL |
len18bits |
||
|
pdcp-SN-Size-DL |
len18bits |
||
|
headerCompression CHOICE { |
|||
|
notUsed |
Null |
||
|
} |
|||
|
integrityProtection |
Not present |
||
|
statusReportRequired |
true |
||
|
outOfOrderDelivery |
Not present |
||
|
} |
|||
|
t-Reordering |
Not present |
||
|
} |
|||
5.5A.1.1.5 Test requirement
The TB success rate of greater than 85% with no PDCP SDU loss shall be sustained during at least 300 frames on each CC.