22.4.25 NB-IoT / SC-MCCH information acquisition

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

22.4.25.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state and interested to receive SC-PTM services }

ensure that {

when { The SystemInformationBlockType20-NB is broadcast }

then { UE shall acquire the SCPTMConfiguration-NB message at the next repetition period }

}

(2)

with { UE in E-UTRAN RRC IDLE state and interested to receive SC-PTM services and received SCPTMConfiguration-NB message }

ensure that {

when { SS transmits MBMS Packets on the SC-MTCH }

then { UE receives the MBMS Packets }

}

22.4.25.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.306, clause 6.16.1; TS 36.331, clause 5.8a.2.1, 5.8a.2.2, 5.8a.2.3 and 5.8a.3.1.

[TS 36.306, clause 6.16.1]

It is optional for UE to support the SC-PTM reception in RRC_IDLE as specified in TS 36.331 [5]. This feature is only applicable if the UE supports UE category M1 or UE category M2 or if the UE supports coverage enhancements (ce-ModeB-r13 and/or ce-ModeA-r13) or if the UE supports any ue-Category-NB.

[TS 36.331, clause 5.8a.2.1]

The UE applies the SC-MCCH information acquisition procedure to acquire the SC-PTM control information that is broadcast by the E-UTRAN. The procedure applies to SC-PTM capable UEs that are in RRC_IDLE. This procedure also applies to SC-PTM capable UEs that are in RRC_CONNECTED except for BL UEs, UEs in CE or NB-IoT UEs.

[TS 36.331, clause 5.8a.2.2]

A UE interested to receive MBMS services via SC-MRB shall apply the SC-MCCH information acquisition procedure upon entering the cell broadcasting SystemInformationBlockType20 (SystemInformationBlockType20-NB in NB-IoT) (e.g. upon power on, following UE mobility) and upon receiving a notification that the SC-MCCH information has changed. A UE, except for BL UE, UE in CE or NB-IoT UE, that is receiving an MBMS service via SC-MRB shall apply the SC-MCCH information acquisition procedure to acquire the SC-MCCH information that corresponds with the service that is being received, at the start of each modification period. The BL UE, UE in CE or NB-IoT UE that is receiving an MBMS service via SC-MRB shall apply the SC-MCCH information acquisition procedure upon receiving a notification that the SC-MCCH information that corresponds with the service that is being received is about to be changed. The BL UE, UE in CE or NB-IoT UE that is receiving an MBMS service via SC-MRB may apply the SC-MCCH information acquisition procedure upon receiving a notification that the SC-MCCH information is about to be changed due to start of a new service.

Unless explicitly stated otherwise in the procedural specification, the SC-MCCH information acquisition procedure overwrites any stored SC-MCCH information, i.e. delta configuration is not applicable for SC-MCCH information and the UE discontinues using a field if it is absent in SC-MCCH information unless explicitly specified otherwise.

[TS 36.331, clause 5.8a.2.3]

A SC-PTM capable UE shall:

1> if the procedure is triggered by an SC-MCCH information change notification and the UE has no ongoing MBMS service:

…

2> for a BL UE, UE in CE or NB-IoT UE, acquire the SCPTMConfiguration message scheduled by the PDCCH in which the change notification was received;

NOTE 1: The UE continues using the previously received SC-MCCH information until the new SC-MCCH information has been acquired.

1> if the UE enters a cell broadcasting SystemInformationBlockType20 (SystemInformationBlockType20-NB in NB-IoT):

2> acquire the SCPTMConfiguration message at the next repetition period;

1> if the UE is receiving an MBMS service via an SC-MRB:

…

2> a BL UE, UE in CE or NB-IoT UE shall start acquiring the SCPTMConfiguration message at the start of the next modification period upon receiving a notification that the SC-MCCH information that corresponds with the service that is being received is about to be changed;

2> a BL UE, UE in CE or NB-IoT UE may start acquiring the SCPTMConfiguration message at the start of the next modification period upon receiving a notification that the SC-MCCH information is about to be changed due to start of a new service;

[TS 36.331, clause 5.8a.3.1]

The SC-PTM radio bearer configuration procedure is used by the UE to configure RLC, MAC and the physical layer upon starting and/or stopping to receive an SC-MRB transmitted on SC-MTCH. The procedure applies to SC-PTM capable UEs that are in RRC_IDLE and to SC-PTM capable UEs that are not BL UEs, UEs in CE or NB-IoT UEs in RRC_CONNECTED, and are interested to receive one or more MBMS services via SC-MRB.

22.4.25.3 Test description

22.4.25.3.1 Pre-test conditions

System Simulator:

– Ncell 1.

– System information combination 5 as defined in TS 36.508[18] clause 8.1.4.3.1.1.

– SCPTMConfiguration-NB as defined in TS 36.508[18] Table 8.1.6.1-15a is transmitted on SC-MCCH.

UE:

– NB-IOT UE supporting SC-PTM services

Preamble:

– UE is in state NB-IoT UE Attach, Connected Mode, UE Test Mode Activated (State 2A-NB) according to [18] with the UE TEST LOOP MODE F.

22.4.25.3.2 Test procedure sequence

Table 22.4.25.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

2

Make UE to interest in receiving SC-PTM service in the PLMN of Ncell 1 with MBMS Service ID 1.

–

–

–

–

3

Wait for a period equal to the SC-MCCH repetition period for the UE to receive SCPTMConfiguration-NB message.

–

–

–

–

4

The generic procedures described in TS 36.508 clause 8.1.5A.2.3 and 8.1.5.2B.3 is performed on NCell 1 to close UE test loop Mode F.

–

–

–

–

5

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

6

The SS transmits 2 MBMS Packets on the SC-MTCH.

<–

MBMS Packets

–

–

7

‘Generic Test Procedure NB-IoT Control Plane CIoT MT user data transfer non-SMS transport’ as described in TS 36.508 [18], clause 8.1.5A.2.3 are performed

–

–

–

–

8

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

<–

TC: UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

–

–

9

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

–>

TC: UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

–

–

10

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

–

–

1, 2

P

22.4.25.3.3 Specific message contents

None.