WO2018039878A1

WO2018039878A1 - Method, apparatus, and system for managing virtual resource

Info

Publication number: WO2018039878A1
Application number: PCT/CN2016/097195
Authority: WO
Inventors: 王凤宝; 周彦; 季莉
Original assignee: 华为技术有限公司
Priority date: 2016-08-29
Filing date: 2016-08-29
Publication date: 2018-03-08

Abstract

A method, an apparatus, and a system for managing a virtual resource. The system comprises a resource management device and a resource configuration device. The resource configuration device is configured to generate a deployment identifier of a virtual resource, and include the deployment identifier in a virtual resource request to be sent to the resource management device, the deployment identifier being used to represent location information of the virtual resource. The resource management device is configured to receive the virtual resource request sent by the resource configuration device, and manage network elements corresponding to the virtual resource according to the deployment identifier of the virtual resource. In this way, the resource management device can aggregate network elements having the same deployment identifier into the definition of one management plane latitude for the purpose of management and maintenance, where the network elements having the same deployment identifier form a site maintenance view.

Description

Method, device and system for managing virtual resources

Technical field

The embodiments of the present invention relate to the field of communications technologies, and in particular, to a method, an apparatus, and a system for managing virtual resources.

Background technique

Network Function Virtualization (NFV) is a software process that telecom network operators use to carry a lot of functions by using general-purpose hardware such as x86 and virtualization technology. It is implemented in general-purpose high-performance servers, switches, and storage devices. The technology of network functions, thereby reducing the cost of expensive equipment on the network.

The deployment of network elements in a communication network on a virtualization platform is a future development trend. In the network deployment process, in addition to deploying the network on a large data center (DC), due to the wide coverage and distribution of communication nodes. Scenarios, high-bandwidth, and low-latency characteristics, there must be a scenario where a small number of network functions are deployed on a small virtualized device. In this scenario, the operator wants to present an overall representation in the operation and maintenance view.

However, the existing virtual network element model does not define a site model, and cannot reflect multiple network elements or multiple network elements deployed at different sites, and does not aggregate to a management plane latitude definition to manage and maintain, which is inconvenient for operation management and maintain.

Summary of the invention

The embodiment of the invention provides a method, a device and a system for managing a virtual resource, so as to solve the problem that the existing virtual network element model does not define a site model, and cannot be aggregated to a management plane latitude to manage and maintain, which is inconvenient for operation management and Maintenance issues.

The first aspect provides a method for managing a virtual resource, including:

The resource management device receives the virtual resource request sent by the resource configuration device, where the virtual resource request includes a deployment identifier of the virtual resource, where the deployment identifier is used to represent location information of the virtual resource;

The resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource.

When the resource management device receives the virtual resource request, the resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource in the virtual resource request, which facilitates maintenance and management of the network element.

In one possible design, the virtual resource request is an instantiation request or an expansion request or an update request.

In a possible design, the deployment identifier is at least one of the following identifiers: an area identifier, a data center identifier, a host identifier, a virtualized infrastructure manager identifier, an access point identifier, a host shelf identifier, a subrack identifier, and a machine room. Identification, cabinet identification, site identification.

In one possible design, the identification of the virtual resource is generated by the resource configuration device.

In a possible design, when the resource management device is an EM, the resource configuration device is NM or VNFM or VIM or NFVO;

When the resource management device is NM, the resource configuration device is EM or VNFM or VIM or NFVO.

In a possible design, the resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, including:

The resource management device aggregates the network elements corresponding to the virtual resources with the same deployment identifier to the same site for site management.

In this design, the resource management device can aggregate the network elements corresponding to the virtual resources with the same deployment ID to the same site to form a site maintenance view, which facilitates the operation management and maintenance of the network element.

The second aspect provides a management system for a virtual resource, including a resource management device and a resource configuration device, where:

The resource configuration device is configured to generate a deployment identifier of the virtual resource, and send the deployment identifier to the resource management device, where the deployment identifier is used to represent location information of the virtual resource;

The resource management device is configured to receive a virtual resource request sent by the resource configuration device, according to The deployment identifier of the virtual resource manages the network element corresponding to the virtual resource.

The resource management device generates a deployment identifier of the virtual resource, and the deployment identifier is carried in the virtual resource request and sent to the resource management device, where the resource management device is configured according to the management system of the virtual resource. The deployment identifier of the virtual resource manages the network element corresponding to the virtual resource, so that the resource management device aggregates the network element to a management plane latitude definition management and maintenance according to the deployment identifier of the virtual resource in the resource request. For easy operation management and maintenance.

The third aspect provides a virtual resource management apparatus, including:

a receiving unit, configured to receive a virtual resource request sent by the resource configuration device, where the virtual resource request includes a deployment identifier of the virtual resource, where the deployment identifier is used to represent location information of the virtual resource;

The processing unit is configured to manage the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource.

In a possible design, the deployment identifier is at least one of the following identifiers: an area identifier, a data center identifier, a host identifier, a VIM identifier, an access point identifier, a host shelf identifier, a subrack identifier, a machine room identifier, and a cabinet identifier. Site ID.

In a possible design, when the processing unit manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, the processing unit is specifically configured to:

The network elements corresponding to the virtual resources with the same deployment ID are aggregated to the same site for site management.

In a fourth aspect, a resource management device is provided, the resource management device having a function of implementing a resource management device behavior in the foregoing method instance. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, the structure of the resource management device includes a transceiver, a processor, a bus, and a memory, the transceiver is configured to communicate with other devices, and the processor is configured to support the resource. The management device performs the corresponding functions in the above methods. The memory is coupled to the processor, which stores program instructions and data necessary for the resource management device.

According to the resource management method provided by the embodiment of the present invention, when the virtual resource request is initiated, the resource configuration device generates a deployment identifier of the virtual resource, where the deployment identifier is used to represent the location information of the virtual resource, and the deployment identifier is carried in the virtual The resource request is sent to the resource management device, and the resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, so that the resource management device allocates the virtual resource according to the resource identifier in the resource request. The network element is aggregated to a management plane latitude definition to be managed and maintained, which facilitates the operation management and maintenance of the network element.

DRAWINGS

Figure 1 is a schematic diagram of an NFV architecture;

2 is a flowchart of a method for managing a virtual resource according to an embodiment of the present invention;

3 is a flowchart of a method for managing a virtual resource according to an embodiment of the present invention;

4 is a flowchart of a method for managing a virtual resource according to an embodiment of the present invention;

FIG. 5 is a flowchart of a method for managing a virtual resource according to an embodiment of the present invention;

FIG. 6 is a flowchart of a method for managing a virtual resource according to an embodiment of the present invention;

FIG. 7 is a structural diagram of a resource management apparatus according to an embodiment of the present invention;

FIG. 8 is a structural diagram of a resource management device according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are a part of the embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Referring to FIG. 1, an embodiment of the present invention provides a schematic diagram of an NFV architecture. The NFV architecture can implement multiple networks, such as a Local Area Network (LAN), an Internet Protocol (IP) network, or an Evolved Packet Core (EPC) network. As shown in FIG. 1, the NFV architecture may include an NFV Management and Orchestration System (NFV-MANO) 110, an NFV Infrastructure (NFVI) 150, and multiple virtual network functions (Virtualized Network Function, VNF) 140, a plurality of Element Manager (EM) 130, and one or more Operation Support System/Business Support System (OSS/BSS) 120.

The NFV-MANO 110 may include an NFVO Orchestrator (NFVO) 111, one or more VNF Managers (VNFMs) 112, and one or more Virtualized Infrastructure Managers (VIMs). The NFVI 150 may include a hardware resource layer composed of computing hardware 1521, storage hardware 1522, network hardware 1523, a virtualization layer, and a virtual resource layer composed of virtual computing 1511 (eg, virtual machine), virtual storage 1512, and virtual network 1513.

