[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2017054129A1 - 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器 - Google Patents

一种网络功能虚拟化资源处理方法及虚拟网络功能管理器 Download PDF

Info

Publication number
WO2017054129A1
WO2017054129A1 PCT/CN2015/091066 CN2015091066W WO2017054129A1 WO 2017054129 A1 WO2017054129 A1 WO 2017054129A1 CN 2015091066 W CN2015091066 W CN 2015091066W WO 2017054129 A1 WO2017054129 A1 WO 2017054129A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
vnfm
information
target
target vim
Prior art date
Application number
PCT/CN2015/091066
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 JP2018516167A priority Critical patent/JP6511585B2/ja
Priority to RU2018115309A priority patent/RU2690198C1/ru
Priority to PCT/CN2015/091066 priority patent/WO2017054129A1/zh
Priority to EP15905041.8A priority patent/EP3358790B1/en
Priority to KR1020187011984A priority patent/KR20180061299A/ko
Priority to CN201580028616.2A priority patent/CN107005452B/zh
Publication of WO2017054129A1 publication Critical patent/WO2017054129A1/zh
Priority to US15/940,102 priority patent/US20180219793A1/en

Links

Images

Classifications

    • 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
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/782—Hierarchical allocation of resources, e.g. involving a hierarchy of local and centralised 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • 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/72—Admission control; Resource allocation using reservation actions during connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • 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/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements

Definitions

  • the present invention relates to the field of network function virtualization, and in particular, to a network function virtualization resource processing method and a virtual network function manager.
  • Network Function Virtualization (English: Network Functions Virtualization, NFV) technology enables many types of network devices to be incorporated into industry standards by borrowing information technology (Information Technology, IT: Virtualization). For example: Services, switching, storage, etc. can be deployed in data centers or network nodes. Implement various network functions in software, run on industry-standard servers, and migrate, instantiate, redeploy, etc. as needed, without the need to install new devices, ie create virtual network functions (English: Virtualized Network Function, referred to as: VNF). Network services can be implemented between multiple virtual network functions (English: Network Service, NS for short).
  • NFV Network Function Virtualization
  • an NFV Orchestrator (English: NFV Orchestrator, referred to as: NFVO) can manage multiple virtual network function managers (English: VNF Manager, referred to as VNFM), a VNFM can manage multiple VNFs, NFVO control Management and allocation of VIM resources.
  • NFV Orchestrator English: NFV Orchestrator, referred to as: NFVO
  • VNFM virtual network function managers
  • a VNFM can manage multiple VNFs
  • NFVO control Management allocation of VIM resources.
  • Embodiments of the present invention provide a network function virtualization resource processing method and a virtual network function manager that can improve the robustness and efficiency of a network in resource allocation management.
  • a first aspect of the embodiments of the present invention provides a network function virtualization resource processing method, including:
  • the first virtual network function manager VNFM sends a first resource request message to the second VNFM, where the first resource request message includes resource information that the first VNFM requests for the virtual network function VNF;
  • the first VNFM receives the first feedback message sent by the second VNFM, where the first feedback message includes the target VIM that reserves or allocates resources for the first VNFM. Information.
  • the method further include:
  • the first VNFM sends a first resource allocation message to the target VIM, where the first resource allocation message is used by the target VIM to allocate resources of the application.
  • the first feedback message includes a resource reservation identifier
  • the first resource allocation message includes the resource reservation identifier, where the resource reservation identifier is used to identify the reserved resource.
  • the first feedback message When the first feedback message includes information of the target VIM to which the resource is allocated for the first VNFM, the first feedback message further includes any combination of the following information: a target virtual target allocated by the target VIM The identifier of the machine VM, the location information of the target VM allocated by the target VIM.
  • the information of the target VIM includes any combination of the following information:
  • An identifier of the target VIM configured to establish configuration information for establishing a connection with the target VIM.
  • the method further includes: when the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application, the first VNFM receives a second feedback message sent by the second VNFM;
  • the second feedback message is used to indicate that the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application.
  • the second feedback message includes resource information of remaining resources of the target VIM connected to the second VNFM, and the resource information of the remaining resources includes a resource type of the remaining resources and a resource amount of the remaining resources.
  • the method further includes:
  • the resource information of the application includes the resource type of the application and the amount of resources requested.
  • a second aspect of the embodiments of the present invention provides a network function virtualization resource processing method, including:
  • the second VNFM receives the first resource request message sent by the first VNFM, where the first resource request message includes resource information that the first VNFM requests for the virtual network function VNF;
  • the first VNFM sends a first feedback message to the first VNFM, the first The feedback message includes information of the target VIM that reserved or allocated resources for the first VNFM.
  • the method further includes:
  • the second VNFM receives a resource reservation feedback message sent by the target VIM.
  • the resource reservation message includes a resource reservation identifier
  • the first feedback message includes the resource reservation identifier, where the resource reservation identifier is used to identify the reserved resource.
  • the method further includes:
  • the second VNFM receives a resource allocation feedback message sent by the target VIM.
  • the first feedback message further includes any combination of the following: an identifier of the target virtual machine VM allocated by the target VIM, and location information of the target VM allocated by the target VIM.
  • the information of the target VIM includes any combination of the following information:
  • An identifier of the target VIM configured to establish configuration information for establishing a connection with the target VIM.
  • the method further includes: when the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application, the second VNFM sends a second feedback message to the first VNFM;
  • the second feedback message is used to indicate that the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application.
  • the second feedback message includes the target VIM connected to the second VNFM Resource information of the remaining resources, where the resource information of the remaining resources includes a resource type of the remaining resources and a resource amount of the remaining resources.
  • the method further includes:
  • the second VNFM receives the first VNFM to send a second resource request message, where the second resource request message includes resource information of a reconfiguration resource, where the remaining resource is used by the target VIM as the first VNFM pre- Leave or allocate the reconfiguration resource.
  • the resource information of the application includes the resource type of the application and the amount of resources requested.
  • a third aspect of the embodiments of the present invention provides a virtual network function manager VNFM, including:
  • a sending unit configured to send a first resource request message to the second VNFM, where the first resource request message includes resource information that is requested by the VNFM for the virtual network function VNF;
  • a receiving unit configured to receive a first feedback message sent by the second VNFM when the resource of the target virtualization infrastructure manager VIM connected to the second VNFM meets the resource information of the application, where the first The feedback message contains information of the target VIM that reserved or allocated resources for the VNFM.
  • the VNFM further includes:
  • a determining unit configured to determine that the first feedback message includes information of the target VIM that reserves resources for the VNFM
  • the sending unit is further configured to: when the first feedback message includes information about the target VIM that reserves resources for the VNFM, send a first resource allocation message to the target VIM, where the first resource is An allocation message is used by the target VIM to allocate resources of the application.
  • the first feedback message received by the receiving unit includes a resource reservation identifier
  • the first resource allocation message sent by the sending unit includes the resource reservation identifier, where the resource reservation identifier is used for marking Know the reserved resources.
  • the VNFM further includes: a determining unit, configured to determine that the first feedback message includes information about the target VIM that is allocated resources for the VNFM, and the first feedback message further includes any combination of the following information: The identifier of the target virtual machine VM allocated by the target VIM, and the location information of the target VM.
  • the VNFM according to any one of the third aspect of the present invention
  • the information of the target VIM received by the receiving unit includes any combination of the following information:
  • An identifier of the target VIM configured to establish configuration information for establishing a connection with the target VIM.
  • the receiving unit is further configured to: when the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application, receive a second feedback message sent by the second VNFM;
  • the second feedback message is used to indicate that the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application.
  • the second feedback message received by the receiving unit further includes resource information of remaining resources of the target VIM connected to the second VNFM, where resource information of the remaining resources includes resource types and remaining resources of the remaining resources. The amount of resources.
  • the sending unit is further configured to send a second resource request message to the second VNFM, where the second resource request message includes resource information of a reconfiguration resource, where the remaining resource is used by the target VIM as the VNFM Reserve or allocate the reconfiguration resources.
  • the resource information of the application sent by the sending unit includes the resource type of the application and the amount of resources requested.
  • a fourth aspect of the embodiments of the present invention provides a virtual network function manager VNFM, including:
  • a receiving unit configured to receive a first resource request message sent by the first VNFM, where the first resource request message includes resource information that is requested by the first VNFM for the virtual network function VNF;
  • a determining unit configured to determine that a resource of the target virtualization infrastructure manager VIM connected to the VNFM satisfies resource information of the application
  • a sending unit configured to send, by the first VNFM, a first feedback message, the first feedback message, when the resource of the target virtualization infrastructure manager VIM that is connected to the VNFM meets the resource information of the application Information including the target VIM that reserves or allocates resources for the first VNFM.
  • the VNFM also includes:
  • the sending unit is further configured to send a resource reservation message to the target VIM;
  • the receiving unit is further configured to receive a resource reservation feedback message sent by the target VIM.
  • the resource reservation message sent by the sending unit includes a resource reservation identifier, where the first feedback message sent by the sending unit includes the resource reservation identifier, and the resource reservation identifier is used to identify the location
  • the resources reserved by the target VIM are used to allocate resources of the application.
  • the VNFM also includes:
  • the sending unit is further configured to send a second resource allocation message to the target VIM.
  • the receiving unit is further configured to receive a resource allocation feedback message sent by the target VIM.
  • the first feedback message sent by the sending unit further includes any combination of the following information: An identifier of the target virtual machine VM allocated by the target VIM, and location information of the target VM allocated by the target VIM.
  • the VNFM according to any one of the fourth implementation manners of the fourth aspect of the present invention
  • the information of the target VIM included in the first feedback message sent by the sending unit includes any combination of the following information:
  • An identifier of the target VIM configured to establish configuration information for establishing a connection with the target VIM.
  • the determining unit is further configured to: determine that the resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application;
  • the sending unit is further configured to: when the resource of the target VIM that is connected to the VNFM cannot meet the resource information of the application, send a second feedback message to the first VNFM, where the second feedback message is used to indicate The resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application.
  • the second feedback message sent by the sending unit includes resource information of remaining resources of the target VIM connected to the VNFM, and the resource information of the remaining resources includes a resource type of the remaining resources and a resource amount of the remaining resources. .
  • the receiving unit is further configured to receive a second resource request message sent by the first VNFM, where the second resource request message includes resource information of a reconfiguration resource, where the remaining resource is used by the target VIM
  • the first VNFM reserves or allocates the reconfiguration resources.
  • the resource information of the application received by the receiving unit includes a resource type of the application and an amount of resources requested.
  • a fifth aspect of the embodiments of the present invention provides a virtual network function manager VNFM, including:
  • a transmitter configured to send a first resource request message to the second VNFM, where the first resource request message includes resource information that is requested by the VNFM for the virtual network function VNF;
  • the receiver And receiving, by the receiver, the first feedback message sent by the second VNFM, when the resource of the target virtualization infrastructure manager VIM connected to the second VNFM meets the resource information of the application, the first The feedback message contains information of the target VIM that reserved or allocated resources for the VNFM.
  • the VNFM further includes a processor
  • the processor configured to determine that the first feedback message includes information of the target VIM that reserves resources for the VNFM;
  • the transmitter is further configured to: when the first feedback message includes information about the target VIM that reserves resources for the VNFM, send a first resource allocation message to the target VIM, where the first resource is An allocation message is used by the target VIM to allocate resources of the application.
  • the first feedback message received by the receiver includes a resource reservation identifier
  • the first resource allocation message sent by the sender includes the resource reservation identifier, where the resource reservation identifier is used to identify the Resources left.
  • the VNFM further includes a processor
  • the processor is configured to determine that the first feedback message includes information about the target VIM that is allocated resources for the VNFM, and the first feedback message further includes any combination of the following information: the target VIM The identifier of the assigned target virtual machine VM, the location information of the target VM.
  • the information of the target VIM received by the receiver includes any combination of the following information:
  • An identifier of the target VIM configured to establish configuration information for establishing a connection with the target VIM.
  • the receiver is further configured to: when the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application, receive a second feedback message sent by the second VNFM;
  • the second feedback message is used to indicate that the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application.
  • the second feedback message received by the receiver further includes resource information of remaining resources of the target VIM connected to the second VNFM, where resource information of the remaining resources includes resource types and remaining resources of the remaining resources. The amount of resources.
  • the transmitter is further configured to send a second resource request message to the second VNFM, where the second resource request message includes resource information of a reconfiguration resource, where the remaining resource is used by the target VIM as the VNFM Reserve or allocate the reconfiguration resources.
  • the resource information of the application sent by the sender includes the resource type of the application and the amount of resources requested.
  • a sixth aspect of the embodiments of the present invention provides a virtual network function manager VNFM, including:
  • a receiver configured to receive a first resource request message sent by the first VNFM, where the first resource request message includes resource information that is requested by the first VNFM for the virtual network function VNF;
  • a processor configured to determine that a resource of the target virtualization infrastructure manager VIM connected to the VNFM satisfies resource information of the application
  • a first feedback message sent to the first VNFM the first feedback message, when the resource of the target virtualization infrastructure manager VIM connected to the VNFM satisfies the resource information of the application Include the target that reserves or allocates resources for the first VNFM VIM information.
  • the transmitter is further configured to send a resource reservation message to the target VIM;
  • the receiver is further configured to receive a resource reservation feedback message sent by the target VIM.
  • the resource reservation message sent by the sender includes a resource reservation identifier
  • the first feedback message sent by the sender includes the resource reservation identifier, where the resource reservation identifier is used to identify the location
  • the resources reserved by the target VIM are used to allocate resources of the application.
  • the transmitter is further configured to send a second resource allocation message to the target VIM.
  • the receiver is further configured to receive a resource allocation feedback message sent by the target VIM.
  • the first feedback message sent by the sender further includes any combination of the following: an identifier of the target virtual machine VM allocated by the target VIM, and location information of the target VM allocated by the target VIM.
  • the information of the target VIM included in the first feedback message sent by the sender includes any combination of the following information:
  • An identifier of the target VIM configured to establish configuration information for establishing a connection with the target VIM.
  • the processor is further configured to determine that the resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application;
  • the transmitter is further configured to: when the resource of the target VIM connected to the VNFM cannot meet the requirement When the resource information of the application is described, the second feedback message is sent to the first VNFM, where the second feedback message is used to indicate that the resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application.
  • the second feedback message sent by the sender includes resource information of remaining resources of the target VIM connected to the VNFM, and the resource information of the remaining resources includes a resource type of the remaining resources and a resource amount of the remaining resources. .
  • the receiver is further configured to receive a second resource request message sent by the first VNFM, where the second resource request message includes resource information of a reconfiguration resource, where the remaining resource is used by the target VIM
  • the first VNFM reserves or allocates the reconfiguration resources.
  • the VNFM according to any one of the eighth implementation manners of the sixth aspect of the present invention
  • the resource information of the application received by the receiver includes a resource type of the application and an amount of resources requested.
  • the present invention provides a network function virtualization resource processing method and a virtual network function manager.
  • the first VNFM determines that a resource needs to be applied for the virtual network function VNF, the first VNFM does not need to pass the NFVO, but is used.
  • the first resource request message for requesting the resource is sent to the second VNFM that is connected to the first VNFM, where the first resource request message includes the resource information that the first VNFM is a VNF request, and the second VNFM
  • the first VNFM determines, according to the received first feedback message, the target that can be determined to be reserved for the first VNFM or to allocate resources. VIM information.
  • the resource processing process shown in this embodiment implements a distributed resource management manner, and when the NFVO fails, the first VNFM can still apply for resources for the virtual network function VNF, thereby effectively improving the robustness of the network. And efficiency.
  • FIG. 1 is a schematic structural diagram of an NFV system according to an embodiment of the present invention
  • FIG. 2 is a schematic partial structural diagram of an NFV system according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of steps of a method for processing a network function virtualization resource according to Embodiment 1 of the present invention
  • FIG. 4 is a flowchart of steps of a method for processing a network function virtualization resource according to Embodiment 2 of the present invention.
  • FIG. 5 is a flowchart of steps of a method for processing a network function virtualization resource according to Embodiment 3 of the present invention.
  • FIG. 6 is a flowchart of steps of a method for processing a network function virtualization resource according to Embodiment 4 of the present invention.
  • FIG. 7 is a flowchart of steps of a method for processing a network function virtualization resource according to Embodiment 5 of the present invention.
  • FIG. 8 is a schematic structural diagram of a virtual network function manager VNFM according to Embodiment 6 of the present invention.
  • FIG. 9 is a schematic structural diagram of a virtual network function manager VNFM according to Embodiment 7 of the present invention.
  • FIG. 10 is a schematic structural diagram of a virtual network function manager VNFM according to Embodiment 8 of the present invention.
  • FIG. 11 is a schematic structural diagram of a virtual network function manager VNFM according to Embodiment 9 of the present invention.
  • FIG. 1 is an architecture diagram of a NFV system in the prior art.
  • the NFV end-to-end architecture defined on the current standard mainly includes three parts: a virtualized network function (VNF), and an NFV infrastructure ( NFV Infrastructure, NFVI), Management and Orchestration (MANO).
  • VNF virtualized network function
  • NFV Infrastructure NFV Infrastructure
  • MANO Management and Orchestration
  • VNF refers to the virtualized network function, which corresponds to the physical network function in the traditional network.
  • NFVI provides hardware and virtual resources for the entire system, consisting of hardware resources (including computing, networking, and storage), virtualization layers (virtualizing hardware resources into resource pools), and virtual resources (also divided into computing, networking, and storage). )composition.
  • MANO includes: NFV Orchestrator (NFVO), VNF Manager (VNFM) and Virtualized Infrastructure Manager (VIM).
  • NFVO NFV Orchestrator
  • VNFM VNF Manager
  • VIP Virtualized Infrastructure Manager
  • NFVO is responsible for life cycle management of network services (NS, service units composed of multiple VNFs), and orchestrate and manage resources (including hardware resources and software resources) of the entire NFV system.
  • VNFM is responsible for lifecycle management of VNF.
  • VIM is responsible for managing NFVI.
  • the VNF is equipped with an Element Management System (EMS) to manage it.
  • EMS Element Management System
  • OSS Operation Support System
  • NFVO Operation Support System
  • FIG. 2 is a schematic structural diagram of a local NFV system capable of implementing a network function virtualization resource processing method according to an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of the NFV system provided by the embodiment of the present invention, which is not limited.
  • the NFV system includes:
  • FIG. 1 For details of the NFV arranger and the VNFM, please refer to FIG. 1 , which is not specifically described in this embodiment.
  • VNFMs included in the management domain of the NFV arranger is not limited in this embodiment.
  • all VNFMs within the management domain of the NFV orchestrator are connected to NFVO.
  • the first VNFM is connected to the second VNFM, so that the message can be transmitted between the first VNFM and the second VNFM;
  • the first VNFM is connected to the second VNFM through an interface.
  • the first VNFM may be connected to the second VNFM, and the first VNFM may be connected to the Nth VNFM.
  • the specific number of N is not limited in this embodiment.
  • Each VNFM management domain contains multiple virtualized infrastructure manager VIMs
  • This embodiment does not limit the specific number of VIMs included in the management domain of each VNFM.
  • two VIMs are provided in connection with the first VNFM, and two VIMs are provided in connection with the second VNFM.
  • the VIM shown in this embodiment can allocate or reserve resources requested by the virtual network function VNF according to the indication of the VNFM.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • FIG. 3 is a flowchart of the steps of the network function virtualization resource processing method according to the first embodiment of the present invention.
  • the first virtual network function manager VNFM sends a first resource request message to the second VNFM.
  • the first VNFM is connected to the second VNFM, and the first VNFM can send the first resource request message to the second VNFM.
  • the present embodiment is exemplified in the management domain of the NFVO by the first VNFM and the second VNFM that are connected to each other, and is not limited.
  • the interconnected first VNFM and the second VNFM may also be located in the management domain of two different NFVOs, as long as the first VNFM can send the first resource request message to the second VNFM.
  • the first resource request message is not limited, as long as the first resource request message includes the resource information that the first VNFM applies for the virtual network function VNF.
  • the first VNFM notifies the second VNFM by using the first resource request message, where the first resource request message includes the resource information that the first VNFM is a VNF request.
  • the specific content of the resource information requested by the first VNFM for the VNF is not limited in this embodiment, as long as the second VNFM determines, according to the resource information of the application, whether the virtualized infrastructure manager VIM connected to the second VNFM can be the first VNFM.
  • the resources of the VNF application can be allocated.
  • the first VNFM receives the first feedback message sent by the second VNFM when the resource of the target virtualization infrastructure manager VIM connected to the second VNFM satisfies the requested resource information.
  • the first VNFM can determine, according to the first feedback message sent by the second VNFM, the target VIM that is reserved or allocated the resource by the first VNFM. Information.
  • the first feedback message is not limited, as long as the first VNFM can determine, according to the first feedback message, the information of the target VIM that is reserved or allocated the resource by the first VNFM.
  • the first VNFM determines that resource allocation is required
  • the first VNFM sends a first resource request message to the second VNFM, and the target VIM connected to the second VNFM
  • the first VNFM determines information of the target VIM that can reserve or allocate the requested resource according to the received first feedback message.
  • a resource management network is formed between the first VNFM and the second VNFM, so that resource processing, such as resource query and resource allocation, can be performed between the VNFMs, and NFVO is not needed. Participation, thus avoiding the impact of NFVO failure on the network, implementing a distributed resource management method, effectively improving the robustness and efficiency of the network.
  • the first embodiment shown in FIG. 3 illustrates the network function virtualization resource processing method from the perspective of the first VNFM.
  • the following describes the network function virtualization resource processing method from the perspective of the second VNFM in conjunction with the second embodiment shown in FIG. 4 .
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the second VNFM receives the first resource request message sent by the first VNFM.
  • the first resource request message includes resource information that the first VNFM applies for the virtual network function VNF.
  • the second VNFM in this embodiment is a VNFM that is connected to the first VNFM and can send messages to each other; the second VNFM and the first VNFM may be located in the same NFVO management domain, or may be located in different NFVO management domains, specifically This embodiment is not limited.
  • the first resource request message is not limited, as long as the second VNFM can determine whether the resource of the VIM connected to the second VNFM can allocate the applied resource after receiving the first resource request message.
  • the second VNFM sends a first feedback message to the first VNFM.
  • the second VNFM when the second VNFM determines that the resource of the target VIM connected to the second VNFM satisfies the requested resource information, the second VNFM sends the first feedback message to the first VNFM.
  • the first feedback message includes information of a target VIM that reserves or allocates resources for the first VNFM.
  • the first VNFM can receive the first resource request message sent by the first VNFM without using the NFVO, and the resource of the target VIM connected to the second VNFM satisfies the first
  • the second VNFM sends the first feedback message to the first VNFM
  • the first VNFM may determine, according to the received first feedback message, that the first VNFM reserves or allocates the resource. VIM information.
  • a resource management network is formed between the first VNFM and the second VNFM, so that resource processing, such as resource query and resource allocation, can be performed between the VNFMs, and the specific processing is performed.
  • resource processing such as resource query and resource allocation
  • NFVO participation is not required, thus avoiding the impact of NFVO failure on the network and implementing a distributed resource management method, so that when the NFVO fails, the second VNFM can still reserve or allocate the applied resources. Effectively improve the robustness and efficiency of the network.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the first VNFM receives a resource application message.
  • the resource application message is not limited, as long as the first VNFM determines that the functional entity applies for the resource to the first VNFM according to the resource application message.
  • the resource request message may be an instantiation request of the VNF, an extension request of the VNF, or any request related to the resource application.
  • the VNF extension request is when the load of a VNF exceeds a certain threshold, or resources.
  • the VNF requests the first VNFM to request to add resources to the VNF through the resource application message.
  • the function entity that sends the resource request message is not limited.
  • the function entity that sends the resource application message may be a VNF or an element management entity (English: element manager, EM for short) or other related resource application operation. Functional entity.
  • the first VNFM can determine the application resource according to the resource application message.
  • the application resource includes the resource amount of the application resource and the resource type of the application resource.
  • the first VNFM sends a first resource request message to the second VNFM.
  • the first VNFM sends the first resource request message according to the resource information of the remaining resources of the VIM that is connected to the first VNFM.
  • the first VNFM may check resource information of remaining resources of the VIM connected to the first VNFM.
  • the resource information of the remaining resources shown in this embodiment may include the resource amount of the remaining resources and the resource type of the remaining resources.
  • the resource type of the remaining resources determined by the first VNFM matches the resource type of the applied resource.
  • the VIM connected to the first VNFM shown in this embodiment may refer to a VIM having a relationship (eg, query, update, management, reservation, allocation, etc.) of resource information interaction with the first VNFM1.
  • the first VNFM can be physically connected to the VIM, but does not trigger a resource management relationship.
  • the present embodiment does not limit how the first VNFM specifically checks the resource information of the remaining resources of the VIM connected to the first VNFM, as long as the first VNFM can determine the resource information of the remaining resources of the VIM connected to the first VNFM. can.
  • the following is an exemplary description of the manner in which the first VNFM determines the resource information of the remaining resources of the VIM connected to the first VNFM:
  • the first VNFM stores a list of resources
  • the resource list stores resource information of the remaining resources of the VIM having the resource management relationship with the first VNFM.
  • the resource list may be directly queried.
  • the resource information of the remaining resources stored in the resource list may be from the first VNFM to the VIM.
  • the VIM connected to the first VNFM may report the resource information of the remaining resources of the VIM to the first VNFM periodically or aperiodically; or the VIM connected to the first VNFM will VIM when the trigger event is met.
  • the resource information of the remaining resources is reported to the first VNFM, and the trigger event may be an event that changes the resources managed by the VIM connected to the first VNFM.
  • the first VNFM may send a resource query message to the VIM connected to the first VNFM, so that the VIM connected to the first VNFM sends a resource response message and passes the resource.
  • the response message indicates resource information of the remaining resources of the VIM.
  • VNFs can allocate resources across VIMs. In this case, only the sum of the remaining resources of all VIMs managed by the first VNFM can be met, but some VNFs cannot allocate resources across VIMs. Then, if the remaining resources of each VIM managed by the first VNFM cannot be satisfied, the first resource request message needs to be sent.
  • the first VNFM determines that the resource quantity of the remaining resources of the VIM connected to the first VNFM is smaller than the resource quantity of the application resource, the first VNFM sends a first resource request message to pass the first resource request message, first.
  • the VNFM can request resources from other VNFMs that are connected to the first VNFM.
  • the first VNFM determines that the application resource is 4 GB vRAM, 2 vCPU, 32 GB virtual storage, and the first VNFM determines that the remaining resources of the VIM connected to the first VNFM are 2 GB vRAM, 1 vCPU, 28 GB virtual storage, and the first VNFM can be determined and The first VNFM can send the first resource request message if the VIM of the first VNFM cannot allocate the application resource.
  • steps 501 to 502 in this embodiment are optional steps, and are not limited;
  • the first VNFM may also send the first resource request message without querying the resource information of the remaining resources of the VIM connected to the first VNFM.
  • the first VNFM may also send the first resource request message if the resource request message is not received, but the resource information of the remaining resources of the VIM connected to the first VNFM cannot meet the pre-configured resource management threshold.
  • the resource management threshold can be defined as a VNFM managed resource needs to meet a certain amount, for example: the resource management threshold can be 10GB vRAM, 8vCPU, 65GB virtual storage.
  • the first resource request message includes resource information that the first VNFM is a VNF request.
  • the resource of the application shown in this embodiment is a resource that the first VNFM requests to allocate with the VIM connected to the second VNFM.
  • the resource that the first VNFM is a VNF application may be all the application resources; or the resource that the first VNFM is a VNF application may be part of the application resource.
  • the first VNFM can request resources from other VNFMs connected to the first VNFM through the first resource request message.
  • the first VNFM may divide the application resource into two parts, which are the first application resource and the second application resource, and the first application resource and the first VNFM are connected.
  • the remaining resources of the VIM are matched, and the first VNFM can allocate the first application resource through the VIM that is connected to the first VNFM.
  • the resource that the first VNFM requests from the VNF is the second application resource, that is, the first VNFM.
  • the VIM that is connected to the second VNFM is requested to allocate the second application resource by using the first resource request message.
  • the resource information of the first VNFM for the VNF application includes a resource type and a resource amount applied for the VNF;
  • the first resource request message may also carry the following information: a related policy of the applied resource, such as affinity/anti-affinity.
  • the second VNFM receives the first resource request message sent by the first VNFM.
  • the second VNFM sends a resource reservation message to the target VIM.
  • the second VNFM determines the target VIM.
  • the process by which the second VNFM determines the target VIM can be:
  • the second VNFM may query the resource information of the remaining resources of the VIM connected to the second VNFM.
  • the second VNMF determines the VIM that can allocate the applied resources in the VIM connected to the second VNFM. For the target VIM.
  • the remaining resources of the VIM4 connected to the second VNFM can allocate the requested resources, and the second VNFM can determine that the VIM4 is the target VIM.
  • the resource reservation message is not limited in this embodiment, as long as the resource reservation message can indicate that the target VIM reserves resources for the applied resource.
  • the resource reservation message includes a resource reservation identifier, and the resource reservation identifier is used to identify the resource reserved by the target VIM for allocating the applied resource.
  • the resource reservation message includes any combination of the following information, the resource reservation identifier, the identifier of the first VNFM, the identifier of the VNF that needs to allocate the resource, the type of the applied resource, the amount of the applied resource, and the related resource. Policy, the identifier of the target VIM.
  • the target VIM performs resource reservation according to the resource reservation message.
  • the target VIM sends a resource reservation feedback message to the second VNFM.
  • the second VNFM receives the resource reservation feedback message sent by the target VIM, and sends a first feedback message to the first VNFM.
  • the second VNFM can determine that the target VIM resource reservation is successful according to the resource reservation feedback message.
  • the second VNFM sends a first feedback message if the target VIM resource reservation is successful.
  • the information of the target VIM included in the first feedback message includes any combination of the following information: an identifier of the target VIM, and configuration information used to establish a connection with the target VIM.
  • the specific information included in the information of the target VIM is described as an example in the embodiment, which is not limited, as long as the first VNFM determines that the target VIM resource reservation is successful according to the first feedback message.
  • the information of the target VIM may also include information of resources reserved on the VIM, such as the type of resources and the corresponding amount of resources.
  • the first feedback message includes a resource reservation identifier.
  • the first VNFM receives the first feedback message.
  • the first VNFM establishes a connection between the first VNFM and the target VIM.
  • the first VNFM may establish a connection with the target VIM according to the first feedback message; more specifically, the first VNFM may establish a connection with the target VIM according to the information of the target VIM included in the first feedback message.
  • the identifier and/or configuration information of the target VIM may be sent by the second VNFM to the first VNFM without using the first feedback message.
  • step 510 if the first VNFM has been connected to the target VIM, step 510 is not required;
  • the step 510 for establishing the connection of the first VNFM to the target VIM is only An example, which is not limited, for example, the first VNFM may also obtain configuration information from the NFVO connected to the first VNFM.
  • the configuration information is not limited in this embodiment, as long as the first VNFM can establish a connection between the first VNFM and the target VIM according to the configuration information;
  • the configuration information includes: an IP address of the target VIM;
  • the configuration information may include any combination of the following information: a uniform resource locator of the target VIM (English: uniform resource locator, abbreviation: URL), a username of the target VIM, and an authentication password of the target VIM.
  • a uniform resource locator of the target VIM English: uniform resource locator, abbreviation: URL
  • a username of the target VIM and an authentication password of the target VIM.
  • the first VNFM sends a first resource allocation message to the target VIM.
  • the first resource allocation message is used by the target VIM to allocate the requested resource according to the first resource allocation message.
  • the first resource allocation message includes a resource reservation identifier.
  • the target VIM allocates the applied resource according to the first resource allocation message.
  • VIM performs resource allocation based on previously reserved resource information, including starting a virtual machine (VM).
  • VM virtual machine
  • the target VIM sends a resource allocation feedback message to the first VNFM.
  • the target VIM may determine, according to the resource reservation identifier included in the first resource allocation message, that the reserved resource is used for allocation of the applied resource;
  • the target VIM can allocate the requested resources through the reserved resources.
  • the target VIM may notify the first VNFM application that the resource has been successfully allocated through the resource allocation feedback message.
  • the first VNFM may also allocate a resource to the NFVO feedback resource connected to the first VNFM.
  • the first VNFM may also perform operations on the related VNF related configuration; for example, if the resource request message is a VNF instantiation request, the first VNFM is VNF Parameter configuration is performed; if the resource request message is a VNF extension request, the first VNFM performs parameter configuration update on the VNF.
  • a resource management network is formed between the first VNFM and the second VNFM, so that resources can be processed between the VNFMs.
  • resource query and resource allocation and in the specific process, NFVO participation is not required, thus avoiding the impact of NFVO failure on the network, implementing a distributed resource management method, and then in the event of NFVO failure, second VNFM can still reserve or allocate resources for application, which effectively improves the robustness and efficiency of the network.
  • FIG. 5 is a third embodiment of the present invention, where the second VNFM reserves resources for the first VNFM to apply for the VNF, and the first VNFM allocates resources to the applied resources, and the following describes the fourth embodiment shown in FIG. 6 .
  • the second VNFM is how to allocate resources for the applied resources.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the first VNFM receives the resource application message.
  • the first VNFM sends a first resource request message to the second VNFM.
  • the second VNFM receives the first resource request message sent by the first VNFM.
  • step 501 to step 603 in this embodiment is shown in FIG. 5, which is shown in FIG. 5, and is not shown in detail in this embodiment.
  • the second VNFM sends a second resource allocation message to the target VIM.
  • the second resource allocation message may include any combination of the following information, the type of the applied resource, the amount of the applied resource, and the related policy of the applied resource.
  • the target VIM performs resource allocation according to the second resource allocation message.
  • the target VIM sends a resource allocation feedback message to the second VNFM.
  • the target VIM may notify the resource that the second VNFM application has been successfully allocated by using the resource allocation feedback message.
  • the resource allocation feedback message may include the identifier of the target VIM and some configuration parameters, such as the location of the allocated resource, connection information, and the like.
  • the second VNFM sends a first feedback message to the first VNFM.
  • the first feedback message contains information of the target VIM to which the resource is allocated for the first VNFM, such as the identity of the target VIM, and information of the resources allocated on the target VIM.
  • the information of the allocated resources includes the type of resources allocated and the amount of resources allocated.
  • the first feedback message may further include any combination of the following information: an identifier of the target virtual machine VM allocated by the target VIM, and location information of the target VM.
  • the first VNFM determines, according to the first resource allocation feedback message, that the applied resource has been successfully allocated by the target VIM.
  • the first VNFM may also allocate a NFVO feedback resource to the first VNFM;
  • the first VNFM may also perform operations on the related VNF related configuration. For example, if the resource request message is a VNF instantiation request, the first VNFM performs parameter configuration on the VNF; if the resource request message is a VNF extension request, the first VNFM performs parameter configuration update on the VNF.
  • a resource management network is formed between the first VNFM and the second VNFM, so that resource processing, such as resource query and resource allocation, can be performed between the VNFMs, and
  • resource processing such as resource query and resource allocation
  • NFVO participation is not required, thereby avoiding the impact of NFVO failure on the network and implementing a distributed resource management mode, so that when the NFVO fails, the second VNFM can still reserve the applied resources. Or allocation, effectively improving the robustness and efficiency of the network.
  • the third embodiment shown in FIG. 5 and the fourth embodiment shown in FIG. 6 illustrate how the network function virtualization resource processing method is implemented when the resource of the target VIM connected to the second VNFM satisfies the applied resource information.
  • the fifth embodiment shown in FIG. 7 illustrates how the network function virtualization resource processing method is implemented when the resource of the target VIM connected to the second VNFM cannot satisfy the applied resource information.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • the first VNFM receives a resource application message.
  • the first VNFM sends a first resource request message to the second VNFM.
  • the second VNFM receives the first resource request message sent by the first VNFM.
  • step 701 to step 703 shown in this embodiment is shown in the steps 501 to 503 shown in FIG. 5 , and is not described in detail in this embodiment.
  • the second VNFM determines that the resource of the target VIM that is connected to the second VNFM cannot meet the resource information of the application.
  • the second VNFM may query resource information of the remaining resources of the target VIM that is connected to the second VNFM.
  • the target VIM connected to the second VNFM cannot allocate the requested resources.
  • the amount of resources of the remaining resources of the target VIM is smaller than the amount of resources requested.
  • the second feedback message is used to indicate that the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application.
  • the second feedback message further includes resource information of remaining resources of the target VIM connected to the second VNFM;
  • the resource information of the remaining resources of the target VIM includes the resource type of the remaining resources and the resource amount of the remaining resources.
  • the first VNFM receives the second feedback message.
  • the first VNFM determines, according to the second feedback message, that the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application, the first VNFM may continue to perform step 707 or step 708;
  • the first VNFM sends the first resource request message to the third VNMF that is connected to the first VNMF. If the resource of the VIM connected to the third VNFM cannot satisfy the applied resource information, the first VNFM will be the first.
  • the request message is sent to other VNFMs connected to the first VNFM until the first resource request message is sent to the VNFM that satisfies the requested resource information.
  • the first VNFM requests the VIM connected to the third VNFM to reserve or allocate the applied resource.
  • the first VNFM may send the first resource request message to all VNFMs connected to the first VNFM, thereby selecting a VNFM that satisfies the requested resource information.
  • the specific implementation process of reserving or allocating the applied resources by the VIM connected to the third VNFM is as follows: the process of reserving or allocating the applied resources by the target VIM connected to the second VNFM as shown in the foregoing, I will not repeat them here.
  • the first VNFM can trigger the target VIM connected to the second VNFM to reserve or allocate a part of the requested resource. For details, refer to steps 708 to 713.
  • the first VNFM sends a first resource request message to the third VNMF.
  • the first VNFM sends a second resource request message to the second VNFM.
  • the second resource request message includes resource information of the re-allocated resource
  • the re-allocation resource is a resource that matches the remaining resources among the applied resources
  • the resource amount of the re-allocated resource is less than or equal to the resource amount of the remaining resource
  • the resource information of the re-allocated resource includes a resource type of the re-allocated resource and a resource amount of the re-allocated resource.
  • the second VNFM receives the first VNFM and sends a second resource request message.
  • the second VNFM control target VIM reserves or allocates reconfiguration resources.
  • the second VNFM reserves or allocates the reconfiguration resource according to the second resource request message.
  • the process of reserving the re-allocated resource by the second VNFM may be referred to the process of reserving the applied resource by the second VNFM shown in FIG. 4, specifically in the implementation. None will be repeated in the example.
  • the process of allocating the re-allocated resource by the second VNFM may be referred to the process of allocating the applied resource by the second VNFM shown in FIG. 5, which is not in this embodiment. Make a statement.
  • the second VNFM sends a third feedback message to the first VNFM.
  • the third feedback message contains information of the VIM that is reserved or allocated resources for the reconfiguration resource.
  • the first VNFM requests resources from other VNFMs connected to the first VNFM until the resource allocation of the application is completed.
  • the applied resources are allocated through multiple VNFMs connected to the first VNFM.
  • a resource management network is formed between the first VNFM and the second VNFM, so that resource processing, such as resource query and resource allocation, can be performed between the VNFMs, and
  • resource processing such as resource query and resource allocation
  • NFVO participation is not required, thereby avoiding the impact of NFVO failure on the network and implementing a distributed resource management mode, so that when the NFVO fails, the second VNFM can still reserve the applied resources. Or allocation, effectively improving the robustness and efficiency of the network.
  • VNFM virtual network function manager
  • the VNFM shown in this embodiment is used to implement the method performed by the first VNFM in FIG. 3 and FIG. 5-7.
  • VNFM includes:
  • the sending unit 801 is configured to send a first resource request message to the second VNFM, where the first resource request message includes resource information that the VNFM requests for the virtual network function VNF.
  • the receiving unit 802 is configured to: when the resource of the target virtualization infrastructure manager VIM connected to the second VNFM meets the requested resource information, receive the first feedback message sent by the second VNFM, where the first feedback message is reserved for the VNFM Or information about the target VIM to which the resource is assigned.
  • the second VNFM shown in this embodiment is a VNFM interconnected with the VNFM provided in this embodiment.
  • the specific number of the sending unit 801 and the receiving unit 802 is not limited, that is, the sending unit 801 may be one or more, and the receiving unit 802 may be one or more.
  • the VNFM in this embodiment further includes: a determining unit 803;
  • the determining unit 803 is configured to determine that the first feedback message includes information of the target VIM in which the resource is reserved for the VNFM.
  • the sending unit 801 is further configured to: when the first feedback message includes the information of the target VIM in which the resource is reserved for the VNFM, send the first resource allocation message to the target VIM, where the first resource allocation message is used by the target VIM Resources are allocated.
  • the first feedback message received by the receiving unit 802 includes a resource reservation identifier.
  • the first resource allocation message sent by the sending unit 801 includes a resource reservation identifier, where the resource reservation identifier is used to identify the reserved resource.
  • the determining unit 803 is further configured to determine that the first feedback message includes information of the target VIM to which the resource is allocated for the VNFM, and the first feedback message further includes any combination of the following information: The identifier of the target virtual machine VM allocated by the target VIM, and the location information of the target VM.
  • the information of the target VIM received by the receiving unit 802 includes any combination of the following information: an identifier of the target VIM, and configuration information for establishing a connection with the target VIM.
  • the receiving unit 802 is further configured to: when the resource of the target VIM connected to the second VNFM cannot meet the applied resource information, receive the second VNFM, if the resource of the VIM that is connected to the second VNFM cannot meet the resource information of the application. Second feedback message.
  • the second feedback message is used to indicate that the resource of the target VIM connected to the second VNFM cannot meet the application Please ask for resource information.
  • the second feedback message received by the receiving unit 802 further includes resource information of the remaining resources of the target VIM connected to the second VNFM, where the resource information of the remaining resources includes the resource type of the remaining resources and the resource amount of the remaining resources.
  • the sending unit 801 is further configured to send a second resource request message to the second VNFM, where the second resource request message includes resource information of the reconfiguration resource, where the remaining resource is used by the target VIM to reserve or allocate a reconfiguration resource for the VNFM.
  • the resource information of the application sent by the sending unit 801 includes the resource type of the application and the amount of resources requested.
  • VNFM virtual network function manager
  • the VNFM shown in this embodiment is used to implement the method performed by the second VNFM in FIG. 4-7.
  • VNFM includes:
  • the receiving unit 901 is configured to receive a first resource request message sent by the first VNFM, where the first resource request message includes resource information that the first VNFM requests for the virtual network function VNF.
  • the determining unit 902 is configured to determine that the resource of the target virtualization infrastructure manager VIM connected to the VNFM satisfies the requested resource information.
  • the sending unit 903 is configured to: when the resource of the target virtualization infrastructure manager VIM connected to the VNFM satisfies the requested resource information, send the first feedback message to the first VNFM, where the first feedback message is reserved for the first VNFM Or information about the target VIM to which the resource is assigned.
  • the first VNFM shown in this embodiment is a VNFM connected to the VNFM provided in this embodiment.
  • the specific number of the receiving unit 901, the determining unit 902, and the sending unit 903 is not limited, that is, the receiving unit 901 may be one or more, and the determining unit 902 may be one or more.
  • the transmitting unit 903 can be one or more.
  • the sending unit 903 is further configured to send a resource reservation message to the target VIM.
  • the receiving unit 901 is further configured to receive a resource reservation feedback message sent by the target VIM.
  • the resource reservation message sent by the sending unit 903 includes a resource reservation identifier.
  • the first feedback message sent by the sending unit 903 includes a resource reservation identifier, and the resource reservation identifier is used.
  • the resources reserved for identifying the target VIM are used to allocate the requested resources.
  • the sending unit 903 is further configured to send a second resource allocation message to the target VIM.
  • the receiving unit 901 is further configured to receive a resource allocation feedback message sent by the target VIM.
  • the first feedback message sent by the sending unit 903 further includes any combination of the following information: an identifier of the target virtual machine VM allocated by the target VIM, and location information of the target VM allocated by the target VIM.
  • the information of the target VIM included in the first feedback message sent by the sending unit 903 includes any combination of the following information: an identifier of the target VIM, and configuration information for establishing a connection with the target VIM.
  • the determining unit 902 is further configured to determine that the resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application.
  • the sending unit 903 is configured to: when the resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application, send a second feedback message to the first VNFM, where the second feedback message is used to indicate that the resource of the target VIM connected to the VNFM cannot be met. Resource information requested.
  • the second feedback message sent by the sending unit 903 includes resource information of the remaining resources of the target VIM connected to the VNFM, and the resource information of the remaining resources includes the resource type of the remaining resources and the resource amount of the remaining resources.
  • the receiving unit 901 is further configured to receive a second resource request message sent by the first VNFM, where the second resource request message includes resource information of the reconfiguration resource, where the remaining resource is used for the target VIM to reserve or allocate the first VNFM. With resources.
  • the resource information of the application received by the receiving unit 901 includes the resource type of the application and the amount of resources requested.
  • An eighth embodiment of the present invention provides a virtual network function manager VNFM.
  • the virtual network function manager VNFM in this embodiment can perform the operations of the first VNFM in the methods shown in FIG. 3 and FIG. 5 to FIG.
  • the VNFM of this embodiment includes: a transmitter 1001 and a receiver 1002;
  • the transmitter 1001 and the receiver 1002 are connected by a bus.
  • other connection manners may be used.
  • the specific connection manner is not limited in this embodiment.
  • the VNFM may have more or less components than those shown in FIG. 10, may combine two or more components, or may have different component configurations or settings, and each component may include one Hardware, software, or a combination of hardware and software, including multiple signal processing and/or application specific integrated circuits.
  • the sender 1001 is configured to send a first resource request message to the second VNFM, where the first resource request message includes resource information that the VNFM requests for the virtual network function VNF.
  • the receiver 1002 is configured to: when the resource of the target virtualization infrastructure manager VIM connected to the second VNFM meets the resource information of the application, receive the first feedback message sent by the second VNFM, where the first feedback message is reserved for the VNFM Or information about the target VIM to which the resource is assigned.
  • the specific number of the transmitter 1001 and the receiver 1002 is not limited in this embodiment, that is, the number of the transmitters 1001 may be one or more, and the number of the receivers 1002 may be one or more.
  • the VNFM further includes a processor 1003;
  • the processor 1003 may be one or more. One embodiment is described in this embodiment.
  • the transmitter 1001, the receiver 1002, and the processor 1003 are connected through a bus.
  • other connection manners may be used.
  • the specific connection manner is not limited in this embodiment.
  • the processor 1003 is configured to determine that the first feedback message includes information of a target VIM that reserves resources for the VNFM.
  • the transmitter 1001 is further configured to: when the first feedback message includes the information of the target VIM in which the resource is reserved for the VNFM, send a first resource allocation message to the target VIM, where the first resource allocation message is used by the target VIM to apply for the requested resource. distribution.
  • the first feedback message received by the receiver 1002 includes a resource reservation identifier
  • the first resource allocation message sent by the sender 1001 includes a resource reservation identifier, where the resource reservation identifier is used to identify the reserved resource.
  • the processor 1003 is configured to determine that the first feedback message includes information about a target VIM to which a resource is allocated for the VNFM, where the first feedback message further includes any combination of the following information: the target virtual machine VM allocated by the target VIM. Identification, location information of the target VM.
  • the information of the target VIM received by the receiver 1002 includes any combination of the following information:
  • the identifier of the target VIM which is used to establish configuration information for establishing a connection with the target VIM.
  • the receiver 1002 is further configured to: when the resource of the target VIM connected to the second VNFM cannot meet the resource information of the application, receive the second feedback message sent by the second VNFM;
  • the second feedback message is used to indicate that the resource of the target VIM connected to the second VNFM cannot satisfy the resource information of the application.
  • the second feedback message received by the receiver 1002 further includes resource information of a remaining resource of the target VIM connected to the second VNFM, where the resource information of the remaining resource includes a resource type of the remaining resource and a resource amount of the remaining resource.
  • the sender 1001 is further configured to send a second resource request message to the second VNFM, where the second resource request message includes resource information of the reconfiguration resource, where the remaining resource is used for the target VIM to reserve or allocate the reconfiguration resource for the VNFM. .
  • the resource information of the application sent by the sender 1001 includes the resource type of the application and the amount of resources requested.
  • the NFVM of the embodiment may further include a memory, where the computer stores executable instructions for instructing the processor 1003 to cooperate with the transmitter 1001 and the receiver 1002 to complete FIG. 3, FIG. 5 to FIG. The operation of the first VNFM in the illustrated method.
  • Embodiment 9 of the present invention provides a virtual network function manager VNFM.
  • the virtual network function manager VNFM in this embodiment can perform the operations of the second VNFM in the methods shown in FIGS. 4 to 7.
  • the VNFM of this embodiment includes: a transmitter 1101, a receiver 1102, and a processor 1103;
  • the VNFM may have more or less components than those shown in FIG. 11, may combine two or more components, or may have different component configurations or settings, and each component may include one Hardware, software, or a combination of hardware and software, including multiple signal processing and/or application specific integrated circuits.
  • the transmitter 1101, the receiver 1102, and the processor 1103 may be one or more.
  • the transmitter 1101, the receiver 1102, and the processor 1103 are connected through a bus.
  • other connection manners may be used.
  • the specific connection manner is not limited in this embodiment.
  • the receiver 1102 is configured to receive a first resource request message sent by the first VNFM, where the first resource is The request message includes resource information that the first VNFM applies for the virtual network function VNF.
  • the processor 1103 is configured to determine that the resource of the target virtualization infrastructure manager VIM connected to the VNFM satisfies the resource information of the application.
  • the sender 1101 is configured to: when the resource of the target virtualization infrastructure manager VIM connected to the VNFM satisfies the requested resource information, send a first feedback message to the first VNFM, where the first feedback message is reserved for the first VNFM Or information about the target VIM to which the resource is assigned.
  • the transmitter 1101 is further configured to send a resource reservation message to the target VIM.
  • the receiver 1102 is further configured to receive a resource reservation feedback message sent by the target VIM.
  • the resource reservation message sent by the sender 1101 includes a resource reservation identifier
  • the first feedback message sent by the transmitter 1101 includes a resource reservation identifier, where the resource reservation identifier is used to identify the resource reserved by the target VIM. Used to allocate resources for the application.
  • the transmitter 1101 is further configured to send a second resource allocation message to the target VIM.
  • the receiver 1102 is further configured to receive a resource allocation feedback message sent by the target VIM.
  • the first feedback message sent by the transmitter 1101 further includes any combination of the following information: an identifier of the target virtual machine VM allocated by the target VIM, and location information of the target VM allocated by the target VIM.
  • the information of the target VIM included in the first feedback message sent by the sender 1101 includes any combination of the following information:
  • the identifier of the target VIM which is used to establish configuration information for establishing a connection with the target VIM.
  • the processor 1103 is further configured to determine that the resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application.
  • the transmitter 1101 is further configured to: when the resource of the target VIM connected to the VNFM cannot satisfy the resource information of the application, send a second feedback message to the first VNFM, where the second feedback message is used to indicate that the resource of the target VIM connected to the VNFM cannot be used. Meet the resource information of the application.
  • the second feedback message sent by the transmitter 1101 includes resource information of the remaining resources of the target VIM that is connected to the VNFM, and the resource information of the remaining resources includes the resource type of the remaining resources and the resource amount of the remaining resources.
  • the receiver 1102 is further configured to receive a second resource request message sent by the first VNFM, where the second resource request message includes resource information of the reconfiguration resource, where the remaining resource is used for the target VIM.
  • the VNFM reserves or allocates reconfiguration resources.
  • the resource information of the application received by the receiver 1102 includes the requested resource type and the requested resource amount.
  • the NFVM of the embodiment may further include a memory, where the computer stores executable instructions for instructing the processor 1103 to cooperate with the transmitter 1101 and the receiver 1102 to complete the operations shown in FIG. 4 to FIG. 7. The operation of the second VNFM in the method.

