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

21.3.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state AND is receiving SC-PTM 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 }

}

21.3.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, 5.8.5.3a and 5.8.5.4.

[TS 36.331 clause 5.8.5.2]

An MBMS or SC-PTM 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;

[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.3a]

The UE shall:

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

2> the UE is SC-PTM capable; and

2> the UE is receiving or interested to receive this service via an SC-MRB; and

2> one session of this service is ongoing or about to start; and

2> one or more MBMS SAIs in the USD for this service is included in SystemInformationBlockType15 acquired from the PCell for a frequency belonging to the set of MBMS frequencies of interest, determined according to 5.8.5.3.

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

21.3.6.3.1 Pre-test conditions

System Simulator:

– 2 E-UTRA cells with the same PLMN (PLMN1), Cell 1 and Cell 2 are intra-frequency cells. Cell 1 is a SC-PTM cell and Cell 2 is a non-SC-PTM cell.

– System information combination 25 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.

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

UE:

– E-UTRAN UE supporting SC-PTM services.

Preamble:

– UE is in state Generic RB Established, Test Mode Activated (state 3A) according to [18] in Cell 1 (serving cell) with the UE TEST LOOP MODE F.

– The UE is made interested in receiving SC-PTM service in the PLMN of Cell 1 with MBMS Service ID=1.

– The UE is made aware that the SC-PTM service is active.

21.3.6.3.2 Test procedure sequence

Table 21.3.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 21.3.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 21.3.6.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a systemInfoModification for Cell 1.	<–	Paging	–	–
2	From the beginning of the next modification period the SS starts broadcast of SystemInformationBlockType15 according to System information combination 27 as defined in TS 36.508[18] clause 4.4.3.1 on Cell 1 including mbms-SAI-IntraFreq-r11 indicating MBMS SAI=1.	<–	SystemInformationBlockType15	–	–
3	The UE transmit MBMSInterestIndication message.	–>	MBMSInterestIndication	–	–
4	The SS transmits an RRCConnectionReconfiguration message to setup intra-frequency measurement.	<–	RRCConnectionReconfiguration	–	–
5	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the setup of intra-frequency measurement.	–>	RRCConnectionReconfigurationComplete	–	–
6	The SS changes Cell 1 and Cell 2 level according to the row "T1" in table 21.3.6.3.2-1.	–	–	–	–
7	The UE transmits a MeasurementReport message to report event A3 on Cell 1 with the measured RSRP, RSRQ value for Cell 2.	–>	MeasurementReport	–	–
8	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra-frequency handover to Cell 2.	<–	RRCConnectionReconfiguration	–	–
9	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2	–>	RRCConnectionReconfigurationComplete	–	–
10	The SS transmits an RRCConnectionReconfiguration message to setup intra frequency measurement on Cell 2.	<–	RRCConnectionReconfiguration	–	–
11	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2 to confirm the setup of intra frequency measurement.	–>	RRCConnectionReconfigurationComplete	–	–
12	Wait 5 seconds for the UE to be able to monitor absence of SystemInformationBlockType15 on Cell 2.	–	–	–	–
13	The SS changes Cell 1 and Cell 2 levels according to the row "T2" in table 21.3.6.3.2-1.	–	–	–	–
14	The UE transmits a MeasurementReport message to report event A3 on Cell 2 with the measured RSRP, RSRQ value for Cell 1.	–>	MeasurementReport	–	–
15	The SS transmits an RRCConnectionReconfiguration message on Cell 2 to order the UE to perform intra-frequency handover to Cell 1.	<–	RRCConnectionReconfiguration	–	–
16	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.	–>	RRCConnectionReconfigurationComplete	–	–
17	Wait for a period equal to the SC-MCCH repetition period for the UE to receive SCPTMConfiguration message on Cell 1.	–	–	–	–
18	Check: Does the UE transmit MBMSInterestIndication message.	–>	MBMSInterestIndication	1	P

21.3.6.3.3 Specific message contents

Table 21.3.6.3.3-1: SystemInformationBlockType15 for Cell 1 (Step 2 and all the subsequent steps, Table 21.3.6.3.2-2)

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

Table 21.3.6.3.3-2: RRCConnectionReconfiguration (step 4 and 10, Table 21.3.6.3.2-2)

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

Table 21.3.6.3.3-3: MeasConfig (Table 21.3.6.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.6.3.3-4: MeasurementReport (step 7, Table 21.3.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 21.3.6.3.3-5: MeasurementReport (step 14, Table 21.3.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 1
cgi-Info[1]	Not present
measResult[1] SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
}
}
}
}
}
}
}

Table 21.3.6.3.3-6: MBMSInterestIndication (step 3 and 18, Table 21.3.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
nonCriticalExtension SEQUENCE {			SC-PTM
mbms-Services-r13 SEQUENCE (SIZE (0..maxMBMS-ServiceListPerUE-r13)) OF SEQUENCE {
tmgi-r13 SEQUENCE {
plmn-Id-r9 CHOICE {
plmn-Index-r9	1
}
serviceId-r9	‘000001’H	OCTET STRING (SIZE (3))
}
}
}
}
}