7.1.3 DL-SCH data transfer

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

Editor’s note: System information combination for broadcasting SIB-BR and SIB1-BR for BL UE (Cat-M1) is FFS.

7.1.3.1 Correct handling of DL assignment / Dynamic case

7.1.3.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives downlink assignment on the PDCCH for the UE’s C-RNTI and receives data in the associated subframe and UE performs HARQ operation }

then { UE sends a HARQ feedback on the HARQ process }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives downlink assignment on the PDCCH with a C-RNTI unknown by the UE and data is available in the associated subframe }

then { UE does not send any HARQ feedback on the HARQ process }

}

7.1.3.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 5.3.1

[TS 36.321, clause 5.3.1]

Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a particular UE and provide the relevant HARQ information.

When the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI during which it monitors PDCCH:

– if a downlink assignment for this TTI has been received on the PDCCH for the UE’s C-RNTI, or Temporary C‑RNTI:

– if this is the first downlink assignment for this Temporary C-RNTI:

– consider the NDI to have been toggled.

– if the downlink assignment is for UE’s C-RNTI and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was either a downlink assignment received for the UE’s Semi-Persistent Scheduling C-RNTI or a configured downlink assignment:

– consider the NDI to have been toggled regardless of the value of the NDI.

– indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI.

7.1.3.1.3 Test description

7.1.3.1.3.1 Pre-test conditions

System Simulator:

  • Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.1.3.3-1

UE:

None.

Preamble:

– The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no data in uplink.

7.1.3.1.3.2 Test procedure sequence

Table 7.1.3.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS transmits a downlink assignment including the C-RNTI assigned to the UE

<–

(PDCCH (C-RNTI))

2

SS transmits in the indicated downlink assignment a RLC PDU in a MAC PDU.

<–

MAC PDU

3

Check: Does the UE transmit an HARQ ACK on PUCCH?

–>

HARQ ACK

1

P

4

SS transmits a downlink assignment to including a C-RNTI different from the assigned to the UE

<–

(PDCCH (unknown C-RNTI))

5

SS transmits in the indicated downlink assignment a RLC PDU in a MAC PDU.

<–

MAC PDU

6

Check: Does the UE send any HARQ ACK on PUCCH?

–>

HARQ ACK

2

F

NOTE 1: For TDD, the timing of ACK/NACK is not constant as FDD, see Table 10.1-1 of TS 36.213.

7.1.3.1.3.3 Specific Message Contents

Table 7.1.3.1.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.3.1.3.3-2: Void

Table 7.1.3.1.3.3-3: Void

7.1.3.2 Correct handling of DL assignment / Semi-persistent case

7.1.3.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state with DRB established and SPS Configuration in DL is enabled }

ensure that {

when { UE receives a DL assignment addressed to its stored SPS-CRNTI in SF-Num y and with NDI set as 0 }

then { UE starts receiving DL MAC PDU in SF-Nums y+n*[semiPersistSchedIntervalDL] where ‘n’ is positive integer starting at zero }

}

(2)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] }

ensure that {

when { UE receives a DL assignment addressed to its SPS-CRNTI in SF-Num p and with NDI set as 0, where p!= y+n*[semiPersistSchedIntervalDL] }

then { UE starts receiving DL MAC PDU in SF-Nums p+n*[semiPersistSchedIntervalDL] and stops receiving DL MAC PDU at SF-Nums y+n*[semiPersistSchedIntervalDL]where ‘n’ is positive integer starting at zero }

}

(3)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num p+n*[semiPersistSchedIntervalDL] }

ensure that {

when { UE receives a DL assignment [for retransmission] addressed to its SPS-CRNTI in SF-Num z and with NDI set as 1, where z!= p+n*[semiPersistSchedIntervalDL] }

then { UE receives MAC PDU in SF-Num z as per the new grant for SPS-CRNTI }

}

(4)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] }

ensure that {

when { UE receives a DL assignment addressed to its CRNTI in SF-Num p, such that p!= y+n*[semiPersistSchedIntervalDL] }

then { UE receives MAC PDU in SF-Num p as per assignment addressed to its C-RNTI }

}

(5)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS grant to receive MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }

ensure that {

when { UE receives a RRCConnectionReconfiguration including SPS Configuration with sps-ConfigDL set as ‘disable’ and hence resulting in DL SPS grant deactivation }

then { UE deletes the stored SPS Configuration DL parameters and stops receiving DL MAC PDU’s as per stored SPS assignment in SF-Num z+n*[semiPersistSchedIntervalDL] }

}

(6)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }

ensure that {

when { UE receives a PDCCH [for DL SPS explicit release according to Table 9.2-1A in TS 36.213] addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p!= z+n*[semiPersistSchedIntervalDL] }

then { UE sends an ACK to SS and releases the configured SPS assignment and stops receiving MAC PDU in SF-Num z+n*[semiPersistSchedIntervalDL] as per assignment addressed to its SPS C-RNTI }

}

NOTE: SF-Num = [10*SFN + subframe] modulo 10240.

7.1.3.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.3.1, 5.10 & 5.10.1, 36.331 clause 5.3.10.5, 36.300 clause 11.1.1 and 36.213 clause 9.2.

[TS 36.321, clause 5.3.1]

Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a particular UE and provide the relevant HARQ information.

When the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI during which it monitors PDCCH:

– if a downlink assignment for this TTI has been received on the PDCCH for the UE’s C-RNTI, or Temporary C‑RNTI:

– if this is the first downlink assignment for this Temporary C-RNTI:

– consider the NDI to have been toggled.

– if the downlink assignment is for UE’s C-RNTI and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was either a downlink assignment received for the UE’s Semi-Persistent Scheduling C-RNTI or a configured downlink assignment:

– consider the NDI to have been toggled regardless of the value of the NDI.

– indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI.

– else, if a downlink assignment for this TTI has been received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI:

– if the NDI in the received HARQ information is 1:

– consider the NDI not to have been toggled;

– indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI.

– else, if the NDI in the received HARQ information is 0:

– if PDCCH contents indicate SPS release:

– clear the configured downlink assignment (if any);

– if timeAlignmentTimer is running:

– instruct the physical layer to transmit a positive acknowledgement.

– else:

– store the downlink assignment and the associated HARQ information as configured downlink assignment;

– initialise (if not active) or re-initialise (if already active) the configured downlink assignment to start in this TTI and to recur according to rules in subclause 5.10.1;

– set the HARQ Process ID to the HARQ Process ID associated with this TTI;

– consider the NDI bit to have been toggled;

– indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity for this TTI.

– else, if a downlink assignment for this TTI has been configured and there is no measurement gap in this TTI:

– instruct the physical layer to receive, in this TTI, transport block on the DL-SCH according to the configured downlink assignment and to deliver it to the HARQ entity;

– set the HARQ Process ID to the HARQ Process ID associated with this TTI;

– consider the NDI bit to have been toggled;

– indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity for this TTI.

For downlink assignments received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI and for configured downlink assignments, the HARQ Process ID associated with this TTI is derived from the following equation:

HARQ Process ID = [floor(CURRENT_TTI/(Downlink Semi-Persistent Scheduling Interval))] modulo Number of Configured SPS Processes,

where CURRENT_TTI=[(SFN * 10) + subframe number], Downlink Semi-Persistent Scheduling Interval is the periodicity of semi-persistent scheduling signalled via RRC and Number of Configured SPS Processes is the number of HARQ processes allocated for semi-persistent scheduling signalled via RRC.

[TS 36.321, clause 5.10]

When Semi-Persistent Scheduling is enabled by upper layer, the following information is provided:

– Semi-Persistent Scheduling C-RNTI;

– Uplink Semi-Persistent Scheduling Interval semiPersistSchedIntervalUL and number of empty transmissions before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the uplink;

– Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;

– Downlink Semi-Persistent Scheduling Interval semiPersistSchedIntervalDL and number of configured HARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is enabled for the downlink;

When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or configured assignment shall be discarded.

[TS 36.321, clause 5.10.1]

After a Semi-Persistent downlink assignment is configured, the UE shall consider that the assignment recurs in each subframe for which:

– (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * (Downlink Semi-Persistent Scheduling Interval)] modulo 10240, for all N>0.

Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the configured downlink assignment were (re-)initialised.

[TS 36.331, clause 5.3.10.5]

The UE shall:

1> reconfigure the semi-persistent scheduling in accordance with the received sps-Config:

[TS 36.300, clause 11.1.1]

In addition, E-UTRAN can allocate semi-persistent downlink resources for the first HARQ transmissions to UEs:

– RRC defines the periodicity of the semi-persistent downlink grant;

– PDCCH indicates whether the downlink grant is a semi-persistent one i.e. whether it can be implicitly reused in the following TTIs according to the periodicity defined by RRC.

When required, retransmissions are explicitly signalled via the PDCCH(s). In the sub-frames where the UE has semi-persistent downlink resource, if the UE cannot find its C-RNTI on the PDCCH(s), a downlink transmission according to the semi-persistent allocation that the UE has been assigned in the TTI is assumed. Otherwise, in the sub-frames where the UE has semi-persistent downlink resource, if the UE finds its C-RNTI on the PDCCH(s), the PDCCH allocation overrides the semi-persistent allocation for that TTI and the UE does not decode the semi-persistent resources.

[TS 36.213, clause 9.2]

A UE shall validate a Semi-Persistent Scheduling assignment PDCCH only if all the following conditions are met:

–    the CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI

–  the new data indicator field is set to ‘0’. In case of DCI formats 2 and 2A, the new data indicator field refers to the one for the enabled transport block.

Validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-1A.

If validation is achieved, the UE shall consider the received DCI information accordingly as a valid semi-persistent activation or release.

If validation is not achieved, the received DCI format shall be considered by the UE as having been received with a non-matching CRC.

Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation

DCI format 0

DCI format 1/1A

DCI format 2/2A

TPC command for scheduled PUSCH

set to ‘00’

N/A

N/A

Cyclic shift DM RS

set to ‘000’

N/A

N/A

Modulation and coding scheme and redundancy version

MSB is set to ‘0’

N/A

N/A

HARQ process number

N/A

FDD: set to ‘000’

TDD: set to ‘0000’

FDD: set to ‘000’

TDD: set to ‘0000’

Modulation and coding scheme

N/A

MSB is set to ‘0’

For the enabled transport block:
MSB is set to ‘0’

Redundancy version

N/A

set to ‘00’

For the enabled transport block:
set to ‘00’

Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH Validation

DCI format 0

DCI format 1A

TPC command for scheduled PUSCH

set to ‘00’

N/A

Cyclic shift DM RS

set to ‘000’

N/A

Modulation and coding scheme and redundancy version

set to ‘11111’

N/A

Resource block assignment and hopping resource allocation

Set to all ‘1’s

N/A

HARQ process number

N/A

FDD: set to ‘000’

TDD: set to ‘0000’

Modulation and coding scheme

N/A

set to ‘11111’

Redundancy version

N/A

set to ‘00’

Resource block assignment

N/A

Set to all ‘1’s

7.1.3.2.3 Test description

7.1.3.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

– The UL RLC SDU size is set to not return any data.

7.1.3.2.3.2 Test procedure sequence

Table 7.1.3.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS Transmits a DL assignment using UE’s SPS C-RNTI in SF-Num ‘Y’, NDI=0

<–

(DL SPS Grant)

2

The SS transmits in SF-Num ‘Y’, a DL MAC PDU containing a RLC PDU (DL-SQN=0)on UM DRB

<–

MAC PDU

3

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

4

The SS transmits in SF-Num ‘Y+X(semiPersistSchedIntervalDL)’, a DL MAC PDU containing a RLC PDU (DL-SQN=1)on DRB

<–

MAC PDU

5

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

6

The SS Transmits a DL assignment using UE’s SPS C-RNTI in SF-Num ‘P’, NDI=0;

(Where Y+X<P< Y+2X)

<–

(DL SPS Grant)

7

The SS transmits in SF-Num ‘P’, a DL MAC PDU containing a RLC PDU (DL-SQN=2)on UM DRB

<–

MAC PDU

8

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

2

P

9

The SS transmits in SF-Num ‘Y+2X’, a DL MAC PDU containing a RLC PDU (DL-SQN=3)on UM DRB

<–

MAC PDU

10

Check: Does the UE transmit a HARQ Feedback?

–>

HARQ ACK/NACK

2

F

10A

The SS Transmits a DL assignment using UE’s C-RNTI in SF-Num ‘P+X(semiPersistSchedIntervalDL)’, NDI=0

<–

(DL Grant)

11

The SS transmits in SF-Num ‘P+X(semiPersistSchedIntervalDL)’, a DL MAC PDU containing a RLC PDU (DL-SQN=3)on UM DRB;

<–

MAC PDU

12

Void

13

Void

14

Void

15

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

4

P

16

The SS transmits in SF-Num ‘P+2X(semiPersistSchedIntervalDL)’, a DL MAC PDU containing a RLC PDU (DL-SQN=4)on UM DRB

<–

MAC PDU

17

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

18

The SS Transmits a DL assignment using UE’s SPS C-RNTI in SF-Num in SF-Num ‘P+3X(semiPersistSchedIntervalDL)’. (Note 1a)

<–

(DL SPS Grant)

19

The SS transmits in SF-Num ‘P+3X(semiPersistSchedIntervalDL)’, a DL MAC PDU containing 1 RLC PDU’s (DL-SQN=5)on UM DRB;Note 1

<–

MAC PDU

19A

Check: Does the UE transmit a HARQ NACK?

–>

HARQ NACK

EXCEPTION: Step 19b and 19c shall be repeated until HARQ retransmission count = 3 is reached for MAC PDU at step 19 (Note 1b).

19b

The SS Transmits a DL assignment using UE’s SPS C-RNTI in SF-Num ‘Z’, NDI=1;

Where (P+3X < Z <P+4X); The DL HARQ process is same as in step 11

<–

(DL SPS Grant)

19c

The SS re-transmits in SF-Num ‘Z’, a DL MAC PDU containing a RLC PDU (DL-SQN=5)on UM DRB; (Note 1a)

<–

MAC PDU

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 20 (Note 1b).

20

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

3

P

21

The SS Transmits a PDCCH [for DL SPS explicit release] using UE’s SPS C-RNTI in SF-Num ‘Q’, NDI=0; Where (P+3X< Q <P+4X).

<–

PDCCH [for DL SPS explicit release]

22

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

6

P

23

The SS transmits in SF-Num ‘P+5X(semiPersistSchedIntervalDL)’, a DL MAC PDU containing 1 RLC PDU’s (DL-SQN=6)on UM DRB;

<–

MAC PDU

24

Check: Does the UE transmit a HARQ Feedback?

–>

HARQ ACK/NACK

6

F

25

The SS Transmits a DL assignment using UE’s SPS C-RNTI in SF-Num ‘P+6X’, NDI=0

<–

(DL SPS Grant)

26

The SS transmits in SF-Num ‘P+6X’, a DL MAC PDU containing a RLC PDU (DL-SQN=6)on UM DRB

<–

MAC PDU

27

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

28

Void

29

Void

30

SS Transmits RRCConnectionReconfiguration to disable SPS Configuration DL

31

The UE transmits RRCConnectionReconfigurationComplete

–>

32

The SS transmits in SF-Num ‘P+8X(semiPersistSchedIntervalDL)’, a DL MAC PDU containing 1 RLC PDU’s (DL-SQN=7) on UM DRB;

<–

MAC PDU

33

Check: Dose the UE transmit a HARQ Feedback?

–>

HARQ ACK/NACK

5

F

Note 1: The DL assignment for C-RNTI and hence the size of MAC PDU is different in size than stored SPS C-RNTI DL assignment in step 6. This assures UE is receiving DSCH data as per DL assignment for C-RNTI and not as per stored grant for SPS C-RNTI.

Note 1a: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in TBSize of 328 and having coding rate more than 1.

Note 1b: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption that, given the radio conditions used in this test case, a UE soft combiner implementation should have sufficient retransmissions to be able to successfully decode the data in its soft buffer.

Note 2: For TDD, the subframe number for ‘Y’, ‘P’, ‘Z’ and ‘Q’ should be ‘0’, ‘4’, ‘5’ and ‘9’ respectively based on TDD configuration 1.

7.1.3.2.3.3 Specific message contents

Table 7.1.3.2.3.3-1: RRCConnectionReconfiguration. RadioResourceConfigDedicated (Preamble)

Derivation path: 36.508 table 4.6.3-16

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

sps-Config ::= SEQUENCE {

semiPersistSchedC-RNTI

‘FFF0’H

sps-ConfigDL::=CHOICE{

enable SEQUENCE {

semiPersistSchedIntervalDL

sf40

40 Subframe

numberOfConfSPS-Processes

8

FDD

numberOfConfSPS-Processes

7

Max DL HARQ processes is 7 considering TDD configuration 1.

TDD

n1Pucch-AN-Persistent

0

}

}

sps-ConfigUL

Not Present

}

}

Table 7.1.3.2.3.3-2: RRCConnectionReconfiguration. RadioResourceConfigDedicated (step 30 of table 7.1.3.2.3.2-1)

Derivation path: 36.508 table 4.6.3-16

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

sps-Config ::= SEQUENCE {

semiPersistSchedC-RNTI

Not Present

sps-ConfigDL::=CHOICE{

disable

NULL

}

sps-ConfigUL

Not Present

}

}

Table 7.1.3.2.3.3-3: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

drx-Config

Not Present

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

7.1.3.3 MAC PDU header handling

7.1.3.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU containing an AMD PDU that is larger than 128 bytes with padding at the end }

then { UE successfully decodes the MAC PDU and forward to higher layer }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU containing an AMD PDU that is smaller than 128 bytes with padding at the end }

then { UE successfully decodes the MAC PDU and forward to higher layer }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU containing an single AMD PDU with no padding }

then { UE successfully decodes the MAC PDU and forward to higher layer }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU containing multiple MAC SDUs each containing an AMD PDU and no padding }

then { UE successfully decodes the MAC PDU and forwards the AMD PDUs to higher layer }

}

7.1.3.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 6.1.2 and 6.2.1.

[TS 36.321, clause 6.1.2]

A MAC PDU consists of a MAC header, zero or more MAC Service Data Units (MAC SDU), zero, or more MAC control elements, and optionally padding; as described in Figure 6.1.2-3.

Both the MAC header and the MAC SDUs are of variable sizes.

A MAC PDU header consists of one or more MAC PDU sub-headers; each sub header corresponding to either a MAC SDU, a MAC control element or padding.

A MAC PDU sub header consists of the six header fields R/R/E/LCID/F/L but for the last sub header in the MAC PDU and for fixed sized MAC control elements. The last sub header in the MAC PDU and sub-headers for fixed sized MAC control elements consist solely of the four header fields R/R/E/LCID. It follows that a MAC PDU sub header corresponding to padding consists of the four header fields R/R/E/LCID.

Figure 6.1.2-1: R/R/E/LCID/F/L MAC sub header

Figure 6.1.2-2: R/R/E/LCID MAC sub header

MAC PDU sub-headers have the same order as the corresponding MAC SDUs, MAC control elements and padding.

MAC control elements, are always placed before any MAC SDU.

Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may have any value and the UE shall ignore it. When padding is performed at the end of the MAC PDU, zero or more padding bytes are allowed.

When single-byte or two-byte padding is required, one or two MAC PDU sub-headers corresponding to padding are placed at the beginning of the MAC PDU before any other MAC PDU subheader. A maximum of one MAC PDU can be transmitted per TB per UE.

Figure 6.1.2-3: Example of MAC PDU consisting of MAC header, MAC control elements, MAC SDUs and padding

[TS 36.321, clause 6.2.1]

The MAC header is of variable size and consists of the following fields:

– LCID: The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC control element or padding as described in tables 6.2.1-1 and 6.2.1-2 for the DL and UL-SCH respectively. There is one LCID field for each MAC SDU, MAC control element or padding included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU, when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC PDU. The LCID field size is 5 bits;

– L: The Length field indicates the length of the corresponding MAC SDU or MAC control element in bytes. There is one L field per MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control elements. The size of the L field is indicated by the F field;

– F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control elements. The size of the F field is 1 bit. If the size of the MAC SDU or MAC control element is less than 128 bytes, the UE shall set the value of the F field to 0, otherwise the UE shall set it to 1;

– E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set to "1" to indicate another set of at least R/R/E/LCID fields. The E field is set to "0" to indicate that either a MAC SDU, a MAC control element or padding starts at the next byte;

– R: Reserved bits, set to "0".

The MAC header and sub-headers are octet aligned.

Table 6.2.1-1: Values of LCID for DL-SCH

Index

LCID values

00000

CCCH

00001-01010

Identity of the logical channel

01011-11011

Reserved

11100

UE Contention Resolution Identity

11101

Timing Advance Command

11110

DRX Command

11111

Padding

Table 6.2.1-2: Values of LCID for UL-SCH

Index

LCID values

00000

CCCH

00001-01010

Identity of the logical channel

01011-11001

Reserved

11010

