WO2017012381A1 - 一种生命周期管理方法及装置 - Google Patents

一种生命周期管理方法及装置 Download PDF

Info

Publication number
WO2017012381A1
WO2017012381A1 PCT/CN2016/080138 CN2016080138W WO2017012381A1 WO 2017012381 A1 WO2017012381 A1 WO 2017012381A1 CN 2016080138 W CN2016080138 W CN 2016080138W WO 2017012381 A1 WO2017012381 A1 WO 2017012381A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnf
instance
request
type
lifecycle management
Prior art date
Application number
PCT/CN2016/080138
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 EP16827072.6A priority Critical patent/EP3313023B1/en
Publication of WO2017012381A1 publication Critical patent/WO2017012381A1/zh
Priority to US15/872,507 priority patent/US10701139B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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
    • 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/0894—Policy-based network configuration management
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281—Proxies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/107—Network architectures or network communication protocols for network security for controlling access to devices or network resources wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • 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/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • 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

Definitions

  • the present invention relates to the field of cloud computing technologies, and in particular, to a lifecycle management method and apparatus.
  • Network Function Virtualization (English: Network Function Virtualization, NFV for short) refers to the use of common hardware devices and virtualization technologies to carry the functions of dedicated devices in traditional networks, thereby reducing the expensive cost of deploying dedicated devices.
  • the software is not tied to proprietary hardware, making network device functionality no longer dependent on dedicated hardware.
  • the characteristics of cloud computing are utilized, so that resources can be fully and flexibly shared, and rapid development and deployment of new services can be realized, and automatic deployment, elastic scaling, fault isolation, and self-healing can be performed based on actual business requirements.
  • the party that receives the instantiation request and instantiates the corresponding service according to the request is called a virtualization service provider (referred to as a service provider), and the party that initiates the instantiation request is called Business requester.
  • Virtualized network service in NFV (English: Network Service, NS for short), for example, an IP Multimedia Subsystem (English: IP Multimedia Subsystem, IMS for short) network service, or an evolved packet core network (English: Evolved Packet Core, referred to as: EPC) service.
  • An NS can contain several virtualized network function (VNF) modules, also called virtualized network elements.
  • the VNF is a software implementation of the network functions that can be deployed on the NFV infrastructure.
  • NSD Network Service descriptor
  • Description information (English: VNF descriptor, referred to as information VNFD).
  • VNFD describes the composition of each VNF, such as the softness of the operation. Pieces, virtual resource information, etc.
  • Virtual resources include CPU resources, storage resources, and the like.
  • FIG. 1 is a schematic diagram of an architecture of an NFV system 100 .
  • Network function virtualization orchestrator (English: NFV Orchestrator, referred to as: NFVO) 102, mainly responsible for handling the life cycle management of virtualized services, as well as virtual infrastructure and network function virtualization infrastructure (English: network functions virtualization infrastructure, referred to as: NFVI) allocation and scheduling of virtual resources.
  • the NFVO 102 can communicate with one or more Virtual Network Function Managers (VNFMs) 104 to perform resource related requests, send configuration information to the VNFM 104, and collect status information of the VNF 108.
  • VNFMs Virtual Network Function Managers
  • the NFVO 102 can also communicate with a Virtual Infrastructure Manager (VIM) 106, perform resource allocation, and/or reserve, exchange virtualized hardware resource configuration and status information.
  • VIP Virtual Infrastructure Manager
  • the VNFM 104 is responsible for lifecycle management of one or more VNFs 108, such as instantiating, updating, querying, scaling, and terminating the VNF 108.
  • the VNFM 104 can communicate with the VNF 108 to complete VNF lifecycle management and exchange configuration and status information.
  • the VIM 106 controls and manages the interaction of the VNF 108 with computing hardware 112, storage hardware 114, network hardware 116, virtual computing 118, virtual storage 120, virtual network 122.
  • the VIM 106 performs resource management functions, including managing infrastructure resources, allocating (eg, adding resources to virtual containers), and running functions (eg, collecting NFVI failure information).
  • the VNFM 104 and the VIM 106 can communicate with each other, request resource allocation, and exchange virtualized hardware resource configuration and status information.
  • NFVI is the infrastructure layer of NFV, consisting of hardware components, software components, or a combination of both to establish a virtualized environment, deploy, manage, and implement VNF108.
  • the hardware resources and virtualization layer are used to provide virtualized resources for the VNF 108, such as virtual machines and other forms of virtual containers.
  • Hardware resources include computing hardware 112, storage hardware 114, and network hardware 116. As an embodiment, the resources of computing hardware 112 and storage hardware 114 may be grouped together.
  • the virtualization layer in NFVI can be abstracted Hardware resources that decouple VNF108 from the underlying physical network layer.
  • a plurality of VNFs 108 are configured to virtualize at least one network function.
  • Each VNF runs in a virtual container, corresponding to a set of network functions belonging to one or more physical devices.
  • the equipment management system (EM) 110 is a system for configuring and managing equipment in a conventional telecommunication system.
  • the EM 110 can also be used to configure and manage the VNF 108, as well as initiate new lifecycle management operations such as instantiation of the VNF to the VNFM 104.
  • the Operation Support System and Business Support System (OSS/BSS) 124 supports various end-to-end telecom services.
  • the management functions supported by OSS include: network configuration, service provision, and fault management.
  • BSS handles orders, payments, revenues, etc., supporting product management, order management, revenue management and customer management.
  • the VNFM needs to apply to the NFVO for the VNF instance after receiving the lifecycle management operation request for the VNF instance sent by the EM. Respond to the authorization authority of the lifecycle management operation request. When NFVO agrees to the operation request, VNFM can apply to VIM for the resources required for the operation request.
  • NFVO needs to manage multiple VNFMs at the same time, and each VNFM may manage multiple VNFs, so the number of operations involved in lifecycle management is large. Therefore, the burden of NFVO is large.
  • the present invention provides a lifecycle management method and apparatus for solving the technical problem that the burden of the authorized subject is large each time the application for the authorization lifecycle management operation needs to be applied to the authorized entity in the prior art.
  • a first aspect of the present invention provides a lifecycle management method, including:
  • a resource operation request is initiated to the virtual infrastructure manager VIM, the resource operation request including the instance ID.
  • the method before the receiving a lifecycle management operation request for the first virtualized network function VNF instance, the method further includes:
  • the proxy authorization request is used to request the authorized entity to authorize all lifecycle management operations of the first VNF instance;
  • proxy authorization policy information sent by the authorization entity, where the proxy authorization policy information is used to indicate a type of authorized lifecycle management operation
  • the method before the receiving the lifecycle management operation request for the first virtualized network function VNF instance, the method further includes:
  • the instantiating request further includes a proxy authorization request, the proxy authorization request is used to request the authorized subject to perform lifecycle management other than instantiation of the first VNF instance Operation for authorization.
  • the method further includes:
  • the location relationship is a positional relationship between the VNF corresponding to the first VNF instance and an instance of another VNF;
  • the method further includes:
  • Determining normal operation of other VNFs according to the VNFD depends on normal operation of the VNF; wherein the other VNFs and the VNFs are managed by the same virtual network function manager VNFM;
  • An operation related to the type of operation is initiated for an instance of the other VNF.
  • a second aspect of the present invention provides a method for determining a proxy authorization policy, including:
  • the proxy authorization request is used to request authorization for a lifecycle management operation of the first virtual network function VNF instance;
  • VNFD VNF description information
  • the policy information is used to indicate the type of operation.
  • the proxy authorization request is carried in an instantiation request for obtaining the first VNF instance, where the proxy authorization request is used to request a pair The lifecycle management operations of the first VNF instance other than instantiation are authorized.
  • the method further includes:
  • the ID of the physical host and the location relationship are provided to the VIM through the VNFM.
  • the dependency relationship is: Whether the VNF and the other VNF are managed by the same VNFM, and the normal operation of the other VNFs Depending on the normal operation of the VNF, or the normal operation of the VNF depends on the normal operation of the other VNFs;
  • the location relationship is that the instance of the VNF and the other VNFs must be deployed on the same physical host, or the instances of the VNF and the other VNFs cannot be deployed on the same physical host at the same time.
  • the operation type is an operation type that does not affect the dependency relationship and/or the location relationship, After performing the operation corresponding to the operation type on the first VNF instance, the other VNFs that depend on the VNF are still able to operate normally, and/or perform the operation type on the first VNF instance. After the corresponding operation, the positional relationship between the VNF and the instances of the other VNFs is not exclusive.
  • the performing according to the description in the VNFD The dependency and/or location relationship between the VNF and other VNFs, determining the types of operations that can be delegated for authorization in all lifecycle management operations for the first VNF instance, including:
  • the type of operation capable of proxy authorization is a type of all lifecycle management operations when normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are both managed by the VNFM; or
  • the type of operation capable of proxy authorization is a type of other lifecycle management operations other than migration.
  • a third aspect of the present invention provides a computer apparatus, including:
  • a receiving unit configured to receive a lifecycle management operation request for the first virtualized network function VNF instance, where the lifecycle management operation request includes an instance identifier ID of the first VNF instance and an operation type;
  • a processing unit configured to determine, according to a correspondence between an instance ID of the VNF instance and a type of a lifecycle management operation, that the operation type is in a type of a lifecycle management operation corresponding to the instance ID, where The type of lifecycle management operation indicates that the type of the lifecycle management operation has been authorized by the authorized principal;
  • a sending unit configured to initiate a resource operation request to the virtual infrastructure manager VIM, where the resource operation request includes the instance ID.
  • the sending unit is further configured to: before the receiving unit receives a lifecycle management operation request for the first virtualized network function VNF instance, Sending a proxy authorization request to the authorized entity; the proxy authorization request is used to request the authorized entity to authorize all lifecycle management operations of the first VNF instance;
  • the receiving unit is further configured to: receive proxy authorization policy information sent by the authorized entity, where the proxy authorization policy information is used to indicate a type of an authorized lifecycle management operation;
  • the processing unit is further configured to: generate the correspondence according to the instance ID and the proxy authorization policy information.
  • the sending unit is further configured to: before the receiving unit receives a lifecycle management operation request for the first virtualized network function VNF instance, Sending an instantiation request to the authorized entity; the instantiating request further includes a proxy authorization request, the proxy authorization request is used to request the authorized subject to perform lifecycle management other than instantiation of the first VNF instance Operation for authorization.
  • the receiving unit is further configured to: after the method unit sends an instantiation request to the authorized entity Receiving a location relationship sent by the authorized entity and an ID of the physical host corresponding to the location relationship; the location relationship is a location relationship between the VNF corresponding to the first VNF instance and an instance of another VNF;
  • the sending unit is further configured to: send an ID of the physical host to the VIM.
  • the processing unit is further configured to: in the determining the operation type, the lifecycle management corresponding to the instance ID After the type of operation, obtaining the VNFD of the VNF corresponding to the first VNF instance; determining that the normal operation of the other VNF is dependent on the normal operation of the VNF according to the VNFD; wherein the other VNF is the same as the VNF Virtual Network Function Manager VNFM Management; initiates operations related to the type of operation for instances of the other VNFs.
  • a fourth aspect of the present invention provides a computer apparatus, including:
  • a receiving unit configured to receive a proxy authorization request sent by the virtual network function manager VNFM, where the proxy authorization request is used to request authorization for a lifecycle management operation of the first virtual network function VNF instance;
  • a processing unit configured to acquire VNF description information VNFD of the VNF corresponding to the first VNF instance, and determine, according to the dependency relationship and/or the location relationship between the VNF and the other VNFs described in the VNFD, An operation type capable of proxying authorization in all lifecycle management operations of a VNF instance; the operation type being an operation type that does not affect the dependency relationship and/or the location relationship;
  • a sending unit configured to send proxy authorization policy information to the VNFM, where the policy information is used to indicate the operation type.
  • the proxy authorization request is carried in an instantiation request for obtaining the first VNF instance, where the proxy authorization request is used to request a pair The lifecycle management operations of the first VNF instance other than instantiation are authorized.
  • the sending unit is further configured to: after the receiving unit receives the instantiation request, according to The location relationship, sending a query request to the virtual infrastructure manager VIM to request an ID of a physical host deployed by an instance of the second VNF having a positional relationship with the VNF; wherein the query request includes the An instance ID of an instance of the second VNF;
  • the receiving unit is further configured to: receive an ID of the physical host that is sent by the VIM;
  • the sending unit is further configured to: provide an ID of the physical host and the location relationship to the VIM through the VNFM.
  • the dependency relationship is: Whether the VNF and the other VNF are managed by the same VNFM, and the normal operation of the other VNF depends on the normal operation of the VNF, or the normal operation of the VNF depends on the normal operation of the other VNF;
  • the location relationship is that the instance of the VNF and the other VNFs must be deployed on the same physical host, or the instances of the VNF and the other VNFs cannot be deployed on the same physical host at the same time.
  • the operation type is an operation type that does not affect the dependency relationship and/or the location relationship, After performing the operation corresponding to the operation type on the first VNF instance, the other VNFs that depend on the VNF are still able to operate normally, and/or perform the operation type on the first VNF instance. After the corresponding operation, the positional relationship between the VNF and the instances of the other VNFs is not exclusive.
  • the processing unit is configured to: when the other The normal operation of the VNF depends on the VNF, and when the other VNF and the VNF are managed by different VNFMs, it is determined that the type of operation capable of proxy authorization is other lifecycle management operations except shutdown and elastic contraction. Type; or
  • the type of operation capable of proxy authorization is a type of all lifecycle management operations when normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are both managed by the VNFM; or
  • the type of operation capable of proxy authorization is a type of other lifecycle management operations other than migration.
  • a fifth aspect of the present invention provides a network element for lifecycle management, including:
  • a memory for storing computer executable program code
  • a processor coupled to the memory and the transceiver
  • program code includes instructions that, when the processor executes the instructions, cause the network element to perform the following operations:
  • a lifecycle management operation request for the first virtualized network function VNF instance including an instance identifier ID of the first VNF instance and an operation type; and an instance ID according to the VNF instance
  • determining that the operation type is in a type of a lifecycle management operation corresponding to the instance ID corresponds to the instance ID
  • a type of the lifecycle management operation in the correspondence relationship represents the life cycle
  • the type of management operation has been authorized by the authorized principal; and a resource operation request is initiated by the transceiver to the virtual infrastructure manager VIM, the resource operation request including the instance ID.
  • the instruction when the processor executes the instruction, the instruction causes the network element to further perform the following operations:
  • the proxy authorization request is for requesting the authorization
  • the principal authorizes all lifecycle management operations of the first VNF instance; receiving, by the transceiver, proxy authorization policy information sent by the authorization entity, where the proxy authorization policy information is used to indicate an authorized lifecycle management operation Type: generating the correspondence according to the instance ID and the proxy authorization policy information.
  • the instruction when the processor executes the instruction, the instruction causes the network element to further perform the following operations:
  • the instantiation request further includes a proxy authorization request,
  • the proxy authorization request is for requesting the authorized subject to the first Authorization of a lifecycle management operation other than instantiation of a VNF instance.
  • the instruction when the processor executes the instruction, the instruction causes the network element to perform the following operations :
  • the location relationship is the first a positional relationship between the VNF corresponding to the VNF instance and other instances of the VNF; the ID of the physical host is sent to the VIM by the transceiver.
  • the instruction causes the network element to further perform the following operations:
  • the VNFD of the VNF corresponding to the first VNF instance After the determining that the operation type is in the type of the lifecycle management operation corresponding to the instance ID, acquiring the VNFD of the VNF corresponding to the first VNF instance; determining, according to the VNFD, that the normal operation of the other VNF depends on the The normal operation of the VNF; wherein the other VNFs and the VNF are managed by the same virtual network function manager VNFM; operations related to the type of operation are initiated for instances of the other VNFs.
  • a sixth aspect of the present invention provides a network element, a memory, for storing a proxy authorization policy, for storing computer executable program code;
  • a processor coupled to the memory and the transceiver
  • program code includes instructions that, when the processor executes the instructions, cause the network element to perform the following operations:
  • a proxy authorization request sent by the virtual network function manager VNFM is used to request authorization for a lifecycle management operation of the first virtual network function VNF instance; and acquiring the first VNF instance corresponding to VNF description information VNFD of the VNF; determining, according to the dependency and/or location relationship between the VNF and other VNFs described in the VNFD, capable of proxy authorization in all lifecycle management operations for the first VNF instance Type of operation;
  • the operation type is an operation type that does not affect the dependency relationship and/or the location relationship; the proxy authorization policy information is sent to the VNFM by the transceiver; the policy information is used to indicate the operation type.
  • the proxy authorization request is carried in an instantiation request for obtaining the first VNF instance, where the proxy authorization request is used to request a pair The lifecycle management operations of the first VNF instance other than instantiation are authorized.
  • the instruction when the processor executes the instruction, the instruction causes the network element to perform the following operations :
  • the transceiver After receiving the instantiation request by the transceiver, sending a query request to the virtual infrastructure manager VIM according to the location relationship to request an instance of the second VNF having a positional relationship with the VNF An ID of the deployed physical host; wherein the query request includes an instance ID of an instance of the second VNF; receiving, by the transceiver, an ID of the physical host sent by the VIM; and an ID of the physical host And the location relationship is provided to the VIM by the VNFM.
  • the dependency relationship is: Whether the VNF and the other VNF are managed by the same VNFM, and the normal operation of the other VNF depends on the normal operation of the VNF, or the normal operation of the VNF depends on the normal operation of the other VNF;
  • the location relationship is that the instance of the VNF and the other VNFs must be deployed on the same physical host, or the instances of the VNF and the other VNFs cannot be deployed on the same physical host at the same time.
  • the operation type is an operation type that does not affect the dependency relationship and/or the location relationship, After performing the operation corresponding to the operation type on the first VNF instance, the other VNFs that depend on the VNF are still able to operate normally, and/or perform the operation type on the first VNF instance. After the corresponding operation, the positional relationship between the VNF and the instances of the other VNFs is not exclusive.
  • the processor executes the instruction
  • the instructions cause the network element to also perform the following operations:
  • the type of operation capable of proxy authorization is a type of all lifecycle management operations when normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are both managed by the VNFM; or
  • the type of operation capable of proxy authorization is a type of other lifecycle management operations other than migration.
  • the operation type carried by the operation request is determined according to the instance ID in the correspondence between the instance ID and the type of the lifecycle management operation.
  • the type of the lifecycle management operation corresponding to the instance ID wherein the type of the lifecycle management operation in the correspondence indicates that the type of the lifecycle management operation has been authorized by the authorized subject. Therefore, it is possible to initiate a resource operation request directly to the VIM without requesting an authorization operation from the authorization body.
  • the resource can be directly requested from the VIM as long as the operation type of the subsequent request is in the type authorized by the authorized entity.
  • the operation does not require authorization from the authorized principal, and waits for authorization to request resource operations from the VIM. Therefore, the burden on the authorized subject can be reduced.
  • the processing time of the lifecycle management operation request is shortened, and the business processing efficiency is improved.
  • FIG. 1 is an architectural diagram of a NFV system in the prior art
  • FIG. 2 is a flowchart of a lifecycle management method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a method for determining a proxy authorization policy according to an embodiment of the present invention
  • 4a-4b are schematic diagrams showing a dependency relationship and a position relationship between VNFs according to an embodiment of the present invention.
  • FIG. 5 is an example interaction diagram of a lifecycle management method according to an embodiment of the present invention.
  • FIG. 6 is a simplified functional block diagram of a computer device according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a network element according to an embodiment of the present invention.
  • the embodiments of the present invention provide a lifecycle management method and apparatus, which are used to solve the technical problem that the burden of the authorized subject is large each time the application for the authorization lifecycle management operation needs to be applied to the authorized entity in the prior art.
  • first and second are used herein for convenience of description, and are used to distinguish between different VNFs or different VNF instances, and have no technical meaning.
  • the network system to which the method can be applied is, for example, the NFV system 100 as shown in FIG.
  • the execution body of the method may be the VNFM 104 as shown in FIG.
  • the method includes the following:
  • Step 101 Receive a lifecycle management operation request for a first VNF instance, where the lifecycle management operation request includes an instance identifier (ID) of the first VNF instance and an operation type.
  • ID instance identifier
  • Step 102 Determine, according to the correspondence between the instance ID of the VNF instance and the type of the lifecycle management operation, the operation type in the type of the lifecycle management operation corresponding to the instance ID, where the life cycle in the correspondence relationship
  • the type of management operation indicates that the type of the lifecycle management operation has been authorized by the authorized principal
  • Step 103 Initiate a resource operation request to the VIM, where the resource operation request includes the instance ID.
  • the lifecycle management operation request may be sent by the EM or sent by the OSS and/or the BSS.
  • Operation types can include: query, elastic shrinkage, elastic expansion, repair, migration, software update, shutdown.
  • the format of the request can be:
  • VNF VNF1instance ID//VNF1 instance ID
  • the authorized subject is, for example, NFVO 102.
  • the corresponding relationship is stored in the VNFM 104, for example, in step 102, the instance ID of the first VNF instance is used to match in the corresponding relationship, and the type of the lifecycle management operation corresponding to the instance ID is determined to include the step 101. Type of operation.
  • the authorized operation types corresponding to the instance ID of the first VNF instance include: query, elastic contraction, elastic expansion, repair, and software update. It can be seen that the type of operation requested in step 101 is among the types of operations that have been authorized, so step 103 can be directly executed next.
  • a resource operation request is initiated to the VIM, the resource request including the instance ID.
  • the resource operation request is used to enable the VIM to perform resource operations corresponding to the operation type on the first VNF instance. Further, if the operation type in step 101 is not closed, but other operations that require a resource request, the request may further include resource information of resources required by the operation type, such as 4 CPUs and 4 GB of memory.
  • the VIM in this embodiment is, for example, the VIM 106 in FIG.
  • the method execution body shown in FIG. 2 can obtain the correspondence between the instance ID and the type of the lifecycle management operation. Therefore, as long as it is determined that the operation type in the lifecycle management operation request is in the operation type authorized by the instance ID of the first VNF instance, the resource operation can be directly requested from the VIM without sending an authorization request to the authorized entity, thereby reducing the authorization.
  • the burden on the main body can also shorten the processing time of the operation request and provide the efficiency of business processing.
  • the resource update success response sent by the VIM is also received.
  • the first VNF instance is then configured based on the updated resources, such as running a business script on the updated resource.
  • the notification information is sent to the authorized entity to notify the authorized entity that the lifecycle management operation is performed on the first VNF instance and the resource information currently occupied by the first VNF instance.
  • the notification information includes an operation type of the lifecycle management operation and resource information currently occupied by the first VNF instance.
  • the format of the notification information can be:
  • step 101 when the operation type in step 101 is not in the authorized operation type, an authorization request is sent to the authorized entity to request the authorized entity to authorize the operation type in step 101.
  • This part of the content is well known to those skilled in the art, so it will not be described here.
  • a possible implementation manner is: before step 101, the method further includes: sending an authorization to the authorized entity And sending a proxy authorization request; the proxy authorization request is used to request the authorized entity to authorize the lifecycle management operation of the first VNF instance; and receive the proxy authorization policy information sent by the authorized entity, where the proxy authorization policy information is used to indicate the authorized life. a type of periodic management operation; generating the correspondence based on the instance ID and the proxy authorization policy information.
  • the proxy authorization request can be included in the instantiation request.
  • the instantiation request includes an ID of a VNFD of the VNF corresponding to the first VNF instance to obtain a first VNF instance.
  • the instantiation request further includes the proxy authorization request for requesting the authorized entity to authorize other lifecycle management operations of the first VNF instance other than instantiation.
  • the format of the instantiation request can be:
  • VNFD ID// represents the VNF information involved in the request.
  • ID of the VNFD of the VNF corresponding to the first VNF instance is
  • the proxy authorization request can be issued just before step 101.
  • the proxy authorization request is used to request the authorized entity to authorize all lifecycle management operations of the first VNF instance.
  • the proxy authorization request is sent after the first VNF instance has been obtained, the proxy authorization request is used to request the authorized entity to authorize other lifecycle management operations other than instantiation of the first VNF instance.
  • the ID of the VNFD of the VNF corresponding to the first VNF instance is included in the proxy authorization request. In order to facilitate the authorization subject to perform the type of operation that allows the proxy authorization for the first VNF instance. determine.
  • the received proxy authorization policy information is used to indicate the type of the authorized lifecycle management operation. Therefore, in actual use, the proxy authorization policy information may be an indication information, or may be an operation type that allows the proxy authorization, or is not allowed. The type of operation authorized by the agent.
  • the indication information is, for example, "full delegated", indicating that all lifecycle management operation types allow proxy authorization.
  • the corresponding relationship may be generated based on the instance ID of the first VNF instance and the proxy authorization policy information.
  • the correspondence can be stored in the form of a table. It is also possible to write the proxy authorization policy information in the attribute information of the first VNF instance.
  • the authorized entity simultaneously authorizes multiple operation types to the execution subject of the method shown in FIG. 2, such as the VNFM 104, in one authorization process. Therefore, the burden on the authorized subject can be greatly reduced, and the message interaction between the authorized subject and the VNFM 104 can be reduced.
  • the present invention does not exclude the manner of authorizing multiple operation types multiple times, for example, when requesting authorization from the authorized entity when the first time the lifecycle management operation request is received, the authorized entity allows the agent to authorize, in addition to continuing execution.
  • the proxy authorization policy information is also returned to the VNFM 104, and the proxy authorization policy information indicates that the VNFM 104 is allowed to manage the operation type in the operation request, and if the operation request of the operation type is received for the second time, the direct Requesting resources from the VIM without requesting authorization from the authorization principal can reduce the burden on the authorized principal and reduce the amount of authorization for the authorized entity each time the same type of operation request is received in the prior art.
  • Message interaction between the authorized principal and the VNFM 104 After all lifecycle management operations request authorization from the authorization principal once, all the types of operations that allow the proxy authorization are obtained, and the corresponding relationship is generated.
  • step 102 Another possible implementation manner of the corresponding relationship in step 102 is that the corresponding relationship is predetermined, or is agreed, or is sent to the authorized subject and executed by the method described in FIG. 2 after being determined by other third party entities. main body.
  • FIG. 3 includes:
  • Step 201 Receive a proxy authorization request sent by the VNFM, where the proxy authorization request is used to request authorization for a lifecycle management operation of the first VNF instance.
  • Step 202 Obtain a VNFD of the VNF corresponding to the first VNF instance.
  • Step 203 Determine, according to a dependency relationship and/or a location relationship between the VNF and the other VNFs described in the VNFD, an operation type capable of proxy authorization in all lifecycle management operations for the first VNF instance; the operation type is An operation type that does not affect the dependency relationship and/or the location relationship;
  • Step 204 Send proxy authorization policy information to the VNFM, where the policy information is used to indicate the operation type.
  • the VNFD of the VNF corresponding to the first VNF instance is obtained in step 202.
  • the manner of obtaining the VNFD is slightly different according to the timing of sending the proxy authorization request in step 201.
  • the proxy authorization request is carried in the instantiation request for obtaining the first VNF instance in step 201
  • the ID of the VNFD of the VNF is carried in the instantiation request, so the authorized subject can
  • the VNFD is obtained according to the ID of the VNFD.
  • the proxy authorization request may carry the instance ID of the first VNF instance, so the authorized entity may obtain the VNFD of the corresponding VNF according to the instance ID.
  • VNFD The dependence and/or positional relationship between the VNF and other VNFs is described in VNFD.
  • the dependency between the VNF and other VNFs means that the normal operation of the VNF depends on the normal operation of other VNFs, or the normal operation of other VNFs depends on the normal operation of the VNF. Further, the dependencies also include whether the VNF and other VNFs are managed by the same VNFM.
  • the location relationship between the VNF and other VNFs is specifically that the instances of the VNF and other VNFs must be deployed on the same physical host, or the instances of the VNF and other VNFs cannot be deployed on the same physical host at the same time.
  • an operation type capable of proxy authorization in all lifecycle management operations for the first VNF instance may be determined according to the dependency relationship, or all lifecycle management operations for the first VNF instance may be determined according to the location relationship.
  • the type of operation that can proxy authorization. Can also be The types of operations capable of proxy authorization in all lifecycle management operations for the first VNF instance are determined in conjunction with the dependencies and location relationships.
  • All lifecycle management operations for the first VNF instance refer to all lifecycle management operations that the first VNF instance can support, such as query, elastic reduction, elastic expansion, repair, migration, software update, and shutdown.
  • the determined operation type is an operation type that does not affect the dependency relationship and/or the location relationship.
  • the operation type is an operation type that does not affect the dependency relationship and/or the location relationship, and is configured to depend on the VNF after performing the operation corresponding to the operation type on the first VNF instance. After the other VNFs are still able to operate normally, and/or the operation corresponding to the operation type is performed on the first VNF instance, the positional relationship between the VNF and the instances of the other VNFs is not exclusive.
  • step 203 includes: determining that the proxy can be authorized when the normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are managed by different VNFMs.
  • the type of operation is the type of lifecycle management operation other than shutdown, elastic contraction; or
  • the type of operation capable of proxy authorization is a type of all lifecycle management operations when normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are both managed by the VNFM; or
  • the type of operation capable of proxy authorization is a type of other lifecycle management operations other than migration.
  • VNF1 and VNF2 are managed by VNFM2.
  • VNF3 and VNF4 are managed by VNFM1.
  • VNF1 depends on VNF2. That is, the normal operation of VNF1 depends on the operation of VNF2.
  • VNF2 must exist, and resources must be above a certain value, such as 2 CPUs, 2 GB of memory, and so on. Therefore, when VNF2 is turned off or elastically contracted, it will definitely affect the operation of VNF1.
  • VNF1 is relied on by VNF3, that is, the normal operation of VNF3 depends on the normal operation of VNF1.
  • the first VNF instance in this embodiment is an instance of VNF2. Since VNF1 is dependent on VNF2, the shutdown or elastic contraction of the first VNF instance must affect the operation of VNF1. However, both VNF1 and VNF2 are managed by VNFM2, so when the type of operation for the first VNF instance is off or elastically contracted, VNFM2 can operate according to the dependency, for example when the first VNF instance is elastically contracted. , also elastic contraction of VNF1. Therefore, in step 203, it is determined that the types of operations capable of proxy authorization in all lifecycle management operations for the first VNF instance are query, elastic contraction, elastic expansion, repair, software update, migration, and shutdown. That is, when these operations are subsequently performed for the first VNF instance, there is no need to request authorization from the authorization principal, but the resource can be directly requested from the VIM.
  • the method further includes: acquiring the VNFD of the VNF corresponding to the first VNF instance; determining whether the normal operation of the other VNF depends on the normal operation of the VNF according to the VNFD;
  • the other VNFs are managed by the same VNFM as the VNF; it is determined whether the type of operation in step 101 affects the normal operation of other VNFs, and if so, the operations related to the types of operations are also initiated for instances of other VNFs. For example, when the type of operation in step 101 is elastic contraction, an elastic contraction operation is also initiated on the other VNFs. In order to maintain the dependence of the other VNFs on the VNF, the other VNFs are not inoperable due to the result of managing the first VNF instance.
  • the first VNF instance in this embodiment is an instance of VNF1. Since VNF1 is dependent on VNF3, and VNF1 and VNF3 are respectively managed by different VNFMs, when VNFM2 is on VNF1 instance, the first VNF instance is closed or elastically contracted. During operation, VNFM1 cannot know the relevant operation and will definitely affect the operation of VNF3. In this case, since all VNFMs are managed by NFVO, when VNFM2 needs to shut down or elastically shrink VNF1, it must first apply for authorization to NFVO. Therefore, at this time, NFVO cannot delegate all lifecycle management operations to VNFM2, so the types of operations that can be authorized are: query, elastic expansion, repair, software update, and migration.
  • VNF1 and VNF2 have a position dependency, that is, a requirement An instance of VNF1 and an instance of VNF2 are deployed on the same physical host.
  • VNF3 and VNF1 have a position exclusion relationship, that is, VNF3 and VNF4 are required to be deployed on different physical hosts.
  • VNF1 has a positional dependency with VNF2
  • migration operations for instances of VNF1 and VNF2 may result in a change in the location dependency of VNF1 and VNF2, so the migration operation requires authorization from the authorized principal.
  • migration operations for instances of VNF3 and VNF4 may also result in changes in the location exclusion relationship between the two, so the migration operation also requires authorization from the authorization principal. Therefore, the types of operations that are allowed to be authorized by the proxy in step 203 include: query, elastic contraction, elastic expansion, repair, software update, and shutdown. Does not include migration operations.
  • proxy authorization policy information is generated and the proxy authorization policy information is sent to the VNFM.
  • the proxy authorization policy information is used to indicate the operation type.
  • the query request is further sent to the VIM according to the location relationship, such as a location dependency or a location exclusion relationship, to request a corresponding to the first VNF instance.
  • the ID of the physical host deployed by the instance of the second VNF that has a positional relationship between the VNFs.
  • the instance ID of the instance of the second VNF is included in the query request.
  • the VIM queries the ID of the deployed physical host according to the instance ID of the second VNF, and returns the ID of the physical host to the authorized principal.
  • the authorized principal then sends the ID of the physical host to the VNFM.
  • the ID of the sending physical host and the proxy authorization policy information are sent in the same message and sent to the VNFM.
  • the format is for example:
  • GrantType Partial delegated ⁇ Scale-up/out,Scale-in/down,Query,hell,update ⁇ //Allows the proxy authorization type to be partial authorization, and allows the proxy to authorize the operation type: elastic expansion, elastic contraction, query, repair , software update, shutdown
  • the VNFM After receiving the ID of the physical host, the VNFM sends the ID of the physical host and the location relationship to the VIM.
  • the VIM allocates resources to the first VNF instance based on the ID of the physical host and the location relationship.
  • the VIM allocates resources for the first VNF instance on the physical host. If the physical host is a physical host corresponding to the location exclusion relationship, the VIM selects to allocate resources for the first VNF instance on other physical hosts than the physical host.
  • the method includes:
  • Step 301 The EM sends an operation request for elastic expansion to the VNFM, where the request carries the instance ID of the first VNF instance; the format of the request is as follows:
  • VNF2instance ID//The first VNF instance is an instance of VNF2, instance ID
  • Step 302 The VNFM searches the database according to the instance ID whether the elastic expansion is in the scope of the operation type that allows the proxy authorization. If not, the step 303 to the step 311 are performed. If so, steps 308 through 310 and step 312 are performed.
  • Step 303 The VNFM sends an elastic expansion operation authorization request to the NFVO; the format of the request is, for example:
  • VNF VNF2instance ID//Instance ID of the first VNF instance
  • Step 304 NFVO verifies whether the requested resource can be allocated; if it can be allocated, step 305 is performed:
  • Step 305 NFVO applies for resource reservation to VIM
  • Step 306 The VIM returns a resource reservation success response to the NFVO.
  • Step 307 NFVO returns an authorization success response to the VNFM.
  • Step 308 The VNFM requests the VIM to request resources for elastic expansion.
  • Step 309 The VIM sends a resource update success response message to the VNFM.
  • Step 310 The VNFM configures the updated resource, for example, running a service script on the updated resource.
  • Step 311 The VNFM notifies the NFVO resource that the update is successful.
  • Step 312 The VNFM notifies the NFVO to perform the elastic expansion operation and the resource information currently occupied by the first VNF instance.
  • the format of the notification message is as follows:
  • Steps 303 to 311 are the processes in the prior art, which are well known to those skilled in the art, and therefore will not be described in detail.
  • step 301 when the type of operation requested in step 301 is an operation type that the VNFM can proxy, the steps 308 to 310 and step 312 are directly performed, and steps 303 to 307 are omitted.
  • the burden of NFVO is greatly reduced, and the processing time of life cycle management operations can be shortened, and the business processing efficiency can be improved.
  • FIG. 6 is a simplified functional block diagram of a computer device according to an embodiment of the present invention.
  • Computer loaded The device includes a receiving unit 401, a processing unit 402, and a transmitting unit 403.
  • unit as used herein, without limitation, may refer to an application-specific integrated circuit (ASIC), electronic circuit, (shared, dedicated or group) processor, and memory that executes one or more software or firmware programs. Combining logic circuits, and/or other suitable components that provide the described functionality.
  • ASIC application-specific integrated circuit
  • the computer device is used to implement the method as shown in FIG. 2 and/or FIG. 3, and the specific configuration may be determined according to actual needs.
  • the receiving unit 401 is configured to receive a lifecycle management operation request for the first virtualized network function VNF instance, where the life is The period management operation request includes an instance identifier ID of the first VNF instance and an operation type
  • the processing unit 402 is configured to determine, according to the correspondence between the instance ID of the VNF instance and the type of the lifecycle management operation, that the operation type is The type of the lifecycle management operation corresponding to the instance ID; wherein the type of the lifecycle management operation in the correspondence indicates that the type of the lifecycle management operation has been authorized by the authorized entity; and the sending unit 403 is configured to the virtual base
  • the facility manager VIM initiates a resource operation request, the resource operation request including the instance ID. And causing the VIM to perform resource operations corresponding to the operation type on the first VNF instance according to the instance ID.
  • the sending unit 403 is further configured to: before the receiving unit 401 receives the lifecycle management operation request for the first virtualized network function VNF instance, send a proxy authorization request to the authorized entity; the proxy authorization request And the receiving unit 401 is further configured to: receive the proxy authorization policy information sent by the authorized entity, where the proxy authorization policy information is used to request the authorization entity to authorize all lifecycle management operations of the first VNF instance; The type of the lifecycle management operation of the authorization is indicated; the processing unit 402 is further configured to: generate the correspondence according to the instance ID and the proxy authorization policy information.
  • the sending unit 403 is further configured to: before the receiving unit 401 receives the lifecycle management operation request for the first VNF instance, send an instantiation request to the authorized entity; the instantiation request further includes a proxy authorization request, The proxy authorization request is used to request the authorized subject to the first Authorization of other lifecycle management operations of the VNF instance other than instantiation.
  • the receiving unit 401 is further configured to: after the method unit sends the instantiation request to the authorized entity, receive a location relationship sent by the authorized entity and an ID of the physical host corresponding to the location relationship;
  • the location relationship is a location relationship between the VNF corresponding to the first VNF instance and an instance of the other VNF;
  • the sending unit 403 is further configured to: send the ID of the physical host to the VIM, so that the VIM is based on The ID of the physical host and the location relationship allocate resources for the first VNF instance.
  • the processing unit 402 is further configured to: after determining that the operation type is in a type of the lifecycle management operation corresponding to the instance ID, acquiring a VNFD of the VNF corresponding to the first VNF instance; The VNFD determines that normal operation of other VNFs is dependent on normal operation of the VNF; wherein the other VNFs are managed by the same VNFM as the VNFs; operations related to the type of operation are initiated for instances of the other VNFs.
  • the receiving unit 401 is configured to receive a proxy authorization request sent by the virtual network function manager VNFM, where the proxy authorization request is used to request a pair.
  • the first virtual network function VNF instance lifecycle management operation is authorized;
  • the processing unit 402 is configured to acquire the VNF description information VNFD of the VNF corresponding to the first VNF instance; according to the VNF described in the VNFD and other VNFs Between the dependencies and/or the location relationships, determining the types of operations that are capable of proxy authorization in all lifecycle management operations for the first VNF instance; the types of operations are not affecting the dependencies and/or the locations The operation type of the relationship; the sending unit 403 is configured to send proxy authorization policy information to the VNFM, where the policy information is used to indicate the operation type.
  • the proxy authorization request is carried in an instantiation request for obtaining the first VNF instance, where the proxy authorization request is used to request a life cycle other than instantiation of the first VNF instance.
  • Manage operations for authorization are carried in an instantiation request for obtaining the first VNF instance, where the proxy authorization request is used to request a life cycle other than instantiation of the first VNF instance.
  • the sending unit 403 is further configured to: after the receiving unit 401 receives the instantiation request, send a query request to the virtual infrastructure manager VIM according to the location relationship, to request An ID of a physical host deployed by an instance of a second VNF having a positional relationship with the VNF; wherein the query request includes an instance ID of an instance of the second VNF; and the receiving unit 401 is further configured to: receive The ID of the physical host sent by the VIM; the sending unit 403 is further configured to: provide the ID of the physical host and the location relationship to the VIM by using the VNFM.
  • providing the ID of the physical host and the location relationship to the VIM by using the VNFM includes: sending an ID of the physical host and the location relationship to the VNFM, where the VNFM The ID of the physical host and the location relationship are sent to the VIM. Then, the VIM allocates resources to the first VNF instance based on the ID of the physical host and the location relationship.
  • the processing unit 402 is configured to: when the normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are managed by different VNFMs, determine that the type of operation capable of proxy authorization is The type of lifecycle management operations other than shutdown, elastic contraction; or
  • the type of operation capable of proxy authorization is a type of all lifecycle management operations when normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are both managed by the VNFM; or
  • the type of operation capable of proxy authorization is a type of other lifecycle management operations other than migration.
  • FIG. 7 is a schematic structural diagram of a network element in an embodiment of the present invention.
  • This network element is used to transfer or process data in the NFV system 100 shown in FIG.
  • the network element 500 is used to create, modify, relocate, and/or migrate one or more virtual machines.
  • Network element 500 can also be used to host, store, and/or perform one or more network functions.
  • the network element 500 can be a sub-component of the NFV system 100 of FIG. 1, such as NFVO 102 or VNFM 104.
  • Network element 500 can include one or more ports 512 coupled to a transceiver 510.
  • Transceiver 510 can be a transmitter, a receiver, or a combination thereof that transmits or receives data packets from other network nodes through port 512.
  • Processor 502 is coupled to transceiver 510 for processing data packets and determining which nodes transmit data packets.
  • Processor 502 can include one or more multi-core processors and/or memory 504.
  • the processor 502 can be a general-purpose processor, an application specific integrated circuit (ASIC), or a digital signal processor (DSP).
  • ASIC application specific integrated circuit
  • DSP digital signal processor
  • Memory 504 can be a non-transitory storage medium coupled to processor 502 for storing different types of data.
  • the memory 504 may include a read only memory (English: Read Only Memory, ROM for short), a random access memory (English: Random Access Memory, RAM for short), or other types of dynamic storage devices that can store information and instructions. Is a disk storage.
  • Memory 504 can be used to hold instructions that implement an NFV system or related methods, such as VNFM 104, VNF 108, NFVO 102.
  • the memory 504 can include an NFV module 506 that can be executed on the processor 502.
  • the NFV module 506 can be used to host, store, and implement network functions of one or more virtualized network devices.
  • the memory 504 can also include an NFV orchestration module 508 for creating, modifying, relocating, and/or migrating one or more virtual machines. It will be appreciated that by programming or loading executable instructions to at least one of processor 502, cache and long term storage of network element 500, network element 500 can be converted to a particular device, such as a router, switch.
  • Network element 500 can implement the functionality of one or more VNFs and execute one or more instructions in accordance with embodiments of the present invention. These instructions may be stored in the memory 504 or integrated into the kernel of the operating system of the network element 500 or a plug-in of the kernel.
  • the network element 500 can implement the method as shown in FIG. 2 and/or FIG. 3, and the specific configuration can be determined according to actual needs.
  • the instruction causes the network element 500 to perform the following operations: receiving, by the transceiver 510, the first virtual The lifecycle management operation request of the network function VNF instance, the lifecycle management operation request includes an instance identification ID of the first VNF instance and an operation type; Corresponding relationship between the instance ID and the type of the lifecycle management operation, determining that the operation type is in a type of a lifecycle management operation corresponding to the instance ID; wherein, the type representation of the lifecycle management operation in the correspondence relationship The type of lifecycle management operation has been authorized by the authorized principal; and a resource operation request is initiated by the transceiver 510 to the virtual infrastructure manager VIM, the resource operation request including the instance ID. And causing the VIM to perform resource operations corresponding to the operation type on the first VNF instance according to the instance ID.
  • the instruction when the processor 502 executes the instruction, the instruction causes the network element 500 to further perform the following operations:
  • the proxy authorization request is for requesting the authorized principal pair All the lifecycle management operations of the first VNF instance are authorized; the proxy authorization policy information sent by the authorized entity is received by the transceiver 510, where the proxy authorization policy information is used to indicate the type of the authorized lifecycle management operation; The instance ID and the proxy authorization policy information generate the corresponding relationship.
  • the instruction when the processor 502 executes the instruction, the instruction causes the network element 500 to further perform the following operations:
  • the instantiation request further includes a proxy authorization request,
  • the proxy authorization request is used to request the authorized entity to authorize other lifecycle management operations of the first VNF instance other than instantiation.
  • the instruction when the processor 502 executes the instruction, the instruction causes the network element 500 to further perform the following operations:
  • the location relationship sent by the authorized entity and the ID of the physical host corresponding to the location relationship are received by the transceiver; the location relationship is the first VNF The location relationship between the VNF corresponding to the instance and the instance of the other VNF; the ID of the physical host is sent to the VIM through the transceiver 510. To make the VIM based on The ID of the physical host and the location relationship allocate resources for the first VNF instance.
  • the instruction when the processor 502 executes the instruction, the instruction causes the network element 500 to further perform the following operations:
  • the VNFD of the VNF corresponding to the first VNF instance After the determining that the operation type is in the type of the lifecycle management operation corresponding to the instance ID, acquiring the VNFD of the VNF corresponding to the first VNF instance; determining, according to the VNFD, that the normal operation of the other VNF depends on the The normal operation of the VNF; wherein the other VNFs and the VNF are managed by the same virtual network function manager VNFM; operations related to the type of operation are initiated for instances of the other VNFs.
  • the instruction causes the network element 500 to perform the following operations:
  • a proxy authorization request sent by the virtual network function manager VNFM is used to request authorization for a lifecycle management operation of the first virtual network function VNF instance; and acquiring the first VNF instance corresponding to the VNF description information VNFD of the VNF; determining, according to the dependency and/or location relationship between the VNF and the other VNFs described in the VNFD, capable of proxy authorization in all lifecycle management operations for the first VNF instance An operation type; the operation type is an operation type that does not affect the dependency relationship and/or the location relationship; the proxy authorization policy information is sent to the VNFM through the transceiver 510; the policy information is used to indicate the operation type .
  • the proxy authorization request is carried in an instantiation request for obtaining the first VNF instance, where the proxy authorization request is used to request a life cycle other than instantiation of the first VNF instance.
  • Manage operations for authorization are carried in an instantiation request for obtaining the first VNF instance, where the proxy authorization request is used to request a life cycle other than instantiation of the first VNF instance.
  • the instruction when the processor 502 executes the instruction, the instruction causes the network element 500 to further perform the following operations:
  • the transceiver 510 After receiving the instantiation request by the transceiver 510, sending a query request to the virtual infrastructure manager VIM according to the location relationship to request deployment of an instance of the second VNF having a positional relationship with the VNF ID of the physical host; wherein the query request includes the second VNF An instance ID of the instance; receiving, by the transceiver 510, an ID of the physical host sent by the VIM; providing the ID of the physical host and the location relationship to the VIM through the VNFM.
  • the ID of the physical host and the location relationship are sent to the VNFM, so that the VNFM sends the ID of the physical host and the location relationship to the VIM, where the VIM is based on the The ID of the physical host and the location relationship allocate resources for the first VNF instance.
  • the dependency relationship is: whether the VNF and the other VNF are managed by the same VNFM, and normal operation of the other VNF depends on normal operation of the VNF, or the normal operation of the VNF depends on Normal operation of the other VNFs;
  • the location relationship is that the instance of the VNF and the other VNFs must be deployed on the same physical host, or the instances of the VNF and the other VNFs cannot be deployed on the same physical host at the same time.
  • the operation type is an operation type that does not affect the dependency relationship and/or the location relationship, and is: after performing the operation corresponding to the operation type on the first VNF instance, depending on the location
  • the other VNFs of the VNF are still able to operate normally, and/or the location relationship between the VNF and the instances of the other VNFs is not repelled after the operation corresponding to the operation type is performed on the first VNF instance. .
  • the instruction when the processor 502 executes the instruction, the instruction causes the network element 500 to further perform the following operations:
  • the type of operation capable of proxy authorization is a type of all lifecycle management operations when normal operation of the other VNF is dependent on the VNF, and the other VNF and the VNF are both managed by the VNFM; or
  • the type of operation capable of proxy authorization is a type of other lifecycle management operations other than migration.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

