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

Core network device, application server, and communication method

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

[0002] Various application services are provided via mobile networks. Application service providers distribute computing resources using physical or virtual servers across multiple locations. Application providers deploy application servers on these computing resources to provide high-quality, highly reliable application services. For example, application servers may provide applications such as mail servers, video distribution servers, and web servers. To provide high-quality, highly reliable application services, providers may dynamically change the allocation of computing resources depending on factors such as the usage status of the computing resources.

[0003] The purpose of dynamically changing the allocation of computing resources is to balance acceptable costs with securing the necessary computing resources. Application service providers can secure computing resources by using cloud services. Cloud services include services that provide high-performance, high-cost computing resources or general-purpose, low-cost computing resources. Computing resources can also be secured at lower costs by signing long-term contracts for high-performance computing resources or by using unused surplus computing resources on a spot basis. Alternatively, reserved computing resources can be allocated to a limited group of users, while other users can be served by on-demand or spot computing resources. This can reduce the total cost of application services. In this way, application providers can secure the necessary computing resources when needed, taking into account acceptable costs, and release the secured computing resources when not needed. In this way, application providers aim to balance acceptable costs with securing computing resources through the operation of dynamically distributed computing resources.

[0004] Non-Patent Document 1 discloses a process for distributing or offloading traffic in a mobile network. Non-Patent Document 1 also discloses that an Application Function (AF) uses a Network Exposure Function (NEF) service to achieve traffic distribution. For example, the AF transmits an AF request including N6 Traffic Routing requirements as an information element to the NEF. The N6 Traffic Routing requirements are information specifying the traffic route at the N6 reference point specified by 3GPP (registered trademark).

[0005] Furthermore, Non-Patent Document 2 defines the TrafficInfluence API as an API (Application Programming Interface) related to N6 Traffic Routing requirements. The TrafficInfluence API defines that multiple RouteToLocation attributes can be specified in the trafficRoutes attribute. Since the RouteToLocation attribute indicates the traffic forwarding destination, specifying multiple RouteToLocation attributes allows distribution or offloading of traffic related to a certain application service.

[0006] 3GPP TS 23.501 V17.5.0 (2022-06)3GPP TS 29.522 V17.6.0 (2022-06)

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

[0008] In view of the above-mentioned problems, one of the objectives of the present disclosure is to provide a core network device, an application server, a communication system, and a communication method that can suppress degradation in the quality of application services when traffic is distributed across multiple computing resources.

[0009] A core network device according to a first aspect of the present disclosure is a core network device that constitutes a mobile network, and includes: 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 the plurality of computing resources and provides application services to a communication terminal via the mobile network; and a transmitting unit that allocates and transmits data received from the communication terminal to the first computing resource and the second computing resource in accordance with the allocation information.

[0010] An application server according to a second aspect of the present 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 that constitutes the mobile network.

[0011] A communication system according to a third aspect of the present 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 that constitutes 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 a plurality of computing resources that provide application services to a communication terminal via the mobile network from the application server that manages the plurality of computing resources, and allocates data received from the communication terminal to the first and second computing resources in accordance with the allocation information.

[0012] A communication method according to a fourth aspect of the present disclosure is executed 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 the plurality of computing resources and provides application services to a communication terminal via a mobile network, and allocates and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information.

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

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

[0015] First Embodiment An example of the configuration of an application server 10 will be described below with reference to Fig. 1. The application server 10 is executed by a computing resource. The computing resource may be a computer device that operates by a processor executing a program stored in a 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 that execute processes by a processor running a program stored in a memory, or may be hardware such as a circuit or a chip.

[0017] The management unit 11 manages first and second computing resources 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 by 3GPP (3rd Generation Partnership Project). The mobile network may be, for example, composed of an access network and a core network. The access network is mainly composed of access devices that communicate with communication terminals. The access devices may, for example, perform wireless communication with the communication terminals. The access network may be, for example, non-3GPP access using communication technologies such as Wi-Fi (Wireless Fidelity) (registered trademark). The core network is composed of core network devices. The core network device may, for example, be a device that performs mobility control, session control, authentication, etc. for communication terminals, or a device that manages subscriber information regarding users who use communication terminals, terminal information of the communication terminals, etc. The core network device may, for example, be a device that processes user data of communication terminals, or a device that routes user data related to communication terminals. The core network may be composed of multiple core network devices that perform different controls.

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

[0019] The computing resource may be a computer resource such as a processor and memory for running an application, and may be partitioned into physical computer devices. In this case, a computer device having a first computing resource is different from a computer device having a second computing resource. Alternatively, the computing resource may be each virtual machine included in multiple virtual machines that operate independently of each other on one or more computer devices. A virtual machine may be referred to as a virtual server, a virtual instance, or simply an instance. Alternatively, the computing resource may be each virtual machine included in multiple virtual machines that are run on a group of computer devices in which multiple computer devices operate in cooperation. Alternatively, the computing resource may be two or more virtual machines. Alternatively, the computing resource may be a container running on a container engine.