Power Headroom Report

11011

C-RNTI

11100

Truncated BSR

11101

Short BSR

11110

Long BSR

11111

Padding

Table 6.2.1-3: Values of F field:

Index

Size of Length field (in bits)

0

7

1

15

7.1.3.3.3 Test description

7.1.3.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The UL RLC SDU size is set to not return any data.

7.1.3.3.3.2 Test procedure sequence

Table 7.1.3.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a MAC PDU containing a RLC SDU of 130 bytes in an AMD PDU (SN=0) with polling field ‘P’ set to ‘1’ and 5 bytes of padding. The MAC header contains two MAC sub-headers where the first MAC sub-header is a 3-byte R/R/E/LCID/F/L MAC sub-header with ‘E’ field set to ‘1’, the ‘F’ set to ‘1’, the ‘LCID’ field set to ‘00011’ and the ‘L’ field set to ‘132’ bytes. The second MAC sub-header is a padding control 1byte R/R/E/LCID MAC sub-header with ‘E’ field set to ‘0’ and ‘LCID’ field set to ‘11111’.

<–

MAC PDU (R/R/E/LCID/F/L MAC sub-header (E=’1’, LCID=’00011’, F=’1’, L=’132’), MAC R/R/E/LCID MAC sub-header (E=’0’, LCID=’11111’), 132 bytes MAC SDU and 5 bytes padding)

2

Check: Does the UE transmit a MAC PDU containing an RLC STATUS PDU acknowledging the reception of the AMD PDU in step 1?

–>

MAC PDU (RLC STATUS PDU (ACK_SN ‘1’))

1

P

3

The SS transmits a MAC PDU containing a RLC SDU of 40 bytes in an AMD PDU(SN=1) with polling field ‘P’ set to ‘1’and 4 bytes of padding. The MAC header contains two MAC sub-headers where the first MAC sub-header is a 2-byte R/R/E/LCID/F/L MAC sub-header with ‘E’ field set to ‘1’, the ‘F’ set to ‘0’, the ‘LCID’ field set to ‘00011’ and the ‘L’ field set to ‘42’ bytes. The second MAC sub-header is a padding control 1byte R/R/E/LCID MAC sub-header with ‘E’ field set to ‘0’ and ‘LCID’ field set to ‘11111’.

<–

MAC PDU (R/R/E/LCID/F/L MAC sub-header (E=’1’, LCID=’00011’, F=’0’, L=’42’), R/R/E/LCID MAC sub-header (E=’0’, LCID=’11111’), 42 bytes MAC SDU and 4 bytes padding)

4

Check: Does the UE transmit a MAC PDU containing an RLC STATUS PDU acknowledging the reception of the AMD PDU in step 3?

–>

MAC PDU (RLC STATUS PDU (ACK_SN ‘2’))

2

P

5

The SS transmits a MAC PDU containing a MAC SDU with a RLC SDU of 130 bytes in an AMD PDU(SN=2) with polling field ‘P’ set to ‘1’. The MAC header contains one R/R/E/LCID MAC sub-header with ‘E’ field set to ‘0’ and the ‘LCID’ field set to ‘00011’.

<–

MAC PDU (R/R/E/LCID MAC sub-header (E=’0’, LCID=’00011’), 132 bytes MAC SDU)

6

Check: Does the UE transmit a MAC PDU containing an RLC STATUS PDU acknowledging the reception of the AMD PDU in step 5?

–>

MAC PDU (RLC STATUS PDU (ACK_SN ‘3’))

3

P

7

The SS transmits a MAC PDU containing one MAC SDU containing a RLC SDU of size 128 bytes in an AMD PDU (SN=3) and five MAC SDUs each containing a RLC SDU of 41 bytes in an AMD PDU (SN=4 to 8) in an AMD PDU with the polling field ‘P’ set to ‘1’ in the last AMD PDU. The MAC header contains six MAC sub-headers where the first MAC sub-header contains a 3 byte R/R/E/LCID/F/L MAC sub-header with ‘E’ field set to ‘1’ , ‘LCID’ field set to ‘00011’, ‘F’ field set to ‘1’ and the ‘L’ field set to ‘130’. The second to fifth MAC sub-header are two byte R/R/E/LCID/F/L MAC sub-headers with ‘E’ field set to ‘1’ , ‘LCID’ field set to ‘00011’, ‘F’ field set to ‘0’ and the ‘L’ field set to ‘43’ bytes. The sixth MAC sub-header is a one byte R/R/E/LCID MAC sub-header with ‘E’ field set to ‘0’ and the ‘LCID’ field set to ‘00011’.

<–

MAC PDU (R/R/E/LCID/L MAC sub-header (E=’1’, LCID=’00011’, F=’1’, L=’ 130’), 4 x R/R/E/LCID/L MAC sub-header (E=’1’, LCID=’00011’, F=’0’, L=’43’), R/R/E/LCID MAC sub-header (E=’0’, LCID=’00011’), 130 bytes MAC SDU, 5 x 43 bytes MAC SDUs)

4

8

Check: Does the UE transmit a MAC PDU containing an RLC STATUS PDU acknowledging the reception of the AMD PDUs in step 7?

–>

MAC PDU (RLC STATUS PDU (ACK_SN ‘9’))

4

P

7.1.3.3.3.3 Specific Message Contents

Table 7.1.3.3.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.3.3.3.2-1)

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

rach-Configuration SEQUENCE {

preambleInformation SEQUENCE {

numberOfRA-Preambles

n64

preamblesGroupAConfig := {SEQUENCE {

sizeOfRA-PreamblesGroupA

n28

messageSizeGroupA

b208

messagePowerOffsetGroupB

minusinfinity

}

}

}

}

ue-TimersAndConstants SEQUENCE{

t300

ms1500

T300

}

}

}

}

7.1.3.3a MAC PDU header handling / UE with limited TB size

7.1.3.3a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU containing an AMD PDU that is smaller than 128 bytes with padding at the end }

then { UE successfully decodes the MAC PDU and forward to higher layer }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU containing an single AMD PDU with no padding }

then { UE successfully decodes the MAC PDU and forward to higher layer }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU containing multiple MAC SDUs each containing an AMD PDU and no padding }

then { UE successfully decodes the MAC PDU and forwards the AMD PDUs to higher layer }

}

7.1.3.3a.2 Conformance requirements

Same as sub-clause 7.1.3.3.2.

7.1.3.3a.3 Test description

7.1.3.3a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The UL RLC SDU size is set to not return any data.

7.1.3.3a.3.2 Test procedure sequence

Table 7.1.3.3a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a MAC PDU containing a RLC SDU of 40 bytes in an AMD PDU(SN=0) with polling field ‘P’ set to ‘1’and 4 bytes of padding. The MAC header contains two MAC sub-headers where the first MAC sub-header is a 2-byte R/R/E/LCID/F/L MAC sub-header with ‘E’ field set to ‘1’, the ‘F’ set to ‘0’, the ‘LCID’ field set to ‘00011’ and the ‘L’ field set to ‘42’ bytes. The second MAC sub-header is a padding control 1byte R/R/E/LCID MAC sub-header with ‘E’ field set to ‘0’ and ‘LCID’ field set to ‘11111’.

<–

MAC PDU (R/R/E/LCID/F/L MAC sub-header (E=’1’, LCID=’00011’, F=’0’, L=’42’), R/R/E/LCID MAC sub-header (E=’0’, LCID=’11111’), 42 bytes MAC SDU and 4 bytes padding)

2

Check: Does the UE transmit a MAC PDU containing an RLC STATUS PDU acknowledging the reception of the AMD PDU in step 1?

–>

MAC PDU (RLC STATUS PDU (ACK_SN ‘1’))

1

P

3

The SS transmits a MAC PDU containing a MAC SDU with a RLC SDU of 38 bytes in an AMD PDU(SN=1) with polling field ‘P’ set to ‘1’. The MAC header contains one R/R/E/LCID MAC sub-header with ‘E’ field set to ‘0’ and the ‘LCID’ field set to ‘00011’.

<–

MAC PDU (R/R/E/LCID MAC sub-header (E=’0’, LCID=’00011’), 40 bytes MAC SDU)

4

Check: Does the UE transmit a MAC PDU containing an RLC STATUS PDU acknowledging the reception of the AMD PDU in step 3?

–>

MAC PDU (RLC STATUS PDU (ACK_SN ‘2’))

2

P

5

The SS transmits five MAC SDUs each containing a RLC SDU of 18 bytes in an AMD PDU (SN=2 to 6) with the polling field ‘P’ set to ‘1’ in the last AMD PDU. The MAC header contains five MAC sub-headers. The first to forth MAC sub-header are two byte R/R/E/LCID/F/L MAC sub-headers with ‘E’ field set to ‘1’ , ‘LCID’ field set to ‘00011’, ‘F’ field set to ‘0’ and the ‘L’ field set to ‘20’ bytes. The fifth MAC sub-header is a one byte R/R/E/LCID MAC sub-header with ‘E’ field set to ‘0’ and the ‘LCID’ field set to ‘00011’.

<–

MAC PDU (4 x R/R/E/LCID/L MAC sub-header (E=’1’, LCID=’00011’, F=’0’, L=’2 0’), R/R/E/LCID MAC sub-header (E=’0’, LCID=’00011’), 5 x 20 bytes MAC SDUs)

6

Check: Does the UE transmit a MAC PDU containing an RLC STATUS PDU acknowledging the reception of the AMD PDUs in step 5?

–>

MAC PDU (RLC STATUS PDU (ACK_SN ‘7’))

3

P

7.1.3.3a.3.3 Specific Message Contents

Same as sub-clause 7.1.3.3.3.

7.1.3.4 Correct HARQ process handling / DCCH and DTCH

7.1.3.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { the UE receives a MAC PDU for DRB and decode fails }

then { the UE transmits a NACK for the corresponding HARQ process }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { the UE receives a MAC PDU retransmission for DRB, and results in successful decode}

then { the UE transmits an ACK for the corresponding HARQ process and delivers data to upper layers }

}

7.1.3.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 & 5.3.2.2.

[TS 36.321, clause 5.3.2.1]

There is one HARQ entity at the UE which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).

The number of DL HARQ processes is specified in [2], clause 7.

When the physical layer is configured for spatial multiplexing [2], one or two TBs are expected per subframe and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.

The UE shall:

– If a downlink assignment has been indicated for this TTI:

– allocate the TBs received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information.

– If a downlink assignment has been indicated for the broadcast HARQ process:

– allocate the received TB to the broadcast HARQ process.

NOTE: In case of BCCH a dedicated broadcast HARQ process is used.

[TS 36.321, clause 5.3.2.2]

For each subframe where a transmission takes place for the HARQ process, one or two (in case of spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity.

For each received TB and associated HARQ information, the HARQ process shall:

– if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or

– if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB according to the system information schedule indicated by RRC; or

– if this is the very first received transmission for this TB(i.e. there is no previous NDI for this TB):

– consider this transmission to be a new transmission.

– else:

– consider this transmission to be a retransmission.

The UE then shall:

– if this is a new transmission

– replace the data currently in the soft buffer for this TB with the received data.

– else if this is a retransmission:

– if the data has not yet been successfully decoded:

– combine the received data with the data currently in the soft buffer for this TB.

– if the TB size is different from the last valid TB size signalled for this TB:

– the UE may replace the data currently in the soft buffer for this TB with the received data.

– attempt to decode the data in the soft buffer for this TB;

– if the data in the soft buffer was successfully decoded for this TB:

– if the HARQ process is equal to the broadcast process, deliver the decoded MAC PDU to upper layers.

– else if this is the first successful decoding of the data in the soft buffer for this TB:

-deliver the decoded MAC PDU to the disassembly and demultiplexing entity.

– generate a positive acknowledgement (ACK) of the data in this TB.

– else:

– generate a negative acknowledgement (NACK) of the data in this TB.

– if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention Resolution is not successful (see subclause 5.1.5); or

– if the HARQ process is equal to the broadcast process; or

– – if timeAlignmentTimer is stopped or expired:

– do not indicate the generated positive or negative acknowledgement to the physical layer.

– else:

– indicate the generated positive or negative acknowledgement for this TB to the physical layer.

The UE shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.

7.1.3.4.3 Test description

7.1.3.4.3.1 Pre-test conditions

System Simulator:

  • Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.4.3.3-1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.3.4.3.2 Test procedure sequence

Table 7.1.3.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: Steps 1 to 7 are run 8[FDD]/7[TDD] times using test parameter values as given for each iteration in table 7.1.3.4.3.2.-2.

1

The SS indicates a new transmission on PDCCH and transmits a MAC PDU (containing an RLC PDU), with content set so that UE could not successfully decode the data from its soft buffer. The AMD PDU contains a full RLC SDU. (Note 1)

<–

MAC PDU

1

2

Check: Does the UE transmit a HARQ NACK?

–>

HARQ NACK

P

EXCEPTION: Step 3 shall be repeated till HARQ ACK is received at step 4 or until HARQ retransmission count = 4 is reached for MAC PDU at step 3 (Note 2).

3

The SS indicates a retransmission on PDCCH and transmits the same MAC PDU like step 1 (Note 1).

<–

MAC PDU

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 4 (Note 2).

4

Check: Does the UE send a HARQ ACK?

–>

HARQ ACK

2

P

5

UE transmit a Scheduling Request on PUCCH

–>

(SR)

6

The SS sends an UL grant suitable for the loop back PDU to transmitted

<–

(UL Grant)

7

The UE transmit a MAC PDU containing the loop back PDU corresponding to step 1 and 3

–>

MAC PDU

Note 1: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in TBSize of 328 and having coding rate more than 1.

Note 2: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption that, given the radio conditions used in this test case, a UE soft combiner implementation should have sufficient retransmissions to be able to successfully decode the data in its soft buffer.

Table 7.1.3.4.3.2-2: Test Parameters

Iteration

DL HARQ process (X)

1

0

2

1

3

2

4

3

5

4

6

5

7

6

8

7[only for FDD]

Note: The maximum DL HARQ process is 7 for TDD configuration 1.

7.1.3.4.3.3 Specific message contents

Table 7.1.3.4.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

7.1.3.4a Correct HARQ process handling / DCCH and DTCH/ Enhanced Coverage / CE Mode A

7.1.3.4a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { the SS transmits a MAC PDU, causing CRC fail on UE side, for DRB in repetitions as per DL_REPETITION_NUMBER }

then { the UE transmits a NACK for the entire bundle as feedback of the corresponding HARQ process }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { the SS retransmits a MAC PDU, causing CRC pass on UE side, for DRB in repetitions as per DL_REPETITION_NUMBER }

then { the UE transmits an ACK for the entire bundle as feedback of the corresponding HARQ process and delivers data to upper layers }

}

7.1.3.4a.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 & 5.3.2.2 and TS 36.213, clause 7.1.11.

[TS 36.321, clause 5.3.2.1]

There is one HARQ entity at the MAC entity for each Serving Cell which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).

The number of DL HARQ processes per HARQ entity is specified in [2], clause 7.

When the physical layer is configured for downlink spatial multiplexing [2], one or two TBs are expected per subframe and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.

For BL UEs or UEs in enhanced coverage, the parameter DL_REPETITION_NUMBER provides the number of transmissions repeated in a bundle. For each bundle, DL_REPETITION_NUMBER is set to a value provided by lower layers. Within a bundle, after the initial (re)transmission, DL_REPETITION_NUMBER HARQ retransmissions follow. The HARQ feedback is transmitted for the bundle and a downlink assignment corresponding to a new transmission or a retransmission of the bundle is received after the last repetition of the bundle. A retransmission of a bundle is also a bundle.

The MAC entity shall:

– If a downlink assignment has been indicated for this TTI:

– allocate the TB(s) received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information.

– If a downlink assignment has been indicated for the broadcast HARQ process:

– allocate the received TB to the broadcast HARQ process.

NOTE: In case of BCCH a dedicated broadcast HARQ process is used.

[TS 36.321, clause 5.3.2.2]

For each subframe where a transmission takes place for the HARQ process, one or two (in case of downlink spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity.

For each received TB and associated HARQ information, the HARQ process shall:

– if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or

– if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB according to the system information schedule indicated by RRC; or

– if this is the very first received transmission for this TB (i.e. there is no previous NDI for this TB):

– consider this transmission to be a new transmission.

– else:

– consider this transmission to be a retransmission.

The MAC entity then shall:

– if this is a new transmission:

– attempt to decode the received data.

– else if this is a retransmission:

– if the data for this TB has not yet been successfully decoded:

– combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data.

– if the data which the MAC entity attempted to decode was successfully decoded for this TB; or

– if the data for this TB was successfully decoded before:

– if the HARQ process is equal to the broadcast process:

– deliver the decoded MAC PDU to upper layers.

– else if this is the first successful decoding of the data for this TB:

– deliver the decoded MAC PDU to the disassembly and demultiplexing entity.

– generate a positive acknowledgement (ACK) of the data in this TB.

– else:

– replace the data in the soft buffer for this TB with the data which the MAC entity attempted to decode.

– generate a negative acknowledgement (NACK) of the data in this TB.

– if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention Resolution is not yet successful (see subclause 5.1.5); or

– if the HARQ process is equal to the broadcast process; or

– if the timeAlignmentTimer, associated with the TAG containing the serving cell on which the HARQ feedback is to be transmitted, is stopped or expired:

– do not indicate the generated positive or negative acknowledgement to the physical layer.

– else:

– indicate the generated positive or negative acknowledgement for this TB to the physical layer.

[TS 36.213, clause 7.1.11]

A BL/CE UE shall upon detection of a MPDCCH with DCI format 6-1A/6-1B/6-2 intended for the UE, adjust the corresponding PDSCH transmission in subframe(s) n+ki with i = 0, 1, …, N-1 according to the MPDCCH, where

– subframe n is the last subframe in which the MPDCCH is transmitted and is determined from the starting subframe of MPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; and

– subframe(s) n+ki with i=0,1,…,N-1 are N consecutive BL/CE DL subframe(s) where, 2≤k0<k1<…,kN-1 and the value of is determined by the repetition number field in the corresponding DCI, where are given in Table 7.1.11-1 and Table 7.1.11-2;

If PDSCH carrying SystemInformationBlockType1-BR or other SI messages is transmitted in subframe n+ki, a BL/CE UE shall assume any other PDSCH in the subframe n+ki is dropped.

Table 7.1.11-1: PDSCH repetition levels (DCI Format 6-1A)

Higher layer parameter

pdsch-maxNumRepetitionCEmodeA

Not configured

{1,2,4,8}

16

{1,4,8,16}

32

{1,4,16,32}

7.1.3.4a.3 Test description

7.1.3.4a.3.1 Pre-test conditions

System Simulator:

  • Cell 1

– System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.4a.3.3-1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4-CE) according to [18].

7.1.3.4a.3.2 Test procedure sequence

Table 7.1.3.4a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: Steps 1 to 7 are run 8[FDD]/9 [TDD] times using test parameter values as given for each iteration in table 7.1.3.4a.3.2.-2.

1

The SS indicates a new transmission on MPDCCH and transmits a MAC PDU (containing an RLC PDU) on HARQ process X, but the CRC is calculated in such a way that it will result in CRC error on UE side. The AMD PDU contains a full RLC SDU. (Note 3)

<–

MAC PDU

2

Note: UE should receive 4 MAC PDU repetitions as per DL_REPETITION_NUMBER (Note3).

1

3

Check: Does the UE transmit a HARQ NACK?

–>

HARQ NACK

1

P

4

The SS indicates a retransmission on MPDCCH and transmits the same MAC PDU like step 1 with CRC is calculated in such a way that it will result in CRC pass on UE side (Note 3).

<–

MAC PDU

5

Note: UE should receive 4 MAC PDU repetitions as per DL_REPETITION_NUMBER (Note3).

2

EXCEPTION: Steps 6a1 to 6a3 and step 6b describe alternative behaviours; the "lower case letter" identifies a step sequence that take place depending on UE implementation (Note 4).

6a1

The UE transmit a HARQ NACK

–>

HARQ NACK

6a2

The SS indicates a retransmission on MPDCCH and transmits the same MAC PDU like step 1 with CRC is calculated in such a way that it will result in CRC pass on UE side (Note 3).

6a3

Check: Does the UE send a HARQ ACK?

–>

HARQ ACK

2

P

6

Check: Does the UE send a HARQ ACK?

–>

HARQ ACK

2

P

7

UE transmits a Scheduling Request on PUCCH.

–>

(SR)

8

The SS sends an UL grant suitable for the loop back PDU to transmitted

<–

(UL Grant)

9

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 1 and 4.

–>

MAC PDU

Note 1: Void.

Note 2: Void.

Note 3: SS should transmit this PDU in repetitions as per the DL_REPETITION_NUMBER provided by the lower layers. In this test this value is set to 4 taken from TS 36.213 Table 7.1.11-1 PDSCH repetition levels(DCI Format 6-1A) based on IE pdsch-maxNumRepetitionCEmodeA configured to value of 16 by upper layers.

