8.7.1 FDD

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.1-1 are valid for all FDD tests unless otherwise stated.

Table 8.7.1-1: Common Test Parameters (FDD)

Parameter	Unit	Value
Cyclic prefix		Normal
Cell ID		0 (Note 1)
Inter-TTI Distance		1
Number of HARQ processes	Processes	Downlink: 8 Uplink: 8
Maximum number of HARQ transmission		Downlink: 4 Uplink: 1
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.
Redundancy version coding sequence		{0,0,1,2} for 64QAM and 256QAM
Number of OFDM symbols for PDCCH	OFDM symbols	1
Cross carrier scheduling		Not configured
Propagation condition		Static propagation condition No external noise sources are applied
Note 1: For CA tests, Cell ID = 0 applies to P-Cell, Cell ID = n (where n is 1, 2, 3..) applies to S-Celln (where n is 1, 2, 3..), respectively

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

8.7.1.1 FDD sustained data rate performance

8.7.1.1.1 Test purpose

The purpose of the test is to verify that the Layer 1 and Layer 2 correctly process in a sustained manner the received packets corresponding to the maximum 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.1.1.1-1 depending on UE capability for CA and EPDCCH.

Table 8.7.1.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
FDD	8.7.1.1, 8.7.1.1_1	8.7.1.1_A	8.7.3.1	8.7.1.1_A, 8.7.3.1

8.7.1.1.2 Test applicability

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

8.7.1.1.3 Minimum requirements

Table 8.7.1.1.3-1: Void

The requirements are specified in Table 8.7.1.1.3-3, with the addition of the parameters in Table 8.7.1.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.1.1.3-4. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.1.1.3-2: Test Parameters for sustained downlink data rate (FDD)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
1	10	1	1 x 2	N/A	0	0	0	-85	OP.6 FDD
2	10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3, 4, 6	20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3A	10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3C, 4B	15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD

Table 8.7.1.1.3-3: 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 [%]
1	10296	R.31-1 FDD	95
2	25456	R.31-2 FDD	95
3	51024	R.31-3 FDD	95
3A	36696 (Note 2)	R.31-3A FDD	85
3C	51024	R.31-3C FDD	85
4	75376 (Note 3)	R.31-4 FDD	85
4B	55056 (Note 5)	R.31-4B FDD	85
6	75376 (Note 3)	R.31-4 FDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752 bits for sub-frame 5.

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

CA config	Maximum supported Bandwidth (MHz)	Category 1	Category 2	Category 3	Category 4	Category 6	Category 7
Single carrier	10	1	2	3A	3A	–	–
	15	–	–	3C	4B	–	–
	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.1

8.7.1.1.4 Test description

8.7.1.1.4.1 Initial conditions

Table 8.7.1.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	PDCP SDU size [Octets] Calculation (Note 1)	PDCP SDU size [Octets]
1	R.31-1 FDD	R.1-1 FDD	10296	1	FLOOR((TB_size– 96)/8)	1275
2	R.31-2 FDD	R.1-2 FDD	25456	3	FLOOR((TB_size– 152)/24)	1054
3	R.31-3 FDD	R.1-3 FDD	51024	5	FLOOR((TB_size-– 208)/40)	1270
3A	R.31-3A FDD	R.1-3A FDD	36696 (Note 3)	4	FLOOR((TB_size– 184)/32)	1141
3C	R.31-3C FDD	R.1-4B FDD	51024	5	FLOOR((TB_size-– 208)/40)	1270
4	R.31-4 FDD	R.1-4 FDD	75376 (Note 4)	7	FLOOR((TB_size– 264)/56)	1341
4B	R.31-4B FDD	R.1-4B FDD	55056 (Note 5)	5	FLOOR((TB_size-– 208)/40)	1371
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. Note 3: 35160 bits for sub-frame 5 Note 4: 71112 bits for sub-frame 5 Note 5: 52752 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.1.1.5-2 depending on the UE category according to Table 8.7.1.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-4 (without using faders and AWGN generators).

2. The parameter settings for the cell are set up according to Table 8.7.1.1.5-2 and Table 8.7.1.1.5-1 depending on the UE category according to Table 8.7.1.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.1.1.4.3. PhysicalConfigDedicated-DEFAULT for transmission mode 3 is defined in Table 8.7.1.1.4.3-3.

8.7.1.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.1.1.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.1.1.5-3.

3. SS sets the counters N_{DL_newtx}N_{DL_retx}, N_{UL_PDCP}, and N_{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.1.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 _{NDL_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.1.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.1.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.1.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 1 0 1 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0	UL PDCP SDU size = 40 bits (5 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1
UE test loop mode B LB setup	Not present

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

8.7.1.1.5 Test requirement

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

Table 8.7.1.1.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
1	10296	R.31-1 FDD	95
2	25456	R.31-2 FDD	95
3	51024	R.31-3 FDD	95
3A	36696 (Note 2)	R.31-3A FDD	85
3C	51024	R.31-3C FDD	85
4	75376 (Note 3)	R.31-4 FDD	85
4B	55056 (Note 5)	R.31-4B FDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5.

Table 8.7.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
1	10	1	1 x 2	N/A	0	0	0	-85	OP.6 FDD
2	10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3,4	20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3A	10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3C, 4B	15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD

Table 8.7.1.1.5-3: Test applicability per UE category

CA config	Maximum supported Bandwidth (MHz)	Category 1	Category 2	Category 3	Category 4	Category 6	Category 7
Single carrier	10	1	2	3A	3A	–	–
	15	–	–	3C	4B	–	–
	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.1.1_1 FDD sustained data rate performance (Rel‑10 and forward)

8.7.1.1_1.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.1.1_1.2 Test applicability

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

8.7.1.1_1.3 Minimum requirements

Same minimum conformance requirements as in clause 8.7.1.1.3.

8.7.1.1_1.4 Test description

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

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

– Instead of Table 8.7.1.1.4.1-1 ‑> use Table 8.7.1.1_1.4-1.

– Instead of Table 8.7.1.1.5-1 ‑> use Table 8.7.1.1_1.5-1.

– Instead of Table 8.7.1.1.5-2 ‑> use Table 8.7.1.1_1.5-2.

– Instead of Table 8.7.1.1.5-3 -> use Table 8.7.1.1_1.5-3.

Table 8.7.1.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

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]

R.31-4 FDD

R.1-4 FDD

75376 (Note 3)

FLOOR((TB_size– 264)/56))

1341

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.1.1_1.5 Test requirement

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

Table 8.7.1.1_1.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
			TB success rate [%]
6	75376 (Note 2)	R.31-4 FDD	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.1.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)

Symbols for unused PRBs

2 x 2

-3

-85

OP.1 FDD

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

CA config