[0020] Managing computing resources may mean starting or stopping a computing resource that is a virtual machine, or may mean determining the function or role of a computing resource, or may mean determining the computer resources to be used by each computing resource.

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

[0022] The computing resource transmits and receives data to and from the communication terminal and provides application services. Here, data transmitted from the communication terminal to the computing resource is referred to as uplink data, and data transmitted from the computing resource to the communication terminal is referred to as downlink data. The traffic allocation information indicates, for example, the proportion of the amount of uplink data directed to the computing resource. The traffic allocation information may also be, for example, the proportion of the number of PDU (Protocol Data Unit) sessions directed to the computing resource. The traffic allocation information may also be, for example, the proportion of bps directed to the computing resource. Note that the traffic allocation information is not limited to the above examples.

[0023] The allocation information may indicate, for example, the traffic volume processed by each of the first computing resource and the second computing resource. Alternatively, the allocation information may indicate the ratio between the traffic volume processed by the first computing resource and the traffic volume processed by the second computing resource. Note that the traffic volume or the ratio of the traffic volume in the allocation information may be specified according to time (time of day, unit time, predetermined period, etc.). Furthermore, the traffic volume or the ratio of the traffic volume 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 traffic volume that is changed in stages.

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

[0025] Next, a configuration example of the core network device 20 will be described with reference to Fig. 2. The core network device 20 may be a computer device that operates by a processor executing a program stored in a 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 that perform processing by a processor executing a program stored in a memory, or may be hardware such as a circuit or a chip.

[0027] The receiving unit 21 receives traffic allocation information for a first computing resource and a second computing resource included in the plurality of computing resources from the application server 10. The receiving unit 21 may receive a message indicating the allocation information. The receiving unit 21 may 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 a mobile network.

[0028] The transmitter 22 allocates the data received from the communication terminal to the first computing resource and the second computing resource in accordance with the allocation information. "Allocating" can be rephrased as "transmitting." The transmitter 22, for example, specifies identification information of the first computing resource and identification information of the second computing resource to transmit the data received from the communication terminal.

[0029] Note that the core network device 20 may also include a control unit (not shown in Fig. 2). In this case, the control unit controls the transmitting unit 22 to allocate data received from the communication terminal to the first computing resource and the second computing resource based on the allocation information. The transmitting unit 22 transmits the amount of data allocated to each of the first and second computing resources to each of the first and second computing resources based on the control from the control unit.

[0030] Next, the flow of communication processing executed in the application server 10 will be explained using Fig. 3. First, 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 (S11). Next, the communication unit 12 transmits traffic allocation information for the first computing resource and the second computing resource to a core network device that constitutes the mobile network (S12).

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

[0032] As described above, the application server 10 specifies the amount of traffic to be processed by each computing resource. For example, when distributing or offloading traffic from a first computing resource to a second computing resource, the amount of traffic to be processed by the second computing resource may be set to be small. As a result, even if the second computing resource cannot process a large amount of traffic during startup or warm-up, the impact of degradation in the quality of the application service can be suppressed.

[0033] (Embodiment 2) Next, an example configuration of a communication system will be described with reference to Figure 5. The communication system in Figure 5 mainly illustrates the configuration of a communication system specified in 3GPP. The communication system in Figure 5 includes a UE 110. Furthermore, the communication system includes a gNB 100 that constitutes an access network. Furthermore, the communication system includes a Network Exposure Function (NEF) node 40, a Unified Data Repository (UDR) node 50, a Policy Control Function (PCF) node 60, a Session Management Function (SMF) node 70, a User Plane Function (UPF) node 80, and an Access and Mobility management Function (AMF) node 90 that constitute a core network. In the following description, the respective nodes will be referred to as NEF 40, UDR 50, PCF 60, SMF 70, UPF 80, and AMF 90. Furthermore, the nodes may correspond to entities (devices) or functions. Furthermore, the communication system includes an EHE (Edge Hosting Environment) 31 , an EHE 32 , an AF controller 33 , and a Gateway 34 that configure a DN (Data Network) 30 .

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

[0035] The AF controller 33 is a network function that executes application services hosted by a physical server or a virtual server and provides an application influence on traffic routing service to an application function (AF) operator. In other words, the AF controller 33 executes the application influence on traffic routing service using an application launched on the physical server or the virtual server. The AF may be an application server launched on the physical server or the virtual server. The application influence on traffic routing service determines the traffic route for a PDU session based on a request from the AF. In other words, a request from the AF influences the traffic route for a PDU session. More specifically, the application influence on traffic routing service may be a service used by the AF to specify traffic to be offloaded to the core network. Note that the node collectively referring to the AF controller 33 and the AF may be the AF in the 3GPP standard.

[0036] Each of the EHE 31 and the EHE 32 is an edge computing environment that constitutes the DN 30. In the following description, the EHE 31 is described as a current edge computing environment that currently provides application services, and the EHE 32 is described as a new edge computing environment to which traffic is offloaded. Each of the EHE 31 and the EHE 32 may be a data center in which multiple computer devices are installed. Furthermore, the EHE 31 may be distributed to a different building or a different region from the EHE 32.

