10.1.6 UE-requested PDU session release
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
10.1.6.1 UE-requested PDU session release / Abnormal / Collision with network-requested PDU session modification procedure
10.1.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.1.6.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.501, clause 6.4.3.2, 6.4.3.3 and 6.4.3.5. Unless otherwise stated these are Rel-15 requirements.
[TS 24.501, clause 6.4.3.2]
In order to initiate the UE-requested PDU session release procedure, the UE shall create a PDU SESSION RELEASE REQUEST message.
The UE may set the 5GSM cause IE of the PDU SESSION RELEASE REQUEST message to indicate the reason for releasing the PDU session.
The 5GSM cause IE typically indicates one of the following 5GSM cause values:
#36 regular deactivation;
#41 Semantic error in the TFT operation;
#42 Syntactical error in the TFT operation;
#44 Semantic errors in packet filter(s);
#45 Syntactical error in packet filter(s).
The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION RELEASE REQUEST message to the allocated PTI value.
The UE shall transport the PDU SESSION RELEASE REQUEST message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3582 (see example in figure 6.4.3.2.1).
[TS 24.501, clause 6.4.3.3]
Upon receipt of a PDU SESSION RELEASE REQUEST message and a PDU session ID, if the SMF accepts the request to release the PDU session, and shall perform the network-requested PDU session release procedure as specified in subclause 6.3.3.
[TS 24.501, clause 6.4.3.5]
The following abnormal cases can be identified:
b) Collision of UE-requested PDU session release procedure and network-requested PDU session modification procedure.
When the UE receives a PDU SESSION MODIFICATION COMMAND message during the UE-requested PDU session release procedure, and the PDU session indicated in PDU SESSION MODIFICATION COMMAND message is the PDU session that the UE had requested to release, the UE shall ignore the PDU SESSION MODIFICATION COMMAND message and proceed with the PDU session release procedure.
10.1.6.1.3 Test description
10.1.6.1.3.1 Pre-test conditions
System Simulator:
– NGC Cell A.
UE:
None.
Preamble:
The UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].
10.1.6.1.3.2 Test procedure sequence
Table 10.1.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 |
The PDU session establishment procedure as specified in TS 38.508-1 [4] subclause 4.5A.2 take place. |
– |
– |
– |
– |
|
3 |
Cause the UE to request release of PDU session established during step 2.(Note 2) |
– |
– |
– |
– |
|
4 |
The UE transmits a PDU SESSION RELEASE REQUEST message. |
–> |
PDU SESSION RELEASE REQUEST |
– |
– |
|
5 |
The SS transmits a PDU SESSION MODIFICATION COMMAND message. |
<– |
PDU SESSION MODIFICATION COMMAND |
– |
– |
|
6 |
Check: Does the UE transmit a PDU SESSION MODIFICATION COMPLETE or PDU SESSION MODIFICATION COMMAND REJECT message in the next 3 seconds? |
– |
– |
1 |
F |
|
7 |
Check: Does the UE perform PDU session release procedure defined in clause 4.9.21 of TS 38.508-1 [4]? |
– |
– |
1 |
P |
|
8 |
Void |
– |
– |
||
|
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. |
|||||
10.1.6.1.3.3 Specific message contents
Table 10.1.6.1.3.3-0: PDU SESSION ESTABLISHMENT ACCEPT (Step 2, Table 10.1.6.1.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Authorized QoS rules |
5GC QoS rule of the Config#1 in Table 4.8.4-1 |
|||
|
Mapped EPS bearer contexts |
||||
|
Mapped EPS bearer context |
||||
|
Mapped EPS QoS parameters |
EPC default bearer context of the Config#1 in Table 4.8.4-1 |
|||
|
DNN |
The same DNN value as sent in the UL NAS TRANSPORT message at (step 2, Table 10.1.6.1.3.2-1; step 2a1, Table 4.5A.2.2.2-2, TS 38.508-1 [4]) |
|||
Table 10.1.6.1.3.3-1: PDU SESSION RELEASE REQUEST (step 4, Table 10.1.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.1.6.1.3.2-1 |
|||
|
PTI |
Any value from 1 to 254 |
|||
Table 10.1.6.1.3.3-2: PDU SESSION MODIFICATION COMMAND (step 5, Table 10.1.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.1.6.1.3.2-1 |
|||
|
PTI |
‘0000 0000’B |
No procedure transaction identity assigned |
||
Table 10.1.6.1.3.3-3: PDU SESSION RELEASE COMMAND (step 7, Table 10.1.6.1.3.2-1; step 1, TS 36.508 [4] Table 4.9.21.2.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-14 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Same ID as the ID UE requested in step 2 in Table 10.1.6.1.3.2-1 |
|||
|
PTI |
The value indicated in PDU SESSION RELEASE REQUEST |
|||
|
5GSM cause |
‘0010 0100’B |
#36 regular deactivation |
||
Table 10.1.6.1.3.3-4: PDU SESSION RELEASE COMPLETE (step 8, Table 10.1.6.1.3.2-1; step 2, TS 36.508 [4] Table 4.9.21.2.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-15 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Same ID as the ID UE requested in step 2 in Table 10.1.6.1.3.2-1 |
|||
|
PTI |
The value indicated in PDU SESSION RELEASE REQUEST |
|||
10.1.6.2 UE-requested PDU session release / Abnormal / Collision with network-requested PDU session release procedure
10.1.6.2.1 Test Purpose (TP)
(1)
with { the UE is in PDU SESSION ACTIVE state and transported the PDU SESSION RELEASE REQUEST message }
ensure that {
when { UE receives a PDU SESSION RELEASE COMMAND message with the PTI IE set to “No procedure transaction identity assigned” indicating a PDU session that UE wants to release }
then { the UE aborts the UE-requested PDU session release procedure and proceeds with the network-requested PDU session release procedure }
}
10.1.6.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.501, clause 6.4.3.2, 6.4.3.3 and 6.4.3.5. Unless otherwise stated these are Rel-15 requirements.
[TS 24.501, clause 6.4.3.2]
In order to initiate the UE-requested PDU session release procedure, the UE shall create a PDU SESSION RELEASE REQUEST message.
The UE may set the 5GSM cause IE of the PDU SESSION RELEASE REQUEST message to indicate the reason for releasing the PDU session.
The 5GSM cause IE typically indicates one of the following 5GSM cause values:
#36 regular deactivation;
#41 Semantic error in the TFT operation;
#42 Syntactical error in the TFT operation;
#44 Semantic errors in packet filter(s);
#45 Syntactical error in packet filter(s).
The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION RELEASE REQUEST message to the allocated PTI value.
The UE shall transport the PDU SESSION RELEASE REQUEST message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3582 (see example in figure 6.4.3.2.1).
[TS 24.501, clause 6.4.3.3]
Upon receipt of a PDU SESSION RELEASE REQUEST message and a PDU session ID, if the SMF accepts the request to release the PDU session, and shall perform the network-requested PDU session release procedure as specified in subclause 6.3.3.
[TS 24.501, clause 6.4.3.5]
The following abnormal cases can be identified:
…
c) Collision of UE-requested PDU session release procedure and network-requested PDU session release procedure.
When the UE receives a PDU SESSION RELEASE COMMAND message with the PTI IE set to "No procedure transaction identity assigned" during the UE-requested PDU session release procedure, and the PDU session indicated in the PDU SESSION RELEASE COMMAND message is the same as the PDU session that the UE requests to release, the UE shall abort the UE-requested PDU session release procedure and proceed with the network-requested PDU session release procedure.
10.1.6.2.3 Test description
10.1.6.2.3.1 Pre-test conditions
System Simulator:
– NGC Cell A.
UE:
None.
Preamble:
– The UE is in state 3N-A on NGC Cell A according to TS 38.508-1 [4].
10.1.6.2.3.2 Test procedure sequence
Table 10.1.6.2.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 |
The PDU session establishment procedure as specified in TS 38.508-1 [4] subclause 4.5A.2 take place. |
– |
– |
– |
– |
|
3 |
Cause the UE to request release of PDU session established during step 2.(Note 2) |
– |
– |
– |
– |
|
4 |
The UE transmits a PDU SESSION RELEASE REQUEST message. |
–> |
PDU SESSION RELEASE REQUEST |
– |
– |
|
5 |
Check: Does the UE perform PDU session release procedure defined in clause 4.9.21 of TS 38.508-1 [4]? |
– |
– |
1 |
P |
|
6 |
Void |
– |
– |
– |
– |
|
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. |
|||||
10.1.6.2.3.3 Specific message contents
Table 10.1.6.2.3.3-0: PDU SESSION ESTABLISHMENT ACCEPT (Step 2, Table 10.1.6.2.3.2-1)
|
Derivation path: TS 38.508-1 [4], Table 4.7.2-2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Authorized QoS rules |
5GC QoS rule of the Config#1 in Table 4.8.4-1 |
|||
|
Mapped EPS bearer contexts |
||||
|
Mapped EPS bearer context |
||||
|
Mapped EPS QoS parameters |
EPC default bearer context of the Config#1 in Table 4.8.4-1 |
|||
|
DNN |
The same DNN value as sent in the UL NAS TRANSPORT message at (step 2, Table 10.1.6.2.3.2-1; step 2a1, Table 4.5A.2.2.2-2, TS 38.508-1 [4]) |
|||
Table 10.1.6.2.3.3-1: PDU SESSION RELEASE REQUEST (step 4, Table 10.1.6.2.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.1.6.2.3.2-1 |
|||
|
PTI |
Any value from 1 to 254 |
|||
Table 10.1.6.2.3.3-2: PDU SESSION RELEASE COMMAND (step 5, Table 10.1.6.2.3.2-1; step 1, TS 36.508 [4] Table 4.9.21.2.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.1.6.2.3.2-1 |
|||
|
PTI |
‘0000 0000’B |
No procedure transaction identity assigned |
||
|
5GSM cause |
‘0010 0100’B |
#36 regular deactivation |
||
Table 10.1.6.2.3.3-3: PDU SESSION RELEASE COMPLETE (step 6, Table 10.1.6.2.3.2-1; step 2, TS 36.508 [4] Table 4.9.21.2.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.1.6.2.3.2-1 |
|||
|
PTI |
‘0000 0000’B |
unassigned |
||