8.7.2 TDD

36.521-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Part 1: Conformance testingRadio transmission and receptionRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

The parameters specified in Table 8.7.2-1 are valid for all TDD tests unless otherwise stated.

Table 8.7.2-1: Common Test Parameters (TDD)

Parameter	Unit	Value
Special subframe configuration (Note 1)		4
Cyclic prefix		Normal
Cell ID		0 (Note 2)
Inter-TTI Distance		1
Maximum number of HARQ transmission		Downlink: 4 Uplink: 1
Redundancy version coding sequence		{0,0,1,2} for 64QAM and 256QAM
Scheduling of retransmissions		1. Retransmissions use the same Transport Block Size (TBS) as the initial transmission. 2. HARQ processes are scheduled consecutively, independent of the fact, whether retransmissions (for negatively acknowledged HARQ processes) or new transmissions (for positively acknowledged HARQ processes) occur. 3. Despite of 1) and 2) the number of RB-s to be allocated in each SF remains firm as specified in the RMC. Thus in case of RMC-s with SF dependent allocation, for retransmissions the TBS and the modulation scheme (MCS) are indicated implicitly () according to TS 36.213 [10] subclause 7.1.7.2.
Number of OFDM symbols for PDCCH	OFDM symbols	1
Cross carrier scheduling		Not configured
Propagation conditions		Static propagation condition No external noise sources are applied
Note 1: as specified in Table 4.2-1 in TS 36.211 [4]. Note 2: For CA tests, Cell ID = 0 applies to P-Cell, Cell ID = n (where n is 1, 2, 3..) applies to S-Cells ( where n is 1, 2, 3..), respectively.

The normative reference for this requirement is TS 36.101[2] clause 8.7.2.

8.7.2.1 TDD sustained data rate performance

8.7.2.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 number of DL-SCH transport block bits received within a TTI for the UE category indicated. 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. The size of the TB per TTI corresponds to the largest possible DL-SCH transport block for each UE category using the maximum number of layers for spatial multiplexing. Transmission modes 1 and 3 are used with radio conditions resembling a scenario where sustained maximum data rates are available. Test case is selected according to table 8.7.2.1.1-1 depending on UE capability for CA and EPDCCH.

Table 8.7.2.1.1-1: SDR test applicability

	Single carrier UE not supporting EPDCCH	CA UE not supporting EPDCCH	Single carrier UE supporting EPDCCH	CA UE supporting EPDCCH
TDD	8.7.2.1, 8.7.2.1_1	8.7.2.1_A	8.7.4.1	8.7.2.1_A, 8.7.4.1

8.7.2.1.2 Test applicability

This test applies to E-UTRA TDD UE release 9 and forward UEs of category 1 to 4 and not supporting 256QAM in DL.

8.7.2.1.3 Minimum requirements

Table 8.7.2.1.3-1: Void

For UE not supporting 256QAM, the requirements are specified in Table 8.7.2.1.3-3, with the addition of the parameters in Table 8.7.2.1.3-2 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category as specified in Table 8.7.2.1.3-4. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1.3-2: Test parameters for sustained downlink data rate (TDD)

Test	Band-width (MHz)	Trans-mission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Band-width (MHz)	Trans-mission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
1	10	1	1 x 2	N/A	0	0	0	-85	Bundling	OP.6 TDD
2	10	3	2 x 2	10	-3	-3	0	-85	Bundling	OP.1 TDD
3	20	3	2 x 2	10	-3	-3	0	-85	Bundling	OP.1 TDD
3A	15	3	2 x 2	10	-3	-3	0	-85	Multiplexing	OP.2 TDD
4,6	20	3	2 x 2	10	-3	-3	0	-85	Multiplexing	OP.1 TDD

Table 8.7.2.1.3-3: Minimum requirement (TDD)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
1	10296/0	R.31-1 TDD	95
2	25456/0	R.31-2 TDD	95
3	51024/0	R.31-3 TDD	95
3A	51024/0	R.31-3A TDD	85
4	75376/0 (Note 2)	R.31-4 TDD	85
6	75376/0 (Note 2)	R.31-4 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1.3-4: Test points for sustained data rate (FRC)

CA config	Bandwidth (MHz)	Category 1	Category 2	Category 3	Category 4	Category 6	Category 7
Single carrier	10	1	2	–	–	–	–
	15	–	–	3A	3A	–	–
	20	–	–	3	4	6	6
Note 1: If UE can be tested for CA configuration, single carrier test is skipped. Note 2: For non-CA UE, test is selected for maximum supported bandwidth.

The normative reference for this requirement is TS 36.101[2] clause 8.7.2

8.7.2.1.4 Test description

8.7.2.1.4.1 Initial conditions

Table 8.7.2.1.4.1-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement Channel	TB_size per Codeword	Number of PDCP SDU per Codeword for normal/special sub-frame	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets] for normal/special sub-frame
1	R.31-1 TDD	R.1-1 TDD	10296	1/0	FLOOR((TB_size– 96)/8)	1275/0
2	R.31-2 TDD	R.1-2 TDD	25456	3/0	FLOOR((TB_size– 152)/24))	1054/0
3	R.31-3 TDD	R.1-3 TDD	51024	5/0	FLOOR((TB_size– 208)/40))	1270/0
3A	R.31-3B TDD	R.1-3B TDD	51024	5/0	FLOOR((TB_size– 208)/40))	1270/0
4	R.31-4 TDD	R.1-4 TDD	75376 (Note 3)	7/0	FLOOR((TB_size– 264)/56))	1341/0
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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of Timing Advance – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 71112 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.2.1.5-2 depending on the UE category according to Table 8.7.2.1.5-3.

1. Connect the SS, to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure A.3 for test 1 and Figure A.10 for tests 2-5 (without using faders and AWGN generators).

2. The parameter settings for the cell are set up according to Table 8.7.2.1.5-2 and Table 8.7.2.1.5-1 depending on the UE category according to Table 8.7.2.1.5-3.

3. Downlink signals are initially set up according to Annex C0, 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.2.1.4.3. PhysicalConfigDedicated-DEFAULT for transmission mode 3 is defined in Table 8.7.2.1.4.3-3.

8.7.2.1.4.2 Test procedure

1. Propagation conditions are set according to Annex B.1. No external noise sources are applied.

2. The SS looks up TB_size in Table 8.7.2.1.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.2.1.5-3.