Landscapes

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

Abstract

本发明提供了一种网络功能虚拟化资源处理方法及虚拟网络功能管理器，第一VNFM无需经过NFVO，而是将用于请求资源的第一资源请求消息发送给与所述第一VNFM连接的第二VNFM，在与所述第二VNFM连接的目标VIM的资源满足申请的资源信息时，所述第一VNFM根据已接收到的第一反馈消息确定能够对申请的资源进行预留或者进行分配的目标VIM的信息。所述第一VNFM和所述第二VNFM之间形成一个资源管理网络，从而相互连接的VNFM之间通过接口可进行资源的处理，例如资源查询和资源分配等，且无需NFVO的参与，从而避免了若NFVO出现故障对网络的影响，实现了分布式的资源管理方式，进而在NFVO出现故障时，所述第一VNFM仍然能够对申请的资源进行管理，有效的提高了网络的健壮性和效率。

Description

一种网络功能虚拟化资源处理方法及虚拟网络功能管理器 技术领域
本发明涉及网络功能虚拟化领域，尤其涉及的是一种网络功能虚拟化资源处理方法及虚拟网络功能管理器。
背景技术
随着云技术的发展，虚拟化技术作为云计算的基础技术，在企业数据中心、大规模集群计算领域得到大规模使用。网络功能虚拟化(英文：Network Functions Virtualization，简称：NFV)技术通过借用信息技术(英文：Information Technology，简称：IT)的虚拟化技术，使得许多类型的网络设备可以合并到工业标准中，例如：服务、交换、存储等可以部署在数据中心或者网络节点中。将各种网络功能以软件方式实现，并能在工业标准的服务器上运行，并还能根据需要进行迁移、实例化、以及重新部署等等，并不需要安装新的设备，即产生虚拟网络功能(英文：Virtualized Network Function，简称：VNF)。多个虚拟网络功能之间可以实现网络业务(英文：Network Service，简称：NS)。在NFV网络架构中，一个NFV编排器(英文：NFV Orchestrator，简称：NFVO)可以管理多个虚拟网络功能管理器(英文：VNF Manager，简称VNFM)，一个VNFM可以管理多个VNF，NFVO控制多个VIM资源的管理和分配。
申请人发现，现有技术的资源的分配管理都要经过NFVO，若出现NFVO单点故障时，则会产生较大的网络影响。
发明内容
本发明实施例提供了在资源分配管理时能够提高网络的健壮性和效率的网络功能虚拟化资源处理方法及虚拟网络功能管理器。
本发明实施例第一方面提供了一种网络功能虚拟化资源处理方法，包括：
第一虚拟网络功能管理器VNFM向第二VNFM发送第一资源请求消息，所述第一资源请求消息包含所述第一VNFM为虚拟网络功能VNF申请的资源信息；
当与所述第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足 所述申请的资源信息时，所述第一VNFM接收所述第二VNFM发送的第一反馈消息,所述第一反馈消息包含为所述第一VNFM预留或者分配了资源的所述目标VIM的信息。
结合本发明实施例第一方面，本发明实施例第一方面的第一种实现方式中，
当所述第一反馈消息包含为所述第一VNFM预留了资源的所述目标VIM的信息时，所述第一VNFM接收所述第二VNFM发送的第一反馈消息之后，所述方法还包括：
所述第一VNFM向所述目标VIM发送第一资源分配消息，所述第一资源分配消息用于所述目标VIM对所述申请的资源进行分配。
结合本发明实施例第一方面的第一种实现方式，本发明实施例第一方面的第二种实现方式中，
所述第一反馈消息包含资源预留标识，所述第一资源分配消息包含所述资源预留标识，所述资源预留标识用于标识所述预留的资源。
结合本发明实施例第一方面，本发明实施例第一方面的第三种实现方式中，
当所述第一反馈消息包含为所述第一VNFM分配了资源的所述目标VIM的信息时，所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VIM所分配的目标VM的位置信息。
结合本发明实施例第一方面至本发明实施例第一方面的第三种实现方式，本发明实施例第一方面的第四种实现方式中，
所述目标VIM的信息包括以下信息的任意组合：
所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
结合本发明实施例第一方面，本发明实施例第一方面的第五种实现方式中，
所述方法还包括：当与所述第二VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，所述第一VNFM接收所述第二VNFM发送的第二反馈消息；
所述第二反馈消息用于指示与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
结合本发明实施例第一方面的第五种实现方式，本发明实施例第一方面的第六种实现方式中，
所述第二反馈消息包含与所述第二VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
结合本发明实施例第一方面的第六种实现方式，本发明实施例第一方面的第七种实现方式中，
所述方法还包括：
所述第一VNFM向所述第二VNFM发送第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述第一VNFM预留或者分配所述重配资源。
结合本发明实施例第一方面至本发明实施例第一方面的第七种实现方式任一项所述的方法，本发明实施例第一方面的第八种实现方式中，
所述申请的资源信息包括申请的资源类型和申请的资源量。
本发明实施例第二方面提供了一种网络功能虚拟化资源处理方法，包括：
第二VNFM接收第一VNFM发送的第一资源请求消息，所述第一资源请求消息包含所述第一VNFM为虚拟网络功能VNF申请的资源信息；
当与所述第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，所述第二VNFM向所述第一VNFM发送的第一反馈消息，所述第一反馈消息包含为所述第一VNFM预留或者分配了资源的所述目标VIM的信息。
结合本发明实施例第二方面，本发明实施例第二方面的第一种实现方式中，
所述第二VNFM向所述第一VNFM发送第一反馈消息之前，所述方法还包括：
所述第二VNFM向所述目标VIM发送资源预留消息；
所述第二VNFM接收所述目标VIM发送的资源预留反馈消息。
结合本发明实施例第二方面的第一种实现方式，本发明实施例第二方面的第二种实现方式中，
所述资源预留消息包含资源预留标识，所述第一反馈消息包含所述资源预留标识，所述资源预留标识用于标识所述预留的资源。
结合本发明实施例第二方面，本发明实施例第二方面的第三种实现方式中，
所述第二VNFM向所述第一VNFM发送第一反馈消息之前，所述方法还包括：
所述第二VNFM向所述目标VIM发送第二资源分配消息；
所述第二VNFM接收所述目标VIM发送的资源分配反馈消息。
结合本发明实施例第二方面，本发明实施例第二方面的第四种实现方式中，
所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VIM所分配的目标VM的位置信息。
结合本发明实施例第二方面至本发明实施例第二方面的第四种实现方式任一项所述的方法，本发明实施例第二方面的第五种实现方式中，
所述目标VIM的信息包括以下信息的任意组合：
所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
结合本发明实施例第二方面，本发明实施例第二方面的第六种实现方式中，
所述方法还包括：当与所述第二VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，所述第二VNFM向所述第一VNFM发送第二反馈消息；
所述第二反馈消息用于指示与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
结合本发明实施例第二方面的第六种实现方式，本发明实施例第二方面的第七种实现方式中，
当与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息时，所述第二反馈消息包含与所述第二VNFM连接的所述目标VIM的 剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
结合本发明实施例第二方面的第七种实现方式，本发明实施例第二方面的第八种实现方式中，
所述方法还包括：
所述第二VNFM接收所述第一VNFM发送第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述第一VNFM预留或者分配所述重配资源。
结合本发明实施例第二方面至本发明实施例第二方面的第八种实现方式任一项所述的方法，本发明实施例第二方面的第九种实现方式中，
所述申请的资源信息包括申请的资源类型和申请的资源量。
本发明实施例第三方面提供了一种虚拟网络功能管理器VNFM，包括：
发送单元，用于向第二VNFM发送第一资源请求消息，所述第一资源请求消息包含所述VNFM为虚拟网络功能VNF申请的资源信息；
接收单元，用于当与所述第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，接收所述第二VNFM发送的第一反馈消息,所述第一反馈消息包含为所述VNFM预留或者分配了资源的所述目标VIM的信息。
结合本发明实施例的第三方面，本发明实施例的第三方面的第一种实现方式中，所述VNFM还包括：
确定单元，用于确定所述第一反馈消息包含为所述VNFM预留了资源的所述目标VIM的信息；
所述发送单元，还用于当所述第一反馈消息包含为所述VNFM预留了资源的所述目标VIM的信息时，向所述目标VIM发送第一资源分配消息，所述第一资源分配消息用于所述目标VIM对所述申请的资源进行分配。
结合本发明实施例的第三方面的第一种实现方式，本发明实施例的第三方面的第二种实现方式中，
所述接收单元接收的所述第一反馈消息包含资源预留标识，所述发送单元所发送的第一资源分配消息包含所述资源预留标识，所述资源预留标识用于标 识所述预留的资源。
结合本发明实施例第三方面，本发明实施例的第三方面的第三种实现方式中，
所述VNFM还包括：确定单元，用于确定所述第一反馈消息包含为所述VNFM分配了资源的所述目标VIM的信息，所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VM的位置信息。
结合本发明实施例第三方面至本发明实施例的第三方面的第三种实现方式任一项所述的VNFM，本发明实施例的第三方面的第四种实现方式中，
所述接收单元接收到的所述目标VIM的信息包括以下信息的任意组合：
所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
结合本发明实施例第三方面，本发明实施例的第三方面的第五种实现方式中，
所述接收单元，还用于当与所述第二VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，接收所述第二VNFM发送的第二反馈消息；
所述第二反馈消息用于指示与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
结合本发明实施例的第三方面的第五种实现方式，本发明实施例的第三方面的第六种实现方式中，
所述接收单元接收到的所述第二反馈消息还包含与所述第二VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
结合本发明实施例的第三方面的第六种实现方式，本发明实施例的第三方面的第七种实现方式中，
所述发送单元，还用于向所述第二VNFM发送第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述VNFM预留或者分配所述重配资源。
结合本发明实施例的第三方面至本发明实施例的第三方面的第七种实现方式任一项所述的VNFM，本发明实施例的第三方面的第八种实现方式中，
所述发送单元发送的所述申请的资源信息包括申请的资源类型和申请的资源量。
本发明实施例第四方面提供了一种虚拟网络功能管理器VNFM，包括：
接收单元，用于接收第一VNFM发送的第一资源请求消息，所述第一资源请求消息包含所述第一VNFM为虚拟网络功能VNF申请的资源信息；
确定单元，用于确定与所述VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息；
发送单元，用于当与所述VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，向所述第一VNFM发送的第一反馈消息，所述第一反馈消息包含为所述第一VNFM预留或者分配了资源的所述目标VIM的信息。
结合本发明实施例第四方面，本发明实施例第四方面的第一种实现方式中，
所述VNFM还包括：
所述发送单元，还用于向所述目标VIM发送资源预留消息；
所述接收单元，还用于接收所述目标VIM发送的资源预留反馈消息。
结合本发明实施例第四方面的第一种实现方式，本发明实施例第四方面的第二种实现方式中，
所述发送单元所发送的所述资源预留消息包含资源预留标识，所述发送单元所发送的所述第一反馈消息包含所述资源预留标识，所述资源预留标识用于标识所述目标VIM所预留的资源用于对所述申请的资源进行分配。
结合本发明实施例第四方面，本发明实施例第四方面的第三种实现方式中，
所述VNFM还包括：
所述发送单元，还用于向所述目标VIM发送第二资源分配消息；
所述接收单元，还用于接收所述目标VIM发送的资源分配反馈消息。
结合本发明实施例第四方面，本发明实施例第四方面的第四种实现方式中，
所述发送单元所发送的所述第一反馈消息还包括以下信息中的任意组合： 所述目标VIM所分配的目标虚拟机VM的标识，所述目标VIM所分配的目标VM的位置信息。
结合本发明实施例第四方面至本发明实施例第四方面的第四种实现方式任一项所述的VNFM，本发明实施例第四方面的第五种实现方式中，
所述发送单元所发送的所述第一反馈消息所包括的所述目标VIM的信息包括以下信息的任意组合：
所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
结合本发明实施例第四方面，本发明实施例第四方面的第六种实现方式中，
所述确定单元，还用于确定与所述VNFM连接的目标VIM的资源不能满足所述申请的资源信息；
所述发送单元，还用于当与所述VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，向所述第一VNFM发送第二反馈消息，所述第二反馈消息用于指示与所述VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
结合本发明实施例第四方面的第六种实现方式，本发明实施例第四方面的第七种实现方式中，
所述发送单元所发送的所述第二反馈消息包含与所述VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
结合本发明实施例第四方面的第七种实现方式，本发明实施例第四方面的第八种实现方式中，
所述接收单元，还用于接收所述第一VNFM发送的第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述第一VNFM预留或者分配所述重配资源。
结合本发明实施例第四方面至本发明实施例第四方面的第八种实现方式任一项所述的VNFM，本发明实施例第四方面的第九种实现方式中，
所述接收单元接收到的所述申请的资源信息包括申请的资源类型和申请的资源量。
本发明实施例第五方面提供了一种虚拟网络功能管理器VNFM，包括：
发送器，用于向第二VNFM发送第一资源请求消息，所述第一资源请求消息包含所述VNFM为虚拟网络功能VNF申请的资源信息；
接收器，用于当与所述第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，接收所述第二VNFM发送的第一反馈消息,所述第一反馈消息包含为所述VNFM预留或者分配了资源的所述目标VIM的信息。
结合本发明实施例第五方面，本发明实施例第五方面的第一种实现方式中，
所述VNFM还包括处理器；
所述处理器，用于确定所述第一反馈消息包含为所述VNFM预留了资源的所述目标VIM的信息；
所述发送器，还用于当所述第一反馈消息包含为所述VNFM预留了资源的所述目标VIM的信息时，向所述目标VIM发送第一资源分配消息，所述第一资源分配消息用于所述目标VIM对所述申请的资源进行分配。
结合本发明实施例第五方面的第一种实现方式，本发明实施例第五方面的第二种实现方式中，
所述接收器接收的所述第一反馈消息包含资源预留标识，所述发送器所发送的第一资源分配消息包含所述资源预留标识，所述资源预留标识用于标识所述预留的资源。
结合本发明实施例第五方面，本发明实施例第五方面的第三种实现方式中，
所述VNFM还包括处理器；
所述处理器，用于确定所述第一反馈消息包含为所述VNFM分配了资源的所述目标VIM的信息，所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VM的位置信息。
结合本发明实施例第五方面至本发明实施例第五方面的第三种实现方式，本发明实施例第五方面的第四种实现方式中，
所述接收器接收到的所述目标VIM的信息包括以下信息的任意组合：
所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
结合本发明实施例第五方面，本发明实施例第五方面的第五种实现方式中，
所述接收器，还用于当与所述第二VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，接收所述第二VNFM发送的第二反馈消息；
所述第二反馈消息用于指示与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
结合本发明实施例第五方面的第五种实现方式，本发明实施例第五方面的第六种实现方式中，
所述接收器接收到的所述第二反馈消息还包含与所述第二VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
结合本发明实施例第五方面的第六种实现方式，本发明实施例第五方面的第七种实现方式中，
所述发送器，还用于向所述第二VNFM发送第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述VNFM预留或者分配所述重配资源。
结合本发明实施例第五方面至本发明实施例第五方面的第七种实现方式任一项所述的VNFM，本发明实施例第五方面的第八种实现方式中，
所述发送器发送的所述申请的资源信息包括申请的资源类型和申请的资源量。
本发明实施例第六方面提供了一种虚拟网络功能管理器VNFM，包括：
接收器，用于接收第一VNFM发送的第一资源请求消息，所述第一资源请求消息包含所述第一VNFM为虚拟网络功能VNF申请的资源信息；
处理器，用于确定与所述VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息；
发送器，用于当与所述VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，向所述第一VNFM发送的第一反馈消息，所述第一反馈消息包含为所述第一VNFM预留或者分配了资源的所述目标 VIM的信息。
结合本发明实施例第六方面，本发明实施例第六方面的第一种实现方式中，
所述发送器，还用于向所述目标VIM发送资源预留消息；
所述接收器，还用于接收所述目标VIM发送的资源预留反馈消息。
结合本发明实施例第六方面的第一种实现方式，本发明实施例第六方面的第二种实现方式中，
所述发送器所发送的所述资源预留消息包含资源预留标识，所述发送器所发送的所述第一反馈消息包含所述资源预留标识，所述资源预留标识用于标识所述目标VIM所预留的资源用于对所述申请的资源进行分配。
结合本发明实施例第六方面，本发明实施例第六方面的第三种实现方式中，
所述发送器，还用于向所述目标VIM发送第二资源分配消息；
所述接收器，还用于接收所述目标VIM发送的资源分配反馈消息。
结合本发明实施例第六方面，本发明实施例第六方面的第四种实现方式中，
所述发送器所发送的所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VIM所分配的目标VM的位置信息。
结合本发明实施例第六方面至本发明实施例第六方面的第四种实现方式任一项所述的VNFM，本发明实施例第六方面的第五种实现方式中，
所述发送器所发送的所述第一反馈消息所包括的所述目标VIM的信息包括以下信息的任意组合：
所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
结合本发明实施例第六方面，本发明实施例第六方面的第六种实现方式中，
所述处理器，还用于确定与所述VNFM连接的目标VIM的资源不能满足所述申请的资源信息；
所述发送器，还用于当与所述VNFM连接的目标VIM的资源不能满足所 述申请的资源信息时，向所述第一VNFM发送第二反馈消息，所述第二反馈消息用于指示与所述VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
结合本发明实施例第六方面的第六种实现方式，本发明实施例第六方面的第七种实现方式中，
所述发送器所发送的所述第二反馈消息包含与所述VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
结合本发明实施例第六方面的第七种实现方式，本发明实施例第六方面的第八种实现方式中，
所述接收器，还用于接收所述第一VNFM发送的第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述第一VNFM预留或者分配所述重配资源。
结合本发明实施例第六方面至本发明实施例第六方面的第八种实现方式任一项所述的VNFM，本发明实施例第六方面的第九种实现方式中，
所述接收器接收到的所述申请的资源信息包括申请的资源类型和申请的资源量。
本发明提供了一种网络功能虚拟化资源处理方法及虚拟网络功能管理器，当第一VNFM确定需要为虚拟网络功能VNF申请资源时，所述第一VNFM无需经过所述NFVO，而是将用于请求资源的第一资源请求消息发送给与所述第一VNFM连接的第二VNFM，所述第一资源请求消息包含所述第一VNFM为VNF申请的资源信息，在与所述第二VNFM连接的目标VIM的资源满足所述申请的资源信息时，所述第一VNFM根据已接收到的所述第一反馈消息确定能够确定为所述第一VNFM预留或者进行分配资源的所述目标VIM的信息。可见在本实施例所示的资源处理过程实现了分布式的资源管理方式，进而在NFVO出现故障时，所述第一VNFM仍然能够为虚拟网络功能VNF申请资源，有效的提高了网络的健壮性和效率。
附图说明
图1为本发明实施例所提供的NFV系统的一种示意性架构图；
图2为本发明实施例所提供的NFV系统的一种局部结构示意图；
图3为本发明实施例一所提供的网络功能虚拟化资源处理方法的步骤流程图；
图4为本发明实施例二所提供的网络功能虚拟化资源处理方法的步骤流程图；
图5为本发明实施例三所提供的网络功能虚拟化资源处理方法的步骤流程图；
图6为本发明实施例四所提供的网络功能虚拟化资源处理方法的步骤流程图；
图7为本发明实施例五所提供的网络功能虚拟化资源处理方法的步骤流程图；
图8为本发明实施例六所提供的虚拟网络功能管理器VNFM结构示意图；
图9为本发明实施例七所提供的虚拟网络功能管理器VNFM的结构示意图；
图10为本发明实施例八所提供的虚拟网络功能管理器VNFM的结构示意图；
图11为本发明实施例九所提供的虚拟网络功能管理器VNFM的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明的一部分实施例，而不是全部实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获得的所有其他实施例，都应属于本发明保护的范围。
图1是现有技术中NFV系统的架构图，请参阅图1，目前标准上定义的NFV端到端架构，主要包括三个部分：虚拟网络功能(Virtualized Network Function，VNF)、NFV基础设施(NFV Infrastructure，NFVI)，管理和编排(Management and Orchestration，MANO)。
VNF指虚拟化的网络功能，对应于传统网络中的物理网络功能。
NFVI提供整个系统运行的硬件和虚拟资源，由硬件资源(包括计算、网络、存储三部分)、虚拟化层(将硬件资源虚拟化成资源池)和虚拟资源(同样分成计算、网络、存储三部分)组成。
MANO包括：NFV编排器(NFV Orchestrator，NFVO)、VNF管理器(VNF Manager，VNFM)和虚拟化基础设施管理器(Virtualized Infrastructure Manager，VIM)。
其中，NFVO负责对网络服务(Network Service，NS，由多个VNF组成的服务单元)进行生命周期管理，并对整个NFV系统的资源(包括硬件资源和软件资源)进行编排和管理。
VNFM负责对VNF进行生命周期管理。
VIM负责管理NFVI。
VNF配有网元管理系统(Element Management System，EMS)来对其进行管理。
此外，运营支撑系统(Operation Support System，OSS)可以通过NFVO对整个NFV系统进行管理。
为更好的理解本发明实施例，在图1所示的基础上，首先对本发明实施例的网络功能虚拟化NFV系统进行说明。
图2为能够实现本发明实施例所示的网络功能虚拟化资源处理方法的局部NFV系统结构示意图；
需明确的是，图2所示为对本发明实施例所提供的NFV系统的示意性架构图，不做限定。
以图2所示为例，NFV系统包括：
NFV编排器以及与NFV编排器连接有多个VNFM；
其中，NFV编排器以及VNFM的具体说明请详见图1所示，具体在本实施例中不做赘述。
需明确的是，本实施例中对NFV编排器的管理域内所包含的VNFM的数量不做限定。
可选的，NFV编排器的管理域内的所有VNFM均与NFVO连接。
本实施例中，第一VNFM与第二VNFM连接，从而使得第一VNFM和第二VNFM之间能够进行消息的传输；
可选的，第一VNFM与第二VNFM通过接口连接。
本实施例中，第一VNFM可不仅仅与第二VNFM连接，第一VNFM还可与第N VNFM连接，本实施例对N的具体数目不做限定。
各VNFM的管理域内包含有多个虚拟化基础设施管理器VIM；
本实施例对各VNFM的管理域内包含的VIM的具体数目不做限定。
以图2所示为例，与第一VNFM连接设置有两个VIM，与第二VNFM连接设置有两个VIM。
其中，本实施例所示的VIM能够根据VNFM的指示对虚拟网络功能VNF申请的资源进行分配或预留。
以下结合具体实施例对本发明所提供的网络功能虚拟化资源处理方法进行详细说明：
实施例一：
以下结合图3所示对实施例一进行详细说明，其中，图3为本发明实施例一所提供的网络功能虚拟化资源处理方法的步骤流程图。
301、第一虚拟网络功能管理器VNFM向第二VNFM发送第一资源请求消息。
本实施例中，第一VNFM与第二VNFM已连接，则第一VNFM能够向第二VNFM发送第一资源请求消息；
需明确的是，本实施例以相互连接的第一VNFM和第二VNFM位于一个NFVO的管理域内进行示例性的说明，不做限定。
在其他可选的应用场景中，相互连接的第一VNFM和第二VNFM还可位于两个不同的NFVO的管理域内，只要第一VNFM能够将第一资源请求消息发送给第二VNFM即可。
本实施例对第一资源请求消息不做限定，只要第一资源请求消息包含第一VNFM为虚拟网络功能VNF申请的资源信息即可。
本实施例中，第一VNFM通过第一资源请求消息通知第二VNFM，第一资源请求消息包括第一VNFM为VNF申请的资源信息。
本实施例对第一VNFM为VNF申请的资源信息的具体内容不做限定，只要第二VNFM根据申请的资源信息确定与第二VNFM连接的虚拟化基础设施管理器VIM能否对第一VNFM为VNF申请的资源进行分配即可。
302、当与第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的的资源信息时，第一VNFM接收第二VNFM发送的第一反馈消息。
本实施例中，当目标VIM的资源满足第一VNFM为VNF申请的资源信息时，第一VNFM能够根据第二VNFM发送的第一反馈消息确定为第一VNFM预留或者分配了资源的目标VIM的信息。
本实施例对第一反馈消息不做限定，只要第一VNFM能够根据第一反馈消息确定为第一VNFM预留或者分配了资源的目标VIM的信息即可。
采用本实施例所示的网络功能虚拟化资源处理方法，当第一VNFM确定需要进行资源分配时，第一VNFM向第二VNFM发送第一资源请求消息，在与第二VNFM连接的目标VIM的资源满足申请的资源信息时，第一VNFM根据接收到的第一反馈消息确定能够对申请的资源进行预留或者进行分配的目标VIM的信息。可见在本实施例所示的资源处理过程中，第一VNFM和第二VNFM之间形成一个资源管理网络，从而VNFM之间可进行资源的处理，例如资源查询和资源分配等，且无需NFVO的参与，从而避免了若NFVO出现故障对网络的影响，实现了分布式的资源管理方式，有效的提高了网络的健壮性和效率。
图3所示的实施例一从第一VNFM的角度说明了网络功能虚拟化资源处理方法，以下结合图4所示的实施例二从第二VNFM的角度说明网络功能虚拟化资源处理方法。
实施例二：
401、第二VNFM接收第一VNFM发送的第一资源请求消息。
第一资源请求消息包含第一VNFM为虚拟网络功能VNF申请的资源信息。
本实施例中的第二VNFM为与第一VNFM连接且能够相互发送消息的VNFM；第二VNFM与第一VNFM可位于同一个NFVO的管理域内，也可位于不同的NFVO的管理域内，具体在本实施例中不做限定。
本实施例对第一资源请求消息不做限定，只要第二VNFM在接收到第一资源请求消息后能够确定与第二VNFM连接的VIM的资源能否对申请的资源进行分配即可。
402、当与第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的资源信息时，第二VNFM向第一VNFM发送第一反馈消息。
本实施例中，在第二VNFM确定与第二VNFM连接的目标VIM的资源满足申请的资源信息时，则第二VNFM将第一反馈消息发送给第一VNFM。
其中，第一反馈消息包含为第一VNFM预留或者分配了资源的目标VIM的信息。
采用本实施例所示的网络功能虚拟化资源处理方法，与第二VNFM无需经过NFVO即可接收第一VNFM发送的第一资源请求消息，在与第二VNFM连接的目标VIM的资源满足第一VNFM为VNF申请的资源信息时，第二VNFM将第一反馈消息发送给第一VNFM，第一VNFM即可根据已接收到的第一反馈消息确定为第一VNFM预留或者分配了资源的目标VIM的信息。可见在本实施例所示的资源处理过程中，第一VNFM和第二VNFM之间形成一个资源管理网络，从而VNFM之间可进行资源的处理，例如资源查询和资源分配等，且在具体处理过程中，无需NFVO的参与，从而避免了若NFVO出现故障对网络的影响，实现了分布式的资源管理方式，进而在NFVO出现故障时，第二VNFM仍然能够对申请的资源进行预留或分配，有效的提高了网络的健壮性和效率。
在实施例一和实施例二的基础上，以下结合图5所示的实施例三说明第一VNFM和第二VNFM是如何实现分布式的资源管理的。
实施例三：
501、第一VNFM接收资源申请消息。
在本步骤中，对资源申请消息不做限定，只要第一VNFM根据该资源申请消息确定有功能实体向第一VNFM申请资源即可。
例如：资源申请消息可为，VNF的实例化请求、VNF的扩展请求、或者是任一与资源申请相关的请求。
其中，VNF的扩展请求为当一个VNF的负载超过一定门限时，或者资源 消耗(如CPU占有率)超过一定门限时，VNF通过资源申请消息向第一VNFM申请对VNF进行增加资源的请求。
本实施例对发送资源申请消息的功能实体不做限定，例如：发送资源申请消息的功能实体可为VNF或者网元管理实体(英文：element manager，简称：EM)或者其他可以发起相关资源申请操作的功能实体。
具体的，第一VNFM能够根据资源申请消息确定申请资源。
可选的，申请资源包括申请资源的资源量和申请资源的资源类型。
502、第一VNFM向第二VNFM发送第一资源请求消息。
可选的，本实施例中，第一VNFM根据与第一VNFM连接的VIM的剩余资源的资源信息以发送第一资源请求消息；
具体的，第一VNFM可检查与第一VNFM连接的VIM的剩余资源的资源信息。本实施例所示的剩余资源的资源信息可包含剩余资源的资源量以及剩余资源的资源类型。
第一VNFM所确定的剩余资源的资源类型与申请资源的资源类型相匹配。
本实施例所示的与第一VNFM连接的VIM可指，与第一VNFM1有资源信息的交互(例如查询，更新，管理，预留，分配等)关系的VIM。
可选的，第一VNFM可以与VIM有物理连接，但没有触发资源管理关系。
本实施例对第一VNFM具体如何对与第一VNFM连接的VIM的剩余资源的资源信息进行检查的不做限定，只要第一VNFM能够确定与第一VNFM连接的VIM的剩余资源的资源信息即可。
以下对第一VNFM确定与第一VNFM连接的VIM的剩余资源的资源信息的方式进行示例性的说明：
本实施例提供了两种第一VNFM确定剩余资源的资源信息的方式：
第一种，第一VNFM存储有资源列表；
资源列表保存有与第一VNFM有资源管理关系的VIM的剩余资源的资源信息；在第一VNFM需要确定剩余资源的资源信息时，直接查询资源列表即可。
具体的，资源列表所存储的剩余资源的资源信息可由第一VNFM向VIM 获取；或，与第一VNFM连接的VIM可周期性或非周期性的将VIM的剩余资源的资源信息上报给第一VNFM；或，与第一VNFM连接的VIM在满足触发事件时将VIM的剩余资源的资源信息上报给第一VNFM，触发事件可为与第一VNFM连接的VIM所管理的资源发生变化的事件。
第二种，在第一VNFM接收到资源申请消息后，第一VNFM可向与第一VNFM连接的VIM发送资源查询消息，从而使得与第一VNFM连接的VIM发送资源响应消息，并通过该资源响应消息指示VIM的剩余资源的资源信息。
需明确的是，有的VNF是可以跨VIM分配资源的，这时候只需要第一VNFM管理的所有VIM的剩余资源总和能够符合需要就可以，但有的VNF是不可以跨VIM分配资源的，那么第一VNFM管理的每个VIM的剩余资源都不能满足就需要发送第一资源请求消息。
可见，若第一VNFM确定与第一VNFM连接的VIM的剩余资源的资源量小于申请资源的资源量时，则第一VNFM发送第一资源请求消息，以通过该第一资源请求消息，第一VNFM能够向与第一VNFM连接的其他VNFM请求资源。
例如：第一VNFM确定申请资源为4GB vRAM,2vCPU,32GB virtual storage，而第一VNFM确定与第一VNFM连接的VIM的剩余资源为2GB vRAM,1vCPU,28GB virtual storage，第一VNFM即可确定与第一VNFM连接的VIM不能对申请资源进行分配，则第一VNFM即可发送第一资源请求消息。
需明确的是，本实施例中的步骤501至步骤502为可选步骤，不做限定；
例如：第一VNFM也可在不对与第一VNFM连接的VIM的剩余资源的资源信息进行查询的情况下发送第一资源请求消息。
还例如：第一VNFM也可在没有接收到资源申请消息，但与第一VNFM连接的VIM的剩余资源的资源信息不能满足预先配置的资源管理门限的情况下发送第一资源请求消息。这里资源管理门限可以定义为一个VNFM管理的资源需要满足一定的量，例如：资源管理门限可为10GB vRAM,8vCPU,65GB virtual storage。
第一资源请求消息包含第一VNFM为VNF申请的资源信息。
本实施例所示的申请的资源为第一VNFM请求与第二VNFM连接的VIM进行分配的资源。
本实施例中，第一VNFM为VNF申请的资源可为全部的申请资源；或，第一VNFM为VNF申请的资源可为部分的申请资源。
若第一VNFM为VNF申请的资源为全部的申请资源，则第一VNFM通过第一资源请求消息能够向与第一VNFM连接的其他VNFM请求资源。
若第一VNFM为VNF申请的资源为部分的申请资源时，第一VNFM可将申请资源分为两部分，为第一申请资源和第二申请资源，第一申请资源和与第一VNFM连接的VIM的剩余资源相匹配，第一VNFM即可通过与第一VNFM连接的VIM对第一申请资源进行分配，此时，第一VNFM为VNF申请的资源即为第二申请资源，即第一VNFM通过第一资源请求消息请求与第二VNFM连接的VIM对第二申请资源进行分配。
具体的，第一VNFM为VNF申请的资源信息包括为VNF申请的资源类型和资源量；
更具体的，第一资源请求消息还可携带以下信息：申请的资源的相关policy，如亲和性/反亲和性(affinity/anti-affinity)。
503、第二VNFM接收第一VNFM发送的第一资源请求消息。
504、第二VNFM向目标VIM发送资源预留消息。
具体的，第二VNFM确定目标VIM。第二VNFM确定目标VIM的过程可为：
第二VNFM接收到第一资源请求消息后，即可查询与第二VNFM连接的VIM的剩余资源的资源信息；第二VNMF确定与第二VNFM连接的VIM中能够对申请的资源进行分配的VIM为目标VIM。
例如：与第二VNFM连接的VIM4的剩余资源能够对申请的资源进行分配，则第二VNFM即可确定VIM4为目标VIM。
本实施例对资源预留消息不做限定，只要资源预留消息能够指示目标VIM为申请的资源预留资源即可。
具体的，资源预留消息包含资源预留标识；资源预留标识用于标识目标VIM所预留的资源用于对申请的资源进行分配。
可选的，资源预留消息包括以下信息中的任意组合，资源预留标识，第一VNFM的标识，需要分配资源的VNF的标识，申请的资源类型，申请的资源量，申请的资源的相关policy，目标VIM的标识。
505、目标VIM根据资源预留消息进行资源预留。
506、目标VIM将资源预留反馈消息发送给第二VNFM。
507、第二VNFM接收目标VIM发送的资源预留反馈消息，并向第一VNFM发送第一反馈消息。
第二VNFM能够根据资源预留反馈消息确定目标VIM资源预留成功。
在目标VIM资源预留成功的情况下，第二VNFM发送第一反馈消息。
具体的，第一反馈消息包含的目标VIM的信息，包括以下信息的任意组合：目标VIM的标识，用于与目标VIM建立连接的配置信息。
需明确的是，本实施例对目标VIM的信息所包括的具体信息为举例进行说明，不做限定，只要第一VNFM根据第一反馈消息确定目标VIM资源预留成功即可。
例如：目标VIM的信息还可包括在该VIM上预留的资源的信息，例如资源的类型和对应的资源量。
更具体的，第一反馈消息包含资源预留标识。
508、第二VNFM向第一VNFM发送的第一反馈消息。
509、第一VNFM接收第一反馈消息。
510、第一VNFM建立第一VNFM与目标VIM连接。
具体的，第一VNFM可根据第一反馈消息建立与目标VIM的连接；更具体的，第一VNFM可根据第一反馈消息所包含的述目标VIM的信息建立与目标VIM的连接。
当然，在具体应用本实施例中的过程中，目标VIM的标识和/或配置信息可由第二VNFM不通过第一反馈消息发送给第一VNFM。
需明确的是，本实施例中用于建立第一VNFM与目标VIM连接的步骤510与步骤504至步骤509之间并无时序上的先后关系，本实施例仅仅为一种示例。
还需明确的是，若第一VNFM已与目标VIM连接，则无需进行步骤510；
还需明确的是，用于建立第一VNFM与目标VIM连接的步骤510仅仅为 一种示例，不做限定，例如：第一VNFM还可向与第一VNFM连接的NFVO获取配置信息。
本实施例对配置信息不做限定，只要第一VNFM能够根据配置信息建立第一VNFM与目标VIM连接即可；
例如：配置信息包括：目标VIM的IP地址；
可选的，配置信息还可以包括以下信息的任意组合：目标VIM的统一资源定位符(英文：uniform resource locator，缩写：URL)、目标VIM的用户名、目标VIM的认证密码等。
511、第一VNFM向目标VIM发送第一资源分配消息。
第一资源分配消息用于目标VIM根据第一资源分配消息对申请的资源进行分配。
具体的，第一资源分配消息包含资源预留标识。
512、目标VIM根据第一资源分配消息对申请的资源进行分配。
例如：VIM根据之前预留的资源信息进行资源分配，包括启动虚拟机(VM，virtual machine)。
513、目标VIM向第一VNFM发送资源分配反馈消息。
具体的，目标VIM在接收到第一资源分配消息后，即可根据第一资源分配消息中所包含的资源预留标识确定已预留的资源用于申请的资源的分配；
目标VIM即可通过已预留的资源对申请的资源进行分配。
目标VIM可通过资源分配反馈消息通知第一VNFM申请的资源已分配成功。
可选的，第一VNFM还可向与第一VNFM连接的NFVO反馈资源分配情况。
可选的，在第一VNFM接收到目标VIM发送的资源分配反馈消息后，第一VNFM还可以对相关VNF相关配置操作；例如：若资源申请消息是VNF实例化请求，则第一VNFM对VNF进行参数配置；若资源申请消息是VNF扩展请求，则第一VNFM对VNF进行参数配置更新。
采用本实施例所示的网络功能虚拟化资源处理方法，第一VNFM和第二VNFM之间形成一个资源管理网络，从而VNFM之间可进行资源的处理，例 如资源查询和资源分配等，且在具体处理过程中，无需NFVO的参与，从而避免了若NFVO出现故障对网络的影响，实现了分布式的资源管理方式，进而在NFVO出现故障时，第二VNFM仍然能够对申请的资源进行预留或分配，有效的提高了网络的健壮性和效率。
图5所示为实施例三为第二VNFM对第一VNFM为VNF申请的资源进行资源预留，第一VNFM对申请的资源进行资源分配的情况，以下结合图6所示的实施例四说明第二VNFM是如何实现对申请的资源进行资源分配的。
实施例四：
601、第一VNFM接收资源申请消息。
602、第一VNFM向第二VNFM发送第一资源请求消息。
603、第二VNFM接收第一VNFM发送的第一资源请求消息。
本实施例中的步骤601至步骤603所示的具体过程请详见图5所示的步骤501至步骤503所示，具体在本实施例中不做赘述。
604、第二VNFM向目标VIM发送第二资源分配消息；
第二VNFM具体如何确定目标VIM的具体过程请详见图4所示的实施例，具体在本实施例中不做赘述。
本实施例中，第二资源分配消息可包括以下信息中的任意组合，申请的资源类型，申请的资源量，申请的资源的相关policy。
605、目标VIM根据第二资源分配消息进行资源分配。
606、目标VIM向第二VNFM发送资源分配反馈消息。
目标VIM可通过资源分配反馈消息通知第二VNFM申请的资源已分配成功；可选的，资源分配反馈消息可包含目标VIM的标识以及一些配置参数，如已分配的资源所在位置，连接信息等。
607、第二VNFM向第一VNFM发送第一反馈消息。
第一反馈消息包含为第一VNFM分配了资源的目标VIM的信息，例如目标VIM的标识，以及在该目标VIM上分配的资源的信息。分配的资源的信息包括分配的资源的类型和分配的资源量。
其中，第一反馈消息还可包括以下信息中的任意组合：目标VIM所分配的目标虚拟机VM的标识，目标VM的位置信息。
608、第一VNFM根据第一资源分配反馈消息确定申请的资源已被目标VIM分配成功。
可选的，第一VNFM还可向与第一VNFM连接的NFVO反馈资源分配情况；
可选的，在第一VNFM接收到目标VIM发送的资源分配反馈消息后，第一VNFM还可以对相关VNF相关配置操作。例如：若资源申请消息是VNF实例化请求，则第一VNFM对VNF进行参数配置；若资源申请消息是VNF扩展请求，则第一VNFM对VNF进行参数配置更新。
采用本实施例所示的网络功能虚拟化资源处理方法，第一VNFM和第二VNFM之间形成一个资源管理网络，从而VNFM之间可进行资源的处理，例如资源查询和资源分配等，且在具体处理过程中，无需NFVO的参与，从而避免了若NFVO出现故障对网络的影响，实现了分布式的资源管理方式，进而在NFVO出现故障时，第二VNFM仍然能够对申请的资源进行预留或分配，有效的提高了网络的健壮性和效率。
图5所示的实施例三和图6所示的实施例四说明了当与第二VNFM连接的目标VIM的资源满足申请的资源信息时是如何实现网络功能虚拟化资源处理方法的，以下结合图7所示的实施例五说明，若与第二VNFM连接的目标VIM的资源不能满足申请的资源信息时是如何实现网络功能虚拟化资源处理方法的。
实施例五：
701、第一VNFM接收资源申请消息。
702、第一VNFM向第二VNFM发送第一资源请求消息。
703、第二VNFM接收第一VNFM发送的第一资源请求消息。
本实施例所示的步骤701至步骤703的具体过程请见图5所示的步骤501至步骤503所示，具体在本实施例中不做赘述。
704、第二VNFM确定与第二VNFM连接的目标VIM的资源不能满足申请的资源信息。
具体的，第二VNFM接收到第一资源请求消息后，即可查询与第二VNFM连接的目标VIM的剩余资源的资源信息；
本实施例中，与第二VNFM连接的目标VIM不能够对申请的资源进行分配。
例如目标VIM的剩余资源的资源量小于申请的资源量。
705、第二VNFM向第一VNFM发送的第二反馈消息。
其中，第二反馈消息用于指示与第二VNFM连接的目标VIM的资源不能满足申请的资源信息。
具体的，第二反馈消息还包含与第二VNFM连接的目标VIM的剩余资源的资源信息；
目标VIM的剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
706、第一VNFM接收第二反馈消息。
第一VNFM根据第二反馈消息确定与第二VNFM连接的目标VIM的资源不能满足申请的资源信息，则第一VNFM可继续执行步骤707或步骤708；
通过执行步骤707，第一VNFM将第一资源请求消息发送给与第一VNMF连接的第三VNMF，若与第三VNFM连接的VIM的资源不能满足申请的资源信息，则第一VNFM将第一请求消息发送给其他与第一VNFM连接的VNFM，直至第一资源请求消息发送给满足申请的资源信息的VNFM。
若与第三VNFM连接的VIM的资源能满足申请的资源信息，则第一VNFM请求与第三VNFM连接的VIM对申请的资源进行预留或分配。
可选的，第一VNFM可将第一资源请求消息发送给所有与第一VNFM连接的VNFM，从而选定满足申请的资源信息的VNFM。
具体的，与第三VNFM连接的VIM对申请的资源进行预留或分配的具体实现过程请见上述所示的与第二VNFM连接的目标VIM对申请的资源进行预留或分配的过程，具体在此处不再赘述。通过执行步骤708，第一VNFM能够触发与第二VNFM连接的目标VIM对申请的资源的一部分进行预留或分配，具体请详见步骤708至步骤713所示。
707、第一VNFM将第一资源请求消息发送给第三VNMF。
708、第一VNFM向第二VNFM发送第二资源请求消息。
其中，第二资源请求消息包含重配资源的资源信息；
重配资源为申请的资源中与剩余资源相匹配的资源；
具体的，重配资源的资源量小于或等于剩余资源的资源量；
更具体的，重配资源的资源信息包括重配资源的资源类型和重配资源的资源量。
709、第二VNFM接收第一VNFM发送第二资源请求消息。
710、第二VNFM控制目标VIM对重配资源进行预留或分配。
具体的，第二VNFM根据第二资源请求消息对重配资源进行预留或分配。
若第二VNFM对待重配资源进行预留，则第二VNFM对待重配资源进行预留的实现过程可参见图4所示的第二VNFM对申请的资源进行预留的过程，具体在本实施例中不做赘述。
若第二VNFM对待重配资源进行分配，则第二VNFM对待重配资源进行分配的实现过程可参见图5所示的第二VNFM对申请的资源进行分配的过程，具体在本实施例中不做赘述。
711、第二VNFM向第一VNFM发送第三反馈消息。
第三反馈消息包含为重配资源预留或者分配了资源的VIM的信息。
712、第一VNFM向与第一VNFM连接的其他VNFM请求资源，直至申请的资源分配完成。
可见，上述步骤中，申请的资源通过与第一VNFM连接的多个VNFM进行分配。
采用本实施例所示的网络功能虚拟化资源处理方法，第一VNFM和第二VNFM之间形成一个资源管理网络，从而VNFM之间可进行资源的处理，例如资源查询和资源分配等，且在具体处理过程中，无需NFVO的参与，从而避免了若NFVO出现故障对网络的影响，实现了分布式的资源管理方式，进而在NFVO出现故障时，第二VNFM仍然能够对申请的资源进行预留或分配，有效的提高了网络的健壮性和效率。
以下结合图8所示的实施例六对本发明实施例所提供的虚拟网络功能管理器VNFM的具体结构进行详细说明：
其中，本实施例所示的VNFM用以实现图3、图5-7中第一VNFM执行的方法。
VNFM包括：
发送单元801，用于向第二VNFM发送第一资源请求消息，第一资源请求消息包含VNFM为虚拟网络功能VNF申请的资源信息。
接收单元802，用于当与第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的资源信息时，接收第二VNFM发送的第一反馈消息,第一反馈消息包含为VNFM预留或者分配了资源的目标VIM的信息。
其中，本实施例所示的第二VNFM为与本实施例所提供的VNFM相互连接的VNFM。
需明确的是，本实施例中，对发送单元801以及接收单元802的具体数目不做限定，即发送单元801可为一个或多个，接收单元802可为一个或多个。
可选的，进一步如图8所示，本实施例中的VNFM还包括：确定单元803；
当第二VNFM能够对申请的资源进行预留时，确定单元803，用于确定第一反馈消息包含为VNFM预留了资源的目标VIM的信息。
其中，发送单元801，还用于当第一反馈消息包含为VNFM预留了资源的目标VIM的信息时，向目标VIM发送第一资源分配消息，第一资源分配消息用于目标VIM对申请的资源进行分配。
具体的，接收单元802接收的第一反馈消息包含资源预留标识。
具体的，发送单元801所发送的第一资源分配消息包含资源预留标识，资源预留标识用于标识预留的资源。
当第二VNFM能够对申请的资源进行分配时，确定单元803，还用于确定第一反馈消息包含为VNFM分配了资源的目标VIM的信息，第一反馈消息还包括以下信息中的任意组合：目标VIM所分配的目标虚拟机VM的标识，目标VM的位置信息。
其中，接收单元802接收到的目标VIM的信息包括以下信息的任意组合：目标VIM的标识，用于与目标VIM建立连接的配置信息。
若与第二VNFM连接的VIM的资源不能满足申请的资源信息时，接收单元802，还用于当与第二VNFM连接的目标VIM的资源不能满足申请的资源信息时，接收第二VNFM发送的第二反馈消息。
第二反馈消息用于指示与第二VNFM连接的目标VIM的资源不能满足申 请的资源信息。
具体的，接收单元802接收到的第二反馈消息还包含与第二VNFM连接的目标VIM的剩余资源的资源信息，剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
具体的，发送单元801，还用于向第二VNFM发送第二资源请求消息，第二资源请求消息包含重配资源的资源信息，剩余资源用于目标VIM为VNFM预留或者分配重配资源。
具体的，发送单元801发送的申请的资源信息包括申请的资源类型和申请的资源量。
以下结合图9所示的实施例七对本发明实施例所提供的一种虚拟网络功能管理器VNFM的具体结构进行详细说明。
其中，本实施例所示的VNFM用以实现图4-7中第二VNFM执行的方法。
VNFM包括：
接收单元901，用于接收第一VNFM发送的第一资源请求消息，第一资源请求消息包含第一VNFM为虚拟网络功能VNF申请的资源信息。
确定单元902，用于确定与VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的资源信息。
发送单元903，用于当与VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的资源信息时，向第一VNFM发送的第一反馈消息，第一反馈消息包含为第一VNFM预留或者分配了资源的目标VIM的信息。
其中，本实施例所示的第一VNFM为与本实施例所提供的VNFM连接的VNFM。
需明确的是，本实施例中，对接收单元901、确定单元902以及发送单元903的具体数目不做限定，即接收单元901可为一个或多个，确定单元902可为一个或多个，发送单元903可为一个或多个。
具体的，发送单元903，还用于向目标VIM发送资源预留消息；
接收单元901，还用于接收目标VIM发送的资源预留反馈消息。
具体的，发送单元903所发送的资源预留消息包含资源预留标识。
发送单元903所发送的第一反馈消息包含资源预留标识，资源预留标识用 于标识目标VIM所预留的资源用于对申请的资源进行分配。
具体的，发送单元903，还用于向目标VIM发送第二资源分配消息；
接收单元901，还用于接收目标VIM发送的资源分配反馈消息。
具体的，发送单元903所发送的第一反馈消息还包括以下信息中的任意组合：目标VIM所分配的目标虚拟机VM的标识，目标VIM所分配的目标VM的位置信息。
发送单元903所发送的第一反馈消息所包括的目标VIM的信息包括以下信息的任意组合：目标VIM的标识，用于与目标VIM建立连接的配置信息。
若与VNFM连接的VIM的资源不能满足申请的资源信息时，确定单元902，还用于确定与VNFM连接的目标VIM的资源不能满足申请的资源信息。
发送单元903，用于当与VNFM连接的目标VIM的资源不能满足申请的资源信息时，向第一VNFM发送第二反馈消息，第二反馈消息用于指示与VNFM连接的目标VIM的资源不能满足申请的资源信息。
具体的，发送单元903所发送的第二反馈消息包含与VNFM连接的目标VIM的剩余资源的资源信息，剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
具体的，接收单元901，还用于接收第一VNFM发送的第二资源请求消息，第二资源请求消息包含重配资源的资源信息，剩余资源用于目标VIM为第一VNFM预留或者分配重配资源。
具体的，接收单元901接收到的申请的资源信息包括申请的资源类型和申请的资源量。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
上述单元的划分仅仅为示例，不做限定。
本发明第八实施例提供一种虚拟网络功能管理器VNFM。本实施例中的虚拟网络功能管理器VNFM可以执行图3、图5至图7所示的方法中的第一VNFM的操作。
如图10所示，本实施例的VNFM包括：发送器1001和接收器1002；
且本实施例中发送器1001和接收器1002之间通过总线进行连接，当然也可采用其他的连接方式，具体连接方式在本实施例中不作限定。
本发明实施例涉及的VNFM可以具有比图10所示出的更多或更少的部件，可以组合两个或更多个部件，或者可以具有不同的部件配置或设置，各个部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件或硬件和软件的组合实现。
发送器1001，用于向第二VNFM发送第一资源请求消息，第一资源请求消息包含VNFM为虚拟网络功能VNF申请的资源信息。
接收器1002，用于当与第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的资源信息时，接收第二VNFM发送的第一反馈消息,第一反馈消息包含为VNFM预留或者分配了资源的目标VIM的信息。
其中，本实施例对发送器1001和接收器1002的具体数目不做限定，即发送器1001的数目可为一个或多个，接收器1002的数目可为一个或多个。
进一步如图10所示，VNFM还包括处理器1003；
其中，处理器1003可为一个或多个，在本实施例中以一个为例进行说明。
且本实施例中发送器1001、接收器1002和处理器1003之间通过总线进行连接，当然也可采用其他的连接方式，具体连接方式在本实施例中不作限定。
处理器1003，用于确定第一反馈消息包含为VNFM预留了资源的目标VIM的信息。
发送器1001，还用于当第一反馈消息包含为VNFM预留了资源的目标VIM的信息时，向目标VIM发送第一资源分配消息，第一资源分配消息用于目标VIM对申请的资源进行分配。
可选的，接收器1002接收的第一反馈消息包含资源预留标识，发送器1001所发送的第一资源分配消息包含资源预留标识，资源预留标识用于标识预留的资源。
可选的，处理器1003，用于确定第一反馈消息包含为VNFM分配了资源的目标VIM的信息，第一反馈消息还包括以下信息中的任意组合：目标VIM所分配的目标虚拟机VM的标识，目标VM的位置信息。
可选的，接收器1002接收到的目标VIM的信息包括以下信息的任意组合：
目标VIM的标识，用于与目标VIM建立连接的配置信息。
可选的，接收器1002，还用于当与第二VNFM连接的目标VIM的资源不能满足申请的资源信息时，接收第二VNFM发送的第二反馈消息；
第二反馈消息用于指示与第二VNFM连接的目标VIM的资源不能满足申请的资源信息。
可选的，接收器1002接收到的第二反馈消息还包含与第二VNFM连接的目标VIM的剩余资源的资源信息，剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
可选的，发送器1001，还用于向第二VNFM发送第二资源请求消息，第二资源请求消息包含重配资源的资源信息，剩余资源用于目标VIM为VNFM预留或者分配重配资源。
可选的，发送器1001发送的申请的资源信息包括申请的资源类型和申请的资源量。
可选的，本实施例的NFVM还可以包括存储器，所述存储器中存储有计算机可执行指令，用于指示处理器1003跟发送器1001和接收器1002配合以完成图3、图5至图7所示的方法中的第一VNFM的操作。
本发明实施例九提供了一种虚拟网络功能管理器VNFM。本实施例中的虚拟网络功能管理器VNFM可以执行图4至图7所示的方法中的第二VNFM的操作。
如图11所示，本实施例的VNFM包括：发送器1101、接收器1102以及处理器1103；
本发明实施例涉及的VNFM可以具有比图11所示出的更多或更少的部件，可以组合两个或更多个部件，或者可以具有不同的部件配置或设置，各个部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件或硬件和软件的组合实现。
其中，发送器1101、接收器1102以及处理器1103可为一个或多个。
且本实施例中发送器1101、接收器1102和处理器1103之间通过总线进行连接，当然也可采用其他的连接方式，具体连接方式在本实施例中不作限定。
接收器1102，用于接收第一VNFM发送的第一资源请求消息，第一资源 请求消息包含第一VNFM为虚拟网络功能VNF申请的资源信息。
处理器1103，用于确定与VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的资源信息。
发送器1101，用于当与VNFM连接的目标虚拟化基础设施管理器VIM的资源满足申请的资源信息时，向第一VNFM发送的第一反馈消息，第一反馈消息包含为第一VNFM预留或者分配了资源的目标VIM的信息。
可选的，发送器1101，还用于向目标VIM发送资源预留消息；
接收器1102，还用于接收目标VIM发送的资源预留反馈消息。
可选的，发送器1101所发送的资源预留消息包含资源预留标识，发送器1101所发送的第一反馈消息包含资源预留标识，资源预留标识用于标识目标VIM所预留的资源用于对申请的资源进行分配。
可选的，发送器1101，还用于向目标VIM发送第二资源分配消息。
接收器1102，还用于接收目标VIM发送的资源分配反馈消息。
可选的，发送器1101所发送的第一反馈消息还包括以下信息中的任意组合：目标VIM所分配的目标虚拟机VM的标识，目标VIM所分配的目标VM的位置信息。
可选的，发送器1101所发送的第一反馈消息所包括的目标VIM的信息包括以下信息的任意组合：
目标VIM的标识，用于与目标VIM建立连接的配置信息。
可选的，处理器1103，还用于确定与VNFM连接的目标VIM的资源不能满足申请的资源信息。
发送器1101，还用于当与VNFM连接的目标VIM的资源不能满足申请的资源信息时，向第一VNFM发送第二反馈消息，第二反馈消息用于指示与VNFM连接的目标VIM的资源不能满足申请的资源信息。
可选的，发送器1101所发送的第二反馈消息包含与VNFM连接的目标VIM的剩余资源的资源信息，剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
可选的，接收器1102，还用于接收第一VNFM发送的第二资源请求消息，第二资源请求消息包含重配资源的资源信息，剩余资源用于目标VIM为第一 VNFM预留或者分配重配资源。
可选的，接收器1102接收到的申请的资源信息包括申请的资源类型和申请的资源量。
可选的，本实施例的NFVM还可以包括存储器，所述存储器中存储有计算机可执行指令，用于指示处理器1103跟发送器1101和接收器1102配合以完成图4至图7所示的方法中的第二VNFM的操作。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (38)

  1. 一种网络功能虚拟化资源处理方法，其特征在于，包括：
    第一虚拟网络功能管理器VNFM向第二VNFM发送第一资源请求消息，所述第一资源请求消息包含所述第一VNFM为虚拟网络功能VNF申请的资源信息；
    当与所述第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，所述第一VNFM接收所述第二VNFM发送的第一反馈消息,所述第一反馈消息包含为所述第一VNFM预留或者分配了资源的所述目标VIM的信息。
  2. 根据权利要求1所述的方法，其特征在于，当所述第一反馈消息包含为所述第一VNFM预留了资源的所述目标VIM的信息时，所述第一VNFM接收所述第二VNFM发送的第一反馈消息之后，所述方法还包括：
    所述第一VNFM向所述目标VIM发送第一资源分配消息，所述第一资源分配消息用于所述目标VIM对所述申请的资源进行分配。
  3. 根据权利要求2所述的方法，其特征在于，所述第一反馈消息包含资源预留标识，所述第一资源分配消息包含所述资源预留标识，所述资源预留标识用于标识所述预留的资源。
  4. 根据权利要求1所述的方法，其特征在于，当所述第一反馈消息包含为所述第一VNFM分配了资源的所述目标VIM的信息时，所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VIM所分配的目标VM的位置信息。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述目标VIM的信息包括以下信息的任意组合：
    所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：当与所述第二VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，所述第一VNFM接收所述第二VNFM发送的第二反馈消息；
    所述第二反馈消息用于指示与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
  7. 根据权利要求6所述的方法，其特征在于，所述第二反馈消息包含与所述第二VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述第一VNFM向所述第二VNFM发送第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述第一VNFM预留或者分配所述重配资源。
  9. 根据权利要求1至8任一项所述的方法，其特征在于，所述申请的资源信息包括申请的资源类型和申请的资源量。
  10. 一种网络功能虚拟化资源处理方法，其特征在于，包括：
    第二VNFM接收第一VNFM发送的第一资源请求消息，所述第一资源请求消息包含所述第一VNFM为虚拟网络功能VNF申请的资源信息；
    当与所述第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，所述第二VNFM向所述第一VNFM发送的第一反馈消息，所述第一反馈消息包含为所述第一VNFM预留或者分配了资源的所述目标VIM的信息。
  11. 根据权利要求10所述的方法，其特征在于，所述第二VNFM向所述第一VNFM发送第一反馈消息之前，所述方法还包括：
    所述第二VNFM向所述目标VIM发送资源预留消息；
    所述第二VNFM接收所述目标VIM发送的资源预留反馈消息。
  12. 根据权利要求11所述的方法，其特征在于，所述资源预留消息包含资源预留标识，所述第一反馈消息包含所述资源预留标识，所述资源预留标识用于标识所述预留的资源。
  13. 根据权利要求10所述的方法，其特征在于，所述第二VNFM向所述第一VNFM发送第一反馈消息之前，所述方法还包括：
    所述第二VNFM向所述目标VIM发送第二资源分配消息；
    所述第二VNFM接收所述目标VIM发送的资源分配反馈消息。
  14. 根据权利要求10所述的方法，其特征在于，所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识， 所述目标VIM所分配的目标VM的位置信息。
  15. 根据权利要求10至14任一项所述的方法，其特征在于，所述目标VIM的信息包括以下信息的任意组合：
    所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
  16. 根据权利要求10所述的方法，其特征在于，所述方法还包括：当与所述第二VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，所述第二VNFM向所述第一VNFM发送第二反馈消息；
    所述第二反馈消息用于指示与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
  17. 根据权利要求16所述的方法，其特征在于，当与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息时，所述第二反馈消息包含与所述第二VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述第二VNFM接收所述第一VNFM发送第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述第一VNFM预留或者分配所述重配资源。
  19. 根据权利要求10至18任一项所述的方法，其特征在于，所述申请的资源信息包括申请的资源类型和申请的资源量。
  20. 一种虚拟网络功能管理器VNFM，其特征在于，包括：
    发送器，用于向第二VNFM发送第一资源请求消息，所述第一资源请求消息包含所述VNFM为虚拟网络功能VNF申请的资源信息；
    接收器，用于当与所述第二VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，接收所述第二VNFM发送的第一反馈消息,所述第一反馈消息包含为所述VNFM预留或者分配了资源的所述目标VIM的信息。
  21. 根据权利要求20所述的VNFM，其特征在于，所述VNFM还包括处理器；
    所述处理器，用于确定所述第一反馈消息包含为所述VNFM预留了资源 的所述目标VIM的信息；
    所述发送器，还用于当所述第一反馈消息包含为所述VNFM预留了资源的所述目标VIM的信息时，向所述目标VIM发送第一资源分配消息，所述第一资源分配消息用于所述目标VIM对所述申请的资源进行分配。
  22. 根据权利要求21所述的VNFM，其特征在于，
    所述接收器接收的所述第一反馈消息包含资源预留标识，所述发送器所发送的第一资源分配消息包含所述资源预留标识，所述资源预留标识用于标识所述预留的资源。
  23. 根据权利要求20所述的VNFM，其特征在于，所述VNFM还包括处理器；
    所述处理器，用于确定所述第一反馈消息包含为所述VNFM分配了资源的所述目标VIM的信息，所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VM的位置信息。
  24. 根据权利要求20至23任一项所述的VNFM，其特征在于，所述接收器接收到的所述目标VIM的信息包括以下信息的任意组合：
    所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
  25. 根据权利要求20所述的VNFM，其特征在于，
    所述接收器，还用于当与所述第二VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，接收所述第二VNFM发送的第二反馈消息；
    所述第二反馈消息用于指示与所述第二VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
  26. 根据权利要求25所述的VNFM，其特征在于，所述接收器接收到的所述第二反馈消息还包含与所述第二VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
  27. 根据权利要求26所述的VNFM，其特征在于，
    所述发送器，还用于向所述第二VNFM发送第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述VNFM预留或者分配所述重配资源。
  28. 根据权利要求20至27任一项所述的VNFM，其特征在于，所述发送器发送的所述申请的资源信息包括申请的资源类型和申请的资源量。
  29. 一种虚拟网络功能管理器VNFM，其特征在于，包括：
    接收器，用于接收第一VNFM发送的第一资源请求消息，所述第一资源请求消息包含所述第一VNFM为虚拟网络功能VNF申请的资源信息；
    处理器，用于确定与所述VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息；
    发送器，用于当与所述VNFM连接的目标虚拟化基础设施管理器VIM的资源满足所述申请的资源信息时，向所述第一VNFM发送的第一反馈消息，所述第一反馈消息包含为所述第一VNFM预留或者分配了资源的所述目标VIM的信息。
  30. 根据权利要求29所述的VNFM，其特征在于，
    所述发送器，还用于向所述目标VIM发送资源预留消息；
    所述接收器，还用于接收所述目标VIM发送的资源预留反馈消息。
  31. 根据权利要求30所述的VNFM，其特征在于，所述发送器所发送的所述资源预留消息包含资源预留标识，所述发送器所发送的所述第一反馈消息包含所述资源预留标识，所述资源预留标识用于标识所述目标VIM所预留的资源用于对所述申请的资源进行分配。
  32. 根据权利要求29所述的VNFM，其特征在于，
    所述发送器，还用于向所述目标VIM发送第二资源分配消息；
    所述接收器，还用于接收所述目标VIM发送的资源分配反馈消息。
  33. 根据权利要求29所述的VNFM，其特征在于，
    所述发送器所发送的所述第一反馈消息还包括以下信息中的任意组合：所述目标VIM所分配的目标虚拟机VM的标识，所述目标VIM所分配的目标VM的位置信息。
  34. 根据权利要求29至33任一项所述的VNFM，其特征在于，所述发送器所发送的所述第一反馈消息所包括的所述目标VIM的信息包括以下信息的任意组合：
    所述目标VIM的标识，用于与所述目标VIM建立连接的配置信息。
  35. 根据权利要求29所述的VNFM，其特征在于，所述处理器，还用于确定与所述VNFM连接的目标VIM的资源不能满足所述申请的资源信息；
    所述发送器，还用于当与所述VNFM连接的目标VIM的资源不能满足所述申请的资源信息时，向所述第一VNFM发送第二反馈消息，所述第二反馈消息用于指示与所述VNFM连接的所述目标VIM的资源不能满足所述申请的资源信息。
  36. 根据权利要求35所述的VNFM，其特征在于，
    所述发送器所发送的所述第二反馈消息包含与所述VNFM连接的所述目标VIM的剩余资源的资源信息，所述剩余资源的资源信息包括剩余资源的资源类型和剩余资源的资源量。
  37. 根据权利要求36所述的VNFM，其特征在于，
    所述接收器，还用于接收所述第一VNFM发送的第二资源请求消息，所述第二资源请求消息包含重配资源的资源信息，所述剩余资源用于所述目标VIM为所述第一VNFM预留或者分配所述重配资源。
  38. 根据权利要求29至37任一项所述的VNFM，其特征在于，所述接收器接收到的所述申请的资源信息包括申请的资源类型和申请的资源量。