The computing hardware 1521 in the hardware resource layer can be a dedicated processor or a general purpose processor for providing processing and computing functions, such as a Central Process Unit (CPU); the storage hardware 1522 is used to provide storage capabilities, such as , Disk or Network Attached Storage (NAS); network hardware 1523 can be a switch, router, and/or other network device.

The virtualization layer in NFVI 150 is used to abstract the hardware resources of the hardware resource layer, decouple the VNF 140 from the physical layer to which the hardware resources belong, and provide virtual resources to the VNF.

The virtual resource layer may include a virtual computing 1511, a virtual storage 1512, and a virtual network 1513. Virtual computing 1511, virtual storage 1512 may be provided to VNF 140 in the form of a virtual machine or other virtual container, such as one or more virtual machines forming a VNF 140. The virtualization layer forms a virtual network 1513 through abstract network hardware 1523. The virtual network 1513 is configured to implement communication between multiple virtual machines, or between other types of virtual containers that carry VNFs. Virtual network can be created by virtual LAN (Vritual LAN, VLAN), Virtual Private LAN Service (VPLS), Virtual eXtensible Local Area Network (VxLAN) or Universal Routing Encapsulation Network Virtualization (Nerwork) Virtualization using Generic Routing Encapsulation, NVGRE) and other technical implementations.

OSS/BSS 120 is mainly for telecom service operators, providing integrated network management and service operation functions, billing management, and customer service management. OSS/BSS 120 can include Network Manager (NM) 121, which can implement faults. Monitoring, network information collection and other functions.

NFV-MANO 110 can be used to monitor and manage VNF 140 and NFVI 150. The NFVO 111 can communicate with one or more VNFMs 112 to implement resource related requests, send configuration information to the VNFM 112, and collect status information for the VNF 140. In addition, NFVO 111 can also communicate with VIM 113 to enable resource allocation, and/or to implement configuration and status information reservation and exchange of virtualized hardware resources. The VNFM 112 can be used to manage one or more VNFs 140, performing various management functions, such as initializing, updating, querying, and/or terminating the VNF 140. The VIM 113 can be used to control and manage the interaction of the VNF 140 and computing hardware 1521, storage hardware 1522, network hardware 1523, virtual computing 1511, virtual storage 1512, and virtual network 1513. For example, VIM 113 can be used to perform resource allocation operations to VNF 140. VNFM 112 and VIM 113 can communicate with one another to exchange virtualized hardware resource configuration and status information.

NFVI 150 includes both hardware and software that together create a virtualized environment to deploy, manage, and execute VNF 140. In other words, the hardware resource layer and the virtual resource layer are used to provide virtual resources, such as virtual machines and/or other forms of virtual containers, to the VNF 140.

As shown in FIG. 1, VNFM 112 can communicate with VNF 140 and EM 130 to perform VNF lifecycle management and implement exchange of configuration/status information. The VNF 140 is a virtualization of at least one network function that was previously provided by a physical network device. In one implementation, VNF 140 It can be a virtualized Mobility Management Entity (MME) node that provides all the network functions provided by a typical non-virtualized MME device. In another implementation, the VNF 140 can be used to implement the functionality of some of the components provided on the non-virtualized MME device. A VNF 140 may be comprised of one or more Virtual Network Function Components (VNFs), which may be virtual machines or other forms of virtual containers. The EM 130 can be used to manage one or more VNFs 140.

Based on the above discussion of the function of each component in the system architecture of the NFV system, the VNFM 112 is used to perform various management functions on the VNF 140, such as initializing, updating, querying, and terminating the VNF 140, while the VIM 113 is used to control and The management VNF 140 interacts with other parts. Therefore, if a VNF 140 is implemented, the VNFM 112 and the VIM 113 must work together. Therefore, the VNFM 112 and the VIM 113 can communicate with each other to exchange virtualized hardware resource configuration and status information, wherein VNFM 112 and VIM 113 establish a communication connection through the interface.

Hereinafter, some of the terms in the present application will be explained to be understood by those skilled in the art.

Involving the embodiments of the present invention

And/or, describing the association relationship of the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that there are three cases where A exists separately, A and B exist at the same time, and B exists separately. The character "/" generally indicates that the contextual object is an "or" relationship.

