8.7.5 TDD FDD CA Sustained data rate performance

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

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

Table 8.7.5-1: Common Test Parameters (TDD FDD CA)

Parameter

Unit

Value

Uplink downlink configuration (Note 1) for TDD CC

1

Special subframe configuration (Note 2) for TDD CC

4

Downlink power allocation

dB

-3

dB

-3

σ

dB

0

Cyclic prefix

Normal

Cell ID

0

Inter-TTI Distance

1

Maximum number of HARQ processes per component carrier

FDD PCell

Processes

8 for FDD and TDD CCs

TDD PCell

Processes

11 for FDD CC; 7 for TDD CC

Maximum number of HARQ transmission

4

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, 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 x 2

at antenna port (dBm/15kHz)

-85

Symbols for unused PRBs

OP.1 FDD for FDD CC,

OP.1 TDD for TDD CC

ACK/NACK feedback mode

PUCCH format 3

Downlink HARQ-ACK timing

FDD PCell

As specified in Clause 7.3.3 in TS36.213 [6]

TDD PCell

As specified in Clause 7.3.4 in TS36.213 [6]

Note 1: as specified in Table 4.2-2 in TS 36.211 [4].

Note 2: as specified in Table 4.2-1 in TS 36.211 [4].

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

8.7.5.1 TDD FDD CA Sustained data rate performance for FDD PCell

8.7.5.1.1 TDD FDD CA Sustained data rate performance for FDD PCell (2DL CA)

8.7.5.1.1.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1.1.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE category 3, 4, 6, 7, 9 and 10, and UE DL category 6, 7, 9 and 10 that support E-UTRA FDD and TDD, 2DL TDD-FDD CA with FDD as PCell and not support 256QAM in DL.

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

8.7.5.1.1.3 Minimum requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1.1.3-1 with the additional parameters specified in Table 8.7.5-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.5.1.1.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1.1.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

2

10+20

10

20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

2A

15+20

15

20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

3

10+10

10

10

36696

36696/0

R.31-3A FDD

R.31-6 TDD

85

Table 8.7.5.1.1.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 2CCs

2×20

20

20

3

3

1

1

10+20

10

20

3

3

2

2

15+20

15

20

3

3

2A

2A

10+10

10

10

3

3

3

3

Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled.

Note 2: Void.

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

8.7.5.1.1.4 Test description

8.7.5.1.1.4.1 Initial conditions

Table 8.7.5.1.1.4.1-1: Further test parameters per test

Test number

1

2

2A

3

Bandwidth

FDD CC

20

10

15

10

TDD CC

20

20

20

10

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-3A FDD

R.31-5 FDD

R.31-3A FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-6 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-1 FDD

R.1-4B FDD

R.1-1 FDD

TDD CC

NA

NA

NA

NA

TBsize per Codeword

FDD CC

75376

36696

55056

36696

TDD CC

75376/0

75376/0

75376/0

36696/0

Number of PDCP SDU per Codeword

FDD CC

7

4

6

4

TDD CC

7

7

7

4

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 184)/32)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 184)/32)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 184)/32)

PDCP SDU size [Octets]

FDD CC

1341

1141

1142

1141

TDD CC

1341

1341

1341

1141

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.

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.1.1.4.3.

8.7.5.1.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 with SCC configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.1.1.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.1.1.4.3-3A.

3. The SS activates SCC by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13,6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).

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

5. The SS looks up TBsize in Table 8.7.5.1.1.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.1.1.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.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 NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.5.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.5.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.5.1.1.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.5.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.5.1.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.5.1.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

}

}

}

}

Table 8.7.5.1.1.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

Ssp4

}

8.7.5.1.1.5 Test requirement

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

Table 8.7.5.1.1.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

2

10+20

10

20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

2A

15+20

15

20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

3

10+10

10

10

36696

36696/0

R.31-3A FDD

R.31-6 TDD

85

Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI.

Note 2: The TB success rate is defined as TB success rate = 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks.

Table 8.7.5.1.1.5-2: 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

Cat 11, 12

Total

FDD CC

TDD CC

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 2CCs

2×20

20

20

3

3

1

1

10+20

10

20

3

3

2

2

15+20

15

20

3

3

2A

2A

10+10

10

10

3

3

3

3

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

8.7.5.1.2 TDD FDD CA Sustained data rate performance for FDD PCell (3DL CA)

8.7.5.1.2.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1.2.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE category 9, 10, 11 and 12, and UE DL category 9, 10, 11 and 12 that support E-UTRA FDD and TDD, 3DL TDD-FDD CA with FDD as PCell and not support 256QAM in DL.

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

8.7.5.1.2.3 Minimum requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1.2.3-1 with the additional parameters specified in Table 8.7.5-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.5.1.2.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1.2.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

2

10+20

10

20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

2A

15+20

15

20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

4

3×20

20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

5

15+20+20

15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

6

10+20+20

10

2×20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

7

3×20

2×20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8

20+20+15

20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

9

20+20+10

20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

Table 8.7.5.1.2.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 3CCs

3×20

20

2×20

1

4

4

15+20+20

15

2×20

2A

5

5

10+20+20

10

2×20

2

6

6

3×20

2×20

20

1

7

7

20+20+15

20+15

20

1

8

8

20+20+10

20+10

20

1

9

9

Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled.

Note 2: Void.

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

8.7.5.1.2.4 Test description

8.7.5.1.2.4.1 Initial conditions

Table 8.7.5.1.2.4.1-1: Further test parameters per test

Test number

1

2

2A

4

5

6

7

8

9

Bandwidth

FDD CC

20

10

15

20

15

20

2×20

20+15

20+10

TDD CC

20

20

20

2×20

2×20

2×20

20

20

20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-3A FDD

R.31-5 FDD

R.31-4 FDD

R.31-5 FDD

R.31-4 FDD

R.31-4 FDD

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC,

R.31-3A FDD for 10MHz CC

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-1 FDD

R.1-4B FDD

R.1-4 FDD

R.1-4B FDD

R.1-4 FDD

R.1-4 FDD

R.1-4 FDD for 20MHz CC,

R.1-4B FDD for 15MHz CC

R.1-4 FDD for 20MHz CC,

R.1-1 FDD for 10MHz CC

TDD CC

NA

NA

NA

NA

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

75376

36696

55056

75376

55056

75376

75376

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

36696 for 10MHz CC

TDD CC

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

4

6

7

6

7

7

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

4 for 10MHz CC

TDD CC

7

7

7

7

7

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 184)/32)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

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

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

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

FLOOR((TBsize – 184)/32) for 10MHz CC

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1141

1142

1341

1142

1341

1341

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1141 for 10MHz CC

TDD CC

1341

1341

1341

1341

1341

1341

1341

1341

1341

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.

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.1.2.4.3.

8.7.5.1.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 SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.1.2.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.1.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 TBsize in Table 8.7.5.1.2.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.1.2.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.1.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 NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.5.1.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.5.1.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.5.1.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.5.1.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.5.1.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.5.1.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

}

}

}

}

Table 8.7.5.1.2.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

Ssp4

}

8.7.5.1.2.5 Test requirement

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

Table 8.7.5.1.2.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

2

10+20

10

20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

2A

15+20

15

20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

4

3×20

20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

5

15+20+20

15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

6

10+20+20

10

2×20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

7

3×20

2×20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8

20+20+15

20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

9

20+20+10

20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

Table 8.7.5.1.2.5-2: 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

Cat 11, 12

Total

FDD CC

TDD CC

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 3CCs

3×20

20

2×20

1

4

4

15+20+20

15

2×20

2A

5

5

10+20+20

10

2×20

2

6

6

3×20

2×20

20

1

7

7

20+20+15

20+15

20

1

8

8

20+20+10

20+10

20

1

9

9

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

Note 3: Test 1, Test 2 and Test 2A are tested in 8.7.5.1.1.

8.7.5.1.3 TDD FDD CA Sustained data rate performance for FDD PCell (4DL CA)

8.7.5.1.3.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1.3.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE category 11 and 12, and UE DL category 11, 12 and 15 that support E-UTRA FDD and TDD, 4DL TDD-FDD CA with FDD as PCell and not support 256QAM in DL.

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

8.7.5.1.3.3 Minimum requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1.3.3-1 with the additional parameters specified in Table 8.7.5-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.5.1.3.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1.3.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

4

3×20

20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

5

15+20+20

15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

7

3×20

2×20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8

20+20+15

20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

10

4×20

20

3×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

11

4×20

2×20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

13

2×15+2×20

2×15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

14

3×20+15

2×20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15A

3×20+10

2×20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

15B

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.1.3.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 4CCs

4×20

20

3×20

4

10

10

4×20

2×20

2×20

4 or 7

11

11

3×20+15

20+15

2×20

4

12

12

2×15+2×20

2×15

2×20

5

13

13

3×20+15

2×20+15

20

7

14

14

2×15+2×20

2×15+20

20

8

15

15

3×20+10

2×20+10

20

7

15A

15A

2×15+2×20

2×15+20

20

8

15B