PCT/CN2015/091066 2015-09-29 2015-09-29 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器 WO2017054129A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
JP2018516167A JP6511585B2 (ja) 2015-09-29 2015-09-29 ネットワーク機能仮想化リソース処理方法および仮想化されたネットワーク機能マネージャ
RU2018115309A RU2690198C1 (ru) 2015-09-29 2015-09-29 Способ обработки ресурсов виртуализации сетевых функций и диспетчер виртуализованной сетевой функции
PCT/CN2015/091066 WO2017054129A1 (zh) 2015-09-29 2015-09-29 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器
EP15905041.8A EP3358790B1 (en) 2015-09-29 2015-09-29 Network function virtualization resource processing method and virtualized network function manager
KR1020187011984A KR20180061299A (ko) 2015-09-29 2015-09-29 네트워크 기능 가상화 자원 처리 방법 및 가상 네트워크 기능 관리자
CN201580028616.2A CN107005452B (zh) 2015-09-29 2015-09-29 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器
US15/940,102 US20180219793A1 (en) 2015-09-29 2018-03-29 Network functions virtualization resource processing method and virtualized network function manager

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/091066 WO2017054129A1 (zh) 2015-09-29 2015-09-29 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/940,102 Continuation US20180219793A1 (en) 2015-09-29 2018-03-29 Network functions virtualization resource processing method and virtualized network function manager

