8.5.5 MBMS Counting

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

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

8.5.5.1 MBMS Counting in Idle Mode / MBMS Selected Service

8.5.5.1.1 Definition

This test case is applicable for all UEs supporting MBMS broadcast services.

8.5.5.1.2 Conformance requirement

The MBMS counting procedure is used by the UE to inform UTRAN about its interest to receive an MBMS transmission.

…

The UE initiates the MBMS counting procedure for an MBMS transmission upon receiving an MBMS MODIFIED SERVICES message including IE "MBMS required UE action" with the value set to ‘Acquire counting info’ or set to "Acquire counting info– PTM RBs unmodified".

…

Upon receiving the MBMS ACCESS INFORMATION message including one or more MBMS service(s) it has joined, and/ or including one or more MBMS Selected Services the UE shall for each joined and / or selected service:

1> if the UE is in idle mode:

2> draw a random number, "rand", uniformly distributed in the range: 0 ≤ rand < 1

2> if ‘rand’ is lower than the value indicated by the IE ‘Access probability factor-Idle’ for the concerned service:

3> indicate to upper layers that establishment of an RRC connection is required to receive the concerned MBMS service, with the establishment cause set to ‘MBMS reception’;

3> if the above condition applies for more than one service, initiate a single indication to upper layers;

3> if the RRC connection establishment succeeds, the procedure ends.

…

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

…

1> otherwise if the UE performs connection establishment for MBMS counting as specified in subclause 8.7.4; and

1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response:

3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority;

3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8.

1> if the UE included one or more "MBMS Selected Service ID" IEs:

2> include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29.

Reference

3GPP TS 25.331 clauses 8.7.4, 8.7.4.1, 8.7.4.2, 8.7.4.3, 8.1.3.3.

8.5.5.1.3 Test purpose

To confirm that the UE starts the MBMS counting procedure in idle mode upon receiving an MBMS MODIFIED SERVICES message including IE "MBMS required UE action" and an ACCESS INFORMATION message including IE "Access probability factor – Idle" set to 0 (corresponding to the actual probability factor value 1).

To verify that the UE correctly includes the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and IE "MBMS Modification Period identity" in the counting response initiated for a MBMS Selected Service.

8.5.5.1.4 Method of test

Initial Condition

System Simulator: 1 MBMS cell (cell 21) using MCCH Longest Default scheduling, and combination C1 as defined in TS 34.108 clause 11.

User Equipment:

The UE is in Idle Mode as specified in clause 7.6 of TS 34.108.

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Broadcast service application available on UE Yes/No.

Test Procedure

The SS transmits an MBMS MODIFIED SERVICE INFORMATION message which includes in the “Modified service list” for the MBMS activated service “MBMS required UE action” set to “Acquire counting info”.

The SS transmits an MBMS ACCESS INFORMATION message, which includes the MBMS Short transmission ID associated to the MBMS activated service and “Access probability factor – Idle” set to 0.

NOTE: The “Access probability factor” sent in the MBMS ACCESS INFORMATION message set to 0 corresponds to an actual Probability Factor = 1, according to the formula in TS 25.331 clause 10.2.16e.

The UE transmits an RRC CONNECTION REQUEST message to the SS, with “Establishment cause” set to “MBMS reception”.

The SS transmits an RRC CONNECTION SETUP message to the UE which moves the UE to CELL_DCH state.

When the UE receives this message, the UE establishes an RRC connection and transmits an RRC CONNECTION SETUP COMPLETE message.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
				The UE is in idle mode.
1			MBMS MODIFIED SERVICES INFORMATION	The SS transmits the message, which includes “MBMS required UE action” set to “Acquire counting info”
2			MBMS ACCESS INFORMATION	The SS transmits the message, which includes “MBMS short transmission ID” IE referring to the service the UE has activated and “Access probability factor – Idle” IE set to 0 (corresponding to actual Access Probability = 1).
3			RRC CONNECTION REQUEST	The UE transmits the message with Establishment cause set to “MBMS reception” and with the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity.
4			RRC CONNECTION SETUP	SS assigns DPCH resources to allow UE to establish an RRC connection. RRC state indicator set to CELL_DCH.
5			RRC CONNECTION SETUP COMPLETE
5a			MBMS MODIFICATION REQUEST	The UE completing the RRC Connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after step 5 and before step 7.
6	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Broadcast service Reception”.
7			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific Message Contents

All messages have the same content as defined in 34.108 clause 9.1.1 with the following exceptions:

MBMS MODIFIED SERVICES INFORMATION (Step 1)

Information Element	Value/remark
Modified service list	Only 1 entry
– MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
– MBMS required UE action	Acquire counting info

MBMS ACCESS INFORMATION (Step 2)

Information Element	Value/remark
Service list	Only 1 entry
– MBMS short transmission ID	Index to the MBMS transmission identity in the previous MBMS MODIFIED SERVICES INFORMATION
– Access probability factor – Idle	0 (corresponding to the actual probability factor value 1)
– Connected mode counting scope
– URA_PCH	FALSE
– CELL_PCH	FALSE
– CELL_FACH	FALSE

RRC CONNECTION REQUEST (Step 3)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI.
Establishment Cause	MBMS reception
Protocol Error Indicator	Check to see if it is set to FALSE
Measured results on RACH	Not checked.
MBMS Selected Services
– MBMS Selected Services	Only 1 entry
– MBMS Selected Service ID	MBMS short transmission identity referring to the service the UE has selected
– Modification period identity	Indicates the modification period the MBMS short transmission identities refer to

MBMS MODIFICATION REQUEST (steps 5a)

Information Element	Value/remark
MBMS preferred frequency request	Check that the IE is not present
MBMS RB list requested to be released	Check that the IE is not present
MBMS Selected Service Info
– CHOICE Status	Some
– MBMS Selected Services Full
– MBMS Selected Service ID	Only 1 entry
– MBMS Service ID	MBMS service ID of the activated MBMS service
– CHOICE PLMN identity	Check to see that one of the below choice element is present
– SameAs-MIB	(no data)
– explicitPLMN_Id	Check to see if it is set to the same value as "PLMN ID” in the Master Information block transmitted for the current serving cell.

8.5.5.1.5 Test requirement

At step 3, the UE shall transmit an RRC CONNECTION REQUEST message with “Establishment Cause” set to “MBMS reception” on the uplink CCCH and including in case of MBMS Selected services the IE “MBMS Selected Service ID” of the concerned MBMS selected service within the IE “MBMS Selected Services Short” and the IE “MBMS Modification Period identity”.

At step 5, the UE shall transmit an RRC CONNECTION SETUP COMPLETE message on a dedicated channel.

8.5.5.1m MBMS Counting in Idle Mode / MBMS Multicast Service

8.5.5.1m.1 Definition

This test is applicable for all UEs that support MBMS multicast services.

8.5.5.1m.2 Conformance requirement

Same conformance requirement as in clause 8.5.5.1.2 except there is no reference to 3GPP TS 25.331 clause 8.1.3.3.

Reference

3GPP TS 25.331 clauses 8.7.4, 8.7.4.1, 8.7.4.2, 8.7.4.3.

8.5.5.1m.3 Test purpose

8.5.5.1m.4 Method of test

Initial condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 22

User Equipment:

The UE is in Idle Mode as specified in clause 7.6 of TS 34.108.

The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Multicast service application available on UE Yes/No.

Test procedure

Same test procedure as in clause 8.5.5.1.4.

Expected sequence

Same expected sequence as in clause 8.5.5.1.4 except for RRC CONNECTION REQUEST message content (step 3) and MODIFICATION REQUEST procedure not required.

Step	Direction		Message	Comment
	UE	SS
				The UE is in idle mode.
1			MBMS MODIFIED SERVICES INFORMATION	The SS transmits the message, which includes “MBMS required UE action” set to “Acquire counting info”
2			MBMS ACCESS INFORMATION	The SS transmits the message, which includes “MBMS short transmission ID” IE referring to the service the UE has joined and “Access probability factor – Idle” IE set to 0 (corresponding to actual Access Probability = 1).
3			RRC CONNECTION REQUEST	The UE transmits the message with Establishment cause set to “MBMS reception”
4			RRC CONNECTION SETUP	SS assigns DPCH resources to allow UE to establish an RRC connection. RRC state indicator set to CELL_DCH.
5			RRC CONNECTION SETUP COMPLETE
6	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Multicast service Reception”.
7			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific message contents

Same specific messages contents as in clause 8.5.5.1.4 except for RRC CONNECTION REQUEST message content (step 3).

RRC CONNECTION REQUEST (Step 3)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI.
Establishment Cause	MBMS reception
Protocol Error Indicator	Check to see if it is set to FALSE
Measured results on RACH	Not checked.
MBMS Selected Services	Not present

8.5.5.1m.5 Test requirements

At step 3, the UE shall transmit an RRC CONNECTION REQUEST message with “Establishment Cause” set to “MBMS reception” on the uplink CCCH.

At step 5, the UE shall transmit an RRC CONNECTION SETUP COMPLETE message on a dedicated channel.

8.5.5.2 MBMS Counting in CELL_FACH / MBMS Selected Service

8.5.5.2.1 Definition

This test case is applicable for UEs that support MBMS broadcast services.

8.5.5.2.2 Conformance requirement

If the IE "MBMS required UE action" is included and concerns an MBMS activated service the UE shall:

…

1> if the IE "MBMS required UE action" is set to ‘Acquire counting info’ or set to ‘Acquire counting info– PTM RBs unmodified’:

2> perform the MBMS counting procedure as specified in subclause 8.7.4;

NOTE: If upper layers indicate that an MBMS transmission has already been received correctly, the UE will continue as if the information about the concerned MBMS transmission was not included in the message. This implies that the UE does not respond to counting for a transmission already received correctly.

…

The MBMS counting procedure is used by the UE to inform UTRAN about its interest to receive an MBMS transmission. The procedure applies to UEs supporting MBMS that are in idle mode or in connected mode. In connected mode the procedure applies to the URA_PCH, Cell_PCH and/ or Cell_FACH states dependent upon the value of the IE "Connected mode counting scope".

…

1> if the UE is in URA_PCH state, Cell_PCH or Cell_FACH state and the IE "Connected mode counting scope" indicates that counting is applicable for this UE state:

2> draw a random number, "rand", uniformly distributed in the range: 0 ≤ rand < 1.

2> if ‘rand’ is lower than the value indicated by the IE ‘Access probability factor-connected’ for the concerned service:

3> if a cell update has not been successfully transmitted for this service in the current modification period:

4> initiate the cell update procedure with ‘Cell update cause’ set to "MBMS reception", in accordance with subclause 8.3.1;

4> if the above condition applies for more than one service, initiate a single cell update;

4> if the cell update procedure succeeds,

5> the procedure ends.

2> otherwise:

3> if the message triggering the MBMS counting procedure included the IE "Continue MCCH reading" with a value set to TRUE:

4> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3.

3> otherwise:

4> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and with stopping at the end of the modification period, in accordance with subclause 8.7.1.3.

1> otherwise:

2> the procedure ends;

Upon receiving the MBMS ACCESS INFORMATION message not including an MBMS service(s) the UE has joined:

1> the procedure ends;

…

The UE shall set the IEs in the CELL UPDATE message as follows:

…

1> otherwise, if the UE performs cell update for MBMS counting as specified in subclause 8.7.4; and

1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response:

3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority;

3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8.

1> if the UE included one or more "MBMS Selected Service ID" IEs:

2> include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29.

Reference

3GPP TS 25.331 clauses 8.6.9.6, 8.7.4, 8.7.4.1, 8.7.4.2, 8.7.4.3, 8.3.1.3.

8.5.5.2.3 Test purpose

To verify that the UE correctly handles the counting procedure in cell_FACH state, upon receiving an MBMS MODIFIED SERVICES message including IE "MBMS required UE action" and an ACCESS INFORMATION message including IE "Access probability factor – Connected" set to 0.

8.5.5.2.4 Method of test

Initial condition

System Simulator: one MBMS cell (cell 21) using MCCH Shortest Default scheduling, and combination C1 as defined in TS 34.108 clause 11.

User Equipment:

The UE is in CELL_FACH state as specified in clause 7.6 of TS 34.108.

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Broadcast service application available on UE Yes/No.

Test procedure

1) The SS sends a MBMS MODIFIED SERVICES INFORMATION message which includes the IE “MBMS required UE action” set to ‘Acquire counting info’ for the MBMS Service identity in the MBMS Transmission identity matching the one in the MBMS_ACTIVATED_SERVICES variable.

2) The SS sends in the same Modification Period the MBMS ACCESS INFORMATION message which includes:

– the “MBMS short transmission ID” IE referring to the service the UE has activated

– the “Connected mode counting scope” IE set to TRUE applicable to the UE connected state and

– the value for “Access probability factor – connected” IE set to 0 (corresponding to the actual probability factor value 1)

3) The UE shall perform the MBMS counting procedure. The UE shall draw a random number ‘rand’. If ‘rand’ is lower than the value indicated by the IE “Access probability factor – connected”, it shall send a CELL UPDATE message to the SS on the uplink CCCH of cell 21 and set IE "Cell update cause" to "MBMS reception". The IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and the IE "MBMS Modification Period identity" shall be included in the counting response initiated for a MBMS Selected Service. After the SS receives this message, it transmits a CELL UPDATE CONFIRM message to the UE on the downlink CCCH.