15B

Note 1: Void.

Note 2: Void.

Note 3: 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.5.1

8.7.5.1.3.4 Test description

8.7.5.1.3.4.1 Initial conditions

Table 8.7.5.1.3.4.1-1: Further test parameters per test (Test number #4 – #11)

Test number

4

5

7

8

10

11

Bandwidth

FDD CC

20

15

2×20

20+15

20

2×20

TDD CC

2×20

2×20

20

20

3×20

2×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-5 FDD

R.31-4 FDD

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD

R.31-4 FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-4B FDD

R.1-4 FDD

R.1-4 FDD for 20MHz CC,

R.1-4B FDD for 15MHz CC

R.1-4 FDD

R.1-4 FDD

TDD CC

NA

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

75376

55056

75376

75376 for 20MHz CC,

55056 for 15MHz CC

75376

75376

TDD CC

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

6

7

7 for 20MHz CC,

6 for 15MHz CC

7

7

TDD CC

7

7

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 264)/56)

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

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

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1142

1341

1341 for 20MHz CC,

1142 for 15MHz CC

1341

1341

TDD CC

1341

1341

1341

1341

1341

1341

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.

Table 8.7.5.1.3.4.1-2: Further test parameters per test (Test number #12 – #15B)

Test number

12

13

14

15

15A

15B

Bandwidth

FDD CC

20+15

2×15

2×20+15

2×15+20

2×20+10

2×15+20

TDD CC

2×20

2×20

20

20

20

20

DL Measurement channel

FDD CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-5 FDD

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC,

R.31-3A FDD for 10MHz CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

R.1-4 FDD for 20MHz CC,

R.1-4B FDD for 15MHz CC

R.1-4B FDD

R.1-4 FDD for 20MHz CC,

R.1-4B FDD for 15MHz CC

R.1-4 FDD for 20MHz CC,

R.1-4B FDD for 15MHz CC

R.1-4 FDD for 20MHz CC,

R.1-1 FDD for 10MHz CC

R.1-4 FDD for 20MHz CC,

R.1-4B FDD for 15MHz CC

TDD CC

NA

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

75376 for 20MHz CC,

55056 for 15MHz CC

55056

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

36696 for 10MHz CC

75376 for 20MHz CC,

55056 for 15MHz CC

TDD CC

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7 for 20MHz CC,

6 for 15MHz CC

6

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

4 for 10MHz CC

7 for 20MHz CC,

6 for 15MHz CC

TDD CC

7

7

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

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

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

FLOOR((TBsize – 240)/48)

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

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

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

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

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

FLOOR((TBsize – 184)/32) for 10MHz CC

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

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

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341 for 20MHz CC,

1142 for 15MHz CC

1142

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1141 for 10MHz CC

1341 for 20MHz CC,

1142 for 15MHz CC

TDD CC

1341

1341

1341

1341

1341

1341

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.

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

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.1.3.4.3.

8.7.5.1.3.4.2 Test procedure

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

2. The SS shall configure SCCs as per TS 36.508 [7] clause 5.2A.4 with SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.1.3.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.1.3.4.3-3A.

3. The SS activates SCCs by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).

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

5. The SS looks up TBsize in Table 8.7.5.1.3.4.1-1 and Table 8.7.5.1.3.4.1-2 for the tests to be performed depending on the UE category according to Table 8.7.5.1.3.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.1.3.4.1-1 and Table 8.7.5.1.3.4.1-2 (Note 1). The SS ciphers the PDCP SDUs, concatenates the resultant PDCP PDUs to form an RLC PDU and then a MAC PDU. The SS transmits the MAC PDU. The SS increments then NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.5.1.3.5-1" and B = 0.

NOTE 1: In case of RLC PDU retransmission, the number of new required PDCP SDUs is as many as to fill the rest of TB.

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

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A

Information Element

Value/remark

Comment

Condition

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.5.1.3.4.3-2: SecurityModeCommand (in the preamble)

Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19

Information Element

Value/remark

Comment

Condition

SecurityModeCommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

securityModeCommand-r8 SEQUENCE {

securityConfiguration SEQUENCE {

cipheringAlgorithm

eea2

nextHopChainingCount

Not present

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 8.7.5.1.3.4.3-3: PhysicalConfigDedicated-DEFAULT

Derivation Path: 36.508 clause 5.5.1, Table 5.5.1.2-1

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

antennaInfo CHOICE {

explicitValue ::= SEQUENCE {

transmissionMode

tm3

Transmission mode 3

codebookSubsetRestriction CHOICE {

n2TxAntenna-tm3

10

}

ue-TransmitAntennaSelection CHOICE {

release

NULL

}

}

}

}

Table 8.7.5.1.3.4.3-3A: PhysicalConfigDedicatedSCell-r10-DEFAULT

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

antennaInfo-r10 CHOICE {

transmissionMode-r10

tm3

Transmission mode 3

codebookSubsetRestriction-r10

10

ue-TransmitAntennaSelection CHOICE {

release

NULL

}

}

}

}

Table 8.7.5.1.3.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

Ssp4

}

8.7.5.1.3.5 Test requirement

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

Table 8.7.5.1.3.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

4

3×20

20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

5

15+20+20

15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

7

3×20

2×20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8

20+20+15

20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

10

4×20

20

3×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

11

4×20

2×20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

13

2×15+2×20

2×15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

14

3×20+15

2×20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15A

3×20+10

2×20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

15B

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.1.3.5-2: 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

Cat 11, 12

DL Cat. 15

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 4CCs

4×20

20

3×20

4

10

10

4×20

2×20

2×20

4 or 7

11

11

3×20+15

20+15

2×20

4

12

12

2×15+2×20

2×15

2×20

5

13

13

3×20+15

2×20+15

20

7

14

14

2×15+2×20

2×15+20

20

8

15

15

3×20+10

2×20+10

20

7

15A

15A

2×15+2×20

2×15+20

20

8

15B

15B

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

Note 3: Test 4, Test 5, Test 7, and Test 8 are tested in 8.7.5.1.2.

8.7.5.1.4 TDD FDD CA Sustained data rate performance for FDD PCell (5DL CA)

8.7.5.1.4.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1.4.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 15 that support E-UTRA FDD and TDD, 5DL TDD-FDD CA with FDD as PCell and not support 256QAM in DL.

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

8.7.5.1.4.3 Minimum requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1.4.3-1 with the additional parameters specified in Table 8.7.5-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.5.1.4.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1.4.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

11

4×20

2×20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

16

4×20+15

2×20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

17

2×15+3×20

2×15+20

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.1.4.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 5 CCs

4×20+15

2×20+15

2×20

11

16

2×15+3×20

2×15+20

2×20

12

17

Note 1: Void.

Note 2: Void.

Note 3: 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.5.1

8.7.5.1.4.4 Test description

8.7.5.1.4.4.1 Initial conditions

Table 8.7.5.1.4.4.1-1: Further test parameters per test

Test number

11

12

16

17

Bandwidth

FDD CC

2×20

20+15

2×20+15

2×15+20

TDD CC

2×20

2×20

2×20

2×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

TDD CC

NA

NA

NA

NA

TBsize per Codeword

FDD CC

75376

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

55056 for 15MHz CC

TDD CC

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

6 for 15MHz CC

TDD CC

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

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

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

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

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

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

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

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1142 for 15MHz CC

TDD CC

1341

1341

1341

1341

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.

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

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.1.4.4.3.

8.7.5.1.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 SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.1.4.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.1.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 TBsize in Table 8.7.5.1.4.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.1.4.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.1.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 NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.5.1.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.5.1.4.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.5.1.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

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.5.1.4.4.3-2: SecurityModeCommand (in the preamble)

Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19

Information Element

Value/remark

Comment

Condition

SecurityModeCommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

securityModeCommand-r8 SEQUENCE {

securityConfiguration SEQUENCE {

cipheringAlgorithm

eea2

nextHopChainingCount

Not present

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 8.7.5.1.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.5.1.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 CHOICE {

transmissionMode-r10

tm3

Transmission mode 3

codebookSubsetRestriction-r10

10

ue-TransmitAntennaSelection CHOICE {

release

NULL

}

}

}

}

Table 8.7.5.1.4.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

8.7.5.1.4.5 Test requirement

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

Table 8.7.5.1.4.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

11

4×20

2×20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

16

4×20+15

2×20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

17

2×15+3×20

2×15+20

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.1.4.5-2: 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

Cat 11, 12

DL Cat. 15

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 5 CCs

4×20+15

2×20+15

2×20

11

16

2×15+3×20

2×15+20

2×20

12

17

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

Note 3: Test 11 and 12 are tested in clause 8.7.5.1.3

8.7.5.1.5 TDD FDD CA Sustained data rate performance for FDD PCell (6DL CA)

8.7.5.1.5.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.5.1.5.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 15 that support E-UTRA FDD and TDD, 6DL TDD-FDD CA with FDD as PCell and not support 256QAM in DL.

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

8.7.5.1.5.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1.5.3-1 with the additional parameters specified in Table 8.7.5-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.5.1.5.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1.5.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

