[go: up one dir, main page]

WO2018024059A1 - 一种虚拟化网络中业务部署的方法和装置 - Google Patents

一种虚拟化网络中业务部署的方法和装置 Download PDF

Info

Publication number
WO2018024059A1
WO2018024059A1 PCT/CN2017/090891 CN2017090891W WO2018024059A1 WO 2018024059 A1 WO2018024059 A1 WO 2018024059A1 CN 2017090891 W CN2017090891 W CN 2017090891W WO 2018024059 A1 WO2018024059 A1 WO 2018024059A1
Authority
WO
WIPO (PCT)
Prior art keywords
deployment
node
information
identifier
preference
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/090891
Other languages
English (en)
French (fr)
Inventor
李世涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP17836241.4A priority Critical patent/EP3471342A4/en
Publication of WO2018024059A1 publication Critical patent/WO2018024059A1/zh
Priority to US16/244,592 priority patent/US10700928B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5045—Making service definitions prior to deployment

Definitions

  • the present invention relates to the field of information technology, and in particular, to a method and apparatus for service deployment in a virtualized network.
  • Network Function Virtualization refers to the use of common hardware devices and virtualization technologies to carry the functions of dedicated devices in traditional networks, thereby reducing the expensive cost of deploying dedicated devices.
  • the software is not tied to proprietary hardware, making network device functionality no longer dependent on dedicated hardware.
  • the characteristics of cloud computing are utilized, so that resources can be fully and flexibly shared, real-time development and deployment of new services, and automatic deployment, elastic scaling, fault isolation, and self-healing based on actual business requirements.
  • the party that receives the instantiation request and instantiates the corresponding service according to the request is called a virtualization service provider (referred to as a service provider), and the party that initiates the instantiation request is called Business requester.
  • the Virtualized Network Service (NS) in NFV can be an IP Multimedia Subsystem (IMS) network service or an Evolved Packet Core (EPC) service.
  • An NS can contain several virtualized network function (VNF) modules, also called virtualized network elements.
  • VNF virtualized network function
  • the service requester first needs to submit the network service descriptor (NSD) to the service provider.
  • NSD network service descriptor
  • the description of the network service is also called the NS deployment template, which mainly includes describing the network.
  • the virtual link descriptor is used in the topology information to describe the connection between the VNFs.
  • the VNFD is a VNF description information, which is also called a VNF deployment template, and includes a Virtual Deployment Deployment Unit (VDU) included in the VNF to be described, a connection point CP (connection point), and a virtual connection VL (virtual link). And other information.
  • the VDU can represent the virtual machine on which the application software is installed.
  • the description of the VDU includes the VDU description of the virtual resource of the virtual machine.
  • the CP represents the connection information on the virtual machine. For example, the virtual network card information can be used.
  • the address or MAC address indicates that VL is a virtual connection connecting multiple VDUs in the VNF, and can be represented by information such as bandwidth and QoS.
  • VNFD The VNF deployment template in the prior art can be described by the YAML (Yet Another Markup Language) model defined by the TOSCA standard.
  • YAML Yet Another Markup Language
  • TOSCA service template can be used to describe the VNFD, exemplary.
  • a deployment template for a router VNF a deployment template for a router VNF:
  • the VNF described in the code (1) includes three VDUs of VDU1, VDU2, and VDU3, and six CPs of CP1-CP6, and two VLs of VL1 and VL2.
  • CP1 contains the code virtualbinding: VDU1 and virtualLink: VL1 indicates that CP1 is attached to VDU1 and is connected to VL1.
  • CP2 contains the code virtualbinding: VDU1 and virtualLink: VL2, indicating that CP2 is attached to VDU1 and connected to VL2.
  • the code contained in CP3 indicates that CP3 is attached to VDU2 and is connected to VL1.
  • the code contained in CP4 indicates that CP4 is attached to VDU2.
  • the code contained in CP5 indicates that CP5 is attached to VDU3 and is connected to VL2.
  • the code contained in CP6 indicates that CP6 is attached to VDU3.
  • the code virtualLink: [CP4, virtualLink] and virtualLink: [CP6, virtualLink] indicate that CP4 and CP6 are connected to the external network as the external connection point of the VNF.
  • the router instance described above may include two deployment methods in the VNFD, where the first deployment method includes VDU1, VDU2, and VL1; and the second deployment method includes VDU1, VDU2, VDU3, VL1, and VL2; Can be a firewall module.
  • the first deployment method includes VDU1, VDU2, and VL1
  • the second deployment method includes VDU1, VDU2, VDU3, VL1, and VL2
  • Can be a firewall module When the router VNF is deployed on the internal network, you can choose to deploy it according to the first deployment method, that is, the firewall module VDU3 is not required.
  • the router VNF is deployed at the edge of the network, it needs to be deployed according to the second deployment method.
  • the first deployment method and the second deployment method deployment example are shown in Figure 2(a) and Figure 2(b).
  • the invention provides a method and a device for deploying a service in a virtualized network, so as to solve the business requirement that a service template in the prior art cannot support multiple deployment preferences.
  • an embodiment of the present invention provides a method for deploying a service in a virtual network, including: a virtual network function manager receiving an instantiation request, where the instantiation request includes a VNF instance identifier and a first deployment preference identifier; acquiring and a VNF The instance identifies the corresponding VNF deployment template VNFD.
  • the embodiments of the present invention extend the content included in the VNFD.
  • the VNFD includes description information of at least two potential deployment nodes and at least two deployment preference description information; wherein the description information of each potential deployment node includes node information of the potential deployment node and deployment conditions, and each deployment preference The description information includes deployment information of the node that needs to be deployed corresponding to the deployment preference.
  • the virtual network function manager determines, according to the first deployment preference identifier in the instantiation request and the VNFD, node information and deployment information of the node to be deployed corresponding to the first deployment preference identifier, and then determines the node of the node that needs to be deployed. Information and deployment information is sent to the Virtual Infrastructure Manager for instantiation by the Virtual Infrastructure Manager.
  • the deployment preference description information is extended in the VNFD, and specifically, the nodes and deployment information that need to be deployed in different deployment preferences are defined, and the deployment preference identifier is added in the instantiation request.
  • the VNFM receives the instantiation request, it determines the node to be deployed according to the deployment preference identifier in the instantiation request.
  • the deployment information is sent to the VIM for instantiation, which enables the same VNFD to support multiple deployment preferences and provides a more flexible service deployment method.
  • the deployment condition includes a deployment identifier
  • the virtual network function manager determines, according to the first deployment preference identifier and the VNFD, a node of the node that needs to be deployed corresponding to the first deployment preference identifier.
  • the information and the deployment information are specifically: comparing the first deployment preference identifier with the deployment identifier of the deployment condition of the potential deployment node for the description information of each potential node; when the first deployment preference identifier and the potential deployment When the deployment identifier of the node is matched, the deployment identifier is determined to be the node that needs to be deployed; the node information of the node to be deployed is acquired; and the deployment corresponding to the first deployment preference identifier in the VNFD is obtained.
  • the description information is preferred; the deployment preference information corresponding to the first deployment preference identifier is determined, and the deployment information of the node to be deployed is determined.
  • the first deployment preference identifier matches the deployment identifier included in the deployment condition of the potential deployment node, where the deployment condition of the potential deployment node includes the same deployment identifier as the first deployment preference identifier; or
  • the deployment condition of the potential deployment node includes the deployment identifier including the first deployment preference identifier; or the deployment condition of the potential deployment node includes a deployment identifier of null (any deployment preference satisfies the deployment condition of the potential deployment node).
  • the embodiment of the present invention increases the deployment condition of the node, and compares the deployment preference with the deployment preference identifier in the instantiation request to determine whether the node needs to be deployed, thereby implementing flexible deployment of the service according to the VNFD. Demand.
  • the network function virtualization orchestrator receives a registration request sent by the sender, and the registration request includes a VNF deployment package.
  • the VNF deployment package includes a VNFD.
  • the VNF deployment package further includes an image file and/or a security certificate.
  • the network function virtualization orchestrator saves the deployment package in the registration request, and returns a response message of successful registration to the sender; the network function virtualization orchestrator receives the request for creating the VNF instance identifier sent by the initiator, and creates a request for the VNF instance identifier.
  • the virtual network function manager Forwarding to the virtual network function manager; the virtual network function manager generates the VNF instance identifier, and sends the VNF instance identifier to the network function virtualization orchestrator; the network function virtualization orchestrator establishes the VNF locally Corresponding relationship between the instance identifier and the deployment package information, and returning the VNF instance identifier to the initiator.
  • the virtual network function manager can update the current VNF deployment preferences according to operational requirements. Specifically, the virtual network function manager receives the update deployment preference request, where the update deployment preference request includes the VNF instance identifier and the second deployment preference identifier; and the VNFD is obtained according to the VNF instance identifier; according to the first deployment Demystifying the identifier, the second deployment preference identifier, and the VNFD, determining node information and deployment information of the node that needs to be updated; sending the determined node information and deployment information of the node that needs to be updated to the virtual infrastructure management In order to facilitate the instantiation of the virtual infrastructure manager.
  • the embodiments of the present invention implement different service deployments by using the same deployment template, improve the flexibility of virtualized service deployment, and save deployment template resources. Compared with the prior art, a plurality of deployment templates are required to implement different service deployments, and the method of the embodiment of the present invention can reduce the time of interruption of existing services when the deployment is performed.
  • an embodiment of the present invention provides a device for deploying a service in a virtual network, where the device for deploying a service has a function of implementing the behavior of the virtual network function manager in the foregoing first aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the device for deploying services in the virtual network includes a processor and a memory for storing a program supporting the device deploying the service in the virtual network to execute the foregoing method, the processor being Configured to execute a program stored in the memory.
  • the device deploying the service in the virtual network may further include a communication interface, and the device for deploying the service in the virtual network communicates with other devices or the communication network.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for a device for deploying services in the virtual network, where the device includes instructions for performing the foregoing aspects of deploying services in a virtual network. Designed program.
  • the node in the foregoing aspect includes a virtual deployment unit (VDU) or a virtual connection VL.
  • the deployment information includes an elastic scaling parameter of the VDU or a quality of service parameter of the VL.
  • the solution provided by the present invention can implement a VNFD to support multiple deployment preferences, and provides a more flexible service deployment method.
  • the initiator since different deployment methods are based on the same deployment template, the initiator does not need to repeatedly register on the NFVO.
  • the VNFM does not need to obtain multiple deployment templates from the NFVO, which simplifies the complexity of service deployment.
  • FIG. 1 is a diagram showing an example of a deployment template of a VNF obtained by VNFD according to code (1);
  • Figure 2 (a) is an example diagram of deployment in accordance with the first deployment method
  • Figure 2(b) is a diagram showing an example of deployment in accordance with a second deployment method
  • FIG. 3 is a network architecture diagram of network function virtualization according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for deploying a service in a virtual network according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a method for switching between different deployment preferences according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a virtual infrastructure manager according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of an NFV system 300 for performing service deployment in a virtualized network according to an embodiment of the present invention.
  • an architectural diagram provided by an embodiment of the present invention includes the following functional components:
  • the network function virtualization orchestrator (NFVO) 302 is mainly responsible for processing the lifecycle management of the virtualized service and the allocation and scheduling of the virtual resources in the virtual infrastructure NFVI.
  • the NFVO 302 can communicate with one or more Virtualized Network Function Managers (VNFMs) 304 to perform resource related requests, send configuration information to the VNFM 304, and collect status information for the VNF 308.
  • VNFMs Virtualized Network Function Managers
  • NFVO 302 can also communicate with Virtualized Infrastructure Manager (VIM) 306, perform resource allocation and/or reservations, and exchange virtualized hardware resource configuration and status information.
  • VIP Virtualized Infrastructure Manager
  • the Virtual Network Function Manager (VNFM) 304 is responsible for lifecycle management of one or more VNFs, such as instantiating, updating, querying, scaling, and terminating the VNF 308.
  • the VNFM 304 can communicate with the VNF 308 to complete VNF lifecycle management and exchange configuration and status information.
  • the NFVO 302 may determine different VNFMs 304 for different VNF 308 selections depending on the type of service the VNFM is responsible for.
  • Virtual Infrastructure Manager (VIM) 306 controls and manages the interaction of VNF 308 with computing hardware 312, storage hardware 314, network hardware 316, virtual computing 318, virtual storage 320, virtual network 322.
  • the VIM 306 performs resource management functions, including managing the allocation of infrastructure resources (eg, adding or subtracting resources to virtual containers) and running functions (eg, collecting NFVI failure information).
  • VNFM 304 and VIM 306 can communicate with one another to request resource allocation.
  • Network functions virtualization infrastructure the infrastructure layer of NFV, consists of hardware components, software components, or a combination of both to establish a virtualized environment, deploy, manage, and implement VNF 308.
  • Hardware resources and virtualization layers are used to provide virtualized resources for VNF 308, such as virtual machine VMs and other forms of virtual containers.
  • Hardware resources include computing hardware 312, storage hardware 314, and network hardware 316.
  • the resources of computing hardware 312 and storage hardware 314 may be pooled together.
  • the virtualization layer in NFVI abstracts hardware resources and decouples VNF 308 from the underlying physical network layer.
  • Virtualized resources include virtual computing 318 (eg, virtual machines, VMs), virtual storage 320, and virtual network 322.
  • Virtual computing 318 and virtual storage 320 are provided to VNF 308 in the form of virtual machines, and/or other virtual containers, by a hypervisor (hypervisor or container runtime). For example, one or more VNFs 308 can be deployed on one VM.
  • a plurality of virtualized network functions (VNFs) 308 are configured to virtualize at least one network function.
  • the VNF 308 may be a virtualization provider edge (PE) node for providing all PE network functions on a non-virtualized PE device, such as a router, a switch, a bridge, and a server. , cloud computing systems, etc.
  • PE virtualization provider edge
  • Each VNF runs in one or more virtual containers, corresponding to a set of network functions belonging to one or more physical devices.
  • the Equipment Management System (EM) 310 is a system for configuring and managing devices in a conventional telecommunication system. In the NFV architecture, the EM 310 can also be used to configure and manage the VNF, and initiate a new VNF to the VNFM 304. Instantiation and other lifecycle management operations.
  • the Operations Support System and Business Support System (OSS/BSS) 324 supports a variety of end-to-end telecommunications services.
  • the management functions supported by OSS include: network configuration, service provision, and fault management.
  • BSS handles orders, payments, revenues, etc., supporting product management, order management, revenue management and customer management.
  • the OSS/BSS 324 can be used as the initiator of the virtualization service, and is mainly used to request the deployment of the virtualized service and the lifecycle management of the virtualized service to the NFV system through the interface opened by the NFV system.
  • the VNFM after receiving the instantiation request, obtains the deployment template VNFD of the VNF from the NFVO according to the VNF instance identifier in the instantiation request; wherein the VNFD includes description information of at least two potential deployment nodes and at least two Deploying preference description information, and description information of each potential deployment node in the description information of the at least two potential deployment nodes includes an identifier of the potential deployment node, node information, and deployment conditions, and the at least two deployment preference description information
  • Each of the deployment preference description information includes a node identifier and deployment information of the node to be deployed corresponding to the deployment preference; the VNFM determines the node to be deployed corresponding to the deployment preference identifier in the instantiation request according to the deployment preference identifier and the VNFD. Node information and deployment information; sending the determined node information and deployment information of the node to be deployed to the virtual infrastructure manager VIM, so that the VIM can be instantiated, thereby implementing different deployments according
  • the code (2) introduces a VNF deployment template, which can be used to implement the deployment plan of the example diagrams shown in FIG. 2(a) and FIG. 2(b) according to the deployment template. It is to be noted that the code (2) only lists the content related to the embodiment of the present invention, and the rest of the content is the prior art, and the embodiment of the present invention is not limited.
  • the embodiment of the present invention can be implemented by using the TOSCA model.
  • the code (2) is partially extended with respect to the prior art code (1).
  • the definition of the deployment preference DF is added in the DSL_definitions section.
  • the definition of each DF includes VDU, VL and external connection point information to be deployed, and the external connection point information is used to indicate which connection points the VNF connects with the external network.
  • DF1 in VNFD includes VDU1, VDU2 and VL1, and codes External_CP_1: CP4 and External_CP_2: CP2 indicate that in DF1, CP2 and CP4 are used as external link points.
  • VDU1 in DF1 contains VDU1, VDU2, VDU3, VL1 and VL2, and codes External_CP_1: CP4 and External_CP_2: CP6 indicate that in DF2, CP4 and CP6 are used as external connection points.
  • the VDU that needs to be deployed in the DF also contains deployment information.
  • the VDU1 in DF1 has a scalable parameter, where the codes min_instances:3 and max_instances:10 define the minimum number of instantiations to be 3, and the maximum number of instantiations. Is 10.
  • VL1 in DF1 contains the Quality of Service (QoS) parameters during deployment, where the latency is 10ms and the Delay is 20ms.
  • QoS Quality of Service
  • the deployment information of the node that needs to be deployed in the DF may also be any information that needs to be used when the node is deployed.
  • the scalability parameter and the QoS parameter are just exemplary. The content is not limited.
  • the embodiment of the present invention extends the description of the alternative mapping portion (subsititution_mappings) in the VNFD to select an external connection point according to deployment preferences.
  • the get_DSL:[(get_input:deployment_flavour),External_CP_1] operation is used to flexibly select corresponding external link points according to different DFs, wherein get_DSL is used to obtain the value of a parameter from DSL_definitions, and the parameter get_input:deployment_flavour is used for
  • the input value of the deployment_flavour is determined by the deployment preference identifier in the VNF instantiation request, for example, may be DF1 or DF2.
  • the parameter External_CP_1 in get_DSL is used to indicate the value of the specific parameter to be acquired.
  • “External_CP_1” indicates that the value of External_CP_1 is obtained.
  • the get_DSL:[(get_input:deployment_flavour),External_CP_1] operation the obtained values are all CP4.
  • the node template (node_templates) part in the VNFD includes description information of nodes such as VDU, VL, and CP in the VNF, including the identifier of the node, the node information, and the deployment condition of the node.
  • a deploy_dependsOnDF parameter is added in each node description, which is used to indicate the deployment condition of the node.
  • the deployment condition may be an identifier of the deployment preference.
  • the code deploy_dependsOnDF: [DF1, DF2] indicates that VDU1 needs to be deployed when the deployment value of deployment_flavour is DF1 or DF2.
  • the code deploy_dependsOnDF:[DF2] means that VDU3 needs to be deployed when the deployment value of deployment_flavour is DF2, and VDU3 is not required when the deployment preference value is DF1.
  • the assignment of some parameters also uses the get_DSL operation, which is used to obtain the corresponding deployment information from the specified deployment preference description information.
  • VDU1 [get_DSL:(get_input:deployment_flavour), VDU1,scalable], which means to obtain the assignment of the scalable parameter in VDU1 from DF1 in DSL_definitions, ie min_instances:3; max_instances:10; QoS in VL1: [get_DSL:(get_input: Deployment_flavour), VL1, QoS]] indicates that the assignment of the QoS parameter of VL1 is obtained from DF1 defined in DSL_definitions.
  • the node It also includes the node information of the node, such as num_cpus in VDU1: ⁇ equal:2 ⁇ , mem_size: ⁇ greater_or_equal: 3GB ⁇ , which is used to indicate the performance requirement of the VDU1 for the virtual machine when deploying VDU1 (2 performance indicators of the CPU, 3GB of RAM).
  • the node information and the deployment information of a node together constitute the information that is needed when the node is deployed, but the node information is used to indicate the information that needs to be used when the node is deployed, and the required information is needed. The information does not change with the deployment preferences.
  • VDU1 when deploying according to DF1 and DF2, VDU1 needs to be deployed, and when deploying VDU1, VDU1 has the same performance requirement for virtual machines (2) The performance of the CPU, 3GB of memory), therefore, the VDU1 performance requirements of the virtual machine can be saved in the node template as the node information of the VDU1 when the VDU1 is deployed.
  • the virtual network function manager VNFM in FIG. 3 can be implemented in the manner of the computer device (or system) in FIG.
  • FIG. 4 is a schematic diagram of a computer device according to an embodiment of the present invention.
  • Computer device 400 includes at least one processor 401, a communication bus 402, a memory 403, and at least one communication interface 404.
  • the processor 401 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 402 can include a path for communicating information between the components described above.
  • the communication interface 504 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently and be connected to the processor via a bus.
  • the memory can also be integrated with the processor.
  • the memory 403 is used to store program code for executing the solution of the present invention, and is controlled by the processor 401 for execution.
  • the processor 401 is configured to execute program code stored in the memory 403.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • computer device 400 can include multiple processors, such as processor 401 and processor 408 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 400 may also include an output device 405 and an input device 406.
  • Output device 405 is in communication with processor 401 and can display information in a variety of ways.
  • the output device 405 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 406 is in communication with processor 401 and can accept user input in a variety of ways.
  • input device 406 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device 400 described above can be a general purpose computer device or a special purpose computer device.
  • the computer device 400 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet, a wireless terminal device, a communication device, an embedded device, or have the following FIG. A device of similar structure.
  • Embodiments of the invention do not limit the type of computer device 400.
  • the virtual network function manager in FIG. 3 may be the device shown in FIG. 4, and one or more software modules are stored in the memory of the virtual network function manager.
  • the virtual network function manager can realize the software modules through the processor and the program code in the memory, and realize different deployment according to the same VNFD.
  • FIG. 5 is a flowchart of a method for deploying a service in a virtual network according to an embodiment of the present invention, including the following steps:
  • Step 501 The initiating direction NFVO sends a registration request for registering the deployment package of the VNF.
  • the VNF deployment package includes a VNFD.
  • the VNF deployment package further includes an image file and/or a security certificate. Except for VNFD, files not related to the present invention will not be described herein.
  • the initiator may be an OSS/BSS 324.
  • the OSS/BSS 324 sends a registration request to the NFVO through an interface open by the NFV system, and the registration request may specifically be an on-boarding request, and the registration request includes the VNF deployment package.
  • the VNFD in the embodiment of the present invention includes description information of at least two potential deployment nodes and at least two deployment preference description information, where each of the description information of the at least two potential deployment nodes is potential deployment
  • the description information of the node includes the identifier of the potential deployment node, the node information, and the deployment condition, and each of the at least two deployment preference description information includes the node identifier and the deployment of the node that needs to be deployed corresponding to the deployment preference. information.
  • the potential deployment node may be a virtual deployment unit VDU or a virtual connection VL, such as VDU1, VDU2, VDU3, VL1 or VL2 in code (2).
  • the deployment information includes an elastic scaling parameter of the VDU or a QoS parameter of the VL.
  • Step 502 The NFVO receives the registration request sent by the initiator, saves the deployment package in the registration request, and returns a response message of successful registration.
  • the response message of the registration success includes deployment package information.
  • the deployment package information may be an identifier of the deployment package, or a set of parameters that can uniquely determine a deployment package.
  • the deployment package information and the corresponding deployment package have a one-to-one correspondence, and the present invention provides a deployment package.
  • the specific form of the information is not limited.
  • Step 503 The initiator receives the response message of the registration success returned by the NFVO, and sends a request for creating the VNF instance identifier to the NFVO.
  • the request for creating the VNF instance identifier includes deployment package information.
  • Step 504 The NFVO receives the request for creating the VNF instance identifier sent by the initiator, and forwards the request for creating the VNF instance identifier to the VNFM.
  • Step 505 The VNFM receives the request for creating the VNF instance identifier sent by the NFVO, generates a VNF instance identifier, and sends the generated VNF instance identifier to the NFVO.
  • VNFM generates a locally unique string that generates a VNF instance identifier based on the address of the VNFM in the NFV system and the string; or VNFM generates a string that is globally unique in the NFV system. Generate a VNF instance ID based on the globally unique string.
  • Step 506 The NFVO receives the VNF instance identifier returned by the VNFM, and establishes the VNF instance identifier and the deployment locally. Corresponding relationship of the packet information, and returning the VNF instance identifier to the initiator.
  • Step 507 The initiator receives the VNF instance identifier returned by the NFVO, and sends a VNF instantiation request to the NFVO.
  • the VNF instantiation request includes the VNF instance identifier and the first deployment preference identifier DF1.
  • Step 508 The NFVO receives the VNF instantiation request sent by the initiator, and forwards the VNF instantiation request to the VNFM.
  • Step 509 The VNFM receives the VNF instantiation request sent by the NFVO, and sends a request for acquiring the deployment package to the NFVO.
  • the request for obtaining the VNF deployment package includes the VNF instance identifier.
  • Step 510 The NFVO receives the request for obtaining the deployment package sent by the VNFM, obtains the deployment package corresponding to the VNF instance identifier, and returns the obtained deployment package to the VNFM.
  • the NFVO obtains the deployment package information corresponding to the VNF instance identifier in the corresponding relationship between the VNF instance identifier and the deployment package information, and the VNF instance identifier is obtained according to the VNF instance identifier.
  • Step 511 The VNFM receives the deployment package returned by the NFVO, and determines the node information of the VDU node that needs to be instantiated in the VNFD in the deployment package, and obtains the deployment information of the VDU node according to the deployment preference description information corresponding to the first deployment preference identifier. .
  • the node information of the VDU node is the same deployment parameter used in the VNFD to characterize the VDU node according to different deployment preferences, such as the CPU and Memory described in the requirements section of the VDU1 node in the code (2). information.
  • the node information of the VDU node may also be described in the deployment preference description information, where the node information may be part of the deployment information; when the node information of the VDU node is part of the deployment information, The VDU instantiation request may only include deployment information of the VDU node.
  • the VDU node For the description information of each VDU node in the VNFD, compare the first deployment preference identifier DF1 with a deployment identifier included in the deployment condition of the VDU node; when the first deployment preference identifier and the VDU node If the deployment identifier includes the matching of the deployment identifiers, the VDU node is determined to be a node to be deployed; the node information of the VDU node is obtained; and the deployment preference description information corresponding to the first deployment preference identifier in the VNFD is obtained; The first deployment preference identifies the corresponding deployment preference description information, and determines deployment information of the VDU node.
  • the first deployment preference identifier is matched with the deployment identifier included in the deployment condition of the VDU node, where the deployment condition of the VDU node includes the same deployment identifier as the first deployment preference identifier; or the VDU node
  • the deployment identifier includes the deployment identifier including the first deployment preference identifier; or the deployment condition of the VDU node includes a deployment identifier of null (any deployment preference satisfies the deployment condition of the VDU node).
  • the VNFM obtains the node information of the VDU, such as the performance requirement of the virtual machine when deploying the VDU1 (2 performance indicators of the CPU, 3 GB of memory).
  • the scalable parameter of VDU1 is obtained from DF1 in the DSL_definitions of the VNFD.
  • Step 512 The VNFM sends a VDU instantiation request to the VIM, where the VDU instantiation request includes node information and deployment information of the VDU node.
  • Step 513 The VIM receives the VDU instantiation request sent by the VNFM, and creates a virtual machine according to the deployment information in the VDU instantiation request, and returns a successful instantiation response to the VNFM.
  • VIM instantiating the VDU according to the node information and the deployment information is a technique well known to those skilled in the art, and the embodiment of the present invention does not. Let me repeat.
  • Step 514 The VNFM determines the VL node that needs to be instantiated in the VNFD in the deployment package, and obtains the node information and deployment information of the VL node according to the deployment preference description information corresponding to the first deployment preference identifier.
  • the deployment information of the VL node includes a QoS parameter of the VL, and the node information of the VL node includes connection point information corresponding to the VL node.
  • the connection point information corresponding to the VL node is used to indicate which connection point the VL node connects to other nodes.
  • the VL node for each VL node in the VNFD, comparing the first deployment preference identifier with a deployment identifier included in a deployment condition of the VL node; when the first deployment preference identifier and the deployment condition of the VL node include When the deployment identifiers match, the VL node is determined to be a node to be deployed; the node information of the VL node is obtained; and the deployment preference description information corresponding to the first deployment preference identifier in the VNF deployment package is obtained; The first deployment preference identifier corresponds to the deployment preference description information, and the deployment information of the VL node is determined.
  • the first deployment preference identifier is matched with the deployment identifier included in the deployment condition of the VL node, specifically, the deployment identifier of the VL node includes the same deployment identifier as the first deployment preference identifier; or the VL node
  • the deployment identifier includes the deployment identifier including the first deployment preference identifier; or the deployment condition of the VL node includes a deployment identifier of null (any deployment preference satisfies the deployment condition of the VL node).
  • the VNF needs to be deployed when the VNF is instantiated.
  • the VNFM obtains the node information of the VL1, such as the connection point information of the VL1 (via the CP1 on the VDU1 and the CP3 on the VDU2, and connects the VDU1 node and the VDU2 node).
  • VL1 [get_DSL: (get_input: deployment_flavour), VL1, QoS]]
  • the QoS parameter of VL1 is obtained from DF1 in DSL_definitions in VNFD.
  • connection point information corresponding to the VL node to be deployed needs to be obtained.
  • VNFM passes the code in node_templates in VNFD:
  • the node VL1 establishes a connection with the VDU1 through the connection point CP1, and establishes a connection with the VDU2 through the connection point CP3, that is, VL1 establishes a connection between the VDU1 and the VDU2 through the connection point CP1 on the VDU1 and the connection point CP3 on the VDU2.
  • Step 515 The VNFM sends a VL instantiation request to the VIM, where the VL instantiation request includes node information and deployment information of the VL node.
  • Step 516 The VIM receives the VL instantiation request sent by the VNFM, and creates a VL instance according to the node information and the deployment information of the VL node in the VL instantiation request, and returns a successful instantiation response to the VNFM.
  • VIM instantiating the VL according to the node information and the deployment information is a technique well known to those skilled in the art, and the embodiment of the present invention does not. Let me repeat.
  • Step 517 The VNFM obtains the external connection point information according to the deployment preference description information corresponding to the first deployment preference identifier.
  • the connection point corresponding to the external connection point External_CP_1 in DF1 is CP4, and the connection point corresponding to the external connection point External_CP_2 is CP2, and the external network corresponding to the connection between CP4 and CP2 is requested from the VIM.
  • Step 518 The VNFM sends an external connection point instantiation request to the VIM.
  • the external connection point instantiation request includes external connection point information.
  • Step 519 The VIM receives the external connection point instantiation request sent by the VNFM, connects to the external network by using the external connection point information, and returns a successful instantiation response to the VNFM.
  • steps 517-519 are not necessary. In particular, when the deployed VNF does not need to be connected to an external network, steps 517-519 may be omitted.
  • Step 520 The VNFM receives the instantiation successful response returned by the VIM, and returns a response of the VNF instantiation success to the NFVO.
  • Step 521 The NFVO receives the successful response of the VNF instantiation returned by the VNFM, and returns a response of the VNF instantiation success to the sender.
  • the NFV system can maintain the current deployment preference information of each VNF instance on any entity in the NFV system after deploying the VNF instance according to the deployment preference identifier and the VNFD.
  • the current deployment preference information is used to indicate that the VNF instance is deployed according to which deployment preference in the VNFD.
  • NFVO is responsible for maintaining current deployment preferences for each VNF instance. Specifically, in step 508, after receiving the VNF instantiation request sent by the initiator, the NFVO saves the VNF instance identifier and the deployment preference identifier as a deployment record, and sets the state of the deployment record to be inactive. When in step 521, after receiving the instantiation successful response sent by the VNFM, the state of the deployment record is set to an active state (active); optionally, after receiving the response of the instantiation failure sent by the VNFM, Then delete the deployment record. When the NFVO receives the request for the current deployment preference information of the VNF sent by the NFVO, the NFVO can obtain the corresponding deployment preference identifier from the deployment record whose status is active according to the VNF instance identifier.
  • the VNFM is responsible for maintaining current deployment preferences for each VNF instance. Specifically, in step 509, after receiving the instantiation request sent by the NFVO, the VNFM saves the VNF instance identifier and the deployment preference as a deployment record, and sets the state of the deployment record to be inactive; After the instantiated successful response sent by the VIM, set the status of the deployment record to active. When the VNFM needs to query the current deployment preference information of the VNF, the VNF instance identifier can be queried from the deployment record whose status is active to obtain the corresponding deployment preference identifier.
  • the deployment preference description information is extended in the VNFD, and specifically, the nodes and deployment information that need to be deployed in different deployment preferences are defined, and the deployment preference identifier is added in the instantiation request.
  • the VNFM receives the instantiation request, it determines the node and the deployment information to be deployed according to the deployment preference identifier in the instantiation request, and sends the information to the VIM to perform the instantiation operation, so that the same VNFD can support multiple deployment preferences. Requirements provide a more flexible approach to business deployment.
  • the initiator since different deployment methods are based on the same deployment template, the initiator does not need to repeatedly register on the NFVO.
  • the VNFM does not need to obtain multiple deployment templates from the NFVO, which simplifies the complexity of service deployment.
  • FIG. 6 is a flowchart of a method for switching between different deployment preferences according to an embodiment of the present invention.
  • FIG. 6 is still exemplified by the VNFD described in code (2).
  • the system has instantiated the VNF according to DF1, and the embodiment method described in FIG. Update the VNF deployment preferences to DF2. specific,
  • Step 601 The initiating direction NFVO sends a request for updating the deployment preference.
  • the update deployment preference request includes the VNF instance identifier and the second deployment preference identifier that need to be updated.
  • the VNF instance that needs to be updated in this example is the VNF instantiated in the embodiment in FIG. 5, and the second deployment preference identifier. For DF2.
  • Step 602 The NFVO receives the update deployment preference request sent by the initiator, and sends the received update deployment preference request to the VNFM.
  • Step 603 The VNFM receives the update deployment preference request sent by the NFVO, and obtains the current deployment preference information of the VNF according to the VNF instance identifier in the update deployment preference request; the VNFM sends a request for acquiring the VNF deployment package to the NFVO.
  • the request for obtaining the VNF deployment package includes the VNF instance identifier that needs to be updated.
  • the VNFM can obtain the current deployment preference information of the VNF through different methods, which is not limited by the present invention.
  • the method in the embodiment described in FIG. 5 can be used to obtain current deployment preference information of the VNF.
  • the current deployment preference information of the VNF is the first deployment preference identifier, that is, DF1.
  • Step 604 The NFVO receives the request for obtaining the deployment package sent by the VNFM, acquires the deployment package corresponding to the VNF instance identifier, and returns the obtained deployment package to the VNFM.
  • Step 605 The VNFM determines node information, deployment information, and external connection point information that needs to be updated, according to the current deployment preference information of the VNF, the second deployment preference identifier, and the VNFD in the deployment package.
  • the VNFM determines the node and the external connection point information that need to be deployed corresponding to the second deployment preference identifier according to the second deployment preference identifier and the VNFD; according to the first deployment preference identifier and the VNFD, Determining, by the first deployment preference identifier, the node and the external connection point information that need to be deployed; determining the node that needs to be updated and the external connection point information that needs to be updated; acquiring the node information of the node that needs to be deployed; The deployment preference description information corresponding to the deployment identifier is determined, and the corresponding deployment information of the node that needs to be updated is determined.
  • the node that needs to be updated and deployed includes the node that needs to be added or deleted in relation to the first deployment preference.
  • the nodes that need to be deployed in the first deployment preference include VDU1, VDU2, and VL1, and the external connection point information is CP4 and CP2; the nodes that need to be deployed in the second deployment preference include VDU1, VDU2, VDU3, VL1, and VL2. And the external connection point information is CP4 and CP6. Therefore, the nodes that need to be updated are the newly added nodes VDU3 and VL2, and the external connection point information to be updated is CP6, that is, CP6 is used as an external connection point instead of CP2 to connect to the external network.
  • Step 606 The VNFM sends the determined node information of the node that needs to be updated, the deployment information, and the external connection point information that needs to be updated to the virtual infrastructure manager VIM, so that the VIM performs the instantiation operation.
  • the instantiation operation of the VIM according to the information sent by the VNFM is a technique well known to those skilled in the art, and details are not described herein again.
  • the VIM When the VIM needs to update the node information of the deployed node, the deployment information, and the external connection point information that needs to be updated according to the needs of the VNFM, the VIM returns a VNF instantiation success response to the VNFM.
  • the VNFM sends a response to the NFVO to update the deployment success, and the NFVO in turn forwards the response to the update deployment preference to the initiator.
  • the node update policy in order to minimize the impact on existing services, can be set to minimize the interruption time of existing services.
  • the VNFM sends the determined node information of the node that needs to be updated, the deployment information, and the external connection point that needs to be updated to the virtual infrastructure manager VIM, specifically: the VNFM is based on a preset node update policy. Node information, deployment information, and external connection points that need to be updated are sent to the nodes that need to be updated. VIM.
  • the current deployment preference is DF1.
  • the VFND described in code (2) can know that the current service is provided by three nodes: VDU1, VDU2, and VL1.
  • node VL1 passes through the connection points CP1 and VDU2 on VDU1.
  • CP3 connects VDU1 and VDU2 and communicates with external network External_VL1 through CP4 on VDU2 through CP2 on VDU1 and external network External_VL2.
  • you need to update the deployment preference DF1 to DF2 you need to add new nodes (new VDU3 and VL2 nodes) for nodes that need to be updated.
  • the VDU3 node in this embodiment and then the node that has a connection relationship with the node in the existing deployment preference, such as VL2 in the embodiment of the present invention, has a connection relationship with the node in the existing deployment preference. Therefore, when deploying this part of the node, you need to release the corresponding connection in the existing deployment preferences. For example, when deploying VL2, you need to use CP2 in VDU1. In the current deployment preference DF1, CP2 acts as the external connection point and external. The network External_VL2 is connected. Therefore, before deploying VL1, you need to release the CP2 node and connect the CP6 to the external network External_VL2 before deploying VL2.
  • the current deployment preference is DF2.
  • the VFND described in the code (2) can know that the current service is provided by five nodes: VDU1, VDU2, VDU3, VL1, and VL2.
  • the node VL1 passes through the connection point on the VDU1.
  • CP3 on CP1 and VDU2 connects VDU1 and VDU2.
  • Node VL2 connects VDU1 and VDU3 through the connection point CP2 on VDU1 and CP5 on VDU3, and passes through CP6 on VDU3 and external network External_VL2 through VDU2.
  • the CP4 communicates with the external network External_VL1.
  • the node that needs to be updated is the node that needs to be deleted (delete the nodes VDU3 and VL2), determine whether there is an external connection point of the current deployment preference on the node to be deleted. If not, Then release all nodes that need to be deleted. If yes, obtain the external connection point of the deployment favorite DF2 that needs to be updated from the VNFD, determine the external connection point that needs to be updated, and determine whether the external connection point that needs to be updated is available.
  • the VL node connected to the external connection point that needs to be updated is released first, and then the external connection point that needs to be updated is connected with the external network, and finally the remaining nodes that need to be deleted are released.
  • the external connection point of the current deployment preference DF1 is CP4 and CP6, and the nodes to be deleted are VDU3 and VL2, wherein the VDU3 includes the external connection point CP6 of the current deployment preference DF1. .
  • the external connection points of the deployment preference DF2 that need to be updated are CP4 and CP2, wherein the external connection point CP4 does not change, CP2 is an external connection point that needs to be updated, and the update needs to be updated.
  • the external connection point CP2 is not available. Therefore, it is necessary to release the VL2 connected to the CP2 first, then connect the CP2 to the external network External_VL2, and finally release the VDU3.
  • the embodiment of the present invention provides a method for deploying a favorite switch, which implements different service deployments by using the same deployment template, improves the flexibility of virtualized service deployment, and saves deployment template resources. Compared with the prior art, a plurality of deployment templates are required to implement different service deployments, and the method of the embodiment of the present invention can reduce the time of the existing service interruption when the deployment is performed.
  • the embodiment of the present invention further describes a schematic structural diagram of a virtual infrastructure manager in the method embodiment of the foregoing FIG. 5 and FIG.
  • the virtual infrastructure manager 700 is configured to perform the functions of the VNFM in the foregoing method embodiment of FIG. 5 to FIG. 6, including: a receiving unit 701, an obtaining unit 703, a determining unit 705, and a sending unit 707.
  • the receiving unit 701 is configured to receive an instantiation request, where the instantiation request includes the deployment package information corresponding to the VNF instantiation and the first deployment preference identifier, and the obtaining unit 703 is configured to obtain the location and the identifier according to the VNF instance identifier.
  • the VNF instance identifies a corresponding VNF deployment template VNFD, the VNFD includes description information of at least two potential deployment nodes and at least two deployment preference description information; wherein each of the description information of the at least two potential deployment nodes Potential department
  • the description information of the node includes the identifier of the potential deployment node, the node information, and the deployment condition, and each of the at least two deployment preference description information includes a node identifier of the node that needs to be deployed corresponding to the deployment preference and a deployment unit 705, configured to determine, according to the first deployment preference identifier and the VNFD, node information and deployment information of a node that needs to be deployed corresponding to the first deployment preference identifier, and a sending unit 707, configured to: The determined node information and deployment information of the node to be deployed are sent to the virtual infrastructure manager VIM.
  • the deployment condition includes a deployment identifier
  • the determining unit is configured to determine, according to the first deployment preference identifier and the VNFD, a required deployment corresponding to the first deployment preference identifier.
  • the node information and the deployment information of the node are specifically: comparing the first deployment preference identifier with the deployment condition of the potential deployment node for the description information of each potential node in the description information of the at least two potential deployment nodes a deployment identifier that is included; when the first deployment preference identifier matches a deployment identifier included in a deployment condition of the potential deployment node, determining that the potential deployment node is a node that needs to be deployed; and acquiring node information of the node that needs to be deployed Obtaining the deployment preference description information corresponding to the first deployment preference identifier in the VNFD, and determining the deployment information of the node to be deployed according to the deployment preference description information corresponding to the first deployment preference identifier.
  • the receiving unit 701 is further configured to receive a request for updating a deployment preference, where the update deployment request packet includes the VNF instance identifier and a second deployment preference identifier; and the acquiring unit 703 is further configured to: Determining, by the VNF instance, the VNFD, the determining unit 705 is further configured to determine, according to the first deployment preference identifier, the second deployment preference identifier, and the VNFD, node information and deployment of a node that needs to be updated.
  • the sending unit 707 is further configured to send the node information and the deployment information of the node that needs to be updated by the determining unit 705 to the virtual infrastructure manager VIM.
  • the determining unit 705 is further configured to determine node information and deployment information of the node that needs to be updated according to the second deployment preference identifier and the VNFD, specifically: according to the second deployment preference identifier and the location Determining a node that needs to be deployed corresponding to the second deployment preference identifier; determining, according to the first deployment preference identifier and the VNFD, a node that needs to be deployed corresponding to the first deployment preference identifier; determining the requirement Updating the deployed node; obtaining the node information of the node to be deployed; determining the deployment information of the node that needs to be updated according to the deployment preference description information corresponding to the second deployment preference identifier.
  • the virtual network function manager 700 is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • FIG. 7 The receiving unit 701, the obtaining unit 703, the determining unit 705 and the transmitting unit 707 can be implemented by the processor and the memory of FIG.
  • the embodiment of the present invention further provides a computer storage medium for storing computer software instructions for implementing the virtual network function manager shown in FIG. 7 above, which includes a program designed to execute the foregoing method embodiment.
  • a computer storage medium for storing computer software instructions for implementing the virtual network function manager shown in FIG. 7 above, which includes a program designed to execute the foregoing method embodiment.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Automation & Control Theory (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Stored Programmes (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供一种虚拟网络中部署业务的方法与装置。在该方法中，虚拟网络功能管理器接收实例化请求，实例化请求包括VNF实例标识和第一部署喜好标识；根据VNF实例标识，获取VNF部署模板VNFD，该VNFD包括至少两个潜在部署节点的描述信息以及至少两个部署喜好描述信息；其中，每一个潜在部署节点的描述信息包括该潜在部署节点的节点信息以及部署条件，每一个部署喜好描述信息包括该部署喜好对应的需要部署的节点的部署信息；根据第一部署喜好标识以及该VNFD，确定需要部署的节点的节点信息和部署信息；将确定的需要部署的节点的节点信息和部署信息发送给虚拟基础设施管理器。从而解决了现有技术中一个业务模板不能支持多个部署喜好的业务需求。

Description

一种虚拟化网络中业务部署的方法和装置
本申请要求于2016年8月5日提交中国专利局、申请号为201610643597.0，发明名称为“一种虚拟化网络中业务部署的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及信息技术领域，尤其涉及一种虚拟化网络中业务部署的方法及装置。
背景技术
网络功能虚拟化(Network Function Virtualization，NFV)，指通过使用通用的硬件设备及虚拟化技术，来承载传统网络中专用设备的功能，从而降低部署专用设备带来的昂贵成本。软件不与专有硬件绑定，使网络设备功能不再依赖于专用硬件。同时利用云计算的特点，使资源可以充分灵活共享，现实新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。在NFV的架构中，接收实例化请求，并根据请求对相应业务进行实例化处理(部署业务)的一方，称为虚拟化业务提供方(简称业务提供方)，发起实例化请求的一方称为业务请求方。
NFV中虚拟化的网络服务(Network Service，NS)，举例来说，可以是一个IP多媒体子系统(IP Multimedia Subsystem，IMS)网络服务，或一个演进型分组核心网(Evolved Packet Core，EPC)服务。一个NS中可以包含若干个虚拟化网络功能(virtualized Network Function，VNF)模块，也称为虚拟化网元。一个NS在进行虚拟化部署时，业务请求方首先需要向业务提供方提交该网络业务的描述信息(Network Service descriptor，NSD)，网络业务的描述信息也称作NS部署模板，主要包括描述该网络业务的拓扑结构的拓扑结构信息以及该网络业务包含的各个VNF的描述信息(VNF descriptor，VNFD)。其中在拓扑结构信息中使用虚拟化连接信息VLD(virtual link descriptor)来描述VNF之间的连接。VNFD是一个VNF的描述信息，也称作VNF的部署模板，其中包含该被描述的VNF包括的虚拟部署单元VDU(Virtualisation Deployment Unit)，连接点CP(connection point)和虚拟连接VL(virtual link)等信息。其中VDU可以代表安装了应用软件的虚拟机，在VDU的描述中包含了VDU对该虚拟机的虚拟资源的需求描述,CP代表虚拟机上的连接信息，比如可以是虚拟网卡信息，可以采用IP地址或MAC地址来表示，VL是VNF内连接多个VDU的虚拟连接，可以用带宽、QoS等信息来表示。
现有技术中的VNF部署模板(VNFD)可以采用TOSCA标准定义的YAML(Yet Another Markup Language)模型对其进行描述，具体的可以采用一个TOSCA的service template(业务模板)来描述VNFD，示例性的，如下为一个路由器VNF的部署模板：
代码(1)
Figure PCTCN2017090891-appb-000001
Figure PCTCN2017090891-appb-000002
Figure PCTCN2017090891-appb-000003
Figure PCTCN2017090891-appb-000004
根据上述VNFD可以获得相应的VNF的部署模板实例图，如图1所示。即该代码(1)描述的VNF包括VDU1、VDU2和VDU3共三个VDU，以及CP1-CP6共6个CP，以及VL1和VL2共两个VL。其中，CP1包含的代码virtualbinding:VDU1以及virtualLink:VL1表明，CP1附属在VDU1上，并同VL1连接，CP2包含的代码virtualbinding:VDU1以及virtualLink:VL2表明CP2附属在VDU1上，并同VL2连接。类似的，CP3包含的代码表明CP3附属在VDU2上并同VL1连接,CP4包含的代码表明CP4附属在VDU2上。CP5包含的代码表明CP5附属在VDU3上,并与VL2连接，CP6包含的代码表明CP6附属在VDU3上。而代码virtualLink:[CP4,virtualLink]和virtualLink:[CP6,virtualLink]表明，CP4和CP6作为该VNF的外部连接点与外部网络进行连接。
现实应用中，有这样的需求：根据不同的部署需求，在部署时从VNFD中选择部署不同的VDU和VL，而不是不论什么应用都部署VNFD中所有的VDU和VL。比如上面介绍的路由器实例，该VNFD中可以包含两种部署方法，其中第一种部署方法中包含VDU1、VDU2和VL1；第二种部署方法中包含VDU1、VDU2、VDU3、VL1和VL2；其中VDU3可以为防火墙模块。当该路由器VNF部署在内部网络时，可以选择按第一种部署方法进行部署，即不需要防火墙模块VDU3；当该路由器VNF部署在网络边缘时，则需要按第二种部署方法进行部署。第一种部署方法和第二种部署方法部署实例图如图2(a)和图2(b)所示。
然而，根据现有技术中采用TOSCA模型描述的VNFD，可以发现如果要描述多个部署方法，则需要采用多个TOSCA的业务模板，从而造成了资源的浪费。
发明内容
本发明提供一种虚拟化网络中业务部署的方法及装置，以解决现有技术中一个业务模板不能支持多个部署喜好的业务需求。
第一方面，本发明的实施例提供一种虚拟网络中部署业务的方法，包括：虚拟网络功能管理器接收实例化请求，该实例化请求包括VNF实例标识和第一部署喜好标识；获取与VNF实例标识对应的VNF部署模板VNFD。相较于现有技术，本发明实施例扩展了VNFD中包括的内容。具体的，该VNFD包括至少两个潜在部署节点的描述信息以及至少两个部署喜好描述信息；其中，每一个潜在部署节点的描述信息包括该潜在部署节点的节点信息以及部署条件，每一个部署喜好描述信息包括该部署喜好对应的需要部署的节点的部署信息。虚拟网络功能管理器根据实例化请求中的第一部署喜好标识以及该VNFD，确定与第一部署喜好标识对应的需要部署的节点的节点信息和部署信息，然后将确定的需要部署的节点的节点信息和部署信息发送给虚拟基础设施管理器，以便于虚拟基础设施管理器进行实例化操作。
在本发明实施例中，通过在VNFD中扩展了部署喜好描述信息，具体的，定义了在不同部署喜好的情况下，需要部署的节点以及部署信息，并且在实例化请求中添加部署喜好的标识。当VNFM接收到实例化请求时，根据实例化请求中的部署喜好标识，确定需要部署的节点 及部署信息，并发送给VIM进行实例化操作，从而可以实现同一个VNFD支持多个部署喜好的业务需求，提供了一种更加灵活的业务部署方法。
在一个可能的设计中，所述部署条件包括部署标识，虚拟网络功能管理器根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点的节点信息和部署信息，具体为：对于每一个潜在节点的描述信息，比较所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识；当所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识相匹配时，确定该潜在部署节点为需要部署的节点；获取所述需要部署的节点的节点信息；获取所述VNFD中与所述第一部署喜好标识对应的部署喜好描述信息；根据所述第一部署喜好标识对应的部署喜好描述信息，确定所述需要部署的节点的部署信息。其中，所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识相匹配，具体为：该潜在部署节点的部署条件包括的部署标识与所述第一部署喜好标识相同；或者该潜在部署节点的部署条件包括的部署标识包括所述第一部署喜好标识；或者该潜在部署节点的部署条件包括的部署标识为null(任意部署喜好都满足该潜在部署节点的部署条件)。相较于现有技术，本发明实施例增加了节点的部署条件，并且通过将部署条件和实例化请求中的部署喜好标识进行比较，确定节点是否需要部署，从而实现了根据VNFD，灵活部署业务的需求。
在另一种可能的设计中，网络功能虚拟化编排器接收发送方发送的注册请求，注册请求中包括VNF部署包。所述VNF部署包包括VNFD。可选的，所述VNF部署包还包括镜像文件和/或安全证书等。网络功能虚拟化编排器保存注册请求中的部署包，向发送方返回注册成功的响应消息；网络功能虚拟化编排器接收发起方发送的创建VNF实例标识的请求，并将创建VNF实例标识的请求转发给虚拟网络功能管理器；虚拟网络功能管理器生成所述VNF实例标识，并将所述VNF实例标识发送给所述网络功能虚拟化编排器；网络功能虚拟化编排器在本地建立所述VNF实例标识和所述部署包信息的对应关系，并将所述VNF实例标识返回给发起方。
在另一种可能的设计中，在VNF实例化以后，虚拟网络功能管理器可以根据运行需求对当前的VNF部署喜好进行更新。具体的，虚拟网络功能管理器接收更新部署喜好的请求，该更新部署喜好的请求包括所述VNF实例标识和第二部署喜好标识；根据所述VNF实例标识，获取所述VNFD；根据第一部署喜好标识、所述第二部署喜好标识以及所述VNFD，确定需要更新部署的节点的节点信息和部署信息；将确定的需要更新部署的节点的节点信息和部署信息发送给所述虚拟基础设施管理器，以便于虚拟基础设施管理器进行实例化操作。本发明实施例通过同一个部署模板实现了不同的业务部署，提高了虚拟化业务部署的灵活性，节约了部署模板资源。相比较与现有技术中需要多个部署模板来实现不同的业务部署，采用本发明实施例的方法，在切换部署时，还可以减小现有业务中断的时间。
第二方面，本发明实施例提供了一种虚拟网络中部署业务的装置，该虚拟网络中部署业务的装置具有实现上述第一方面中虚拟网络功能管理器行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中，该虚拟网络中部署业务的装置的结构中包括处理器和存储器，所述存储器用于存储支持该虚拟网络中部署业务的装置执行上述方法的程序，所述处理器被配置为用于执行所述存储器中存储的程序。该虚拟网络中部署业务的装置还可以包括通信接口，用于该虚拟网络中部署业务的装置与其他设备或通信网络通信。
第三方面，本发明实施例提供了一种计算机存储介质，用于储存为上述虚拟网络中部署业务的装置所用的计算机软件指令，其包含用于执行上述方面为虚拟网络中部署业务的装置所设计的程序。
可选的，上述方面所述的节点包括虚拟部署单元VDU或者虚拟连接VL；所述部署信息包括VDU的弹性伸缩参数或者VL的服务质量参数。
相较于现有技术，本发明提供的方案可以实现一个VNFD支持多个部署喜好的业务需求，提供了一种更加灵活的业务部署方法。此外，由于不同的部署方法都是基于相同的部署模板，所以发起方不需要重复在NFVO上进行注册，VNFM也不需要从NFVO上获取多个部署模板，简化了业务部署的复杂度。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
现将参考附图通过非限制性的实施例描述本发明的优选特征，其中：
图1为根据代码(1)所示VNFD获得的VNF的部署模板实例图；
图2(a)为按照第一种部署方法部署的实例图；
图2(b)为按照第二种部署方法部署的实例图；
图3为本发明一实施例所提供的网络功能虚拟化的网络架构图；
图4为本发明一实施例提供的计算机设备示意图；
图5为本发明一实施例提供的一种虚拟网络中部署业务的方法流程图；
图6为本发明一实施例提供的一种不同部署喜好切换的方法流程图；
图7为本发明一实施例提供的虚拟基础设施管理器的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。
图3为本发明一实施例提供的一种NFV系统300的架构示意图，用于在虚拟化网络中进行业务部署。具体的，为实现本发明的目的，本发明实施例提供的一个架构示意图包括以下功能部件：
网络功能虚拟化编排器(network function virtualization orchestrator，NFVO)302，主要负责处理虚拟化业务的生命周期管理以及虚拟基础设施NFVI中虚拟资源的分配和调度等。NFVO 302可以与一个或多个虚拟网络功能管理器(Virtualized Network Function Manager，VNFM)304通信，以执行资源相关请求，发送配置信息给VNFM 304，收集VNF 308的状态信息。另外，NFVO 302也可与虚拟基础设施管理器(Virtualized Infrastructure Manager,VIM)306通信，执行资源分配和/或预留，交换虚拟化硬件资源配置和状态信息。
虚拟网络功能管理器(VNFM)304，负责一个或多个VNF的生命周期管理，比如实例化(instantiating)，更新(updating)，查询，扩容(scaling)，终止(terminating)VNF 308。VNFM 304可以与VNF 308通信以完成VNF生命周期管理及交换配置和状态信息。在NFV架构中VNFM可以有多个，负责对不同类型的VNF进行生命周期管理。NFVO 302可以根据VNFM负责的业务类型，对不同的VNF 308选择确定不同的VNFM 304。
虚拟基础设施管理器(VIM)306，控制和管理VNF 308与计算硬件312，存储硬件314，网络硬件316，虚拟计算(virtual computing)318，虚拟存储320，虚拟网络322的交互。例如VIM306执行资源管理功能，包括管理基础设施资源的分配(例如给虚拟容器增加或减少资源)及运行功能(例如收集NFVI故障信息)。VNFM 304及VIM306可以相互通信，请求资源分配。
网络功能虚拟化基础设施(network functions virtualization infrastructure，NFVI)即NFV的基础设施层，包含硬件部件，软件部件或两者组合，以建立虚拟化环境，部署、管理及实现VNF 308。硬件资源和虚拟化层用于为VNF 308提供虚拟化资源，如虚拟机VMs和其他形式的虚拟容器。硬件资源包括计算(computing)硬件312，存储硬件314，网络硬件316。作为一种实施方式，计算硬件312和存储硬件314的资源可以集中(pooled)在一起。NFVI中的虚拟化层可以抽象硬件资源，解耦VNF 308与底层的物理网络层。虚拟化资源包含虚拟计算318(例如虚拟机，VMs)，虚拟存储320和虚拟网络322。虚拟计算318和虚拟存储320通过系统管理程序(hypervisor或容器runtime)以虚拟机，和/或其他虚拟容器的形式被提供给VNF 308。例如，一个或多个VNF 308可被部署在一个VM上。
多个虚拟化网络功能(VNF)308，被配置成至少一种网络功能的虚拟化。VNF308可以是一个虚拟化提供者边缘(provider edge，PE)节点，用于提供非虚拟化PE设备上所有的PE网络功能，例如路由器(router)，交换机(switch)，网桥(bridge)，服务器，云计算系统等。每个VNF运行在一个或者多个虚拟容器中，对应于一组属于一个或多个物理设备的网络功能。
设备管理系统(EM)310，是传统电信系统中用于对设备进行配置和管理的系统，在NFV架构中，EM 310也可以用于对VNF进行配置和管理，以及向VNFM304发起新的VNF的实例化等生命周期管理操作。
运营支持系统和业务支持系统(Operations Support System and Business Support System，OSS/BSS)324，支持各种端到端电信业务。OSS支持的管理功能包括：网络配置，业务提供，故障管理等。BSS处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。OSS/BSS 324可以作为虚拟化业务的发起方，主要用于通过NFV系统开放出来的接口向NFV系统请求部署虚拟化业务及虚拟化业务的生命周期管理。
本发明实施例中VNFM接收到实例化请求后，根据实例化请求中的VNF实例标识，从NFVO获取VNF的部署模板VNFD；其中，VNFD中包括至少两个潜在部署节点的描述信息以及至少两个部署喜好描述信息，且所述至少两个潜在部署节点的描述信息中的每一个潜在部署节点的描述信息包括该潜在部署节点的标识、节点信息以及部署条件，所述至少两个部署喜好描述信息中的每一个部署喜好描述信息包括该部署喜好对应的需要部署的节点的节点标识及部署信息；VNFM根据部署喜好标识以及VNFD，确定与实例化请求中的部署喜好标识对应的需要部署的节点的节点信息和部署信息；将确定的需要部署的节点的节点信息和部署信息发送给虚拟基础设施管理器VIM，以便于VIM进行实例化操作，从而实现了根据同一个部署模板，进行不同部署的目的。
为了便于描述本发明实施例的方案，代码(2)介绍了一个VNF的部署模板，根据该部署模板可以用于实现图2(a)以及图2(b)所述实例图的部署方案，需要说明的是，代码(2)中只列出了与本发明实施例相关的内容，其余的内容为现有技术，本发明实施例不做限定。
代码(2)：
Figure PCTCN2017090891-appb-000005
Figure PCTCN2017090891-appb-000006
Figure PCTCN2017090891-appb-000007
Figure PCTCN2017090891-appb-000008
Figure PCTCN2017090891-appb-000009
本发明实施例可以采用TOSCA模型实现，示例性的，代码(2)相对于现有技术的代码(1)而言，进行了部分扩展。具体的，在DSL_definitions部分增加了对部署喜好DF的定义。其中每个DF的定义中包含有需要部署的VDU，VL以及外部连接点信息，所述外部连接点信息用于指示VNF通过哪些连接点与外部网络进行连接。比如代码(2)所述VNFD中的DF1中包含VDU1，VDU2和VL1，代码External_CP_1：CP4和External_CP_2：CP2表明在DF1中，由CP2和CP4作为外部链接点。DF2中包含VDU1，VDU2，VDU3，VL1和VL2，代码External_CP_1:CP4和External_CP_2:CP6表明在DF2中，由CP4和CP6作为外部连接点。在DF中需要部署的VDU，VL中还包含有部署信息，比如DF1中的VDU1中具有scalable参数，其中代码min_instances:3和max_instances:10定义了最小实例化个数为3，最大实例化个数为10。而DF1中的VL1中包含有部署时的服务质量(Quality of Service，QoS)参数，其中latency(延时)为10ms,Delay(抖动)为20ms。需要说明的是，DF中需要部署的节点的部署信息还可以是任何在部署节点时需要用到的信息，这里的scalable参数以及QoS参数等只是示例性的展示，本发明实施例部署信息的具体内容不做限定。
进一步的，本发明实施例对VNFD中的替代映射部分(subsititution_mappings)扩展了根据部署喜好选择外部连接点的描述。具体的，采用get_DSL：[(get_input:deployment_flavour),External_CP_1]操作来灵活地根据不同的DF选择相应的外部链接点，其中，get_DSL用于从DSL_definitions中获取一个参数的值，参数get_input:deployment_flavour用于获取deployment_flavour的输入值，在本发明实施例中，deployment_flavour的输入值由VNF实例化请求中的部署喜好标识确定，比如可以是DF1或DF2。get_DSL中的参数External_CP_1用于指示需获取的具体参数的值。在代码(2)的示例中，“External_CP_1”表示，获取的是External_CP_1的值。根据上面代码(2)中对DF的描述，比如当deployment_flavour的输入值为DF1或者DF2时，则get_DSL：[(get_input:deployment_flavour),External_CP_1]操作，获取到的的值均是CP4。
另外，在VNFD中的节点模板(node_templates)部分包括了对VNF中VDU、VL以及CP等节点的描述信息，包括节点的标识、节点信息以及节点的部署条件。相对于现有技术，在每个节点描述中增加了deploy_dependsOnDF参数，该参数用来指示节点的部署条件。可选的，该部署条件可以是部署喜好的标识。比如在VDU1节点描述中，代码deploy_dependsOnDF:[DF1,DF2]，表示当部署喜好deployment_flavour的值为DF1或DF2时都需要部署VDU1。对于VDU3，代码deploy_dependsOnDF:[DF2]，则表示当部署喜好deployment_flavour的值为DF2时需要部署VDU3，而部署喜好的值为DF1时，不需要部署VDU3。在节点的描述信息中，有些参数的赋值也用到了get_DSL操作，该操作用来从指定的部署喜好描述信息中获取相应的部署信息，比如，当输入的deployment_flavour为DF1时，VDU1中的scalable:[get_DSL：(get_input:deployment_flavour),VDU1,scalable]，表示从DSL_definitions中的DF1中获取VDU1中scalable参数的赋值，即为min_instances:3；max_instances:10；VL1中的QoS:[get_DSL：(get_input:deployment_flavour),VL1,QoS]]表示从DSL_definitions中定义的DF1中获取VL1的QoS参数的赋值。此外，在节点的描述信息中 还包括节点的节点信息，比如VDU1中的num_cpus:{equal:2}，mem_size:{greater_or_equal:3GB}，即用于指示部署VDU1时，VDU1对虚拟机的性能需求(2个性能指标的CPU，3GB的内存)。需要说明的是，一个节点的节点信息和部署信息共同构成在部署该节点时需要用到的信息，但是节点信息用于指示在部署该节点时，需要用到的信息，且该需要用到的信息不随部署喜好的变化而变化；例如，在本发明实施例中，在按照DF1和DF2部署时，VDU1都需要部署，且在部署VDU1时，VDU1对虚拟机的性能需求都是一样的(2个性能指标的CPU，3GB的内存)，因此，可以将部署VDU1时，VDU1对虚拟机的性能需求作为VDU1的节点信息保存在节点模板中。
如图4所示，图3中的虚拟网络功能管理器VNFM可以以图4中的计算机设备(或系统)的方式来实现。
图4所示为本发明实施例提供的计算机设备示意图。计算机设备400包括至少一个处理器401，通信总线402，存储器403以及至少一个通信接口404。
处理器401可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线402可包括一通路，在上述组件之间传送信息。所述通信接口504，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器403可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，所述存储器403用于存储执行本发明方案的程序代码，并由处理器401来控制执行。所述处理器401用于执行所述存储器403中存储的程序代码。
在具体实现中，作为一种实施例，处理器401可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备400可以包括多个处理器，例如图4中的处理器401和处理器408。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备400还可以包括输出设备405和输入设备406。输出设备405和处理器401通信，可以以多种方式来显示信息。例如，输出设备405可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备406和处理器401通信，可以以多种方式接受用户的输入。例如，输入设备406可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备400可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备400可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图4中类似结构的设备。本发明实施例不限定计算机设备400的类型。
如图3中的虚拟网络功能管理器可以为图4所示的设备，虚拟网络功能管理器的存储器中存储了一个或多个软件模块。虚拟网络功能管理器可以通过处理器以及存储器中的程序代码来实现软件模块，实现根据同一个VNFD，进行不同部署的目的。
图5为本发明实施例提供的一种虚拟网络中部署业务的方法流程图，包括如下步骤：
步骤501、发起方向NFVO发送用于注册VNF的部署包的注册请求。
具体的，所述VNF部署包包括VNFD。可选的，所述VNF部署包还包括镜像文件和/或安全证书等。除VNFD外，与本发明不相关的文件这里不再赘述。
结合图3所述NFV系统架构示意图，所述发起方可以是OSS/BSS 324。OSS/BSS 324通过NFV系统开放的接口向NFVO发送注册请求，该注册请求具体可以是on-boarding请求，且所述注册请求中包括所述VNF部署包。
示例性的，本发明实施例中所述VNFD包括至少两个潜在部署节点的描述信息以及至少两个部署喜好描述信息；其中，所述至少两个潜在部署节点的描述信息中的每一个潜在部署节点的描述信息包括该潜在部署节点的标识、节点信息以及部署条件，所述至少两个部署喜好描述信息中的每一个部署喜好描述信息包括该部署喜好对应的需要部署的节点的节点标识及部署信息。
所述潜在部署节点可以是虚拟部署单元VDU或虚拟连接VL，如代码(2)中的VDU1、VDU2、VDU3、VL1或VL2。
所述部署信息包括VDU的弹性伸缩参数或VL的QoS参数。
步骤502、NFVO接收发起方发送的注册请求，并保存所述注册请求中的部署包，返回注册成功的响应消息。
其中，所述注册成功的响应消息中包括部署包信息。
其中，所述部署包信息可以是部署包的标识，也可以是可以唯一确定一个部署包的一组参数，总之，部署包信息和对应的部署包存在一一对应的关系，本发明对部署包信息的具体形式不做限定。
步骤503、发起方接收NFVO返回的注册成功的响应消息，向NFVO发送创建VNF实例标识的请求。
具体的，该创建VNF实例标识的请求包括部署包信息。
步骤504、NFVO接收发起方发送的创建VNF实例标识的请求，并将创建VNF实例标识的请求转发给VNFM。
步骤505、VNFM接收NFVO发送的创建VNF实例标识的请求，并且生成VNF实例标识，并将生成的VNF实例标识发送给NFVO。
需要说明的是，本发明对具体如何生成VNF实例标识不做限定。一种可能的设计中，VNFM生成在本地具有唯一性的字符串，根据VNFM在NFV系统中的地址以及该字符串，生成VNF实例标识；或者VNFM生成在NFV系统中具有全局唯一性的字符串，根据该全局唯一性的字符串，生成VNF实例标识。
步骤506、NFVO接收VNFM返回的VNF实例标识，在本地建立所述VNF实例标识和所述部署 包信息的对应关系，并将所述VNF实例标识返回给发起方。
步骤507、发起方接收NFVO返回的VNF实例标识，并向NFVO发送VNF实例化请求。
具体的，所述VNF实例化请求包括所述VNF实例标识和第一部署喜好标识DF1。
步骤508、NFVO接收发起方发送的VNF实例化请求，并将VNF实例化请求转发给VNFM。
步骤509、VNFM接收NFVO发送的VNF实例化请求，并向NFVO发送获取部署包的请求。
具体的，所述获取VNF部署包的请求中包括所述VNF实例标识。
步骤510、NFVO接收VNFM发送的获取部署包的请求，获取所述VNF实例标识对应的部署包，并将获取的部署包返回给VNFM。
获取所述VNF实例标识对应的部署包，具体为：NFVO在本地保存的VNF实例标识和部署包信息的对应关系中，获取与所述VNF实例标识对应的部署包信息；根据所述VNF实例标识对应的部署包信息，获取部署包。
步骤511、VNFM接收NFVO返回的部署包，并确定部署包中的VNFD中需要进行实例化的VDU节点的节点信息，并根据第一部署喜好标识对应的部署喜好描述信息获取该VDU节点的部署信息。
其中，所述VDU节点的节点信息为所述VNFD中用于表征该VDU节点按照不同部署喜好进行部署时，相同的部署参数，如代码(2)中VDU1节点的requirements部分描述的CPU和Memory等信息。
可选的，所述VDU节点的节点信息也可以在部署喜好的描述信息中描述，此时节点信息可以是部署信息的一部分；当所述VDU节点的节点信息是部署信息的一部分时，所述VDU实例化请求可以只包括VDU节点的部署信息。
具体的，对于所述VNFD中的每一个VDU节点的描述信息，比较所述第一部署喜好标识DF1与该VDU节点的部署条件包括的部署标识；当所述第一部署喜好标识与该VDU节点的部署条件包括的部署标识相匹配时，确定该VDU节点为需要部署的节点；获取该VDU节点的节点信息；获取所述VNFD中与所述第一部署喜好标识对应的部署喜好描述信息；根据所述第一部署喜好标识对应的部署喜好描述信息，确定该VDU节点的部署信息。
其中，所述第一部署喜好标识与该VDU节点的部署条件包括的部署标识相匹配，具体为：该VDU节点的部署条件包括的部署标识与所述第一部署喜好标识相同；或者该VDU节点的部署条件包括的部署标识包括所述第一部署喜好标识；或者该VDU节点的部署条件包括的部署标识为null(任意部署喜好都满足该VDU节点的部署条件)。
例如，在本发明实施例中，相对于代码(2)，对于VDU1节点的描述信息，由于VDU1的deploy_dependsOnDF参数中包含有实例化请求中的部署喜好标识DF1，因此，VNF实例化时需要部署VDU1。VNFM获取该VDU的节点信息，如部署VDU1时对虚拟机的性能需求(2个性能指标的CPU，3GB的内存)。再根据VDU1中scalable:[get_DSL：(get_input:deployment_flavour),VDU1,scalable]从VNFD的DSL_definitions中的DF1中获取VDU1的scalable参数。
步骤512、VNFM向VIM发送VDU实例化请求，所述VDU实例化请求包括VDU节点的节点信息和部署信息。
步骤513、VIM接收VNFM发送的VDU实例化请求，并根据VDU实例化请求中的部署信息创建虚拟机，向VNFM返回实例化成功的响应。
VIM根据节点信息和部署信息实例化VDU是本领域技术人员公知的技术，本发明实施例不 再赘述。
步骤514、VNFM确定部署包中的VNFD中需要进行实例化的VL节点，并根据第一部署喜好标识对应的部署喜好描述信息获取该VL节点的节点信息和部署信息。
所述VL节点的部署信息包括VL的服务质量参数，所述VL节点的节点信息包括该VL节点对应的连接点信息。其中，所述VL节点对应的连接点信息用于指示VL节点通过哪个连接点与其他节点连接。
具体的，对于所述VNFD中的每一个VL节点，比较所述第一部署喜好标识与该VL节点的部署条件包括的部署标识；当所述第一部署喜好标识与该VL节点的部署条件包括的部署标识相匹配时，确定该VL节点为需要部署的节点；获取该VL节点的节点信息；获取所述VNF部署包中与所述第一部署喜好标识对应的部署喜好描述信息；根据所述第一部署喜好标识对应的部署喜好描述信息，确定该VL节点的部署信息。
其中，所述第一部署喜好标识与该VL节点的部署条件包括的部署标识相匹配，具体为：该VL节点的部署条件包括的部署标识与所述第一部署喜好标识相同；或者该VL节点的部署条件包括的部署标识包括所述第一部署喜好标识；或者该VL节点的部署条件包括的部署标识为null(任意部署喜好都满足该VL节点的部署条件)。
例如，在本发明实施例中，相对于代码(2)，对于VL1节点的描述信息，由于VL1的deploy_dependsOnDF参数中包含有实例化请求中的部署喜好标识DF1，因此，VNF实例化时需要部署VL1。VNFM获取该VL1的节点信息，如部署该VL1的连接点信息(通过VDU1上的CP1和VDU2上的CP3，连接VDU1节点和VDU2节点)。再根据VL1中的QoS:[get_DSL：(get_input:deployment_flavour),VL1,QoS]]从VNFD中的DSL_definitions中的DF1中获取VL1的QoS参数。
具体的，当确定好需要部署的VL节点后，需要获取需要部署的VL节点对应的连接点信息。例如，确定VL1需要部署后，VNFM通过VNFD中的node_templates中的代码：
Figure PCTCN2017090891-appb-000010
可以获知节点VL1通过连接点CP1与VDU1建立连接，同时通过连接点CP3与VDU2建立连接，也就是说VL1通过VDU1上连接点CP1和VDU2上的连接点CP3，使得VDU1和VDU2建立连接。
步骤515、VNFM向VIM发送VL实例化请求，所述VL实例化请求包括VL节点的节点信息和部署信息。
步骤516、VIM接收VNFM发送的VL实例化请求，并根据VL实例化请求中的VL节点的节点信息和部署信息，创建VL实例，向VNFM返回实例化成功的响应。
VIM根据节点信息和部署信息实例化VL是本领域技术人员公知的技术，本发明实施例不 再赘述。
步骤517、VNFM根据第一部署喜好标识对应的部署喜好描述信息获取外部连接点信息。
例如，在代码(2)所述的VNFD中subsititution_mappings部分所示：
get_DSL：[(get_input:deployment_flavour),External_CP_1
get_DSL：[(get_input:deployment_flavour),External_CP_2
VNFM根据DF1，获取到DF1中对应的外部连接点External_CP_1对应的连接点为CP4，外部连接点External_CP_2对应的连接点为CP2，则向VIM请求采用CP4和CP2连接对应的外部网络。
步骤518、VNFM向VIM发送外部连接点实例化请求。
其中，所述外部连接点实例化请求中包括外部连接点信息。
步骤519、VIM接收VNFM发送的外部连接点实例化请求，使用外部连接点信息连接外部网络，并向VNFM返回实例化成功的响应。
需要说明的是，步骤517-步骤519不是必需的，特别地，当部署的VNF不需要跟外部网络进行连接时，步骤517-步骤519可以省略。
步骤520、VNFM接收VIM返回的实例化成功的响应，向NFVO返回VNF实例化成功的响应。
步骤521、NFVO接收VNFM返回的VNF实例化成功的响应，向发送方返回VNF实例化成功的响应。
需要说明的是，NFV系统根据部署喜好标识和VNFD，部署VNF实例后，可以在NFV系统中的任意实体上维护每一个VNF实例的当前部署喜好信息。所述当前部署喜好信息用于指示该VNF实例是按照VNFD中的哪个部署喜好进行部署的。
一种可能的设计中，NFVO负责维护每一个VNF实例的当前部署喜好信息。具体的，在步骤508中，NFVO接收到发起方发送的VNF实例化请求后，将VNF实例标识和部署喜好标识作为一条部署记录保存下来，并设置该部署记录的状态为非激活状态(inactive)；当在步骤521中，收到VNFM发送的实例化成功的响应后，将该部署记录的状态设置为激活状态(active)；可选的，当接收到VNFM发送的实例化失败的响应后，则删除该部署记录。后续当NFVO接收到其他实体发送的查询VNF的当前部署喜好信息的请求时，NFVO可以根据VNF实例标识从状态为active的部署记录中查询获取对应的部署喜好标识。
在另一种可能的设计中，VNFM负责维护每一个VNF实例的当前部署喜好信息。具体的，在步骤509中，VNFM接收到NFVO发送的实例化请求后，将VNF实例标识和部署喜好作为一条部署记录保存下来，并设置该部署记录的状态为inactive；当在步骤520中，收到VIM发送的实例化成功的响应后，将该部署记录的状态设置为active。后续VNFM需要查询VNF的当前部署喜好信息时，可以根据VNF实例标识从状态为active的部署记录中查询获取对应的部署喜好标识。
在本发明实施例中，通过在VNFD中扩展了部署喜好描述信息，具体的，定义了在不同部署喜好的情况下，需要部署的节点以及部署信息，并且在实例化请求中添加部署喜好的标识。当VNFM接收到实例化请求时，根据实例化请求中的部署喜好标识，确定需要部署的节点及部署信息，并发送给VIM进行实例化操作，从而可以实现同一个VNFD支持多个部署喜好的业务需求，提供了一种更加灵活的业务部署方法。此外，由于不同的部署方法都是基于相同的部署模板，所以发起方不需要重复在NFVO上进行注册，VNFM也不需要从NFVO上获取多个部署模板，简化了业务部署的复杂度。
在实际运行过程中，有时在VNF实例化以后，需要根据运行需求对当前的VNF部署喜好进 行更新。图6为本发明实施例提供的一种不同部署喜好切换的方法流程图。
示例性的，图6实施例还是以代码(2)所述的VNFD为例，图5所述的实施例中，系统已经根据DF1，对VNF进行了实例化，图6所述的实施例方法将VNF部署喜好更新为DF2。具体的，
步骤601、发起方向NFVO发送更新部署喜好的请求。
其中，所述更新部署喜好的请求包含需要更新的VNF实例标识和第二部署喜好标识，本例中需要更新的VNF实例即是图5所述实施例中实例化的VNF，第二部署喜好标识为DF2。
步骤602、NFVO接收发起方发送的更新部署喜好的请求，并将接收到的更新部署喜好的请求发送给VNFM。
步骤603、VNFM接收NFVO发送的更新部署喜好的请求，根据更新部署喜好的请求中的VNF实例标识，获取VNF的当前部署喜好信息；VNFM向NFVO发送获取VNF部署包的请求。
其中，所述获取VNF部署包的请求中包括所述需要更新的VNF实例标识。
VNFM可以通过不同的方法获取VNF的当前部署喜好信息，本发明对此不做限定。例如，可以采用图5所述实施例中的方法来获取VNF的当前部署喜好信息。在本发明实施例中，VNF的当前部署喜好信息为第一部署喜好标识，即DF1。
步骤604、NFVO接收VNFM发送的获取部署包的请求，获取所述VNF实例标识对应的部署包，并将获取的部署包返回给VNFM。
步骤605、VNFM根据VNF的当前部署喜好信息、所述第二部署喜好标识以及所述部署包中的VNFD，确定需要更新的节点的节点信息、部署信息以及需要更新的外部连接点信息。
具体的，VNFM根据所述第二部署喜好标识以及所述VNFD，确定与所述第二部署喜好标识对应需要部署的节点和外部连接点信息；根据所述第一部署喜好标识以及所述VNFD，确定所述第一部署喜好标识对应需要部署的节点和外部连接点信息；确定需要更新部署的节点和需要更新的外部连接点信息；获取所述需要部署的节点的节点信息；根据所述第二部署喜好标识对应的部署喜好描述信息，确定所述需要更新部署的节点的对应的部署信息。
其中，需要更新部署的节点包括第二部署喜好相对于第一部署喜好需要新增的节点或者删除的节点。
本发明实施例中，第一部署喜好需要部署的节点包括VDU1、VDU2和VL1，且外部连接点信息为CP4和CP2；第二部署喜好需要部署的节点包括VDU1、VDU2、VDU3、VL1和VL2，且外部连接点信息为CP4和CP6。因此，需要更新的节点为新增节点VDU3和VL2，需要更新的外部连接点信息为CP6，即由CP6代替CP2作为外部连接点与外部网络相连。
步骤606、VNFM将确定的需要更新部署的节点的节点信息、部署信息以及需要更新的外部连接点信息发送给虚拟基础设施管理器VIM，以便于VIM进行实例化操作。
VIM根据VNFM发送的信息进行实例化操作是本领域技术人员熟知的技术，这里不再赘述。
当VIM根据VNFM发送的需要更新部署的节点的节点信息、部署信息以及需要更新的外部连接点信息，更新部署成功后，向VNFM返回VNF实例化成功的响应。VNFM向NFVO发送更新部署喜好成功的响应，NFVO进而将所述更新部署喜好成功的响应转发给发起方。
在一种可能的设计中，为了尽量减小对现有业务的影响，可以通过设定节点更新策略，使得现有业务的中断时间最小化。
一种可能的设计中，VNFM将确定的需要更新部署的节点的节点信息、部署信息以及需要更新的外部连接点发送给虚拟基础设施管理器VIM，具体为：VNFM根据预设的节点更新策略，依次将需要更新部署的节点的的节点信息、部署信息以及需要更新的外部连接点发生给 VIM。
例如，当前部署喜好为DF1，从代码(2)描述的VFND可以知道，当前的业务由VDU1、VDU2和VL1这三个节点提供，具体的，节点VL1通过VDU1上的连接点CP1和VDU2上的CP3，将VDU1和VDU2连接起来，并且通过VDU1上的CP2与外部网络External_VL2，通过VDU2上的CP4与外部网络External_VL1进行通信。当需要将部署喜好DF1更新为DF2时，对于需要更新部署的节点为需要新增的节点(新增VDU3和VL2节点)，先部署与现有部署喜好中的节点没有连接关系的节点。如本实施例中的VDU3节点，然后再部署与现有部署喜好中的节点有连接关系的节点，如本发明实施例中的VL2，由于这部分节点与现有部署喜好中的节点有连接关系，所以部署这部分节点的时候，需要先释放现有部署喜好中相应的连接，例如，部署VL2时，需要使用到VDU1中的CP2，而在当前部署喜好DF1中，CP2作为外部连接点与外部网络External_VL2相连，因此，部署VL1前，需要先释放CP2节点，并连接CP6与外部网络External_VL2的连接，然后再部署VL2。
再例如，当前部署喜好为DF2，从代码(2)描述的VFND可以知道，当前的业务由VDU1、VDU2、VDU3、VL1和VL2这五个节点提供，具体的，节点VL1通过VDU1上的连接点CP1和VDU2上的CP3，将VDU1和VDU2连接起来，节点VL2通过VDU1上的连接点CP2和VDU3上的CP5，将VDU1和VDU3连接起来，并且通过VDU3上的CP6与外部网络External_VL2，通过VDU2上的CP4与外部网络External_VL1进行通信。当需要将部署喜好DF2更新为DF1时，对于需要更新部署的节点为需要删除的节点(删除节点VDU3和VL2)时，确定需要删除的节点上是否有当前部署喜好的外部连接点，如果没有，则释放所有需要删除的节点。如果有，则从VNFD中获取需要更新的部署喜好DF2的外部连接点，确定需要更新的外部连接点，并判断该需要更新的外部连接点是否可用，如果该需要更新的外部连接点不可用，则先释放与该需要更新的外部连接点相连的VL节点，然后再将该需要更新的外部连接点与外部网络建立连接，最后再释放剩余需要删除的节点。具体的，从从代码(2)描述的VFND可以知道，当前部署喜好DF1的外部连接点为CP4和CP6，需要删除的节点为VDU3和VL2，其中VDU3上包括当前部署喜好DF1的外部连接点CP6。从从代码(2)描述的VFND可以知道，需要更新的部署喜好DF2的外部连接点为CP4和CP2，其中外部连接点CP4没有发生变化，CP2为需要更新的外部连接点，且该需要更新的外部连接点CP2不可用，因此，需要先释放与CP2相连的VL2，然后再将CP2与外部网络External_VL2进行连接，最后再释放VDU3。
本发明实施例提供了一种部署喜好切换的方法，通过同一个部署模板实现了不同的业务部署，提高了虚拟化业务部署的灵活性，节约了部署模板资源。相比较与现有技术中需要多个部署模板来实现不同的业务部署，采用本发明实施例的方法，在切换部署时，可以减小现有业务中断的时间。
本发明实施例还描述了上述图5和图6所述方法实施例属于同一发明构思下的一种虚拟基础设施管理器结构示意图。如图7所示，该虚拟基础设施管理器700用于执行图5-图6上述方法实施例中VNFM的功能，包括：接收单元701，获取单元703，确定单元705和发送单元707。
其中，接收单元701，用于接收实例化请求，所述实例化请求包括VNF实例化对应的部署包信息和第一部署喜好标识；获取单元703，用于根据所述VNF实例标识，获取与所述VNF实例标识对应的VNF部署模板VNFD，所述VNFD包括至少两个潜在部署节点的描述信息以及至少两个部署喜好描述信息；其中，所述至少两个潜在部署节点的描述信息中的每一个潜在部 署节点的描述信息包括该潜在部署节点的标识、节点信息以及部署条件，所述至少两个部署喜好描述信息中的每一个部署喜好描述信息包括该部署喜好对应的需要部署的节点的节点标识及部署信息；确定单元705，用于根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点的节点信息和部署信息；发送单元707，用于将确定的需要部署的节点的节点信息和部署信息发送给虚拟基础设施管理器VIM。
在一种可能的实现方式中，所述部署条件包括部署标识，所述确定单元，用于根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点的节点信息和部署信息，具体为：对于所述至少两个潜在部署节点的描述信息中的每一个潜在节点的描述信息，比较所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识；当所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识相匹配时，确定该潜在部署节点为需要部署的节点；获取所述需要部署的节点的节点信息；获取所述VNFD中与所述第一部署喜好标识对应的部署喜好描述信息；根据所述第一部署喜好标识对应的部署喜好描述信息，确定所述需要部署的节点的部署信息。
可选的，所述接收单元701，还用于接收更新部署喜好的请求，所述更新部署喜好的请求包所述VNF实例标识和第二部署喜好标识；所述获取单元703，还用于根据所述VNF实例标识，获取所述VNFD；所述确定单元705，还用于根据第一部署喜好标识、所述第二部署喜好标识以及所述VNFD，确定需要更新部署的节点的节点信息和部署信息；所述发送单元707，还用于将所述确定单元705确定的需要更新部署的节点的节点信息和部署信息发送给虚拟基础设施管理器VIM。其中，所述确定单元705，还用于根据所述第二部署喜好标识以及所述VNFD，确定需要更新部署的节点的节点信息和部署信息，具体为：根据所述第二部署喜好标识以及所述VNFD，确定与所述第二部署喜好标识对应的需要部署的节点；根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点；确定需要更新部署的节点；获取所述需要部署的节点的节点信息；根据所述第二部署喜好标识对应的部署喜好描述信息，确定所述需要更新部署的节点的部署信息。
在本实施例中，虚拟网络功能管理器700是以功能单元的形式来呈现。这里的“单元”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到虚拟网络功能管理器700可以采用图4所示的形式。接收单元701,获取单元703，确定单元705和发送单元707可以通过图4的处理器和存储器来实现。
本发明实施例还提供了一种计算机存储介质，用于储存实现上述图7所示的虚拟网络功能管理器的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。通过执行存储的程序，可以实现同一个VNFD支持多个部署喜好的业务需求，提供了一种更加灵活的业务部署方法，简化了业务部署的复杂度。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动 作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
尽管在此结合各实施例对本发明进行了描述，然而，在实施所要求保护的本发明过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白，本发明的实施例可提供为方法、装置(设备)、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。计算机程序存储/分布在合适的介质中，与其它硬件一起提供或作为硬件的一部分，也可以采用其他分布形式，如通过Internet或其它有线或无线电信系统。
本发明是参照本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (11)

  1. 一种虚拟网络中部署业务的方法，其特征在于，包括：
    接收实例化请求，所述实例化请求包括VNF实例标识和第一部署喜好标识；
    获取与所述VNF实例标识对应的VNF部署模板VNFD，所述VNFD包括至少两个潜在部署节点的描述信息以及至少两个部署喜好描述信息；其中，所述至少两个潜在部署节点的描述信息中的每一个潜在部署节点的描述信息包括该潜在部署节点的节点信息以及部署条件，所述至少两个部署喜好描述信息中的每一个部署喜好描述信息包括该部署喜好对应的需要部署的节点的部署信息；
    根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点的节点信息和部署信息；
    将确定的需要部署的节点的节点信息和部署信息发送给虚拟基础设施管理器。
  2. 如权利要求1所述的方法，其特征在于，所述部署条件包括部署标识，所述根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点的节点信息和部署信息，具体为：
    对于所述至少两个潜在部署节点的描述信息中的每一个潜在节点的描述信息，比较所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识；
    当所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识相匹配时，确定该潜在部署节点为需要部署的节点；
    获取所述需要部署的节点的节点信息；
    获取所述VNFD中与所述第一部署喜好标识对应的部署喜好描述信息；
    根据所述第一部署喜好标识对应的部署喜好描述信息，确定所述需要部署的节点的部署信息。
  3. 如权利要求1或2所述的方法，其特征在于，所述方法还包括：
    接收更新部署喜好的请求，所述更新部署喜好的请求包括所述VNF实例标识和第二部署喜好标识；
    根据所述VNF实例标识，获取所述VNFD；
    根据第一部署喜好标识、所述第二部署喜好标识以及所述VNFD，确定需要更新部署的节点的节点信息和部署信息；
    将确定的需要更新部署的节点的节点信息和部署信息发送给所述虚拟基础设施管理器。
  4. 如权利要求3所述的方法，其特征在于，所述根据所述第一部署喜好标识、所述第二部署喜好标识以及所述VNFD，确定需要更新部署的节点的节点信息和部署信息，具体为：
    根据所述第二部署喜好标识以及所述VNFD，确定与所述第二部署喜好标识对应的需要部署的节点；
    根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点；
    确定需要更新部署的节点；
    获取所述需要部署的节点的节点信息；
    根据所述第二部署喜好标识对应的部署喜好描述信息，确定所述需要更新部署的节点的部署信息。
  5. 如权利要求1-4任一所述的方法，其特征在于，所述节点包括虚拟部署单元VDU或者虚拟连接VL；
    所述部署信息包括VDU的弹性伸缩参数或者VL的服务质量参数。
  6. 一种虚拟网络中部署业务的装置，其特征在于，包括：
    接收单元，用于接收实例化请求，所述实例化请求包括VNF实例化对应的部署包信息和第一部署喜好标识；
    获取单元，用于根据所述VNF实例标识，获取与所述VNF实例标识对应的VNF部署模板VNFD，所述VNFD包括至少两个潜在部署节点的描述信息以及至少两个部署喜好描述信息；其中，所述至少两个潜在部署节点的描述信息中的每一个潜在部署节点的描述信息包括该潜在部署节点的节点信息以及部署条件，所述至少两个部署喜好描述信息中的每一个部署喜好描述信息包括该部署喜好对应的需要部署的节点的部署信息；
    确定单元，用于根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点的节点信息和部署信息；
    发送单元，用于将确定的需要部署的节点的节点信息和部署信息发送给虚拟基础设施管理器VIM。
  7. 如权利要求6所述的装置，其特征在于，所述部署条件包括部署标识，所述确定单元，用于根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点的节点信息和部署信息，具体为：
    对于所述至少两个潜在部署节点的描述信息中的每一个潜在节点的描述信息，比较所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识；
    当所述第一部署喜好标识与该潜在部署节点的部署条件包括的部署标识相匹配时，确定该潜在部署节点为需要部署的节点；
    获取所述需要部署的节点的节点信息；
    获取所述VNFD中与所述第一部署喜好标识对应的部署喜好描述信息；
    根据所述第一部署喜好标识对应的部署喜好描述信息，确定所述需要部署的节点的部署信息。
  8. 如权利要求6或7所述的装置，其特征在于，
    所述接收单元，还用于接收更新部署喜好的请求，所述更新部署喜好的请求包所述VNF实例标识和第二部署喜好标识；
    根据所述VNF实例标识，获取所述VNFD；
    根据第一部署喜好标识、所述第二部署喜好标识以及所述VNFD，确定需要更新部署的节点的节点信息和部署信息；
    将确定的需要更新部署的节点的节点信息和部署信息发送给虚拟基础设施管理器VIM。
  9. 如权利要求8所述的装置，其特征在于，所述确定单元，还用于根据所述第二部署喜好标识以及所述VNFD，确定需要更新部署的节点的节点信息和部署信息，具体为：
    根据所述第二部署喜好标识以及所述VNFD，确定与所述第二部署喜好标识对应的需要部署的节点；
    根据所述第一部署喜好标识以及所述VNFD，确定与所述第一部署喜好标识对应的需要部署的节点；
    确定需要更新部署的节点；
    获取所述需要部署的节点的节点信息；
    根据所述第二部署喜好标识对应的部署喜好描述信息，确定所述需要更新部署的节点的部署信息。
  10. 如权利要求6-9任一所述的装置，其特征在于，所述节点包括虚拟部署单元VDU或者虚拟连接VL；
    所述部署信息包括VDU的弹性伸缩参数或者VL的服务质量参数。
  11. 一种虚拟网络中部署业务的装置，其特征在于，包括：处理器和存储器，其中，
    所述存储器中存有计算机可读程序；
    所述处理器通过运行所述存储器中的程序，以用于完成上述权利要求1至5所述的方法。
PCT/CN2017/090891 2016-08-05 2017-06-29 一种虚拟化网络中业务部署的方法和装置 Ceased WO2018024059A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17836241.4A EP3471342A4 (en) 2016-08-05 2017-06-29 METHOD AND DEVICE FOR DEPLOYING SERVICE IN A VIRTUALIZED NETWORK
US16/244,592 US10700928B2 (en) 2016-08-05 2019-01-10 Method and apparatus for deploying service in virtualized network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610643597.0A CN107689882B (zh) 2016-08-05 2016-08-05 一种虚拟化网络中业务部署的方法和装置
CN201610643597.0 2016-08-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/244,592 Continuation US10700928B2 (en) 2016-08-05 2019-01-10 Method and apparatus for deploying service in virtualized network

Publications (1)

Publication Number Publication Date
WO2018024059A1 true WO2018024059A1 (zh) 2018-02-08

Family

ID=61072471

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/090891 Ceased WO2018024059A1 (zh) 2016-08-05 2017-06-29 一种虚拟化网络中业务部署的方法和装置

Country Status (4)

Country Link
US (1) US10700928B2 (zh)
EP (1) EP3471342A4 (zh)
CN (1) CN107689882B (zh)
WO (1) WO2018024059A1 (zh)

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115037605B (zh) 2016-10-05 2025-04-18 交互数字专利控股公司 核心网络
FR3071948A1 (fr) * 2017-09-29 2019-04-05 Orange Procede et dispositif de traitement d'une requete d'instanciation d'un service reseau.
US11075925B2 (en) 2018-01-31 2021-07-27 EMC IP Holding Company LLC System and method to enable component inventory and compliance in the platform
WO2019174000A1 (zh) * 2018-03-15 2019-09-19 华为技术有限公司 用于业务管理的方法和装置
CN110300007B (zh) * 2018-03-22 2022-03-29 中兴通讯股份有限公司 Vnfd多部署规格的部署方法、装置、网元设备、管理设备及存储介质
CN110324164B (zh) * 2018-03-29 2020-10-16 华为技术有限公司 一种网络切片的部署方法及装置
US11086738B2 (en) 2018-04-24 2021-08-10 EMC IP Holding Company LLC System and method to automate solution level contextual support
US10795756B2 (en) 2018-04-24 2020-10-06 EMC IP Holding Company LLC System and method to predictively service and support the solution
CN110661641B (zh) 2018-06-29 2021-07-16 华为技术有限公司 一种虚拟网络功能vnf部署方法及装置
JP6947129B2 (ja) * 2018-07-05 2021-10-13 日本電信電話株式会社 管理装置およびネットワーク管理方法
US11599422B2 (en) 2018-10-16 2023-03-07 EMC IP Holding Company LLC System and method for device independent backup in distributed system
CN111143023B (zh) * 2018-11-05 2024-10-18 中兴通讯股份有限公司 一种资源变更的方法及装置、设备、存储介质
US10797968B2 (en) 2018-11-15 2020-10-06 Cisco Technology, Inc. Automated provisioning of radios in a virtual radio access network
CN111221618B (zh) * 2018-11-23 2024-01-30 华为技术有限公司 一种容器化虚拟网络功能的部署方法和装置
CN111221619B (zh) * 2018-11-27 2023-09-08 中国移动通信集团江西有限公司 一种业务开通和编排的方法、装置及设备
CN111371578B (zh) * 2018-12-26 2021-11-30 华为技术有限公司 部署虚拟化网络功能的方法和装置
CN111416727B (zh) * 2019-01-07 2023-05-09 中国移动通信有限公司研究院 Vnf上载实例化方法及装置
CN111443984B (zh) * 2019-01-17 2023-03-31 中国移动通信有限公司研究院 网络功能虚拟化nvf系统的容器部署方法及装置
CN109889377B (zh) * 2019-01-29 2022-03-25 京信网络系统股份有限公司 基于Openstack的NFV系统中部署VNF的方法和装置
US11102087B2 (en) * 2019-04-05 2021-08-24 At&T Intellectual Property I, L.P. Service deployment for geo-distributed edge clouds
CN111800442B (zh) * 2019-04-08 2022-10-28 阿里巴巴集团控股有限公司 网络系统、镜像管理方法、设备及存储介质
US10862761B2 (en) * 2019-04-29 2020-12-08 EMC IP Holding Company LLC System and method for management of distributed systems
CN112087311B (zh) 2019-06-14 2022-04-12 华为技术有限公司 一种虚拟网络功能vnf部署方法及装置
US11301557B2 (en) 2019-07-19 2022-04-12 Dell Products L.P. System and method for data processing device management
CN112463285A (zh) * 2019-09-06 2021-03-09 中国移动通信有限公司研究院 一种部署虚拟化的网络功能模块的方法及设备
US11418429B2 (en) 2019-11-01 2022-08-16 Microsoft Technology Licensing, Llc Route anomaly detection and remediation
US11132217B2 (en) * 2019-11-03 2021-09-28 Microsoft Technology Licensing, Llc Cloud-based managed networking service that enables users to consume managed virtualized network functions at edge locations
CN112764873B (zh) 2019-11-05 2023-07-14 华为技术有限公司 实例化ns的方法及nfvo
CN113127138B (zh) * 2019-12-31 2024-04-16 西安华为技术有限公司 虚拟化网络功能部署方法、装置和系统
CN113138833A (zh) * 2020-01-19 2021-07-20 华为技术有限公司 一种部署虚拟机的方法及相关装置
US12047241B2 (en) * 2020-02-05 2024-07-23 Telefonaktiebolaget Lm Ericsson (Publ) Identifying an instance of a virtual network function
EP4101127B1 (en) 2020-02-06 2025-04-09 Telefonaktiebolaget LM Ericsson (publ) Controlling network node, and method performed therein
CN113760440B (zh) * 2020-06-03 2024-09-24 华为技术有限公司 一种虚拟化的网络服务的部署方法及装置
CN113495776B (zh) * 2020-03-18 2025-05-16 华为技术有限公司 Vnf实例化方法及装置
US12500778B2 (en) * 2020-05-26 2025-12-16 Verizon Patent And Licensing Inc. Systems and methods for managing public key infrastructure certificates for components of a network
CN112667247B (zh) * 2020-12-11 2025-07-04 深圳市远行科技股份有限公司 服务管理方法、系统、终端及存储介质
US11785468B2 (en) * 2021-02-26 2023-10-10 Microsoft Technology Licensing, Llc Subscriber identification module (SIM) management for cloud-based private mobile networks
EP4290819A4 (en) * 2021-03-18 2024-06-26 Huawei Technologies Co., Ltd. Service deployment method, apparatus, and system
CN115514652B (zh) * 2022-09-19 2023-12-19 北京航空航天大学 服务功能链部署方法、装备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
WO2016070609A1 (zh) * 2014-11-04 2016-05-12 中兴通讯股份有限公司 实现vnf实例化的方法、系统及nfvo和vnfm
CN105634782A (zh) * 2014-11-06 2016-06-01 华为技术有限公司 一种实例化vnf的方法及网元管理设备
CN105791147A (zh) * 2014-12-26 2016-07-20 华为技术有限公司 负载均衡器的连接方法、业务的实例化部署方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9838483B2 (en) * 2013-11-21 2017-12-05 Oracle International Corporation Methods, systems, and computer readable media for a network function virtualization information concentrator
EP2955631B1 (en) * 2014-06-09 2019-05-01 Nokia Solutions and Networks Oy Controlling of virtualized network functions for usage in communication network
CN105791073B (zh) * 2014-12-23 2019-07-19 华为技术有限公司 一种虚拟化网络中业务部署的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
WO2016070609A1 (zh) * 2014-11-04 2016-05-12 中兴通讯股份有限公司 实现vnf实例化的方法、系统及nfvo和vnfm
CN105634782A (zh) * 2014-11-06 2016-06-01 华为技术有限公司 一种实例化vnf的方法及网元管理设备
CN105791147A (zh) * 2014-12-26 2016-07-20 华为技术有限公司 负载均衡器的连接方法、业务的实例化部署方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"Network Functions Virtualisation (NFV); Management and Orchestration", ETSI GS NFV-MAN 001 V1.1.1, 31 December 2014 (2014-12-31), pages 37 - 53, 65, 108-117, XP014311783 *
OASIS: "TOSCA Simple Profile for Network Functions Virtualization (NFV) Version 1.0 Committee Specification Draft 03", TOSCA-NFV-V1.0-CSD03, 17 March 2016 (2016-03-17), XP055560060 *
See also references of EP3471342A4

Also Published As

Publication number Publication date
CN107689882B (zh) 2020-04-21
EP3471342A4 (en) 2019-05-22
EP3471342A1 (en) 2019-04-17
CN107689882A (zh) 2018-02-13
US20190149408A1 (en) 2019-05-16
US10700928B2 (en) 2020-06-30

Similar Documents

Publication Publication Date Title
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US10701139B2 (en) Life cycle management method and apparatus
US20220377045A1 (en) Network virtualization of containers in computing systems
CN106301829B (zh) 一种网络业务扩容的方法和装置
US11611481B2 (en) Policy management method and system, and apparatus
WO2020135799A1 (zh) Vnf服务实例化方法及装置
WO2019184967A1 (zh) 一种网络切片的部署方法及装置
WO2018006676A1 (zh) 加速资源处理方法、装置及网络功能虚拟化系统
WO2017113201A1 (zh) 一种网络服务的生命周期管理方法及设备
US12056094B2 (en) Method and apparatus for deploying virtualised network function
WO2018072612A1 (zh) 一种切片实例的管理方法及装置
WO2018072503A1 (zh) 软件修改的发起方法、发布元数据的方法及装置
WO2018090299A1 (zh) 网络服务生命周期管理的许可方法和装置
CN109995552B (zh) Vnf服务实例化方法及装置
WO2017185251A1 (zh) Vnfm的确定方法和网络功能虚拟化编排器
WO2016183832A1 (zh) 一种网络业务实例化的方法及设备
CN105791147B (zh) 负载均衡器的连接方法、业务的实例化部署方法及装置
CN112087311A (zh) 一种虚拟网络功能vnf部署方法及装置
CN113342456A (zh) 一种连接方法、装置、设备和存储介质
CN112889247B (zh) Vnf服务实例化方法及装置
US20250293933A1 (en) Instantiation method and apparatus for virtualised network function vnf
CN120785935A (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: 17836241

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017836241

Country of ref document: EP

Effective date: 20190110

NENP Non-entry into the national phase

Ref country code: DE