Core network device and communication method

Abstract

The purpose of the present invention is to provide a core network device which is capable of preventing reduction in quality relating to an application service when traffic is distributed to a plurality of computing resources. A core network device according to the present disclosure is provided with: a reception unit that receives, from an application server that manages a plurality of computing resources for providing application services to a communication terminal via a mobile network, allocation information relating to traffic in a first computing resource and in a second computing resource that are included in the plurality of computing resources; and a transmission unit that allocates and transmits data items received from the communication terminal to the first computing resource and to the second computing resource, in accordance with the allocation information.

Description

Technical Field

[0001] The present disclosure relates to a core network device, an application server, a communication system, a communication method, and a program.

Background Art

[0002] Various application services are provided via a mobile network. An operator providing an application service distributes and arranges computing resources using a physical server, a virtual server, or the like over a plurality of locations. The application operator deploys an application server to the computing resources to provide a high-quality and highly reliable application service. For example, the application server may be a server that provides applications such as a mail server, a video distribution server, a Web server, and the like. In order to provide a high-quality and highly reliable application service, the operator may dynamically change the arrangement of the computing resources according to the usage status of the computing resources and the like.

[0003] The purpose of dynamically changing the allocation of computing resources is to achieve both acceptable costs and the availability of necessary computing resources. Providers of application services can secure computing resources using cloud services. Cloud services offer various options, such as high-performance, high-cost computing resources, or general-purpose, low-cost computing resources. Furthermore, long-term contracts for high-performance computing resources or spot usage of unused surplus computing resources can provide resources at a lower cost. Additionally, reserved computing resources can be allocated to limited user groups, while other users can be provided with on-demand or spot computing resources. This can reduce the overall cost of application services. In this way, application providers secure the necessary computing resources when needed, based on acceptable costs, and release those resources when they are not needed. Through the dynamic operation of distributed computing resources, application providers aim to achieve both acceptable costs and the availability of computing resources.

[0004] Non-Patent Document 1 discloses a process for distributing or offloading traffic in a mobile network. Non-Patent Document 1 discloses that an Application Function (AF) can achieve traffic distribution using a Network Exposure Function (NEF) service. For example, the AF sends an AF request to the NEF that includes N6 Traffic Routing requirements as an Information element. N6 Traffic Routing requirements are information that specifies the traffic route at N6 reference points as defined by 3GPP®.

[0005] Furthermore, Non-Patent Document 2 specifies the TrafficInfluence API as an Application Programming Interface (API) related to N6 Traffic Routing requirements. The TrafficInfluence API specifies that it is possible to specify multiple RouteToLocation attributes in the trafficRoutes attribute. Since the RouteToLocation attribute indicates the destination of traffic, specifying multiple RouteToLocation attributes enables the distribution or offloading of traffic related to a particular application service. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 23.501 V17.5.0 (2022-06) [Non-Patent Document 2] 3GPP TS 29.522 V17.6.0 (2022-06) [Overview of the project] [Problems that the invention aims to solve]

[0007] This section describes the case where traffic is forwarded by specifying multiple RouteToLocation attributes in the operation of dynamically managed distributed computing resources. In this case, for example, at a destination, the computing resource may go through a resource deployment state, then an operational state, and then a warm-up state after resource deployment before achieving its full performance. If traffic is forwarded to a destination in such a resource deployment or warm-up state, the traffic may not be processed properly, and users or communication terminals may be unable to receive application services.

[0008] One of the purposes of this disclosure is, in light of the above-mentioned issues, to provide a core network device, application server, communication system, and communication method that can suppress the degradation of the quality of application services when traffic is distributed across multiple computing resources. [Means for solving the problem]

[0009] A core network device according to a first aspect of the present disclosure is a core network device that constitutes a mobile network, comprising: a receiving unit that receives traffic allocation information for a first computing resource and a second computing resource included in a plurality of computing resources from an application server that manages a plurality of computing resources that provide application services to a communication terminal via the mobile network; and a transmitting unit that distributes and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information.

[0010] An application server according to a second aspect of this disclosure includes a management unit that manages a first computing resource and a second computing resource that provide application services to a communication terminal via a mobile network, and a communication unit that transmits traffic allocation information for the first computing resource and the second computing resource to a core network device constituting the mobile network.

[0011] A communication system according to a third aspect of this disclosure includes: an application server that manages a first computing resource and a second computing resource that provide application services to a communication terminal via a mobile network, and transmits traffic allocation information for the first computing resource and the second computing resource to a core network device constituting the mobile network; and a core network device that receives traffic allocation information for the first computing resource and the second computing resource included in the plurality of computing resources from the application server that manages a plurality of computing resources that provide application services to a communication terminal via a mobile network, and distributes data received from the communication terminal to the first and second computing resources according to the allocation information.

[0012] A communication method according to a fourth aspect of this disclosure is performed in a core network device that receives traffic allocation information for a first computing resource and a second computing resource included in a plurality of computing resources from an application server that manages a plurality of computing resources that provide application services to a communication terminal via a mobile network, and distributes and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information. [Effects of the Invention]

[0013] This disclosure provides a core network device, application server, communication system, and communication method that can prevent a degradation in the quality of application services when traffic is distributed across multiple computing resources. [Brief explanation of the drawing]

[0014] [Figure 1]It is a configuration diagram of an application server according to the present disclosure. [Figure 2] It is a configuration diagram of a core network device according to the present disclosure. [Figure 3] It is a diagram showing the flow of communication processing executed in an application server according to the present disclosure. [Figure 4] It is a diagram showing the flow of communication processing executed in a core network device according to the present disclosure. [Figure 5] It is a diagram of a communication system according to the present disclosure. [Figure 6] It is a diagram for explaining a resource group according to the present disclosure. [Figure 7] It is a diagram showing the flow of traffic offload processing according to the present disclosure. [Figure 8] It is a diagram for explaining the TrafficInfluence API according to the present disclosure. [Figure 9] It is a diagram for explaining the AF Request information according to the present disclosure. [Figure 10] It is a diagram for explaining the TrafficControlData attribute according to the present disclosure. [Figure 11] It is a diagram for explaining a resource group according to the present disclosure. [Figure 12] It is a diagram for explaining the TrafficInfluence API according to the present disclosure. [Figure 13] It is a diagram for explaining the AF Request information according to the present disclosure. [Figure 14] It is a diagram for explaining the TrafficControlData attribute according to the present disclosure. [Figure 15] It is a configuration diagram of an application server and a core network device according to the present disclosure.