Publications (1)

Publication Number Publication Date
WO2017054129A1 true WO2017054129A1 (zh) 2017-04-06

Family

ID=58422597

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/091066 WO2017054129A1 (zh) 2015-09-29 2015-09-29 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器

Country Status (7)

Country Link
US (1) US20180219793A1 (zh)
EP (1) EP3358790B1 (zh)
JP (1) JP6511585B2 (zh)
KR (1) KR20180061299A (zh)
CN (1) CN107005452B (zh)
RU (1) RU2690198C1 (zh)
WO (1) WO2017054129A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108738027A (zh) * 2017-04-25 2018-11-02 华为技术有限公司 一种网络处理方法、资源管理系统及网络设备
EP3661140A4 (en) * 2017-08-18 2020-06-24 Huawei Technologies Co., Ltd. COMMON SERVICE RESOURCE REQUEST METHOD, ASSOCIATED DEVICE, AND SYSTEM

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109491889B (zh) * 2018-10-10 2021-09-24 中国联合网络通信集团有限公司 Nfv中自动化测试的方法和装置
EP4066446B1 (en) 2019-11-25 2024-08-21 Telefonaktiebolaget LM Ericsson (publ) Technique for replacing vnfms in a vnf based environment
US11979289B2 (en) * 2020-04-03 2024-05-07 Nokia Technologies Oy Coordinated control of network automation functions
JP7472677B2 (ja) 2020-06-24 2024-04-23 日本電気株式会社 仮想ネットワーク機能管理装置、管理システム、管理方法及びプログラム
WO2022003953A1 (ja) * 2020-07-03 2022-01-06 日本電信電話株式会社 ネットワーク仮想化システム、仮想リソース管理装置、仮想リソース管理方法およびプログラム
WO2022208754A1 (ja) * 2021-03-31 2022-10-06 日本電気株式会社 管理装置、管理方法及びプログラムが格納されたコンピュータ可読媒体

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN104579732A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 虚拟化网络功能网元的管理方法、装置和系统
WO2015099035A1 (ja) * 2013-12-27 2015-07-02 株式会社Ｎｔｔドコモ 管理システム、仮想通信機能管理ノード及び管理方法

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3650878B2 (ja) * 1999-04-01 2005-05-25 日本電信電話株式会社 ネットワーク装置
AU2003255352A1 (en) * 2003-08-01 2005-02-25 Docomo Communications Laboratories Europe Gmbh Inter-domain handover
RU2468511C2 (ru) * 2008-01-07 2012-11-27 Эл Джи Электроникс Инк. Способ планирования распределенных блоков виртуальных ресурсов
EP2936754B1 (en) * 2013-01-11 2020-12-02 Huawei Technologies Co., Ltd. Network function virtualization for a network device
US9760428B1 (en) * 2013-12-19 2017-09-12 Amdocs Software Systems Limited System, method, and computer program for performing preventative maintenance in a network function virtualization (NFV) based communication network
CN104951353B (zh) * 2014-03-28 2018-09-21 华为技术有限公司 一种对vnf实现加速处理的方法及装置
EP2940582A1 (en) * 2014-04-30 2015-11-04 DoCoMo Communications Laboratories Europe GmbH Automated configuration of virtual infrastructure manager access for the virtual network function manager
US9806975B2 (en) * 2014-06-12 2017-10-31 Futurewei Technologies, Inc. Methods and systems for managing capacity in a virtualized network
US10291689B2 (en) * 2014-08-20 2019-05-14 At&T Intellectual Property I, L.P. Service centric virtual network function architecture for development and deployment of open systems interconnection communication model layer 4 through layer 7 services in a cloud computing system
EP3855681A1 (en) * 2014-09-25 2021-07-28 Apple Inc. Network functions virtualization
AU2016209319B2 (en) * 2015-01-20 2019-01-17 Huawei Technologies Co., Ltd. Method and apparatus for NFV management and orchestration
US9769694B2 (en) * 2015-03-13 2017-09-19 Intel IP Corporation MME overload or underload mitigation by MME VNF apparatus and method
CN107431634B (zh) * 2015-03-30 2020-02-14 华为技术有限公司 一种建立vnfm之间的接口的方法、装置及系统
US10263911B2 (en) * 2015-05-01 2019-04-16 Futurewei Technologies, Inc. System and method for resource management
US9854048B2 (en) * 2015-06-29 2017-12-26 Sprint Communications Company L.P. Network function virtualization (NFV) hardware trust in data communication systems
US20170031986A1 (en) * 2015-07-31 2017-02-02 Huawei Technologies Co., Ltd. Method and System for Providing Integrated Virtualized Database Management and Software Defined Network Topology
US10187324B2 (en) * 2015-08-10 2019-01-22 Futurewei Technologies, Inc. System and method for resource management

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104579732A (zh) * 2013-10-21 2015-04-29 华为技术有限公司 虚拟化网络功能网元的管理方法、装置和系统
WO2015099035A1 (ja) * 2013-12-27 2015-07-02 株式会社Ｎｔｔドコモ 管理システム、仮想通信機能管理ノード及び管理方法
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108738027A (zh) * 2017-04-25 2018-11-02 华为技术有限公司 一种网络处理方法、资源管理系统及网络设备
CN108738027B (zh) * 2017-04-25 2021-05-18 华为技术有限公司 一种网络处理方法、资源管理系统及网络设备
EP3661140A4 (en) * 2017-08-18 2020-06-24 Huawei Technologies Co., Ltd. COMMON SERVICE RESOURCE REQUEST METHOD, ASSOCIATED DEVICE, AND SYSTEM
US11442756B2 (en) 2017-08-18 2022-09-13 Huawei Technologies Co., Ltd. Common service resource application method, related device, and system

