8.5.1 MBMS Session Start

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

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

8.5.1.1 MBMS PTP Session Start at MCCH Acquisition in Idle mode / MBMS Selected Service

8.5.1.1.1 Definition

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

8.5.1.1.2 Conformance requirement

The UE applies the MCCH acquisition procedure to determine the MBMS services available in the cell and to initiate reception of the services that the UE has joined. The procedure applies to all UEs supporting MBMS, irrespective of their state (idle, URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH).

…

If the variable MBMS_ACTIVATED_services is not empty, the UE shall apply the MCCH acquisition procedure upon selecting (e.g. upon power on) or re- selecting a cell supporting MBMS, upon change of MBMS controlling cell (e.g. due to an active set update or hard handover), upon entering UTRA from another RAT, upon release of a MBMS PTP RB for the purpose of changing transfer mode, upon return from loss of coverage and upon receiving an indication from upper layers that the set of activated services has changed.

…

The UE shall detect the available MBMS services by acquiring the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES 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.

The UE shall immediately acquire the MBMS ACCESS INFORMATION and the MBMS GENERAL INFORMATION messages i.e. it shall not delay reception of these messages until it has completed the acquisition of the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages. Likewise, the UE should immediately acquire the MBMS CURRENT CELL P-T-M RB INFORMATION and MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages.

The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information e.g. both the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION message should be acquired in the same modification period.

…

When requested to acquire MBMS control information other than the MBMS Access Information message , the UE shall:

1> if requested to start reading MCCH at the next modification period:

2> start reading MCCH at the beginning of the next modification period.

1> otherwise

2> start reading MCCH at the beginning of the next repetition period.

1> if requested to stop reading MCCH at the end of the modification period:

2> continue reading MCCH until the required MBMS control information is received or until the UE detects a TTI in which no MCCH information is transmitted, whichever is first;

2> continue reading MCCH in this manner at every subsequent repetition period, until the information is received correctly or until the end of the modification period.

1> otherwise:

2> continue reading MCCH until the required MBMS control information is received or until the UE detects a TTI in which no MCCH information is transmitted, whichever is first;

2> continue reading MCCH in this manner at every subsequent repetition period, until the information is received correctly.

NOTE 1: The UE may combine information received at different repetition periods within a modification period.

When requested to acquire the MBMS Access Information message, the UE shall:

1> if requested to start reading MCCH at the next modification period:

2> start reading MCCH at the beginning of the next modification period.

1> otherwise:

2> start reading MCCH at the beginning of the next access info period.

1> continue reading MCCH in this manner at every subsequent access info period, until the message is received correctly or until the end of the modification period.

If the UE is CELL_DCH and has a compressed mode pattern that overlaps with the period in which it needs to read MCCH, the UE may temporarily refrain from receiving MCCH unless it is capable of simultaneous operation. If the UE is CELL_FACH and has a measurement occasion that overlaps with the period in which it needs to read MCCH, the UE may temporarily refrain from receiving MCCH unless it is capable of simultaneous operation. A UE in CELL_FACH may omit performing measurements during a measurement occasion in order to receive MCCH provided that this does not prevent it from fulfilling the measurement performance requirements as specified in [19]. In Idle mode as well as in CELL_PCH and URA_PCH states the UE may temporarily refrain from receiving MCCH if needed to fulfil the measurements performance requirements as specified in [19].

NOTE 2: The UTRAN should endeavour to ensure that for each UE in CELL_FACH the assigned measurement occasions do not overlap constantly with the periodic MCCH transmissions.

If the UE selects to another cell, the UE shall re-establish the RLC entity used for MCCH reception.

…

The UE may:

1> if in idle mode, URA_PCH, CELL_PCH or CELL_FACH state; and

1> if not receiving an MBMS service provided via a p-t-m radio bearer:

2> monitor the MBMS notification Indicator Channel (MICH).

2> if a notification on the MICH for one or more of the MBMS services included in the variable MBMS_ACTIVATED_SERVICES is detected:

3> acquire the MBMS MODIFIED SERVICES INFORMATION message with delaying the 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;

3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.

The UE shall:

1> if in idle mode, URA_PCH, CELL_PCH or CELL_FACH state:

2> if receiving an MBMS service that is provided via a p-t-m radio bearer; or

2> if not receiving an MBMS service that is provided via a p-t-m radio bearer and not monitoring MICH:

3> acquire the MBMS MODIFIED SERVICES INFORMATION message from MCCH at the start of every modification period, in accordance with subclause 8.7.1.3;

3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.

…

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 ‘Request PTP RB’:

2> if the UE is in idle mode:

3> indicate to upper layers that establishment of a PS signalling connection is required to receive the concerned MBMS service [5], unless the UE has already requested p-t-p RB establishment in the current modification period, and use the establishment cause set to ‘MBMS ptp RB request’ in the RRC connection establishment procedure.

…

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

…

1> if the UE performs connection establishment for MBMS ptp radio bearer request as specified in subclause 8.6.9.6; and

1> if one or more of the MBMS services for which the UE initiates the ptp radio bearer request concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the ptp radio bearer request:

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.

…

In the UE, the initial direct transfer procedure shall be initiated, when the upper layers request establishment of a signalling connection. This request also includes a request for the transfer of a NAS message.

Upon initiation of the initial direct transfer procedure the UE shall:

1> set the variable ESTABLISHMENT_CAUSE to the cause for establishment indicated by upper layers.

Upon initiation of the initial direct transfer procedure when the UE is in idle mode, the UE shall:

1> perform an RRC connection establishment procedure, according to subclause 8.1.3;

NOTE: If an RRC connection establishment is ongoing, this procedure continues unchanged, i.e. it is not interrupted.

1> if the RRC connection establishment procedure was not successful:

2> if the establishment cause for the failed RRC connection establishment was set to "MBMS reception" and a different cause value is stored in the variable "ESTABLISHMENT_CAUSE":

3> UE-AS (RRC) initiates a new RRC connection establishment procedure, using the establishment cause as contained in the variable ESTABLISHMENT_CAUSE.

2> otherwise:

3> indicate failure to establish the signalling connection to upper layers and end the procedure.

1> when the RRC connection establishment procedure is completed successfully:

2> continue with the initial direct transfer procedure as below.

Upon initiation of the initial direct transfer procedure when the UE is in CELL_PCH or URA_PCH state, the UE shall:

1> perform a cell update procedure, according to subclause 8.3.1, using the cause "uplink data transmission";

1> when the cell update procedure completed successfully:

2> continue with the initial direct transfer procedure as below.

The UE shall, in the INITIAL DIRECT TRANSFER message:

1> set the IE "NAS message" as received from upper layers; and

1> set the IE "CN domain identity" as indicated by the upper layers; and

1> set the IE "Intra Domain NAS Node Selector" as follows:

2> derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and

2> provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:

1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a valid TMSI/PTMSI is available;

2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;

3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.

1> if the UE, on the existing RRC connection, has received a dedicated RRC message containing the IE "Primary PLMN Identity" in the IE "CN Information Info":

2> set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the latest PLMN information received via dedicated RRC signalling. If NAS has indicated the PLMN towards which a signalling connection is requested, and this PLMN is not in agreement with the latest PLMN information received via dedicated RRC signalling, then the initial direct transfer procedure shall be aborted, and NAS shall be informed.

1> if the UE, on the existing RRC connection, has not received a dedicated RRC message containing the IE "CN Information Info" , and if the IE "Multiple PLMN List" was broadcast in the cell where the current RRC connection was established:

2> set the IE "PLMN identity" in the INITIAL DIRECT TRANSFER message to the PLMN chosen by higher layers [5, 25] amongst the PLMNs in the IE "Multiple PLMN List" broadcast in the cell where the RRC connection was established.

1> if the IE "Activated service list" within variable MBMS_ACTIVATED_SERVICES includes one or more MBMS services with the IE "Service type" set to "Multicast" and;

1> if the IE "CN domain identity" as indicated by the upper layers is set to "CS domain" and;

1> if the variable ESTABLISHED_SIGNALLING_CONNECTIONS does not include the CN domain identity ‘PS domain’:

2> include the IE "MBMS joined information";

2> include the IE "P-TMSI" within the IE "MBMS joined information" if a valid PTMSI is available.

1> if the variable ESTABLISHMENT_CAUSE_ is initialised:

2> set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE;

2> clear the variable ESTABLISHMENT_CAUSE.

1> calculate the START according to subclause 8.5.9 for the CN domain as set in the IE "CN Domain Identity"; and

1> include the calculated START value for that CN domain in the IE "START".

The UE shall:

1> transmit the INITIAL DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB3;

1> when the INITIAL DIRECT TRANSFER message has been submitted to lower layers for transmission:

2> confirm the establishment of a signalling connection to upper layers; and

2> add the signalling connection with the identity indicated by the IE "CN domain identity" in the variable ESTABLISHED_SIGNALLING_CONNECTIONS.

1> when the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC:

2> the procedure ends.

When not stated otherwise elsewhere, the UE may also initiate the initial direct transfer procedure when another procedure is ongoing, and in that case the state of the latter procedure shall not be affected.

A new signalling connection request may be received from upper layers during transition to idle mode. In those cases, from the time of the indication of release to upper layers until the UE has entered idle mode, any such upper layer request to establish a new signalling connection shall be queued. This request shall be processed after the UE has entered idle mode.

…

The UE shall:

1> if the IE "Secondary CCPCH system information MBMS" is included:

2> apply the Secondary CCPCH and FACH indicated by the IE "FACH carrying MCCH" for receiving MCCH.

1> otherwise, if the IE "Secondary CCPCH system information" includes the IE "MCCH configuration information":

2> apply the Secondary CCPCH and FACH indicated by the IE “MCCH configuration information” for receiving MCCH.

…

The UE shall select the Secondary CCPCH for acquiring MCCH information according to the following rules:

1> if System Information Block type 5 or System Information Block type 5bis is defined and includes an S-CCPCH within the IE "Secondary CCPCH system information" including a FACH for which the IE "MCCH configuration information" is included:

2> select that S-CCPCH and FACH for receiving MCCH.

1> otherwise if System Information Block type 5 or System Information Block type 5bis is defined and includes an SCCPCH within the IE "Secondary CCPCH system information MBMS" for which the IE "FACH carrying MCCH" is included:

2> select that S-CCPCH and FACH for receiving MCCH.

Reference

3GPP TS 25.331 clauses 8.7.2, 8.7.1.3, 8.7.3.3.1, 8.6.9.6, 8.1.3.3, 8.1.8.2, 8.1.1.6.5, 8.5.19a.

8.5.1.1.3 Test purpose

To verify that the UE receives the MBMS info in idle mode state and to verify that the UE starts the reception of MBMS services at MCCH acquisition.

8.5.1.1.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 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

Table 8.5.1.1

Parameter	Unit	Cell 21		Cell 22
Parameter	Unit	T0	T1	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency		Mid Range Test Frequency
CPICH Ec (FDD)	dBm/3.84MHz	-60	OFF	-70	-60
P-CCPCH RSCP (TDD)	dBM	-60	OFF	-70	-60

Table 8.5.1.1 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution.

1) The UE is camping on cell 21, the SS configures its downlink transmission power settings according to columns "T1" in table 8.5.1.1, the UE re-selects to cell 22 supporting MBMS (MBMS_ACTIVATED_services is not empty). The SS transmits SYSTEM INFORMATION BLOCK TYPE 5 or 5bis messages including the MCCH configuration specified within the IE "Secondary CCPCH system information" (there is only one S-CCPCH in this cell, SS uses S-CCPCH combination from TS34.108 clause 6.10.2.4.3.9 Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH + SRB for MCCH) mapped on to an S-CCPCH also used for non-MBMS purposes. The UE shall perform the MCCH acquisition procedure:

2) The UE shall detect the available MBMS services by acquiring the MBMS MODIFIED SERVICES INFORMATION, the MBMS UNMODIFIED SERVICES INFORMATION (including both IEs “MBMS required UE action” set to “Request PTP RB”) and the MBMS GENERAL INFORMATION.

3) The UE shall request a p-t-p RB establishment.

4) The SS transmits a RADIO BEARER SETUP message to the UE. This message requests the establishment of a radio access bearer. The UE shall establish this radio bearer. Then the UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC.

5) SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE re-selects to cell 22 supporting MBMS (MBMS service already activated).
1			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis
2			MBMS MODIFIED SERVICES INFORMATION
3				The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information in the same modification period.
4			MBMS UNMODIFIED SERVICES INFORMATION	"MBMS required UE action" set to Request PTP RB.
5			MBMS GENERAL INFORMATION
6			RRC CONNECTION REQUEST	The UE transmits the message with Establishment cause set to “MBMS ptp RB request” and with the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity.
7			RRC CONNECTION SETUP	RRC state indicator set to Cell_FACH
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 14.
9	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Broadcast service Reception”.
10			SECURITY MODE COMMAND
11			SECURITY MODE COMPLETE
12			RADIO BEARER SETUP
13			RADIO BEARER SETUP COMPLETE
14			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 2)

Information Element	Value/remark
Modified services list	Only 1 entry
– MBMS Transmission identity	MBMS Transmission identity (different from the MBMS activated service)
– MBMS required UE action	request PTP RB

MBMS UNMODIFIED SERVICES INFORMATION (Step 4)

Information Element	Value/remark
Unmodified services list	Only 1 entry
– MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
MBMS required UE action	Request PTP RB

RRC CONNECTION REQUEST (Step 6)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI
Establishment Cause	MBMS ptp RB request
Domain indicator	PS domain
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)

Information Element	Value/remark
Message type
Initial UE identity	Set to same value as received in Step 6
RRC State Indicator	Cell_FACH

MBMS MODIFICATION REQUEST (Step 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.

RADIO BEARER SETUP (Step 12)

Use the same message as the one specified for "MBMS PtP" in TS 34.108 clause 9, with the condition B2.

SYSTEM INFORMATION BLOCK TYPE 5 and 5bis (Step1)

As specified in TS 34.108 clause 6.1 and by using condition M2 for SYSTEM INFORMATION BLOCK TYPE 5 message.

8.5.1.1.5 Test requirements

After step 2, after the UE has received a MBMS modified services Information message, the UE continues acquiring the MBMS information.

At step 4, after the UE has received an MBMS unmodified services Information message including the IE “MBMS required UE action” set to Request PTP RB, the UE shall indicate to upper layers that the establishment of an RRC connection is required to receive the concerned MBMS service with the establishment cause set to “MBMS ptp RB request”.

At step 13, the UE shall send a RADIO BEARER SETUP COMPLETE message.

8.5.1.1m MBMS PTP Session Start at MCCH Acquisition in Idle mode / MBMS Multicast Service

8.5.1.1m.1 Definition

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

8.5.1.1m.2 Conformance requirement

Same conformance requirement as in clause 8.5.1.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.2, 8.7.1.3, 8.7.3.3.1, 8.6.9.6, 8.1.8.2, 8.1.1.6.5, 8.5.19a.

8.5.1.1m.3 Test purpose

Same test purpose as in clause 8.5.1.1.3.

8.5.1.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.1.1.4.

Expected sequence

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

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE re-selects to cell 22 supporting MBMS (MBMS service already activated).
1			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis
2			MBMS MODIFIED SERVICES INFORMATION
3				The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information in the same modification period.
4			MBMS GENERAL INFORMATION
5			MBMS UNMODIFIED SERVICES INFORMATION	"MBMS required UE action" set to Request PTP RB.
6			RRC CONNECTION REQUEST	The UE transmits the message with Establishment cause set to “MBMS ptp RB request”.
7			RRC CONNECTION SETUP	RRC state indicator set to Cell_FACH
8			RRC CONNECTION SETUP COMPLETE
9	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Multicast service Reception”.
10			SECURITY MODE COMMAND
11			SECURITY MODE COMPLETE
12			RADIO BEARER SETUP
13			RADIO BEARER SETUP COMPLETE
14			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.1.1.4 except for RRC CONNECTION REQUEST message content (step 6).

RRC CONNECTION REQUEST (Step 6)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI
Establishment Cause	MBMS ptp RB request
Domain indicator	PS domain

8.5.1.1m.5 Test requirements

Same test requirement as in clause 8.5.1.1.5.

8.5.1.2 MBMS PTP Session Start at MCCH Notification in CELL_PCH / MBMS Selected Service

8.5.1.2.1 Definition

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

8.5.1.2.2 Conformance requirement

The MBMS notification procedure is used by the UE to respond to a notification provided by UTRAN, indicating a change applicable for one or more MBMS services the UE has joined. The procedure applies to all UEs supporting MBMS, irrespective of their state (idle and connected mode: URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH). The actual notification mechanism to be used depends on the UE state.

…

The UE shall:

1> if in idle mode, URA_PCH, CELL_PCH or CELL_FACH state:

2> if receiving an MBMS service that is provided via a p-t-m radio bearer; or

2> if not receiving an MBMS service that is provided via a p-t-m radio bearer and not monitoring MICH:

3> acquire the MBMS MODIFIED SERVICES INFORMATION message from MCCH at the start of every modification period, in accordance with subclause 8.7.1.3;

3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.

….

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 ‘Request PTP RB’:

…

2> if the UE is in URA_PCH, Cell_PCH, or CELL_FACH states:

3> perform a cell update procedure with cause "MBMS ptp RB request", as specified in subclause 8.3.1.2, unless the UE has already requested p-t-p RB establishment in the current modification period.

…

A UE shall initiate the cell update procedure in the following cases:

….

1> MBMS ptp RB request:

2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and

2> if the UE is in URA_PCH, Cell_PCH or Cell_FACH state; and

2> if the UE should perform cell update for MBMS ptp radio bearer request as specified in 8.6.9.6:

3> perform cell update using the cause "MBMS ptp RB request".

…

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

…

1> if the UE performs cell update for MBMS ptp radio bearer request as specified in subclause 8.6.9.6; and

1> if one or more of the MBMS services for which the UE initiates the ptp radio bearer request concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates ptp radio bearer request:

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> 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> 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.3.1, 8.7.3.3.1, 8.6.9.6, 8.3.1.2, 8.3.1.3.

8.5.1.2.3 Test purpose

To verify that the UE in Cell_PCH state, correctly handle the Notification procedure after receiving the MODIFIED SERVICES INFORMATION message via MCCH.

8.5.1.2.4 Method of test

Initial condition

System Simulator:

1 MBMS cell

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

1) The UE in Cell_PCH, shall detect the available MBMS services by acquiring the MBMS MODIFIED SERVICES INFORMATION including the IE “MBMS required UE action” set to “Request PTP RB”.

2) The UE shall perform a cell update procedure with cause "MBMS ptp RB request". The UE transmits a CELL UPDATE message 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".

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE is in Cell_PCH state.
1			MBMS MODIFIED SERVICES INFORMATION	"MBMS required UE action" set to Request PTP RB".
2			CELL UPDATE	The UE enters the CELL_FACH state. UE performs cell update procedure. The CELL UPDATE message shall contain the value "Cell Update Cause" set to "MBMS ptp RB request" and the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity.
3			CELL UPDATE CONFIRM
3a			UTRAN MOBILITY INFORMATION CONFIRM
4			RADIO BEARER SETUP
5			RADIO BEARER SETUP COMPLETE
5a			MBMS MODIFICATION REQUEST	This message may be received at any point after step 4 and before step 6.
6			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 services list	Only 1 entry
– MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
– MBMS required UE action	request PTP RB

CELL UPDATE (Step 2)

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

CELL UPDATE CONFIRM (Step 3)

Information Element	Value/remark
New C-RNTI	‘1010 1010 1010 1010’

RADIO BEARER SETUP (Step 4)

Use the same message as the one specified for "MBMS PtP" in TS 34.108 clause 9, with the condition B4.

MBMS MODIFICATION REQUEST (step 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
– 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.1.2.5 Test requirements

At step 2, the UE shall initiate a cell update procedure for MBMS ptp radio bearer request.

8.5.1.2m MBMS PTP Session Start at MCCH Notification in CELL_PCH / MBMS Multicast Service

8.5.1.2m.1 Definition

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

8.5.1.2m.2 Conformance requirement

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

8.5.1.2m.3 Test purpose

Same test purpose as in clause 8.5.1.2.3.

8.5.1.2m.4 Method of test

Initial condition

System Simulator:

1 MBMS cell

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

1) The UE in Cell_PCH, shall detect the available MBMS services by acquiring the MBMS MODIFIED SERVICES INFORMATION including the IE “MBMS required UE action” set to “Request PTP RB”.

2) The UE shall perform a cell update procedure with cause "MBMS ptp RB request".

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
				The UE is in Cell_PCH state.
1			MBMS MODIFIED SERVICES INFORMATION	"MBMS required UE action" set to Request PTP RB".
2			CELL UPDATE	The UE enters the CELL_FACH state. UE performs cell update procedure. The CELL UPDATE message shall contain the value "Cell Update Cause" set to "MBMS ptp RB request"
3			CELL UPDATE CONFIRM
4			RADIO BEARER SETUP
5			RADIO BEARER SETUP COMPLETE
6			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.1.2.4 except for CELL UPDATE message content (step 2).

CELL UPDATE (Step 2)

Information Element	Value/remark
Cell update cause	MBMS ptp RB request

8.5.1.2m.5 Test requirements

Same test requirement as in clause 8.5.1.2.5.

8.5.1.3 MBMS PTM Session Start at MCCH Acquisition in CELL_FACH state / MBMS Broadcast Service

8.5.1.3.1 Definition and applicability

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

8.5.1.3.2 Conformance requirement

If the variable MBMS_ACTIVATED_services is not empty, the UE shall apply the MCCH acquisition procedure upon selecting (e.g. upon power on) or re-selecting a cell supporting MBMS, upon change of MBMS controlling cell (e.g. due to an active set update or hard handover), upon entering UTRA from another RAT, upon release of a MBMS PTP RB for the purpose of changing transfer mode, upon return from loss of coverage and upon receiving an indication from upper layers that the set of activated services has changed.

…

1> if the IE "MBMS required UE action" is set to ‘Acquire PTM RB info’; or

1> if the IE "MBMS required UE action" is set to ‘Acquire counting info– PTM RBs unmodified’ and the UE is not receiving a p-t-m RB for the concerned service:

2> continue acquiring the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB 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

2> act upon the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message, if received, in accordance with subclause 8.7.5;

Reference

3GPP TS 25.331 clauses 8.7.2.2, 8.7.2.3, 8.6.9.6.

8.5.1.3.3 Test purpose

1. To verify that the UE receives the MBMS information on MCCH in CELL_FACH state.

2. To verify that the UE correctly handles the notification procedure after receiving the MBMS MODIFIED SERVICES INFORMATION message via MCCH if no ongoing MBMS p-t-m session (MICH supported/not supported by the UE).

3. To verify that the UE starts the reception of MBMS services according to notification via MICH/MCCH when the UE is in CELL_FACH state.

8.5.1.3.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 is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statement(s)

– MBMS Broadcast service application available on UE Yes/No

Test Procedure

Table 8.5.1.3

Parameter	Unit	Cell 21		Cell 22
Parameter	Unit	T0	T1	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency		Mid Range Test Frequency
CPICH Ec (FDD)	dBm/3.84MHz	-60	OFF	-70	-60
P-CCPCH RSCP (TDD)	dBM	-60	OFF	-70	-60

Table 8.5.1.3 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution.

The UE is in the CELL_FACH state in Cell 21 and is interested in the broadcast service to be provided by the SS.

The SS applies the power settings of “T1” in table 8.5.1.3. The UE shall reselect to Cell 22 and send a CELL UPDATE message. The UE shall perform the MCCH acquisition procedure. The UE shall continue acquiring the MBMS information messages until it has received a consistent set of MCCH information. The UE received an MBMS UNMODIFIED SERVICES INFORMATION message including IE “MBMS required UE action” set to “Acquire PTM RB info”.

The SS waits for the UE to start reception of the MBMS data on MTCH.

The MBMS radio bearer on MTCH is put into loopback mode 3.

The SS sends 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer, then retrieves the number of RLC SDUs on MTCH counted by the UE by sending the UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST message. The number of received RLC SDUs reported by the UE shall be at least one.

The loopback mode 3 in the UE is deactivated.

SS calls for generic procedure C.2 to check that UE is in CELL_FACH state.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				The UE is in Cell_FACH in Cell 21
1			ACTIVATE RB TEST MODE
2			ACTIVATE RB TEST MODE COMPLETE
				SS reconfigures itself according to the settings stated in column "T1" of table 8.5.3.5-1.