Maximum supported Bandwidth (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.1.1_2 FDD sustained data rate performance for UE category 1bis

8.7.1.1_2.1 Test purpose

Same test purpose as in clause 8.7.1.1.1.

8.7.1.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.1.1_2.3 Minimum conformance requirements

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

– Instead of Table 8.7.1.1.3-2 🡪 use Table 8.7.1.1_2.3-1.

– Instead of Table 8.7.1.1.3-3 🡪 use Table 8.7.1.1_2.3-2.

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

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

Table 8.7.1.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	R.31-1 FDD	95
1B	10296	R.31-1A FDD	95

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

8.7.1.1_2.4 Test description

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

– Instead of Table 8.7.1.1.4.1-1 ‑> use Table 8.7.1.1_2.4-1.

– Instead of Table 8.7.1.1.5-1 ‑> use Table 8.7.1.1_2.5-1.

– Instead of Table 8.7.1.1.5-2 ‑> use Table 8.7.1.1_2.5-2.

– Instead of Table 8.7.1.1.5-3 -> use Table 8.7.1.1_2.5-3.

Table 8.7.1.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 FDD	R.1-1 FDD	10296	1	FLOOR((TB_size– 96)/8)	1275
1B	R.31-1A FDD	R.1-1 FDD	10296	3	FLOOR((TB_size– 96)/8)	1275
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.1.1_2.5 Test requirement

The requirements are specified in Table 8.7.1.1_2.5-1 depending on the UE category according to Table 8.7.1.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.1.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
1A	10	1	1×1	N/A	0	0	0	-85	OP.6 FDD
1B	20	1	1×1	N/A	0	0	0	-85	OP.6 FDD

Table 8.7.1.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.1.1_A FDD sustained data rate performance for CA

8.7.1.1_A.1 FDD Sustained data rate performance for CA (2DL CA)

8.7.1.1_A.1.1 Test purpose

Same test purpose as 8.7.1.1

8.7.1.1_A.1.2 Test applicability

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

This test also applies to E-UTRA FDD release 11 and forward UEs of category 3, 4, 6, 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.1.1_A.1.3 Minimum requirements

Table 8.7.1.1_A.1.3-1: Void

For UE not supporting 256QAM, the requirements are specified in Table 8.7.1.1_A.1.3-3, with the addition of the parameters in Table 8.7.1.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, CA capability and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.1.1_A.1.3-4. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.1.1_A.1.3-2: Test Parameters for sustained downlink data rate for CA (FDD)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
3,4	20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3B, 4A	2×10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6A	2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6B	10+15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6C	10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6D	15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6E	2×15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6F	15+5	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6G	20+5	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 1b with channel selection is used to feedback ACK/NACK for Test 1-6E, and PUCCH format 3 is used to feedback ACK/NACK for Test 7-7G.

Table 8.7.1.1_A.1.3-3: Minimum requirement for CA (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 [%]
3	51024	R.31-3 FDD	95
3B	25456	R.31-2 FDD	95
4	75376 (Note 3)	R.31-4 FDD	85
4A	36696 (Note 2)	R.31-3A FDD	85
6A	75376 (Note 3)	R.31-4 FDD	85
6B	36696 (Note 2) for 10MHz CC 55056 for 15MHz CC	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC	85
6C	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
6D	55056 for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
6E	55056 (Note 5) for two 15MHz CCs	R.31-4B FDD for two 15MHz CCs	85
6F	55056 (Note 5) for 15MHz CC 18336 (Note 6) for 5MHz CC	R.31-5 FDD for 15MHz CC R.31-6 FDD for 5MHz CC	85
6G	75376 (Note 3) for 20MHz CC 18336 (Note 6) for 5MHz CC	R.31-4 FDD for 20MHz CC R.31-6 FDD for 5MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10
CA with 2CCs	10+10	–	–	3B	4A	4A	4A
	10+15	–	–	3B	4A	6B	6B
	10+20	–	–	3B	4A	6C	6C
	15+15			3B	4A	6E	6E
	15+20	–	–	3B	4A	6D	6D
	20+5	–	–	3	4	6G	6G
	20+20	–	–	3B or 3 (Note 4)	4A or 4 (Note 4)	6A	6A
	15+5			3B	4A	6F	6F
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, the single carrier test is selecte, i.e., Test 3 for UE category 3 and Test 4 for UE category 4. Otherwise, Test 3B applies for category 3 UE and Test 4A applies for category 4 UE. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: 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.

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

8.7.1.1_A.1.4 Test description

8.7.1.1_A.1.4.1 Initial conditions

Table 8.7.1.1_A.1.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]
3	R.31-3 FDD	R.1-4 FDD	51024	7	FLOOR((TBsize – 264)/56)	1341
3B	R.31-2 FDD	R.1-2 FDD	25456	3	FLOOR((TBsize – 152)/24)	1054
4	R.31-4 FDD	R.1-4 FDD	75376 (Note 4)	7	FLOOR((TBsize – 264)/56)	1341
4A	R.31-3A FDD	R.1-3A FDD	36696 (Note 3)	4	FLOOR((TBsize – 184)/32)	1141
6A	R.31-4 FDD	R.1-4 FDD	75376 (Note 4)	7	FLOOR((TBsize – 264)/56)	1341
6B	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC	R.1-4B FDD	36696 (Note 3) for 10MHz CC 55056 for 15MHz CC	4 for 10MHz CC 6 for 15 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 240)/48) for 15 MHz CC	1141 for 10MHz CC 1142 for 15MHz CC
6C	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
6D	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	55056 for 15MHz CC 75376 (Note 4) 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
6E	R.31-4B FDD for two 15MHz CCs	R.1-4B FDD	55056 (Note 5) for two 15MHz CCs	6 for two 15MHz CCs	FLOOR((TB_size– 240)/48) for two 15 MHz CCs	1142 for two 15MHz CCs
6F	R.31-5 FDD for 15MHz CC R.31-6 FDD for 5MHz CC	R.1-4B FDD	55056 (Note 5) for 15MHz CC 18336 (Note 6) for 5MHz CC	2 for 5MHz CC 6 for 15MHz CC	FLOOR((TB_size– 128)/16) for 5MHz CC FLOOR((TB_size– 240)/48) for 15 MHz CC	1138 for 5MHz CC 1142 for 15MHz CC
6G	R.31-4 FDD for 20MHz CC R.31-6 FDD for 5MHz CC	R.1-4 FDD	75376 (Note 4) for 20MHz CC 18336 (Note 6) for 5MHz CC	7 for 20 MHz CC 2 for 5MHz CC	FLOOR((TBsize – 264)/56) for 20 MHz CC FLOOR((TB_size– 128)/16) for 5MHz CC	1341 for 20MHz CC 1138 for 5MHz 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: 35160 bits for sub-frame 5. Note 4: 71112 bits for sub-frame 5. Note 5: 52752 bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

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.1.1_A.1.5-2 depending on the UE category according to Table 8.7.1.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.1.1_A.1.5-2 and Table 8.7.1.1_A.1.5-1 depending on the UE category according to Table 8.7.1.1_A.1.5-3.

3. Downlink signals for PCC 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.1.1_A.1.4.3.

8.7.1.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.1.1_A.1.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.1.1_A.1.4.3-3A.

3. 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.1.1_A.1.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.1.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.1.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.

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.1.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.1.1_A.1.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.1.1_A.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 1 0 1 0 0 0, 0 0 0 Q4 Q3 Q2 Q1 Q0	UL PDCP SDU size = 40 bits (5 bytes) Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1
UE test loop mode B LB setup	Not present

Table 8.7.1.1_A.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.1.1_A.1.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.1.1_A.1.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.1.1_A.1.5 Test requirement

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

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

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
		Measurement channel	TB success rate [%]
