21.2 DRX operation

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

21.2.1 DRX operation / Parameters configured by RRC

21.2.1.1 Test Purpose (TP)

(1)

with { UE in CONNECTED mode }

ensure that {

when { SC-MTCH-SchedulingCycle is configured and [(SFN * 10) + subframe number] modulo (SC-MTCH-SchedulingCycle) = SC-MTCH-SchedulingOffset }

then { UE starts the OnDurationTimerSCPTM and monitors the PDCCH for OnDurationTimerSCPTM PDCCH-subframes }

}

(2)

with { UE in CONNECTED mode }

ensure that {

when { SC-MTCH-SchedulingCycle is configured and a new DL transmission is indicated on the PDCCH during Active Time }

then { UE starts or restarts the Drx-InactivityTimerSCPTM and monitors the PDCCH for Drx-InactivityTimerSCPTM PDCCH sub-frames starting from the next PDCCH sub-frame of the PDCCH sub-frame where the DL new transmission was indicated }

}

21.2.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7a.

[TS 36.321, clause 3.1]

Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH in PDCCH-subframes.

DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).

Figure 3.1-1: DRX Cycle

drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.

drxStartOffset: Specifies the subframe where the DRX Cycle starts.

onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.

PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and subframes including DwPTS.

[TS 36.321, clause 5.7a]

Each G-RNTI of the MAC entity may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring activity for this G-RNTI as specified in [8]. When in RRC_IDLE or RRC_CONNECTED, if DRX is configured, the MAC entity is allowed to monitor the PDCCH for this G-RNTI discontinuously using the DRX operation specified in this subclause; otherwise the MAC entity monitors the PDCCH for this G-RNTI continuously. For each G-RNTI of the MAC entity, RRC controls its DRX operation by configuring the timers onDurationTimerSCPTM, drx-InactivityTimerSCPTM, the SC-MTCH-SchedulingCycle and the value of the SC-MTCH-SchedulingOffset. The DRX operation specified in this subclause is performed independently for each G-RNTI and independently from the DRX operation specified in subclause 5.7.

When DRX is configured for a G-RNTI, the Active Time includes the time while:

– onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.

When DRX is configured for a G-RNTI as specified in [8], the MAC entity shall for each subframe for this G-RNTI:

– if [(SFN * 10) + subframe number] modulo (SC-MTCH-SchedulingCycle) = SC-MTCH-SchedulingOffset:

– start onDurationTimerSCPTM.

– during the Active Time, for a PDCCH-subframe:

– monitor the PDCCH;

– if the PDCCH indicates a DL transmission:

– start or restart drx-InactivityTimerSCPTM.

21.2.1.3 Test description

21.2.1.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– System information combination 25 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cell 1.

– SCPTMConfiguration as defined in TS 36.508[18] table 4.6.1-18a is transmitted on SC-MCCH in Cell 1.

UE:

– E-UTRAN UE supporting SC-PTM services.

Preamble:

– UE is in Registered, Idle mode, Test Mode Activated (State 2A) according to [18] in Cell 1(serving cell) with the UE TEST LOOP MODE F.

– The UE is made interested in receiving SC-PTM service in the PLMN of Cell 1 with MBMS Service ID 1.

21.2.1.3.2 Test procedure sequence

For FDD, NormalSF(current SFN,current subframe number,y)=y; For TDD, NormalSF(current SFN,current subframe number,y) counts the minimum number of normal subframes needed to cover y number of PDCCH-subframes until next PDCCH-subframe available, starting from current subframe number on current SFN. For example at step 1, drxStartOffset can point to UL or DL subframe for TDD. If it points to a UL subframe, NormalSF(current SFN,current subframe number,0) counts the number of normal subframes until reach the first DL/special subframe available. If drxStartOffset points to a DL subframe, NormalSF(current SFN,current subframe number,0)=0.

For example at step 12, assuming SC-MTCH-SchedulingOffset points to subframe number 0 at frame number A, NormalSF(A, 0, onDurationTimer+drx-InactivityTimer-1) is added, which counts 18 PDCCH-subframes/30 normal subframes in this case. The current subframe becomes subframe number 0 at frame number A+3.

Table 21.2.1.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS transmits updated SCPTMConfiguration to configure specific DRX parameters, from the beginning of next modification period MPa.

<–

SCPTMConfiguration

2

Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration message

3

The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 1 to close UE test loop.

4

In the first PDCCH subframe when the OnDurationTimer is running, the SS indicates the transmission of a DL MAC PDU on the PDCCH using G-RNTI.

i.e., on the subframe with the subframe number = [csfn1 + NormalSF(SFN1, csfn1, 0)] modulo 10, and system frame number = SFN1 + floor([csfn1 + NormalSF(SFN1, csfn1, 0)]/10); where [(SFN1 * 10) + csfn1] modulo (SC-MTCH-SchedulingCycle) = SC-MTCH-SchedulingOffset

<–

MAC PDU

5

The SS transmits a UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

6

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

7

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 6 greater than zero?

1

P

8

At least drx-InactivityTimer PDCCH-sub frames after the transmission of the MBMS packet in Step 3 has been indicated(This means the next DRX cycle or later after Step 3) in the last PDCCH subframe while the onDurationTimer is still running, the SS indicates the transmission of a DL MAC PDU on the PDCCH using G-RNTI. (Note 3).

i.e., on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)]/10); where [(SFN2 * 10) + csfn2] modulo (SC-MTCH-SchedulingCycle) = SC-MTCH-SchedulingOffset

<–

MAC PDU

9

The SS transmits a UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

10

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

11

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 10 greater than the value reported in step 6?

1

P

12

drx-InactivityTimer PDCCH-subframes after the transmission of the SC-MTCH transmitted in step 8 was indicated on the PDCCH, the SS indicates the transmission of a DL MAC PDU on the PDCCH using G-RNTI. (Note 3)

i.e. on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimer + drx-InactivityTimer-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimer+ drx-InactivityTimer-1)]/10)

<–

MAC PDU

13

The SS transmits a UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

14

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

15

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 14 greater than the value reported in step 10?

2

P

Note 1: All the DL MAC PDU are transmitted with the NDI set on the PDCCH.

Note 2: Timer tolerances for the MAC DRX related drx-InactivityTimer measured in subframes or PDCCH subframes is 0.

Note 3: The drx-InactivityTimer is started in the next PDCCH sub-frame of the PDCCH sub-frame where DL new transmission is indicated.

21.2.1.3.3 Specific message contents

Table 21.2.1.3.3-1: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE F.

Table 21.2.1.3.3-2: SCPTMConfiguration for Cell 1 (step 1, Table 21.2.1.3.2-1)

Derivation Path: 36.508 table 4.6.1-18a

Information Element

Value/remark

Comment

Condition

SCPTMConfiguration-r13 ::= SEQUENCE {

sc-mtch-InfoList-r13 SEQUENCE (SIZE (0..maxSC-MTCH-r13)) OF SEQUENCE {

sc-mtch-schedulingInfo-r13 SEQUENCE {

on-DurationTimerSCPTM-r13

psf50

drx-InactivityTimerSCPTM-r13

psf10

schedulingPeriodStartOffsetSCPTM-r13 CHOICE{

sf160

10

}

}

}

}

Table 21.2.1.3.3-3: CLOSE UE TEST LOOP (step 4, Table 21.2.1.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE F

21.2.2 DRX operation / Parameters configured by RRC / Enhanced Coverage

21.2.2.1 Test Purpose (TP)

(1)

with { UE in CONNECTED mode }

ensure that {

when { SCPTM-SchedulingCycle is configured and [(H-SFN * 10240 + SFN * 10) + subframe number] modulo (SCPTM-SchedulingCycle) = SCPTM-SchedulingOffset }

then { UE starts the onDurationTimerSCPTM and monitors the PDCCH for onDurationTimerSCPTM PDCCH-subframes }

}

(2)

with { UE in CONNECTED mode }

ensure that {

when { SCPTM-SchedulingCycle is configured and a new DL transmission is indicated on the PDCCH during Active Time }

then { UE starts or restarts the drx-InactivityTimerSCPTM and monitors the PDCCH for drx-InactivityTimerSCPTM PDCCH sub-frames starting from the next PDCCH sub-frame of the PDCCH sub-frame where the DL new transmission was indicated }

}

21.2.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7a.

[TS 36.321, clause 3.1]

Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH in PDCCH-subframes.

DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).

Figure 3.1-1: DRX Cycle

drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.

drxStartOffset: Specifies the subframe where the DRX Cycle starts.

onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.

PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and subframes including DwPTS.

[TS 36.321, clause 5.7a]

Each G-RNTI and, for NB-IoT UEs, BL UEs or UEs in enhanced coverage, each SC-RNTI of the MAC entity may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring activity for this G-RNTI and SC-RNTI as specified in [8]. When in RRC_IDLE or RRC_CONNECTED, if DRX is configured, the MAC entity is allowed to monitor the PDCCH for this G-RNTI or SC-RNTI discontinuously using the DRX operation specified in this subclause; otherwise the MAC entity monitors the PDCCH for this G-RNTI or SC-RNTI continuously. For each G-RNTI or SC-RNTI of the MAC entity, RRC controls its DRX operation by configuring the timers onDurationTimerSCPTM, drx-InactivityTimerSCPTM, the SCPTM-SchedulingCycle and the value of the SCPTM-SchedulingOffset for G-RNTI and for SC-RNTI. The DRX operation specified in this subclause is performed independently for each G-RNTI and SC-RNTI and independently from the DRX operation specified in subclause 5.7.

When DRX is configured for a G-RNTI or for SC-RNTI, the Active Time includes the time while:

– onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.

When DRX is configured for a G-RNTI or for SC-RNTI as specified in [8], the MAC entity shall for each subframe for this G-RNTI:

– if [(H-SFN * 10240 + SFN * 10) + subframe number] modulo (SCPTM-SchedulingCycle) = SCPTM-SchedulingOffset:

– start onDurationTimerSCPTM.

– during the Active Time, for a PDCCH-subframe:

– monitor the PDCCH;

– if the PDCCH indicates a DL transmission:

– if the UE is a BL UE or a UE in enhanced coverage:

– start or re-start the drx-InactivityTimerSCPTM in the subframe containing the last repetition of the corresponding PDSCH reception.

– if the UE is an NB-IoT UE:

– stop onDurationTimerSCPTM;

– stop drx-InactivityTimerSCPTM;

– start the drx-InactivityTimerSCPTM in the first subframe of the next PDCCH occasion following the subframe containing the last repetition of the corresponding PDSCH reception.

– else:

– start or restart drx-InactivityTimerSCPTM.

NOTE: If H-SFN is not configured its value is set to 0 in the calculation of the starting subframe.

21.2.2.3 Test description

21.2.2.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– System information combination 25 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cell 1.

– SCPTMConfiguration-BR as defined in TS 36.508[18] table 4.6.1-18b is transmitted on SC-MCCH in Cell 1.

UE:

– E-UTRAN UE supporting Enhanced Coverage and SC-PTM services.

Preamble:

– UE is in Registered, Idle mode, Test Mode Activated (State 2A) according to [18] in Cell 1(serving cell) with the UE TEST LOOP MODE F.

– The UE is made interested in receiving SC-PTM service in the PLMN of Cell 1 with MBMS Service ID 1.

21.2.2.3.2 Test procedure sequence

For FDD, NormalSF(current SFN,current subframe number,y)=y; For TDD, NormalSF(current SFN,current subframe number,y) counts the minimum number of normal subframes needed to cover y number of PDCCH-subframes until next PDCCH-subframe available, starting from current subframe number on current SFN. For example at step 1, SCPTM-SchedulingOffset can point to UL or DL subframe for TDD. If it points to a UL subframe, NormalSF(current SFN,current subframe number,0) counts the number of normal subframes until reach the first DL/special subframe available. If SCPTM-SchedulingOffset points to a DL subframe, NormalSF(current SFN,current subframe number,0)=0.

For example at step 12, assuming SCPTM-SchedulingOffset points to subframe number 0 at frame number A, NormalSF(A, 0, onDurationTimerSCPTM +drx-InactivityTimerSCPTM -1) is added, which counts 18 PDCCH-subframes/30 normal subframes in this case. The current subframe becomes subframe number 0 at frame number A+3.

Table 21.2.2.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS transmits updated SCPTMConfiguration-BR to configure specific DRX parameters, from the beginning of next modification period MPa.

<–

SCPTMConfiguration-BR

2

Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration message

3

The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 1 to close UE test loop F

4

In the first PDCCH subframe when the onDurationTimerSCPTM is running, the SS indicates the transmission of a DL MAC PDU on the PDCCH using SC-RNTI.

i.e., on the subframe with the subframe number = [csfn1 + NormalSF(SFN1, csfn1, 0)] modulo 10, and system frame number = SFN1 + floor([csfn1 + NormalSF(SFN1, csfn1, 0)]/10); where [(H-SFN * 10240 + SFN1 * 10) + csfn1] modulo (SCPTM-SchedulingCycle) = SCPTM-SchedulingOffset

<–

MAC PDU

5

The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

6

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

7

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 6 greater than zero?

1

P

8

At least drx-InactivityTimerSCPTM PDCCH-sub frames after the transmission of the MBMS packet in Step 3 has been indicated(This means the next DRX cycle or later after Step 3) in the last PDCCH subframe while the onDurationTimerSCPTM is still running, the SS indicates the transmission of a DL MAC PDU on the PDCCH using SC-RNTI. (Note 3).

i.e., on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimerSCPTM-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimerSCPTM-1)]/10); where [(H-SFN * 10240 + SFN2 * 10) + csfn2] modulo (SCPTM-SchedulingCycle) = SCPTM-SchedulingOffset

<–

MAC PDU

9

The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

10

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

11

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 10 greater than the value reported in step 6?

1

P

12

drx-InactivityTimerSCPTM PDCCH-subframes after the transmission of the SC-MTCH transmitted in step 8 was indicated on the PDCCH, the SS indicates the transmission of a DL MAC PDU on the PDCCH using SC-RNTI. (Note 3)

i.e. on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimerSCPTM + drx-InactivityTimerSCPTM-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimerSCPTM+ drx-InactivityTimerSCPTM-1)]/10)

<–

MAC PDU

13

The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

14

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

15

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 14 greater than the value reported in step 10?

2

P

Note 1: All the DL MAC PDU are transmitted with the NDI set on the PDCCH.

Note 2: Timer tolerances for the MAC DRX related drx-InactivityTimerSCPTM measured in subframes or PDCCH subframes is 0.

Note 3: The drx-InactivityTimerSCPTM is started in the subframe containing the last repetition of the corresponding PDSCH reception.

21.2.2.3.3 Specific message contents

Table 21.2.2.3.3-1: SystemInformationBlockType20 for Cell 1 (all steps, Table 21.2.2.3.2-1)

Derivation Path: 36.508 table 4.4.3.3-18

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType20-r13 ::= SEQUENCE {

br-BCCH-Config-r14 SEQUENCE {

dummy

rf1

dummy2

rf1

mpdcch-Narrowband-SC-MCCH-r14

1

mpdcch-NumRepetition-SC-MCCH-r14

r1

mpdcch-StartSF-SC-MCCH-r14 CHOICE {

fdd-r14

v1

FDD

tdd-r14

v1

TDD

}

mpdcch-PDSCH-HoppingConfig-SC-MCCH-r14

off

sc-mcch-CarrierFreq-r14

FFS

sc-mcch-Offset-BR-r14

0

sc-mcch-RepetitionPeriod-BR-r14

rf32

sc-mcch-ModificationPeriod-BR-r14

Rf512

}

sc-mcch-SchedulingInfo-r14

Not present

pdsch-maxNumRepetitionCEmodeA-SC-MTCH-r14

Not present

r32

CE-ModeA

pdsch-maxNumRepetitionCEmodeB-SC-MTCH-r14

Not present

r512

CE-ModeB

sc-mcch-RepetitionPeriod-v1470

Not present

sc-mcch-ModificationPeriod-v1470

Not present

}

Table 21.2.2.3.3-2: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE F.

Table 21.2.2.3.3-3: SCPTMConfiguration-BR for Cell 1 (step 1, Table 21.2.2.3.2-1)

Derivation Path: 36.508 table 4.6.1-18b

Information Element

Value/remark

Comment

Condition

SCPTMConfiguration-BR-r14 ::= SEQUENCE {

sc-mtch-InfoList-r14 SEQUENCE (SIZE (0..maxSC-MTCH-BR-r14)) OF SEQUENCE {

sc-mtch-schedulingInfo-r14SEQUENCE {

onDurationTimerSCPTM-r14

psf300

drx-InactivityTimerSCPTM-r14

psf8

schedulingPeriodStartOffsetSCPTM-r14 CHOICE {

sf160

10

}

}

}

}

Table 21.2.2.3.3-4: CLOSE UE TEST LOOP (step 4, Table 21.2.2.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE F