WO2016070609A1 - 实现vnf实例化的方法、系统及nfvo和vnfm - Google Patents

实现vnf实例化的方法、系统及nfvo和vnfm Download PDF

Info

Publication number
WO2016070609A1
WO2016070609A1 PCT/CN2015/079839 CN2015079839W WO2016070609A1 WO 2016070609 A1 WO2016070609 A1 WO 2016070609A1 CN 2015079839 W CN2015079839 W CN 2015079839W WO 2016070609 A1 WO2016070609 A1 WO 2016070609A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
vdu
nfvo
instantiated
vnfm
Prior art date
Application number
PCT/CN2015/079839
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 WO2016070609A1 publication Critical patent/WO2016070609A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • NFV Network Function Virtualization
  • NFV technology refers to the traditional network functions, such as: Proxy call session control function (P-CSCF), Interrogating call session control function (I-CSCF), service
  • P-CSCF Proxy call session control function
  • I-CSCF Interrogating call session control function
  • S-CSCF Serving call session control function
  • HSS Home Subscriber Server
  • AS Application Server
  • VNF Virtual network Function Component
  • the European Telecommunications Standards Institute has developed the telecommunication NFV protocol standard, defines an end-to-end reference architecture in the ETSI NFV technical specification, and introduces a network function virtualization orchestrator (NFVO) in the end-to-end reference architecture.
  • NFVO network function virtualization orchestrator
  • Network Functions Virtualization Orchestrator also known as Orchestrator
  • VNFM Virtual Network Function Manager
  • VIM Virtual Infrastructure Manager
  • NFVI Network Functions Virtualization Infrastructure
  • VNF Virtual Network Function
  • NFVO is mainly responsible for network service, virtual resources and physical resource scheduling and related management functions of the whole network
  • VNFM is mainly responsible for lifecycle management of network element VNF (such as instantiate, delete, view, update, horizontal elastic expansion) Scale in/out, vertical elastic scaling scale up/down, self-healing, etc.) VNF-related virtual resource allocation and management
  • VIM is mainly responsible for virtualized infrastructure management, the main function is Now the entire infrastructure layer resources include computing, storage, network resource allocation and management (such as adding, deleting, viewing, updating, fault recovery, etc.); NFVI as a virtualization resource layer, including virtualization new virtualization platform And the original hardware resources; the VNF refers to the virtualized network element, deployed on the NFVI, and performs the network element function defined by the 3GPP, and the function is consistent with the non-virtualization.
  • NFV technology manages resources uniformly and manages VNF.
  • the functions of NFV technology include: cloud resource management function, VNF management function, network service management function, etc.
  • the function involved in this paper is VNF management function.
  • VNF instantiation function is a function that specifies the function that specifies the function that specifies the function that specifies the function that specifies the function that specifies the function that specifies the function that specifies the function that specifies VNF.
  • FIG. 1 is a schematic diagram of the VNF registration process in the relevant specification, as shown in Figure 1. include:
  • Step 100 The user submits the VNF version package to the NFVO to register the VNFD.
  • Step 101 NFVO checks the necessary elements of NVFD, and checks the authenticity and security through the Manifest file;
  • Step 102 NFVO registers VNFD in the database
  • Step 103 NFVO saves the image file in the VNF version package to the image database of the VIM;
  • Step 104 The VIM returns to the NFVO to reserve the mirror successfully.
  • Step 105 NFVO replies to the user that the VNFD registration is successful.
  • Appendix B.3.1 and B.3.2 of the ETSI standard GS NFV-MAN 001 V0.5.0 (2014-05) describe the scheme of VNF instantiation.
  • Appendix B.3.1 describes the scheme.
  • Appendix B.3.2.1 describes scheme 2: that is, VNFM is responsible for allocating resources, certified network elements (EM, Element Management) The VNF instantiation that initiated the instantiation request;
  • Appendix B.3.2.2 describes the third scenario: that is, the VNFM is responsible for allocating resources, and the NFVO initiates the VNF instantiation of the instantiation request.
  • FIG. 2 is a schematic diagram of a VNF instantiation process in which the NFVO is responsible for allocating resources in the related specification, as shown in FIG. 2, including the following steps:
  • Step 200 A sender sends an instantiation VNF request to the NFVO.
  • Step 201 The NFVO checks the validity of the request, including but not limited to: 1) authenticating the user who initiated the request; 2) performing legality check on the requested parameter;
  • Step 202 NFVO performs feasibility analysis on the instantiation request
  • NFVO reserves resources
  • Step 203 NFVO requests VNFM to instantiate VNF
  • Step 204 The VNFM processes the instantiation request, including but not limited to: 1) checking the legality of the request; 2) checking the validity of the request parameter; 3) checking the VNF related parameter, such as a license check; ) computing virtual deployment units (VDUs, Virtual Deployment Unit);
  • Step 205 The VNFM sends a resource reservation request to the NFVO according to the calculated resource requirement.
  • Step 206 The NFVO checks the legality of the resource reservation request, including but not limited to: 1) checking the validity of the resource reservation request parameter; 2) checking the resource location requirement to confirm whether the NFVO can satisfy the VNFM. Resource location requirements; 3) check the interdependence of resources;
  • Step 207 The NFVO initiates a resource occupation request to the VIM, where the resource includes a computing resource, a storage resource, a network resource, and the like;
  • Step 208 The VIM creates an internal network.
  • Step 209 The VIM creates a virtual machine and links the virtual machine to the relevant internal and external network.
  • Step 210 The VIM returns a create resource success response to the NFVO.
  • Step 211 The NFVO notifies the VNFM resource reservation success.
  • Step 212 The VNFM configures VNF deployment related data.
  • Step 213 The VNFM notifies the EM that the VNF deployment is successful, and the VNF is required to be included in the EM management scope;
  • Step 214 The EM configures VNF data, including but not limited to: 1) office data; 2) user data;
  • Step 215 The VNFM notifies the NFVO that the VNF is successfully instantiated
  • Step 216 The NFVO notifies the user that the VNF is successfully instantiated.
  • FIG. 3 is a schematic diagram of a VNF instantiation process in which the VNFM is responsible for allocating resources and the EM initiates an instantiation request in the related specification, as shown in FIG. 3, including:
  • Step 300 EM (Authenticated) sends an instantiation VNF request to the VNFM;
  • Step 301 The VNFM calculates the required number of resources, and then sends an instantiated VNF request to the NFVO, including resource requirements;
  • the instantiated VNF request is used to request the NFVO to perform legality and feasibility check on the instantiation request, and the resource reservation is performed only after the check is passed.
  • Step 302 NFVO performs legality and feasibility check on the instantiation request.
  • Step 303 After the NFVO check is completed, initiate a reservation request for the resource to the VIM.
  • Step 304 The VIM returns a resource reservation success response to the NFVO.
  • step 303 and step 304 are optional steps.
  • Step 305 NFVO replies to the VNFM for legality check, feasibility check, and resource reservation success response;
  • Step 306 The VNFM sends a request to create a network and create a virtual machine (VMs) to the VIM.
  • VMs virtual machine
  • Step 307 After the VIM creates the network and creates the VMs, the VNFM returns a creation success response.
  • Step 308 The VNFM configures the VNF deployment data.
  • Step 309 The VNFM returns to the EM to successfully instantiate the VNF.
  • Step 310 EM and VNFM incorporate VNF into their own management scope
  • Step 311 The EM configures VNF data, including but not limited to: 1) office data; 2) user data;
  • Step 312 The VNFM notifies the NFVO that the VNF is successfully instantiated
  • Step 313 The NFVO establishes a correspondence between the VNF and the resource pool.
  • FIG. 4 is a schematic diagram of a VNF instantiation process in which the VNFM is responsible for allocating resources and the NFVO initiates an instantiation request in the related specification, as shown in FIG. 4, including:
  • Step 400 The NFVO receives the VNF instantiation request; the VNF instantiation request in this step may be manually triggered or automatically triggered, such as triggering from the OSS/BSS;
  • Step 401 NFVO sends an instantiation VNF request to the VNFM.
  • Step 402 The VNFM calculates the required number of resources, and then sends an instantiated VNF request to the NFVO, including resource requirements;
  • the instantiated VNF request is used to request the NFVO to perform legality and feasibility check on the instantiation request, and the resource reservation is performed only after the check is passed.
  • Step 403 NFVO performs legality and feasibility check on the instantiation request.
  • Step 404 After the NFVO check is completed, initiate a reservation request for the resource to the VIM.
  • Step 405 The VIM returns a resource reservation success response to the NFVO.
  • step 303 and step 304 are optional steps.
  • Step 406 The NFVO replies to the VNFM for legality check, feasibility check, and resource reservation success response;
  • Step 407 The VNFM sends a request to create a network and create a VMs to the VIM.
  • Step 408 After the VIM creates the network and creates the VMs, the VNFM returns a creation success response.
  • Step 409 The VNFM configures the VNF deployment data.
  • Step 410 The VNFM returns to the EM to successfully instantiate the VNF.
  • Step 411 EM and VNFM incorporate VNF into their own management scope
  • Step 412 The EM configures the VNF data, including but not limited to: 1) office data; 2) user data;
  • Step 413 The VNFM notifies the NFVO that the VNF is successfully instantiated
  • Step 414 The NFVO establishes a correspondence between the VNF and the resource pool.
  • VNF registration and VNF instantiation scheme of ETSI the same version of VNF is required to release corresponding VNF version packages according to different VNF capacities.
  • These VNF version packages need to be registered on NFVO and generate corresponding Templates, then these templates are referenced during deployment to facilitate the creation of VNFs of corresponding capacity.
  • the VNF registration and instantiation scheme in the relevant specifications has a complicated process and the system is easy to use.
  • a vendor does not release a different version package for different capacities. That is to say, according to the current ETSI specification, VNF instantiation cannot be realized for this case.
  • This paper provides a method, system and NFVO and VNFM for realizing VNF instantiation. It does not need to release different VNF version packages for different capacities, which can simplify the VNF instantiation process and improve the system's ease of use.
  • An embodiment of the present invention provides a method for realizing a virtual network function VNF, including:
  • the virtual network function management VNFM calculates the virtual network function component VNFC and its virtual deployment unit VDU instantiated by the VNF according to the tool for automatically calculating the VDU, combining the capacity of the VNF to be instantiated and its information.
  • the method further includes: in the process of registering the virtual network function description VNFD, the network function virtualization orchestrator NFVO acquires and saves the tool for automatically calculating the VDU.
  • the tool for the NFVO to acquire and save the automatically calculated VDU includes:
  • the user automatically submits the VDU plugin to the NFVO in the VNF version package
  • the obtained plug-in for automatically calculating the VDU is saved in the database.
  • the method further includes: when the NFVO requests the VNFM to instantiate the VNF, the NFVO carries the tool for automatically calculating the VDU. Passed to VNFM in the request.
  • the VNFM calculates the VNFC and its VDU instantiated by the VNF according to the tool for automatically calculating the VDU, and the capacity of the VNF to be instantiated and the information thereof, including:
  • the VNFM After the VNFM receives the instantiation VNF request, the VNFM invokes a tool for automatically calculating the VDU, and combines the capacity of the VNF to be instantiated and its information to calculate the VNFC and the VDU of the VNF instance that is currently requested to be instantiated;
  • the method further includes the VNFM initiating an instantiation VNF request to the NFVO.
  • the resource of the VNF to be instantiated is allocated by the VNFM, and the instantiated VNF request is initiated by the authenticated network element EM or by the network function virtualization orchestrator NFVO.
  • An embodiment of the present invention further provides a system for implementing VNF instantiation, including at least a VNFM;
  • the VNFM includes at least a processor, and is configured to automatically calculate the VNFC and its VDU instantiated by the VNF according to the capacity of the VNF to be instantiated and its information according to the tool for automatically calculating the VDU during the VNF instantiation process.
  • the system further includes: NFVO; the NFVO includes an obtaining module configured to acquire and save a tool for automatically calculating the VDU during registration of the VNFD;
  • the sending module is configured to, when the NFVO is instantiated to the VNFM requesting to instantiate the VNF, the tool that automatically calculates the VDU is carried in the request to the VNFM.
  • the processor is configured to: allocate resources for the VNF to be instantiated, and receive an instantiation VNF request initiated by the authenticated network element EM or initiated by the network function virtualization orchestrator NFVO, and then invoked
  • the tool for automatically calculating the VDU combined with the capacity of the VNF to be instantiated and its information, calculates the VNFC and its VDU of the VNF instance that is currently requested to be instantiated, and then initiates an instantiation VNF request to the NFVO.
  • the processor is configured to: when the resource of the VNF to be instantiated is allocated by the NFVO, receive a request for instantiating the VNF sent by the NFVO, where the request carries the automatically calculated VDU
  • the tool in the process of processing the request for instantiating the VNF, invokes a tool for automatically calculating the VDU, and automatically calculates the VNF instance that is currently instantiated by requesting the capacity of the VNF to be instantiated and its information. VNFC and its VDU.
  • the embodiment of the present invention further provides a VNFM, where the VNFM includes at least a processor, and is configured to automatically calculate the VNF according to the tool for automatically calculating the VDU, combining the capacity of the VNF to be instantiated and the information thereof during the VNF instantiation process.
  • VN instantiated VNFC and its VDU are configured to automatically calculate the VNF according to the tool for automatically calculating the VDU, combining the capacity of the VNF to be instantiated and the information thereof during the VNF instantiation process.
  • the processor is configured to: when the resource of the VNF to be instantiated is allocated by the NFVO, receive a request for instantiating the VNF sent by the NFVO, where the request carries the automatically calculated VDU
  • the tool in the process of processing the request for instantiating the VNF, invokes a tool for automatically calculating the VDU, and automatically calculates the VNF instance that is currently instantiated by requesting the capacity of the VNF to be instantiated and its information. VNFC and its VDU.
  • the processor is configured to: allocate resources for the VNF to be instantiated, and receive an instantiation VNF request initiated by the authenticated network element EM or initiated by the network function virtualization orchestrator NFVO, and then invoked
  • the tool for automatically calculating the VDU combined with the capacity of the VNF to be instantiated and its information, calculates the VNFC and its VDU of the VNF instance that is currently requested to be instantiated, and then initiates an instantiation VNF request to the NFVO.
  • An embodiment of the present invention further provides an NFVO, where the NFVO includes an obtaining module and a sending module, where
  • the obtaining module is configured to acquire and save a tool for automatically calculating a VDU during registration of the VNFD;
  • the sending module is configured to: when the NFVO requests the VNF to be instantiated by the NFVO, when the NFVO requests the VNFM to instantiate the VNF, the tool that automatically calculates the VDU is carried in the request and transmitted to the VNFM.
  • the obtaining module is configured to: receive a VNF version package from the user that carries the plug-in that automatically calculates the VDU; and save the obtained VDF plug-in to the database while registering the VNFD in the database.
  • the embodiment of the invention further provides a computer readable storage medium storing program instructions, which can be implemented when the program instructions are executed.
  • the technical solution of the embodiment of the present invention includes a tool with a calculation capacity in the VNF version package in the VNF instantiation process, and the VNFM combines the requirements of the VNF to be instantiated according to the tool for automatically calculating the VDU. And information, etc., automatically calculate the VNFCs and their VDUs instantiated by the VNF.
  • the embodiment of the present invention does not need to release different VNF version packages for different capacities, reduces the number of VNF release packages, reduces the number of NFVO management VNF versions, and simplifies the VNF instantiation process. Thereby improving the ease of use of the system.
  • the technical solution provided by the embodiment of the present invention is applicable to all types of VNFs.
  • FIG. 1 is a schematic flow chart of a VNF registration process in a related specification
  • FIG. 2 is a schematic flow chart of VNF instantiation by the NFVO for allocating resources in the relevant specification
  • FIG. 3 is a schematic diagram of a VNF instantiation process in which the VNFM is responsible for allocating resources and the EM initiates an instantiation request in the related specification;
  • VNFM is responsible for allocating resources and the NFVO initiates an instantiation request in the related specification
  • FIG. 5 is a flowchart of a method for implementing VNF instantiation according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of a system for implementing VNF instantiation according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for implementing VNF instantiation according to an embodiment of the present invention. As shown in FIG. 5, the method includes:
  • Step 501 During the VNF instantiation process, the VNFM calculates the VNFC and its VDU instantiated by the VNF according to the tool for automatically calculating the VDU, combining the capacity of the VNF to be instantiated and its information.
  • This step includes:
  • the NFVO When the VNF that is responsible for allocating resources by the NFVO is instantiated, that is, when the resources of the VNF to be instantiated are allocated by the NFVO, when the NFVO requests the VNFM to instantiate the VNF, that is, the step 203 of FIG. 2, the NFVO will automatically calculate the VDU tool. Carry in the request to VNFM;
  • the VNFM invokes a tool for automatically calculating the VDU, and automatically calculates the VNFC of the VNF instance that is currently requested to be instantiated, combined with the capacity of the VNF to be instantiated and its information. Its VDU.
  • VNFM When the VNFM is responsible for allocating resources, the EM initiates an instantiation request, or the VNFM is responsible for allocating resources, and the NFVO initiates an instantiation request, the VNFM initiates an instantiation VNF request to the NFVO, ie, step 301 of FIG. 3 or step 402 of FIG. 4, VNFM
  • the tool that automatically calculates the VDUs is called, and the VNFC and its VDU of the VNF instance that is currently requested to be instantiated are automatically calculated according to the capacity of the VNF to be instantiated and its information.
  • Each VNF has its own unique information, that is, the information of the VNF to be instantiated in step 100 of FIG. 1.
  • the information of the VNF is different for different VNFs, such as CSCF and SSS, and the information is different, corresponding to the CSCF. It may include the frequency of registration and logout, the number of user traffic erl, the frequency of subscription and refresh subscriptions, and the frequency of short messages.
  • For SSS it may include the service penetration rate of call forwarding and the service penetration rate of three-party calls.
  • the capacity to be instantiated is mainly the number of users (different VNFs may be different).
  • the tool that automatically calculates the VDU calculates how many virtual machines (VNFC and VDU) are needed, how much memory each virtual machine requires, how many vCPUs, how many hard disks, and each virtual Network link of the machine, etc.
  • VNFC and VDU The calculation of the VNFC and the VDU of the VNF instance that is currently requested to be instantiated in the step 501 is described in the ETSI specification, and includes the requirements of the VNFC and the VDU for calculation, storage, and network resources, and details are not described herein.
  • VNF instantiation process on the basis of the original instantiation mechanism, different VNF version packages are not required to be released for different capacities, the number of VNF release packages is reduced, and the NFVO management VNF version is reduced. The number simplifies the VNF instantiation process, thereby providing improved ease of use of VNF management.
  • This step also includes:
  • Step 500 During registration of the VNFD, the NFVO acquires and saves a tool for automatically calculating the VDU;
  • the method in the embodiment when the user submits the VNF version package to the NFVO, the method in the embodiment also carries the tool for automatically calculating the VDU and sends it to the NFVO in the VNF version package;
  • the method of the embodiment further includes: the NFVO saves the obtained tool for automatically calculating the VDU to the database.
  • the tool for automatically calculating the VDU can be developed, for example, by using C++. In actual implementation, it can be implemented by means of a plug-in or the like, and details are not described herein.
  • the technical solution provided in this embodiment carries a tool for automatically calculating a VDU in the VNF version package, so that the tool for calculating the capacity is used in the deployment process, and corresponding VNFCs and VDUs are calculated according to different VNF capacity requirements (VNFC).
  • VNFC VNF capacity requirements
  • One-to-one correspondence with VDU VDU
  • the automatic calculation tool in the released version automatically calculates the VDU for 100,000 bureaus, 200,000 bureaus, 500,000 bureaus, 1 million bureaus, and the like.
  • VNF The number of tools; if there is no automatic calculation of VDU tools, for 100,000 bureaus, 200,000 bureaus, 500,000 bureaus, 1 million bureaus, etc., because there is no automatic calculation function, different versions need to be released. Therefore, the same version of the VNF in this embodiment only needs to release one version package, and only needs to be registered once on the NFVO. VNF does not need to release different VNF version packages for different capacities, which simplifies the release of VNF and improves the system's ease of use.
  • the optimization of the process described in FIG. 1 includes:
  • the VNF version package that the user submits to the NFVO to register the VNFD further includes a plug-in that automatically calculates the VDU;
  • the plug-in that automatically calculates the VDU obtained from the VNF version report is also saved to the database.
  • the present example optimizes the flow of FIG. 2 on the basis of inheriting the flow shown in FIG. 2, including:
  • the NFVO In the NFVO request VNFM shown in step 203 to instantiate the VNF, the NFVO simultaneously carries the automatic calculation tool for automatically calculating the VDU in the request and sends it to the VNFM;
  • VNFM calls a tool for automatically calculating the VDU, and combines the capacity of the VNF to be instantiated and its information to calculate the VDU corresponding to the VNF that the current request instance will be.
  • the present example optimizes the flow of FIG. 3 on the basis of inheriting the flow shown in FIG. :
  • the method further includes: the VNFM invokes a tool for automatically calculating the VDU, and combines the capacity of the VNF to be instantiated and the information thereof to calculate a VDU corresponding to the VNF that is currently requested by the instance. Then, in step 301, the method sends an instantiation VNF request (including resource requirements) to the NFVO, and requests the NFVO to perform legality and feasibility check on the instantiation request, and if the check passes, the resource reservation is performed.
  • the VNFM invokes a tool for automatically calculating the VDU, and combines the capacity of the VNF to be instantiated and the information thereof to calculate a VDU corresponding to the VNF that is currently requested by the instance.
  • the method sends an instantiation VNF request (including resource requirements) to the NFVO, and requests the NFVO to perform legality and feasibility check on the instantiation request, and if the check passes, the resource reservation is performed.
  • the present example optimizes the flow of FIG. 4 on the basis of inheriting the flow shown in FIG. :
  • the method further includes: the VNFM invokes a tool for automatically calculating the VDU, and combines the capacity of the VNF to be instantiated and the information thereof to calculate the current request instance.
  • the method sends an instantiation VNF request (including resource requirements) to the NFVO, and requests the NFVO to perform legality and feasibility check on the instantiation request, and if the check passes, the resource reservation is performed.
  • FIG. 6 is a schematic structural diagram of a system for implementing VNF instantiation according to an embodiment of the present invention, as shown in FIG. 6, including at least a VNFM;
  • the VNFM includes a processor, and is configured to automatically calculate the VNFC and its VDU instantiated by the VNF according to the tool for automatically calculating the VDU, combined with the capacity of the VNF to be instantiated and its information, in the VNF instantiation process.
  • the processor is configured to receive a request for instantiating a VNF sent by the NFVO when the resource of the VNF to be instantiated is allocated by the NFVO, where the request carries a tool for automatically calculating the VDU; In the process of instantiating the request for processing, the tool for automatically calculating the VDU is invoked, and the VNFC and its VDU of the VNF instance that is currently requested to be instantiated are automatically calculated according to the capacity of the VNF to be instantiated and its information.
  • the processor is configured to, when the VNFM is responsible for allocating resources, when the EM initiates an instantiation request, or when the VNFM is responsible for allocating resources, and the NFVO initiates the instantiation request, the VNFM calls automatically before the VNFM initiates the instantiation VNF request to the NFVO.
  • the tool for calculating VDUs combined with the capacity to be instantiated and its information, automatically calculates the VNFC and its VDU of the VNF instance that is currently requested to be instantiated.
  • the processor is configured to allocate resources for the VNF to be instantiated, and after receiving an instantiated VNF request initiated by the authenticated network element EM or initiated by the NFVO, invoke a tool for automatically calculating the VDU, and combine the instance to be executed.
  • the VNF capacity and its information calculate the VNFC and VDU of the VNF instance that is currently requested to be instantiated, and then initiate instantiation VNF request to NFVO.
  • the system of the embodiment of the present invention further includes: NFVO; the NFVO includes at least an obtaining module and a sending module, where:
  • the obtaining module is configured to acquire and save a tool for automatically calculating a VDU during registration of the VNFD;
  • the sending module is configured to be instantiated when the VNF that is responsible for allocating resources by the NFVO
  • the NFVO requests the VNFM to instantiate the VNF
  • the tool that automatically calculates the VDU is carried in the request to the VNFM.
  • the obtaining module is configured to: receive a VNF version package from the user that carries the plug-in that automatically calculates the VDU; and store the VNFD in the database, and save the obtained plug-in for automatically calculating the VDU into the database.

