Edge node, core network node, communication method, and program

Abstract

The purpose of the present invention is to provide an edge node that can minimize difference in quality of edge computing service to be provided to a plurality of UEs. An edge node according to the present disclosure is deployed in an edge computing service environment, and comprises: a generation unit that generates cost values corresponding to a plurality of paths for transferring user plane data between a core network and the edge computing service environment; and a communication unit that transmits the cost values to a core network node deployed in the core network.

Description

Edge node, core network node, communication method, and program

[0001] The present disclosure relates to an edge node, a core network node, a communication method, and a program.

[0002] In recent years, the application of a network technology known as edge computing has been considered in contrast to cloud computing, which aggregates all information in the cloud and executes data processing on high-performance servers on the cloud. In edge computing, data processing, data analysis, and other processes are performed on servers located in the vicinity of devices at the network edge, such as IoT (Internet of Things) terminals. The server that has executed the data processing, etc., then transmits the processed or analyzed data to the cloud or the device. This can reduce communication delays and network loads.

[0003] Non-Patent Document 1 exemplifies services provided in edge computing. For example, edge computing assumes a case where multiple UEs need to use the same edge computing environment. For example, it is assumed that a specific edge computing environment handles multiple UEs in order to provide services of the same quality to multiple moving UEs.

[0004] 3GPP TR 23.700-48 V2.0.0 (2022-11)

[0005] There are multiple paths for transmitting data between a core network that provides mobile network services and an edge computing environment that provides edge computing services. However, for example, when multiple UEs transmit and receive data to and from the edge computing environment via different paths, the transmission time varies depending on the distance or bandwidth of each path. As a result, there is a problem that an operator providing an edge computing service may not be able to provide the same quality of service to multiple UEs.

[0006] In view of the above-mentioned problems, the object of the present disclosure is to provide an edge node, a core network node, a communication method, and a program that can reduce the difference in quality of edge computing services provided to multiple UEs.

[0007] An edge node according to a first aspect of the present disclosure is arranged in an edge computing environment and comprises: a generation unit that generates cost values ​​corresponding to each of a plurality of paths for transferring user plane data between a core network and the edge computing environment; and a communication unit that transmits the cost values ​​to a first core network node arranged in the core network.

[0008] A core network node according to a second aspect of the present disclosure is arranged in a core network and comprises: a first receiver that receives a request message from a session management device arranged in the core network to request notification of cost values ​​corresponding to each of a plurality of paths for forwarding user plane data between the core network and an edge computing environment; a second receiver that receives the cost values ​​from an edge node arranged in the edge computing environment; and a transmitter that, upon receiving the cost values, transmits the cost values ​​to the session management device.

[0009] A communication system according to a third aspect of the present disclosure comprises an edge node disposed in an edge computing environment and a core network node disposed in a core network, wherein the edge node generates cost values ​​corresponding to each of a plurality of paths for transferring user plane data between the core network and the edge computing environment, transmits the cost values ​​to the core network node, and the core network node receives the cost values ​​and notifies a session management device of the cost values.

[0010] A communication method according to a fourth aspect of the present disclosure is a communication method executed in an edge application device disposed in an edge computing environment, which generates cost values ​​corresponding to each of a plurality of paths for transferring user plane data between a core network and the edge computing environment, and transmits the cost values ​​to a first core network node disposed in the core network.

[0011] A program according to a fifth aspect of the present disclosure is a program to be executed by a computer device that is an edge node disposed in an edge computing environment, and causes the computer to generate cost values ​​corresponding to each of a plurality of paths for transferring user plane data between a core network and the edge computing environment, and transmit the cost values ​​to a first core network node disposed in the core network.

[0012] The present disclosure provides an edge node, a core network node, a communication method, and a program that can select a more suitable communication path. For example, the present disclosure provides an edge node, a core network node, a communication method, and a program that can reduce the difference in quality of edge computing services provided to multiple UEs. This prevents degradation of the quality of edge computing services due to differences in communication paths.

[0013] FIG. 1 is a configuration diagram of an edge node according to the present disclosure. FIG. 2 is a diagram illustrating a flow of communication processing executed in an edge node according to the present disclosure. FIG. 3 is a diagram illustrating a flow of communication processing executed in a core network node according to the present disclosure. FIG. 4 is a diagram illustrating a configuration diagram of a communication system according to the present disclosure. FIG. 5 is a diagram illustrating a configuration diagram of a Local part of DN according to the present disclosure. FIG. 6 is a diagram illustrating a configuration diagram of an EHE according to the present disclosure. FIG. 7 is a diagram illustrating a flow of request processing in an AF according to the present disclosure. FIG. 8 is a diagram illustrating a flow of DNAI preference generation processing according to the present disclosure. FIG. 9 is a diagram illustrating an example of information elements included in an EAS profile according to the present disclosure. FIG. 10 is a diagram illustrating an example of information elements included in EAS Service KPIs according to the present disclosure. FIG. 11 is a diagram illustrating a flow of DNAI preference generation processing according to the present disclosure. FIG. 12 is a diagram illustrating a flow of DNAI preference generation processing according to the present disclosure. FIG. 13 is a diagram illustrating a flow of DNAI preference transfer processing according to the present disclosure. FIG. 14 is a diagram illustrating the configuration diagram of an edge node and a core network node according to the present disclosure.

[0014] (First Embodiment) Hereinafter, an example configuration of an edge node 10 will be described with reference to FIG. 1 . The edge node 10 is disposed in an edge computing environment 300. At least one edge node 10 is disposed in the edge computing environment 300. The edge node 10 provides an edge computing service to communication terminals and the like connected to a core network 200. The edge computing service may be referred to as an edge application service or an application service. The edge computing environment 300 may also be referred to as a data network connected to the core network 200. The core network 200 and the edge computing environment 300 may be managed by different operators or the same operator. Note that, although the edge computing environment is outside the core network in FIG. 1 , an edge computing environment may exist within the core network. Below, a case where the edge computing environment is outside the core network will be described with reference to FIG. 1 as an example.

[0015] The edge node 10 may be a computer device that operates when a processor executes a program stored in a memory. The edge node 10 has a generation unit 11 and a communication unit 12. The generation unit 11 and the communication unit 12 may be software or modules that perform processing when a processor executes a program stored in a memory.

[0016] The generation unit 11 generates cost values ​​for each path (hereinafter also referred to as a communication path) for transferring user plane data between the core network 200 and the edge computing environment 300. The user plane data may be, for example, text data, image data, video data, etc. On the other hand, data used to control a communication terminal may be referred to as control plane data. The user plane data may be referred to as user data, and the control plane data may be referred to as control data.

[0017] There are multiple paths for transmitting user plane data between the core network 200 and the edge computing environment 300. The core network nodes on the core network 200 side that are the endpoints of the paths may be different for each path or may be the same. The core network nodes on the edge computing environment 300 side that are the endpoints of the paths may also be different for each path or may be the same.

[0018] The cost value is used as a reference value or a standard value when selecting a route. For example, a route with a lower cost value may be selected as a route for transmitting user plane data from the core network 200 to the edge computing environment 300. Alternatively, a route with a higher cost value may be selected as a route for transmitting user plane data from the core network 200 to the edge computing environment 300. Note that the cost value may be a priority for selecting a communication route. In this case, for example, a route with a higher priority may be selected preferentially, or a route with a lower priority may be selected preferentially.

[0019] The generator 11 may generate a cost value corresponding to each route according to predetermined information for each route. The generator 11 may generate a cost value for each route based on information about each of the multiple routes. "Generating" may be synonymous with "calculating," "changing," or "updating." The predetermined information may be, for example, static information (information that does not change over time) such as the number of relay devices through which each route passes, the length of the route, and the bandwidth of each route. Alternatively, the generator 11 may dynamically generate a cost value for each route according to dynamic information (information that changes over time). The dynamically changing information may be, for example, the amount of data transmitted over each route, the transmission time of data over each route, and the like. The generator 11 may, for example, determine the cost value of each route so that the cost value of a route desired to be preferentially selected is low. Furthermore, the generator 11 may set the same cost value for multiple routes when considering load balancing using each route.

[0020] The communication unit 12 transmits the cost value to a core network node 20 arranged in the core network 200. Specifically, the communication unit 12 may transmit to the core network node 20 information associating identification information capable of identifying a network connection or a route with the cost value of the route. The core network node 20 may be, for example, a gateway device, or a control device that manages a session between a communication terminal and the edge computing environment 300. The gateway device may be arranged, for example, at the boundary between the core network 200 and another network. In other words, the gateway device may be arranged at the edge of the core network 200.

[0021] The communication unit 12 may transmit the cost value to the core network node 20 via a path for transferring control plane data, rather than via a path for transferring user plane data. In other words, the communication unit 12 may transmit the cost value as control plane data.

[0022] Next, the flow of communication processing executed in the edge node 10 will be described with reference to Fig. 2. First, the generation unit 11 generates cost values ​​of each path for transferring user plane data between the core network 200 and the edge computing environment 300 (S11). Next, the communication unit 12 transmits the cost values ​​to the core network node 20 arranged in the core network 200.

[0023] As described above, the edge node 10 transmits to the core network node 20 the cost values ​​of each of the multiple routes set for transferring user plane data between the core network 200 and the edge computing environment 300. This makes it possible to collect the routes of user plane data transferred from the core network 200 to the edge computing environment 300 into a specific route. Furthermore, by collecting the routes of user plane data into a specific route, it is possible to make the route lengths between the core network 200 and the edge computing environment 300 constant when providing edge computing to multiple communication terminals. As a result, it is possible to reduce differences in the quality of edge computing services provided to multiple communication terminals.

[0024] Furthermore, the edge node 10 may determine a cost value for each communication terminal group to which multiple communication terminals belong. In other words, the route of user plane data transferred from the core network 200 to the edge computing environment 300 may be determined for each communication terminal group. This makes it possible to distribute the routes of user plane data and provide a uniform edge computing service to multiple communication terminals belonging to the same communication terminal group.

[0025] (Embodiment 2) Next, a configuration example of a core network node 30 (hereinafter also referred to as a "gateway device") arranged in a core network 200 will be described using Figure 3. The core network node 30 may be a computer device that operates when a processor executes a program stored in a memory. The core network node 30 has a receiving unit 31, a receiving unit 32, and a transmitting unit 33. The receiving unit 31, the receiving unit 32, and the transmitting unit 33 may be software or modules that perform processing when a processor executes a program stored in a memory.

[0026] The receiving unit 31 (hereinafter also referred to as a first receiving unit) receives a request message requesting notification of cost values ​​of each path for transmitting user plane data from the session management device 40 arranged in the core network 200. The receiving unit 31 is used to communicate with devices or nodes arranged in the core network 200. Each path for transmitting user plane data is a path between the core network 200 and the edge computing environment 300. The core network node 30 may store the request message or flag information indicating a request for notification of cost values ​​in a memory or the like within the core network node 30.

[0027] The session management device 40 may, for example, select one route from among a plurality of routes set between the core network 200 and the edge computing environment 300, and set the route along which the user plane data is to be transferred. Specifically, the session management device 40 may select one route from among the plurality of routes by using the cost value of each route.

[0028] The receiver 32 (hereinafter also referred to as a second receiver) receives cost values ​​from the edge node 10 arranged in the edge computing environment 300. The receiver 32 is used to communicate with devices or nodes arranged in the edge computing environment 300. The receivers 31 and 32 may be included in one physical component as logical components, or may be included in different physical components. The physical component may be a circuit, a module, or the like.

[0029] The transmitter 33 transmits the cost value received via the receiver 32 to the session management device 40. The cost value may be a cost value notified for the first time by the edge node 10 for each path, or may be a cost value updated from a previously notified cost value. The receiver 31 may include the cost value in a response message to the request message and transmit the response message to the session management device 40. Alternatively, the receiver 31 may transmit the cost value to another core network node in the core network 200. In this case, the receiver 31 may notify the session management device 40 that the cost value is stored in another core network node in the core network 200 in which the cost value is stored. The session management device 40 may acquire the cost value from the other core network node in the core network 200.

[0030] Next, the flow of communication processing executed in the core network node 30 will be described using Figure 4. First, the receiver 31 receives a request message requesting notification of cost values ​​of each path for forwarding user plane data from the session management device 40 located in the core network 200 (S21). Next, the receiver 32 receives cost values ​​from the edge node 10 located in the edge computing environment 300 (S22). Next, the transmitter 33 transmits the cost values ​​received via the receiver 32 to the session management device 40 (S23).

[0031] As described above, the core network node 30 has received a request message in advance from the session management device 40. When the core network node 30 receives the cost value from the edge node 10, it includes the cost value in a response message to the request message and transmits the response message to the session management device 40. This enables the core network node 30 to notify the session management device 40, which selects one route from multiple routes between the core network 200 and the edge computing environment 300, of the cost value used for route selection.

[0032] (Embodiment 3) Next, an example of the configuration of a communication system will be described with reference to Fig. 5 . The communication system of Fig. 5 includes a UE 70 and an AN (Access Network) 50. The communication system further includes a UPF (User Plane Function) 60 that mainly processes User Plane (UP) data. The UPF 60 is connected to a local part of a DN 170. The communication system further includes a UDR (User Data Repository) 80 that mainly processes Control Plane (CP) data, an NRF (Network Repository Function) 90, an AMF (Access and Mobility Management Function) 100, a PCF (Policy Control Function) 110, an SMF (Session Management Function) 120, an AF (Application Function) 130, an NEF (Network Exposure Function) 140, a UDM (Unified Data Management) 150, and an EASDF (Edge Application Server Discovery Function) 160.