Note 4: Additional NACK is allowed to ensure that the UE has more than 50 % PDU received with CRC pass

Table 7.1.3.4a.3.2-2: Test Parameters

Iteration

DL HARQ process (X)

1

0

2

1

3

2

4

3

5

4

6

5

7

6

8

7

9

8[only for TDD]

Note: The maximum DL HARQ process is 9 for TDD configuration 1 with CEmodeA.

7.1.3.4a.3.3 Specific message contents

Table 7.1.3.4a.3.3-1: RRCConnectionReconfiguration (preamble)

Derivation path: 36.508 table 4.6.1.8

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

explicitValue SEQUENCE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

}

Table 7.1.3.4a.3.3-2: RadioResourceConfigCommon-DEFAULT (Table 7.1.3.4a.3.3-1)

Derivation Path : 36.508 table 4.6.3-13 with condition FullConfig and CEmodeA

Table 7.1.3.4a.3.3-3: PDSCH-ConfigCommon-v1310DEFAULT (Table 7.1.3.4a.3.3-2)

Derivation Path: 36.508 Table 4.6.3-5 A with CEmodeA

7.1.3.5 Correct HARQ process handling / CCCH

7.1.3.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { UE receives a MAC PDU addressed to RA-RNTI }

then { UE does not transmit ACK/NACK for the corresponding HARQ process }

}

(2)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { UE receives a MAC PDU addressed to T-CRNTI without UE Contention Resolution Identity matching the one included in the RRCConnectionRequest message }

then { UE does not transmit an ACK/NACK for the corresponding HARQ process }

}

(3)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { UE receives a MAC PDU addressed to T-CRNTI and cannot decode properly }

then { UE does not transmits a NACK for the corresponding HARQ }

}

(4)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { UE receives a MAC PDU addressed to T-CRNTI with UE Contention Resolution Identity matching the one included in the RRCConnectionRequest message }

then { UE transmits an ACK for the corresponding HARQ process and delivers data to upper layers }

}

7.1.3.5.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 and 5.3.2.2.

[TS 36.321, clause 5.3.2.1]

There is one HARQ entity at the UE which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).

The number of DL HARQ processes is specified in [2], clause 7.

When the physical layer is configured for spatial multiplexing [2], one or two TBs are expected per subframe and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.

The UE shall:

– If a downlink assignment has been indicated for this TTI:

– allocate the TBs received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information.

– If a downlink assignment has been indicated for the broadcast HARQ process:

– allocate the received TB to the broadcast HARQ process.

NOTE: In case of BCCH a dedicated broadcast HARQ process is used.

[TS 36.321, clause 5.3.2.2]

For each subframe where a transmission takes place for the HARQ process, one or two (in case of spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity.

For each received TB and associated HARQ information, the HARQ process shall:

– if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or

– if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB according to the system information schedule indicated by RRC; or

– if this is the very first received transmission for this TB(i.e. there is no previous NDI for this TB):

– consider this transmission to be a new transmission.

– else:

– consider this transmission to be a retransmission.

The UE then shall:

– if this is a new transmission

– replace the data currently in the soft buffer for this TB with the received data.

– if a retransmission is indicated for this TB:

– if the data has not yet been successfully decoded:

– combine the received data with the data currently in the soft buffer for this TB.

– if the TB size is different from the last valid TB size signalled for this TB:

– the UE may replace the data currently in the soft buffer for this TB with the received data.

– attempt to decode the data in the soft buffer for this TB;

– if the data in the soft buffer was successfully decoded for this TB:

– if the HARQ process is equal to the broadcast process:

– deliver the decoded MAC PDU to upper layers.

– else if this is the first successful decoding of the data in the soft buffer for this TB:

– deliver the decoded MAC PDU to the disassembly and demultiplexing entity.

– generate a positive acknowledgement (ACK) of the data in this TB.

– else:

– generate a negative acknowledgement (NACK) of the data in this TB.

– if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and a UE the Contention Resolution Identity match is not indicated successful (see subclause 5.1.5); or

– if the HARQ process is equal to the broadcast process; or

– – if timeAlignmentTimer is stopped or expired:

– do not indicate the generated positive or negative acknowledgement to the physical layer.

– else:

– indicate the generated positive or negative acknowledgement for this TB to the physical layer.

The UE shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.

7.1.3.5.3 Test description

7.1.3.5.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information taking into account parameters in table 7.1.3.5.3.3-1

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode state (state 2) according to [18].

7.1.3.5.3.2 Test procedure sequence

Table 7.1.3.5.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a Paging message including a matched identity.

<–

2

The UE transmits Preamble on PRACH

–>

PRACH Preamble

3

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI. The CRC is calculated in such a way, it will result in CRC error on UE side

<–

Random Access Response

4

Check: does the UE transmit a HARQ ACK/NACK?

–>

HARQ ACK/NACK

1

F

5

The UE transmits Preamble on PRACH

–>

PRACH Preamble

6

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI. The CRC is calculated in such a way, it will result in CRC pass on UE side.

<–

Random Access Response

7

Check: does the UE transmit a HARQ ACK/NACK?

–>

HARQ ACK/NACK

1

F

8

The UE transmits a MAC PDU containing an RRCConnectionRequest message.

–>

MAC PDU

9

The SS transmits a valid MAC PDU containing RRCConnectionSetup, and including ‘UE Contention Resolution Identity’ MAC control element with not matching ‘Contention Resolution Identity’.

<–

MAC PDU

10

Check: does the UE transmit a HARQ ACK/NACK?

–>

HARQ ACK/NACK

2

F

11

The UE transmits Preamble on PRACH

–>

PRACH Preamble

12

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI.

<–

Random Access Response

13

The UE transmits a MAC PDU containing an RRCConnectionRequest message.

–>

MAC PDU

14

The SS transmits a valid MAC PDU containing RRCConnectionSetup, and including ‘UE Contention Resolution Identity’ MAC control element with matching ‘Contention Resolution Identity’. The CRC is calculated in such a way that it will result in CRC error on UE side

<–

MAC PDU

15

Check: Does UE transmit a HARQ NACK?

–>

HARQ NACK

3

F

16

The UE transmits Preamble on PRACH

–>

PRACH Preamble

17

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI.

<–

Random Access Response

18

The UE transmits a MAC PDU containing an RRCConnectionRequest message.

–>

MAC PDU

19

The SS transmits the same MAC PDU like in step 14, but the CRC is calculated in such a way that it will result in CRC pass on UE side

<–

MAC PDU

20

Check: does the UE transmit a HARQ ACK?

–>

HARQ ACK

4

P

21

The UE transmits a MAC PDU containing an RRCConnectionSetupComplete message including SERVICE REQUEST message indicating acceptance of RRCConnectionSetup message

–>

MAC PDU

22-25

Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.

7.1.3.5.3.3 Specific message contents

Table 7.1.3.5.3.3-1: SystemInformationBlockType2 (all steps, table 7.1.3.5.3.2-1)

Derivation path: 36.508 table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

rach-Configuration SEQUENCE {

ra-SupervisionInformation SEQUENCE {

preambleTransMax

n8

mac-ContentionResolutionTimer

sf64

Max Value

}

}

prach-Configuration SEQUENCE {

prach-ConfigInfo SEQUENCE {

prach-ConfigurationIndex

1

As per table 5.7.1-2 of 36.211, this results in PRACH preamble transmission start in even frame numbers and sub-frame number 4

FDD

prach-ConfigurationIndex

0

As per table 5.7.1-4 of 36.211, this results in PRACH preamble transmission with frequency resource index=0; occurring in even radio frames; resource is located in first half frame and sub frame number 3 Note 1

TDD

}

}

}

ue-TimersAndConstants SEQUENCE{

t300

ms2000

T300

}

}

7.1.3.5a Correct HARQ process handling / CCCH/ Enhanced Coverage / CE Mode A

7.1.3.5a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { SS transmits a MAC PDU addressed to RA-RNTI in repetitions as per DL_REPETITION_NUMBER }

then { UE does not transmit ACK/NACK for the entire bundle as feedback of the corresponding HARQ process }

}

(2)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { SS transmits a MAC PDU addressed to T-CRNTI in repetitions as per DL_REPETITION_NUMBER without UE Contention Resolution Identity matching the one included in the RRCConnectionRequest message }

then { UE does not transmit an ACK/NACK for the entire bundle as feedback of the corresponding HARQ process }

}

(3)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { SS transmits a MAC PDU addressed to T-CRNTI in repetitions as per DL_REPETITION_NUMBER and cannot decode properly }

then { UE does not transmits a NACK for the entire bundle as feedback of the corresponding HARQ }

}

(4)

with { UE in E-UTRA RRC_IDLE state with RRC connection establishment procedure initiated }

ensure that {

when { SS transmits a MAC PDU addressed to T-CRNTI in repetitions as per DL_REPETITION_NUMBER with UE Contention Resolution Identity matching the one included in the RRCConnectionRequest message }

then { UE transmits an ACK for the corresponding HARQ process and delivers data to upper layers }

}

7.1.3.5a.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 & 5.3.2.2 and TS 36.213, clause 7.1.11.

[TS 36.321, clause 5.3.2.1]

There is one HARQ entity at the MAC entity for each Serving Cell which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).

The number of DL HARQ processes per HARQ entity is specified in [2], clause 7.

When the physical layer is configured for downlink spatial multiplexing [2], one or two TBs are expected per subframe and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.

For BL UEs or UEs in enhanced coverage, the parameter DL_REPETITION_NUMBER provides the number of transmissions repeated in a bundle. For each bundle, DL_REPETITION_NUMBER is set to a value provided by lower layers. Within a bundle, after the initial (re)transmission, DL_REPETITION_NUMBER HARQ retransmissions follow. The HARQ feedback is transmitted for the bundle and a downlink assignment corresponding to a new transmission or a retransmission of the bundle is received after the last repetition of the bundle. A retransmission of a bundle is also a bundle.

The MAC entity shall:

– If a downlink assignment has been indicated for this TTI:

– allocate the TB(s) received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information.

– If a downlink assignment has been indicated for the broadcast HARQ process:

– allocate the received TB to the broadcast HARQ process.

NOTE: In case of BCCH a dedicated broadcast HARQ process is used.

[TS 36.321, clause 5.3.2.2]

For each subframe where a transmission takes place for the HARQ process, one or two (in case of downlink spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity.

For each received TB and associated HARQ information, the HARQ process shall:

– if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or

– if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB according to the system information schedule indicated by RRC; or

– if this is the very first received transmission for this TB (i.e. there is no previous NDI for this TB):

– consider this transmission to be a new transmission.

– else:

– consider this transmission to be a retransmission.

The MAC entity then shall:

– if this is a new transmission:

– attempt to decode the received data.

– else if this is a retransmission:

– if the data for this TB has not yet been successfully decoded:

– combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data.

– if the data which the MAC entity attempted to decode was successfully decoded for this TB; or

– if the data for this TB was successfully decoded before:

– if the HARQ process is equal to the broadcast process:

– deliver the decoded MAC PDU to upper layers.

– else if this is the first successful decoding of the data for this TB:

– deliver the decoded MAC PDU to the disassembly and demultiplexing entity.

– generate a positive acknowledgement (ACK) of the data in this TB.

– else:

– replace the data in the soft buffer for this TB with the data which the MAC entity attempted to decode.

– generate a negative acknowledgement (NACK) of the data in this TB.

– if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention Resolution is not yet successful (see subclause 5.1.5); or

– if the HARQ process is equal to the broadcast process; or

– if the timeAlignmentTimer, associated with the TAG containing the serving cell on which the HARQ feedback is to be transmitted, is stopped or expired:

– do not indicate the generated positive or negative acknowledgement to the physical layer.

– else:

– indicate the generated positive or negative acknowledgement for this TB to the physical layer.

[TS 36.213, clause 7.1.11]

A BL/CE UE shall upon detection of a MPDCCH with DCI format 6-1A/6-1B/6-2 intended for the UE, adjust the corresponding PDSCH transmission in subframe(s) n+ki with i = 0, 1, …, N-1 according to the MPDCCH, where

– subframe n is the last subframe in which the MPDCCH is transmitted and is determined from the starting subframe of MPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; and

– subframe(s) n+ki with i=0,1,…,N-1 are N consecutive BL/CE DL subframe(s) where, 2≤k0<k1<…,kN-1 and the value of is determined by the repetition number field in the corresponding DCI, where are given in Table 7.1.11-1 and Table 7.1.11-2;

If PDSCH carrying SystemInformationBlockType1-BR or other SI messages is transmitted in subframe n+ki, a BL/CE UE shall assume any other PDSCH in the subframe n+ki is dropped.

Table 7.1.11-1: PDSCH repetition levels (DCI Format 6-1A)

Higher layer pararameter

pdsch-maxNumRepetitionCEmodeA

Not configured

{1,2,4,8}

16

{1,4,8,16}

32

{1,4,16,32}

7.1.3.5a.3 Test description

7.1.3.5a.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.

– System information taking into account parameters in table 7.1.3.5a.3.3-1

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode state (state 2-CE) according to [18].

7.1.3.5a.3.2 Test procedure sequence

Table 7.1.3.5a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a Paging message including a matched identity.

<–

2

The UE transmits Preamble on PRACH

–>

PRACH Preamble

3

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI. The CRC is calculated in such a way, it will result in CRC error on UE side. (Note 1)

<–

Random Access Response

4

Check: does the UE transmit a HARQ ACK/NACK for the bundle of 4 Random Access Response repetitions?

–>

HARQ ACK/NACK

1

F

5

The UE transmits Preamble on PRACH

–>

PRACH Preamble

6

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI. The CRC is calculated in such a way, it will result in CRC pass on UE side. (Note 1)

<–

Random Access Response

7

Check: does the UE transmit a HARQ ACK/NACK for the bundle of 4 Random Access Response repetitions?

–>

HARQ ACK/NACK

1

F

8

The UE transmits a MAC PDU containing an RRCConnectionRequest message.

–>

MAC PDU

9

The SS transmits a valid MAC PDU containing RRCConnectionSetup, and including ‘UE Contention Resolution Identity’ MAC control element with not matching ‘Contention Resolution Identity’. (Note 1)

<–

MAC PDU

10

Check: does the UE transmit a HARQ ACK/NACK for the bundle of 4 MAC PDU repetitions?

–>

HARQ ACK/NACK

2

F

11

The UE transmits Preamble on PRACH

–>

PRACH Preamble

12

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI. (Note 1).

<–

Random Access Response

13

The UE transmits a MAC PDU containing an RRCConnectionRequest message.

–>

MAC PDU

14

The SS transmits a valid MAC PDU containing RRCConnectionSetup, and including UE Contention Resolution Identity’ MAC control element with matching ‘Contention Resolution Identity’. The CRC is calculated in such a way that it will result in CRC error on UE side (Note 1).

<–

MAC PDU

15

Check: Does UE transmit a HARQ NACK for the bundle of 4 MAC PDU repetitions?

–>

HARQ NACK

3

F

16

The UE transmits Preamble on PRACH

–>

PRACH Preamble

17

The SS transmits Random Access Response with matching RA-Id and including T-CRNTI. (Note 1).

<–

Random Access Response

18

The UE transmits a MAC PDU containing an RRCConnectionRequest message.

–>

MAC PDU

19

The SS transmits the same MAC PDU like in step 14, but the CRC is calculated in such a way that it will result in CRC pass on UE side (Note 1).

<–

MAC PDU

20

Check: does the UE transmit a HARQ ACK for the bundle of 4 MAC PDU repetitions?

–>

HARQ ACK

4

P

21

The UE transmits a MAC PDU containing an RRCConnectionSetupComplete message including SERVICE REQUEST message indicating acceptance of RRCConnectionSetup message

–>

MAC PDU

22-25

Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.

Note 1: SS should transmit this PDU in repetitions as per the DL_REPETITION_NUMBER provided by the lower layers. In this test this value is set to 4 (in case of FDD) resp. 2 (in case of TDD) taken from TS 36.213 Table 7.1.11-1 PDSCH repetition levels(DCI Format 6-1A) based on IE pdsch-maxNumRepetitionCEmodeA configured to value of 16 (in case of FDD) resp. “omit” (in case of TDD) by upper layers.

7.1.3.5a.3.3 Specific message contents

Table 7.1.3.5a.3.3-1: Void

Table 7.1.3.5a.3.3-2: Void

Table 7.1.3.5a.3.3-3: Void

Table 7.1.3.5a.3.3-4: SystemInformationBlockType2 (preamble)

Derivation Path: 36.508 clause 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ac-BarringInfo SEQUENCE {}

Not present

radioResourceConfigCommon SEQUENCE {}

RadioResourceConfigCommonSIB-DEFAULT

See subclause 4.6.3

}

Table 7.1.3.5a.3.3-5: RadioResourceConfigCommonSIB-DEFAULT (Table 7.1.3.5a.3.3-4)

Derivation Path : 36.508 table 4.6.3-14with condition CEmodeA

Table 7.1.3.5a.3.3-6: PDSCH-ConfigCommon-v1310-DEFAULT (Table 7.1.3.5a.3.3-5)

Derivation Path: 36.508 Table 4.6.3-10A

Information Element

Value/remark

Comment

Condition

PDSCH-ConfigCommon ::= SEQUENCE {

PDSCH-ConfigCommon-v1310 ::= SEQUENCE {

pdsch-maxNumRepetitionCEmodeA-r13

omit

TDD

}

7.1.3.6 Correct HARQ process handling / BCCH

7.1.3.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives a MAC PDU addressed to SI-RNTI }

then { UE does not send any ACK/NACK for the corresponding dedicated HARQ process }

}

7.1.3.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1 & 5.3.2.2.

[TS 36.321, clause 5.3.2.1]

There is one HARQ entity at the UE which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).

The number of DL HARQ processes is specified in [2], clause 7.

When the physical layer is configured for spatial multiplexing [2], one or two TBs are expected per subframe and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.

The UE shall:

– If a downlink assignment has been indicated for this TTI:

– allocate the TBs received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information.

– If a downlink assignment has been indicated for the broadcast HARQ process:

– allocate the received TB to the broadcast HARQ process.

NOTE: In case of BCCH a dedicated broadcast HARQ process is used.

[TS 36.321, clause 5.3.2.2]

For each subframe where a transmission takes place for the HARQ process, one or two (in case of spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity.

For each received TB and associated HARQ information, the HARQ process shall:

– if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or

– if the HARQ process is equal to the broadcast process and if the physical layer indicates a new transmission for the TB according to the system information schedule indicated by RRC; or

– if this is the very first received transmission for this TB(i.e. there is no previous NDI for this TB):

– consider this transmission to be a new transmission.

– else:

– consider this transmission to be a retransmission.

The UE then shall:

– if this is a new transmission:

– replace the data currently in the soft buffer for this TB with the received data.

– else if this is a retransmission:

– if the data has not yet been successfully decoded:

– combine the received data with the data currently in the soft buffer for this TB.

– if the TB size is different from the last valid TB size signalled for this TB:

– the UE may replace the data currently in the soft buffer for this TB with the received data.

– attempt to decode the data in the soft buffer for this TB;

– if the data in the soft buffer was successfully decoded for this TB:

– if the HARQ process is equal to the broadcast process:

– deliver the decoded MAC PDU to upper layers.

– else if this is the first successful decoding of the data in the soft buffer for this TB:

– deliver the decoded MAC PDU to the disassembly and demultiplexing entity.

– generate a positive acknowledgement (ACK) of the data in this TB.

– else:

– generate a negative acknowledgement (NACK) of the data in this TB.

– if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention Resolution is not yet successful (see subclause 5.1.5); or

– if the HARQ process is equal to the broadcast process; or

– if timeAlignmentTimer is stopped or expired:

– do not indicate the generated positive or negative acknowledgement to the physical layer.

– else:

– indicate the generated positive or negative acknowledgement for this TB to the physical layer.

The UE shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.

7.1.3.6.3 Test description

7.1.3.6.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

– None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– RRC Connection Reconfiguration (Preamble: Table 4.5.3.3-1) using parameters as specified in Table 7.1.3.6.3.3-4

7.1.3.6.3.2 Test procedure sequence

Table 7.1.3.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

A

The SS transmits a Paging message including the systemInfoModification. (Note 1)

1

The SS transmits an updated system information with SI-RNTI addressed in L1/L2 header at the start of the modification period. CRC is calculated in such a way, it will result in CRC fail on UE side. Dedicated HARQ process for broadcast is used.

<–

2

Check: Does the UE transmit a HARQ ACK/NACK? (Note 2 and 3)

–>

HARQ ACK/NACK

1

F

3

Void

4

Void

5

Void

6

After 100ms of step 2, the SS transmits an updated system information [contents same as in step 1] with SI-RNTI addressed in L1/L2 header. CRC is calculated in such a way, it will result in CRC pass on UE side. Dedicated HARQ process for broadcast is used.

7

Check: Does the UE transmit an ACK/NACK? (Note 2 and 4)

->

HARQ ACK/NACK

1

F

8

SS is configured to not allocate UL Grants on Scheduling Request

9

The SS Transmits MAC PDU containing a RLC PDU

<–

MAC PDU

10

The UE transmits a HARQ ACK

–>

HARQ ACK

11

Check: Does the UE transmit PRACH Preamble, using PRACH resources as in new SI?

–>

PRACH Preamble

1

P

12

The SS transmits Random Access Response

<–

Random Access Response

13

The UE transmits a MAC PDU with C-RNTI containing loop backed RLC PDU

–>

MAC PDU

14

SS sends PDCCH transmission for UE C-RNTI to complete contention resolution.

Note 1: To guarantee that the UE will receive at least one Paging in the Modification Period preceding the SysInfo change, SS should send the Paging message in every eligible PO in this Modification Period.

Note 2: When requested to check HARQ feedback for the dedicated broadcast HARQ process, the SS shall assume the same PUCCH reception requirement as specified in TS 36.213 section 10 for a normal HARQ process.

Note 3: For duration of 100ms, the SS should check HARQ NACK for all broadcast SIBs. This duration is sufficient to ensure that SS transmits few times SIBs with CRC corruption.

Note 4: For duration of 5020ms (5120 – 100), the SS should check HARQ ACK for all broadcast SIBs. 5120ms is the system information modification period calculated based on the default values of parameters specified in TS 36.508.( modification period = modificationPeriodCoeff * defaultPagingCycle,and in TS 36.508, modificationPeriodCoeff=4 and defaultPagingCycle=128radio frames).

7.1.3.6.3.3 Specific message contents

Table 7.1.3.6.3.3-1: SystemInformationBlockType2 (steps 1 and 6 of table 7.1.3.6.3.2-1)

Derivation path: 36.508 table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

prach-Config SEQUENCE {

rootSequenceIndex

20 (u = 2, Value different than default in TS 36.508)

FDD

rootSequenceIndex

2 (u = 2, Value different than default in TS 36.508)

rootSequenceIndex should take value from table of 5.7.2-5 in TS 36.211 since, the PRACH format 4 is used as default for testing for TDD.

TDD

}

}

}

