17.1 MCCH Information Acquisition

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.1.1 MCCH information acquisition/ UE is switched on

17.1.1.1 Test Purpose (TP)

(1)

with { UE in switched off state and interested to receive MBMS services }

ensure that {

when { UE is switched on }

then { acquire the MBSFNAreaConfiguration message at the next repetition period }

}

17.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8.2.2 and 5.8.2.3.

[TS 36.331, clause 5.8.2.2]

A UE interested to receive MBMS services shall apply the MCCH information acquisition procedure upon entering the corresponding MBSFN area (e.g. upon power on, following UE mobility) and upon receiving a notification that the MCCH information has changed. A UE that is receiving an MBMS service shall apply the MCCH information acquisition procedure to acquire the MCCH, that corresponds with the service that is being received, at the start of each modification period.

Unless explicitly stated otherwise in the procedural specification, the MCCH information acquisition procedure overwrites any stored MCCH information, i.e. delta configuration is not applicable for MCCH information and the UE discontinues using a field if it is absent in MCCH information unless explicitly specified otherwise.

[TS 36.331, clause 5.5.2.3]

An MBMS capable UE shall:

1> if the UE enters an MBSFN area:

2> acquire the MBSFNAreaConfiguration message at the next repetition period;

17.1.1.3 Test description

17.1.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

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

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 4.6.1-4A is transmitted on MCCH

UE:

– E-UTRAN UE supporting MBMS services.

Preamble:

– UE is in state Switched OFF (state 1).

– Before being switched off the UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

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

17.1.1.3.2 Test procedure sequence

Table 17.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE is switched on.	–	–	–	–
2	The generic procedure described in TS 36.508 subclause 4.5.2A.3 is performed on Cell 1 to activate the UE test mode.	–		–	–
3	Void	–	–	–	–
4	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message	–	–	–	–
5	The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 1 activating UE test loop Mode C	–	–	–	–
–	Exception; Step 6 is repeated 5 times	–	–	–	–
6	The SS transmits 2 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000001’ in the first MAC PDU of the MCH Scheduling Period	<–	MBMS Packets.	–	–
7	Void	–	–	–	–
8	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
9	UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	–	–
10	Check: Is the number of reported MBMS Packets received on the MTCH in step 9 greater than zero?	–	–	1	P

17.1.1.3.3 Specific message contents

Table 17.1.1.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble and all steps, Table 17.1.1.3.2-1)

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

Table 17.1.1.3.3-2: ACTIVATE TEST MODE (step 2, Table 17.1.1.3.2-1)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C

Table 17.1.1.3.3-3: CLOSE UE TEST LOOP (step 5, Table 17.1.1.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C

17.1.2 MCCH information acquisition/ cell reselection to a cell in a new MBSFN area

17.1.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state and interested to receive MBMS services }

ensure that {

when { UE reselects to a cell in a new MBSFN area }

then { UE shall acquire the MBSFNAreaConfiguration message at the next repetition period }

}

17.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8.2.2 and 5.8.2.3.

[TS 36.331, clause 5.8.2.2]

[TS 36.331, clause 5.5.2.3]

An MBMS capable UE shall:

…

1> if the UE enters an MBSFN area:

2> acquire the MBSFNAreaConfiguration message at the next repetition period;

…

17.1.2.3 Test description

17.1.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 11 which belong to different MBSFN areas.

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

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 4.6.1-4A is transmitted on MCCH in Cell 1

– MBSFNAreaConfiguration as defined in table 17.1.2.3.3-4 is transmitted on MCCH in Cell 11

UE:

– E-UTRAN UE supporting MBMS services

Preamble:

– UE is in Registered, Idle mode, Test Mode Activated (State 2A) according to [18] in Cell 1(serving cell) with the UE TEST LOOP MODE C.

– The UE is made interested in receiving MBMS service in the PLMN of Cell 11 with MBMS Service ID 1.

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

17.1.2.3.2 Test procedure sequence

Table 17.1.2.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 "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.1.2.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 11	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	-91
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy R_{Cell 1} < R_{Cell 11.}

Table 17.1.2.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes Cell 11 level according to the row "T1" in table 17.1.2.3.2-1.	–	–	–	–
2	The UE executes the generic test procedure described in TS 36.508 subclause 6.4.2.7 and UE shall camp on E-UTRA Cell 11. NOTE: The UE performs a TAU procedure and the RRC connection is released.	–	–	–	–
3	Void	–
4	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message		–	–	–
5	The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 11 activating UE test loop Mode C.	–	–	–	–
–	Exception: Step 6 is repeated 5 times	–	–	–	–
6	The SS transmits 2 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000001’ in the first MAC PDU of the MCH Scheduling Period	<–	MBMS Packets.	–	–
7	Void	–	–	–	–
8	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message to set UE to Mode C.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
9	UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	–	–
10	Check: Is the number of reported MBMS Packets received on the MTCH in step 9 greater than zero?	–	–	1	P

17.1.2.3.3 Specific message contents

Table 17.1.2.3.3-1: SystemInformationBlockType2 for Cells 1 and 11 (preamble and all steps, Table 17.1.2.3.2-2)

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

Table 17.1.2.3.3-1a: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C.

Table 17.1.2.3.3-2: CLOSE UE TEST LOOP (step 5, Table 17.1.2.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C
Information Element	Value/remark	Comment	Condition
UE test loop mode C LB setup		MTCH ID
MBSFN area identity	0 0 0 0 0 0 0 1	1, same value as broadcasted in the default SystemInformationBlockType13 on Cell 11 (Table 17.1.2.3.3-3)

Table 17.1.2.3.3-3: SystemInformationBlockType13 (preamble and all steps Cell 11, Table 17.1.2.3.2-2)

Derivation Path: 36.508 Table 4.4.3.3-13
Information Element	Value/remark	Comment	Condition
MBSFN-AreaInfo-r9 SEQUENCE (SIZE(1..maxMBSFN-Area)) OF SEQUENCE {
mbsfn-AreaId-r9	1
}

Table 17.1.2.3.3-4: MBSFNAreaConfiguration (preamble and all steps Cell 11, Table 17.1.2.3.2-2)

Derivation Path: 36.508 Table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {
pmch-Config-r9 SEQUENCE {
dataMCS-r9	14
}
mbms-SessionInfoList-r9 SEQUENCE (SIZE (0..maxSessionPerPMCH)) OF SEQUENCE {
MBMS-SessionInfo-r9 SEQUENCE {
tmgi-r9 SEQUENCE {
serviceId-r9	‘000001’
}
}
}
}

17.1.3 MCCH information acquisition/ UE handover to a cell in a new MBSFN area

17.1.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC CONNECTED state and interested to receive MBMS services }

ensure that {

when { UE handovers to a cell in a new MBSFN area }

then { UE should acquire the MBSFNAreaConfiguration message at the next repetition period }

}

17.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8.2.2 and 5.8.2.3.

[TS 36.331, clause 5.8.2.2]

A UE interested to receive MBMS services shall apply the MCCH information acquisition procedure upon entering the corresponding MBSFN area (e.g. upon power on, following UE mobility) and upon receiving a notification that the MCCH information has changed. A UE that is receiving an MBMS service shall apply the MCCH information acquisition procedure to acquire the MCCH that corresponds with the service that is being received, at the start of each modification period.

[TS 36.331, clause 5.5.2.3]

An MBMS capable UE shall:

…

1> if the UE enters an MBSFN area:

2> acquire the MBSFNAreaConfiguration message at the next repetition period;

…

17.1.3.3 Test description

17.1.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2 which belong to different MBSFN areas.

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

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 4.6.1-4A is transmitted on MCCH in Cell 1.

– MBSFNAreaConfiguration as defined in table 17.1.3.3.3-1ab is transmitted on MCCH in Cell 2

UE:

– E-UTRAN UE supporting MBMS 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 C.

– The UE is made interested in receiving MBMS service in the PLMN of Cell 2 with MBMS Service ID 1.

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

17.1.3.3.2 Test procedure sequence

Table 17.1.3.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 "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.1.3.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 4 (M4) satisfy exit condition for event A3 (M4 < M1) (NOTE 1).
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are such that measurement results for Cell 1 (M1) and Cell 4 (M4) satisfy entry condition for event A3 (M4 > M1) (NOTE 1).

