17.4.6 MBMS Interest Indication retransmission after returning from cell not broadcasting SIB15

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

(1)

with { UE in E-UTRA RRC_Connected state AND is receiving MBMS service and having transmitted a MBMSInterestIndication message }

ensure that {

when { UE performs handover to a Pcell not broadcasting SystemInformationBlockType15 followed by a handover to a Pcell broadcasting SystemInformationBlockType15 }

then { UE transmits a MBMSInterestIndication message }

}

17.4.6.2 Conformance requirements

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

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

[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;

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

NOTE: 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.6.3 Test description

17.4.6.3.1 Pre-test conditions

System Simulator:

– 2 E-UTRA cells with the same PLMN, Cell 1 and Cell 2 are intra-frequency cells. Cell 1 is a MBMS cell and Cell 2 is a non-MBMS cell.

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

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

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

UE:

– The UE is configured to receive MBMS services.

Preamble:

– UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

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

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

NOTE: AT Commands for eMBMS service activation specified in TS 27.007 [58] cannot be used as TP cannot be achieved.

17.4.6.3.2 Test procedure sequence

Table 17.4.6.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","T1" and "T2" 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.6.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

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 2 (M2) satisfy exit condition for event A3 (M1 > M2).

T1

Cell-specific RS EPRE

dBm/15kHz

-91

-85

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

T2

Cell-specific RS EPRE

dBm/15kHz

-85

-91

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

Table 17.4.6.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

The SS transmits a Paging message including a systemInfoModification for Cell 1.

<–

Paging

1

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

<–

SystemInformationBlockType15

2

Check: Does the UE transmit MBMSInterestIndication message.

–>

MBMSInterestIndication

1

P

3

The SS transmits an RRCConnectionReconfiguration message to setup intra- frequency measurement.

<–

RRCConnectionReconfiguration

4

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

–>

RRCConnectionReconfigurationComplete

5

The SS changes Cell 1 and Cell 2 level according to the row "T1" in table 17.4.6.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 2.

–>

MeasurementReport

7

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

<–

RRCConnectionReconfiguration

8

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2

–>

RRCConnectionReconfigurationComplete

9

The SS transmits an RRCConnectionReconfiguration message to setup intra frequency measurement on Cell 2.

<–

RRCConnectionReconfiguration

10

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

–>

RRCConnectionReconfigurationComplete

11

The SS changes Cell 1 and Cell 2 levels according to the row "T2" in table 17.4.6.3.2-1.

12

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

–>

MeasurementReport

13

Void

14

Void

EXCEPTION: the behaviour in table 17.4.6.3.2-3 runs in parallel with step 15 below.

15

Check: Does the UE transmit MBMSInterestIndication message.

–>

MBMSInterestIndication

2

P

Table 17.4.6.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS transmits an RRCConnectionReconfiguration message on Cell 2 to order the UE to perform intra-frequency handover to Cell 1.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

17.4.6.3.3 Specific message contents

Table 17.4.6.3.3-1: SystemInformationBlockType2 for Cells 1 (Preamble and all steps, Table 17.4.6.3.2-2)

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

Table 17.4.6.3.3-1a: SystemInformationBlockType15 for Cell 1 (Step 1 and all the subsequent steps, Table 17.4.6.3.2-2)

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

Table 17.4.6.3.3-2: RRCConnectionReconfiguration (step 3 and 9, Table 17.4.6.3.2-2)

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

Table 17.4.6.3.3-3: MeasConfig (step 3 and 9, Table 17.4.4.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 {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

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-f1

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 f 1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 17.4.6.3.3-4: MeasurementReport (step 6, Table 17.4.6.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 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 17.4.6.3.3-5: MeasurementReport (step 12, Table 17.4.6.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

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

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

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 17.4.6.3.3-6: MBMSInterestIndication (step 2 and 15, Table 17.4.6.3.2-2)

Derivation Path: 36.508, Table 4.6.1-4AC

Information Element

Value/remark

Comment

Condition

criticalExtensions CHOICE {

c1 CHOICE{

interestIndication-r11 OF SEQUENCE {

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

EARFCN of Cell 1

}

}

}