WO2016115896A1 - 虚拟网络功能vnf的管理方法及装置 - Google Patents

虚拟网络功能vnf的管理方法及装置 Download PDF

Info

Publication number
WO2016115896A1
WO2016115896A1 PCT/CN2015/087708 CN2015087708W WO2016115896A1 WO 2016115896 A1 WO2016115896 A1 WO 2016115896A1 CN 2015087708 W CN2015087708 W CN 2015087708W WO 2016115896 A1 WO2016115896 A1 WO 2016115896A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual machine
vnf
virtual
management
entity
Prior art date
Application number
PCT/CN2015/087708
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 WO2016115896A1 publication Critical patent/WO2016115896A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks

Definitions

  • the present invention relates to the field of communications, and in particular, to a management method and apparatus for a virtualized network function (VNF).
  • VNF virtualized network function
  • network functions and network devices are super-coupling relationships, and network functions are implemented through specially designed, vendor-specific devices.
  • the existing network function will be implemented on the VNF, which can be regarded as the application layer of the VNF.
  • Each VNF can implement different network functions according to the specific application configuration. Because the VNF usually contains multiple VNF components (VNF Component), the VNFC is generally implemented by a virtual machine, and the VNFC and the virtual machine usually have a one-to-one correspondence, so each VNF will be composed of multiple virtual machines, and each virtual machine is implemented. The functions and virtual resources that can be used may be different. At the same time, because the VNF can expand and shrink during its life cycle, the number of virtual machines included in the VNF and the virtual resources that the virtual machine can use may be in the process of running the network.
  • the Network Management System (NMS, also referred to as NM) needs to be obtained. relevant information.
  • the network elements managed by the NMS through the Element Management System (EMS, also referred to as EM) are physical machines. There are no virtual machines and virtual resources. The operators pass the NMS. This information is not available to the northbound interface between the EMS and the EMS.
  • an embodiment of the present invention provides a VNF management method and apparatus.
  • a VNF management method including: network element management (Element Management, abbreviated as EM) acquiring information about a virtual machine under the VNF entity from the VNF entity; the EM establishing, for each virtual machine, a virtual machine object instance corresponding to the virtual machine according to the related information; The virtual machine object instance is managed.
  • Network element management Element Management, abbreviated as EM
  • EM Network element management
  • the related information of the virtual machine includes at least one of the following: a virtual machine identifier, a number of CPUs in the virtual machine, a memory capacity of the virtual machine, a storage capacity of the virtual machine, and a location of the virtual machine. , VNFC information.
  • the object instance representing the virtual machine and the VNFC are in a one-to-one or one-to-many relationship.
  • the method further includes: the EM establishing an instance of a management function object corresponding to the VNF entity, wherein the management function object instance name includes (name-contained): one or more virtual Machine object instance.
  • the management function object instance includes: an identifier used to represent the VNF entity.
  • the method further includes: the EM receiving a request message from a network management (NM) entity and/or an operation support system (OSS), where The request message is used to request, by the EM, related information of the virtual machine under the VNF; the EM sends an instance of a management function object corresponding to the VNF and a virtual machine object instance included in the management function object instance To the NM and/or OSS.
  • NM network management
  • OSS operation support system
  • the EM manages the virtual machine object instance, including: the EM receiving first change notification information from the VNF; and triggering, by the first change information, the EM acquisition The related information of the virtual machine under the current VNF entity; the EM compares the currently acquired related information with the related information locally saved by the EM; and the EM determines, according to the comparison result, that the VNF increases or decreases virtual machine.
  • the EM determines, according to the comparison result, that the VNF increases or decreases the virtual machine, including: indicating, in the comparison result, that the currently acquired related information is more than the EM locally saved
  • the EM determines that the VNF increases the virtual machine
  • the comparison result indicates that the currently acquired related information is smaller than the related information locally saved by the EM
  • the EM determines the VNF Reduce virtual machines.
  • the method further includes: when the EM is added according to the comparison result, the EM is an added virtual machine. Establishing a virtual machine object instance corresponding to the added virtual machine; when determining that the EM deletes the virtual machine according to the comparison result, the EM deletes the virtual machine object instance corresponding to the deleted virtual machine.
  • the EM manages the virtual machine object instance, including: the EM receives second change notification information from the VNF; and the EM is triggered by the second change notification information, Update the properties of the virtual machine object instance corresponding to the virtual machine.
  • the EM receives the second change notification information of the virtual machine related information from the VNF in at least one of the following situations: after the capacity of the VNF entity changes, the EM restarts.
  • a method for managing a virtual network function VNF comprising: a network management NM entity sending a request message to a network element management EM entity, wherein the request message is used for the EM And requesting, by the NM entity, the management function object instance corresponding to the VNF returned by the EM entity according to the request message, and the virtual machine included in the management function object instance.
  • a network management NM entity sending a request message to a network element management EM entity, wherein the request message is used for the EM
  • the management function object instance corresponding to the VNF returned by the EM entity according to the request message, and the virtual machine included in the management function object instance.
  • the related information of the virtual machine includes at least one of the following: a virtual machine identifier, a number of CPUs in the virtual machine, a memory capacity of the virtual machine, a storage capacity of the virtual machine, and a location of the virtual machine. , VNFC information.
  • a management device for a virtual network function VNF is further provided, which is applied to the network element management EM, and includes: an obtaining module, configured to acquire, from the VNF entity, related information of the virtual machine under the VNF entity; And establishing a module, where the related information is used to establish an instance of the virtual machine object corresponding to the virtual machine for each of the virtual machines; and the management module is configured to manage the virtual machine object instance.
  • the information about the virtual machine acquired by the acquiring module includes at least one of the following: a virtual machine identifier, a number of CPUs in a virtual machine, a memory capacity of a virtual machine, and a storage of a virtual machine. Capacity, location of the virtual machine, VNFC information.
  • the management module includes: an establishing unit, configured to establish an instance of a management function object corresponding to the VNF entity, where the management function object instance name includes: one or more virtual machine objects Example.
  • a management apparatus for a virtual network function VNF which is applied to a network management NM entity, and includes: a sending module, configured to send a request message to a network element management EM entity, where The request message is used to request the EM to request related information of the virtual machine under the VNF entity, and the receiving module is configured to receive an instance of the management function object corresponding to the VNF returned by the EM entity according to the request message, and An instance of a virtual machine object contained in an instance of a management function object.
  • the information about the virtual machine requested by the sending module includes: a virtual machine identifier, a number of CPUs in a virtual machine, a memory capacity of a virtual machine, a storage capacity of a virtual machine, and a virtual machine. Location, VNFC information.
  • a virtual machine object instance corresponding to the virtual machine is established according to the related information of the virtual machine, and the virtual machine object instance is managed to implement the technical solution for managing the virtual machine, and the related art is solved.
  • the problem that the EM can not manage the virtual machine and the virtual resource can not be known about the current virtual machine and the operation status of the virtual resource, so that the operator can obtain the virtual resource status of the current virtual machine and expand the application scope of the virtual network function.
  • FIG. 1 is a flowchart of a method for managing a VNF according to an embodiment of the present invention
  • FIG. 2 is a diagram showing an object relationship between a virtual network function and a virtual machine according to an embodiment of the present invention
  • FIG. 3 is a flowchart of managing virtual machine information of a VNF according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of a management apparatus of a VNF according to an embodiment of the present invention.
  • FIG. 5 is a block diagram showing still another structure of a VNF management apparatus according to an embodiment of the present invention.
  • FIG. 6 is another flowchart of a method for managing a VNF according to an embodiment of the present invention.
  • FIG. 7 is still another structural block diagram of a VNF management apparatus according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of acquiring NNF/OSS VNF virtual machine information after VNF instantiation is completed according to an embodiment of the present invention
  • FIG. 9 is a flowchart of acquiring virtual machine information by an NM/OSS after an EM restart according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of acquiring virtual machine information by a NM/OSS after VNF expansion according to an embodiment of the present invention
  • FIG. 11 is a flowchart of acquiring virtual machine information by a NM/OSS after VNF shrinking according to an embodiment of the present invention
  • FIG. 12 is a flowchart of acquiring virtual machine information by the NM/OS after the VNF capacity is increased or decreased according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a VNF management method according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps:
  • Step S102 The network element management EM acquires related information of the virtual machine under the VNF entity from the VNF entity.
  • Step S104 the EM establishes, according to the related information, a virtual machine object instance corresponding to the virtual machine for each of the virtual machines;
  • Step S106 the EM manages the virtual machine object instance.
  • the virtual machine object instance corresponding to the virtual machine is established according to the related information of the virtual machine, and the virtual machine object instance (the virtual machine object example mentioned in the embodiment of the present invention can be understood as representing the virtual
  • the object instance of the machine is managed to implement the technical solution for managing the virtual machine, and solves the problem that the EM cannot manage the virtual machine and the virtual resource due to the fact that the EM cannot manage the current virtual machine and the virtual resource.
  • the operator can obtain the virtual resources of the current virtual machine, and expand the application range of the virtual network function.
  • the related information of the virtual machine includes at least one of the following: a virtual machine identifier, a number of CPUs in the virtual machine, a memory capacity of the virtual machine, a storage capacity of the virtual machine, The location of the virtual machine and VNFC information.
  • the VNF since the virtual machine under the VNF entity has established a virtual machine object instance corresponding to the virtual machine one by one, the VNF also needs to establish an instance of the management function object corresponding thereto, and the management function object instance name includes And one or more virtual machine object instances, wherein the management function object instance includes an identifier for indicating the VNF entity, and as shown in FIG. 2, the management object indicating the virtual network function includes a management object representing the virtual machine, and the representation
  • the attributes of the management object of the virtual machine include the identifier of the virtual machine, the number of CPUs, the memory capacity, the storage capacity, the location of the virtual machine, and the identifier of the virtual network function in the management object attribute of the virtual network function.
  • the EM receives a request message from the network management NM entity and/or the operation support system OSS, where the request message is used to request the EM to request information about the virtual machine under the VNF; and the EM manages the VNF corresponding to the VNF.
  • the functional object instance and the virtual machine object instance included in the foregoing management function object instance are sent to the NM and/or the OSS, and the following technical solutions are described below with reference to an example:
  • FIG. 3 is a flowchart of managing virtual machine information of a VNF according to an embodiment of the present invention, including the following steps:
  • Step S300 the EM acquires virtual machine related information from the VNF.
  • Step S302 the VNF returns virtual machine related information
  • step S304 the management object instance corresponding to the virtual machine is created, updated, or deleted, that is, the EM establishes a corresponding management object instance for each virtual machine according to the obtained information, and of course, the management object instance of the virtual machine may be updated if necessary. Attributes, delete the management object instance corresponding to the virtual machine that does not exist, and add the object instance of the virtual machine corresponding to the virtual machine. For example, the following technical solutions can be implemented:
  • the EM receives the first change notification information from the VNF.
  • the EM obtains the related information of the virtual machine under the current VNF entity, and the EM compares the currently obtained related information with the EM local save. The above related information; the EM determines that the VNF increases or decreases the virtual machine according to the comparison result.
  • the EM determines that the VNF is increased or decreased according to the comparison result by using the following technical solution: when the comparison result indicates that the currently acquired related information is more than the related information stored locally by the EM, the EM determines the VNF. Adding a virtual machine; when the comparison result indicates that the currently acquired related information is smaller than the related information stored locally by the EM, the EM determines that the VNF reduces the virtual machine.
  • the method further includes: when determining that the EM adds a virtual machine according to the comparison result, the EM establishes a virtual virtual machine corresponding to the added virtual machine for the added virtual machine.
  • the machine object instance when determining that the EM deletes the virtual machine according to the comparison result, the EM deletes the virtual machine object instance corresponding to the deleted virtual machine.
  • the EM receives the second change notification information from the VNF.
  • the EM updates the attribute of the virtual machine object instance corresponding to the virtual machine under the trigger of the second change notification information. Specifically, the EM receives the VNF from the VNF in at least one of the following cases.
  • Second change notification information of the virtual machine related information After the capacity of the VNF entity changes, the EM restarts.
  • Step S306 acquiring VNF and virtual machine related information
  • Step S308 returning the VNF and the object instance information of each virtual machine.
  • a VNF management device is also provided, which is applied to the network element management EM for implementing the foregoing embodiments and preferred embodiments.
  • the descriptions of the foregoing embodiments are omitted, and the following is related to the device.
  • the module is explained.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • 4 is a structural block diagram of a VNF management apparatus according to an embodiment of the present invention, as shown in FIG. 4:
  • the obtaining module 40 is configured to acquire, from the VNF entity, related information of the virtual machine under the VNF entity;
  • the establishing module 42 is connected to the obtaining module 40, and is configured to establish the virtual machine object instance corresponding to the virtual machine for each of the virtual machines by using the related information.
  • the management module 44 is connected to the establishing module 42 and configured to manage the virtual machine object instance.
  • the virtual machine object instance corresponding to the virtual machine is established according to the relevant information of the virtual machine, and the virtual machine object instance is managed to realize the technical solution for managing the virtual machine, and the related technology is solved.
  • the EM still cannot manage the virtual machine and the virtual resource, and the problem that the current virtual machine and the virtual resource are running cannot be known, so that the operator can obtain the virtual resource of the current virtual machine and expand the application of the virtual network function. range.
  • the related information of the virtual machine acquired by the obtaining module 40 includes at least one of the following: a virtual machine identifier, a number of CPUs in the virtual machine, a memory capacity of the virtual machine, a storage capacity of the virtual machine, and a virtual machine. Location, VNFC information.
  • the management module 44 includes: an establishing unit 440, configured to establish a management function object instance corresponding to the VNF entity, where the management function object instance name includes One or more virtual machine object instances.
  • FIG. 6 is another flowchart of the VNF management method according to an embodiment of the present invention, as shown in FIG. Show, including the following steps:
  • Step S602 the network management NM entity sends a request message to the network element management EM entity, where the request message is Corresponding to requesting, by the foregoing EM, related information of the foregoing virtual machine under the VNF entity;
  • Step S604 the NM entity receives the management function object instance corresponding to the VNF returned by the EM entity according to the request message, and the virtual machine object instance included in the management function object instance.
  • the NM can, after sending the request information to the EM, the EM can establish a virtual machine object instance corresponding to the virtual machine according to the related information of the virtual machine, and return the management function object instance corresponding to the VNF according to the request message.
  • the technical solution of the virtual machine object instance included in the foregoing management function object instance solves the related art, the EM can not manage the virtual machine and the virtual resource, and cannot know the current virtual machine and the virtual resource running condition, and then the NM does not The problem of the virtual resource running status can be obtained according to the EM, so that the operator can obtain the virtual resource status of the current virtual machine, and expand the application range of the virtual network function.
  • the related information of the virtual machine includes at least one of the following: a virtual machine identifier, a number of CPUs in the virtual machine, a memory capacity of the virtual machine, a storage capacity of the virtual machine, a location of the virtual machine, and a VNFC. information.
  • the virtual machine object instance and the VNFC are in a one-to-one or one-to-many relationship.
  • FIG. 7 is a structural block diagram of a VNF management apparatus according to an embodiment of the present invention, as shown in FIG.
  • the sending module 70 is configured to send a request message to the network element management EM entity, where the request message is used to request, by the EM, the related information of the virtual machine under the VNF entity;
  • the receiving module 72 is connected to the sending module 70, and is configured to receive the management function object instance corresponding to the VNF returned by the EM entity according to the request message and the virtual machine object instance included in the management function object instance.
  • the NM can establish a virtual machine object instance corresponding to the virtual machine according to the related information of the virtual machine after the request information is sent to the EM, and the management corresponding to the VNF returned according to the request message.
  • the technical solution of the functional object instance and the virtual machine object instance included in the foregoing management function object instance solves the related art, and the EM cannot manage the virtual machine and the virtual resource, and cannot know the current virtual machine and the virtual resource operation, and further The NM cannot obtain the problem of the virtual resource running according to the EM, so that the operator can obtain the virtual resource status of the current virtual machine and expand the application scope of the virtual network function.
  • the information about the virtual machine requested by the sending module 70 includes: the identifier of the virtual machine, the number of CPUs in the virtual machine, the memory capacity of the virtual machine, the storage capacity of the virtual machine, the location of the virtual machine, and the VNFC information. .
  • Preferred Embodiment 1 After the VNF instantiation is completed, the EM needs to model all the virtual machines of the VNF, as shown in FIG. 8:
  • Step S800 After the VNF instantiation is completed, the VNF establishes a link with the EM;
  • Step S802 The EM obtains all virtual machine related information of the VNF from the VNF, where the related information of each virtual machine includes the virtual machine identifier, the number of CPUs, the memory capacity, the storage capacity, the location of the virtual machine, and for each virtual
  • the machine establishes a corresponding instance of the VirtualMachine object to represent each virtual machine, indicating that the VNF's ManagedFunction object instance contains all the VirtualMachine object instances, and the ManagedFunction object has the VNF identifier.
  • Step S804 The NM/OSS sends a message for obtaining the VNF and its virtual machine information to the EM;
  • Step S806 The EM sends an instance of the ManagedFunction object representing the VNF and all the information of the VirtualMachine object instance representing the virtual machine it contains to the NM/OSS.
  • Preferred Embodiment 2 After the VNF is extended, the EM needs to model the newly added virtual machine, as shown in FIG. 9:
  • Step S900 The Scale out operation of the VNF is completed, and the VNF sends a virtual machine information change notification to the EM;
  • Step S902 The EM obtains, according to the notification information, related information of all the virtual machines of the VNF from the VNF, where the related information of each virtual machine includes the virtual machine identifier, the number of CPUs, the memory capacity, the storage capacity, the location of the virtual machine, and Create a corresponding VirtualMachine object instance for the newly added virtual machine to represent the virtual machine.
  • the VirtualMachine object instance is represented by the VNF's ManagedFunction object instance, and the ManagedFunction object has the VNF identifier.
  • Step S904 The NM/OSS sends a message for obtaining the VNF and its virtual machine information to the EM;
  • Step S906 The EM sends an instance of the ManagedFunction object representing the VNF and all the information of the VirtualMachine object instance representing the virtual machine to the NM/OSS;
  • Preferred Embodiment 3 After the VNF shrinks, the EM should delete the object instance corresponding to the reduced virtual machine, as shown in FIG. 10:
  • Step S100 After the Scale in operation of the VNF is completed, the VNF sends a virtual machine information change notification to the EM.
  • Step S102 The EM obtains related information of all the virtual machines of the VNF from the VNF according to the notification information, and deletes the VirtualMachine object instance corresponding to the virtual machine that does not exist.
  • Step S104 The NM/OSS sends a message for obtaining the VNF and its virtual machine information to the EM;
  • Step S106 The EM sends an instance of the ManagedFunction object representing the VNF and all the information of the VirtualMachine object instance representing the virtual machine to the NM/OSS;
  • Preferred Embodiment 4 After the VNF capacity is increased or decreased, the EM needs to update the attributes of the object instance representing the virtual machine, as shown in FIG.
  • Step S110 After the scale up or down operation of the VNF is completed, the VNF sends a virtual machine information change notification to the EM;
  • Step S112 The EM obtains related information of all virtual machines of the VNF from the VNF according to the notification information, where the related information of each virtual machine includes the virtual machine identifier, the number of CPUs, the memory capacity, the storage capacity, the location of the virtual machine, and Update the attributes of the VirtualMachine object instance corresponding to the virtual machine;
  • Step S114 The NM/OSS sends a message for obtaining the VNF and its virtual machine information to the EM;
  • Step S116 The EM sends an instance of the ManagedFunction object representing the VNF and all the information of the VirtualMachine object instance representing the virtual machine to the NM/OSS;
  • Preferred Embodiment 5 After the EM is restarted, the attributes of the object instance representing the virtual machine need to be updated, as shown in FIG. 12:
  • Step S120 After the EM is restarted, the EM establishes a link with the VNF;
  • Step S122 The EM obtains information about all virtual machines of the VNF from the VNF, where the related information of each virtual machine includes the virtual machine identifier, the number of CPUs, the memory capacity, the storage capacity, the location of the virtual machine, and the corresponding virtual machine corresponding The properties of the VirtualMachine object instance;
  • Step S124 The NM/OSS sends a message for obtaining the VNF and its virtual machine information to the EM;
  • Step S126 The EM sends an instance of the ManagedFunction object representing the VNF and all the information of the VirtualMachine object instance representing the virtual machine it contains to the NM/OSS.
  • the foregoing technical solutions of the embodiments of the present invention achieve the following technical effects: the related art, the EM cannot manage the virtual machine and the virtual resources, and cannot know the current virtual machine and the virtual resources, and further The NM cannot obtain the problem of the virtual resource running according to the EM, so that the operator can obtain the virtual resource status of the current virtual machine and expand the application scope of the virtual network function.
  • a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • a virtual machine object instance corresponding to the virtual machine is established according to the related information of the virtual machine, and the virtual machine object instance is managed to implement the technical solution for managing the virtual machine, and the related solution is solved.
  • the EM is still unable to manage the virtual machine and the virtual resource, and the problem that the current virtual machine and the virtual resource are running cannot be known, so that the operator can obtain the virtual resource of the current virtual machine and expand the virtual network function.
  • Application range

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明提供了一种虚拟网络功能VNF的管理方法及装置，其中，所述方法包括：网元管理EM从VNF实体获取该VNF实体下虚拟机的相关信息；所述EM根据所述相关信息为每一个所述虚拟机建立与该虚拟机对应的虚拟机对象实例；所述EM对所述虚拟机对象实例进行管理。采用本发明提供的上述技术方案，解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。

Description

虚拟网络功能VNF的管理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种虚拟网络功能(Virtualized Network Function，简称为VNF)的管理方法及装置。
背景技术
在现有网络架构之中，网络功能与网络设备是超强耦合的关系，网络功能均通过专门设计的、厂商专有的设备来实现。这带来了诸多不便：比如这些设备在性能上的提高，受限于满足特定/定制化需求而且同时保持电信级可靠性的硬件的发展；又如，当运营商要部署新的业务时，须事先部署新设计的、具有相关专用功能的设备，这会提高运营商的业务部署成本。另一方面，随着中央处理器(Central Processing Unit，简称为CPU)及内存的性能快速地提高，通用型服务器上以软件形式运行网络功能就具备了基础条件，网络功能虚拟化(Network Function Virtualization，简称为NFV)技术也应运而生，它目标就是在通用的硬件设备上运行网络功能，从而通过大范围的部署，可降低资本输出(Capital Expenditure，简称为CAPEX)。“虚拟化”使得网络功能可以按需地部署及更新，且极大地方便远程管理及维护，可降低运营成本(Operating Expense，简称为OPEX)。
网络功能虚拟化后现有网络功能将在VNF上实现，可看作是VNF的应用层。每个VNF可以根据具体的应用配置实现不同的网络功能。因为VNF通常包含多个VNF组件VNFC(VNF Component)，VNFC一般由虚拟机实现，且VNFC和虚拟机通常是一一对应的关系，所以每个VNF将由多个虚拟机构成，每个虚拟机实现的功能以及能使用的虚拟资源都可能不同，同时由于VNF在其生命周期中可以进行扩展和收缩的操作，VNF包含的虚拟机数量以及虚拟机能使用的虚拟资源都可能在网络运行的过程中变化，在这种情况下为了使运营商能够了解虚拟网络功能的构成以及对应的各虚拟机的虚拟资源情况，网络管理系统(Network Management System，简称为NMS，又可称为NM)需要获取到相关的信息。而在传统网络管理系统中NMS通过网元管理系统(Element Management System，简称为EMS，又可称为EM)所管理的网元都是物理机，不存在虚拟机和虚拟资源，运营商通过NMS和EMS之间的北向接口也就不能获取到这些信息。
针对相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况的问题，尚未提出有效的解决方案。
发明内容
为了解决上述技术问题，本发明实施例提供了一种VNF的管理方法及装置。
根据本发明的一个实施例，提供了一种VNF的管理方法，包括：网元管理(Element  Management，简称为EM)从VNF实体获取该VNF实体下虚拟机的相关信息；所述EM根据所述相关信息为每一个所述虚拟机建立与该虚拟机对应的虚拟机对象实例；所述EM对所述虚拟机对象实例进行管理。
在本发明实施例中，所述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
在本发明实施例中，所述表示虚拟机的对象实例和VNFC为一对一，或一对多的关系。
在本发明实施例中，所述方法还包括：所述EM建立与所述VNF实体对应的管理功能对象实例，其中，所述管理功能对象实例命名包含(name-contained)：一个或多个虚拟机对象实例。
在本发明实施例中，所述管理功能对象实例中包括：用于表示所述VNF实体的标识。
在本发明实施例中，所述方法还包括：所述EM接收来自网络管理(Network Management，简称为NM)实体和/或运营支撑系统(Operation Support System，简称为OSS)的请求消息，其中，所述请求消息用于向所述EM请求所述VNF下所述虚拟机的相关信息；所述EM将所述VNF对应的管理功能对象实例以及所述管理功能对象实例包括的虚拟机对象实例发送至所述NM和/或OSS。
在本发明实施例中，所述EM对所述虚拟机对象实例进行管理，包括：所述EM接收来自VNF的第一变更通知信息；在所述第一变更信息的触发下，所述EM获取当前该VNF实体下虚拟机的所述相关信息；所述EM比较当前获取的所述相关信息与所述EM本地保存的所述相关信息；所述EM根据比较结果判定所述VNF增加或减少虚拟机。
在本发明实施例中，所述EM根据比较结果判定所述VNF增加或减少虚拟机，包括：在所述比较结果指示所述当前获取的所述相关信息多于所述EM本地保存的所述相关信息时，所述EM判定所述VNF增加虚拟机；在所述比较结果指示所述当前获取的所述相关信息小于所述EM本地保存的所述相关信息时，所述EM判定所述VNF减少虚拟机。
在本发明实施例中，所述EM根据比较结果判定所述VNF增加或减少虚拟机之后，还包括：在根据所述比较结果判定所述EM增加虚拟机时，所述EM为增加的虚拟机建立与该增加的虚拟机对应的虚拟机对象实例；在根据所述比较结果判定所述EM删除虚拟机时，所述EM删除与删除的虚拟机对应的虚拟机对象实例。
在本发明实施例中，所述EM对所述虚拟机对象实例进行管理，包括：所述EM接收来自VNF的第二变更通知信息；所述EM在所述第二变更通知信息的触发下，更新虚拟机对应的虚拟机对象实例的属性。
在本发明实施例中，在至少以下情况之一时所述EM接收来自VNF的虚拟机相关信息的第二变更通知信息：所述VNF实体的容量发生变化后、所述EM重启。
根据本发明的另一个实施例，还提供了一种虚拟网络功能VNF的管理方法，包括：网络管理NM实体向网元管理EM实体发送请求消息，其中，所述请求消息用于向所述EM请求所述VNF实体下所述虚拟机的相关信息；所述NM实体接收所述EM实体根据所述请求消息返回的所述VNF对应的管理功能对象实例以及所述管理功能对象实例包含的虚拟机对象实例。
在本发明实施例中，所述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
根据本发明的另一个实施例，还提供了一种虚拟网络功能VNF的管理装置，应用于网元管理EM，包括：获取模块，设置为从VNF实体获取该VNF实体下虚拟机的相关信息；建立模块，设置为所述相关信息为每一个所述虚拟机建立与该虚拟机对应的虚拟机对象实例；管理模块，设置为对所述虚拟机对象实例进行管理。
在本发明实施例中，所述获取模块获取的所述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
在本发明实施例中，所述管理模块，包括：建立单元，设置为建立与所述VNF实体对应的管理功能对象实例，其中，所述管理功能对象实例命名包含：一个或多个虚拟机对象实例。
根据本发明的另一个实施例，还提供了一种虚拟网络功能VNF的管理装置，应用于网络管理NM实体，包括：发送模块，设置为向网元管理EM实体发送请求消息，其中，所述请求消息用于向所述EM请求所述VNF实体下所述虚拟机的相关信息；接收模块，设置为接收所述EM实体根据所述请求消息返回的所述VNF对应的管理功能对象实例以及所述管理功能对象实例包含的虚拟机对象实例。
在本发明实施例中，所述发送模块请求的所述虚拟机的相关信息包括：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
通过本发明实施例，采用根据虚拟机的相关信息建立与虚拟机对应的虚拟机对象实例，并通过对虚拟机对象实例进行管理来实现对虚拟机进行管理的技术方案，解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为根据本发明实施例的VNF的管理方法的流程图；
图2为根据本发明实施例的虚拟网络功能及虚拟机的对象关系图；
图3为根据本发明实施例的管理VNF的虚拟机信息的流程图；
图4为根据本发明实施例的VNF的管理装置的结构框图；
图5为根据本发明实施例的VNF的管理装置的再一结构框图；
图6为根据本发明实施例的VNF的管理方法的另一流程图；
图7为根据本发明实施例的VNF的管理装置的又一结构框图；
图8为根据本发明实施例的VNF实例化完成后NM/OSS获取VNF虚拟机信息的流程图；
图9为根据本发明实施例的EM重启后NM/OSS获取虚拟机信息的流程图；
图10为根据本发明实施例的VNF扩展后NM/OSS获取虚拟机信息的流程图；
图11为根据本发明实施例的VNF收缩后NM/OSS获取虚拟机信息的流程图；
图12为根据本发明实施例的VNF容量增加或减少后NM/OS获取虚拟机信息的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明的目的和其他优点可通过在所写的说明书、权利要求书、以及附图中所特别指出的结构来实现和获得。
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
为了解决上述技术问题，在本实施例中提供了一种VNF的管理方法，图1为根据本发明实施例的VNF的管理方法的流程图，如图1所示，包括以下步骤：
步骤S102，网元管理EM从VNF实体获取该VNF实体下虚拟机的相关信息；
步骤S104，上述EM根据上述相关信息为每一个上述虚拟机建立与该虚拟机对应的虚拟机对象实例；
步骤S106，上述EM对上述虚拟机对象实例进行管理。
通过上述各个步骤，采用根据虚拟机的相关信息建立与虚拟机对应的虚拟机对象实例，并通过对虚拟机对象实例(本发明实施例中提及的虚拟机对象示例均可以理解为是表示虚拟机的对象实例)进行管理来实现对虚拟机进行管理的技术方案，解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。
需要说明的是，在本发明实施例中，上述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
在具体实施过程中，由于VNF实体下的虚拟机已经建立了与虚拟机一一对应的虚拟机对象实例，那么VNF也是需要建立与其对应的管理功能对象实例的，并且，管理功能对象实例命名包含：一个或多个虚拟机对象实例，其中，上述管理功能对象实例中包括用于表示上述VNF实体的标识，如图2所示，表示虚拟网络功能的管理对象包含表示虚拟机的管理对象，表示虚拟机的管理对象的属性包括该虚拟机的标识，CPU数量，内存容量，存储容量，该虚拟机的位置，表示虚拟网络功能的管理对象属性中包含虚拟网络功能的标识。
进一步地，EM接收来自网络管理NM实体和/或运营支撑系统OSS的请求消息，其中，上述请求消息用于向上述EM请求上述VNF下上述虚拟机的相关信息；上述EM将上述VNF对应的管理功能对象实例以及上述管理功能对象实例包括的虚拟机对象实例发送至上述NM和/或OSS，以下结合一示例对上述技术方案进行说明：
如图3所示，图3为根据本发明实施例的管理VNF的虚拟机信息的流程图，包括以下步骤：
步骤S300，EM从VNF获取虚拟机相关信息；
步骤S302，VNF返回虚拟机相关信息；
步骤S304，建立、更新或删除虚拟机对应的管理对象实例，即EM根据获取的信息为每个虚拟机建立对应的管理对象实例，当然在需要的情况下，还可以更新虚拟机的管理对象实例属性、删除不存在的虚拟机对应的管理对象实例、增加虚拟机对应的表示虚拟机的对象实例，例如，可以通过以下技术方案实现：
EM接收来自VNF的第一变更通知信息；在上述第一变更信息的触发下，上述EM获取当前该VNF实体下虚拟机的上述相关信息；上述EM比较当前获取的上述相关信息与上述EM本地保存的上述相关信息；上述EM根据比较结果判定上述VNF增加或减少虚拟机。
其中，EM根据比较结果判定上述VNF增加或减少虚拟机可以通过以下技术方案实现：在上述比较结果指示上述当前获取的上述相关信息多于上述EM本地保存的上述相关信息时，上述EM判定上述VNF增加虚拟机；在上述比较结果指示上述当前获取的上述相关信息小于上述EM本地保存的上述相关信息时，上述EM判定上述VNF减少虚拟机。
并且，在EM根据比较结果判定上述VNF增加或减少虚拟机之后，还包括：在根据上述比较结果判定上述EM增加虚拟机时，上述EM为增加的虚拟机建立与该增加的虚拟机对应的虚拟机对象实例；在根据上述比较结果判定上述EM删除虚拟机时，上述EM删除与删除的虚拟机对应的虚拟机对象实例。
EM接收来自VNF的第二变更通知信息；上述EM在上述第二变更通知信息的触发下，更新虚拟机对应的虚拟机对象实例的属性，具体地，在至少以下情况之一时上述EM接收来自VNF的虚拟机相关信息的第二变更通知信息：上述VNF实体的容量发生变化后、上述EM重启。
步骤S306，获取VNF及虚拟机相关信息；
步骤S308，返回标识VNF及各虚拟机的对象实例信息。
在本实施例中还提供了一种VNF的管理装置，应用于网元管理EM用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述，下面对该装置中涉及到的模块进行说明。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。图4为根据本发明实施例的VNF的管理装置的结构框图，如图4所示：
获取模块40，设置为从VNF实体获取该VNF实体下虚拟机的相关信息；
建立模块42，与获取模块40连接，设置为上述相关信息为每一个上述虚拟机建立与该虚拟机对应的虚拟机对象实例；
管理模块44，与建立模块42连接，设置为对上述虚拟机对象实例进行管理。
通过上述各个模块的综合作用，采用根据虚拟机的相关信息建立与虚拟机对应的虚拟机对象实例，并通过对虚拟机对象实例进行管理来实现对虚拟机进行管理的技术方案，解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。
可选地，获取模块40获取的上述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
为了更好的完成管理模块44的功能，如图5所示，管理模块44，包括：建立单元440，设置为建立与上述VNF实体对应的管理功能对象实例，其中，上述管理功能对象实例命名包含一个或多个虚拟机对象实例。
为了完善本发明提供的上述技术方案，在本发明实施例中，还提供了一种VNF的管理方法，图6为根据本发明实施例的VNF的管理方法的另一流程图，如图6所示，包括以下步骤：
步骤S602，网络管理NM实体向网元管理EM实体发送请求消息，其中，上述请求消息 用于向上述EM请求上述VNF实体下上述虚拟机的相关信息；
步骤S604，NM实体接收上述EM实体根据上述请求消息返回的上述VNF对应的管理功能对象实例以及上述管理功能对象实例包含的虚拟机对象实例。
通过上述各个步骤，NM能够在向EM发送请求信息后，EM就能够根据虚拟机的相关信息建立与虚拟机对应的虚拟机对象实例，并根据上述请求消息返回的上述VNF对应的管理功能对象实例以及上述管理功能对象实例包含的虚拟机对象实例的技术方案，解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况，进而NM就不能够根据EM获取到虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。
在本发明实施例中，虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
在本发明实施例中，虚拟机对象实例和VNFC为一对一，或一对多的关系。
在本实施例中还提供了一种VNF的管理装置，应用于NM实体，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述，下面对该装置中涉及到的模块进行说明。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。图7为根据本发明实施例的VNF的管理装置的结构框图，如图7所示：
发送模块70，设置为向网元管理EM实体发送请求消息，其中，上述请求消息用于向上述EM请求上述VNF实体下上述虚拟机的相关信息；
接收模块72，与发送模块70连接，设置为接收上述EM实体根据上述请求消息返回的上述VNF对应的管理功能对象实例以及上述管理功能对象实例包含的虚拟机对象实例。
通过上述各个模块的综合作用，NM能够在向EM发送请求信息后，EM就能够根据虚拟机的相关信息建立与虚拟机对应的虚拟机对象实例，并根据上述请求消息返回的上述VNF对应的管理功能对象实例以及上述管理功能对象实例包含的虚拟机对象实例的技术方案，解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况，进而NM就不能够根据EM获取到虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。
需要说明的是，发送模块70请求的虚拟机的相关信息包括：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、VNFC信息。
为了更好的理解上述VNF的管理过程，以下结合辅图8-附图12以及优选实施例一至优选实施例五进行说明，但不用于限定本发明实施例的保护范围。
优选实施例一：VNF实例化完成后，EM需要给VNF的所有虚拟机建模，如图8所示：
步骤S800：VNF实例化完成后，VNF与EM建立链接；
步骤S802：EM从VNF获取该VNF的所有虚拟机相关信息，其中每个虚拟机的相关信息包括该虚拟机标识，CPU数量，内存容量，存储容量，该虚拟机的位置，并为每个虚拟机建立一个对应的VirtualMachine对象实例来表示各个虚拟机，表示该VNF的ManagedFunction对象实例包含所有的VirtualMachine对象实例，且ManagedFunction对象中有VNF的标识。
步骤S804：NM/OSS发送获取VNF及其虚拟机信息的消息给EM；
步骤S806：EM发送表示该VNF的ManagedFunction对象实例及其包含的所有表示虚拟机的VirtualMachine对象实例的信息给NM/OSS。
优选实施例二：VNF扩展后，EM需要给新增的虚拟机建模，如图9所示：
步骤S900：VNF的Scale out操作完成，VNF给EM发送虚拟机信息变更通知；
步骤S902：EM根据通知信息，从VNF获取该VNF所有虚拟机的相关信息，其中每个虚拟机的相关信息包括该虚拟机标识，CPU数量，内存容量，存储容量，该虚拟机的位置，并为新增的虚拟机建立一个对应的VirtualMachine对象实例来表示该虚拟机，该VirtualMachine对象实例被表示该VNF的ManagedFunction对象实例包含，且ManagedFunction对象中有VNF的标识。
步骤S904：NM/OSS发送获取VNF及其虚拟机信息的消息给EM；
步骤S906：EM发送表示该VNF的ManagedFunction对象实例及其包含的所有表示虚拟机的VirtualMachine对象实例的信息给NM/OSS；
优选实施例三：VNF收缩后，EM应该将减少的虚拟机对应的对象实例删除，如图10所示：
步骤S100：VNF的Scale in操作完成后，VNF给EM发送虚拟机信息变更通知；
步骤S102：EM根据通知信息，从VNF获取该VNF所有虚拟机的相关信息，并删除已经不存在的虚拟机所对应的VirtualMachine对象实例；
步骤S104：NM/OSS发送获取VNF及其虚拟机信息的消息给EM；
步骤S106：EM发送表示该VNF的ManagedFunction对象实例及其包含的所有表示虚拟机的VirtualMachine对象实例的信息给NM/OSS；
优选实施例四：VNF容量增加或减少后，EM需要更新表示虚拟机的对象实例的属性，如图11所示：
步骤S110：VNF的Scale up或down操作完成后，VNF给EM发送虚拟机信息变更通知；
步骤S112：EM根据通知信息，从VNF获取该VNF所有虚拟机的相关信息，其中每个虚拟机的相关信息包括该虚拟机标识，CPU数量，内存容量，存储容量，该虚拟机的位置，并更新虚拟机对应的VirtualMachine对象实例的属性；
步骤S114：NM/OSS发送获取VNF及其虚拟机信息的消息给EM；
步骤S116：EM发送表示该VNF的ManagedFunction对象实例及其包含的所有表示虚拟机的VirtualMachine对象实例的信息给NM/OSS；
优选实施例五：EM重启后，需要更新表示虚拟机的对象实例的属性，如图12所示：
步骤S120：EM重启后，EM与VNF建立链接；
步骤S122：EM从VNF获取该VNF所有虚拟机的相关信息，其中每个虚拟机的相关信息包括该虚拟机标识，CPU数量，内存容量，存储容量，该虚拟机的位置，并更新虚拟机对应的VirtualMachine对象实例的属性；
步骤S124：NM/OSS发送获取VNF及其虚拟机信息的消息给EM；
步骤S126：EM发送表示该VNF的ManagedFunction(管理功能)对象实例及其包含的所有表示虚拟机的VirtualMachine(虚拟机)对象实例的信息给NM/OSS。
综上所述，本发明实施例的上述技术方案达到了以下技术效果：解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况，进而NM就不能够根据EM获取到虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。
在另外一个实施例中，还提供了一种软件，该软件用于执行上述实施例及优选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的对象在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员 来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
通过本发明提供的上述技术方案，采用根据虚拟机的相关信息建立与虚拟机对应的虚拟机对象实例，并通过对虚拟机对象实例进行管理来实现对虚拟机进行管理的技术方案，解决了相关技术中，EM尚不能管理虚拟机和虚拟资源而导致的不能知晓当前虚拟机以及虚拟资源的运行情况的问题，进而实现运营商能够获取到当前虚拟机的虚拟资源情况，扩展了虚拟网络功能的应用范围。

Claims (18)

  1. 一种虚拟网络功能VNF的管理方法，包括：
    网元管理EM从VNF实体获取该VNF实体下虚拟机的相关信息；
    所述EM根据所述相关信息为每一个所述虚拟机建立与该虚拟机对应的虚拟机对象实例；
    所述EM对所述虚拟机对象实例进行管理。
  2. 根据权利要求1所述的方法，其中，所述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、虚拟网络功能构件VNFC的信息。
  3. 根据权利要求1所述的方法，其中，所述虚拟机对象实例对应一个或多个VNFC。
  4. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述EM建立与所述VNF实体对应的管理功能对象实例，其中，所述管理功能对象实例命名包含：一个或多个虚拟机对象实例。
  5. 根据权利要求4所述的方法，其中，所述管理功能对象实例中包括：用于表示所述VNF实体的标识。
  6. 根据权利要求5所述的方法，其中，所述方法还包括：
    所述EM接收来自网络管理NM实体和/或运营支撑系统OSS的请求消息，其中，所述请求消息用于向所述EM请求所述VNF下所述虚拟机的相关信息；
    所述EM将所述VNF对应的管理功能对象实例以及所述管理功能对象实例包括的虚拟机对象实例发送至所述NM和/或OSS。
  7. 根据权利要求1所述的方法，其中，所述EM对所述虚拟机对象实例进行管理，包括：
    所述EM接收来自VNF的第一变更通知信息；
    在所述第一变更信息的触发下，所述EM获取当前该VNF实体下虚拟机的所述相关信息；
    所述EM比较当前获取的所述相关信息与所述EM本地保存的所述相关信息；
    所述EM根据比较结果判定所述VNF增加或减少虚拟机。
  8. 根据权利要求7所述的方法，其中，所述EM根据比较结果判定所述VNF增加或减少虚拟机，包括：
    在所述比较结果指示所述当前获取的所述相关信息多于所述EM本地保存的所述相关信息时，所述EM判定所述VNF增加虚拟机；
    在所述比较结果指示所述当前获取的所述相关信息小于所述EM本地保存的所述相关信息时，所述EM判定所述VNF减少虚拟机。
  9. 根据权利要求7或8所述的方法，其中，所述EM根据比较结果判定所述VNF增加或减少虚拟机之后，还包括：
    在根据所述比较结果判定所述EM增加虚拟机时，所述EM为增加的虚拟机建立与该增加的虚拟机对应的虚拟机对象实例；
    在根据所述比较结果判定所述EM删除虚拟机时，所述EM删除与删除的虚拟机对应的虚拟机对象实例。
  10. 根据权利要求1所述的方法，其中，所述EM对所述虚拟机对象实例进行管理，包括：
    所述EM接收来自VNF的第二变更通知信息；
    所述EM在所述第二变更通知信息的触发下，更新虚拟机对应的虚拟机对象实例的属性。
  11. 根据权利要求10所述的方法，其中，在至少以下情况之一时所述EM接收来自VNF的虚拟机相关信息的第二变更通知信息：所述VNF实体的容量发生变化后、所述EM重启。
  12. 一种虚拟网络功能VNF的管理方法，包括：
    网络管理NM实体向网元管理EM实体发送请求消息，其中，所述请求消息用于向所述EM请求所述VNF实体下虚拟机的相关信息；
    所述NM实体接收所述EM实体根据所述请求消息返回的所述VNF对应的管理功能对象实例以及所述管理功能对象实例包含的虚拟机对象实例。
  13. 根据权利要求12所述的方法，其中，所述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置、虚拟网络功能构件VNFC的信息。
  14. 一种虚拟网络功能VNF的管理装置，应用于网元管理EM，包括：
    获取模块，设置为从VNF实体获取该VNF实体下虚拟机的相关信息；
    建立模块，设置为所述相关信息为每一个所述虚拟机建立与该虚拟机对应的虚拟机对象实例；
    管理模块，设置为对所述虚拟机对象实例进行管理。
  15. 根据权利要求14所述的装置，其中，所述获取模块获取的所述虚拟机的相关信息包括以下至少之一：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置。
  16. 根据权利要求15所述的装置，其中，所述管理模块，包括：
    建立单元，设置为建立与所述VNF实体对应的管理功能对象实例，其中，所述管理功能对象实例命名包含：一个或多个虚拟机对象实例。
  17. 一种虚拟网络功能VNF的管理装置，应用于网络管理NM实体，包括：
    发送模块，设置为向网元管理EM实体发送请求消息，其中，所述请求消息用于向所述EM请求所述VNF实体下虚拟机的相关信息；
    接收模块，设置为接收所述EM实体根据所述请求消息返回的所述VNF对应的管理功能对象实例以及所述管理功能对象实例包含的虚拟机对象实例。
  18. 根据权利要求17所述的装置，其中，所述发送模块请求的所述虚拟机的相关信息包括：虚拟机标识、虚拟机中的中央处理器CPU数量、虚拟机的内存容量、虚拟机的存储容量、虚拟机的位置。
PCT/CN2015/087708 2015-01-20 2015-08-20 虚拟网络功能vnf的管理方法及装置 WO2016115896A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510027963.5 2015-01-20
CN201510027963.5A CN105871570A (zh) 2015-01-20 2015-01-20 虚拟网络功能vnf的管理方法及装置

Publications (1)

Publication Number Publication Date
WO2016115896A1 true WO2016115896A1 (zh) 2016-07-28

Family

ID=56416376

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/087708 WO2016115896A1 (zh) 2015-01-20 2015-08-20 虚拟网络功能vnf的管理方法及装置

Country Status (2)

Country Link
CN (1) CN105871570A (zh)
WO (1) WO2016115896A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190026168A1 (en) * 2017-07-24 2019-01-24 At&T Intellectual Property I, L.P. Geographical Redundancy and Dynamic Scaling for Virtual Network Functions
US11201798B2 (en) 2018-05-07 2021-12-14 At&T Intellectual Property I, L.P. Automated virtual network function modification

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107819598A (zh) * 2016-09-13 2018-03-20 中兴通讯股份有限公司 一种管理网络功能节点的方法及装置
CN108023749A (zh) * 2016-11-03 2018-05-11 华为技术有限公司 管理网络切片的方法、设备和系统
CN108207008A (zh) * 2016-12-19 2018-06-26 中兴通讯股份有限公司 一种虚拟化网元的管理方法和装置
CN109213567B (zh) * 2017-06-29 2022-05-13 华为技术有限公司 一种管理vnf实例化的方法和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102364894A (zh) * 2011-10-21 2012-02-29 中兴通讯股份有限公司 一种配置数据文件的下发方法及网管设备
US20140201374A1 (en) * 2013-01-11 2014-07-17 Futurewei Technologies, Inc. Network Function Virtualization for a Network Device
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN104253866A (zh) * 2014-09-20 2014-12-31 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102364894A (zh) * 2011-10-21 2012-02-29 中兴通讯股份有限公司 一种配置数据文件的下发方法及网管设备
US20140201374A1 (en) * 2013-01-11 2014-07-17 Futurewei Technologies, Inc. Network Function Virtualization for a Network Device
CN104219127A (zh) * 2014-08-30 2014-12-17 华为技术有限公司 一种虚拟网络实例的创建方法以及设备
CN104253866A (zh) * 2014-09-20 2014-12-31 华为技术有限公司 虚拟网络功能网元的软件部署方法、系统及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ETSI: "Network Functions Virtualisation (NFV); Management and Orchestration", ETSI GS NFV-MAN 001 VL. 1.1, vol. 28, 31 December 2014 (2014-12-31), pages 100-101 - 115-117 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190026168A1 (en) * 2017-07-24 2019-01-24 At&T Intellectual Property I, L.P. Geographical Redundancy and Dynamic Scaling for Virtual Network Functions
US11003516B2 (en) * 2017-07-24 2021-05-11 At&T Intellectual Property I, L.P. Geographical redundancy and dynamic scaling for virtual network functions
US11201798B2 (en) 2018-05-07 2021-12-14 At&T Intellectual Property I, L.P. Automated virtual network function modification

Also Published As

Publication number Publication date
CN105871570A (zh) 2016-08-17

Similar Documents

Publication Publication Date Title
WO2016115896A1 (zh) 虚拟网络功能vnf的管理方法及装置
CN109729143B (zh) 在终端设备上部署基于网络的云平台
CN107689882B (zh) 一种虚拟化网络中业务部署的方法和装置
US10862760B2 (en) Network functions virtualization
US10545750B2 (en) Distributed upgrade in virtualized computing environments
US10917294B2 (en) Network function instance management method and related device
US20170244596A1 (en) Configuration Information Management Method, Device, Network Element Management System and Storage Medium
CN107959582B (zh) 一种切片实例的管理方法及装置
US11496414B2 (en) Interoperable cloud based media processing using dynamic network interface
CN107800565B (zh) 巡检方法、装置、系统、计算机设备和存储介质
EP3291499A1 (en) Method and apparatus for network service capacity expansion
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
CN103595801B (zh) 一种云计算系统及其虚拟机实时监控方法
US20170373931A1 (en) Method for updating network service descriptor nsd and apparatus
CN111130825B (zh) 网络切片模板生成方法、装置、设备及存储介质
US20180034709A1 (en) Method and Device for Asset Information Management
CN107967140B (zh) 软件修改的发起方法、发布元数据的方法及装置
EP3455728A1 (en) Orchestrator for a virtual network platform as a service (vnpaas)
WO2014169870A1 (zh) 虚拟网元自动装载及虚拟机ip地址获取的方法与系统、存储介质
CN104199957A (zh) 一种Redis通用代理的实现方法
WO2016179999A1 (zh) 虚拟网络功能vnf的虚拟资源的管理方法及装置
EP3672314B1 (en) Network management method, device and system
CN111090495A (zh) 节点管理方法、装置、设备、存储介质和系统
KR20150108230A (ko) 클러스터 시스템 구축 방법 및 장치
WO2016183832A1 (zh) 一种网络业务实例化的方法及设备

Legal Events

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

Ref document number: 15878565

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

Country of ref document: EP

Kind code of ref document: A1