4.3.3 PDU Session Modification

23.5023GPPProcedures for the 5G System (5GS)Release 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.3.3.1 General

The procedure is used when one or several of the QoS parameters exchanged between the UE and the network are modified and/or to send updated ECS Address Configuration Information as defined in clause 6.5.2 of TS 23.548 [74] to the UE and/or to send the updated DNS server address as defined in clause 6.2.3.2.3 of TS 23.548 [74].

NOTE 1: The conditions when to use this procedure for QoS change as well as the QoS parameters exchanged between the UE and the network are defined in clause 5.7 of TS 23.501 [2].

NOTE 2: The conditions when to use this procedure for the exchange of ECS Address Configuration Information are described in clause 6.5.2 of TS 23.548 [74].

NOTE 3: The conditions when to use this procedure for the update of DNS server address are described in clause 6.2.3.2.3 of TS 23.548 [74].

4.3.3.2 UE or network requested PDU Session Modification (non-roaming and roaming with local breakout)

The UE or network requested PDU Session Modification procedure (non-roaming and roaming with local breakout scenario) is depicted in figure 4.3.3.2-1.

Figure 4.3.3.2-1: UE or network requested PDU Session Modification (for non-roaming and roaming with local breakout)

1. The procedure may be triggered by following events:

1a. (UE initiated modification) The UE initiates the PDU Session Modification procedure by the transmission of an NAS message (N1 SM container (PDU Session Modification Request (PDU session ID, Packet Filters, Operation, Requested QoS, Segregation, 5GSM Core Network Capability, Number Of Packet Filters, [Always-on PDU Session Requested])), PDU Session ID, UE Integrity Protection Maximum Data Rate, [Port Management Information Container]) message. Depending on the Access Type, if the UE was in CM-IDLE state, this SM-NAS message is preceded by the Service Request procedure. The NAS message is forwarded by the (R)AN to the AMF with an indication of User location Information. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N1 SM container (PDU Session Modification Request)).

When the UE requests specific QoS handling for selected SDF(s), the PDU Session Modification Request includes Packet Filters describing the SDF(s), the requested Packet Filter Operation (add, modify, delete) on the indicated Packet Filters, the Requested QoS and optionally a Segregation indication. The Segregation indication is included when the UE recommends to the network to bind the applicable SDF(s) on a distinct and dedicated QoS Flow e.g. even if an existing QoS Flow can support the requested QoS. The network should abide by the UE request, but is allowed to proceed instead with binding the selected SDF(s) on an existing QoS Flow.

NOTE 1: Only one QoS Flow is used for traffic segregation. If UE makes subsequent requests for segregation of additional SDF(s), the additional SDF(s) are multiplexed on the existing QoS Flow that is used for segregation.

The UE shall not trigger a PDU Session Modification procedure for a PDU Session corresponding to a LADN when the UE is outside the area of availability of the LADN.

The PS Data Off status, if changed, shall be included in the PCO in the PDU Session Modification Request message.

For a PDU Session which was established in the EPS, when the UE moves from EPS to 5GS for the first time, the UE includes an Always-on PDU Session Requested indication in the PDU Session Modification Request message if it wants to change the PDU Session to an always-on PDU Session.

When PCF is deployed, the SMF shall further report the PS Data Off status to PCF if the PS Data Off event trigger is provisioned, the additional behaviour of SMF and PCF for 3GPP PS Data Off is defined in TS 23.503 [20].

The 5GSM Core Network Capability is provided by the UE and handled by SMF as defined in clause 5.4.4b of TS 23.501 [2].

The UE Integrity Protection Maximum Data Rate indicates the maximum data rate up to which the UE can support UP integrity protection. It is set as defined in TS 23.501 [2].

The Number Of Packet Filters indicates the number of supported packet filters for signalled QoS rules as described in clause 5.17.2.2.2 of TS 23.501 [2].

When it moves from EPS to 5GS for the first time, a UE that supports EAS re-discovery as described in clause 6.2.3.3 of TS 23.548 [74], may indicate so in the PCO.

When it moves from EPS to 5GS for the first time, a UE that hosts the EDC functionality shall indicate in the PCO its capability to support the EDC functionality (see clause 5.2.1 of TS 23.548 [74]).

Port Management Information Container is received from DS-TT and includes DS-TT port related management information as defined in clause 5.28.3 of TS 23.501 [2].

1b. (PCF initiated SM Policy Association Modification) The PCF performs a PCF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.2 to notify SMF about the modification of policies. This may e.g. have been triggered by a policy decision or upon AF requests, e.g. Application Function influence on traffic routing as described in step 5 in clause 4.3.6.2 or AF to provide Port management information Container.

If the QoS Monitoring for URLLC is requested by the AF, the PCF generates the QoS Monitoring policy for the corresponding service data flow and provides the policy in the PCC rules to the SMF in this step.

1c. (SMF requested modification) The UDM updates the subscription data of SMF by Nudm_SDM_Notification (SUPI, Session Management Subscription Data). The SMF updates the Session Management Subscription Data and acknowledges the UDM by returning an Ack with (SUPI).

1d. (SMF requested modification) The SMF may decide to modify PDU Session. This procedure also may be triggered based on locally configured policy or triggered from the (R)AN (see clause 4.2.6 and clause 4.9.1). It may also be triggered if the UP connection is activated (as described in Service Request procedure) and the SMF has marked that the status of one or more QoS Flows are deleted in the 5GC but not synchronized with the UE yet.

If interworking with TSN deployed in the transport network is supported and either the UPF supports CN-TL or NG-RAN supports AN-TL (see clause 4.4.8 of TS 23.501 [2]), the procedure may be triggered due to reception of Status group from TN CNC.

The SMF may decide to modify PDU Session to send updated ECS Address Configuration Information to the UE as defined in clause 6.5.2 of TS 23.548 [74].

The SMF may decide to modify PDU Session to send updated DNS server address to the UE as defined in clause 6.2.3.2.3 of TS 23.548 [74].

The SMF may decide to modify PDU Session to send the EAS rediscovery indication to the UE as defined in clause 6.2.3.3 of TS 23.548 [74].

If the SMF receives one of the triggers in step 1b ~ 1d, the SMF starts SMF requested PDU Session Modification procedure.

1e. (AN initiated modification) (R)AN shall indicate to the SMF when the AN resources onto which a QoS Flow is mapped are released irrespective of whether notification control is configured. (R)AN sends the N2 message (PDU Session ID, N2 SM information) to the AMF. The N2 SM information includes the QFI, User location Information and an indication that the QoS Flow is released. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N2 SM information).

(AN initiated notification control) If notification control is configured for a GBR QoS Flow, (R)AN sends a N2 message (PDU Session ID, N2 SM information) to SMF when the (R)AN decides the QoS targets of the QoS Flow cannot be fulfilled or can be fulfilled again, respectively. The N2 SM information includes the QFI and an indication that the QoS targets for that QoS Flow cannot be fulfilled or can be fulfilled again, respectively. When QoS targets cannot be fulfilled, the N2 SM information indicates a reference to the Alternative QoS Profile matching the values of the QoS parameters that the NG-RAN is currently fulfilling as specified in clause 5.7.2.4 of TS 23.501 [2]. If the QoS Flow has a TSCAI including Capability for BAT adaptation and without Burst Arrival Time, the N2 SM information can also include a BAT offset as described in clause 5.27.2.5 of TS 23.501 [2]. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N2 SM information). If the PCF has subscribed to the event, SMF reports this event to the PCF for each PCC Rule for which notification control is set in step 2.

1f. (AMF initiated modification) If the UE supports CE mode B and use of CE mode changes from restricted to unrestricted or vice versa in the Enhanced Coverage Restriction information in the UE context in the AMF and the UE has already established PDU sessions, then the AMF shall trigger a PDU session modification to the SMFs serving the UE’s PDU sessions when the AMF determines that NAS-SM timer shall be updated due to the change of Enhanced Coverage Restriction and include the extended NAS-SM indication only if use of CE mode B is now unrestricted in the Enhanced Coverage Restriction information in the UE context in the AMF.

If the AMF, based on configuration, is aware that the UE is accessing over a gNB using GEO satellite backhaul and GEO Satellite ID needs to be updated to the SMF, the AMF may, based on configuration, include the latest GEO Satellite ID as described in clause 5.43.2 of TS 23.501 [2].

1g. (AMF initiated modification) the AMF informs the SMF of updates of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s). Also, If the PCF request notification of SM Policy Association and there is any PDU Session established to that DNN, S-NSSAI [PCF binding information, notification of SM Policy Association establishment Indication].

Based on the extended NAS-SM timer indication, the SMF shall use the extended NAS-SM timer setting for the UE as specified in TS 24.501 [25].

2. The SMF may need to report some subscribed event to the PCF by performing an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1. This step may be skipped if PDU Session Modification procedure is triggered by step 1b or 1d. If dynamic PCC is not deployed, the SMF may apply local policy to decide whether to change the QoS profile.

Steps 2a to 7 are not invoked when the PDU Session Modification requires only action at a UPF (e.g. gating).

2a. The SMF may update the UPF with N4 Rules related to new or modified QoS Flow(s).

NOTE 2: This allows the UL packets with the QFI of a new or modified QoS Flow to be transferred.

If the SMF initiated the PDU Session Modification procedure in step 1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with a TSC Assistance Container, and if interworking with TSN deployed in the transport network is supported and the UPF does not support CN-TL, the SMF instructs the UPF to assign a distinct N3 tunnel end point address for the QoS Flow(s) assigned with a TSC Assistance Container.

If the SMF initiated the PDU Session Modification procedure in step 1d due to reception of Status group from TN CNC, the SMF includes a TL-Container with a set-request to the N4 Session Modification request that is sent to the UPF, as described in clause 5.28a.2 of TS 23.501 [2].

If redundant transmission has not been activated to the PDU session and the SMF decides to perform redundant transmission for the QoS Flow, the SMF indicates to the UPF to perform packet duplication and elimination for the QoS Flow.

If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission, the SMF indicates the UPF to release the CN Tunnel Info which is used as the redundancy tunnel of the PDU Session and also indicates the UPF to stop packet duplication and elimination for the corresponding QoS Flow(s).

NOTE 3: The method to perform elimination and reordering on RAN/UPF based on the packets received from the two GTP-U tunnels is up to RAN/UPF implementation. The two GTP-U tunnels are terminated at the same RAN node and UPF.

If redundant transmission has not been activated to the PDU Session and the SMF decides to perform redundant transmission for the QoS Flow with two I-UPFs between the PSA UPF and the NG-RAN, the SMF sends a N4 Session Establishment Request message to the I-UPFs including UL CN Tunnel Info of the PSA UPF and a request to allocate CN Tunnel Info.

SMF may make use of Redundant Transmission Experience analytics provided by NWDAF, when SMF takes a decision whether to perform redundant transmission, or stop redundant transmission if it had been activated, as described in clause 6.13 of TS 23.288 [50].

2b. The UPF(s) respond to the SMF. If redundant transmission has not been activated to the PDU session and the SMF indicated the UPF to perform packet duplication and elimination for the QoS Flow in step 2a, the UPF allocates an additional CN Tunnel Info. The additional CN Tunnel Info is provided to the SMF.

If redundant transmission has not been activated to the PDU Session and the SMF decides to perform redundant transmission for the QoS Flow with two I-UPFs in step 2a, the UPFs allocate CN Tunnel Info. The CN Tunnel Info of each I-UPF is provided to the SMF.

If interworking with TSN deployed in the transport network is supported and the UPF supports CN-TL and received a TL-Container with a set-request from the SMF/CUC in step 2a (see clause 4.4.8 of TS 23.501 [2]), the UPF/CN-TL includes a TL-Container with a set-response to the N4 Session Modification response, as described in clause 5.28a.2 of TS 23.501 [2].

3a. For UE or AN initiated modification, the SMF responds to the AMF through Nsmf_PDUSession_UpdateSMContext Response ([N2 SM information (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR], [CN Tunnel Info(s)]), N1 SM container (PDU Session Modification Command (PDU Session ID, QoS rule(s), QoS rule operation, QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), Session-AMBR, [Always-on PDU Session Granted], [Port Management Information Container]))). See clause 5.7 of TS 23.501 [2] for the QoS Profile, Alternative QoS Profile and QoS rule and QoS Flow level QoS parameters. Alternative QoS Profile is only valid for AN initiated modification.

If the PDU Session Modification was requested by the UE to modify a PDU Session to an always-on PDU Session, the SMF shall include an Always-on PDU Session Granted indication in the PDU Session Modification Command to indicate whether the PDU Session is to be changed to an always-on PDU Session or not via the Always-on PDU Session Granted indication in the PDU Session Modification Command.

The N2 SM information carries information that the AMF shall provide to the (R)AN. It may include the QoS profiles and the corresponding QFIs to notify the (R)AN that one or more QoS flows were added, or modified. It may include only QFI(s) to notify the (R)AN that one or more QoS flows were removed. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decides to activate redundant transmission in step 2a, the SMF includes the allocated additional CN Tunnel Info in the N2 SM information. If the SMF decides to perform redundant transmission for new QoS Flow with two I-UPFs in step 2a, the SMF includes the allocated CN Tunnel Info of the two I-UPFs in the N2 SM information. If the PDU Session Modification was triggered by the (R)AN Release in step 1e the N2 SM information carries an acknowledgement of the (R)AN Release. If the PDU Session Modification was requested by the UE for a PDU Session that has no established User Plane resources, the N2 SM information provided to the (R)AN includes information for establishment of User Plane resources.

If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission in step 2a, the SMF indicates the (R)AN to release the AN Tunnel and stop packet duplication and elimination associated with the redundancy tunnel of the PDU Session.

The N1 SM container carries the PDU Session Modification Command that the AMF shall provide to the UE. It may include the QoS rules, QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) and corresponding QoS rule operation and QoS Flow level QoS parameters operation to notify the UE that one or more QoS rules were added, removed or modified.

If port number and a Port Management Information Container have been received from PCF in Step 2 and the port number matches the port number assigned for the DS-TT port for this PDU session, then SMF includes the Port Management Information Container in the N1 SM container.

The SMF may need to send transparently through NG-RAN the PDU Session Modification Command to inform the UE about changes in the QoS parameters (i.e. 5QI, GFBR, MFBR) that the NG-RAN is currently fulfilling after the SMF receives QoS Notification Control as defined in clause 5.7.2.4 of TS 23.501 [2]. When the SMF sends on the PDU Session Modification Command transparently through NG-RAN, the N2 SM information is not included as part of the Namf_Communication_N1N2MessageTransfer.

If the UE indicated in the PCO that it supports the EDC functionality, the SMF may indicate to the UE either that the use of the EDC functionality is allowed for the PDU Session or that the use of the EDC functionality is required for the PDU Session (see clause 5.2.1 of TS 23.548 [74]).

3b. For SMF requested modification, the SMF invokes Namf_Communication_N1N2MessageTransfer ([N2 SM information] (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR, [CN Tunnel Info(s)], QoS Monitoring indication, QoS Monitoring reporting frequency, [TSCAI(s)], TL-Container), N1 SM container (PDU Session Modification Command (PDU Session ID, QoS rule(s), QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), QoS rule operation and QoS Flow level QoS parameters operation, Session-AMBR))).

If the SMF initiated the PDU Session Modification procedure in step 1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with a TSC Assistance Container and if interworking with TSN deployed in the transport network is supported and the NG-RAN does not support AN-TL, the SMF instructs the NG-RAN to assign a distinct N3 tunnel end point address for the QoS Flow(s) assigned with a TSC Assistance Container.

The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decides to activate redundant transmission in step 2a, the SMF includes the allocated additional CN Tunnel Info in the N2 SM information. If the SMF decides to perform redundant transmission for new QoS Flow with two I-UPFs in step 2a, the SMF includes the allocated CN Tunnel Info of the two I-UPFs in the N2 SM information.

The SMF indicates the request for QoS Monitoring for the QoS Flow according to the information received from the PCF in step 1b, or based on SMF local policy, e.g. when the RAN rejected the creation of a specific QoS Flow for URLLC. In the case of receiving the QoS Monitoring indication, the RAN enables the RAN part of UL/DL packet delay measurement for the QoS Flow and the QoS Monitoring reporting frequency is used by RAN to determine the packet delay measurement frequency of the RAN part. The TSCAI is defined in clause 5.27.2 of TS 23.501 [2].

If the SMF initiated the PDU Session Modification procedure in step 1d due to reception of Status group from TN CNC, the SMF includes a TL-Container with a set-request to the N2 SM information, as described in clause 5.28a.2 of TS 23.501 [2].

If the UE is in CM-IDLE state and an ATC is activated, the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer and steps 4, 5, 6 and 7 are skipped. When the UE is reachable e.g. when the UE enters CM-CONNECTED state, the AMF forwards the N1 message to synchronize the UE context with the UE.

3c. For SMF requested modification due to updated SMF-Associated parameters from the UDM, the SMF may provide the SMF derived CN assisted RAN parameters tuning to the AMF. The SMF invokes Nsmf_PDUSession_SMContextStatusNotify (SMF derived CN assisted RAN parameters tuning) towards the AMF. The AMF stores the SMF derived CN assisted RAN parameters tuning in the associated PDU Session context for this UE.

3d. For SMF requested modification due to updated NWDAF ID, the SMF informs the AMF of updates of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s).

4. The AMF may send N2 ([N2 SM information received from SMF], NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command))) Message to the (R)AN.

5. The (R)AN may issue AN specific signalling exchange with the UE that is related with the information received from SMF. For example, in the case of a NG-RAN, an RRC Connection Reconfiguration may take place with the UE modifying the necessary (R)AN resources related to the PDU Session or if only N1 SM container is received in step 4 from AMF, RAN transports only the N1 SM container to the UE.

The (R)AN may consider the updated CN assisted RAN parameters tuning to reconfigure the AS parameters.

As part of this, the N1 SM container is provided to the UE. If the N1 SM container includes a Port Management Information Container then the UE provides the container to DS-TT.

If new DNS server address is provided to the UE in the PCO, the UE can refresh all EAS(s) information (e.g. DNS cache) bound to the PDU Session, based on UE implementation as described in clause 6.2.3.2.3 of TS 23.548 [74].

6. The (R)AN may acknowledge N2 PDU Session Request by sending a N2 PDU Session Ack (N2 SM information (List of accepted/rejected QFI(s), AN Tunnel Info, PDU Session ID, Secondary RAT usage data, TL-Container), User location Information) Message to the AMF. In the case of Dual Connectivity, if one or more QFIs were added to the PDU Session, the Master RAN node may assign one or more of these QFIs to a NG-RAN node which was not involved in the PDU Session earlier. In this case the AN Tunnel Info includes a new N3 tunnel endpoint for QFIs assigned to the new NG-RAN node. Correspondingly, if one or more QFIs were removed from the PDU Session, a (R)AN node may no longer be involved in the PDU Session anymore and the corresponding tunnel endpoint is removed from the AN Tunnel Info. The NG-RAN may reject QFI(s) if it cannot fulfil the User Plane Security Enforcement information for a corresponding QoS Profile, e.g. due to the UE Integrity Protection Maximum Data Rate being exceeded. When receiving the request for QoS Monitoring, the (R)AN may indicate its rejection to perform QoS Monitoring, e.g. due to the (R)AN load condition. The (R)AN may reject the addition or modification of a QoS Flow, e.g. due to handling of the UE-Slice-MBR as described in clause 5.7.1.10 of TS 23.501 [2]. If the (R)AN rejects the addition or modification of a QoS Flow, the SMF is responsible of updating the QoS rules and QoS Flow level QoS parameters associated to that QoS Flow in the UE accordingly.

If the PLMN has configured secondary RAT usage reporting, the NG-RAN node may provide RAN Usage Data Report. The User Location Information shall include the serving cell’s ID and, if Dual Connectivity is activated for the UE, the PSCell ID.

If the redundant transmission has not been activated to the PDU session and the SMF indicates to the RAN that one of the QoS Flow shall perform redundant transmission, the RAN includes an additional AN tunnel info in N2 SM information.

If interworking with TSN deployed in the transport network is supported and the NG-RAN supports AN-TL and received a TL-Container with a set-request from the SM/CUC in step 3b (see clause 4.4.8 of TS 23.501 [2]), the NG-RAN/AN-TL includes a TL-Container with a set-response to the N2 SM information, as described in clause 5.28a.2 of TS 23.501 [2].

7. The AMF forwards the N2 SM information and the User location Information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation. The SMF replies with a Nsmf_PDUSession_UpdateSMContext Response.

If the N2 SM information indicates failure of whole N2 SM request (i.e. no part of the N2 SM request is successful in (R)AN), the SMF assumes that the NAS PDU, if provided in step 3, was not forwarded by NG-RAN to UE, as described in TS 38.413 [10]. In this case, if the PDU Session modification is UE triggered the SMF shall reject the PDU session modification by including a N1 SM container with a PDU Session Modification Reject message (see clause 8.3.3 of TS 24.501 [25]) in the Nsmf_PDUSession_UpdateSMContext Response in step 7b. Step 8 is skipped in this case.

Otherwise, the SMF assumes that the NAS PDU was sent to UE successfully. If the (R)AN rejects QFI(s), the SMF is responsible of updating the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE accordingly, i.e. the SMF shall trigger a separate NAS PDU Session Modification procedure after step 11 to align the SM context of this PDU Session in UE.

8. The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by sending N4 Session Modification Request message to the UPF (see NOTE 3).

The SMF may update the UPF with N4 Rules related to new, modified or removed QoS Flow(s), unless it was done already in step 2a.

NOTE 4: This allows the DL packets of the new or modified QoS Flow to be transferred.

If an additional AN Tunnel Info is returned by RAN in step 6, the SMF informs the UPF about this AN Tunnel Info for redundant transmission. In the case of redundant transmission with two I-UPFs, the SMF provides AN Tunnel Info to two I-UPFs. If CN Tunnel Info of two I-UPFs is allocated by the UPFs in step 2b, the SMF also provides the DL CN Tunnel Info of two I-UPFs to the UPF (PSA).

If the QoS Monitoring for URLLC is enabled for the QoS Flow, the SMF provides the N4 rules containing the QoS Monitoring policy generated according to the information received in step 1b to the UPF via the N4 Session Modification Request message.

If port number and a Port Management Information Container have been received from PCF in Step 2 and the port number matches the port number of the NW-TT port for this PDU session, then SMF includes the Port Management Information Container in the N4 Session Modification Request. If the N4 Session Modification Request includes a Port Management Information Container, then UPF also includes a Port Management Information Container in the N4 Session Modification Response.

9. The UE acknowledges the PDU Session Modification Command by sending a NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command Ack, [Port Management Information Container])) message.

10. The (R)AN forwards the NAS message to the AMF.

11. The AMF forwards the N1 SM container (PDU Session Modification Command Ack) and User Location Information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation. The SMF replies with a Nsmf_PDUSession_UpdateSMContext Response.

If the SMF initiated modification is to delete QoS Flows (e.g. triggered by PCF) which do not include QoS Flow associated with the default QoS rule and the SMF does not receive response from the UE, the SMF marks that the status of those QoS Flows is to be synchronized with the UE.

If interworking with TSN deployed in the transport network is supported, for any QoS Flow including a TSC Assistance Container, the SMF/CUC derives the merged stream requirements as described in Annex M of TS 23.501 [2]. If AN-TL and CN-TL are supported, the SMF/CUC uses the get-responses stored during the PDU Session Establishment procedure to derive the merged stream requirements. The SMF/CUC interacts with the CNC deployed in the transport network and provides the merged stream requirements in the Talker and Listener groups to the TN CNC. The TN CNC uses the merged stream requirements as input to select respective path(s) and calculate schedules in TN.

Based on the results, the TN CNC provides a Status group that contains the merged end station communication-configuration back to the SMF/CUC.

12. The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by sending N4 Session Modification Request (N4 Session ID) message to the UPF. For a PDU Session of Ethernet PDU Session Type, the SMF may notify the UPF to add or remove Ethernet Packet Filter Set(s) and forwarding rule(s).

NOTE 5: The UPFs that are impacted in the PDU Session Modification procedure depends on the modified QoS parameters and on the deployment. For example in the case of the session AMBR of a PDU Session with an UL CL changes, only the UL CL is involved. This note also applies to the step 8.

13. If the SMF interacted with the PCF in step 1b or 2, the SMF notifies the PCF whether the PCC decision could be enforced or not by performing an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1. If the trigger for 5GS Bridge information available is armed and the SMF received a Port Management Information Container from either UE or UPF, then SMF provides the Port Management Information Container and the port number of the related port to the PCF in this step, as described in clause 5.28.3.2 of TS 23.501 [2]. If the trigger for 5GS Bridge information available is armed and the SMF received the User Plane node Management Information Container from UPF, then the SMF provides the User Plane node Management Information Container to the PCF as described in clause 5.28.3.2 of TS 23.501 [2].

SMF notifies any entity that has subscribed to User Location Information related with PDU Session change.

If step 1b is triggered to perform Application Function influence on traffic routing by step 5 in clause 4.3.6.2, the SMF may reconfigure the User Plane of the PDU Session as described in step 6 in clause 4.3.6.2.

If interworking with TSN deployed in the transport network is supported and if the Status group from TN CNC to SMF/CUC in step 11 includes InterfaceConfiguration, and if the AN-TL/CN-TL are supported, the SMF/CUC initiates a PDU Session Modification procedure as in step 1d.

4.3.3.3 UE or network requested PDU Session Modification (home-routed roaming)

The UE or network requested PDU Session Modification procedure (home-routed roaming scenario) is depicted in figure 4.3.3.3-1.

Figure 4.3.3.3-1: UE or network requested PDU Session Modification (for home-routed roaming scenario)

1. The procedure is triggered by one of the following events:

1a. (UE or serving network requested) As in step 1a of clause 4.3.3.2 with the addition that:

– The V-SMF checks whether it can accept the request from the UE;

– The V-SMF invokes an Nsmf_PDUSession_Update Request (SM Context ID, UE request for PDU Session Modification or the QoS modification request from the VPLMN, UE location information, Time Zone, the current Access Type, PCO, [Always-on PDU Session Requested]) service operation to inform the H-SMF to update the PDU Session. The H-SMF responds to the request immediately. If the AMF notified the V-SMF that the access type of the PDU session can be changed, as described in the UE Triggered Service Request procedure in clause 4.2.3.2, the V-SMF shall also indicate that the access type can be changed.

The PS Data Off status, if changed, shall be included in PCO (Protocol Configuration Option) in the PDU Session Modification Request message.

1b. (HPLMN requested) This step is the same as step 1b in clause 4.3.3.2. If the H-SMF received the indication that the access type of the PDU session can be changed, the H-SMF shall indicate the target access type to the PCF in the Access Type information of the Npcf_SMPolicyControl_Update Request.

1c. (HPLMN requested) This step is the same as step 1c in clause 4.3.3.2.

1d. (HPLMN requested) This step is the same as step 1d in clause 4.3.3.2.

1e. As in step 1e of clause 4.3.3.2 with addition that:

– The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM context ID, N2 SM information) and sends it to the V-SMF;

– The V-SMF invokes an Nsmf_PDUSession_Update Request (SM context ID, ULI, AN type, QoS Flow to be released) service operation to inform the H-SMF to update the PDU Session. The H-SMF responds to the request immediately. For AN initiated notification control in step 1e of clause 4.3.3.2, the V-SMF includes also QoS Flow notification information as specified in clause 5.7 of TS 23.501 [2].

NOTE 1: SM Context ID between AMF and V-SMF and between V-SMF and H-SMF are different. SM Context ID has local significance per SMF instance.

2. This step is the same as steps 2 in clause 4.3.3.2 with the SMF is H-SMF.

3. (UE or serving network requested or HPLMN requested) The H-SMF invokes the Nsmf_PDUSession_Update Request (SM Context ID, QoS profiles, [Alternative QoS profile(s)], Session-AMBR, information needed to build the SM PDU Session Modification Command message towards the UE including the QoS rule(s) and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) and QoS rule operation and the QoS Flow level QoS parameters operation) service operation to the V-SMF.

Based on operator policies and roaming agreements, the V-SMF may decide to fully accept or reject the QoS information provided by the H-SMF. The V-SMF shall also be able to accept a subset of the QoS flows requested to be created or modified within a single H-SMF request i.e. V-SMF can accept some QoS flows and reject other QoS flows in same response to H-SMF.

3a-3b (HPLMN requested) These steps are executed if new QoS Flow(s) are to be created. The SMF updates the UPF with UL Packet Detection Rules of the new QoS Flow.

NOTE 2: This allows the UL packets with the QFI of the new QoS Flow to be transferred.

If an Always-on PDU Session Granted indication was provided by the H-SMF to indicate that the PDU Session is to be changed to an always-on PDU Session, the V-SMF decides whether to accept or reject the request from the H-SMF based on local policies.

4a-4b. These steps are the same as step 3a-3b in clause 4.3.3.2 but controlled from the V-SMF. The V-SMF uses the information received in step 3 to generate any N1 and/or N2 signalling to be sent towards the UE and/or the (R)AN.

5-7. These steps are the same as step 4-6 in clause 4.3.3.2.

8. This step is the same as step 7a in clause 4.3.3.2 with the difference that the SMF is V-SMF.

If the N2 SM information indicates modification failure and the V-SMF rejected the PDU session modification as described in step 7 in clause 4.3.3.2, step 9 is skipped.

9a-9b are the same as step 8a-8b in clause 4.3.3.2 but executed in Visited PLMN

10. This step is the same as step 7b in clause 4.3.3.2 with the difference that the SMF is V-SMF.

11-12. These steps are the same as steps 8-9 in 4.3.3.2.

13-14. These steps are the same as step 11a-11b in clause 4.3.3.2 but executed in Visited PLMN.

15. V-SMF responds to the H-SMF with an Nsmf_PDUSession_Update response carrying the information like PCO provided by the UE in the SM PDU Session Modification Command Ack message from the UE to the V-SMF, Secondary RAT usage data. The H-SMF shall modify the PDU Session context.

If the V-SMF has rejected QFI(s) (step3) or the (R)AN has rejected QFI(s) in step 6 of Figure 4.3.3.2-1, the H-SMF is responsible of later updating the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE.

16-17. These steps are the same as steps 12-13 in clause 4.3.3.2 with the difference that the SMF is H-SMF.