21.1 SC-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

(…)

21.1.1 SC-MCCH information acquisition/ UE is switched on

21.1.1.1 Test Purpose (TP)

(1)

with { UE in switched off state and interested to receive MBMS services via SC-MRB }

ensure that {

when { UE is switched on }

then { acquire the SCPTM-Configuration message at the next repetition period }

}

21.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8a.2.2 and 5.8a.2.3.

[TS 36.331, clause 5.8a.2.2]

A UE interested to receive MBMS services via SC-MRB shall apply the SC-MCCH information acquisition procedure upon entering the cell broadcasting SystemInformationBlockType20 (e.g. upon power on, following UE mobility) and upon receiving a notification that the SC-MCCH information has changed. A UE that is receiving an MBMS service via SC-MRB shall apply the SC-MCCH information acquisition procedure to acquire the SC-MCCH information 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 SC-MCCH information acquisition procedure overwrites any stored SC-MCCH information, i.e. delta configuration is not applicable for SC-MCCH information and the UE discontinues using a field if it is absent in SC-MCCH information unless explicitly specified otherwise.

[TS 36.331, clause 5.8a.2.3]

A SC-PTM capable UE shall:

…

1> if the UE enters a cell broadcasting SystemInformationBlockType20:

2> acquire the SCPTM-Configuration message at the next repetition period;

…

21.1.1.3 Test description

21.1.1.3.1 Pre-test conditions

System Simulator:

– Cell 1.

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

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

UE:

– E-UTRAN UE supporting SC-PTM 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 1.

21.1.1.3.2 Test procedure sequence

Table 21.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	Wait for a period equal to the SC-MCCH repetition period for the UE to receive SCPTMConfiguration message.	–	–	–	–
4	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 F.	–	–	–	–
–	Exception; Step 5 is repeated 5 times.	–	–	–	–
5	The SS transmits 2 MBMS Packets on the SC-MTCH.	<–	MBMS Packets.	–	–
6	The SS transmits an UE TEST LOOP MODE F SC-PTM PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE F SC-PTM PACKET COUNTER REQUEST	–	–
7	UE responds with UE TEST LOOP MODE F SC-PTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SC-PTM PACKET COUNTER RESPONSE	–	–
8	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 7 greater than zero?	–	–	1	P

21.1.1.3.3 Specific message contents

Table 21.1.1.3.3-1: ACTIVATE TEST MODE (step 2, Table 21.1.1.3.2-1)

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

Table 21.1.1.3.3-2: CLOSE UE TEST LOOP (step 4, Table 21.1.1.3.2-1)

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

21.1.2 SC-MCCH information acquisition/ cell reselection to a cell broadcasting SIB20

21.1.2.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE reselects to a cell broadcasting SIB20 }

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

}

21.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8a.2.2 and 5.8a.2.3.

[TS 36.331, clause 5.8a.2.2]

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

[TS 36.331, clause 5.8a.2.3]

A SC-PTM capable UE shall:

…

1> if the UE enters a cell broadcasting SystemInformationBlockType20:

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

…

21.1.2.3 Test description

21.1.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

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

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

UE:

– E-UTRAN UE supporting SC-PTM 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 F.

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

21.1.2.3.2 Test procedure sequence

Table 21.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 the column 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.1.2.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
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-79	The power level values are assigned to satisfy R_{Cell 1} < R_{Cell 2.}

Table 21.1.2.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes Cell 2 level according to the row "T1" in table 21.1.2.3.2-1.	–	–	–	–
2	The UE executes the generic test procedure described in TS 36.508 subclause 6.4.2.2 and UE shall camp on E-UTRA Cell 2.	–	–	–	–
3	Wait for a period equal to the SC-MCCH repetition period for the UE to receive SCPTMConfiguration message.		–	–	–
4	The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 2 activating UE test loop Mode F.	–	–	–	–
–	Exception: Step 5 is repeated 5 times	–	–	–	–
5	The SS transmits 2 MBMS Packets on the SC-MTCH.	<–	MBMS Packets.	–	–
6	The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message to set UE to Mode F.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
7	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
8	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 7 greater than zero?	–	–	1	P

21.1.2.3.3 Specific message contents

Table 21.1.2.3.3-1: ACTIVATE TEST MODE (preamble)

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

Table 21.1.2.3.3-2: CLOSE UE TEST LOOP (step 4, Table 21.1.2.3.2-2)

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

