Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 38.413  Word version:  16.3.0

Top   Top   Up   Prev   Next
1…   4…   8…   8.2…   8.2.3…   8.3…   8.3.4…   8.4…   8.4.3…   8.5…   8.7…   8.8…   8.10…   8.12…   9…   9.2.5…   9.3…   9.3.2…   10…

 

8.2.3  PDU Session Resource Modify

8.2.3.1  General

The purpose of the PDU Session Resource Modify procedure is to enable configuration modifications of already established PDU session(s) for a given UE. It is also to enable the setup, modification and release of the QoS flow for already established PDU session(s). The procedure uses UE-associated signalling.

8.2.3.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.2.3.2-1: PDU session resource modify: successful operation
Up
The AMF initiates the procedure by sending a PDU SESSION RESOURCE MODIFY REQUEST message to the NG-RAN node.
The PDU SESSION RESOURCE MODIFY REQUEST message shall contain the information required by the NG-RAN node, which may trigger the NG-RAN configuration modification for the existing PDU sessions listed in the PDU Session Resource Modify Request List IE.
Upon reception of the PDU SESSION RESOURCE MODIFY REQUEST message, if the NG-RAN configuration is triggered to be modified and if resources are available for the modified NG-RAN configuration, the NG-RAN node shall execute the configuration modification for the requested PDU session.
If the RAN Paging Priority IE is included in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node may use it to determine a priority for paging the UE in RRC_INACTIVE state.
For each PDU session, if the S-NSSAI IE is included in the PDU Session Resource Modify Request Item IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall replace the previously provided S-NSSAI by the received S-NSSAI for the concerned PDU session and use it as specified in TS 23.502.
For each PDU session, if the Network Instance IE is included in the PDU Session Resource Modify Request Transfer IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message and the Common Network Instance IE is not present, the NG-RAN node shall, if supported, use it as specified in TS 23.501.
For each PDU session, if the Common Network Instance IE is included in the PDU Session Resource Modify Request Transfer IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, use it as specified in TS 23.501.
For each PDU session, if the Redundant Common Network Instance IE is included in the PDU Session Resource Modify Request Transfer IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, use it for the redundant transmission as specified in TS 23.501.
For each PDU session, if the TSC Traffic Characteristics IE is included in the PDU Session Resource Modify Request Transfer IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall, if supported, store it and use it as specified in TS 23.501.
For each PDU session, if the Redundant QoS Flow Indicator IE is included and set to "false" for all QoS flows, the NG-RAN node shall, if supported, stop the redundant transmission and release the redundant tunnel for the concerned PDU session as specified in TS 23.501.
For each PDU session in the PDU SESSION RESOURCE MODIFY REQUEST message, if the Alternative QoS Parameters Set List IE is included in the GBR QoS Flow Information IE in the PDU Session Resource Modify Request Transfer IE of the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node may accept the setup of the QoS flow when notification control has been enabled if the requested QoS parameters or at least one of the alternative QoS parameters sets can be fulfilled at the time of setup. In case the NG-RAN node accepts the setup fulfilling one of the alternative QoS parameters it shall indicate the alternative QoS parameters set which it currently fulfils in the Current QoS Parameters Set Index IE within the PDU Session Resource Setup Response Transfer IE of the PDU SESSION RESOURCE MODIFY RESPONSE message.
For each PDU session included in the PDU Session Resource Modify Request List IE:
  • For each QoS flow included in the QoS Flow Add or Modify Request List IE, based on the QoS Flow Level QoS Parameters IE, the NG-RAN node may establish, modify or release the DRB configuration and may change allocation of resources on NG or Uu accordingly. The NG-RAN node shall associate each QoS flow accepted to setup or modify with a DRB of the PDU session. The associated DRB for the QoS flow accepted to modify may not change.
  • For each QoS flow, if the Redundant QoS Flow Indicator IE is included, the NG-RAN node shall, if supported, store it and consider it for the redundant transmission as specified in TS 23.501.
  • For each QoS flow included in the QoS Flow Add or Modify Request List IE, if the QoS Flow Add or Modify Request Item IE is included for an existing QoS Flow Identifier IE, the NG-RAN node shall overwrite the content of the full QoS Flow Add or Modify Request Item IE.
  • For each QoS flow included in the QoS Flow to Release List IE, the NG-RAN node shall de-associate the QoS flow with the previously associated DRB.
  • If the NAS-PDU IE is received for the PDU session, the NG-RAN node shall pass it to the UE when modifying the Data Radio Bearer configuration. The NG-RAN node does not send the NAS PDU received for the PDU session when all the QoS flows to be added or modified are failed and no QoS flow was requested to be released, even if e.g. the NG-U UP TNL modification is successful.
  • The NG-RAN node may change allocation of resources on NG according to the requested target configuration.
  • If the PDU Session Aggregate Maximum Bit Rate IE is included in the PDU Session Resource Modify Request Transfer IE, the NG-RAN node shall store and use the received PDU Session Aggregate Maximum Bit Rate value when enforcing traffic policing for Non-GBR QoS flows for the concerned UE as specified in TS 23.501.
  • If the UL NG-U UP TNL Modify List IE is included in the PDU Session Resource Modify Request Transfer IE, the NG-RAN node shall update the transport layer information for the uplink data accordingly for the concerned transport bearers identified by the DL NG-U UP TNL Information IE included in the PDU Session Resource Modify Request Transfer IE for the concerned PDU session.
  • If the Additional UL NG-U UP TNL Information IE is included in the PDU Session Resource Modify Request Transfer IE, the NG-RAN node may allocate resources for an additional NG-U transport bearer for some or all of the QoS flows present in the QoS Flow Add or Modify Request List IE and it shall indicate these QoS flows in the Additional DL QoS Flow per TNL Information IE in the PDU Session Resource Modify Response Transfer IE. In case the Additional DL QoS Flow per TNL Information IE is not included the SMF shall consider the proposed additional UL NG-U UP TNL information as available again.
  • In case more than one NG-U transport bearers have been set up for the PDU session, if all the QoS flows associated to one existing NG-U transport bearer are included in the QoS Flow to Release List IE in the PDU Session Resource Modify Request Transfer IE, the NG-RAN node and 5GC shall consider that the concerned NG-U transport bearer is removed for the PDU session, and both NG-RAN node and 5GC shall therefore consider the related NG-U UP TNL information as available again.
  • If the Redundant UL NG-U UP TNL Information IE is included in the PDU Session Resource Modify Request Transfer IE, the NG-RAN node shall update the transport layer information for the uplink data accordingly for the concerned transport bearer identified by the Redundant DL NG-U UP TNL Information IE included in the PDU Session Resource Modify Request Transfer IE for the concerned PDU session.
  • If the Additional Redundant UL NG-U UP TNL Information IE is included in the PDU Session Resource Modify Request Transfer IE, the NG-RAN node may allocate resources for an additional redundant NG-U transport bearer for some or all of the QoS flows present in the QoS Flow Add or Modify Request List IE and it shall indicate these QoS flows in the Additional Redundant DL QoS Flow per TNL Information IE in the PDU Session Resource Modify Response Transfer IE. In case the Additional Redundant DL QoS Flow per TNL Information IE is not included the SMF shall consider the proposed additional Redundant UL NG-U UP TNL information as available again.