28

2×20+4×20

2×20

4×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

Table 8.7.5.1.5.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 6 CCs

20+5×20

20

5×20

27

27

2×20+4×20

2×20

4×20

28

28

Note 1: Void.

Note 2: Void.

Note 3: 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.5.1

8.7.5.1.5.4 Test description

8.7.5.1.5.4.1 Initial conditions

Table 8.7.5.1.5.4.1-1: Further test parameters per test

Test number

27

28

Bandwidth

FDD CC

20

2×20

TDD CC

5×20

4×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-4 FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-4 FDD

TDD CC

NA

NA

TBsize per Codeword

FDD CC

75376

75376

TDD CC

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

7

TDD CC

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1341

TDD CC

1341

1341

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.

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

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.1.5.4.3.

8.7.5.1.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 SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.1.5.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.1.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 TBsize in Table 8.7.5.1.5.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.1.5.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.1.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 NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

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

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A

Information Element

Value/remark

Comment

Condition

UE test loop mode A LB setup

Length of UE test loop mode A LB setup list in bytes

0 0 0 0 0 0 1 1

Length of one LB setup DRB (3 bytes)

LB setup DRB

0 0 0 0 0 0 0 0,

0 0 1 0 1 0 0 0,

0 0 0 Q4 Q3 Q2 Q1 Q0

UL PDCP SDU size = 40 bits (5 bytes)

Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1

Table 8.7.5.1.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.5.1.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.5.1.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

}

}

}

}

Table 8.7.5.1.5.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

8.7.5.1.5.5 Test Requirements

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

Table 8.7.5.1.5.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

28

2×20+4×20

2×20

4×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

Table 8.7.5.1.5.5-2: 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

Cat 11, 12

DL Cat. 15

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 6 CCs

20+5×20

20

5×20

27

27

2×20+4×20

2×20

4×20

28

28

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

8.7.5.1.6 TDD FDD CA Sustained data rate performance for FDD PCell (7DL CA)

8.7.5.1.6.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.5.1.6.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 15 that support E-UTRA FDD and TDD, 7DL TDD-FDD CA with FDD as PCell and not support 256QAM in DL.

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

8.7.5.1.6.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1.6.3-1 with the additional parameters specified in Table 8.7.5-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.5.1.6.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1.6.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

29

20+6×20

20

6×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

30

2×20+5×20

2×20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

Table 8.7.5.1.6.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 7 CCs

20+6×20

20

6×20

29

29

2×20+5×20

2×20

5×20

30

30

Note 1: Void.

Note 2: Void.

Note 3: 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.5.1

8.7.5.1.6.4 Test description

8.7.5.1.6.4.1 Initial conditions

Table 8.7.5.1.6.4.1-1: Further test parameters per test

Test number

29

30

Bandwidth

FDD CC

20

2×20

TDD CC

6×20

5×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-4 FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-4 FDD

TDD CC

NA

NA

TBsize per Codeword

FDD CC

75376

75376

TDD CC

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

7

TDD CC

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1341

TDD CC

1341

1341

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.

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

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.1.6.4.3.

8.7.5.1.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 SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.1.6.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.1.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 TBsize in Table 8.7.5.1.6.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.1.6.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.1.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 NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

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

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A

Information Element

Value/remark

Comment

Condition

UE test loop mode A LB setup

Length of UE test loop mode A LB setup list in bytes

0 0 0 0 0 0 1 1

Length of one LB setup DRB (3 bytes)

LB setup DRB

0 0 0 0 0 0 0 0,

0 0 1 0 1 0 0 0,

0 0 0 Q4 Q3 Q2 Q1 Q0

UL PDCP SDU size = 40 bits (5 bytes)

Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1

Table 8.7.5.1.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.5.1.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.5.1.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

}

}

}

}

Table 8.7.5.1.6.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

8.7.5.1.6.5 Test Requirements

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

Table 8.7.5.1.6.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

29

20+6×20

20

6×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

30

2×20+5×20

2×20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

Table 8.7.5.1.6.5-2: 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

Cat 11, 12

DL Cat. 15

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 7 CCs

20+6×20

20

6×20

29

29

2×20+5×20

2×20

5×20

30

30

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

8.7.5.1_H TDD FDD CA Sustained data rate performance for FDD PCell 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.5.1_H.1 TDD FDD CA Sustained data rate performance for FDD PCell (2DL CA) for 256QAM in DL
8.7.5.1_H.1.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1_H.1.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 11, 12 and 13 that support 256QAM in DL and support E-UTRA FDD and TDD, 2DL TDD-FDD CA with FDD as PCell.

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

8.7.5.1_H.1.3 Minimum requirements

For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1_H.1.3-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with the maximum aggregated bandwidth as specified in Table 8.7.5.1_H.1.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.5.1.1.3-1 is not applicable.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1_H.1.3-1: Minimum requirement (TDD FDD CA 256QAM)

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

R.68 FDD

R.68 TDD

85

2

10+20

10

20

R.68-2 FDD

R.68 TDD

85

3

15+20

15

20

R.68-1 FDD

R.68 TDD

85

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

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 2CCs

2×20

20

20

1

1

10+20

10

20

2

2

15+20

15

20

3

3

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

8.7.5.1_H.1.4 Test description

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

– Instead of Table 8.7.5.1.1.4.1-1 ‑> use Table 8.7.5.1_H.1.4-1.

– Instead of Table 8.7.5.1.1.5-1 ‑> use Table 8.7.5.1_H.1.5-1.

– Instead of Table 8.7.5.1.1.5-2 ‑> use Table 8.7.5.1_H.1.5-2.

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

Test number

1

2

3

Bandwidth

FDD CC

20

10

15

TDD CC

20

20

20

DL Measurement channel

FDD CC

R.68 FDD

R.68-2 FDD

R.68-1 FDD

TDD CC

R.68 FDD

R.68 FDD

R.68 FDD

UL channel

FDD CC

R.1-4 FDD

R.1-1 FDD

R.1-4B FDD

TDD CC

NA

NA

NA

TBsize per Codeword

FDD CC

97896(Note 3)

48936(Note 5)

75376(Note 4)

TDD CC

97896/0(Note 6)

97896/0(Note 6)

97896/0(Note 6)

Number of PDCP SDU per Codeword

FDD CC

10

5

7

TDD CC

10/0

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 208)/40)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219

1218

1341

TDD CC

1219/0

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – 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.

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: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

8.7.5.1_H.1.5 Test requirement

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

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

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

R.68 FDD

R.68 TDD

85

2

10+20

10

20

R.68-2 FDD

R.68 TDD

85

3

15+20

15

20

R.68-1 FDD

R.68 TDD

[85]

Table 8.7.5.1_H.1.5-2: Test applicability per UE category

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 2CCs

2×20

20

20

1

1

10+20

10

20

2

2

15+20

15

20

3

3

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: 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.5.1_H.2 TDD FDD CA Sustained data rate performance for FDD PCell (3DL CA) for 256QAM in DL

8.7.5.1_H.2.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1_H.2.2 Test applicability

This test applies to Release 12 and forward of UE DL category 11, 12 and 15 UE that support 256QAM in DL and E-UTRA FDD and TDD, 3DL TDD-FDD CA with FDD as PCell.

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

8.7.5.1_H.2.3 Minimum requirements

For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1_H.2.3-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with the maximum aggregated bandwidth as specified in Table 8.7.5.1_H.2.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.5.1.2.3-1 is not applicable.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1_H.2.3-1: Minimum requirement (TDD FDD CA 256QAM)

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

R.68 FDD

R.68 TDD

85

2

10+20

10

20

R.68-2 FDD

R.68 TDD

85

3

15+20

15

20

R.68-1 FDD

R.68 TDD

85

4

3×20

20

2×20

R.68 FDD

R.68 TDD

85

5

15+20+20

15

2×20

R.68-1 FDD

R.68 TDD

85

6

10+20+20

10

2×20

R.68-2 FDD

R.68TDD

85

7

3×20

2×20

20

R.68 FDD

R.68 TDD

85

8

20+20+15

20+15

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

9

20+20+10

20+10

20

R.68 FDD for 20MHz CC, R.68-2 FDD for 10MHz CC

R.68 TDD

85

9A

20+10+10

2×10

20

R.68-2 FDD

R.68 TDD

85

Table 8.7.5.1_H.2.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 3CCs

3×20

20

2×20

4

1

4

15+20+20

15

2×20

5

3

5

10+20+20

10

2×20

6

2

6

3×20

2×20

20

7

1

7

20+20+15

20+15

20

8

1

8

20+20+10

20+10

20

9

1

9

20+10+10

2×10

20

9A

2

9A

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

8.7.5.1_H.2.4 Test description

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

– Instead of Table 8.7.5.1.2.4.1-1 ‑> use Table 8.7.5.1_H.2.4-1 and Table 8.7.5.1_H.2.4-2.

– Instead of Table 8.7.5.1.2.5-1 ‑> use Table 8.7.5.1_H.2.5-1.