21.1.3 SC-MCCH information acquisition/ UE handover to a cell broadcasting SIB20

21.1.3.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE handovers to a cell broadcasting SIB20 }

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

}

21.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8a.2.2 and 5.8a.2.3.

[TS 36.331, clause 5.8a.2.2]

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

[TS 36.331, clause 5.8a.2.3]

A SC-PTM capable UE shall:

…

1> if the UE enters a cell broadcasting SystemInformationBlockType20:

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

…

21.1.3.3 Test description

21.1.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

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

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

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 2 with MBMS Service ID 1.

21.1.3.3.2 Test procedure sequence

Table 21.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" 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.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 2 (M2) satisfy exit condition for event A3 (M2 < 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 2 (M2) satisfy entry condition for event A3 (M2 > M1) (NOTE 1).

Table 21.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 21.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	Wait for a period equal to the SC-MCCH repetition period for the UE to receive SCPTMConfiguration message		–
8	The generic procedures described in TS 36.508 subclause 4.5.4.3 are performed on Cell 2 activating UE test loop Mode F.	–	–	–	–
–	Exception: Step 9 is repeated 5 times	–	–	–	–
9	The SS transmits 2 MBMS Packets on the SC-MTCH.	<–	MBMS Packets.	–	–
10	The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message to set UE to Mode F.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
11	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
12	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 11 greater than zero?	–	–	1	P

21.1.3.3.3 Specific message contents

Table 21.1.2.3.3-0: Conditions for specific message contents
in Tables 21.1.2.3.3-3 and Table 21.1.3.3.3-6

Condition	Explanation
Band > 64	This condition applies if the band number is bigger than 64.
Band 24 High range	If Band 24 high frequency range is selected for the target cell

Table 21.1.3.3.3-1: ACTIVATE TEST MODE (preamble)

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

Table 21.1.3.3.3-2: RRCConnectionReconfiguration (step 1, Table 21.1.3.3.2-2)

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

Table 21.1.3.3.3-3: MeasConfig (Table 21.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 {	1 entry		Band > 64
measObjectEUTRA-v9e0[1] SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
}
}

Table 21.1.3.3.3-4: MeasurementReport (step 4, Table 21.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 21.1.3.3.3-5: RRCConnectionReconfiguration (step 5, Table 21.1.3.3.2-2)

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

Table 21.1.3.3.3-6: MobilityControlInfo (Table 21.1.3.3.3-5)

Derivation Path: 36.508, Table 4.6.5-1
Information Element	Value/remark	Comment	Condition
MobilityControlInfo ::= SEQUENCE {
targetPhysCellId	PhysicalCellIdentity of Cell 2
carrierFreq SEQUENCE {
dl-CarrierFreq	Same downlink EARFCN as used for Cell 2
ul-CarrierFreq	Not present
	Same uplink EARFCN as used for Cell 2		Band 24 High range
}
carrierFreq	Not present		Band > 64
carrierFreq-v9e0 SEQUENCE {			Band > 64
dl-CarrierFreq-v9e0	Same downlink EARFCN as used for Cell 2
}
}

Table 21.1.3.3.3-7: CLOSE UE TEST LOOP (step 8, Table 21.1.3.3.2-2)

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

21.1.4 SC-MCCH information acquisition/ UE is receiving an SC-PTM service

21.1.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state }

ensure that {

when { UE is receiving an SC-PTM service }

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

}

21.1.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8a.2.2 and 5.8a.2.3.

[TS 36.331, clause 5.8a.2.2]

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

[TS 36.331, clause 5.8a.2.3]

An SC-PTM capable UE shall:

…

1> if the UE is receiving an MBMS service via an SC-MRB:

2> start acquiring the SCPTMConfiguration message from the beginning of each modification period.

…

21.1.4.3 Test description

21.1.4.3.1 Pre-test conditions

System Simulator:

– Cell 1.

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

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

UE:

– E-UTRAN UE supporting SC-PTM 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 F.

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

21.1.4.3.2 Test procedure sequence

