Management device, management method, and program

Abstract

A management device according to the present disclosure is provided with: a virtualized infrastructure manager (VIM) (3) that controls a network function virtualization infrastructure (NFVI) that provides a virtual resource for a virtual network function (VNF) (4) executed as a network function implemented in software; an NFV orchestrator (NFVO) (1) that realizes a network service on the NFVI; a VNF manager (VNFM) (2) that manages the VNF (4); a detection unit (11) that detects a data failure in the VNFM; and a construction unit (12) that, when a data failure is detected, collects information from the NFVO (1), the VIM (3), and the VNF (4) and constructs new operation data for the VNFM.

Description

[Technical field]

[0001] The present disclosure relates to a management device, a management method, and a computer-readable medium storing a program for network functions virtualization (NVF). [Background technology]

[0002] NFV and the like are known, which realize a network in software using virtualization technology. In Non-Patent Document 1, the European Telecommunications Standards Institute (ETSI) defines the NFV reference architectural framework.

[0003] In this architecture, NFV MANO (Management and Orchestration) comprises NFVO (NFV Orchestrator), VNFM (VNF Manager), and VIM (Virtualized Infrastructure Manager). VNFM operates and manages VNF (Virtual Network Function), which realizes network functions with VM (Virtual Machine).

[0004] Patent Document 1 discloses a virtualization management and orchestration device including a database (DB) for holding data for an NFVO, a DB for holding data for a VNFM, a DB for holding data for a VIM, and a synchronization unit for synchronizing data between at least two of the DBs. In this device, when the NFVO detects that the state of a VNF is unknown (for example, data included in a VNFR (Virtual Network Function Record) held in the NFVO DB is undefined), a maintenance person uses data held in the VNFM or VIM DB to update the corresponding data in the NFVO DB, thereby recovering data consistency. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] International Publication No. 2016 / 052492 [Non-patent literature]

[0006] [Non-Patent Document 1] ETSI GS NFV 002 V1.1.1 (2013-10) Network Functions Virtualization (NFV); Figure 4. NFV Reference Architectural Framework Summary of the Invention [Problem to be solved by the invention]

[0007] When data inconsistency occurs in the VNFM, it is possible to restore the data using backup data. However, if the backup data is old due to the operation method, there will be a difference between the latest VNF ​​state and the old data, which may cause the VNF to become uncontrollable.

[0008] There is also a method to reconstruct the VNF, but this has the problem of significant impacts on services when the VNF is stopped and restarted. Since reconstructing the VNF creates new management information for the VNF, the information of the VNF that was previously used is discarded, which may cause operational problems.

[0009] An object of the present disclosure is to provide a management device, a management method, and a computer-readable medium storing a program that enables a new VNFM to be constructed using the most up-to-date data possible without using backup data. [Means for solving the problem]

[0010] A management device according to one embodiment includes a VIM that controls an NFVI that provides virtual resources of a VNF that is executed as a network function implemented in software, an NFVO that realizes a network service on the NFVI, a VNFM that manages the VNF, a detection unit that detects a data failure in the VNFM, and a construction unit that, when the data failure is detected, collects information from the NFVO, the VIM, and the VNF, and constructs operational data for a new VNFM.

[0011] A management method according to one embodiment detects a data failure in a VNFM that manages a VNF executed as a network function implemented in software, and when the data failure is detected, collects information from a VIM that controls an NFVI that provides virtual resources for the VNF, and an NFVO and the VNF that realize a network service on the NFVI, and constructs new operational data for the VNFM.

[0012] A computer-readable medium according to one embodiment has stored therein a program that causes a computer to execute a process of detecting a data failure in a VNFM that manages a VNF executed as a network function implemented in software, and, if the data failure is detected, collecting information from a VIM that controls an NFVI that provides virtual resources for the VNF, and from an NFVO and the VNF that realizes a network service on the NFVI, and constructing operational data for a new VNFM. Effect of the Invention

[0013] According to the above-described aspects, it is possible to provide a management device, a management method, and a computer-readable medium storing a program, which enables a new VNFM to be constructed using the most up-to-date data possible without using backup data. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram illustrating the NFV reference architecture defined by ETSI. [Diagram 2] FIG. 2 is a block diagram showing a configuration of a management device according to the embodiment. [Diagram 3] FIG. 1 is a flow diagram showing a management method according to an embodiment. [Figure 4] FIG. 10 is a diagram illustrating a sequence of a management method according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. Note that the following description and drawings are omitted and simplified as appropriate for clarity of explanation. In addition, in each of the following drawings, the same elements are given the same reference numerals, and duplicated explanations are omitted as necessary. In addition, the specific numerical values ​​shown below are merely examples for facilitating understanding of the present disclosure, and are not limited thereto.