Modes for Carrying Out the Invention

[0015] (Embodiment 1) The following describes an example configuration of the application server 10 using Figure 1. The application server 10 runs on computing resources. These computing resources may be computer devices that operate by having a processor execute programs stored in memory.

[0016] The application server 10 includes a management unit 11 and a communication unit 12. The management unit 11 and the communication unit 12 may be software or modules whose processing is performed by the processor executing a program stored in memory. Alternatively, the management unit 11 and the communication unit 12 may be hardware such as a circuit or chip.

[0017] The management unit 11 manages a first computing resource and a second computing resource that provide application services to communication terminals via a mobile network. The mobile network may be, for example, a network whose operation and processing are defined in 3GPP (3rd Generation Partnership Project). The mobile network may consist of, for example, an access network and a core network. The access network mainly consists of access devices that communicate with communication terminals. The access devices may, for example, communicate wirelessly with communication terminals. The access network may be Non-3GPP access using communication technologies such as WiFi (Wireless Fidelity) (registered trademark). The core network consists of core network devices. The core network devices may be, for example, devices that perform mobility control, session control, authentication, etc., of communication terminals, or devices that manage subscriber information regarding users of communication terminals, terminal information of communication terminals, etc. The core network devices may be, for example, devices that process user data of communication terminals, or devices that distribute the routing of user data related to communication terminals. The core network may consist of multiple core network devices that perform different controls.

[0018] A communication terminal may be a computer device that operates by a processor executing a program stored in memory. For example, a communication terminal may be a smartphone or an IoT (Internet of Things) device. Alternatively, a communication terminal may be a dedicated terminal used for application services. For example, if the first and second computing resources provide XR (Extended Reality), the communication terminal may be a headset-type terminal, etc. If the first and second computing resources provide autonomous driving services, the communication terminal may be a communication device mounted on a vehicle or the vehicle itself. Alternatively, a communication terminal may be a UE (User Equipment), which is a general term for communication terminals in 3GPP.

[0019] Computing resources may be computer resources such as processors and memory for running an application, and may be divided into physical computer devices. In this case, a computer device having the first computing resources is different from a computer device having the second computing resources. Alternatively, computing resources may be each virtual machine included in multiple virtual machines operating independently of each other on one or more computer devices. A virtual machine may be called a virtual server, virtual instance, or simply an instance. Alternatively, computing resources may be each virtual machine included in multiple virtual machines launched on a group of computer devices operating collaboratively. Alternatively, computing resources may be two or more virtual machines. Alternatively, computing resources may be containers running on a container engine.

[0020] Managing computing resources may involve starting or stopping computing resources that are virtual machines. Alternatively, managing computing resources may involve determining the functions or roles of computing resources. Or, managing computing resources may involve determining the computer resources that each computing resource uses.

[0021] The communication unit 12 transmits traffic allocation information for the first computing resource and the second computing resource to the core network device constituting the mobile network. The communication unit 12 may also transmit a message indicating the said allocation information. The message may include the said allocation information.

[0022] Computing resources transmit and receive data with communication terminals and provide application services. Here, data transmitted from communication terminals to computing resources is called uplink data, and data transmitted from computing resources to communication terminals is called downlink data. Traffic allocation information may, for example, indicate the proportion of uplink data directed to computing resources. Alternatively, traffic allocation information may also be, for example, the proportion of PDU (Protocol Data Unit) sessions directed to computing resources. Furthermore, traffic allocation information may also be, for example, the proportion of bps directed to computing resources. Note that traffic allocation information is not limited to the examples above.

[0023] The allocation information may, for example, indicate the amount of traffic processed by the first computing resource and the second computing resource. Alternatively, the allocation information may indicate the ratio of the amount of traffic processed by the first computing resource to the amount of traffic processed by the second computing resource. The amount of traffic or the ratio of traffic in the allocation information may be specified according to time (time, unit time, predetermined period, etc.). Furthermore, the amount of traffic or the ratio of traffic in the allocation information may be the ratio of the number of communication terminals or the ratio of the number of groups of communication terminals. The allocation information may be changed in stages. Furthermore, the allocation information may indicate the ratio of the amount of traffic that is changed in stages.

[0024] The allocation information may be linked to the application identifier and / or traffic filtering information. The traffic volume may be, for example, the amount of uplink data, the number of PDU sessions, or bps. The traffic volume is not limited to the examples above.

[0025] Next, an example configuration of the core network device 20 will be explained using Figure 2. The core network device 20 may be a computer device that operates by having a processor execute a program stored in memory. The core network device 20 is a device that constitutes a mobile network.

[0026] The core network device 20 has a receiving unit 21 and a transmitting unit 22. The receiving unit 21 and the transmitting unit 22 may be software or modules whose processing is performed by a processor executing a program stored in memory. Alternatively, the receiving unit 21 and the transmitting unit 22 may be hardware such as a circuit or chip.

[0027] The receiving unit 21 receives traffic allocation information for the first and second computing resources, which are included in a plurality of computing resources, from the application server 10. The receiving unit 21 may also receive a message indicating the said allocation information. The receiving unit 21 may also receive the allocation information via one or more other core network devices. The application server 10 manages a plurality of computing resources that provide application services to communication terminals via the mobile network.

[0028] The transmitting unit 22 distributes the data received from the communication terminal to the first computing resource and the second computing resource according to the distribution information. Distributing can also be rephrased as transmitting. For example, the transmitting unit 22 specifies the identification information of the first computing resource and the identification information of the second computing resource and transmits the data received from the communication terminal.

[0029] The core network device 20 may also include a control unit, which is not shown in Figure 2. In this case, the control unit controls the transmission unit 22 to distribute the data received from the communication terminal to the first computing resource and the second computing resource based on the distribution information. Based on the control unit's control, the transmission unit 22 transmits the data allocated to the first and second computing resources to the first and second computing resources, respectively.

