11.5 MBMS Context Activation
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
11.5.1m MBMS Context Activation requested by the network, Successful and Unsuccessful procedure / MBMS Multicast Service
11.5.1m.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.5.1m.2 Conformance requirement
The purpose of this procedure is to establish an MBMS context in the MS and in the network for a specific IP Multicast Address using a specific NSAPI for MBMS user plane transmission. The MS shall only initiate the MBMS context activation when requested by the network. However, the trigger for the activation request by the network is initiated by the MS at the application layer.
1) Successful MBMS context activation
In order to request an MBMS context activation, the network sends a REQUEST MBMS CONTEXT ACTIVATION message to the MS, enters the state MBMS-ACTIVE-PENDING and starts timer T3385. The message shall contain the IP multicast address, the APN and the Linked NSAPI.
Upon receipt of a REQUEST MBMS CONTEXT ACTIVATION message, the MS shall validate the message by verifying the NSAPI given in the Linked NSAPI IE to be one of the active PDP context(s), and send an ACTIVATE MBMS CONTEXT REQUEST, enter state MBMS-ACTIVE-PENDING and start timer T3380. The message shall contain an IP multicast address and an APN, which shall be the same as the IP multicast address and the APN requested by the network in the REQUEST MBMS CONTEXT ACTIVATION message. Furthermore, the MS shall include the Supported MBMS bearer capabilities, i.e. the maximum downlink bit rate the MS can handle.
Upon receipt of the ACTIVATE MBMS CONTEXT REQUEST message, the network shall stop timer T3385. If the network accepts the request, it shall reply with an ACTIVATE MBMS CONTEXT ACCEPT message.
Upon receipt of the message ACTIVATE MBMS CONTEXT ACCEPT the MS shall stop timer T3380 and shall enter the state MBMS-ACTIVE.
2) Whenever a REQUEST MBMS CONTEXT ACTIVATION message is received by the MS specifying a transaction identifier relating to a PDP context or MBMS context not in state PDP-INACTIVE, the MS shall locally deactivate the old PDP context or MBMS context relating to the received transaction identifier. Furthermore, the MS shall continue with the activation procedure of a new MBMS context as indicated in the received message.
3) Upon receipt of the REQUEST MBMS CONTEXT ACTIVATION message, the MS may reject the network requested MBMS context activation by sending the REQUEST MBMS CONTEXT ACTIVATION REJECT message to the network The sender of the message shall include the same TI as included in the REQUEST MBMS CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes:
………
# 40: feature not supported; or
………
The network shall stop timer T3385 and enter in state PDP-INACTIVE.
Reference
3GPP TS 24.008 clauses 6.1.3.8 and 8.3.2 f.
11.5.1m.3 Test purpose
To test behaviour of the UE upon receipt of a MBMS context activation request from the SS:
a) When UE supports MBMS context activation requested by the network
b) When UE supporting MBMS context activation requested by the network, receives REQUEST MBMS CONTEXT ACTIVATION message with transaction identifier relating to an already active MBMS or PDP context
11.5.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 at least two PDP context activated. PDP one trans_id 0 and nsapi 5. PDP two trans_id 1 and nsapi 6.
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.
A REQUEST MBMS CONTEXT ACTIVATION message is sent by the SS. UE will start MBMS context activation procedure
On receipt of the ACTIVATE MBMS CONTEXT REQUEST message from the UE, an ACTIVATE MBMS CONTEXT ACCEPT message is returned by the SS.
REQUEST MBMS CONTEXT ACTIVATION message is then sent by the SS using transaction identifier of the currently active MBMS context. The UE shall activate this context to replace the previous context.
REQUEST MBMS CONTEXT ACTIVATION message is then sent by the SS using transaction identifier of the currently active PDP context. The UE shall activate this context to replace the previous context.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
0 |
SS |
Join MBMS session |
Join 1st MBMS session. See TS 34.108 clause 7.6.1 |
|
|
1 |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS sends Request a MBMS context activation to UE and starts timer T3385. The linked nsapi set to 5. |
|
|
2 |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE supporting Multicast replies with a MBMS context activation request |
|
|
3 |
SS |
The SS stops timer T3385. |
||
|
4 |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation. |
|
|
5 |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS requests a MBMS context activation for an existing MBMS context with the same TI value as one of the active MBMS contexts and starts timer T3385 |
|
|
6 |
UE |
UE locally deactivates the old MBMS context with the same TI value |
||
|
7 |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE continues with the activation of a new MBMS context to replace locally deactivated MBMS context |
|
|
8 |
SS |
The SS stops timer T3385. |
||
|
9 |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation |
|
|
10 |
|
REQUEST MBMS CONTEXT ACTIVATION |
requests MBMS context activation for an existing PDP context with linked NSAPI 5 and by setting TI value same as the TI value of other active PDP context (TI value set to 1); and starts timer T3385 |
|
|
11 |
UE |
UE locally deactivates the PDP context with TI value 1 and NSAPI 6 |
||
|
12 |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE continues with the activation of a new MBMS context which is linked to NSAPI 5 |
|
|
13 |
SS |
The SS stops timer T3385 and releases Radio Access Bearer for old PDP context. |
||
|
14 |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation |
|
Specific message contents
Step 5: TI IE value is equal to the TI value of one of the active MBMS contexts , Offered multicast address IE value and/or Access point name IE value are (is) different from the corresponding IE value(s) in the existing MBMS context.
Step 10: TI IE value is equal to the TI value of one of the active PDP contexts .
11.5.1m.5 Test requirements
At step 2, the UE shall accept MBMS context activation initiated by the SS.
At step 6, the UE shall locally deactivate the old MBMS context when a REQUEST MBMS CONTEXT ACTIVATION message is received, specifying a transaction identifier relating to an active MBMS context and continue with the activation procedure of a new MBMS context as indicated in the received message.
At step 11, the UE shall locally deactivate the old MBMS context when a REQUEST MBMS CONTEXT ACTIVATION message is received, specifying a transaction identifier relating to an active PDP context and continue with the activation procedure of a new MBMS context as indicated in the received message.
11.5.2m Abnormal Cases
11.5.2.1m T3380 Expiry / MBMS Multicast Service
11.5.2.1m.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.5.2.1m.2 Conformance requirement
On the first expiry of the timer T3380, the UE shall resend the ACTIVATE MBMS CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3380, the UE shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic MBMS context activation re-attempt shall be performed.
Upon receipt of the REQUEST MBMS CONTEXT ACTIVATION message, the MS may reject the network requested MBMS context activation by sending the REQUEST MBMS CONTEXT ACTIVATION REJECT message to the network The sender of the message shall include the same TI as included in the REQUEST MBMS CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes:
………
# 40: feature not supported; or
………
The network shall stop timer T3385 and enter in state PDP-INACTIVE.
Reference
3GPP TS 24.008 clause 6.1.3.8.4 a.
11.5.2.1.3m Test purpose
To test the behaviour of the UE when the SS does not reply to MBMS CONTEXT ACTIVATION REQUEST.
11.5.2.1.4m Method of test
Initial conditions
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 at least one PDP context activated. PDP one trans_id 0 and nsapi 5.
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.
A MBMS context activation is requested by the SS. The UE shall send the ACTIVATE MBMS CONTEXT REQUEST message five times with T3380 seconds between each message. After this, no further ACTIVATE MBMS CONTEXT REQUEST messages shall be sent by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
0 |
SS |
Join MBMS session |
Join 1st MBMS session. See TS 34.108 clause 7.6.1 |
|
|
1 |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS sends Request a MBMS context activation to UE and starts timer T3385. The linked nsapi set to 5. |
|
|
2 |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE supporting Multicast replies with a MBMS context activation request |
|
|
3 |
SS |
The SS stops timer T3385. |
||
|
4 |
SS |
T3380 seconds |
||
|
5 |
|
ACTIVATE MBMS CONTEXT REQUEST |
Request a MBMS context activation |
|
|
6 |
SS |
T3380 seconds |
||
|
7 |
|
ACTIVATE MBMS CONTEXT REQUEST |
Request a MBMS context activation |
|
|
8 |
SS |
T3380 seconds |
||
|
9 |
|
ACTIVATE MBMS CONTEXT REQUEST |
Request a MBMS context activation |
|
|
10 |
SS |
T3380 seconds |
||
|
11 |
|
ACTIVATE MBMS CONTEXT REQUEST |
Request a MBMS context activation |
|
|
12 |
SS |
Wait for T3380 seconds to ensure no further ACTIVATE MBMS CONTEXT REQUEST messages are sent by the UE |
||
Specific message contents
None.
11.5.2.1m.5 Test requirements
At step 5, the UE On the first expiry of the timer T3380, the UE shall re-send the MBMS CONTEXT ACTIVATION REQUEST.
At step 7, On the second expiry of the timer T3380, the UE shall re-send the MBMS CONTEXT ACTIVATION REQUEST.
At step 9, On the third expiry of the timer T3380, the UE shall re-send the MBMS CONTEXT ACTIVATION REQUEST.
At step 11, On the fourth expiry of the timer T3380, the UE shall re-send the MBMS CONTEXT ACTIVATION REQUEST.
At step 12, On the fifth expiry of the timer T3380, the UE shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic MBMS context activation re-attempt shall be performed.
11.5.2.2m Network initiated MBMS context activation request for an already activated context (on the UE side) / MBMS Multicast Service
11.5.2.2m.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.5.2.2m.2 Conformance requirement
………..
MBMS context activation request for an already activated MBMS context (on the mobile station side): If the MS receives a REQUEST MBMS CONTEXT ACTIVATION message with the same combination of APN and IP multicast address (i.e. PDP type and PDP address) as an already activated MBMS context, the MS shall deactivate the existing MBMS context locally without notification to the network and proceed with the requested MBMS context activation.
………..
Upon receipt of the REQUEST MBMS CONTEXT ACTIVATION message, the MS may reject the network requested MBMS context activation by sending the REQUEST MBMS CONTEXT ACTIVATION REJECT message to the network The sender of the message shall include the same TI as included in the REQUEST MBMS CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes:
………
# 40: feature not supported; or
………
The network shall stop timer T3385 and enter in state PDP-INACTIVE.
Reference
3GPP TS 24.008 clause 6.1.3.8.4 c).
11.5.2.2m.3 Test purpose
To test the behaviour of the UE when it detects a network initiated MBMS context activation for the MBMS context already activated on the UE side.
11.5.2.2m.4 Method of test
Initial conditions
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 at least one PDP context activated. PDP one trans_id 0 and nsapi 5.
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.
A MBMS context activation is requested by the SS. UE accepts MBMS context activation and sends MBMS CONTEXT ACTIVATION REQUEST which SS responds with MBMS CONTEXT ACTIVATION ACCEPT. SS sends a REQUEST MBMS CONTEXT ACTIVATION message with the same combination of APN and multicast address as an already activated MBMS context. The UE deactivates the existing MBMS context locally without notification to the SS and proceeds with the requested MBMS context activation.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
0 |
SS |
Join MBMS session |
Join 1st MBMS session. See TS 34.108 clause 7.6.1 |
|
|
1 |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS sends Request a MBMS context activation to UE and starts timer T3385. The linked nsapi set to 5. |
|
|
2 |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE supporting Multicast replies with a MBMS context activation request. |
|
|
3 |
SS |
The SS stops timer T3385. |
||
|
4 |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation. |
|
|
5 |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS requests a MBMS context activation for an existing MBMS context with the same APN and multicast address as the active MBMS context and starts timer T3385 |
|
|
6 |
UE |
UE locally deactivates the old MBMS context with the same APN and multicast address |
||
|
7 |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE continues with the activation of a new MBMS context to replace locally deactivated MBMS context |
|
|
8 |
SS |
The SS stops timer T3385. |
||
|
9 |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation |
|
Specific message contents
None.
11.5.2.2.5m Test requirements
At step 6, the UE shall locally deactivate old MBMS context.
At step 7, the UE shall continue with the activation of a new MBMS context.