3. SS sets the counters N_{DL_newtx}, N_{DL_retx}, N_{UL_PDCP}, and ND_{DL_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.2.1.4.1-1 (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 N_{DL_newtx} by one and N_{DL_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 N_{DL_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 N_{UL_PDCP} by one.

8. The SS calculates the TB success rate as A = 100%*N_{DL_newtx}/ (N_{DL_newtx} + N_{DL_retx}). Measurements are not based on UE feedback but on SS counters instead (N_{DL_newtx} and N_{DL_retx}) in order to validate HARQ feedback received from the UE.

9. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP}

10. The UE passes the test if A ≥ "corresponding TB success rates according to Table 8.7.2.1.5-1" 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.2.1.4.3 Message contents

Message contents are according to TS 36.508 [7] clause 4.6 and 4.7A, with the following exceptions:

Table 8.7.2.1.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 101 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.2.1.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.2.1.4.3-3: 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	tm1 for Test 1 tm3 for other Test 2, 3, 3B and 4
codebookSubsetRestriction CHOICE {
n2TxAntenna-tm3	Not present for Test 1 10 for other Test 2, 3, 3B and 4
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.2.1.5 Test requirement

The requirements are specified in Table 8.7.2.1.5-1 depending on the UE category according to Table 8.7.2.1.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
1	10296/0	R.31-1 TDD	95
2	25456/0	R.31-2 TDD	95
3	51024/0	R.31-3 TDD	95
3A	51024/0	R.31-3A TDD	85
4	75376/0 (Note 2)	R.31-4 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
1	10	1	1 x 2	N/A	0	0	0	-85	Bundling	OP.6 TDD
2	10	3	2 x 2	10	-3	-3	0	-85	Bundling	OP.1 TDD
3	20	3	2 x 2	10	-3	-3	0	-85	Bundling	OP.1 TDD
3A	15	3	2 x 2	10	-3	-3	0	-85	Multiplexing	OP.2 TDD
4	20	3	2 x 2	10	-3	-3	0	-85	Multiplexing	OP.1 TDD
Note 1: N/A.

Table 8.7.2.1.5-3: Test applicability per UE category

CA config	Bandwidth (MHz)	Category 1	Category 2	Category 3	Category 4	Category 6	Category 7
Single carrier	10	1	2	–	–	–	–
	15	–	–	3A	3A	–	–
	20	–	–	3	4	–	–
Note 1: If UE can be tested for CA configuration, single carrier test is skipped. Note 2: For non-CA UE, test is selected for maximum supported bandwidth in this table for the corresponding category.

8.7.2.1_1 TDD sustained data rate performance (Rel‑10 and forward)

8.7.2.1_1.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.2.1_1.2 Test applicability

This test case applies to E-UTRA TDD release 10 and forward of UEs category 6 and 7.

8.7.2.1_1.3 Minimum requirements

Table 8.7.2.1_1.3-1: Void

Same minimum conformance requirements as in clause 8.7.2.1.3.

8.7.2.1_1.4 Test description

Same test description as in clause 8.7.2.1.4 with the following exceptions:

– Connection diagram Figure A.10 (without using faders and AWGN generators).

– Instead of Table 8.7.2.1.4.1-1 ‑> use Table 8.7.2.1_1.4-1.

– Instead of Table 8.7.2.1.5-1 ‑> use Table 8.7.2.1_1.5-1.

– Instead of Table 8.7.2.1.5-2 ‑> use Table 8.7.2.1_1.5-2.

– Instead of Table 8.7.2.1.5-3 ‑> use Table 8.7.2.1_1.5-3.

Table 8.7.2.1_1.4-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement Channel

TB_size per Codeword

Number of PDCP SDU per Codeword for normal/special sub-frame

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]
for normal/special sub-frame

R31-4 TDD

R.1-4 TDD

75376 (Note 3)

7/0

FLOOR((TB_size– 264)/56)

1341/0

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).

The PDCP SDU size of each PDCP SDU is:

PDCP SDU size = (TBsize – N*PDCP header size – AMD PDU header size – MAC header size – Size of Timing Advance – Size of RLC STATUS PDU) / N,

where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)*12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CEIL((16+(N-1)*12)/8) – 64)/(8*N)) bits.
The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test.

Note 3: 71112 bits for sub-frame 5.

8.7.2.1_1.5 Test requirement

The requirements are specified in Table 8.7.2.1.5-1 depending on the UE category according to Table 8.7.2.1_1.5-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_1.5-1: Test requirements for sustained downlink data rate (TDD)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
			TB success rate [%]
6	75376/0 (Note 2)	R.31-4 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_1.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
6	20	3	2 x 2	10	-3	-3	0	-85	Multiplexing	OP.1 TDD
Note 1: N/A.

Table 8.7.2.1_1.5-3: Test applicability per UE category

CA config

Bandwidth/ Bandwidth combination

(MHz)

Category 1

Category 2

Category 3

Category 4

Category 6

Category 7

Single carrier

–

Note 1: If UE can be tested for CA configuration, single carrier test is skipped.

Note 2: For non-CA UE, test is selected for maximum supported bandwidth.

8.7.2.1_2 TDD sustained data rate performance for UE category 1bis

8.7.2.1_2.1 Test purpose

Same test purpose as in clause 8.7.2.1.1.

8.7.2.1_2.2 Test applicability

This test applies to all types of E-UTRA FDD UE release 13 and forward of UE category 1bis.

8.7.2.1_2.3 Minimum conformance requirements

Same minimum conformance requirements as in clause 8.7.2.1.3 with the following exceptions:

– Instead of Table 8.7.2.1.3-2 🡪 use Table 8.7.2.1_2.3-1.

– Instead of Table 8.7.2.1.3-3 🡪 use Table 8.7.2.1_2.3-2.

Table 8.7.2.1_2.3-1: Test parameters for sustained downlink data rate (TDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
1A	10	1	1×1	N/A	0	0	0	-85	Bundling	OP.6 TDD
1B	20	1	1×1	N/A	0	0	0	-85	Bundling	OP.6 TDD

Table 8.7.2.1_2.3-2: Minimum Requirement (FDD)

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
1A	10296/0	R.31-1 TDD	95
1B	10296/0	R.31-1A TDD	95

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_2.4 Test description

Same test description as in clause 8.7.2.1.4 with the following exceptions:

– Instead of Table 8.7.2.1.4.1-1 ‑> use Table 8.7.2.1_2.4-1.

– Instead of Table 8.7.2.1.5-1 ‑> use Table 8.7.2.1_2.5-1.

– Instead of Table 8.7.2.1.5-2 ‑> use Table 8.7.2.1_2.5-2.

– Instead of Table 8.7.2.1.5-3 -> use Table 8.7.2.1_2.5-3.

Table 8.7.2.1_2.4.1-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TB_size per Codeword	Number of PDCP SDU per Codeword	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
1A	R.31-1 TDD	R.1-1 TDD	10296	1/0	FLOOR((TB_size– 96)/8)	1275/0
1B	R.31-1A FDD	R.1-1 TDD	10296	1/0	FLOOR((TB_size– 96)/8)	1275/0
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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test.

8.7.2.1_2.5 Test requirement

The requirements are specified in Table 8.7.2.1_2.5-1 depending on the UE category according to Table 8.7.2.1_2.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.1.1_2.5-1: Test Requirements (FDD)

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
1A	10296	R.31-1 FDD	95
1B	10296	R.31-1A FDD	95

Table 8.7.2.1_2.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
1A	10	1	1×1	N/A	0	0	0	-85	Bundling	OP.6 TDD
1B	20	1	1×1	N/A	0	0	0	-85	Bundling	OP.6 TDD

Table 8.7.2.1_2.5-3: Test applicability per UE category

Config	Maximum supported Bandwidth (MHz)	Category 1	Category 1bis	Category 2	Category 3	Category 4	Category 6	Category 7
Single carrier	10	–	1A	–	–	–	–	–
Single carrier	20	–	1B	–	–	–	–	–
Note 1: Test is selected for maximum supported bandwidth.

8.7.2.1_A TDD sustained data rate performance for CA

8.7.2.1_A.1 TDD sustained data rate performance for CA (2DL CA)

8.7.2.1_A.1.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.2.1_A.1.2 Test applicability

This test applies to E-UTRA TDD release 10 and forward UEs of category 6, 7, 9 and 10 which support inter-band DL CA OR intra‑band contiguous DL CA and not support 256QAM in DL.

This test also applies to E-UTRA TDD release 11 and forward UEs of category6, 7, 9 and 10 which support intra band non-contiguous DL CA and not support 256QAM in DL.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_A.1.3 Minimum requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.2.1_A.1.3-3, with the addition of the parameters in Table 8.7.2.1_A.1.3-2 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_A.1.3-4. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.1.3-1: Void

Table 8.7.2.1_A.1.3-2: Test parameters for sustained downlink data rate for CA (TDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
3	20	3	2 x 2	10	-3	-3	0	-85	Bundling	OP.1 TDD
4	20	3	2 x 2	10	-3	-3	0	-85	Multiplexing	OP.1 TDD
6A	2×20	3	2 x 2	10	-3	-3	0	-85	– (Note 1)	OP.1 TDD
6B	20+15	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK.

Table 8.7.2.1_A.1.3-3: Minimum requirement for CA (TDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
3	51024/0	R31-3 TDD	95
4	75376/0 (Note 2)	R31-4 TDD	85
6A	75376/0 (Note 2)	R.31-4 TDD	85
6B	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.1.3-4: Test points for sustained data rate for CA (FRC 64QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat 11, 12
CA with 2CCs	20+20	–	—	3(Note 4)	4 (Note 4)	6A	6A	–
		15+20	–	–	3(Note 4)	4 (Note 4)	6B	6B	–
Note 1: Void. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

The normative reference for this requirement is TS 36.101[2] clause 8.7.2

8.7.2.1_A.1.4 Test description

8.7.2.1_A.1.4.1 Initial conditions

Table 8.7.2.1_A.1.4.1-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TB_size per Codeword per Component Carrier

Number of PDCP SDU per Codeword for normal/special sub-frame

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]
for normal/special sub-frame

R.31-4 TDD

R.1-4 TDD

75376
(Note 3)

7/0

FLOOR((TB_size– 264)/56))

1341/0

R.31-5 TDD

for 15MHz CC

R.31-4 TDD for 20MHz CC

R.1-4 TDD

55056/0 for 15MHz CC

75376/0 for 20MHz CC (Note 3)

6 for 15MHz CC

7 for 20 MHz CC

FLOOR((TB_size– 240)/48) for 15 MHz CC

FLOOR((TBsize – 264)/56) for 20 MHz CC

1142 for 15MHz CC

1341 for 20MHz CC

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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers.

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).

The PDCP SDU size of each PDCP SDU is:

PDCP SDU size = (TBsize – N*PDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N,

where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)*12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CEIL((16+(N-1)*12)/8) – 64)/(8*N)) bits.

The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test.

Note 3: 71112 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: Maximum WGap for Intra-band non-contiguous CA, otherwise Mid Range as defined in TS 36.508 [7] clause 4.3.1.2.

Channel Bandwidths to be tested: according to Table 8.7.2.1_A.1.5-2 depending on the UE category according to Table 8.7.2.1_A.1.5-3.

1. Connect the SS to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure group A.36 (without using faders and AWGN generators) for UE supporting only 2Rx RF bands on all CC. Annex A, Figure A.85 for UE supporting 4Rx RF band on any of the CC.

2. The parameter settings for the cell are set up according to Table 8.7.2.1_A.1.5-2 and Table 8.7.2.1_A.1.5-1 depending on the UE category according to Table 8.7.2.1_A.1.5-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/4.5.4.5. Message contents are defined in clause 8.7.2.1_A.1.4.3.

8.7.2.1_A.1.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.2.1_A.1.4.3-1, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.2.1_A.1.4.3-1A.

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. The SS looks up TB_size in Table 8.7.2.1_A.1.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.2.1_A.1.5-3.

6. SS sets the counters N_{DL_newtx},N_{DL_retx}, N_{UL_PDCP}, and ND_{DL_PDCP} to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.2.1_A.1.4.1-1 (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 N_{DL_newtx} by one and N_{DL_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 N_{DL_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 N_{UL_PDCP} by one

11. The SS calculates the TB success rate as A = 100%*N_{DL_newtx}/ (N_{DL_newtx} + N_{DL_retx}). Measurements are not based on UE feedback but on SS counters instead (N_{DL_newtx} and N_{DL_retx}) in order to validate HARQ feedback received from the UE.

11. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP}

12. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.2.1_A.1.5-1" 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.2.1_A.1.4.3 Message contents

Same message contents as in clause 8.7.2.1.4.3 with the following exceptions:

Table 8.7.2.1_A.1.4.3-1: 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		Transmission mode 3
codebookSubsetRestriction CHOICE {
n2TxAntenna-tm3	10
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

Table 8.7.2.1_A.1.4.3-1A: 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
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.2.1_A.1.5 Test requirement

The requirements are specified in Table 8.7.2.1_A.1.5-1 depending on the UE category according to Table 8.7.2.1_A.1.5-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.1.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
6A	75376/0 (Note 2)	R.31-4 TDD	85
6B	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.1.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
6A	2×20	3	2 x 2	10	-3	-3	0	-85	– (Note 1)	OP.1 TDD
6B	20+15	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK.

Table 8.7.2.1_A.1.5-3: Test applicability per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat 11, 12
CA with 2CCs	20+20	–	—	3(Note 4)	4 (Note 4)	6A	6A	–
CA with 2CCs	15+20	–	–	3(Note 4)	4 (Note 4)	6B	6B	–
Note 1: Void. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities. Only one test point to be tested.

8.7.2.1_A.2 TDD Sustained data rate performance for CA (3DL CA)

8.7.2.1_A.2.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.2.1_A.2.2 Test applicability

This test case applies to all types of E-UTRA TDD UE release 10 and forward of UE category 9, 10, 11 and 12 that support 3DL with CA configurations in Table 7.1-2a and not support 256QAM in DL. This test case also applies to all types of E-UTRA TDD UE release 11 and forward of UE category 9, 10, 11 and 12 that support 3DL with CA configurations in Table 7.1-2a and not support 256QAM in DL.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_A.2.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.2.1_A.2.3-2, with the addition of the parameters in Table 8.7.2.1_A.2.3-1 and the downlink physical channel setup according to Table C.3.2-1 in Annex C. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_A.2.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.2.3-1: test parameters for sustained downlink data rate (TDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
6A	2×20	3	2 x 2	10	-3	-3	0	-85	– (Note 1)	OP.1 TDD
7	3×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
7A	15+20+20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.2.3-2: Minimum requirement (TDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
6A	75376/0 (Note 2)	R.31-4 TDD	85
7	75376/0 (Note 2)	R.31-4 TDD	85
7A	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.2.3-3: Test points for sustained data rate (FRC 64QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat 11, 12
CA with 3 CCs	3×20	–	–	–	–	6A	7	7
CA with 3 CCs	15+20+20	–	–	–	–	6A	7A	7A
Note 1: Void. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_A.2.4 Test description

8.7.2.1_A.2.4.1 Initial conditions

Table 8.7.2.1_A.2.4.1-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TBsize per Codeword per Component Carrier	Number of PDCP SDU per Codeword	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
6A	R.31-4 TDD for two 20MHz CCs	R.1-4 TDD	75376 (Note 3)	7 for two 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for two 20MHz CCs
7	R.31-4 TDD for three 20MHz CCs	R.1-4 TDD	75376 (Note 3)	7 for three 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for three 20MHz CCs
7A	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	R.1-4 TDD	55056 for 15MHz CC 75376 (Note 3) for 20MHz CC	6 for 15MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 240)/48) for 15 MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1142 for 15MHz CC 1341 for 20MHz CC
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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. 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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 71112 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: Maximum WGap for Intra-band non-contiguous CA, otherwise Mid Range as defined in TS 36.508 [7] clause 4.3.1.2.

Channel Bandwidths to be tested: according to Table 8.7.2.1_A.5-2 depending on the UE category according to Table 8.7.2.1_A.2.5-3.

1. Connect the SS to the UE antenna connector(s) as shown in TS 36.508 [7] Annex A, Figure group A.60 (without using faders and AWGN generators) for UE supporting only 2Rx RF bands on all CC. Annex A, Figure A.85 for UE supporting 4Rx RF band on any of the CC.

2. The parameter settings for the cell are set up according to Table 8.7.2-1 and Table 8.7.2.1_A.2.5-1 depending on the UE category according to Table 8.7.2.1_A.2.5-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.2.1_A.2.4.3.

8.7.2.1_A.2.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.2 with two SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.2.1_A.2.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.2.1_A.2.4.3-3A.

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. The SS looks up TB_size in Table 8.7.2.1_A.2.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.2.1_A.2.5-3.

6. The SS sets the counters, N_{DL_newtx} ,N_{DL_retx}, N_{UL_PDCP}, and ND_{DL_PDCP} to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.2.1_A.2.4.1-1 (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 N_{DL_newtx} by one and N_{DL_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 N_{DL_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 N_{UL_PDCP} by one

12. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP}

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.2.1_A.2.5-1" 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.2.1_A.2.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.2.1_A.2.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A
Information Element	Value/remark	Comment	Condition
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

Table 8.7.2.1_A.2.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.2.1_A.2.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
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

Table 8.7.2.1_A.2.4.3-3A: 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
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.2.1_A.2.5 Test requirement

The requirements are specified in Table 8.7.2.1_A.2.5-1 depending on the UE category according to Table 8.7.2.1_A.2.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.2.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
7	75376/0 (Note 2)	R.31-4 TDD	85
7A	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.2.5-2: test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
7	3×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
7A	15+20+20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.2.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat 11, 12
CA with 3 CCs	3×20	–	–	–	–	6A	7	7
	15+20+20	–	–	–	–	6A	7A	7A
Note 1: Void. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: Void. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities. Note 7: Test 6A is tested in 8.7.2.1_A.1.

8.7.2.1_A.3 TDD Sustained data rate performance for CA (4DL CA)

8.7.2.1_A.3.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_A.3.2 Test applicability

This test case applies to all types of E-UTRA TDD UE release 11 and forward of UE DL category 11, 12 and 15 that support 4DL with CA configurations in Table 7.1-2b.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_A.3.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.2.1_A.3.3-2, with the addition of the parameters in Table 8.7.2.1_A.3.3-1 and the downlink physical channel setup according to Table C.3.2-1 in Annex C. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_A.3.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.3.3-1: test parameters for sustained downlink data rate (TDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
7	3×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
8	4×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
9	15+3×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.3.3-2: Minimum requirement (TDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
7	75376/0 (Note 2)	R.31-4 TDD	85
8	75376/0 (Note 2)	R.31-4 TDD	85
9	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.3.3-3: Test points for sustained data rate (FRC 64QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 4 CCs	4×20	–	–	–	–	–	7	8	8
	15+3×20	–	–	–	–	–	7	9	9
Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_A.3.4 Test description

8.7.2.1_A.3.4.1 Initial conditions

Table 8.7.2.1_A.3.4.1-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TBsize per Codeword per Component Carrier	Number of PDCP SDU per Codeword	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
7	R.31-4 TDD for three 20MHz CCs	R.1-4 TDD	75376 (Note 3)	7 for three 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for three 20MHz CCs
8	R.31-4 TDD for four 20MHz CCs	R.1-4 TDD	75376 (Note 3)	7 for four 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for four 20MHz CCs
9	R.31-5 TDD for 15MHz CC R.31-4 TDD for three 20MHz CC	R.1-4 TDD	55056 for 15MHz CC 75376 (Note 3) for 20MHz CC	6 for 15MHz CC 7 for three 20 MHz CC	FLOOR((TB_size– 240)/48) for 15 MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1142 for 15MHz CC 1341 for three 20MHz CC
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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. 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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 71112 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: 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.2.1_A.3.5-2 depending on the UE category according to Table 8.7.2.1_A.3.5-3.

2. The parameter settings for the cell are set up according to Table 8.7.1-1 and Table 8.7.2.1_A.3.5-1 depending on the UE category according to Table 8.7.2.1_A.3.5-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.2.1_A.3.4.3.

8.7.2.1_A.3.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 five SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.2.1_A.3.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.2.1_A.3.4.3-3A.

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. The SS looks up TB_size in Table 8.7.2.1_A.3.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.2.1_A.3.5-3.

6. The SS sets the counters, N_{DL_newtx} ,N_{DL_retx}, N_{UL_PDCP}, and ND_{DL_PDCP} to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.2.1_A.3.4.1-1 (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 N_{DL_newtx} by one and N_{DL_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 N_{DL_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 N_{UL_PDCP} by one

12. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP}

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.2.1_A.3.5-1" 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.2.1_A.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.2.1_A.3.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A
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

Table 8.7.2.1_A.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.2.1_A.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
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

Table 8.7.2.1_A.3.4.3-3A: 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
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.2.1_A.3.5 Test requirement

The requirements are specified in Table 8.7.2.1_A.3.5-1 depending on the UE category according to Table 8.7.2.1_A.3.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.3.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
7	75376/0 (Note 2)	R.31-4 TDD	85
8	75376/0 (Note 2)	R.31-4 TDD	85
9	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.3.5-2: test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
7	3×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
8	4×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
9	15+3×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.3.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 4 CCs	4×20	–	–	–	–	–	7	8	8
	15+3×20	–	–	–	–	–	7	9	9
Note 1: Void. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: Void. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities. Note 7: Test 7 is tested in 8.7.2.1_A.2.

8.7.2.1_A.4 Void

8.7.2.1_A.5 TDD Sustained data rate performance for CA (5DL CA)

8.7.2.1_A.5.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_A.5.2 Test applicability

This test case applies to all types of E-UTRA TDD UE and forward of UE DL category 11, 12 and 15 that support 5DL with CA configurations in Table 7.1-2c.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_A.5.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.2.1_A.5.3-2, with the addition of the parameters in Table 8.7.2.1_A.5.3-1 and the downlink physical channel setup according to Table C.3.2-1 in Annex C. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_A.5.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.5.3-1: Test parameters for sustained downlink data rate (TDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
10	5×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
11	15+4×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.5.3-2: Minimum requirement (TDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
10	75376/0 (Note 2)	R.31-4 TDD	85
11	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.5.3-3: Test points for sustained data rate (FRC 64QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 5 CCs	5×20
	15+4×20
Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_A.5.4 Test description

8.7.2.1_A.5.4.1 Initial conditions

Table 8.7.2.1_A.5.4.1-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TBsize per Codeword per Component Carrier	Number of PDCP SDU per Codeword	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
10	R.31-4 TDD for five 20MHz CCs	R.1-4 TDD	75376 (Note 3)	7 for five 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for four 20MHz CCs
11	R.31-5 TDD for 15MHz CC R.31-4 TDD for four 20MHz CCs	R.1-4 TDD	55056 for 15MHz CC 75376 (Note 3) for 20MHz CC	6 for 15MHz CC 7 for four 20 MHz CCs	FLOOR((TB_size– 240)/48) for 15 MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1142 for 15MHz CC 1341 for four 20MHz CCs
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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. 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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 71112 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: 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.2.1_A.5.5-2 depending on the UE category according to Table 8.7.2.1_A.5.5-3.

2. The parameter settings for the cell are set up according to Table 8.7.1-1 and Table 8.7.2.1_A.5.5-1 depending on the UE category according to Table 8.7.2.1_A.5.5-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.2.1_A.5.4.3.

8.7.2.1_A.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 four SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.2.1_A.5.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.2.1_A.5.4.3-3A.

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. The SS looks up TB_size in Table 8.7.2.1_A.5.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.2.1_A.5.5-3.

6. The SS sets the counters, N_{DL_newtx} ,N_{DL_retx}, N_{UL_PDCP}, and ND_{DL_PDCP} to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.2.1_A.5.4.1-1 (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 N_{DL_newtx} by one and N_{DL_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 N_{DL_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 N_{UL_PDCP} by one

12. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP}

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.2.1_A.5.5-1" 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.2.1_A.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.2.1_A.5.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.508 clause 4.7A Table 4.7A-3 with condition UE TEST LOOP MODE A
Information Element	Value/remark	Comment	Condition
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

Table 8.7.2.1_A.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.2.1_A.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
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

Table 8.7.2.1_A.5.4.3-3A: 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
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.2.1_A.5.5 Test requirement

The requirements are specified in Table 8.7.2.1_A.5.5-1 depending on the UE category according to Table 8.7.2.1_A.5.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.5.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
10	75376/0 (Note 2)	R.31-4 TDD	85
11	55056/0 for 15MHz CC 75376/0 for 20MHz CC (Note 2)	R.31-5 TDD for 15MHz CC R.31-4 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.5.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
10	5×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
11	15+4×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.5.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 5 CCs	5×20	–	–	–	–	–
	15+4×20	–	–	–	–	–
Note 1: Void. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: Void. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities. Note 7: Test 7 is tested in 8.7.2.1_A.2.

8.7.2.1_A.6 TDD Sustained data rate performance for CA (6DL CA)

8.7.2.1_A.6.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_A.6.2 Test applicability

This test case applies to all types of E-UTRA TDD UE and forward of UE DL category 11, 12 and 15 that support 6DL with CA configurations in Table 7.1-2d.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_A.6.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.2.1_A.6.3-2, with the addition of the parameters in Table 8.7.2.1_A.6.3-1 and the downlink physical channel setup according to Table C.3.2-1 in Annex C. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_A.6.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.6.3-1: Test parameters for sustained downlink data rate (TDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
12	6×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.6.3-2: Minimum requirement (TDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
			TB success rate [%]
12	75376/0 (Note 2)	R.31-4 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.6.3-3: Test points for sustained data rate (FRC 64QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 6 CCs	6×20							12	12
Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_A.6.4 Test description

8.7.2.1_A.6.4.1 Initial conditions

Table 8.7.2.1_A.6.4.1-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TBsize per Codeword per Component Carrier

Number of PDCP SDU per Codeword

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]

R.31-4 TDD for six 20MHz CCs

R.1-4 TDD

75376
(Note 3)

7 for six 20MHz CCs

FLOOR((TBsize – 264)/56) for 20 MHz CC

1341 for six 20MHz CCs

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).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – N*PDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N,
where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)*12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8*FLOOR((TBsize – N*16- 8*CEIL((16+(N-1)*12)/8) – 64)/(8*N)) bits.
The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test.

Note 3: 71112 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: 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.2.1_A.6.5-2 depending on the UE category according to Table 8.7.2.1_A.6.5-3.

2. The parameter settings for the cell are set up according to Table 8.7.1-1 and Table 8.7.2.1_A.6.5-1 depending on the UE category according to Table 8.7.2.1_A.6.5-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.2.1_A.6.4.3.

8.7.2.1_A.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.2.1_A.6.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.2.1_A.6.4.3-3A.

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. The SS looks up TB_size in Table 8.7.2.1_A.6.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.2.1_A.6.5-3.

6. The SS sets the counters, N_{DL_newtx} ,N_{DL_retx}, N_{UL_PDCP}, and ND_{DL_PDCP} to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.2.1_A.6.4.1-1 (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 N_{DL_newtx} by one and N_{DL_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 N_{DL_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 N_{UL_PDCP} by one

12. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP}

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.2.1_A.6.5-1" 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.2.1_A.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.2.1_A.6.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.508 clause 4.7A Table 4.7A-3 with condition UE TEST LOOP MODE A
Information Element	Value/remark	Comment	Condition
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

Table 8.7.2.1_A.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.2.1_A.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
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

Table 8.7.2.1_A.6.4.3-3A: 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
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.2.1_A.6.5 Test requirement

The requirements are specified in Table 8.7.2.1_A.6.5-1 depending on the UE category according to Table 8.7.2.1_A.6.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.6.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
			TB success rate [%]
12	75376/0 (Note 2)	R.31-4 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.6.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
12	6×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.6.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 6 CCs	6×20							12	12
Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

8.7.2.1_A.7 TDD Sustained data rate performance for CA (7DL CA)

8.7.2.1_A.7.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_A.7.2 Test applicability

This test case applies to all types of E-UTRA TDD UE release and forward of UE DL category 11, 12 and 15 that support 7DL CA.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_A.7.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.2.1_A.7.3-2, with the addition of the parameters in Table 8.7.2.1_A.7.3-1 and the downlink physical channel setup according to Table C.3.2-1 in Annex C. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_A.7.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.7.3-1: Test parameters for sustained downlink data rate (TDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
13	7×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.7.3-2: Minimum requirement (TDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
			TB success rate [%]
13	75376/0 (Note 2)	R.31-4 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.7.3-3: Test points for sustained data rate (FRC 64QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 7 CCs	7×20							13	13
Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_A.7.4 Test description

8.7.2.1_A.7.4.1 Initial conditions

Table 8.7.2.1_A.7.4.1-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TBsize per Codeword per Component Carrier

Number of PDCP SDU per Codeword

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]

R.31-4 TDD for seven 20MHz CCs

R.1-4 TDD

75376
(Note 3)

7 for seven 20MHz CCs

FLOOR((TBsize – 264)/56) for 20 MHz CC

1341 for seven 20MHz CCs

Note 3: 71112 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: 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.2.1_A.7.5-2 depending on the UE category according to Table 8.7.2.1_A.7.5-3.

2. The parameter settings for the cell are set up according to Table 8.7.1-1 and Table 8.7.2.1_A.7.5-1 depending on the UE category according to Table 8.7.2.1_A.7.5-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.2.1_A.7.4.3.

8.7.2.1_A.7.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.2.1_A.7.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.2.1_A.7.4.3-3A.

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. The SS looks up TB_size in Table 8.7.2.1_A.7.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.2.1_A.7.5-3.

6. The SS sets the counters, N_{DL_newtx} ,N_{DL_retx}, N_{UL_PDCP}, and ND_{DL_PDCP} to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.2.1_A.7.4.1-1 (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 N_{DL_newtx} by one and N_{DL_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 N_{DL_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 N_{UL_PDCP} by one

12. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP}

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.2.1_A.7.5-1" 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.2.1_A.7.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.2.1_A.7.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.508 clause 4.7A Table 4.7A-3 with condition UE TEST LOOP MODE A
Information Element	Value/remark	Comment	Condition
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

Table 8.7.2.1_A.7.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.2.1_A.7.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
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

Table 8.7.2.1_A.7.4.3-3A: 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
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.2.1_A.7.5 Test requirement

The requirements are specified in Table 8.7.2.1_A.7.5-1 depending on the UE category according to Table 8.7.2.1_A.7.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_A.7.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame	Measurement channel	Reference value
			TB success rate [%]
13	75376/0 (Note 2)	R.31-4 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 71112 bits for sub-frame 5. Note 3: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_A.7.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
13	7×20	3	2 x 2	10	-3	-3	0	-85	(Note 2)	OP.1 TDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK. Note 2: PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_A.7.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9, 10	Cat. 11, 12	DL Cat. 15
								DL Cat. 11, 12
CA with 7 CCs	7×20							13	13
Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled. Note 2: For non-CA UE, test is selected for maximum supported bandwidth. Note 3: Void. Note 4: If the intra-band contiguous CA is the only CA configuration supported by category 3 or 4 UE, single carrier test is selected. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3.

8.7.2.1_H TDD sustained data rate performance for 256QAM in DL

Editor’s notes:

– Discussion on DL EVM for 256QAM demodulation test as per R5-155895 is still ongoing

– Whether UL modulation mode QPSK is suitable to use is FFS

8.7.2.1_H.1 TDD sustained data rate performance for 256QAM in DL (Single Carrier)

8.7.2.1_H.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 number of DL-SCH transport block bits received within a TTI for the UE category indicated. 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. The size of the TB per TTI corresponds to the largest possible DL-SCH transport block for each UE category using the maximum number of layers for spatial multiplexing. Transmission mode 3 is used with radio conditions resembling a scenario where sustained maximum data rates are available.

8.7.2.1_H.1.2 Test applicability

This test applies to E-UTRA TDD UE release 12 and forward UE DL category 13 that support 256QAM in DL.

8.7.2.1_H.1.3 Minimum requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.2-2, with the addition of the parameters in Table 8.7.2-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2-3. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2.1_A.4.3-2 is not applicable.

Table 8.7.2.1_H.1.3-1: test parameters for sustained downlink data rate (TDD 256QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
1	20	3	2 x 2	10	-3	-3	0	-85	Bundling	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.1.3-2: Minimum requirement (TDD 256QAM)

Test	Measurement channel	Reference value
		TB success rate [%]
1	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.1.3-3: Test points for sustained data rate (FRC 256QAM)

CA config

Bandwidth/ Bandwidth combination

(MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 11, 12

Single carrier

–

The normative reference for this requirement is TS 36.101[2] clause 8.7.2

8.7.2.1_H.1.4 Test description

Same test description as in clause 8.7.2.1.4 with the following exceptions:

– Connection diagram Figure A.10 (without using faders and AWGN generators).

– Instead of Table 8.7.2.1.4.1-1 ‑> use Table 8.7.2.1_H.1.4-1.

– Instead of Table 8.7.2.1.5-1 ‑> use Table 8.7.2.1_H.1.5-1.

– Instead of Table 8.7.2.1.5-2 ‑> use Table 8.7.2.1_H.1.5-2.

– Instead of Table 8.7.2.1.5-3 -> use Table 8.7.2.1_H.1.5-3.

Table 8.7.2.1_H.1.4-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement Channel

TB_size per Codeword

Number of PDCP SDU per Codeword for normal/special sub-frame

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]
for normal/special sub-frame

R.68 TDD

R.1-4 TDD

97896(Note 3)

10/0

FLOOR((TB_size– 352)/80)

1219/0

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).

The PDCP SDU size of each PDCP SDU is:

PDCP SDU size = (TBsize – N*PDCP header size – AMD PDU header size – MAC header size – Size of Timing Advance – Size of RLC STATUS PDU) / N,

Note 3: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

8.7.2.1_H.1.5 Test requirement

The requirements are specified in Table 8.7.2.1_H.1.5-1 depending on the UE category according to Table 8.7.2.1_H.1.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_H.1.5-1: Test requirements per test

Test	Measurement channel	Reference value
		TB success rate [%]
1	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.1.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
1	20	3	2 x 2	10	-3	-3	0	-85	Bundling	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.1.5-3: Test applicability per UE category

CA config

Bandwidth/ Bandwidth combination

(MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 11, 12

Single carrier

–

8.7.2.1_H.2 TDD sustained data rate performance for CA (2DL CA) for 256QAM in DL

8.7.2.1_H.2.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.2.1_H.2.2 Test applicability

This test applies to E-UTRA TDD UE release 12 and forward and UE DL category 11, 12 and 13 that support 256QAM in DL and 2DL CA.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_H.2.3 Minimum requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.2.1_H.2.3-2, with the addition of the parameters in Table 8.7.2.1_H.2.3-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_H.2.3-3. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2.1_A.1.3-3 is not applicable.

Table 8.7.2.1_H.2.3-1: test parameters for sustained downlink data rate (TDD 256QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
2	15+20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
3	2×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.2.3-2: Minimum requirement (TDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
2	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
3	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.2.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13
		DL Cat. 11, 12
CA with 2CCs	15+20	2	2
	2×20	3	3

The normative reference for this requirement is TS 36.101[2] clause 8.7.2

8.7.2.1_H.2.4 Test description

Same test description as in clause 8.7.2.1_A.1.4 with the following exceptions:

– Instead of Table 8.7.2.1_A.1.4.1-1 ‑> use Table 8.7.2.1_H.2.4-1.

– Instead of Table 8.7.2.1_A.1.5-1 ‑> use Table 8.7.2.1_H.2.5-1.

– Instead of Table 8.7.2.1_A.1.5-2 ‑> use Table 8.7.2.1_H.2.5-2.

– Instead of Table 8.7.2.1_A.1.5-3 -> use Table 8.7.2.1_H.2.5-3.

Table 8.7.2.1_H.2.4-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TB_size per Codeword per Component Carrier	Number of PDCP SDU per Codeword for normal/special sub-frame	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets] for normal/special sub-frame
2	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	R.1-4 TDD	75376 (Note 4) for 15MHz CC 97896(Note 3) for 20MHz CC	7/0 for 15MHz CC 10/0 for 20MHz CC	FLOOR((TB_size– 264)/56)) for 15MHz CC FLOOR((TB_size– 352)/80) for 20MHz CC	1341/0 for 15MHz CC 1219/0 for 20MHz CC
3	R.68 TDD	R.1-4 TDD	97896(Note 3)	10/0	FLOOR((TB_size– 352)/80)	1219/0
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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. 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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5. Note 4: 63776 bits for sub-frame 0, 4 and 61664 bits for sub-frame 5.

8.7.2.1_H.2.5 Test requirement

The requirements are specified in Table 8.7.2.1_H.2.5-1 depending on the UE category according to Table 8.7.2.1_H.2.5-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_H.2.5-1: Test requirements per test

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
2	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
3	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.2.5-2: Test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
2	15+20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
3	2×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.2.5-3: Test applicability per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13
		DL Cat. 11, 12
CA with 2CCs	15+20	2	2
	2×20	3	3
Note 1: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 2: Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities. Only one test point to be tested.

8.7.2.1_H.3 TDD Sustained data rate performance for CA (3DL CA) for 256QAM in DL

8.7.2.1_H.3.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.2.1_H.3.2 Test applicability

This test case applies to all types of E-UTRA TDD UE release 12 and forward of UE DL category 11, 12 and 15 that support 256QAM in DL and 3DL CA.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_H.3.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.2.1_H.3.3-2, with the addition of the parameters in Table 8.7.2.1_H.3.3-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_H.3.3-3. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2.1_A.2.3-2 is not applicable.

Table 8.7.2.1_H.3.3-1: test parameters for sustained downlink data rate (TDD 256QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
4	3×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
5	15+20+20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.3.3-2: Minimum requirement (TDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
4	R.68 TDD	85
5	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.3.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15
		DL Cat. 11, 12
CA with 3 CCs	3×20	4	3	4
	15+20+20	5	3	5

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_H.3.4 Test description

Same test description as in clause 8.7.2.1_A.1.4 with the following exceptions:

– Instead of Table 8.7.2.1_A.2.4.1-1 ‑> use Table 8.7.2.1_H.3.4-1.

– Instead of Table 8.7.2.1_A.2.5-1 ‑> use Table 8.7.2.1_H.3.5-1.

– Instead of Table 8.7.2.1_A.2.5-2 ‑> use Table 8.7.2.1_H.3.5-2.

– Instead of Table 8.7.2.1_A.2.5-3 -> use Table 8.7.2.1_H.3.5-3.

Table 8.7.2.1_H.3.4-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TBsize per Codeword per Component Carrier	Number of PDCP SDU per Codeword	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
4	R.68 TDD	R.1-4 TDD	97896(Note 3)	10/0	FLOOR((TB_size– 352)/80)	1219/0
5	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	R.1-4 TDD	75376 (Note 4) for 15MHz CC 97896(Note 3) for 20MHz CC	7/0 for 15MHz CC 10/0 for 20MHz CC	FLOOR((TB_size– 264)/56)) for 15MHz CC FLOOR((TB_size– 352)/80) for 20MHz CC	1341/0 for 15MHz CC 1219/0 for 20MHz CC
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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. 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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5. Note 4: 63776 bits for sub-frame 0, 4 and 61664 bits for sub-frame 5.

8.7.2.1_H.3.5 Test requirement

The requirements are specified in Table 8.7.2.1_H.3.5-1 depending on the UE category according to Table 8.7.2.1_H.3.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_H.3.5-1: Minimum requirement

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
4	R.68 TDD	85
5	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.3.5-2: test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
4	3×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
5	15+20+20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.3.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15
		DL Cat. 11, 12
CA with 3 CCs	3×20	4	3	4
	15+20+20	5	3	5
Note 1: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 2: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities. Note 3: Test 3 is tested in 8.7.2.1_H.2.

8.7.2.1_H.4 TDD Sustained data rate performance for CA (4DL CA) for 256QAM in DL

8.7.2.1_H.4.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_H.4.2 Test applicability

This test case applies to all types of E-UTRA TDD UE and forward of UE DL category 11, 12, 15 and 16 that support 4DL with CA configurations in Table 7.1-2b and 256QAM in DL.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_H.4.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.2.1_H.4.3-2, with the addition of the parameters in Table 8.7.2.1_H.4.3-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_H.4.3-3, the TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2.1_A.3.3-2 is not applicable.

Table 8.7.2.1_H.4.3-1: test parameters for sustained downlink data rate (TDD 256QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
6	4×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
7	15+3×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.4.3-2: Minimum requirement (TDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
6	R.68 TDD	85
7	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.4.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
		DL Cat. 11, 12
CA with 4 CCs	4×20	4	–	6	6
	15+3×20	5	–	7	7

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_H.4.4 Test description

Same test description as in clause 8.7.2.1_A.3.4 with the following exceptions:

– Instead of Table 8.7.2.1_A.3.4.1-1 ‑> use Table 8.7.2.1_H.4.4-1.

– Instead of Table 8.7.2.1_A.3.5-1 ‑> use Table 8.7.2.1_H.4.5-1.

– Instead of Table 8.7.2.1_A.3.5-2 ‑> use Table 8.7.2.1_H.4.5-2.

– Instead of Table 8.7.2.1_A.3.5-3 -> use Table 8.7.2.1_H.4.5-3.

Table 8.7.2.1_H.4.4-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TBsize per Codeword per Component Carrier	Number of PDCP SDU per Codeword	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
6	R.68 TDD	R.1-4 TDD	97896 (Note 3) for 20MHz CC	10 for 20MHz CC	FLOOR((TB_size– 352)/80) for 20MHz CC	1219 for 20MHz CC
7	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	R.1-4 TDD	75376 (Note 4) for 15MHz CC 97896 (Note 3) for 20MHz CC	7 for 15MHz CC 10 for 20MHz CC	FLOOR((TBsize – 264)/56) for 15MHz CC FLOOR((TB_size– 352)/80) for 20MHz CC	1341 for 15MHz CC 1219 for 20MHz CC
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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. 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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 84760 bits for sub-frames 0,1,2,6,7 and 81176 bits for sub-frames 5. Note 4: 63776 bits for sub-frames 0,1,2,6,7 and 61664 bits for sub-frames 5. Note 5: 42368 bits for sub-frames 0,1,2,6,7 and 40576 bits for sub-frames 5. Note 6: 21384 bits for sub-frames 0,1,2,6,7 and 19848 bits for sub-frames 5.

8.7.2.1_H.4.5 Test requirement

The requirements are specified in Table 8.7.2.1_H.4.5-1 depending on the UE category according to Table 8.7.2.1_H.4.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_H.4.5-1: Minimum requirement

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
6	R.68 TDD	85
7	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.4.5-2: test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
6	4×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
7	15+3×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.4.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
		DL Cat. 11, 12
CA with 4 CCs	4×20	4	–	6	6
	15+3×20	5	–	7	7

8.7.2.1_H.5 TDD Sustained data rate performance for CA (5DL CA) for 256QAM in DL

8.7.2.1_H.5.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_H.5.2 Test applicability

This test case applies to all types of E-UTRA TDD UE and forward of UE DL category 16 that support 5DL with CA configurations in Table 7.1-2c and 256QAM in DL.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_H.5.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.2.1_H.5.3-2, with the addition of the parameters in Table 8.7.2.1_H.5.3-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_H.5.3-3, the TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2.1_A.5.3-2 is not applicable.

Table 8.7.2.1_H.5.3-1: test parameters for sustained downlink data rate (TDD 256QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
8	5×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
9	15+4×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.5.3-2: Minimum requirement (TDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
8	R.68 TDD	85
9	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.5.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
		DL Cat. 11, 12
CA with 5 CCs	5×20				8
	15+4×20				9

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_H.5.4 Test description

Same test description as in clause 8.7.2.1_A.5.4 with the following exceptions:

– Instead of Table 8.7.2.1_A.5.4.1-1 ‑> use Table 8.7.2.1_H.5.4-1.

– Instead of Table 8.7.2.1_A.5.5-1 ‑> use Table 8.7.2.1_H.5.5-1.

– Instead of Table 8.7.2.1_A.5.5-2 ‑> use Table 8.7.2.1_H.5.5-2.

– Instead of Table 8.7.2.1_A.5.5-3 -> use Table 8.7.2.1_H.5.5-3.

Table 8.7.2.1_H.5.4-1: Further test parameters per test

Test	DL Measurement channel	UL Measurement channel	TBsize per Codeword per Component Carrier	Number of PDCP SDU per Codeword	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
8	R.68 TDD	R.1-4 TDD	97896 (Note 3) for 20MHz CC	10 for 20MHz CC	FLOOR((TB_size– 352)/80) for 20MHz CC	1219 for 20MHz CC
9	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	R.1-4 TDD	75376 (Note 4) for 15MHz CC 97896 (Note 3) for 20MHz CC	7 for 15MHz CC 10 for 20MHz CC	FLOOR((TBsize – 264)/56) for 15MHz CC FLOOR((TB_size– 352)/80) for 20MHz CC	1341 for 15MHz CC 1219 for 20MHz CC
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. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. 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). The PDCP SDU size of each PDCP SDU is: PDCP SDU size = (TBsize – NPDCP header size – AMD PDU header size – MAC header size – Size of RLC STATUS PDU) / N, where PDCP header size is 16 bits for the RLC AM and 12-bit SN case; AMD PDU header size is CEIL[(16+(N-1)12)/8] bytes which includes 16 bit standard AM header and (N-1) Length indicators; and MAC header size = R/R/E/LCID/F/L MAC subheader (24 bits for MAC SDU for RLC STATUS PDU with 15 bit LI) + R/R/E/LCID MAC subheader (8 bits for MAC SDU for RLC Data PDU) = 32 bits. The size of RLC STATUS PDU including one ACK_SN field and one NACK_SN field is 32 bits (if no STATUS PDU is sent or if the size of the STATUS PDU is less than 32 bits then padding will be used to fill the 32 bits). This gives: PDCP SDU size = 8FLOOR((TBsize – N16- 8CEIL((16+(N-1)12)/8) – 64)/(8*N)) bits. The calculation of PDCP SDU sizes does not consider timing advance MAC CE as timing advance is not transmitted by SS for RF test cases, and the header sizes are informative and may vary during the test. Note 3: 84760 bits for sub-frames 0,1,2,6,7 and 81176 bits for sub-frames 5. Note 4: 63776 bits for sub-frames 0,1,2,6,7 and 61664 bits for sub-frames 5. Note 5: 42368 bits for sub-frames 0,1,2,6,7 and 40576 bits for sub-frames 5. Note 6: 21384 bits for sub-frames 0,1,2,6,7 and 19848 bits for sub-frames 5.

8.7.2.1_H.5.5 Test requirement

The requirements are specified in Table 8.7.2.1_H.5.5-1 depending on the UE category according to Table 8.7.2.1_H.5.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_H.5.5-1: Minimum requirement

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
8	R.68 TDD	85
9	R.68-1 TDD for 15MHz CC R.68 TDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.5.5-2: test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
8	5×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
9	15+4×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.5.5-3: Test points per UE category

CA config	Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
		DL Cat. 11, 12
CA with 5 CCs	5×20				8
	15+4×20				9

8.7.2.1_H.6 TDD Sustained data rate performance for CA (6DL CA) for 256QAM in DL

8.7.2.1_H.6.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_H.6.2 Test applicability

This test case applies to all types of E-UTRA TDD UE and forward of UE DL category 16 that support 6DL with CA configurations in Table 7.1-2d and 256QAM in DL.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_H.6.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.2.1_H.6.3-2, with the addition of the parameters in Table 8.7.2.1_H.6.3-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_H.6.3-3, the TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2.1_A.5.3-2 is not applicable.

Table 8.7.2.1_H.6.3-1: test parameters for sustained downlink data rate (TDD 256QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
10	6×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.6.3-2: Minimum requirement (TDD 256QAM)

Test	Measurement channel	Reference value
		TB success rate [%]
10	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.6.3-3: Test points for sustained data rate (FRC 256QAM)

CA config

Bandwidth/ Bandwidth combination

(MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

DL Cat. 11, 12

CA with 6 CCs

6×20

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_H.6.4 Test description

Same test description as in clause 8.7.2.1_A.5.4 with the following exceptions:

– Instead of Table 8.7.2.1_A.5.4.1-1 ‑> use Table 8.7.2.1_H.6.4-1.

– Instead of Table 8.7.2.1_A.5.5-1 ‑> use Table 8.7.2.1_H.6.5-1.

– Instead of Table 8.7.2.1_A.5.5-2 ‑> use Table 8.7.2.1_H.6.5-2.

– Instead of Table 8.7.2.1_A.5.5-3 -> use Table 8.7.2.1_H.6.5-3.

Table 8.7.2.1_H.6.4-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TBsize per Codeword per Component Carrier

Number of PDCP SDU per Codeword

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]

R.68 TDD

R.1-4 TDD

97896 (Note 3) for 20MHz CC

10 for 20MHz CC

FLOOR((TB_size– 352)/80) for 20MHz CC

1219 for 20MHz CC

Note 3: 84760 bits for sub-frames 0,1,2,6,7 and 81176 bits for sub-frames 5.

Note 4: 63776 bits for sub-frames 0,1,2,6,7 and 61664 bits for sub-frames 5.

Note 5: 42368 bits for sub-frames 0,1,2,6,7 and 40576 bits for sub-frames 5.

Note 6: 21384 bits for sub-frames 0,1,2,6,7 and 19848 bits for sub-frames 5.

8.7.2.1_H.6.5 Test requirement

The requirements are specified in Table 8.7.2.1_H.6.5-1 depending on the UE category according to Table 8.7.2.1_H.6.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_H.6.5-1: Minimum requirement

Test	Measurement channel	Reference value
		TB success rate [%]
10	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.6.5-2: test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
10	6×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.6.5-3: Test points per UE category

CA config

Bandwidth/ Bandwidth combination

(MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

DL Cat. 11, 12

CA with 6 CCs

6×20

8.7.2.1_H.7 TDD Sustained data rate performance for CA (7DL CA) for 256QAM in DL

8.7.2.1_H.7.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.2.1_H.7.2 Test applicability

This test case applies to all types of E-UTRA TDD UE release and forward of UE DL category 16 that support 7DL CA and 256QAM in DL.

Note: This test also applies to UE supporting 4Rx antenna ports.

8.7.2.1_H.7.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.2.1_H.7.3-2, with the addition of the parameters in Table 8.7.2.1_H.7.3-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.2.1_H.7.3-3, the TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2.1_A.7.3-2 is not applicable.

Table 8.7.2.1_H.7.3-1: test parameters for sustained downlink data rate (TDD 256QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
11	7×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.7.3-2: Minimum requirement (TDD 256QAM)

Test	Measurement channel	Reference value
		TB success rate [%]
11	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.7.3-3: Test points for sustained data rate (FRC 256QAM)

CA config

Bandwidth/ Bandwidth combination

(MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

DL Cat. 11, 12

CA with 7 CCs

7×20

The normative reference for this requirement is TS 36.101 [2] clause 8.7.2.

8.7.2.1_H.7.4 Test description

Same test description as in clause 8.7.2.1_A.5.4 with the following exceptions:

– Instead of Table 8.7.2.1_A.5.4.1-1 ‑> use Table 8.7.2.1_H.7.4-1.

– Instead of Table 8.7.2.1_A.5.5-1 ‑> use Table 8.7.2.1_H.7.5-1.

– Instead of Table 8.7.2.1_A.5.5-2 ‑> use Table 8.7.2.1_H.7.5-2.

– Instead of Table 8.7.2.1_A.5.5-3 -> use Table 8.7.2.1_H.7.5-3.

Table 8.7.2.1_H.7.4-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TBsize per Codeword per Component Carrier

Number of PDCP SDU per Codeword

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]

R.68 TDD

R.1-4 TDD

97896 (Note 3) for 20MHz CC

10 for 20MHz CC

FLOOR((TB_size– 352)/80) for 20MHz CC

1219 for 20MHz CC

Note 3: 84760 bits for sub-frames 0,1,2,6,7 and 81176 bits for sub-frames 5.

Note 4: 63776 bits for sub-frames 0,1,2,6,7 and 61664 bits for sub-frames 5.

Note 5: 42368 bits for sub-frames 0,1,2,6,7 and 40576 bits for sub-frames 5.

Note 6: 21384 bits for sub-frames 0,1,2,6,7 and 19848 bits for sub-frames 5.

8.7.2.1_H.7.5 Test requirement

The requirements are specified in Table 8.7.2.1_H.7.5-1 depending on the UE category according to Table 8.7.2.1_H.7.5-3. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.2.1_H.7.5-1: Minimum requirement

Test	Measurement channel	Reference value
		TB success rate [%]
11	R.68 TDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: The TB success rate is defined as TB success rate = 100%*N_{DL_correct_rx}/ (N_{DL_newtx} + N_{DL_retx}), where N_{DL_newtx}is the number of newly transmitted DL transport blocks, N_{DL_retx} is the number of retransmitted DL transport blocks, and N_{DL_correct_rx}is the number of correctly received DL transport blocks.

Table 8.7.2.1_H.7.5-2: test parameters per test

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	ACK/NACK feedback mode	Symbols for unused PRBs
							σ
11	7×20	3	2 x 2	10	-3	-3	0	-85	(Note 1)	OP.1 TDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

Table 8.7.2.1_H.7.5-3: Test points per UE category

CA config

Bandwidth/ Bandwidth combination

(MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

DL Cat. 11, 12

CA with 7 CCs

7×20