WO2021111213A1 - Régulation de charge de fonction de plan utilisateur - Google Patents

Régulation de charge de fonction de plan utilisateur Download PDF

Info

Publication number
WO2021111213A1
WO2021111213A1 PCT/IB2020/060533 IB2020060533W WO2021111213A1 WO 2021111213 A1 WO2021111213 A1 WO 2021111213A1 IB 2020060533 W IB2020060533 W IB 2020060533W WO 2021111213 A1 WO2021111213 A1 WO 2021111213A1
Authority
WO
WIPO (PCT)
Prior art keywords
upf
load
policy
network slice
data collection
Prior art date
Application number
PCT/IB2020/060533
Other languages
English (en)
Inventor
Miguel Angel MUÑOZ DE LA TORRE ALONSO
Miguel Angel PUENTE PESTAÑA
Rodrigo Alvarez Dominguez
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to EP20807132.4A priority Critical patent/EP4070529A1/fr
Publication of WO2021111213A1 publication Critical patent/WO2021111213A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/101—Server selection for load balancing based on network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/088—Load balancing or load distribution among core entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0925—Management thereof using policies

Definitions

  • the present disclosure generally relates to wireless communication networks, and more particularly relates to controlling user plane function (UPF) load in Third Generation Partnership Project (3GPP) networks.
  • UPF user plane function
  • the 3GPP is a telecommunication standards organization that produces specifications defining numerous technologies in support of wireless networks, such networks including (for example) Long Term Evolution (LTE) networks and Fifth Generation (5G) networks.
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • a fundamental characteristic of a 5G core network is the separation of the control and user planes.
  • the control plane is the portion of the network that handles signaling traffic
  • the user plane is the portion of the network that handles network user traffic. Due to the ever- increasing amount of user traffic wireless communication networks are transporting (e.g., to stream high-definition video), the user plane is increasingly likely to be overloaded relative to the control plane.
  • Embodiments of the present disclosure generally relate to methods of performing load control of the User Plane Function (UPF) in a wireless communication network.
  • Particular embodiments take advantage of machine learning (ML) techniques that may be leveraged to autonomously perform UPF load control, e.g., on a per network slice basis.
  • ML machine learning
  • Such embodiments may reduce the amount of traffic handled by one or more UPFs while maintaining or even increasing the number of user sessions being serviced and/or mitigating negative impact to user experience.
  • One or more embodiments of the present disclosure includes a method implemented in a network node of a wireless communication network.
  • the method comprises receiving load control information identifying a network slice and indicating a target load for the network slice.
  • the method further comprises triggering data collection at a user plane function (UPF) that is in the identified network slice and that has a load above the target load.
  • the method further comprises determining, based on a result of the data collection received from the UPF, a policy that achieves the target load at the UPF.
  • the method further comprises signaling a Policy Control Function (PCF) in the identified network slice to control the load of the UPF in accordance with the policy.
  • PCF Policy Control Function
  • the method further comprises discovering the UPF that is in the identified network slice and that has the load above the target load in response to receiving the load control information.
  • the method further comprises discovering the PCF in the identified network slice to control the load of the UPF in response to receiving the result of the data collection.
  • the method further comprises sending a notification indicating that load control has completed in response to determining that the UPF is below the desired target load.
  • the method further comprises registering with a Network Repository Function (NRF) that the network node supports user plane load control.
  • NRF Network Repository Function
  • the load control information further comprises an analytics identifier that indicates that user plane load control is desired.
  • triggering data collection at the UPF comprises notifying the UPF of the target load, and the result of the data collection is received from the UPF responsive to the load of the UPF exceeding the target load.
  • triggering data collection at the UPF comprises sending an event identifier corresponding to a type of data to be collected.
  • the method further comprises receiving the result of the data collection from the UPF in an event notification message.
  • determining the policy that achieves the target load at the UPF comprises determining a plurality of policy actions that achieves the target load at the UPF.
  • the method further comprises triggering data collection at a further UPF that is in the identified network slice and that has a load above the target load, determining, based on a result of the data collection received from the further UPF, a further policy that achieves the target load at the further UPF, and signaling the PCF in the identified network slice to control the load of the further UPF in accordance with the further policy.
  • determining the policy that achieves the target load at the UPF comprises determining a suggested Quality of Service action.
  • determining the policy that achieves the target load at the UPF comprises determining an Adaptive Bit Rate policy.
  • determining the policy that achieves the target load at the UPF comprises determining a bandwidth limitation.
  • the method further comprises, responsive to signaling the PCF in the identified network slice to control the load of the UPF and after the load of the UPF has been controlled, receiving notification of a successful operation from the PCF.
  • receiving the load control information comprises receiving the load control information from an Operations and Maintenance (OAM) node.
  • OAM Operations and Maintenance
  • the method further comprises notifying the OAM node that the load has been controlled in accordance with the load control information.
  • the network node comprises a Network Data Analytics Function (NWDAF).
  • NWDAF Network Data Analytics Function
  • One or more embodiments of the present disclosure includes a network node of a wireless communication network.
  • the network node is configured to receive load control information identifying a network slice and indicating a target load for the network slice.
  • the network node is further configured to trigger data collection at a user plane function (UPF) that is in the identified network slice and that has a load above the target load.
  • the network node is further configured to determine, based on a result of the data collection received from the UPF, a policy that achieves the target load at the UPF.
  • the network node is further configured to signal a Policy Control Function (PCF) in the identified network slice to control the load of the UPF in accordance with the policy.
  • PCF Policy Control Function
  • the network node is further configured to perform any of the methods described herein.
  • the network node comprises interface circuitry configured to couple the network node to the wireless communication network.
  • the network node further comprises processing circuitry communicatively coupled to the interface circuitry and whereby the network node is configured as described herein.
  • the network node further comprises a memory communicatively coupled to the processing circuitry, and the memory contains instructions executable by the processing circuitry whereby the network node is configured as described herein.
  • inventions include a carrier containing such a computer program, the carrier being one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
  • FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
  • FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
  • FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
  • FIG. 1 A block diagram illustrating an exemplary computing environment in accordance with the present disclosure.
  • Figure 1 is a schematic block diagram illustrating an example wireless communication network architecture according to one or more embodiments of the present disclosure.
  • Figure 2 is a flow diagram illustrating an example method according to one or more embodiments of the present disclosure.
  • Figures 3A through 3E are swimming lane diagrams illustrating a more detailed example method according to one or more embodiments of the present disclosure.
  • Figure 4 illustrates an example network node according to one or more embodiments of the present disclosure.
  • example embodiments of the disclosure will be described below in the context of a 5G wireless communication network.
  • Those skilled in the art will appreciate that the methods and apparatus herein described are not limited to use in 5G networks but may also be used in wireless communication networks operating according to other standards. Such embodiments may be particularly well suited for (but not limited to) derivatives of, and/or successors to, 5G networks, for example.
  • FIG. 1 illustrates an example architecture of a wireless communication network 10 according to one or more embodiments of the present disclosure.
  • the wireless communication network 10 comprises a radio access network (RAN) 20 and a core network 30 employing a service-based architecture.
  • the RAN 20 comprises one or more base stations 25 providing radio access to UEs 100 operating within the wireless communication network 10.
  • the base stations 25 are also referred to as gNodeBs (gNBs).
  • the core network 30 provides a connection between the RAN 20 and other packet data networks, such as the Internet Protocol (IP) Multimedia Subsystem (IMS) or the Internet.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the core network 30 comprises a plurality of network functions (NFs), such as a User Plane Function (UPF) 35, an Access and Mobility Management Function (AMF) 40, a Session Management Function (SMF) 45, a Policy Control Function (PCF) 50, a Unified Data Management (UDM) function 55, an Authentication Server function (AUSF) 60, a Network Exposure Function (NEF) 70, a Network Repository Function (NRF) 75, a Network Slice Selection Function (NSSF) 80, and a Network Data Analytics Function (NWDAF) 65.
  • NFs comprise logical entities that reside in one or more core network nodes, which may be implemented by one or more processors, hardware, firmware, or a combination thereof.
  • the functions may reside in a single core network node or may be distributed among two or more core network nodes.
  • the various NFs e.g., SMF 45, AMF 40, etc.
  • the wireless communication network 10 uses a services model in which the NFs query the NRF 75 or other NF discovery node to discover and communicate with each other.
  • the 5G core (5GC) network is designed to support network slicing.
  • Network slicing allows the use of virtualized networks to separate networks designed for different purposes.
  • Each network slice provides customized features and connectivity specifically tailored for a specific purpose, and executes on a shared, distributed infrastructure that provides high availability and flexibility.
  • the Global System for Mobile Communications Association Network Group 116 (GSMA NG.116) describes a set of attributes that can be used by an operator to define a network slice type (NEST). These parameters include the maximum number of connections (e.g., concurrent Packet Data Unit (PDU) sessions) supported by the network slice and the maximum number of users (e.g., user equipment (UEs)) supported by the network slice. These attributes provide useful input to scale the network slice and provides enough physical resources to the network slice. There is a significant difference between a network slice designed to serve 10 users and a network slice designed to serve 1 ,000,000 users. Typically, either the maximum number of connections or the maximum number of terminals is defined by the NEST. The NEST can, in some cases define both the maximum number of connections and the maximum number of terminals supported by the network slice.
  • PDU Packet Data Unit
  • UEs user equipment
  • One aspect of the present disclosure comprises mechanisms for controlling the load of a UPF 35, particularly with respect to a given network slice in the network.
  • embodiments of the present disclosure include particular enhancements to the NWDAF 65, PCF 50, SMF 45, and/or UPF 35, as will be disclosed in further detail below.
  • the NWDAF 65 represents an operator-managed network analytics logical function.
  • the NWDAF 65 is part of the architecture specified in 3GPP TS 23.501 and uses the mechanisms and interfaces specified for the 5GC and Operations, Administration, and Maintenance (OAM).
  • OAM Operations, Administration, and Maintenance
  • the NWDAF 65 may interact with different entities in the network for different purposes.
  • the NWDAF 65 may trigger, request, and/or receive data collection based on event subscription, provided by AMF 40, SMF 45, PCF 50, UDM 55, an Application Function (AF) (e.g., directly or via NEF 70), and/or an OAM.
  • the NWDAF 65 may additionally or alternatively retrieve information from data repositories (e.g.
  • UDR Universal Data Repository
  • the NWDAF 65 may additionally or alternatively provide analytics to consumers on demand.
  • the PCF 50 supports a unified policy framework to govern the behavior of the network.
  • the PCF 50 may provide Policy and Charging Control (PCC) rules to the SMF 45.
  • PCC Policy and Charging Control
  • the SMF 45 supports, e.g., session establishment, modification, and release, as well as policy related functionalities like termination of interfaces towards policy control functions, charging data collection, support of charging interfaces and/or control/coordination of charging data collection at the UPF 35.
  • the SMF 45 receives PCC rules from the PCF 50 and configures the UPF 35 accordingly (e.g., through the N4 reference point using Packet Forwarding Control Protocol (PFCP).
  • PFCP Packet Forwarding Control Protocol
  • the SMF 45 controls the packet processing in the UPF 35 by establishing, modifying and/or deleting PFCP sessions and by provisioning (e.g., adding, modifying and/or deleting) Packet Detection Rules (PDRs), Forwarding Action Rules (FARs), Quality of Service (QoS) Enforcement Rules (QERs), and/or Usage Reporting Rules (URRs) per PFCP session.
  • PDRs Packet Detection Rules
  • FARs Forwarding Action Rules
  • QoS Quality of Service
  • QERs Quality of Service
  • URRs Usage Reporting Rules
  • a PFCP session may correspond to an individual PDU session or a standalone PFCP session not tied to any PDU session.
  • Each PDR contains Packet Detection Information (PDI) specifying the traffic filters and/or signatures against which incoming packets are matched.
  • PDR Packet Detection Information
  • Each PDR is associated with rules that provide the set of instructions to apply to packets matching the PDI.
  • These rules include one FAR that contains instructions related to the processing of the packets (e.g., forward, duplicate, drop, or buffer packets) with or without notifying the CP function about the arrival of a DL packet.
  • the rules may also include zero, one, or more QERs that contain instructions related to the QoS enforcement of the traffic.
  • the rules may also include zero, one, or more URRs that contain instructions related to traffic measurement and reporting.
  • the UPF 35 supports the handling of user plane traffic based on the rules received from the SMF 45.
  • the UPF 35 may perform packet inspection (e.g., through PDRs) and one or more enforcement actions. These enforcement actions may include, for example, traffic steering, QoS, and/or Charging/Reporting (e.g., through FARs, QERs, URRs).
  • one or more NFs may identify one or more network slices using Network Slice Selection Assistance Information (NSSAI), which is a collection of Single NSSAIs (S-NSSAIs) that may be used to identify network slices.
  • NSSAI Network Slice Selection Assistance Information
  • S-NSSAIs Single NSSAIs
  • up to eight (8) S-NSSAIs may be included in the NSSAI sent in signaling messages between a UE 100 and the network 10.
  • a single UE 100 may, at most, use eight network slices at a time.
  • the UE 100 sends the S-NSSAI to the network 10 in a request (or other signaling message) to assist the network in selecting a particular network slice instance (NSI).
  • An S-NSSAI may comprise a Slice/Service type (SST), which refers to the expected features and services offered by the network slice.
  • SST Slice/Service type
  • currently defined service types include Enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), Massive Internet of Things (MloT), vehicle-to-vehicle (V2V) communications and vehicle-to-everything (V2X) communications.
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra Reliable Low Latency Communications
  • MloT Massive Internet of Things
  • V2V vehicle-to-vehicle
  • V2X vehicle-to-everything
  • SD Slice Differentiator
  • the S-NSSAI may be associated with a Public Land Mobile Network (PLMN) that is identified by a PLMN Identifer (PLMN ID).
  • PLMN Public Land Mobile Network
  • PLMN ID PLMN Identifer
  • a UE 100 may provide the AMF 40 or SMF 45 with a S-NSSAI when the UE 100 is connected to an access network in the PLMN associated with the S-NSSAI.
  • the S-NSSAI can have network-specific values, standard values, or some combination thereof.
  • PFCP load/overload control procedures may include a variety of approaches, which may (for example) be compatible with (or suitable for incorporation into) 3GPP TS 29.244.
  • a simple load control procedure may be used mainly for load balancing.
  • the SMF 45 prioritizes selection of UPFs 35 with less load.
  • the overload control procedure may define mitigation actions (i.e., in case of overload) that are based on not allowing new sessions to be established (e.g., through message throttling, redirection and prioritization).
  • mitigation actions i.e., in case of overload
  • embodiments that incorporate such an approach may be effective at controlling load, it should be noted that not allowing new sessions to be established may directly and negatively impact the user ' s experience, which would not be desirable.
  • NFs may register NF load information in the NRF 75 so that when a consumer (e.g., SMF 45) triggers a discovery procedure, this load information can be used to achieve load balancing (e.g., when SMF 45 triggers a UPF 35 selection procedure).
  • a consumer e.g., SMF 45
  • load balancing e.g., when SMF 45 triggers a UPF 35 selection procedure.
  • Such approaches may be compatible or suitable for incorporation into 3GPP TS 29.510, for example.
  • These embodiments may also support subscription to NF load changes. However, the resulting notifications produced under such embodiments may be quite demanding on the network (e.g., in terms of network traffic).
  • Other embodiments may include different network functions (e.g. the UPF 35) sending load information to an OAM so that Performance Measurements (PM) or statistics may be taken.
  • PM Performance Measurements
  • traditional 5G networks do not define a procedure regarding what action(s) an OAM should perform in response to particular conditions (e.g., if a UPF load goes above a certain threshold).
  • the NWDAF 65 may perform NF load analytics and provide those analytics (e.g., in the form of statistics or predictions or both) to other entities in the network.
  • traditional 5G networks limit load analytics to the AMF 40, Non-3GPP Interworking Function (N3IWF, not shown), SMF 45, and PCF 50. That is, the UPF 35 is not included in the NF load analytics performed by a traditional NWDAF 65 (e.g., as discussed in 3GPP TS 29.288).
  • User plane NFs like the UPF 35 have a high risk of becoming overloaded, largely due to the exponential increase of user traffic (mainly due to video streaming applications).
  • control plane NFs like the AMF 40, SMF 45, PCF 50, and NEF 70 which only need to handle control plane signaling
  • user plane NFs are far more likely to suffer an overload.
  • embodiments of the present disclosure may include traffic optimization techniques (Transmission Control Protocol (TCP)/Quick User Datagram Protocol (UDP) Internet Connections (QUIC) optimization, Adaptive Bit Rate (ABR) shaping, etc) that reduce the amount of traffic handled by UPFs, while also maintaining support for at least the same number of user sessions and mitigating the negative impact of overloading on the user ' s experience.
  • TCP Transmission Control Protocol
  • UDP Quick User Datagram Protocol
  • ABR Adaptive Bit Rate
  • embodiments are directed to implementing 5G networks as Smart Networks, and in particular, provide UPF load control procedures that may be fully automated and minimally impact existing network operability.
  • UPF load control procedures as may be known in traditional 3GPP 5GC are still far from providing such solutions.
  • embodiments of the present disclosure address one or more of the problems described above.
  • Particular embodiments propose to leverage the NWDAF 65 (e.g. using ML techniques) to automate control of the UPF load.
  • FIG. 2 illustrates an example method 200 implemented by an NWDAF 65.
  • the method 200 comprises receiving load control information identifying a network slice and indicating a target load for the network slice (block 205).
  • the method 200 further comprises triggering data collection at a user plane function (UPF) 35 that is in the identified network slice and that has a load above the target load (block 210).
  • the method 200 further comprises determining, based on a result of the data collection received from the UPF 35, a policy that achieves the target load at the UPF 35 (block 215).
  • the method further comprises signaling a PCF 50 in the identified network slice to control the load of the UPF 35 in accordance with the policy (block 220).
  • the method 200 further comprises discovering the UPF 35 that is in the identified network slice and that has the load above the target load in response to receiving the load control information (block 225). Additionally or alternatively, in accordance with particular embodiments, the method 200 may comprise discovering the PCF in the identified network slice to control the load of the UPF in response to receiving the result of the data collection from the UPF 35 (block 230).
  • triggering the data collection may comprise indicating a particular event-id to the UPF in order to obtain certain information in response.
  • receiving the result of the data collection may comprise receiving a percentage of audio/video streaming traffic relative to the total traffic volume and/or one or more UE-IDs where audio/video streaming traffic has been detected.
  • the NWDAF 65 may be pre-configured with one or more policies that may be applied to reduce UPF load, e.g. on a per slice type basis.
  • the NWDAF 65 may be preconfigured with a policy that may be effective to reduce UPF load for MBB types of slices.
  • policies may include an ABR shaping policy (e.g., to be applied to ABR streaming traffic such as Audio and/or Video streaming), Bandwidth (BW) limitation (e.g., to be applied to all traffic of only Heavy Users, which are defined as subscribers consuming more than a threshold amount of traffic, which is typically set quite high).
  • some embodiments include receiving one or more such policies and determining the policy that achieves the target load may comprise selecting one of the received policies.
  • the NWDAF 65 may use the result of the data collection and apply ML techniques to determine the policy that will achieve the desired target load. Indeed, the NWDAF 65 may use information obtained from the above events, and determine suggested policy actions to achieve the desired target load on a per UPF instance basis.
  • the NWDAF 65 determine the ABR shaping level/s to be applied. For Heavy users, the NWDAF 65 may determine the BW limitation level/s to be applied.
  • the NWDAF 65 may, for each UE-ID obtained, signal the PCF 50 to apply a policy that such that the PCF 50 creates/updates a corresponding PCC rule (i.e., corresponding to the above policies) and sends it to an SMF 45.
  • the SMF 45 may then trigger, towards the UPF 35, a PFCP Session Modification procedure with the corresponding policies.
  • the UPF may then detect traffic and apply a corresponding policy (e.g., ABR shaping for Audio/Video Streaming traffic and/or BW limitation for heavy users).
  • the method 200 further comprises sending a notification indicating that load control has completed in response to determining that the UPF 35 is below the target load (block 235).
  • embodiments of the present disclosure may automate the control of user plane load on a per slice basis using an NWDAF 65 (e.g., by applying ML techniques).
  • NWDAF 65 e.g., by applying ML techniques.
  • Figures 3A through 3E illustrate a more detailed example of automating control of user plane load for a MBB slice.
  • Figure 3 is a swimming lane diagram illustrating signaling between entities within a wireless communication network 10.
  • Figures 3A through 3E illustrates forty steps, particular embodiments may include additional, fewer, or different steps from those illustrated therein, consistent with the discussion above and/or variations as further described below.
  • Analytic- ID UP_LOAD_CONTROL
  • the NWDAF 65 is preconfigured with the suggested policies to be applied to reduce the UPF load on a per slice type basis.
  • the NWDAF 65 is preconfigured with an ABR shaping policy to be applied to ABR streaming traffic (e.g., to Audio and Video streaming) and/or a BW limitation policy to be applied to all the traffic of only Heavy Users (i.e., subscribers consuming more than a threshold amount of traffic).
  • the NWDAF may additionally or alternatively be preconfigured with one or more other policies that may be applied to reduce the UPF load, e.g., a TCP Optimization policy to be applied to TCP traffic and/or a QUIC Optimization policy to be applied to QUIC traffic.
  • the UPF 35 has registered with the NRF that it supports the Event-IDs AUDIO_VIDEO_STREAMING,
  • a consumer wants the user plane load for a certain slice (e.g., MBB1) to be below a certain threshold (e.g. 70%).
  • a certain threshold e.g. 70%.
  • the consumer e.g. OAM
  • the consumer triggers a Nnwdaf_AnalyticsSubscription Subscribe message towards a previously discovered NWDAF 65 instance.
  • the NWDAF 65 accepts the request and answers the consumer (e.g. OAM) with a successful Nnwdaf_AnalyticsSubscription response message.
  • the NWDAF 65 triggers UPF discovery in order to identify UPF instances (i.e., preferably all) that pertain to the MBB1 slice and which are above the target load threshold of 70%.
  • the NWDAF 65 sends an Nnrf NFDiscovery message towards the NRF 75.
  • the NWDAF 65 may perform discovery of UPFs that have load above a certain threshold.
  • the NRF 75 checks the registered NFProfiles and responds to the NWDAF 65 with a list of UPF instances matching the criteria in Step 4 above.
  • the NWDAF 65 triggers data collection from the UPF instances in the list received from the NRF 75.
  • the NWDAF 65 triggers towards the relevant UPF 65 instance a Nupf_EventExposure Subscribe message.
  • the network slice identifier may be particularly useful according to embodiments in which a given UPF 35 instance serves different network slices concurrently.
  • Event-ID UPF_LOAD
  • the Nupf_EventExposure Subscribe further comprises a load threshold (e.g. 70%).
  • the UPF 65 triggers a notification when the current load is equal or above the threshold.
  • Event-ID HEAVY_USERS
  • the Nupf_EventExposure Subscribe further comprises a heavy user category.
  • heavy users may be categorized in accordance with the amount of traffic they generate.
  • the UPF 35 responds to the NWDAF 65 with an indication that the subscription request has bene accepted.
  • the UPF 35 activates the requested events.
  • the UPF 35 monitors the load (e.g., CPU and Memory resources) and reports either periodically or when the current load is equal or above a certain threshold (e.g. 70%).
  • the UPF 35 detects audio/video streaming traffic (e.g. using Deep Packet Inspection (DPI) techniques) and calculates the percentage of audio/video streaming traffic with respect to the total amount of traffic. The UPF 35 also calculates for which UE-IDs there is presence of audio/video streaming traffic.
  • DPI Deep Packet Inspection
  • a threshold amount of traffic e.g. using DPI techniques, in accordance with the criteria for being classified as a heavy user category as discussed above, which may be locally configured in the UPF 35 for each heavy user category.
  • the UPF 35 may calculate the percentage of heavy user ' s traffic (with respect to the total traffic volume) and identify the UE-IDs corresponding to heavy users.
  • the Load-Information comprises the UPF CPU and Memory usage for the identified slice.
  • the NWDAF 65 responds to the UPF 35 accordingly (e.g., to acknowledge the notification message indicating the UPF LOAD event identifier).
  • the NWDAF 65 responds to the UPF 35 accordingly (e.g., to acknowledge the notification message indicating the AUDIO_VIDEO_STREAMING event identifier).
  • the NWDAF 65 responds to the UPF 35 accordingly (e.g., to acknowledge the notification message indicating the HEAVYJJSERS event identifier).
  • the NWDAF 65 determines, on a per UPF instance basis, the suggested policy actions to achieve the desired target load.
  • the NWDAF 65 may use ML techniques and/or the information obtained from one or more of the above events. For example, for Audio/Video streaming traffic, the NWDAF 65 may determine the ABR shaping level (hereinafter referred to as an X value) to be applied. Additionally or alternatively, for Heavy users, the NWDAF 65 may determine the BW limitation level (hereinafter referred to as a Y value) to be applied.
  • X and Y values may be obtained by the NWDAF 65 by any appropriate means. For example, the X and/or Y value may be preconfigured in, or calculated by, the NWDAF 65.
  • the NWDAF 65 discovers the PCF 50 instance(s) in the slice.
  • the NWDAF 65 triggers a Nnrf NFDiscovery message towards the NRF 75.
  • the NRF 75 responds to the Nnrf NFDiscovery message sent by the NWDAF 65 with a list of PCF addresses.
  • a single PCF 50 is included in the list (i.e., as policy controller for the MBB1 slice).
  • other examples may include a plurality of PCF addresses in the list that correspond to respective PCF 50 instances.
  • the NWDAF 65 indicates to the identified PCF(s) 50 one or more suggested policies.
  • the NWDAF 65 triggers towards the PCF 50 a Npcf_PolicyControl Request message.
  • the PCF 50 decides to execute the suggested policies.
  • the PCF 50 updates the policies on a per UE-ID basis. For example, at Step 22, for each UE-ID in list A (i.e., for the UE-IDs in which Audio/Video Streaming has been detected), the PCF 50 requests ABR shaping for Audio/Video Streaming traffic.
  • ABR shaping at Step 23 the PCF 50 triggers, towards the SMF 45, a Nsmf PolicyControl Request message.
  • the Nsmf PolicyControl Request message comprises a UE-ID (i.e., from List A), a PCC rule (e.g., create, update).
  • the SMF 45 triggers a PFCP Session Modification.
  • the SMF 45 sends a PFCP Session Modification Request message towards the UPF 35.
  • the UPF 35 detects Audio/Video streaming traffic based on the PDR and applies ABR shaping to the target level (i.e., X, in this example) based on the above QER.
  • the UPF 35 answers the SMF 45 with a PFCP Session Modification Response.
  • the SMF 45 answers the PCF 50 with a Nsmf PolicyControl Response.
  • the PCF 50 requests a BW limitation for all user traffic with respect to that UE-ID.
  • the PCF 50 triggers towards the SMF 45 a Nsmf PolicyControl Request message.
  • the Nsmf PolicyControl Request message comprises a UE-ID (i.e., from List B), and a PCC rule (e.g., create, update).
  • the SMF 45 triggers a PFCP Session Modification.
  • the SMF 45 sends a PFCP Session Modification Request message towards the UPF 35.
  • the UPF 35 applies the BW limitation (e.g., of Y kbps) to all user traffic of the identified heavy user.
  • the UPF 35 answers the SMF 45 with a PFCP Session Modification Response.
  • the SMF 45 answers the PCF 50 with a Nsmf PolicyControl Response.
  • the consumer e.g. OAM
  • Figure 4 illustrates a network node 500 according to one or more embodiments that may be configured to function as an NWDAF 65, NRF 75, AMF 40, SMF 45, PCF 50, or UPF 35, for example.
  • the network node 500 comprises interface circuitry 520 and processing circuitry 530 that is communicatively coupled to the interface circuitry 520.
  • the network node 500 further comprises memory 540.
  • the interface circuitry 520 couples the network node 500 to a wireless communication network 10 and enables communication with other network nodes in a core network 30 of the wireless communication network 10.
  • the processing circuitry 530 controls the overall operation of the network node 500.
  • the processing circuitry 530 executes one or more computer programs 550 stored in memory 540 to perform one or more of the methods as herein described.
  • the processing circuitry 530 may comprise one or more microprocessors, hardware, firmware, or a combination thereof.
  • Memory 540 may comprises volatile memory and/or non-volatile memory for storing computer program code and data needed by the processing circuitry 530 for operation.
  • the memory 540 may comprise any tangible, non-transitory computer-readable storage medium for storing data including electronic, magnetic, optical, electromagnetic, or semiconductor data storage.
  • the memory 540 may store a computer program 550 comprising executable instructions that configure the processing circuitry 530 to implement the method 200 according to, e.g., Figure 2, Figures 3A through 3E, or one or more of the methods described above.
  • a computer program 550 in this regard may comprise one or more code modules corresponding to the means or units described above.
  • computer program instructions and configuration information are stored in a non-volatile memory, such as a ROM, erasable programmable read only memory (EPROM) or flash memory.
  • Temporary data generated during operation may be stored in a volatile memory, such as a random access memory (RAM).
  • the computer program for configuring the processing circuitry 530 as herein described may be stored in a removable memory, such as a portable compact disc, portable digital video disc, or other removable media.
  • the computer program 550 may also be embodied in a carrier such as an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • a computer program comprises instructions that, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above.
  • a computer program in this regard may comprise one or more code modules corresponding to the means or units described above.
  • Embodiments further include a carrier containing such a computer program.
  • This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.
  • Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device.
  • This computer program product may be stored on a computer readable recording medium.

Landscapes

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

Abstract

Selon l'invention, un nœud de réseau (500) d'un réseau de communication sans fil (10) reçoit (205) des informations de régulation de charge identifiant une tranche de réseau et indiquant une charge cible pour la tranche de réseau. Le nœud de réseau (500) déclenche (210) une collecte de données au niveau d'une fonction de plan utilisateur (UPF) (35) qui est dans la tranche de réseau identifiée et qui a une charge supérieure à la charge cible. Le nœud de réseau (500) détermine (215), sur la base d'un résultat de la collecte de données reçu en provenance de l'UPF (35), une politique qui atteint la charge cible au niveau de l'UPF (35), et signale (220) une fonction de commande de politique (PCF) (50) dans la tranche de réseau identifiée pour réguler la charge de l'UPF (35) conformément à la politique.
PCT/IB2020/060533 2019-12-05 2020-11-09 Régulation de charge de fonction de plan utilisateur WO2021111213A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20807132.4A EP4070529A1 (fr) 2019-12-05 2020-11-09 Régulation de charge de fonction de plan utilisateur

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP19383085 2019-12-05
EP19383085.8 2019-12-05

Publications (1)

Publication Number Publication Date
WO2021111213A1 true WO2021111213A1 (fr) 2021-06-10

Family

ID=68808275

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/060533 WO2021111213A1 (fr) 2019-12-05 2020-11-09 Régulation de charge de fonction de plan utilisateur

Country Status (2)

Country Link
EP (1) EP4070529A1 (fr)
WO (1) WO2021111213A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113811013A (zh) * 2021-09-10 2021-12-17 阿里巴巴达摩院(杭州)科技有限公司 集群容量动态调节方法、设备、存储介质和通信系统
CN114124686A (zh) * 2021-11-29 2022-03-01 新华三技术有限公司成都分公司 一种为ue会话分配用户面功能网元upf的方法及装置
WO2023035925A1 (fr) * 2021-09-09 2023-03-16 华为技术有限公司 Procédé, appareil et système de traitement de service
WO2024072880A1 (fr) * 2022-09-27 2024-04-04 Ofinno, Llc Configuration de notification de congestion de plan utilisateur

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019197467A1 (fr) * 2018-04-10 2019-10-17 Telefonaktiebolaget Lm Ericsson (Publ) Analyse distribuée dans un système 5gc

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019197467A1 (fr) * 2018-04-10 2019-10-17 Telefonaktiebolaget Lm Ericsson (Publ) Analyse distribuée dans un système 5gc

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL: "Moving Network Analytics functionality into 23.501", vol. SA WG2, no. Montreal, Canada; 20180226 - 20180302, 14 March 2018 (2018-03-14), XP051531753, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/TSG%5FSA/TSGS%5F79/Docs/SP%2D180091%2Ezip> [retrieved on 20180314] *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023035925A1 (fr) * 2021-09-09 2023-03-16 华为技术有限公司 Procédé, appareil et système de traitement de service
CN113811013A (zh) * 2021-09-10 2021-12-17 阿里巴巴达摩院(杭州)科技有限公司 集群容量动态调节方法、设备、存储介质和通信系统
CN113811013B (zh) * 2021-09-10 2023-11-10 阿里巴巴达摩院(杭州)科技有限公司 集群容量动态调节方法、设备、存储介质和通信系统
CN114124686A (zh) * 2021-11-29 2022-03-01 新华三技术有限公司成都分公司 一种为ue会话分配用户面功能网元upf的方法及装置
CN114124686B (zh) * 2021-11-29 2024-02-27 新华三技术有限公司成都分公司 一种为ue会话分配用户面功能网元upf的方法及装置
WO2024072880A1 (fr) * 2022-09-27 2024-04-04 Ofinno, Llc Configuration de notification de congestion de plan utilisateur

Also Published As

Publication number Publication date
EP4070529A1 (fr) 2022-10-12

Similar Documents

Publication Publication Date Title
US11438464B2 (en) Method of reporting traffic metrics by a user plane function, UPF, to a session management function, SMF, in a telecommunication network, as well as a corresponding UPF
WO2021111213A1 (fr) Régulation de charge de fonction de plan utilisateur
US11711471B2 (en) Methods of and devices for implementing and executing policy rules on a per application basis in a telecommunications system
US10848381B2 (en) Cross-domain service optimization
EP3780682A1 (fr) Procédé et dispositif d&#39;abonnement à un service
JP7269377B2 (ja) 移動通信ネットワークのネットワークスライスインスタンスに関するネットワーク解析及び／又は予測情報を提供するためのネットワーク解析コンポーネント及び方法。
JP7285342B2 (ja) 登録及び／又はセッション要求を処理するための通信ネットワーク構成及び方法
JP5727091B2 (ja) インテリジェントな輻輳存在通知サービス
CN112350841B (zh) 一种管理数据的获取方法及装置
EP4154497A1 (fr) Amélioration de la précision de classification dans des scénarios de resélection de fonction de plan utilisateur
CN111919501B (zh) 专用承载管理
US20220286904A1 (en) Technique for Controlling and Performing Data Traffic Handling in a Core Network Domain
JP2014155096A (ja) 通信ポリシルール動的変更システムおよび通信ポリシルールの動的変更方法
WO2019015755A1 (fr) Procédés et nœuds permettant de fournir ou de sélectionner un nœud de trafic utilisateur
EP4315777A1 (fr) Commande de charge de fonction de plan utilisateur (upf)
US20240107282A1 (en) Service Function Chaining Exposure in 5G Networks
EP3235314B1 (fr) Commande d&#39;accès de réseau local sans fil
US20240137276A1 (en) Controlling User Plane Function (UPF) Load
US20220394596A1 (en) Enforcement of maximum number of admitted terminals per network slice
WO2022003407A1 (fr) Recommandation de politiques de routage d&#39;informatique à la frontière (ec) basée sur des analyses d&#39;inférence causale
US11910306B2 (en) Methods, systems, and computer readable media for providing updated network slice information to a network slice selection function (NSSF)
JP2023544182A (ja) 通信ネットワーク構成及びネットワークコンポーネントの選択方法

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: 20807132

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020807132

Country of ref document: EP

Effective date: 20220705