[0030] Next, the flow of communication processing performed in the application server 10 will be explained using Figure 3. First, the management unit 11 manages the first computing resource and the second computing resource that provide application services to communication terminals via the mobile network (S11). Next, the communication unit 12 transmits traffic allocation information for the first computing resource and the second computing resource to the core network device that constitutes the mobile network (S12).

[0031] Next, the flow of communication processing performed in the core network device 20 will be explained using Figure 4. First, the receiving unit 21 receives traffic allocation information for the first computing resource and the second computing resource, which are included in a plurality of computing resources, from the application server 10 (S21). The receiving unit 21 may receive the message via one or more other core network devices. Next, the transmitting unit 22 distributes the data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information (S22).

[0032] As explained above, the application server 10 specifies the amount of traffic each computing resource will handle. This allows, for example, when distributing or offloading traffic from the first computing resource to the second computing resource, the amount of traffic handled by the second computing resource may be set to be small. As a result, even if the second computing resource cannot handle a large amount of traffic while it is starting up or warming up, the impact of a decrease in the quality of the application service can be minimized.

[0033] (Embodiment 2) Next, an example of a communication system configuration will be explained using Figure 5. The communication system in Figure 5 mainly shows the configuration of a communication system specified in 3GPP. The communication system in Figure 5 has a UE110. Furthermore, the communication system has a gNB100 which constitutes the access network. Furthermore, the communication system has a core network consisting of NEF (Network Exposure Function) node 40, UDR (Unified Data Repository) node 50, PCF (Policy Control Function) node 60, SMF (Session Management Function) node 70, UPF (User Plane Function) node 80, and AMF (Access and Mobility management Function) node 90. In the following explanation, each node will be referred to as NEF40, UDR50, PCF60, SMF70, UPF80, and AMF90. Also, the nodes may correspond to entities (devices) or functions (functions). Furthermore, the communication system includes an EHE (Edge Hosting Environment) 31, an EHE 32, an AF controller 33, and a Gateway 34, which constitute the DN (Data Network) 30.

[0034] DN30 is an external network system that connects to 5G (Fifth Generation) systems under 3GPP.

[0035] The AF controller 33 is a Network Function that runs application services hosted on a physical or virtual server, and provides Application influence on traffic routing services to Application Function (AF) operators. In other words, the AF controller 33 executes Application influence on traffic routing services using applications started on a physical or virtual server. The AF may be an application server started on a physical or virtual server. The Application influence on traffic routing service determines the route of traffic related to a PDU session based on a request from the AF. In other words, a request from the AF influences the route of traffic related to a PDU session. More specifically, the Application influence on traffic routing service may be a service used by the AF to specify which traffic to offload to the core network. Note that the node, collectively referred to as AF controller 33 and AF, may be an AF in the 3GPP standard.

[0036] EHE31 and EHE32 are edge computing environments that constitute DN30. In the following description, EHE31 will be described as the current edge computing environment providing application services, and EHE32 as the new edge computing environment to which traffic is offloaded. EHE31 and EHE32 may each be a data center with multiple computer devices installed. Furthermore, EHE31 may be distributed across different buildings, different regions, etc., from EHE32.

[0037] Gateway34 is a device that interconnects with UPF80 within DN30, and may be, for example, a router.

[0038] NEF40 exposes services provided by Network Functions, such as those defined in 3GPP TS23.501 V17.5.0 (2022-06), to external edge computing environments. Furthermore, NEF40 sends and receives structured data to and from edge computing environments or other core network devices.

[0039] UDR50 provides services to NEF40 or PCF60 for storing or retrieving structured data. UDR50 also retrieves and stores policies from PCF60.

[0040] PCF60 generates policy rules and provides them to the C-Plane function, which processes C (Control)-Plane data.

[0041] The SMF70 manages PDU sessions in 5G systems.

[0042] UPF80 acts as an anchor point in the 5G system, interconnecting PDU sessions with external edge computing environments. In other words, UPF80 may be connected to Gateway34 in DN30 via an L2 network. The L2 network may be referred to as, for example, N6-LAN (Local Area Network). UPF80 may also be a device that processes user data from communication terminals, for example, and may route user data related to communication terminals.

[0043] The AMF90 manages access to or movement of the UE110.

[0044] The gNB100 is a base station that supports the communication method defined as 5G. UE110 is defined in 3GPP as a general term for communication terminals.

[0045] The UE110 communicates wirelessly with the gNB100.

[0046] Next, we will explain resource groups using Figure 6. Figure 6 shows that multiple computing resources providing a common application service constitute a single resource group. In Figure 6, computing resources are described as AFs (Application Functions). In Figure 6, n AFs, AF#r_1 to AF#r_n (where n is an integer greater than or equal to 2), constitute resource group #g_1. For example, resource group #g_1 may provide an autonomous driving service.

[0047] Each computing resource (AF) constituting resource group #g_1 may be distributed across multiple EHEs. For example, AF#r_1 to AF#r_2 may be started in EHE31, and AF#r_3 to AF#r_n may be started in EHE32. The AF controller 33 may control the startup of AF#r_1 to AF#r_n. The AF controller 33 may, for example, determine which AFs from AF#r_1 to AF#r_n included in resource group #g_1 will start in EHE31 and which will start in EHE32. Furthermore, the AF controller 33 may determine which AFs that are running in EHE31 or EHE32 will be stopped.

[0048] Next, the traffic offloading process will be explained using Figure 7. First, the application service operator creates N6 Traffic Routing requirements information, which indicates traffic distribution information, in the AF controller 33 (S31). For example, the TrafficInfluence API may be associated with the N6 Traffic Routing requirements. The TrafficInfluence API is an API used to specify the traffic to be offloaded.

[0049] Here, we will explain the TrafficInfluence API using Figure 8. The TrafficInfluence API includes the trafficRoutes attribute. Furthermore, the trafficRoutes attribute specifies multiple RouteToLocation attributes. The RouteToLocation attribute indicates the destination of traffic. For example, the dnai attribute may specify EHE31 or EHE32 as the destination, and the routeInfo attribute may specify the IP address of the AF running on EHE31 or EHE32. Each running AF has an IP address set. In Figure 8, EHE31 is shown as EHE#1 and EHE32 is shown as EHE#2. Furthermore, the trafficRoutes attribute specifies traffic distribution information. Distribution information may be specified, for example, as the af_weight attribute for each RouteToLocation attribute. The af_weight attribute indicates the proportion of traffic received from the UE110 that the UPF80 forwards to its respective destination. This proportion may also be referred to as the weight value.

