WO2016107506A1 - 虚拟网络加载方法和装置 - Google Patents

虚拟网络加载方法和装置 Download PDF

Info

Publication number
WO2016107506A1
WO2016107506A1 PCT/CN2015/099070 CN2015099070W WO2016107506A1 WO 2016107506 A1 WO2016107506 A1 WO 2016107506A1 CN 2015099070 W CN2015099070 W CN 2015099070W WO 2016107506 A1 WO2016107506 A1 WO 2016107506A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
nfvo
nsd
vnfd
image file
Prior art date
Application number
PCT/CN2015/099070
Other languages
English (en)
French (fr)
Inventor
余芳
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2016107506A1 publication Critical patent/WO2016107506A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

  • the embodiments of the present invention relate to network technologies, and in particular, to a virtual network loading method and apparatus.
  • NFV White Paper Network Function Virtualization
  • ETSI European Telecommunications Standards Institute
  • ISG Industry Standard Group
  • the sponsors of NFV ISG include American Telephone &
  • the purpose of the NFV ISG is to define the requirements for the virtualization of the operator's network functions and related technical reports. It is hoped that the information technology (Information Technology, IT for short) virtualization technology will be used in general-purpose high-performance servers and network switches. Implement some network functions in the storage device. This requires network functions to be implemented in software and run on common server hardware, which can be migrated, instantiated, deployed in different locations on the network as needed, and does not require new equipment to be installed.
  • Various types of network devices such as servers, routers, storage devices, switches, etc., can be separated by software and hardware through NFV technology. They can be deployed in data centers, network nodes, or users' homes.
  • NFV has three key features: completely separate software that defines network functions from common high-performance hardware servers, storage devices, and network switches; independent modular features of software and hardware components; Automate remote installation and management of software devices.
  • a Network Service (NS) instance consists of multiple Virtualization Network Function (VNF) instances. Needed in the NS instance To add a VNF, you need to perform VNF loading (On-boarding).
  • the VNF On-boarding process refers to the submission of the VNF Package (VNF Package) to the Network Functions Virtualization Orchestrator (NFVO), which enables NFVO to incorporate the VNF Package into the Virtualized Infrastructure Manager Descriptor (Virtualised Infrastructure Manager Descriptor, VNFD) in the directory.
  • VNF Package is an archive of the VNF, including the VNFD of the VNF, the Virtual Machine Image (VM image) file, and other components, such as the components used to check the integrity of the archive and prove its validity.
  • the VM image file will be uploaded to the Virtualized Infrastructure Manager (VIM), so that when the NFVO receives the VNF instantiation request, it can directly read the VIM.
  • VIM Virtualized Infrastructure Manager
  • the VM image file can save time for VNF instantiation.
  • VNF virtualization deployment unit
  • VDU Select the location of the deployment. Different deployment locations will correspond to different VIMs. Therefore, during the VNF On-boarding process, the VNF image file will be uploaded to multiple possible VIMs, so that after the VNF is instantiated, the VM image file can be read in the corresponding VIM, thereby saving the VNF instantiation. time.
  • the VM image file accounts for the majority. In the process of VNF On-boarding, uploading the VM image file to multiple possible VIMs may result in The VM image file is uploaded to the unrelated VIM, which may cause unnecessary operations and waste of network transmission resources and storage space on the VIM during loading.
  • the embodiment of the invention provides a virtual network loading method and device for optimizing a virtual network loading process, saving network transmission resources in the loading process and storage resources in the VIM.
  • the first aspect provides a network function virtualization orchestrator, including:
  • a receiving module configured to receive an NSD sent by the first network entity
  • a processing module configured to select a candidate that can allocate a virtual resource to the VNF when deploying the VNF according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory VIM;
  • a sending module configured to send a URL corresponding to the VM image file of the stored VNF or the VM image file of the VNF to the candidate VIM; notify the NS directory to join the NSD; and send an NSD loading success notification message to the first network entity .
  • the receiving module is further configured to: before receiving the NSD sent by the first network entity, receive the VNF package sent by the first network entity;
  • the sending module is further configured to notify the VNF directory to join the VNFD in the VNF package;
  • the NFVO further includes: a storage module, configured to store a VM image file of the VNF in the VNF package or a URL corresponding to the VM image file of the VNF;
  • the sending module is further configured to send a VNF package loading success notification message to the first network entity.
  • the processing module is further configured to: store, in the storage module, a VM image of a VNF in the VNF package Check the VNF package before the URL corresponding to the file or VNF VM image file;
  • the storage module is specifically configured to store a VM image file of the VNF in the VNF package if the VNF package includes a VM image file of the VNF package; if the VNF package includes a VM image file of the VNF
  • the corresponding URL stores the URL corresponding to the VM image file of the VNF in the VNF package.
  • the processing module is further configured to: when the sending module notifies the VNF directory to join the Before the VNFD in the VNF package, verifying the VNF package, the processing module verifying the VNF package, including at least one of the following steps: the processing module checks whether a necessary element in the VNF package is Existing, the processing module verifies the authenticity and reliability of the VNFD using a form and a certificate in the VNFD in the VNF package;
  • the sending module is specifically configured to: if the processing module checks for a necessary element in the VNF package, or if the processing module uses the VNFD in the VNF package The form and certificate verify that the VNFD is authentic and reliable, and then notify the VNF directory to join the VNFD in the VNF package.
  • the processing module is further configured to perform the NSD according to the NSD The restriction condition in the VNFD in the VNF directory, selecting a candidate VIM capable of allocating a virtual resource to the VNF when the VNF is deployed, verifying the NSD, the processing module verifying the NSD, including the following steps At least one of: the processing module checks whether a VNF package of the VNF in the NS described by the NSD exists, the processing module checks whether a necessary element in the NSD exists, and the processing module checks whether the VNFD is present Describe the external interface required to provide NS;
  • the processing module is further configured to: if the VNF package of the VNF in the NS described by the NSD is checked, check for the existence of a necessary element in the NSD, and check that the VNFD has an external interface required to provide the NS. Then, select a candidate VIM that can allocate virtual resources to the VNF when deploying the VNF.
  • the limiting condition in the NSD includes at least one of the following conditions a: a limitation of a deployment location of the VNF in the NS described by the NSD, an identifier of the VIM corresponding to the NS deployment location described by the NSD, and an affinity description between the VNFs included in the NSD description NS; the VNFD
  • the constraint condition includes at least one of the following: a constraint of deployment of the VNF or VNFC described by the VNFD, an identifier of a VIM corresponding to a VNF or VNFC deployment location of the VNFD, and a VNF described by the VNFD. Affinity description between VDUs.
  • the sending module is specifically configured to use the VNF image management interface. Sending the VM image file of the stored VNF to the candidate VIM; or sending the URL corresponding to the VM image file of the stored VNF to the candidate VIM through the VNF image management interface.
  • the sending module is specifically used to describe the NSD All VNF VM image files included in the NS are stored to When the corresponding VIM is received, the NS directory is notified to join the NSD.
  • the second aspect provides a network function virtualization orchestrator, including:
  • a receiving module configured to receive an NSD sent by the first network entity
  • a processing module configured to select, according to the restriction condition in the NSD and a restriction condition in the VNFD in the VNF directory, a candidate VIM capable of allocating a virtual resource to the VNF when the VNF is deployed;
  • a sending module configured to notify the candidate VIM to download a VM image file according to a URL corresponding to the VM image file; notify the NS directory to join the NSD; and send an NSD loading success notification message to the first network entity.
  • the receiving module is further configured to: before receiving the NSD sent by the first network entity, receive the VNF package sent by the first network entity;
  • the sending module is further configured to notify the VNF directory to join the VNFD in the VNF package, and send a URL corresponding to the VM image file of the VNF in the VNF package to the at least one VIM;
  • the network entity sends a VNF package loading success notification message.
  • the sending module is specifically configured to send a URL corresponding to the VM image file of the VNF in the VNF package Give all VIMs connected to the NFVO.
  • the processing module is further configured to: when the sending module notifies the VNF directory to join the Before the VNFD in the VNF package, verifying the VNF package, the processing module verifying the VNF package, including at least one of the following steps: the processing module checks whether a necessary element in the VNF package is Existing, the processing module verifies the authenticity and reliability of the VNFD using a form and a certificate in the VNFD in the VNF package;
  • the sending module is specifically configured to: if the processing module checks for a necessary element in the VNF package, or if the processing module uses the form and certificate in the VNFD in the VNF package to verify that the VNFD has Authenticity and reliability, the VNF directory is notified to join the VNFD in the VNF package.
  • the processing module is further configured to perform the NSD according to the The restriction condition in the VNFD in the VNF directory, selecting a candidate VIM capable of allocating a virtual resource to the VNF when the VNF is deployed, verifying the NSD, the processing module verifying the NSD, including the following steps At least one of: the processing module checks whether a VNF package of the VNF in the NS described by the NSD exists, the processing module checks whether a necessary element in the NSD exists, and the processing module checks whether the VNFD is present Describe the external interface required to provide NS;
  • the processing module is further configured to: if the VNF package of the VNF in the NS described by the NSD is checked, check for the existence of a necessary element in the NSD, and check that the VNFD has an external interface required to provide the NS. And selecting, for the NFVO, a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed.
  • the limitation condition in the NSD includes at least one of the following conditions a: a limitation of a deployment location of the VNF in the NS described by the NSD, an identifier of the VIM corresponding to the NS deployment location described by the NSD, and an affinity description between the VNFs included in the NSD description NS; the VNFD
  • the constraint condition includes at least one of the following: a constraint of deployment of the VNF or VNFC described by the VNFD, an identifier of a VIM corresponding to a VNF or VNFC deployment location of the VNFD, and a VNF described by the VNFD. Affinity description between VDUs.
  • the sending module is specifically configured to use the VNF image management interface
  • the VIM is notified to download the VM image file according to the URL corresponding to the VM image file.
  • the sending module is specifically used to describe the NSD When all VM image files of the VNF included in the NS are sent to the corresponding candidate VIM, the NS directory is notified to join the NSD.
  • the third aspect provides a virtual network loading method, including:
  • the NFVO receives the NSD sent by the first network entity
  • the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory;
  • the NFVO sends the URL corresponding to the VM image file of the stored VNF or the VM image file of the VNF to the candidate VIM;
  • the NFVO notifies the NS directory to join the NSD
  • the NFVO sends an NSD loading success notification message to the first network entity.
  • the method before the NFVO receives the NSD sent by the first network entity, the method further includes:
  • the NFVO notifies the VNF directory to join the VNFD in the VNF package
  • the NFVO stores a VM image file of the VNF in the VNF package or a URL corresponding to the VM image file of the VNF;
  • the NFVO sends a VNF package loading success notification message to the first network entity.
  • the NFVO stores a VM image file of the VNF in the VNF package or a URL corresponding to the VM image file of the VNF Previously, it also included:
  • the NFVO checks the VNF package
  • the NFVO stores a URL corresponding to the VM image file of the VNF in the VNF package or the VM image file of the VNF, including:
  • the NFVO stores a VM image file of the VNF in the VNF package; if the VNF package includes a URL corresponding to the VM image file of the VNF, The NFVO stores a URL corresponding to the VM image file of the VNF in the VNF package.
  • the method further includes :
  • the NFVO verifies the VNF package, and the NFVO verifies the VNF package, including at least one of the following steps: the NFVO checks whether a necessary element in the VNF package exists, and the NFVO usage Table in VNFD in the VNF package Single and certificate verification of the authenticity and reliability of the VNFD;
  • the NFVO notifies the VNF directory to join the VNFD in the VNF package, including:
  • the NFVO checks for the presence of a necessary element in the VNF package, or if the NFVO uses the form and certificate in the VNFD in the VNF package to verify that the VNFD is authentic and reliable, then the NFVO The VNF directory is notified to join the VNFD in the VNF package.
  • the NFVO is based on a constraint condition and a VNF in the NSD.
  • the restrictions in the VNFD in the directory, before selecting a candidate VIM that can allocate virtual resources to the VNF when deploying the VNF include:
  • the NFVO verifies the NSD, and the NFVO verifies the NSD, including at least one of the following steps: the NFVO checks whether a VNF package of a VNF in the NS described by the NSD exists, the NFVO checkpoint Whether the necessary elements in the NSD are present, and the NFVO checks whether the VNFD has an external interface required to provide the NS;
  • the NFVO selects a candidate VIM that can allocate a virtual resource to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory, including:
  • the NFVO checks for the presence of a VNF package for the VNF in the NS described by the NSD, the NFVO checks for the presence of a necessary element in the NSD, and the NFVO checks that the VNFD has an external interface required to provide the NS Then, the NFVO selection can allocate a candidate VIM of the virtual resource to the VNF when the VNF is deployed.
  • the limitation condition in the NSD includes at least one of the following conditions a: a limitation of a deployment location of the VNF in the NS described by the NSD, an identifier of the VIM corresponding to the NS deployment location described by the NSD, and an affinity description between the VNFs included in the NSD description NS; the VNFD
  • the constraint condition includes at least one of the following: a constraint of deployment of the VNF or VNFC described by the VNFD, an identifier of a VIM corresponding to a VNF or VNFC deployment location of the VNFD, and a VNF described by the VNFD. Affinity description between VDUs.
  • the NFVO is to store the VM image file or the VM image
  • the URL corresponding to the file is sent to the candidate VIM, including:
  • the NFVO sends the VM image file of the stored VNF to the candidate VIM through the VNF image management interface; or the NFVO sends the URL corresponding to the VM image file of the stored VNF to the candidate through the VNF image management interface.
  • VIM the NFVO
  • the NFVO notifying the NS directory to join the NSD includes:
  • the NFVO notifies the NS directory to join the NSD.
  • the fourth aspect provides a virtual network loading method, including:
  • the NFVO receives the NSD sent by the first network entity
  • the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory;
  • the NFVO notifies the candidate VIM to download a VM image file according to a URL corresponding to the VM image file;
  • the NFVO notifies the NS directory to join the NSD
  • the NFVO sends an NSD loading success notification message to the first network entity.
  • the method before the NFVO receives the NSD sent by the first network entity, the method further includes:
  • the NFVO notifies the VNF directory to join the VNFD in the VNF package
  • the NFVO sends a URL corresponding to the VM image file of the VNF in the VNF package to at least one VIM;
  • the NFVO sends a VNF package loading success notification message to the first network entity.
  • the NFVO sends a URL corresponding to the VM image file of the VNF in the VNF package to the at least one VIM, Includes:
  • the NFVO sends a URL corresponding to the VM image file of the VNF in the VNF package to all VIMs connected to the NFVO.
  • the method further includes :
  • the NFVO verifies the VNF package, and the NFVO verifies the VNF package, including at least one of the following steps: the NFVO checks whether a necessary element in the VNF package exists, and the NFVO usage Forms and certificates in the VNFD in the VNF package verify the authenticity and reliability of the VNFD;
  • the NFVO notifies the VNF directory to join the VNFD in the VNF package, including:
  • the NFVO checks for the presence of a necessary element in the VNF package, or if the NFVO uses the form and certificate in the VNFD in the VNF package to verify that the VNFD is authentic and reliable, then the NFVO The VNF directory is notified to join the VNFD in the VNF package.
  • the NFVO is based on a restriction condition and a VNF in the NSD
  • the restrictions in the VNFD in the directory, before selecting a candidate VIM that can allocate virtual resources to the VNF when deploying the VNF include:
  • the NFVO verifies the NSD, and the NFVO verifies the NSD, including at least one of the following steps: the NFVO checks whether a VNF package of a VNF in the NS described by the NSD exists, the NFVO checkpoint Whether the necessary elements in the NSD are present, and the NFVO checks whether the VNFD has an external interface required to provide the NS;
  • the NFVO selects a candidate VIM that can allocate a virtual resource to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory, including:
  • the NFVO checks for the presence of a VNF package for the VNF in the NS described by the NSD, the NFVO checks for the presence of a necessary element in the NSD, and the NFVO checks that the VNFD has an external interface required to provide the NS Then, the NFVO selection can allocate a candidate VIM of the virtual resource to the VNF when the VNF is deployed.
  • the limitation condition in the NSD includes at least one of the following conditions a: a limitation of a deployment location of the VNF in the NS described by the NSD, an identifier of the VIM corresponding to the NS deployment location described by the NSD, and an affinity description between the VNFs included in the NSD description NS; the VNFD
  • the constraint condition includes at least one of the following: a constraint of deployment of the VNF or VNFC described by the VNFD, an identifier of a VIM corresponding to a VNF or VNFC deployment location of the VNFD, and a VNF described by the VNFD. Affinity description between the virtualized deployment unit VDUs.
  • the fourth possible implementation manner of the fourth aspect the NFVO notifying the candidate VIM according to the VM Download the VM image file for the URL corresponding to the image file, including:
  • the NFVO notifies the candidate VIM to download the VM image file according to the URL corresponding to the VM image file through the VNF image management interface.
  • the NFVO notifying the NS directory to join the NSD including :
  • the NFVO notifies the NS directory to join the NSD.
  • a fifth aspect provides a virtualization infrastructure manager, comprising:
  • a receiving module configured to receive a URL corresponding to the VM image file of the VNF sent by the NFVO;
  • a storage module configured to store a URL corresponding to the VM image file of the VNF
  • the receiving module is further configured to receive a download notification message sent by the NFVO, where the download notification message is used to instruct the VIM to download a VM image file corresponding to a VM image file of the VNF.
  • the processing module is configured to download the VM image file according to the URL corresponding to the VM image file of the VNF, where the VIM is a candidate VIM that can allocate a virtual resource to the VNF corresponding to the VM image file when the VNF is deployed.
  • the sixth aspect provides a virtual network loading method, including:
  • the VIM receives the URL corresponding to the VM image file of the VNF sent by the NFVO;
  • the VIM stores a URL corresponding to the VM image file of the VNF
  • the VIM receives the download notification message sent by the NFVO, where the download notification message is used to instruct the VIM to download a VM image file corresponding to the VM image file of the VNF.
  • the VIM downloads the VM image file according to the URL corresponding to the VM image file of the VNF, and the VIM is a candidate VIM that can allocate a virtual resource to the VNF corresponding to the VM image file when the VNF is deployed.
  • the virtual network loading method and apparatus in the NSD loading process, select a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed according to the restriction conditions in the VNFD in the NSD and VNF directories, and then The URL corresponding to the VM image file of the VNF or the VM image file of the VNF is sent to the candidate VIM, and then the NSD loading process is ended, thereby avoiding sending the VM image file of the VNF to the unrelated VIM, thereby saving the loading process.
  • Network transport resources and VIM storage space and avoid the operations required to send VM image files to unrelated VIMs.
  • Figure 1 is a schematic diagram of the NFV MANO architecture
  • FIG. 2 is a schematic diagram of signaling of VNF loading
  • 3 is a schematic diagram of signaling of NSD loading
  • Embodiment 1 of an NFVO is a schematic structural diagram of Embodiment 1 of an NFVO according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of Embodiment 2 of an NFVO according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of Embodiment 1 of a virtual network loading method according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of Embodiment 2 of a virtual network loading method according to an embodiment of the present disclosure
  • FIG. 8 is a flowchart of Embodiment 3 of a virtual network loading method according to an embodiment of the present disclosure.
  • FIG. 9 is a flowchart of Embodiment 4 of a virtual network loading method according to an embodiment of the present disclosure.
  • FIG. 10 is a signaling flowchart of Embodiment 1 of a VNF loading and loading method according to an embodiment of the present disclosure
  • FIG. 11 is a signaling flowchart of Embodiment 1 of an NSD loading and loading method according to an embodiment of the present disclosure
  • FIG. 12 is a signaling flowchart of Embodiment 2 of a VNF loading and loading method according to an embodiment of the present disclosure
  • FIG. 13 is a signaling flowchart of Embodiment 2 of an NSD loading and loading method according to an embodiment of the present disclosure
  • FIG. 14 is a signaling flowchart of Embodiment 3 of a VNF loading and loading method according to an embodiment of the present disclosure
  • FIG. 15 is a signaling flowchart of Embodiment 3 of an NSD loading and loading method according to an embodiment of the present disclosure
  • FIG. 16 is a schematic structural diagram of Embodiment 1 of a virtualization infrastructure manager according to an embodiment of the present disclosure
  • FIG. 17 is a flowchart of Embodiment 5 of a virtual network loading method according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of the NFV MANO architecture.
  • the NFV MANO architecture 11 includes: Network Function Virtualization Orchestrator (NFVO) 101, Virtualized Network Function Manager (VNFM). 102, Virtualization Infrastructure Manager (VIF) 103, and NS Directory 104, VNF Directory 105, NFV Instances 106, NFV Infrastructure (NFV Infrastructure) Capital Resources 107 four databases.
  • NFVO Network Function Virtualization Orchestrator
  • VNFM Virtualized Network Function Manager
  • VIP Virtualization Infrastructure Manager
  • NS Directory 104 VNF Directory 105
  • NFV Instances 106 NFV Infrastructure (NFV Infrastructure)
  • NFV Infrastructure NFV Infrastructure
  • NFVO 101 implements Network Service Descriptor (NSD), management and processing of Virtualized Network Function Forwarding Graph (VNFFG), management of NS lifecycle, and VNFM 102 to implement VNF. 12 lifecycle management and global view capabilities of resources.
  • VNFM 102 implements lifecycle management of VNF 12, including management and processing of Virtualized Network Function Descriptor (VNFD), initialization of VNF instance, expansion/reduction of VNF12, and termination of VNF instance. Supports receiving the capacity scaling policy delivered by NFVO 101 to achieve capacity adjustment of VNF 12.
  • VIM 103 is mainly responsible for infrastructure layer hardware resources, virtualization resource management, monitoring and fault reporting, and provides virtualized resource pools for upper-layer applications.
  • the NS Catalog 104 includes all NSDs that have been loaded.
  • the VNF Catalog 105 includes all VNF Packages that have been loaded.
  • NFV Instances 106 includes all running NS instances and VNF instances.
  • NFVI Resources 107 includes all NFVI resource status, available/reserved/allocated NFVI resources.
  • the VNF 12 corresponds to a Physical Network Function (PNF) in a traditional non-virtualized network, such as an evolved Evolved Packet Core (EPC) node (Mobile Management Entity, Mobile Management Entity, MME), Service Gateway (SGW), Packet Data Network Gateway (PGW), etc.
  • EPC evolved Evolved Packet Core
  • MME Mobile Management Entity
  • SGW Service Gateway
  • PGW Packet Data Network Gateway
  • VNF 12 can be composed of multiple lower-level components. Therefore, one VNF 12 can be deployed on multiple virtual machines (VMs), each VM host a VNF component; VNF 12 can also be deployed. On a VM.
  • VMs virtual machines
  • the Operations Support Systems (OSS)/Business Support Systems (BSS) 13 refers to the existing OSS/BSS of the operator.
  • Element Management System (EMS)/Network Management System (NMS) 14 performs traditional fault management, configuration management, billing management, performance management, and security management (Fault Management, Configuration Management, for VNF 12). Accounting Management, Performance Management, Security Management, referred to as FCAPS).
  • NFVI 15 consists of hardware resources and virtual resources as well as virtual layers. From a VNF perspective, the virtualization layer and hardware resources appear to be an entity that provides the required virtual resources.
  • the number of VNFMs 102 and VIMs 103 may be multiple.
  • the VNFM 102 manages and maintains multiple VNFs
  • the VIM 103 manages and maintains the virtual resources required to deploy the VNFs.
  • NFVO 101 and OSS/BSS 13 are connected through Os-Ma-Nfvo interface
  • NFVO 101 and VNFM 102 are connected through Or-Vnfm interface
  • VNFM 102 and VIM 103 are connected through Vi-Vnfm interface
  • NFVO 101 and VIM 103 are connected through Or-Vi interface.
  • the VNFM 102 is connected to the VNF 12 via the Ve-Vnfm-vnf interface
  • the VNFM 102 is connected to the EMS/NMS 14 via the Ve-Vnfm-em interface
  • the VIM 103 is connected to the NFVI 15 via the Nf-Vi interface.
  • the NFVO 101 is connected to four databases of the NS Catalog 104, the VNF Catalog 105, the VNF Instances 106, and the NFV Resources 107
  • the VNFM 102 is connected to the database VNF Catalog 105.
  • FIG. 2 shows the signaling diagram of VNF loading.
  • the first step is In S201, the VNF package needs to be sent by the sender to the NFVO.
  • the VNF package includes the VNFD and the VM image file of the VNF, and requests the NFVO to load the VNFD in the VNF package, where the sender is usually OSS. That is, the operator's operation administrator manually triggers the VNF loading; the sender may also be other authorized third-party entities, such as a third-party network service provider.
  • step S202 the NFVO processes the received VNFD, including but not limited to checking whether some necessary elements are present, and verifying the authenticity and reliability of the VNFD with the form and certificate in the VNFD.
  • step S203 when the NFVO verifies the VNFD, the NFVO sends the VNFD to the NFV directory, informing the VNF directory to join the VNFD.
  • step S204 the NFVO sends the VM image file in the VNF package to the VIM.
  • step S205 when the VIM confirms that the VM image file transmitted by the NFVO is received, the VM image file is stored, and the VIM transmits a reception success confirmation message to the NFVO.
  • step S206 after receiving the reception success confirmation message sent by the VIM, the NFVO will send a VNF package loading success notification message to the transmitting end.
  • NFVO In the NFV MANO architecture, there may be multiple VIMs in an NFVO management domain. During VNF loading, NFVO cannot know which VIM the loaded VNF corresponds to during the instantiation process. Therefore, NFVO may need to be sent to multiple VIMs. All possible VIMs for NFVO) Send the VM image file in the VNF package. Thus, when the NFVO receives the instantiation request of the VNF, since the VM image file of the VNF is already stored in the VIM, this will save time for instantiation of the VNF. However, in the VNF instantiation process, each VDU of the VNF has only a certain deployment location.
  • VNF For each VDU of the VNF, there is only one corresponding VIM, so that when the VNF is instantiated, some VIMs may be stored.
  • the VNF VM image file will not be used. Since the size of the VNF package is gigabyte-sized, the VM image file accounts for the majority, and the VM image file that some VIM storage will not be used will waste a lot of storage space, and NFVO sends VM image files to multiple VIMs. Will produce some unnecessary operations.
  • the NSD loading process in NFV is considered.
  • the NSD loading process and the VNFD loading process are two independent processes, and in principle, the VNF loading process of the VNF included in the NS is completed first, and then the NSD loading process is performed. Therefore, the process of sending the VM image file in the VNF package can be performed in the NSD loading process, and the VIM that may allocate the virtual resource for the deployment of the VNF is selected in advance, thereby avoiding the process of the NFVO sending the VM image file to the unrelated VIM.
  • FIG. 3 is a schematic diagram of signaling of NSD loading.
  • the NSD is required to be sent by the transmitting end to the NFVO, where the transmitting end is usually It is OSS, that is, the operator's operation administrator manually triggers NSD loading; the sender can also be other authorized third-party entities, such as third-party network service providers.
  • the NFVO processes the received NSD, including but not limited to checking whether the VNF package (VNF package) of the VNF in the NS exists, checking whether some necessary elements exist, and checking whether there is a description in the VNFD to provide the NS. External interface.
  • VNF package VNF package
  • step S303 when the NFVO verification of the NSD is passed, the NFVO sends the NSD to the NS directory.
  • step S304 if the NFVO has sent the NSD to the NS directory, the NSD loading success notification message is sent to the transmitting end.
  • FIG. 4 is a schematic structural diagram of Embodiment 1 of an NFVO according to an embodiment of the present invention. As shown in FIG. 4, the NFVO of this embodiment includes:
  • the receiving module 41 is configured to receive an NSD sent by the first network entity.
  • the NFVO provided by the embodiment improves the existing NSD loading process.
  • the receiving module 41 receives the NSD sent by the first network entity, triggering an NSD loading process, where the first network entity sends the NSD loading.
  • the first network entity is usually The OSS, that is, the operator's operation administrator manually triggers the NSD loading, and the first network entity may also be other authorized third-party entities, such as a third-party network service provider.
  • the processing module 42 is configured to select a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory.
  • this embodiment is a loading process of the NSD. Since an NS is composed of multiple VNFs, the loading process of each VNF in the NS needs to be performed before the NSD is loaded. After the VNFs in the NS are loaded, the NSD can be performed. Loading. Therefore, before the receiving module 41 receives the NSD sent by the first network entity in this embodiment, the NFVO provided in this embodiment should also perform the loading process of each VNF in the NS. In the VNF loading process, the NFVO receives the VM image file of the VNF in the VNF package, or the Uniform Resource Locator (URL) corresponding to the VM image file that the NFVO can receive only for the VNF.
  • URL Uniform Resource Locator
  • the URL corresponding to the VM image file of the VNF indicates the download address corresponding to the VM image file of the VNF.
  • NFVO can store the URL of the VNF image file received in the VNF loading process or the URL of the VNF VM image file.
  • the processing module 42 selects the deployment according to the restriction conditions in the NSD and the restriction conditions in the VNFD read from the VNF directory.
  • the VNF allocates a candidate VIM of virtual resources to the VNF.
  • a VNF may contain multiple VNF components (VNFs, VNFs).
  • VNFs VNFs
  • VNFs VNFs
  • the VDUs corresponding to these VNFCs may need to be deployed across VIMs.
  • the VDUs corresponding to these VNFCs may also need to be deployed in a VIM management domain.
  • the URLs corresponding to the VM image files or VM image files of different VDUs need to be uploaded to the same VIM.
  • the candidate VIMs that can be allocated for each VNFC to allocate virtual resources may be one or more.
  • the restrictions in the NSD and the restrictions in the VNFD define the location where the NS is to be deployed, the location where the VNF is to be deployed, and the relationship between the VNF deployment locations in the NS.
  • the NFVO determines the deployment location of the VNF based on the above various location relationships. , that is, the VIM corresponding to the VNF. After the NFVO determines the VIM corresponding to the VNF, the corresponding VIM is selected for the URL corresponding to the VM image file of the VNF or the VM image file of the VNF.
  • the sending module 43 is configured to send a URL corresponding to the VM image file of the stored VNF or the VM image file of the VNF to the candidate VIM, notify the NS directory to join the NSD, and send an NSD loading success notification to the first network entity. Message.
  • the sending module 43 may send the stored VM image file or the URL corresponding to the VM image file to the corresponding VIM. Then, the sending module 43 sends a notification message to the NS directory to notify the NS directory to join the NSD, and sends an NSD loading success notification message to the first network entity to complete the NSD loading process. If the sending module 43 sends the URL corresponding to the VM image file to the VIM, after the VIM receives the URL, the corresponding VM image file may be downloaded from the address corresponding to the URL.
  • the NFVO provided in this embodiment is in the NSD loading process, after selecting the corresponding VIM for the VNF according to the restriction conditions in the NSD and the VNFD, the VM image file of the VNF or the VM image file of the VNF is sent to the selected VIM.
  • the URL therefore, does not send the VNF's VM image file to an unrelated VIM, saving VIM capacity and not generating additional send operations.
  • the NFVO provided in this embodiment only improves the NSD loading process.
  • the default NFVO has saved the VM image file of the VNF or the URL corresponding to the VM image file, but the VNF VM image file or the VM image file corresponds to the VM image file.
  • the URL can be sent to NFVO by any other means before the NSD loading process.
  • An optional way is that during the VNF loading process, NFVO saves the URL of the VM image file or VM image file of the VNF.
  • the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when deploying the VNF, and then stores the stored VNF by the NFVO according to the restrictions in the NSF and the VNF directory in the VNFD in the NSD loading process.
  • the URL corresponding to the VM image file or the VM image file of the VNF is sent to the candidate VIM, and then the NSD loading process is ended, which avoids sending the VM image file of the VNF to the unrelated VIM, thereby saving the network transmission resource and the VIM during the loading process. Storage space and avoid the operations required to send VM image files to unrelated VIMs.
  • FIG. 5 is a schematic structural diagram of Embodiment 2 of the NFVO according to the embodiment of the present invention. As shown in FIG. 5, the NFVO of the present embodiment further includes: a storage module 44.
  • the receiving module 41 is configured to receive the NSD before receiving the NSD sent by the first network entity.
  • the NFVO provided in this embodiment improves the existing VNF loading process, and is executed before the NSF loading of the NFVO in the embodiment shown in FIG. 4, and is used to save in the NFVO during the loading process of the VNF.
  • the receiving module 41 in the NFVO receives the VNF package sent by the first network entity, triggering the VNF loading process, where the first network entity is a trigger end of the NSD loading, and the first network entity is usually an OSS, that is, an operator.
  • the operation administrator manually triggers the NSD loading.
  • the first network entity may also be other authorized third-party entities, such as a third-party network service provider.
  • the sending module 43 is configured to notify the VNF directory to join the VNFD in the VNF package.
  • the sending module 43 needs to send the VNFD in the VNF package to the VNF directory, and notify the VNF directory to join the VNFD in the VNF package.
  • the storage module 44 is configured to store a VM image file of the VNF in the VNF package or a URL corresponding to the VM image file of the VNF.
  • the NFVO cannot know the VIM corresponding to the VNF. Therefore, if the NFVO needs to send the VNF VM image file to the VIM at this time, the NFVO may need to provide multiple VIMs in order to ensure the efficiency of the VNF instantiation process. Send the VM image file of the VNF in the VNF package. But this will create additional operations and may send the VM image file to an unrelated VIM. Therefore, the storage module 44 is set in the NFVO. After the receiving module 41 receives the VNF package, the storage module 44 stores the VM image file of the VNF in the VNF package or the URL corresponding to the VM image file of the VNF.
  • the URL corresponding to the VM image file of the stored VNF or the VM image file of the VNF will be sent to the VIM after the NFVO determines the VIM corresponding to the VNF, thereby avoiding unnecessary operations and avoiding the VNF.
  • the VM image file is sent to an unrelated VIM.
  • the sending module 43 is further configured to send a VNF package loading success notification message to the first network entity.
  • the sending module 43 can implement the first network.
  • the body sends a VNF package loading success notification message to complete the VNF loading process.
  • the NFVO provided in this embodiment does not send the URL corresponding to the VM image file of the VNF or the VM image file of the VNF to the VIM in the VNF loading process, thereby avoiding sending the VM image file of the VNF to the unrelated VIM. , saves network transmission resources and VIM storage space during loading, and avoids the operations required to send VM image files to unrelated VIMs.
  • the processing module 42 is further configured to check, before the storage module 44 stores the VM image file of the VNF in the VNF package or the URL corresponding to the VM image file of the VNF.
  • the storage module 44 specifically configured to store a VM image file of the VNF in the VNF package if the VNF package includes a VM image file of the VNF package; if the VNF package includes a VNF
  • the URL corresponding to the VM image file stores the URL corresponding to the VM image file of the VNF in the VNF package.
  • the VNF package received by the receiving module 41 may include a VM image file of the VNF, and may also include a URL corresponding to the VM image file of the VNF. Therefore, after the receiving module 41 receives the VNF package, the processing module 42 needs to check the received VNF package. If the VNF package includes the VNF image file, the storage module 44 stores the VNF image file. If the VNF package includes a URL corresponding to the image file of the VNF, the storage module 44 stores the URL corresponding to the image file of the VNF.
  • the NFVO in the VNF loading process, the NFVO first needs to receive the URL corresponding to the VM image file including the VNF, and then to multiple The VIM sends the URL, but does not notify the VIM to download the VM image file corresponding to the URL.
  • the NFVO In the NSD loading process, after determining the VIM corresponding to the VNF according to the restrictions in the NSD and the VNFD, the NFVO notifies the corresponding VIM to download the VM image file corresponding to the URL of the VM image file of the VNF.
  • NFVO also sends a URL file to multiple VIMs, but the process of downloading the VM image file by VIM is still in the NSD loading process, and is performed only after the VIM corresponding to the VNF is determined. . Since the URL file occupies a small amount of storage space, this implementation can also prevent the excessive VM image file from being sent to the irrelevant VIM, thus saving the storage space of the VIM.
  • the receiving module 41 is configured to receive the NSD sent by the first network entity
  • the processing module 42 is configured to select, according to the limiting condition in the NSD and the limiting condition in the VNFD in the VNF directory, a VIM is configured to allocate a virtual resource candidate VIM to the VNF
  • the sending module 43 is configured to notify the candidate VIM to download the VM image file according to the URL corresponding to the VM image file; notify the NS directory to join the NSD;
  • the network entity sends an NSD loading success notification message.
  • the receiving module 41 receives the NSD sent by the first network entity, triggering the NSD loading process, where the first network entity is the trigger end of the NSD loading.
  • the first network entity is usually an OSS, that is, the operator's operation administrator manually triggers the NSD loading.
  • the first network entity may also be another authorized third-party entity, such as a third-party network service provider.
  • the processing module 42 selects according to the restriction condition in the NSD received by the receiving module 41 and the restriction condition in the VNFD read from the VNF directory.
  • the candidate VIM for assigning virtual resources to the VNF when deploying the VNF is.
  • the sending module 43 notifies the candidate VIM to download the VM image file according to the URL corresponding to the VM image file; and notifies the NS directory to join the NSD; and sends an NSD loading success notification message to the first network entity to complete the NSD loading.
  • the NFVO provided in this implementation only improves the NSD loading process.
  • the default NFVO has sent the URL corresponding to the VM image file of the VNF to the VIM, but the URL corresponding to the VNF VM image file may be in the NSD. It is sent to VIM by any other means before the loading process.
  • An optional way is that during the VNF loading process, NFVO sends the URL corresponding to the VM image file of the VNF to the VIM.
  • the following provides a specific implementation manner of the URL corresponding to the VM image file of the VNF sent by the NFVO to the VIM during the VNF loading process.
  • This implementation improves the VNF loading process.
  • the receiving module 41 receives the VNF package sent by the first network entity.
  • the sending module 43 then notifies the VNF directory to join the VNFD in the VNF package; and sends the URL corresponding to the VM image file of the VNF in the VNF package to at least one VIM; finally sends the VNF program to the first network entity.
  • the packet loading success notification message ends the VNF loading process.
  • the URL corresponding to the VM image file that needs to include the VNF in the VNF package received by the receiving module 41 is included in the VNF package.
  • the sending module 43 can send the URL corresponding to the VM image file of the VNF to all possible VIMs, that is, all VIMs connected to the NFVO. In the NSD loading process, it is ensured that all possible VIMs have a URL corresponding to the VM image file of the VNF.
  • the processing module 42 is further configured to verify that the VNF directory is added to the VNFD in the VNF package before the sending module 43 notifies the VNF directory.
  • the form and certificate in the VNFD verifies the authenticity and reliability of the VNFD; the sending module 43 is specifically configured to: if the processing module 42 checks for the presence of necessary elements in the VNF package, or if the processing module 42 uses the VNF program The form and certificate in the VNFD in the package verifies that the VNFD is authentic and reliable, and then notifies the VNF directory to join the VNFD in the VNF package.
  • the VNF package needs to be verified before the NFVO notifies the VNF directory to join the NVFD of the NVF package.
  • the processing module 42 needs to verify the VNF package first.
  • the processing module 42 verifies the VNF package, including at least one of the following steps: the processing module 42 checks if the necessary elements in the VNF package are present, and the processing module 42 uses the form and certificate in the VNFD in the VNF package. Verify the authenticity and reliability of the VNFD. If the verification of the VNF package by the processing module 42 is passed, the sending module 43 notifies the VNF directory to join the VNFD in the VNF package. The NFVO then proceeds to the subsequent VNF loading process.
  • the processing module 42 is further configured to select, according to the restriction condition in the NSD and the limitation condition in the VNFD in the VNF directory, to allocate a virtual resource to the VNF when deploying the VNF.
  • the processing module 42 verifies the NSD, including at least one of the following steps: the processing module 42 checks whether a VNF package of the VNF in the NS described by the NSD exists, and the processing module 42 Checking whether the necessary elements in the NSD are present, the processing module 42 checks if there is an external interface in the VNFD that describes the need to provide the NS.
  • the processing module 42 is specifically configured to check the NSD The existence of the VNF package of the VNF in the described NS, checking the existence of necessary elements in the NSD, checking the external interface required to provide the NS in the VNFD, and selecting the virtual resource that can be allocated to the VNF when the VNF is deployed.
  • NSD The existence of the VNF package of the VNF in the described NS
  • checking the existence of necessary elements in the NSD checking the external interface required to provide the NS in the VNFD
  • the processing module 42 needs to verify the NSD.
  • the processing module 42 verifies the NSD, including at least one of the following steps: the processing module 42 checks whether a VNF package of the VNF in the NS described by the NSD exists, and the processing module 42 checks whether a necessary element in the NSD exists.
  • the processing module 42 checks if there is an external interface in the VNFD that describes the need to provide the NS.
  • the processing module 42 checks the VNF package presence of the VNF in the NS described by the NSD, checks for the presence of necessary elements in the NSD, and checks that the VNFD has an external interface required to describe the NS, the processing module 42 selects A candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed.
  • the processing module 42 selects a restriction condition in the NSD according to the candidate VIM that can allocate a virtual resource to the VNF when deploying the VNF, and a restriction condition in the VNFD in the VNF directory, specifically
  • the restriction in the NSD includes at least one of the following: a limitation of a deployment location of the VNF in the NS described by the NSD, an identifier of the VIM corresponding to the NS deployment location described by the NSD, and the NSD description NS Affinity description between VNFs included in the VNFD;
  • the constraint condition in the VNFD includes at least one of the following conditions: a constraint of deployment of the VNF or VNFC described by the VNFD, a VNF or VNFC deployment described by the VNFD
  • the description of the affinity between the VNFs included in the NS describes the placement strategy between the VNFs in the NS, for example, a certain VNF cannot be placed in the same VIM or the like.
  • the constraints of the deployment of the VNF or VNFC described by the VNFD represent, for example, the need for a particular hardware by the VNF or VNFC.
  • the affinity description between the VDUs included in the VNF described by the VNFD represents a placement strategy between each VFU in the VNF.
  • the sending module 43 is specifically configured to send the VM image file of the stored VNF to the candidate VIM through the VNF image management interface; or
  • the VNF image management interface sends the URL corresponding to the VM image file of the stored VNF to the candidate VIM.
  • the sending module 43 sends the VM image file of the stored VNF or the URL corresponding to the VM image file of the VNF.
  • the process of giving the candidate VIM needs to be performed for each VNF in the NS described by the NSD.
  • the sending module 43 notifies the NS directory to join the NSD. In order to complete the NSD loading process.
  • FIG. 6 is a flowchart of Embodiment 1 of a method for loading a virtual network according to an embodiment of the present invention. As shown in FIG. 6, the method in this embodiment includes:
  • Step S601 the NFVO receives the NSD sent by the first network entity.
  • Step S602 the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory.
  • the candidate VIM may be one or more.
  • a VNF may include multiple VNF components (VNFs, VNFs).
  • VNFs VNFs
  • VDUs corresponding to these VNFCs may need to be deployed across VIMs.
  • the URL corresponding to the file needs to be uploaded to a different VIM.
  • the VDUs corresponding to these VNFCs may also need to be deployed in a VIM management domain.
  • the URLs corresponding to the VM image files or VM image files of different VDUs need to be uploaded to the same VIM.
  • the candidate VIMs that can be allocated for each VNFC to allocate virtual resources may be one or more.
  • Step S603 the NFVO sends the URL corresponding to the stored VM image file of the VNF or the VM image file of the VNF to the candidate VIM.
  • Step S604 the NFVO notifies the NS directory to join the NSD.
  • Step S605 the NFVO sends an NSD loading success notification message to the first network entity.
  • This embodiment provides an improved NSD loading process for implementing the processing of the NFVO in the embodiment shown in FIG. 4, and the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 7 is a flowchart of Embodiment 2 of a virtual network loading method according to an embodiment of the present invention. The method of the embodiment is performed before the embodiment shown in FIG. 6. As shown in FIG. 7, the method of this embodiment includes:
  • Step S701 the NFVO receives the VNF package sent by the first network entity.
  • Step S702 the NFVO notifies the VNF directory to join the VNFD in the VNF package.
  • Step S703 the NFVO stores a URL corresponding to the VM image file of the VNF in the VNF package or the VM image file of the VNF.
  • Step S704 the NFVO sends a VNF package loading success notification message to the first network entity.
  • This embodiment provides an improved VNF loading process for implementing the processing of the NFVO in the embodiment shown in FIG. 5, and the implementation principle and technical effects are similar, and details are not described herein again.
  • the method further includes: the NFVO checking the VNF package; and the step S703 specifically: if the VNF package includes a VM image file of the VNF, The NFVO stores a VM image file of the VNF in the VNF package; if the VNF package includes a URL corresponding to the VM image file of the VNF, the NFVO stores a VM image file corresponding to the VNF in the VNF package. URL.
  • the method further includes: the NFVO verifying the VNF package, and the NFVO verifying the VNF package, including at least one of the following steps: the NFVO Checking whether the necessary elements in the VNF package exist, the NFVO verifying the authenticity and reliability of the VNFD using a form and a certificate in the VNFD in the VNF package; the step S702 specifically includes: if the NFVO Checking for the presence of necessary elements in the VNF package, or notifying the VNF if the NFVO uses the form and certificate in the VNFD in the VNF package to verify that the VNFD is authentic and reliable The directory is added to the VNFD in the VNF package.
  • the method further includes: the NFVO verifying the NSD, and the NFVO verifying the NSD, including at least one of the following steps: the NFVO checks the NSD Whether the VNF package of the VNF in the described NS exists, the NFVO checks whether the necessary elements in the NSD are present, and the NFVO checks whether the VNFD has an external interface required to provide the NS; Step S602 Specifically, if the NFVO checks for the presence of a VNF package of the VNF in the NS described by the NSD, the NFVO checks for the presence of a necessary element in the NSD, and the NFVO check includes that the VNFD is required to provide an NS. The external interface, the NFVO selection can allocate a candidate VIM of the virtual resource to the VNF when the VNF is deployed.
  • the restriction condition in the NSD includes at least one of the following conditions: a limitation of a deployment location of the VNF in the NS described by the NSD, and an NS deployment location corresponding to the NSD description.
  • the identification of the VIM, the NSD describes an affinity description between the VNFs included in the NS;
  • the constraint in the VNFD includes at least one of the following conditions: a constraint of deployment of the VNF or VNFC described by the VNFD And an affinity description between the VIM corresponding to the VNF or VNFC deployment location of the VNFD and the VDU included in the VNF described by the VNFD.
  • step S603 specifically includes: the NFVO sends a VM image file of the stored VNF to the candidate VIM through a VNF image management interface; or the NFVO is managed by the VNF image.
  • the interface sends the URL corresponding to the stored VM image file of the VNF to the candidate VIM.
  • the step S604 specifically includes: when the VM image files of all the VNFs included in the NS described by the NSD are stored to the corresponding VIM, the NFVO notifies the NS directory. Join the NSD.
  • FIG. 8 is a flowchart of Embodiment 3 of a method for loading a virtual network according to an embodiment of the present invention. As shown in FIG. 8 , the method in this embodiment includes:
  • Step S801 the NFVO receives the NSD sent by the first network entity.
  • Step S802 the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory.
  • Step S803 the NFVO notifies the candidate VIM to download a VM image file according to a URL corresponding to the VM image file.
  • Step S804 the NFVO notifies the NS directory to join the NSD.
  • Step S805 the NFVO sends an NSD loading success notification message to the first network entity.
  • This embodiment provides another improved NSD loading process.
  • FIG. 9 is a flowchart of Embodiment 4 of a virtual network loading method according to an embodiment of the present invention. The method in this embodiment is performed before the embodiment shown in FIG. 8. As shown in FIG. 9, the method in this embodiment includes:
  • Step S901 the NFVO receives the VNF package sent by the first network entity.
  • Step S902 the NFVO notifies the VNF directory to join the VNFD in the VNF package.
  • Step S903 the NFVO sends a URL corresponding to the VM image file of the VNF in the VNF package to at least one VIM.
  • Step S904 the NFVO sends a VNF package loading success notification message to the first network entity.
  • This embodiment provides another improved VNF loading procedure.
  • step 903 of the embodiment shown in FIG. 9 specifically includes: the NFVO sending a URL corresponding to the VM image file of the VNF in the VNF package to all VIMs connected to the NFVO.
  • the method further includes: the NFVO verifying the VNF package, and the NFVO verifying the VNF package, including at least one of the following steps: the NFVO Checking whether the necessary elements in the VNF package are present, the NFVO verifying the authenticity and reliability of the VNFD using a form and a certificate in the VNFD in the VNF package; the step S902 specifically includes: if the NFVO Checking for the presence of necessary elements in the VNF package, or notifying the VNF if the NFVO uses the form and certificate in the VNFD in the VNF package to verify that the VNFD is authentic and reliable The directory is added to the VNFD in the VNF package.
  • the method further includes: the NFVO verifying the NSD, and the NFVO authenticating the NSD includes at least one of the following steps: the NFVO checks the NSD Whether the VNF package of the VNF in the described NS exists, the NFVO checks whether the necessary elements in the NSD are present, and the NFVO checks whether the VNFD has an external interface required to provide the NS; the step S802 specifically includes : if the NFVO checks for the presence of a VNF package of the VNF in the NS described by the NSD, the NFVO checks for the presence of a necessary element in the NSD, and the NFVO checks that the VNFD has an externality required to provide the NS Interface, then the NFVO selection can A candidate VIM that allocates virtual resources to the VNF when the VNF is deployed.
  • the restriction condition in the NSD includes at least one of the following conditions: a limitation of a deployment location of the VNF in the NS described by the NSD, and an NS deployment location corresponding to the NSD description.
  • the identification of the VIM, the NSD describes an affinity description between the VNFs included in the NS;
  • the constraint in the VNFD includes at least one of the following conditions: a constraint of deployment of the VNF or VNFC described by the VNFD And an affinity description between the VIM corresponding to the VNF or VNFC deployment location of the VNFD and the VDU included in the VNF described by the VNFD.
  • the step S803 specifically includes: the NFVO notifying the candidate VIM to download the VM image file according to the URL corresponding to the VM image file through the VNF image management interface.
  • step S804 specifically includes: when the VM image files of all VNFs included in the NS described in the NSD are all sent to the corresponding candidate VIM, the NFVO notifies the NS The directory is added to the NSD.
  • FIG. 10 is a signaling flowchart of Embodiment 1 of a VNF loading method according to an embodiment of the present invention
  • FIG. 11 is a signaling flowchart of Embodiment 1 of an NSD loading method according to an embodiment of the present invention, and the VNF loading method shown in FIG. It is used in conjunction with the NSD loading method shown in FIG. 11.
  • the VNF loading shown in FIG. 10 is performed first. After all the VNFs in one NS are loaded, the NSD loading shown in FIG. 11 is performed.
  • step S1001 the transmitting end sends a VNF package to the NFVO.
  • the VNF package includes a VNFD, and a VM image file of the VNF, requesting the NFVO to load the VNFD in the VNF package.
  • step S1002 the NFVO processes the received VNFD, including but not limited to checking whether some necessary elements are present, and verifying the authenticity and reliability of the VNFD with the form and certificate in the VNFD.
  • step S1003 when the verification of the VNFD by the NFVO is passed, the NFVO sends the VNFD to the NFV directory, informing the VNF directory to join the VNFD.
  • step S1004 the NFVO stores the VM image file in the VNF package.
  • step S1005 the NFVO sends a VNF package loading success notification message to the transmitting end.
  • step S1101 the transmitting end transmits an NSD to the NFVO.
  • step S1102 the NFVO processes the received NSD, including but not limited to checking the VNF in the NS. Whether the VNF package exists, check if some necessary elements exist, and check if there is an external interface in the VNFD that describes the NS.
  • step S1103 the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when deploying the VNF according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory.
  • step S1104 the NFVO transmits the VM image file of the stored VNF to the candidate VIM.
  • step S1105 after receiving the VM image file of the VNF transmitted by the NFVO, the VIM sends a reception success confirmation message to the NFVO.
  • step S1106 when the NFVO determines that the VM image files of all the VNFs included in the NS described in the NSD are stored to the corresponding VIM, the NSD is sent to the NS directory.
  • step S1107 the NFVO sends an NSD loading success notification message to the transmitting end.
  • FIG. 12 is a signaling flowchart of Embodiment 2 of a VNF loading and loading method according to an embodiment of the present invention
  • FIG. 13 is a signaling flowchart of Embodiment 2 of an NSD loading and loading method according to an embodiment of the present invention, where the VNF is shown in FIG.
  • the loading method is used in conjunction with the NSD loading method shown in FIG. 13.
  • the VNF loading shown in FIG. 12 is performed first. After all the VNFs in one NS are loaded, the NSD loading shown in FIG. 13 is performed.
  • step S1201 the transmitting end sends a VNF package to the NFVO.
  • the VNF package includes a VNFD, and a URL corresponding to the VM image file of the VNF, requesting the NFVO to load the VNFD in the VNF package.
  • the NFVO processes the received VNFD, including but not limited to checking whether some necessary elements are present, and verifying the authenticity and reliability of the VNFD with the form and certificate in the VNFD.
  • step S1203 when the verification of the VNFD by the NFVO is passed, the NFVO sends the VNFD to the NFV directory, informing the VNF directory to join the VNFD.
  • step S1204 the NFVO stores the URL corresponding to the VM image file in the VNF package.
  • the NFVO sends a VNF package loading success notification message to the transmitting end.
  • step S1301 the transmitting end transmits an NSD to the NFVO.
  • step S1302 the NFVO processes the received NSD, including but not limited to checking whether the VNF package of the VNF in the NS exists, checking whether some necessary elements exist, and checking whether there is an external interface in the VNFD describing the NS.
  • step S1303 the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when the VNF is deployed according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory.
  • step S1304 the NFVO transmits the URL corresponding to the stored VM image file of the VNF to the candidate VIM.
  • step S1305 After receiving the URL corresponding to the VM image file of the VNF sent by the NFVO, the VIM downloads the corresponding VM image file according to the URL, and sends a reception success confirmation message to the NFVO.
  • step S1306 when the NFVO determines that the URL corresponding to the VM image file of all the VNFs included in the NS described in the NSD is stored to the corresponding VIM, the NSD is sent to the NS directory.
  • step S1307 the NFVO sends an NSD loading success notification message to the transmitting end.
  • FIG. 14 is a signaling flowchart of Embodiment 3 of a VNF loading and loading method according to an embodiment of the present invention
  • FIG. 15 is a signaling flowchart of Embodiment 3 of an NSD loading and loading method according to an embodiment of the present invention, where the VNF is shown in FIG.
  • the loading method is used in conjunction with the NSD loading method shown in FIG. 15.
  • the VNF loading shown in FIG. 14 is performed first. After all the VNFs in one NS are loaded, the NSD loading shown in FIG. 15 is performed.
  • step S1401 the transmitting end sends a VNF package to the NFVO.
  • the VNF package includes a VNFD, and a URL corresponding to the VM image file of the VNF, requesting the NFVO to load the VNFD in the VNF package.
  • step S1402 the NFVO processes the received VNFD, including but not limited to checking whether some necessary elements are present, and verifying the authenticity and reliability of the VNFD with the form and certificate in the VNFD.
  • step S1403 when the NFVO verifies the VNFD, the NFVO sends the VNFD to the NFV directory, informing the VNF directory to join the VNFD.
  • step S1404 the NFVO sends a URL corresponding to the VM image file in the VNF package to the plurality of VIMs, where the NFVO generally sends the URL to all possible VIMs.
  • step S1405 the NFVO sends a VNF package loading success notification message to the transmitting end.
  • step S1501 the transmitting end transmits an NSD to the NFVO.
  • step S1502 the NFVO processes the received NSD, including but not limited to checking whether the VNF package of the VNF in the NS exists, checking whether some necessary elements exist, and checking whether there is an external interface in the VNFD describing the NS.
  • step S1503 the NFVO selects a candidate VIM capable of allocating virtual resources to the VNF when deploying the VNF according to the restriction condition in the NSD and the restriction condition in the VNFD in the VNF directory.
  • step S1504 the NFVO sends a notification message to the candidate VIM to notify the candidate VIM to download the VM image file corresponding to the saved URL.
  • step S1505 after receiving the notification message of the VM corresponding to the download URL by the NFVO, the VIM downloads the corresponding VM image file according to the URL, and sends a reception success confirmation message to the NFVO.
  • step S1506 NFVO determines the NS in the NSD description. When the URL corresponding to the VM image file of all the VNFs is stored in the corresponding VIM, the NSD is sent to the NS directory.
  • step S1507 the NFVO sends an NSD loading success notification message to the transmitting end.
  • FIG. 16 is a schematic structural diagram of Embodiment 1 of a virtualization infrastructure manager according to an embodiment of the present invention. As shown in FIG. 16, the virtualization infrastructure manager of this embodiment includes:
  • the receiving module 161 is configured to receive a URL corresponding to the VM image file of the VNF sent by the NFVO.
  • the storage module 162 is configured to store a URL corresponding to the VM image file of the VNF.
  • the receiving module 161 is further configured to receive the download notification message sent by the NFVO, where the download notification message is used to instruct the VIM to download a URL image file corresponding to the VM image file of the VNF.
  • the processing module 163 is configured to download the VM image file according to the URL corresponding to the VM image file of the VNF, where the VIM is a candidate VIM that can allocate a virtual resource to the VNF corresponding to the VM image file when the VNF is deployed.
  • VIM is mainly responsible for infrastructure layer hardware resources, virtualization resource management, monitoring, and fault reporting in the NFV architecture, and provides a virtualized resource pool for upper-layer applications.
  • the VIM will receive the VM image file of the VNF sent by the NFVO or the URL corresponding to the VM image file during the VNF loading process.
  • the VIM receives the VM image file
  • the VM image file will be saved.
  • the VIM receives the URL corresponding to the VM image file
  • the VM image file is downloaded and saved according to the URL.
  • the VNF corresponding to the VM image file saved by the VIM may not be deployed on the VIM, so the VIM may save the unrelated VM image file.
  • the receiving module 161 when the receiving module 161 receives the URL corresponding to the VM image file of the VNF sent by the NFVO, the download of the VM image file is not triggered, but the storage module 163 stores the URL.
  • the processing module 163 downloads the corresponding VM image file according to the URL stored by the storage module 163.
  • the receiving module 161 receives the URL corresponding to the VM image file of the VNF sent by the NFVO in the VNF loading process, and the receiving module 161 receives the download notification message sent by the NFVO in the NSD loading process.
  • NFVO will describe the NS as NSD according to the restrictions in the NSF and the VNFD stored in the VNF directory.
  • Each VNF in the selection selects a corresponding deployment location, so that the download of the VM image file after the receiving module 161 receives the download notification message sent by the NFVO can prevent the VIM from downloading the unrelated VM image file. Since the URL corresponding to the VM image file of the VNF is only an address information, the storage space occupied by the VNF is very small.
  • the VIM receives the URL corresponding to the VM image file of the VNF sent by the NFVO, the VIM stores the URL and receives the NFVO transmission. After downloading the notification message, the VM image file is downloaded, which will save a lot of storage space.
  • FIG. 17 is a flowchart of Embodiment 5 of a method for loading a virtual network according to an embodiment of the present invention. As shown in FIG. 17, the method in this embodiment includes:
  • step S1701 the VIM receives the URL corresponding to the VM image file of the VNF sent by the NFVO.
  • Step S1702 The VIM stores a URL corresponding to the VM image file of the VNF.
  • Step S1703 The VIM receives the download notification message sent by the NFVO, and the download notification message is used to instruct the VIM to download a URL image file corresponding to the VM image file of the VNF.
  • step S1704 the VIM downloads the VM image file according to the URL corresponding to the VM image file of the VNF, and the VIM is a candidate VIM that can allocate a virtual resource to the VNF corresponding to the VM image file when the VNF is deployed.
  • the receiving module 41 in the embodiment of the present invention may correspond to the receiver of the NFVO, and may also correspond to the transceiver of the NFVO.
  • the transmitting module 43 may correspond to the transmitter of the NFVO or may correspond to the transceiver of the NFVO.
  • the processing module 42 may correspond to a processor of the NFVO, where the processor may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or implement an embodiment of the present invention. One or more integrated circuits.
  • the storage module 44 can correspond to the memory of the NFVO, the memory is used to store the instruction code, the processor calls the instruction code of the memory, and the receiving module 41, the transmitting module 43, and the storage module 44 in the embodiment of the present invention are controlled to perform the above operations.
  • the receiving module 161 in the embodiment of the present invention may correspond to the receiver of the VIM, and may also correspond to the transceiver of the VIM.
  • the processing module 163 may correspond to a processor of the VIM, where the processor may be a central processing unit (CPU) or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits implementing embodiments of the present invention.
  • the storage module 162 can correspond to the memory of the VIM, the memory is used to store the instruction code, the processor calls the instruction code of the memory, and the receiving module 161 and the storage module 162 in the embodiment of the present invention are controlled to perform the above operations.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Facsimiles In General (AREA)

