8.7.4 TDD (EPDCCH scheduling)

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

Table 8.7.4-1: Common test parameters (TDD)

Parameter

Unit

Value

Special subframe configuration (Note 1)

4

Cyclic prefix

Normal

Cell ID

0

Inter-TTI Distance

1

Maximum number of HARQ transmission

4

Redundancy version coding sequence

{0,0,1,2} for 64QAM

Number of OFDM symbols for PDCCH per component carrier

OFDM symbols

1

Cross carrier scheduling

Not configured

Number of EPDCCH sets

1

EPDCCH transmission type

Localized

Number of PRB per EPDCCH set and EPDCCH PRB pair allocation

2 PRB pairs

10MHz BW: Resource blocks nPRB = 48, 49

15MHz BW: Resource blocks nPRB = 70, 71
20MHz BW: Resource blocks nPRB = 98, 99

EPDCCH Starting Symbol

Derived from CFI (i.e. default behaviour)

ECCE Aggregation Level

2 ECCEs

Number of EREGs per ECCE

4 for normal subframe and for special subframe

EPDCCH scheduling

EPDCCH candidate is randomly assigned in each subframe

EPDCCH precoder

(Note 2)

Fixed PMI 0

EPDCCH monitoring SF pattern

UL-DL configuration 1: 1101111111 0000000000

UL-DL configuration 5: 1100111001 0000000000

Timing advance

μs

100

Propagation condition

Static propagation condition

No external noise sources are applied

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

Note 2: EPDCCH precoder parameters are defined for tests with 2 x 2 antenna configuration

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

8.7.4.1 TDD sustained data rate performance for EPDCCH scheduling

8.7.4.1.1 Test purpose

Same test purpose as in clause 8.7.2.1.

8.7.4.1.2 Test applicability

This test applies to all types of E-UTRA FDD UE Release 11 and forward supporting EPDCCH.

8.7.4.1.3 Minimum requirements

Table 8.7.4.1.3-1: Void

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

Table 8.7.4.1.3-2: Test parameters for SDR test for PDSCH scheduled by EPDCCH (TDD)

Bandwidth (MHz)

Transmission mode

Antenna configuration

Codebook subset restriction

Downlink power allocation (dB)

at antenna port (dBm/15kHz)

Symbols for unused PRBs

ACK/NACK feedback mode

σ

δ

1

10

1

1 x 2

N/A

0

0

0

0

-85

OP.6 TDD

Bundling

2

10

3

2 x 2

10

-3

-3

0

3

-85

OP.1 TDD

Bundling

3

20

3

2 x 2

10

-3

-3

0

3

-85

OP.1 TDD

Bundling

3A

15

3

2 x 2

10

-3

-3

0

3

-85

OP.2 TDD

Multiplexing

4,6

20

3

2 x 2

10

-3

-3

0

3

-85

OP.1 TDD

Multiplexing

Table 8.7.4.1.3-3: Minimum requirement (TDD)

Test

Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame

Measurement channel

Reference value

TB success rate [%]

1

10296/0

R.31E-1 TDD

95

2

25456/0

R.31E-2 TDD

95

3

51024/0

R.31E-3 TDD

95

3A

51024/0

R.31E-3A TDD

85

4

75376/0 (Note 2)

R.31E-4 TDD

85

6

75376/0 (Note 2)

R.31E-4 TDD

85

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

Note 2: 71112 bits for sub-frame 5.

Note 3: The TB success rate is defined as TB success rate = 100%*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.4.1.3-4: Test points for sustained data rate (FRC)

CA config

Bandwidth/ Bandwidth combination

(MHz)

Category 1

Category 2

Category 3

Category 4

Category 6

Category 7

Single carrier

10

1

2

–

–

–

–

15

–

–

3A

3A

–

–

20

–

–

3

4

6

6

Note 1: The test is selected for maximum supported bandwidth.

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

8.7.4.1.4 Test description

8.7.4.1.4.1 Initial conditions

Table 8.7.4.1.4.1-1: Further test parameters per test

Test

DL Measurement channel

UL Measurement channel

TBsize per Codeword

Number of PDCP SDU per Codeword

PDCP SDU size [Octets] Calculation

(Note 1)

PDCP SDU size [Octets]

1

R.31E-1 TDD

R.1-1 TDD

10296

1/0

FLOOR((TBsize – 96)/8)

2

R.31E-2 TDD

R.1-2 TDD

25456

3/0

FLOOR((TBsize – 152)/24))

3

R.31E-3 TDD

R.1-3 TDD

51024

5/0

FLOOR((TBsize – 208)/40))

3A

R.31E-3A TDD

R.1-3B TDD

51024

4/0

FLOOR((TBsize – 184)/32))"

4

R.31E-4 TDD

R.1-4 TDD

75376 (Note 3)

7/0

FLOOR((TBsize – 264)/56))

6

R.31E-4 TDD

R.1-4 TDD

75376 (Note 3)

7/0