4) The SS sends the MBMS ACCESS INFORMATION message again in the same Modification Period. The UE shall not perform the MBMS counting procedure during the same Modification Period.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			MBMS MODIFIED SERVICES INFORMATION	“MBMS required UE action” IE is set to "Acquire counting info"
2			MBMS ACCESS INFORMATION	“MBMS short transmission ID” IE referring to the service the UE has activated, “Connected mode counting scope” IE set to "TRUE", “Access probability factor – connected” IE set to 0.
3			CELL UPDATE	The CELL UPDATE message shall contain the value "Cell Update Cause" set to "MBMS reception" and in case of MBMS Selected service the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity.
4			CELL UPDATE CONFIRM
5			MBMS ACCESS INFORMATION	The SS sends again in the same MP a MBMS access Information message.
6				The SS check that the UE shall not perform again the counting procedure by sending another cell update message.
7			CALL C.2	If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails.

Specific message contents

All messages have the same content as defined in 34.108 clause 9.1.1 with the following exceptions:

MBMS modified services Information (Step 1)

Information Element	Value/remark
Modified services list	Only 1 entry
-MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
-MBMS required UE action	Acquire counting info

MBMS Access Information (Steps 2 and 5)

Information Element	Value/remark
Service list	Only 1 entry
-MBMS short transmission ID	Index to the MBMS transmission identity in the previous MBMS MODIFIED SERVICES INFORMATION
-Access probability factor – connected	0 (corresponding to the actual probability factor value 1)
-Connected mode counting scope
– URA_PCH	FALSE
– CELL_PCH	FALSE
– CELL_FACH	TRUE

CELL UPDATE (Step 3)

Information Element	Value/remark
Cell update cause	MBMS reception
MBMS Selected Services	present in case of MBMS Selected service
– MBMS Selected Services	Only 1 entry
– MBMS Selected Service ID	MBMS short transmission identity referring to the service the UE has selected
– Modification period identity	Indicates the modification period the MBMS short transmission identities refer to

8.5.5.2.5 Test requirements

At step 3, check that the UE performs the MBMS counting procedure by performing the cell update procedure using the cause value “MBMS reception" and using in case of MBMS Selected services the IE “MBMS Selected Service ID” of the concerned MBMS selected service within the IE “MBMS Selected Services Short” and the IE “MBMS Modification Period identity”.

At step 6, check that the UE does not perform the MBMS counting again during the same Modification Period.

8.5.5.2m MBMS Counting in CELL_FACH / MBMS Multicast Service

8.5.5.2m.1 Definition

This test is applicable for all UEs that support MBMS multicast services.

8.5.5.2m.2 Conformance requirement

Same conformance requirement as in clause 8.5.5.2.2 except there is no reference to 3GPP TS 25.331 clause 8.3.1.3.

8.5.5.2m.3 Test purpose

8.5.5.2m.4 Method of test

Initial condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 22

User Equipment:

The UE is in CELL_FACH state as specified in clause 7.6 of TS 34.108.

The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Multicast service application available on UE Yes/No.

Test procedure

Same test procedure as in clause 8.5.5.2.4 except for the points 2 and 3:

2) The SS sends in the same Modification Period the MBMS ACCESS INFORMATION message which includes:

– the “MBMS short transmission ID” IE referring to the service the UE has joined

– the “Connected mode counting scope” IE set to TRUE applicable to the UE connected state and

– the value for “Access probability factor – connected” IE set to 0 (corresponding to the actual probability factor value 1)

Expected sequence

Same expected sequence as in clause 8.5.5.2.4 except for CELL UPDATE message content (step 3).

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			MBMS MODIFIED SERVICES INFORMATION	“MBMS required UE action” IE is set to "Acquire counting info"
2			MBMS ACCESS INFORMATION	“MBMS short transmission ID” IE referring to the service the UE has joined, “Connected mode counting scope” IE set to "TRUE", “Access probability factor – connected” IE set to 0.
3			CELL UPDATE	The CELL UPDATE message shall contain the value "Cell Update Cause" set to "MBMS reception".
4			CELL UPDATE CONFIRM
5			MBMS ACCESS INFORMATION	The SS sends again in the same MP a MBMS access Information message.
6				The SS check that the UE shall not perform again the counting procedure by sending another cell update message.
7			CALL C.2	If the test result of C.2 indicates that UE is in CELL_FACH state, the test passes, otherwise it fails.

Specific message contents

Same specific messages contents as in clause 8.5.5.2.4 except for CELL UPDATE message content (step 3).

CELL UPDATE (Step 3)

Use the message sub-type in default message content defined in 3GPP TS 34.108 [9] clause 9, with the following exceptions.

Information Element	Value/remark
Cell update cause	MBMS reception

8.5.5.2m.5 Test requirements

At step 3, check that the UE performs the MBMS counting procedure by performing the cell update procedure using the cause value “MBMS reception”.

At step 6, check that the UE does not perform the MBMS counting again during the same Modification Period.

8.5.5.3 MBMS No Counting in CELL_DCH / MBMS Selected Service

8.5.5.3.1 Definition

This test is applicable for all UEs that support MBMS broadcast services and capable of reading MCCH in CELL_DCH state.

8.5.5.3.2 Conformance requirement

If the IE "MBMS required UE action" is included and concerns an MBMS activated service the UE shall:

1> if the "MBMS required UE action" is set to ‘None’:

2> take no action with respect to this IE.

1> if the IE "MBMS required UE action" is set to ‘Acquire counting info’ or set to ‘Acquire counting info– PTM RBs unmodified’:

2> perform the MBMS counting procedure as specified in subclause 8.7.4;

…

The UE shall acquire the MBMS ACCESS INFORMATION message without delaying reading of MCCH until the next modification period in accordance with subclause 8.7.1.3. If the procedure the UE would apply to respond to counting (Idle mode: RRC connection establishment, connected mode: Cell update) is ongoing, the UE may defer acquiring the MBMS ACCESS INFORMATION message until this procedure has completed.

The UE behaviour upon receiving an MBMS ACCESS INFORMATION message that is contained in more than one TTI is not specified.

Upon receiving the MBMS ACCESS INFORMATION message including one or more MBMS service(s) it has joined, and/or including one or more MBMS Selected Services the UE shall for each joined and/or selected service:

1> if the UE is in idle mode:

…

1> if the UE is in URA_PCH state, Cell_PCH or Cell_FACH state and the IE "Connected mode counting scope" indicates that counting is applicable for this UE state:

…

1> otherwise:

2> the procedure ends;

Reference

3GPP TS 25.331 clauses 8.6.9.6, 8.7.4.1, 8.7.4.2, 8.7.4.3.

8.5.5.3.3 Test purpose

To verify that the UE in CELL_DCH state (with the probability factor set to 1) does not perform the MBMS counting procedure.

8.5.5.3.4 Method of test

Initial condition

System Simulator: one MBMS cell (cell 21) using MCCH Default2 scheduling, and combination C1 as defined in TS 34.108 clause 11.

User Equipment:

The UE is in CELL_DCH state as specified in clause 7.6 of TS 34.108. The UE has been registered in both CS and PS domains.

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Broadcast service application available on UE Yes/No.

– UE supports MCCH reception in CELL_DCH state Yes/No.

Test procedure

The UE is in CELL_DCH state. The SS transmits an MBMS MODIFIED SERVICES INFORMATION message which includes the IE “MBMS required UE action” set to "Acquire counting info" for the MBMS Service identity in the MBMS Transmission identity matching the one in the MBMS_ACTIVATED_SERVICES variable.

The UE receives an MBMS ACCESS INFORMATION message including the concerned MBMS Selected service.

The UE shall not perform the MBMS counting procedure.

The SS continues to send MBMS ACCESS INFORMATION messages including the MBMS Selected service in the same Modification Period. The UE shall not perform the MBMS counting procedure.

The UE receives an MBMS ACCESS INFORMATION message including the MBMS Selected service in the next Modification Period. The UE shall not perform the MBMS counting procedure.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE is in CELL_DCH state.
1			MBMS MODIFIED SERVICES INFORMATION	“MBMS required UE action” IE is set to "Acquire counting info"
2			MBMS ACCESS INFORMATION	“MBMS short transmission ID” IE referring to the service the UE has activated, “Connected mode counting scope” IE set to "TRUE", “Access probability factor – connected” IE “ set to 0 (corresponding to the actual probability factor value 1).
3				The SS checks that the UE does not perform the counting procedure.
4			MBMS ACCESS INFORMATION	The SS continues to send MBMS access Information messages in the same MP.
5				The SS checks that the UE does not perform the counting procedure.
6			MBMS ACCESS INFORMATION	The SS sends a MBMS access Information message in the next MP.
7				The SS checks that the UE does not perform the counting procedure.
8			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific message contents

MBMS MODIFIED SERVICES INFORMATION (Step 1)

Information Element	Value/remark
Modified service list	Only 1 entry
– MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
– MBMS required UE action	Acquire counting info
– Continue MCCH reading	TRUE

MBMS ACCESS INFORMATION (Step 2, Step 4 and Step 6)

Information Element	Value/remark
Service list	Only 1 entry
– MBMS short transmission ID	Index to the MBMS transmission identity in the previous MBMS MODIFIED SERVICES INFORMATION
– Access probability factor – Idle	0 (corresponding to the actual probability factor value 1)
– Connected mode counting scope
– URA_PCH	TRUE
– CELL_PCH	TRUE
– CELL_FACH	TRUE

8.5.5.3.5 Test requirements

After step 2, the UE shall not perform the MBMS counting procedure.

After step 4, the UE shall not perform the MBMS counting procedure.

After step 6, the UE shall not perform the MBMS counting procedure.

8.5.5.3m MBMS No Counting in CELL_DCH / MBMS Multicast Service

8.5.5.3m.1 Definition

This test is applicable for all UEs that support MBMS multicast services and capable of reading MCCH in CELL_DCH state.

8.5.5.3m.2 Conformance requirement

Same conformance requirement as in clause 8.5.5.3.2.

8.5.5.3m.3 Test purpose

Same test purpose as in clause 8.5.5.3.3.

8.5.5.3m.4 Method of test

Initial condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 22

User Equipment:

The UE is in CELL_DCH state as specified in clause 7.6 of TS 34.108.

The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Multicast service application available on UE Yes/No.

– UE supports MCCH reception in CELL_DCH state Yes/No.

Test procedure

The UE receives an MBMS ACCESS INFORMATION message including the MBMS service the UE has joined.

The UE shall not perform the MBMS counting procedure.

The SS continues to send MBMS ACCESS INFORMATION messages including the MBMS service the UE has joined in the same Modification Period. The UE shall not perform the MBMS counting procedure.

The UE receives an MBMS ACCESS INFORMATION message including the MBMS service the UE has joined in the next Modification Period. The UE shall not perform the MBMS counting procedure.

Expected sequence

Same expected sequence as in clause 8.5.5.3.4 except for MBMS ACCESS INFORMATION message contents (steps 2, 4 and 6).

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE is in CELL_DCH state.
1			MBMS MODIFIED SERVICES INFORMATION	“MBMS required UE action” IE is set to "Acquire counting info"
2			MBMS ACCESS INFORMATION	“MBMS short transmission ID” IE referring to the service the UE has joined.
3				The SS checks that the UE does not perform the counting procedure.
4			MBMS ACCESS INFORMATION	The SS continues to send MBMS access Information messages in the same MP.
5				The SS checks that the UE does not perform the counting procedure.
6			MBMS ACCESS INFORMATION	The SS sends a MBMS access Information message in the next MP.
7				The SS checks that the UE does not perform the counting procedure.
8			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific message contents

Same specific messages contents as in clause 8.5.5.3.4.

8.5.5.3m.5 Test requirements

Same test requirement as in clause 8.5.5.3.5.

8.5.5.4 MBMS Counting in CELL_PCH / MBMS Selected Service

8.5.5.4.1 Definition

This test case is applicable for UEs that support MBMS broadcast services.

8.5.5.4.2 Conformance requirement

…

1> if the UE is in URA_PCH state, Cell_PCH or Cell_FACH state and the IE "Connected mode counting scope" indicates that counting is applicable for this UE state:

2> draw a random number, "rand", uniformly distributed in the range: 0 ≤ rand < 1.

2> if ‘rand’ is lower than the value indicated by the IE ‘Access probability factor-connected’ for the concerned service:

3> if a cell update has not been successfully transmitted for this service in the current modification period:

4> initiate the cell update procedure with ‘Cell update cause’ set to "MBMS reception", in accordance with subclause 8.3.1;

4> if the above condition applies for more than one service, initiate a single cell update;

4> if the cell update procedure succeeds,

5> the procedure ends.

2> otherwise:

3> if the message triggering the MBMS counting procedure included the IE "Continue MCCH reading" with a value set to TRUE:

3> otherwise:

1> otherwise:

2> the procedure ends;

Upon receiving the MBMS ACCESS INFORMATION message not including an MBMS service(s) the UE has joined:

1> the procedure ends;

…

The UE shall set the IEs in the CELL UPDATE message as follows:

…

1> otherwise, if the UE performs cell update for MBMS counting as specified in subclause 8.7.4; and

1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response:

3> order the MBMS Selected Services such that those selected with a higher priority are listed in the IE "MBMS Selected Services Short" before those selected with a lower priority;

3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8.

1> if the UE included one or more "MBMS Selected Service ID" IEs:

2> include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29.

Reference

3GPP TS 25.331 clauses 8.7.4, 8.7.4.1, 8.7.4.2, 8.7.4.3, 8.3.1.3.

8.5.5.4.3 Test purpose

To verify that the UE correctly handles the counting procedure in cell_PCH state, upon receiving an MBMS MODIFIED SERVICES message including IE "MBMS required UE action" and an ACCESS INFORMATION message including IE "Access probability factor – Connected" set to 0 for the selected services.

8.5.5.4.4 Method of test

Initial condition

System Simulator: one MBMS cell (cell 21)

User Equipment:

The UE is in CELL_PCH state as specified in clause 7.6 of TS 34.108.

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Broadcast service application available on UE Yes/No.

Test procedure

2) The SS sends in the same Modification Period the MBMS ACCESS INFORMATION message which includes:

– the “MBMS short transmission ID” IE referring to the service the UE has activated

– the “Connected mode counting scope” IE set to TRUE applicable to the UE connected state and

– the value for “Access probability factor – connected” IE set to 0 (corresponding to the actual probability factor value 1)

3) The UE shall perform the MBMS counting procedure. The UE shall draw a random number ‘rand’. If ‘rand’ is lower than the value indicated by the IE “Access probability factor – connected”, it shall send a CELL UPDATE message to the SS on the uplink CCCH of cell 21 and set IE "Cell update cause" to "MBMS reception". The IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and the IE "MBMS Modification Period identity" shall be included in the counting response initiated for the MBMS Selected Service. After the SS receives this message, it transmits a CELL UPDATE CONFIRM message to the UE on the downlink CCCH. The UE shall move to the Cell_PCH state as indicated by the IE "RRC State Indicator".

4) The SS sends the MBMS ACCESS INFORMATION message again in the same Modification Period. The UE shall not perform the MBMS counting procedure during the same Modification Period.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE is in cell_PCH
1			MBMS MODIFIED SERVICES INFORMATION	“MBMS required UE action” IE is set to "Acquire counting info"
2			MBMS ACCESS INFORMATION	“MBMS short transmission ID” IE referring to the service the UE has activated and “Connected mode counting scope” IE set to "TRUE", “Access probability factor – connected” IE set to 0.
3			CELL UPDATE	The UE shall perform the MBMS counting procedure which triggers the cell updating procedure which moves the UE into CELL_FACH state. The CELL UPDATE message shall contain the value "Cell Update Cause" set to "MBMS reception" and the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity.
4			CELL UPDATE CONFIRM	IE "RRC State Indicator” is set to CELL_PCH.
5			MBMS ACCESS INFORMATION	The SS sends again in the same MP a MBMS access Information message.
6				The SS check that the UE shall not perform again the counting procedure by sending another cell update message.
7			CALL C.4	If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails.

Specific message contents

MBMS modified services Information (Step 1)

Information Element	Value/remark
Modified services list	Only 1 entry
-MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
-MBMS required UE action	Acquire counting info

MBMS Access Information (Steps 2 and 5)

Information Element	Value/remark
Service list	Only 1 entry
-MBMS short transmission ID	Index to the MBMS transmission identity in the previous MBMS MODIFIED SERVICES INFORMATION
-Access probability factor – connected	0 (corresponding to the actual probability factor value 1)
-Connected mode counting scope
– URA_PCH	TRUE
– CELL_PCH	TRUE
– CELL_FACH	TRUE

CELL UPDATE (Step 3)

Use the message sub-type in default message content defined in 3GPP TS 34.108 [9] clause 9, with the following exceptions.

Information Element	Value/remark
Cell update cause	MBMS reception
MBMS Selected Services
– MBMS Selected Services	Only 1 entry
– MBMS Selected Service ID	MBMS short transmission identity referring to the service the UE has selected
– Modification period identity	Indicates the modification period the MBMS short transmission identities refer to

CELL UPDATE CONFIRM (Step 4)

Use the message sub-type in default message content defined in 3GPP TS 34.108 [9] clause 9, with the following exceptions.

Information Element	Value/remark
RRC State Indicator	Cell_PCH
UTRAN DRX cycle length coefficient	7

8.5.5.4.5 Test requirements

At step 3, check that the UE performs the MBMS counting procedure by performing the cell update procedure using the cause value “MBMS reception” and using in case of MBMS Selected services the IE “MBMS Selected Service ID” of the concerned MBMS selected service within the IE “MBMS Selected Services Short” and the IE “MBMS Modification Period identity”.

At step 6, check that the UE does not perform the MBMS counting again during the same Modification Period.

8.5.5.4m MBMS Counting in CELL_PCH / MBMS Multicast Service

8.5.5.4m.1 Definition

This test is applicable for all UEs that support MBMS multicast services.

8.5.5.4m.2 Conformance requirement

Same conformance requirement as in clause 8.5.5.4.2 except there is no reference to 3GPP TS 25.331 clause 8.3.1.3.

8.5.5.4m.3 Test purpose

8.5.5.4m.4 Method of test

Initial condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 22

User Equipment:

The UE is in CELL_PCH state as specified in clause 7.6 of TS 34.108.

The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Multicast service application available on UE Yes/No.

Test procedure

Same test procedure as in clause 8.5.5.2.4 except for the points 2 and 3:

2) The SS sends in the same Modification Period the MBMS ACCESS INFORMATION message which includes:

– the “MBMS short transmission ID” IE referring to the service the UE has joined

– the “Connected mode counting scope” IE set to TRUE applicable to the UE connected state and

– the value for “Access probability factor – connected” IE set to 0 (corresponding to the actual probability factor value 1)

3) The UE shall perform the MBMS counting procedure. The UE shall draw a random number ‘rand’. If ‘rand’ is lower than the value indicated by the IE “Access probability factor – connected”, it shall send a CELL UPDATE message to the SS on the uplink CCCH of cell 21 and set IE "Cell update cause" to "MBMS reception". After the SS receives this message, it transmits a CELL UPDATE CONFIRM message to the UE on the downlink CCCH. The UE shall move to the Cell_PCH state as indicated by the IE "RRC State Indicator".

Expected sequence

Same expected sequence as in clause 8.5.5.4.4 except for MBMS ACCESS INFORMATION message content (step 2) and CELL UPDATE message content (step 3).

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE is in cell_PCH
1			MBMS MODIFIED SERVICES INFORMATION	“MBMS required UE action” IE is set to "Acquire counting info"
2			MBMS ACCESS INFORMATION	“MBMS short transmission ID” IE referring to the service the UE has joined and “Connected mode counting scope” IE set to "TRUE", “Access probability factor – connected” IE set to 0.
3			CELL UPDATE	The UE shall perform the MBMS counting procedure which triggers the cell updating procedure which moves the UE into CELL_FACH state. The CELL UPDATE message shall contain the value "Cell Update Cause" set to "MBMS reception".
4			CELL UPDATE CONFIRM	IE "RRC State Indicator” is set to CELL_PCH.
5			MBMS ACCESS INFORMATION	The SS sends again in the same MP a MBMS access Information message.
6				The SS check that the UE shall not perform again the counting procedure by sending another cell update message.
7			CALL C.4	If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails.

Specific message contents

Same specific messages contents as in clause 8.5.5.4.4.

CELL UPDATE (Step 3)

Use the message sub-type in default message content defined in 3GPP TS 34.108 [9] clause 9, with the following exceptions.

Information Element	Value/remark
Cell update cause	MBMS reception

CELL UPDATE CONFIRM (Step 4)

Use the same specific message content as in clause 8.5.5.4.4 for CELL UPDATE CONFIRM message at Step 4.

8.5.5.4m.5 Test requirements

At step 3, check that the UE performs the MBMS counting procedure by performing the cell update procedure using the cause value “MBMS reception”.

At step 6, check that the UE does not perform the MBMS counting again during the same Modification Period.

8.5.5.5 Void

8.5.5.6 Void

8.5.5.7 RRC Connection establishment for MBMS Counting :Success after T318 Timeout/ MBMS Selected Service

8.5.5.7.1 Definition

This test case is applicable for UEs that support MBMS broadcast services.

8.5.5.7.2 Conformance requirement

The MBMS counting procedure is used by the UE to inform UTRAN about its interest to receive an MBMS transmission. The procedure applies to UEs supporting MBMS that are in idle mode or in connected mode for cells not operating in MBSFN mode as indicated in subclause 8.1.1.6.3.

…

Upon receiving the MBMS ACCESS INFORMATION message for cells not operating in MBSFN mode as indicated in subclause 8.1.1.6.3 including one or more MBMS service(s) it has joined and/or including one or more MBMS Selected Services, the UE shall for each joined and/or selected service:

1> if the UE is in idle mode:

2> draw a random number, "rand", uniformly distributed in the range: 0 ≤ rand < 1

2> if ‘rand’ is lower than the value indicated by the IE ‘Access probability factor-Idle’ for the concerned service:

3> indicate to upper layers that establishment of an RRC connection is required to receive the concerned MBMS service, with the establishment cause set to ‘MBMS reception’;

3> if the above condition applies for more than one service, initiate a single indication to upper layers;

3> if the RRC connection establishment succeeds, the procedure ends.

…

1> submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH;

1> set counter V300 to 1; and

1> if the variable ESTABLISHMENT_CAUSE is set to "MBMS reception":

2> when the MAC layer indicates success or failure to transmit the message:

3> if the MAC layer indicates failure:

4> enter idle mode;

4> consider the procedure to be unsuccessful;

4> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2;

4> the procedure ends.

3> else:

4> start timer T318;

4> apply value 0 for counter N300 regardless of the value included in IE "UE Timers and Constants in idle mode".

…

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

…

1> otherwise if the UE performs connection establishment for MBMS counting as specified in subclause 8.7.4; and

1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response:

3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8.

1> if the UE included one or more "MBMS Selected Service ID" IEs:

include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29.

…

If the counting response procedure (RRC connection establishment or Cell update) fails, the UE shall:

1> if the failure occurs in the same modification period as the one in which the UE initiated the counting response procedure; or

1> if the message triggering the MBMS counting procedure included the IE "Continue MCCH reading" with a value set to TRUE that is applicable in the modification period in which the UE detects the failure:

2> continue acquiring further MBMS ACCESS INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3.

1> otherwise:

2> the procedure ends.

Reference

3GPP TS 25.331 clauses 8.7.4, 8.7.4.1, 8.7.4.2, 8.7.4.3, 8.1.3.2, 8.1.3.3, 8.7.4.5.

8.5.5.7.3 Test purpose

To confirm that the UE starts T318 timer once UE MAC layer indicates successful transmission of RRC Connection Request message for MBMS counting.

To verify that the UE continues to acquire MBMS ACCESS INFORMATION messages after Expiry of T318, and hence re-start RRC Connection Request procedure for counting.

8.5.5.7.4 Method of test

Initial Condition

System Simulator: 1 MBMS cell (cell 21).

User Equipment:

The UE is in Idle Mode as specified in clause 7.6 of TS 34.108.

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Longest MCCH scheduling configuration defined in 34.108 clause 11.1.1.3 is used.

Related ICS/IXIT statements

– MBMS Broadcast service application available on UE Yes/No.

Test Procedure

The SS transmits an MBMS ACCESS INFORMATION message, which includes the MBMS Short transmission ID associated to the MBMS activated service and “Access probability factor – Idle” set to 0.

NOTE: The “Access probability factor” sent in the MBMS ACCESS INFORMATION message set to 0 corresponds to an actual Probability Factor = 1, according to the formula in TS 25.331 clause 10.2.16e.

The UE transmits an RRC CONNECTION REQUEST message to the SS, with “Establishment cause” set to “MBMS reception”. After MAC indication on successful transmission, starts T318 timer.

SS does not respond to the RRC CONNECTION REQUEST message.

After expiry of T318, UE Re-acquires MBMS ACCESS INFORMATION, and re-starts the counting procedure. The UE transmits an RRC CONNECTION REQUEST message to the SS, with “Establishment cause” set to “MBMS reception”.

The SS transmits an RRC CONNECTION SETUP message to the UE which moves the UE to CELL_DCH state.

When the UE receives this message, the UE establishes an RRC connection and transmits an RRC CONNECTION SETUP COMPLETE message.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				The UE is in idle mode.
1			MBMS MODIFIED SERVICES INFORMATION	The SS transmits the message, which includes “MBMS required UE action” set to “Acquire counting info”
2			MBMS ACCESS INFORMATION	The SS transmits the message, which includes “MBMS short transmission ID” IE referring to the service the UE has activated and “Access probability factor – Idle” IE set to 0 (corresponding to actual Access Probability = 1).
3			MBMS GENERAL INFORMATION
4			RRC CONNECTION REQUEST	The UE transmits the message with Establishment cause set to “MBMS reception”
5				SS does not respond to RRC Connection Request message in step 4.
6			RRC CONNECTION REQUEST	The UE re-sends the message with Establishment cause set to “MBMS reception” with the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity.
7			RRC CONNECTION SETUP	SS assigns DPCH resources to allow UE to establish an RRC connection. RRC state indicator set to CELL_DCH.
8			RRC CONNECTION SETUP COMPLETE
8a			MBMS MODIFICATION REQUEST	The UE completing the RRC connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after step 8 and before step 10.
9	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Broadcast service Reception”.
10			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific Message Contents

System Information Block type 1 (FDD)

Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:

Information Element	Value/remark
– UE Timers and constants in idle mode
-T300	8000 milliseconds

MBMS MODIFIED SERVICES INFORMATION (Step 1)

Information Element	Value/remark
Modified service list	Only 1 entry
– MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
– MBMS required UE action	Acquire counting info
– Continue MCCH reading	TRUE

MBMS ACCESS INFORMATION (Step 2)

Information Element	Value/remark
Service list	Only 1 entry
– MBMS short transmission ID	Index to the MBMS transmission identity in the previous MBMS MODIFIED SERVICES INFORMATION
– Access probability factor – Idle	0 (corresponding to the actual probability factor value 1)

MBMS GENERAL INFORMATION (Step 3)

Use the default message type found in TS 34.108, 9.1.1 except for

MBMS timers and counters
– T318	1500 ms

RRC CONNECTION REQUEST (Step 4 and 6)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI.
Establishment Cause	MBMS reception
Protocol Error Indicator	Check to see if it is set to FALSE
Measured results on RACH	Not checked.
MBMS Selected Services
– MBMS Selected Services	Only 1 entry
– MBMS Selected Service ID	MBMS short transmission identity referring to the service the UE has selected
– Modification period identity	Indicates the modification period the MBMS short transmission identities refer to

RRC CONNECTION SETUP (Step 7)

Use the default message type found in TS 34.108, 9.1.1.

RRC CONNECTION SETUP COMPLETE (Step 8)

Use the default message type found in TS 34.108, 9.1.1.

MBMS MODIFICATION REQUEST (steps 8a)

Information Element	Value/remark
MBMS preferred frequency request	Check that the IE is not present
MBMS RB list requested to be released	Check that the IE is not present
MBMS Selected Service Info
– CHOICE Status	Some
– MBMS Selected Services Full
– MBMS Selected Service ID	Only 1 entry
– MBMS Service ID	MBMS service ID of the activated MBMS service
– CHOICE PLMN identity	Check to see that one of the below choice element is present
– SameAs-MIB	(no data)
– explicitPLMN_Id	Check to see if it is set to the same value as "PLMN ID” in the Master Information block transmitted for the current serving cell.

8.5.5.7.5 Test requirement

At step 4 and 6, the UE shall transmit an RRC CONNECTION REQUEST message with “Establishment Cause” set to “MBMS reception” on the uplink CCCH and including the IE “MBMS Selected Service ID” of the concerned MBMS selected service within the IE “MBMS Selected Services Short” and the IE “MBMS Modification Period identity”.

The time difference between step 4 and 6 should be at least 1500 milliseconds (T318 expiry), and less than 6 seconds (T318 [1500ms] +2*AP [1280ms] +Transmission time on PRACH)

At step 8, the UE shall transmit an RRC CONNECTION SETUP COMPLETE message on a dedicated channel.

8.5.5.7m RRC Connection establishment for MBMS Counting :Success after T318 Timeout / MBMS Multicast Service

8.5.5.7m.1 Definition

This test is applicable for all UEs that support MBMS multicast services.

8.5.5.7m.2 Conformance requirement

Same conformance requirement as in clause 8.5.5.7.2.

8.5.5.7m.3 Test purpose

Same test purpose as in clause 8.5.5.7.3.

8.5.5.7m.4 Method of test

Initial Condition

System Simulator: 1 MBMS cell (cell 21).

User Equipment:

The UE is in Idle Mode as specified in clause 7.6 of TS 34.108.

The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Multicast service application available on UE Yes/No.

Test procedure

Same test procedure as in clause 8.5.5.7.4, except expected sequence step 8a is not applicable and at step 9 UE transmits Service Request, with IE "Service type" set to "MBMS Multicast service Reception”.

Specific message contents

Same specific messages contents as in clause 8.5.5.7.4 except for RRC CONNECTION REQUEST message content (step 4 and 6). Step 8a contents are not applicable.

RRC CONNECTION REQUEST (Step 4 and 6)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered P-TMSI.
Establishment Cause	MBMS reception
Protocol Error Indicator	Check to see if it is set to FALSE
Measured results on RACH	Not checked.
MBMS Selected Services	Not present

8.5.5.7m.5 Test requirements

Same Test Requirements as in clause 8.5.5.7.5, except UE shall not include in the IE “MBMS Selected Service ID” of the concerned MBMS selected service within the IE “MBMS Selected Services Short” and the IE “MBMS Modification Period identity” in step 4 and 6.

8.5.5.8 RRC Connection establishment for MBMS Counting :Success after MAC Layer Failure Indication/ MBMS Selected Service

8.5.5.8.1 Definition

This test case is applicable for UEs that support MBMS broadcast services.

8.5.5.8.2 Conformance requirement

The MBMS counting procedure is used by the UE to inform UTRAN about its interest to receive an MBMS transmission. The procedure applies to UEs supporting MBMS that are in idle mode or in connected mode for cells not operating in MBSFN mode as indicated in subclause 8.1.1.6.3.

…

1> if the UE is in idle mode:

2> draw a random number, "rand", uniformly distributed in the range: 0 ≤ rand < 1

2> if ‘rand’ is lower than the value indicated by the IE ‘Access probability factor-Idle’ for the concerned service:

3> indicate to upper layers that establishment of an RRC connection is required to receive the concerned MBMS service, with the establishment cause set to ‘MBMS reception’;

3> if the above condition applies for more than one service, initiate a single indication to upper layers;

3> if the RRC connection establishment succeeds, the procedure ends.

…

1> submit the RRC CONNECTION REQUEST message for transmission on the uplink CCCH;

1> set counter V300 to 1; and

1> if the variable ESTABLISHMENT_CAUSE is set to "MBMS reception":

2> when the MAC layer indicates success or failure to transmit the message:

3> if the MAC layer indicates failure:

4> enter idle mode;

4> consider the procedure to be unsuccessful;

4> perform other actions when entering idle mode from connected mode as specified in subclause 8.5.2;

4> the procedure ends.

3> else:

4> start timer T318;

4> apply value 0 for counter N300 regardless of the value included in IE "UE Timers and Constants in idle mode".

…

The UE shall, in the transmitted RRC CONNECTION REQUEST message:

…

1> otherwise if the UE performs connection establishment for MBMS counting as specified in subclause 8.7.4; and

1> if one or more of the MBMS services for which the UE initiates the counting response concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the counting response:

3> include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and set it to a value in accordance with subclause 8.6.9.8.

1> if the UE included one or more "MBMS Selected Service ID" IEs:

include the IE "MBMS Modification Period identity" and set it to a value in accordance with subclause 8.5.29.

…

If the counting response procedure (RRC connection establishment or Cell update) fails, the UE shall:

1> if the failure occurs in the same modification period as the one in which the UE initiated the counting response procedure; or

1> otherwise:

2> the procedure ends.

Reference

3GPP TS 25.331 clauses 8.7.4, 8.7.4.1, 8.7.4.2, 8.7.4.3, 8.1.3.2, 8.1.3.3, 8.7.4.5.

8.5.5.8.3 Test purpose

To confirm that the UE does not start T318 timer once UE MAC layer indicates un-successful transmission of RRC Connection Request message for MBMS counting.

To verify that the UE continues to acquire MBMS ACCESS INFORMATION messages after MAC layer failure indication for first RRC Connection Request transmission, and hence re-start RRC Connection Request procedure for counting.

8.5.5.8.4 Method of test

Initial Condition

System Simulator: 1 MBMS cell (cell 21).

User Equipment:

The UE is in Idle Mode as specified in clause 7.6 of TS 34.108.

The UE is interested in the selected service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Longest MCCH scheduling configuration defined in 34.108 clause 11.1.1.3 is used.

Related ICS/IXIT statements

– MBMS Broadcast service application available on UE Yes/No.

Test Procedure

The SS transmits an MBMS ACCESS INFORMATION message, which includes the MBMS Short transmission ID associated to the MBMS activated service and “Access probability factor – Idle” set to 0.

NOTE: The “Access probability factor” sent in the MBMS ACCESS INFORMATION message set to 0 corresponds to an actual Probability Factor = 1, according to the formula in TS 25.331 clause 10.2.16e.

The UE submits RRC CONNECTION REQUEST message for transmission, with “Establishment cause” set to “MBMS reception”.

SS does not acknowledge the RACH access on AICH.

After Failure indication by UE MAC Layer, UE Re-acquires MBMS ACCESS INFORMATION, and re-starts the counting procedure. The UE transmits RRC CONNECTION REQUEST message to the SS, with “Establishment cause” set to “MBMS reception”.

The SS transmits an RRC CONNECTION SETUP message to the UE which moves the UE to CELL_DCH state.

When the UE receives this message, the UE establishes an RRC connection and transmits an RRC CONNECTION SETUP COMPLETE message.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				The UE is in idle mode.
1			MBMS MODIFIED SERVICES INFORMATION	The SS transmits the message, which includes “MBMS required UE action” set to “Acquire counting info”
2			MBMS ACCESS INFORMATION	The SS transmits the message, which includes “MBMS short transmission ID” IE referring to the service the UE activated and “Access probability factor – Idle” IE set to 0 (corresponding to actual Access Probability = 1).
3			MBMS GENERAL INFORMATION
4			ACCESS PREAMBLE(RRC CONNECTION REQUEST)
5				SS does not respond to ACCESS PREAMBLE on AICH channel.
6				After Failure indication by MAC Layer, UE starts acquiring MBMS ACCESS INFORMATION
7			RRC CONNECTION REQUEST	The UE re-sends the message with Establishment cause set to “MBMS reception”. (SS ACKS on AICH for ACCESS PREAMBLE)
8			RRC CONNECTION SETUP	SS assigns DPCH resources to allow UE to establish an RRC connection. RRC state indicator set to CELL_DCH.
9			RRC CONNECTION SETUP COMPLETE
9a			MBMS MODIFICATION REQUEST	The UE completing the RRC connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after step 9 and before step 11.
10	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Broadcast service Reception”.
11			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific Message Contents

System Information Block type 1 (FDD)

Use the default system information block with the same type specified in clause 6.1 of TS 34.108, with the following exceptions:

Information Element	Value/remark
– UE Timers and constants in idle mode
-T300	8000 milliseconds

MBMS MODIFIED SERVICES INFORMATION (Step 1)

Information Element	Value/remark
Modified service list	Only 1 entry
– MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
– MBMS required UE action	Acquire counting info
– Continue MCCH reading	TRUE

MBMS ACCESS INFORMATION (Step 2)

Information Element	Value/remark
Service list	Only 1 entry
– MBMS short transmission ID	Index to the MBMS transmission identity in the previous MBMS MODIFIED SERVICES INFORMATION
– Access probability factor – Idle	0 (corresponding to the actual probability factor value 1)

MBMS GENERAL INFORMATION (Step 3)

Use the default message type found in TS 34.108, 9.1.1 except for

MBMS timers and counters
– T318	16000 ms

RRC CONNECTION REQUEST (Step 7)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI.
Establishment Cause	MBMS reception
Protocol Error Indicator	Check to see if it is set to FALSE
Measured results on RACH	Not checked.
MBMS Selected Services
– MBMS Selected Services	Only 1 entry
– MBMS Selected Service ID	MBMS short transmission identity referring to the service the UE has selected
– Modification period identity	Indicates the modification period the MBMS short transmission identities refer to

RRC CONNECTION SETUP (Step 8)

Use the default message type found in TS 34.108, 9.1.1.

RRC CONNECTION SETUP COMPLETE (Step 9)

Use the default message type found in TS 34.108, 9.1.1.

MBMS MODIFICATION REQUEST (steps 9a)

Information Element	Value/remark
MBMS preferred frequency request	Check that the IE is not present
MBMS RB list requested to be released	Check that the IE is not present
MBMS Selected Service Info
– CHOICE Status	Some
– MBMS Selected Services Full
– MBMS Selected Service ID	Only 1 entry
– MBMS Service ID	MBMS service ID of the activated MBMS service
– CHOICE PLMN identity	Check to see that one of the below choice element is present
– SameAs-MIB	(no data)
– explicitPLMN_Id	Check to see if it is set to the same value as "PLMN ID” in the Master Information block transmitted for the current serving cell.

8.5.5.8.5 Test requirement

At step 7, the UE shall transmit an RRC CONNECTION REQUEST message with “Establishment Cause” set to “MBMS reception” on the uplink CCCH and including the IE “MBMS Selected Service ID” of the concerned MBMS selected service within the IE “MBMS Selected Services Short” and the IE “MBMS Modification Period identity”.

The time difference between step 4(last Access Preamble Reception) and 7 should be at least 1280 milliseconds (one AP), and less than 4 seconds (2*AP[1280ms]+Transmission time on PRACH).

At step 9, the UE shall transmit an RRC CONNECTION SETUP COMPLETE message on a dedicated channel.

8.5.5.8m RRC Connection establishment for MBMS Counting :Success after MAC Layer Failure Indication / MBMS Multicast Service

8.5.5.8m.1 Definition

This test is applicable for all UEs that support MBMS multicast services.

8.5.5.8m.2 Conformance requirement

Same conformance requirement as in clause 8.5.5.8.2.

8.5.5.8m.3 Test purpose

Same test purpose as in clause 8.5.5.8.3.

8.5.5.8m.4 Method of test

Initial Condition

System Simulator: 1 MBMS cell (cell 21).

User Equipment:

The UE is in Idle Mode as specified in clause 7.6 of TS 34.108.

The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

– MBMS Multicast service application available on UE Yes/No.

Test procedure

Same test procedure as in clause 8.5.5.8.4, except expected sequence step 9a is not applicable and at step 10 UE transmits Service Request, with IE "Service type" set to "MBMS Multicast service Reception”.

Specific message contents

Same specific messages contents as in clause 8.5.5.8.4 except for RRC CONNECTION REQUEST message content (step 7). Step 9a contents are not applicable.

RRC CONNECTION REQUEST (Step 7)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered P-TMSI.
Establishment Cause	MBMS reception
Protocol Error Indicator	Check to see if it is set to FALSE
Measured results on RACH	Not checked.
MBMS Selected Services	Not present

8.5.5.8m.5 Test requirements

Same Test Requirements as in clause 8.5.5.8.5, except UE shall not include in the IE “MBMS Selected Service ID” of the concerned MBMS selected service within the IE “MBMS Selected Services Short” and the IE “MBMS Modification Period identity” in step 7.