WO2022003407A1 - Recommandation de politiques de routage d'informatique à la frontière (ec) basée sur des analyses d'inférence causale - Google Patents

Recommandation de politiques de routage d'informatique à la frontière (ec) basée sur des analyses d'inférence causale Download PDF

Info

Publication number
WO2022003407A1
WO2022003407A1 PCT/IB2020/057083 IB2020057083W WO2022003407A1 WO 2022003407 A1 WO2022003407 A1 WO 2022003407A1 IB 2020057083 W IB2020057083 W IB 2020057083W WO 2022003407 A1 WO2022003407 A1 WO 2022003407A1
Authority
WO
WIPO (PCT)
Prior art keywords
routing
node
policy
network
recommendation
Prior art date
Application number
PCT/IB2020/057083
Other languages
English (en)
Inventor
Miguel Angel PUENTE PESTAÑA
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)
Publication of WO2022003407A1 publication Critical patent/WO2022003407A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • This application relates generally to routing user traffic in a communications network, and more particularly to determining routing recommendations for user traffic in an Edge Cloud Data Network (ECDN) or a Central DN based on a causal inference analysis.
  • ECDN Edge Cloud Data Network
  • Central DN Central DN
  • Edge computing is a distributed computing model that situates the computational and data storage resources of a communications network closer to where they are needed by the User Equipment (UEs) that use them. Typically, edge computing applies to non-roaming and Local Break Out (LBO) roaming scenarios. Regardless, however, situating the resources as such enables network operators and third-party service providers to be hosted close to a UE's point of attachment to the network (e.g., an Access Point - AP). This, in turn, allows for a more efficient delivery of services to a user, reduces the end-to-end latency, and reduces the load on the transport network.
  • UE User Equipment
  • LBO Local Break Out
  • a 5G Core Network selects a User Plane Function (UPF) close to the UE and executes the traffic steering from the UPF to the local Data Network (DN) via a N6 interface.
  • UPF User Plane Function
  • DN Data Network
  • the selection of a UPF can be based, for example, on the UE's subscription data, the UE’s current location, the information from an Application Function (AF), a policy, or other related traffic rules.
  • AF Application Function
  • the 5G Core Network may also expose network information and capabilities to an Edge Computing Application Function. Further, depending on operator deployment, certain selected AFs can interact directly with the Control Plane Network Functions with which they need to interact. Other AFs, however, will need to use the external exposure framework via the Network Exposure Function (NEF).
  • NEF Network Exposure Function
  • edge computing can be supported by one or a combination of the following enabling functionalities.
  • the 5G Core Network can select/reselect a UPF to route the user traffic to a local DN;
  • the 5G Core Network selects the traffic to be routed to the applications in the local DN. This includes the use of a single Packet Data Unit (PDU) Session with multiple PDU Session Anchor(s) (e.g., UL CL/IPv6 multi-homing).
  • PDU Packet Data Unit
  • PDU Session Anchor(s) e.g., UL CL/IPv6 multi-homing
  • An AF may influence UPF selection/reselection and traffic routing via a Policy Control Function (PCF) or NEF;
  • PCF Policy Control Function
  • QoS Quality of Service
  • Charging The PCF provides rules for QoS Control and Charging for the traffic routed to the local DN;
  • LADN Local Area Data Networks
  • a DN Access Identifier identifies a user plane access to one or more DN(s) where applications are deployed.
  • DNAI DN Access Identifier
  • a Session Management Function decides whether to apply traffic routing in a PDU Session.
  • the SMF may use UL Classifier functionality or IPv6 multi-homing based on one or more DNAI(s) included in the Policy and Charging Control (PCC) rules.
  • PCC Policy and Charging Control
  • an AF may send requests to influence the SMF routing decisions. More particularly, the AF requests may influence UPF selection/reselection and allow the SMF to route user traffic to a local access of a DN identified by a DNAI.
  • An AF may also indicate the location of an application by means of a DNAI.
  • Randomized Controlled Trials RCTs
  • RCT randomized controlled trials
  • A/B tests One standard for inferring cause and effect is randomized controlled trials (RCTs) or A/B tests.
  • RCT is a type of scientific (often medical) experiment that aims to reduce certain sources of bias when testing the effectiveness of new treatments. This is accomplished by randomly allocating subjects into two or more groups, treating each group of subjects differently, and then comparing the results of their respective treatments to those of a measured response.
  • RCTs call for splitting a population of subjects (e.g., individuals) into at least two groups - a treatment/experimental group, to which a treatment is administered, and a control group to which nothing (or a placebo) is administered.
  • the respective outcomes of the treatment and non-treatment for the groups is then measured.
  • the effectiveness of the treatment can be inferred based on the difference in outcomes between the two groups.
  • the 3GPP is currently studying in potential solutions for EC based on analytics in “3GPP TR 23.700-91 V0.3.0 (2020-01 )” dated January 2020. Although no solutions have yet been proposed, section 5.1 .6 of this document details a use case that is directed to the support of edge computing.
  • TR 23.700-91 states that edge computing can improve the quality and experience of services by allowing huge data volume with low latency and high efficiency. Therefore, to support edge computing, 5GS introduced several enabling features, including giving the AF the ability to influence traffic routing, Local Area DN (LADN) functionality, and Uplink Classifier (UL CL)/Branching point functionality.
  • LADN Local Area DN
  • UL CL Uplink Classifier
  • a Network Data Analytics Function can enhance both edge computing and 5GS operations.
  • the NWDAF can be configured to assist with traffic influencing decisions and operations by providing analytics related to network and service data in advance.
  • the use of the NWDAF in supporting edge computing is beneficial because it considers at least the following aspects:
  • Service/application characteristics such as QoS/QoE
  • 5GS could be evolved to support mobility management considering both UE and resource mobility/availability, traffic steering (e.g., UPF selection considering DNAI characteristics), UP path changes and optimization (e.g., SMF path allocation decisions and SSC mode selection), and the like. Consequently, it can improve the quality of hosted edge computing services.
  • traffic steering e.g., UPF selection considering DNAI characteristics
  • UP path changes and optimization e.g., SMF path allocation decisions and SSC mode selection
  • a network analytics node implements a procedure for determining routing recommendations for user traffic to one of an Edge Cloud Data Network (ECDN) and a Central DN.
  • a method implemented at the network analytics node comprises receiving a routing recommendation request from a policy control node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE.
  • the method further comprises determining a routing recommendation based on the optimization objective responsive to receiving the routing recommendation request, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed.
  • DNAI Data Network Access Identifier
  • the method further comprises sending the routing recommendation to the policy control node.
  • a policy control node implements a method for determining routing recommendations for user traffic to one of an Edge Cloud Data Network (ECDN) and a Central DN.
  • the method comprises sending a routing recommendation request to a network analytics node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE.
  • the method then calls for receiving, in response, a routing recommendation for the UE, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed.
  • the method calls for PCF 60 updating a routing policy for the UE based on the routing recommendation.
  • DNAI Data Network Access Identifier
  • the present disclosure provides a network analytics node for determining routing recommendations for user traffic to one of an Edge Cloud Data Network (ECDN) and a Central DN.
  • the network analytics node comprises interface circuitry configured for communication with one or more network nodes in a communication network and processing circuitry operatively connected to the interface circuit.
  • the processing circuitry is configured to receive a routing recommendation request from a policy control node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE, determine a routing recommendation based on the optimization objective responsive to receiving the routing recommendation request, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed, and send the routing recommendation to the policy control node.
  • UE User Equipment
  • DNAI Data Network Access Identifier
  • the present disclosure provides a network analytics node for determining routing recommendations for user traffic to one of an Edge Cloud Data Network (ECDN) and a Central DN.
  • the network analytics node is configured to receive a routing recommendation request from a policy control node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE, determine a routing recommendation based on the optimization objective responsive to receiving the routing recommendation request, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed, and send the routing recommendation to the policy control node.
  • UE User Equipment
  • DNAI Data Network Access Identifier
  • the present disclosure provides a non-transitory computer-readable storage medium.
  • the medium has a computer program comprising executable instructions stored thereon that, when executed by a processing circuit of a network analytics node in a communications network, causes the network analytics node to receive a routing recommendation request from a policy control node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE, determine a routing recommendation based on the optimization objective responsive to receiving the routing recommendation request, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed, and send the routing recommendation to the policy control node.
  • DNAI Data Network Access Identifier
  • the present disclosure provides a policy control node for determining routing recommendations for user traffic to one of an Edge Cloud Data Network (ECDN) and a Central DN.
  • the policy control node comprises interface circuitry configured for communication with one or more nodes in a communications network, and processing circuitry operatively connected to the interface circuitry.
  • the processing circuitry is configured to send a routing recommendation request to a network analytics node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE, receive, in response to the routing recommendation request, a routing recommendation for the UE, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed, and update a routing policy for the UE based on the routing recommendation.
  • UE User Equipment
  • DNAI Data Network Access Identifier
  • the present disclosure provides a policy control node for routing recommendations for user traffic to one of an Edge Cloud Data Network (ECDN) and a Central DN.
  • the policy control node is configured to send a routing recommendation request to a network analytics node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE, receive, in response to the routing recommendation request, a routing recommendation for the UE, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed, and update a routing policy for the UE based on the routing recommendation.
  • DNAI Data Network Access Identifier
  • the present disclosure provides a non-transitory computer-readable storage medium having a computer program comprising executable instructions stored thereon.
  • the executable instructions of the computer program When executed by processing circuitry in a policy control node in a communication network, the executable instructions of the computer program causes the policy control node to send a routing recommendation request to a network analytics node, wherein the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE, receive, in response to the routing recommendation request, a routing recommendation for the UE, wherein the routing recommendation comprises a Data Network Access Identifier (DNAI) identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed, and update a routing policy for the UE based on the routing recommendation.
  • DNAI Data Network Access Identifier
  • Figure 1 illustrates an exemplary wireless communication network configured according to one embodiment of the present disclosure.
  • Figures 2A-2B are signaling diagrams illustrating a subscription-based method for determining routing recommendations according to one embodiment of the present disclosure.
  • Figure 3 is a signaling diagram illustrating a request-response based method for determining routing recommendations according to one embodiment of the present disclosure.
  • Figure 4 is a flow diagram illustrating a method, implemented at a network analytics node, for determining routing recommendations according to one embodiment of the present disclosure.
  • Figure 5 is a flow diagram illustrating a method, implemented at a policy control node, for determining routing recommendations according to one embodiment of the present disclosure.
  • FIG. 6 illustrates an exemplary Network Data Analytics Function (NWDAF) node configured according to one embodiment of the present disclosure.
  • NWDAAF Network Data Analytics Function
  • FIG. 7 illustrates an exemplary Policy Control Function (PCF) node configured according to one embodiment of the present disclosure.
  • PCF Policy Control Function
  • Figure 8 illustrates the main functional components of an exemplary Network Data Analytics Function (NWDAF) node configured according to one embodiment of the present disclosure.
  • NWDAAF Network Data Analytics Function
  • FIG. 9 illustrates the main functional components of an exemplary Policy Control Function (PCF) node configured according to one embodiment of the present disclosure.
  • PCF Policy Control Function
  • FIG 1 illustrates a wireless communication network 10 according to one exemplary embodiment.
  • the wireless communication network 10 comprises a radio access network (RAN)
  • RAN radio access network
  • the RAN 20 comprises one or more base stations 25 providing radio access to UEs 40 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 IMS or the Internet.
  • 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) 50, a Session Management Function (SMF) 55, a Policy Control Function (PCF) 60, a Unified Data Management (UDM) function 65, a Authentication Server Function (AUSF) 70, a Unified Data Repository (UDR) 75, a Network Exposure Function (NEF) 80, a Network Repository Function (NRF) 85, and a Network Slice Selection Function (NSSF) 90.
  • the core network 30 additionally includes a NWDAF 100 for generating and distributing analytics reports.
  • 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 network 10 may further include one or more Application Functions (AFs) 95 providing services to the network and or subscribers.
  • AFs 95 may be located in the core network 30 or be external to the core network 30.
  • the various NFs e.g., SMF 55, AMF 50, etc.
  • the wireless communication network 10 uses a services model in which the NFs query the NRF 85 or other NF discovery node to discover and communicate with each other.
  • UEs are allocated/routed to the Edge Cloud (EC) in a non-intelligent manner. That is, the UEs are allocated to the EC based either on a static configuration, or in response to routing requests from an AF. Additionally, there is no guarantee that the currently proposed solutions fulfill the desired benefits of the EC.
  • the EC was initially conceived to fulfill certain objectives, such as to ensure low latency to latency critical applications, provide high throughput content from local servers, reduce the load on the core network (CN), and the like.
  • the currently proposed solutions simply assume that these objectives are fulfilled when the UE is allocated to an Edge Cloud. There is no close-loop feedback to ensure that the objectives are being fulfilled, or to trigger corrective actions if they are not being fulfilled.
  • the currently proposed solutions do not provide a mechanism to intelligently allocate and/or reallocate UEs among ECs and Central DNs when the QoS/QoE requirements of the UE can be fulfilled by the Central DN. That is, the currently proposed solutions do not allocate and/or reallocate UEs considering certain optimization objectives, such as fulfilling user QoE, reducing latency and/or the load on the CN, and the like.
  • Embodiments of the present disclosure provide a system and method that enables intelligent EC routing decisions in 5GC networks.
  • the embodiments are based on the analytics capabilities of the NWDAF and configure the NWDAF to:
  • EC routing recommendations i.e. , DNAI recommendations
  • the optimization objectives can be, but are not limited to, fulfilling a user’s QoE/QoS requirements, minimizing communications latency, minimizing the load on the CN, balancing the traffic load among Edge Clouds and Central DNs, and the like.
  • Network Functions such as the PCF, for example, can be configured to subscribe to the EC routing recommendations provided by NWDAF.
  • the NWDAF is configured to obtain:
  • the location of the UE e.g., from the AMF
  • Network status and KPIs such as information defining the state of network congestion, link capacities, and the like (e.g., from the UPF).
  • the NWDAF is configured to execute causal inference analytics processes to determine a best Edge Cloud or Central DN that should serve a certain user and/or an application providing service to the user.
  • causal inference analytics processes to determine a best Edge Cloud or Central DN that should serve a certain user and/or an application providing service to the user.
  • the NWDAF may optionally identify available DNs at a certain location based on information received from the OSS. If one of the available DNs are deemed suitable, and if an application of interest is not already deployed in that DN, the NWDAF may request the OSS to deploy that application in that DN.
  • the NWDAF may initiate an “experiment procedure” to determine how a given EC routing policy would affect one or more UEs (i.e., how a given EC would perform for a given UE in a certain location and with a certain application). To perform the experiment procedures, the NWDAF first selects a set of one or more “test” UEs. The NWDAF then sends a request message to the PCF to route the set of “test” UEs to the DNAI identifying the given Edge Cloud.
  • the NWDAF then measures the effect of the EC routing policy on the optimization objective(s) of the test UEs. If the NWDAF determines that the given EC routing policy is more appropriate for UEs in a given location executing a given application subject to the optimization objectives, the NWDAF will:
  • the EC routing recommendation identifies the UE(s), the application, and the DNAI to which the recommendation applies.
  • the NWDAF is configured to provide such EC routing recommendations responsive to receiving an explicit request for the EC routing recommendations.
  • Figures 2A-2B are flow diagrams illustrating a method 110 of determining routing recommendations for user traffic in an EC DN or a Central DN based on a causal inference analysis according to one embodiment of the present disclosure.
  • Figures 2A-2B illustrate this embodiment as a subscription-based model in which PCF 60 subscribes to receive the EC routing recommendations from the NWDAF 100.
  • method 110 begins with the PCF 60 subscribing to the NWDAF 100 for EC routing recommendations (line 112).
  • the subscription request includes a UE-ID (i.e., a unique identifier identifying the UE), an Application ID (i.e., a unique identifier identifying a given application to provide service to the UE), and an optimization objective for the UE that indicates a particular optimization that should be satisfied for the UE.
  • optimizations may include, but are not limited to, fulfilling a user’s QoE/QoS requirements, minimizing communications latency, minimizing a load on the CN, balancing the traffic load among ECs and Central DNs, and the like.
  • the NWDAF 100 Responsive to receiving the subscription request, the NWDAF 100 sends a request message to the AMF 50 requesting the UE’s location following standard data collection mechanisms (line 114). The AMF 50 then responds to the NWDAF 100 with the UE’s current location (line 116).
  • the NWDAF 100 then sends another request message to the OSS 105 requesting the locations of the applications identified by the Application-ID (line 118).
  • the OSS 105 sends a list of DNAIs identifying the DNs where the application is currently deployed (line 120).
  • the NWDAF 100 then sends a request message to the UPF 35 (or some other network entity) requesting the current status of the network(s) identified in the list of DNAIs using standard data collection mechanisms (line 122).
  • the UPF 35 (or other requested entity) then responds with the network status information and the KPIs for the identified network(s) (line 124).
  • the NWDAF 100 determines, based on the collected data and on the optimization objective(s), which of the DNAIs on the list of DNAIs is the best for the EC routing recommendation (box 126).
  • the NWDAF 100 then sends an acknowledgment response to PCF 60 acknowledging the subscription request (line 128).
  • the response includes the initial DNAI recommendation.
  • the NWDAF 100 then begins diagnostics for the optimization objective(s) based on the collected data and using standard data collection mechanisms (box 130). Upon the NWDAF 100 detecting that an optimization objective is not satisfied (box 132), the NWDAF 100 initiates an “experiment procedure” in which the NWDAF 100 determines an “experimental” or “test” EC routing recommendation to send to the PCF 60. This experimental EC routing recommendation will be evaluated to determine whether it will satisfy the optimization objective(s).
  • the NWDAF 100 is configured to obtain a list of DNAIs.
  • the NWDAF 100 may send a request message to the OSS 105 requesting that it provide the available DNs in the UE location (line 134).
  • the request message may also request that OSS 105 provide a maximum distance that is allowed to exist between the UE and the DN.
  • the OSS 105 sends a response message to the NWDAF 100 including a list of available DNs (line 136).
  • the response message also includes DNAI and location for each DN on the list.
  • the NWDAF 100 sends a request message to the OSS 105 to deploy a given application in a specified DNAI, provided that the given application is not already deployed there (line 138).
  • the OSS 105 is configured to respond with an acknowledgement message indicating whether the deployment request was accepted or not accepted (line 140).
  • the NWDAF 100 then decides to trigger a causal inference analytics procedure (line 142). To accomplish this function, the NWDAF 100 sends a message to the PCF 60 including an “experimental” EC routing policy to apply to temporarily route a group of UEs to an Edge Cloud.
  • the NWDAF 100 may provide a list of UE-IDs identifying which particular UEs that have been selected for the experimental routing procedure, an Application-ID identifying the particular application the experiment pertains to, and a DNAI identifying the particular EC the UEs are to be routed towards for the experiment.
  • the present disclosure is not limited to triggering the causal inference analytics procedure using only a single Application-ID.
  • the NWDAF 100 may send a list of Application-IDs identifying each application. Additionally, according to the present embodiments, this procedure may also be accomplished using the DNAI of a Central DN. Thus, the present embodiments are not limited only to providing routing recommendations for ECs.
  • the PCF 60 then responds to the NWDAF 100 with an acknowledgement message including the list of UEs that are accepted for the experimental routing procedure (line 144), and triggers an EC routing policies update (box 146).
  • the NWDAF 100 then begins measuring the effects of the EC routing policy on the optimization objective(s) of the UEs that were routed in accordance with the experimental EC routing recommendation (box 148).
  • the NWDAF 100 determines, based on the measured effects on the optimization objectives, that the experimental EC routing policy is more appropriate for UEs that are in a given location and executing a given application (box 150).
  • This “experimental” EC routing recommendation is therefore the new routing recommendation.
  • the NWDAF 100 sends a message to the PCF 60 to cancel the experimental routing (line 152).
  • the message may include the list of UE-IDs and Application-ID(s).
  • PCF 60 Upon receipt of the message, PCF 60 returns the “temporarily routed” UEs back to their original routing policies (box 154), and acknowledges cancellation of the experimental routing to the NWDAF 100 (line 156). The NWDAF 100 then notifies the PCF 60, as well as any other subscribed network functions, of the new EC routing recommendation (line 158). In this aspect, the notification includes the UE-ID(s) and Application-ID(s) that the new recommendation pertains to as well as the recommended DNAI. The PCF 60 then accepts or rejects the recommendation (box 160) and responds to the NWDAF 100 indicating whether it accepted or rejected the recommendation (box 162).
  • the present disclosure is not limited to utilizing a subscription-based model for providing EC routing recommendations. Rather, the NWDAF 100 is configured to provide such EC routing recommendations responsive to receiving an explicit request for the EC routing recommendations.
  • This request/response model may be implemented in addition to or in lieu of the previously described subscription-based model.
  • Figure 3 is a flow diagram illustrating a method 170 of determining routing recommendations for user traffic in an EC DN or a Central DN based on a causal inference analysis, and using a request/response type of model according to one embodiment of the present disclosure.
  • the NWDAF 100 activates the EC routing policies recommendation analytics and collects the corresponding data for the corresponding UEs, applications, and DNs (box 172). This can be accomplished internally by the NWDAF 100 using any method needed or desired; however, in one embodiment, this process is triggered by an OAM command.
  • SMF 55 sends a request message to the PCF 60 requesting the PCC rules for a given UE-ID (line 174).
  • the PCF 60 then sends a message to the NWDAF 100 requesting the EC routing recommendations (line 176).
  • the request comprises the UE-ID, the Application-ID(s), and the optimization objective for the UE.
  • the NWDAF 100 then sends a response message to the PCF 60 including the recommended DNAI (line 178), which in turn, sends a response message to the SMF 55 comprising the Application-ID and the PCC rules and including the DNAI (line 180).
  • Figure 4 is a flow diagram illustrating an exemplary method 190 for determining routing recommendations for user traffic to one of an EC DN and a Central DN.
  • method 190 is implemented at a network analytics node, such as NWDAF 100 for example.
  • NWDAF 100 for example.
  • NWDAF 100 for example.
  • NWDAF 100 for example.
  • network analytics node receives a routing recommendation request from a policy control node (box 192).
  • the routing recommendation request comprises an optimization objective for one or both of a User Equipment (UE) and an application to provide service to the UE.
  • the network analytics node determines a routing recommendation based on the optimization objective (box 194).
  • the routing recommendation may comprise a DNAI identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed. So determined, the network analytics node sends the routing recommendation to the policy control node (box 196).
  • the routing recommendation request in some embodiments further comprises an application ID that identifies the application to provide service to the UE.
  • method 190 further comprises determining a list of DNAIs based on the application identifier.
  • the network analytics node sends an application location request to an operation support node, and receives, in return, the list of DNAIs from the operation support node.
  • the application location request sent to the operation support node includes the application ID received in the routing recommendation request.
  • the routing recommendation request further comprises a UE ID that identifies the UE.
  • Some embodiments of method 190 further comprise determining a location of the UE based on the UE identifier, and determining a network status for the one of the EC DN and Central DN identified by the DNAI.
  • the routing recommendation is also determined based on the UE location, the network status, and the list of DNAIs.
  • the routing recommendation sent to the policy control node comprises a DNAI selected from the list of DNAIs.
  • the routing recommendation is an initial routing recommendation.
  • the method 190 further comprises the network analytics node determining one or more updated routing recommendations based on diagnostic information associated with the optimization objective.
  • method 190 further comprises the network analytics node determining that the optimization objective is not satisfied based on the diagnostic information.
  • method 190 further comprises the network analytics node sending a message to the operations support node requesting a current location for the UE, a list of available DNs, and a maximum distance from the UE to each of the available DNs.
  • the network analytics node receives the list of available DNs from the operations support node.
  • each DN in the list includes a DNAI and a location.
  • Some embodiments of method 190 further comprise the network analytics node sending a request to the operations support node to deploy the application to a selected DNAI.
  • method 190 further comprise the network analytics node performing a causal inference analysis at the network analytics node.
  • the causal inference analysis measures an effect of an updated routing policy on the optimization objective of each of one or more selected UEs.
  • Some embodiments of method 190 further comprise the network analytics node performing the causal inference analysis by sending a message to the policy control node that causes the policy control node to initiate a routing policy update procedure.
  • the message comprises a list of candidate UE IDs on which to test the updated routing policy, a candidate application ID that identifies an application to be tested according to the updated routing policy, and a candidate DNAI identifying the network to which the updated routing policy should apply.
  • the network analytics node receives an acknowledgement message from the policy control node in response. In these embodiments, the acknowledgement message comprises the list of one or more selected UEs.
  • Some embodiments of method 190 further comprise the network analytics node measuring the effect of the updated routing policy on the optimization objective of each of one or more selected UEs.
  • Some embodiments of method 190 further comprise the network analytics node determining a new routing recommendation for a selected UE based on the measured effects of the routing policy on the selected UE, indicating to the policy control node that the network analytics node has ended the causal inference analysis, and sending the new routing recommendation to the policy control node.
  • the routing recommendation request from the policy control node is a subscription request.
  • the routing recommendation request from the policy control node is an explicit request for the routing recommendation.
  • the routing recommendation is an EC routing recommendation.
  • Figure 5 is a flow diagram illustrating an exemplary method 200 for determining routing recommendations for user traffic to one of an EC DN and a Central DN.
  • method 200 is implemented at a policy control node, such as PCF 60, for example.
  • method 200 comprises the PCF 60 sending a routing recommendation request to a network analytics node (box 202).
  • the routing recommendation request comprises an optimization objective for one or both of a UE and an application to provide service to the UE.
  • Method 200 also comprises the PCF 60 receiving, in response to the routing recommendation request, a routing recommendation for the UE (box 204).
  • the routing recommendation comprises DNAI identifying one of an ECDN and a Central DN to which user traffic for the UE will be routed.
  • Method 200 then comprises PCF 60 updating a routing policy for the UE based on the routing recommendation (box 206).
  • Some embodiments of method 200 further comprise the policy control node 60 initiating a causal inference analytics procedure at the network analytics node in response to receiving a message from the network analytics node.
  • the causal inference analysis measures an effect of a provisional routing policy on the optimization objective of each of one or more selected UEs.
  • the message from the network analytics node causes the policy control node to initiate a routing update policy procedure, and comprises the policy control node 60 a list of candidate UE IDs on which to test the provisional routing policy, a candidate application ID that identifies an application to be tested according to the provisional routing policy, and a candidate DNAI identifying one of a target ECDN and a target Central DN to which the provisional routing policy should apply.
  • Some embodiments of method 200 further comprise the policy control node 60 initiating the causal inference analytics procedure at the network analytics node by sending an acknowledgement message to the network analytics node, wherein the acknowledgement message comprises a list of one or more selected UEs on which the network analytics node should perform the causal inference analytics procedure, and temporarily updating a current routing policy of the one or more selected UEs to the provisional routing policy.
  • Some embodiments of method 200 further comprise the policy control node 60 restoring the current routing policy of the one or more selected UEs responsive to receiving an indication from the network analytics node that the causal inference analysis procedure is complete.
  • the routing recommendation is an initial routing recommendation.
  • method 200 further comprises the policy control node 60 receiving an updated routing recommendation for the one or more selected UEs, and updating the routing policy of the given UE according to the updated routing recommendation.
  • the updated routing recommendation comprises the candidate DNAI, the candidate application ID, and the UE ID of a given UE to which the updated routing recommendation applies.
  • an apparatus can perform any of the methods herein described by implementing any functional means, modules, units, or circuitry.
  • the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures.
  • the circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory.
  • the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like.
  • DSPs Digital Signal Processors
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.
  • Figure 6 illustrates a network node configured to function as a network analytics node, such as NWDAF 100, according to one embodiment of the present disclosure.
  • the NWDAF 100 comprises interface circuitry 210, processing circuitry 212, and memory circuitry 214.
  • the communication circuitry 210 comprises network interface circuitry for communicating with other network nodes in the wireless communication network over a communication network.
  • network nodes include, but are not limited to, a policy control node (e.g., PCF 60), an operations support node (e.g., OSS 105), an access and mobility management function (e.g., AMF 50), and a user plane function (e.g., UPF 35).
  • PCF 60 policy control node
  • OSS 105 operations support node
  • AMF 50 access and mobility management function
  • UPF 35 user plane function
  • Processing circuitry 212 controls the overall operation of the NWDAF 100 and is configured to perform one or more of the methods 110 and 190 shown in Figures 2A-2B and 4, respectively. Such processing includes coding and modulation of transmitted data signals, and the demodulation and decoding of received data signals.
  • the processing circuitry 212 may comprise one or more microprocessors, hardware, firmware, or a combination thereof.
  • Memory circuitry 214 comprises both volatile and non-volatile memory for storing computer program code and data needed by the processing circuitry 212 for operation.
  • Memory circuitry 214 may comprise any tangible, non-transitory computer-readable storage medium for storing data including electronic, magnetic, optical, electromagnetic, or semiconductor data storage.
  • Memory circuitry 214 stores a computer program 216 comprising executable instructions that configure the processing circuitry 212 to implement the methods 110 and 190 shown in Figures 2A-2B and 4, respectively.
  • a computer program 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).
  • computer program 216 for configuring the processing circuitry 212 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 216 may also be embodied in a carrier such as an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • FIG. 7 illustrates a network node configured to function as a policy control node, such as PCF 60, according to one embodiment of the present disclosure.
  • the PCF 60 comprises interface circuitry 220, processing circuitry 222, and memory circuitry 224.
  • a computer program 226 that configures PCF 60 to operate according to the present embodiments may be stored in memory circuitry 224.
  • the communication circuitry 220 comprises network interface circuitry for communicating with other network nodes in the wireless communication network over a communication network.
  • network nodes include, but are not limited to, a network analytics node (e.g., NWDAF 100), an operations support node (e.g., OSS 105), an access and mobility management function (e.g., AMF 50), and a user plane function (e.g., UPF 35).
  • NWDAF 100 network analytics node
  • OSS 105 operations support node
  • AMF 50 access and mobility management function
  • UPF 35 user plane function
  • Processing circuitry 222 controls the overall operation of PCF 60 and is configured to perform one or more of the methods 170 and 200 shown in Figures 3 and 5, respectively. Such processing may include, for example, the coding and modulation of transmitted data signals, and the demodulation and decoding of received data signals.
  • the processing circuitry 222 may comprise one or more microprocessors, hardware, firmware, or a combination thereof.
  • Memory circuitry 224 comprises both volatile and non-volatile memory for storing computer program code and data needed by the processing circuitry 222 for operation.
  • Memory circuitry 224 may comprise any tangible, non-transitory computer-readable storage medium for storing data including electronic, magnetic, optical, electromagnetic, or semiconductor data storage.
  • Memory circuitry 224 stores computer program 226 comprising executable instructions that configure the processing circuitry 222 to implement the methods 170 and 200 shown in Figures 3 and 5, respectively.
  • a computer program 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).
  • computer program 226 for configuring the processing circuitry 222 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 226 may also be embodied in a carrier such as an electronic signal, optical signal, radio signal, or computer readable storage medium.
  • FIG 8 illustrates an exemplary network analytics node, such as NWDAF 100, configured to perform methods 110 and 190 shown in Figures 2A-2B and 4, respectively.
  • NWDAF 100 comprises a communications unit/module 230, a routing recommendation unit/module 232, and a causal inference analytics unit/module 234.
  • the various units/modules 230-234 can be implemented by hardware and/or by software code that is executed by a processor or processing circuitry 212.
  • the communications unit/module 230 is configured to receive routing recommendation requests from other network entities, such as PCF 60.
  • the requests may be explicit requests for EC routing recommendations, or may be subscription requests to subscribe to receiving EC routing recommendations from NWDAF 100. Additionally, the communications unit/module 230 is configured to send the EC routing recommendations to the PCF 60.
  • the routing recommendation unit/module 232 performs its functions responsive to receiving the routing recommendation request from PCF 60, and is configured to determine the EC routing recommendations based on an optimization objective received with the request.
  • the EC routing recommendations comprise a DNAI that identifies one of an EC DN and a Central DN to which user traffic for the UE will be routed.
  • the causal inference analytics unit/module 234 is configured implement an analytics process in which NWDAF 100 initiates the “experiment procedure” describe previously to determine how a given EC routing policy would affect one or more UEs.
  • the causal inference analytics unit/module 234 selects a set of one or more “test” UEs and triggers PCF 60 into routing traffic from the set of “test” UEs to a selected DNAI.
  • the causal inference analytics unit/module 234 measures the effect of the EC routing policy on the optimization objective(s) of the test UEs, and based on those measurements, sends the “test” routing procedure to the PCF 60 as a new EC routing recommendation the NFs that are subscribed to receive such information.
  • FIG 9 illustrates an exemplary policy control node, such as PCF 60, configured to perform methods 170 and 200 shown in Figures 3 and 5, respectively.
  • the PCF 60 comprises a communications unit/module 240 and a routing policy unit/module 242.
  • the various units/modules 240 and 242 can be implemented by hardware and/or by software code that is executed by a processor or processing circuitry 222.
  • the communications unit/module 240 is configured to receive routing recommendations from NWDAF 100, as well as other data and information from NWDAF 100 and other network entities. In addition, the communications unit/module 240 is configured to send requests to NWDAF 100 to provide EC routing recommendations. As previously described, the may be explicit requests for EC routing recommendations, or may be subscription requests to subscribe to receiving EC routing recommendations from NWDAF 100.
  • the routing policy unit/module 242 is configured to update its policy tables according to the EC routing recommendations received from NWDAF 100.
  • a computer program comprises instructions which, 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