In addition, it should be understood that in the description of the present application, the terms "first", "second" and the like are used only to distinguish the purpose of description, and are not to be understood as indicating or implying relative importance, nor as an indication. Or suggest the order.

A method for managing a virtual resource provided by an embodiment of the present invention may be, but is not limited to, used in an NFV architecture as shown in FIG. 1. The method is applied to a resource management device and a resource configuration device NFV architecture, the resource management device may include an EM or an NM, and the resource configuration device may include an EM or NM or VNFM or VIM or NFVO.

Referring to Figure 2, the specific process of the method includes:

Step 20: The resource configuration device generates a deployment identifier of the virtual resource, and carries the deployment identifier. The band is sent to the resource management device in the virtual resource request.

The deployment identifier is used to represent the location information of the virtual resource, and may be one or more resource identifiers (such as a zone identifier (ZONE ID), a data center identifier (DC ID), a host identifier (HOST ID), and a VIM identifier (VIM ID). ), access point identifier (POP ID), host frame identifier (Rack ID), sub-rack ID (sub-rack ID), machine room ID, cabinet ID (bay ID), site ID (site ID); Logical location ID, the same deployment ID represents the same location; different deployment IDs represent different locations.

The virtual resource request is an instantiation request or an expansion request or an update request of the virtual resource.

In a possible implementation, when the resource management device is an EM, the resource configuration device is NM or VNFM or VIM or NFVO;

In a possible implementation manner, when the resource management device is an NM, the resource configuration device is an EM or a VNFM or a VIM or an NFVO.

Step 21: The resource management device receives a virtual resource request sent by the resource configuration device, where the virtual resource request includes a deployment identifier of the virtual resource.

Step 22: The resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource.

Specifically, the resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, including:

The resource management device aggregates the network elements corresponding to the virtual resources of the same deployment identifier to the same site for site management. The aggregation here refers to the resource management device concentrating the network elements corresponding to the virtual resources of the same deployment identifier to one site, and the network elements of the same deployment identifier form a site maintenance view, thereby forming a network topology map of multiple sites, thereby enabling Operation management and maintenance of each network element at a latitude of a management level.

The method in Figure 2 is described in detail below through several different virtual resource request procedures.

Embodiment 1

The instantiation process of the NM application VNF, as shown in FIG. 3, specifically includes the following steps:

30. The NM sends an instantiation request for the VNF to the EM.

31. The EM sends an instantiation request for the VNF to the VNFM.

32. The VNFM feedback operation sends an identification to the EM.

The VNFM sends an authorization request to the NFVO, where the authorization request carries a deployment identifier of the virtual resource of the VNF, and the deployment identifier is generated by the VNFM.

The deployment identifier is used to represent the location information of the virtual resource, and may be one or more resource identifiers (such as ZONE ID, DC ID, HOST ID, VIM ID, POP ID, Rack ID, sub-rack ID, room ID, bay ID, Site ID); can also be a logical location identifier, the same deployment identifier represents the same location; different deployment identifiers represent different locations.

34. The NFVO sends a resource reservation request to the VIM, where the resource reservation request carries the deployment identifier.

The VIM sends a resource reservation response request to the NFVO, where the resource reservation response request carries the deployment identifier. Optionally, step 34 and step 35 may not be performed.

36. The NFVO sends an authorization response request to the VNFM, where the authorization response request carries the deployment identifier.

The VNFM sends a resource allocation request to the VIM, where the resource allocation request carries the deployment identifier.

The VIM sends a resource allocation response request to the VNFM, where the resource allocation response request carries the deployment identifier.

The VNFM sends a VNF lifecycle change notification message to the EM to notify the EM that the instantiation of the VNF is completed, and the lifecycle change notification message carries the deployment identifier.

The EM sends an acknowledgment message to the NM, and confirms that the instantiation of the VNF is completed. The acknowledgment message carries the deployment identifier, so that the NM aggregates the network elements corresponding to the virtual resources of the same deployment identifier into the same network based on the deployment identifier of the virtual resource. Sites, operating management of the same site and different sites.

