17.4.7 MBMS Interest Indication after Radio Link Failure

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

(1)

with { UE in RRC_CONNECTED }

ensure that {

when { the UE detects a radio link failure less than 1 second after the last transmission of an MBMSInterestIndication message }

then { the UE transmits a MBMSInterestIndication message }

}

17.4.7.2 Conformance requirements

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

[TS 36.331, clause 5.3.7.5]

1> if SystemInformationBlockType15 is broadcast by the PCell:

2> if the UE has transmitted an MBMSInterestIndication message during the last 1 second preceding detection of radio link failure:

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

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

3> 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 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: Within this section, the term frequency does not indicate a physical frequency but covers the associated band(s), noting that additional bands may be indicated in SystemInformationBlockType1 (serving frequency) or SystemInformationBlockType15 (neighbouring frequencies).

[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, if applicable, and the EARFCN(s) as included in SystemInformationBlockType15;

NOTE 1: The mbms-FreqList merely indicates the physical frequencies the UE is interested to receive and does not imply the UE supports the associated band.

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.7.3 Test description

17.4.7.3.1 Pre-test conditions

System Simulator:

– 2 cells on the same E-UTRA frequency and with the same PLMN.

– The 2 cells 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 2.

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

UE:

– The UE is configured to receive MBMS services

Preamble:

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

17.4.7.3.2 Test procedure sequence

Table 17.4.7.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 the row marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the text of the column "Procedure" in Table 17.4.7.3.2-2.

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

Parameter

Unit

Cell 1

Cell 2

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-115

T1

Cell-specific RS EPRE

dBm/15kHz

“Off”

-85

Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1.

Table 17.4.7.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 2.

<–

Paging

0B

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 and Cell 2 including mbms-SAI-IntraFreq-r11 list indicating MBMS SAI=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 2 (Note 2).

0E

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

1-1D

Steps 1 to 5 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed.

EXCEPTION: In parallel to the events described in step 1E, the steps specified in Table 17.4.7.3.2-3 take place.

1E

Wait 2s until UE transmits MBMSInterestIndication

1F-1J

Steps 6 to 9 of the generic radio bearer establishment procedure TS 36.508, section 4.5.3.3-1 are executed.

2

Void

3

SS re-adjusts the cell-specific reference signal level according to row "T1" in table 17.4.7.3.2-1.

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

4

UE transmits RRCConnectionReestablishmentRequest message.

–>

RRCConnectionReestablishmentRequest

5

SS transmits RRCConnectionReestablishment message.

<–

RRCConnectionReestablishment

6

UE transmits RRCConnectionReestablishmentComplete message.

–>

RRCConnectionReestablishmentComplete

EXCEPTION: the behaviour in table 17.4.7.3.2-4 runs in parallel with step 9 below.

7

Void

8

Void

9

Check: Does the UE transmit MBMSInterestIndication message?

–>

MBMSInterestIndication

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.7.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: Step 1a describes a behaviour which depends on the UE implementation

1a

UE transmits a MBMSInterestIndication message.

–>

MBMSInterestIndication

Table 17.4.7.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS transmits an RRCConnectionReconfiguration message to resume existing radio bearer.

<–

RRCConnectionReconfiguration

2

UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

17.4.7.3.3 Specific message contents

Table 17.4.7.3.3-1: SystemInformationBlockType2 for Cells 1 and 2 (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.7.3.3-1A: SystemInformationBlockType3 for Cells 1 and 2 (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.7.3.3-2: SystemInformationBlockType15 for Cells 1 and 2 (Step 0B and subsequent steps, Table 17.4.2.3.2-2)

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

Table 17.4.7.3.3-3: MBMSInterestIndication (steps 1a, Table 17.4.7.3.2-3 and 9, Table 17.4.7.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

1 entry

}

}

}

Table 17.4.7.3.3-4: SystemInformationBlockType2 for Cell 1 (preamble and all steps, Table 17.4.7.3.2-2)

Derivation path: 36.508 table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ue-TimersAndConstants SEQUENCE {

t310

ms200

}

}

Table 17.4.7.3.3-5: RRCConnectionReconfiguration (step 1, Table 17.4.7.3.2-2; Step 8, 36.508 Table 4.5.3.3-1 and step 1, Table 17.4.7.3.2-4)

Derivation Path: 36.508 table 4.6.1-8, condition SRB2-DRB(1, 0)

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

drx-Config

Not present

NOT pc_FeatrGrp_5

drx-Config CHOICE {

pc_FeatrGrp_5

setup SEQUENCE {

onDurationTimer

Psf2

drx-InactivityTimer

Psf100

drx-RetransmissionTimer

sf16

longDRX-CycleStartOffset CHOICE {

sf40

4

}

shortDRX

Not present

}

}

}

}

}

}

}

}