[0016] The embodiment relates to a management device for NFV (Network Functions Virtualization) that realizes network functions by software using a VM (Virtual Machine) implemented on a virtualization layer on a server. First, the NFV reference architecture defined by ETSI will be described with reference to Fig. 1. Fig. 1 is a diagram for explaining the NFV reference architecture defined by ETSI.

[0017] Referring to Fig. 1, a VNF (Virtual Network Function) 4 is implemented in software and executed as a network function. In addition, an EMS (Element Management System) 5 is provided as a management function for each VNF 4. The VNF 4 holds unique information such as performance setting information and fault information.

[0018] NFVI6 is the execution platform for VNF4. NFVI6 realizes hardware resources of physical machines (servers), such as computing, storage, and network functions, as virtual resources such as virtualized computing, virtualized storage, and virtualized networks, which are virtualized by a virtualization layer such as a hypervisor.

[0019] NFV MANO (Management and Orchestration) 10 provides management of hardware and software resources, as well as management and orchestration functions for VNFs. NFV MANO 10 includes NFVO (NFV-Orchestrator) 1, VNFM (VNF manager) 2, and VIM (Virtualized Infrastructure Manager) 3.

[0020] NFVO1 manages and orchestrates VNF4 and NFVI6. Specifically, NFVO1 realizes network services (resource allocation to VNF4, management of VNF (e.g. auto-healing (automatic reconfiguration upon failure), auto-scaling, VNF lifecycle management, etc.) on NFVI6. NFVO1 holds and manages VNFR (VNF Record) information that indicates the state and operational status of VNF4. NFVO1 also manages VNFD (VNF Descriptor), which defines the configuration of VNF4.

[0021] The VNFM2 performs lifecycle management (e.g., creation, update, query, healing, scaling, termination, etc.) and event notification of the VNF4. The VNFM2 uses the VNFD in instantiating the VNF4 and in lifecycle management of the VNF instances.

[0022] VIM3 allocates the virtual resources required to operate VNF4. VIM3 controls NFVI6 via the virtualization layer, and performs, for example, resource management of computing, storage, and network, fault monitoring of NFVI, which is the execution platform of NFV, and monitoring of resource information.

[0023] Outside the NFV framework, OSS (Operations Support Systems) / BSS (Business Support systems)7 are established. OSS is a general term for the systems (equipment, software, mechanisms, etc.) required by, for example, a telecommunications carrier to build and operate a service. BSS is a general term for the information systems (equipment, software, mechanisms, etc.) used by, for example, a telecommunications carrier to charge usage fees, bill, and handle customer support.

[0024] In this way, the embodiment complies with the NFV reference architecture defined by ETSI. As described above, the VNFM2 is defined as a mechanism for operating and managing VNFs as one component of the NFV MANO10.

[0025] VNFM2 has connections with three major counterpart systems. In other words, VNFM2 cooperates with NFVO1, VIM3, and VNF4. VNFM2 transmits and receives information with these three counterpart systems and manages and operates VNFs.

[0026] The inventors have devised the following configuration to reconstruct VNFM2 using the latest information possible, assuming a case where data inconsistency occurs in VNFM2 and system recovery is not possible. The information to be managed by VNFM2 is configured based on the information held by the above three opposing systems. By utilizing this characteristic, it is possible to reconstruct VNFM by collecting information to be managed by VNFM2 from the three opposing systems.

[0027] Fig. 2 is a block diagram showing a configuration of a management device according to an embodiment. In Fig. 2, the same components as those in Fig. 1 are denoted by the same reference numerals. As shown in Fig. 2, the management device includes an NFVO1, a VNFM2, a VIM3, and a VNF4. In addition, the VNFM2 includes a detection unit 11 and a construction unit 12.

[0028] The detection unit 11 detects a data failure in the VNFM 2. When the detection unit 11 detects a data failure, the construction unit 12 collects information from the NFVO 1, the VIM 3, and the VNF 4, and constructs a new VNFM. In this manner, in the embodiment, by acquiring information from the three opposing systems, it becomes possible to construct a new VNFM and restore the system.

[0029] VNFM2 holds the following information in order to manage VNF4. -VNF configuration information The configuration information of the VNF4 includes, for example, information such as the VNF name, the VNF function, whether or not it is FPGA compatible, the VNF image file, and FPGA compatibility. -Connection information to VIM to obtain virtual resources The information for the VIM 3 includes, for example, an identifier of the VIM 3 and information about virtual resources allocated by the VIM 3. The information about the allocated virtual resources may include the type and amount of the allocated resources. - VNF lifecycle management policy information This policy information is used to describe the authority of a device to perform lifecycle management operations on the VNF4 and deploy network services.

[0030] If the operational data of VNFM2 is destroyed, in order to restore the above information, VNFM2 needs to obtain information from the opposing system using the following information as a key. Connection information to the opposing system (NFVO1, VIM3, VNF4) List of VNF4 in operation

[0031] Regarding the method for acquiring information from the opposing system when VNFM2 fails, 3 , 4 The following description will be given with reference to FIG. 3 FIG. 1 is a flow diagram showing a management method according to an embodiment; 4 FIG. 1 is a diagram illustrating the sequence. In the following description, the failed VNFM is the VNFM of the old environment, and the VNFM newly constructed for recovery is the VNFM of the new environment. 4 VNFM2 in is the VNFM of the new environment. 4 In Fig. 3 The same reference numerals are given to the steps corresponding to those in the previous step.

[0032] In step S10, the detection unit 11 detects a failure of the VNFM of the old environment. When a failure of the VNFM of the old environment is detected, the operator constructs a new VNFM to be restored (step S11). When constructing the VNFM2 of the new environment, the construction unit 12 sets connection information (such as EndPoint) with the opposing system that was connected in the old environment. At this time, the VNFM2 of the new environment does not hold operation information related to the VNF4.

[0033] Next, the construction unit 12 acquires a list of VNFRs from the NFVO 1 (step S12). The VNFRs include operation information related to the VNFs 4, such as information for uniquely identifying the VNFs 4 (for example, a VNF ID), VNFD information describing the configuration of the VNFs 4, operation and running status of the VNFs 4, and connection information for managing the VNFs 4.

[0034] After acquiring the list of VNFRs from the NFVO 1, the construction unit 12 extracts operation information of the VNFs from the acquired VNFRs, and then constructs operation data of the VNFM of the new environment using the operation information (step S13).

[0035] The NFVO1 holds information on all VNFs 4 operating on the NFVI6 as VNFRs. Therefore, the construction unit 12 can recognize VNFs that are in an operational state by referring to all of these VNFRs. Here, "VNFs in an operational state" refers to VNFs that have not been deleted from the operational status of the VNFR.

[0036] For example, the construction unit 12 identifies a VNF 4 that is in an operational state. The construction unit 12 may use operation information of the identified VNF 4 in an operational state to construct operation data for managing only the VNF 4 in an operational state in the VNFM 2 of the new environment.

[0037] Specifically, the construction unit 12 acquires configuration information of the VNF (information such as the VDUs (Virtual Deployment Units) and CPs (Connection Points) that constitute the VNF) and connection information for accessing these resources from the VNFR of the identified VNF4 in an operational state, and constructs operational data for the VNF4.

[0038] The VDU information includes a VDU identifier, connection destination information of the VIM 3 indicating through which VIM 3 the virtual resource was created, etc. The construction unit 12 acquires virtual resource information managed by the NFVI 6 from the VIM 3 to which the VNF 4 is connected, using the acquired VDU information of the VNF 4 in operation (step S14).

[0039] The VDU information of VNF4 is defined in the VNFD of the VNF package of NFVO1. Using this definition information and the virtual resource information confirmed in step S14, configuration information (operation data) of the virtual resource of VNF4 in the VNFM2 of the new environment is constructed.

[0040] Then, the VNFM2 restores the connection to the VNF4 (step S15). The construction unit 12 acquires management connection information for each VNF and VDU from each VNFR. The management connection information for the VNF and VDU includes information on the connection destination IP address (VDUmgmt IP address) for the VNFM2 to manage various virtual resources.

[0041] The VNFM2 uses this IP address to access the VNF4. The construction unit 12 uses this management connection information to access each VNF4 and acquires current unique information of the VNF4, such as stateless setting information and fault information required for operation. In this way, according to the embodiment, it is possible to construct operation data of the VNFM2 in the new environment using information acquired from each opposing system.

[0042] As described above, according to the embodiment, by collecting information to be managed by the VNFM2 from the opposing system of the VNFM2, it is possible to always recover the operation data of the VNFM2 with the latest information. In addition, since new operation data of the VNFM2 can be constructed without constructing the VNF4 again, it is possible to reduce the service downtime to less than the VNF reconstruction time.

[0043] In addition, each functional block performing various processes shown in the drawings can be configured in hardware terms with a processor, memory, and other circuits. Also, the above-mentioned processes can be realized by having a processor execute a program. Therefore, these functional blocks can be realized in various forms by only hardware, only software, or a combination of both, and are not limited to any one of them.

[0044] The above-mentioned program can be stored and provided to a computer using various types of non-transitory computer readable media. The non-transitory computer readable medium includes various types of tangible storage media. Examples of the non-transitory computer readable medium include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). The program may also be provided to a computer by various types of transitory computer readable media. Examples of the transitory computer readable medium include electric signals, optical signals, and electromagnetic waves. The transitory computer readable medium can provide the program to a computer via a wired communication path such as an electric wire and an optical fiber, or via a wireless communication path.

