WO2016180143A1 - 一种网络功能虚拟化***及网络服务实例化方法 - Google Patents

一种网络功能虚拟化***及网络服务实例化方法 Download PDF

Info

Publication number
WO2016180143A1
WO2016180143A1 PCT/CN2016/079197 CN2016079197W WO2016180143A1 WO 2016180143 A1 WO2016180143 A1 WO 2016180143A1 CN 2016079197 W CN2016079197 W CN 2016079197W WO 2016180143 A1 WO2016180143 A1 WO 2016180143A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
resource
nfv
vnf
vnfm
Prior art date
Application number
PCT/CN2016/079197
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 中兴通讯股份有限公司
Priority to US15/768,502 priority Critical patent/US11175955B2/en
Priority to EP16791993.5A priority patent/EP3364606B1/en
Publication of WO2016180143A1 publication Critical patent/WO2016180143A1/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
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
    • H04L12/4683—Dynamic sharing of VLAN information amongst network nodes characterized by the protocol used
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • 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
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • the present application relates to, but is not limited to, the field of network function virtualization, and in particular, to a network function virtualization system and a network service instantiation method.
  • the network operator's network is deployed through large, growing, dedicated hardware devices.
  • the introduction of a new network service usually requires another variant, and now it is increasingly difficult to find space and power; in addition, energy consumption is increasing, capital investment is challenging, and the necessary skills are lacking to design Integrate and operate increasingly complex hardware devices.
  • NFV Network Function Virtualization
  • Figure 1 shows the NFV system defined by ETSI (European Telecommunications Standards Institute) in the first phase.
  • NFV MANO Management and Orchestration, Management and Orchestration
  • NFVO Network Function Virtualization Orchestrator
  • NS Network Service
  • VNF Virtualized Network Function
  • NFV Instances Instance
  • NFVI Network Function Virtualization Infrastructure Resources
  • VNFM Virtualized Network Function Manager
  • VIM Virtualized Infrastructure Manager
  • NFVO and VNFM and VIM, VNFM and VIM are set with Main NFV reference points (main network function virtualization reference point), and Figure 1 is short vertical on the solid line.
  • Lines indicate that Or-Vnfm, Or-Vi, Vi-Vnfm in Figure 1, NFVO and NS Catalogue, VNF Catalogue, NFV Instances, NFVI Resources, and VNFM and VNF Catalogue are provided with Other NFV reference points ( Other network function virtualization reference points), shown in Figure 1 as short vertical lines on the dotted line.
  • NFVO and OSS Interation support system
  • BSS Business support system
  • VNFM and EM Element Manage
  • VNFVI Network Function Virtualization Infrastructure
  • Main NFV reference points which are Os-Ma-nfvo, Ve-Vnfm-em, Ve-Vnfm-vnf, Nf-Vi in Figure 1
  • OSS Other NFV reference points are set between /BSS and EM, NFVI, EM and VNF
  • Execution reference points are set between VNF and NFVI: Vn-Nf, in Figure 1 there are origins at both ends A short vertical line representation on a solid line.
  • Figure 2 is a draft of the second phase definition, the separation of resources and service orchestration management, canceling the NFV MANO in Figure 1; dividing NFVO into NSO (Network Service Orchestrator) and CDRO (Cross-domain) Resource Orchestrator, cross-domain resource orchestrator, replaces EM with ENMS (Network Management System). Classify OSS/BSS, ENMS, VNF, NS Catalogue, VNF Catalogue, VNFM, and NSO into TENANT DOMAIN (rental domain); divide CDRO, NFV Instances, NFVI Resources, VIM, and NFVI into NFVINFRASTRUCTURE DOMAIN (infrastructure domain).
  • NSO Network Service Orchestrator
  • CDRO Cross-domain resource orchestrator
  • the Main NFV reference points set between NSO and VNFM, OSS/BSS, VNFM and VIM, ENMS, VNF are respectively in Figure 2: Nfvo-Vnfm, Os-Nfvo, Vnfm-Vi, VeEn-Vnfm , VeNf-Vnfm; Main NFV reference points set between CDRO and VIM, VIM and NFVI are respectively in Figure 2: Nfvo-Vi, Nf-Vi; Execution reference points between VNF and NFVI are Vn -Nf.
  • the NFV implementation process may first implement a single-domain NFV, which may be extended to the whole domain in the future; or it may be implemented in a certain administrative domain and then extended to the full-administrative domain. At this point, a single service orchestration is difficult to meet the requirements.
  • the embodiment of the invention discloses an NFV system and a network service instantiation method, which can meet the requirements of the phased evolution of the current NFV system implementation and the requirements of multinational, inter-regional, multi-vendor service and multi-layer management.
  • the embodiment of the invention provides a network function virtualization (NFV) system, including:
  • VNFM Single Domain Virtualized Network Function Manager
  • VNF Single Domain Virtualized Network Function
  • VNF Virtualized Network Function
  • VIP Virtualized Infrastructure Manager
  • NFV-DO network function virtualization single domain orchestrators
  • the NFV-DO includes: a Virtualized Network Function Orchestrator (VNFO) configured to: manage any one or more of the following functions of a single domain: a network service instance, a network service life cycle, a VNFM instantiation, an instance of a VNF The life cycle of VNF.
  • VNFO Virtualized Network Function Orchestrator
  • the NFV-DO further includes:
  • the single-domain resource orchestrator is configured to perform one or more of the following processes in the single domain: VNF instance and resource association, resource authentication and management, resource orchestration policy management, and resource monitoring.
  • the NFV system further includes:
  • NFVO Network Function Virtualization Orchestrator
  • the NFVO includes a service orchestrator (SO) and a cross-domain resource orchestrator (CDRO);
  • the SO interacts with one or more of the docked VNFOs and interacts with an Operational Support System (OSS) or a Business Support System (BSS), configured to: perform one or more of the following processing across domains: a network Service orchestration, management of network service instances, network service lifecycle management, network services, and policy management of VNF instances;
  • OSS Operational Support System
  • BSS Business Support System
  • the CDRO interacts with one or more NFV-DOs that are docked, and/or with a plurality of VIMs, Set to: perform one or more of the following processing across domains: resource authentication and management, resource orchestration policy management, and resource monitoring.
  • the NFVO belongs to a network service layer; the NFV-DO, VNFM, and VNF entities belong to a domain layer; the VIM belongs to a virtual resource layer;
  • the system further includes: a computing resource pool, a network resource pool, a storage resource pool belonging to the virtual resource layer; and an infrastructure belonging to the physical layer.
  • the RO is set to: forward a resource request in a single domain to the CDRO, or send to a VIM;
  • the NFV-DO includes an RO, and the RO is set to: send a resource request in a single domain to the VIM;
  • An embodiment of the present invention further provides a network service instantiation method applied to the NFV system, which includes:
  • VNFO single-domain virtualized network function orchestrator
  • the VNFO After receiving the resource reservation information indicating that the resource reservation application is successful, the VNFO initiates a VNF instantiation request to the virtualized network function manager (VNFM) of the single domain;
  • VNFM virtualized network function manager
  • the VNFM initiates a resource instantiation request to a Virtualization Infrastructure Manager (VIM) based on the resource reservation information.
  • VIP Virtualization Infrastructure Manager
  • the sending resource reservation application includes:
  • the VNFO determines that the single domain has a resource orchestrator (RO)
  • the VNFO sends a resource reservation application to the RO;
  • the RO determines whether the RO is a channel, and if it is a channel, the RO sends the resource reservation request to a cross-domain resource orchestrator (CDRO); if not, the RO sends a resource reservation request Give VIM;
  • CDRO cross-domain resource orchestrator
  • the VNFO sends a resource reservation request to the CDRO; the CDRO initiates a resource reservation request to the VIM.
  • the method further includes:
  • the CDRO receives the resource reservation information of the VIM feedback, and feeds back to the VNFO that sends the resource reservation application.
  • the method before the VNFO of the single domain receives the VNF instantiation request, the method further includes:
  • the service orchestrator receives the network service instantiation request; determines the home domain of the VNF instance in the service; if it belongs to the single domain, delivers the VNF instantiation request to the VNFO of the single domain to which the VNF instance belongs; A cross-domain VNF instantiates a cross-domain VNF instantiation request to a cross-domain independent VNFM.
  • the method further includes:
  • a cross-domain independent VNFM initiates a resource reservation application to the CDRO
  • the CDRO initiates a resource reservation request to the VIM, and receives resource reservation information fed back by the VIM and sends the resource reservation information to the inter-domain independent VNFM;
  • the cross-domain independent VNFM initiates a resource instantiation request to the VIM according to the resource reservation information.
  • an embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, where the computer executable instructions are implemented to implement the network service instantiation method.
  • the embodiments of the present invention can meet the requirements of the phased evolution of the current NFV system implementation and the requirements for multinational, cross-regional, multi-vendor provision of services and multi-layer management.
  • Figure 1 is a NFV system diagram defined in the first phase of the ETSI Standards Organization
  • Figure 2 is a draft NFV system defined in the second phase of the ETSI Standards Organization
  • Figure 3 is a schematic illustration of the NFV system of the first embodiment
  • FIG. 5 is a flowchart of a method for implementing an NFV system of Embodiment 1;
  • FIG. 6 is a schematic diagram of an implementation of a networkless service layer in the NFV domain of Embodiment 1;
  • FIG. 7 is a schematic diagram of an implementation of a network service layer in the NFV field of Embodiment 2;
  • FIG. 8 is a schematic diagram of an implementation of a network service layer, a domain layer, and an RO forwarding channel in the NFV domain of Embodiment 3;
  • FIG. 9 is a schematic diagram of an implementation scheme of a network service layer, a domain layer, and no RO in the NFV domain of the implementation example 4;
  • FIG. 10 is a schematic diagram of an embodiment of a network service layer with no domain layer in the NFV field of Embodiment 5;
  • FIG. 11 is a schematic diagram of an implementation scheme of a network service layer, a domain layer, and a cross-domain VNFM in the NFV domain of Embodiment 6;
  • FIG. 12 is a schematic flowchart of instantiation of a network service according to Embodiment 2;
  • Figure 13 is a schematic diagram showing an example of the second embodiment.
  • This embodiment provides an NFV system, as shown in FIG. 3, including:
  • NFV-DO Network Function Virtualization Domain Orchestrate
  • VNFM Single Domain Virtualized Network Function Manager
  • VNF Single Domain Virtualized Network Function Entity
  • VIM Virtualized Infrastructure Management
  • the VNFM is configured to: manage the NFV entity
  • the NFV-DO may have one or more, one-to-one correspondence with a single domain
  • the NFV-DO includes a VNFO (Virtualized Network Function Orchestrate);
  • the VNFO is configured to: manage any one or more of the following functions in a single domain: a network service instance, a network service life cycle, a VNFM instantiation, an instantiation of a VNF, a life cycle of a VNF, and the like.
  • the NFV-DO may further include a single domain RO (Resource Orchestrator), and the RO may or may not exist as needed.
  • RO Resource Orchestrator
  • the RO is set to: perform one or more of the following processes in the single domain: VNF instance and resource association, resource authentication and management, resource orchestration policy management, resource monitoring, and the like;
  • the NFV-DO may also be absent; when the NFV-DO is absent, it is compatible with the NFV system in the relevant standard.
  • the system further includes NFVO;
  • the NFVO includes an SO (Service Orchestrate) and a Cross-Domain Resource Orchestor (CDRO);
  • SO Service Orchestrate
  • CDRO Cross-Domain Resource Orchestor
  • the SO is set to: perform one or more of the following processes across domains (multi-product or multi-admin domain, etc.): network service orchestration, management of network service instances, network service lifecycle management, network services, and VNF instances. Policy management, etc., the SO interacts with one or more VNFOs that are docked, and interacts with the OSS/BSS;
  • the CDRO is set to: perform the following one of cross-domain (multi-product or multi-admin domain, etc.) or Multiple processing: resource authentication and management, resource orchestration policy management, resource monitoring, etc., the CDRO interacts with one or more NFV-DOs that are docked, and/or with multiple VIMs.
  • the resource request in the domain may be forwarded to the CDRO of the NFVO through the RO, and the RO functions as a forwarding channel; and the RO and the multiple VIMs may also interact.
  • the RO and the CDRO do not interact; the RO can interact with the CDRO only when there is a cross-domain resource request (such as insufficient resources in the local domain), otherwise the RO only interacts with multiple VIMs.
  • the resource request is processed by CDRO of NFVO. In the absence of NFVO, the RO must exist.
  • the system can be applied to a four-layer framework: a network service layer, a domain layer, a virtual resource layer, and a physical layer.
  • a network service layer When applied in a single domain, it can also be reduced to a three-tier framework: domain layer, virtual resource layer, and physical layer.
  • NFVO belongs to the network service layer and can include SO and CDRO;
  • NFV-DO, VNFM and VNF entities belong to the domain layer, and NFV-DO may include VNFO and RO;
  • the virtual resource layer may include multiple VIMs and computing resource pools, network resource pools, and storage resource pools, and is responsible for processing virtual resources, such as virtual machine creation, deletion, migration, and the like;
  • the physical layer may include infrastructure such as servers, storage devices, and network devices.
  • the implementation method of the NFV system of the first embodiment is as shown in FIG. 5, and includes the following steps:
  • Step S501 setting up a cloud computing infrastructure hardware environment, including a computing facility, a storage facility, a network facility, and the like;
  • Step S502 installing and configuring a virtualization infrastructure manager (VIM);
  • VIP virtualization infrastructure manager
  • Step S503 determining whether a single domain orchestration is required, that is, determining whether a network function virtualization single domain orchestrator (NFV-DO) is required;
  • NFV-DO network function virtualization single domain orchestrator
  • step S504 If a single domain orchestration is required, proceed to step S504, if not, proceed to step S507;
  • Step S504 installing and configuring a virtualized network function orchestrator (VNFO) for each single domain;
  • VNFO virtualized network function orchestrator
  • Step S505 Determine, for each single domain, whether a single domain resource scheduling is required
  • step S506 If a single domain resource arrangement is required, proceed to step S506, if not, proceed to step S507;
  • Step S506 installing and configuring a single domain RO
  • Step S507 determining whether cross-domain orchestration is required
  • step S508 If cross-domain orchestration is required, proceed to step S508, and if not, end the process;
  • Step S508 installing and configuring an inter-domain network function virtualization orchestrator (NFVO);
  • NFVO inter-domain network function virtualization orchestrator
  • Step S509 determining whether cross-domain independent management is required
  • step S510 is performed, and if not, the process is ended;
  • Step S510 installing and configuring a cross-domain independent virtualized network function manager (VNFM); ending the process.
  • VNFM virtualized network function manager
  • FIG. 6 is a schematic diagram of an implementation of a networkless service layer in the NFV domain according to an embodiment of the present invention. At this time, it is mainly applied in a single-domain scenario to complete single-domain self-operation and maintenance. For example: core network product domain, or a single domain such as the administrative domain east zone. At this time, VNFO is responsible for the network service orchestration management and lifecycle management of the domain, and the resource scheduling is completed by RO.
  • the implementation steps include the following steps:
  • Step 11 Set up a cloud computing infrastructure hardware environment, including computing facilities, storage facilities, network facilities, and the like;
  • Step 12. Install and configure VIM.
  • Step 13 Determine whether a single domain orchestration is required (ie, whether NFV-DO is required); if a single domain orchestration is required, install and configure VNFO for each single domain;
  • Step 14 For each single domain, determine whether single domain resource scheduling is required; if single domain resource scheduling is required, install and configure a single domain RO.
  • FIG. 7 is a schematic diagram of an embodiment of a network service layer in the NFV field according to an embodiment of the present invention.
  • the inter-domain network service and resource orchestration are completed in NFVO, and the single-domain network service and resource scheduling are delivered to the single-domain NFV-DO.
  • the resource arrangement in the NFV-DO directly interacts with one or more VIMs by the RO.
  • the RO completes the logical processing of the domain resource arrangement, if cross-domain resource orchestration is involved.
  • the NFVO's CDRO interacts with one or more VIMs.
  • the implementation steps include the following steps:
  • Step 21 Build a cloud computing infrastructure hardware environment, including a computing facility, a storage facility, a network facility, and the like;
  • Step 22 Install and configure the VIM.
  • Step 23 Determine whether a single domain orchestration is required (ie, whether NFV-DO is required); if a single domain orchestration is required, install and configure VNFO for each single domain;
  • Step 24 Determine, for each single domain, whether single domain resource scheduling is required; if single domain resource scheduling is required, install and configure a single domain RO;
  • Step 25 Determine whether cross-domain orchestration is required; if cross-domain orchestration is required, install and configure cross-domain NFVO.
  • FIG. 8 is a schematic diagram of an embodiment of a network service layer, a domain layer, and an RO forwarding channel in the NFV field according to an embodiment of the present invention.
  • the inter-domain network service and resource orchestration are completed in NFVO, and the single-domain network service and resource scheduling are delivered to the single-domain NFV-DO.
  • the resource arrangement in the NFV-DO is completed by the RO forwarding CDRO, and the RO does not do
  • the logical processing of resource orchestration or simple logical processing, NFVO's CDRO interacts with one or more VIMs to complete resource orchestration.
  • the implementation steps include the following steps:
  • Step 31 Build a cloud computing infrastructure hardware environment, including a computing facility, a storage facility, a network facility, and the like;
  • Step 32 Install and configure VIM.
  • Step 33 Determine whether a single domain orchestration is required (ie, whether NFV-DO is required); if a single domain orchestration is required, install and configure VNFO for each single domain;
  • Step 34 Determine, for each single domain, whether a single domain resource scheduling is required.
  • the single domain resource scheduling is not required, but the single domain RO is still installed and configured as a channel docking CDRO.
  • Step 35 Determine whether cross-domain orchestration is required; if cross-domain orchestration is required, install and configure cross Domain NFVO.
  • FIG. 9 is a schematic diagram of an embodiment of a network service layer, a domain layer, and no RO in the NFV field according to an embodiment of the present invention.
  • the development of resource management orchestration has a trend of concentration. This scenario may exist in the early single domain, and the implementation of cross-domain orchestration in the later stage, while requiring centralized resource management orchestration scenarios.
  • the inter-domain network service and resource orchestration are completed in NFVO, and the single-domain network service and resource scheduling are delivered to the single-domain NFV-DO.
  • the resource arrangement in NFV-DO directly interacts with CDRO, and the NFVO CDRO interaction.
  • One or more VIMs complete resource orchestration.
  • the implementation steps include the following steps:
  • Step 41 Build a cloud computing infrastructure hardware environment, including a computing facility, a storage facility, a network facility, and the like;
  • Step 42 install and configure the VIM
  • Step 43 Determine whether a single domain orchestration is required (ie, whether NFV-DO is required); if a single domain orchestration is required, install and configure VNFO for each single domain;
  • Step 44 Determine, for each single domain, whether a single domain resource scheduling is required; in this implementation example, the result of the determination is that no single domain resource scheduling is required;
  • Step 45 Determine whether cross-domain orchestration is required; if cross-domain orchestration is required, install and configure cross-domain NFVO.
  • FIG. 10 is a schematic diagram of an embodiment of a network service layer and a domain-free layer in the NFV field according to an embodiment of the present invention. At this point all network services and resource orchestration are completed in NFVO, and SO interacts with the independent VNFM.
  • the implementation steps include the following steps:
  • Step 51 Build a cloud computing infrastructure hardware environment, including a computing facility, a storage facility, a network facility, and the like;
  • Step 52 installing and configuring the VIM
  • Step 53 Determine whether a single domain orchestration is required (ie, whether NFV-DO is required); In the example, the result of the judgment is that no single domain arrangement is required;
  • Step 54 Determine whether cross-domain orchestration is required; if cross-domain orchestration is required, install and configure cross-domain NFVO;
  • Step 55 Determine whether a cross-domain independent VNFM is required. If a cross-domain independent VNFM is required, install and configure a cross-domain independent VNFM.
  • FIG. 11 is a schematic diagram of an embodiment of a network service layer, a domain layer, and a cross-domain VNFM in the NFV field according to an embodiment of the present invention.
  • the inter-domain network service and resource orchestration are completed in NFVO, and the single-domain network service and resource scheduling are delivered to the single-domain NFV-DO.
  • the resource arrangement in the NFV-DO directly interacts with one or more VIMs by the RO.
  • Completion, if cross-domain resource orchestration is involved, is done by NFVO's CDRO interaction with one or more VIMs.
  • the cross-domain service orchestration is completed by the interaction between SO and VNFM, and the resource application is completed by VNFM and CDRO.
  • the implementation steps include the following steps:
  • Step 61 Build a cloud computing infrastructure hardware environment, including a computing facility, a storage facility, a network facility, and the like;
  • Step 62 installing and configuring the VIM
  • Step 63 Determine whether a single domain orchestration is required (that is, whether NFV-DO is required); if a single domain orchestration is required, install and configure VNFO for each single domain;
  • Step 64 Determine, for each single domain, whether single domain resource scheduling is required; if single domain resource scheduling is required, install and configure a single domain RO;
  • Step 65 Determine whether cross-domain orchestration is required; if cross-domain orchestration is required, install and configure cross-domain NFVO;
  • Step 66 Determine whether a cross-domain independent VNFM is required. If a cross-domain independent VNFM is required, install and configure a cross-domain independent VNFM.
  • This embodiment provides a network service instantiation method applied to the NFV system, as shown in FIG. 12, including the following steps:
  • Step S1201 After receiving the VNF instantiation request, the VNFO of the single domain sends a resource reservation request.
  • Step S1202 After receiving the resource reservation information indicating that the resource reservation application is successful, the VNFO initiates a VNF instantiation request to the VNFM in the single domain;
  • Step S1203 The VNFM initiates a resource instantiation request to the VIM according to the resource reservation information.
  • the sending resource reservation application includes:
  • the VNFO determines that the single domain has an RO
  • the VNFO sends a resource reservation application to the RO
  • the RO determines whether the RO is a channel, and if it is a channel, the RO sends the resource reservation request to the CDRO; if not, the RO sends a resource reservation request to the VIM;
  • the VNFO sends a resource reservation request to the CDRO; the CDRO initiates a resource reservation request to the VIM.
  • the method further includes:
  • the CDRO receives the resource reservation information of the VIM feedback, and feeds back to the VNFO that sends the resource reservation application.
  • the method before the VNFO of the single domain receives the VNF instantiation request, the method further includes:
  • the SO receives the network service instantiation request; determines the home domain of the VNF instance in the service; if it belongs to the single domain, delivers the VNF instantiation request to the VNFO of the single domain to which the VNF instance belongs; if it is a cross-domain VNF, The cross-domain VNF instantiation request is delivered to the cross-domain independent VNFM.
  • the method further includes:
  • a cross-domain independent VNFM initiates a resource reservation application to the CDRO
  • the CDRO initiates a resource reservation request to the VIM, and receives resource reservation information fed back by the VIM and sends the resource reservation information to the inter-domain independent VNFM;
  • the cross-domain independent VNFM initiates a resource instantiation request to the VIM according to the resource reservation information.
  • FIG. 13 An example of this embodiment is shown in FIG. 13 and includes the following steps:
  • Step S1301 Initiating a network service instantiation request
  • Step S1302 the service orchestrator (SO) determines the home domain of the VNF instance in the service; if it belongs to a single domain, proceed to step S1303; if it is a cross-domain VNF, proceed to step S1311;
  • Step S1303 The SO sends the VNF instantiation request to the virtualized network function orchestrator (VNFO) corresponding to the single domain;
  • VNFO virtualized network function orchestrator
  • Step S1304 In this example, the single domain has a resource orchestrator (RO), and the VNFO sends a resource reservation request to the RO. If there is no RO in other embodiments, the VNFO sends the resource reservation request to the cross-domain resource arrangement.
  • RO resource orchestrator
  • CDRO Device
  • Step S1305 RO determines whether it is a channel; if it is a channel, proceed to step S1306; if it is not a channel, proceed to step S1307;
  • Step S1306 the RO sends a resource reservation request to the CDRO, and proceeds to step S1313;
  • Step S1307 The RO sends the resource reservation request to the virtualization infrastructure manager (VIM);
  • Step S1308 The RO receives the resource reservation information fed back by the VIM and sends the information to the VNFO.
  • Step S1309 After receiving the resource reservation information indicating that the resource reservation application is successful, the VNFO initiates a VNF instantiation request to the virtualized network function manager (VNFM).
  • VNFM virtualized network function manager
  • Step S1310 The VNFM initiates a resource instantiation request to the VIM according to the resource reservation information.
  • Step S1311 The SO sends a cross-domain VNF instantiation request to the inter-domain independent VNFM.
  • Step S1312 A cross-domain independent VNFM initiates a resource reservation application to the CDRO;
  • Step S1313 The CDRO initiates a resource reservation application to the VIM.
  • Step S1314 The CDRO receives the resource reservation information fed back by the VIM, and sends the resource reservation information fed back by the VIM to the inter-domain independent VNFM.
  • Step S1315 The inter-domain independent VNFM initiates a resource instantiation request to the VIM according to the resource reservation information.
  • an embodiment of the present invention further provides a computer readable storage medium storing computer executable instructions, where the computer executable instructions are implemented to implement the network service instantiation method.
  • each module/unit in the above embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, executing a program stored in the memory by a processor. / instruction to achieve its corresponding function.
  • This application is not limited to any specific combination of hardware and software.
  • the embodiment of the invention provides a network function virtualization system and a network service instantiation method, which can meet the requirements of the phased evolution of the current NFV system implementation and the requirements of multinational, cross-regional, multi-vendor service and multi-layer management.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种网络功能虚拟化***，包括：单域的虚拟化网络功能管理器VNFM、单域的虚拟化网络功能VNF实体、虚拟化基础设施管理器VIM；一个或多个网络功能虚拟化单域编排器NFV-DO，所述NFV-DO与单域一一对应；所述NFV-DO包括：虚拟化网络功能编排器VNFO，设置为：管理所在单域的以下任一项或任几项功能：网络服务实例、网络服务生命周期、VNFM实例化、VNF的实例化、VNF的生命周期。上述方案能满足目前NFV***实施的分阶段演进要求和跨国、跨区域、多厂商提供服务及多层管理的要求。

Description

一种网络功能虚拟化***及网络服务实例化方法 技术领域
本申请涉及但不限于网络功能虚拟化领域，尤其涉及一种网络功能虚拟化***及网络服务实例化方法。
背景技术
网络运营商的网络是通过大型的不断增长的专属硬件设备来部署。一项新网络服务的推出，通常需要另一种变体，而现在也越来越难找到空间和动力；除此之外，能耗在增加，资本投入存在挑战，又缺少必要的技能来设计、整合和操作日趋复杂的硬件设备。
借助NFV(Network Function Virtualization，网络功能虚拟化)技术，网络运营商将在如何建立自己的网络，并实施新的服务上发生翻天覆地的变化。通过虚拟化技术，运营商可以提供更快更好的网络服务，帮助运营商提升竞争力。
图1是ETSI(European Telecommunications Standards Institute，欧洲电信标准化协会)在第一阶段定义的NFV***，如图1所示，右边点划线围成的框中为NFV MANO(Management and Orchestration，管理和编排)，包括NFVO(Network Function Virtualization Orchestrator，网络功能虚拟化编排器)、与NFVO连接的NS(Network Service，网络服务)Catalogue(目录)、VNF(Virtualized Network Function，虚拟化网络功能)Catalogue、NFV Instances(实例)、NFVI(Network Function Virtualization Infrastructure，网络功能虚拟化基础设施)Resources(资源)、VNFM(Virtualized Network Function Manager，虚拟化网络功能管理器)、与VNFM以及NFVO连接的VIM(Virtualized Infrastructure Manager，虚拟化基础设施管理器)；其中，VNFM还与VNF Catalogue连接。
其中，NFVO与VNFM及VIM之间、VNFM与VIM之间设置有Main NFV reference points(主要的网络功能虚拟化参考点)，图1里以实线上的短垂直 线表示，分别为图1里的Or-Vnfm、Or-Vi、Vi-Vnfm；NFVO与NS Catalogue、VNF Catalogue、NFV Instances、NFVI Resources之间、VNFM与VNF Catalogue之间设置有Other NFV reference points(其他的网络功能虚拟化参考点)，图1里以虚线上的短垂直线表示。
另外，NFVO与OSS(Operation support system，运营支撑***)/BSS(Business support system，业务支撑***)之间、VNFM和EM(Element Manage，网络管理)/VNF之间、VIM和NFVI(Network Function Virtualization Infrastructure，网络功能虚拟化基础设施)之间也设置有Main NFV reference points，分别为图1里的Os-Ma-nfvo、Ve-Vnfm-em、Ve-Vnfm-vnf、Nf-Vi；另外，OSS/BSS与EM、NFVI之间、EM与VNF之间设置有Other NFV reference points；VNF和NFVI之间设置有Execution reference points(执行参考点)：Vn-Nf，图1中以两端有原点的实线上的短垂直线表示。
图2是第二阶段定义的草案，做了资源和服务编排管理的分离，取消了图1中的NFV MANO；将NFVO划分为NSO(Network Service Orchestrator，网络服务编排器)和CDRO(Cross-domain Resource Orchestrator，跨域资源编排器)两部分，将EM更换为ENMS(Network Manage System，网络管理***)。将OSS/BSS、ENMS、VNF、NS Catalogue、VNF Catalogue、VNFM以及NSO划分到TENANT DOMAIN(出租域)；将CDRO、NFV Instances、NFVI Resources、VIM和NFVI划分到NFVINFRASTRUCTURE DOMAIN(基础设施域)。
其中，NSO和VNFM、OSS/BSS之间、VNFM和VIM、ENMS、VNF之间所设置的Main NFV reference points分别为图2里的：Nfvo-Vnfm、Os-Nfvo、Vnfm-Vi、VeEn-Vnfm、VeNf-Vnfm；CDRO和VIM之间、VIM和NFVI之间所设置的Main NFV reference points分别为图2里的：Nfvo-Vi、Nf-Vi；VNF和NFVI之间设置的Execution reference points为Vn-Nf。
但是，目前的方案未考虑到***实施的阶段演进及跨国、跨区域、多厂商提供服务等多域复杂运营环境。NFV实施过程可能首先实施一个单域NFV，后续再扩展到全域；也可能是先在某个管理域实施，然后再扩展到全管理域的阶段演进实施。此时，单个服务编排难以满足要求。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例公开一种NFV***及网络服务实例化方法，能满足目前NFV***实施的分阶段演进要求和跨国、跨区域、多厂商提供服务及多层管理的要求。
本发明实施例提供一种网络功能虚拟化(NFV)***，包括：
单域的虚拟化网络功能管理器(VNFM)、单域的虚拟化网络功能(VNF)实体、虚拟化基础设施管理器(VIM)；
一个或多个网络功能虚拟化单域编排器(NFV-DO)，所述NFV-DO与单域一一对应；
所述NFV-DO包括：虚拟化网络功能编排器(VNFO)，设置为：管理所在单域的以下任一项或多项功能：网络服务实例、网络服务生命周期、VNFM实例化、VNF的实例化、VNF的生命周期。
可选地，所述NFV-DO还包括：
单域的资源编排器(RO)，设置为：进行所在单域的以下任一项或多项处理：VNF实例与资源关联、资源鉴权与管理、资源编排策略管理、资源监控。
可选地，所述NFV***还包括：
网络功能虚拟化编排器(NFVO)；
所述NFVO包括服务编排器(SO)和跨域资源编排器(CDRO)；
所述SO和对接的一个或多个所述VNFO进行交互，以及和运营支撑***(OSS)或业务支撑***(BSS)交互，设置为：进行跨域的以下任一项或多项处理：网络服务编排、网络服务实例的管理、网络服务生命周期管理、网络服务和VNF实例的策略管理；
所述CDRO与对接的一个或多个NFV-DO、和/或与多个VIM进行交互， 设置为：进行跨域的以下任一项或多项处理：资源鉴权与管理、资源编排策略管理、资源监控。
可选地，
所述NFVO属于网络服务层；所述NFV-DO、VNFM及VNF实体属于领域层；所述VIM属于虚拟资源层；
所述***还包括：属于虚拟资源层的计算资源池、网络资源池、存储资源池；以及属于物理层的基础设施。
可选地，
当所述***还包括NFVO且所述NFV-DO还包括RO时，所述RO设置为：将所在单域中的资源申请转发到所述CDRO，或发送给VIM；
当所述***不包括NFVO时，所述NFV-DO包括RO，所述RO设置为：将所在单域中的资源申请发送给VIM；
当所述NFV-DO不包括RO时，单域的资源申请由所述CDRO处理。
本发明实施例还提供一种应用于上述的NFV***的网络服务实例化方法，包括：
单域的虚拟化网络功能编排器(VNFO)收到虚拟化网络功能(VNF)实例化请求后，发送资源预留申请；
所述VNFO收到表示资源预留申请成功的资源预留信息后，向所在单域的虚拟化网络功能管理器(VNFM)发起VNF实例化请求；
所述VNFM根据所述资源预留信息向虚拟化基础设施管理器(VIM)发起资源实例化请求。
可选地，所述发送资源预留申请包括：
所述VNFO判断本单域有资源编排器(RO)时，所述VNFO发送资源预留申请给RO；
所述RO判断本RO是否为通道，如果是通道，则所述RO将所述资源预留申请发送给跨域资源编排器(CDRO)；如果不是通道，则所述RO将资源预留申请发送给VIM；
如果没有RO，则所述VNFO发送资源预留申请给CDRO；所述CDRO向VIM发起资源预留申请。
可选地，所述发送资源预留申请后，所述方法还包括：
所述RO从VIM接收资源预留信息并发送给本单域的VNFO；
或者，
所述CDRO接收VIM反馈的资源预留信息，并反馈给发送资源预留申请的VNFO。
可选地，单域的VNFO收到VNF实例化请求前，所述方法还包括：
服务编排器(SO)接收网络服务实例化请求；判断服务中VNF实例的归属域；如果是归属于单域，则将VNF实例化请求下发到VNF实例所归属的单域的VNFO；如果是跨域VNF，则下发跨域VNF实例化请求给跨域独立VNFM。
可选地，所述下发跨域VNF实例化请求给跨域独立VNFM后，所述方法还包括：
跨域独立VNFM向CDRO发起资源预留申请；
所述CDRO向VIM发起资源预留申请，接收VIM反馈的资源预留信息并发送给所述跨域独立VNFM；
所述跨域独立VNFM根据资源预留信息向VIM发起资源实例化请求。
此外，本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述网络服务实例化方法。
本发明实施例能满足目前NFV***实施的分阶段演进要求和跨国、跨区域、多厂商提供服务及多层管理的要求。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是ETSI标准组织第一阶段定义的NFV***图；
图2是ETSI标准组织第二阶段定义的NFV***草案图；
图3是实施例一的NFV***的示意图；
图4是实施例一的NFV***的层次示意图；
图5是实施例一的NFV***的实施方法的流程图；
图6是实施示例1的NFV领域无网络服务层的实施方案示意图；
图7是实施示例2的NFV领域有网络服务层的实施方案示意图；
图8是实施示例3的NFV领域有网络服务层、领域层、RO转发通道的实施方案示意图；
图9是实施示例4的NFV领域有网络服务层、领域层，无RO的实施方案示意图；
图10是实施示例5的NFV领域有网络服务层，无领域层的实施方案示意图；
图11是实施示例6的NFV领域有网络服务层、有领域层、有跨域VNFM的实施方案示意图；
图12是实施例二的网络服务实例化的流程示意图；
图13是实施例二的示例示意图。
本发明的实施方式
下面将结合附图及实施例对本申请的技术方案进行更详细的说明。
需要说明的是，如果不冲突，本发明实施例以及实施例中的各个特征可以相互结合，均在本申请的保护范围之内。另外，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的 步骤。
实施例一
本实施例提供一种NFV***，如图3所示，包括：
NFV-DO(Network Function Virtualization Domain Orchestrate，网络功能虚拟化单域编排器)、单域的虚拟化网络功能管理器(VNFM)、单域的虚拟化网络功能(VNF)实体、虚拟化基础设施管理器(VIM)等；
所述VNFM设置为：管理所述NFV实体；
所述NFV-DO可以有一个或多个，与单域一一对应；
所述NFV-DO包括VNFO(Virtualized Network Function Orchestrate，虚拟化网络功能编排器)；
所述VNFO设置为：管理所在单域的以下任一项或多项功能：网络服务实例、网络服务生命周期、VNFM实例化、VNF的实例化、VNF的生命周期等。
可选地，所述NFV-DO还可以包括单域的RO(Resource Orchestrator，资源编排器)，RO根据需要可以存在也可以不存在。
所述RO设置为：进行所在单域的以下任一项或多项处理：VNF实例与资源关联、资源鉴权与管理、资源编排策略管理、资源监控等；
可选地，所述NFV-DO也可以不存在；NFV-DO不存在时可兼容相关标准中的NFV***。
可选地，所述***还包括NFVO；
其中，所述NFVO包括SO(Service Orchestrate，服务编排器)和跨域资源编排器(CDRO)；
所述SO设置为：进行跨域(多产品或多管理域等)的以下任一项或多项处理：网络服务编排、网络服务实例的管理、网络服务生命周期管理、网络服务和VNF实例的策略管理等，所述SO和对接的一个或多个VNFO进行交互，以及和OSS/BSS交互；
所述CDRO设置为：进行跨域(多产品或多管理域等)的以下任一项或 多项处理：资源鉴权与管理、资源编排策略管理、资源监控等，所述CDRO与对接的一个或多个NFV-DO、和/或与多个VIM进行交互。
可选地，在有NFVO时，当域中存在RO时，所述域中的资源申请可以通过RO转发到NFVO的CDRO，此时RO起转发通道作用；也可以通过RO和多个VIM交互，此时RO和CDRO不交互；也可以只有存在跨域资源申请(如本域资源不足等)时，RO才和CDRO交互，否则RO只和多个VIM交互。当域中不存在RO时，资源申请通过NFVO的CDRO处理。在没有NFVO时，RO必须存在。
可选地，该***可以应用于四层框架上：网络服务层、领域层、虚拟资源层、物理层。当在单域应用时，也可以简化为三层框架：领域层、虚拟资源层、物理层。
如图4所示，NFVO属于网络服务层，可以包括SO和CDRO；
NFV-DO、VNFM及VNF实体属于领域层，NFV-DO可以包括VNFO和RO；
虚拟资源层可以包括多个VIM和计算资源池、网络资源池、存储资源池，负责实际处理虚拟资源的处理，如虚机创建、删除、迁移等；
物理层可以包括服务器、存储设备、网络设备等基础设施。
实施例一的NFV***的实施方法如图5所示，包括如下步骤：
步骤S501、搭建云计算基础设施硬件环境，包括计算设施、存储设施、网络设施等；
步骤S502、安装和配置虚拟化基础设施管理器(VIM)；
步骤S503、判断是否需要单域编排，即判断是否需要网络功能虚拟化单域编排器(NFV-DO)；
如果需要单域编排，则进行步骤S504，如果不需要则进行步骤S507；
步骤S504、针对每个单域，安装和配置虚拟化网络功能编排器(VNFO)；
步骤S505、针对每个单域，判断是否需要单域资源编排；
如果需要单域资源编排，则进行步骤S506，如果不需要则进行步骤S507；
步骤S506、安装和配置单域RO；
步骤S507、判断是否需要跨域编排；
如果需要跨域编排，则进行步骤S508，不需要则结束流程；
步骤S508、安装和配置跨域网络功能虚拟化编排器(NFVO)；
步骤S509、判断是否需要跨域独立管理；
如果需要跨域独立管理，则进行步骤S510，不需要则结束流程；
步骤S510、安装和配置跨域独立虚拟化网络功能管理器(VNFM)；结束流程。
实施示例1：
图6是本发明实施例在NFV领域无网络服务层的实施方案的示意图。此时主要在单域场景下应用，完成单域自运维。例如：核心网产品域，或者某个管理域东区等单域。此时VNFO负责本域的网络服务编排管理、生命周期管理等，资源编排通过RO完成。实施步骤包括如下步骤：
步骤11、搭建云计算基础设施硬件环境，包括计算设施、存储设施、网络设施等；
步骤12、安装和配置VIM；
步骤13、判断是否需要单域编排(即：是否需要NFV-DO)；如果需要单域编排，则针对每个单域，安装和配置VNFO；
步骤14、针对每个单域，判断是否需要单域资源编排；如果需要单域资源编排，则安装和配置单域RO。
实施示例2：
图7是本发明实施例在NFV领域有网络服务层的实施方案的示意图。此时跨域网络服务和资源编排在NFVO完成，单域的网络服务和资源编排下发到单域的NFV-DO完成，此时NFV-DO内的资源编排由RO直接交互一个或多个VIM完成，RO完成本域资源编排的逻辑处理，如果涉及跨域资源编排 则由NFVO的CDRO交互一个或多个VIM完成。实施步骤包括如下的步骤：
步骤21、搭建云计算基础设施硬件环境，包括计算设施、存储设施、网络设施等；
步骤22、安装和配置VIM；
步骤23、判断是否需要单域编排(即：是否需要NFV-DO)；如果需要单域编排，则针对每个单域，安装和配置VNFO；
步骤24、针对每个单域，判断是否需要单域资源编排；如果需要单域资源编排，则安装和配置单域RO；
步骤25、判断是否需要跨域编排；如果需要跨域编排，则安装和配置跨域NFVO。
实施示例3：
图8是本发明实施例在NFV领域有网络服务层、领域层、RO转发通道的实施方案的示意图。此时跨域网络服务和资源编排在NFVO完成，单域的网络服务和资源编排下发到单域的NFV-DO完成，此时NFV-DO内的资源编排由RO转发CDRO完成，RO不做资源编排的逻辑处理或仅简单逻辑处理，NFVO的CDRO交互一个或多个VIM完成资源编排。实施步骤包括如下的步骤：
步骤31、搭建云计算基础设施硬件环境，包括计算设施、存储设施、网络设施等；
步骤32、安装和配置VIM；
步骤33、判断是否需要单域编排(即：是否需要NFV-DO)；如果需要单域编排，则针对每个单域，安装和配置VNFO；
步骤34、针对每个单域，判断是否需要单域资源编排；本实施示例中判断结果为不需要单域资源编排，但仍安装和配置单域RO作为通道对接CDRO；
步骤35、判断是否需要跨域编排；如果需要跨域编排，则安装和配置跨 域NFVO。
实施示例4：
图9是本发明实施例在NFV领域有网络服务层、领域层，无RO的实施方案的示意图。资源管理编排的发展有集中化的趋势，此场景可能存在于早期单域，后期实施跨域编排，同时要求集中化资源管理编排的场景。此时跨域网络服务和资源编排在NFVO完成，单域的网络服务和资源编排下发到单域的NFV-DO完成，此时NFV-DO内的资源编排直接交互CDRO完成，NFVO的CDRO交互一个或多个VIM完成资源编排。实施步骤包括如下的步骤：
步骤41、搭建云计算基础设施硬件环境，包括计算设施、存储设施、网络设施等；
步骤42、安装和配置VIM；
步骤43、判断是否需要单域编排(即：是否需要NFV-DO)；如果需要单域编排，则针对每个单域，安装和配置VNFO；
步骤44、针对每个单域，判断是否需要单域资源编排；本实施示例中判断结果为不需要单域资源编排；
步骤45、判断是否需要跨域编排；如果需要跨域编排，则安装和配置跨域NFVO。
实施示例5：
图10是本发明实施例在NFV领域有网络服务层，无领域层的实施方案的示意图。此时所有的网络服务和资源编排都在NFVO完成，SO和独立VNFM交互。实施步骤包括如下的步骤：
步骤51、搭建云计算基础设施硬件环境，包括计算设施、存储设施、网络设施等；
步骤52、安装和配置VIM；
步骤53、判断是否需要单域编排(即：是否需要NFV-DO)；本实施示 例中判断结果为不需要单域编排；
步骤54、判断是否需要跨域编排；如果需要跨域编排，则安装和配置跨域NFVO；
步骤55、判断是否需要跨域独立VNFM；如果需要跨域独立VNFM，则安装和配置跨域独立VNFM。
实施示例6：
图11是本发明实施例在NFV领域有网络服务层、有领域层、有跨域VNFM的实施方案的示意图。此时跨域网络服务和资源编排在NFVO完成，单域的网络服务和资源编排下发到单域的NFV-DO完成，此时NFV-DO内的资源编排由RO直接交互一个或多个VIM完成，如果涉及跨域资源编排则由NFVO的CDRO交互一个或多个VIM完成。跨域的服务编排由SO和VNFM交互完成，资源申请等由VNFM和CDRO交互完成。实施步骤包括如下的步骤：
步骤61、搭建云计算基础设施硬件环境，包括计算设施、存储设施、网络设施等；
步骤62、安装和配置VIM；
步骤63、判断是否需要单域编排(即：是否需要NFV-DO)；如果需要单域编排，则针对每个单域，安装配置VNFO；
步骤64、针对每个单域，判断是否需要单域资源编排；如果需要单域资源编排，则安装和配置单域RO；
步骤65、判断是否需要跨域编排；如果需要跨域编排，则安装和配置跨域NFVO；
步骤66、判断是否需要跨域独立VNFM；如果需要跨域独立VNFM，则安装和配置跨域独立VNFM。
实施例二
本实施例提供一种应用于上述NFV***的网络服务实例化方法，如图12所示，包括以下步骤：
步骤S1201：单域的VNFO收到VNF实例化请求后，发送资源预留申请；
步骤S1202：所述VNFO收到表示资源预留申请成功的资源预留信息后，向所在单域的VNFM发起VNF实例化请求；
步骤S1203：所述VNFM根据所述资源预留信息向VIM发起资源实例化请求。
可选地，所述发送资源预留申请包括：
所述VNFO判断本单域有RO时，所述VNFO发送资源预留申请给RO；
所述RO判断本RO是否为通道，如果是通道，则所述RO将所述资源预留申请发送给CDRO；如果不是通道，则所述RO将资源预留申请发送给VIM；
如果没有RO，则所述VNFO发送资源预留申请给CDRO；所述CDRO向VIM发起资源预留申请。
可选地，所述发送资源预留申请后，所述方法还包括：
所述RO从VIM接收资源预留信息并发送给本单域的VNFO；
或者，
所述CDRO接收VIM反馈的资源预留信息，并反馈给发送资源预留申请的VNFO。
可选地，所述单域的VNFO收到VNF实例化请求前，所述方法还包括：
SO接收网络服务实例化请求；判断服务中VNF实例的归属域；如果是归属于单域，则将VNF实例化请求下发到VNF实例所归属的单域的VNFO；如果是跨域VNF，则下发跨域VNF实例化请求给跨域独立VNFM。
可选地，所述下发跨域VNF实例化请求给跨域独立VNFM后，所述方法还包括：
跨域独立VNFM向CDRO发起资源预留申请；
所述CDRO向VIM发起资源预留申请，接收VIM反馈的资源预留信息并发送给所述跨域独立VNFM；
所述跨域独立VNFM根据资源预留信息向VIM发起资源实例化请求。
本实施例的一个示例如图13所示，包括以下步骤：
步骤S1301、发起网络服务实例化请求；
步骤S1302、服务编排器(SO)判断服务中VNF实例的归属域；如果是归属于某个单域，则进行步骤S1303；如果是跨域VNF，则进行步骤S1311；
步骤S1303、SO将VNF实例化请求下发到对应单域的虚拟化网络功能编排器(VNFO)；
步骤S1304、本例中，本单域有资源编排器(RO)，VNFO将资源预留申请发给RO；如果在其它实施例中没有RO，则VNFO将资源预留申请发给跨域资源编排器(CDRO)；
步骤S1305、RO判断自身是否为通道；如果是通道，则进行步骤S1306；如果不是通道，则进行步骤S1307；
步骤S1306、RO将资源预留申请发给CDRO，进行步骤S1313；
步骤S1307、RO将资源预留申请发给虚拟化基础设施管理器(VIM)；
步骤S1308、RO接收VIM反馈的资源预留信息并发送给VNFO；
步骤S1309、VNFO收到RO反馈的表示资源预留申请成功的资源预留信息后，向虚拟化网络功能管理器(VNFM)发起VNF实例化请求；
步骤S1310、VNFM根据资源预留信息向VIM发起资源实例化请求；
步骤S1311、SO下发跨域VNF实例化请求给跨域独立VNFM；
步骤S1312、跨域独立VNFM向CDRO发起资源预留申请；
步骤S1313、CDRO向VIM发起资源预留申请；
步骤S1314、CDRO接收VIM反馈的资源预留信息，将VIM反馈的资源预留信息发给跨域独立VNFM；
步骤S1315、跨域独立VNFM根据资源预留信息向VIM发起资源实例化请求。
此外，本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述网络服务实例化方法。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件(例如处理器)完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现。相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，例如通过集成电路来实现其相应功能，也可以采用软件功能模块的形式实现，例如通过处理器执行存储于存储器中的程序/指令来实现其相应功能。本申请不限制于任何特定形式的硬件和软件的结合。
虽然本申请所揭露的实施方式如上，但所述的内容仅为便于理解本申请而采用的实施方式，并非用以限定本申请。任何本申请所属领域内的技术人员，在不脱离本申请所揭露的精神和范围的前提下，可以在实施的形式及细节上进行任何的修改与变化，但本申请的专利保护范围，仍须以所附的权利要求书所界定的范围为准。
工业实用性
本发明实施例提供一种网络功能虚拟化***及网络服务实例化方法，能满足目前NFV***实施的分阶段演进要求和跨国、跨区域、多厂商提供服务及多层管理的要求。

