Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

6.4.2  UE-requested PDU session modification procedureWord‑p. 546

6.4.2.1  GeneralWord‑p. 546

The purpose of the UE-requested PDU session modification procedure is:
  1. to enable the UE to request modification of a PDU session;
  2. to indicate a change of 3GPP PS data off UE status for a PDU session;
  3. to revoke the previously indicated support for reflective QoS;
  4. to request specific QoS handling and segregation of service data flows;
  5. to indicate to the network the relevant 5GSM parameters and capabilities (e.g. the UE's 5GSM capabilities, whether the UE supports more than 16 packet filters, the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink, the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink and whether the UE requests the PDU session to be an always-on PDU session in the 5GS) for a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface and the UE has not previously successfully performed the UE-requested PDU session modification to indicate to the network the relevant 5GSM parameters and capabilities;
  6. to delete one or more mapped EPS bearer contexts;
  7. to convey a port management information container;
  8. to re-negotiate header compression configuration associated to a PDU session using control plane CIoT 5GS optimization; or
  9. to enable the UE to request to join or leave one or more MBS multicast sessions associated with a PDU session.
When the UE-requested PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session (see subclause 6.2.10), the UE shall initiate the UE-requested PDU session modification procedure even if the UE is outside the LADN service area or the timer T3396, T3584, T3585 or the back-off timer is running or is deactivated.
If the UE needs to revoke the previously indicated support for reflective QoS for a PDU session and timer T3396, T3584, T3585 or the back-off timer is running or is deactivated, the UE shall not initiate the UE-requested PDU session modification procedure and shall instead initiate the UE-requested PDU session release procedure.
If the UE needs to initiate the UE-requested PDU session modification procedure to indicate to the network the relevant 5GSM parameters and capabilities (e.g. the UE's 5GSM capabilities, whether the UE supports more than 16 packet filters, the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink, the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink and whether the UE requests the PDU session to be an always-on PDU session in the 5GS) for a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, the UE is a UE operating in single-registration mode in the network supporting N26 interface, the UE has not previously successfully performed the UE-requested PDU session modification to indicate to the network the relevant 5GSM parameters and capabilities, and:
  1. timer T3396, T3584, T3585 or the back-off timer is running, the UE shall initiate the UE-requested PDU session modification procedure after expiry of timer T3396, T3584 or T3585 or after expiry of the back-off timer; or
  2. the UE is in substate 5GMM-REGISTERED.NON-ALLOWED-SERVICE and has not performed the the UE-requested PDU session modification procedure (see subclause 5.3.5), the UE shall initiate the UE-requested PDU session modification procedure after entering substate 5GMM-REGISTERED.NORMAL-SERVICE.
Up

6.4.2.2  UE-requested PDU session modification procedure initiationWord‑p. 547

In order to initiate the UE-requested PDU session modification procedure, the UE shall create a PDU SESSION MODIFICATION REQUEST message.
The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION MODIFICATION REQUEST message to the allocated PTI value.
The UE shall not perform the UE-requested PDU session modification procedure for an emergency PDU session, except for a procedure initiated according to subclause 6.4.2.1, item e) only, and for the error cases described in subclause 6.4.1.3 and subclause 6.3.2.3.
The UE shall not perform the UE-requested PDU session modification procedure for a PDU session for LADN when the UE is located outside the LADN service area except for indicating a change of 3GPP PS data off UE status.
If the UE requests a specific QoS handling and the PDU session is not associated with the control plane only indication, the UE shall include the Requested QoS rules IE indicating requested QoS rules or the Requested QoS flow descriptions IE indicating requested QoS flow descriptions or both for the specific QoS handling. The Requested QoS rules IE includes the packet filters which describe the service data flows requested by the UE. The specific QoS parameters requested by the UE are specified in the Requested QoS flow descriptions IE. If the UE requests the network to bind specific service data flows to a dedicated QoS flow, the UE shall create a new QoS rule by setting the rule operation code to "Create new QoS rule" and shall set the segregation bit to "Segregation requested" for the corresponding QoS rule in the Requested QoS rules IE. The UE shall set the QRI values to "no QoS rule identifier assigned" in the Requested QoS rules IE, if the QoS rules are newly created; otherwise, the UE shall set the QRI values to those of the existing QoS rules for which the specific QoS handling applies. The UE shall set the QFI values to "no QoS flow identifier assigned" in the Requested QoS flow descriptions IE, if the QoS flow descriptions are newly created; otherwise, the UE shall set the QFI values to the QFIs of the existing QoS flow descriptions for which the specific QoS handling applies. The UE shall not request to create more than one QoS flow in a UE-requested PDU session modification procedure. If the SMF receives a PDU SESSION MODIFICATION REQUEST message with a Requested QoS rules IE containing more than one QoS rule with the rule operation code set to "Create new QoS rule", the SMF shall assign the same QFI to all the QoS rules which are created.
If the UE requests to join or leave one or more MBS multicast sessions associated with a PDU session, the UE shall include the Requested MBS container IE in the PDU SESSION MODIFICATION REQUEST message and shall set the MBS operation to "Join MBS session" for the join case or to "Leave MBS session" for the leave case. The UE shall include the MBS session information(s) and shall set the Type of MBS session ID for each of the MBS session information to either "Temporary Mobile Group Identity (TMGI)" or "Source specific IP multicast address" depending on the type of the MBS session ID available in the UE. Then the remaining values of each of the MBS session informations shall be set as following:
  1. if the Type of MBS session ID is set to "Temporary Mobile Group Identity (TMGI)", the UE shall set the MBS session ID to the TMGI; or
  2. if the Type of MBS session ID is set to "Source specific IP multicast address for IPv4" or " Source specific IP multicast address for IPv6", the UE shall set the Source IP address information and the Destination IP address information to the corresponding values.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDU session type, the PDU session is not associated with the control plane only indication:
  1. the UE is performing the PDU session modification procedure to indicate the support of reflective QoS and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the RQoS bit to "Reflective QoS supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; or
  2. the UE is performing the PDU session modification procedure to indicate that reflective QoS is not supported and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the RQoS bit to "Reflective QoS not supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message.
    If the UE is performing the PDU session modification procedure to revoke the previously indicated support of reflective QoS and the PDU session is not associated with the control plane only indication, the UE shall set the RQoS bit to "Reflective QoS not supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message. The UE shall not indicate support for reflective QoS for this PDU Session for the remaining lifetime of the PDU Session.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is of "IPv6" or "IPv4v6" PDU session type, the PDU session is not associated with the control plane only indication:
  1. the UE is performing the PDU session modification procedure to indicate the support of Multi-homed IPv6 PDU session and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the MH6-PDU bit to "Multi-homed IPv6 PDU session supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; or
  2. the UE is performing the PDU session modification procedure to indicate that Multi-homed IPv6 PDU session is not supported and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall set the MH6-PDU bit to "Multi-homed IPv6 PDU session not supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDU session type, the PDU session is not associated with the control plane only indication, the UE supports more than 16 packet filters for this PDU session, and the UE has not previously successfully performed the UE-requested PDU session modification to provide this indication, the UE shall indicate the maximum number of packet filters supported for the PDU session in the Maximum number of supported packet filters IE of the PDU SESSION MODIFICATION REQUEST message.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is not associated with the control plane only indication, and the UE has not previously successfully performed the UE-requested PDU session modification to include the Integrity protection maximum data rate IE in the PDU SESSION MODIFICATION REQUEST message, the UE shall include the Integrity protection maximum data rate IE in the PDU SESSION MODIFICATION REQUEST message.
If the UE is performing the PDU session modification procedure
  1. to request the deletion of a non-default QoS rule due to errors in QoS operations or packet filters;
  2. to request the deletion of a QoS flow description due to errors in QoS operations; or
  3. to request the deletion of a mapped EPS bearer context due to errors in mapped EPS bearer operation, TFT operation or packet filters,
the UE shall include the 5GSM cause IE in the PDU SESSION MODIFICATION REQUEST message as described in subclauses 6.3.2.3, 6.3.2.4 and 6.4.1.3.
When the UE-requested PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session, the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and setting the 3GPP PS data off UE status.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, if the UE is a UE operating in single-registration mode in a network supporting N26 interface, the PDU session is not associated with the control plane only indication, the UE requests the PDU session to be an always-on PDU session in the 5GS and the UE has not previously successfully performed the UE-requested PDU session modification to request this, the UE shall include the Always-on PDU session requested IE and set the value of the IE to "Always-on PDU session requested" in the PDU SESSION MODIFICATION REQUEST message.
If a port management information container needs to be delivered (see TS 23.501 and TS 23.502), the UE shall include a Port management information container IE in the PDU SESSION MODIFICATION REQUEST message.
To request re-negotiation of IP header compression configuration, the UE shall include the IP header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message if the network indicated "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature support IE.
To request re-negotiation of Ethernet header compression configuration, the UE shall include the Ethernet header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message if the network indicated "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature support IE.
After an inter-system change from S1 mode to N1 mode, if:
  1. the UE is operating in single-registration mode in the network supporting N26 interface;
  2. the PDU session type value of the PDU session type IE is set to "IPv4", "IPv6" or "IPv4v6";
  3. the UE indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and
  4. the network indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message;
the UE shall initiate the PDU session modification procedure to negotiate the IP header compression configuration and include the IP header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message.
The UE shall include the Service-level-AA container IE in the PDU SESSION MODIFICATION REQUEST message, when requesting to modify an established PDU session for C2 communication. In the Service-level-AA container IE, the UE shall include:
  1. the service-level device ID with the value set to the CAA-level UAV ID of the UE;
  2. if available, the identification information of UAV-C to pair; and
  3. if available, the flight authorization information.
After an inter-system change from S1 mode to N1 mode, if:
  1. the UE is operating in single-registration mode in a network that supports N26 interface;
  2. the PDU session type value of the PDU session type IE is set to "Ethernet";
  3. the UE indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and
  4. the network indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message;
the UE shall initiate the PDU session modification procedure to negotiate the Ethernet header compression configuration and include the Ethernet header compression configuration IE in the PDU SESSION MODIFICATION REQUEST message.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, and if the UE is a UE operating in single-registration mode in a network supporting N26 interface, and the UE supports provisioning of ECS configuration information to the EEC in the UE and the UE has not previously successfully performed the UE-requested PDU session modification to include the ECS configuration information provisioning support indicator, the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and shall include the ECS configuration information provisioning support indicator.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, and if the UE is a UE operating in single-registration mode in a network supporting N26 interface, and the UE supports receiving DNS server addresses in protocol configuration options and the UE has not previously successfully performed the UE-requested PDU session modification to indicate this support, the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and:
  1. if the PDU session is of "IPv4" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv4 address request; and
  2. if the PDU session is of "IPv6" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv6 address request.
For a PDN connection established when in S1 mode, after an inter-system change from S1 mode to N1 mode, and if the UE is a UE operating in single-registration mode in a network supporting N26 interface, and the UE supports the EAS rediscovery and the UE has not previously successfully performed the UE-requested PDU session modification to indicate this support, the UE shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION REQUEST message and shall include the EAS rediscovery support indication in the Extended protocol configuration options IE.
The UE shall transport:
  1. the PDU SESSION MODIFICATION REQUEST message;
  2. the PDU session ID; and
  3. if the UE-requested PDU session modification:
    1. is not initiated to indicate a change of 3GPP PS data off UE status associated to a PDU session, then the request type set to "modification request"; and
    2. is initiated to indicate a change of 3GPP PS data off UE status associated to a PDU session, then without transporting the request type;
using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3581 (see example in Figure 6.4.2.2.1).
For a PDN connection established when in S1 mode and not associated with the control plane only indication, after inter-system change from S1 mode to N1 mode, if the UE is registered in a network supporting the ATSSS,
  1. the UE may request to modify a PDU session to an MA PDU session; or
  2. the UE may allow the network to upgrade the PDU session to an MA PDU session. In order for the UE to allow the network to upgrade the PDU session to an MA PDU session, the UE shall set "MA PDU session network upgrade is allowed" in the MA PDU session information IE and set the request type to "modification request" in the UL NAS TRANSPORT message.
In case the UE executes case a) or b):
  1. if the UE supports ATSSS Low-Layer functionality with any steering mode as specified in subclause 5.32.6 of TS 23.501, the UE shall set the ATSSS-ST bits to "ATSSS Low-Layer functionality with any steering mode supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message;
  2. if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode as specified in subclause 5.32.6 of TS 23.501, the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message;
  3. if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode as specified in subclause 5.32.6 of TS 23.501, the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message; and
  4. if a performance measurement function in the UE can perform access performance measurements using the QoS flow of the non-default QoS rule as specified in subclause 5.32.5 of TS 23.501, the UE shall set the APMQF bit to "Access performance measurements per QoS flow supported" in the 5GSM capability IE of the PDU SESSION MODIFICATION REQUEST message.
