17.4.1 Cell reselection to intra-frequency cell to continue 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.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state with ongoing MBMS reception on a cell broadcasting SIB15 indicating the MBMS SAI associated with the ongoing MBMS service for the frequency of the cell}

ensure that {

when { an intra-frequency neighbour cell providing the MBMS service and an inter-frequency neighbour cell not providing the MBMS service becomes better than the serving cell }

then { UE performs cell reselection to the intra-frequency cell even if the inter-frequency cell is better and continues MBMS reception }

}

17.4.1.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.1.3 Test description

17.4.1.3.1 Pre-test conditions

System Simulator:

  • 3 E-UTRA cells with the same PLMN. Cell 1 and Cell 11 are intra-frequency cells. Cell 3 is inter-frequency cell to Cell 1 and Cell 11. Cell 1 "Serving cell", Cell 11 and Cell 3 are "Non-suitable cell" as defined in TS 36.508 Table 6.2.2.1-1.
  • Cell 1 and Cell 11 are part of the same MBSFN area
  • MBSFNAreaConfiguration message as defined in TS 36.508 [18] Table 4.6.1-4A is transmitted on Cell 1 and Cell 11.
  • System information combination 16 as defined in TS 36.508[18] clause 4.4.3.1 is used in Cell 1 and Cell 11.
  • System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in Cell 3.

UE:

– The UE is configured to receive MBMS services.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] in Cell 1(serving cell), with the UE TEST LOOP MODE C.

– 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-IntraFreq list on Cell 1 and Cell 11.

– The UE is made aware that the MBMS service is active.

17.4.1.3.2 Test procedure sequence

Table 17.4.1.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, while row 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 17.4.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 11

Cell 3

Remark

T0

Cell-specific RS EPRE (FDD)

dBm/15kHz

-85

-91

-91

Cell-specific RS EPRE (TDD)

dBm/15kHz

-85

-89

-89

T1

Cell-specific RS EPRE (FDD)

dBm/15kHz

-91

-85

-79

The power level values are assigned to satisfy RCell 1 < R Cell 11 < RCell 3

Cell-specific RS EPRE (TDD)

dBm/15kHz

-89

-85

-79

Table 17.4.1.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 11.

<–

Paging

0B

From the beginning of the next modification period the SS starts broadcast of SystemInformationBlockType15 (according to System information combination 20 as defined in TS 36.508[18] clause 4.4.3.1) on Cell 1 and Cell 11 including mbms-SAI-IntraFreq-r11 list indicating MBMS SAI=1.

<–

SystemInformationBlockType15

The following messages are to be observed on Cell 1 unless explicitly stated otherwise.

0C

UE transmits a MBMSInterestIndication message.

–>

MBMSInterestIndication

1

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

<–

RRC: RRCConnectionRelease

EXCEPTION: Step 2 is repeated 5 times.

2

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

3

Void

EXCEPTION: In parallel to the events described in steps 3A, 4 and 5, the steps described in Table 17.4.1.3.2-3 may take place, depending on the UE implementation.

3A

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

4

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

<–

UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST

5

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

–>

UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE

6

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

(Note: This verifies that MBMS reception is active in the UE in RRC_IDLE mode on Cell 1 before the cell re-selection to Cell 11)

1

P

6A

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

<–

RRC: RRCConnectionRelease

7

The SS changes Cell 1, Cell 11 and Cell 3 levels according to the row "T1" in table 17.4.1.3.2-1.

The following messages are to be observed on Cell 11 unless explicitly stated otherwise.

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

8

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 11.

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

9

Void

10

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

EXECPTION: Step 11 is repeated 5 times.

11

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

12

Void

EXCEPTION: In parallel to the events described in steps 12A, 13 and 14, the steps described in Table 17.4.1.3.2-3 may takeplace, depending on the UE implementation.

12A

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

13

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

<–

UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST

14

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

–>

UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE

15

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

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

1

P

Table 17.4.1.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE transmits a MBMSInterestIndication message.

–>

MBMSInterestIndication

17.4.1.3.3 Specific message contents

Table 17.4.1.3.3-1: SystemInformationBlockType2 for Cells 1 and 11 (preamble and all steps, Table 17.4.1.3.2-2)

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

Table 17.4.1.3.3-1A: SystemInformationBlockType3 for Cells 1 and 11 (Preamble and all steps)

Derivation Path: 36.508, Table 4.4.3.3-2

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType3 ::= SEQUENCE {

intraFreqCellReselectionInfo SEQUENCE {

neighCellConfig

’10’B

The MBSFN subframe allocations of all neighbour cells are identical to or subsets of that in the serving cell on this frequency, if configured, and of that in the PCell otherwise

}

}

Table 17.4.1.3.3-1B: SystemInformationBlockType5 for Cell 1 and 11 (Preamble and all steps)

Derivation Path: 36.508, Table 4.4.3.3-4

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType5 ::= SEQUENCE {

interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE {

neighCellConfig[n]

’10’B

The MBSFN subframe allocations of all neighbour cells are identical to or subsets of that in the serving cell on this frequency, if configured, and of that in the PCell otherwise

}

}

Table 17.4.1.3.3-2: SystemInformationBlockType15 for Cells 1 and 11 (Step 0B and subsequent steps, Table 17.4.1.3.2-2)

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

Table 17.4.1.3.3-3: ACTIVATE TEST MODE (preamble)

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

Table 17.4.1.3.3-4: CLOSE UE TEST LOOP (preamble)

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