11.3 PDP context deactivation procedures
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
11.3.1 PDP context deactivation initiated by the UE
11.3.1.1 Definition
11.3.1.2 Conformance requirement
In order to deactivate a PDP context, the UE sends a DEACTIVATE PDP CONTEXT REQUEST message to the network, enters the state PDP-INACTIVE-PENDING and starts timer T3390. The message contains the transaction identifier (TI) in use for the PDP context to be deactivated and a cause code that typically indicates one of the following causes:
– #26: insufficient resources;
– #36: regular PDP context deactivation; or
– #37: QoS not accepted.
The network shall reply with the DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the UE shall stop timer T3390. In UMTS, the network shall initiate the release of Radio Access Bearer associated with this PDP context.
Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS is received by the UE specifying a transaction identifier which is not recognised as relating to an active context or to a context that is in the process of activation or deactivation, the UE 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.
Reference
3GPP TS 24.008 clauses 6.1.3.4.1 and 8.3.2 (b).
11.3.1.3 Test purpose
To test the behaviour of the UE upon receipt of a DEACTIVATE PDP CONTEXT ACCEPT message from the SS in PDP context deactivation procedure initiated by the UE.
To test the behaviour of the UE upon receipt of a session management message (except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS) specifying a transaction identifier which is not recognised as relating to an active context or to a context that is in the process of activation or deactivation.
11.3.1.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
– PS Supported yes/no
– Method of activating a PDP context
– Method of deactivating the PDP context
– Support of automatic PS attach procedure at switch on yes/no
Test procedure
A PDP context is activated by the user and accepted by the SS. PDP context deactivation is then requested by the user. The UE shall send a DEACTIVATE PDP CONTEXT REQUEST message to the SS. The SS shall then reply with a DEACTIVATE PDP CONTEXT ACCEPT message. The SS shall then wait for T3390 seconds to ensure T3390 has been stopped and that no further messages are sent from the UE. The UE in manual mode may perform a detach procedure. The SS shall then send a MODIFY PDP CONTEXT REQUEST for the deactivated context and if the UE has not started a detach procedure it shall reply with an SM STATUS message with cause #81 ‘transaction identifier not known’.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
Initiate a context activation with traffic class “originatingStreamingCall”, "originatingInteractiveCall" or "originatingBackgroundCall". |
||
|
1a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to either Originating Streaming Call, Originating Interactive Call or Originating Background Call or OriginatingSubscribedTrafficCall |
||
|
1b |
|
SERVICE REQUEST |
||
|
1c |
SS |
The SS starts ciphering and integrity protection. |
||
|
2 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context |
|
|
2a |
SS |
The SS establishes the RAB. |
||
|
3 |
|
ACTIVATE PDP CONTEXT ACCEPT |
Accept the PDP context |
|
|
4 |
UE |
Initiate a context deactivation |
||
|
5 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of a PDP context and starts waiting for ‘T3390’. SM cause set to #36. |
|
|
6 |
|
DEACTIVATE PDP CONTEXT ACCEPT |
SS accepts the PDP context deactivation and timer ‘T3390’ is cancelled. |
|
|
6a |
Void |
|||
|
7 |
|
DETACH REQUEST |
The UE may (optionally) send a Detach Request (only Note 1). The SS shall wait up to ‘T3390’ seconds for the Detach Request. While waiting the SS releases the RAB associated with this PDP Context. If the SS receives a Detach Request the test execution continues from step A8, otherwise from step B8. SS shall check that no further deactivate request messages are sent during this time. |
|
|
A8 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the deactivated context. |
|
|
A9 |
SS |
Start timer ‘T3386’ and wait until is expires to ensure that UE does not respond to Modify PDP Context Request(Net) after Detach Request has been sent from UE. |
||
|
A10 |
|
DETACH ACCEPT |
SS responds with DETACH ACCEPT message as a Detach Request was transmitted by the UE |
|
|
B8 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the deactivated context. (Allowed for Note 1 and Note 2). |
|
|
B9 |
|
SM STATUS |
Cause set to #81 |
|
|
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
Steps 2 and 5: TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, 6, A8 and B8: TI flag in TI IE is set to 1.
Steps 2, 3, 5, 6, A8 and B8: The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these test steps.
11.3.1.5 Test requirements
At step 1a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to one of the following causes:
- Originating Streaming Call;
- Originating Interactive Call or
- Originating Background Call
- OriginatingSubscribedTrafficCall
In PDP context deactivation procedure initiated by the UE, upon receipt of a DEACTIVATE PDP CONTEXT ACCEPT message from the SS, the UE shall deactivate PDP context associated with given PDP address and TI.
If the UE has not performed a detach procedure then, upon modification procedure initiated by the network, for deactivated PDP context, the UE shall reply with SM STATUS message with cause #81.
11.3.2 PDP context deactivation initiated by the network
11.3.2.1 Definition
11.3.2.2 Conformance requirement
In order to deactivate a PDP context, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the UE and starts timer T3395. The message contains the transaction identifier in use for the PDP context to be deactivated and a cause code that typically indicates one of the following causes:
# 36: regular PDP context deactivation;
# 38: network failure; or
# 39: reactivation requested.
The UE shall, upon receipt of this message, reply with a DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395. In UMTS, the network shall initiate the release of Radio Access Bearer associated with this PDP context.
Reference
3GPP TS 24.008 clause 6.1.3.4.2.
11.3.2.3 Test purpose
To test the behaviour of the UE upon receipt of a DEACTIVATE PDP CONTEXT REQUEST message from the SS.
11.3.2.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
– PS Supported yes/no
– Method of activating a PDP context
– Support of automatic PS attach procedure at switch on yes/no
Test procedure
A PDP context is activated by the user and accepted by the SS. A DEACTIVATE PDP CONTEXT REQUEST message is then sent by the SS. The UE shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message. The SS shall then wait for T3395 seconds to ensure that no further messages are sent from the UE. The UE in manual mode may perform a detach procedure. The SS shall then send a MODIFY PDP CONTEXT REQUEST for the deactivated context and if the UE has not started a detach procedure it shall reply with an SM STATUS message with cause #81 ‘invalid transaction identifier value’.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
Initiate a context activation with traffic class “originatingStreamingCall”, "originatingInteractiveCall" or "originatingBackgroundCall". |
||
|
1a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to either Originating Streaming Call, Originating Interactive Call or Originating Background Call or OriginatingSubscribedTrafficCall |
||
|
1b |
|
SERVICE REQUEST |
||
|
1c |
SS |
The SS starts ciphering and integrity protection. |
||
|
2 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context |
|
|
2a |
SS |
The SS establishes the RAB. |
||
|
3 |
|
ACTIVATE PDP CONTEXT ACCEPT |
Accept the PDP context |
|
|
4 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of a PDP context and starts waiting for ‘T3395’. SM cause set to #36. |
|
|
5 |
|
DEACTIVATE PDP CONTEXT ACCEPT |
Accept the PDP context deactivation and timer ‘T3395’ is cancelled. |
|
|
5a |
Void |
|||
|
5b |
|
DETACH REQUEST |
The UE may (optionally) send a Detach Request (only Note 1). The SS shall wait up to ‘T3395’ seconds for the Detach Request. While waiting the SS releases the RAB associated with this PDP Context. If the SS receives a Detach Request the test execution continues from step A6, otherwise from step B6. SS shall check that no further deactivate request messages are sent during this time. |
|
|
A6 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the deactivated context. |
|
|
A7 |
SS |
Start timer ‘T3386’ and wait until is expires to ensure that UE does not respond to Modify PDP Context Request(Net) after Detach Request has been sent from UE. |
||
|
A8 |
|
DETACH ACCEPT |
SS responds with DETACH ACCEPT message as a Detach Request was transmitted by the UE |
|
|
B6 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the deactivated context. (Allowed for Note 1 and Note 2). |
|
|
B7 |
|
SM STATUS |
Cause set to #81 |
|
|
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
Steps 2 and 5: TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, 4, A6 and B6: TI flag in TI IE is set to 1.
Steps 2, 3, 4, 5, A6 and B6: The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these test steps.
11.3.2.5 Test requirements
At step 1a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to one of the following causes:
- Originating Streaming Call;
- Originating Interactive Call or
- Originating Background Call
- OriginatingSubscribedTrafficCall
Upon receipt of a request for deactivation of a PDP context from the SS, the UE shall deactivate PDP context.
If the UE has not performed a detach procedure then, upon modification procedure initiated by the network, for deactivated PDP context, UE shall reply with SM STATUS message with cause #81, as confirmation that previously SS requested PDP context deactivation was performed by the UE.
11.3.2a PDP context deactivation initiated by the network / secondary PDP context active / deactivation of primary PDP context
11.3.2a.1 Definition
11.3.2a.2 Conformance requirement
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.
An MS supporting S1 mode shall always include the tear down indicator when deactivating the default PDP context. An MS not supporting S1 mode should apply the same behaviour (see 3GPP TS 23.060 [74]).
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).
…
In order to deactivate a PDP context, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the MS and starts timer T3395. The message contains the transaction identifier in use for the PDP context to be deactivated and a cause code that typically indicates one of the following causes:
# 8: Operator Determined Barring;
# 25: LLC or SNDCP failure (A/Gb mode only);
# 36: regular deactivation;
# 38: network failure; or
# 39: reactivation requested.
#112: APN restriction value incompatible with active PDP context.
The MS shall, upon receipt of this message, reply with a DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395.
If a detach is requested by the HLR for an MS that has PDP contexts for emergency services, the SGSN shall send a DEACTIVATE PDP CONTEXT REQUEST message to the MS for all the PDP contexts that are not PDP contexts for emergency services.
In A/Gb mode, both the MS and the network shall initiate local release of the logical link if it is not used by another PDP context.
In Iu mode, the network shall initiate the release of Radio Access Bearer associated with this PDP context.
Reference
3GPP TS 24.008 clause 6.1.3.4 and 6.1.3.4.2.
11.3.2a.3 Test purpose
To verify that the UE deactivates an active secondary PDP context when the network requests deactivation of a primary PDP context with the tear down indicator information element included.
11.3.2a.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
– Method of activating a PDP context
– Support of automatic PS attach procedure at switch on yes/no
Test procedure
A PDP context activation is requested by the user and accepted by the SS.
If the UE set the PDP type to ‘IPv4’ in the ACTIVATE PDP CONTEXT then the SS allocates an IPv4 address to the UE. If the UE sets the PDP type to IPv4v6 in the ACTIVATE PDP CONTEXT then the SS allocates an IPv4v6 address to the UE.
Else if the UE set the PDP type to ‘IPv6’ in the ACTIVATE PDP CONTEXT REQUEST then the SS allocates an IPv6 address via stateless address auto configuration on the established primary PDP context.
A secondary PDP context activation is requested by the SS and the activation procedure is completed by the UE.
A DEACTIVATE PDP CONTEXT REQUEST message is then sent to the UE requesting the deactivation of the primary PDP context. The UE shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message. The SS shall then wait for T3395 seconds to ensure that no further messages are sent from the UE. The UE in manual mode may perform a detach procedure. The SS shall then send a MODIFY PDP CONTEXT REQUEST for the deactivated PDP context and if the UE has not started a detach procedure it shall reply with an SM STATUS message with cause #81 ‘invalid transaction identifier value’.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
SS |
The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to either Originating Streaming Call, Originating Interactive Call or Originating Background Call or OriginatingSubscribedTrafficCall |
||
|
2 |
|
SERVICE REQUEST |
Service type = "signalling" |
|
|
3 |
SS |
The SS starts integrity protection. |
||
|
4 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context |
|
|
4A |
SS |
IF the UE in step 4 set the PDP type to ‘ IPv4’ in the ACTIVATE PDP CONTEXT REQUEST message then the SS allocates an IPv4 address. IF the UE in step 4 set the PDP type to ‘IPv4v6’ in the ACTIVATE PDP CONTEXT REQUEST message then the SS allocates an IPv4v6 address. ELSE IF the UE in step 4 set the PDP type to ‘ IPv6’ in the ACTIVATE PDP CONTEXT REQUEST message then the SS allocates an IPv6 address. |
||
|
5 |
SS |
The SS establishes the RAB according to reference radio bearer combination 6.10.2.4.1.26 in [9] (1xPS RB 64kbps). |
||
|
6 |
|
ACTIVATE PDP CONTEXT ACCEPT |
The SS accepts the PDP context |
|
|
EXCEPTION: If the "PDP type" in the ACTIVATE PDP CONTEXT REQUEST message was ‘IPv6’ then stateless address auto configuration occurs on the user plane bearer established with the ACTIVATE PDP CONTEXT REQUEST |
||||
|
7 |
SS |
The SS initiates a secondary PDP context activation |
||
|
8 |
|
REQUEST SECONDARY PDP CONTEXT ACTIVATION |
The SS requests a Secondary PDP context activation and starts timer T3385. |
|
|
9 |
|
ACTIVATE SECONDARY PDP CONTEXT REQUEST |
The UE requests a Secondary PDP context activation, enters the state PDP-ACTIVE-PENDING and starts timer T3380. NSAPI IE value is different from the value in Step 4. |
|
|
10 |
SS |
The SS stops timer T3385. The SS reconfigures the RAB according to reference radio bearer combination 6.10.2.4.1.57 in [9] (2xPS RB 64kbps). |
||
|
11 |
|
ACTIVATE SECONDARY PDP CONTEXT ACCEPT |
The SS accepts the Secondary PDP context activation with the requested QoS |
|
|
12 |
SS |
The SS waits for T3380 seconds to ensure no further activate request messages come from the UE |
||
|
13 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of the primary PDP context and starts waiting for ‘T3395’. SM cause set to #36. |
|
|
14 |
|
DEACTIVATE PDP CONTEXT ACCEPT |
Accept the PDP context deactivation and timer ‘T3395’ is cancelled. |
|
|
14b |
|
DETACH REQUEST |
The UE may (optionally) send a Detach Request (only Note 1). The SS shall wait up to ‘T3395’ seconds for the Detach Request. While waiting the SS releases the RABs associated with primary and secondary PDP Contexts. If the SS receives a Detach Request the test execution continues from step A15, otherwise from step B15. SS shall check that no further deactivate request messages are sent during this time. |
|
|
A15 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the primary context. |
|
|
A16 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the secondary context. |
|
|
A17 |
SS |
Start timer ‘T3386’ and wait until is expires to ensure that UE does not respond to Modify PDP Context Request(Net) after Detach Request has been sent from UE. |
||
|
A18 |
|
DETACH ACCEPT |
SS responds with DETACH ACCEPT message as a Detach Request was transmitted by the UE |
|
|
B15 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the primary context. (Allowed for Note 1 and Note 2). |
|
|
B15A |
|
SM STATUS |
Cause set to #81(For Primary PDP) |
|
|
B16 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Send a modify request to UE for the secondary context. (Allowed for Note 1 and Note 2). |
|
|
B17 |
|
SM STATUS |
Cause set to #81(For Secondary PDP) |
|
|
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
Step 6: The IE Protocol Configuration Options is included in this message which has 0005H (Selected Bearer control Mode) set as container identifier in the Additional parameters list. Also, the container identifier contents are set as ‘02’H which means that MS/NW mode is selected.
Step 8: The request includes a bi-directional packet filter. For details please refer 23.060 Sec 9.2.2.3.
Steps 13:
– The TI shall indicate the primary PDP context
– The tear down indicator shall be set.
11.3.2a.5 Test requirements
Upon receipt of a request for deactivation of the primary PDP context, with the tear down indicator information element included, from the SS the UE shall deactivate the primary and secondary PDP contexts.
If the UE has not performed a detach procedure then, upon modification procedure initiated by the network, for deactivated PDP context, UE shall reply with SM STATUS message with cause #81, as confirmation that previously SS requested PDP context deactivation was performed by the UE.
11.3.3 Abnormal cases
11.3.3.1 T3390 Expiry
11.3.3.1.1 Definition
11.3.3.1.2 Conformance requirement
Expiry of timers
In the UE:
On the first expiry of timer T3390, the UE shall resent the message DEACTIVATE PDP CONTEXT REQUEST and shall reset and restart the timer T3390. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3390, the UE shall release all resources allocated and shall erase the PDP context related data.
Reference
3GPP TS 24.008 clause 6.1.3.4.3 a), case In the UE.
11.3.3.1.3 Test purpose
To test the behaviour of the UE when the SS does not reply to a DEACTIVATE PDP CONTEXT REQUEST message from the UE.
11.3.3.1.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
– PS Supported yes/no
– Method of activating a PDP context
– Method of deactivating a PDP context
Test procedure
A PDP context is activated by the user and accepted by the SS. PDP context deactivation is then requested by the user. The UE shall send a DEACTIVATE PDP CONTEXT REQUEST message five times with T3390 seconds between each message. After that, the UE shall release the PDP context. T3390 seconds after the fifth message the SS shall send a MODIFY PDP CONTEXT REQUEST message for the deactivated context and the UE shall reply with SM STATUS with cause set to #81 ‘Transaction identifier not known’.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
Initiate a context activation |
||
|
1a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to either Originating Streaming Call, Originating Interactive Call or Originating Background Call or OriginatingSubscribedTrafficCall |
||
|
1b |
|
SERVICE REQUEST |
||
|
1c |
SS |
The SS starts ciphering and integrity protection. |
||
|
2 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context |
|
|
2a |
SS |
The SS establishes the RAB. |
||
|
3 |
|
ACTIVATE PDP CONTEXT ACCEPT |
Accept the PDP context |
|
|
4 |
UE |
Initiate a context deactivation |
||
|
5 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of a PDP context |
|
|
6 |
SS |
T3390 seconds |
||
|
7 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of a PDP context |
|
|
8 |
SS |
T3390 seconds |
||
|
9 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of a PDP context |
|
|
10 |
SS |
T3390 seconds |
||
|
11 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of a PDP context |
|
|
12 |
SS |
T3390 seconds |
||
|
13 |
|
DEACTIVATE PDP CONTEXT REQUEST |
Request a deactivation of a PDP context |
|
|
14 |
SS |
Wait T3390 seconds |
||
|
14a |
UE |
The UE releases the PDP context and all allocated resources |
||
|
15 |
|
MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION) |
Try to modify the deactivated context. |
|
|
16 |
|
SM STATUS |
Cause set to #81 |
|
Specific message contents
Steps 2, 5, 7, 9, 11 and 13: TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, and 15: TI flag in TI IE is set to 1.
Steps 2, 3, 5, 7, 9, 11, 13, and 15: The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these test steps.
11.3.3.1.5 Test requirements
If SS does not respond to the UE initiated PDP context deactivation procedure, the UE shall retransmit four more DEACTIVATE PDP CONTEXT Requests four times, with T3390 timer expiry between the successive messages, before releasing resources allocated to the PDP context and deleting PDP context related data.
11.3.3.2 Collision of UE and network initiated PDP context deactivation requests
11.3.3.2.1 Definition
11.3.3.2.2 Conformance requirement
If the UE and the network initiated PDP context deactivation requests collide, the UE and the network shall each reply with the message DEACTIVATE PDP CONTEXT ACCEPT and shall stop timer T3390 and T3395, respectively.
Reference
3GPP TS 24.008 clause 6.1.3.4.3 b).
11.3.3.2.3 Test purpose
To test the behaviour of the UE when there is a collision between an UE initiated and network initiated context deactivation.
11.3.3.2.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN
Related ICS/IXIT statements
– PS Supported yes/no
– Method of activating a PDP context
– Method of deactivating a PDP context
Test procedure
A PDP context is activated by the user and accepted by the SS. Context deactivation is then requested by the user. Upon receipt of the DEACTIVATE PDP CONTEXT REQUEST message the SS sends a DEACTIVATE PDP CONTEXT REQUEST message. The UE shall reply with only one DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of this message the SS sends a DEACTIVATE PDP CONTEXT ACCEPT message.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
Initiate a context activation |
||
|
1a |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to either Originating Streaming Call, Originating Interactive Call or Originating Background Call or OriginatingSubscribedTrafficCall |
||
|
1b |
|
SERVICE REQUEST |
||
|
1c |
SS |
The SS starts ciphering and integrity protection. |
||
|
2 |
|
ACTIVATE PDP CONTEXT REQUEST |
Activate a PDP context |
|
|
2a |
SS |
SS establishes the RAB |
||
|
3 |
|
ACTIVATE PDP CONTEXT ACCEPT |
Accept the PDP context |
|
|
4 |
UE |
Initiate a context deactivation |
||
|
5 |
|
DEACTIVATE PDP CONTEXT REQUEST |
UE requests deactivation of a PDP context |
|
|
6 |
|
DEACTIVATE PDP CONTEXT REQUEST |
SS requests deactivation of a PDP context and starts T3390 and T3395 |
|
|
7 |
|
DEACTIVATE PDP CONTEXT ACCEPT |
UE accepts the PDP context deactivation requested by the SS |
|
|
7a |
SS |
SS stops T3395 |
||
|
8 |
|
DEACTIVATE PDP CONTEXT ACCEPT |
SS accepts the PDP context deactivation requested by the UE |
|
|
9 |
SS |
SS releases the RAB |
||
|
10 |
SS |
SS waits for expiry of T3390 to ensure no further deactivate request messages are sent |
||
Specific message contents
Steps 2 and 5. TI flag (bit 8) in TI IE is set to 0 (transaction initiated by the UE).
Steps 3, 6 and 8. TI flag in TI IE is set to 1.
Steps 2, 3, 5, 6, 7 and 8. The value of TIO IE (bits 5-7) of the transaction identifier (TI) is the same in these test steps.
11.3.3.2.5 Test requirements
When UE and SS initiated PDP context deactivation requests collide, the UE shall reply with DEACTIVATE PDP CONTEXT ACCEPT to the SS.