3	51024	R.31-3 FDD	95
3B	25456	R.31-2 FDD	95
4	75376 (Note 3)	R.31-4 FDD	85
4A	36696 (Note 2)	R.31-3A FDD	85
6A	75376 (Note 3) for 20MHz CC	R.31-4 FDD for 20MHz CC	85
6B	36696 (Note 2) for 10MHz CC 55056 for 15MHz CC	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC	85
6C	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
6D	55056 for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
6E	55056 (Note 6) for two 15MHz CCs	R.31-4B FDD for two 15MHz CCs	85
6F	55056 (Note 6) for 15MHz CC 18336 (Note 8) for 5MHz CC	R.31-5 FDD for 15MHz CC R.31-6 FDD for 5MHz CC	85
6G	75376 (Note 3) for 20MHz CC 18336 (Note 8) for 5MHz CC	R.31-4 FDD for 20MHz CC R.31-6 FDD for 5MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: For category 6 and 7 UE, select one CA configuration among CA configurations corresponding to largest aggregated CA bandwidth signalled by UE. Note 6: 52752 bits for sub-frame 5. Note 7: In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers. Note 8: 15840bits for sub-frame 0.

Table 8.7.1.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
3, 4	20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3B, 4A	2×10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6A	2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6B	10+15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6C	10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6D	15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6E	2×15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6F	15+5	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6G	20+5	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10
CA with 2CCs	10+10	–	–	3B	4A	4A	4A
	10+15	–	–	3B	4A	6B	6B
	10+20	–	–	3B	4A	6C	6C
	15+15			3B	4A	6E	6E
	15+20	–	–	3B	4A	6D	6D
	20+5	–	–	3	4	6G	6G
	20+20	–	–	3B or 3 (Note 4)	4A or 4 (Note 4)	6A	6A
	15+5			3B	4A	6F	6F
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, the single carrier test is selecte, i.e., Test 3 for UE category 3 and Test 4 for UE category 4. Otherwise, Test 3B applies for category 3 UE and Test 4A applies for category 4 UE. 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.1.1_A.2 FDD Sustained data rate performance for CA (3DL CA)

8.7.1.1_A.2.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_A.2.2 Test applicability

This test case applies to all types of E-UTRA FDD 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 applies to all types of E-UTRA FDD UE release 10 and forward of UE category 6 and 7 that support 3DL with CA configurations in Table 7.1-2a and support at most 40MHz aggregated bandwidth and not support 256QAM in DL.

This test case also applies to all types of E-UTRA FDD 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.

This test case also applies to all types of E-UTRA FDD UE release 11 and forward of UE category 6 and 7 that support 3DL with CA configurations in Table 7.1-2a and support at most 40MHz aggregated bandwidth and not support 256QAM in DL.

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

8.7.1.1_A.2.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.1.1_A.2.3-2, with the addition of the parameters in Table 8.7.1.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.1.1_A.2.3-3. The TB success rate shall be sustained during at least 300 frames.

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

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
6A	2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6D	15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7	3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7A	15+20+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7B	10+20+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7C	15+15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7D	10+15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7E	10+10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7F	10+15+15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7G	5+10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7H	5+15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7I	5+10+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 1b with channel selection is used to feedback ACK/NACK for Test 1-6E, and PUCCH format 3 is used to feedback ACK/NACK for Test 7-7G.

Table 8.7.1.1_A.2.3-2: Minimum requirement (FDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
6A	75376 (Note 3)	R.31-4 FDD	85
6D	55056 for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7	75376 (Note 3)	R.31-4 FDD	85
7A	55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7B	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
7C	55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7D	36696 (Note 2) for 10MHz CC 55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7E	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
7F	36696 (Note 2) for 10MHz CC 55056 (Note 5) for 15MHz CC	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC	85
7G	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
7H	18336 (Note 6) for 5MHz CC 55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7I	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	Cat 11, 12
CA with 3CCs	3×20	–	–	–	–	6A	7	7
	15+20+20	–	–	–	–	6A	7A	7A
	10+20+20	–	–	–	–	6A	7B	7B
	15+15+20					6D	7C	7C
	10+15+20	–	–	–	–	6D	7D	7D
	10+10+20	–	–	–	–	7E	7E	7E
	10+15+15	–	–	–	–	7F	7F	7F
	5+10+20	–	–	–	–	7G	7G	7G
	5+15+20	–	–	–	–	7H	7H	7H
	5+10+10	–	–	–	–	7I	7I	7I
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, the single carrier test is selecte, i.e., Test 3 for UE category 3 and Test 4 for UE category 4. Otherwise, Test 3B applies for category 3 UE and Test 4A applies for category 4 UE. 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.1.

8.7.1.1_A.2.4 Test description

8.7.1.1_A.2.4.1 Initial conditions

Table 8.7.1.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 FDD for two 20MHz CCs	R.1-4 FDD	75376 (Note 4)	7 for two 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for two 20MHz CCs
6D	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	55056 for 15MHz CC 75376 (Note 4) 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
7	R.31-4 FDD for three 20MHz CCs	R.1-4 FDD	75376 (Note 4)	7 for three 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for three 20MHz CCs
7A	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	55056 for 15MHz CC 75376 (Note 4) 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
7B	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
7C	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	55056 for 15MHz CC 75376 (Note 4) 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
7D	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 55056 for 15MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 6 for 15MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TB_size– 240)/48) for 15 MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1142 for 15MHz CC 1341 for 20MHz CC
7E	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
7F	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC	R.1-4B FDD	36696 (Note 3) for 10MHz CC 55056 for 15MHz CC	4 for 10MHz CC 6 for 15MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TB_size– 240)/48) for 15 MHz CC	1141 for 10MHz CC 1142 for 15MHz CC
7G	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	18336 (Note 6) for 5MHz CC 36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	2 for 5MHz CC 4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 128)/16) for 5MHz CC FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1138 for 5MHz CC 1141 for 10MHz CC 1341 for 20MHz CC
7H	R.31-6 FDD for 5MHz CC R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	18336 (Note 6) for 5MHz CC 55056 for 15MHz CC 75376 (Note 4) for 20MHz CC	2 for 5MHz CC 6 for 15MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 128)/16) for 5MHz CC FLOOR((TB_size– 240)/48) for 15 MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1138 for 5MHz CC 1142 for 15MHz CC 1341 for 20MHz CC
7I	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC	R.1-1 FDD	18336 (Note 6) for 5MHz CC 36696 (Note 3) for 10MHz CC	2 for 5MHz CC 4 for 10MHz CC	FLOOR((TB_size– 128)/16) for 5MHz CC FLOOR((TB_size– 184)/32) for 10MHz CC	1138 for 5MHz CC 1141 for 10MHz 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: 35160 bits for sub-frame 5. Note 4: 71112 bits for sub-frame 5. Note 5: 52752 bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

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.1.1_A.2.5-2 depending on the UE category according to Table 8.7.1.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.1-1 and Table 8.7.1.1_A.2.5-1 depending on the UE category according to Table 8.7.1.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.1.1_A.2.4.3.

8.7.1.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.4 with two SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.1.1_A.2.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.1.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.1.1_A.2.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.1_A.2.5 Test requirement

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

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

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
7	75376 (Note 3)	R.31-4 FDD	85
7A	55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7B	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
7C	55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7D	36696 (Note 2) for 10MHz CC 55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7E	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
7F	36696 (Note 2) for 10MHz CC 55056 (Note 5) for 15MHz CC	R.31-3A FDD for 10MHz CC R.31-5 FDD for 15MHz CC	85
7G	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
7H	18336 (Note 6) for 5MHz CC 55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
7I	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

Table 8.7.1.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
7	3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7A	15+20+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7B	10+20+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7C	15+15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7D	10+15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7E	10+10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7F	10+15+15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7G	5+10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7H	5+15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7I	5+10+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: PUCCH format 1b with channel selection is used to feedback ACK/NACK for Tests 6A and 6D, and PUCCH format 3 is used to feedback ACK/NACK for Test 7-7G.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	Cat 11, 12
CA with 3CCs	3×20	–	–	–	–	6A	7	7
	15+20+20	–	–	–	–	6A	7A	7A
	10+20+20	–	–	–	–	6A	7B	7B
	15+15+20					6D	7C	7C
	10+15+20	–	–	–	–	6D	7D	7D
	10+10+20	–	–	–	–	7E	7E	7E
	10+15+15	–	–	–	–	7F	7F	7F
	5+10+20	–	–	–	–	7G	7G	7G
	5+15+20	–	–	–	–	7H	7H	7H
	5+10+10	–	–	–	–	7I	7I	7I
Note 1: Void. Note 2: Void. 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 and 6D are tested in 8.7.1.1_A.1

8.7.1.1_A.3 Void

8.7.1.1_A.4 FDD Sustained data rate performance for CA (4DL CA)

8.7.1.1_A.4.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_A.4.2 Test applicability

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

This test case applies to all types of E-UTRA FDD UE release 11 and forward of UE category 9 and 10 that support 4DL with CA configurations in Table 7.1-2b and support at most 60MHz aggregated bandwidth and not support 256QAM in DL.

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

8.7.1.1_A.4.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.1.1_A.4.3-2, with the addition of the parameters in Table 8.7.1.1_A.4.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.1.1_A.4.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.1.1_A.4.3-1: test parameters for sustained downlink data rate (FDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
7	3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
8	4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
8A	20+20+20+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
8B	20+20+10+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
8D	20+10+10+5	3	2 x2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 1b with channel selection is used to feedback ACK/NACK for Test 1-6E, and PUCCH format 3 is used to feedback ACK/NACK for Test 7-7G.

Table 8.7.1.1_A.4.3-2: Minimum requirement (FDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
7	75376 (Note 3)	R.31-4 FDD	85
8	75376 (Note 3)	R.31-4 FDD	85
8A	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
8B	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
8D	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	Cat 11, 12	DL Cat. 15
CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	DL Cat. 11,12	DL Cat. 15
CA with 4CCs	4×20	–	–	–	–	–	7	8	8
	20+20+20+10	–	–	–	–	–	7	8A	8A
	20+20+10+10	–	–	–	–	–	8B	8B	8B
	20+10+10+5	–	–	–	–	–	8D	8D	8D
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, the single carrier test is selected, i.e. Test 3 for UE category 3 and Test 4 for UE category 4. Otherwise, Test 3B applies for category 3 UE and Test 4A applies for category 4 UE. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: 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.

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

8.7.1.1_A.4.4 Test description

8.7.1.1_A.4.4.1 Initial conditions

Table 8.7.1.1_A.4.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 FDD for three 20MHz CCs	R.1-4 FDD	75376 (Note 4)	7 for three 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for three 20MHz CCs
8	R.31-4 FDD for four 20MHz CCs	R.1-4 FDD	75376 (Note 4)	7 for four 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for 20MHz CC
8A	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
8B	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
8D	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	18336 (Note 6) for 5MHz CC 36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	2 for 5MHz CC 4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 128)/16) for 5MHz CC FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1138 for 5MHz CC 1141 for 10MHz 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: 35160 bits for sub-frame 5. Note 4: 71112 bits for sub-frame 5. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

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.1.1_A.4.5-2 depending on the UE category according to Table 8.7.1.1_A.4.5-3.

2. The parameter settings for the cell are set up according to Table 8.7.1-1 and Table 8.7.1.1_A.4.5-1 depending on the UE category according to Table 8.7.1.1_A.4.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.1.1_A.4.4.3.

8.7.1.1_A.4.4.2 Test procedure

1. Configure SCCs according to Annex C.0, C.1 and Annex C.3.2 for all downlink physical channels.

2. The SS shall configure SCCs as per TS 36.508 [7] clause 5.2A.4 with three SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.1.1_A.4.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.1.1_A.4.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.1.1_A.4.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.1.1_A.4.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.1.1_A.4.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.1.1_A.4.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.1.1_A.4.4.3 Message contents

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

Table 8.7.1.1_A.4.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.1.1_A.4.4.3-2: SecurityModeCommand (in the preamble)

Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19
Information Element	Value/remark	Comment	Condition
SecurityModeCommand ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
securityModeCommand-r8 SEQUENCE {
securityConfigSMC SEQUENCE {
securityAlgorithmConfig SEQUENCE {
cipheringAlgorithm	eea2
}
}
nonCriticalExtension SEQUENCE {}	Not present
}
}
}
}

Table 8.7.1.1_A.4.4.3-3: PhysicalConfigDedicated-DEFAULT

Derivation Path: 36.508 clause 5.5.1, Table 5.5.1.2-1
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
antennaInfo CHOICE {
explicitValue ::= SEQUENCE {
transmissionMode	tm3		Transmission mode 3
codebookSubsetRestriction CHOICE {
n2TxAntenna-tm3	10
}
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

Table 8.7.1.1_A.4.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 SEQUENCE {
transmissionMode-r10	tm3		Transmission mode 3
codebookSubsetRestriction-r10	10
ue-TransmitAntennaSelection CHOICE {
release	NULL
}
}
}
}

8.7.1.1_A.4.5 Test requirement

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

Table 8.7.1.1_A.4.5-1: Test requirements per test

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
8	75376 (Note 3)	R.31-4 FDD	85
8A	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
8B	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
8D	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

Table 8.7.1.1_A.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
8	4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
8A	20+20+20+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
8B	20+20+10+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
8D	20+10+10+5	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: void

Table 8.7.1.1_A.4.5-3: Test points per UE category

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	Cat 11, 12
CA with 4CCs	4×20	–	–	–	–	–	7	8
	20+20+20+10	–	–	–	–	–	7	8A
	20+20+10+10	–	–	–	–	–	8B	8B
	20+10+10+5	–	–	–	–	–	8D	8D
Note 1-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.1.1_A.2

8.7.1.1_A.5 FDD Sustained data rate performance for CA (5DL CA)

8.7.1.1_A.5.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_A.5.2 Test applicability

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

This test case also applies to all types of E-UTRA FDD UE release 12 and forward UE of DL category 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.1.1_A.5.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.1.1_A.5.3-2, with the addition of the parameters in Table 8.7.1.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.1.1_A.5.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.1.1_A.5.3-1: test parameters for sustained downlink data rate (FDD 64QAM)

Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction	Downlink power allocation (dB)			at antenna port (dBm/15kHz)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
8	4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9	5×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9A	15+4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9B	10+4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9C	2×10+3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9D	5+10+3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9E	3×10+2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9F	4×10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD

Table 8.7.1.1_A.5.3-2: Minimum requirement (FDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
8	75376 (Note 3)	R.31-4 FDD	85
9	75376 (Note 3)	R.31-4 FDD	85
9A	55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
9B	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9C	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9D	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9E	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9F	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5. Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	Cat 11, 12	DL Cat. 15
CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	DL Cat. 11,12	DL Cat. 15
CA with 5CCs	5×20	–	–	–	–	–	–	8	9
	15+4×20	–	–	–	–	–	–	–	9A
	10+4×20	–	–	–	–	–	–	–	9B
	2×10+3×20	–	–	–	–	–	–	–	9C
	5+10+3×20	–	–	–	–	–	–	–	9D
	3×10+2×20	–	–	–	–	–	–	–	9E
	4×10+20	–	–	–	–	–	–	–	9F
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, the single carrier test is selected, i.e., Test 3 for UE category 3 and Test 4 for UE category 4. Otherwise, Test 3B applies for category 3 UE and Test 4A applies for category 4 UE. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: 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.

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

8.7.1.1_A.5.4 Test description

8.7.1.1_A.5.4.1 Initial conditions

Table 8.7.1.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]
8	R.31-4 FDD for four 20MHz CCs	R.1-4 FDD	75376 (Note 4)	7 for four 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for 20MHz CC
9	R.31-4 FDD for five 20MHz CCs	R.1-4 FDD	75376 (Note 4)	7 for five 20MHz CCs	FLOOR((TBsize – 264)/56)	1341 for 20MHz CC
9A	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	55056 (Note 5) 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
9B	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
9C	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
9D	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	18336 (Note 6) for 5MHz CC 36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	2 for 5MHz CC 4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 128)/16) for 5MHz CC FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1138 for 5MHz CC 1141 for 10MHz CC 1341 for 20MHz CC
9E	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz CC 1341 for 20MHz CC
9F	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	R.1-4 FDD	36696 (Note 3) for 10MHz CC 75376 (Note 4) for 20MHz CC	4 for 10MHz CC 7 for 20 MHz CC	FLOOR((TB_size– 184)/32) for 10MHz CC FLOOR((TBsize – 264)/56) for 20 MHz CC	1141 for 10MHz 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: Void. Note 4: 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.1.1_A.5.5-2 depending on the UE category according to Table 8.7.1.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.1.1_A.5.5-1 depending on the UE category according to Table 8.7.1.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.1.1_A.5.4.3.

8.7.1.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.1.1_A.5.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.1.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.1.1_A.5.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.1.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.1.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.1.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.1.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.1.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
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.1.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.1.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.1.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.1.1_A.5.5 Test requirement

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

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

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
Test		Measurement channel	TB success rate [%]
8	75376 (Note 3)	R.31-4 FDD	85
9	75376 (Note 3)	R.31-4 FDD	85
9A	55056 (Note 5) for 15MHz CC 75376 (Note 3) for 20MHz CC	R.31-5 FDD for 15MHz CC R.31-4 FDD for 20MHz CC	85
9B	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9C	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9D	18336 (Note 6) for 5MHz CC 36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-6 FDD for 5MHz CC R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9E	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
9F	36696 (Note 2) for 10MHz CC 75376 (Note 3) for 20MHz CC	R.31-3A FDD for 10MHz CC R.31-4 FDD for 20MHz CC	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: 35160 bits for sub-frame 5 Note 3: 71112 bits for sub-frame 5. Note 4: 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. Note 5: 52752bits for sub-frame 5. Note 6: 15840bits for sub-frame 0.

Table 8.7.1.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
8	4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9	5×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9A	15+4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9B	10+4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9C	2×10+3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9D	5+10+3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9E	3×10+2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
9F	4×10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	Cat 11, 12	DL Cat. 15
CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 1	Cat. 2	Cat. 3	Cat. 4	Cat. 6,7	Cat. 9,10	DL Cat. 11,12	DL Cat. 15
CA with 5CCs	5×20	–	–	–	–	–	–	8	9
	15+4×20	–	–	–	–	–	–	–	9A
	10+4×20	–	–	–	–	–	–	–	9B
	2×10+3×20	–	–	–	–	–	–	–	9C
	5+10+3×20	–	–	–	–	–	–	–	9D
	3×10+2×20	–	–	–	–	–	–	–	9E
	4×10+20	–	–	–	–	–	–	–	9F
Note 1: Void. Note 2: Void 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 8 is tested in 8.7.1.1_A.4

8.7.1.1_A.6 FDD Sustained data rate performance for CA (6DL CA)

8.7.1.1_A.6.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_A.6.2 Test applicability

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

This test case also applies to all types of E-UTRA FDD UE release 12 and forward UE of DL category 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.1.1_A.6.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.1.1_A.6.3-2, with the addition of the parameters in Table 8.7.1.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.1.1_A.6.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.1.1_A.6.3-1: test parameters for sustained downlink data rate (FDD 64QAM)

Test

Bandwidth (MHz)

Transmission mode

Antenna configuration

Codebook subset restriction

Downlink power allocation (dB)

at antenna port (dBm/15kHz)

Symbols for unused PRBs

6×20

2 x 2

-3

-85

OP.1 FDD

Table 8.7.1.1_A.6.3-2: Minimum requirement (FDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
			TB success rate [%]
10	75376 (Note 3)	R.31-4 FDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: Void Note 3: 71112 bits for sub-frame 5. Note 4: 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.1.1_A.6.3-3: Test points for sustained data rate (FRC 64QAM)

CA config	Maximum supported 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 6CCs	6×20	–	–	–	–	–	–	10	10
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, the single carrier test is selected, i.e., Test 3 for UE category 3 and Test 4 for UE category 4. Otherwise, Test 3B applies for category 3 UE and Test 4A applies for category 4 UE. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: 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.

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

8.7.1.1_A.6.4 Test description

8.7.1.1_A.6.4.1 Initial conditions

Table 8.7.1.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 FDD for six 20MHz CCs

R.1-4 FDD

75376 (Note 4)

7 for six 20MHz CCs

FLOOR((TBsize – 264)/56)

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: Void.

Note 4: 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.1.1_A.6.5-2 depending on the UE category according to Table 8.7.1.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.1.1_A.6.5-1 depending on the UE category according to Table 8.7.1.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.1.1_A.6.4.3.

8.7.1.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 five SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.1.1_A.6.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.1.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.1.1_A.6.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.1.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.1.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.1.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.1.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.1.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
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.1.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.1.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.1.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.1.1_A.6.5 Test Requirements

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

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

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
			TB success rate [%]
10	75376 (Note 3)	R.31-4 FDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: Void Note 3: 71112 bits for sub-frame 5. Note 4: 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.1.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)

Symbols for unused PRBs

6×20

2 x 2

-3

-85

OP.1 FDD

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

CA config	Maximum supported 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 6CCs	6×20	–	–	–	–	–	–	10	10
Note 1: Void. Note 2: Void 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.

8.7.1.1_A.7 FDD Sustained data rate performance for CA (7DL CA)

8.7.1.1_A.7.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_A.7.2 Test applicability

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

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

8.7.1.1_A.7.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.1.1_A.7.3-2, with the addition of the parameters in Table 8.7.1.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.1.1_A.7.3-3. The TB success rate shall be sustained during at least 300 frames.

Table 8.7.1.1_A.7.3-1: test parameters for sustained downlink data rate (FDD 64QAM)

Test

Bandwidth (MHz)

Transmission mode

Antenna configuration

Codebook subset restriction

Downlink power allocation (dB)

at antenna port (dBm/15kHz)

Symbols for unused PRBs

7×20

2 x 2

-3

-85

OP.1 FDD

Table 8.7.1.1_A.7.3-2: Minimum requirement (FDD 64QAM)

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
			TB success rate [%]
11	75376 (Note 3)	R.31-4 FDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: Void. Note 3: 71112 bits for sub-frame 5. Note 4: 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.1.1_A.7.3-3: Test points for sustained data rate (FRC 64QAM)

