45 Session Management Procedures

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

45.1 Definition

Test cases identified in TS 51.010-2 as “EC-GSM –IoT compatible” should consider the default cells in the “Initial Conditions” to be EC-GSM-IoT cells if the test has to be executed in “EC Mode. Otherwise the cell should be considered as a basic GPRS cell.

45.2 PDP context activation

45.2.1 Initiated by the mobile station

45.2.1.1 Attach initiated by context activation/QoS Offered by Network is the QoS Requested

45.2.1.1.1 Conformance requirement

PDP context activation shall initiate GPRS Attach by the MS when the MS is GPRS Detached.

In order to request a PDP context activation, the MS sends an ACTIVATE PDP CONTEXT REQUEST message to the network. If the QoS offered by the network is the same as the QoS requested by the mobile, then upon receipt of the message ACTIVATE PDP CONTEXT ACCEPT the MS shall stop timer T3380 and shall initiate establishment of the logical link with the offered QoS.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclauses 6.1.1 and 6.1.3.1.1.

45.2.1.1.2 Test purpose

To check the MS initiates a GPRS ATTACH if one is not already active. To test the behaviour of the MS when the network responds to a PDP context activation request with the requested QoS.

45.2.1.1.3 Method of test

Specific PICS statements:

– GPRS Auto Attach (TSPC_AddInfo_on_auto_GPRS_AP)

PIXIT statements:

-Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-DEREGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

If the MS is attached, it should be triggered to initiates a GPRS detach procedure. A context activation is then requested by the user. On receipt of the ACTIVATE PDP CONTEXT REQUEST message a ACTIVATE PDP CONTEXT ACCEPT is returned by the SS with the same requested QoS. The contents of the ACTIVATE PDP CONTEXT REQUEST message shall then be checked. The SS then waits for T3380 +10% seconds to ensure T3380 has been stopped and no more ACTIVATE PDP CONTEXT REQUEST messages are sent by the MS. The SS then sends a MODIFY PDP CONTEXT REQUEST message to which the MS shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the context has been set up.

Expected sequence

Step

Direction

Message

Comments

1

MS

If MS is not configured for GPRS auto attachment (see PICS), go to step 5.

2

MS

The MS initiates a GPRS detach (without power off) by MMI or by AT command.

3

MS -> SS

DETACH REQUEST

Detach type = ‘normal detach, GPRS detach’

4

SS -> MS

DETACH ACCEPT

5

MS

Initiate a context activation

6

MS -> SS

ATTACH REQUEST

Request attach

7

SS -> MS

ATTACH ACCEPT

Accept attach

Negotiated Ready timer value IE should not be included

Force to standby indicator set

8

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

9

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

10

SS

Wait for T3380 +10% seconds to ensure no further activate request messages come from the MS

11

SS -> MS

MODIFY PDP CONTEXT REQUEST

Send a modify request for the activated context

12

MS -> SS

MODIFY PDP CONTEXT ACCEPT

Accept the modification request to show context is activated

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Modify PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

As above

Modify PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

45.2.1.2 QoS Offered by Network is a lower QoS

45.2.1.2.1 QoS Accepted by MS

45.2.1.2.1.1 Conformance requirement

In order to request a PDP context activation, the MS sends an ACTIVATE PDP CONTEXT REQUEST message to the network. If the QoS offered by the network is acceptable to mobile, then upon receipt of the message ACTIVATE PDP CONTEXT ACCEPT the MS shall initiate establishment of the logical link with the offered QoS.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.1.1.

45.2.1.2.1.2 Test purpose

To test the behaviour of the MS when the network responds to a PDP context activation request with a lower QoS than that requested.

45.2.1.2.1.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

The requested QoS and Minimum QoS are set. A context activation is requested by the user. On receipt of the ACTIVATE PDP CONTEXT REQUEST message a ACTIVATE PDP CONTEXT ACCEPT is returned by the SS with a QoS lower than the requested but higher than or equal to the minimum. The SS then sends a MODIFY PDP CONTEXT REQUEST message and the MS shall respond with a MODIFY PDP CONTEXT ACCEPT message to confirm the context is active.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept a PDP context activation

4

SS -> MS

MODIFY PDP CONTEXT REQUEST

Send a modify request for the activated context

5

MS -> SS

MODIFY PDP CONTEXT ACCEPT

Accept the modification request to show context is activated

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

At least one value lower than in above but higher than or equal to minimum

Radio priority level

Arbitrarily chosen

Spare half octet

0

PDP address

omitted

Modify PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

As above

Modify PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

45.2.1.2.2 QoS Rejected by MS

45.2.1.2.2.1 Conformance requirement

In order to request a PDP context activation, the MS sends an ACTIVATE PDP CONTEXT REQUEST message to the network.

Upon receipt of the message ACTIVATE PDP CONTEXT ACCEPT offering a QoS which is not acceptable to the mobile, the MS shall initiate the PDP context deactivation procedure.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.1.1.

45.2.1.2.2.2 Test purpose

To test the behaviour of the MS when the QoS offered by the network in response to a PDP context activation request is not acceptable to the MS.

45.2.1.2.2.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

The requested QoS and Minimum QoS are set. A context activation is requested by the user. On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP CONTEXT ACCEPT message is returned by the SS with a QoS lower than the minimum. The MS shall then send a DEACTIVATE PDP CONTEXT REQUEST message. A DEACTIVATE PDP CONTEXT ACCEPT message will be sent in return by the SS.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

4

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Deactivate the PDP context

5

SS -> MS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

At least one value lower than in above and lower than minimum

Radio priority level

Arbitrarily chosen

Spare half octet

0

Deactivate PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM cause

QoS not acceptable

Deactivate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

45.2.2 PDP context activation requested by the network, successful and unsuccessful

Applicability

This test needs to take into account the number of contexts supported by the MS to be able to test the response when all contexts are activated and the network tries to initiate a new context.

45.2.2.1 Conformance requirement

1) Upon receipt of a REQUEST PDP CONTEXT ACTIVATION message:

– If the MS accepts the request the MS shall then initiate the PDP context activation procedure.

– If the MS rejects the request, the MS shall send a REQUEST PDP CONTEXT ACTIVATION REJECT message with one of the following causes:

– #26: insufficient resources;

– #31: activation rejected, unspecified;

– #40: feature not supported; or

– #95 – 111: protocol errors.

2) The MS shall not ignore the request.

3) If the MS accepts the request, the ACTIVATE PDP CONTEXT REQUEST message sent by the MS shall contain the parameters requested by the network in the REQUEST PDP CONTEXT ACTIVATION message, except for the offered QoS which may be changed by the MS.

4) Whenever a REQUEST PDP CONTEXT ACTIVATION message is received by the MS specifying a transaction identifier relating to a PDP context not in state PDP-INACTIVE, the MS shall locally deactivate the old PDP context relating to the received transaction identifier. Furthermore, the MS shall continue with the activation procedure of a new PDP context as indicated in the received message.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclauses 6.1.3.1.2, 6.1.3.1.4 and 8.3.2 (f).

45.2.2.2 Test purpose

To test the behaviour of the MS upon receipt of a context activation request from the network.

45.2.2.3 Method of test

Specific PICS statements:

PIXIT statements:

– Number of network initiated PDP contexts supported

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Case 1

For an MS that supports PDP Context Activation requested by the network.

Test procedure

A REQUEST PDP CONTEXT ACTIVATION message is sent by the SS. On receipt of the ACTIVATE PDP CONTEXT REQUEST message an ACTIVATE PDP CONTEXT ACCEPT message is returned by the SS. This is repeated until the maximum number of contexts supported by the MS are activated. If the MS cannot support seven PDP contexts then one greater than the maximum supported by the MS should be requested. In response to this activation request the MS shall return a REQUEST PDP CONTEXT ACTIVATION REJECT message with cause set to ‘insufficient resources’, ‘feature not supported’, ‘activation rejected, unspecified’ or ‘protocol errors’ using cause values #26, #31, #40 or #95-#111. A REQUEST PDP CONTEXT ACTIVATION message is then sent using a currently activated context transaction identifier. The MS shall activate this context in place of the previous context.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

Request a PDP context activation request

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

4

SS

Steps 1-3 are repeated for Min( number of Network Initiated contexts supported, 7 )

NOTE: If all 7 contexts are supported steps 5 and 6 should not be performed

5

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

Request a PDP context activation request

6

MS -> SS

REQUEST PDP CONTEXT ACTIVATION REJECT

The context activation request is rejected with cause ‘insufficient resources’, ‘feature not supported’, ‘activation rejected, unspecified’ or ‘protocol errors’ using cause values #26, #31, #40 or #95-111.

7

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

Request a PDP context activation request for an existing context

8

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation to replace the existing context

9

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

Case 2

For an MS that does not support PDP Context Activation requested by the network.

Test procedure

A REQUEST PDP CONTEXT ACTIVATION message is sent by the SS. The MS shall then send an REQUEST PDP CONTEXT ACTIVATION REJECT message with cause set to ‘insufficient resources’ or ‘feature not supported’ or ‘activation rejected, unspecified’ or ‘protocol errors’.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

Request a PDP context activation request

2

MS -> SS

REQUEST PDP CONTEXT ACTIVATION REJECT

Reject the PDP context activation request with cause ‘insufficient resources’, ‘feature not supported’, ‘activation rejected, unspecified’ or ‘protocol errors’ using cause values #26, #31, #40 or #95-111.

Specific message contents

As default except:

Request PDP Context Activation

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

Offered PDP address

Arbitrarily chosen

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

As above

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Request PDP Context Activation Reject

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

PDP address

As above

SM cause

‘insufficient resources’ or ‘feature not supported’ or ‘activation rejected, unspecified’ or ‘protocol errors’

45.2.3 Void

45.2.4 Abnormal cases

45.2.4.1 T3380 Expiry

45.2.4.1.1 Conformance requirement

1) On the first expiry of the timer T3380, the MS shall resend the PDP CONTEXT ACTIVATION REQUEST.

2) On the second expiry of the timer T3380, the MS shall resend the PDP CONTEXT ACTIVATION REQUEST.

3) On the third expiry of the timer T3380, the MS shall resend the PDP CONTEXT ACTIVATION REQUEST.

4) On the fourth expiry of the timer T3380, the MS shall resend the PDP CONTEXT ACTIVATION REQUEST.

5) On the fifth expiry of the timer T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic PDP context activation re-attempt shall be performed.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.1.5.

45.2.4.1.2 Test purpose

To test the behaviour of the MS when the network does not reply to PDP CONTEXT ACTIVATION REQUEST

45.2.4.1.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A context activation is requested by the user. The MS shall send the ACTIVATE PDP CONTEXT REQUEST message five times with T3380 ±10 % seconds between each message. After this no further ACTIVATE PDP CONTEXT REQUEST messages shall be sent by the MS.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

3

SS

T3380 ±10% seconds

4

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

5

SS

T3380 ±10% seconds

6

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

7

SS

T3380 ±10% seconds

8

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

9

SS

T3380 ±10% seconds

10

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

11

SS

Wait for T3380 +10% seconds to ensure no further ACTIVATE PDP CONTEXT REQUEST messages are sent by the MS

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

45.2.4.2 Collision of MS initiated and network requested PDP context activation

45.2.4.2.1 Conformance requirement

In the event of collision between MS initiated and network initiated PDP context activation requests, the MS shall discard the REQUEST PDP CONTEXT ACTIVATION message and shall wait for an ACTIVATE PDP CONTEXT ACCEPT message.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.1.5.

45.2.4.2.2 Test purpose

To test the behaviour of the MS when there is a collision between an MS initiated and network requested PDP context activation.

45.2.4.2.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Case 1

For an MS that supports PDP Context Activation requested by the network.

Test procedure

A context activation is requested by the user. After receipt of the ACTIVATE PDP CONTEXT REQUEST message the SS sends a REQUEST PDP CONTEXT ACTIVATION message followed by an ACTIVATE PDP CONTEXT ACCEPT message in a time less than T3380 (Use T3380/2). The MS shall send no messages within this time.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

3

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

Request a PDP context activation request

4

SS

Wait for T3380/2 seconds to ensure MS does not resend ACTIVATE PDP CONTEXT REQUEST

5

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

Case 2

For an MS that does not support PDP Context Activation requested by the network.

Test procedure

A context activation is requested by the user. After receipt of the ACTIVATE PDP CONTEXT REQUEST message the SS sends a REQUEST PDP CONTEXT ACTIVATION message. The MS shall send a REQUEST PDP CONTEXT ACTIVATION REJECT message with cause set to ‘insufficient resources’ or ‘feature not supported’ or ‘activation rejected, unspecified’ or ‘protocol errors’. The SS then sends an ACTIVATE PDP CONTEXT ACCEPT.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP context activation

3

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

Request a PDP context activation request

4

MS -> SS

REQUEST PDP CONTEXT ACTIVATION REJECT

The context activation request is rejected with cause ‘insufficient resources’, ‘feature not supported’, ‘activation rejected, unspecified’ or ‘protocol errors’ using cause values #26, #31, #40 or #95-111.

5

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

APN

Arbitrarily chosen

Request PDP Context Activation

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

Offered PDP address

As requested by the MS

APN

As requested by the MS (Case 1)

Different from requested by the MS (Case 2)

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Request PDP Context Activation Reject

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

SM cause

‘insufficient resources’ or ‘feature not supported’ or ‘activation rejected, unspecified’ or ‘protocol errors’

45.2.4.3 Network initiated PDP context activation request for an already activated PDP context (on the MS side)

45.2.4.3.1 Definition

45.2.4.3.2 Conformance requirement

If the MS receives a REQUEST PDP CONTEXT ACTIVATION message with the same combination of APN, PDP type and PDP address as an already activated PDP context, the MS shall deactivate the existing PDP context and, if any, all the linked PDP contexts (matching the combination of APN, PDP type and PDP address) locally without notification to the network and proceed with the requested PDP context activation.

Reference

3GPP TS 24.008 clause 6.1.3.1.5 d).

45.2.4.3.3 Test purpose

To test the behaviour of the MS when it detects a network initiated PDP context activation for the PDP context already activated on the MS side.

45.2.4.3.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

– Network requested PDP context activation supported (TSPC_AddInfo_N_req_PDP_CA)

PIXIT statements:

Test procedure

A PDP context activation is requested by the user. SS accepts PDP context activation. Secondary PDP context activation is requested by the user. SS accepts secondary PDP context activation. SS sends a REQUEST PDP CONTEXT ACTIVATION message with the same combination of APN, PDP type and PDP address as an already activated PDP context. 2 cases are expected:

Case A (MS supports “Network requested PDP context activation”):
The MS deactivates the existing PDP context and linked secondary PDP context (matching the combination of APN, PDP type and PDP address) locally without notification to the SS and proceeds with the requested PDP context activation.

Case B (MS does not support “Network requested PDP context activation”):
The MS sends REQUEST PDP CONTEXT ACTIVATION REJECT message with cause set to ‘insufficient resources’ or ‘feature not supported’ or ‘activation rejected, unspecified’ or ‘protocol errors’ and the existing PDP contexts stay still active.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

MS requests a PDP context activation

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

SS accepts the PDP context activation

4

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

MS requests a secondary PDP context activation

5

SS -> MS

ACTIVATE SECONDARY PDP CONTEXT ACCEPT

SS accepts the secondary PDP context activation

6

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

SS requests a PDP context activation with the same combination of APN, PDP type and PDP address as the activated PDP context

If the MS supports “Network requested PDP context activation” branch A is performed, otherwise branch B is performed.

7A

MS

MS locally deactivates the activated PDP context and the secondary PDP context

8A

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

MS replies with a Request PDP context activation

9A

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

SS accepts the PDP context activation

10A

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of the secondary PDP context

11A

MS -> SS

SM STATUS

Cause set to #81. This verifies that the secondary PDP context was locally deactivated.

12A

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of the first PDP context

13A

MS -> SS

SM STATUS

Cause set to #81. This verifies that the first PDP context was locally deactivated.

7B

MS -> SS

REQUEST PDP CONTEXT ACTIVATION REJECT

The context activation request is rejected with cause ‘insufficient resources’, ‘feature not supported’, ‘activation rejected, unspecified’ or ‘protocol errors’ using cause values #26, #31, #40 or #95-111.

8B

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of the secondary PDP context

9B

MS -> SS

MODIFY PDP CONTEXT ACCEPT

MS Accepts PDP context modification.

Specific message contents

None.

45.2.4.4 Network reject with Extended Wait Timer

45.2.4.4.1 Conformance requirement

An MS configured for NAS signalling low priority indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured to NAS signalling low priority" except for the following cases in which the MS shall set the low priority indicator to "MS is not configured for NAS signalling low priority":

– the MS is performing an attach for emergency bearer services;

– the MS has a PDN connection for emergency bearer services established and is performing mobility management procedures, or is establishing a PDN connection for emergency bearer services;

– the MS is accessing the network with access class 11 – 15; or

– the MS is responding to paging.

The network may use the NAS signalling low priority indication for NAS level mobility management congestion control on a per core network node basis and APN based congestion control.

If the NAS signalling low priority indication is provided in an ACTIVATE PDP CONTEXT REQUEST message, the SGSN stores the NAS signalling low priority indication within the default PDP context activated due to this request

The network may detect and start performing the APN based congestion control when one or more APN congestion criteria as specified in 3GPP TS 23.060 [74] are met. The network may store an APN congestion back-off time on a per MS and congested APN basis and reject any subsequent PDP context activation request, secondary PDP context activation request or PDP context modification request from the MS targeted towards the congested APN before the APN congestion back-off time for the congested APN elapses.

Reference

3GPP TS 24.008 clauses 1.8 and 6.1.3.11

45.2.4.4.2 Test purpose

1) To verify that the LAP indicator can be set in the UE.

2) To verify that the Delay Tolerant indicator is sent by the UE.

3) To verify that the UE uses the back-off timer if the network reject a request with the T3396 timer.

45.2.4.4.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A PDP context activation is requested by the user. The UE shall send the ACTIVATE PDP CONTEXT REQUEST. The SS responds with the ACTIVATE PDP CONTEXT REJECT message with cause code #26, “insufficient resources”, and the T3396 timer with a value of 10 seconds. The UE starts the T3396 timer with the value of 10 seconds. When timer T3396 has expired the UE requests a PDP context activation.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP Context Activation

The SS verifies that the IE “Device properties” is set to “MS is configured for NAS signalling low priority”

3

SS -> MS

ACTIVATE PDP CONTEXT REJECT

The SS includes the IEs SM Cause with value #26 “insufficient resources” and T3396 with value 10 seconds.

MS starts timer T3396 with the value of 10 seconds.

4

MS

Initiate a PDP Context Activation

5

SS

The SS verifies that the UE does not initiate any communication before the T3396 timer has expired

6

MS

Initiate a PDP Context Activation

7

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Request a PDP Context Activation

8

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP Context Activation

Specific message contents

None.

45.2.5 Secondary PDP context activation procedures

45.2.5.1 Successful Secondary PDP Context Activation Procedure Initiated by the MS

45.2.5.1.1 QoS Offered by Network is the QoS Requested

45.2.5.1.1.1 Definition

45.2.5.1.1.2 Conformance requirement

In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the MS shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network, enter the state PDP-ACTIVE-PENDING and start timer T3380. The message shall contain the selected NSAPI. The MS shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the MS. The message shall also include a QoS profile, a requested LLC SAPI and the Linked TI. The QoS profile is the requested QoS.

Reference

3GPP TS 24.008 clauses 6.1.3.2 and 6.1.3.2.1.

45.2.5.1.1.3 Test purpose

To test the behaviour of the MS when SS responds to a Secondary PDP context activation request with the requested QoS.

45.2.5.1.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

PIXIT statements:

Test procedure

A PDP context activation is requested by the MS and accepted by the SS. Secondary PDP context activation is requested by the MS. On receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message an ACTIVATE SECONDARY PDP CONTEXT ACCEPT is returned by the SS with the same requested QoS. The SS then waits for T3380 seconds to ensure T3380 has been stopped and no more ACTIVATE SECONDARY PDP CONREXT REQUEST messages are sent by the MS. The SS then sends a MODIFY PDP CONTEXT REQUEST message to which the MS shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the PDP context has been activated.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a secondary PDP context activation

5

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request a Secondary PDP context activation.

Check that TFT filed is present in message and TFT operation is "Create a new TFT".

6

SS -> MS

ACTIVATE SECONDARY PDP CONTEXT ACCEPT

Accept the Secondary PDP context activation, the QoS is set to the requested QoS.

7

SS

Wait for T3380 seconds to ensure no further activate request messages come from the MS

8

SS -> MS

MODIFY PDP CONTEXT REQUEST

SS sends a modify request to MS for the activated context

9

MS -> SS

MODIFY PDP CONTEXT ACCEPT

The MS accepts the modification request from the network to show context is activated

Specific message contents

45.2.5.1.2 QoS Offered by Network is a lower QoS
45.2.5.1.2.1 QoS accepted by MS

45.2.5.1.2.1.1 Definition

45.2.5.1.2.1.2 Conformance requirement

In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the MS shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network, enter the state PDP-ACTIVE-PENDING and start timer T3380. The message shall contain the selected NSAPI. The MS shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the MS. The message shall also include a QoS profile, a requested LLC SAPI and the Linked TI. The QoS profile is the requested QoS.

Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the MS shall stop timer T3380 and enter the state PDP-ACTIVE. If the offered QoS parameters received from the network differ from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure.

In GSM the MS shall initiate establishment of the logical link for the LLC SAPI indicated by the network with the offered QoS and selected radio priority level if no logical link has been already established for that SAPI. If the LLC SAPI indicated by the network can not be supported by the MS, the MS shall initiate the PDP context deactivation procedure.

Reference

3GPP TS 24.008 clauses 6.1.3.2 and 6.1.3.2.1.

45.2.5.1.2.1.3 Test purpose

To test the behaviour of the MS when the SS responds to a Secondary PDP context activation request with a lower QoS than that requested.

45.2.5.1.2.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

PIXIT statements:

Test procedure

The requested QoS and Minimum QoS are set. A PDP context activation is requested by the MS and accepted by the SS. Secondary context activation is requested by the user. On receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message an ACTIVATE SECONDARY PDP CONTEXT ACCEPT is returned by the SS with a QoS lower than the requested but higher than or equal to the minimum. The SS then sends a MODIFY PDP CONTEXT REQUEST message and the MS shall respond with a MODIFY PDP CONTEXT ACCEPT message to confirm the context is active.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a secondary PDP context activation

5

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request a Secondary PDP context activation.

Check that TFT filed is present in message and TFT operation is "Create a new TFT".

6

SS -> MS

ACTIVATE SECONDARY PDP CONTEXT ACCEPT

Accept a Secondary PDP context activation, the QoS is lower than the requested QoS and higher that minimum QoS.

7

SS -> MS

MODIFY PDP CONTEXT REQUEST

Send a modify request to MS for the activated context

8

MS -> SS

MODIFY PDP CONTEXT ACCEPT

Accept the modification request from network to show context is activated

Specific message contents

None.

45.2.5.1.2.2 QoS rejected by MS

45.2.5.1.2.2.1 Definition

45.2.5.1.2.2.2 Conformance requirement

In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the MS shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network, enter the state PDP-ACTIVE-PENDING and start timer T3380. The message shall contain the selected NSAPI. The MS shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the MS. The message shall also include a QoS profile, a requested LLC SAPI and the Linked TI. The QoS profile is the requested QoS.

Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the MS shall stop timer T3380 and enter the state PDP-ACTIVE. If the offered QoS parameters received from the network differ from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure.

In GSM the MS shall initiate establishment of the logical link for the LLC SAPI indicated by the network with the offered QoS and selected radio priority level if no logical link has been already established for that SAPI. If the LLC SAPI indicated by the network can not be supported by the MS, the MS shall initiate the PDP context deactivation procedure.

Reference

3GPP TS 24.008 clauses 6.1.3.2 and 6.1.3.2.1.

45.2.5.1.2.2.3 Test purpose

To test the behaviour of the MS when the SS responds to a Secondary PDP context activation request with a lower QoS than that requested and not acceptable by the MS.

45.2.5.1.2.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

PIXIT statements:

Test procedure

The requested QoS and Minimum QoS are set. PDP context activation is requested by the user and accepted by the SS. Secondary PDP context activation is requested by the user. On receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message an ACTIVATE SECONDARY PDP CONTEXT ACCEPT message is returned by the SS with the QoS lower than the minimum. The MS shall then send a DEACTIVATE PDP CONTEXT REQUEST message for the secondary PDP context. A DEACTIVATE PDP CONTEXT ACCEPT message will be sent in return by the SS.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a secondary PDP context activation

5

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request a Secondary PDP context activation

Check that TFT filed is present in message and TFT operation is "Create a new TFT".

6

SS -> MS

ACTIVATE SECONDARY PDP CONTEXT ACCEPT

Accept the Secondary PDP context activation with QoS lower than Minimum QoS

7

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request deactivation of the secondary PDP context

SM Cause = #37, ‘QoS not accepted’

Tear down indicator IE shall not be included

8

SS -> MS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation

Specific message contents

None

45.2.5.2 Unsuccessful Secondary PDP Context Activation Procedure Initiated by the MS

45.2.5.2.1 Definition

45.2.5.2.2 Conformance requirement

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network may reject the MS initiated PDP context activation by sending an ACTIVATE SECONDARY PDP CONTEXT REJECT message to the MS.

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REJECT message, the MS shall stop timer T3380 and enter the state PDP-INACTIVE.

Reference

3GPP TS 24.008 clauses 6.1.3.2 and 6.1.3.2.2.

45.2.5.2.3 Test purpose

To test the behaviour of the MS when network rejects the MS initiated Secondary PDP context activation.

45.2.5.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

PIXIT statements:

Test procedure

A PDP context activation is requested by the user and accepted by the SS. Secondary context activation is requested by the user. On receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message from the MS, an ACTIVATE SECONDARY PDP CONTEXT REJECT with cause #43 ‘unknown PDP context’ is returned by the SS. SS shall wait for T3380 seconds to ensure that the MS sends no more ACTIVATE SECONDARY PDP CONTEXT REQUEST messages.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a secondary PDP context activation

5

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request a Secondary PDP context activation.

Check that TFT filed is present in message and TFT operation is "Create a new TFT".

6

SS -> MS

ACTIVATE SECONDARY PDP CONTEXT REJECT

SS rejects the Secondary PDP context activation with cause ‘#43: unknown PDP context’

7

SS

Wait for T3380 seconds to ensure no further ACTIVATE SECONDARY PDP CONTEXT REQUEST messages come from the MS

Specific message contents

None.

45.2.5.3 Abnormal cases

45.2.5.3.1 T3380 Expiry

45.2.5.3.1.1 Definition

45.2.5.3.1.2 Conformance requirement

1) On the first expiry of the timer T3380, the MS shall re-send the ACTIVATE SECONDARY PDP CONTEXT REQUEST.

2) On the second expiry of the timer T3380, the MS shall re-send the ACTIVATE SECONDARY PDP CONTEXT REQUEST.

3) On the third expiry of the timer T3380, the MS shall re-send the ACTIVATE SECONDARY PDP CONTEXT REQUEST.

4) On the fourth expiry of the timer T3380, the MS shall re-send the ACTIVATE SECONDARY PDP CONTEXT REQUEST.

5) On the fifth expiry of the timer T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic secondary PDP context activation re-attempt shall be performed.

Reference

3GPP TS 24.008 clause 6.1.3.2.3 a).

45.2.5.3.1.3 Test purpose

To test the behaviour of the MS when the SS does not reply to ACTIVATE SECONDARY PDP CONTEXT REQUEST message.

45.2.5.3.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

PIXIT statements:

Test procedure

A PDP context is activated by the user and accepted by the SS. Secondary PDP context activation is requested by the user. The MS shall send ACTIVATE SECONDARY PDP CONTEXT REQUEST message five times with T3380 seconds between each message. After this, no further ACTIVATE SECONDARY PDP CONTEXT REQUEST messages shall be sent by the MS.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a secondary PDP context activation

5

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request a Secondary PDP context activation

6

SS

T3380 +10% seconds

7

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request the Secondary PDP context activation

8

SS

T3380 +10% seconds

9

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request the Secondary PDP context activation

10

SS

T3380 +10% seconds

11

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request the Secondary PDP context activation

12

SS

T3380 +10% seconds

13

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request the Secondary PDP context activation

14

SS

Wait for T3380 +10% seconds to ensure no further ACTIVATE SECONDARY PDP CONTEXT REQUEST messages are sent by the MS

Specific message contents

None.

45.3 PDP context modification procedure

45.3.1 Network initiated PDP context modification

45.3.1.1 Conformance requirement

1) Upon receipt of a MODIFY PDP CONTEXT REQUEST message.

– If the MS can accept the modification requested, the MS shall reply with the MODIFY PDP CONTEXT ACCEPT message.

– If the MS is unable to accept the modification requested, the MS shall initiate the PDP context deactivation procedure for the NSAPI that has been indicated in the message MODIFY PDP CONTEXT REQUEST – the reject cause IE value of the DEACTIVATE PDP CONTEXT REQUEST message shall indicate "QoS not accepted".

2) The MS shall either accept the modification request or deactivate the PDP context, it shall not ignore the modification request.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.2.

45.3.1.2 Test purpose

To test the behaviour of the MS upon receipt of a MODIFY PDP CONTEXT REQUEST message.

45.3.1.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A PDP context is activated by the user and accepted by the SS. A MODIFY PDP CONTEXT REQUEST message is then sent to the MS with a QoS that is acceptable to the MS (higher than or equal to the minimum QoS set in the MS). The MS shall send a MODIFY PDP CONTEXT ACCEPT message in return. A MODIFY PDP CONTEXT REQUEST message is then sent to the MS with a QoS that is not acceptable to the MS (lower than the minimum QoS set in the MS). The MS shall send a DEACTIVATE PDP CONTEXT REQUEST message in return.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of a PDP context

5

MS -> SS

MODIFY PDP CONTEXT ACCEPT

Accept the PDP context modification

6

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of a PDP context

7

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Reject the PDP context modification by deactivating the PDP context. Cause set to ‘QoS not acceptable’

8

SS -> MS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Modify PDP Context Request (used in step 4)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

Higher than or equal to the minimum QoS and lower than the requested QoS.

Modify PDP Context Request (used in step 6)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

Lower than the minimum QoS

Modify PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

Deactivate PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM cause

QoS not acceptable

Deactivate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

45.3.2 MS initiated PDP context modification

45.3.2.1 MS initiated PDP Context Modification accepted by network

45.3.2.1.1 Definition

45.3.2.1.2 Conformance requirement

In order to initiate the procedure, the MS sends the MODIFY PDP CONTEXT REQUEST message to the network, enters the state PDP-MODIFY-PENDING and starts timer T3381. The message may contain the requested new QoS and/or the TFT and the requested LLC SAPI (used in GSM).

Upon receipt of the MODIFY PDP CONTEXT REQUEST message, the network may reply with the MODIFY PDP CONTEXT ACCEPT message in order to accept the context modification. The reply message may contain the negotiated QoS and the radio priority level based on the new QoS profile and the negotiated LLC SAPI that shall be used in GSM by the logical link.

Upon receipt of the MODIFY PDP CONTEXT ACCEPT message, the MS shall stop the timer T3381. If the offered QoS parameters received from the network differs from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure.

Reference

3GPP TS 24.008 clauses 6.1.3.3 and 6.1.3.3.2.

45.3.2.1.3 Test purpose

To test the behaviour of the MS upon receipt of a MODIFY PDP CONTEXT ACCEPT message from the network with

– Requested QoS;

45.3.2.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

MS Higher Layer release (TSPC_MS_HIGHER_LAYER_RELEASE)

PIXIT statements:

Test procedure

For a R97 to R7 MS, MS initiated PDP Context Modification for first PDP context is supported.

For a R8 MS, MS initiated PDP Context Modification for first PDP context is not supported. Hence this TC is not applicable.

The requested QoS and Minimum QoS are set. A PDP context is activated by the user and accepted by the SS. The MS initiates a PDP context modification by sending a MODIFY PDP CONTEXT REQUEST message with new QoS. The SS accepts the context modification and replies with the MODIFY PDP CONTEXT ACCEPT message with the QoS requested. The SS waits ‘T3390’ seconds to confirm that UE will not initiate a PDP context deactivation.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request the modification of a PDP context, with new QoS

5

SS -> MS

MODIFY PDP CONTEXT ACCEPT

Accept the PDP context modification with QoS requested

6

SS waits ‘T3390’ seconds to confirm UE

does not initiate PDP context deactivation.

Specific message contents

None.

45.3.2.2 MS initiated PDP Context Modification not accepted by the network

45.3.2.2.1 Definition

45.3.2.2.2 Conformance requirement

In order to initiate the procedure, the MS sends the MODIFY PDP CONTEXT REQUEST message to the network, enters the state PDP-MODIFY-PENDING and starts timer T3381. The message may contain the requested new QoS and/or the TFT and the requested LLC SAPI (used in GSM).

Upon receipt of a MODIFY PDP CONTEXT REQUEST message, the network may reject the MS initiated PDP context modification request by sending a MODIFY PDP CONTEXT REJECT message to the MS. The message shall contain a cause code that typically indicates one of the following:

# 26: insufficient resources;

# 32: Service option not supported;

# 41: semantic error in the TFT operation;

# 42: syntactical error in the TFT operation;

# 44: semantic errors in packet filter(s);

# 45: syntactical errors in packet filter(s);

# 95 – 111: protocol errors.

Upon receipt of a MODIFY PDP CONTEXT REJECT message, the MS shall stop timer T3381 and enter the state PDP-ACTIVE.

Reference

3GPP TS 24.008 clauses 6.1.3.3, 6.1.3.3.2 and 6.1.3.3.3.

45.3.2.2.3 Test purpose

To test the behaviour of the MS upon receipt of a MODIFY PDP CONTEXT REJECT message from the network.

45.3.2.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

  • MS Higher Layer release (TSPC_MS_HIGHER_LAYER_RELEASE)

PIXIT statements:

Test procedure

For a R97 to R7 MS, MS initiated PDP Context Modification for first PDP context is supported.

For a R8 MS, MS initiated PDP Context Modification for first PDP context is not supported. Hence this TC is not applicable. A PDP context is activated by the user and accepted by the SS. The MS initiates a PDP context modification by sending a MODIFY PDP CONTEXT REQUEST message. The SS rejects the context modification and replies with the MODIFY PDP CONTEXT REJECT with cause set to # 26: insufficient resources.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request the modification of a PDP context

5

SS -> MS

MODIFY PDP CONTEXT REJECT

SS rejects PDP context modification

SM cause set to # 26: ‘insufficient resources’

6

SS

Wait for T3381 seconds to ensure no further MODIFY PDP CONTEXT REQUEST messages are sent by the MS

Specific message contents

None.

45.3.3 Abnormal cases

45.3.3.1 T3381 Expiry

45.3.3.1.1 Definition

45.3.3.1.2 Conformance requirement

On the first expiry of timer T3381, the MS shall resend the MODIFY PDP CONTEXT REQUEST message reset and restart timer T3381. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3381, the MS may continue to use the previously negotiated QoS or it may initiate the PDP context deactivation procedure.

Reference

3GPP TS 24.008 clause 6.1.3.3.4 a) case: In the MS.

45.3.3.1.3 Test purpose

To test the behaviour of the MS when SS does not reply to MODIFY PDP CONTEXT REQUEST message.

45.3.3.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

  • MS Higher Layer release (TSPC_MS_HIGHER_LAYER_RELEASE)

PIXIT statements:

Test procedure

For a R97 to R7 MS, MS initiated PDP Context Modification for first PDP context is supported.

For a R8 MS, MS initiated PDP Context Modification for first PDP context is not supported. Hence this TC is not applicable.

A PDP context activation is requested by the user and accepted by the SS. The MS shall send MODIFY PDP CONTEXT REQUEST message five times with T3381 seconds between each message. After this no further MODIFY PDP CONTEXT REQUEST messages shall be sent by the MS.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

4

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request modification of the PDP context, with new QoS

5

SS

T3381 ±10% seconds

6

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request modification of the PDP context, with new QoS

7

SS

T3381 ±10% seconds

8

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request modification of the PDP context, with new QoS

9

SS

T3381 ±10% seconds

10

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request modification of the PDP context, with new QoS

11

SS

T3381 ±10% seconds

12

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request modification of the PDP context, with new QoS

13

SS

Wait for T3381 +10% seconds to ensure no further MODIFY PDP CONTEXT REQUEST messages are sent by the MS. The MS may initiate PDP context deactivation procedure.

Specific message contents

None.

45.3.3.2 Collision of MS and network initiated PDP context modification procedures

45.3.3.2.1 Definition

45.3.3.2.2 Conformance requirement

A collision of a MS and network initiated PDP context modification procedures is identified by the MS if a MODIFY PDP CONTEXT REQUEST message is received from the network after the MS has sent a MODIFY PDP CONTEXT REQUEST message itself, and both messages contain the same TI and the MS has not yet received a MODIFY PDP CONTEXT ACCEPT message from the network.

In the case of such a collision, the network initiated PDP context modification shall take precedence over the MS initiated PDP context modification. The MS shall terminate internally the MS initiated PDP context modification procedure, enter the state PDP-Active and proceed with the network initiated PDP context modification procedure by sending a MODIFY PDP CONTEXT ACCEPT message. The network shall ignore the MODIFY PDP CONTEXT REQUEST message received in the state PDP-MODIFY-PENDING. The network shall proceed with the network initiated PDP context modification procedure as if no MODIFY PDP CONTEXT REQUEST message was received from the MS.

Reference

3GPP TS 24.008 clause 6.1.3.3.4 b).

45.3.3.2.3 Test purpose

To test behaviour of the MS when it identifies collision of the MS and SS initiated PDP context modification with the same TI.

45.3.3.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Specific PICS statements:

MS Higher Layer release (TSPC_MS_HIGHER_LAYER_RELEASE)

PIXIT statements:

Test procedure

For a R97 to R7 MS, MS initiated PDP Context Modification for first PDP context is supported.

For a R8 MS, MS initiated PDP Context Modification for first PDP context is not supported. Hence this TC is not applicable.

A PDP context is activated by the user and accepted by the SS. The MS initiates a PDP context modification by sending a MODIFY PDP CONTEXT REQUEST message. Then the SS initiates the PDP context modification by sending MODIFY PDP CONTEXT REQUEST message with the same TI. The MS shall reply to the SS initiated PDP context modification procedure by sending MODIFY PDP CONTEXT ACCEPT message with the same TI.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a PDP context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context activation

4

MS -> SS

MODIFY PDP CONTEXT REQUEST

Request modification of the PDP context, with new QoS

5

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request modification of the PDP context with the same TI

6

MS

MS identifies collision, terminates internally the MS initiated PDP context modification procedure

7

MS -> SS

MODIFY PDP CONTEXT ACCEPT

Accept SS initiated PDP context modification.

The TI flag set to 0.

8

SS

Wait for T3381 +10% seconds from Step 4 to ensure no further MODIFY PDP CONTEXT REQUEST messages are sent by the MS

Specific message contents

Activate PDP Context Request (used in step 2)

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Modify PDP Context Request (MS to Network direction) (used in step 4)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

Modify PDP Context Request (Network to MS direction) (used in step 5)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Modify PDP Context Accept (used in step 7)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

45.4 PDP context deactivation procedure

45.4.1 PDP context deactivation initiated by the MS

45.4.1.1 Conformance requirement

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:

– #26: insufficient resources;

– #36: regular PDP context deactivation; or

– #37: QoS not accepted.

Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the MS shall stop timer T3390.

– Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION or SM‑STATUS is received by the MS 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 MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and remain in the PDP-INACTIVE state.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclauses 6.1.3.3.1 and 8.3.2 (b).

45.4.1.2 Test purpose

To test the behaviour of the MS upon receipt of a DEACTIVATE PDP CONTEXT ACCEPT message from the network.

45.4.1.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A PDP context is activated by the user and accepted by the SS. The context deactivation is then requested by the user. The MS 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 +10% seconds to ensure T3390 has been stopped and that no further messages are sent from the MS. If the MS did not initiate detach procedure, the SS shall then send a MODIFY PDP CONTEXT REQUEST for the deactivated context and the MS shall reply with an SM STATUS message with cause #81 ‘transaction identifier not known’.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a context deactivation

5

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

6

SS -> MS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation

7

SS

Wait for T3390 +10% seconds to ensure no further deactivate request messages are sent

Note: The MS may initiate Detach procedure during this time.

8A

MS -> SS

DETACH REQUEST

9A

SS -> MS

DETACH ACCEPT

8B

SS -> MS

MODIFY PDP CONTEXT REQUEST

Send a modify request for the deactivated context.

9B

MS -> SS

SM STATUS

Cause set to #81

Note: Branch ‘A’ is applicable if the MS initiates Detach procedure after the PDP context is deactivated. Otherwise branch ‘B’ is applicable.

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Deactivate PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM cause

Regular Deactivation

Deactivate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Modify PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

As above

SM Status

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM Cause

#81

45.4.2 PDP context deactivation initiated by the network

45.4.2.1 Conformance requirement

The MS shall, upon receipt of the DEACTIVATE PDP CONTEXT REQUEST message, reply with a DEACTIVATE PDP CONTEXT ACCEPT message.

– Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION or SM‑STATUS is received by the MS 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 MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and remain in the PDP-INACTIVE state.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclauses 6.1.3.3.2 and 8.3.2 (b).

45.4.2.2 Test purpose

To test the behaviour of the MS upon receipt of a DEACTIVATE PDP CONTEXT REQUEST message from the network.

45.4.2.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

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 MS shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message. If the MS did not initiate detach procedure, the SS shall then send a MODIFY PDP CONTEXT REQUEST for the deactivated context and the MS shall reply with an SM STATUS message with cause #81 ‘transaction identifier not known’.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

SS -> MS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

5

MS -> SS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation.

Wait for 10 seconds. The MS may initiate Detach procedure.

6A

MS -> SS

DETACH REQUEST

6B

SS -> MS

MODIFY PDP CONTEXT REQUEST

Send a modify request for the deactivated context.

7B

MS -> SS

SM STATUS

Cause set to #81

Note: Branch ‘A’ is applicable if the MS initiates Detach procedure after the PDP context is deactivated. Otherwise branch ‘B’ is applicable.

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Deactivate PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

SM cause

Regular Deactivation

Deactivate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

Modify PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

As above

SM Status

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM Cause

#81

45.4.3 Abnormal cases

45.4.3.1 T3390 Expiry

45.4.3.1.1 Conformance requirement

1) On the first expiry of timer T3390, the MS shall resend the message DEACTIVATE PDP CONTEXT REQUEST.

2) On the second expiry of timer T3390, the MS shall resend the message DEACTIVATE PDP CONTEXT REQUEST.

3) On the third expiry of timer T3390, the MS shall resend the message DEACTIVATE PDP CONTEXT REQUEST.

4) On the fourth expiry of timer T3390, the MS shall resend the message DEACTIVATE PDP CONTEXT REQUEST.

5) On the fifth expiry of timer T3390, the MS shall release all resources allocated and shall erase the PDP context related data.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.3.3.

45.4.3.1.2 Test purpose

To test the behaviour of the MS when the network does not reply to a DEACTIVATE PDP CONTEXT REQUEST message from the MS.

45.4.3.1.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A PDP context is activated by the user and accepted by the SS. A context deactivation is then requested by the user. The MS shall send a DEACTIVATE PDP CONTEXT REQUEST message five times with T3390 ±10% seconds between each message. T3390 +10 % seconds after the fifth message the SS shall send a MODIFY PDP CONTEXT REQUEST message for the deactivated context and the MS shall reply with SM STATUS with cause set to #81 ‘Transaction identifier not known’.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a context deactivation

5

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

6

SS

T3390 ±10% seconds

7

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

8

SS

T3390 ±10% seconds

9

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

10

SS

T3390 ±10% seconds

11

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

12

SS

T3390 ±10% seconds

13

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

14

SS

Wait T3390 +10% seconds

15

SS -> MS

MODIFY PDP CONTEXT REQUEST

Try to modify the deactivated context.

16

MS -> SS

SM STATUS

Cause set to #81

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Deactivate PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM cause

Regular Deactivation

Modify PDP Context Request

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

As above

SM Status

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM Cause

#81

45.4.3.2 Collision of MS and network initiated PDP context deactivation requests

45.4.3.2.1 Conformance requirement

If the MS and the network initiated PDP context deactivation requests collide, the MS and the network shall each reply with the message DEACTIVATE PDP CONTEXT ACCEPT and shall stop timer T3390 and T3395, respectively.

Reference

3GPP TS 04.08 / 3GPP TS 24.008 subclause 6.1.3.3.3.

45.4.3.2.2 Test purpose

To test the behaviour of the MS when there is a collision between an MS initiated and a network initiated context deactivation.

45.4.3.2.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A PDP context is activated by the user and accepted by the SS. A 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 MS shall reply with only one DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of this message the SS sends a DEACTIVATE PDP CONTEXT ACCEPT message.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a context deactivation

5

MS -> SS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

6

SS -> MS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context

7

MS -> SS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation

8

SS -> MS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation

Specific message contents

As default except:

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

Deactivate PDP Context Request (used in step 5)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

SM cause

Regular Deactivation

Deactivate PDP Context Request (used in step 6)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

SM cause

Regular Deactivation

Deactivate PDP Context Accept (used in step 7)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

0

Deactivate PDP Context Accept (used in step 8)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

45.4.4 PDP context deactivation initiated by the network / Tear down indicator

45.4.4.1 Conformance requirement

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 as the PDP context associated with this specific TI shall be deactivated. 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.

The Tear down indicator IE is included in the 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 as the PDP context associated with this specific TI shall be deactivated.

Reference

3GPP TS 24.008 subclauses 6.1.3.4, 8.3.2 (b) and 9.5.14.1.

45.4.4.2 Test purpose

To test the behaviour of the MS upon receipt of a DEACTIVATE PDP CONTEXT REQUEST message from the network including Tear down indicator IE.

45.4.4.3 Method of test

Specific PICS statements:

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A PDP context is activated by the user and accepted by the SS. A Secondary PDP context is activated by the user and accepted by the SS. A DEACTIVATE PDP CONTEXT REQUEST message is then sent by the SS indicating the TI of second PDP context and including Tear down indicator IE. The MS shall reply with a DEACTIVATE PDP CONTEXT ACCEPT message. The SS shall then send a MODIFY PDP CONTEXT REQUEST including the TI of second PDP context and the MS shall reply with an SM STATUS message with cause #81 ‘transaction identifier not known’. The SS shall then send a MODIFY PDP CONTEXT REQUEST including the TI of the first PDP context and the MS shall reply with an SM STATUS message with cause #81 ‘transaction identifier not known’.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

Initiate a context activation

2

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context

3

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

4

MS

Initiate a secondary PDP context activation

5

MS -> SS

ACTIVATE SECONDARY PDP CONTEXT REQUEST

Request a Secondary PDP context activation

6

SS -> MS

ACTIVATE SECONDARY PDP CONTEXT ACCEPT

Accept the Secondary PDP context activation

7

SS -> MS

DEACTIVATE PDP CONTEXT REQUEST

Request a deactivation of a PDP context. Include TI of second PDP context and Tear down indicator flag set to 1.

8

MS -> SS

DEACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context deactivation.

TI is the same as step 7.

9

SS -> MS

MODIFY PDP CONTEXT REQUEST

Send a modify request including the TI of second PDP context.

10

MS -> SS

SM STATUS

Cause set to #81

11

SS -> MS

MODIFY PDP CONTEXT REQUEST

Send a modify request including the TI of first PDP context.

12

MS -> SS

SM STATUS

Cause set to #81

Specific message contents

None.

45.5 Unknown or Unforeseen Transaction Identifier/Non-semantical Mandatory Information Element Errors

45.5.1 Error cases

45.5.1.1 Conformance requirement

45.5.1.1.1 Conformance requirement for release 98 and earlier MS

The mobile station shall reject a session management message other than SM-STATUS received with TI value "111" by immediately sending an SM-STATUS message with TI value "111". For a session management message received with TI different from "111", the following procedures shall apply:

– Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS is received by the MS 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 or has been [recently] deactivated, the MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and remain in the PDP-INACTIVE state.

– When a REQUEST PDP CONTEXT ACTIVATION message is received with a transaction identifier flag set to "1", this message shall be ignored.

When on receipt of a message:

– an "imperative message part" error; or

– a "missing mandatory IE" error;

is diagnosed or when a message containing:

– a syntactically incorrect mandatory IE; or

– an IE unknown in the message, but encoded as "comprehension required"; or

– an out of sequence IE encoded as "comprehension required";

is received, the mobile station shall proceed as follows:

– If the message was an SM message the SM-STATUS message with cause # 96 "invalid mandatory information" shall be returned.

– If a mobile station receives a GMM message or SM message with message type not defined for the PD or not implemented by the receiver, it shall return a status message (GMM STATUS or SM STATUS depending on the protocol discriminator) with cause #97 ‘message type non-existent or not implemented’.

– If the mobile station receives a message not compatible with the protocol state, the mobile station shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause #98 "Message type not compatible with protocol state". When the message was a GMM message the GMM-STATUS message with cause #98 "Message type not compatible with protocol state" shall be returned. When the message was a SM message the SM-STATUS message with cause #98 ‘Message type not compatible with protocol state’ shall be returned.

– Other syntactic errors.

This subclause applies to the analysis of the value part of an information element. It defines the following terminology:

– An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as ‘reserved’, or if its value part violates syntactic rules given in the specification of the value part. However it is not a syntactical error that a type 4 standard IE specifies in its length indicator a greater length than possible according to the value part specification: extra bits are ignored.

Reference

3GPP TS 04.08 subclauses 8.3.2 and 8.5.

3GPP TS 04.07 subclause 11.4.2.

45.5.1.1.2 Conformance requirement for release 99 and later MS

The mobile station and network shall ignore a session management message with TI EXT bit = 0. Otherwise, the following procedures shall apply:

– Whenever any session management message except REQUEST PDP 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.

– When REQUEST PDP CONTEXT ACTIVATION message is received with a transaction identifier flag set to "1", this message shall be ignored.

When on receipt of a message,

– an "imperative message part" error; or

– a "missing mandatory IE" error;

is diagnosed or when a message containing:

– a syntactically incorrect mandatory IE; or

– an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007); or

– an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007) is received,

the mobile station shall proceed as follows:

If the message is not one of the messages listed in subclauses 8.5.1, 8.5.2, 8.5.3, 8.5.4 and 8.5.5 a) or b), the mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 96 "Invalid mandatory information". If the message was a GMM message the GMM-STATUS message with cause #96 " Invalid mandatory information" shall be returned. If the message was an SM message the SM-STATUS message with cause # 96 "invalid mandatory information" shall be returned.

– the network shall proceed as follows:

When the message is not one of the messages listed in subclause 8.5.3 b), c), d) or e) and 8.5.5 a) or c), the network shall either:

– try to treat the message (the exact further actions are implementation dependent), or

– ignore the message except that it should return a status message (STATUS, or MM STATUS (depending on the protocol discriminator), GMM STATUS, or SM STATUS) with cause # 96 "Invalid mandatory information".

This subclause applies to the analysis of the value part of an information element. It defines the following terminology:

– An IE is defined to be syntactically incorrect in a message if it contains at least one value defined as ‘reserved’, or if its value part violates syntactic rules given in the specification of the value part. However it is not a syntactical error that a type 4 standard IE specifies in its length indicator a greater length than possible according to the value part specification: extra bits are ignored.

Reference

3GPP TS 24.008 subclauses 6.1, 8.3.2, 8.5 and 9.5.2.1.

3GPP TS 24.007 subclause 11.4.2.

45.5.1.2 Test Purpose

To test the behaviour of the MS when messages with unknown or unforeseen transaction identifiers or non-semantical mandatory information element errors occur.

45.5.1.3 Method of test

Specific PICS statements:

– MS Higher Layer Release (TSPC_MS_HIGHER_LAYER_RELEASE)

PIXIT statements:

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.

Test procedure

A PDP context activation is requested by the SS with the transaction identifier set to ‘1’. The MS shall not respond to this request.

A PDP context is then activated from the MS. An invalid accept message is then sent by the SS. The MS shall then send an SM STATUS message. After the MS has sent an ACTIVATE PDP CONTEXT REQUEST message the SS sends a MODIFY PDP CONTEXT REQUEST message with the same transaction identifier. The MS shall reply with an SM STATUS message with the cause set to #98 ‘Message type not compatible with protocol state’.

After T3380 has expired 10% seconds the MS shall send another ACTIVATE PDP CONTEXT REQUEST message. The SS sends back a Session Management message with an unknown message type. The MS shall reply with an SM STATUS message with the cause set to #97 ‘Message type non-existent or not implemented’.

After a further T3380 has expired the MS shall send another ACTIVATE PDP CONTEXT REQUEST message 10% seconds. Another invalid accept message is sent by the SS.

After a further T3380 has expired 10% seconds a valid accept message with QoS length greater than 3 is sent by the SS. This shall be accepted by the MS.

A deactivate message is then sent from the SS coded with the extension mechanism for TI. Therefore the TIO value is set to 111 and the transaction identifier extension TIE is set to an unused value greater than 6(no reserved value) . A MS implemented release 98 or earlier should reply with an SM STATUS message with transaction identifier set to ‘111’. A Rel.99 MS shall reply with an SM STATUS message with cause #81 ‘invalid transaction identifier value’.

A deactivate message is then sent from the SS with a different transaction identifier to the one used in the activate request message sent by the MS. The MS shall reply with an SM STATUS message with cause #81 ‘invalid transaction identifier value’.

Two invalid modification messages are then sent to the MS in turn. The MS shall respond each time with an SM-STATUS message with cause # 96 "invalid mandatory information".

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

SS -> MS

REQUEST PDP CONTEXT ACTIVATION

Request the activation of a PDP context with the transaction identifier flag set to "1"

2

SS

Wait 30 seconds to ensure MS does not request context activation

3

MS

Initiate a context request

4

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context from the MS

5

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Unknown IE encoded as ‘comprehension required’

6

MS -> SS

SM STATUS

Cause set to #96

7

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context from the MS (auto-generated)

This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message

8

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of the PDP context

9

MS -> SS

SM STATUS

Cause set to #98 ‘Message type not compatible with protocol state’.

10

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context from the MS (auto-generated)

This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message

11

SS -> MS

UNKNOWN MESSAGE

Message with unknown message type

12

MS -> SS

SM STATUS

Cause set to #97 ‘message type non-existent or not implemented’.

13

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context from the MS (auto-generated)

This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message

14

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Out of sequence IE encoded as ‘comprehension required’

15

MS -> SS

SM STATUS

Cause set to #96

16

MS -> SS

ACTIVATE PDP CONTEXT REQUEST

Activate a PDP context from the MS (auto-generated)

This message shall be sent within T3380 seconds ±10% from the last ACTIVATE PDP CONTEXT REQUEST message

17

SS -> MS

ACTIVATE PDP CONTEXT ACCEPT

Accept the PDP context

Step 18A, 19A is performed for release 98 and earlier MS and step 18B, 19B for release 99 and later MS implementation

18A

SS -> MS

DEACTIVATE PDP CONTEXT REQUEST

TI set to "111"

18B

SS -> MS

DEACTIVATE PDP CONTEXT REQUEST

TIO=111 and TIE=not used value greater than 6

19A

MS -> SS

SM STATUS

TI set to "111", cause value not checked

19B

MS->SS

SM STATUS

with cause #81 "invalid transaction identifier value

20

SS -> MS

DEACTIVATE PDP CONTEXT REQUEST

Try to deactivate the context with a different transaction identifier to that used to activate the context

21

MS -> SS

SM STATUS

Cause set to # 81

22

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of the PDP context

23

MS -> SS

SM STATUS

Cause set to # 96

24

SS -> MS

MODIFY PDP CONTEXT REQUEST

Request the modification of the PDP context

25

MS -> SS

SM STATUS

Cause set to # 96

Specific message contents

As default except:

Request PDP Context Activation

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

1

Offered PDP address

Arbitrarily chosen

Activate PDP Context Request

Information Element

Value/remark

Transaction identifier

In the range 0-6

Transaction identifier flag

0

NSAPI

In the range 5-15

Requested LLC SAPI

3, 5, 9 or 11

Requested QoS

Arbitrarily chosen

Requested PDP address

Arbitrarily chosen

Activate PDP Context Accept (used in step 5)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

PDP address

Arbitrarily chosen

‘Comprehension required IE’

0Fh NOTE: first four bits encoded as ‘comprehension required’

Activate PDP Context Accept (used in step 14)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above

Radio priority level

Arbitrarily chosen

Spare half octet

0

PDP address

omitted

‘Comprehension required IE’

07h NOTE: first four bits encoded as ‘comprehension required’

Protocol configuration options

Minimum length with Configuration protocol of ‘PPP’

Activate PDP Context Accept (used in step 17)

Information Element

Value/remark

Transaction identifier

As above

Transaction identifier flag

1

Negotiated LLC SAPI

As above

Negotiated QoS

As above but

For R97 and R98 : Length set to 5 and 2 extra octets set to 0 after the normal QoS octets

For R99 and Rel-4 : Length set to 13 and 2 extra octets set to 0 after the normal QoS octets

For Rel-5 and later: Length set to 16 and 2 extra octets set to 0 after the normal QoS octets

For Rel-7 and later: Length set to 18 and 2 extra octets set to 0 after the normal QoS octets

Radio priority level

Arbitrarily chosen

Spare half octet

0

PDP address

Arbitrarily chosen

Deactivate PDP Context Request (used in step 18)

Information Element

Value/remark

Transaction identifier

111

Transaction identifier flag

1

SM cause

24h, regular deactivation

Deactivate PDP Context Request (used in step 20)

Information Element

Value/remark

Transaction identifier

In the range 0-6, but different from the TI in the Activate PDP Context Request message

Transaction identifier flag

1

SM cause

24h, regular deactivation

Modify PDP Context Request (used in step 22)

Information Element

Value/remark

Transaction identifier

As in step 17

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

As above

New QoS

This IE will NOT be present

Modify PDP Context Request (used in step 24)

Information Element

Value/remark

Transaction identifier

As in step 17

Transaction identifier flag

1

Radio priority level

As above

Spare half octet

0

Requested LLC SAPI

Fh, NOTE: this is a reserved value

New QoS

Arbitrary value