It should be noted that, in the instantiation process of the VNF in the first embodiment, the deployment identifier may also be generated by the VIM. In this case, the VIM generation is carried in the resource reservation response request in step 35. The deployment identifier, the message request involved in step 30-step 34 does not carry the deployment identifier, That is, the authorization request in step 33 does not carry the deployment identifier, the resource reservation request in step 34 does not carry the deployment identifier, and steps 34 and 35 are steps that must be performed, and other steps are as shown in FIG. 3 above. The steps are the same and will not be described here.

It should be noted that, in the instantiation process of the VNF in the first embodiment, the deployment identifier may also be generated by the VNFO. In this case, the VNFO-generated deployment is carried in the authorization response request in step 36. The identifier is not carried in the message request in step 30-step 35, that is, the authorization request in step 33, the resource reservation request in step 34, and the resource reservation response request in step 35 are not carried. The other steps are the same as those in Figure 3 above, and are not described here.

Embodiment 2

The instantiation process of the NM application NS, as shown in FIG. 4, specifically includes the following steps:

41. The NM sends an instantiation request for the NS to the NFVO.

42. NFVO sends an instantiation request for the VNF to the VNFM.

Before performing step 42, the instantiation process of the NS needs to be decomposed into the instantiation process of the VNF, because the NS is composed of one or more VNFs. When instantiating the NS, the NS template corresponding to the NS needs to be determined. The NS template contains information about which VNFs the NS needs to be. Since the NFVO stores the NSD, the NFVO can determine which VNF the NS should be composed of according to the NSD. Each VNF is then instantiated.

It should be noted that, although not shown in FIG. 4, the instantiation process of the VNF is included between the step 42 and the step 43. For details, refer to step 33 to step 38 in FIG. 3 of the first embodiment, and details are not described herein again.

43. The VNFM sends a VNF Lifecycle Change Notification message to the NFVO, the VNF Lifecycle Change Notification message being used to characterize the instantiation result of the VNF. The VNF lifecycle change notification message carries the deployment identifier of the virtual resource of the VNF, and the deployment identifier is generated by the VNFM.

The NFVO sends an NS lifecycle change notification message to the NM, where the NS lifecycle change notification message is used to represent the instantiation result of the NS, and the NS lifecycle change notification message carries the deployment identifier of the virtual resource of the NS.

The NM sends the NS instantiation confirmation information to the EM, so that the EM aggregates the virtual resources of the same deployment identifier to the same location based on the deployment identifier of the virtual resource, which is convenient for management.

It should be noted that, in the instantiation process of the NS in the second embodiment, the deployment identifier may also be generated by the VNFO. In this case, the VNFO generation is carried in the instantiation request of the VNF in step 42. The deployment identifier is delivered to the EM in the subsequent steps. The other steps are the same as those in Figure 4 above, and are not described here.

It should be noted that, in the instantiation process of the NS in the second embodiment, the deployment identifier may also be generated by the VIM, and the generated deployment identifier is delivered to the EM in a subsequent step, and other steps are as shown in the foregoing figure. The steps in 4 are the same and will not be described here.

Embodiment 3

The NM application VNF expansion and contraction process, as shown in Figure 5, specifically includes the following steps:

50. The NM sends a VNF expansion and contraction request to the EM.

51. The EM sends a VNF extension request to the VNFM.

52. The VNFM feedback operation sends an identification to the EM.

53. VNFM sends an authorization request to NFVO.

54. NFVO sends a resource reservation request to the VIM.

The VIM sends a resource reservation response request to the NFVO, where the resource reservation response request carries the deployment identifier of the virtual resource of the VNF, and the deployment identifier is generated by the VIM.

The NFVO sends an authorization response request to the VNFM, where the authorization response request carries the deployment identifier.

The VIM allocates a response request to the VNFM resource, where the resource allocation response request carries the deployment identifier.

The VNFM sends a VNF lifecycle change notification message to the EM to notify the EM VNF that the expansion and contraction is complete, and the VNF lifecycle change notification message carries the deployment identifier.