[0050] Figure 8 shows that the first RouteToLocation attribute specifies the current edge computing environment, and the second RouteToLocation attribute specifies the new edge computing environment. The af_weight attribute is set so that 90% of all traffic processed by resource group #g_1 is forwarded to the AF with the IPv4 address 192.168.10.1, which is deployed in the current edge computing environment, EHE31. Furthermore, the af_weight attribute is set so that 10% of all traffic processed by resource group #g_1 is forwarded to the AF with the IPv4 address 192.168.20.1, which is deployed in the new edge computing environment, EHE32. In other words, the af_weight attribute is set so that 10% of the traffic that was processed by the AF deployed in EHE31 is offloaded to the AF deployed in EHE32.

[0051] Returning to Figure 7, the application service operator creates AF Request information in the AF controller 33 that shows traffic allocation information used in the Application influence on traffic routing service (S32). Note that the AF Request information may also include N6 Traffic Routing requirements information that shows traffic allocation information. Figure 9 shows that the AF Request information includes the trafficRoutes attribute. The AF controller 33 invokes the Nnef_TrafficInfluence_Create service operation to create the AF Request information. The AF controller 33 also invokes the Nnef_TrafficInfluence_Create service operation to request the NEF 40 to update the subscriber information (subscription resource) in the UDR 50. Updating the subscriber information may include, for example, generating an AF Request as subscriber information.

[0052] Returning to Figure 7, the AF controller 33 uses the Nnef_TrafficInfluence_Create service operation provided by the NEF 40 to send AF Request information indicating traffic allocation information to the NEF 40 (S33). In other words, the AF controller 33 uses the Nnef_TrafficInfluence_Create service operation provided by the NEF 40 to send a request message to the NEF 40 requesting the creation or registration of an AF Request. The Nnef_TrafficInfluence_Create service operation is used when newly created AF Request information is sent to the NEF 40. On the other hand, when updating AF Request information already registered in the UDR 50, the AF controller 33 uses the Nnef_TrafficInfluence_Update service operation to send AF Request information to the NEF 40.

[0053] Next, NEF40 uses the Nudr_DM_Create service operation provided by UDR50 to send AF Request information indicating traffic allocation information to UDR50 (S34). When NEF40 sends AF Request information to UDR50, the AF Request information is registered in UDR50. The registration of AF Request information in UDR50 can also be rephrased as the AF Request information being held or stored in UDR50. The Nudr_DM_Create service operation is used when newly created AF Request information is sent to UDR50. On the other hand, when updating AF Request information already registered in UDR50, NEF40 uses the Nudr_DM_Update service operation to send AF Request information to UDR50.

[0054] Next, UDR50 uses the Nudr_DM_Notify service operation provided by UDR50 to notify PCF60 that AF Request information indicating traffic allocation information has been registered or updated (S35). For UDR50 to notify PCF60 using the Nudr_DM_Notify service operation, it is assumed that PCF60 has previously registered to use the Nudr_DM_Notify service operation provided by UDR50.

[0055] Next, PCF60 uses the Npcf_SMPolicyControl_UpdateNotify service operation provided by PCF60 to notify SMF70 that the policy information has been updated, and also notifies SMF70 of the policy information showing the traffic distribution information (S36). PCF60 determines whether the policy for the existing PDU session is affected by the AF Request information showing the notified traffic distribution information. If PCF60 determines that it is affected, it may notify SMF70 that the policy information has been updated, and also notify SMF70 of the policy information showing the traffic distribution information. The policy information may be, for example, traffic routing information for the PDU session. For example, PCF60 may determine that the policy for the existing PDU session is affected if the AF Request information includes multiple routing information (route info attribute) including offload destinations. The policy information is related to the PDU session managed by SMF70 and is defined as AF influenced Traffic Steering Enforcement Control information. When PCF60 notifies SMF70 of policy information, SMF70 performs processing using the Npcf_SMPolicyControl_Create service operation provided by PCF60 beforehand. Specifically, SMF70 associates SMF70 with the policy information related to the PDU session by providing or notifying PCF60 of the relevant information of the PDU session generated by SMF70.

[0056] The Npcf_SMPolicyControl_UpdateNotify service operation includes the SmPolicyDecision attribute contained in the SmPolicyNotification information. Furthermore, the SmPolicyDecision attribute contains the trafficContDescs attribute, which in turn contains the TrafficControlData attribute. The TrafficControlData attribute then contains the routeToLocs attribute, which in turn contains the RouteToLocation attribute, indicating traffic distribution information. The RouteToLocation attribute is the same as the one included in the AF Request information.

[0057] Here, we will explain the TrafficControlData attribute using Figure 10. The TrafficControlData attribute specifies multiple RouteToLocation attributes in the routeToLocs attribute. The RouteToLocation attribute has settings similar to the AF Request information that shows traffic distribution information generated in step S31. Specifically, the dnai attribute may specify EHE31 or EHE32 as the forwarding destination, and the routeInfo attribute may specify the IP address of the AF running on EHE31 or EHE32. Furthermore, the trafficRoutes attribute specifies traffic distribution information. The distribution information may be specified, for example, as the af_weight attribute in each RouteToLocation attribute. The af_weight attribute indicates the proportion of traffic received from UE110 that UPF80 forwards to its respective destination. The proportion may be called the weight value.

[0058] Figure 10 shows that the first RouteToLocation attribute specifies the current edge computing environment, and the second RouteToLocation attribute specifies the new edge computing environment. The af_weight attribute is set so that 90% of all traffic processed by resource group #g_1 is forwarded to the AF with the IPv4 address 192.168.10.1, which is deployed in the current edge computing environment, EHE31. Furthermore, the af_weight attribute is set so that 10% of all traffic processed by resource group #g_1 is forwarded to the AF with the IPv4 address 192.168.20.1, which is deployed in the new edge computing environment, EHE32. In other words, the af_weight attribute is set so that 10% of the traffic that was processed by the AF deployed in EHE31 is offloaded to the AF deployed in EHE32.