Nœud d'analyse de réseau (100) mettant en œuvre une procédure pour déterminer des recommandations de routage pour un trafic d'utilisateur vers l'un d'un réseau de données en nuage périphérique (ECDN) et d'un réseau de données (DN) central. Selon un aspect, le nœud d'analyse de réseau reçoit (112, 192) une demande de recommandation de routage provenant d'un nœud de commande de politique (60). La demande de recommandation de routage comprend un objectif d'optimisation pour l'un ou les deux d'un équipement utilisateur (UE) (40) et d'une application pour fournir un service à l'UE. Le nœud d'analyse de réseau détermine également (126, 194) une recommandation de routage sur la base de l'objectif d'optimisation en réponse à la réception de la demande de recommandation de routage. La recommandation de routage comprend un identifiant d'accès au réseau de données (DNAI) qui identifie l'un d'un ECDN et d'un DN central auxquels le trafic d'utilisateur pour l'UE sera acheminé. Une fois déterminé, le nœud d'analyse de réseau envoie (128, 196) la recommandation de routage au nœud de commande de politique.
PCT/IB2020/057083 2020-06-30 2020-07-27 Recommandation de politiques de routage d'informatique à la frontière (ec) basée sur des analyses d'inférence causale WO2022003407A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP20382585.6 2020-06-30
EP20382585 2020-06-30

Publications (1)

Publication Number Publication Date
WO2022003407A1 true WO2022003407A1 (fr) 2022-01-06

Family

ID=71607866

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/057083 WO2022003407A1 (fr) 2020-06-30 2020-07-27 Recommandation de politiques de routage d'informatique à la frontière (ec) basée sur des analyses d'inférence causale

Country Status (1)

Country Link
WO (1) WO2022003407A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220124015A1 (en) * 2020-10-01 2022-04-21 Nokia Technologies Oy Historical data support enhancement for network entities

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020018012A1 (fr) * 2018-07-17 2020-01-23 Telefonaktiebolaget Lm Ericsson (Publ) Interaction entre une plate-forme d'automatisation de réseau ouvert (onap) et un cœur de cinquième génération (5gc) permettant une analyse

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020018012A1 (fr) * 2018-07-17 2020-01-23 Telefonaktiebolaget Lm Ericsson (Publ) Interaction entre une plate-forme d'automatisation de réseau ouvert (onap) et un cœur de cinquième génération (5gc) permettant une analyse

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"5G; System Architecture for the 5G System", 3GPP TS 23.501 VERSION 15.2.0 RELEASE 15, June 2018 (2018-06-01)
3GPP TR 23.700-91 V0.3.0, January 2020 (2020-01-01)
SAMSUNG ET AL: "KI #16, New Sol: Network Assisted DNAI selection", vol. SA WG2, no. 20200601 - 20200612, 8 June 2020 (2020-06-08), XP051894603, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/TSGS2_139e_Electronic/Docs/S2-2004564.zip S2-2004564_eNA_pCR_23.700_91_DNAI selection_r03.docx> [retrieved on 20200608] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220124015A1 (en) * 2020-10-01 2022-04-21 Nokia Technologies Oy Historical data support enhancement for network entities

Similar Documents

Publication Publication Date Title
JP7047113B2 (ja) アプリケーションのサービスレベル合意を保証するための方法、デバイスおよびシステム
US11330069B2 (en) Service subscription method and system for reporting service change in communication system
CN110049070B (zh) 事件通知方法及相关设备
JP7269377B2 (ja) 移動通信ネットワークのネットワークスライスインスタンスに関するネットワーク解析及び／又は予測情報を提供するためのネットワーク解析コンポーネント及び方法。
US20220377655A1 (en) Network Slicing Scalability Attributes
US20220417101A1 (en) Communication method, apparatus, and system
KR102233894B1 (ko) 네트워크 기능 장치 및 이를 이용한 요청 처리 방법
EP4070529A1 (fr) Régulation de charge de fonction de plan utilisateur
WO2022003407A1 (fr) Recommandation de politiques de routage d&#39;informatique à la frontière (ec) basée sur des analyses d&#39;inférence causale
US20230336969A1 (en) User equipment data collection
CN115915137A (zh) 一种网络功能服务授权方法及装置
US11910306B2 (en) Methods, systems, and computer readable media for providing updated network slice information to a network slice selection function (NSSF)
US11923994B2 (en) Method and packet core system for common charging of network connectivity and cloud resource utilization
KR102333106B1 (ko) Pdu 세션 수립 방법 및 상기 방법을 수행하는 사용자 단말
JP2023544182A (ja) 通信ネットワーク構成及びネットワークコンポーネントの選択方法
US20180343582A1 (en) Congestion control method and apparatus
JP2024517038A (ja) 通信ネットワークコンポーネントの構成と通信ネットワーク分析を行うための機械学習モデルの提供方法
CN117939454A (zh) 信息传输方法、设备及存储介质

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20749966

Country of ref document: EP

Kind code of ref document: A1