17.3 MBMS Counting Procedure

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.3.1 MBMS Counting / UE not receiving MBMS service

17.3.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state}

ensure that {

when { UE is not in MBSFN area, enters another cell in MBSFN area, SS sends MBMSCountingRequest message and UE is interested to receive at least one of the services received in MBMSCountingRequest message }

then { UE shall start acquiring the MBMSCountingRequest message from the beginning of the repetition period and send MBMSCountingResponse message }

}

(2)

with { UE in E-UTRA RRC_Connected state }

ensure that {

when { UE is not receiving an MBMS service, receives MCCH information change notification, SS sends MBMSCountingRequest message and UE is interested to receive at least one of the services received in the MBMSCountingRequest message }

}

17.3.1.2 Conformance requirements

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

[TS 36.331 clause 5.8.2.3]

An MBMS capable UE shall:

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

2> start acquiring the MBSFNAreaConfiguration message and the MBMSCountingRequest message if present, 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.

1> if the UE enters an MBSFN area:

2> acquire the MBSFNAreaConfiguration message and the MBMSCountingRequest message if present, at the next repetition period;

1> if the UE is receiving an MBMS service:

2> start acquiring the MBSFNAreaConfiguration message and the MBMSCountingRequest message if present, that both concern the MBSFN area of the service that is being received, from the beginning of each modification period;

[TS 36.331 clause 5.8.4.1]

Figure 5.8.4.1-1: MBMS Counting procedure

The MBMS Counting procedure is used by the E-UTRAN to count the number of RRC_CONNECTED mode UEs which are receiving via an MRB or interested to receive via an MRB the specified MBMS services.

The UE determines interest in an MBMS service, that is identified by the TMGI, by interaction with upper layers.

[TS 36.331 clause 5.8.4.2]

E-UTRAN initiates the procedure by sending an MBMSCountingRequest message.

[TS 36.331 clause 5.8.4.3]

Upon receiving the MBMSCountingRequest message, the UE in RRC_CONNECTED mode shall:

1> if the UE is receiving via an MRB or interested to receive via an MRB at least one of the services in the received countingRequestList:

2> if more than one entry is included in the mbsfn-AreaInfoList received in SystemInformationBlockType13:

3> include the mbsfn-AreaIndex in the MBMSCountingResponse message and set it to the index of the entry in the mbsfn-AreaInfoList within the received SystemInformationBlockType13 that corresponds with the MBSFN area used to transfer the received MBMSCountingRequest message;

2> for each MBMS service included in the received countingRequestList:

3> if the UE is receiving via an MRB or interested to receive via an MRB this MBMS service:

4> include an entry in the countingResponseList within the MBMSCountingResponse message with countingResponseService set it to the index of the entry in the countingRequestList within the received MBMSCountingRequest that corresponds with the MBMS service the UE is receiving or interested to receive;

2> submit the MBMSCountingResponse message to lower layers for transmission upon which the procedure ends;

NOTE 1: UEs that are receiving an MBMS User Service [56] by means of a Unicast Bearer Service [57] (i.e. via a DRB), but are interested to receive the concerned MBMS User Service [56] via an MBMS Bearer Service (i.e. via an MRB), respond to the counting request.

NOTE 2: The UE treats the MBMSCountingRequest messages received in each modification period independently. In the unlikely case E-UTRAN would repeat an MBMSCountingRequest (i.e. including the same services) in a subsequent modification period, the UE responds again.

17.3.1.3 Test description

17.3.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 does not belong to any MBSFN areas

– Cell 2 belongs to an MBSFN area

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

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

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 17.3.1.3.3-1a is transmitted on MCCH in Cell 2

UE:

– None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18] on Cell 1.

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

NOTE 1: This test case use the default message for MBMSCountingRequest in [18] which includes MBMS service with MBMS Service ID 0 in the CountingRequestList.

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

17.3.1.3.2 Test procedure sequence

Table 17.3.1.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 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 17.3.1.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	-91	-85	The power level values are assigned to satisfy R_{Cell 1} < R_{Cell 2.}

Table 17.3.1.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes Cell 1 and Cell 2 level according to the row "T1" in table 17.3.1.3.2-1.	–	–	–	–
2	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform handover to Cell 2.	<–	RRCConnectionReconfiguration	–	–
3	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2	–>	RRCConnectionReconfigurationComplete	–	–
3A	SS transmits MCCH information change notification	–	–	–	–
4	The SS sends MBSFNAreaConfiguration message and MBMSCountingRequest message in the next MCCH modification period after the sending of MCCH information change notification in step 3A	<–	MBSFNAreaConfiguration MBMSCountingRequest	–	–
5	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message and MBMSCountingRequest message	–	–	–	–
6	Void	–	–	–	–
7	Check: Does the UE send MBMSCountingResponse message?	–>	MBMSCountingResponse	1	P
8	The SS transmits MCCH information change notification	–	–	–	–
9	The SS transmits MBSFNAreaConfiguration message and MBMSCountingRequest message in the next MCCH modification period after the sending of MCCH information change notification in step 8	<–	MBSFNAreaConfiguration MBMSCountingRequest	–	–
10	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message and MBMSCountingRequest message	–	–	–	–
11	Void	–	–	–	–
12	Check: Does the UE send MBMSCountingResponse message?	–>	MBMSCountingResponse	2	P

17.3.1.3.3 Specific message contents

Table 17.3.1.3.3-1: SystemInformationBlockType2 for Cell 2 (preamble and all steps, Table 17.3.1.3.2-2)

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

Table 17.3.1.3.3-1a: MBSFNAreaConfiguration Cell 2 (preamble and all steps)

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.3.1.3.3-2: RRCConnectionReconfiguration (step 2, Table 17.3.1.3.2-2)

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

Table 17.3.1.3.3-3: MobilityControlInfo (Table 17.3.1.3.3-2)

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
}

Table 17.3.1.3.3-4: MBSFNAreaConfiguration (steps 4 and 9, Table 17.3.1.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	E-UTRAN configures mch-SchedulingPeriod of the (P)MCH listed first in PMCH-InfoList to be smaller than or equal to mcch-RepetitionPeriod.
}
}
}
}

17.3.2 MBMS Counting / UE receiving MBMS service

17.3.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state}

ensure that {

when { UE is in MBSFN area, enters another cell in MBSFN area, SS sends MBMSCountingRequest message and UE is interested to receive at least one of the services received in MBMSCountingRequest message }

then { UE shall start acquiring the MBMSCountingRequest message from the beginning of the repetition period and send MBMSCountingResponse message with the countingResponseService-r10 set to the corresponding entry of serviceId-r9 in the received MBMSCountingRequest and the mbsfn_AreaIndex_r10 set as the number of mbsfn-AreaInfoList received in SystemInformationBlockType13 }

}

(2)

with { UE in E-UTRA RRC_Connected state }

ensure that {

when { UE is receiving an MBMS service, receives MCCH information change notification, SS sends MBMSCountingRequest message and UE is interested to receive at least one of the services received in the MBMSCountingRequest message }

then { UE shall start acquiring the MBMSCountingRequest message from the beginning of the modification period following the one in which the change notification was received and send MBMSCountingResponse message with the countingResponseService-r10 set to the corresponding entry of serviceId-r9 in the received MBMSCountingRequest and the mbsfn_AreaIndex_r10 set as the number of mbsfn-AreaInfoList received in SystemInformationBlockType13 }

}

17.3.2.2 Conformance requirements

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

[TS 36.331 clause 5.8.2.3]

An MBMS capable UE shall:

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

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

1> if the UE enters an MBSFN area:

2> acquire the MBSFNAreaConfiguration message and the MBMSCountingRequest message if present, at the next repetition period;

1> if the UE is receiving an MBMS service:

[TS 36.331 clause 5.8.4.1]

Figure 5.8.4.1-1: MBMS Counting procedure

The MBMS Counting procedure is used by the E-UTRAN to count the number of RRC_CONNECTED mode UEs which are receiving via an MRB or interested to receive via an MRB the specified MBMS services.

The UE determines interest in an MBMS service that is identified by the TMGI, by interaction with upper layers.

[TS 36.331 clause 5.8.4.2]

E-UTRAN initiates the procedure by sending an MBMSCountingRequest message.

[TS 36.331 clause 5.8.4.3]

Upon receiving the MBMSCountingRequest message, the UE in RRC_CONNECTED mode shall:

1> if the UE is receiving via an MRB or interested to receive via an MRB at least one of the services in the received countingRequestList:

2> if more than one entry is included in the mbsfn-AreaInfoList received in SystemInformationBlockType13:

2> for each MBMS service included in the received countingRequestList:

3> if the UE is receiving via an MRB or interested to receive via an MRB this MBMS service:

2> submit the MBMSCountingResponse message to lower layers for transmission upon which the procedure ends;

17.3.2.3 Test description

17.3.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 belongs to an MBSFN area

– Cell 2 belongs to another 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

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

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