Abstract

一种实现VNF实例化的方法、系统及NFVO和VNFM,包括在VNF实例化过程中,VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出该VNF实例化的VNFC及其VDU。

Description

实现VNF实例化的方法、系统及NFVO和VNFM 技术领域
本文涉及网络功能虚拟(NFV,Network Functions Virtualization)技术,尤指一种实现VNF实例化的方法、系统及NFVO和VNFM。
背景技术
NFV技术指的是,将传统网络功能,比如:代理呼叫会话控制功能实体(P-CSCF,Proxy call session control Function),查询呼叫会话控制功能实体(I-CSCF,Interrogating call session control Function),服务呼叫会话控制功能实体(S-CSCF,Serving call session control Function),归属用户服务器(HSS,Home subscriber Server),以及应用服务器(AS,Application Server),等进行虚拟化,并将这些虚拟网络功能组件(VNFC,Virtualized Network Function Component)部署在云虚拟机上,从而实现网络功能的虚拟化,虚拟化后的网络功能称为虚拟网络功能(VNF),VNF运行在云之上,NFV实现了VNF和硬件资源的解耦,VNF按需占用资源,从而提高了资源的利用效率,当网络负荷低时,还会关闭部分服务器,从而也节约了能源,更加绿色环保。
欧洲电信标准化协会(ETSI,European Telecommunications Standards Institute)制定了电信NFV协议标准,在ETSI NFV技术规范中定义了端到端参考架构,在端到端参考架构中引入了网络功能虚拟化编排器(NFVO,Network Functions Virtualization Orchestrator,也称Orchestrator)、虚拟网络功能管理(VNFM,Virtualized Network Function Manager)、虚拟基础设施管理(VIM,Virtualized Infrastructure Manager)、网络功能虚拟化基础设施(NFVI,Network Functions Virtualization Infrastructure),以及虚拟网络功能(VNF,Virtualized Network Function)等功能单元。其中,NFVO主要负责全网的网络服务、虚拟资源以及物理资源的编排和相关管理功能;VNFM主要负责网元VNF的生命周期管理(如实例化(instantiate)、删除、查看、更新、横向弹性伸缩scale in/out、纵向弹性伸缩scale up/down、自愈等)和VNF相关的虚拟资源的分配和管理;VIM主要负责虚拟化基础设施管理,主要功能是实 现对整个基础设施层资源包括计算、存储、网络资源的分配和管理(如增加、删除、查看、更新、故障恢复等);NFVI作为虚拟化资源层,包括虚拟化后新增的虚拟化平台和原有的硬件资源;VNF指虚拟化后的网元,部署在NFVI上,执行着3GPP定义的网元功能,功能与非虚拟化时保持一致。
相对于传统网络而言,NFV技术对资源统一管理、对VNF进行统一管理,NFV技术包括的功能有:云资源管理功能、VNF管理功能、网络业务管理功能等,本文涉及的功能是VNF管理功能中的VNF实例化功能。
ETSI标准《GS NFV-MAN 001 V0.5.0(2014-05)》附录B.3.1和B.3.2描述的是VNF实例化的协作流程,在VNF实例化的协作流程中,VNF的同一个版本需要根据不同的VNF容量,发布相应的多个VNF版本包,这些版本包都需要在NFVO上注册并产生相应的模版,在部署的过程中引用这些模版以创建相应容量的VNF。
ETSI标准《GS NFV-MAN 001 V0.5.0(2014-05)》的附录B.2描述的是VNF注册过程,VNF注册过程完成虚拟网络功能描述(VNFD,Virtual network function descriptor)在NFVO数据库中的注册过程,相当于在NFVO数据库中注册一个VNF的模版,后续在部署的过程中,可以引用这个模版创建VNF实例,图1为相关规范中的VNF注册过程的流程示意图,如图1所示,包括:
步骤100:用户将VNF版本包提交给NFVO,对VNFD进行注册;
步骤101:NFVO检查NVFD的必要元素,通过Manifest文件检查真实性和安全性;
步骤102:NFVO在数据库中登记VNFD;
步骤103:NFVO将VNF版本包中的镜像文件保存到VIM的镜像库中;
步骤104:VIM向NFVO回复保留镜像成功;
步骤105:NFVO向用户回复VNFD注册成功。
ETSI标准《GS NFV-MAN 001 V0.5.0(2014-05)》的附录B.3.1和B.3.2描述了VNF实例化的方案,一共有三种实现方式,其中,附录B.3.1描述了方案一:即由NFVO负责分配资源的VNF实例化;附录B.3.2.1描述了方案二:即由VNFM负责分配资源,经过认证的网元(EM,Element Management) 发起实例化请求的VNF实例化;附录B.3.2.2描述了方案三:即由VNFM负责分配资源,NFVO发起实例化请求的VNF实例化。
图2为相关规范中的由NFVO负责分配资源的VNF实例化的流程示意图,如图2所示,包括以下步骤:
步骤200:用户(sender)向NFVO发送实例化VNF请求;
步骤201:NFVO对请求进行有效性检查,包括但不限于:1)对发起请求的用户进行鉴权;2)对请求的参数进行合法性检查;
步骤202:NFVO对实例化请求进行可行性分析;
本步骤中,在可行性分析的同时,可选地,NFVO对资源进行预留;
步骤203:NFVO请求VNFM对VNF进行实例化;
步骤204:VNFM对实例化请求进行处理,包括但不限于:1)检查请求的合法性;2)检查请求参数的合法性;3)VNF相关参数检查,比如许可证(license)检查等;4)计算虚拟部署单元(VDUs,Virtual Deployment Unit);
步骤205:VNFM根据计算后的资源需求,向NFVO发送资源预留请求;
步骤206:NFVO对资源预留请求进行合法性检查,包括但不限于:1)对资源预留请求的参数进行合法性检查;2)对资源的位置要求进行检查,确认NFVO能否满足VNFM的资源位置要求;3)对资源的相互依赖关系进行检查;
步骤207:NFVO向VIM发起资源占用请求,资源包括计算资源、存储资源、网络资源等;
步骤208:VIM创建内部网络;
步骤209:VIM创建虚拟机,并将虚拟机链接到相关内外部网络;
步骤210:VIM向NFVO返回创建资源成功响应;
步骤211:NFVO通知VNFM资源预留成功;
步骤212:VNFM配置VNF部署相关数据;
步骤213:VNFM通知EM:VNF部署成功,要求将VNF纳入到EM管理范围;
步骤214:EM配置VNF数据,包括但不限于:1)局数据;2)用户数据;
步骤215:VNFM通知NFVO:VNF实例化成功;
步骤216:NFVO通知用户:VNF实例化成功。
图3为相关规范中的由VNFM负责分配资源,EM发起实例化请求的VNF实例化的流程示意图,如图3所示,包括:
步骤300:EM(经认证)向VNFM发送实例化VNF请求;
步骤301:VNFM计算所需的资源数,然后向NFVO发送实例化VNF请求,其中包括有资源要求;
本步骤中,实例化VNF请求用于请求NFVO对实例化请求进行合法性、可行性检查,并且只有在检查通过后才则进行资源预留。
步骤302:NFVO对实例化请求进行合法性、可行性检查;
步骤303:NFVO检查完毕后,向VIM发起对资源进行预留请求;
步骤304:VIM向NFVO回复资源预留成功响应;
需要说明的是,步骤303和步骤304为可选步骤。
步骤305:NFVO向VNFM回复进行合法性检查通过、可行性检查通过、资源预留成功响应;
步骤306:VNFM向VIM发送创建网络和创建虚拟机(VMs)请求;
步骤307:VIM创建网络、创建VMs后,向VNFM返回创建成功响应。
步骤308:VNFM配置VNF部署数据;
步骤309:VNFM向EM返回VNF实例化成功;
步骤310:EM和VNFM将VNF纳入到自身的管理范围;
步骤311:EM配置VNF数据,包括但不限于:1)局数据;2)用户数据;
步骤312:VNFM通知NFVO:VNF实例化成功;
步骤313:NFVO建立VNF和资源池的对应关系。
图4为相关规范中的由VNFM负责分配资源,NFVO发起实例化请求的VNF实例化的流程示意图,如图4所示,包括:
步骤400:NFVO收到VNF实例化请求;本步骤中的VNF实例化请求可能是手动触发或者自动触发,比如从OSS/BSS触发等;
步骤401:NFVO向VNFM发送实例化VNF请求;
步骤402:VNFM计算所需的资源数,然后向NFVO发送实例化VNF请求,其中包括有资源要求;
本步骤中,实例化VNF请求用于请求NFVO对实例化请求进行合法性、可行性检查,并且只有在检查通过后才则进行资源预留。
步骤403:NFVO对实例化请求进行合法性、可行性检查;
步骤404:NFVO检查完毕后,向VIM发起对资源进行预留请求;
步骤405:VIM向NFVO回复资源预留成功响应;
需要说明的是,步骤303和步骤304为可选步骤。
步骤406:NFVO向VNFM回复进行合法性检查通过、可行性检查通过、资源预留成功响应;
步骤407:VNFM向VIM发送创建网络和创建VMs请求;
步骤408:VIM创建网络、创建VMs后,向VNFM返回创建成功响应;
步骤409:VNFM配置VNF部署数据;
步骤410:VNFM向EM返回VNF实例化成功;
步骤411:EM和VNFM将VNF纳入到自身的管理范围;
步骤412:EM配置VNF数据,包括但不限于:1)局数据;2)用户数据;
步骤413:VNFM通知NFVO:VNF实例化成功;
步骤414:NFVO建立VNF和资源池的对应关系。
在实际应用过程中,当通过NFVO实例化VNF时,经常需要针对同一个VNF版本实例化不同容量的VNF,比如同一个S-CSCF版本,需要实例化一 个上海局和一个苏州局,这两个局的容量可能完全不同。目前,在ETSI的VNF注册和VNF实例化方案中,要求VNF的同一个版本需要根据不同的VNF容量,发布相应的多个VNF版本包,这些VNF版本包都需要在NFVO上注册并产生相应的模版,然后,在部署的过程中引用这些模版以便于创建相应容量的VNF。相关规范中的VNF注册及实例化方案,过程复杂,系统的易用性较差。而且,一般,厂商在发布VNF版本包时,不会针对不同容量发布不同的版本包。也就是说,按照目前ETSI的规范,对于这种情况是无法实现VNF实例化的。
发明内容
本文提供一种实现VNF实例化的方法、系统及NFVO和VNFM,不需要针对不同容量发布不同的VNF版本包,能够简化VNF实例化过程,提高系统的易用性。
本发明实施例提供了一种实现虚拟网络功能VNF实例化的方法,包括:
在VNF实例化过程中,虚拟网络功能管理VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出该VNF实例化的虚拟网络功能组件VNFC及其虚拟部署单元VDU。
可选地,该方法之前还包括:在对虚拟网络功能描述VNFD进行注册过程中,网络功能虚拟化编排器NFVO获取并保存所述自动计算VDU的工具。
可选地,所述NFVO获取并保存所述自动计算VDU的工具包括:
用户将自动计算VDU的插件携带在VNF版本包中提交给所述NFVO;
所述NFVO在数据库中登记VNFD时,将获得的自动计算VDU的插件保存到数据库中。
可选地,所述待实例化的VNF的资源由NFVO负责分配时,所述方法还包括:在所述NFVO向VNFM请求对VNF进行实例化时,所述NFVO将自动计算VDU的工具携带在请求中传递给VNFM。
可选地,所述VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出该VNF实例化的VNFC及其VDU,包括:
所述VNFM接收到实例化VNF请求后,所述VNFM调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出当前请求实例化的VNF实例的VNFC及其VDU;
所述计算出该VNF实例化的VNFC及其VDU之后,所述方法还包括所述VNFM向NFVO发起实例化VNF请求。
可选地,所述待实例化的VNF的资源由VNFM负责分配,所述实例化VNF请求由经过认证的网元EM发起或由网络功能虚拟化编排器NFVO发起。
本发明实施例还提供了一种实现VNF实例化的系统,至少包括VNFM;
VNFM至少包括处理器,设置为在VNF实例化过程中,根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出该VNF实例化的VNFC及其VDU。
可选地,所述系统还包括:NFVO;NFVO包括获取模块,设置为在对VNFD进行注册过程中,获取并保存自动计算VDU的工具;以及
发送模块,设置为当由所述NFVO负责分配资源的VNF实例化时,在NFVO向VNFM请求对VNF进行实例化时,将自动计算VDU的工具携带在请求中传递给VNFM。
可选地,所述处理器是设置为:为所述待实例化的VNF分配资源,接收由经过认证的网元EM发起或由网络功能虚拟化编排器NFVO发起的实例化VNF请求后,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出当前请求实例化的VNF实例的VNFC及其VDU,之后向NFVO发起实例化VNF请求。
可选地,所述处理器是设置为:所述待实例化的VNF的资源由NFVO负责分配时,接收NFVO发送的对VNF进行实例化的请求,所述请求中携带有所述自动计算VDU的工具,在对所述对VNF进行实例化的请求进行处理的过程中,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。
本发明实施例还提供了一种VNFM,VNFM至少包括处理器,设置为在VNF实例化过程中,VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出该VNF实例化的VNFC及其VDU。
可选地,所述处理器是设置为:所述待实例化的VNF的资源由NFVO负责分配时,接收NFVO发送的对VNF进行实例化的请求,所述请求中携带有所述自动计算VDU的工具,在对所述对VNF进行实例化的请求进行处理的过程中,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。
可选地,所述处理器是设置为:为所述待实例化的VNF分配资源,接收由经过认证的网元EM发起或由网络功能虚拟化编排器NFVO发起的实例化VNF请求后,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出当前请求实例化的VNF实例的VNFC及其VDU,之后向NFVO发起实例化VNF请求。
本发明实施例还提供了一种NFVO,NFVO包括获取模块和发送模块,其中,
所述获取模块,设置为在对VNFD进行注册过程中,NFVO获取并保存自动计算VDU的工具;
所述发送模块,设置为当由所述NFVO负责分配资源的VNF实例化时,在NFVO向VNFM请求对VNF进行实例化时,将自动计算VDU的工具携带在请求中传递给VNFM。
可选地,所述获取模块设置为:在接收来自用户的携带有自动计算VDU的插件的VNF版本包;在数据库中登记VNFD的同时,将获得的自动计算VDU的插件保存到数据库中。
本发明实施例还提供一种计算机可读存储介质,存储有程序指令,当该程序指令被执行时可实现上述方法。
与相关技术相比,本发明实施例技术方案包括在VNF实例化过程中,在VNF版本包中带有计算容量的工具,VNFM根据自动计算VDU的工具,结合待实例化的VNF的要求如容量及信息等,自动计算出该VNF实例化的VNFCs及其VDUs。本发明实施例在原有实例化机制的基础上,不需要针对不同容量发布不同的VNF版本包,减少了VNF发布版本包的次数,减少了NFVO管理VNF版本的数目,简化了VNF实例化过程,从而提高了系统的易用性。本发明实施例提供的技术方案适应于所有类型的VNF。
附图概述
图1为相关规范中的VNF注册过程的流程示意图;
图2为相关规范中的由NFVO负责分配资源的VNF实例化的流程示意图;
图3为相关规范中的由VNFM负责分配资源,EM发起实例化请求的VNF实例化的流程示意图;
图4为相关规范中的由VNFM负责分配资源,NFVO发起实例化请求的VNF实例化的流程示意图;
图5为本发明实施例实现VNF实例化的方法的流程图;
图6为本发明实施例实现VNF实例化的系统的组成结构示意图。
本发明的实施方式
需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互任意组合。
图5为本发明实施例实现VNF实例化的方法的流程图,如图5所示,包括:
步骤501:在VNF实例化过程中,VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算该VNF实例化的VNFC及其VDU。
本步骤包括:
当由NFVO负责分配资源的VNF实例化时,即待实例化的VNF的资源是由NFVO分配时,在NFVO向VNFM请求对VNF进行实例化即图2步骤203时,NFVO将自动计算VDU的工具携带在请求中传递给VNFM;
在VNFM对实例化请求进行处理的过程即图2步骤204中,VNFM调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。
或者,
当由VNFM负责分配资源,EM发起实例化请求时,或由VNFM负责分配资源,NFVO发起实例化请求时,在VNFM向NFVO发起实例化VNF请求即图3步骤301或图4步骤402之前,VNFM调用自动计算VDUs的工具,结合待实例化的VNF的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。
其中,每种VNF有自己独特的信息即图1步骤100中的待实例化的VNF的信息,不同的VNF,其信息会有所不同,比如CSCF和SSS,其信息会不同,对应CSCF而言,可能会包括注册注销的频率、用户话务erl数、订阅和刷新订阅频率、短消息频率等,而对于SSS而言,可能包括呼叫前转的业务渗透率、三方通话的业务渗透率等。待实例化的容量主要是用户数(不同VNF可能会不同)。
例如,局方要部署一个100万容量的局,该自动计算VDU的工具会计算出需要多少虚拟机(VNFC和VDU),每个虚拟机需要多少内存,多少个vCPU,多大的硬盘,每个虚拟机的网络链接等。步骤501中的计算出当前请求实例化的VNF实例的VNFC及其VDU如何实现,在ETSI规范中有描述,主要包括VNFC和VDU对计算、存储、网络资源的需求等,这里不再赘述。
通过本实施例技术方案,在VNF实例化过程中,在原有实例化机制的基础上,不需要针对不同容量发布不同的VNF版本包,减少了VNF发布版本包的次数,减少了NFVO管理VNF版本的数目,简化了VNF实例化过程,从而提供提高了VNF管理的易用性。
本步骤之前还包括:
步骤500:在对VNFD进行注册过程中,NFVO获取并保存自动计算VDU的工具;
按照图1所示的VNF注册流程,用户在将VNF版本包提交给NFVO时,本实施例方法中同时还将自动计算VDU的工具携带在VNF版本包中发送给NFVO;
按照图1所示的VNF注册流程,在NFVO在数据库中登记VNFD的同时,本实施例方法还包括:NFVO将获得的自动计算VDU的工具保存到数据库中。
其中,自动计算VDU的工具例如可以使用C++开发,在实际实现中可以通过插件等方式来实现,这里不再赘述。
本实施例提供的技术方案,在VNF版本包中携带有自动计算VDU的工具,这样,在部署的过程中利用该计算容量的工具,根据不同VNF容量要求,计算出相应的VNFCs及VDUs(VNFC与VDU一一对应),然后再根据VDUs进行实例化。采用本实施例方法,由于有了自动计算VDU的工具,针对10万的局、20万的局、50万的局、100万的局等等,发布的版本中的自动计算工具会自动计算VDU的数目;而如果没有自动计算VDU的工具,针对10万的局、20万的局、50万的局、100万的局等等,由于不具备自动计算的功能,需要发布不同的版本。因此,本实施例中的VNF的同一版本只需要发布一个版本包,在NFVO上也只需要注册一次。VNF不需要针对不同容量发布不同的VNF版本包,简化了VNF的发布,提高了系统的易用性。
下面结合应用示例对本发明实施例方法进行详细描述。
应用示例1
针对图1所示的相关规范中的VNF注册过程的流程,本示例对其流程进行了优化,在继承图1所示流程的基础上,对图1所述流程进行的优化包括:
在图1所示的步骤100中,用户提交给NFVO的对VNFD进行注册的VNF版本包中还包括有自动计算VDU的插件;
而且,在NFVO在数据库中登记VNFD时,同时将从VNF版本报中获得的自动计算VDU的插件保存到数据库中。
应用示例2
针对图2所示的相关规范中的由NFVO负责分配资源的VNF实例化的流程,本示例在继承图2所示流程的基础上,对图2的流程进行的优化包括:
在步骤203所示的NFVO请求VNFM对VNF进行实例化中,NFVO同时将自动计算VDU的自动计算工具携带在请求中发送给VNFM;
在步骤204所示的VNFM对实例化请求进行处理中,除了包括相关流程中的:VNFM检查请求的合法性;VNFM检查请求参数的合法性;以及VNFM检查VNF相关参数,例如license检查之外,还包括:VNFM调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算当前请求实例会化的VNF对应的VDU。
应用示例3
针对图3所示的相关规范中的由VNFM负责分配资源,EM发起实例化请求的VNF实例化的流程,本示例在继承图3所示流程的基础上,对图3的流程进行的优化包括:
在步骤300之后,步骤301之前,还包括:VNFM调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算当前请求实例会化的VNF对应的VDU。之后在执行步骤301中的向NFVO发送实例化VNF请求(包括资源要求),请求NFVO对实例化请求进行合法性、可行性检查,如检查通过,则进行资源预留等。
应用示例4
针对图4所示的相关规范中的由VNFM负责分配资源,NFVO发起实例化请求的VNF实例化的流程,本示例在继承图4所示流程的基础上,对图4的流程进行的优化包括:
在步骤401之后,步骤402之前,还包括:VNFM调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算当前请求实例会化的 VNF对应的VDU。之后在执行步骤301中的向NFVO发送实例化VNF请求(包括资源要求),请求NFVO对实例化请求进行合法性、可行性检查,如检查通过,则进行资源预留等。
图6为本发明实施例实现VNF实例化的系统的组成结构示意图,如图6所示,至少包括VNFM;
VNFM包括处理器,设置为在VNF实例化过程中,VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出该VNF实例化的VNFC及其VDU。
其中,所述处理器是设置为,所述待实例化的VNF的资源由NFVO负责分配时,接收NFVO发送的对VNF进行实例化的请求,所述请求中携带有自动计算VDU的工具;在实例化请求进行处理的过程中,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。
或者,
所述处理器是设置为,当由VNFM负责分配资源,EM发起实例化请求时,或由VNFM负责分配资源,NFVO发起实例化请求时,在VNFM向NFVO发起实例化VNF请求之前,VNFM调用自动计算VDUs的工具,结合待实例化的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。即所述处理器是设置为:为所述待实例化的VNF分配资源,接收由经过认证的网元EM发起或由NFVO发起的实例化VNF请求后,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出当前请求实例化的VNF实例的VNFC及其VDU,之后向NFVO发起实例化VNF请求
本发明实施例系统还包括:NFVO;NFVO至少包括获取模块和发送模块,其中:
所述获取模块,设置为在对VNFD进行注册过程中,NFVO获取并保存自动计算VDU的工具;
所述发送模块,设置为当由所述NFVO负责分配资源的VNF实例化时, 在NFVO向VNFM请求对VNF进行实例化时,将自动计算VDU的工具携带在请求中传递给VNFM。
其中,所述获取模块是设置为:在接收来自用户的携带有自动计算VDU的插件的VNF版本包;在数据库中登记VNFD的同时,将获得的自动计算VDU的插件保存到数据库中。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成,所述程序可以存储于计算机可读存储介质中,如只读存储器、磁盘或光盘等。可选地,上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地,上述实施例中的各模块/单元可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
工业实用性
在本发明实施例方案,在原有实例化机制的基础上,不需要针对不同容量发布不同的VNF版本包,减少了VNF发布版本包的次数,减少了NFVO管理VNF版本的数目,简化了VNF实例化过程,从而增加了系统的易用性。

