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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

17.4.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state AND SystemInformationBlockType15 have been acquired by the UE on the Pcell 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 }

}

17.4.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.8.5.3, 5.3.5.4, 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.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> 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;

[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.5.3 Test description

17.4.5.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2 are intra-frequency cells and belongs to 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 19 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA Cell 1 and Cell 2.

UE:

– The UE is configured to receive MBMS services.

Preamble:

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

17.4.5.3.2 Test procedure sequence

Table 17.4.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 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.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 17.4.5.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message.	–	–	–	–
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 17.4.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 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 2 (Note 1)	–	–	–	–
7A	The UE is made aware that the MBMS service is active (Note 1).	–	–	–	–
8	Check: Does the UE transmit MBMSInterestIndication message?	–>	MBMSInterestIndication	1	P
9 -10	Void	–	–
–	EXCEPTION: the behaviour in table 17.4.5.3.2-3 runs in parallel with step 11 below.	–	–	–	–
11	Check: Does the UE transmit MBMSInterestIndication message?	–>	MBMSInterestIndication	1	P
Note 1: The request may be performed by MMI or AT command.

Table 17.4.5.3.2-3: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits an RRCConnectionReconfiguration message message on Cell 1 to order the UE to perform intra-frequency handover to Cell 2 less than [600ms] after reception of the MBMSInterestIndication message in step 8 of Table 17.4.5.3.2-2	<–	RRCConnectionReconfiguration	–	–
2	UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationtComplete	–	–

17.4.5.3.3 Specific message contents

Table 17.4.5.3.3-1: SystemInformationBlockType2 for Cells 1 and 2 (Preamble and all steps, Table 17.4.5.3.2-2)

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

Table 17.4.5.3.3-1A: SystemInformationBlockType3 for Cells 1 and 2 (Preamble and all steps, Table 17.4.5.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.5.3.3-2: SystemInformationBlockType15 for Cells 1 and 2 (Preamble and all steps, Table 17.4.5.3.2-2)

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

Table 17.4.5.3.3-3: RRCConnectionReconfiguration (step 2, Table 17.4.5.3.2-2)

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

Table 17.4.5.3.3-4: MeasConfig (Table 17.4.5.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 f1
}
}
}

Condition	Explanation
Band > 64	If band > 64 is selected

Table 17.4.5.3.3-4A: MeasObjectEUTRA-GENERIC(f1) (Table 17.4.5.3.3-4)

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.5.3.3-5: MeasurementReport (step 6, Table 17.4.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 17.4.5.3.3-6: MBMSInterestIndication (step 8 & 11, Table 17.4.5.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[n] SEQUENCE (SIZE (1..maxFreqMBMS-r11)) OF { INTEGER (0..maxEARFCN2) }	Same EARFCN as used for Cell 2
mbms-Priority-r11	Not present
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {}	Not present
}
}
}

Table 17.4.5.3.3-7: RRCConnectionReconfiguration (step 1, Table 17.4.5.3.2-3)

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

Table 17.4.5.3.3-8: MobilityControlInfo (Table 17.4.5.3.3-7)

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
}