CA config	Maximum supported 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 7CCs	7×20	–	–	–	–	–	–	11	11
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, the single carrier test is selected, i.e., Test 3 for UE category 3 and Test 4 for UE category 4. Otherwise, Test 3B applies for category 3 UE and Test 4A applies for category 4 UE. Note 5: The applicability of requirements for different CA configurations and bandwidth combination sets is defined in 8.1.2.3. Note 6: 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.

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

8.7.1.1_A.7.4 Test description

8.7.1.1_A.7.4.1 Initial conditions

Table 8.7.1.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 FDD for seven 20MHz CCs

R.1-4 FDD

75376 (Note 4)

7 for seven 20MHz CCs

FLOOR((TBsize – 264)/56)

1341 for 20MHz CC

Note 3: Void.

Note 4: 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.1.1_A.7.5-2 depending on the UE category according to Table 8.7.1.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.1.1_A.7.5-1 depending on the UE category according to Table 8.7.1.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.1.1_A.7.4.3.

8.7.1.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 five SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.1.1_A.7.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.1.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.1.1_A.7.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.1.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.1.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.1.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.1.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.1.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
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.1.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.1.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.1.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.1.1_A.7.5 Test Requirements

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

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

Test	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value
			TB success rate [%]
11	75376 (Note 3)	R.31-4 FDD	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: Void Note 3: 71112 bits for sub-frame 5. Note 4: 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.1.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)

Symbols for unused PRBs

7×20

2 x 2

-3

-85

OP.1 FDD

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

CA config	Maximum supported 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 7CCs	7×20	–	–	–	–	–	–	11	11
Note 1: Void. Note 2: Void. 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.

8.7.1.1_H FDD 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.1.1_H.1 FDD sustained data rate performance for 256QAM in DL (Single Carrier)

8.7.1.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.1.1_H.1.2 Test applicability

This test applies to E-UTRA FDD UEs Release 12 and forward of UE DL category 13 that support 256QAM in DL.

8.7.1.1_H.1.3 Minimum requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.1.1_H.1.3-2, with the addition of the parameters in Table 8.7.1.1_H.1.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.1.1_H.1.3-3, the TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.1.1.3-3 is not applicable.

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

Test

Bandwidth (MHz)

Transmission mode

Antenna configuration

Codebook subset restriction

Downlink power allocation (dB)

at antenna port (dBm/15kHz)

Symbols for unused PRBs

2 x 2

-3

-85

OP.1 FDD

Table 8.7.1.1_H.1.3-2: Minimum requirement (FDD 256QAM)

Test	Measurement channel	Reference value
		TB success rate [%]
1	R.68 FDD	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.1.1_H.1.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13
		DL Cat. 11, 12
Single carrier	20	–	1

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

8.7.1.1_H.1.4 Test description

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

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

– Instead of Table 8.7.1.1.4.1-1 ‑> use Table 8.7.1.1_H.1.4-1.

– Instead of Table 8.7.1.1.5-1 ‑> use Table 8.7.1.1_H.1.5-1.

– Instead of Table 8.7.1.1.5-2 ‑> use Table 8.7.1.1_H.1.5-2.

– Instead of Table 8.7.1.1.5-3 -> use Table 8.7.1.1_H.1.5-3.

Table 8.7.1.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

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]

R.68 FDD

R.1-4 FDD

97896

FLOOR((TB_size– 352)/80)

1219

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: 84760 bits for sub-frames 0,1,2,6,7 and 81176 bits for sub-frames 5.

8.7.1.1_H.1.5 Test requirement

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

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

Test	Measurement channel	Reference value
		TB success rate [%]
1	R.68 FDD	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.1.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)

Symbols for unused PRBs

2 x 2

-3

-85

OP.1 FDD

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13
		DL Cat. 11, 12
Single carrier	20	–	1

8.7.1.1_H.2 FDD Sustained data rate performance for CA (2DL CA) for 256QAM in DL

8.7.1.1_H.2.1 Test purpose

Same test purpose as 8.7.1.1

8.7.1.1_H.2.2 Test applicability

This test applies to E-UTRA FDD UE release 12 and forward of 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.1.1_H.2.3 Minimum requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.1.1_H.2.3-2, with the addition of the parameters in Table 8.7.1.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.1.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.1.1_A.1.3-3 is not applicable.

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

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

Table 8.7.1.1_H.2.3-2: Minimum requirement (FDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
2	R.68-2 FDD	85
3	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC	85
4	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
5	R.68-1 FDD	85
6	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
7	R.68 FDD	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.1.1_H.2.3-3: Test points for sustained data rate (FRC 256QAM)

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

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

8.7.1.1_H.2.4 Test description

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

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

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

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

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

Table 8.7.1.1_H.2.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]
2	R.68-2 FDD	R.1-2 FDD	48936(Note 5)	5	FLOOR((TBsize – 208)/40)	1218
3	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC	R.1-4B FDD	48936 (Note 5) for 10MHz CC 75376 (Note 4) for 15MHz CC	5 for 10MHz CC 7 for 15MHz CC	FLOOR((TBsize – 208)/40) for 10MHz CC FLOOR((TBsize – 264)/64) for 15MHz CC	1218 for 10MHz CC 1341 for 15MHz CC
4	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	R.1-4 FDD	48936 (Note 5) for 10MHz CC 97896 (Note 3) for 20MHz CC	5 for 10MHz CC 10 for 20MHz CC	FLOOR((TBsize – 208)/40) for 10MHz CC FLOOR((TB_size– 352)/80) for 20MHz CC	1218 for 10MHz CC 1219 for 20MHz CC
5	R.68-1 FDD	R.1-4B FDD	75376(Note 4)	7	FLOOR((TB_size– 264)/64)	1341
6	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	R.1-4 FDD	75376 (Note 4) for 15MHz CC 97896(Note 3) for 20MHz CC	7 for 15MHz CC 10 for 20 MHz CC	FLOOR((TB_size– 264)/64) for 15MHz CC FLOOR((TB_size– 352)/80) for 20 MHz CC	1341 for 15MHz CC 1219 for 20MHz CC
7	R.68 FDD	R.1-4 FDD	97896(Note 3)	10	FLOOR((TB_size– 352)/80)	1219
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.

8.7.1.1_H.2.5 Test requirement

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

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

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
2	R.68-2 FDD	85
3	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC	85
4	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
5	R.68-1 FDD	85
6	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
7	R.68 FDD	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.1.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
2	2×10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
3	10+15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
4	10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
5	2×15	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
6	15+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
7	2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13
CA config		DL Cat. 11, 12	DL Cat. 13
CA with 2CCs	2×10	2	2
	10+15	3	3
	10+20	4	4
	2×15	5	5
	15+20	6	6
	20+20	7	7
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.1.1_H.3 FDD Sustained data rate performance for CA for 256QAM in DL (3DL CA)

8.7.1.1_H.3.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_H.3.2 Test applicability

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

This test case applies to all types of E-UTRA FDD UE release 12 and forward of UE DL category 13 that support 3DL CA and 256QAM in DL and at most 40MHz aggregated bandwidth.

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

8.7.1.1_H.3.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.1.1_H.3.3-2, with the addition of the parameters in Table 8.7.1.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.1.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.1.1_A.2.3-2 is not applicable.

The test coverage for different number of component carriers is defined in 8.1.2.4.

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

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

