10.3 5GS Non-3GPP Access Session Management
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
10.3.1 PDU session authentication and authorization
10.3.1.1 PDU session authentication and authorization / during the UE-requested PDU session procedure
10.3.1.1.1 Test Purpose (TP)
Same Test Purpose as in clause 10.1.1.1.1
10.3.1.1.2 Conformance requirements
Same conformance requirements as in clause 10.1.1.1.2
10.3.1.1.3 Test description
10.3.1.1.3.1 Pre-test conditions
System Simulator:
WLAN Cell 27
UE:
None.
Preamble:
The UE is in state 1W-A with PDU session Active state according to TS 38.508-1 [4].
10.3.1.1.3.2 Test procedure sequence
Table 10.3.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request connectivity to an additional PDU session. (see Note 1) |
– |
– |
– |
– |
|
2 |
UE transmits establishes a IPSEC SA and NAS signalling connection as per generic procedure in table 4.5A.4.2.2-1 of 38.508-1 [4]”. |
– |
– |
– |
– |
|
3 |
The UE transmits a PDU SESSION ESTABLISHMENT REQUEST message to request an additional PDU session. Note: PDU SESSION ESTABLISHMENT REQUEST is included in UL NAS transport. UL NAS transport message is included in dedicatedNAS-Message of ULInformationTransfer message. DNN information is included in UL NAS transport message. |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
– |
– |
|
4 |
The SS transmits PDU SESSION AUTHENTICATION COMMAND including an EAP-Request message. |
<– |
PDU SESSION AUTHENTICATION COMMAND |
||
|
5 |
Check: Does the UE transmit a PDU SESSION AUTHENTICATION COMPLETE containing EAP-Response message? |
–> |
PDU SESSION AUTHENTICATION COMPLETE |
1 |
P |
|
6 |
The SS transmits PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause #29 including an EAP-Failure message. |
<– |
PDU SESSION ESTABLISHMENT REJECT |
||
|
7 |
The generic procedure for SS-requested IPsec Secure tunnel disconnection, specified in subclause 4.5A.3 of TS 38.508-1 [4], takes place performing disconnection of security association. |
– |
– |
– |
|
|
8 |
Cause the UE to request connectivity to an additional PDU session. (see Note 1) |
– |
– |
– |
– |
|
9 |
UE transmits establishes a IPSEC SA and NAS signalling connection as per generic procedure in table 4.5A.4.2.2-1 of 38.508-1 [4]”. |
– |
– |
– |
– |
|
10 |
The UE transmits a PDU SESSION ESTABLISHMENT REQUEST message to request an additional PDU session. Note: PDU SESSION ESTABLISHMENT REQUEST is included in UL NAS transport. UL NAS transport message is included in dedicatedNAS-Message of ULInformationTransfer message DNN information is included in UL NAS transport message. |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
2 |
P |
|
11 |
The SS transmits PDU SESSION AUTHENTICATION COMMAND including an EAP-Request message. |
<– |
PDU SESSION AUTHENTICATION COMMAND |
||
|
12 |
Check: Does the UE transmit a PDU SESSION AUTHENTICATION COMPLETE containing EAP-Response message? |
–> |
PDU SESSION AUTHENTICATION COMPLETE |
– |
– |
|
13 |
The SS establishes an IPSec child security association according to the IKEv2 specification in RFC 7296 [32] |
– |
– |
– |
|
|
14 |
The SS transmits PDU SESSION ESTABLISHMENT ACCEPT message containing an EAP-Success message. |
<– |
PDU SESSION ESTABLISHMENT ACCEPT |
||
|
15 |
SS Transmits PDU SESSION MODIFICATION COMMAND |
<– |
PDU SESSION MODIFICATION COMMAND |
– |
– |
|
Check: Does the UE transmit a PDU SESSION MODIFICATION COMPLETE? |
–> |
PDU SESSION MODIFICATION COMPLETE |
3 |
P |
|
|
– |
EXCEPTION: Step 16a1 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action. |
– |
– |
– |
– |
|
16a1 |
If initiated by the UE, the generic procedure for IP address allocation in the user plane, specified in subclause 4.5.6, takes place performing IP address allocation in the user plane. |
– |
– |
– |
– |
|
Note 1: The request of connectivity to an additional PDU session may be performed by MMI or AT command +CGACT. |
|||||
10.3.1.1.3.3 Specific message contents
Table 10.3.1.1.3.3-1: Void
Table 10.3.1.1.3.3-2: Void
Table 10.3.1.1.3.3-3: PDU SESSION ESTABLISHMENT REQUEST (step 3 and 10, Table 10.3.1.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
PSI-1 |
UE assigns a particular PSI not yet used between 1 and 15 |
||
|
PTI |
PTI-1 |
UE assigns a particular PTI not yet used between 1 and 254 |
||
Table 10.3.1.1.3.3-4: UL NAS Transport (step 3 and 10, Table 10.3.1.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Payload container type |
‘0001’B |
N1 SM information |
||
|
PDU session ID |
PSI-1 |
|||
|
Request type |
‘001’B |
Initial request |
||
|
S-NSSAI |
Not Present |
|||
|
DNN |
DNN-1 (New DNN name) |
The requested DNN is different from default DNN. |
||
Table 10.3.1.1.3.3-5: PDU SESSION ESTABLISHMENT REJECT (step 6, Table 10.3.1.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
PSI-1 |
|||
|
PTI |
PTI-1 |
|||
|
5GSM cause |
‘00011 101’ |
User authentication or authorization failed |
||
Table 10.3.1.1.3.3-6: PDU SESSION ESTABLISHMENT ACCEPT (step 14, Table 10.3.1.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
PSI-1 |
|||
|
PTI |
PTI-1 |
|||
|
EAP message |
Set according to TS 38.508-1 [4] Table 4.7.3.2-3 |
EAP-Success |
||
|
QoS flow description |
||||
|
QFI |
‘00 0011’B |
QFI 3 |
||
|
Operation code |
‘001’B |
Create new QoS flow description |
||
|
E bit |
‘1’B |
Parameters list is included |
||
|
Number of parameters |
’00 0001’B |
1 parameters |
||
|
5QI |
‘0000 1001’B |
5QI 9 |
||
|
DNN |
DNN-1 |
|||
10.3.2 Network-requested PDU session modification
10.3.2.1 Network-requested PDU session modification /Accepted/Rejected
10.3.2.1.1 Test Purpose (TP)
(1)
with { the UE in PDU SESSION ACTIVE state and 5GMM-CONNECTED mode }
ensure that {
when { the UE receives a PDU SESSION MODIFICATION COMMAND message include the PDU session ID which does not belong to any PDU session in PDU SESSION ACTIVE state in UE }
then { UE sends a PDU SESSION MODIFICATION COMMAND REJECT message and set the 5GSM cause to #43: invalid PDU session identity }
}
(2)
with { the UE in PDU SESSION ACTIVE state and 5GMM-CONNECTED mode }
ensure that {
when { the UE receives a PDU SESSION MODIFICATION COMMAND message include the PDU session ID which belongs to a PDU session in PDU SESSION ACTIVE state in UE }
then { UE sends a PDU SESSION MODIFICATION COMMAND REJECT message and set the 5GSM cause to #43: invalid PDU session identity }
}
10.3.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 6.3.2.2, 6.3.2.4. Unless otherwise stated these are Rel-15 requirements.
[TS 24.501, clause 6.3.2.2]
In order to initiate the network-requested PDU session modification procedure, the SMF shall create a PDU SESSION MODIFICATION COMMAND message.
If the authorized QoS rules of the PDU session is modified, the SMF shall set the authorized QoS rules IE of the PDU SESSION MODIFICATION COMMAND message to the authorized QoS rules of the PDU session. The SMF shall ensure that the number of the packet filters used in the authorized QoS rules of the PDU Session does not exceed the maximum number of packet filters supported by the UE for the PDU session. The SMF may bind service data flows for which the UE has requested traffic segregation to a dedicated QoS flow for the PDU session, if possible. Otherwise the SMF may bind the service data flows to an existing QoS flow. The SMF shall use only one dedicated QoS flow for traffic segregation. If the UE has requested traffic segregation for multiple service data flows with different QoS handling, the SMF shall bind all these service data flows to a single QoS flow. If the SMF allows traffic segregation for service data flows in a QoS rule, then the SMF shall create a new authorized QoS rule for these service data flows and shall delete packet filters corresponding to these service data flows from the other authorized QoS rules.
If the authorized QoS flow descriptions of the PDU session is modified, the SMF shall set the authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message to the authorized QoS flow descriptions of the PDU session.
If SMF creates a new authorized QoS rule for a new QoS flow, then SMF shall include the authorized QoS flow description for that QoS flow in the authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message, if:
a) the newly created authorized QoS rules is for a new GBR QoS flow;
b) the QFI of the new QoS flow is not the same as the 5QI of the QoS flow identified by the QFI; or
c) the new QoS flow can be mapped to an EPS bearer as specified in subclause 4.11.2 of 3GPP TS 23.502 [9].
If the session-AMBR of the PDU session is modified, the SMF shall set the selected Session-AMBR IE of the PDU SESSION MODIFICATION COMMAND message to the session-AMBR of the PDU session.
If interworking with EPS is supported for the PDU session and if the mapped EPS bearer contexts of the PDU session is modified, the SMF shall set the mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message to the mapped EPS bearer contexts of the PDU session. If the association between a QoS flow and the mapped EPS bearer context is changed, the SMF shall set the EPS bearer identity parameter in authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message to the new EPS bearer identity associated with the QoS flow.
If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the PDU SESSION MODIFICATION REQUEST message includes a 5GSM capability IE, the SMF shall:
a) if the RQoS bit is set to:
1) "Reflective QoS supported", consider that the UE supports reflective QoS for this PDU session; or
2) "Reflective QoS not supported", consider that the UE does not support reflective QoS for this PDU session; and;
b) if the MH6-PDU bit is set to:
1) "Multi-homed IPv6 PDU session supported", consider that this PDU session is supported to use multiple IPv6 prefixes; or
2) "Multi-homed IPv6 PDU session not supported", consider that this PDU session is not supported to use multiple IPv6 prefixes.
If the SMF considers that reflective QoS is supported for QoS flows belonging to this PDU session, the SMF may include the RQ timer IE set to an RQ timer value in the PDU SESSION MODIFICATION COMMAND message.
If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the PDU session type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and the PDU SESSION MODIFICATION REQUEST message includes a Maximum number of supported packet filters IE, the SMF shall consider this number as the maximum number of packet filters that can be supported by the UE for this PDU session. Otherwise the SMF considers that the UE supports 16 packet filters for this PDU session.
For a PDN connection established when in S1 mode, upon the first inter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the SMF shall consider that the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink are valid for the lifetime of the PDU session.
For a PDN connection established when in S1 mode, upon the first inter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the SMF determines, based on local policies or configurations in the SMF and the Always-on PDU session requested IE in the PDU SESSION MODIFICATION REQUEST message (if available), that either:
a) the requested PDU session needs to be an always-on PDU session, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session required"; or
b) the requested PDU session shall not be an always-on PDU session and:
i) if the UE included the Always-on PDU session requested IE, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session not allowed"; or
ii) if the UE did not include the Always-on PDU session requested IE, the SMF shall not include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message.
If the value of the RQ timer is set to "deactivated" or has a value of zero, the UE considers that RQoS is not applied for this PDU session and remove the derived QoS rule(s) associated with the PDU session, if any.
If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the SMF shall set the PTI IE of the PDU SESSION MODIFICATION COMMAND message to the PTI of the PDU SESSION MODIFICATION REQUEST message received as part of the UE-requested PDU session modification procedure.
If the network-requested PDU session modification procedure is not triggered by a UE-requested PDU session modification procedure, the SMF shall set the PTI IE of the PDU SESSION MODIFICATION COMMAND message to "No procedure transaction identity assigned".
If the selected SSC mode of the PDU session is "SSC mode 3" and the SMF requests the relocation of SSC mode 3 PDU session anchor with multiple PDU sessions as specified in 3GPP TS 23.502 [9], the SMF shall include 5GSM cause #39 "reactivation requested" , in the PDU SESSION MODIFICATION COMMAND message, and may include the PDU session address lifetime in a PDU session address lifetime PCO parameter in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message.
The SMF shall send the PDU SESSION MODIFICATION COMMAND message, and the SMF shall start timer T3591 (see example in figure 6.3.2.2.1).
NOTE: If the SMF requests the relocation of SSC mode 3 PDU session anchor with multiple PDU sessions as specified in 3GPP TS 23.502 [9], the reallocation requested indication indicating whether the SMF is to be reallocated or the SMF is to be reused is provided to the AMF.
Figure 6.3.2.2.1: Network-requested PDU session modification procedure
[TS 24.501, clause 6.3.2.4]
Upon receipt of a PDU SESSION MODIFICATION COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, if the UE rejects the PDU SESSION MODIFICATION COMMAND message, the UE shall create a PDU SESSION MODIFICATION COMMAND REJECT message.
If the PDU SESSION MODIFICATION COMMAND message contains the PTI value allocated in the UE-requested PDU session modification procedure, the UE shall release the PTI indicated by the PTI IE and shall stop the timer T3581.
The UE shall set the 5GSM cause IE of the PDU SESSION MODIFICATION COMMAND REJECT message to indicate the reason for rejecting the PDU session modification.
The 5GSM cause IE typically indicates one of the following 5GSM cause values:
#26 insufficient resources;
#43 invalid PDU session identity;
#44 semantic error in packet filter(s);
#45 syntactical error in packet filter(s);
#83 semantic error in the QoS operation; or
#84 syntactical error in the QoS operation.
10.3.2.1.3 Test description
10.3.2.1.3.1 Pre-test conditions
System Simulator:
WLAN Cell 27
UE:
None.
Preamble:
The UE is in state 3W-A on WLAN Cell 27 with PDU session Active state according to TS 38.508-1 [4].
10.3.2.1.3.2 Test procedure sequence
Table 10.3.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits a PDU session modification command message with PDU session ID IE is set to a different value from the value set in PDU SESSION ESTABLISHMENT REQUEST message. This message is included in a DLInformationTransfer message. |
<– |
PDU SESSION MODIFICATION COMMAND |
– |
– |
|
2 |
Check: Does the UE transmit a PDU session modification reject with the 5GSM cause IE indicating #43 " invalid PDU session identity"? |
–> |
PDU SESSION MODIFICATION REJECT |
1 |
P |
|
3 |
The SS transmits a PDU session modification command message with PDU session ID IE is the value set in PDU SESSION ESTABLISHMENT REQUEST message. This message is included in a DLInformationTransfer message. |
<– |
PDU SESSION MODIFICATION COMMAND |
– |
– |
|
4 |
Check: Does the UE transmit a PDU session modification complete? |
–> |
PDU SESSION MODIFICATION COMPLETE |
2 |
P |
10.3.2.1.3.3 Specific message contents
Table 10.3.2.1.3.3-1: PDU SESSION MODIFICATION COMMAND (Step 1, Table 10.3.2.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], table 4.7.2-9 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
PDU session ID |
The different value from the value set in PDU SESSION ESTABLISHMENT REQUEST message in preamble |
||
Table 10.3.2.1.3.3-2: PDU SESSION MODIFICATION REJECT (Step 2, Table 10.3.2.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], table 4.7.2-8 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
PDU session ID |
The same value as the value set in PDU SESSION modification command message |
||
|
5GSM cause |
‘00101011’B |
Invalid PDU session identity |
|
Table 10.3.2.1.3.3-1: PDU SESSION MODIFICATION COMMAND (Step 3, Table 10.3.2.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], table 4.7.2-9 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
PDU session ID |
The value set in PDU SESSION ESTABLISHMENT REQUEST message in preamble |
||
|
Authorized QoS rules |
Reference QoS rule #3 as defined in 38.508-1 [4]Table 4.8.2.1-1. |
||
10.3.3 Network-requested PDU session Release
10.3.3.1 Network-requested PDU session release / accepted/ with and without reactivation
10.3.3.1.1 Test Purpose (TP)
(1)
with { the UE in PDU SESSION ACTIVE state }
ensure that {
when { the UE receives a PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested"}
then { the UE re-initiates a PDU SESSION establishment procedure for the same [S-NSSAI, DNN] combination provided in PDU session establishment procedure }
}
(2)
with { UE is in PDU SESSION ACTIVE state }
ensure that {
when { UE receives a PDU SESSION RELEASE COMMAND message including 5GSM cause #26 "insufficient resources" and the Back-off timer value that indicates deactivated }
then { UE does not send a PDU SESSION ESTABLISHMENT REQUEST message until the UE is switched off or the USIM is removed }
}
10.3.3.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.501, clauses 6.3.3.2, 6.3.3.3. Unless otherwise stated these are Rel-15 requirements.
[TS 24.501, clause 6.3.3.2]
In order to initiate the network-requested PDU session release procedure, the SMF shall create a PDU SESSION RELEASE COMMAND message.
The SMF shall set the SM cause IE of the PDU SESSION RELEASE COMMAND message to indicate the reason for releasing the PDU session.
The SM cause IE typically indicates one of the following SM cause values:
#26 insufficient resources;
…
The SMF may include a Back-off timer value IE in the PDU SESSION RELEASE COMMAND message when the 5GSM cause value #26 "insufficient resources" is included in the PDU SESSION RELEASE COMMAND message. If the 5GSM cause value is #26 "insufficient resources" and the PDU SESSION RELEASE COMMAND message is sent to a UE configured for high priority access in selected PLMN or the request type was set to "initial emergency request" or "existing emergency PDU session" for the establishment of the PDU session, the network shall not include a Back-off timer value IE.
The SMF may include a Back-off timer value IE in the PDU SESSION RELEASE COMMAND message when the 5GSM cause value #67 "insufficient resources for specific slice and DNN" is included in the PDU SESSION RELEASE COMMAND message. If the 5GSM cause value is #67 "insufficient resources for specific slice and DNN" and the PDU SESSION RELEASE COMMAND message is sent to a UE configured for high priority access in selected PLMN or the request type was set to "initial emergency request" or "existing emergency PDU session" for the establishment of the PDU session, the network shall not include a Back-off timer value IE.
[TS 24.501, clause 6.3.3.3]
Upon receipt of a PDU SESSION RELEASE COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE considers the PDU session as released and the UE shall create a PDU SESSION RELEASE COMPLETE message.
If the PDU SESSION RELEASE COMMAND message contains the PTI value allocated in the UE-requested PDU session release procedure, the UE shall stop the timer T3582. The UE should ensure that the PTI value assigned to this procedure is not released immediately.
NOTE 1: The way to achieve this is implementation dependent. For example, the UE can ensure that the PTI value assigned to this procedure is not released during the time equal to or greater than the default value of timer T3592.
While the PTI value is not released, the UE regards any received PDU SESSION RELEASE COMMAND message with the same PTI value as a network retransmission (see subclause 7.3.1).
If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested", then after completion of the network-requested PDU session release procedure, the UE should re-initiate the UE-requested PDU session establishment procedure as specified in subclause 6.4.1 for:
a) the PDU session type associated with the released PDU session;
b) the SSC mode associated with the released PDU session;
c) the DNN associated with the released PDU session; and
d) the S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI if provided in the UE-requested PDU session establishment procedure of the released PDU session.
If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested" and the UE provided an S-NSSAI during the PDU session establishment, the UE shall stop timer T3585 if it is running for the S-NSSAI provided by the UE. The UE should then re-initiate the UE requested PDU session establishment procedure for the same S-NSSAI. If the UE did not provide an S-NSSAI during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3585 associated with no S-NSSAI if it is running, and should re-initiate the UE requested PDU session establishment procedure without including an S-NSSAI. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3585 associated with no S-NSSAI if it is running.
If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested" and the UE provided a DNN during the PDU session establishment, the UE shall stop timer T3396 if it is running for the DNN provided by the UE. The UE should then re-initiate the UE requested PDU session establishment procedure for the same DNN. If the UE did not provide a DNN during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3396 associated with no DNN if it is running, and should re-initiate the UE requested PDU session establishment procedure without including a DNN. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3396 associated with no DNN if it is running.
If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested" and the UE provided an S-NSSAI and a DNN during the PDU session establishment, the UE shall stop timer T3584 if it is running for the same [S-NSSAI, DNN] combination provided by the UE. The UE should then re-initiate the UE requested PDU session establishment procedure for the same [S-NSSAI, DNN] combination. If the UE did not provide an S-NSSAI during the PDU session establishment, the UE shall stop the timer T3584 associated with [no S-NSSAI, DNN] if it is running, and should re-initiate the UE requested PDU session establishment procedure with the same DNN but without an S-NSSAI. If the UE did not provide a DNN during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3584 associated with [S-NSSAI, no DNN] if it is running, and should re-initiate the UE requested PDU session establishment procedure with the same S-NSSAI but without a DNN. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3584 associated with [S-NSSAI, no DNN] if it is running. If the UE provided neither a DNN nor an S-NSSAI during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3584 associated with [no S-NSSAI, no DNN] if it is running, and should re-initiate the UE requested PDU session establishment procedure without an S-NSSAI and a DNN. If the PDU SESSION RELEASE COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3584 associated with [no S-NSSAI, no DNN] if it is running.
NOTE 2: User interaction is necessary in some cases when the UE cannot re-initiate the UE-requested PDU session establishment procedure automatically.
NOTE 3: If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested" for a PDU session, the UE provided a DNN (or no DNN) and an S-NSSAI (or no S-NSSAI) when the PDU session is established, timer T3396 associated with the DNN (or no DNN, if no DNN was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3396 and the timer T3584.
NOTE 4: If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #39 "reactivation requested" for a PDU session, the UE provided a DNN (or no DNN) and an S-NSSAI (or no S-NSSAI) when the PDU session is established, timer T3585 associated with the S-NSSAI (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3585 and the timer T3584.
10.3.3.1.3 Test description
10.3.3.1.3.1 Pre-test conditions
System Simulator:
– WLAN Cell 27
UE:
– None.
Preamble:
– The UE is in state 3W-A on WLAN Cell 27 according to TS 38.508-1 [4].
10.3.3.1.3.2 Test procedure sequence
Table 10.3.3.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits a PDU SESSION RELEASE COMMAND including 5GSM cause #39 “reactivation requested " with PDU session ID IE is set to the same value in PDU SESSION ESTABLISHMENT REQUEST message in preamble. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMMAND |
– |
– |
|
2 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST and the S-NSSAI and DNN in UL NAS TRANSPORT message are the same values in UL NAS TRANSPORT message in preamble? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
1 |
P |
|
3 |
The SS transmits an PDU SESSION ESTABLISHMENT ACCEPT |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
||
|
4 |
The SS transmits a PDU SESSION RELEASE COMMAND including 5GSM cause #26 “insufficient resources" and T3396 value (deactivated). |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMMAND |
– |
– |
|
5 |
The UE transmits a PDU SESSION RELEASE COMPLETE message. |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMPLETE |
– |
– |
|
6 |
Cause the UE to request establishment of PDU session without DNN.(Note 1) |
– |
– |
– |
– |
|
7 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
2 |
F |
|
8 |
Switch off procedure in Ipsec_SA_Established specified in TS 38.508-1 [4] subclause 4.9.6.5 is performed. |
– |
|||
|
9 |
Switch on UE. |
– |
|||
|
10 |
The general procedure is completed by executing of the UE registration procedure in TS 38.508-1 [4] table 4.5.2.2-3 , ‘connected without release‘. |
– |
|||
|
11 |
Cause the UE to request establishment of PDU session without DNN.(Note 1) |
– |
– |
– |
– |
|
12 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
3 |
P |
|
13 |
The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
|
Note 1: The request to establish a PDU session may be performed by MMI or AT command. |
|||||
10.3.3.1.3.3 Specific message contents
Table 10.3.3.1.3.3-1: PDU SESSION RELEASE COMMAND (Step 1, Table 10.3.3.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], table 4.7.2-14 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
PDU session ID |
The same value indicated in PDU SESSION ESTABLISHMENT REQUEST message in preamble |
||
|
5GSM cause |
‘00100111’B |
Reactivation requested |
|
Table 10.3.3.1.3.3-2: UL NAS TRANSPORT (Step 2, Table 10.3.3.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], table 4.7.1-10 |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
S-NSSAI |
The same value indicated in UL NAS TRANSPORT message in preamble |
If present in UL NAS TRANSPORT message in preamble |
|
|
Not present |
If not present in UL NAS TRANSPORT message in preamble |
||
|
DNN |
The same value indicated in UL NAS TRANSPORT message in preamble |
If present in UL NAS TRANSPORT message in preamble |
|
|
Not present |
If not present in UL NAS TRANSPORT message in preamble |
||
Table 10.3.3.1.3.3-3: PDU SESSION RELEASE COMMAND (step 4, Table 10.3.3.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-14 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
The same ID as the ID of PDU session which UE request in step 13 in Table 10.1.3.2.3.2-1 |
|||
|
5GSM cause |
‘0001 1010’B |
insufficient resources |
||
|
Back-off timer value |
‘1110 0000’B |
deactivated |
||
10.3.4 UE-requested PDU session establishment
10.3.4.1 UE-requested PDU session establishment / Abnormal / T3580
10.3.4.1.1 Test Purpose (TP)
Same test purpose as in clause 10.1.4.2.1
10.3.4.1.2 Conformance requirements
Same conformance requirements as in clause 10.1.4.2.2
10.3.4.1.3 Test description
10.3.4.1.3.1 Pre-test conditions
System Simulator:
– WLAN Cell 27
UE:
– None.
Preamble:
– The UE is in state Switched OFF [State 0-A as per TS 38.508-1 [4] Table 4.4A.2-0].
10.3.4.1.3.2 Test procedure sequence
Table 10.3.4.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
UE is switched on |
– |
– |
– |
– |
|
2-10 |
Steps 1-9 of Table 4.5.2.2-3 of the generic procedure in TS 38.508-1 [4] are performed. |
– |
– |
– |
– |
|
11 |
The UE transmits a PDU SESSION ESTABLISHMENT REQUEST message to request an additional PDU session. |
–> |
PDU SESSION ESTABLISHMENT REQUEST |
– |
– |
|
– |
EXCEPTION: Steps 12-13 shall be repeated for 4 times |
– |
– |
– |
– |
|
12 |
The SS waits 16 seconds (T3580). |
– |
– |
– |
– |
|
13 |
The UE transmits a PDU SESSION ESTABLISHMENT REQUEST message to request an additional PDU session. (Attempt counter = 5) |
–> |
PDU SESSION ESTABLISHMENT REQUEST |
1 |
P |
|
15 |
The UE transmits a PDU SESSION ESTABLISHMENT REQUEST message to request an additional PDU session. |
–> |
PDU SESSION ESTABLISHMENT REQUEST |
2 |
F |
10.3.4.1.3.3 Specific message contents
None.
10.3.5 UE-requested PDU session modification
10.3.5.1 UE-requested PDU session modification/Success
10.3.5.1.1 Test Purpose (TP)
(1)
with { UE in PDU SESSION ACTIVE state and in 5GMM-CONNECTED mode }
ensure that {
when { UE is requested to modify of PDU session }
then { UE sends a PDU SESSION MODIFICATION REQUEST message }
}
10.3.5.1.2 Conformance requirements
Same conformance requirements as in clause 10.1.5.1.2
10.3.5.1.3 Test description
10.3.5.1.3.1 Pre-test conditions
System Simulator:
– WLAN Cell 27.
UE:
– None.
Preamble:
– The UE is in state 3W-A onWLAN Cell 27 with PDU SESSION ACTIVE according to TS 38.508-1 [4].
10.3.5.1.3.2 Test procedure sequence
Same test procedure sequence as in clause 10.1.5.1.3.2
10.3.5.1.3.3 Specific message contents
Same specific message contents as in clause 10.1.5.1.3.3
10.3.6 UE-requested PDU session release
10.3.6.1 UE-requested PDU session release / Abnormal / Collision with network-requested PDU session modification procedure
10.3.6.1.1 Test Purpose (TP)
(1)
with { the UE is in PDU SESSION ACTIVE state and has sent a PDU SESSION RELEASE REQUEST message }
ensure that {
when { UE receives a PDU SESSION MODIFICATION COMMAND message indicating a PDU session that UE wants to release }
then { the UE ignores the PDU SESSION MODIFICATION COMMAND message and proceed with the PDU session release procedure }
}
10.3.6.1.2 Conformance requirements
Same conformance requirements as in clause 10.1.6.1.2
10.3.6.1.3 Test description
10.3.6.1.3.1 Pre-test conditions
System Simulator:
– WLAN Cell 27.
UE:
None.
Preamble:
– The UE is in state 3W-A on WLAN Cell 27 according to TS 38.508-1 [4].
10.3.6.1.3.2 Test procedure sequence
Table 10.3.6.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request establishment of PDU session to the DN.(Note 1) |
– |
– |
– |
– |
|
2 |
New PDU session establishment procedure is performed as per generic procedure in clause 4.5A.2A of TS 38.508-1 [4] |
– |
– |
– |
– |
|
3 |
Cause the UE to request release of PDU session established during preamble.(Note 2) |
– |
– |
– |
– |
|
4 |
The UE transmits a PDU SESSION RELEASE REQUEST message. |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION RELEASE REQUEST |
– |
– |
|
5 |
The SS transmits a PDU SESSION MODIFICATION COMMAND message. |
<– |
5GMM: DL NAS TRANSPROT 5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
|
6 |
The SS transmits a PDU SESSION RELEASE COMMAND message. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMMAND |
– |
– |
|
7 |
Check: Does the UE transmit PDU SESSION RELEASE COMPLETE message? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMPLETE |
1 |
P |
|
8 |
The SS deletes the payload associated with IPSec child security association according to the IKEv2 specification in RFC 7296 [32] |
– |
– |
– |
– |
|
Note 1: The request to establish a PDU session may be performed by MMI or AT command. Note 2: The request to release a PDU session may be performed by MMI or AT command. |
|||||
10.3.6.1.3.3 Specific message contents
Table 10.3.6.1.3.3-1: PDU SESSION RELEASE REQUEST (step 4, Table 10.3.6.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-12 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Set to the ID UE requested in step 2 in Table 10.3.6.1.3.2-1 |
|||
|
PTI |
Any value from 1 to 254 |
|||
Table 10.3.6.1.3.3-2: PDU SESSION MODIFICATION COMMAND (step 5, Table 10.3.6.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-9 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Set to the ID UE requested in step 2 in Table 10.3.6.1.3.2-1 |
|||
|
PTI |
‘0000 0000’B |
No procedure transaction identity assigned |
||
Table 10.3.6.1.3.3-3: PDU SESSION RELEASE COMMAND (step 6, Table 10.3.6.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-14 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Set to the ID UE requested in step 2 in Table 10.3.6.1.3.2-1 |
|||
|
PTI |
The value indicated in PDU SESSION RELEASE REQUEST |
|||
|
5GSM cause |
‘0010 0100’B |
#36 regular deactivation |
||
Table 10.3.6.1.3.3-4: PDU SESSION RELEASE COMPLETE (step 7, Table 10.3.6.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-15 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Set to the ID UE requested in step 2 in Table 10.3.6.1.3.2-1 |
|||
|
PTI |
The value indicated in PDU SESSION RELEASE REQUEST |
|||