21.3.5 Conditional retransmission of MBMS Interest Indication after handover

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

21.3.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC_Connected state AND SystemInformationBlockType15 and SystemInformationBlockType20 have been acquired by the UE AND the UE has transmitted a MBMSInterestIndication message on the Pcell }

ensure that {

when { UE receives a RRCConnectionReconfiguration message including mobilityControlInfo less than 1 second after the last transmission of an MBMSInterestIndication message AND UE has completed the intra frequency handover procedure }

then { UE should re-transmit a MBMSInterestIndication message }

}

21.3.5.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.3 and 5.8.5.4. Unless otherwise stated these are Rel-13 requirements.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> stop timer T370, if running;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

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> determine the set of MBMS services of interest in accordance with 5.8.5.3a;

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

[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 or SC-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 or SC-MRB for the concerned session. I.e. the UE does not verify if the session is indicated on (SC-)MCCH

NOTE 3: The UE considers the frequencies of interest independently of any synchronization state, e.g. [9, Annex J.1]

2> the UE is capable of simultaneously receiving MRBs and/or is capable of simultaneously receiving SC-MRBs on 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 4: Indicating a frequency implies that the UE supports SystemInformationBlockType13 or SystemInformationBlockType20 acquisition for the concerned frequency i.e. the indication should be independent of whether a serving cell is configured on that frequency.

NOTE 5: 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 6: 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 sorted by decreasing order 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;

2> if SystemInformationBlockType20 is broadcast by the PCell:

3> include mbms-Services and set it to indicate the set of MBMS services of interest determined in accordance with 5.8.5.3a;

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.

21.3.5.3 Test description

21.3.5.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 "Serving cell" and Cell 2 is "Non-suitable cell" as defined in TS 36.508 Table 6.2.2.1-1.

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

SCPTMConfiguration as defined in TS 36.508[18] table 4.6.1-18a is transmitted on SC-MCCH on Cell 1 and Cell 2.

UE:

– E-UTRAN UE supporting SC-PTM services.

Preamble:

– UE is in state Registered, Idle Mode (state 2) on Cell 1 according to [18].

21.3.5.3.2 Test procedure sequence

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

Table 21.3.5.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

The generic procedures described in TS 36.508 sub clause 4.5.3.3 are performed on Cell 1.

3

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

<–

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 21.3.5.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 UE is made interested in receiving SC-PTM service with MBMS Service ID=0 associated with the MBMS SAI (1) broadcasted in SIB15 mbms-SAI-IntraFreq list on Cell 1 and Cell 2.

8

The UE transmits a MBMSInterestIndication message.

–>

MBMSInterestIndication

9

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra-frequency handover to Cell 2 within 500 ms after reception of the MBMSInterestIndication message in step 8.

<–

RRCConnectionReconfiguration

10

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2.

–>

RRCConnectionReconfigurationtComplete

11

Check: Does the UE transmit MBMSInterestIndication message?

–>

MBMSInterestIndication

1

P

21.3.5.3.3 Specific message contents

Table 21.3.5.3.3-1: SystemInformationBlockType15 for Cell 1 (step 2 and all later steps)

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

Table 21.3.5.3.3-2: RRCConnectionReconfiguration (step 3, Table 21.3.5.3.2-2)

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

Table 21.3.5.3.3-3: MeasConfig (Table 21.3.5.3.3-2)

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 f1

}

}

}

Condition

Explanation

Band > 64

This condition applies if the band number is bigger than 64.

Table 21.3.5.3.3-4: MeasurementReport (step 6, Table 21.3.5.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 21.3.5.3.3-5: MBMSInterestIndication (step 8 and step 11, Table 21.3.5.3.2-2)

Derivation Path: 36.508, Table 4.6.1-4AC, condition SC-PTM.

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 1

INTEGER (0..maxEARFCN2)

}

}

Table 21.3.5.3.3-6: RRCConnectionReconfiguration (step 9, Table 21.3.5.3.2-2)

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

Table 21.3.5.3.3-7: MobilityControlInfo-HO (Table 21.3.5.3.3-6)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}