– Instead of Table 8.7.5.1.2.5-2 ‑> use Table 8.7.5.1_H.2.5-2.

Table 8.7.5.1_H.2.4-1: Further test parameters per test (Test number #1 – #5)

Test number

1

2

3

4

5

Bandwidth

FDD CC

20

10

15

20

15

TDD CC

20

20

20

2×20

2×20

DL Measurement channel

FDD CC

R.68 FDD

R.68-2 FDD

R.68-1 FDD

R.68 FDD

R.68-1 FDD

TDD CC

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-1 FDD

R.1-4B FDD

R.1-4 FDD

R.1-4B FDD

TDD CC

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

97896(Note 3)

48936(Note 5)

75376(Note 4)

97896(Note 3)

75376(Note 4)

TDD CC

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

Number of PDCP SDU per Codeword

FDD CC

10

5

7

10

7

TDD CC

10/0

10/0

10/0

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 208)/40)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219

1218

1341

1219

1341

TDD CC

1219/0

1219/0

1219/0

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – 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.

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: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

Table 8.7.5.1_H.2.4-2: Further test parameters per test (Test number #6 – #9A)

Test number

6

7

8

9

9A

Bandwidth

FDD CC

10

2×20

20+15

20+10

2×10

TDD CC

2×20

20

20

20

20

DL Measurement channel

FDD CC

R.68-2 FDD

R.68 FDD

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-2 FDD for 10MHz CC

R.68-2 FDD

TDD CC

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

UL channel

FDD CC

R.1-1 FDD

R.1-4 FDD

R.1-4 FDD for 20MHz CC, R.1-4B FDD for 15MHz CC

R.1-4 FDD for 20MHz CC, R.1-1 FDD for 10MHz CC

R.1-1 FDD

TDD CC

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

48936(Note 5)

97896(Note 3)

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

97896(Note 3) for 20MHz CC, 48936(Note 5) for 10MHz CC

48936(Note 5)

TDD CC

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

Number of PDCP SDU per Codeword

FDD CC

5

10

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 5 for 10MHz CC

5

TDD CC

10/0

10/0

10/0

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 208)/40)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 208)/40) for 10MHz CC

FLOOR((TBsize – 208)/40)

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1218

1219

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1218 for 10MHz CC

1218

TDD CC

1219/0

1219/0

1219/0

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – 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.

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: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

8.7.5.1_H.2.5 Test requirement

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

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

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

R.68 FDD

R.68 TDD

85

2

10+20

10

20

R.68-2 FDD

R.68 TDD

85

3

15+20

15

20

R.68-1 FDD

R.68 TDD

85

4

3×20

20

2×20

R.68 FDD

R.68 TDD

85

5

15+20+20

15

2×20

R.68-1 FDD

R.68 TDD

85

6

10+20+20

10

2×20

R.68-2 FDD

R.68TDD

85

7

3×20

2×20

20

R.68 FDD

R.68 TDD

85

8

20+20+15

20+15

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

9

20+20+10

20+10

20

R.68 FDD for 20MHz CC, R.68-2 FDD for 10MHz CC

R.68 TDD

85

9A

20+10+10

2×10

20

R.68-2 FDD

R.68 TDD

85

Table 8.7.5.1_H.2.5-2: Test applicability per UE category

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 3CCs

3×20

20

2×20

4

1

4

15+20+20

15

2×20

5

3

5

10+20+20

10

2×20

6

2

6

3×20

2×20

20

7

1

7

20+20+15

20+15

20

8

1

8

20+20+10

20+10

20

9

1

9

20+10+10

2×10

20

9A

2

9A

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

Note 3: Test 1, 2, and 3 are tested in 8.7.5.1_H.1.

8.7.5.1_H.3 TDD FDD CA Sustained data rate performance for FDD PCell (4DL CA) for 256QAM in DL

8.7.5.1_H.3.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1_H.3.2 Test applicability

This test applies to Release 12 and forward of UE DL category 15 and 16 that support 256QAM in DL and E-UTRA FDD and TDD, 4DL TDD-FDD CA with FDD as PCell.

8.7.5.1_H.3.3 Minimum requirements

For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1_H.3.3-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with the maximum aggregated bandwidth as specified in Table 8.7.5.1_H.3.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.5.1.3.3-1 is not applicable.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1_H.3.3-1: Minimum requirement (TDD FDD CA 256QAM)

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

4

3×20

20

2×20

R.68 FDD

R.68 TDD

85

5

15+20+20

15

2×20

R.68-1 FDD

R.68 TDD

85

7

3×20

2×20

20

R.68 FDD

R.68 TDD

85

8

20+20+15

20+15

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

10

4×20

20

3×20

R.68-2 FDD

R.68TDD

85

11

4×20

2×20

2×20

R.68 FDD

R.68 TDD

85

12

3×20+15

20+15

2×20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

13

2×15+2×20

2×15

2×20

R.68-1 FDD

R.68 TDD

85

14

3×20+15

2×20+15

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

15

2×15+2×20

2×15+20

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

15A

3×20+10

2×20+10

20

R.68 FDD for 20MHz CC, R.68-2 FDD for 10MHz CC

R.68 TDD

85

Table 8.7.5.1_H.3.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 4CCs

4×20

20

3×20

4

10

10

4×20

2×20

2×20

4 or 7

11

11

3×20+15

20+15

2×20

8

12

12

2×15+2×20

2×15

2×20

5

13

13

3×20+15

2×20+15

20

7

14

14

2×15+2×20

2×15+20

20

8

15

15

3×20+10

2×20+10

20

7

15A

15A

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

8.7.5.1_H.3.4 Test description

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

– Instead of Table 8.7.5.1.3.4.1-1 ‑> use Table 8.7.5.1_H.3.4-1 and Table 8.7.5.1_H.3.4-2.

– Instead of Table 8.7.5.1.3.5-1 ‑> use Table 8.7.5.1_H.3.5-1.

– Instead of Table 8.7.5.1.3.5-2 ‑> use Table 8.7.5.1_H.3.5-2.

Table 8.7.5.1_H.3.4-1: Further test parameters per test (Test number #4 – #10)

Test number

4

5

7

8

10

Bandwidth

FDD CC

20

15

2×20

20+15

20

TDD CC

2×20

2×20

20

20

3×20

DL Measurement channel

FDD CC

R.68 FDD

R.68-1 FDD

R.68 FDD

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD

TDD CC

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-4B FDD

R.1-4 FDD

R.1-4 FDD for 20MHz CC, R.1-4B FDD for 15MHz CC

R.1-4 FDD

TDD CC

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

97896(Note 3)

75376(Note 4)

97896(Note 3)

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

97896(Note 3)

TDD CC

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

Number of PDCP SDU per Codeword

FDD CC

10

7

10

10 for 20MHz CC, 7 for 15MHz CC

10

TDD CC

10/0

10/0

10/0

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80)

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219

1341

1219

1219 for 20MHz CC, 1341 for 15MHz CC

1219

TDD CC

1219/0

1219/0

1219/0

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – 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.

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: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

