11.7m Network Feature Support IE for MBMS / MBMS Multicast Service
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
11.7m.1 Definition and applicability
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.7m.2 Conformance requirement
The network informs the MS about the support of specific features, such as LCS-MOLR or MBMS, in the "Network feature support" Information Element. The information is either explicitly given by sending the "Network feature support" IE or implicitly by not sending it. The handling in the network is described in subclause 9.4.2.9. The MS may use the indication to inform the user about the availability of the appropriate services and it shall not request services that have not been indicated as available. The indication for MBMS is defined in subclause "MBMS feature support indication" in 3GPP TS 23.246.
…
An SGSN that supports MBMS shall indicate MBMS feature support to the UE during Routing Area Update procedure in the Routing Area Update Accept message and during GPRS attach procedure in the Attach Accept message. The UE then knows it can use already activated MBMS bearers, or activate new MBMS bearers according to subclause 8.2 "MBMS Multicast Service Activation".
An SGSN that does not support MBMS will not indicate MBMS feature support to the UE. This indicates to the UE that MBMS bearers are no longer supported, which may allow the UE to use point-to-point bearers for MBMS data transfer. In this case, the UE shall deactivate all active MBMS UE Contexts locally.
Reference(s)
Clause 4.7.3 of TS 24.008
Clause 8.9a of TS 23.246
11.7m.3 Test purpose
To verify that the UE correctly reads the "Network feature support" IE received in ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message and does not try to request MBMS services if those are not available in the network.
11.7m.4 Method of test
Initial conditions
System Simulator:
2 MBMS cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2).
Both cells are operating in network operation mode II.
User Equipment:
The UE is Idle updated on Cell A
Related ICS/IXIT statement(s)
– MBMS Multicast service application available on UE Yes/No
Test procedure
The UE initiates attach procedure for PS services. The SS responds with ATTACH ACCEPT message where "Network feature support" IE indicates that MBMS is supported in the network. The UE shall join the MBMS service. The SS adjusts the cell levels so that the UE starts the ROUTING AREA UPDATE procedure. The SS responds with ROUTING AREA UPDATE ACCEPT message where "Network feature support" IE indicates that MBMS is not supported in the network. The UE shall deactivate the active 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". The UE initiates detach procedure.
The UE initiates attach procedure for PS services. The SS responds with ATTACH ACCEPT message where "Network feature support" IE is omitted and implicitly indicates that MBMS is not supported in the network. The UE shall not try to join the MBMS service. The SS adjusts the cell levels so that the UE starts the ROUTING AREA UPDATE procedure. The SS responds with ROUTING AREA UPDATE ACCEPT message where "Network feature support" IE indicates that MBMS is supported in the network. The UE shall join the MBMS service. The UE initiates detach procedure.
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 |
|
ATTACH REQUEST |
||
|
3 |
|
AUTHENTICATION AND CIPHERING REQUEST |
||
|
4 |
|
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
5 |
|
ATTACH ACCEPT |
Network feature support: MBMS supported |
|
|
6 |
|
ATTACH COMPLETE |
||
|
7 |
SS |
Join MBMS session |
Join 1st MBMS session. See TS 34.108 clause 7.6.1 |
|
|
7a |
|
PDP CONTEXT REQUEST |
UE supporting Multicast replies with a PDP context activation request |
|
|
7b |
|
PDP CONTEXT ACCEPT |
SS accepts the PDP context activation. |
|
|
7c |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS sends Request a MBMS context activation to UE. The linked nsapi set to 5. |
|
|
7d |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE supporting Multicast replies with a MBMS context activation request |
|
|
7e |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation. |
|
|
8 |
The following messages are sent and shall be received on cell B. |
|||
|
9 |
SS |
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). |
||
|
10 |
|
ROUTING AREA UPDATE REQUEST |
Update type: RA updating Old routing area identification: RAI-1 Old P-TMSI signature: P-TMSI-1 signature |
|
|
11 |
SS |
The SS starts integrity protection. |
||
|
12 |
|
ROUTING AREA UPDATE ACCEPT |
Update result: RA updated Routing area identification: RAI-2 P-TMSI signature: P-TMSI-2 signature Mobile identity: P-TMSI-2 Network feature support: MBMS not supported |
|
|
12a |
|
ROUTING AREA UPDATE COMPLETE |
||
|
13 |
UE |
The UE deactivates the MBMS context locally |
||
|
A14 |
UE |
The UE may decide to deactivate the PDP Context. The UE may send a DETACH REQUEST (NOTE 1). |
||
|
A14a |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request deactivation of the PDP context activated in steps 7a-7b |
|
|
A14b |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request MBMS context deactivation Including trans_id 1of previous MBMS context activated (Nsapi 128) SM cause: #36 regular deactivation. |
|
|
A14c |
|
SM STATUS |
SM cause value to #81 “invalid transaction identifier value”. |
|
|
A14d |
|
DEACTIVATE PDP CONTEXT ACCEPT |
Accept request to deactivate the PDP context established in steps 7a-7b |
|
|
A14e |
|
DETACH REQUEST |
Detach type: “normal detach, GPRS detach” Mobile identity = P-TMSI-2 If the UE does not transmit DETACH REQUEST, then SS should send the DETACH REQUEST. |
|
|
A14f |
|
DETACH ACCEPT |
||
|
A14g |
SS |
The SS shall check that no messages are sent from the UE. |
||
|
B14 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request MBMS context deactivation Including trans_id 1of previous MBMS context activated (Nsapi 128) SM cause: #36 regular deactivation (NOTE 2). |
|
|
B14a |
|
SM STATUS |
SM cause value to #81 “invalid transaction identifier value”. |
|
|
B14b |
Void |
|||
|
B14c |
|
DETACH REQUEST |
Detach type: “re-attach not required” |
|
|
B14d |
|
DETACH ACCEPT |
||
|
15 |
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. |
|||
|
16 |
|
ATTACH REQUEST |
||
|
17 |
|
AUTHENTICATION AND CIPHERING REQUEST |
||
|
18 |
|
AUTHENTICATION AND CIPHERING RESPONSE |
||
|
19 |
|
ATTACH ACCEPT |
Network feature support IE not present |
|
|
20 |
|
ATTACH COMPLETE |
||
|
21 |
SS |
The SS verifies that the UE does not try to activate PDP context, which is needed prior to JOIN MBMS procedure. |
||
|
22 |
The following messages are sent and shall be received on cell B. |
|||
|
23 |
SS |
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). |
||
|
24 |
|
ROUTING AREA UPDATE REQUEST |
Update type: RA updating Old routing area identification: RAI-1 Old P-TMSI signature: P-TMSI-1 signature |
|
|
25 |
The SS starts integrity protection. |
|||
|
26 |
|
ROUTING AREA UPDATE ACCEPT |
Update result: RA updated Routing area identification: RAI-2 P-TMSI signature: P-TMSI-2 signature Mobile identity: P-TMSI-2 Network feature support: MBMS supported |
|
|
27 |
|
ROUTING AREA UPDATE COMPLETE |
||
|
28 |
SS |
Join MBMS session |
Join 2nd MBMS session. See TS 34.108 clause 7.6.1 |
|
|
29 |
Void |
|||
|
30 |
|
PDP CONTEXT REQUEST |
UE supporting Multicast replies with a PDP context activation request |
|
|
31 |
|
PDP CONTEXT ACCEPT |
SS accepts the PDP context activation. |
|
|
32 |
|
REQUEST MBMS CONTEXT ACTIVATION |
SS sends Request a MBMS context activation to UE. The linked nsapi set to 5. |
|
|
33 |
|
ACTIVATE MBMS CONTEXT REQUEST |
UE supporting Multicast replies with a MBMS context activation request |
|
|
34 |
|
ACTIVATE MBMS CONTEXT ACCEPT |
SS accepts the MBMS context activation. |
|
|
NOTE: The definitions for "Suitable neighbour cell" and "Serving cell" are specified in TS34.108 clause 6.1.5 “Reference Radio Conditions (FDD)” NOTE 1: Support of automatic PS attach procedure at switch on – no NOTE 2: Support of automatic PS attach procedure at switch on – yes |
||||
Specific Message Contents
None
11.7m.5 Test requirements
In step 7 the UE shall join the MBMS session.
In step 13 the UE shall deactivate the MBMS contexts locally.
In step A14c or B14a 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 21 the UE shall not try to join the MBMS session.
In step 28 the UE shall join the MBMS session.