NETWORK FUNCTIONS VIRTUALIZATION MANAGEMENT AND ORCHESTRATION METHOD, NETWORK FUNCTIONS VIRTUALIZATION MANAGEMENT AND ORCHESTRATION SYSTEM, AND PROGRAM

Abstract

A network functions virtualization management and orchestration system with a VNF descriptor (VNFD) including a information element that allows an instance created based on the VNFD to be distinguished by name. The information element includes an information element of a VM name that describes a naming rule for a virtual machine (VM).

Claims

1. A network functions virtualization management and orchestration method comprising: receiving information of a template from a storage unit; and creating an instance based on the information of the template, wherein an information element that allows an instance created based on the information of the template to be distinguished by name is provided in the template that is stored in the storage unit.

2. The network functions virtualization management and orchestration method according to claim 1, wherein the information element that allows the instance to be distinguished by name includes an information element that gives a naming rule for a name of the instance.

3. A network functions virtualization management and orchestration method, comprising: providing, in a VNF (Virtualized Network Function) descriptor (VNFD), an information element that gives a naming rule for a name of an instance, to allow an instance created based on information of the VNFD to be distinguished by name.

4. The network functions virtualization management and orchestration method according to claim 3, comprising: providing an information element of a virtual machine (VM) name that describes a naming rule for a VM on a same layer as information elements of an ID (Identifier) and a VDU (Virtualized Deployment Unit) of the VNFD, to allow a plurality of instances created based on the VNFD to be distinguished by name.

5. A network functions virtualization management and orchestration system, comprising: an input unit that receives information of a template from a storage unit; and a creation unit that creates an instance based on the information of the template, wherein the template includes an information element that allows an instance created based on the information of the template to be distinguished by name.

6. The network functions virtualization management and orchestration system according to claim 5, wherein the information element that allows the instance to be distinguished by name includes an information element that gives a naming rule for the name of the instance.

7. A network functions virtualization management and orchestration system comprising: a first unit that receives a VNF (Virtualized Network Function) descriptor (VNFD) including an information element that gives a naming rule for a name of an instance; and a second unit that creates an instance based on information of the VNFD.

8. The network functions virtualization management and orchestration system according to claim 7, wherein an information element of a virtual machine (VM) name that describes a naming rule for a VM is provided in the VNFD on a same layer as information elements of an ID (Identifier) and a VDU (Virtualized Deployment Unit) of the VNFD, to allow a plurality of instances created based on the VNFD to be distinguished by name.

9. A non-transitory computer-readable recording medium storing therein a program causing a computer to execute processing comprising: receiving, from a storage unit, a template including an information element that allows an instance created based on information of the received template to be distinguished by name; and creating an instance based on the information of the received template.

10. The non-transitory computer-readable recording medium storing therein a program according to claim 9, wherein the information element that allows the instance to be distinguished by name includes an information element that gives a naming rule for the name of the instance.

11. A non-transitory computer-readable recording medium storing therein a program causing a computer to execute processing comprising: receiving a VNF (Virtualized Network Function) descriptor (VNFD) with an information element that gives a naming rule for a name of an instance; and creating an instance based on information of the VNFD.

12. The non-transitory computer-readable recording medium storing therein a program according to claim 11, wherein an information element of a virtual machine (VM) name that describes a naming rule for (VM) is provided in the VNFD on a same layer as information elements of an ID and a VDU (Virtualized Deployment Unit), to allow the instance created based on the VNFD to be distinguished by name.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0076] FIG. 1 is a diagram illustrating NFV-MANO of an NFV architecture (cited from FIG. 5.1 in Non-Patent Literature 1).

[0077] FIG. 2 is a diagram illustrating templates and instance records according to Non-Patent Literature (cited from FIG. 6.2 in Non-Patent Literature 1).

[0078] FIG. 3 is a diagram illustrating a relationship among a VNF, VNFCs, and VDUs.

[0079] FIG. 4 is a diagram schematically illustrating a logical relationship among descriptors (cited from FIG. 6.4 in Non-Patent Literature 1).

[0080] FIG. 5 is a diagram schematically illustrating a structure of a VNF descriptor (vnfd).

[0081] FIG. 6 is a diagram illustrating information elements in a table of the VNF descriptor (vnfd) (cited from 6.3.1.1 in Non-Patent Literature 1).

[0082] FIG. 7A is a diagram illustrating information elements of VDU

[0083] FIG. 7B is a diagram illustrating information elements of VNFC

[0084] FIG. 7C is a diagram illustrating information elements of Connection point (FIGS. 7A-7C: respectively cited from 6.3.1.2.1, 6.3.1.2.1.1, and 6.3.1.2.1.2 in Non-Patent Literature 1).

[0085] FIG. 8A is a diagram illustrating VDU information elements related to storage

[0086] FIG. 8B is a diagram illustrating information elements of each VNF internal Virtual Link.

[0087] FIG. 8C is a diagram illustrating information elements of Connection points (FIGS. 8A-8C: cited from 6.3.1.2.10 in Non-Patent Literature 1).

[0088] FIG. 9A is a diagram illustrating information elements of deployment flavor (Deployment Flavor).

[0089] FIG. 9B is a diagram illustrating information elements of each constituent VDU (FIGS. 9A-9: cited respectively cited from 6.3.1.5 and 6.3.1.5.1 in Non-Patent Literature 1).

[0090] FIG. 10 is a diagram illustrating information elements of a VNF descriptor (vnfd) in an exemplary embodiment.

[0091] FIG. 11 is a diagram schematically illustrating a structure of the VNF descriptor (vnfd) in the exemplary embodiment.

[0092] FIG. 12 is a diagram illustrating an example of scaling-out of VMs in the exemplary embodiment.

[0093] FIG. 13 is a diagram illustrating NFV-MANO configured to process the descriptor in the exemplary embodiment.

PREFERRED MODES

[0094] According to one of some exemplary embodiments, a VNF (Virtualized Network Function) descriptor (VNFD) includes an entry (information element) of a VM name that describes a naming rule for a virtual machine (VM) on the same layer (immediately below a VNFD root) as information elements of an identifier (ID) and a VDU (Virtualized Deployment Unit), for example. An instance (virtual machine (VM) or the like) that is created based on the descriptor may be distinguished by name. This enables distinction among instances (VMs or the like) in terms of management.

[0095] As described above, in the standard specification for NFV, with respect to VNFD, VDU, and VNFC, an ID can be given for VNFD, for VDU, and for VNFC, as illustrated in FIG. 6, FIG. 7A, and FIG. 7B, respectively. However, a name cannot be given for VM (instance), for example, as a result of which, when congestion (processing congestion due to a load that has exceeded capability of VM), a fault, or the like occurs and scaling-out (such as addition of a VM) is performed, for example, distinction cannot be made among of VMs (instances), in terms of management. A similar problem may occur in the case of VNF or VDU as well.

[0096] In order to solve this type of problem, according to the present exemplary embodiment, as illustrated in FIG. 10, for example, an information element (VM name) that gives a naming rule for a VM name is provided as a type of leaf (Leaf), for example, on the same layer as entries such as an identifier (ID (identifier)), a vendor (Vendor), a version (Version), and a VDU located on a layer immediately below a root, for example, in a VDN descriptor (VNFD).

[0097] FIG. 11 is a diagram illustrating a structure of a VNF descriptor in the exemplary embodiment illustrated in FIG. 10 and corresponds to FIG. 5 described above.

[0098] Referring to FIG. 11, the VNF descriptor (vnfd) includes information elements (entries) of one to N (N being an integer equal to 1 or more) virtual machine names (VM names) on the same layer as a vdu, a Virtual Link, Connection Points, and a Deployment Flavor. These information elements (VM names) are connected as end nodes (Leaves) in a structure of the VNF descriptor. NNFV-MANO (see FIG. 2) generates each VM name based on the naming rule of the VM name for the VM in the descriptor, using an instantiation operation.

[0099] FIG. 12 is a diagram illustrating a specific example of the present exemplary embodiment. FIG. 12 illustrates respective names (a physical server name, a VDU name, and a logical node name) of a physical machine PM (Physical Machine), a virtual machine VM (Virtual Machine), and an application (APL) on the virtual machine, corresponding to servers before and after scaling-out (where two servers are added). The following describes a case where NFV-MANO executes auto scale-out, as a result of detection of a fault, congestion, or the like, in a server apparatus having

a physical server name: PM01,
a VDU name: OsakaSGW001 U-Plane001, and
a logical node name: OsakaSGW001 U-Plane001.

[0100] One of the two servers to be added is one having a physical server name: PM02 and a VM name (VDU name) of OsakaSGW001 U-Plane002. The other of the two servers to be added is the one having

a physical server name: PM03 and
a VM name (VDU name) of OsakaSGW001 U-Plane003.

[0101] These VM names are each created as an instance name (VDU name) by instantiation by NFV-MANO according to the description of the information element of the VM name (VM names) that has defined the naming rule for the VM.

[0102] To take an example, the naming rule for the VM set in the information element of the VM name (VM name) of the VNF descriptor is set to “OsakaSGW001 U-Plane” && “++integer-value”. Then, the initial value of the integer-value is set to 0. At a time of instantiation, for example, the “integer-value” following the character string (character string) of the “Osaka SGW001 U-Plane” is auto-incremented (automatically incremented by 1) due to “++integer-value” in the rule, a resulting integer value is converted to a character string of three decimal digits (such as “002”), and the character string of “002” is concatenated to the character string of “OsakaSGW001 U-Plane) using an operator “&&”, thereby generating the VDU name of “OsakaSGW001 U-Plane002” or the like.

[0103] Therefore, the names of “OsakaSGW001 U-Plane002” and “OsakaSGW001 U-Plane003” are respectively assigned to second and third, VMs added by auto scaling (auto-scale V-MANO). That is, according this exemplary embodiment, distinction can be made, in terms of management.

[0104] An operator ++ in the “++integer-value” of the instruction rule is given as the simplest example among examples of naming rule for the auto-increment (in which on syntax of the naming rule is arbitrary). Naturally, the present invention is not limited to such a naming rule. To take an example, in place of the “OsakaSGW001 U-Plane “++ integer-value””, an instruction of inserting a text code of a “building name” in place of a field of “Osaka” as an argument (variable) of the naming rule may be embedded. When orchestration is performed, NFVO may select a building or the like with sufficient resources (resources), for example. In that case, it may be so arranged that an instruction of automatically inserting “building name” is specified as the naming rule, and NFVO gives VM name (VDU name) by referring to repository information of NFVI and VNF that NFVO manages at the time of the orchestration.

[0105] FIG. 13 is a diagram illustrating NFV-MANO (in FIG. 2) configured to execute a process of loading the VNF descriptor (vnfd) in this exemplary embodiment described with reference to FIGS. 10 and 11 and generating an NFV instance. The process may be implemented in NFVO, VFNM, or the like of NFV-MANO as a program. In this case, a processor (CPU (Central Processing Unit)), not shown, which constitutes NFVO, VNFM, or the like of the NFV-MANO loads the program stored in a semiconductor memory, an HDD (Hard Disk Drive), or the like into a main memory, and executes the program, thereby implementing a VNF descriptor loading process from the storage unit and an NFV instance creation process.

[0106] NFV-MANO 100 includes a descriptor input unit 101 configured to receive the VNF descriptor (vnfd) (including an information element of a VM name) in this exemplary embodiment illustrated in FIG. 10 and so on, an instantiation input parameter input unit 102 configured to receive an instantiation input parameter, an instantiation execution unit 103 configured to execute an instantiation operation, and an instance record output unit 104 configured to output an instance record. The instance record and data are stored in an instance record storage unit 112.

[0107] For example, from OSS/BSS or VNFM to NFVO, NS (Network Service) or VNF instantiation operation is executed. The instantiation input parameter is used to customize network service NS or VNF to specific instantiation, for example. As the instantiation input parameter, information for identifying a deployment flavor (Deployment Flavor) to be used, and VNF and PNF to be incorporated by the instantiation operation are referred to. The instantiation execution unit 103 creates records (NSR, VNFR, VLR, VNFFGR and so forth) indicating a newly created instance. Each record created based on information given by each descriptor and additional runtime information related to a component instance, provides a data group necessary for modeling a state of a network service (NS) instance, VNF instance, VNFFG instance, or VL (Virtual Link) instance. Distinction among instances such as a plurality of VMs (VDUs) that have been created can be made by names (such as VDU names).

[0108] In the above-mentioned exemplary embodiment, the description has been given, using, as an example, virtual machines (VMs) instantiated based on information on the descriptor or the like. With respect to VNF, VNFC, and VDU as well, by including an information element for setting a name (naming rule) to be associated with an instance to be created, distinction among instances (VNF, VNFC, and VDU) created based on the descriptor is made possible, in terms of management.

[0109] Each disclosure of the above-listed Non-Patent Literature is incorporated herein by reference. Modification and adjustment of each exemplary embodiment or each example are possible within the scope of the overall disclosure (including the claims) of the present invention and based on the basic technical concept of the present invention. Various combinations and selections of various disclosed elements (including each element in each claim, each element in each example, each element in each drawing, and so on) are possible within the scope of the claims of the present invention. That is, the present invention naturally includes various variations and modifications that could be made by those skilled in the art according to the overall disclosure including the claims and the technical concept.