11.1 PDP context activation

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

11.1.1 Initiated by the UE

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

11.1.1.1.1 Definition

11.1.1.1.2 Conformance requirement

SM procedures for identified access can only be performed if a GMM context has been established between the UE and the network. If no GMM context has been established, the MM sublayer has to initiate the establishment of a GMM context by use of the GMM procedures as described in chapter 4, 3GPP TS 24.008. After GMM context establishment, SM uses services offered by GMM (see 3GPP TS 24.007). Ongoing SM procedures are suspended during GMM procedure execution.

In UMTS only, integrity protected signalling (see 3GPP TS 24.008 clause 4.1.1.1.1 and in general, see 3GPP TS 33.102) is mandatory. In UMTS only, all protocols shall use integrity protected signalling. Integrity protection of all SM signalling messages is the responsibility of lower layers. It is the network which activates integrity protection. This is done using the security mode control procedure (TS 25.331).

In order to request a PDP context activation, the UE sends an ACTIVATE PDP CONTEXT REQUEST message to the network, enters the state PDP-ACTIVE-PENDING and starts timer T3380. The message contains the selected NSAPI, PDP type, requested QoS and, if the UE requests a static address, the PDP address.

If the QoS offered by the network is the same as the QoS requested by the UE, the UE shall accept the negotiated QoS.

In UMTS, both the network and the UE shall store the LLC SAPI and the radio priority in the PDP context. If a UMTS to GSM system change is performed, the new SGSN shall initiate establishment of the logical link using the negotiated QoS profile, the negotiated LLC SAPI, and selected radio priority level stored in the PDP context as in a GSM to GSM Routing Area Update.

A UE, which is capable of operating in both GSM and UMTS, shall use a valid LLC SAPI, while a UE which is capable of operating only in UMTS shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and any other possible confusion in the network.

NOTE 1: The radio priority level and the LLC SAPI parameters, though not used in UMTS, shall be included in the messages, in order to support handover between UMTS and GSM networks.

Reference

3GPP TS 24.008 clauses 6.1.1 and 6.1.3.1.1.

11.1.1.1.3 Test purpose

To check that the UE initiates a PS attach, if one is not already active, when PDP context activation is requested.

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

11.1.1.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

– Auto Attach supported yes / no

– Method of context activation

Test procedure

The UE is attached, then the Detach Request is originated from the UE indicating "GPRS detach without switching off". The SS responds with a Detach Accept after completing the security mode procedures. A PDP context activation is then requested by the user. The PS attach (ATTACH REQUEST) is then indirectly caused by a requested PDP context activation. The SS returns the ATTACH ACCEPT message to the UE. Now session management can proceed with PDP context activation.

On receipt of the ACTIVATE PDP CONTEXT REQUEST message an 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 seconds to ensure T3380 has been stopped and no more ACTIVATE PDP CONTEXT REQUEST messages are sent by the UE. The SS then sends a MODIFY PDP CONTEXT REQUEST message to which the UE shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the context has been set up.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
0a	UE			Detach is performed by the UE using MMI or AT Commands
0	SS			SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Detach".
1			DETACH REQUEST
1a	SS			The SS starts integrity protection.
2			DETACH ACCEPT	SS sends Detach Accept message.
2a	SS			The SS releases the RRC connection.
3	UE			Initiate a context activation
3a	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
4			ATTACH REQUEST	The UE requests attach
4a	SS			The SS starts integrity protection.
5			ATTACH ACCEPT	The SS accepts attach Negotiated Ready timer value IE should not be included Force to standby IE set to “Force to standby not indicated”
6			ACTIVATE PDP CONTEXT REQUEST	The UE requests a PDP context activation, enters the state PDP-ACTIVE-PENDING and starts timer T3380
6a	SS			The SS establishes the RAB.
7			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context activation and starts T3380
7a	UE			The UE stops T3380 and enters the state PDP-ACTIVE
8	SS			The SS waits for T3380 expiry to ensure no further activate request messages come from the UE
9			MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION)	The SS sends a modify request to UE for the activated context
10			MODIFY PDP CONTEXT ACCEPT (UE TO NETWORK DIRECTION)	The UE accepts the modification request from the SS. This re-confirms that step 6 was correctly executed in the UE.
11	SS			The SS releases the RRC connection due to inactivity (no user data transferred)

Specific message contents

None.

11.1.1.1.5 Test requirements

At step 0 the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Detach".

At step 3a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration".

When requesting a PDP context activation, the UE shall:

– initiate PS ATTACH;

– when the SS responds to a PDP context activation request, initiated by the UE, with the requested QoS, the UE shall complete the PDP context activation procedure. To check if the PDP context activation was successful, SS shall request PDP context modification and UE shall accept it.

11.1.1.1a Attach initiated by context activation/QoS Offered by Network is the QoS Requested/Correct handling of QoS extensions for rates above 8640 kbps

11.1.1.1a.1 Definition and applicability

UEs which support HS-PDSCH and supporting rates above 8640 kbps (UE Category 9 and/or UE Category 10).

11.1.1.1a.2 Conformance requirement

1. SM procedures for identified access can only be performed if a GMM context has been established between the UE and the network. If no GMM context has been established, the MM sublayer has to initiate the establishment of a GMM context by use of the GMM procedures as described in chapter 4. After GMM context establishment, SM uses services offered by GMM (see 3GPP TS 24.007). Ongoing SM procedures are suspended during GMM procedure execution. In UMTS only, integrity protected signalling (see 3GPP TS 24.008 clause 4.1.1.1.1 and in general, see 3GPP TS 33.102) is mandatory. In UMTS only, all protocols shall use integrity protected signalling. Integrity protection of all SM signalling messages is the responsibility of lower layers. It is the network which activates integrity protection. This is done using the security mode control procedure (TS 25.331).

2. In order to request a PDP context activation, the UE sends an ACTIVATE PDP CONTEXT REQUEST message to the network, enters the state PDP-ACTIVE-PENDING and starts timer T3380. The message contains the selected NSAPI, PDP type, requested QoS and, if the UE requests a static address, the PDP address. The UE shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the MS.

Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message, the network selects a radio priority level based on the QoS negotiated and may reply with an ACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the message ACTIVATE PDP CONTEXT ACCEPT the UE shall stop timer T3380, shall 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 UMTS, both the network and the UE shall store the LLC SAPI and the radio priority in the PDP context. If a UMTS to GSM system change is performed, the new SGSN shall initiate establishment of the logical link using the negotiated QoS profile, the negotiated LLC SAPI, and selected radio priority level stored in the PDP context as in a GSM to GSM Routing Area Update.

NOTE 1: The radio priority level and the LLC SAPI parameters, though not used in UMTS, shall be included in the messages, in order to support handover between UMTS and GSM networks.

3. The quality of service is a type 4 information element with a minimum length of 14 octets and a maximum length of 16 octets. The QoS requested by the MS shall be encoded both in the QoS attributes specified in octets 3-5 and in the QoS attributes specified in octets 6-14.

In the UE to network direction and in the network to UE direction the following applies:

– Octets 15 and 16 are optional. If octet 15 is included, then octet 16 shall also be included.

– A QoS IE received without octets 6-16, without octets 14-16, or without octets 15-16 shall be accepted by the receiving entity.

NOTE 2: This behaviour is required for interworking with entities supporting an earlier version of the protocol, or when the Maximum bit rate for downlink is negotiated to a value lower than 8700 kbps.

…

8	7	6		5		4	3	2	1
Quality of service IEI										octet 1
Length of quality of service IE										octet 2
0 0 spare		Delay class					Reliability class			octet 3
Peak throughput						0 spare	Precedence class			octet 4
0 0 0 spare				Mean throughput						octet 5
Traffic Class				Delivery order			Delivery of erroneous SDU			octet 6
Maximum SDU size										octet 7
Maximum bit rate for uplink										octet 8
Maximum bit rate for downlink										octet 9
Residual BER						SDU error ratio				octet 10
Transfer delay								Traffic Handling priority		octet 11
Guaranteed bit rate for uplink										octet 12
Guaranteed bit rate for downlink										octet 13
0 0 0 spare			Signal-ling Indicat-ion		Source Statistics Descriptor					octet 14
Maximum bit rate for downlink (extended)										octet 15
Guaranteed bit rate for downlink (extended)										octet 16