Table 8.7.5.1_H.3.4-2: Further test parameters per test (Test number #11 – #15A)

Test number

11

12

13

14

15

15A

Bandwidth

FDD CC

2×20

20+15

2×15

2×20+15

2×15+20

2×20+10

TDD CC

2×20

2×20

2×20

20

20

20

DL Measurement channel

FDD CC

R.68 FDD

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68-1 FDD

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-2 FDD for 10MHz CC

TDD CC

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-4 FDD for 20MHz CC, R.1-4B FDD for 15MHz CC

R.1-4B FDD

R.1-4 FDD for 20MHz CC, R.1-4B FDD for 15MHz CC

R.1-4 FDD for 20MHz CC, R.1-4B FDD for 15MHz CC

R.1-4 FDD for 20MHz CC, R.1-1 FDD for 10MHz CC

TDD CC

NA

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

97896(Note 3)

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

75376(Note 4)

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

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

97896(Note 3) for 20MHz CC, 48936(Note 5) for 10MHz CC

TDD CC

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

Number of PDCP SDU per Codeword

FDD CC

10

10 for 20MHz CC, 7 for 15MHz CC

7

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 5 for 10MHz CC

TDD CC

10/0

10/0

10/0

10/0

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((Tbsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((Tbsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((Tbsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((Tbsize – 208)/40) for 10MHz CC

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219

1219 for 20MHz CC, 1341 for 15MHz CC

1341

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1218 for 10MHz CC

TDD CC

1219/0

1219/0

1219/0

1219/0

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (Tbsize – 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.

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: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

8.7.5.1_H.3.5 Test requirement

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

Table 8.7.5.1_H.3.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

4

3×20

20

2×20

R.68 FDD

R.68 TDD

85

5

15+20+20

15

2×20

R.68-1 FDD

R.68 TDD

85

7

3×20

2×20

20

R.68 FDD

R.68 TDD

85

8

20+20+15

20+15

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

10

4×20

20

3×20

R.68-2 FDD

R.68TDD

85

11

4×20

2×20

2×20

R.68 FDD

R.68 TDD

85

12

3×20+15

20+15

2×20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

13

2×15+2×20

2×15

2×20

R.68-1 FDD

R.68 TDD

85

14

3×20+15

2×20+15

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

15

2×15+2×20

2×15+20

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

15A

3×20+10

2×20+10

20

R.68 FDD for 20MHz CC, R.68-2 FDD for 10MHz CC

R.68 TDD

85

Table 8.7.5.1_H.3.5-2: Test applicability per UE category

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 4CCs

4×20

20

3×20

4

10

10

4×20

2×20

2×20

4 or 7

11

11

3×20+15

20+15

2×20

8

12

12

2×15+2×20

2×15

2×20

5

13

13

3×20+15

2×20+15

20

7

14

14

2×15+2×20

2×15+20

20

8

15

15

3×20+10

2×20+10

20

7

15A

15A

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

Note 3: Test 4, 5, 7, and 8 are tested in 8.7.5.1_H.2.

8.7.5.1_H.4 TDD FDD CA Sustained data rate performance for FDD PCell (5DL CA) for 256QAM in DL

8.7.5.1_H.4.1 Test purpose

Same test purpose as in clause 8.7.1.1.

8.7.5.1_H.4.2 Test applicability

This test applies to Release 12 and forward of UE DL category 16 that support 256QAM in DL and E-UTRA FDD and TDD, 5DL TDD-FDD CA with FDD as PCell.

8.7.5.1_H.4.3 Minimum requirements

For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1_H.4.3-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with the maximum aggregated bandwidth as specified in Table 8.7.5.1_H.4.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.5.1.4.3-1 is not applicable.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1_H.4.3-1: Minimum requirement (TDD FDD CA 256QAM)

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

12

3×20+15

20+15

2×20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

14

3×20+15

2×20+15

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

15

2×15+2×20

2×15+20

20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

16

4×20+15

2×20+15

2×20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

17

2×15+3×20

2×15+20

2×20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

Table 8.7.5.1_H.4.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 5CCs

4×20+15

2×20+15

2×20

14 or 12

16

2×15+3×20

2×15+20

2×20

15 or 12

17

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

8.7.5.1_H.4.4 Test description

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

– Instead of Table 8.7.5.1.4.4.1-1 ‑> use Table 8.7.5.1_H.4.4-1.

– Instead of Table 8.7.5.1.4.5-1 ‑> use Table 8.7.5.1_H.4.5-1.

– Instead of Table 8.7.5.1.4.5-2 ‑> use Table 8.7.5.1_H.4.5-2.

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

Test number

12

14

15

16

17

Bandwidth

FDD CC

20+15

2×20+15

2×15+20

2×20+15

2×15+20

TDD CC

2×20

20

20

2×20

2×20

DL Measurement channel

FDD CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

TDD CC

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

UL channel

FDD CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

TDD CC

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

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

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

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

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

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

TDD CC

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

Number of PDCP SDU per Codeword

FDD CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

TDD CC

10/0

10/0

10/0

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

TDD CC

1219/0

1219/0

1219/0

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – 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.

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: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

8.7.5.1_H.4.5 Test requirement

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

Table 8.7.5.1_H.4.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

16

4×20+15

2×20+15

2×20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

17

2×15+3×20

2×15+20

2×20

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 TDD

85

Table 8.7.5.1_H.4.5-2: Test applicability per UE category

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 5CCs

4×20+15

2×20+15

2×20

14 or 12

16

2×15+3×20

2×15+20

2×20

15 or 12

17

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category.

Note 3: Test 12, 14, and 15 are tested in clause 8.7.5.1_H.3.

8.7.5.1_H.5 TDD FDD CA Sustained data rate performance for FDD PCell (6DL CA) for 256QAM in DL

8.7.5.1_H.5.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.5.1_H.5.2 Test applicability

This test applies to Release 12 and forward of UE DL category 16 that support 256QAM in DL and E-UTRA FDD and TDD, 6DL TDD-FDD CA with FDD as PCell.

8.7.5.1_H.5.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.1_H.5.3-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with the maximum aggregated bandwidth as specified in Table 8.7.5.1_H.5.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.5.1.5.3-1 is not applicable.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.1_H.5.3-1: Minimum requirement (TDD FDD CA 256QAM)

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

R.68-2 FDD

R.68 TDD

85

28

2×20+4×20

2×20

4×20

R.68-2 FDD

R.68 TDD

85

Table 8.7.5.1_H.5.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 6CCs

20+5×20

20

5×20

27

2×20+4×20

2×20

4×20

28

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

8.7.5.1_H.5.4 Test description

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

– Instead of Table 8.7.5.1.5.4.1-1 ‑> use Table 8.7.5.1_H.5.4-1.

– Instead of Table 8.7.5.1.5.5-1 ‑> use Table 8.7.5.1_H.5.5-1.

– Instead of Table 8.7.5.1.5.5-2 ‑> use Table 8.7.5.1_H.5.5-2.

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

Test number

27

28

Bandwidth

FDD CC

20

5×20

TDD CC

2×20

4×20

DL Measurement channel

FDD CC

R.68-2 FDD

R.68-2 FDD

TDD CC

R.68 TDD

R.68 TDD

UL channel

FDD CC

R.1-4 FDD

R.1-4 FDD

TDD CC

NA

NA

TBsize per Codeword

FDD CC

97896(Note 3)

97896(Note 3)

TDD CC

97896/0

(Note 4)

97896/0

(Note 4)

Number of PDCP SDU per Codeword

FDD CC

10

10

TDD CC

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219

1219

TDD CC

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – 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.

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

8.7.5.1_H.5.5 Test Requirements

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

Table 8.7.5.1_H.5.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

R.68-2 FDD

R.68 TDD

85

28

2×20+4×20

2×20

4×20

R.68-2 FDD

R.68 TDD

85

Table 8.7.5.1_H.5.5-2: Test applicability per UE category

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 6CCs

20+5×20

20

5×20

27

2×20+4×20

2×20

4×20

28

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category.

8.7.5.2 TDD FDD CA Sustained data rate performance for TDD PCell

8.7.5.2.1 TDD FDD CA Sustained data rate performance for TDD PCell (2DL CA)

8.7.5.2.1.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.5.2.1.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE category 3, 4, 6, 7, 9 and 10 and UE DL category 6, 7, 9 and 10 that support E-UTRA FDD and TDD, 2DL TDD-FDD CA with TDD as PCell and not support 256QAM in DL.

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

8.7.5.2.1.3 Minimum requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.2.1.3-1 with the additional parameters specified in Table 8.7.5-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.5.2.1.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.2.1.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

2

10+20

10

20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

2A

15+20

15

20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

3

10+10

10

10

36696

36696/0

R.31-3A FDD

R.31-6 TDD

85

Table 8.7.5.2.1.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 2CCs

2×20

20

20

3

3

1

1

10+20

10

20

3

3

2

2

15+20

15

20

3

3

2A

2A

Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled.

Note 2: Void

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

8.7.5.2.1.4 Test description

8.7.5.2.1.4.1 Initial conditions

Table 8.7.5.2.1.4.1-1: Further test parameters per test

Test number

1

2

2A

3

Bandwidth

FDD CC

20

10

15

10

TDD CC

20

20

20

10

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-3A FDD

R.31-5 FDD

R.31-3A FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-6 TDD

UL channel

FDD CC

NA

NA

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-5 TDD

TBsize per Codeword

FDD CC

75376

36696

55056

36696

TDD CC

75376/0

75376/0

75376/0

36696/0

Number of PDCP SDU per Codeword

FDD CC

7

4

6

4

TDD CC

7

7

7

4

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 184)/32)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 184)/32)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 184)/32)

PDCP SDU size [Octets]

FDD CC

1341

1141

1142

1141

TDD CC

1341

1341

1341

1141

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.

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.2.1.4.3.

8.7.5.2.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 with SCC configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.2.1.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.2.1.4.3-3A.

3. The SS activates SCC by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).

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

5. The SS looks up TBsize in Table 8.7.5.2.1.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.2.1.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.2.1.4.1-1 (Note 1). The SS ciphers the PDCP SDUs, concatenates the resultant PDCP PDUs to form an RLC PDU and then a MAC PDU. The SS transmits the MAC PDU. The SS increments then NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.5.2.1.5-1" and B = 0.

NOTE 1: In case of RLC PDU retransmission, the number of new required PDCP SDUs is as many as to fill the rest of TB.

8.7.5.2.1.4.3 Message contents

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

Table 8.7.5.2.1.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.5.2.1.4.3-2: SecurityModeCommand (in the preamble)

Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19

Information Element

Value/remark

Comment

Condition

SecurityModeCommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

securityModeCommand-r8 SEQUENCE {

securityConfiguration SEQUENCE {

cipheringAlgorithm

eea2

nextHopChainingCount

Not present

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 8.7.5.2.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.5.2.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

}

}

}

}

Table 8.7.5.2.1.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

Ssp4

}

8.7.5.2.1.5 Test requirement

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

Table 8.7.5.2.1.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

2

10+20

10

20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

2A

15+20

15

20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

3

10+10

10

10

36696

36696/0

R.31-3A FDD

R.31-6 TDD

85

Note 1: For 2 layer transmissions, 2 transport blocks are received within a TTI.

Note 2: The TB success rate is defined as TB success rate = 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks.

Table 8.7.5.2.1.5-2: 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

Cat 11, 12

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

Total

FDD CC

TDD CC

CA with 2CCs

2×20

20

20

3

3

1

1

10+20

10

20

3

3

2

2

15+20

15

20

3

3

2A

2A

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

8.7.5.2.2 TDD FDD CA Sustained data rate performance for TDD PCell (3DL CA)

8.7.5.2.2.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.5.2.2.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE category 9, 10, 11 and 12, and UE DL category 9, 10,11 and 12 that support E-UTRA FDD and TDD, 3DL TDD-FDD CA with TDD as PCell and not support 256QAM in DL.

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

8.7.5.2.2.3 Minimum requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with TDD PCell are specified in Table 8.7.5.2-1 with the additional parameters specified in Table 8.7.5-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.5.2-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.2-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

1

2×20

20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

2

10+20

10

20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

2A

15+20

15

20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

3

10+10

10

10

36696

36696/0

R.31-3A FDD

R.31-6 TDD

85

4

3×20

20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

5

15+20+20

15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

6

10+20+20

10

2×20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

7

3×20

2×20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8

20+20+15

20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

9

20+20+10

20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

9A

20+10+10

2×10

20

36696

75376/0

R.31-3A

R.31-4 TDD

85

Table 8.7.5.2-2: 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

Total

FDD CC

TDD CC

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 3CCs

3×20

20

2×20

1

4

4

15+20+20

15

2×20

2A

5

5

10+20+20

10

2×20

2

6

6

3×20

2×20

20

1

7

7

20+20+15

20+15

20

1

8

8

20+20+10

20+10

20

1

9

9

20+10+10

2×10

20

2

9A

9A

Note 1: If DL category is signalled by the UE under test, then select the test point according to UE DL Category. Otherwise, select the test point according to the UE category signalled.

Note 2: Void.

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

8.7.5.2.2.4 Test description

8.7.5.2.2.4.1 Initial conditions

Table 8.7.5.2.2.4.1-1: Further test parameters per test (Test number #1 – #6)

Test number

1

2

2A

4

5

6

Bandwidth

FDD CC

20

10

15

20

15

10

TDD CC

20

20

20

2×20

2×20

2×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-3A FDD

R.31-5 FDD

R.31-4 FDD

R.31-5 FDD

R.31-3A FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

NA

NA

NA

NA

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

TBsize per Codeword

FDD CC

75376

36696

55056

75376

55056

36696

TDD CC

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

4

6

7

6

4

TDD CC

7

7

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 184)/32)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 184)/32)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1141

1142

1341

1142

1141

TDD CC

1341

1341

1341

1341

1341

1341

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.

Table 8.7.5.2.2.4.1-2: Further test parameters per test (Test number #7 – #9A)

Test number

7

8

9

9A

Bandwidth

FDD CC

2×20

20+15

20+10

2×10

TDD CC

20

20

20

20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-3A

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

NA

NA

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

TBsize per Codeword

FDD CC

75376

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

36696 for 10MHz CC

36696

TDD CC

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

4 for 10MHz CC

7

TDD CC

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

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

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

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

FLOOR((TBsize – 184)/32) for 10MHz CC

FLOOR((TBsize – 184)/32)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1141 for 10MHz CC

1141

TDD CC

1341

1341

1341

1341

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.

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.2.2.4.3.

8.7.5.2.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 SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.2.2.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.2.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 TBsize in Table 8.7.5.2.2.4.1-1 and Table 8.7.5.2.2.4.1-2 for the tests to be performed depending on the UE category according to Table 8.7.5.2.2.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.2.2.4.1-1 (Note 1) and Table 8.7.5.2.2.4.1-2 (Note 1). The SS ciphers the PDCP SDUs, concatenates the resultant PDCP PDUs to form an RLC PDU and then a MAC PDU. The SS transmits the MAC PDU. The SS increments then NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.5.2.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.5.2.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.5.2.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.5.2.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.5.2.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.5.2.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

}

}

}

}

Table 8.7.5.2.2.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

Ssp4

}

8.7.5.2.2.5 Test requirement

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

Table 8.7.5.2.2.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

4

3×20

20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

5

15+20+20

15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

6

10+20+20

10

2×20

36696

75376/0

R.31-3A FDD

R.31-4 TDD

85

7

3×20

2×20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8

20+20+15

20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

9

20+20+10

20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

9A

20+10+10

2×10

20

36696

75376/0

R.31-3A

R.31-4 TDD

85

Table 8.7.5.2.2.5-2: 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

Cat 11, 12

Total

FDD CC

TDD CC

DL Cat. 6,7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 3CCs

3×20

20

2×20

1

4

4

15+20+20

15

2×20

2A

5

5

10+20+20

10

2×20

2

6

6

3×20

2×20

20

1

7

7

20+20+15

20+15

20

1

8

8

20+20+10

20+10

20

1

9

9

20+10+10

2×10

20

2

9A

9A

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

Note 3: Test 1, 2, and 2A are tested in clause 8.7.5.2.1.

8.7.5.2.3 TDD FDD CA Sustained data rate performance for TDD PCell (4DL CA)

8.7.5.2.3.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.5.2.3.2 Test applicability

This test applies to all types of UE Release 13 and forward of UE category 11 and 12, and UE DL category 11, 12 and 15 that support E-UTRA FDD and TDD, 4DL TDD-FDD CA with TDD as PCell and not support 256QAM in DL.

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

8.7.5.2.3.3 Minimum requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with TDD PCell are specified in Table 8.7.5.2.3.3-1 with the additional parameters specified in Table 8.7.5-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.5.2.3.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.2.3.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

4

3×20

20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

5

15+20+20

15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

7

3×20

2×20

20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8

20+20+15

20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

10

4×20

20

3×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

11

4×20

2×20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

13

2×15+2×20

2×15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

14

3×20+15

2×20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15A

3×20+10

2×20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

15B

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.2.3.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 4CCs

4×20

20

3×20

4

10

10

4×20

2×20

2×20

4 or 7

11

11

3×20+15

20+15

2×20

4

12

12

2×15+2×20

2×15

2×20

5

13

13

3×20+15

2×20+15

20

7

14

14

2×15+2×20

2×15+20

20

8

15

15

3×20+10

2×20+10

20

7

15A

15A

2×15+2×20

2×15+20

20

8

15B

15B

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

8.7.5.2.3.4 Test description

8.7.5.2.3.4.1 Initial conditions

Table 8.7.5.2.3.4.1-1: Further test parameters per test (Test number #4 – #11)

Test number

4

5

7

8

10

11

Bandwidth

FDD CC

20

15

2×20

20+15

20

2×20

TDD CC

2×20

2×20

20

20

3×20

2×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-5 FDD

R.31-4 FDD

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD

R.31-4 FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

NA

NA

NA

NA

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

TBsize per Codeword

FDD CC

75376

55056

75376

75376 for 20MHz CC,

55056 for 15MHz CC

75376

75376

TDD CC

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

6

7

7 for 20MHz CC,

6 for 15MHz CC

7

7

TDD CC

7

7

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 240)/48)

FLOOR((TBsize – 264)/56)

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

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

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1142

1341

1341 for 20MHz CC,

1142 for 15MHz CC

1341

1341

TDD CC

1341

1341

1341

1341

1341

1341

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.