Table 21.1.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits SCPTMConfiguration message.	<–	SCPTMConfiguration	–	–
2	Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration message.	–	–	–	–
3	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 F.	–	–	–	–
–	Exception: Step 4 is repeated 2 times	–	–	–	–
4	The SS transmits 5 MBMS Packets on the SC-MTCH.	–	MBMS Packets.	–	–
5	The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
6	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
7	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 7 greater than zero?	–	–	1	P
8	SS performs procedures on opening UE test loop Mode F and then closing it again for the g-RNTI defined in step 10
9	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease	–	–
10	SS transmits an updated SCPTMConfiguration message, at the beginning of next modification period MPa.	<–	SCPTMConfiguration	–	–
11	Wait for the duration of one repetition period for the UE to receive SCPTMConfiguration message.	–	–	–	–
–	Exception: Step 12 is repeated 2 times	–	–	–	–
12	The SS transmits 5 MBMS Packets on the SC-MTCH.	<–	MBMS Packets.	–	–
13	Steps 2 to 7 of the generic procedure described in TS 36.508 subclause 4.5.3A.3 are performed on Cell 1.	–	–
14	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context.	<–	RRC: RRCConnectionReconfiguration
15	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
16	The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
17	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
18	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 17 greater than zero?	–	–	1	P
Note: The checking of UE received MBMS packets in steps 7 and 18 is to verify that SC-PTM reception is ongoing before and after the SCPTMconfiguration change in step 10.

21.1.4.3.3 Specific message contents

Table 21.1.4.3.3-1: ACTIVATE TEST MODE (preamble)

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

Table 21.1.4.3.3-2: CLOSE UE TEST LOOP (step 3, Table 21.1.4.3.2-1)

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

Table 21.1.4.3-3: CLOSE UE TEST LOOP (step 8, Table 21.1.4.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE F
Information Element	Value/remark	Comment	Condition
UE test loop mode F setup		SC-MCCH ID
g-RNTI	‘0200’H

Table 21.1.4.3.3-4: SCPTMConfiguration for Cell 1 (step 10, Table 21.1.4.3.2-1)

Derivation Path: 36.508 table 4.6.1-18a
Information Element	Value/remark	Comment	Condition
SCPTMConfiguration-r13 ::= SEQUENCE {
sc-mtch-InfoList-r13 SEQUENCE (SIZE (0..maxSC-MTCH-r13)) OF SEQUENCE {
g-RNTI-r13	‘0200’H

Table 21.1.4.3.3-5: RRCConnectionReconfiguration (step 14, Table 21.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
}
}
}
}

21.1.5 SC-MCCH information acquisition/ UE is not receiving SC-PTM data

21.1.5.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE is not receiving an SC-PTM service and receives SC-MCCH information change notification }

then { UE shall start acquiring the SCPTMConfiguration message from the subframe where the change notification was received }

}

21.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8a.2.2 and 5.8a.2.3.

[TS 36.331, clause 5.8a.2.2]

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

[TS 36.331, clause 5.8a.2.3]

An SC-PTM capable UE shall:

1> if the procedure is triggered by an SC-MCCH information change notification:

2> start acquiring the SCPTMConfiguration message from the subframe where the change notification was received;

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

21.1.5.3 Test description

21.1.5.3.1 Pre-test conditions

System Simulator:

– Cell 1.

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

– 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 Registered, Idle mode, Test Mode Activated (State 2A) 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 0.

21.1.5.3.2 Test procedure sequence

Table 21.1.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits updated SCPTMConfiguration and SC-MCCH information change notification from the beginning of next modification period MPa.	–	SCPTMConfiguration (MCCH information change notification)	–	–
2	Void	–	–	–	–
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 F	–	–	–	–
–	Exception: Step 4 is repeated 2 times	–	–	–	–
4	The SS transmits 8 MBMS Packets on the SC-MTCH	<–	MBMS Packets	–	–
5	The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
6	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
7	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 6 greater than zero?	–	–	1	P

21.1.5.3.3 Specific message contents

Table 21.1.5.3.3-1: ACTIVATE TEST MODE (preamble)

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

Table 21.1.5.3.3-2: SystemInformationBlockType20 (preamble)

Derivation Path: 36.331 clause 6.3.1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType20-r13 ::= SEQUENCE {
sc-mcch-RepetionPeriod-r13	Rf64
sc-mcch-Offset-r13	1
sc-mcch-FirstSubframe-r13	0
sc-mcch-duration-r13	2
sc-mcch-ModificationPeriod-r13	Rf512
lateNonCriticalExtension
}

Table 21.1.5.3.3-3: SCPTMConfiguration for Cell 1 (step 1, Table 21.1.5.3.2-1)

