JPWO2017002729A1 - Control method and control apparatus - Google Patents

Abstract

Provided are a control method and a control apparatus capable of appropriately changing a device on a network for executing a request process from a terminal. In the node changing device 10, the sequence monitoring unit 12 acquires information (for example, a charging upper limit notification) indicating the usage state of the node by the UE 90. The placement calculation unit 14 changes the node that executes the request processing from the UE 90 from the edge 40 connected to the RAN to the data center 70 based on the above-mentioned charging upper limit notification. Therefore, since the processing is changed to a node in another network using the usage information, it is possible to balance the cost and the speed according to the usage.

Description

  The present invention relates to a control method and a control apparatus.

  Conventionally, there is a technology called edge computing that reduces communication delays compared to cloud computing environments that are centrally deployed on a global scale by distributing processing to edge servers near the terminal such as smartphones on the network. It is considered (Non-Patent Document 1).

“Edge Computing Concept”, [online], NTT Holding Company News Release, [Search June 18, 2015], Internet <http: // www. ntt. co. jp / news2014 / 1401 / 140123a. html>

  As described above, since it is assumed that the edge server performs processing near the terminal, it is necessary to install the edge server in more places. Therefore, if a resource for a service (application) executed by the edge server is secured regardless of the use state, the resource may be wasted. On the other hand, if processing is performed on a data server on a cloud network that is centrally deployed, it becomes difficult to realize processing with low delay.

  Therefore, an object of the present invention is to provide a control method and a control device that can appropriately change a device on a network that executes a request process from a terminal in order to solve the above-described problems.

  In order to achieve the above object, a control method according to an embodiment of the present invention provides information indicating a usage state of a first node that executes a request process by a communication terminal in the control method of a communication system that performs communication of a communication terminal. Or according to the information indicating the usage status of the second node located in a different network hierarchy from the first node, or according to the information indicating the service usage status of the communication terminal, The node that executes the request processing from the communication terminal is changed.

  Further, the control device according to an embodiment of the present invention is a control device of a communication system that performs communication of a communication terminal, according to information indicating a use state of a first node that executes request processing by the communication terminal, or , According to the information indicating the usage status of the second node located in a different network hierarchy from the first node, or according to the information indicating the service usage status of the communication terminal, between the first node and the second node, The node that executes the request processing from the communication terminal is changed.

  According to the above invention, the node that executes the request processing of the communication terminal is changed to a node in another network layer based on the usage state of the first node that executes the request processing by the communication terminal. Balance between cost and speed.

  In the above control method, the communication delay between the communication terminal and the first node may be different from the communication delay between the communication terminal and the second node. As described above, the request and the processing from the communication terminal are executed at the nodes of the network having different delay times according to the use state, thereby making it possible to balance the cost and the speed.

  In the above control method and control apparatus, when the node that executes the request processing from the communication terminal is changed between the first node and the second node, the virtual machine that executes the request processing from the communication terminal It is good also as changing a certain node. In this case, the cost and speed can be balanced in the virtual network.

  In the above control method, the first node activates the virtual machine, makes the application to be executed on the first node executable, executes the request processing from the communication terminal, and requests from the communication terminal. Changing the node that executes the process may be to move the virtual machine of the first node to the second node and execute the application on the virtual machine of the second node. In this way, the cost and speed can be balanced by moving the virtual machine of the first node to the second node and executing the application on the virtual machine of the second node.

  In addition, the control method and the control device described above are information indicating the usage status of the first node that executes the request processing by the communication terminal, or information indicating the usage status of the second node located in a different network hierarchy from the first node. Or a node that executes request processing from the communication terminal between the first node and the second node when any of the information indicating the service usage status of the communication terminal satisfies a predetermined condition May be changed. In this case, since the network hierarchy is changed to a different node based on the usage state, the processing load can be distributed.

  In the above control method and control apparatus, one of the first node and the second node belongs to a self network that is a network in which a communication terminal is located, and the other node is a network different from the self network. It acquires usage information that indicates a usage state by an external terminal that is a terminal belonging to a certain external network and that is a terminal via the external network, and usage information that indicates a usage state by an internal terminal that is a terminal via its own network. Then, the control method and the control device specify the node that executes the request processing from the communication terminal based on the result of comparing the usage information indicating the usage status of the external terminal and the usage information indicating the usage status of the internal terminal. You may change between 1 node and a 2nd node. In this case, the communication control device compares the usage status of the external network and the self network and moves the processing node. Therefore, the processing speed and internal speed of each of the communication terminal from the external network and the communication terminal from the self network are determined. The amount of communication flowing through the network can be adjusted.

  According to an embodiment of the present invention, it is possible to appropriately change a device on a network that executes processing for a request from a terminal.