FLOOR((TBsize – 264)/56))

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

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

Note 3: 71112 bits for sub-frame 5.

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

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

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

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

Channel Bandwidths to be tested: According to table 8.7.4.1.3-2.

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

2. The parameter settings for the cell are set up according to Table 8.7.4.1.5-1 and Table 8.7.4.1.5-2.

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

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

5. Ensure the UE is in State 4 (Loopback activated) according to TS 36.508 [7] clause 4.5.4. Message contents are defined in clause 8.7.4.1.4.3.

6. SS sends Timing Advance Command MAC CE with timing advance 100us to UE.

8.7.4.1.4.2 Test procedure

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

2. The SS looks up TBsize in table 8.7.4.1.4.1-1 according to the UE category under test.

3. SS sets the counters NDL_newtx ,NDL_retx, NUL_PDCP, and NDL_PDCP to 0.

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

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

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

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

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

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

10. The UE passes the test if A ≥ "corresponding TB success rates according to Table 8.7.4.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.4.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.4.1.4.3-1: CLOSE UE TEST LOOP (in the preamble)

Derivation Path: 36.509 clause 6.1

Information Element

Value/remark

Comment

Condition

Protocol discriminator

1 1 1 1

Skip indicator

0 0 0 0

Message type

1 0 0 0 0 0 0 0

UE test loop mode

0 0 0 0 0 0 0 0

UE test loop mode A

UE test loop mode A LB setup

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

0 0 0 0 0 0 1 1

Length of one LB setup DRB (3 bytes)

LB setup DRB

0 0 0 0 0 0 0 0,

0 0 101 0 0 0,

0 0 0 Q4 Q3 Q2 Q1 Q0

UL PDCP SDU size = 40 bits (5 bytes)

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

UE test loop mode B LB setup

Not present

Table 8.7.4.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.4.1.4.3-3: EPDCCH-Config-r11-DEFAULT

Derivation Path: 36.508 clause 4.6

Information Element

Value/remark

Comment

Condition

EPDCCH-Config-r11 ::= SEQUENCE{

config-r11 CHOICE {

setup SEQUENCE {

subframePatternConfig-r11

1101111111 000000000 or

1100111001 000000000

1101111111 000000000 for UL-DL configuration 1 and 1100111001 000000000 for UL-DL configuration 5

startSymbol-r11

Not present

Derived from CFI

setConfigToReleaseList-r11

Null

setConfigToAddModList-r11 SEQUENCE {

1 entry

setConfigId-r11[1]

0

transmissionType-r11[1]

localized

resourceBlockAssignment-r11[1] SEQUENCE{

numberPRB-Pairs-r11

n2

resourceBlockAssignment-r11

0000

or

1001

0000 for Bandwidth 10MHz and 20MHz;

1001 only for Bandwidth 15MHz

}

}

}

}

}

Table 8.7.4.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 or sa5

The two cases will be configured for each test

specialSubframePatterns

Ssp4

}

8.7.4.1.5 Test requirement

The requirements are specified in Table 8.7.4.1.5-1. The PDCP SDU success rate shall be sustained during at least 300 frames.

Table 8.7.4.1.5-1: Test requirements per test

Test

Number of bits of a DL-SCH transport block received within a TTI for normal/special sub-frame

Measurement channel

Reference value

TB success rate [%]

1

10296/0

R.31E-1 TDD

95

2

25456/0

R.31E-2 TDD

95

3

51024/0

R.31E-3 TDD

95

3A

51024/0

R.31E-3A TDD

85

4

75376/0 (Note 2)

R.31E-4 TDD

85

6

75376/0 (Note 2)

R.31E-4 TDD

85

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

Note 2: 71112 bits for sub-frame 5.

Note 3: The TB success rate is defined as TB success rate = 100%*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.4.1.5-2: Test parameters per test

Bandwidth (MHz)

Transmission mode

Antenna configuration

Codebook subset restriction

Downlink power allocation (dB)

at antenna port (dBm/15kHz)

Symbols for unused PRBs

ACK/NACK feedback mode

σ

δ

1

10

1

1 x 2

N/A

0

0

0

0

-85

OP.6 TDD

Bundling

2

10

3

2 x 2

10

-3

-3

0

3

-85

OP.1 TDD

Bundling

3

20

3

2 x 2

10

-3

-3

0

3

-85

OP.1 TDD

Bundling

3A

15

3

2 x 2

10

-3

-3

0

3

-85

OP.2 TDD

Multiplexing

4,6

20

3

2 x 2

10

-3

-3

0

3

-85

OP.1 TDD

Multiplexing

Table 8.7.4.1.5-3: Test applicability per UE category

CA config

Bandwidth/ Bandwidth combination

(MHz)

Category 1

Category 2

Category 3

Category 4

Category 6

Category 7

Single carrier

10

1

2

–

–

–

–

15

–

–

3A

3A

–

–

20

–

–

3

4

6

6

Note 1: The test is selected for maximum supported bandwidth.