17.4.2 Cell reselection to inter- frequency cell to start MBMS service reception

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

17.4.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state on a cell broadcasting SIB15 and interested to receive a MBMS service}

ensure that {

when { SIB15 indicates that the MBMS service is available on a frequency of an inter-frequency neighbour cell }

then { UE performs cell reselection to the inter-frequency neighbour cell even if the serving cell is better and starts MBMS reception }

}

17.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.1 and TS 36.331, clause 5.2.2.4. Unless otherwise stated these are Rel-11 requirements.

[TS 36.304 clause 5.2.4.1]

Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an E-UTRAN frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and deprioritisationReq received in RRCConnectionReject unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than the eight network configured values). While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than the eight network configured values), irrespective of any other priority value allocated to this frequency. If the UE is capable of MBMS Service Continuity and receiving or interested to receive an MBMS service and can only receive this MBMS service while camping on a frequency on which it is provided, the UE may consider that frequency to be the highest priority during the MBMS session [2] as long as the reselected cell is broadcasting SIB13 and as long as:

– SIB15 of the serving cell indicates for that frequency one or more MBMS SAIs included in the MBMS User Service Description (USD) [22] of this service; or

– SIB15 is not broadcast in the serving cell and that frequency is included in the USD of this service.

If the UE is not capable of MBMS Service Continuity but has knowledge on which frequency an MBMS service of interest is provided, it may consider that frequency to be the highest priority during the MBMS session [2] as long as the reselected cell is broadcasting SIB13.

NOTE: The UE considers that the MBMS session is ongoing using the session start and end times as provided by upper layers in the USD i.e. the UE does not verify if the session is indicated on MCCH.

[TS 36.331 clause 5.2.2.4]

The UE shall:

1> if the UE is interested to receive MBMS services:

2> if schedulingInfoList indicates that SystemInformationBlockType13 is present and the UE does not have stored a valid version of this system information block:

3> acquire SystemInformationBlockType13;

2> if the UE is capable of MBMS Service Continuity:

3> if schedulingInfoList indicates that SystemInformationBlockType15 is present and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType15;

17.4.2.3 Test description

17.4.2.3.1 Pre-test conditions

System Simulator:

– 2 E-UTRA cells with the same PLMN. Cell 1 and Cell 23 are inter-frequency cells. Cell 1 is "Serving cell" and Cell 23 is "Non-suitable cell" as defined in TS 36.508 Table 6.2.2.1-1.

  • MBSFNAreaConfiguration message as defined in TS 36.508 [18] Table 4.6.1-4A is transmitted on Cell 23.

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

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

UE:

– The UE is configured to receive MBMS 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 C.

17.4.2.3.2 Test procedure sequence

Table 17.4.2.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 after preamble.

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

Parameter

Unit

Cell 1

Cell 23

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are assigned to satisfy R Cell 23 < RCell 1.

Table 17.4.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0A

The SS transmits a Paging message including a systemInfoModification for Cell1 and Cell 23.

<–

Paging

0B

From the beginning of the next modification period the SS starts broadcast of SystemInformationBlockType15 according to system information combination 18 on Cell 1 and according to system information combination 20 on Cell 23 including mbms-SAI-IntraFreq-r11 list indicating MBMS SAI=1.

Note: System information combination 18 and 20 is defined in TS 36.508[18] clause 4.4.3.1.

<–

SystemInformationBlockType15

0C

Wait 13 s for UE to receive modified system information (Note 1).

0D

The UE is made interested in receiving a MBMS service with MBMS Service ID=0 associated with the MBMS SAI (1) broadcasted in SIB15 mbms-SAI-InterFreq list on Cell 1 and Cell 23 (Note 2).

0E

The UE is made aware that the MBMS service is active (Note 2).

EXCEPTION: the behaviour in table 17.4.2.3.2-3 runs in parallel with steps 1 to 3 below.

1

The UE executes the generic test procedure described in TS 36.508 subclause 6.4.2.7 and UE should camp on E-UTRA Cell 23.

NOTE: The UE performs a TAU procedure and the RRC connection is released.

2

Void

3

Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message

EXCEPTION: In parallel to the events described in step 4,The steps described in Table 17.4.2.3.2-3 may takeplace, depending on the UE implementation.

4

The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 23 activating UE test loop Mode C.

4A

The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.

<–

RRC: RRCConnectionRelease

Exception; Step 5 is repeated 5 times

5

The SS transmits 2 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000001’ in the first MAC PDU of the MCH Scheduling Period.

<–

MBMS Packets

6

Void

EXCEPTION: In parallel to the events described in steps 6A, 7 and 8, the steps described in Table 17.4.2.3.2-3 may takeplace, depending on the UE implementation.

6A

Generic test procedure Generic Radio Bearer Establishment as described in TS 36.508 subclause 4.5.3 is executed.

7

The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST

8

UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE

9

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

(Note: This verifies that UE has selected Cell 23 providing the MBMS service and starts MBMS reception)

1

P

Note 1: Minimum delay 12,8 sec. = 2.5 * BCCH modification period (512 rf) to ensure UE detected SIB update.

Note 2: The request may be performed by MMI or AT command.

Table 17.4.2.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE transmits a MBMSInterestIndication message.

–>

MBMSInterestIndication

17.4.2.3.3 Specific message contents

Table 17.4.2.3.3-1: SystemInformationBlockType2 for Cell 23 (preamble and all steps, Table 17.4.2.3.2-2)

Derivation Path: 36.508 table 4.4.3.3-1, condition MBMS.

Table 17.4.2.3.3-2: SystemInformationBlockType15 for Cell 1 (Step 0B and later steps preamble and all steps, Table 17.4.2.3.2-2)

Derivation Path: 36.508 table 4.4.3.3-14, condition MBMS_interFreq.

SystemInformationBlockType15 ::= SEQUENCE {

mbms-SAI-IntraFreq-r11 SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

Not present

mbms-SAI-InterFreqList-r11[1] SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE {

1 entry

dl-CarrierFreq-r11

Downlink EARFCN for Cell 23, see table 6.3.1.2-1.

mbms-SAI-List-r11[1] SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

1

1 entry

INTEGER (0..65535)

Table 17.4.2.3.3-3: SystemInformationBlockType15 for Cell 23 (Step 0B and later steps preamble and all steps, Table 17.4.2.3.2-2)

Derivation Path: 36.508 table 4.4.3.3-14, condition MBMS_intraFreq.

Table 17.4.2.3.3-4: ACTIVATE TEST MODE (preamble)

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

Table 17.4.2.3.3-5: CLOSE UE TEST LOOP (step 4, Table 17.4.2.3.2-2)

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