Reproduction of 3GPP TS 24.501, Fig. 6.4.2.2.1: UE-requested PDU session modification procedure
Up

6.4.2.3  UE-requested PDU session modification procedure accepted by the networkWord‑p. 552

Upon receipt of a PDU SESSION MODIFICATION REQUEST message, if the SMF accepts the request to modify the PDU session, the SMF shall perform the network-requested PDU session modification procedure as specified in subclause 6.3.2.
If the PDU SESSION MODIFICATION REQUEST message contains a Port management information container IE, the SMF shall handle the contents of the Port management information container IE as specified in TS 23.501 and TS 23.502.
Up

6.4.2.4  UE-requested PDU session modification procedure not accepted by the networkWord‑p. 552

6.4.2.4.1  General |R16|Word‑p. 552
Upon receipt of a PDU SESSION MODIFICATION REQUEST message, if the SMF does not accepts the request to modify the PDU session, the SMF shall create a PDU SESSION MODIFICATION REJECT message.
The SMF shall set the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message to indicate the reason for rejecting the PDU session modification.
The 5GSM cause IE typically indicates one of the following SM cause values:
#26
insufficient resources;
#29
user authentication or authorization failed;
#31
request rejected, unspecified;
#32
service option not supported;
#33
requested service option not subscribed;
#35
PTI already in use;
#37
5GS QoS not accepted;
#43
Invalid PDU session identity;
#44
Semantic errors in packet filter(s);
#45
Syntactical error in packet filter(s);
#46
out of LADN service area;
#59
unsupported 5QI value;
#67
insufficient resources for specific slice and DNN;
#69
insufficient resources for specific slice;
#83
Semantic error in the QoS operation;
#84
Syntactical error in the QoS operation; or
#95 – 111
protocol errors.
If the UE requests a PDU session modification for an LADN when the UE is located outside of the LADN service area, the SMF shall include the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.
If the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message indicates 3GPP PS data off UE status and the SMF detects the change of the 3GPP PS data off UE status, the SMF shall not include the 5GSM cause value #26 "insufficient resources", the 5GSM cause value #67 "insufficient resources for specific slice and DNN", the 5GSM cause value #69 "insufficient resources for specific slice" and the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.
If the UE initiates UE-requested PDU session modification procedure to modify the PDU session transferred from EPS to an MA PDU session with the Request type IE set to "MA PDU request" in the UL NAS TRANSPORT message as specified in TS 24.193 and the SMF determines, based on operator policy and subscription information, that the PDU SESSION MODIFICATION REQUEST message is to be rejected, the SMF shall include the 5GSM cause value #33 "requested service option not subscribed" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.
The network may include a Back-off timer value IE in the PDU SESSION MODIFICATION REJECT message.
If the 5GSM cause value is #26"insufficient resources", #67 "insufficient resources for specific slice and DNN", or #69 "insufficient resources for specific slice" and the PDU SESSION MODIFICATION REQUEST message was received from a UE configured for high priority access in selected PLMN or the request type provided during the PDU session establishment is set to "initial emergency request" or "existing emergency PDU session", the network shall not include a Back-off timer value IE.
The SMF shall send the PDU SESSION MODIFICATION REJECT message.
Upon receipt of a PDU SESSION MODIFICATION REJECT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shall stop timer T3581, release the allocated PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE.
Up
6.4.2.4.2  Handling of network rejection due to congestion control |R16|Word‑p. 553
If:
  • the 5GSM cause value #26 "insufficient resources" and the Back-off timer value IE are included in the PDU SESSION MODIFICATION REJECT message; or
  • an indication that the 5GSM message was not forwarded due to DNN based congestion control is received along a Back-off timer value and a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session;
the UE shall ignore the Re-attempt indicator IE or the 5GSM congestion re-attempt indicator IE provided by the network, if any, and the UE shall take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN, exceptions are specified in subclause 6.2.7):
  1. 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 or with the Back-off timer value received from the 5GMM sublayer and:
    1. shall not send another 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 another PDU SESSION ESTABLISHMENT REQUEST message without a DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without a 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.
  2. 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 another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, for the same DNN until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the same DNN from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the same DNN from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same DNN from the network; and
    2. shall not send another PDU SESSION ESTABLISHMENT REQUEST message without a DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without a 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, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without a DNN provided by the UE, a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without a DNN provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established without a DNN provided by the UE.
    The timer T3396 remains deactivated upon a PLMN change or inter-system change.
  3. if the timer value indicates zero, the UE:
    1. shall stop timer T3396 associated with the corresponding DNN, if running, and may send another 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 another PDU SESSION ESTABLISHMENT REQUEST message without a DNN, or another PDU SESSION MODIFICATION REQUEST message without a DNN provided by the UE.
If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN or without a DNN.
If the timer T3396 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3396 is associated (if any) is not updated, then timer T3396 is kept running until it expires or it is stopped
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 UE is switched off when the timer T3396 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3396 is associated (if any) is not updated 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 UE is a UE operating in single-registration mode in a network supporting N26 interface and the PDU SESSION MODIFICATION REQUEST message was sent for a PDN connection established when in S1 mode after an inter-system change from S1 mode to N1 mode and timer T3396 associated with the corresponding DNN (or no DNN) is running, then the UE shall re-initiate the UE-requested PDU session modification procedure after expiry of timer T3396.
If:
  • the 5GSM cause value #67 "insufficient resources for specific slice and DNN" and the Back-off timer value IE are included in the PDU SESSION MODIFICATION REJECT message; or
  • an indication that the 5GSM message was not forwarded due to S-NSSAI and DNN based congestion control is received along a Back-off timer value and a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session;
the UE shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3584 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN, exceptions are specified in subclause 6.2.8):
  1. If the timer value indicates neither zero nor deactivated, and both an S-NSSAI and a DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated, an S-NSSAI 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 T3584 associated with [S-NSSAI of the PDU session, no DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated, no S-NSSAI and a DNN was provided during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination, if it is running. If the timer value indicates neither zero nor deactivated and neither S-NSSAI nor 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 T3584 associated with the [no S-NSSAI, no DNN] combination, if it is running. The timer T3584 to be stopped includes the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running. The UE shall then start timer T3584 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and:
    1. shall not send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [S-NSSAI, DNN] combination, until timer T3584 expires or timer T3584 is stopped;
    2. 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 another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, no DNN] combination, if no DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped;
    3. shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, DNN] combination, if no S-NSSAI was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped; and
    4. 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 another PDU SESSION MODIFICATION REQUEST message with the exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, no DNN] combination, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped.
    The UE shall not stop timer T3584 upon a PLMN change or inter-system change;
  2. if the timer value indicates that this timer is deactivated:
    1. if both S-NSSAI and DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [S-NSSAI of the PDU session, DNN] combination that was sent by the UE, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the [S-NSSAI of the PDU session, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the [S-NSSAI of the PDU session, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the [S-NSSAI of the PDU session, DNN] combination from the network;
    2. if an S-NSSAI was provided but a DNN was not provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, no DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message 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 the [S-NSSAI of the PDU session, no DNN] combination, if no DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established for the [S-NSSAI of the PDU session, no DNN] combination from the network;
    3. if an S-NSSAI was not provided but a DNN was provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message, or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the [no S-NSSAI, DNN] combination, if no S-NSSAI was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the [no S-NSSAI, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the [no S-NSSAI, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the [no S-NSSAI, DNN] combination from the network; and
    4. if neither S-NSSAI nor DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message 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 the [no S-NSSAI, no DNN] combination, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established for the [no S-NSSAI, no DNN] combination from the network.
    The timer T3584 remains deactivated upon a PLMN change or inter-system change; and
  3. if the timer value indicates zero:
    1. if both S-NSSAI and DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the [S-NSSAI of the PDU session, DNN] combination;
    2. if an S-NSSAI was provided but a DNN was not provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [S-NSSAI of the PDU session, no DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [S-NSSAI of the PDU session, no DNN] combination if the request type was different from "initial emergency request" and different from "existing emergency PDU session";
    3. if an S-NSSAI was not provided but a DNN was provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [no S-NSSAI, DNN] combination; and
    4. if neither S-NSSAI nor DNN were provided by the UE during the PDU session establishment, the UE shall stop timer T3584 associated with the [no S-NSSAI, no DNN] combination (including the timer T3584 applied for all the PLMNs, if running, and the timer T3584 applied for the registered PLMN, if running), if it is running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the [no S-NSSAI, no DNN] combination and the request type was different from "initial emergency request" and different from "existing emergency PDU session".
If the 5GSM congestion re-attempt indicator IE set to "The back-off timer is applied in all PLMNs" is included in the PDU SESSION MODIFICATION REJECT message with the 5GSM cause value #67 "insufficient resources for specific slice and DNN", then the UE shall apply the timer T3584 for all the PLMNs. Otherwise, the UE shall apply the timer T3584 for the registered PLMN.
If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination, or for the same [S-NSSAI, no DNN] combination, or for the same [no S-NSSAI, DNN] combination, or for the same [no S-NSSAI, no 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 (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3584 is associated (if any) is not updated, 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 (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3584 is associated (if any) is not updated 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.
If the UE is a UE operating in single-registration mode in a network supporting N26 interface and the PDU SESSION MODIFICATION REQUEST message was sent for a PDN connection established when in S1 mode after an inter-system change from S1 mode to N1 mode and timer T3584 associated with the corresponding [no S-NSSAI, DNN] combination or [no S-NSSAI, no DNN] combination is running, then the UE shall re-initiate the UE-requested PDU session modification procedure after expiry of timer T3584.
If:
  • the 5GSM cause value #69 "insufficient resources for specific slice" and the Back-off timer value IE are included in the PDU SESSION MODIFICATION REJECT message; or
  • an indication that the 5GSM message was not forwarded due to S-NSSAI only based congestion control is received along a Back-off timer value and a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session;
the UE shall ignore the bit "RATC" and the bit "EPLMNC" in the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3585 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN, exceptions are specified in subclause 6.2.8):
  1. If the timer value indicates neither zero nor deactivated and an S-NSSAI 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 T3585 associated with the S-NSSAI of the PDU session, if it is running. If the timer value indicates neither zero nor deactivated and no S-NSSAI 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 T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running. The UE shall then start timer T3585 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and:
    1. if an S-NSSAI was provided by the UE during the PDU session establishment, 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 another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session for the S-NSSAI of the PDU session, until timer T3585 expires or timer T3585 is stopped; and
    2. if the request type was different from "initial emergency request" and from "existing emergency PDU session", and an S-NSSAI was not provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another 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 S-NSSAI provided by the UE, , until timer T3585 expires or timer T3585 is stopped.
    The UE shall not stop timer T3585 upon a PLMN change or inter-system change;
  2. if the timer value indicates that this timer is deactivated and an S-NSSAI 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 T3585 associated with the S-NSSAI of the PDU session, if it is running. If the timer value indicates that this timer is deactivated and no S-NSSAI 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 T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running. In addition:
    1. if an S-NSSAI was provided by the UE during the PDU session establishment, 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 another PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session for the S-NSSAI of the PDU session until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session for the S-NSSAI of the PDU session from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session for the S-NSSAI of the PDU session from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the S-NSSAI of the PDU session from the network; and
    2. if the request type was different from "initial emergency request" and from "existing emergency PDU session", and an S-NSSAI was not provided by the UE during the PDU session establishment, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another 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 S-NSSAI provided by the UE, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established without an S-NSSAI provided by the UE.
    The timer T3585 remains deactivated upon a PLMN change or inter-system change; and
  3. if the timer value indicates zero:
    1. if an S-NSSAI was provided by the UE during the PDU session establishment, the UE shall stop timer T3585 associated with the S-NSSAI of the PDU session (including the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running), if running, and may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the S-NSSAI of the PDU session; and
    2. if no S-NSSAI 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 T3585 associated with no S-NSSAI (including the timer T3585 applied for all the PLMNs, if running, and the timer T3585 applied for the registered PLMN, if running), if running, and may send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI, or another PDU SESSION MODIFICATION REQUEST message without an S-NSSAI provided by the UE.
If the 5GSM congestion re-attempt indicator IE set to "The back-off timer is applied in all PLMNs" is included in the PDU SESSION MODIFICATION REJECT message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE shall apply the timer T3585 for all the PLMNs. Otherwise, the UE shall apply the timer T3585 for the registered PLMN.
If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same S-NSSAI or without an S-NSSAI.
When the timer T3585 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services.
If the timer T3585 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3585 is associated (if any) is not updated, then timer T3585 is kept running until it expires or it is stopped.
If the UE is switched off when the timer T3585 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" for the SNPN to which timer T3585 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows:
  • let t1 be the time remaining for T3585 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 UE is a UE operating in single-registration mode in a network supporting N26 interface and the PDU SESSION MODIFICATION REQUEST message was sent for a PDN connection established when in S1 mode after an inter-system change from S1 mode to N1 mode and timer T3585 associated with no S-NSSAI is running, then the UE shall re-initiate the UE-requested PDU session modification procedure after expiry of timer T3585.
Upon PLMN change, if T3584 is running or is deactivated for an S-NSSAI, a DNN, and old PLMN, but T3584 is not running and is not deactivated for the S-NSSAI, the DNN, and new PLMN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI and the same DNN in the new PLMN.
Upon PLMN change, if T3585 is running or is deactivated for an S-NSSAI and old PLMN, but T3585 is not running and is not deactivated for the S-NSSAI and new PLMN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new PLMN.
Up
6.4.2.4.3  Handling of network rejection not due to congestion control |R16|Word‑p. 560
If the 5GSM cause value is different from #26 "insufficient resources", #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #46 "out of LADN service area", #59 "unsupported 5QI value", #67 "insufficient resources for specific slice and DNN", #69 "insufficient resources for specific slice", #83 "Semantic error in the QoS operation", and #84 "Syntactical error in the QoS operation", and the Back-off timer value IE is included, the UE shall behave as follows: (if the UE is a UE configured for high priority access in selected PLMN, exceptions are specified in subclause 6.2.12):
  1. if the timer value indicates neither zero nor deactivated and:
    1. if the UE provided DNN and S-NSSAI to the network during the PDU session establishment, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDU session modification procedure and [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session] combination. The UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN and the (mapped) HPLMN S-NSSAI of the PDU session in the current PLMN, until the back-off timer expires, the UE is switched off, the USIM is removed, or the entry in the "list of subscriber data" for the current SNPN is updated; or
    2. if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment, it shall start the back-off timer accordingly for the PDU session modification procedure and the [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the back-off timer expires, the UE is switched off, the USIM is removed, or the entry in the "list of subscriber data" for the current SNPN is updated;
  2. if the timer value indicates that this timer is deactivated and:
    1. if the UE provided DNN and S-NSSAI to the network during the PDU session establishment, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN and the (mapped) HPLMN S-NSSAI of the PDU session in the current PLMN, until the UE is switched off, the USIM is removed, or the entry in the "list of subscriber data" for the current SNPN is updated; or
    2. if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the UE is switched off, the USIM is removed, or the entry in the "list of subscriber data" for the current SNPN is updated; and
  3. if the timer value indicates zero, the UE may send another PDU SESSION MODIFICATION REQUEST message for the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no DNN, no S-NSSAI] in the current PLMN.
If the Back-off timer value IE is not included, then the UE shall ignore the Re-attempt indicator IE provided by the network in the PDU SESSION MODIFICATION REJECT message, if any.
  1. Additionally, if the 5GSM cause value is #32 "service option not supported", or #33 "requested service option not subscribed", then:
    1. the UE not operating in SNPN access operation mode shall proceed as follows:
      1. if the UE is registered in the HPLMN or in a PLMN that is within the EHPLMN list, the UE shall behave as described above in the present subclause using the configured SM Retry Timer value as specified in TS 24.368 or in USIM file NASCONFIG as specified in TS 31.102, if available, as back-off timer value; and
        • an SM Retry Timer value in the ME as specified in TS 24.368; and
        • an SM Retry Timer value in USIM file NASCONFIG as specified in TS 31.102.
      2. otherwise, if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list, or if the SM Retry Timer value is not configured, the UE shall behave as described above in the present subclause, using the default value of 12 minutes for the back-off timer; or
    2. the UE operating in SNPN access operation mode shall proceed as follows:
      1. if:
        1. the SM Retry Timer value for the current SNPN as specified in TS 24.368 is available; or
        2. the SM Retry Timer value in USIM file NASCONFIG as specified in TS 31.102 is available and the UE used the USIM for registration to the current SNPN;
        then the UE shall behave as described above in the present subclause using the configured SM Retry Timer value as back-off timer value; or
      2. otherwise, the UE shall behave as described above in the present subclause, using the default value of 12 minutes for the back-off timer.
  2. For 5GSM cause values different from #32 "service option not supported", or #33 "requested service option not subscribed", the UE behaviour regarding the start of a back-off timer is unspecified.
The UE shall not stop any back-off timer:
  1. upon a PLMN change;
  2. upon an inter-system change; or
  3. upon registration over another access type.
If the network indicates that a back-off timer for the PDU session modification procedure is deactivated, then it remains deactivated:
  1. upon a PLMN change;
  2. upon an inter-system change; or
  3. upon registration over another access type.
If the back-off timer is started upon receipt of a PDU SESSION MODIFICATION REJECT (i.e. the timer value was provided by the network, a configured value is available or the default value is used as explained above) or the back-off timer is deactivated, the UE behaves as follows:
  1. after a PLMN change the UE may send a PDU SESSION MODIFICATION REQUEST message for the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [new PLMN, no DNN, no S-NSSAI] in the new PLMN, if the back-off timer is not running and is not deactivated for the PDU session modification procedure and the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [new PLMN, no DNN, no S-NSSAI];
    Furthermore, as an implementation option, for the 5GSM cause value #32 "service option not supported" or #33 "requested service option not subscribed", if the network does not include a Re-attempt indicator IE, the UE may decide not to automatically send another PDU SESSION MODIFICATION REQUEST message for the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no DNN, no S-NSSAI], if the UE is registered to a new PLMN which is in the list of equivalent PLMNs.
  2. if the network does not include the Re-attempt indicator IE to indicate whether re-attempt in S1 mode is allowed, or the UE ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then:
    1. if the UE is registered in its HPLMN or in a PLMN that is within the EHPLMN list and the back-off timer is running for the combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN DNN, no S-NSSAI], the UE shall apply the configured value SM_RetryAtRATChange value as specified in TS 24.368 or in USIM file NASCONFIG as specified in TS 31.102, if available, to determine whether the UE may attempt an EPS bearer resource allocation procedure or an EPS bearer resource modification procedure for the same [PLMN, DNN] combination in S1 mode; and
    2. if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list, or if the NAS configuration MO as specified in TS 24.368 is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the UE behaviour regarding an EPS bearer resource allocation procedure or an EPS bearer resource modification procedure for the same [PLMN, DNN] combination in S1 mode is unspecified; and
  3. if the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN is not allowed, then depending on the timer value received in the Back-off timer value IE, for each combination of a PLMN from the equivalent PLMN list and the respective [DNN, (mapped) HPLMN S-NSSAI of the PDU session], [DNN, no S-NSSAI], [no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [no DNN, no S-NSSAI] combination, the UE shall start a back-off timer for the PDU session modification procedure with the value provided by the network, or deactivate the respective back-off timer as follows:
    1. if the Re-attempt indicator IE additionally indicates that re-attempt in S1 mode is allowed, the UE shall start or deactivate the back-off timer for N1 mode only; and
    2. otherwise, the UE shall start or deactivate the back-off timer for S1 and N1 mode.
If the back-off timer for a [PLMN, DNN] or [PLMN, no DNN] combination was started or deactivated in S1 mode upon receipt of BEARER RESOURCE ALLOCATION REJECT message or BEARER RESOURCE MODIFICATION REJECT message (see TS 24.301) and the network indicated that re-attempt in N1 mode is allowed, then this back-off timer does not prevent the UE from sending a PDU SESSION MODIFICATION REQUEST message in this PLMN for the same DNN after inter-system change to N1 mode. If the network indicated that re-attempt in N1 mode is not allowed, the UE shall not send any PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, in this PLMN for the same DNN in combination with any S-NSSAI or without S-NSSAI, after inter-system change to N1 mode until the timer expires, the UE is switched off or the USIM is removed.
If the 5GSM cause value is #46 "out of LADN service area", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. If the UE is not located inside the LADN service area, the UE shall not send another PDU SESSION MODIFICATION REQUEST message or another PDU SESSION ESTABLISHMENT REQUEST message for the LADN DNN provided by the UE during the PDU session establishment procedure until the LADN information for the specific LADN DNN is updated as described in subclause 5.4.4 and subclause 5.5.1. If the UE is not located inside the LADN service area, the UE shall not indicate the PDU session(s) for the LADN DNN provided by the UE during the PDU session establishment procedure in the Uplink data status IE included in the SERVICE REQUEST message until the LADN information for the specific LADN DNN is provided by network as described in subclause 5.4.4 and subclause 5.5.1.
If the 5GSM cause value is #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #59 "unsupported 5QI value", #83 "Semantic error in the QoS operation" or #84 "Syntactical error in the QoS operation", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE should pass the corresponding error cause to the upper layers.
Up

6.4.2.5  Abnormal cases in the UEWord‑p. 563

The following abnormal cases can be identified:
  1. Expiry of timer T3581.
    The UE shall, on the first expiry of the timer T3581, retransmit the PDU SESSION MODIFICATION REQUEST message and the PDU session information which was transported together with the initial transmission of the PDU SESSION MODIFICATION REQUEST message and shall reset and start timer T3581. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3581, the UE shall abort the procedure and shall release the allocated PTI.
  2. Invalid PDU session identity.
    Upon receipt of the PDU SESSION MODIFICATION REJECT message including 5GSM cause #43 "invalid PDU session identity", the UE shall perform a local release of the existing PDU session and shall stop the timer T3581.
  3. Collision of network-requested PDU session release procedure and UE-requested PDU session modification procedure.
    If the UE receives a PDU SESSION RELEASE COMMAND message during the UE-requested PDU session modification procedure, and the PDU session indicated in the PDU SESSION RELEASE COMMAND message is the PDU session that the UE had requested to modify, the UE shall abort the PDU session modification procedure and proceed with the network-requested PDU session release procedure.
  4. Handling DL user data packets marked with RQI when UE has already revoked the usage of reflective QoS
    If the UE receives a DL user data packet marked with a RQI and the DL user data packet belongs to a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type for which the UE has already revoked the usage of reflective QoS, then the UE shall ignore the RQI and shall handle the received DL user data packet.
  5. Collision of network-requested PDU session modification procedure and UE-requested PDU session modification procedure.
    The handling of the same abnormal case as described in subclause 6.3.2.6 applies.
  6. Upon receiving an indication that the 5GSM message was not forwarded due to service area restrictions along with a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall abort the procedure and shall stop the timer T3581.
  7. Upon receiving an indication that the 5GSM message was not forwarded due to routing failure along with a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3581 and shall abort the procedure.
  8. Collision of UE-requested PDU session modification procedure and N1 NAS signalling connection release
    The UE may immediately retransmit the PDU SESSION MODIFICATION REQUEST message and stop, reset and restart timer T3581, if the following conditions apply:
    1. The original UE-requested PDU session modification procedure was initiated over an existing N1 NAS signalling connection;
    2. the previous transmission of the PDU SESSION MODIFICATION REQUEST message was not initiated due to timer T3581 expiry; and
    3. no 5GSM message related to the PDU session (e.g. PDU SESSION MODIFICATION REJECT or PDU SESSION RELEASE COMMAND message, see item c)) or indication that the 5GSM message was not forwarded (see item f) and g)) was received after the PDU SESSION MODIFICATION REQUEST message was transmitted.
Up

6.4.2.6  Abnormal cases on the network sideWord‑p. 564

The following abnormal cases can be identified:
  1. If the PDU session is an emergency PDU session and the 5GSM cause IE is not included in the PDU SESSION MODIFICATION REQUEST message or is set to a 5GSM cause other than the 5GSM causes #41, #42, #44, #45, #83, #84, and #85, the SMF shall reject the PDU SESSION MODIFICATION REQUEST message with 5GSM cause #31 "request rejected, unspecified".
  2. PDU session inactive for the received PDU session identity.
    If the PDU session ID in the PDU SESSION MODIFICATION REQUEST message belongs to any PDU session in state PDU SESSION INACTIVE in the SMF, the SMF shall set the 5GSM cause IE to #43 "Invalid PDU session identity" in the PDU SESSION MODIFICATION REJECT message.
  3. Collision of network-requested PDU session modification procedure and UE-requested PDU session modification procedure.
    The handling of the same abnormal case as described in subclause 6.3.2.5 applies.
  4. AMF provides a "message was exempted from the DNN based congestion activated in the AMF" but the UE-requested PDU session modification procedure is not exempt from DNN based congestion control.
    If the SMF receives an exemptionInd attribute indicating "message was exempted from the DNN based congestion activated in the AMF" as specified in TS 29.502, and the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message does not indicate 3GPP PS data off UE status, then the SMF shall set the 5GSM cause #26 "insufficient resources" in the PDU SESSION MODIFICATION REJECT message.
  5. AMF provides a "message was exempted from the S-NSSAI and DNN based congestion activated in the AMF" but the UE-requested PDU session modification procedure is not exempt from S-NSSAI only based congestion control.
    If the SMF receives an exemptionInd attribute indicating "message was exempted from the S-NSSAI and DNN based congestion activated in the AMF" as specified in TS 29.502, and the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message does not indicate 3GPP PS data off UE status, then the SMF shall set the 5GSM cause #67 "insufficient resources for specific slice and DNN" in the PDU SESSION MODIFICATION REJECT message.
  6. AMF provides a "message was exempted from the S-NSSAI only based congestion activated in the AMF" but the UE-requested PDU session modification procedure is not exempt from S-NSSAI only based congestion control.
    If the SMF receives an exemptionInd attribute indicating "message was exempted from the S-NSSAI only based congestion activated in the AMF" as specified in TS 29.502, and the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message does not indicate 3GPP PS data off UE status, then the SMF shall set the 5GSM cause #69 "insufficient resources for specific slice" in the PDU SESSION MODIFICATION REJECT message.
  7. 5G access network cannot forward the message.
    If the SMF determines based on content of the n2SmInfo attribute specified in TS 29.502 that the DL NAS TRANSPORT message carrying the PDU SESSION MODIFICATION COMMAND message was not forwarded to the UE by the 5G access network due to a cause other than handover procedure in progress, then the SMF shall reject the UE-requested PDU session modification procedure with an appropriate 5GSM cause value in the PDU SESSION MODIFICATION REJECT message.
Up

6.4.3  UE-requested PDU session release procedureWord‑p. 565

6.4.3.1  GeneralWord‑p. 565

The purpose of the UE-requested PDU session release procedure is to enable by the UE to request a release of a PDU session.
The UE is allowed to initiate the PDU session release procedure even if the timer T3396 is running.
The UE is allowed to initiate the PDU session release procedure even if the timer T3584 is running.
The UE is allowed to initiate the PDU session release procedure even if the timer T3585 is running.
The UE is allowed to initiate the PDU session release procedure even if the UE is outside the LADN service area.
Up

6.4.3.2  UE-requested PDU session release procedure initiationWord‑p. 565

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:
#26
insufficient resources;
#36
regular deactivation;
#44
Semantic errors in packet filter(s);
#45
Syntactical error in packet filter(s);
#83
Semantic error in the QoS operation;
#84
Syntactical error in the QoS operation;
#96
Invalid mandatory information.
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).
If the UE is releasing the PDU session due to:
  1. errors in QoS operations or packet filters; or
  2. the number of the authorized QoS rules, the number of the packet filters, or the number of the authorized QoS flow descriptions associated with the PDU session have reached the maximum number supported by the UE,
the UE shall include the 5GSM cause IE in the PDU SESSION RELEASE REQUEST message as described in subclauses 6.3.2.4 and 6.4.1.3.
Reproduction of 3GPP TS 24.501, Fig. 6.4.3.2.1: UE-requested PDU session release procedure
Up

6.4.3.3  UE-requested PDU session release procedure accepted by the networkWord‑p. 566

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.

6.4.3.4  UE-requested PDU session release procedure not accepted by the networkWord‑p. 566

Upon receipt of a PDU SESSION RELEASE REQUEST message, if the SMF does not accept the request to release the PDU session, the SMF shall create a PDU SESSION RELEASE REJECT message.
The SMF shall set the 5GSM cause IE of the PDU SESSION RELEASE REJECT message to indicate the reason for rejecting the PDU session release.
The 5GSM cause IE typically indicates one of the following SM cause values:
#35
PTI already in use; or
#43
Invalid PDU session identity; or
#95 – 111:
protocol errors.
The SMF shall send the PDU SESSION RELEASE REJECT message.
Upon receipt of a PDU SESSION RELEASE REJECT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shall stop timer T3582, release the allocated PTI value and locally release the PDU session.
Up

6.4.3.5  Abnormal cases in the UEWord‑p. 566

The following abnormal cases can be identified:
  1. Expiry of timer T3582.
    The UE shall, on the first expiry of the timer T3582, retransmit the PDU SESSION RELEASE REQUEST message and the PDU session information which was transported together with the initial transmission of the PDU SESSION RELEASE REQUEST message and shall reset and start timer T3582. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3582, the UE shall abort the procedure, release the allocated PTI, perform a local release of the PDU session, and perform the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message including the PDU session status IE over each access that user plane resources have been established if the PDU session is an MA PDU session, or over the access the PDU session is associated with if the PDU session is a single access PDU session.
  2. 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.
  3. 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, the PDU session indicated in the PDU SESSION RELEASE COMMAND message is the same as the PDU session that the UE requests to release:
    • if the Access type IE is included in the PDU SESSION RELEASE COMMAND message and the PDU session is an MA PDU session and having user-plane resources established on the access different from the access indicated in the Access type IE in the PDU SESSION RELEASE COMMAND message, the UE shall proceed both the UE-requested PDU session release procedure and network-requested PDU session release procedure; or
    • otherwise, the UE shall abort the UE-requested PDU session release procedure and shall stop the timer T3582 and proceed with the network-requested PDU session release procedure.
  4. Receipt of an indication that the 5GSM message was not forwarded due to routing failure
    Upon receiving an indication that the 5GSM message was not forwarded due to routing failure along with a PDU SESSION RELEASE REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3582, abort the procedure, release the allocated PTI, perform a local release of the PDU session, and perform the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message including the PDU session status IE over each access that user plane resources have been established if the PDU session is an MA PDU session, or over the access the PDU session is associated with if the PDU session is a single access PDU session.
  5. PDU session release signalling restricted due to service area restriction
    The UE may delay the release of the PDU session until the UE is not restricted by service area restrictions, or it may release the allocated PTI, perform a local release of the PDU session, and include the PDU session status IE over each access that user plane resources have been established if the PDU session is an MA PDU session, or over the access the PDU session is associated with if the PDU session is a single access PDU when performing the next registration procedure.
  6. Collision of UE-requested PDU session release procedure and N1 NAS signalling connection release
    The UE may immediately retransmit the PDU SESSION RELEASE REQUEST message and stop, reset and restart timer T3582, if the following conditions apply:
    1. The original UE-requested PDU session release procedure was initiated over an existing N1 NAS signalling connection;
    2. the previous transmission of the PDU SESSION RELEASE REQUEST message was not initiated due to timer T3582 expiry; and
    3. no 5GSM message related to the PDU session (e.g. PDU SESSION RELEASE REJECT message) or indication that the 5GSM message was not forwarded (see item d) was received after the PDU SESSION RELEASE REQUEST message was transmitted.
Up

6.4.3.6  Abnormal cases on the network sideWord‑p. 568

The following abnormal cases can be identified:
  1. PDU session inactive for the received PDU session identity.
    If the PDU session ID in the PDU SESSION RELEASE REQUEST message belongs to any PDU session in state PDU SESSION INACTIVE in the SMF, the SMF shall send the PDU SESSION RELEASE REJECT message to the UE with the 5GSM cause #43 "Invalid PDU session identity".

Up   Top   ToC