WO2018149272A1 - 基于sla的资源分配方法和nfvo - Google Patents

基于sla的资源分配方法和nfvo Download PDF

Info

Publication number
WO2018149272A1
WO2018149272A1 PCT/CN2018/073681 CN2018073681W WO2018149272A1 WO 2018149272 A1 WO2018149272 A1 WO 2018149272A1 CN 2018073681 W CN2018073681 W CN 2018073681W WO 2018149272 A1 WO2018149272 A1 WO 2018149272A1
Authority
WO
WIPO (PCT)
Prior art keywords
sla
vnf
nfvi
nfvo
resource
Prior art date
Application number
PCT/CN2018/073681
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 EP18754170.1A priority Critical patent/EP3471345B1/en
Publication of WO2018149272A1 publication Critical patent/WO2018149272A1/zh
Priority to US16/273,165 priority patent/US20190173802A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • 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/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • 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
    • 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/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • 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/5003—Managing SLA; Interaction between SLA and QoS
    • 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/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • 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
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
    • 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/82—Miscellaneous aspects
    • H04L47/829—Topology based
    • 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
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • 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
    • G06F2009/45579—I/O management, e.g. providing access to device drivers or storage
    • 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
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation

Definitions

  • the embodiments of the present invention relate to a communication technology, and in particular, to a service level agreement (SLA)-based resource allocation method and a network function virtualization orchestrator (NFVO).
  • SLA service level agreement
  • NFVO network function virtualization orchestrator
  • Network Function Virtualization (NFV) technology reduces the expensive equipment cost of the network by using general-purpose hardware and virtualization technology to carry software processing of many functions.
  • the architecture of the NFV system consists mainly of the following functional components:
  • NFVO responsible for the life cycle management of Network Service (NS), orchestration management resources, real-time monitoring of network function virtualization infrastructure (NFV Infrastructure) resources and operational status information; and virtual network function manager (Virtualised The Network Function Manager (VNFM) is used to implement a global view of the lifecycle management and resources of the Virtualized Network Function (VNF).
  • NS Network Service
  • NFV Infrastructure network function virtualization infrastructure
  • VNFM Virtualised The Network Function Manager
  • VNFM is responsible for VNF lifecycle management, such as initialization of VNF instances, expansion/reduction of VNF instances, termination of VNF instances, and management of VNF operational status information.
  • Virtualized Infrastructure Manager is responsible for infrastructure layer hardware resources, virtualized resource management, monitoring, and fault reporting, and provides virtualized resource pools for upper-layer applications. For example, it is responsible for managing and allocating NFVI resources and monitoring and collecting NFVI operational status information.
  • NFVI resources consisting of hardware resources, virtual resources, and virtualization layers, including all NFVI resource states, available/reserved/allocated NFVI resources. From a VNF perspective, the virtualization layer and hardware resources appear to be an entity that provides the required virtual resources.
  • the VNF is a software implementation of a Network Function (NF) that can run on the NFVI, which is equivalent to the entity of the network node and is expected to be delivered in pure software that is free of hardware dependencies.
  • NF Network Function
  • NFVO when NFVO needs to apply for NFVI virtual resources to VIM in the process of instantiating, expanding, and migrating NS/VNF, NFVO only tells the number of NFVI virtual resources required by VIM, and the number of NFVI virtual resources that VIM needs according to NFVO. The corresponding number of NFVI virtual resources are returned to the NFVI, but the NFVO virtual resources applied by the NFVO may not meet the service quality of the NS/VNF. It may be necessary to apply for the NFVI virtual resources to the VIM multiple times, resulting in a low hit rate of the NFVI virtual resource application.
  • the embodiment of the invention provides an SLA-based resource allocation method and NFVO.
  • the NFVO considers the NFVI SLA parameter, so that the obtained virtual resource satisfies the user requirement and improves the qualified hit rate of the resource application.
  • an embodiment of the present invention provides an SLA-based resource allocation method, including: an NFVO receiving network service instantiation request, where the network service instantiation request includes an identifier of a network service SLA, according to the network service
  • the identifier of the SLA determines an NFVI SLA parameter required to instantiate the network service, and obtains, according to the NFVI SLA parameter, a virtual resource that meets the NFVI SLA parameter requirement from the virtualization infrastructure manager VIM, according to the obtained
  • the virtual resource instantiates the network service.
  • the NFVO considers the NFVI SLA parameter when applying for the virtual resource, so that the obtained virtual resource satisfies the user requirement and improves the qualified hit rate of the resource application.
  • the network service is an NS
  • the network service instantiation request is an NS instantiation request
  • the identifier of the SLA of the network service is an identifier of an NS SLA
  • the NFVO is determined according to an identifier of the SLA of the network service. Determining the NFVI SLA parameters required to instantiate the network service, specifically:
  • the NFVO acquires a network service descriptor NSD of the NS, where the NSD includes information about the NS SLA, a VNF included by the NS, and an association relationship between the NS SLA and the virtual network function VNF SLA;
  • the NFVO acquires a virtual network function descriptor VNFD of the VNF included in the NS, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVO determines an NFVI SLA parameter of the VNF included in the NS based on the identification of the VNF SLA of the VNF included in the NS and the VNFD of the VNF included in the NS.
  • the information about the NS SLA includes an identifier, a keyword, and a specific value of the NS SLA
  • the association relationship between the NS SLA and the VNF SLA includes: an identifier of the VNF SLA of the VNF included in the NS, an NS SLA parameter, and Correlation calculation model of VNF SLA parameters;
  • the VNF SLA information includes an identifier, a keyword, and a specific value of the VNF SLA, and the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier and an associated calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the network service is a virtual network function VNF
  • the network service instantiation request is a VNF instantiation request
  • the identifier of the SLA of the network service is an identifier of a VNF SLA
  • the NFVO is according to the network service.
  • the identifier of the SLA determines the NFVI SLA parameters required to instantiate the network service, specifically:
  • the NFVO acquires a virtual network function descriptor VNFD of the VNF, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVO determines an NFVI SLA parameter of the VNF based on the identification of the VNF SLA and the VNFD.
  • the information of the VNF SLA includes an identifier, a keyword, and a specific value of the VNF SLA
  • the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier, and an association calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the NFVO obtains, according to the NFVI SLA parameter, a virtual resource that meets the NFVI SLA parameter requirement from the virtualization infrastructure manager VIM, specifically:
  • the NFVO sends a first resource request message to the VIM, where the first resource request message includes the NFVI SLA parameter;
  • the NFVO receives the first resource response message sent by the VIM, where the first resource request message includes information of a virtual resource that meets the NFVI SLA parameter requirement.
  • the NFVO obtains, according to the NFVI SLA parameter, a virtual resource that meets the NFVI SLA parameter requirement from the virtualization infrastructure manager VIM, specifically:
  • the NFVO sends a second resource request message to the VIM, where the second resource request message includes information about the virtual resource, and the second resource request message is used to query availability of the virtual resource and schedule the Virtual resource
  • the NFVO receives a second resource response message sent by the VIM.
  • the method further includes:
  • the NFVO groups the SLA parameters of the virtual resources in the NFVI resource pool according to a preset grouping rule
  • the NFVO determines, according to the NFVI SLA parameter, and the SLA parameter information of the NFVI resource pool acquired from the VIM, the virtual resource that meets the requirement of the NFVI SLA parameter from the NFVI resource pool.
  • Information specifically:
  • the NFVO determines a target packet that satisfies the NFVI SLA parameter requirement from each packet based on the NFVI SLA parameter.
  • the preset grouping rule is grouping according to a region of a virtual resource or a cluster of virtual resources.
  • an embodiment of the present invention provides a network function virtualization orchestrator NFVO, including:
  • a receiving module configured to receive a network service instantiation request, where the network service instantiation request includes an identifier of a service level agreement SLA of the network service;
  • a determining module configured to determine, according to the identifier of the SLA of the network service, a network function virtualization infrastructure NFVI SLA parameter required to instantiate the network service;
  • An obtaining module configured to obtain, from the virtualization infrastructure manager VIM, a virtual resource that meets the NFVI SLA parameter requirement according to the NFVI SLA parameter;
  • an instantiation module configured to instantiate the network service according to the obtained virtual resource.
  • the network service is a network service NS
  • the network service instantiation request is an NS instantiation request
  • the identifier of the SLA of the network service is an identifier of the NS SLA
  • NSD network service descriptor of the NS, where the NSD includes information about the NS SLA, a VNF included by the NS, and an association relationship between an NS SLA and a virtual network function VNF SLA;
  • VNFD virtual network function descriptor VNFD of the VNF included in the NS, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVI SLA parameter of the VNF included in the NS is determined based on the identification of the VNF SLA of the VNF included in the NS and the VNFD of the VNF included in the NS.
  • the information about the NS SLA includes an identifier, a keyword, and a specific value of the NS SLA
  • the association relationship between the NS SLA and the VNF SLA includes: an identifier of the VNF SLA of the VNF included in the NS, an NS SLA parameter, and Correlation calculation model of VNF SLA parameters;
  • the VNF SLA information includes an identifier, a keyword, and a specific value of the VNF SLA, and the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier and an associated calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the network service is a virtual network function VNF
  • the network service instantiation request is a VNF instantiation request
  • the identifier of the SLA of the network service is an identifier of the VNF SLA
  • the determining module is specifically configured to:
  • VNFD virtual network function descriptor VNFD of the VNF, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVI SLA parameter of the VNF is determined based on the identification of the VNF SLA and the VNFD.
  • the information of the VNF SLA includes an identifier, a keyword, and a specific value of the VNF SLA
  • the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier, and an association calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the acquiring module is specifically configured to:
  • the acquiring module is specifically configured to:
  • the NFVO further includes a grouping module
  • the receiving module is further configured to receive SLA parameter information of the NFVI resource pool reported by the VIM;
  • the grouping module is configured to group SLA parameters of the virtual resources in the NFVI resource pool according to a preset grouping rule
  • the acquiring module is specifically configured to: determine, according to the NFVI SLA parameter, a target group that meets the NFVI SLA parameter requirement from each group.
  • the preset grouping rule is grouping according to a region of a virtual resource or a cluster of virtual resources.
  • an embodiment of the present invention provides an NFVO, including: a transmitter, a receiver, a memory, and a processor, the memory is configured to store program instructions, the transmitter is configured to send data to other devices, and the receiver is configured to receive Data sent by other devices, the processor is used to invoke program instructions in the memory to perform the following methods:
  • the network service is a network service NS
  • the network service instantiation request is an NS instantiation request
  • the identifier of the SLA of the network service is an identifier of an NS SLA
  • the processor is configured according to the NS SLA.
  • the identifier and the NSD determine a VNF SLA of the VNF included in the NS, specifically:
  • the NSD includes information about the NS SLA, a VNF included by the NS, and an association relationship between an NS SLA and a VNF SLA;
  • VNFD virtual network function descriptor VNFD of the VNF included in the NS, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and an NFVI SLA;
  • the NFVI SLA parameter of the VNF included in the NS is determined based on the identification of the VNF SLA of the VNF included in the NS and the VNFD of the VNF included in the NS.
  • the information about the NS SLA includes an identifier, a keyword, and a specific value of the NS SLA
  • the association relationship between the NS SLA and the VNF SLA includes: an identifier of the VNF SLA of the VNF included in the NS, an NS SLA parameter, and Correlation calculation model of VNF SLA parameters;
  • the VNF SLA information includes an identifier, a keyword, and a specific value of the VNF SLA, and the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier and an associated calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the network service is a VNF
  • the network service instantiation request is a VNF instantiation request
  • the identifier of the SLA of the network service is an identifier of a VNF SLA
  • the processor is configured according to the identifier of the NS SLA and The NSD determines a VNF SLA of the VNF included in the NS, specifically:
  • VNFD virtual network function descriptor VNFD of the VNF, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVI SLA parameter of the VNF is determined based on the identification of the VNF SLA and the VNFD.
  • the information of the VNF SLA includes an identifier, a keyword, and a specific value of the VNF SLA
  • the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier, and an association calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the processor obtains, according to the NFVI SLA parameter, a virtual resource that meets the NFVI SLA parameter requirement from the virtualization infrastructure manager VIM, specifically:
  • the processor obtains, according to the NFVI SLA parameter, a virtual resource that meets the NFVI SLA parameter requirement from the virtualization infrastructure manager VIM, specifically:
  • the processor is further configured to: receive SLA parameter information of the NFVI resource pool reported by the VIM; and group SLA parameters of the virtual resource in the NFVI resource pool according to a preset grouping rule;
  • a target packet that satisfies the NFVI SLA parameter requirement is determined from each packet based on the NFVI SLA parameter.
  • the preset grouping rule is grouping according to a region of a virtual resource or a cluster of virtual resources.
  • the embodiment of the present invention further provides a computer program product, where the computer program product includes a computer program, which can be implemented by the processor or other types of chips to implement the foregoing embodiments provided by the present invention.
  • SLA-based resource allocation method SLA-based resource allocation method.
  • Figure 1 is a schematic diagram of the architecture of an NFV system
  • FIG. 3 is a signaling flowchart of an SLA-based resource allocation method according to Embodiment 2 of the present invention.
  • FIG. 4 is a schematic structural diagram of an NFVO according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic structural diagram of an NFVO according to Embodiment 4 of the present invention.
  • the method of the embodiment of the present invention can be applied to an NFV system, where the NFV system can implement multiple networks, such as a local area network (LAN), an Internet Protocol (IP) network, or an evolved packet core network (Evolved). Packet Core (referred to as EPC) network.
  • LAN local area network
  • IP Internet Protocol
  • EPC evolved packet core network
  • FIG. 1 is a schematic diagram of the architecture of an NFV system.
  • the NFV system may include an NFV Management and Orchestration System (NFV-MANO) 110, NFVI 150, VNF 140, and multiple network element management systems. (Element Management System, EMS) 130, and one or more Operation Support System/Business Support System (OSS/BSS) 120.
  • NFV-MANO NFV Management and Orchestration System
  • EMS Operation Support System/Business Support System
  • OSS/BSS Operation Support System/Business Support System
  • NFV-MANO 110 may include NFVO 111, one or more VNFMs 112, and one or VIM 113;
  • NFVI 150 may include computing hardware 1521, storage hardware 1522, hardware resources layer composed of network hardware 1523, virtualization layer, and virtual computing 1511.
  • a virtual resource layer composed of (for example, a virtual machine), a virtual storage 1512, and a virtual network 1513.
  • the computing hardware 1521 in the hardware resource layer may be a dedicated processor or a general purpose processor for providing processing and computing functions, such as a Central Process Unit (CPU); the storage hardware 1522 is configured to provide storage capabilities.
  • a disk or Network Attached Storage (NAS); network hardware 1523 can be a switch, a router, and/or other network device.
  • CPU Central Process Unit
  • NAS Network Attached Storage
  • the virtualization layer in NFVI 150 is used to abstract the hardware resources of the hardware resource layer, decouple the VNF 140 from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF.
  • the virtual resource layer may include a virtual computing 1511, a virtual storage 1512, and a virtual network 1513.
  • Virtual computing 1511, virtual storage 1512 may be provided to VNF 140 in the form of a virtual machine or other virtual container, such as one or more virtual machines forming a VNF 140.
  • the virtualization layer forms a virtual network 1513 through abstract network hardware 1523.
  • the virtual network 1513 is configured to implement communication between multiple virtual machines, or between other types of virtual containers that carry VNFs.
  • the virtual network can be created by virtual LAN (Vritual LAN, VLAN for short), Virtual Private LAN Service (VPLS), Virtual eXtensible Local Area Network (VxLAN), or general routing. Technology implementation such as Nerwork Virtualization using Generic Routing Encapsulation (NVGRE).
  • NVGRE Generic Routing Encapsulation
  • OSS/BSS 120 is mainly for telecom service operators, providing comprehensive network management and service operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • network management such as fault monitoring, network information collection, etc.
  • billing management billing management
  • customer service management customer service management
  • NFV-MANO 110 can be used to monitor and manage VNF 140 and NFVI 150.
  • the NFVO 111 can communicate with one or more VNFMs 112 to implement resource related requests, send configuration information to the VNFM 112, and collect status information for the VNF 140.
  • NFVO 111 can also communicate with VIM 113 to enable resource allocation, and/or to implement configuration and status information reservation and exchange of virtualized hardware resources.
  • the VNFM 112 can be used to manage one or more VNFs 140, performing various management functions, such as initializing, updating, querying, and/or terminating the VNF 140.
  • the VIM 113 can be used to control and manage the interaction of the VNF 140 and computing hardware 1521, storage hardware 1522, network hardware 1523, virtual computing 1511, virtual storage 1512, and virtual network 1513.
  • VIM 113 can be used to perform resource allocation operations to VNF 140.
  • VNFM 112 and VIM 113 can communicate with one another to exchange virtualized hardware resource configuration and status information.
  • NFVI 150 includes both hardware and software that together create a virtualized environment to deploy, manage, and execute VNF 140.
  • the hardware resource layer and the virtual resource layer are used to provide virtual resources, such as virtual machines and/or other forms of virtual containers, to the VNF 140.
  • VNFM 112 can communicate with VNF 140 and EMS 130 to perform VNF lifecycle management and implement exchange of configuration/status information.
  • the VNF 140 is a virtualization of at least one network function that was previously provided by a physical network device.
  • the VNF 140 may be a virtualized Mobility Management Entity (MME) node for providing all network functions provided by a typical non-virtualized MME device.
  • MME Mobility Management Entity
  • the VNF 140 can be used to implement the functionality of some of the components provided on the non-virtualized MME device.
  • a VNF 140 may be composed of one or more virtual network function components (VNF Components, VNFC for short), which may be virtual machines or other forms of virtual containers.
  • the EMS 130 can be used to manage one or more VNFs 140.
  • the VNFM 112 is used to perform various management functions on the VNF 140, such as initializing, updating, querying, and terminating the VNF 140, while the VIM 113 is used to control and The management VNF 140 interacts with other parts. Therefore, if a VNF 140 is implemented, the VNFM 112 and the VIM 113 must work together. Therefore, the VNFM 112 and the VIM 113 can communicate with each other to exchange virtualized hardware resource configuration and status information, wherein VNFM 112 and VIM 113 establish a communication connection through the interface.
  • FIG. 1 is a flowchart of an SLA-based resource allocation method according to Embodiment 1 of the present invention. As shown in FIG. 1 , the method in this embodiment may include the following steps:
  • the NFVO receives the network service instantiation request, and the network service instantiation request includes an identifier (Idengtity, ID for short) of the service level agreement (SLA) of the network service.
  • Idengtity ID for short
  • SLA service level agreement
  • the network service instantiation request is used to request instantiation of the network service, and the network service instantiation request may be initiated by the operator to the NFVO, or may be initiated by other software or hardware devices to the NFVO.
  • a parameter is added in the network service instantiation request: the ID of the SLA of the network service, and the ID of the SLA of the network service is used to identify the SLA parameter of the network service, and different The SLA parameters of the network service are different.
  • the IDs of the SLAs of different network services are different.
  • SLA is an internationally accepted evaluation standard for telecommunication services.
  • SLAs usually include guarantees of service availability and customer support services, such as circuit availability, network performance, service response time, service provision guarantee, etc., and commitment to service quality, charging standards, and payment standards.
  • the network service related to the embodiment may be an NS or a VNF
  • the network service instantiation request may be an NS instantiation request or a VNF instantiation request
  • the identifier of the network service included in the NS instantiation request is The identifier of the NS SLA
  • the identifier of the SLA of the network service included in the VNF instantiation request is the identifier of the VNF SLA.
  • the NS is a network service composed of multiple VNFs to provide more complex functions. Instantiating the NS is actually instantiating the VNFs included in the NS.
  • Step 102 The NFVO determines, according to the identifier of the SLA of the network service, an NFVI SLA parameter required to instantiate the network service.
  • the NFVO determines the NFVI SLA parameters required to instantiate the network service according to the identifier of the SLA of the network service, specifically: the NFVO acquires the Network Service Descriptor (NSD) of the NS.
  • the NSD includes information about the NS SLA, the VNF included by the NS, and the association between the NS SLA and the VNF SLA. Then, the NFVO determines the VNF SLA of the VNF included in the NS according to the identifier of the NS SLA and the NSD, and obtains the virtual VNF included in the NS.
  • the Virtualized Network Function Descriptor includes the VNF SLA information, the VNF SLA and the NFV Infrastructure (NFVI) SLA, and the NFVO includes the VNF according to the NS.
  • the VNF SLA marker and the NS include the VNF of the VNFD, which determines the NFVI SLA parameters of the VNF included in the NS.
  • the NSD can be carried in the NS instantiation request.
  • the NSD can also be stored in the log.
  • the NFVO parses the NS instantiation request to learn the NS that needs to be instantiated, and then obtains the NSD, NSD from the log. It is uploaded to the log by the operator through NFVO, and the operator can also upload the VNFD and VNF images to the log.
  • the NSD is an NS description template corresponding to the NS, and can be used to describe the information of the NS. For example, the number of VNFs included in an NS, and the links between the network elements, and the NNF can also include the VNFD.
  • the NSD is completed by the operator before the NS is deployed.
  • the NSD includes the VNFs.
  • the NS SLA information, the NS SLA, and the VNF SLA are added to the NSD.
  • the information of the NS SLA includes an identifier of the NS SLA (service_sla_id), a keyword of the NS SLA (service_sla_key), and a specific value of the NS SLA (service_sla_value).
  • the relationship between NS SLA and VNF SLA includes: the VNF SLA identifier of the VNF included in the NS, and the correlation calculation model of the NS SLA parameter and the VNF SLA parameter.
  • Table 1 shows the format of the new base element NS SLA identifier in NSD.
  • Table 2 shows the information format of the NS SLA, and
  • Table 3 shows the format of the association between the NS SLA and the VNF SLA.
  • the NFVO determines the VNF SLA of the VNF included in the NS based on the identity of the NS SLA and the NSD. Specifically, the NFVO determines whether the NSD includes the information of the NS SLA according to the identifier of the NS SLA. When the information of the NS SLA is included in the NSD, the NFVO calculates the VNF SLA parameter corresponding to the NS SLA parameter according to the correlation calculation model of the NS SLA information and the VNF SLA parameter. When the NS includes multiple VNFs, the NFVO is settled according to the association. The model can get the VNF SLA for each VNF.
  • the VNFD can be carried in the NS instantiation request.
  • the NFVO obtains the VNFD of the VNF included in the NS from the NS instantiation request.
  • the VNFD can also be stored in the log, and the NFVO obtains the VNFD from the log.
  • the VNFD includes information on the VNF SLA, the relationship between the VNF SLA and the NFVI SLA.
  • the information of the VNF SLA includes the identifier, keyword and specific value of the VNF SLA.
  • the relationship between the VNF SLA and the NFVI SLA includes: the relationship identifier and the correlation calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • Table 5 shows the format of the identification of the new basic element VNFD SLA in VNFD.
  • Table 5 shows the information format of the VNFD SLA, and
  • Table 6 shows the format of the relationship between the VNFD SLA and the NFVI SLA.
  • the NFVO determines the NFVI SLA parameters of the VNF included in the NS based on the VNF SLA identification and the VNFD. Specifically, NFVO first determines whether the VNFD contains the VNF SLA identifier. When the VNFD contains a VNF SLA identifier, the NFVO calculates the NFVI SLA parameter corresponding to the VNF SLA parameter based on the VNF SLA information and the NFVI SLA parameter correlation calculation model.
  • the NFVO determines the NFVI SLA parameters required to instantiate the network service according to the identifier of the SLA of the network service, specifically: the NFVO acquires the VNFD of the VNF, and the VNFD includes the information of the VNF SLA and the VNF SLA. In association with the NFVI SLA, NFVO determines the NFVI SLA parameters of the VNF based on the VNF SLA identification and the VNFD.
  • the VNFD may be carried in the VNF instantiation request or may be stored in the VIM log.
  • the information of the VNF SLA includes the identifier, keyword and specific value of the VNF SLA.
  • the relationship between the VNF SLA and the NFVI SLA includes: the relationship identifier and the correlation calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the format of the information of the VNF SLA and the format of the relationship between the VNF SLA and the NFVI SLA are as described in Tables 4 to 6 above.
  • Step 103 The NFVO obtains a virtual resource that meets the NFVI SLA parameter requirement from the VIM according to the NFVI SLA parameter.
  • the NFVO sends a first resource request message to the VIM, where the first resource request message includes an NFVI SLA parameter, and the first resource request message further includes the required number of virtual resources.
  • the VIM determines the virtual resource that meets the NFVI SLA parameter requirement according to the NFVI SLA parameter, and returns a first resource response message to the NFVO, and the NFVO receives the first resource response message sent by the VIM, and the first resource request message. It includes virtual resources that meet the needs of the NFVI SLA parameters.
  • the NFVO determines the virtual resource information that meets the requirements of the NFVI SLA parameter from each NFVI resource pool according to the NFVI SLA parameter and the SLA parameter information of the NFVI resource pool obtained from the VIM, and sends the information to the VIM. And sending a second resource request message, where the second resource request message is used to query the availability of the virtual resource and the virtual resource is reserved, and the second resource request message includes the information of the virtual resource.
  • the VIM checks whether the virtual resource of the NFVO application is available according to the information of the virtual resource. If the virtual resource requested by the NFVO is available, the virtual resource is reserved for the NFVO, and the second resource response message is returned to the NFVO.
  • the second resource response message includes a predetermined result.
  • NFVI resources are managed by NFVO.
  • the NFVO receives the SLA parameter information of the NFVI resource pool reported by the VIM, and groups the SLA parameters of the virtual resources in the NFVI resource pool according to a preset grouping rule.
  • the NFVO may be based on the NFVI SLA parameter.
  • a target grouping that satisfies the NFVI SLA parameter requirement is determined from each group, and then the virtual resource is requested from the target group.
  • the preset grouping rule is a cluster of virtual resources or a cluster of virtual resources, that is, the NFVO can manage the SLA parameters of the virtual resources according to the resource pool granularity such as a region or a cluster.
  • Step 104 The NFVO instantiates the network service according to the obtained virtual resource.
  • the method in the foregoing embodiment can be used not only in the instantiation process of the NS and the VNF, but also in the migration and expansion of the NS, and the VNF migration and expansion scenario.
  • the NFVO receives the network service instantiation request, the network service instantiation request includes the identifier of the SLA of the network service, and the NFVO determines the NFVI SLA required to instantiate the network service according to the identifier of the SLA of the network service.
  • the parameter further obtains a virtual resource that satisfies the NFVI SLA parameter requirement from the VIM according to the NFVI SLA parameter, and instantiates the network service according to the obtained virtual resource.
  • the method considers the NFVI SLA parameter when the NFVO applies for the virtual resource, so that the obtained virtual resource satisfies the user requirement and improves the qualified hit rate of the resource application.
  • FIG. 3 is a signaling flowchart of an SLA-based resource allocation method according to Embodiment 2 of the present invention. As shown in FIG. 3, the method provided in this embodiment may include the following steps:
  • the operator sends an NS instantiation request to the NFVO, where the NS instantiation request includes an identifier of the NS SLA and an NSD.
  • the NFVO verifies the legality of the NS instantiation request.
  • NFVO verifies the legitimacy of the NS instantiation request and the legitimacy of the NS that needs to be instantiated.
  • the NFVO sends a VNF instance query request to the VNFM.
  • the NS instantiation request also includes the VNF included in the NS.
  • the NS may include multiple VNFs.
  • the VNF instance query request is used to query whether the VNF included in the NS exists. If a VNF instance exists, the VNF needs to be instantiated. If the VNF does not exist, then further VNF needs to be instantiated.
  • the VNFM sends a VNF instance query response to the NFVO.
  • the VNF instance query response includes information about whether the VNF instance of the query exists.
  • the NFVO determines the VNF SLA of the VNF included in the NS according to the identifier of the NS SLA and the NSD.
  • the NSD includes information about the NS SLA, and the association between the NS SLA and the VNF SLA. For the specific implementation of this step, refer to the related description of the foregoing Embodiment 1.
  • the NFVO sends a VNFD query request to the log.
  • the VNFD query request is used to request a VNFD and mirror of the VNF included in the NS.
  • the log sends a VNFD query response to the NFVO.
  • the VNFD query response includes the VNFD neutralization image of the VNF of the query, and the VNFD includes information of the VNF SLA, the relationship between the VNF SLA and the NFVI SLA.
  • NFVO can also query the VNFD and mirror of the VNF from a specific VNFM.
  • NFVI SLA of the VNF determines the NFVI SLA of the VNF based on the VNF SLA identification and the VNFD.
  • the NFVO queries the information of the virtual resource of the NFVI SLA that satisfies the VNF from the local.
  • the NFVO queries the VIM for the availability of the virtual resource and reserves the virtual resource.
  • the VIM returns a predetermined result of the virtual resource to the NFVO.
  • FIG. 4 is a schematic structural diagram of an NFVO according to Embodiment 3 of the present invention.
  • the NFVO includes: a receiving module 11, a determining module 12, an obtaining module 13, and an instantiation module 14.
  • the receiving module 11 is configured to receive a network service instantiation request, where the network service instantiation request includes an identifier of a service level agreement SLA of the network service.
  • the determining module 12 is configured to determine, according to the identifier of the SLA of the network service, a network function virtualization infrastructure NFVI SLA parameter required to instantiate the network service;
  • the obtaining module 13 is configured to obtain, from the virtualization infrastructure manager VIM, a virtual resource that meets the NFVI SLA parameter requirement according to the NFVI SLA parameter;
  • the instantiation module 14 is configured to instantiate the network service according to the obtained virtual resource.
  • the network service is a network service NS
  • the network service instantiation request is an NS instantiation request
  • the identifier of the SLA of the network service is an identifier of the NS SLA
  • the determining module 12 is specifically configured to:
  • NSD network service descriptor of the NS, where the NSD includes information about the NS SLA, a VNF included by the NS, and an association relationship between an NS SLA and a virtual network function VNF SLA;
  • VNFD virtual network function descriptor VNFD of the VNF included in the NS, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVI SLA parameter of the VNF included in the NS is determined based on the identification of the VNF SLA of the VNF included in the NS and the VNFD of the VNF included in the NS.
  • the information about the NS SLA includes an identifier, a keyword, and a specific value of the NS SLA
  • the association relationship between the NS SLA and the VNF SLA includes: an identifier of the VNF SLA of the VNF included in the NS, an NS SLA parameter, and Correlation calculation model of VNF SLA parameters;
  • the VNF SLA information includes an identifier, a keyword, and a specific value of the VNF SLA, and the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier and an associated calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the network service is a VNF
  • the network service instantiation request is a VNF instantiation request
  • the identifier of the SLA of the network service is an identifier of the VNF SLA
  • the determining module 12 is specifically configured to:
  • VNFD virtual network function descriptor VNFD of the VNF, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVI SLA parameter of the VNF is determined based on the identification of the VNF SLA and the VNFD.
  • the obtaining module 13 is configured to: send a first resource request message to the VIM, where the first resource request message includes the NFVI SLA parameter, and receive a first resource response sent by the VIM.
  • the message that the first resource request message includes information of a virtual resource that meets the NFVI SLA parameter requirement.
  • the obtaining module 13 is specifically configured to: determine, according to the NFVI SLA parameter, and the SLA parameter information of the NFVI resource pool acquired from the VIM, from the NFVI resource pools to meet the The information of the virtual resource of the NFVI SLA parameter is sent to the VIM, where the second resource request message includes the information of the virtual resource, where the second resource request message is used to query the The availability of the virtual resource and the scheduling of the virtual resource, receiving a second resource response message sent by the VIM.
  • the NFVO further includes a grouping module, where the receiving module is further configured to receive SLA parameter information of the NFVI resource pool reported by the VIM, where the grouping module is configured to: according to a preset grouping rule The SLA parameters of the virtual resources in the NFVI resource pool are grouped.
  • the obtaining module 13 is specifically configured to: determine, according to the NFVI SLA parameter, a target group that meets the NFVI SLA parameter requirement from each group.
  • the preset grouping rule is grouping according to a region of a virtual resource or a cluster of virtual resources.
  • the NFVO provided in the embodiment of the present invention may perform the foregoing method embodiments, and the implementation principles and technical effects thereof are similar, and details are not described herein again.
  • FIG. 5 is a schematic structural diagram of an NFVO according to Embodiment 4 of the present invention.
  • the NFVO includes: a transmitter 21, a receiver 22, a memory 23, and a processor 24.
  • the memory 23 is configured to store program instructions.
  • the transmitter 21 is configured to send data to other devices
  • the receiver 22 is configured to receive data sent by other devices
  • the processor 24 is configured to invoke program instructions in the memory 23 to perform the following methods:
  • the network service is a network service NS
  • the network service instantiation request is an NS instantiation request
  • the identifier of the SLA of the network service is an identifier of an NS SLA
  • the processor 24 is configured according to the NS SLA.
  • the NSD determining a VNF SLA of the VNF included in the NS, specifically:
  • the NSD includes information about the NS SLA, a VNF included by the NS, and an association relationship between an NS SLA and a VNF SLA;
  • VNFD virtual network function descriptor VNFD of the VNF included in the NS, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and an NFVI SLA;
  • the NFVI SLA parameter of the VNF included in the NS is determined based on the identification of the VNF SLA of the VNF included in the NS and the VNFD of the VNF included in the NS.
  • the information about the NS SLA includes an identifier, a keyword, and a specific value of the NS SLA
  • the association relationship between the NS SLA and the VNF SLA includes: an identifier of the VNF SLA of the VNF included in the NS, an NS SLA parameter, and Correlation calculation model of VNF SLA parameters;
  • the VNF SLA information includes an identifier, a keyword, and a specific value of the VNF SLA, and the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier and an associated calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the network service is a VNF
  • the network service instantiation request is a VNF instantiation request
  • the identifier of the SLA of the network service is an identifier of a VNF SLA
  • the processor 24 is configured according to the identifier of the NS SLA.
  • the NSD determining a VNF SLA of the VNF included in the NS, specifically:
  • VNFD virtual network function descriptor VNFD of the VNF, where the VNFD includes information of a VNF SLA, and a relationship between a VNF SLA and a network function virtualization infrastructure NFVI SLA;
  • the NFVI SLA parameter of the VNF is determined based on the identification of the VNF SLA and the VNFD.
  • the information of the VNF SLA includes an identifier, a keyword, and a specific value of the VNF SLA
  • the relationship between the VNF SLA and the NFVI SLA includes: a relationship identifier, and an association calculation model of the VNF SLA parameter and the NFVI SLA parameter.
  • the processor 24 obtains, according to the NFVI SLA parameter, a virtual resource that meets the NFVI SLA parameter requirement from the virtualization infrastructure manager VIM, specifically:
  • the processor 24 obtains, according to the NFVI SLA parameter, a virtual resource that meets the NFVI SLA parameter requirement from the virtualization infrastructure manager VIM, specifically:
  • the processor 24 is further configured to: receive SLA parameter information of the NFVI resource pool reported by the VIM; and group SLA parameters of the virtual resources in the NFVI resource pool according to a preset grouping rule;
  • a target packet that satisfies the NFVI SLA parameter requirement is determined from each packet based on the NFVI SLA parameter.
  • the preset grouping rule is grouping according to a region of a virtual resource or a cluster of virtual resources.
  • the transmitter 21, the receiver 22, and the memory 23 are connected to the processor 24, and the communication bus is used to implement a communication connection between components.
  • the communication bus may be an ISA (Industry Standard Architecture). A bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the communication bus may be one or more physical lines, and when it is a plurality of physical lines, it may be divided into an address bus, a data bus, a control bus, and the like.
  • the memory 23 in this embodiment may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the present implementation.
  • the receiver 22 in this embodiment may be a corresponding input interface having a communication function and a function of receiving information.
  • the transmitter 21 in this embodiment may be a corresponding output interface having a communication function and a function of transmitting information, and the sending
  • the device 21 and the receiver 22 can be integrated in one communication interface, or can be two separate communication interfaces.
  • the processor 24 can be, for example, a central processing unit (CPU), or a processing chip having a function of generating a service configuration command and other functions.
  • the various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments.
  • the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Abstract

本发明实施例提供一种基于SLA的资源分配方法和NFVO，包括：NFVO接收网络业务实例化请求，该网络业务实例化请求中包该网络业务的SLA的标识，NFVO根据该网络业务的SLA的标识确定实例化该网络业务所需的NFVI SLA参数，进一步根据NFVI SLA参数，从VIM处获取满足NFVI SLA参数需求的虚拟资源，根据获取的虚拟资源对该网络业务进行实例化。所述方法由于NFVO在申请虚拟资源时，考虑了NFVI SLA参数，从而使得获取到的虚拟资源满足用户需求，提高了资源申请的合格命中率。

Description

基于SLA的资源分配方法和NFVO
本申请要求于2017年2月20日提交中国专利局、申请号为201710091068.9，发明名称为“基于SLA的资源分配方法和NFVO”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术，尤其涉及一种基于服务水平协议(Service Level Agreement，简称SLA)的资源分配方法和网络功能虚拟化编排器(Network Function Virtualization Orchestrator，简称NFVO)。
背景技术
网络功能虚拟化(Network Function Virtualization，简称NFV)技术通过使用通用性硬件以及虚拟化技术，来承载很多功能的软件处理，从而降低网络昂贵的设备成本。
NFV系统的架构主要由以下几个功能构件组成：
NFVO，负责网络服务(Network Service，简称NS)的生命周期管理，编排管理资源，实时监测网络功能虚拟化基础设施(NFV Infrastructure，简称NFVI)资源及运行状态信息；与虚拟网络功能管理器(Virtualised Network Function Manager，简称VNFM)配合实现监控虚拟网络功能(Virtualised Network Function，简称VNF)的生命周期管理和资源的全局视图。
VNFM，负责VNF的生命周期管理，如，VNF实例的初始化、VNF实例的扩/缩容、VNF实例的终止、管理VNF运行状态信息。
虚拟化基础设施管理器(Virtualised Infrastructure Manager，简称VIM)，负责基础设施层硬件资源、虚拟化资源的管理、监控和故障上报，面向上层应用提供虚拟化资源池。如，负责管理、分配NFVI资源、监测收集NFVI运行状态信息。NFVI资源，由硬件资源、虚拟资源以及虚拟化层组成，其包括所有NFVI资源状态，可用的/已预留的/已分配的NFVI资源。从VNF的角度来说，虚拟化层和硬件资源看起来是一个能够提供所需虚拟资源的实体。
在该NFV系统中，VNF是能够在NFVI上运行的网络功能(NF，Network Function)的软件实现，其相当于网络节点的实体，被期望以摆脱硬件依赖的纯软件来交付。
现有技术中在NFVO对NS/VNF实例化、扩容、迁移过程中，需要向VIM申请NFVI虚拟资源时，NFVO只告诉VIM需要的NFVI虚拟资源的数量，VIM根据NFVO需要的NFVI虚拟资源的数量向NFVI返回相应数量的NFVI虚拟资源，但是NFVO申请的NFVO虚拟资源可能无法满足NS/VNF的服务质量，可能需要多次向VIM申请NFVI虚拟资源，导致NFVI虚拟资源申请的合格命中率低。
发明内容
本发明实施例提供一种基于SLA的资源分配方法和NFVO，NFVO在申请虚拟资源时，考虑了NFVI SLA参数，从而使得获取到的虚拟资源满足用户需求，提高了资源申请的合格命中率。
第一方面，本发明实施例提供一种基于SLA的资源分配方法，包括：NFVO接收网络业务实例化请求，所述网络业务实例化请求中包括网络业务的SLA的标识，根据所述网络业务的SLA的标识确定实例化所述网络业务所需的NFVI SLA参数，根据所述NFVI SLA参数，从虚拟 化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，根据获取的所述虚拟资源对所述网络业务进行实例化。该方法中，NFVO在申请虚拟资源时，考虑了NFVI SLA参数，从而使得获取到的虚拟资源满足用户需求，提高了资源申请的合格命中率。
可选地，所述网络业务为NS，所述网络业务实例化请求为NS实例化请求，所述网络业务的SLA的标识为NS SLA的标识，所述NFVO根据所述网络业务的SLA的标识确定实例化所述网络业务所需的NFVI SLA参数，具体为：
所述NFVO获取所述NS的网络服务描述符NSD，所述NSD中包括所述NS SLA的信息、所述NS包括的VNF、NS SLA与虚拟网络功能VNF SLA的关联关系；
所述NFVO根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA；
所述NFVO获取所述NS包括的VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
所述NFVO根据所述NS包括的VNF的VNF SLA的标识和所述NS包括的VNF的VNFD，确定所述NS包括的VNF的NFVI SLA参数。
可选的，所述NS SLA的信息包括NS SLA的标识、关键字和具体值，所述NS SLA与VNF SLA的关联关系包括：所述NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型；
所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述网络业务为虚拟网络功能VNF，所述网络业务实例化请求为VNF实例化请求，所述网络业务的SLA的标识为VNF SLA的标识，所述NFVO根据所述网络业务的SLA的标识确定实例化所述网络业务所需的NFVI SLA参数，具体为：
所述NFVO获取所述VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
所述NFVO根据所述VNF SLA的标识和所述VNFD，确定所述VNF的NFVI SLA参数。
可选的，所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述NFVO根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，具体为：
所述NFVO向所述VIM发送第一资源请求消息，所述第一资源请求消息中包括所述NFVI SLA参数；
所述NFVO接收所述VIM发送的第一资源响应消息，所述第一资源请求消息中包括满足所述NFVI SLA参数需求的虚拟资源的信息。
可选地，所述NFVO根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，具体为：
所述NFVO根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息；
所述NFVO向所述VIM发送第二资源请求消息，所述第二资源请求消息中包括所述虚拟资源的信息，所述第二资源请求消息用于查询所述虚拟资源的可用性和预定所述虚拟资源；
所述NFVO接收所述VIM发送的第二资源响应消息。
可选地，所述方法还包括：
所述NFVO接收所述VIM上报的NFVI资源池的SLA参数信息；
所述NFVO按照预设的分组规则对所述NFVI资源池中虚拟资源的SLA参数进行分组；
相应的，所述NFVO根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息，具体为：
所述NFVO根据所述NFVI SLA参数，从各分组中确定满足所述NFVI SLA参数需求的目标分组。
可选的，所述预设的分组规则为按照虚拟资源的地域或虚拟资源的簇进行分组。
第二方面，本发明实施例提供一种网络功能虚拟化编排器NFVO，包括：
接收模块，用于接收网络业务实例化请求，所述网络业务实例化请求中包括网络业务的服务水平协议SLA的标识；
确定模块，用于根据所述网络业务的SLA的标识确定实例化所述网络业务所需的网络功能虚拟化基础设施NFVI SLA参数；
获取模块，用于根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源；
实例化模块，用于根据获取的所述虚拟资源对所述网络业务进行实例化。
可选地，所述网络业务为网络服务NS，所述网络业务实例化请求为NS实例化请求，所述网络业务的SLA的标识为NS SLA的标识，所述确定模块具体用于：
获取所述NS的网络服务描述符NSD，所述NSD中包括所述NS SLA的信息、所述NS包括的VNF、NS SLA与虚拟网络功能VNF SLA的关联关系；
根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA；
获取所述NS包括的VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
根据所述NS包括的VNF的VNF SLA的标识和所述NS包括的VNF的VNFD，确定所述NS包括的VNF的NFVI SLA参数。
可选的，所述NS SLA的信息包括NS SLA的标识、关键字和具体值，所述NS SLA与VNF SLA的关联关系包括：所述NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型；
所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述网络业务为虚拟网络功能VNF，所述网络业务实例化请求为VNF实例化请求，所述网络业务的SLA的标识为VNF SLA的标识，所述确定模块具体用于：
获取所述VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
根据所述VNF SLA的标识和所述VNFD，确定所述VNF的NFVI SLA参数。
可选的，所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述获取模块，具体用于：
向所述VIM发送第一资源请求消息，所述第一资源请求消息中包括所述NFVI SLA参数；
接收所述VIM发送的第一资源响应消息，所述第一资源请求消息中包括满足所述NFVI SLA 参数需求的虚拟资源的信息。
可选地，所述获取模块，具体用于：
根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息；
向所述VIM发送第二资源请求消息，所述第二资源请求消息中包括所述虚拟资源的信息，所述第二资源请求消息用于查询所述虚拟资源的可用性和预定所述虚拟资源；
接收所述VIM发送的第二资源响应消息。
可选的，所述NFVO还包括分组模块；
所述接收模块，还用于接收所述VIM上报的NFVI资源池的SLA参数信息；
所述分组模块，用于按照预设的分组规则对所述NFVI资源池中虚拟资源的SLA参数进行分组；
相应的，所述获取模块，具体用于：根据所述NFVI SLA参数，从各分组中确定满足所述NFVI SLA参数需求的目标分组。
可选的，所述预设的分组规则为按照虚拟资源的地域或虚拟资源的簇进行分组。
第三方面，本发明实施例提供一种NFVO，包括：发送器、接收器、存储器和处理器，存储器用于存储程序指令，所述发送器用于向其他设备发送数据，所述接收器用于接收其他设备发送的数据，所述处理器用于调用所述存储器中的程序指令执行下述方法：
接收网络业务实例化请求，所述网络业务实例化请求中包括网络业务的SLA的标识；
根据所述网络业务的SLA的标识确定实例化所述网络业务所需的NFVI SLA参数；
根据所述NFVI SLA参数，从VIM处获取满足所述NFVI SLA参数需求的虚拟资源；
根据获取的所述虚拟资源对所述网络业务进行实例化。
可选地，所述网络业务为网络服务NS，所述网络业务实例化请求为NS实例化请求，所述网络业务的SLA的标识为NS SLA的标识，所述处理器根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA，具体为：
获取所述NS的NSD，所述NSD中包括所述NS SLA的信息、所述NS包括的VNF、NS SLA与VNF SLA的关联关系；
根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA；
获取所述NS包括的VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与NFVI SLA的关联关系；
根据所述NS包括的VNF的VNF SLA的标识和所述NS包括的VNF的VNFD，确定所述NS包括的VNF的NFVI SLA参数。
可选的，所述NS SLA的信息包括NS SLA的标识、关键字和具体值，所述NS SLA与VNF SLA的关联关系包括：所述NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型；
所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述网络业务为VNF，所述网络业务实例化请求为VNF实例化请求，所述网络业务的SLA的标识为VNF SLA的标识，所述处理器根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA，具体为：
获取所述VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与 网络功能虚拟化基础设施NFVI SLA的关联关系；
根据所述VNF SLA的标识和所述VNFD，确定所述VNF的NFVI SLA参数。
可选的，所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述处理器根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，具体为：
向所述VIM发送第一资源请求消息，所述第一资源请求消息中包括所述NFVI SLA参数；
接收所述VIM发送的第一资源响应消息，所述第一资源请求消息中包括满足所述NFVI SLA参数需求的虚拟资源的信息。
可选地，所述处理器根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，具体为：
根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息；
向所述VIM发送第二资源请求消息，所述第二资源请求消息中包括所述虚拟资源的信息，所述第二资源请求消息用于查询所述虚拟资源的可用性和预定所述虚拟资源；
接收所述VIM发送的第二资源响应消息。
可选的，所述处理器还用于：接收所述VIM上报的NFVI资源池的SLA参数信息；按照预设的分组规则对所述NFVI资源池中虚拟资源的SLA参数进行分组；
则根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息，具体为：
根据所述NFVI SLA参数，从各分组中确定满足所述NFVI SLA参数需求的目标分组。
可选的，所述预设的分组规则为按照虚拟资源的地域或虚拟资源的簇进行分组。
第四方面，本发明实施例还提供一种计算机程序产品，该计算机程序产品中包含计算机程序，该计算机程序当被处理器或其它类型芯片读取并执行时可以实现本发明前述实施例提供的基于SLA的资源分配方法。该计算机程序产品可达到的有益效果和具体工作原理参考前述实施例，在此不再赘述。
附图说明
图1为NFV系统的架构示意图；
图2为本发明实施例一提供的基于SLA的资源分配方法的流程图；
图3为本发明实施例二提供的基于SLA的资源分配方法的信令流程图；
图4为本发明实施例三提供的一种NFVO的结构示意图；
图5为本发明实施例四提供的一种NFVO的结构示意图。
具体实施方式
本发明实施例的方法可以应用在NFV系统中，该NFV系统可以实现多种网络，例如局域网(Local Area Network，简称LAN)、互联网协议(Internet Protocol，简称IP)网络或者演进分组核心网(Evolved Packet Core，简称EPC)网络。图1为NFV系统的架构示意图，如图1所示，该NFV系统可以包括NFV管理和编排系统(NFV Management and Orchestration System，NFV-MANO)110，NFVI 150，VNF 140，多个网元管理系统(Element Management System， EMS)130，以及一个或多个运营支撑系统/业务支撑系统(Operation Support System/Business Support System，简称OSS/BSS)120。
NFV-MANO 110可以包括NFVO 111、一个或多个VNFM 112，以及一个或VIM113；NFVI 150可以包括计算硬件1521、存储硬件1522、网络硬件1523组成的硬件资源层、虚拟化层、以及虚拟计算1511(例如虚拟机)、虚拟存储1512和虚拟网络1513组成的虚拟资源层。
硬件资源层中的计算硬件1521可以为专用的处理器或通用的用于提供处理和计算功能的处理器，如中央处理器(Central Process Unite，简称CPU)；存储硬件1522用于提供存储能力，例如，磁盘或网络附属存储(Network Attached Storage，简称NAS)；网络硬件1523可以是交换机、路由器和/或其他网络设备。
NFVI 150中的虚拟化层用于抽象硬件资源层的硬件资源，将VNF 140和硬件资源所属的物理层解耦，向VNF提供虚拟资源。
虚拟资源层可以包括虚拟计算1511、虚拟存储1512和虚拟网络1513。虚拟计算1511、虚拟存储1512可以以虚拟机或其他虚拟容器的形式向VNF 140提供，例如一个或多个虚拟机组成一个VNF 140。虚拟化层通过抽象网络硬件1523形成虚拟网络1513。虚拟网络1513，用于实现多个虚拟机之间，或多个承载VNF的其他类型的虚拟容器之间的通信。虚拟网络的创建可以通过虚拟LAN(Vritual LAN，简称VLAN)、虚拟专用局域网业务(Virtual Private LAN Service，简称VPLS)、虚拟可扩展局域网(Virtual eXtensible Local Area Network，简称VxLAN)或通用路由封装网络虚拟化(Nerwork Virtualization using Generic Routing Encapsulation，简称NVGRE)等技术实现。
OSS/BSS 120主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。
NFV-MANO 110可以用于实现VNF 140和NFVI 150的监控和管理。NFVO 111可以与一个或多个VNFM 112进行通信以实现与资源相关的请求、发送配置信息给VNFM 112、以及收集VNF 140的状态信息。另外，NFVO 111还可以与VIM 113进行通信以实现资源分配，和/或，实现虚拟化硬件资源的配置信息和状态信息的预留和交换。VNFM 112可以用于管理一个或多个VNF 140，执行各种管理功能，例如初始化、更新、查询、和/或终止VNF 140。VIM 113可以用于控制和管理VNF 140和计算硬件1521、存储硬件1522、网络硬件1523、虚拟计算1511、虚拟存储1512以及虚拟网络1513的交互。例如，VIM 113可以用于执行资源向VNF 140的分配操作。VNFM 112和VIM 113可以互相通信以交换虚拟化硬件资源配置和状态信息。
NFVI 150包含硬件和软件，二者共同建立虚拟化环境以部署、管理和执行VNF 140。换句话说，硬件资源层和虚拟资源层用于向VNF 140提供虚拟资源，例如虚拟机和/或其他形式的虚拟容器。
如图1所示，VNFM 112可以与VNF 140和EMS 130通信以执行VNF生命周期管理和实现配置/状态信息的交换。VNF 140是至少一个网络功能的虚拟化，该网络功能之前是由物理网络设备提供的。在一种实现方式下，VNF 140可以是一个虚拟化的移动管理实体(Mobility Management Entity，简称MME)节点，用于提供典型的非虚拟化的MME设备提供的所有网络功能。在另一种实现方式下，VNF 140可以用于实现非虚拟化的MME设备上提供的全部组件中的部分组件的功能。一个VNF 140可以由一个或多个虚拟网络功能组件(VNF Component，简称VNFC)组成，所述VNFC可以为虚拟机或其他形式的虚拟容器。EMS 130可以用于管理一个或多个VNF 140。
根据以上对NFV系统的系统架构中每个构成部分的功能论述可知，VNFM 112用于对VNF 140执行各种管理功能，如初始化、更新、查询以及终止VNF 140等，而VIM 113用于控制和管理VNF 140与其他部分进行交互，因此，若实现一个VNF 140，则必须VNFM 112和VIM 113协同工作，因此，VNFM 112和VIM 113可以互相通信以交换虚拟化硬件资源配置和状态信息，其中，VNFM 112和VIM 113通过接口建立通信连接。
基于上述图1所示的VNF系统架构，图1为本发明实施例一提供的基于SLA的资源分配方法的流程图，如图1所示，本实施例的方法可以包括以下步骤：
S101、NFVO接收网络业务实例化请求，该网络业务实例化请求中包括该网络业务的服务水平协议(Service-Level Agreement，简称SLA)的标识(Idengtity，简称ID)。
网络业务实例化请求用于请求对网络业务进行实例化，该网络业务实例化请求可以是操作员向NFVO发起的，还可以是其他的软件或者硬件设备向NFVO发起的。不同于现有的网络业务实例化请求，本实施例中在网络业务实例化请求中新增了参数：网络业务的SLA的ID，网络业务的SLA的ID用于标识网络业务的SLA参数，不同网络业务的SLA参数不同，相应的，不同网络业务的SLA的ID不同。SLA是国际通行的电信服务评估标准，是指运营商和用户之间达成的就用户支付一定的费用而要求运营商保证特定的业务性能和可靠度的一项协议。传统的SLA通常包括业务可用度和客户支持服务的保证，如电路可用性、网络性能、服务响应时间、业务提供保证等，进行服务质量、收费标准及赔付标准的承诺等。
可选的，本实施例涉及的网络业务可以为NS或VNF相应的，网络服务实例化请求可以为NS实例化请求或VNF实例化请求，NS实例化请求中包括的网络业务的SLA的标识为NS SLA的标识，VNF实例化请求中包括的网络业务的SLA的标识为VNF SLA的标识。其中，NS是由多个VNF组成的以提供更复杂的功能的网络业务，对NS进行实例化实际上是对NS包括的VNF进行实例化。
步骤102、NFVO根据该网络业务的SLA的标识确定实例化该网络业务所需的NFVI SLA参数。
当该网络业务为NS时，NFVO根据该网络业务的SLA的标识确定实例化该网络业务所需的NFVI SLA参数，具体为：NFVO获取NS的网络服务描述符(Network Service Descriptor，简称NSD)，该NSD中包括NS SLA的信息、NS包括的VNF、NS SLA与VNF SLA的关联关系，然后，NFVO根据NS SLA的标识以及NSD，确定NS包括的VNF的VNF SLA，获取NS包括的VNF的虚拟网络功能描述符(Virtualized Network Function Descriptor，简称VNFD)，该VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施(NFV Infrastructure，简称NFVI)SLA的关联关系，NFVO根据NS包括的VNF的VNF SLA的标识和NS包括的VNF的VNFD，确定NS包括的VNF的NFVI SLA参数。
NSD可以携带在NS实例化请求中，NSD还可以存储在日志(catalog)中，NFVO收到NS实例化请求后，解析NS实例化请求获知需要实例化的NS，然后从日志处获取NSD，NSD是操作员通过NFVO上传至日志的，操作员还将可以将VNFD、VNF镜像上传至日志。NSD是NS对应的NS描述模板，可以用于描述NS的信息，例如描述一个NS中包括的VNF的个数，以及各网元之间的链路等，该NSD中还可以包括VNFD。
NSD由运营商在NS部署前完成，NSD中包括NS由哪些VNF组成，本实施例中在NSD中增加了NS SLA的信息、NS SLA与VNF SLA的关联关系。其中，NS SLA的信息包括NS SLA的标识(service_sla_id)、NS SLA的关键字(service_sla_key)和NS SLA的具体值 (service_sla_value)。NS SLA与VNF SLA的关联关系包括：NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型。
表1为NSD中新增的基本元素(base element)NS SLA的标识的格式。表2为NS SLA的信息格式，表3为NS SLA与VNF SLA关联关系的格式。
表1
Figure PCTCN2018073681-appb-000001
表2
Figure PCTCN2018073681-appb-000002
表3
Figure PCTCN2018073681-appb-000003
在获取NSD后，NFVO根据NS SLA的标识和该NSD，确定NS包括的VNF的VNF SLA。具体的，NFVO根据NS SLA的标识判断NSD中是否包含NS SLA的信息。当NSD中包含NS SLA的信息时，NFVO根据该NS SLA的信息与VNF SLA参数的关联计算模型，计算NS SLA参数对应的VNF SLA参数，当NS中包括多个VNF时，NFVO根据该关联结算模型可以得到每个VNF的VNF SLA。
VNFD可以携带在NS实例化请求中，NFVO从NS实例化请求中获取NS包括的VNF的VNFD，VNFD还可以存储在日志中，NFVO从日志中获取VNFD。该VNFD中包括VNF SLA的信息、VNF SLA与NFVI SLA的关联关系。其中，VNF SLA的信息包括VNF SLA的标识、关键字和具体值，VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
表5为VNFD中新增的基本元素VNFD SLA的标识的格式。表5为VNFD SLA的信息格式，表6为VNFD SLA与NFVI SLA的关联关系的格式。
表4
Figure PCTCN2018073681-appb-000004
表5
Figure PCTCN2018073681-appb-000005
Figure PCTCN2018073681-appb-000006
表6
Figure PCTCN2018073681-appb-000007
在获取VNFD后，NFVO根据VNF SLA的标识以及VNFD，确定NS包括的VNF的NFVI SLA参数。具体的，NFVO先判断VNFD中是否包含VNF SLA的标识。当VNFD中包含某个VNF SLA的标识时，NFVO根据VNF SLA的信息与NFVI SLA参数的关联计算模型，确定VNF SLA参数对应的NFVI SLA参数。
当该网络业务为NS时，NFVO根据该网络业务的SLA的标识确定实例化该网络业务所需的NFVI SLA参数，具体为：NFVO获取VNF的VNFD，该VNFD中包括VNF SLA的信息、VNF SLA与NFVI SLA的关联关系，NFVO根据VNF SLA的标识和该VNFD，确定VNF的NFVI SLA参数。
其中，该VNFD可以携带在VNF实例化请求中，也可以存储在VIM的日志中。该VNF SLA的信息包括VNF SLA的标识、关键字和具体值，VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。VNF SLA的信息的格式和VNF SLA与NFVI SLA的关联关系的格式参照上述表4-表6的描述。
步骤103、NFVO根据NFVI SLA参数，从VIM处获取满足NFVI SLA参数需求的虚拟资源。
第一种实现方式中，NFVO向VIM发送第一资源请求消息，第一资源请求消息中包括NFVI SLA参数，第一资源请求消息中还包括需要的虚拟资源的数量。VIM接收到第一资源请求消息后，根据NFVI SLA参数确定满足NFVI SLA参数需求的虚拟资源，并向NFVO返回第一资源响应消息，NFVO接收VIM发送的第一资源响应消息，第一资源请求消息中包括满足NFVI SLA参数需求的虚拟资源。
第二种实现方式中，NFVO根据NFVI SLA参数，以及预先从VIM处获取的NFVI资源池的SLA参数信息，从各NFVI资源池中确定满足NFVI SLA参数的需求的虚拟资源的信息，并向VIM发送第二资源请求消息，第二资源请求消息用于查询虚拟资源的可用性和预定该虚拟资源，第二资源请求消息中包括虚拟资源的信息。VIM接收到第二资源请求消息后，根据虚拟资源的信息检查NFVO申请的虚拟资源是否可用，如果NFVO申请的虚拟资源可用，则为NFVO预留该虚拟资源，并向NFVO返回第二资源响应消息，第二资源响应消息中包括预定结果。
在第二种实现方式中，由NFVO对NFVI资源进行管理。相应的，NFVO会接收VIM上报的NFVI资源池的SLA参数信息，按照预设的分组规则对NFVI资源池中虚拟资源的SLA参数进行分组。后续，当NFVO根据NFVI SLA参数，以及预先从VIM处获取的NFVI资源池的SLA参数信息，从各NFVI资源池中确定满足NFVI SLA参数的需求的虚拟资源的信息时，NFVO可以根据NFVI SLA参数，从各分组中确定满足NFVI SLA参数需求的目标分组，然后向目标分组申请该虚拟资源。 其中，预设的分组规则为虚拟资源的地域或虚拟资源的簇(Cluster)，即NFVO可以根据地域或Cluster等资源池粒度对虚拟资源的SLA参数进行管理。
步骤104、NFVO根据获取的虚拟资源对网络业务进行实例化。
需要说明的是，上述实施例的方法不仅可以用在NS和VNF的实例化过程中，还可以应用在NS的迁移和扩容，以及VNF迁移和扩容场景中。
本实施例的方法，NFVO接收网络业务实例化请求，该网络业务实例化请求中包该网络业务的SLA的标识，NFVO根据该网络业务的SLA的标识确定实例化该网络业务所需的NFVI SLA参数，进一步根据NFVI SLA参数，从VIM处获取满足NFVI SLA参数需求的虚拟资源，根据获取的虚拟资源对该网络业务进行实例化。所述方法由于NFVO在申请虚拟资源时，考虑了NFVI SLA参数，从而使得获取到的虚拟资源满足用户需求，提高了资源申请的合格命中率。
在实施例一的基础上，图3为本发明实施例二提供的基于SLA的资源分配方法的信令流程图，如图3所示，本实施例提供的方法可以包括以下步骤：
S201、操作员向NFVO发送NS实例化请求，该NS实例化请求中包括NS SLA的标识和NSD。
S202、NFVO验证NS实例化请求的合法性。
NFVO验证NS实例化请求的合法性，以及需要实例化的NS的合法性。
S203、NFVO向VNFM发送VNF实例查询请求。
NS实例化请求中还包括NS包括的VNF，NS包括的VNF可能为多个，VNF实例查询请求用于查询NS包括的VNF是否存在，如果某个VNF实例存在，则不需要实例化该VNF，如果VNF不存在，则需要进一步实例化VNF。
S204、VNFM向NFVO发送VNF实例查询响应。
VNF实例查询响应中包括查询的VNF实例是否存在的信息。
S205、NFVO根据NS SLA的标识和NSD确定NS包括的VNF的VNF SLA。
该NSD中包括NS SLA的信息、NS SLA和VNF SLA的关联关系，本步骤的具体实现方式参照上述实施例一的相关描述。
S206、NFVO向日志发送VNFD查询请求。
该VNFD查询请求用于请求查询NS包括的VNF的VNFD和镜像。
S207、日志向NFVO发送VNFD查询响应。
该VNFD查询响应中包括查询的VNF的VNFD中和镜像，VNFD中包括VNF SLA的信息、VNF SLA与NFVI SLA的关联关系。
需要说明的是，NFVO也可以从特定的VNFM查询VNF的VNFD和镜像。
S208、NFVO根据VNF SLA的标识和VNFD，确定VNF的NFVI SLA。
S209、NFVO从本地查询满足VNF的NFVI SLA的虚拟资源的信息。
S210、NFVO向VIM查询虚拟资源的可用性并预定虚拟资源。
S211、VIM向NFVO返回虚拟资源的预定结果。
图4为本发明实施例三提供的一种NFVO的结构示意图，如图4所示，该NFVO包括：接收模块11、确定模块12、获取模块13和实例化模块14。
其中，接收模块11，用于接收网络业务实例化请求，所述网络业务实例化请求中包括网络业务的服务水平协议SLA的标识；
确定模块12，用于根据所述网络业务的SLA的标识确定实例化所述网络业务所需的网络功能虚拟化基础设施NFVI SLA参数；
获取模块13，用于根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源；
实例化模块14，用于根据获取的所述虚拟资源对所述网络业务进行实例化。
可选地，所述网络业务为网络服务NS，所述网络业务实例化请求为NS实例化请求，所述网络业务的SLA的标识为NS SLA的标识，则所述确定模块12具体用于：
获取所述NS的网络服务描述符NSD，所述NSD中包括所述NS SLA的信息、所述NS包括的VNF、NS SLA与虚拟网络功能VNF SLA的关联关系；
根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA；
获取所述NS包括的VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
根据所述NS包括的VNF的VNF SLA的标识和所述NS包括的VNF的VNFD，确定所述NS包括的VNF的NFVI SLA参数。
可选的，所述NS SLA的信息包括NS SLA的标识、关键字和具体值，所述NS SLA与VNF SLA的关联关系包括：所述NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型；
所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述网络业务为VNF，所述网络业务实例化请求为VNF实例化请求，所述网络业务的SLA的标识为VNF SLA的标识，则所述确定模块12具体用于：
获取所述VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
根据所述VNF SLA的标识和所述VNFD，确定所述VNF的NFVI SLA参数。
可选的，所述获取模块13，具体用于：向所述VIM发送第一资源请求消息，所述第一资源请求消息中包括所述NFVI SLA参数，接收所述VIM发送的第一资源响应消息，所述第一资源请求消息中包括满足所述NFVI SLA参数需求的虚拟资源的信息。
可选地，所述获取模块13，具体用于：根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息，向所述VIM发送第二资源请求消息，所述第二资源请求消息中包括所述虚拟资源的信息，所述第二资源请求消息用于查询所述虚拟资源的可用性和预定所述虚拟资源，接收所述VIM发送的第二资源响应消息。
可选地，所述NFVO还包括分组模块，所述接收模块，还用于接收所述VIM上报的NFVI资源池的SLA参数信息，所述分组模块，用于按照预设的分组规则对所述NFVI资源池中虚拟资源的SLA参数进行分组，相应的，所述获取模块13，具体用于：根据所述NFVI SLA参数，从各分组中确定满足所述NFVI SLA参数需求的目标分组。
可选的，所述预设的分组规则为按照虚拟资源的地域或虚拟资源的簇进行分组。
本发明实施例提供的NFVO，可以执行上述方法实施例，其实现原理和技术效果类似，在此不再赘述。
图5为本发明实施例四提供的一种NFVO的结构示意图，如图5所示，该NFVO包括：发送器21、接收器22、存储器23和处理器24，存储器23用于存储程序指令，所述发送器21用于向其他设备发送数据，所述接收器22用于接收其他设备发送的数据，所述处理器24用于调用所述存储器23中的程序指令执行下述方法：
接收网络业务实例化请求，所述网络业务实例化请求中包括网络业务的SLA的标识；
根据所述网络业务的SLA的标识确定实例化所述网络业务所需的NFVI SLA参数；
根据所述NFVI SLA参数，从VIM处获取满足所述NFVI SLA参数需求的虚拟资源；
根据获取的所述虚拟资源对所述网络业务进行实例化。
可选地，所述网络业务为网络服务NS，所述网络业务实例化请求为NS实例化请求，所述网络业务的SLA的标识为NS SLA的标识，所述处理器24根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA，具体为：
获取所述NS的NSD，所述NSD中包括所述NS SLA的信息、所述NS包括的VNF、NS SLA与VNF SLA的关联关系；
根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA；
获取所述NS包括的VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与NFVI SLA的关联关系；
根据所述NS包括的VNF的VNF SLA的标识和所述NS包括的VNF的VNFD，确定所述NS包括的VNF的NFVI SLA参数。
可选的，所述NS SLA的信息包括NS SLA的标识、关键字和具体值，所述NS SLA与VNF SLA的关联关系包括：所述NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型；
所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述网络业务为VNF，所述网络业务实例化请求为VNF实例化请求，所述网络业务的SLA的标识为VNF SLA的标识，所述处理器24根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA，具体为：
获取所述VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
根据所述VNF SLA的标识和所述VNFD，确定所述VNF的NFVI SLA参数。
可选的，所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
可选地，所述处理器24根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，具体为：
向所述VIM发送第一资源请求消息，所述第一资源请求消息中包括所述NFVI SLA参数；
接收所述VIM发送的第一资源响应消息，所述第一资源请求消息中包括满足所述NFVI SLA参数需求的虚拟资源的信息。
可选地，所述处理器24根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，具体为：
根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息；
向所述VIM发送第二资源请求消息，所述第二资源请求消息中包括所述虚拟资源的信息，所述第二资源请求消息用于查询所述虚拟资源的可用性和预定所述虚拟资源；
接收所述VIM发送的第二资源响应消息。
可选的，所述处理器24还用于：接收所述VIM上报的NFVI资源池的SLA参数信息；按照预设的分组规则对所述NFVI资源池中虚拟资源的SLA参数进行分组；
则根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息，具体为：
根据所述NFVI SLA参数，从各分组中确定满足所述NFVI SLA参数需求的目标分组。
可选的，所述预设的分组规则为按照虚拟资源的地域或虚拟资源的簇进行分组。
本实施例中，发送器21、接收器22、存储器23通信总线与处理器24连接，通信总线用于实现元件之间的通信连接，该通信总线可以是ISA(Industry Standard Architecture，工业标准体系结构)总线、PCI(Peripheral Component Interconnect，外部设备互连)总线或EISA(Extended Industry Standard Architecture，扩展工业标准体系结构)总线等。所述通信总线可以是一条或多条物理线路，当是多条物理线路时可以分为地址总线、数据总线、控制总线等。本实施例中的存储器23可能包含高速RAM存储器，也可能还包括非易失性存储NVM，例如至少一个磁盘存储器，存储器23中可以存储各种程序，用于完成各种处理功能以及实现本实施例的方法步骤。另外，本实施例中的接收器22可以为相应的具有通信功能和接收信息功能的输入接口，本实施例中的发送器21可以为相应的具有通信功能和发送信息功能的输出接口，该发送器21和接收器22可以集成在一个通信接口中，也可以分别为独立的两个通信接口。该处理器24例如可以为中央处理器(Central Processing Unit，简称CPU)，还可以为具有生成业务配置命令功能以及其他功能的处理芯片。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于装置实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的 相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (18)

  1. 一种基于SLA的资源分配方法，其特征在于，包括：
    网络功能虚拟化编排器NFVO接收网络业务实例化请求，所述网络业务实例化请求中包括网络业务的服务水平协议SLA的标识；
    所述NFVO根据所述网络业务的SLA的标识确定实例化所述网络业务所需的网络功能虚拟化基础设施NFVI SLA参数；
    所述NFVO根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源；
    所述NFVO根据获取的所述虚拟资源对所述网络业务进行实例化。
  2. 根据权利要求1所述的方法，其特征在于，所述网络业务为网络服务NS，所述网络业务实例化请求为NS实例化请求，所述网络业务的SLA的标识为NS SLA的标识，所述NFVO根据所述网络业务的SLA的标识确定实例化所述网络业务所需的NFVI SLA参数，包括：
    所述NFVO获取所述NS的网络服务描述符NSD，所述NSD中包括所述NS SLA的信息、所述NS包括的VNF、NS SLA与虚拟网络功能VNF SLA的关联关系；
    所述NFVO根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA；
    所述NFVO获取所述NS包括的VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
    所述NFVO根据所述NS包括的VNF的VNF SLA的标识和所述NS包括的VNF的VNFD，确定所述NS包括的VNF的NFVI SLA参数。
  3. 根据权利要求2所述的方法，其特征在于，所述NS SLA的信息包括NS SLA的标识、关键字和具体值，所述NS SLA与VNF SLA的关联关系包括：所述NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型；
    所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
  4. 根据权利要求1所述的方法，其特征在于，所述网络业务为虚拟网络功能VNF，所述网络业务实例化请求为VNF实例化请求，所述网络业务的SLA的标识为VNF SLA的标识，所述NFVO根据所述网络业务的SLA的标识确定实例化所述网络业务所需的NFVI SLA参数，包括：
    所述NFVO获取所述VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
    所述NFVO根据所述VNF SLA的标识和所述VNFD，确定所述VNF的NFVI SLA参数。
  5. 根据权利要求4所述的方法，其特征在于，所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述NFVO根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，包括：
    所述NFVO向所述VIM发送第一资源请求消息，所述第一资源请求消息中包括所述NFVI SLA参数；
    所述NFVO接收所述VIM发送的第一资源响应消息，所述第一资源请求消息中包括满足所述NFVI SLA参数需求的虚拟资源的信息。
  7. 根据权利要求1-5任一项所述的方法，其特征在于，所述NFVO根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源，包括：
    所述NFVO根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息；
    所述NFVO向所述VIM发送第二资源请求消息，所述第二资源请求消息中包括所述虚拟资源的信息，所述第二资源请求消息用于查询所述虚拟资源的可用性和预定所述虚拟资源；
    所述NFVO接收所述VIM发送的第二资源响应消息。
  8. 根据权利要求7所述的方法，其特征在于，还包括：
    所述NFVO接收所述VIM上报的NFVI资源池的SLA参数信息；
    所述NFVO按照预设的分组规则对所述NFVI资源池中虚拟资源的SLA参数进行分组；
    所述NFVO根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息，包括：
    所述NFVO根据所述NFVI SLA参数，从各分组中确定满足所述NFVI SLA参数需求的目标分组。
  9. 根据权利要求8所述的方法，其特征在于，所述预设的分组规则为按照虚拟资源的地域或虚拟资源的簇进行分组。
  10. 一种网络功能虚拟化编排器NFVO，其特征在于，包括：
    接收模块，用于接收网络业务实例化请求，所述网络业务实例化请求中包括网络业务的服务水平协议SLA的标识；
    确定模块，用于根据所述网络业务的SLA的标识确定实例化所述网络业务所需的网络功能虚拟化基础设施NFVI SLA参数；
    获取模块，用于根据所述NFVI SLA参数，从虚拟化基础设施管理器VIM处获取满足所述NFVI SLA参数需求的虚拟资源；
    实例化模块，用于根据获取的所述虚拟资源对所述网络业务进行实例化。
  11. 根据权利要求10所述的NFVO，其特征在于，所述网络业务为网络服务NS，所述网络业务实例化请求为NS实例化请求，所述网络业务的SLA的标识为NS SLA的标识，所述确定模块具体用于：
    获取所述NS的网络服务描述符NSD，所述NSD中包括所述NS SLA的信息、所述NS包括的VNF、NS SLA与虚拟网络功能VNF SLA的关联关系；
    根据所述NS SLA的标识以及所述NSD，确定所述NS包括的VNF的VNF SLA；
    获取所述NS包括的VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
    根据所述NS包括的VNF的VNF SLA的标识和所述NS包括的VNF的VNFD，确定所述NS包括的VNF的NFVI SLA参数。
  12. 根据权利要求11所述的NFVO，其特征在于，所述NS SLA的信息包括NS SLA的标识、关键字和具体值，所述NS SLA与VNF SLA的关联关系包括：所述NS包括的VNF的VNF SLA的标识、NS SLA参数与VNF SLA参数的关联计算模型；
    所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
  13. 根据权利要求10所述的NFVO，其特征在于，所述网络业务为虚拟网络功能VNF，所 述网络业务实例化请求为VNF实例化请求，所述网络业务的SLA的标识为VNF SLA的标识，所述确定模块具体用于：
    获取所述VNF的虚拟网络功能描述符VNFD，所述VNFD中包括VNF SLA的信息、VNF SLA与网络功能虚拟化基础设施NFVI SLA的关联关系；
    根据所述VNF SLA的标识和所述VNFD，确定所述VNF的NFVI SLA参数。
  14. 根据权利要求13所述的NFVO，其特征在于，所述VNF SLA的信息包括VNF SLA的标识、关键字和具体值，所述VNF SLA与NFVI SLA的关联关系包括：关系标识以及VNF SLA参数与NFVI SLA参数的关联计算模型。
  15. 根据权利要求10-14任一项所述的NFVO，其特征在于，所述获取模块，具体用于：
    向所述VIM发送第一资源请求消息，所述第一资源请求消息中包括所述NFVI SLA参数；
    接收所述VIM发送的第一资源响应消息，所述第一资源请求消息中包括满足所述NFVI SLA参数需求的虚拟资源的信息。
  16. 根据权利要求10-14任一项所述的NFVO，其特征在于，所述获取模块，具体用于：
    根据所述NFVI SLA参数，以及预先从所述VIM处获取的NFVI资源池的SLA参数信息，从所述各NFVI资源池中确定满足所述NFVI SLA参数的需求的虚拟资源的信息；
    向所述VIM发送第二资源请求消息，所述第二资源请求消息中包括所述虚拟资源的信息，所述第二资源请求消息用于查询所述虚拟资源的可用性和预定所述虚拟资源；
    接收所述VIM发送的第二资源响应消息。
  17. 根据权利要求16所述的NFVO，其特征在于，还包括分组模块；
    所述接收模块，还用于接收所述VIM上报的NFVI资源池的SLA参数信息；
    所述分组模块，用于按照预设的分组规则对所述NFVI资源池中虚拟资源的SLA参数进行分组；
    所述获取模块，具体用于：根据所述NFVI SLA参数，从各分组中确定满足所述NFVI SLA参数需求的目标分组。
  18. 根据权利要求17所述的NFVO，其特征在于，所述预设的分组规则为按照虚拟资源的地域或虚拟资源的簇进行分组。
PCT/CN2018/073681 2017-02-20 2018-01-23 基于sla的资源分配方法和nfvo WO2018149272A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18754170.1A EP3471345B1 (en) 2017-02-20 2018-01-23 Sla-based resource allocation method and nfvo
US16/273,165 US20190173802A1 (en) 2017-02-20 2019-02-12 Sla-based resource allocation method and nfvo

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710091068.9A CN108462592A (zh) 2017-02-20 2017-02-20 基于sla的资源分配方法和nfvo
CN201710091068.9 2017-02-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/273,165 Continuation US20190173802A1 (en) 2017-02-20 2019-02-12 Sla-based resource allocation method and nfvo

Publications (1)

Publication Number Publication Date
WO2018149272A1 true WO2018149272A1 (zh) 2018-08-23

Family

ID=63170486

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/073681 WO2018149272A1 (zh) 2017-02-20 2018-01-23 基于sla的资源分配方法和nfvo

Country Status (4)

Country Link
US (1) US20190173802A1 (zh)
EP (1) EP3471345B1 (zh)
CN (1) CN108462592A (zh)
WO (1) WO2018149272A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109379699A (zh) * 2018-11-12 2019-02-22 中国联合网络通信集团有限公司 创建虚拟化转发面网元的方法及装置

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110620754B (zh) * 2018-09-05 2021-01-22 中兴通讯股份有限公司 Nf所需资源的部署方法、装置、存储介质及电子装置
US11249796B2 (en) * 2018-10-03 2022-02-15 Samsung Electronics Co., Ltd. Method and apparatus for enhanced assertion management in cloud media processing
CN111949364A (zh) 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
CN112087311B (zh) 2019-06-14 2022-04-12 华为技术有限公司 一种虚拟网络功能vnf部署方法及装置
US10931507B2 (en) * 2019-06-25 2021-02-23 Vmware, Inc. Systems and methods for selectively implementing services on virtual machines and containers
US11296975B2 (en) 2019-06-25 2022-04-05 Vmware, Inc. Systems and methods for implementing multi-part virtual network functions
US11924060B2 (en) * 2019-09-13 2024-03-05 Intel Corporation Multi-access edge computing (MEC) service contract formation and workload execution
CN112583615B (zh) 2019-09-29 2022-04-29 北京华为数字技术有限公司 Vnf实例化方法、nfvo、vim、vnfm及系统
CN112631712A (zh) * 2019-10-08 2021-04-09 中国电信股份有限公司 网络功能虚拟化的实现方法、装置以及系统
US11818019B2 (en) 2019-11-08 2023-11-14 Telefonaktiebolaget Lm Ericsson (Publ) Achieving requested service availability
WO2021164888A1 (en) * 2020-02-21 2021-08-26 Nokia Solutions And Networks Oy Discovery of service instance
CN113328868B (zh) * 2020-02-28 2022-12-16 中移雄安信息通信科技有限公司 Nfv管理方法、vnfm、mec平台及存储介质
CN114666223B (zh) * 2020-12-04 2023-11-21 中国移动通信集团设计院有限公司 云计算资源池处理方法、装置及可读存储介质
CN114666211B (zh) * 2020-12-23 2023-11-17 上海华为技术有限公司 一种通信方法、模型处理方法及相关设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105453485A (zh) * 2013-09-06 2016-03-30 华为技术有限公司 用于服务嵌入和资源协调的系统及方法
CN105743962A (zh) * 2014-12-23 2016-07-06 英特尔公司 端对端数据中心性能控制
US20160205004A1 (en) * 2015-01-13 2016-07-14 Intel IP Corporation Techniques for Monitoring Virtualized Network Functions or Network Functions Virtualization Infrastructure

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100512307C (zh) * 2006-03-06 2009-07-08 华为技术有限公司 通讯网络中网络资源的分配方法及系统
US9838265B2 (en) * 2013-12-19 2017-12-05 Amdocs Software Systems Limited System, method, and computer program for inter-module communication in a network based on network function virtualization (NFV)
US20150281006A1 (en) * 2014-03-14 2015-10-01 Avni Networks Inc. Method and apparatus distributed multi- cloud resident elastic analytics engine

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105453485A (zh) * 2013-09-06 2016-03-30 华为技术有限公司 用于服务嵌入和资源协调的系统及方法
CN105743962A (zh) * 2014-12-23 2016-07-06 英特尔公司 端对端数据中心性能控制
US20160205004A1 (en) * 2015-01-13 2016-07-14 Intel IP Corporation Techniques for Monitoring Virtualized Network Functions or Network Functions Virtualization Infrastructure

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3471345A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109379699A (zh) * 2018-11-12 2019-02-22 中国联合网络通信集团有限公司 创建虚拟化转发面网元的方法及装置

Also Published As

Publication number Publication date
EP3471345A4 (en) 2019-08-21
EP3471345B1 (en) 2022-03-09
EP3471345A1 (en) 2019-04-17
US20190173802A1 (en) 2019-06-06
CN108462592A (zh) 2018-08-28

Similar Documents

Publication Publication Date Title
WO2018149272A1 (zh) 基于sla的资源分配方法和nfvo
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US11456930B2 (en) Network resource management method, apparatus, and system
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
US11301303B2 (en) Resource pool processing to determine to create new virtual resource pools and storage devices based on currebt pools and devices not meeting SLA requirements
JP6834033B2 (ja) ネットワークスライス管理方法、ユニット、及びシステム
WO2020258920A1 (zh) 一种网络切片资源管理方法及设备
EP3133794B1 (en) Network function virtualization network system
WO2018058579A1 (zh) 网络切片的管理方法及管理单元
US10924966B2 (en) Management method, management unit, and system
EP2849064B1 (en) Method and apparatus for network virtualization
WO2017113201A1 (zh) 一种网络服务的生命周期管理方法及设备
WO2018205325A1 (zh) 在异构资源上构建内容分发网络平台的方法和系统
JP6463851B2 (ja) サービス可用性管理のための方法およびエンティティ
US20190261186A1 (en) Network Slice Management Method, Management Unit, and System
WO2015113234A1 (zh) 网络功能虚拟化的方法及装置
JP2018530214A (ja) ネットワークサービスをデプロイするための方法及び装置
WO2015021629A1 (zh) 一种资源发放方法
EP3531749B1 (en) Management method, management unit and system for network function
WO2017035738A1 (zh) 一种资源管理方法及装置
EP3528472B1 (en) Method for managing hardware resource, method for querying location of hardware resource, and related apparatus
WO2019174000A1 (zh) 用于业务管理的方法和装置
WO2020211652A1 (zh) 多租户场景下的租户资源管理方法和装置
WO2020108443A1 (zh) 一种虚拟化管理方法及装置
WO2016183832A1 (zh) 一种网络业务实例化的方法及设备

Legal Events

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

Ref document number: 18754170

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018754170

Country of ref document: EP

Effective date: 20190109

NENP Non-entry into the national phase

Ref country code: DE