17.4.3 Handover 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 17TSUser Equipment (UE) conformance specification

17.4.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state AND 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 transmits a MBMSInterestIndication message indicating interest in MBMS reception on the frequency }

}

(2)

with { UE in E-UTRA RRC_Connected state AND having transmitted a MBMSInterestIndication message indicating interest in MBMS reception on a frequency of an inter-frequency neighbour cell }

ensure that {

when { 1s after the UE has transmitted the MBMSInterestIndication message the UE receives RRCConnectionReconfiguration message including a mobilityControlInfo indicating a the E-UTRA frequency of the inter-frequency neighbour cell }

then { UE performs inter-frequency handover and starts MBMS reception }

}

17.4.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.5.4, 5.8.5.2, 5.8.5.3, 5.8.5.4. Unless otherwise stated these are Rel-11 requirements.

[TS 36.331 clause 5.3.5.4]

  1. submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

….

2> if SystemInformationBlockType15 is broadcast by the PCell:

3> if the UE has transmitted a MBMSInterestIndication message during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo:

4> ensure having a valid version of SystemInformationBlockType15 for the PCell;

4> determine the set of MBMS frequencies of interest in accordance with 5.8.5.3;

4> initiate transmission of the MBMSInterestIndication message in accordance with 5.8.5.4;

2> the procedure ends;

[TS 36.331 clause 5.8.5.2]

An MBMS capable UE in RRC_CONNECTED may initiate the procedure in several cases including upon successful connection establishment, upon entering or leaving the service area, upon session start or stop, upon change of interest, upon change of priority between MBMS reception and unicast reception or upon change to a PCell broadcasting SystemInformationBlockType15.

Upon initiating the procedure, the UE shall:

1> if SystemInformationBlockType15 is broadcast by the PCell:

2> ensure having a valid version of SystemInformationBlockType15 for the PCell;

2> if the UE did not transmit an MBMSInterestIndication message since last entering RRC_CONNECTED state; or

2> if since the last time the UE transmitted an MBMSInterestIndication message, the UE connected to a PCell not broadcasting SystemInformationBlockType15:

3> if the set of MBMS frequencies of interest, determined in accordance with 5.8.5.3, is not empty:

4> initiate transmission of the MBMSInterestIndication message in accordance with 5.8.5.4;

2> else:

3> if the set of MBMS frequencies of interest, determined in accordance with 5.8.5.3, has changed since the last transmission of the MBMSInterestIndication message; or

3> if the prioritisation of reception of all indicated MBMS frequencies compared to reception of any of the established unicast bearers has changed since the last transmission of the MBMSInterestIndication message:

4> initiate transmission of the MBMSInterestIndication message in accordance with 5.8.5.4;

NOTE: The UE may send an MBMSInterestIndication even when it is able to receive the MBMS services it is interested in i.e. to avoid that the network allocates a configuration inhibiting MBMS reception.

[TS 36.331 clause 5.8.5.3]

The UE shall:

1> consider a frequency to be part of the MBMS frequencies of interest if the following conditions are met:

2> at least one MBMS session the UE is receiving or interested to receive via an MRB is ongoing or about to start; and

NOTE 1: The UE may determine whether the session is ongoing from the start and stop time indicated in the User Service Description (USD), see 3GPP TS 36.300 [9] or 3GPP TS 26.346 [57].

2> for at least one of these MBMS sessions SystemInformationBlockType15 acquired from the PCell includes for the concerned frequency one or more MBMS SAIs as indicated in the USD for this session; and

NOTE 2: The UE considers a frequency to be part of the MBMS frequencies of interest even though E-UTRAN may (temporarily) not employ an MRB for the concerned session. I.e. the UE does not verify if the session is indicated on MCCH.

2> the UE is capable of simultaneously receiving the set of MBMS frequencies of interest, regardless of whether a serving cell is configured on each of these frequencies or not; and

2> the supportedBandCombination the UE included in UE-EUTRA-Capability contains at least one band combination including the set of MBMS frequencies of interest;

NOTE 3: Indicating a frequency implies that the UE supports SystemInformationBlockType13 acquisition for the concerned frequency i.e. the indication should be independent of whether a serving cell is configured on that frequency.

NOTE 4: When evaluating which frequencies it can receive simultaneously, the UE does not take into account the serving frequencies that are currently configured i.e. it only considers MBMS frequencies it is interested to receive.

NOTE 5: The set of MBMS frequencies of interest includes at most one frequency for a given physical frequency. The UE only considers a physical frequency to be part of the MBMS frequencies of interest if it supports at least one of the bands indicated for this physical frequency in SystemInformationBlockType1 (for serving frequency) or SystemInformationBlockType15 (for neighbouring frequencies). In this case, E-UTRAN may assume the UE supports MBMS reception on any of the bands supported by the UE (i.e. according to supportedBandCombination).

[TS 36.331 clause 5.8.5.4]

The UE shall set the contents of the MBMSInterestIndication message as follows:

1> if the set of MBMS frequencies of interest, determined in accordance with 5.8.5.3, is not empty:

2> include mbms-FreqList and set it to include the MBMS frequencies of interest, using the EARFCN corresponding with freqBandIndicator included in SystemInformationBlockType1 (for serving frequency), if applicable, and the EARFCN(s) as included in SystemInformationBlockType15 (for neighbouring frequencies);

NOTE 1: The EARFCN included in mbms-FreqList is merely used to indicate a physical frequency the UE is interested to receive i.e. the UE may not support the band corresponding to the included EARFCN (but it does support at least one of the bands indicated in system information for the concerned physical frequency).

2> include mbms-Priority if the UE prioritises reception of all indicated MBMS frequencies above reception of any of the unicast bearers;