Table 8.7.5.2.3.4.1-2: Further test parameters per test (Test number #12 – #15B)

Test number

12

13

14

15

15A

15B

Bandwidth

FDD CC

20+15

2×15

2×20+15

2×15+20

2×20+10

2×15+20

TDD CC

2×20

2×20

20

20

20

20

DL Measurement channel

FDD CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-5 FDD

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

R.31-4 FDD for 20MHz CC,

R.31-3A FDD for 10MHz CC

R.31-4 FDD for 20MHz CC,

R.31-5 FDD for 15MHz CC

TDD CC

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

NA

NA

NA

NA

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

R.1-4 TDD

TBsize per Codeword

FDD CC

75376 for 20MHz CC,

55056 for 15MHz CC

55056

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

55056 for 15MHz CC

75376 for 20MHz CC,

36696 for 10MHz CC

75376 for 20MHz CC,

55056 for 15MHz CC

TDD CC

75376/0

75376/0

75376/0

75376/0

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7 for 20MHz CC,

6 for 15MHz CC

6

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

6 for 15MHz CC

7 for 20MHz CC,

4 for 10MHz CC

7 for 20MHz CC,

6 for 15MHz CC

TDD CC

7

7

7

7

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

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

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

FLOOR((TBsize – 240)/48)

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

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

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

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

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

FLOOR((TBsize – 184)/32) for 10MHz CC

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

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

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341 for 20MHz CC,

1142 for 15MHz CC

1142

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1142 for 15MHz CC

1341 for 20MHz CC,

1141 for 10MHz CC

1341 for 20MHz CC,

1142 for 15MHz CC

TDD CC

1341

1341

1341

1341

1341

1341

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.

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

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.2.3.4.3.

8.7.5.2.3.4.2 Test procedure

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

2. The SS shall configure SCCs as per TS 36.508 [7] clause 5.2A.4 with SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.2.3.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.2.3.4.3-3A.

3. The SS activates SCCs by sending the activation MAC-CE (Refer TS 36.321 [13], clauses 5.13, 6.1.3.8). Wait for at least 2 seconds (Refer TS 36.133, clauses 8.3.3.2).

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

5. The SS looks up TBsize in Table 8.7.5.2.3.4.1-1 and Table 8.7.5.2.3.4.1-2 for the tests to be performed depending on the UE category according to Table 8.7.5.2.3.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.2.3.4.1-1 and Table 8.7.5.2.3.4.1-2 (Note 1). The SS ciphers the PDCP SDUs, concatenates the resultant PDCP PDUs to form an RLC PDU and then a MAC PDU. The SS transmits the MAC PDU. The SS increments then NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

13. The UE passes the test if A ≥ "corresponding TB success rate according to Table 8.7.5.2.3.5-1" and B = 0.

NOTE 1: In case of RLC PDU retransmission, the number of new required PDCP SDUs is as many as to fill the rest of TB.

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

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A

Information Element

Value/remark

Comment

Condition

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.5.2.3.4.3-2: SecurityModeCommand (in the preamble)

Derivation Path: TS 36.508 clause 4.6.1 table 4.6.1-19

Information Element

Value/remark

Comment

Condition

SecurityModeCommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

securityModeCommand-r8 SEQUENCE {

securityConfiguration SEQUENCE {

cipheringAlgorithm

eea2

nextHopChainingCount

Not present

}

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 8.7.5.2.3.4.3-3: PhysicalConfigDedicated-DEFAULT

Derivation Path: 36.508 clause 5.5.1, Table 5.5.1.2-1

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

antennaInfo CHOICE {

explicitValue ::= SEQUENCE {

transmissionMode

tm3

Transmission mode 3

codebookSubsetRestriction CHOICE {

n2TxAntenna-tm3

10

}

ue-TransmitAntennaSelection CHOICE {

release

NULL

}

}

}

}

Table 8.7.5.2.3.4.3-3A: PhysicalConfigDedicatedSCell-r10-DEFAULT

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

antennaInfo-r10 CHOICE {

transmissionMode-r10

tm3

Transmission mode 3

codebookSubsetRestriction-r10

10

ue-TransmitAntennaSelection CHOICE {

release

NULL

}

}

}

}

Table 8.7.5.2.3.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

Ssp4

}

8.7.5.2.3.5 Test requirement

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

Table 8.7.5.2.3.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

10

4×20

20

3×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

11

4×20

2×20

2×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

13

2×15+2×20

2×15

2×20

55056

75376/0

R.31-5 FDD

R.31-4 TDD

85

14

3×20+15

2×20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15A

3×20+10

2×20+10

20

75376 for 20MHz CC 36696 for 10MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-3A FDD for 10MHz CC

R.31-4 TDD

85

15B

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.2.3.5-2: 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

Cat 11, 12

DL Cat. 15

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 4CCs

4×20

20

3×20

4

10

10

4×20

2×20

2×20

4 or 7

11

11

3×20+15

20+15

2×20

4

12

12

2×15+2×20

2×15

2×20

5

13

13

3×20+15

2×20+15

20

7

14

14

2×15+2×20

2×15+20

20

8

15

15

3×20+10

2×20+10

20

7

15A

15A

2×15+2×20

2×15+20

20

8

15B

15B

Note 1: Only one test point is tested. Select the largest aggregated CA bandwidth combination supported by the UE among the UE supported CA capabilities.

Note 2: The test point is selected according to the UE DL Category, or UE Category (only if UE DL Category not available) as appropriate.

Note 3: Test 4, Test 5, Test 7 and Test 8 are tested in clause 8.7.5.2.2.

8.7.5.2.4

8.7.5.2.5 TDD FDD CA Sustained data rate performance for TDD PCell (6DL CA)

8.7.5.2.5.1 Test purpose

Same test purpose as 8.7.1.1.rr

8.7.5.2.5.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 15 that support E-UTRA FDD and TDD, 6DL TDD-FDD CA with TDD as PCell and not support 256QAM in DL.

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

8.7.5.2.5.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with TDD PCell are specified in Table 8.7.5.2.5.3-1 with the additional parameters specified in Table 8.7.5-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.5.2.5.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.2.5.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

28

2×20+4×20

2×20

4×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

Table 8.7.5.2.5.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 6 CCs

20+5×20

20

5×20

27

28

2×20+4×20

2×20

4×20

27

28

Note 3: 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.5.2

8.7.5.2.5.4 Test description

8.7.5.2.5.4.1 Initial conditions

Table 8.7.5.2.5.4.1-1: Further test parameters per test

Test number

27

28

Bandwidth

FDD CC

20

2×20

TDD CC

5×20

4×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-4 FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

TBsize per Codeword

FDD CC

75376

75376

TDD CC

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

7

TDD CC

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1341

TDD CC

1341

1341

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.

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

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.2.5.4.3.

8.7.5.2.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 SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.2.5.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.2.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 TBsize in Table 8.7.5.2.5.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.2.5.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.2.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 NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

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

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A

Information Element

Value/remark

Comment

Condition

UE test loop mode A LB setup

Length of UE test loop mode A LB setup list in bytes

0 0 0 0 0 0 1 1

Length of one LB setup DRB (3 bytes)

LB setup DRB

0 0 0 0 0 0 0 0,

0 0 1 0 1 0 0 0,

0 0 0 Q4 Q3 Q2 Q1 Q0

UL PDCP SDU size = 40 bits (5 bytes)

Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1

Table 8.7.5.2.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.5.2.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.5.2.5.5.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

}

}

}

}

Table 8.7.5.2.5.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

8.7.5.2.5.5 Test Requirements

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

Table 8.7.5.2.5.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

28

2×20+4×20

2×20

4×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8.7.5.2.6 TDD FDD CA Sustained data rate performance for TDD PCell (7DL CA)

8.7.5.2.6.1 Test purpose

Same test purpose as 8.7.2.1

8.7.5.2.6.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 15 that support E-UTRA FDD and TDD, 6DL TDD-FDD CA with TDD as PCell and not support 256QAM in DL.

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

8.7.5.2.6.3 Minimum conformance requirements

For UE not supporting 256QAM, the requirements for TDD FDD CA with TDD PCell are specified in Table 8.7.5.2.6.3-1 with the additional parameters specified in Table 8.7.5-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.5.2.6.3-2. The TB success rate shall be sustained during at least 300 frames.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.2.6.3-1: test parameters for sustained downlink data rate (TDD FDD CA 64QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

29

20+6×20

20

6×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

30

2×20+5×20

2×20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

Table 8.7.5.2.6.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 6, 7

DL Cat. 9, 10

DL Cat. 11, 12

CA with 7 CCs

20+6×20

20

6×20

29

29

2×20+5×20

2×20

5×20

30

30

Note 3: 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.5.2

8.7.5.2.6.4 Test description

8.7.5.2.6.4.1 Initial conditions

Table 8.7.5.2.6.4.1-1: Further test parameters per test

Test number

29

30

Bandwidth

FDD CC

20

2×20

TDD CC

6×20

5×20

DL Measurement channel

FDD CC

R.31-4 FDD

R.31-4 FDD

TDD CC

R.31-4 TDD

R.31-4 TDD

UL channel

FDD CC

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

TBsize per Codeword

FDD CC

75376

75376

TDD CC

75376/0

75376/0

Number of PDCP SDU per Codeword

FDD CC

7

7

TDD CC

7

7

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

TDD CC

FLOOR((TBsize – 264)/56)

FLOOR((TBsize – 264)/56)

PDCP SDU size [Octets]

FDD CC

1341

1341

TDD CC

1341

1341

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.

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

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

3. Downlink signals are initially set up according to Annex C.0, C.1 and Annex C.3.2 and uplink signals according to Annex H.1 and H.3.2.

4. Propagation conditions are set according to Annex B.0.

5. Ensure the UE is in State 4A-RF according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.5.2.6.4.3.

8.7.5.2.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 SCCs configured. PhysicalConfigDedicated-DEFAULT is defined in Table 8.7.5.2.6.4.3-3, PhysicalConfigDedicatedSCell-r10-DEFAULT is defined in Table 8.7.5.2.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 TBsize in Table 8.7.5.2.6.4.1-1 for the tests to be performed depending on the UE category according to Table 8.7.5.2.6.5-2.

6. The SS sets the counters, NDL_newtx ,NDL_retx, NUL_PDCP, and NDDL_PDCP to 0.

7. For each new DL HARQ transmission the SS generates sufficient PDCP SDUs to fill up the TB in accordance with Table 8.7.5.2.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 NDL_newtx by one and NDL_PDCP by the number of new PDCP SDUs (Note 1) included in the sent MAC PDU.

8. If PHY requests a DL HARQ retransmission, the SS performs a HARQ retransmission and increments NDL_retx by one.

9. Steps 7 to 8 are repeated at every TTI for at least 300 frames and the SS waits for 300ms to let any HARQ retransmissions and RLC retransmissions to finish.

10. For each PDCP SDU received at the SS, if the content of the data matches that of the truncated version of the original PDCP SDU generated at the SS, the SS increments NUL_PDCP by one

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

12. The SS calculates the PDCP SDU loss as B = NDL_PDCP – NUL_PDCP

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

Derivation Path: 36.508 clause 4.7A table 4.7A-3 with condition UE TEST LOOP MODE A

Information Element

Value/remark

Comment

Condition

UE test loop mode A LB setup

Length of UE test loop mode A LB setup list in bytes

0 0 0 0 0 0 1 1

Length of one LB setup DRB (3 bytes)

LB setup DRB

0 0 0 0 0 0 0 0,

0 0 1 0 1 0 0 0,

0 0 0 Q4 Q3 Q2 Q1 Q0

UL PDCP SDU size = 40 bits (5 bytes)

Q4..Q0 = Data Radio Bearer identity number for the default radio bearer. See 36.509 clause 6.1

Table 8.7.5.2.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.5.2.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.5.2.6.5.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

}

}

}

}

