11.8 MBMS Service Request
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
11.8.1m MBMS Service request procedure not accepted by the network / MBMS Multicast Service
11.8.1m.1 Definition and applicability
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.8.1m.2 Conformance requirement
If the Service request cannot be accepted, the network returns a SERVICE REJECT message to the mobile station. An MS that receives a SERVICE REJECT message stops timer T3317. The MS shall then take different actions depending on the received reject cause value:
…
# 40 (No PDP context activated)
- The MS shall deactivate locally all active PDP and MBMS contexts and the MS shall enter the state GMM-REGISTERED.NORMAL-SERVICE. The MS may also activate PDP context(s) to replace any previously active PDP contexts. The MS may also perform the procedures needed in order to activate any previously active multicast service(s).
NOTE: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS context(s) automatically.
Reference(s)
Clause 4.7.13.4 of TS 24.008
11.8.1m.3 Test purpose
To verify that the UE correctly handles a SERVICE REJECT message with SM cause “#40 No PDP context activated” received from the network and deactivates the MBMS context locally.
11.8.1m.4 Method of test
Initial conditions
System Simulator:
1 MBMS cell, default parameters.
User Equipment:
The UE is in "PMM-IDLE” mode and has joined the multicast service provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Related ICS/IXIT statement(s)
– MBMS Multicast service application available on UE Yes/No
Test procedure
The UE receives an MBMS MODIFIED SERVICES INFORMATION message for an MBMS multicast service for which the UE has activated an MBMS context. The UE will try to establish a PS signalling connection and sends a SERVICE REQUEST message to the SS where the service type is set to "MBMS multicast service reception". The SS returns a SERVICE REJECT message to the UE with SM cause “#40 No PDP context activated”. The UE shall deactivate locally the active MBMS context and shall enter the state GMM-REGISTERED.NORMAL-SERVICE. In order to check that the MBMS context has been deactivated, a DEACTIVATE PDP CONTEXT REQUEST message using transaction identifier of the deactivated MBMS context is sent by the SS. The UE shall send the SM STATUS message using cause #81 "invalid transaction identifier value".
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
MBMS MODIFIED SERVICES INFORMATION |
The SS informs the UE about a change for the MBMS service available in the cell |
|
|
2 |
|
SERVICE REQUEST |
Service type: MBMS Multicast Service Reception |
|
|
3 |
|
SERVICE REJECT |
GMM cause: # 40 No PDP context activated |
|
|
4 |
UE |
The UE deactivates the MBMS context locally |
||
|
5 |
SS |
The SS shall check that no messages are sent from the UE |
||
|
6 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request MBMS context deactivation Including the transaction Identifier of the previous activated MBMS context. SM cause: #36 regular deactivation. |
|
|
7 |
|
SM STATUS |
SM cause value to #81 “invalid transaction identifier value”. |
|
Specific Message Contents
11.8.1m.5 Test requirements
In step 2 the UE shall send a SERVICE REQUEST message containing the service type IE MBMS Service Reception.
In step 4 the UE shall deactivate the MBMS contexts locally.
In step 7 the UE shall send an SM STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value including the extension octet.
11.8.2 MBMS Service Request procedure collision with Routing Area Update/ MBMS Selected Service
11.8.2.1 Definition and applicability
This test is applicable for Rel-6 UEs supporting MBMS broadcast services.
11.8.2.2 Conformance requirement
The following abnormal cases can be identified:
…
e) Routing area update procedure is triggered
If a cell change into a new routing area occurs and the necessity of routing area update procedure is determined before the security mode control procedure is completed, a SERVICE ACCEPT or SERVICE REJECT message has been received, the Service request procedure shall be aborted and the routing area updating procedure is started immediately. Follow-on request pending may be indicated in the ROUTING AREA UPDATE REQUEST for the service, which was the trigger of the aborted Service request procedure, to restart the pending service itself or the Service request procedure after the completion of the routing area updating procedure. If the Service type of the aborted SERVICE REQUEST was indicating "data", then the routing area update procedure may be followed by a re-initiated Service request procedure indicating "data", if it is still necessary. If the Service type was indicating "MBMS multicast service reception", or "MBMS broadcast service reception" the Service request procedure shall be aborted.
Reference(s)
Clause 4.7.13.5 of TS 24.008 (Rel-7 version)
11.8.2.3 Test purpose
To verify that the UE correctly aborts a SERVICE REQUEST procedure if a ROUTING AREA UPDATE procedure is initiated before the SERVICE REQUEST procedure has been completed.
11.8.2.4 Method of test
Initial conditions
System Simulator:
2 MBMS cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II.
User Equipment:
The UE is in "PMM-IDLE” mode and is interested in the selected service 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
The UE receives an MBMS MODIFIED SERVICES INFORMATION message for an MBMS selected service for which the UE has activated an MBMS context. The UE will try to establish a PS signalling connection and sends a SERVICE REQUEST message to the SS where the service type is set to "MBMS broadcast service reception ". The SS adjusts the cell levels so that the UE starts the ROUTING AREA UPDATE procedure and aborts the SERVICE REQUEST procedure. The ROUTING AREA UPDATE procedure is completed. The SS checks that the UE does not initiate further SERVICE REQUEST
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
The SS sets the cell type of cell B to the "Suitable neighbour cell" and the cell type of cell A to the "Serving cell" (see NOTE). The following messages are sent and shall be received on cell A. |
|||
|
2 |
SS |
SS initiates PTPRB setup procedure by sending MBMS Modified services Information with “MBMS required UE action” IE set to “Request PTP RB”. |
||
|
2a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to “mbms_PTP_RB_Request”. |
||
|
2b |
UE |
The UE after completing the RRC Connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after RRC CONNECTION SETUP COMPLETE. |
||
|
3 |
|
SERVICE REQUEST |
Service type: MBMS Broadcast Service Reception Timer T3317 shall be started. |
|
|
4 |
|
AUTHENTICATION AND CIPHERING REQUEST |
||
|
5 |
|
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5a |
SS |
The SS releases the RRC connection. |
||
|
6 |
SS |
Within timer T3317 the SS sets the cell type of cell A to the "Suitable neighbour cell" and the cell type of cell B to the "Serving cell" (see NOTE). |
||
|
7 |
The SS sets the cell type of cell A to the "Suitable neighbour cell" and the cell type of cell B to the "Serving cell" (see NOTE). The following messages are sent and shall be received on cell B. |
|||
|
8 |
UE |
The SERVICE REQUEST procedure shall be aborted. Timer T3317 shall be stopped. |
||
|
8a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to " registration ". |
||
|
8b |
UE |
The UE after completing the RRC Connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after RRC CONNECTION SETUP COMPLETE. |
||
|
9 |
|
ROUTING AREA UPDATE REQUEST |
Update type: RA updating Old routing area identification: RAI-1 Old P-TMSI signature: P-TMSI-1signature |
|
|
10 |
SS |
The SS starts integrity protection. |
||
|
11 |
|
ROUTING AREA UPDATE ACCEPT |
Update result: RA updated Routing area identification: RAI-4 P-TMSI signature: P-TMSI-2 signature Mobile identity: P-TMSI-2 |
|
|
12 |
|
ROUTING AREA UPDATE COMPLETE |
||
|
13 |
SS |
SS waits for 30 seconds to check that no further SERVICE REQUEST messages are sent by the UE. |
||
|
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1.5 “Reference Radio Conditions (FDD)”. |
||||
Specific Message Contents
In step 2, MBMS Modified services Information sent by SS with “MBMS required UE action” IE set to “Request PTP RB”.
11.8.2.5 Test requirements
In step 9 the UE shall send ROUTING AREA UPDATE REQUEST.
11.8.2m MBMS Service Request procedure collision with Routing Area Update / MBMS Multicast Service
11.8.2.1m Definition and applicability
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.8.2.2m Conformance requirement
Same conformance requirement as in clause 11.8.2.2.
11.8.2.3m Test purpose
Same test purpose as in clause 11.8.2.3.
11.8.2.4m Method of test
Initial conditions
System Simulator:
2 MBMS cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II.
User Equipment:
The UE is in "PMM-IDLE” mode and has joined the multicast service provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Related ICS/IXIT statement(s)
– MBMS Multicast service application available on UE Yes/No
Test procedure
Same test procedure as in clause 11.8.2.4m except that the UE receives an MBMS MODIFIED SERVICES INFORMATION message for an MBMS multicast service for which the UE has activated an MBMS context and the Service Type in SERVICE REQUEST message to the SS indicates ‘MBMS Multicast Service Reception’.
Expected sequence
Same expected sequence as in clause 11.8.2.4m except that the expected sequence steps 2b and 8b are not applicable and the Service Type in SERVICE REQUEST message in step 3 indicates ‘MBMS Multicast Service Reception’.
Specific Message Contents
Same as clause 11.8.2.4
11.8.2.5m Test requirements
Same test requirements as in clause 11.8.2.5