NOTE 2: If the UE prioritises MBMS reception and unicast data cannot be supported because of congestion on the MBMS carrier(s), E-UTRAN may initiate release of unicast bearers. It is up to E-UTRAN implementation whether all bearers or only GBR bearers are released. E-UTRAN does not initiate re-establishment of the released unicast bearers upon alleviation of the congestion.

The UE shall submit the MBMSInterestIndication message to lower layers for transmission.

17.4.3.3 Test description

17.4.3.3.1 Pre-test conditions

System Simulator:

– 2 E-UTRA cells with the same PLMN belonging to same MBSFN area. Cell 1 and Cell 3 are inter-frequency cells. Cell 1 is "Serving cell" and Cell 3 is "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 1 and Cell 3.

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

UE:

– The UE is configured to receive MBMS services.

Preamble:

– UE is in state Loopback Activated (State 4) with UE TEST LOOP MODE C on Cell 1 according to [18].

17.4.3.3.2 Test procedure sequence

Table 17.4.3.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 columns marked "T0", and "T1" are 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.3.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

Table 17.4.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

00

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 3. (Note 1).

–

–

–

–

00A

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

–

–

–

–

0

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

<–

Paging

–

–

1

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 3. SystemInformationBlockType15 on Cell 1 is including mbms-SAI-InterFreq list for the frequency of Cell 3 indicating MBMS SAI=1. SystemInformationBlockType15 on Cell 3 is including mbms-SAI-IntraFreq list indicating MBMS SAI=1.

<–

SystemInformationBlockType15

–

–

2

Check: Does the UE transmit MBMSInterestIndication message.

–>

MBMSInterestIndication

1

P

2A

The SS waits for 1s.

3

The SS transmits an RRCConnectionReconfiguration message to setup inter frequency measurement on Cell 1.

<–

RRCConnectionReconfiguration

–

–

4

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the setup of inter frequency measurement.

–>

RRCConnectionReconfigurationComplete

–

–

5

The SS changes Cell 1 and Cell 3 level according to the row "T1" in table 17.4.3.3.2-1.

–

–

–

–

6

The UE transmits a MeasurementReport message to report event A3 on Cell 1 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

7

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-frequency handover to Cell 3.

<–

RRCConnectionReconfiguration

–

–

8

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3?

–>

RRCConnectionReconfigurationComplete

–

–

–

Exception; Step 9 is repeated 5 times

–

–

–

–

9

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

–

–

10

Void

–

–

–

–

11

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

<–

UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST

–

–

12

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

–>

UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE

–

–

13

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

–

–

2

P

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

17.4.3.3.3 Specific message contents

Table 17.4.3.3.3-0: Conditions for specific message contents
in Tables 17.4.3.3.3-1B, 17.4.3.3.3-6 and 17.4.3.3.3-9

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 17.4.3.3.3-1: SystemInformationBlockType2 for Cells 1 and 3 (Preamble and all steps, Table 17.4.3.3.2-2)

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

Table 17.4.3.3.3-1A: SystemInformationBlockType3 for Cells 1 and 3 (Preamble and all steps, Table 17.4.3.3.2-2)

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.3.3.3-1B: SystemInformationBlockType5 for Cell 1 and Cell 3 (Preamble and all steps, Table 17.4.3.3.2-2)

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.3.3.3-2: SystemInformationBlockType15 for Cell 1 (step 1 and all subsequent steps, Table 17.4.3.3.2-2)

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

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType15 ::= SEQUENCE {

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

2

1 entry

INTEGER (0..65535)

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

1 entry

n denotes the index of the entry

dl-CarrierFreq-r11

Downlink EARFCN of Cell 3, see table 6.3.1.2-1.

}

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

1

INTEGER (0..65535)

}

Table 17.4.3.3.3-3: SystemInformationBlockType15 for Cell 3 (step 1 and all subsequent steps, Table 17.4.3.3.2-2)

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

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType15 ::= SEQUENCE {

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

1

1 entry

INTEGER (0..65535)

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

1 entry

n denotes the index of the entry

dl-CarrierFreq-r11

Downlink EARFCN of Cell 1, see table 6.3.1.2-1.

}

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

2

INTEGER (0..65535)

}

Table 17.4.3.3.3-4: MBMSInterestIndication (step 2, Table 17.4.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-4C

Information Element

Value/remark

Comment

Condition

criticalExtensions CHOICE {

c1 CHOICE{

mbms-FreqList-r11[1] SEQUENCE (SIZE (1..maxFreqMBMS-r11)) OF { INTEGER (0..maxEARFCN2) }

Same EARFCN as used for Cell 3

INTEGER (0..maxEARFCN2)

}

}

Table 17.4.3.3.3-5: RRCConnectionReconfiguration (step 3, Table 17.4.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 17.4.3.3.3-6: MeasConfig (Table 17.4.3.3.3-3)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

Cell 1

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Cell 3

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

}

Table 17.4.3.3.3-6A: MeasObjectEUTRA-GENERIC(f1/f2) (Table 17.4.3.3.3-3)

Derivation Path: 36.508, Table 4.6.6-2

Information Element

Value/remark

Comment

Condition

MeasObjectEUTRA-GENERIC(Freq) ::= SEQUENCE {

neighbourCellConfig

’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.3.3.3-7: MeasurementReport (step 6, Table 17.4.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 17.4.3.3.3-8: RRCConnectionReconfiguration (step 7, Table 17.4.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 17.4.3.3.3-9: MobilityControlInfo (Table 17.4.3.3.3-6)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 3

Band 24 High range

}

carrierFreq

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3.

}

}