[0037] The Gateway 34 is a device that interconnects with the UPF 80 within the DN 30, and may be, for example, a router.

[0038] The NEF 40 exposes services provided by a Network Function, for example, as defined in 3GPP TS23.501 V17.5.0 (2022-06), to an external edge computing environment. The NEF 40 also transmits and receives structured data between the edge computing environment or other core network devices.

[0039] The UDR 50 provides a service for saving structured data or reading structured data to the NEF 40 or the PCF 60. The UDR 50 also acquires and saves policies from the PCF 60.

[0040] The PCF 60 generates policy rules and provides them to a C-Plane function that processes C (Control)-Plane data.

[0041] SMF70 manages PDU sessions in the 5G system.

[0042] The UPF 80 serves as an anchor point in the 5G system and interconnects PDU sessions with an external edge computing environment. That is, the UPF 80 may be connected to the Gateway 34 in the DN 30 via an L2 network. The L2 network may be referred to as, for example, an N6-LAN (Local Area Network). The UPF 80 may also be, for example, a device that processes user data of a communication terminal and distributes the path of user data related to the communication terminal.

[0043] The AMF 90 performs access management or mobility management of the UE 110 .

[0044] The gNB 100 is a base station that supports a communication method defined as 5G. The UE 110 is defined in 3GPP as a general term for a communication terminal.

[0045] UE110 performs wireless communication with gNB100.

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

[0047] The AFs, which are the respective computing resources constituting resource group #g_1, may be distributed across multiple EHEs. For example, AF#r_1 to AF#r_2 may be started in EHE 31, and AF#r_3 to AF#r_n may be started in EHE 32. The AF controller 33 may control the start-up of AF#r_1 to AF#r_n. For example, the AF controller 33 may determine which AFs from AF#r_1 to AF#r_n included in resource group #g_1 are to be started in EHE 31 and which are to be started in EHE 32. Furthermore, the AF controller 33 may determine which AFs from the AFs started in EHE 31 or EHE 32 are to be stopped.

[0048] Next, the flow of traffic offload processing will be explained using Fig. 7. First, the operator of the application service creates N6 Traffic Routing requirements information indicating traffic allocation information in the AF controller 33 (S31). For example, the Traffic Influence API may be associated with the N6 Traffic Routing requirements. The Traffic Influence API is an API used to specify the traffic to be offloaded.

[0049] Here, the TrafficInfluence API will be described with reference to FIG. 8 . The TrafficInfluence API includes a trafficRoutes attribute. Furthermore, the trafficRoutes attribute specifies multiple RouteToLocation attributes. The RouteToLocation attribute indicates a traffic forwarding destination. For example, EHE 31 or EHE 32 may be specified as the forwarding destination in the dnai attribute, and the IP address of an AF activated in EHE 31 or EHE 32 may be specified in the routeInfo attribute. An IP address is set for each activated AF. In FIG. 8 , EHE 31 is indicated as EHE#1, and EHE 32 is indicated as EHE#2. Furthermore, traffic allocation information is specified in the trafficRoutes attribute. The allocation information may be specified, for example, as an af_weight attribute in each RouteToLocation attribute. The af_weight attribute indicates the proportion of traffic received from the UE 110 that the UPF 80 forwards to each destination. The proportion may also be referred to as a weight value.

[0050] In Figure 8, 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 specified so that 90% of all traffic processed by resource group #g_1 is forwarded to the AF with an IPv4 address of 192.168.10.1 deployed in EHE31, the current edge computing environment. Furthermore, the af_weight attribute is specified so that 10% of all traffic processed by resource group #g_1 is forwarded to the AF with an IPv4 address of 192.168.20.1 deployed in EHE32, the new edge computing environment. In other words, the af_weight attribute is specified so that 10% of the traffic processed by the AF deployed in EHE31 is offloaded to the AF deployed in EHE32.

[0051] Returning to FIG. 7 , the operator of the application service creates AF Request information indicating traffic allocation information used in the Application Influence on Traffic Routing service in the AF controller 33 (S32). The AF Request information may include N6 Traffic Routing requirements information indicating traffic allocation information. FIG. 9 shows that the AF Request information includes a 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 subscription resource in the UDR 50. Updating the subscription resource may include, for example, generating an AF Request as the subscription resource.

[0052] 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, the NEF 40 uses the Nudr_DM_Create service operation provided by the UDR 50 to send AF Request information indicating traffic allocation information to the UDR 50 (S34). Note that when the NEF 40 sends the AF Request information to the UDR 50, the AF Request information is registered in the UDR 50. Registering the AF Request information in the UDR 50 can also be said to mean that the AF Request information is held or stored in the UDR 50. The Nudr_DM_Create service operation is used when newly created AF Request information is sent to the UDR 50. On the other hand, when updating AF Request information already registered in the UDR 50, the NEF 40 uses the Nudr_DM_Update service operation to send the AF Request information to the UDR 50.

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