510. The EM sends a VNF expansion and contraction confirmation message to the NM to confirm that the expansion and contraction VNF is completed. The VNF expansion and contraction confirmation message carries the deployment identifier, so that the NM aggregates the network elements corresponding to the virtual resources of the same deployment identifier to the same site based on the deployment identifier of the virtual resource, and performs operation management of the same site and different sites.

It should be noted that, in the process of the expansion and contraction of the VNF in the third embodiment, the deployment identifier may also be generated by the VNFO. In this case, the VNFO generation is carried in the resource reservation request in step 54. The deployment identifier is delivered to the NM in the subsequent steps. The other steps are the same as those in Figure 5 above, and are not described here.

It should be noted that, in the process of the expansion and contraction of the VNF in the third embodiment, the deployment identifier may also be generated by the VNFM. In this case, the VNFM generated deployment is carried in the authorization request in step 53. For example, the resource reservation request in step 54 also carries the deployment identifier, and the generated deployment identifier is delivered to the NM in the subsequent step. The other steps are the same as those in the foregoing step 5, and details are not described herein again.

Embodiment 4

The NM application NS expansion and contraction process, as shown in Figure 6, specifically includes the following steps:

61. The NM sends an NS expansion and contraction request to the NFVO.

62. NFVO sends a VNF expansion and contraction request to the VNFM.

Before performing step 62, the expansion and contraction process of the NS needs to be decomposed into the expansion and contraction process of the VNF, because the NS is composed of one or more VNFs. When expanding and shrinking the NS, it is necessary to determine the NS template corresponding to the NS. The NS template contains information about which VNFs the NS needs to be. Since the NFVO stores the NSD, the NFVO can determine which NS should be based on the NSD. The VNF is composed, and then the expansion and contraction is performed for the corresponding VNF according to the expansion and contraction request.

It should be noted that, although not shown in FIG. 6, the expansion and contraction process of the VNF is included between the step 62 and the step 63. For details, refer to step 53 to step 58 in FIG. 5 of the third embodiment, and details are not described herein again.

63. The VNFM sends a VNF lifecycle change notification message to the NFVO, and the VNF lifecycle change notification message is used to notify the VNF of the expansion and contraction result. The VNF lifecycle change notification message carries the deployment identifier of the virtual resource of the VNF, and the deployment identifier is generated by the VNFM.

64. The NFVO sends an NS lifecycle change notification message to the NM, where the NS lifecycle change notification message is used to represent the expansion and contraction result of the NS, and the NS lifecycle change notification message carries the deployment identifier of the virtual resource of the NS.

65. The NM sends the NS expansion and contraction confirmation information to the EM, so that the EM aggregates the virtual resources of the same deployment identifier to the same location based on the deployment identifier of the virtual resource, which is convenient for management.

It should be noted that, in the expansion and contraction process of the NS in the fourth embodiment, the deployment identifier may also be generated by the VNFO. In this case, the VNF expansion and contraction request in the step 62 carries the The deployment identifier generated by the VNFO is delivered to the EM in the subsequent steps. The other steps are the same as those in Figure 6 above, and are not described here.

It should be noted that, in the process of expanding and shrinking the NS of the fourth embodiment, the deployment identifier may also be generated by the VIM, and the generated deployment identifier is delivered to the EM in a subsequent step, and other steps are as follows. The steps in FIG. 6 are the same and will not be described again here.

It should be noted that the update process of the NS is similar to the process of the expansion and contraction of the NS in FIG. 6 , and the difference is that the request for the expansion and contraction of the NS in the step 61 is replaced with the update request of the NS, and other similarities are not described herein again.

Embodiment 5

In the operation of the VNF instantiation process or the VNF expansion process or the NS instantiation process or the NS update process or the NS expansion process, the deployment identifier of the virtual resource may also be generated by the EM or the NM.

If the NM generates the deployment identifier, the NM carries the deployment identifier to the EM in the above operation process. After the EM completes the operation, the EM maps the generated VNF or VNFC to the deployment identifier to facilitate management and maintenance of the management plane.

