8.7.10 TDD sustained data rate performance (4 layer MIMO)
36.521-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Part 1: Conformance testingRadio transmission and receptionRelease 17TSUser Equipment (UE) conformance specification
8.7.10.1 Minimum conformance requirements
The parameters specified in Table 8.7.10.1-1 are valid for all TDD tests unless otherwise stated.
Table 8.7.10.1-1: Common Test Parameters (TDD)
|
Parameter |
Unit |
Value |
|||
|
Transmission mode |
3 |
||||
|
Special subframe configuration (Note 1) |
4 |
||||
|
Cyclic prefix |
Normal |
||||
|
Cell ID |
0 |
||||
|
Inter-TTI Distance |
1 |
||||
|
Number of HARQ processes per component carrier |
Processes |
8 |
|||
|
Maximum number of HARQ transmission |
4 |
||||
|
Redundancy version coding sequence |
{0,0,1,2} for 64QAM and 256QAM |
||||
|
Number of OFDM symbols for PDCCH per component carrier |
OFDM symbols |
1 |
|||
|
Cross carrier scheduling |
Not configured |
||||
|
Propagation condition |
Static propagation condition No external noise sources are applied |
||||
|
at antenna port
|
dBm/15kHz |
-85 |
|||
|
Symbols for unused PRBs |
OP.1 TDD |
||||
|
Antenna configuration |
2 layer CC |
2×2 or 2×4 |
|||
|
4 layer CC |
4×4 |
||||
|
Codebook subset restriction |
2 layer CC |
10 |
|||
|
4 layer CC |
1000 |
||||
|
Downlink power allocation |
2 layer CC |
|
|||
|
4 layer CC |
|
||||
|
Symbols for unused PRBs |
OP.1 TDD |
||||
= -3dB, 
= -3dB, σ = 0dB
= -6dB, 
= -6dB, σ = 3dBFor UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.10.1-2 with the downlink physical channel setup according to Annex C.3.2.
For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.10.1-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable.
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 TB success rate shall be sustained during at least 300 frames.
Table 8.7.10.1-2: Per-CC FRC for SDR test(TDD 64QAM)
|
MIMO layer |
Bandwidth |
Reference channel |
|
2 layer |
10 |
R.31-6 TDD |
|
15 |
R.31-5 TDD |
|
|
20 |
R.31-4 TDD |
|
|
4 layer |
10 |
R.31-7 TDD |
|
15 |
R.31-8 TDD |
|
|
20 |
R.31-9 TDD |
Table 8.7.10.1-3: Per-CC FRC for SDR test (TDD 256QAM)
|
MIMO layer |
Bandwidth |
Reference channel |
|
2 layer |
10 |
R.68-2 TDD |
|
15 |
R.68-1 TDD |
|
|
20 |
R.68 TDD |
|
|
4 layer |
10 |
R.68-5 TDD |
|
15 |
R.68-6 TDD |
|
|
20 |
R.68-7 TDD |
CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure.
– Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as
where 
is number of CCs, 
and 
is MIMO layer and bandwidth of CC 
.
– When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs.
– The procedure applies also for single carrier using operating band instead of CA configuration, and bandwidth instead of bandwidth combination.
The normative reference for this requirement is TS 36.101 [2] clause 8.7.10.
8.7.10.2 TDD sustained data rate performance for 4 layer MIMO (single carrier)
8.7.10.2.1 Test purpose
Same test purpose as 8.7.1.1.
8.7.10.2.2 Test applicability
This test applies to E-UTRA TDD release 10 and forward UE of category 6 and 7 and DL category 13 that supports 4 Rx antenna ports and 4-layer spatial multiplexing for PDSCH transmission mode 3 in any TDD RF band.
8.7.10.2.3 Minimum conformance requirements
The minimum conformance requirements are defined in clause 8.7.10.1.
8.7.10.2.4 Test description
8.7.10.2.4.1 Initial conditions
For UE not supporting 256QAM, the requirements are specified in Table 8.7.10.1-2, with the addition of the parameters in Table 8.7.10.2.4.1-1 and Table 8.7.10.2.4.1-3. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.2.4.1-2.
For UE supporting 256QAM, the requirements are specified in Table 8.7.10.1-3, with the addition of the parameters in Table 8.7.10.2.4.1-1 and Table 8.7.10.2.4.1-5. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.2.4.1-4.
Table 8.7.10.2.4.1-1: Test parameters for sustained downlink data rate (TDD single carrier)
|
Test |
Bandwidth (MHz) |
MIMO layer |
Antenna configuration |
Equivalent aggr. BW (MHz) |
|
1 |
20 |
4 layer |
4×4 |
80 |
Table 8.7.10.2.4.1-2: Test points for sustained data rate (FRC 64QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 6, 7 |
Cat. 9, 10 |
Cat. 11, 12 |
DL Cat. 13 |
||
|
Bagg (MHz) |
BW (MHz) |
MIMO layer |
DL Cat. 9, 10 |
DL Cat. 11, 12 |
||
|
80 |
20 |
4 |
1 |
– |
– |
– |
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||
Table 8.7.10.2.4.1-3: Further test parameters per test (FRC 64QAM)
|
Test |
Bandwidth and number of Rx antennas |
DL Measurement channel |
UL Measurement channel |
TBsize per Codeword per CC |
Number of PDCP SDU per Codeword |
PDCP SDU size [Octets] Calculation (Note 1) |
PDCP SDU size [Octets] |
|
1 |
20MHz 4Rx |
R.31-9 TDD |
R.1-4 TDD |
128496 (Note 3) |
11 |
FLOOR((TBsize – 376)/88) |
1455 |
|
Note 1: Transport block size under test according to applicable Fixed Reference Channel for sustained data-rate test in annex A.3.9. In case of varying TBS across SFs of the RMC, only the maximum TBS is used for PDCP SDU size calculation. Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12). Note 3: 124464 bits for sub-frame 5. |
|||||||
Table 8.7.10.2.4.1-4: Test points for sustained data rate (FRC 256QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW (MHz) |
MIMO layer |
DL Cat. 11, 12 |
|||||
|
80 |
20 |
4 |
– |
1 |
– |
– |
– |
– |
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
Table 8.7.10.2.4.1-5: Further test parameters per test (FRC 256QAM)
|
Test |
Bandwidth and number of Rx antennas |
DL Measurement channel |
UL Measurement channel |
TBsize per Codeword per CC |
Number of PDCP SDU per Codeword |
PDCP SDU size [Octets] Calculation (Note 1) |
PDCP SDU size [Octets] |
|
1 |
20MHz 4Rx |
R.68-7 TDD |
R.1-4 TDD |
169544 (Note 3) |
15 |
FLOOR((TBsize – 488)/120) |
1408 |
|
Note 1: Transport block size under test according to applicable Fixed Reference Channel for sustained data-rate test in annex A.3.9. In case of varying TBS across SFs of the RMC, only the maximum TBS is used for PDCP SDU size calculation. Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12). Note 3: 161760 bits for sub-frame 5. |
|||||||
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.
Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2.
Test Environment: Normal as defined in TS 36.508 [7] clause 4.1.
Frequencies to be tested: Mid Range as defined in TS 36.508 [7] clause 4.3.1.1.
Channel Bandwidths to be tested: according to Table 8.7.10.2.4.1-1 depending on the UE category according to Table 8.7.10.2.4.1-2 for UE not supporting 256QAM or Table 8.7.10.2.4.1-4 for UE supporting 256QAM.
1. Connect the SS to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure A.74 (without using faders and AWGN generators).
2. For UE not supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.2.4.1-1 and Table 8.7.10.2.4.1-3 depending on the UE category according to Table 8.7.10.2.4.1-2. For UE supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.2.4.1-1 and Table 8.7.10.2.4.1-5 depending on the UE category according to Table 8.7.10.2.4.1-4.
3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.
4. Propagation conditions are set according to Annex B.0.
5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 5.2A.3. Message contents are defined in clause 8.7.9.2.4.3.
8.7.9.2.4.2 Test procedure
1. Propagation conditions are set according to Annex B.1 (No external noise sources are applied).
2. For UE not supporting 256QAM the SS looks up TBsize in Table 8.7.10.2.4.1-3 for the tests to be performed depending on the UE category according to Table 8.7.10.2.4.1-2. For UE supporting 256QAM the SS looks up TBsize in Table 8.7.10.2.4.1-5 for the tests to be performed depending on the UE category according to Table 8.7.10.2.4.1-4.
3. The SS sets the counters NDL_newtx, NDL_retx, NUL_PDCP and NDL_PDCP to 0.
4. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.10.2.4.1-3 (Note 1) for UE not supporting 256QAM or in accordance with Table 8.7.10.2.4.1-5 (Note 1) for UE supporting 256QAM. 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 and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.
5. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.
6. Steps 4 to 5 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. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one
8. The SS calculates the TB success rate as A = 100%*NDL_newtx / (NDL_newtx + NDL_retx). Measurements are not based on UE feedback but on SS counters instead (NDL_newtx and NDL_retx) in order to validate HARQ feedback received from the UE.
9. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP
10. The UE passes the test if A > 85% 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.
8.7.10.2.4.3 Message contents
Table 8.7.10.2.4.3-1: CLOSE UE TEST LOOP (in the preamble)
|
Derivation Path: 36.509 clause 6.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 1 0 1 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0 |
UL PDCP SDU size = 40 bits (5 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1 |
||
|
UE test loop mode B LB setup |
Not present |
|||
Table 8.7.9.4.2.3-2: SecurityModeCommand (in the preamble)
|
Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
SecurityModeCommand ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE{ |
||||
|
securityModeCommand-r8 SEQUENCE { |
||||
|
securityConfiguration SEQUENCE { |
||||
|
cipheringAlgorithm |
eea2 |
|||
|
nextHopChainingCount |
Not present |
|||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.7.10.2.4.3-3: RRCConnectionReconfiguration
|
Derivation Path: 36.331 clause 6.2.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
lateNonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
antennaInfoDedicatedPCell-v10i0 SEQUENCE { |
||||
|
maxLayersMIMO-r10 |
fourLayers |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.7.10.2.4.3-4: PhysicalConfigDedicated-DEFAULT
|
Derivation Path: 36.508 clause 4.8.2.1.6-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
|||
|
antennaInfo CHOICE { |
|||
|
explicitValue ::= SEQUENCE { |
|||
|
transmissionMode |
tm3 |
||
|
codebookSubsetRestriction CHOICE { |
|||
|
n4TxAntenna-tm3 |
1000 |
||
|
} |
|||
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
Release |
NULL |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
8.7.10.2.5 Test requirement
The pass fail decision is as specified in the test procedure in clause 8.7.10.2.4.2.
There are no parameters in the test setup or measurement process whose variation impacts the results so there are no applicable test tolerances for this test.
8.7.10.3 TDD sustained data rate performance for 4 layer MIMO (2DL CA)
Editor’s note: Simplification of test point tables, to reduce future maintenance, needs further investigation.
8.7.10.3.1 Test purpose
Same test purpose as 8.7.1.1.
8.7.10.3.2 Test applicability
This test applies to E-UTRA TDD release 10 and forward UE of category 9, 10, 11 and 12 and DL category 9, 10, 11, 12 and 15 that supports inter-band OR intra‑band contiguous DL CA and supports 4 Rx antenna ports and 4-layer spatial multiplexing for PDSCH transmission mode 3 in any TDD RF band of the DL CA configuration.
This test also applies to E-UTRA TDD release 11 and forward UE of category 9, 10, 11 and 12 and DL category 9, 10, 11, 12 and 15 that supports intra band non-contiguous DL CA and supports 4 Rx antenna ports and 4-layer spatial multiplexing for PDSCH transmission mode 3 in any TDD RF band of the DL CA configuration.
8.7.10.3.3 Minimum conformance requirements
The minimum conformance requirements are defined in clause 8.7.10.1.
8.7.10.3.4 Test description
8.7.10.3.4.1 Initial conditions
For UE not supporting 256QAM, the requirements are specified in Table 8.7.10.1-2, with the addition of the parameters in Table 8.7.10.3.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.3.4.1-2.
For UE supporting 256QAM, the requirements are specified in Table 8.7.10.1-3, with the addition of the parameters in Table 8.7.10.3.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.3.4.1-3.
Table 8.7.10.3.4.1-1: Test parameters for sustained downlink data rate (TDD 2DL CA)
|
Test |
Bandwidth (MHz) |
MIMO layer |
Antenna configuration |
Equivalent aggr. BW (MHz) |
PDCP SDU size [Octets] 64QAM |
PDCP SDU size [Octets] 256QAM |
|
1 |
2×20 |
4 layer |
4×4 |
160 |
1455 |
1408 |
|
2 |
15+20 |
4 layer |
4×4 |
140 |
1455 |
1408 |
|
3 |
20 |
2 layer |
2×2 |
120 |
1341 |
1355 |
|
20 |
4 layer |
4×4 |
Editor’s note: Tests in Table 8.7.10.3.4.1-1 are covering maximum aggregated bandwidth for each Bandwidth combination set with 2DL CA which are defined in Table 5.4.2A.1-1, Table 5.4.2A.1-2 or Table 5.4.2A.1-3.
Table 8.7.10.3.4.1-2: Test points for sustained data rate (FRC 64QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 9, 10 |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
MIMO layer |
DL Cat. 9, 10 |
DL Cat. 11, 12 |
|||||
|
160 |
2×20 |
4 |
2 |
1 |
– |
– |
– |
– |
– |
|
140 |
15+20 |
4 |
2 |
2 |
– |
– |
– |
– |
– |
|
120 |
20 |
2 |
3 |
3 |
– |
– |
– |
– |
– |
|
20 |
4 |
||||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
|||||||||
Table 8.7.10.3.4.1-3: Test points for sustained data rate (FRC 256QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
MIMO layer |
DL Cat. 11, 12 |
|||||
|
160 |
2×20 |
4 |
2 |
– |
1 |
– |
– |
– |
|
140 |
15+20 |
4 |
2 |
– |
2 |
– |
– |
– |
|
120 |
20 |
2 |
3 |
– |
3 |
– |
– |
– |
|
20 |
4 |
|||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
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.
Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2.
Test Environment: Normal as defined in TS 36.508 [7] clause 4.1.
Frequencies to be tested: Maximum WGap for Intra-band non-contiguous CA, otherwise Mid Range as defined in TS 36.508 [7] clause 4.3.1.1.
Channel Bandwidths to be tested: according to Table 8.7.10.3.4.1-1 depending on the UE category according to Table 8.7.10.3.4.1-2 for UE not supporting 256QAM or Table 8.7.10.3.4.1-3 for UE supporting 256QAM.
1. Connect the SS to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure A.91.
2. For UE not supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.3.4.1-1 depending on the UE category according to Table 8.7.10.3.4.1-2. For UE supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.3.4.1-1 depending on the UE category according to Table 8.7.10.3.4.1-3.
3. Downlink signals for PCC are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.
4. Propagation conditions are set according to Annex B.0.
5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 5.2A.3. Message contents are defined in clause 8.7.10.3.4.3.
8.7.10.3.4.2 Test procedure
1. Configure SCC according to Annex C.0, C.1 and Annex C.3.2 for all downlink physical channels.
2. The SS shall configure SCC as per TS 36.508 [7] clause 5.2A.4. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.10.3.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.10.3.4.3-4. Cell ID = 1 applies to S-Cell.
3. The SS activates SCC by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).
4. Propagation conditions are set according to Annex B.1 (No external noise sources are applied).
5. For UE not supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-2, for the tests to be performed depending on the UE category according to Table 8.7.10.3.4.1-2. For UE supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-3, for the tests to be performed depending on the UE category according to Table 8.7.10.3.4.1-3.
6. The SS sets the counters NDL_newtx, NDL_retx, NUL_PDCP and NDDL_PDCP to 0.
7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB (Note 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 and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.
8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.
9. Steps 7 to 8 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.
10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one
11. The SS calculates the TB success rate as A = 100%*NDL_newtx / (NDL_newtx + NDL_retx). Measurements are not based on UE feedback but on SS counters instead (NDL_newtx and NDL_retx) in order to validate HARQ feedback received from the UE.
12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP
13. The UE passes the test if A > 85% 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.
8.7.10.3.4.3 Message contents
Message contents are according to TS 36.508 [7] clauses 5.5 and 4.6 and 4.7A, with the following exceptions:
Table 8.7.10.3.4.3-1: CLOSE UE TEST LOOP (in the preamble)
|
Derivation Path: 36.509 clause 6.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 1 0 1 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0 |
UL PDCP SDU size = 40 bits (5 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1 |
||
|
UE test loop mode B LB setup |
Not present |
|||
Table 8.7.10.3.4.3-2: SecurityModeCommand (in the preamble)
|
Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
SecurityModeCommand ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE{ |
||||
|
securityModeCommand-r8 SEQUENCE { |
||||
|
securityConfiguration SEQUENCE { |
||||
|
cipheringAlgorithm |
eea2 |
|||
|
nextHopChainingCount |
Not present |
|||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.7.10.3.4.3-3: PhysicalConfigDedicated-DEFAULT
|
Derivation Path: 36.508 clause 5.5.1, Table 5.5.1.2-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
|||
|
antennaInfo CHOICE { |
|||
|
explicitValue ::= SEQUENCE { |
|||
|
transmissionMode |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction CHOICE { |
|||
|
n2TxAntenna-tm3 |
10 |
2TX |
|
|
n4TxAntenna-tm3 |
1000 |
4TX |
|
|
} |
|||
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
Release |
NULL |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna P-Cell |
|
4TX |
4 SS Tx antenna P-Cell |
Table 8.7.10.3.4.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT
|
Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE { |
|||
|
nonUL-Configuration-r10 SEQUENCE { |
|||
|
antennaInfo-r10 CHOICE { |
|||
|
transmissionMode-r10 |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction-r10 |
10 |
2TX |
|
|
codebookSubsetRestriction-r10 |
1000 |
4TX |
|
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
Release |
NULL |
||
|
} |
|||
|
} |
|||
|
pdsch-ConfigDedicated-r10 CHOICE { |
4TX |
||
|
p-a |
dB-6 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna S-Cell |
|
4TX |
4 SS Tx antenna S-Cell |
8.7.10.3.5 Test requirement
The pass fail decision is as specified in the test procedure in clause 8.7.10.3.4.2.
There are no parameters in the test setup or measurement process whose variation impacts the results so there are no applicable test tolerances for this test.
8.7.10.4 TDD sustained data rate performance for 4 layer MIMO (3DL CA)
Editor’s note: Simplification of test point tables, to reduce future maintenance, needs further investigation.
8.7.10.4.1 Test purpose
Same test purpose as 8.7.1.1.
8.7.10.4.2 Test applicability
This test applies to E-UTRA TDD release 10 and forward UE of category 11 and 12 and DL category 11, 12, 15, 16 and 18 that supports 3DL with CA configurations in Table 7.1-2a and supports 4 Rx antenna ports and 4-layer spatial multiplexing for PDSCH transmission mode 3 in any TDD RF band of the 3DL CA configuration.
This test applies to E-UTRA TDD release 11 and forward UE of category 11 and 12 and DL category 11, 12, 15, 16 and 18 that supports 3DL with CA configurations in Table 7.1-2a and supports 4 Rx antenna ports and 4-layer spatial multiplexing for PDSCH transmission mode 3 in any TDD RF band of the 3DL CA configuration.
8.7.10.4.3 Minimum conformance requirements
The minimum conformance requirements are defined in clause 8.7.10.1.
8.7.10.4.4 Test description
8.7.10.4.4.1 Initial conditions
For UE not supporting 256QAM, the requirements are specified in Table 8.7.10.1-2, with the addition of the parameters in Table 8.7.10.4.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.4.4.1-2.
For UE supporting 256QAM, the requirements are specified in Table 8.7.10.1-3, with the addition of the parameters in Table 8.7.10.4.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.4.4.1-3.
Table 8.7.10.4.4.1-1: Test parameters for sustained downlink data rate (TDD 3DL CA)
|
Test |
Bandwidth (MHz) |
MIMO layer |
Antenna configuration |
Equivalent aggr. BW (MHz) |
PDCP SDU size [Octets] 64QAM |
PDCP SDU size [Octets] 256QAM |
|
1 |
3×20 |
4 layer |
4×4 |
240 |
1455 |
1408 |
|
2 |
15+20+20 |
4 layer |
4×4 |
220 |
1455 |
1408 |
|
3 |
20 |
2 layer |
2×2 |
200 |
1341 |
1355 |
|
2×20 |
4 layer |
4×4 |
||||
|
4 |
20 |
2 layer |
2×2 |
180 |
1341 |
1355 |
|
15+20 |
4 layer |
4×4 |
||||
|
5 |
2×20 |
2 layer |
2×2 |
160 |
1341 |
1355 |
|
20 |
4 layer |
4×4 |
||||
|
6 |
15+20 |
2 layer |
2×2 |
150 |
1341 |
1341 |
|
20 |
4 layer |
4×4 |
Editor’s note: Tests in Table 8.7.10.4.4.1-1 are covering maximum aggregated bandwidth for each Bandwidth combination set with 3DL CA which are defined in Table 5.4.2A.1-1 or Table 5.4.2A.1-2.
Table 8.7.10.4.4.1-2: Test points for sustained data rate (FRC 64QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
Antenna config. |
DL Cat. 11, 12 |
|||||
|
240 |
3×20 |
4×4 |
4 |
– |
2 |
1 |
– |
– |
|
220 |
15+20+20 |
4×4 |
4 |
– |
2 |
2 |
– |
– |
|
200 |
20 |
2×2 |
4 |
– |
3 |
3 |
– |
– |
|
2×20 |
4×4 |
|||||||
|
180 |
20 |
2×2 |
4 |
– |
4 |
4 |
– |
– |
|
15+20 |
4×4 |
|||||||
|
160 |
2×20 |
2×2 |
5 |
– |
5 |
5 |
– |
– |
|
20 |
4×4 |
|||||||
|
150 |
15+20 |
2×2 |
6 |
– |
6 |
6 |
– |
– |
|
20 |
4×4 |
|||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
Table 8.7.10.4.4.1-3: Test points for sustained data rate (FRC 256QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
Antenna config. |
DL Cat. 11, 12 |
|||||
|
240 |
3×20 |
4×4 |
– |
– |
5 |
2 |
1 |
– |
|
220 |
15+20+20 |
4×4 |
– |
– |
6 |
2 |
2 |
– |
|
200 |
20 |
2×2 |
– |
– |
5 |
3 |
3 |
– |
|
2×20 |
4×4 |
|||||||
|
180 |
20 |
2×2 |
– |
– |
6 |
4 |
4 |
– |
|
15+20 |
4×4 |
|||||||
|
160 |
2×20 |
2×2 |
– |
– |
5 |
5 |
5 |
– |
|
20 |
4×4 |
|||||||
|
150 |
15+20 |
2×2 |
– |
– |
6 |
6 |
6 |
– |
|
20 |
4×4 |
|||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
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.
Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2.
Test Environment: Normal as defined in TS 36.508 [7] clause 4.1.
Frequencies to be tested: Maximum WGap for Intra-band non-contiguous CA, otherwise Mid Range as defined in TS 36.508 [7] clause 4.3.1.1.
Channel Bandwidths to be tested: according to Table 8.7.10.4.4.1-1 depending on the UE category according to Table 8.7.10.4.4.1-2 for UE not supporting 256QAM or Table 8.7.10.4.4.1-3 for UE supporting 256QAM.
1. Connect the SS to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure A.91.
2. For UE not supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.4.4.1-1 depending on the UE category according to Table 8.7.10.4.4.1-2. For UE supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.4.4.1-1 and depending on the UE category according to Table 8.7.10.4.4.1-3.
3. Downlink signals for PCC are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.
4. Propagation conditions are set according to Annex B.0.
5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 5.2A.3. Message contents are defined in clause 8.7.10.4.4.3.
8.7.10.4.4.2 Test procedure
1. Configure SCCs according to Annex C.0, C.1 and Annex C.3.2 for all downlink physical channels.
2. The SS shall configure SCCs as per TS 36.508 [7] clause 5.2A.4 with two SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.10.4.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.10.4.4.3-4. Cell ID = n (where n is 1, 2) applies to S-Celln (where n is 1, 2).
3. The SS activates SCCs by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).
4. Propagation conditions are set according to Annex B.1 (No external noise sources are applied).
5. For UE not supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-2, for the tests to be performed depending on the UE category according to Table 8.7.10.4.4.1-2. For UE supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-3, for the tests to be performed depending on the UE category according to Table 8.7.10.4.4.1-3.
6. The SS sets the counters NDL_newtx, NDL_retx, NUL_PDCP and NDDL_PDCP to 0.
7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the (Note 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 and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.
8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.
9. Steps 7 to 8 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.
10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one
11. The SS calculates the TB success rate as A = 100%*NDL_newtx / (NDL_newtx + NDL_retx). Measurements are not based on UE feedback but on SS counters instead (NDL_newtx and NDL_retx) in order to validate HARQ feedback received from the UE.
12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP
13. The UE passes the test if A > 85% 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.
8.7.10.4.4.3 Message contents
Message contents are according to TS 36.508 [7] clauses 5.5 and 4.6 and 4.7A, with the following exceptions:
Table 8.7.10.4.4.3-1: CLOSE UE TEST LOOP (in the preamble)
|
Derivation Path: 36.509 clause 6.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 1 0 1 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0 |
UL PDCP SDU size = 40 bits (5 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1 |
||
|
UE test loop mode B LB setup |
Not present |
|||
Table 8.7.10.4.4.3-2: SecurityModeCommand (in the preamble)
|
Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
SecurityModeCommand ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE{ |
||||
|
securityModeCommand-r8 SEQUENCE { |
||||
|
securityConfiguration SEQUENCE { |
||||
|
cipheringAlgorithm |
eea2 |
|||
|
nextHopChainingCount |
Not present |
|||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.7.10.4.4.3-3: PhysicalConfigDedicated-DEFAULT
|
Derivation Path: 36.508 clause 5.5.1, Table 5.5.1.2-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
|||
|
antennaInfo CHOICE { |
|||
|
explicitValue ::= SEQUENCE { |
|||
|
transmissionMode |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction CHOICE { |
|||
|
n2TxAntenna-tm3 |
10 |
2TX |
|
|
n4TxAntenna-tm3 |
1000 |
4TX |
|
|
} |
|||
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
release |
NULL |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna P-Cell |
|
4TX |
4 SS Tx antenna P-Cell |
Table 8.7.10.4.4.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT
|
Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE { |
|||
|
nonUL-Configuration-r10 SEQUENCE { |
|||
|
antennaInfo-r10 CHOICE { |
|||
|
transmissionMode-r10 |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction-r10 |
10 |
2TX |
|
|
codebookSubsetRestriction-r10 |
1000 |
4TX |
|
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
Release |
NULL |
||
|
} |
|||
|
} |
|||
|
pdsch-ConfigDedicated-r10 CHOICE { |
4TX |
||
|
p-a |
dB-6 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna S-Cell |
|
4TX |
4 SS Tx antenna S-Cell |
8.7.10.4.5 Test requirement
The pass fail decision is as specified in the test procedure in clause 8.7.10.4.4.2.
There are no parameters in the test setup or measurement process whose variation impacts the results so there are no applicable test tolerances for this test.
8.7.10.5 TDD sustained data rate performance for 4 layer MIMO (4DL CA)
Editor’s note: Simplification of test point tables, to reduce future maintenance, needs further investigation.
8.7.10.5.1 Test purpose
Same test purpose as 8.7.1.1.
8.7.10.5.2 Test applicability
This test case applies to all types of E-UTRA TDD UE release 11 and forward of UE DL category 16, 18 and 19 that support 4DL with CA configurations in Table 7.1-2b and supports 4 Rx antenna ports and 4-layer spatial multiplexing for PDSCH transmission mode 3 in any TDD RF band of the 4DL CA configuration.
8.7.10.5.3 Minimum conformance requirements
The minimum conformance requirements are defined in clause 8.7.10.1.
8.7.10.5.4 Test description
8.7.10.5.4.1 Initial conditions
For UE not supporting 256QAM, the requirements are specified in Table 8.7.10.1-2, with the addition of the parameters in Table 8.7.10.5.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.5.4.1-2.
For UE supporting 256QAM, the requirements are specified in Table 8.7.10.1-3, with the addition of the parameters in Table 8.7.10.5.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.5.4.1-4.
Table 8.7.10.5.4.1-1: Test parameters for sustained downlink data rate (TDD 4DL CA)
|
Test |
Bandwidth (MHz) |
MIMO layer |
Antenna configuration |
Equivalent aggr. BW (MHz) |
PDCP SDU size [Octets] 64QAM |
PDCP SDU size [Octets] 256QAM |
|
1 |
4×20 |
4 layer |
4×4 |
320 |
1455 |
1408 |
|
2 |
15+20+20+20 |
4 layer |
4×4 |
300 |
1455 |
1408 |
|
3 |
20 |
2 layer |
2×2 |
280 |
1341 |
1355 |
|
3×20 |
4 layer |
4×4 |
||||
|
4 |
2×20 |
2 layer |
2×2 |
240 |
1341 |
1355 |
|
2×20 |
4 layer |
4×4 |
||||
|
5 |
15+20 |
2 layer |
2×2 |
230 |
1341 |
1341 |
|
2×20 |
4 layer |
4×4 |
||||
|
6 |
2×20 |
2 layer |
2×2 |
220 |
1341 |
1355 |
|
15+20 |
4 layer |
4×4 |
||||
|
7 |
3×20 |
2 layer |
2×2 |
200 |
1341 |
1355 |
|
20 |
4 layer |
4×4 |
Editor’s note: Tests in Table 8.7.10.5.4.1-1 are covering maximum aggregated bandwidth for each Bandwidth combination set with 4DL CA which are defined in Table 5.4.2A.1-1 or Table 5.4.2A.1-2.
Table 8.7.10.5.4.1-2: Test points for sustained data rate (FRC 64QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
Antenna config. |
DL Cat. 11, 12 |
|||||
|
320 |
4×20 |
4×4 |
– |
– |
– |
2 |
1 |
– |
|
300 |
15+20+20+20 |
4×4 |
– |
– |
– |
2 |
2 |
– |
|
280 |
20 |
2×2 |
– |
– |
– |
3 |
3 |
– |
|
3×20 |
4×4 |
|||||||
|
240 |
2×20 |
2×2 |
– |
– |
– |
4 |
4 |
– |
|
2×20 |
4×4 |
|||||||
|
230 |
15+20 |
2×2 |
– |
– |
– |
5 |
5 |
– |
|
2×20 |
4×4 |
|||||||
|
220 |
2×20 |
2×2 |
– |
– |
– |
6 |
6 |
– |
|
15+20 |
4×4 |
|||||||
|
200 |
3×20 |
2×2 |
– |
– |
– |
7 |
7 |
– |
|
20 |
4×4 |
|||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
Table 8.7.10.5.4.1-3: Test points for sustained data rate (FRC 256QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
Antenna config. |
DL Cat. 11, 12 |
|||||
|
320 |
4×20 |
4×4 |
– |
– |
– |
– |
4 |
1 |
|
300 |
15+20+20+20 |
4×4 |
– |
– |
– |
– |
5 |
2 |
|
280 |
20 |
2×2 |
– |
– |
– |
– |
4 |
3 |
|
3×20 |
4×4 |
|||||||
|
240 |
2×20 |
2×2 |
– |
– |
– |
– |
4 |
4 |
|
2×20 |
4×4 |
|||||||
|
230 |
15+20 |
2×2 |
– |
– |
– |
– |
5 |
5 |
|
2×20 |
4×4 |
|||||||
|
220 |
2×20 |
2×2 |
– |
– |
– |
– |
6 |
6 |
|
15+20 |
4×4 |
|||||||
|
200 |
3×20 |
2×2 |
– |
– |
– |
– |
7 |
7 |
|
20 |
4×4 |
|||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
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.
Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2.
Test Environment: Normal as defined in TS 36.508 [7] clause 4.1.
Frequencies to be tested: Mid Range as defined in TS 36.508 [7] clause 4.3.1.1.
Channel Bandwidths to be tested: according to Table 8.7.10.5.4.1-1 depending on the UE category according to Table 8.7.10.5.4.1-2 for UE not supporting 256QAM or Table 8.7.10.5.4.1-3 for UE supporting 256QAM.
1. Connect the SS to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure A.91.
2. For UE not supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.5.4.1-1 depending on the UE category according to Table 8.7.10.5.4.1-2. For UE supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.5.4.1-1 depending on the UE category according to Table 8.7.10.5.4.1-3.
3. Downlink signals for PCC are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.
4. Propagation conditions are set according to Annex B.0.
5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 5.2A.3. Message contents are defined in clause 8.7.10.5.4.3.
8.7.10.5.4.2 Test procedure
1. Configure SCCs according to Annex C.0, C.1 and Annex C.3.2 for all downlink physical channels.
2. The SS shall configure SCCs as per TS 36.508 [7] clause 5.2A.4 with three SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.10.5.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.10.5.4.3-4. Cell ID = n (where n is 1, 2, 3) applies to S-Celln (where n is 1, 2, 3).
3. The SS activates SCCs by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).
4. Propagation conditions are set according to Annex B.1 (No external noise sources are applied).
5. For UE not supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-2, for the tests to be performed depending on the UE category according to Table 8.7.10.5.4.1-2. For UE supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-3, for the tests to be performed depending on the UE category according to Table 8.7.10.5.4.1-3.
6. The SS sets the counters NDL_newtx, NDL_retx, NUL_PDCP and NDDL_PDCP to 0.
7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB (Note 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 and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.
8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.
9. Steps 7 to 8 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.
10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one
11. The SS calculates the TB success rate as A = 100%*NDL_newtx / (NDL_newtx + NDL_retx). Measurements are not based on UE feedback but on SS counters instead (NDL_newtx and NDL_retx) in order to validate HARQ feedback received from the UE.
12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP
13. The UE passes the test if A > 85% 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.
8.7.10.5.4.3 Message contents
Message contents are according to TS 36.508 [7] clauses 5.5 and 4.6 and 4.7A, with the following exceptions:
Table 8.7.10.5.4.3-1: CLOSE UE TEST LOOP (in the preamble)
|
Derivation Path: 36.509 clause 6.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 1 0 1 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0 |
UL PDCP SDU size = 40 bits (5 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1 |
||
|
UE test loop mode B LB setup |
Not present |
|||
Table 8.7.10.5.4.3-2: SecurityModeCommand (in the preamble)
|
Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
SecurityModeCommand ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE{ |
||||
|
securityModeCommand-r8 SEQUENCE { |
||||
|
securityConfiguration SEQUENCE { |
||||
|
cipheringAlgorithm |
eea2 |
|||
|
nextHopChainingCount |
Not present |
|||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.7.10.5.4.3-3: PhysicalConfigDedicated-DEFAULT
|
Derivation Path: 36.508 clause 5.5.1, Table 5.5.1.2-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
|||
|
antennaInfo CHOICE { |
|||
|
explicitValue ::= SEQUENCE { |
|||
|
transmissionMode |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction CHOICE { |
|||
|
n2TxAntenna-tm3 |
10 |
2TX |
|
|
n4TxAntenna-tm3 |
1000 |
4TX |
|
|
} |
|||
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
release |
NULL |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna P-Cell |
|
4TX |
4 SS Tx antenna P-Cell |
Table 8.7.10.5.4.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT
|
Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE { |
|||
|
nonUL-Configuration-r10 SEQUENCE { |
|||
|
antennaInfo-r10 CHOICE { |
|||
|
transmissionMode-r10 |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction-r10 |
10 |
2TX |
|
|
codebookSubsetRestriction-r10 |
1000 |
4TX |
|
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
Release |
NULL |
||
|
} |
|||
|
} |
|||
|
pdsch-ConfigDedicated-r10 CHOICE { |
4TX |
||
|
p-a |
dB-6 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna S-Cell |
|
4TX |
4 SS Tx antenna S-Cell |
8.7.10.5.5 Test requirement
The pass fail decision is as specified in the test procedure in clause 8.7.10.5.4.2.
There are no parameters in the test setup or measurement process whose variation impacts the results so there are no applicable test tolerances for this test.
8.7.10.6 TDD sustained data rate performance for 4 layer MIMO (5DL CA)
Editor’s note: Simplification of test point tables, to reduce future maintenance, needs further investigation.
8.7.10.6.1 Test purpose
Same test purpose as 8.7.1.1.
8.7.10.6.2 Test applicability
This test applies to E-UTRA TDD release 11 and forward UE of DL category 18 and 19 that supports 5DL with CA configurations in Table 7.1-2c and supports 4 Rx antenna ports and 4-layer spatial multiplexing for PDSCH transmission mode 3 in any TDD RF band of the 5DL CA configuration.
8.7.10.6.3 Minimum conformance requirements
The minimum conformance requirements are defined in clause 8.7.10.1.
8.7.10.6.4 Test description
8.7.10.6.4.1 Initial conditions
For UE not supporting 256QAM, the requirements are specified in Table 8.7.10.1-2, with the addition of the parameters in Table 8.7.10.6.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.6.4.1-2.
For UE supporting 256QAM, the requirements are specified in Table 8.7.10.1-3, with the addition of the parameters in Table 8.7.10.6.4.1-1. The test points are applied to UE category and bandwidth combination with maximum equivalent aggregated bandwidth as specified in Table 8.7.10.6.4.1-3.
Table 8.7.10.6.4.1-1: Test parameters for sustained downlink data rate (TDD 5DL CA)
|
Test |
Bandwidth (MHz) |
MIMO layer |
Antenna configuration |
Equivalent aggr. BW (MHz) |
PDCP SDU size [Octets] 64QAM |
PDCP SDU size [Octets] 256QAM |
|
1 |
5×20 |
4 layer |
4×4 |
400 |
1455 |
1408 |
|
2 |
15+(4×20) |
4 layer |
4×4 |
380 |
1455 |
1408 |
|
3 |
2×20 |
2 layer |
2×2 |
320 |
1341 |
1355 |
|
3×20 |
4 layer |
4×4 |
||||
|
4 |
15+20 |
2 layer |
2×2 |
310 |
1341 |
1341 |
|
3×20 |
4 layer |
4×4 |
||||
|
5 |
3×20 |
2 layer |
2×2 |
280 |
1341 |
1355 |
|
2×20 |
4 layer |
4×4 |
||||
|
6 |
3×20 |
2 layer |
2×2 |
260 |
1341 |
1355 |
|
15+20 |
4 layer |
4×4 |
Editor’s note: Tests in Table 8.7.10.6.4.1-1 are covering maximum aggregated bandwidth for each Bandwidth combination set with 5DL CA which are defined in Table 5.4.2A.1-1 and Table 5.4.2A.1-2.
Table 8.7.10.6.4.1-2: Test points for sustained data rate (FRC 64QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
Antenna config. |
DL Cat. 11, 12 |
|||||
|
400 |
5×20 |
4×4 |
– |
– |
– |
– |
3 |
1 |
|
380 |
15+20+20+20+20 |
4×4 |
– |
– |
– |
– |
4 |
2 |
|
320 |
2×20 |
2×2 |
– |
– |
– |
– |
3 |
3 |
|
3×20 |
4×4 |
|||||||
|
310 |
15+20 |
2×2 |
– |
– |
– |
– |
4 |
4 |
|
3×20 |
4×4 |
|||||||
|
280 |
3×20 |
2×2 |
– |
– |
– |
– |
5 |
5 |
|
2×20 |
4×4 |
|||||||
|
260 |
3×20 |
2×2 |
– |
– |
– |
– |
6 |
6 |
|
15+20 |
4×4 |
|||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
Table 8.7.10.6.4.1-3: Test points for sustained data rate (FRC 256QAM)
|
Maximum supported equivalent aggr. BW |
Cat. 11, 12 |
DL Cat. 13 |
DL Cat. 15 |
DL Cat. 16 |
DL Cat. 18 |
DL Cat. 19 |
||
|
Bagg (MHz) |
BW combi-nation (MHz) |
Antenna config. |
DL Cat. 11, 12 |
|||||
|
400 |
5×20 |
4×4 |
– |
– |
– |
– |
– |
3 |
|
380 |
15+20+20+20+20 |
4×4 |
– |
– |
– |
– |
– |
4 |
|
320 |
2×20 |
2×2 |
– |
– |
– |
– |
– |
3 |
|
3×20 |
4×4 |
|||||||
|
310 |
15+20 |
2×2 |
– |
– |
– |
– |
– |
4 |
|
3×20 |
4×4 |
|||||||
|
280 |
3×20 |
2×2 |
– |
– |
– |
– |
– |
5 |
|
2×20 |
4×4 |
|||||||
|
260 |
3×20 |
2×2 |
– |
– |
– |
– |
– |
6 |
|
15+20 |
4×4 |
|||||||
|
Note 1: Select the largest equivalent aggregated bandwidth supported by the UE as defined in clause 8.7.10.1. Only one test point to be tested. |
||||||||
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.
Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2.
Test Environment: Normal as defined in TS 36.508 [7] clause 4.1.
Frequencies to be tested: Mid Range as defined in TS 36.508 [7] clause 4.3.1.1.
Channel Bandwidths to be tested: according to Table 8.7.10.6.4.1-1 depending on the UE category according to Table 8.7.10.6.4.1-2 for UE not supporting 256QAM or Table 8.7.10.6.4.1-3 for UE supporting 256QAM.
1. Connect the SS to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure A.91.
2. For UE not supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.6.4.1-1 depending on the UE category according to Table 8.7.10.6.4.1-2. For UE supporting 256QAM the parameter settings for the cell are set up according to Table 8.7.10.1-1, Table 8.7.10.6.4.1-1 depending on the UE category according to Table 8.7.10.6.4.1-3.
3. Downlink signals for PCC are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.
4. Propagation conditions are set according to Annex B.0.
5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 5.2A.3. Message contents are defined in clause 8.7.10.6.4.3.
8.7.10.6.4.2 Test procedure
1. Configure SCCs according to Annex C.0, C.1 and Annex C.3.2 for all downlink physical channels.
2. The SS shall configure SCCs as per TS 36.508 [7] clause 5.2A.4 with four SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.10.6.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.10.6.4.3-4. Cell ID = n (where n is 1, 2, 3, 4) applies to S-Celln (where n is 1, 2, 3, 4).
3. The SS activates SCCs by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).
4. Propagation conditions are set according to Annex B.1 (No external noise sources are applied).
5. For UE not supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-2, for the tests to be performed depending on the UE category according to Table 8.7.10.6.4.1-2. For UE supporting 256QAM the SS looks up TBsize in Annex A.3.9 for the RMCs in accordance with table 8.7.10.1-3, for the tests to be performed depending on the UE category according to Table 8.7.10.6.4.1-3.
6. The SS sets the counters NDL_newtx, NDL_retx, NUL_PDCP and NDDL_PDCP to 0.
7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB (Note 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 and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.
8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.
9. Steps 7 to 8 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.
10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one
11. The SS calculates the TB success rate as A = 100%*NDL_newtx / (NDL_newtx + NDL_retx). Measurements are not based on UE feedback but on SS counters instead (NDL_newtx and NDL_retx) in order to validate HARQ feedback received from the UE.
12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP
13. The UE passes the test if A > 85% 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.
8.7.10.6.4.3 Message contents
Message contents are according to TS 36.508 [7] clauses 5.5 and 4.6 and 4.7A, with the following exceptions:
Table 8.7.10.6.4.3-1: CLOSE UE TEST LOOP (in the preamble)
|
Derivation Path: 36.509 clause 6.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 1 0 1 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0 |
UL PDCP SDU size = 40 bits (5 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1 |
||
|
UE test loop mode B LB setup |
Not present |
|||
Table 8.7.10.6.4.3-2: SecurityModeCommand (in the preamble)
|
Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
SecurityModeCommand ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE{ |
||||
|
securityModeCommand-r8 SEQUENCE { |
||||
|
securityConfiguration SEQUENCE { |
||||
|
cipheringAlgorithm |
eea2 |
|||
|
nextHopChainingCount |
Not present |
|||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 8.7.10.6.4.3-3: PhysicalConfigDedicated-DEFAULT
|
Derivation Path: 36.508 clause 5.5.1, Table 5.5.1.2-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
|||
|
antennaInfo CHOICE { |
|||
|
explicitValue ::= SEQUENCE { |
|||
|
transmissionMode |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction CHOICE { |
|||
|
n2TxAntenna-tm3 |
10 |
2TX |
|
|
n4TxAntenna-tm3 |
1000 |
4TX |
|
|
} |
|||
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
release |
NULL |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna P-Cell |
|
4TX |
4 SS Tx antenna P-Cell |
Table 8.7.10.6.4.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT
|
Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE { |
|||
|
nonUL-Configuration-r10 SEQUENCE { |
|||
|
antennaInfo-r10 CHOICE { |
|||
|
transmissionMode-r10 |
tm3 |
Transmission mode 3 |
|
|
codebookSubsetRestriction-r10 |
10 |
2TX |
|
|
codebookSubsetRestriction-r10 |
1000 |
4TX |
|
|
ue-TransmitAntennaSelection CHOICE { |
|||
|
Release |
NULL |
||
|
} |
|||
|
} |
|||
|
pdsch-ConfigDedicated-r10 CHOICE { |
4TX |
||
|
p-a |
dB-6 |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
Condition |
Explanation |
|
2TX |
2 SS Tx antenna S-Cell |
|
4TX |
4 SS Tx antenna S-Cell |
8.7.10.6.5 Test requirement
The pass fail decision is as specified in the test procedure in clause 8.7.10.6.4.2.
There are no parameters in the test setup or measurement process whose variation impacts the results so there are no applicable test tolerances for this test.