Abstract

本发明实施例提供一种虚拟网络加载方法和装置，一种虚拟网络加载方法包括：NFVO接收第一网络实体发送的NSD；所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM；所述NFVO将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM；所述NFVO通知NS目录加入所述NSD；所述NFVO向所述第一网络实体发送NSD加载成功通知消息。本发明实施例提供的虚拟网络加载方法和装置，用于优化虚拟网络加载流程，节约加载过程中的网络传输资源和VIM中的存储空间。

Description

虚拟网络加载方法和装置 技术领域
本发明实施例涉及网络技术，尤其涉及一种虚拟网络加载方法和装置。
背景技术
2012年10月23日，13个电信行业的大型运营商发布了网络功能虚拟化(Network Function Virtualization，简称NFV)白皮书，宣布在欧洲电信标准化协会(European Telecommunications Standards Institute，简称ETSI)成立NFV工业标准组织(Industry Standard Group，简称ISG)。NFV ISG的发起成员包括美国电话电报公司(American Telephone&Telegraph，简称ATT)、德国电信(Deutsche Telekom，简称DT)、英国电信(British Telecom，简称BT)、西班牙电话公司(Telefonica)、法国电信(France Telecom，简称FT)等公司。目前全球已有近百家公司成为NFV ISG组织的成员。
运营商成立NFV ISG的目的是为了定义运营商网络功能虚拟化的需求和相关的技术报告，希望通过借鉴信息技术(Information Technology，简称IT)的虚拟化技术，在通用的高性能服务器、网络交换机和存储设备中实现部分网络功能。这需要网络功能以软件方式实现，并能在通用的服务器硬件上运行，可以根据需要进行迁移、实例化、部署在网络的不同位置，并且不需要安装新设备。各种类型的网络设备，如服务器、路由器、存储设备、交换机等，都可以通过NFV技术实现软硬件分离，它们可以部署在数据中心、网络节点或者用户家中。
概括起来，NFV有3个关键特性：将定义网络功能的软件从通用的高性能的硬件服务器、存储设备以及网络交换机中完全分离出来；软件和硬件组件的独立的模块化特征；基于通用硬件完全自动化地远程安装和管理软件设备。
NFV技术中，一个网络服务(Network Service，NS)实例由多个虚拟网络功能(Virtualization Network Function，VNF)实例组成。在NS实例中需 要新增一个VNF时，需要进行VNF的加载(On-boarding)。VNF On-boarding过程是指将VNF程序包(VNF Package)提交给网络功能虚拟化编排器(Network Functions Virtualization Orchestrator，NFVO)，使NFVO将VNF Package纳入虚拟化网络功能描述符(Virtualised Infrastructure Manager Descriptor，VNFD)目录中。VNF Package是VNF的档案文件，包括VNF的VNFD，虚拟机镜像(Virtual Machine image，VM image)文件，以及其它一些构件，如用来检查该档案文件的完整性和证明其有效性的构件。当VNF On-boarding过程进行完毕后，VM image文件会被上传到虚拟化基础设施管理器(Virtualised Infrastructure Manager，VIM)中，这样当NFVO收到VNF实例化请求后，即可直接读取VIM中的VM image文件，可以节省VNF实例化的时间。
但是由于在VNF架构中，一个操作的管理域可能存在多个VIM，而由于NFVO在实例化VNF时，执行资源分配的过程中才会为VNF中的每个虚拟化部署单元(Virtualization Deployment Unit，VDU)选择部署的位置，不同的部署位置将对应不同的VIM。因此在VNF On-boarding的过程中，VNF image文件会被上传到多个可能的VIM中，这样才能使VNF实例化后，可以在相应的VIM中读取VM image文件，从而节省VNF实例化的时间。
但是，由于VNF package的大小是吉比特(gigabyte)量级的，其中VM image文件占了大部分，在VNF On-boarding的过程中，将VM image文件上传到多个可能的VIM中，可能导致VM image文件被上传到不相关的VIM中，从而可能产生不必要的操作以及加载过程中的网络传输资源和VIM上存储空间的浪费。
发明内容
本发明实施例提供一种虚拟网络加载方法和装置，用于优化虚拟网络加载流程，节约加载过程中的网络传输资源和VIM中的存储资源。
第一方面提供一种网络功能虚拟化编排器，包括：
接收模块，用于接收第一网络实体发送的NSD；
处理模块，用于根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选 VIM；
发送模块，用于将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM；通知NS目录加入所述NSD；向所述第一网络实体发送NSD加载成功通知消息。
结合第一方面，在第一方面第一种可能的实现方式中，所述接收模块，还用于在接收第一网络实体发送的NSD之前，接收所述第一网络实体发送的VNF程序包；
所述发送模块，还用于通知所述VNF目录加入所述VNF程序包中的VNFD；
所述NFVO还包括：存储模块，用于存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL；
所述发送模块，还用于向所述第一网络实体发送VNF程序包加载成功通知消息。
结合第一方面第一种可能的实现方式，在第一方面第二种可能的实现方式中，所述处理模块，还用于在所述存储模块存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL之前，检查所述VNF程序包；
所述存储模块，具体用于若所述VNF程序包中包括VNF的VM镜像文件，则存储所述VNF程序包中的VNF的VM镜像文件；若所述VNF程序包中包括VNF的VM镜像文件对应的URL，则存储所述VNF程序包中的VNF的VM镜像文件对应的URL。
结合第一方面第一种或第二种可能的实现方式，在第一方面第三种可能的实现方式中，所述处理模块，还用于在所述发送模块通知所述VNF目录加入所述VNF程序包中的VNFD之前，验证所述VNF程序包，所述处理模块验证所述VNF程序包，包括如下步骤中的至少一项：所述处理模块检查所述VNF程序包中必要的元素是否存在、所述处理模块使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；
所述发送模块，具体用于若所述处理模块检查所述VNF程序包中必要的元素存在，或者若所述处理模块使用所述VNF程序包中的VNFD中 的表单和证书验证所述VNFD具有真实性和可靠性，则通知所述VNF目录加入所述VNF程序包中的VNFD。
结合第一方面至第一方面第三种可能的实现方式中任一种可能的实现方式，在第一方面第四种可能的实现方式中，所述处理模块，还用于在根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，验证所述NSD，所述处理模块验证所述NSD，包括如下步骤中的至少一项：所述处理模块检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述处理模块检查所述NSD中必要的元素是否存在、所述处理模块检查所述VNFD中是否有描述提供NS所需的外部接口；
所述处理模块，具体还用于若检查所述NSD描述的NS中的VNF的VNF程序包存在、检查所述NSD中必要的元素存在、检查所述VNFD中有描述提供NS所需的外部接口，则选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
结合第一方面至第一方面第四种可能的实现方式中任一种可能的实现方式，在第一方面第五种可能的实现方式中，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的VDU之间的亲和性描述。
结合第一方面至第一方面第五种可能的实现方式中任一种可能的实现方式，在第一方面第六种可能的实现方式中，所述发送模块，具体用于通过VNF镜像管理接口将存储的VNF的VM镜像文件发送给所述候选VIM；或者通过所述VNF镜像管理接口将存储的VNF的VM镜像文件对应的URL发送给所述候选VIM。
结合第一方面至第一方面第六种可能的实现方式中任一种可能的实现方式，在第一方面第七种可能的实现方式中，所述发送模块，具体用于当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都存储至 对应的VIM时，通知所述NS目录加入所述NSD。
第二方面提供一种网络功能虚拟化编排器，包括：
接收模块，用于接收第一网络实体发送的NSD；
处理模块，用于根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM；
发送模块，用于通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件；通知NS目录加入所述NSD；向所述第一网络实体发送NSD加载成功通知消息。
结合第二方面，在第二方面第一种可能的实现方式中，所述接收模块，还用于在接收第一网络实体发送的NSD之前，接收所述第一网络实体发送的VNF程序包；
所述发送模块，还用于通知所述VNF目录加入所述VNF程序包中的VNFD；将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM；向所述第一网络实体发送VNF程序包加载成功通知消息。
结合第二方面第一种可能的实现方式，在第二方面第二种可能的实现方式中，所述发送模块，具体用于将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给与所述NFVO连接的所有VIM。
结合第二方面第一种或第二种可能的实现方式，在第二方面第三种可能的实现方式中，所述处理模块，还用于在所述发送模块通知所述VNF目录加入所述VNF程序包中的VNFD之前，验证所述VNF程序包，所述处理模块验证所述VNF程序包，包括如下步骤中的至少一项：所述处理模块检查所述VNF程序包中必要的元素是否存在、所述处理模块使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；
所述发送模块，具体用于若所述处理模块检查所述VNF程序包中必要的元素存在，或者若所述处理模块使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则通知所述VNF目录加入所述VNF程序包中的VNFD。
结合第二方面至第二方面第三种可能的实现方式中任一种可能的实现方式，在第二方面第四种可能的实现方式中，所述处理模块，还用于在根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，验证所述NSD，所述处理模块验证所述NSD，包括如下步骤中的至少一项：所述处理模块检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述处理模块检查所述NSD中必要的元素是否存在、所述处理模块检查所述VNFD中是否有描述提供NS所需的外部接口；
所述处理模块，具体还用于若检查所述NSD描述的NS中的VNF的VNF程序包存在、检查所述NSD中必要的元素存在、检查所述VNFD中有描述提供NS所需的外部接口，则为所述NFVO选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
结合第二方面至第二方面第四种可能的实现方式中任一种可能的实现方式，在第二方面第五种可能的实现方式中，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的VDU之间的亲和性描述。
结合第二方面至第二方面第五种可能的实现方式中任一种可能的实现方式，在第二方面第六种可能的实现方式中，所述发送模块，具体用于通过VNF镜像管理接口通知所述候VIM根据所述VM镜像文件对应的URL下载VM镜像文件。
结合第二方面至第二方面第六种可能的实现方式中任一种可能的实现方式，在第二方面第七种可能的实现方式中，所述发送模块，具体用于当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都发送至对应的候选VIM时，通知所述NS目录加入所述NSD。
第三方面提供一种虚拟网络加载方法，包括：
NFVO接收第一网络实体发送的NSD；
所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM；
所述NFVO将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM；
所述NFVO通知NS目录加入所述NSD；
所述NFVO向所述第一网络实体发送NSD加载成功通知消息。
结合第三方面，在第三方面第一种可能的实现方式中，所述NFVO接收第一网络实体发送的NSD之前，还包括：
所述NFVO接收所述第一网络实体发送的VNF程序包；
所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD；
所述NFVO存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL；
所述NFVO向所述第一网络实体发送VNF程序包加载成功通知消息。
结合第三方面第一种可能的实现方式，在第三方面第二种可能的实现方式中，所述NFVO存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL之前，还包括：
所述NFVO检查所述VNF程序包；
所述NFVO存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL，包括：
若所述VNF程序包中包括VNF的VM镜像文件，则所述NFVO存储所述VNF程序包中的VNF的VM镜像文件；若所述VNF程序包中包括VNF的VM镜像文件对应的URL，则所述NFVO存储所述VNF程序包中的VNF的VM镜像文件对应的URL。
结合第三方面第一种或第二种可能的实现方式，在第三方面第三种可能的实现方式中，所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD之前，还包括：
所述NFVO验证所述VNF程序包，所述NFVO验证所述VNF程序包，包括如下步骤中的至少一项：所述NFVO检查所述VNF程序包中必要的元素是否存在、所述NFVO使用所述VNF程序包中的VNFD中的表 单和证书验证所述VNFD的真实性和可靠性；
所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD，包括：
若所述NFVO检查所述VNF程序包中必要的元素存在，或者若所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
结合第三方面至第三方面第三种可能的实现方式中任一种可能的实现方式，在第三方面第四种可能的实现方式中，所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，还包括：
所述NFVO验证所述NSD，所述NFVO验证所述NSD，包括如下步骤中的至少一项：所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述NFVO检查所述NSD中必要的元素是否存在、所述NFVO检查所述VNFD中是否有描述提供NS所需的外部接口；
所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM，包括：
若所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包存在、所述NFVO检查所述NSD中必要的元素存在、所述NFVO检查所述VNFD中有描述提供NS所需的外部接口，则所述NFVO选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
结合第三方面至第三方面第四种可能的实现方式中任一种可能的实现方式，在第三方面第五种可能的实现方式中，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的VDU之间的亲和性描述。
结合第三方面至第三方面第五四种可能的实现方式中任一种可能的实现方式，在第三方面第六种可能的实现方式中，所述NFVO将存储的VM镜像文件或VM镜像文件对应的URL发送给所述候选VIM，包括：
所述NFVO通过VNF镜像管理接口将存储的VNF的VM镜像文件发送给所述候选VIM；或者所述NFVO通过所述VNF镜像管理接口将存储的VNF的VM镜像文件对应的URL发送给所述候选VIM。
结合第三方面至第三方面第六种可能的实现方式中任一种可能的实现方式，在第三方面第七种可能的实现方式中，所述NFVO通知NS目录加入所述NSD，包括：
当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都存储至对应的VIM时，所述NFVO通知所述NS目录加入所述NSD。
第四方面提供一种虚拟网络加载方法，包括：
NFVO接收第一网络实体发送的NSD；
所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM；
所述NFVO通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件；
所述NFVO通知NS目录加入所述NSD；
所述NFVO向所述第一网络实体发送NSD加载成功通知消息。
结合第四方面，在第四方面第一种可能的实现方式中，所述NFVO接收第一网络实体发送的NSD之前，还包括：
所述NFVO接收所述第一网络实体发送的VNF程序包；
所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD；
所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM；
所述NFVO向所述第一网络实体发送VNF程序包加载成功通知消息。
结合第四方面第一种可能的实现方式，在第四方面第二种可能的实现方式中，所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM，包括：
所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给与所述NFVO连接的所有VIM。
结合第四方面第一种或第二种可能的实现方式，在第四方面第三种可能的实现方式中，所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD之前，还包括：
所述NFVO验证所述VNF程序包，所述NFVO验证所述VNF程序包，包括如下步骤中的至少一项：所述NFVO检查所述VNF程序包中必要的元素是否存在、所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；
所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD，包括：
若所述NFVO检查所述VNF程序包中必要的元素存在，或者若所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
结合第四方面至第四方面第三种可能的实现方式中任一种可能的实现方式，在第四方面第四种可能的实现方式中，所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，还包括：
所述NFVO验证所述NSD，所述NFVO验证所述NSD，包括如下步骤中的至少一项：所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述NFVO检查所述NSD中必要的元素是否存在、所述NFVO检查所述VNFD中是否有描述提供NS所需的外部接口；
所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM，包括：
若所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包存在、所述NFVO检查所述NSD中必要的元素存在、所述NFVO检查所述VNFD中有描述提供NS所需的外部接口，则所述NFVO选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
结合第四方面至第四方面第四种可能的实现方式中任一种可能的实现方式，在第四方面第五种可能的实现方式中，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的虚拟化部署单元VDU之间的亲和性描述。
结合第四方面至第四方面第五四种可能的实现方式中任一种可能的实现方式，在第四方面第六种可能的实现方式中，所述NFVO通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件，包括：
所述NFVO通过VNF镜像管理接口通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件。
结合第四方面至第四方面第六种可能的实现方式中任一种可能的实现方式，在第四方面第七种可能的实现方式中于，所述NFVO通知NS目录加入所述NSD，包括：
当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都发送至对应的候选VIM时，所述NFVO通知所述NS目录加入所述NSD。
第五方面提供一种虚拟化基础设施管理器，包括：
接收模块，用于接收NFVO发送的VNF的VM镜像文件对应的URL；
存储模块，用于存储所述VNF的VM镜像文件对应的URL；
所述接收模块，还用于接收所述NFVO发送的下载通知消息，所述下载通知消息用于指示所述VIM下载所述VNF的VM镜像文件对应的URL下载VM镜像文件；
处理模块，用于根据所述VNF的VM镜像文件对应的URL下载所述VM镜像文件，所述VIM为能够在部署VNF时给所述VM镜像文件对应的VNF分配虚拟资源的候选VIM。
第六方面提供一种虚拟网络加载方法，包括：
VIM接收NFVO发送的VNF的VM镜像文件对应的URL；
所述VIM存储所述VNF的VM镜像文件对应的URL；
所述VIM接收所述NFVO发送的下载通知消息，所述下载通知消息用于指示所述VIM下载所述VNF的VM镜像文件对应的URL下载VM镜像文件；
所述VIM根据所述VNF的VM镜像文件对应的URL下载所述VM镜像文件，所述VIM为能够在部署VNF时给所述VM镜像文件对应的VNF分配虚拟资源的候选VIM。
本发明实施例提供的虚拟网络加载方法和装置，通过在NSD加载流程中，由NFVO根据NSD及VNF目录中VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM，然后再将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM，接着结束NSD加载流程，避免了将VNF的VM镜像文件发送给无关的VIM，节约了加载过程中的网络传输资源和VIM的存储空间，并且避免了向无关的VIM发送VM镜像文件所需的操作。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为NFV MANO架构示意图；
图2为VNF加载的信令示意图；
图3为NSD加载的信令示意图；
图4为本发明实施例提供的NFVO实施例一的结构示意图；
图5为发明实施例提供的NFVO实施例二的结构示意图；
图6为本发明实施例提供的虚拟网络加载方法实施例一的流程图；
图7为本发明实施例提供的虚拟网络加载方法实施例二的流程图；
图8为本发明实施例提供的虚拟网络加载方法实施例三的流程图；
图9为本发明实施例提供的虚拟网络加载方法实施例四的流程图；
图10为本发明实施例提供的VNF加载加载方法实施例一的信令流程图；
图11为本发明实施例提供的NSD加载加载方法实施例一的信令流程图；
图12为本发明实施例提供的VNF加载加载方法实施例二的信令流程图；
图13为本发明实施例提供的NSD加载加载方法实施例二的信令流程图；
图14为本发明实施例提供的VNF加载加载方法实施例三的信令流程图；
图15为本发明实施例提供的NSD加载加载方法实施例三的信令流程图；
图16为本发明实施例提供的虚拟化基础设施管理器实施例一的结构示意图；
图17为本发明实施例提供的虚拟网络加载方法实施例五的流程图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
图1为NFV MANO架构示意图，如图1所示，NFV MANO架构11包括：网络功能虚拟化编排器(Network Function Virtualization Orchestrator，简称NFVO)101、虚拟网络功能管理器(Virtualized Network Function Manager，简称VNFM)102、虚拟化基础设施管理器(Infrastructure Manager，简称VIM)103，以及NS目录(Catalog)104、VNF目录(Catalog)105、NFV实例(Instances)106、NFV基础设备(NFV Infrastructure，简称NFVI)资 源(Resources)107四个数据库。
其中，NFVO 101实现网络服务描述符(Network Service Descriptor，简称NSD)，虚拟网络功能转发图(Virtualized Network Function Forwarding Graph，简称VNFFG)的管理及处理，NS生命周期的管理，和VNFM 102配合实现VNF 12的生命周期管理和资源的全局视图功能。VNFM 102实现VNF 12的生命周期管理，包括虚拟化网络功能描述符(Virtualized Network Function Descriptor，简称VNFD)的管理及处理，VNF实例的初始化，VNF12的扩容/缩容，VNF实例的终止。支持接收NFVO 101下发的容量调整(scaling)策略，实现VNF 12的容量调整。VIM 103主要负责基础设施层硬件资源，虚拟化资源的管理，监控和故障上报，面向上层应用提供虚拟化资源池。NS Catalog 104包括所有已经加载的NSD。VNF Catalog 105包括所有已经加载的VNF程序包(VNF Packages)。NFV Instances 106包括所有正在运行的NS实例和VNF实例。NFVI Resources 107包括所有NFVI资源状态，可用的/已预留的/已分配的NFVI资源。
VNF 12对应于传统非虚拟化网络中的物理网络功能(Physical Network Function，简称PNF)，如虚拟化的演进的分组核心网(Evolved Packet Core，简称EPC)节点(移动管理实体(Mobile Management Entity，简称MME)、服务网关(Service Gateway，简称SGW)，分组数据网关(Packet Data Network Gateway，简称PGW)等)。网络功能的功能性行为和状态与虚拟化与否无关，NFV希望VNF 12和PNF拥有相同的功能性行为和外部接口。VNF 12可以由多个更低级别的组件来组成，因此，一个VNF 12可以部署在多个虚拟机(Virtualized Machine，VM)上，每个VM主机(host)一个VNF组件；VNF 12也可以部署在一个VM上。
运营支撑系统(Operations Support Systems，简称OSS)/业务支撑系统(Business Support Systems，简称BSS)13指运营商现有的OSS/BSS。网元管理系统(Element Management System，EMS)/网络管理系统Network Management System，NMS)14针对VNF 12执行传统的故障管理，配置管理，计费管理，性能管理，安全管理(Fault Management，Configuration Management，Accounting Management，Performance Management，Security Management，简称FCAPS)功能。
NFVI 15由硬件资源和虚拟资源以及虚拟层组成。从VNF的角度来说，虚拟化层和硬件资源看起来是一个能够提供所需虚拟资源的实体。
在整个NFV MANO架构中，VNFM 102和VIM 103的数量可能为多个，VNFM 102管理和维护多个VNF，VIM 103管理和维护部署VNF所需要的虚拟资源。
NFVO 101与OSS/BSS 13通过Os-Ma-Nfvo接口连接，NFVO 101与VNFM 102通过Or-Vnfm接口连接，VNFM 102与VIM 103通过Vi-Vnfm接口连接，NFVO 101与VIM 103通过Or-Vi接口连接，VNFM 102与VNF 12通过Ve-Vnfm-vnf接口连接，VNFM102与EMS/NMS 14通过Ve-Vnfm-em接口连接，VIM 103与NFVI 15通过Nf-Vi接口连接。NFVO 101与NS Catalog104、VNF Catalog 105、VNF Instances 106、NFV Resources 107四个数据库连接，VNFM 102与数据库VNF Catalog 105连接。
在NFV中，当需要新增一个VNF时，需要进行VNF的加载过程，图2为VNF加载的信令示意图，如图2所示，在NFV MANO架构中，需要进行VNF加载时，首先在步骤S201中，需要由发送端向NFVO发送VNF程序包，VNF程序包中包括VNFD，以及VNF的VM镜像文件，请求NFVO加载该VNF程序包中的VNFD，其中，这里的发送端通常是OSS，也就是运营商的操作管理员手动触发VNF加载；发送端也可以是其它被授权的第三方实体，如第三方网络服务提供商。在步骤S202中，NFVO处理接收到的VNFD，包括但不限于检查一些必要的元素是否存在，用VNFD中的表单和证书验证所述VNFD的真实性和可靠性。在步骤S203中，当NFVO对VNFD的验证通过，NFVO向NFV目录发送该VNFD，通知VNF目录加入该VNFD。在步骤S204中，NFVO将VNF程序包中的VM镜像文件发送给VIM。在步骤S205中，当VIM确认接收到NFVO发送的VM镜像文件，存储该VM镜像文件，并且VIM向NFVO发送接收成功确认消息。在步骤S206中，NFVO当接收到VIM发送的接收成功确认消息后，将向发送端发送VNF程序包加载成功通知消息。
在NFV MANO架构中，一个NFVO管理域中可能存在多个VIM，在VNF加载的过程中，NFVO无法获知加载的VNF在实例化过程中与哪个VIM对应，因此NFVO可能需要向多个VIM(一般为NFVO所有可能发送的VIM) 发送VNF程序包中的VM镜像文件。这样当NFVO接收到该VNF的实例化请求后，由于VNF的VM镜像文件已经存储于VIM中，这样将节省VNF实例化的时间。但是在VNF实例化的过程中，VNF的每个VDU都只有一个确定的部署位置，也就对于VNF的每个VDU，都只有一个对应的VIM，这样当VNF实例化后，可能有些VIM中存储的该VNF的VM镜像文件不会被使用。由于VNF程序包的大小是gigabyte量级的，其中VM镜像文件占了大部分，部分VIM存储不会被使用的VM镜像文件将浪费大量的存储空间，同时NFVO向多个VIM发送VM镜像文件也将产生一些不必要的操作。
为了解决上述问题，考虑到NFV中的NSD加载过程。NSD加载过程和VNFD加载过程是两个独立的流程，并且原则上先完成NS中包括的VNF的VNF加载过程，然后才进行NSD的加载过程。因此，可以将VNF程序包中的VM镜像文件的发送过程在NSD加载过程中再进行，并且提前选择可能为部署VNF分配虚拟资源的VIM，从而可以避免NFVO向无关的VIM发送VM镜像文件的过程，从而解决上述问题。
图3为NSD加载的信令示意图，如图3所示，在NFV MANO架构中，需要进行NSD加载时，首先在步骤S301中，需要由发送端向NFVO发送NSD，其中，这里的发送端通常是OSS，也就是运营商的操作管理员手动触发NSD加载；发送端也可以是其它被授权的第三方实体，如第三方网络服务提供商。在步骤S302中，NFVO处理接收到的NSD，包括但不限于检查NS中的VNF的VNF程序包(VNF package)是否存在，检查一些必要的元素是否存在，检查VNFD中是否有描述提供NS所需的外部接口。在步骤S303中，当NFVO对NSD的验证通过，NFVO向NS目录发送该NSD。在步骤S304中，NFVO若已经向NS目录发送NSD，则向发送端发送NSD加载成功通知消息。
图4为本发明实施例提供的NFVO实施例一的结构示意图，如图4所示，本实施例的NFVO包括：
接收模块41，用于接收第一网络实体发送的NSD。
具体地，本实施例提供的NFVO对现有的NSD加载流程进行了改进，首先，接收模块41接收第一网络实体发送的NSD，触发NSD加载流程，这里的第一网络实体为NSD加载的发送端，第一网络实体通常是 OSS，也就是运营商的操作管理员手动触发NSD加载，第一网络实体也可以是其它被授权的第三方实体，如第三方网络服务提供商。
处理模块42，用于根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
具体地，本实施例为NSD的加载流程，由于一个NS由多个VNF组成，因此在NSD加载之前，需要进行NS中各VNF的加载过程，当NS中的各VNF完成加载后，才能进行NSD的加载。因此，在本实施例中接收模块41接收第一网络实体发送的NSD之前，本实施例提供的NFVO还应进行了NS中各VNF的加载流程。在VNF的加载流程中，NFVO会接收到VNF程序包中的VNF的VM镜像文件，或者，NFVO接收到的可以仅为VNF的VM镜像文件对应的统一资源定位符(Uniform Resource Locator，URL)，VNF的VM镜像文件对应的URL表示了VNF的VM镜像文件对应的下载地址。NFVO可以将VNF加载流程中接收到的VNF的镜像文件或VNF的VM镜像文件对应的URL存储起来。在NFVO进行本实施例中的NSD加载过程时，当接收模块41接收到NSD，处理模块42将根据NSD中的限制条件，以及从VNF目录中读取的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
一个VNF可能包含多个VNF部件(VNFC，VNF Component)，根据VNF部署需求和限制条件，这些VNFC对应的VDU可能需要跨VIM部署，此时不同VDU对应的VM镜像文件或VM镜像文件对应的URL需要上载到不同的VIM。这些VNFC对应的VDU也可能需要部署在一个VIM管理域内部，此时不同VDU对应的VM镜像文件或VM镜像文件对应的URL需要上载到相同的VIM上。不管是哪种条件下，为每个VNFC选择的可以分配虚拟资源的候选VIM可以是一个，也可以是多个。
其中，NSD中的限制条件和VNFD中的限制条件限定了NS所要部署的位置、VNF所要部署的位置、NS中各VNF部署位置的关系等，NFVO根据上述各种位置关系最终确定VNF的部署位置，即VNF对应的VIM。当NFVO确定了VNF对应的VIM后，即为VNF的VM镜像文件或VNF的VM镜像文件对应的URL选择对应的VIM。
发送模块43，用于将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM；通知NS目录加入所述NSD；向所述第一网络实体发送NSD加载成功通知消息。
具体地，在处理模块42确定了候选VIM后，发送模块43即可向相应的VIM发送存储的VM镜像文件或VM镜像文件对应的URL。随后发送模块43还向NS目录发送通知消息，通知NS目录加入该NSD，向第一网络实体发送NSD加载成功通知消息，完成NSD加载流程。若发送模块43向VIM发送的是VM镜像文件对应的URL，则当VIM接收到该URL后，从该URL对应的地址下载相应的VM镜像文件即可。
由于本实施例提供的NFVO是在NSD加载流程中，根据NSD和VNFD中的限制条件为VNF选择了对应的VIM后，才向选定的VIM发送VNF的VM镜像文件或VNF的VM镜像文件对应的URL，因此不会将VNF的VM镜像文件发送给无关的VIM，从而节约了VIM的容量并且不会产生额外的发送操作。
需要说明的是，本实施例提供的NFVO只是对NSD加载流程进行了改进，其中默认NFVO已经保存有VNF的VM镜像文件或VM镜像文件对应的URL，但VNF的VM镜像文件或VM镜像文件对应的URL可以是在NSD加载流程之前通过其他任一种方式发送至NFVO的。其中一种可选的方式是在VNF加载的过程中，NFVO保存VNF的VM镜像文件或VM镜像文件对应的URL。
本实施例提供的NFVO，通过在NSD加载流程中，由NFVO根据NSD及VNF目录中VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM，然后再将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM，接着结束NSD加载流程，避免了将VNF的VM镜像文件发送给无关的VIM，节约了加载过程中的网络传输资源和VIM的存储空间，并且避免了向无关的VIM发送VM镜像文件所需的操作。
图5为发明实施例提供的NFVO实施例二的结构示意图，如图5所示，本实施例的NFVO在图4的基础上，还包括：存储模块44。
接收模块41，用于在接收第一网络实体发送的NSD之前，接收所述 第一网络实体发送的VNF程序包。
具体地，本实施例提供的NFVO对现有的VNF加载流程进行了改进，用于在图4所示实施例的NFVO进行NSD加载之前执行，用于在VNF的加载过程中，在NFVO中保存VNF的VM镜像文件或VM镜像文件对应的URL。
首先，NFVO中的接收模块41接收第一网络实体发送的VNF程序包，触发VNF加载流程，这里的第一网络实体为NSD加载的触发端，第一网络实体通常是OSS，也就是运营商的操作管理员手动触发NSD加载，第一网络实体也可以是其它被授权的第三方实体，如第三方网络服务提供商。
发送模块43，用于通知VNF目录加入所述VNF程序包中的VNFD。
具体地，当接收模块41接收到VNF程序包后，发送模块43需要向VNF目录发送VNF程序包中的VNFD，通知VNF目录加入该VNF程序包中的VNFD。
存储模块44，用于存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL。
具体地，在VNF加载过程中，NFVO还无法获知VNF对应的VIM，因此若此时NFVO需要向VIM发送VNF的VM镜像文件，则NFVO为了保证VNF实例化过程的效率，可能需要向多个VIM发送VNF程序包中VNF的VM镜像文件。但这样就会产生额外的操作并且可能将VM镜像文件发送至不相关的VIM。因此，在NFVO中设置存储模块44，当接收模块41接收到VNF程序包后，存储模块44即存储VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL。被存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL将在NSD加载过程中，当NFVO确定了VNF对应的VIM后，再向VIM发送，从而可以避免多余的操作以及避免将VNF的VM镜像文件发送至不相关的VIM。
发送模块43，还用于向第一网络实体发送VNF程序包加载成功通知消息。
具体地，存储模块44存储了VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL后，发送模块43即可向第一网络实 体发送VNF程序包加载成功通知消息，完成VNF加载流程。
本实施例提供的NFVO，通过在VNF加载流程中，NFVO存储VNF的VM镜像文件或VNF的VM镜像文件对应的URL，而不向VIM发送，避免了将VNF的VM镜像文件发送给无关的VIM，节约了加载过程中的网络传输资源和VIM的存储空间，并且避免了向无关的VIM发送VM镜像文件所需的操作。
进一步地，在图5所示实施例中，处理模块42，还用于在存储模块44存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL之前，检查所述VNF程序包；存储模块44，具体用于若所述VNF程序包中包括VNF的VM镜像文件，则存储所述VNF程序包中的VNF的VM镜像文件；若所述VNF程序包中包括VNF的VM镜像文件对应的URL，则存储所述VNF程序包中的VNF的VM镜像文件对应的URL。
具体地，由于接收模块41接收的VNF程序包中可能包括VNF的VM镜像文件，也可能包括VNF的VM镜像文件对应的URL。因此当接收模块41接收到VNF程序包后，处理模块42需要检查接收到的VNF程序包，若VNF程序包中包括VNF的镜像文件，则存储模块44存储VNF的镜像文件。若VNF程序包中包括VNF的镜像文件对应的URL，则存储模块44存储VNF的镜像文件对应的URL。
下面提供图4所示实施例提供的NFVO的另一种实现方式，在这种实现方式中，NFVO在VNF加载流程中，首先需要接收到包括VNF的VM镜像文件对应的URL，然后向多个VIM发送该URL，但并不通知VIM下载该URL对应的VM镜像文件。NFVO在NSD加载流程中，当根据NSD及VNFD中的限制条件确定了VNF对应的VIM后，再通知相应的VIM下载VNF的VM镜像文件的URL对应的VM镜像文件。虽然这种实现方式中，在VNF加载过程中，NFVO也会向多个VIM发送URL文件，但是VIM下载VM镜像文件的过程还是在NSD加载流程中，当确定了VNF对应的VIM后才进行的。由于URL文件占用的存储空间极小，因此这种实现方式同样可以避免过大的VM镜像文件被发送至无关的VIM，从而节约了VIM的存储空间。
在这种实现方式中，接收模块41，用于接收第一网络实体发送的NSD；处理模块42，用于根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM；发送模块43，用于通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件；通知NS目录加入所述NSD；向所述第一网络实体发送NSD加载成功通知消息。
具体地，这种实现方式同样对现有的NSD加载流程进行了改进，首先，接收模块41接收第一网络实体发送的NSD，触发NSD加载流程，这里的第一网络实体为NSD加载的触发端，第一网络实体通常是OSS，也就是运营商的操作管理员手动触发NSD加载，第一网络实体也可以是其它被授权的第三方实体，如第三方网络服务提供商。然后，若NFVO已发送给VIM了VNF的VM镜像文件对应的URL，则处理模块42根据接收模块41接收到的NSD中的限制条件和从VNF目录中读取的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM为。最后发送模块43才通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件；并通知NS目录加入所述NSD；向所述第一网络实体发送NSD加载成功通知消息，完成NSD加载流程。需要说明的是，本实现方式提供的NFVO只是对NSD加载流程进行了改进，其中默认NFVO已经向VIM发送了VNF的VM镜像文件对应的URL，但VNF的VM镜像文件对应的URL可以是在NSD加载流程之前通过其他任一种方式发送至VIM的。其中一种可选的方式是在VNF加载的过程中，NFVO向VIM发送了VNF的VM镜像文件对应的URL。
以下提供在VNF加载的过程中，NFVO向VIM发送了VNF的VM镜像文件对应的URL的具体实现方式。这种实现方式对VNF加载流程进行了改进，首先，接收模块41，接收第一网络实体发送的VNF程序包。然后发送模块43，通知VNF目录加入所述VNF程序包中的VNFD；并且将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM；最后向第一网络实体发送VNF程序包加载成功通知消息，结束VNF加载流程。在这个VNF加载流程中，接收模块41接收到的VNF程序包中需要包括VNF的VM镜像文件对应的URL，若VNF程序包中包括 的是VNF的VM镜像文件，则不能采用此流程。发送模块43可以将VNF的VM镜像文件对应的URL发送给所有可能的VIM，即与NFVO连接的所有VIM。这样在NSD加载流程中，可以保证所有可能的VIM中都有VNF的VM镜像文件对应的URL。
进一步地，在图5所示实施例或上述另一种VNF加载流程中，处理模块42，还用于在发送模块43通知所述VNF目录加入所述VNF程序包中的VNFD之前，验证所述VNF程序包，处理模块42验证所述VNF程序包，包括如下步骤中的至少一项：处理模块42检查所述VNF程序包中必要的元素是否存在、处理模块42使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；发送模块43，具体用于若处理模块42检查所述VNF程序包中必要的元素存在，或者若处理模块42使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则通知所述VNF目录加入所述VNF程序包中的VNFD。
具体地，在图2所示的现有VNF加载过程中，在NFVO通知VNF目录加入NVF程序包的NVFD之前，还需要验证VNF程序包。图5所示实施例提供的NFVO中同样如此，在接收模块41接收到第一网络实体发送的VNF程序包后，处理模块42需要先验证该VNF程序包。处理模块42验证VNF程序包，包括如下步骤中的至少一项：处理模块42检查所述VNF程序包中必要的元素是否存在、处理模块42使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性。若处理模块42对VNF程序包的验证通过，则发送模块43再通知所述VNF目录加入所述VNF程序包中的VNFD。然后NFVO再进行后续VNF加载流程。
进一步地，在图4所示实施例中，处理模块42，还用于在根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，验证所述NSD，处理模块42验证所述NSD，包括如下步骤中的至少一项：处理模块42检查所述NSD描述的NS中的VNF的VNF程序包是否存在、处理模块42检查所述NSD中必要的元素是否存在、处理模块42检查所述VNFD中是否有描述提供NS所需的外部接口。处理模块42，具体还用于若检查所述NSD 描述的NS中的VNF的VNF程序包存在、检查所述NSD中必要的元素存在、检查所述VNFD中有描述提供NS所需的外部接口，则选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
具体地，在图3所示的现有NSD加载过程中，在NFVO接收到NSD之后，需要验证该NSD。在图4所示实施例中，当接收模块41接收到第一网络实体发送的NSD之后，与图3所示的NSD加载过程类似地，处理模块42需要验证所述NSD。处理模块42验证所述NSD，包括如下步骤中的至少一项：处理模块42检查所述NSD描述的NS中的VNF的VNF程序包是否存在、处理模块42检查所述NSD中必要的元素是否存在、处理模块42检查所述VNFD中是否有描述提供NS所需的外部接口。当处理模块42检查所述NSD描述的NS中的VNF的VNF程序包存在、检查所述NSD中必要的元素存在、检查所述VNFD中有描述提供NS所需的外部接口，则处理模块42选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
进一步地，图4所示实施例中，处理模块42选择能够在部署VNF时给VNF分配虚拟资源的候选VIM所依据的所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，具体为：所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的VDU之间的亲和性描述。
其中，所述NSD描述NS中包括的VNF之间的亲和性描述表示NS中各VNF之间的放置策略，例如某两个VNF不能放置于同一个VIM等。所述VNFD描述的VNF或VNFC的部署的约束条件例如表示VNF或VNFC对某种特殊硬件的需求。所述VNFD描述的VNF中包括的VDU之间的亲和性描述表示VNF中的各VFU之间的放置策略。
进一步地，图4所示实施例中，发送模块43具体用于通过VNF镜像管理接口将存储的VNF的VM镜像文件发送给所述候选VIM；或者通过 所述VNF镜像管理接口将存储的VNF的VM镜像文件对应的URL发送给所述候选VIM。
进一步地，图4所示实施例中，由于是NSD加载流程，而NSD描述的NS可能包括多个VNF，因此发送模块43将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM的过程，需要对NSD描述的NS中的每个VNF都进行。当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都存储至对应的VIM时，发送模块43才通知NS目录加入所述NSD。从而才能完成NSD加载流程。
图6为本发明实施例提供的虚拟网络加载方法实施例一的流程图，如图6所示，本实施例的方法包括：
步骤S601，NFVO接收第一网络实体发送的NSD。
步骤S602，所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。其中，候选VIM可以是一个或多个。
具体是指，一个VNF可能包含多个VNF部件(VNFC，VNF Component)，根据VNF部署需求和限制条件，这些VNFC对应的VDU可能需要跨VIM部署，此时不同VDU对应的VM镜像文件或VM镜像文件对应的URL需要上载到不同的VIM。这些VNFC对应的VDU也可能需要部署在一个VIM管理域内部，此时不同VDU对应的VM镜像文件或VM镜像文件对应的URL需要上载到相同的VIM上。不管是哪种条件下，为每个VNFC选择的可以分配虚拟资源的候选VIM可以是一个，也可以是多个。
步骤S603，所述NFVO将存储的VNF的VM镜像文件或VNF的VM镜像文件对应的URL发送给所述候选VIM。
步骤S604，所述NFVO通知NS目录加入所述NSD。
步骤S605，所述NFVO向所述第一网络实体发送NSD加载成功通知消息。
本实施例提供了一种改进的NSD加载流程，用于实现图4所示实施例的NFVO的处理，其实现原理和技术效果类似，此处不再赘述。
图7为本发明实施例提供的虚拟网络加载方法实施例二的流程图，本 实施例的方法在图6所示实施例之前执行，如图7所示，本实施例的方法包括：
步骤S701，NFVO接收所述第一网络实体发送的VNF程序包。
步骤S702，所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
步骤S703，所述NFVO存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL。
步骤S704，所述NFVO向所述第一网络实体发送VNF程序包加载成功通知消息。
本实施例提供了一种改进的VNF加载流程，用于实现图5所示实施例的NFVO的处理，其实现原理和技术效果类似，此处不再赘述。
进一步地，在图7所示实施例的步骤S703之前，还包括：所述NFVO检查所述VNF程序包；步骤S703具体包括：若所述VNF程序包中包括VNF的VM镜像文件，则所述NFVO存储所述VNF程序包中的VNF的VM镜像文件；若所述VNF程序包中包括VNF的VM镜像文件对应的URL，则所述NFVO存储所述VNF程序包中的VNF的VM镜像文件对应的URL。
进一步地，在图7所示实施例的步骤S702之前，还包括：所述NFVO验证所述VNF程序包，所述NFVO验证所述VNF程序包，包括如下步骤中的至少一项：所述NFVO检查所述VNF程序包中必要的元素是否存在、所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；步骤S702具体包括：若所述NFVO检查所述VNF程序包中必要的元素存在，或者若所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
进一步地，在图6所示实施例的步骤S602之前，还包括：所述NFVO验证所述NSD，所述NFVO验证所述NSD，包括如下步骤中的至少一项：所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述NFVO检查所述NSD中必要的元素是否存在、所述NFVO检查所述VNFD中是否有描述提供NS所需的外部接口；步骤S602 具体包括：若所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包存在、所述NFVO检查所述NSD中必要的元素存在、所述NFVO检查所述VNFD中有描述提供NS所需的外部接口，则所述NFVO选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
进一步地，在图6所示实施例中，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的VDU之间的亲和性描述。
进一步地，在图6所示实施例中，步骤S603具体包括：所述NFVO通过VNF镜像管理接口将存储的VNF的VM镜像文件发送给所述候选VIM；或者所述NFVO通过所述VNF镜像管理接口将存储的VNF的VM镜像文件对应的URL发送给所述候选VIM。
进一步地，在图6所示实施例中，步骤S604具体包括：当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都存储至对应的VIM时，所述NFVO通知所述NS目录加入所述NSD。
图8为本发明实施例提供的虚拟网络加载方法实施例三的流程图，如图8所示，本实施例的方法包括：
步骤S801，NFVO接收第一网络实体发送的NSD。
步骤S802，所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
步骤S803，所述NFVO通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件。
步骤S804，所述NFVO通知NS目录加入所述NSD。
步骤S805，所述NFVO向所述第一网络实体发送NSD加载成功通知消息。
本实施例提供了另一种改进的NSD加载流程。
图9为本发明实施例提供的虚拟网络加载方法实施例四的流程图，本实施例的方法在图8所示实施例之前执行，如图9所示，本实施例的方法包括：
步骤S901，NFVO接收所述第一网络实体发送的VNF程序包。
步骤S902，所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
步骤S903，所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM。
步骤S904，所述NFVO向所述第一网络实体发送VNF程序包加载成功通知消息。
本实施例提供了另一种改进的VNF加载流程。
进一步地，在图9所示实施例的步骤903具体包括：所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给与所述NFVO连接的所有VIM。
进一步地，在图9所示实施例的步骤S902之前，还包括：所述NFVO验证所述VNF程序包，所述NFVO验证所述VNF程序包，包括如下步骤中的至少一项：所述NFVO检查所述VNF程序包中必要的元素是否存在、所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；步骤S902具体包括：若所述NFVO检查所述VNF程序包中必要的元素存在，或者若所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
进一步地，在图8所示实施例的步骤S802之前，还包括：所述NFVO验证所述NSD，所述NFVO验证所述NSD，包括如下步骤中的至少一项：所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述NFVO检查所述NSD中必要的元素是否存在、所述NFVO检查所述VNFD中是否有描述提供NS所需的外部接口；步骤S802具体包括：若所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包存在、所述NFVO检查所述NSD中必要的元素存在、所述NFVO检查所述VNFD中有描述提供NS所需的外部接口，则所述NFVO选择能够 在部署VNF时给VNF分配虚拟资源的候选VIM。
进一步地，在图8所示实施例中，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的VDU之间的亲和性描述。
进一步地，在图8所示实施例中，步骤S803具体包括：所述NFVO通过VNF镜像管理接口通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件。
进一步地，在图8所示实施例中，步骤S804具体包括：当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都发送至对应的候选VIM时，所述NFVO通知所述NS目录加入所述NSD。
图10为本发明实施例提供的VNF加载方法实施例一的信令流程图，图11为本发明实施例提供的NSD加载方法实施例一的信令流程图，图10所示的VNF加载方法和图11所示的NSD加载方法配合使用，一般地，先进行图10所示的VNF加载，当一个NS中的所有VNF都加载完成后，再进行图11所示的NSD加载。
在图10中，首先，在步骤S1001中，发送端向NFVO发送VNF程序包，VNF程序包中包括VNFD，以及VNF的VM镜像文件，请求NFVO加载该VNF程序包中的VNFD。在步骤S1002中，NFVO处理接收到的VNFD，包括但不限于检查一些必要的元素是否存在，用VNFD中的表单和证书验证所述VNFD的真实性和可靠性。在步骤S1003中，当NFVO对VNFD的验证通过，NFVO向NFV目录发送该VNFD，通知VNF目录加入该VNFD。在步骤S1004中，NFVO存储VNF程序包中的VM镜像文件。在步骤S1005中，NFVO向发送端发送VNF程序包加载成功通知消息。
在图11中，首先在步骤S1101中，发送端向NFVO发送NSD。在步骤S1102中，NFVO处理接收到的NSD，包括但不限于检查NS中的VNF 的VNF程序包是否存在，检查一些必要的元素是否存在，检查VNFD中是否有描述提供NS所需的外部接口。在步骤S1103中，NFVO根据NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。在步骤S1104中，NFVO将存储的VNF的VM镜像文件发送给候选VIM。在步骤S1105中，当VIM接收到NFVO发送的VNF的VM镜像文件后，向NFVO发送接收成功确认消息。在步骤S1106中，NFVO确定NSD描述的NS中包括的所有的VNF的VM镜像文件都存储至对应的VIM时，向NS目录发送该NSD。在步骤S1107中，NFVO向发送端发送NSD加载成功通知消息。
图12为本发明实施例提供的VNF加载加载方法实施例二的信令流程图，图13为本发明实施例提供的NSD加载加载方法实施例二的信令流程图，图12所示的VNF加载方法和图13所示的NSD加载方法配合使用，一般地，先进行图12所示的VNF加载，当一个NS中的所有VNF都加载完成后，再进行图13所示的NSD加载。
在图12中，首先，在步骤S1201中，发送端向NFVO发送VNF程序包，VNF程序包中包括VNFD，以及VNF的VM镜像文件对应的URL，请求NFVO加载该VNF程序包中的VNFD。在步骤S1202中，NFVO处理接收到的VNFD，包括但不限于检查一些必要的元素是否存在，用VNFD中的表单和证书验证所述VNFD的真实性和可靠性。在步骤S1203中，当NFVO对VNFD的验证通过，NFVO向NFV目录发送该VNFD，通知VNF目录加入该VNFD。在步骤S1204中，NFVO存储VNF程序包中的VM镜像文件对应的URL。在步骤S1205中，NFVO向发送端发送VNF程序包加载成功通知消息。
在图13中，首先在步骤S1301中，发送端向NFVO发送NSD。在步骤S1302中，NFVO处理接收到的NSD，包括但不限于检查NS中的VNF的VNF程序包是否存在，检查一些必要的元素是否存在，检查VNFD中是否有描述提供NS所需的外部接口。在步骤S1303中，NFVO根据NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。在步骤S1304中，NFVO将存储的VNF的VM镜像文件对应的URL发送给候选VIM。在步骤S1305 中，当VIM接收到NFVO发送的VNF的VM镜像文件对应的URL后，根据该URL下载相应的VM镜像文件，并向NFVO发送接收成功确认消息。在步骤S1306中，NFVO确定NSD描述的NS中包括的所有的VNF的VM镜像文件对应的URL都存储至对应的VIM时，向NS目录发送该NSD。在步骤S1307中，NFVO向发送端发送NSD加载成功通知消息。
图14为本发明实施例提供的VNF加载加载方法实施例三的信令流程图，图15为本发明实施例提供的NSD加载加载方法实施例三的信令流程图，图14所示的VNF加载方法和图15所示的NSD加载方法配合使用，一般地，先进行图14所示的VNF加载，当一个NS中的所有VNF都加载完成后，再进行图15所示的NSD加载。
在图14中，首先，在步骤S1401中，发送端向NFVO发送VNF程序包，VNF程序包中包括VNFD，以及VNF的VM镜像文件对应的URL，请求NFVO加载该VNF程序包中的VNFD。在步骤S1402中，NFVO处理接收到的VNFD，包括但不限于检查一些必要的元素是否存在，用VNFD中的表单和证书验证所述VNFD的真实性和可靠性。在步骤S1403中，当NFVO对VNFD的验证通过，NFVO向NFV目录发送该VNFD，通知VNF目录加入该VNFD。在步骤S1404中，NFVO向多个VIM发送VNF程序包中的VM镜像文件对应的URL，在这里，NFVO一般是向所有可能的VIM发送该URL。在步骤S1405中，NFVO向发送端发送VNF程序包加载成功通知消息。
在图15中，首先在步骤S1501中，发送端向NFVO发送NSD。在步骤S1502中，NFVO处理接收到的NSD，包括但不限于检查NS中的VNF的VNF程序包是否存在，检查一些必要的元素是否存在，检查VNFD中是否有描述提供NS所需的外部接口。在步骤S1503中，NFVO根据NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。在步骤S1504中，NFVO向候选VIM发送通知消息，通知候选VIM下载已保存的URL对应的VM镜像文件。在步骤S1505中，当VIM接收到NFVO发送下载URL对应的VM的通知消息后，根据该URL下载相应的VM镜像文件，并向NFVO发送接收成功确认消息。在步骤S1506中，NFVO确定NSD描述的NS中 包括的所有的VNF的VM镜像文件对应的URL都存储至对应的VIM时，向NS目录发送该NSD。在步骤S1507中，NFVO向发送端发送NSD加载成功通知消息。
图16为本发明实施例提供的虚拟化基础设施管理器实施例一的结构示意图，如图16所示，本实施例的虚拟化基础设施管理器包括：
接收模块161，用于接收NFVO发送的VNF的VM镜像文件对应的URL。
存储模块162，用于存储所述VNF的VM镜像文件对应的URL。
接收模块161，还用于接收所述NFVO发送的下载通知消息，所述下载通知消息用于指示所述VIM下载所述VNF的VM镜像文件对应的URL下载VM镜像文件。
处理模块163，用于根据所述VNF的VM镜像文件对应的URL下载所述VM镜像文件，所述VIM为能够在部署VNF时给所述VM镜像文件对应的VNF分配虚拟资源的候选VIM。
具体地，VIM在NFV架构中主要负责基础设施层硬件资源，虚拟化资源的管理，监控和故障上报，面向上层应用提供虚拟化资源池。为了节约VNF实例化过程的时间，VIM会在VNF加载过程中接收到NFVO发送的VNF的VM镜像文件或者VM镜像文件对应的URL，当VIM接收到VM镜像文件时将保存该VM镜像文件，当VIM接收到VM镜像文件对应的URL时，将根据该URL下载并保存该VM镜像文件。但是在VNF实例化的过程中，VIM保存的VM镜像文件对应的VNF不一定会部署在该VIM上，因此VIM可能会保存不相关的VM镜像文件。
本实施例提供的VIM，当接收模块161接收到NFVO发送的VNF的VM镜像文件对应的URL时，不触发VM镜像文件的下载，而是由存储模块163将该URL存储起来。当接收模块161接收到NFVO发送的下载通知消息后，处理模块163才根据存储模块163存储的URL下载对应的VM镜像文件。其中，接收模块161接收NFVO发送的VNF的VM镜像文件对应的URL发生在VNF加载过程中，接收模块161接收NFVO发送的下载通知消息发生在NSD加载过程中。在NSD加载过程中，NFVO会根据NSD以及VNF目录中存储的VNFD中的限制条件为NSD描述的NS 中的各VNF选择相应订的部署位置，因此在接收模块161接收到NFVO发送的下载通知消息后才进行VM镜像文件的下载可以避免VIM下载不相关的VM镜像文件。由于VNF的VM镜像文件对应的URL只是一个地址信息，其占用的存储空间非常小，VIM在接收到NFVO发送的VNF的VM镜像文件对应的URL时，存储该URL，并在接收到NFVO发送的下载通知消息后才进行VM镜像文件的下载，将节约大量的存储空间。
图17为本发明实施例提供的虚拟网络加载方法实施例五的流程图，如图17所示，本实施例的方法包括：
步骤S1701，VIM接收NFVO发送的VNF的VM镜像文件对应的URL。
步骤S1702，所述VIM存储所述VNF的VM镜像文件对应的URL。
步骤S1703，所述VIM接收所述NFVO发送的下载通知消息，所述下载通知消息用于指示所述VIM下载所述VNF的VM镜像文件对应的URL下载VM镜像文件。
步骤S1704，所述VIM根据所述VNF的VM镜像文件对应的URL下载所述VM镜像文件，所述VIM为能够在部署VNF时给所述VM镜像文件对应的VNF分配虚拟资源的候选VIM。
需要说明的是，本发明实施例中的接收模块41可以与NFVO的接收器对应，也可以对应NFVO的收发器。发送模块43可以与NFVO的发送器对应，也可以对应NFVO的收发器。处理模块42可以与NFVO的处理器对应，这里处理器可以是一个中央处理器(Central Processing Unit，CPU)，或者是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者完成实施本发明实施例的一个或多个集成电路。存储模块44可以与NFVO的存储器对应，存储器用于存储指令代码，处理器调用存储器的指令代码，控制本发明实施例中的接收模块41、发送模块43和存储模块44执行上述操作。
需要说明的是，本发明实施例中的接收模块161可以与VIM的接收器对应，也可以对应VIM的收发器。处理模块163可以与VIM的处理器对应，这里处理器可以是一个中央处理器(Central Processing Unit，CPU)，或者是特定集成电路(Application Specific Integrated Circuit， ASIC)，或者完成实施本发明实施例的一个或多个集成电路。存储模块162可以与VIM的存储器对应，存储器用于存储指令代码，处理器调用存储器的指令代码，控制本发明实施例中的接收模块161和存储模块162执行上述操作。
本领域普通技术人员可以理解：实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储介质包括：ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (34)

  1. 一种网络功能虚拟化编排器，其特征在于，包括：
    接收模块，用于接收第一网络实体发送的网络服务描述符NSD；
    处理模块，用于根据所述NSD中的限制条件和虚拟网络功能VNF目录中的虚拟网络功能描述符VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选虚拟化基础设施管理器VIM；
    发送模块，用于将存储的VNF的虚拟机VM镜像文件或VNF的VM镜像文件对应的统一资源定位符URL发送给所述候选VIM；通知网络服务NS目录加入所述NSD；向所述第一网络实体发送NSD加载成功通知消息。
  2. 根据权利要求1所述的网络功能虚拟化编排器，其特征在于，所述接收模块，还用于在接收第一网络实体发送的NSD之前，接收所述第一网络实体发送的VNF程序包；
    所述发送模块，还用于通知所述VNF目录加入所述VNF程序包中的VNFD；
    所述网络功能虚拟化编排器NFVO还包括：存储模块，用于存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL；
    所述发送模块，还用于向所述第一网络实体发送VNF程序包加载成功通知消息。
  3. 根据权利要求2所述的网络功能虚拟化编排器，其特征在于，所述处理模块，还用于在所述存储模块存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL之前，检查所述VNF程序包；
    所述存储模块，具体用于若所述VNF程序包中包括VNF的VM镜像文件，则存储所述VNF程序包中的VNF的VM镜像文件；若所述VNF程序包中包括VNF的VM镜像文件对应的URL，则存储所述VNF程序包中的VNF的VM镜像文件对应的URL。
  4. 根据权利要求2或3所述的网络功能虚拟化编排器，其特征在于，所述处理模块，还用于在所述发送模块通知所述VNF目录加入所述 VNF程序包中的VNFD之前，验证所述VNF程序包，所述处理模块验证所述VNF程序包，包括如下步骤中的至少一项：所述处理模块检查所述VNF程序包中必要的元素是否存在、所述处理模块使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；
    所述发送模块，具体用于若所述处理模块检查所述VNF程序包中必要的元素存在，或者若所述处理模块使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则通知所述VNF目录加入所述VNF程序包中的VNFD。
  5. 根据权利要求1～4任一项所述的网络功能虚拟化编排器，其特征在于，所述处理模块，还用于在根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，验证所述NSD，所述处理模块验证所述NSD，包括如下步骤中的至少一项：所述处理模块检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述处理模块检查所述NSD中必要的元素是否存在、所述处理模块检查所述VNFD中是否有描述提供NS所需的外部接口；
    所述处理模块，具体还用于若检查所述NSD描述的NS中的VNF的VNF程序包存在、检查所述NSD中必要的元素存在、检查所述VNFD中有描述提供NS所需的外部接口，则选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
  6. 根据权利要求1～5任一项所述的网络功能虚拟化编排器，其特征在于，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或虚拟化网络功能组件VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的虚拟化部署单元VDU之间的亲和性描述。
  7. 根据权利要求1～6任一项所述的网络功能虚拟化编排器，其特征在于，所述发送模块，具体用于通过VNF镜像管理接口将存储的VNF的 VM镜像文件发送给所述候选VIM；或者通过所述VNF镜像管理接口将存储的VNF的VM镜像文件对应的URL发送给所述候选VIM。
  8. 根据权利要求1～7任一项所述的网络功能虚拟化编排器，其特征在于，所述发送模块，具体用于当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都存储至对应的VIM时，通知所述NS目录加入所述NSD。
  9. 一种网络功能虚拟化编排器，其特征在于，包括：
    接收模块，用于接收第一网络实体发送的网络服务描述符NSD；
    处理模块，用于根据所述NSD中的限制条件和虚拟网络功能VNF目录中的虚拟网络功能描述符VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选虚拟化基础设施管理器VIM；
    发送模块，用于通知所述候选VIM根据虚拟机VM镜像文件对应的统一资源定位符URL下载VM镜像文件；通知网络服务NS目录加入所述NSD；向所述第一网络实体发送NSD加载成功通知消息。
  10. 根据权利要求9所述的网络功能虚拟化编排器，其特征在于，所述接收模块，还用于在接收第一网络实体发送的NSD之前，接收所述第一网络实体发送的VNF程序包；
    所述发送模块，还用于通知所述VNF目录加入所述VNF程序包中的VNFD；将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM；向所述第一网络实体发送VNF程序包加载成功通知消息。
  11. 根据权利要求10所述的网络功能虚拟化编排器，其特征在于，所述发送模块，具体用于将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给与所述网络功能虚拟化编排器NFVO连接的所有VIM。
  12. 根据权利要求10或11所述的网络功能虚拟化编排器，其特征在于，所述处理模块，还用于在所述发送模块通知所述VNF目录加入所述VNF程序包中的VNFD之前，验证所述VNF程序包，所述处理模块验证所述VNF程序包，包括如下步骤中的至少一项：所述处理模块检查所述VNF程序包中必要的元素是否存在、所述处理模块使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；
    所述发送模块，具体用于若所述处理模块检查所述VNF程序包中必要的元素存在，或者若所述处理模块使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则通知所述VNF目录加入所述VNF程序包中的VNFD。
  13. 根据权利要求9～12任一项所述的网络功能虚拟化编排器，其特征在于，所述处理模块，还用于在根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，验证所述NSD，所述处理模块验证所述NSD，包括如下步骤中的至少一项：所述处理模块检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述处理模块检查所述NSD中必要的元素是否存在、所述处理模块检查所述VNFD中是否有描述提供NS所需的外部接口；
    所述处理模块，具体还用于若检查所述NSD描述的NS中的VNF的VNF程序包存在、检查所述NSD中必要的元素存在、检查所述VNFD中有描述提供NS所需的外部接口，则为所述NFVO选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
  14. 根据权利要求9～13任一项所述的网络功能虚拟化编排器，其特征在于，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或虚拟化网络功能组件VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的虚拟化部署单元VDU之间的亲和性描述。
  15. 根据权利要求9～14任一项所述的网络功能虚拟化编排器，其特征在于，所述发送模块，具体用于通过VNF镜像管理接口通知所述候VIM根据所述VM镜像文件对应的URL下载VM镜像文件。
  16. 根据权利要求9～15任一项所述的网络功能虚拟化编排器，其特征在于，所述发送模块，具体用于当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都发送至对应的候选VIM时，通知所述NS目录加 入所述NSD。
  17. 一种虚拟网络加载方法，其特征在于，包括：
    网络功能虚拟化编排器NFVO接收第一网络实体发送的网络服务描述符NSD；
    所述NFVO根据所述NSD中的限制条件和虚拟网络功能VNF目录中的虚拟网络功能描述符VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选虚拟化基础设施管理器VIM；
    所述NFVO将存储的VNF的虚拟机VM镜像文件或VNF的VM镜像文件对应的统一资源定位符URL发送给所述候选VIM；
    所述NFVO通知网络服务NS目录加入所述NSD；
    所述NFVO向所述第一网络实体发送NSD加载成功通知消息。
  18. 根据权利要求17所述的方法，其特征在于，所述NFVO接收第一网络实体发送的NSD之前，还包括：
    所述NFVO接收所述第一网络实体发送的VNF程序包；
    所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD；
    所述NFVO存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL；
    所述NFVO向所述第一网络实体发送VNF程序包加载成功通知消息。
  19. 根据权利要求18所述的方法，其特征在于，所述NFVO存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL之前，还包括：
    所述NFVO检查所述VNF程序包；
    所述NFVO存储所述VNF程序包中的VNF的VM镜像文件或VNF的VM镜像文件对应的URL，包括：
    若所述VNF程序包中包括VNF的VM镜像文件，则所述NFVO存储所述VNF程序包中的VNF的VM镜像文件；若所述VNF程序包中包括VNF的VM镜像文件对应的URL，则所述NFVO存储所述VNF程序包中的VNF的VM镜像文件对应的URL。
  20. 根据权利要求18或19所述的方法，其特征在于，所述NFVO通 知所述VNF目录加入所述VNF程序包中的VNFD之前，还包括：
    所述NFVO验证所述VNF程序包，所述NFVO验证所述VNF程序包，包括如下步骤中的至少一项：所述NFVO检查所述VNF程序包中必要的元素是否存在、所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；
    所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD，包括：
    若所述NFVO检查所述VNF程序包中必要的元素存在，或者若所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
  21. 根据权利要求17～20任一项所述的方法，其特征在于，所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，还包括：
    所述NFVO验证所述NSD，所述NFVO验证所述NSD，包括如下步骤中的至少一项：所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述NFVO检查所述NSD中必要的元素是否存在、所述NFVO检查所述VNFD中是否有描述提供NS所需的外部接口；
    所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM，包括：
    若所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包存在、所述NFVO检查所述NSD中必要的元素存在、所述NFVO检查所述VNFD中有描述提供NS所需的外部接口，则所述NFVO选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
  22. 根据权利要求17～21任一项所述的方法，其特征在于，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中 的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或虚拟化网络功能组件VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的虚拟化部署单元VDU之间的亲和性描述。
  23. 根据权利要求17～22任一项所述的方法，其特征在于，所述NFVO将存储的VM镜像文件或VM镜像文件对应的URL发送给所述候选VIM，包括：
    所述NFVO通过VNF镜像管理接口将存储的VNF的VM镜像文件发送给所述候选VIM；或者所述NFVO通过所述VNF镜像管理接口将存储的VNF的VM镜像文件对应的URL发送给所述候选VIM。
  24. 根据权利要求17～23任一项所述的方法，其特征在于，所述NFVO通知NS目录加入所述NSD，包括：
    当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都存储至对应的VIM时，所述NFVO通知所述NS目录加入所述NSD。
  25. 一种虚拟网络加载方法，其特征在于，包括：
    网络功能虚拟化编排器NFVO接收第一网络实体发送的网络服务描述符NSD；
    所述NFVO根据所述NSD中的限制条件和虚拟网络功能VNF目录中的虚拟网络功能描述符VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选虚拟化基础设施管理器VIM；
    所述NFVO通知所述候选VIM根据虚拟机VM镜像文件对应的统一资源定位符URL下载VM镜像文件；
    所述NFVO通知网络服务NS目录加入所述NSD；
    所述NFVO向所述第一网络实体发送NSD加载成功通知消息。
  26. 根据权利要求25所述的方法，其特征在于，所述NFVO接收第一网络实体发送的NSD之前，还包括：
    所述NFVO接收所述第一网络实体发送的VNF程序包；
    所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD；
    所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM；
    所述NFVO向所述第一网络实体发送VNF程序包加载成功通知消息。
  27. 根据权利要求26所述的方法，其特征在于，所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给至少一个VIM，包括：
    所述NFVO将所述VNF程序包中的VNF的VM镜像文件对应的URL发送给与所述NFVO连接的所有VIM。
  28. 根据权利要求26或27所述的方法，其特征在于，所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD之前，还包括：
    所述NFVO验证所述VNF程序包，所述NFVO验证所述VNF程序包，包括如下步骤中的至少一项：所述NFVO检查所述VNF程序包中必要的元素是否存在、所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD的真实性和可靠性；
    所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD，包括：
    若所述NFVO检查所述VNF程序包中必要的元素存在，或者若所述NFVO使用所述VNF程序包中的VNFD中的表单和证书验证所述VNFD具有真实性和可靠性，则所述NFVO通知所述VNF目录加入所述VNF程序包中的VNFD。
  29. 根据权利要求25～28任一项所述的方法，其特征在于，所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM之前，还包括：
    所述NFVO验证所述NSD，所述NFVO验证所述NSD，包括如下步骤中的至少一项：所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包是否存在、所述NFVO检查所述NSD中必要的元素是否存在、所述NFVO检查所述VNFD中是否有描述提供NS所需的外部接口；
    所述NFVO根据所述NSD中的限制条件和VNF目录中的VNFD中的限制条件，选择能够在部署VNF时给VNF分配虚拟资源的候选VIM，包括：
    若所述NFVO检查所述NSD描述的NS中的VNF的VNF程序包存在、所述NFVO检查所述NSD中必要的元素存在、所述NFVO检查所述VNFD中有描述提供NS所需的外部接口，则所述NFVO选择能够在部署VNF时给VNF分配虚拟资源的候选VIM。
  30. 根据权利要求25～29任一项所述的方法，其特征在于，所述NSD中的限制条件包括如下条件中的至少一个：所述NSD描述的NS中VNF的部署位置的限制、所述NSD描述的NS部署位置对应的VIM的标识、所述NSD描述NS中包括的VNF之间的亲和性描述；所述VNFD中的限制条件包括如下条件中的至少一个：所述VNFD描述的VNF或虚拟化网络功能组件VNFC的部署的约束条件、所述VNFD描述的VNF或VNFC部署位置对应的VIM的标识、所述VNFD描述的VNF中包括的虚拟化部署单元VDU之间的亲和性描述。
  31. 根据权利要求25～30任一项所述的方法，其特征在于，所述NFVO通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件，包括：
    所述NFVO通过VNF镜像管理接口通知所述候选VIM根据所述VM镜像文件对应的URL下载VM镜像文件。
  32. 根据权利要求25～31任一项所述的方法，其特征在于，所述NFVO通知NS目录加入所述NSD，包括：
    当所述NSD描述的NS中包括的所有的VNF的VM镜像文件都发送至对应的候选VIM时，所述NFVO通知所述NS目录加入所述NSD。
  33. 一种虚拟化基础设施管理器，其特征在于，包括：
    接收模块，用于接收网络功能虚拟化编排器NFVO发送的虚拟网络功能VNF的虚拟机VM镜像文件对应的统一资源定位符URL；
    存储模块，用于存储所述VNF的VM镜像文件对应的URL；
    所述接收模块，还用于接收所述NFVO发送的下载通知消息，所述下载通知消息用于指示所述虚拟化基础设施管理器VIM下载所述VNF的VM镜像文件对应的URL下载VM镜像文件；
    处理模块，用于根据所述VNF的VM镜像文件对应的URL下载所述VM镜像文件，所述VIM为能够在部署VNF时给所述VM镜像文件对应 的VNF分配虚拟资源的候选VIM。
  34. 一种虚拟网络加载方法，其特征在于，包括：
    虚拟化基础设施管理器VIM接收网络功能虚拟化编排器NFVO发送的虚拟网络功能VNF的虚拟机VM镜像文件对应的统一资源定位符URL；
    所述VIM存储所述VNF的VM镜像文件对应的URL；
    所述VIM接收所述NFVO发送的下载通知消息，所述下载通知消息用于指示所述VIM下载所述VNF的VM镜像文件对应的URL下载VM镜像文件；
    所述VIM根据所述VNF的VM镜像文件对应的URL下载所述VM镜像文件，所述VIM为能够在部署VNF时给所述VM镜像文件对应的VNF分配虚拟资源的候选VIM。
PCT/CN2015/099070 2014-12-31 2015-12-25 虚拟网络加载方法和装置 WO2016107506A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410853745.2 2014-12-31
CN201410853745.2A CN105808316B (zh) 2014-12-31 2014-12-31 虚拟网络加载方法和装置

Publications (1)

Publication Number Publication Date
WO2016107506A1 true WO2016107506A1 (zh) 2016-07-07

Family

ID=56284261

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/099070 WO2016107506A1 (zh) 2014-12-31 2015-12-25 虚拟网络加载方法和装置

Country Status (2)

Country Link
CN (1) CN105808316B (zh)
WO (1) WO2016107506A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230623A (zh) * 2016-07-22 2016-12-14 中国联合网络通信集团有限公司 一种vim站点选择方法及装置
CN106385330A (zh) * 2016-09-07 2017-02-08 中国联合网络通信集团有限公司 一种网络功能虚拟化编排器的实现方法及装置
WO2018014356A1 (zh) * 2016-07-22 2018-01-25 华为技术有限公司 一种加载方法及装置
WO2018045540A1 (zh) * 2016-09-08 2018-03-15 华为技术有限公司 一种生命周期管理方法及管理单元
RU2769106C1 (ru) * 2018-09-18 2022-03-28 Зте Корпарейшн Способ, устройство и система для предоставления услуг, носитель данных и электронное устройство
US20230024067A1 (en) * 2020-03-18 2023-01-26 Huawei Technologies Co., Ltd. Vnf instantiation method and apparatus
US11870768B1 (en) 2020-04-10 2024-01-09 Cisco Technology, Inc. Certificate-based techniques to securely onboard a radio interface unit

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108011739B (zh) * 2016-10-31 2021-05-04 华为技术有限公司 一种虚拟网络的部署方法、装置及系统
CN108234174B (zh) * 2016-12-21 2020-04-21 华为技术有限公司 虚拟网络功能的管理方法和装置
US20180191607A1 (en) * 2016-12-29 2018-07-05 Juniper Networks, Inc. Network service application and customer-aware virtualized network function placement
CN106856441A (zh) * 2017-01-23 2017-06-16 北京市天元网络技术股份有限公司 Nfvo中的vim选择方法和装置
CN108809907B (zh) * 2017-05-04 2021-05-11 华为技术有限公司 一种证书请求消息发送方法、接收方法和装置
CN108881338B (zh) * 2017-05-10 2022-08-09 中兴通讯股份有限公司 网络功能虚拟化镜像文件升级的方法及装置
CN109413011B (zh) * 2017-08-18 2021-12-14 华为技术有限公司 公共服务资源申请方法、相关设备及系统
FR3071948A1 (fr) * 2017-09-29 2019-04-05 Orange Procede et dispositif de traitement d'une requete d'instanciation d'un service reseau.
CN110365508B (zh) * 2018-04-10 2022-05-31 中国移动通信有限公司研究院 虚拟网络功能实例化的方法和网络功能虚拟化编排器
FR3081582A1 (fr) * 2018-06-18 2019-11-29 Orange Procede d'installation d'une fonction reseau virtualisee
CN111416727B (zh) * 2019-01-07 2023-05-09 中国移动通信有限公司研究院 Vnf上载实例化方法及装置
CN110727498B (zh) * 2019-09-03 2023-04-07 中国联合网络通信集团有限公司 一种虚拟网络功能的管理方法、nfvo、区块链节点及mano网元
CN112463285A (zh) * 2019-09-06 2021-03-09 中国移动通信有限公司研究院 一种部署虚拟化的网络功能模块的方法及设备
CN112748981B (zh) * 2019-10-29 2024-03-26 华为技术有限公司 虚拟网络功能的软件镜像的处理方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130246731A1 (en) * 2012-03-15 2013-09-19 Michael Mihn-Jong Lee Distributed graph storage system
WO2014169870A1 (zh) * 2013-08-05 2014-10-23 中兴通讯股份有限公司 虚拟网元自动装载及虚拟机ip地址获取的方法与系统、存储介质
CN104243301A (zh) * 2013-06-08 2014-12-24 华为技术有限公司 一种生成业务路径的方法、设备及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015157896A1 (zh) * 2014-04-14 2015-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130246731A1 (en) * 2012-03-15 2013-09-19 Michael Mihn-Jong Lee Distributed graph storage system
CN104243301A (zh) * 2013-06-08 2014-12-24 华为技术有限公司 一种生成业务路径的方法、设备及系统
WO2014169870A1 (zh) * 2013-08-05 2014-10-23 中兴通讯股份有限公司 虚拟网元自动装载及虚拟机ip地址获取的方法与系统、存储介质

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106230623A (zh) * 2016-07-22 2016-12-14 中国联合网络通信集团有限公司 一种vim站点选择方法及装置
WO2018014356A1 (zh) * 2016-07-22 2018-01-25 华为技术有限公司 一种加载方法及装置
CN106230623B (zh) * 2016-07-22 2019-03-15 中国联合网络通信集团有限公司 一种vim站点选择方法及装置
CN106385330A (zh) * 2016-09-07 2017-02-08 中国联合网络通信集团有限公司 一种网络功能虚拟化编排器的实现方法及装置
CN106385330B (zh) * 2016-09-07 2019-10-11 中国联合网络通信集团有限公司 一种网络功能虚拟化编排器的实现方法及装置
WO2018045540A1 (zh) * 2016-09-08 2018-03-15 华为技术有限公司 一种生命周期管理方法及管理单元
RU2769106C1 (ru) * 2018-09-18 2022-03-28 Зте Корпарейшн Способ, устройство и система для предоставления услуг, носитель данных и электронное устройство
US20230024067A1 (en) * 2020-03-18 2023-01-26 Huawei Technologies Co., Ltd. Vnf instantiation method and apparatus
US11888696B2 (en) * 2020-03-18 2024-01-30 Huawei Technologies Co., Ltd. VNF instantiation method and apparatus
US11870768B1 (en) 2020-04-10 2024-01-09 Cisco Technology, Inc. Certificate-based techniques to securely onboard a radio interface unit

Also Published As

Publication number Publication date
CN105808316A (zh) 2016-07-27
CN105808316B (zh) 2019-04-23

Similar Documents

Publication Publication Date Title
WO2016107506A1 (zh) 虚拟网络加载方法和装置
US11586461B2 (en) Service creation and management
WO2016095121A1 (zh) 网络服务能力自动调整方法和系统
US10057127B2 (en) Processing method for service allocation and related apparatus
EP3170071B1 (en) Self-extending cloud
CN107005435B (zh) 一种网络服务描述符上架方法及装置
CN108632063B (zh) 管理网络切片实例的方法、装置和系统
CN107105050B (zh) 一种业务对象的存储、下载方法及系统
CN110661647A (zh) 一种生命周期管理方法及装置
WO2018000394A1 (zh) 网络资源的编排方法和设备
US20230261950A1 (en) Method of container cluster management and system thereof
CN112948248A (zh) 云计算服务中的软件调试的方法和装置
CN111371578B (zh) 部署虚拟化网络功能的方法和装置
KR101597246B1 (ko) 가상머신 간에 이동 가능한 가상 디스크 연결방법
US11442756B2 (en) Common service resource application method, related device, and system
CN111786843B (zh) 一种流量采集方法、装置、网络设备及存储介质
CN113504872A (zh) 一种云物理机挂载虚拟磁盘的方法、系统、设备及介质
CN107005468B (zh) 一种待上载的nsd的确定方法及装置
US12026539B2 (en) Service creation and management
WO2020233205A1 (zh) 容器服务管理方法及装置
CN112748981B (zh) 虚拟网络功能的软件镜像的处理方法和装置
JP2016100750A (ja) 設定情報生成システム及び設定情報生成方法
KR20200077943A (ko) 동적 네트워크 확장 방법, 장치 및 시스템
KR20150120220A (ko) 가상화 기반의 서비스 배치 및 제어 장치 및 방법

Legal Events

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

Ref document number: 15875183

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15875183

Country of ref document: EP

Kind code of ref document: A1