Table 7.1.3.6.3.3-2: Paging (step A, 5 of table 7.1.3.6.3.2-1)

Derivation path: 36.508 table 4.6.1-7

Information Element

Value/Remark

Comment

Condition

Paging ::= SEQUENCE {

pagingRecordList

Not present

systemInfoModification

true

etws-Indication

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

Table 7.1.3.6.3.3-3: SystemInformationBlockType1 (step 1 of table 7.1.3.6.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

systemInfoValueTag

1

}

Table 7.1.3.6.3.3-4: RRCConnectionReconfiguration (Preamble)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

7.1.3.6a Correct HARQ process handling / Enhanced Coverage / HARQ-ACK bundling

7.1.3.6a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { the SS transmits a MAC PDU }

then { the UE transmits a ACK for the entire bundle in the subframe as indicated in the ‘HARQ-ACK delay’ field in the corresponding DCI }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { the SS transmits a MAC PDU, causing CRC fail on UE side }

then { the UE transmits a NACK for the entire bundle in the subframe as indicated in the ‘HARQ-ACK delay’ field in the corresponding DCI }

}

7.1.3.6a.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.213, clauses 7.1.11 and 7.3.1.

[TS 36.213, clause 7.1.11]

A BL/CE UE shall upon detection of a MPDCCH with DCI format 6-1A/6-1B/6-2 intended for the UE, decode the corresponding PDSCH in subframe(s) n+ki with i = 0, 1, …, N-1 according to the MPDCCH, where

– subframe n is the last subframe in which the MPDCCH is transmitted and is determined from the starting subframe of MPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; and

– subframe(s) n+ki with i=0,1,…,N-1 are N consecutive BL/CE DL subframe(s) where, x=k0<k1<…,kN-1 and the value of is determined by the repetition number field in the corresponding DCI, where are given in Table 7.1.11-1, Table 7.1.11-2 and Table 7.1.11-3, respectively and subframe n+x is the second BL/CE DL subframe after subframe n.

For BL/CE UEs, and for a PDSCH transmission starting in subframe n+k0 without a corresponding MPDCCH, the UE shall decode the PDSCH transmission in subframe(s) n+ki with i = 0, 1, …, N-1, where

– subframe(s) n+ki with i=0,1,…,N-1 are N consecutive BL/CE DL subframe(s), where 0≤k0<k1<…,kN-1 and the value of is determined by the repetition number field in the activation DCI, where are given in Table 7.1.11-1, Table 7.1.11-2 and Table 7.1.11-3, respectively.

If PDSCH carrying SystemInformationBlockType1-BR is transmitted in one narrowband in subframe n+ki, a BL/CE UE shall assume any other PDSCH in the same narrowband in the subframe n+ki is dropped. If PDSCH carrying SI message is transmitted in one narrowband in subframe n+ki, a BL/CE UE shall assume any other PDSCH not carrying SystemInformationBlockType1-BR in the same narrowband in the subframe n+ki is dropped.

For a BL/CE UE in half-duplex FDD operation, if the UE is configured with CEModeA, and configured with higher layer parameter ce-HARQ-AckBundling, and ‘HARQ-ACK bundling flag’ in the corresponding DCI is set to 1, the UE shall assume .

Table 7.1.11-1: PDSCH repetition levels (DCI Format 6-1A)

Higher layer parameter

pdsch-maxNumRepetitionCEmodeA

Not configured

{1,2,4,8}

16

{1,4,8,16}

32

{1,4,16,32}

[TS 36.213, clause 7.3.1]

For a BL/CE UE, for PDSCH transmission in subframe n-k, if the UE is in half-duplex FDD operation and is configured with CEModeA and higher layer parameter ce-HARQ-AckBundling and the ‘HARQ-ACK bundling flag’ in the corresponding DCI is set to 1, or if the UE is configured with higher layer parameter ce-SchedulingEnhancement,

– if the ‘HARQ-ACK delay’ field in the corresponding DCI indicates value k, the UE shall determine the subframe n as the HARQ-ACK transmission subframe.

– the HARQ-ACK delay value k is determined from the corresponding DCI based on the higher layer parameters according to Table 7.3.1-2.

For a BL/CE UE in half-duplex FDD operation, if the UE is configured with CEModeA, and if the UE is configured with higher layer parameter ce-HARQ-AckBundling and the ‘HARQ-ACK bundling flag’ in the corresponding DCI is set to 1.

– for HARQ-ACK transmission in subframe n, the UE shall generate one HARQ-ACK bit by performing a logical AND operation of HARQ-ACKs across all BL/CE DL subframes for which subframe n is the ‘HARQ-ACK transmission subframe’.

– if subframe n-k1 is the most recent subframe for which subframe n is the ‘HARQ-ACK transmission subframe’, and if the ‘Transport blocks in a bundle’ field in the corresponding DCI for PDSCH transmission in subframe n-k1 indicates a value other than , the UE shall generate a NACK for HARQ-ACK transmission in subframe n.

– if the UE has received W PDSCH transmissions before subframe n, and if the UE is expected to transmit HARQ-ACK for the W PDSCH transmissions in subframes , the UE is not expected to receive a new PDSCH transmission in subframe n, where W=10 if higher layer parameter ce-pdsch-tenProcesses-config is set to ‘On‘, and W=8 otherwise.

– if the UE is expected to transmit HARQ-ACK for the PDSCH transmissions received before subframe n in subframes , the UE is not expected to receive a new PDSCH transmission in subframe n for which the HARQ-ACK is to be transmitted in subframe

Table 7.3.1-2: HARQ-ACK delay for BL/CE UE in CEModeA

‘HARQ-ACK delay’ field in DCI

HARQ-ACK delay value when ‘ce-SchedulingEnhancement’ set to ‘range1’

HARQ-ACK delay value when ‘ce-SchedulingEnhancement’ set to ‘range2’ or ’ce-HARQ-AckBundling’ is set

000

4

4

001

5

5

010

7

6

011

9

7

100

11

8

101

13

9

110

15

10

111

17

11

[TS 36.321, clause 5.3.2.1]

There is one HARQ entity at the UE which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).

The number of DL HARQ processes is specified in [2], clause 7.

When the physical layer is configured for spatial multiplexing [2], one or two TBs are expected per subframe and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.

The UE shall:

– If a downlink assignment has been indicated for this TTI:

– allocate the TBs received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information.

– If a downlink assignment has been indicated for the broadcast HARQ process:

– allocate the received TB to the broadcast HARQ process.

NOTE: In case of BCCH a dedicated broadcast HARQ process is used.

[TS 36.321, clause 5.3.2.2]

For each subframe where a transmission takes place for the HARQ process, one or two (in case of spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity.

For each received TB and associated HARQ information, the HARQ process shall:

– if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or

– if the HARQ process is equal to the broadcast process and if the physical layer indicates a new transmission for the TB according to the system information schedule indicated by RRC; or

– if this is the very first received transmission for this TB(i.e. there is no previous NDI for this TB):

– consider this transmission to be a new transmission.

– else:

– consider this transmission to be a retransmission.

The UE then shall:

– if this is a new transmission:

– replace the data currently in the soft buffer for this TB with the received data.

– else if this is a retransmission:

– if the data has not yet been successfully decoded:

– combine the received data with the data currently in the soft buffer for this TB.

– if the TB size is different from the last valid TB size signalled for this TB:

– the UE may replace the data currently in the soft buffer for this TB with the received data.

– attempt to decode the data in the soft buffer for this TB;

– if the data in the soft buffer was successfully decoded for this TB:

– if the HARQ process is equal to the broadcast process:

– deliver the decoded MAC PDU to upper layers.

– else if this is the first successful decoding of the data in the soft buffer for this TB:

– deliver the decoded MAC PDU to the disassembly and demultiplexing entity.

– generate a positive acknowledgement (ACK) of the data in this TB.

– else:

– generate a negative acknowledgement (NACK) of the data in this TB.

– if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention Resolution is not yet successful (see subclause 5.1.5); or

– if the HARQ process is equal to the broadcast process; or

– if timeAlignmentTimer is stopped or expired:

– do not indicate the generated positive or negative acknowledgement to the physical layer.

– else:

– indicate the generated positive or negative acknowledgement for this TB to the physical layer.

The UE shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission.

7.1.3.6a.3 Test description

7.1.3.6a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

– Configured to use HARQ-ACK bundling

Preamble:

– System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.4a.3.3-1.

7.1.3.6a.3.2 Test procedure sequence

Table 7.1.3.6a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The following step shall be repeated 3 times.

1

The SS transmits a valid MAC PDU (Note 1).

<–

MAC PDU

2

The SS transmits a MAC PDU, but the CRC is calculated in such a way that it will result in CRC error on UE side (Note 1).

<–

MAC PDU

3

Check: Does the UE transmit a HARQ NACK?

–>

HARQ NACK

1

P

4

The SS retransmits the MAC PDUs transmitted in steps 2 and 3 above but with CRC calculated in such a way that it will result in CRC pass on UE side (Note 1).

<–

MAC PDU

5

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

2

P

6

UE transmits a Scheduling Request on PUCCH.

–>

(SR)

7

The SS sends an UL grant suitable for the loop back PDU to transmitted

<–

(UL Grant)

8

The UE transmits the MAC PDUs containing the loopback PDUs corresponding to step 4.

–>

MAC PDU

Note 1: SS should transmit this PDU in repetitions as per the DL_REPETITION_NUMBER provided by the lower layers. SS shall set the ‘HARQ-ACK bundling flag’ in the corresponding DCI is to 1, thus the SS shall use the value 1 for DL_REPETITION_NUMBER, see TS 36.213 Table 7.1.11. The SS shall also set the ‘HARQ-ACK delay’ field in in the corresponding DCI is to ‘000’ to indicate a HARQ-ACK delay of 4 subframes to the UE.

7.1.3.6a.3.3 Specific message contents

Table 7.1.3.6a.3.3-1: UECapabilityInformation (preamble)

Derivation Path: 36.508 Table 4.6.1.23

Information Element

Value/Remark

Comment

Condition

UE-EUTRA-Capability ::= SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

fdd-Add-UE-EUTRA-Capabilities-v1430 SEQUENCE {

phyLayerParameters-v1430 SEQUENCE {

ce-HARQ-AckBundling-r14

supported

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 7.1.3.6a.3.3-2: RadioResourceConfigCommon-DEFAULT (preamble)

Derivation Path: 36.508 table 4.6.3-13 with condition FullConfig and CEmodeA

Table 7.1.3.6a.3.3-3: PhysicalConfigDedicated-DEFAULT (preamble)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with CEmodeA

Information Element

Value/Remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

pdsch-ConfigDedicated-v1430 SEQUENCE {

ce-HARQ-AckBundling-r14

on

}

}

Table 7.1.3.6a.3.3-4: PDSCH-ConfigCommon-v1310-DEFAULT (preamble)

Derivation Path: 36.508 Table 4.6.3-5A with CEmodeA

7.1.3.7 MAC padding

7.1.3.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when{ UE is receiving RLC PDUs in MAC PDUs with padding greater than 2 bytes }

then { UE acknowledges reception of the RLC PDUs }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE is receiving RLC PDUs in MAC PDUs with padding equal to or less than 2 bytes }

then { UE acknowledges reception of the RLC PDUs }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { SS is transmitting a MAC control Timing Advance PDU with padding equal to or less than 2 bytes and no Data MAC PDU sub-headers followed by transmitting a RLC PDU }

then { UE acknowledges reception of the RLC PDU using the new Timing Advance }

}

7.1.3.7.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 6.1.2.

[TS 36.321 clause 6.1.2]

Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may have any value and the UE shall ignore it. When padding is performed at the end of the MAC PDU, zero or more padding bytes are allowed.

When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding are placed at the beginning of the MAC PDU before any other MAC PDU subheader.

A maximum of one MAC PDU can be transmitted per TB per UE.

Figure 6.1.2-3: Example of MAC PDU consisting of MAC header, MAC control elements, MAC SDUs and padding

7.1.3.7.3 Test description

7.1.3.7.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The UL RLC SDU size is set to not return any data.

7.1.3.7.3.2 Test procedure sequence

Table 7.1.3.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a MAC PDU containing an RLC SDU in an AMD PDU with polling field ‘P’ set to ‘1’. The MAC SDU payload is set 8 bytes smaller than the TB size allocated in the DL Assignment minus AMD PDU and MAC headers. SS adds a 7-byte padding at the end of the MAC PDU and inserts a MAC padding sub-header after the MAC SDU sub-header.

<–

MAC PDU(AMD PDU, 7-byte padding)

2

Check: Does the UE transmit an RLC STATUS PDU with ACK_SN field equal to 1?

–>

RLC STATUS PDU (ACK_SN ‘1’)

1

P

3

The SS transmits a MAC PDU containing an RLC SDU in an AMD PDU with polling field ‘P’ set to ‘1’. The MAC SDU payload is set to 1-byte smaller than the TB size allocated in the DL Assignment minus AMD PDU and MAC headers. SS adds a 1 byte padding by inserting a MAC PDU sub-header before first Data MAC PDU sub-header.

<–

MACPDU(AMD PDU, one byte padding)

4

Check: Does the UE transmit an RLC STATUS PDU with ACK_SN field equal to 2?

–>

MAC PDU(RLC STATUS PDU (ACK_SN =2) )

2

P

5

The SS sets the downlink assignment for TBS of ’16-bits’

6

The SS transmits a Timing Advance without any additional padding. Start Timer_1 = Time Alignment timer value.

<–

MAC Control PDU(Timing Advance)

7

The SS sets the downlink assignment for TBS of ’24-bits’

8

The SS waits a time period equal to 0.5 of Timer_1 value and configures a MAC PDU that consists of only a Control MAC PDU sub header (8-bits). Transmit another Timing Advance MAC PDU (8-bits) which leaves 1-byte padding. The SS does not transmit any subsequent timing alignment. Restart Timer_1 = Time Alignment timer value

<–

MAC Control Element (Timing Advance) + 1-byte padding

9

The SS waits a time period equal to 0.7 of Timer_1.

9A

SS transmits MAC PDU containing one RLC SDU in an AMD PDU with polling field ‘P’ set to ‘1’.

<–

MAC PDU(AMD PDU (SN=2, P=1))

10

Check: Does the UE transmit an RLC STATUS PDU acknowledging the reception of the RLC PDU in step 9 with new Timing Advance?

–>

MAC PDU(RLC STATUS PDU (ACK_SN =3))

3

P

7.1.3.7.3.3 Specific Message Contents

None.

7.1.3.8 Void

7.1.3.9 MAC reset / DL

7.1.3.9.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE MAC is reset, due to handover to a new cell }

then { UE flushes DL HARQ buffer }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state )

ensure that {

when{ UE MAC is reset, due to handover to a new cell }

then { UE considers the next transmission for each DL HARQ process as very first }

}

7.1.3.9.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.9.

[TS 36.321 clause 5.9]

If a reset of the MAC entity is requested by upper layers, the UE shall:

– initialize Bj for each logical channel to zero;

– stop (if running) all timers;

– consider the timeAlignmentTimer as expired and perform the corresponding actions in subclause 5.2;

– set the NDIs for all uplink HARQ processes to the value 0;

– stop, if any, ongoing RACH procedure;

– discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any;

– flush Msg3 buffer;

– cancel, if any, triggered Scheduling Request procedure;

– cancel, if any, triggered Buffer Status Reporting procedure;

– cancel, if any, triggered Power Headroom Reporting procedure;

– flush the soft buffers for all DL HARQ processes;

– for each DL HARQ process, consider the next received transmission for a TB as the very first;

– release, if any, Temporary C-RNTI.

7.1.3.9.3 Test description

7.1.3.9.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18] using parameters as specified in Table 7.1.3.9.3.3-3.

7.1.3.9.3.2 Test procedure sequence

Table 7.1.3.9.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 7.1.3.9.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15Khz

-85

Off

T1

Cell-specific RS EPRE

dBm/15Khz

-85

-79

Table 7.1.3.9.3.3-2 illustrates the specific message content of RRC Connection Reconfiguration message during preamble.

Table 7.1.3.9.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 2 power level according to the row "T1" in table 7.1.3.9.3.2-1

2

The SS transmits a MAC PDU containing one RLC SDU on DRB, but the CRC is calculated in such a way that it will result in CRC error on UE side.

<–

MAC PDU (1 RLC SDU of 38 bytes on DRB)

3

The UE transmit a HARQ NACK

–>

HARQ NACK

4

Void

5

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2

<–

6

The UE transmits on Cell 2, RRCConnectionReconfigurationComplete

–>

7

Check: For 100 ms, does the UE transmit any HARQ NACK?

–>

HARQ NACK

1

F

8

The SS transmits a MAC PDU containing RLC SDU on DRB. The HARQ Process and NDI on PDCCH is same as in step 2. The SS shall ensure that the HARQ process used at step 2 will not be used in between steps 4 and 7.

<–

MAC PDU (1 RLC SDU of 38 bytes on DRB)

9

Check: Does the UE transmit a scheduling request?

–>

(SR)

2

P

10

The SS allocates UL Grant sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission

<–

Uplink Grant

11

The UE transmits a MAC PDU including one RLC SDU

–>

MAC PDU

7.1.3.9.3.3 Specific Message Contents

Table 7.1.3.9.3.3-1: RRCConnectionReconfiguration (step 5, table 7.1.3.9.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo SEQUENCE {

MobilityControlInfo-HO

targetPhysCellId

PhysicalCellIdentity of Cell 2 (see 36.508 clause 4.6.5)

carrierFreq

Not present

}

nonCriticalExtension SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 7.1.3.9.3.3-2: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.3.9.3.3-3: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)}

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1

Information Element

Value/Remark

Comment

Condition

RLC-Config-DRB-AM ::= CHOICE {

am SEQUENCE {

ul-AM-RLC SEQUENCE {

t-PollRetransmit

ms250

}

}

}

7.1.3.10

7.1.3.11 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell

7.1.3.11.1 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Intra-band Contiguous CA

7.1.3.11.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU for DRB and decode fails }

then { the UE transmits a NACK for the corresponding HARQ process within HARQ entity }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU retransmission for DRB, and results in successful decode }

then { the UE transmits an ACK for the corresponding HARQ process within HARQ entity and delivers data to upper layers }

}

7.1.3.11.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1.

[TS 36.321, clause 5.3.2.1]

There is one HARQ entity at the UE for each Serving Cell which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see subclause 5.3.2.2).

The number of DL HARQ processes per HARQ entity is specified in [2], clause 7.

When the physical layer is configured for downlink spatial multiplexing [2], one or two TBs are expected per subframe and they are associated with the same HARQ process. Otherwise, one TB is expected per subframe.

The UE shall:

– If a downlink assignment has been indicated for this TTI:

– allocate the TB(s) received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information.

– If a downlink assignment has been indicated for the broadcast HARQ process:

– allocate the received TB to the broadcast HARQ process.