If the EM generates the deployment identifier, the EM generates the deployment identifier and the newly generated VNF or VNFC to be associated with the mapping in the above operation, and then sends the deployment identifier to the NM in the EM to return confirmation message to the NM, which facilitates management and maintenance of the management plane. ;

The NM manages and maintains the virtualized device based on the deployment ID sent by the EM.

In summary, the deployment identity is passed in the interface between the NM-EMs.

Based on the above embodiment, the embodiment of the present invention further provides a resource management device, where the resource configuration device can implement the resource management method as shown in FIG. 2. Referring to FIG. 7, the resource management device 700 includes: a receiving unit 701. And processing unit 702, wherein

The receiving unit 701 is configured to receive a virtual resource request sent by the resource configuration device, where the virtual resource request includes a deployment identifier of the virtual resource, where the deployment identifier is used to represent location information of the virtual resource;

The processing unit 702 is configured to manage the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource.

Optionally, the virtual resource request is an instantiation request or an expansion request or an update request.

Optionally, the deployment identifier is at least one of the following identifiers: an area identifier, a data center identifier, a host identifier, a VIM identifier, an access point identifier, a host shelf identifier, a subrack identifier, a machine room identifier, a cabinet identifier, and a site identifier.

Optionally, the identifier of the virtual resource is generated by the resource configuration device.

Optionally, when the resource management device is an EM, the resource configuration device is NM or VNFM or VIM or NFVO.

Optionally, when the resource management device is an NM, the resource configuration device is an EM or a VNFM Or VIM or NFVO.

Optionally, when the processing unit 702 manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, the processing unit 702 is specifically configured to:

It should be understood that the division of each unit in the above apparatus 700 is only a division of a logical function, and may be integrated into one physical entity in whole or in part, or may be physically separated. For example, each of the above units may be a separate processing element, or may be integrated in a chip of the resource management device, or may be stored in a storage element of the resource management device in the form of program code, by the resource management device. One of the processing elements invokes and performs the functions of each of the above units. In addition, the individual units can be integrated or implemented independently. The processing elements described herein can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method or each of the above units may be completed by an integrated logic circuit of hardware in the processor element or an instruction in a form of software. The processing element may be a general purpose processor, such as a CPU, or may be one or more integrated circuits configured to implement the above methods, such as one or more ASICs, or one or more DSPs, or one or more FPGA and so on.

It should be noted that the function implementation and the interaction mode of the various units of the apparatus 700 in the embodiment of the present invention may be further referred to the description of the related method embodiments, and details are not described herein again.

Based on the above embodiment, the embodiment of the present invention further provides a resource management device, where the resource management device may include NFVO or VIM or EM or NM or VNFM in the NFV architecture as shown in FIG. As shown in FIG. 8 , the resource management device 800 includes a transceiver 801, a processor 802, a bus 803, and a memory 804, where

The transceiver 801, the processor 802, and the memory 804 are connected to each other through the bus 803; the bus 803 may be a peripheral component interconnect (PCI) bus or an extended industry standard structure. (extended industry standard architecture, referred to as EISA) bus. The bus can be divided into an address bus, a data bus, Control bus, etc. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.

The transceiver 801 is configured to perform communication interaction with other devices connected to the resource management device 800.

The processor 802 is configured to implement the resource management method as shown in FIG. 2 to FIG. 6, and includes:

Receiving a virtual resource request sent by the resource configuration device, where the virtual resource request includes a deployment identifier of the virtual resource, where the deployment identifier is used to represent location information of the virtual resource, and the virtual resource is corresponding to the virtual resource according to the deployment identifier of the virtual resource. The network element is managed.

Optionally, when the resource management device is an NM, the resource configuration device is an EM or a VNFM or a VIM or an NFVO.

Optionally, the processor 802 is specifically configured to:

The memory 804 is configured to store a program or the like. In particular, the program can include program code, the program code including computer operating instructions. The memory 804 may include a random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage. The processor 802 executes the application stored in the memory 804 to implement the above functions, thereby implementing the resource management method as shown in FIGS. 2 to 6.

According to the resource management method provided by the embodiment of the present invention, when the virtual resource request is initiated, the resource configuration device generates a deployment identifier of the virtual resource, where the deployment identifier is used to represent the location information of the virtual resource, and the deployment identifier is carried in the virtual Send the resource request to the resource management device The resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, so that the resource management device aggregates the network element to a management plane latitude according to the deployment identifier of the virtual resource in the resource request. Define management and maintenance to facilitate the operation and maintenance of network elements.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be performed by a program, and the program may be stored in a computer readable storage medium, which is non-transitory ( English: non-transitory) media, such as random access memory, read-only memory, flash memory, hard disk, solid state disk, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), CD (English: optical disc) And any combination thereof.

The present invention has been described with reference to the respective flowcharts and block diagrams of the method and apparatus of the embodiments of the invention. It will be understood that each flow and block of the flowchart illustrations. FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. A device that implements the functions specified in one or more blocks of a flowchart or a plurality of flows and block diagrams.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

A method for managing a virtual resource, comprising:

The resource management device receives the virtual resource request sent by the resource configuration device, where the virtual resource request includes a deployment identifier of the virtual resource, where the deployment identifier is used to represent location information of the virtual resource;

The resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource.
The method of claim 1 wherein the virtual resource request is an instantiation request or an expansion request or an update request.
The method according to claim 1 or 2, wherein the deployment identifier is at least one of the following identifiers: area identifier, data center identifier, host identifier, virtualized infrastructure manager VIM identifier, access point identifier, host Shelf identification, subrack identification, equipment room identification, cabinet identification, site identification.
The method of any of claims 1-3, wherein the identification of the virtual resource is generated by the resource configuration device.
The method according to claim 4, wherein when the resource management device is a network element manager EM, the resource configuration device is a network manager NM or a virtual network function manager VNFM or a virtualized infrastructure management VIM or network function virtualization orchestrator NFVO;

When the resource management device is NM, the resource configuration device is EM or VNFM or VIM or NFVO.
The method according to any one of claims 1-5, wherein the resource management device manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, including:

The resource management device aggregates the network elements corresponding to the virtual resources with the same deployment identifier to the same site for site management.
A management system for a virtual resource, comprising: a resource management device and a resource configuration device,

The resource configuration device is configured to generate a deployment identifier of the virtual resource, and the deployment identifier The carrying is sent to the resource management device in the virtual resource request, where the deployment identifier is used to represent location information of the virtual resource;

The resource management device is configured to receive a virtual resource request sent by the resource configuration device, and manage the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource.
A management device for a virtual resource, comprising:

a receiving unit, configured to receive a virtual resource request sent by the resource configuration device, where the virtual resource request includes a deployment identifier of the virtual resource, where the deployment identifier is used to represent location information of the virtual resource;

The processing unit is configured to manage the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource.
The apparatus of claim 8, wherein the virtual resource request is an instantiation request or an expansion request or an update request.
The device according to claim 8 or 9, wherein the deployment identifier is at least one of the following identifiers: an area identifier, a data center identifier, a host identifier, a virtualized infrastructure manager VIM identifier, an access point identifier, and a host. Shelf identification, subrack identification, equipment room identification, cabinet identification, site identification.
The apparatus according to any one of claims 8 to 10, wherein the identifier of the virtual resource is generated by the resource configuration device.
The apparatus according to claim 11, wherein when the resource management device is a network element manager EM, the resource configuration device is a network manager NM or a virtual network function manager VNFM or a virtualized infrastructure management VIM or network function virtualization orchestrator NFVO;

When the resource management device is NM, the resource configuration device is EM or VNFM or VIM or NFVO.
The device according to any one of claims 8 to 12, wherein, when the processing unit manages the network element corresponding to the virtual resource according to the deployment identifier of the virtual resource, the processing unit is specifically configured to:

Aggregate the NEs corresponding to the virtual resources with the same deployment ID to the same site and perform the site. management.