Claims (10)

  1. 一种网络功能虚拟化NFV***，包括：
    单域的虚拟化网络功能管理器VNFM、单域的虚拟化网络功能VNF实体、虚拟化基础设施管理器VIM；
    一个或多个网络功能虚拟化单域编排器NFV-DO，所述NFV-DO与单域一一对应；
    所述NFV-DO包括：虚拟化网络功能编排器VNFO，设置为：管理所在单域的以下任一项或多项功能：网络服务实例、网络服务生命周期、VNFM实例化、VNF的实例化、VNF的生命周期。
  2. 如权利要求1所述的***，其中，所述NFV-DO还包括：
    单域的资源编排器RO，设置为：进行所在单域的以下任一项或多项处理：VNF实例与资源关联、资源鉴权与管理、资源编排策略管理、资源监控。
  3. 如权利要求1所述的***，所述NFV***还包括：
    网络功能虚拟化编排器NFVO；
    所述NFVO包括服务编排器SO和跨域资源编排器CDRO；
    所述SO和对接的一个或多个所述VNFO进行交互，以及和运营支撑***OSS或业务支撑***BSS交互，设置为：进行跨域的以下任一项或多项处理：网络服务编排、网络服务实例的管理、网络服务生命周期管理、网络服务和VNF实例的策略管理；
    所述CDRO与对接的一个或多个NFV-DO、和/或与多个VIM进行交互，设置为：进行跨域的以下任一项或多项处理：资源鉴权与管理、资源编排策略管理、资源监控。
  4. 如权利要求3所述的***，其中，
    所述NFVO属于网络服务层；所述NFV-DO、VNFM及VNF实体属于领域层；所述VIM属于虚拟资源层；
    所述***还包括：属于虚拟资源层的计算资源池、网络资源池、存储资 源池；以及属于物理层的基础设施。
  5. 如权利要求1到4中任一项所述的***，其中，
    当所述***还包括NFVO且所述NFV-DO还包括RO时，所述RO设置为：将所在单域中的资源申请转发到所述CDRO，或发送给VIM；
    当所述***不包括NFVO时，所述NFV-DO包括RO，所述RO设置为：将所在单域中的资源申请发送给VIM；
    当所述NFV-DO不包括RO时，单域的资源申请由所述CDRO处理。
  6. 一种应用于权利要求1～5中任一项所述的网络功能虚拟化NFV***的网络服务实例化方法，包括：
    单域的虚拟化网络功能编排器VNFO收到虚拟化网络功能VNF实例化请求后，发送资源预留申请；
    所述VNFO收到表示资源预留申请成功的资源预留信息后，向所在单域的虚拟化网络功能管理器VNFM发起VNF实例化请求；
    所述VNFM根据所述资源预留信息向虚拟化基础设施管理器VIM发起资源实例化请求。
  7. 如权利要求6所述的方法，其中，所述发送资源预留申请包括：
    所述VNFO判断本单域有资源编排器RO时，所述VNFO发送资源预留申请给RO；
    所述RO判断本RO是否为通道，如果是通道，则所述RO将所述资源预留申请发送给跨域资源编排器CDRO；如果不是通道，则所述RO将资源预留申请发送给VIM；
    如果没有RO，则所述VNFO发送资源预留申请给CDRO；所述CDRO向VIM发起资源预留申请。
  8. 如权利要求7所述的方法，所述发送资源预留申请后，所述方法还包括：
    所述RO从VIM接收资源预留信息并发送给本单域的VNFO；
    或者，
    所述CDRO接收VIM反馈的资源预留信息，并反馈给发送资源预留申请的VNFO。
  9. 如权利要求6所述的方法，所述单域的VNFO收到VNF实例化请求前，所述方法还包括：
    服务编排器SO接收网络服务实例化请求；判断服务中VNF实例的归属域；如果是归属于单域，则将VNF实例化请求下发到VNF实例所归属的单域的VNFO；如果是跨域VNF，则下发跨域VNF实例化请求给跨域独立VNFM。
  10. 如权利要求9所述的方法，所述下发跨域VNF实例化请求给跨域独立VNFM后，所述方法还包括：
    跨域独立VNFM向CDRO发起资源预留申请；
    所述CDRO向VIM发起资源预留申请，接收VIM反馈的资源预留信息并发送给所述跨域独立VNFM；
    所述跨域独立VNFM根据资源预留信息向VIM发起资源实例化请求。
PCT/CN2016/079197 2015-10-14 2016-04-13 一种网络功能虚拟化***及网络服务实例化方法 WO2016180143A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/768,502 US11175955B2 (en) 2015-10-14 2016-04-13 Network function virtualization system and network service instantiation method
EP16791993.5A EP3364606B1 (en) 2015-10-14 2016-04-13 Network function virtualization system and network service instantiation method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510662615.5A CN106603371B (zh) 2015-10-14 2015-10-14 一种网络功能虚拟化***及网络服务实例化方法
CN201510662615.5 2015-10-14

Publications (1)

Publication Number Publication Date
WO2016180143A1 true WO2016180143A1 (zh) 2016-11-17

Family

ID=57248835

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/079197 WO2016180143A1 (zh) 2015-10-14 2016-04-13 一种网络功能虚拟化***及网络服务实例化方法

Country Status (4)

Country Link
US (1) US11175955B2 (zh)
EP (1) EP3364606B1 (zh)
CN (1) CN106603371B (zh)
WO (1) WO2016180143A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3550775A4 (en) * 2016-12-02 2020-06-24 ZTE Corporation METHOD AND DEVICE FOR DETERMINING RESOURCES AND NFVO

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106375101B (zh) * 2015-07-20 2019-08-27 华为技术有限公司 一种生命周期管理方法及装置
CN107294769A (zh) * 2017-05-16 2017-10-24 南京邮电大学 一种基于5g网络的敏捷化云服务管理***及其控制方法
CN109587024B (zh) * 2017-09-29 2020-12-22 华为技术有限公司 一种资源处理的方法以及相关装置
US11405263B2 (en) * 2018-02-02 2022-08-02 Nokia Solutions And Networks Oy Using self-operation cases to identify and resolve issues causing network slice reselection
CN110401554B (zh) * 2018-04-25 2021-11-30 中移(苏州)软件技术有限公司 Vnf纳管的方法、装置、***、电子设备及存储介质
CN109347661B (zh) * 2018-09-25 2021-12-17 中国联合网络通信集团有限公司 消费者vnf的实例化方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015126430A1 (en) * 2014-02-24 2015-08-27 Hewlett-Packard Development Company, L.P. Virtual network function management with deactivated virtual machines
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2467939A1 (en) * 2004-05-20 2005-11-20 Fernando Cuervo Architecture for configuration and management of cross-domain network services
US8832249B2 (en) * 2011-11-30 2014-09-09 At&T Intellectual Property I, L.P. Methods and apparatus to adjust resource allocation in a distributive computing network
US9973375B2 (en) * 2013-04-22 2018-05-15 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions
US9864623B2 (en) * 2013-11-21 2018-01-09 Centurylink Intellectual Property Llc Physical to virtual network transport function abstraction
CN105103507B (zh) * 2014-01-28 2018-01-05 华为技术有限公司 网络功能虚拟化的方法及装置
JP6408602B2 (ja) * 2014-03-24 2018-10-17 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． Ｎｆｖシステムにおけるサービス実装のための方法および通信ユニット
US10880180B2 (en) * 2015-09-16 2020-12-29 Huawei Technologies Co., Ltd. Method and apparatus for data analytics management

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015126430A1 (en) * 2014-02-24 2015-08-27 Hewlett-Packard Development Company, L.P. Virtual network function management with deactivated virtual machines
CN104954220A (zh) * 2014-03-31 2015-09-30 华为技术有限公司 一种虚拟网络业务部署方法和设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3364606A4 *
XUE, HAIQIANG ET AL.: "Network function virtualization and standardization", ZTE TECHNOLOGY JOURNAL, vol. 21, no. 2, 30 April 2015 (2015-04-30), XP009507553, ISSN: 1009-6868 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3550775A4 (en) * 2016-12-02 2020-06-24 ZTE Corporation METHOD AND DEVICE FOR DETERMINING RESOURCES AND NFVO

