CN108234158B - VNF establishment method, NFVO and network system - Google Patents

VNF establishment method, NFVO and network system Download PDF

Info

Publication number
CN108234158B
CN108234158B CN201611149076.6A CN201611149076A CN108234158B CN 108234158 B CN108234158 B CN 108234158B CN 201611149076 A CN201611149076 A CN 201611149076A CN 108234158 B CN108234158 B CN 108234158B
Authority
CN
China
Prior art keywords
vim
nfvo
vnfm
vnf instance
vnf
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201611149076.6A
Other languages
Chinese (zh)
Other versions
CN108234158A (en
Inventor
李晨
解冲锋
史凡
束栋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN201611149076.6A priority Critical patent/CN108234158B/en
Publication of CN108234158A publication Critical patent/CN108234158A/en
Application granted granted Critical
Publication of CN108234158B publication Critical patent/CN108234158B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation

Abstract

The invention discloses a VNF establishing method, an NFVO and a network system, and relates to the technical field of communication, wherein the method comprises the following steps: the NFVO requests the VIM to allocate virtual resources, and when judging that an abnormal condition occurs, the NFVO sends a VNF instance creating instruction to the VNFM and allocates the authority of creating the VNF instance; the VNFM requests allocation of virtual resources for creating the VNF instance and creates the VNF instance from the VIM. According to the establishing method, the NFVO and the network system, the VNF instance is established in the indirect mode, the direct mode is used as a backup mode during fault, when the resource call for establishing the VM in the indirect mode fails, the VNF instance is automatically sensed and switched to the direct mode to complete the resource call established by the VM, and subsequent operations such as automatic establishment, monitoring and the like are completed, so that the fault recovery capability of the indirect mode is improved, the change of an NFV system architecture is small, and the actual operation of the existing network is facilitated.

Description

VNF establishment method, NFVO and network system
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a VNF establishment method, an NFVO, and a network system.
Background
NFV (Network Functions Virtualization) refers to implementing various Network device Functions on standardized general IT devices (x86 servers, storage and switching devices) by using Virtualization technology. After the NFV is adopted, on one hand, the functions of the network equipment do not depend on special hardware, the IT equipment based on the x86 standard has low cost, and the equipment investment cost can be expected to be saved for operators; on the other hand, through software and hardware decoupling and function abstraction, resources can be fully and flexibly shared, rapid development and deployment of new services are achieved, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are carried out based on actual service requirements. For example, network services such as NAT, firewall, intrusion detection, dns (domain Name service), and cache can be delivered in the form of software and deployed on a general hardware platform, which can provide great flexibility and flexibility for design, deployment, and management of network services.
The entire NFV architecture can be divided into several parts: the NFVI (NFV Infrastructure) includes physical resources, a virtualization layer and virtual resources thereon, where the physical resources include three hardware resources of computation, storage and network, and are devices that undertake tasks of computation, storage and intercommunication between internal and external interconnects. Virtual network element and network management: including VNF and EM. A VNF (virtualized Network Function) is a Network element after software is implemented, and is deployed on a virtual machine, and the Function of the VNF is consistent with that of an interface and non-virtualization. The EM (Element Management) mainly performs a conventional Element Management function and a new Management function in a virtualization environment. MANOs (NFV Management and organization, NFV Management and Orchestrator) include orchelstrators, VNFM and VIM. The NFV editor (network function virtualization Orchestrator) is responsible for the overall management of network traffic, VNF and resources, and is the control core of the entire NFV architecture. The VNFM (VNFManager, virtualized network function manager) is mainly responsible for related management of resources and life cycles of the VNF, such as functions of instantiating, expanding, and contracting network elements. The main function of VIM (virtualization Infrastructure Management ) is to manage and monitor the resources of the entire Infrastructure layer, including hardware resources and virtual resources. Besides, the system also comprises an OSS/BSS network element which supports the traditional network management function and also supports the interaction with an Orchester in a virtualization environment to complete the maintenance and management functions. In the NFV network, the generation, configuration management, monitoring, termination, etc. of the virtual network element will be substantially fully automated, and the automatic creation of the virtual network element needs to be completed depending on the information interaction between the NFVO, VNFM, and VIM and the invocation of API.
The automatic creation, monitoring and scaling of the virtual machine support two modes: direct mode and indirect mode. The direct mode performs resource allocation for VM establishment by the VNFM connecting directly to the VIM, which requires direct connection establishment with the VIM. The indirect mode is used for resource allocation of VM establishment by connecting the NFVO and the VIM, and the VNFM does not need to have direct connection establishment with the VIM. In the direct mode, resources of the VIM are called by the VNFM, and for the NFVO, the calling of the resources is obtained through the VNFM, and original information of the calling of the resources cannot be obtained. The indirect mode is that the NFVO calls the resource of the VIM, and the NFVO can directly obtain the call information of the resource and globally control the allocation of the resource, and the indirect mode is more suitable for the requirement of deployment for the NFV of the operator network. When the indirect mode is adopted, since the NFVO is deployed at a higher position than the VNFM, a network failure between the NFVO and the VIM or an interface call failure may occur. If the connection between the NFVO and the VIM is abnormal or the called VIM-related API interface fails, the resource allocation for establishing the VM fails, and the VM cannot be created successfully.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a VNF establishing method, an NFVO, and a network system.
According to an aspect of the present invention, there is provided a method for establishing a virtualized network function VNF, including: a network function virtualization orchestrator NFVO requests a virtualized infrastructure equipment management system (VIM) to allocate virtual resources to create a Virtualized Network Function (VNF) instance; when the abnormal condition is judged to occur, the NFVO sends a VNF instance creating instruction to a VNFM (virtual network function manager) so as to distribute a VNF instance creating authority to the VNFM; the VNFM requests the VIM to allocate virtual resources for creating the VNF instances, and creates the VNF instances according to the virtual resources allocated by the VIM.
Optionally, after the NFVO requests the VIM to allocate a virtual resource, the NFVO receives the virtual resource information allocated to the VNF sent by the VIM; and the NFVO sends the virtual resource information to the VNFM, and the VNFM creates a VNF instance according to the virtual resource information.
Optionally, the VNF instance creation instruction carries a resource reservation condition for creating the VNF instance and a network element attribute of the VNF instance; and the VNFM requests the VIM to allocate virtual resources for creating the VNF instance according to the resource reservation condition and the network element attribute.
Optionally, before the NFVO requests the VIM to allocate virtual resources, the NFVO sends an instantiation request for the VNF instance to the VNFM, wherein the instantiation request carries a virtualized network function description template, VNFD, for the VNF instance; the VNFM analyzes the VNFD, determines virtual resources required for deploying the VNF instances, and returns a virtual resource list for deploying the VNF instances to the NFVO.
Optionally, the NFVO determines to establish a virtual resource of the VNF instance based on the virtual resource list, and requests allocation of the virtual resource for creating the VNF instance to the VIM; the VIM allocates virtual resources required by the VNF instances and sends virtual resource information corresponding to the allocated virtual resources to the NFVO; the NFVO sends the virtual resource information to the VNFM to inform the VNFM of the completion of the configuration of the virtual resources; and the VNFM acquires information needing to establish the VNF instance from the NFVO to establish the VNF instance.
Optionally, the NFVO requesting allocation of virtual resources to the VIM includes: and the NFVO calls a first resource allocation API interface to request allocation of virtual resources to the VIM.
Optionally, when it is determined that an abnormal condition occurs, the sending, by the NFVO, a VNF instance creation instruction to the VNFM further includes: monitoring the network connection state between the NFVO and the VIM and calling the state of a first resource allocation API interface; and when the network connection state between the NFVO and the VIM is determined and/or a first resource allocation API interface is called to be abnormal, judging that an abnormal condition occurs, and sending a VNF instance creating instruction to the VNFM by the NFVO.
Optionally, when it is determined that the network connection state between the NFVO and the VIM is abnormal, a network connection abnormality report message is sent to the NFVO, where information carried in the network connection abnormality report message includes: VIM identification, VIM state, network type, connection state, failure reason; when determining that the calling of the first resource allocation API interface is abnormal, sending an interface calling abnormal report message to the NFVO, wherein information carried in the interface calling abnormal report message includes: VIM identification, VIM state, API identification, API name, API call state, and failure reason.
Optionally, the VNFM requesting allocation of virtual resources for creating the VNF instance from the VIM comprises: the VNFM calls a second resource allocation API interface to request allocation of virtual resources for creating the VNF instance from the VIM; and the VNFM sends operation result information for calling a second resource allocation API interface to the NFVO.
According to another aspect of the present invention, there is provided a network function virtualization orchestrator NFVO, comprising: the resource scheduling module is used for requesting allocation of virtual resources to a virtual basic equipment management system (VIM) so as to create a Virtual Network Function (VNF) instance; the fault management module is used for sending a VNF instance creating instruction to a VNFM when the abnormal condition is judged to occur, and distributing the authority for creating the VNF instance to the VNFM; wherein the VNFM requests the VIM to allocate virtual resources for creating the VNF instance, and creates the VNF instance according to the virtual resources allocated by the VIM.
Optionally, the resource scheduling module is configured to receive, after requesting allocation of virtual resources to the VIM, virtual resource information, which is sent by the VIM and allocated to the VNF, of the VNF; the NFVO further comprises: and the configuration management module is used for sending the virtual resource information to the VNFM, and the VNFM creates a VNF instance according to the virtual resource information.
Optionally, the VNF instance creation instruction carries a resource reservation condition for creating the VNF instance and a network element attribute of the VNF instance; and the VNFM requests the VIM to allocate virtual resources for creating the VNF instance according to the resource reservation condition and the network element attribute.
Optionally, before the resource scheduling module requests the VIM to allocate virtual resources, the configuration management module sends an instantiation request of the VNF instance to the VNFM, where the instantiation request carries a virtualized network function description template, VNFD, of the VNF instance; the VNFM analyzes the VNFD, determines virtual resources required for deploying the VNF instances, and returns a virtual resource list for deploying the VNF instances to the configuration management module.
Optionally, the resource scheduling module is further configured to determine, based on the virtual resource list, to establish a virtual resource of the VNF instance, and request, from the VIM, to allocate a virtual resource for creating the VNF instance; the VIM allocates virtual resources required by the VNF instances and sends virtual resource information corresponding to the allocated virtual resources to the resource scheduling module; the configuration management module is further configured to send the virtual resource information to the VNFM to notify the VNFM that the configuration of the virtual resource is completed; the VNFM creates the VNF instance according to the information which is acquired from the configuration management module and needs to establish the VNF instance.
Optionally, the resource scheduling module is specifically configured to invoke a first resource allocation API interface to request allocation of a virtual resource to the VIM.
Optionally, the connection status monitoring module is configured to monitor a network connection status between the NFVO and the VIM; the API calls the monitoring module, is used for monitoring and calling the state of the first resource allocation API interface; the fault management module is further configured to determine that an abnormal condition occurs when it is determined that a network connection state between the NFVO and the VIM and/or an abnormality occurs when a first resource allocation API interface is called, and the resource scheduling module sends a VNF instance creation instruction to the VNFM.
Optionally, when it is determined that the network connection state between the NFVO and the VIM is abnormal, the connection state monitoring module sends a network connection abnormality report message to the fault management module, where information carried in the network connection abnormality report message includes: VIM identification, VIM state, network type, connection state, failure reason; when determining that the calling of the first resource allocation API interface is abnormal, the API calling monitoring module sends an interface calling abnormal report message to the fault management module, wherein the information carried in the interface calling abnormal report message includes: VIM identification, VIM state, API identification, API name, API call state, and failure reason.
Optionally, the VNFM calls a second resource allocation API interface to request allocation of virtual resources for creating the VNF instance from the VIM; and the VNFM sends operation result information for calling a second resource allocation API interface to the configuration management module.
According to still another aspect of the present invention, there is provided a network system including: a virtualized network function manager VNFM, a virtualized infrastructure device management system VIM, a network function virtualization orchestrator NFVO as described above.
According to the VNF establishing method, the NFVO and the network system, the instance of the VNF is established in the indirect mode, the direct mode is used as a backup mode during fault, and when the resource call for establishing the VM in the indirect mode fails, the direct mode is automatically sensed and switched to complete the resource call established by the VM and subsequent operations such as automatic establishment, monitoring and the like; by increasing the fault recovery capability of the indirect mode, when the NFVO cannot complete the VNF network element creation process, the VNFM and the VIM are adopted to perform resource allocation and VNF creation process, so that the VNF network element is automatically created with the fault recovery capability.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of an embodiment of a VNF establishment method according to the present invention;
FIG. 2 is a diagram illustrating partial calls to establish a VNF instance using a conventional indirection pattern;
figure 3 is a diagram of various part calls for establishing a VNF instance using the existing direct mode;
figure 4 is a schematic diagram of call-up of parts of an instance of establishing a VNF according to an embodiment of the method of establishing a VNF of the present invention;
fig. 5 is a schematic flow chart of another embodiment of a VNF establishment method according to the present invention;
fig. 6 is a schematic diagram of an example of establishing a VNF according to another embodiment of the VNF establishing method of the present invention;
fig. 7 is a block diagram of an embodiment of an NFVO according to the present invention.
Detailed Description
The present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. The technical solution of the present invention is described in various aspects below with reference to various figures and embodiments.
Fig. 1 is a schematic flow chart of an embodiment of a VNF establishment method according to the present invention, as shown in fig. 1:
step 101, the network function virtualization orchestrator NFVO requests the virtualized infrastructure management system VIM for allocation of virtual resources to create a virtualized network function VNF instance. The virtual resource may be a virtual machine VM or the like.
Under normal conditions, after the NFVO requests the VIM to allocate virtual resources, the NFVO receives the virtual resource information for VNF allocation sent by the VIM. And the NFVO sends the virtual resource information to the VNFM, and the VNFM creates a VNF instance according to the virtual resource information.
Step 102, when the abnormal condition is judged to occur, the NFVO sends a VNF instance creation instruction to the virtualized network function manager VNFM, so as to assign the right of creating the VNF instance to the VNFM.
The VNF instance creation instruction carries a resource reservation condition of the VNF instance creation and a network element attribute of the VNF instance, and the VNFM requests the VIM to allocate virtual resources for creating the VNF instance according to the resource reservation condition and the network element attribute.
Step 103, the VNFM requests the VIM to allocate virtual resources for creating VNF instances, and creates VNF instances according to the virtual resources allocated by the VIM.
In the direct mode and the indirect mode, the NFVO and the VNFM are interconnected and intercommunicated with a virtual facility management layer of the underlying VIM through different network connections, and the call of the VIM is completed through different API interfaces respectively. As shown in fig. 2, the indirect mode executes a resource allocation application for the VIM platform for the NFVO, and the VIM completes resource allocation. As shown in fig. 3, in the direct mode, the NFVO authorizes the VNFM to interact with the VIM to apply for resource allocation, and the VIM completes resource allocation.
The NFVO belongs to a higher-level network element in an NFV system and is responsible for resource global control and virtual machine state monitoring of the whole system, and different VNF network elements all have own VNFM, so that the positions of the VNFM, the network elements and the VIM are closer. If the indirect mode is adopted to complete the automatic generation of the virtual machine, because the NFVO is less compact than the VNFM in the VIM and the VNF, the probability of network failure or API call failure is greater. If network faults of the NFVO and the cloud platform and other abnormalities occur, subsequent flows of virtual machine state monitoring, alarming and the like are affected, and the fault between the NFVO and the VIM can cause the problem that resource allocation generated by the virtual machine fails and the virtual machine is finally pulled up to fail.
As shown in fig. 4, when the indirect mode is adopted, the reliability mechanism of the failure is realized by taking the direct mode as a backup mechanism, that is, both NFVO and VNFM keep the interworking with the connection of VIM and the API interface related to the resource call, and the NFVO and VNFM periodically exchange status information about the resource call. When the NFVO is connected with the VIM or the calling of the related API fails, the NFVO can quickly start a backup mechanism, the NFVO notifies and authorizes the VNFM to complete application of resource calling with the VIM cloud platform and assist the VIM in completing a subsequent VM creation process, and the resource calling and VNF instance generation states are fed back to the NFVO through a related interface of the NFVO.
In the method for establishing the VNF in the above embodiment, the instance of the VNF is established in the indirect mode, the direct mode is used as the backup mode when the fault occurs, and when the resource call for establishing the VM in the indirect mode fails, the indirect mode is automatically sensed and switched to the direct mode to complete the resource call created by the VM and subsequent operations such as automatic establishment and monitoring, so as to increase the fault recovery capability of the indirect mode.
Before the NFVO requests the VIM to allocate virtual resources, the NFVO sends an instantiation request for a VNF instance to a VNFM, where the instantiation request carries information such as a virtualized network function description template vnfd (VNF descriptor) for the VNF instance. The VNFM analyzes the VNFD, determines virtual resources required by the VNF instance deployment, and returns a virtual resource list for the VNF instance deployment to the NFVO.
The NFVO determines to establish virtual resources of the VNF instance based on the virtual resource list, and requests allocation of the virtual resources for creating the VNF instance to the VIM. The VIM allocates virtual resources required to create the VNF instance and sends virtual resource information corresponding to the allocated virtual resources to the NFVO. And the NFVO sends the virtual resource information to the VNFM to inform the VNFM of the completion of the virtual resource configuration. And the VNFM acquires information required to establish the VNF instance from the NFVO to establish the VNF instance.
Fig. 5 is a flowchart illustrating another embodiment of a VNF establishment method according to the present invention, as shown in fig. 5:
in step 501, the NFVO sends a VNF instantiation request operation to the VNFM.
Step 502, the VNFM parses the VNFD, obtains virtual resources required for deploying the VNF, and returns a resource list.
Step 503, the NFVO calls API interfaces related to VIM, and executes each step of the resource allocation application created by the VNF network element.
At step 504, NFVO notifies VNFM of the operation result of each step of calling the VIM-related API interface.
Step 505, when a connection exception occurs between the NFVO and the VIM or the API call fails, the operation of step 506 is triggered.
At step 506, the NFVO authorizes the VNFM operation right and notifies the VNFM of the resource reservation condition.
In step 507, the VNFM accepts the request to create the VNF instance in response to the NFVO.
And step 508, connecting the VNFM and the VIM, calling a relevant API interface, and executing a relevant operation of the resource allocation application created by the VNF network element.
In step 509, the VNFM notifies the NFVO of the operation result of each step.
NFVO calls a first resource allocation API interface to request allocation of virtual resources to the VIM. Monitoring the network connection state between the NFVO and the VIM and calling the state of the first resource allocation API interface. And when the network connection state between the NFVO and the VIM is determined and the first resource allocation API interface is called to be abnormal, judging that an abnormal condition occurs, and sending a VNF instance creating instruction to the VNFM by the NFVO. The VNFM requesting allocation of virtual resources for creating the VNF instance to the VIM may call a second resource allocation API interface, requesting allocation of virtual resources for creating the VNF instance to the VIM. And the VNFM sends operation result information for calling the second resource allocation API interface to the NFVO.
When determining that the network connection state between the NFVO and the VIM is abnormal, sending a network connection abnormal report message to the NFVO, wherein the information carried in the network connection abnormal report message comprises: VIM identification, VIM status, network type, status of connection, failure cause, etc. The format of the network connection exception report message is shown in table 1 below.
When determining that the calling of the first resource allocation API interface is abnormal, sending an interface calling abnormal report message to the NFVO, wherein information carried in the interface calling abnormal report message comprises: VIM identification, VIM state, API identification, API name, API call state, and failure reason. The format of the interface call exception report message is shown in table 2 below.
Figure BDA0001179421680000101
Table 1-format table of network connection exception report message
Figure BDA0001179421680000111
Table 2-format table of interface call exception report message
In the method for establishing the VNF in the embodiment, the NFVO is used as an indirect mode to dominate a deployment mode of a process of automatically creating the VNF network element, and a resource calling mode of the VNFM and the VIM is used as a backup mechanism to process related faults that may occur in a resource application and allocation process of the NFVO and the VIM, so as to increase a fault recovery capability of the indirect mode.
As shown in fig. 6, NFVO60, three components of the NFV architecture, is responsible for global resource management and network element performance monitoring. The VNFM61 is responsible for life cycle management of the network element and participates in an automatic generation process of the network element. The VIM cloud platform 63 is responsible for resource allocation of network elements. The three components are connected through different networks, the API interfaces between the three components are different in calling, and the three components complete the instantiation work of the VNF network element through related message interaction.
An operator initiates a VNF instantiation request, NFVO60 checks and initiates the VNF instantiation request to VNFM61, VNFM61 analyzes VNFD, obtains virtual resources required by VNF deployment, returns a resource list, and NFVO60 determines to accept the request according to the current available resource quantity, local policy and the like and requests to allocate resources to the VIM cloud platform 62. NFVO60 calls the relevant API interfaces of VIM cloud platform 62 regarding resource allocation while monitoring the status of the network connection and API interface calls between NFVO60 and VIM cloud platform 62. When monitoring that the network connection between the NFVO60 and the VIM cloud platform 62 is abnormal or an API call is wrong, notifying the NFVO60 of interworking with the VNFM61 according to the abnormal condition, notifying the VNFM61 of starting a backup mechanism, at the same time, authorizing the VNFM61 operation authority by the NFVO60 and notifying the VNFM61 of resource reservation, and responding to the VNFM61 and starting the connection with the VIM cloud platform 61 and a related API call flow.
The VNFM61 requests resources from the VIM cloud platform 62, the VIM cloud platform 62 notifies the VNFM61 after the resources are allocated, the VNFM61 configures VNF deployment parameters according to a template, the VNFM61 notifies the EMS to manage VNF, the EMS configures application parameters for VNF, and the VNFM61 notifies the NFVO60 to complete VNF instantiation. During the interaction between the VNFM60 and the VIM cloud platform 62, the operation result of each step is notified to the NFVO60, so that the NFVO60 knows the resource allocation and VNF network element creation.
In one embodiment, as shown in fig. 7, the present invention provides an NFVO70, comprising: a resource scheduling module 71, a fault management module 72, a configuration management module 73, a connection status monitoring module 74, an API call monitoring module 75, and the like. The resource scheduling module 71 requests allocation of virtual resources to the virtualized infrastructure management system, VIM, for creating a virtualized network function, VNF, instance. When it is determined that an abnormal condition occurs, the fault management module 72 sends a command to create a VNF instance to the virtualized network function manager VNFM, so as to assign a right to create the VNF instance to the VNFM. The VNFM requests the VIM to allocate virtual resources for creating the VNF instances, and creates the VNF instances according to the virtual resources allocated by the VIM.
The resource scheduling module 71 receives the virtual resource information for VNF allocation sent by the VIM after requesting allocation of virtual resources to the VIM. The configuration management module 73 sends the virtual resource information to the VNFM, and the VNFM creates a VNF instance according to the virtual resource information. The VNF instance creation instruction carries the resource reservation condition of the VNF instance creation and the network element attribute of the VNF instance. And the VNFM requests the VIM to allocate virtual resources for creating the VNF instance according to the resource reservation condition and the network element attribute.
Before the resource scheduling module 71 requests the VIM to allocate virtual resources, the configuration management module 73 sends an instantiation request for the VNF instance to the VNFM, where the instantiation request carries a virtualized network function description template VNFD for the VNF instance, and the like. The VNFM parses the VNFD, determines the virtual resources needed to deploy the VNF instance, and returns a list of the virtual resources to deploy the VNF instance to the configuration management module 73.
The resource scheduling module 71 determines, based on the virtual resource list, to establish virtual resources of the VNF instance, and requests allocation of the virtual resources for creating the VNF instance to the VIM. The VIM allocates virtual resources required to create the VNF instance and sends virtual resource information corresponding to the allocated virtual resources to the resource scheduling module 71. The configuration management module 73 sends the virtual resource information to the VNFM to notify the VNFM that the virtual resource configuration is completed. The VNFM creates a VNF instance according to the information that the VNF instance needs to be established, which is acquired from the configuration management module 73. The VNFM calls a second resource allocation API interface to request allocation of virtual resources for creating the VNF instance from the VIM. The VNFM sends operation result information calling the second resource allocation API interface to the configuration management module 72.
Resource scheduling module 71 invokes the first resource allocation API interface to request allocation of virtual resources to the VIM. The connection status monitoring module 74 monitors the status of the network connection between NFVO and VIM. The API call monitoring module 75 monitors the status of calling the first resource allocation API interface. When determining that the network connection state between the NFVO and the VIM and/or calling the first resource allocation API interface is abnormal, the fault management module 72 determines that an abnormal condition occurs, and the resource scheduling module 71 sends an instruction to create a VNF instance to the VNFM.
The fault management module 72 is responsible for collecting and managing network connection abnormal information of the NFVO and the VIM platform and abnormal information called by the API interface, and the resource scheduling module 71 notifies the NFVO and the VNFM communication subsystem to interact with the VNFM according to the abnormal information, so as to notify the VNFM to start connection and call with the VIM. The API call monitoring module 75 is responsible for monitoring the call states of the NFVO and the VIM platform with respect to the API interfaces related to resource allocation generated by the virtual machine, and when a certain API call is abnormal or the call is not in effect, the related information is fed back to the fault management module 72. The connection state monitoring module 74 is responsible for monitoring the network connection state between the NFVO and the VIM platform, and may determine whether the connection between the components is normal by sending a keepalive message periodically, and once a fault such as abnormal connection or connection interruption occurs between the NFVO and the VIM platform, the connection state monitoring module feeds back related information to the fault management module 72, and the related information is used as a basis for starting a subsequent process.
When determining that the network connection state between the NFVO and the VIM is abnormal, the connection state monitoring module 74 sends a network connection abnormality report message to the fault management module 72, where the information carried in the network connection abnormality report message includes: VIM identification, VIM status, network type, status of connection, failure cause, etc. When determining that the calling of the first resource allocation API interface is abnormal, the API call monitoring module 75 sends an interface call abnormal report message to the fault management module 72, where the information carried in the interface call abnormal report message includes: VIM identification, VIM status, API identification, API name, status of API call, failure cause, etc.
In one embodiment, the present invention provides a network system comprising: VNFM, VIM, NFVO as above.
In the method for establishing the VNF, the NFVO, and the network system in the above embodiments, the instance of the VNF is established in the indirect mode, the direct mode is used as a backup mode when a fault occurs, and when a resource call for establishing the VM in the indirect mode fails, the VNF is automatically sensed and switched to the direct mode to complete the resource call established by the VM and subsequent operations such as automatic establishment and monitoring; by increasing the fault recovery capability of the indirect mode, when the NFVO cannot complete the VNF network element creation process, VNFM and VIM are adopted to perform resource allocation and VNF creation process, so that the VNF network element is automatically created to have the fault recovery capability; based on monitoring of the API call state and the network connection state, fault management is carried out, and a VNFM is informed to serve as an execution unit of resource allocation when a fault occurs; the change to the NFV system architecture is small, and the actual operation of the existing network is facilitated.
The method and system of the present invention may be implemented in a number of ways. For example, the methods and systems of the present invention may be implemented in software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustrative purposes only, and the steps of the method of the present invention are not limited to the order specifically described above unless specifically indicated otherwise. Furthermore, in some embodiments, the present invention may also be embodied as a program recorded in a recording medium, the program including machine-readable instructions for implementing a method according to the present invention. Thus, the present invention also covers a recording medium storing a program for executing the method according to the present invention.
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims (15)

1. A method for establishing a Virtual Network Function (VNF), comprising:
a network function virtualization orchestrator NFVO requests a virtualized infrastructure equipment management system (VIM) to allocate virtual resources to create a Virtualized Network Function (VNF) instance;
when the abnormal condition is judged to occur, the NFVO sends a VNF instance creating instruction to a VNFM (virtual network function manager) so as to distribute a VNF instance creating authority to the VNFM;
the VNFM requests the VIM to allocate virtual resources for creating the VNF instances, and creates the VNF instances according to the virtual resources allocated by the VIM;
the VNF instance creation instruction carries a resource reservation condition for creating the VNF instance and a network element attribute of the VNF instance; the VNFM requests the VIM to allocate virtual resources for creating the VNF instances according to the resource reservation conditions and the network element attributes;
the VNFM returns a virtual resource list for deploying the VNF instance to the NFVO; the NFVO determines to establish virtual resources of the VNF instance based on the virtual resource list, and requests allocation of the virtual resources for creating the VNF instance to the VIM; the VIM allocates virtual resources required by the VNF instances and sends virtual resource information corresponding to the allocated virtual resources to the NFVO; the NFVO sends the virtual resource information to the VNFM to inform the VNFM of the completion of the configuration of the virtual resources; and the VNFM acquires information needing to establish the VNF instance from the NFVO to establish the VNF instance.
2. The method of claim 1, further comprising:
after the NFVO requests the VIM to allocate virtual resources, the NFVO receives the virtual resource information for the VNF allocation sent by the VIM;
and the NFVO sends the virtual resource information to the VNFM, and the VNFM creates a VNF instance according to the virtual resource information.
3. The method of claim 1, further comprising:
before the NFVO requests allocation of virtual resources to the VIM, the NFVO sends an instantiation request for the VNF instance to the VNFM, wherein the instantiation request carries a virtualized network function description template, VNFD, for the VNF instance;
the VNFM parses the VNFD, determines virtual resources needed to deploy the VNF instance, and returns the virtual resource list to the NFVO.
4. The method of claim 1, wherein the NFVO requesting allocation of virtual resources from the VIM comprises:
and the NFVO calls a first resource allocation API interface to request allocation of virtual resources to the VIM.
5. The method of claim 4, wherein the sending, by the NFVO to the VNFM, a create VNF instance instruction when the abnormal condition is determined to occur further comprises:
monitoring the network connection state between the NFVO and the VIM and calling the state of a first resource allocation API interface;
and when the network connection state between the NFVO and the VIM is determined and/or a first resource allocation API interface is called to be abnormal, judging that an abnormal condition occurs, and sending a VNF instance creating instruction to the VNFM by the NFVO.
6. The method of claim 5, further comprising:
when determining that the network connection state between the NFVO and the VIM is abnormal, sending a network connection abnormality report message to the NFVO, where information carried in the network connection abnormality report message includes: VIM identification, VIM state, network type, connection state, failure reason;
when determining that the calling of the first resource allocation API interface is abnormal, sending an interface calling abnormal report message to the NFVO, wherein information carried in the interface calling abnormal report message includes: VIM identification, VIM state, API identification, API name, API call state, and failure reason.
7. The method of claim 1, wherein the VNFM requesting allocation of virtual resources to the VIM for creating the VNF instance comprises:
the VNFM calls a second resource allocation API interface to request allocation of virtual resources for creating the VNF instance from the VIM;
and the VNFM sends operation result information for calling a second resource allocation API interface to the NFVO.
8. A network function virtualization orchestrator NFVO, comprising:
the resource scheduling module is used for requesting allocation of virtual resources to a virtual basic equipment management system (VIM) so as to create a Virtual Network Function (VNF) instance;
the fault management module is used for sending a VNF instance creating instruction to a VNFM when the abnormal condition is judged to occur, and distributing the authority for creating the VNF instance to the VNFM;
wherein the VNFM requests the VIM to allocate virtual resources for creating the VNF instance, and creates the VNF instance according to the virtual resources allocated by the VIM;
the VNF instance creation instruction carries a resource reservation condition for creating the VNF instance and a network element attribute of the VNF instance; the VNFM requests the VIM to allocate virtual resources for creating the VNF instances according to the resource reservation conditions and the network element attributes; the VNFM returns a virtual resource list for deploying the VNF instance to a configuration management module;
the resource scheduling module is further configured to determine, based on the virtual resource list, to establish a virtual resource of the VNF instance, and request allocation of the virtual resource for creating the VNF instance to the VIM; the VIM allocates virtual resources required by the VNF instances and sends virtual resource information corresponding to the allocated virtual resources to the resource scheduling module;
the configuration management module is further configured to send the virtual resource information to the VNFM to notify the VNFM that the configuration of the virtual resource is completed; the VNFM creates the VNF instance according to the information which is acquired from the configuration management module and needs to establish the VNF instance.
9. The NFVO of claim 8,
the resource scheduling module is configured to receive, after requesting allocation of virtual resources to the VIM, virtual resource information for the VNF allocation sent by the VIM;
the NFVO further comprises:
and the configuration management module is used for sending the virtual resource information to the VNFM, and the VNFM creates a VNF instance according to the virtual resource information.
10. The NFVO of claim 8,
before the resource scheduling module requests the VIM to allocate virtual resources, the configuration management module sends an instantiation request of the VNF instance to the VNFM, wherein the instantiation request carries a virtualized network function description template (VNFD) of the VNF instance;
the VNFM parses the VNFD, determines virtual resources needed to deploy the VNF instance, and returns the virtual resource list to the configuration management module.
11. The NFVO of claim 8,
the resource scheduling module is specifically configured to invoke a first resource allocation API interface to request allocation of virtual resources to the VIM.
12. The NFVO of claim 11, further comprising:
the connection state monitoring module is used for monitoring the network connection state between the NFVO and the VIM;
the API calls the monitoring module, is used for monitoring and calling the state of the first resource allocation API interface;
the fault management module is further configured to determine that an abnormal condition occurs when it is determined that a network connection state between the NFVO and the VIM and/or an abnormality occurs when a first resource allocation API interface is called, and the resource scheduling module sends a VNF instance creation instruction to the VNFM.
13. The NFVO of claim 12, further comprising:
when determining that the network connection state between the NFVO and the VIM is abnormal, the connection state monitoring module sends a network connection abnormality report message to the fault management module, where information carried in the network connection abnormality report message includes: VIM identification, VIM state, network type, connection state, failure reason;
when determining that the calling of the first resource allocation API interface is abnormal, the API calling monitoring module sends an interface calling abnormal report message to the fault management module, wherein the information carried in the interface calling abnormal report message includes: VIM identification, VIM state, API identification, API name, API call state, and failure reason.
14. The NFVO of claim 8,
the VNFM calls a second resource allocation API interface to request allocation of virtual resources for creating the VNF instance from the VIM; and the VNFM sends operation result information for calling a second resource allocation API interface to the configuration management module.
15. A network system, comprising:
virtualized network function manager VNFM, virtualized infrastructure device management system VIM, network function virtualization orchestrator NFVO according to any of claims 8 to 14.
CN201611149076.6A 2016-12-14 2016-12-14 VNF establishment method, NFVO and network system Active CN108234158B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611149076.6A CN108234158B (en) 2016-12-14 2016-12-14 VNF establishment method, NFVO and network system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611149076.6A CN108234158B (en) 2016-12-14 2016-12-14 VNF establishment method, NFVO and network system

Publications (2)

Publication Number Publication Date
CN108234158A CN108234158A (en) 2018-06-29
CN108234158B true CN108234158B (en) 2021-04-20

Family

ID=62638701

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611149076.6A Active CN108234158B (en) 2016-12-14 2016-12-14 VNF establishment method, NFVO and network system

Country Status (1)

Country Link
CN (1) CN108234158B (en)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110673981B (en) * 2018-07-03 2022-06-17 中国电信股份有限公司 Fault recovery method, device and system
CN110677268B (en) * 2018-07-03 2022-04-08 中国电信股份有限公司 NFV automatic arrangement scheduling method, device and system
CN110740047B (en) * 2018-07-18 2020-09-25 大唐移动通信设备有限公司 Network slice management arrangement system
CN110868310B (en) * 2018-08-27 2022-04-01 中国移动通信有限公司研究院 CDN edge node online and offline method, device and system
CN109379699B (en) * 2018-11-12 2020-08-25 中国联合网络通信集团有限公司 Method and device for creating virtual forwarding plane network element
CN111245634B (en) * 2018-11-29 2021-05-18 华为技术有限公司 Virtualization management method and device
CN109753343B (en) * 2018-11-30 2021-03-23 北京天元创新科技有限公司 VNF instantiation method and device
CN111399967B (en) * 2019-01-02 2023-03-31 中国移动通信有限公司研究院 Container-based virtual resource management method, device and system
CN111399968B (en) * 2019-01-02 2023-03-31 中国移动通信有限公司研究院 Virtual resource management method, device and system based on container
CN111404712B (en) * 2019-01-02 2023-01-03 中国移动通信有限公司研究院 NFV network element deployment system, method, device, medium and equipment
CN112087311B (en) 2019-06-14 2022-04-12 华为技术有限公司 Virtual network function VNF deployment method and device
CN112860370B (en) * 2019-11-27 2024-02-13 中国电信股份有限公司 Virtual machine resource allocation method, device, system and storage medium
CN113472552B (en) * 2020-03-30 2023-04-25 中国移动通信集团浙江有限公司 VIM selection method, device, computing equipment and storage medium based on deep learning
CN112333034A (en) * 2020-12-08 2021-02-05 上海欣方智能系统有限公司 Network architecture and method for realizing automatic operation and maintenance

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104115447A (en) * 2014-04-14 2014-10-22 华为技术有限公司 Allowing destroy scheme configuration method and device under cloud computing architecture
CN104980297A (en) * 2014-04-14 2015-10-14 中兴通讯股份有限公司 Virtual machine resource changing method and device, and virtualized network function device
CN105656646A (en) * 2014-11-10 2016-06-08 中国移动通信集团公司 Deploying method and device for virtual network element

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9806975B2 (en) * 2014-06-12 2017-10-31 Futurewei Technologies, Inc. Methods and systems for managing capacity in a virtualized network
US10263911B2 (en) * 2015-05-01 2019-04-16 Futurewei Technologies, Inc. System and method for resource management

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104115447A (en) * 2014-04-14 2014-10-22 华为技术有限公司 Allowing destroy scheme configuration method and device under cloud computing architecture
CN104980297A (en) * 2014-04-14 2015-10-14 中兴通讯股份有限公司 Virtual machine resource changing method and device, and virtualized network function device
CN105656646A (en) * 2014-11-10 2016-06-08 中国移动通信集团公司 Deploying method and device for virtual network element

Also Published As

Publication number Publication date
CN108234158A (en) 2018-06-29

Similar Documents

Publication Publication Date Title
CN108234158B (en) VNF establishment method, NFVO and network system
US10601657B2 (en) Instance node management method and management device
US10931525B2 (en) Managing planned adjustment of allocation of resources in a virtualised network
EP3800926B1 (en) Alarm method and device
US10644952B2 (en) VNF failover method and apparatus
US10140112B2 (en) Update management system and update management method
EP3163797B1 (en) Service orchestration method and apparatus in software-defined networking, and storage medium
CN103618621B (en) A kind of software defined network SDN method of automatic configuration, equipment and system
CA2975071A1 (en) Management of network functions virtualization and orchestration apparatus, system, management method, and program
US11886904B2 (en) Virtual network function VNF deployment method and apparatus
WO2017133020A1 (en) Method and device for policy transmission in nfv system
Lee et al. Fault localization in NFV framework
CN114338670B (en) Edge cloud platform and network-connected traffic three-level cloud control platform with same
CN113973127B (en) Network deployment method, device and storage medium
CN107122228A (en) The dispositions method and device of the management platform of super emerging system
CN115640096A (en) Application management method and device based on kubernets and storage medium
CN107783855B (en) Fault self-healing control device and method for virtual network element
WO2019216210A1 (en) Service continuation system and service continuation method
CN111209145A (en) Virtual machine disaster tolerance-based service self-healing method, equipment and storage medium
CN110417568B (en) NFV strategy negotiation method and system
CN116820686B (en) Physical machine deployment method, virtual machine and container unified monitoring method and device
CN110545193B (en) Virtual resource management method, virtual resource management equipment and server
TWI659631B (en) Method and system for establishing virtual backup network and virtual network card
CN112199167A (en) High-availability method for multi-machine rapid one-key deployment based on battlefield environment
KR20200011079A (en) System for upgrading / updating software of virtual network apparatus or system, method thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant