6 PDP Context Activation
34.229-13GPPInternet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification
6.1 General Purpose PDP Context Establishment
Implicitly tested.
NOTE: This is implicitly tested as part of generic procedures.
6.2 General Purpose PDP Context Establishment (UE Requests for a Dedicated PDP Context)
6.2.1 Definition
Test to verify that the UE can establish a ‘General Purpose PDP context’ for SIP signalling.
6.2.2 Conformance requirement
Prior to communication with the IM CN subsystem, the UE shall:
a) perform a GPRS attach procedure as specified in 3GPP TS 24.008 [8];
b) ensure that a PDP context used for SIP signalling according to the APN and GGSN selection criteria described in 3GPP TS 23.060 [4] and 3GPP TS 27.060 [10A] is available. This PDP context shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration. As a result, the PDP context provides the UE with information that makes the UE able to construct an IPv4 or an IPv6 address;
NOTE 1: During the PDP context activation procedure, the UE and network negotiate whether the UE or the GPRS IP-CAN is responsible for the resource reservation applicable to all PDP contexts within the activated PDP address/APN pair, as described in 3GPP TS 24.008 [8].
When the bearer establishment is controlled by the UE, the UE shall choose one of the following options when performing establishment of this PDP context:
I. ….
II. A general-purpose PDP context:
The UE may decide to use a general-purpose PDP Context to carry IM CN subsystem-related signalling. The UE shall indicate to the GGSN that this is a general-purpose PDP context by not setting the IM CN Subsystem Signalling Flag. The UE may carry both signalling and media on the general-purpose PDP context. The UE can also set the Signalling Indication attribute within the QoS information element.
NOTE 2: When the bearer establishment is controlled by the GPRS IP-CAN, the GGSN follows the procedures described in 3GPP TS 29.061 [11] in order to establish a dedicated PDP context for SIP signalling.
The UE indicates the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options information element of the ACTIVATE PDP CONTEXT REQUEST message or ACTIVATE SECONDARY PDP CONTEXT REQUEST message. Upon successful signalling PDP context establishment the UE receives an indication from GGSN in the form of IM CN Subsystem Signalling Flag within the Protocol Configuration Options information element. If the flag is not received, the UE shall consider the PDP context as a general-purpose PDP context.
The encoding of the IM CN Subsystem Signalling Flag within the Protocol Configuration Options information element is described in 3GPP TS 24.008 [8].
Reference(s)
3GPP TS 24.229 [10], clause B.2.2.1.
6.2.3 Test purpose
To verify that the UE sends a correctly composed Activate PDP context request by setting the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options IE.
On receiving Activate PDP Context accept with IM CN Subsystem Signalling Flag not set within the Protocol Configuration Options IE, UE shall consider the PDP context as a General Purpose PDP context for SIP signalling.
6.2.4 Method of test
Initial conditions
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN. UE is not registered to IMS services, has not established PDP context for IMS
Test procedure
1) UE is configured for setting the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options IE in Activate PDP Context Request message. UE initiates an Activate PDP Context procedure.
2) SS Responds with an Activate PDP Context Accept message by not setting IM CN Subsystem Signalling Flag within the Protocol Configuration Options IE
3) P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4.
4) UE sends an initial REGISTER request.
5) Continue test execution with the Generic test procedure, Annex C.2 or C.2a (GIBA only), step 5.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
🡪 |
Activate PDP Context Request |
UE sends this PDU by setting the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options IE |
|
|
2 |
🡨 |
Activate PDP Context Accept |
SS Sends this response by not setting IM CN Subsystem Signalling Flag within the Protocol Configuration Options IE |
|
|
3 |
P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4. |
|||
|
4 |
🡪 |
REGISTER |
UE sends initial registration for IMS services |
|
|
5 |
🡨🡪 |
Continue with Annex C.2 or C.2a step 5 |
Execute the Generic test procedure Annex C.2 step 5-11 or C.2a (GIBA only) step 5-9 in order to get the UE in a stable registered state |
|
NOTE 1: The default messages contents in annex A are used with condition "IMS security" or "GIBA".
Specific Message Contents:
Activate PDP Context Request (step 1)
|
IE |
Value/Remarks |
|
Protocol Configuration options |
|
|
– Additional Parameters |
(Note 2) |
|
— container 1 Identifier |
0002H (IM CN Subsystem Signalling Flag) |
|
— Container 1 Length |
0 bytes |
NOTE 2: UE may include additional containers also. If multiple containers are present they can be in any order.
Activate PDP Context Accept (step 2)
Case 1: UE supports IPv6 / IPv6 and IPv4
|
IE |
Value/Remarks |
|
Protocol Configuration options |
|
|
– Additional Parameters |
|
|
— container 1 Identifier |
0001H (P-CSCF Address) (Included if ‘P-CSCF Server Address Request’ is received) |
|
— Container 1 Length |
16 bytes |
|
— Container 1 contents |
IPV6 address of SS P-CSCF Server |
|
— container 2 Identifier |
0003H (DNS Address) (Included if ‘DNS Server Address Request’ is received) |
|
— Container 2 Length |
16 bytes |
|
— Container 2 contents |
IPV6 address of SS DNS Server |
Case 2: UE supports only IPv4
|
IE |
Value/Remarks |
|
Protocol Configuration options |
|
|
– Additional Parameters |
|
|
— container 1 Identifier |
0001H (P-CSCF Address) |
|
— Container 1 Length |
16 bytes |
|
— Container 1 contents |
IPV4 address of SS P-CSCF encoded as per 3GPP TR 23.981[35] |
|
— container 2 Identifier |
0003H (DNS Address) (Included if ‘DNS Server Address Request’ is received) |
|
— Container 2 Length |
16 bytes |
|
— Container 2 contents |
IPV4 address of SS DNS server encoded as per 3GPP TR23.981[35] |
REGISTER (Step 4)
Use the default message “REGISTER” in annex A.1.1 with condition A1 "Initial unprotected REGISTER"
6.2.5 Test requirements
1) In step 1, the UE shall set the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options IE.
2) In step 4, the UE shall send an initial REGISTER message using the established PDP context.
6.3 Dedicated PDP Context Establishment
6.3.1 Definition
Test to verify that the UE can establish a ‘Dedicated PDP context’ for SIP signalling.
6.3.2 Conformance requirement
Prior to communication with the IM CN subsystem, the UE shall:
a) perform a GPRS attach procedure as specified in 3GPP TS 24.008 [8];
b) ensure that a PDP context used for SIP signalling according to the APN and GGSN selection criteria described in 3GPP TS 23.060 [4] and 3GPP TS 27.060 [10A] is available. This PDP context shall remain active throughout the period the UE is connected to the IM CN subsystem, i.e. from the initial registration and at least until the deregistration. As a result, the PDP context provides the UE with information that makes the UE able to construct an IPv4 or an IPv6 address;
NOTE 1: During the PDP context activation procedure, the UE and network negotiate whether the UE or the GPRS IP-CAN is responsible for the resource reservation applicable to all PDP contexts within the activated PDP address/APN pair, as described in 3GPP TS 24.008 [8].
When the bearer establishment is controlled by the UE, the UE shall choose one of the following options when performing establishment of this PDP context:
I. A dedicated PDP context for SIP signalling:
The UE shall indicate to the GGSN that this is a PDP context intended to carry IM CN subsystem-related signalling only by setting the IM CN Subsystem Signalling Flag. The UE may also use this PDP context for DNS and DHCP signalling according to the static packet filters as described in 3GPP TS 29.061 [11]. The UE can also set the Signalling Indication attribute within the QoS information element;
II. A general-purpose PDP context:
The UE may decide to use a general-purpose PDP Context to carry IM CN subsystem-related signalling. The UE shall indicate to the GGSN that this is a general-purpose PDP context by not setting the IM CN Subsystem Signalling Flag. The UE may carry both signalling and media on the general-purpose PDP context. The UE can also set the Signalling Indication attribute within the QoS information element.
NOTE 2: When the bearer establishment is controlled by the GPRS IP-CAN, the GGSN follows the procedures described in 3GPP TS 29.061 [11] in order to establish a dedicated PDP context for SIP signalling.
The UE indicates the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options information element of the ACTIVATE PDP CONTEXT REQUEST message or ACTIVATE SECONDARY PDP CONTEXT REQUEST message. Upon successful signalling PDP context establishment the UE receives an indication from GGSN in the form of IM CN Subsystem Signalling Flag within the Protocol Configuration Options information element. If the flag is not received, the UE shall consider the PDP context as a general-purpose PDP context.
The encoding of the IM CN Subsystem Signalling Flag within the Protocol Configuration Options information element is described in 3GPP TS 24.008 [8].
Reference(s)
3GPP TS 24.229 [10], clause B.2.2.1.
6.3.3 Test purpose
To verify that on receiving Activate PDP Context accept with IM CN Subsystem Signalling Flag included within the Protocol Configuration Options IE, UE shall consider the PDP context as a Dedicated PDP context for SIP signalling.
6.3.4 Method of test
Initial conditions
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN. UE is not registered to IMS services, has not established PDP context.
Test procedure
1) UE is configured for setting the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options IE in Activate PDP Context Request message. UE initiates an Activate PDP Context procedure.
2) SS Responds with an Activate PDP Context Accept message by including IM CN Subsystem Signalling Flag within the Protocol Configuration Options IE.
3) P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4.
4) UE sends an initial REGISTER request.
5) Continue test execution with the Generic test procedure, Annex C.2 or C.2a (GIBA only), step 5.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
🡪 |
Activate PDP Context Request |
UE sends this PDU by setting the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options IE |
|
|
2 |
🡨 |
Activate PDP Context Accept |
SS Sends this response by including IM CN Subsystem Signalling Flag within the Protocol Configuration Options IE |
|
|
3 |
P-CSCF address discovery using the DHCP procedure according to Annex C.3 for IPv6 or Annex C.4 for IPv4. |
|||
|
4 |
🡪 |
REGISTER |
UE sends initial registration for IMS services |
|
|
5 |
🡨🡪 |
Continue with Annex C.2 or C.2a step 5 |
Execute the Generic test procedure Annex C.2 step 5-11 or C.2a (GIBA only) step 5-9 in order to get the UE in a stable registered state |
|
NOTE 1: The default messages contents in annex A are used with condition “IMS security“ or “GIBA”.
Specific Message Contents:
Activate PDP Context Request (step 1)
|
IE |
Value/Remarks |
|
Requested NSAPI Protocol Configuration options |
Any value |
|
– Additional Parameters |
(Note 2) |
|
— container 1 Identifier |
0002H (IM CN Subsystem Signalling Flag) |
|
— Container 1 Length |
0 bytes |
NOTE 2: UE may include additional containers also. If multiple containers are present they can be in any order.
Activate PDP Context Accept (step 2)
Case 1: UE supports IPv6 / IPv6 and IPv4
|
IE |
Value/Remarks |
|
Protocol Configuration options |
|
|
– Additional Parameters |
|
|
— container 1 Identifier |
0002H (IM CN Subsystem Signalling Flag) |
|
— Container 1 Length |
0 bytes |
|
— container 2 Identifier |
0001H (P-CSCF Address) (Included if ‘P-CSCF Server Address Request’ is received) |
|
— Container 2 Length |
16 bytes |
|
— Container 2 contents |
IPV6 address of SS P-CSCF Server |
|
— container 3 Identifier |
0003H (DNS Address) (Included if ‘DNS Server Address Request’ is received) |
|
— Container 3 Length |
16 bytes |
|
— Container 3 contents |
IPV6 address of SS DNS Server |
Case 2: UE supports only IPv4
|
IE |
Value/Remarks |
|
Protocol Configuration options |
|
|
– Additional Parameters |
|
|
— container 1 Identifier |
0002H (IM CN Subsystem Signalling Flag) |
|
— Container 1 Length |
0 bytes |
|
— container 2 Identifier |
0001H (P-CSCF Address) |
|
— Container 2 Length |
16 bytes |
|
— Container 2 contents |
IPV4 address of SS P-CSCF encoded as per 3GPP TR 23.981 |
|
— container 3 Identifier |
0003H (DNS Address) (Included if ‘DNS Server Address Request’ is received) |
|
— Container 3 Length |
16 bytes |
|
— Container 3 contents |
IPV4 address of SS DNS server encoded as per 3GPP TR 23.981[35] |
REGISTER (Step 4)
Use the default message “REGISTER” in annex A.1.1 with condition A1 "Initial unprotected REGISTER" and with the following exceptions:
|
Header/param |
Value/remark |
|---|---|
|
Contact |
|
|
feature-param |
Not checked |
6.3.5 Test requirements
1) In step 1, the UE shall set the IM CN Subsystem Signalling Flag to the GGSN within the Protocol Configuration Options IE.
2) In step 4, the UE shall send an initial REGISTER message using the established PDP context.