WO2017002729A1 - Control method and control device - Google Patents

Control method and control device Download PDF

Info

Publication number
WO2017002729A1
WO2017002729A1 PCT/JP2016/068854 JP2016068854W WO2017002729A1 WO 2017002729 A1 WO2017002729 A1 WO 2017002729A1 JP 2016068854 W JP2016068854 W JP 2016068854W WO 2017002729 A1 WO2017002729 A1 WO 2017002729A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
communication terminal
network
information indicating
edge
Prior art date
Application number
PCT/JP2016/068854
Other languages
French (fr)
Japanese (ja)
Inventor
健生 山▲崎▼
基 田村
滋 岩科
陳　嵐
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to JP2017526323A priority Critical patent/JP6731407B2/en
Publication of WO2017002729A1 publication Critical patent/WO2017002729A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]

Definitions

  • the present invention relates to a control method and control device.
  • edge computing that reduces communication delay compared to a globally deployed cloud computing environment on a global scale. It is considered (nonpatent literature 1).
  • edge server assumes processing near the terminal, it is necessary to install the edge server in more places. Therefore, if resources for services (applications) to be executed by the edge server are secured regardless of the use state, the resources may be wasted. On the other hand, if processing is performed by a centralizedly deployed data server on a cloud network, it becomes difficult to realize processing with low delay.
  • a control method is, in a control method of a communication system that performs communication of communication terminals, information indicating a use state of a first node that executes request processing by the communication terminals. Or according to the information indicating the use state of the second node located in the network layer different from the first node, or according to the information indicating the service use state of the communication terminal, the first node and the second node Between the nodes, the node executing the request processing from the communication terminal is changed.
  • control device is a control device of a communication system which performs communication of the communication terminal, and according to the information indicating the usage state of the first node which executes the request processing by the communication terminal, Between the first node and the second node according to the information indicating the use state of the second node located in the network layer different from the first node, or according to the information indicating the service use state of the communication terminal, Change the node that executes the request processing from the communication terminal.
  • the node executing the request processing of the communication terminal is changed to a node of another network layer based on the usage state of the first node executing the request processing by the communication terminal, etc. Cost and speed.
  • 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.
  • cost and speed can be balanced by executing request processing from the communication terminal at nodes of different networks depending on the use state.
  • changing the node that executes the request processing from the communication terminal between the first node and the second node means that the virtual machine executes the request processing from the communication terminal. It is also possible to change a certain node. In this case, cost and speed can be balanced in the virtualization network.
  • the first node starts a virtual machine, enables execution of an application for execution on the first node, executes request processing from the communication terminal, and requests from the communication terminal Changing the node that executes processing may move the virtual machine of the first node to the second node and cause the application to be executed by the virtual machine of the second node.
  • Changing the node that executes processing may move the virtual machine of the first node to the second node and cause the application to be executed by the virtual machine of the second node.
  • control method and the control device described above may be information indicating the use state of the first node that executes the request processing by the communication terminal, or information indicating the use state of the second node located in a different network layer from the first node.
  • the node that executes request processing from the communication terminal between the first node and the second node May be changed. In this case, the processing load can be distributed because the network hierarchy is changed to a different node based on the usage state.
  • one of the first node and the second node belongs to a self network which is a network in which the communication terminal is located, and the other node is a network different from the self network.
  • Usage information that belongs to a certain external network and indicates usage by an external terminal that is a terminal via the external network and usage information that indicates usage by an internal terminal that is a terminal via the own network is acquired.
  • the control method and the control device are configured to execute the request processing from the communication terminal based on the result of comparing the usage information indicating the usage status of the external terminal with the usage information indicating the usage status of the internal terminal. It may be changed between one node and the second node.
  • the communication control device compares the use state of the external network and the own network, and moves the processing node, so the processing speed and internal speed of the communication terminal from the external network and the communication terminal from the own network are different. The amount of traffic flowing through the network can be adjusted.
  • FIG. 1 shows the 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 a device that performs processing based on the usage status of the UE 90 from the edge 40 connected to its own network such as RAN (Regional Area Network) to a device connected to the core network, or performs processing.
  • the self network is a network operated by one communication carrier and in which the UE 90 is located.
  • the communication system 1 includes a node change device 10, an OSS / Operations Support System / Business Support System (BSS) 20, a Management & Orchestration (MANO) 30, an edge 40, an MME 50, and an SPGW 60. , A data center 70, an eNode 80, and a UE 90.
  • BSS Operations Support System
  • MME Management & Orchestration
  • the OSS / BSS (Operations Support System / Business Support System) 20, MANO (Management & Orchestration) 30, part of the edge 40, and the MME 50 constitute the core network of the communication system 1.
  • the data center 70 constitutes a wide area network (WAN). Also, 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 require transmission and reception of information to each other are connected by wire and wireless, and can transmit and receive information.
  • the UE 90 is a terminal including a smartphone and a tablet terminal, and can perform communication by communication connection with the communication system 1.
  • a service processing request is made from the UE 90 to the communication system 1
  • the edge 40 connected to the RAN, the edge 40 connected to the core network, and any device (node) of the data center 70 processes the service (application Processing is performed.
  • the distance from the UE 90 is shorter 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 three devices.
  • communication delay refers to an apparatus that processes according to a processing request from UE 90 (edge 40 connected to RAN, edge 40 connected to core network, data center 70), and UE 90. It is determined by the communication time.
  • the communication system 1 has nodes that perform 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) ) Share and save.
  • the differential data of the user data is copied to each other every predetermined period.
  • 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 edges 40 of the RAN execute processing near the UE 90, they are widely distributed in large numbers. On the other hand, since the data centers 70 are accessed from the external network, they are not dispersed as much because they are collectively processed. Therefore, although the edge 40 can provide processing results immediately to the UE 90 when all of the above services are executed, a large number of distributed results will result in increased installation costs and resource costs. On the other hand, since the data centers 70 are not dispersed as much, installation and resource costs can be reduced if the data centers 70 execute the above services in a centralized manner. However, because of the distance to the UE 90, processing time is longer than when the edge 40 performs a service.
  • the node change device 10 confirms the status of the device that processes the service request from the UE 90, and changes the device 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 issues an instruction related to the communication function in the communication system 1. For example, the OSS / BSS 20 instructs the MANO 30 to add a new communication function (communication service). In addition, the OSS / BSS 20 can be operated by a communication carrier related to the communication system 1.
  • the MANO 30 is configured to include an NFVO (Network Functions Virtualisation Orchestrator), a VNFM (Virtual Network Function Manager), and a VIM (Virtualized Infrastructure Management).
  • the NFVO is a general management node (functional entity) that manages the entire virtual network built on physical resources.
  • 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 physical resources (nodes). Specifically, management of allocation / update / collection of resources, association of physical resources with a virtualization network, and management of hardware resources and a list of SW resources (hypervisors) are performed.
  • NFVO, VNFM, and VIM are realized by executing a program on a physical server device (however, there is no limitation to what is realized on virtualization, and after separating the management system, , May be realized on virtualization).
  • the NFVO, the VNFM, and the 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.
  • SGW Serving Gate Way
  • PGW Packet Data Network Gate Way
  • the PGW is a gateway connected to the external network, and performs IP address delivery to the UE 90 and the like.
  • the MME 50 is a part that performs position management of the UE 90 located in the LTE network, authentication control, and setting processing of a communication path of user data.
  • 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 processes in response to a service request from the UE 90. It also stores various data.
  • the node change device 10 includes a placement information storage unit 11, a sequence monitoring unit 12 (use information acquisition means), a traffic monitoring unit 13 (use information acquisition means), and a placement calculation unit 14 (change means). And a placement instructing unit 15 (changing means).
  • FIG. 3 shows a hardware configuration of a server device that constitutes the node change device 10 according to the present embodiment.
  • the node change device 10 includes a CPU 101, a RAM (Random Access Memory) 102 and a ROM (Read Only Memory) 103 as main storage devices, a communication module 104 for communication, and assistance such as a hard disk. It is configured to include a computer including hardware such as the storage device 105.
  • the functions of the above-described node change device 10 are exhibited by operating these components by a program or the like.
  • the node change 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 related to the arrangement of devices that execute processing from the UE 90, such as determination information for changing the arrangement.
  • the arrangement information storage unit 11 stores information of a plurality of types of tables.
  • the arrangement information storage unit 11 includes a service policy table which is a table having information indicating a change condition of a node to be executed, an execution place management table having information of a place to execute a process, and a charging status of each user.
  • a charge management table having information to be shown, and a traffic information table having information indicating the use status from the external network side and the use status on the internal network side (self network side) are stored.
  • FIG. 4 shows an example of the service policy table.
  • 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 has transmitted the policy.
  • the service name is a name for identifying a service (for example, a name indicating a video distribution service, an ITS service, etc.).
  • a policy is information indicating a change condition of a 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 at a device other than the edge if it exceeds 300 yen. Further, the policy whose service name is service 5 indicates that edge usage is regulated when the processing load status exceeds 80%, and edge usage regulation 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 processing is moved from the edge processing to the data center, and returned from the data center to the edge at the time of the request. .
  • FIG. 5 shows an example of the execution place management table.
  • the execution place management table is a table for storing information having a service name, a place, and a user ID.
  • the service name is a name for identifying a service.
  • the place is information indicating a node that executes the service.
  • the user ID is information for identifying a user.
  • FIG. 5 with regard to the service 1, when a processing request is made from the UE 90 of a user whose user ID is the user 1, the user 2, and the user 3, processing is performed at the edge 1. Further, even in the same service 1, when the processing request is made from the UE of the user whose user ID is user 4 and user 5, the processing is performed in the data center 1. Thus, even for the same service, different nodes execute depending on users.
  • FIG. 6 shows an example of the charge management table.
  • the charging management table is a table for storing information having a user ID, a service name, and a charging status.
  • the user ID is information for identifying a user.
  • the service name is information for identifying a service.
  • the charging status is information indicating whether the charging 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.
  • FIG. 7 shows an example of the traffic information table.
  • the traffic information table has a service name, an execution device, a target user, traffic on the UE side (delay, bandwidth used), and traffic on the WAN side (delay, bandwidth used) It is a table for storing information.
  • the service name is information for identifying a service.
  • the execution device is information indicating a device that executes a process.
  • the target user is information for specifying the target user.
  • a user ID indicating a specific user and information indicating all users are input.
  • the traffic on the UE side indicates information of traffic that has been accessed from the internal network (average communication delay value, communication amount per second).
  • the traffic on the WAN side indicates information on traffic accessed from the external network.
  • the sequence monitoring unit 12 is a part that requests the MME 50 or the like to monitor the sequence, and acquires the monitoring result of the sequence from the MME 50 or the like. Specifically, the sequence monitoring unit 12 makes a monitoring request regarding charging, and makes a monitoring request regarding the type of line to be connected (for example, 4G, 5G).
  • the sequence monitoring unit 12 receives a monitoring instruction from the placement instructing unit 15, the monitoring instruction (for example, the user ID to be monitored and the service ID to the monitoring target device (for example, MME 50)) and information indicating the monitoring target policy Send out).
  • 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 the information on the usage status of the user. The sequence monitoring unit 12 sends the monitoring result to the placement calculation unit 14.
  • the traffic monitoring unit 13 is a part that requests traffic monitoring to a router / switch or the like and acquires traffic monitoring results from the router / switch or the like. Upon receiving the monitoring instruction from the placement instructing unit 15, the traffic monitoring unit 13 sends out a monitoring instruction (information indicating a user ID to be monitored, a service ID, and a policy) to the device to be monitored (for example, SPGW). Do.
  • a monitoring instruction information indicating a user ID to be monitored, a service ID, and a policy
  • the traffic monitoring unit 13 receives the monitoring result at a predetermined timing from the device that instructed the traffic monitoring. As described above, the traffic monitoring unit 13 receives the monitoring result as the information on the usage status of the user, and sends the monitoring result to the placement calculating unit 14.
  • the placement calculation unit 14 is a part that determines an apparatus that performs processing for the service request from the UE 90. When newly obtaining a service request from the UE 90, the placement calculation unit 14 determines an apparatus to be executed based on the policy.
  • the placement calculation unit 14 determines an apparatus (data center, edge of core network, edge of RAN) that executes a service based on the policy. That is, the placement calculation unit 14 determines the position at which the service is to be performed. When determining to execute on the edge connected to the RAN, the placement calculation unit 14 determines the edge closest to the UE 90 as the device to be executed, based on the position of the UE 90.
  • the arrangement calculation unit 14 receives the monitoring result from the sequence monitoring unit 12 or the traffic monitoring unit 13 and 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.
  • the placement calculation unit 14 changes the node that executes the request process from the communication terminal.
  • the processing target device (node) To be changed from the edge 40 to the edge 40 or data center 70 of the core node. That is, the placement calculation unit 14 determines to change to a node of a network having a long distance from the UE 90 as compared with the network of the node performing the request processing. After determining the device to be executed, the placement calculation unit 14 notifies the placement instruction unit 15 of the device to be processed.
  • the placement instructing unit 15 receives a device to be processed from the placement calculating 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.
  • the application related to the operation state includes a function of combining images outside the vehicle captured by a plurality of users, and a function of route search.
  • an application to be executed at an edge (edge application) and an application to be executed at a data center (server side application) are included as applications related to the operation state executed on the in-vehicle terminal I assume.
  • edge application processing is performed to display and output an image obtained by synthesizing the result of analysis of an image (for example, an image in front of the vehicle) indicating the operation status and the image.
  • the server side application server side
  • the UE 90B After 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, to be able to execute an edge application (step S2).
  • VM virtual machine
  • the edge 40 After activating the VM, 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 sends 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).
  • the edge 40 analyzes and combines the respective images (step S6).
  • the edge 40 transmits the synthesized image to the UE 90A and the UE 90B (step S7).
  • the UE 90A and the UE 90B perform AR (Augmented Reality) display on the received image (Steps S8 and S9).
  • 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 the request (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).
  • a function that requires immediacy such as display of a captured image
  • a function that does not require immediacy such as path search
  • the data center 70 sends a policy registration request to the OSS / BSS 20 together with the service name and the contents of the policy to which the policy is applied (step S21).
  • the OSS / BSS 20 issues a policy setting request to the node change device 10 (step S22).
  • the node change device 10 registers the service name to be the target of the policy and the content of the policy in the service policy table.
  • the node change device 10 notifies the OSS / BSS 20 that the registration has been completed (step S23).
  • the OSS / BSS 20 notifies the data center 70 of the notification (step S24).
  • step S 25 When an edge connection request is made from the UE 90 to the data center 70 (a request to execute a service to be executed in principle) (step S 25), the data center 70 notifies the OSS / BSS 20 of the service name and the address of the UE 90, and A creation request is made (step S26). The OSS / BSS 20 sends an edge creation request to the node change device 10 (step S27).
  • the node change device 10 refers to the service policy table corresponding to the service name (step S28, step S29).
  • the placement calculation unit 14 determines a device to be executed based on the contents of the service policy table (step S30). In addition, the placement calculation unit 14 also determines a monitoring target indicating the monitoring content (for example, service, user ID, charging status, etc.).
  • the layout calculation unit 14 of the node change device 10 registers, in the execution place management table, information in which the device to be executed and the user ID of the UE 90 that has made the service request are associated (Step S31 and Step S32).
  • the placement calculation unit 14 of the node change device 10 notifies the placement request unit 15 of a monitoring request and a placement request (step S33).
  • the placement instructing unit 15 notifies the MANO 30 of the service name and the address of the edge and makes a VM creation request in response to the placement request.
  • the MANO 30 In response to the VM creation request, the MANO 30 notifies the edge 40 of the requested device of the service name and makes a VM creation request (step S35).
  • the edge 40 prepares for VM activation and activates an edge application operating on the VM (step S36).
  • the edge 40 sends an edge application activation completion notification to the MANO 30 (step S37).
  • the MANO 30 sends an edge application activation completion notification to the node change device 10 (step S38).
  • the placement instructing unit 15 sends a monitoring instruction to the traffic monitoring unit 13 (step S39).
  • the traffic monitoring unit 13 issues a monitoring instruction to the target apparatus and issues the monitoring instruction to the placement instructing unit 15 (step S40).
  • the placement calculation unit 14 issues a monitoring instruction to the sequence monitoring unit 12 (step S41).
  • the sequence monitoring unit 12 issues a monitoring instruction to the target apparatus and issues the result of the monitoring instruction to the placement instructing unit 15 (step S42).
  • the placement instruction unit 15 notifies the placement calculation unit 14 of the placement completion (step S43). In response to this, the placement calculation unit 14 transmits connection information (address of connection destination) to the data center 70 (step S44). The data center 70 notifies the UE 90 of connection information (step S45), and the UE 90 connects to the edge 40 based on the connection information (step S46).
  • step S51 When the UE 90 makes an edge connection request through a router switch in the core network (step S51), the router switch transfers communication contents to the edge 40 (step S52).
  • the OSS / BSS 20 determines the charge status, and when the charge limit is reached, notifies the node change device 10 of the charge limit (step S53).
  • the sequence monitoring unit 12 notifies the allocation calculation unit 14 of the charging limit notification (step S54).
  • the node change device 10 refers to the service policy table, the execution place management table, and the charge management table (steps S55 and S56).
  • the placement calculation unit 14 determines the device to be executed based on the contents of the service policy table (step S57).
  • the placement calculation unit 14 also determines a monitoring target (for example, service, user ID, charging status, etc.).
  • the layout calculation unit 14 of the node change device 10 registers, in the execution location management table, information in which the device to be executed is associated with the user ID of the UE 90 that has made the service request, and updates the charge management table (step S58 and step S59).
  • the placement calculation unit 14 of the node change device 10 notifies the placement request unit 15 of a monitoring request and a placement request (step S60).
  • the placement instructing unit 15 notifies the MANO 30 of the service name and the address of the device of the change destination in response to the placement request, and makes a VM creation request (step S61).
  • the MANO 30 sets the distributed DB replication destination in the data center 70 which is the device of the change destination, and makes a registration request for user information (step S62). Also, the MANO 30 prohibits the subsequent update to the distributed DB of the change source device.
  • the data center 70 notifies the MANO 30 to that effect (step S63).
  • the MANO 30 sends a notification (VM consolidation) to the effect of changing the processing target to the edge 40 (step S64), and the edge 40 performs end processing (edge application activation end) according to this (step S65).
  • VM consolidation VM consolidation
  • end processing edge application activation end
  • the MANO 30 instructs the SPGW 60 to perform the flow switching (step S67), and the SPGW 60 performs the flow switching processing according to this, and notifies the MANO 30 of the processing completion (step S68). Also, a flow switching instruction is issued from the MANO 30 to the router switch (step S69). When switching is completed, the router switch notifies the MANO 30 (step S70). Thus, in response to the processing request from the UE 90, the MANO 30 sets the communication path so that the data center 70 performs the processing.
  • the MANO 30 notifies the arrangement instructing unit 15 of the completion of aggregation (step S71).
  • the placement instructing unit 15 instructs the sequence monitoring unit 12 to finish 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 finish monitoring (step S74), and receives a completion notification from the traffic monitoring unit 13 (step S75). Thereafter, the arrangement instructing unit 15 notifies the arrangement calculating unit 14 that the rearrangement is completed (step S76).
  • the router switch when the UE 90 makes a server application communication request via the router switch (step S 77), the router switch notifies the SPGW, and in response, the SPGW transmits the data center 70 via the router switch. (Step S79, step S80).
  • the data center 70 requests the distributed DB of the edge 40 to read user data (step S 81), and acquires 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.
  • step S57 shown in FIG. 10 a process of the movement calculation performed by the placement calculation unit 14 (step S57 shown in FIG. 10) will be described using the flowchart shown in FIG.
  • the placement calculation unit 14 always waits for a movement change event (step S91). When the notification of an event is received, the process after step S92 is performed. When a charge event occurs, such as when the sequence monitoring unit 12 receives a charge limit notification (step S92; YES), the charge management table is updated (step S93). It is determined whether the processing apparatus is the edge 40 or the data center 70 (step S94). If the processing device is the edge 40, a charging event has occurred, and if a charging limit notification has been received (step S95; YES), the process moves to step S97.
  • a charge event occurs, such as when the sequence monitoring unit 12 receives a charge limit notification (step S92; YES)
  • the charge management table is updated (step S93). It is determined whether the processing apparatus is the edge 40 or the data center 70 (step S94). If the processing device is the edge 40, a charging event has occurred, and if a charging limit notification has been received (step S95; YES), the process moves to step S97.
  • step S96 If the charging limit notification has not been received, and if 3G or 4G has not been transitioned (step S96; NO), the process proceeds to step S91 without changing the processing device. If the charging limit notification has not been received, and if the line type has transitioned to 3G or 4G (step S96; YES), the process moves to step S97. In step S97, the placement calculation unit 14 determines to move to the data center 70 (step S97).
  • step S98 If the device currently being processed is the data center 70, the process moves to step S98, and if it does not transition to 5G (step S98; NO), the process moves to step S91. If it has transitioned to 5G (step S98; YES), if it has reached the charging limit (step S99; NO), it moves to step S91 without changing the processing device, and if it has not reached the charging limit (step S99; YES), to move to the edge 40, is determined (step S100).
  • the router / switch 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 the traffic of communication for the edge 40 (step S113).
  • the traffic monitoring unit 13 receives an update request for traffic information and an update completion notification based on the notification (step S114, step S115).
  • the UE 90B (terminal WAN), which is an external terminal (terminal connected via an external network), requests the router / switch to process the edge 40 via the data center 70 (step S116).
  • the router switch connects to the edge 40 accordingly (step S117).
  • the router / switch notifies the traffic monitoring unit 13 of the traffic of the communication for the edge 40 (step S118).
  • the traffic monitoring unit 13 receives an update request for traffic information and an update completion notification based on the notification (steps S119 and S120).
  • the traffic monitoring unit 13 periodically compares the traffic on the UE side acquired in step S113 with the traffic on the WAN side acquired in step S118, and conditions such as when there is a difference greater than or equal to a predetermined threshold value Is notified to the layout calculation unit 14 (step S121).
  • the placement calculation unit 14 requests the placement information storage unit 11 to obtain the service policy table and the traffic information table (step S122), and obtains the service policy table and the traffic information table from the placement information storage unit 11 (step S123). .
  • the placement calculation unit 14 changes the processing device based on the result of comparison between the traffic on the UE side and the traffic on the WAN side (step S124).
  • the placement calculation unit 14 requests update of the execution place management table and the traffic information table (step S125), and when the update result is received (step S126), the relocation / monitoring destination / change notification is sent to the placement instruction unit 15.
  • the operation is performed (step S127).
  • the process of step S128 to step S145 is the process of step S61 to step of FIG. 10 except that the process (step S67 and step S68 of FIG. 10) of the flow switching instruction between MANO 30 and SPGW is not included in the sequence of FIG. The description is omitted because it is the same as S82.
  • step S124 shown in FIG. 12 The process (step S124 shown in FIG. 12) in which the placement calculation unit 14 makes a movement determination will be described using the flowchart shown in FIG.
  • the placement calculation unit 14 always waits for a movement change event (step S151).
  • the notification from the traffic monitoring unit 13 is received, it is checked which of the two has more bandwidth usage (that is, the amount of communication per second) (step S152).
  • the DC (data center 70) side is changed to the DC (data center 70) side in a range that satisfies the delay request (step S153). If there are more UEs, the UE is changed to the UE side in a range satisfying the delay request (step S154).
  • the change to the DC side means a change from the edge 40 of the RAN to the edge 40 of the core network or the data center 70 or a change from the edge 40 of the core network to the data center 70.
  • the change to the UE side refers to 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.
  • the placement calculation unit 14 determines a change destination in a range that satisfies the delay request based on a preset threshold value of the delay time. The placement calculation unit 14 determines whether the delay time on the UE side of the edge to be changed in the traffic information table is less than or equal to the threshold and determines whether the delay request is satisfied.
  • FIG. 14 shows an example of moving to the data center 70 when the operation is performed at the edge 40.
  • the use band is larger on the WAN side.
  • the edge 40 is changed to the data center 70 as shown in FIG.
  • the OSS / BSS 20 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).
  • the OSS / BSS 20 receives the information indicating the processing load status from the data center 70 and the edge 40, it stores the information indicating the processing load status for each device (location) in the processing load status table as shown in FIG. .
  • the OSS / BSS 20 stores a processing load situation table in which places and processing load situations are associated with each other.
  • the processing load status is information indicating the resource usage rate.
  • Edge 1 Since Edge 1 has a processing load status of 30%, it has room to newly accept a processing request from UE 90. However, since Edge 2 has a processing load status of 90%, Edge 2 newly receives a request from UE 90. There is not enough time to receive the processing request.
  • step S30A the placement calculation unit 14 determines the device to be executed (edge 40) based on the contents of the service policy table, and if the policy of the service 5 of the service policy table is valid, the OSS / BSS 20 is selected. Then, the processing load status of the edge 40 is inquired. The arrangement calculating unit 14 determines that the data center 70 is to execute the processing load condition if the processing load condition is to be restricted based on the condition of the policy. For example, in the case where the edge 40 to be inquired is the edge 2 in the example shown in FIG. 16, since the processing load situation is 90%, it is a restriction object. Furthermore, the placement calculation unit 14 sets the edge 40 initially determined as a monitoring target.
  • step S33A the placement calculation unit 14 notifies the placement instructing unit 15 of the device to be executed (data center 70) and the monitoring target.
  • the placement instructing unit 15 requests the MANO 30 to create a VM (step S34).
  • the placement instructing unit 15 causes the OSS / BSS 20 to monitor the edge 40 to be monitored via the MANO 30.
  • the MANO 30 requests the data center 70 to create a VM (step S35A), and the data center 70 starts a VM activation / edge application (step S36A).
  • the edge application activation is completed, the data center 70 notifies the MANO 30 to that effect (step S37A).
  • the data center 70 may activate the VM and the edge application in advance.
  • the deployment instruction unit 15 causes the data center 70 to process the request processing from the UE 90, so when the UE 90 makes a connection request (step S46A), the deployment instruction unit 15 connects with the data center 70 via the SPGW.
  • FIG. 17 An example of processing of moving a VM from the data center 70 to the edge 40 (processing of changing a VM for executing a processing request from the UE 90 from the data center 70 to the edge 40) will be described using FIG.
  • the process shown in FIG. 17 will be described focusing on parts different from the process of FIG.
  • step S51 When a processing request is issued from the UE 90 (step S51), the connection is made to the data center 70 via the router / switch via the SPGW (step S52A).
  • the edge 40 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).
  • the OSS / BSS 20 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 placement calculation unit 14 that the processing load status has fallen below 70% (step S54A).
  • the MANO 30 requests the edge 40 to set a DB replication destination (step S62A).
  • the edge 40 notifies the MANO 30 of DB replication setting completion (step S63A), and the edge 40 further activates the VM and the edge application (step S65A).
  • the flow is switched (steps S67 to S70)
  • the UE 90 makes a connection request, the UE 90 is connected to the edge 40 (step S77A, step S80).
  • the usage status of the device (the edge 40 in the above example) other than the device (the above example, the data center 70) executing the request processing from the UE 90 is monitored, and according to the usage state , VM may be moved from data center 70 to edge 40.
  • the VM may be moved from the edge 40 to the data center 70 based on the policy of the service 6. For example, after it is determined that the edge 40 performs the request process from the UE 90, the edge 40 may not transmit or receive data from the UE 90 to the edge 40 as a result of monitoring the process request from the UE 90. Move the VM from the data center to the data center 70.
  • the OSS / BSS 20 detects that the processing request has been made from the UE 90, the OSS / BSS 20 notifies the placement calculation unit 14 of the node change device 10.
  • the placement calculation unit 14 changes the data center 70 to an edge 40.
  • the VM change may be determined based on the strict / loose condition of the data communication delay required for the service.
  • the VM may be changed from the edge 40 to the data center 70 based on the service utilization state of the UE 90 (the request processing state from the UE 90 to the edge 40), or from the data center 70 to the edge 40 May be changed.
  • the VM is moved from the edge 40 of the RAN to the data center 70 based on the charging limit notification, but may be moved from the edge 40 of the RAN to the edge 40 of the core network .
  • the function of the node change device 10 may be realized by a plurality of server devices.
  • the node change device 10 uses the MANO 30 for information on the number of CPUs, memory amount, disk amount (disk capacity) of the move destination node, number of communication terminals connected to the move destination node / number of sessions and NW band The acquired information is compared with a preset threshold to determine whether the node can be moved to the destination node.
  • the node change device 10 requires a node which is required for the movement destination node to perform processing (for example, SPGW 60, local gateway (LGW), DPI (Deep Packet Inspection), DNS ( Even if information indicating the load amount of Domain Name Server) is acquired from MANO 30, and the acquired information is compared with a preset threshold value to determine whether or not the node can be moved to the destination node. Good. If the above destination node is not a virtualized node required to perform processing, each destination node can manage the load amount, or a management system dedicated to mobile edge computers The above-mentioned load may be managed by (a system different from MANO 30).
  • a node which is required for the movement destination node to perform processing for example, SPGW 60, local gateway (LGW), DPI (Deep Packet Inspection), DNS ( Even if information indicating the load amount of Domain Name Server) is acquired from MANO 30, and the acquired information is compared with a preset threshold value to determine whether or not the node can be moved to the
  • the node changing device 10 may use the base station device or the information of the capacity of the radio equipment (the utilization rate of the radio resource block, the CPU utilization rate of the base station device, etc.) in the destination node. Acquired from MANO30 (when the base station device is managed on a virtualization basis), compare the acquired information with a preset threshold value, and judge whether it is possible to move to the destination node It is also good.
  • the low priority application allocated to the destination node is moved to another node Move it again.
  • the SPGW 60, DNS, etc. can be expanded by scaling out, scaling up, etc. Move after augmentation.
  • the sequence monitoring unit 12 acquires information (for example, charging limit notification) indicating the usage state of the first node (for example, the edge 40 connected to the RAN) by the UE 90.
  • the placement calculation unit 14 changes the node performing the request process from the UE 90 from the edge 40 connected to the RAN to the data center 70 (a second node having a different network hierarchy) based on the charging upper limit notification.
  • the edge 40 executes the 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.
  • the node that executes the request processing of the UE 90 is changed to a node of another network based on the usage information, so that cost and speed can be balanced according to the usage state.
  • the edge 40 which is the node before the change, and the data center 70, which is the node after the change, have different types of connected networks.
  • the edge 40 is connected to the RAN, and the data center 70 is connected to the WAN.
  • the edge 40 connected to the RAN has a shorter communication delay than the data center 70 because the edge 40 connected to the RAN is closer to the UE 90 than the data center 70 connected to the WAN.
  • cost and speed can be balanced by changing the device that executes the request process from the UE 90 according to the usage state.
  • the arrangement calculating unit 14 compares it with the network (RAN) of the node performing the request processing. Then, the distance from the UE 90 is changed to the data center 70 connected to a long network (WAN). As described above, since the nodes are changed to nodes of networks having different hierarchies based on the use state, the processing load and the use bandwidth amount of the network can be distributed.
  • 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.
  • the placement calculation unit 14 determines the node that executes the request process from the UE 90 based on the result of comparing the usage information indicating the usage status of the UE 90 via the WAN with the usage information indicating the usage status of the UE 90 by the RAN. Switch to the network node of. As a result, the processing node is moved by comparing the use state of the external network and the own network, and therefore, the processing speed of each of the communication terminal from the external network and the communication terminal from the own network can be adjusted.
  • Software may be called software, firmware, middleware, microcode, hardware description language, or any other name, and may be instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules. Should be interpreted broadly to mean applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc.
  • software, instructions, etc. may be sent and received via a transmission medium.
  • software may use a wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission medium.
  • wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave
  • data, instructions, commands, information, signals, bits, symbols, chips etc may be voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any of these May be represented by a combination of
  • the channels and / or symbols may be signals.
  • the signal may be a message.
  • the component carrier (CC) may be called a carrier frequency, a cell or the like.
  • system and "network” as used herein are used interchangeably.
  • radio resources may be indexed.
  • a base station can accommodate one or more (e.g., three) cells (also called sectors). If the base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small base station RRH for indoor use: Remote Communication service can also be provided by Radio Head.
  • the terms “cell” or “sector” refer to a part or all of the coverage area of a base station and / or a base station subsystem serving communication services in this coverage.
  • base station “eNB”, “cell” and “sector” may be used interchangeably herein.
  • a base station may be called in terms of a fixed station (Node station), NodeB, eNodeB (eNB), access point (access point), femtocell, small cell, and the like.
  • the mobile station may be a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, by those skilled in the art. It may also be called a terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.
  • determining encompass a wide variety of operations.
  • “Judgment”, “decision” are, for example, judging, calculating, calculating, processing, processing, deriving, investigating, looking up (for example, a table) (Searching in a database or another data structure), ascertaining may be regarded as “decision”, “decision”, etc.
  • “determination” and “determination” are receiving (e.g. receiving information), transmitting (e.g. transmitting information), input (input), output (output), access (accessing) (for example, accessing data in a memory) may be regarded as “judged” or “decided”.
  • connection means any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements that are “connected” or “coupled”.
  • the coupling or connection between elements may be physical, logical or a combination thereof.
  • the two elements are by using one or more wires, cables and / or printed electrical connections, and radio frequency as some non-limiting and non-exclusive examples. It can be considered “connected” or “coupled” to one another by using electromagnetic energy such as electromagnetic energy having wavelengths in the region, microwave region and light (both visible and invisible) regions.
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to an element using the designation "first,” “second,” etc. as used herein does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient way of distinguishing between two or more elements. Thus, reference to the first and second elements does not mean that only two elements can be taken there, or that in any way the first element must precede the second element.
  • each of the above-described devices may be replaced with a “unit”, a “circuit”, a “device” or the like.
  • notification of information is not limited to the aspect / embodiment described in the present specification, and may be performed by another method.
  • notification of information may be physical layer signaling (for example, Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message, or the like.
  • each aspect / embodiment described in the present specification is 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)
  • the present invention may be applied to a system utilizing Bluetooth), another appropriate system, and / or an advanced next-generation system based on these.
  • the specific operation supposed to be performed by the base station in this specification may be performed by its upper node.
  • the various operations performed for communication with the terminals may be the base station and / or other network nodes other than the base station (eg, It is clear that it may be performed by MME or S-GW etc but not limited to these).
  • MME Mobility Management Entity
  • S-GW Serving Mobility Management Entity
  • the above information and the like may be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input and output may be performed via a plurality of network nodes.
  • the input / output information or the like may be stored in a specific place (for example, a memory) or may be managed by a management table. Information to be input or output may be overwritten, updated or added. The output information etc. may be deleted. The input information may be deleted. The input information or the like may be transmitted to another device.
  • the determination may be performed by a value (0 or 1) represented by one bit, may be performed by a boolean value (Boolean: true or false), or may be compared with a numerical value (for example, a predetermined value). Comparison with the value).
  • notification of predetermined information is not limited to what is explicitly performed, but is performed by implicit (for example, not notifying of the predetermined information) It is also good.
  • SYMBOLS 1 Communication system, 10 ... Node change apparatus, 11 ... Placement information storage part, 12 ... Sequence monitoring part, 13 ... Traffic monitoring part, 14 ... Placement calculation part, 15 ... Placement 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Provided are a control method and a control device that can appropriately change the device, on a network, that executes processing requested by a terminal. According to the present invention, a sequence-monitoring unit 12 of a node-changing device 10 acquires information (for example, a maximum charges notification) that indicates the usage state of a node by UE 90. On the basis of the maximum charges notification, an arrangement-calculating unit 14 changes the node that executes processing requested by the UE 90 from an edge 40 that is connected to a RAN to data center 70. As a result, because usage information is used to change processing to a node on separate network, cost and speed can be balanced in accordance with degree of use.

Description

制御方法及び制御装置Control method and control device
　本発明は、制御方法及び制御装置に関する。 The present invention relates to a control method and control device.
　従来から、ネットワーク上においてスマートフォンなど端末の近くにあるエッジサーバに処理を分散させることで、地球規模で集中的配備されたクラウドコンピューティングの環境と比べて通信遅延を短縮するエッジコンピューティングという技術が考えられている（非特許文献１）。 Conventionally, by distributing processing to edge servers close to terminals such as smartphones on the network, there is a technology called edge computing that reduces communication delay compared to a globally deployed cloud computing environment on a global scale. It is considered (nonpatent literature 1).
　上述のように、エッジサーバが、端末の近くで処理をすることを想定しているので、より多くの場所にエッジサーバを設置する必要がある。よって、使用状態によらずにエッジサーバで実行するサービス（アプリケーション）のためのリソースを確保してしまうと、当該リソースが無駄になってしまう可能性がある。一方、集中的に配備されたクラウドネットワーク上のデータサーバで処理をすると、低遅延で処理を実現することが困難になる。 As mentioned above, since the edge server assumes processing near the terminal, it is necessary to install the edge server in more places. Therefore, if resources for services (applications) to be executed by the edge server are secured regardless of the use state, the resources may be wasted. On the other hand, if processing is performed by a centralizedly deployed data server on a cloud network, it becomes difficult to realize processing with low delay.
　そこで、本発明は、上記問題点を解決するために、端末からの要求処理を実行するネットワーク上の装置を適切に変更することができる制御方法及び制御装置を提供することを目的とする。 Therefore, it is an object of the present invention to provide a control method and a control device capable of appropriately changing an apparatus on a network that executes request processing from a terminal in order to solve the above-mentioned problems.
　上記目的を達成するために、本発明の一実施形態に係る制御方法は、通信端末の通信を行う通信システムの制御方法において、通信端末による要求処理を実行する第１ノードの使用状態を示す情報に応じ、若しくは、第１ノードと異なるネットワーク階層に位置する第２ノードの使用状態を示す情報に応じ、若しくは、通信端末のサービス利用状態を示す情報に応じ、第１ノードと、第２ノードとの間で、前記通信端末からの要求処理を実行するノードを変更する。 In order to achieve the above object, a control method according to an embodiment of the present invention is, in a control method of a communication system that performs communication of communication terminals, information indicating a use state of a first node that executes request processing by the communication terminals. Or according to the information indicating the use state of the second node located in the network layer different from the first node, or according to the information indicating the service use state of the communication terminal, the first node and the second node Between the nodes, the node executing 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 which performs communication of the communication terminal, and according to the information indicating the usage state of the first node which executes the request processing by the communication terminal, Between the first node and the second node according to the information indicating the use state of the second node located in the network layer different from the first node, or according to the information indicating the service use state of the communication terminal, Change the node that executes the request processing from the communication terminal.
　上記の発明によれば、通信端末による要求処理を実行する第１ノードの使用状態等に基づいて、通信端末の要求処理を実行するノードを別ネットワーク階層のノードに変更するので、使用状態に応じて、コストと速度とのバランスを取ることができる。 According to the above invention, the node executing the request processing of the communication terminal is changed to a node of another network layer based on the usage state of the first node executing the request processing by the communication terminal, etc. 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, cost and speed can be balanced by executing request processing from the communication terminal at nodes of different networks depending on the use state.
　また、上記の制御方法及び制御装置では、第１ノードと、第２ノードとの間で、通信端末からの要求処理を実行するノードを変更するとは、通信端末からの要求処理を実行する仮想マシンがあるノードを変更することとしてもよい。この場合、仮想化ネットワークにおいて、コストと速度とのバランスを取ることができる。 Further, in the above control method and control apparatus, changing the node that executes the request processing from the communication terminal between the first node and the second node means that the virtual machine executes the request processing from the communication terminal. It is also possible to change a certain node. In this case, cost and speed can be balanced in the virtualization network.
　また、上記の制御方法は、第１ノードは、仮想マシンを起動し、第１ノードで実行するためのアプリケーションを実行できる状態にして、通信端末からの要求処理を実行し、通信端末からの要求処理を実行するノードを変更するとは、第１ノードの仮想マシンを、第２ノードへ移動させ、当該アプリケーションを第２ノードの仮想マシンで実行させることとしてもよい。このように、第１ノードの仮想マシンを、第２ノードへ移動させ、当該アプリケーションを第２ノードの仮想マシンで実行させることにより、コストと速度とのバランスを取ることができる。 Further, in the above control method, the first node starts a virtual machine, enables execution of an application for execution on the first node, executes request processing from the communication terminal, and requests from the communication terminal Changing the node that executes processing may move the virtual machine of the first node to the second node and cause the application to be executed by the virtual machine of the second node. Thus, 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, it is possible to balance the cost and the speed.
　また、上記の制御方法及び制御装置は、通信端末による要求処理を実行する第１ノードの使用状態を示す情報、若しくは、第１ノードと異なるネットワーク階層に位置する第２ノードの使用状態を示す情報、若しくは、通信端末のサービス利用状態を示す情報の何れかの情報が予め定められた条件を満たす場合、第１ノードと、第２ノードとの間で、通信端末からの要求処理を実行するノードを変更してもよい。この場合、使用状態に基づいてネットワーク階層が異なるノードに変更するので、処理負荷を分散させることができる。 Further, the control method and the control device described above may be information indicating the use state of the first node that executes the request processing by the communication terminal, or information indicating the use state of the second node located in a different network layer from the first node. Alternatively, if any of the information indicating the service use state of the communication terminal satisfies a predetermined condition, the node that executes request processing from the communication terminal between the first node and the second node May be changed. In this case, the processing load can be distributed because the network hierarchy is changed to a different node based on the usage state.
　また、上記の制御方法及び制御装置では、第１ノード及び前記第２ノードの何れかは、通信端末が在圏するネットワークである自己ネットワークに属し、他方のノードは、自己ネットワークとは異なるネットワークである外部ネットワークに属し、外部ネットワークを介した端末である外部端末による使用状態を示す使用情報と、自己ネットワークを介した端末である内部端末による使用状態を示す使用情報とを取得する。そして、制御方法及び制御装置は、外部端末の使用状態を示す使用情報と、内部端末の使用状態を示す使用情報とを比較した結果に基づいて、通信端末からの要求処理を実行するノードを第１ノードと第２ノードとの間で変更してもよい。この場合、通信制御装置は、外部ネットワークと自己ネットワークの使用状態を比較して、処理ノードを移動させるので、外部ネットワークからの通信端末と、自己ネットワークからの通信端末とのそれぞれの処理速度や内部ネットワークを流れる通信量を調整することができる。 Further, in the above control method and control device, one of the first node and the second node belongs to a self network which is a network in which the communication terminal is located, and the other node is a network different from the self network. Usage information that belongs to a certain external network and indicates usage by an external terminal that is a terminal via the external network and usage information that indicates usage by an internal terminal that is a terminal via the own network is acquired. Then, the control method and the control device are configured to execute the request processing from the communication terminal based on the result of comparing the usage information indicating the usage status of the external terminal with the usage information indicating the usage status of the internal terminal. It may be changed between one node and the second node. In this case, the communication control device compares the use state of the external network and the own network, and moves the processing node, so the processing speed and internal speed of the communication terminal from the external network and the communication terminal from the own network are different. The amount of traffic flowing through the network can be adjusted.
　本発明の一実施形態によれば、端末からの要求処理を実行するネットワーク上の装置を適切に変更することができる。 According to one embodiment of the present invention, it is possible to appropriately change the device on the network that executes the request processing from the terminal.
本発明の実施形態に係るシステムの構成を示す図である。It is a figure showing composition of a system concerning an embodiment of the present invention. 本発明の実施形態に係るノード変更装置を示すブロック図である。It is a block diagram showing a node change device concerning an embodiment of the present 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 a charge 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 edge starting processing. エッジからデータセンタへ処理装置を変更するシーケンス図である。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 zone | band 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 will be denoted by the same reference symbols, without redundant description.
　図１に本実施形態に係るノード変更装置１０（通信制御装置）を含む通信システム１の構成を示す。通信システム１は、ＵＥ９０の使用状況に基づいて処理をする装置をＲＡＮ（Regional Area Network）等の自己ネットワークに接続されているエッジ４０からコアネットワークに接続されている装置に移動したり、処理をする装置をデータセンタ７０からエッジ４０に移動したりするシステムである。ここで自己ネットワークとは、一つの通信事業者により運用され、ＵＥ９０が在圏するネットワークである。 FIG. 1 shows the 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 a device that performs processing based on the usage status of the UE 90 from the edge 40 connected to its own network such as RAN (Regional Area Network) to a device connected to the core network, or performs processing. Device from the data center 70 to the edge 40. Here, the self network is a network operated by one communication carrier and in which the UE 90 is located.
　図１に示すように通信システム１は、ノード変更装置１０と、ＯＳＳ／ＢＳＳ（Operations Support System／Business Support System）２０と、ＭＡＮＯ（Management & Orchestration）３０と、エッジ４０と、ＭＭＥ５０と、ＳＰＧＷ６０と、データセンタ７０と、ｅＮｏｄｅ８０と、ＵＥ９０とを含んで構成されている。 As shown in FIG. 1, the communication system 1 includes a node change device 10, an OSS / Operations Support System / Business Support System (BSS) 20, a Management & Orchestration (MANO) 30, an edge 40, an MME 50, and an SPGW 60. , A data center 70, an eNode 80, and a UE 90.
　このうち、ＯＳＳ／ＢＳＳ（Operations Support System／Business Support System）２０と、ＭＡＮＯ（Management & Orchestration）３０と、エッジ４０の一部と、ＭＭＥ５０とは、通信システム１のコアネットワークを構成するものである。ｅＮｏｄｅ８０とエッジ４０との一部がＲＡＮを構成するものである。データセンタ７０は、ＷＡＮ（Wide Area Network）を構成する。また、データセンタ７０は、ＷＡＮのような外部ネットワーク（上記自己ネットワークとは異なるネットワーク）を介して接続することができる。互いに情報の送受信が必要な構成要素間は、有線・無線により接続されており情報の送受信が可能となっている。 Among them, the OSS / BSS (Operations Support System / Business Support System) 20, MANO (Management & Orchestration) 30, part of the edge 40, and the MME 50 constitute the core network of the communication system 1. . Part of the eNode 80 and the edge 40 constitute a RAN. The data center 70 constitutes a wide area network (WAN). Also, 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 require transmission and reception of information to each other are connected by wire and wireless, and can transmit and receive information.
　ＵＥ９０は、スマートフォン、タブレット端末を含む端末であり、この通信システム１と通信接続することにより通信を行うことができる。ＵＥ９０から通信システム１へサービス処理要求をすると、ＲＡＮに接続されているエッジ４０、コアネットワークに接続されているエッジ４０、及びデータセンタ７０の何れかの装置（ノード）により当該サービスの処理（アプリケーションの処理）がなされる。 The UE 90 is a terminal including a smartphone and a tablet terminal, and can perform communication by communication connection with the communication system 1. When a service processing request is made from the UE 90 to the communication system 1, the edge 40 connected to the RAN, the edge 40 connected to the core network, and any device (node) of the data center 70 processes the service (application Processing is performed.
　ＲＡＮに接続されているエッジ４０、コアネットワークに接続されているエッジ４０、外部ネットワークに接続しているデータセンタ７０の順にＵＥ９０からの距離が短い。よって、距離が短いＲＡＮに接続されているエッジ４０は、上記３つの装置の中で通信遅延が最も小さい。ここで通信遅延とは、ＵＥ９０からの処理要求に応じて処理をする装置（ＲＡＮに接続されているエッジ４０、コアネットワークに接続されているエッジ４０、データセンタ７０）と、ＵＥ９０との間における通信時間により定められるものである。このように、通信システム１は、ＵＥ９０までの距離が互いに異なる複数のネットワークでＵＥ９０からの要求処理を実行するノードを有する。ＲＡＮに接続されているエッジ４０、コアネットワークに接続されているエッジ４０、及びデータセンタ７０は、それぞれ分散データベース（分散ＤＢ）を有しており、サービス実行時のユーザデータ（ユーザ設定等のデータ）を共有して保存している。所定期間毎に互いにユーザデータの差分データを複製する。 The distance from the UE 90 is shorter 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 three devices. Here, communication delay refers to an apparatus that processes according to a processing request from UE 90 (edge 40 connected to RAN, edge 40 connected to core network, data center 70), and UE 90. It is determined by the communication time. Thus, the communication system 1 has nodes that perform 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) ) Share and save. The differential data of the user data is copied to each other every predetermined period.
　また、ＲＡＮに接続されているエッジ４０、コアネットワークに接続されているエッジ４０、及びＷＡＮ（外部ネットワーク）に接続されているデータセンタ７０は、互いに異なる階層（種類）のネットワークに接続されている。ＲＡＮのエッジ４０は、ＵＥ９０の近くの位置で処理を実行するので、広範囲に多数分散している。一方、データセンタ７０は、外部ネットワークからアクセスされるので、統括して処理をするため、それほど分散していない。よって、エッジ４０が、上記のサービスを全て実行すると、ＵＥ９０へ即時に処理結果を提供できるが、多数分散しているため、設置コスト・リソースコストがかかってしまう。一方、データセンタ７０は、それほど分散していないため、データセンタ７０が、上記サービスを集約して実行すれば、設置コスト・リソースコストを抑えることができる。しかし、ＵＥ９０との距離があるため、エッジ４０がサービスを実行する場合より処理時間がかかる。 In addition, 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 edges 40 of the RAN execute processing near the UE 90, they are widely distributed in large numbers. On the other hand, since the data centers 70 are accessed from the external network, they are not dispersed as much because they are collectively processed. Therefore, although the edge 40 can provide processing results immediately to the UE 90 when all of the above services are executed, a large number of distributed results will result in increased installation costs and resource costs. On the other hand, since the data centers 70 are not dispersed as much, installation and resource costs can be reduced if the data centers 70 execute the above services in a centralized manner. However, because of the distance to the UE 90, processing time is longer than when the edge 40 performs a service.
　ノード変更装置１０は、ＵＥ９０からのサービス要求に対する処理をする装置の状況を確認し、当該状況に基づいて実行している装置の変更を行う。詳細は後述する。 The node change device 10 confirms the status of the device that processes the service request from the UE 90, and changes the device 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 issues an instruction related to the communication function in the communication system 1. For example, the OSS / BSS 20 instructs the MANO 30 to add a new communication function (communication service). In addition, the OSS / BSS 20 can be operated by a communication carrier related to the communication system 1.
　ＭＡＮＯ３０は、ＮＦＶＯ(Network Functions Virtualisation Orchestrator)と、ＶＮＦＭ(Virtual Network Function Manager)と、ＶＩＭ(Virtualised Infrastructure Management: 仮想化基盤管理)とを含んで構成されている。ＮＦＶＯは、物理資源上に構築された仮想ネットワーク全体の管理を行う全体管理ノード（機能エンティティ）である。ＶＮＦＭは、物理資源（ノード）に対して、サービスに係る機能を追加する仮想通信機能管理ノード（機能エンティティ）である。物理資源（ノード）各々を管理する物理資源管理ノード（機能エンティティ）である。具体的には、資源の割当・更新・回収の管理、物理資源と仮想化ネットワークとの関連付け、ハードウェア資源とＳＷ資源（ハイパーバイザー）一覧の管理を行う。 The MANO 30 is configured to include an NFVO (Network Functions Virtualisation Orchestrator), a VNFM (Virtual Network Function Manager), and a VIM (Virtualized Infrastructure Management). The NFVO is a general management node (functional entity) that manages the entire virtual network built on physical resources. 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 physical resources (nodes). Specifically, management of allocation / update / collection of resources, association of physical resources with a virtualization network, and management of hardware resources and a list of SW resources (hypervisors) are performed.
　なお、ＮＦＶＯ、ＶＮＦＭ及びＶＩＭは、物理的なサーバ装置上でプログラムが実行されることにより実現される（但し仮想化上で実現されることを制限するものでは無く、管理系統を分離した上で、仮想化上で実現してもよい）。ＮＦＶＯ、ＶＮＦＭ及びＶＩＭは、それぞれ別々の物理的なサーバ装置で実現されていてもよいし、同じサーバ装置で実現されていてもよい。ＮＦＶＯ、ＶＮＦＭ及びＶＩＭ（を実現するためのプログラム）は、別々のベンダから提供されていてもよい。 Note that NFVO, VNFM, and VIM are realized by executing a program on a physical server device (however, there is no limitation to what is realized on virtualization, and after separating the management system, , May be realized on virtualization). The NFVO, the VNFM, and the 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.
　ＳＰＧＷ６０は、ＳＧＷ又はＰＧＷである。ＳＧＷ（Serving Gate Way）は、ＬＴＥを収容する在圏パケット交換機で、ＰＧＷ（Packet data network Gate Way）との間でユーザデータの送受信を行う。ＰＧＷは、外部ネットワークと接続するゲートウェイであり、ＵＥ９０へのＩＰアドレス払出しなどを行う。 The SPGW 60 is an SGW or a PGW. SGW (Serving Gate Way) is a serving packet switch accommodating LTE, and transmits / receives user data to / from Packet Data Network Gate Way (PGW). The PGW is a gateway connected to the external network, and performs IP address delivery to the UE 90 and the like.
　ＭＭＥ５０は、ＬＴＥネットワークに在圏するＵＥ９０の位置管理、認証制御、及びユーザデータの通信経路の設定処理を行う部分である。 The MME 50 is a part that performs position management of the UE 90 located in the LTE network, authentication control, and setting processing of a communication path of user data.
　エッジ４０は、ＵＥ９０からのサービス要求に応じて、処理をするサーバ装置である。 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 processes in response to a service request from the UE 90. It also stores various data.
　引き続いて、ノード変更装置１０について、本実施形態に係る機能を、図２を用いて説明する。図２に示すようにノード変更装置１０は、配置情報記憶部１１と、シーケンス監視部１２（使用情報取得手段）と、トラヒック監視部１３（使用情報取得手段）と、配置計算部１４（変更手段）と、配置指示部１５（変更手段）と、を有する。 Subsequently, functions of the node change device 10 according to the present embodiment will be described with reference to FIG. As shown in FIG. 2, the node change device 10 includes a placement information storage unit 11, a sequence monitoring unit 12 (use information acquisition means), a traffic monitoring unit 13 (use information acquisition means), and a placement calculation unit 14 (change means). And a placement instructing unit 15 (changing means).
　ここで、図３に本実施形態に係るノード変更装置１０を構成するサーバ装置のハードウェア構成を示す。図３に示すように当該ノード変更装置１０は、ＣＰＵ１０１、主記憶装置であるＲＡＭ（Random Access Memory）１０２及びＲＯＭ（Read Only Memory）１０３、通信を行うための通信モジュール１０４、並びにハードディスク等の補助記憶装置１０５等のハードウェアを備えるコンピュータを含むものとして構成される。これらの構成要素がプログラム等により動作することにより、上述するノード変更装置１０の機能が発揮される。なお、ノード変更装置１０は複数のサーバ装置からなるコンピュータシステムによって構成されていてもよい。 Here, FIG. 3 shows a hardware configuration of a server device that constitutes the node change device 10 according to the present embodiment. As shown in FIG. 3, the node change device 10 includes a CPU 101, a RAM (Random Access Memory) 102 and a ROM (Read Only Memory) 103 as main storage devices, a communication module 104 for communication, and assistance such as a hard disk. It is configured to include a computer including hardware such as the storage device 105. The functions of the above-described node change device 10 are exhibited by operating these components by a program or the like. The node change 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 related to the arrangement of devices that execute processing from the UE 90, such as determination information for changing the arrangement. The arrangement information storage unit 11 stores information of a plurality of types of tables. Specifically, the arrangement information storage unit 11 includes a service policy table which is a table having information indicating a change condition of a node to be executed, an execution place management table having information of a place to execute a process, and a charging status of each user. A charge management table having information to be shown, and a traffic information table having information indicating the use status from the external network side and the use 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 has transmitted the policy. The service name is a name for identifying a service (for example, a name indicating a video distribution service, an ITS service, etc.). A policy is information indicating a change condition of a 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 at a device other than the edge if it exceeds 300 yen. Further, the policy whose service name is service 5 indicates that edge usage is regulated when the processing load status exceeds 80%, and edge usage regulation 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 processing is moved from the edge processing to the data center, and returned from the data center to the edge at the time of the request. .
　図５に実行場所管理テーブルの例を示す。図５に示すように、実行場所管理テーブルは、サービス名と、場所と、ユーザＩＤとを有する情報を記憶するためのテーブルである。サービス名は、サービスを識別するための名称である。場所は、当該サービスを実行するノードを示す情報である。ユーザＩＤは、ユーザを識別する情報である。図５に示すように、サービス１については、ユーザＩＤがユーザ１、ユーザ２、ユーザ３であるユーザのＵＥ９０から処理要求がなされた場合、エッジ１で処理を行う。また、同じサービス１でも、ユーザＩＤがユーザ４、ユーザ５であるユーザのＵＥから処理要求がなされた場合、データセンタ１で処理を行う。このように、同一のサービスでもユーザによって実行するノードが異なる。 FIG. 5 shows an example of the execution place management table. As shown in FIG. 5, the execution place management table is a table for storing information having a service name, a place, and a user ID. The service name is a name for identifying a service. The place is information indicating a node that executes the service. The user ID is information for identifying a user. As shown in FIG. 5, with regard to the service 1, when a processing request is made from the UE 90 of a user whose user ID is the user 1, the user 2, and the user 3, processing is performed at the edge 1. Further, even in the same service 1, when the processing request is made from the UE of the user whose user ID is user 4 and user 5, the processing is performed in the data center 1. Thus, even for the same service, different nodes execute depending on users.
　続いて、図６に課金管理テーブルの例を示す。図６に示すように、課金管理テーブルは、ユーザＩＤと、サービス名と、課金の状態とを有する情報を記憶するためのテーブルである。 Subsequently, FIG. 6 shows an example of the charge management table. As shown in FIG. 6, the charging management table is a table for storing information having a user ID, a service name, and a charging status.
　ユーザＩＤは、ユーザを識別する情報である。サービス名は、サービスを識別するための情報である。課金の状態は、課金が上限に達したか否かを示す情報である。例えば、サービス１については、ユーザ１が上限に達しており、ユーザ２は、まだ上限に達していないことを示す。 The user ID is information for identifying a user. The service name is information for identifying a service. The charging status is information indicating whether the charging 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 the traffic information table. As shown in FIG. 7, the traffic information table has a service name, an execution device, a target user, traffic on the UE side (delay, bandwidth used), and traffic on the WAN side (delay, bandwidth used) It is a table for storing information.
　サービス名は、サービスを特定するための情報である。実行装置は、処理を実行する装置を示す情報である。対象ユーザは、対象ユーザを特定するための情報である。ここには、特定のユーザを示すユーザＩＤや、全ユーザを示す情報が入力される。ＵＥ側のトラヒックは、内部ネットワークからのアクセスがあったトラヒックの情報（通信遅延の平均値、１秒あたりの通信量）を示す。ＷＡＮ側のトラヒックは、外部ネットワークからのアクセスがあったトラヒックの情報を示す。 The service name is information for identifying a service. The execution device is information indicating a device that executes a process. 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 of traffic that has been accessed from the internal network (average communication delay value, communication amount per second). The traffic on the WAN side indicates information on traffic accessed from the external network.
　シーケンス監視部１２は、ＭＭＥ５０等にシーケンスの監視要求をして、当該ＭＭＥ５０等からシーケンスの監視結果を取得する部分である。具体的に、シーケンス監視部１２は、課金に関する監視要求、接続する回線種別（例えば、４Ｇ、５Ｇ）に関する監視要求をする。シーケンス監視部１２は、配置指示部１５から監視指示を受け付けると、監視対象となる装置（例えば、ＭＭＥ５０）に対して監視指示（監視対象となるユーザＩＤ、サービスＩＤ、監視対象のポリシーを示す情報）を送出する。 The sequence monitoring unit 12 is a part that requests the MME 50 or the like to monitor the sequence, and acquires the monitoring result of the sequence from the MME 50 or the like. Specifically, the sequence monitoring unit 12 makes a monitoring request regarding charging, and makes a monitoring request regarding the type of line to be connected (for example, 4G, 5G). When the sequence monitoring unit 12 receives a monitoring instruction from the placement instructing unit 15, the monitoring instruction (for example, the user ID to be monitored and the service ID to the monitoring target device (for example, MME 50)) and information indicating the monitoring target policy Send out).
　シーケンス監視部１２は、シーケンス監視指示した装置から所定のタイミングで監視結果を受信する。このように、シーケンス監視部１２は、ユーザの使用状況の情報として、監視結果を受信する。シーケンス監視部１２は、当該監視結果を、配置計算部１４へ送出する。 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 the information on the usage status of the user. The sequence monitoring unit 12 sends the monitoring result to the placement calculation unit 14.
　トラヒック監視部１３は、ルータ・スイッチ等にトラヒックの監視要求をして、当該ルータ・スイッチ等からトラヒックの監視結果を取得する部分である。トラヒック監視部１３は、配置指示部１５から監視指示を受け付けると、監視対象となる装置（例えば、ＳＰＧＷ）に対して監視指示（監視対象となるユーザＩＤ、サービスＩＤ、ポリシーを示す情報）を送出する。 The traffic monitoring unit 13 is a part that requests traffic monitoring to a router / switch or the like and acquires traffic monitoring results from the router / switch or the like. Upon receiving the monitoring instruction from the placement instructing unit 15, the traffic monitoring unit 13 sends out a monitoring instruction (information indicating a user ID to be monitored, a service ID, and a policy) to the device to be monitored (for example, SPGW). Do.
　トラヒック監視部１３は、トラヒック監視指示した装置から所定のタイミングで監視結果を受信する。このように、トラヒック監視部１３は、ユーザの使用状況の情報として、監視結果を受信し、当該監視結果を配置計算部１４へ送出する。 The traffic monitoring unit 13 receives the monitoring result at a predetermined timing from the device that instructed the traffic monitoring. As described above, the traffic monitoring unit 13 receives the monitoring result as the information on the usage status of the user, and sends the monitoring result to the placement calculating unit 14.
　配置計算部１４は、ＵＥ９０からのサービス要求に対する処理を行う装置を決定する部分である。配置計算部１４は、ＵＥ９０からサービス要求を新たに取得した場合、ポリシーに基づいて実行する装置を決定する。 The placement calculation unit 14 is a part that determines an apparatus that performs processing for the service request from the UE 90. When newly obtaining a service request from the UE 90, the placement calculation unit 14 determines an apparatus to be executed based on the policy.
　具体的に、配置計算部１４は、ポリシーに基づいてサービスを実行する装置（データセンタ、コアネットワークのエッジ、ＲＡＮのエッジ）を決定する。すなわち、配置計算部１４は、サービスを実行する位置を決定する。配置計算部１４は、ＲＡＮに接続されているエッジで実行することを決定した場合、ＵＥ９０の位置に基づいて、ＵＥ９０から最も近いエッジを実行対象の装置に決定する。 Specifically, the placement calculation unit 14 determines an apparatus (data center, edge of core network, edge of RAN) that executes a service based on the policy. That is, the placement calculation unit 14 determines the position at which the service is to be performed. When determining to execute on the edge connected to the RAN, the placement calculation unit 14 determines the edge closest to the UE 90 as the device to be executed, based on the position of the UE 90.
　また、配置計算部１４は、シーケンス監視部１２又はトラヒック監視部１３から監視結果を受信すると、当該監視結果がサービスポリシーテーブルのポリシーに基づいて、実行する装置の変更条件を満たす場合、実行対象の装置を変更する旨、決定する。このように、配置計算部１４は、シーケンス監視部１２又はトラヒック監視部１３によって取得された監視結果に基づいて、通信端末からの要求処理を実行するノードを変更する。 Further, when the arrangement calculation unit 14 receives the monitoring result from the sequence monitoring unit 12 or the traffic monitoring unit 13 and 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. Thus, based on the monitoring result acquired by the sequence monitoring unit 12 or the traffic monitoring unit 13, the placement calculation unit 14 changes the node that executes the request process from the communication terminal.
　例えば、配置計算部１４は、上記監視結果に基づき、課金の上限値を超えた場合（すなわち、監視結果に基づいた使用度が予め定められた条件を上回る場合）、処理対象の装置（ノード）をエッジ４０から、コアノードのエッジ４０又はデータセンタ７０に変更する旨、決定する。すなわち、配置計算部１４は、要求処理をしているノードのネットワークと比較して、ＵＥ９０からの距離が長いネットワークのノードに変更する旨、決定する。配置計算部１４は、実行する装置を決定すると、処理対象の装置を配置指示部１５へ通知する。 For example, when the arrangement calculation unit 14 exceeds the charging upper limit value based on the monitoring result (that is, when the usage degree based on the monitoring result exceeds a predetermined condition), the processing target device (node) To be changed from the edge 40 to the edge 40 or data center 70 of the core node. That is, the placement calculation unit 14 determines to change to a node of a network having a long distance from the UE 90 as compared with the network of the node performing the request processing. After determining the device to be executed, the placement calculation unit 14 notifies the placement instruction unit 15 of the device to be processed.
　配置指示部１５は、配置計算部１４から処理対象の装置を受け付けて、当該装置への配置変更指示をＭＡＮＯ３０に対して行う。ＭＡＮＯ３０は、これに応じて、対象装置へＵＥ９０のサービス要求処理を実行する旨指示する。 The placement instructing unit 15 receives a device to be processed from the placement calculating 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.
　続いて、図８から図１４を用いて、上記システムにおける処理を説明する。まず図８を用いて、サービスとして、車載端末で実行される運行状態に関するアプリケーションを実行する場合の処理を説明する。具体的には、運行状態に関するアプリケーションには、複数のユーザにより撮像された車外の画像を合成する機能と、経路探索の機能が含まれる。 Subsequently, processing in the above system will be described with reference to FIGS. 8 to 14. First, with reference to FIG. 8, a process in the case of executing an application related to an operation state performed by the on-vehicle terminal will be described as a service. Specifically, the application related to the operation state includes a function of combining images outside the vehicle captured by a plurality of users, and a function of route search.
　また、車載端末で実行される運行状態に関するアプリケーションとして、エッジで実行するためのアプリケーション（エッジアプリ）と、データセンタで実行するためのアプリケーション（サーバサイドアプリ）との２種類のアプリケーションが含まれるものとする。 In addition, two types of applications including an application to be executed at an edge (edge application) and an application to be executed at a data center (server side application) are included as applications related to the operation state executed on the in-vehicle terminal I assume.
　具体的には、エッジアプリ（エッジアプリケーション）では、運行状況を示す画像（例えば、車両前方の画像）を解析した結果と上記画像とを合成した画像を表示出力する処理を行う。サーバサイドアプリ（サーバサイド）は、経路探索依頼に基づき、経路探索をする。 Specifically, in the edge application (edge application), processing is performed to display and output an image obtained by synthesizing the result of analysis of an image (for example, an image in front of the vehicle) indicating the operation status and the image. The server side application (server side) searches for a route based on the route search request.
　ＵＥ９０Ｂは、ログイン要求をデータセンタ７０へ送信すると、エッジ４０へログイン要求を通知する（ステップＳ１）。エッジ４０は、これに応じて仮想マシンであるＶＭ（Virtual Machine）を起動し、エッジアプリを実行できる状態にする（ステップＳ２）。 After 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, to be able to execute an edge application (step S2).
　エッジ４０は、ＶＭ起動後、データセンタ７０へＶＭを起動した旨を通知するし、データセンタ７０は、ＵＥ９０ＢへＶＭ起動した旨を通知する（ステップＳ３）。 After activating the VM, 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 sends 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).
　ＵＥ９０Ａ及びＵＥ９０Ｂが、自端末で撮影した画像をエッジ４０へ送信すると（ステップＳ５）、エッジ４０は、それぞれの画像を解析・合成する（ステップＳ６）。 When the UE 90A and the UE 90B transmit the image captured by the own terminal to the edge 40 (step S5), the edge 40 analyzes and combines the respective images (step S6).
　エッジ４０は、合成した画像をＵＥ９０Ａ及びＵＥ９０Ｂへ送信する（ステップＳ７）。ＵＥ９０Ａ及びＵＥ９０Ｂは、受信した画像をＡＲ（拡張現実）表示をする（ステップＳ８及びステップＳ９）。 The edge 40 transmits the synthesized image to the UE 90A and the UE 90B (step S7). The UE 90A and the UE 90B perform AR (Augmented Reality) display on the received image (Steps S8 and 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 the request (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, a function that requires immediacy, such as display of a captured image, is processed by the edge 40 with a small amount of delay, and a function that does not require immediacy, such as path search, is processed by the data center 70. Do the processing.
　続いて、図９に示すシーケンス図を用いてポリシーの登録及びＶＭ生成の処理手順を説明する。 Subsequently, the processing procedure of policy registration and VM generation will be described using the sequence diagram shown in FIG.
　まず、データセンタ７０においてポリシ－の入力操作がなされると、データセンタ７０は、ポリシーの対象となるサービス名とポリシーの内容と共にポリシーの登録要求をＯＳＳ／ＢＳＳ２０へ行う（ステップＳ２１）。ＯＳＳ／ＢＳＳ２０は、これに応じて、ノード変更装置１０へポリシーの設定要求を行う（ステップＳ２２）。ノード変更装置１０は、上記ポリシーの対象となるサービス名、ポリシーの内容をサービスポリシーテーブルへ登録する。ノード変更装置１０は、登録完了した旨をＯＳＳ／ＢＳＳ２０へ通知する（ステップＳ２３）。ＯＳＳ／ＢＳＳ２０は、当該通知をデータセンタ７０へ通知する（ステップＳ２４）。ステップＳ２１～ステップＳ２４の処理により、ノード変更装置１０のサービスポリシーテーブルにポリシーが登録されることになる。 First, when an operation of entering a policy 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 the contents of the policy to which the policy is applied (step S21). In response to this, the OSS / BSS 20 issues a policy setting request to the node change device 10 (step S22). The node change device 10 registers the service name to be the target of the policy and the content of the policy in the service policy table. The node change device 10 notifies the OSS / BSS 20 that the registration has been completed (step S23). The OSS / BSS 20 notifies the data center 70 of the notification (step S24). By the processes of steps S21 to S24, the policy is registered in the service policy table of the node change device 10.
　ＵＥ９０からデータセンタ７０へエッジ接続依頼（原則エッジで実行されるサービスの実行要求）がなされると（ステップＳ２５）、データセンタ７０からＯＳＳ／ＢＳＳ２０へサービス名、ＵＥ９０のアドレスを通知すると共に、エッジ作成要求を行う（ステップＳ２６）。ＯＳＳ／ＢＳＳ２０は、ノード変更装置１０に対して、エッジ作成依頼を行う（ステップＳ２７）。 When an edge connection request is made from the UE 90 to the data center 70 (a request to execute a service to be executed in principle) (step S 25), the data center 70 notifies the OSS / BSS 20 of the service name and the address of the UE 90, and A creation request is made (step S26). The OSS / BSS 20 sends an edge creation request to the node change device 10 (step S27).
　ノード変更装置１０は、サービス名に対応するサービスポリシーテーブルを参照する（ステップＳ２８、ステップＳ２９）。配置計算部１４は、上記サービスポリシーテーブルの内容に基づいて、実行対象の装置を決定する(ステップＳ３０)。また、配置計算部１４は、監視内容を示す監視対象も決定する（例えば、サービスとユーザＩＤと課金状況等）。 The node change device 10 refers to the service policy table corresponding to the service name (step S28, step S29). The placement calculation unit 14 determines a device to be executed based on the contents of the service policy table (step S30). In addition, the placement calculation unit 14 also determines a monitoring target indicating the monitoring content (for example, service, user ID, charging status, etc.).
　ノード変更装置１０の配置計算部１４は、実行対象の装置と、サービス要求したＵＥ９０のユーザＩＤとを対応付けた情報を実行場所管理テーブルに登録する（ステップＳ３１及びステップＳ３２）。 The layout calculation unit 14 of the node change device 10 registers, in the execution place management table, information in which the device to be executed and the user ID of the UE 90 that has made the service request are associated (Step S31 and Step S32).
　ノード変更装置１０の配置計算部１４は、監視要求及び配置要求を配置指示部１５へ通知する（ステップＳ３３）。配置指示部１５は、配置要求に応じて、ＭＡＮＯ３０へサービス名及びエッジのアドレスを通知すると共に、ＶＭ作成要求をする。 The placement calculation unit 14 of the node change device 10 notifies the placement request unit 15 of a monitoring request and a placement request (step S33). The placement instructing unit 15 notifies the MANO 30 of the service name and the address of the edge and makes a VM creation request in response to the placement request.
　ＭＡＮＯ３０は、当該ＶＭ作成要求に応じて、要求対象の装置のエッジ４０へサービス名を通知するともに、ＶＭ作成依頼をする（ステップＳ３５）。 In response to the VM creation request, the MANO 30 notifies the edge 40 of the requested device of the service name and makes a VM creation request (step S35).
　エッジ４０は、ＶＭ起動準備をすると共に、ＶＭ上で動作するエッジアプリを起動する（ステップＳ３６）。エッジ４０は、エッジアプリ起動完了通知をＭＡＮＯ３０へ行う（ステップＳ３７）。ＭＡＮＯ３０は、これに応じて、エッジアプリ起動完了通知をノード変更装置１０へ行う（ステップＳ３８）。 The edge 40 prepares for VM activation and activates an edge application operating 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 change device 10 (step S38).
　配置指示部１５は、監視指示をトラヒック監視部１３へ行う（ステップＳ３９）。トラヒック監視部１３は、これに応じて対象となる装置へ監視指示を行い、監視指示を行った結果を配置指示部１５へ行う（ステップＳ４０）。 The placement instructing unit 15 sends 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 apparatus and issues the monitoring instruction to the placement instructing unit 15 (step S40).
　配置計算部１４は、監視指示をシーケンス監視部１２へ行う（ステップＳ４１）。シーケンス監視部１２は、これに応じて対象となる装置へ監視指示を行い、監視指示を行った結果を配置指示部１５へ行う（ステップＳ４２）。 The placement 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 apparatus and issues the result of the monitoring instruction to the placement instructing unit 15 (step S42).
　配置指示部１５は、配置計算部１４へ配置完了通知をする（ステップＳ４３）。配置計算部１４は、これに応じて、接続情報（接続先のアドレス）をデータセンタ７０へ送信する（ステップＳ４４）。データセンタ７０は、ＵＥ９０へ接続情報を通知し（ステップＳ４５）、ＵＥ９０は、当該接続情報に基づいてエッジ４０へ接続する（ステップＳ４６）。 The placement instruction unit 15 notifies the placement calculation unit 14 of the placement completion (step S43). In response to this, the placement calculation unit 14 transmits connection information (address of connection destination) to the data center 70 (step S44). The data center 70 notifies the UE 90 of connection information (step S45), and the UE 90 connects to the edge 40 based on the connection information (step S46).
　続いて、図１０のシーケンス図を用いて、実行する装置を変更する処理を説明する。ＵＥ９０は、コアネットワーク内のルータ・スイッチを通じてエッジ接続要求をすると、（ステップＳ５１）、ルータ・スイッチは、エッジ４０へ通信内容を転送する(ステップＳ５２)。 Subsequently, a process of changing an apparatus to be executed will be described using the sequence diagram of FIG. When the UE 90 makes an edge connection request through a router switch in the core network (step S51), the router switch transfers communication contents to the edge 40 (step S52).
　ＯＳＳ／ＢＳＳ２０は、課金状況を判断して、課金限界に達している場合、ノード変更装置１０へ課金限界通知をする（ステップＳ５３）。シーケンス監視部１２は、当該課金限界通知を配置計算部１４へ通知する（ステップＳ５４）。 The OSS / BSS 20 determines the charge status, and when the charge limit is reached, notifies the node change device 10 of the charge limit (step S53). The sequence monitoring unit 12 notifies the allocation calculation unit 14 of the charging limit notification (step S54).
　ノード変更装置１０は、サービスポリシーテーブル、実行場所管理テーブル、及び課金管理テーブルを参照する（ステップＳ５５、ステップＳ５６）。 The node change device 10 refers to the service policy table, the execution place management table, and the charge management table (steps S55 and S56).
　配置計算部１４は、上記サービスポリシーテーブルの内容に基づいて、実行対象の装置を決定する(ステップＳ５７)。また、配置計算部１４は、監視対象も決定する（例えば、サービスとユーザＩＤと課金状況等）。 The placement calculation unit 14 determines the device to be executed based on the contents of the service policy table (step S57). The placement calculation unit 14 also determines a monitoring target (for example, service, user ID, charging status, etc.).
　ノード変更装置１０の配置計算部１４は、実行対象の装置と、サービス要求したＵＥ９０のユーザＩＤとを対応付けた情報を実行場所管理テーブルに登録し、課金管理テーブルを更新する（ステップＳ５８及びステップＳ５９）。 The layout calculation unit 14 of the node change device 10 registers, in the execution location management table, information in which the device to be executed is associated with the user ID of the UE 90 that has made the service request, and updates the charge management table (step S58 and step S59).
　ノード変更装置１０の配置計算部１４は、監視要求及び配置要求を配置指示部１５へ通知する（ステップＳ６０）。配置指示部１５は、配置要求に応じて、ＭＡＮＯ３０へサービス名及び変更先の装置のアドレスを通知すると共に、ＶＭ作成要求をする（ステップＳ６１）。ＭＡＮＯ３０は、分散ＤＢレプリケーション先を変更先の装置であるデータセンタ７０に設定し、ユーザ情報の登録要求をする（ステップＳ６２）。また、ＭＡＮＯ３０は、変更元装置の分散ＤＢへ以後の更新を禁止する。データセンタ７０は、ユーザ情報の登録を完了すると、その旨をＭＡＮＯ３０へ通知する（ステップＳ６３）。 The placement calculation unit 14 of the node change device 10 notifies the placement request unit 15 of a monitoring request and a placement request (step S60). The placement instructing unit 15 notifies the MANO 30 of the service name and the address of the device of the change destination in response to the placement request, and makes a VM creation request (step S61). The MANO 30 sets the distributed DB replication destination in the data center 70 which is the device of the change destination, and makes a registration request for user information (step S62). Also, the MANO 30 prohibits the subsequent update to the distributed DB of the change source device. When the registration of the user information is completed, the data center 70 notifies the MANO 30 to that effect (step S63).
　ＭＡＮＯ３０は、処理対象変更の旨の通知（ＶＭ集約）をエッジ４０に対して行い（ステップＳ６４）、エッジ４０は、これに応じて終了処理（エッジアプリ起動終了）をする（ステップＳ６５）。処理を終了すると、その旨をＭＡＮＯ３０へ通知する（ステップＳ６６）。 The MANO 30 sends a notification (VM consolidation) to the effect of changing the processing target to the edge 40 (step S64), and the edge 40 performs end processing (edge application activation end) according to this (step S65). When the process is completed, the fact is notified to the MANO 30 (step S66).
　ＭＡＮＯ３０は、ＳＰＧＷ６０に対して、フロー切替を指示し（ステップＳ６７）、ＳＰＧＷ６０は、これに応じてフロー切替処理をして、処理完了の旨をＭＡＮＯ３０へ通知する（ステップＳ６８）。また、ＭＡＮＯ３０からルータ・スイッチへフロー切替指示をする（ステップＳ６９）。ルータ・スイッチは、切替終了すると、ＭＡＮＯ３０へ通知する（ステップＳ７０）。このように、ＭＡＮＯ３０は、ＵＥ９０からの処理要求に応じて、データセンタ７０が当該処理を行うように、通信経路を設定する。 The MANO 30 instructs the SPGW 60 to perform the flow switching (step S67), and the SPGW 60 performs the flow switching processing according to this, and notifies the MANO 30 of the processing completion (step S68). Also, a flow switching instruction is issued from the MANO 30 to the router switch (step S69). When switching is completed, the router switch notifies the MANO 30 (step S70). Thus, in response to the processing request from the UE 90, the MANO 30 sets the communication path so that the data center 70 performs the processing.
　ＭＡＮＯ３０は、配置指示部１５へ集約完了通知をする（ステップＳ７１）。配置指示部１５は、シーケンス監視部１２へ監視終了指示をして（ステップＳ７２）、シーケンス監視部１２から完了通知を受領する（ステップＳ７３）。 The MANO 30 notifies the arrangement instructing unit 15 of the completion of aggregation (step S71). The placement instructing unit 15 instructs the sequence monitoring unit 12 to finish 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 finish monitoring (step S74), and receives a completion notification from the traffic monitoring unit 13 (step S75). Thereafter, the arrangement instructing unit 15 notifies the arrangement calculating 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 S 77), the router switch notifies the SPGW, and in response, the SPGW transmits the data center 70 via the router switch. (Step S79, step S80). The data center 70 requests the distributed DB of the edge 40 to read user data (step S 81), and acquires 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.
　続いて、図１１に示すフローチャートを用いて、配置計算部１４が移動判定をする処理（図１０に示すステップＳ５７）を説明する。 Subsequently, a process of the movement calculation performed by the placement calculation unit 14 (step S57 shown in FIG. 10) will be described using the flowchart shown in FIG.
　配置計算部１４は、常時移動変更イベントの待ち受けをする（ステップＳ９１）。何らかのイベントの通知を受信した場合、ステップＳ９２以降の処理を行う。シーケンス監視部１２が課金限界通知を受信する等、課金イベントが発生した場合（ステップＳ９２；ＹＥＳ）、課金管理テーブルの更新処理をする（ステップＳ９３）。処理をしている装置がエッジ４０かデータセンタ７０かを判断する（ステップＳ９４）。処理をしている装置がエッジ４０である場合、課金イベントが発生しており、且つ課金限界通知を受けている場合（ステップＳ９５；ＹＥＳ）、ステップＳ９７へ移動する。 The placement calculation unit 14 always waits for a movement change event (step S91). When the notification of an event is received, the process after step S92 is performed. When a charge event occurs, such as when the sequence monitoring unit 12 receives a charge limit notification (step S92; YES), the charge management table is updated (step S93). It is determined whether the processing apparatus is the edge 40 or the data center 70 (step S94). If the processing device is the edge 40, a charging event has occurred, and if a charging limit notification has been received (step S95; YES), the process moves to step S97.
　課金限界通知を受けていない場合、３Ｇ、４Ｇに遷移していない場合（ステップＳ９６；ＮＯ）、処理装置を変更することなく、ステップＳ９１へ進む。課金限界通知を受けていない場合、回線種別が３Ｇ、４Ｇに遷移した場合（ステップＳ９６；ＹＥＳ）、ステップＳ９７へ移動する。ステップＳ９７では、配置計算部１４は、データセンタ７０へ移動させる旨、決定する（ステップＳ９７）。 If the charging limit notification has not been received, and if 3G or 4G has not been transitioned (step S96; NO), the process proceeds to step S91 without changing the processing device. If the charging limit notification has not been received, and if the line type has transitioned to 3G or 4G (step S96; YES), the process moves to step S97. In step S97, the placement 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 it does not transition to 5G (step S98; NO), the process moves to step S91. If it has transitioned to 5G (step S98; YES), if it has reached the charging limit (step S99; NO), it moves to step S91 without changing the processing device, and if it has not reached the charging limit (step S99; YES), to move to the edge 40, is determined (step S100).
　続いて、図１２のシーケンス図を用いて、トラヒックに基づいて、処理装置を変更する処理を説明する。 Subsequently, a process of changing the processing apparatus 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 the traffic of communication for the edge 40 (step S113).
　トラヒック監視部１３は、当該通知に基づいて、トラヒック情報を更新要求、更新完了通知を受領する（ステップＳ１１４、ステップＳ１１５）。 The traffic monitoring unit 13 receives an update request for traffic information and an update completion notification based on the notification (step S114, step S115).
　外部端末（外部ネットワークを介して接続する端末）であるＵＥ９０Ｂ（端末ＷＡＮ）が、データセンタ７０を介してルータ・スイッチへエッジ４０への処理要求をする（ステップＳ１１６）。ルータ・スイッチは、これに応じて、エッジ４０へ接続する（ステップＳ１１７）。ルータ・スイッチは、当該エッジ４０に対する通信のトラヒックをトラヒック監視部１３へ通知する（ステップＳ１１８）。 The UE 90B (terminal WAN), which is an external terminal (terminal connected via an external network), requests the router / switch to process the edge 40 via the data center 70 (step S116). The router switch connects to the edge 40 accordingly (step S117). The router / switch notifies the traffic monitoring unit 13 of the traffic of the communication for the edge 40 (step S118).
　トラヒック監視部１３は、当該通知に基づいて、トラヒック情報を更新要求、更新完了通知を受領する（ステップＳ１１９、ステップＳ１２０）。 The traffic monitoring unit 13 receives an update request for traffic information and an update completion notification based on the notification (steps S119 and S120).
　トラヒック監視部１３は、定期的にステップＳ１１３で取得したＵＥ側のトラフィックと、ステップＳ１１８で取得したＷＡＮ側のトラフィックとを比較をして、予め定められた閾値以上に差がある場合等の条件を満たした場合、配置計算部１４へ通知する（ステップＳ１２１）。配置計算部１４は、配置情報記憶部１１へサービスポリシーテーブルとトラヒック情報テーブルの取得要求をして（ステップＳ１２２）、配置情報記憶部１１からサービスポリシーテーブル及びトラヒック情報テーブルを取得する（ステップＳ１２３）。 The traffic monitoring unit 13 periodically compares the traffic on the UE side acquired in step S113 with the traffic on the WAN side acquired in step S118, and conditions such as when there is a difference greater than or equal to a predetermined threshold value Is notified to the layout calculation unit 14 (step S121). The placement calculation unit 14 requests the placement information storage unit 11 to obtain the service policy table and the traffic information table (step S122), and obtains the service policy table and the traffic information table from the placement information storage unit 11 (step S123). .
　配置計算部１４は、上述のＵＥ側のトラヒックとＷＡＮ側のトラヒックとを比較した結果に基づいて処理装置を変更する（ステップＳ１２４）。配置計算部１４は、実行場所管理テーブル及びトラヒック情報テーブルの更新要求をして（ステップＳ１２５）、当該更新結果を受け取ると（ステップＳ１２６）、再配置・監視先・変更通知を配置指示部１５へ行う（ステップＳ１２７）。ステップＳ１２８～ステップＳ１４５の処理は、ＭＡＮＯ３０とＳＰＧＷ間におけるフロー切替指示の処理（図１０のステップＳ６７及びステップＳ６８）が、図１２のシーケンスには含まれないこと以外、図１０のステップＳ６１～ステップＳ８２と同様のため、説明を省略する。 The placement calculation unit 14 changes the processing device based on the result of comparison between the traffic on the UE side and the traffic on the WAN side (step S124). The placement calculation unit 14 requests update of the execution place management table and the traffic information table (step S125), and when the update result is received (step S126), the relocation / monitoring destination / change notification is sent to the placement instruction unit 15. The operation is performed (step S127). The process of step S128 to step S145 is the process of step S61 to step of FIG. 10 except that the process (step S67 and step S68 of FIG. 10) of the flow switching instruction between MANO 30 and SPGW is not included in the sequence of FIG. The description is omitted because it is the same as S82.
　図１３に示すフローチャートを用いて、配置計算部１４が移動判定をする処理（図１２に示すステップＳ１２４）を説明する。 The process (step S124 shown in FIG. 12) in which the placement calculation unit 14 makes a movement determination will be described using the flowchart shown in FIG.
　配置計算部１４は、常時移動変更イベントの待ち受けをする（ステップＳ１５１）。トラヒック監視部１３からの通知を受信した場合、どちらの方が帯域利用（すなわち、１秒あたりの通信量）が多いかを確認する（ステップＳ１５２）。この結果、ＷＡＮ側の方が多い場合、遅延要求を満たす範囲でＤＣ（データセンタ７０）側に変更する（ステップＳ１５３）。ＵＥ側の方が多い場合、遅延要求を満たす範囲でＵＥ側に変更する（ステップＳ１５４）。ここで、ＤＣ側への変更とは、ＲＡＮのエッジ４０からコアネットワークのエッジ４０又はデータセンタ７０への変更や、コアネットワークのエッジ４０からデータセンタ７０への変更をいう。また、ＵＥ側への変更とは、データセンタ７０からコアネットワークのエッジ４０又はＲＡＮのエッジ４０への変更や、コアネットワークのエッジ４０からＲＡＮのエッジ４０への変更をいう。また、配置計算部１４は、予め設定されている遅延時間の閾値に基づいて、遅延要求を満たす範囲で変更先を決める。配置計算部１４は、トラヒック情報テーブルにおける、変更先となるエッジのＵＥ側の遅延時間が、上記閾値以下であるか否かを判断して、遅延要求を満たすか否かを判断する。 The placement 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 checked which of the two has more bandwidth usage (that is, the amount of communication per second) (step S152). As a result, when there are more on the WAN side, it is changed to the DC (data center 70) side in a range that satisfies the delay request (step S153). If there are more UEs, the UE is changed to the UE side in a range satisfying the delay request (step S154). Here, the change to the DC side means a change from the edge 40 of the RAN to the edge 40 of the core network or the data center 70 or a change from the edge 40 of the core network to the data center 70. Further, the change to the UE side refers to 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 placement calculation unit 14 determines a change destination in a range that satisfies the delay request based on a preset threshold value of the delay time. The placement calculation unit 14 determines whether the delay time on the UE side of the edge to be changed in the traffic information table is less than or equal to the threshold and determines whether the delay request is satisfied.
　ここで、図１４に、エッジ４０で実施していたときにデータセンタ７０へ移動する例を示す。エッジ４０で処理を実施していた結果、図１４（Ａ）に示すように、サービス１のエッジ２について、利用帯域がＷＡＮ側の方が多くなる。これに応じて、図１４（Ｂ）に示すようにエッジ４０からデータセンタ７０へ変更する。 Here, FIG. 14 shows an example of moving to the data center 70 when the operation is performed at the edge 40. As a result of performing the processing at the edge 40, as shown in FIG. 14A, for the edge 2 of the service 1, the use band 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 modified example will be described with reference to FIGS. In this modification, when the processing load condition of the edge 40 satisfies the restriction condition, the processing is performed by the data center 70 until the processing load condition satisfies the restriction cancellation condition.
　図１５に示したシーケンス図は、図９に示すシーケンス図と共通している部分を多く含むので、図９に示すシーケンス図と異なる部分を中心に説明する。 Since the sequence diagram shown in FIG. 15 includes many parts in common with the sequence diagram shown in FIG. 9, the description will be made focusing on parts different from the sequence diagram shown in FIG.
　ＯＳＳ／ＢＳＳ２０が、ポリシー登録の完了通知をデータセンタ７０へ通知した後に、データセンタ７０及びエッジ４０は、ＯＳＳ／ＢＳＳ２０へデータセンタ７０及びエッジ４０の処理負荷状況を示す情報を通知する（ステップＳ２４Ａ及びステップＳ２４Ｂ）。ＯＳＳ／ＢＳＳ２０は、データセンタ７０及びエッジ４０から処理負荷状況を示す情報を受信すると、図１６に示すような、処理負荷状況テーブルへ当該処理負荷状況を示す情報を装置（場所）毎に記憶する。図１６に示すように、ＯＳＳ／ＢＳＳ２０は、場所と処理負荷状況とを対応付けた処理負荷状況テーブルを記憶している。ここで、処理負荷状況とは、リソースの使用率を示す情報である。エッジ１は、処理負荷状況が３０％であるので、新たにＵＥ９０からの処理要求を受け付けることができる余裕があるが、エッジ２は、処理負荷状況が９０％であるので、新たにＵＥ９０からの処理要求を受け付けることができる余裕がない。 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 the information indicating the processing load status from the data center 70 and the edge 40, it stores the information indicating the processing load status for each device (location) in the processing load status table as shown in FIG. . As shown in FIG. 16, the OSS / BSS 20 stores a processing load situation table in which places and processing load situations are associated with each other. Here, the processing load status is information indicating the resource usage rate. Since Edge 1 has a processing load status of 30%, it has room to newly accept a processing request from UE 90. However, since Edge 2 has a processing load status of 90%, Edge 2 newly receives a request from UE 90. There is not enough time to receive the processing request.
　ステップＳ３０Ａにおいて、配置計算部１４は、上記サービスポリシーテーブルの内容に基づいて、実行対象の装置（エッジ４０）を決定し、サービスポリシーテーブルのサービス５のポリシーが有効である場合、ＯＳＳ／ＢＳＳ２０に対して、当該エッジ４０の処理負荷状況を問合せる。配置計算部１４は、当該処理負荷状況が上記ポリシーの条件に基づき、規制対象となる場合、データセンタ７０で実行する旨、決定する。例えば、上記問合せ対象のエッジ４０が、図１６に示す例のエッジ２である場合、処理負荷状況が９０％であるので、規制対象となる。また、配置計算部１４は、当初決定していたエッジ４０を監視対象とする。 In step S30A, the placement calculation unit 14 determines the device to be executed (edge 40) based on the contents of the service policy table, and if the policy of the service 5 of the service policy table is valid, the OSS / BSS 20 is selected. Then, the processing load status of the edge 40 is inquired. The arrangement calculating unit 14 determines that the data center 70 is to execute the processing load condition if the processing load condition is to be restricted based on the condition of the policy. For example, in the case where the edge 40 to be inquired is the edge 2 in the example shown in FIG. 16, since the processing load situation is 90%, it is a restriction object. Furthermore, the placement calculation unit 14 sets the edge 40 initially determined as a monitoring target.
　ステップＳ３３Ａにおいて、配置計算部１４は、実行対象の装置（データセンタ７０）及び監視対象を配置指示部１５へ通知する。これに応じて、配置指示部１５は、ＭＡＮＯ３０へＶＭ作成依頼をする（ステップＳ３４）。また、配置指示部１５は、ＭＡＮＯ３０を介してＯＳＳ／ＢＳＳ２０に対して上記監視対象のエッジ４０を監視させる。ＭＡＮＯ３０は、データセンタ７０へＶＭ作成依頼をし（ステップＳ３５Ａ）、データセンタ７０は、ＶＭ起動・エッジアプリを起動する（ステップＳ３６Ａ）。データセンタ７０は、エッジアプリ起動完了すると、その旨をＭＡＮＯ３０へ通知する（ステップＳ３７Ａ）。なお、データセンタ７０は、予めＶＭ及びエッジアプリを起動していてもよい。上記のように、配置指示部１５は、ＵＥ９０からの要求処理をデータセンタ７０に処理させるので、ＵＥ９０が接続要求をすると（ステップＳ４６Ａ）、ＳＰＧＷを介してデータセンタ７０と接続する。 In step S33A, the placement calculation unit 14 notifies the placement instructing unit 15 of the device to be executed (data center 70) and the monitoring target. In response to this, the placement instructing unit 15 requests the MANO 30 to create a VM (step S34). Further, the placement instructing unit 15 causes the OSS / BSS 20 to monitor the edge 40 to be monitored via the MANO 30. The MANO 30 requests the data center 70 to create a VM (step S35A), and the data center 70 starts a VM activation / edge application (step S36A). When the edge application activation is completed, the data center 70 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 deployment instruction unit 15 causes the data center 70 to process the request processing from the UE 90, so when the UE 90 makes a connection request (step S46A), the deployment instruction unit 15 connects with the data center 70 via the SPGW.
　続いて、図１７を用いて、データセンタ７０からエッジ４０へＶＭを移動する処理（ＵＥ９０からの処理要求を実行するＶＭをデータセンタ７０からエッジ４０へ変更する処理）の例を説明する。図１７に示す処理は、図１０の処理とは異なる部分を中心に説明する。 Subsequently, an example of processing of moving a VM from the data center 70 to the edge 40 (processing of changing a VM for executing a processing request from the UE 90 from the data center 70 to the edge 40) will be described using FIG. The process shown in FIG. 17 will be described focusing on parts different from the process of FIG.
　ＵＥ９０から処理要求がなされると（ステップＳ５１）、ルータ・スイッチを通じてＳＰＧＷを経由し、データセンタ７０へ接続する（ステップＳ５２Ａ）。図１５で説明したように、エッジ４０が監視対象であるので、当該エッジ４０は、定期的にＯＳＳ／ＢＳＳ２０へ処理負荷状況を示す情報を通知する（ステップＳ５２Ｂ）。ＯＳＳ／ＢＳＳ２０は、エッジ４０の処理負荷状況が７０％を下回った場合、シーケンス監視部１２へ、その旨を通知する（ステップＳ５３Ａ）。そして、シーケンス監視部１２は、処理負荷状況が７０％を下回った旨を配置計算部１４へ通知する（ステップＳ５４Ａ）。 When a processing request is issued from the UE 90 (step S51), the connection is made to the data center 70 via the router / switch via the SPGW (step S52A). As described in 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 placement calculation unit 14 that the processing load status has fallen below 70% (step S54A).
　ＭＡＮＯ３０は、エッジ４０へＤＢレプリケーション先設定要求する（ステップＳ６２Ａ）。エッジ４０は、ＭＡＮＯ３０へＤＢレプリケーション設定完了通知し（ステップＳ６３Ａ）、さらにエッジ４０は、ＶＭ及びエッジアプリを起動する（ステップＳ６５Ａ）。そして、フロー切替がなされた後（ステップＳ６７～ステップＳ７０）、ＵＥ９０が、接続要求するとエッジ４０へ接続する（ステップＳ７７Ａ、ステップＳ８０）。 The MANO 30 requests the edge 40 to set a DB replication destination (step S62A). The edge 40 notifies the MANO 30 of DB replication setting completion (step S63A), and the edge 40 further activates the VM and the edge application (step S65A). Then, after the flow is switched (steps S67 to S70), when the UE 90 makes a connection request, the UE 90 is connected to the edge 40 (step S77A, step S80).
　このように、ＵＥ９０からの要求処理を実行している装置（上述の例ではデータセンタ７０）以外の装置（上述の例では、エッジ４０）の使用状況を監視して、当該使用状況に応じて、ＶＭをデータセンタ７０からエッジ４０へ移動してもよい。 In this way, the usage status of the device (the edge 40 in the above example) other than the device (the above example, the data center 70) executing the request processing from the UE 90 is monitored, and according to the usage state , VM may be moved from data center 70 to edge 40.
　上述では記載していないが、ＵＥ９０が、一定期間データの送受信をしていない場合、サービス６のポリシーに基づいて、エッジ４０からデータセンタ７０へＶＭを移動するようにしてもよい。例えば、エッジ４０がＵＥ９０からの要求処理を実行する旨決定された後、ＯＳＳ／ＢＳＳ２０が、ＵＥ９０からの処理要求を監視した結果、ＵＥ９０からエッジ４０へデータの送受信が一定期間無い場合、エッジ４０からデータセンタ７０へＶＭを移動する。この後で、ＵＥ９０から処理要求がなされたことをＯＳＳ／ＢＳＳ２０が検知すると、ＯＳＳ／ＢＳＳ２０がノード変更装置１０の配置計算部１４へ通知する。配置計算部１４は、当該通知を受信すると、データセンタ７０からエッジ４０へ変更する。また、データ通信中／データの通信の無い状態など通信端末のデータ通信状態に関する情報以外に、通信端末のデータ通信頻度（単位時間当たりの通信量・回数）に関わる情報、通信端末で利用しているサービスに求められるデータ通信の遅延要求が厳しい／緩い状態などに基づいて、ＶＭの変更を判断してもよい。このように、ＵＥ９０のサービス利用状態（ＵＥ９０からエッジ４０への要求処理状態）に基づいて、エッジ４０からデータセンタ７０へＶＭを変更するようにしてもよいし、データセンタ７０からエッジ４０へＶＭを変更するようにしてもよい。 Although not described above, when the UE 90 does not transmit and receive data for a certain period, the VM may be moved from the edge 40 to the data center 70 based on the policy of the service 6. For example, after it is determined that the edge 40 performs the request process from the UE 90, the edge 40 may not transmit or receive data from the UE 90 to the edge 40 as a result of monitoring the process request from the UE 90. Move the VM from the data center to the data center 70. After that, when the OSS / BSS 20 detects that the processing request has been made from the UE 90, the OSS / BSS 20 notifies the placement calculation unit 14 of the node change device 10. When receiving the notification, the placement calculation unit 14 changes the data center 70 to an edge 40. In addition to information on the data communication state of the communication terminal such as data communication in progress / no state of data communication, information related to the data communication frequency (the amount of communication per unit time, the number of times) of the communication terminal The VM change may be determined based on the strict / loose condition of the data communication delay required for the service. Thus, the VM may be changed from the edge 40 to the data center 70 based on the service utilization state of the UE 90 (the request processing state from the UE 90 to the edge 40), or from the data center 70 to the edge 40 May be changed.
　上述の実施形態では、課金限界通知に基づいて、ＲＡＮのエッジ４０からデータセンタ７０へＶＭを移動させる場合について述べたが、ＲＡＮのエッジ４０からコアネットワークのエッジ４０へ移動させるようにしてもよい。 In the above embodiment, the VM is moved from the edge 40 of the RAN to the data center 70 based on the charging limit notification, but may be moved from the edge 40 of the RAN to the edge 40 of the core network .
　上述の実施形態では、ノード変更装置１０が１台のサーバ装置により実現する場合について述べたが、当該ノード変更装置１０が有する機能を複数のサーバ装置により実現するようにしてもよい。 Although the above-mentioned embodiment described the case where the node change device 10 is realized by one server device, the function of the node change device 10 may be realized by a plurality of server devices.
　上述の実施形態では、特に述べてなかったが、ノード変更装置１０が移動先のノードに移動可能か否かを判断するようにしてもよい。当該判断の例として、ノード変更装置１０が、移動先ノードのＣＰＵ数、メモリ量、ディスク量（ディスク容量）、移動先ノードに接続される通信端末数／セッション数及びＮＷ帯域の情報をＭＡＮＯ３０から取得し、取得した情報と、予め設定されている閾値とを比較して移動先のノードへ移動可能か否かを判断する。また、上記判断の別の例として、ノード変更装置１０が、移動先のノードが処理を行なうために必要となるノード（例えば、ＳＰＧＷ６０、ローカルゲートウェイ（ＬＧＷ）、ＤＰＩ（Deep Packet Inspection）、ＤＮＳ（Domain Name Server）等）の負荷量を示す情報をＭＡＮＯ３０から取得して、取得した情報と、予め設定されている閾値とを比較して移動先のノードへ移動可能か否かを判断してもよい。なお、上記の移動先のノードが処理を行なうために必要となるノードが仮想化されてない装置である場合、各移動先のノードで上記負荷量を管理したり、モバイルエッジコンピュータ専用の管理システム（ＭＡＮＯ３０とは別のシステム）で上記負荷量を管理したりしてもよい。また、上記判断の別の例として、ノード変更装置１０が、移動先のノードにおける無線設備の容量（無線のリソースブロックの使用率、基地局装置のＣＰＵ使用率等）の情報を基地局装置又はＭＡＮＯ３０（基地局装置が仮想化基盤で管理されている場合）から取得して、取得した情報と、予め設定されている閾値とを比較して移動先のノードへ移動可能か否か判断してもよい。 Although not described in the above embodiment, it may be determined whether or not the node change device 10 can move to the destination node. As an example of the determination, the node change device 10 uses the MANO 30 for information on the number of CPUs, memory amount, disk amount (disk capacity) of the move destination node, number of communication terminals connected to the move destination node / number of sessions and NW band The acquired information is compared with a preset threshold to determine whether the node can be moved to the destination node. In addition, as another example of the above determination, the node change device 10 requires a node which is required for the movement destination node to perform processing (for example, SPGW 60, local gateway (LGW), DPI (Deep Packet Inspection), DNS ( Even if information indicating the load amount of Domain Name Server) is acquired from MANO 30, and the acquired information is compared with a preset threshold value to determine whether or not the node can be moved to the destination node. Good. If the above destination node is not a virtualized node required to perform processing, each destination node can manage the load amount, or a management system dedicated to mobile edge computers The above-mentioned load may be managed by (a system different from MANO 30). In addition, as another example of the above determination, the node changing device 10 may use the base station device or the information of the capacity of the radio equipment (the utilization rate of the radio resource block, the CPU utilization rate of the base station device, etc.) in the destination node. Acquired from MANO30 (when the base station device is managed on a virtualization basis), compare the acquired information with a preset threshold value, and judge whether it is possible to move to the destination node It is also good.
　ノード変更装置１０が移動先のノードに移動可能か否かを判断した結果、移動不可と判断した場合、移動先のノードに割り当てられている優先度の低いアプリケーションを別のノードに移動させてから再度移動させる。また、ノード変更装置１０が移動先のノードに移動可能か否かを判断した結果、移動不可と判断した場合、ＳＰＧＷ６０やＤＮＳ等、スケールアウトやスケールアップ等によって設備増強可能である場合には、増強後に移動させる。 As a result of judging whether the node change device 10 can move to the destination node, if it is determined that movement is not possible, the low priority application allocated to the destination node is moved to another node Move it again. When it is determined that the node change device 10 can not move to the destination node, if it is determined that the node change device 10 can not move, the SPGW 60, DNS, etc. can be expanded by scaling out, scaling up, etc. Move after augmentation.
　次に、本実施形態におけるノード変更装置１０の作用効果について説明する。本実施形態のノード変更装置１０において、シーケンス監視部１２が、ＵＥ９０による第１ノード（例えば、ＲＡＮに接続しているエッジ４０）の使用状態を示す情報（例えば、課金上限通知）を取得する。配置計算部１４は、上記課金上限通知に基づいて、ＵＥ９０からの要求処理を実行するノードを、ＲＡＮに接続しているエッジ４０からデータセンタ７０（ネットワーク階層が異なる第２ノード）へ変更する。具体的には、エッジ４０は、ＶＭ・エッジアプリを起動することにより、ＵＥ９０からの要求処理を実行しており、配置計算部１４及び配置指示部１５は、ＶＭをデータセンタ７０へ移動させ、エッジアプリをデータセンタ７０で実行させる。これにより、使用情報に基づいて、ＵＥ９０の要求処理を実行するノードを別ネットワークのノードに処理を変更するので、使用状態に応じて、コストと速度とのバランスを取ることができる。 Next, the operation and effect of the node change device 10 in the present embodiment will be described. In the node change device 10 of the present embodiment, the sequence monitoring unit 12 acquires information (for example, charging limit notification) indicating the usage state of the first node (for example, the edge 40 connected to the RAN) by the UE 90. The placement calculation unit 14 changes the node performing the request process from the UE 90 from the edge 40 connected to the RAN to the data center 70 (a second node having a different network hierarchy) based on the charging upper limit notification. Specifically, the edge 40 executes the 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. As a result, the node that executes the request processing of the UE 90 is changed to a node of another network based on the usage information, so that cost and speed can be balanced according to the usage state.
　変更前のノードであるエッジ４０と、変更後のノードであるデータセンタ７０とは、接続されているネットワークの種類が互いに異なる。エッジ４０は、ＲＡＮに接続しており、データセンタ７０は、ＷＡＮに接続している。ＲＡＮに接続しているエッジ４０は、ＷＡＮに接続しているデータセンタ７０と比較して、ＵＥ９０までの距離が近いので、データセンタ７０よりエッジ４０の方が、通信遅延が小さい。よって、使用状態に応じて、ＵＥ９０からの要求処理を実行する装置を変えることにより、コストと速度とのバランスを取ることができる。 The edge 40, which is the node before the change, and the data center 70, which is the node after the change, have different types of connected networks. The edge 40 is connected to the RAN, and the data center 70 is connected to the WAN. The edge 40 connected to the RAN has a shorter communication delay than the data center 70 because the edge 40 connected to the RAN is closer to the UE 90 than the data center 70 connected to the WAN. Thus, cost and speed can be balanced by changing the device that executes the request process from the UE 90 according to the usage state.
　配置計算部１４は、上記のように課金状態が条件（課金上限）を上回る場合（使用状態が予め定められた条件を満たす場合）、要求処理をしているノードのネットワーク（ＲＡＮ）と比較して、ＵＥ９０からの距離が長いネットワーク（ＷＡＮ）に接続されているデータセンタ７０に変更する。このように、使用状態に基づいて階層が異なるネットワークのノードに変更するので、処理負荷やネットワークの利用帯域量を分散させることができる。 When the charging state exceeds the condition (charging upper limit) as described above (when the usage state satisfies the predetermined condition) as described above, the arrangement calculating unit 14 compares it with the network (RAN) of the node performing the request processing. Then, the distance from the UE 90 is changed to the data center 70 connected to a long network (WAN). As described above, since the nodes are changed to nodes of networks having different hierarchies based on the use state, the processing load and the use bandwidth amount of the network can be distributed.
　また、トラヒック監視部１３は、外部ネットワークを用いたＵＥ９０の使用状態を示す使用情報と、ＲＡＮによるＵＥ９０の使用状態を示す使用情報とを取得する。配置計算部１４は、ＷＡＮを介したＵＥ９０の使用状態を示す使用情報と、ＲＡＮによるＵＥ９０の使用状態を示す使用情報とを比較した結果に基づいて、ＵＥ９０からの要求処理を実行するノードを他のネットワークのノードに切り替える。これにより、外部ネットワークと自己ネットワークの使用状態を比較して、処理ノードを移動させるので、外部ネットワークからの通信端末と、自己ネットワークからの通信端末とのそれぞれの処理速度を調整することができる。 In addition, 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. The placement calculation unit 14 determines the node that executes the request process from the UE 90 based on the result of comparing the usage information indicating the usage status of the UE 90 via the WAN with the usage information indicating the usage status of the UE 90 by the RAN. Switch to the network node of. As a result, the processing node is moved by comparing the use state of the external network and the own network, and therefore, the processing speed of each of the communication terminal from the external network and the communication terminal from the own network can be adjusted.
　ソフトウェアは、ソフトウェア、ファームウェア、ミドルウェア、マイクロコード、ハードウェア記述言語と呼ばれるか、他の名称で呼ばれるかを問わず、命令、命令セット、コード、コードセグメント、プログラムコード、プログラム、サブプログラム、ソフトウェアモジュール、アプリケーション、ソフトウェアアプリケーション、ソフトウェアパッケージ、ルーチン、サブルーチン、オブジェクト、実行可能ファイル、実行スレッド、手順、機能などを意味するよう広く解釈されるべきである。 Software may be called software, firmware, middleware, microcode, hardware description language, or any other name, and may be instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules. Should be interpreted broadly to mean applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc.
　また、ソフトウェア、命令などは、伝送媒体を介して送受信されてもよい。例えば、ソフトウェアが、同軸ケーブル、光ファイバケーブル、ツイストペア及びデジタル加入者回線（ＤＳＬ）などの有線技術及び／又は赤外線、無線及びマイクロ波などの無線技術を使用してウェブサイト、サーバ、又は他のリモートソースから送信される場合、これらの有線技術及び／又は無線技術は、伝送媒体の定義内に含まれる。 Also, software, instructions, etc. may be sent and received via a transmission medium. For example, software may use a wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission medium.
　本明細書で説明した情報、信号などは、様々な異なる技術のいずれかを使用して表されてもよい。例えば、上記の説明全体に渡って言及され得るデータ、命令、コマンド、情報、信号、ビット、シンボル、チップなどは、電圧、電流、電磁波、磁界若しくは磁性粒子、光場若しくは光子、又はこれらの任意の組み合わせによって表されてもよい。 The information, signals, etc. described herein may be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips etc that may be mentioned throughout the above description may be voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any of these May be represented by a combination of
　なお、本明細書で説明した用語及び／又は本明細書の理解に必要な用語については、同一の又は類似する意味を有する用語と置き換えてもよい。例えば、チャネル及び／又はシンボルは信号（シグナル）であってもよい。また、信号はメッセージであってもよい。また、コンポーネントキャリア（ＣＣ）は、キャリア周波数、セルなどと呼ばれてもよい。 The terms described in the present specification and / or the terms necessary for the understanding of the present specification may be replaced with terms having the same or similar meanings. For example, the channels and / or symbols may be signals. Also, the signal may be a message. Also, the component carrier (CC) may be called a carrier frequency, a cell or the like.
　本明細書で使用する「システム」および「ネットワーク」という用語は、互換的に使用される。 The terms "system" and "network" as used herein are used interchangeably.
　また、本明細書で説明した情報、パラメータなどは、絶対値で表されてもよいし、所定の値からの相対値で表されてもよいし、対応する別の情報で表されてもよい。例えば、無線リソースはインデックスで指示されるものであってもよい。 In addition, the information, parameters, and the like described in the present specification may be represented by absolute values, may be represented by relative values from predetermined values, or may be represented by corresponding other information. . For example, radio resources may be indexed.
　上述したパラメータに使用する名称はいかなる点においても限定的なものではない。さらに、これらのパラメータを使用する数式等は、本明細書で明示的に開示したものと異なる場合もある。様々なチャネル（例えば、ＰＵＣＣＨ、ＰＤＣＣＨなど）及び情報要素（例えば、ＴＰＣなど）は、あらゆる好適な名称によって識別できるので、これらの様々なチャネル及び情報要素に割り当てている様々な名称は、いかなる点においても限定的なものではない。 The names used for the parameters described above are in no way limiting. In addition, the formulas etc. 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 names, the various names assigned to these various channels and information elements can be Is not limited.
　基地局は、１つまたは複数（例えば、３つ）の（セクタとも呼ばれる）セルを収容することができる。基地局が複数のセルを収容する場合、基地局のカバレッジエリア全体は複数のより小さいエリアに区分でき、各々のより小さいエリアは、基地局サブシステム（例えば、屋内用の小型基地局ＲＲＨ：Ｒｅｍｏｔｅ　Ｒａｄｉｏ　Ｈｅａｄ）によって通信サービスを提供することもできる。「セル」または「セクタ」という用語は、このカバレッジにおいて通信サービスを行う基地局、および／または基地局サブシステムのカバレッジエリアの一部または全体を指す。さらに、「基地局」「ｅＮＢ」、「セル」、および「セクタ」という用語は、本明細書では互換的に使用され得る。基地局は、固定局（fixed station）、ＮｏｄｅＢ、ｅＮｏｄｅＢ（ｅＮＢ）、アクセスポイント（access point）、フェムトセル、スモールセルなどの用語で呼ばれる場合もある。 A base station can accommodate one or more (e.g., three) cells (also called sectors). If the base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small base station RRH for indoor use: Remote Communication service can also be provided by Radio Head. The terms "cell" or "sector" refer to a part or all of the coverage area of a base station and / or a base station subsystem serving communication services in this coverage. Furthermore, the terms "base station" "eNB", "cell" and "sector" may be used interchangeably herein. A base station may be called in terms of a fixed station (Node station), NodeB, eNodeB (eNB), access point (access point), femtocell, small cell, and the like.
　移動局は、当業者によって、加入者局、モバイルユニット、加入者ユニット、ワイヤレスユニット、リモートユニット、モバイルデバイス、ワイヤレスデバイス、ワイヤレス通信デバイス、リモートデバイス、モバイル加入者局、アクセス端末、モバイル端末、ワイヤレス端末、リモート端末、ハンドセット、ユーザエージェント、モバイルクライアント、クライアント、またはいくつかの他の適切な用語で呼ばれる場合もある。 The mobile station may be a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, by those skilled in the art. It may also be called a terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.
　また、本明細書で使用する「判断(determining)」、「決定(determining)」という用語は、多種多様な動作を包含する。「判断」、「決定」は、例えば、判定(judging)、計算(calculating)、算出(computing)、処理(processing)、導出(deriving)、調査(investigating)、探索(looking up)（例えば、テーブル、データベースまたは別のデータ構造での探索）、確認(ascertaining)した事を「判断」「決定」したとみなす事などを含み得る。また、「判断」、「決定」は、受信(receiving)（例えば、情報を受信すること）、送信(transmitting)（例えば、情報を送信すること）、入力(input)、出力(output)、アクセス(accessing)（例えば、メモリ中のデータにアクセスすること）した事を「判断」「決定」したとみなす事などを含み得る。また、「判断」、「決定」は、解決(resolving)、選択(selecting)、選定(choosing)、確立(establishing)、比較(comparing)などした事を「判断」「決定」したとみなす事を含み得る。つまり、「判断」「決定」は、何らかの動作を「判断」「決定」したとみなす事を含み得る。 Also, as used herein, the terms "determining", "determining" encompass a wide variety of operations. "Judgment", "decision" are, for example, judging, calculating, calculating, processing, processing, deriving, investigating, looking up (for example, a table) (Searching in a database or another data structure), ascertaining may be regarded as “decision”, “decision”, etc. Also, "determination" and "determination" are receiving (e.g. receiving information), transmitting (e.g. transmitting information), input (input), output (output), access (accessing) (for example, accessing data in a memory) may be regarded as “judged” or “decided”. Also, "judgement" and "decision" are to be considered as "judgement" and "decision" that they have resolved (resolving), selecting (selecting), choosing (choosing), establishing (establishing), etc. May be included. That is, "judgment" "decision" may include considering that some action is "judged" "decision".
　「接続された(connected)」、「結合された(coupled)」という用語、又はこれらのあらゆる変形は、２又はそれ以上の要素間の直接的又は間接的なあらゆる接続又は結合を意味し、互いに「接続」又は「結合」された２つの要素間に１又はそれ以上の中間要素が存在することを含むことができる。要素間の結合又は接続は、物理的なものであっても、論理的なものであっても、或いはこれらの組み合わせであってもよい。本明細書で使用する場合、２つの要素は、１又はそれ以上の電線、ケーブル及び／又はプリント電気接続を使用することにより、並びにいくつかの非限定的かつ非包括的な例として、無線周波数領域、マイクロ波領域及び光（可視及び不可視の両方）領域の波長を有する電磁エネルギーなどの電磁エネルギーを使用することにより、互いに「接続」又は「結合」されると考えることができる。 The terms "connected", "coupled" or any variants thereof mean any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements that are “connected” or “coupled”. The coupling or connection between elements may be physical, logical or a combination thereof. As used herein, the two elements are by using one or more wires, cables and / or printed electrical connections, and radio frequency as some non-limiting and non-exclusive examples. It can be considered "connected" or "coupled" to one another by using electromagnetic energy such as electromagnetic energy having wavelengths in the region, microwave region and light (both visible and invisible) regions.
　本明細書で使用する「に基づいて」という記載は、別段に明記されていない限り、「のみに基づいて」を意味しない。言い換えれば、「に基づいて」という記載は、「のみに基づいて」と「に少なくとも基づいて」の両方を意味する。 As used herein, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
　本明細書で使用する「第１の」、「第２の」などの呼称を使用した要素へのいかなる参照も、それらの要素の量または順序を全般的に限定するものではない。これらの呼称は、２つ以上の要素間を区別する便利な方法として本明細書で使用され得る。したがって、第１および第２の要素への参照は、２つの要素のみがそこで採用され得ること、または何らかの形で第１の要素が第２の要素に先行しなければならないことを意味しない。 Any reference to an element using the designation "first," "second," etc. as used herein does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient way of distinguishing between two or more elements. Thus, reference to the first and second elements does not mean that only two elements can be taken there, or that in any way the first element must precede the second element.
　また、上記の各装置の構成における「手段」を、「部」、「回路」、「デバイス」等に置き換えてもよい。 Further, the “means” in the configuration of each of the above-described devices may be replaced with a “unit”, a “circuit”, a “device” or the like.
　「含む(ｉｎｃｌｕｄｉｎｇ)」、「含んでいる（ｃｏｍｐｒｉｓｉｎｇ）」、およびそれらの変形が、本明細書あるいは特許請求の範囲で使用されている限り、これら用語は、用語「備える」と同様に、包括的であることが意図される。さらに、本明細書あるいは特許請求の範囲において使用されている用語「または（or）」は、排他的論理和ではないことが意図される。 As long as “including”, “comprising”, and variations thereof are used in the present specification or claims, these terms as well as the term “comprising” are inclusive. Intended to be Further, it is intended that the term "or" as used in the present specification or in the claims is not an exclusive OR.
　なお、情報の通知は、本明細書で説明した態様／実施形態に限られず、他の方法で行われてもよい。例えば、情報の通知は、物理レイヤシグナリング（例えば、ＤＣＩ（Downlink　Control　Information）、ＵＣＩ（Uplink　Control　Information））、上位レイヤシグナリング（例えば、ＲＲＣ（Radio　Resource　Control）シグナリング、ＭＡＣ（Medium　Access　Control）シグナリング、報知情報（ＭＩＢ（Master　Information　Block）、ＳＩＢ（System　Information　Block）））、その他の信号又はこれらの組み合わせによって実施されてもよい。また、ＲＲＣシグナリングは、ＲＲＣメッセージと呼ばれてもよく、例えば、ＲＲＣ接続セットアップ（RRC Connection Setup）メッセージ、ＲＲＣ接続再構成（RRC Connection Reconfiguration）メッセージなどであってもよい。 In addition, notification of information is not limited to the aspect / embodiment described in the present specification, and may be performed by another method. For example, notification of information may be physical layer signaling (for example, Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Also, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message, or the like.
　また、本明細書で説明した各態様／実施形態は、ＬＴＥ（Long　Term　Evolution）、ＬＴＥ－Ａ（LTE-Advanced）、ＳＵＰＥＲ　３Ｇ、ＩＭＴ－Ａｄｖａｎｃｅｄ、４Ｇ、５Ｇ、ＦＲＡ（Future　Radio　Access）、Ｗ－ＣＤＭＡ（登録商標）、ＧＳＭ（登録商標）、ＣＤＭＡ２０００、ＵＭＢ（Ultra　Mobile　Broadband）、ＩＥＥＥ　８０２．１１（Ｗｉ－Ｆｉ）、ＩＥＥＥ　８０２．１６（ＷｉＭＡＸ）、ＩＥＥＥ　８０２．２０、ＵＷＢ（Ultra-WideBand）、Ｂｌｕｅｔｏｏｔｈ（登録商標）、その他の適切なシステムを利用するシステム及び／又はこれらに基づいて拡張された次世代システムに適用されてもよい。 In addition, each aspect / embodiment described in the present specification is 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) The present invention may be applied to a system utilizing Bluetooth), another appropriate system, and / or an advanced next-generation system based on these.
　また、本明細書で説明した各態様／実施形態の処理手順、シーケンス、フローチャートなどは、矛盾の無い限り、順序を入れ替えてもよい。例えば、本明細書で説明した方法については、例示的な順序で様々なステップの要素を提示しており、提示した特定の順序に限定されない。 Moreover, as long as there is no contradiction, you may replace the order of the processing procedure of each aspect / embodiment, sequence, flowchart, etc. which were demonstrated in this specification. For example, for the methods described herein, elements of the various steps are presented in an exemplary order and are not limited to the particular order presented.
　また、本明細書において基地局によって行われるとした特定動作は、場合によってはその上位ノード（upper node）によって行われることもある。基地局を有する１つまたは複数のネットワークノード（network nodes）からなるネットワークにおいて、端末との通信のために行われる様々な動作は、基地局および／または基地局以外の他のネットワークノード(例えば、MMEまたはS-GWなどが考えられるが、これらに限られない)によって行われ得ることは明らかである。上記において基地局以外の他のネットワークノードが１つである場合を例示したが、複数の他のネットワークノードの組み合わせ(例えば、MMEおよびS-GW)であってもよい。 Also, in some cases, the specific operation supposed to be performed by the base station in this specification may be performed by its upper node. In a network of one or more network nodes with a base station, the various operations performed for communication with the terminals may be the base station and / or other network nodes other than the base station (eg, It is clear that it may be performed by MME or S-GW etc but not limited to these). Although the case where one other network node other than a base station was illustrated above was illustrated, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).
　上記の情報等は、上位レイヤ（または下位レイヤ）から下位レイヤ（または上位レイヤ）へ出力され得る。複数のネットワークノードを介して入出力されてもよい。 The above information and the like may be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input and output may be performed via a plurality of network nodes.
　入出力された情報等は特定の場所（例えば、メモリ）に保存されてもよいし、管理テーブルで管理してもよい。入出力される情報等は、上書き、更新、または追記され得る。出力された情報等は削除されてもよい。入力された情報等は削除されてもよい。入力された情報等は他の装置へ送信されてもよい。 The input / output information or the like may be stored in a specific place (for example, a memory) or may be managed by a management table. Information to be input or output may be overwritten, updated or added. The output information etc. may be deleted. The input information may be deleted. The input information or the like may be transmitted to another device.
　判定は、１ビットで表される値（０か１か）によって行われてもよいし、真偽値(Boolean：trueまたはfalse)によって行われてもよいし、数値の比較（例えば、所定の値との比較）によって行われてもよい。 The determination may be performed by a value (0 or 1) represented by one bit, may be performed by a boolean value (Boolean: true or false), or may be compared with a numerical value (for example, a predetermined value). Comparison with the value).
　本明細書で説明した各態様／実施形態は単独で用いてもよいし、組み合わせて用いてもよいし、実行に伴って切り替えて用いてもよい。また、所定の情報の通知（例えば、「Ｘであること」の通知）は、明示的に行うものに限られず、暗黙的（例えば、当該所定の情報の通知を行わない）ことによって行われてもよい。 Each aspect / embodiment described in this specification may be used alone, may be used in combination, and may be switched and used along with execution. In addition, notification of predetermined information (for example, notification of "it is X") is not limited to what is explicitly performed, but is performed by implicit (for example, not notifying of the predetermined information) It is also good.
　本開示の全体において、明らかに単数であることを示しているものではない限り、単数および複数の両方のものを含むものとする。 Throughout the present disclosure, both singular and plural are intended to be included, unless expressly indicated to be singular.
　以上、本発明について詳細に説明したが、当業者にとっては、本発明が本明細書中に説明した実施形態に限定されるものではないということは明らかである。本発明は、特許請求の範囲の記載により定まる本発明の趣旨及び範囲を逸脱することなく修正及び変更態様として実施することができる。したがって、本明細書の記載は、例示説明を目的とするものであり、本発明に対して何ら制限的な意味を有するものではない。 Although the present invention has been described above in detail, it is apparent to those skilled in the art that the present invention is not limited to the embodiments described herein. The present invention can be embodied as modifications and alterations without departing from the spirit and scope of the present invention defined by the description of the claims. Accordingly, the description in the present specification is for the purpose of illustration and does not have any limiting meaning on the present invention.
　１…通信システム、１０…ノード変更装置、１１…配置情報記憶部、１２…シーケンス監視部、１３…トラヒック監視部、１４…配置計算部、１５…配置指示部、２０…ＯＳＳ／ＢＳＳ、３０…ＭＡＮＯ、４０…エッジ、５０…ＭＭＥ、６０…ＳＰＧＷ、７０…データセンタ、８０…ｅＮｏｄｅＢ、９０…ＵＥ、１０１…ＣＰＵ、１０２…ＲＡＭ、１０３…ＲＯＭ、１０４…通信モジュール、１０５…補助記憶装置。 DESCRIPTION OF SYMBOLS 1 ... Communication system, 10 ... Node change apparatus, 11 ... Placement information storage part, 12 ... Sequence monitoring part, 13 ... Traffic monitoring part, 14 ... Placement calculation part, 15 ... Placement 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)

  1. 　通信端末の通信を行う通信システムの制御方法において、
    　前記通信端末による要求処理を実行する第１ノードの使用状態を示す情報に応じ、若しくは、
    　前記第１ノードと異なるネットワーク階層に位置する第２ノードの使用状態を示す情報に応じ、若しくは、
    　前記通信端末のサービス利用状態を示す情報に応じ、
    　前記第１ノードと、前記第２ノードとの間で、前記通信端末からの要求処理を実行するノードを変更する、制御方法。     In a control method of a communication system which performs communication of a communication terminal,
    According to the information indicating the use state of the first node that executes the request processing by the communication terminal, or
    According to the information indicating the use state of the second node located in the network hierarchy different from the first node, or
    According to the information indicating the service utilization state of the communication terminal,
    A control method for changing a node that executes request processing from the communication terminal between the first node and the second node.
  2. 　前記通信端末と第１ノードとの間の通信遅延と、前記通信端末と第２ノードとの間の通信遅延とが異なる、請求項１に記載の制御方法。 The control method according to claim 1, wherein a communication delay between the communication terminal and the first node and a communication delay between the communication terminal and the second node are different.
  3. 　前記第１ノードと、前記第２ノードとの間で、前記通信端末からの要求処理を実行するノードを変更するとは、
    　前記通信端末からの要求処理を実行する仮想マシンがあるノードを変更することである、請求項１に記載の制御方法。     Between the first node and the second node, changing a node that performs request processing from the communication terminal,
    The control method according to claim 1, wherein a virtual machine that executes request processing from the communication terminal is to change a node.
  4. 　前記第１ノードは、仮想マシンを起動し、前記第１ノードで実行するためのアプリケーションを実行できる状態にして、前記通信端末からの要求処理を実行し、
    　前記通信端末からの要求処理を実行するノードを変更するとは、前記第１ノードの仮想マシンを、前記第２ノードへ移動させ、
    　当該アプリケーションを前記第２ノードの仮想マシンで実行させる、
    請求項３に記載の制御方法。     The first node activates a virtual machine, enables execution of an application to be executed on the first node, and executes request processing from the communication terminal.
    Changing the node that executes the request process from the communication terminal moves the virtual machine of the first node to the second node,
    Execute the application on a virtual machine of the second node,
    The control method according to claim 3.
  5. 　前記通信端末による要求処理を実行する第１ノードの使用状態を示す情報、若しくは、
    　第１ノードと異なるネットワーク階層に位置する第２ノードの使用状態を示す情報、若しくは、
    　前記通信端末のサービス利用状態を示す情報の何れかの情報が予め定められた条件を満たす場合、前記第１ノードと、前記第２ノードとの間で、前記通信端末からの要求処理を実行するノードを変更する、請求項１～４の何れか一項に記載の制御方法。     Information indicating the use 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 network hierarchy different from the first node, or
    If any of the information indicating the service use state of the communication terminal satisfies a predetermined condition, the request process from the communication terminal is executed between the first node and the second node The control method according to any one of claims 1 to 4, wherein the node is changed.
  6. 　前記第１ノード及び前記第２ノードの何れかは、前記通信端末が在圏するネットワークである自己ネットワークに属し、他方のノードは、前記自己ネットワークとは異なるネットワークである外部ネットワークに属し、
    　前記外部ネットワークを介して接続する端末である外部端末による使用状態を示す使用情報と、前記自己ネットワークにおける端末である内部端末による使用状態を示す使用情報とを取得し、
    　前記外部端末の使用状態を示す使用情報と、前記内部端末の使用状態を示す使用情報とを比較した結果に基づいて、通信端末からの要求処理を実行するノードを第１ノードと第２ノードとの間で変更する、請求項１～５の何れか一項に記載の制御方法。     One of the first node and the second node belongs to a self network which is a network in which the communication terminal is located, and the other node belongs to an external network which is a network different from the self network.
    Acquiring usage information indicating usage status by an external terminal that is a terminal connected via the external network, and usage information indicating usage status by an internal terminal that is a terminal in the self network;
    Based on the result of comparing the use information indicating the use state of the external terminal with the use information indicating the use state of the internal terminal, a node that executes request processing from the communication terminal is a first node and a second node The control method according to any one of claims 1 to 5, which changes between
  7. 　通信端末の通信を行う通信システムの制御装置において、
    　前記通信端末による要求処理を実行する第１ノードの使用状態を示す情報に応じ、若しくは、
    　前記第１ノードと異なるネットワーク階層に位置する第２ノードの使用状態を示す情報に応じ、若しくは、
    　前記通信端末のサービス利用状態を示す情報に応じ、
    　前記第１ノードと、前記第２ノードとの間で、前記通信端末からの要求処理を実行するノードを変更する、制御装置。     In a control device of a communication system performing communication of a communication terminal,
    According to the information indicating the use state of the first node that executes the request processing by the communication terminal, or
    According to the information indicating the use state of the second node located in the network hierarchy different from the first node, or
    According to the information indicating the service utilization state of the communication terminal,
    A control device for changing a node that executes request processing from the communication terminal between the first node and the second node.
  8. 　前記第１ノードと、前記第２ノードとの間で、前記通信端末からの要求処理を実行するノードを変更するとは、
    　前記通信端末からの要求処理を実行する仮想マシンがあるノードを変更することである、請求項７に記載の制御装置。     Between the first node and the second node, changing a node that performs request processing from the communication terminal,
    The control device according to claim 7, wherein a virtual machine that executes request processing from the communication terminal is to change a node.
  9. 　前記通信端末による要求処理を実行する第１ノードの使用状態を示す情報、若しくは、
    　第１ノードと異なるネットワーク階層に位置する第２ノードの使用状態を示す情報、若しくは、
    　前記通信端末のサービス利用状態を示す情報の何れかの情報が、予め定められた条件を満たす場合、前記第１ノードと、前記第２ノードとの間で、前記通信端末からの要求処理を実行するノードを変更する、請求項７に記載の制御装置。     Information indicating the use 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 network hierarchy different from the first node, or
    If any of the information indicating the service utilization state of the communication terminal satisfies a predetermined condition, the request processing from the communication terminal is executed between the first node and the second node The control device according to claim 7, wherein the node to be changed is changed.
  10. 　前記第１ノード及び前記第２ノードの何れかは、前記通信端末が在圏するネットワークである自己ネットワークに属し、他方のノードは、前記自己ネットワークとは異なるネットワークである外部ネットワークに属し、
    　前記外部ネットワークを介して接続する端末である外部端末による使用状態を示す使用情報と、前記自己ネットワークにおける端末である内部端末による使用状態を示す使用情報とを取得し、
    　前記外部端末の使用状態を示す使用情報と、前記内部端末の使用状態を示す使用情報とを比較した結果に基づいて、通信端末からの要求処理を実行するノードを第１ノードと第２ノードとの間で変更する、請求項７～９の何れか一項に記載の制御装置。     One of the first node and the second node belongs to a self network which is a network in which the communication terminal is located, and the other node belongs to an external network which is a network different from the self network.
    Acquiring usage information indicating usage status by an external terminal that is a terminal connected via the external network, and usage information indicating usage status by an internal terminal that is a terminal in the self network;
    Based on the result of comparing the use information indicating the use state of the external terminal with the use information indicating the use state of the internal terminal, a node that executes request processing from the communication terminal is a first node and a second node The control device according to any one of claims 7 to 9, which changes between