NOTE: In case of BCCH a dedicated broadcast HARQ process is used.

7.1.3.11.1.3 Test description

7.1.3.11.1.3.1 Pre-test conditions

System Simulator:

  • Cell 1 (PCell) and Cell 3(SCell)
  • Cell 3 is an Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.11.1.3.3-1 and 7.1.3.11.1.3.3-2.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18].

7.1.3.11.1.3.2 Test procedure sequence

In Table 7.1.3.11.1.3.2-1, Row marked "T0" denotes the initial conditions which illustrates the downlink power levels and other changing parameters to be applied for the cells after preamble.

Table 7.1.3.11.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-85

Table 7.1.3.11.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 3) addition.

<–

RRCConnectionReconfiguration

2

The UE transmit an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits Activation MAC control element to activate Scell (Cell 3).

<–

MAC PDU (Activation (C1=1))

3A

Wait for 100ms to handle any UE messages related to the completion of the HARQ process

4

The SS indicates a new transmission on PDCCH of CC1 and transmits a MAC PDU (containing an RLC PDU with SN=0), with content set so that UE could not successfully decode the data from its soft buffer. (Note 1)

<–

MAC PDU (CC1)

5

Check: Does the UE transmit a HARQ NACK for the DL data corresponding DL CC1?

–>

HARQ NACK (CC1)

1

P

EXCEPTION: Step 6 shall be repeated till HARQ ACK is received at step 7 or until HARQ retransmission count = 4 is reached for MAC PDU at step 7 (Note 2).

6

The SS indicates a retransmission on PDCCH of CC1 and transmits the same MAC PDU like step 4 (Note 1).

<–

MAC PDU (CC1)

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 7 (Note 2).

7

Check: Does the UE send a HARQ ACK for the DL data corresponding to DL CC1?

–>

HARQ ACK (CC1)

2

P

8

The UE transmit a Scheduling Request on PUCCH

–>

(SR)

9

The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1.

<–

(UL Grant)

10

The UE transmit a MAC PDU containing the loop back PDU corresponding to step 4 and 6

–>

MAC PDU

10a

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 10

<–

MAC PDU (CC1)

11

The SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU with SN=1), with content set so that UE could not successfully decode the data from its soft buffer. (Note 1)

<–

MAC PDU (CC2)

12

Check: Does the UE transmit a HARQ NACK for the DL data corresponding to DL CC2?

–>

HARQ NACK (CC2)

1

P

EXCEPTION: Step 13 shall be repeated till HARQ ACK is received at step 14 or until HARQ retransmission count = 4 is reached for MAC PDU at step 14 (Note 2).

13

The SS indicates a retransmission on PDCCH of CC2 and transmits the same MAC PDU like step 11 (Note 1).

<–

MAC PDU (CC2)

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 14 (Note 2).

14

Check: Does the UE send a HARQ ACK for the DL data corresponding to DL CC2?

–>

HARQ ACK (CC2)

2

P

15

UE transmit a Scheduling Request on PUCCH

–>

(SR)

16

The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1.

<–

(UL Grant)

17

The UE transmit a MAC PDU containing the loop back PDU corresponding to step 11 and 13

–>

MAC PDU

17a

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 17

<–

MAC PDU (CC1)

EXCEPTION: Steps 18 to 21 are run 8 [FDD]/7 [TDD] times using test parameter values as given for each iteration in table 7.1.3.11.1.3.2-4 (Note 6).

18

The SS indicates new transmissions on PDCCHs of CC1 and CC2 and transmits a MAC PDU (containing an RLC PDU) on both CCs respectively with contents set so that UE could not successfully decode the data from its soft buffers. (Note 1) (Note 6).

<–

MAC PDU (CC1) and MAC PDU (CC2)

19

Check: Does the UE transmit HARQ NACK for the DL data corresponding to DL CC1 and CC2 respectively?

–>

HARQ NACK (CC1 and CC2)

1

P

EXCEPTION: In parallel with steps 20 to 21, the parallel behaviour in table 7.1.3.11.1.3.2-3 is running.

EXCEPTION: Step 20 shall be repeated till HARQ ACK is received at step 21 for the data corresponding both DL CC1 and DL CC2 or until HARQ retransmission count = 4 is reached for MAC PDUs at step 21 (Note 2).

20

The SS indicates retransmissions on PDCCHs of CC1 and CC2 and transmits the same MAC PDUs like step 18 (Note 1)(Note 3).

<–

MAC PDU (CC1) and MAC PDU(CC2)

EXCEPTION: Up to 3 HARQ NACK per CC from the UE should be allowed at step 21 (Note 2).

21

Check: Does the UE send a HARQ ACKs for the DL data corresponding to DL CC1 and DL CC2 (Note 7)?

–>

HARQ ACK (CC1) and HARQ ACK (CC2)

2

P

Note 1: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in TBSize of 328 and having coding rate more than 1.

Note 2: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption that, given the radio conditions used in this test case, a UE soft combiner implementation should have sufficient retransmissions to be able to successfully decode the data in its soft buffer.

Note 3: Retransmission is done only for the DL CCs, for which HARQ NACK was received.

Note 4: Void.

Note 5: CC1 corresponds to Pcell (Cell 1) and CC2 corresponds to Scell (Cell 3).

Note 6: At each iteration RLC PDU SN is incremented by 1 such that RLC PDUs with SN = 2, 4, 6, 8, 10 (and 12) are being transmitted on CC1 whereas RLC PDUs with SN = 3, 5, 7, 9, 11 (and 13) on CC2.

Note 7: HARQ ACKs are expected only for those CCs for which retransmission was done in step 20.

Table 7.1.3.11.1.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

Wait for 50ms after SS sends MAC PDU on both CCs at Step 18 in Table 7.1.3.11.1.3.2-2 to ensure HARQ processes for both CCs are finished.

3

The SS allocates UL Grant sufficient for two RLC SDU to be loop backed on Cell 1.

<–

(UL Grant)

4

The UE transmits a MAC PDU including two RLC SDU corresponding to step 18 in table 7.1.3.11.1.3.2-2.

–>

MAC PDU

5

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDUs in step 4

<–

MAC PDU (CC1)

Table 7.1.3.11.1.3.2-4: Test Parameters

Iteration

DL HARQ process (X)

1

0

2

1

3

2

4

3

5

4

6

5

7

6

8

7[only for FDD]

Note: The maximum DL HARQ process is 7 for TDD configuration 1.

7.1.3.11.1.3.3 Specific message contents

Table 7.1.3.11.1.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 Table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig SEQUENCE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.3.11.1.3.3-2: SchedulingRequest-Configuration (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 clause 4.6.3-20

Information Element

Value/remark

Comment

Condition

SchedulingRequest-Configuration ::= CHOICE {

setup SEQUENCE {

dsr-TransMax

n8

}

}

Table 7.1.3.11.1.3.3-2A: RLC-Config-DRB-AM (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1

Information Element

Value/Remark

Comment

Condition

RLC-Config-DRB-AM ::= CHOICE {

am SEQUENCE {

ul-AM-RLC SEQUENCE {

t-PollRetransmit

ms200

}

}

}

Table 7.1.3.11.1.3.3-3: RRCConnectionReconfiguration (step 1, Table 7.1.3.11.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.3.11.1.3.3-4: SCellToAddMod-r10 (Table 7.1.3.11.1.3.3-3)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 7.1.3.11.1.3.3-5: MAC-MainConfig-RBC (Table 7.1.3.11.3.3-4)

Derivation Path: 36.508, Table 4.8.2.1.5, condition SCell_AddMod

Information Element

Value/remark

Comment

Condition

mac-MainConfig-v1020

mac-MainConfig-v1020SEQUENCE {

sCellDeactivationTimer-r10

rf128

}

7.1.3.11.2 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Inter-band CA

The scope and description of the present TC is the same as test case 7.1.3.11.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Active SCell according to [18] cl. 6.3.4.

7.1.3.11.3 CA / Correct HARQ process handling / DCCH and DTCH / Pcell and Scell / Intra-band non-Contiguous CA

The scope and description of the present TC is the same as test case 7.1.3.11.1 with the following differences:

– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA

7.1.3.11.4 FDD-TDD CA / Correct HARQ process handling / DCCH and DTCH / FDD PCell and TDD SCell

7.1.3.11.4.1 Test Purpose (TP)

(1)

with { UE supporting of FDD-TDD CA with FDD PCell and TDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU for DRB of FDD PCell in SF-Num x and decode fails }

then { the UE transmits a NACK in SF-Num x+4 for the corresponding FDD PCell HARQ process within HARQ entity }

}

(2)

with { UE supporting of FDD-TDD CA with FDD PCell and TDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU retransmission and results in successful decode for DRB of FDD PCell for the UE’s C-RNTI in the SF-Num x }

then { the UE transmits an ACK in SF-Num x+4 for the corresponding HARQ process of FDD PCell within HARQ entity and delivers data to upper layers }

}

(3)

with { the UE supporting of TDD-FDD CA with FDD PCell and TDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives downlink assignment on the PDCCH of TDD SCell for the UE’s C-RNTI and receives data in the associated SF-Num y and decode fails }

then { the UE transmits a NACK in SF-Num y+4 for the HARQ process of TDD SCell by following FDD PCell timing }

}

(4)

with { the UE supporting of TDD-FDD CA with FDD PCell and TDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU retransmission and results in successful decode for DRB of TDD SCell for the UE’s C-RNTI in the SF-Num y }

then { the UE transmits an ACK in SF-Num y+4 for the HARQ process of TDD SCell by following FDD PCell timing }

}

7.1.3.11.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clauses 7 and 10.2. Unless otherwise stated these are Rel-12 requirements.

[TS 36.213, clause 7]

For FDD-TDD and primary cell frame structure type 1, there shall be a maximum of 8 downlink HARQ processes per serving cell.

[TS 36.213, clause 10.2]

For FDD or for FDD-TDD and primary cell frame structure type 1, the UE shall upon detection of a PDSCH transmission in subframe n-4 intended for the UE and for which an HARQ-ACK shall be provided, transmit the HARQ-ACK response in subframe n. If HARQ-ACK repetition is enabled, upon detection of a PDSCH transmission in subframe n-4 intended for the UE and for which HARQ-ACK response shall be provided, and if the UE is not repeating the transmission of any HARQ-ACK in subframe corresponding to a PDSCH transmission in subframes , … , , the UE:

– shall transmit only the HARQ-ACK response (corresponding to the detected PDSCH transmission in subframe ) on PUCCH in subframes , , …, ;

– shall not transmit any other signal in subframes , , …, ; and

– shall not transmit any HARQ-ACK response repetitions corresponding to any detected PDSCH transmission in subframes , …, .

For FDD-TDD and primary cell frame structure type 1, if a serving cell is a secondary serving cell with frame structure type 2, the DL-reference UL/DL configuration for the serving cell is the UL/DL configuration of the serving cell.

7.1.3.11.4.3 Test description

7.1.3.11.4.3.1 Pre-test conditions

System Simulator:

  • Cell 1 PCell (FDD), Cell 10 SCell (TDD)
  • Cell 10 is Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.11.4.3.3-1

UE:

None.

Preamble:

– The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no data in uplink.

7.1.3.11.4.3.2 Test procedure sequence

In Table 7.1.3.11.4.3.2-1, Row marked "T0" denotes the initial conditions which illustrates the downlink power levels and other changing parameters to be applied for the cells after preamble.

Table 7.1.3.11.4.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 10

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-85

Table 7.1.3.11.4.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits Activation MAC control element to activate SCell (Cell 10).

<–

MAC PDU (Activation (C1=1))

3A

Wait for 100ms to handle any UE messages related to the completion of the HARQ process

4

The SS indicates a new transmission on PDCCH of CC1 and transmits a MAC PDU (containing an RLC PDU with SN=0) in SF-Num ‘X’, with content set so that UE could not successfully decode the data from its soft buffer. (Note 1)

<–

MAC PDU (CC1)

5

Check: Does the UE transmit a HARQ NACK for the DL data corresponding DL CC1 in SF-Num ‘X+4’?

–>

HARQ NACK (CC1)

1

P

EXCEPTION: Step 6 shall be repeated till HARQ ACK is received at step 7 or until HARQ retransmission count = 4 is reached for MAC PDU at step 7 (Note 2).

6

The SS indicates a retransmission on PDCCH of CC1 and transmits the same MAC PDU like step 4 in SF-Num ‘X’’(Note 1).

<–

MAC PDU (CC1)

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 7 (Note 2).

7

Check: Does the UE send a HARQ ACK for the DL data corresponding to DL CC1 in SF-Num ‘X’+4’?

–>

HARQ ACK (CC1)

2

P

8

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

9

The SS sends an UL grant suitable for transmitting loop back PDU on PCell (Cell 1).

<–

(UL Grant)

10

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 4 and 6

–>

MAC PDU

10a

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 10

<–

MAC PDU (CC1)

11

The SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU with SN=1) in SF-Num ‘Y’, with content set so that UE could not successfully decode the data from its soft buffer. (Note 1)

<–

MAC PDU (CC2)

12

Check: Does the UE transmit a HARQ NACK for the DL data corresponding to DL CC2 in SF-Num ‘Y+4’?

–>

HARQ NACK (CC2)

3

P

EXCEPTION: Step 13 shall be repeated till HARQ ACK is received at step 14 or until HARQ retransmission count = 4 is reached for MAC PDU at step 14 (Note 2).

13

The SS indicates a retransmission on PDCCH of CC2 and transmits the same MAC PDU like step 11 in SF-Num ‘Y’’(Note 1).

<–

MAC PDU (CC2)

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 14 (Note 2).

14

Check: Does the UE send a HARQ ACK for the DL data corresponding to DL CC2 in SF-Num ‘Y’+4’?

–>

HARQ ACK (CC2)

4

P

15

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

16

The SS sends an UL grant suitable for transmitting loop back PDU on PCell (Cell 1).

<–

(UL Grant)

17

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 11 and 13 on PCell (Cell 1).

–>

MAC PDU

17a

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 17

<–

MAC PDU (CC2)

EXCEPTION: Steps 18 to 21 are run 8 times (Note 6).

18

The SS indicates new transmissions on PDCCHs of CC1 and CC2 and transmits a MAC PDU (containing an RLC PDU) on both CCs respectively in SF-Num ‘Z’, with contents set so that UE could not successfully decode the data from its soft buffers. (Note 1) (Note 6).

<–

MAC PDU (CC1) and MAC PDU (CC2)

19

Check: Does the UE transmit HARQ NACK for the DL data corresponding to DL CC1 and CC2 respectively in SF-Num ‘Z+4’?

–>

HARQ NACK (CC1 and CC2)

1, 3

P

EXCEPTION: In parallel with steps 20 to 21, the parallel behaviour in table 7.1.3.11.4.3.2-3 is running.

EXCEPTION: Step 20 shall be repeated till HARQ ACK is received at step 21 for the data corresponding both DL CC1 and DL CC2 or until HARQ retransmission count = 4 is reached for MAC PDUs at step 21 (Note 2).

20

The SS indicates retransmissions on PDCCHs of CC1 and CC2 and transmits the same MAC PDUs like step 18 in SF-Num ‘Z’’(Note 1)(Note 3).

<–

MAC PDU (CC1) and MAC PDU(CC2)

EXCEPTION: Up to 3 HARQ NACK per CC from the UE should be allowed at step 21 (Note 2).

21

Check: Does the UE send a HARQ ACKs for the DL data corresponding to DL CC1 and DL CC2 in SF-Num ‘Z’+4’(Note 7)?

–>

HARQ ACK (CC1) and HARQ ACK (CC2)

2, 4

P

Note 1: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in TBSize of 328 and having coding rate more than 1.

Note 2: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption that, given the radio conditions used in this test case, a UE soft combiner implementation should have sufficient retransmissions to be able to successfully decode the data in its soft buffer.

Note 3: Retransmission is done only for the DL CCs, for which HARQ NACK was received.

Note 4: Void.

Note 5: CC1 corresponds to PCell (Cell 1) and CC2 corresponds to SCell (Cell 10).

Note 6: At each iteration RLC PDU SN is incremented by 1 such that RLC PDUs with SN = 2, 4, 6, 8, 10 (and 12) are being transmitted on CC1 whereas RLC PDUs with SN = 3, 5, 7, 9, 11 (and 13) on CC2.

Note 7: HARQ ACKs are expected only for those CCs for which retransmission was done in step 20.

Table 7.1.3.11.4.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

Wait for 50ms after SS sends MAC PDU on both CCs at Step 18 in Table 7.1.3.11.4.3.2-2 to ensure HARQ processes for both CCs are finished.

3

The SS allocates UL Grant sufficient for two RLC SDU to be loop backed on Cell 1.

<–

(UL Grant)

4

The UE transmits a MAC PDU including two RLC SDU corresponding to step 18 in table 7.1.3.11.4.3.2-2 on Cell 1.

–>

MAC PDU

5

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDUs in step 4

<–

MAC PDU (CC1)

7.1.3.11.4.3.3 Specific Message Contents

Table 7.1.3.11.4.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.3.11.4.3.3-1A: RLC-Config-DRB-AM (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1

Information Element

Value/Remark

Comment

Condition

RLC-Config-DRB-AM ::= CHOICE {

am SEQUENCE {

ul-AM-RLC SEQUENCE {

t-PollRetransmit

ms200

}

}

}

Table 7.1.3.11.4.3.3-2: RRCConnectionReconfiguration (step 1, Table 7.1.3.11.4.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.3.11.4.3.3-3: SCellToAddMod-r10 (Table 7.1.3.11.4.3.2-1)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 10

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 10

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 10

Band > 64

}

Condition

Explanation

Band > 64

If band > 64 is selected

7.1.3.11.5 FDD-TDD CA / Correct HARQ process handling / DCCH and DTCH / TDD PCell and FDD SCell

7.1.3.11.5.1 Test Purpose (TP)

(1)

with { the UE supporting of FDD-TDD CA with TDD PCell and FDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU for DRB of TDD PCell in SF-Num i-K and decode fails }

then { the UE transmits a NACK in SF-Num i by setting as defined in Table 10.1.3.1-1 in TS 36.213 for the corresponding TDD PCell HARQ process within HARQ entity }

}

(2)

with { the UE supporting of FDD-TDD CA with TDD PCell and FDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU retransmission and results in successful decode for DRB of TDD PCell for the UE’s C-RNTI in the SF-Num j-K }

then { the UE transmits an ACK in SF-Num j by setting as defined in Table 10.1.3.1-1 in TS 36.213 for the corresponding HARQ process of TDD PCell within HARQ entity and delivers data to upper layers }

}

(3)

with { the UE supporting of TDD-FDD CA with TDD PCell and FDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives downlink assignment on the PDCCH of FDD SCell for the UE’s C-RNTI and receives data in the associated SF-Num x-K and decode fails }

then { the UE transmits a NACK in SF-Num x by setting as defined in Table 10.1.3A-1 in TS 36.213 for the HARQ process of FDD SCell }

}

(4)

with { the UE supporting of TDD-FDD CA with TDD PCell and FDD SCell in E-UTRA RRC_CONNECTED state with SCell activated }

ensure that {

when { the UE receives a MAC PDU retransmission and results in successful decode for DRB of FDD SCell for the UE’s C-RNTI in the SF-Num y-K }

then { the UE transmits an ACK in SF-Num y by setting as defined in Table 10.1.3A-1 in TS 36.213 for the HARQ process of FDD SCell }

}

7.1.3.11.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clauses 7, 10.2 and 10.1.3A. Unless otherwise stated these are Rel-12 requirements.

[TS 36.213, clause 7]

For FDD-TDD and primary cell frame structure type 2 and serving cell frame structure type 1, the maximum number of downlink HARQ processes for the serving cell shall be determined by the DL-reference UL/DL configuration for the serving cell (as defined in subclause 10.2), as indicated in Table 7-2.

The dedicated broadcast HARQ process defined in [8] is not counted as part of the maximum number of HARQ processes for FDD, TDD and FDD-TDD.

Table 7-2: Maximum number of DL HARQ processes for FDD-TDD, primary cell frame structure type 2, and serving cell frame structure type 1

DL-reference UL/DL

Configuration

Maximum number of HARQ processes

0

10

1

11

2

12

3

15

4

16

5

16

6

12

[TS 36.213, clause 10.1.3.1]

Table 10.1.3.1-1: Downlink association set : for TDD

UL/DL

Configuration

Subframe n

0

1

2

3

4

5

6

7

8

9

0

6

4

6

4

1

7, 6

4

7, 6

4

2

8, 7, 4, 6

8, 7, 4, 6

3

7, 6, 11

6, 5

5, 4

4

12, 8, 7, 11

6, 5, 4, 7

5

13, 12, 9, 8, 7, 5, 4, 11, 6

6

7

7

5

7

7

[TS 36.213, clause 10.1.3A]

For a serving cell, if the serving cell is frame structure type 1, and a UE is not configured to monitor PDCCH/EPDCCH in another serving cell for scheduling the serving cell, set is defined in Table 10.1.3A-1, otherwise set is defined in Table 10.1.3.1-1.

Table 10.1.3A-1: Downlink association set : for FDD-TDD and serving cell frame structure type 1

DL-reference UL/DL

Configuration

Subframe n

0

1

2

3

4

5

6

7

8

9

0

6, 5

5, 4

4

6, 5

5, 4

4

1

7, 6

6, 5, 4

7, 6

6, 5, 4

2

8, 7, 6, 5, 4

8, 7, 6, 5, 4

3

11, 10, 9, 8, 7, 6

6, 5

5, 4

4

12, 11, 10, 9, 8, 7

7, 6, 5, 4

5

13, 12, 11, 10, 9, 8, 7, 6, 5, 4

6

8, 7

7, 6

6, 5

7

7, 6, 5

[TS 36.213, clause 10.2]

For FDD-TDD and primary cell frame structure type 2, if a serving cell is a primary cell or if a serving cell is a secondary cell with frame structure type 1, then the primary cell UL/DL configuration is the DL-reference UL/DL configuration for the serving cell.

For FDD-TDD and primary cell frame structure type 2, if a serving cell is frame structure type 1 and a UE is not configured to monitor PDCCH/EPDCCH in another serving cell for scheduling the serving cell , then the UE shall upon detection of a PDSCH transmission within subframe(s) for serving cell , where , and is defined in Table 10.1.3A-1 intended for the UE and for which HARQ-ACK response shall be provided, transmit the HARQ-ACK response in subframe n.

7.1.3.11.5.3 Test description

7.1.3.11.5.3.1 Pre-test conditions

System Simulator:

  • Cell 1 PCell (TDD), Cell 10 SCell (FDD)
  • Cell 10 is Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.11.5.3.3-1

UE:

None.

Preamble:

– The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no data in uplink.

7.1.3.11.5.3.2 Test procedure sequence

In Table 7.1.3.11.5.3.2-1, Row marked "T0" denotes the initial conditions which illustrates the downlink power levels and other changing parameters to be applied for the cells after preamble.

Table 7.1.3.11.5.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 10

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-85

Table 7.1.3.11.5.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits Activation MAC control element to activate SCell (Cell 10).

<–

MAC PDU (Activation (C1=1))

3A

Wait for 100ms to handle any UE messages related to the completion of the HARQ process

4

The SS indicates a new transmission on PDCCH of CC1 and transmits a MAC PDU (containing an RLC PDU with SN=0) in SF-Num ‘i-K’, with content set so that UE could not successfully decode the data from its soft buffer. (Note 1) (Note 7)

<–

MAC PDU (CC1)

5

Check: Does the UE transmit a HARQ NACK for the DL data corresponding DL CC1 in SF-Num ‘i’?

–>

HARQ NACK (CC1)

1

P

EXCEPTION: Step 6 shall be repeated till HARQ ACK is received at step 7 or until HARQ retransmission count = 4 is reached for MAC PDU at step 7 (Note 2).

6

The SS indicates a retransmission on PDCCH of CC1 and transmits the same MAC PDU like step 4 in SF-Num ‘j-K’. (Note 1) (Note 7).

<–

MAC PDU (CC1)

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 7 (Note 2).

7

Check: Does the UE send a HARQ ACK for the DL data corresponding to DL CC1 in SF-Num ‘j’?

–>

HARQ ACK (CC1)

2

P

8

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

9

The SS sends an UL grant suitable for transmitting loop back PDU on PCell (Cell 1).

<–

(UL Grant)

10

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 4 and 6

–>

MAC PDU

10a

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 10

<–

MAC PDU (CC1)

11

The SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU with SN=1) in SF-Num ‘x-K’, with content set so that UE could not successfully decode the data from its soft buffer. (Note 1) (Note 8)

<–

MAC PDU (CC2)

12

Check: Does the UE transmit a HARQ NACK for the DL data corresponding to DL CC2 in SF-Num ‘x’?

–>

HARQ NACK (CC2)

3

P

EXCEPTION: Step 13 shall be repeated till HARQ ACK is received at step 14 or until HARQ retransmission count = 4 is reached for MAC PDU at step 14 (Note 2).

13

The SS indicates a retransmission on PDCCH of CC2 and transmits the same MAC PDU like step 11 in SF-Num ‘y-K’’(Note 1) (Note 8).

<–

MAC PDU (CC2)

EXCEPTION: Up to 3 HARQ NACK from the UE should be allowed at step 14 (Note 2).

14

Check: Does the UE send a HARQ ACK for the DL data corresponding to DL CC2 in SF-Num ‘y’?

–>

HARQ ACK (CC2)

4

P

15

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

16

The SS sends an UL grant suitable for transmitting loop back PDU on PCell (Cell 1).

<–

(UL Grant)

17

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 11 and 13 on PCell (Cell 1).

–>

MAC PDU

17a

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 17

<–

MAC PDU (CC2)

EXCEPTION: Steps 18 to 21 are run 11 times (Note 5).

18

The SS indicates new transmissions on PDCCHs of CC1 and CC2 and transmits a MAC PDU (containing an RLC PDU) on both CCs respectively in SF-Num ‘m-K’, with contents set so that UE could not successfully decode the data from its soft buffers. (Note 1) (Note 5) (Note 7) (Note 8).

<–

MAC PDU (CC1) and MAC PDU (CC2)

19

Check: Does the UE transmit HARQ NACK for the DL data corresponding to DL CC1 and CC2 respectively in SF-Num ‘m’?

–>

HARQ NACK (CC1 and CC2)

1, 3

P

EXCEPTION: In parallel with steps 20 to 21, the parallel behaviour in table 7.1.3.11.5.3.2-3 is running.

EXCEPTION: Step 20 shall be repeated till HARQ ACK is received at step 21 for the data corresponding both DL CC1 and DL CC2 or until HARQ retransmission count = 4 is reached for MAC PDUs at step 21 (Note 2).

20

The SS indicates retransmissions on PDCCHs of CC1 and CC2 and transmits the same MAC PDUs like step 18 in SF-Num ‘n-K’(Note 1)(Note 3)(Note 7) (Note 8).

<–

MAC PDU (CC1) and MAC PDU(CC2)

EXCEPTION: Up to 3 HARQ NACK per CC from the UE should be allowed at step 21 (Note 2).

21

Check: Does the UE send a HARQ ACKs for the DL data corresponding to DL CC1 and DL CC2 in SF-Num ‘n’(Note 6)?

–>

HARQ ACK (CC1) and HARQ ACK (CC2)

2, 4

P

Note 1: SS should transmit this PDU using ITBS=6, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1. This will result in TBSize of 328 and having coding rate more than 1.

Note 2: The value 4 for the maximum number of HARQ retransmissions has been chosen based on an assumption that, given the radio conditions used in this test case, a UE soft combiner implementation should have sufficient retransmissions to be able to successfully decode the data in its soft buffer.

Note 3: Retransmission is done only for the DL CCs, for which HARQ NACK was received.

Note 4: CC1 corresponds to PCell (Cell 1) and CC2 corresponds to SCell (Cell 10).

Note 5: At each iteration RLC PDU SN is incremented by 1 such that RLC PDUs with SN = 2, 4, 6, 8, 10 (and 12) are being transmitted on CC1 whereas RLC PDUs with SN = 3, 5, 7, 9, 11 (and 13) on CC2.

Note 6: HARQ ACKs are expected only for those CCs for which retransmission was done in step 20.

Note 7: For the TDD PCell HARQ timing, set is defined in Table 10.1.3.1-1 of TS 36.213[30] based on the UL/DL configuration 1. SF-Num ‘n’ can be ‘2’, ‘3’, ‘7’ and ‘8’, the corresponding SF-Num ‘n-k’ is ‘5’ or ‘6’, ‘9’, ‘0’ or ‘1’ and ‘4’.

Note 8: For the FDD SCell, set is defined in Table 10.1.3A-1 of TS 36.213[30] based on the DL-reference UL/DL configuration 1 which is the primary cell 1’s UL/DL configuration. SF-Num ‘n’ can be ‘2’, ‘3’, ‘7’ and ‘8’, the corresponding SF-Num ‘n-k’ is ‘5’ or ‘6’, ‘7’ or ‘8’ or ‘9’, ‘0’ or ‘1’ and ‘2’ or ‘3’ or ‘4’.

Table 7.1.3.11.5.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

Wait for 50ms after SS sends MAC PDU on both CCs at Step 18 in Table 7.1.3.11.5.3.2-2 to ensure HARQ processes for both CCs are finished.

3

The SS allocates UL Grant sufficient for two RLC SDU to be loop backed on Cell 1.

<–

(UL Grant)

4

The UE transmits a MAC PDU including two RLC SDU corresponding to step 18 in table 7.1.3.11.4.3.2-2 on Cell 1.

–>

MAC PDU

5

The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDUs in step 4

<–

MAC PDU (CC1)

7.1.3.11.5.3.3 Specific Message Contents

Table 7.1.3.11.5.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.3.11.5.3.3-1A: RLC-Config-DRB-AM (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1

Information Element

Value/Remark

Comment

Condition

RLC-Config-DRB-AM ::= CHOICE {

am SEQUENCE {

ul-AM-RLC SEQUENCE {

t-PollRetransmit

ms200

}

}

}

Table 7.1.3.11.5.3.3-2: RRCConnectionReconfiguration (step 1, Table 7.1.3.11.5.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.3.11.5.3.3-3: SCellToAddMod-r10 (Table 7.1.3.11.5.3.2-1)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 10

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 10

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 10

Band > 64

}

Condition

Explanation

Band > 64

If band > 64 is selected

7.1.3.12 TDD additional special subframe configuration / Special subframe pattern 9 with Normal Cyclic Prefix / CRS based transmission scheme

7.1.3.12.1 Test Purpose (TP)

(1)

with { UE in E-UTRA TDD RRC_CONNECTED state }

ensure that {

when { UE is configured with tdd-Config-v1130 equalling to ssp9 for normal cyclic prefix which is configured in UL-CyclicPrefixLength equalling to len1, network schedules and transmits PDSCH data in DwPTS }

then { UE sends ACK to the network after successfully receive and decode the data }

}

7.1.3.12.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.211 clause 4.2, TS 36.213 clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.

[TS 36.211, clause 4.2]

Frame structure type 2 is applicable to TDD. Each radio frame of length consists of two half-frames of length each. Each half-frame consists of five subframes of length. The supported uplink-downlink configurations are listed in Table 4.2-2 where, for each subframe in a radio frame, “D” denotes the subframe is reserved for downlink transmissions, “U” denotes the subframe is reserved for uplink transmissions and “S” denotes a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS is given by Table 4.2-1 subject to the total length of DwPTS, GP and UpPTS being equal to. Each subframe is defined as two slots, and of length in each subframe.

Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity are supported.

In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe exists in both half-frames.

In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe exists in the first half-frame only.

Subframes 0 and 5 and DwPTS are always reserved for downlink transmission. UpPTS and the subframe immediately following the special subframe are always reserved for uplink transmission.

In case multiple cells are aggregated, the UE may assume that the guard period of the special subframe in the different cells have an overlap of at least .

In case multiple cells with different uplink-downlink configurations are aggregated and the UE is not capable of simultaneous reception and transmission in the aggregated cells, the following constraints apply:

– if the subframe in the primary cell is a downlink subframe, the UE shall not transmit any signal or channel on a secondary cell in the same subframe

– if the subframe in the primary cell is an uplink subframe, the UE is not expected to receive any downlink transmissions on a secondary cell in the same subframe

– if the subframe in the primary cell is a special subframe and the same subframe in a secondary cell is a downlink subframe, the UE is not expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the secondary cell in the same subframe, and the UE is not expected to receive any other signals on the secondary cell in OFDM symbols that overlaps with the guard period or UpPTS in the primary cell.

Figure 4.2-1: Frame structure type 2 (for 5 ms switch-point periodicity)

Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS)

Special subframe configuration

Normal cyclic prefix in downlink

Extended cyclic prefix in downlink

DwPTS

UpPTS

DwPTS

UpPTS

Normal cyclic prefix

in uplink

Extended cyclic prefix

in uplink

Normal cyclic prefix in uplink

Extended cyclic prefix in uplink

0

1

2

3

4

5

6

7

8

9

[TS 36.213, clause 7.1.7]

To determine the modulation order and transport block size(s) in the physical downlink shared channel, the UE shall first

– read the 5-bit “modulation and coding scheme” field () in the DCI

and second if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then

– for DCI format 1A:

– set the Table 7.1.7.2.1-1 column indicator to from Section 5.3.3.1.3 in [4]

– for DCI format 1C:

– use Table 7.1.7.2.3-1 for determining its transport block size.

else

– set to the total number of allocated PRBs based on the procedure defined in Section 7.1.6.

if the transport block is transmitted in DwPTS of the special subframe in frame structure type 2, then

– for special subframe configuration 9 with normal cyclic prefix or special subframe configuration 7 with extended cyclic prefix:

– set the Table 7.1.7.2.1-1 column indicator ,

– for other special subframe configurations:

– set the Table 7.1.7.2.1-1 column indicator ,

else, set the Table 7.1.7.2.1-1 column indicator .

The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than 0.930, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits) divided by the number of physical channel bits on PDSCH. If the UE skips decoding, the physical layer indicates to higher layer that the transport block is not successfully decoded. For the special subframe configurations 0 and 5 with normal downlink CP or configurations 0 and 4 with extended downlink CP, shown in Table 4.2-1 of [3], there shall be no PDSCH transmission in DwPTS of the special subframe.

[TS 36.306, clause 4.3.4.21]

This field defines whether the UE supports TDD special subframe as specified in [TS 36.211]. It is mandatory for UEs of this release of the specification.

[TS 36.331, clause 6.3.2]

The IE TDD-Config is used to specify the TDD specific physical channel configuration.

TDD-Config information element

— ASN1START

TDD-Config ::= SEQUENCE {

subframeAssignment ENUMERATED {

sa0, sa1, sa2, sa3, sa4, sa5, sa6},

specialSubframePatterns ENUMERATED {

ssp0, ssp1, ssp2, ssp3, ssp4,ssp5, ssp6, ssp7,

ssp8}

}

TDD-Config-v1130 ::= SEQUENCE {

specialSubframePatterns-v1130 ENUMERATED {ssp7,ssp9}

}

— ASN1STOP

TDD-Config field descriptions

specialSubframePatterns

Indicates Configuration as in TS 36.211 [21, table 4.2-1] where ssp0 points to Configuration 0, ssp1 to Configuration 1 etc. Value ssp7 points to Configuration 7 for extended cyclic prefix and value ssp9 points to Configuration 9 for normal cyclic prefix. E-UTRAN signals ssp7 only when setting specialSubframePatterns (without suffix i.e. the version defined in REL-8) to ssp4. E-UTRAN signals value ssp9 only when setting specialSubframePatterns (without suffix) to ssp5. If specialSubframePatterns-v1130 is present, the UE shall ignore specialSubframePatterns (without suffix).

subframeAssignment

Indicates DL/UL subframe configuration where sa0 point to Configuration 0, sa1 to Configuration 1 etc. as specified in TS 36.211 [21, table 4.2-2]. E-UTRAN configures the same value for serving cells residing on same frequency band.

7.1.3.12.3 Test description

7.1.3.12.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18] using parameters as specified in section 7.1.3.12.3.3.

7.1.3.12.3.2 Test procedure sequence

Table 7.1.3.12.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS indicates a new transmission on PDCCH and transmits a MAC PDU in SF-Num 1 or 6 where the DwPTS belongs to.

<–

MAC PDU

2

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

3

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

4

The SS sends an UL grant suitable for the loop back PDU to be transmitted

<–

(UL Grant)

5

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 1

–>

MAC PDU

7.1.3.12.3.3 Specific message contents

Table 7.1.3.12.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.12.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp5

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp9

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.12.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell 1 (preamble when UE under test is CAT M1, Table 7.1.3.12.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3A

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1-BR-r13 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp5

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp9

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.12.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.12.3.2-1)

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

ul-CyclicPrefixLength

len1

}

}

Table 7.1.3.12.3.3-3: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

7.1.3.12a TDD additional special subframe configuration / Special subframe pattern 7 with Extended Cyclic Prefix / CRS based transmission scheme

7.1.3.12a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA TDD RRC_CONNECTED state }

ensure that {

when { UE is configured with tdd-Config-v1130 equalling to ssp7 for extended cyclic prefix which is configured in UL-CyclicPrefixLength equalling to len2, network schedules and transmits PDSCH data in DwPTS }

then { UE sends ACK to the network after successfully receive and decode the data }

}

7.1.3.12.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.211 clause 4.2, TS 36.213 clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.

[TS 36.211, clause 4.2]

Frame structure type 2 is applicable to TDD. Each radio frame of length consists of two half-frames of length each. Each half-frame consists of five subframes of length. The supported uplink-downlink configurations are listed in Table 4.2-2 where, for each subframe in a radio frame, “D” denotes the subframe is reserved for downlink transmissions, “U” denotes the subframe is reserved for uplink transmissions and “S” denotes a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS is given by Table 4.2-1 subject to the total length of DwPTS, GP and UpPTS being equal to. Each subframe is defined as two slots, and of length in each subframe.

Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity are supported.

In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe exists in both half-frames.

In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe exists in the first half-frame only.

Subframes 0 and 5 and DwPTS are always reserved for downlink transmission. UpPTS and the subframe immediately following the special subframe are always reserved for uplink transmission.

In case multiple cells are aggregated, the UE may assume that the guard period of the special subframe in the different cells have an overlap of at least .

In case multiple cells with different uplink-downlink configurations are aggregated and the UE is not capable of simultaneous reception and transmission in the aggregated cells, the following constraints apply:

– if the subframe in the primary cell is a downlink subframe, the UE shall not transmit any signal or channel on a secondary cell in the same subframe

– if the subframe in the primary cell is an uplink subframe, the UE is not expected to receive any downlink transmissions on a secondary cell in the same subframe

– if the subframe in the primary cell is a special subframe and the same subframe in a secondary cell is a downlink subframe, the UE is not expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the secondary cell in the same subframe, and the UE is not expected to receive any other signals on the secondary cell in OFDM symbols that overlaps with the guard period or UpPTS in the primary cell.

Figure 4.2-1: Frame structure type 2 (for 5 ms switch-point periodicity)

Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS)

Special subframe configuration

Normal cyclic prefix in downlink

Extended cyclic prefix in downlink

DwPTS

UpPTS

DwPTS

UpPTS

Normal cyclic prefix

in uplink

Extended cyclic prefix

in uplink

Normal cyclic prefix in uplink

Extended cyclic prefix in uplink

0

1

2

3

4

5

6

7

8

9

[TS 36.213, clause 7.1.7]

To determine the modulation order and transport block size(s) in the physical downlink shared channel, the UE shall first

– read the 5-bit “modulation and coding scheme” field () in the DCI

and second if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then

– for DCI format 1A:

– set the Table 7.1.7.2.1-1 column indicator to from Section 5.3.3.1.3 in [4]

– for DCI format 1C:

– use Table 7.1.7.2.3-1 for determining its transport block size.

else

– set to the total number of allocated PRBs based on the procedure defined in Section 7.1.6.

if the transport block is transmitted in DwPTS of the special subframe in frame structure type 2, then

– for special subframe configuration 9 with normal cyclic prefix or special subframe configuration 7 with extended cyclic prefix:

– set the Table 7.1.7.2.1-1 column indicator ,

– for other special subframe configurations:

– set the Table 7.1.7.2.1-1 column indicator ,

else, set the Table 7.1.7.2.1-1 column indicator .

The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is higher than 0.930, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits) divided by the number of physical channel bits on PDSCH. If the UE skips decoding, the physical layer indicates to higher layer that the transport block is not successfully decoded. For the special subframe configurations 0 and 5 with normal downlink CP or configurations 0 and 4 with extended downlink CP, shown in Table 4.2-1 of [3], there shall be no PDSCH transmission in DwPTS of the special subframe.

[TS 36.306, clause 4.3.4.21]

This field defines whether the UE supports TDD special subframe as specified in [TS 36.211]. It is mandatory for UEs of this release of the specification.

[TS 36.331, clause 6.3.2]

The IE TDD-Config is used to specify the TDD specific physical channel configuration.

TDD-Config information element

— ASN1START

TDD-Config ::= SEQUENCE {

subframeAssignment ENUMERATED {

sa0, sa1, sa2, sa3, sa4, sa5, sa6},

specialSubframePatterns ENUMERATED {

ssp0, ssp1, ssp2, ssp3, ssp4,ssp5, ssp6, ssp7,

ssp8}

}

TDD-Config-v1130 ::= SEQUENCE {

specialSubframePatterns-v1130 ENUMERATED {ssp7,ssp9}

}

— ASN1STOP

TDD-Config field descriptions

specialSubframePatterns

Indicates Configuration as in TS 36.211 [21, table 4.2-1] where ssp0 points to Configuration 0, ssp1 to Configuration 1 etc. Value ssp7 points to Configuration 7 for extended cyclic prefix and value ssp9 points to Configuration 9 for normal cyclic prefix. E-UTRAN signals ssp7 only when setting specialSubframePatterns (without suffix i.e. the version defined in REL-8) to ssp4. E-UTRAN signals value ssp9 only when setting specialSubframePatterns (without suffix) to ssp5. If specialSubframePatterns-v1130 is present, the UE shall ignore specialSubframePatterns (without suffix).

subframeAssignment

Indicates DL/UL subframe configuration where sa0 point to Configuration 0, sa1 to Configuration 1 etc. as specified in TS 36.211 [21, table 4.2-2]. E-UTRAN configures the same value for serving cells residing on same frequency band.

7.1.3.12a.3 Test description

7.1.3.12a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18] using parameters as specified in section 7.1.3.12a.3.3.

7.1.3.12a.3.2 Test procedure sequence

Table 7.1.3.12a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS indicates a new transmission on PDCCH and transmits a MAC PDU in SF-Num 1 or 6 where the DwPTS belongs to.

<–

MAC PDU

2

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

3

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

4

The SS sends an UL grant suitable for the loop back PDU to be transmitted

<–

(UL Grant)

5

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 1

–>

MAC PDU

7.1.3.12a.3.3 Specific message contents

Table 7.1.3.12a.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.12a.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp7

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.12a.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell 1 (preamble when UE under test is CAT M1, Table 7.1.3.12a.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3A

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1-BR-r13 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp7

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.12a.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.12a.3.2-1)

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

ul-CyclicPrefixLength

len2

}

}

Table 7.1.3.12a.3.3-3: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

7.1.3.13 TDD additional special subframe configuration / Special subframe pattern 9 with Normal Cyclic Prefix / UE-specific reference signals based transmission scheme

7.1.3.13.1 Test Purpose (TP)

(1)

with { UE in E-UTRA TDD RRC_CONNECTED state }

ensure that {

when { UE is configured with tdd-Config-v1130 equalling to ssp9 for normal cyclic prefix which is configured in UL-CyclicPrefixLength equalling to len1 under tm8 transmission mode, network uses DCI format 2B for PDSCH scheduling and transmits PDSCH data in DwPTS }

then { UE sends ACK to the network after UE successfully receives and decodes the data }

}

7.1.3.13.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.211 clause 4.2, TS 36.213 clause 6.10.3.2 and clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.

[TS 36.211, clause 4.2]

Frame structure type 2 is applicable to TDD. Each radio frame of length consists of two half-frames of length each. Each half-frame consists of five subframes of length. The supported uplink-downlink configurations are listed in Table 4.2-2 where, for each subframe in a radio frame, “D” denotes the subframe is reserved for downlink transmissions, “U” denotes the subframe is reserved for uplink transmissions and “S” denotes a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS is given by Table 4.2-1 subject to the total length of DwPTS, GP and UpPTS being equal to. Each subframe is defined as two slots, and of length in each subframe.

Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity are supported.

In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe exists in both half-frames.

In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe exists in the first half-frame only.

Subframes 0 and 5 and DwPTS are always reserved for downlink transmission. UpPTS and the subframe immediately following the special subframe are always reserved for uplink transmission.

In case multiple cells are aggregated, the UE may assume that the guard period of the special subframe in the different cells have an overlap of at least .

In case multiple cells with different uplink-downlink configurations are aggregated and the UE is not capable of simultaneous reception and transmission in the aggregated cells, the following constraints apply:

– if the subframe in the primary cell is a downlink subframe, the UE shall not transmit any signal or channel on a secondary cell in the same subframe

– if the subframe in the primary cell is an uplink subframe, the UE is not expected to receive any downlink transmissions on a secondary cell in the same subframe

– if the subframe in the primary cell is a special subframe and the same subframe in a secondary cell is a downlink subframe, the UE is not expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the secondary cell in the same subframe, and the UE is not expected to receive any other signals on the secondary cell in OFDM symbols that overlaps with the guard period or UpPTS in the primary cell.

Figure 4.2-1: Frame structure type 2 (for 5 ms switch-point periodicity)

Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS).

Special subframe configuration

Normal cyclic prefix in downlink

Extended cyclic prefix in downlink

DwPTS

UpPTS

DwPTS

UpPTS

Normal cyclic prefix
in uplink

Extended cyclic prefix
in uplink

Normal cyclic prefix in uplink

Extended cyclic prefix in uplink

0

1

2

3

4

5

6

7

8

9

[TS 36.213, clause 6.10.3.2]

For antenna ports , or , in a physical resource block with frequency-domain index assigned for the corresponding PDSCH transmission, a part of the reference signal sequence shall be mapped to complex-valued modulation symbols in a subframe according to

Normal cyclic prefix:

where

The sequence is given by Table 6.10.3.2-1.

Table 6.10.3.2-1: The sequence for normal cyclic prefix.

Antenna port

7

8

9

10

11

12

13

14

Extended cyclic prefix:

where

The sequence is given by Table 6.10.3.2-2.

Table 6.10.3.2-2: The sequence for extended cyclic prefix.

Antenna port

7

8

For extended cyclic prefix, UE-specific reference signals are not supported on antenna ports 9 to 14.

Resource elements used for transmission of UE-specific reference signals to one UE on any of the antenna ports in the set , where or shall

– not be used for transmission of PDSCH on any antenna port in the same slot, and

– not be used for UE-specific reference signals to the same UE on any antenna port other than those in in the same slot.

Figure 6.10.3.2-3 illustrates the resource elements used for UE-specific reference signals for normal cyclic prefix for antenna ports 7, 8, 9 and 10. Figure 6.10.3.2-4 illustrates the resource elements used for UE-specific reference signals for extended cyclic prefix for antenna ports 7, 8.

Figure 6.10.3.2-3: Mapping of UE-specific reference signals, antenna ports 7, 8, 9 and 10 (normal cyclic prefix)

[TS 36.213, clause 7.1]

For frame structure type 2,

– the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in any subframe in which the number of OFDM symbols for PDCCH with normal CP is equal to four;

– the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in the two PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a transmission of PBCH in the same subframe;

– the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 7, 8, 9, 10, 11, 12, 13 or 14 in the two PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a transmission of primary or secondary synchronisation signals in the same subframe;

– with normal CP configuration, the UE is not expected to receive PDSCH on antenna port 5 for which distributed VRB resource allocation is assigned in the special subframe with configuration #1 or #6;

– the UE is not expected to receive PDSCH on antenna port 7 for which distributed VRB resource allocation is assigned;

– with normal cyclic prefix, the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in DwPTS when the UE is configured with special subframe configuration 9.

– The UE may skip decoding the transport block(s) if it does not receive all assigned PDSCH resource blocks. If the UE skips decoding, the physical layer indicates to higher layer that the transport block(s) are not successfully decoded.

If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the C-RNTI, the UE shall decode the PDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5. The scrambling initialization of PDSCH corresponding to these PDCCHs is by C-RNTI.

If a UE is configured by higher layers to decode EPDCCH with CRC scrambled by the C-RNTI, the UE shall decode the EPDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5A. The scrambling initialization of PDSCH corresponding to these EPDCCHs is by C-RNTI.

If the UE is configured with the carrier indicator field for a given serving cell and, if the UE is configured by higher layers to decode PDCCH/EPDCCH with CRC scrambled by the C-RNTI, then the UE shall decode PDSCH of the serving cell indicated by the carrier indicator field value in the decoded PDCCH/EPDCCH.

When a UE configured in transmission mode 3, 4, 8, 9 or 10 receives a DCI Format 1A assignment, it shall assume that the PDSCH transmission is associated with transport block 1 and that transport block 2 is disabled.

When a UE is configured in transmission mode 7, scrambling initialization of UE-specific reference signals corresponding to these PDCCHs/EPDCCHs is by C-RNTI.

The UE does not support transmission mode 8 if extended cyclic prefix is used in the downlink.

When a UE is configured in transmission mode 9 or 10, in the subframes indicated by the higher layer parameter mbsfn-SubframeConfigList except in subframes for the serving cell

– indicated by higher layers to decode PMCH or,

– configured by higher layers to be part of a positioning reference signal occasion and the positioning reference signal occasion is only configured within MBSFN subframes and the cyclic prefix length used in subframe #0 is normal cyclic prefix,

the UE shall upon detection of a PDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for the UE or, upon detection of an EPDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for the UE, decode the corresponding PDSCH in the same subframe.

A UE configured in transmission mode 10 can be configured with scrambling identities, , by higher layers for UE-specific reference signal generation as defined in Section 6.10.3.1 of [3] to decode PDSCH according to a detected PDCCH/EPDCCH with CRC scrambled by the C-RNTI with DCI format 2D intended for the UE.

Table 7.1-5: PDCCH and PDSCH configured by C-RNTI

Transmission mode

DCI format

Search Space

Transmission scheme of PDSCH corresponding to PDCCH

Mode 1

DCI format 1A

Common and

UE specific by C-RNTI

Single-antenna port, port 0 (see subclause 7.1.1)

DCI format 1

UE specific by C-RNTI

Single-antenna port, port 0 (see subclause 7.1.1)

Mode 2

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 1

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

Mode 3

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 2A

UE specific by C-RNTI

Large delay CDD (see subclause 7.1.3) or Transmit diversity (see subclause 7.1.2)

Mode 4

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 2

UE specific by C-RNTI

Closed-loop spatial multiplexing (see subclause 7.1.4)or Transmit diversity (see subclause 7.1.2)

Mode 5

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 1D

UE specific by C-RNTI

Multi-user MIMO (see subclause 7.1.5)

Mode 6

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 1B

UE specific by C-RNTI

Closed-loop spatial multiplexing (see subclause 7.1.4) using a single transmission layer

Mode 7

DCI format 1A

Common and

UE specific by C-RNTI

If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

DCI format 1

UE specific by C-RNTI

Single-antenna port, port 5 (see subclause 7.1.1)

Mode 8

DCI format 1A

Common and

UE specific by C-RNTI

If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

DCI format 2B

UE specific by C-RNTI

Dual layer transmission, port 7 and 8 (see subclause 7.1.5A) or single-antenna port, port 7 or 8 (see subclause 7.1.1)

Mode 9

DCI format 1A

Common and

UE specific by C-RNTI

Non-MBSFN subframe: If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

MBSFN subframe: Single-antenna port, port 7 (see subclause 7.1.1)

DCI format 2C

UE specific by C-RNTI

Up to 8 layer transmission, ports 7-14 (see subclause 7.1.5B) or single-antenna port, port 7 or 8 (see subclause 7.1.1)

Mode 10

DCI format 1A

Common and

UE specific by C-RNTI

Non-MBSFN subframe: If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

MBSFN subframe: Single-antenna port, port 7 (see subclause 7.1.1)

DCI format 2D

UE specific by C-RNTI

Up to 8 layer transmission, ports 7-14 (see subclause 7.1.5B) or single-antenna port, port 7 or 8 (see subclause 7.1.1)

[TS 36.306, clause 4.3.4.21]

This field defines whether the UE supports TDD special subframe as specified in [TS 36.211]. It is mandatory for UEs of this release of the specification.

[TS 36.331, clause 6.3.2]

The IE TDD-Config is used to specify the TDD specific physical channel configuration.

TDD-Config information element

— ASN1START

TDD-Config ::= SEQUENCE {

subframeAssignment ENUMERATED {

sa0, sa1, sa2, sa3, sa4, sa5, sa6},

specialSubframePatterns ENUMERATED {

ssp0, ssp1, ssp2, ssp3, ssp4,ssp5, ssp6, ssp7,

ssp8}

}

TDD-Config-v1130 ::= SEQUENCE {

specialSubframePatterns-v1130 ENUMERATED {ssp7,ssp9}

}

— ASN1STOP

TDD-Config field descriptions

specialSubframePatterns

Indicates Configuration as in TS 36.211 [21, table 4.2-1] where ssp0 points to Configuration 0, ssp1 to Configuration 1 etc. Value ssp7 points to Configuration 7 for extended cyclic prefix and value ssp9 points to Configuration 9 for normal cyclic prefix. E-UTRAN signals ssp7 only when setting specialSubframePatterns (without suffix i.e. the version defined in REL-8) to ssp4. E-UTRAN signals value ssp9 only when setting specialSubframePatterns (without suffix) to ssp5. If specialSubframePatterns-v1130 is present, the UE shall ignore specialSubframePatterns (without suffix).

subframeAssignment

Indicates DL/UL subframe configuration where sa0 point to Configuration 0, sa1 to Configuration 1 etc. as specified in TS 36.211 [21, table 4.2-2]. E-UTRAN configures the same value for serving cells residing on same frequency band.

7.1.3.13.3 Test description

7.1.3.13.3.1 Pre-test conditions

System Simulator:

  • Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18] using parameters as specified in section 7.1.3.13.3.3.

7.1.3.13.3.2 Test procedure sequence

Table 7.1.3.13.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS indicates a new transmission on PDCCH by using DCI format 2B and transmits a MAC PDU in SF-Num 1 or 6 where the DwPTS belongs to.

<–

MAC PDU

2

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

3

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

4

The SS sends an UL grant suitable for the loop back PDU to be transmitted

<–

(UL Grant)

5

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 1

–>

MAC PDU

7.1.3.13.3.3 Specific message contents

Table 7.1.3.13.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.13.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp5

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp9

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.13.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell 1 (preamble when UE under test is CAT M1, Table 7.1.3.13.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3A

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1-BR-r13 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp5

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp9

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.13.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.13.3.2-1)

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

ul-CyclicPrefixLength

len1

}

}

Table 7.1.3.13.3.3-3: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.3.13.3.3-4: PhysicalConfigDedicated-DEFAULT (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

antennaInfo CHOICE {

explicitValue SEQUENCE {

2TX

transmissionMode

tm8-v920

ue-TransmitAntennaSelection CHOICE {

Release

NULL

}

}

}

}

7.1.3.13a TDD additional special subframe configuration / Special subframe pattern 7 with Extended Cyclic Prefix / UE-specific reference signals based transmission scheme

7.1.3.13a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA TDD RRC_CONNECTED state }

ensure that {

when { UE is configured with tdd-Config-v1130 equalling to ssp7 for extended cyclic prefix which is configured in UL-CyclicPrefixLength equalling to len2 under tm7 transmission mode, network uses DCI format 1 for PDSCH scheduling and transmits PDSCH data in DwPTS }

then { UE sends ACK to the network after UE successfully receives and decodes the data }

}

7.1.3.13a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.211 clause 4.2, TS 36.213 clause 6.10.3.2 and clause 7.1.7, TS 36.306 clause 4.3.4.21 and TS 36.331 clause 6.3.2.

[TS 36.211, clause 4.2]

Frame structure type 2 is applicable to TDD. Each radio frame of length consists of two half-frames of length each. Each half-frame consists of five subframes of length. The supported uplink-downlink configurations are listed in Table 4.2-2 where, for each subframe in a radio frame, “D” denotes the subframe is reserved for downlink transmissions, “U” denotes the subframe is reserved for uplink transmissions and “S” denotes a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS is given by Table 4.2-1 subject to the total length of DwPTS, GP and UpPTS being equal to. Each subframe is defined as two slots, and of length in each subframe.

Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity are supported.

In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe exists in both half-frames.

In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe exists in the first half-frame only.

Subframes 0 and 5 and DwPTS are always reserved for downlink transmission. UpPTS and the subframe immediately following the special subframe are always reserved for uplink transmission.

In case multiple cells are aggregated, the UE may assume that the guard period of the special subframe in the different cells have an overlap of at least .

In case multiple cells with different uplink-downlink configurations are aggregated and the UE is not capable of simultaneous reception and transmission in the aggregated cells, the following constraints apply:

– if the subframe in the primary cell is a downlink subframe, the UE shall not transmit any signal or channel on a secondary cell in the same subframe

– if the subframe in the primary cell is an uplink subframe, the UE is not expected to receive any downlink transmissions on a secondary cell in the same subframe

– if the subframe in the primary cell is a special subframe and the same subframe in a secondary cell is a downlink subframe, the UE is not expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the secondary cell in the same subframe, and the UE is not expected to receive any other signals on the secondary cell in OFDM symbols that overlaps with the guard period or UpPTS in the primary cell.

Figure 4.2-1: Frame structure type 2 (for 5 ms switch-point periodicity)

Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS)

Special subframe configuration

Normal cyclic prefix in downlink

Extended cyclic prefix in downlink

DwPTS

UpPTS

DwPTS

UpPTS

Normal cyclic prefix

in uplink

Extended cyclic prefix

in uplink

Normal cyclic prefix in uplink

Extended cyclic prefix in uplink

0

1

2

3

4

5

6

7

8

9

[TS 36.213, clause 6.10.3.2]

For antenna ports , or , in a physical resource block with frequency-domain index assigned for the corresponding PDSCH transmission, a part of the reference signal sequence shall be mapped to complex-valued modulation symbols in a subframe according to

Normal cyclic prefix:

where

The sequence is given by Table 6.10.3.2-1.

Table 6.10.3.2-1: The sequence for normal cyclic prefix

Antenna port

7

8

9

10

11

12

13

14

Extended cyclic prefix:

where

The sequence is given by Table 6.10.3.2-2.

Table 6.10.3.2-2: The sequence for extended cyclic prefix.

Antenna port

7

8

For extended cyclic prefix, UE-specific reference signals are not supported on antenna ports 9 to 14.

Resource elements used for transmission of UE-specific reference signals to one UE on any of the antenna ports in the set , where or shall

– not be used for transmission of PDSCH on any antenna port in the same slot, and

– not be used for UE-specific reference signals to the same UE on any antenna port other than those in in the same slot.

Figure 6.10.3.2-3 illustrates the resource elements used for UE-specific reference signals for normal cyclic prefix for antenna ports 7, 8, 9 and 10. Figure 6.10.3.2-4 illustrates the resource elements used for UE-specific reference signals for extended cyclic prefix for antenna ports 7, 8.

Figure 6.10.3.2-3: Mapping of UE-specific reference signals, antenna ports 7, 8, 9 and 10 (normal cyclic prefix)

[TS 36.213, clause 7.1]

For frame structure type 2,

– the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in any subframe in which the number of OFDM symbols for PDCCH with normal CP is equal to four;

– the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in the two PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a transmission of PBCH in the same subframe;

– the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 7, 8, 9, 10, 11, 12, 13 or 14 in the two PRBs to which a pair of VRBs is mapped if either one of the two PRBs overlaps in frequency with a transmission of primary or secondary synchronisation signals in the same subframe;

– with normal CP configuration, the UE is not expected to receive PDSCH on antenna port 5 for which distributed VRB resource allocation is assigned in the special subframe with configuration #1 or #6;

– the UE is not expected to receive PDSCH on antenna port 7 for which distributed VRB resource allocation is assigned;

– with normal cyclic prefix, the UE is not expected to receive PDSCH resource blocks transmitted on antenna port 5 in DwPTS when the UE is configured with special subframe configuration 9.

– The UE may skip decoding the transport block(s) if it does not receive all assigned PDSCH resource blocks. If the UE skips decoding, the physical layer indicates to higher layer that the transport block(s) are not successfully decoded.

If a UE is configured by higher layers to decode PDCCH with CRC scrambled by the C-RNTI, the UE shall decode the PDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5. The scrambling initialization of PDSCH corresponding to these PDCCHs is by C-RNTI.

If a UE is configured by higher layers to decode EPDCCH with CRC scrambled by the C-RNTI, the UE shall decode the EPDCCH and any corresponding PDSCH according to the respective combinations defined in Table 7.1-5A. The scrambling initialization of PDSCH corresponding to these EPDCCHs is by C-RNTI.

If the UE is configured with the carrier indicator field for a given serving cell and, if the UE is configured by higher layers to decode PDCCH/EPDCCH with CRC scrambled by the C-RNTI, then the UE shall decode PDSCH of the serving cell indicated by the carrier indicator field value in the decoded PDCCH/EPDCCH.

When a UE configured in transmission mode 3, 4, 8, 9 or 10 receives a DCI Format 1A assignment, it shall assume that the PDSCH transmission is associated with transport block 1 and that transport block 2 is disabled.

When a UE is configured in transmission mode 7, scrambling initialization of UE-specific reference signals corresponding to these PDCCHs/EPDCCHs is by C-RNTI.

The UE does not support transmission mode 8 if extended cyclic prefix is used in the downlink.

When a UE is configured in transmission mode 9 or 10, in the subframes indicated by the higher layer parameter mbsfn-SubframeConfigList except in subframes for the serving cell

– indicated by higher layers to decode PMCH or,

– configured by higher layers to be part of a positioning reference signal occasion and the positioning reference signal occasion is only configured within MBSFN subframes and the cyclic prefix length used in subframe #0 is normal cyclic prefix,

the UE shall upon detection of a PDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for the UE or, upon detection of an EPDCCH with CRC scrambled by the C-RNTI with DCI format 1A/2C/2D intended for the UE, decode the corresponding PDSCH in the same subframe.