[0045] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by a person skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure.

[0046] Furthermore, some or all of the above-described embodiments can be described as, but are not limited to, the following supplementary notes.

[0047] (Appendix 1) VIM (Virtualized Infrastructure Manager) controls NFVI (Network Function Virtualization Infrastructure), which provides virtual resources for VNF (Virtual Network Function) that is executed as a network function implemented in software. NFVO (NFV-Orchestrator) that realizes network services on the NFVI; A VNFM (VNF Manager) that manages the VNF; A detection unit for detecting a data failure in the VNFM; A construction unit that collects information from the NFVO, the VIM, and the VNF when the data failure is detected, and constructs new VNFM operation data; Equipped with Management device. (Appendix 2) The NFVO holds at least a Virtualized Network Function Record (VNFR), The construction unit includes: Obtaining the VNFR from the NFVO; Extracting operation information of the VNF from the acquired VNFR; Using the operational information, construct operational data for the new VNFM; 2. The management device of claim 1. (Appendix 3) The construction unit identifies the VNF that is in an operational state, and constructs operational data of the new VNFM for managing the identified VNF in the operational state. 3. The management device according to claim 2. (Appendix 4) The construction unit includes: Obtain information on a VDU (Virtualization Deployment Unit) that is a component of the VNF in an operational state from the VNFR; Using the acquired VDU information, acquire virtual resource information managed by the NFVI from the VIM to which the VNF in operation is connected; Using the VDU information and the virtual resource information, construct operation data of the new VNFM; 4. The management device according to claim 3. (Appendix 5) The construction unit includes: Obtain management connection information from the obtained VNFR to the VNF; Access the VNF using the management connection information, and acquire unique information of the VNF to construct operation data of the new VNFM. 5. The management device according to any one of claims 2 to 4. (Appendix 6) Detects data failures in the VNFM (VNF Manager), which manages VNFs (Virtual Network Functions) that are executed as network functions implemented in software, When the data failure is detected, a VIM (Virtualized Infrastructure Manager) that controls an NFVI (Network Function Virtualization Infrastructure) that provides virtual resources for the VNF, and an NFVO (NFV-Orchestrator) that realizes network services on the NFVI and collect information from the VNF to construct new VNFM operation data. Management method. (Appendix 7) The NFVO holds at least a Virtualized Network Function Record (VNFR), Obtaining the VNFR from the NFVO; Extracting operation information of the VNF from the acquired VNFR; Using the operational information, construct operational data for the new VNFM; The management method described in Appendix 6. (Appendix 8) Identifying the VNFs that are operational and constructing operational data of the new VNFM for managing the identified VNFs that are operational. The management method described in Appendix 7. (Appendix 9) Obtain information on a VDU (Virtualization Deployment Unit) that is a component of the VNF in an operational state from the VNFR; Using the acquired VDU information, acquire virtual resource information managed by the NFVI from the VIM to which the VNF in operation is connected; Using the VDU information and the virtual resource information, construct operation data of the new VNFM; The management method described in Appendix 8. (Appendix 10) Obtain management connection information from the obtained VNFR to the VNF; Access the VNF using the management connection information, and acquire unique information of the VNF to construct operation data of the new VNFM. The management method according to any one of Appendices 7 to 9. (Appendix 11) Detects data failures in the VNFM (VNF Manager), which manages VNFs (Virtual Network Functions) that are executed as network functions implemented in software, When the data failure is detected, a VIM (Virtualized Infrastructure Manager) that controls an NFVI (Network Function Virtualization Infrastructure) that provides virtual resources for the VNF, and an NFVO (NFV-Orchestrator) that realizes network services on the NFVI and collect information from the VNF to construct new VNFM operation data. A program that causes a computer to execute a process is stored. Computer-readable medium. (Appendix 12) The NFVO holds at least a Virtualized Network Function Record (VNFR), Obtaining the VNFR from the NFVO; Extracting operation information of the VNF from the acquired VNFR; Using the operational information, construct operational data for the new VNFM; A program that causes a computer to execute a process is stored. 12. The computer-readable medium of claim 11. (Appendix 13) Identifying the VNFs that are operational and constructing operational data of the new VNFM for managing the identified VNFs that are operational. A program that causes a computer to execute a process is stored. 13. The computer-readable medium of claim 12. (Appendix 14) Obtain information on a VDU (Virtualization Deployment Unit) that is a component of the VNF in an operational state from the VNFR; Using the acquired VDU information, acquire virtual resource information managed by the NFVI from the VIM to which the VNF in operation is connected; Using the VDU information and the virtual resource information, construct operation data of the new VNFM; A program that causes a computer to execute a process is stored. 14. The computer-readable medium of claim 13. (Appendix 15) Obtain management connection information from the obtained VNFR to the VNF; Access the VNF using the management connection information, and acquire unique information of the VNF to construct operation data of the new VNFM. A program that causes a computer to execute a process is stored. 15. A computer-readable medium according to any one of appendices 12 to 14. [Explanation of symbols]

[0048] 1. NFVO 2. VNFM 3. VIM 4 VNF 5. EMS 6 NFVI 7 OSS / BSS 10 NFV MANO 11 Detection section 12 Construction Department

Claims

1. A VIM (Virtualized Infrastructure Manager) that controls a Network Function Virtualization Infrastructure (NFVI) that provides virtual resources for a Virtual Network Function (VNF) that is executed as a network function implemented in software; An NFVO (NFV-Orchestrator) that realizes network services on the NFVI; A VNFM (VNF Manager) that manages the VNF; A detection unit for detecting a data failure in the VNFM; a construction unit that collects information from the NFVO, the VIM, and the VNF when the data failure is detected, and constructs new operation data of the VNFM; Equipped with The construction unit identifies the VNF that is in an operational state, and constructs operational data of the new VNFM for managing the identified VNF in the operational state. Management device.

2. The NFVO holds at least a Virtualized Network Function Record (VNFR), The construction unit includes: Obtaining the VNFR from the NFVO; Extracting operation information of the VNF from the acquired VNFR; constructing operational data for the new VNFM using the operational information; The management device according to claim 1 .

3. The construction unit includes: Acquire information on a VDU (Virtualization Deployment Unit) that is a component of the VNF in an operational state from the VNFR; Using the acquired VDU information, acquire virtual resource information managed by the NFVI from the VIM to which the VNF in operation is connected; Using the VDU information and the virtual resource information, construct operation data of the new VNFM. The management device according to claim 2 .

4. The construction unit includes: Obtaining management connection information from the obtained VNFR to the VNF; accessing the VNF using the management connection information and acquiring unique information of the VNF, thereby constructing operation data of the new VNFM; The management device according to claim 2 or 3.

5. Detecting a data failure in a VNFM (VNF Manager) that manages a VNF (Virtual Network Function) that is executed as a network function implemented in software, When the data failure is detected, a VIM (Virtualized Infrastructure Manager) identifies the VNF in an operational state, controls a NFVI (Network Function Virtualization Infrastructure) that provides virtual resources for the VNF, and collects information from a NFVO (NFV-Orchestrator) that realizes network services on the NFVI and the VNF, and constructs operation data for a new VNFM to manage the VNF in the identified operational state. Management method.

6. Detecting a data failure in a VNFM (VNF Manager) that manages a VNF (Virtual Network Function) that is executed as a network function implemented in software, When the data failure is detected, a VIM (Virtualized Infrastructure Manager) identifies the VNF in an operational state, controls a NFVI (Network Function Virtualization Infrastructure) that provides virtual resources for the VNF, and collects information from a NFVO (NFV-Orchestrator) that realizes network services on the NFVI and the VNF, and constructs operation data for a new VNFM to manage the VNF in the identified operational state. A program that causes a computer to carry out processing.

7. The NFVO holds at least a Virtualized Network Function Record (VNFR), Obtaining the VNFR from the NFVO; Extracting operation information of the VNF from the acquired VNFR; constructing operational data for the new VNFM using the operational information; Have a computer carry out the process, The program according to claim 6.

8. Acquire information on a VDU (Virtualization Deployment Unit) that is a component of the VNF in an operational state from the VNFR; Using the acquired VDU information, acquire virtual resource information managed by the NFVI from the VIM to which the VNF in operation is connected; Using the VDU information and the virtual resource information, construct operation data of the new VNFM. Have a computer carry out the process, The program according to claim 7.

9. Obtaining management connection information from the obtained VNFR to the VNF; accessing the VNF using the management connection information and acquiring unique information of the VNF, thereby constructing operation data of the new VNFM; The program according to claim 7 or 8.

Images