21.3.13 SC-PTM Stop Indication / Enhanced Coverage

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.3.13.1 Test Purpose (TP)

(1)

with { Enhanced Coverage Capable UE receiving SC-PTM service }

ensure that {

when { SC-PTM Stop Indication MAC control element associated with a G-RNTI is received }

then { UE stops monitoring the PDCCH for this G-RNTI }

}

21.3.13.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 5.21, 6.1.3.12 and 6.2.1

[TS 36.321, clause 5.21]

For NB-IoT UEs, BL UEs or UEs in enhanced coverage, the eNB may transmit the SC-PTM Stop Indication MAC control element to the MAC entity to indicate that the transmission of SC-MTCH associated with a G-RNTI is stopped as described in subclause 6.1.3.12.

Upon reception of the SC-PTM Stop Indication MAC control element associated with a G-RNTI, the MAC entity shall:

– stop monitoring the PDCCH for this G-RNTI;

– indicate to upper layers that the associated MBMS session is stopped.

[TS 36.321, clause 6.1.3.12]

The SC-PTM Stop Indication MAC control element is applicable to NB-IoT UEs and BL UEs or UEs in enhanced coverage and indicates that the SC-MTCH transmission for a specific G-RNTI is stopped. It is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1.

It has a fixed size of zero bits.

[TS 36.321, clause 6.2.1]

The MAC header and subheaders are octet aligned.

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

Codepoint/Index

LCID values

00000

CCCH

00001-01010

Identity of the logical channel

01011-01111

Reserved

10000

Extended logical channel ID field

10001

Reserved

10010

Activation/Deactivation of PDCP Duplication

10011

Hibernation (1 octet)

10100

Hibernation (4 octets)

10101

Activation/Deactivation of CSI-RS

10110

Recommended bit rate

10111

SC-PTM Stop Indication

11000

Activation/Deactivation (4 octets)

11001

SC-MCCH, SC-MTCH (see note)

11010

Long DRX Command

11011

Activation/Deactivation (1 octet)

11100

UE Contention Resolution Identity

11101

Timing Advance Command

11110

DRX Command

11111

Padding

NOTE: Both SC-MCCH and SC-MTCH cannot be multiplexed with other logical channels in the same MAC PDU except for Padding and SC-PTM Stop Indication

Table 6.2.1-1a: Values of eLCID for DL-SCH

Codepoint

Index

LCID values

000000-000110

32-38

Identity of the logical channel

000111-111111

39-95

Reserved

For NB-IoT only the following LCID values for DL-SCH are applicable: CCCH, Identity of the logical channel, SC-PTM Stop Indication, SC-MCCH/SC-MTCH, UE Contention Resolution Identity, Timing Advance Command, DRX Command and Padding.

21.3.13.3 Test description

21.3.13.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.3.13.3.2 Test procedure sequence

Table 21.3.13.3.2-1: Main Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS transmits SCPTMConfiguration-BR message.

<–

SCPTMConfiguration-BR

2

Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration-BR 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

Exception: Step 4 is repeated 2 times

4

The SS transmits 5 MBMS Packets on the SC-MTCH using G-RNTI.

<–

MBMS Packets.

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?

8

The SS transmits 1 MBMS Packet on the SC-MTCH, with SC-PTM Stop Indication MAC Control Element with LCID = ‘10111’.

<–

MBMS Packet.

10

The SS transmits 2 MBMS Packets on the SC-MTCH using G-RNTI

<–

MBMS Packets.

11

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

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

12

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

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

13

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 10 the same as the value reported in step 6 +1?

1

P

21.3.13.3.3 Specific message contents

Table 21.3.13.3.3-1: SystemInformationBlockType20 for Cell 1 (all steps, Table 21.3.13.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

Same frequency as Cell 1

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.3.13.3.3-2: ACTIVATE TEST MODE (preamble)

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

Table 21.3.13.3.3-3: CLOSE UE TEST LOOP (step 3, Table 21.3.13.3.2-1)

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