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.3.2  Network-requested PDU session modification procedureWord‑p. 473

6.3.2.1  GeneralWord‑p. 473

The purpose of the network-requested PDU session modification procedure is to enable the network to modify a PDU session, re-negotiate header compression configuration associated to a PDU session, convey a port management information container, to trigger EAS rediscovery, provide updated DNS server address(es) due to the newly selected local DNS server or the newly selected EASDF, remove joined UE from one or more MBS multicast sessions associated with a PDU session, update ATSSS parameters (e.g. ATSSS rules) or update the MBS service area of MBS multicast session that the UE has joined.
Up

6.3.2.2  Network-requested PDU session modification procedure initiationWord‑p. 473

In order to initiate the network-requested PDU session modification procedure, the SMF shall create a PDU SESSION MODIFICATION COMMAND message.
If the authorized QoS rules of the PDU session is modified or is marked as to be synchronised with the UE, the SMF shall set the Authorized QoS rules IE of the PDU SESSION MODIFICATION COMMAND message to the authorized QoS rules of the PDU session. The SMF shall ensure that the number of the packet filters used in the authorized QoS rules of the PDU Session does not exceed the maximum number of packet filters supported by the UE for the PDU session. The SMF may bind service data flows for which the UE has requested traffic segregation to a dedicated QoS flow for the PDU session, if possible. Otherwise the SMF may bind the service data flows to an existing QoS flow. The SMF shall use only one dedicated QoS flow for traffic segregation. If the UE has requested traffic segregation for multiple service data flows with different QoS handling, the SMF shall bind all these service data flows to a single QoS flow. If the SMF allows traffic segregation for service data flows in a QoS rule, then the SMF shall create a new authorized QoS rule for these service data flows and shall delete packet filters corresponding to these service data flows from the other authorized QoS rules.
If the authorized QoS flow descriptions of the PDU session is modified or is marked as to be synchronised with the UE, the SMF shall set the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message to the authorized QoS flow descriptions of the PDU session.
If SMF creates a new authorized QoS rule for a new QoS flow, then SMF shall include the authorized QoS flow description for that QoS flow in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message, if:
  1. the newly created authorized QoS rules is for a new GBR QoS flow;
  2. the QFI of the new QoS flow is not the same as the 5QI of the QoS flow identified by the QFI;
  3. the new QoS flow can be mapped to an EPS bearer as specified in subclause 4.11.1 of TS 23.502; or
  4. the new QoS flow is established for the PDU session used for relaying, as specified in subclause 5.6.2.1 of TS 23.304.
If the session-AMBR of the PDU session is modified, the SMF shall set the selected Session-AMBR IE of the PDU SESSION MODIFICATION COMMAND message to the session-AMBR of the PDU session.
If interworking with EPS is supported for the PDU session and if the mapped EPS bearer contexts of the PDU session is modified, the SMF shall set the Mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message to the mapped EPS bearer contexts of the PDU session. If the association between a QoS flow and the mapped EPS bearer context is changed, the SMF shall set the EPS bearer identity parameter in Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message to the new EPS bearer identity associated with the QoS flow.
If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the PDU SESSION MODIFICATION REQUEST message includes a 5GSM capability IE, the SMF shall:
  1. if the RQoS bit is set to:
    1. "Reflective QoS supported", consider that the UE supports reflective QoS for this PDU session; or
    2. "Reflective QoS not supported", consider that the UE does not support reflective QoS for this PDU session; and;
  2. if the MH6-PDU bit is set to:
    1. "Multi-homed IPv6 PDU session supported", consider that this PDU session is supported to use multiple IPv6 prefixes; or
    2. "Multi-homed IPv6 PDU session not supported", consider that this PDU session is not supported to use multiple IPv6 prefixes.
If the SMF considers that reflective QoS is supported for QoS flows belonging to this PDU session, the SMF may include the RQ timer IE set to an RQ timer value in the PDU SESSION MODIFICATION COMMAND message.
If a port management information container needs to be delivered (see TS 23.501 and TS 23.502) and the UE has set the TPMIC bit to "Transport of port management information container supported" in the 5GSM capability IE, the SMF shall include a Port management information container IE in the PDU SESSION MODIFICATION COMMAND message.
For a PDN connection established when in S1 mode, upon the first inter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the PDU session type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and the PDU SESSION MODIFICATION REQUEST message includes a Maximum number of supported packet filters IE, the SMF shall consider this number as the maximum number of packet filters that can be supported by the UE for this PDU session. Otherwise the SMF considers that the UE supports 16 packet filters for this PDU session.
For a PDN connection established when in S1 mode, upon the first inter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the SMF shall consider that the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink are valid for the lifetime of the PDU session.
For a PDN connection established when in S1 mode, upon the first inter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the SMF determines, based on local policies or configurations in the SMF and the Always-on PDU session requested IE in the PDU SESSION MODIFICATION REQUEST message (if available), that either:
  1. the requested PDU session needs to be an always-on PDU session, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session required"; or
  2. the requested PDU session shall not be an always-on PDU session and:
    1. if the UE included the Always-on PDU session requested IE, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session not allowed"; or
    2. if the UE did not include the Always-on PDU session requested IE, the SMF shall not include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message.
If a QoS flow for URLLC is created in a PDU session and the SMF has not provided the Always-on PDU session indication IE with the value set to "Always-on PDU session required" in the UE-requested PDU session establishment procedure or a network-requested PDU session modification procedure for the PDU session, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session required".
If the value of the RQ timer is set to "deactivated" or has a value of zero, the UE considers that RQoS is not applied for this PDU session and remove the derived QoS rule(s) associated with the PDU session, if any.
If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the SMF shall set the PTI IE of the PDU SESSION MODIFICATION COMMAND message to the PTI of the PDU SESSION MODIFICATION REQUEST message received as part of the UE-requested PDU session modification procedure.
If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the UE has included the Requested MBS container IE in the PDU SESSION MODIFICATION REQUEST message with the MBS operation set to "Join MBS session", the SMF:
  1. shall include the TMGI for the MBS session IDs that the UE is allowed to join, if any, in the Received MBS container IE, shall set the MBS Decision to "MBS join is accepted" for each of those Received MBS information and may include the MBS start time to indicate the time when the MBS session starts;
  2. shall include the TMGI for MBS session IDs that the UE is rejected to join, if any, in the Received MBS container IE, shall set the MBS Decision to "MBS join is rejected" for each of those Received MBS information, shall set the Rejection cause for each of those Received MBS information with the reason of rejection and, if the Rejection cause is set to "MBS session has not started or will not start soon", may include an MBS back-off timer value; and
  3. may include in the Received MBS container IE the MBS service area for each MBS session and include in it the MBS TAI list, the NR CGI list or both, that identify the service area(s) for the local MBS service;
in the PDU SESSION MODIFICATION COMMAND message. If the UE has set the Type of MBS session ID to "Source specific IP multicast address" in the Requested MBS container IE for certain MBS session(s) in the PDU SESSION MODIFICATION REQUEST message, the SMF shall include the Source IP address information and Destination IP address information in the Received MBS information together with the TMGI for each of those MBS sessions.
If:
  1. the SMF wants to remove joined UE from one or more MBS sessions; or
  2. the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the UE has included the Requested MBS container IE in the PDU SESSION MODIFICATION REQUEST message with the MBS operation set to "Leave MBS session",
the SMF shall include the MBS session IDs that the UE is removed from, if any, in the Received MBS container IE in the PDU SESSION MODIFICATION COMMAND message and shall set the MBS Decision to "Remove UE from MBS session" for each of those Received MBS information. The SMF may include the updated MBS service area in each of the Received MBS information, if any.
If the SMF wants to update the MBS service area of an MBS session that the UE has joined, the SMF shall include the corresponding MBS session ID and the updated MBS service area in the Received MBS container IE in the PDU SESSION MODIFICATION COMMAND message, and shall set the MBS Decision to "MBS service area update" in the Received MBS information.
If the network needs to update ATSSS parameters (see subclause 5.2.4 of TS 24.193), the SMF shall include the ATSSS container IE with the updates of ATSSS parameters in the PDU SESSION MODIFICATION COMMAND message.
If the network-requested PDU session modification procedure is not triggered by a UE-requested PDU session modification procedure, the SMF shall set the PTI IE of the PDU SESSION MODIFICATION COMMAND message to "No procedure transaction identity assigned".
If the selected SSC mode of the PDU session is "SSC mode 3" and the SMF requests the relocation of SSC mode 3 PDU session anchor with multiple PDU sessions as specified in TS 23.502, the SMF shall include 5GSM cause #39 "reactivation requested" , in the PDU SESSION MODIFICATION COMMAND message, and may include the PDU session address lifetime in a PDU session address lifetime parameter in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message.
The SMF shall send the PDU SESSION MODIFICATION COMMAND message, and the SMF shall start timer T3591 (see example in Figure 6.3.2.2.1).
If the control plane CIoT 5GS optimization is enabled for a PDU session and the IP header compression configuration IE was included in the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST message, and the SMF supports control plane CIoT 5GS optimization and IP header compression for control plane CIoT 5GS optimization, the SMF may include the IP header compression configuration IE in the PDU SESSION MODIFICATION COMMAND message to re-negotiate IP header compression configuration associated to the PDU session.
If the control plane CIoT 5GS optimization is enabled for a PDU session and the Ethernet header compression configuration IE was included in the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST message, and the SMF supports control plane CIoT 5GS optimization and Ethernet header compression for control plane CIoT 5GS optimization, the SMF may include the Ethernet header compression configuration IE in the PDU SESSION MODIFICATION COMMAND message to re-configure Ethernet header compression configuration associated with the PDU session.
If the network-requested PDU session modification procedure which is associated with C2 communication of the UAS services, is triggered by a UE-requested PDU session modification procedure, the PDU SESSION MODIFICATION REQUEST message includes Service-level-AA container IE and the request is accepted by the network, the SMF shall send the PDU SESSION MODIFICATION COMMAND message by including the Service-level-AA container IE. The Service-level-AA container IE:
  1. includes C2 authorization result;
  2. can include C2 session security information; and
  3. can include the service-level device ID set to a new CAA-level UAV ID.
If the service-level AA procedure is triggered for the established PDU session for UAS services with re-authentication purpose, and the SMF is informed by the UAS NF that UUAA-SM is successful, the SMF shall transmit a PDU SESSION MODIFICATION COMMAND message to the UE, where the PDU SESSION MODIFICATION COMMAND message:
  1. shall include a service-level-AA response in the service-level-AA container, with the value of the service-level-AA result, set to "Service level authentication and authorization was successful";
  2. may include the service-level device ID with the value set to the CAA-level UAV ID if received from the UAS-NF; and
  3. may include the service-level-AA payload with the value set to the UUAA authorization payload if received from the UAS-NF.
If the SMF needs to provide new ECS configuration information to the UE and the UE has indicated support for ECS configuration information provisioning in the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST message, then the SMF may include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message with at least one of ECS IPv4 Address, ECS IPv6 Address and ECS FQDN included and may include an ECS provider identifier. A spatial validity condition where the ECS configuration information is applicable may be included by the SMF along with a ECS IPv4 Address, a ECS IPv6 Address, or a ECS FQDN respectively.
If the SMF needs to provide DNS server address(es) to the UE and the UE has provided the DNS server IPv4 address request, the DNS server IPv6 address request or both of them, in the PDU SESSION ESTABLISHMENT REQUEST message or a PDU SESSION MODIFICATION REQUEST message, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message with one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them.
If the SMF needs to trigger EAS rediscovery and the UE has indicated support of the EAS rediscovery in the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST message, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message:
  1. with the EAS rediscovery indication without indicated impact; or
  2. with the following:
    1. one or more EAS rediscovery indication(s) with impacted EAS IPv4 address range, if the UE supports EAS rediscovery indication(s) with impacted EAS IPv4 address range;
    2. one or more EAS rediscovery indication(s) with impacted EAS IPv6 address range, if the UE supports EAS rediscovery indication(s) with impacted EAS IPv6 address range;
    3. one or more EAS rediscovery indication(s) with impacted EAS FQDN, if the UE supports EAS rediscovery indication(s) with impacted EAS FQDN; or
    4. any combination of the above.
When UE has requested P-CSCF IPv6 address or P-CSCF IPv4 address and the SMF has provided P-CSCF address(es) during the PDU session establishment procedure, if the network-requested PDU session modification procedure is triggered for P-CSCF restoration, the SMF shall include the P-CSCF IP address(es) in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message as specified in subclause 5.8.2.2 of TS 23.380.
Reproduction of 3GPP TS 24.501, Fig. 6.3.2.2.1: Network-requested PDU session modification procedure
Up

6.3.2.3  Network-requested PDU session modification procedure accepted by the UEWord‑p. 478

Upon receipt of the PDU SESSION MODIFICATION COMMAND message, if the UE provided a DNN during the PDU session establishment, the UE shall stop timer T3396, if it is running for the DNN provided by the UE. If the UE did not provide a DNN during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3396 associated with no DNN if it is running. If the PDU SESSION MODIFICATION COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3396 associated with no DNN if it is running.
Upon receipt of the PDU SESSION MODIFICATION COMMAND message, if the UE provided an S-NSSAI and a DNN during the PDU session establishment, the UE shall stop timer T3584, if it is running for the [S-NSSAI of the PDU session, DNN] combination provided by the UE. If the UE provided a DNN and did not provide an S-NSSAI during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [no S-NSSAI, DNN] combination provided by the UE. If the UE provided an S-NSSAI and did not provide a DNN during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [S-NSSAI, no DNN] combination provided by the UE. If the UE provided neither a DNN nor an S-NSSAI during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [no S-NSSAI, no DNN] combination provided by the UE. 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.
Upon receipt of the PDU SESSION MODIFICATION COMMAND message, if the UE provided an S-NSSAI during the PDU session establishment, the UE shall stop timer T3585, if it is running for the S-NSSAI of the PDU session. If the UE did not provide an S-NSSAI during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3585 associated with no S-NSSAI if it is running. 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. If the PDU SESSION MODIFICATION COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3585 associated with no S-NSSAI if it is running.
If the PDU SESSION MODIFICATION COMMAND message includes the Authorized QoS rules IE, the UE shall process the QoS rules sequentially starting with the first QoS rule.
If the PDU SESSION MODIFICATION COMMAND message includes the Mapped EPS bearer contexts IE, the UE shall process the mapped EPS bearer contexts sequentially starting with the first mapped EPS bearer context.
If the PDU SESSION MODIFICATION COMMAND message includes the Authorized QoS flow descriptions IE, the UE shall process the QoS flow descriptions sequentially starting with the first QoS flow description.
The UE shall replace the stored authorized QoS rules, authorized QoS flow descriptions and session-AMBR of the PDU session with the received value(s), if any, in the PDU SESSION MODIFICATION COMMAND message.
If the PDU SESSION MODIFICATION COMMAND message includes a Mapped EPS bearer contexts IE, the UE shall check each mapped EPS bearer context for different types of errors as follows:
  1. Semantic error in the mapped EPS bearer operation:
    1. operation code = "Create new EPS bearer" and there is already an existing mapped EPS bearer context with the same EPS bearer identity associated with any PDU session.
    2. operation code = "Delete existing EPS bearer" and there is no existing mapped EPS bearer context with the same EPS bearer identity associated with the PDU session that is being modified.
    3. operation code = "Modify existing EPS bearer" and there is no existing mapped EPS bearer context with the same EPS bearer identity associated with the PDU session that is being modified.
    4. operation code = "Create new EPS bearer" or "Modify existing EPS bearer" and the resulting mapped EPS bearer context has invalid or missing mandatory parameters (e.g., mapped EPS QoS parameters or traffic flow template for a dedicated EPS bearer context).
    In case 1, if the existing mapped EPS bearer context is associated with the PDU session that is being modified, the UE shall not diagnose an error, further process the create request and, if it was process successfully, delete the old EPS bearer context.
    In case 2, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the mapped EPS bearer context as successfully deleted.
    Otherwise, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity".
    b) if the mapped EPS bearer context includes a traffic flow template, the UE shall check the traffic flow template for different types of TFT IE errors as follows:
    1. Semantic errors in TFT operations:
      1. TFT operation = "Create a new TFT" when there is already an existing TFT for the EPS bearer context.
      2. When the TFT operation is an operation other than "Create a new TFT" and there is no TFT for the EPS bearer context.
      3. TFT operation = "Delete packet filters from existing TFT" when it would render the TFT empty.
      4. TFT operation = "Delete existing TFT" for a dedicated EPS bearer context.
      In case iv, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #41 "semantic error in the TFT operation".
      In the other cases the UE shall not diagnose an error and perform the following actions to resolve the inconsistency:
      In case i, the UE shall further process the new activation request to create a new TFT and, if it was processed successfully, delete the old TFT.
      In case ii, the UE shall:
      • process the new request and if the TFT operation is "Delete existing TFT" or "Delete packet filters from existing TFT", and if no error according to items 2, 3, and 4 was detected, consider the TFT as successfully deleted;
      • process the new request as an activation request, if the TFT operation is "Add packet filters in existing TFT" or "Replace packet filters in existing TFT".
      In case iii, if the packet filters belong to a dedicated EPS bearer context, the UE shall process the new deletion request and, if no error according to items 2, 3, and 4 was detected, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #41 "semantic error in the TFT operation".
      In case iii, if the packet filters belong to the default EPS bearer context, the UE shall process the new deletion request and if no error according to items 2, 3, and 4 was detected then delete the existing TFT, this corresponds to using match-all packet filter for the default EPS bearer context.
    2. Syntactical errors in TFT operations:
      1. When the TFT operation = "Create a new TFT", "Add packet filters in existing TFT", "Replace packet filters in existing TFT" or "Delete packet filters from existing TFT" and the packet filter list in the TFT IE is empty.
      2. TFT operation = "Delete existing TFT" or "No TFT operation" with a non-empty packet filter list in the TFT IE.
      3. TFT operation = "Replace packet filters in existing TFT" when the packet filter to be replaced does not exist in the original TFT.
      4. TFT operation = "Delete packet filters from existing TFT" when the packet filter to be deleted does not exist in the original TFT.
      5. Void.
      6. When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE).
      In case iii, the UE shall not diagnose an error, further process the replace request and, if no error according to items 3 and 4 was detected, include the packet filters received to the existing TFT.
      In case iv, the UE shall not diagnose an error, further process the deletion request and, if no error according to items 3 and 4 was detected, consider the respective packet filter as successfully deleted.
      Otherwise, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #42 "syntactical error in the TFT operation".
    3. Semantic errors in packet filters:
      1. When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document.
      2. When the resulting TFT, which is assigned to a dedicated EPS bearer context, does not contain any packet filter applicable for the uplink direction among the packet filters created on request from the network.
      After sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #44 "semantic errors in packet filter(s)".
    4. Syntactical errors in packet filters:
      1. When the TFT operation = "Create a new TFT", "Add packet filters to existing TFT", or "Replace packet filters in existing TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers.
      2. When the TFT operation = "Create a new TFT", "Add packet filters to existing TFT" or "Replace packet filters in existing TFT", and two or more packet filters among all TFTs associated with this PDN connection would have identical packet filter precedence values.
      3. When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier.
      In case i, if two or more packet filters with identical packet filter identifiers are contained in the new request, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical error in packet filter(s)". Otherwise, the UE shall not diagnose an error, further process the new request and, if it was processed successfully, delete the old packet filters which have the identical packet filter identifiers.
      In case ii, if the old packet filters do not belong to the default EPS bearer context, the UE shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old packet filters which have identical filter precedence values.
      In case ii, if one or more old packet filters belong to the default EPS bearer context, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical errors in packet filter(s)".
      Otherwise, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical error in packet filter(s)".
And if a new EPS bearer identity parameter in Authorized QoS flow descriptions IE is received for a QoS flow which can be transferred to EPS, the UE shall update the association between the QoS flow and the mapped EPS bearer context, based on the new EPS bearer identity and the mapped EPS bearer contexts. If the "Delete existing EPS bearer" operation code in the Mapped EPS bearer contexts IE was received, the UE shall discard the association between the QoS flow and the corresponding mapped EPS bearer context.
If:
  1. the UE detects different errors in the mapped EPS bearer contexts as described above which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts; and
  2. optionally, if the UE detects errors in QoS rules that require to delete at least one QoS rule as described in subclause 6.3.2.4 which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous QoS rules;
the UE, after sending the PDU SESSSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, may send a single PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts, and optionally to delete the erroneous QoS rules. The UE shall include a 5GSM cause IE in the PDU SESSION MODIFICATION REQUEST message.
Upon receipt of a PDU SESSION MODIFICATION COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, if the UE accepts the PDU SESSION MODIFICATION COMMAND message, the UE considers the PDU session as modified and the UE shall create a PDU SESSION MODIFICATION COMPLETE message.
If the PDU SESSION MODIFICATION COMMAND message contains the PTI value allocated in the UE-requested PDU session modification procedure, the UE shall stop the timer T3581. The UE should ensure that the PTI value assigned to this procedure is not released immediately.
While the PTI value is not released, the UE regards any received PDU SESSION MODIFICATION COMMAND message with the same PTI value as a network retransmission (see subclause 7.3.1).
If the selected SSC mode of the PDU session is "SSC mode 3" and the PDU SESSION MODIFICATION COMMAND message includes 5GSM cause #39 "reactivation requested", the UE can provide to the upper layers the PDU session address lifetime if received in the PDU session address lifetime parameter of the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message. After the completion of the network-requested PDU session modification procedure:
  1. if the PDU session is an MA PDU session:
    1. established over both 3GPP access and non-3GPP access, and:
      • the UE is registered over both 3GPP access and non-3GPP access in the same PLMN:
        • the UE should re-initiate a UE-requested PDU session establishment procedure as specified in subclause 6.4.1 over the access the PDU SESSION MODIFICATION COMMAND message is received; or
      • the UE is registered over both 3GPP access and non-3GPP access in different PLMNs:
        • the UE should re-initiate UE-requested PDU session establishment procedures as specified in subclause 6.4.1 over both accesses. The UE should re-initiate the UE-requested PDU session establishment procedure over the access the PDU SESSION MODIFICATION COMMAND message is received first; or
    2. established over only single access:
      • the UE should re-initiate a UE-requested PDU session establishment procedure as specified in subclause 6.4.1 over the access the user plane resources were established; or
  2. if the PDU session is a single access PDU session:
    • the UE should re-initiate a UE-requested PDU session establishment procedure as specified in subclause 6.4.1 over the access the PDU session was associated with; and
for the re-initiated UE-requested PDU session establishment procedure(s) the UE should set a new PDU session ID different from the PDU session ID associated with the present PDU session and shoulds:
  1. the PDU session type to the PDU session type associated with the present PDU session;
  2. the SSC mode to the SSC mode associated with the present PDU session;
  3. the DNN to the DNN associated with the present PDU session; and
  4. the S-NSSAI to the SNSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI if provided in the UE-requested PDU session establishment procedure of the present PDU session.
If the UE has indicated support for CIoT 5GS optimizations and receives a small data rate control parameters container in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message, the UE shall store the small data rate control parameters value and use the stored small data rate control parameters value as the maximum allowed limit of uplink user data for the PDU session in accordance with TS 23.501. If the UE has a previously stored small data rate control parameter value for the PDU session, the UE shall replace the stored small data rate control parameters value for the PDU session with the received small data rate control parameters value in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message.
If the UE has indicated support for CIoT 5GS optimizations and receives an additional small data rate control parameters for exception data container in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message, the UE shall store the additional small data rate control parameters for exception data value and use the stored additional small data rate control parameters for exception data value as the maximum allowed limit of uplink exception data for the PDU session in accordance with TS 23.501. If the UE has a previously stored additional small data rate control parameters for exception data value for the PDU session, the UE shall replace the stored additional small data rate control parameters for exception data value for the PDU session with the received additional small data rate control parameters for exception data value in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message.
The UE shall include the PDU session ID of the old PDU session which is about to get released in the old PDU session ID IE of the UL NAS TRANSPORT message that transports the PDU SESSION ESTABLISHMENT REQUEST message.
If the selected PDU session type of the PDU session is "Unstructured", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. After sending the PDU SESSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity".
If the selected PDU session type of the PDU session is "Ethernet", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, the UE, the network or both of them do not support Ethernet PDN type in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message contains an EPS bearer identity (EBI), the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. After sending the PDU SESSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity".
If the Always-on PDU session indication IE is included in the PDU SESSION MODIFICATION COMMAND message and:
  1. the value of the IE is set to "Always-on PDU session required", the UE shall consider the established PDU session as an always-on PDU session; or
  2. the value of the IE is set to "Always-on PDU session not allowed", the UE shall not consider the established PDU session as an always-on PDU session.
If the UE does not receive the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message:
  1. if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure upon an inter-system change from S1 mode to N1 mode for a PDN connection established when in S1 mode, the UE shall not consider the modified PDU session as an always-on PDU session; or
  2. otherwise:
    1. if the UE has received the Always-on PDU session indication IE with the value set to "Always-on PDU session required" for this PDU session, the UE shall consider the PDU session as an always-on PDU session; or
    2. otherwise the UE shall not consider the PDU session as an always-on PDU session.
If the PDU SESSION MODIFICATION COMMAND message contains a Port management information container IE, the UE shall forward the contents of the Port management information container IE to the DS-TT (see TS 23.501 and TS 23.502).
If the UE receives a Serving PLMN rate control IE in the PDU SESSION MODIFICATION COMMAND message, the UE shall store the Serving PLMN rate control IE value, replacing any existing value, and use the stored serving PLMN rate control value as the maximum allowed limit of uplink control plane user data for the corresponding PDU session in accordance with TS 23.501.
If the PDU SESSION MODIFICATION COMMAND message includes the Received MBS container IE, for each of the Received MBS informations:
  1. if MBS decision is set to "MBS join is accepted", the UE shall consider that it has successfully joined the MBS session. The UE shall store the received TMGI and shall use it for any further operation on that MBS session. The UE shall store the received MBS service area associated with the received TMGI, if any. The UE may provide the MBS start time if it is included in the Received MBS information to upper layers;
  2. if MBS decision is set to "MBS join is rejected", the UE shall consider the requested join as rejected. The UE shall store the received MBS service area associated with the received TMGI, if any. If the received Rejection cause is set to "User is outside of local MBS service area", the UE shall not request to join the same MBS session if the UE is camping on a cell that is outside the received MBS service area. If the received Rejection cause is set to "MBS session has not started or will not start soon" and an MBS back-off timer value is included with value that indicates neither zero nor deactivated, the UE shall start a back-off timer T35zx with the value provided in the MBS back-off timer value, and shall not attempt to join the same MBS session until the expiry of T35zx;
  3. if the MBS decision is set to "Remove UE from MBS session", the UE shall consider that it has successfully left the MBS session; or
  4. if the MBS decision is set to "MBS service area update", the UE shall store the received MBS service area and replace the current MBS service area with the received one.
If the UE has indicated support for ECS configuration information provisioning and receives one or more ECS IPv4 addresses, ECS IPv6 addresses, ECS FQDNs, or an ECS provider identifier in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, then the UE shall pass the ECS IPv4 address(es), if any, ECS IPv6 address(es), if any, ECS FQDN(s), if any, and the ECS provider identifier, if any, to the upper layers. If the UE receives spatial validity condition along with the ECS IPv4 Address, ECS IPv6 Address, or ECS FQDN respectively in the Extended protocol configuration options IE, then the UE shall pass the spatial validity condition associated with the ECS IPv4 Address, ECS IPv6 Address, or ECS FQDN respectively to the upper layers.
If the UE supports receiving DNS server addresses in protocol configuration options and receives one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them, in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, then the UE shall pass the received DNS server IPv4 address(es), if any, and the received DNS server IPv6 address(es), if any, to upper layers.
If the UE supports the EAS rediscovery and receives:
  1. the EAS rediscovery indication without indicated impact; or
  2. the following:
    1. one or more EAS rediscovery indication(s) with impacted EAS IPv4 address range, if supported by the UE;
    2. one or more EAS rediscovery indication(s) with impacted EAS IPv6 address range, if supported by the UE;
    3. one or more EAS rediscovery indication(s) with impacted EAS FQDN, if supported by the UE; or
    4. any combination of the above;
in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, then the UE shall pass the EAS rediscovery indication and the received impacted EAS IPv4 address range(s), if supported and included, the received EAS IPv6 address range(s), if supported and included, and the received EAS FQDN(s), if supported and included, to upper layers.
Upon receipt of PDU SESSION MODIFICATION COMMAND message, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the Service-level-AA container IE is included and it contains a CAA-level UAV ID and the C2 authorization result, the UE shall replace its currently stored CAA-level UAV ID with the new CAA-level UAV ID.
The UE shall transport the PDU SESSION MODIFICATION COMPLETE message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5.
After sending the PDU SESSION MODIFICATION COMPLETE message, if the "Create new EPS bearer" operation code in the Mapped EPS bearer contexts IE was received in the PDU SESSION MODIFICATION COMMAND message and there is neither a corresponding Authorized QoS flow descriptions IE in the PDU SESSION MODIFICATION COMMAND message nor an existing QoS flow description corresponding to the EPS bearer identity included in the mapped EPS bearer context, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a Mapped EPS bearer contexts IE to delete the mapped EPS bearer context.
After sending the PDU SESSION MODIFICATION COMPLETE message, if for the PDU session being modified, there are mapped EPS bearer context(s) but none of them is associated with the default QoS rule, the UE shall locally delete the mapped EPS bearer context(s) and shall locally delete the stored EPS bearer identity (EBI) in all the QoS flow descriptions of the PDU session, if any.
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 COMPLETE message.
Upon receipt of a PDU SESSION MODIFICATION COMPLETE message, the SMF shall stop timer T3591 and shall consider the PDU session as modified. If the selected SSC mode of the PDU session is "SSC mode 3" and the PDU SESSION MODIFICATION COMMAND message included 5GSM cause #39 "reactivation requested", the SMF shall start timer T3593. If the PDU Session Address Lifetime value is sent to the UE in the PDU SESSION MODIFICATION COMMAND message then timer T3593 shall be started with the same value, otherwise it shall use a default value. If the PDU SESSION MODIFICATION COMPLETE 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.3.2.4  Network-requested PDU session modification procedure not accepted by the UEWord‑p. 486

Upon receipt of a PDU SESSION MODIFICATION COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, if the UE rejects the PDU SESSION MODIFICATION COMMAND message, the UE shall create a PDU SESSION MODIFICATION COMMAND REJECT message.
If the PDU SESSION MODIFICATION COMMAND message contains the PTI value allocated in the UE-requested PDU session modification procedure, the UE shall stop the timer T3581. The UE should ensure that the PTI value assigned to this procedure is not released immediately.
While the PTI value is not released, the UE regards any received PDU SESSION MODIFICATION COMMAND message with the same PTI value as a network retransmission (see subclause 7.3.1).
The UE shall set the 5GSM cause IE of the PDU SESSION MODIFICATION COMMAND REJECT message to indicate the reason for rejecting the PDU session modification.
The 5GSM cause IE typically indicates one of the following 5GSM cause values:
#26
insufficient resources;
#44
semantic error in packet filter(s);
#45
syntactical error in packet filter(s);
#83
semantic error in the QoS operation; or
#84
syntactical error in the QoS operation.
If the selected SSC mode of the PDU session is "SSC mode 3" and the PDU SESSION MODIFICATION COMMAND messages includes 5GSM cause #39 "reactivation requested", while the UE does not have sufficient resources for initiating the PDU session establishment procedure as specified in subclause 6.4.1 then the UE shall set cause IE to #26 "insufficient resources".
If the PDU SESSION MODIFICATION COMMAND message includes a request to add a new authorized QoS rule, or a request to modify the authorized QoS rules, or both, and the UE decides to reject the request due to e.g. the supported number of authorized QoS rules or number of packet filters associated with a PDU session having reached the maximum number, then the UE shall set the 5GSM cause IE to #26 "insufficient resources".
If the PDU SESSION MODIFICATION COMMAND message includes a request to add a new authorized QoS flow description, or a request to modify the authorized QoS flow descriptions, or both and the UE decides to reject the request due to e.g. the supported number of authorized QoS flow descriptions, then the UE shall set the 5GSM cause IE to #26 "insufficient resources".
If the PDU SESSION MODIFICATION COMMAND message includes the Authorized QoS rules IE, the UE shall process the QoS rules sequentially starting with the first QoS rule. The UE shall check the QoS rule and the QoS flow description provided in the PDU SESSION MODIFICATION COMMAND message for different types of errors as follows:
  1. Semantic errors in QoS operations:
    1. When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on the default QoS rule and the DQR bit is set to "the QoS rule is not the default QoS rule".
    2. When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on a QoS rule which is not the default QoS rule and the DQR bit is set to "the QoS rule is the default QoS rule".
    3. When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule with different QoS rule identifier.
    4. When the rule operation is "Delete existing QoS rule" on the default QoS rule.
    5. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters ", or "Modify existing QoS rule without modifying packet filters" and two or more QoS rules associated with this PDU session would have identical precedence values, and the UE is not in NB-N1 mode.
    6. When the rule operation is "Modify existing QoS rule and delete packet filters", the QoS rule is a QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the resultant QoS rule is empty.
    7. When the rule operation is "Create new QoS rule", there is already an existing QoS rule with the same QoS rule identifier and the UE is not in NB-N1 mode.
    8. When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters", the associated QoS rule does not exist and the UE is not in NB-N1 mode.
    9. When the rule operation is different than "Delete existing QoS rule", the DQR bit of the QoS rule is set to "the QoS rule is not the default QoS rule" and the UE is in NB-N1 mode.
    10. When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", and the PDU session type of the PDU session is "Unstructured".
    11. When the rule operation is "Delete existing QoS rule" and there is no existing QoS rule with the same QoS rule identifier.
    12. When the flow description operation is "Create new QoS flow description", there is already an existing QoS flow description with the same QoS flow identifier and the UE is not in NB-N1 mode.
    13. When the flow description operation is "Modify existing QoS flow description", the associated QoS flow description does not exist and the UE is not in NB-N1 mode.
    14. When the flow description operation is "Delete existing QoS flow description" and there is no existing QoS flow description with the same QoS flow identifier.
    15. When the flow description operation is different than "Delete existing QoS flow description", the QFI is not the same as the QFI of the default QoS rule and the UE is in NB-N1 mode.
    16. When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule, and the PDU session type of the PDU session is "Unstructured".
    17. When the rule operation is "Modify existing QoS rule and add packet filters", the "packet filter list" field contains a match-all packet filter, the resultant QoS rule is the default QoS rule and there is already an existing match-all packet filter associated with the default QoS rule.
    18. When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is not the default QoS rule", or the rule operation is "Modify existing QoS rule and add packet filters" on a QoS rule which is not the default QoS rule or "Modify existing QoS rule and replace all packet filters" on a QoS rule which is not the default QoS rule, and one match-all packet filter is to be associated with the resultant QoS rule.
    In case 4, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation".
    In case 5, if the old QoS rule (i.e. the QoS rule that existed before the PDU SESSION MODIFICATION COMMAND message was received) is not the default QoS rule, the UE shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old QoS rule which has identical precedence value. Furthermore, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS rule.
    In case 5, if the old QoS rule (i.e. the QoS rule that existed before the PDU SESSION MODIFICATION COMMAND message was received) is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation".
    In case 6, if the QoS rule is not the default QoS rule, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS rule.
    In case 6, if the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation".
    In case 7, if the existing QoS rule is not the default QoS rule and the DQR bit of the new QoS rule is set to "the QoS rule is not the default QoS rule", the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS rule. If the existing QoS rule is the default QoS rule or the DQR bit of the new QoS rule is set to "the QoS rule is the default QoS rule", the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #83 "semantic error in the QoS operation".
    In case 9 or case 10, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS rule.
    In case 11, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS rule as successfully deleted.
    In case 12, the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS flow description.
    In case 14, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS flow description as successfully deleted.
    In case 15 or case 16, after sending the PDU SESSSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS flow description.
    Otherwise, the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #83 "semantic error in the QoS operation".
  2. Syntactical errors in QoS operations:
    1. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters" or "Modify existing QoS rule and delete packet filters", the PDU session type of the PDU session is IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the QoS rule is empty.
    2. When the rule operation is "Delete existing QoS rule" or "Modify existing QoS rule without modifying packet filters" with a non-empty packet filter list in the QoS rule.
    3. When the rule operation is "Modify existing QoS rule and delete packet filters" and the packet filter to be deleted does not exist in the original QoS rule.
    4. Void.
    5. When there are other types of syntactical errors in the coding of the Authorized QoS rules IE or the Authorized QoS flow descriptions IE, such as: a mismatch between the number of packet filters subfield and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned", or the QoS flow identifier is set to "no QoS flow identifier assigned".
    6. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters", the DQR bit is set to "the QoS rule is the default QoS rule", the PDU session type of the PDU session is "Unstructured", and the packet filter list in the QoS rule is not empty.
    7. When, the
      1. rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters", there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule and the UE determines that there is a resulting QoS rule for a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1).
      2. flow description operation is "Delete existing QoS flow description", and the UE determines, by using the QoS rule's QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1) with a QFI corresponding to the QFI of the QoS flow description that is deleted (i.e. there is no associated QoS flow description with the same QFI).
    8. When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in TS 23.501 Table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI,
    In case 3 the UE shall not diagnose an error, further process the deletion request and, if no error according to items c and d was detected, consider the respective packet filter as successfully deleted.
    In case 6, after completion of the PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #84 "syntactical error in the QoS operations" to delete all the packet filters for the default QoS rule.
    In case 7, if the Authorized QoS rules IE contains at least one other valid QoS rule, the UE shall not diagnose an error and shall further process the request, if no error according to items c and d was detected. After completion of the PDU session modification procedure, the UE shall delete the QoS rule for which no corresponding QoS flow description is available and initiate UE-requested PDU session modification procedure with 5GSM cause #84 "syntactical error in the QoS operation" to delete the QoS rule for which it has deleted.
    In case 8, if the default QoS rule is associated with the QoS flow description which lacks at least one of the mandatory parameters, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #84 "syntactical error in the QoS operation". Otherwise, if the Authorized QoS rules IE contains at least one other valid QoS rule or the QoS flow description IE contains at least one other valid QoS flow description, the UE shall not diagnose an error and shall further process the request, if no error according to items c and d was detected. After completion of the PDU session modification procedure, the UE shall delete the QoS flow description which lacks at least one of the mandatory parameters and the associated QoS rule(s), if any, and initiate UE-requested PDU session modification procedure with 5GSM cause #84 "syntactical error in the QoS operation" to delete the QoS flow description and the associated QoS rule(s), if any, which it has deleted.
    Otherwise the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #84 "syntactical error in the QoS operation".
  3. Semantic errors in packet filters:
    1. When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document.
    The UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #44 "semantic error in packet filter(s)".
  4. Syntactical errors in packet filters:
    1. When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters", and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers.
    2. When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier.
    In case 1, if two or more packet filters with identical packet filter identifiers are contained in the PDU SESSION MODIFICATION COMMAND message, the UE shall reject the PDU SESSION MODIFICATION COMMAND with 5GSM cause #45 "syntactical errors in packet filter(s)". Otherwise, the UE shall not diagnose an error, further process the PDU SESSION MODIFICATION COMMAND message and, if it was processed successfully, replace the old packet filter with the new packet filter which have the identical packet filter identifiers.
    Otherwise the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #45 "syntactical errors in packet filter(s)".
If:
  1. the UE detects errors in QoS rules that require to delete at least one QoS rule as described above which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts; and
  2. optionally, if the UE detects different errors in the mapped EPS bearer contexts as described in subclause 6.3.2.3 which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous QoS rules;
the UE, after sending the PDU SESSSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, may send a single PDU SESSION MODIFICATION REQUEST message to delete the erroneous QoS rules, and optionally to delete the erroneous mapped EPS bearer contexts. The UE shall include a 5GSM cause IE in the PDU SESSION MODIFICATION REQUEST message.
The UE shall transport the PDU SESSION MODIFICATION COMMAND REJECT message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5.
Upon receipt of a PDU SESSION MODIFICATION COMMAND REJECT message with 5GSM cause value in state PDU SESSION MODIFICATION PENDING, the SMF shall stop timer T3591, enter the state PDU SESSION ACTIVE and abort the PDU session modification procedure.
Up

6.3.2.5  Abnormal cases on the network sideWord‑p. 490

The following abnormal cases can be identified:
  1. Expiry of timer T3591.
    On the first expiry of the timer T3591, the SMF shall resend the PDU SESSION MODIFICATION COMMAND message and shall reset and restart timer T3591. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3591, the SMF shall abort the procedure and enter the state PDU SESSION ACTIVE.
    The SMF may continue to use the previous configuration of the PDU session or initiate the network-requested PDU session release procedure. If the SMF decides to continue to use the previous configuration of the PDU session and
    1. the Authorized QoS rules IE is included in the PDU SESSION MODIFICATION COMMAND message, the SMF may mark the corresponding authorized QoS rule(s) of the PDU session as to be synchronised with the UE; and
    2. the Authorized QoS flow descriptions IE is included in the PDU SESSION MODIFICATION COMMAND message, the SMF may mark the corresponding authorized QoS flow description(s) of the PDU session as to be synchronised with the UE.
  2. Void.
  3. Collision of UE-requested PDU session release procedure and network-requested PDU session modification procedure.
    If the SMF receives a PDU SESSION RELEASE REQUEST message during the network-requested PDU session modification procedure, and the PDU session indicated in the PDU SESSION RELEASE REQUEST message is the PDU session that the SMF had requested to modify, the SMF shall abort the PDU session modification procedure and proceed with the UE-requested PDU session release procedure.
  4. Collision of UE-requested PDU session modification procedure and network-requested PDU session modification procedure.
    If the network receives a PDU SESSION MODIFICATION REQUEST message during the network-requested PDU session modification procedure, and the PDU session indicated in the PDU SESSION MODIFICATION REQUEST message is the PDU session that the network had requested to modify, the network shall ignore the PDU SESSION MODIFICATION REQUEST message received in the state PDU SESSION MODIFICATION PENDING. The network shall proceed with the network-requested PDU session modification procedure as if no PDU SESSION MODIFICATION REQUEST message was received from the UE.
  5. 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, then the SMF shall abort the procedure and enter the state PDU SESSION ACTIVE.
  6. 5G access network cannot forward the message due to handover.
    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 handover, then the SMF shall abort the procedure and enter the state PDU SESSION ACTIVE.
    The SMF may re-initiate, up to a pre-configured number of times, the network-requested PDU session modification procedure when the SMF detects that the handover is completed successfully or has failed or at the expiry of the configured guard timer as specified in TS 23.502.
  7. Collision of re-establishment of the user-plane resources and network-requested PDU session modification procedure for the same PDU session.
    If the SMF receives an indication from the AMF to re-establish the user-plane resources during the network-requested PDU session modification procedure for the same PDU session, the network shall abort the network-requested PDU session modification procedure and proceed with re-establishment of the user-plane resources for the PDU session as specified in TS 29.502, subclause 5.2.2.3.2.2.
  8. Collision of UE-requested PDU session establishment procedure and network-requested PDU session modification procedure.
    If the network receives a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing PDU session" or "existing emergency PDU session" during the network-requested PDU session modification procedure, and the PDU session ID indicated in the PDU SESSION ESTABLISHMENT REQUEST message is the PDU session that the network had requested to modify, the network shall abort the network-requested PDU session modification procedure and proceed with the UE-requested PDU session establishment procedure.
Up

6.3.2.6  Abnormal cases in the UEWord‑p. 492

The following abnormal cases can be identified:
  1. PDU session inactive for the received PDU session ID.
    If the PDU session ID in the PDU SESSION MODIFICATION COMMAND message belongs to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall set the 5GSM cause IE to #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.
  2. Collision of network-requested PDU session modification procedure and UE-requested PDU session modification procedure.
    If the UE receives a PDU SESSION MODIFICATION COMMAND message during the UE-requested PDU session modification procedure, the PTI IE of the PDU SESSION MODIFICATION COMMAND message is set to "No procedure transaction identity assigned", and the PDU session indicated in the PDU SESSION MODIFICATION COMMAND message is the PDU session that the UE had requested to modify, the UE shall abort internally the UE-requested PDU session modification procedure, enter the state PDU SESSION ACTIVE and proceed with the network-requested PDU session modification procedure.
Up

Up   Top   ToC