…

Maximum bit rate for downlink, octet 9 (see 3GPP TS 23.107)

Coding is identical to that of Maximum bit rate for uplink.

If the sending entity wants to indicate a Maximum bit rate for downlink higher than 8640 kbps, it shall set octet 9 to ”11111110”, i.e. 8640 kbps, and shall encode the value for the Maximum bit rate in octet 15.

…

Maximum bit rate for downlink (extended), octet 15
Bits
8 7 6 5 4 3 2 1
In MS to network direction and in network to MS direction:
0 0 0 0 0 0 0 0 Use the value indicated by the Maximum bit rate for downlink in octet 9.

0 0 0 0 0 0 0 1 Ignore the value indicated by the Maximum bit rate for downlink in octet 9. The maximum bit
rate is
0 1 0 0 1 0 1 0 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps), giving a range of values from
8700 kbps to 16000 kbps in 100 kbps increments.

Reference

3GPP TS 24.008 clauses 6.1.1, 6.1.3.1.1 and 10.5.6.5.

11.1.1.1a.3 Test purpose

To check that the UE initiates a PS attach, if one is not already active, when PDP context activation is requested.

To check that the UE performs correct handling of QoS extensions for rates above 8640 kbps, and to check that the UE is, as well, capable of correct handling of QoS not requiring the extension information.

To check the UE successfully completes the PDP context activation when the SS responds to the PDP context activation request with the requested QoS.

11.1.1.1a.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

– Auto Attach supported yes / no

– Method of context activation

– Supported downlink rates above 8640 kbps yes/no

Test procedure

Table 11.1.1.1a.1 Test execution test parameters

Execution	Maximum bit rate for downlink
1	Value supported by the UE which is less than 8640 kbps
2	Value supported by the UE which is bigger than 8640 kbps, see Note 1

The UE is attached, then the Detach Request is originated from the UE indicating "GPRS detach without switching off". The SS responds with a Detach Accept after completing the security mode procedures. A PDP context activation is then requested. The IE “Maximum bit rate for downlink” is selected according to Table 11.1.1.1a.1 for execution=1. The PS attach (ATTACH REQUEST) is then indirectly caused by the requested PDP context activation. The SS returns the ATTACH ACCEPT message to the UE. Now session management can proceed with PDP context activation.

The test case is repeated with test parameters according to Table 11.1.1.1a.1 for execution=2.

Note 1: A Rel-7 or later UE supporting higher HSDPA categories, 13 or above, is executed as category 9 or 10 depending on UE capability.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
0a	UE			Detach is performed by the UE using MMI or AT Commands
0	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Detach".
1			DETACH REQUEST
1a	SS			The SS starts integrity protection.
2			DETACH ACCEPT	The SS sends Detach Accept message.
2a	SS			The SS releases the RRC connection.
3	UE			The UE initiates a context activation with a requested “Maximum bit rate for downlink” according to Table 11.1.1.1a.1
3a	SS			The SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Registration".
4			ATTACH REQUEST	The UE requests attach
4a	SS			The SS starts integrity protection.
5			ATTACH ACCEPT	The SS accepts attach Negotiated Ready timer value IE should not be included Force to standby IE set to “Force to standby not indicated”
6			ACTIVATE PDP CONTEXT REQUEST	The UE requests a PDP context activation, enters the state PDP-ACTIVE-PENDING and starts timer T3380
6a	SS			The SS establishes the RAB.
7			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context activation and starts T3380
7a	UE			The UE stops T3380 and enters the state PDP-ACTIVE
8	SS			The SS waits for T3380 seconds to ensure no further activate request messages come from the UE
9			MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION)	The SS sends a modify request to UE for the activated context
10			MODIFY PDP CONTEXT ACCEPT (UE TO NETWORK DIRECTION)	The UE accepts the modification request from the SS. This re-confirms that step 6 was correctly executed in the UE.
11	SS			The SS releases the RRC connection due to inactivity (no user data transferred)

The test sequence is repeated according to Table 11.1.1.1a.1.

Specific message contents

None.

11.1.1.1a.5 Test requirements

At step 0 the UE shall send RRC CONNECTION REQUEST message with the IE Establishment cause set to "Detach";

At step 3a the UE shall send RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration";

At step 4 the UE shall initiate PS ATTACH;

At step 6 the UE shall send ACTIVE PDP CONTEXT REQUEST message with the IE Requested QoS and Maximum bit rate for downlink set to value according to Table 11.1.1.1a.1;

At step 10 the UE shall send a MODIFY PDP CONTEXT ACCEPT message.

11.1.1.2 QoS offered by the network is a lower QoS

11.1.1.2.1 Void

11.1.1.2.2 Void

11.1.1.3 Dual priority / T3396 override

11.1.1.3.1 Definition

Void

11.1.1.3.2 Conformance requirement

If timer T3396 is running for a specific APN, because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396 and SM cause value #26 "insufficient resources", upon request of the upper layers the MS can:

– send an ACTIVATE PDP CONTEXT REQUEST message to the same APN, with low priority indicator set to "MS is not configured for NAS signalling low priority"; or,

– send an ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message, with low priority indicator set to "MS is not configured for NAS signalling low priority", for an active PDP context established with low priority indicator set to "MS is not configured for NAS signalling low priority" exists.

If timer T3396 is running, because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message without APN containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396 and SM cause value #26 "insufficient resources", upon request of the upper layers the MS can:

– send an ACTIVATE PDP CONTEXT REQUEST message with low priority indicator set to "MS is not configured for NAS signalling low priority"; or

– send an ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message, with low priority indicator set to "MS is not configured for NAS signalling low priority", for an active PDP context established with low priority indicator set to "MS is not configured for NAS signalling low priority" exists.

For requests with low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall follow the procedures specified in subclause 6.1.3.1.3.

Reference

3GPP TS 24.008 clause 6.1.3.12.

11.1.1.3.3 Test purpose

To verify that a UE configured for dual priority that has T3396 is running for a specific APN can send a request to activate or modify the same APN, with low priority indicator set to "MS is not configured for NAS signalling low priority"

11.1.1.3.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.

The UE is configured for NAS signalling low priority

The UE is configured for NAS signalling low priority override

The UE is equipped with a USIM containing default values except for those listed below.

USIM field

Value

EF_UST

Service 96 is supported

EF_NASCONFIG

“NAS_SignallingPriority is set to “NAS signalling low priority”

“Override_NAS_SignallingLowPriority” is set to 1, as defined in TS 24.368, clause 5.3.

“ExtendedAccessBarring is set to 1 which indicate the extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8.

OverrideExtendedAccessBarring is set to 1 which indicate the Override extended access barring is applied for the UE” as defined in TS 24.368, clause 5.10

Related ICS/IXIT statements

– PS Supported yes/no

Test procedure

An ACTIVATE PDP CONTEXT REQUEST message is sent by the UE with an indication that the UE is configured for NAS signalling low priority. The request is rejected by the SS with T3396 and SM cause value #26 "insufficient resources.

The UE issues another ACTIVATE PDP CONTEXT REQUEST message, before the expiration of timer T3396, this time with an indication that the UE is not configured for NAS signalling low priority. The request is accepted by the SS.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	UE			Initiate a context activation
2			ACTIVATE PDP CONTEXT REQUEST	The UE requests a PDP context activation. Device properties = ‘MS is configured for NAS signalling low priority’
3			ACTIVATE PDP CONTEXT REJECT	SS reject the PDP context activation with SM cause value #26 "insufficient resources and the T3396 timer
4	UE			Cause the UE to request the activation of the same context with the NAS signalling low priority override indicator. (see Note)
5			ACTIVATE PDP CONTEXT REQUEST	The UE requests a PDP context activation, Device properties = ‘MS is not configured for NAS signalling low priority’
6	SS			The SS establishes the RAB.
7			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context activation and starts T3380
8	UE			The UE stops T3380 and enters the state PDP-ACTIVE
9	SS			The SS waits for T3380 expiry to ensure no further activate request messages come from the UE
10			MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION)	The SS sends a modify request to UE for the activated context
11			MODIFY PDP CONTEXT ACCEPT (UE TO NETWORK DIRECTION)	The UE accepts the modification request from the SS. This re-confirms that step 6 was correctly executed in the UE.
12	SS			The SS releases the RRC connection due to inactivity (no user data transferred)

Specific message contents

None.

11.1.1.3.5 Test requirements

Step 2: ACTIVATE PDP CONTEXT REQUEST message contains the Device properties IE set to ‘MS is configured for NAS signalling low priority’

Step 5: ACTIVATE PDP CONTEXT REQUEST message contains the Device properties IE set to ‘MS is not configured for NAS signalling low priority’. This message shall be sent before the expiry of timer T3396.

11.1.1.4 Dual priority / T3346 override

11.1.1.4.1 Definition

Void

11.1.1.4.2 Conformance requirement

The following abnormal cases can be identified:

…

m) Timer T3346 is running

The MS shall not start the service request procedure unless:

– the MS receives a paging; or

– the MS is an MS configured to use AC11 – 15 in selected PLMN; or

– the MS has a PDN connection for emergency bearer services established; or

– the MS is establishing a PDN connection for emergency bearer services; or

– the MS has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication and if the timer T3346 was started due to a NAS request message (ATTACH REQUEST, ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority".

The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped.

Reference

3GPP TS 24.008 clauses 4.7.13.5.

11.1.1.4.3 Test purpose

To verify that a MS configured for dual priority and which has sent a SERVICE REQUEST message indicating low NAS signalling priority, when it receives a SERVICE REJECT message with timer T3346 and MM cause value #22 “Congestion”, the UE sends an ACTIVATE PDP CONTEXT REQUEST message with the low priority indicator set to "MS is not configured for NAS signalling low priority” if higher layers in the UE request the activation of such a connection/context.

11.1.1.4.4 Method of test

Initial condition

System Simulator:

1 cell, default parameters.

User Equipment:

The UE is equipped with a USIM containing default values except for those listed below.

USIM field

Value

EF_UST

Service 96 is supported.

EF_NASCONFIG

“NAS_SignallingPriority is set to “NAS signalling low priority” as defined in TS 24.368, clause 5.3

“Override_NAS_SignallingLowPriority” is set to “enable”, as defined in TS 24.368, clause 5.9.

“ExtendedAccessBarring is set to 1 which indicate the extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8.

OverrideExtendedAccessBarring is set to 1 which indicate the Override extended access barring is applied for the UE” as defined in TS 24.368, clause 5.10

Related ICS/IXIT statements

Support of PS service Yes/No
Method of activating a PDP context Yes/No

Test procedure

A PDP context is activated by the UE. The UE initiates a PDP context modification by sending a SERVICE REQUEST message, indicating that the UE is configured for NAS signalling low priority. The SS sends a SERVICE REJECT message with cause 22 “Congestion” and the UE starts timer T3346. The UE sends a SERVICE REQUEST message with NAS signalling low priority override. The UE initiates a PDP context before expiry of T3346. The SS confirms that the UE initiates a PDP context activation with normal priority before ‘T3346’has expired.

Expected Sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a PDP context activation
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context
3			ACTIVATE PDP CONTEXT ACCEPT
3a	SS			The SS initiates a Radio Bearer release procedure and SS releases the RRC connection.
4			SERVICE REQUEST (UE TO NETWORK DIRECTION)	Request modification of PDP context Device properties = ‘MS is configured for NAS signalling low priority’
5			SERVICE REJECT (NETWORK TO UE DIRECTION)	Reject message with cause 22 “Congestion” and timer ‘T3346’ value included
6	UE			Initiate a PDP context activation with NAS signalling low priority override indicator
7			SERVICE REQUEST (UE TO NETWORK DIRECTION)	Device properties = ‘MS is not configured for NAS signalling low priority’
8			ACTIVATE PDP CONTEXT REQUEST	UE initiates PDP context before ‘T3346’ seconds
9			ACTIVATE PDP CONTEXT ACCEPT

Specific message contents

None.

11.1.1.4.5 Test requirements

Step 4: SERVICE REQUEST message contains the Device properties IE set to ‘MS is configured for NAS signalling low priority’.

Step 7: SERVICE REQUEST message contains the Device properties IE set to ‘MS is not configured for NAS signalling low priority’.

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

11.1.2.1 Definition

Void

11.1.2.2 Conformance requirement

1) Successful PDP context activation requested by the network

In order to request a PDP context activation, the network sends a REQUEST PDP CONTEXT ACTIVATION message to the UE and starts timer T3385. The message contains an offered PDP address. If available, the APN shall be included in the REQUEST PDP CONTEXT ACTIVATION message.

Upon receipt of a REQUEST PDP CONTEXT ACTIVATION message, the UE shall than either initiate the PDP context activation procedure as described in 3GPP TS 24.008 clause 6.1.3.1.1, or shall reject the activation request by sending a REQUEST PDP CONTEXT ACTIVATION REJECT message as described in 3GPP TS 24.008 clause 6.1.3.1.4. The value of the reject cause IE of the REQUEST PDP CONTEXT ACTIVATION REJECT message shall indicate the reason for rejection, e.g. "insufficient resources to activate another context".

The ACTIVATE PDP CONTEXT REQUEST message sent by the UE in order to initiate the PDP context activation procedure shall contain the PDP address, PDP Type and APN requested by the network in the REQUEST PDP CONTEXT ACTIVATION message.

Upon receipt of the ACTIVATE PDP CONTEXT REQUEST message, the network shall stop timer T3385.

The same procedures then apply as described for UE initiated PDP context activation (3GPP TS 24.008, clause 6.1.3.1.1.

2) Unsuccessful PDP context activation requested by the network

Upon receipt of the REQUEST PDP CONTEXT ACTIVATION message, the UE may reject the network requested PDP context activation by sending the REQUEST PDP CONTEXT ACTIVATION REJECT message to the network. The message contains the same TI as included in the REQUEST PDP CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes:

#26: insufficient resources;

#31: activation rejected, unspecified;

#40: feature not supported; or

#95 – 111: protocol errors.

The network shall stop timer T3385 and enter state PDP-INACTIVE.

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

Reference

3GPP TS 24.008 clauses 6.1.3.1.2, 6.1.3.1.4 and 8.3.2.f).

11.1.2.3 Test purpose

To test behaviour of the UE upon receipt of a PDP context activation request from the SS:

a) When UE supports PDP context activation requested by the network

b) When UE supporting PDP context activation requested by the network, receives REQUEST PDP CONTEXT ACTIVATION message with transaction identifier relating to an already active PDP context

c) When UE does not support PDP context activation requested by the network

11.1.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

Test procedure

A REQUEST PDP CONTEXT ACTIVATION message is sent by the SS. If UE does not accept PDP context activation, it shall send a REQUEST PDP CONTEXT ACTIVATION REJECT message (UE behaviour type B); else UE will start PDP context activation procedure (UE behaviour type A).

On receipt of the ACTIVATE PDP CONTEXT REQUEST message from the UE, an ACTIVATE PDP CONTEXT ACCEPT message is returned by the SS. This is repeated until the maximum number of PDP contexts supported by the UE is activated (up to two).

When maximum number of PDP contexts is reached, UE shall reject next REQUEST PDP CONTEXT ACTIVATION message.

In response to the last activation request the UE shall return a REQUEST PDP CONTEXT ACTIVATION REJECT message with cause set to ‘insufficient resources’, ‘activation rejected, unspecified’, ‘feature not supported’ or ‘protocol errors’ using cause values #26, #31, #40 or #95-111.

REQUEST PDP CONTEXT ACTIVATION message is then sent by the SS using transaction identifier of the currently active PDP context. The UE shall activate this context to replace the previous context.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			REQUEST PDP CONTEXT ACTIVATION	SS sends Request a PDP context activation to UE and starts timer T3385. UE behaviour type B: test case continues from Step 6
A2			ACTIVATE PDP CONTEXT REQUEST	UE behaviour type A:UE replies with a PDP context activation request, Traffic class set to Streaming class or Interactive class or Background class
A2a	SS			The SS stops timer T3385 and establishes the Radio Access Bearer.
A3			ACTIVATE PDP CONTEXT ACCEPT	SS accepts the PDP context activation. If maximum number of PDP contexts of 2 (in future implementations this number might change) is reached, test execution continues from Step A5.
A4	SS			Steps 1, A2, A2a and A3 are repeated until maximum number of PDP contexts is reached, using various values for Traffic class IE. NOTE: In future implementations, if all 7 contexts are activated steps A5, 6 and 6a shall not be performed.
A5			REQUEST PDP CONTEXT ACTIVATION	SS requests a PDP context activation and starts timer T3385
6			REQUEST PDP CONTEXT ACTIVATION REJECT	The PDP context activation request is rejected with cause ‘insufficient resources’ or ‘activation rejected, unspecified’ or ‘feature not supported’ or ‘protocol errors’ using cause values #26, #31, #40 or #95-111.
6a	SS			The SS stops timer T3385. UE behaviour type B: test case ends.
A7			REQUEST PDP CONTEXT ACTIVATION	SS requests a PDP context activation for an existing PDP context with the same TI value as one of the active PDP contexts and starts timer T3385
A8	UE			UE locally deactivates the old PDP context with the same TI value
A9			ACTIVATE PDP CONTEXT REQUEST	UE continues with the activation of a new PDP context to replace locally deactivated PDP context
A9a	SS			The SS stops timer T3385 and releases Radio Access Bearer for old PDP context.
A9b	SS			The SS establishes the Radio Access Bearer for new PDP context.
A10			ACTIVATE PDP CONTEXT ACCEPT	SS accepts the PDP context activation

Specific message contents

Case 1

Step 6: REQUEST PDP CONTEXT ACTIVATION REJECT message contains the same TI as included in the REQUEST PDP CONTEXT ACTIVATION message in step 5.

Step 7: TI IE value is equal to the TI value of one of the active PDP contexts, Offered PDP address IE value and/or Access point name IE value are (is) different from the corresponding IE value(s) in the existing PDP context.

11.1.2.5 Test requirements

The UE that is configured to support one or more PDP contexts simultaneously shall:

– accept PDP context activation initiated by the SS if number of active contexts is lower than the maximum.

– locally deactivate the old PDP context when a REQUEST PDP CONTEXT ACTIVATION message is received, specifying a transaction identifier relating to an active PDP context and continue with the activation procedure of a new PDP context as indicated in the received message.

The UE that does not support PDP Context Activation (a number of active contexts supported by the UE is equal to maximum or UE does not support PDP context) shall reject PDP context activation initiated by the SS.

11.1.3 Abnormal Cases

11.1.3.1 T3380 Expiry

11.1.3.1.1 Definition

11.1.3.1.2 Conformance requirement

1) On the first expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.

2) On the second expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.

3) On the third expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.

4) On the fourth expiry of the timer T3380, the UE shall re-send the PDP CONTEXT ACTIVATION REQUEST.

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

Reference

3GPP TS 24.008 clause 6.1.3.1.5 a).

11.1.3.1.3 Test purpose

To test the behaviour of the UE when the SS does not reply to PDP CONTEXT ACTIVATION REQUEST.

11.1.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 context

Test procedure

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

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a context activation
2			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation
3	SS			T3380 seconds
4			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation
5	SS			T3380 seconds
6			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation
7	SS			T3380 seconds
8			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation
9	SS			T3380 seconds
10			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation
11	SS			Wait for T3380 seconds to ensure no further ACTIVATE PDP CONTEXT REQUEST messages are sent by the UE

Specific message contents

None.

11.1.3.1.5 Test requirements

UE shall re-send the ACTIVATE PDP CONTEXT REQUEST to SS five times in order to initiate PDP context, with expiry of timer T3380 between messages. After fifth try, UE shall send no more ACTIVATE PDP CONTEXT REQUEST to SS.

11.1.3.2 Collision of UE initiated and network requested PDP context activation

11.1.3.2.1 Definition

This test needs to take into account the number of PDP contexts supported by the UE, to be able to test the response when the network tries to initiate a new context.

11.1.3.2.2 Conformance requirement

A collision of a UE initiated and a network requested PDP context activation procedure is identified by the UE if a REQUEST PDP CONTEXT ACTIVATION message is received from the network after the UE has sent an ACTIVATE PDP CONTEXT REQUEST message, and the UE has not yet received an ACTIVATE PDP CONTEXT ACCEPT or ACTIVATE PDP CONTEXT REJECT message.

NOTE: In general, the UE is unable to test if the PDP type, PDP address and APN in the REQUEST PDP CONTEXT ACTIVATION message are the same as those for the PDN to which it is attempting to activate a context. This is because the UE may have omitted one or more of the parameters in the ACTIVATE PDP CONTEXT REQUEST message, since it is relying on default values to be provided by the network.

In the case of such a collision, the UE initiated PDP context activation shall take precedence over the network requested PDP context activation. If the UE is able to compare the PDP type, PDP address and APN requested in the ACTIVATE PDP CONTEXT REQUEST message with those requested in the REQUEST PDP CONTEXT ACTIVATION message and these parameters are equal, then the UE shall discard the REQUEST PDP CONTEXT ACTIVATION message and shall wait for the network response to its ACTIVATE PDP CONTEXT REQUEST message. If the UE is not able to compare the PDP type, PDP address, and APN requested in the ACTIVATE PDP CONTEXT REQUEST message with those requested in the REQUEST PDP CONTEXT ACTIVATION message, then the UE shall send a REQUEST PDP CONTEXT ACTIVATION REJECT message with the cause ‘insufficient resources’ to the network, and wait for an ACTIVATE PDP CONTEXT ACCEPT message.

Reference

3GPP TS 24.008 clause 6.1.3.1.5 b), case: Static PDP address collision detected within the UE.

11.1.3.2.3 Test purpose

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

11.1.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

– Network requested PDP context activation supported yes/no

– Method of PDP context activation

Case 1

For an UE that supports PDP context activation requested by the network.

Test procedure

A PDP context activation is requested by the user with a static PDP address. 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 UE shall send no messages within this time.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a context activation
2			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation (with static PDP address)
3			REQUEST PDP CONTEXT ACTIVATION	Request a PDP context activation request
4	SS			Wait for T3380/2 seconds to ensure UE does not re-send ACTIVATE PDP CONTEXT REQUEST
5			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context activation

Case 2

For a UE that does not support PDP context activation requested by the network.

Test procedure

A PDP 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 UE shall send a REQUEST PDP CONTEXT ACTIVATION REJECT message with cause set to ‘insufficient resources’. The SS then sends an ACTIVATE PDP CONTEXT ACCEPT.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a context activation
2			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation
3			REQUEST PDP CONTEXT ACTIVATION	Request a PDP context activation
4			REQUEST PDP CONTEXT ACTIVATION REJECT	Cause set to ‘insufficient resources’.
5			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context activation

Specific message contents

For Case 1 and Case 2:

Step 2: ACTIVATE PDP CONTEXT REQUEST message contains PDP address and APN IEs.

Step 3: REQUEST PDPD CONTEXT ACTIVATION message contains the same PDP address and APN values as in Step 2.

11.1.3.2.5 Test requirements

In the case of such collision,

– UE that supports PDP context activation requested by the network shall discard the REQUEST PDP CONTEXT ACTIVATION message from SS and wait for an ACTIVATE PDP CONTEXT ACCEPT message.

– UE that does not support PDP context activation requested by the network shall reject PDP context activation initiated by the SS.

11.1.3.3 Network initiated PDP context activation request for an already activated PDP context (on the UE side)

11.1.3.3.1 Definition

11.1.3.3.2 Conformance requirement

If the UE 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 UE 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).

11.1.3.3.3 Test purpose

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

11.1.3.3.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 PDP context activation

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. The UE 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.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a context activation
2			ACTIVATE PDP CONTEXT REQUEST	UE requests a PDP context activation
3			ACTIVATE PDP CONTEXT ACCEPT	SS accepts the PDP context activation
4			ACTIVATE SECONDARY PDP CONTEXT REQUEST	UE requests a secondary PDP context activation
5			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	SS accepts the secondary PDP context activation
6			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
7	UE			UE locally deactivates the activated PDP context and the secondary PDP context
9			ACTIVATE PDP CONTEXT REQUEST	UE replies with a Request PDP context activation
10			ACTIVATE PDP CONTEXT ACCEPT	SS accepts the PDP context activation

Specific message contents

None.

11.1.3.3.5 Test requirements

When inconsistency of PDP context between the UE and network is detected by the UE, then local synchronisation procedure shall be initiated in the UE. The PDP context and all (if any) linked contexts are implicitly deactivated and the new request shall be proceeded.

11.1.3.4 Network reject with Back-off Timer

11.1.3.4.1 Definition

11.1.3.4.2 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.

References

3GPP TS 24.008 clauses 1.8 and 6.1.3.11

11.1.3.4.3 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.

11.1.3.4.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.

The UE is equipped with a USIM containing default values except for those listed below.

USIM field	Value
EF_UST	Service 96 is supported
EF_NASCONFIG	“NAS_SignallingPriority is set to “NAS signalling low priority” as defined in TS 24.368, clause 5.3
EF_NASCONFIG	“ExtendedAccessBarring is set to extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8

Related ICS/IXIT statements

– PS Supported yes/no

– Method of activating a context

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 60 seconds. The UE starts the T3396 timer with the value of 60 seconds. When timer T3396 has expired the UE requests a PDP context activation.

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 " Delay Tolerant Access”
2			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			ACTIVATE PDP CONTEXT REJECT	The SS includes the IEs SM Cause with value #26 “insufficient resources” and T3396 with value 60 seconds. MS starts timer T3396 with the value of 60 seconds.
3A	SS			Initiate a context activation.
3B	SS			The SS verifies that the UE does not initiate any communication before the T3396 timer has expired
3C	SS			Initiate a context activation.

5			ACTIVATE PDP CONTEXT REQUEST	Request a PDP context activation
6			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context activation

Specific message contents

None.

11.1.3.4.5 Test requirements

To pass the test the UE shall:

At step 2 the UE shall include the IE “Device properties”, set to “MS is configured for NAS signalling low priority”, in the ACTIVATE PDP CONTEXT REQUEST.
At step 3 the UE shall set the timer T3396 to the value of the “T3396” IE, as received in the ACTIVATE PDP CONTEXT REJECT message.
At step 3B the UE shall not initiate any communication attempts.

11.1.4 Secondary PDP context activation procedures

11.1.4.1 Successful Secondary PDP Context Activation Procedure Initiated by the UE

11.1.4.1.1 QoS Offered by Network is the QoS Requested

11.1.4.1.1.1 Definition

11.1.4.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 UE 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 UE shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the UE. The message shall also include a QoS profile, a requested LLC SAPI and the Linked TI. The QoS profile is the requested QoS. If present, the TFT shall be sent transparently through the SGSN to the GGSN to enable packet classification and policing for downlink data transfer.

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST, the network shall validate the message by verifying the TI given in the Linked TI IE to be any of the active PDP context(s). The same GGSN address shall be used by the SGSN as for the already established PDP context(s) for that PDP address. The network shall select a radio priority level based on the QoS negotiated and shall reply with an ACTIVATE SECONDARY PDP CONTEXT ACCEPT message, if the request can be accepted.

NOTE 1: If the UE requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107, the network should negotiate the parameter to a value that lies within the specified range.

Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the UE 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 UE, the UE shall either accept the negotiated QoS or initiate the PDP context deactivation procedure.

In UMTS, both SGSN and UE shall store the LLC SAPI and the radio priority in the PDP context. If a UMTS to GSM Routing Area Update is performed, the new SGSN shall initiate establishment of the logical link using the negotiated LLC SAPI, the negotiated QoS profile and selected radio priority level stored in the PDP context as in a GSM to GSM Routing Area Update.

An UE, which is capable of operating in both GSM and UMTS, shall use a valid LLC SAPI, while an UE which is capable of operating only in UMTS shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and any other possible confusion in the network. When the UE uses a valid LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the “LLC SAPI not assigned” value only when the UE uses the “LLC SAPI not assigned” value.

NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in UMTS, shall be included in the messages, in order to support handover between UMTS and GSM networks.

Reference

3GPP TS 24.008 clauses 6.1.3.2 and 6.1.3.2.1.

11.1.4.1.1.3 Test purpose

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

11.1.4.1.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

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

Related ICS/IXIT statements

– PS Supported yes/no

– Method of context activation

– Secondary PDP context activation supported yes/no

Test procedure

A 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 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 UE. The SS then sends a MODIFY PDP CONTEXT REQUEST message to which the UE shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the context has been set up.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	UE			Initiate a PDP context activation
1a	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
1b			SERVICE REQUEST	Service type = "signalling"
1c	SS			The SS starts integrity protection.
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context
2a	SS			The SS establishes the RAB
3			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context with the requested QoS
4	UE			The UE initiates a secondary PDP context activation
5			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 2.
6			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	The SS accepts the Secondary PDP context activation with the requested QoS
7	SS			The SS waits for T3380 seconds to ensure no further activate request messages come from the UE
8			MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION)	The SS sends a modify request to UE for secondary PDP context
9			MODIFY PDP CONTEXT ACCEPT (UE TO NETWORK DIRECTION)	The UE accepts the modification request from the SS. This re-confirms that step 5 was correctly executed in the UE.

Specific message contents

Step 2: TI flag (octet 1, Bit 8) in TI IE is set to ‘0’ and value of TIO (octet 1, Bits 765) is set in range 0-6.

Step 3: TI flag in TI IE is set to ‘1’ and value of TIO is the same as in Step 2. Step 5:

The Linked TI information element in ACTIVATE SECONDARY PDP CONTEXT REQUEST message specifies the TI for the PDP context already activated. The SS can derive PDP address for the secondary PDP context from the Linked TI,
TI flag in TI IE is set to ‘0’ and value of TIO is the same as in Step 2 and 3
NSAPI IE value is different from NSAPI value in Step 2

Step 6 and 8: TI flag in TI IE is set to ‘1’ and value of TIO is the same as in Step 5.

Step 9: TI flag in TI IE is set to ‘0’ and value of TIO is the same as in Step 5.

11.1.4.1.1.5 Test requirements

To pass the test the UE shall:

– when the SS responds to Secondary PDP context activation request initiated by the UE, with the requested QoS, the UE shall complete the Secondary PDP context activation procedure. To check if the Secondary PDP context activation was successful, the SS shall request PDP context modification and UE shall accept it.

11.1.4.1.2 QoS Offered by Network is a lower QoS

11.1.4.1.2.1 Void

11.1.4.1.2.2 Void

11.1.4.1.2.3 LLC SAPI rejected by the UE

Definition

This test can only be performed if LLC SAPI can be set by the user.

11.1.4.1.2.3.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 UE shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network.

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST, the network shall select a radio priority level based on the QoS negotiated and shall reply with an ACTIVATE SECONDARY PDP CONTEXT ACCEPT message, if the request can be accepted.

Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the UE shall stop timer T3380 and enter the state PDP-ACTIVE.

In GSM the UE shall initiate establishment of the logical link for the LLC SAPI indicated by the network 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 UE, the UE shall initiate the PDP context deactivation procedure.

11.1.4.1.2.3.3 Test Purpose

To verify the behaviour of the UE when the network responds to the ACTIVATE SECONDARY PDP CONTEXT REQUEST message with a negotiated LLC SAPI which is not supported by the UE.

Reference

3GPP TS 24.008, clause 6.1.3.2.1.

11.1.4.1.2.3.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

– User setting of LLC SAPI supported yes/no

– Method of setting LLC SAPI

– Method of context activation

– Secondary PDP context activation supported yes/no

Test procedure

The requested LLC SAPI is set. This is the only LLC SAPI supported by the UE. A PDP context activation is requested by the user and accepted by the SS. A 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 LLC SAPI not supported by the UE. The UE 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
	UE	SS
1	UE			Initiate a PDP context activation
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context
3			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context
4	UE			Initiate a secondary PDP context activation
5			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request a Secondary PDP context activation
6			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	Accept the Secondary PDP context activation with LLC SAPI not supported by the UE
7			DEACTIVATE PDP CONTEXT REQUEST	Request deactivation of all PDP contexts
8			DEACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context deactivation

Specific message contents

In step 3 Negotiated LLC SAPI IE is equal to Requested LLC SAPI IE in step 2 and step 5.

In step 7 SM cause IE shall have value #25: LLC or SNDCP failure. Also, Tear down indicator IE shall be included in the DEACTIVATE PDP CONTEXT REQUEST message to deactivate all PDP contexts for this PDP address.

11.1.4.2 Unsuccessful Secondary PDP Context Activation Procedure Initiated by the UE

11.1.4.2.1 Definition

11.1.4.2.2 Conformance requirement

Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network may reject the UE initiated PDP context activation by sending an ACTIVATE SECONDARY PDP CONTEXT REJECT message to the UE. Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REJECT message, the UE 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.

11.1.4.2.3 Test purpose

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

11.1.4.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

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

Related ICS/IXIT statements

– PS Supported yes/no

– Method of context activation

– Secondary PDP context activation supported yes/no

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 UE, 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 UE sends no more ACTIVATE SECONDARY PDP CONTEXT REQUEST messages.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	UE			Initiate a PDP context activation
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context
3			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context
4	UE			Initiate a secondary PDP context activation
5			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request a Secondary PDP context activation
6			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 request messages come from the UE

Specific message contents

Step 5. The Linked TI information element specifies the TI which is different from the TI in the PDP context activated in steps 1-3.

11.1.4.2.5 Test requirements

After a secondary PDP context activation being rejected by the network, the UE shall not re-send the ACTIVATE SECONDARY PDP CONTEXT REQUEST message.

11.1.4.3 Abnormal cases

11.1.4.3.1 T3380 Expiry

11.1.4.3.1.1 Definition

11.1.4.3.1.2 Conformance requirement

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

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

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

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

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

Reference

3GPP TS 24.008 clause 6.1.3.2.3 a).

11.1.4.3.1.3 Test purpose

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

11.1.4.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 context

– Secondary PDP context activation supported yes/no

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 UE 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 UE.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	UE			Initiate a PDP context activation
2			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context
3			ACTIVATE PDP CONTEXT ACCEPT	Accept the PDP context
4	UE			Initiate a secondary PDP context activation
5			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request a Secondary PDP context activation
6	SS			T3380 seconds
7			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request the Secondary PDP context activation
8	SS			T3380 seconds
9			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request the Secondary PDP context activation
10	SS			T3380 seconds
11			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request the Secondary PDP context activation
12	SS			T3380 seconds
13			ACTIVATE SECONDARY PDP CONTEXT REQUEST	Request the Secondary PDP context activation
14	SS			Wait for T3380 seconds to ensure no further ACTIVATE SECONDARY PDP CONTEXT REQUEST messages are sent by the UE

Specific message contents

None.

11.1.4.3.1.5 Test requirements

UE shall re-send the ACTIVATE SECONDARY PDP CONTEXT REQUEST to SS five times in order to initiate a Secondary PDP context, with expiry of timer T3380 between messages. After fifth try, UE shall send no more ACTIVATE SECONDARY PDP CONTEXT REQUEST messages to SS.

11.1.5 Secondary PDP context activation procedures initiated by network

11.1.5.1 Successful Secondary PDP Context Activation Procedure Initiated by the Network

11.1.5.1.1 Definition

11.1.5.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. If present, the TFT shall be sent transparently through the SGSN to the GGSN to enable packet classification and policing for downlink data transfer.

NOTE 1: If the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107 [81], the network should negotiate the parameter to a value that lies within the specified range.

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 A/Gb mode 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.

In Iu mode, both SGSN and MS shall store the LLC SAPI and the radio priority in the PDP context. If an Iu mode to A/Gb mode Routing Area Update is performed, the new SGSN shall initiate establishment of the logical link using the negotiated LLC SAPI, the negotiated QoS profile and selected radio priority level stored in the PDP context as in an A/Gb mode to A/Gb mode Routing Area Update.

An MS, which is capable of operating in both A/Gb mode and Iu mode, shall use a valid LLC SAPI, while an MS which is capable of operating only in Iu mode shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and any other possible confusion in the network. When the MS uses a valid LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the “LLC SAPI not assigned” value only when the MS uses the “LLC SAPI not assigned” value.

NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in Iu mode, shall be included in the messages, in order to support handover between Iu mode and A/Gb mode networks.

…

In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the network shall send a REQUEST SECONDARY PDP CONTEXT ACTIVATION message to the MS and start timer T3385. The message contains the required QoS, Linked TI, and optionally protocol configuration options and a TFT. If present, the TFT shall be sent transparently through the SGSN to the MS to enable packet classification and policing for uplink and downlink data transfer.

Upon receipt of a REQUEST SECONDARY PDP CONTEXT ACTIVATION message, the MS shall then either initiate the secondary PDP context activation procedure as described in the subclause 6.1.3.2.1 or shall reject the activation request by sending a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message as described in subclause 6.1.3.2.2a. The value of the reject cause IE of the REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message shall indicate the reason for rejection, e.g. "insufficient resources to activate another context".

The ACTIVATE SECONDARY PDP CONTEXT REQUEST message sent by the MS in order to initiate the secondary PDP context activation procedure shall contain the QoS and Linked TI required in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. The MS shall also include a TFT with the downlink packet filters as specified in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message.

Upon receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network shall stop timer T3385.

The same procedures then apply as described for MS initiated secondary PDP context activation.

Reference

3GPP TS 24.008 clauses 6.1.3.2, 6.1.3.2.1, 6.1.3.2.1a and 10.5.6.3.

11.1.5.1.3 Test purpose

To test the behaviour of the UE when it detects a network initiated secondary PDP context activation request on the existing PDP context already activated on the UE side

11.1.5.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

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

Related ICS/IXIT statements

– Method of context activation

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 by sending a REQUEST SECONDARY PDP CONTEXT ACTIVATION. The UE requests activation of the secondary PDP context. 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 UE. The SS then sends a MODIFY PDP CONTEXT REQUEST message to which the UE shall reply with a MODIFY PDP CONTEXT ACCEPT message to ensure the context has been set up.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
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 the primary 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 with the requested QoS
				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			MODIFY PDP CONTEXT REQUEST (NETWORK TO UE DIRECTION)	The SS sends a modify request to UE for secondary PDP context
14			MODIFY PDP CONTEXT ACCEPT (UE TO NETWORK DIRECTION)	The UE accepts the modification request from the SS. This re-confirms that step 9 was correctly executed in the UE.

Specific message contents

Step 4: TI flag (octet 1, Bit 8) in TI IE is set to ‘0’ and value of TIO (octet 1, Bits 765) is set in range 0-6.

Step 6: TI flag in TI IE is set to ‘1’ and value of TIO is the same as in Step 4. 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 Linked TI information element in REQUEST SECONDARY PDP CONTEXT ACTIVATION message specifies the TI for the primary PDP context already activated and is set according to Step 6. The request includes a TFT. The request also includes a bi-directional packet filter. For details please refer 23.060 Sec 9.2.2.3.

– TI flag in TI IE is set to ‘0’ and value of TIO is different to Step 4.

Step 9:

– The Linked TI information element in ACTIVATE SECONDARY PDP CONTEXT REQUEST message specifies the TI for the PDP context already activated, as received in step 8

– TI flag in TI IE is set to ‘1’ and value of TIO is the same as in Step 8

– NSAPI IE value is different from NSAPI value in Step 4

Step 11 and 13: TI flag in TI IE is set to ‘0’ and value of TIO is the same as in Step 9.

Step 14: TI flag in TI IE is set to ‘1’ and value of TIO is the same as in Step 9.

11.1.5.1.5 Test requirements

To pass the test the UE shall:

at step 9 send a ACTIVATE SECONDARY PDP CONTEXT REQUEST message with a NSAPI value different from the value in Step 4.
at step 14 send a MODIFY PDP CONTEXT ACCEPT message.

11.1.5.2 Successful Secondary PDP Context Activation, Deactivation and Re-activation Initiated by the Network

11.1.5.2.1 Definition

11.1.5.2.2 Conformance requirement

NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in Iu mode, shall be included in the messages, in order to support handover between Iu mode and A/Gb mode networks.

…

Upon receipt of the ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network shall stop timer T3385.

The same procedures then apply as described for MS initiated secondary PDP context activation.

…

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.

…

Each valid downlink- and uplink-packet filter contains a unique identifier within a given TFT, an evaluation precedence index that is unique among all packet filters for the same direction (downlink or uplink) for one PDP address and APN pair, and at least one of the following attributes:

– Remote Address and Subnet Mask.

– Protocol Number (IPv4) / Next Header (IPv6).

– Local Port Range.

– Remote Port Range.

– IPSec Security Parameter Index (SPI).

– Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask.

– Flow Label (IPv6).

In the list of attributes above ‘Remote’ refers to the external network entity, and ‘Local’ to the MS.

Some of the above-listed attributes may coexist in a packet filter while others mutually exclude each other. In table 12 below, the possible combinations are shown. Only those attributes marked with an "X" may be specified for a single packet filter. All marked attributes may be specified, but at least one shall be specified.

If the parameters of the header of a received PDP PDU match all specified attribute values in a packet filter, then it is considered that a match is found for this packet filter. In this case, the evaluation procedure is aborted. Other packet filters in increasing order of their evaluation precedence index are evaluated until such match is found.

There may be potential conflicts if attribute values are combined in such a way that the defined filter can never achieve a match to a valid IP packet header. However, the determination of such conflicts is outside the scope of GPRS standardization.

Table 12: Valid Packet Filter Attribute Combinations

	Valid combination types
Packet filter attribute	I	II	III
Remote Address and Subnet Mask	X	X	X
Protocol Number (IPv4) / Next Header (IPv6)	X	X
Local Port Range	X
Remote Port Range	X
IPSec SPI		X
TOS (IPv4) / Traffic Class (IPv6) and Mask	X	X	X
Flow Label (IPv6)			X

Reference

3GPP TS 24.008 clauses 6.1.3.2, 6.1.3.2.1, 6.1.3.2.1a and 6.1.3.4.2. 3GPP TS 23.060 clause 15.3.2.0.

11.1.5.2.3 Test purpose

1. To verify that the UE, after having deactivated a network initiated secondary PDP context successfully, can re-activate a new network requested secondary PDP context associated with the same primary PDP context.

2. To verify that the UE successfully performs data transfer on the radio bearer associated with the secondary PDP context packet filtering before and after the re-activation of the secondary PDP context.

11.1.5.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

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

Related ICS/IXIT statements

– Method of context activation

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 REQUEST 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.

A Secondary PDP context activation is requested by the SS by sending a REQUEST SECONDARY PDP CONTEXT ACTIVATION including Packet Filter#1 in the UL TFT. The UE requests activation of the secondary PDP context. 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 UE.

The SS activates UE test loop mode 4 and transmits two IP Packets to the UE, IP packet#1 and IP packet#2. IP packet#1 does not match Packet Filter#1. IP packet#2 matches Packet Filter#1. The SS checks that IP packet#1 is returned by the UE on the radio bearer associated with the primary PDP context and IP packet#2 is returned by the UE on the radio bearer associated with the secondary PDP context. The SS deactivates UE test loop mode 4.

The SS then requests to deactivate the secondary PDP context by sending DEACTIVATE PDP CONTEXT message to the user. The SS starts the T3395 timer. The UE deactivates the secondary PDP context and issues the DEACTIVATE PDP CONTEXT ACCEPT message. On receipt of this message the SS stops the T3395 timer.

A re-activation of the secondary PDP context is requested by the SS by sending a REQUEST SECONDARY PDP CONTEXT ACTIVATION includes Packet Filter#2 (different from Packet Filter#1) in the UL TFT IE. The UE requests activation of the secondary PDP context. 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 UE.

The SS activates UE test loop mode 4 and transmits two IP Packets to the UE, IP packet#3 and IP packet#4. IP packet#3 matches Packet Filter#1, but do not match Packet Filter#2. IP packet#4 matches Packet Filter#2. The SS checks that IP packet#3 is returned by the UE on the radio bearer associated with the primary PDP context (see Note) and IP packet#4 is returned by the UE on the radio bearer associated with the secondary PDP context. Note IP packet#3 is set to match Packet Filter#1 to verify that UE does not re-activate Packet Filter#1 when the secondary PDP context is reactivated. If Packet Filter#1 would still be active after the deactivation and re-activation of the secondary PDP context then would IP packet#3 have been returned on the radio bearer associated with the secondary PDP context instead of the primary PDP context.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
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	SS
3			SERVICE REQUEST	Service type = "signalling"
3a			Void
4	SS			The SS starts integrity protection.
5			ACTIVATE PDP CONTEXT REQUEST	Activate a PDP context
5A0				The SS activates UE radio bearer test mode in accordance to [10] TS 34.109, clause 5.2.1
5A	SS			IF the UE in step 5 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 5 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 5 set the PDP type to ‘ IPv6′ in the ACTIVATE PDP CONTEXT REQUEST message then the SS sets the test variable IPtype=’IPv6’
6	SS			The SS establishes the RAB according to reference radio bearer combination 6.10.2.4.1.26 in [9] (1xPS RB 64kbps).
7			ACTIVATE PDP CONTEXT ACCEPT	The SS accepts the PDP context.
				EXCEPTION: If the test variable is set to ‘IPv6’ then stateless address auto configuration occurs on the user plane bearer established with the ACTIVATE PDP CONTEXT REQUEST message.
8	SS			The SS initiates a secondary PDP context activation
9			REQUEST SECONDARY PDP CONTEXT ACTIVATION	The SS requests a Secondary PDP context activation and starts timer T3385. A UL TFT filter (Packet Filter#1) is configured.
10			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.
11	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).
12			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	The SS accepts the Secondary PDP context activation with the requested QoS
13	SS			The SS waits for T3380 seconds to ensure no further activate request messages come from the UE
14	SS			The SS activates UE test loop mode 4 to establish UE loopback of IP PDUs. See [10] TS 34.109 clause 5.3.2.
15			IP PDU (IP packet#1)	The SS transmits IP packet#1 to the UE. IP packet#1 does not match Packet Filter#1.
16			IP PDU (IP packet#1)	The SS checks during 1 second that UE transmits IP packet#1 on the radio bearer associated with the primary PDP context.
17			IP PDU (IP packet#2)	The SS transmits IP packet#2 to the UE. IP packet#2 matches Packet Filter#1.
18			IP PDU (IP packet#2)	The SS checks during 1 second that UE transmits IP packet#2 on the radio bearer associated with the secondary PDP context.
19	SS			The SS deactivates UE test loop mode 4. See [10] TS 34.109 clause 5.3.3.
20			DEACTIVATE PDP CONTEXT	The SS starts timer T3395. Cause code set to #36 (regular deactivation)
21			DEACTIVATE PDP CONTEXT ACCEPT	The SS stops timer T3395. The SS reconfigures the RAB.
22	SS			The SS initiates a secondary PDP context activation
23			REQUEST SECONDARY PDP CONTEXT ACTIVATION	The SS requests a Secondary PDP context activation and starts timer T3385. The SS configures Packet Filter#2 in the UL TFT associated with the secondary PDP context.
24			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.
25	SS			The SS stops timer T3385. The SS reconfigures the RAB.
26			ACTIVATE SECONDARY PDP CONTEXT ACCEPT	The SS accepts the Secondary PDP context activation with the requested QoS
27	SS			The SS waits for T3380 seconds to ensure no further activate request messages come from the UE
28	SS			The SS activates UE test loop mode 4 to establish UE loopback of IP PDUs. See [10] TS 34.109 clause 5.3.2.
29			IP PDU (IP packet#3)	The SS transmits IP packet#3 to the UE. IP packet#3 do not match Packet Filter#2, but do match Packet Filter#1.
30			IP PDU (IP packet#3)	The SS checks during 1 second that UE transmits IP packet#3 on the radio bearer associated with the primary PDP context.
31			IP PDU (IP packet#4)	The SS transmits IP packet#4 to the UE. IP packet#4 matches Packet Filter#2.
32			IP PDU (IP packet#4)	The SS checks during 1 second that UE transmits IP packet#4 on the radio bearer associated with the secondary PDP context.

Specific message contents

Step 5: TI flag (octet 1, Bit 8) in TI IE is set to ‘0’ and value of TIO (octet 1, Bits 765) is set in range 0-6.

Step 7: TI flag in TI IE is set to ‘1’ and value of TIO is the same as in Step 5. 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 9:

– The Linked TI information element in REQUEST SECONDARY PDP CONTEXT ACTIVATION message specifies the TI for the PDP context already activated and is set according to Step 7. The request includes a Bi-directional Packet filter, Packet Filter#1.

– TI flag in TI IE is set to ‘0’ and value of TIO is different to Step 5

– Packet Filter#1 is set according to table11.1.5.2.4-1.

Step 10:

– The Linked TI information element in ACTIVATE SECONDARY PDP CONTEXT REQUEST message specifies the TI for the PDP context already activated, as received in step 9

– TI flag in TI IE is set to ‘1’ and value of TIO is the same as in Step 5 and 7

– NSAPI IE value is different from NSAPI value in Step 5

Step 12: TI flag in TI IE is set to ‘0’ and value of TIO is the same as in Step 10.

Step 14: UE test loop mode IE is set to UE test loop mode 4 in the CLOSE UE TEST LOOP message, see [10] TS 34.109 clause 6.2.

Step 15: IP packet#1 is set according to table11.1.5.2.4-2.

Step 17: IP packet#2 is set according to table11.1.5.2.4-3

Step 20:

– TI flag in TI IE is set to ‘0’ and value of TIO is the same as in Step 10

– The Cause Code IE is set to #36 (regular deactivation)

Step 23: The Linked TI information element in ACTIVATE SECONDARY PDP CONTEXT REQUEST message specifies the TI for the PDP context already activated, as received in step 9. The request includes an UL TFT filter, Packet Filter#2.

Packet Filter#2 is set according to table11.1.5.2.4-1.

Step 24:

– The Linked TI information element in ACTIVATE SECONDARY PDP CONTEXT REQUEST message specifies the TI for the PDP context already activated, as received in step 9

– TI flag in TI IE is set to ‘0’ and value of TIO is the same as in Step 5 and 7

– NSAPI IE value is different from NSAPI value in Step 5

Step 28: UE test loop mode IE is set to UE test loop mode 4 in the CLOSE UE TEST LOOP message, see [10] TS 34.109 clause 6.2.

Step 29: IP packet#3 is set according to table11.1.5.2.4-4.

Step 31: IP packet#4 is set according to table11.1.5.2.4-2.

Table 11.1.5.2.4-1: Packet Filter Table

Packet filter ID

UL TFT

Packet filter evaluation precedence

Protocol Number (IPv4) / Next Header (IPv6)

Remote address and Subnet mask

Single Local Port

(UE)

Local Port Range

(UE)

Single Remote Port

(NW)

Remote Port Range

(NW)

IPSec SPI range

Type of Service (IPv4) / Traffic Class (IPv6) and Mask

Flow Label (IPv6)

Comments

Secondary PDP Context (step 9)

17
(UDP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

60001

–

60350:

60450

–

10101000, Mask=
11111100

–

UDP application identified by remote address, type of service/traffic class and specific local port number and remote port number range. This is a valid Packet Filter Attribute Combination Type I according to TS 23.060, subclause 15.3.2.0.

Secondary PDP Context (step23)

17
(UDP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

60001

–

60350:

60450

–

10100000, Mask=
11111100

–

Same as packet filter#1 except for “Type of Service(IPv4) / Traffic Class (IPv6)” packet filter component.

Table 11.1.5.2.4-2: IP packet#1 (step 15, does not match packet filter#1)

Derivation path: IETF RFC 791 section 3.1 (IPv4) or RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10101001	Significant for packet filter 1. Value matches packet filter 1.
Protocol	17	UDP Significant packet filters 1. Value matches packet filter 1.
Source Address	192.168.0.1	Not significant for any packet filters	IPv4
	Fe80::1:1	Not significant for any packet filters	IPv6
Destination Address	172.168.9.1	Significant for packet filter 1. Value does not match packet filter 1.	IPv4
	2001:0bb0:0001:0001	Significant for packet filter 1 Value does not match packet filter 1.	IPv6
Source Port	60001	Significant for packet filter 1. Value matches packet filter 1.
Destination Port	60350	Significant for packet filter 1. Value matches packet filter 1.

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 11.1.5.2.4-3: IP packet#2 (step 17, matches packet filter#1)

Derivation path: IP packet#1, Table 11.1.5.2.4-2.
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10101001	Significant for packet filter 1. Value matches packet filter 1.
Destination Address	172.168.8.1	Significant for packet filter 1. Value matches packet filter 1.	IPv4
	2001:0ba0:0001:0001	Significant for packet filter 1. Value matches packet filter 1.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 11.1.5.2.4-4: IP packet#3 (step 29, does not match packet filter#2, matches removed packet filter#1)

Derivation path: IP packet#1, Table 11.1.5.2.4-2.
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10101001	Significant for packet filter 2. Value does not match packet filter 2.
Destination Address	172.168.8.1	Significant for packet filter 2. Value matches packet filter 2.	IPv4
	2001:0ba0:0001:0001	Significant for packet filter 1. Value matches packet filter 2.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 11.1.5.2.4-5: IP packet#4 (step 31, matches packet filter#2)

Derivation path: IP packet#1, Table 11.1.5.2.4-2.
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10100000	Significant for packet filter 2. Value matches packet filter 2.
Destination Address	172.168.8.1	Significant for packet filter 2. Value matches packet filter 2.	IPv4
	2001:0ba0:0001:0001	Significant for packet filter 2. Value matches packet filter 2.	IPv6

11.1.5.2.5 Test requirements

To pass the test the UE shall:

– at step 16 transmit an IP PDU containing IP packet#1 on the radio bearer associated with the primary PDP context.

– at step 18 transmit an IP PDU containing IP packet#2 on the radio bearer associated with the secondary PDP context.

– at step 30 transmit an IP PDU containing IP packet#3 on the radio bearer associated with the primary PDP context.

– at step 32 transmit an IP PDU containing IP packet#4 on the radio bearer associated with the secondary PDP context.