[go: up one dir, main page]

WO2025028194A1 - Nœud de réseau d'accès radio, nœud de réseau central et procédés associés - Google Patents

Nœud de réseau d'accès radio, nœud de réseau central et procédés associés Download PDF

Info

Publication number
WO2025028194A1
WO2025028194A1 PCT/JP2024/024903 JP2024024903W WO2025028194A1 WO 2025028194 A1 WO2025028194 A1 WO 2025028194A1 JP 2024024903 W JP2024024903 W JP 2024024903W WO 2025028194 A1 WO2025028194 A1 WO 2025028194A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos
network node
core network
radio access
access network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2024/024903
Other languages
English (en)
Japanese (ja)
Inventor
豊武 田村
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Publication of WO2025028194A1 publication Critical patent/WO2025028194A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device

Definitions

  • the present disclosure relates to wireless communication systems, and in particular to signaling between a radio access network and a core network.
  • Notification control is also called Quality of Service (QoS) Notification Control (QNC).
  • QoS Quality of Service
  • Notification control enables the core network to receive notifications from the Radio Access Network (RAN) when "Guaranteed Flow Bit Rate (GFBR) can no longer (or can again) be guaranteed" for Guaranteed Flow Bit Rate (GBR) QoS flows.
  • RAN Radio Access Network
  • GBR Guaranteed Flow Bit Rate
  • the QoS profile of the QoS flow can be provided to the RAN by the core network.
  • the Session Management Function (SMF) in the core network provides the QoS profile to the RAN via the Access and Mobility Management Function (AMF) in the core network.
  • a QoS flow can be either "GBR" or "non-GBR” depending on its QoS profile.
  • the QoS profile includes multiple QoS parameters.
  • the QoS profile includes a 5G QoS Identifier (5QI) and an Allocation and Retention Priority (ARP).
  • the QoS profile includes a Guaranteed Flow Bit Rate (GFBR) and a Maximum Flow Bit Rate (MFBR).
  • GFBR Guaranteed Flow Bit Rate
  • MFBR Maximum Flow Bit Rate
  • the QoS profile may include a Notification control.
  • the 5QI values define static values for Packet Delay Budget (PDB) and Packet Error Rate (PER).
  • PDB Packet Delay Budget
  • PER Packet Error Rate
  • signaling of the complete 5G QoS characteristics is required as part of the QoS profile.
  • GFBR indicates the bit rate that the network guarantees to provide to a GBR QoS flow over an Averaging Time Window.
  • PDB defines an upper bound on the time that a packet may be delayed between the User Equipment (UE) and the N6 termination point of the User Plane Function (UPF). The PDB applies to downlink packets received on the N6 interface by the UPF and uplink packets sent by the UE.
  • UE User Equipment
  • UPF User Plane Function
  • Protocol Data Units e.g., Internet Protocol (IP) packets
  • IP Internet Protocol
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the QoS parameter notification control (hereafter referred to as the notification control parameter) indicates whether to request notification from the NG-RAN when GFBR can no longer (or can again) be guaranteed for a QoS flow during the lifetime of the QoS flow.
  • the notification control parameter can be used for GBR QoS flows when the application traffic can adapt to QoS changes (e.g., when the Application Function (AF) can trigger rate adaptation).
  • the SMF enables notification control only if the notification control parameter is set in the Policy and Charging Control (PCC) rule (received from the Policy Control Function (PCF)) associated with the QoS flow.
  • PCC Policy and Charging Control
  • the NG-RAN If notification control is enabled for a GBR QoS flow and the NG-RAN determines that the GFBR, PDB or PER of the QoS profile cannot be met, the NG-RAN sends a notification to the SMF that "GFBR can no longer be guaranteed".
  • the NG-RAN can determine that "GFBR can no longer be guaranteed” based on measurements such as queuing delay and system load.
  • the NG-RAN keeps the QoS flow while it cannot meet the requested QoS profile for this QoS flow, unless a specific condition in the NG-RAN requires the release of NG-RAN resources for this GBR QoS flow, due to e.g. radio link failure or internal RAN congestion.
  • the NG-RAN should make an effort to meet the GFBR, PDB and PER of the QoS profile again.
  • the SMF can receive QoS notification control information (i.e., events "GFBR can no longer be guaranteed” and "GFBR can be guaranteed again") from the NG-RAN via the AMF. Additionally or alternatively, based on the PCC rules, the SMF may instruct the NG-RAN to report the QoS notification control information via a tunnel between the NG-RAN and the PDU Session Anchor (PSA) UPF and instruct the PSA UPF to notify when the report is received as instructed. In this case, the SMF can receive the QoS notification control information from the NG-RAN via the PSA UPF. Upon receiving the notification "GFBR can no longer be guaranteed" from the NG-RAN, the SMF may forward the notification to the PCF.
  • QoS notification control information i.e., events "GFBR can no longer be guaranteed" and "GFBR can be guaranteed again
  • the NG-RAN determines that the QoS profile's GFBR, PDB, and PER can be fulfilled again for the QoS flow (for which a notification that "GFBR can no longer be guaranteed” was sent), the NG-RAN notifies the SMF that "GFBR can be guaranteed” again. The SMF may forward this notification to the PCF.
  • the NG-RAN determines that it cannot meet the GFBR, PDB or PER of the QoS profile, it shall send a notification to the SMF that "GFBR can no longer be guaranteed". Before sending the notification that "GFBR can no longer be guaranteed" to the SMF, the NG-RAN shall check whether the GFBR, PDB and PER currently met by the NG-RAN match any of the alternative QoS profiles, according to the indicated priorities.
  • the NG-RAN shall indicate, together with the notification to the SMF, the reference to the matching Alternative QoS Profile with the highest priority. If no match is found, the NG-RAN sends a notification to the SMF that "GFBR can no longer be guaranteed" and indicates that the lowest alternative QoS profile cannot be met (unless certain conditions in the NG-RAN require the release of NG-RAN resources for this GBR QoS flow, e.g. due to radio link failure or internal RAN congestion).
  • the alternative QoS profile indicates the combination of QoS parameters: PDB, PER, Averaging Window, and GFBR to which the application traffic can adapt.
  • the NG-RAN shall send a notification (i.e. "GFBR can no longer be guaranteed” or "GFBR can be guaranteed again") to the SMF and indicate the current situation (unless certain conditions in the NG-RAN require the release of NG-RAN resources for this GBR QoS flow, e.g. due to radio link failure or internal RAN congestion).
  • the current situation is either that the QoS profile can be satisfied (which is implicit in the notification "GFBR can be guaranteed again" itself), that a different alternative QoS profile can be satisfied, or that the alternative QoS profile with the lowest priority cannot be satisfied.
  • the NG-RAN shall always attempt to satisfy the QoS profile and, if this is not possible, to satisfy the alternative QoS profile with a higher priority.
  • the SMF may inform the PCF. In that case, the SMF indicates to the PCF the currently met status. Unless otherwise indicated by the PCF, the SMF uses Non-Access Stratum (NAS) signalling (sent transparently via the RAN) to inform the UE about changes in QoS parameters (e.g. 5QI, GFBR, MFBR) currently met by the NG-RAN for the QoS flow after the notification control has occurred.
  • NAS Non-Access Stratum
  • Non-patent document 2 specifies the PDU Session Resource Notify procedure between the NG-RAN node and the AMF.
  • One of the purposes of the PDU Session Resource Notify procedure is to notify that already established QoS flow(s) or PDU Session(s) for a UE are released or are not fulfilled anymore or fulfilled again by the NG-RAN node for which notification control is required.
  • the procedure uses UE-associated or UE-specific signalling.
  • the NG-RAN node initiates the procedure by sending a PDU SESSION RESOURCE NOTIFY message.
  • the PDU SESSION RESOURCE NOTIFY message contains information of PDU session resources or QoS flows that are released or are no longer filled or refilled by the NG-RAN node. Specifically, for each PDU session for which some QoS flows are released or are no longer filled or refilled by the NG-RAN node, the PDU SESSION RESOURCE NOTIFY message contains a PDU Session Resource Notify Transfer information element (IE).
  • IE PDU Session Resource Notify Transfer information element
  • the PDU Session Resource Notify Transfer IE may contain a QoS Flow Notify List IE.
  • the QoS Flow Notify List IE indicates a list of GBR QoS flows that are no longer fulfilled or will be fulfilled again by the NG-RAN node.
  • the QoS Flow Notify List IE contains a QoS Flow Identifier IE and a Notification Cause IE for each QoS flow contained in the list.
  • the Notification Cause IE is of type ENUMERATED and can indicate "fulfilled" or "not fulfilled".
  • the NG-RAN node may indicate in the Current QoS Parameters Set Index IE an alternative QoS parameter set that can currently be fulfilled for the QoS flows that are indicated as no longer fulfilled.
  • the AMF Upon receiving a PDU SESSION RESOURCE NOTIFY message, the AMF transparently forwards, for each PDU session indicated in the PDU Session ID IE, a PDU Session Resource Notify Transfer IE to the SMF associated with that PDU session.
  • a PDU Session Resource Notify Transfer IE Upon receiving a PDU Session Resource Notify Transfer IE, the SMF typically initiates appropriate release or modification procedures on the core network side for the PDU session(s) or QoS flow(s) identified as no longer being satisfied.
  • 3GPP TS 23.501 V18.1.0 (2023-03) "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)", March 2023
  • 3GPP TS 38.413 V17.4.0 (2023-03) "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 17)", March 2023
  • the notification control specified in 3GPP Release 15 and later releases may have some room for improvement, for example in the following areas:
  • One of these improvements relates to the notification from the NG-RAN to the core network (e.g., AMF, UPF, or SMF) of the reason (or cause, or factor) that led to the decision on the QoS notification control information.
  • the NG-RAN can send a notification to the core network (e.g., AMF, UPF, or SMF) that the GFBR or QoS profile is no longer met or will be met again.
  • the current 3GPP specifications regarding notification control do not allow the NG-RAN to inform the core network of the reason why the NG-RAN has determined that the GFBR or QoS profile is no longer met.
  • a situation in which a specified QoS profile is no longer met may be a situation in which any of the alternative QoS profiles are met. This may also be a situation in which even the lowest priority alternative QoS profile cannot be met.
  • the current 3GPP specifications for QoS notification control do not allow the NG-RAN to inform the core network of the reason why the NG-RAN determines that the specified GFBR or QoS profile is satisfied again. Notification from the NG-RAN to the core network of the reason (or cause or factor) that led to the decision on the QoS notification control information may be useful for the core network (e.g., SMF or PCF or both) to optimize the actions it takes with respect to the QoS flow.
  • Another of these improvements relates to the notification from the NG-RAN to the core network of the QoS parameters (e.g., GFBR, PDB, PER, 5QI) or QoS profile preferred for the NG-RAN.
  • the NG-RAN can send a notification to the core network (e.g., AMF, UPF, or SMF) that the GFBR or QoS profile is no longer satisfied or will be satisfied again.
  • the core network e.g., AMF, UPF, or SMF
  • the NG-RAN can send a reference to the highest priority matching alternative QoS profile for this GBR QoS flow to the core network together with the notification that the specified QoS profile is no longer satisfied.
  • the NG-RAN may prefer other values of the QoS parameter for the GBR QoS flow than the value of the QoS parameter indicated by the QoS profile specified by the core network for the GBR QoS flow or than the alternative value of the QoS parameter indicated by any of the alternative QoS profiles.
  • the current notification control provisions in the 3GPP specifications do not allow the NG-RAN to inform the core network of the NG-RAN's preferred QoS parameter values for a GBR QoS flow. Informing the core network of the NG-RAN's preferred QoS parameter values for a QoS flow may be useful for the core network (e.g., SMF or PCF or both) to optimize the actions it takes with respect to that QoS flow.
  • the core network e.g., SMF or PCF or both
  • the above-mentioned improvements to notification control specified in the 3GPP specifications may also be necessary or beneficial in communication systems other than 3GPP systems or fifth generation (5G) systems, such as Beyond 5G and sixth generation (6G) communication systems.
  • 5G fifth generation
  • 6G sixth generation
  • One of the objectives that the embodiments disclosed in this specification aim to achieve is to provide an apparatus, a method, and a program that contribute to at least one of the improvements (including those described above) to notification control between the RAN and the core network. It should be noted that this objective is only one of the objectives that the embodiments disclosed in this specification aim to achieve. Other objectives or problems and novel features will become apparent from the description of this specification or the accompanying drawings.
  • a Radio Access Network (RAN) node is configured to receive a QoS profile for a packet flow from a core network.
  • the RAN node is further configured to, when sending a notification to the core network that the QoS profile is no longer met or that the QoS profile will be met again while maintaining the packet flow without releasing the packet flow or rejecting the setup or modification of the packet flow, also inform the core network of the reason, cause or factor that led to the determination that the QoS profile is no longer met or that the QoS profile will be met again.
  • a method performed by a RAN node includes the following steps: (a) receiving a QoS profile for a packet flow from a core network; and (b) when sending a notification to the core network that the QoS profile is no longer met or that the QoS profile will be met again while maintaining the packet flow without releasing the packet flow or rejecting the setup or modification of the packet flow, also informing the core network of the reasons, causes, or factors that led to the determination that the QoS profile is no longer met or that the QoS profile will be met again.
  • a core network node is configured to send a QoS profile for a packet flow to a RAN node.
  • the core network node is further configured to receive a first notification from the RAN node that the packet flow is not released or the setup or modification of the packet flow is not rejected and the packet flow is maintained but the QoS profile is no longer met or the QoS profile is met again, together with a second notification of reasons, causes or factors that led to the determination that the QoS profile is no longer met or is met again.
  • a method performed by a core network node comprises the following steps: (a) sending a QoS profile for a packet flow to a RAN node; and (b) receiving a first notification from the RAN node that the packet flow is not released or the setup or modification of the packet flow is not rejected and the packet flow is maintained but the QoS profile is no longer met or the QoS profile is again met, along with a second notification of reasons, causes, or factors that led to a determination that the QoS profile is no longer met or is again met.
  • the RAN node is configured to receive a QoS profile for a packet flow from a core network.
  • the RAN node is further configured to, when sending a notification to the core network that the QoS profile is no longer satisfied or that the QoS profile is satisfied again while maintaining the packet flow, also inform the core network of values preferred by the RAN node of one or more QoS parameters for the packet flow.
  • a method performed by a RAN node includes the following steps: (a) receiving from a core network a QoS profile for the packet flow; and (b) informing the core network of preferred values for the RAN node of one or more QoS parameters for the packet flow when sending a notification to the core network that the QoS profile is no longer met or that the QoS profile will again be met while maintaining the packet flow.
  • the core network node is configured to send a QoS profile for a packet flow to a RAN node.
  • the core network node is further configured to receive a first notification from the RAN node that the packet flow is maintained but that the QoS profile is no longer satisfied or that the QoS profile is satisfied again, together with a second notification indicating preferred values for the RAN node of one or more QoS parameters for the packet flow.
  • a method performed by a core network node comprises the following steps: (a) sending a QoS profile for a packet flow to a RAN node; and (b) receiving a first notification from the RAN node that the packet flow is maintained but the QoS profile is no longer met or that the QoS profile is again met, along with a second notification indicating preferred values to the RAN node of one or more QoS parameters for the packet flow.
  • the program includes a set of instructions (software code) that, when loaded into a computer, causes the computer to perform the operation or method of a RAN node or core network node described in the above aspects.
  • the above-described aspects provide an apparatus, method, and program that contribute to at least one of several improvements (including those described above) to notification control between the RAN and the core network.
  • FIG. 1 illustrates an example configuration of a wireless communication system related to one or more embodiments.
  • 1 is a flow chart illustrating an example of the operation of a RAN node in accordance with one or more embodiments.
  • 1 is a flow chart illustrating an example of the operation of a core network node in accordance with one or more embodiments.
  • FIG. 2 illustrates an example of signaling between a RAN node and a core network node in accordance with one or more embodiments.
  • FIG. 2 illustrates an example of signaling between a RAN node and a core network node in accordance with one or more embodiments.
  • FIG. 2 illustrates an example of signaling between a RAN node and a core network node in accordance with one or more embodiments.
  • 1 is a flow chart illustrating an example of the operation of a RAN node in accordance with one or more embodiments.
  • 1 is a flow chart illustrating an example of the operation of a core network node in accordance with one or more embodiments.
  • FIG. 2 illustrates an example of signaling between a RAN node and a core network node in accordance with one or more embodiments.
  • FIG. 2 illustrates an example of signaling between a RAN node and a core network node in accordance with one or more embodiments.
  • FIG. 2 illustrates an example of signaling between a RAN node and a core network node in accordance with one or more embodiments.
  • FIG. 1 is a block diagram illustrating an example configuration of a RAN node in accordance with one or more embodiments.
  • FIG. 2 is a block diagram illustrating an example configuration of a core network node according to one or more embodiments.
  • multiple embodiments described below may be used alone, or two or more embodiments may be combined as appropriate. These multiple embodiments may have novel features that are different from each other. Thus, these multiple embodiments may contribute to achieving different objectives or solving different problems, and may contribute to providing different effects.
  • if may be construed to mean “when,” “while,” “at or around the time,” “after,” “upon,” “in response to determining,” “in accordance with a determination,” or “in response to detecting.” These expressions may be construed to have the same meaning, depending on the context.
  • FIG. 1 shows an example configuration of a wireless communication system related to multiple embodiments.
  • Each element (network function) shown in FIG. 1 can be implemented, for example, as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an application platform.
  • the wireless communication system shown in Figure 1 may be provided by a Mobile Network Operator (MNO) or it may be a Non-Public Network (NPN) provided by a party other than an MNO. If the cellular network shown in Figure 1 is an NPN, it may be an independent network called a Stand-alone Non-Public Network (SNPN) or an NPN linked to an MNO network called a Public network integrated NPN (PNI-NPN).
  • MNO Mobile Network Operator
  • NPN Non-Public Network
  • PNI-NPN Public network integrated NPN
  • the wireless communication system includes a UE 1, an NG-RAN 2, and a 5G Core Network (5GC) 4.
  • the UE 1 may be referred to as a wireless terminal, a mobile terminal, a mobile station, or other terms such as a wireless transmit receive unit (WTRU).
  • the NG-RAN 2 includes one or more NG-RAN nodes 3.
  • the 5GC 4 includes one or more network functions or nodes in the control plane and one or more functions or nodes in the user plane.
  • FIG. 1 illustrates some representative network functions or nodes in the 5GC 4, including an AMF 5, an SMF 6, a PCF 7, and a UPF 8.
  • the UPF 8 may include multiple UPFs interconnected.
  • the UE 1 uses 5G connectivity services provided by the NG-RAN 2 and the 5GC 4 to communicate with a Data Network (DN) 9. More specifically, UE1 is connected to NG-RAN node 3 in NG-RAN2 and communicates with DN9 via UPF8 in 5GC4.
  • DN Data Network
  • PDU session 100 is an association, session, or connection between UE1 and DN9.
  • PDU session 100 is used to provide PDU connectivity services (i.e., exchange of PDUs between UE1 and DN9).
  • PDU session 100 consists of a tunnel within 5GC4 (N9 tunnel), a tunnel between 5GC4 and NG-RAN2 (N3 tunnel), and one or more radio bearers.
  • UE1 may establish multiple PDU sessions with multiple UPFs (PDU session anchors) 8 respectively to access multiple DNs9 concurrently.
  • the 5G QoS model is based on QoS flows.
  • the 5G QoS model supports both QoS flows that require flow bit rate guarantees (GBR QoS flows) and QoS flows that do not require flow bit rate guarantees (Non-GBR QoS flows).
  • QoS flows are the finest granularity of QoS differentiation in a PDU session. In other words, QoS flows are the finest granularity for QoS forwarding treatment in a 5G system. All traffic mapped to the same 5G QoS flow receives the same forwarding treatment (e.g., scheduling policy, queue management policy, rate shaping, Radio Link Control (RLC) settings, etc.).
  • RLC Radio Link Control
  • Every QoS flow is characterized by a QoS profile; one or more QoS rules and optionally QoS flow level parameters; and one or more uplink and downlink Packet Detection Rule(s) (PDR(s)).
  • the QoS profile is provided from SMF 6 to NG-RAN 2 (or NG-RAN node 3) via AMF 5 on the N2 reference point.
  • One or more QoS rules and QoS flow level parameters are provided from SMF 6 to UE 1 via AMF 5 on the N1 reference point.
  • One or more uplink and downlink PDR(s) are provided from SMF 6 to UPF 8.
  • multiple QoS flows 120 associated with different QoS requirements can be established for one PDU session 100.
  • One or more applications 10 in UE1 transmit or receive multiple packet flows between one or more applications 90 in DN9 via multiple QoS flows 120.
  • a QoS flow can be considered as a packet flow between UE1 and 5GC4 consisting of one or more packet flows transferred between UE1 and DN9.
  • a QoS flow can be considered as a transmission path or connection set up or established between UE1 and 5GC4 to forward one or more packet flows transferred between UE1 and DN9.
  • the NG-RAN node 3 may provide one or more cells, and the UE 1 may be simultaneously connected to multiple cells provided by the NG-RAN node 3. In other words, the UE 1 may perform Carrier Aggregation (CA) between multiple cells provided by the NG-RAN node 3.
  • CA Carrier Aggregation
  • the UE 1 may be simultaneously connected to the NG-RAN node 3 and other RAN nodes (e.g., NG-RAN nodes or Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) nodes) for Dual Connectivity (DC).
  • This dual connectivity may be Multi-Radio Dual Connectivity (MR-DC).
  • the NG-RAN node 3 may be a gNB or a ng-eNB.
  • the ng-eNB is a node that provides Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to the UE and is connected to the 5GC via the NG interface.
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • the NG-RAN node 3 may be a Central Unit (e.g., gNB-CU) in a cloud RAN (C-RAN) deployment, or a combination of a CU and one or more Distributed Units (e.g., gNB-DUs).
  • the C-RAN is also referred to as a CU/DU split.
  • the CU may include a Control Plane (CP) Unit (e.g., gNB-CU-CP) and one or more User Plane (UP) Units (e.g., gNB-CU-UP).
  • CP Control Plane
  • UP User Plane
  • the NG-RAN node 3 may be a CU-CP or a combination of a CU-CP and a CU-UP.
  • the CU may be a logical node that hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB (or the RRC and PDCP protocols of the gNB).
  • RRC Radio Resource Control
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • the DU may be a logical node that hosts the Radio Link Control (RLC), Medium Access Control (MAC), and Physical (PHY) layers of the gNB.
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical
  • AMF5 is one of the network functions in the 5GC control plane.
  • AMF5 provides the termination of the RAN Control Plane (CP) interface (i.e., N2 interface).
  • AMF5 terminates a single signaling connection (i.e., NAS signaling connection) with UE1 and provides registration management, connection management, and mobility management.
  • Registration management is used to register and deregister UE1 to the network (5G system).
  • Connection management is used to establish and release the NAS signaling connection between UE1 and AMF5.
  • Mobility management is used to keep track of the location of UE1. Mobility management uses periodic registration update and mobility registration update procedures. Therefore, in 5G systems, mobility management can be said to be included in registration management.
  • AMF5 provides NF services to Network Function (NF) consumers (e.g. other AMFs and SMF6) over a service-based interface (i.e. Namf interface).
  • NF Network Function
  • the NF services provided by AMF5 include a communication service (Namf_Communication), which enables NF consumers (e.g. SMF6) to communicate with UE1 or NG-RAN2 via AMF5.
  • SMF6 is one of the network functions in the 5GC control plane. SMF6 provides session management. Session management is used to establish, modify, and release PDU sessions to provide PDU connectivity services to UE1. Session management includes signaling with UE1, NG-RAN2, AMF5, and UPF8 for establishing, modifying, and releasing PDU sessions.
  • the SMF6 transmits and receives SM signaling messages (NAS-SM messages, N1 SM messages) to and from the NAS Session Management (SM) layer of UE1 via the communication services provided by AMF5.
  • SM NAS Session Management
  • the SMF6 transmits and receives N2SM information to and from NG-RAN2 (or NG-RAN node 3) via the communication services provided by AMF5.
  • the N2SM information sent from the SMF6 to the NG-RAN2 via AMF5 may include, among other information, a PDU session ID, QoS flow Identifiers (QFIs) and QoS profiles of one or more QoS flows.
  • QFIs QoS flow Identifiers
  • the N2SM information sent from the NG-RAN2 to the SMF6 via AMF5 may also include, among other information, a QFI of a QoS flow and QoS notification control information for that QoS flow.
  • the QoS notification control information indicates that the QoS profile or target (e.g., GFBR) of the QoS flow cannot be fulfilled or can be fulfilled again.
  • SMF6 provides NF services to NF consumers (e.g., AMF5, other SMFs) over a service-based interface (i.e., Nsmf interface).
  • NF services provided by SMF6 include a session management service (Nsmf_PDUSession) that allows NF consumers (e.g., AMF5) to handle PDU sessions.
  • Nsmf_PDUSession session management service
  • PCF7 is one of the network functions in the 5GC control plane. PCF7 supports interactions with access and mobility policy enforcement in AMF5 via a service-based interface. PCF7 provides access and mobility management related policies to AMF5. Additionally, PCF7 provides session related policies to SMF6. Session related policies include PDU Session related policy information and PCC rule information.
  • NG-RAN2 and 5GC4 support Notification control, also known as QoS Notification Control (QNC).
  • QoS Notification Control enables 5GC4 to receive notifications from NG-RAN2 when the Guaranteed Flow Bit Rate (GFBR) can no longer be guaranteed (or can again) for GBR QoS flows.
  • GFBR Guaranteed Flow Bit Rate
  • the QoS profile of a QoS flow can be provided to the NG-RAN 2 (or NG-RAN node 3) by the SMF 6 in the 5GC 4 via the AMF 5.
  • a QoS flow can be either "GBR" or "non-GBR” depending on its QoS profile.
  • the QoS profile includes multiple QoS parameters.
  • the QoS profile includes 5QI and ARP.
  • the QoS profile includes GFBR and MFBR.
  • the QoS profile may include Notification control. Note that if a standardized 5QI value is used, the 5QI value defines the static values of PDB and PER. On the other hand, if a non-standardized or dynamically assigned 5QI value is used, signaling of the complete 5G QoS characteristics (including PDB and PER) is required as part of the QoS profile.
  • GFBR indicates the bit rate that the network guarantees to provide to a GBR QoS flow over an Averaging Time Window.
  • PDB defines an upper bound on the time that packets may be delayed between UE1 and the N6 termination point of UPF8. PDB applies to downlink packets received on the N6 interface by UPF8 and uplink packets sent by UE1.
  • PER defines an upper bound on the rate of PDUs (e.g., IP packets) that are processed at the transmitting side of the link layer protocol (e.g., RLC in 3GPP access) but not successfully delivered to the corresponding higher layer at the receiving side (e.g., PDCP in RAN in 3GPP access).
  • the link layer protocol e.g., RLC in 3GPP access
  • PDCP in RAN in 3GPP access
  • the QoS parameter notification control indicates whether to request a notification from NG-RAN2 if GFBR can no longer be guaranteed (or can again) for a QoS flow during the QoS flow's lifetime.
  • the notification control parameter can be used for GBR QoS flows if the application traffic can adapt to QoS changes (e.g., if the Application Function (AF) can trigger rate adaptation).
  • SMF6 enables notification control only if the notification control parameter is set in the PCC rule (received from PCF7) associated with the QoS flow.
  • the NG-RAN node 3 If notification control is enabled for a GBR QoS flow and the NG-RAN node 3 determines that the GFBR, PDB or PER of the QoS profile cannot be met, the NG-RAN node 3 sends a notification to the SMF 6 that "GFBR can no longer be guaranteed".
  • the NG-RAN node 3 can determine that "GFBR can no longer be guaranteed” based on measurements such as, for example, queuing delay and system load.
  • the NG-RAN node 3 keeps the QoS flow even while the NG-RAN node 3 does not meet the QoS profile requested for this QoS flow, unless a specific condition at the NG-RAN node 3 requires the release of NG-RAN resources for this GBR QoS flow, due to, for example, radio link failure or internal RAN congestion.
  • the NG-RAN node 3 will make an effort to meet the GFBR, PDB and PER of the QoS profile again.
  • the SMF 6 can receive QoS notification control information (i.e., events "GFBR can no longer be guaranteed” and "GFBR can be guaranteed again") from the NG-RAN node 3 via the AMF 5. Additionally or alternatively, based on the PCC rules, the SMF 6 may instruct the NG-RAN node 3 to report the QoS notification control information via the tunnel between the NG-RAN node 3 and the PSA UPF 8, and instruct the PSA UPF 8 to notify when the report is received as instructed. In this case, the SMF 6 can receive the QoS notification control information from the NG-RAN node 3 via the PSA UPF 8.
  • QoS notification control information i.e., events "GFBR can no longer be guaranteed" and "GFBR can be guaranteed again
  • the SMF 6 When the SMF 6 receives the notification "GFBR can no longer be guaranteed" from the NG-RAN node 3, it may forward the notification to the PCF 7. If the NG-RAN node 3 determines that the GFBR, PDB, and PER of the QoS profile can be fulfilled again for the QoS flow (for which a notification that "GFBR can no longer be guaranteed” was sent), the NG-RAN node 3 notifies the SMF 6 that "GFBR can be guaranteed” again. The SMF 6 may forward this notification to the PCF 7.
  • the NG-RAN node 3 determines that it cannot meet the GFBR, PDB or PER of the QoS profile, it shall send a notification to the SMF 6 that "GFBR can no longer be guaranteed". Before sending the notification that "GFBR can no longer be guaranteed" to the SMF 6, the NG-RAN node 3 shall check whether the GFBR, PDB and PER currently met by the NG-RAN node 3 match any of the alternative QoS profiles, according to the indicated priorities.
  • the NG-RAN node 3 shall indicate, together with its notification to the SMF 6, the reference to the matching Alternative QoS Profile with the highest priority. If no match is found, the NG-RAN node 3 sends a notification to the SMF 6 that "GFBR can no longer be guaranteed" and indicates that the lowest alternative QoS profile cannot be met (unless certain conditions in the NG-RAN node 3 require the release of NG-RAN resources for this GBR QoS flow, e.g. due to radio link failure or internal RAN congestion).
  • the alternative QoS profile indicates the combination of QoS parameters: PDB, PER, Averaging Window, GFBR to which the application traffic can adapt.
  • the NG-RAN node 3 If the NG-RAN node 3 has already sent a notification "GFBR can no longer be guaranteed" to the SMF 6 and determines that the currently satisfied GFBR, PDB or PER is different (better or worse) from the situation indicated in the previous notification, the NG-RAN node 3 sends a notification (i.e., "GFBR can no longer be guaranteed” or "GFBR can be guaranteed again") to the SMF 6 and indicates the current situation (unless certain conditions in the NG-RAN node 3 require the release of NG-RAN resources for this GBR QoS flow, e.g. due to radio link failure or internal RAN congestion).
  • a notification i.e., "GFBR can no longer be guaranteed” or "GFBR can be guaranteed again
  • the current situation is either that the QoS profile can be satisfied (which is implicit in the notification "GFBR can be guaranteed again" itself), that a different alternative QoS profile can be satisfied, or that the alternative QoS profile with the lowest priority cannot be satisfied.
  • the NG-RAN node 3 always attempts to satisfy the QoS profile, and if this is not possible, it attempts to satisfy an alternative QoS profile with a higher priority.
  • the SMF 6 may inform the PCF 7. In that case, the SMF 6 indicates the currently satisfied status to the PCF 7.
  • the SMF 6 uses NAS signaling to inform the UE 1 about the changes in QoS parameters (5QI, GFBR, MFBR, etc.) currently satisfied by the NG-RAN 2 for the QoS flow after the notification control has occurred.
  • QoS parameters 5QI, GFBR, MFBR, etc.
  • the NG-RAN node 3 and the AMF 5 support the PDU Session Resource Notify procedure.
  • One of the purposes of the PDU Session Resource Notify procedure is to notify that already established QoS flow(s) or PDU Session(s) for the UE 1 are released or are not fulfilled anymore or are fulfilled again by the NG-RAN node 3, for which notification control is required.
  • the procedure uses UE-associated or UE-specific signalling.
  • the NG-RAN node 3 initiates the procedure by sending a PDU SESSION RESOURCE NOTIFY message.
  • the PDU SESSION RESOURCE NOTIFY message contains information of PDU session resources or QoS flows that are released or are no longer filled or are refilled by the NG-RAN node 3. Specifically, for each PDU session for which some QoS flows are released or are no longer filled or are refilled by the NG-RAN node 3, the PDU SESSION RESOURCE NOTIFY message contains a PDU Session Resource Notify Transfer information element (IE).
  • IE PDU Session Resource Notify Transfer information element
  • the PDU Session Resource Notify Transfer IE may contain a QoS Flow Notify List IE.
  • the QoS Flow Notify List IE indicates a list of GBR QoS flows that are no longer fulfilled or will be fulfilled again by the NG-RAN node 3.
  • the QoS Flow Notify List IE contains a QoS Flow Identifier IE and a Notification Cause IE for each QoS flow contained in the list.
  • the Notification Cause IE may be of type ENUMERATED and indicate "fulfilled" or "not fulfilled".
  • the NG-RAN node 3 may indicate in the Current QoS Parameters Set Index IE an alternative QoS parameter set that can currently be fulfilled for the QoS flows indicated as no longer fulfilled.
  • the AMF5 Upon receiving a PDU SESSION RESOURCE NOTIFY message, the AMF5 transparently forwards, for each PDU session indicated in the PDU Session ID IE, a PDU Session Resource Notify Transfer IE to the SMF6 associated with that PDU session.
  • the SMF6 may initiate appropriate release or modification procedures on the 5GC4 side for the PDU session(s) or QoS flow(s) identified as no longer being satisfied.
  • a configuration example of the wireless communication system according to this embodiment is similar to the configuration example described with reference to Fig. 1.
  • This embodiment provides an improvement in QoS notification control.
  • FIG. 2 illustrates an example of the operation of a RAN node.
  • the RAN node may be the NG-RAN node 3 shown in FIG. 1.
  • the RAN node receives a QoS profile for a packet flow from a core network.
  • the core network may be the 5GC 4 shown in FIG. 1.
  • the packet flow may be a QoS flow in a PDU session.
  • the RAN node may receive the QoS profile for the packet flow in an initial context setup procedure, a PDU session resource setup procedure, or a PDU session resource modification procedure.
  • the QoS profile may include QoS parameters including 5QI, ARP, and GBFR.
  • the QoS profile may include a notification control parameter.
  • the notification control parameter may indicate that notification control is enabled for the QoS flow.
  • step 202 when sending a notification to the core network that the QoS profile is no longer met or is again met while maintaining the packet flow, the RAN node also informs the core network of the reason, cause, or factor(s) that led to that decision. More specifically, when sending a notification to the core network that the QoS profile is no longer met or is again met while maintaining the packet flow without releasing the packet flow or refusing to set up or modify the packet flow, the RAN node also informs the core network of the reason, cause, or factor(s) that led to that decision.
  • a situation in which a QoS profile is no longer satisfied may be a situation in which any of the alternative QoS profiles are satisfied. It may also be a situation in which even the lowest priority alternative QoS profile cannot be satisfied.
  • the reason, cause, or factor notified by the RAN node in step 202 may include a reason, cause, or factor that is due to measurements of queuing delay or system load.
  • the notification in step 202 may include an indication that the determination that the QoS profile is no longer being met or will again be met is based on, caused by, or related to measurements of queuing delay or system load.
  • the reason, cause or factor notified by the RAN node in step 202 may indicate a location or element within the RAN that led to or triggered the transmission of the QoS notification control information.
  • the notification in step 202 may indicate whether the determination that the QoS profile is no longer met or will be met again is due to a problem with the CU, the DU, or the radio link quality (or Radio Unit (RU)).
  • the notification in step 202 may indicate that the determination that the QoS profile of a packet flow is no longer met is due to a CU overload, a DU overload, or radio link quality degradation.
  • the notification in step 202 may indicate whether the determination that the QoS profile is no longer met or will be met again is due to a problem with the PDCP layer, the RLC layer, the MAC layer, or the PHY layer.
  • the notification in step 202 may indicate that the determination that the QoS profile of a packet flow is no longer met is due to congestion or overload of a PDCP entity or buffer for a radio bearer associated with the packet flow.
  • the notification of step 202 may indicate that the reason for the determination is congestion or overload of an RLC entity or buffer.
  • the notification of step 202 may indicate that the reason for the determination is a scheduling delay in a MAC entity.
  • the reason, cause or factor notified by the RAN node in step 202 may include a reason, cause or factor due to a request for radio bandwidth by another higher priority GBR QoS flow.
  • the notification in step 202 may include an indication that the determination that the QoS profile is no longer satisfied is based on, caused by or related to a request for radio bandwidth by another higher priority GBR QoS flow.
  • the notification in step 202 may also include an indication that the determination that the QoS profile is again satisfied is based on, caused by or related to no longer requiring radio bandwidth by another higher priority GBR QoS flow (or the other higher priority GBR QoS flow being released).
  • the reason, cause or factor notified by the RAN node in step 202 may include a reason, cause or factor that is based on the result of Artificial Intelligence (AI) or Machine Learning (ML) inference.
  • the reason, cause or factor notified by the RAN node in step 202 may include information indicative of a reason, cause or factor that is based on the result of inference using AI or ML.
  • the notification in step 202 may include an indication that the determination that the QoS profile is no longer met or will be met again is based on, caused by or related to the result of inference using a trained AI or ML model.
  • the reason, cause or factor notified by the RAN node in step 202 may include a reason, cause or factor due to a radio link failure or radio access network internal congestion.
  • the notification of step 202 may include an indication that the determination that the QoS profile is no longer met or will be met again is based on, caused by, or related to a radio link failure or radio access network internal congestion.
  • the RAN node may itself determine or generate the notification or indication of the reason, cause or factor that led to the decision. Alternatively, the RAN node may determine the notification or indication of the reason, cause or factor that led to the decision based on information received from another control node. Alternatively, the RAN node may receive the notification or indication of the reason, cause or factor that led to the decision from another control node.
  • the other control node may determine, by inference using a trained AI or ML model, that the QoS profile for a packet flow is not met or will be met again and inform the RAN node along with the reason that led to the decision.
  • the other control node may be a Near-Real-Time (RT) RAN Intelligent Controller (RIC) or a Non-RT RIC.
  • RT Near-Real-Time
  • RIC RAN Intelligent Controller
  • Non-RT RIC Non-RT RIC
  • the Near-RT RIC is a logical function that enables near real-time control and optimization of RAN elements and resources through granular data collection and actions over the E2 interface.
  • the Near-RT RIC hosts a set of applications called xApps and provides a set of commonly used platform functions to support the specific functions hosted by the xApps.
  • xApps are applications designed to run within the Near-RT RIC.
  • xApps execute in the Near-RT RIC as part of the RAN (O-RAN).
  • xApps are independent of the Near-RT RIC and can be provided by third parties.
  • xApps are used to provide radio resource management over the standardized E2 interface and E2 service model. For example, xApps receive data from the RAN and calculate and send back control actions as required.
  • the Non-RT RIC is a logical function within the Service Management and Orchestration (SMO) framework.
  • the Non-RT RIC consists of the Non-RT RIC framework and Non-RT RIC applications (rApps).
  • rApps are applications designed to run within the Non-RT RIC.
  • rApps execute within the Non-RT RIC as part of the SMO framework.
  • rApps leverage the functionality exposed by the Non-RT RIC to provide value-added services to support and facilitate RAN optimization and operations, such as policy guidance, enrichment information, configuration management, and data analytics.
  • the RAN node may send the notification of step 202 using the PDU Session Resource Notify procedure.
  • the RAN node may use a PDU SESSION RESOURCE NOTIFY message for the notification of step 202 including an indication of the reason, cause or factor that led to the decision.
  • the RAN node may send the notification of step 202 in the initial context setup procedure, the PDU session resource setup procedure or the PDU session resource modification procedure.
  • the RAN node may use an INITIAL CONTEXT SETUP RESPONSE, a PDU SESSION RESOURCE SETUP RESPONSE or a PDU SESSION RESOURCE MODIFY RESPONSE message for the notification of step 202 including an indication of the reason, cause or factor that led to the decision.
  • Figure 3 shows an example of the operation of a core network node in relation to the operation of the RAN node shown in Figure 2.
  • the core network node may be the AMF5 or SMF6 shown in Figure 1.
  • the core network node sends a QoS profile for a packet flow (e.g., QoS flow) to the RAN node.
  • the RAN node may be the NG-RAN node 3 shown in Figure 1.
  • the core network node e.g., SMF6
  • the core network node may send the QoS profile for a packet flow in an initial context setup procedure, a PDU session resource setup procedure, or a PDU session resource modification procedure.
  • the QoS profile may include QoS parameters including 5QI, ARP, and GBFR.
  • the QoS profile may include a notification control parameter, which may indicate that notification control is enabled for the QoS flow.
  • the core network node receives from the RAN node a first notification that the packet flow is maintained but the QoS profile is no longer met or is again met, together with a second notification of the reason, cause or factor that led to the determination that the QoS profile is no longer met or is again met. More specifically, the core network node receives from the RAN node a first notification that the packet flow is maintained but the QoS profile is no longer met or is again met, without the packet flow being released or the setup or modification of the packet flow being rejected, together with a second notification of the reason, cause or factor that led to the determination that the QoS profile is no longer met or is again met.
  • the core network node e.g., SMF 6
  • a situation in which a QoS profile is no longer satisfied may be a situation in which any of the alternative QoS profiles are satisfied. It may also be a situation in which even the lowest priority alternative QoS profile cannot be satisfied.
  • the message or information field containing or indicating the first and second notifications of step 302 may be sent in a notification control procedure (e.g., PDU Session Resource Notify procedure), an initial context setup procedure, a PDU Session Resource Setup procedure or a PDU Session Resource Modification procedure.
  • a notification control procedure e.g., PDU Session Resource Notify procedure
  • an initial context setup procedure e.g., PDU Session Resource Setup procedure
  • PDU Session Resource Modification procedure e.g., PDU Session Resource Modification procedure.
  • FIG. 4 shows an example of signaling between a RAN node 410 and a core network node 420.
  • the RAN node 410 may be the NG-RAN node 3 shown in FIG. 1.
  • the core network node 420 may be the AMF 5, SMF 6 or UPF 8 shown in FIG. 1.
  • the RAN node 410 sends a control message or information field to the core network node 420.
  • the control message or information field indicates that the QoS profile of a given (GBR) packet flow is not met or will be met again, together with the reason, cause, or factor(s) that led to the decision.
  • GLR QoS profile of a given
  • the RAN node 410 may send the control message or information field to the core network node 520 (e.g., SMF 6) via another core network node (e.g., AMF 5 or UPF 8).
  • the core network node 520 e.g., SMF 6
  • AMF 5 or UPF 8 another core network node
  • the control message or information field of step 401 may be sent in a notification control procedure (e.g., PDU Session Resource Notify procedure).
  • a notification control procedure e.g., PDU Session Resource Notify procedure.
  • the RAN node 410 may include in the control message or information field an indication of the reasons, causes or factors that led to or triggered this notification.
  • the control message or information field of step 401 may be sent in a procedure involving the establishment or setup of a new packet flow.
  • These procedures include, for example, an initial context setup procedure, a PDU session resource setup procedure, and a PDU session resource modification procedure.
  • the RAN node 410 may include in the response message a notification indicating that the QoS profile of the packet flow is not satisfied but an alternative QoS profile is satisfied.
  • the RAN node 410 may include in the control message or information field an indication of the reason, cause or factor that led to or triggered this notification.
  • control message or information field of step 401 may be sent in a procedure involving modification of an established packet flow (e.g., modification of a QoS profile). These procedures include, for example, PDU session modification procedures.
  • the RAN node 410 may include in the response message a notification indicating that the QoS profile of the packet flow is not satisfied but an alternative QoS profile is satisfied.
  • the RAN node 410 may include in the control message or information field an indication of the reasons, causes or factors that led to or triggered this notification.
  • FIG. 5 shows an example of signaling between a RAN node 510 and a core network node 520.
  • the RAN node 510 may be the NG-RAN node 3 shown in FIG. 1.
  • the core network node 520 may be the AMF 5 shown in FIG. 1.
  • the signaling in FIG. 5 is one example of the signaling in FIG. 4.
  • the RAN node 510 sends a PDU SESSION RESOURCE NOTIFY message to the core network node 520.
  • the PDU SESSION RESOURCE NOTIFY message indicates that the QoS profile of a (GBR) QoS flow is not met or will be met again, together with the reason, cause, or factor(s) that led to this decision.
  • Example reasons, causes, or factors notified by the RAN node 510 in step 501 are similar to those described above with respect to step 202.
  • the core network node 520 e.g., AMF 5
  • Figure 6 shows an example of signaling between a RAN node 610 and a core network node 620.
  • the RAN node 610 may be the NG-RAN node 3 shown in Figure 1.
  • the core network node 620 may be the AMF 5 shown in Figure 1.
  • the signaling in Figure 6 is one example of the signaling in Figure 4.
  • the RAN node 610 sends an INITIAL CONTEXT SETUP RESPONSE, a PDU SESSION RESOURCE SETUP RESPONSE or a PDU SESSION RESOURCE MODIFY RESPONSE message to the core network node 620.
  • the message indicates that the QoS profile of a (GBR) QoS flow is not met, along with the reason, cause, or factor(s) that led to this decision.
  • reasons, causes, or factors notified by the RAN node 610 in step 601 are similar to those described above with respect to step 202.
  • the core network node 620 e.g., AMF 5
  • FIG. 7 shows an example of the format of the improved PDU Session Resource Notify Transfer information element (IE).
  • the PDU Session Resource Notify Transfer IE is included in the PDU SESSION RESOURCE NOTIFY message sent from the NG-RAN node to the AMF.
  • the PDU Session Resource Notify Transfer IE may contain a QoS Flow Notify List IE.
  • the QoS Flow Notify List IE indicates a list of GBR QoS flows that are no longer fulfilled or will be fulfilled again by the NG-RAN node.
  • the QoS Flow Notify List IE contains a QoS Flow Identifier IE and a Notification Cause IE for each QoS flow included in the list.
  • the Notification Cause IE is of type ENUMERATED and can indicate "fulfilled” or "not fulfilled". Additionally, in the example of FIG. 7, the Notification Cause IE is extended to indicate the reason, cause, or factor that led to the determination that the QoS profile of the GBR QoS flow is not met or will be met again.
  • the NG-RAN node 3 may set a value in the Notification Cause IE shown in FIG. 7 to indicate the reason, cause, or factor that led to the determination that the QoS profile of the GBR QoS flow is not met or will be met again.
  • the Notification Cause IE in Figure 7 may indicate "not fulfilled due to radio link failure", “not fulfilled due to RAN internal congestion”, “fulfilled due to radio link recovery”, “fulfilled due to RAN internal congestion resolution”, or “fulfilled due to mobility”. Additionally or alternatively, the Notification Cause IE may indicate "not fulfilled due to AI/ML result", or “fulfilled due to AI/ML result”. Additionally or alternatively, the Notification Cause IE may indicate "not fulfilled due to bandwidth requested by other higher priority GBR QoS Flows" or "fulfilled due to absence of bandwidth requests by other high priority GBR QoS flows”.
  • Figure 8 shows another example of the format of the improved PDU Session Resource Notify Transfer IE.
  • the QoS Flow Notify List IE in the PDU Session Resource Notify Transfer IE is extended to include a Cause IE for each QoS flow included in the list.
  • This Cause IE is used to indicate the reason, cause or factor that led to the decision that the QoS profile of the GBR QoS flow is not met or will be met again.
  • the set of values that the Cause IE can indicate as radio network layer causes is extended compared to the existing one.
  • the NG-RAN node 3 may set the Cause IE shown in Figure 8 to a value indicating the reason, cause or factor that led to the decision that the QoS profile of the GBR QoS flow is not met or will be met again.
  • the Cause IE in FIG. 8 may indicate "radio link failure", “RAN internal congestion”, “radio link recovery”, or “RAN internal congestion resolution”. Additionally or alternatively, the Cause IE may indicate "AI/ML result”. Additionally or alternatively, the Cause IE may indicate "bandwidth requested by other higher priority GBR QoS Flows", or "absence of bandwidth requests by other high priority GBR QoS flows”.
  • FIG 9 shows an example of the format of the improved PDU Session Resource Modify Response Transfer IE.
  • the PDU Session Resource Modify Response Transfer IE is included in the PDU SESSION RESOURCE MODIFY RESPONSE message sent from the NG-RAN node to the AMF.
  • the PDU Session Resource Modify Response Transfer IE may include a QoS Flow Add or Modify Response List IE.
  • the QoS Flow Add or Modify Response List IE indicates a list of QoS flows that have been added or modified by the NG-RAN node.
  • the QoS Flow Add or Modify Response List IE includes a QoS Flow Identifier IE for each QoS flow included in the list.
  • the QoS Flow Add or Modify Response List IE may include a Current QoS Parameters Set Index IE for each GBR QoS flow included in the list.
  • the Current QoS Parameters Set Index IE indicates the index to the alternative QoS parameter set that is currently satisfied.
  • the QoS Flow Add or Modify Response List IE is extended to include a Cause IE for each GBR QoS flow included in the list.
  • This Cause IE is used to indicate the reason, cause or factor that led to the determination that the QoS profile of the added or modified GBR QoS flow is not met.
  • the set of values that the Cause IE can indicate as radio network layer causes is extended compared to the existing one.
  • the NG-RAN node 3 may set the Cause IE shown in FIG. 9 to a value indicating the reason, cause or factor that led to the determination that the QoS profile of the added or modified GBR QoS flow is not met.
  • the Cause IE in FIG. 9 may indicate "radio link failure" or "RAN internal congestion”. Additionally or alternatively, the Cause IE may indicate "AI/ML result”. Additionally or alternatively, the Cause IE may indicate "bandwidth requested by other higher priority GBR QoS Flows".
  • FIG 10 shows an example of the format of the improved PDU Session Resource Setup Response Transfer IE.
  • the PDU Session Resource Setup Response Transfer IE is included in the INITIAL CONTEXT SETUP RESPONSE message or the PDU SESSION RESOURCE SETUP RESPONSE message sent from the NG-RAN node to the AMF.
  • the PDU Session Resource Setup Response Transfer IE may include a QoS Flow Setup Response List IE.
  • the QoS Flow Setup Response List IE indicates a list of QoS flows set up by the NG-RAN node.
  • the QoS Flow Setup Response List IE includes a QoS Flow Identifier IE for each QoS flow included in the list.
  • the QoS Flow Setup Response List IE may include a Current QoS Parameters Set Index IE for each GBR QoS flow included in the list.
  • the Current QoS Parameters Set Index IE indicates the index to the alternative QoS parameter set that is currently satisfied.
  • the QoS Flow Setup Response List IE is extended to include a Cause IE for each GBR QoS flow included in the list.
  • This Cause IE is used to indicate the reason, cause or factor that led to the determination that the QoS profile of the set up GBR QoS flow is not met.
  • the set of values that the Cause IE can indicate as radio network layer causes is extended compared to the existing one.
  • the NG-RAN node 3 may set the Cause IE shown in Figure 10 to a value indicating the reason, cause or factor that led to the determination that the QoS profile of the set up GBR QoS flow is not met.
  • the Cause IE in FIG. 10 may indicate "radio link failure" or "RAN internal congestion”. Additionally or alternatively, the Cause IE may indicate "AI/ML result”. Additionally or alternatively, the Cause IE may indicate "bandwidth requested by other higher priority GBR QoS Flows".
  • the RAN node may inform the core network of the reason (or cause, or factor) that led to the decision regarding the QoS notification control information (i.e., notification that the QoS profile (e.g., GFBR) of the packet flow is not met or will be met again).
  • the notification of this reason, cause, or factor may be useful for the core network (e.g., SMF 6 or PCF 7 or both) to optimize the action taken with respect to that packet flow (e.g., QoS flow).
  • the core network may take the reason, cause, or factor notification into account to determine an updated QoS profile for the packet flow.
  • the core network may inform the RAN node of the updated QoS profile.
  • the core network may use the reason, cause, or factor notification as input data to a trained AI/ML model for performing inference. Additionally or alternatively, the core network may utilize the reason, cause, or factor notification for training an AI/ML model.
  • the core network may modify the action taken with respect to a packet flow based on the content of the notification of the reason, cause, or factor that caused the QoS profile (e.g., GFBR) of the packet flow to be determined to be unmet or remet.
  • the core network e.g., SMF6 or PCF7 or both
  • AF Application Function
  • the core network may decide whether to request the Application Function (AF) to lower the downlink GFBR of the packet flow.
  • AF Application Function
  • Second Embodiment A configuration example of the wireless communication system according to this embodiment is similar to the configuration example described with reference to Fig. 1. This embodiment provides an improvement in QoS notification control.
  • FIG. 11 illustrates an example of the operation of a RAN node.
  • the RAN node may be the NG-RAN node 3 shown in FIG. 1.
  • the RAN node receives a QoS profile for a packet flow from a core network.
  • the core network may be the 5GC 4 shown in FIG. 1.
  • the packet flow may be a QoS flow in a PDU session.
  • the RAN node may receive the QoS profile for the packet flow in an initial context setup procedure, a PDU session resource setup procedure, or a PDU session resource modification procedure.
  • the QoS profile may include QoS parameters including 5QI, ARP, and GBFR.
  • the QoS profile includes a notification control parameter, which may indicate that notification control is enabled for the QoS flow.
  • the RAN node when sending a notification to the core network that the QoS profile is no longer met or is again met while maintaining the packet flow, the RAN node also informs the core network of the RAN node's preferred values of one or more QoS parameters for that packet flow.
  • These one or more QoS parameters may include at least one of GFBR, 5QI, PDB, or PER.
  • a situation in which a QoS profile is no longer satisfied may be a situation in which any of the alternative QoS profiles are satisfied. It may also be a situation in which even the lowest priority alternative QoS profile cannot be satisfied.
  • the RAN node may determine the preferred values of one or more QoS parameters on its own. In some implementations, the RAN node may determine the preferred values of one or more QoS parameters on its own through inference using a trained AI or ML model. Alternatively, the RAN node may determine the preferred values of one or more QoS parameters based on information received from another control node. Alternatively, the RAN node may receive the preferred values of one or more QoS parameters from another control node. The other control node may determine the preferred values of one or more QoS parameters through inference using a trained AI or ML model. The other control node may be a Near-RT RIC or a Non-RT RIC.
  • the RAN node may send the notification of step 1102 using a PDU Session Resource Notify procedure.
  • the RAN node may use a PDU SESSION RESOURCE NOTIFY message for the notification of step 1102 including an indication of the QoS parameter values preferred for the RAN node.
  • the RAN node may send the notification of step 1102 in an initial context setup procedure, a PDU session resource setup procedure or a PDU session resource modification procedure.
  • the RAN node may use an INITIAL CONTEXT SETUP RESPONSE, a PDU SESSION RESOURCE SETUP RESPONSE or a PDU SESSION RESOURCE MODIFY RESPONSE message for the notification of step 1102 including an indication of the QoS parameter values preferred for the RAN node.
  • the core network node 12 illustrates an example of the operation of a core network node in relation to the operation of the RAN node illustrated in FIG. 11.
  • the core network node may be the AMF5 or SMF6 illustrated in FIG. 1.
  • the core network node sends a QoS profile for a packet flow (e.g., QoS flow) to the RAN node.
  • the RAN node may be the NG-RAN node 3 illustrated in FIG. 1.
  • the core network node e.g., SMF6
  • the core network node may send the QoS profile for a packet flow in an initial context setup procedure, a PDU session resource setup procedure, or a PDU session resource modification procedure.
  • the QoS profile may include QoS parameters including 5QI, ARP, and GBFR.
  • the QoS profile may include a notification control parameter, which may indicate that notification control is enabled for the QoS flow.
  • the core network node receives a first notification from the RAN node that the packet flow is maintained but the QoS profile is no longer met or is met again, together with a second notification indicating preferred values for the RAN node of one or more QoS parameters for the packet flow.
  • These one or more QoS parameters may include at least one of GFBR, 5QI, PDB or PER.
  • the core network node e.g., SMF 6
  • a message or information field containing or indicating the first and second notifications of step 1202 may be sent in a PDU Session Resource Notify procedure, an Initial Context Setup procedure, a PDU Session Resource Setup procedure or a PDU Session Resource Modification procedure.
  • the RAN node 1310 shows an example of signaling between a RAN node 1310 and a core network node 1320.
  • the RAN node 1310 may be the NG-RAN node 3 shown in FIG. 1.
  • the core network node 1320 may be the AMF5, SMF6 or UPF8 shown in FIG. 1.
  • the RAN node 1310 sends a control message or information field to the core network node 1320.
  • the control message or information field indicates that the QoS profile of a (GBR) packet flow is not met or is met again, together with values preferred by the RAN node 1310 for one or more QoS parameters for the packet flow.
  • GLR QoS profile of a
  • the RAN node 1310 may send the control message or information field to the core network node 1320 (e.g., SMF6) via another core network node (e.g., AMF5 or UPF8).
  • the core network node 1320 e.g., SMF6
  • another core network node e.g., AMF5 or UPF8.
  • the control message or information field of step 1301 may be sent in a notification control procedure (e.g., PDU Session Resource Notify procedure).
  • a notification control procedure e.g., PDU Session Resource Notify procedure
  • the RAN node 1310 may include one or more preferred QoS parameter values in the control message or information field.
  • control message or information field of step 1301 may be sent in a procedure involving modification of an established packet flow (e.g., modification of a QoS profile).
  • These procedures include, for example, a PDU session resource modification procedure.
  • the RAN node 1310 may include in the response message a notification indicating that the QoS profile of the packet flow is not satisfied but an alternative QoS profile is satisfied.
  • the RAN node 1310 may include one or more preferred QoS parameter values in the control message or information field.
  • FIG 16 shows an example of the format of the improved PDU Session Resource Notify Transfer IE.
  • the PDU Session Resource Notify Transfer IE is included in the PDU SESSION RESOURCE NOTIFY message sent from the NG-RAN node to the AMF.
  • the PDU Session Resource Notify Transfer IE may contain a QoS Flow Notify List IE.
  • the QoS Flow Notify List IE indicates a list of GBR QoS flows that are no longer fulfilled or will be fulfilled again by the NG-RAN node.
  • the QoS Flow Notify List IE contains a QoS Flow Identifier IE and a Notification Cause IE for each QoS flow included in the list.
  • the QoS Flow Notify List IE is extended to include a Preferred GFBR IE, Preferred PDB IE, and Preferred PER IE for each GBR QoS flow included in the list. These IEs can be used to indicate the preferred GFBR, PDB, and PER values for the RAN node (e.g., NG-RAN node 3) for that GBR QoS flow.
  • FIG 17 shows an example of the format of the improved PDU Session Resource Modify Response Transfer IE.
  • the PDU Session Resource Modify Response Transfer IE is included in the PDU SESSION RESOURCE MODIFY RESPONSE message sent from the NG-RAN node to the AMF.
  • the PDU Session Resource Modify Response Transfer IE may include a QoS Flow Add or Modify Response List IE.
  • the QoS Flow Add or Modify Response List IE indicates a list of QoS flows that have been added or modified by the NG-RAN node.
  • the QoS Flow Add or Modify Response List IE includes a QoS Flow Identifier IE for each QoS flow included in the list.
  • the QoS Flow Add or Modify Response List IE may include a Current QoS Parameters Set Index IE for each GBR QoS flow included in the list.
  • the Current QoS Parameters Set Index IE indicates the index to the alternative QoS parameter set that is currently satisfied.
  • the QoS Flow Add or Modify Response List IE is extended to include a Preferred GFBR IE, Preferred PDB IE, and Preferred PER IE for each GBR QoS flow included in the list. These IEs can be used to indicate the preferred GFBR, PDB, and PER values for the RAN node (e.g., NG-RAN node 3) for that GBR QoS flow.
  • FIG 18 shows an example of the format of the improved PDU Session Resource Setup Response Transfer IE.
  • the PDU Session Resource Setup Response Transfer IE is included in the INITIAL CONTEXT SETUP RESPONSE message or the PDU SESSION RESOURCE SETUP RESPONSE message sent from the NG-RAN node to the AMF.
  • the PDU Session Resource Setup Response Transfer IE may include a QoS Flow Setup Response List IE.
  • the QoS Flow Setup Response List IE indicates a list of QoS flows set up by the NG-RAN node.
  • the QoS Flow Setup Response List IE includes a QoS Flow Identifier IE for each QoS flow included in the list.
  • the QoS Flow Setup Response List IE may include a Current QoS Parameters Set Index IE for each GBR QoS flow included in the list.
  • the Current QoS Parameters Set Index IE indicates the index to the alternative QoS parameter set that is currently satisfied.
  • the QoS Flow Setup Response List IE is extended to include a Preferred GFBR IE, Preferred PDB IE, and Preferred PER IE for each GBR QoS flow included in the list. These IEs can be used to indicate the preferred GFBR, PDB, and PER values for the RAN node (e.g., NG-RAN node 3) for that GBR QoS flow.
  • a RAN node may inform the core network of preferred QoS parameter values for the RAN node for a packet flow when sending QoS notification control information (i.e., notification that the QoS profile (e.g., GFBR) of the packet flow is not met or is met again) for that packet flow.
  • QoS notification control information i.e., notification that the QoS profile (e.g., GFBR) of the packet flow is not met or is met again
  • Notification of preferred QoS parameter values for the RAN node may be useful for the core network (e.g., SMF 6 or PCF 7 or both) to optimize actions to be taken with respect to that packet flow (e.g., QoS flow).
  • the core network may take into account notification of preferred QoS parameter values for the RAN node to determine an updated QoS profile for the packet flow.
  • the core network may inform the RAN node of the updated QoS profile.
  • the core network may use the preferred QoS parameter values for the RAN node as input data to a trained AI/ML model for performing inference. Additionally or alternatively, the core network may utilize the preferred QoS parameter values for the RAN node for training an AI/ML model.
  • the NG-RAN node may also inform the core network of a more preferred GFBR value, PDB value, or PER value, or any combination of these.
  • the more preferred GFBR value, PDB value, and PER value may be better than the GFBR value, PDB value, and PER value specified in the (non-alternative) QoS profile for the GBR QoS flow.
  • the core network e.g., SMF6 or PCF7 or both
  • the core network may set a higher GFBR value, a lower PDB value, or a lower PER value for the GBR QoS flow based on the notification from the NG-RAN node.
  • the core network e.g., SMF6 or PCF7 or both
  • FIG. 19 is a block diagram showing an example of the configuration of an NG-RAN node 3.
  • the configurations of other RAN nodes 410 and 510, etc. may also be similar to the configuration shown in FIG. 19.
  • the NG-RAN node 3 includes a Radio Frequency (RF) transceiver 1901, a network interface 1903, a processor 1904, and a memory 1905.
  • the RF transceiver 1901 performs analog RF signal processing to communicate with UEs including UE1.
  • the RF transceiver 1901 may include multiple transceivers.
  • the RF transceiver 1901 is coupled to an antenna array 1902 and a processor 1904.
  • the RF transceiver 1901 receives modulation symbol data from the processor 1904, generates a transmit RF signal, and provides the transmit RF signal to the antenna array 1902.
  • the RF transceiver 1901 also generates a baseband receive signal based on the receive RF signal received by the antenna array 1902 and supplies the baseband receive signal to the processor 1904.
  • the RF transceiver 1901 may include an analog beamformer circuit for beamforming.
  • the analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.
  • the network interface 1903 is used to communicate with network nodes (e.g., other RAN nodes, as well as nodes within the 5GC4).
  • the network interface 1903 may include, for example, an IEEE 802.3 series compliant network interface card (NIC).
  • NIC network interface card
  • the processor 1904 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
  • the processor 1904 may include multiple processors.
  • the processor 1904 may include a modem processor (e.g. Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g. Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing.
  • DSP Digital Signal Processor
  • MPU Micro Processing Unit
  • digital baseband signal processing by processor 1904 may include signal processing of the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer.
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical
  • control plane processing by processor 1904 may include processing of Non-Access Stratum (NAS) messages, RRC messages, MAC Control Elements (CEs), and Downlink Control Information (DCI).
  • NAS Non-Access Stratum
  • RRC Radio Link Control
  • CEs MAC Control Elements
  • DCI Downlink Control Information
  • the processor 1904 may include a digital beamformer module for beamforming.
  • the digital beamformer module may include a Multiple Input Multiple Output (MIMO) encoder and precoder.
  • MIMO Multiple Input Multiple Output
  • the memory 1905 is comprised of a combination of volatile and non-volatile memory.
  • the volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof.
  • the non-volatile memory is Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof.
  • the memory 1905 may include storage located remotely from the processor 1904. In this case, the processor 1904 may access the memory 1905 via the network interface 1903 or an I/O interface not shown.
  • the memory 1905 may store one or more software modules (computer programs) 1906 including instructions and data for performing the processing by the NG-RAN node 3 described in the above-mentioned embodiments.
  • the processor 1904 may be configured to read the software modules 1906 from the memory 1905 and execute them to perform the processing by the NG-RAN node 3 described in the above-mentioned embodiments.
  • the control plane processing and operations performed by the NG-RAN node 3 described in the above embodiment can be realized by a processor 1904 and a memory 1905 storing a software module 1906.
  • the NG-RAN node 3 may not include the RF transceiver 1901 (and the antenna array 1902).
  • FIG. 20 shows an example configuration of the AMF 5.
  • the configurations of other core network nodes such as the SMF 6, PCF 7, and UPF 8 may also be similar to the configuration shown in FIG. 20.
  • the AMF 5 includes a network interface 2001, a processor 2002, and a memory 2003.
  • the network interface 2001 is used, for example, to communicate with other Network Functions (NFs) or nodes.
  • the network interface 2001 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series.
  • NIC network interface card
  • Processor 2002 may be, for example, a microprocessor, an MPU, or a CPU. Processor 2002 may include multiple processors.
  • Memory 2003 is composed of volatile memory and non-volatile memory. Memory 2003 may include multiple physically independent memory devices. Volatile memory is, for example, SRAM or DRAM, or a combination of these. Non-volatile memory is MROM, EEPROM, flash memory, or a hard disk drive, or any combination of these. Memory 2003 may include storage located away from processor 2002. In this case, processor 2002 may access memory 2003 via network interface 2001 or an I/O interface.
  • the memory 2003 may store one or more software modules (computer programs) 2004 including instructions and data for performing the processing by AMF5 described in the above-mentioned embodiments.
  • the processor 2002 may be configured to read the software modules 2004 from the memory 2003 and execute them to perform the processing by AMF5 described in the above-mentioned embodiments.
  • the informing means is adapted to use an INITIAL CONTEXT SETUP RESPONSE message, a PDU SESSION RESOURCE SETUP RESPONSE message, or a PDU SESSION RESOURCE MODIFY RESPONSE message to indicate the reason, cause, or factor to the core network.
  • a radio access network node as claimed in claim 1. (Appendix 6) The reasons, causes, or factors include reasons, causes, or factors based on measurements of queuing delay or system load; 6. A radio access network node according to any one of claims 1 to 5.
  • the reasons, causes, or factors include reasons, causes, or factors due to radio link failure, due to radio access network internal congestion, or due to artificial intelligence or machine learning inference results; 6.
  • the situation where the QoS profile is no longer satisfied includes a situation where any of one or more alternative QoS profiles provided by the core network is satisfied, or even a situation where a lowest priority alternative QoS profile of the one or more alternative QoS profiles cannot be satisfied.
  • a radio access network node according to any one of claims 1 to 7. (Appendix 9) the indication of the reason, cause, or factor is taken into account by the core network to determine an updated QoS profile for the packet flow. 9.
  • the QoS profile includes QoS parameters including 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), and Guaranteed Flow Bit Rate (GBFR). 17.
  • QoS Quality of Service
  • ARP Allocation and Retention Priority
  • GBFR Guaranteed Flow Bit Rate
  • a radio access network node according to any one of claims 1 to 16.
  • (Appendix 18) receiving from a core network a Quality of Service (QoS) profile for a packet flow; and, when sending a notification to the core network that the QoS profile is no longer met or that the QoS profile will be met again while maintaining the packet flow without releasing the packet flow or rejecting the setup or modification of the packet flow, also informing the core network of reasons, causes, or factors that led to a determination that the QoS profile is no longer met or that the QoS profile will be met again.
  • QoS Quality of Service
  • a method performed by a radio access network node comprising: (Appendix 19) The notifying includes using a PDU SESSION RESOURCE NOTIFY message to indicate the reason, cause, or factor to the core network. 19. The method according to claim 18. (Appendix 20) The notifying includes setting a value indicating the reason, cause, or factor to a Notification Cause information element in a QoS Flow Notify List information element in a PDU Session Resource Notify Transfer information element in the PDU SESSION RESOURCE NOTIFY message. 20. The method according to claim 19.
  • the notifying includes setting a value indicating the reason, cause, or factor to a Cause information element in a QoS Flow Notify List information element in a PDU Session Resource Notify Transfer information element in the PDU SESSION RESOURCE NOTIFY message.
  • the informing includes using an INITIAL CONTEXT SETUP RESPONSE message, a PDU SESSION RESOURCE SETUP RESPONSE message, or a PDU SESSION RESOURCE MODIFY RESPONSE message to indicate the reason, cause, or factor to the core network. 19.
  • the reasons, causes, or factors include reasons, causes, or factors based on measurements of queuing delay or system load; 23.
  • the method according to any one of claims 18 to 22. (Appendix 24)
  • the reasons, causes, or factors include reasons, causes, or factors due to radio link failure, due to radio access network internal congestion, or due to artificial intelligence or machine learning inference results; 23.
  • the method of any one of claims 18 to 22. (Appendix 25)
  • the situation where the QoS profile is no longer satisfied includes a situation where any of one or more alternative QoS profiles provided by the core network is satisfied, or even a situation where a lowest priority alternative QoS profile of the one or more alternative QoS profiles cannot be satisfied. 25.
  • Appendix 26 the indication of the reason, cause, or factor is taken into account by the core network to determine an updated QoS profile for the packet flow. 26. The method of any one of claims 18 to 25. (Appendix 27) the notification of the reason, cause, or factor causes the core network to determine and inform the radio access network node of an updated QoS profile for the packet flow. 27. The method of any one of claims 18 to 26. (Appendix 28) and further indicating to the core network preferred values for the radio access network node of one or more QoS parameters for the packet flow upon sending an indication to the core network that the QoS profile is no longer satisfied. 28. The method according to any one of claims 18 to 27.
  • the one or more QoS parameters include at least one of a Guaranteed Flow Bit Rate (GBFR), a 5G QoS Identifier (5QI), a Packet Delay Budget (PDB), or a Packet Error Rate (PER); 29.
  • GBFR Guaranteed Flow Bit Rate
  • 5QI 5G QoS Identifier
  • PDB Packet Delay Budget
  • PER Packet Error Rate
  • the method according to claim 28. (Appendix 30) generating a notification indicating a preferred value for the one or more QoS parameters based on results of the artificial intelligence or machine learning based inference received from a Radio Access Network (RAN) Intelligent Controller (RIC). 30.
  • RAN Radio Access Network
  • RIC Radio Access Network Intelligent Controller
  • the indication of the preferred values of the one or more QoS parameters is taken into account by the core network to determine an updated QoS profile for the packet flow.
  • a program for causing a computer to perform a method for a radio access network node comprising: (Appendix 36) The notifying includes using a PDU SESSION RESOURCE NOTIFY message to indicate the reason, cause, or factor to the core network. 36.
  • the informing includes using an INITIAL CONTEXT SETUP RESPONSE message, a PDU SESSION RESOURCE SETUP RESPONSE message, or a PDU SESSION RESOURCE MODIFY RESPONSE message to indicate the reason, cause, or factor to the core network.
  • 36 The program according to claim 35.
  • the reasons, causes, or factors include reasons, causes, or factors based on measurements of queuing delay or system load; 40.
  • the reasons, causes, or factors include reasons, causes, or factors due to radio link failure, due to radio access network internal congestion, or due to artificial intelligence or machine learning inference results; 40.
  • the one or more QoS parameters include at least one of a Guaranteed Flow Bit Rate (GBFR), a 5G QoS Identifier (5QI), a Packet Delay Budget (PDB), or a Packet Error Rate (PER); 46.
  • the program according to claim 45. The method further comprises generating a notification indicating a preferred value for the one or more QoS parameters based on results of artificial intelligence or machine learning based inference received from a Radio Access Network (RAN) Intelligent Controller (RIC). 47.
  • RAN Radio Access Network
  • RIC Radio Access Network
  • the indication of the preferred values of the one or more QoS parameters is taken into account by the core network to determine an updated QoS profile for the packet flow.
  • the program according to any one of appendices 45 to 47. the notification of the preferred values of the one or more QoS parameters causes the core network to determine and inform the radio access network node of an updated QoS profile for the packet flow. 49.
  • the program according to any one of appendices 45 to 48. The packet flow is a Quality of Service (QoS) flow included in a protocol data unit (PDU) session. 50.
  • the QoS profile includes QoS parameters including 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), and Guaranteed Flow Bit Rate (GBFR). 50.
  • 5QI 5G QoS Identifier
  • ARP Allocation and Retention Priority
  • GBFR Guaranteed Flow Bit Rate
  • (Appendix 52) means for sending a Quality of Service (QoS) profile for the packet flow to a radio access network node; means for receiving from the radio access network node a first indication that the packet flow is not released or the set-up or modification of the packet flow is not rejected, and the packet flow is maintained but the QoS profile is no longer met or the QoS profile will be met again, together with a second indication of reasons, causes or factors that led to a determination that the QoS profile is no longer met or will be met again;
  • a core network node comprising:
  • the receiving means is adapted to receive a PDU SESSION RESOURCE NOTIFY message including the first and second notifications. 53.
  • the first and second notifications are both indicated by a Notification Cause information element in a QoS Flow Notify List information element in a PDU Session Resource Notify Transfer information element in the PDU SESSION RESOURCE NOTIFY message.
  • the second notification is indicated by a Cause information element in a QoS Flow Notify List information element in a PDU Session Resource Notify Transfer information element in the PDU SESSION RESOURCE NOTIFY message.
  • the receiving means is adapted to receive an INITIAL CONTEXT SETUP RESPONSE message, a PDU SESSION RESOURCE SETUP RESPONSE message, or a PDU SESSION RESOURCE MODIFY RESPONSE message containing the first and second notifications; 53.
  • the receiving means being adapted to receive the first and second notifications via one or more other core network nodes.
  • the reasons, causes, or factors include reasons, causes, or factors based on measurements of queuing delay or system load; 58.
  • the reasons, causes, or factors include reasons, causes, or factors due to radio link failure, due to radio access network internal congestion, or due to artificial intelligence or machine learning inference results; 58.
  • the situation where the QoS profile is no longer satisfied includes a situation where any of one or more alternative QoS profiles provided by the core network node is satisfied, or a situation where even a lowest priority alternative QoS profile of the one or more alternative QoS profiles cannot be satisfied. 60.
  • 61. A core network node according to any one of Additions 52 to 60.
  • (Appendix 62) means for informing the radio access network node of the updated QoS profile.
  • 62. A core network node as described in Supplementary Note 61.
  • the receiving means is adapted to receive, together with the first and second notifications, a third notification from the radio access network node indicating preferred values for the radio access network node of one or more QoS parameters for the packet flow.
  • 63. A core network node according to any one of Additions 52 to 62.
  • the one or more QoS parameters include at least one of a Guaranteed Flow Bit Rate (GBFR), a 5G QoS Identifier (5QI), a Packet Delay Budget (PDB), or a Packet Error Rate (PER); A core network node as described in Supplementary Note 63.
  • (Appendix 65) means for taking into account the preferred values of the one or more QoS parameters to determine an updated QoS profile for the packet flow. 65.
  • (Appendix 66) means for informing the radio access network node of the updated QoS profile.
  • the packet flow is a Quality of Service (QoS) flow included in a protocol data unit (PDU) session. 7.
  • QoS Quality of Service
  • PDU protocol data unit
  • the QoS profile includes QoS parameters including 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), and Guaranteed Flow Bit Rate (GBFR).
  • 5QI 5G QoS Identifier
  • ARP Allocation and Retention Priority
  • GBFR Guaranteed Flow Bit Rate
  • (Appendix 69) sending a Quality of Service (QoS) profile for a packet flow to a radio access network node; and receiving a first notification from the radio access network node that the packet flow is not released or the setup or modification of the packet flow is not rejected and the packet flow is maintained but the QoS profile is no longer met or the QoS profile will be met again, together with a second notification of reasons, causes, or factors that led to a determination that the QoS profile is no longer met or will be met again.
  • a method performed by a core network node comprising: (Appendix 70) receiving includes receiving a PDU SESSION RESOURCE NOTIFY message containing the first and second notifications; 70. The method of claim 69.
  • the first and second notifications are both indicated by a Notification Cause information element in a QoS Flow Notify List information element in a PDU Session Resource Notify Transfer information element in the PDU SESSION RESOURCE NOTIFY message. 71. The method of claim 70. (Appendix 72) The second notification is indicated by a Cause information element in a QoS Flow Notify List information element in a PDU Session Resource Notify Transfer information element in the PDU SESSION RESOURCE NOTIFY message. 71. The method of claim 70.
  • the receiving includes receiving an INITIAL CONTEXT SETUP RESPONSE message, a PDU SESSION RESOURCE SETUP RESPONSE message, or a PDU SESSION RESOURCE MODIFY RESPONSE message that includes the first and second notifications.
  • the reasons, causes, or factors include reasons, causes, or factors based on measurements of queuing delay or system load; 75. The method of any one of claims 69 to 74.
  • the reasons, causes, or factors include reasons, causes, or factors due to radio link failure, due to radio access network internal congestion, or due to artificial intelligence or machine learning inference results; 75.
  • the method of any one of claims 69 to 74. (Appendix 77)
  • the situation where the QoS profile is no longer satisfied includes a situation where any of one or more alternative QoS profiles provided by the core network node is satisfied, or a situation where even a lowest priority alternative QoS profile of the one or more alternative QoS profiles cannot be satisfied. 77.
  • the method of any one of claims 69 to 77. (Appendix 79) and informing the radio access network node of the updated QoS profile. 79. The method of claim 78. (Appendix 80) and receiving, together with the first and second notifications, a third notification from the radio access network node indicating preferred values for the radio access network node of one or more QoS parameters for the packet flow. 80. The method of any one of claims 69 to 79. (Appendix 81)
  • the one or more QoS parameters include at least one of a Guaranteed Flow Bit Rate (GBFR), a 5G QoS Identifier (5QI), a Packet Delay Budget (PDB), or a Packet Error Rate (PER); 81.
  • GBFR Guaranteed Flow Bit Rate
  • 5QI 5G QoS Identifier
  • PDB Packet Delay Budget
  • PER Packet Error Rate
  • the method of claim 80 taking into account the preferred values of the one or more QoS parameters to determine an updated QoS profile for the packet flow. 82. The method according to claim 80 or 81. (Appendix 83) and informing the radio access network node of the updated QoS profile. 83. The method of claim 82. (Appendix 84) The packet flow is a Quality of Service (QoS) flow included in a protocol data unit (PDU) session. 84. The method of any one of claims 69 to 83. (Appendix 85) The QoS profile includes QoS parameters including 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), and Guaranteed Flow Bit Rate (GBFR). 5.
  • 5QI 5G QoS Identifier
  • ARP Allocation and Retention Priority
  • GBFR Guaranteed Flow Bit Rate

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un nœud de réseau d'accès radio (RAN) selon la présente invention reçoit, en provenance d'un réseau central, un profil de QoS (qualité de service) pour un flux de paquets. Lorsque le nœud RAN transmet, au réseau central, une notification indiquant qu'un profil QoS n'est plus satisfait ou sera à nouveau satisfaite tout en maintenant le flux de paquets sans libérer le flux de paquets ou sans refuser d'établir ou de corriger le flux de paquets, le nœud RAN notifie également au réseau central la raison, la cause ou un facteur qui a conduit à la détermination que le profil QoS n'est plus satisfait ou sera à nouveau satisfait. Ceci contribue à une amélioration de la commande de notifications entre un RAN et un réseau central.
PCT/JP2024/024903 2023-08-02 2024-07-10 Nœud de réseau d'accès radio, nœud de réseau central et procédés associés Pending WO2025028194A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023-126636 2023-08-02
JP2023126636 2023-08-02

Publications (1)

Publication Number Publication Date
WO2025028194A1 true WO2025028194A1 (fr) 2025-02-06

Family

ID=94395155

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/024903 Pending WO2025028194A1 (fr) 2023-08-02 2024-07-10 Nœud de réseau d'accès radio, nœud de réseau central et procédés associés

Country Status (1)

Country Link
WO (1) WO2025028194A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116419329A (zh) * 2021-12-30 2023-07-11 中国移动通信有限公司研究院 QoS调整方法、装置、无线接入网设备及核心网设备

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116419329A (zh) * 2021-12-30 2023-07-11 中国移动通信有限公司研究院 QoS调整方法、装置、无线接入网设备及核心网设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3 Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.413, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. V17.5.0, 28 June 2023 (2023-06-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 584, XP052409606 *

Similar Documents

Publication Publication Date Title
JP6687744B2 (ja) 無線通信システムにおけるデータを送受信するための方法及びこれを支援する装置
US11206580B2 (en) Communication method and communications apparatus
WO2019228214A1 (fr) Procédé et appareil pour établir une porteuse radio et surveiller un flux de services
US20160234851A1 (en) Data transmission apparatus and method
CN115836564A (zh) 具有中继功能的无线网络中的增强调度
CN111770531A (zh) 获取数据包延迟参数的方法、系统和装置
US11202338B2 (en) Session establishment method and apparatus
US20220386164A1 (en) Device and method for supporting quality of service in wireless communication system
US12133096B2 (en) Data transmission method, apparatus, and device
JP6518382B2 (ja) 通信システムにおけるデータフロートランスポートのための改善されたプライオリティハンドリング
US20170070895A1 (en) Traffic management in the mobile network
US20250350997A1 (en) Communication method, apparatus, and system
US20140369197A1 (en) Method, apparatus, system, computer program and computer program product for mitigating end user congestion in a wireless network
JP7516678B2 (ja) ハンドオーバ手順に基づくメッセージ送信方法、装置、機器及びプログラム
CN117641467A (zh) 一种通信方法及装置
US9246817B1 (en) System and method of managing traffic flow in a communication network
CN111373834B (zh) 用于建立数据无线承载的客户端设备、接入网设备、方法及计算机程序
WO2025028194A1 (fr) Nœud de réseau d'accès radio, nœud de réseau central et procédés associés
US9042317B2 (en) Non-guaranteed bit rate bearer control in a mobile communication network
CN116321281A (zh) 多接入数据分流方法、装置、电子设备及存储介质
KR20210105197A (ko) 무선 통신 시스템에서 서비스 품질을 지원하기 위한 방법 및 장치
CN107431940B (zh) 用于在无线通信系统中控制上行链路的覆盖的方法和装置
US20240306149A1 (en) Intelligent carrier aggregation for two-way traffic
CN120979600A (zh) 控制信息发送方法、装置、设备、存储介质和程序产品
WO2025139729A1 (fr) Procédé et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24848853

Country of ref document: EP

Kind code of ref document: A1