Table 17.1.3.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message to setup intra frequency measurement on Cell 1.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the setup of intra frequency measurement.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS changes Cell 1, Cell 2 parameters according to the row "T1" in table 17.1.3.3.2-1.	–	–	–	–
4	The UE transmits a MeasurementReport message to report event A3 on Cell 1 with the measured RSRP, RSRQ value for Cell 2.	–>	MeasurementReport	–	–
5	The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2.	<–	RRCConnectionReconfiguration	–	–
6	UE transmits an RRCConnectionReconfigurationComplete message on Cell 2	–>	RRCConnectionReconfigurationComplete	–	–
7	Void	–	–	–	–
8	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message		–
8A	The generic procedures described in TS 36.508 subclause 4.5.4.3 are performed on Cell 2 activating UE test loop Mode C.	–	–	–	–
–	Exception: Step 9 is repeated 5 times	–	–	–	–
9	The SS transmits 2 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000001’ in the first MAC PDU of the MCH Scheduling Period	<–	MBMS Packets.	–	–
10	Void	–	–	–	–
11	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message to set UE to Mode C.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
12	UE responds with UE TEST LOOP MODE 3 MBMS PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	–	–
13	Check: Is the number of reported MBMS Packets received on the MTCH in step 12 greater than zero?	–	–	1	P

17.1.3.3.3 Specific message contents

Table 17.1.3.3.3-1: SystemInformationBlockType2 for Cells 1 and 2 (preamble and all steps, Table 17.1.3.3.2-2)

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

Table 17.1.3.3.3-1a: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C.

Table 17.1.3.3.3-1aa: SystemInformationBlockType13 (preamble and all steps Cell 2, Table 17.1.3.3.2-2)

Derivation Path: 36.508 Table 4.4.3.3-13
Information Element	Value/remark	Comment	Condition
MBSFN-AreaInfo-r9 SEQUENCE (SIZE(1..maxMBSFN-Area)) OF SEQUENCE {
mbsfn-AreaId-r9	1
}

Table 17.1.3.3.3-1ab: MBSFNAreaConfiguration (preamble and all steps Cell 2, Table 17.1.3.3.2-2)

Derivation Path: 36.508 Table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {
pmch-Config-r9 SEQUENCE {
dataMCS-r9	1
}
mbms-SessionInfoList-r9 SEQUENCE (SIZE (0..maxSessionPerPMCH)) OF SEQUENCE {
MBMS-SessionInfo-r9 SEQUENCE {
tmgi-r9 SEQUENCE {
serviceId-r9	‘000001’
}
}
}
}

Table 17.1.3.3.3-2: Void

Table 17.1.3.3.3-1b: CLOSE UE TEST LOOP (step 8A, Table 17.1.3.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C.
Information Element	Value/remark	Comment	Condition
UE test loop mode C LB setup		MTCH ID
MBSFN area identity	0 0 0 0 0 0 0 1	1, same value as broadcasted in the default SystemInformationBlockType13 on Cell 2 (Table 17.1.3.3.3-1aa)

Table 17.1.3.3.3-2: RRCConnectionReconfiguration (step 1, Table 17.1.3.3.2-2)

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

Table 17.1.3.3.3-3: MeasConfig (Table 17.1.3.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	If band > 64 is selected

Table 17.1.3.3.3-4: MeasurementReport (step 4, Table 17.1.3.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 2
cgi-Info[1]	Not present
measResult[1] SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
}
}
}
}
}
}
}

Table 17.1.3.3.3-5: RRCConnectionReconfiguration (step 5, Table 17.1.3.3.2-2)

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

Table 17.1.3.3.3-6: MobilityControlInfo (step 5, Table 17.1.3.3.2-5)

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
}

17.1.4 MCCH information acquisition/ UE is receiving an MBMS service

17.1.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state }

ensure that {

when { UE is receiving an MBMS service }

then { UE shall start acquiring the MBSFNAreaConfiguration message that corresponds with the service that is being received, from the beginning of each modification period }

}