[0033] Each of the components constituting the communication system in Fig. 5 may be a node, which may correspond to a physical entity (device) or a logical function (function).

[0034] The core network node 20 according to the first embodiment corresponds to, for example, the SMF 120 or the NEF 140. The edge computing environment 300 according to the first embodiment is constructed in the local part of the DN 170, and the edge node 10 is also located in the local part of the DN 170.

[0035] The session management device 40 according to the second embodiment corresponds to the SMF 120. The core network node 30 according to the second embodiment corresponds to the NEF 140.

[0036] The UPF 60, the UDR 80, the NRF 90, the AMF 100, the PCF 110, the SMF 120, the AF 130, the NEF 140, the UDM 150, and the EASDF 160 constitute a 5G (5th Generation) core network. The 5G core network corresponds to the core network 200 in the first embodiment. A service-based architecture is applied to the UDR 80, the NRF 90, the AMF 100, the PCF 110, the SMF 120, the AF 130, the NEF 140, the UDM 150, and the EASDF 160, and they are connected to each other via a service-based interface. For example, the HyperText Transfer Protocol (HTTP) may be used as the service-based interface. For example, Nudr, Nnrf, Namf, Npcf, Nsmf, Naf, Nnef, Nudm, and Neasdf are defined as the service interfaces.

[0037] Reference points are defined between the nodes that make up the communication system. Specifically, N1 is defined between the UE 70 and the AMF 100. N2 is defined between the AN 50 and the AMF 100. N3 is defined between the AN 50 and the UPF 60. N4 is defined between the UPF 60 and the SMF 120. N6 is defined between the UPF 60 and the local part of the DN 180. N9 is defined between the UPFs 60.

[0038] The AN 50 includes at least one of a Next Generation (NG)-RAN (Radio Access Network) and a non-3GPP AN, and is connected to a 5G core network. The AN 50 may be referred to as a 5G access network. The AN 50 that provides a wireless communication link to the UE 70 may be referred to as an (R)AN (Radio AN).

[0039] As an anchor point in the 5G system, the UPF 60 terminates PDU (Protocol Data Unit) sessions and interconnects with external networks. Among the UPFs, a UPF that particularly terminates PDU sessions and connects to a DN is referred to as a PSA (PDU Session Anchor)-UPF. Furthermore, among the PSA-UPFs, a UPF that connects to a Central DN may be referred to as a Central-PSA or C-PSA, and a UPF 60 that connects to a Local part of DN 180 may be referred to as a Local-PSA or L-PSA.

[0040] The NRF 90 provides a function for network functions in the 5G system to discover services. The AMF 100 manages terminal access and terminal mobility. The PCF 110 generates and provides policy rules.

[0041] The SMF 120 manages PDU sessions. Furthermore, the SMF 120 has a DHCP (Dynamic Host Configuration Protocol) function, and assigns an IP address to a connected UE and notifies the UE of the IP address of the EASDF 160 or the FQDN (Fully Qualified Domain Name) of the EASDF 160.

[0042] The AF 130 cooperates with other network functions to provide the Application Influence on Traffic Routing service defined in the 3GPP (registered trademark) network. The AF 130 also provides EAS Deployment Information via the NEF 140, which is stored in the UDR 80. The EAS Deployment Information includes information about the Edge Hosting Environment (EHE), specifically, information about the Edge Application Server (EAS) and DNS. The UDR 80 provides the NEF 140 and the PCF 110 with a service for saving and reading structured data.

[0043] The NEF 140 provides 3GPP network services that can be exposed to the external environment. The UDM 150 holds confidential information such as user identification information, passwords, and authentication information.

[0044] The EASDF 160 provides a service equivalent to a Full Resolver described in IETF RFC8499. When the EASDF 160 receives a DNS Query from the UE, it accesses a DNS server and resolves the queried FQDN. The EASDF 160 is connected to the PSA-UPF via the N6 reference point (user plane) and exchanges DNS messages with the UE 40. The DNS messages may be, for example, DNS Query and DNS Response.

[0045] The local part of DN 170 is an external network connected to the 5G system. An example configuration of the local part of DN 170 will now be described with reference to FIG. 6 . The local part of DN 170 configures an EHE (Edge Hosting Environment) 400 to realize edge computing. The EHE 400 corresponds to the edge computing environment 300 in the first embodiment. The EHE 400 is connected to multiple gateway devices (hereinafter referred to as GWs) via a network 500. FIG. 6 shows a configuration in which the EHE 400 is connected to GWs 601 and 602 via the network 500. The network 500 may be, for example, an IP network, an L3VPN service described in IETF RFC8299, or an L2VPN service described in IETF RFC8466. The GWs 601 and 602 may be relay devices such as routers or switches. The EHE 400 receives data from the UPF 62 via the GW 601, or transmits data to the UPF 62 via the GW 601. Furthermore, the EHE 400 receives data from the UPF 64 via the GW 602 or transmits data to the UPF 64 via the GW 602 .

[0046] The path or link between the UPF 62 and the GW 601 and the path or link between the UPF 64 and the GW 602 are identified by a DNAI (Data Network Access Identifier). The DNAI is identification information that can identify a network connection or a communication path. For example, the path or link between the UPF 62 and the GW 601 may be assigned DNAI_1, and the path or link between the UPF 64 and the GW 602 may be assigned DNAI_2.

[0047] Next, a configuration example of the EHE 400 and the 5G core network will be described using FIG. 7 . In FIG. 7 , the NEF 140 and the PCF 110 are illustrated as nodes included in the 5G core network. The EHE 400 includes an ECS (Edge Configuration Server) 410, an EES (Edge Enabler Server) 420, and an EAS (Edge Application Server) 430. A service-based architecture is applied to the ECS 410, the EES 420, the EAS 430, the PCF 110, and the NEF 140, and they are connected to each other via a service-based interface. For example, the HyperText Transfer Protocol (HTTP) may be used as the service-based interface. The EES 420, the ECS 410, and the EAS 430 may be connected to each other via a common service interface, for example, via an IntraLocalPartOfDn-ControlPlane (a control plane network within the local part of DN). Furthermore, the PCF 440 and the NEF 450 may be connected via a common service interface, for example, via an Intra5GC-ControlPlane (a control plane network within a 5G core network). The EES 420 included in the local part of DN and the NEF 140 included in the 5G core network may be connected via a common service interface, for example, via an Inter-ControlPlane (a network that interconnects the local part of DN and the control plane within a 5G core network).

[0048] The ECS 410 may be included in the AF and deployed in the EHE. The ECS 410 supports registration, update, and re-registration functions of the EES 420. The ECS 410 also directly or indirectly intercommunicates with network functions (NFs) deployed in the core network 200. The NFs may be nodes (core network nodes) that constitute the core network 200. Direct intercommunication may be performed, for example, via the PCF 110, and indirect intercommunication may be performed, for example, via the NEF 140. Direct intercommunication may be permitted, for example, when the operator of the AF and the operator of the 5G core network are the same. Indirect intercommunication may be performed, for example, when the operator of the AF and the operator of the 5G core network are different.

[0049] The EES 420 may be included in the AF and may be deployed in the EHE. The EES 420 supports the registration, update, and re-registration functions of the EAS 430. The EES 420 also directly or indirectly communicates with network functions (NFs) deployed in the core network 200. The NFs may be nodes that constitute the core network 200. Direct communication may be performed via the PCF 110, for example, and indirect communication may be performed via the NEF 140, for example.

[0050] The EAS 430 may be included in the AF and is deployed in the EHE. The EAS 430 executes an Edge Application Service.

[0051] Next, the flow of request processing in the AF will be described with reference to FIG. 8 . First, the EES 420 generates a Traffic Influence Information Element (IE) to be included in the AF Request (S31). The AF Request may be information indicating a request for use of a service provided by a core network node from an AF deployed in the EHE 400. The AF deployed in the EHE 400 may include, for example, an ECS 410, an EES 420, and an EAS 430. Here, the core network node that provides the service may be referred to as an NF (Network Function) service producer, and the AF or the like that uses the service may be referred to as an NF service consumer.

[0052] The Traffic Influence IE is an IE used to request the use of the Nnef_TrafficInfluence service. For example, the Nnef_TrafficInfluence service may request approval for an NF service consumer who wishes to use a service, or request the execution of traffic routing. The Traffic Influence IE includes information for identifying the EES 420 or the EHE 400, such as an External Application Identifier or an AF Service-Identifier. Furthermore, the Traffic Influence IE includes a DNAI Preference.

[0053] DNAI Preference is a value that represents the cost assigned to a DNAI. For example, when there are two routes, DNAI_1 and DNAI_2, the DNAI with the smaller DNAI Preference value is more preferable. If the DNAI Preference value of DNAI_1 is 10 and the DNAI Preference value of DNAI_2 is 5, then DNAI_2 is more preferable. Alternatively, a DNAI with a larger DNAI Preference value may be more preferable. In the following explanation, we will proceed assuming that a DNAI with a smaller DNAI Preference value is more preferable.

[0054] Next, the EES 420 transmits an AF Request using the Nnef_TrafficInfluence service provided by the NEF 140 (S32). In other words, the EES 420 transmits a request message including the AF Request to the NEF 140 using the Nnef_TrafficInfluence service. For example, the EES 420 may transmit the DNAI Preference to the NEF 140 by setting multiple DNAIs in the RouteToLocation attribute information in the Nnef_TrafficInfluence service and setting a DNAI Preference in each DNAI as DNAI_preference attribute information.

[0055] Next, the NEF 140 transmits an AF Request using the Nudr_DM service provided by the UDR 80 (S33). The Nudr_DM service provided by the UDR 80 may be, for example, a Nudr_DM_Create service. The UDR 80 receives the AF Request through the Nudr_DM service.

[0056] Next, the UDR 80 holds the AF Request received through the Nudr_DM service (S34). "Hold" may be rephrased as recording, memorizing, storing, or the like.

[0057] Next, the UDR 80 notifies the PCF 110 that the AF Request has been sent by using the Nudr_DM service (S35). For example, the UDR 80 notifies the PCF 110 that the AF Request has been sent by sending a Nudr_DM_Notify to the PCF 110.

[0058] Next, the PCF 110 notifies the SMF 120 that the AF Request has been submitted, using the Npcf_SMPolicyControl_Update service (S36). The Npcf_SMPolicyControl_Update service may be specifically referred to as an Npcf_SMPolicyControl_UpdateNotify service.

[0059] For example, in step S35, the PCF 110 may receive a Nudr_DM_Notify including an AF Request, or after receiving the Nudr_DM_Notify, may acquire the AF Request from the UDR 80. Also, in step S36, the SMF 120 may receive an Npcf_SMPolicyControl_UpdateNotify including an AF Request, or after receiving the Npcf_SMPolicyControl_UpdateNotify, may acquire the AF Request from the UDR 80.

[0060] After acquiring the AF Request including the DNAI Preference, the SMF 120 establishes a session for the UE to use the service provided by the EES 420. For example, when there are multiple routes from the 5G core network to the EES 420, the SMF 120 selects a route using the DNAI Preference. For example, the SMF 120 may select a UPF connected to a route for which the smallest DNAI Preference is set. Note that in addition to the example of the route between the UPF and GW described above, the route may also be a route between the UPF and EHE (e.g., a route between the UPF and EES, a route between the UPF and AF, etc.), a route between the UPF and a local part of an Edge Data Network (DNN), a route between the UPF and a network, etc.

[0061] As described above, the EES 420 according to the third embodiment transmits an AF Request including a DNAI Preference indicating a cost value for each DNAI to the NEF 140 located in the core network. Furthermore, the DNAI Preference is transferred from the NEF 140 to the SMF 120 within the core network. As a result, when establishing a session between the UE and the EES 420, the SMF 120 determines the route between the UPF and the EHE 400 based on the DNAI Preference. As a result, the EES 420 can guide traffic transferred between the UE and the EHE 400 to a desired route. For example, the EES 420 may guide traffic to one route by lowering the DNAI Preference value of that route and use the other route as a backup route. Alternatively, the EES 420 may guide traffic to a UPF or GW with high processing capacity, or to a route with a shorter distance between the UPF and the GW. As a result, the EES 420 can provide high-quality services that can achieve low latency, high availability, and the like.

[0062] (Fourth Embodiment) Next, the flow of the DNAI preference generation process will be described with reference to Fig. 9. First, the EAS 430 decides to perform registration with the EES 420 (S41). In order for the EAS 430 and the EES 420 to communicate with each other, the EES 420 needs to register the EAS 430. For example, the EAS 430 may decide to perform registration processing with the EES 420 when a virtual machine related to the EAS 430 is started, when a container that executes the EAS 430 is deployed, when a server device that operates as the EAS 430 is started, etc.

[0063] Next, the EAS 430 sends an EAS registration request to the EES 420 to request registration (S42). The EAS registration request includes the EAS profile, and may further include information indicating the validity period of the registration of the EAS 430 in the EES 420.