[0055] Next, the PCF 60 notifies the SMF 70 that the policy information has been updated and that the policy information indicates traffic allocation information, using the Npcf_SMPolicyControl_UpdateNotify service operation provided by the PCF 60 (S36). The PCF 60 determines whether the policy for the existing PDU session is affected by the AF Request information indicating the notified traffic allocation information. If the PCR 60 determines that the policy is affected, it may notify the SMF 70 that the policy information has been updated and that the policy information indicates the traffic allocation information. The policy information may be, for example, route information for the traffic related to the PDU session. For example, if the AF Request information includes multiple route information (route info attribute) including an offload destination, the PCF 60 may determine that the policy for the existing PDU session is affected. The policy information is related to the PDU session managed by the SMF 70 and is defined as AF-influenced Traffic Steering Enforcement Control information. When the PCF 60 notifies the SMF 70 of policy information, the SMF 70 first executes processing using the Npcf_SMPolicyControl_Create service operation provided by the PCF 60. Specifically, the SMF 70 associates the SMF 70 with the policy information related to the PDU session in the PCF 60 by providing or notifying the PCF 60 of information related to the PDU session created by the SMF 70.

[0056] The Npcf_SMPolicyControl_UpdateNotify service operation includes the SmPolicyDecision attribute included in the SmPolicyNotification information. The SmPolicyDecision attribute further includes a trafficContDescs attribute, which further includes a TrafficControlData attribute. The TrafficControlData attribute then includes a routeToLocs attribute, which includes a RouteToLocation attribute that indicates traffic allocation information. The RouteToLocation attribute indicates the same attribute as that included in the AF Request information.

[0057] Here, the TrafficControlData attribute will be described with reference to FIG. 10 . The TrafficControlData attribute specifies multiple RouteToLocation attributes in the routeToLocs attribute. The RouteToLocation attribute has the same settings as the AF Request information generated in step S31, which indicates traffic allocation information. Specifically, the dnai attribute may specify EHE 31 or EHE 32 as the forwarding destination, and the routeInfo attribute may specify the IP address of the AF activated in EHE 31 or EHE 32. Furthermore, the trafficRoutes attribute specifies traffic allocation information. The allocation information may be specified as an af_weight attribute in each RouteToLocation attribute, for example. The af_weight attribute indicates the proportion of traffic received from UE 110 that the UPF 80 forwards to each destination. The proportion may be referred to as a weight value.

[0058] In Figure 10, 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 specified so that 90% of all traffic processed by resource group #g_1 is forwarded to the AF with an IPv4 address of 192.168.10.1 deployed in EHE31, the current edge computing environment. Furthermore, the af_weight attribute is specified so that 10% of all traffic processed by resource group #g_1 is forwarded to the AF with an IPv4 address of 192.168.20.1 deployed in EHE32, the new edge computing environment. In other words, the af_weight attribute is specified so that 10% of the traffic processed by the AF deployed in EHE31 is offloaded to the AF deployed in EHE32.

[0059] Returning to FIG. 7 , the SMF 70 updates the configuration of the UPF 80 based on the updated policy information indicating traffic allocation information (S37). The configuration of the UPF 80 may be, for example, a configuration related to the User Plane of the PDU session. Specifically, the UPF 80 is configured to forward 90% of all traffic processed by the resource group #g_1 to the AF having the IPv4 address 192.168.10.1. Furthermore, the UPF 80 is configured to forward 10% of all traffic processed by the resource group #g_1 to the AF having the IPv4 address 192.168.20.1.

[0060] Next, the SMF 70 uses the Nsmf_PDUSession_SMContextStatusNotify service operation to notify the AMF 90 that information related to the PDU session in the UPF 80 has been updated (S38). To make this notification, the AMF 90 associates the AMF 90 with the generated SMContext information through the Nsmf_PDUSession_CreateSMContext service operation provided by the SMF 70.

[0061] Here, we will explain the case where traffic offloading is performed normally in the UPF 80. In this case, by updating policy information indicating traffic allocation information, 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.

[0062] For example, a monitoring server that monitors whether the AF is operating normally may determine whether traffic offloading to the new edge computing environment is being performed normally. For example, the AF controller 33 may be used as the monitoring server, or a server device different from the AF controller 33 may be used. When a server device different from the AF controller 33 is used as the monitoring server, the AF controller 33 may receive the monitoring results from the monitoring server via a network. The monitoring server may determine that traffic offloading to the new edge computing environment is being performed normally, for example, when a 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 normally when no interruption of application services occurs in the new edge computing environment.

[0063] If the AF controller 33 determines that the offloading of traffic to the new edge computing environment is being performed normally, the AF controller 33 may perform the process in step S31 in FIG. 7 to update the af_weight attribute, which indicates traffic distribution information. Furthermore, the AF controller 33 performs the process in step S33 to send 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, for example, so as to increase the traffic offloaded to the new edge computing environment. Specifically, the af_weight value associated with EHE#1 may be changed to a value smaller than the current value, and the af_weight value associated with EHE#2 may be changed to a value larger than the current value.

[0064] As described above, the AF controller 33 can gradually offload traffic that has been transferred to the current edge computing environment to the new edge computing environment by changing the value set in the af_weight attribute. As a result, it is possible to prevent an increase in load due to a sudden increase in traffic in the new edge computing environment. Furthermore, if traffic offloaded to the new edge computing environment is not processed normally, it is possible to minimize the amount of traffic that is affected.

[0065] Furthermore, the af_weight attribute specified in step S31 may be set to final traffic allocation information. For example, if 50% of the traffic in the current edge computing environment is ultimately offloaded to a new edge computing environment, the af_weight attributes set in the two routeInfo attributes may each be set to a value of 50. In this case, in step S37 of FIG. 7 , the SMF 70 may update the setting of the UPF 80 so that the allocation information set in the af_weight attribute gradually becomes the allocation information set in the af_weight attribute. For example, the SMF 70 may initially set the setting to offload 10% of the traffic to the new edge computing environment. Thereafter, when the monitoring server determines that the offloading is being performed normally, the SMF 70 may update the setting of the UPF 80 so that 20% of the traffic is offloaded to the new edge computing environment. In this way, the SMF 70 may gradually update the setting of the UPF 80 so that the value set in the af_weight attribute becomes the value set in the af_weight attribute, thereby increasing the amount of traffic to be offloaded.

[0066] The allocation information may also include information for changing the traffic volume (or traffic volume ratio) at predetermined time intervals. For example, the allocation information may specify that 15% of traffic is to be offloaded to the new edge computing environment as the initial allocation volume ratio. Furthermore, the allocation information may specify that the allocation volume to the new edge computing environment is to be increased by 5% every two hours until the allocation volume ratios between the current edge computing environment and the new edge computing environment become equal.

[0067] (Embodiment 3) Next, a resource group will be described with reference to Fig. 11. Fig. 11 shows that a plurality of AFs providing a common application service constitute two resource groups. Although Fig. 11 shows that a plurality of AFs constitute two resource groups, a plurality of AFs may also constitute three or more resource groups.

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

[0069] Next, the flow of traffic offload processing will be explained, mainly focusing on a modified example of traffic offload processing, with reference to FIG.

[0070] First, similar to step S31 in Fig. 7, the operator of the application service creates N6 Traffic Routing requirements information indicating traffic allocation information for each resource group in the AF controller 33. Here, the TrafficInfluence API including the targetGroups attribute will be described with reference to Fig. 12.

[0071] The TrafficInfluence API may include multiple targetGroup attributes. FIG. 12 shows that the TrafficInfluence API includes two targetGroup attributes. Each targetGroup attribute specifies a RouteToLocation attribute indicating the traffic forwarding destination. The dnai attribute included in the RouteToLocation attribute specifies group #1 or group #2. Group #1 corresponds to, for example, resource group #g_1, and group #2 corresponds to resource group #g_2. Furthermore, the routeInfo attribute may specify, for example, the IP address of a device that distributes or allocates traffic to multiple AFs that make up resource group #g_1 and resource group #g_2. The device that distributes or allocates traffic to multiple AFs may be, for example, a load balancer. Furthermore, a group_weight attribute is specified as traffic allocation information for resource group #g_1 and resource group #g_2. The group_weight attribute indicates the proportion of traffic received from the UE 110 that the UPF 80 forwards to each destination specified in the routeInfo.

[0072] In Figure 12, the first RouteToLocation attribute specifies the current edge computing environment, and the second RouteToLocation attribute specifies the new edge computing environment. The group_weight attribute is specified so that 90% of all traffic previously 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 specified so that 10% of all traffic previously 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 specified so that 10% of the traffic previously processed by resource group #g_1 is offloaded to resource group #g_2.

[0073] Next, similar to step S32 in Fig. 7, the operator of the application service creates AF Request information indicating traffic allocation information for each resource group, which is used in the Application Influence on Traffic Routing service, in the AF controller 33. Here, the AF Request information includes targetGroups, as shown in Fig. 13.

[0074] Next, the same processes as steps S33 to S35 in FIG. 7 are executed.

[0075] Next, similarly to step S36 in FIG. 7, the PCF 60 uses the Npcf_SMPolicyControl_UpdateNotify service operation provided by the PCF 60 to notify the SMF 70 that the policy information has been updated, and further notifies the SMF 70 of the policy information indicating traffic allocation information for each resource group (S36).

[0076] The Npcf_SMPolicyControl_UpdateNotify service operation includes an SmPolicyDecision attribute included in the SmPolicyNotification information. The SmPolicyDecision attribute further includes a trafficContDescs attribute, which further includes a TrafficControlData attribute. The TrafficControlData attribute then includes a targetGroups attribute included in the AF Request information, as shown in FIG. 14.

[0077] 7, the SMF 70 updates the settings of the UPF 80 based on the updated policy information indicating traffic allocation information for each resource group. Specifically, the UPF 80 is configured to forward 90% of all traffic processed by the resource group #g_1 to the load balancer having the IPv4 address 192.168.10.1. Furthermore, the UPF 80 is configured to forward 10% of all traffic processed by the resource group #g_1 to the load balancer having the IPv4 address 192.168.20.1.

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

[0079] Here, if the offloading of traffic in the UPF 80 is being performed normally, the policy information may be updated to increase the amount of traffic offloaded to the new edge computing environment.

[0080] As described above, the AF controller 33 can gradually offload traffic that has been transferred to the current edge computing environment to the new edge computing environment by changing the value set in the group_weight attribute. As a result, it is possible to prevent an increase in load due to a sudden increase in traffic in the new edge computing environment. Furthermore, if traffic offloaded to the new edge computing environment is not processed normally, it is possible to minimize the amount of traffic that is affected.

[0081] The allocation information may also include information for changing the traffic volume (or traffic volume ratio) at predetermined time intervals. For example, the allocation information may specify that 15% of traffic is to be offloaded to the new edge computing environment as the initial allocation volume ratio. Furthermore, the allocation information may specify that the allocation volume to the new edge computing environment is to be increased by 5% every hour thereafter until the ratio of the allocation volumes between the current edge computing environment and the new edge computing environment becomes equal.

[0082] FIG. 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 FIG. 15, the application server 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.

[0083] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform the processing of the application server 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.

[0084] 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).

[0085] 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 application server 10 and the like described in the above-described embodiment.

[0086] As explained using Figure 15, each of the processors possessed by the application server 10, etc. in the above-mentioned embodiments executes one or more programs including a group of instructions for causing a computer to perform the algorithm explained using the drawings.

[0087] 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.

[0088] 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.

[0089] 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.

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

[0091] (Supplementary Note 1) A core network device constituting a mobile network, comprising: a receiver that receives, from an application server that manages a plurality of computing resources that provide application services to a communication terminal via the mobile network, traffic allocation information for a first computing resource and a second computing resource included in the plurality of computing resources; and a transmitter that allocates and transmits data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information. (Supplementary Note 2) The core network device according to Supplementary Note 1, wherein the receiver receives a message including first allocation information that associates first address information indicating the first computing resource with information on a first traffic volume to be allocated to the first computing resource, and second allocation information that associates second address information indicating the second computing resource with information on a second traffic volume to be allocated to the second computing resource. (Supplementary Note 3) The core network device according to Supplementary Note 2, wherein the receiver receives the message via one or more other core network devices. (Supplementary Note 4) The core network device according to Supplementary Note 2 or 3, wherein the receiving unit receives a message including the changed first traffic volume and the second traffic volume after receiving the message. (Supplementary Note 5) The core network device according to any one of Supplementary Notes 2 to 4, wherein the receiving unit receives the 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 about the first traffic volume, and an attribute indicating the second address information and an attribute indicating information about the second traffic volume are associated with an attribute indicating the second allocation information. (Supplementary Note 6) The core network device according to any one of Supplementary Notes 2 to 5, wherein the information about the first traffic volume and the second traffic volume is indicated using a weight value.(Supplementary Note 7) The core network device according to Supplementary Note 1, wherein the receiver 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. (Supplementary Note 8) The core network device according to Supplementary Note 7, wherein the receiver receives a message including third allocation information associating first group information indicating the first computing resource group with information on a first traffic amount to be allocated to the first computing resource, and fourth allocation information associating second group information indicating the second computing resource group with information on a second traffic amount to be allocated to the second computing resource. (Supplementary Note 9) The core network device according to Supplementary Note 8, wherein the receiver receives a message including the changed first traffic amount and the changed second traffic amount after receiving the message. (Supplementary Note 10) The core network device according to Supplementary Note 8 or 9, wherein the receiving unit 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 related to the first traffic volume, and an attribute indicating the second group information and an attribute indicating information related to the second traffic volume are associated with an attribute indicating the fourth allocation information. (Supplementary Note 11) The core network device according to any one of Supplementary Notes 8 to 10, wherein the information related to the first traffic volume and the second traffic volume is indicated using a weight value. (Supplementary Note 12) An application server comprising: a management unit that manages first and second computing resources that provide application services to communication terminals via a mobile network; and a communication unit that transmits traffic allocation information of the first and second computing resources to a core network device that constitutes the mobile network.(Supplementary Note 13) The application server according to Supplementary Note 12, wherein the communication unit transmits a message including first allocation information associating first address information indicating the first computing resource with information on a first traffic volume to be allocated to the first computing resource, and second allocation information associating second address information indicating the second computing resource with information on a second traffic volume to be allocated to the second computing resource. (Supplementary Note 14) The application server according to Supplementary Note 13, wherein the communication unit transmits a message including the changed first traffic volume and the changed second traffic volume after transmitting the message. (Supplementary Note 15) The application server according to Supplementary Note 13 or 14, wherein the communication unit transmits the 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 about the first traffic volume, and an attribute indicating the second address information and an attribute indicating information about the second traffic volume are associated with an attribute indicating the second allocation information. (Supplementary Note 16) The application server according to any one of Supplementary Notes 13 to 15, wherein the information about the first traffic volume and the second traffic volume is indicated using a weight value. (Supplementary Note 17) The application server according to Supplementary Note 12, wherein the management unit manages 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, and the communication unit transmits a message specifying traffic allocation information in the first computing resource group and the second computing resource group to the core network device.(Supplementary Note 18) The application server according to Supplementary Note 17, wherein the communication unit transmits the message including third allocation information associating first group information indicating the first computing resource group with information on a first traffic volume to be allocated to the first computing resource, and fourth allocation information associating second group information indicating the second computing resource group with information on a second traffic volume to be allocated to the second computing resource. (Supplementary Note 19) The application server according to Supplementary Note 18, wherein the communication unit transmits a message including the changed first traffic volume and the changed second traffic volume after transmitting the message. (Supplementary Note 20) The application server according to Supplementary Note 18 or 19, wherein the communication unit 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 related to the first traffic volume, and an attribute indicating the second group information and an attribute indicating information related to the second traffic volume are associated with an attribute indicating the fourth allocation information. (Supplementary Note 21) The application server according to any one of Supplementary Notes 18 to 20, wherein the information related to the first traffic volume and the second traffic volume is indicated using a weight value.(Supplementary Note 22) A communications system comprising: an application server that manages a first computing resource and a second computing resource that provide application services to communications terminals 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, from the application server that manages a plurality of computing resources that provide application services to communications terminals via the mobile network, traffic allocation information for the first computing resource and the second computing resource included in the plurality of computing resources, and allocates data received from the communications terminal to the first computing resource and the second computing resource in accordance with the allocation information. (Supplementary Note 23) The communications system according to Supplementary Note 22, wherein the application server transmits a message including first allocation information that associates first address information indicating the first computing resource with information on a first traffic volume to be allocated to the first computing resource, and second allocation information that associates second address information indicating the second computing resource with information on a second traffic volume to be allocated to the second computing resource. (Supplementary Note 24) A communication method executed in a core network device, comprising: receiving, from an application server that manages a plurality of computing resources that provide application services to a communication terminal via a mobile network, traffic allocation information for a first computing resource and a second computing resource included in the plurality of computing resources; and allocating and transmitting data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information.(Supplementary Note 25) The communication method according to Supplementary Note 24, wherein, when receiving the allocation information, a message is received including first allocation information associating first address information indicating the first computing resource with information on a first traffic volume to be allocated to the first computing resource, and second allocation information associating second address information indicating the second computing resource with information on a second traffic volume to be allocated to the second computing resource. (Supplementary Note 26) The communication method according to Supplementary Note 25, when receiving the message, the message is received via one or more other core network devices. (Supplementary Note 27) The communication method according to Supplementary Note 25 or 26, wherein, after receiving the message, a message is received including the changed first traffic volume and second traffic volume. (Supplementary Note 28) The communication method according to any one of Supplementary Notes 25 to 27, wherein, when receiving the message, the 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 related to the first traffic volume, and an attribute indicating the second address information and an attribute indicating information related to the second traffic volume are associated with an attribute indicating the second allocation information. (Supplementary Note 29) The communication method according to any one of Supplementary Notes 25 to 28, wherein the information related to the first traffic volume and the second traffic volume is indicated using a weight value. (Supplementary Note 30) The communication method according to Supplementary Note 24, when receiving the allocation information, receives traffic allocation information for 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.(Supplementary Note 31) The communication method according to Supplementary Note 30, wherein, when receiving the allocation information, a message is received including third allocation information associating first group information indicating the first computing resource group with information on a first traffic volume to be allocated to the first computing resource, and fourth allocation information associating second group information indicating the second computing resource group with information on a second traffic volume to be allocated to the second computing resource. (Supplementary Note 32) The communication method according to Supplementary Note 31, when receiving the message, a message is received including the changed first traffic volume and second traffic volume after receiving the message. (Supplementary Note 33) The communication method according to Supplementary Note 31 or 32, wherein, when receiving the message, 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 related to the first traffic volume, and an attribute indicating the second group information and an attribute indicating information related to the second traffic volume are associated with an attribute indicating the fourth allocation information. (Supplementary Note 34) The communication method according to any one of Supplementary Notes 31 to 33, wherein the information related to the first traffic volume and the second traffic volume is indicated using a weight value. (Supplementary Note 35) A communication method executed in an application server, which manages a first computing resource and a second computing resource that provide an application service to a communication terminal via a mobile network, and transmits traffic allocation information of the first computing resource and the second computing resource to a core network device that constitutes the mobile network.(Supplementary Note 36) The communication method according to Supplementary Note 35, wherein, when transmitting the allocation information, a message including first allocation information associating first address information indicating the first computing resource with information on a first traffic volume to be allocated to the first computing resource, and second allocation information associating second address information indicating the second computing resource with information on a second traffic volume to be allocated to the second computing resource is transmitted. (Supplementary Note 37) The communication method according to Supplementary Note 36, wherein, after transmitting the message, a message including information on the changed first traffic volume and second traffic volume is transmitted. (Supplementary Note 38) The communication method according to Supplementary Note 36 or 37, wherein, when transmitting the message, 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 about the first traffic volume, and an attribute indicating the second address information and an attribute indicating information about the second traffic volume are associated with an attribute indicating the second allocation information. (Supplementary Note 39) The communication method according to any one of Supplementary Notes 36 to 38, wherein the information about the first traffic volume and the second traffic volume is indicated using a weight value. (Supplementary Note 40) The communication method according to Supplementary Note 35, managing 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, and, when transmitting the allocation information, transmitting a message specifying traffic allocation information in the first computing resource group and the second computing resource group to the core network device.(Supplementary Note 41) The communication method according to Supplementary Note 40, wherein, when transmitting the message, the message includes third allocation information associating first group information indicating the first computing resource group with information on a first traffic volume to be allocated to the first computing resource, and fourth allocation information associating second group information indicating the second computing resource group with information on a second traffic volume to be allocated to the second computing resource. (Supplementary Note 42) The communication method according to Supplementary Note 41, wherein, after transmitting the message, a message including information on the changed first traffic volume and second traffic volume is transmitted. (Supplementary Note 43) The communication method according to Supplementary Note 41 or 42, wherein, when transmitting the message, an attribute indicating the third allocation information is associated with an attribute indicating the first group information and an attribute indicating information related to the first traffic volume, and an attribute indicating the second group information and an attribute indicating information related to the second traffic volume are associated with an attribute indicating the fourth allocation information. (Supplementary Note 44) The communication method according to any one of Supplementary Notes 41 to 43, wherein the information related to the first traffic volume and the second traffic volume is indicated using a weight value. (Supplementary Note 45) A program causing a computer to execute the following: managing a first computing resource and a second computing resource that provide an application service to a communication terminal via a mobile network, and transmitting traffic allocation information of the first computing resource and the second computing resource to a core network device that constitutes the mobile network.(Supplementary Note 46) A program that causes a computer to execute the following: receiving, from an application server that manages a plurality of computing resources that provide application services to a communication terminal via a mobile network, traffic allocation information for a first computing resource and a second computing resource included in the plurality of computing resources; and allocating data received from the communication terminal to the first computing resource and the second computing resource according to the allocation information.

[0092] This application claims priority based on Japanese Patent Application No. 2022-127027, filed on August 9, 2022, the disclosure of which is incorporated herein by reference in its entirety.

[0093] 10 Application server 11 Management unit 12 Communication unit 20 Core network device 21 Receiving unit 22 Transmitting unit 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 constituting a mobile network, a receiving means for receiving, from an application server managing a plurality of computing resources that provide an application service to a communication terminal via the mobile network, traffic allocation information for a first computing resource and a second computing resource included in the plurality of computing resources; A core network device comprising: a transmitting means for allocating and transmitting data received from the communication terminal to the first computing resource and the second computing resource in accordance with the allocation information.

2. The receiving means includes:

2. The core network device of claim 1, receiving a message including first allocation information that associates first address information indicating the first computing resource with information regarding a first traffic amount to be allocated to the first computing resource, and second allocation information that associates second address information indicating the second computing resource with information regarding a second traffic amount to be allocated to the second computing resource.

3. The core network device according to claim 2 , wherein the receiving means receives the message via one or more other core network devices.

4. The receiving means includes: The core network device according to claim 2 or 3, further comprising: a message including the first traffic volume and the second traffic volume that have been changed after receiving the message.

5. A core network device as described in claim 2 or 3, wherein information regarding the first traffic volume and the second traffic volume is indicated using a weight value.

6. The receiving means: The core network device according to claim 1 , further comprising: 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.

7. The receiving means:

7. The core network device of claim 6, further comprising: a message including: third allocation information associating first group information indicating the first computing resource group with information regarding a first traffic amount to be allocated to the first computing resource; and fourth allocation information associating second group information indicating the second computing resource group with information regarding a second traffic amount to be allocated to the second computing resource.

8. The receiving means: The core network device according to claim 7 , further comprising: a message receiving unit configured to receive, after receiving the message, a message including the first traffic volume and the second traffic volume that have been changed.

9. The receiving means:

9. The core network device according to claim 7 or 8, 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 volume, 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 volume.

10. A method for receiving traffic distribution information for a first computing resource and a second computing resource included in a plurality of computing resources from an application server that manages the plurality of computing resources and provides an application service to a communication terminal via a mobile network; A communication method executed 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 in accordance with the distribution information.