Table 8.7.5.2.6.4.3-4: TDD-Config-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

TDD-Config-DEFAULT ::= SEQUENCE {

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

8.7.5.2.6.5 Test Requirements

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

Table 8.7.5.2.6.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

29

20+6×20

20

6×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

30

2×20+5×20

2×20

5×20

75376

75376/0

R.31-4 FDD

R.31-4 TDD

85

8.7.5.2_H.4 TDD FDD CA Sustained data rate performance for TDD PCell (5DL CA) for 256QAM in DL

8.7.5.2_H.4.1 Test purpose

Same test purpose as 8.7.2.1.

8.7.5.2_H.4.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 16 that support 256QAM in DL and support E-UTRA FDD and TDD, 5DL TDD-FDD CA with TDD as PCell.

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

8.7.5.2_H.4.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.2_H.4.3-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.5.2_H.4.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements in Table 8.7.5.2-3 is not applicable.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.2_H.4.3-1: Minimum requirement (TDD FDD CA 256QAM)

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

14

3×20+15

2×20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

16

4×20+15

2×20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

17

2×15+3×20

2×15+20

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.2_H.4.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 5CCs

4×20+15

2×20+15

2×20

14 or 12

16

2×15+3×20

2×15+20

2×20

15 or 12

17

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

8.7.5.2_H.4.4 Test description

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

– Instead of Table 8.7.5.2.4.4.1-1 ‑> use Table 8.7.5.2_H.4.4-1.

– Instead of Table 8.7.5.2.4.5-1 ‑> use Table 8.7.5.2_H.4.5-1.

– Instead of Table 8.7.5.2.4.5-2 ‑> use Table 8.7.5.2_H.4.5-2.

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

Test number

12

14

15

16

17

Bandwidth

FDD CC

20+15

2×20+15

2×15+20

2×20+15

2×15+20

TDD CC

2×20

20

20

2×20

2×20

DL Measurement channel

FDD CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

R.68 FDD for 20MHz CC, R.68-1 FDD for 15MHz CC

TDD CC

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

R.68 TDD

UL channel

FDD CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

R.1-4 FDD for 20MHz CC

TDD CC

NA

NA

NA

NA

NA

TBsize per Codeword

FDD CC

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

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

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

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

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

TDD CC

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

97896/0

(Note 6)

Number of PDCP SDU per Codeword

FDD CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

10 for 20MHz CC, 7 for 15MHz CC

TDD CC

10/0

10/0

10/0

10/0

10/0

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

FLOOR((TBsize – 352)/80) for 20MHz CC, FLOOR((TBsize – 264)/56) for 15MHz CC

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

1219 for 20MHz CC, 1341 for 15MHz CC

TDD CC

1219/0

1219/0

1219/0

1219/0

1219/0

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

Note 2: Each PDCP SDU is limited to 1500 octets (to keep below maximum SDU size of ESM as specified in TS 24.301 clause 9.9.4.12).
The PDCP SDU size of each PDCP SDU is:
PDCP SDU size = (TBsize – 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.

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: 84760 bits for sub-frame 0, 4 and 81176 bits for sub-frame 5.

8.7.5.2_H.4.5 Test requirement

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

Table 8.7.5.2_H.4.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Number of bits of a DL-SCH transport block received within a TTI (for normal/special subframe for TDD, except for subframe #5)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

12

3×20+15

20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

14

3×20+15

2×20+15

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

15

2×15+2×20

2×15+20

20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

16

4×20+15

2×20+15

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

17

2×15+3×20

2×15+20

2×20

75376 for 20MHz CC 55056 for 15MHz CC

75376/0

R.31-4 FDD for 20MHz CC, R.31-5 FDD for 15MHz CC

R.31-4 TDD

85

Table 8.7.5.2_H.4.5-2: Test applicability per UE category

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 5CCs

4×20+15

2×20+15

2×20

14 or 12

16

2×15+3×20

2×15+20

2×20

15 or 12

17

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.5.2_H.5 TDD FDD CA Sustained data rate performance for TDD PCell (6DL CA) for 256QAM in DL

8.7.5.2_H.5.1 Test purpose

Same test purpose as 8.7.1.1.

8.7.5.2_H.5.2 Test applicability

This test applies to all types of UE Release 12 and forward of UE DL category 16 that support 256QAM in DL and support E-UTRA FDD and TDD, 6DL TDD-FDD CA with TDD as PCell.

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

8.7.5.2_H.5.3 Minimum conformance requirements

For UE supporting 256QAM, the requirements for TDD FDD CA with FDD PCell are specified in Table 8.7.5.2_H.5.3-1 with the additional parameters specified in Table 8.7.5-1, and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category or UE DL category, and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.5.2_H.5.3-2. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements in Table 8.7.5.2-1 is not applicable.

The applicability of the requirements are specified in Clause 8.1.2.3B. The test coverage for different number of component carriers is defined in 8.1.2.4.

Table 8.7.5.2_H.5.3-1: Minimum requirement (TDD FDD CA 256QAM)

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

R.68-2 FDD

R.68 TDD

85

28

2×20+4×20

2×20

4×20

R.68-2 FDD

R.68 TDD

85

Table 8.7.5.2_H.5.3-2: 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

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 6CCs

20+5×20

20

5×20

27

2×20+4×20

2×20

4×20

28

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

8.7.5.2_H.5.4 Test description

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

– Instead of Table 8.7.5.2.5.4.1-1 and Table 8.7.5.2.5.4.1-2 ‑> use Table 8.7.5.2_H.5.4-1 and Table 8.7.5.2_H.5.4-2.

– Instead of Table 8.7.5.2.5.5-1 ‑> use Table 8.7.5.2_H.5.5-1.

– Instead of Table 8.7.5.2.5.5-2 ‑> use Table 8.7.5.2_H.5.5-2.

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

Test number

27

28

Bandwidth

FDD CC

20

2×20

TDD CC

5×20

4×20

DL Measurement channel

FDD CC

R.68-2 FDD

R.68-2 FDD

TDD CC

R.68 TDD

R.68 TDD

UL channel

FDD CC

NA

NA

TDD CC

R.1-4 TDD

R.1-4 TDD

TBsize per Codeword

FDD CC

97896 (Note 3)

97896 (Note 3)

TDD CC

97896/0 (Note 4)

97896/0 (Note 4)

Number of PDCP SDU per Codeword

FDD CC

10

10

TDD CC

10

10

PDCP SDU size [Octets] Calculation

(Note 1)

FDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

TDD CC

FLOOR((TBsize – 352)/80)

FLOOR((TBsize – 352)/80)

PDCP SDU size [Octets]

FDD CC

1219

1341

TDD CC

1219

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

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

8.7.5.2_H.5.5 Test Requirements

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

Table 8.7.5.2_H.5.5-1: Test requirements per test

Test number

Bandwidth (MHz)

Measurement channel

Reference value

Total

FDD CC

TDD CC

FDD CC

TDD CC

TB success rate [%]

27

20+5×20

20

5×20

R.68-2 FDD

R.68 TDD

85

28

2×20+4×20

2×20

4×20

R.68-2 FDD

R.68 TDD

85

Table 8.7.5.2_H.3.5-2: Test applicability per UE category

CA config

Maximum supported Bandwidth/ Bandwidth combination (MHz)

Cat. 11, 12

DL Cat. 13

DL Cat. 15

DL Cat. 16

Total

FDD CC

TDD CC

DL Cat. 11, 12

CA with 6CCs

20+5×20

20

5×20

27

2×20+4×20

2×20

4×20

28

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.