3			CELL UPDATE	This message is transmitted in Cell 22
4			CELL UPDATE CONFIRM
5			MBMS UNMODIFIED SERVICES INFORMATION	MBMS required UE action set to ‘Acquire PTM info’
6			CLOSE UE TEST LOOP
7			CLOSE UE TEST LOOP COMPLETE	Loop back mode 3 on MTCH is activated.
8	SS			The SS broadcasts 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer.
9			UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST
10			UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE	The SS checks that the UE has received MBMS data.
11			OPEN UE TEST LOOP
12			OPEN UE TEST LOOP COMPLETE
13			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

MBMS UNMODIFIED SERVICES INFORMATION (Step 5)

Information Element	Value/remark
Unmodified service list
– MBMS Transmission identity	MBMS Transmission identity indicating MBMS activated service
– MBMS required UE action	Acquire PTM RB info

UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE (Step 10)

Information Element	Value/remark
RLC SDU Counter Value	Check that the number is greater than zero.

8.5.1.3.5 Test requirement

After step 9, the UE shall transmit a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message with the number of reported RLC SDUs shall be greater than zero.

8.5.1.3m MBMS PTM Session Start at MCCH Acquisition in CELL_FACH state / MBMS Multicast Service

8.5.1.3m.1 Definition

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

8.5.1.3m.2 Conformance requirement

Same conformance requirement as in clause 8.5.1.3.2.

8.5.1.3m.3 Test purpose

Same test purpose as in clause 8.5.1.3.3.

8.5.1.3m.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.1.3.4.

Specific message contents

Same specific messages contents as in clause 8.5.1.3.4.

8.5.1.3m.5 Test requirements

Same test requirement as in clause 8.5.1.3.5.

8.5.1.4 MBMS PTM Session Start at MCCH Notification in CELL_DCH state / MBMS Broadcast Service

8.5.1.4.1 Definition

This test case is applicable for all UEs that support MBMS broadcast services and support MBMS p-t-m reception in CELL_DCH state.

8.5.1.4.2 Conformance requirement

…

1> if the IE "MBMS required UE action" is set to ‘Acquire PTM RB info’; or

1> if the IE "MBMS required UE action" is set to ‘Acquire counting info– PTM RBs unmodified’ and the UE is not receiving a p-t-m RB for the concerned service:

2> act upon the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message, if received, in accordance with subclause 8.7.5;

Reference

3GPP TS 25.331 clauses 8.7.2.3, 8.7.3.3.1, 8.6.9.6.

8.5.1.4.3 Test purpose

1 To verify that the UE handles reading of MCCH during compressed mode measurements in CELL_DCH state if the UE requires compressed mode.

2. To verify that the UE correctly handles the notification procedure after receiving the MBMS MODIFIED SERVICES INFORMATION message via MCCH in CELL_DCH state.

3. To verify that the UE starts the p-t-m reception of MBMS services according to notification via MCCH when the UE is in CELL_DCH state.

8.5.1.4.4 Method of test

Initial Condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 24

User Equipment:

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

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

Related ICS/IXIT statement(s)

– MBMS Broadcast service application available on UE Yes/No

– UE supports MBMS p-t-m reception in CELL_DCH state Yes/No

– Compressed mode required Yes/No

Test Procedure

Table 8.5.1.4

Parameter	Unit	Cell 21		Cell 24
Parameter	Unit	T0	T1	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency		High Range Test Frequency
CPICH Ec (FDD)	dBm/3.84MHz	-60	-70	-70	-60
P-CCPCH RSCP (TDD)	dBm	-60	-70	-70	-60

The UE is in the CELL_DCH state in cell 21 and has selected the broadcast service to be provided by the SS.

The SS configures then compressed mode (if required), to prepare the UE for inter-frequency measurements, by sending a PHYSICAL CHANNEL RECONFIGURATION message on DCCH using AM-RLC. The UE shall answer with a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.

The SS then sets up inter-frequency measurements (event 2b), by sending a MEASUREMENT CONTROL message to the UE. Compressed mode is started at the same time in that message (if required).

The SS notifies on MCCH about the start of an MBMS session. The SS waits for the UE to start reception of the MBMS data on MTCH and then the MBMS radio bearer on MTCH is put into loopback mode 3.

The SS sends 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer. The SS then applies the power settings according to column “T1” in table 8.5.1.4. The UE transmits a MEASUREMENT REPORT message to the SS.

The SS retrieves the number of RLC SDUs on MTCH counted by the UE by sending the UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST message. The number of received RLC SDUs reported by the UE shall be at least one.

The loopback mode 3 in the UE is deactivated.

SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.

NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
	UE	SS	Message	Comment
1			ACTIVATE RB TEST MODE
2			ACTIVATE RB TEST MODE COMPLETE	If compressed mode is not required (refer ICS/IXIT), goto step 5.
3			PHYSICAL CHANNEL RECONFIGURATION	The SS downloads the compressed mode parameters in the UE.
4			PHYSICAL CHANNEL RECONFIGURATION COMPLETE	The UE acknowledges the downloading of the compressed mode parameters.
5			MEASUREMENT CONTROL	The SS configures inter-frequency measurements in the UE, and If compressed mode is required (refer ICS/IXIT) activates compressed mode.
6			MBMS MODIFIED SERVICES INFORMATION	MBMS session start.
7	SS			The SS waits for the UE to start MTCH reception according to the activation time.
8			CLOSE UE TEST LOOP
9			CLOSE UE TEST LOOP COMPLETE	Loop back mode 3 on MTCH is activated.
10	SS			The SS sends 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer.
11				The SS changes the power of the cells according to column T1 in table 8.5.1.4.
12			MEASUREMENT REPORT	Cell 24 triggers event 2b in the UE, which sends a MEASUREMENT REPORT message to the SS.
13			UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST
14			UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE	The SS checks that the UE has received MBMS data.
15			OPEN UE TEST LOOP
16			OPEN UE TEST LOOP COMPLETE
17			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

PHYSICAL CHANNEL RECONFIGURATION (Step 3)

The contents of PHYSICAL CHANNEL RECONFIGURATION message in this test case is identical to the message sub-type titled as "Packet to CELL_DCH from CELL_DCH in PS" as found in [9] TS 34.108 clause 9, with the following exceptions:

Information Element	Value/Remark	Version
Downlink information common for all radio links
– Downlink DPCH info common for all RL	Not Present
– DPCH compressed mode info
– TGPSI	1
– TGPS Status Flag	Deactivate
– TGCFN	Not present
– Transmission gap pattern sequence configuration parameters
– TGMP	FDD Measurement
– TGPRC	Infinity
– TGSN	8
– TGL1	14
– TGL2	Not Present
– TGD	undefined
– TGPL1	4
– RPP	Mode 0
– ITP	Mode 0
– CHOICE UL/DL Mode	UL and DL, UL only or DL only (depending on the UE capability)
– Downlink compressed mode method	SF/2
– Uplink compressed mode method	SF/2
– Downlink frame type	11B
– DeltaSIR1	20 (2.0)
– DeltaSIRAfter1	10 (1.0)
– DeltaSIR2	Not Present
– DeltaSIRAfter2	Not Present
– N identify abort	Not Present
– T Reconfirm abort	Not Present
– TX Diversity mode	Not Present
– Default DPCH Offset Value	Not Present
Downlink information per radio link list
– Choice mode	FDD
– Primary CPICH info
– Primary scrambling code	Ref. to the Default setting in clause 6.1 (FDD)
– PDSCH with SHO DCH info	Not Present	R99 and Rel-4 only
– PDSCH code mapping	Not Present	R99 and Rel-4 only
– Serving HS-DSCH radio link indicator	FALSE	Rel-5
– Serving E-DCH radio link indicator	FALSE	Rel-6
– Downlink DPCH info for each RL
– CHOICE mode	FDD
– Primary CPICH usage for channel estimation	Primary CPICH may be used
– DPCH frame offset	Set to value : Default DPCH Offset Value (as currently stored in SS) mod 38 400
– Secondary CPICH info	Not Present
– DL channelisation code
– Secondary scrambling code	5
– Spreading factor	Reference to clause 6.10 Parameter Set
– Code number	0
– Scrambling code change	Set to value default1: No code change (if the UE has a compressed mode pattern sequence configured in variable TGPS_IDENTITY or included in the message including IE "Downlink DPCH info for each RL", which is using compressed mode method "SF/2")
– TPC combination index	0
– SSDT Cell Identity	Not Present	R99 and Rel-4 only
– Closed loop timing adjustment mode	Not Present
– E-AGCH Info	Not Present	Rel-6
– E-HICH Information	Not Present	Rel-6
– E-RGCH Information	Not Present	Rel-6
– SCCPCH information for FACH	Not Present	R99 and Rel-4 only

MEASUREMENT CONTROL (Step 5)(FDD)

Information Element	Value/Remark
Measurement Identity	2
Measurement Command	Setup
Measurement Reporting Mode
– Measurement Reporting Transfer Mode	Acknowledged Mode RLC
– Periodical Reporting / Event Trigger Reporting Mode	Event Trigger
Additional measurements list	Not Present
CHOICE measurement type	Inter-frequency measurement
– Inter-frequency cell info list
– CHOICE inter-frequency cell removal	No inter-frequency cells removed
– New inter-frequency info list	1 inter-frequency cell
– Inter-frequency cell id	24
– Frequency info	Set to the frequency of cell 24
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not present
– Read SFN Indicator	FALSE
– CHOICE Mode	FDD
– Primary CPICH Info
– Primary Scrambling Code	Scrambling code of cell 24
– Primary CPICH TX power	Not Present
– TX Diversity Indicator	FALSE
– Cells for measurement	Not present
– Inter-frequency measurement quantity
– CHOICE reporting criteria	Inter-frequency reporting criteria
– Filter Coefficient	0
– Measurement quantity for frequency quality estimate	CPICH RSCP
– Inter-frequency reporting quantity
– UTRA Carrier RSSI	FALSE
– Frequency quality estimate	FALSE
– Non frequency related cell reporting quantities
– SFN-SFN observed time difference reporting indicator	No report
– Cell synchronisation information reporting indicator	FALSE
– Cell Identity reporting indicator	FALSE
– CPICH Ec/No reporting indicator	TRUE
– CPICH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Measurement validity
– UE State	CELL_DCH
– Inter-frequency set update
– UE autonomous update	On with no reporting
– Non autonomous update mode	Not present
– CHOICE report criteria	Inter-frequency measurement reporting criteria
– Parameters required for each event
– Inter-frequency event identity	2b
– Threshold used frequency	-65 dBm
– W used frequency	0 (0.0)
– Hysteresis	2 (1.0 dB)
– Time to trigger	100 ms
– Reporting cell status	Report cells within monitored and/or virtual active set on non-used frequency
– Maximum number of reported cells per reported non-used frequency	1
– Parameters required for each non-used frequency
– Threshold non used frequency	-65 dBm
– W non-used frequency	0
DPCH compressed mode status info	If the UE requires compressed mode (refer ICS/IXIT), this IE is present and contains the IEs as follows. If the UE does not require compressed mode (refer ICS/IXIT), this IE is not present.
– TGPS reconfiguration CFN	((Current CFN + (256 – TTI/10msec))mod 256
– Transmission gap pattern sequence
– TGPSI	1
– TGPS Status Flag	Activate
– TGCFN	(Current CFN + (256 – TTI/10msec))mod 256

MEASUREMENT CONTROL (Step 5)( 3.84Mcps, 1.28Mcps and 7.68Mcps TDD)

Information Element	Value/Remark
Measurement Identity	2
Measurement Command	Setup
Measurement Reporting Mode
– Measurement Reporting Transfer Mode	Acknowledged Mode RLC
– Periodical Reporting / Event Trigger Reporting Mode	Event Trigger
Additional measurements list	Not Present
CHOICE measurement type	Inter-frequency measurement
– Inter-frequency cell info list
– CHOICE inter-frequency cell removal	No inter-frequency cells removed
– New inter-frequency info list	1 inter-frequency cell
– Inter-frequency cell id	24
– Frequency info	Set to the frequency of cell 24
– Cell info
– Cell individual offset	0 (0 dB)
– Reference time difference to cell	Not present
– Read SFN Indicator	FALSE
– CHOICE Mode	TDD
– Primary CCPCH Info
– CHOICE Mode	TDD
– CHOICE TDD option	1.28Mcps TDD
-TSTD indicator	FALSE
– Cell parameters ID	Set to same code as used for cell 24
– SCTD indicator	FALSE
– Primary CCPCH Tx power	Not present
– Timeslot list	Not present
– Cells for measurement	Not present
– Inter-frequency measurement quantity
– CHOICE reporting criteria	Inter-frequency reporting criteria
– Filter Coefficient	0
– Measurement quantity for frequency quality estimate	PCCPCH RSCP
– Inter-frequency reporting quantity
– UTRA Carrier RSSI	FALSE
– Frequency quality estimate	FALSE
– Non frequency related cell reporting quantities
– SFN-SFN observed time difference reporting indicator	No report
– Cell synchronisation information reporting indicator	FALSE
– Cell Identity reporting indicator	FALSE
– CHOICE mode	TDD
– Timeslot ISCP reporting indicator	FALSE
– Proposed TGSN Reporting required	FALSE
– Primary CCPCH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Measurement validity
– UE State	CELL_DCH
– Inter-frequency set update	Not present
– CHOICE report criteria	Inter-frequency measurement reporting criteria
– Parameters required for each event
– Inter-frequency event identity	2b
– Threshold used frequency	-65 dBm
– W used frequency	0 (0.0)
– Hysteresis	2 (1.0 dB)
– Time to trigger	100 ms
– Reporting cell status	Report cells within monitored and/or virtual active set on non-used frequency
– Maximum number of reported cells per reported non-used frequency	1
– Parameters required for each non-used frequency
– Threshold non used frequency	-65 dBm
– W non-used frequency	0.0
DPCH compressed mode status info	Not Present

MEASUREMENT REPORT (Step 12)(FDD)

Information Element	Value/Remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
Measurement identity	2
Measured Results
– Inter-frequency measured results list
– Frequency info
– UARFCN uplink	The presence of this IE is not checked
– UARFCN downlink	Check that the value of this IE is set to the downlink UARFN of cell 24
– UTRA carrier RSSI	Check that this IE is absent
– Inter-frequency cell measurement results	Check that the value of this IE is set to 1 cell reported
– Cell measured results
– Cell Identity	Check that this IE is absent
– SFN-SFN observed time difference	Check that this IE is absent
– Cell synchronisation information	Check that this IE is absent
– Primary CPICH info
– Primary scrambling code	Check that the value of this IE is set to Scrambling code of cell 24
– CPICH Ec/N0	Check that this IE is present
– CPICH RSCP	Check that this IE is present
– Pathloss	Check that this IE is absent
Measured results on RACH	Check that this IE is absent
Additional measured results	Check that this IE is absent
Event results
– Inter-frequency measurement event results
– Inter-frequency event identity	2b
– Inter-frequency cells
– Frequency info
– UARFCN uplink	The presence of this IE is not checked
– UARFCN downlink	Check that the value of this IE is set to the downlink UARFN of cell 24
– Non freq related measurement event results
– Primary CPICH info
– Primary scrambling code	Check that the value of this IE is set to Scrambling code of cell 24

MEASUREMENT REPORT (Step 12) (1.28Mcps TDD)

Information Element	Value/Remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
Measurement identity	2
Measured Results
– Inter-frequency measured results list
– Frequency info
– CHOICE mode	TDD
– UARFCN	Check that the value of this IE is set to the UARFN of cell 24
– UTRA carrier RSSI	Check that this IE is absent
– Inter-frequency cell measurement results	Check that the value of this IE is set to 1 cell reported
– Cell measured results
– Cell Identity	Check that this IE is absent
– SFN-SFN observed time difference	Check that this IE is absent
– Cell synchronisation information	Check that this IE is absent
– CHOICE mode	TDD
– Cell parameters Id	Check to see if it’s the same for cell 24
– Proposed TGSN	Check that this IE is absent
– Primary CCPCH Info	Check that this IE is present
– PCCPCH RSCP	Check that this IE is present
– Pathloss	Check that this IE is absent
-Timeslot list	Check that this IE is absent
Measured results on RACH	Check that this IE is absent
Additional measured results	Check that this IE is absent
Event results
– Inter-frequency measurement event results
– Inter-frequency event identity	2b
– Inter-frequency cells
– Frequency info
– UARFCN	Check that the value of this IE is set to the UARFN of cell 24
– Non freq related measurement event results	Cell measurement event results
– CHOICE mode	TDD
– Primary CCPCH info
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– TSTD indicator	FALSE
– Cell parameters ID	Check to see if set to the same for cell 24
– SCTD indicator	FALSE

MEASUREMENT REPORT (Step 12) (3.84Mcps TDD)

Information Element	Value/Remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
Measurement identity	2
Measured Results
– Inter-frequency measured results list
– Frequency info
– CHOICE mode	TDD
– UARFCN	Check that the value of this IE is set to the UARFN of cell 4
– UTRA carrier RSSI	Check that this IE is absent
– Inter-frequency cell measurement results	Check that the value of this IE is set to 1 cell reported
– Cell measured results
– Cell Identity	Check that this IE is absent
– SFN-SFN observed time difference	Check that this IE is absent
– Cell synchronisation information	Check that this IE is absent
– CHOICE mode	TDD
– Cell parameters Id	Check to see if it’s the same for cell 4
– Proposed TGSN	Check that this IE is absent
– Primary CCPCH Info	Check that this IE is present
– PCCPCH RSCP	Check that this IE is present
– Pathloss	Check that this IE is absent
-Timeslot list	Check that this IE is absent
Measured results on RACH	Check that this IE is absent
Additional measured results	Check that this IE is absent
Event results
– Inter-frequency measurement event results
– Inter-frequency event identity	2b
– Inter-frequency cells
– Frequency info
– UARFCN	Check that the value of this IE is set to the UARFN of cell 4
– Non freq related measurement event results
– CHOICE mode	TDD
– Primary CCPCH info
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps TDD
– CHOICE SyncCase	Sync Case 2
– Timeslot	0
– Cell parameters ID	Check to see if set to the same for cell 4
– SCTD indicator	FALSE

MEASUREMENT REPORT (Step 12) (7.68Mcps TDD)

Information Element	Value/Remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
Measurement identity	2
Measured Results
– Inter-frequency measured results list
– Frequency info
– CHOICE mode	TDD
– UARFCN	Check that the value of this IE is set to the UARFN of cell 4
– UTRA carrier RSSI	Check that this IE is absent
– Inter-frequency cell measurement results	Check that the value of this IE is set to 1 cell reported
– Cell measured results
– Cell Identity	Check that this IE is absent
– SFN-SFN observed time difference	Check that this IE is absent
– Cell synchronisation information	Check that this IE is absent
– CHOICE mode	TDD
– Cell parameters Id	Check to see if it’s the same for cell 4
– Proposed TGSN	Check that this IE is absent
– Primary CCPCH Info	Check that this IE is present
– PCCPCH RSCP	Check that this IE is present
– Pathloss	Check that this IE is absent
-Timeslot list	Check that this IE is absent
Measured results on RACH	Check that this IE is absent
Additional measured results	Check that this IE is absent
Event results
– Inter-frequency measurement event results
– Inter-frequency event identity	2b
– Inter-frequency cells
– Frequency info
– UARFCN	Check that the value of this IE is set to the UARFN of cell 4
– Non freq related measurement event results
– CHOICE mode	TDD
– Primary CCPCH info
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps TDD
– CHOICE SyncCase	Sync Case 2
– Timeslot	0
– Cell parameters ID	Check to see if set to the same for cell 4
– SCTD indicator	FALSE

UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE (Step 14)

Information Element	Value/remark
RLC SDU Counter Value	Check that the number is greater than zero.

8.5.1.4.5 Test requirement

After step 3, if compression is required, the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.

After step 11, the UE shall transmit a MEASUREMENT REPORT message with cell 24 as the reported cell. After step 13, the UE shall transmit a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message with the number of reported RLC SDUs shall be greater than zero.

8.5.1.4m MBMS PTM Session Start at MCCH Notification in CELL_DCH state / MBMS Multicast Service

8.5.1.4m.1 Definition

This test is applicable for all UEs that support MBMS multicast services and support MBMS p-t-m reception in CELL_DCH state.

8.5.1.4m.2 Conformance requirement

Same conformance requirement as in clause 8.5.1.4.2

8.5.1.4m.3 Test purpose

Same test purpose as in clause 8.5.1.4.3.

8.5.1.4m.4 Method of test

Initial condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 24.

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 MBMS p-t-m reception in CELL_DCH state Yes/No

Test procedure

Same test procedure as in clause 8.5.1.4.4.

Specific message contents

Same specific messages contents as in clause 8.5.1.4.4

8.5.1.4m.5 Test requirements

Same test requirement as in clause 8.5.1.4.5.

8.5.1.5 MBMS PTM Session Start at MCCH Acquisition in CELL_DCH (for a non-MBMS service) when entering into an MBMS cell (UE capable of MBMS p-t-m reception in CELL_DCH) / MBMS Broadcast Service

8.5.1.5.1 Definition and applicability

This test case is applicable for all UEs that support MBMS broadcast services and support MBMS p-t-m reception in CELL_DCH state.

8.5.1.5.2 Conformance requirement

…

1> if the IE "MBMS required UE action" is set to ‘Acquire PTM RB info’; or

1> if the IE "MBMS required UE action" is set to ‘Acquire counting info– PTM RBs unmodified’ and the UE is not receiving a p-t-m RB for the concerned service:

2> act upon the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message, if received, in accordance with subclause 8.7.5;

Reference

3GPP TS 25.331 clauses 8.7.2.3, 8.7.3.3.1, 8.6.9.6.

8.5.1.5.3 Test purpose

1. To verify that the UE receives the MBMS information on MCCH in CELL_DCH state.

2. To verify that the UE, when entering into an MBMS cell in CELL_DCH state, starts the p-t-m reception of MBMS services according to the information on MCCH.

8.5.1.5.4 Method of test

Initial Condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 24.

User Equipment:

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

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

Related ICS/IXIT statement(s)

– MBMS Broadcast service application available on UE Yes/No

– UE supports MBMS p-t-m reception in CELL_DCH state Yes/No

Test Procedure

Table 8.5.1.5

Parameter	Unit	Cell 21		Cell 24
Parameter	Unit	T0	T1	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency		High Range Test Frequency
CPICH Ec (FDD)	dBm/3.84MHz	-60	-70	-70	-60
P-CCPCH RSCP (TDD)	dBm	-60	-70	-70	-60

Table 8.5.1.5 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution.

The UE is in the CELL_DCH state in cell 21 and has selected the broadcast service or joined the multicast service to be provided by the SS. The SS has configured its downlink transmission power setting according to columns "T0" in table 8.5.1.5.

The SS then configures its downlink transmission power setting according to columns "T1" in table 8.5.1.5 and transmits a PHYSICAL CHANNEL RECONFIGURATION message to the UE ordering the UE to change to Cell 24 on frequency Ch 2. At the activation time the UE changes to Cell 24 and transmits a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message using AM RLC.

The SS waits for the UE to start reception of the MBMS data on MTCH and then the MBMS radio bearer on MTCH is put into loopback mode 3.

The SS sends 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer. The SS retrieves the number of RLC SDUs on MTCH counted by the UE by sending the UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST message. The number of received RLC SDUs reported by the UE shall be at least one.

The loopback mode 3 in the UE is deactivated.

SS calls for generic procedure C.3 to check that UE is in CELL_DCH state.

NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1			ACTIVATE RB TEST MODE
2			ACTIVATE RB TEST MODE COMPLETE
3				The SS changes the power of the cells according to column T1 in table 8.5.1.5.
4			PHYSICAL CHANNEL RECONFIGURATION	The SS instructs the UE to change to Cell 24.
5			PHYSICAL CHANNEL RECONFIGURATION COMPLETE
6	SS			The SS waits for the UE to activate MTCH reception in cell 24.
7			CLOSE UE TEST LOOP
8			CLOSE UE TEST LOOP COMPLETE	Loop back mode 3 on MTCH is activated.
9	SS			The SS broadcasts 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer.
10			UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST
11			UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE	The SS checks that the UE has received MBMS data.
12			OPEN UE TEST LOOP
13			OPEN UE TEST LOOP COMPLETE
14			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

PHYSICAL CHANNEL RECONFIGURATION (Step 4) (FDD)

Use the same message as specified for "Packet to CELL_DCH from CELL_DCH in PS" in 34.108 except for the following:

Information Element	Value/remark	Version
Frequency info	Set to the frequency of cell 24
Downlink information per radio link list	1 radio link
Downlink information for each radio link
– CHOICE mode	FDD
– Primary CPICH info	Set to the scrambling code for cell 24

PHYSICAL CHANNEL RECONFIGURATION (Step 4) (3.84Mcps, 1.28Mcps and 7.68Mcps TDD)

Use the same message as specified for "Packet to CELL_DCH from CELL_DCH in PS" in 34.108 except for the following:

Information Element	Value/remark	Version
Frequency info	Set to the frequency of cell 24
Downlink information per radio link list	1 radio link
– Downlink information for each radio link
– CHOICE mode	TDD
– Primary CCPCH info	Set to same code as used for cell 24

UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE (Step 11)

Information Element	Value/remark
RLC SDU Counter Value	Check that the number is greater than zero.

8.5.1.5.5 Test requirement

After step 4, the UE shall transmit a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message in cell 24.

After step 10, the UE shall transmit a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message with the number of reported RLC SDUs shall be greater than zero.

8.5.1.5m MBMS PTM Session Start at MCCH Acquisition in CELL_DCH (for a non-MBMS service) when entering into an MBMS cell (UE capable of MBMS p-t-m reception in CELL_DCH) / MBMS Multicast Service

8.5.1.5m.1 Definition

This test is applicable for all UEs that support MBMS multicast services and support MBMS p-t-m reception in CELL_DCH state.

8.5.1.5m.2 Conformance requirement

Same conformance requirement as in clause 8.5.1.5.2

8.5.1.5m.3 Test purpose

Same test purpose as in clause 8.5.1.5.3.

8.5.1.5m.4 Method of test

Initial condition

System Simulator:

2 MBMS cells, Cell 21 and Cell 24.

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.

Test procedure

Same test procedure as in clause 8.5.1.5.4.

Specific message contents

Same specific messages contents as in clause 8.5.1.5.4

8.5.1.5m.5 Test requirements

Same test requirement as in clause 8.5.1.5.5.

8.5.1.6 Void

8.5.1.6m Void

8.5.1.7 Void

8.5.1.7m Void

8.5.1.8 Void

8.5.1.9 MBMS PTM Session Start at MCCH Notification in Idle Mode / MBMS Broadcast Service

8.5.1.9.1 Definition and applicability

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

8.5.1.9.2 Conformance requirement

…

The UE may:

1> monitor the MBMS notification Indicator Channel (MICH);

1> if a notification on the MICH for one or more of the MBMS services included in the variable MBMS_ACTIVATED_SERVICES is detected:

2> acquire the MBMS MODIFIED SERVICES INFORMATION message with delaying the 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;

2> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.

The UE shall:

1> if in idle mode, URA_PCH, CELL_PCH or CELL_FACH state:

2> if not monitoring MICH:

3> acquire the MBMS MODIFIED SERVICES INFORMATION message from MCCH at the start of every modification period, in accordance with subclause 8.7.1.3;

3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.

…

1> if the IE "MBMS required UE action" is set to ‘Acquire PTM RB info’; or

1> if the IE "MBMS required UE action" is set to ‘Acquire counting info– PTM RBs unmodified’ and the UE is not receiving a p-t-m RB for the concerned service:

2> act upon the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message, if received, in accordance with subclause 8.7.5.

Reference

3GPP TS 25.331 clause 8.7.2.3, 8.7.3.3.1, 8.6.9.6.

8.5.1.9.3 Test purpose

1. To verify that the UE receives the MBMS information on MCCH in Idle Mode.

3. To verify that the UE starts the reception of MBMS services according to notification via MICH/MCCH when the UE is in Idle Mode.

8.5.1.9.4 Method of test

Initial Condition

System Simulator:

– 1 MBMS cell.

User Equipment:

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

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

Related ICS/IXIT statement(s)

– MBMS Broadcast service application available on UE Yes/No

Test Procedure

UE is moved to CELL_DCH for RB Test Mode to be activated and then the RRC Connection is released to move UE back to Idle Mode.

The SS notifies on MICH and MCCH about the start of an MBMS session. The SS waits for the UE to start reception of the MBMS data on MTCH.

UE is moved to CELL_DCH for the UE Test Loop Mode 3 to be closed and then the RRC Connection is released to move UE back to Idle Mode.

The SS sends 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer.

UE is moved to CELL_DCH then retrieves the number of RLC SDUs on MTCH counted by the UE by sending the UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST message. The number of received RLC SDUs reported by the UE shall be at least one.

The UE Test Loop is opened and RB Test Mode in the UE is deactivated.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1			PAGING TYPE1	Paging (PS domain, P-TMSI)
2			RRC CONNECTION REQUEST
3			RRC CONNECTION SETUP
4			RRC CONNECTION SETUP COMPLETE
5			SERVICE REQUEST
6			AUTHENTICATION AND CIPHERING REQUEST
7			AUTHENTICATION AND CIPHERING RESPONSE
8			SECURITY MODE COMMAND
9			SECURITY MODE COMPLETE
10			ACTIVATE RB TEST MODE
11			ACTIVATE RB TEST MODE COMPLETE
12			RRC CONNECTION RELEASE
13			RRC CONNECTION RELEASE COMPLETE
14			MBMS MODIFIED SERVICES INFORMATION	MBMS session start. The SS also sets the Notification Indicator on MICH. The SS waits for the UE to establish the MTCH according to MBMS p-t-m activation time set to the first TTI of the next modification period.
15			PAGING TYPE1 (PCCH)	Paging (PS domain, P-TMSI)
16			RRC CONNECTION REQUEST
17			RRC CONNECTION SETUP
18			RRC CONNECTION SETUP COMPLETE
19			SERVICE REQUEST
20			AUTHENTICATION AND CIPHERING REQUEST
21			AUTHENTICATION AND CIPHERING RESPONSE
22			SECURITY MODE COMMAND
23			SECURITY MODE COMPLETE
24			CLOSE UE TEST LOOP
25			CLOSE UE TEST LOOP COMPLETE	Loop back mode 3 on MTCH is activated.
26			RRC CONNECTION RELEASE
27			RRC CONNECTION RELEASE COMPLETE
28	SS			The SS broadcasts 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer.
29			PAGING TYPE1	Paging (PS domain, P-TMSI)
30			RRC CONNECTION REQUEST
31			RRC CONNECTION SETUP
32			RRC CONNECTION SETUP COMPLETE
33			SERVICE REQUEST
34			AUTHENTICATION AND CIPHERING REQUEST
35			AUTHENTICATION AND CIPHERING RESPONSE
36			SECURITY MODE COMMAND
37			SECURITY MODE COMPLETE
38			UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST
39			UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE	The SS checks that the UE has received MBMS data.
40			OPEN UE TEST LOOP
41			OPEN UE TEST LOOP COMPLETE
42			DEACTIVATE RB TEST MODE
43			DEACTIVATE RB TEST MODE COMPLETE

Specific Message Contents

UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE (Step 39)

Information Element	Value/remark
RLC SDU Counter Value	Check that the number is greater than zero.

8.5.1.9.5 Test requirement

After step 38, the UE shall transmit a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message with the number of reported RLC SDUs shall be greater than zero.

8.5.1.9m MBMS PTM Session Start at MCCH Notification in Idle Mode / MBMS Multicast Service

8.5.1.9m.1 Definition

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

8.5.1.9m.2 Conformance requirement

Same conformance requirement as in clause 8.5.1.9.2

8.5.1.9m.3 Test purpose

Same test purpose as in clause 8.5.1.9.3.

8.5.1.9m.4 Method of test

Initial Condition

System Simulator:

– 1 MBMS cell.

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.1.9.4.

Specific message contents

Same specific messages contents as in clause 8.5.1.9.4

8.5.1.9m.5 Test requirements

Same test requirement as in clause 8.5.1.9.5.

8.5.1.10 Void

8.5.1.11 MBMS PTP Session Start at MCCH Notification in Idle Mode / MBMS Selected Service

8.5.1.11.1 Definition

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

8.5.1.11.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 ‘Request PTP RB’:

2> if the UE is in idle mode:

3> indicate to upper layers that establishment of a PS signalling connection is required to receive the concerned MBMS [5], unless the UE has already requested p-t-p RB establishment in the current modification period, and use the establishment cause set to ‘MBMS ptp RB request’ in the RRC connection establishment procedure.

…

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

1> set the IE "Establishment cause" to the value of the variable ESTABLISHMENT_CAUSE;

1> set the IE "Initial UE identity" to the value of the variable INITIAL_UE_IDENTITY;

1> set the IE "Protocol error indicator" to the value of the variable PROTOCOL_ERROR_INDICATOR; and

1> include the IE "Predefined configuration status information" and set this IE to true if the UE has all pre- configurations stored with the same value tag as broadcast in the cell in which the RRC connection establishment is initiated.

1> if the UE is attempting to establish the signalling connection to PS-domain:

include the IE "Domain Indicator" and set it to "PS domain".
else if the UE is attempting to establish the signalling connection to CS domain:

2> include the IE "Domain Indicator" and set it to "CS domain".

1> if the UE only supports HS-DSCH but not E-DCH:

2> include the IE "UE capability indication" and set it to the "HS-DSCH" value.

1> if the UE supports HS-DSCH and E-DCH:

2> include the IE "UE capability indication" and set it to the "HS-DSCH+E-DCH" value.

1> if the UE performs connection establishment for MBMS ptp radio bearer request as specified in subclause 8.6.9.6; and

1> if one or more of the MBMS services for which the UE initiates the ptp radio bearer request concerns an MBMS Selected Service:

2> for each MBMS Selected Service that is indicated on MCCH and for which the UE initiates the ptp radio bearer request:

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> 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:

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

The UE shall not include the IE "UE Specific Behaviour Information 1 idle".

…

If the IE "MBMS short transmission ID" is included the UE shall:

1> if the value of the "MBMS short transmission ID" is less than or equal to the number of services identified by the IE "Modified services list" included in the MBMS MODIFIED SERVICES INFORMATION message acquired in the same modification period as the one in which the "MBMS short transmission ID" is received:

2> consider the "MBMS short transmission ID" to be an index to the list of services contained in the IE "Modified services list" and apply the MBMS transmission identity specified for this entry.

1> otherwise:

2> compile a list of available MBMS services, as included in the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages acquired in the same modification period as the one in which the "MBMS short transmission ID" is received:

3> concatenate the services contained in IE "Modified services list" included in the MBMS MODIFIED SERVICES INFORMATION and the services contained in IE "Unmodified services list" included in the MBMS UNMODIFIED SERVICES INFORMATION.

2> consider the "MBMS short transmission ID" to be the index of the entry in the list of available services and apply the MBMS transmission identity specified for this entry.

…

The UE shall calculate the identity of a Modification period as follows:

MP identity= (SFNMP div MPlen) mod 2

With SFN_MP being the SFN corresponding with the frame in which the concerned Modification Period starts

MP_len being the length of the Modification Period, that is indicated by the IE "Modification period coefficient" that is included in System Information Block type 5 and 5bis.

Reference

3GPP TS 25.331 clauses 8.6.9.6, 8.1.3.3, 8.6.9.8, 8.5.29.

8.5.1.11.3 Test purpose

To verify that the UE receives the MBMS info in idle mode state and correctly triggers the P-t-p request procedure.

8.5.1.11.4 Method of test

Initial condition

System Simulator:

1 MBMS cell

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 the MBMS_ACTIVATED_SERVICES variable).

Related ICS/IXIT statements

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

Test procedure

1) The UE camping on Cell 21, receives an MBMS MODIFIED SERVICES INFORMATION messages including IEs “MBMS required UE action” set to “Request PTP RB”.

2) The UE shall request a p-t-p RB establishment. The UE transmits a RRC CONNECTION REQUEST message including the IE "MBMS Selected Service ID" of the concerned MBMS selected services within the IE "MBMS Selected Services Short" and the IE "MBMS Modification Period identity".

3) The SS transmits a RADIO BEARER SETUP message to the UE. This message requests the establishment of a radio access bearer. The UE shall establish this radio bearer. Then the UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			MBMS MODIFIED SERVICES INFORMATION	"MBMS required UE action" set to Request PTP RB.
2			RRC CONNECTION REQUEST	The UE transmits the message with Establishment cause set to “MBMS ptp RB request” and with the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity.
3			RRC CONNECTION SETUP	RRC state indicator set to Cell_DCH
4			RRC CONNECTION SETUP COMPLETE
5			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 11.
6	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Broadcast service Reception”.
7			SECURITY MODE COMMAND
8			SECURITY MODE COMPLETE
9			RADIO BEARER SETUP
10			RADIO BEARER SETUP COMPLETE
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

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	Request PTP RB
– Continue MCCH reading	FALSE

RRC CONNECTION REQUEST (Step 2)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI.
Establishment Cause	MBMS ptp RB request
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 3)

Information Element	Value/remark
Message type
RRC State Indicator	Cell_DCH

MBMS MODIFICATION REQUEST (steps 5)

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.

RADIO BEARER SETUP (Step 9)

Use the same message as the one specified for "MBMS PtP" in TS 34.108 clause 9 with the condition B1.

8.5.1.11.1.5 Test requirements

At step 2, the UE shall transmit a RRC CONNECTION REQUEST message with Establishment cause set to “MBMS ptp RB request”. The UE shall include the IE "MBMS Selected Service ID" within the IE "MBMS Selected Services Short" and the IE "MBMS Modification Period identity".

8.5.1.11m MBMS PTP Session Start at MCCH Notification in Idle Mode / MBMS Multicast Service

8.5.1.11m.1 Definition

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

8.5.1.11m.2 Conformance requirement

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

Reference

3GPP TS 25.331 clauses 8.6.9.6, 8.6.9.8, 8.5.29.

8.5.1.11m.3 Test purpose

Same test purpose as in clause 8.5.1.11.3.

8.5.1.11m.4 Method of test

Initial condition

System Simulator:

1 MBMS cell

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.1.11.4 except for the point 2:

2) The UE shall request a p-t-p RB establishment. The UE transmits a RRC CONNECTION REQUEST message.

Expected sequence

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

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			MBMS MODIFIED SERVICES INFORMATION	"MBMS required UE action" set to Request PTP RB.
2			RRC CONNECTION REQUEST	The UE transmits the message with Establishment cause set to “MBMS ptp RB request”
3			RRC CONNECTION SETUP	RRC state indicator set to Cell_DCH
4			RRC CONNECTION SETUP COMPLETE
5	UE			UE transmits SERVICE REQUEST, with IE "Service type" set to "MBMS Multicast service Reception”.
6			SECURITY MODE COMMAND
7			SECURITY MODE COMPLETE
8			RADIO BEARER SETUP
9			RADIO BEARER SETUP COMPLETE
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

Same specific messages contents as in clause 8.5.1.11.4 except for RRC CONNECTION REQUEST message content (step 2)

RRC CONNECTION REQUEST (Step 2)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered TMSI or P-TMSI.
Establishment Cause	MBMS ptp RB request
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.1.11m.5 Test requirements

At step 2, the UE shall transmit a RRC CONNECTION REQUEST message with Establishment cause set to “MBMS ptp RB request”.

8.5.1.12 MBMS PTP Session Start at MCCH Notification in URA_PCH / MBMS Selected Service

8.5.1.12.1 Definition

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

8.5.1.12.2 Conformance requirement

…

The UE shall:

1> if in idle mode, URA_PCH, CELL_PCH or CELL_FACH state:

2> if not monitoring MICH:

3> acquire the MBMS MODIFIED SERVICES INFORMATION message from MCCH at the start of every modification period, in accordance with subclause 8.7.1.3;

3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.

….

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 ‘Request PTP RB’:

…

2> if the UE is in URA_PCH, Cell_PCH or CELL_FACH states:

3> indicate to upper layers to initiate a service request procedure [5] to receive the concerned MBMS service;

3> perform the cell update procedure with cause "MBMS ptp RB request", as specified in subclause 8.3.1.2, unless the UE has already requested p-t-p RB establishment in the current modification period.