Claims (17)

  1. 一种实现虚拟网络功能VNF实例化的方法,包括:
    在VNF实例化过程中,虚拟网络功能管理VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出该VNF实例化的虚拟网络功能组件VNFC及其虚拟部署单元VDU。
  2. 根据权利要求1所述的方法,该方法之前还包括:
    在对虚拟网络功能描述VNFD进行注册过程中,网络功能虚拟化编排器NFVO获取并保存所述自动计算VDU的工具。
  3. 根据权利要求2所述的方法,其中,所述NFVO获取并保存所述自动计算VDU的工具,包括:
    所述NFVO从用户提交的VNF版本包中获取自动计算VDU的插件;所述NFVO在数据库中登记VNFD时,将获得的自动计算VDU的插件保存到数据库中。
  4. 根据权利要求2所述的方法,所述待实例化的VNF的资源由NFVO负责分配时,所述方法还包括:在所述NFVO向VNFM请求对VNF进行实例化时,所述NFVO将自动计算VDU的工具携带在请求中传递给VNFM。
  5. 根据权利要求1-4中任一权利要求所述的方法,其中,
    所述VNFM根据自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出该VNF实例化的VNFC及其VDU,包括:
    所述VNFM接收到实例化VNF请求后,所述VNFM调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出当前请求实例化的VNF实例的VNFC及其VDU;
    所述计算出该VNF实例化的VNFC及其VDU之后,所述方法还包括所述VNFM向NFVO发起实例化VNF请求。
  6. 根据权利要求5所述的方法,其中,所述待实例化的VNF的资源由VNFM负责分配,所述实例化VNF请求由经过认证的网元EM发起或由网络功能虚拟化编排器NFVO发起。
  7. 一种实现虚拟网络功能VNF实例化的系统,包括虚拟网络功能管理VNFM;
    所述VNFM包括处理器,设置为在VNF实例化过程中,根据自动计算虚拟部署单元VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出该VNF实例化的虚拟网络功能组件VNFC及其VDU。
  8. 根据权利要求7所述的系统,所述系统还包括:网络功能虚拟化编排器NFVO;NFVO包括:
    获取模块,设置为在对虚拟网络功能描述VNFD进行注册过程中,获取并保存自动计算VDU的工具;以及
    发送模块,设置为当由所述NFVO负责分配资源的VNF实例化时,在NFVO向VNFM请求对VNF进行实例化时,将自动计算VDU的工具携带在请求中传递给VNFM。
  9. 根据权利要求8所述的系统,其中,所述获取模块是设置为:在接收来自用户的携带有自动计算VDU的插件的VNF版本包;在数据库中登记VNFD的同时,将获得的自动计算VDU的插件保存到数据库中。
  10. 根据权利要求7所述的系统,其中,所述处理器是设置为:
    为所述待实例化的VNF分配资源,接收由经过认证的网元EM发起或由网络功能虚拟化编排器NFVO发起的实例化VNF请求后,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出当前请求实例化的VNF实例的VNFC及其VDU,之后向NFVO发起实例化VNF请求。
  11. 根据权利要求8或9所述的系统,其中,所述处理器是设置为:
    所述待实例化的VNF的资源由NFVO负责分配时,接收NFVO发送的对VNF进行实例化的请求,所述请求中携带有所述自动计算VDU的工具,在对所述对VNF进行实例化的请求进行处理的过程中,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。
  12. 一种虚拟网络功能管理VNFM,包括处理器,设置为在VNF实例化过程中,VNFM根据自动计算虚拟部署单元VDU的工具,结合待实例化的 VNF的容量及其信息,自动计算出该VNF实例化的虚拟网络功能组件VNFC及其VDU。
  13. 根据权利要求12所述的VNFM,其中,所述处理器是设置为:
    所述待实例化的VNF的资源由NFVO负责分配时,接收NFVO发送的对VNF进行实例化的请求,所述请求中携带有所述自动计算VDU的工具,在对所述对VNF进行实例化的请求进行处理的过程中,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,自动计算出当前请求实例化的VNF实例的VNFC及其VDU。
  14. 根据权利要求12所述的VNFM,其中,所述处理器是设置为:为所述待实例化的VNF分配资源,接收由经过认证的网元EM发起或由网络功能虚拟化编排器NFVO发起的实例化VNF请求后,调用自动计算VDU的工具,结合待实例化的VNF的容量及其信息,计算出当前请求实例化的VNF实例的VNFC及其VDU,之后向NFVO发起实例化VNF请求。
  15. 一种网络功能虚拟化编排器NFVO,包括获取模块和发送模块,其中,
    所述获取模块,设置为在对虚拟网络功能描述VNFD进行注册过程中,获取并保存自动计算VDU的工具;
    所述发送模块,设置为当由所述NFVO负责分配资源的VNF实例化时,在NFVO向VNFM请求对VNF进行实例化时,将自动计算VDU的工具携带在请求中传递给VNFM。
  16. 根据权利要求15所述的NFVO,其中,所述获取模块是设置为:在接收来自用户的携带有自动计算VDU的插件的VNF版本包;在数据库中登记VNFD的同时,将获得的自动计算VDU的插件保存到数据库中。
  17. 一种计算机可读存储介质,存储有程序指令,当该程序指令被执行时可实现权利要求1-6任一项所述的方法。
PCT/CN2015/079839 2014-11-04 2015-05-26 实现vnf实例化的方法、系统及nfvo和vnfm WO2016070609A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410612825.9 2014-11-04
CN201410612825.9A CN105634778B (zh) 2014-11-04 2014-11-04 实现vnf实例化的方法、系统及nfvo和vnfm

Publications (1)

Publication Number Publication Date
WO2016070609A1 true WO2016070609A1 (zh) 2016-05-12

Family

ID=55908502

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/079839 WO2016070609A1 (zh) 2014-11-04 2015-05-26 实现vnf实例化的方法、系统及nfvo和vnfm

Country Status (2)

Country Link
CN (1) CN105634778B (zh)
WO (1) WO2016070609A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018024059A1 (zh) * 2016-08-05 2018-02-08 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置
CN108132827A (zh) * 2016-11-30 2018-06-08 华为技术有限公司 一种网络切片资源映射方法、相关设备及系统
CN109428874A (zh) * 2017-08-31 2019-03-05 华为技术有限公司 基于服务化架构的注册方法及装置
EP4109251A4 (en) * 2020-03-18 2023-08-09 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR INSTANCIATING VNF

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786360A (zh) * 2016-08-30 2018-03-09 中兴通讯股份有限公司 网络功能虚拟化管理方法及装置
CN108011733B (zh) * 2016-10-27 2021-04-16 上海中兴软件有限责任公司 一种插件的实现方法和装置
CN108243205B (zh) * 2016-12-23 2021-06-08 上海诺基亚贝尔股份有限公司 一种用于控制云平台资源分配的方法、设备与系统
CN109495529B (zh) * 2017-09-12 2022-04-12 华为技术有限公司 业务处理方法、第一设备及第二设备
CN109784085B (zh) * 2017-11-15 2023-10-27 中兴通讯股份有限公司 虚拟网络应用实现方法及管理系统、计算机可读存储介质
CN112242918B (zh) * 2019-07-19 2023-03-24 中兴通讯股份有限公司 Vnfd多版本兼容处理方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120072481A1 (en) * 2010-09-21 2012-03-22 Vishwamitra Nandlall Cloud phone with distributed processing
CN102857363A (zh) * 2012-05-04 2013-01-02 运软网络科技(上海)有限公司 一种虚拟网络的自主管理系统和方法
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100440797C (zh) * 2005-05-18 2008-12-03 中兴通讯股份有限公司 一种h.323网守实现h.323终端及时注册的方法
DE112006003589B4 (de) * 2005-12-31 2019-07-18 General Motors Llc ( N. D. Ges. D. Staates Delaware ) Verfahren zum Bereitstellen einer Fahrzeuginformation durch eine Fahrzeug-Email-Benachrichtigung unter Verwendung von Daten von verschiedenen Quellen
CN103838871B (zh) * 2014-03-21 2019-11-29 北京广利核系统工程有限公司 一种核电站安全级dcs s-vdu过程文件的校验方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120072481A1 (en) * 2010-09-21 2012-03-22 Vishwamitra Nandlall Cloud phone with distributed processing
CN102857363A (zh) * 2012-05-04 2013-01-02 运软网络科技(上海)有限公司 一种虚拟网络的自主管理系统和方法
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CUI, CHUNFENG; ET AL.: "Network Functions Virtualization: How Far Away from the Telecom Operators?", COMMUNICATIONS WORLD, 25 October 2013 (2013-10-25), pages 25 - 27 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018024059A1 (zh) * 2016-08-05 2018-02-08 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置
US10700928B2 (en) 2016-08-05 2020-06-30 Huawei Technologies Co., Ltd. Method and apparatus for deploying service in virtualized network
CN108132827A (zh) * 2016-11-30 2018-06-08 华为技术有限公司 一种网络切片资源映射方法、相关设备及系统
CN109428874A (zh) * 2017-08-31 2019-03-05 华为技术有限公司 基于服务化架构的注册方法及装置
CN109428874B (zh) * 2017-08-31 2020-10-09 华为技术有限公司 基于服务化架构的注册方法及装置
US11496320B2 (en) 2017-08-31 2022-11-08 Huawei Technologies Co., Ltd. Registration method and apparatus based on service-based architecture
EP4109251A4 (en) * 2020-03-18 2023-08-09 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR INSTANCIATING VNF
US11888696B2 (en) 2020-03-18 2024-01-30 Huawei Technologies Co., Ltd. VNF instantiation method and apparatus

Also Published As

Publication number Publication date
CN105634778B (zh) 2020-09-22
CN105634778A (zh) 2016-06-01

Similar Documents

Publication Publication Date Title
WO2016070609A1 (zh) 实现vnf实例化的方法、系统及nfvo和vnfm
US10523529B2 (en) Method and apparatus for deploying network service
US11272036B2 (en) API hybrid multi-tenant routing method and system, and API gateway
US10701139B2 (en) Life cycle management method and apparatus
US10944621B2 (en) Orchestrator for a virtual network platform as a service (VNPAAS)
US10298439B2 (en) Network functions virtualization network system and data processing method, and apparatus
US9307017B2 (en) Member-oriented hybrid cloud operating system architecture and communication method thereof
US10567196B2 (en) Decision coordination method, execution apparatus, and decision coordinator
EP3471342A1 (en) Method and device for service deployment in virtualized network
WO2019029327A1 (zh) 网络功能服务的发现方法及设备
JP6190949B2 (ja) 仮想ネットワーク機能マネージャによる仮想インフラストラクチャマネージャへのアクセスの自動化構成
WO2018006676A1 (zh) 加速资源处理方法、装置及网络功能虚拟化系统
US11687354B2 (en) Virtual machine management using onboarding operations and openstack control
RU2683630C2 (ru) Способ обновления дескриптора сетевой службы nsd и устройство
WO2016037479A1 (zh) 虚拟化网络功能vnf优化方法、装置及系统
WO2018145615A1 (zh) 一种部署vnf的方法和系统
WO2015113234A1 (zh) 网络功能虚拟化的方法及装置
US11301284B2 (en) Method for managing VNF instantiation and device
WO2013152565A1 (zh) 能力聚合开放的方法和系统
WO2017041562A1 (zh) 一种识别终端设备用户身份的方法和装置
US20170338968A1 (en) Certificate Management Method, Device, and System
US20180062946A1 (en) Method and Apparatus for Establishing Network Service Instance
WO2018000394A1 (zh) 网络资源的编排方法和设备
WO2018153354A1 (zh) 一种资源申请、vnf实例创建方法及装置
WO2015192556A1 (zh) 云调度管理方法、管理中心及管理系统

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: 15857297

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: 15857297

Country of ref document: EP

Kind code of ref document: A1