[0059] Returning to Figure 7, SMF70 updates the UPF80 configuration based on the updated policy information, which shows the traffic distribution information (S37). The UPF80 configuration may, for example, be a configuration related to the User Plane of a PDU session. Specifically, UPF80 is configured to forward 90% of all traffic handled by resource group #g_1 to the AF with the IPv4 address 192.168.10.1. Furthermore, UPF80 is configured to forward 10% of all traffic handled by resource group #g_1 to the AF with the IPv4 address 192.168.20.1.

[0060] Next, SMF70 uses the Nsmf_PDUSession_SMContextStatusNotify service operation to notify AMF90 that the information regarding the PDU session in UPF80 has been updated (S38). In making this notification, AMF90 associates itself with the generated SMContext information through the Nsmf_PDUSession_CreateSMContext service operation provided by SMF70.

[0061] Here, we will describe the case where traffic offloading in UPF80 is being performed successfully. In this case, the amount of traffic transferred to the new edge computing environment may be increased and the amount of traffic transferred to the current edge computing environment may be decreased by updating the policy information that indicates the traffic distribution information.

[0062] For example, a monitoring server that monitors whether AF is operating normally may determine whether traffic offloading to the new edge computing environment is being performed successfully. For example, AF controller 33 may be used as the monitoring server, or a different server device may be used. If a different server device is used as the monitoring server, AF controller 33 may receive the monitoring results from the monitoring server via the network. The monitoring server may determine that traffic offloading to the new edge computing environment is being performed successfully, for example, if the value indicating the processing load in the new edge computing environment does not exceed a predetermined threshold. Alternatively, the monitoring server may determine that traffic offloading to the new edge computing environment is being performed successfully if there is no interruption of application services in the new edge computing environment.

[0063] If the AF controller 33 determines that traffic offloading to the new edge computing environment is successfully performed, it may execute the process in step S31 in Figure 7 and update the af_weight attribute, which indicates traffic distribution information. Furthermore, the AF controller 33 executes the process in step S33 and sends AF Request information to the NEF 40 using the Nnef_TrafficInfluence_Update service operation. The AF Request information sent using the Nnef_TrafficInfluence_Update service operation includes the updated af_weight attribute. The updated af_weight attribute may be set to a value that increases the amount of traffic offloaded to the new edge computing environment, for example. Specifically, the value of af_weight associated with EHE#1 may be changed to a value smaller than the current value, and the value of af_weight associated with EHE#2 may be changed to a value larger than the current value.

[0064] As explained above, the AF controller 33 can offload traffic that was being transferred to the current edge computing environment in stages to the new edge computing environment by changing the value set in the af_weight attribute. As a result, it is possible to prevent the load from increasing due to a sudden increase in traffic in the new edge computing environment. Furthermore, if the traffic offloaded to the new edge computing environment is not processed properly, the amount of traffic affected can be minimized.

[0065] Furthermore, the af_weight attribute specified in step S31 may be set to the final traffic allocation information. For example, if 50% of the traffic from the current edge computing environment is to be offloaded to the new edge computing environment, the af_weight attribute set in the two routeInfo attributes may each be set to a value of 50. In this case, SMF70 may update the UPF80 settings in step S37 of Figure 7 to match the allocation information set in the af_weight attribute in stages. For example, SMF70 may initially be set to offload 10% of the traffic to the new edge computing environment. Then, if the monitoring server determines that the offload has been successfully executed, SMF70 may update the UPF80 settings to offload 20% of the traffic to the new edge computing environment. In this way, SMF70 may gradually update the UPF80 settings to match the value set in the af_weight attribute, increasing the amount of traffic to be offloaded.

[0066] Furthermore, the allocation information may include information that changes the traffic volume (or the percentage of traffic volume) at predetermined intervals. For example, the allocation information may initially set the allocation percentage to offload 15% of the traffic to the new edge computing environment. Furthermore, it may be specified that the allocation to the new edge computing environment be increased by 5% every two hours until the allocation ratio between the current edge computing environment and the new edge computing environment becomes equal.

[0067] (Embodiment 3) Next, resource groups will be explained using Figure 11. Figure 11 shows that multiple AFs providing a common application service constitute two resource groups. In Figure 11, multiple AFs are shown to constitute two resource groups, but multiple AFs may constitute three or more resource groups.

[0068] Figure 11 shows that n AFs, from AF#r_1 to AF#r_n (where n is an integer greater than or equal to 2), constitute resource group #g_1. Furthermore, m AFs, from AF#s_1 to AF#s_m (where m is an integer greater than or equal to 2), constitute resource group #g_2. Each AF constituting resource group #g_1 may be distributed across multiple EHEs. Similarly, each AF constituting resource group #g_2 may also be distributed across multiple EHEs.

[0069] Next, we will explain the flow of traffic off-road processing. Here, we will mainly explain modified examples of traffic off-road processing using Figure 7.

[0070] First, similar to step S31 in Figure 7, the application service operator creates N6 Traffic Routing requirements information in the AF controller 33, which shows the traffic distribution information to each resource group. Here, we will explain the TrafficInfluence API, including the targetGroups attribute, using Figure 12.

[0071] The TrafficInfluence API may contain multiple targetGroup attributes. Figure 12 shows that the TrafficInfluence API contains two targetGroup attributes. Each targetGroup attribute specifies a RouteToLocation attribute that indicates the destination of traffic. The dnai attribute included in the RouteToLocation attribute specifies either group#1 or group#2. group#1 corresponds to resource group#g_1, for example, and group#2 corresponds to resource group#g_2. Furthermore, the routeInfo attribute may specify, for example, the IP addresses of devices that distribute or allocate traffic to multiple AFs that make up resource group#g_1 and resource group#g_2. The devices that distribute or allocate traffic to multiple AFs may be load balancers, for example. Furthermore, the group_weight attribute is specified as information on how traffic is distributed to resource group#g_1 and resource group#g_2. The group_weight attribute indicates the proportion of traffic received from UE110 that UPF80 forwards to each destination specified in routeInfo.

[0072] Figure 12 shows that the current edge computing environment is specified in the first RouteToLocation attribute, and the new edge computing environment is specified in the second RouteToLocation attribute. The group_weight attribute is set so that 90% of all traffic processed by resource group #g_1 is forwarded to resource group #g_1, which is the current edge computing environment. Furthermore, the group_weight attribute is set so that 10% of all traffic processed by resource group #g_1 is forwarded to resource group #g_2, which is the new edge computing environment. In other words, the group_weight attribute is set so that 10% of the traffic processed by resource group #g_1 is offloaded to resource group #g_2.

[0073] Next, similar to step S32 in Figure 7, the application service operator creates AF Request information in the AF controller 33, which shows the traffic allocation information to each resource group used by the Application influence on traffic routing service. Here, the AF Request information includes targetGroups, as shown in Figure 13.

[0074] Next, the same process as in steps S33 to S35 in Figure 7 is executed.

[0075] Next, similar to step S36 in Figure 7, PCF60 uses the Npcf_SMPolicyControl_UpdateNotify service operation provided by PCF60 to notify SMF70 that the policy information has been updated, and also notifies it of the policy information showing the traffic allocation information to each resource group (S36).

[0076] The Npcf_SMPolicyControl_UpdateNotify service operation includes the SmPolicyDecision attribute contained in the SmPolicyNotification information. Furthermore, the SmPolicyDecision attribute contains the trafficContDescs attribute, which in turn contains the TrafficControlData attribute. And the TrafficControlData attribute, as shown in Figure 14, contains the targetGroups attribute contained in the AF Request information.

[0077] Next, similar to step S37 in Figure 7, SMF70 updates the UPF80 configuration based on the updated policy information, which shows the traffic distribution information to each resource group. Specifically, UPF80 is configured to forward 90% of all traffic handled by resource group #g_1 to the load balancer with the IPv4 address 192.168.10.1. Furthermore, UPF80 is configured to forward 10% of all traffic handled by resource group #g_1 to the load balancer with the IPv4 address 192.168.20.1.

[0078] Next, the same process as in step S38 in Figure 7 is executed.

[0079] Here, if traffic offloading in UPF80 is working correctly, the policy information may be updated to increase the amount of traffic offloaded to the new edge computing environment.

[0080] As explained above, the AF controller 33 can offload traffic that was being transferred to the current edge computing environment in stages to the new edge computing environment by changing the value set in the group_weight attribute. As a result, it is possible to prevent the load from increasing due to a sudden increase in traffic in the new edge computing environment. Furthermore, if the traffic offloaded to the new edge computing environment is not processed properly, the amount of traffic affected can be minimized.

[0081] Furthermore, the allocation information may include information that changes the traffic volume (or the percentage of traffic volume) at predetermined intervals. For example, the allocation information may initially set the allocation percentage to offload 15% of the traffic to the new edge computing environment. In addition, it may be specified that the allocation to the new edge computing environment be increased by 5% every hour thereafter until the allocation ratio between the current edge computing environment and the new edge computing environment becomes equal.

[0082] Figure 15 is a block diagram showing an example configuration of an application server 10 and a core network device 20 (hereinafter referred to as the application server 10, etc.). Referring to Figure 15, the application server 10, etc. includes a network interface 1201, a processor 1202, and memory 1203. The network interface 1201 may be used to communicate with network nodes. The network interface 1201 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series. IEEE stands for Institute of Electrical and Electronics Engineers.

[0083] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform processing such as that of the application server 10 as described using the flowchart in the above embodiment. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

[0084] Memory 1203 is composed of a combination of volatile and non-volatile memory. Memory 1203 may also include storage located away from the processor 1202. In this case, the processor 1202 may access memory 1203 via an I / O (Input / Output) interface, which is not shown.

[0085] In the example shown in Figure 15, memory 1203 is used to store a group of software modules. The processor 1202 can read these software modules from memory 1203 and execute them, thereby enabling the application server 10 and other processes described in the above embodiment.

[0086] As explained with reference to Figure 15, each of the processors in the application server 10, etc., in the above-described embodiment executes one or more programs that include a set of instructions for causing the computer to perform the algorithm described with reference to the diagram.

[0087] In the examples described above, the program includes a set of instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more of the functions described in the embodiments. The program may be stored on a non-temporary computer-readable medium or a physical storage medium. Examples, but not limited to, include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technologies, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disc storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices. The program may be transmitted over a temporary computer-readable medium or a communication medium. Examples, but not limited to, include temporary computer-readable medium or a communication medium that includes electrically, optically, acoustically or otherwise propagating signals.

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

[0089] Each drawing is merely illustrative to illustrate one or more embodiments. Each drawing may be associated with one or more other embodiments rather than with only one specific embodiment. As those skilled in the art will understand, 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, for example, to create embodiments not explicitly shown or described. Not all features or steps shown in any one drawing to illustrate an exemplary embodiment are necessarily required, and some features or steps may be omitted. The order of steps shown in any of the drawings may be changed as appropriate.

[0090] Some or all of the above embodiments may also be described as follows, but are not limited to the following:

