8.7.7 TDD (Dual Connectivity)

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

Table 8.7.7-1: Common Test Parameters (TDD)

Parameter	Unit		Value
Uplink downlink configuration			2 (Note 2)
Special subframe configuration			4
Cyclic prefix			Normal
Cell ID			0
Inter-TTI Distance			1
Number of HARQ processes per component carrier	Processes		7
Maximum number of HARQ transmission			4
Redundancy version coding sequence			{0,0,1,2} for 64QAM and 256QAM
Number of OFDM symbols for PDCCH per component carrier	OFDM symbols		1
Cross carrier scheduling			Not configured
Propagation condition			Static propagation condition No external noise sources are applied
Transmission mode			TM3
Codebook subset restriction			10
Antenna configuration			2×2
at antenna port (dBm/15kHz)			-85
Symbols for unused PRBs			OP.1 TDD
ACK/NACK feedback mode			Separate ACK/NACK feedbacks with PUCCH format 3 on the MCG and SCG
Time offset between MCG CC and SCG CC	μs		0 for UE under test supporting synchronous dual connectivity; 500 for UE under test supporting both asynchronous and synchronous dual connectivity (Note 1)
Downlink power allocation		dB	-3
		dB	-3
	σ	dB	0
Note 1: Asynchronous and synchronous dual connectivity are defined in TS36.300 [18]. Note 2: If the UE supports both SCG bearer and Split bearer, the Split bearer is configured.

8.7.7.1 TDD sustained data rate performance for Dual Connectivity 64QAM

8.7.7.1.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.7.1.2 Test applicability

This test case applies to all types of E-UTRA TDD release 12 and forward UE of category 6, 7, 9, and 10 that support Dual Connectivity and not supporting 256QAM in DL.

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

8.7.7.1.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements are specified in Table 8.7.7.1.3-12, with the addition of the parameters in Table 8.7.7-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.7.1.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements is specified in Clause 8.1.2.3A.

Table 8.7.7.1.3-1: Minimum requirement (DC 64QAM)

Test number	Bandwidth combination (MHz)	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value TB success rate across CGs(%)
				DRB type of Split bearer (Note 2)	DRB type of SCG bearer (Note 3)
					MCG	SCG
1	2×20	75376/0 (Note 4)	R.31-4A TDD	85	85	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: For the configuration of DRB type of Split bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks across all the CGs used for DC transmission or reception. Note 3: For the configuration of DRB type of SCG bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks per CG used for DC transmission or reception, separately. Note 4: 71112 bits for sub-frame 5.

Table 8.7.7.1.3-2: Test points for sustained data rate (FRC DC 64QAM)

DC config	Maximum supported Bandwidth combination (MHz)	Cat. 3	Cat. 4	Cat. 6, 7	Cat. 9, 10	Cat. 11, 12
DC with 2CCs	2×20	–	–	1	1	–

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

8.7.7.1.4 Test description

8.7.7.1.4.1 Initial conditions

Table 8.7.7.1.4.1-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TB_size per Codeword per Component Carrier

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

PDCP SDU size [Octets] Calculation

(Note 1)

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

R.31-4A TDD

R.1-4 TDD

75376
(Note 3)

7/0

FLOOR((TB_size– 264)/56))

1341/0

Note 1: Transport block size under test according to applicable Fixed Reference Channel for sustained data-rate test in annex A.3.9. In case of varying TBS across SFs of the RMC, only the maximum TBS is used for PDCP SDU size calculation. In case of different resulting PDCP SDU sizes among component carriers, the smaller calculated PDCP SDU size is used across all the carriers.

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

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

Note 3: 71112 bits for sub-frame 5

Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.

Configurations of PDSCH and PDCCH before measurement are specified in Annex C.2.

Test Environment: Normal as defined in TS 36.508 [7] clause 4.1.

Frequencies to be tested: Mid Range as defined in TS 36.508 [7] clause 4.3.1.1.

Channel Bandwidths to be tested: according to Tables 8.1.2.3A-1 and 8.7.7.1.5-1 depending on the UE category according to Table 8.7.7.1.5-2.

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.7-1 and Table 8.7.7.1.5-1 depending on the UE category according to Table 8.7.7.1.5-2.

3. Downlink signals for MCG CC (PCell) and SCG CC (PSCell) 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. If the SCG bearer is only supported, ensure the UE is in State 4A-RF-DC1 according to TS 36.508 [7] clause 5.2A.3A. Otherwise, ensure that the UE is in State 4A-RF-DC2 according to TS 36.508 [7] clause 5.2A.3B. Message contents are defined in clause 8.7.7.1.4.3.

8.7.7.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.7.1.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.7.1.5-2.

3. SS sets the counters N_{DL_newtx}, N_{DL_retx}, N_{UL_PDCP}, and N_{DL_PDCP} to 0 on PCell and PSCell respectively.

4. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.7.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 on PCell and PSCell respectively.

5. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments N_{DL_retx} by one on PCell and PSCell respectively.

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 on PCell and PSCell respectively.

8. The SS calculates the TB success rate as A = 100%*N_{DL_newtx}/ (N_{DL_newtx} + N_{DL_retx}) on PCell and PSCell respectively. 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 on PCell and PSCell respectively. The total TB success rate is calculated as A_total= PCell’s A + PSCell’s A.

9. The SS calculates the PDCP SDU loss as B = N_{DL_PDCP} – N_{UL_PDCP} on PCell and PSCell respectively. The total PDCP SDU loss is calculated as B_total = PCell’s B + PSCell’s B.