Table 8.7.1.1_H.3.3-2: Minimum requirement (FDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
8	R.68 FDD	85
9	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
10	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
11	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
12	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
13	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
14	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC	85
15	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
15A	R.68-3 FDD for 5MHz CC R.68-1 FDD for 15MHz CC R.68 FDD 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.1.1_H.3.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15
CA config		DL Cat. 11, 12	DL Cat. 13
CA with 3CCs	3×20	8	7	8
	15+20+20	9	7	9
	10+20+20	10	7	10
	15+15+20	11	6	11
	10+15+20	12	6	12
	10+10+20	13	13	13
	10+15+15	14	14	14
	5+10+20	15	15	15
	5+15+20	15A	15A	15A

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

8.7.1.1_H.3.4 Test description

Same test description as in clause 8.7.1.1_A.2.4 with the following exceptions:

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

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

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

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

Table 8.7.1.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]

R.68 FDD for 20MHz CC

R.1-4 FDD

97896 (Note 3) for 20MHz CC

10 for 20MHz CC

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

1219 for 20MHz CC

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

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

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

75376 (Note 4) for 15MHz CC
97896 (Note 3) for 20MHz CC

7 for 15MHz CC

10 for 20 MHz CC

FLOOR((TB_size– 264)/56) for 15MHz CC

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

1341 for 15MHz CC

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

75376 (Note 4) for 15MHz CC

97896(Note 3) for 20MHz CC

5 for 10MHz CC

7 for 15MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

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

1218 for 10MHz CC

1341 for 15MHz CC

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68-1 FDD for 15MHz CC

R.1-4B FDD

48936 (Note 5) for 10MHz CC

75376 (Note 4) for 15MHz CC

5 for 10MHz CC

7 for 15MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1341 for 15MHz CC

R.68-3 FDD for 5MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

3 for 5MHz CC

5 for 10MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1014 for 5MHz CC

1218 for 10MHz CC

1219 for 20MHz CC

15A

R.68-3 FDD for 5MHz CC

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

75376 (Note 4) for 15MHz CC 97896 (Note 3) for 20MHz CC

3 for 5MHz CC

7 for 15MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

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

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

1014 for 5MHz CC

1341 for 15MHz 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.1.1_H.3.5 Test requirement

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

Table 8.7.1.1_H.3.5-1: Minimum requirement

		TB success rate [%]
8	R.68 FDD	85
9	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
10	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
11	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
12	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
13	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
14	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC	85
15	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
15A	R.68-3 FDD for 5MHz CC R.68-1 FDD for 15MHz CC R.68 FDD 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.1.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)		Symbols for unused PRBs
												σ
8	3×20	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
9	15+20+20	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
10	10+20+20	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
11	15+15+20	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
12	10+15+20	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
13	10+10+20	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
14	10+15+15	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
15	5+10+20	3		2 x 2		10		-3		-3		0		-85		OP.1 FDD
15A	5+15+20	3	2 x 2		10		-3		-3		0		-85		OP.1 FDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15
CA config		DL Cat. 11, 12	DL Cat. 13	DL Cat. 15
CA with 3CCs	3×20	8	7	8
	15+20+20	9	7	9
	10+20+20	10	7	10
	15+15+20	11	6	11
	10+15+20	12	6	12
	10+10+20	13	13	13
	10+15+15	14	14	14
	5+10+20	15	15	15
	5+15+20	15A	15A	15A
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 6 and Test 7 are tested in 8.7.1.1_H.2.

8.7.1.1_H.4 FDD Sustained data rate performance for CA (4DL CA) for 256QAM in DL

8.7.1.1_H.4.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_H.4.2 Test applicability

This test case applies to all types of E-UTRA FDD UE release 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.1.1_H.4.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.1.1_H.4.3-2, with the addition of the parameters in Table 8.7.1.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.1.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.1.1_A.4.3-2 is not applicable.

The test coverage for different number of component carriers is defined in 8.1.2.4.

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

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

Table 8.7.1.1_H.4.3-2: Minimum requirement (FDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
16	R.68 FDD	85
17	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18A	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18B	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18C	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
18D	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
18E	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
18F	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18G	R.68-3 FDD for 5MHz CC R.68 FDD for 20MHz CC	85
18H	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18I	R.68-2 FDD for 10MHz 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.1.1_H.4.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA config		DL Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA with 4CCs	4×20	8	–	16	16
	20+20+20+10	8	–	17	17
	20+20+10+10	18	–	18	18
	20+20+10+5	18A	–	18A	18A
	20+10+10+5	18B	–	18B	18B
	15+3×20	18C		18C	18C
	2×15+2×20	18D		18D	18D
	10+15+2×20	18E		18E	18E
	3×10+20	18F		18F	18F
	2×5+2×20	18G		18G	18G
	2×5+10+20	18H		18H	18H
	4×10	18I		18I	18I
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.

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

8.7.1.1_H.4.4 Test description

Same test description as in clause 8.7.1.1_A.4.4 with the following exceptions:

– Instead of Table 8.7.1.1_A.4.4.1-1 ‑> use Table 8.7.1.1_H.4.4-1.

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

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

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

Table 8.7.1.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]

R.68 FDD for 20MHz CC

R.1-4 FDD

97896 (Note 3) for 20MHz CC

10 for 20MHz CC

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

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

18A

R.68-3 FDD for 5MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

3 for 5MHz CC

5 for 10MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1014 for 5MHz CC

1218 for 10MHz CC

1219 for 20MHz CC

18B

R.68-3 FDD for 5MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

3 for 5MHz CC

5 for 10MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1014 for 5MHz CC

1218 for 10MHz CC

1219 for 20MHz CC

18C

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

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

18D

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

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

18E

R.68-2 FDD for 10MHz CC

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

75376 (Note 4) for 15MHz CC 97896 (Note 3) for 20MHz CC

3 for 5MHz CC

7 for 15MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

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

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

1014 for 5MHz CC

1341 for 15MHz CC

1219 for 20MHz CC

18F

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

18G

R.68-3 FDD for 5MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

97896 (Note 3) for 20MHz CC

3 for 5MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

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

1014 for 5MHz CC

1219 for 20MHz CC

18H

R.68-3 FDD for 5MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

3 for 5MHz CC

5 for 10MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1014 for 5MHz CC

1218 for 10MHz CC

1219 for 20MHz CC

18I

R.68-2 FDD for 10MHz CC

R.1-3a FDD

48936 (Note 5) for 10MHz CC

5 for 10MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

1218 for 10MHz 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.1.1_H.4.5 Test requirement

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

Table 8.7.1.1_H.4.5-1: Minimum requirement

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
16	R.68 FDD	85
17	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18A	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18B	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18C	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
18D	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
18E	R.68-2 FDD for 10MHz CC R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
18F	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18G	R.68-3 FDD for 5MHz CC R.68 FDD for 20MHz CC	85
18H	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
18I	R.68-2 FDD for 10MHz 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.1.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
16	4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
17	20+20+20+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18	20+20+10+10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18A	20+20+10+5	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18B	20+10+10+5	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18C	15+3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18D	2×15+2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18E	10+15+2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18F	3×10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18G	2×5+2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18H	2×5+10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
18I	4×10	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA config		DL Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA with 4CCs	4×20	8	–	16	16
	20+20+20+10	8	–	17	17
	20+20+10+10	18	–	18	18
	20+20+10+5	18A	–	18A	18A
	20+10+10+5	18B	–	18B	18B
	15+3×20	18C		18C	18C
	2×15+2×20	18D		18D	18D
	10+15+2×20	18E		18E	18E
	3×10+20	18F		18F	18F
	2×5+2×20	18G		18G	18G
	2×5+10+20	18H		18H	18H
	4×10	18I		18I	18I
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.