[0091] (Note 1) A core network device that constitutes a mobile network, A receiving unit receives traffic allocation information for a first computing resource and a second computing resource included in the plurality of computing resources from an application server that manages a plurality of computing resources that provide application services to a communication terminal via the aforementioned mobile network. A core network device comprising: a transmission unit that distributes and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the distribution information. (Note 2) The receiving unit is The core network device described in Appendix 1, which receives a message including first allocation information relating first address information indicating the first computing resource and information regarding a first traffic amount to be allocated to the first computing resource, and second allocation information relating second address information indicating the second computing resource and information regarding a second traffic amount to be allocated to the second computing resource. (Note 3) The receiving unit is a core network device as described in Appendix 2, which receives the message via one or more other core network devices. (Note 4) The receiving unit is The core network device according to Appendix 2 or 3, which, after receiving the aforementioned message, receives a message containing the modified first traffic amount and the second traffic amount. (Note 5) The receiving unit is A core network device according to any one of the appendices 2 to 4, which receives a message in which an attribute indicating the first allocation information is associated with an attribute indicating the first address information and an attribute indicating information regarding the first traffic volume, and an attribute indicating the second allocation information is associated with an attribute indicating the second address information and an attribute indicating information regarding the second traffic volume. (Note 6) The information relating to the first traffic volume and the second traffic volume is indicated using weight values, as described in any one of the appendices 2 to 5, for the core network device. (Note 7) The receiving unit is The core network device described in Appendix 1, which receives traffic allocation information in a first computing resource group including at least the first computing resource and a second computing resource group including at least the second computing resource. (Note 8) The receiving unit is The core network device described in Appendix 7, which receives a message including a message relating a first group information indicating the first computing resource group to a first traffic amount to be allocated to the first computing resource, and a fourth allocation information relating a second group information indicating the second computing resource group to a second traffic amount to be allocated to the second computing resource. (Note 9) The receiving unit is The core network device described in Appendix 8, which, after receiving the aforementioned message, receives a message containing the modified first traffic amount and the second traffic amount. (Note 10) The receiving unit is The core network device according to Appendix 8 or 9, which transmits the message in which an attribute indicating the third allocation information is associated with an attribute indicating the first group information and an attribute indicating information regarding the first traffic amount, and an attribute indicating the fourth allocation information is associated with an attribute indicating the second group information and an attribute indicating information regarding the second traffic amount. (Note 11) The information relating to the first traffic volume and the second traffic volume is indicated using weight values, as described in any one of the appendices 8 to 10, for the core network device. (Note 12) A management unit that manages a first computing resource and a second computing resource that provide application services to communication terminals via a mobile network, An application server comprising: a communication unit that transmits traffic allocation information for the first computing resource and the second computing resource to the core network device constituting the mobile network. (Note 13) The aforementioned communications unit is An application server as described in Appendix 12, which sends a message including first allocation information relating first address information indicating the first computing resource and information regarding a first traffic amount to be allocated to the first computing resource, and second allocation information relating second address information indicating the second computing resource and information regarding a second traffic amount to be allocated to the second computing resource. (Note 14) The aforementioned communications unit is The application server described in Appendix 13, which, after sending the aforementioned message, sends a message containing the modified first traffic volume and the second traffic volume. (Note 15) The aforementioned communications unit is An application server according to Appendix 13 or 14, which transmits a message in which an attribute indicating the first allocation information is associated with an attribute indicating the first address information and an attribute indicating information regarding the first traffic volume, and an attribute indicating the second allocation information is associated with an attribute indicating the second address information and an attribute indicating information regarding the second traffic volume. (Note 16) The application server described in any one of appendices 13 to 15, wherein the information regarding the first traffic volume and the second traffic volume is indicated using weight values. (Note 17) The aforementioned management department, A first computing resource group including at least the first computing resource and a second computing resource group including at least the second computing resource are managed. The aforementioned communications unit is The application server described in Appendix 12 sends a message to the core network device specifying traffic allocation information for the first computing resource group and the second computing resource group. (Note 18) The aforementioned communications unit is An application server as described in Appendix 17, which transmits a message including a first group information indicating the first computing resource group and a third allocation information relating to a first traffic amount to be allocated to the first computing resource, and a fourth allocation information relating to a second group information indicating the second computing resource group and a second traffic amount to be allocated to the second computing resource. (Note 19) The aforementioned communications unit is The application server described in Appendix 18, which, after sending the aforementioned message, sends a message containing the modified first traffic volume and the second traffic volume. (Note 20) The aforementioned communications unit is The application server described in Appendix 18 or 19 transmits the message, wherein the attribute indicating the third allocation information is associated with the attribute indicating the first group information and the attribute indicating the first traffic amount, and the attribute indicating the fourth allocation information is associated with the attribute indicating the second group information and the attribute indicating the second traffic amount. (Note 21) The application server described in any one of the appendices 18 to 20, wherein the information relating to the first traffic volume and the second traffic volume is indicated using weight values. (Note 22) An application server manages a first computing resource and a second computing resource that provide application services to communication terminals via a mobile network, and transmits traffic allocation information for the first computing resource and the second computing resource to the core network device constituting the mobile network. A communication system comprising: a core network device that receives traffic allocation information for the first computing resource and the second computing resource included in the plurality of computing resources from an application server that manages a plurality of computing resources that provide application services to a communication terminal via a mobile network, and distributes data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information. (Note 23) The aforementioned application server The communication system described in Appendix 22, which transmits a message including first allocation information relating first address information indicating the first computing resource and information regarding a first traffic amount to be allocated to the first computing resource, and second allocation information relating second address information indicating the second computing resource and information regarding a second traffic amount to be allocated to the second computing resource. (Note 24) An application server that manages multiple computing resources that provide application services to communication terminals via a mobile network receives traffic allocation information for a first computing resource and a second computing resource included in the multiple computing resources. A communication method performed in a core network device, which distributes and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the distribution information. (Note 25) When receiving the aforementioned allocation information, The communication method described in Appendix 24, which receives a message including first allocation information relating first address information indicating the first computing resource and information regarding a first traffic amount to be allocated to the first computing resource, and second allocation information relating second address information indicating the second computing resource and information regarding a second traffic amount to be allocated to the second computing resource. (Note 26) When receiving the aforementioned message, The communication method described in Appendix 25, which receives the message via one or more other core network devices. (Note 27) The communication method according to Appendix 25 or 26, which, after receiving the aforementioned message, receives a message containing the modified first traffic amount and the second traffic amount. (Note 28) When receiving the aforementioned message, A communication method according to any one of the appendices 25 to 27, wherein a message is received in which an attribute indicating the first allocation information is associated with an attribute indicating the first address information and an attribute indicating information regarding the first traffic amount, and an attribute indicating the second allocation information is associated with an attribute indicating the second address information and an attribute indicating information regarding the second traffic amount. (Note 29) The communication method described in any one of appendices 25 to 28, wherein the information relating to the first traffic amount and the second traffic amount is indicated using weight values. (Note 30) When receiving the aforementioned allocation information, The communication method described in Appendix 24, which receives traffic allocation information in a first computing resource group including at least the first computing resource and a second computing resource group including at least the second computing resource. (Note 31) When receiving the aforementioned allocation information, The communication method described in Appendix 30, which receives a message including a message relating a first group information indicating the first computing resource group to a first traffic amount to be allocated to the first computing resource, and a fourth allocation information relating a second group information indicating the second computing resource group to a second traffic amount to be allocated to the second computing resource. (Note 32) When receiving the aforementioned message, The communication method according to Appendix 31, which, after receiving the aforementioned message, receives a message containing the modified first traffic amount and the second traffic amount. (Note 33) When receiving the aforementioned message, The communication method according to Appendix 31 or 32, wherein the message is transmitted in which an attribute indicating the third allocation information is associated with an attribute indicating the first group information and an attribute indicating information regarding the first traffic amount, and an attribute indicating the fourth allocation information is associated with an attribute indicating the second group information and an attribute indicating information regarding the second traffic amount. (Note 34) The communication method described in any one of appendices 31 to 33, wherein information regarding the first traffic amount and the second traffic amount is indicated using weight values. (Note 35) It manages a first computing resource and a second computing resource that provide application services to communication terminals via a mobile network, A communication method performed in an application server, which transmits traffic allocation information for the first computing resource and the second computing resource to the core network device constituting the mobile network. (Note 36) When transmitting the aforementioned allocation information, The communication method according to Appendix 35, which transmits a message including first allocation information relating first address information indicating the first computing resource and information relating to a first traffic amount to be allocated to the first computing resource, and second allocation information relating second address information indicating the second computing resource and information relating to a second traffic amount to be allocated to the second computing resource. (Note 37) The communication method according to Appendix 36, wherein after sending the aforementioned message, a message is sent containing information regarding the changed first traffic amount and the second traffic amount. (Note 38) When sending the aforementioned message, The communication method according to Appendix 36 or 37, wherein the message is transmitted in which an attribute indicating the first allocation information is associated with an attribute indicating the first address information and an attribute indicating information regarding the first traffic amount, and an attribute indicating the second allocation information is associated with an attribute indicating the second address information and an attribute indicating information regarding the second traffic amount. (Note 39) The communication method described in any one of appendices 36 to 38, wherein the information relating to the first traffic amount and the second traffic amount is indicated using weight values. (Note 40) A first computing resource group including at least the first computing resource and a second computing resource group including at least the second computing resource are managed. When transmitting the aforementioned allocation information, The communication method described in Appendix 35, which involves sending a message to the core network device specifying traffic allocation information in the first computing resource group and the second computing resource group. (Note 41) When sending the aforementioned message, The communication method according to Appendix 40, which transmits a message including a message relating a first group information indicating the first computing resource group to a first traffic amount to be allocated to the first computing resource, and a fourth allocation information relating a second group information indicating the second computing resource group to a second traffic amount to be allocated to the second computing resource. (Note 42) The communication method according to Appendix 41, wherein after sending the aforementioned message, a message is sent containing information regarding the modified first traffic amount and the second traffic amount. (Note 43) When sending the aforementioned message, The communication method according to Appendix 41 or 42, wherein the message is transmitted in which an attribute indicating the third allocation information is associated with an attribute indicating the first group information and an attribute indicating information regarding the first traffic amount, and an attribute indicating the fourth allocation information is associated with an attribute indicating the second group information and an attribute indicating information regarding the second traffic amount. (Note 44) The communication method described in any one of appendices 41 to 43, wherein information regarding the first traffic amount and the second traffic amount is indicated using weight values. (Note 45) It manages a first computing resource and a second computing resource that provide application services to communication terminals via a mobile network, A program that causes a computer to transmit traffic allocation information for the first computing resource and the second computing resource to the core network device constituting the mobile network. (Note 46) An application server that manages multiple computing resources that provide application services to communication terminals via a mobile network receives traffic allocation information for a first computing resource and a second computing resource included in the multiple computing resources. A program that causes a computer to distribute data received from the communication terminal to the first computing resource and the second computing resource according to the distribution information.