PCT/JP2016/068854 2015-06-29 2016-06-24 Control method and control device WO2017002729A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2017526323A JP6731407B2 (en) 2015-06-29 2016-06-24 Control method and control device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2015-130477 2015-06-29
JP2015130477 2015-06-29

Publications (1)

Publication Number Publication Date
WO2017002729A1 true WO2017002729A1 (en) 2017-01-05

Family

ID=57608303

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/068854 WO2017002729A1 (en) 2015-06-29 2016-06-24 Control method and control device

Country Status (2)

Country Link
JP (1) JP6731407B2 (en)
WO (1) WO2017002729A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020152954A1 (en) * 2019-01-23 2020-07-30 ソニー株式会社 Network arrangement control device, communication system, and control method thereof
US10904324B2 (en) 2017-10-30 2021-01-26 Hitachi, Ltd. Computer system and method of controlling data processing

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012118980A (en) * 2010-11-29 2012-06-21 Internatl Business Mach Corp <Ibm> Method, system, and computer program for providing plan for highly reliable shift in stability-limited virtualized environment
JP2015041198A (en) * 2013-08-21 2015-03-02 日本電信電話株式会社 Management device, communication system, management method and management program

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013117757A (en) * 2011-12-01 2013-06-13 Sony Computer Entertainment Inc Information processing system, information processing server, information processing method, information processing program, computer-readable storage medium storing information processing program
JP5832481B2 (en) * 2013-06-12 2015-12-16 株式会社ソニー・コンピュータエンタテインメント Information processing apparatus, information processing system, and information processing method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012118980A (en) * 2010-11-29 2012-06-21 Internatl Business Mach Corp <Ibm> Method, system, and computer program for providing plan for highly reliable shift in stability-limited virtualized environment
JP2015041198A (en) * 2013-08-21 2015-03-02 日本電信電話株式会社 Management device, communication system, management method and management program

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10904324B2 (en) 2017-10-30 2021-01-26 Hitachi, Ltd. Computer system and method of controlling data processing
WO2020152954A1 (en) * 2019-01-23 2020-07-30 ソニー株式会社 Network arrangement control device, communication system, and control method thereof
US11937118B2 (en) 2019-01-23 2024-03-19 Sony Group Corporation Network deployment control apparatus, communication system, and control method therefor

Also Published As

Publication number Publication date
JPWO2017002729A1 (en) 2018-03-01
JP6731407B2 (en) 2020-07-29

Similar Documents

Publication Publication Date Title
JP6402253B2 (en) COMMUNICATION CONTROL METHOD, COMMUNICATION CONTROL DEVICE, AND COMMUNICATION SYSTEM
CN111480366B (en) Shared PDU session establishment and binding
US11212731B2 (en) Mobile network interaction proxy
US11968750B2 (en) System and method for session relocation at edge networks
US20230189006A1 (en) Orchestration and configuration of e2e network slices across 3gpp core network and oran
US10798761B2 (en) Method for establishing protocol data unit session in communication system
US10356663B2 (en) Service allocation determining methid
US11252048B2 (en) Capability exposure for service instantiation
US11109202B2 (en) Method and system for intelligent routing for mobile edge computing
US20190159107A1 (en) Method for processing access request from ue, and network node
KR102024332B1 (en) Mme reselection method and mme
US10917527B2 (en) Policy device selection by common IMS
JP2015525492A (en) System and method for network detection and selection
US11129092B2 (en) Application specific location discovery
WO2017002729A1 (en) Control method and control device
US11700563B2 (en) Systems and methods for device-assisted seamless transfer between edge computing systems in a wireless network
US11563827B1 (en) Method and system for network performance optimization service
US11985731B2 (en) Systems and methods for exposing user equipment identity
JP6967018B2 (en) RAN connection control method and base station
WO2019078212A1 (en) Communication control method and connection target change method
JP7034098B2 (en) Communication control device and communication control method
US20240154935A1 (en) Integrating mobile network capabilities with cloud platform services
JP2020194990A (en) Node group and migration method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16817837

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017526323

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16817837

Country of ref document: EP

Kind code of ref document: A1