10. The UE passes the test if A_total ≥ "corresponding TB success rates according to Table 8.7.7.1.5-1" and B_total = 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.7.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.7.1.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.508 [7] 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.7.1.4.3-2: SecurityModeCommand (in the preamble)

Derivation Path: TS 36.508 [7] 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.7.1.4.3-2A: MobilityControlInfoSCG-r12

Derivation Path: TS 36.331 [5] clause 6.3.4 MobilityControlInfoSCG-r12
Information Element	Value/remark	Comment	Condition
MobilityControlInfoSCG-r12 ::= SEQUENCE {
t307-r12	ms2000
ue-IdentitySCG-r12	C-RNTI	PSCell’s C-RNTI
rach-ConfigDedicated-r12	Rach-ConfigDedicated-DEFAULT
cipheringAlgorithmSCG-r12	eea2
}

Table 8.7.7.1.4.3-3: PhysicalConfigDedicated-DEFAULT (PCell and PSCell)

Derivation Path: 36.508 [7] 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
}
}
}
}

8.7.7.1.5 Test requirement

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

Table 8.7.7.1.5-1: Test requirement (DC 64QAM)

Test number	Bandwidth combination (MHz)	Number of bits of a DL-SCH transport block received within a TTI	Measurement channel	Reference value TB success rate across CGs(%)
				DRB type of Split bearer (Note 2)	DRB type of SCG bearer (Note 3)
					MCG	SCG
1	2×20	75376/0 (Note 4)	R.31-4A TDD	85	85	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: For the configuration of DRB type of Split bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks across all the CGs used for DC transmission or reception. Note 3: For the configuration of DRB type of SCG bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks per CG used for DC transmission or reception, separately. Note 4: 71112 bits for sub-frame 5.

Table 8.7.7.1.5-2: Test points for sustained data rate (FRC DC 64QAM)

DC config	Maximum supported Bandwidth combination (MHz)	Cat. 3	Cat. 4	Cat. 6, 7	Cat. 9, 10	Cat. 11, 12
DC with 2CCs	2×20	–	–	1	1	–

8.7.7.2 TDD sustained data rate performance for Dual Connectivity 256QAM

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

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

– Check whether MCG/SCG should be mentioned in Annex C.

– Check how to measure the throughput using two uplink component carriers.

8.7.7.2.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.7.2.2 Test applicability

This test case applies to all types of E-UTRA TDD release 12 and forward UEs that support Dual Connectivity and 256QAM in DL.

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

8.7.7.2.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements are specified in Table 8.7.7.2.3-1, with the addition of the parameters in Table 8.7.7-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.7.2.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements in Table 8.7.7.1.3-1 are not applicable.

The applicability of the requirements is specified in Clause 8.1.2.3A.

Table 8.7.7.2.3-1: Minimum requirement (DC 256QAM)

Test number	Bandwidth combination (MHz)	Measurement channel	Reference value TB success rate (%)
			DRB type of Split bearer (Note 2)	DRB type of SCG bearer (Note 3)
				MCG	SCG
1	2×20	R.68-3 TDD	85	85	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: For the configuration of DRB type of Split bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks across all the CGs used for DC transmission or reception. Note 3: For the configuration of DRB type of SCG bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks per CG used for DC transmission or reception, separately.

Table 8.7.7.2.3-2: Test points for sustained data rate (FRC DC 256QAM)

DC config	Maximum supported Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13
		DL Cat. 11, 12
DC with 2CCs	2×20	1	1

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

8.7.7.2.4 Test description

8.7.7.2.4.1 Initial conditions

Table 8.7.7.2.4.1-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TB_size per Codeword per Component Carrier

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

PDCP SDU size [Octets] Calculation

(Note 1)

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

R.68-3 TDD

R.1-4 TDD

97896(Note 3)

10/0

FLOOR((TB_size– 352)/80)

1219/0

Note 3: 84760 bits for sub-frame 0, 4 and 81176 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 Tables 8.1.2.3A-1 and 8.7.7.2.5-1 depending on the UE category according to Table 8.7.7.2.5-2.

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.7-1 and Table 8.7.7.1.5-1 depending on the UE category according to Table 8.7.7.1.5-2.

3. Downlink signals for MCG CC and SCG CC 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.

8.7.7.2.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.7.2.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.7.2.5-2.

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

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.7.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.7.2.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.7.2.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.508 [7] 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.7.2.4.3-2: SecurityModeCommand (in the preamble)

Derivation Path: TS 36.508 [7] 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.7.2.4.3-3: PhysicalConfigDedicated-DEFAULT

Derivation Path: 36.508 [7] 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
}
}
}
}

8.7.7.2.5 Test requirement

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

Table 8.7.7.2.5-1: Test requirement (DC 256QAM)

Test number	Bandwidth combination (MHz)	Measurement channel	Reference value TB success rate (%)
			DRB type of Split bearer (Note 2)	DRB type of SCG bearer (Note 3)
				MCG	SCG
1	2×20	R.68-3 TDD	85	85	85
Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI. Note 2: For the configuration of DRB type of Split bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks across all the CGs used for DC transmission or reception. Note 3: For the configuration of DRB type of SCG bearer, the TB success rate across CGs 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. All the above numbers of transmitted, retransmitted or correctly received DL transport blocks are calculated as the sum of the numbers of DL transport blocks per CG used for DC transmission or reception, separately.

Table 8.7.7.2.5-2: Test points for sustained data rate (FRC DC 256QAM)

DC config	Maximum supported Bandwidth combination (MHz)	Cat. 11, 12	DL Cat. 13
		DL Cat. 11, 12
DC with 2CCs	2×20	1	1