[0092] This application claims priority based on Japanese Patent Application No. 2022-127027, filed on 9 August 2022, and incorporates all of its disclosures herein. [Explanation of Symbols]

[0093] 10 Application Servers 11 Management Department 12 Communications Department 20 Core Network Devices 21 Receiving unit 22 Transmitter 30 DN 31 EHE 32 EHE 33 AF controller 34 Gateway 40 NEF 50 UDR 60 PCF 70 SMF 80 UPF 90 AMF 100 gNB 110 UE

Claims

1. A core network device that constitutes a mobile network, Receiving means for receiving traffic allocation information for a first computing resource and a second computing resource included in the plurality of computing resources from an application server that manages a plurality of computing resources that provide application services to a communication terminal via the mobile network, The system includes a transmission means that distributes and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the distribution information, The receiving means is A core network device that receives, via one or more other core network devices, a message including first allocation information relating first address information indicating the first computing resource to information regarding a first traffic amount to be allocated to the first computing resource, and second allocation information relating second address information indicating the second computing resource to information regarding a second traffic amount to be allocated to the second computing resource.

2. The receiving means is The core network device according to claim 1, which, after receiving the aforementioned message, receives a message including the modified first traffic amount and the second traffic amount.

3. The core network device according to claim 1, wherein information regarding the first traffic amount and the second traffic amount is indicated using weight values.

4. The receiving means is The core network device according to claim 1, which receives traffic allocation information in a first computing resource group including at least the first computing resource and a second computing resource group including at least the second computing resource.

5. The receiving means is The core network device according to claim 4, which receives a message including a message relating a first group information indicating the first computing resource group to a first traffic amount to be allocated to the first computing resource, and a fourth allocation information relating a second group information indicating the second computing resource group to a second traffic amount to be allocated to the second computing resource.

6. The receiving means is The core network device according to claim 5, which, after receiving the aforementioned message, receives a message including the modified first traffic amount and the second traffic amount.

7. The receiving means is The core network device according to claim 5 or 6, which receives a message in which an attribute indicating the third allocation information is associated with an attribute indicating the first group information and an attribute indicating information regarding the first traffic amount, and an attribute indicating the fourth allocation information is associated with an attribute indicating the second group information and an attribute indicating information regarding the second traffic amount.

8. A message is received via one or more other core network devices from an application server that manages multiple computing resources providing application services to communication terminals via a mobile network. The message includes first allocation information, which associates first address information indicating a first computing resource included in the multiple computing resources with information regarding a first traffic amount to be allocated to the first computing resource, and second allocation information, which associates second address information indicating a second computing resource with information regarding a second traffic amount to be allocated to the second computing resource. A communication method performed in a core network device, which distributes and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the first allocation information and the second allocation information.

Images