Also Published As

Publication number Publication date
KR20180061299A (ko) 2018-06-07
US20180219793A1 (en) 2018-08-02
JP2018531549A (ja) 2018-10-25
CN107005452A (zh) 2017-08-01
RU2690198C1 (ru) 2019-05-31
EP3358790A1 (en) 2018-08-08
EP3358790A4 (en) 2018-11-21
EP3358790B1 (en) 2020-03-18
JP6511585B2 (ja) 2019-05-15
CN107005452B (zh) 2020-07-07

Similar Documents

Publication Publication Date Title
WO2017054129A1 (zh) 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器
US10701139B2 (en) Life cycle management method and apparatus
US10862760B2 (en) Network functions virtualization
US10205719B2 (en) Network function virtualization-based certificate configuration method, apparatus, and system
US10684888B1 (en) Self-organizing server migration to service provider systems
US9485323B1 (en) Managing pooled client-premise resources via provider-defined interfaces
US8321862B2 (en) System for migrating a virtual machine and resource usage data to a chosen target host based on a migration policy
CA2924655C (en) Client-premise resource control via provider-defined interfaces
JP6738965B2 (ja) ネットワークサービスライフサイクル管理許可方法及び装置
JP2018531549A6 (ja) ネットワーク機能仮想化リソース処理方法および仮想化されたネットワーク機能マネージャ
US20170373931A1 (en) Method for updating network service descriptor nsd and apparatus
KR20180002771A (ko) 네트워크 서비스 수명 주기 관리 방법 및 디바이스
JP6568238B2 (ja) ハードウェアアクセラレーション方法及び関連デバイス
US11734172B2 (en) Data transmission method and apparatus using resources in a resource pool of a same NUMA node
US10884880B2 (en) Method for transmitting request message and apparatus
US9342291B1 (en) Distributed update service
WO2017075796A1 (zh) 网络功能虚拟化nfv网络中分配虚拟资源的方法和装置
US9942118B1 (en) Sentinel network devices and sentinel marker
WO2016101639A1 (zh) 负载均衡器的连接方法、业务的实例化部署方法及装置
WO2016179803A1 (zh) 建立vnfm与vim之间的连接的方法、装置及系统
US20230138867A1 (en) Methods for application deployment across multiple computing domains and devices thereof
WO2018014351A1 (zh) 一种资源配置方法及装置
KR102025425B1 (ko) 가상 네트워크 기능 배치를 위한 네트워크 장치 및 그 방법

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2018516167

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20187011984

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2015905041

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2018115309

Country of ref document: RU