A UE configured in transmission mode 10 can be configured with scrambling identities, , by higher layers for UE-specific reference signal generation as defined in Section 6.10.3.1 of [3] to decode PDSCH according to a detected PDCCH/EPDCCH with CRC scrambled by the C-RNTI with DCI format 2D intended for the UE.

Table 7.1-5: PDCCH and PDSCH configured by C-RNTI

Transmission mode

DCI format

Search Space

Transmission scheme of PDSCH corresponding to PDCCH

Mode 1

DCI format 1A

Common and

UE specific by C-RNTI

Single-antenna port, port 0 (see subclause 7.1.1)

DCI format 1

UE specific by C-RNTI

Single-antenna port, port 0 (see subclause 7.1.1)

Mode 2

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 1

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

Mode 3

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 2A

UE specific by C-RNTI

Large delay CDD (see subclause 7.1.3) or Transmit diversity (see subclause 7.1.2)

Mode 4

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 2

UE specific by C-RNTI

Closed-loop spatial multiplexing (see subclause 7.1.4)or Transmit diversity (see subclause 7.1.2)

Mode 5

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 1D

UE specific by C-RNTI

Multi-user MIMO (see subclause 7.1.5)

Mode 6

DCI format 1A

Common and

UE specific by C-RNTI

Transmit diversity (see subclause 7.1.2)

DCI format 1B

UE specific by C-RNTI

Closed-loop spatial multiplexing (see subclause 7.1.4) using a single transmission layer

Mode 7

DCI format 1A

Common and

UE specific by C-RNTI

If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

DCI format 1

UE specific by C-RNTI

Single-antenna port, port 5 (see subclause 7.1.1)

Mode 8

DCI format 1A

Common and

UE specific by C-RNTI

If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

DCI format 2B

UE specific by C-RNTI

Dual layer transmission, port 7 and 8 (see subclause 7.1.5A) or single-antenna port, port 7 or 8 (see subclause 7.1.1)

Mode 9

DCI format 1A

Common and

UE specific by C-RNTI

Non-MBSFN subframe: If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

MBSFN subframe: Single-antenna port, port 7 (see subclause 7.1.1)

DCI format 2C

UE specific by C-RNTI

Up to 8 layer transmission, ports 7-14 (see subclause 7.1.5B) or single-antenna port, port 7 or 8 (see subclause 7.1.1)

Mode 10

DCI format 1A

Common and

UE specific by C-RNTI

Non-MBSFN subframe: If the number of PBCH antenna ports is one, Single-antenna port, port 0 is used (see subclause 7.1.1), otherwise Transmit diversity (see subclause 7.1.2)

MBSFN subframe: Single-antenna port, port 7 (see subclause 7.1.1)

DCI format 2D

UE specific by C-RNTI

Up to 8 layer transmission, ports 7-14 (see subclause 7.1.5B) or single-antenna port, port 7 or 8 (see subclause 7.1.1)

[TS 36.306, clause 4.3.4.21]

This field defines whether the UE supports TDD special subframe as specified in [TS 36.211]. It is mandatory for UEs of this release of the specification.

[TS 36.331, clause 6.3.2]

The IE TDD-Config is used to specify the TDD specific physical channel configuration.

TDD-Config information element

— ASN1START

TDD-Config ::= SEQUENCE {

subframeAssignment ENUMERATED {

sa0, sa1, sa2, sa3, sa4, sa5, sa6},

specialSubframePatterns ENUMERATED {

ssp0, ssp1, ssp2, ssp3, ssp4,ssp5, ssp6, ssp7,

ssp8}

}

TDD-Config-v1130 ::= SEQUENCE {

specialSubframePatterns-v1130 ENUMERATED {ssp7,ssp9}

}

— ASN1STOP

TDD-Config field descriptions

specialSubframePatterns

Indicates Configuration as in TS 36.211 [21, table 4.2-1] where ssp0 points to Configuration 0, ssp1 to Configuration 1 etc. Value ssp7 points to Configuration 7 for extended cyclic prefix and value ssp9 points to Configuration 9 for normal cyclic prefix. E-UTRAN signals ssp7 only when setting specialSubframePatterns (without suffix i.e. the version defined in REL-8) to ssp4. E-UTRAN signals value ssp9 only when setting specialSubframePatterns (without suffix) to ssp5. If specialSubframePatterns-v1130 is present, the UE shall ignore specialSubframePatterns (without suffix).

subframeAssignment

Indicates DL/UL subframe configuration where sa0 point to Configuration 0, sa1 to Configuration 1 etc. as specified in TS 36.211 [21, table 4.2-2]. E-UTRAN configures the same value for serving cells residing on same frequency band.

7.1.3.13a.3 Test description

7.1.3.13a.3.1 Pre-test conditions

System Simulator:

  • Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18] using parameters as specified in section 7.1.3.13a.3.3.

7.1.3.13a.3.2 Test procedure sequence

Table 7.1.3.13a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS indicates a new transmission on PDCCH by using DCI format 1 and transmits a MAC PDU in SF-Num 1 or 6 where the DwPTS belongs to.

<–

MAC PDU

2

Check: Does the UE transmit a HARQ ACK?

–>

HARQ ACK

1

P

3

The UE transmits a Scheduling Request on PUCCH

–>

(SR)

4

The SS sends an UL grant suitable for the loop back PDU to be transmitted

<–

(UL Grant)

5

The UE transmits a MAC PDU containing the loop back PDU corresponding to step 1

–>

MAC PDU

7.1.3.13a.3.3 Specific message contents

Table 7.1.3.13a.3.3-1: SystemInformationBlockType1 for Cell 1 (preamble, Table 7.1.3.13a.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp7

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.13a.3.3-1A: SystemInformationBlockType1-BR-r13 for Cell 1 (preamble when UE under test is CAT M1, Table 7.1.3.13a.3.2-1)

Derivation Path: 36.508 clause 4.4.3.2, Table 4.4.3.2-3A

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1-BR-r13 ::= SEQUENCE {

tdd-Config SEQUENCE {

TDD

subframeAssignment

sa1

specialSubframePatterns

ssp4

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

tdd-Config-v1130 SEQUENCE {

specialSubframePatterns-v1130

ssp7

}

nonCriticalExtension

Not present

}

}

}

}

Table 7.1.3.13a.3.3-2: SystemInformationBlockType2 for Cell 1 (preamble, table 7.1.3.13a.3.2-1)

Derivation path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

ul-CyclicPrefixLength

len2

}

}

Table 7.1.3.13a.3.3-3: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

Table 7.1.3.13a.3.3-4: PhysicalConfigDedicated-DEFAULT (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

antennaInfo CHOICE {

explicitValue SEQUENCE {

1TX

transmissionMode

tm7

ue-TransmitAntennaSelection CHOICE {

Release

NULL

}

}

}

}

7.1.3.14 Correct handling of DL assignment / Dynamic case / EPDCCH

7.1.3.14.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with EPDCCH in localized transmission type }

ensure that {

when { UE receives downlink assignment on the EPDCCH for the UE’s C-RNTI and receives data in the associated subframe and UE performs HARQ operation }

then { UE sends a HARQ feedback on the HARQ process }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and EPDCCH in localized transmission type }

ensure that {

when { UE receives downlink assignment on the EPDCCH with a C-RNTI unknown by the UE and data is available in the associated subframe }

then { UE does not send any HARQ feedback on the HARQ process }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives downlink assignment on the EPDCCH for the UE’s C-RNTI and receives data in the associated subframe and UE performs HARQ operation }

then { UE sends a HARQ feedback on the HARQ process }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives downlink assignment on the EPDCCH with a C-RNTI unknown by the UE and data is available in the associated subframe }

then { UE does not send any HARQ feedback on the HARQ process }

}

7.1.3.14.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 3.1 and 5.3.1. Unless otherwise stated these are Rel-11 requirements.

[36.321, clause 3.1]

PDCCH: Refers to the PDCCH [7], EPDCCH (in subframes when configured) or, for an RN with R-PDCCH configured and not suspended, to the R-PDCCH.

[TS 36.321, clause 5.3.1]

Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a particular UE and provide the relevant HARQ information.

When the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI during which it monitors PDCCH:

– if a downlink assignment for this TTI has been received on the PDCCH for the UE’s C-RNTI, or Temporary C‑RNTI:

– if this is the first downlink assignment for this Temporary C-RNTI:

– consider the NDI to have been toggled.

– if the downlink assignment is for UE’s C-RNTI and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was either a downlink assignment received for the UE’s Semi-Persistent Scheduling C-RNTI or a configured downlink assignment:

– consider the NDI to have been toggled regardless of the value of the NDI.

– indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI.

7.1.3.14.3 Test description

7.1.3.14.3.1 Pre-test conditions

System Simulator:

  • Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.3.1.3.3-1

UE:

None.

Preamble:

– The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no data in uplink.

7.1.3.14.3.2 Test procedure sequence

Table 7.1.3.14.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS transmits a downlink assignment including the C-RNTI assigned to the UE

<–

(EPDCCH (C-RNTI))

2

SS transmits in the indicated downlink assignment a RLC PDU in a MAC PDU.

<–

MAC PDU

3

Check: Does the UE transmit an HARQ ACK on PUCCH?

–>

HARQ ACK

1

P

4

SS transmits a downlink assignment to including a C-RNTI different from the assigned to the UE

<–

(EPDCCH (unknown C-RNTI))

5

SS transmits in the indicated downlink assignment a RLC PDU in a MAC PDU.

<–

MAC PDU

6

Check: Does the UE send any HARQ ACK/ NACK on PUCCH?

–>

HARQ ACK/ NACK

2

F

7

SS sends RRCConnectionReconfiguration to configure EPDCCH in distributed transmission mode

8

SS transmits a downlink assignment including the C-RNTI assigned to the UE

<–

(EPDCCH (C-RNTI))

9

SS transmits in the indicated downlink assignment a RLC PDU in a MAC PDU.

<–

MAC PDU

10

Check: Does the UE transmit an HARQ ACK on PUCCH?

–>

HARQ ACK

3

P

11

SS transmits a downlink assignment to including a C-RNTI different from the assigned to the UE

<–

(EPDCCH (unknown C-RNTI))

12

SS transmits in the indicated downlink assignment a RLC PDU in a MAC PDU.

<–

MAC PDU

13

Check: Does the UE send any HARQ ACK/ NACK on PUCCH?

–>

HARQ ACK/ NACK

4

F

NOTE 1: For TDD, the timing of ACK/NACK is not constant as FDD, see Table 10.1-1 of TS 36.213.

7.1.3.14.3.3 Specific Message Contents

Table 7.1.3.14.3.3-1: MAC-MainConfig-RBC (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

MAC-MainConfig-RBC ::= SEQUENCE {

timeAlignmentTimerDedicated

Infinity

}

Table 7.1.3.14.3.3-2: PhysicalConfigDedicated (Preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 clause 4.8.2.1.6, Table 4.8.2.1.6-1 with condition ePDCCH

Table 7.1.3.14.3.3-3: EPDCCH-Config-r11 (Preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 clause 4.6.3, Table 4.6.3-2B

Information Element

Value/remark

Comment

Condition

EPDCCH-Config-r11 ::= SEQUENCE{

startSymbol-r11

3

setConfigToAddModList-r11 SEQUENCE (SIZE(1..maxEPDCCH-Set-r11)) OF SEQUENCE {

1 entry

setConfigId-r11[1]

0

transmissionType-r11[1]

localised

resourceBlockAssignment-r11[1] SEQUENCE{

numberPRB-Pairs-r11

n8

resourceBlockAssignment-r11

11100100101110110011001101100

}

dmrs-ScramblingSequenceInt-r11[1]

0

pucch-ResourceStartOffset-r11[1]

0

re-MappingQCL-ConfigListId-r11[1]

Not present

}

}

}

}

Table 7.1.3.14.3.3-4: Void

7.1.3.15 Correct handling of DL assignment / Semi-persistent case / EPDCCH

7.1.3.15.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state with DRB established and SPS Configuration in DL is enabled and EPDCCH in localized transmission mode }

ensure that {

when { UE receives a DL assignment addressed to its stored SPS-CRNTI in SF-Num y and with NDI set as 0 }

then { UE starts receiving DL MAC PDU in SF-Nums y+n*[semiPersistSchedIntervalDL] where ‘n’ is positive integer starting at zero }

}

(2)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }

ensure that {

when { UE receives a DL assignment addressed to its SPS-CRNTI in SF-Num p and with NDI set as 0, where p!= y+n*[semiPersistSchedIntervalDL] }

then { UE starts receiving DL MAC PDU in SF-Nums p+n*[semiPersistSchedIntervalDL] and stops receiving DL MAC PDU at SF-Nums y+n*[semiPersistSchedIntervalDL]where ‘n’ is positive integer starting at zero }

}

(3)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num p+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }

ensure that {

when { UE receives a DL assignment [for retransmission] addressed to its SPS-CRNTI in SF-Num z and with NDI set as 1, where z!= p+n*[semiPersistSchedIntervalDL] }

then { UE receives MAC PDU in SF-Num z as per the new grant for SPS-CRNTI }

}

(4)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }

ensure that {

when { UE receives a DL assignment addressed to its CRNTI in SF-Num p, such that p!= y+n*[semiPersistSchedIntervalDL] }

then { UE receives MAC PDU in SF-Num p as per assignment addressed to its C-RNTI }

}

(5)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS grant to receive MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }

ensure that {

when { UE receives a RRCConnectionReconfiguration including SPS Configuration with sps-ConfigDL set as ‘disable’ and hence resulting in DL SPS grant deactivation }

then { UE deletes the stored SPS Configuration DL parameters and stops receiving DL MAC PDU’s as per stored SPS assignment in SF-Num z+n*[semiPersistSchedIntervalDL] }

}

(6)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] and EPDCCH in localized transmission mode }

ensure that {

when { UE receives a EPDCCH [for DL SPS explicit release according to Table 9.2-1A in TS 36.213] addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p!= z+n*[semiPersistSchedIntervalDL] }

then { UE sends an ACK to SS and releases the configured SPS assignment and stops receiving MAC PDU in SF-Num z+n*[semiPersistSchedIntervalDL] as per assignment addressed to its SPS C-RNTI }

}

(7)

with { UE in E-UTRA RRC_Connected state with DRB established and SPS Configuration in DL is enabled }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives a DL assignment addressed to its stored SPS-CRNTI in SF-Num y and with NDI set as 0 }

then { UE starts receiving DL MAC PDU in SF-Nums y+n*[semiPersistSchedIntervalDL] where ‘n’ is positive integer starting at zero }

}

(8)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives a DL assignment addressed to its SPS-CRNTI in SF-Num p and with NDI set as 0, where p!= y+n*[semiPersistSchedIntervalDL] }

then { UE starts receiving DL MAC PDU in SF-Nums p+n*[semiPersistSchedIntervalDL] and stops receiving DL MAC PDU at SF-Nums y+n*[semiPersistSchedIntervalDL]where ‘n’ is positive integer starting at zero }

}

(9)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num p+n*[semiPersistSchedIntervalDL] }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives a DL assignment [for retransmission] addressed to its SPS-CRNTI in SF-Num z and with NDI set as 1, where z!= p+n*[semiPersistSchedIntervalDL] }

then { UE receives MAC PDU in SF-Num z as per the new grant for SPS-CRNTI }

}

(10)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num y+n*[semiPersistSchedIntervalDL] }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives a DL assignment addressed to its CRNTI in SF-Num p, such that p!= y+n*[semiPersistSchedIntervalDL] }

then { UE receives MAC PDU in SF-Num p as per assignment addressed to its C-RNTI }

}

(11)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS grant to receive MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives a RRCConnectionReconfiguration including SPS Configuration with sps-ConfigDL set as ‘disable’ and hence resulting in DL SPS grant deactivation }

then { UE deletes the stored SPS Configuration DL parameters and stops receiving DL MAC PDU’s as per stored SPS assignment in SF-Num z+n*[semiPersistSchedIntervalDL] }

}

(12)

with { UE in E-UTRA RRC_Connected state with DRB established and stored DL SPS assignment to receive MAC PDU at SF-Num z+n*[semiPersistSchedIntervalDL] }

ensure that {

when { EPDCCH is configured with distributed transmission type and UE receives a ePDCCH [for DL SPS explicit release according to Table 9.2-1A in TS 36.213] addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p!= z+n*[semiPersistSchedIntervalDL] }

then { UE sends an ACK to SS and releases the configured SPS assignment and stops receiving MAC PDU in SF-Num z+n*[semiPersistSchedIntervalDL] as per assignment addressed to its SPS C-RNTI }

}

NOTE: SF-Num = [10*SFN + subframe] modulo 10240.

7.1.3.15.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.3.1, 5.10 & 5.10.1, 36.331 clause 5.3.10.5, 36.300 clause 11.1.1 and 36.213 clause 9.2. Unless otherwise stated these are Rel-11 requirements.

[TS 36.321, clause 5.3.1]

Downlink assignments transmitted on the PDCCH indicate if there is a transmission on the DL-SCH for a particular UE and provide the relevant HARQ information.

When the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI during which it monitors PDCCH:

– if a downlink assignment for this TTI has been received on the PDCCH for the UE’s C-RNTI, or Temporary C‑RNTI:

– if this is the first downlink assignment for this Temporary C-RNTI:

– consider the NDI to have been toggled.

– if the downlink assignment is for UE’s C-RNTI and if the previous downlink assignment indicated to the HARQ entity of the same HARQ process was either a downlink assignment received for the UE’s Semi-Persistent Scheduling C-RNTI or a configured downlink assignment:

– consider the NDI to have been toggled regardless of the value of the NDI.

– indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI.

– else, if a downlink assignment for this TTI has been received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI:

– if the NDI in the received HARQ information is 1:

– consider the NDI not to have been toggled;

– indicate the presence of a downlink assignment and deliver the associated HARQ information to the HARQ entity for this TTI.

– else, if the NDI in the received HARQ information is 0:

– if PDCCH contents indicate SPS release:

– clear the configured downlink assignment (if any);

– if timeAlignmentTimer is running:

– instruct the physical layer to transmit a positive acknowledgement.

– else:

– store the downlink assignment and the associated HARQ information as configured downlink assignment;

– initialise (if not active) or re-initialise (if already active) the configured downlink assignment to start in this TTI and to recur according to rules in subclause 5.10.1;

– set the HARQ Process ID to the HARQ Process ID associated with this TTI;

– consider the NDI bit to have been toggled;

– indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity for this TTI.

– else, if a downlink assignment for this TTI has been configured and there is no measurement gap in this TTI:

– instruct the physical layer to receive, in this TTI, transport block on the DL-SCH according to the configured downlink assignment and to deliver it to the HARQ entity;

– set the HARQ Process ID to the HARQ Process ID associated with this TTI;

– consider the NDI bit to have been toggled;

– indicate the presence of a configured downlink assignment and deliver the stored HARQ information to the HARQ entity for this TTI.

For downlink assignments received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI and for configured downlink assignments, the HARQ Process ID associated with this TTI is derived from the following equation:

HARQ Process ID = [floor(CURRENT_TTI/(Downlink Semi-Persistent Scheduling Interval))] modulo Number of Configured SPS Processes,

where CURRENT_TTI=[(SFN * 10) + subframe number], Downlink Semi-Persistent Scheduling Interval is the periodicity of semi-persistent scheduling signalled via RRC and Number of Configured SPS Processes is the number of HARQ processes allocated for semi-persistent scheduling signalled via RRC.

[TS 36.321, clause 5.10]

When Semi-Persistent Scheduling is enabled by upper layer, the following information is provided:

– Semi-Persistent Scheduling C-RNTI;

– Uplink Semi-Persistent Scheduling Interval semiPersistSchedIntervalUL and number of empty transmissions before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the uplink;

– Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;

– Downlink Semi-Persistent Scheduling Interval semiPersistSchedIntervalDL and number of configured HARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is enabled for the downlink;

When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or configured assignment shall be discarded.

[TS 36.321, clause 5.10.1]

After a Semi-Persistent downlink assignment is configured, the UE shall consider that the assignment recurs in each subframe for which:

– (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * (Downlink Semi-Persistent Scheduling Interval)] modulo 10240, for all N>0.

Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the configured downlink assignment were (re-)initialised.

[TS 36.331, clause 5.3.10.5]

The UE shall:

1> reconfigure the semi-persistent scheduling in accordance with the received sps-Config:

[TS 36.300, clause 11.1.1]

In addition, E-UTRAN can allocate semi-persistent downlink resources for the first HARQ transmissions to UEs:

– RRC defines the periodicity of the semi-persistent downlink grant;

– PDCCH indicates whether the downlink grant is a semi-persistent one i.e. whether it can be implicitly reused in the following TTIs according to the periodicity defined by RRC.

When required, retransmissions are explicitly signalled via the PDCCH(s). In the sub-frames where the UE has semi-persistent downlink resource, if the UE cannot find its C-R