JP6263424B2 - Management system and management method - Google Patents

Description

  The present invention relates to a management system and management method related to management of a communication system.

  Conventionally, for various purposes, a computer has been made a virtual machine (VM) by server virtualization technology. In addition, using this technique, it is considered to use a node in a core network of a mobile communication network (mobile communication network) as a virtual machine (for example, see Non-Patent Document 1).

ETSI Group Specification (ETSI GS NFV 002 v1.1.1 (2013.10)) Network Functions Virtualisation (NFV); Architectural Framework

  A node in a core network of a mobile communication network is realized by a virtual network function (VNF) that is a virtualized communication function on a virtual machine in the NFV (Network Functions Virtualisation) environment disclosed in Non-Patent Document 1 above. Is done. It is conceivable that the management of the mobile communication network as described above is performed by three functional entities of VNFM (VNF Manager), VIM (Virtualized Infrastructure Manager), and Orchestrator. The VNFM holds detailed information for realizing the VNF on the virtual machine, and has a VNF management function. The VIM monitors the status of physical servers (physical servers and virtual resources) on which virtual machines are realized, and creates and deletes virtual machines and VNFs on physical servers under the control of VNFM or orchestrator.

  Note that a plurality of physical servers are normally arranged in a data center, and the VIM performs processing for a group of physical servers installed in one or more data centers. In addition, management (resource management) of physical server groups in the data center is performed by different mounting methods such as OPENSTACK (registered trademark) or vCenter. The VIM is provided for each mounting method in the data center. The orchestrator performs overall resource management across a plurality of VIMs.

  In such an NFV environment, it is assumed that VNFM additionally reserves resources via an orchestrator when VNF is scaled out due to lack of resources in VNF. However, through the orchestrator, there is a problem that the processing of the orchestrator increases and the time for scaling out the VNF increases.

  Therefore, the present invention has been made in view of such a problem, and an object of the present invention is to provide a management system and a management method that can scale out VNF more quickly in an NFV environment.

In order to solve the above problem, the management system of the present invention is included in a communication system including a virtual resource including a physical server on which a virtual server that executes communication processing is generated, and the virtual server has A management system comprising a virtual communication function management node that manages a function for executing communication processing, a virtual resource management node that manages each of the virtual resources, and an overall management node that manages the entire virtual resources. The virtual communication function management node includes a surplus resource information database that stores surplus resource information related to surplus resources that are surplus virtual resources reserved in advance by the virtual resource management node, and a function that executes communication processing. When a notification indicating that the virtual resources are insufficient is received, a reservation is made based on the surplus resource information stored in the surplus resource information database. Identifying a virtual server surplus resources, and a deployment instruction transmitting means for transmitting to the virtual resource managing without the intervention of the overall management node an instruction to deploy virtual servers identified, virtualized resource management node When receiving an instruction to deploy a virtual server from the virtual communication function management node without going through the overall management node , the virtual communication function management node includes virtual server deployment means for deploying the virtual server.

  According to such a management system, when the virtual communication function management node receives a notification that the virtual resources are insufficient from the function that executes the communication processing, the virtual communication function management node identifies the virtual server of the reserved surplus resource in advance. Then, an instruction to deploy the identified virtual server is transmitted to the virtual resource management node, and the virtual server is deployed by the virtual resource management node. In other words, when the VNFM (virtual communication function management node) receives notification from the VNF (function for executing communication processing) that the virtual resources are insufficient, the VIMM (virtual communication function management node) does not go through the orchestrator (overall management node). An instruction to deploy a virtual server can be directly transmitted to the (virtualized resource management node). Thereby, the processing burden of the orchestrator can be suppressed, and the VNF can be scaled out more quickly. In addition, since a virtual server of surplus resources reserved in advance is deployed, it is possible to omit the process of determining whether or not a virtual resource can be secured before securing the virtual server. Can be scaled out. In other words, VNF can be scaled out more quickly in an NFV environment.

  In the management system of the present invention, the overall management node requests one of the virtualization resource management nodes to reserve and secure a surplus resource, and the virtual communication function management node Stores information on one virtual resource management node for which reservation and reservation of surplus resources are requested by the surplus resource information database, and receives notification from the function that executes communication processing that the virtual resources are insufficient. Preferably, one virtual resource management node is identified from the surplus resource information database, and an instruction to deploy a virtual server is transmitted to the one virtual resource management node. If such a configuration is adopted, when the VNFM (virtual communication function management node) receives notification from the VNF (function for executing communication processing) that the virtual resources are insufficient, the VNFM (virtual communication function management node) passes through the orchestrator (overall management node). Without specifying the specific VIM (one virtualization resource management node) for which the orchestrator has made a reservation and reservation request in advance, an instruction to deploy a virtual server is sent to the specific VIM. Can do. Thereby, the processing burden of the orchestrator can be suppressed, and the VNF can be scaled out more quickly. In other words, VNF can be scaled out more quickly in an NFV environment.

  In the management system of the present invention, the virtual resource management node is a deployment completion response when the virtual server is deployed by the virtual server deployment means, and is a response indicating completion of deployment and includes virtual resource information related to the deployed virtual server. A deployment completion response transmitting means for transmitting a completion response to the virtual communication function management node. When the virtual communication function management node receives the deployment completion response from the virtualization resource management node, the virtual communication function management node is deployed in the deployment completion response. It is preferable to further include surplus resource information updating means for updating surplus resource information stored in the surplus resource information database based on the virtual resource information regarding the virtual server. With this configuration, when a virtual server is deployed, a VNFM (virtual communication function management node) updates surplus resource information based on the virtual resource information related to the virtual server. That is, the VNFM can manage surplus resource information in accordance with the current situation. As a result, VNFM can identify and deploy virtual servers for reserved surplus resources based on surplus resource information in accordance with the current situation, and therefore scales out VNF more quickly and reliably. be able to.

  In the management system of the present invention, when the virtual communication function management node receives an instruction to cancel the reservation of the surplus resource from the overall management node, the virtual communication function management node makes a reservation among the surplus resource information stored in the surplus resource information database. Reservation cancellation response that identifies the surplus resource information to be released, deletes the specified surplus resource information, and a reservation cancellation response that transmits a reservation cancellation response to the overall management node when the reservation cancellation of the surplus resource is canceled And a transmission means. If such a configuration is adopted, for example, when virtual resources other than reserved surplus resources are depleted, other services such as an orchestrator (overall management node) are transferred to the VNFM (virtual communication function management node). On the other hand, the reservation can be released, and the surplus resources for which the reservation has been released can be used effectively.

  By the way, the present invention can be described as the invention of the management system as described below, in addition to the invention of the management system as described above. This is substantially the same invention only in different categories, and has the same operations and effects.

In other words, the management method according to the present invention is included in a communication system including a virtual resource including a physical server on which a virtual server that executes communication processing is generated, and executes the communication processing that the virtual server has. Management method executed by a management system comprising a virtual communication function management node for managing a function to be performed, a virtual resource management node for managing each of the virtual resources, and an overall management node for managing the entire virtual resources The virtual communication function management node includes a surplus resource information database that stores surplus resource information related to surplus resources that are surplus virtual resources reserved in advance by the virtual resource management node, and includes virtual communication function management. When the node receives notification from the function that executes communication processing that the virtual resources are insufficient, it is stored in the surplus resource information database. Based on the redundant resource information, identifies a virtual server surplus resources are reserved, the deployment instruction transmission step of transmitting to the virtual resource managing without the intervention of the overall management node an instruction to deploy virtual servers identified And a virtual server deployment step of deploying the virtual server when the virtual resource management node receives an instruction from the virtual communication function management node to deploy the virtual server without going through the overall management node .

  According to the present invention, VNF can be scaled out more quickly in an NFV environment.

It is a figure which shows the structure of the management system which concerns on embodiment of this invention, and the mobile communication system containing the said management system. It is a figure which shows the function structure of the management system which concerns on embodiment of this invention. It is a figure which shows the hardware constitutions of the node contained in the management system which concerns on embodiment of this invention. It is a sequence diagram which shows the process (management method) at the time of Instantiation in the mobile communication system 1 which concerns on embodiment of this invention. It is a table figure which shows the correspondence table between a communication service and VNF, and a table figure which shows the correspondence table between VNFM and VNF which VNFM manages. It is a table figure which shows DC which can be arrange | positioned for every VNF classification, and a table figure which shows topology information between DC. It is a table figure of NW whole resource information DB, and a table figure of resource information. It is a table figure which shows the conversion table of VIM and DC which VIM manages. It is a table figure of VNF detailed information DB. It is a table figure of the required resource information list for every usable DC, and a table figure of the necessary resource information list for surplus resources for every usable DC. It is a table figure of a priority index of DC selection, and a table figure of a required resource information list. It is a table figure of required resource information. It is a table figure which shows arrangement | positioning / starting information and NW structure information. It is a table figure of a reservation number, VM deployment destination physical apparatus, and allocation resource information. It is a table figure of the required resource information list for surplus resources for every usable DC, and a table figure of the required resource information for surplus resources. It is a table figure of VIM surplus resource information DB. It is a table figure of VNFM surplus resource information DB. It is another table figure of VNFM surplus resource information DB. It is a table figure of VIM surplus resource information DB. It is a sequence diagram which shows the process (management method) at the time of the resource augmentation request | requirement from VNF in the mobile communication system 1 which concerns on embodiment of this invention. It is a table figure of an additional required resource condition. It is a table figure of arrangement | positioning / starting information and NW structure information. It is a table figure of a reservation number, VM deployment destination physical apparatus, and allocation resource information. It is a table figure of VIM surplus resource information DB. It is a table figure of VNFM surplus resource information DB. It is a table figure of VNFM surplus resource information DB. It is a table figure of VIM surplus resource information DB. The table figure of VNFM surplus resource information DB. It is a sequence diagram which shows the process (management method) when the surplus resource which VNFM manages can be shared by different VNFs at the time of the resource increase request from VNF in the mobile communication system 1 which concerns on embodiment of this invention. It is a table figure of VNFM surplus resource information DB. It is a table figure of VIM surplus resource information DB. It is a table figure which shows a reservation number, VM deployment destination physical apparatus, and allocation resource information. It is a table figure which shows VIM surplus resource information DB. It is a table figure which shows VNFM surplus resource information DB. It is a sequence diagram which shows a process (management method) when a surplus resource of VNFM is available at the time of resource shortage at the instant of instantiation in the mobile communication system according to the embodiment of the present invention. It is a table figure which shows the resource information extracted from NW whole resource information DB. It is a table figure of VNFM surplus resource DB. It is a table figure of VIM surplus resource information DB. It is a table figure of a required resource information list. It is a table figure of VNFM surplus resource information DB. It is a sequence diagram which shows the process (management method) when the surplus resources of other VNFMs are available when the resources are insufficient except for the surplus resources during Instantiation in the mobile communication system according to the embodiment of the present invention. It is a table figure of VNFM surplus resource DB. It is a table figure of VIM surplus resource information DB. It is a table figure which shows the required resource information list for every surplus resource reservation information which can be utilized. It is a table figure of VNFM surplus resource information DB. It is a table figure of VIM surplus resource reservation information DB. It is a table figure which shows required resource information.

  DESCRIPTION OF EMBODIMENTS Hereinafter, preferred embodiments of a management system and a management method according to the present invention will be described in detail with reference to the drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted.

  FIG. 1 shows a configuration of a mobile communication system 1 including a management system 10 (management system) according to the present embodiment. The mobile communication system 1 is a system that provides a mobile communication function to a mobile communication terminal (mobile device) (not shown). A mobile communication terminal is a device that is used by a user to connect to a mobile communication system (mobile communication network) by wireless communication and perform mobile communication. Specifically, the mobile communication terminal corresponds to a mobile phone or the like. For example, the mobile communication terminal establishes a call connection with the opposite node via the mobile communication system 1 and performs communication. The opposite node is, for example, another mobile communication terminal, a server device that provides various services to the mobile communication terminal, or a device (for example, MME (Mobility Management Entity), S-GW ( Serving Gateway), P-GW (PDN Gateway)) and the like. The mobile communication terminal can perform mobile communication by, for example, a user of the mobile communication terminal making a contract with a communication carrier of the mobile communication system 1. The mobile communication terminal may be the same as a conventional mobile communication terminal.

  As shown in FIG. 1, the management system 10 includes an orchestrator 20 (overall management node), a VNFM 30 (virtual communication function management node), and a VIM 40 (virtual resource management node). The mobile communication system 1 includes an OSS / BSS (Operations Support System / Business Support System) 50, an NFVI (NFV Infrastructure) 60, and a VNF (Virtual Network Function) 70 (virtual server, which will be described later). A function to be executed) and an EMS (Element Management System) 80. These components constitute a core network of the mobile communication system 1 (mobile communication network). Note that components that need to transmit and receive information to each other are connected by wire or the like so that information can be transmitted and received.

  In the mobile communication system 1 according to the present embodiment, a communication function is provided to a mobile communication terminal by a virtual server that operates in a virtual machine realized on a physical server. That is, the mobile communication system 1 is a virtualized mobile communication network. The communication function is provided to the mobile communication terminal by executing a communication process corresponding to the communication function by the virtual machine.

  The NFVI 60 is a physical resource, a virtualization layer, and a virtualization resource that constitute a virtualization environment. Physical resources include computing resources, storage resources, and transmission resources. The virtualization layer virtualizes physical resources and provides them to the VNF 70 (APL) (for example, a hypervisor). The virtualized resource is a virtualized infrastructure resource provided to the VNF 70. That is, the NFVI 60 is a virtualized resource that includes a physical server that is a physical server device that performs communication processing in the mobile communication system 1. The physical server includes a storage unit such as a CPU (core, processor), a memory, and a hard disk. Usually, a plurality of physical servers constituting the NFVI 60 are arranged together at a base such as a data center (DC). In the data center, the arranged physical servers are connected by a network inside the data center, and can exchange information with each other. The mobile communication system 1 is provided with a plurality of data centers. Data centers are connected by a network, and physical servers provided in different data centers can transmit / receive information to / from each other via the network.

  The VNF 70 is a virtual server that is a virtual communication processing node that executes communication processing (a function that executes communication processing that the VNF 70 has). The VNF 70 is realized in the NFVI 60. For example, the virtual machine (VM) technology is used for the VNF 70, the CPU provided in the NFVI 60 is allocated for the VNF 70, the virtual machine is realized on the allocated CPU, and the program is executed on the virtual machine. It is realized by. The VNF 70 is normally generated (implemented) according to the communication process to be executed. Further, the VNF 70 may be configured to include a plurality of VNFCs (Virtual Network Function Components) that are its constituent elements.

  The mobile communication system 1 includes one or more (or a plurality) VNFs 70. The VNF 70 corresponds to a node such as CSCF (Call Session Control Function) or AS (Application Server) in the IMS. Alternatively, the VNF 70 is a GPRS (General Packet Radio Service) system, which is one of mobile communication systems, for example, an SGSN (Serving GPRS Support Node), an LTE / EPC (Long Term Evolution / Evolved Packet Core) system, an MME ( It corresponds to a node such as Mobility Management Entity) or S-GW (Serving Gateway).

  The EMS 80 is a node that monitors and controls the VNF 70. The EMS 80 is also virtually realized in the NFVI 60 like the VNF 70. The EMS 80 is generated in association with the VNF 70 (for example, in a one-to-one relationship with the VNF 70 as shown in FIG. 1). The EMS 80 monitors and controls the associated VNF 70. The EMS 80 performs FCAPS (fault, configuration, billing, performance, security) management of the VNF 70. The EMS 80 may be virtually realized as described above, or may be physically realized in order to avoid management complexity in performing FCAPS management.

  The OSS / BSS 50 is a node that performs service management in the mobile communication system 1 and instructs the management system 10 regarding a communication function in the mobile communication system 1. For example, the OSS / BSS 50 instructs the management system 10 to activate a new communication function (communication service). In addition, the OSS / BSS 50 receives information from the EMS 80 and instructs the management system 10 or the EMS 80 based on the information. The OSS / BSS 50 can be operated by a telecommunications carrier related to the mobile communication system 1.

  The orchestrator 20 that is a component of the management system 10 is an overall management node (functional entity) that manages the entire NFVI 60 that is a virtualized resource. The orchestrator 20 receives an instruction from the OSS / BSS 50 (of which the OSS 51), and performs processing according to the instruction. The orchestrator 20 manages the entire virtualized resources of the mobile communication network for infrastructure and communication services. The orchestrator 20 realizes a communication service composed of a plurality of VNFs 70 at an appropriate location via the VNFM 30 and the VIM 40. For example, service life cycle management (specifically, for example, generation, update, scale control, event collection), resource distribution / reservation / allocation management, service / instance management, and policy management (in the entire mobile communication network) Specifically, for example, resource reservation / allocation, optimal placement based on geography / laws, etc.) is performed.

  The VNFM 30 that is a component of the management system 10 is a virtual communication function management node (functional entity) that manages the VNF 70. A plurality of VNFMs 30 may be provided in the mobile communication system 1. In that case, the VNFM 30 managed for each VNF 70 may be determined in advance. The VNFM 30 performs life cycle management of the VNF 70 (APL). The VNFM 30 performs overall control related to the virtualization of the VNF 70. For example, VNF70 instance generation, update, scale control, termination, and auto healing (automatic healing) are performed.

  The VIM 40 that is a component of the management system 10 is a virtual resource management node (functional entity) that manages each virtual resource (infrastructure resource) in a unit in which the VNF 70 in the NFVI 60 is realized. Specifically, resource allocation / update / recovery management, association between virtual resources and physics, and management of hardware resources and SW resources (hypervisor) list are performed. Usually, the VIM 40 performs management for each data center (station building). The management of virtual resources can be performed by a method according to the data center. Data center management methods (management resource implementation methods) include OPENSTACK (registered trademark) and vCenter. Normally, the VIM 40 is provided for each data center management method. In other words, the management system 10 includes a plurality of VIMs 40 that manage the respective virtual resources in units in which the VNFs 70 in the NFVI 60 are realized in different ways. Note that the units of virtual resources managed by different management methods do not necessarily have to be data center units.

  The orchestrator 20, the VNFM 30, and the VIM 40 are realized by executing a program on a physical server device (however, they are not limited to being realized on virtualization, and the management system is separated) Above, may be realized on virtualization). The orchestrator 20, the VNFM 30, and the VIM 40 may be realized by separate physical server devices, or may be realized by the same server device. The orchestrator 20, the VNFM 30, and the VIM 40 (programs for realizing) may be provided from different vendors.

  The architecture is based on that described in Non-Patent Document 1. In addition, the mobile communication system 1 may include components other than those described above in order to realize a mobile communication function. For example, the mobile communication system 1 includes a base station device and an open flow. A network (including virtualized ones as described above) or the like may also be included.

  Subsequently, functions according to the present embodiment which the management system 10 has will be described. As shown in FIG. 2, the VNFM 30 includes a VNFM surplus resource information DB 31 (surplus resource information database), a deployment instruction transmission unit 32 (deployment instruction transmission unit), a VNFM surplus resource information update unit 33 (surplus resource information update unit), The reservation cancellation unit 34 (reservation cancellation unit) and the reservation cancellation response transmission unit 35 (reservation cancellation response transmission unit) are provided. The VIM 40 includes a virtual server deployment unit 41 (virtual server deployment unit), a deployment completion response transmission unit 42 (deployment completion response transmission unit), and a VIM surplus resource information DB 43.

  The VNFM surplus resource information DB 31 is a database that stores surplus resource information related to surplus resources that are surplus virtual resources reserved in advance in the VIM 40.

  When receiving the notification that the virtual resources are insufficient from the VNF 70, the deployment instruction transmission unit 32 selects the reserved surplus resource virtual server based on the surplus resource information stored in the VNFM surplus resource information DB 31. An instruction to identify and deploy the identified virtual server is transmitted to the VIM 40.

  When the VNFM surplus resource information update unit 33 receives the deployment completion response from the VIM 40, the surplus resource stored in the VNFM surplus resource information DB 31 based on the virtual resource information related to the deployed virtual server included in the deployment completion response. Update information.

  When receiving the instruction to cancel the reservation of the surplus resource from the orchestrator 20, the reservation canceling unit 34 specifies the surplus resource information to cancel the reservation from the surplus resource information stored in the VNFM surplus resource information DB 31. Delete the specified surplus resource information.

  The reservation cancellation response transmission unit 35 transmits a reservation cancellation response to the orchestrator 20 when the reservation cancellation unit 34 cancels the reservation of the surplus resource.

  When receiving an instruction to deploy a virtual server from the VNFM 30, the virtual server deployment unit 41 deploys the virtual server.

  When a virtual server is deployed by the virtual server deployment unit 41, the deployment completion response transmission unit 42 transmits a deployment completion response that includes a virtual resource information related to the deployed virtual server to the VNFM 30. .

  The VIM surplus resource information DB 43 is a database that stores surplus resource information related to surplus resources that are surplus virtual resources reserved in advance in the VIM 40. The VIM 40 may further include a VIM surplus resource information update unit (not shown) that appropriately updates the surplus resource information stored in the VIM surplus resource information DB 43, similarly to the VNFM surplus resource information update unit 33 described above.

  The above is the function according to the present embodiment that the management system 10 has. In the following description of processing by the management system 10 using the sequence diagram, the functions of the orchestrator 20, the VNFM 30, and the VIM 40 according to this embodiment will be described in more detail. Further, the orchestrator 20, the VNFM 30, and the VIM 40 have functions that are not included in the above-described functional units, but descriptions of the functions are also included in the description of the processing by the management system 10 using the sequence diagram.

  FIG. 3 shows a hardware configuration of a server device that constitutes the orchestrator 20, the VNFM 30, and the VIM 40 included in the management system 10 according to the present embodiment. As shown in FIG. 3, the server device includes a CPU 101, a RAM (Random Access Memory) 102 and a ROM (Read Only Memory) 103, which are main storage devices, a communication module 104 for performing communication, and an auxiliary storage device such as a hard disk. The computer is configured to include a computer having hardware such as 105. By operating these components by a program or the like, the functions of the orchestrator 20, the VNFM 30, and the VIM 40 described above and later are exhibited. The orchestrator 20, the VNFM 30, and the VIM 40 may be configured by a computer system including a plurality of server devices. Further, nodes other than those described above included in the mobile communication system 1 may also be realized by a server device having the above hardware configuration. The above is the configuration of the management system 10 according to the present embodiment.

  Hereinafter, the flow of processing in the mobile communication system 1 will be described in detail using various sequence diagrams and table diagrams. First, FIG. 4 is a sequence diagram showing a processing flow at the time of Instantiation in the mobile communication system 1.

  First, the OSS / BSS 50 transmits a service generation request to the orchestrator 20 using the signal (1). The service generation request includes a service ID, a communication service, a performance condition, and an NW (network) condition. Here, the service ID is a number that uniquely identifies the generated service. The communication service is information for identifying the communication service. The performance condition is a normalized index value used to indicate the capability in the control (generation, augmentation, reduction, etc.) of the VNF 70 and the service configured by the VNF 70, and is negotiated between the OSS / BSS 50 and the VNFM 30 in advance. It shall be. The NW condition is a condition indicating the bandwidth of the NW connection with the DC. In the specific example of the present embodiment, “communication service 1” for the communication service, “100” for the performance condition, “DC connected to DC1 in a band of 5 Gbps or more” for the NW condition “DC1 connection, band 5 Gbps or more” Is set.

  Next, in procedure A, the orchestrator 20 extracts the VNF 70 and the VNFM 30 corresponding to the service. That is, the orchestrator 20 that has received the service request identifies the VNF 70 (virtualization function) and the VNFM 30 (management function) that constitute the received communication service from the operation data registered in advance. FIG. 5 is a table of operational data registered in advance in the orchestrator 20. FIG. 5A is a table showing a correspondence table between communication services and VNFs 70, and FIG. 5B is a table showing a correspondence table between VNFM 30 and VNFs 70 managed by VNFM 30. First, the orchestrator 20 extracts “VNF10” and “VNF21” as VNFs 70 constituting the communication service “communication service 1” obtained by the signal (1) from the table shown in FIG. Next, the orchestrator 20 extracts “VNFM1” that is the VNFM30 of the extracted “VNF10” from the table shown in FIG. 5B, and extracts “VNFM2” that is the VNFM30 of the extracted “VNF21”. .

  Next, in step B, the orchestrator 20 selects DC from the VNF 70 and the NW condition. Note that the procedure B is repeated for each VNF 70 unit or is performed in parallel. Hereinafter, “VNF10” extracted in the procedure A will be described. In the procedure B, the orchestrator 20 generates the “VNF10” extracted in the procedure A, the DC in which the “VNF10” can be placed, the NW condition obtained from the operation condition and the signal (1), and the DC Select using the connection configuration. FIG. 6 is a table of operational data registered in advance in the orchestrator 20. FIG. 6A is a table showing DCs that can be arranged for each VNF type, and FIG. 6B is a table showing DC topology information. First, the orchestrator 20 sets “DC2”, “DC3”, “DC4”, and “DC5” as DCs that can be placed in “VNF10” extracted in the procedure A from the table shown in FIG. As a candidate. Next, the orchestrator 20 connects to “DC1” as connection information satisfying the NW condition “DC1 connection, bandwidth 5 Gbps or higher” obtained from the signal (1) from the table shown in FIG. Connection information indicating that the DCs are “DC2”, “DC3”, and “DC4” is obtained. That is, it turns out that “DC5” does not satisfy the condition among the candidates obtained from the table shown in FIG. As described above, the orchestrator 20 obtains “DC2”, “DC3”, and “DC4” as candidate DCs.

  FIG. 7A is a table of the NW overall resource information DB accumulated by the orchestrator 20 by regular collection. Next, the orchestrator 20 reads the obtained resource information (corresponding DC record) of “DC2”, “DC3”, and “DC4” from the table shown in FIG. FIG. 7B is a table of resource information read (extracted) from the NW overall resource information DB.

  Next, with the signal (2), the orchestrator 20 transmits a necessary resource inquiry to “VNFM1” managing “VNF10” specified in the procedure A. The necessary resource inquiry includes a service ID, a combination of candidate DC and resource information, a VNF type, a VNF identification number, and a performance condition. Here, the service ID is the same as the service ID of the signal (1). The combination of the candidate DC and the resource information is the resource information extracted from FIG. The VNF type is extracted in the procedure A, and is “VNF10” here. The VNF identification number is a VNF identification number as a number for uniquely identifying the generated VNF 70, and is assumed to be “VNF10_001” here. The orchestrator 20 pays out the VNF identification number. The performance condition is the same as the performance condition of the signal (1), and is “100” here.

  An embodiment in which the combination of the candidate DC and the resource information is not included in the signal (2) is also possible. In this case, the orchestrator 20 reads the identification number of the VIM 40 that manages each DC from the table shown in FIG. 8 instead of extracting the resource information of each DC from FIG. FIG. 8 is a table showing a correspondence table between the VIM 40 and the DC managed by the VIM 40 registered in advance in the orchestrator 20. From the table shown in FIG. 8, the orchestrator 20 is a combination in which the VIM 40 of “DC2” is “VIM1”, the VIM 40 of “DC3” is “VIM1”, and the VIM 40 of “DC4” is “VIM2”. Is set to signal (2).

  Next, in procedure C, the VNFM 30 (“VNFM1”) selects an available DC. “VNFM1” adds the description of the surplus resource to the item of the requirement condition of VNF70. In addition, “VNFM1” also determines a surplus resource deployment destination DC when selecting a DC.

  Specifically, first, when the VIM identification number is set instead of the resource information in the received signal (2), “VNFM1” requests and collects the resource information of each DC from the VIM 40 by itself. Specifically, “VNFM1” inquires the resource information of “DC2” and “DC3” to “VIM1” received by the signal (2) from the combination set in the signal (2), and “VIM2” Is inquired about resource information of “DC4”, and as a result, the table shown in FIG. 7B is obtained.

  “VNFM1” obtained from the signal (2) or the table shown in FIG. 7B which is DC resource information by the above procedure is the detailed information of “VNF10” set in the VNF type of the signal (2). Are read from the VNF detailed information DB registered in advance in “VNFM1”. FIG. 9 is a table of the VNF detailed information DB registered in advance in the VNFM 30 and indicating the request conditions for each VNF 70. As shown in the table of FIG. 9, the VNF detailed information DB registers the VNF internal structure, VM resource information according to performance conditions, NW resource information, function information, and surplus resource information to be provided for each VNF 70. Has been. “VNFM1” refers to the resource information, function information, and surplus resource information necessary for the performance condition “100” of the VNF type “VNF10” received by the signal (2) from the read VNF detailed information DB. Then, “VNFM1” uses the resource information and the function information that has been referred to as the available resource information and the provided function of the resource information (table diagram shown in FIG. 7B) obtained by the signal (2) or the above procedure. Compare and extract available DCs. Specifically, “VNFM1” requires “function 1” and “function 2” from the table shown in FIG. 9, and “function 1” from the table shown in FIG. 7B. The DCs that can provide “function 2” are determined to be “DC2” and “DC3”.

  Next, “VNFM1” derives resource information necessary for generating the VNF 70 with resources provided by the available DC. Specifically, “VNFM1” can provide CPU performance “DC2” is “High” and “Low”, and “DC3” is “Low” based on the table shown in FIG. 7B. Determine. “VNFM1” compares this with the CPU performance of the table shown in FIG. 9, and obtains the table shown in FIG. 10A as a combination of resource information that can be taken by “DC2” and “DC3”. FIG. 10A is a table of a necessary resource information list for each usable DC. “VNFM1” also extracts DC and necessary resource information for surplus resources in the same manner, and obtains the table shown in FIG. FIG. 10B is a table of the necessary resource information list for surplus resources for each usable DC. Next, “VNFM1” stores the service ID of the signal (2), the VNF type, the VNF identification number, and the table shown in FIG. 9 which is detailed information.

  Next, the VNFM 30 (“VNFM1”) transmits a necessary resource response to the orchestrator 20 using the signal (3). The necessary resource response includes a necessary resource information list for each usable DC and a surplus resource necessary resource information list (surplus resource DC and necessary resource information) for each usable DC. Specifically, the required resource response includes a table diagram shown in FIG. 10A and a table diagram shown in FIG. As described above, the surplus resource DC and the necessary resource information are handled separately from the normal request resources.

  Next, in step D, the orchestrator 20 selects the reservation destination DC and VIM 40. Specifically, first, the orchestrator 20 adds the necessary resource information list (table diagram shown in FIG. 10A) for each usable DC received by the signal (3) to the table shown in FIG. The table shown in FIG. 11B to which priority is given based on the priority index is obtained. FIG. 11A is a table of DC selection priority indexes registered in advance in the orchestrator 20. FIG. 11B is a table of a necessary resource information list for each usable DC that has been prioritized. Next, the orchestrator 20 makes a reservation to the VIM 40 that manages the DC in the order of priority. Here, the orchestrator 20 first selects “combination 2” of “DC2” having the highest priority in the table shown in FIG. Next, the orchestrator 20 determines that “VIM1” is managing “DC2” from the table shown in FIG.

  Next, the orchestrator 20 transmits a resource reservation request to “VIM1” determined in the procedure D by the signal (4). The resource reservation request includes necessary resource information. The necessary resource information is specifically a table diagram shown in FIG. 12 which is resource information of “DC2” and “combination 2” selected in the procedure D. FIG. 12 is a table of necessary resource information.

  Next, in procedure E, the VIM 40 (“VIM1”) determines whether or not reservation is possible. Specifically, first, “VIM1” can secure the table diagram shown in FIG. 12, which is a necessary resource requested in signal (4), in “DC2” set in signal (4). Check based on the resource information DB in the management area to determine whether the resource can be secured (reserved).

  Next, “VIM1” transmits a resource reservation response to the orchestrator 20 by a signal (5). The resource reservation response includes a reservation number. Specifically, when it is determined that the resource can be secured in the procedure E, “VIM1” reserves the resource, pays out a reservation number, and transmits it to the orchestrator 20. On the other hand, if “VIM1” determines that the resource cannot be secured, it returns an error to the orchestrator 20.

  Next, in procedure F, the orchestrator 20 determines whether or not the reservation is successful. Specifically, the orchestrator 20 determines that the reservation is successful when the reservation number is received by the signal (5). On the other hand, the orchestrator 20 determines that the reservation is not successful when an error is received by the signal (5). If the orchestrator 20 determines that the reservation is not successful, the orchestrator 20 returns to the procedure D and makes a reservation to the VIM 40 for the next priority item.

  Next, the orchestrator 20 that determines that the reservation is successful in the procedure F by signal (6) transmits a VNF 70 generation request to “VNFM1”. The VNF 70 generation request includes a service ID, a VNF identification number, a reservation destination VIM, a reservation number, and reservation resource information. Here, the service ID is the same as the service ID of the signal (1). The VNF identification number is the same as the VNF identification number of the signal (2). The reservation destination VIM is the VIM 40 that is the transmission source of the signal (5). The reservation number is the reservation number of the signal (5). The reserved resource information is necessary resource information transmitted in the procedure D.

  Next, in procedure G, “VNFM1” associates VNFC and VM. Specifically, “VNFM1” reads out the table shown in FIG. 9 which is the detailed information stored in the procedure C from the service ID and VNF identification number received by the signal (6), and receives the signal (6). The arrangement / activation information and NW configuration information corresponding to the model numbers “001” and “005” of the received reservation resource information (table diagram shown in FIG. 12) are determined, and the VM identification number is issued to each VM to be generated, Give. FIG. 13 is a table diagram showing the arrangement / activation information and NW configuration information that are generated by “VNFM1” and notified to the VIM 40.

  Next, in signal (7), “VNFM1” transmits a VNF generation request to “VIM1” that is the reservation destination VIM received in signal (6). The VNF generation request includes a reservation number, arrangement / activation information, and NW configuration information. Here, the reservation number is the reservation number received by the signal (6). The placement / activation information and the NW configuration information are the placement / activation information and the NW configuration information determined in the procedure G.

  Next, in the procedure H, “VIM1” activates the VNF 70. Specifically, first, “VIM1” specifies the resource of “DC2” secured in the procedure E as a resource for starting the VNF 70 from the reservation number received by the signal (7). Next, “VIM1” reads the image files of VM and VNF 70 into “DC2” based on the arrangement / startup information and NW configuration information received by the signal (7), and generates / starts up. Next, “VIM1” assigns “external IP address 01” and “external IP address 02” to the VM as the number of external addresses designated by the signal (7) from the pre-assigned external IP address band. . Next, “VIM1” is a reservation number, a DC number, a VM identification number of “VNFM1”, an identifier of a physical device (HW), assigned resource information, and an identification of the source VNFM 30 of the signal (7). The table shown in FIG. 14 in which numbers are associated is stored. FIG. 14 is a table of reservation numbers, VM deployment destination physical devices, and allocation resource information.

  Next, in procedure I, the orchestrator 20 selects the surplus resource reservation destination DC and VIM 40. The orchestrator 20 selects the DC and VIM 40 that reserve the surplus resource from the surplus resource DC and the necessary resource information after the normal VNF 70 is deployed. Specifically, the orchestrator 20 first adds the necessary resource information list for surplus resources for each usable DC received by the signal (3) (table diagram shown in FIG. 10B) to FIG. 11A. Priorities are given based on the priority index of the table diagram shown in FIG. 15 to obtain the table diagram shown in FIG. FIG. 15A is a table of the necessary resource information list for surplus resources for each usable DC that has been prioritized. Next, the orchestrator 20 makes a reservation to the VIM 40 that manages the DC in the order of priority. Here, the orchestrator 20 first selects “DC2” having the highest priority in the table shown in FIG. Next, the orchestrator 20 determines that “VIM1” is managing “DC2” from the table shown in FIG.

  Next, the orchestrator 20 transmits a surplus resource reservation request to “VIM1” determined in the procedure I by the signal (8). The surplus resource reservation request includes necessary resource information for surplus resources. Here, the necessary resource information for surplus resources is the necessary resource information for surplus resources of “DC2” selected in the procedure I (table diagram shown in FIG. 15B).

  Next, in procedure J, “VIM1” determines whether or not reservation is possible. Specifically, first, “VIM1” can secure the table shown in FIG. 15B, which is a necessary resource requested by the signal (8), in “DC2” set in the signal (8). Whether or not resources can be secured (reserved). Next, when it is determined that the resource can be secured, “VIM1” reserves the resource and issues a surplus resource reservation number. Next, “VIM1” associates the surplus resource reservation number with the required required resource and stores it in the VIM surplus resource information DB. FIG. 16 is a table of the VIM surplus resource information DB of “VIM1”. In the table shown in FIG. 16, “Reserved VNFM 30” is blank.

  Next, “VIM1” transmits a surplus resource reservation response to the orchestrator 20 by a signal (9). The surplus resource reservation response includes a surplus resource reservation number. In this way, a normal resource reservation number and a surplus resource reservation number are distinguished. Specifically, when it is determined that the resource can be secured in the procedure J, “VIM1” transmits the surplus resource reservation number that has been paid out to the orchestrator 20. On the other hand, if “VIM1” determines that the resource cannot be secured, it returns an error to the orchestrator 20.

  Next, in step K, the orchestrator 20 determines whether or not the reservation is successful. Specifically, the orchestrator 20 determines that the reservation is successful when the surplus resource reservation number is received by the signal (9). On the other hand, the orchestrator 20 determines that the reservation is not successful when an error is received by the signal (9). If the orchestrator 20 determines that the reservation is not successful, the orchestrator 20 returns to Procedure I and makes a reservation to the VIM 40 for the next priority item.

  Next, the orchestrator 20 that has determined that the reservation has succeeded in the procedure K with the signal (10) transmits a surplus resource reservation request to “VNFM1”. The surplus resource reservation request includes a service ID, a VNF identification number, a reservation destination VIM, a surplus resource reservation number, reserved surplus resource information, and DC providing function information. Here, the service ID is the service ID of the signal (1). The VNF identification number is the VNF identification number of the signal (2). The reservation destination VIM is the VIM 40 that is the communication source of the signal (9). The surplus resource reservation number is the surplus resource reservation number received by the signal (9). The reserved surplus resource information is the necessary resource information (table diagram shown in FIG. 15B) transmitted in the procedure I. The DC providing function information is “function 1” and “function 2” which are providing function information corresponding to DC.

  Next, in the procedure L, “VNFM1” stores the reservation destination VIM, the surplus resource reservation number, and the reserved surplus resource information in the DB. Specifically, “VNFM1” first summarizes the reservation destination VIM, surplus resource reservation number, VNF identification number, reserved surplus resource information, and DC providing function information received by the signal (10). And stored in the VNFM surplus resource information DB. FIG. 17 is a table of the VNFM surplus resource information DB of “VNFM1”. Note that “VNFM1” may store only the reservation destination VIM, the VNF identification number, and the surplus resource reservation number in the VNFM surplus resource information DB as shown in the table of FIG. In this case, “VNFM1” acquires the surplus resource information from the VIM 40 each time based on the surplus resource reservation number. FIG. 18 is another table of the VNFM surplus resource information DB of “VNFM1”.

  Next, “VNFM1” that has updated the VNFM surplus resource information DB by signal (11) transmits surplus resource reservation completion to “VIM1”. The surplus resource reservation completion includes a surplus resource reservation number. Here, the surplus resource reservation number is a surplus resource reservation number included in the signal (10).

  Next, in the procedure M, “VIM1” stores the surplus resource reservation number and the VNFM 30 in association with each other in the DB. Specifically, “VIM1” extracts a record corresponding to the surplus resource reservation number received by the signal (11) from the VIM surplus resource information DB (table diagram shown in FIG. 16), and sets “reserved VNFM30” as “VIM1”. Update as “VNFM1” of the transmission source. FIG. 19 is a table of the VIM surplus resource information DB of “VIM1” updated as described above.

  Next, FIG. 20 is a sequence diagram showing a flow of processing when a resource enhancement request is issued from the VNF 70 in the mobile communication system 1.

  First, the VNF 70 transmits a resource shortage notification to the VNFM 30 using the signal (1). The resource shortage notification includes a VNF identification number, a shortage VNFC, and an additional necessary resource condition. Specifically, due to an increase in load, the VNF identification number “VNF10 — 001” determines that the resource of its component “VNFC100” is insufficient, and “VNFM1” managing this “VNF10 — 001” Resource shortage notification. At this time, the resource shortage notification includes “VNF10 — 001” that is the identification number of the VNF 70 that is short of resources, “VNFC100” that is an internal function unit, and the table shown in FIG. 21 that is an additional necessary resource condition. FIG. 21 is a table of additional necessary resource conditions notified by “VNF10_001” to “VNFM1”.

  Next, in procedure A, the VNFM 30 (“VNFM1”) compares the surplus resource information with the additional necessary resource condition. Specifically, first, the signal (1) “VNFM1” received includes an additional necessary resource condition and a record whose VNF identification number of the VNFM surplus resource information DB (table diagram shown in FIG. 17) is “VNF10_001”. A comparison is made to determine whether the surplus resource of “VNF10 — 001” satisfies the additional necessary resource condition. When the VNFM surplus resource information DB has only the reservation destination VIM, the VNF identification number, and the surplus resource reservation number as shown in the table of FIG. 18, “VNFM1” makes an inquiry to the corresponding VIM 40, It is determined whether or not the surplus resources are satisfied by acquiring the data in the table shown in FIG. 16 corresponding to the surplus resource reservation number.

  Next, a process when it is determined that the surplus resources are sufficient in the procedure A will be described.

  First, “VNFM1” is a request of the VNF10 held by “VNFM1” for the VNF identification number “VNF10_001” received by the signal (1), the internal function unit “VNFC100”, and the additional necessary resource condition. Referring to the conditions (table diagram shown in FIG. 9), the corresponding arrangement / startup information and NW configuration information are determined, and the VM identification numbers (“VM_003” and “VM_004”) are issued and assigned to each VM to be generated . Next, “VNFM1” uses these to create a table of arrangement / startup information and NW configuration information shown in FIG. FIG. 22 is a table of arrangement / activation information and NW configuration information to be notified to the VIM 40.

  Next, with a signal (2), “VNFM1” transmits a VNFC generation request to the reservation destination “VIM1”. The VNFC generation request includes “xxxx” which is the surplus resource reservation number received by the signal (1), the arrangement / activation information of the table diagram shown in FIG.

  Next, in procedure B, the VIM (“VIM1”) activates the VM image file. Specifically, “VIM1” searches the VIM surplus resource information DB (table diagram shown in FIG. 16) of “VIM1” using the surplus resource reservation number “xxxx” received by the signal (2), and corresponds. Specify surplus resource information. Next, “VIM1” reads a VM image file into “DC2” based on the arrangement / activation information, NW configuration information received by the signal (2), and the specified surplus resource information, and generates / activates it. . Next, “VIM1” uses “external IP address 03” and “external IP address 04” as VM “VM — 003” as the number of external addresses designated by the signal (2) from the external IP address band assigned in advance. "External IP address 05" and "External IP address 06" are assigned to VM "VM_004". Next, “VIM1” includes the surplus resource reservation number, the DC number, the VM identification number, the physical device (HW) identifier, the allocated resource information, and the identification number of the transmission source VNFM of the signal (2). The table is stored in association with the table shown in FIG. FIG. 23 is a table of reservation numbers, VM deployment destination physical devices, and allocation resource information. Next, “VIM1” subtracts the used resources from the surplus resource information and updates the VIM surplus resource information DB (updates the reserved surplus resource information corresponding to the surplus resource reservation number ( Subtract the additional VM setting))). FIG. 24 is a table of the updated VIM surplus resource information DB.

  Next, with the signal (3), “VIM1” transmits a VNFC generation response to “VNFM1”. The VNFC generation response includes a surplus resource reservation number and updated reservation surplus resource information. If the VNFM surplus resource information DB has only the reservation destination VIM, the VNF identification number, and the surplus resource reservation number as shown in the table of FIG. 18, it is not necessary to transmit surplus resource information.

  Next, in the procedure C, “VNFM1” updates the VNFM surplus resource information DB. Specifically, “VNFM1” receives the signal (3), and updates the surplus resource information of the corresponding surplus resource reservation number (updates the reserved surplus resource information corresponding to the surplus resource reservation number (additional VM setting amount). Subtract)). FIG. 25 is a table of the updated VNFM surplus resource information DB.

  Next, with the signal (4), “VNFM1” transmits a resource enhancement completion response to “VNF10_001”. The resource augmentation completion response includes the VNF identification number.

  Subsequently, a process when it is determined in step A that there is not enough surplus resources will be described.

  First, “VNFM1” needs to be added by comparing the additional necessary resource condition (table diagram shown in FIG. 21) with the record of the VNF identification number “VNF10 — 001” in the VNFM surplus resource information DB (table diagram shown in FIG. 26). It is determined whether or not the surplus resource “VNF10 — 001” satisfies the resource condition. At this time, it is determined that there are insufficient reserved surplus resources for expansion. Next, “VNFM1” determined to be resource shortage performs resource reservation again through the orchestrator 20 without using surplus resources, and thus once cancels the surplus resource reservation status.

  Next, “VNFM1” transmits a reserved surplus resource deletion request to “VIM1” by a signal (5). The reserved surplus resource deletion request includes a surplus resource reservation number “xxxx”.

  Next, in procedure D, “VIM1” updates the VIM surplus resource information DB. Specifically, “VIM1” receives the signal (5), and deletes the record corresponding to the surplus resource reservation number indicated in the signal (5) from the VIM surplus resource information DB to cancel the reservation. That is, “VIM1” deletes the record of the surplus resource reservation number “xxxx” in the table diagram of the VIM surplus resource information DB shown in FIG. Next, since “VIM1” has canceled the reservation, the resource information DB in the management area of “VIM1” is updated by adding an amount of resources corresponding to the deleted reserved surplus resource information (corresponding to the surplus resource reservation number). Delete reserved surplus resource information).

  Next, with the signal (6), “VIM1” transmits a reservation deletion response to “VNFM1”. The reservation deletion response includes a surplus resource reservation number “xxxx”.

  Next, in the procedure E, “VNFM1” updates the VNFM surplus resource information DB. Specifically, “VNFM1” receives the signal (6) and deletes the record of the VNFM surplus resource information DB corresponding to the surplus resource reservation number “xxxx”. That is, “VNFM1” deletes the record corresponding to the surplus resource reservation number “xxxx” in the table diagram of the VNFM surplus resource information DB shown in FIG. 28 (the reserved surplus resource information corresponding to the surplus resource reservation number is deleted).

  Next, “VNFM1” transmits a resource enhancement failure response to “VNF10 — 001” by signal (7). The resource augmentation failure response includes the VNF identification number.

  Next, “VNF10_001” having received the signal (7) through the signal (8) transmits a resource shortage notification to the OSS / BSS 50. The resource shortage notification includes a VNF identification number, a shortage VNFC, and an additional necessary resource condition.

  Next, the OSS / BSS 50 that has received the signal (8) performs scale-out. Specifically, the OSS / BSS 50 executes a request for deployment of the VNF 70 by executing procedures B to M in the sequence diagram at the time of Instantiation shown in FIG.

  Next, FIG. 29 is a sequence diagram showing a processing flow when the surplus resources managed by the VNFM 30 can be shared by different VNFs 70 at the time of resource enhancement request from the VNF 70 in the mobile communication system 1.

  As a premise, in the sequence diagram at the time of Instantiation shown in FIG. 4, it is assumed that VNFM 30 can add a priority to the reserved surplus resource for each VNF identification number in procedure L. Here, the higher the priority value, the higher the priority. Using this priority, when the reserved surplus resource of a certain VNF identification number is insufficient, the reserved surplus resource of the VNF identification number having a lower priority than itself can be used.

  First, in procedure A, “VNFM1” compares the surplus resource information with the additional necessary resource condition. Specifically, “VNFM1” compares the additional necessary resource condition (table diagram shown in FIG. 21) with the record of the VNF identification number “VNF10 — 001” in the table diagram of the VNFM surplus resource information DB shown in FIG. It is determined whether the extra resource of “VNF10 — 001” satisfies the additional necessary resource condition. At this time, it is determined that there are insufficient reserved surplus resources for expansion. Next, “VNFM1” searches the VNFM surplus resource information DB for a reserved surplus resource having a lower priority than “VNF10 — 001”. At this time, surplus resources of “VNF12_001” and “VNF11_001” are found. Next, “VNFM1” determines whether or not the additional necessary resource condition is satisfied in order from the surplus resource with the lowest priority among the surplus resources found above. At this time, it is determined that the reserved surplus resource of “VNF11_001” having the lowest priority satisfies the condition.

  Next, in the signal (9), “VNFM1” sends the confirmation of the correspondence between VNF, DC, and NW to the orchestrator 20 in order to confirm whether “VNF10 — 001” can be deployed in the reserved surplus resource of “VNF11_001”. . The confirmation of the correspondence between the VNF, the DC, and the NW includes the VNF identification number “VNF10 — 001”, the reservation surplus resource information “DC4” determined to satisfy the resource condition in the above procedure, and the surplus resource reservation number. And “zzz”.

  Next, in step F, the orchestrator 20 confirms the DC and NW conditions necessary for the VNF 70. Specifically, the orchestrator 20 can arrange DCs that can be arranged for each VNF type of the orchestrator 20 with respect to the VNF identification number “VNF10 — 001” and the reservation destination DC “DC4” of the received signal (9) (FIG. 6A ), It is determined whether “VNF10” can be deployed in “DC4”. As a result, it is determined that deployment is possible. Further, the orchestrator 20 starts from the VNF identification number “VNF10 — 001” of the received signal (9), and the NW condition “DC1 connection, bandwidth of 5 Gbps or more” given when this VNF 70 is deployed (sequence diagram at the time of Instantiation shown in FIG. 4) In order to determine whether or not the reservation destination DC “DC4” of the signal (9) satisfies this condition (the condition given by the signal (1)) (see FIG. 6B). Reference is made to the table diagram shown in FIG. As a result, it is determined that deployment is possible. Next, the orchestrator 20 notifies the “VNFM1” of “VNF deployment possible” if it is determined that deployment is possible in both the above determinations, and “VNF deployment impossible” if it is determined that either of them is impossible.

  That is, by the signal (10), the orchestrator 20 transmits a correspondence confirmation response of VNF, DC, and NW to “VNFM1”. The VNF / DC / NW correspondence confirmation response includes a VNF identification number “VNF10 — 001”, a reservation destination DC “DC4”, a surplus resource reservation number “zzz”, and VNF deployment availability “VNF deployment”. Includes "Yes".

  Next, in procedure G, it is determined whether “VNFM1” can be deployed with VNF. Specifically, when “VNFM1” is notified by the signal (10) that deployment is not possible, the procedure returns to procedure A and the procedure is repeated for the next priority resource. On the other hand, if “VNF101” is notified that “VNF10 — 001” can be deployed to “DC4” by the signal (10), “VNFM1” refers to the requirements for “VNF10” (table diagram shown in FIG. 9) and Activation information and NW configuration information are determined, and VM identification numbers (“VM — 003” and “VM004”) are issued and assigned to each VM to be generated. Next, “VNFM1” uses these to create arrangement / startup information and NW configuration information which are the table diagram shown in FIG.

  Next, with the signal (11), “VNFM1” transmits a VNFC generation request to “VIM2” corresponding to “VNF11_001”. The VNFC generation request includes the surplus resource reservation number “zzz”, the arrangement / activation information and the NW configuration information that are the table shown in FIG.

  Next, in procedure H, “VIM2” activates the VM image file. Specifically, “VIM2” searches the VIM surplus resource information DB of “VIM2” in the table diagram shown in FIG. 31 with the surplus resource reservation number “zzz” received by the signal (11), and the corresponding surplus Identify resource information. Next, “VIM2” uses the placement / startup information received by the signal (11), the NW configuration information (table diagram shown in FIG. 22), and the surplus resource information specified in the above procedure to “DC2”. Reads an image file, generates it, and starts it.

  Next, “VIM2” uses “external IP address 03” and “external IP address 04” as VM “VM — 003” as the number of external addresses designated by the signal (11) from the external IP address band assigned in advance. "External IP address 05" and "External IP address 06" are assigned to VM "VM_004". Next, “VIM2” correlates the surplus resource reservation number, the DC number, the VM identification number, the physical device (HW) identifier, the allocated resource information, and the transmission source VNFM of the signal (11). The table shown in FIG. 32 is stored. FIG. 32 is a table showing a reservation number, a VM deployment destination physical device, and allocation resource information. Next, “VIM2” subtracts the used resources from the surplus resource information and updates the VIM surplus resource information DB corresponding to the generation of the VM (updates the reserved surplus resource information corresponding to the surplus resource reservation number ( Subtract the additional VM setting))). FIG. 33 is a table showing the updated VIM surplus resource information DB.

  Next, with the signal (12), “VIM2” transmits a VNFC generation response to “VNFM1” as a VNFC generation response. The VNFC generation response includes a surplus resource reservation number “zzz” and updated reservation surplus resource information.

  Next, in the procedure I, “VNFM1” updates the VNFM surplus resource information DB. Specifically, “VNFM1” receives the signal (12) and updates the surplus resource information of the corresponding surplus resource reservation number (updates the reserved surplus resource information corresponding to the surplus resource reservation number (additional VM setting amount). Subtract)). FIG. 34 is a table showing the updated VNFM surplus resource information DB.

  Next, “VNFM 1” transmits a resource enhancement completion response to the VNF 70 with the signal (13). The resource augmentation completion response includes “VNF10_001” that is the VNF identification number.

  Next, FIG. 35 is a sequence diagram showing the flow of processing when the surplus resources of the VNFM 30 are available when the surplus resources are excluded at the instant of instantiation in the mobile communication system 1. This sequence diagram shows a sequence in the case where the VNFM 30 that has received the resource inquiry has surplus resources. The part where the reserved surplus resource is deleted may be used for generating the VNF 70 only for a part of the resource, and the amount of the reserved surplus resource may be subtracted and updated accordingly. First, as a premise, the service generation request of the signal (1) in the sequence diagram at the time of Instantiation shown in FIG. 4 includes the service ID “s1”, the NW condition “DC1 connection, bandwidth 5 Gbps or more”, and the VNF type “VNF10”. And a VNF identification number “VNF10 — 002” and a performance condition “100”. The first process is the same as the procedure A, the procedure B, and the signals (2) and (2a) in the sequence diagram at the instantiation shown in FIG.

  Next, in procedure C, “VNFM1” compares the resource information of the candidate DC (table diagram shown in FIG. 36) with the requirement condition of “VNF10” (table diagram shown in FIG. 9), but the memory capacity It is determined that VNF deployment is not possible due to insufficient capacity. FIG. 36 is a table showing the resource information extracted from the NW overall resource information DB.

  Next, in the procedure N, “VNFM1” refers to the VNFM surplus resource information DB. Specifically, “VNFM1” refers to its own VNFM surplus resource DB, which is the table diagram shown in FIG. 37, and there is no reserved surplus resource information that satisfies the requirement condition of “VNF10” (table diagram shown in FIG. 9). (A determination is made as to whether a resource satisfying the VNF 70 requirement is reserved as a surplus resource). When priority is used, “VNFM1” searches in order from the lowest priority. Here, “VNFM1” selects “VNF11 — 001” of “VIM2” and the surplus resource reservation number “zzz”.

  Next, in the signal (11), “VNFM1” transmits to the orchestrator 20 a confirmation of the correspondence between VNF 70, DC, and NW in order to confirm whether “VNF10” can be deployed in the reserved surplus resource of “VNF11_001”. . Specifically, the confirmation of the correspondence between the VNF 70, the DC, and the NW includes the VNF identification number “VNF10 — 002” desired to be deployed this time, the reserved surplus resource information destination DC “DC4” determined to satisfy the resource conditions in the above procedure, The surplus resource reservation number “zzz” is included.

  Next, in procedure O, the orchestrator 20 confirms the DC and NW conditions necessary for the VNF 70. Specifically, the orchestrator 20 can arrange DCs that can be arranged for each VNF type possessed by the orchestrator 20 with respect to the VNF identification number “VNF10 — 002” and the reservation destination DC “DC4” of the received signal (1) (FIG. 6 ( With reference to the table shown in a), it is determined whether “VNF10” can be deployed in “DC4”. As a result, it is determined that deployment is possible. Further, the orchestrator 20 starts from the VNF identification number “VNF10 — 002” of the received signal (9), and the NW condition “DC1 connection, bandwidth of 5 Gbps or more” given at the time of deployment of this VNF (sequence diagram at the time of Instantiation shown in FIG. 4) In order to determine whether or not the reservation destination DC “DC4” of the signal (9) satisfies this condition (the condition given by the signal (1)), the DC topology information (FIG. 6 (b) )). As a result, it is determined that deployment is possible. Next, the orchestrator 20 notifies the “VNFM1” of “VNF deployment possible” if it is determined that deployment is possible in both the above determinations, and “VNF deployment impossible” if it is determined that either of them is impossible.

  That is, the orchestrator 20 transmits a response corresponding to VNF 70, DC, and NW to “VNFM1” using the signal (2). The correspondence response between the VNF 70, the DC, and the NW includes a VNF identification number “VNF10 — 002”, a reservation destination DC “DC4”, a surplus resource reservation number “zzz”, and whether or not VNF deployment is possible “VNF deployment is possible”.

  Next, in procedure P, “VNFM1” determines whether or not VNF deployment is possible. Specifically, when “VNFM1” is notified by the signal (2) that deployment is not possible, the procedure returns to Procedure N, and the procedure is repeated for the next priority resource. On the other hand, if “VNFM1” is notified that “VNF10 — 002” can be deployed to “DC4” by the signal (2), the resource reservation is performed via the orchestrator 20, so the reservation status of the surplus resources is once canceled. . First, “VNFM1” determines that the reservation destination VIM 40 is “VIM2” based on the surplus resource reservation number “zzz” notified by the signal (2) from the table shown in FIG.

  Next, with a signal (3), “VNFM1” transmits a reservation surplus resource deletion request to “VIM2”. The reserved surplus resource deletion request includes a surplus resource reservation number “zzz”.

  Next, in procedure Q, “VIM2” deletes it from the VIM surplus resource information DB. Specifically, “VIM2” deletes the reserved surplus resource information corresponding to the surplus resource reservation number “zzz” received by the signal (3). That is, the record corresponding to the surplus resource reservation number “zzz” is deleted from the VIM surplus resource information DB shown in FIG. 38 (reservation surplus resource information corresponding to the surplus resource reservation number is deleted). This is the same as the procedure D in the sequence diagram at the time of a resource enhancement request from the VNF 70 shown in FIG. Next, “VIM2” adds and updates an amount of resources corresponding to the deleted reserved surplus resource information in the management area resource information DB of “VIM2” in accordance with the reservation deletion.

  Next, with the signal (4), “VIM2” transmits a reservation deletion response to “VNFM1”. The reservation deletion response includes a surplus resource reservation number “zzz” and a reservation destination DC “DC4”.

  Next, in the procedure R, “VNFM1” deletes from the VNFM surplus resource information DB. Specifically, “VNFM1” is reserved surplus resource information (table diagram shown in FIG. 37) corresponding to the reservation destination DC “DC4” and surplus resource reservation number “zzz” received by the signal (4), and VNF70. From the required conditions (table diagram shown in FIG. 9) for each, a table diagram of the necessary resource information list shown in FIG. 39 is created. Next, “VNFM1” deletes the reserved surplus resource information corresponding to the surplus resource reservation number “zzz” received by the signal (4) from the VNFM surplus resource information DB. That is, “VNFM1” deletes the record corresponding to the surplus resource reservation number “zzz” in the table of the VNFM surplus resource information DB shown in FIG. 40 (deletes the reserved surplus resource information corresponding to the surplus resource reservation number). ).

  Next, “VNFM 1” transmits a necessary resource response to the orchestrator 20 with a signal (5). The required resource response includes a required resource information list which is a table diagram shown in FIG. The subsequent procedure is the same as the procedures D to H in the sequence diagram during Instantiation shown in FIG. Procedures I to M, which are reserved portions of surplus resources, are not performed because of insufficient resources.

  Next, FIG. 41 is a sequence diagram showing the flow of processing when there is a shortage of resources excluding surplus resources during instantiation in the mobile communication system 1 and surplus resources of other VNFMs are available. This sequence diagram shows a sequence in the case where the VNFM 30 that has received the resource inquiry does not have a surplus resource. The part where the reserved surplus resource is deleted may be used for generating the VNF 70 only for a part of the resource, and the amount of the reserved surplus resource may be subtracted and updated accordingly. The first process is the same up to procedure C in the sequence diagram shown in FIG.

  Next, in the procedure N, “VNFM1” refers to the VNFM surplus resource information DB. Specifically, “VNFM1” refers to its own VNFM surplus resource DB, which is the table diagram shown in FIG. 42, and there is no reserved surplus resource information that satisfies the requirement condition of “VNF10” (table diagram shown in FIG. 9). I search, but I can't find it.

  Next, “VNFM 1” transmits a securement failure response to the orchestrator 20 with the signal (1). The reservation failure response includes “VNF10 — 002” which is a VNF identification number.

  Next, in step S, the orchestrator 20 selects a DC and a VIM 40 that can deploy the VNF 70. Specifically, the orchestrator 20 determines the failure to secure the resource with the VNF identification number “VNF10 — 002” from the received signal (1). Next, the orchestrator 20 selects a DC on which “VNF10 — 002” can be placed from DCs that can be placed for each VNF type (table diagram shown in FIG. 6A). That is, the orchestrator 20 selects “DC2”, “DC3”, “DC4”, and “DC5. The orchestrator 20 also has an NW condition“ DC1 connection, bandwidth 5 Gbps or more corresponding to “VNF10 — 002”. “DC2”, “DC3”, and “DC4” that satisfy the conditions are selected with reference to the topology information between DCs (table diagram shown in FIG. 6B). The VIM 40 corresponding to the DC selected from the VIM 40 and the DC managed by the VIM 40 (table diagram shown in Fig. 8) is selected, that is, the orchestrator 20 selects "VIM1" and "VIM2".

  Next, the orchestrator 20 transmits a surplus resource reservation status request to the selected “VIM1” and “VIM2” using the signal (2). The surplus resource reservation status request includes DC lists “DC2”, “DC3”, and “DC4”.

  Next, in procedure T, the VIM 40 extracts surplus resource information corresponding to DC. Specifically, the VIMs “VIM1” and “VIM2” that received the signal (2) are the surplus resources corresponding to the DC lists “DC2”, “DC3”, and “DC4” of the signal (2). Information is extracted from its own VIM surplus resource information DB. 43A is a table diagram of the VIM surplus resource information DB stored in “VIM1”, and FIG. 43B is a table diagram of the VIM surplus resource information DB stored in “VIM2”. Here, “VIM1” extracts surplus resource information of surplus resource reservation number “xxxx”, and “VIM2” extracts surplus resource information of surplus resource reservation numbers “yyyy” and “zzz”.

  Next, each signal VIM 40 transmits a surplus resource reservation status response to the orchestrator 20 with a signal (3). The surplus resource reservation status response includes the extracted surplus resource information list.

  Next, in procedure U, the orchestrator 20 combines the surplus resource information lists. Specifically, the orchestrator 20 that has received the signal (3) combines all the surplus resource information lists included in each signal (3), and is a combined surplus resource information list that is a table shown in FIG. 43 (c). Is generated.

  Next, in signal (4), the orchestrator 20 transmits a necessary resource inquiry to “VNFM1” in order to make an inquiry about the necessary resource. The necessary resource inquiry includes “s1” as a service ID, a table shown in FIG. 43C as a combined surplus resource information list, “VNF10” as a VNF type, and “VFN10 — 002” as VNF identification information. And “100” which is a performance condition.

  Next, in procedure V, “VNFM1” selects available surplus resource information from the surplus resource information list. Specifically, the “VNFM1” that received the signal (4) is the surplus resource information list (table diagram shown in FIG. 43C) included in the signal (4), the VNF type, and the performance condition (see FIG. 9). And a surplus resource that satisfies the performance condition is selected. Here, for “VNFM1”, surplus resources with surplus resource reservation numbers “yyyy” and “zzz” are selected, and the table shown in FIG. 44 is obtained as a combination of resource information necessary for VNF 70 deployment for each surplus resource. . FIG. 44 is a table showing a necessary resource information list for each available surplus resource reservation information.

  Next, “VNFM1” transmits a necessary resource response to the orchestrator 20 by a signal (5). The required resource response includes a required resource information list for each surplus resource reservation information, which is the table shown in FIG.

  Next, in the procedure W, the orchestrator 20 selects a surplus resource whose reservation is to be canceled. Specifically, the orchestrator 20 that has received the signal (5) uses which surplus resource from the necessary resource information list (table diagram shown in FIG. 44) for each surplus resource reservation information included in the signal (5). Decide whether to generate VNF70. Although this selection criterion depends on the policy of the orchestrator 20, it is assumed here that the reserved surplus resource amount is smaller. For this reason, the orchestrator 20 selects a surplus resource reservation number “zzz” having a smaller surplus resource amount.

  Next, with the signal (6), the orchestrator 20 transmits a VNFM reserved surplus resource deletion request to “VNFM2” that is the VNFM 30 corresponding to the surplus resource reservation number “zzz”. The VNFM reservation surplus resource deletion request includes “zzz” which is a surplus resource reservation number.

  Next, in procedure X, “VNFM2” deletes the VNFM reserved surplus resource. Specifically, “VNFM2” deletes the reserved surplus resource information corresponding to the surplus resource reservation number “zzz” received by the signal (6) from the VNFM surplus resource reservation information DB. That is, “VNFM2” deletes the record corresponding to the surplus resource reservation number “zzz” from the VNFM surplus resource information DB which is the table diagram shown in FIG.

  Next, “VNFM2” transmits a VIM reserved surplus resource deletion request to “VIM2” corresponding to the surplus resource reservation number “zzz” by a signal (7). The VIM reservation surplus resource deletion request includes “zzz” which is a surplus resource reservation number.

  Next, in procedure Y, “VIM2” deletes the VIM reserved surplus resource. Specifically, “VIM2” deletes the reserved surplus resource information corresponding to the surplus resource reservation number “zzz” received by the signal (7) from the VIM surplus resource reservation information DB. That is, “VIM2” deletes the record corresponding to the surplus resource reservation number “zzz” from the VIM surplus resource reservation information DB which is the table diagram shown in FIG.

  Next, in signal (8), “VIM2” sends a VIM reserved surplus resource deletion response to “VNFM2” in order to notify the completion of deletion of the VIM reserved surplus resource information corresponding to the surplus resource reservation number “zzz”. Send. The VIM reserved surplus resource deletion response includes “zzz” which is a surplus resource reservation number.

  Next, in response to the signal (9), the “VNFM2” receiving the signal (8) transmits a VNFM reserved surplus resource deletion response to the orchestrator 20 to notify the completion of deletion of the VNFM reserved surplus resource information. The VNFM reservation surplus resource deletion response includes a surplus resource reservation number “zzz”. Next, the orchestrator 20 that has received the signal (9) extracts the necessary resource information corresponding to the surplus resource reservation number “zzz” from the necessary resource information list (table diagram shown in FIG. 44) for each surplus resource reservation information. To do. FIG. 47 is a table showing the extracted necessary resource information.

  Next, the orchestrator 20 transmits necessary resource information to “VIM2” using the signal (10). The necessary resource information includes the table shown in FIG. The subsequent procedure is the same as the procedures E to H in the sequence diagram at the time of Instantiation shown in FIG. Reservation of surplus resources by procedures I to M is not performed due to lack of resources.

  The above is the description of the detailed processing in the mobile communication system 1 using the sequence diagram and the table diagram. The orchestrator 20, VNFM30, VIM40, OSS / BSS50, NFVI60, VNF70, and EMS80 included in the mobile communication system 1 are means for executing their own procedures and processes described in the above sequence diagram, and It has means for transmitting / receiving signals, means for holding each table diagram or database, and means for updating each table diagram (these units are not shown).

  Next, the operation and effect of the management system 10 configured as in the present embodiment will be described.

  According to the management system 10 of the present embodiment, when the VNFM 30 receives a notification that the virtual resources are insufficient from the VNF 70, the VNFM 30 identifies the virtual server of the surplus resource reserved in advance, and identifies the identified virtual server. An instruction to deploy is transmitted to the VIM 40, and the virtual server is deployed by the VIM 40. That is, when the VNFM 30 receives a notification from the VNF 70 that the virtual resources are insufficient, the VNFM 30 can directly transmit an instruction to deploy a virtual server to the VIM 40 without going through the orchestrator 20. Thereby, the processing load of the orchestrator 20 can be suppressed, and the VNF 70 can be scaled out more quickly. In addition, since a virtual server for surplus resources reserved in advance is deployed, it is possible to omit the process of determining whether or not a virtual resource can be secured before securing the virtual server. Can be scaled out. That is, the VNF 70 can be scaled out more quickly in the NFV environment.

  Further, according to the management system 10 of the present embodiment, when the VNFM 30 receives a notification that the virtual resources are insufficient from the VNF 70, the orchestrator 20 reserves and reserves in advance without using the orchestrator 20. The specific VIM 40 that made the request can be specified, and an instruction to deploy the virtual server can be transmitted to the specific VIM 40. Thereby, the processing load of the orchestrator 20 can be suppressed, and the VNF 70 can be scaled out more quickly. That is, the VNF 70 can be scaled out more quickly in the NFV environment.

  Further, according to the management system 10 of the present embodiment, when a virtual server is deployed, the VNFM 30 updates surplus resource information based on virtualized resource information related to the virtual server. That is, the VNFM 30 can manage surplus resource information in accordance with the current situation. As a result, the VNFM 30 can identify and deploy the virtual server of the reserved surplus resource based on the surplus resource information in accordance with the current situation, and thus scales out the VNF 70 more quickly and reliably. be able to.

  Further, according to the management system 10 of the present embodiment, for example, when virtual resources other than reserved surplus resources are depleted, other services such as the orchestrator 20 make a reservation to the VNFM 30. The surplus resources for which the reservation has been canceled can be effectively utilized.

  As described above, according to the management system 10 of the present embodiment, by making a resource reservation with a sufficient margin in advance for the VNF 70, an orchestrator can be used when more resources than normal operation are required. Thus, the VNF 70 can be scaled out quickly without applying an additional processing load to the 20.

  DESCRIPTION OF SYMBOLS 1 ... Mobile communication system, 10 ... Management system, 20 ... Orchestrator, 30 ... VNFM, 31 ... VNFM surplus resource information DB, 32 ... Deployment instruction transmission part, 33 ... VNFM surplus resource information update part, 34 ... Reservation cancellation part 35 ... Reservation cancellation response transmission unit, 40 ... VIM, 41 ... Virtual server deployment unit, 42 ... Deployment completion response transmission unit, 43 ... VIM surplus resource information DB, 50 ... OSS / BSS, 60 ... NFVI, 70 ... VNF, 80 ... EMS80.

Claims (5)

A virtual communication function management node that is included in a communication system including a virtual resource including a physical server on which a virtual server that executes communication processing is generated, and that manages a function that executes the communication processing of the virtual server A virtual resource management node that manages each of the virtual resources, and a general management node that manages the entire virtual resources,
The virtual communication function management node is
A surplus resource information database that stores surplus resource information related to surplus resources that are surplus virtual resources reserved in advance in the virtual resource management node;
When a notification indicating that there is a shortage of virtualized resources is received from the function for executing the communication process, the reserved surplus resource virtual server is identified based on the surplus resource information stored in the surplus resource information database. A deployment instruction transmission means for transmitting an instruction to deploy the identified virtual server to the virtual resource management node without going through the overall management node ;
With
The virtual resource management node is:
When receiving an instruction to deploy a virtual server from the virtual communication function management node without going through the overall management node, virtual server deployment means for deploying the virtual server,
A management system comprising: The overall management node is
Requesting one of the virtual resource management nodes to reserve and secure a surplus resource from one virtual resource management node;
The virtual communication function management node is
Storing information on the one virtual resource management node requested to reserve and secure surplus resources by the overall management node in the surplus resource information database;
Upon receiving a notification that virtual resources are insufficient from the function that executes the communication process, an instruction to specify the one virtual resource management node from the surplus resource information database and to deploy a virtual server To the one virtual resource management node,
The management system according to claim 1. The virtual resource management node is:
When a virtual server is deployed by the virtual server deployment unit, a deployment completion response is a deployment completion response that transmits a deployment completion response including virtualization resource information related to the deployed virtual server to the virtual communication function management node Transmission means,
Further comprising
The virtual communication function management node is
When a deployment completion response is received from the virtual resource management node, the surplus resource information stored in the surplus resource information database is updated based on the virtualization resource information regarding the deployed virtual server included in the deployment completion response. Surplus resource information update means,
The management system according to claim 1, further comprising: The virtual communication function management node is
Upon receiving an instruction to cancel the reservation of surplus resources from the general management node, the surplus resource information to be canceled is specified from the surplus resource information stored in the surplus resource information database, and the specified surplus resource information Reservation cancellation means to delete
Reservation cancellation response transmission means for transmitting a reservation cancellation response to the general management node when the reservation of surplus resources is canceled by the reservation cancellation means;
The management system according to claim 1, further comprising: A virtual communication function management node that is included in a communication system including a virtual resource including a physical server on which a virtual server that executes communication processing is generated, and that manages a function that executes the communication processing of the virtual server And a management method executed by a management system comprising a virtual resource management node that manages each of the virtual resources, and an overall management node that manages the entire virtual resources,
The virtual communication function management node includes a surplus resource information database that stores surplus resource information regarding surplus resources that are surplus virtualization resources reserved in advance in the virtualization resource management node;
When the virtual communication function management node receives notification from the function that executes the communication process that the virtual resources are insufficient, the virtual communication function management node reserves based on the surplus resource information stored in the surplus resource information database. A deployment instruction transmission step of identifying a virtual server of a surplus resource and transmitting an instruction to deploy the identified virtual server to the virtual resource management node without going through the overall management node ;
When the virtual resource management node receives an instruction to deploy a virtual server from the virtual communication function management node without going through the overall management node, a virtual server deployment step of deploying the virtual server;
Management method.

Images