Also Published As

Publication number Publication date
US11175955B2 (en) 2021-11-16
EP3364606A1 (en) 2018-08-22
US20180307538A1 (en) 2018-10-25
CN106603371A (zh) 2017-04-26
EP3364606B1 (en) 2023-07-26
EP3364606A4 (en) 2019-06-05
CN106603371B (zh) 2020-11-24

Similar Documents

Publication Publication Date Title
WO2016180143A1 (zh) 一种网络功能虚拟化***及网络服务实例化方法
EP3313023B1 (en) Life cycle management method and apparatus
US10367714B2 (en) Apparatus for testing and developing products of network computing based on open-source virtualized cloud
US20190173978A1 (en) Attaching service level agreements to application containers and enabling service assurance
US8683464B2 (en) Efficient virtual machine management
US9348646B1 (en) Reboot-initiated virtual machine instance migration
WO2019184116A1 (zh) 自动搭建Kubernetes主节点的方法、装置、终端设备及可读存储介质
EP3639134B1 (en) Detecting and managing recurring patterns in device and service configuration data
WO2016037479A1 (zh) 虚拟化网络功能vnf优化方法、装置及***
US20130311631A1 (en) Integrated cloud data center management
WO2017041649A1 (zh) 一种应用部署方法及设备
US11182217B2 (en) Multilayered resource scheduling
US20160364252A1 (en) Migrating servers into a secured environment
US10346192B2 (en) Method, apparatus, and system for displaying virtual machine name
Awasthi et al. Openstack-paradigm shift to open source cloud computing & its integration
US10782991B2 (en) Customizable virtual machine retirement in a management platform
US20180335894A1 (en) Messaging and orchestrating platform in a computer network environment
US20140195590A1 (en) Managing a logical client for a virtual machine
US20210160138A1 (en) Dynamic network of supercomputing resources with unified management interface
WO2018039878A1 (zh) 一种虚拟资源的管理方法、装置及***
US10284668B2 (en) Managing a logical client for an application
US9553767B2 (en) Host connectivity templates to configure host of virtual machines
WO2023245440A1 (zh) 私有化空间创建方法、装置、设备及介质
US11221871B2 (en) Enabling a management function on a compute node in response to a user workload ownership level
US20240028416A1 (en) Centralized Management of External Clusters on Managed Kubernetes Platforms

Legal Events

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

Ref document number: 16791993

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15768502

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016791993

Country of ref document: EP