UE:

– None.

Preamble:

– The UE is in state Generic RB Established (state 3A) on Cell 1 according to [18].

– 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.3.2.3.2 Test procedure sequence

Table 17.3.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.3.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	-91	-85	The power level values are assigned to satisfy R_{Cell 1} < R_{Cell 2.}

Table 17.3.2.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes Cell 1 and Cell 2 level according to the row "T1" in table 17.3.1.3.2-1.	–	–	–	–
2	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform handover to Cell 2.	<–	RRCConnectionReconfiguration	–	–
3	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2?	–>	RRCConnectionReconfigurationComplete	–	–
3A	SS transmits MCCH information change notification	–	–	–	–
4	SS sends MBSFNAreaConfiguration message and MBMSCountingRequest message in the next MCCH modification period after the sending of MCCH information change notification in step 3A	<–	MBSFNAreaConfiguration MBMSCountingRequest	–	–
5	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message and MBMSCountingRequest message	–	–	–	–
6	Void	–	–	–	–
7	Check: Does UE send MBMSCountingResponse message?	–>	MBMSCountingResponse	1	P
7A	The generic procedures described in TS 36.508 subclause 4.5.4.3 is performed on Cell 2 closing UE test loop Mode C	–	–	–	–
7B	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	–	–
7C	Void	–	–	–	–
7C1	The SS waits 6 seconds for the MBMS counter check procedure to start, and during this time allows reception of MBMSCountingResponse which may occur on each MCCH modification period.	–	–	–	–
7D	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
7E	UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	–	–
7F	Check: Is the number of reported MBMS Packets received on the MTCH greater than zero? Note: This verifies that UE is receiving the MBMS data	–	–	2	P
8	SS transmits MCCH information change notification	–	–	–	–
9	SS transmits MBSFNAreaConfiguration message and MBMSCountingRequest message in the next MCCH modification period after the sending of MCCH information change notification in step 8	<–	MBSFNAreaConfiguration MBMSCountingRequest	–	–
10	Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message and MBMSCountingRequest message	–	–	–	–
11	Void	–	–	–	–
12	Check: Does UE send MBMSCountingResponse message?	–>	MBMSCountingResponse	2	P

17.3.2.3.3 Specific message contents

Table 17.3.2.3.3-1: SystemInformationBlockType 1 &2 for Cell 2 (preamble and all steps, Table 17.3.2.3.2-2)

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

Table 17.3.2.3.3-1a: SystemInformationBlockType13 (preamble and all steps Cell 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
}

17.3.2.3.3-1b: MBSFNAreaConfiguration (preamble and all steps Cell 2)

Derivation Path: 36.508 table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
mbms-SessionInfoList-r9 SEQUENCE (SIZE (0..maxSessionPerPMCH)) OF SEQUENCE {
MBMS-SessionInfo-r9 SEQUENCE {
serviceId-r9	‘000000’O
}
}
}

Table 17.3.2.3.3-2: MBSFNAreaConfiguration (steps 4 and 9, Table 17.3.2.3.2-2)

Derivation Path:. table 17.3.2.3.3-1b
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	E-UTRAN configures mch-SchedulingPeriod of the (P)MCH listed first in PMCH-InfoList to be smaller than or equal to mcch-RepetitionPeriod.
}
}
}
}

Table 17.3.2.3.3-4: MBMSCountingResponse (step 7 and step 12, Table 17.3.2.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-4AB
Information Element	Value/remark	Comment	Condition
MBMSCountingResponse-r10 ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
CountingResponse-r10 SEQUENCE (SIZE (1.. maxServiceCount)) OF SEQUENCE {
mbsfn_AreaIndex_r10	Not present	MBSFN Area Index (TS 36.331 clause 5.8.4.3)
countingResponseList-r10 SEQUENCE {
countingResponseService-r10	‘0’	Corresponding the entry of MBMS service ID list
}
}
}
}
}

Table 17.3.2.3.3-3: MBMSCountingRequest (step 4 and step 9, Table 17.3.2.3.2-2)

Derivation Path: 36.508 Table 4.6.1-4AA
Information Element	Value/remark	Comment	Condition
MBMSCountingRequest-r10 ::= SEQUENCE {
CountingRequestList-r10 SEQUENCE (SIZE (1.. maxServiceCount)) OF SEQUENCE {
tmgi-r10 SEQUENCE {
serviceId-r9	‘000001’O	MBMS service ID (TS 24.008 clause 10.5.6.13), OCTET STRING (SIZE (3))
}
}
}