17.1.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8.2.2 and 5.8.2.3.

[TS 36.331, clause 5.8.2.2]

A UE interested to receive MBMS services shall apply the MCCH information acquisition procedure upon entering the corresponding MBSFN area (e.g. upon power on, following UE mobility) and upon receiving a notification that the MCCH information has changed. A UE that is receiving an MBMS service shall apply the MCCH information acquisition procedure to acquire the MCCH that corresponds with the service that is being received, at the start of each modification period.

[TS 36.331, clause 5.5.2.3]

An MBMS capable UE shall:

…

1> if the UE is receiving an MBMS service:

2> start acquiring the MBSFNAreaConfiguration message, that corresponds with the service that is being received, from the beginning of each modification period;

17.1.4.3 Test description

17.1.4.3.1 Pre-test conditions

System Simulator:

– Cell 1

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

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 4.6.1-4A is transmitted on MCCH

UE:

– E-UTRAN UE supporting MBMS services.

Preamble:

– UE is in Registered, Idle mode, Test Mode Activated (State 2A) according to [18] in Cell 1(serving cell) with the UE TEST LOOP MODE C.

– The UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

17.1.4.3.2 Test procedure sequence

Table 17.1.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits MBSFNAreaConfiguration message	<–	MBSFNAreaConfiguration	–	–
2	Wait for a period equal to the MCCH modification period for the UE to receive MBSFNAreaConfiguration message	–	–	–	–
2A	The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 1 closing UE test loop Mode C	–	–	–	–
–	Exception: Step 3 is repeated 5 times	–	–	–	–
3	The SS transmits 2 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000001’ in the first MAC PDU of the MCH Scheduling Period	–	MBMS Packets.	–	–
4	Void	–	–	–	–
4A	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
4B	UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	–	–
4C	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease	–	–
5	SS transmits an updated system information [contents different from preamble]	–	–	–	–
6	SS transmits MBSFNAreaConfiguration message at the beginning of next modification period MPa.	<–	MBSFNAreaConfiguration	–	–
7	Wait until the start of the next modification period MPa for the duration of one repetition period for the UE to receive MBSFNAreaConfiguration message	–	–	–	–
8	Void	–	–	–	–
–	Exception: Step 9 is repeated 2 times	–	–	–	–
9	The SS transmits 5 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000100’ in the first MAC PDU of the MCH Scheduling Period	<–	MBMS Packets.	–	–
10	Void	–	–	–	–
10A	Steps 2 to 7 of the generic procedure described in TS 36.508 subclause 4.5.3A.3 are performed on Cell 1	–	–	–	–
10B	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context	<–	RRC: RRCConnectionReconfiguration	–	–
10C	The UE transmits an RRCConnectionReconfigurationComplete message	–>	RRC: RRCConnectionReconfigurationComplete	–	–
11	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
12	UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	–	–
13	Check: Is the number of reported MBMS Packets received on the MTCH in step 12 greater than the value reported in step 4B?	–	–	1	P
Note: The checking of UE received MBMS packets in steps 4B and 12 is to verify that MBMS reception is ongoing before and after the MBMS area configuration change in step 6.

17.1.4.3.3 Specific message contents

Table 17.1.4.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble)

Derivation Path: 36.508 table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
mbsfn-SubframeConfiguration SEQUENCE {
radioframeAllocationPeriod	n4
radioframeAllocationOffset	1		FDD
	0		TDD
subframeAllocation CHOICE{
oneFrame	‘110000’		FDD
	‘010010’		TDD
}
}
}

Table 17.1.4.3.3-1a: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C.

Table 17.1.4.3.3-2: SystemInformationBlockType2 for Cell 1 (step 5, Table 17.1.4.3.2-1)

Derivation Path: 36.508 table 4.4.3.3-1, condition MBMS.
Information Element	Value/remark	Comment	Condition

Table 17.1.4.3.3-3: MBSFNAreaConfiguration (step 6, Table 17.1.4.3.2-1)

Derivation Path: 36.508 table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
commonSF-Alloc-r9 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {
commonSF-AllocPeriod-r9	rf32
pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {
pmch-Config-r9 SEQUENCE {
sf-AllocEnd-r9	7
dataMCS-r9	1
mch-SchedulingPeriod-r9	rf32
}
}
}
}

Table 17.1.4.3.3-4: CLOSE UE TEST LOOP (step 2A, Table 17.1.4.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C

Table 17.1.4.3.3-5: RRCConnectionReconfiguration (step 10B, Table 17.1.4.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(2, 0)
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF	Not present
}
}
}
}

17.1.5 MCCH information acquisition/ UE is not receiving MBMS data

17.1.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state and interested to receive MBMS services }

ensure that {

when { UE is not receiving an MBMS service and receives MCCH information change notification }

then { UE shall start acquiring the MBSFNAreaConfiguration message from the beginning of the modification period following the one in which the change notification was received }

}

17.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8.2.2 and 5.8.2.3.

[TS 36.331, clause 5.8.2.2]

A UE interested to receive MBMS services shall apply the MCCH information acquisition procedure upon entering the corresponding MBSFN area (e.g. upon power on, following UE mobility) and upon receiving a notification that the MCCH information has changed. A UE that is receiving an MBMS service shall apply the MCCH information acquisition procedure to acquire the MCCH that corresponds with the service that is being received, at the start of each modification period.

[TS 36.331, clause 5.5.2.3]

An MBMS capable UE shall:

1> if the procedure is triggered by a MCCH information change notification:

2> start acquiring the MBSFNAreaConfiguration message from the beginning of the modification period following the one in which the change notification was received;

NOTE 1: The UE continues using the previously received MCCH information until the new MCCH information has been acquired.

17.1.5.3 Test description

17.1.5.3.1 Pre-test conditions

System Simulator:

– Cell 1 belongs to MBSFN area

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

– MBSFNAreaConfiguration as defined in Table 17.1.5.3.3-1b is transmitted on MCCH in Cell 1

UE:

– E-UTRAN UE supporting MBMS services.

Preamble:

– UE is in Registered, Idle mode, Test Mode Activated (State 2A) according to [18] in Cell 1(serving cell) with the UE TEST LOOP MODE C.

The UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

17.1.5.3.2 Test procedure sequence

Table 17.1.5.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits MCCH information change notification in modification period MPa.	–	(MCCH information change notification)	–	–
1A	SS transmits the updated MBSFNAreaConfiguration message from the beginning of next modification period (MPa+1).	<–	MBSFNAreaConfiguration	–	–
2	Wait for a period equal to the MCCH modification period for the UE to receive MBSFNAreaConfiguration message from the beginning of the modification period (MPa+1)	–	–	–	–
3	The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 1 to close UE test loop	–	–	–	–
–	Exception: Step 4 is repeated 2 times	–	–	–	–
4	The SS transmits 8 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000111’ in the first MAC PDU of the MCH Scheduling Period	<–	MBMS Packets	–	–
5	Void	–	–	–	–
6	Void	–	–	–	–
7	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
8	UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	–	–
9	Check: Is the number of reported MBMS Packets received on the MTCH in step 8 greater than zero?	–	–	1	P

17.1.5.3.3 Specific message contents

Table 17.1.5.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble and all steps, Table 17.1.5.3.2-2)

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

Table 17.1.5.3.3-1a: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C.

Table 17.1.5.3.3-1b: MBSFNAreaConfiguration (preamble)

Derivation Path: 36.508 table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
commonSF-Alloc-r9 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {
commonSF-AllocPeriod-r9	rf32
pmch-InfoList-r9 SEQUENCE {}		No entry
}
}

Table 17.1.5.3.3-2: MBSFNAreaConfiguration (steps 1A, Table 17.1.5.3.2-2)

Derivation Path: 36.508 table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
commonSF-Alloc-r9 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {
commonSF-AllocPeriod-r9	rf32
pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {
pmch-Config-r9 SEQUENCE {
sf-AllocEnd-r9	7
dataMCS-r9	0
mch-SchedulingPeriod-r9	rf32
}
}
}
}

Table 17.1.5.3.3-3: CLOSE UE TEST LOOP (step 3, Table 17.1.5.3.2-2)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C