本发明提供一种生命周期管理方法及装置，该方法包括：接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。

Description

一种生命周期管理方法及装置
本申请要求于2015年7月20日提交中国专利局、申请号为201510429123.1，发明名称为“一种生命周期管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及云算机技术领域，尤其涉及一种生命周期管理方法及装置。
背景技术
网络功能虚拟化(英文：Network Function Virtualization，简称：NFV)，指通过使用通用的硬件设备及虚拟化技术，来承载传统网络中专用设备的功能，从而降低部署专用设备带来的昂贵成本。软件不与专有硬件绑定，使网络设备功能不再依赖于专用硬件。同时利用云计算的特点，使资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。在NFV的架构中，接收实例化请求，并根据请求对相应业务进行实例化处理(部署业务)的一方，称为虚拟化业务提供方(简称业务提供方)，发起实例化请求的一方称为业务请求方。
NFV中虚拟化的网络服务(英文：Network Service，简称：NS)，举例来说，可以是一个IP多媒体子系统(英文：IP Multimedia Subsystem，简称：IMS)网络服务，或一个演进型分组核心网(英文：Evolved Packet Core，简称：EPC)服务。一个NS中可以包含若干个虚拟化网络功能(virtualized Network Function，VNF)模块，也称为虚拟化网元。VNF是可部署在NFV基础架构上的网络功能的软件实现。一个NS在进行虚拟化部署时，业务请求方首先需要向业务提供方提交该网络业务的描述信息(英文：Network Service descriptor，简称：NSD)，主要描述该网络业务的拓扑结构以及包含的各个VNF的描述信息(英文：VNF descriptor，简称信息VNFD)。VNFD描述了每个VNF的构成，比如运行的软 件，需要的虚拟资源信息等。虚拟资源包括CPU资源，存储资源等。
请参考如图1，为一种NFV系统100的架构示意图。
网络功能虚拟化编排器(英文：NFV Orchestrator，简称：NFVO)102，主要负责处理虚拟化业务的生命周期管理，以及虚拟基础设施及网络功能虚拟化基础设施(英文：network functions virtualization infrastructure，简称：NFVI)中虚拟资源的分配和调度等。NFVO102可以与一个或多个虚拟网络功能管理器(英文：Virtualized Network Function Manager，简称：VNFM)104通信，以执行资源相关请求，发送配置信息给VNFM104，收集VNF108的状态信息。另外，NFVO102也可与虚拟基础设施管理器(英文：Virtualized Infrastructure Manager,简称：VIM)106通信，执行资源分配，和/或预留，交换虚拟化硬件资源配置和状态信息。
VNFM104，负责一个或多个VNF108的生命周期管理，比如实例化(instantiating)，更新(updating)，查询，弹性伸缩(scaling)，终止(terminating)VNF108。VNFM104可以与VNF108通信以完成VNF生命周期管理及交换配置和状态信息。在NFV架构中VNFM可以有多个，负责对不同类型的VNF进行生命周期管理。
VIM106，控制和管理VNF108与计算硬件112、存储硬件114、网络硬件116、虚拟计算(virtual computing)118、虚拟存储120、虚拟网络122的交互。例如VIM106执行资源管理功能，包括管理基础设施资源、分配(例如增加资源给虚拟容器)及运行功能(例如收集NFVI故障信息)。VNFM104及VIM106可以相互通信，请求资源分配，交换虚拟化硬件资源配置和状态信息。
NFVI即NFV的基础设施层，包含硬件部件，软件部件或两者组合，以建立虚拟化环境，部署，管理及实现VNF108。硬件资源和虚拟化层用于为VNF108提供虚拟化资源，如虚拟机和其他形式的虚拟容器。硬件资源包括计算(computing)硬件112，存储硬件114，网络硬件116。作为一种实施方式，计算硬件112和存储硬件114的资源可以集中在一起。NFVI中的虚拟化层可以抽象 硬件资源，解耦VNF108与底层的物理网络层。
多个VNF108，被配置成至少一种网络功能的虚拟化。每个VNF运行在一个虚拟容器中，对应于一组属于一个或多个物理设备的网络功能。
设备管理系统(EM)110，是传统电信系统中用于对设备进行配置，管理的系统。在NFV架构中，EM110也可以用于对VNF108进行配置和管理，以及向VNFM104发起新的VNF的实例化等生命周期管理操作。
运营支持系统和业务支持系统(英文：Operations Support System and Business Support System，简称：OSS/BSS)124，支持各种端到端电信业务。OSS支持的管理功能包括：网络配置，业务提供，故障管理等。BSS处理订单，付费，收入等，支持产品管理，订单管理，收益管理及客户管理。
在现有的NFV架构中，由于NFVO需要对资源作全局控制，所以VNFM在收到EM发送的针对某个VNF实例的生命周期管理操作请求之后，需要先向NFVO申请对所述某个VNF实例响应所述生命周期管理操作请求的授权权限。当NFVO同意该操作请求后，VNFM才可以向VIM申请该操作请求所需的资源。
然而，一个NFVO需要同时管理多个VNFM，每个VNFM又可能管理多个VNF，所以涉及生命周期管理的操作数量是很大的。因此，NFVO的负担较大。
发明内容
本发明提供一种生命周期管理方法及装置，用以解决现有技术中每次都需要向授权主体申请授权生命周期管理操作而导致授权主体的负担较大的技术问题。
本发明第一方面提供了一种生命周期管理方法，包括：
接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；
根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应 关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；
向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。
结合第一方面，在第一方面的第一种可能的实现方式中，在所述接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，所述方法还包括：
向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；
接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；
基于所述实例ID及所述代理授权策略信息生成所述对应关系。
结合第一方面，在第一方面的第二种可能的实现方式中，在所述接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，所述方法还包括：
向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
结合第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述向所述授权主体发送实例化请求之后，所述方法还包括：
接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；
将所述物理主机的ID发送给所述VIM。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第三种可能的实现方式中的任意一种，在第一方面的第四种可能的实现方式中，在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，所述方法还包括：
获取所述第一VNF实例对应的VNF的VNFD；
根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一虚拟网络功能管理器VNFM管理；
针对所述其它VNF的实例发起与所述操作类型相关的操作。
本发明第二方面提供一种代理授权策略的确定方法，包括：
接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；
获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；
根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；
向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
结合第二方面，在第二方面的第一种可能的实现方式中，所述代理授权请求携带在用于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
结合第二方面的第一种可能的实现方式，在第二方面的第二种可能的实现方式中，在接收到所述实例化请求之后，所述方法还包括：
根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的实例的实例ID；
接收所述VIM发送的所述物理主机的ID；
将所述物理主机的ID以及所述位置关系通过所述VNFM提供给所述VIM。
结合第二方面或第二方面的第一种可能的实现方式或第二方面的第二种可能的实现方式，在第二方面的第三种可能的实现方式中，所述依赖关系为：所述VNF与所述其它VNF是否由同一VNFM管理，以及所述其它VNF的正常运行依 赖于所述VNF的正常运行，或所述VNF的正常运行依赖于所述其它VNF的正常运行；
所述位置关系为所述VNF同所述其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同所述其它VNF的实例不能同时部署在同一个物理主机上。
结合第二方面的第三种可能的实现方式，在第二方面的第四种可能的实现方式中，所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
结合第二方面的第三种可能的实现方式或第二方面的第四种可能的实现方式，在第二方面的第五种可能的实现方式中，所述根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型，包括：
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
本发明第三方面提供一种计算机装置，包括：
接收单元，用于接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；
处理单元，用于根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；
发送单元，用于向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。
结合第三方面，在第三方面的第一种可能的实现方式中，所述发送单元还用于：在所述接收单元接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；
所述接收单元还用于：接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；
所述处理单元还用于：基于所述实例ID及所述代理授权策略信息生成所述对应关系。
结合第三方面，在第三方面的第二种可能的实现方式中，所述发送单元还用于：在所述接收单元接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
结合第三方面的第二种可能的实现方式，在第三方面的第三种可能的实现方式中，所述接收单元还用于：在所述方法单元向所述授权主体发送实例化请求之后，接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；
所述发送单元还用于：将所述物理主机的ID发送给所述VIM。
结合第三方面或第三方面的第一种可能的实现方式至第三方面的第三种可 能的实现方式中的任意一种，在第三方面的第四种可能的实现方式中，所述处理单元还用于：在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，获取所述第一VNF实例对应的VNF的VNFD；根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一虚拟网络功能管理器VNFM管理；针对所述其它VNF的实例发起与所述操作类型相关的操作。
本发明第四方面提供一种计算机装置，包括：
接收单元，用于接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；
处理单元，用于获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；
发送单元，用于向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
结合第四方面，在第四方面的第一种可能的实现方式中，所述代理授权请求携带在用于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
结合第四方面的第一种可能的实现方式，在第四方面的第二种可能的实现方式中，所述发送单元还用于：在所述接收单元接收到所述实例化请求之后，根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的实例的实例ID；
所述接收单元还用于：接收所述VIM发送的所述物理主机的ID；
所述发送单元还用于：将所述物理主机的ID以及所述位置关系通过所述VNFM提供给所述VIM。
结合第四方面或第四方面的第一种可能的实现方式或第四方面的第二种可能的实现方式，在第四方面的第三种可能的实现方式中，所述依赖关系为：所述VNF与所述其它VNF是否由同一VNFM管理，以及所述其它VNF的正常运行依赖于所述VNF的正常运行，或所述VNF的正常运行依赖于所述其它VNF的正常运行；
所述位置关系为所述VNF同所述其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同所述其它VNF的实例不能同时部署在同一个物理主机上。
结合第四方面的第三种可能的实现方式，在第四方面的第四种可能的实现方式中，所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
结合第四方面的第三种可能的实现方式或第四方面的第四种可能的实现方式，在第四方面的第五种可能的实现方式中，所述处理单元用于：当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
本发明第五方面提供一种用于生命周期管理的网元，包括：
存储器，用于存储计算机可执行程序代码；
收发器，以及
处理器，与所述存储器和所述收发器耦合；
其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：
通过所述收发器接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；并通过所述收发器向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。
结合第五方面，在第五方面的第一种可能的实现方式中，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
在通过所述收发器接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，通过所述收发器向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；通过所述收发器接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；基于所述实例ID及所述代理授权策略信息生成所述对应关系。
结合第五方面，在第五方面的第二种可能的实现方式中，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
在通过所述收发器接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，通过所述收发器向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第 一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
结合第五方面的第二种可能的实现方式，在第五方面的第三种可能的实现方式中，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
在通过所述收发器向所述授权主体发送实例化请求之后，通过收发器接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；通过所述收发器将所述物理主机的ID发送给所述VIM。
结合第五方面或第五方面的第一种可能的实现至第五方面的第三种可能的实现方式中的任意一种，在第五方面的第四种可能的实现方式中，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，获取所述第一VNF实例对应的VNF的VNFD；根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一虚拟网络功能管理器VNFM管理；针对所述其它VNF的实例发起与所述操作类型相关的操作。
本发明第六方面提供一种用于确定代理授权策略的网元，存储器，用于存储计算机可执行程序代码；
收发器，以及
处理器，与所述存储器和所述收发器耦合；
其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：
通过所述收发器接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型； 所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；通过所述收发器向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
结合第六方面，在第六方面的第一种可能的实现方式中，所述代理授权请求携带在用于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
结合第六方面的第一种可能的实现方式，在第六方面的第二种可能的实现方式中，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
在通过所述收发器接收到所述实例化请求之后，根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的实例的实例ID；通过所述收发器接收所述VIM发送的所述物理主机的ID；将所述物理主机的ID以及所述位置关系通过所述VNFM提供给所述VIM。
结合第六方面或第六方面的第一种可能的实现方式或第六方面的第二种可能的实现方式，在第六方面的第三种可能的实现方式中，所述依赖关系为：所述VNF与所述其它VNF是否由同一VNFM管理，以及所述其它VNF的正常运行依赖于所述VNF的正常运行，或所述VNF的正常运行依赖于所述其它VNF的正常运行；
所述位置关系为所述VNF同所述其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同所述其它VNF的实例不能同时部署在同一个物理主机上。
结合第六方面的第三种可能的实现方式，在第六方面的第四种可能的实现方式中，所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
结合第六方面的第三种可能的实现方式或第六方面的第四种可能的实现方式，在第六方面的第五种可能的实现方式中，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
本发明实施例中提供的一个或多个技术方案，至少具有如下技术效果或优点：
本发明实施例中，当接收到一个针对第一VNF实例的生命周期管理操作请求时，根据实例ID在实例ID与生命周期管理操作的类型的对应关系中确定，所述操作请求携带的操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权。因此，就可以直接向VIM发起资源操作请求，而不用再去向授权主体请求授权操作。换言之，在本发明实施例中，对于已经获得授权主体授权的对第一VNF实例的生命周期管理操作类型，只要后续请求的操作类型在授权主体已经授权的类型中，就可以直接向VIM请求资源操作，而不需要向授权主体请求授权，等到授权之后再去向VIM请求资源操作。因此，可以减少授权主体的负担。同时也缩短了对生命周期管理操作请求的处理时间，提高了业务处理效率。
附图说明
图1为现有技术中NFV系统的架构图；
图2为本发明实施例提供的一种生命周期管理方法的流程图；
图3为本发明实施例提供的一种代理授权策略的确定方法的流程图；
图4a-图4b为本发明实施例提供的VNF之间的依赖关系以及位置关系示意图；
图5为本发明实施例提供的一种生命周期管理方法的实例交互图；
图6为本发明实施例提供的一种计算机装置的简化功能框图；
图7为本发明实施例提供的一种网元的结构示意图。
具体实施方式
本发明实施例提供一种生命周期管理方法及装置，用以解决现有技术中每次都需要向授权主体申请授权生命周期管理操作而导致授权主体的负担较大的技术问题。
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
另外，在本文中术语“第一”、“第二”仅仅是为了便于描述，用来区分不同VNF或不同VNF实例，并没有技术含义。
下面结合附图对本发明优选的实施方式进行详细说明。
请参考图2所示，为本发明一实施例提供的一种生命周期管理方法的流程 图。该方法可以应用的网络系统例如如图1所示的NFV系统100。该方法的执行主体可以是如图1所示的VNFM104。该方法包括以下内容：
步骤101：接收针对第一VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识(ID)以及操作类型；
步骤102：根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；
步骤103：向VIM发起资源操作请求，所述资源操作请求包括所述实例ID。
其中，在步骤101中，生命周期管理操作请求可以是EM发送的，或者是OSS和/或BSS发送的。操作类型可以包括：查询、弹性缩容、弹性扩容、修复、迁移、软件更新、关闭。
该请求的格式可以为：
Scale out：//操作类型为弹性扩容
VNF：VNF1instance ID//VNF1的实例ID
Resource：//弹性扩容所需资源
CPU：4//CPU4个
Memory：4GB//内存4GB
授权主体例如是NFVO102。所述对应关系例如存储在VNFM104中，在步骤102中，利用第一VNF实例的实例ID在所述对应关系中进行匹配，确定该实例ID对应的生命周期管理操作的类型中包括步骤101中的操作类型。
举例来说，假设步骤101中的操作类型为弹性扩容，第一VNF实例的实例ID对应的已被授权的操作类型包括：查询、弹性缩容、弹性扩容、修复、软件更新。由此可见，步骤101中请求的操作类型在已被授权的操作类型当中，所以接下来可以直接执行步骤103。
在步骤103中，向VIM发起资源操作请求，所述资源请求包括所述实例ID。 所述资源操作请求用于使得所述VIM对所述第一VNF实例进行与所述操作类型对应的资源操作。进一步，如果步骤101中的操作类型不是关闭，而是其它需要请求资源的操作，那么该请求中还可以包括该操作类型所需资源的资源信息，如需要CPU4个、内存4GB。本实施例中的VIM例如为图1中的VIM106。
由此可见，图2所示方法执行主体侧能够获得实例ID与生命周期管理操作的类型的对应关系。所以只要确定生命周期管理操作请求中的操作类型在第一VNF实例的实例ID已授权的操作类型中，即可直接向VIM请求资源操作，而不需向授权主体发送授权请求，所以减轻了授权主体的负担，同时也能缩短对该操作请求的处理时间，提供业务处理的效率。
可选的，在步骤103之后，还接收VIM发送的资源更新成功响应。然后基于更新后的资源对第一VNF实例进行配置，例如在更新的资源上运行业务脚本等。
可选的，在对第一VNF实例进行了配置之后，还向授权主体发送通知信息，以通知授权主体针对第一VNF实例进行了生命周期管理操作以及第一VNF实例当前所占用的资源信息。该通知信息包括生命周期管理操作的操作类型、第一VNF实例当前所占用的资源信息。举例来说，该通知信息的格式可以为：
Notification：//通知
Operation：scale out//操作类型为弹性扩容
Resource://资源信息
CPU：4//CPU4个
Memory：4GB//内存4GB
需要说明的是，当步骤101中的操作类型没有在已授权的操作类型中，那么就向授权主体发送授权请求，以请求授权主体对步骤101中的操作类型进行授权。该部分内容为本领域技术人员所熟知的内容，所以在此不再赘述。
接下来将详细描述步骤102中对应关系的生成过程。
一种可能的实现方式为：在步骤101之前，该方法还包括：向授权主体发 送代理授权请求；代理授权请求用于请求授权主体对第一VNF实例的生命周期管理操作进行授权；接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；基于所述实例ID及所述代理授权策略信息生成所述对应关系。
具体的，代理授权请求可以包含在实例化请求中。所述实例化请求中包括第一VNF实例对应的VNF的VNFD的ID以获得第一VNF实例。该实例化请求还包括所述代理授权请求，用于请求所述授权主体对第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。举例来说，该实例化请求的格式可以为：
Grant lifecycle operation://代表该消息是一个生命周期管理授权请求
VNF:VNFD ID//代表该请求所涉及的VNF信息，本实施例中为第一VNF实例对应的VNF的VNFD的ID
Operation:instantiate//该请求所涉及的生命周期管理操作是一个实例化操作
Required resource://实例化操作所需的资源
CPU:2//CPU2个
Memory:2GB//内存2GB
Delegation:active//代理授权请求，请求除实例化以外的其它生命周期周期管理操作的授权
当然，在实际运用中，代理授权请求只要在步骤101之前发出即可。当代理授权请求是在发送上述实例化请求之前发的，那么该代理授权请求用于请求授权主体对第一VNF实例的所有生命周期管理操作进行授权。当代理授权请求是在已经得到第一VNF实例之后才发的，那么该代理授权请求用于请求授权主体对第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
在这两种情况下，在代理授权请求中包括第一VNF实例所对应的VNF的VNFD的ID。以便于授权主体对第一VNF实例进行允许代理授权的操作类型的 确定。
接收的代理授权策略信息用于指示授权的生命周期管理操作的类型，所以在实际运用中，代理授权策略信息可以是一个指示信息，也可以是列举了允许代理授权的操作类型，或者是不允许代理授权的操作类型。指示信息例如为“full delegated”，表示所有生命周期管理操作类型都允许代理授权。
在接收到代理授权策略信息之后，就可以基于第一VNF实例的实例ID及代理授权策略信息生成所述对应关系。该对应关系可以以表格的形式进行存储。也可以是将代理授权策略信息写在第一VNF实例的属性信息中。
在本实施例中，授权主体在一次授权过程中，同时授权多个操作类型给图2所示方法的执行主体，如VNFM104。因此，可以较大的减轻授权主体的负担，也减少了授权主体与VNFM104之间的消息交互。
在实际运用中，本发明也不排除多次授权多个操作类型的方式，例如在第一次收到生命周期管理操作请求时，向授权主体请求授权，授权主体允许代理授权的话，除了继续执行授权流程外，还向VNFM104返回代理授权策略信息，代理授权策略信息指示允许VNFM104对该生命周期管理操作请求中的操作类型，如果在第二次收到该操作类型的操作请求时，就可以直接向VIM请求资源，而不用再向授权主体请求授权，相比现有技术中每次收到同样类型的操作请求都要向授权主体请求授权的方案而言，也能减轻授权主体的负担以及减少授权主体与VNFM104之间的消息交互。当所有生命周期管理操作都向授权主体请求授权过一次之后，就可以获得全部允许代理授权的操作类型了，进而生成所述对应关系。
步骤102中对应关系的另一种可能的实现方式为：所述对应关系是预定的，或者是约定的，或者是由其它第三方主体确定之后下发给授权主体以及图2所述方法的执行主体。
以下将从授权主体的角度来描述代理授权策略信息的生成过程。具体请参考图3所示，该方法包括：
步骤201：接收VNFM发送的代理授权请求；所述代理授权请求用于请求对第一VNF实例的生命周期管理操作进行授权；
步骤202：获取第一VNF实例对应的VNF的VNFD；
步骤203：根据VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；
步骤204：向VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
具体的，在步骤202中获取第一VNF实例对应的VNF的VNFD，根据步骤201中发送代理授权请求的时机不同，获取VNFD的方式会稍有不同。举例来说，当在步骤201中，代理授权请求携带在用于获得第一VNF实例的实例化请求中，那么在实例化请求中就会携带所述VNF的VNFD的ID，所以授权主体就可以根据VNFD的ID获取到VNFD。如果代理授权请求是在第一VNF实例已经实例化成功之后，代理授权请求可以携带第一VNF实例的实例ID，所以授权主体可以根据实例ID获取到对应的VNF的VNFD。
VNFD中描述有所述VNF同其它VNF之间的依赖关系和/或位置关系。VNF同其它VNF之间的依赖关系，具体是指所述VNF的正常运行依赖于其它VNF的正常运行，或者是其它VNF的正常运行依赖于所述VNF的正常运行。进一步，依赖关系还包括所述VNF和其它VNF是否由同一VNFM的管理。
VNF和其它VNF之间的位置关系，具体是指所述VNF同其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同其它VNF的实例不能同时部署在同一个物理主机上。
在步骤203中，可以根据所述依赖关系确定针对第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型，或者根据所述位置关系确定针对第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型。也可以同时 结合所述依赖关系和位置关系一起确定针对第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型。
其中，针对第一VNF实例的所有生命周期管理操作，是指第一VNF实例能够支持的所有生命周期管理操作，例如查询、弹性缩容、弹性扩容、修复、迁移、软件更新、关闭。
需要说明的是，确定出的操作类型是不影响所述依赖关系和/或所述位置关系的操作类型。所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
在一种可能的实现方式中，步骤203包括：当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
以下将举例说明如何根据依赖关系和/或所述位置关系确定操作类型。
如图4a所示，VNF1和VNF2由VNFM2管理。VNF3和VNF4由VNFM1管理，VNF1依赖VNF2，即VNF1的正常运行依赖于VNF2的运行，比如VNF2必须存在，且资源必须在某一规定值以上，如2个CPU、2GB内存等。因此，当VNF2关闭或弹性缩容时，必将影响VNF1的运行。VNF1被VNF3所依赖，即VNF3的正常运行依赖于VNF1的正常运行。
假设本实施例中的第一VNF实例为VNF2的实例，因为VNF1依赖于VNF2，所以针对第一VNF实例的关闭或弹性缩容时，必将影响VNF1的运行。然而，VNF1和VNF2都是由VNFM2管理，所以当针对第一VNF实例的操作类型为关闭或弹性缩容时，VNFM2可以根据所述依赖关系进行操作，例如当第一VNF实例进行弹性缩容时，对VNF1也发起弹性缩容。因此，在步骤203中确定出针对第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型为查询、弹性缩容、弹性扩容、修复、软件更新、迁移、关闭。即当后续针对第一VNF实例进行这些操作时，不需要再向授权主体请求授权，而是可以直接向VIM请求资源。
在该种情况下，在步骤102之后，为该方法还包括：获取所述第一VNF实例对应的VNF的VNFD；根据VNFD确定其他VNF的正常运行是否依赖于所述VNF的正常运行；其中，其它VNF与所述VNF由同一VNFM管理；确定步骤101中的操作类型是否会影响其它VNF的正常运行，如果影响，则针对其他VNF的实例也发起与所述操作类型相关的操作。举例来说，当步骤101中的操作类型为弹性缩容时，对所述其它VNF也发起弹性缩容的操作。以使所述其它VNF与所述VNF的依赖关系维持不变，所述其它VNF不会因为管理第一VNF实例的结果导致不能正常运行。
假设本实施例中的第一VNF实例为VNF1的实例，由于VNF1被VNF3所依赖，而且VNF1和VNF3分别由不同的VNFM管理，当VNFM2对VNF1的实例，第一VNF实例进行关闭或弹性缩容操作时，VNFM1无法得知相关操作，必将影响VNF3的运行。在这种情况下，由于所有的VNFM都由NFVO管理，所以当VNFM2需要对VNF1进行关闭或弹性缩容操作时，必须先向NFVO进行授权申请。因此，此时NFVO不能将所有的生命周期管理操作都代理给VNFM2进行，所以确定出的可以授权的操作类型有：查询、弹性扩容、修复、软件更新、迁移。
如图4b所示，在本实施例中，VNF1和VNF2具有位置依赖关系，即要求 VNF1的实例和VNF2的实例部署在同一个物理主机上。VNF3和VNF1具有位置排斥关系，即要求VNF3和VNF4部署在不同的物理主机上。
因为VNF1同VNF2具有位置依赖关系，所以针对VNF1以及VNF2的实例的迁移操作，都可能导致VNF1与VNF2的位置依赖关系改变，所以迁移操作需要向授权主体请求授权。类似的，针对VNF3和VNF4的实例的迁移操作，也可能导致两者的位置排斥关系发生变化，所以迁移操作也需要向授权主体请求授权。因此，在步骤203中确定出的允许代理授权的操作类型包括：查询、弹性缩容、弹性扩容、修复、软件更新、关闭。而不包括迁移操作。
当在步骤203中确定出允许代理授权的操作类型之后，生成代理授权策略信息，并将代理授权策略信息发送给VNFM。其中，代理授权策略信息用于指示所述操作类型。
在进一步的实施例中，在获取第一VNF实例的实例化过程中，还根据所述位置关系，如位置依赖关系或位置排斥关系，向VIM发送查询请求，以请求与第一VNF实例对应的VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID。在查询请求中包括第二VNF的实例的实例ID。
VIM根据第二VNF的实例ID查询到所部署的物理主机的ID，并将该物理主机的ID返回给授权主体。
然后授权主体将物理主机的ID发送给VNFM。
可选的，发送物理主机的ID和代理授权策略信息承载在同一个消息中发送给VNFM。举例来说，该格式例如为：
GrantType:Partial delegated{Scale-up/out,Scale-in/down，Query,hell,update}//允许代理授权类型为部分授权，允许代理授权的操作类型：弹性扩容、弹性缩容、查询、修复、软件更新、关闭
Avaliable Policies://可用策略
Affinity{Host ID}//位置依赖关系：物理主体的ID
Anti-affinity{Host ID}//位置排斥关系：物理主机的ID
VNFM在接收到所述物理主机的ID之后，将所述物理主机的ID以及位置关系发送给VIM。以使VIM基于所述物理主机的ID及所述位置关系为第一VNF实例分配资源。
具体的，如果所述物理主机为位置依赖关系对应的物理主机，那么VIM就在所述物理主机上为第一VNF实例分配资源。如果所述物理主机为位置排斥关系对应的物理主机，那么VIM则选择在除了所述物理主机之外的其它物理主机上为第一VNF实例进行资源分配。
以下将举一个具体的例子来说明本发明实施例中的生命周期管理方法的实施过程，请参考图5所示，该方法包括：
步骤301：EM向VNFM发送弹性扩容的操作请求，该请求中携带第一VNF实例的实例ID；该请求的格式如下：
Scale out：//操作类型为弹性扩容
VNF：VNF2instance ID//第一VNF实例为VNF2的实例，实例ID
Resource：//弹性扩容所需资源
CPU：4//CPU4个
Memory：4GB//内存4GB
步骤302：VNFM根据所述实例ID在数据库中查找弹性扩容是否在允许代理授权的操作类型范围中，如果不在，则执行步骤303至步骤311。如果在，则执行步骤308至步骤310、以及步骤312。
步骤303：VNFM向NFVO发送弹性扩容操作授权请求；该请求的格式例如为：
Grant lifecycle operation://代表该消息是一个生命周期管理授权请求
VNF:VNF2instance ID//第一VNF实例的实例ID
Operation:scale out//请求所涉及的生命周期管理操作是一个弹性扩容操作
Required resource://弹性扩容操作所需的资源信息
CPU:4//CPU4个
Memory:4GB//内存4GB
步骤304：NFVO验证该请求的资源是否可以分配；如果可以分配的话，执行步骤305：
步骤305：NFVO向VIM申请资源预留；
步骤306：VIM向NFVO返回资源预留成功响应；
步骤307：NFVO向VNFM返回授权成功响应；
步骤308：VNFM向VIM请求弹性扩容所需的资源；
步骤309：VIM向VNFM发送资源更新成功响应消息；
步骤310：VNFM对更新的资源做配置，例如在更新的资源上运行业务脚本；
步骤311：VNFM通知NFVO资源更新成功；
步骤312：VNFM通知NFVO执行了弹性扩容操作以及第一VNF实例当前所占用的资源信息，该通知消息的格式例如为：
Notification：//代表该消息为通知消息
Operation：scale out//代表执行的生命周期管理操作为弹性扩容操作
Resource://第一VNF实例所占用的资源信息
CPU：4//CPU4个
Memory：4GB//内存4GB
其中，步骤303至步骤311为现有技术中的流程，为本领域技术人员所熟知的内容，所以将不再详细描述。
由该实施例可以看出，当在步骤301中请求的操作类型是VNFM可以代理授权的操作类型时，就直接执行步骤308至步骤310、以及步骤312，省去了步骤303至步骤307，所以大大减轻了NFVO的负担，也可以缩短对生命周期管理操作的处理时间，提高业务处理效率。
图6为本发明实施例提供的一种计算机装置的简化功能框图。该计算机装 置包括：接收单元401、处理单元402以及发送单元403。
需要说明的是，计算机装置以功能单元的形式展示。在不受限制的情况下，本文所使用的术语“单元”可指执行一个或多个软件或固件程序的专用集成电路(ASIC)、电子电路、(共享、专用或组)处理器以及存储器，组合逻辑电路，和/或提供所述功能的其它合适的部件。
可选的，该计算机装置用于实现如图2和/或图3所示的方法，具体的配置可以依据实际需要确定。
具体的，该报文转换装置用于实现本发明图2所示的生命周期管理方法时，接收单元401，用于接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；处理单元402，用于根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；发送单元403，用于向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。以使所述VIM根据所述实例ID对所述第一VNF实例进行与所述操作类型对应的资源操作。
可选的，发送单元403还用于：在所述接收单元401接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；接收单元401还用于：接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；处理单元402还用于：基于所述实例ID及所述代理授权策略信息生成所述对应关系。
可选的，发送单元403还用于：在接收单元401接收针对第一VNF实例的生命周期管理操作请求之前，向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第一 VNF实例的除实例化以外的其它生命周期管理操作进行授权。
可选的，接收单元401还用于：在所述方法单元向所述授权主体发送实例化请求之后，接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；发送单元403还用于：将所述物理主机的ID发送给所述VIM，以使所述VIM基于所述物理主机的ID及所述位置关系为所述第一VNF实例分配资源。
可选的，处理单元402还用于：在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，获取所述第一VNF实例对应的VNF的VNFD；根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一VNFM管理；针对所述其它VNF的实例发起与所述操作类型相关的操作。
具体的，该计算机装置用于实现本发明图3所示的生命周期管理方法时，接收单元401，用于接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；处理单元402，用于获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；发送单元403，用于向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
可选的，所述代理授权请求携带在用于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
可选的，发送单元403还用于：在所述接收单元401接收到所述实例化请求之后，根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请 求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的实例的实例ID；接收单元401还用于：接收所述VIM发送的所述物理主机的ID；发送单元403还用于：将所述物理主机的ID以及所述位置关系通过所述所述VNFM提供给所述VIM。具体的，将所述物理主机的ID以及所述位置关系通过所述所述VNFM提供给所述VIM包括：将所述物理主机的ID以及所述位置关系发送给所述VNFM，所述VNFM将所述物理主机的ID及所述位置关系发送给所述VIM。然后，所述VIM基于所述物理主机的ID及所述位置关系为所述第一VNF实例分配资源。
可选的，处理单元402用于：当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
前述图2，图3所示的实施例中的生命周期管理方法以及代理授权的确定方法中的各种变化方式和具体实例同样适用于本实施例的计算机装置，通过前述对生命周期方法以及代理授权的确定方法的详细描述，本领域技术人员可以清楚的知道本实施例中计算机装置的实施方法，所以为了说明书的简洁，在此不再详述。
图7显示了本发明实施例中的一种网元的结构示意图。这一网元用于在图1所示的NFV系统100中传送或处理数据。网元500用于创建(create)、修改(modify)，重定位(relocate)和/或迁移(migrate)一个或多个虚拟机。网元500还可用于容纳(host)、存储和/或执行一个或多个网络功能。网元500可以是一个如图1中NFV系统100中一个子部件，例如NFVO 102或VNFM 104。
网元500可包含一个或多个端口512，与收发器(transceiver)510相耦合。收发器510可以是发射器，接收器或其组合，从其他网络节点通过端口512发送或接收数据包。处理器502耦合到收发器510，用于处理数据包，决定哪些节点发送数据包。处理器502可包含一个或多个多核处理器和/或存储器504。处理器502可以是一个通用处理器，专用集成电路(英文：Application Specific Integrated Circuit，简称：ASIC)，或数字信号处理器(DSP)。
存储器504可为非瞬时性的存储介质，与处理器502相耦合，用于保存不同类型的数据。存储器504可包含只读存储器(英文：Read Only Memory，简称：ROM)，随机存取存储器(英文：Random Access Memory，简称：RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是磁盘存储器。存储器504可用于保存实现NFV系统或相关方法的指令，例如作为VNFM 104，VNF 108，NFVO 102。作为一种实施方式，存储器504可包含NFV模块506，该NFV模块可在处理器502上执行。NFV模块506可用于容纳(host)，存储及实现一个或多个虚拟化网络设备的网络功能。在另一实施方式中，存储器504还可包含一个NFV编排模块508，用于创建，修改，重定位和/或迁移一个或多个虚拟机。可以理解，通过编程或装载可执行指令到网元500的处理器502，缓存和长期存储中的至少一个，网元500可转换为特定的设备，例如路由器，交换机。
网元500可实现一个或多个VNF的功能，并根据本发明的实施例执行一个或多个指令。这些指令可存储在存储器504中，也可集成在网元500的操作系统的内核或内核的插件中。
可选的，网元500可以实现如图2和/或图3所示的方法，具体的配置可以依据实际需要确定。
具体的，当网元500用于实现如图2所示的生命周期管理方法时，处理器502执行前述指令时，所述指令使网元500执行以下操作：通过收发器510接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；根据VNF实 例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；并通过收发器510向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。以使所述VIM根据所述实例ID对所述第一VNF实例进行与所述操作类型对应的资源操作。
可选的，当处理器502执行所述指令时，所述指令使网元500还执行以下操作：
在通过收发器510接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，通过收发器510向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；通过收发器510接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；基于所述实例ID及所述代理授权策略信息生成所述对应关系。
可选的，当处理器502执行所述指令时，所述指令使网元500还执行以下操作：
在通过收发器510接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，通过收发器510向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
可选的，当处理器502执行所述指令时，所述指令使网元500还执行以下操作：
在通过收发器510向所述授权主体发送实例化请求之后，通过收发器接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；通过收发器510将所述物理主机的ID发送给所述VIM。以使所述VIM基于所 述物理主机的ID及所述位置关系为所述第一VNF实例分配资源。
可选的，当处理器502执行所述指令时，所述指令使网元500还执行以下操作：
在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，获取所述第一VNF实例对应的VNF的VNFD；根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一虚拟网络功能管理器VNFM管理；针对所述其它VNF的实例发起与所述操作类型相关的操作。
具体的，当网元500用于实现本发明图3所示的代理授权策略的确定方法时，处理器502执行前述指令时，所述指令使网元500执行以下操作：
通过收发器510接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；通过收发器510向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
可选的，所述代理授权请求携带在用于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
可选的，当处理器502执行所述指令时，所述指令使网元500还执行以下操作：
在通过收发器510接收到所述实例化请求之后，根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的 实例的实例ID；通过收发器510接收所述VIM发送的所述物理主机的ID；将所述物理主机的ID以及所述位置关系通过所述VNFM提供给所述VIM。具体的，将所述物理主机的ID以及所述位置关系发送给所述VNFM，以使所述VNFM将所述物理主机的ID及所述位置关系发送给所述VIM，所述VIM基于所述物理主机的ID及所述位置关系为所述第一VNF实例分配资源。
可选的，所述依赖关系为：所述VNF与所述其它VNF是否由同一VNFM管理，以及所述其它VNF的正常运行依赖于所述VNF的正常运行，或所述VNF的正常运行依赖于所述其它VNF的正常运行；
所述位置关系为所述VNF同所述其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同所述其它VNF的实例不能同时部署在同一个物理主机上。
可选的，所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
可选的，当处理器502执行所述指令时，所述指令使网元500还执行以下操作：
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
前述图2，图3所示的实施例中的生命周期管理方法以及代理授权的确定方 法中的各种变化方式和具体实例同样适用于本实施例的网元500，通过前述对生命周期方法以及代理授权的确定方法的详细描述，本领域技术人员可以清楚的知道本实施例中网元500的实施方法，所以为了说明书的简洁，在此不再详述。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (33)

  1. 一种生命周期管理方法，其特征在于，包括：
    接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；
    根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；
    向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。
  2. 如权利要求1所述的方法，其特征在于，在所述接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，所述方法还包括：
    向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；
    接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；
    基于所述实例ID及所述代理授权策略信息生成所述对应关系。
  3. 如权利要求1所述的方法，其特征在于，在所述接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，所述方法还包括：
    向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
  4. 如权利要求3所述的方法，其特征在于，所述向所述授权主体发送实例化请求之后，所述方法还包括：
    接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的 ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；
    将所述物理主机的ID发送给所述VIM。
  5. 如权利要求1-4任一项所述的方法，其特征在于，在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，所述方法还包括：
    获取所述第一VNF实例对应的VNF的VNFD；
    根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一虚拟网络功能管理器VNFM管理；
    针对所述其它VNF的实例发起与所述操作类型相关的操作。
  6. 一种代理授权策略的确定方法，其特征在于，包括：
    接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；
    获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；
    根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；
    向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
  7. 如权利要求6所示的方法，其特征在于，所述代理授权请求携带在用于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
  8. 如权利要求7所述的方法，其特征在于，在接收到所述实例化请求之后，所述方法还包括：
    根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的实例的实例ID；
    接收所述VIM发送的所述物理主机的ID；
    将所述物理主机的ID以及所述位置关系通过所述VNFM提供给所述VIM。
  9. 如权利要求6-8任一项所述的方法，其特征在于，所述依赖关系为：所述VNF与所述其它VNF是否由同一VNFM管理，以及所述其它VNF的正常运行依赖于所述VNF的正常运行，或所述VNF的正常运行依赖于所述其它VNF的正常运行；
    所述位置关系为所述VNF同所述其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同所述其它VNF的实例不能同时部署在同一个物理主机上。
  10. 如权利要求9所述的方法，其特征在于，所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
  11. 如权利要求9或10所述的方法，其特征在于，所述根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型，包括：
    当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
    当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
    当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
  12. 一种计算机装置，其特征在于，包括：
    接收单元，用于接收针对第一虚拟化网络功能VNF实例的生命周期管理操 作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；
    处理单元，用于根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；
    发送单元，用于向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。
  13. 如权利要求12所述的计算机装置，其特征在于，所述发送单元还用于：在所述接收单元接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；
    所述接收单元还用于：接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；
    所述处理单元还用于：基于所述实例ID及所述代理授权策略信息生成所述对应关系。
  14. 如权利要求12所述的计算机装置，其特征在于，所述发送单元还用于：在所述接收单元接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
  15. 如权利要求14所述的计算机装置，其特征在于，所述接收单元还用于：在所述方法单元向所述授权主体发送实例化请求之后，接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；
    所述发送单元还用于：将所述物理主机的ID发送给所述VIM。
  16. 如权利要求12-15任一项所述的计算机装置，其特征在于，所述处理单元还用于：在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，获取所述第一VNF实例对应的VNF的VNFD；根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一虚拟网络功能管理器VNFM管理；针对所述其它VNF的实例发起与所述操作类型相关的操作。
  17. 一种计算机装置，其特征在于，包括：
    接收单元，用于接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；
    处理单元，用于获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；
    发送单元，用于向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
  18. 如权利要求17所述的计算机装置，其特征在于，所述代理授权请求携带在用于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
  19. 如权利要求18所述的计算机装置，其特征在于，所述发送单元还用于：在所述接收单元接收到所述实例化请求之后，根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的实例的实例ID；
    所述接收单元还用于：接收所述VIM发送的所述物理主机的ID；
    所述发送单元还用于：将所述物理主机的ID以及所述位置关系通过所述所述VNFM提供给所述VIM。
  20. 如权利要求17-19任一项所述的计算机装置，其特征在于，所述依赖关系为：所述VNF与所述其它VNF是否由同一VNFM管理，以及所述其它VNF的正常运行依赖于所述VNF的正常运行，或所述VNF的正常运行依赖于所述其它VNF的正常运行；
    所述位置关系为所述VNF同所述其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同所述其它VNF的实例不能同时部署在同一个物理主机上。
  21. 如权利要求20所述的计算机装置，其特征在于，所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
  22. 如权利要求20或21所述的计算机装置，其特征在于，所述处理单元用于：当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
    当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
    当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
  23. 一种用于生命周期管理的网元，其特征在于，包括：
    存储器，用于存储计算机可执行程序代码；
    收发器，以及
    处理器，与所述存储器和所述收发器耦合；
    其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：
    通过所述收发器接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求，所述生命周期管理操作请求包括所述第一VNF实例的实例标识ID以及操作类型；根据VNF实例的实例ID与生命周期管理操作的类型的对应关系，确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中；其中，所述对应关系中的生命周期管理操作的类型表示所述生命周期管理操作的类型已被授权主体授权；并通过所述收发器向虚拟基础设施管理器VIM发起资源操作请求，所述资源操作请求包括所实例ID。
  24. 如权利要求23所述的网元，其特征在于，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
    在通过所述收发器接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，通过所述收发器向所述授权主体发送代理授权请求；所述代理授权请求用于请求所述授权主体对所述第一VNF实例的所有生命周期管理操作进行授权；通过所述收发器接收所述授权主体发送的代理授权策略信息，所述代理授权策略信息用于指示授权的生命周期管理操作的类型；基于所述实例ID及所述代理授权策略信息生成所述对应关系。
  25. 如权利要求23所述的网元，其特征在于，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
    在通过所述收发器接收针对第一虚拟化网络功能VNF实例的生命周期管理操作请求之前，通过所述收发器向所述授权主体发送实例化请求；所述实例化请求还包括代理授权请求，所述代理授权请求用于请求所述授权主体对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
  26. 如权利要求25所述的网元，其特征在于，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
    在通过所述收发器向所述授权主体发送实例化请求之后，通过收发器接收所述授权主体发送的位置关系以及所述位置关系对应的物理主机的ID；所述位置关系为所述第一VNF实例对应的VNF与其它VNF的实例之间的位置关系；通过所述收发器将所述物理主机的ID发送给所述VIM。
  27. 如权利要求23-26任一项所述的网元，其特征在于，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
    在所述确定所述操作类型在所述实例ID对应的生命周期管理操作的类型中之后，获取所述第一VNF实例对应的VNF的VNFD；根据所述VNFD确定其它VNF的正常运行依赖于所述VNF的正常运行；其中，所述其它VNF与所述VNF由同一虚拟网络功能管理器VNFM管理；针对所述其它VNF的实例发起与所述操作类型相关的操作。
  28. 一种用于确定代理授权策略的网元，其特征在于，包括：
    存储器，用于存储计算机可执行程序代码；
    收发器，以及
    处理器，与所述存储器和所述收发器耦合；
    其中所述程序代码包括指令，当所述处理器执行所述指令时，所述指令使所述网元执行以下操作：
    通过所述收发器接收虚拟网络功能管理器VNFM发送的代理授权请求；所述代理授权请求用于请求对第一虚拟网络功能VNF实例的生命周期管理操作进行授权；获取所述第一VNF实例对应的VNF的VNF描述信息VNFD；根据所述VNFD中描述的所述VNF同其它VNF之间的依赖关系和/或位置关系，确定针对所述第一VNF实例的所有生命周期管理操作中能够代理授权的操作类型；所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型；通过所述收发器向所述VNFM发送代理授权策略信息；所述策略信息用于指示所述操作类型。
  29. 如权利要求28所述的网元，其特征在于，所述代理授权请求携带在用 于获得所述第一VNF实例的实例化请求中，所述代理授权请求用于请求对所述第一VNF实例的除实例化以外的其它生命周期管理操作进行授权。
  30. 如权利要求29所述的网元，其特征在于，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
    在通过所述收发器接收到所述实例化请求之后，根据所述位置关系，向虚拟基础设施管理器VIM发送查询请求，以请求与所述VNF之间有位置关系的第二VNF的实例所部署的物理主机的ID；其中，所述查询请求包括所述第二VNF的实例的实例ID；通过所述收发器接收所述VIM发送的所述物理主机的ID；将所述物理主机的ID以及所述位置关系通过所述VNFM提供给所述VIM。
  31. 如权利要求28-30任一项所述的网元，其特征在于，所述依赖关系为：所述VNF与所述其它VNF是否由同一VNFM管理，以及所述其它VNF的正常运行依赖于所述VNF的正常运行，或所述VNF的正常运行依赖于所述其它VNF的正常运行；
    所述位置关系为所述VNF同所述其它VNF的实例必须部署在同一个物理主机上，或者所述VNF同所述其它VNF的实例不能同时部署在同一个物理主机上。
  32. 如权利要求31所述的网元，其特征在于，所述操作类型为不影响所述依赖关系和/或所述位置关系的操作类型，为：对所述第一VNF实例执行所述操作类型对应的操作之后，依赖于所述所述VNF的所述其它VNF依然能够正常运行，和/或对所述第一VNF实例执行所述操作类型对应的操作之后，所述VNF与所述其它VNF的实例之间的位置关系不相斥。
  33. 如权利要求31或32所述的网元，其特征在于，当所述处理器执行所述指令时，所述指令使所述网元还执行以下操作：
    当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF由不同的VNFM管理时，确定所述能够代理授权的操作类型为除关闭、弹性缩容之外的其它生命周期管理操作的类型；或
    当所述其它VNF的正常运行依赖于所述VNF，且所述其它VNF与所述VNF 均由所述VNFM管理时；确定所述能够代理授权的操作类型为所有生命周期管理操作的类型；或
    当所述VNF和所述其它VNF之间具有所述位置关系时，确定所述能够代理授权的操作类型为除迁移之外的其它生命周期管理操作的类型。
PCT/CN2016/080138 2015-07-20 2016-04-25 一种生命周期管理方法及装置 WO2017012381A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16827072.6A EP3313023B1 (en) 2015-07-20 2016-04-25 Life cycle management method and apparatus
US15/872,507 US10701139B2 (en) 2015-07-20 2018-01-16 Life cycle management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510429123.1A CN106375101B (zh) 2015-07-20 2015-07-20 一种生命周期管理方法及装置
CN201510429123.1 2015-07-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/872,507 Continuation US10701139B2 (en) 2015-07-20 2018-01-16 Life cycle management method and apparatus

Publications (1)

Publication Number Publication Date
WO2017012381A1 true WO2017012381A1 (zh) 2017-01-26

Family

ID=57833772

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/080138 WO2017012381A1 (zh) 2015-07-20 2016-04-25 一种生命周期管理方法及装置

Country Status (4)

Country Link
US (1) US10701139B2 (zh)
EP (1) EP3313023B1 (zh)
CN (2) CN106375101B (zh)
WO (1) WO2017012381A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200004572A1 (en) * 2018-06-28 2020-01-02 Cable Television Laboratories, Inc Systems and methods for secure network management of virtual network functions
US11563677B1 (en) * 2018-06-28 2023-01-24 Cable Television Laboratories, Inc. Systems and methods for secure network management of virtual network function

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107135192B (zh) * 2016-02-26 2020-04-21 中国移动通信集团公司 部署vnf的资源授权方法、vnfm和nfvo
CN109219949B (zh) * 2016-05-27 2021-10-12 瑞典爱立信有限公司 在网络功能虚拟化基础结构中配置安全域的方法和设备
US10476839B2 (en) * 2016-08-15 2019-11-12 Cisco Technology, Inc. Datapath triggered on-demand NFV service activation
US10997197B2 (en) * 2016-09-27 2021-05-04 International Business Machines Corporation Dependencies between site components across geographic locations
KR102272229B1 (ko) * 2016-11-17 2021-07-05 후아웨이 테크놀러지 컴퍼니 리미티드 네트워크 서비스 라이프 사이클 관리 승인 방법 및 장치
CN108628660B (zh) * 2017-03-24 2021-05-18 华为技术有限公司 一种虚拟机扩缩容方法及虚拟管理设备
CN109428764B (zh) * 2017-09-05 2021-10-15 华为技术有限公司 虚拟网络功能的实例化方法
US10680898B2 (en) * 2018-03-06 2020-06-09 At&T Intellectual Property I, L.P. Mini-cloud deployment system
CN110275756B (zh) * 2018-03-13 2023-04-18 华为技术有限公司 虚拟化网元的部署方法以及装置
US11382150B2 (en) * 2018-03-26 2022-07-05 Apple Inc. System and method of managing PNF connectivity in a network slice instance
GB2573283B (en) 2018-04-26 2020-04-29 Metaswitch Networks Ltd Improvements relating to network functions virtualization
CN114880078A (zh) 2018-06-05 2022-08-09 华为技术有限公司 管理容器服务的方法和装置
CN109828830B (zh) * 2019-01-18 2021-07-16 北京百度网讯科技有限公司 用于管理容器的方法和装置
CN111641515B (zh) * 2019-03-01 2021-11-19 华为技术有限公司 Vnf的生命周期管理方法及装置
CN111726241B (zh) * 2019-03-22 2023-05-19 中兴通讯股份有限公司 网络资源管理方法、系统、网络设备和可读存储介质
US11451549B2 (en) * 2019-11-20 2022-09-20 Verizon Patent And Licensing Inc. Authorization for network function registration
CN111090495A (zh) * 2019-12-02 2020-05-01 中兴通讯股份有限公司 节点管理方法、装置、设备、存储介质和系统
CN113726541B (zh) * 2020-05-25 2023-11-07 中移(苏州)软件技术有限公司 一种网元配置的方法、装置、电子设备和存储介质
JP7409504B2 (ja) * 2020-07-03 2024-01-09 日本電信電話株式会社 ネットワーク仮想化システム、仮想リソース管理装置、仮想リソース管理方法およびプログラム
CN114598604B (zh) * 2020-12-01 2023-09-19 中移(苏州)软件技术有限公司 虚拟网络功能实例信息的监控方法、监控装置及终端

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
WO2015042937A1 (zh) * 2013-09-30 2015-04-02 华为技术有限公司 故障管理的方法、实体和系统

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5379423A (en) * 1988-09-28 1995-01-03 Hitachi, Ltd. Information life cycle processor and information organizing method using it
US7082102B1 (en) * 2000-10-19 2006-07-25 Bellsouth Intellectual Property Corp. Systems and methods for policy-enabled communications networks
US8204931B2 (en) * 2004-12-28 2012-06-19 Sap Ag Session management within a multi-tiered enterprise network
US8627490B2 (en) * 2005-12-29 2014-01-07 Nextlabs, Inc. Enforcing document control in an information management system
US8365298B2 (en) * 2006-09-29 2013-01-29 Sap Ag Comprehensive security architecture for dynamic, web service based virtual organizations
US20080115192A1 (en) * 2006-11-07 2008-05-15 Rajandra Laxman Kulkarni Customizable authentication for service provisioning
US8490150B2 (en) * 2009-09-23 2013-07-16 Ca, Inc. System, method, and software for enforcing access control policy rules on utility computing virtualization in cloud computing systems
CN101976314B (zh) 2010-09-21 2012-08-01 用友软件股份有限公司 权限控制方法和系统
WO2012045021A2 (en) * 2010-09-30 2012-04-05 Commvault Systems, Inc. Efficient data management improvements, such as docking limited-feature data management modules to a full-featured data management system
US10404551B2 (en) * 2012-04-30 2019-09-03 Entit Software Llc Automated event management
US9389898B2 (en) * 2012-10-02 2016-07-12 Ca, Inc. System and method for enforcement of security controls on virtual machines throughout life cycle state changes
US9378035B2 (en) * 2012-12-28 2016-06-28 Commvault Systems, Inc. Systems and methods for repurposing virtual machines
US9973375B2 (en) * 2013-04-22 2018-05-15 Cisco Technology, Inc. App store portal providing point-and-click deployment of third-party virtualized network functions
US10020996B1 (en) * 2013-06-27 2018-07-10 EMC IP Holding Company LLC Real-time policy management of data management life cycle
WO2015013548A1 (en) * 2013-07-24 2015-01-29 Visa International Service Association Systems and methods for interoperable network token processing
EP3063668A4 (en) * 2013-10-30 2017-05-31 Hewlett-Packard Enterprise Development LP Managing the lifecycle of a cloud service modeled as topology decorated by a number of policies
KR20150053513A (ko) * 2013-11-08 2015-05-18 한국전자통신연구원 클라우드 서비스 브로커 장치 및 이를 이용한 클라우드 서비스 제공 방법
US10481935B2 (en) * 2013-12-27 2019-11-19 Ntt Docomo, Inc. Management system, overall management node, and management method for managing virtualization resources in a mobile communication network
EP3125122B1 (en) * 2014-03-28 2017-10-11 Ntt Docomo, Inc. Virtualized resource management node and virtual machine migration method
US9942043B2 (en) * 2014-04-23 2018-04-10 Visa International Service Association Token security on a communication device
EP3133794B1 (en) * 2014-05-15 2019-04-03 Huawei Technologies Co., Ltd. Network function virtualization network system
US9497222B2 (en) * 2014-05-20 2016-11-15 International Business Machines Corporation Identification of web form parameters for an authorization engine
CN105323085A (zh) * 2014-07-10 2016-02-10 中兴通讯股份有限公司 创建性能测量任务、性能测量结果的处理方法及装置
CN104219127B (zh) * 2014-08-30 2018-06-26 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
US20160063417A1 (en) * 2014-09-03 2016-03-03 International Business Machines Corporation Life cycle management for an asset
US9853938B2 (en) * 2014-09-08 2017-12-26 Quanta Computer Inc. Automatic generation of server network topology
CN105528234A (zh) * 2014-10-24 2016-04-27 中兴通讯股份有限公司 虚拟机迁移处理方法及装置
CN105591784A (zh) * 2014-10-24 2016-05-18 中兴通讯股份有限公司 告警处理方法及装置
US9804789B2 (en) * 2015-06-24 2017-10-31 Vmware, Inc. Methods and apparatus to apply a modularized virtualization topology using virtual hard disks
CN106603371B (zh) * 2015-10-14 2020-11-24 中兴通讯股份有限公司 一种网络功能虚拟化系统及网络服务实例化方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015042937A1 (zh) * 2013-09-30 2015-04-02 华为技术有限公司 故障管理的方法、实体和系统
CN104170323A (zh) * 2014-04-09 2014-11-26 华为技术有限公司 基于网络功能虚拟化的故障处理方法及装置、系统
CN104115447A (zh) * 2014-04-14 2014-10-22 华为技术有限公司 一种云计算架构下的容灾方案配置方法及装置

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200004572A1 (en) * 2018-06-28 2020-01-02 Cable Television Laboratories, Inc Systems and methods for secure network management of virtual network functions
US11563677B1 (en) * 2018-06-28 2023-01-24 Cable Television Laboratories, Inc. Systems and methods for secure network management of virtual network function
US11822946B2 (en) * 2018-06-28 2023-11-21 Cable Television Laboratories, Inc. Systems and methods for secure network management of virtual network functions
US11855890B2 (en) 2018-06-28 2023-12-26 Cable Television Laboratories, Inc. Systems and methods for secure network management of virtual network function

Also Published As

Publication number Publication date
CN106375101A (zh) 2017-02-01
US10701139B2 (en) 2020-06-30
CN110661647A (zh) 2020-01-07
CN106375101B (zh) 2019-08-27
EP3313023A1 (en) 2018-04-25
EP3313023B1 (en) 2020-09-23
EP3313023A4 (en) 2018-05-30
US20180146031A1 (en) 2018-05-24

Similar Documents

Publication Publication Date Title
WO2017012381A1 (zh) 一种生命周期管理方法及装置
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US10719348B2 (en) Network function virtualization management and orchestration apparatus, method, and program
US11947697B2 (en) Method and system to place resources in a known state to be used in a composed information handling system
US9413604B2 (en) Instance host configuration
WO2019233273A1 (zh) 管理容器服务的方法和装置
WO2016184045A1 (zh) 一种网络业务扩容的方法和装置
WO2018006676A1 (zh) 加速资源处理方法、装置及网络功能虚拟化系统
WO2018090299A1 (zh) 网络服务生命周期管理的许可方法和装置
US8966025B2 (en) Instance configuration on remote platforms
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
US10728169B1 (en) Instance upgrade migration
JP6003590B2 (ja) データセンタ，仮想システムの複写サービスの提供方法，データセンタの管理サーバ及び仮想システムの複写プログラム
WO2019129118A1 (zh) Vnf服务实例化方法及装置
US20200133708A1 (en) Method for Managing VNF Instantiation and Device
WO2020140945A1 (zh) 基于容器的虚拟资源管理方法、装置及系统
WO2015117278A1 (zh) 时钟中断信号的获取方法和nfv功能实体
WO2022140945A1 (zh) 容器集群的管理方法和装置
CN113918268A (zh) 一种多租户管理方法及装置
US11604595B2 (en) Data mirroring and data migration between storage volumes using system control processors
CN112015515A (zh) 一种虚拟网络功能的实例化方法及装置
WO2020077585A1 (zh) Vnf服务实例化方法及装置
WO2023274014A1 (zh) 容器集群的存储资源管理方法、装置及系统
US11704159B2 (en) System and method for unified infrastructure architecture
WO2022141293A1 (zh) 一种弹性伸缩的方法及装置

Legal Events

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

Ref document number: 16827072

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE