WO2017181875A1 - 虚拟化网络的部署方法和部署系统 - Google Patents

虚拟化网络的部署方法和部署系统 Download PDF

Info

Publication number
WO2017181875A1
WO2017181875A1 PCT/CN2017/080110 CN2017080110W WO2017181875A1 WO 2017181875 A1 WO2017181875 A1 WO 2017181875A1 CN 2017080110 W CN2017080110 W CN 2017080110W WO 2017181875 A1 WO2017181875 A1 WO 2017181875A1
Authority
WO
WIPO (PCT)
Prior art keywords
nfvo
deployment
information
request
virtualized network
Prior art date
Application number
PCT/CN2017/080110
Other languages
English (en)
French (fr)
Inventor
赵洁
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2017181875A1 publication Critical patent/WO2017181875A1/zh

Links

Images

Classifications

    • 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
    • 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
    • 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/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/131—Protocols for games, networked simulations or virtual reality

Definitions

  • the present invention relates to the field of virtual network technologies, and in particular, to a method and system for deploying a virtualized network.
  • Network Function Virtualization is a standard-setting project under the European Telecommunications Standards Institute (ETSI), which sets industry-wide standards for network cloudization. Based on modern IT virtualization technology, it provides a new network product environment, reducing costs, improving efficiency and increasing agility.
  • Software processing that carries many functions by using general-purpose hardware such as x86 and virtualization technology. Thereby reducing the cost of equipment expensive in the network.
  • Through software and hardware decoupling and functional abstraction, network device functions are no longer dependent on dedicated hardware. Resources can be fully and flexibly shared, enabling rapid development and deployment of new services, and automatic deployment, elastic scaling, and fault isolation based on actual business requirements. And self-healing.
  • the NFV deploys a network service (NS), that is, instantiates a network service, including a network function virtualization orchestrator (NFVO) to check the received virtual network service deployment request.
  • NS network service
  • NFVO network function virtualization orchestrator
  • VNF virtual network function
  • VNFM Virtual Network Function Manager
  • the application scenarios considered in the prior art are relatively simple, mainly to uniformly deploy a network service, and the service instantiation instantiation belongs to one management domain, but in reality, a network is deployed, and the service programming instantiation may belong to multiple management domains, or A network service may consist of multiple parts, each part being responsible for the deployment and management of the virtualized network by different management domains.
  • the method of deploying network services in the prior art is not applicable to the case of deploying multiple parts.
  • the deployment method and deployment system of a virtualized network provided by the present invention can implement deployment of a virtual network service composed of multiple parts.
  • the present invention provides a method for deploying a virtualized network, the method comprising:
  • the first network function virtualization orchestrator NFVO receives the first part of the deployment request sent by the service operation and management platform, and the first part of the deployment request includes an indication of resource reservation; after the first NFVO completes the resource reservation request, the service is performed to the service And the management platform sends the resource reservation completion information;
  • the second NFVO receives the second part of the deployment request sent by the service operation and management platform; the second NFVO checks the layout information of the first part that the second part needs to rely on, obtains the arrangement information of the first part, and performs the first part according to the arrangement information of the first part. The second NFVO determines whether the first part of the programming information meets the programming requirements of the second part; when the first part of the programming information satisfies the second part of the programming requirements, the second NFVO sends the acceptance information to the business operation and management platform. , accepting information for indicating acceptance of the first part of the arrangement information;
  • the first NFVO receives the resource allocation request sent by the service operation and management platform, and requests the resource allocation of the first part;
  • the second NFVO requests the resource allocation of the second part.
  • the resource reservation is performed on the part that needs to be deployed, and the resource allocation is not performed after the resource is reserved. After all the parts are deployed, the resource allocation is performed; and other parts are
  • the deployment implements the deployment of a multi-part virtualized network service based on the orchestration information of the deployed network. When performing virtualized network deployment, different parts of the network can coordinate with each other, improving the flexibility and versatility of network deployment.
  • the deployment method further includes:
  • the first NFVO requests the first virtualized infrastructure manager VIM resource reservation
  • the first NFVO receives the resource reservation completion information sent by the first VIM to implement resource reservation required for deploying the first part.
  • the first network function virtualization orchestrator NFVO receives the first part sent by the service operation and management platform After the deployment request, the deployment method also includes:
  • the first NFVO generates the first part of the programming information.
  • the second NFVO obtains the information of the first part, including:
  • the second NFVO acquires the first part of the scheduling information from the first NFVO, so that the second NFVO obtains the first part of the scheduling information through the interface between the NFVOs.
  • the second partial deployment request includes an IP address of the first NFVO to implement the second NFVO according to the first NFVO
  • the IP address directly requests the first NFVO to obtain the scheduling information of the first part.
  • the second NFVO obtains the first part of the programming information, including:
  • the second NFVO may obtain the first part of the orchestration information from the first NFVO through the service operation and management platform, and the specific process may send the acquisition request to the service operation and management platform by the second NFVO, and the service operation and management platform forwards the acquisition to the first NFVO.
  • the second NFVO receives the first part of the scheduling information sent by the first NFVO through the service operation and management platform.
  • the second NFVO acquisition The first part of the layout information, including:
  • the second NFVO obtains the first part of the programming information from the capability open platform.
  • the deployment method further includes:
  • the first NFVO sends the first part of the programming information to the capability open platform, so that the second NFVO obtains the first part of the programming information from the capability open platform.
  • the second NFVO obtains the information of the first part, and may obtain the information of the first part by using an interface between the MANOs provided by the operator.
  • the second NFVO may be from the first through the interface between the MANO provided by the operator and the service operation and management platform from the first NFVO gets the first part of the layout information.
  • the second NFVO may obtain the first part of the orchestration from the capability open platform by using an interface between MANOs provided by the operator information.
  • the scheduling information may include a virtualized network
  • the deployment location information of the function VNF is arranged according to the arrangement information of the first part, including:
  • the second part is arranged according to the deployment location information of the virtualized network function VNF.
  • the deployment method may further include:
  • the second NFVO sends a reject message to the service operation and management platform, where the reject message is used to indicate that the first part is not accepted. Orchestration information, resending the first partial deployment request.
  • the present invention provides a deployment system, including: a first network function virtualization orchestrator NFVO and a second NFVO;
  • the first NFVO is configured to receive a first part of the deployment request sent by the service operation and management platform, where the first part of the deployment request includes an indication of resource reservation; and the resource reservation completion information is sent to the service operation and management platform;
  • the second NFVO is configured to receive a second part of the deployment request sent by the service operation and management platform; obtain the first part of the arrangement information; and perform the second part of the arrangement according to the first part of the arrangement information;
  • the second NFVO When the arrangement information of the first part satisfies the scheduling requirement of the second part, the second NFVO sends the acceptance information to the service operation and management platform, and the acceptance information is used to indicate acceptance of the arrangement information of the first part;
  • the first NFVO is further configured to receive a resource allocation request sent by the service operation and management platform, requesting resource allocation of the first part;
  • the second NFVO is used to request the resource allocation of the second part.
  • the resource reservation is performed on the part to be deployed, and the resource allocation is not performed after the resource is reserved. After all the parts are deployed, the resource allocation is performed, and the virtualized network service is realized.
  • the components are composed, when the virtualized network is deployed, different parts of the network can be coordinated with each other, which improves the flexibility and versatility of the network deployment.
  • an embodiment of the present invention provides a method for deploying a virtualized network, where the virtualized network consists of multiple parts. Composition, the deployment method includes:
  • the first virtualized network function manager VNFM receives the first partial deployment request sent by the NFVO;
  • the second VNFM receives the second part of the deployment request sent by the NFVO, and the second part of the deployment request includes the first part of the scheduling information;
  • the second VNFM verifies the second part of the deployment request
  • the second VNFM When the arrangement information of the first part satisfies the scheduling requirement of the second part, the second VNFM sends an acceptance message to the NFVO, the acceptance information is used to indicate acceptance of the arrangement information of the first part, and instructs the NFVO to request the resource allocation of the first part and the second part.
  • the resource allocation is not performed after the resource is reserved. After all the parts are deployed, the resource allocation is performed.
  • the virtualized network service is composed of multiple parts, the virtualized network is executed. When deployed, different parts of the network can be coordinated with each other, improving the flexibility and versatility of network deployment.
  • the present invention provides a deployment system, where the deployment system includes a first virtualized network function manager VNFM and a second VNFM;
  • a first VNFM configured to receive a first part of the deployment request sent by the network function virtualization orchestrator NFVO after completing the first part of the resource reservation;
  • a second VNFM configured to receive a second part of the deployment request sent by the NFVO, where the second part of the deployment request includes the first part of the scheduling information
  • the second VNFM is further configured to verify the second part of the deployment request; when the first part of the scheduling information satisfies the scheduling requirement of the second part, the second VNFM is used to send the acceptance information to the NFVO, and the acceptance information is used to indicate acceptance Part of the information is programmed and instructs NFVO to request resource allocation for the first and second parts.
  • the resource reservation is performed on the part that needs to be deployed, and the resource allocation is not performed after the resource is reserved. After all the parts are deployed, the resource allocation is performed; and other parts are
  • the deployment implements the deployment of a multi-part virtualized network service based on the orchestration information of the deployed network. When performing virtualized network deployment, different parts of the network can coordinate with each other, improving the flexibility and versatility of network deployment.
  • Figure 1 is a network function virtualization NFV architecture diagram
  • FIG. 2 is an application scenario of a method for deploying a virtualized network according to an embodiment of the present disclosure
  • FIG. 3 is another application scenario of a method for deploying a virtualized network according to an embodiment of the present disclosure
  • FIG. 4 is still another application scenario of a method for deploying a virtualized network according to an embodiment of the present disclosure
  • FIG. 5 is a schematic structural diagram of a network function virtualization orchestrator NFVO according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of still another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of still another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 11 is a flowchart of a method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 12 is a flowchart of another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 13 is a flowchart of still another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 14 is a flowchart of still another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a deployment system according to an embodiment of the present disclosure.
  • FIG. 16 is a flowchart of a method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 17 is a flowchart of another method for deploying a virtualized network according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of a deployment system according to an embodiment of the present invention.
  • Figure 1 shows the network function virtualization NFV architecture.
  • the architecture diagram is the reference architecture defined in the NFV ISG.
  • NFV-MANO NFV Management and Orchestration
  • NFVO Orchestrator Network Function Virtualization Orchestrator
  • VNFM Virtual Network Function Manager
  • VIM Virtualization Infrastructure Manager
  • NFVO is mainly used to implement network service (NS) lifecycle management (such as deployment/expansion/reduction/downline) in the carrier domain (one or more data centers), and network function virtualization infrastructure layer.
  • NS network service
  • NFVI Virtualised Network Function Infrastructure
  • Orchestrator decomposes the requirements of each VNF (Virtualised Network Functation) according to the Network Service Descriptor (NSD), and virtualizes the network with VNFM. Deployment of the function (Virtual Network Functition, VNF).
  • VNFM is mainly used to implement VNF lifecycle management, such as deployment/expansion/contraction/downline automation.
  • VNFM decomposes the virtual resource requirements such as virtual machines according to the template and VNF capacity requirements, and cooperates with NFVO and VIM. Instantiation of VNF.
  • VIM is an I-layer management system, such as VMware, Openstack, which implements management and monitoring of infrastructure layer resources (including computing, storage, and network resources).
  • infrastructure layer resources including computing, storage, and network resources.
  • the NFV architecture also includes the EMS/NMS (Element Management System/Network Management System).
  • EMS/NMS is the network management system. It is used to vertically pull through the S layer I layer fault monitoring and demarcation, and maintain the management capabilities of the existing network management. Manage clouded and non-clouded network elements.
  • the Operation-Support System/Business Support System can manage clouded and non-clouded network elements in a unified manner.
  • a network service deployed may include multiple parts, such as deploying a vertical industry application, possibly deploying an Evolved Packet Core (EPC), IP Multimedia Subsystem (IMS). And the IoT connection management platform three parts, each part can include several VNFs.
  • EPC Evolved Packet Core
  • IMS IP Multimedia Subsystem
  • Each part may be provided by a different operator, and each part may be provided by a different vendor (supplier); the network element in the part provided by each operator may be provided by other operators or third-party institutions; Administrative Conveniently, each vendor will provide operators with different Mobile Virtual Network Operator (MVNO) systems or different NVFMs.
  • MVNO Mobile Virtual Network Operator
  • each part needs to be negotiated, or it needs to be deployed with the operator or The MANO of the third-party organization negotiates, including the deployment location of the virtualized network function VNF, the connectivity of the VNF, and the quality of service (QoS) requirements.
  • QoS quality of service
  • the embodiment of the invention provides a method for deploying a virtualized network and a deployment system, which can be flexibly applied to a scenario in which a virtualized network deployment is performed when a virtual network service is composed of multiple parts.
  • the scenario shown in Figure 2 to Figure 4 deploying a virtual network.
  • the virtual network in Figure 2 consists of two parts, which can be the core network EPC and IoT connection management platform. These two parts are provided by different vendors or third parties. That is, they belong to two different management domains, each of which has an independent network function virtualization orchestrator NFVO and a virtualized network function manager VNFM.
  • the virtual network in Figure 3 also includes two parts, namely the core network EPC and IoT connection management platform, wherein the core network EPC part is provided by one operator, and the IoT connection management platform is provided by another operator, that is, the two parts belong to two Administrative domains.
  • the virtual network in Figure 4 consists of three parts, namely the core network EPC, IMS and IoT connection management platform, each part is provided by different equipment vendors, with independent virtualized network function manager VNFM, but adopts a network function virtual The NFVO, that is, three parts belong to three administrative domains.
  • the deployment method and the deployment system provided by the embodiments of the present invention can be applied not only to the above-described virtualized network composed of the core network EPC and the IoT connection management platform, but also to the core network described above.
  • a virtualized network composed of parts such as EPC, IMS, and IoT connection management platform and not limited to the system described above, it can also be applied to a deployment system including other parts, that is, virtualization composed of multiple components.
  • the internet is a virtualized network composed of the core network EPC and the IoT connection management platform, and not limited to the system described above.
  • a virtualized network that needs to be deployed in the embodiment of the present invention may include multiple parts, and each part may be deployed by an independent management domain.
  • the first part of the deployment needs to be resource reserved (only resource reservation is performed, and resource allocation is not performed), and the first part of the arrangement information is obtained, and the arrangement information refers to the virtualization in the first part.
  • a virtualized network deployment when there are other parts than the first part and the second part, the deployment process of the first part and the second part is repeated until all parts are deployed. After all the parts are deployed, the resource allocation of each part is performed, so that when the virtualized network service is composed of multiple parts, the virtualized network is deployed, and the parts can be coordinated with each other to improve the flexibility and generality of the virtualized network deployment. Sex.
  • the scheduling information of all deployed completion parts needs to be obtained.
  • the deployment may be understood as a process of scheduling and planning a virtualized network function VNF in each part of the network service.
  • the deployment system may include multiple parts, each part may be arranged and planned by the independent network function virtualization orchestrator NFVO, or may be virtualized by the same network function orchestrator NFVO pair. Network business is organized and planned.
  • FIG. 5 is a schematic structural diagram of a network function virtualization orchestrator NFVO according to an embodiment of the present invention.
  • the network function virtualization orchestrator NFVO 200 includes a receiver 210, a transmitter 220, a processor 230, a memory 240, a communication interface 250, and a communication bus 260.
  • the receiver 210, the transmitter 220, the processor 230, the memory 240, and the communication interface 250 are connected by a communication bus 260 and complete communication with each other.
  • the receiver 210 and the transmitter 220 are configured to receive data transmitted by other devices or send data and instructions to other devices through the communication interface 250.
  • Memory 240 is used to store instructions and data.
  • the processor 230 is configured to call instructions in the memory and perform corresponding operations.
  • the processor 230 may be a central processing unit (CPU), and the processor 230 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), Ready-to-use programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • Memory 240 can include read only memory and random access memory and provides instructions and data to processor 230.
  • a portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the communication bus 260 may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like. However, for clarity of description, various buses are labeled as communication bus 260 in the figure.
  • FIG. 6 is a flowchart of a method for deploying a virtualized network according to an embodiment of the present invention.
  • the execution method of the deployment method 300 is a network function virtualization orchestrator NFVO in the deployment system, and the deployment method may include the following steps:
  • the first network function virtualization orchestrator NFVO receives a first part of the deployment request sent by the service operation and management platform, where the first part of the deployment request includes an indication of resource reservation;
  • the first NFVO sends resource reservation completion information to the service operation and management platform.
  • the second NFVO receives a second part of the deployment request sent by the service operation and management platform.
  • the second NFVO acquires the arrangement information of the first part, and performs the second part of the arrangement according to the arrangement information of the first part;
  • the second NFVO when the scheduling information of the first part satisfies the scheduling requirement of the second part, the second NFVO sends the acceptance information to the service operation and management platform, and the acceptance information is used to indicate that the arrangement information of the first part is accepted;
  • the first NFVO receives a resource allocation request sent by the service operation and management platform, and requests resource allocation of the first part.
  • the second NFVO requests resource allocation of the second part.
  • the virtualized network is composed of multiple parts.
  • a virtual network needs to be deployed for a vertical industry application, and the core network EPC and IoT connection management platform may need to be deployed.
  • Each part is organized and planned by a separate network function virtualization orchestrator, NFVO, for each part of the virtualized network.
  • NFVO network function virtualization orchestrator
  • the first part of the embodiment of the invention may include multiple parts of the virtualized network that need to be deployed.
  • the resource reservation only performs resource reservation, and does not really allocate resource reservation.
  • each part included in the virtualized network needs to perform resource reservation, but the part may be considered as the second part in the embodiment of the present invention except for the last deployed part of the virtual network.
  • the first part is other parts of the virtual network except the last part to be deployed.
  • the deployed part of the NFVO needs to obtain the arrangement information of all parts that have been deployed to complete. Virtualize the deployment of the network and request resource allocation.
  • the first NFVO when the virtualized network is deployed, the first NFVO receives a first part of the resource reservation request sent by the Operation-Support System/Business Support System (OSS/BSS), where the first part of the deployment request includes An indication indicating that the first NFVO performs resource reservation.
  • the first NFVO needs to perform the first part of the scheduling and planning according to the requirements of the virtualized network, complete the selection of the network template, and set the VNF configuration data of each virtualized network function, that is, generate the first part of the programming information, And request resource reservation.
  • OSS/BSS Operation-Support System/Business Support System
  • the first NFVO When the first NFVO completes requesting resource reservation, executing S302, the first NFVO sends resource reservation completion information to the OSS/BSS to notify the OSS/BSS to complete the resource reservation of the first part.
  • the second NFVO receives the second partial deployment request sent by the OSS/BSS to instruct the second NFVO to deploy the second part.
  • the second NFVO needs to obtain the second part of the scheduling information on which the second part deploys the virtualized network, the arrangement information includes location information of the virtualized network function VNF, and may also include virtual The number of network functions VNF, virtual link VL information, quality service QoS and other information.
  • the second NFVO arranges and plans information such as the location of the virtualized network function VNF that needs to be deployed in the second part according to the arrangement information of the first part acquired in S330, and determines that the second part is deployed after the second part is deployed. Whether the programming information meets the programming requirements of the second part, if yes, execute S350, otherwise execute S350'.
  • the OSS/BSS transmits information that accepts the first part of the arrangement information, that is, the arrangement of the first part and the planning scheme, that is, the acceptance information.
  • the first NFVO sends an acquisition resource allocation request to the virtualized infrastructure management system VIM in the first part according to the received acceptance information sent by the second NFVO to complete resource allocation to the first part.
  • the second NFVO when the second NFVO sends the acceptance information to the first NFVO, that is, when the first part of the arrangement information satisfies the scheduling requirement of the second part, the information may be directly sent to the infrastructure management system VIM in the second part.
  • the resource allocator requests to complete the resource allocation of the second part, that is, execute S307.
  • the deployment method may further include:
  • the second NFVO when the arrangement information of the first part does not satisfy the scheduling requirement of the second part, the second NFVO is operated to the business And the management platform sends a rejection message, the rejection message is used to indicate that the first part of the scheduling information is not accepted;
  • the first NFVO receiving service operation and management platform resends the first partial deployment request.
  • the method for deploying a virtualized network performed by the embodiment of the present invention performs resource reservation on the part to be deployed, and does not perform resource allocation after the resource is reserved. After all the parts are deployed, the resource allocation is implemented.
  • the virtualized network service is composed of multiple parts, when the virtualized network is deployed, different parts of the network can be coordinated with each other, which improves the flexibility and versatility of the network deployment.
  • the deployment method 300 further includes:
  • the first NFVO generates the first part of the programming information
  • the first NFVO performs the first part of the virtual network planning according to the deployment of the first part of the virtualized network deployment requirement, completes the selection of the network template, and configures the configuration data of each virtualized network function VNF to complete the first part of the scheduling information.
  • the scheduling information may include information such as location information, quantity, virtual link VL, quality of service QoS, etc. of the virtualized network function.
  • the second NFVO acquires the scheduling information of the first part, and may include: acquiring, by the second NFVO, the first part of the scheduling information from the capability opening platform.
  • the second NFVO obtains the information of the first part of the information from the capability open platform, which may specifically include:
  • the second NFVO sends an acquisition request to the capability open platform, where the acquisition request is used to indicate that the first part of the scheduling information is obtained.
  • the second NFVO receives the scheduling information of the first part sent by the open platform.
  • the second NFVO checks, according to the received second partial deployment request, the second part of the virtualized network function VNF depends on which virtualized network functions and virtual links in the first part, that is, depends on the first part.
  • Which programming information for example, the second part is the IoT connection management platform, the first part is the core network EPC, then the second NFVO check IoT connection management platform depends on which virtualized network functions VNF and virtual link VL in the core network EPC
  • the second part is IMS
  • the first part is the core network EPC
  • the second NFVO check IMS needs to depend on which virtualized network functions VNF and virtual link VL in the core network EPC.
  • the second NFVO After the second NFVO determines that the second part needs to rely on which arrangement information in the first part, the second NFVO sends an acquisition request to the capability open platform, and acquires the information of the first part of the dependency relationship with the second part for the capability open platform. And, according to the obtaining request, sending, to the second NFVO, the scheduling information of the first part having the dependency of the second part; the second NFVO receiving the scheduling information of the first part having the dependency of the second part sent by the openness platform, and according to the Part of the layout information is organized and planned for the second part.
  • the deployment method 300 further includes:
  • the first NFVO sends the first part of the scheduling information to the capability open platform.
  • the first part of the scheduling information may be sent to the capability open platform for the second NFVO to obtain from the capability open platform.
  • the second part has the layout information of the first part of the dependency.
  • the orchestration information may include a location of the virtualized network function VNF deployment. It should be noted that, in the embodiment of the present invention, the scheduling information may further include the number of virtualized network functions, an IP address, virtual link VL information, and/or configuration information, and the like.
  • the scheduling information sent by the first NFVO to the capability open platform may determine the information to be sent according to the relationship between the various parts in the virtualized network, or the relationship between the various management domains, and therefore, each The arrangement information sent between the parts may be different, that is to say, the arrangement information of the first part sent by the first NFVO to the capability open center is different, as shown in Table 1.
  • the relationship between the management domains is tight, the security requirements are not high.
  • the mutual security of each part deploying the virtualized network function VNF is low. It can send internal information used within the management domain, such as the data center geographic location and data center name in the deployment location of the virtualized network function VNF.
  • the relationship between the management domains is not tight, in order to improve security and avoid exposing information such as the architecture inside the management domain, send information that the management domain presents externally, such as the data center geographic location or port in the virtualized network function VNF deployment location. Information such as the IP address of the external network.
  • the virtualized network function VNF and the virtual link VL may be used as the granularity, that is, in units of VNF and VL, as shown in Table 1, the first NFVO direction
  • the capability open platform sends the first part of the deployed virtualized network function VNF. If two VNFs have been deployed, the ID of the virtualized network function in the first virtualized network function VNF will be deployed. After the information such as the port, the network, and the configuration data is sent one by one, the information in the second virtualized network VNF is sent.
  • the first one is also The ID, quality of service QoS, and configuration data of the virtualized network function in the virtual link VL are completed one by one, and then the pieces of information in the other virtual link VL are transmitted.
  • the orchestration information may include a deployment location in the virtualized network function VNF, and may also include a virtualized network function VNF.
  • the ID of the virtualized network function information such as location, port, network, and configuration data.
  • the arrangement information transmitted at the granularity of the virtual link VL includes information such as an ID of the virtualized network function in the virtual link VL, quality of service QoS, and configuration data.
  • the first NFVO may also send only the VNF and VL with the link relationship between the management domain and the external to the capability open platform.
  • the second NFVO acquires the information of the first part, and may include: the second NFVO acquires the information of the first part from the first NFVO through the service operation and management platform. .
  • the process may specifically include:
  • the second NFVO sends an acquisition request to the first NFVO through the service operation and management platform, where the acquisition request is used to indicate that the first part of the scheduling information is obtained.
  • the second NFVO receives the first part of the scheduling information sent by the first NFVO through the service operation and management platform.
  • the second NFVO sends an acquisition request to the service operation and management platform OSS/BSS to obtain the scheduling information of the first part that has a dependency relationship with the second part, and is used for the service management platform.
  • An NFVO forwards the acquisition request; the first NFVO sends the first part of the scheduling information to the second NFVO through the OSS/BSS according to the acquisition request.
  • the second NFVO acquires the information of the first part, and may include: acquiring, by the second NFVO, the information of the first part from the first NFVO.
  • the process may specifically include:
  • the second NFVO sends an acquisition request to the first NFVO, where the acquisition request is used to indicate that the first part of the scheduling information is obtained.
  • the second NFVO receives the scheduling information of the first part of the first NFVO transmission.
  • the second part of the deployment request sent by the OSS/BSS to the second NFVO includes an Internet Protocol (IP) address between the Internets of the first NFVO.
  • IP Internet Protocol
  • the second NFVO sends, to the first NFVO, the scheduling information of the first part related to the second part according to the second part deployment request; the second NFVO receives the scheduling information of the first part of the first NFVO transmission.
  • the second NFVO acquires the information of the first part, and may further include:
  • the second NFVO obtains the first part of the orchestration information through an interface provided by the operator, and the specific process may include:
  • the second NFVO sends an acquisition request by using an interface provided by the operator, the first NFVO.
  • the second NFVO receives the first part of the scheduling information sent by the first NFVO through an interface provided by the operator.
  • the interface provided by the operator may be a Potal interface provided by the operator or an open platform for the capability.
  • the capability open platform in order to distinguish the capability open platform from the previously mentioned capability open credential, Call this capability open platform the second capability open platform, and call the previously mentioned capability open platform the first capability. Open platform.
  • the second NFVO passes the second capability open platform, the business operation and management platform OSS/BSS in the second part (referred to herein as the second OSS/BSS), and the business operation and management platform OSS/BSS in the first part (herein referred to as Sending an acquisition request to the first NFVO for the first OSS/BSS), the second NFVO receiving the information of the first part of the first NFVO transmitted by the first OSS/BSS, the second capability open platform, and the second OSS/BSS.
  • the second capability open platform, the second OSS/BSS, and the first OSS/BSS transmit data or instructions to the second or first NFVO through a function of forwarding information that they have.
  • the method of sending the request or the first part of the information is sent to the first NFVO or the second NFVO by using the first OSS/BSS.
  • the specific process is similar to that of S314 and S315, and is not described here.
  • the second NFVO acquires the scheduling information of the first part, and may further include:
  • the second NFVO obtains the first part of the programming information from the first capability open platform through an interface provided by the operator.
  • the process can specifically include:
  • the second NFVO sends an acquisition request to the first capability open platform by using an interface provided by the operator, where the obtaining request is used to indicate that the first part of the scheduling information is obtained.
  • the second NFVO receives the first part of the scheduling information sent by the first capability open platform through an interface provided by the operator.
  • the scheduling information may include deployment location information of the virtualization network function VNF
  • the second NFVO may perform the second part of the scheduling information according to the scheduling information of the first part
  • the second NFVO may specifically include: The first part of the layout information of the virtualized network function VNF deployment location information is arranged in the second part.
  • the scheduling information may further include the number of virtualized network functions VNF, configuration information, such as: specifications (information that can support the number of users, etc.), virtual link VL information, and quality of service QoS information.
  • the method for deploying a virtualized network performs resource reservation for the part to be deployed, and does not perform resource allocation after the resource is reserved. After all the deployment parts complete the planning and scheduling, the resource allocation is also performed. It can be said that resources are reserved first for coordination, and the process of optimizing the deployment is realized.
  • the virtual network service is composed of multiple parts, when the virtualized network is deployed, the mutual coordination between the parts is realized, and the flexibility of the network deployment is improved. And versatility. At the same time, it can adapt to the scenario where multiple vendors and multiple operators deploy a virtualized network at the same time, which improves the automation of deployment and improves the efficiency of deployment.
  • FIG. 11 is a flowchart of a method for deploying a virtualized network according to an embodiment of the present invention.
  • the deployment method shown in FIG. 11 can be applied to the scenario shown in FIG. 2: an operator needs to deploy a virtual network, where the virtual network includes two components, namely a core network EPC and an IoT connection management platform, and The two components are provided by different providers (equipment vendors) or third parties, that is, there are two management domains, each of which has independent NFVO and VNFM.
  • the virtual network includes two components, namely a core network EPC and an IoT connection management platform, and The two components are provided by different providers (equipment vendors) or third parties, that is, there are two management domains, each of which has independent NFVO and VNFM.
  • the EPC part includes NFVO1, VNFM1 and VIM1;
  • the IoT connection management platform part includes NFVO2 and VNFM2 And VIM2.
  • the deployment method 400 includes the following steps:
  • the OSS sends an EPC deployment request to the NFVO1.
  • the OSS requests the NFVO1 to deploy the EPC part in the virtualized network, where the EPC deployment request includes an indication of resource reservation, which is used to indicate that the NFVO1 requests to perform resource reservation, because other parts of the virtualized network are deployed, such as
  • the IoT connects to the management platform, so the OSS instructs NFVO1 to only perform resource reservation.
  • S401 only performs resource reservation and does not perform resource allocation.
  • the NFVO1 sends a resource reservation request to the VIM1 according to the requirement of the EPC to deploy the virtualized network.
  • NFVO1 performs EPC network planning according to the requirements of deploying the core network EPC in the virtualized network, completes the selection of the network template, and configures the virtualized network function VNF, that is, sets configuration data, and NFVO1 then requests the VIM1.
  • the required resources are reserved, and the resources may include information such as a virtualized network function VNF, a virtual link VL, and the like.
  • the resource reservation completion information is sent to the NFVO1.
  • the NFVO1 sends an EPC deployment request to the VNFM1, and the EPC deployment request may include an NSD, a VNFD, and a parameter required for instantiation.
  • the VNFM1 verifies the start of the EPC deployment request.
  • the verification of the start of the EPC deployment request by the VNFM1 includes: checking whether the sender NFVO1 that initiates the EPC deployment request is authorized, starting the verification of the parameter validity in the EPC deployment request, and the virtualized network function VMF. Verification of life cycle management, etc.
  • the verification of the validity of the parameters may include the technical correctness of the parameters and the verification of the compliance of the policies.
  • the verification of the lifecycle management of the virtualized network function VNF may include: virtualizing the VNF lifecycle management interface of the virtualized network between the NFVO1 and the VNFM1 for each virtualized network function VNF instance required for the virtualized network service.
  • the network VNF query operation checks if there is already a VNF instance that satisfies the requirement, and if so, the VNF is part of the network service.
  • the verification completion information includes the result of the confirmation check, that is, the verification is passed.
  • the NFVO1 sends the EPC scheduling information to the capability open platform, including the location information of the virtualized network function VNF deployed by the EPC, and the virtual link VL.
  • the specific NFVO1 sends the EPC scheduling information to the capability open platform in the deployment system, including the location information of the virtualized network function VNF deployment, and the virtual link VL, which may also include configuration information, such as specifications, as shown in Table 1.
  • configuration information such as specifications, as shown in Table 1.
  • the management domain of the two parts of the EPC and IoT connection management platform is closely related and the security requirements are low, the internal information is transmitted.
  • Information such as virtual data center IDs, etc., otherwise pass external information, such as geographic location information of the data center.
  • the virtualized network function VNF and the virtual link VL may be granular, that is, the information is organized in units of VNF, VL.
  • information such as the virtualized network function VNF and the virtual link VL having the external connection relationship may be sent only to the capability opening platform.
  • the capability opening platform receives the EPC scheduling information and saves the information, and sends the received completion information to NFVO1.
  • the capability open platform saves the virtualized network function VNF, the virtual link VL, and the configuration information in the EPC deployment virtualized network, and sends an acknowledgement message to the NFVO1, where the acknowledgement message is used to indicate that the capability open platform is successfully connected.
  • Receive EPC layout information
  • the NFVO1 sends resource reservation completion information to the OSS, where the resource reservation completion information is used to notify the OSS EPC part of the resource reservation and the parameter check has been completed.
  • the OSS sends a request to the NFVO2 to start deploying the IoT connection management platform.
  • the OSS requests the NFVO2 to deploy the IoT connection management platform part of the virtualized network. Because there are only two parts of the EPC and the IoT connection management platform in the virtual network, there is no other part of the deployment after the IoT connection management platform, so the OSS is The NFVO2 sends an initial deployment IoT connection management platform request that does not need to include an indication that NFVO2 performs resource reservation for the IoT Connection Management Platform portion.
  • NFVO2 checks the layout information of the EPC that the IoT connection management platform needs to rely on.
  • NFVO2 is ready to deploy the IoT connection management platform. Before deployment, NFVO2 checks which IoT needs to rely on which virtualized network functions VNF and virtual link VL in the EPC. For example, the IoT connection management platform needs and the HSS, PCRF, MTC- in the EPC. The IWF needs to be connected, so it is necessary to obtain information about the virtualized network function VNF and the virtual link VL related to the HSS, PCRF, and MTC-IWF connections in the EPC.
  • the NFVO2 sends an acquisition request to the capability open platform, where the acquisition request is used to indicate the EPC scheduling information that the IoT connection management platform needs to rely on.
  • NFVO2 obtains dependent VNF, VL and other programming information from the capability open platform, that is, acquires information of HSS, PCRF, MTC-IWF, and VL information related to the IoT platform.
  • the capability open platform sends the EPC scheduling information to NFVO2.
  • the capability open platform queries the EVC virtualized network function VNF, the virtual link VL, and the like information acquired in the S408 before the acquisition request, and feeds back the information to the NFVO2.
  • the NFVO2 orchestrate the IoT connection management platform according to the acquired layout information of the EPC.
  • the NFVO2 starts the IoT connection management platform scheduling and planning according to the dependent virtualized network function VNF and the virtual link VL obtained in S413, specifically according to the related virtualized network function.
  • the location and quantity of the VNF are used to arrange and plan the deployment location of the virtualized network function VNF in the IoT connection management platform.
  • the virtual link VL in the EPC the specification of the virtual link VL in the IoT connection management platform, the quality of service QoS, etc.
  • the device triggering function of the IoT connection management platform needs to establish a connection with the MTC-IWF.
  • the AAA server needs to establish a connection with the HSS.
  • the device trigger and AAA can be determined in combination with the requirements of the network application.
  • the IoT platform should also plan the resources that need to be provided according to the requirements of the link.
  • the AAA server is a server capable of handling user access requests, providing authentication, authorization, and accounting services.
  • the NFVO2 when the programming information of the EPC satisfies the scheduling requirement of the IoT connection management platform, the NFVO2 sends an acceptance information to the OSS, and the acceptance information indicates that the scheduling information of the EPC is accepted.
  • the NFVO2 sends a message to the OSS, indicating that the EPC scheduling information meets the deployment requirements of the IoT connection management platform, and the two are compatible.
  • the OSS sends a resource allocation request to the NFVO1, where the resource allocation information is used to indicate that the NFVO1 requests resource allocation.
  • the OSS sends resource allocation information to the NFVO1, indicating that the component EPC can perform resource allocation.
  • NFVO1 requests VIM1 to perform resource allocation.
  • the VIM1 returns resource allocation completion information, where the resource completion information is used to indicate that the resource allocation is completed.
  • steps S402 and S403 first perform resource reservation, and the purpose of performing resource allocation is because the entire virtualized network deployment involves other parts. If the layout information of the EPC does not meet the scheduling requirements of other parts, adjustment can be made.
  • NFVO2 sends a request to deploy the IoT connection management platform to VNFM2.
  • the NFVO2 requests the VNFM2 to initiate a request to deploy the IoT connection management platform, and the request for deploying the IoT connection management platform may include an NSD to be deployed, a VNFD, and parameters required for instantiation.
  • VNFM2 verifies the request to deploy the IoT connection management platform.
  • VNFM2 verifies the request sent by NFVO2, including parameter validity, lifecycle management, and the like. This step is similar to the process of verifying the deployment of the EPC request in S405. For the sake of brevity, it will not be described here.
  • VNFM2 sends verification result information to NFVO2.
  • the verification result includes the result of the verification check of the verification pass.
  • NFVO2 sends a resource allocation request to VIM2.
  • NFVO2 instructs VIM2 to perform resource allocation according to the verification result.
  • the VIM2 return message indicates that the resource allocation is completed.
  • the deployment method 400 further includes:
  • the NFVO2 when the layout information of the EPC does not satisfy the scheduling requirement of the IoT connection management platform, the NFVO2 sends a rejection information to the OSS, and the rejection information indicates that the layout information of the EPC is not accepted.
  • NFVO2 sends a message to the OSS, indicating which virtualized network functions VNF in the EPC, or the arrangement of the virtual link VL does not meet the scheduling requirements of the IoT connected network platform, and other specific reasons.
  • the OSS sends an EPC resource reservation request to the NFVO1 according to the rejection information.
  • the OSS sends an EPC resource reservation request to the NFVO1, and forwards the requirement of the NFVO2 orchestration IoT connection management platform, so that the NFVO1 re-arranges the EPC and reserves the resources, and can arrange and resource according to the orchestration requirements of the orchestration IoT connection management platform.
  • Reserved repeat S402 to S423.
  • FIG. 12 is a flowchart of another method for deploying a virtualized network according to an embodiment of the present invention.
  • the deployment method shown in FIG. 12 can be applied in the scenario shown in FIG. 2, and the virtual network can be composed of two parts, an EPC and an IMS.
  • the EPC part includes NFVO1, VNFM1 and VIM1;
  • the IMS part includes NFVO2, VNFM2 and VIM2.
  • the deployment method 500 shown in FIG. 12 differs from the method 400 shown in FIG. 7 in that the deployment method 500 is to deliver the information through the OSS, and the deployment method 400 is to deliver the information through the capability open platform.
  • the deployment method 500 includes the following steps:
  • S501 to S507 reserve resources for the EPC part. This process is the same as the execution process of S401 to 406 and S409 shown in FIG. 11, and will not be described again for brevity.
  • the OSS sends an IMS request to the NFVO2 to start deploying.
  • the OSS requests the NFVO2 to deploy the IMS part in the virtualized network, because only the EPC and the IMS part exist in the virtualized network, and there is no other part of the deployment after the IMS part, so the OSS sends the IMS request to the NFVO2 to start deployment. There is no need to include an indication that NFVO2 is performing IMS resource reservation.
  • NFVO2 checks the scheduling information of the EPC that the IMS needs to rely on.
  • NFVO2 is ready to deploy IMS. Before deployment, NFVO2 checks which IMS network functions VNF and virtual link VL in the EPC. For example, IMS needs to be connected with HSS, PCRF, and PGW in EPC, so it needs to be Obtain information about the virtualized network function VNF related to the HSS, PCRF, and PGW connections, and the associated virtual link VL.
  • the NFVO2 sends an acquisition request to the OSS, where the acquisition request is used to indicate the scheduling of the EPC that the IMS needs to rely on.
  • NFVO2 obtains the VNF and VL scheduling information of the dependency from the OSS, that is, acquires the scheduling information of the HSS, the PCRF, and the PGW, and the VL information related to the IMS for these functions; the granularity of the request may be VNF, VL, that is, The virtualized network function VNF and virtual link VL are organizational units.
  • the OSS forwards the acquisition request to the NFVO2.
  • NFVO1 sends the EPC scheduling information to the OSS.
  • the NFVO1 sends the scheduling information of the VNF and VL required by the IMS to the OSS according to the acquisition request, and the process needs to rely on the relationship between the EPC part and the IMS part to manage the domain, and the process is similar to the process of S407, specifically Table 1 is a brief description and will not be described here.
  • the OSS forwards the EPC scheduling information to the NFVO2.
  • the NFVO2 orchestrate the IMS according to the acquired information of the EPC.
  • the NFVO2 starts the IMS scheduling and planning according to the dependent virtualized network function VNF and the virtual link VL obtained in S513, and specifically, according to the related virtualized network function VNF deployment location.
  • Information such as the quantity and other information.
  • the deployment location of the virtualized network function VNF in the IMS is planned and planned.
  • the specifications of the virtual link VL in the IMS, the quality of service QoS, etc. are designed; for example, P- in the IMS network.
  • the CSCF needs to be connected to the PGW. After obtaining the deployment location of the PGW, the deployment location of the P-CSCF is determined, and the P-CSCF is configured according to the link configuration information of the PGW.
  • the NFVO2 when the editing information of the EPC satisfies the programming requirement of the IMS, the NFVO2 sends an acceptance information to the OSS, and the acceptance information indicates that the scheduling information of the EPC is accepted.
  • the NFVO2 sends a message to the OSS, indicating that the EPC scheduling scheme satisfies the IMS scheduling requirements, and the two are compatible.
  • the OSS sends resource allocation information to the NFVO1, where the resource allocation information is used to indicate that the NFVO1 requests resource allocation.
  • the OSS sends resource allocation information to the NFVO1, indicating that the EPC can perform resource allocation.
  • NFVO1 instructs VIM1 to perform resource allocation.
  • the VIM1 returns resource allocation completion information, where the resource completion information is used to indicate that the resource allocation is completed.
  • steps S502 and S503 first perform resource reservation, and the purpose of performing resource allocation is because the entire virtualized network deployment involves other parts. If the layout information of the EPC does not meet the scheduling requirements of other parts, adjustment can be made.
  • NFVO2 sends a deployment IMS request to VNFM2.
  • the NFVO2 requests the VNFM2 to initiate a request to deploy the IMS, and the request for deploying the IoT connection management platform may include an NSD to be deployed, a VNFD, and parameters required for instantiation.
  • VNFM2 verifies the deployment IMS request.
  • the process of verifying the EPC request in the steps S520 and S505 is similar, and is not described here for brevity.
  • VNFM2 sends verification result information to NFVO2.
  • the verification result includes the result of the verification check of the verification pass.
  • NFVO2 sends a resource allocation request to VIM2.
  • NFVO2 instructs VIM2 to perform resource allocation according to the verification result.
  • the VIM2 return message indicates that the resource allocation is completed.
  • the deployment method 500 further includes:
  • the NFVO2 when the layout information of the EPC does not satisfy the scheduling requirement of the IMS, the NFVO2 sends a rejection information to the OSS, and the rejection information indicates that the layout information of the EPC is not accepted.
  • NFVO2 sends a message to the OSS, indicating which virtualized network functions VNF in the EC, or the arrangement of the virtual link VL does not meet the programming requirements of the IMS, and other specific reasons.
  • the OSS sends an EPC resource reservation request to the NFVO1 according to the rejection information.
  • the OSS sends an EPC resource reservation request to the NFVO1, and forwards the NFVO2 scheduling IMS requirement, so that the NFVO1 re-arranges the EPC and reserves the resource, and can perform the scheduling and resource reservation according to the orchestration requirements of the orchestration IMS, and repeat S502 to S523.
  • FIG. 13 is a flowchart of another method for deploying a virtualized network according to an embodiment of the present invention.
  • the deployment method shown in FIG. 13 can be applied in the scenario shown in FIG. 2, and the virtual network can be composed of two parts: EPC and IMS.
  • the EPC part includes NFVO1, VNFM1 and VIM1;
  • the IMS part includes NFVO2, VNFM2 and VIM2.
  • the deployment method 600 shown in FIG. 13 differs from the method 500 shown in FIG. 12 in that the method 600 is configured to transfer information through an interface between NFVOs, and the deployment method 500 is to deliver information through the OSS.
  • the deployment method 600 includes the following steps:
  • the process of reserving resources for the EPC from S601 to S607 is the same as the process of S501 to S507 in the deployment method 500. For brevity, it will not be repeated here.
  • the OSS sends an IMS deployment request to the NFVO2 according to the resource reservation complete information, where the deployed IMS request includes an IP address of the NFVO1.
  • the OSS requests the NFVO2 to deploy the IMS part in the virtual network, because there are only two parts of the EPC and the IMS in the virtualized network, and there is no other part of the deployment after the IMS part, so the OSS sends the IMS request to the NFVO2 to start deploying the IMS request. It is not necessary to include an indication that NFVO2 is required to perform IMS resource reservation.
  • the OSS informs the NFVO2 of the IP address or domain name of the NFVO1, so that the NFVO2 of the IMS part acquires the network deployment and obtains the information of the EPC network deployment.
  • NFVO2 checks the EPC scheduling information that the IMS needs to rely on.
  • NFVO2 is ready to deploy IMS. Before deployment, NFVO2 checks which IMS network functions VNF and virtual link VL in the EPC. For example, IMS needs to be connected with HSS, PCRF, and PGW in EPC, so it needs to be Obtain information about the virtualized network function VNF related to the HSS, PCRF, and PGW connections, and the associated virtual link VL.
  • the NFVO2 sends an acquisition request to the NFVO1 according to the deployment IMS request, where the acquisition request is used to indicate the deployment and configuration information of the EPC that the IMS needs to rely on.
  • NFVO2 obtains the VNF and VL scheduling information of the dependency from the OSS, that is, acquires the scheduling information of the HSS, the PCRF, and the PGW, and the VL information related to the IMS for these functions; the granularity of the request may be VNF, VL, that is, The virtualized network function VNF and virtual link VL are organizational units.
  • NFVO1 sends the EPC scheduling information to NFVO2.
  • the NFVO1 sends the scheduling information of the VNF and VL required by the IMS to the OSS according to the acquisition request, and the process needs to rely on the relationship between the EPC part and the IMS part to manage the domain, and the process is similar to the process of S407, specifically Table 1 is a brief description and will not be described here.
  • the steps of NFVO to arrange the IMS part and then allocate resources for EPC and IMS are the same as S512 to S521 and S514 to S523, and are not described here for brevity.
  • FIG. 14 is a flowchart of a method for deploying a virtualized network according to an embodiment of the present invention.
  • the deployment method shown in Figure 14 can be applied to the scenario shown in Figure 3.
  • Two carriers (operator A and carrier B) need to deploy a virtual network.
  • the virtual network includes two components, respectively.
  • the core network EPC and IoT are connected to the management platform, and the EPC component is provided by one operator (operator A), and the IoT connection management platform is provided by another operator (operator B), that is, there are two management domains, each management The domains have independent NFVO and VNFM.
  • the OSS1, NFVO1, and VIM of the operator A perform the deployment of the EPC part; the OSS2, NFVO2, and VIM2 of the operator B perform the deployment of the IoT connection platform part.
  • the deployment method 700 includes the following steps:
  • the OSS1 indicates that resources are reserved for deploying the EPC.
  • the deployment of the EPC part of the OSS1, NFVO1, and VIM in the operator A first completes the resource reservation, and the reserved resource process is the same as S401 to S407 in the deployment method 400, which is a brief description here. No longer.
  • the OSS1 sends an IoT connection management platform deployment request to the capability open platform 2 through the Portal interface provided by the operator B.
  • OSS1 starts to deploy the IoT connection management platform. Because it does not have the deployment capability itself, it initiates a request to the Portal interface provided by the operator B.
  • the capability open platform 2 forwards the request to the OSS2 to start deploying the IoT connection management platform.
  • the OSS2 sends a request to the NFVO2 to start deploying the IoT connection management platform.
  • NFVO2 checks the orchestration information that the IoT connection management platform needs to rely on.
  • this step is the same as the step of S405, and is not described here for brevity.
  • the NFVO2 sends an acquisition request to the OSS2, where the obtaining request is used to indicate that the scheduling information required to deploy the IoT connection management platform depends on the EPC.
  • the OSS2 forwards the acquisition request to the capability open platform 1.
  • the capability opening platform 1 sends the deployment and configuration information of the EPC to the OSS2 according to the acquisition request.
  • OSS2 forwards the EPC scheduling information to NFVO2.
  • the NFVO2 obtains the scheduling information of the EPC on which the IoT connection management platform is deployed, and can also be implemented by S706' to S713'.
  • the NFVO2 sends an acquisition request to the OSS2, where the acquisition request is used to indicate the scheduling information of the EPC that the IoT connection management platform needs to rely on.
  • the capability opening platform 2 forwards the acquisition request to the OSS1 of the operation A through the Portal interface.
  • NFVO1 sends the EPC scheduling information to OSS1.
  • the capability opening platform 2 forwards the EPC scheduling information to the OSS 2.
  • the NFVO2 deploys the IoT connection management platform according to the acquired EPC scheduling information.
  • the resource allocation for the EPC and the IoT connection management platform is performed, and the operation steps are the same as those of the S415 to S423 in the deployment method 400. For the sake of brevity, no further description is provided herein. .
  • the EPC part is scheduled and planned and the resource reservation is re-requested, and the execution steps are the same as S415' and S416' in the deployment method 400, for the sake of brevity, I won't go into details here.
  • FIG. 6 to FIG. 14 are detailed descriptions of the deployment method of the virtualized network in the two different application scenarios of FIG. 2 and FIG. 3 .
  • the deployment system is described in detail below with reference to FIG. 15 .
  • FIG. 15 is a deployment system according to an embodiment of the present invention.
  • the system 1500 can be composed of multiple parts, including a first network function virtualization orchestrator NFVO 1510 and a second NFVO 1520 and a service operation and management platform 1530.
  • the first NFVO 1510 is configured to receive a first part of the deployment request sent by the service operation and management platform 1530, where the first part of the deployment request includes an indication of resource reservation; and the resource reservation completion information is sent to the service operation and management platform;
  • the second NFVO 1520 is configured to receive a second part of the deployment request sent by the service operation and management platform 1530; obtain the arrangement information of the first part; and perform the second part of the arrangement according to the arrangement information of the first part;
  • the second NFVO 1520 sends the acceptance information to the business operation and management platform 1530, and the acceptance information is used to indicate acceptance of the arrangement information of the first part;
  • the first NFVO 1510 is further configured to receive a resource allocation request sent by the service operation and management platform 1530, requesting resource allocation of the first part;
  • the second NFVO 1520 is configured to request resource allocation of the second part.
  • the virtualization network is composed of multiple parts, and each part is arranged and planned by the independent network function virtualization orchestrator NFVO for each part of the virtualized network, the first part and the second part. Belongs to two parts of multiple parts.
  • NFVO independent network function virtualization orchestrator
  • a plurality of parts in the first part of the virtualized network may be understood, and the second part is the last part of the virtualized network.
  • resource reservation is required for the first part of the deployment.
  • the resource reservation only performs resource reservation and does not actually allocate resources.
  • each part included in the virtualized network needs to perform resource reservation, except for the last deployed part of the virtual network.
  • the first NFVO 1510 requests resource reservation according to the first partial deployment request sent by the received service operation and management platform OSS/BSS 1530, and sends resource reservation completion information to the OSS/BSS 1530;
  • the second NFVO 1520 receives the OSS/BSS 1530 sends a second part of the deployment request, and obtains the first part of the arrangement information, according to the first part of the arrangement information for the second deployment, to determine whether the first part of the arrangement information meets the second part of the layout requirements;
  • the second NFVO 1520 sends an acceptance message to the OSS/BSS 1530 informing the OSS/BSS 1530 to accept the first part of the orchestration information, ie the arrangement and planning of the first part.
  • a deployment system provided by the embodiment of the present invention performs resource reservation on a part to be deployed, and does not perform resource allocation after the resource is reserved. After all the parts are deployed, the resource allocation is performed, and the virtualized network is realized.
  • the service consists of multiple parts, when the virtualized network is deployed, different parts of the network can be coordinated with each other, which improves the flexibility and versatility of the network deployment.
  • the second NFVO 1520 when the scheduling information of the first part does not meet the scheduling requirement of the second part, the second NFVO 1520 sends a rejection information to the OSS/BSS 1530, notifying the OSS/BSS 1530 that the first part is not accepted. Orchestration and planning.
  • the first NFVO 1510 is further configured to generate the first partial programming information. Specifically, after the first network function virtualization orchestrator NFVO 1510 receives the first part of the deployment request sent by the service operation and management platform, according to the first part of the virtualized network deployment requirement, the first part of the virtual network is planned, and the network is completed.
  • the template is selected, and the configuration data of each virtualized network function VNF is configured to complete the first part of the orchestration information, and the arrangement information may include information such as location information, quantity, virtual link VL, and quality of service QoS of the virtualized network function.
  • the first NFVO 1510 is further configured to: request a first virtualized infrastructure manager VIM resource reservation; and the first NFVO 1510 is further configured to receive the resource pre-sent by the first VIM. Leave the completion information.
  • the second partial deployment request includes an IP address of the first NFVO 1510.
  • the second NFVO 1520 is specifically configured to obtain the scheduling information of the first part from the first NFVO 1510.
  • the second NFVO 1520 is specifically configured to obtain, by using the service operation and management platform 1530, the first part of the scheduling information from the first NFVO 1510.
  • each part of the embodiment of the present invention also needs to include a virtualized network function manager VNFM and a virtualized infrastructure management system VIM, as shown in FIG.
  • the deployment system 1500 may further include a capability opening platform 1540.
  • the second NFVO 1520 is further configured to obtain the first part of the scheduling information from the capability opening platform.
  • the first NFVO 1510 is further configured to send the first part of the scheduling information to the capability opening platform 1540.
  • the scheduling information includes deployment location information of the virtualization network function VNF
  • the second NFVO 1520 orchestras the second portion according to the deployment location information of the virtualization network function VNF.
  • a deployment system provided by the embodiment of the present invention performs resource reservation after the resource is reserved, and does not perform resource allocation after the resource is reserved. After all the deployment parts complete the planning and scheduling, the resource allocation is also performed. The resources are reserved for coordination, and the process of optimizing the deployment is realized.
  • the virtual network service is composed of multiple parts, when the virtualized network is deployed, the mutual coordination between the parts is realized, and the flexibility and generality of the network deployment are improved. Sex. At the same time, it can adapt to the scenario where multiple vendors and multiple operators deploy a virtualized network at the same time, which improves the automation of deployment and improves the efficiency of deployment.
  • NFVOs in the deployment system 1500 provided in FIG. 15 can implement the methods/steps shown in FIG. 6 to FIG. 14 for brevity and will not be described herein.
  • Another embodiment of the present invention provides a method for deploying a virtualized network, as shown in FIG. 16.
  • FIG. 16 is a flowchart of another method for deploying a virtualized network according to an embodiment of the present invention.
  • the network function virtualization orchestrator NFVO in the deployment system may include the following steps:
  • the first virtualized network function manager VNFM receives the first part of the deployment request sent by the network function virtualization orchestrator NFVO.
  • the second VNFM receives a second part of the deployment request sent by the NFVO, where the second part of the deployment request includes the first part of the scheduling information.
  • the second VNFM checks the second part of the deployment request.
  • the second VNFM sends an acceptance information to the NFVO, where the acceptance information is used to indicate that the arrangement information of the first part is accepted.
  • the virtualized network is composed of multiple parts, and multiple parts can be arranged and planned by the same network function virtualization orchestrator NFVO for each part of the virtualized network, and each part is managed by an independent virtualized network function.
  • the VNFM cooperates with NFVO to complete the instantiation of the virtualized network function VNF.
  • resource reservation when a virtualized network is deployed, resource reservation needs to be performed on the first part of the deployment, and the resource reservation only performs resource reservation, and does not perform real resource allocation.
  • the resource reservation is required for each part, but the part of the last programming plan in the virtualized network does not need to be reserved. In the embodiment of the present invention, it can be understood as the second part.
  • each part of the VNFM needs to verify the orchestration information of all the parts that have been deployed before, to determine whether the arrangement information of the completed part of the deployment meets the programming requirements of the part, and if so, use Complete the deployment of the virtualized network at NFVO and request each part for resource allocation.
  • the first VNFM in the first part receives the first part deployment request sent by the network function virtualization NFVO.
  • the first VNFM verifies the first part of the deployment request, including verifying parameters required for deployment, validity of parameters, and lifecycle management.
  • the first VNFM may send verification completion information to the NFVO to notify the NFVO that the verification of the first partial deployment request is completed.
  • the second VNFM receives the second partial deployment request sent by the NFVO, and the second partial deployment request further needs to include various parameters required for the second part.
  • the second VNFM verifies the second partial deployment request, verifies the validity of each parameter required for the second part included in the second partial deployment request, and passes the VNF life cycle between the NFVO and the VNFM.
  • the VNF query operation of the management interface checks whether there is already a VNF instance that satisfies the second part of the programming requirements. If it exists, the VNF can be used as part of the VNF of the second part of the virtualized network; and whether the first part of the scheduling information can be determined Meet the layout requirements of the second part.
  • the second VNFM sends an acceptance message to the NFVO to inform the NFVO to accept the layout and planning scheme of the first part, and the layout and planning scheme of the first part is compatible with the layout and planning scheme of the second part, so as to facilitate the NFVO request for each part. Resource allocation.
  • the second VNFM when the scheduling information of the first part does not meet the scheduling requirement of the second part, the second VNFM sends a rejection information to the NFVO, where the rejection information is used to indicate that the scheduling information of the first part is not accepted;
  • the first VNFM re-receives the first partial deployment request.
  • the method for deploying a virtualized network performed by the embodiment of the present invention performs resource reservation on the part to be deployed, and does not perform resource allocation after the resource is reserved. After all the parts are deployed, the resource allocation is implemented.
  • a virtualized network service consists of multiple parts, when performing virtualized network deployment, different parts of the network can Coordinated with each other to improve the flexibility and versatility of network deployment.
  • the scheduling information may include deployment location information of the virtualization network function VNF, and the second VNFM checks the second partial deployment request, including:
  • the second VNFM determines whether the deployment location information of the virtualized network function VNF satisfies the scheduling requirements of the second part.
  • the scheduling information may further include the number of virtualized network functions, an IP address, virtual link VL information, and/or configuration information, and the like.
  • FIG. 17 is a flowchart of a method for deploying a virtualized network according to an embodiment of the present invention.
  • the deployment method shown in Figure 17 can be applied to the scenario shown in Figure 4.
  • One carrier A needs to deploy a virtual network.
  • the virtual network consists of three components: core network EPC, IMS, and IoT connection management.
  • the platform, and the three components are provided by different providers (equipment vendors), each using a separate VNFM, but sharing one NFVO.
  • the EPC component includes VNFM1; the IMS includes VNFM2; and the IoT connection management platform component includes VNFM3.
  • the deployment method 900 includes the following steps:
  • S901 The OSS sends a start deployment request to the NFVO.
  • OSS requests NFVO to deploy virtual networks, including EPC, IMS, and IoT connection management platform.
  • the NFVO sends a request for an EPC resource reservation to the VIM.
  • the NFVO performs the planning of the EPC network according to the requirements of the EPC part of the deployed virtualization network, completes the selection of the network template, and configures each VNF, that is, sets the configuration data, and the NFVO then requests the VIM to reserve the required resources.
  • This resource includes information such as VNF and VL.
  • NFVO1 sends an EPC deployment request to the VNFM1, and the EPC deployment request may include an NSD, a VNFD, and a parameter required for instantiation.
  • the verification of the start of the EPC deployment request by the VNFM1 includes: checking whether the sender NFVO1 that initiates the EPC deployment request is authorized, starting the verification of the parameter validity in the EPC deployment request, and the virtualized network function VMF. Verification of life cycle management, etc.
  • the verification of the validity of the parameters may include the technical correctness of the parameters and the verification of the compliance of the policies.
  • the verification of the lifecycle management of the virtualized network function VNF may include: virtualizing the VNF lifecycle management interface of the virtualized network between the NFVO1 and the VNFM1 for each virtualized network function VNF instance required for the virtualized network service.
  • the network VNF query operation checks if there is already a VNF instance that satisfies the requirement, and if so, the VNF is part of the network service.
  • the verification completion information includes the result of the confirmation check, that is, the verification is passed.
  • the NFVO sends a VIMSM2 to start deploying the IMS request.
  • the NFVO requests the VNFM2 to initiate a request for deploying the IMS
  • the message may include the VNFD, the VLD, and the parameters required for the instantiation required by the IMS, and the information of the EPC is also required to be included in the embodiment of the present invention. Pass the layout information of the EPC related to the IMS orchestration.
  • VNFM2 verifies the start of the IMS deployment request.
  • the VNFM2 verifies the parameters sent by the NFVO, including the validity of the parameters, the lifecycle management, and the like, and the specific verification process is similar to the verification process of the S905, and is not described here.
  • the verification completion information is sent to the NFVO.
  • VNFM2 determines that the EPC's orchestration cannot meet the IMS scheduling requirements, it returns an error response and requests NFVO to re-execute the EPC deployment request. If yes, S910 to S911 are performed.
  • S910 The NFVO sends an IMS resource reservation request to the VIM.
  • the VIM performs resource reservation according to the IMS resource reservation request.
  • the NFVO sends a request to deploy the IoT connection management platform to the VNFM3 according to the resource reserved by the IMS.
  • the NFVO requests the VIM to reserve the resources required for deploying the IMS, including the VNF and the virtual link VL.
  • the NFVO requests the VNFM3 to initiate a request for deploying the IoT.
  • the message may include the VNFD, the VLD, and the parameters required for the instantiation that need to be deployed in the third part, and also includes the EPC scheduling information and the IMS scheduling information information. Among them, only the EPC and IMS scheduling information related to the IoT connection management platform can be delivered.
  • VNFM3 verifies the start of the IoT connection management platform deployment request.
  • the verification process is similar to the verification process of S908, and is not described here for brevity.
  • the verification completion information is sent to the NFVO.
  • S915 The NFVO sends a resource allocation request for resource allocation to the EPC, the IMS, and the IoT connection management platform to the VIM.
  • the VIM allocates resources for the EPC, IMS, and IoT connection management platforms, respectively, and sends resource allocation completion information to the NFVO.
  • S917 The NFVO sends deployment completion information to the OSS, where the deployment completion information is used to indicate that the virtual network deployment is completed.
  • the embodiment of the invention further provides a deployment system, as shown in FIG.
  • FIG. 18 is a schematic structural diagram of a deployment system according to an embodiment of the present invention.
  • the deployment system 1800 may include a first virtualization network function manager VNFM 1810 and a second VNFM 1820 and a network function virtualization orchestrator NFVO 1830.
  • the first VNFM 1810 is configured to receive the first partial deployment request sent by the network function virtualization orchestrator NFVO 1830 after completing the first partial resource reservation.
  • the second VNFM 1820 is configured to receive a second part of the deployment request sent by the NFVO 1830, where the second part of the deployment request may include the first part of the scheduling information;
  • the second VNFM 1820 is also used to verify the second part of the deployment request.
  • the second VNFM 1820 is configured to send the acceptance information to the NFVO, the acceptance information is used to indicate acceptance of the arrangement information of the first part, and instruct the NFVO to request the first part and the second part. Resource allocation.
  • the scheduling information may include deployment location information of the virtualization network function VNF
  • the second VNFM 1820 is further configured to determine whether the deployment location information of the virtualization network function VNF meets the scheduling requirement of the second part.
  • the deployment system 1800 may include multiple deployment parts, each deployment part may include an independent virtualized network function manager VNFM, and deploys with the NFVO and completes the virtualized network function VNF. (or instantiate).
  • each deployment part may include an independent virtualized network function manager VNFM, and deploys with the NFVO and completes the virtualized network function VNF. (or instantiate).
  • the first part, the second part, and the first VNFM and the second VNFM are mentioned. This is only for the purpose of schematically describing the technical solution provided by the embodiment.
  • the first part, the first part A VNFM is understood to be part of multiple virtualized networks, multiple VNFMs.
  • the last deployment part of the virtualized network does not need to be reserved for resources. Therefore, the last deployed part of the virtual network may be understood as the second in the embodiment of the present invention. In part, this part is managed by the second VNFM for virtualized network functions.
  • a service operation and management platform 1840 is further required to request a start deployment request from the NFVO 1830; and a virtualized infrastructure management system VIM is used to reserve resources and allocate resources for the deployment part.
  • the deployment system provided by the embodiment of the present invention performs resource reservation on the part to be deployed, and does not perform resource allocation after the resource is reserved. After all the parts complete the deployment planning, resource allocation is performed to implement the virtualized network service.
  • resource allocation is performed to implement the virtualized network service.
  • VNFMs in the deployment system 1800 provided in FIG. 18 can implement the methods/steps shown in FIG. 16 and FIG. 17, which are not described herein for brevity.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein can be implemented in hardware, a software module executed by a processor, or a combination of both.
  • the software module can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or technical field. Any other form of storage medium known.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明涉及一种虚拟化网络的部署方法和部署系统，虚拟化网络由多个部分组成，该方法包括：第一网络功能虚拟化编排器NFVO接收业务运营和管理平台发送的第一部分部署请求，包括资源预留指示，第二NFVO接收第二部分部署请求，获取第一部分的编排信息，并根据第一部分的编排信息进行第二部分的编排，当第一部分的编排信息满足第二部分的部署需求时，第一NFVO和第二NFVO分别请求资源分配。对需要部署部分进行资源预留，资源预留后不执行资源分配，待所有的部署部分进行完成编排规划后，再进行资源分配，实现了虚拟网络业务由多个部分构成时，执行虚拟化网络的部署时，实现各部分之间的相互协调，提高了网络部署的灵活性和通用性。

Description

虚拟化网络的部署方法和部署系统
本申请要求于2016年4月22日提交中国专利局、申请号为201610259561.2、发明名称为“虚拟化网络的部署方法和部署系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及虚拟网络技术领域，尤其涉及一种虚拟化网络的部署方法和系统。
背景技术
网络功能虚拟化(Network Function Virtualization，NFV)是欧洲电信标准委员会(European Telecommunications Standards Institute，ETSI)下的一个标准制定项目，主要针对网络云化制定业界通用标准。基于现代化的IT虚拟化技术，提供一个新的网络产品环境，降低成本，提高效率、增加敏捷能力。通过使用x86等通用性硬件以及虚拟化技术，来承载很多功能的软件处理。从而降低网络昂贵的设备成本。可以通过软硬件解耦及功能抽象，使网络设备功能不再依赖于专用硬件，资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。
在现有技术中，NFV部署一个网络业务(Network Service，NS)也就是实例化一个网络业务，包括网络功能虚拟化编排器(Network Functions Virtualization Orchestrator，NFVO)检查接收到的虚拟网络业务部署请求的有效性，并针对网络需求的每个虚拟网络功能(Virtual Network Function，VNF)，通过与虚拟化网络功能管理器(Virtual Network Function Manager，VNFM)之间的VNF生命周期管理接口的VNF查询操作检查是否已经存在满足需求的VNF部署；当满足需求的VNF部署时，请求虚拟化基础设施管理器，或者说虚拟化基础设施管理系统(Virtual Infrastructure Manager，VIM)实例化网络连接，并进一步进行网络业务部署。
现有技术中考虑的应用场景比较简单，主要是统一部署一个网络业务，业务的编排实例化属于一个管理域，但现实中部署一个网络，业务的编排实例化可能属于多个管理域，或者说一个网络业务可能由多个部分组成，每一部分由不同管理域负责虚拟化网络的部署和管理。而现有技术中部署网络业务的方法还不适用于部署多个部分的情况。
发明内容
本发明提供的一种虚拟化网络的部署方法和部署系统，可以实现一个由多个部分构成的虚拟网络业务的部署。
第一方面，本发明提供了一种虚拟化网络的部署方法，该方法包括：
第一网络功能虚拟化编排器NFVO接收业务运营和管理平台发送的第一部分部署请求，该第一部分部署请求中包括资源预留的指示；第一NFVO完成资源预留请求后，向业务运营 和管理平台发送资源预留完成信息；
第二NFVO接收业务运营和管理平台发送的第二部分部署请求；第二NFVO检查部署第二部分需要依赖的第一部分的编排信息，获取第一部分的编排信息，并根据第一部分的编排信息进行第二部分的编排；第二NFVO确定第一部分的编排信息是否满足第二部分的编排需求；当第一部分的编排信息满足第二部分的编排需求时，第二NFVO向业务运营和管理平台发送接受信息，接受信息用于指示接受第一部分的编排信息；
第一NFVO接收业务运营和管理平台发送的资源分配请求，请求第一部分的资源分配；
当第一部分的编排信息满足第二部分的编排需求时，第二NFVO请求第二部分的资源分配。
基于第一方面提供的虚拟化网络的部署方法，通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配；并且其他部分的部署要根据已经部署的网络的编排信息，实现了由多个部分组成的虚拟化网络业务的部署。执行虚拟化网络部署时，网络的不同部分之间能够相互协调，提高了网络部署的灵活性和通用性。
结合第一方面，在第一方面的第一种可能实现方式中，在第一网络功能虚拟化控制器NFVO接收业务运营和管理平台发送的第一部分部署请求之后，该部署方法还包括：
第一NFVO请求第一虚拟化基础设施管理器VIM资源预留；
第一NFVO接收第一VIM发送的资源预留完成信息，以实现部署第一部分所需的资源预留。
结合第一方面或第一方面的第一种可能实现的方式，第一方面的第二种可能实现的方式中，在第一网络功能虚拟化编排器NFVO接收业务运营和管理平台发送的第一部分部署请求之后，部署方法还包括：
第一NFVO生成第一部分的编排信息。
结合第一方面的以上几种可能实现方式中的任一种可能实现的方式，在第一方面的第三种可能实现的方式中，第二NFVO获取第一部分的编排信息，包括：
第二NFVO从第一NFVO获取第一部分的编排信息，以实现第二NFVO通过NFVO之间的接口获取第一部分的编排信息。
结合第一方面的第三种可能实现的方式中，第一方面的第四种可能实现的方式中，第二部分部署请求包括第一NFVO的IP地址，以实现第二NFVO根据第一NFVO的IP地址，直接向第一NFVO中请求获取第一部分的编排信息。
结合第一方面或者第一方面的第一种可能实现的方式或者第一方面中第二种可能实现的方式中的任一可能实现的方式，在第一方面的第五种可能实现的方式中，第二NFVO获取第一部分的编排信息，包括：
第二NFVO可以通过业务运营和管理平台从第一NFVO获取第一部分的编排信息，其具体过程可以为第二NFVO向业务运营和管理平台发送获取请求，业务运营和管理平台向第一NFVO转发获取请求；第二NFVO接收第一NFVO通过业务运营和管理平台发送的第一部分的编排信息。
结合第一方面或者第一方面的第一种可能实现的方式或者第一方面中第二种可能实现的方式中的任一可能实现的方式，在第一方面的第六种可能实现的方式中，第二NFVO获取 第一部分的编排信息，包括：
第二NFVO从能力开放平台获取第一部分的编排信息。
结合第一方面的第六种可能实现的方式，在第一方面的第七种可能实现的方式中，该部署方法还包括：
第一NFVO向能力开放平台发送第一部分的编排信息，以实现第二NFVO从能力开放平台获取第一部分的编排信息。
作为第一方面的第八种可能实现的方式，第二NFVO获取第一部分的编排信息，可以通过运营商提供的MANO之间的接口获取第一部分的编排信息。
结合第一方面的第八种可能实现的方式，在第一方面的第九种可能实现的方式中，第二NFVO可以通过运营商提供的MANO之间的接口和业务运营和管理平台从第一NFVO获取第一部分的编排信息。
结合第一方面的八种可能实现的方式中，在第一方面的第十种可能实现的方式中，第二NFVO可以通过运营商提供的MANO之间的接口从能力开放平台获取第一部分的编排信息。
结合第一方面或第一方面的第一至第十种可能实现的方式中的任一可能实现的方式，在第一方面的第十一种可能实现的方式中，编排信息可以包括虚拟化网络功能VNF的部署位置信息，根据第一部分的编排信息进行第二部分的编排，包括：
根据虚拟化网络功能VNF的部署位置信息对第二部分进行编排。
结合第一方面或第一方面中任一可能实现的方式，在第一方面的第十二种可能实现的方式，该部署方法还可以包括：
当所述第一部分的编排信息不满足所述第二部分的编排需求时，所述第二NFVO向所述业务运营和管理平台发送拒绝消息，所述拒绝消息用于指示不接受所述第一部分的编排信息，重新发送所述第一部分部署请求。
第二方面，本发明提供一种部署系统，该部署系统包括：第一网络功能虚拟化编排器NFVO和第二NFVO；
第一NFVO，用于接收业务运营和管理平台发送的第一部分部署请求，第一部分部署请求中包括资源预留的指示；向业务运营和管理平台发送资源预留完成信息；
第二NFVO用于接收业务运营和管理平台发送的第二部分部署请求；获取第一部分的编排信息；根据第一部分的编排信息进行第二部分的编排；
当第一部分的编排信息满足第二部分的编排需求时，第二NFVO向业务运营和管理平台发送接受信息，接受信息用于指示接受第一部分的编排信息；
第一NFVO还用于，接收业务运营和管理平台发送的资源分配请求，请求第一部分的资源分配；
当第一部分的编排信息满足第二部分的编排需求时，第二NFVO，用于请求第二部分的资源分配。
基于第二方面提供的部署系统，通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配，实现了虚拟化网络业务由多个部分组成时，执行虚拟化网络部署时，网络的不同部分之间能够相互协调，提高了网络部署的灵活性和通用性。
第三方面，本发明实施例提供了一种虚拟化网络的部署方法，虚拟化网络由多个部分 组成，该部署方法包括：
第一虚拟化网络功能管理器VNFM接收NFVO发送的第一部分部署请求；
第二VNFM接收NFVO发送的第二部分部署请求，第二部分部署请求中包括第一部分的编排信息；
第二VNFM对第二部分部署请求进行校验；；
当第一部分的编排信息满足第二部分的编排需求时，第二VNFM向NFVO发送接受信息，接受信息用于指示接受第一部分的编排信息，并指示NFVO请求第一部分和第二部分的资源分配。
通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配，实现了虚拟化网络业务由多个部分组成时，执行虚拟化网络部署时，网络的不同部分之间能够相互协调，提高了网络部署的灵活性和通用性。
第四方面，本发明提供了一种部署系统，该部署系统包括第一虚拟化网络功能管理器VNFM和第二VNFM；
第一VNFM，用于在完成第一部分资源预留之后，接收网络功能虚拟化编排器NFVO发送的第一部分部署请求；
第二VNFM，用于接收NFVO发送的第二部分部署请求，第二部分部署请求中包括第一部分的编排信息；
第二VNFM还用于，对第二部分部署请求进行校验；当第一部分的编排信息满足第二部分的编排需求时，第二VNFM用于向NFVO发送接受信息，接受信息用于指示接受第一部分的编排信息，并指示NFVO请求第一部分和第二部分的资源分配。
基于第一方面提供的虚拟化网络的部署方法，通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配；并且其他部分的部署要根据已经部署的网络的编排信息，实现了由多个部分组成的虚拟化网络业务的部署。执行虚拟化网络部署时，网络的不同部分之间能够相互协调，提高了网络部署的灵活性和通用性
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对本发明实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为网络功能虚拟化NFV架构图；
图2为本发明实施例提供的虚拟化网络的部署方法的一种应用场景；
图3为本发明实施例提供的虚拟化网络的部署方法的另一种应用场景；
图4为本发明实施例提供的虚拟化网络的部署方法的又一种应用场景；
图5为本发明实施例提供的一种网络功能虚拟化编排器NFVO的结构示意图；
图6为本发明实施例提供的一种虚拟化网络的部署方法的流程图；
图7为本发明实施例提供的另一种虚拟化网络的部署方法的流程图；
图8为本发明实施例提供的另一种虚拟化网络的部署方法的流程图；
图9为本发明实施例提供的又一种虚拟化网络的部署方法的流程图；
图10为本发明实施例提供的再一种虚拟化网络的部署方法的流程图；
图11为本发明实施例提供的一种虚拟化网络的部署方法的流程图；
图12为本发明实施例提供的另一种虚拟化网络的部署方法的流程图；
图13为本发明实施例提供的又一种虚拟化网络的部署方法的流程图；
图14为本发明实施例提供的再一种虚拟化网络的部署方法的流程图
图15为本发明实施例提供的一种部署系统的结构示意图；
图16为本发明实施例提供的一种虚拟化网络的部署方法的流程图；
图17为本发明实施例提供的另一种虚拟化网络的部署方法的流程图；
图18为本发明实施例提供的一种部署系统的结构示意图。
具体实施方式
图1为网络功能虚拟化NFV架构图。该架构图为NFV ISG中定义了的参考架构。
如图1所示，NFV-MANO(NFV Management and Orchestration)由网络功能虚拟化编排器(NFVO Orchestrator)、虚拟化网络功能管理器(Virtual Network Function Manager，VNFM)和虚拟化基础设施管理器(Virtualized Infrastructure Manager，VIM)共同组成。
NFVO主要用于实现运营商域内(一个或多个数据中心)的网络业务(Network Service，NS)生命周期管理(如部署/扩容/缩容/下线等)，以及网络功能虚拟化基础设施层(Virtualised Network Function Infrastructure，NFVI)资源编排、策略管理等功能；Orchestrator根据网络服务描述器(Network Service Descriptor，NSD)分解出对各VNF(Virtualised Network Funct ion)的需求，配合VNFM实现虚拟化的网络功能(Virtual Network Funct ion，VNF)的部署。
VNFM主要用于实现VNF的生命周期管理，如部署/扩容/缩容/下线等自动化能力；VNFM根据模板及VNF容量需求，分解出对虚拟机等虚拟资源的需求，与NFVO、VIM配合完成VNF的实例化。
VIM为I层管理系统，比如Vmware,Openstack，实现基础设施层资源(包括计算、存储、网络资源)的管理和监控。
在NFV架构中还包括EMS/NMS(Element Management System/Network Management System)，EMS/NMS为网管，用于垂直拉通S层I层故障监控和定界，保持现有网管的管理能力，可以统一管理云化和非云化网元。
业务运营和管理平台(Operation-Support System/Business Support System，OSS/BSS)，可以统一管理云化和非云化网元。
图1所示的NFV架构中只示出一个网络业务NS中的一部分。在实际应用中，部署的一个网络业务中可能包括多个部分，例如要部署一个垂直行业的应用，可能要部署核心网(Evolved Packet Core，EPC)，IP多媒体子网络(IP Multimedia Subsystem，IMS)，以及IoT连接管理平台三个部分，每个部分都可以包括若干个VNF。
每个部分可能由不同的运营商提供，而每个部分可能由不同的厂商(供应商)提供；每个运营商提供的部分中的网元可能由其他的运营商或者第三方机构提供；为了管理上的 方便，每个厂商会给运营商提供不同的移动虚拟运营商(Mobile Virtual Network Operator，MVNO)系统或者不同的NVFM，在部署网络中就需要各个部分间进行协商，或者部署时需要与运营商或第三方机构的MANO进行协商，包括虚拟化网络功能VNF的部署位置，VNF的连通性，服务质量(Quality of Service，QoS)要求等。现有技术中还不能实现网络部署过程中各个部分之间的相互协调，部署网络的通用性和灵活性比较差。
本发明实施例提供了一种虚拟化网络的部署方法和部署系统，可以灵活应用在一个虚拟网络业务由多个部分构成时，执行虚拟化网络部署的场景。
例如涉及多个厂商、运营商或第三方分别负责部署多个部分中的一个部分的场景。如图2至图4所示的场景：部署一个虚拟网络，图2中虚拟网络包括两部分，可以分别为核心网EPC和IoT连接管理平台，这两部分由不同的供应商或第三方提供，即属于两个不同的管理域，每个管理域都有独立的网络功能虚拟化编排器NFVO和虚拟化网络功能管理器VNFM。
图3中的虚拟网络也包括两部分，分别为核心网EPC和IoT连接管理平台，其中，核心网EPC部分由一个运营商提供，IoT连接管理平台由另一个运营商提供，即两部分属于两个管理域。
图4中的虚拟网络包括三部分，分别为核心网EPC、IMS和IoT连接管理平台，每个部分由不同的设备商提供，具有独立的虚拟化网络功能管理器VNFM，但采用一个网络功能虚拟化编排器NFVO，即三个部分属于三个管理域。
需要说明的是，本发明实施例提供的部署方法和部署系统不仅可以应用在上述描述的由核心网EPC和IoT连接管理平台组成的虚拟化网络中，而且还可以应用在上述描述的由核心网EPC、IMS和IoT连接管理平台等部分组成的虚拟化网络中，并且不限于上述描述的系统，还可以应用于包括其他多个部分的部署系统中，也就是由多个组成部分构成的虚拟化网络。
本发明实施例需要部署的一个虚拟化网络中可以包括多个部分，每个部分可以由独立的管理域进行部署。在虚拟化网络部署时，先对需要部署的第一部分进行资源预留(只执行资源预留，不进行资源分配)，得到第一部分的编排信息，该编排信息是指对第一部分中的虚拟化网络功能VNF的位置等进行规划的信息；开始编排第二部分，获取第一部分的编排信息，根据第一编排信息中的虚拟化网络功能VNF的位置信息等信息编排第二部分中虚拟化网络功能VNF的位置等；当第二部分编排完成后确定第一部分的编排信息是否满足第二部分的编排需求，或者说第一部分的编排信息是否满足虚拟化网络的需求；当第一部分的编排信息满足第二部分的编排需求时，向第一部分反馈接受第一部分编排信息的接受信息，表示接受第一部分的编排(或部署)的方案，同时执行第二部分虚拟化网络的资源预留(值执行资源预留，不进行资源分配)；当第一部分的编排信息不满足第二部分的编排需求时，通知第一部分需要重新编排。
在虚拟化网络部署中，当存在除第一部分和第二部分之外的其他部分时，重复第一部分和第二部分的部署过程，直到所有的部分都部署完成。所有部分部署完成后执行各个部分的资源分配，以实现虚拟化网络业务由多个部分构成时，执行虚拟化网络的部署，各个部分之间能够相互协调，提高虚拟化网络部署的灵活性和通用性。
需要说明的是，部署中需要获取所有已部署完成部分的编排信息，在本发明实施例中， 可以获取与部署部分相关的所有已部署完成部分的编排信息。还需要说明的是，在本发明实施例中，部署可以理解为对网络业务中各个部分中的虚拟化网络功能VNF进行编排、规划的过程。
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明的一部分实施例，而不是全部实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都应属于本发明保护的范围。
在本发明实施例中，部署系统可以包括多个部分，每个部分可以由独立的网络功能虚拟化编排器NFVO进行网络业务的编排和规划，也可以由同一个网络功能虚拟化编排器NFVO对网络业务进行编排和规划。
图5为本发明实施例提供的一种网络功能虚拟化编排器NFVO的结构示意图。
如图5所示，该网络功能虚拟化编排器NFVO 200包括：接收器210、发送器220、处理器230、存储器240、通信接口250和通信总线260。接收器210、发送器220、处理器230、存储器240、通信接口250通过通信总线260连接，并完成相互之间的通信。接收器210、发送器220用于通过通信接口250接收其他设备发送的数据或向其他设备发送数据和指令。存储器240用来存储指令和数据。处理器230用于调用存储器中的指令，并执行相应的操作。
在本发明实施例中，处理器230可以是中央处理单元(Central Processing Unit，CPU)，该处理器230还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
存储器240可以包括只读存储器和随机存取存储器，并向处理器230提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。
通信总线260除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都标为通信总线260。
图6为本发明实施例提供的一种虚拟化网络的部署方法的流程图。
如图6所示，该部署方法300的执行主体为部署系统中各个网络功能虚拟化编排器NFVO，该部署方法可以包括以下步骤：
S301，第一网络功能虚拟化编排器NFVO接收业务运营和管理平台发送的第一部分部署请求，第一部分部署请求中包括资源预留的指示；
S302，第一NFVO向业务运营和管理平台发送资源预留完成信息；
S303，第二NFVO接收业务运营和管理平台发送的第二部分部署请求；
S304，第二NFVO获取第一部分的编排信息，根据第一部分的编排信息进行第二部分的编排；
S305，当第一部分的编排信息满足第二部分的编排需求时，第二NFVO向业务运营和管理平台发送接受信息，接受信息用于指示接受所述第一部分的编排信息；
S306，第一NFVO接收业务运营和管理平台发送的资源分配请求，请求第一部分的资源分配；
S307，当第一部分的编排信息满足第二部分的编排需求时，第二NFVO请求第二部分的资源分配。
具体的，虚拟化网络由多个部分组成，例如：需要为一个垂直行业的应用部署一个虚拟网络，可能需要部署核心网EPC和IoT连接管理平台。每个部分由独立的网络功能虚拟化编排器NFVO对每一部分的虚拟化网络进行编排和规划。
在本发明实施例中第一部分可以包括虚拟化网络需要部署的多个部分。在部署虚拟化网络时，需要先对部署的第一部分进行资源预留，该资源预留只执行资源预留，并不真正的分配资源预留。在本发明实施例中，虚拟化网络中包括的每个部分都需要进行资源预留，但除虚拟网络中的最后一个部署的部分，该部分可以认为是本发明实施例中的第二部分。
在本发明实施例中，也可以理解第一部分为虚拟网络中除需要部署的最后一个部分外的其他部分，部署过程中，部署部分的NFVO需要获取已部署完成的所有部分的编排信息，以完成虚拟化网络的部署，并请求资源分配。
在S301中，当部署虚拟化网络时，第一NFVO接收业务运营和管理平台(Operation-Support System/Business Support System，OSS/BSS)发送的第一部分资源预留请求，该第一部分部署请求中包括指示第一NFVO执行资源预留的指示。在S301中，第一NFVO需要根据虚拟化网络的需求，进行第一部分的编排和规划，完成网络模板的选择，以及各个虚拟化网络功能VNF配置数据的设定，即生成第一部分的编排信息，并请求进行资源预留。
当第一NFVO完成请求资源预留时，执行S302，第一NFVO向OSS/BSS发送资源预留完成信息，以通知OSS/BSS完成第一部分的资源预留。
在S303中，第二NFVO接收OSS/BSS发送的第二部分部署请求，以指示进行第二NFVO对第二部分进行部署。在第二NFVO对第二部分进行部署之前，第二NFVO需要获取第二部分部署虚拟化网络所依赖的第一部分的编排信息，该编排信息包括虚拟化网络功能VNF的位置信息，还可以包括虚拟化网络功能VNF的数量，虚拟链路VL信息、质量服务QoS等信息。
在S304中，第二NFVO根据S330中获取的第一部分的编排信息对第二部分需要部署的虚拟化网络功能VNF的位置等信息进行编排和规划，并确定第二部分部署完成后，第一部分的编排信息是否满足第二部分的编排需求，如果满足，执行S350，反之则执行S350’。
在S305中，当第二NFVO确定第一部分的编排信息满足第二部分的编排需求时，向OSS/BSS发送接受第一部分编排信息，也就是第一部分的编排和规划方案的信息，即接受信息。
需要说明的是，部署的虚拟化网络中的各个部分部署完成后，均需要确定该部分部署之前已部署完成部分的编排信息是否满足该部分的部署需求。
在S306中，第一NFVO根据接收到的第二NFVO发送的接受信息向第一部分中的虚拟化基础设施管理系统VIM发送获取资源分配请求，以完成对第一部分的资源分配。
在本发明实施例中，当第二NFVO向第一NFVO发送接受信息时，也就是第一部分编排信息满足第二部分的编排需求时，可以直接向第二部分中的基础设施管理系统VIM发送获取资源分配器请求，以完成第二部分的资源分配，即执行S307。
在本发明实施例中，所述部署方法还可以包括：
S305’，当第一部分的编排信息不满足第二部分的编排需求时，第二NFVO向业务运营 和管理平台发送拒绝消息，该拒绝消息用于指示不接受第一部分的编排信息；
S306’，第一NFVO接收业务运营和管理平台重新发送第一部分部署请求。
通过本发明实施例提供的一种虚拟化网络的部署方法，通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配，实现了虚拟化网络业务由多个部分组成时，执行虚拟化网络部署时，网络的不同部分之间能够相互协调，提高了网络部署的灵活性和通用性。
可选地，作为本发明另一实施例，如图7所示，在第一网络功能虚拟化编排器NFVO接收业务运营和管理平台发送的第一部分部署请求之后，该部署方法300还包括：
S308，第一NFVO生成第一部分的编排信息，
具体的，第一NFVO根据部署第一部分的虚拟化网络部署需求，进行第一部分的虚拟网络的规划，完成网络模板的选择，并配置各个虚拟化网络功能VNF的配置数据，完成第一部分的编排信息，该编排信息可以包括虚拟化网络功能的位置信息、数量、虚拟链路VL、服务质量QoS等信息。
可选地，作为本发明另一实施例，如图7所示，第二NFVO获取第一部分的编排信息，可以包括：第二NFVO从能力开放平台获取第一部分的编排信息。
在本发明实施例中，第二NFVO从能力开放平台获取第一部分的编排信息，可以具体包括：
S309，第二NFVO向能力开放平台发送获取请求，该获取请求用于指示获取第一部分的编排信息。
S310，第二NFVO接收能力开放平台发送的第一部分的编排信息。
具体的，第二NFVO根据接收到的第二部分部署请求，检查第二部分的虚拟化网络功能VNF依赖第一部分中的哪些虚拟化网络功能和虚拟链路等信息，也就是依赖第一部分中的哪些的编排信息，例如，第二部分为IoT连接管理平台，第一部分为核心网EPC，那么第二NFVO检查IoT连接管理平台需要依赖核心网EPC中的哪些虚拟化网络功能VNF和虚拟链路VL；或者第二部分为IMS，第一部分为核心网EPC，第二NFVO检查IMS需要依赖核心网EPC中的哪些虚拟化网络功能VNF和虚拟链路VL等。
第二NFVO确定第二部分需要依赖第一部分中的哪些编排信息之后，第二NFVO向能力开放平台发送获取请求，获取与第二部分由依赖关系的第一部分的编排信息，以用于能力开放平台根据获取请求，向第二NFVO发送以第二部分有依赖关系的第一部分的编排信息；第二NFVO接收能力开放平台发送的与第二部分有依赖关系的第一部分的编排信息，并根据该第一部分的编排信息进行第二部分的编排和规划。
在本发明实施例中，如图7所示，该部署方法300还包括：
S311，第一NFVO向能力开放平台发送第一部分的编排信息。
具体的，在第一NFVO根据部署第一部分的虚拟化网络需求生成第一部分的编排信息之后，可以将第一部分的编排信息发送给能力开放平台，以用于第二NFVO从能力开放平台获取与第二部分有依赖关系的第一部分的编排信息。
其中，编排信息可以包括虚拟化网络功能VNF部署的位置。需要说明的是，在本发明实施例中，编排信息中还可以包括虚拟化网络功能的数量、IP地址、虚拟链路VL信息和/或配置信息等等。
在本发明实施例中，第一NFVO向能力开放平台发送的编排信息可以依据虚拟化网络中各个部分之间的关系，或者说各个管理域之间的关系，确定发送的编排信息，因此，各个部分之间发送的编排信息可能不同，也就是说第一NFVO向能力开放中心发送的第一部分的编排信息不同，具体请参见表1。
例如，表1所示，如果管理域之间的关系紧密时，安全性要求不高，如各个部分由不同的管理域独立部署时，各个部分部署虚拟化网络功能VNF的相互影响的安全性低，可以发送管理域范围内使用的内部信息，如虚拟化网络功能VNF的部署位置中数据中心地理位置、数据中心名称等信息。
如果管理域之间的关系不紧密时，为了提高安全性，避免暴露管理域内部的架构等信息，发送管理域对外呈现的信息，如虚拟化网络功能VNF部署位置中数据中心地理位置或端口中外部网络的IP地址等信息。
在第一NFVO向能力开放平台发送第一部分的编排信息时，可以以虚拟化网络功能VNF和虚拟链路VL为粒度，即以VNF和VL为单位组织，如表1所示，第一NFVO向能力开放平台发送已部署完成的第一部分的虚拟化网络功能VNF，假设有两个VNF已经部署完成，则将部署完成的第一个虚拟化网络功能VNF中的虚拟化网络功能的ID，部署位置、端口、网络和配置数据等信息逐条发送完成后，进行第二个的虚拟化网络VNF中各条信息的发送；如果发送的编排信息中还包括虚拟链路VL时，也同样将第一条虚拟链路VL中的虚拟化网络功能的ID、服务质量QoS和配置数据等逐条完成之后再进行另一条虚拟链路VL中各条信息的发送。
需要说明的是，在以虚拟化网络功能VNF为粒度向能力开放平台发送已部署完成的编排信息时，编排信息可以包括虚拟化网络功能VNF中的部署位置，也可以包括虚拟化网络功能VNF中的虚拟化网络功能的ID，部署位置、端口、网络和配置数据等信息。以虚拟链路VL为粒度发送的编排信息包括虚拟链路VL中的虚拟化网络功能的ID、服务质量QoS和配置数据等信息。
需要说明的是，第一NFVO也可以只向能力开放平台发送管理域与外部有链接关系的VNF和VL。
表1
Figure PCTCN2017080110-appb-000001
Figure PCTCN2017080110-appb-000002
可选地，作为本发明另一实施例，如图8所示，第二NFVO获取第一部分的编排信息，可以包括：第二NFVO通过业务运营和管理平台从第一NFVO获取第一部分的编排信息。
在本发明实施例中，该过程可以具体包括：
S312，第二NFVO通过业务运营和管理平台向第一NFVO发送获取请求，该获取请求用于指示获取第一部分的编排信息。
S313，第二NFVO接收第一NFVO通过业务运营和管理平台发送的第一部分的编排信息。
具体的，在本发明实施例中，第二NFVO向业务运营和管理平台OSS/BSS发送获取请求，以获取与第二部分有依赖关系的第一部分的编排信息，以用于业务管理平台向第一NFVO转发该获取请求；第一NFVO根据获取请求通过OSS/BSS向第二NFVO发送第一部分的编排信息。
可选的，作为本发明另一实施例，如图9所示，第二NFVO获取第一部分的编排信息，可以包括：第二NFVO从第一NFVO中获取第一部分的编排信息。
在本发明实施例中，该过程可以具体包括：
S314，第二NFVO向第一NFVO发送获取请求，该获取请求用于指示获取第一部分的编排信息。
S315，第二NFVO接收第一NFVO发送的第一部分的编排信息。
具体的，在本发明实施例中，OSS/BSS向第二NFVO发送的第二部分部署请求中包括第一NFVO的互联网之间的协议(Internet Protocol，IP)地址。第二NFVO根据第二部分部署请求向第一NFVO发送获取与第二部分有关系的第一部分的编排信息；第二NFVO接收第一NFVO发送的第一部分的编排信息。
可选地，作为本发明另一实施例，如图10所示，第二NFVO获取第一部分的编排信息，还可以包括：
第二NFVO通过运营商提供的接口获取第一部分的编排信息，其具体过程可以包括：
S316，第二NFVO通过运营商提供的接口第一NFVO发送获取请求；
S317，第二NFVO接收第一NFVO通过运营商提供的接口发送的第一部分的编排信息。
具体的，在本发明实施例中，运营商提供的接口可以为运营商提供的Potal接口或者为能力开放平台，在这里，为了将该能力开放平台与之前提到的能力开放凭条进行区分，将该能力开放平台称之为第二能力开放平台，将之前提到的能力开放平台称之为第一能力 开放平台。
第二NFVO通过第二能力开放平台、第二部分中的业务运营和管理平台OSS/BSS(在这里称为第二OSS/BSS)和第一部分中的业务运营和管理平台OSS/BSS(这里称为第一OSS/BSS)向第一NFVO发送获取请求，第二NFVO接收第一NFVO通过第一OSS/BSS、第二能力开放平台和第二OSS/BSS发送的第一部分的编排信息。
在本发明实施例中，第二能力开放平台、第二OSS/BSS和第一OSS/BSS通过本身具有的转发信息的功能向第二或第一NFVO发送数据或指令。其通过第一OSS/BSS向第一NFVO或第二NFVO发送获取请求或第一部分的编排信息，具体过程与S314和S315类似，为简洁描述，在这里不再赘述。
可选地，在本发明实施例中，第二NFVO获取第一部分的编排信息，还可以包括：
第二NFVO通过运营商提供的接口向从第一能力开放平台中获取第一部分的编排信息。
该过程可以具体包括：
S318，第二NFVO通过运营商提供的接口向第一能力开放平台发送获取请求，该获取请求用于指示获取第一部分的编排信息。
S319，第二NFVO接收第一能力开放平台通过运营商提供的接口发送的第一部分的编排信息。
需要说明的是，该过程与S311和S322的过程类似，为了简洁描述，在这里不再赘述。
还需要说明的是，在本发明实施中，包括S313，为了简洁描述，在这里就不再赘述该过程。
可选地，作为本发明另一实施例，编排信息可以包括虚拟化网络功能VNF的部署位置信息，第二NFVO根据第一部分的编排信息进行第二部分的编排信息可以具体包括：第二NFVO根据第一部分编排信息中的虚拟化网络功能VNF的部署位置信息进行第二部分的编排。
在本发明实施例中，编排信息还可以包括虚拟化网络功能VNF的数量、配置信息，例如：规格(可以支持用户的数量等信息)，虚拟链路VL信息，以及服务质量QoS信息等。
通过本发明实施例提供的虚拟化网络的部署方法，通过对需要部署部分进行资源预留，资源预留后不执行资源分配，待所有的部署部分进行完成编排规划后，再进行资源分配，也可以说先预留资源进行协调，优化部署的过程，实现了虚拟网络业务由多个部分构成时，执行虚拟化网络的部署时，实现各部分之间的相互协调，提高了网络部署的灵活性和通用性。同时能适应多个厂商、多个运营商同时部署一个虚拟化网络的场景，提高了部署的自动化，同时提高了部署的效率。
为便于说明，下面结合图2至图4以及图11至图14对本发明实施例的技术方案进行详细的说明。应理解，这仅是用以说明本发明实施例的技术方案的一个例子，并不对本发明实施例构成任何的限定。
图11为本发明实施例提供的一种虚拟化网络的部署方法的流程图。
如图11所示的部署方法可以应用在如图2所示的场景:一个运营商需要部署一个虚拟网络，该虚拟网络中包括两个组成部分，分别为核心网EPC和IoT连接管理平台，且两个组成部分分别由不同的提供商(设备商)或者第三方提供，即存在两个管理域，每个管理域均有独立的NFVO和VNFM。
其中，EPC部分包括NFVO1、VNFM1和VIM1；IoT连接管理平台部分包括NFVO2、VNFM2 和VIM2。
如图11所示，该部署方法400包括以下步骤：
S401，OSS向NFVO1发送EPC部署请求。
具体的，OSS请求NFVO1部署虚拟化网络中的EPC部分，该EPC部署请求中包括资源预留的指示，用于指示NFVO1请求执行资源预留，由于虚拟化网络中还存在其他部分的部署，如IoT连接管理平台，所以OSS指示NFVO1只执行资源预留。
需要说明的是，S401只执行资源预留，不执行资源分配。
S402，NFVO1根据EPC部署虚拟化网络的需求，向VIM1发送资源预留请求。
具体的，NFVO1根据部署虚拟化网络中核心网EPC的需求，进行EPC网络的规划，完成网络模板的选择，以及各虚拟化网络功能VNF的配置，也就是设置配置数据，NFVO1接着向VIM1请求预留所需要的资源，该资源可以包括虚拟化网络功能VNF,虚拟链路VL等信息。
S403，VIM1资源预留后向NFVO1发送资源预留完成信息。
S404，NFVO1向VNFM1发送开始EPC部署请求，开始EPC部署请求中可以包括需要部署的NSD,VNFD，以及实例化需要的参数。
S405，VNFM1对开始EPC部署请求进行校验。
具体的，VNFM1对开始EPC部署请求的校验包括：对发送该开始EPC部署请求的发送者NFVO1是否授权的校验，开始EPC部署请求中参数有效性的校验，以及虚拟化网络功能VMF的生命周期管理的校验等。
其中，对参数有效性的校验可以包括参数技术上的正确性和策略上的顺从性的校验。对虚拟化网络功能VNF的生命周期管理的校验可以包括：针对虚拟化网络业务需要的每个虚拟化网络功能VNF实例，NFVO1通过与VNFM1之间的虚拟化网络VNF生命周期管理接口的虚拟化网络VNF查询操作检查是否已经存在满足需求的VNF实例，如果存在，将该VNF作为网络业务的一部分。
S406，VNFM1校验完成后，向NFVO1发送校验完成信息。
校验完成信息中包括确认检查的结果，即校验通过。
S407，NFVO1向能力开放平台发送EPC的编排信息，包括EPC的虚拟化网络功能VNF部署的位置信息和虚拟链路VL等。
具体的NFVO1向部署系统中的能力开放平台发送EPC的编排信息，包括虚拟化网络功能VNF部署的位置信息，虚拟链路VL，还可以包括配置信息，例如规格等信息，具体可见表1。根据部署EPC和IoT连接管理平台的管理域之间的关系，确定向能力开放平台发送的哪些信息，如果EPC和IoT连接管理平台两部分的管理域关系紧密，对安全性要求低，就传递内部的信息，例如虚拟数据中心ID等，否则就传递外部信息，例如数据中心的地理位置信息。
在向能力开放平台发送EPC的编排信息时可以以虚拟化网络功能VNF和虚拟链路VL为粒度，即信息以VNF，VL为单位组织。在本发明实施例中，可以只向能力开放平台发送有外部连接关系的虚拟化网络功能VNF和虚拟链路VL等信息。
S408，能力开放平台接收EPC的编排信息并保存，并向NFVO1发送已接收完成信息。
具体的，能力开放平台保存EPC部署虚拟化网络中各个虚拟化网络功能VNF,虚拟链路VL以及配置信息等，并发送确认消息给NFVO1，该确认消息用于指示能力开放平台成功接 收EPC的编排信息
S409，NFVO1向OSS发送资源预留完成信息，该资源预留完成信息用于通知OSS EPC部分的资源预留以及参数检查已经完成。
S410，OSS向NFVO2发送开始部署IoT连接管理平台请求。
具体的，OSS请求NFVO2部署虚拟化网络中的IoT连接管理平台部分，因为该虚拟网络中只存在EPC和IoT连接管理平台两部分，在IoT连接管理平台后不存在其他部分的部署，因此OSS向NFVO2发送的开始部署IoT连接管理平台请求中不需要包括指示NFVO2执行IoT连接管理平台部分的资源预留的指示。
S411，NFVO2检查IoT连接管理平台需要依赖的EPC的编排信息。
具体的，NFVO2准备部署IoT连接管理平台，在部署前，NFVO2检查IoT需要依赖EPC中哪些虚拟化网络功能VNF和虚拟链路VL，例如IoT连接管理平台需要和EPC中的HSS,PCRF，MTC-IWF都要连接，所以需要获取与EPC中的HSS,PCRF，MTC-IWF连接有关的虚拟化网络功能VNF和虚拟链路VL的信息。
S412，NFVO2向能力开放平台发送获取请求，该获取请求用于指示获取部署IoT连接管理平台需要依赖的EPC编排信息。
具体的，NFVO2向能力开放平台获取有依赖关系的VNF，VL等编排信息，即获取HSS，PCRF，MTC-IWF的编排信息，以及这些功能对IoT平台相关的VL信息。
S413，能力开放平台向NFVO2发送EPC的编排信息。
具体的，能力开放平台根据获取请求，查询之前在S408中获取到的EPC的虚拟化网络功能VNF,虚拟链路VL等编排信息，并反馈给NFVO2。
S414，NFVO2根据获取到的EPC的编排信息对IoT连接管理平台进行编排。
具体的，NFVO2根据S413中获取到的有依赖关系的虚拟化网络功能VNF，虚拟链路VL等编排信息后，开始进行IoT连接管理平台的编排和规划，具体来说根据相关的虚拟化网络功能VNF位置、数量等信息对IoT连接管理平台中虚拟化网络功能VNF的部署位置进行编排和规划，根据EPC中的虚拟链路VL设计IoT连接管理平台中虚拟链路VL的规格，服务质量QoS等；例如，IoT连接管理平台的设备触发功能需要与MTC-IWF建立连接，AAA服务器需要与HSS建立连接，在得到MTC-IWF，HSS的部署位置后，结合网络应用的需求才能确定设备触发和AAA部署的最佳位置，有些场景需要设备触发功能与MTC-IWF位置靠近。同时IoT平台也要根据链路的要求规划需要提供的资源。其中，AAA服务器是一个能够处理用户访问请求的服务器，提供验证(Authentication)、授权(Authorization)以及记账(Accounting)服务。
S415，当EPC的编排信息满足IoT连接管理平台的编排需求时，NFVO2向OSS发送接受信息，该接受信息表示接受EPC的编排信息。
具体的，NFVO2向OSS发送消息，指示EPC的编排信息满足IoT连接管理平台的部署需要，两者可以相容。
S416，OSS向NFVO1发送资源分配请求，该资源分配信息用于指示NFVO1请求资源分配。
具体的，OSS向NFVO1发送资源分配信息，指示组成部分EPC可以执行资源分配。
S417，NFVO1请求VIM1执行资源分配。
S418，VIM1返回资源分配完成信息，该资源完成信息用于指示资源分配完成。
这里步骤S402和S403先执行资源预留，后执行资源分配的目的是因为整个虚拟化网络部署涉及其他部分，如果EPC的编排信息不满足其他部分的编排需求，可进行调整。
S419，NFVO2向VNFM2发送部署IoT连接管理平台请求。
具体的，NFVO2请求VNFM2发起部署IoT连接管理平台的请求，该部署IoT连接管理平台的请求可以包括需要部署的NSD,VNFD，以及实例化需要的参数。
S420，VNFM2对部署IoT连接管理平台请求进行校验。
具体的，VNFM2对NFVO2发送的请求进行校验，包括参数的有效性，生命周期管理等。该步骤与S405中对部署EPC请求进行校验的过程类似，为简洁描述，在这里不在赘述。
S421，VNFM2向NFVO2发送校验结果信息。
该校验结果包括校验通过的确认检查的结果。
S422，NFVO2向VIM2发送资源分配请求。
具体的，NFVO2根据校验结果指示VIM2执行资源分配。
S423，VIM2返回消息指示资源分配完成。
至此，整个虚拟化网络的部署已完成。
本发明实施例中，当S414中，NFVO2分析后发现EPC的编排信息不能满足IoT连接管理平台的编排要求，例如IoT连接管理平台要求HSS部署在用户近端的数据中心上，以降低鉴权接入的时延，而当前HSS部署在远端的数据中心上时，该部署方法400还包括：
S415’，当EPC的编排信息不满足IoT连接管理平台的编排需求时时，NFVO2向OSS发送拒绝信息，该拒绝信息表示不接受EPC的编排信息。
具体的，NFVO2向OSS发送消息，指示EPC中哪些虚拟化网络功能VNF，或者虚拟链路VL的编排不满足IoT连接网络平台的编排需求，以及其他的具体原因。
S416’，OSS根据拒绝信息向NFVO1发送EPC资源预留请求。
具体的，OSS向NFVO1发送EPC资源预留请求，转发NFVO2编排IoT连接管理平台的需求，以便于NFVO1重新进行EPC的编排和资源预留，可以根据编排IoT连接管理平台的编排需求进行编排和资源预留，重复S402至S423。
图12为本发明实施例提供的另一种虚拟化网络的部署方法的流程图。
如图12所示的部署方法可以应用在如图2所示的场景中，虚拟网络可以由EPC和IMS两个部分组成。
其中，EPC部分包括NFVO1、VNFM1和VIM1；IMS部分包括NFVO2、VNFM2和VIM2。
图12所示的部署方法500与图7所示的方法400的区别在于，部署方法500是通过OSS进行编排信息的传递，而部署方法400是通过能力开放平台进行编排信息的传递。
如图12所示，该部署方法500包括以下步骤：
S501至S507为EPC部分预留资源，该过程与图11所示的S401至406和S409的执行过程是相同的，为简洁描述在这里就不再赘述。
S508，OSS向NFVO2发送开始部署IMS请求。
具体的，OSS请求NFVO2部署虚拟化网络中的IMS部分，因为该虚拟化网络中只存在EPC和IMS两部分，在IMS部分之后不存在其他部分的部署，因此OSS向NFVO2发送的开始部署IMS请求中不需要包括指示NFVO2执行IMS资源预留的指示。
S509，NFVO2检查IMS需要依赖的EPC的编排信息。
具体的，NFVO2准备部署IMS，在部署前，NFVO2检查IMS需要依赖EPC中的哪些虚拟化网络功能VNF和虚拟链路VL，例如IMS需要和EPC中的HSS,PCRF，PGW都要连接，所以需要获取与HSS,PCRF，PGW连接有关的虚拟化网络功能VNF，相关虚拟链路VL的信息。
S510，NFVO2向OSS发送获取请求，该获取请求用于指示获取部署IMS需要依赖的EPC的编排。
具体的，NFVO2向OSS获取有依赖关系的VNF,VL的编排信息，即获取HSS，PCRF,PGW的编排信息，以及这些功能对于IMS相关的VL信息；请求的粒度可以是VNF,VL，即以虚拟化网络功能VNF和虚拟链路VL为组织单位。
S511，OSS向NFVO2转发获取请求。
S512，NFVO1向OSS发送EPC的编排信息。
具体的，NFVO1根据获取请求，将IMS需要的VNF，VL的编排信息发送给OSS，该过程需要依赖EPC部分和IMS部分两者管理域之间的关系，其过程与S407的过程类似，具体可见表1，为简洁描述，在这里不再赘述。
S513，OSS向NFVO2转发EPC的编排信息。
S514，NFVO2根据获取到的EPC的编排信息对IMS进行编排。
具体的，NFVO2根据S513中获取到的有依赖关系的虚拟化网络功能VNF，虚拟链路VL等编排信息后，开始进行IMS的编排和规划，具体来说根据相关的虚拟化网络功能VNF部署位置、数量等信息对IMS中虚拟化网络功能VNF的部署位置进行编排和规划，根据EPC中的虚拟链路VL设计IMS中虚拟链路VL的规格，服务质量QoS等；例如IMS网络中的P-CSCF需要与PGW相连，在获得PGW的部署位置后，决策P-CSCF的部署位置，并且根据PGW的链路配置信息配置P-CSCF。
S515，当EPC的编片信息满足IMS的编排需求时，NFVO2向OSS发送接受信息，该接受信息表示接受EPC的编排信息。
具体的，NFVO2向OSS发送消息，指示EPC的编排方案满足IMS的编排需要，两者可以相容。
S516，OSS向NFVO1发送资源分配信息，该资源分配信息用于指示NFVO1请求资源分配。
具体的，OSS向NFVO1发送资源分配信息，指示EPC可以执行资源分配。
S517，NFVO1指示VIM1执行资源分配。
S518，VIM1返回资源分配完成信息，该资源完成信息用于指示资源分配完成。
这里步骤S502和S503先执行资源预留，后执行资源分配的目的是因为整个虚拟化网络部署涉及其他部分，如果EPC的编排信息不满足其他部分的编排需求，可进行调整。
S519，NFVO2向VNFM2发送部署IMS请求。
具体的，NFVO2请求VNFM2发起部署IMS的请求，该部署IoT连接管理平台的请求可以包括需要部署的NSD,VNFD，以及实例化需要的参数。
S520，VNFM2对部署IMS请求进行校验。
具体的，该步骤S520与S505中对EPC请求进行校验的过程类似，为简洁描述，在这里不再赘述。
S521，VNFM2向NFVO2发送校验结果信息。
该校验结果包括校验通过的确认检查的结果。
S522，NFVO2向VIM2发送资源分配请求。
具体的，NFVO2根据校验结果指示VIM2执行资源分配。
S523，VIM2返回消息指示资源分配完成。
至此，整个虚拟化网络的部署已完成。
本发明实施例中，当S514中，NFVO2分析后发现EPC的编排信息不能满足IMS的编排要求，例如IMS要求HSS部署在用户近端的数据中心上，以降低鉴权接入的时延，而当前HSS部署在远端的数据中心上时，该部署方法500还包括：
S515’，当EPC的编排信息不满足IMS的编排需求时，NFVO2向OSS发送拒绝信息，该拒绝信息表示不接受EPC的编排信息。
具体的，NFVO2向OSS发送消息，指示EC中哪些虚拟化网络功能VNF，或者虚拟链路VL的编排不满足IMS的编排需求，以及其他具体的原因。
S516’，OSS根据拒绝信息向NFVO1发送EPC资源预留请求。
具体的，OSS向NFVO1发送EPC资源预留请求，转发NFVO2编排IMS的需求，以便于NFVO1重新进行EPC的编排和资源预留，可以根据编排IMS的编排需求进行编排和资源预留，重复S502至S523。
图13为本发明实施例提供的另一种虚拟化网络的部署方法的流程图。
如图13所示的部署方法可以应用在如图2所示的场景中，虚拟网络可以由EPC和IMS两部分组成。
其中，EPC部分包括NFVO1、VNFM1和VIM1；IMS部分包括NFVO2、VNFM2和VIM2。
图13所示的部署方法600与图12所示的方法500的区别在于，部署方法600时通过NFVO间的接口进行编排信息的传递，而部署方法500是通过OSS进行编排信息的传递。
如图13所示，该部署方法600包括以下步骤：
S601至S607为EPC预留资源的过程与部署方法500中的S501至S507的过程是相同的，为简洁表述，在这里就不再赘述。
S608，OSS根据资源预留完成信息向NFVO2发送开始IMS部署请求，该部署IMS请求中包括NFVO1的IP地址。
具体的，OSS请求NFVO2部署虚拟网络中的IMS部分，因为该虚拟化网络中只存在EPC和IMS两部分，在IMS部分之后不存在其他部分的部署，因此OSS向NFVO2发送的开始部署IMS请求中不需要包括指示NFVO2执行IMS资源预留的指示。在本发明实施了中，，OSS将NFVO1的IP地址或者域名告诉NFVO2，是为了让IMS部分的NFVO2获取网络部署获取EPC网络部署的信息。
S609，NFVO2检查IMS需要依赖的EPC编排信息。
具体的，NFVO2准备部署IMS，在部署前，NFVO2检查IMS需要依赖EPC中的哪些虚拟化网络功能VNF和虚拟链路VL，例如IMS需要和EPC中的HSS,PCRF，PGW都要连接，所以需要获取与HSS,PCRF，PGW连接有关的虚拟化网络功能VNF，相关虚拟链路VL的信息。
S610，NFVO2根据部署IMS请求向NFVO1发送获取请求，该获取请求用于指示获取部署IMS需要依赖的EPC的部署和配置信息。
具体的，NFVO2向OSS获取有依赖关系的VNF,VL的编排信息，即获取HSS，PCRF,PGW的编排信息，以及这些功能对于IMS相关的VL信息；请求的粒度可以是VNF,VL，即以虚拟化网络功能VNF和虚拟链路VL为组织单位。
S611，NFVO1向NFVO2发送EPC的编排信息。
具体的，NFVO1根据获取请求，将IMS需要的VNF，VL的编排信息发送给OSS，该过程需要依赖EPC部分和IMS部分两者管理域之间的关系，其过程与S407的过程类似，具体可见表1，为简洁描述，在这里不再赘述。NFVO2获取到EPC的编排信息后，NFVO对IMS部分进行编排以及之后为EPC和IMS进行资源分配的步骤与S512至S521以及S514至S523相同，为简洁描述，在这里也不再进行赘述。
图14为本发明实施例提供的一种虚拟化网络的部署方法的流程图。
如图14所示的部署方法可以应用在如图3所示的场景:两个运营商(运营商A和运营商B)需要部署一个虚拟网络，该虚拟网络中包括两个组成部分，分别为核心网EPC和IoT连接管理平台，且EPC组成部分由一个运营商(运营商A)提供，IoT连接管理平台由另一个运营商(运营商B)提供，即存在两个管理域，每个管理域均有独立的NFVO和VNFM。
其中，运营商A内部的OSS1，NFVO1，VIM等执行EPC部分的部署；运营商B内部的OSS2，NFVO2，VIM2等执行IoT连接平台部分的部署。
如图14所示，该部署方法700包括以下步骤：
S701，OSS1指示为部署EPC预留资源。
具体的，运营商A内部的OSS1，NFVO1，VIM等执行EPC部分的部署，首先完成资源预留，其预留资源过程与部署方法400中的S401至S407的相同，为简洁描述，在这里就不再赘述。
S702，OSS1通过运营商B提供的Portal接口向能力开放平台2发送开始IoT连接管理平台部署请求。
具体的，OSS1开始发起IoT连接管理平台的部署，因为本身不具有部署能力，因此向运营商B提供的Portal接口发起请求。
S703，能力开放平台2向OSS2转发开始部署IoT连接管理平台请求。
S704，OSS2向NFVO2发送开始部署IoT连接管理平台请求。
S705，NFVO2检查IoT连接管理平台需要依赖的编排信息。
具体的，该步骤与S405的步骤相同，为简洁描述，在这里不再赘述。
S706，NFVO2向OSS2发送获取请求，该获取请求用于指示获取部署IoT连接管理平台需要依赖EPC的编排信息。
S707，OSS2向能力开放平台1转发获取请求。
S708，能力开放平台1根据获取请求向OSS2发送EPC的部署和配置信息。
S709，OSS2向NFVO2转发EPC的编排信息。
在本发明实施例中，NFVO2获取部署IoT连接管理平台所依赖的EPC的编排信息，还可以通过S706’至S713’实现。
S706’，NFVO2向OSS2发送获取请求，该获取请求用于指示获取部署IoT连接管理平台需要依赖的EPC的编排信息。
S707’，OSS2向能力开放平台2转发获取请求。
S708’，能力开放平台2通过Portal接口向运营A的OSS1转发获取请求。
S709’，OSS1向NFVO1转发获取请求。
S710’，NFVO1向OSS1发送EPC的编排信息。
S711’，OSS1向能力开放平台2转发EPC的编排信息。
S712’，能力开放平台2向OSS2转发EPC的编排信息。
S713’，OSS2向NFVO2转发EPC的编排信息。
S714，NFVO2根据获取到的EPC的编排信息对IoT连接管理平台进行部署。
当EPC的编排信息满足IoT连接管理平台的编排需求时，执行为EPC和IoT连接管理平台的资源分配，其操作步骤与部署方法400中的S415至S423相同，为简洁描述，在这里不再赘述。
当EPC的编排信息不满足IoT连接管理平台的编排需求时，重新请求对EPC部分进行编排和规划以及资源预留，其执行步骤与部署方法400中的S415’和S416’相同，为简洁描述，在这里不不再赘述。
以上图6至图14是对图2和图3两种不同应用场景下，虚拟化网络的部署方法的详细说明，下面结合图15对该部署系统进行详细说明。
图15为本发明实施例提供的一种部署系统，该系统1500可以由多个部分组成，包括第一网络功能虚拟化编排器NFVO 1510和第二NFVO 1520和业务运营和管理平台1530。
第一NFVO 1510用于接收业务运营和管理平台1530发送的第一部分部署请求，第一部分部署请求中包括资源预留的指示；向业务运营和管理平台发送资源预留完成信息；
第二NFVO 1520用于接收业务运营和管理平台1530发送的第二部分部署请求；获取第一部分的编排信息；根据第一部分的编排信息进行第二部分的编排；
当第一部分的编排信息满足第二部分的编排需求时，第二NFVO 1520向业务运营和管理平台1530发送接受信息，接受信息用于指示接受第一部分的编排信息；
第一NFVO 1510还用于，接收业务运营和管理平台1530发送的资源分配请求，请求第一部分的资源分配；
当第一部分的编排信息满足第二部分的编排需求时，第二NFVO 1520，用于请求第二部分的资源分配。
具体的，在本发明实施例中，虚拟化网络由多个部分组成，每个部分由独立的网络功能虚拟化编排器NFVO对每一部分的虚拟化网络进行编排和规划，第一部分和第二部分属于多个部分中的两个部分。在本发明实施例中，可以理解第一部分虚拟化网络中的多个部分，第二部分为虚拟化网络中的最后一个编排的部分。
在部署虚拟化网络时，需要对部署的第一部分进行资源预留，该资源预留只执行资源预留，并不真正的分配资源。在本发明实施例中，虚拟化网络中包括的每个部分都需要进行资源预留，但除虚拟网络中的最后一个部署的部分。
第一NFVO 1510根据接收到的业务运营和管理平台OSS/BSS 1530发送的第一部分部署请求，请求资源预留，并向OSS/BSS 1530发送资源预留完成信息；第二NFVO 1520接收OSS/BSS 1530发送的第二部分部署请求，并获取第一部分的编排信息，根据第一部分的编排信息进行第二部署的编排，确定第一部分的编排信息是否满足第二部分的编排需求；当 满足时，第二NFVO 1520向OSS/BSS 1530发送接受信息，通知OSS/BSS 1530接受第一部分的编排信息，即第一部分的编排和规划方案。
通过本发明实施例提供的一种部署系统，通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配，实现了虚拟化网络业务由多个部分组成时，执行虚拟化网络部署时，网络的不同部分之间能够相互协调，提高了网络部署的灵活性和通用性。
可选地，在本发明实施例中，当第一部分的编排信息不满足第二部分的编排需求时，第二NFVO 1520向OSS/BSS 1530发送拒绝信息，通知OSS/BSS 1530不接受第一部分的编排和规划方案。
可选地，作为本发明另一实施例，第一NFVO 1510还用于，生成第一部分编排信息。具体的，在第一网络功能虚拟化编排器NFVO 1510接收业务运营和管理平台发送的第一部分部署请求之后，根据部署第一部分的虚拟化网络部署需求，进行第一部分的虚拟网络的规划，完成网络模板的选择，并配置各个虚拟化网络功能VNF的配置数据，完成第一部分的编排信息，该编排信息可以包括虚拟化网络功能的位置信息、数量、虚拟链路VL、服务质量QoS等信息。
可选地，作为本发明另一实施例，第一NFVO 1510还用于，请求第一虚拟化基础设施管理器VIM资源预留；第一NFVO 1510还用于，接收第一VIM发送的资源预留完成信息。
可选地，作为本发明另一实施例，第二部分部署请求包括第一NFVO1510的IP地址。第二NFVO 1520具体用于，从第一NFVO 1510获取第一部分的编排信息。
可选地，作为本发明另一实施例，第二NFVO 1520具体用于，通过业务运营和管理平台1530从第一NFVO 1510获取第一部分的编排信息。
需要说明的是，在本发明实施例中每个部分还需要包括虚拟化网络功能管理器VNFM和虚拟化基础设施管理系统VIM，如图15所示。
可选地，作为本发明另一实施例，如图15，该部署系统1500还可以包括能力开放平台1540第二NFVO1520还用于，从能力开放平台获取第一部分的编排信息。
可选地，作为本发明另一实施例，第一NFVO 1510还用于，向能力开放平台1540发送第一部分的编排信息。
可选地，作为本发明另一实施例，编排信息包括虚拟化网络功能VNF的部署位置信息，第二NFVO1520根据虚拟化网络功能VNF的部署位置信息对第二部分进行编排。
通过本发明实施例提供的一种部署系统，通过对需要部署部分进行资源预留，资源预留后不执行资源分配，待所有的部署部分进行完成编排规划后，再进行资源分配，也可以说先预留资源进行协调，优化部署的过程，实现了虚拟网络业务由多个部分构成时，执行虚拟化网络的部署时，实现各部分之间的相互协调，提高了网络部署的灵活性和通用性。同时能适应多个厂商、多个运营商同时部署一个虚拟化网络的场景，提高了部署的自动化，同时提高了部署的效率。
还需要说明的是，图15提供的部署系统1500中的各个NFVO可以实现图6至图14所示的方法/步骤，为简洁描述，在这里就不再赘述。
本发明实施例还提供另一种虚拟化网络的部署方法，如图16所示。
图16为本发明实施例提供的另一种虚拟化网络的部署方法的流程图，该方法的执行主 体为部署系统中各个网络功能虚拟化编排器NFVO，该部署方法800可以包括以下步骤：
S801，第一虚拟化网络功能管理器VNFM接收网络功能虚拟化编排器NFVO发送的第一部分部署请求；
S802，第二VNFM接收NFVO发送的第二部分部署请求，该第二部分部署请求中包括第一部分的编排信息；
S803，第二VNFM对第二部分部署请求进行校验；
S804，当第一部分的编排信息满足第二部分的编排需求时，第二VNFM向NFVO发送接受信息，该接受信息用于指示接受第一部分的编排信息。
具体的，虚拟化网络由多个部分组成，多个部分可以由同一个的网络功能虚拟化编排器NFVO对各部分的虚拟化网络进行编排和规划，每个部分由独立的虚拟化网络功能管理器VNFM与NFVO配合完成虚拟化网络功能VNF的实例化。
在本发明实施例中，在部署虚拟化网络时，需要先对部署的第一部分进行资源预留，该资源预留只执行资源预留，不进行真正的资源分配。在本发明实施例中，每一部分都需要进行资源预留，但虚拟化网络中最后一个编排规划的部分不需要进行资源预留，在本发明实施例中，可以理解为第二部分。
在本发明实施例中，每部分的VNFM均需要对之前部署完成的所有部分的编排信息进行校验，以确定已完成部署的部分的编排信息是否满足该部分的编排需求，如果满足时，用于NFVO完成虚拟化网络的部署，并请求各个部分进行资源分配。
在S801中，当完成第一部分的资源预留时，第一部分中的第一VNFM接收网络功能虚拟化NFVO发送的第一部分部署请求。第一VNFM对该第一部分部署请求进行校验，包括对部署需要的参数、参数的有效性以及生命周期管理等进行校验。待校验完成后第一VNFM可以向NFVO发送校验完成信息，以通知NFVO对第一部分部署请求校验完成。
在S802中，第二VNFM接收NFVO发送的第二部分部署请求，该第二部分部署请求中还需要包括编排第二部分需要的各个参数。
在S803中，第二VNFM对第二部分部署请求进行校验，校验第二部分部署请求中包括的编排第二部分需要的各个参数的有效性，以及通过NFVO和VNFM之间的VNF生命周期管理接口的VNF查询操作检查是否已经存在满足第二部分编排需求的VNF实例，如果存在，可以将该VNF作为该虚拟化网络中第二部分的VNF的一部分；并确定第一部分的编排信息是否可以满足第二部分的编排需求。
如果第一部分的编排信息满足第二部分的编排需求时，执行S804，否则，执行S804’。
在S804中，第二VNFM向NFVO发送接受信息，以通知NFVO接受第一部分的编排和规划方案，第一部分的编排和规划方案与第二部分的编排和规划方案可以兼容，以便于NFVO请求各个部分的资源分配。
S804’，当第一部分的编排信息不满足第二部分的编排需求时，第二VNFM向NFVO发送拒绝信息，该拒绝信息用于指示不接受第一部分的编排信息；
S805’，第一VNFM重新接收第一部分部署请求。
通过本发明实施例提供的一种虚拟化网络的部署方法，通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配，实现了虚拟化网络业务由多个部分组成时，执行虚拟化网络部署时，网络的不同部分之间能 够相互协调，提高了网络部署的灵活性和通用性。
可选地，在本发明实施例中，编排信息可以包括虚拟化网络功能VNF的部署位置信息，第二VNFM对第二部分部署请求进行校验，包括：
第二VNFM确定虚拟化网路功能VNF的部署位置信息是否满足第二部分的编排需求。
需要说明的是，在本发明实施例中，编排信息还可以包括虚拟化网络功能的数量、IP地址、虚拟链路VL信息和/或配置信息等等。
为便于说明，下面结合图17对本发明实施例的技术方案进行详细的说明。应理解，这仅是用以说明本发明实施例的技术方案的一个例子，并不对本发明实施例构成任何的限定。
图17为本发明实施例提供的一种虚拟化网络的部署方法的流程图。
如图17所示的部署方法可以应用在如图4所示的场景:一个运营商A需要部署一个虚拟网络，该虚拟网络中包括三个组成部分，分别为核心网EPC、IMS和IoT连接管理平台，且三个组成部分分别由不同的提供商(设备商)提供，均使用独立的VNFM，但公用一个NFVO。
其中，EPC组成部分包括VNFM1；IMS包括VNFM2；IoT连接管理平台组成部分包括VNFM3。
如图17所示，该部署方法900包括以下步骤：
S901，OSS向NFVO发送开始部署请求。
具体的，OSS请求NFVO部署虚拟网络，包括EPC，IMS以及IoT连接管理平台三部分。
S902，NFVO向VIM发送对EPC资源预留请求。
具体的，NFVO根据部署虚拟化网络中EPC部分的需求，进行EPC网络的规划，完成网络模板的选择，以及各VNF的配置，即设置配置数据，NFVO接着向VIM请求所需要资源的预留，该资源包括VNF和VL等信息。
S903，VIM资源预留后向NFVO发送资源预留完成信息。
S904，NFVO1向VNFM1发送开始EPC部署请求，开始EPC部署请求中可以包括需要部署的NSD,VNFD，以及实例化需要的参数。
S905，VNFM1对开始EPC部署请求进行校验。
具体的，VNFM1对开始EPC部署请求的校验包括：对发送该开始EPC部署请求的发送者NFVO1是否授权的校验，开始EPC部署请求中参数有效性的校验，以及虚拟化网络功能VMF的生命周期管理的校验等。
其中，对参数有效性的校验可以包括参数技术上的正确性和策略上的顺从性的校验。对虚拟化网络功能VNF的生命周期管理的校验可以包括：针对虚拟化网络业务需要的每个虚拟化网络功能VNF实例，NFVO1通过与VNFM1之间的虚拟化网络VNF生命周期管理接口的虚拟化网络VNF查询操作检查是否已经存在满足需求的VNF实例，如果存在，将该VNF作为网络业务的一部分。
S906，VNFM1校验完成后，向NFVO发送校验完成信息。
校验完成信息中包括确认检查的结果，即校验通过。
S907，NFVO向VNFM2发送开始部署IMS请求。
具体的，NFVO请求VNFM2发起部署IMS的请求，消息中可以包括编排IMS部分需要的VNFD，VLD，以及实例化需要的参数,同时还需要包括EPC的编排信息，在本发明实施例中，可以只传递与IMS编排相关的EPC的编排信息。
S908，VNFM2对开始IMS部署请求进行校验。
具体的，VNFM2对NFVO发送的参数进行校验，包括参数的有效性，生命周期管理等，其具体校验过程与S905的校验过程类似，为简洁描述，在这里不再赘述。
在S908中，还需要确定EPC的编排信息是否满足IMS的编排需求。
S909，VNFM2校验完成后，向NFVO发送校验完成信息。
需要说明的是，如果VNFM2确定发现EPC的编排不能满足IMS的编排需求，则返回错误响应，请求NFVO重新进行EPC的部署请求。如果满足，则执行S910至S911。
S910，NFVO向VIM发送IMS资源预留请求。
S911，VIM根据IMS资源预留请求进行资源预留。
S912，NFVO根据IMS预留的资源向VNFM3发送开始部署IoT连接管理平台请求。
具体的，NFVO向VIM请求部署IMS所需要的资源的预留，包括VNF,虚拟链路VL。
NFVO请求VNFM3发起部署IoT的请求，消息可以包括编排第三部分需要部署的VNFD，VLD，以及实例化需要的参数,同时还需要包括EPC的编排信息和IMS的编排信息信息；在本发明实施例中，可以只传递与编排IoT连接管理平台相关的EPC、IMS的编排信息。
S913，VNFM3对开始IoT连接管理平台部署请求进行校验。
具体的，在S913中，其校验过程与S908的校验过程类似，为简洁描述，在这里就不再赘述。
但需要说明的是，在S913中还需要确定IMS的编排信息是否满足IoT连接管理平台的编排需求。
S914，VNFM3校验完成后，向NFVO发送校验完成信息。
S915，NFVO向VIM发送对EPC、IMS、IoT连接管理平台进行资源分配的资源分配请求。
S916，VIM为EPC、IMS和IoT连接管理平台分别分配资源，并向NFVO发送资源分配完成信息。
S917，NFVO向OSS发送部署完成信息，该部署完成信息用于指示虚拟网络部署完成。
本发明实施例还提供了一种部署系统，如图18所示。
图18为本发明实施例提供的一种部署系统的结构示意图，该部署系统1800可以包括第一虚拟化网络功能管理器VNFM1810和第二VNFM1820和网络功能虚拟化编排器NFVO1830。
第一VNFM1810用于在完成第一部分资源预留之后，接收网络功能虚拟化编排器NFVO 1830发送的第一部分部署请求。
第二VNFM1820用于接收NFVO 1830发送的第二部分部署请求，该第二部分部署请求中可以包括第一部分的编排信息；
第二VNFM1820还用于对第二部分部署请求进行校验
当第一部分的编排信息满足第二部分的编排需求时，第二VNFM1820用于向NFVO发送接受信息，接受信息用于指示接受第一部分的编排信息，并指示NFVO请求所述第一部分和第二部分的资源分配。
可选地，在本发明实施例中，编排信息可以包括虚拟化网络功能VNF的部署位置信息，第二VNFM1820还用于确定虚拟化网络功能VNF的部署位置信息是否满足第二部分的编排需求。
具体的，在本发明实施例中，部署系统1800可以包括多个部署部分，每个部署部分可以包括独立的虚拟化网络功能管理器VNFM，并与NFVO派和完成虚拟化网络功能VNF的部署 (或实例化)。
在本发明实施例中，只提到了第一部分、第二部分以及第一VNFM和第二VNFM，这仅仅是为了示意性的描述本实施例提供的技术方案，在这里，可以将第一部分、第一VNFM理解为多个虚拟化网络的部分、多个VNFM。
需要说明的是，在本发明实施例中，虚拟化网络中最后一个部署部分是不需要进行资源预留的，因此，虚拟网络中最后一个部署的部分可以理解为本发明实施例中的第二部分，该部分由第二VNFM进行虚拟化网络功能的管理。
应理解，在本发明实施例中还需要包括业务运营和管理平台1840，用于向NFVO1830请求开始部署请求；虚拟化基础设施管理系统VIM，用于为部署部分预留资源和分配资源
本发明实施例提供的一种部署系统，通过对需要部署的部分进行资源预留，资源预留后不执行资源分配，待所有部分完成部署规划后，再进行资源分配，实现了虚拟化网络业务由多个部分组成时，执行虚拟化网络部署时，网络的不同部分之间能够相互协调，提高了网络部署的灵活性和通用性。
还需要说明的是，图18提供的部署系统1800中的各个VNFM可以实现图16和图17所示的方法/步骤，为简洁描述，在这里就不再赘述。
专业人员应该还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
结合本文中所公开的实施例描述的方法或算法的步骤可以用硬件、处理器执行的软件模块，或者二者的结合来实施。软件模块可以置于随机存储器(RAM)、内存、只读存储器(ROM)、电可编程ROM、电可擦除可编程ROM、寄存器、硬盘、可移动磁盘、CD-ROM、或技术领域内所公知的任意其它形式的存储介质中。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (22)

  1. 一种虚拟化网络的部署方法，其特征在于，虚拟化网络由多个部分组成，所述部署方法包括：
    第一网络功能虚拟化编排器NFVO接收业务运营和管理平台发送的第一部分部署请求，所述第一部分部署请求中包括资源预留的指示；
    所述第一NFVO向所述业务运营和管理平台发送资源预留完成信息；
    第二NFVO接收所述业务运营和管理平台发送的第二部分部署请求；
    所述第二NFVO获取第一部分的编排信息，根据所述第一部分的编排信息进行所述第二部分的编排；
    当所述第一部分的编排信息满足所述第二部分的编排需求时，所述第二NFVO向所述业务运营和管理平台发送接受信息，所述接受信息用于指示接受所述第一部分的编排信息；
    所述第一NFVO接收所述业务运营和管理平台发送的资源分配请求，请求所述第一部分的资源分配；
    当所述第一部分的编排信息满足所述第二部分的编排需求时，所述第二NFVO请求所述第二部分的资源分配。
  2. 根据权利要求1所述的部署方法，其特征在于，在所述第一网络功能虚拟化控制器NFVO接收业务运营和管理平台发送的第一部分部署请求之后，所述部署方法还包括：
    所述第一NFVO请求第一虚拟化基础设施管理器VIM资源预留；
    所述第一NFVO接收所述第一VIM发送的资源预留完成信息。
  3. 根据权利要求1或2所述的部署方法，其特征在于，在所述第一网络功能虚拟化编排器NFVO接收业务运营和管理平台发送的第一部分部署请求之后，所述部署方法还包括：
    所述第一NFVO生成所述第一部分的编排信息。
  4. 根据权利要求1-3任一项所述的部署方法，其特征在于，所述第二NFVO获取第一部分的编排信息，包括：
    所述第二NFVO从所述第一NFVO获取所述第一部分的编排信息。
  5. 根据权利要求4所述的部署方法，其特征在于，所述第二部分部署请求包括所述第一NFVO的IP地址。
  6. 根据权利要求1-3所述的部署方法，其特征在于，所述第二NFVO获取所述第一部分的编排信息，包括：
    所述第二NFVO通过所述业务运营和管理平台从所述第一NFVO获取所述第一部分的编排信息。
  7. 根据权利要求1-3任一项所述的部署方法，其特征在于，所述第二NFVO获取第一部分的编排信息，包括：
    所述第二NFVO从能力开放平台获取所述第一部分的编排信息。
  8. 根据权利要求7所述的部署方法，其特征在于，所述部署方法还包括：
    所述第一NFVO向能力开放平台发送所述第一部分的编排信息。
  9. 根据权利要求1-8任一项所述的部署方法，其特征在于，所述编排信息包括虚拟化网络功能VNF的部署位置信息，所述根据所述第一部分的编排信息进行所述第二部分的编排， 包括：
    根据所述虚拟化网络功能VNF的部署位置信息对所述第二部分进行编排。
  10. 一种虚拟化网络的部署系统，其特征在于，所述部署系统包括第一网络功能虚拟化编排器NFVO和第二NFVO；
    所述第一NFVO，用于接收业务运营和管理平台发送的第一部分部署请求，所述第一部分部署请求中包括资源预留的指示；向所述业务运营和管理平台发送资源预留完成信息；
    第二NFVO用于接收所述业务运营和管理平台发送的第二部分部署请求；获取第一部分的编排信息；根据所述第一部分的编排信息进行所述第二部分的编排；当所述第一部分的编排信息满足所述第二部分的编排需求时，所述第二NFVO向所述业务运营和管理平台发送接受信息，所述接受信息用于指示接受所述第一部分的编排信息；
    所述第一NFVO还用于，接收所述业务运营和管理平台发送的资源分配请求，请求所述第一部分的资源分配；
    所述第二NFVO，还用于当所述第一部分的编排信息满足所述第二部分的编排需求时，请求所述第二部分的资源分配。
  11. 根据权利要求10所述的部署系统，其特征在于，
    所述第一NFVO，还用于请求第一虚拟化基础设施管理器VIM资源预留；
    接收所述第一VIM发送的资源预留完成信息。
  12. 根据权利要求10或11所述的部署系统，其特征在于，
    所述第一NFVO，还用于生成所述第一部分编排信息。
  13. 根据权利要求10-12任一项所述的部署系统，其特征在于，所述第二NFVO用于获取第一部分的编排信息，具体包括：所述第二NFVO用于从所述第一NFVO获取所述第一部分的编排信息。
  14. 根据权利要求13所述的系统，其特征在于，
    所述第二部分部署请求包括所述第一NFVO的IP地址。
  15. 根据权利要求10-12任一项所述的部署系统，其特征在于，所述第二NFVO用于获取第一部分的编排信息，具体包括：
    所述第二NFVO用于通过所述业务运营和管理平台从所述第一NFVO获取所述第一部分的编排信息。
  16. 根据权利要求10-12任一项所述的部署系统，其特征在于，所述第二NFVO用于获取第一部分的编排信息，具体包括：
    所述第二NFVO用于从能力开放平台获取所述第一部分的编排信息。
  17. 根据权利要求16所述的部署系统，其特征在于，
    所述第一NFVO，还用于向能力开放平台发送所述第一部分的编排信息。
  18. 根据权利要求10-17任一项所述的部署系统，其特征在于，所述编排信息包括虚拟化网络功能VNF的部署位置信息，所述第二NFVO用于根据所述第一部分的编排信息进行所述第二部分的编排，具体包括：所述第二NFVO用于根据所述虚拟化网络功能VNF的部署位置信息对所述第二部分进行编排。
  19. 一种虚拟化网络的部署方法，其特征在于，虚拟化网络由多个部分组成，所述部署方法包括：
    第一虚拟化网络功能管理器VNFM接收网络功能虚拟化编排器NFVO发送的第一部分部署 请求；
    第二VNFM接收所述NFVO发送的第二部分部署请求，所述第二部分部署请求中包括第一部分的编排信息；
    所述第二VNFM对所述第二部分部署请求进行校验；
    当所述第一部分的编排信息满足所述第二部分的编排需求时，所述第二VNFM向所述NFVO发送接受信息，所述接受信息用于指示接受所述第一部分的编排信息。
  20. 根据权利要求19所述的部署方法，其特征在于，所述编排信息包括虚拟化网络功能VNF的部署位置信息，所述第二VNFM对所述第二部分部署请求进行校验，包括：
    所述第二VNFM确定所述虚拟化网络功能VNF的部署位置信息是否满足所述第二部分的编排需求。
  21. 一种虚拟化网络的部署系统，其特征在于，所述部署系统包括第一虚拟化网络功能管理器VNFM和第二VNFM；
    所述第一VNFM，用于接收网络功能虚拟化编排器NFVO发送的第一部分部署请求；
    所述第二VNFM，用于接收所述NFVO发送的第二部分部署请求，所述第二部分部署请求中包括第一部分的编排信息；
    所述第二VNFM还用于，对所述第二部分部署请求进行校验；当所述第一部分的编排信息满足所述第二部分的编排需求时，所述第二VNFM用于向所述NFVO发送接受信息，所述接受信息用于指示接受所述第一部分的编排信息。
  22. 根据权利要求21所述的部署系统，其特征在于，所述编排信息包括虚拟化网络功能VNF的部署位置信息，所述第二VNFM还用于确定所述虚拟化网络功能VNF的部署位置信息是否满足所述第二部分的编排需求。
PCT/CN2017/080110 2016-04-22 2017-04-11 虚拟化网络的部署方法和部署系统 WO2017181875A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610259561.2A CN107306201A (zh) 2016-04-22 2016-04-22 虚拟化网络的部署方法和部署系统
CN201610259561.2 2016-04-22

Publications (1)

Publication Number Publication Date
WO2017181875A1 true WO2017181875A1 (zh) 2017-10-26

Family

ID=60115665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/080110 WO2017181875A1 (zh) 2016-04-22 2017-04-11 虚拟化网络的部署方法和部署系统

Country Status (2)

Country Link
CN (1) CN107306201A (zh)
WO (1) WO2017181875A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112003931A (zh) * 2020-08-21 2020-11-27 济南浪潮数据技术有限公司 一种编排控制器部署方法、系统及相关组件
CN113495869A (zh) * 2020-03-20 2021-10-12 华为技术有限公司 文件系统空间的调整方法、装置和电子设备
WO2023217639A1 (fr) * 2022-05-12 2023-11-16 Orange Procédé, dispositif et système d'élaboration dynamique d'une infrastructure de données
WO2024046298A1 (zh) * 2022-08-31 2024-03-07 华为技术有限公司 创建虚拟网络的方法和装置

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109218086B (zh) * 2018-09-05 2022-10-25 全球能源互联网研究院有限公司 一种交换网构建方法与系统
CN111953503B (zh) * 2019-05-14 2023-04-07 中国电信股份有限公司 Nfv资源部署编排方法和网络功能虚拟化编排器
CN112583615B (zh) 2019-09-29 2022-04-29 北京华为数字技术有限公司 Vnf实例化方法、nfvo、vim、vnfm及系统
CN112910673B (zh) * 2019-12-04 2023-05-09 中国移动通信有限公司研究院 一种确定网元部署信息的方法、装置、设备及存储介质
CN111679893A (zh) * 2020-04-23 2020-09-18 平安科技（深圳）有限公司 运行系统构建方法、装置、电子设备及存储介质
CN113691383B (zh) * 2020-05-18 2023-03-31 中国电信股份有限公司 部署虚拟化网络功能实体的方法以及管理器和编排器
CN111901154B (zh) * 2020-07-04 2022-05-27 烽火通信科技股份有限公司 基于nfv的安全架构系统和安全部署及安全威胁处理方法
TWI760948B (zh) * 2020-11-30 2022-04-11 中華電信股份有限公司 用於管理電信等級虛擬網路服務之加速資源分配之系統、方法及電腦可讀取儲存媒體

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104734931A (zh) * 2015-03-31 2015-06-24 华为技术有限公司 一种虚拟网络功能间链路建立方法及装置
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备
EP2940968A1 (en) * 2014-04-30 2015-11-04 Hewlett-Packard Development Company, L.P. Network infrastructure management
WO2015172362A1 (zh) * 2014-05-15 2015-11-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 华为技术有限公司 一种虚拟网络业务部署方法和设备
EP2940968A1 (en) * 2014-04-30 2015-11-04 Hewlett-Packard Development Company, L.P. Network infrastructure management
WO2015172362A1 (zh) * 2014-05-15 2015-11-19 华为技术有限公司 一种网络功能虚拟化网络系统、数据处理方法及装置
CN104734931A (zh) * 2015-03-31 2015-06-24 华为技术有限公司 一种虚拟网络功能间链路建立方法及装置

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113495869A (zh) * 2020-03-20 2021-10-12 华为技术有限公司 文件系统空间的调整方法、装置和电子设备
CN113495869B (zh) * 2020-03-20 2024-04-26 华为技术有限公司 文件系统空间的调整方法、装置和电子设备
CN112003931A (zh) * 2020-08-21 2020-11-27 济南浪潮数据技术有限公司 一种编排控制器部署方法、系统及相关组件
CN112003931B (zh) * 2020-08-21 2023-04-18 济南浪潮数据技术有限公司 一种编排控制器部署方法、系统及相关组件
WO2023217639A1 (fr) * 2022-05-12 2023-11-16 Orange Procédé, dispositif et système d'élaboration dynamique d'une infrastructure de données
FR3135584A1 (fr) * 2022-05-12 2023-11-17 Orange Procédé, dispositif et système d’élaboration dynamique d’une infrastructure de données
WO2024046298A1 (zh) * 2022-08-31 2024-03-07 华为技术有限公司 创建虚拟网络的方法和装置

Also Published As

Publication number Publication date
CN107306201A (zh) 2017-10-31

Similar Documents

Publication Publication Date Title
WO2017181875A1 (zh) 虚拟化网络的部署方法和部署系统
US11032214B2 (en) Method, apparatus, and system for managing network slice instance
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
US11063831B2 (en) Network slice management method and apparatus
EP3313023B1 (en) Life cycle management method and apparatus
WO2018006381A1 (zh) 一种网络资源的管理方法、装置及系统
EP3512233A1 (en) Method for managing network slice and management unit
WO2017148249A1 (zh) 配置资源的方法及其网络设备
US10848366B2 (en) Network function management method, management unit, and system
JP2018530214A (ja) ネットワークサービスをデプロイするための方法及び装置
US20190281503A1 (en) Management Method, Management Unit, and System
WO2018082491A1 (zh) 扩展网络切片实例的方法、网络设备和网络构架
WO2018072503A1 (zh) 软件修改的发起方法、发布元数据的方法及装置
EP3349397A1 (en) Scaling out method, device and system
KR102086486B1 (ko) 네트워크 서비스 디스크립터를 온-보딩하기 위한 방법 및 장치
US11175955B2 (en) Network function virtualization system and network service instantiation method
WO2019174000A1 (zh) 用于业务管理的方法和装置
WO2017035738A1 (zh) 一种资源管理方法及装置
US10999211B2 (en) Resource authorization method for deployment of virtual network function, virtual network function manager, and network function virtualization orchestrator
US20230261950A1 (en) Method of container cluster management and system thereof
EP3468105A1 (en) Method and apparatus for arranging network resources
WO2020135517A1 (zh) 部署虚拟化网络功能的方法和装置
WO2020133691A1 (zh) 一种嵌入式系统驱动层的实现方法和装置
WO2024046298A1 (zh) 创建虚拟网络的方法和装置
WO2021129868A1 (zh) 网络服务实例化的方法及网络功能虚拟化编排器

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17785360

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17785360

Country of ref document: EP

Kind code of ref document: A1