[0064] The EAS profile is information related to the EAS. Fig. 10 shows examples of information elements included in the EAS profile. For example, the EAS profile includes EASID, EAS Endpoint, EAS Geographical Service Area, EAS Topological Service Area, EAS Service KPIs (Key Performance Indicators), List of EAS DNAI(s), List of N6 Traffic Routing requirements, etc.

[0065] EASID is identification information of the EAS 430. EAS Endpoint is endpoint information used for communication with the EAS 430. The endpoint information may be, for example, a Uniform Resource Identifier (URI), a Fully Qualified Domain Name (FQDN), or an IP address. EAS Geographical Service Area may be geographical information related to the service area provided by the EAS 430. EAS Topological Service Area may be information indicating an area including cells in which UEs provided by the EAS 430 reside. EAS Service KPIs are information indicating the characteristics or features of the services provided by the EAS 430. FIG. 11 shows example information elements included in the EAS Service KPIs. For example, the EAS Service KPIs include Connection Bandwidth, which indicates the bandwidth for each DNAI or the total bandwidth of all DNAIs associated with the EAS 430. List of EAS DNAI(s) is list information indicating at least one DNAI associated with the EAS 430. The DNAI associated with the EAS 430 may be, for example, information that identifies a session or a path between the UPF and the GW for accessing the EAS 430. The List of N6 Traffic Routing requirements may be information that indicates conditions for routing to the local part of DN 170 including EHE 400.

[0066] 9 , next, the EES 420 executes authentication processing for the EAS 430 (S43). Specifically, the EES 420 determines whether or not to permit registration of the EAS 430. For example, the EES 420 may store in advance a list of EASs that are permitted to be registered, and permit registration of the EAS 430 if the EAS 430 is included in the list.

[0067] Next, if the EES 420 permits the registration of the EAS 430, it transmits an EAS registration response indicating that the registration is permitted to the EAS 430 (S44). If the EES 420 permits the registration of the EAS 430, it saves an EAS profile related to the EAS 430.

[0068] Next, the EES 420 generates a DNAI preference (S45). An example of the DNAI preference generation process will now be described. It is assumed that the EES 420 has information called Reference Bandwidth as reference information related to bandwidth. The Reference Bandwidth has a value related to bandwidth, and for example, the value of the Reference Bandwidth is assumed to be 1000 Mbps. Here, it is assumed that the EAS profile related to the EAS 430 includes DNAI_1 and DNAI_2, and indicates that the interface bandwidth of DNAI_1 is 1000 Mbps and the interface bandwidth of DNAI_2 is 100 Mbps.

[0069] In this case, the EES 420 may divide the Reference Bandwidth by each interface bandwidth and use the resulting calculated value as the DNAI Preference. For example, the DNAI Preference for DNAI_1 may be calculated as 1, and the DNAI Preference for DNAI_2 may be calculated as 10. Therefore, the DNAI Preference for DNAI_1 may be set to 1, and the DNAI Preference for DNAI_2 may be set to 10.

[0070] After generating the DNAI preference, the EES 420 executes the processes of steps S31 to S36 in Fig. 8 and notifies the SMF 120 of the DNAI preference. As described above, in this embodiment, the EES 420 generates a cost value based on the reference information of each communication path. For example, the reference information is bandwidth information of the communication path, but is not limited to this and may be any static information (information that does not change over time) related to the communication status of the communication path.

[0071] As described above, the EES 420 according to the fourth embodiment can generate a DNAI preference for each DNAI by using the EAS profile received from the EAS 430. As a result, similar to the third embodiment, the SMF 120 can establish a session to the EES 420 by using the DNAI preference for each DNAI.

[0072] (Fifth Embodiment) Next, a flow of a process for generating a DNAI preference using performance information related to the EAS 430 will be described with reference to Fig. 12. In Fig. 12, an Edge Computing Service Provider (ECSP) Management System is used to monitor the performance information of the EAS 430. The ECSP Management System may be part of a 3GPP management system that enables an NF service consumer, such as the EAS 430, to manage an Edge Data Network (EDN) using a management service defined in 3GPP. The EDN corresponds to, for example, the local part of DN 170.

[0073] First, the EES 420 executes a createMeasurementjob operation with the ECSP Management System (S51). Specifically, the EES 420 requests the ECSP Management System to collect performance data related to the EAS 430 and receives the performance data. The performance data may be, for example, the number of input packets, the number of output packets, the traffic rate, and the number of error packets per DNAI. Alternatively, the performance data may be, for example, the response time, availability, reliability, and bandwidth per DNAI. The EES 420 may also specify a method for the ECSP Management System to report the performance data. For example, the performance data may be reported by the ECSP Management System transmitting performance data accumulated over a predetermined period of time as a file to the EES 420. Alternatively, the performance data may be reported by the ECSP Management System transmitting the performance data to the EES 420 each time the performance data is generated or acquired. This method of periodically transmitting performance data as time-series data each time the performance data is generated may be referred to as a streaming service. The following describes the procedure by which the EES 420 receives performance information for a streaming service.

[0074] Next, in order for the ECSP Management System to transmit the performance information as streaming data to the EES 420, the EES 420 establishes a streaming connection with the ECSP Management System (S52).

[0075] Next, the ECSP Management System collects performance information related to the EAS 430 and transmits the collected performance information to the EES 420 as a streaming service (S53). As a result, the EES 420 receives the performance information.

[0076] Next, the EES 420 generates a DNAI preference using the performance information (S54). Below, as an example, a procedure in which the EES 420 generates a DNAI preference using a decision tree model will be described. Note that the trained model used to generate the DNAI preference is not limited to a decision tree model.

[0077] A decision tree model determines an output value (objective variable) for a given input value (explanatory variable). For example, a decision tree model is generated by having a program that implements a machine learning decision tree algorithm learn the input and output values. In the learning phase, performance monitoring data is prepared in advance as learning data, and a DNAI Preference value that serves as the correct answer is prepared for each piece of performance monitoring data. By inputting this performance monitoring data for learning and the DNAI Preference value that serves as the correct answer into the decision tree model, patterns that serve as decision criteria become clear.

[0078] For example, the EES 420 has a decision tree model that determines the DNAI preference according to the value indicated by the maximum response time for each path identified by the DNAI, and determines the DNAI preference using the decision tree model. The shorter the maximum response time, the smaller the DNAI preference value that is determined.

[0079] Similarly, the EES 420 may have a decision tree model that determines the DNAI preference according to the value indicated by the availability of each DNAI, and may use the decision tree model to determine the DNAI preference. If higher availability is reported, a smaller DNAI preference value is determined.

[0080] Furthermore, the EES 420 may have a decision tree model that determines the DNAI preference according to the value indicated by the connection bandwidth for each DNAI, and may use the decision tree model to determine the DNAI preference. If a larger connection bandwidth is notified, a smaller DNAI preference value is determined. In other words, the EES 420 can determine the DNAI preference value by acquiring the DNAI preference value output by inputting the value indicated by the connection bandwidth for each DNAI into the decision tree model.

[0081] Then, a decision tree model for determining DNAI preference may be created by combining the above three or other performance information, and the DNAI preference may be determined using the decision tree model.

[0082] After generating the DNAI preference, the EES 420 executes the processes of steps S31 to S36 in FIG. 8 and notifies the SMF 120 of the DNAI preference. As described above, in this embodiment, the EES 420 generates a cost value based on performance information for each communication path. The performance information may be, for example, the number of input packets, the number of output packets, the traffic rate, the number of error packets, etc. for each DNAI. Alternatively, the performance information may be, but is not limited to, the response time, availability, reliability, bandwidth, etc. for each DNAI, and may be any dynamic information (information that changes over time) related to the communication status of the communication path.

[0083] As described above, the EES 420 according to the fifth embodiment can generate a DNAI preference for each DNAI by using performance information received from the ECSP Management System. As a result, similar to the third embodiment, the SMF 120 can establish a session with the EES 420 by using the DNAI preference for each DNAI. Note that in the above description, an example has been described in which a decision tree model, which is a representative example of supervised learning, is used as the trained model. However, the trained model used to calculate the DNAI preference value is not limited to supervised learning, and the DNAI preference value may be calculated using a trained model generated by unsupervised learning, reinforcement learning, or the like.

[0084] Sixth Embodiment Next, a flow of a process for generating a DNAI preference using traffic prediction information will be described with reference to Fig. 13. The traffic prediction information may be generated in a Network Data Analytics Function (NWDAF), which is a node arranged in the service-based architecture of the core network, but the node that generates the prediction information is not limited to this. The NWDAF collects data from NFs connected via a service-based interface and analyzes the collected data.

[0085] First, the EES 420 subscribes to the collection of analytical information (S61) using Nnef_AnalyticsExposure_Subscribe, a service provided by the NEF 140. The EES 420 may notify the NEF 140 of, for example, an AF ID (Identifier) ​​that identifies the AF and an Analytics ID that identifies the requested analysis item (analysis item).

[0086] Next, the NEF 140 applies for collection of analytical information using Nnwdaf_AnalyticsSubscription_Subscribe, a service provided by the NWDAF (S62). For example, the NEF 140 may store information that combines an AF ID and an Analytics ID as information for managing the analysis items that the AF ID is permitted to collect. If the combination of the AF ID and the Analytics ID notified by the EES 420 is included in the information stored in advance, the NEF 140 may execute a process of applying to the NWDAF for collection of analytical information.

[0087] Next, the NWDAF notifies the NEF 140 of the analysis information by using Nnwdaf_AnalyticsSubscription_Notify, a service provided by the NWDAF (S63). Next, the NEF 140 notifies the EES 420 of the analysis information by using Nnef_AnalyticsExposure_Notify, a service provided by the NEF 140.

[0088] Here, the analysis information acquired by the EES 420 will be described. The EES 420 may acquire DN Performance Analytics and UE mobility Analytics as the analysis information. In step S61, the EES 420 may set information identifying each of the DN Performance Analytics and the UE mobility Analytics to the Analytics ID. Alternatively, in step S61, the EES 420 may set information identifying one of the DN Performance Analytics and the UE mobility Analytics to the Analytics ID. In this case, after acquiring the analysis information related to the identification information set to the Analytics ID, the EES 420 may set information identifying the other of the DN Performance Analytics and the UE mobility Analytics to the Analytics ID, and repeat steps S61 to S64.

[0089] DN Performance Analytics is, for example, an analysis of the User Plane for each DNAI, and the analysis content may be, for example, an average or maximum traffic rate, an average or maximum packet delay, an average or maximum packet loss rate, etc. Alternatively, DN Performance Analytics may be an analysis of the User Plane for each UPF.

[0090] The UE mobility analytics may indicate, for example, the location of the UE within a predetermined period of time. The location of the UE may be indicated using, for example, a Tracking Area (TA) or a cell.

[0091] Analysis information such as DN performance analytics and UE mobility analytics may be statistical information using past data, or may be predictive information predicted from past data.

[0092] Next, the EES 420 generates a DNAI preference using the acquired analysis information (or prediction information) (S65). The EES 420 may generate a DNAI preference based on the analysis information using a decision tree model used in machine learning. In the learning phase, training DN performance analytics and training UE mobility analytics may be prepared in advance as training data. Furthermore, correct DNAI preference values ​​are prepared for each training DN performance analytics and training UE mobility analytics. The EES 420 inputs these training DN performance analytics and training UE mobility analytics and the correct DNAI preference values ​​into the decision tree model, thereby clarifying patterns that serve as judgment criteria.

[0093] For example, the EES 420 may have a decision tree model that determines the DNAI preference according to the value indicated by the maximum traffic rate, and determine the DNAI preference by inputting the maximum traffic rate value into the decision tree model. A larger maximum traffic rate value results in a smaller DNAI preference value being determined. Similarly, the EES 420 may have a decision tree model that determines the DNAI preference according to the value indicated by the average packet delay, and use the decision tree model to determine the DNAI preference. A smaller average packet delay value is notified, and a smaller DNAI preference value is determined. The EES 420 may also have a decision tree model that determines the DNAI preference according to the value indicated by the maximum packet delay, and use the decision tree model to determine the DNAI preference. A smaller maximum packet delay value is notified, and a smaller DNAI preference value is determined. Alternatively, a decision tree model that determines the DNAI preference in combination with the above three or other performance information may be maintained, and the DNAI preference value may be determined using the decision tree model.

[0094] Furthermore, the EES 420 may detect that a UE is approaching based on UE Mobility Analytics information, and may determine a DNAI Preference value for the detected UE using the decision tree model described above.

[0095] After generating the DNAI preference, the EES 420 executes the processes of steps S31 to S36 in Fig. 8 and notifies the SMF 120 of the DNAI preference. Note that, although the above description has been given of an example in which the EES 420 determines the DNAI preference value using a decision tree model, the trained model used to determine the DNAI preference value is not limited to a decision tree model. For example, the EES 420 may determine the DNAI preference value using a trained model generated by unsupervised learning or reinforcement learning.

[0096] As described above, the EES 420 according to the sixth embodiment can generate a DNAI preference for each DNAI by using the analysis information received from the NWDAF. As a result, similar to the third embodiment, the SMF 120 can establish a session to the EES 420 by using the DNAI preference for each DNAI.

[0097] (Seventh embodiment) Next, the flow of the DNAI preference transfer process will be described with reference to Figure 14. First, the SMF 120 registers with the EAS Deployment information Change Notification service provided by the NEF 140 by sending an Nnef_EASDeployment_Subscribe Request message to the NEF 140 (S71). For example, the SMF 120 may set a DNAI in the Nnef_EASDeployment_Subscribe Request message. Next, the NEF 140 sends an Nnef_EASDeployment_Subscribe Response message to the SMF 120 as a response message to the Nnef_EASDeployment_Subscribe Request message (S72).

[0098] Next, the EES 420 transmits a request message to use the Nnef_EASDeployment_Create service provided by the NEF 140 (S73). Here, the EES 420 generates a DNAI preference in the same manner as in any of the third to sixth embodiments. The EES 420 notifies the NEF 140 of the generated DNAI preference by including it in the request message.

[0099] Next, the NEF 140 notifies the UDR 80 of the DNAI preference using the Nudr_DM_Create service provided by the UDR 80 (S74). The NEF 140 may notify the UDR 80 of the DNAI preference by sending a Nudr_DM_Create Request message including an AF Request including the DNAI preference.

[0100] Next, the UDR 80 transmits a Nudr_DM_Create Response message to the NEF 140 as a response message to the Nudr_DM_Create Request message (S75). Next, the NEF 140 transmits a Nnef_EASDeployment_Create Response message to the EES 420 as a response message to the request message in step S73 (S76).

[0101] Next, the NEF 140 sends an Nnef_EASDeployment_Notify Request message to the SMF 120 to notify the SMF 120 that the DNAI Preference of the DNAI received in step S71 is recorded in the UDR 80 (S77). Next, the SMF 120 sends an Nnef_EASDeployment_Notify Response message to the NEF 140.

[0102] After being notified in step S77 that a DNAI preference is recorded in the UDR 80, the SMF 120 may acquire the DNAI preference from the UDR 80.

[0103] As described above, the SMF 120 according to the seventh embodiment can obtain the DNAI preference generated in the EES 420 from the UDR 80. As a result, similar to the third embodiment, the SMF 120 can establish a session to the EES 420 using the DNAI preference for each DNAI.

[0104] FIG. 15 is a block diagram showing a configuration example of an edge node 10 and a core network node 30 (hereinafter referred to as the edge node 10, etc.). Referring to FIG. 15, the core network node 10, etc. includes a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 may be used to communicate with a network node. The network interface 1201 may include, for example, a network interface card (NIC) conforming to the IEEE 802.3 series. IEEE stands for Institute of Electrical and Electronics Engineers.

[0105] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform the processing of the edge node 10 and the like described using flowcharts in the above-described embodiments. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

[0106] The memory 1203 is configured by a combination of volatile memory and non-volatile memory. The memory 1203 may include storage located remotely from the processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O (Input / Output) interface (not shown).

[0107] 15, the memory 1203 is used to store software modules. The processor 1202 reads and executes these software modules from the memory 1203, thereby performing the processing of the edge node 10 and the like described in the above-described embodiment.

[0108] As described with reference to FIG. 15, each of the processors included in the edge nodes 10 and the like executes one or more programs including a set of instructions for causing a computer to perform the algorithm described with reference to the drawings.

[0109] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

[0110] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0111] Each drawing is merely an example for describing one or more embodiments. Each drawing may not relate to only one particular embodiment, but may also relate to one or more other embodiments. As will be understood by those skilled in the art, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings to create, for example, an embodiment not explicitly shown or described. Not all features or steps shown in any one drawing are necessary to describe an exemplary embodiment, and some features or steps may be omitted. The order of steps described in any drawing may be changed as appropriate.

[0112] A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes.

[0113] (Supplementary Note 1) An edge node arranged in an edge computing environment, comprising: a generation unit that generates cost values ​​corresponding to each of a plurality of routes for transferring user plane data between a core network and the edge computing environment; and a communication unit that transmits the cost values ​​to a first core network node arranged in the core network. (Supplementary Note 2) The edge node according to Supplementary Note 1, wherein the communication unit transmits the cost values ​​to the core network node as control plane data. (Supplementary Note 3) The edge node according to Supplementary Note 2, wherein a destination of the control plane data is a gateway arranged in the core network. (Supplementary Note 4) The edge node according to any one of Supplements 1 to 3, wherein each of the plurality of routes is identified by a Data Network Access Identifier (DNAI). (Supplementary Note 5) The edge node according to Supplementary Note 4, wherein the DNAI is an identifier for identifying a route between a second core network node arranged in the core network and a node in the edge computing environment. (Supplementary Note 6) The edge node according to any one of Supplements 1 to 5, wherein the generation unit generates the cost value for each of the routes using reference information for each of the routes. (Supplementary Note 7) The edge node according to Supplementary Note 6, wherein the reference information is bandwidth information for each of the plurality of routes. (Supplementary Note 8) The edge node according to any one of Supplementary Notes 1 to 5, wherein the generation unit generates the cost value for each of the routes using performance information for each of the routes. (Supplementary Note 9) The edge node according to Supplementary Note 8, wherein the performance information is information generated based on the number of packets forwarded on each of the plurality of routes or a learned model. (Supplementary Note 10) The edge node according to any one of Supplementary Notes 1 to 5, wherein the generation unit generates the cost value for each of the routes using predicted information for traffic for each of the routes. (Supplementary Note 11) The edge node according to Supplementary Note 10, wherein the predicted information is traffic information generated based on a learned model.(Supplementary Note 12) A core network node arranged in a core network, comprising: a first receiving unit that receives, from a session management device arranged in the core network, a request message for requesting notification of cost values ​​corresponding to each of a plurality of routes for forwarding user plane data between the core network and an edge computing environment, a second receiving unit that receives the cost values ​​from an edge node arranged in the edge computing environment, and a transmitting unit that, when the cost values ​​are received, transmits the cost values ​​to the session management device. (Supplementary Note 13) The core network node according to Supplementary Note 12, wherein the transmitting unit notifies the session management device that the cost values ​​are recorded in a core network node in the core network. (Supplementary Note 14) A communication system comprising an edge node arranged in an edge computing environment and a core network node arranged in a core network, wherein the edge node generates a cost value corresponding to each of a plurality of routes for forwarding user plane data between the core network and the edge computing environment, and transmits the cost values ​​to the core network node, and the core network node receives the cost values ​​and notifies the session management device of the cost values. (Supplementary Note 15) The communication system according to Supplementary Note 14, wherein the edge node transmits the cost values ​​to the core network node as control plane data. (Supplementary Note 16) A communication method executed in an edge application device arranged in an edge computing environment, the communication method comprising: generating cost values ​​corresponding to each of a plurality of paths for transferring user plane data between a core network and the edge computing environment; and transmitting the cost values ​​to a first core network node arranged in the core network. (Supplementary Note 17) The communication method according to Supplementary Note 16, wherein the cost values ​​are transmitted to the core network node as control plane data.(Supplementary Note 18) The communication method according to Supplementary Note 17, wherein a destination of the control plane data is a gateway arranged in the core network. (Supplementary Note 19) The communication method according to any one of Supplements 16 to 18, wherein each of the plurality of routes is identified by a DNAI (Data Network Access Identifier). (Supplementary Note 20) The communication method according to Supplementary Note 19, wherein the DNAI is an identifier for identifying a route between a second core network node arranged in the core network and a node in the edge computing environment. (Supplementary Note 21) The communication method according to any one of Supplements 16 to 20, wherein, when generating the cost values, reference information for each of the routes is used to generate the cost values ​​for each of the routes. (Supplementary Note 22) The communication method according to Supplementary Note 21, wherein, when generating the cost values, the reference information is bandwidth information for each of the plurality of routes. (Supplementary Note 23) The communication method according to any one of Supplements 16 to 20, wherein, when generating the cost values, performance information for each of the routes is used to generate the cost values ​​for each of the routes. (Supplementary Note 24) The communication method according to Supplementary Note 23, wherein, when generating the cost values, the performance information is information generated based on the number of packets forwarded on each of the plurality of routes or a learned model. (Supplementary Note 25) The communication method according to any one of Supplements 16 to 20, wherein, when generating the cost values, the cost values ​​for each of the routes are generated using predicted information of traffic for each of the routes. (Supplementary Note 26) The communication method according to Supplementary Note 25, wherein the predicted information is traffic information generated based on a learned model.(Supplementary Note 27) A communication method executed in a core network node arranged in a core network, comprising: receiving, from a session management device arranged in the core network, a request message for requesting notification of cost values ​​of each of a plurality of communication paths for forwarding user plane data between the core network and an edge computing environment; receiving the cost values ​​from an edge node arranged in the edge computing environment; and, upon receiving the cost values, transmitting the cost values ​​to the session management device. (Supplementary Note 28) The communication method according to Supplementary Note 27, further comprising: notifying the session management device that the cost values ​​exist by notifying the session management device that the cost values ​​are recorded in a core network node in the core network. (Supplementary Note 29) A program to be executed by a computer device that is an edge node arranged in an edge computing environment, causing the computer to generate cost values ​​corresponding to each of a plurality of paths for forwarding user plane data between a core network and the edge computing environment, and transmitting the cost values ​​to a first core network node arranged in the core network. (Supplementary Note 30) A program to be executed by a computer device that is a core network node arranged in a core network, the program causing the computer to receive, from a session management device arranged in the core network, a request message for requesting notification of cost values ​​corresponding to each of a plurality of routes for transferring user plane data between the core network and an edge computing environment, receive the cost values ​​from an edge node arranged in the edge computing environment, and, upon receiving the cost values, transmit the cost values ​​to the session management device.

[0114] Some or all of the elements (e.g., configurations and functions) described in Supplementary Notes 2 to 11 that are dependent on Supplementary Note 1 may also be dependent on Supplementary Note 29 in the same dependent relationship as Supplementary Notes 2 to 11. Some or all of the elements (e.g., configurations and functions) described in Supplementary Note 28 that are dependent on Supplementary Note 27 may also be dependent on Supplementary Note 30 in the same dependent relationship as Supplementary Note 28. Some or all of the elements described in any of the Supplements may be applied to various hardware, software, recording means for recording software, systems, and methods.

[0115] This application claims priority based on Japanese Patent Application No. 2023-032493, filed on March 3, 2023, the disclosure of which is incorporated herein by reference in its entirety.

[0116] 10 Edge node 11 Generation unit 12 Communication unit 20 Core network node 30 Core network node 31 Receiving unit 32 Receiving unit 33 Transmitting unit 40 Session management device 50 AN 60 UPF 62 UPF 64 UPF 70 UE 80 UDR 90 NRF 100 AMF 110 PCF 120 SMF 130 AF 140 NEF 150 UDM 160 EASDF 170 Local part of DN 200 Core network 300 Edge computing environment 400 EHE 410 ECS 420 EES 430 EAS 500 Network 601 GW 602 GW

Claims

1. An edge node disposed in an edge computing environment, a generating means for generating cost values ​​corresponding to each of a plurality of paths for transferring user plane data between a core network and the edge computing environment; and a communication means for transmitting the cost value to a first core network node disposed in the core network.

2. The communication means is The edge node of claim 1 , wherein the cost value is transmitted to the core network node as control plane data.

3. The generating means The edge node according to claim 1 or 2, wherein the cost value for each of the routes is generated using traffic prediction information for each of the routes.

4. The prediction information is traffic information generated based on a trained model. The edge node according to claim 3 .

5. A core network node disposed in a core network, a first receiving means for receiving, from a session management device disposed in the core network, a request message for requesting notification of cost values ​​corresponding to each of a plurality of paths for transferring user plane data between the core network and an edge computing environment; a second receiving means for receiving the cost value from an edge node disposed in the edge computing environment; a transmitting means for transmitting the cost value to the session management device when the cost value is received.

6. A communication method executed in an edge application device disposed in an edge computing environment, generating cost values ​​corresponding to each of a plurality of paths for forwarding user plane data between a core network and the edge computing environment; transmitting the cost value to a first core network node located in the core network.

7. The communication method according to claim 6 , wherein the cost values ​​are transmitted to the core network node as control plane data.

8. A communication method performed in a core network node located in a core network, comprising: receiving, from a session management device disposed in the core network, a request message for requesting notification of cost values ​​of each of a plurality of communication paths for transferring user plane data between the core network and an edge computing environment; receiving the cost values ​​from edge nodes disposed in the edge computing environment; a communication method, wherein, when the cost value is received, the cost value is transmitted to the session management device;

9. A program to be executed on a computer device that is an edge anode disposed in an edge computing environment, generating cost values ​​corresponding to each of a plurality of paths for forwarding user plane data between a core network and the edge computing environment; a program for causing a computer to execute the program to transmit the cost value to a first core network node disposed in the core network;

10. A program to be executed by a computer device that is a core network node arranged in a core network, receiving, from a session management device disposed in the core network, a request message for requesting notification of cost values ​​corresponding to each of a plurality of paths for transferring user plane data between the core network and an edge computing environment; receiving the cost values ​​from edge nodes disposed in the edge computing environment; a program that causes a computer to execute the following: when the cost value is received, transmitting the cost value to the session management device;