8.7.1.1_H.5 FDD Sustained data rate performance for CA (5DL CA) for 256QAM in DL

Editor’s notes: This test case is incomplete. The following items are missing or are incomplete:

8.7.1.1_H.5.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_H.5.2 Test applicability

This test case applies to all types of E-UTRA FDD UE release and forward of UE DL category 15 and 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.1.1_H.5.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.1.1_H.5.3-2, with the addition of the parameters in Table 8.7.1.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.1.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.1.1_A.5.3-2 is not applicable.

The test coverage for different number of component carriers is defined in 8.1.2.4.

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

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

Table 8.7.1.1_H.5.3-2: Minimum requirement (FDD 256QAM)

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
19	R.68 FDD	85
20	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
21	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
22	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
23	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
24	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
25	R.68-2 FDD for 10MHz CC R.68 FDD 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.1.1_H.5.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA config		DL Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA with 5CCs	5×20	–	–	16	19
	15+4×20				20
	10+4×20				21
	2×10+3×20				22
	5+10+3×20				23
	3×10+2×20				24
	4×10+20				25
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.

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

8.7.1.1_H.5.4 Test description

Same test description as in clause 8.7.1.1_A.4.4 with the following exceptions:

– Instead of Table 8.7.1.1_A.4.4.1-1 ‑> use Table 8.7.1.1_H.5.4-1.

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

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

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

Table 8.7.1.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]

R.68 FDD for 20MHz CC

R.1-4 FDD

97896 (Note 3) for 20MHz CC

10 for 20MHz CC

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

1219 for 20MHz CC

R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

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

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

R.68-3 FDD for 5MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

24496 (Note 6) for 5MHz CC

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

3 for 5MHz CC

5 for 10MHz CC

10 for 20MHz CC

FLOOR((TBsize – 152)/24) for 10MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1014 for 5MHz CC

1218 for 10MHz CC

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz CC

1219 for 20MHz CC

R.68-2 FDD for 10MHz CC

R.68 FDD for 20MHz CC

R.1-4 FDD

48936 (Note 5) for 10MHz CC

97896 (Note 3) for 20MHz CC

5 for 10MHz CC

10 for 20 MHz CC

FLOOR((TBsize – 208)/40) for 10MHz CC

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

1218 for 10MHz 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.1.1_H.5.5 Test requirement

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

Table 8.7.1.1_H.5.5-1: Minimum requirement

Test	Measurement channel	Reference value
Test	Measurement channel	TB success rate [%]
19	R.68 FDD	85
20	R.68-1 FDD for 15MHz CC R.68 FDD for 20MHz CC	85
21	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
22	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
23	R.68-3 FDD for 5MHz CC R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
24	R.68-2 FDD for 10MHz CC R.68 FDD for 20MHz CC	85
25	R.68-2 FDD for 10MHz CC R.68 FDD 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.1.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)	Symbols for unused PRBs
Test	Bandwidth (MHz)	Transmission mode	Antenna configuration	Codebook subset restriction			σ	at antenna port (dBm/15kHz)	Symbols for unused PRBs
19	5×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
20	15+4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
21	10+4×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
22	2×10+3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
23	5+10+3×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
24	3×10+2×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
25	4×10+20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA config		DL Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
CA with 5CCs	5×20	–	–	16	19
	15+4×20				20
	10+4×20				21
	2×10+3×20				22
	5+10+3×20				23
	3×10+2×20				24
	4×10+20				25
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.

8.7.1.1_H.6 FDD Sustained data rate performance for CA (6DL CA) for 256QAM in DL

8.7.1.1_H.6.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_H.6.2 Test applicability

This test case applies to all types of E-UTRA FDD UE release 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.1.1_H.6.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.1.1_H.6.3-2, with the addition of the parameters in Table 8.7.1.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.1.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.1.1_A.6.3-2 is not applicable.

The test coverage for different number of component carriers is defined in 8.1.2.4.

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

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

Table 8.7.1.1_H.6.3-2: Minimum requirement (FDD 256QAM)

Test	Measurement channel	Reference value
		TB success rate [%]
20	R.68 FDD	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.1.1_H.6.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
		DL Cat. 11, 12
CA with 6CCs	6×20	–	–	–	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.

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

8.7.1.1_H.6.4 Test description

Same test description as in clause 8.7.1.1_A.4.4 with the following exceptions:

– Instead of Table 8.7.1.1_A.4.4.1-1 ‑> use Table 8.7.1.1_H.6.4-1.

– Instead of Table 8.7.1.1_A.4.5-1 ‑> use Table 8.7.1.1_H.6.5-1.

– Instead of Table 8.7.1.1_A.4.5-2 ‑> use Table 8.7.1.1_H.6.5-2.

– Instead of Table 8.7.1.1_A.4.5-3 -> use Table 8.7.1.1_H.6.5-3.

Table 8.7.1.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 FDD for 20MHz CC

R.1-4 FDD

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.

8.7.1.1_H.6.5 Test Requirements

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

Table 8.7.1.1_H.6.5-1: Minimum requirement

Test	Measurement channel	Reference value
		TB success rate [%]
20	R.68 FDD	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.1.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)	Symbols for unused PRBs
							σ
20	6×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16	DL Cat. 18
		DL Cat. 11, 12
CA with 6CCs	6×20	–	–	–	–	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.

8.7.1.1_H.7 FDD Sustained data rate performance for CA (7DL CA) for 256QAM in DL

8.7.1.1_H.7.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.1.1_H.7.2 Test applicability

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

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

8.7.1.1_H.7.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.1.1_H.7.3-2, with the addition of the parameters in Table 8.7.1.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.1.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.1.1_A.6.3-2 is not applicable.

The test coverage for different number of component carriers is defined in 8.1.2.4.

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

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

Table 8.7.1.1_H.7.3-2: Minimum requirement (FDD 256QAM)

Test	Measurement channel	Reference value
		TB success rate [%]
21	R.68 FDD	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.1.1_H.7.3-3: Test points for sustained data rate (FRC 256QAM)

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
		DL Cat. 11, 12
CA with 7CCs	7×20	–	–	–	21
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.

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

8.7.1.1_H.7.4 Test description

Same test description as in clause 8.7.1.1_A.4.4 with the following exceptions:

– Instead of Table 8.7.1.1_A.4.4.1-1 ‑> use Table 8.7.1.1_H.7.4-1.

– Instead of Table 8.7.1.1_A.4.5-1 ‑> use Table 8.7.1.1_H.7.5-1.

– Instead of Table 8.7.1.1_A.4.5-2 ‑> use Table 8.7.1.1_H.7.5-2.

– Instead of Table 8.7.1.1_A.4.5-3 -> use Table 8.7.1.1_H.7.5-3.

Table 8.7.1.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 FDD for 20MHz CC

R.1-4 FDD

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.

8.7.1.1_H.7.5 Test Requirements

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

Table 8.7.1.1_H.7.5-1: Minimum requirement

Test	Measurement channel	Reference value
		TB success rate [%]
21	R.68 FDD	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.1.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)	Symbols for unused PRBs
							σ
21	7×20	3	2 x 2	10	-3	-3	0	-85	OP.1 FDD
Note 1: For CA test cases, PUCCH format 3 is used to feedback ACK/NACK.

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

CA config	Maximum supported Bandwidth/ Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13	DL Cat. 15	DL Cat. 16
		DL Cat. 11, 12
CA with 7CCs	7×20	–	–	–	21
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.