For each QoS flow which has been successfully added or modified, if the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the PDU SESSION RESOURCE MODIFY REQUEST message, the NG-RAN node shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501.
The NG-RAN node shall report to the AMF, in the PDU SESSION RESOURCE MODIFY RESPONSE message, the result for each PDU session requested to be modified listed in the PDU SESSION RESOURCE MODIFY REQUEST message:
  • For each PDU session which is successfully modified, the PDU Session Resource Modify Response Transfer IE shall be included containing:
    1. The list of QoS flows which have been successfully setup or modified, if any, in the QoS Flow Add or Modify Response List IE in case the PDU Session Resource Modify procedure is triggered by QoS flow setup or modification.
    2. The list of QoS flows which have failed to be setup or modified, if any, in the QoS Flow Failed to Add or Modify List IE in case the PDU Session Resource Modify procedure is triggered by QoS flow setup or modification.
  • For each PDU session which failed to be modified, the PDU Session Resource Modify Unsuccessful Transfer IE shall be included containing the failure cause.
  • For each PDU session, if the DL NG-U UP TNL Information IE is included in the PDU Session Resource Modify Response Transfer IE in the PDU SESSION RESOURCE MODIFY RESPONSE message, it shall be considered by the SMF as the new DL transport layer address for the PDU session. The NG-RAN also may indicate the mapping between each new DL transport layer address and the corresponding UL transport layer address assigned by the 5GC.
  • For each PDU session, if the Additional NG-U UP TNL Information IE is included in the PDU Session Resource Modify Response Transfer IE in the PDU SESSION RESOURCE MODIFY RESPONSE message, it shall be considered by the SMF as the new DL transport layer address(es) for the PDU session. The NG-RAN also may indicate the mapping between each new DL transport layer address and the corresponding UL transport layer address assigned by the 5GC.
Upon reception of the PDU SESSION RESOURCE MODIFY RESPONSE message the AMF shall, for each PDU session indicated in the PDU Session ID IE, transfer transparently the PDU Session Resource Modify Response Transfer IE or PDU Session Resource Modify Unsuccessful Transfer IE to each SMF associated with the concerned PDU session.
The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE MODIFY RESPONSE message location information of the UE in the User Location Information IE.
For a PDU session or a QoS flow which failed to be modified, the NG-RAN node shall fall back to the configuration of the PDU session or the QoS flow as it was configured prior to the reception of the PDU SESSION RESOURCE MODIFY REQUEST message.
Upon reception of the PDU SESSION RESOURCE MODIFY REQUEST message to setup a QoS flow for IMS voice, if the NG-RAN node is not able to support IMS voice, the NG-RAN node shall initiate EPS fallback or RAT fallback for IMS voice procedure as specified in TS 23.501 and report unsuccessful establishment of the QoS flow in the PDU Session Resource Modify Response Transfer IE or in the PDU Session Resource Modify Unsuccessful Transfer IE with cause value "IMS voice EPS fallback or RAT fallback triggered".
If the User Location Information IE is included in the PDU SESSION RESOURCE MODIFY RESPONSE message, the AMF shall handle this information as specified in TS 23.501.
Interactions with Handover Preparation procedure:
If a handover becomes necessary during the PDU Session Resource Modify procedure, the NG-RAN node may interrupt the ongoing PDU Session Resource Modify procedure and initiate the Handover Preparation procedure as follows:
  1. The NG-RAN node shall send the PDU SESSION RESOURCE MODIFY RESPONSE message in which the NG-RAN node shall indicate, if necessary, all the PDU sessions failed with an appropriate cause value, e.g. "NG intra-system handover triggered", "NG inter-system handover triggered" or "Xn handover triggered".
  2. The NG-RAN node shall trigger the handover procedure.
Up

8.2.3.3  Unsuccessful OperationWord‑p. 33
The unsuccessful operation is specified in the successful operation section.

8.2.3.4  Abnormal Conditions

If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing several PDU Session ID IEs (in the PDU Session Resource Modify Request List IE) set to the same value, the NG-RAN node shall report the modification of the corresponding PDU sessions as failed in the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value.
If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing some PDU Session ID IEs (in the PDU Session Resource Modify Request List IE) that the NG-RAN node does not recognize, the NG-RAN node shall report the corresponding invalid PDU sessions as failed in the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value.
If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing a QoS Flow Level QoS Parameters IE in the PDU Session Resource Modify Request Transfer IE for a GBR QoS flow but the GBR QoS Flow Information IE is not present, the NG-RAN node shall report the addition or modification of the corresponding QoS flow as failed in the PDU Session Resource Modify Response Transfer IE of the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value.
If the NG-RAN node receives a PDU SESSION RESOURCE MODIFY REQUEST message containing the Delay Critical IE in the Dynamic 5QI Descriptor IE of the QoS Flow Level QoS Parameters IE of the PDU Session Resource Modify Request Transfer IE set to the value "delay critical" but the Maximum Data Burst Volume IE is not present, the NG-RAN node shall report the addition or modification of the corresponding QoS flow as failed in the PDU Session Resource Modify Response Transfer IE of the PDU SESSION RESOURCE MODIFY RESPONSE message with an appropriate cause value.
Up

8.2.4  PDU Session Resource NotifyWord‑p. 34

8.2.4.1  General

The purpose of the PDU Session Resource Notify procedure is to notify that the already established QoS flow(s) or PDU session(s) for a given UE are released or not fulfilled anymore or fulfilled again by the NG-RAN node for which notification control is requested. The procedure uses UE-associated signalling.

8.2.4.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.2.4.2-1: PDU session resource notify
Up
The NG-RAN node initiates the procedure by sending a PDU SESSION RESOURCE NOTIFY message.
The PDU SESSION RESOURCE NOTIFY message shall contain the information of PDU session resources or QoS flows which are released or not fulfilled anymore or fulfilled again by the NG-RAN node.
  • For each PDU session for which some QoS flows are released or not fulfilled anymore or fulfilled again by the NG-RAN node, the PDU Session Resource Notify Transfer IE shall be included containing:
    1. The list of QoS flows which are released by the NG-RAN node, if any, in the QoS Flow Released List IE.
    2. The list of GBR QoS flows which are not fulfilled anymore or fulfilled again by the NG-RAN node, if any, in the QoS Flow Notify List IE together with the Notification Cause IE. For a QoS flow indicated as not fulfilled anymore the NG-RAN node may also indicate an alternative QoS parameters set which it can currently fulfil in the Current QoS Parameters Set Index IE.
  • For each PDU session resource which is released by the NG-RAN node, the PDU Session Resource Notify Released Transfer IE shall be included containing the release cause in the Cause IE.
The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE NOTIFY message location information of the UE in the User Location Information IE.
Upon reception of the PDU SESSION RESOURCE NOTIFY message, the AMF shall, for each PDU session indicated in the PDU Session ID IE, transfer transparently the PDU Session Resource Notify Transfer IE or PDU Session Resource Notify Released Transfer IE to the SMF associated with the concerned PDU session. Upon reception of PDU Session Resource Notify Transfer IE, the SMF normally initiate the appropriate release or modify procedure on the core network side for the PDU session(s) or QoS flow(s) identified as not fulfilled anymore.
For each PDU session for which the Secondary RAT Usage Information IE is included in the PDU Session Resource Notify Transfer IE or the PDU Session Resource Notify Released Transfer IE, the SMF shall handle this information as specified in TS 23.502.
If the User Location Information IE is included in the PDU SESSION RESOURCE NOTIFY message, the AMF shall handle this information as specified in TS 23.501.
Up

8.2.4.3  Abnormal Conditions

Void.

8.2.5  PDU Session Resource Modify IndicationWord‑p. 35

8.2.5.1  General

The purpose of the PDU Session Resource Modify Indication procedure is for the NG-RAN node to request modification of the established PDU session(s). The procedure uses UE-associated signalling.

8.2.5.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.2.5.2-1: PDU session resource modify indication: successful operation
Up
The NG-RAN node initiates the procedure by sending a PDU SESSION RESOURCE MODIFY INDICATION message. Upon reception of the PDU SESSION RESOURCE MODIFY INDICATION message, the AMF shall, for each PDU session indicated in the PDU Session ID IE, transparently transfer the PDU Session Resource Modify Indication Transfer IE to the SMF associated with the concerned PDU session.
For each PDU session for which the DL QoS Flow per TNL Information IE is included in the PDU Session Resource Modify Indication Transfer IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall consider the included DL transport layer address as the DL transport layer address for the included associated QoS flows and it may provide the associated UL transport layer address in the UL NG-U UP TNL Information IE in the PDU Session Resource Modify Confirm Transfer IE in the PDU SESSION RESOURCE MODIFY CONFIRM message.
For each PDU session for which the Additional DL QoS Flow per TNL Information IE is included in the PDU Session Resource Modify Indication Transfer IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall, if supported, consider for this split PDU session each included DL transport layer address(es) as the DL transport layer address(s) for the included associated QoS flows and it may provide the associated UL transport layer address(s) in the Additional NG-U UP TNL Information IE in the PDU Session Resource Modify Confirm Transfer IE in the PDU SESSION RESOURCE MODIFY CONFIRM message.
In case more than one NG-U transport bearers have been set up for the PDU session, the DL QoS Flow per TNL Information IE and the Additional DL QoS Flow per TNL Information IE in the PDU Session Resource Modify Indication Transfer IE in the PDU SESSION RESOURCE MODIFY INDICATION message shall be included if at least one QoS flow is associated to their respective NG-U transport bearer; if no QoS flow is associated to one existing NG-U transport bearer after the modification, the NG-RAN node and 5GC shall consider that the concerned NG-U transport bearer is removed for the PDU session, and both NG-RAN node and 5GC shall therefore consider the related NG-U UP TNL information as available again.
For each PDU session for which the Redundant DL QoS Flow per TNL Information IE is included in the PDU Session Resource Modify Indication Transfer IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall consider the included DL transport layer address as the new DL transport layer address for the included associated QoS flows for redundant transmission and it may provide the associated UL transport layer address in the Redundant UL NG-U UP TNL Information IE in the PDU Session Resource Modify Confirm Transfer IE in the PDU SESSION RESOURCE MODIFY CONFIRM message.
For each PDU session for which the Additional Redundant DL QoS Flow per TNL Information IE is included in the PDU Session Resource Modify Indication Transfer IE in the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall consider for this split PDU session each included DL transport layer address(es) as the new downlink termination point(s) for the included associated QoS flows and it may provide the associated UL transport layer address(s) in the Additional Redundant NG-U UP TNL Information IE in the PDU Session Resource Modify Confirm Transfer IE in the PDU SESSION RESOURCE MODIFY CONFIRM message for the redundant transmission.
For each PDU session for which the Global RAN Node ID of Secondary NG-RAN Node IE is included in the PDU Session Resource Modify Indication Transfer IE of the PDU SESSION RESOURCE MODIFY INDICATION message, the SMF shall, if supported, handle this information as specified in TS 23.501.
If the Security Result IE is included in the PDU Session Resource Modify Indication Transfer IE in the PDU SESSION RESOURCE MODIFY INDICATION message, it may be considered by the SMF as the new security status of the PDU session.
For each PDU session for which the Secondary RAT Usage Information IE is included in the PDU Session Resource Modify Indication Transfer IE, the SMF shall handle this information as specified in TS 23.502.
The AMF shall report to the NG-RAN node in the PDU SESSION MODIFY RESOURCE CONFIRM message the result for each PDU session listed in PDU SESSION RESOURCE MODIFY INDICATION message:
  • For each PDU session which is successfully modified, the PDU Session Resource Modify Confirm Transfer IE shall be included containing:
    1. The list of QoS flows which have been successfully modified in the QoS Flow Modify Confirm List IE.
    2. The list of QoS flows which have failed to be modified, if any, in the QoS Flow Failed to Modify List IE.
  • For each PDU session which failed to be modified, the PDU Session Resource Modify Indication Unsuccessful Transfer IE shall be included to report the failure cause.
Upon reception of the PDU Session Resource Modify Confirm Transfer IE for each PDU session listed in the PDU SESSION RESOURCE MODIFY CONFIRM message:
  • If the QoS Flow Failed To Modify List IE is included, the NG-RAN node shall either
    1. de-associate the corresponding DRB for the concerned QoS flow, or
    2. keep the previous transport layer information before sending the PDU SESSION RESOURCE MODIFY INDICATION unchanged for the concerned QoS flow.
Upon reception of the PDU Session Resource Modify Indication Unsuccessful Transfer IE for each PDU session listed in the PDU SESSION RESOURCE MODIFY CONFIRM message, the NG-RAN node shall either:
    1. release all corresponding NG-RAN configuration and resources for the concerned PDU session, or
    2. keep the previous transport layer information before sending the PDU SESSION RESOURCE MODIFY INDICATION unchanged for the concerned PDU session.
The NG-RAN node shall, if supported, report in the PDU SESSION RESOURCE MODIFY INDICATION message location information of the UE in the User Location Information IE.
Up

8.2.5.3  Unsuccessful OperationWord‑p. 36
The unsuccessful operation is specified in the successful operation section.

8.2.5.4  Abnormal Conditions

Void.


Up   Top   ToC