WO2018113571A1 - 一种虚拟化网元的管理方法和装置及计算机存储介质 - Google Patents

一种虚拟化网元的管理方法和装置及计算机存储介质 Download PDF

Info

Publication number
WO2018113571A1
WO2018113571A1 PCT/CN2017/116002 CN2017116002W WO2018113571A1 WO 2018113571 A1 WO2018113571 A1 WO 2018113571A1 CN 2017116002 W CN2017116002 W CN 2017116002W WO 2018113571 A1 WO2018113571 A1 WO 2018113571A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
virtualized network
vnfm
adaptation component
component
Prior art date
Application number
PCT/CN2017/116002
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 中兴通讯股份有限公司
Publication of WO2018113571A1 publication Critical patent/WO2018113571A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present invention relates to network technologies, and in particular, to a method and device for managing a virtualized network element and a computer storage medium.
  • the technical solution adopted by the current operation and maintenance unit is to develop a special adaptation component for different network element types or the same type of network element that has a communication protocol or operation and maintenance interaction information difference, and it should be noted that the adaptation is The function of the component is to adapt different communication protocols and parse different operation and maintenance interaction information, and adapt it to the format required by the operation and maintenance unit. That is to say, after the processing of the adaptation component, all the operation and maintenance interaction information will remove the difference caused by different communication protocols or information structures, and enter a consistent operation and maintenance processing mode.
  • the embodiment of the present invention is to provide a method and an apparatus for managing a virtualized network element; reducing the running of useless components increases the consumption and waste of resources.
  • an embodiment of the present invention provides a method for managing a virtualized network element, where the method includes:
  • the lifecycle change information and the resource change information of the adaptation component are obtained from the VNFM.
  • the embodiment of the present invention provides a management device for a virtualized network element, where the device includes: a receiving unit, an obtaining unit, and a sending unit;
  • the receiving unit is configured to receive lifecycle change information for the virtualized network element sent by the virtualized network function manager VNFM;
  • the obtaining unit is configured to determine and determine an adaptation component corresponding to the virtualized network element
  • the sending unit is configured to send an operation request for the adaptation component to the VNFM according to the lifecycle change information of the virtualized network element;
  • the receiving unit is configured to acquire lifecycle change information and resource change information of the adaptation component from the VNFM.
  • an embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions. After the computer executable instructions are executed, the virtualized network element provided by the foregoing technical solution can be implemented. method.
  • Embodiments of the present invention provide a method and a device for managing a virtualized network element, and a computer storage medium.
  • the network function virtualization orchestrator (NFVO, NFV Orchestration) and the change according to the life cycle state of the virtualized network element are The lifecycle state of the adaptation component of the virtualized network element is changed.
  • the network element management entity or system is not used to actively detect the adaptation component that needs to be stopped, and then terminate the operation after detecting the adaptation component that needs to be stopped, which simplifies the termination of the operation of the adaptation component that is no longer needed. , not only can terminate the termination operation of the adapter component that is no longer needed in time, and can reduce the network element management. Or a system load.
  • FIG. 1A is a schematic diagram of a Network Function Virtualization (NFV) architecture according to an embodiment of the present invention
  • FIG. 1B is a schematic diagram of another NFV architecture according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for managing a virtualized network element according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a specific embodiment 1 according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a second embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a third embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a fourth embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a device for managing a virtualized network element according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of another device for managing a virtualized network element according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a management device for a virtualized network element according to an embodiment of the present invention.
  • FIG. 1A is a schematic diagram of an NFV system architecture.
  • the NFV system 10 may include: NFV Management and Orchestration (NFV MANO) 101, NFV Infrastructure (NFVI Infrastructure) 102. , multiple virtual network functions (VNF) 103, multiple network element management (EM, Element Manager) 104, network services, VNF and infrastructure description (Network Service, VNF and Infrastructure Description) 105, and service support Management device (OSS/BSS, Operation-Support System/Business Support System) 106.
  • NFV MANO NFV Management and Orchestration
  • VNF virtual network functions
  • EM multiple network element management
  • EM network element management
  • Network Services VNF and infrastructure description
  • OSS/BSS Operation-Support System/Business Support System
  • the NFV-MANO 101 may include: NFV orchestrator (NFVO, NFV Orchestrator) 1011, one or more VNF Manager (VNFM, VNF Manager) 1012, and a Virtualized Infrastructure Manager (VIM) 1013; NFV MANO101 is mainly used to monitor and manage VNF103 and NFVI102; NFVO1011 in NFV MANO101 is mainly used to receive resource related requests from one or more VNFM1012, and send configuration information to VNFM1012 to collect status information of VNF103.
  • NFV orchestrator NFVO, NFV Orchestrator
  • VNFM VNF Manager
  • VIP Virtualized Infrastructure Manager
  • NFVO1011 It is also used to communicate with VIM1013 to implement resource allocation and/or reservation and exchange configuration and status information of virtualized hardware resources;
  • VNFM1012 is mainly used to manage one or more VNF103, such as: instantiate, update, query, zoom And/or terminate VNF 103, etc.;
  • VIM 1013 mainly performs resource management functions, such as managing allocation of infrastructure resources (such as adding resources to virtual containers) and operational functions (such as collecting NFVI failure information).
  • the NFVI 102 can include computing hardware 1021, storage hardware 1022, network hardware 1023, virtualization layer, virtual computing 1024, virtual storage 1025, and virtual network 1026.
  • the virtualization layer in NFVI102 can abstract hardware resources from the physical layer and decouple VNF103 to provide virtualized resources to VNF103, virtual computing 1024 and virtual storage 1025.
  • the VNF 103 can be provided in the form of a virtual machine, and/or other virtual container.
  • one or more VNFs 103 can be deployed on a virtual machine (VM).
  • the virtualization layer abstracts network hardware 1023 to form a virtual network 1026, which may include a virtual switch that can be used to provide connection communication between VMs on the VNF 103 and other VMs.
  • the NFV architecture may include: a network function virtualization orchestrator (NFVO, NFV Orchestration), a VNF manager (VNFM, VNF Manager), a blueprint catalog catalog, a software warehouse (SWR, SoftWare Repository, EM (Element Manager), and Virtual Infrastructure Manager (VIM); where VNFM is responsible for lifecycle management of VNF instances, such as instantiating network elements, terminating network elements, and upgrading Network elements, etc.; Catalog is to save various blueprints and supporting files contained in the software package and provide downloads; SWR is to save the software image files contained in the software package and provide downloads, such as saving and placing VNF Package, in addition to the Package.
  • VNF Network Function Virtualization Infrastructure
  • network elements described in the embodiments of the present invention are virtualized network elements, which are implemented and implemented by virtualizing network functions.
  • the software package of the operation and maintenance unit is usually packaged with all the adaptation components of all supported network element types. Therefore, when the version is running, the operation and maintenance unit starts all the adaptation components of the supported network element type, which makes some unnecessary adaptation components occupy the resources of the system, thereby causing a problem of large overhead of system resources.
  • the network element types of mobile communication networks will be more diverse. And the speed of network type evolution and elimination will be greatly accelerated.
  • the method may be applied to NFVO in an NFV architecture, and the method may include:
  • S201 Receive lifecycle change information sent by the VNFM for the virtualized network element.
  • S202 Determine and determine an adaptation component corresponding to the virtualized network element.
  • S203 Send an operation request for the adaptation component to the VNFM according to the lifecycle change information of the virtualized network element.
  • the virtualized network element may be, for example, a VNF network element, and details are not described herein.
  • the lifecycle change corresponding to the virtualized network element and the operation of the adaptation component corresponding to the virtualized network element are operations for respective lifecycles; optionally, the lifecycle change corresponding to the virtualized network element may include : virtualized network element instantiation, virtualized network element termination, virtualized network element upgrade, etc.; and corresponding to virtualized network element instantiation, corresponding operations of the adaptation component may include instantiation of the adaptation component; corresponding to virtual The network element is terminated, and the corresponding operation of the adaptation component may include termination of the instance of the adaptation component; corresponding to the virtualized network element upgrade, the corresponding operations of the adaptation component include: instantiation of the upgraded component after the upgrade and the pre-upgrade adaptation component Termination of.
  • the meaning of the term "instantiated” means that in a virtualized infrastructure, a virtualized network element passes certain communication network elements or functions. Set up, turn on, activate, create, or perform your own virtualized network functions in some way.
  • the instantiation may include: virtualizing network elements instantiated according to needs
  • the description information is used to allocate the resources required for the virtualized network element, create an instance of the virtualized network element, and assign an instance identifier to the instance.
  • the instance of the virtualized network element can be used for communication.
  • the life cycle of the adaptation component corresponds to the life cycle of the virtualized network element. Therefore, it is not necessary to start all the adaptation components of the network element type that the EM can support when the version is running, thereby reducing uselessness.
  • the resource consumption and waste caused by the operation of the adaptation component; and the EM can automatically adapt to the life cycle changes of the VNF and the adaptation component without stopping the operation when the life cycle of the VNF and the adaptation component is changed.
  • the life cycle of the adaptation component corresponds to its corresponding life cycle (ie, the life cycle of the virtualized network element that needs to be adapted, such that if the operation of a virtualized network element is terminated, the virtual The exclusive adaptation component used by the network element will also be terminated. If a virtualized network element is upgraded and the old adaptation component is no longer needed, the life cycle of the lower version of the virtualized network element is terminated. The adaptation component used by the version of the virtualized network element is also terminated accordingly. Therefore, the operation request includes at least: a termination request indicating that the adaptation component ends running when the operation of its corresponding virtualized network element terminates.
  • the lifecycle change information of the virtualized network element includes: attribute information of the virtualized network element to be instantiated.
  • the determining and determining the adaptation component corresponding to the virtualized network element may include: determining, according to the attribute information of the virtualized network element to be instantiated, and determining the corresponding virtualized network element to be instantiated An adaptation component to be instantiated.
  • the attribute information of the virtualized network element to be instantiated may include one or more of information such as a virtualized network element name, a virtualized network element type, and a virtualized network element version.
  • the NFVO can obtain the adaptation component to be instantiated by searching the mapping table between the adaptation component and the virtualized network element attribute information such as the network element type and the network element version.
  • the adaptation component can have a mapping relationship with more than one type of virtualized network element attribute information.
  • step S203 the sending, by the lifecycle change information of the virtualized network element, the operation request for the adaptation component to the VNFM may include:
  • the adaptation component instantiation request comprises: an adaptation component type and an adaptation blueprint identifier to be instantiated;
  • the blueprint identifier is used by the VNFM to obtain an adaptation component blueprint to be instantiated according to the adaptation blueprint identifier, and calculate the resources required for the adaptation component to be instantiated according to the adaptation component blueprint to be instantiated.
  • the obtaining the lifecycle change information and the resource change information of the adaptation component from the VNFM may include:
  • resource authorization information to the VNFM according to the resource request request, where the resource authorization information is used to instruct the VNFM to request, by the VNFM, the resources required for the adaptation component to be instantiated to run;
  • the NFVO may apply to the NFVO for resources required for the component to operate, such as network resources, memory resources, CPU resources, and the like; And after receiving the resource authorization information returned by the NFVO, the VNFM may request the VIM to allocate resources; when the VIM viewing required resources are available, The resource will be allocated and the resource allocation completion notification will be returned to the VFNM; the VNFM will notify the NFVO that the required resources will be used by the adaptation component, and the VNFM instantiates the adaptation of the virtualized network element required by the instantiated maintenance unit EM. After the component, the NFVO is notified that the instantiated component is instantiated.
  • the operation and maintenance unit EM can support the management of the new type of network element without upgrading or suspending the operation.
  • the operation of the adaptation component can automatically adapt to changes in the network elements managed by the EM.
  • the lifecycle change information of the virtualized network element includes: attribute information of the terminated virtualized network element.
  • the method may include:
  • the attribute information of the terminated virtualized network element may include: a name of the terminated virtualized network element, a network element type, a network element version, a network element instance number, and the like.
  • the NFVO can obtain the adaptation component to be terminated by looking up a mapping table between the adaptation component and the attribute information of the virtualized network element.
  • step S203 it may include:
  • the terminated network element of the same virtualized network element type is not in the running state, sending an adaptation component termination request to the VNFM; wherein the adaptation component termination request includes the adaptation component to be terminated Instance number.
  • step S204 the obtaining a lifecycle change of the adaptation component from the VNFM Information and resource change information, which can include:
  • the VNFM after receiving the adaptation component termination request, the VNFM returns an operation task number to the NFVO, so that the NFVO can initiate a query for the task operation state; and after the VNFM terminates the adaptation component to be terminated, the NFVO targets The termination operation of the adapter component to be terminated has been completed; the VNFM notifies the VIM to release the resources occupied by the adapter component to be terminated, and after the VIM notifies the release of the VNFM resource, the VNFM notifies the NFVO that the termination needs to be terminated. The resources occupied by the component have been released, and the resource usage status is updated.
  • the virtualized network element of a certain network element type terminates in the operation of the system, the corresponding adaptation component is terminated, so that the operation and maintenance unit EM does not need to upgrade or suspend the operation. You can terminate the adaptation component that is not running and release resources.
  • the lifecycle change information of the virtualized network element includes: attribute information of the upgraded virtualized network element and attribute information of the virtualized network element before the upgrade. It should be noted that, due to the upgrade of the virtualized network element, the operation of the adaptation component of the virtualized network element may be performed to start the adaptation component that needs to be instantiated corresponding to the virtualized network element after the upgrade. And terminating the adaptation component corresponding to the virtualized network element before the upgrade.
  • the determining and determining the adaptation component corresponding to the virtualized network element may include:
  • the attribute information of the upgraded virtualized network element may include: a network element name, a network element type, an upgraded network element version, and an NE instance identifier.
  • the NFVO can obtain the adaptation component to be instantiated by searching the mapping table between the adaptation component and the virtualized network element attribute information such as the network element type and the upgraded network element version.
  • the sending the operation request for the adaptation component to the VNFM according to the lifecycle change information of the virtualized network element may include:
  • the adapter component instantiation request corresponding to the upgraded virtualized network element that needs to be instantiated includes: an adapted component type and an adaptation blueprint identifier to be instantiated corresponding to the upgraded virtualized network element; and an adaptation blueprint identifier is used for
  • the VNFM obtains the blueprint of the adaptation component that needs to be instantiated corresponding to the upgraded virtualized network element according to the adaptation blueprint identifier, and calculates the upgrade according to the blueprint of the adaptation component that needs to be instantiated corresponding to the upgraded virtualized network element.
  • the virtualized network element corresponds to the resources required for the instantiated component to be instantiated.
  • the acquiring the lifecycle change information and the resource change information of the adaptation component from the VNFM may include:
  • the resource authorization information is sent to the VNFM according to the resource application request, where the resource authorization information is used to indicate that the VNFM requests the VIM to allocate the resources required for the optimized component to be instantiated corresponding to the upgraded virtualized network element. ;
  • the adaptation component to be instantiated corresponding to the upgraded virtualized network element sent by the VNFM is corresponding to the instantiation completion notification.
  • the NFVO may apply to the NFVO for resources required for the component to run, such as network resources.
  • resources required for the component to run such as network resources.
  • the VNFM will notify the NFVO that the required resources will be used by the adaptation component, and the VNFM instantiates the adaptation component of the virtualized network element required by the instantiated operation maintenance unit EM to notify the NFVO that the adaptation needs to be instantiated. Component instantiation is complete.
  • the determining and determining the adaptation component corresponding to the virtualized network element may include:
  • the attribute information of the virtualized network element before the upgrade may include: a virtualized network element name, an NE type, an NE version before the upgrade, and an NE instance number.
  • the NFVO can obtain the adaptation component corresponding to the virtualized network element before the upgrade by searching the mapping table between the adaptation component and the attribute information of the virtualized network element before the upgrade.
  • the sending the operation request for the adaptation component to the VNFM according to the lifecycle change information of the virtualized network element may include:
  • the acquiring the lifecycle change information and the resource change information of the adaptation component from the VNFM may include:
  • the VNFM after receiving the adaptation component termination request, the VNFM returns an operation task number to the NFVO, so that the NFVO can initiate a query for the task operation state; and the VNFM terminates the corresponding virtualized network element corresponding to the upgrade.
  • the termination operation of the NFVO for the adaptation component corresponding to the pre-upgrade virtualized network element is completed; the VNFM notifies the VIM to release the resources occupied by the adaptation component corresponding to the pre-upgrade virtualized network element, and After the VIM is notified that the VNFM resource is released, the VNFM notifies the NFVO that the resources occupied by the adaptation component corresponding to the pre-upgrade virtualized network element have been released, and the resource usage status is updated.
  • the corresponding component to be instantiated corresponding to the upgraded virtualized network element corresponding to the network element after the upgrade is started and the corresponding virtualized network element corresponding to the pre-upgrade network element corresponding to the pre-upgrade network element.
  • the optimized component corresponding to the upgraded virtualized network element corresponding to the upgraded network element needs to be instantiated.
  • the adaptation component corresponding to the pre-upgrade virtualized network element corresponding to the pre-upgrade network element is terminated.
  • the specific implementation process may refer to the solution for running the adaptation component corresponding to the VNF after the instantiation is completed, and The termination component of the VNF corresponding to the termination is not described in this embodiment.
  • the method further includes:
  • the NFVO receives the update request, where the update request includes an operation maintenance package identifier to be updated, a file path of the operation maintenance package to be updated, and an update information description;
  • the NFVO saves the operation and maintenance package to be updated, saves the blueprint file in the operation and maintenance package to be updated to the catalog, and saves the software image package according to the file path of the operation and maintenance package.
  • the NFVO obtains the blueprint file in the Catalog according to the operation and maintenance package identifier
  • NFVO updates the mapping table of network element attributes and adaptation components in the blueprint file to the local.
  • the implementation of the NE type that can be supported by the operation and maintenance unit EM is described.
  • the core idea is to add the NE type of the supported NE type when the supported NE type is added.
  • the adaptation component mapping table the new adaptation component software image package is saved to the catalog and the software warehouse. Therefore, when the EM adds a supported network element type, there is no need to upgrade or abort the operation. And the new network element adaptation component will not run immediately, but will actually start running when the subsequent system needs it, and adapt to the real running condition of the system network element.
  • the NFVO changes the life cycle state of the adaptation component of the virtualized network element according to the change of the life cycle state of the virtualized network element, thereby virtualizing
  • the EM does not need to terminate the operation or upgrade process, which reduces the resource consumption and waste caused by the operation of the useless adaptation component.
  • This embodiment describes the specific implementation process of the foregoing embodiment by using the following specific embodiments.
  • the following embodiments may be applied to the network architecture shown in FIG. 1, and the NFVO in the architecture may include: a command verification module, a lifecycle management module, a resource allocation module, a component verification module, and a package management module.
  • the specific embodiment may include:
  • the VNFM sends a first notification message to the NFVO lifecycle management module, where The VNF network element is instantiated;
  • the first notification message includes the name, instance number, and network element blueprint identifier of the virtualized network element to be instantiated.
  • the NFVO lifecycle management sends a second notification message to the NFVO component verification module, to indicate that the VNF network element is instantiated;
  • the second notification message includes attribute information such as a name, a network element type, and a network element version of the virtualized network element to be instantiated.
  • the NFVO component verification module searches for an adaptation to be instantiated according to the mapping information between the adaptation component and the network element attribute information according to the attribute information such as the network element name, the network element type, and the network element version included in the second notification message.
  • the attribute information such as the network element name, the network element type, and the network element version included in the second notification message.
  • the network element attribute information is preferably a VNF network element type.
  • the NFVO component verification module initiates a query request to the NFVO lifecycle management module, and is used to query whether the adaptation component to be instantiated is in a running state;
  • the query request includes an adaptation component name to be instantiated and an adaptation component blueprint identifier to be instantiated.
  • S305 The NFVO lifecycle management module feeds back, to the NFVO component verification module, whether the adaptation component to be instantiated is running according to the instance lifecycle state maintained by itself.
  • the instantiation request includes the adaptation component name to be instantiated and the adaptation component blueprint identifier to be instantiated.
  • the NFVO command check module verifies the adaptation component instantiation request
  • the NFVO command verification module may determine whether the initiator of the adaptation component instantiation request has the command authority, and the information necessary in the component instantiation request, such as the adaptation component type, the adaptation blueprint identifier is complete, and the like.
  • the NFVO command verification module forwards the adaptation component instantiation request to the NFVO lifecycle management module.
  • the NFVO lifecycle management module initiates an adaptation component instantiation request to the VNFM.
  • the request command includes the type of the adaptation component to be instantiated and the adaptation component blueprint identifier to be instantiated.
  • the VNFM allocates an instance number and an operation task number to the adaptation component to be instantiated, and feeds back to the NFVO lifecycle management module.
  • the allocation instance number is convenient for the VNFM to avoid the instance number allocation conflict when receiving the multi-party instantiation request parallel processing, and the task number facilitates the NFVO to perform the task status query.
  • the VNFM downloads the blueprint of the adaptation component in Catallog according to the adaptation component type and the blueprint identifier in the adaptation component instantiation request.
  • the VFNM requests the NFVO resource management module to request resources for running the adaptation component.
  • the resources may include system resources such as network, memory, and CPU.
  • the NFVO resource management module returns resource authorization information to the VNFM.
  • S317 The VIM checks whether the required resource is available, and if so, allocates the resource and returns a resource allocation completion notification to the VFNM.
  • VNFM notifies the NFVO resource management module that the resource will be used by the adaptation component to be instantiated.
  • VNFM instantiates an adaptation component corresponding to the instantiated VNF network element in the operation and maintenance unit EM.
  • the VNFM After the adaptation component is instantiated, the VNFM notifies the NFVO lifecycle management module that the instantiated component is instantiated.
  • the effect of this embodiment is that as the new network element type is online on the system, its corresponding adaptation component will run along with it, so that the operation and maintenance unit EM can support the new network element without upgrading or suspending operation.
  • Type management The operation of the adaptation component automatically adapts to changes in the type of network element.
  • the specific embodiment may include:
  • the VNFM sends a third notification message to the NFVO lifecycle management module, to indicate that the VNF network element is terminated.
  • the third notification message includes the name of the terminated VNF network element, the network element type, the network element version, and the network element instance number.
  • the NFVO lifecycle management sends a fourth notification message to the NFVO component verification module, which is used to indicate that the VNF network element is terminated, and the fourth notification message also includes the terminated network element name, the network element type, the network element version, and the network. Attribute information such as the meta-instance number.
  • the NFVO component verification module determines, according to the attribute information in the fourth notification message, the adaptation component to be terminated according to the correspondence between the adaptation component and the network element attribute information.
  • the network element attribute information is preferably a VNF network element type.
  • the NFVO component verification module initiates a query request to the NFVO lifecycle management module to query whether the adaptation component to be terminated is in a running state.
  • the query request includes the name of the adaptation component to be terminated and the blueprint identifier of the adaptation component to be terminated.
  • S405 The NFVO lifecycle management module feeds back to the NFVO component verification module whether the adapter component to be terminated is running according to the instance lifecycle state maintained by the NFVO lifecycle management module. If the adapter component is to be terminated, the adapter component to be terminated is also returned. Instance number.
  • the NFVO component verification module initiates, to the NFVO lifecycle management module, a query request for whether the same type of network element instance of the VNF network element is running.
  • the NFVO lifecycle management module is based on the instance lifecycle state maintained by itself.
  • the NFVO component verification module feeds back and terminates the same type of network element instance of the VNF network element.
  • the request command contains the adaptation component instance number to be terminated.
  • the NFVO command check module may determine whether the adaptation component terminates the request initiator with command authority, and the information necessary for adapting the component termination request, if the adapter component instance number to be terminated is complete.
  • the NFVO command verification module forwards the adaptation component termination request to the NFVO lifecycle management module.
  • the request command includes an adaptation component instance number to be terminated.
  • the NFVO lifecycle management module sends an adaptation component termination request to the VNFM.
  • the request command includes an adaptation component instance number to be terminated.
  • the VNFM returns the operation task number to the NFVO lifecycle management module.
  • the operation task number facilitates the NFVO to initiate a query of the task operational status.
  • S414 The termination operation of the adaptation component that the VNFM notifies the NFVO lifecycle management module to terminate has been completed.
  • the notification content may be used to indicate that the resources of the adaptation component to be terminated have been released, and instruct the NFVO to perform resource usage status update.
  • the effect of this embodiment is that with the termination of a network element type in the system, its corresponding adaptation
  • the component will be terminated, so that the operation and maintenance unit EM can terminate the components that are not necessary for operation and release resources without upgrading or aborting the operation.
  • the operation of the adaptation component automatically adapts to changes in network element termination.
  • the specific embodiment may include:
  • the VNFM sends a fifth notification message to the NFVO lifecycle management module, to indicate that the VNF network element is upgraded.
  • the fifth notification message includes: the name of the upgraded network element, the type of the network element, the version of the network element before the upgrade, the version of the network element after the upgrade, and the instance number of the network element.
  • the NFVO lifecycle management sends a sixth notification message to the NFVO component verification module, which is used to indicate that the VNF network element is upgraded, and the sixth notification message includes the name of the upgraded network element, the network element type, and the network element version before the upgrade. NE version after upgrade, NE instance number.
  • the operation of the adaptation component of the VNF network element may include starting the adaptation component corresponding to the upgraded VNF network element and terminating the VNF network element before the upgrade.
  • Corresponding adaptation components in two aspects Correspondingly, for the adaptation component corresponding to the VNF network element after the upgrade is started, refer to step A series shown in FIG. 5; for the adaptation component corresponding to the VNF network element before the upgrade is terminated, refer to FIG. 5 Show step B series. Step A series and step B series can be performed concurrently.
  • the NFVO component verification module searches for the attribute information to be instantiated according to the mapping between the adaptation component and the network element attribute according to the attribute information of the network element name, the network element type, and the upgraded network element version included in the sixth notification message. With components.
  • the network element attribute information is preferably an upgraded VNF network element version.
  • the NFVO component verification module initiates a query request to the NFVO lifecycle management module, and is used to query whether the adaptation component to be instantiated is in a running state;
  • the query request includes an adaptation component name to be instantiated and an adaptation component blueprint identifier to be instantiated.
  • S505A The NFVO lifecycle management module feeds back to the NFVO component verification module whether the adaptation component to be instantiated is running according to the instance lifecycle state maintained by itself.
  • the request command contains the type of the adaptation component to be instantiated and the adaptation component blueprint identifier to be instantiated.
  • S507A The NFVO command check module verifies the adaptation component instantiation request
  • the NFVO command verification module may determine whether the initiator of the adaptation component instantiation request has the command authority, and the information necessary in the component instantiation request, such as the adaptation component type, the adaptation blueprint identifier is complete, and the like.
  • the NFVO command verification module forwards the adaptation component instantiation request to the NFVO lifecycle management module.
  • S509A The NFVO lifecycle management module initiates an adaptation component instantiation request to the VNFM.
  • the request command includes the type of the adaptation component to be instantiated and the adaptation component blueprint identifier to be instantiated.
  • S510A The VNFM allocates an instance number and an operation task number to the adaptation component to be instantiated, and feeds back to the NFVO lifecycle management module.
  • the allocation instance number is convenient for the VNFM to avoid the instance number allocation conflict when receiving the multi-party instantiation request parallel processing, and the task number facilitates the NFVO to perform the task status query.
  • S511A The VNFM downloads the blueprint of the adaptation component in Catallog according to the adaptation component type and the blueprint identifier in the adaptation component instantiation request.
  • VNFM downloads the adaptation component software image package in the software repository SWR.
  • S513A The VNFM analyzes the blueprint of the component and calculates the required resources.
  • S514A The VFNM requests the NFVO resource management module to request resources for running the adaptation component;
  • the resources may include system resources such as network, memory, and CPU.
  • S515A The NFVO resource management module returns resource authorization information to the VNFM.
  • S516A The VNFM requests the VIM to allocate resources
  • S517A The VIM checks whether the required resources are available, and if so, allocates the resources and returns a resource allocation completion notification to the VFNM.
  • the VNFM notifies the NFVO resource management module that the resource will be used by the adaptation component that needs to be instantiated.
  • the VNFM instantiates an adaptation component corresponding to the upgraded VNF network element in the operation and maintenance unit EM.
  • the VNFM After the adaptation component is instantiated, the VNFM notifies the NFVO lifecycle management module that the instantiated component is instantiated.
  • the NFVO component verification module determines, according to the attribute information of the upgraded network element, the network element type, and the network element version before the upgrade, according to the correspondence between the adaptation component and the network element attribute information. Terminated adapter component.
  • the network element attribute information is preferably a pre-upgrade VNF network element version.
  • S504B The NFVO component verification module initiates a query request to the NFVO lifecycle management module to query whether the adaptation component to be terminated is in a running state.
  • the query request includes the name of the adaptation component to be terminated and the blueprint identifier of the adaptation component to be terminated.
  • S505B The NFVO lifecycle management module feeds back to the NFVO component verification module whether the adapter component to be terminated is running according to the instance lifecycle state maintained by itself, and if the adapter component is to be terminated, the adapter component to be terminated is also returned. Instance number.
  • S506B If the adapter component is running, the NFVO component verification module is to NFVO Lifecycle The period management module initiates a query request for whether the same type of network element instance of the VNF network element is running.
  • S507B The NFVO lifecycle management module feeds back and terminates the same type of network element instance of the VNF network element to the NFVO component verification module according to the instance lifecycle state maintained by itself.
  • the request command contains the adaptation component instance number to be terminated.
  • the S509B NFVO command check module verifies the adaptation component termination request
  • the NFVO command check module may determine whether the adaptation component terminates the request initiator with command authority, and the information necessary for adapting the component termination request, if the adapter component instance number to be terminated is complete.
  • the request command includes an adaptation component instance number to be terminated.
  • S511B The NFVO lifecycle management module sends an adaptation component termination request to the VNFM.
  • the request command includes an adaptation component instance number to be terminated.
  • VNFM returns the operation task number to the NFVO lifecycle management module.
  • the operation task number facilitates the NFVO to initiate a query of the task operational status.
  • S514B The termination operation of the adaptation component that the VNFM notifies the NFVO lifecycle management module to terminate has been completed.
  • S515B The VNFM notifies the VIM to release the resources occupied by the adaptation component to be terminated.
  • S516B The VIM notifies the release of the VNFM resource.
  • the notification content may be used to indicate that the resources of the adaptation component to be terminated have been released. And instruct NFVO to update the resource usage status.
  • the effect of this embodiment is that, with the upgrade of the network element, the adaptation component corresponding to the upgraded network element will run, and the adaptation component corresponding to the network element before the upgrade will be terminated.
  • the operation and maintenance unit EM supports the management of the upgraded NEs without upgrading or aborting the operation.
  • the operation of the adaptation component automatically adapts to changes in the network element upgrade.
  • the core idea is that the newly added NE type does not upgrade the operation and maintenance unit EM or terminate the normal operation of the EM. Instead, the newly added network element type and adaptation component mapping table caused by the supported network element type, and the newly added adaptation component software image package are saved to the catalog and the software warehouse. The operation of the adapter component is still performed according to the real situation of the network element of the system, and is consistent with the running network element.
  • This embodiment may include:
  • S601 The operator or other docking unit initiates an operation and maintenance package update request
  • the update request includes an operation and maintenance package ID, an operation and maintenance package file path and file name, and an update information description.
  • the NFVO command verification module checks the update request.
  • the NFVO command verification module may determine whether the update request initiator has the corresponding operation authority, the operation maintenance package ID included in the update request, the operation and maintenance package file path and the file name, and whether the update information description is complete.
  • the information in the forwarded update request still includes the operation and maintenance package ID, and the operation and maintenance package file path and file name are included in the forwarding command.
  • the NFVO package management module determines whether the operation and maintenance package has been stored according to the operation and maintenance package ID, and returns an error information if not stored. If already in the library, the virtual network function descriptor (VNFD, Virtualised Network) in the package Function blueprint files such as Function Descriptor) are stored in the Catalog.
  • VNFD Virtualised Network
  • the NFVO package management module stores the software image package in the software warehouse.
  • the NFVO packet management module determines whether the update information description includes adaptation support for the newly added network element type; if yes, notifies the NFVO component verification module to update the mapping table between the network element type and the adaptation component.
  • the notification contains the updated operation and maintenance package ID, the file name, and the path on the Catalog.
  • the NFVO packet management module notifies the NFVO component verification module mapping table that there is an update.
  • the NFVO component verification module downloads the updated network element type and the adaptation component mapping table to the catalog for local storage.
  • S609 The NFVO component verification module notifies the NFVO package management module mapping table that the download is completed.
  • the NFVO package management module notifies the NFVO lifecycle management module that the package update operation has been completed.
  • the NFVO lifecycle management module notifies the operator or other docking unit operation maintenance package that initiates the operation to complete the update.
  • the effect of this embodiment is that when the operation and maintenance unit EM supports the new network element type, there is no need to upgrade or suspend operation. And the new network element adaptation component will not run immediately, but will actually start running when the subsequent system needs it, and adapt to the real running condition of the system network element.
  • the technical solution in the first embodiment is described by using four specific embodiments, and the life cycle state of the adaptation component of the VNF network element is changed according to the change of the life cycle state of the VNF network element by the NFVO, thereby When the life cycle state of the network element changes, the EM does not need to terminate the operation or upgrade process, which reduces the resource consumption and waste caused by the operation of the useless adaptation component.
  • a management device for a virtualized network element according to an embodiment of the present invention is shown. 70, the device 70 can be applied to the NFVO, the device 70 includes: a receiving unit 701, an obtaining unit 702, and a sending unit 703;
  • the receiving unit 701 is configured to receive lifecycle change information for the virtualized network element sent by the virtualized network function manager VNFM;
  • the obtaining unit 702 is configured to determine and determine an adaptation component corresponding to the virtualized network element
  • the sending unit 703 is configured to send an operation request for the adaptation component to the VNFM according to the lifecycle change information of the virtualized network element;
  • the receiving unit 701 is configured to acquire lifecycle change information and resource change information of the adaptation component from the VNFM.
  • the lifecycle change information of the virtualized network element includes: attribute information of the virtualized network element to be instantiated.
  • the obtaining unit 702 is configured to:
  • the attribute information includes: a virtualized network element name, a virtualized network element type, and a virtualized network element version.
  • the sending unit 703 is configured to:
  • the adaptation component instantiation request comprises: the type of the adaptation component to be instantiated And the blueprinting identifier is used by the VNFM to obtain the blueprint of the adaptation component to be instantiated according to the adaptation blueprint identifier, and calculate the requirement according to the blueprint of the adaptation component to be instantiated The resources required to instantiate the adaptation component runtime.
  • the receiving unit 701 is configured to receive a resource request request from the VNFM, where the resource request request is used to request that the adaptation component to be instantiated is required to run Resource
  • the sending unit 703 is configured to send resource authorization information to the VNFM according to the application information of the VNFM, where the resource authorization information is used to indicate that the VNFM requests the virtualized basic device management system VIM to allocate the required instantiation.
  • the receiving unit 701 is configured to receive a resource allocation result sent by the VNFM.
  • the lifecycle change information of the virtualized network element includes: attribute information of the terminated virtualized network element, where the attribute information of the terminated virtualized network element includes the name of the terminated virtualized network element, One or more of the NE type, the NE version, and the NE instance number.
  • the obtaining unit 702 is configured to:
  • the sending unit 703 is configured to:
  • the terminated network element of the same virtualized network element type is not in the running state, sending an adaptation component termination request to the VNFM; wherein the adaptation component termination request includes the adaptation component to be terminated Instance number.
  • the receiving unit 701 is configured to receive a termination completion notification sent by the VNFM after the termination of the adaptation component to be terminated, and the termination completion notification for the termination component to be terminated;
  • the lifecycle change information of the virtualized network element includes: virtualized network element attribute information before upgrade and upgraded virtualized network element attribute information.
  • the obtaining unit 702 is configured to:
  • the sending unit 703 is configured to:
  • the adapter component to be instantiated corresponding to the upgraded virtualized network element When the adapter component to be instantiated corresponding to the upgraded virtualized network element is not running, sending an instantiation of the adaptation component to be instantiated corresponding to the upgraded virtualized network element to the VNFM
  • the request component; the adaptation component instantiation request corresponding to the upgraded virtualized network element includes: an adapted component type and an adaptation blueprint corresponding to the upgraded virtualized network element to be instantiated
  • the adaptation blueprint identifier is used by the VNFM to obtain an adaptation component blueprint corresponding to the upgraded virtualized network element according to the adaptation blueprint identifier, and according to the upgraded virtualization
  • the adaptation component blueprint corresponding to the network element needs to calculate the resources required for the optimized component to be instantiated corresponding to the upgraded virtualized network element.
  • the receiving unit 701 is configured to receive a resource request request from the VNFM, where the resource request request is used to request resources required for the adaptation component to be instantiated to run;
  • the sending unit 703 is configured to send resource authorization information to the VNFM according to the resource request request, where the resource authorization information is used to indicate that the VNFM requests the VIM to allocate the upgraded virtualized network element.
  • the receiving unit 701 is configured to receive a resource allocation result sent by the VNFM.
  • the receiving component that needs to be instantiated corresponding to the upgraded virtualized network element sent by the VNFM corresponds to an instantiation completion notification.
  • the obtaining unit 702 is configured to:
  • the sending unit 703 is configured to:
  • the receiving unit 701 is configured to receive, after the VNFM terminates the adaptation component corresponding to the pre-upgrade virtualized network element, the adaptation component corresponding to the pre-upgrade virtualized network element Termination completion notice; and,
  • the receiving unit 701 is further configured to receive an update request, where the update request includes an operation maintenance package identifier to be updated, a file path of the operation maintenance package to be updated, and an update information description;
  • the device 70 further includes a saving unit 704 configured to determine, according to the operation and maintenance package identifier to be updated, the operation and maintenance package to be updated, and the operation and maintenance package to be updated.
  • the blueprint file is saved to the blueprint catalog catalog, and the software image package is saved to the software warehouse according to the file path of the operation and maintenance package;
  • the obtaining unit 702 is further configured to: when the update information description includes the support indication information of the newly added network element type, obtain the blueprint file in the catalog according to the operation and maintenance package identifier;
  • the apparatus 70 further includes an updating unit 705 configured to use the blueprint file.
  • the mapping table of the middle network element attribute and the adaptation component is updated to the local.
  • the device 70 involved in the embodiment is applied to the NFVO. Therefore, the functional unit in the device 70 can be implemented by using a specific functional module in the NFVO in the second embodiment. Therefore, in this embodiment, The functional units involved in the implementation of the specific embodiments of the second embodiment may correspond to the specific functional modules in the second embodiment.
  • a management device 90 for a virtualized network element may be provided, which may include: a communication interface 901, a memory 902, a processor 903, and a bus 904;
  • the bus 904 is configured to connect the communication interface 901, the processor 903, and the memory 902 and mutual communication between the devices;
  • the communication interface 901 is configured to perform data transmission with an external network element
  • the memory 902 is configured to store instructions and data
  • the processor 903 is configured to: instruct the communication interface 901 to receive service description information corresponding to a service to be transmitted;
  • the communication interface 901 is instructed to send the radio resource configuration information to the terminal.
  • the memory 902 may be a volatile memory, such as a random access memory (RAM), or a non-volatile memory, such as a read only memory.
  • RAM random access memory
  • ROM Read-Only Memory
  • flash memory hard disk (HDD, Hard Disk Drive) or solid state drive (SSD, Solid-State Drive); or a combination of the above types of memory, and to the processor 903 Provide instructions and data.
  • HDD Hard Disk Drive
  • SSD Solid-State Drive
  • the processor 903 may be an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), or a Programmable Logic Device (PLD). At least one of a Programmable Logic Device, a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, and a microprocessor. It is to be understood that, for the different devices, the electronic device for implementing the above-mentioned processor functions may be other, which is not specifically limited in the embodiment of the present invention.
  • ASIC Application Specific Integrated Circuit
  • DSP Digital Signal Processor
  • DSPD Digital Signal Processing Device
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • CPU Central Processing Unit
  • controller a controller
  • microcontroller a microcontroller
  • Embodiments of the present invention provide a computer storage medium storing computer executable instructions, which may be computer programs, application software, or compilable code, etc.; the computer executable instructions are executed Thereafter, the management method of the virtualized network element provided by the foregoing one or more technical solutions can be implemented, for example, the method shown in one or more of FIG. 2 to FIG.
  • the computer storage medium can be a non-transitory storage medium.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a 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.
  • an operation request for the adaptation component used by the virtualized network element is sent to the VNFM according to the lifecycle change information of the virtualized network element of the virtualized network element. Therefore, when a virtualized network element ends or is upgraded, the operation of the corresponding termination adaptation component is equivalent to using the lifecycle information of the virtualized network element to manage the lifecycle of the adaptation component used by the virtualized network element, thereby reducing the lifecycle management.
  • the operation of the useless adaptation component that does not need to be used reduces the system resources occupied by the adapter component, thereby reducing the system resource overhead, reducing the slow speed caused by the useless system component consumption of the system, and improving the system operation. Speed, thus having a positive industrial effect, and is easy to implement and achievable.

Abstract

本发明实施例公开了一种虚拟化网元的管理方法和装置；该方法可以包括：接收由虚拟化的网络功能管理器VNFM发送的针对虚拟化网元的生命周期变更信息；判断并确定所述虚拟化网元对应的适配组件；根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对所述适配组件的操作请求；从所述VNFM获取所述适配组件的生命周期变更信息和资源变更信息。本发明实施例还公开一种计算机存储介质。

Description

一种虚拟化网元的管理方法和装置及计算机存储介质
相关申请的交叉引用
本申请基于申请号为201611182006.0、申请日为2016年12月19日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明涉及网络技术，尤其涉及一种虚拟化网元的管理方法和装置及计算机存储介质。
背景技术
在移动通讯网络的管理领域，往往需要针对不同类型的网元进行操作和维护，因此，操作维护单元就需要同时针对不同类型网元进行兼管。但是，不同类型的网元之间，甚至同类型网元随着商用演进的变化，都会造成操作维护通讯协议及操作维护交互信息的结构也存在不同。
对于上述问题，当前操作维护单元所采用的技术方案是：针对不同网元类型或者针对存在通讯协议或操作维护交互信息差异的同类型网元开发专用的适配组件，需要说明的是，适配组件的作用是适配不同的通讯协议并解析不同的操作维护交互信息，将之适配成操作维护单元统一要求的格式。也就是说，经过适配组件的处理之后，所有的操作维护交互信息将去除不同通讯协议或信息结构所引起的差异，进入一致的操作维护处理模式。
在现有技术中，经常发现适配组件所消耗的系统资源大等问题。
发明内容
为解决上述技术问题，本发明实施例期望提供一种虚拟化网元的管理方法和装置；能够减少无用组件的运行就会增加对资源的消耗和浪费。
本发明的技术方案是这样实现的：
第一方面，本发明实施例提供了一种虚拟化网元的管理方法，所述方法包括：
接收由虚拟化的网络功能管理器VNFM发送的针对虚拟化网元的生命周期变更信息；
判断并确定所述虚拟化网元对应的适配组件；
根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对所述适配组件的操作请求；
从所述VNFM获取所述适配组件的生命周期变更信息和资源变更信息。
第二方面，本发明实施例提供了一种虚拟化网元的管理装置，所述装置包括：接收单元、获取单元、发送单元；其中，
所述接收单元，配置为接收由虚拟化的网络功能管理器VNFM发送的针对虚拟化网元的生命周期变更信息；
所述获取单元，配置为判断并确定所述虚拟化网元对应的适配组件；
所述发送单元，配置为根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对所述适配组件的操作请求；
所述接收单元，配置为从所述VNFM获取所述适配组件的生命周期变更信息和资源变更信息。
第三方面，本发明实施例提供一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令；所述计算机可执行指令被执行后，能够实现前述技术方案提供的虚拟化网元的管理方法。
本发明实施例提供了一种虚拟化网元的管理方法和装置及计算机存储介质；通过网络功能虚拟化编排器(NFVO，NFV Orchestration)且根据虚拟化网元的生命周期状态的变更对应的将虚拟化网元的适配组件的生命周期状态进行改变，第一方面，从而在虚拟化网元的生命周期状态发生改变时，减少了无用适配组件的运行所造成的资源消耗和浪费；第二方面，减少了不必要的适配组件运行占用的系统资源多，大致系统用于有用的适配组件少，进而导致的速度慢的问题，具有系统资源消耗少及运行速度快的特点；第三方面，不用网元管理实体或系统，主动检测需要停止运行的适配组件，再检测到需要停止运行的适配组件之后终止其运行，简化了已经无需再用到的适配组件的运行终止，不仅能够及时终止无需再使用的适配组件的终止运行，而且能够减少网元管理实体或系统的负荷。
附图说明
图1A为本发明实施例提供的一种网络功能虚拟化(NFV，Network Function Virtualization)架构示意图；
图1B为本发明实施例提供的另一种NFV架构示意图；
图2为本发明实施例提供的一种虚拟化网元的管理方法流程示意图；
图3为本发明实施例提供的具体实施例一的流程示意图；
图4为本发明实施例提供的具体实施例二的流程示意图；
图5为本发明实施例提供的具体实施例三的流程示意图；
图6为本发明实施例提供的具体实施例四的流程示意图；
图7为本发明实施例提供的一种虚拟化网元的管理装置结构示意图；
图8为本发明实施例提供的另一种虚拟化网元的管理装置结构示意图；
图9为本发明实施例提供的一种虚拟化网元的管理设备结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。
图1A为一种NFV系统架构示意图，如图1A所示，该NFV系统10可以包括：NFV管理和编排装置(NFV MANO，NFV Management and Orchestration)101、NFV基础设施层(NFVI，NFV Infrastructure)102、多个虚拟网络功能(VNF，Virtual Network Function)103、多个网元管理(EM，Element Manager)104、网络服务、VNF和基础设施描述(Network Service，VNF and Infrastructure Description)105、以及业务支持管理装置(OSS/BSS，Operation-Support System/Business Support System)106。其中，NFV-MANO101可以包括：NFV编排器(NFVO，NFV Orchestrator)1011、一个或多个VNF管理器(VNFM，VNF Manager)1012、以及虚拟化基础设施管理器(VIM，Virtualized Infrastructure Manager)1013；NFV MANO101主要用于对VNF103和NFVI102进行监视和管理；NFV MANO101中的NFVO1011主要用于接收来自一个或多个VNFM1012的资源相关请求，并发送配置信息到VNFM1012，收集VNF103的状态信息，另外，NFVO1011还用于与VIM1013通信，以实现资源的分配和/或预留以及交换虚拟化硬件资源的配置和状态信息；VNFM1012主要用于管理一个或多个VNF103，如：实例化、更新、查询、缩放和/或终止VNF103等；VIM1013主要执行资源管理的功能，例如管理基础设施资源的分配(例如增加资源到虚拟容器)和操作功能(如收集NFVI故障信息)。
NFVI 102可以包括计算硬件1021、存储硬件1022、网络硬件1023、虚拟化层(Virtualization Layer)、虚拟计算1024、虚拟存储1025和虚拟网络1026。NFVI102里面的虚拟化层可以从物理层抽象硬件资源和解耦VNF103，以便向VNF103提供虚拟化资源，虚拟计算1024和虚拟存储1025 可以以虚拟机、和/或其他虚拟容器的形式提供给VNF103，例如，一个或一个以上的VNF103可以部署在一个虚拟机(VM，Virtual Machine)上。虚拟化层抽象网络硬件1023从而形成虚拟网络1026，虚拟网络1026可以包括虚拟交换机(Virtual Switch)，虚拟交换机可以用来提供VNF103上的VM和其他VM之间的连接通信。
在本发明实施例中，如图1B所示，NFV架构可以包括：网络功能虚拟化编排器(NFVO，NFV Orchestration)、VNF管理器(VNFM，VNF Manager)、蓝图目录Catalog、软件仓库(SWR，SoftWare Repository)、网元管理(EM，Element Manager)和虚拟化基础设备管理系统(VIM，Virtual Infrastructure Manager)；其中，VNFM负责VNF实例的生命周期管理，例如实例化网元，终止网元及升级网元等；Catalog为保存软件包中所包含的各种蓝图和配套文件，并提供下载；SWR为保存软件包中所包含的软件镜像文件，并提供下载，比如保存放置VNF Package，该Package除了软件镜像包之外，还包括VNF的各种说明文件和配套使用文件，例如EM Package支持的所有的网元类型以及配套的适配组件列表等；EM为本系统中的所有VNF提供操作维护功能；VIM则为网络功能虚拟化基础设施(NFVI，Network Function Virtualization Infrastructure)提供控制和管理。
需要说明的是，本发明实施例中所述的网元，均为虚拟化网元，是通过虚拟化网络功能来完成和实现的。
研究发现，由于无法预知操作维护单元需要管理哪些类型的网元，通常在版本发布时，操作维护单元的软件包往往是将自身所有支持的网元类型的适配组件全部打包。从而在版本运行时，操作维护单元就会启动所有能够支持的网元类型的适配组件，这使得一些不必要的适配组件占用了系统的资源，进而导致系统资源的开销大的问题。可选地，随着虚拟化技术的发展，以及物联网的推广，移动通讯网络的网元类型会更加丰富多样， 并且网络类型进行演进及淘汰的速度也会大大加快，所以在版本运行时，操作维护单元由于启动所有能够支持的网元类型的适配组件，因此，无用组件的运行就会增加对资源的消耗和浪费。因此以下基于图1A及图1B所示的架构，提出本申请的以下实施例。
实施例一
参见图2，其示出了本发明实施例提供的一种虚拟化网元的管理方法，该方法可以应用于NFV架构中的NFVO，该方法可以包括：
S201：接收由VNFM发送的针对虚拟化网元的生命周期变更信息；
S202：判断并确定虚拟化网元对应的适配组件；
S203：根据虚拟化网元的生命周期变更信息向VNFM发送针对适配组件的操作请求；
S204：从VNFM获取适配组件的生命周期变更信息和资源变更信息。
需要说明的是，在本实施例中，虚拟化网元例如可以为VNF网元，后续不再赘述。
针对虚拟化网元所对应的生命周期变更以及针对虚拟化网元对应的适配组件的操作均是对于各自生命周期的操作；可选地，针对虚拟化网元所对应的生命周期变更可以包括：虚拟化网元实例化、虚拟化网元终止、虚拟化网元升级等操作；而对应于虚拟化网元实例化，适配组件相应的操作可以包括适配组件的实例化；对应于虚拟化网元终止，适配组件相应的操作可以包括适配组件的实例终止；对应于虚拟化网元升级，适配组件相应的操作包括：升级后适配组件的实例化以及升级前适配组件的终止。
可以理解地，在本实施例以及本申请的后续实施例中，术语“实例化的”(或实例化)的含义表示在虚拟化基础设施中，虚拟化网元通过某些通信网络元素或功能以可用的某种方式设立、开启、激活、创建或进行自身的虚拟化网络功能。所述实例化，可包括：根据需要实例化的虚拟化网元 的描述信息，分配虚拟化网元所需的资源，创建一个虚拟化网元的实例，并为该实例分配实例标识等，该虚拟化网元的实例可以用于通信。
通过上述方案，可以看出，适配组件的生命周期根据虚拟化网元的生命周期相对应，因此，无需在版本运行时，启动EM所有能够支持的网元类型的适配组件，减少了无用适配组件的运行所造成的资源消耗和浪费；并且EM在VNF和适配组件的生命周期进行变更时，无需终止运行就可以自动适应VNF和适配组件的生命周期变化。
例如，在一些实施例中，所述适配组件的生命周期与其对应(即需要其进行适配的虚拟化网元的生命周期对应，如此，若一个虚拟化网元的运行终止，则该虚拟化网元所使用的专属的适配组件也将终止。若一个虚拟化网元升级了，不再需要使用旧的适配组件，则相当于低版本的虚拟化网元生命周期终止了，低版本的虚拟化网元使用的适配组件也会相应的终止。故所述操作请求，至少包括：指示所述适配组件在其对应的虚拟化网元的运行终止时结束运行的终止请求。
以下通过虚拟化网元具体的生命周期状态对图2所示的技术方案进行说明。
示例性地，当虚拟化网元实例化完成后，所述虚拟化网元的生命周期变更信息，包括：需实例化的虚拟化网元的属性信息。对于步骤S202，所述判断并确定所述虚拟化网元对应的适配组件，可包括：根据需实例化的虚拟化网元的属性信息判断并确定所述需实例化的虚拟化网元对应的需实例化的适配组件。
可选地，需实例化的虚拟化网元的属性信息可以包括：虚拟化网元名称，虚拟化网元类型，虚拟化网元版本等信息中的一项或多项。NFVO可以通过查找适配组件与网元类型、网元版本等虚拟化网元属性信息之间的映射表来获取需实例化的适配组件。
需要说明的是，不同虚拟化网元类型可以对应不同的适配组件；而对于相同类型的虚拟化网元，不同的网元版本也会对应不同的适配组件；因此，在实际应用时，适配组件可以和不止一种虚拟化网元属性信息之间具有映射关系。
相应地，对于步骤S203，所述根据虚拟化网元的生命周期变更信息向VNFM发送针对适配组件的操作请求，可包括：
当需实例化的适配组件未运行时，向VNFM发送适配组件实例化请求；其中，所述适配组件实例化请求包括：需实例化的适配组件类型和适配蓝图标识；适配蓝图标识用于VNFM根据适配蓝图标识获取需实例化的适配组件蓝图，并根据所述需实例化的适配组件蓝图计算所述需实例化的适配组件运行时所需的资源。
相应地，对于步骤S204，所述从VNFM获取适配组件的生命周期变更信息和资源变更信息，可包括：
从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的资源；
以及，根据资源申请请求向VNFM发送资源授权信息；所述资源授权信息用于指示VNFM向VIM请求分配所述需实例化的适配组件运行时所需的资源；
以及，接收VNFM发送的资源分配结果；
以及，接收VNFM发送的所述需实例化的适配组件对应实例化完成通知。
可选地，VNFM计算得到所述需实例化的适配组件运行时所需的资源之后，可以向NFVO申请适配组件运行所需的资源，比如网络资源，内存资源，CPU资源等系统资源；并且VNFM在接收到NFVO返回的资源授权信息之后，可以请求VIM分配资源；当VIM查看所需的资源可以提供时， 会分配资源并返回资源分配完成通知给VFNM；VNFM就会通知NFVO所需的资源将被适配组件使用，并且VNFM实例化操作维护单元EM所需要的实例化完成的虚拟化网元的适配组件后，通知NFVO需实例化的适配组件实例化完成。
需要说明的是，对于本示例，新类型网元在系统上线后，其相应的适配组件会随之运行，使得操作维护单元EM无须升级或者中止运行，即可支持对新类型网元的管理，适配组件的运行能够自动适应EM所管理的网元的变化。
示例性地，当虚拟化网元终止完成后，所述虚拟化网元的生命周期变更信息包括：终止的虚拟化网元的属性信息。对于步骤S202，具体可以包括：
根据终止的虚拟化网元的属性信息获取所述终止的虚拟化网元对应的需终止的适配组件；
可选地，终止的虚拟化网元的属性信息可以包括：终止的虚拟化网元的名称、网元类型、网元版本、网元实例号等。NFVO可以通过查找适配组件与虚拟化网元的属性信息之间的映射表来获取需终止的适配组件。
相应地，对于步骤S203，可以包括：
确定需终止的适配组件的运行状态；
当所述需终止的适配组件正在运行时，确定所述需终止的适配组件对应的实例号以及所述终止的虚拟化网元类型相同的网元是否处于运行状态；
当所述终止的虚拟化网元类型相同的网元没有处于运行状态时，向所述VNFM发送适配组件终止请求；其中，所述适配组件终止请求包括所述需终止的适配组件的实例号。
相应地，对于步骤S204，所述从VNFM获取适配组件的生命周期变更 信息和资源变更信息，可包括：
接收VNFM终止所述需终止的适配组件之后所发送的针对所述需终止的适配组件的终止完成通知；
接收VNFM在所述需终止的适配组件的资源释放完成之后，所发送的资源释放通知。
可选地，VNFM在接收到适配组件终止请求之后，会向NFVO返回操作任务号，以便于NFVO能够发起针对任务操作状态的查询；并且VNFM终止所述需终止的适配组件之后，NFVO针对所述需终止的适配组件的终止操作已经完成；VNFM通知VIM释放所述需终止的适配组件所占用的资源，并且VIM通知VNFM资源释放完成后，VNFM通知NFVO，所述需终止的适配组件所占用的资源已经释放，资源使用状态更新。
需要说明的是，对于本示例，随着某种网元类型的虚拟化网元在系统的运行终止，其相应的适配组件会随之终止，使得操作维护单元EM无须自行升级或者中止运行，即可终止已无运行必要的适配组件，释放资源。
示例性地，虚拟化网元升级完成后，所述虚拟化网元的生命周期变更信息包括：升级后的虚拟化网元的属性信息以及升级前的虚拟化网元的属性信息。需要说明的是，由于涉及到虚拟化网元的升级，相应地，针对虚拟化网元的适配组件的操作，可以包括启动运行升级后的虚拟化网元对应的需实例化的适配组件以及终止升级前的虚拟化网元对应的适配组件两个方面。
一方面，针对启动运行升级后的虚拟化网元对应的需实例化的适配组件，需要说明的是：
对于步骤S202，所述判断并确定所述虚拟化网元对应的适配组件，可包括：
根据升级后的虚拟化网元的属性信息确定所述升级后的虚拟化网元对 应的适配组件。
可选地，升级后的虚拟化网元的属性信息可以包括：网元名称、网元类型、升级后的网元版本，网元实例标识等信息。NFVO可以通过查找适配组件与网元类型、升级后的网元版本等虚拟化网元属性信息之间的映射表来获取需实例化的适配组件。
对于步骤S203，所述根据虚拟化网元的生命周期变更信息向所述VNFM发送针对适配组件的操作请求，可包括：
当升级后的虚拟化网元对应的需实例化的适配组件未运行时，向VNFM发送针对升级后的虚拟化网元对应的需实例化的适配组件的实例化请求；其中，所述升级后的虚拟化网元对应的需实例化的适配组件实例化请求包括：升级后的虚拟化网元对应的需实例化的适配组件类型和适配蓝图标识；适配蓝图标识用于VNFM根据适配蓝图标识获取升级后的虚拟化网元对应的需实例化的适配组件蓝图，并根据所述升级后的虚拟化网元对应的需实例化的适配组件蓝图计算所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源。
对于步骤S204，所述从VNFM获取适配组件的生命周期变更信息和资源变更信息，可包括：
从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的资源；
以及，根据资源申请请求向VNFM发送资源授权信息；所述资源授权信息用于指示VNFM向VIM请求分配所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源；
以及，接收VNFM发送的资源分配结果；
以及，接收VNFM发送的所述升级后的虚拟化网元对应的需实例化的适配组件对应实例化完成通知。
可选地，VNFM计算得到所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源之后，可以向NFVO申请适配组件运行所需的资源，比如网络资源，内存资源，CPU资源等系统资源；并且VNFM在接收到NFVO返回的资源授权信息之后，可以请求VIM分配资源；当VIM查看所需的资源可以提供时，会分配资源并返回资源分配完成通知给VFNM；VNFM就会通知NFVO所需的资源将被适配组件使用，并且VNFM实例化操作维护单元EM所需要的实例化完成的虚拟化网元的适配组件后，通知NFVO需实例化的适配组件实例化完成。
另一方面，针对终止升级前的虚拟化网元对应的适配组件，需要说明的是：
对于步骤S202，所述判断并确定所述虚拟化网元对应的适配组件，可包括：
根据升级前的虚拟化网元的属性信息获取所述升级前的虚拟化网元对应的适配组件；
可选地，升级前的虚拟化网元的属性信息可以包括：虚拟化网元名称、网元类型、升级前的网元版本、网元实例号等。NFVO可以通过查找适配组件与升级前的虚拟化网元的属性信息之间的映射表来获取升级前的虚拟化网元对应的适配组件。
对于步骤S203，所述根据虚拟化网元的生命周期变更信息向VNFM发送针对适配组件的操作请求，可包括：
确定升级前的虚拟化网元对应的适配组件的运行状态；
当升级前的虚拟化网元对应的适配组件正在运行时，获取升级前的虚拟化网元对应的适配组件对应的实例号；
当确定没有与升级前的虚拟化网元类型相同的网元处于运行状态时，向VNFM发送适配组件终止请求；其中，适配组件终止请求包括升级前的 虚拟化网元对应的适配组件的实例号。
对于步骤S204，所述从VNFM获取适配组件的生命周期变更信息和资源变更信息，可包括：
接收VNFM终止所述升级前的虚拟化网元对应的适配组件之后所发送的针对所述升级前的虚拟化网元对应的适配组件的终止完成通知；
接收VNFM在所述升级前的虚拟化网元对应的适配组件的资源释放完成之后，所发送的资源释放通知。
可选地，VNFM在接收到适配组件终止请求之后，会向NFVO返回操作任务号，以便于NFVO能够发起针对任务操作状态的查询；并且VNFM终止所述升级前的虚拟化网元对应的适配组件之后，NFVO针对所述升级前的虚拟化网元对应的适配组件的终止操作已经完成；VNFM通知VIM释放所述升级前的虚拟化网元对应的适配组件所占用的资源，并且VIM通知VNFM资源释放完成后，VNFM通知NFVO，所述升级前的虚拟化网元对应的适配组件所占用的资源已经释放，资源使用状态更新。
需要说明的是，通过上述针对启动运行升级后网元对应的升级后的虚拟化网元对应的需实例化的适配组件以及终止升级前网元对应的升级前的虚拟化网元对应的适配组件这两个方面的实现方案，可以了解到，当虚拟化网元升级之后，就需要针对升级后网元对应的升级后的虚拟化网元对应的需实例化的适配组件进行实例化，并且对升级前网元对应的升级前的虚拟化网元对应的适配组件进行终止，具体实现过程可以参照前述示例中针对实例化完成后的VNF对应的适配组件进行运行的方案以及针对终止后的VNF对应的适配组件进行终止的方案，本实施例对此不做赘述。
示例性地，当EM新增能够支持的网元类型时，所述方法还包括：
NFVO接收更新请求；其中，更新请求包括待更新的操作维护包标识、待更新的操作维护包的文件路径以及更新信息说明；
NFVO根据待更新的操作维护包标识确定所述待更新的操作维护包入库之后，将待更新的操作维护包中的蓝图文件保存至Catalog，并根据操作维护包的文件路径将软件镜像包保存至软件仓库；
更新信息说明中包括有新增网元类型的支持指示信息时，NFVO根据操作维护包标识获取Catalog中的蓝图文件；
NFVO将蓝图文件中网元属性和适配组件的映射表更新至本地。
需要说明的是，对于本示例，说明了操作维护单元EM新增能够支持的网元类型实施过程，核心思路是新增支持的网元类型时，将新增支持网元类型引起的网元类型和适配组件映射表，新增的适配组件软件镜像包保存到Catalog和软件仓库。从而EM新增支持的网元类型时，无须升级或者中止运行。并且新的网元适配组件也不会立即运行，而是在后续系统需要的时候真正启动运行，和系统网元的真实运行情况适配。
本实施例提供的一种虚拟化网元的管理方法，通过NFVO根据虚拟化网元的生命周期状态的变更对应的将虚拟化网元的适配组件的生命周期状态进行改变，从而在虚拟化网元的生命周期状态发生改变时，EM无需进行终止运行或升级过程，减少了无用适配组件的运行所造成的资源消耗和浪费。
实施例二
本实施例通过以下具体实施例对上述实施例的具体实现过程进行阐述。下述实施例可以应用于图1所示的网络架构，并且架构中的NFVO可以包括：命令校验模块、生命周期管理模块、资源分配模块、组件校验模块和包管理模块。
具体实施例一
参见图3，当VNF网元实例化之后，本具体实施例可以包括：
S301：VNFM向NFVO生命周期管理模块发送第一通知消息，用于指 示VNF网元实例化完成；
其中，第一通知消息中包含需实例化的虚拟化网元的名称、实例号以及使用的网元蓝图标识。
S302：NFVO生命周期管理向NFVO组件校验模块发送第二通知消息，用于指示VNF网元实例化完成；
可以理解地，第二通知消息中包含需实例化的虚拟化网元的名称、网元类型、网元版本等属性信息。
S303：NFVO组件校验模块根据第二通知消息中包含的网元名称，网元类型，网元版本等属性信息，根据适配组件和网元属性信息之间映射表查找需实例化的适配组件。
可选地，本实施例中，网元属性信息优选为VNF网元类型。
S304：NFVO组件校验模块向NFVO生命周期管理模块发起查询请求，用于查询需实例化的适配组件是否处于运行状态；
其中，查询请求包括需实例化的适配组件名称和需实例化的适配组件蓝图标识。
S305：NFVO生命周期管理模块根据自身维护的实例生命周期状态，向NFVO组件校验模块反馈需实例化的适配组件是否运行。
S306：当需实例化的适配组件未运行时，NFVO组件校验模块向NFVO命令校验模块发起适配组件实例化请求；
可以理解地，这也是对操作维护单元EM instance的更新；实例化请求中包括需实例化的适配组件名称和需实例化的适配组件蓝图标识。
S307：NFVO命令校验模块校验适配组件实例化请求；
可选地，NFVO命令校验模块可以判断适配组件实例化请求的发起方是否具备命令权限，以及适配组件实例化请求中必须的信息如适配组件类型，适配蓝图标识是否完整等。
S308：校验通过后，NFVO命令校验模块将适配组件实例化请求转发给NFVO生命周期管理模块。
S309：NFVO生命周期管理模块向VNFM发起适配组件实例化请求。
可以理解地，请求命令中包含需实例化的适配组件类型和需实例化的适配组件蓝图标识。
S310：VNFM为需实例化的适配组件分配实例号以及本次操作任务号，并反馈给NFVO生命周期管理模块。
可选地，分配实例号是便于VNFM在接收多方实例化请求并行处理时避免实例号分配冲突，任务号便于NFVO进行任务状态的查询。
S311：VNFM根据适配组件实例化请求中适配组件类型和蓝图标识，在Catallog下载适配组件的蓝图。
S312：VNFM在软件仓库SWR下载适配组件软件镜像包。
S313：VNFM分析适配组件蓝图，计算所需资源。
S314：VFNM向NFVO资源管理模块申请运行适配组件所需资源；
其中，资源可以包括网络，内存，CPU等系统资源。
S315：NFVO资源管理模块返回资源授权信息给VNFM。
S316：VNFM请求VIM分配资源；
S317：VIM查看所需资源是否可以提供，如果可以，则分配资源并返回资源分配完成通知给VFNM。
S318：VNFM通知NFVO资源管理模块资源将被需实例化的适配组件使用。
S319：VNFM实例化操作维护单元EM中实例化后的VNF网元对应的适配组件。
S320：适配组件实例化完成后，VNFM通知NFVO生命周期管理模块需实例化的适配组件实例化完成。
本具体实施例的效果是，随着新的网元类型在系统的上线，其相应的适配组件会随之运行，使得操作维护单元EM无须升级或者中止运行，即可支持对新的网元类型的管理。适配组件的运行自动适应网元类型的变化。
具体实施例二
参见图4，当VNF网元终止之后，本具体实施例可以包括：
S401：VNFM向NFVO生命周期管理模块发送第三通知消息，用于指示有VNF网元终止完成；
其中，第三通知消息包括终止的VNF网元的名称，网元类型，网元版本，网元实例号等属性信息。
S402：NFVO生命周期管理向NFVO组件校验模块发送第四通知消息；用于指示有VNF网元终止完成，第四通知消息中也包括终止的网元名称，网元类型，网元版本，网元实例号等属性信息。
S403：NFVO组件校验模块根据第四通知消息中的属性信息，根据适配组件和网元属性信息之间的对应关系确定需终止的适配组件。
可选地，本实施例中，网元属性信息优选为VNF网元类型。
S404：NFVO组件校验模块向NFVO生命周期管理模块发起查询请求，用于查询需终止的适配组件是否处于运行状态。
其中，查询请求包括需终止的适配组件名称和需终止的适配组件蓝图标识。
S405：NFVO生命周期管理模块根据自身维护的实例生命周期状态，向NFVO组件校验模块反馈需终止的适配组件是否运行，如果需终止适配组件正在运行，则同时返回需终止的适配组件实例号。
S406：如果适配组件运行中，NFVO组件校验模块向NFVO生命周期管理模块发起与终止的VNF网元同类型网元实例是否运行的查询请求。
S407：NFVO生命周期管理模块根据自身维护的实例生命周期状态， 向NFVO组件校验模块反馈与终止的VNF网元同类型网元实例是否运行。
S408：如果没有同类型网元处于运行中，NFVO组件校验模块向NFVO命令校验模块发起适配组件终止请求，
可以理解地，这也是对操作维护单元EM instance的更新。请求命令中包含需终止的适配组件实例号。
S409：NFVO命令校验模块校验适配组件终止请求；
可选地，NFVO命令校验模块可以判断适配组件终止请求发起方是否具备命令权限，以及适配组件终止请求中必须的信息如需终止的适配组件实例号是否完整。
S410：校验通过后，NFVO命令校验模块将适配组件终止请求转发NFVO生命周期管理模块。
其中，请求命令中包含需终止的适配组件实例号。
S411：NFVO生命周期管理模块将适配组件终止请求发送到VNFM。
可以理解地，请求命令中包含需终止的适配组件实例号。
S412：VNFM返回本次操作任务号给NFVO生命周期管理模块。
可以理解地，操作任务号便于NFVO能够发起任务操作状态的查询。
S413：VNFM终止需终止的适配组件。
S414：VNFM通知NFVO生命周期管理模块需终止的适配组件的终止操作已经完成。
S415：VNFM通知VIM释放需终止的适配组件占用的资源。
S416：VIM通知VNFM资源释放完成。
S417：VNFM通知NFVO资源管理模块；
可选地，通知内容可以用于说明需终止的适配组件的资源已经释放，并指示NFVO进行资源使用状态更新。
本实施例的效果是，随着一种网元类型在系统的终止，其相应的适配 组件会随之终止，使得操作维护单元EM无须升级或者中止运行，即可终止已无运行必要的组件，释放资源。适配组件的运行自动适应网元终止的变化。
具体实施例三
参见图5，当VNF网元升级之后，本具体实施例可以包括：
S501：VNFM向NFVO生命周期管理模块发送第五通知消息，用于指示有VNF网元升级完成；
其中，第五通知消息包括：升级网元的名称，网元类型，升级前网元版本，升级后网元版本，网元实例号等属性信息。
S502：NFVO生命周期管理向NFVO组件校验模块发送第六通知消息；用于指示有VNF网元升级完成，第六通知消息中包含升级网元的名称，网元类型，升级前网元版本，升级后网元版本，网元实例号。
需要说明的是，由于涉及到VNF网元的升级，因此，针对VNF网元的适配组件的操作，可以包括启动运行升级后的VNF网元对应的适配组件以及终止升级前的VNF网元对应的适配组件两个方面。相应地，对于启动运行升级后的VNF网元对应的适配组件，可以参见图5中所示的步骤A系列；对于终止升级前的VNF网元对应的适配组件，可以参见图5中所示的步骤B系列。步骤A系列和步骤B系列可以并发进行。
下面是步骤A系列的详细说明：
S503A：NFVO组件校验模块根据第六通知消息中包含的网元名称，网元类型，升级后网元版本等属性信息，根据适配组件和网元属性之间映射表查找需实例化的适配组件。
可选地，本实施例中，网元属性信息优选为升级后的VNF网元版本。
S504A：NFVO组件校验模块向NFVO生命周期管理模块发起查询请求，用于查询需实例化的适配组件是否处于运行状态；
其中，查询请求包括需实例化的适配组件名称和需实例化的适配组件蓝图标识。
S505A：NFVO生命周期管理模块根据自身维护的实例生命周期状态，向NFVO组件校验模块反馈需实例化的适配组件是否运行。
S506A：当需实例化的适配组件未运行时，NFVO组件校验模块向NFVO命令校验模块发起适配组件实例化请求，
可以理解地，这也是对操作维护单元EM instAnce的更新。请求命令中包含需实例化的适配组件类型和需实例化的适配组件蓝图标识。
S507A：NFVO命令校验模块校验适配组件实例化请求；
可选地，NFVO命令校验模块可以判断适配组件实例化请求的发起方是否具备命令权限，以及适配组件实例化请求中必须的信息如适配组件类型，适配蓝图标识是否完整等。
S508A：校验通过后，NFVO命令校验模块将适配组件实例化请求转发给NFVO生命周期管理模块。
S509A：NFVO生命周期管理模块向VNFM发起适配组件实例化请求。
可以理解地，请求命令中包含需实例化的适配组件类型和需实例化的适配组件蓝图标识。
S510A：VNFM为需实例化的适配组件分配实例号以及本次操作任务号，并反馈给NFVO生命周期管理模块。
可选地，分配实例号是便于VNFM在接收多方实例化请求并行处理时避免实例号分配冲突，任务号便于NFVO进行任务状态的查询。
S511A：VNFM根据适配组件实例化请求中适配组件类型和蓝图标识，在Catallog下载适配组件的蓝图。
S512A：VNFM在软件仓库SWR下载适配组件软件镜像包。
S513A：VNFM分析适配组件蓝图，计算所需资源。
S514A：VFNM向NFVO资源管理模块申请运行适配组件所需资源；
其中，资源可以包括网络，内存，CPU等系统资源。
S515A：NFVO资源管理模块返回资源授权信息给VNFM。
S516A：VNFM请求VIM分配资源；
S517A：VIM查看所需资源是否可以提供，如果可以，则分配资源并返回资源分配完成通知给VFNM。
S518A：VNFM通知NFVO资源管理模块资源将被需实例化的适配组件使用。
S519A：VNFM实例化操作维护单元EM中升级后的VNF网元对应的适配组件。
S520A：适配组件实例化完成后，VNFM通知NFVO生命周期管理模块需实例化的适配组件实例化完成。
下面是步骤B系列的详细说明：
S503B：NFVO组件校验模块根据第六通知消息中包含的升级网元的名称，网元类型，升级前网元版本等属性信息，根据适配组件和网元属性信息之间的对应关系确定需终止的适配组件。
其中，本实施例中，网元属性信息优选为升级前VNF网元版本。
S504B：NFVO组件校验模块向NFVO生命周期管理模块发起查询请求，用于查询需终止的适配组件是否处于运行状态。
其中，查询请求包括需终止的适配组件名称和需终止的适配组件蓝图标识。
S505B：NFVO生命周期管理模块根据自身维护的实例生命周期状态，向NFVO组件校验模块反馈需终止的适配组件是否运行，如果需终止适配组件正在运行，则同时返回需终止的适配组件实例号。
S506B：如果适配组件运行中，NFVO组件校验模块向NFVO生命周 期管理模块发起与终止的VNF网元同类型网元实例是否运行的查询请求。
S507B：NFVO生命周期管理模块根据自身维护的实例生命周期状态，向NFVO组件校验模块反馈与终止的VNF网元同类型网元实例是否运行。
S508B：如果没有同类型网元处于运行中，NFVO组件校验模块向NFVO命令校验模块发起适配组件终止请求，
可以理解地，这也是对操作维护单元EM instance的更新。请求命令中包含需终止的适配组件实例号。
S509B NFVO命令校验模块校验适配组件终止请求；
可选地，NFVO命令校验模块可以判断适配组件终止请求发起方是否具备命令权限，以及适配组件终止请求中必须的信息如需终止的适配组件实例号是否完整。
S510B：校验通过后，NFVO命令校验模块将适配组件终止请求转发NFVO生命周期管理模块。
其中，请求命令中包含需终止的适配组件实例号。
S511B：NFVO生命周期管理模块将适配组件终止请求发送到VNFM。
可以理解地，请求命令中包含需终止的适配组件实例号。
S512B：VNFM返回本次操作任务号给NFVO生命周期管理模块。
可以理解地，操作任务号便于NFVO能够发起任务操作状态的查询。
S513B：VNFM终止需终止的适配组件。
S514B：VNFM通知NFVO生命周期管理模块需终止的适配组件的终止操作已经完成。
S515B：VNFM通知VIM释放需终止的适配组件占用的资源。
S516B：VIM通知VNFM资源释放完成。
S517B：VNFM通知NFVO资源管理模块；
可选地，通知内容可以用于说明需终止的适配组件的资源已经释放， 并指示NFVO进行资源使用状态更新。
本实施例的效果是，随着网元的升级，升级后的网元对应的适配组件会随之运行，升级前的网元对应的适配组件会随之终止。操作维护单元EM无须升级或者中止运行，即可支持升级后网元的管理。适配组件的运行自动适应网元升级的变化。
具体实施例四
参见图6，当EM新增支持的网元类型时，核心思路是新增支持的网元类型既不升级操作维护单元EM，也不终止EM的正常运行。而是将新增支持网元类型引起的网元类型和适配组件映射表，新增的适配组件软件镜像包保存到Catalog和软件仓库。适配组件的运行仍然是按照系统的网元真实情况进行，和运行的网元保持一致。本具体实施例可以包括：
S601：操作者或者其它对接单元发起操作维护包更新请求；
其中，更新请求包含操作维护包ID，操作维护包文件路径和文件名以及更新信息说明等。
S602：NFVO命令校验模块对更新请求进行校验；
可选地，NFVO命令校验模块可以判断更新请求发起者是否具有相应操作权限，以及更新请求中包括的操作维护包ID，操作维护包文件路径和文件名，本次更新信息说明等是否完整。
S603：校验通过后，NFVO命令校验模块将更新请求转发给NFVO包管理模块；
可以理解地，转发的更新请求中的信息仍然包括操作维护包ID，操作维护包文件路径和文件名等包含在转发命令中。
S604：NFVO包管理模块接收到操作维护包更新请求后，根据操作维护包ID判断该操作维护包是否已经入库，如果未入库，则返回报错信息。如果已经入库，则将包中的虚拟网络功能描述符(VNFD，Virtualised Network  Function Descriptor)等蓝图文件存入到Catalog。
S605：NFVO包管理模块将软件镜像包存入软件仓库。
S606：NFVO包管理模块判断更新信息说明中是否包含对新增网元类型的适配支持；如果包含，则通知NFVO组件校验模块更新网元类型和适配组件之间的映射表。
可以理解地，该通知中包含更新的操作维护包ID，文件名以及Catalog上的路径。
S607：NFVO包管理模块通知NFVO组件校验模块映射表有更新。
S608：NFVO组件校验模块到Catalog上下载更新后网元类型和适配组件映射表进行本地保存。
S609：NFVO组件校验模块通知NFVO包管理模块映射表下载完成。
S610：NFVO包管理模块通知NFVO生命周期管理模块包更新操作已经完成。
S611：NFVO生命周期管理模块通知操作者或者发起操作的其它对接单元操作维护包更新完成。
本实施例的效果是，当操作维护单元EM支持新的网元类型时，无须升级或者中止运行。并且新的网元适配组件也不会立即运行，而是在后续系统需要的时候真正启动运行，和系统网元的真实运行情况适配。
上述通过四个具体实施例对实施例一中的技术方案进行说明，通过NFVO根据VNF网元的生命周期状态的变更对应的将VNF网元的适配组件的生命周期状态进行改变，从而在VNF网元的生命周期状态发生改变时，EM无需进行终止运行或升级过程，减少了无用适配组件的运行所造成的资源消耗和浪费。
实施例三
参见图7，其示出了本发明实施例提供的一种虚拟化网元的管理装置 70，该装置70可以应用于NFVO中，该装置70包括：接收单元701、获取单元702、发送单元703；其中，
所述接收单元701，配置为接收由虚拟化的网络功能管理器VNFM发送的针对虚拟化网元的生命周期变更信息；
所述获取单元702，配置为判断并确定所述虚拟化网元对应的适配组件；
所述发送单元703，配置为根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对所述适配组件的操作请求；
所述接收单元701，配置为从所述VNFM获取所述适配组件的生命周期变更信息和资源变更信息。
示例性地，所述虚拟化网元的生命周期变更信息，包括：需实例化的虚拟化网元的属性信息。
可选地，所述获取单元702，配置为：
根据所述需实例化的虚拟化网元的属性信息判断并确定所述需实例化的虚拟化网元对应的需实例化的适配组件；其中，所述需实例化的虚拟化网元的属性信息包括：虚拟化网元名称，虚拟化网元类型，虚拟化网元版本。
可选地，所述发送单元703，配置为：
当所述需实例化的适配组件未运行时，向所述VNFM发送适配组件实例化请求；其中，所述适配组件实例化请求包括：所述需实例化的适配组件类型和适配蓝图标识；所述适配蓝图标识用于所述VNFM根据所述适配蓝图标识获取所述需实例化的适配组件蓝图，并根据所述需实例化的适配组件蓝图计算所述需实例化的适配组件运行时所需的资源。
可选地，所述接收单元701，配置为从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的 资源；
所述发送单元703，配置为根据所述VNFM的申请信息向VNFM发送资源授权信息；其中，所述资源授权信息用于指示VNFM向虚拟化基础设备管理系统VIM请求分配所述需实例化的适配组件运行时所需的资源；
所述接收单元701，配置为接收所述VNFM发送的资源分配结果；以及，
接收所述VNFM发送的所述需实例化的适配组件对应实例化完成通知。
示例性地，所述虚拟化网元的生命周期变更信息包括：终止的虚拟化网元的属性信息；其中，终止的虚拟化网元的属性信息包括所述终止的虚拟化网元的名称、网元类型、网元版本及网元实例号中的一个或多个。
可选地，所述获取单元702，配置为：
根据所述终止的虚拟化网元的属性信息获取所述终止的虚拟化网元对应的需终止的适配组件。
可选地，所述发送单元703，配置为：
确定所述需终止的适配组件的运行状态；
当所述需终止的适配组件正在运行时，确定所述需终止的适配组件对应的实例号以及所述终止的虚拟化网元类型相同的网元是否处于运行状态；
当所述终止的虚拟化网元类型相同的网元没有处于运行状态时，向所述VNFM发送适配组件终止请求；其中，所述适配组件终止请求包括所述需终止的适配组件的实例号。
可选地，所述接收单元701，配置为接收所述VNFM终止所述需终止的适配组件之后所发送的针对所述需终止的适配组件的终止完成通知；以及，
接收所述VNFM在所述需终止的适配组件的资源释放完成之后，所发送的资源释放通知。
示例性地，所述虚拟化网元的生命周期变更信息包括：升级前的虚拟化网元属性信息和升级后的虚拟化网元属性信息。
可选地，所述获取单元702，配置为：
根据所述升级后的虚拟化网元的属性信息确定所述升级后的虚拟化网元对应的需实例化的适配组件。
可选地，所述发送单元703，配置为：
当所述升级后的虚拟化网元对应的需实例化的适配组件未运行时，向所述VNFM发送针对所述升级后的虚拟化网元对应的需实例化的适配组件的实例化请求；其中，所述升级后的虚拟化网元对应的需实例化的适配组件实例化请求包括：所述升级后的虚拟化网元对应的需实例化的适配组件类型和适配蓝图标识；所述适配蓝图标识用于所述VNFM根据所述适配蓝图标识获取所述升级后的虚拟化网元对应的需实例化的适配组件蓝图，并根据所述升级后的虚拟化网元对应的需实例化的适配组件蓝图计算所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源。
可选地，所述接收单元701，配置为从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的资源；
所述发送单元703，配置为根据所述资源申请请求向所述VNFM发送资源授权信息；所述资源授权信息用于指示所述VNFM向VIM请求分配所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源；
所述接收单元701，配置为接收所述VNFM发送的资源分配结果；
以及，接收所述VNFM发送的所述升级后的虚拟化网元对应的需实例化的适配组件对应实例化完成通知。
可选地，所述获取单元702，配置为：
根据所述升级前的虚拟化网元的属性信息获取所述升级前的虚拟化网元对应的适配组件。
可选地，所述发送单元703，配置为：
确定所述升级前的虚拟化网元对应的适配组件的运行状态；
当所述升级前的虚拟化网元对应的适配组件正在运行时，获取所述升级前的虚拟化网元对应的适配组件对应的实例号；
当确定没有与所述升级前的虚拟化网元类型相同的网元处于运行状态时，向所述VNFM发送适配组件终止请求；其中，所述适配组件终止请求包括所述升级前的虚拟化网元对应的适配组件的实例号。
可选地，所述接收单元701，配置为接收所述VNFM终止所述升级前的虚拟化网元对应的适配组件之后所发送的针对所述升级前的虚拟化网元对应的适配组件的终止完成通知；以及，
接收所述VNFM在所述升级前的虚拟化网元对应的适配组件的资源释放完成之后，所发送的资源释放通知。
示例性地，所述接收单元701，还配置为接收更新请求；其中，所述更新请求包括待更新的操作维护包标识、待更新的操作维护包的文件路径以及更新信息说明；
参见图8，所述装置70还包括保存单元704，配置为根据所述待更新的操作维护包标识确定所述待更新的操作维护包入库之后，将所述待更新的操作维护包中的蓝图文件保存至蓝图目录Catalog，并根据所述操作维护包的文件路径将软件镜像包保存至软件仓库；
所述获取单元702，还配置为所述更新信息说明中包括有新增网元类型的支持指示信息时，根据操作维护包标识获取Catalog中的蓝图文件；
参见图8，所述装置70还包括更新单元705，配置为将所述蓝图文件 中网元属性和适配组件的映射表更新至本地。
需要说明的是，本实施例中所涉及到的装置70应用于NFVO，因此，装置70中的功能单元，可以通过实施例二中NFVO中的具体功能模块来实现，因此，本实施例中所涉及到的功能单元在实现实施例二的各具体实施例的过程中，可以对应于实施例二中的具体功能模块，本申请对此不再赘述。
实施例四
参见图9，其示出了本发明实施例提供的一种虚拟化网元的管理设备90，可以包括：通信接口901、存储器902、处理器903和总线904；其中，
所述总线904配置为连接所述通信接口901、所述处理器903和所述存储器902以及这些器件之间的相互通信；
所述通信接口901，配置为与外部网元进行数据传输；
所述存储器902，配置为存储指令和数据；
所述处理器903执行所述指令用于：指示所述通信接口901接收待传输业务对应的业务描述信息；
以及，根据预设的配置策略和所述待传输业务对应的业务描述信息生成所述待传输业务对应的无线资源配置信息；
以及，根据所述无线资源配置信息进行无线资源配置；
以及，指示所述通信接口901将所述无线资源配置信息发送至终端。
在实际应用中，上述存储器902可以是易失性存储器(volatile memory)，例如随机存取存储器(RAM，Random-Access Memory)；或者非易失性存储器(non-volatile memory)，例如只读存储器(ROM，Read-Only Memory)，快闪存储器(flash memory)，硬盘(HDD，Hard Disk Drive)或固态硬盘(SSD，Solid-State Drive)；或者上述种类的存储器的组合，并向处理器903提供指令和数据。
上述处理器903可以为特定用途集成电路(ASIC，Application Specific Integrated Circuit)、数字信号处理器(DSP，Digital Signal Processor)、数字信号处理装置(DSPD，Digital Signal Processing Device)、可编程逻辑装置(PLD，Programmable Logic Device)、现场可编程门阵列(FPGA，Field Programmable Gate Array)、中央处理器(CPU，Central Processing Unit)、控制器、微控制器、微处理器中的至少一种。可以理解地，对于不同的设备，用于实现上述处理器功能的电子器件还可以为其它，本发明实施例不作具体限定。
本发明实施例提供一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令可为计算机程序、应用软件或者可编译代码等；所述计算机可执行指令被执行后，能够实现前述一个或多个技术方案提供的虚拟化网元的管理方法，例如，如图2至图6中一个或多个所示的方法。
所述计算机存储介质可为非瞬间存储介质。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现 在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。
工业实用性
本发明实施例提供的技术方案中，会根据虚拟化网元的虚拟化网元的生命周期变更信息，向该虚拟化网元向VNFM发送针对该虚拟化网元使用的适配组件的操作请求，如此，在一个虚拟化网元结束或升级时，对应的终止适配组件的运行，相当于利用虚拟化网元的生命周期信息对其使用的适配组件进行了生命周期的管理，减少了不需再使用的无用适配组件的运行，降低了这一部分适配组件占用的系统资源，从而减少系统资源开销，减少了无用适配组件消耗系统资源导致的速度慢的现象，提升了系统运行速度，从而具有积极的工业效果，并且实现简便，具有可实现性强的特点。

Claims (35)

  1. 一种虚拟化网元的管理方法，所述方法包括：
    接收由虚拟化的网络功能管理器VNFM发送的针对虚拟化网元的生命周期变更信息；
    判断并确定所述虚拟化网元对应的适配组件；
    根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对所述适配组件的操作请求；
    从所述VNFM获取所述适配组件的生命周期变更信息和资源变更信息。
  2. 根据权利要求1所述的方法，其中，所述虚拟化网元的生命周期变更信息，包括：需实例化的虚拟化网元的属性信息。
  3. 根据权利要求2所述的方法，其中，所述判断并确定所述虚拟化网元对应的适配组件，可包括：
    根据所述需实例化的虚拟化网元的属性信息判断并确定所述需实例化的虚拟化网元对应的需实例化的适配组件；其中，所述需实例化的虚拟化网元的属性信息包括：虚拟化网元名称、虚拟化网元类型及虚拟化网元版本的至少其中之一。
  4. 根据权利要求3所述的方法，其中，所述根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对所述适配组件的操作请求，包括：
    当所述需实例化的适配组件未运行时，向所述VNFM发送适配组件实例化请求；其中，所述适配组件实例化请求包括：所述需实例化的适配组件类型和适配蓝图标识；所述适配蓝图标识用于所述VNFM根据所述适配蓝图标识获取需实例化的适配组件蓝图，并根据所述需实例化的适配组件蓝图计算所述需实例化的适配组件运行时所需的资源。
  5. 根据权利要求4所述的方法，其中，所述从所述VNFM获取所述适 配组件的生命周期变更信息和资源变更信息，包括：
    从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的资源；
    根据所述资源申请请求向VNFM发送资源授权信息；其中，所述资源授权信息用于指示VNFM向虚拟化基础设备管理系统VIM请求分配所述需实例化的适配组件运行时所需的资源；
    接收所述VNFM发送的资源分配结果；
    接收所述VNFM发送的所述需实例化的适配组件对应实例化完成通知。
  6. 根据权利要求1所述的方法，其中，所述虚拟化网元的生命周期变更信息包括：终止的虚拟化网元的属性信息；其中，终止的虚拟化网元的属性信息包括所述终止的虚拟化网元的名称、网元类型、网元版本、网元实例号。
  7. 根据权利要求6所述的方法，其中，所述判断并确定所述虚拟化网元对应的适配组件，可包括：
    根据所述终止的虚拟化网元的属性信息获取所述终止的虚拟化网元对应的需终止的适配组件。
  8. 根据权利要求7所述的方法，其中，所述根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对适配组件的操作请求，可包括：
    确定所述需终止的适配组件的运行状态；
    当所述需终止的适配组件正在运行时，确定所述需终止的适配组件对应的实例号以及所述终止的虚拟化网元类型相同的网元是否处于运行状态；
    当所述终止的虚拟化网元类型相同的网元没有处于运行状态时，向所述VNFM发送适配组件终止请求；其中，所述适配组件终止请求包括所述 需终止的适配组件的实例号。
  9. 根据权利要求8所述的方法，其中，所述从所述VNFM获取适配组件的生命周期变更信息和资源变更信息，可包括：
    接收所述VNFM终止所述需终止的适配组件之后所发送的针对所述需终止的适配组件的终止完成通知；
    接收所述VNFM在所述需终止的适配组件的资源释放完成之后，所发送的资源释放通知。
  10. 根据权利要求1所述的方法，其中，所述虚拟化网元的生命周期变更信息包括：升级前的虚拟化网元属性信息和升级后的虚拟化网元属性信息。
  11. 根据权利要求10所述的方法，其中，所述判断并确定所述虚拟化网元对应的适配组件，可包括：
    根据所述升级后的虚拟化网元的属性信息确定所述升级后的虚拟化网元对应的需实例化的适配组件。
  12. 根据权利要求11所述的方法，其中，所述根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对适配组件的操作请求，可包括：
    当所述升级后的虚拟化网元对应的需实例化的适配组件未运行时，向所述VNFM发送针对所述升级后的虚拟化网元对应的需实例化的适配组件的实例化请求；其中，所述升级后的虚拟化网元对应的需实例化的适配组件实例化请求包括：所述升级后的虚拟化网元对应的需实例化的适配组件类型和适配蓝图标识；所述适配蓝图标识用于所述VNFM根据所述适配蓝图标识获取所述升级后的虚拟化网元对应的需实例化的适配组件蓝图，并根据所述升级后的虚拟化网元对应的需实例化的适配组件蓝图计算所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源。
  13. 根据权利要求12所述的方法，其中，所述从所述VNFM获取适配 组件的生命周期变更信息和资源变更信息，可包括：
    从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的资源；
    根据所述资源申请请求向所述VNFM发送资源授权信息；所述资源授权信息用于指示所述VNFM向VIM请求分配所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源；
    以及，接收所述VNFM发送的资源分配结果；
    以及，接收所述VNFM发送的所述升级后的虚拟化网元对应的需实例化的适配组件对应实例化完成通知。
  14. 根据权利要求10所述的方法，其中，所述判断并确定所述虚拟化网元对应的适配组件，可包括：
    根据所述升级前的虚拟化网元的属性信息获取所述升级前的虚拟化网元对应的适配组件。
  15. 根据权利要求14所述的方法，其中，所述根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对适配组件的操作请求，可包括：
    确定所述升级前的虚拟化网元对应的适配组件的运行状态；
    当所述升级前的虚拟化网元对应的适配组件正在运行时，获取所述升级前的虚拟化网元对应的适配组件对应的实例号；
    当确定没有与所述升级前的虚拟化网元类型相同的网元处于运行状态时，向所述VNFM发送适配组件终止请求；其中，所述适配组件终止请求包括所述升级前的虚拟化网元对应的适配组件的实例号。
  16. 根据权利要求15所述的方法，其中，所述从所述VNFM获取适配组件的生命周期变更信息和资源变更信息，可包括：
    接收所述VNFM终止所述升级前的虚拟化网元对应的适配组件之后所发送的针对所述升级前的虚拟化网元对应的适配组件的终止完成通知；
    接收所述VNFM在所述升级前的虚拟化网元对应的适配组件的资源释放完成之后，所发送的资源释放通知。
  17. 根据权利要求1至16任一项所述的方法，其中，所述方法还包括：
    接收更新请求；其中，所述更新请求包括待更新的操作维护包标识、待更新的操作维护包的文件路径以及更新信息说明；
    根据所述待更新的操作维护包标识确定所述待更新的操作维护包入库之后，将所述待更新的操作维护包中的蓝图文件保存至蓝图目录Catalog，并根据所述操作维护包的文件路径将软件镜像包保存至软件仓库；
    所述更新信息说明中包括有新增网元类型的支持指示信息时，根据操作维护包标识获取Catalog中的蓝图文件；
    将所述蓝图文件中网元属性和适配组件的映射表更新至本地。
  18. 一种虚拟化网元的管理装置，所述装置包括：接收单元、获取单元、发送单元；其中，
    所述接收单元，配置为接收由虚拟化的网络功能管理器VNFM发送的针对虚拟化网元的生命周期变更信息；
    所述获取单元，配置为判断并确定所述虚拟化网元对应的适配组件；
    所述发送单元，配置为根据所述虚拟化网元的生命周期变更信息向所述VNFM发送针对所述适配组件的操作请求；
    所述接收单元，配置为从所述VNFM获取所述适配组件的生命周期变更信息和资源变更信息。
  19. 根据权利要求18所述的装置，其中，所述虚拟化网元的生命周期变更信息，包括：需实例化的虚拟化网元的属性信息。
  20. 根据权利要求19所述的装置，其中，所述获取单元，配置为：
    根据所述需实例化的虚拟化网元的属性信息判断并确定所述需实例化的虚拟化网元对应的需实例化的适配组件；其中，所述需实例化的虚拟化 网元的属性信息包括：虚拟化网元名称、虚拟化网元类型及虚拟化网元版本的至少其中之一。
  21. 根据权利要求20所述的装置，其中，所述发送单元，配置为：
    当所述需实例化的适配组件未运行时，向所述VNFM发送适配组件实例化请求；其中，所述适配组件实例化请求包括：所述需实例化的适配组件类型和适配蓝图标识；所述适配蓝图标识用于所述VNFM根据所述适配蓝图标识获取所述需实例化的适配组件蓝图，并根据所述需实例化的适配组件蓝图计算所述需实例化的适配组件运行时所需的资源。
  22. 根据权利要求21所述的装置，其中，
    所述接收单元，配置为从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的资源；
    所述发送单元，配置为根据所述VNFM的申请信息向VNFM发送资源授权信息；其中，所述资源授权信息用于指示VNFM向虚拟化基础设备管理系统VIM请求分配所述需实例化的适配组件运行时所需的资源；
    所述接收单元，配置为接收所述VNFM发送的资源分配结果；以及，
    接收所述VNFM发送的所述需实例化的适配组件对应实例化完成通知。
  23. 根据权利要求18所述的装置，其中，所述虚拟化网元的生命周期变更信息包括：终止的虚拟化网元的属性信息；其中，终止的虚拟化网元的属性信息包括所述终止的虚拟化网元的名称、网元类型、网元版本、网元实例号。
  24. 根据权利要求23所述的装置，其中，所述获取单元，配置为：
    根据所述终止的虚拟化网元的属性信息获取所述终止的虚拟化网元对应的需终止的适配组件。
  25. 根据权利要求24所述的装置，其中，所述发送单元，配置为：
    确定所述需终止的适配组件的运行状态；
    当所述需终止的适配组件正在运行时，确定所述需终止的适配组件对应的实例号以及所述终止的虚拟化网元类型相同的网元是否处于运行状态；
    当所述终止的虚拟化网元类型相同的网元没有处于运行状态时，向所述VNFM发送适配组件终止请求；其中，所述适配组件终止请求包括所述需终止的适配组件的实例号。
  26. 根据权利要求25所述的装置，其中，所述接收单元，配置为接收所述VNFM终止所述需终止的适配组件之后所发送的针对所述需终止的适配组件的终止完成通知；以及，
    接收所述VNFM在所述需终止的适配组件的资源释放完成之后，所发送的资源释放通知。
  27. 根据权利要求18所述的装置，其中，所述虚拟化网元的生命周期变更信息包括：升级前的虚拟化网元属性信息和升级后的虚拟化网元属性信息。
  28. 根据权利要求27所述的装置，其中，所述获取单元，配置为：
    根据所述升级后的虚拟化网元的属性信息确定所述升级后的虚拟化网元对应的需实例化的适配组件。
  29. 根据权利要求28所述的装置，其中，所述发送单元，配置为：
    当所述升级后的虚拟化网元对应的需实例化的适配组件未运行时，向所述VNFM发送针对所述升级后的虚拟化网元对应的需实例化的适配组件的实例化请求；其中，所述升级后的虚拟化网元对应的需实例化的适配组件实例化请求包括：所述升级后的虚拟化网元对应的需实例化的适配组件类型和适配蓝图标识；所述适配蓝图标识用于所述VNFM根据所述适配蓝图标识获取所述升级后的虚拟化网元对应的需实例化的适配组件蓝图，并 根据所述升级后的虚拟化网元对应的需实例化的适配组件蓝图计算所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源。
  30. 根据权利要求29所述的装置，其中，
    所述接收单元，配置为从所述VNFM接收资源申请请求；其中，所述资源申请请求用于请求所述需实例化的适配组件运行时所需的资源；
    所述发送单元，配置为根据所述资源申请请求向所述VNFM发送资源授权信息；所述资源授权信息用于指示所述VNFM向VIM请求分配所述升级后的虚拟化网元对应的需实例化的适配组件运行时所需的资源；
    所述接收单元，配置为接收所述VNFM发送的资源分配结果；
    以及，接收所述VNFM发送的所述升级后的虚拟化网元对应的需实例化的适配组件对应实例化完成通知。
  31. 根据权利要求27所述的装置，其中，所述获取单元，配置为：
    根据所述升级前的虚拟化网元的属性信息获取所述升级前的虚拟化网元对应的适配组件。
  32. 根据权利要求31所述的装置，其中，所述发送单元，配置为：
    确定所述升级前的虚拟化网元对应的适配组件的运行状态；
    当所述升级前的虚拟化网元对应的适配组件正在运行时，获取所述升级前的虚拟化网元对应的适配组件对应的实例号；
    当确定没有与所述升级前的虚拟化网元类型相同的网元处于运行状态时，向所述VNFM发送适配组件终止请求；其中，所述适配组件终止请求包括所述升级前的虚拟化网元对应的适配组件的实例号。
  33. 根据权利要求32所述的装置，其中，所述接收单元，配置为接收所述VNFM终止所述升级前的虚拟化网元对应的适配组件之后所发送的针对所述升级前的虚拟化网元对应的适配组件的终止完成通知；以及，
    接收所述VNFM在所述升级前的虚拟化网元对应的适配组件的资源释 放完成之后，所发送的资源释放通知。
  34. 根据权利要求18至33任一项所述的装置，其中，所述接收单元，还配置为接收更新请求；其中，所述更新请求包括待更新的操作维护包标识、待更新的操作维护包的文件路径以及更新信息说明；
    所述装置还包括保存单元，配置为根据所述待更新的操作维护包标识确定所述待更新的操作维护包入库之后，将所述待更新的操作维护包中的蓝图文件保存至蓝图目录Catalog，并根据所述操作维护包的文件路径将软件镜像包保存至软件仓库；
    所述获取单元，还配置为所述更新信息说明中包括有新增网元类型的支持指示信息时，根据操作维护包标识获取Catalog中的蓝图文件；
    所述装置还包括更新单元，配置为将所述蓝图文件中网元属性和适配组件的映射表更新至本地。
  35. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令；所述计算机可执行指令被执行后，能够实现权利要求1至17任一项提供的虚拟化网元的管理方法。
PCT/CN2017/116002 2016-12-19 2017-12-13 一种虚拟化网元的管理方法和装置及计算机存储介质 WO2018113571A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611182006.0 2016-12-19
CN201611182006.0A CN108207008A (zh) 2016-12-19 2016-12-19 一种虚拟化网元的管理方法和装置

Publications (1)

Publication Number Publication Date
WO2018113571A1 true WO2018113571A1 (zh) 2018-06-28

Family

ID=62603038

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/116002 WO2018113571A1 (zh) 2016-12-19 2017-12-13 一种虚拟化网元的管理方法和装置及计算机存储介质

Country Status (2)

Country Link
CN (1) CN108207008A (zh)
WO (1) WO2018113571A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110943967A (zh) * 2018-09-21 2020-03-31 中兴通讯股份有限公司 一种认证方法、装置和系统
CN113726541A (zh) * 2020-05-25 2021-11-30 中移(苏州)软件技术有限公司 一种网元配置的方法、装置、电子设备和存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110716788B (zh) * 2018-07-13 2022-07-26 华为技术有限公司 管理虚拟化资源的方法和装置
CN110896407B (zh) * 2018-09-13 2023-03-10 亿阳信通股份有限公司 一种nfvo组件配置管理、请求转发方法和请求处理装置
CN111143023A (zh) * 2018-11-05 2020-05-12 中兴通讯股份有限公司 一种资源变更的方法及装置、设备、存储介质
CN111586081B (zh) * 2019-02-18 2022-01-11 宁波方太厨具有限公司 一种基于物模型的物联网实现方法
CN110086652B (zh) * 2019-03-25 2023-04-18 北京天地互连信息技术有限公司 一种针对5g核心网中服务网元的管理系统及其方法
CN112217654B (zh) * 2019-07-11 2022-06-07 华为技术有限公司 服务资源许可管理方法和相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103414589A (zh) * 2013-08-13 2013-11-27 华为技术有限公司 一种管理资源信息的方法及装置
CN105354076A (zh) * 2015-10-23 2016-02-24 深圳前海达闼云端智能科技有限公司 一种应用部署方法及装置
US20160057102A1 (en) * 2014-08-19 2016-02-25 Futurewei Technologies, Inc. Methods and System for Allocating an IP Address for an Instance in a Network Function Virtualization (NFV) system
CN105871570A (zh) * 2015-01-20 2016-08-17 中兴通讯股份有限公司 虚拟网络功能vnf的管理方法及装置
CN106209924A (zh) * 2015-04-29 2016-12-07 中国移动通信集团公司 部署虚拟网元的方法、装置及网络功能虚拟化调度服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3101846A4 (en) * 2014-01-29 2016-12-21 Huawei Tech Co Ltd WIRELESS COMMUNICATION NETWORK AND DEVICE
CN104253866B (zh) * 2014-09-20 2018-03-27 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备
CN105934919B (zh) * 2014-12-17 2019-03-19 华为技术有限公司 网络服务能力自动调整方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103414589A (zh) * 2013-08-13 2013-11-27 华为技术有限公司 一种管理资源信息的方法及装置
US20160057102A1 (en) * 2014-08-19 2016-02-25 Futurewei Technologies, Inc. Methods and System for Allocating an IP Address for an Instance in a Network Function Virtualization (NFV) system
CN105871570A (zh) * 2015-01-20 2016-08-17 中兴通讯股份有限公司 虚拟网络功能vnf的管理方法及装置
CN106209924A (zh) * 2015-04-29 2016-12-07 中国移动通信集团公司 部署虚拟网元的方法、装置及网络功能虚拟化调度服务器
CN105354076A (zh) * 2015-10-23 2016-02-24 深圳前海达闼云端智能科技有限公司 一种应用部署方法及装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110943967A (zh) * 2018-09-21 2020-03-31 中兴通讯股份有限公司 一种认证方法、装置和系统
CN113726541A (zh) * 2020-05-25 2021-11-30 中移(苏州)软件技术有限公司 一种网元配置的方法、装置、电子设备和存储介质
CN113726541B (zh) * 2020-05-25 2023-11-07 中移(苏州)软件技术有限公司 一种网元配置的方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN108207008A (zh) 2018-06-26

Similar Documents

Publication Publication Date Title
WO2018113571A1 (zh) 一种虚拟化网元的管理方法和装置及计算机存储介质
US10496503B2 (en) Healing cloud services during upgrades
JP6677294B2 (ja) ネットワークシステム、パッチファイル適用方法、及びプログラム
US10599457B2 (en) Importing and exporting virtual disk images
EP3839726B1 (en) Software modification initiation method and apparatus
US11914881B2 (en) Data migration method and apparatus
US10922123B2 (en) Container migration in computing systems
CN108028827B (zh) 网络功能虚拟化架构中证书的管理方法及装置
EP3879752A1 (en) Data processing method and apparatus, and server
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
WO2018192478A1 (zh) 云管理平台、虚拟机管理方法及其系统
US11343141B2 (en) Methods and apparatus to migrate physical server hosts between virtual standard switches and virtual distributed switches in a network
CN108073423B (zh) 一种加速器加载方法、系统和加速器加载装置
US20180307498A1 (en) Driver Loading Method and Server
JP2012078893A (ja) 計算機システム、及び管理計算機
JP2019101866A (ja) アプリケーションの更新方法およびプログラム
US11671379B1 (en) System and method for subscription management using dynamically composed management entities
US20230221997A1 (en) System and method for subscription management using composed systems
CN108062239B (zh) 一种加速器加载方法、系统和加速器加载装置
JP2021184235A5 (zh)
JP2016181091A (ja) 情報管理装置、情報管理方法、情報管理プログラム、データ構造、及び、ソフトウェア資産管理システム
CN117631994A (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: 17884487

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17884487

Country of ref document: EP

Kind code of ref document: A1