11.6 MBMS Context deactivation
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
11.6.1m MBMS Context deactivation requested by the network, Successful / MBMS Multicast Service
11.6.1m.1 Definition
This test case is applicable for Rel-6 UEs that support MBMS multicast services.
11.6.1m.2 Conformance requirement
The purpose of the MBMS context deactivation procedure is to deactivate an existing MBMS context in the MS and the network. The MS shall only initiate the MBMS context deactivation when requested by the network, however the trigger for the deactivation request by the network may be initiated by the MS at application layer or by the network, see 3GPP TS 23.246.
After a successful MBMS context deactivation, the associated MBMS NSAPI and TI values shall be released in both the MS and the network and can be reassigned to another MBMS context.
The MBMS context deactivation procedure makes use of the messaging and signalling of the PDP context deactivation procedure as described in the subclause 6.2.3.2.1.
In order to request an MBMS context deactivation, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the MS, enters the state MBMS-INACTIVE-PENDING and starts timer T3395. The messages contains the transaction identifier (TI) in use for the MBMS context to be deactivated and a cause code that typically indicates one of the following causes:
# 36: regular deactivation;
# 38: network failure;
# 47: multicast group membership time-out.
The MS shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message and enter the state PDP-INACTIVE. Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395 and enter the state PDP-INACTIVE.
….
Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION, REQUEST MBMS CONTEXT ACTIVATION, or SM-STATUS is received by the MS specifying a transaction identifier which is not recognized as relating to an active context or to a context that is in the process of activation or deactivation, the MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value including the extension octet and remain in the PDP-INACTIVE state.
….
The purpose of this procedure is to deactivate an existing PDP context between the MS and the network. The PDP context deactivation may be initiated by the MS or by the network. The tear down indicator information element may be included in the DEACTIVATE PDP CONTEXT REQUEST message in order to indicate whether only the PDP context associated with this specific TI or all active PDP contexts sharing the same PDP address and APN as the PDP context associated with this specific TI shall be deactivated. If the tear down is requested, all other active PDP contexts sharing the same PDP address and APN as the PDP context associated with this specific TI shall be deactivated locally without peer-to-peer signalling. If the tear down indicator information element is not included in the DEACTIVATE PDP CONTEXT REQUEST message, only the PDP context associated with this specific TI shall be deactivated.
After successful PDP context deactivation, the associated NSAPI and TI values are released and can be reassigned to another PDP context.
If one or more MBMS contexts are linked to a PDP context that has been deactivated, the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and the network).
Reference
3GPP TS 24.008 clauses 6.1.3.4, 6.1.3.9 and 8.3.2.
11.6.1m.3 Test purpose
To verify that the UE correctly handle a MBMS context deactivation procedure requested by the network, upon reception of a DEACTIVATE PDP CONTEXT REQUEST. To verify that the UE correctly handle a MBMS context deactivation procedure locally, when the linked PDP context is deactivated.
11.6.1m.4 Method of test
Initial condition
System Simulator:
1 MBMS cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
The UE has one PDP context activated (trans_id 0 and nsapi 5) and one MBMS context activated (trans_id 1 and mbms nsapi 128).
Related ICS/IXIT statements
MBMS Multicast service application available on UE Yes/No
Test procedure
The UE joins a multicast service provided by the SS.
During the 1st MBMS session the SS sends a DEACTIVATE PDP CONTEXT REQUEST message using transaction identifier of the currently active MBMS context. The SS sets T3395 timer to wait for the response from the UE.
The UE shall initiate a MBMS context deactivation procedure.
The UE shall send the DEACTIVATE PDP CONTEXT ACCEPT message within T3395 timer duration.
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".
The UE joins a multicast service provided by the SS.
During the 2nd MBMS session the SS sends a DEACTIVATE PDP CONTEXT REQUEST message using the tear down indicator.
The UE shall deactivate the MBMS context locally.
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 |
SS |
Join MBMS session |
Join 1st MBMS session. See TS 34.108 clause 7.6.1 |
|
|
1a |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS sends Request a MBMS context activation to UE. The linked nsapi set to 5. |
|
|
1b |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE supporting Multicast replies with a MBMS context activation request |
|
|
1c |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation. |
|
|
2 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request MBMS context deactivation Including trans_id 1 For MBMS context ( Nsapi 128) SM cause: #36 regular deactivation. SS starts T3395. |
|
|
3 |
|
DEACTIVATE PDP CONTEXT ACCEPT |
After sending the message the UE enters in state PDP-INACTIVE. |
|
|
4 |
SS |
SS stop T3395 |
||
|
5 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request MBMS context deactivation Including trans_id 1of previous MBMS context activated (Nsapi 128) SM cause: #36 regular deactivation. |
|
|
6 |
|
SM STATUS |
SM cause value to #81 “invalid transaction identifier value”. |
|
|
7 |
SS |
Join MBMS session |
Join 2nd MBMS session. See TS 34.108 clause 7.6.1 |
|
|
7a |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS sends Request a MBMS context activation to UE. The linked nsapi set to 5. |
|
|
7b |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE supporting Multicast replies with a MBMS context activation request |
|
|
7c |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation. |
|
|
8 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Tear down requested |
|
|
9 |
UE |
The UE deactivates the MBMS contexts locally. |
||
|
10 |
SS |
The SS shall check that no messages are sent from the UE. |
||
|
11 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request MBMS context deactivation Including trans_id 1of previous MBMS context activated (Nsapi 128) SM cause: #36 regular deactivation. |
|
|
12 |
|
SM STATUS |
SM cause value to #81 “invalid transaction identifier value”. |
|
Specific message contents
DEACTIVATE PDP CONTEXT REQUEST (step 2)
|
Information Element |
Value/remark |
|
Transaction identifier |
TI value of the MBMS context in use: trans_id1 |
|
SM cause |
#36: regular deactivation |
DEACTIVATE PDP CONTEXT ACCEPT (step 3)
|
Information Element |
Value/remark |
|
Transaction identifier |
TI value of the MBMS context in use: trans_id1 |
DEACTIVATE PDP CONTEXT REQUEST (steps 5 and 11)
|
Information Element |
Value/remark |
|
Transaction identifier |
TI value of the MBMS context which was requested to be deactivated at step 1: trans_id1 |
|
SM cause |
#36: regular deactivation |
SM STATUS (steps 6 and 12)
|
Information Element |
Value/remark |
|
Transaction identifier |
trans_id1 |
|
SM cause |
#81 "invalid transaction identifier value" |
DEACTIVATE PDP CONTEXT REQUEST (step 8)
|
Information Element |
Value/remark |
|
Tear down indicator |
tear down requested |
11.6.1m.5 Test requirements
In step 3, the UE shall send a DEACTIVATE PDP CONTEXT ACCEPT message containing the transaction identifier (TI) in use for the MBMS context.
In step 6, 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.
In step 9, the UE shall deactivate the MBMS contexts locally.
In step 12, 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.