10.1.3 Network-requested PDU session release
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
10.1.3.1 Void
10.1.3.2 Network-requested PDU session release / Insufficient resources, insufficient resources for specific slice and DNN, abnormal / Invalid PDU session identity
10.1.3.2.1 Test Purpose (TP)
(1)
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 neither zero nor deactivated }
then { UE does not send a PDU SESSION ESTABLISHMENT REQUEST until timer T3396 expires or timer T3396 is stopped }
}
(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 zero }
then { UE sends a PDU SESSION ESTABLISHMENT REQUEST message }
}
(3)
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 }
}
(4)
with { UE is in PDU SESSION ACTIVE state }
ensure that {
when { UE receives a PDU SESSION RELEASE COMMAND message including 5GSM cause #67 "insufficient resources for specific slice and DNN" and the Back-off timer value that indicates neither zero nor deactivated }
then { UE does not send a PDU SESSION ESTABLISHMENT REQUEST message for the same [S-NSSAI, DNN] combination until timer T3584 expires }
}
(5)
with { UE is in PDU SESSION ACTIVE state }
ensure that {
when { UE receives a PDU SESSION RELEASE COMMAND message including 5GSM cause #67 "insufficient resources for specific slice and DNN" and the Back-off timer value that indicates zero }
then { UE sends a PDU SESSION ESTABLISHMENT REQUEST message for the same [S-NSSAI, DNN] combination }
}
(6)
with { UE is in PDU SESSION ACTIVE state }
ensure that {
when { UE receives a PDU SESSION RELEASE COMMAND message including 5GSM cause #67 "insufficient resources for specific slice and DNN" and the Back-off timer value that indicates deactivated }
then { UE does not send a PDU SESSION ESTABLISHMENT REQUEST message for the same [S-NSSAI, DNN] combination until the UE is switched off or the USIM is removed }
}
(7)
with { UE is in PDU SESSION ACTIVE state }
ensure that {
when { UE receives a PDU SESSION RELEASE COMMAND message, in which the PDU session ID belongs to any PDU session in state PDU SESSION INACTIVE in the UE }
then { UE sends 5GSM STATUS message including 5GSM cause #43 "Invalid PDU session identity" }
}
10.1.3.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 24.501, clause 6.3.3.2 and 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;
…
#67 insufficient resources for specific slice and DNN;
…
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 includes 5GSM cause #26 "insufficient resources" and the Back-off timer value IE, the UE shall take different actions depending on the timer value received for timer T3396 in the Back-off timer value:
a) If the timer value indicates neither zero nor deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates neither zero nor deactivated and no DNN was provided 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 timer T3396 associated with no DNN if it is running. The UE shall then start timer T3396 with the value provided in the Back-off timer value IE and:
1) shall not send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN that was sent by the UE, until timer T3396 expires or timer T3396 is stopped; and
2) shall not send a PDU SESSION ESTABLISHMENT REQUEST message without an DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until timer T3396 expires or timer T3396 is stopped.
The UE shall not stop timer T3396 upon a PLMN change or inter-system change;
b) if the timer value indicates that this timer is deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates that this timer is deactivated and no DNN was provided 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 timer T3396 associated with no DNN if it is running. The UE:
1) shall not send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN until the UE is switched off or the USIM is removed, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the same DNN from the network or a PDU SESSION RELEASE COMMAND message including 5GSM cause #39 "reactivation requested" for the same DNN from the network; and
2) shall not send a PDU SESSION ESTABLISHMENT REQUEST message without an DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until the UE is switched off or the USIM is removed, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without an DNN provided by the UE, or a PDU SESSION RELEASE COMMAND message including 5GSM cause IE set to 5GSM cause #39 "reactivation requested" for a non-emergency PDU session established without an DNN provided by the UE.
The timer T3396 remains deactivated upon a PLMN change or inter-system change; and
c) if the timer value indicates zero, the UE:
1) shall stop timer T3396 associated with the corresponding DNN, if running, and may send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN; and
2) if no DNN was provided 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 timer T3396 associated with no DNN, if running, and may send a PDU SESSION ESTABLISHMENT REQUEST message without a DNN, or a PDU SESSION MODIFICATION REQUEST message without an DNN provided by the UE.
If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #26 "insufficient resources" and the Back-off timer value IE is not included, then the UE may send a PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN or without a DNN.
When the timer T3396 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services.
If the timer T3396 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then timer T3396 is kept running until it expires or it is stopped.
If the UE is switched off when the timer T3396 is running, and if the USIM in the UE remains the same when the UE is switched on, the UE shall behave as follows:
– let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1.
If the 5GSM cause value is #67 "insufficient resources for specific slice and DNN" and the Back-off timer value IE is included, the UE shall take different actions depending on the timer value received for timer T3584 in the Back-off timer value:
a) If the timer value indicates neither zero nor deactivated, the UE shall stop timer T3584 associated with the same [S-NSSAI, DNN] combination as that the UE provided when the PDU session is established, if it is running. The UE shall then start timer T3584 with the value provided in the Back-off timer value IE.
The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [S-NSSAI, DNN] combination that was sent by the UE, until timer T3584 expires or timer T3584 is stopped;
The UE shall not stop timer T3584 upon a PLMN change or inter-system change;
b) if the timer value indicates that this timer is deactivated, the UE shall stop timer T3584 associated with the same [S-NSSAI, DNN] combination as that the UE provided when the PDU session is established, if it is running.
The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [S-NSSAI, DNN] combination that was sent by the UE, until the UE is switched off or the USIM is removed, or the UE receives a PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination from the network or a PDU SESSION RELEASE COMMAND message including 5GSM cause #39 "reactivation requested" for the same [S-NSSAI, DNN] combination from the network; and
The timer T3584 remains deactivated upon a PLMN change or inter-system change; and
c) if the timer value indicates zero, the UE shall stop timer T3584 associated with the same [S-NSSAI, DNN] combination that was sent by the UE, if running, and may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination.
If the 5GSM cause value is #67 "insufficient resources for specific slice and DNN" and the Back-off timer value IE is not included, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination.
When the timer T3584 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services.
If the timer T3584 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then timer T3584 is kept running until it expires or it is stopped.
If the UE is switched off when the timer T3584 is running, and if the USIM in the UE remains the same when the UE is switched on, the UE shall behave as follows:
– let t1 be the time remaining for T3584 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1.
[TS 24.501, clause 6.3.3.6]
The following abnormal cases can be identified:
a) PDU session inactive for the received PDU session ID.
If the PDU session ID in the PDU SESSION RELEASE COMMAND message belongs to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall include the 5GSM cause #43 "Invalid PDU session identity" in the 5GSM STATUS message, and set the PDU session ID to the received PDU session ID in the UL NAS TRANSPORT message as specified in subclause 5.4.5.
[TS 24.501, clause B.1]
Cause #43 –Invalid PDU session identity
This 5GSM cause is used by the network or the UE to indicate that the PDU session identity value provided to it is not a valid value or the PDU session identified by the PDU session identity IE in the request or the command is not active.
[24.501, clause 7.3.2]
…
The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PDU session identity received in the header of a 5GSM message:
a) If the UE receives a 5GSM message which includes an unassigned or reserved PDU session identity value, the UE shall ignore the message.
b) If the UE receives a 5GSM message which includes a PDU session identity belonging to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall respond with a 5GSM STATUS message including 5GSM cause #43 "invalid PDU session identity".
10.1.3.2.3 Test description
10.1.3.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.3.2.3.2 Test procedure sequence
Table 10.1.3.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 without DNN.(Note 1) |
– |
– |
– |
– |
|
|
2 |
The PDU session establishment procedure as specified in TS 38.508-1 [4] subclause 4.5A.2 take place. |
– |
– |
– |
– |
|
|
3 |
The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed. |
– |
– |
– |
– |
|
|
4 |
Void |
– |
– |
– |
– |
|
|
5 |
Cause the UE to request establishment of PDU session without DNN within 2 minutes of Step 3 (Note 1) |
– |
– |
– |
– |
|
|
6 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message before timer T3396 has expired? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
1 |
F |
|
|
7 |
Cause the UE to request establishment of PDU session without DNN after 2 minutes since Step 3.(Note 1) |
– |
– |
– |
– |
|
|
8 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
1 |
P |
|
|
9 |
The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
|
|
10 |
The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed |
– |
– |
– |
– |
|
|
11 |
Void |
– |
– |
– |
– |
|
|
12 |
Cause the UE to request establishment of PDU session without DNN.(Note 1) |
– |
– |
– |
– |
|
|
13 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
2 |
P |
|
|
14 |
The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
|
|
15 |
The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed |
– |
– |
– |
– |
|
|
16 |
Void |
– |
– |
– |
– |
|
|
17 |
Cause the UE to request establishment of PDU session without DNN.(Note 1) |
– |
– |
– |
– |
|
|
18 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message in 5 seconds? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
3 |
F |
|
|
19 |
Switch off UE in RRC CONNECTED as described in TS38.508-1 [4] subclause 4.9.6.3 |
– |
||||
|
20 |
Switch on UE. |
– |
||||
|
21 |
The general procedure is completed by executing of the UE registration procedure in TS 38.508-1 [4] table 4.5.2.2-2 , ‘connected without release‘. |
– |
||||
|
22 |
Cause the UE to request establishment of PDU session without DNN.(Note 1) |
– |
– |
– |
– |
|
|
23 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST message? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
3 |
P |
|
|
24 |
The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
|
|
25 |
Cause the UE to request establishment of PDU session with [S-NSSAI, DNN] combination.(Note 1) |
– |
– |
– |
– |
|
|
26 |
The PDU session establishment procedure as specified in TS 38.508-1 [4] subclause 4.5A.2 take place. |
– |
– |
– |
– |
|
|
27 |
The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed |
– |
– |
– |
– |
|
|
28 |
Void |
– |
– |
– |
– |
|
|
29 |
Cause the UE to request establishment of PDU session with the same [S-NSSAI, DNN] combination as the PDU session established at step 26 within 2 minutes of Step 27.(Note 1) |
– |
– |
– |
– |
|
|
30 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST before timer T3584 has expired? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
4 |
F |
|
|
31 |
Cause the UE to request establishment of PDU session with the same [S-NSSAI, DNN] combination as the PDU session established at step 26 after 2 minutes since Step 27.(Note 1) |
– |
– |
– |
– |
|
|
32 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
4 |
P |
|
|
33 |
The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
|
|
34 |
The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed |
– |
– |
– |
– |
|
|
35 |
Void |
– |
– |
– |
– |
|
|
36 |
Cause the UE to request establishment of PDU session with the same [S-NSSAI, DNN] combination as the PDU session established at step 26.(Note 1) |
– |
– |
– |
– |
|
|
37 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
5 |
P |
|
|
38 |
The SS transmits a PDU SESSION ESTABLISHMENT ACCEPT message. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
|
|
39 |
The generic test procedure in TS 38.508-1 Table 4.9.21.2.2-1 of Procedure for PDU Session Release is performed |
– |
– |
– |
– |
|
|
40 |
Void |
– |
– |
– |
– |
|
|
41 |
Cause the UE to request establishment of PDU session with the same [S-NSSAI, DNN] combination as the PDU session established at step 26.(Note 1) |
– |
– |
– |
– |
|
|
42 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST in 5 seconds? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
6 |
F |
|
|
43 |
The SS transmits a PDU SESSION RELEASE COMMAND including the PDU session ID UE requested in step 42. |
<– |
5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION RELEASE COMMAND |
– |
– |
|
|
44 |
Check: Does the UE transmit a 5GSM STATUS message with value #43? |
–> |
5GSM: UL NAS TRANSPORT 5GSM: 5GSM STATUS |
7 |
P |
|
|
45 |
Switch off UE in RRC CONNECTED as described in TS38.508-1 [4] subclause 4.9.6.3 |
– |
– |
– |
– |
|
|
46 |
Switch on UE. |
– |
– |
– |
– |
|
|
47 |
The general procedure is completed by executing of the UE registration procedure in TS 38.508-1 [4] table 4.5.2.2-2 , ‘connected without release’. |
– |
– |
– |
– |
|
|
48 |
Cause the UE to request establishment of PDU session with the same [S-NSSAI, DNN] combination as the PDU session established at step 26.(Note 1) |
– |
– |
– |
– |
|
|
49 |
Check: Does the UE transmit a PDU SESSION ESTABLISHMENT REQUEST? |
–> |
5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
6 |
P |
|
|
50 |
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. |
||||||
Table 10.1.3.2.3.2-2: Void
Table 10.1.3.2.3.2-3: Void
10.1.3.2.3.3 Specific message contents
Table 10.1.3.2.3.3-1: UL NAS TRANSPORT (step 2, 8, 13 and 23, Table 10.1.3.2.3.2-1; step 2a1, Table 4.5A.2.2.2-2, TS 38.508-1[4]); step 2a1, Table 4.5A.2.2.2-2, TS 38.508-1 [4]))
|
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 |
||
|
Payload container |
PDU SESSION ESTABLISHMENT REQUEST |
|||
|
DNN |
Not present |
|||
Table 10.1.3.2.3.3-1A: PDU SESSION ESTABLISHMENT ACCEPT (step 2, 9, 14 and 24, Table 10.1.3.2.3.2-1; step 3, Table 4.5A.2.2.2-1, TS 38.508-1 [4])
|
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 DNN/APN ID of the Config#1 in Table 4.8.4-1 |
|||
Table 10.1.3.2.3.3-2: PDU SESSION RELEASE COMMAND (step 3, Table 10.1.3.2.3.2-1; step 1, Table 4.9.21.2.2-1, TS 38.508-1 [4])
|
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 2 in Table 10.1.3.2.3.2-1 |
|||
|
5GSM cause |
‘0001 1010’B |
insufficient resources |
||
|
Back-off timer value |
‘1010 0010’B |
2 minutes |
||
Table 10.1.3.2.3.3-3: Void
Table 10.1.3.2.3.3-4: PDU SESSION RELEASE COMMAND (step 10, Table 10.1.3.2.3.2-1; step 1, Table 4.9.21.2.2-1, TS 38.508-1 [4])
|
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 8 in Table 10.1.3.2.3.2-1 |
|||
|
5GSM cause |
‘0001 1010’B |
insufficient resources |
||
|
Back-off timer value |
‘1010 0000’B |
0 minutes |
||
Table 10.1.3.2.3.3-5: PDU SESSION RELEASE COMMAND (step 15, Table 10.1.3.2.3.2-1; step 1, Table 4.9.21.2.2-1, TS 38.508-1 [4])
|
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 |
||
Table 10.1.3.2.3.3-6: UL NAS TRANSPORT (step 26, Table 10.1.3.2.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 |
||
|
Payload container |
PDU SESSION ESTABLISHMENT REQUEST |
|||
|
S-NSSAI |
present |
|||
|
DNN |
present |
|||
Table 10.1.3.2.3.3-6A: PDU SESSION ESTABLISHMENT ACCEPT (step 26, 33, 38, and 50,Table 10.1.3.2.3.2-1; step 3, Table 4.5A.2.2.2-1, TS 38.508-1 [4])
|
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 26, 33, 38, and 50,Table 10.1.3.2.3.2-1; step 2a1, Table 4.5A.2.2.2-2, TS 38.508-1 [4]) |
|||
Table 10.1.3.2.3.3-7: PDU SESSION RELEASE COMMAND (step 27, Table 10.1.3.2.3.2-1; step 1, Table 4.9.21.2.2-1, TS 38.508-1 [4])
|
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 26 in Table 10.1.3.2.3.2-1 |
|||
|
5GSM cause |
‘0100 0011’B |
insufficient resources for specific slice and DNN |
||
|
Back-off timer value |
‘1010 0010’B |
2 minutes |
||
Table 10.1.3.2.3.3-8: UL NAS TRANSPORT (step 32, 37 and 49, Table 10.1.3.2.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 |
||
|
Payload container |
PDU SESSION ESTABLISHMENT REQUEST |
|||
|
S-NSSAI |
The same S-NSSAI as the S-NSSAI of the PDU session which UE request at step 26 |
|||
|
DNN |
The same DNN as the DNN of the PDU session which UE request at step 26 |
|||
Table 10.1.3.2.3.3-9: PDU SESSION RELEASE COMMAND (step 34, Table 10.1.3.2.3.2-1; step 1, Table 4.9.21.2.2-1, TS 38.508-1 [4])
|
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 32 in Table 10.1.3.2.3.2-1 |
|||
|
5GSM cause |
‘0100 0011’B |
insufficient resources for specific slice and DNN |
||
|
Back-off timer value |
‘1010 0000’B |
0 minutes |
||
Table 10.1.3.2.3.3-10: PDU SESSION RELEASE COMMAND (step 39, Table 10.1.3.2.3.2-1; step 1, Table 4.9.21.2.2-1, TS 38.508-1 [4])
|
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 37 in Table 10.1.3.2.3.2-1 |
|||
|
5GSM cause |
‘0100 0011’B |
insufficient resources for specific slice and DNN |
||
|
Back-off timer value |
‘1110 0000’B |
deactivated |
||
Table 10.1.3.2.3.3-11: PDU SESSION RELEASE COMMAND (step 43, Table 10.1.3.2.3.2-1; step 1, Table 4.9.21.2.2-1, TS 38.508-1 [4])
|
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 37 in Table 10.1.3.2.3.2-1 |
|||
|
5GSM cause |
‘0010 0100’B |
#36 regular deactivation |
||
Table 10.1.3.2.3.3-11A: UL NAS TRANSPORT (step 44, Table 10.1.3.2.3.2-1)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.1-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
The same ID as the ID of PDU session which UE request in step 37 in Table 10.1.3.2.3.2-1 |
|||
|
Payload container type |
‘0001’B |
N1 SM information |
||
|
Payload container |
5GSM STATUS |
|||
Table 10.1.3.2.3.3-12: 5GSM STATUS (Table 10.1.3.2.3.3-11A)
|
Derivation Path: TS 38.508-1 [4] Table 4.7.2-16 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
5GSM cause |
‘0010 1011’B |
#43 Invalid PDU session identity |
||