It is a figure which shows the structure of the system which concerns on embodiment of this invention. It is a block diagram which shows the node change apparatus which concerns on embodiment of this invention. It is a hardware block diagram of a node change apparatus. It is a figure which shows a service policy table. It is a figure which shows an execution place management table. It is a figure which shows an accounting management table. It is a figure which shows a traffic information table. It is a sequence diagram which shows the example of execution of an application. It is a sequence diagram which shows an edge starting process. It is a sequence diagram which changes a processing apparatus from an edge to a data center. It is a flowchart which shows the process which changes an execution apparatus based on charge. It is a sequence diagram which changes a processing apparatus from a data center to an edge. It is a flowchart which shows the process which changes an execution apparatus based on bandwidth utilization. It is a figure which shows the example which changes traffic information based on the change of an execution apparatus. It is a sequence diagram which shows the edge starting process in a modification. It is a figure which shows a processing load condition table. It is a sequence diagram which changes a processing apparatus from the edge in a modification to a data center.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted.

  FIG. 1 shows a configuration of a communication system 1 including a node change device 10 (communication control device) according to the present embodiment. The communication system 1 moves an apparatus that performs processing based on the usage status of the UE 90 from an edge 40 connected to its own network such as a RAN (Regional Area Network) to an apparatus connected to the core network. Or a device that moves the data center 70 from the data center 70 to the edge 40. Here, the self network is a network that is operated by one communication carrier and in which the UE 90 is located.

  As shown in FIG. 1, the communication system 1 includes a node changing device 10, an OSS / BSS (Operations Support System / Business Support System) 20, a MANO (Management & Orchestration) 30, an edge 40, an MME 50, and an SPGW 60. The data center 70, the eNode 80, and the UE 90 are configured.

  Among these, an OSS / BSS (Operations Support System / Business Support System) 20, a MANO (Management & Orchestration) 30, a part of the edge 40, and the MME 50 constitute a core network of the communication system 1. . A part of the eNode 80 and the edge 40 constitutes the RAN. The data center 70 constitutes a WAN (Wide Area Network). The data center 70 can be connected via an external network such as a WAN (a network different from the self network). The components that need to transmit and receive information to each other are connected by wire and wireless so that information can be transmitted and received.

  The UE 90 is a terminal including a smartphone and a tablet terminal, and can communicate by being connected to the communication system 1. When a service processing request is made from the UE 90 to the communication system 1, the service processing (application) is performed by any device (node) of the edge 40 connected to the RAN, the edge 40 connected to the core network, and the data center 70. Is processed).

  The distance from the UE 90 is short in the order of the edge 40 connected to the RAN, the edge 40 connected to the core network, and the data center 70 connected to the external network. Therefore, the edge 40 connected to the RAN having a short distance has the smallest communication delay among the above three devices. Here, the communication delay is between the UE 90 and a device that performs processing in response to a processing request from the UE 90 (the edge 40 connected to the RAN, the edge 40 connected to the core network, and the data center 70). It is determined by the communication time. As described above, the communication system 1 includes a node that executes request processing from the UE 90 in a plurality of networks having different distances to the UE 90. The edge 40 connected to the RAN, the edge 40 connected to the core network, and the data center 70 each have a distributed database (distributed DB), and user data at the time of service execution (data such as user settings). ) Is shared and saved. The difference data of the user data is copied for each predetermined period.

  Further, the edge 40 connected to the RAN, the edge 40 connected to the core network, and the data center 70 connected to the WAN (external network) are connected to networks of different layers (types). . Since the RAN edge 40 executes processing at a position near the UE 90, a large number of RAN edges 40 are widely distributed. On the other hand, since the data center 70 is accessed from an external network, the data center 70 performs processing in an integrated manner and is not so distributed. Therefore, when the edge 40 executes all the above services, the processing result can be immediately provided to the UE 90. However, since the edge 40 is distributed in large numbers, installation costs and resource costs are required. On the other hand, since the data centers 70 are not so distributed, if the data centers 70 consolidate and execute the above services, installation costs and resource costs can be suppressed. However, since there is a distance from the UE 90, the processing time is longer than when the edge 40 executes the service.

  The node changing device 10 confirms the status of the device that performs processing for the service request from the UE 90, and changes the device that is being executed based on the status. Details will be described later.

  The OSS / BSS 20 is a node that performs service management in the communication system 1 and gives instructions related to communication functions in the communication system 1. For example, the OSS / BSS 20 instructs the MANO 30 to add a new communication function (communication service). The OSS / BSS 20 can be operated by a telecommunications carrier related to the communication system 1.

  The MANO 30 includes an NFVO (Network Functions Virtualization Orchestrator), a VNFM (Virtual Network Function Manager), and a VIM (Virtualized Infrastructure Management). The NFVO is an overall management node (functional entity) that manages the entire virtual network constructed on the physical resource. The VNFM is a virtual communication function management node (functional entity) that adds a function related to a service to a physical resource (node). It is a physical resource management node (functional entity) that manages each physical resource (node). Specifically, resource allocation / update / recovery management, association between physical resources and virtualized network, and management of hardware resources and SW resources (hypervisor) list are performed.

  Note that NFVO, VNFM, and VIM are realized by executing a program on a physical server device (however, they are not limited to being realized on virtualization, and are separated from a management system). And may be realized on virtualization). NFVO, VNFM, and VIM may be realized by separate physical server devices, or may be realized by the same server device. NFVO, VNFM, and VIM (programs for realizing) may be provided from different vendors.

  The SPGW 60 is an SGW or a PGW. The SGW (Serving Gate Way) is a visited packet switch that accommodates LTE, and transmits and receives user data to and from the PGW (Packet data network Gate Way). The PGW is a gateway connected to an external network, and performs IP address issue to the UE 90 and the like.

  The MME 50 is a part that performs location management, authentication control, and user data communication path setting processing for the UE 90 located in the LTE network.

  The edge 40 is a server device that performs processing in response to a service request from the UE 90.

  The data center 70 is a server device that performs processing in response to a service request from the UE 90. Various data are also stored.

  Subsequently, functions of the node changing device 10 according to the present embodiment will be described with reference to FIG. As shown in FIG. 2, the node changing device 10 includes an arrangement information storage unit 11, a sequence monitoring unit 12 (use information acquisition unit), a traffic monitoring unit 13 (use information acquisition unit), and an arrangement calculation unit 14 (change unit). ) And an arrangement instructing unit 15 (changing means).

  Here, FIG. 3 shows a hardware configuration of the server apparatus constituting the node changing apparatus 10 according to the present embodiment. As shown in FIG. 3, the node changing device 10 includes a CPU 101, a RAM (Random Access Memory) 102 and a ROM (Read Only Memory) 103, which are main storage devices, a communication module 104 for communication, and an auxiliary device such as a hard disk. The computer is configured to include a computer including hardware such as the storage device 105. The functions of the node changing device 10 described above are exhibited by the operation of these components by a program or the like. Note that the node changing device 10 may be configured by a computer system including a plurality of server devices.

  The arrangement information storage unit 11 is a part that stores information relating to the arrangement of the device that performs processing from the UE 90, such as determination information for changing the arrangement. The arrangement information storage unit 11 stores information on a plurality of types of tables. Specifically, the arrangement information storage unit 11 stores a service policy table, which is a table having information indicating a change condition of a node to be executed, an execution location management table having information on a location where processing is performed, and a charging status of each user. An accounting management table having information to indicate, a usage status from the external network side, and a traffic information table having information indicating the usage status on the internal network side (self network side) are stored.

  FIG. 4 shows an example of the service policy table. As shown in FIG. 4, the service policy table is a table for storing information having a server application address, a service name, and a policy. The server application address is the address of the data center 70 that transmitted the policy. The service name is a name for identifying a service (for example, a name indicating a moving image distribution service, an ITS service, or the like). The policy is information indicating a change condition of the node to be executed.

  The policy whose service name is service 1 indicates that one user executes processing from the UE 90 at the edge up to 300 yen in January, and executes it by a device other than the edge when it exceeds 300 yen. The policy whose service name is service 5 indicates that edge usage is restricted when the processing load status exceeds 80%, and edge usage restriction is canceled when the processing load status falls below 70%. The policy whose service name is service 6 indicates that if there is no service request from the terminal for 10 minutes, the service process is transferred from the edge process to the data center, and is returned from the data center to the edge when requested again. .

  FIG. 5 shows an example of the execution location management table. As shown in FIG. 5, the execution location management table is a table for storing information having a service name, a location, and a user ID. The service name is a name for identifying the service. The location is information indicating a node that executes the service. The user ID is information for identifying the user. As shown in FIG. 5, the service 1 is processed at the edge 1 when a process request is made from the user's UE 90 whose user IDs are the user 1, the user 2, and the user 3. Further, even in the same service 1, when a processing request is made from a user's UE whose user ID is user 4 or user 5, the processing is performed in the data center 1. In this way, the node to be executed varies depending on the user even in the same service.

  Next, FIG. 6 shows an example of the accounting management table. As shown in FIG. 6, the billing management table is a table for storing information having a user ID, a service name, and a billing state.

  The user ID is information for identifying the user. The service name is information for identifying the service. The billing status is information indicating whether the billing has reached the upper limit. For example, for service 1, user 1 has reached the upper limit and user 2 has not yet reached the upper limit.

  Next, FIG. 7 shows an example of a traffic information table. As illustrated in FIG. 7, the traffic information table includes a service name, an execution device, a target user, UE-side traffic (delay and used bandwidth), and WAN-side traffic (delay and used bandwidth). It is a table for storing information.

  The service name is information for specifying the service. The execution device is information indicating a device that executes processing. The target user is information for specifying the target user. Here, a user ID indicating a specific user and information indicating all users are input. The traffic on the UE side indicates information on traffic that has been accessed from the internal network (average value of communication delay, amount of communication per second). The traffic on the WAN side indicates information on traffic that has been accessed from an external network.

  The sequence monitoring unit 12 is a part that makes a sequence monitoring request to the MME 50 or the like and acquires the sequence monitoring result from the MME 50 or the like. Specifically, the sequence monitoring unit 12 makes a monitoring request for charging and a monitoring request for the type of line to be connected (for example, 4G, 5G). When the sequence monitoring unit 12 receives the monitoring instruction from the arrangement instruction unit 15, the sequence monitoring unit 12 monitors the device to be monitored (for example, the MME 50), and indicates the monitoring instruction (user ID to be monitored, service ID, and monitoring target policy). ).

  The sequence monitoring unit 12 receives the monitoring result at a predetermined timing from the device that has instructed the sequence monitoring. As described above, the sequence monitoring unit 12 receives the monitoring result as information on the usage state of the user. The sequence monitoring unit 12 sends the monitoring result to the arrangement calculation unit 14.

  The traffic monitoring unit 13 is a part that makes a traffic monitoring request to a router / switch or the like and obtains a traffic monitoring result from the router / switch or the like. When the traffic monitoring unit 13 receives a monitoring instruction from the arrangement instruction unit 15, the traffic monitoring unit 13 sends a monitoring instruction (information indicating a user ID, a service ID, and a policy to be monitored) to a device to be monitored (for example, SPGW). To do.

  The traffic monitoring unit 13 receives a monitoring result at a predetermined timing from a device that has instructed traffic monitoring. In this way, the traffic monitoring unit 13 receives the monitoring result as information on the usage status of the user, and sends the monitoring result to the arrangement calculation unit 14.

  The arrangement calculation unit 14 is a part that determines a device that performs processing for a service request from the UE 90. When a service request is newly acquired from the UE 90, the arrangement calculation unit 14 determines an apparatus to be executed based on the policy.

  Specifically, the arrangement calculation unit 14 determines a device (data center, core network edge, RAN edge) that executes a service based on a policy. That is, the arrangement calculation unit 14 determines a position where the service is executed. If the placement calculation unit 14 decides to execute at the edge connected to the RAN, the placement calculation unit 14 determines the edge closest to the UE 90 as the execution target device based on the position of the UE 90.

  In addition, when the placement calculation unit 14 receives the monitoring result from the sequence monitoring unit 12 or the traffic monitoring unit 13, if the monitoring result satisfies the change condition of the device to be executed based on the policy of the service policy table, Decide to change the device. As described above, the arrangement calculation unit 14 changes the node that executes the request processing from the communication terminal based on the monitoring result acquired by the sequence monitoring unit 12 or the traffic monitoring unit 13.

  For example, if the upper limit value of charging is exceeded based on the monitoring result (that is, when the usage based on the monitoring result exceeds a predetermined condition), the arrangement calculation unit 14 is a processing target device (node). Is changed from the edge 40 to the edge 40 or the data center 70 of the core node. That is, the arrangement calculation unit 14 determines to change to a network node having a longer distance from the UE 90 compared to the network of the node that is performing the request processing. When the placement calculation unit 14 determines the device to be executed, the placement calculation unit 14 notifies the placement instruction unit 15 of the processing target device.

  The placement instruction unit 15 receives a device to be processed from the placement calculation unit 14 and issues a placement change instruction to the device to the MANO 30. In response to this, the MANO 30 instructs the target device to execute the service request process of the UE 90.

  Next, processing in the system will be described with reference to FIGS. First, with reference to FIG. 8, processing in the case of executing an application relating to an operation state executed by an in-vehicle terminal will be described as a service. Specifically, the application relating to the driving state includes a function of combining images outside the vehicle taken by a plurality of users and a function of route search.

  In addition, as applications related to the operation state executed on the in-vehicle terminal, two types of applications including an application executed at the edge (edge application) and an application executed at the data center (server side application) are included. And

  Specifically, the edge application (edge application) performs a process of displaying and outputting an image obtained by synthesizing a result of analyzing an image indicating an operation state (for example, an image ahead of the vehicle) and the image. The server side application (server side) searches for a route based on the route search request.

  When transmitting the login request to the data center 70, the UE 90B notifies the edge 40 of the login request (step S1). In response to this, the edge 40 activates a virtual machine (VM), which is a virtual machine, so that the edge application can be executed (step S2).

  After the VM is activated, the edge 40 notifies the data center 70 that the VM has been activated, and the data center 70 notifies the UE 90B that the VM has been activated (step S3).

  The UE 90A makes a login request to the data center 70, and the data center 70 notifies the UE 90B that the login has been accepted and the connection destination address (step S4).

  If UE90A and UE90B transmit the image image | photographed with the own terminal to the edge 40 (step S5), the edge 40 will analyze and synthesize | combine each image (step S6).

  The edge 40 transmits the combined image to the UE 90A and the UE 90B (step S7). UE90A and UE90B display AR (augmented reality) the received image (step S8 and step S9).

  Further, the UE 90B requests a route search request to the data center 70 (step S10), and the data center 70 creates a route according to this (step S11). The data center 70 transmits this route to the UE 90B (step S12). The UE 90B displays and outputs this route (step S13).

  As described above, the function that asks for immediacy such as display of a captured image is processed by the edge 40 with a small delay amount, and the function that does not ask for immediacy such as route search is performed by the data center 70. Process.

  Next, a policy registration and VM generation processing procedure will be described with reference to the sequence diagram shown in FIG.

  First, when a policy input operation is performed in the data center 70, the data center 70 sends a policy registration request to the OSS / BSS 20 together with the service name and policy contents to be policyd (step S21). In response to this, the OSS / BSS 20 makes a policy setting request to the node changing device 10 (step S22). The node changing device 10 registers the service name and policy contents that are the subject of the policy in the service policy table. The node changing device 10 notifies the OSS / BSS 20 that registration has been completed (step S23). The OSS / BSS 20 notifies the data center 70 of the notification (step S24). A policy is registered in the service policy table of the node changing device 10 by the processing of step S21 to step S24.

  When an edge connection request (execution request for a service executed at the edge) is made from the UE 90 to the data center 70 (step S25), the service name and the address of the UE 90 are notified from the data center 70 to the OSS / BSS 20, and the edge A creation request is made (step S26). The OSS / BSS 20 makes an edge creation request to the node changing device 10 (step S27).

  The node changing device 10 refers to the service policy table corresponding to the service name (step S28, step S29). The placement calculation unit 14 determines an execution target device based on the contents of the service policy table (step S30). The arrangement calculation unit 14 also determines a monitoring target indicating monitoring contents (for example, a service, a user ID, and a charging status).

  The location calculation unit 14 of the node change device 10 registers information in which the execution target device is associated with the user ID of the UE 90 that requested the service in the execution location management table (step S31 and step S32).

  The placement calculation unit 14 of the node changing device 10 notifies the placement instruction unit 15 of the monitoring request and the placement request (step S33). In response to the placement request, the placement instruction unit 15 notifies the MANO 30 of the service name and the edge address and makes a VM creation request.

  In response to the VM creation request, the MANO 30 notifies the service name to the edge 40 of the requested device and makes a VM creation request (step S35).

  The edge 40 prepares for VM activation and activates an edge application that operates on the VM (step S36). The edge 40 sends an edge application activation completion notification to the MANO 30 (step S37). In response to this, the MANO 30 sends an edge application activation completion notification to the node changing device 10 (step S38).

  The placement instruction unit 15 issues a monitoring instruction to the traffic monitoring unit 13 (step S39). In response to this, the traffic monitoring unit 13 issues a monitoring instruction to the target device, and sends the result of the monitoring instruction to the arrangement instruction unit 15 (step S40).

  The arrangement calculation unit 14 issues a monitoring instruction to the sequence monitoring unit 12 (step S41). In response to this, the sequence monitoring unit 12 issues a monitoring instruction to the target device, and sends the result of the monitoring instruction to the arrangement instruction unit 15 (step S42).

  The placement instruction unit 15 notifies the placement calculation unit 14 of the completion of placement (step S43). In response, the arrangement calculation unit 14 transmits connection information (connection destination address) to the data center 70 (step S44). The data center 70 notifies the connection information to the UE 90 (step S45), and the UE 90 connects to the edge 40 based on the connection information (step S46).

  Next, a process for changing the device to be executed will be described with reference to the sequence diagram of FIG. When the UE 90 makes an edge connection request through the router / switch in the core network (step S51), the router / switch transfers the communication contents to the edge 40 (step S52).

  The OSS / BSS 20 determines the charging status, and if the charging limit has been reached, notifies the node changing device 10 of the charging limit (step S53). The sequence monitoring unit 12 notifies the billing limit notification to the arrangement calculation unit 14 (step S54).

  The node changing device 10 refers to the service policy table, the execution location management table, and the charge management table (steps S55 and S56).

  The placement calculation unit 14 determines an execution target device based on the contents of the service policy table (step S57). In addition, the arrangement calculation unit 14 also determines a monitoring target (for example, a service, a user ID, and a charging status).

  The location calculation unit 14 of the node change device 10 registers information in which the execution target device is associated with the user ID of the UE 90 that requested the service in the execution location management table, and updates the charging management table (step S58 and step S58). S59).

  The placement calculation unit 14 of the node changing device 10 notifies the placement instruction unit 15 of the monitoring request and the placement request (step S60). In response to the placement request, the placement instruction unit 15 notifies the MANO 30 of the service name and the address of the change destination device and makes a VM creation request (step S61). The MANO 30 sets the distributed DB replication destination in the data center 70 that is the change destination device, and requests registration of user information (step S62). Further, the MANO 30 prohibits subsequent updates to the distributed DB of the change source device. When the registration of user information is completed, the data center 70 notifies the MANO 30 to that effect (step S63).

  The MANO 30 notifies the edge 40 of the change of processing target (VM aggregation) (step S64), and the edge 40 performs an end process (edge application activation end) accordingly (step S65). When the process is finished, the MANO 30 is notified to that effect (step S66).

  The MANO 30 instructs the SPGW 60 to switch the flow (step S67), and the SPGW 60 performs a flow switching process accordingly and notifies the MANO 30 that the process is complete (step S68). The MANO 30 issues a flow switching instruction to the router / switch (step S69). When the switching is completed, the router / switch notifies the MANO 30 (step S70). In this way, the MANO 30 sets a communication path so that the data center 70 performs the processing in response to a processing request from the UE 90.

  The MANO 30 notifies the arrangement instruction unit 15 of the completion of aggregation (Step S71). The arrangement instruction unit 15 instructs the sequence monitoring unit 12 to end monitoring (step S72), and receives a completion notification from the sequence monitoring unit 12 (step S73).

  The placement instructing unit 15 instructs the traffic monitoring unit 13 to end monitoring (step S74), and receives a completion notification from the traffic monitoring unit 13 (step S75). Thereafter, the arrangement instruction unit 15 notifies the arrangement calculation unit 14 that the rearrangement is completed (step S76).

  Thus, when the UE 90 makes a server application communication request via the router / switch (step S77), the router / switch notifies the SPGW, and in response, the SPGW receives the data center 70 via the router / switch. (Step S79, step S80). The data center 70 issues a user data read request to the distributed DB at the edge 40 (step S81), and acquires the user data from the edge 40. The data center 70 performs processing according to the processing request from the UE 90 using this user data.

  Next, a process (step S57 shown in FIG. 10) in which the arrangement calculation unit 14 performs movement determination will be described using the flowchart shown in FIG.

  The arrangement calculation unit 14 always waits for a movement change event (step S91). When a notification of any event is received, the processing after step S92 is performed. When a charging event occurs, such as when the sequence monitoring unit 12 receives a charging limit notification (step S92; YES), the charging management table is updated (step S93). It is determined whether the processing device is the edge 40 or the data center 70 (step S94). When the processing apparatus is the edge 40, when a charging event has occurred and a charging limit notification has been received (step S95; YES), the process moves to step S97.

  If no billing limit notification has been received, and no transition has been made to 3G or 4G (step S96; NO), the process proceeds to step S91 without changing the processing device. If the billing limit notification has not been received and the line type has changed to 3G or 4G (step S96; YES), the process moves to step S97. In step S97, the arrangement calculation unit 14 determines to move to the data center 70 (step S97).

  If the device currently being processed is the data center 70, the process moves to step S98, and if not the transition to 5G (step S98; NO), the process moves to step S91. When the transition is made to 5G (step S98; YES), when the charging limit is reached (step S99; NO), the processing device is moved to step S91 without changing, and the charging limit is not reached (step S99; YES), it is determined to move to the edge 40 (step S100).

  Next, processing for changing a processing device based on traffic will be described using the sequence diagram of FIG.

  When the UE 90A, which is an internal terminal (terminal in its own network), requests the router / switch to process the edge 40 (step S111), the router / switch connects to the edge 40 (step S112). The router / switch notifies the traffic monitoring unit 13 of communication traffic to the edge 40 (step S113).

  Based on the notification, the traffic monitoring unit 13 receives a traffic information update request and an update completion notification (steps S114 and S115).

  The UE 90B (terminal WAN), which is an external terminal (terminal connected via an external network), issues a processing request to the edge switch 40 to the router / switch via the data center 70 (step S116). In response to this, the router switch connects to the edge 40 (step S117). The router / switch notifies the traffic monitoring unit 13 of communication traffic to the edge 40 (step S118).

  Based on the notification, the traffic monitoring unit 13 receives an update request for traffic information and an update completion notification (steps S119 and S120).

  The traffic monitoring unit 13 periodically compares the UE-side traffic acquired in step S113 with the WAN-side traffic acquired in step S118, and conditions such as when there is a difference greater than or equal to a predetermined threshold Is satisfied, the placement calculation unit 14 is notified (step S121). The arrangement calculation unit 14 requests the arrangement information storage unit 11 to acquire the service policy table and the traffic information table (step S122), and acquires the service policy table and the traffic information table from the arrangement information storage unit 11 (step S123). .

  The placement calculation unit 14 changes the processing device based on the result of comparing the above-described UE-side traffic and WAN-side traffic (step S124). The placement calculation unit 14 makes an update request for the execution location management table and the traffic information table (step S125), and when receiving the update result (step S126), the placement calculation unit 14 sends a rearrangement / monitoring destination / change notification to the placement instruction unit 15. This is performed (step S127). The processing of step S128 to step S145 is the same as that of step S61 of FIG. 10 except that the flow switching instruction processing between MANO 30 and SPGW (step S67 and step S68 of FIG. 10) is not included in the sequence of FIG. Since it is the same as S82, description is abbreviate | omitted.

  A process (step S124 shown in FIG. 12) in which the placement calculation unit 14 performs movement determination will be described using the flowchart shown in FIG.

  The arrangement calculation unit 14 always waits for a movement change event (step S151). When the notification from the traffic monitoring unit 13 is received, it is confirmed which one has the higher bandwidth utilization (that is, the communication amount per second) (step S152). As a result, if there are more on the WAN side, it is changed to the DC (data center 70) side within a range that satisfies the delay request (step S153). When there are more UE side, it changes to UE side in the range which satisfies a delay request | requirement (step S154). Here, the change to the DC side means a change from the edge 40 of the RAN to the edge 40 or the data center 70 of the core network, or a change from the edge 40 of the core network to the data center 70. Further, the change to the UE side means a change from the data center 70 to the edge 40 of the core network or the edge 40 of the RAN, or a change from the edge 40 of the core network to the edge 40 of the RAN. Further, the arrangement calculation unit 14 determines a change destination within a range satisfying the delay request based on a preset delay time threshold. The arrangement calculation unit 14 determines whether or not the delay time on the UE side of the edge to be changed in the traffic information table is equal to or less than the threshold value, and determines whether or not the delay request is satisfied.

  Here, FIG. 14 shows an example of moving to the data center 70 when implemented at the edge 40. As a result of performing the processing at the edge 40, as shown in FIG. 14A, the usage band of the edge 2 of the service 1 is larger on the WAN side. In response to this, the edge 40 is changed to the data center 70 as shown in FIG.

  Subsequently, a modification will be described with reference to FIGS. In this modification, when the processing load status of the edge 40 satisfies the regulation condition, the data center 70 performs processing until the processing load status satisfies the regulation release condition.

  The sequence diagram shown in FIG. 15 includes many parts that are common to the sequence diagram shown in FIG. 9, and therefore, the description will focus on parts different from the sequence diagram shown in FIG. 9.

  After the OSS / BSS 20 notifies the data center 70 of the policy registration completion notification, the data center 70 and the edge 40 notify the OSS / BSS 20 of information indicating the processing load status of the data center 70 and the edge 40 (step S24A). And step S24B). When the OSS / BSS 20 receives information indicating the processing load status from the data center 70 and the edge 40, the OSS / BSS 20 stores the information indicating the processing load status for each apparatus (location) in the processing load status table as shown in FIG. . As shown in FIG. 16, the OSS / BSS 20 stores a processing load status table in which a location and a processing load status are associated with each other. Here, the processing load status is information indicating a resource usage rate. Since edge 1 has a processing load status of 30%, there is room to accept a new processing request from UE 90, but edge 2 has a processing load status of 90%, so There is no room to accept the processing request.

  In step S30A, the arrangement calculation unit 14 determines an execution target device (edge 40) based on the contents of the service policy table. If the policy of the service 5 in the service policy table is valid, the arrangement calculation unit 14 On the other hand, the processing load status of the edge 40 is inquired. The placement calculation unit 14 determines that the processing load situation is to be executed in the data center 70 when the processing load status is to be regulated based on the policy condition. For example, when the inquiry target edge 40 is the edge 2 in the example shown in FIG. 16, the processing load status is 90%, and thus the restriction target. In addition, the arrangement calculation unit 14 sets the initially determined edge 40 as a monitoring target.

  In step S33A, the arrangement calculation unit 14 notifies the arrangement instruction unit 15 of the execution target device (data center 70) and the monitoring target. In response to this, the placement instruction unit 15 requests the MANO 30 to create a VM (step S34). Further, the placement instruction unit 15 causes the OSS / BSS 20 to monitor the edge 40 to be monitored via the MANO 30. The MANO 30 makes a VM creation request to the data center 70 (step S35A), and the data center 70 activates the VM activation / edge application (step S36A). When the data center 70 completes the activation of the edge application, it notifies the MANO 30 to that effect (step S37A). The data center 70 may activate the VM and the edge application in advance. As described above, the arrangement instructing unit 15 causes the data center 70 to process the request processing from the UE 90. When the UE 90 makes a connection request (step S46A), the arrangement instructing unit 15 connects to the data center 70 via the SPGW.

  Next, an example of a process of moving a VM from the data center 70 to the edge 40 (a process of changing a VM that executes a processing request from the UE 90 from the data center 70 to the edge 40) will be described with reference to FIG. The process illustrated in FIG. 17 will be described with a focus on differences from the process of FIG.

  When a processing request is made from the UE 90 (step S51), the UE 90 is connected to the data center 70 through the router / switch via the SPGW (step S52A). As described with reference to FIG. 15, since the edge 40 is a monitoring target, the edge 40 periodically notifies the OSS / BSS 20 of information indicating the processing load status (step S52B). When the processing load status of the edge 40 falls below 70%, the OSS / BSS 20 notifies the sequence monitoring unit 12 to that effect (step S53A). Then, the sequence monitoring unit 12 notifies the arrangement calculation unit 14 that the processing load status has fallen below 70% (step S54A).

  The MANO 30 issues a DB replication destination setting request to the edge 40 (step S62A). The edge 40 notifies the MANO 30 of DB replication setting completion (step S63A), and the edge 40 activates the VM and the edge application (step S65A). Then, after the flow is switched (steps S67 to S70), when the UE 90 requests connection, the UE 90 connects to the edge 40 (steps S77A and S80).

  In this way, the usage status of a device (the edge 40 in the above example) other than the device (the data center 70 in the above example) that executes the request processing from the UE 90 is monitored, and according to the usage status. , The VM may be moved from the data center 70 to the edge 40.

  Although not described above, the UE 90 may move the VM from the edge 40 to the data center 70 based on the policy of the service 6 when the UE 90 does not transmit and receive data for a certain period. For example, after the edge 40 is determined to execute the request processing from the UE 90, as a result of the OSS / BSS 20 monitoring the processing request from the UE 90, when there is no data transmission / reception from the UE 90 to the edge 40, the edge 40 The VM is moved from the data center 70 to the data center 70. Thereafter, when the OSS / BSS 20 detects that a processing request has been made from the UE 90, the OSS / BSS 20 notifies the arrangement calculation unit 14 of the node change device 10. Upon receiving the notification, the arrangement calculation unit 14 changes from the data center 70 to the edge 40. In addition to information related to the data communication status of the communication terminal, such as during data communication / no data communication, information related to the data communication frequency (communication amount / number of times per unit time) of the communication terminal is used by the communication terminal. The change of the VM may be determined based on, for example, a severe / loose state of a data communication delay requirement required for a certain service. In this way, the VM may be changed from the edge 40 to the data center 70 based on the service usage state of the UE 90 (request processing state from the UE 90 to the edge 40), or the VM from the data center 70 to the edge 40 may be changed. May be changed.

  In the above-described embodiment, the case where the VM is moved from the RAN edge 40 to the data center 70 based on the charging limit notification has been described. However, the VM may be moved from the RAN edge 40 to the edge 40 of the core network. .

  In the above-described embodiment, the case where the node changing device 10 is realized by one server device has been described. However, the function of the node changing device 10 may be realized by a plurality of server devices.

  Although not particularly described in the above-described embodiment, it may be determined whether or not the node changing device 10 can move to the destination node. As an example of the determination, the node change device 10 obtains information about the number of CPUs of the destination node, the amount of memory, the amount of disk (disk capacity), the number of communication terminals / sessions connected to the destination node, and the NW bandwidth information from the MANO 30. The acquired information is compared with a preset threshold value to determine whether or not it is possible to move to the destination node. Further, as another example of the above determination, the node change device 10 may be a node (for example, SPGW 60, local gateway (LGW), DPI (Deep Packet Inspection), DNS ( Domain Name Server) etc.) is obtained from MANO 30, and the obtained information is compared with a preset threshold value to determine whether or not it is possible to move to the destination node. Good. In addition, when the node required for the processing of the destination node is a non-virtualized device, the load amount is managed by each destination node, or a management system dedicated to a mobile edge computer The load amount may be managed by (a system different from MANO 30). Further, as another example of the above determination, the node changing device 10 obtains information on the capacity of the radio equipment (the usage rate of the radio resource block, the CPU usage rate of the base station device, etc.) in the destination node as the base station device or It is acquired from MANO30 (when the base station device is managed by the virtualization platform), and the acquired information is compared with a preset threshold value to determine whether or not it is possible to move to the destination node Also good.

  As a result of determining whether or not the node changing apparatus 10 can move to the movement destination node, if it is determined that movement is not possible, the low priority application assigned to the movement destination node is moved to another node. Move again. As a result of determining whether or not the node changing device 10 can move to the destination node, if it is determined that the movement is impossible, SPGW 60, DNS, etc., if the equipment can be augmented by scaling out or scaling up, Move after enhancement.

  Next, the effect of the node change apparatus 10 in this embodiment is demonstrated. In the node change device 10 of the present embodiment, the sequence monitoring unit 12 acquires information (for example, a charging upper limit notification) indicating the usage state of the first node (for example, the edge 40 connected to the RAN) by the UE 90. Based on the above charging upper limit notification, the arrangement calculation unit 14 changes the node that executes the request processing from the UE 90 from the edge 40 connected to the RAN to the data center 70 (second node having a different network hierarchy). Specifically, the edge 40 executes a request process from the UE 90 by activating the VM / edge application, and the placement calculation unit 14 and the placement instruction unit 15 move the VM to the data center 70, The edge application is executed in the data center 70. Thereby, since the process which changes the node which performs the request | requirement process of UE90 to the node of another network based on use information can be balanced with cost and speed according to a use state.

  The edge 40 that is the node before the change and the data center 70 that is the node after the change are different from each other in the types of the connected networks. The edge 40 is connected to the RAN, and the data center 70 is connected to the WAN. Since the edge 40 connected to the RAN has a shorter distance to the UE 90 than the data center 70 connected to the WAN, the edge 40 has a smaller communication delay than the data center 70. Therefore, the cost and speed can be balanced by changing the device that executes the request processing from the UE 90 according to the use state.

  When the charging state exceeds the condition (charging upper limit) as described above (when the usage state satisfies a predetermined condition), the arrangement calculation unit 14 compares the request with the network (RAN) of the node that is performing the request processing. Thus, the data center 70 is connected to a network (WAN) having a long distance from the UE 90. As described above, since the node is changed to a network node having a different hierarchy based on the use state, it is possible to distribute the processing load and the bandwidth usage of the network.

  Further, the traffic monitoring unit 13 acquires usage information indicating the usage status of the UE 90 using the external network and usage information indicating the usage status of the UE 90 by the RAN. Based on the result of comparing the usage information indicating the usage status of the UE 90 via the WAN and the usage information indicating the usage status of the UE 90 via the RAN, the arrangement calculation unit 14 sets other nodes that execute the request processing from the UE 90. Switch to the network node. Thereby, since the processing node is moved by comparing the usage state of the external network and the self network, the processing speeds of the communication terminal from the external network and the communication terminal from the self network can be adjusted.

  Software, whether it is called software, firmware, middleware, microcode, hardware description language, or other names, instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. should be interpreted broadly.

  Also, software, instructions, etc. may be transmitted / received via a transmission medium. For example, software may use websites, servers, or other devices using wired technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or wireless technology such as infrared, wireless and microwave. When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission media.

  Information, signals, etc. described herein may be represented using any of a variety of different technologies. For example, data, commands, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these May be represented by a combination of

  Note that the terms described in this specification and / or terms necessary for understanding this specification may be replaced with terms having the same or similar meaning. For example, the channel and / or symbol may be a signal. The signal may be a message. Further, the component carrier (CC) may be called a carrier frequency, a cell, or the like.

  As used herein, the terms “system” and “network” are used interchangeably.

  In addition, information, parameters, and the like described in this specification may be represented by absolute values, may be represented by relative values from a predetermined value, or may be represented by other corresponding information. . For example, the radio resource may be indicated by an index.

  The names used for the parameters described above are not limiting in any way. Further, mathematical formulas and the like that use these parameters may differ from those explicitly disclosed herein. Since various channels (eg, PUCCH, PDCCH, etc.) and information elements (eg, TPC, etc.) can be identified by any suitable name, the various names assigned to these various channels and information elements are However, it is not limited.

  A base station may accommodate one or more (eg, three) cells (also referred to as sectors). When the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each smaller area can be divided into a base station subsystem (for example, an indoor small base station RRH: Remote). Communication service can also be provided by Radio Head). The term “cell” or “sector” refers to part or all of the coverage area of a base station and / or base station subsystem that provides communication services in this coverage. Further, the terms “base station”, “eNB”, “cell”, and “sector” may be used interchangeably herein. A base station may also be referred to in terms such as a fixed station, NodeB, eNodeB (eNB), access point, femtocell, small cell, and the like.

  A mobile station is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be called terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terminology.

  In addition, the terms “determining” and “determining” as used herein encompass a wide variety of operations. “Judgment” and “determination” are, for example, judgment, calculation, calculation, processing, derivation, investigating, looking up (eg, table , Searching in a database or another data structure), considering ascertaining as “determining”, “deciding”, and the like. Also, “determination” and “determination” are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (accessing) (e.g., accessing data in a memory) may be considered as "determined" or "determined". In addition, “determination” and “decision” means that “resolving”, “selecting”, “choosing”, “establishing”, and “comparing” are regarded as “determining” and “deciding”. May be included. In other words, “determination” and “determination” may include considering some operation as “determination” and “determination”.

  The terms “connected”, “coupled”, or any variation thereof, means any direct or indirect connection or coupling between two or more elements and It can include the presence of one or more intermediate elements between two “connected” or “coupled” elements. The coupling or connection between the elements may be physical, logical, or a combination thereof. As used herein, the two elements are radio frequency by using one or more wires, cables and / or printed electrical connections, and as some non-limiting and non-inclusive examples By using electromagnetic energy, such as electromagnetic energy having a wavelength in the region, microwave region, and light (both visible and invisible) region, it can be considered to be “connected” or “coupled” to each other.

  As used herein, the phrase “based on” does not mean “based only on,” unless expressly specified otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”

  Any reference to elements using the designations "first", "second", etc. as used herein does not generally limit the amount or order of those elements. These designations can be used herein as a convenient way to distinguish between two or more elements. Thus, a reference to the first and second elements does not mean that only two elements can be employed there, or that in some way the first element must precede the second element.

  Further, the “means” in the configuration of each apparatus described above may be replaced with “unit”, “circuit”, “device”, and the like.

  As long as the terms “including”, “comprising”, and variations thereof are used herein or in the claims, these terms are inclusive of the term “comprising”. Intended to be Furthermore, the term “or” as used herein or in the claims is not intended to be an exclusive OR.

  The notification of information is not limited to the aspect / embodiment described in the present specification, and may be performed by other methods. For example, information notification includes physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or a combination thereof. The RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

  In addition, each aspect / embodiment described in this specification includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W -CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-WideBand) ), Bluetooth (registered trademark), other appropriate systems, and / or next-generation systems extended based on these systems.

  In addition, the order of the processing procedures, sequences, flowcharts, and the like of each aspect / embodiment described in this specification may be changed as long as there is no contradiction. For example, the methods described herein present the elements of the various steps in an exemplary order and are not limited to the specific order presented.

  In addition, the specific operation assumed to be performed by the base station in this specification may be performed by the upper node in some cases. In a network composed of one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station and / or other network nodes other than the base station (e.g., Obviously, this can be done by MME or S-GW, but not limited to these. Although the case where there is one network node other than the base station in the above is illustrated, a combination of a plurality of other network nodes (for example, MME and S-GW) may be used.

  The above information and the like can be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input / output may be performed via a plurality of network nodes.

  Input / output information or the like may be stored in a specific location (for example, a memory) or may be managed by a management table. Input / output information and the like can be overwritten, updated, or additionally written. The output information or the like may be deleted. The input information etc. may be deleted. The input information or the like may be transmitted to another device.

  The determination may be performed by a value represented by 1 bit (0 or 1), may be performed by a true / false value (Boolean: true or false), or may be performed by comparing numerical values (for example, a predetermined value) Comparison with the value).

  Each aspect / embodiment described in this specification may be used independently, may be used in combination, or may be switched according to execution. In addition, notification of predetermined information (for example, notification of being “X”) is not limited to explicitly performed, but is performed implicitly (for example, notification of the predetermined information is not performed). Also good.

  Throughout this disclosure, both the singular and the plural are intended to be included unless clearly indicated to be singular.

  Although the present invention has been described in detail above, it will be apparent to those skilled in the art that the present invention is not limited to the embodiments described herein. The present invention can be implemented as modified and changed modes without departing from the spirit and scope of the present invention defined by the description of the scope of claims. Therefore, the description of the present specification is for illustrative purposes and does not have any limiting meaning to the present invention.

  DESCRIPTION OF SYMBOLS 1 ... Communication system, 10 ... Node change apparatus, 11 ... Arrangement information storage part, 12 ... Sequence monitoring part, 13 ... Traffic monitoring part, 14 ... Arrangement calculation part, 15 ... Arrangement instruction part, 20 ... OSS / BSS, 30 ... MANO, 40 ... edge, 50 ... MME, 60 ... SPGW, 70 ... data center, 80 ... eNodeB, 90 ... UE, 101 ... CPU, 102 ... RAM, 103 ... ROM, 104 ... communication module, 105 ... auxiliary storage device.

Claims (10)

In a control method of a communication system that performs communication of a communication terminal,
According to the information indicating the usage state of the first node that executes the request processing by the communication terminal, or
According to information indicating a usage state of a second node located in a different network hierarchy from the first node, or
According to the information indicating the service usage status of the communication terminal,
The control method of changing the node which performs the request process from the said communication terminal between the said 1st node and the said 2nd node.   The control method according to claim 1, wherein a communication delay between the communication terminal and the first node is different from a communication delay between the communication terminal and the second node. To change a node that executes a request process from the communication terminal between the first node and the second node,
The control method according to claim 1, wherein the node having a virtual machine that executes a request process from the communication terminal is changed. The first node starts a virtual machine, makes an application to be executed on the first node ready, and executes a request process from the communication terminal,
To change the node that executes the request processing from the communication terminal, the virtual machine of the first node is moved to the second node,
Running the application on the virtual machine of the second node;
The control method according to claim 3. Information indicating the usage state of the first node that executes request processing by the communication terminal, or
Information indicating the usage status of the second node located in a different network hierarchy from the first node, or
When any of the information indicating the service usage status of the communication terminal satisfies a predetermined condition, a request process from the communication terminal is executed between the first node and the second node. The control method according to claim 1, wherein the node is changed. Either the first node or the second node belongs to a self-network that is a network in which the communication terminal is located, and the other node belongs to an external network that is a network different from the self-network,
Obtaining usage information indicating a usage state by an external terminal that is a terminal connected via the external network, and usage information indicating a usage state by an internal terminal that is a terminal in the self-network;
Based on the result of comparing the usage information indicating the usage status of the external terminal and the usage information indicating the usage status of the internal terminal, the nodes that execute the request processing from the communication terminal are the first node and the second node The control method according to any one of claims 1 to 5, wherein the control method is changed between. In a control device of a communication system that performs communication of a communication terminal,
According to the information indicating the usage state of the first node that executes the request processing by the communication terminal, or
According to information indicating a usage state of a second node located in a different network hierarchy from the first node, or
According to the information indicating the service usage status of the communication terminal,
The control apparatus which changes the node which performs the request | requirement process from the said communication terminal between the said 1st node and the said 2nd node. To change a node that executes a request process from the communication terminal between the first node and the second node,
The control device according to claim 7, wherein the node is a node in which a virtual machine that executes request processing from the communication terminal is located. Information indicating the usage state of the first node that executes request processing by the communication terminal, or
Information indicating the usage status of the second node located in a different network hierarchy from the first node, or
When any of the information indicating the service usage status of the communication terminal satisfies a predetermined condition, a request process from the communication terminal is executed between the first node and the second node. The control device according to claim 7, wherein a node to be changed is changed. Either the first node or the second node belongs to a self-network that is a network in which the communication terminal is located, and the other node belongs to an external network that is a network different from the self-network,
Obtaining usage information indicating a usage state by an external terminal that is a terminal connected via the external network, and usage information indicating a usage state by an internal terminal that is a terminal in the self-network;
Based on the result of comparing the usage information indicating the usage status of the external terminal and the usage information indicating the usage status of the internal terminal, the nodes that execute the request processing from the communication terminal are the first node and the second node The control device according to any one of claims 7 to 9, wherein the control device is changed between.

Images