Derivation Path: 36.508 table 4.6.1-18a
Information Element	Value/remark	Comment	Condition
SCPTMConfiguration-r13 ::= SEQUENCE {
sc-mtch-InfoList-r13 SEQUENCE (SIZE (0..maxSC-MTCH-r13)) OF SEQUENCE {
mbmsSessionInfo-r13 SEQUENCE {
tmgi-r13 SEQUENCE {
plmn-Id-r9 CHOICE {
plmn-Index-r9	1
}
}
serviceId-r9	‘000000’H	OCTET STRING (SIZE (3))
}
sessionId-r13	Not present
}
g-RNTI-r13	‘0200’H

Table 21.1.5.3.3-4: CLOSE UE TEST LOOP (step 3, Table 21.1.5.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 F setup		SC-MCCH ID
g-RNTI	‘0200’H

21.1.6 SC-MCCH information acquisition / Enhanced Coverage

21.1.6.1 Test Purpose (TP)

(1)

with { Enhanced Coverage Capable UE in E-UTRAN RRC IDLE state }

ensure that {

when { UE is receiving SC-PTM service }

then { { UE shall start acquiring the SCPTMConfiguration message at the start of the next modification period upon receiving a notification that the SC-MCCH information that corresponds with the service that is being received is about to be changed }

}

21.1.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.8a.1.3 and 5.8.2.

[TS 36.331, clause 5.8a.1.3]

…

When the network changes (some of) the SC-MCCH information for start of new MBMS service(s) transmitted using SC-PTM, it notifies BL UEs, UEs in CE or NB-IoT UEs about the change in every PDCCH which schedules the first SC-MCCH in a repetition period in the current modification period. The notification is transmitted with 1 bit. The bit, when set to ‘1’, indicates the start of new MBMS service(s), see TS 36.212 [22, 5.3.3.1.14 & 6.4.3.3]. Upon receiving a change notification, a BL UE, UE in CE or NB-IoT UE interested to receive MBMS services transmitted using SC-PTM acquires the new SC-MCCH information scheduled by the PDCCH. The BL UE, UE in CE or NB-IoT UE applies the previously acquired SC-MCCH information until the BL UE, UE in CE or NB-IoT UE acquires the new SC-MCCH information.

…

[TS 36.331, clause 5.8.2]

…

The UE applies the SC-MCCH information acquisition procedure to acquire the SC-PTM control information that is broadcast by the E-UTRAN. The procedure applies to SC-PTM capable UEs that are in RRC_IDLE. This procedure also applies to SC-PTM capable UEs that are in RRC_CONNECTED except for BL UEs, UEs in CE or NB-IoT UEs.

…

A UE interested to receive MBMS services via SC-MRB shall apply the SC-MCCH information acquisition procedure upon entering the cell broadcasting SystemInformationBlockType20 (SystemInformationBlockType20-NB in NB-IoT) (e.g. upon power on, following UE mobility) and upon receiving a notification that the SC-MCCH information has changed. A UE, except for BL UE, UE in CE or NB-IoT UE, that is receiving an MBMS service via SC-MRB shall apply the SC-MCCH information acquisition procedure to acquire the SC-MCCH information that corresponds with the service that is being received, at the start of each modification period. The BL UE, UE in CE or NB-IoT UE that is receiving an MBMS service via SC-MRB shall apply the SC-MCCH information acquisition procedure upon receiving a notification that the SC-MCCH information that corresponds with the service that is being received is about to be changed. The BL UE, UE in CE or NB-IoT UE that is receiving an MBMS service via SC-MRB may apply the SC-MCCH information acquisition procedure upon receiving a notification that the SC-MCCH information is about to be changed due to start of a new service.

…

A SC-PTM capable UE shall:

1> if the procedure is triggered by an SC-MCCH information change notification and the UE has no ongoing MBMS service:

2> except for a BL UE, UE in CE or NB-IoT UE, start acquiring the SCPTMConfiguration message from the subframe in which the change notification was received;

2> for a BL UE, UE in CE or NB-IoT UE, acquire the SCPTMConfiguration message scheduled by the PDCCH in which the change notification was received;

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

1> if the UE enters a cell broadcasting SystemInformationBlockType20 (SystemInformationBlockType20-NB in NB-IoT):

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

1> if the UE is receiving an MBMS service via an SC-MRB:

2> except for BL UE, UE in CE or NB-IoT UE, start acquiring the SCPTMConfiguration message from the beginning of each modification period;

2> a BL UE, UE in CE or NB-IoT UE shall start acquiring the SCPTMConfiguration message at the start of the next modification period upon receiving a notification that the SC-MCCH information that corresponds with the service that is being received is about to be changed;

2> a BL UE, UE in CE or NB-IoT UE may start acquiring the SCPTMConfiguration message at the start of the next modification period upon receiving a notification that the SC-MCCH information is about to be changed due to start of a new service;

…

21.1.6.3 Test description

21.1.6.3.1 Pre-test conditions

System Simulator:

– Cell 1.

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

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

UE:

– E-UTRAN UE supporting Enhanced Coverage and SC-PTM 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 F.

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

21.1.6.3.2 Test procedure sequence

Table 21.1.6.3.2-1: Main Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits SCPTMConfiguration-BR message.	<–	SCPTMConfiguration-BR	–	–
2	Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration-BR message	–	–	–	–
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 F	–	–	–	–
–	Exception: Step 4 is repeated 2 times	–	–	–	–
4	The SS transmits 5 MBMS Packets on the SC-MTCH.	<–	MBMS Packets.	–	–
5	The SS transmits a UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
6	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
7	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 6 greater than zero?	–	–	–	–
8	SS procedures on opening UE test loop Mode F and then closing it again for the G-RNTI defined in step 11	–	–	–	–
9	The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.	<–	RRC: RRCConnectionRelease	–	–
10	SS transmits updated SCPTMConfiguration-BR and SC-MCCH information change notification from the next modification period.	<–	SCPTMConfiguration-BR (SC-MCCH information change notification)	–	–
11	Wait for a period equal to the SC-MCCH modification period for the UE to receive the SCPTMConfiguration-BR message	–	–	–	–
–	Exception: Step 12 is repeated 2 times	–	–	–	–
12	The SS transmits 5 MBMS Packets on the SC-MTCH	<–	MBMS Packets	–	–
13	Steps 2 -7 of the generic procedures described in TS 36.508 subclause 4.5.3A.3 are performed on Cell 1.	–	–	–	–
14	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context.	<–	RRC: RRCConnectionReconfiguration	–	–
15	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete	–	–
16	The SS transmits a UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
17	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
18	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 17 greater than zero?	–	–	1	P
Note: The checking of UE received MBMS packets in steps 7 and 15 is to verify that SC-PTM reception is ongoing before and after the SCPTMconfiguration change in step 10.

21.1.6.3.3 Specific message contents

Table 21.1.6.3.3-1: SystemInformationBlockType20 for Cell 1 (all steps, Table 21.1.6.3.2-1)

Derivation Path: 36.508 table 4.4.3.3-18
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType20-r13 ::= SEQUENCE {
br-BCCH-Config-r14 SEQUENCE {
dummy	rf1
dummy2	rf1
mpdcch-Narrowband-SC-MCCH-r14	1
mpdcch-NumRepetition-SC-MCCH-r14	r1
mpdcch-StartSF-SC-MCCH-r14 CHOICE {
fdd-r14	v1		FDD
tdd-r14	v1		TDD
}
mpdcch-PDSCH-HoppingConfig-SC-MCCH-r14	off
sc-mcch-CarrierFreq-r14	Same frequency as Cell 1
sc-mcch-Offset-BR-r14	0
sc-mcch-RepetitionPeriod-BR-r14	rf32
sc-mcch-ModificationPeriod-BR-r14	Rf512
}
sc-mcch-SchedulingInfo-r14	Not present
pdsch-maxNumRepetitionCEmodeA-SC-MTCH-r14	Not present
pdsch-maxNumRepetitionCEmodeA-SC-MTCH-r14	r32		CE-ModeA
pdsch-maxNumRepetitionCEmodeB-SC-MTCH-r14	Not present
pdsch-maxNumRepetitionCEmodeB-SC-MTCH-r14	r512		CE-ModeB
sc-mcch-RepetitionPeriod-v1470	Not present
sc-mcch-ModificationPeriod-v1470	Not present
}

Table 21.1.6.3.3-1: ACTIVATE TEST MODE (preamble)

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

Table 21.1.6.3.3-2: CLOSE UE TEST LOOP (step 3, Table 21.1.6.3.2-1)

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

Table 21.1.4.3-3: CLOSE UE TEST LOOP (step 8, Table 21.1.4.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE F
Information Element	Value/remark	Comment	Condition
UE test loop mode F setup		SC-MCCH ID
g-RNTI	‘0200’H

Table 21.1.4.3-4: SCPTMConfiguration-BR (step 11, Table 21.1.4.3.2-1)

Derivation Path: 36.508, Table 4.6.1-18b
Information Element	Value/remark	Comment	Condition
SCPTMConfiguration-BR-r14 ::= SEQUENCE {		SC-MCCH ID
sc-mtch-InfoList-r14 SEQUENCE (SIZE (0..maxSC-MTCH-BR-r14)) OF SEQUENCE {
g-RNTI-r14	‘0200’H
}
}

21.1.7 SC-MCCH information acquisition / Enhanced Coverage / Paging precedence

21.1.7.1 Test Purpose (TP)

(1)

with { Enhanced Coverage Capable UE in E-UTRAN RRC IDLE state and is receiving an SC-PTM service }

ensure that {

when { UE is paged }

then { UE responds to paging }

}

21.1.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 36.304 cl. 6.2.

[TS 36.304, clause 6.2]

A UE, except for BL UE or UE in enhanced coverage or NB-IoT UE, interested to receive MBMS services provided using MBSFN transmission shall apply the MCCH information acquision procedure as specified in [3] to receive the MCCH information upon entering the corresponding MBSFN area and upon receiving a notification that the MCCH information has changed. A UE interested to receive MBMS services provided using MBSFN transmission identifies if a service that it is interested to receive is started or ongoing by receiving the MCCH information, and then receives a MTCH corresponding to the identified service.

A UE interested to receive MBMS services provided using SC-PTM transmission shall apply the SC-MCCH information acquisition procedure as specified in [3] to receive the SC-MCCH information upon entering a new cell and upon receiving a notification that the SC-MCCH information has changed. A UE interested to receive MBMS services provided using SC-PTM transmission identifies if a service that it is interested to receive is started or ongoing by receiving the SC-MCCH information, and then receives a SC-MTCH configured using the SC-MRB establishment procedure in [3] and using the DL-SCH reception and SC-PTM DRX procedure as specified in [30].

For BL UE or UE in enhanced coverage or NB-IoT UE interested to receive MBMS services provided using SC-PTM transmission, in case of conflict, reception of paging or establishment of a RRC connection for Mobile Terminated Call and Mobile Originated Signalling takes precedence over SC-PTM reception.

21.1.7.3 Test description

21.1.7.3.1 Pre-test conditions

System Simulator:

– Cell 1.

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

– SCPTMConfiguration-BR as defined in TS 36.508[18] table 4.6.1-18b is transmitted on SC-MCCH

UE:

– E-UTRAN UE supporting Enhanced Coverage and SC-PTM services

Preamble:

– UE is in Registered, Idle mode, Test Mode Activated (State 2A-CE) 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.

21.1.7.3.2 Test procedure sequence

Table 21.1.7.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits SCPTMConfiguration-BR message.	<–	SCPTMConfiguration-BR	–	–
2	Wait for a period equal to the SC-MCCH modification period for the UE to receive SCPTMConfiguration-BR message.	–	–	–	–
3	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 F.	–	–	–	–
4	The SS transmits an RRCConnectionRelease message to release RRC connection	<–	RRC: RRCConnectionRelease	–	–
–	EXCEPTION: Step 5 is repeated 2 times	–	–	–	–
5	The SS transmits 5 MBMS Packets on the SC-MTCH.	–	MBMS Packets.	–	–
–	EXCEPTION: In parallel to the events described in steps 6-8, the Step 5 specified above is repeated 2 times.	–	–	–	–
6	Steps 2 to 7 of the generic procedure described in TS 36.508 subclause 4.5.3A.3 are performed on Cell 1.	–	–
7	The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context.	<–	RRC: RRCConnectionReconfiguration
8	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRC: RRCConnectionReconfigurationComplete
9	The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST	–	–
10	UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE	–	–
11	Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 10 greater than zero?	–	–	1	P

21.1.7.3.3 Specific message contents

Table 21.1.7.3.3-1: ACTIVATE TEST MODE (preamble)

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

Table 21.1.7.3.3-2: CLOSE UE TEST LOOP (step 3, Table 21.1.7.3.2-1)

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