WO2017173667A1 - 一种管理方法及装置 - Google Patents

一种管理方法及装置 Download PDF

Info

Publication number
WO2017173667A1
WO2017173667A1 PCT/CN2016/078913 CN2016078913W WO2017173667A1 WO 2017173667 A1 WO2017173667 A1 WO 2017173667A1 CN 2016078913 W CN2016078913 W CN 2016078913W WO 2017173667 A1 WO2017173667 A1 WO 2017173667A1
Authority
WO
WIPO (PCT)
Prior art keywords
affinity
information
rule
management unit
target object
Prior art date
Application number
PCT/CN2016/078913
Other languages
English (en)
French (fr)
Inventor
许瑞岳
张凯
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201680083907.6A priority Critical patent/CN108886473B/zh
Priority to JP2018552724A priority patent/JP6680901B2/ja
Priority to BR112018070584-5A priority patent/BR112018070584B1/pt
Priority to KR1020187032019A priority patent/KR102184512B1/ko
Priority to EP16897601.7A priority patent/EP3432515B1/en
Priority to PCT/CN2016/078913 priority patent/WO2017173667A1/zh
Publication of WO2017173667A1 publication Critical patent/WO2017173667A1/zh
Priority to US16/151,100 priority patent/US11296945B2/en
Priority to US17/698,169 priority patent/US20220210019A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management

Definitions

  • the present invention relates to the field of communications, and in particular, to a management method and apparatus in the field of Network Function Virtualization (NFV) technology, such as a management method and apparatus based on affinity information.
  • NFV Network Function Virtualization
  • NFV technology is based on massive and normalized servers and switches, and implements various network functions (such as virtual operations, virtual wide area networks, and virtual application access routers) through software to reduce costs and accelerate service deployment and resource flexibility. , build an innovative ecological chain.
  • a computer is virtualized into multiple virtual logical computers, namely virtual machines (VMs).
  • VMs virtual machines
  • a virtual machine generally uses a server physical network port, a virtual network card, and a virtual switch connected to the switch in the chassis or the top switch to perform data communication with the outside of the server.
  • NFV technology By borrowing the information technology (Information Technology, IT) virtualization technology, NFV technology enables many types of network devices to be incorporated into industry standards. For example, network devices such as services, switching, and storage can be deployed in data centers or network nodes. . NFV technology implements various network functions in software and can run these network functions on industry-standard servers. It can also migrate, instantiate, redeploy, etc. these network functions as needed, and does not need to install new ones. device of. That is, the virtualized network function (VNF) can be generated by the NFV technology. Network Service (NS) can be implemented between multiple VNFs.
  • VNFD Virtualized Network Function Descriptor
  • NSD Network Service Descriptor
  • the embodiment of the invention provides a management method and device, so as to implement effective management of a network service unit or a virtual network function unit.
  • an embodiment of the present invention provides a management method, where the method includes: the second management unit acquires affinity information, where the affinity information is used to configure affinity between the target object and other objects, and/or Anti-affinity, or affinity and/or anti-affinity for configuring a sub-object of the target object with other objects; the second management unit sends a management request to the first management unit, the management request carrying the pro And information; the first management unit receives the management request sent by the second management unit and manages the target object according to the affinity information.
  • the first management unit may be used to manage virtual resources of the target object; the second management unit may be used to manage services of the target object.
  • the target object may be a network service unit or a virtual network functional unit. For example, when the target object is a network business unit, the child object of the target object may be a virtual network functional unit.
  • the first management unit After receiving the management request carrying the affinity information, the first management unit can effectively manage the target object according to the affinity information. Further, the solution of the embodiment of the present invention can implement affinity and/or anti-affinity between network elements in all stages of the management process. For example, the network element can be implemented in a deployment phase and a maintenance phase in the management process. Affinity and/or anti-affinity between.
  • the affinity information described above includes at least one of the following:
  • the affinity information may be an affinity deactivation indication information, where the affinity deactivation indication information is used to indicate that the first management unit ignores the first affinity rule related to the target object in the process of managing the target object.
  • the first affinity rule may be an affinity rule preset in the first management unit.
  • the affinity information may be a second affinity rule, and the second affinity rule includes at least one of rule indication information, affinity object identifier, and range indication information.
  • the second affinity rule may be an affinity rule obtained by the second management unit according to the configuration requirement.
  • the affinity information described above may be affinity constraint information for indicating constraints of affinity and/or anti-affinity associated with the target object.
  • affinity constraint information for indicating constraints of affinity and/or anti-affinity associated with the target object.
  • the rule indication information may be used to indicate that the second affinity rule is an affinity rule and/or an anti-affinity rule.
  • the affinity object identifier may be used to identify an action object of the second affinity rule, where the affinity object includes an identifier of the network service instance, an identifier of the network service descriptor, an identifier of the virtual network function instance, or an identifier of the virtual network function descriptor. At least one of them to describe affinity and anti-affinity between network elements in a variety of ways.
  • the above range indication information may be used to indicate the scope of application of the second affinity rule, for example, a data center or the like. It can be seen that, in the solution of the embodiment of the present invention, the affinity and/or the anti-affinity between the network elements can be described in various manners, and the implementation is more flexible.
  • the first management unit receives the management request sent by the second management unit, and manages the target object according to the affinity information.
  • the management process may include: determining, according to the affinity information, the management target object. a third affinity rule for managing the required information; deploying the target object according to a third affinity rule of the management requirement information; and determining a fourth affinity rule of the corresponding virtual resource according to the third rule of the management requirement information;
  • a virtual resource is configured for deploying the target object according to a fourth affinity rule of the virtual resource.
  • the foregoing management request further carries a descriptor identifier of the target object, which is an identifier of the network service descriptor or an identifier of the virtual network function descriptor, so that the first management unit determines the management according to the descriptor identifier of the target object.
  • the management requirements information required by the target object is an identifier of the network service descriptor or an identifier of the virtual network function descriptor.
  • the foregoing management request is a lifecycle management request, and the life cycle management of the network service or the virtual network function can be implemented by the foregoing method.
  • the embodiment of the present invention provides a management device, which can implement the functions performed by the first management unit in the foregoing method instance, and the functions can be implemented by using hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the apparatus includes a processor and a transceiver configured to support the apparatus to perform the corresponding functions of the above methods.
  • the transceiver is used to support communication between the device and other network elements.
  • the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • the embodiment of the present invention provides a management device, which can implement the functions performed by the second management unit in the foregoing method instance, and the functions can be implemented by using hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the apparatus includes a processor and a transceiver configured to support the apparatus to perform the corresponding functions of the above methods.
  • the transceiver is used to support communication between the device and other network elements.
  • the apparatus can also include a memory for coupling with the processor that retains the program instructions and data necessary for the apparatus.
  • an embodiment of the present invention provides a communication system, where the system includes the apparatus that can implement the functions of the first management unit and the apparatus that can implement the functions of the second management unit.
  • an embodiment of the present invention provides a computer storage medium for storing the foregoing A computer software instruction for a management unit that includes a program designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions used by the second management unit, which includes a program designed to execute the above aspects.
  • the affinity information is acquired by the second management unit, and the management request for carrying the affinity information is sent to the first management unit; the second management unit receives the first management unit. After the management request is sent, the target object is managed according to the affinity information carried in the management request, thereby implementing effective management of the network service unit or the virtual network functional unit.
  • the solution of the embodiment of the present invention can implement affinity and/or anti-affinity between network elements in all stages of management, and describe affinity and/or inverse between network elements in various manners. Affinity makes the realization of affinity and/or anti-affinity between network elements more flexible.
  • FIG. 1 is a schematic diagram of a possible network architecture according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of communication of a management method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of communication of another management method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of communication according to still another management method according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a first management unit according to an embodiment of the present disclosure.
  • FIG. 5B is a schematic structural diagram of another first management unit according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a second management unit according to an embodiment of the present disclosure.
  • FIG. 6B is a schematic structural diagram of another second management unit according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and are not limited to the technical solutions provided by the embodiments of the present invention.
  • Evolution and implementation of new business scenarios, implementation of the present invention The technical solutions provided by the examples are equally applicable to similar technical problems.
  • the NFV-based network architecture mainly includes: Operation Support System (OSS)/Business Support System (BSS), Element Manager (EM) unit, and virtualized network.
  • Function (VNF) unit NFV Infrastructure (NFVI) unit, NFV Orchestrator (NFVO) unit, Virtual Network Function Management (VNF Manager, VNFM) unit and virtualization infrastructure Management (Virtualised Infrastructure Manager, VIM) unit.
  • VNF Operation Support System
  • BSS Business Support System
  • EM Element Manager
  • VNF Function
  • NFVI NFV Infrastructure
  • NFVO NFV Orchestrator
  • VNF Manager Virtual Network Function Management
  • VIM Virtualised Infrastructure Manager
  • OSS/BSS is a support system for the integration and information resource sharing of telecom operators. It is mainly composed of network management, system management, billing, business, accounting and customer services, while the system passes through a unified information bus. Organically integrated. OSS/BSS can help operators determine the development direction of the system while helping them to develop their own operational support systems. It can also help users to formulate system integration standards and improve and improve users' business levels. The OSS/BSS is used in the NFV-based network architecture to make necessary modifications and adjustments to the lifecycle management (eg, instantiation, etc.) of each network element.
  • the EM unit is used to manage some of the VNF units.
  • the NFVI unit is a collective term for all hardware devices and software components in an environment with the ability to deploy network function virtualization.
  • An NFVI unit can be deployed across several physical sites (eg, data center operations) where the network providing data connections to these physical sites is also considered part of the NFVI unit.
  • the NFVO unit can be used to manage the life cycle of the NS, coordinate the lifecycle management of the NS, coordinate the lifecycle management of the VNF (requires support from the VNFM), and coordinate the management of various resources of the NFVI unit (requires VIM support) to ensure Optimized configuration of all types of resources and connections required.
  • life cycle management refers to the management of instantiation, maintenance and termination of VNF units or NS units.
  • the VNFM unit is responsible for the lifecycle management of the VNF.
  • the VIM unit is responsible for controlling and managing the computing resources, storage resources, and network resources of the NFVI unit.
  • the VIM can be deployed to the infrastructure domain of the underlying network operator (eg, NFVI access point/service offering point).
  • the network architecture shown in FIG. 1 above may include a part of a 3rd Generation Partnership Project (3GPP) system and a part of a NFV Management and Orchestration (NFV MANO) system.
  • 3GPP system The parts mainly include the OSS/BSS and EM units shown in FIG. 1.
  • the parts of the NFV MANO (also abbreviated as MANO) system mainly include the NFVO unit, the VNFM unit and the VIM unit shown in FIG. 1. Informational interactions can be established between portions of the 3GPP system and portions of the MANO system.
  • affinity and anti-affinity can also be understood as: if multiple VNF units can exist in the same area (such as data center, etc.), then these VNF units are said to have affinity; If multiple VNF units are not present in the same region, then these VNF units are said to have anti-affinity.
  • low-loss requires that the interacting network elements are deployed in the same or similar physical areas, that is, there is affinity between the interacting network elements.
  • high-availability requires that the primary network element and the standby network element cannot be deployed. The same physical area, that is, the primary network element and the standby network element have anti-affinity.
  • the network element is a soft and hard machine, and the affinity and/or anti-affinity between the network elements can be implemented within the 3GPP system.
  • the NFV-based network architecture software and hardware are separated, and related information of the network element is managed by a part of the 3GPP system, and related information of the resource element of the network element is managed by a part of the MANO system, in order to implement the network element.
  • affinity and/or anti-affinity there is a need to establish an interaction of information about affinity and/or anti-affinity between portions of the 3GPP system and portions of the MANO system.
  • the traditional network element virtual It is a VNF unit with corresponding functions.
  • an embodiment of the present invention provides a management method, and an apparatus and system based on the method, in order to implement effective management of a network service unit or a virtual network function unit.
  • the second management unit sends a management request of the target object to the first management unit, where the management request carries affinity information, and the affinity information is used to configure affinity between the target object and other objects and/or Or anti-affinity, or for configuring affinity and/or anti-affinity between the sub-object of the target object and other objects; the first management unit manages the target object according to the affinity information.
  • the target object may be an NS unit or a VNF unit.
  • the child object of the NS is a VNF unit.
  • the first management unit is one end that receives the management request, and may be, for example, the NFVO unit or the VNFM unit in FIG. 1;
  • the second management unit is one end that sends a management request, and may be, for example, the OSS in FIG. /BSS or EM unit.
  • the first management unit may be used to manage virtual resources of the target object, and the second management unit may be used to manage services of the target object.
  • the solution of the embodiment of the present invention can be applied to the NFV-based network architecture shown in FIG. 1.
  • the solution of the embodiment of the present invention can implement the interaction of the affinity information between the part of the 3GPP system and the part of the MANO system, thereby effectively managing target. Further, the solution provided by the embodiment of the present invention can implement affinity and/or anti-affinity between different network elements in all stages of management.
  • FIG. 2 shows a method for managing affinity information based on an embodiment of the present invention.
  • the method shown in Figure 2 can be applied to the network architecture shown in Figure 1, wherein the first management unit can be an NFVO unit, and the second management unit can be an OSS/BSS, and the first management unit and the second management unit can be The communication may be performed through the OS-Ma-nfvo interface; or the first management unit may be a VNFM unit, and the second management unit may be an EM unit, and the first management unit and the second management unit may be connected through the Ve-Vnfm-em interface. Communication.
  • the second management unit obtains affinity information for configuring affinity and/or anti-affinity between the target object and other objects, or for configuring sub-objects of the target object with other Affinity and/or anti-affinity between objects.
  • affinity information does not preclude the affinity information from being used for configuring the affinity and/or anti-affinity between the target object and other objects, and for configuring the child of the target object.
  • affinity and/or anti-affinity between an object and other objects does not preclude the affinity information from being used for configuring the affinity and/or anti-affinity between the target object and other objects, and for configuring the child of the target object.
  • the second management unit before the second management unit acquires the affinity information, it also determines the target object to be managed.
  • the target object may be an NS unit or a VNF unit.
  • the second management unit may determine that a certain NS unit is the target object among the plurality of NS units, or may be in multiple VNF units. Determine a VNF unit as the above target object.
  • the second management unit may first determine whether the target object is an NS unit or a VNF unit; when determining to be an NS unit, the second management unit determines, in the plurality of NS units, an NS unit as a target.
  • the affinity information may include at least one of: affinity deactivation indication information; affinity constraint information, the affinity constraint information is used to indicate affinity and/or anti-affinity associated with the target object.
  • the second affinity rule includes at least one of rule indication information, affinity object identifier, and range indication information.
  • the affinity information includes the affinity deactivation indication information, where the affinity deactivation indication information is used to indicate that the first management unit ignores the target object in the process of managing the target object.
  • First affinity rule specifies an object having affinity and/or anti-affinity with the target object, and ignoring the first affinity rule associated with the target object can be understood as ignoring affinity with the target object. And/or anti-affinity objects.
  • the foregoing target object may be a first virtual network functional unit (which may be described as VNF1)
  • the first affinity rule associated with the target object may be: VNF 1 and a second virtual network functional unit.
  • VNF 2 (Can be described as VNF 2) has affinity, and VNF 1 has anti-affinity with a third virtual network functional unit (which can be described as VNF 3).
  • VNF 3 a third virtual network functional unit
  • the affinity deactivation indication information may be used to instruct the first management unit to ignore the VNF 1 related An affinity rule that ignores the affinity of VNF1 to VNF 2 and the anti-affinity of VNF1 to VNF 3.
  • the first affinity rule related to the target object can be ignored in an emergency, and the management operation of the first management network element can be simplified, thereby quickly performing the target object. Deploy or maintain to improve management efficiency.
  • the affinity information is the deactivation indication information
  • the affinity information may cause the first management unit to use the first affinity rule. Configured to be inactive or in a deactivated state.
  • the affinity information includes the affinity constraint information described above, the affinity constraint information being used to indicate a constraint of affinity and/or anti-affinity associated with the target object,
  • the constraint can be the degree of reliability, the length of the delay, and the like.
  • the second management unit requires a first virtual network function instance (which may be described as VNF instance 1) based on a first virtual network function descriptor (which may be described as VNFD1), and a second virtual network function instance (which may be described as a VNF)
  • VNF instance 1 a first virtual network function instance
  • VNFD1 a first virtual network function descriptor
  • VNF 2 a second virtual network function instance
  • VNF instance 3 a second virtual network function instance
  • VNF instance 4 which can be described as VNF instance 4
  • the affinity constraint information can be used for Indicates that VNF instance 1, VNF instance 2, VNF instance 3, and VNF instance 4 need to be deployed in different physical areas or data centers as much as possible.
  • the affinity information is a second affinity rule
  • the second affinity rule includes at least one of rule indication information, affinity object identifier, and range indication information.
  • the rule indication information may be used to indicate that the second affinity rule is an affinity rule and/or an anti-affinity rule.
  • the affinity object identifier can be used to indicate the action object of the second affinity rule, for example, it can be understood that the affinity object identifier can indicate which objects have affinity and/or anti-affinity, or the affinity object identifier It can indicate which objects need to be constrained by affinity and/or anti-affinity.
  • the affinity object identification may include an identification of an instance of the affinity object and/or an identification of a descriptor of the affinity object, eg, the affinity object identification may include an identification of a network service instance, an identification of a network service descriptor, a virtual network function instance At least one of an identifier or an identifier of a virtual network function descriptor.
  • the affinity object may be the above target object, may be a unit related to the target object, or may be another unit.
  • the affinity object may be the NS unit, or may be a VNF unit associated with the NS unit, or may be other units.
  • the affinity object identifier may include at least one of an identifier of the network service instance, an identifier of the network service descriptor, an identifier of the virtual network function instance, or an identifier of the virtual network function descriptor.
  • the affinity object identifier includes an identification of the virtual network function instance and/or an identification of the virtual network function descriptor.
  • the range indication information may be used to indicate the scope of application of the second affinity rule, for example, the scope of application may be a physical area, a data center, or the like.
  • the affinity and anti-affinity between network elements can be described by the VNFD included in the NSD or VNFD. It can be understood that the identifier of the VNFD is used to indicate the affinity and anti-affinity constraints. VNFD or Virtual Link Descriptor (VLD) identifiers of all instances.
  • VNFD or Virtual Link Descriptor (VLD) identifiers of all instances.
  • the affinity and/or anti-parity between network elements can only be described based on the granularity of VNFD.
  • sexuality has certain limitations.
  • the affinity information may be based on the granularity of the VNFD or the granularity of the NSD, or may be based on the granularity of the NS instance or the granularity of the VNF instance. Therefore, the solution of the embodiment of the present invention.
  • the affinity and/or anti-affinity between network elements can be described in various ways, and the implementation is more flexible.
  • the second management unit sends a management request to the first management unit, the management request carrying the affinity information.
  • the management request may further carry an identifier of the descriptor of the target object.
  • the identifier of the descriptor of the target object may be an identifier of the network service descriptor or an identifier of the virtual network function descriptor.
  • the second management unit may send a management request to the first management unit through a communication interface between the first management unit and the second management unit.
  • the communication interface between the first management unit and the second management unit may be an OS-Ma-nfvo interface or a Ve-Vnfm-em interface.
  • the management request may be a lifecycle management request, and the lifecycle management request may be used for lifecycle management of the target object; or the management request may be other types of management requests.
  • some or all of the above affinity information may also be preset in the first management unit.
  • at least one of the affinity deactivation indication information, the second affinity rule, or the affinity constraint information is preset in the first management unit.
  • the first management unit receives the management request sent by the second management unit and manages the target object according to the affinity information.
  • the process by which the first management unit manages the target object according to the affinity information may include the following four parts:
  • the first part determines a third affinity rule for managing the management requirement information required by the target object according to the affinity information.
  • the affinity information may include an identifier of a descriptor of the target object, and the first part may include the following two steps:
  • the first management unit searches for the descriptor of the target object according to the descriptor identifier of the target object, and parses the descriptor of the target object, and determines management requirement information required for managing the target object. If the target object is an NS, the corresponding NSD is searched according to the NSD ID of the NS, and the NSD is parsed. Since each NSD includes multiple VNFDs, the process of parsing the NSD is to analyze which VNFDs and combinations of deployment specifications are available under the NSD. The management requirement information required for managing the NS is determined according to the analysis result.
  • the management requirement information of the NS includes multiple VNF instance requirement information, and the VNF instance requirement information includes a VNFD ID and a deployment specification corresponding to the VNFD ID. If the target object is The VNF searches for the corresponding VNFD according to the VNFD ID of the VNF, and parses the VNFD to determine instance demand information of the VNF.
  • the first management unit determines a third affinity rule for managing the demand information based on the affinity information. If the target object is an NS, determining, according to the VNFD in each VNF instance requirement information in the plurality of VNF instance requirement information and/or the affinity rule and/or the affinity information in the NSD corresponding to the NS in the NFV network architecture, respectively An affinity rule for each VNF instance requirement information, that is, an object that has affinity and/or anti-affinity with each VNF instance requirement information, respectively.
  • the target object is a VNF, determining an affinity rule of the VNF instance requirement information according to the VNFD corresponding to the VNF and/or an affinity rule associated with the VNFD in the NSF, that is, determining affinity with the VNF instance requirement information, and / or anti-affinity objects.
  • the second part the first management unit deploys the target object according to the third affinity rule of the management requirement information. For example, if the target object is an NS, the VNF instantiation is deployed or requested according to the affinity rule of each VNF instance requirement information; if the target object is a VNF, the VNF is instantiated according to the affinity rule of the VNF instance requirement information.
  • the third part the first management unit determines a fourth affinity rule of the corresponding virtual resource according to the third affinity rule of the management requirement information. For example, the first management unit converts the third affinity rule that manages the demand information into a fourth affinity rule of the corresponding virtual resource; and, for example, the first management unit generates a corresponding virtual according to the third affinity rule of the management requirement information.
  • a fourth affinity rule of the resource for example, the first management unit may search for a fourth affinity rule of the corresponding virtual resource according to the third affinity rule of the management requirement information.
  • the virtual resource may be a computing resource, a network resource, a storage resource, or the like on the virtual machine.
  • the same VNF instance can be deployed on multiple virtual machines, or multiple VNF instances can be deployed on one virtual machine. Therefore, when the affinity object is a VNF instance, the foregoing fourth affinity rule for managing the requirement information is converted into a fourth affinity rule of the corresponding virtual resource, which can be understood as converting the affinity rule between the affinity objects into Affinity rules between virtual machines that store VNF instances.
  • VNF instance 1 has a reverse affinity with VNF instance 2, and the virtual machine corresponding to VNF instance 1 is VM1, and the virtual machine corresponding to VNF instance 2 is VM2, the first between VNF instance 1 and VNF instance 2
  • the amphipathic rule is converted into a fourth affinity rule between the virtual machine 1 and the virtual machine 2, that is, the virtual machine 1 and the virtual machine 2 also have a reverse affinity.
  • the fourth part the first management unit configures the virtual resource for the deployment target object according to the fourth affinity rule of the virtual resource.
  • the target object is a VNF instance
  • configuring a virtual resource for the deployment target object can be understood as determining which virtual machine the instantiated VNF instance exists on, and which resources on the virtual machine are used.
  • the fourth affinity rule of the virtual resource is virtual machine 1 and virtual machine 2 Having a reverse affinity, the VNF instance 1 and the VNF instance 2 are respectively requested to configure virtual resources according to the reverse affinity between the virtual machine 1 and the virtual machine 2.
  • the second management unit acquires affinity information for configuring affinity and/or anti-affinity between the target object and other sub-objects, or for configuring the target object. Affinity and/or anti-affinity between the child object and other child objects; the second management unit sends a management request carrying the affinity information to the first management unit; the second management unit according to the affinity in the management request Information is managed on the target object to enable efficient management of network business units or virtual network functional units. Further, the solution of the embodiment of the present invention can implement affinity and/or anti-affinity between network elements in all stages of management, and describe affinity and/or inverse between network elements in various manners. Affinity makes the realization of affinity and/or anti-affinity between network elements more flexible.
  • FIG. 3 illustrates another method for managing affinity based information provided by an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 2 can be referred to the detailed description of FIG. 2, and details are not described herein.
  • the solution shown in Figure 3 can be applied to the following application scenarios: OSS/BSS needs to create an NS instance 2, based on the service management requirements (for example, service delay, low loss) in the scenario.
  • NS instance 2 an instance based on a second virtual network function descriptor (which may be described as VNFD 2) is required to be in the same physical area as the existing first virtual network function instance (which may be described as VNF instance 1).
  • the premise of the implementation of the embodiment of the present invention is that the NSD of the NS instance 2 and the related VNFD have been sent by the OSS/BSS to the NFVO, and the NFVO uploads the NSD and the related VNFD to the corresponding directory.
  • the embodiment of the present invention introduces a management method based on affinity information based on NS instantiation in NS lifecycle management, and other NS lifecycle management is similar to this embodiment. The method shown in Fig. 3 will be described below.
  • the OSS/BSS obtains affinity information that is used to configure affinity and/or anti-affinity between the target NS and other objects.
  • the affinity information can also be used to configure affinity and/or anti-affinity between the sub-object VNF unit of the target NS and other objects.
  • OSS/BSS is based on a need to instantiate an NS with the NS as the target NS.
  • the OSS/BSS acquires and determines affinity information for configuring affinity and/or anti-affinity between the target NS and other objects, or determines a sub-object between the VNF unit and other objects for configuring the target NS
  • affinity information required for instantiation of the target NS is obtained and determined.
  • the affinity information may include at least one of: affinity deactivation indication information; affinity constraint information, and the affinity constraint information is used to indicate affinity and/or anti-target related to the target object. a constraint of affinity; a second affinity rule, the second affinity rule comprising at least one of rule indication information, affinity object identifier, and range indication information.
  • the OSS/BSS sends an instantiation request for the target NS to the NFVO, the instantiation request carrying the affinity information described above.
  • the instantiation request may also carry the descriptor identifier of the target NS, that is, the NSD ID.
  • the OSS/BSS sends an instantiation request of the target NS to the NFVO through the OS-Ma-nfvo interface between the OSS/BSS and the NFVO on the premise that the affinity information is determined.
  • affinity information may also be preset in the NFVO.
  • affinity deactivation indication information For example, at least one of the above-described affinity deactivation indication information, second affinity rule, or affinity constraint information is preset in the NFVO.
  • the NFVO determines a plurality of VNF instance requirement information required for instantiation of the target NS based on the instantiation request of the target NS.
  • the NFVO receives an instantiation request for the target NS and determines a plurality of VNF instance requirement information required for instantiation of the target NS based on the target NSD ID.
  • the NFVO searches for the target NSD in the network according to the target NSD ID, and parses the target NSD, and analyzes multiple VNF instance requirement information under the target NSD.
  • a VNF instance requirement information includes a VNFD ID and a deployment specification corresponding to the VNFD ID.
  • NFVO or VNFM can instantiate the VNF based on a VNF instance requirement information.
  • the NFVO determines a third affinity rule for each VNF instance requirement information in the plurality of VNF instance requirement information based on the affinity information.
  • the NFVO determines a third affinity rule for each VNF instance requirement information in the plurality of VNF instance requirement information according to the affinity deactivation information.
  • the NFVO parses the affinity constraint information, and determines a third affinity rule for each VNF instance requirement information in the plurality of VNF instance requirement information according to the affinity constraint information.
  • the NFVO is configured according to the VNFD in each VNF instance requirement information in the VNF instance requirement information and/or the first affinity associated with the target NS in the NFV network architecture.
  • the rules and/or the second affinity rules described above determine a third affinity rule for each of the VNF instance requirements information, respectively.
  • NFVO finds whether there is a certain VNF in the above first affinity rule Affinity and/or anti-affinity of the instance requirement information, if present, determining affinity and/or anti-affinity of the VNF instance requirement information according to the first affinity rule; if not, then Finding and determining the affinity and/or anti-affinity of the VNF instance requirement information in the second parent rule; if the first affinity rule and the second affinity rule are unable to determine the affinity of the VNF instance requirement information For the sex and/or anti-affinity, the third affinity rule of the VNF instance requirement information is determined according to the VNFD corresponding to the VNF instance requirement information.
  • the NFVO instantiates the target NS based on the third affinity rule for each VNF instance requirement information.
  • the NFVO instantiates the target NS according to a third affinity rule for each of the VNF instance requirement information.
  • the NFVO determines a fourth affinity rule for the corresponding virtual resource based on a third affinity rule for each VNF instance requirement information.
  • the NFVO determines a fourth affinity rule for the corresponding virtual resource according to a third affinity rule of each VNF instance requirement information, eg, the NFVO converts the third affinity rule of each VNF instance requirement information into a corresponding a fourth affinity rule of the virtual resource; for example, the NFVO generates a fourth affinity rule of the corresponding virtual resource according to a third affinity rule of each VNF instance requirement information; and, for example, the NFVO is configured according to each VNF instance
  • the third affinity rule of the requirement information finds a fourth affinity rule of the corresponding virtual resource.
  • the virtual resource may be a computing resource, a network resource, a storage resource, or the like on the virtual machine. It should be noted that the same VNF instance can be deployed on multiple virtual machines, or one virtual machine can deploy multiple VNF instances.
  • the fourth affinity rule converted to the corresponding virtual resource that is, converted into an affinity rule between the virtual machines.
  • NFVO allocates virtual resources to the VIM for the instantiation request of the target NS.
  • the NFVO allocates a virtual resource to the VIM for the instantiation request of the target NS according to the fourth affinity rule of the virtual resource and the VNFD corresponding to each VNF instance requirement information, that is, requests the VIM to allocate the instantiated VNF instance. virtual machine.
  • the NFVO sends a VNF instantiation request to the VNFM, the VNF instantiation request including a VNFD ID corresponding to each VNF instance requirement information and a fourth affinity rule for each VNF instance requirement information.
  • the NFVO sends a VNF instantiation request to the VNFM, and the VNFM instantiates a plurality of VNF instances according to the VNF instantiation request, thereby implementing instantiation of the target NS.
  • the VNF instantiation request includes a VNFD ID corresponding to each VNF instance requirement information and a fourth affinity rule of each VNF instance requirement information.
  • the VNFM determines a fourth affinity rule for the corresponding virtual resource based on a third affinity rule for each VNF instance requirement information.
  • the VNFM receives the VNF instantiation request sent by the NFVO, and performs VNF instantiation according to the affinity rule of each VNF instance requirement information to instantiate multiple VNF instances.
  • the VNFM determines a fourth affinity rule of the corresponding virtual resource according to the third affinity rule of each VNF instance requirement information, that is, determines an affinity rule between the virtual machines.
  • the VNFM configures virtual resources for the instantiation request of the target NS.
  • the VNFM sends a request to the VIM according to the fourth affinity rule of the virtual resource and the VNFD corresponding to each VNF instance requirement information, to configure the virtual resource for the instantiation request of the target NS, that is, requesting the VIM to be instantiated.
  • the VNF instance allocates virtual machines.
  • 306-307 and 308-310 are two parallel schemes, and only one of them can be executed, that is, 306-307 or 308-310 is executed, and which scheme is determined by NFVO, which is not performed here. limited.
  • the affinity information is transmitted through the communication interface between the OSS/BSS and the NFVO, so as to implement effective management of the network service unit.
  • the solution of the embodiment of the present invention can implement affinity and/or anti-affinity between network elements in both the deployment phase and the maintenance phase, and the communication interface can be based on the VNF instance granularity, the NS instance granularity,
  • the affinity information of the VNF instance group granularity, the VNFD granularity, and the NSD granularity makes the affinity and/or anti-affinity between the network elements more flexible.
  • FIG. 4 shows still another method for managing affinity information according to an embodiment of the present invention.
  • the same or similar content as the method shown in FIG. 2 or FIG. 3 can be referred to the detailed description of FIG. 2 or FIG. 3, and details are not described herein.
  • the solution shown in Figure 3 can be applied to the following application scenarios: EM needs to create a VNF instance. Based on the service management requirements (for example, reliability) in the scenario, the newly created VNF instance needs to be the same as the existing one.
  • An example of a virtual network function (which can be described as VNF instance 1) is in a different physical area.
  • the premise of the implementation of the embodiment of the present invention is that the VNFD corresponding to the VNF instance has been sent to the NFVO by the OSS/BSS, and the NFVO uploads the VNFD to the corresponding directory.
  • Embodiments of the present invention are based on VNF in VNF lifecycle management Instantiation introduces the management method based on affinity information, and other VNF lifecycle management is similar to this embodiment. The method shown in Fig. 4 will be described below.
  • the EM obtains affinity information that is used to configure affinity and/or anti-affinity between the target VNF and other objects.
  • EM is based on a need to instantiate a VNF that targets the VNF.
  • the EM acquires and determines affinity information for configuring affinity and/or anti-affinity between the target VNF and other objects, in the embodiment of the invention, obtaining and determining the required for the target VNF to be instantiated Affinity information.
  • the affinity information may include at least one of: affinity deactivation indication information; affinity constraint information, the affinity constraint information is used to indicate affinity and/or anti-affinity associated with the target VNF.
  • the second affinity rule includes at least one of rule indication information, affinity object identifier, and range indication information.
  • the EM sends an instantiation request for the target VNF to the VNFM, the instantiation request carrying the affinity information described above.
  • the instantiation request may also carry a descriptor identifier of the target VNF, that is, a VNFD ID.
  • the EM sends an instantiation request of the target VNF to the VNFM through the Ve-Vnfm-em interface between the EM and the VNFM on the premise that the affinity information is determined.
  • some or all of the above affinity information may also be preset in the VNFM.
  • at least one of the above-described affinity deactivation indication information, second affinity rule, or affinity constraint information is preset in the VNFM.
  • the VNFM determines instance demand information for the target VNF based on the instantiation request of the target VNF.
  • the VNFM receives an instantiation request for the target VNF and determines target VNF instance demand information based on the target VNFDID.
  • the VNFM looks up the target VNFD in the network according to the target VNFD ID and parses the target VNFD.
  • the VNFM searches for the corresponding target NSD according to the target VNFD, and searches for the first affinity rule in the target NSD related to the target VNF.
  • the VNFM sends a query request to the NFVO requesting the NFVO to look up the first affinity rule associated with the target VNF in the target NSD.
  • the VNFM determines a third affinity rule for the target VNF instance requirement information based on the affinity information.
  • the VNFM determines a third affinity rule for the target VNF instance requirement information based on the affinity deactivation information.
  • the VNFM parses the affinity constraint information, and determines a third affinity rule of the target VNF instance requirement information according to the affinity constraint information.
  • the VNFM determines the target VNF instance requirement information according to the target VNFD and/or the first affinity rule related to the target VNF in the target NSD and/or the second affinity rule.
  • the third affinity rule determines whether there is affinity and/or anti-affinity of the target VNF instance requirement information in the first affinity rule related to the target VNF in the target NSD, and if yes, determines the target according to the first affinity rule Affinity and/or anti-affinity of the VNF instance requirement information; if not present, finding and determining the affinity and/or anti-affinity of the target VNF instance requirement information in the second affinity rule; If both the affinity rule and the second affinity rule cannot determine the affinity and/or anti-affinity of the target VNF instance requirement information, the third affinity rule of the target VNF instance requirement information is determined according to the target VNFD.
  • the VNFM instantiates the target VNF according to a third affinity rule of the target VNF instance requirement information.
  • the VNFM instantiates the target VNF according to a third affinity rule of the target VNF instance requirement information to instantiate the target VNF instance.
  • the VNFM determines a fourth affinity rule for the corresponding virtual resource based on a third affinity rule of the target VNF instance requirement information.
  • the VNFM determines a fourth affinity rule of the corresponding virtual resource according to a third affinity rule of the target VNF instance requirement information, for example, the VNFM determines a corresponding virtual resource by using a third affinity rule of the target VNF instance requirement information.
  • the fourth affinity rule for example, the VNFM searches for a fourth affinity rule of the corresponding virtual resource according to the third affinity rule of the target VNF instance requirement information.
  • the virtual resource may be a computing resource, a network resource, a storage resource, or the like on the virtual machine. It should be noted that the same VNF instance can be deployed on multiple virtual machines, or one virtual machine can deploy multiple VNF instances.
  • the fourth affinity rule converted to the corresponding virtual resource that is, converted into an affinity rule between the virtual machines.
  • the VNFM configures virtual resources for instantiation requests for the target VNF.
  • the VNFM sends a request to the VIM according to the fourth affinity rule of the virtual resource and the target VNFD to configure the virtual resource for the instantiation request of the target VNF, ie, requesting the VIM to allocate the virtual machine to the instantiated target VNF instance.
  • the VNFM sends a resource request to the NFVO, the resource request including a fourth affinity rule for the virtual resource.
  • the VNFM sends a resource request to the NFVO, the resource request including a fourth affinity rule for the virtual resource.
  • the VNFM does not directly request the virtual resource to the VIM, but requests the virtual resource to be configured by the NFVO to the VIM.
  • the NFVO configures the virtual resource to the VIM for the instantiation request of the target VNF based on the resource request.
  • the NFVO receives the resource request sent by the VNFM, and configures the virtual resource to the VIM for the instantiation request of the target VNF according to the fourth affinity rule of the virtual resource in the resource request, that is, requests the VIM as the instantiated target VNF.
  • the instance allocates a virtual machine.
  • 406-407 and 406, 408, and 409 are two parallel schemes, and only one of them may be executed, that is, 406-407 or 406, 408, and 409 are executed, and which scheme is specifically determined by the VNFM. There is no limit here.
  • the process of instantiating the VNF is taken as an example, and the affinity information is transmitted through the communication interface between the EM and the VNFM to implement effective management of the virtual network functional unit.
  • the solution of the embodiment of the present invention can implement affinity and/or anti-affinity between network elements in both the deployment phase and the maintenance phase, and the communication interface can deliver the VNF instance granularity and the VNF instance group granularity.
  • the affinity information of the VNFD granularity makes the affinity and/or anti-affinity between the network elements more flexible.
  • each network element for example, the first management unit, the second management unit, and the like, in order to implement the above functions, includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may apply to the first management unit, the second management unit, etc. according to the foregoing method example.
  • the division of the line function module for example, can divide each function module for each function, or integrate two or more functions into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 5A shows a possible structural diagram of the first management unit involved in the above embodiment.
  • the first management unit 500 includes a processing module 502 and a communication module 503.
  • the processing module 502 is configured to perform control management on the actions of the first management unit.
  • the processing module 502 is configured to support the first management unit to perform the process 203 in FIG. 2, the processes 303, 304, 305, 306, 307 in FIG. And 308, processes 403, 404, 405, 406, 407, and 408 in FIG. 4 and/or other processes for the techniques described herein.
  • the communication module 503 is for supporting communication between the first management unit and the second management unit or other network entity, such as communication with the NFVO unit or VNFM unit shown in FIG.
  • the first management unit may further include a storage module 501 for storing program codes and data of the first management unit.
  • the processing module 502 can be a processor or a controller, and can be, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 503 can be a transceiver, a transceiver circuit or a communication interface, etc., for example, can be an OS-Ma-nfvo interface or a Ve-Vnfm-em interface as described above.
  • the storage module 501 can be a memory.
  • the first management unit involved in the embodiment of the present invention may be the first management unit shown in FIG. 5B.
  • the first management unit 510 includes a processor 512, a transceiver 513, and a memory 511.
  • the first management unit 510 may further include a bus 514.
  • the transceiver 513, the processor 512, and the memory 511 may be connected to each other through a bus 514.
  • the bus 514 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (abbreviated). EISA) bus and so on.
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus 514 can be divided into an address bus, a data bus, a control bus, and the like.
  • the diagram 5B is represented by only one thick line, but does not mean that there is only one bus or one type of bus.
  • FIG. 6A shows a possible structural diagram of the second management unit involved in the above embodiment.
  • the second management unit 600 includes a processing module 602 and a communication module 603.
  • the processing module 602 is configured to perform control management on the actions of the second management unit.
  • the processing module 602 is configured to support the second management unit to perform the processes 201 and 202 in FIG. 2, the processes 301 and 302 in FIG. 3, in FIG. Processes 401 and 402 and/or other processes for the techniques described herein.
  • the communication module 603 is for supporting communication between the second management unit and the first management unit or other network entity, such as communication with the OSS/BSS unit or EM unit shown in FIG.
  • the second management unit may further include a storage module 601 for storing program codes and data of the second management unit.
  • the processing module 602 can be a processor or a controller, for example, a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and an application-specific integrated circuit (Application-Specific). Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 603 can be a transceiver, a transceiver circuit or a communication interface, etc., for example, can be an OS-Ma-nfvo interface or a Ve-Vnfm-em interface as described above.
  • the storage module 601 can be a memory.
  • the first management unit involved in the embodiment of the present invention may be the second management unit shown in FIG. 6B.
  • the first management unit 610 includes a processor 612, a transceiver 613, and a memory 611.
  • the first management unit 610 may further include a bus 614.
  • the transceiver 613, the processor 612, and the memory 611 may be connected to each other through a bus 614.
  • the bus 614 may be a peripheral component interconnection standard bus or an extended industry standard structure bus or the like.
  • the bus 614 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 6B, but it does not mean that there is only one bus or one type of bus.
  • the steps of the method or algorithm described in connection with the disclosure of the embodiments of the present invention may be implemented in a hardware manner, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM, EPROM), electrically erasable programmable Read only memory (Electrically EPROM, EEPROM), registers, hard disk, removable hard disk, read-only optical disk (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the ASIC can be located in a core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the functions described in the embodiments of the present invention may be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

一种管理方法及装置，该方法包括：第二单元获取亲和信息，该亲和信息用于配置目标对象与其他对象之间的亲和性和/或反亲和性，或者用于配置目标对象的子对象与其他对象之间的亲和性和/或反亲和性；第二管理单元向第一管理单元发送目标对象的管理请求，该管理请求携带亲和信息；第一管理单元接收第二管理单元发送的目标对象的管理请求后，根据亲和信息对目标对象进行管理。本发明实施例能够实现对网络业务单元或虚拟网络功能单元的有效管理。

Description

一种管理方法及装置 技术领域
本发明涉及通信领域，尤其涉及网络功能虚拟化(Network Function Virtualization，NFV)技术领域中的一种管理方法及装置，例如一种基于亲和信息的管理方法及装置。
背景技术
NFV技术基于海量的、归一化的服务器和交换机，通过软件实现多种网络功能(例如：虚拟运营、虚拟广域网、虚拟应用接入路由器等功能)，从而降低成本，加速业务部署、资源弹性伸缩，构建创新生态链。NFV技术中，一台计算机被虚拟为多台虚拟逻辑计算机，即虚拟机(Virtual Machine，VM)。虚拟机一般使用连接机框内交换机或者架顶交换机的服务器物理网口、虚拟网卡以及虚拟交换机，与服务器外部进行数据通信。
NFV技术通过借用信息技术(Information Technology，IT)的虚拟化技术，使得许多类型的网络设备可以合并到工业标准中，例如，使得业务、交换、存储等网络设备可以部署在数据中心或者网络节点中。NFV技术将各种网络功能以软件方式实现，并能在工业标准的服务器上运行这些网络功能，还能根据需要对这些网络功能进行迁移、实例化、以及重新部署等等，并且不需要安装新的设备。即通过NFV技术可以产生虚拟网络功能(Virtualized Network Function，VNF)。多个VNF之间可以实现网络业务(Network Service，NS)。实践中，厂商用来部署VNF的模板是虚拟网络功能描述符(Virtualized Network Function Descriptor，VNFD)，厂商用来部署NS的模板是网络业务描述符(Network Service Descriptor，NSD)，其中，一个NSD可以包括多个VNFD。
然而，现有的方案无法实现对网络业务单元或虚拟网络功能单元的有效管理。
发明内容
本发明实施例提供了一种管理方法及装置，以期实现对网络业务单元或虚拟网络功能单元的有效管理。
一方面，本发明实施例提供了一种管理方法，该方法包括：第二管理单元获取亲和信息，该亲和信息用于配置目标对象与其他对象之间的亲和性和/或 反亲和性，或者用于配置目标对象的子对象与其他对象之间的亲和性和/或反亲和性；第二管理单元向第一管理单元发送管理请求，该管理请求携带上述亲和信息；第一管理单元接收第二管理单元发送的管理请求并根据上述亲和信息对目标对象进行管理。其中，上述第一管理单元可以用于管理目标对象的虚拟资源；上述第二管理单元可以用于管理目标对象的业务。其中，该目标对象可以为网络业务单元或虚拟网络功能单元。例如，当目标对象为网络业务单元时，目标对象的子对象可以为虚拟网络功能单元。
上述第一管理单元接收携带亲和信息的管理请求后，能够根据亲和信息对目标对象进行有效管理。进一步的，本发明实施例的方案能够在管理过程的所有阶段实现网元之间的亲和性和/或反亲和性，例如，可以在管理过程中的部署阶段和维护阶段等实现网元之间的亲和性和/或反亲和性。
在一种可能的设计中，上述亲和信息包括以下情形中的至少一种：
上述亲和信息可以为亲和去激活指示信息，该亲和去激活指示信息用于指示第一管理单元在对目标对象进行管理的过程中忽略与目标对象相关的第一亲和规则。其中，该第一亲和规则可以为第一管理单元中预置的亲和规则。通过亲和去激活指示信息，可以在紧急情况下忽略与目标对象有关的第一亲和规则，能够简化第一管理网元的管理操作，从而对目标对象进行快速部署或维护，以提高管理效率。
上述亲和信息可以为第二亲和规则，该第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种。其中，该第二亲和规则可以为第二管理单元根据配置需求获取的亲和规则。
上述亲和信息可以为亲和约束信息，该亲和约束信息用于指示与目标对象相关的亲和性和/或反亲和性的约束条件。通过亲和约束信息，本发明实施例的方案可以根据性能需求或其他情况对网元进行更为精细的管理。
当亲和信息为第二亲和规则时，上述规则指示信息可以用于指示第二亲和规则为亲和性规则和/或反亲和性规则。上述亲和对象标识可以用于标识第二亲和规则的作用对象，上述亲和对象包括网络业务实例的标识、网络业务描述符的标识、虚拟网络功能实例的标识或虚拟网络功能描述符的标识中的至少一种，以便通过多种方式描述网元之间的亲和性和反亲和性。上述范围指示信息可以用于指示第二亲和规则的适用范围，例如，数据中心等。可见，本发明实施例的方案中可以通过各种方式来描述网元之间的亲和性和/或反亲和性，实施起来更为灵活。
在一种可能的设计中，第一管理单元接收第二管理单元发送的管理请求，并根据上述亲和信息对目标对象进行管理，管理的过程可以包括：根据上述亲和信息确定管理目标对象所需的管理需求信息的第三亲和规则；根据管理需求信息的第三亲和规则对所述目标对象进行部署；根据管理需求信息的第三规则确定对应的虚拟资源的第四亲和规则；根据虚拟资源的第四亲和规则为部署所述目标对象配置虚拟资源。本发明实施例的方案，通过上述过程能够基于亲和信息实现对网络业务或虚拟网络功能的有效管理。
在一种可能的设计中，上述管理请求还携带目标对象的描述符标识，为网络业务描述符的标识或虚拟网络功能描述符的标识，以便第一管理单元根据目标对象的描述符标识确定管理目标对象所需的管理需求信息。
在一种可能的设计中，上述管理请求为生命周期管理请求，通过前面所述的方法可实现对网络业务或虚拟网络功能的生命周期管理。
另一方面，本发明实施例提供了一种管理装置，该装置可以实现上述方法实例中第一管理单元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中，该装置的结构中包括处理器和收发器，该处理器被配置为支持该装置执行上述方法中相应的功能。该收发器用于支持该装置与其他网元之间的通信。该装置还可以包括存储器，该存储器用于与处理器耦合，其保存该装置必要的程序指令和数据。
又一方面，本发明实施例提供了一种管理装置，该装置可以实现上述方法实例中第二管理单元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。
在一种可能的设计中，该装置的结构中包括处理器和收发器，该处理器被配置为支持该装置执行上述方法中相应的功能。该收发器用于支持该装置与其他网元之间的通信。该装置还可以包括存储器，该存储器用于与处理器耦合，其保存该装置必要的程序指令和数据。
又一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的可以实现第一管理单元的功能的装置和可以实现第二管理单元的功能的装置。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述第 一管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述第二管理单元所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
相较于现有技术，本发明实施例提供的方案中，通过第二管理单元获取亲和信息，并向第一管理单元发送携带亲和信息的管理请求；第二管理单元接收第一管理单元发送的管理请求后，根据管理请求携带的亲和信息对目标对象进行管理，从而实现对网络业务单元或虚拟网络功能单元的有效管理。进一步的，本发明实施例的方案能够在管理的所有阶段实现网元之间的亲和性和/或反亲和性，并通过多种方式描述网元之间的亲和性和/或反亲和性，使得网元之间的亲和性和/或反亲和性的实现更加灵活。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种可能的网络架构示意图；
图2为本发明实施例提供的一种管理方法的通信示意图；
图3为本发明实施例提供的另一种管理方法的通信示意图；
图4为本发明实施例提供的又一种管理方法的通信示意图；
图5A为本发明实施例提供的一种第一管理单元的结构示意图；
图5B为本发明实施例提供的另一种第一管理单元的结构示意图；
图6A为本发明实施例提供的一种第二管理单元的结构示意图；
图6B为本发明实施例提供的另一种第二管理单元的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施 例提供的技术方案对于类似的技术问题，同样适用。
如图1所示，基于NFV的网络架构主要包括：运营支撑系统(Operation Support System，OSS)/业务支撑系统(Business Support System，BSS)、网元管理(Element Manager，EM)单元、虚拟化网络功能(VNF)单元、网络功能虚拟化基础设施(NFV Infrastructure，NFVI)单元、网络功能虚拟化调度(NFV Orchestrator，NFVO)单元、虚拟化网络功能管理(VNF Manager，VNFM)单元和虚拟化基础设施管理(Virtualised Infrastructure Manager，VIM)单元。需要说明的是，在下文中，可以各用单元的英文缩写来描述对应单元，例如网元管理单元可以描述为EM或EM单元。下面对上述单元做简单介绍：
OSS/BSS是电信运营商的一体化、信息资源共享的支持系统，其主要由网络管理、系统管理、计费、营业、账务和客户业务等部分组成，而系统间则通过统一的信息总线有机整合在一起。OSS/BSS能在帮助运营商制订符合自身特点的运营支撑系统的同时帮助确定系统的发展方向，还能帮助用户制订系统的整合标准，改善和提高用户的业务水平。OSS/BSS在基于NFV的网络架构中用于对各个网元的生命周期管理(例如实例化等)进行必要的修改和调整。
EM单元用于对部分VNF单元进行管理。
NFVI单元为具有部署网络功能虚拟化的能力的环境中的所有硬件设备与软件组件的统称。NFVI单元可以跨越若干个物理站点(例如：数据中心运营场所)进行扩展部署，此时，为这些物理站点提供数据连接的网络也认为是NFVI单元的一部分。
NFVO单元可用于管理NS的生命周期，并协调NS的生命周期管理、协调VNF的生命周期管理(需要得到VNFM的支持)、协调NFVI单元各类资源的管理(需要得到VIM的支持)，从而确保所需各类资源与连接的优化配置。其中，生命周期管理，是指对VNF单元或NS单元等的实例化、维护以及终结进行管理。
VNFM单元负责VNF的生命周期管理。
VIM单元负责对NFVI单元的计算资源、存储资源以及网络资源进行控制与管理。VIM可被部署于基础网络运营商的基础设施域(例如：NFVI接入点/服务提供点)。
上述图1所示的网络架构可以包括第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)系统的部分和网络功能虚拟化管理调度(NFV Management and Orchestration，NFV MANO)系统的部分。其中，3GPP系统 的部分主要包括图1所示的OSS/BSS和EM单元，NFV MANO(也可以简称为MANO)系统的部分主要包括图1所示的NFVO单元、VNFM单元和VIM单元。3GPP系统的部分与MANO系统的部分之间可建立信息交互。3GPP系统的部分与MANO系统的部分之间存在两个通信接口，一个为OSS/BSS与NFVO单元之间的接口，该接口可称为OS-Ma-nfvo接口，未在图1中标明；另一个为EM单元与VNFM单元之间的接口，该接口可称为Ve-Vnfm-em接口，未在图1中标明。通过这两个通信接口，可实现3GPP系统的部分与MANO系统的部分之间的信息交互。
下面将基于上面所述的本发明实施例涉及的共性方面，对本发明实施例进一步详细说明。
基于业务的可靠性、低损耗等管理，网元(Network Element，NE)之间存在某种亲和性和/或反亲和性。通常，若同一个物理机上可以有多个虚拟机，则称这些虚拟机具有亲和性；而两两都不在同一物理机上的多个虚拟机则具有反亲和性。在NFV技术领域，亲和性和反亲和性也可以引申理解为：若多个VNF单元可以存在于同一个区域(例如数据中心等)中，则称这些VNF单元之间具有亲和性；若多个VNF单元不可以存在于同一个区域中，则称这些VNF单元之间具有反亲和性。例如，低损耗要求存在交互的网元部署在同一个或相近的物理区域，即存在交互的网元之间具有亲和性；又例如，高可用性要求主网元与备用网元不可以部署在同一个物理区域，即主网元与备用网元之间具有反亲和性。
在对NE进行管理的过程中，需要实现NE之间的亲和性和/或反亲和性。目前，NSD或VNFD中包含用于描述NE之间的亲和性和/或反亲和性的信息。但利用该信息仅能够在NE的部署阶段实现NE之间的亲和性和/或反亲和性，却无法在其他管理阶段实现NE之间的亲和性和/或反亲和性。可见现有技术中缺乏在NE的管理过程中的所有阶段实现NE之间的亲和性和/或反亲和性的可行方案。
在传统的网络架构中，网元为软硬一体机，网元之间的亲和性和/或反亲和性在3GPP系统内部即可实现。而在基于NFV的网络架构中，软硬件分离，网元的业务方面的相关信息由3GPP系统的部分进行管理，网元的资源方面的相关信息由MANO系统的部分进行管理，为了实现网元之间的亲和性和/或反亲和性，3GPP系统的部分与MANO系统的部分之间需要建立有关亲和性和/或反亲和性的信息的交互。其中，在基于NFV的网络架构中，传统网元虚拟 为具有相应功能的VNF单元。
基于此，本发明的一个实施例提供一种管理方法，和基于这个方法的装置和系统，以期对网络业务单元或虚拟网络功能单元实现有效管理。在该方法中，第二管理单元向第一管理单元发送目标对象的管理请求，该管理请求中携带亲和信息，该亲和信息用于配置目标对象与其他对象之间的亲和性和/或反亲和性，或者用于配置目标对象的子对象与其他对象之间的亲和性和/或反亲和性；第一管理单元根据该亲和信息对目标对象进行管理。进一步的，可以通过多种方式描述目标对象与其他对象之间的亲和性和/或反亲和性，以及目标对象的子对象与其他对象之间的亲和性和/或反亲和性，使得网元之间的亲和性和/或反亲和性的实现更加灵活。其中，上述目标对象可以为NS单元或VNF单元。例如，当目标对象为NS单元时，NS的子对象为VNF单元。需要说明的是，上述第一管理单元为接收管理请求的一端，例如可以为图1中的NFVO单元或VNFM单元；上述第二管理单元为发送管理请求的一端，例如可以为图1中的OSS/BSS或EM单元。其中，上述第一管理单元可以用于管理目标对象的虚拟资源，上述第二管理单元可以用于管理目标对象的业务。
本发明实施例的方案可以应用于图1所示的基于NFV的网络架构，通过本发明实施例的方案可以在3GPP系统的部分和MANO系统的部分之间实现亲和信息的交互，从而有效管理目标对象。进一步的，本发明实施例提供的方案能够在管理的所有阶段实现不同网元之间的亲和性和/或反亲和性。
下面结合附图2～图4对本发明实施例提供的方案进行说明。
图2示出了本发明实施例提供的一种基于亲和信息的管理方法。图2所示的方法可以应用于图1所示的网络架构，其中，第一管理单元可以为NFVO单元，第二管理单元可以为OSS/BSS，第一管理单元与第二管理单元之间可以通过OS-Ma-nfvo接口进行通信；或者，第一管理单元可以为VNFM单元，第二管理单元可以为EM单元，第一管理单元与第二管理单元之间可以通过Ve-Vnfm-em接口进行通信。
在201部分，第二管理单元获取亲和信息，该亲和信息用于配置目标对象与其他对象之间的亲和性和/或反亲和性，或者用于配置目标对象的子对象与其他对象之间的亲和性和/或反亲和性。
可以理解的是，此处对于亲和信息的定义并不排除亲和信息既用于配置目标对象与其他对象之间的亲和性和/或反亲和性，又用于配置目标对象的子对象与其他对象之间的亲和性和/或反亲和性的情况。
在一个示例中，第二管理单元获取亲和信息之前，还确定所需管理的目标对象。其中，该目标对象可以为NS单元或VNF单元。例如，在基于NFV的网络架构中，存在多个NS单元和多个VNF单元，第二管理单元可以在多个NS单元中确定某个NS单元为上述目标对象，也可以在多个VNF单元中确定某个VNF单元为上述目标对象。在一种可能的实现方式中，第二管理单元可以先确定目标对象为NS单元还是VNF单元；当确定为NS单元时，第二管理单元再在多个NS单元中确定某个NS单元为目标对象；或者，当确定为VNF单元时，第二管理单元再在多个VNF单元中确定某个VNF单元为目标对象。需要说明的是，本发明实施例不限定上述第二管理单元确定所需管理的目标对象的实施过程，该实施过程可以视具体情况而定，例如可以依据应用场景或3GPP系统的需求来确定。
在一个示例中，上述亲和信息可以包括以下至少一种：亲和去激活指示信息；亲和约束信息，亲和约束信息用于指示与目标对象相关的亲和性和/或反亲和性的约束条件；第二亲和规则，该第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种。
在一种可能的实现方式中，亲和信息包括上述亲和去激活指示信息，该亲和去激活指示信息用于指示第一管理单元在对目标对象进行管理的过程中忽略与目标对象相关的第一亲和规则。例如，该第一亲和规则规定了与目标对象具有亲和性和/或反亲和性的对象，忽略与目标对象相关的第一亲和规则即可以理解为忽略与目标对象具有亲和性和/或反亲和性的对象。下面以一个具体的例子进行说明：上述目标对象可以为第一虚拟网络功能单元(可描述为VNF1)，上述与目标对象相关的第一亲和规则可以为：VNF 1与第二虚拟网络功能单元(可描述为VNF 2)具有亲和性，VNF 1与第三虚拟网络功能单元(可描述为VNF 3)具有反亲和性。假设由于自然灾害等特殊情况，VNF 1出现了故障，现需要快速部署一个虚拟网络功能实例来代替VNF 1以保证业务。此时，第二管理单元决定不需要考虑任何与VNF 1相关的亲和性和反亲和性，那么此处亲和去激活指示信息可以用于指示第一管理单元忽略与VNF 1相关的第一亲和规则，即忽略VNF1与VNF 2的亲和性以及VNF1与VNF 3的反亲和性。本发明实施例的方案中，通过亲和去激活指示信息，可以在紧急情况下忽略与目标对象有关的第一亲和规则，能够简化第一管理网元的管理操作，从而对目标对象进行快速部署或维护，以提高管理效率。可以理解的是，当亲和信息为去激活指示信息时，亲和信息可以使得第一管理单元将上述第一亲和规则 配置为失效或处于去激活的状态。
在一种可能实现的方式中，亲和信息包括上述亲和约束信息，该亲和约束信息用于指示与所述目标对象相关的亲和性和/或反亲和性的约束条件，所述约束条件可以为可靠性程度、延时长度等。例如，所述第二管理单元要求基于第一虚拟网络功能描述符(可描述为VNFD1)的第一虚拟网络功能实例(可描述为VNF实例1)、第二虚拟网络功能实例(可描述为VNF实例2)、第三虚拟网络功能实例(可描述为VNF实例3)以及第四虚拟网络功能实例(可描述为VNF实例4)之间的可靠性最高，那么所述亲和约束信息可以用于指示VNF实例1、VNF实例2、VNF实例3以及VNF实例4需要尽可能部署在不同的物理区域或数据中心。通过亲和约束信息，本发明实施例的方案可以根据性能需求或其他情况对网元进行更为精细的管理。
在一种可能实现的方式中，亲和信息为第二亲和规则，该第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种。其中，规则指示信息可以用于指示第二亲和规则为亲和性规则和/或反亲和性规则。亲和对象标识可以用于指示第二亲和规则的作用对象，例如可以理解为：亲和对象标识可以指示哪些对象之间具有亲和性和/或反亲和性，或者，亲和对象标识可以指示哪些对象需要受亲和性和/或反亲和性的约束。亲和对象标识可以包括亲和对象的实例的标识和/或亲和对象的描述符的标识，例如亲和对象标识可以包括网络业务实例的标识、网络业务描述符的标识、虚拟网络功能实例的标识或虚拟网络功能描述符的标识中的至少一种。需要说明的是，亲和对象可以是上述目标对象，也可以是与目标对象相关的单元，还可以是其它单元。例如，当目标对象为NS单元时，亲和对象可以是该NS单元，也可以是与该NS单元相关的VNF单元，还可以是其它单元。例如，若目标对象为NS单元，则亲和对象标识可以包括网络业务实例的标识、网络业务描述符的标识、虚拟网络功能实例的标识或虚拟网络功能描述符的标识中的至少一种。又例如，若目标对象为VNF单元，则亲和对象标识包括虚拟网络功能实例的标识和/或虚拟网络功能描述符的标识。上述范围指示信息可以用于指示第二亲和规则的适用范围，例如，该适用范围可以为物理区域、数据中心等。
目前，可以通过NSD或VNFD中包含的VNFD来描述网元之间的亲和性和反亲和性，可以理解的是，通过VNFD的标识符来表示受亲和性和反亲和性约束的所有实例的VNFD或虚拟链路描述符(Virtual Link Descriptor，VLD)标识符，现有技术中仅能基于VNFD的粒度描述网元之间的亲和性和/或反亲 和性，具有一定的局限性。而由上所述可知，本发明实施例的方案中，亲和信息既可以基于VNFD的粒度或NSD的粒度，也可以基于NS实例的粒度或VNF实例的粒度，因此，本发明实施例的方案中可以通过各种方式来描述网元之间的亲和性和/或反亲和性，实施起来更为灵活。
在202部分，第二管理单元向第一管理单元发送管理请求，该管理请求携带上述亲和信息。
其中，该管理请求中还可以携带目标对象的描述符的标识，例如，目标对象的描述符的标识可以为网络业务描述符的标识或虚拟网络功能描述符的标识。
在一个示例中，第二管理单元可以通过第一管理单元与第二管理单元之间的通信接口向第一管理单元发送管理请求。例如，第一管理单元与第二管理单元之间的通信接口可以为OS-Ma-nfvo接口或Ve-Vnfm-em接口。
在一个示例中，该管理请求可以为生命周期管理请求，该生命周期管理请求可以用于上述目标对象的生命周期管理；或者，该管理请求也可以为其它类型的管理请求。
在一个示例中，上述亲和信息中的部分或全部也可以是预置在第一管理单元中的。例如，上述亲和去激活指示信息、第二亲和规则或亲和约束信息中的至少一种预置在第一管理单元中。
在203部分，第一管理单元接收第二管理单元发送的管理请求并根据上述亲和信息对目标对象进行管理。
在一个示例中，第一管理单元根据亲和信息对目标对象进行管理的过程可以包括以下四个部分：
第一部分：第一管理单元根据亲和信息确定管理上述目标对象所需的管理需求信息的第三亲和规则。在一种可能的实现方式中，该亲和信息可以包括目标对象的描述符的标识，第一部分可以包括以下两个步骤：
(1)：第一管理单元根据目标对象的描述符标识查找目标对象的描述符，并解析目标对象的描述符，确定管理目标对象所需的管理需求信息。若目标对象为NS，则根据该NS的NSD ID查找对应的NSD，并对该NSD进行解析。由于每个NSD包括多个VNFD，所以对该NSD解析的过程即为分析该NSD下有哪些VNFD与部署规格的组合。根据解析结果确定管理NS所需的管理需求信息，NS的管理需求信息包括多个VNF实例需求信息，一个VNF实例需求信息包括一个VNFD ID以及该VNFD ID对应的部署规格。若目标对象为 VNF，则根据该VNF的VNFD ID查找对应的VNFD，并对该VNFD进行解析，确定该VNF的实例需求信息。
(2)：第一管理单元根据亲和信息确定管理需求信息的第三亲和规则。若目标对象为NS，则根据多个VNF实例需求信息中的每个VNF实例需求信息中的VNFD和/或NFV网络架构中该NS对应的NSD中的亲和规则和/或亲和信息分别确定每个VNF实例需求信息的亲和规则，即分别确定与每个VNF实例需求信息具有亲和性和/或反亲和性的对象。若目标对象为VNF，则根据该VNF对应的VNFD和/或NSD中与该VNFD相关的亲和规则确定该VNF实例需求信息的亲和规则，即确定与该VNF实例需求信息具有亲和性和/或反亲和性的对象。
第二部分：第一管理单元根据管理需求信息的第三亲和规则对目标对象进行部署。例如，若目标对象为NS，则根据每个VNF实例需求信息的亲和规则部署或请求VNF实例化；若目标对象为VNF，则根据该VNF实例需求信息的亲和规则实例化该VNF。
第三部分：第一管理单元根据管理需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则。例如，第一管理单元将管理需求信息的第三亲和规则转换为对应的虚拟资源的第四亲和规则；又例如，第一管理单元根据管理需求信息的第三亲和规则生成对应的虚拟资源的第四亲和规则；又例如，第一管理单元可以根据管理需求信息的第三亲和规则查找对应的虚拟资源的第四亲和规则。其中，上述虚拟资源可以为虚拟机上的计算资源、网络资源、存储资源等。需要说明的是，同一VNF实例可部署在多个虚拟机上，或者，一个虚拟机上也可部署多个VNF实例。因此，当亲和对象为VNF实例时，上述将管理需求信息的第三亲和规则转换为对应的虚拟资源的第四亲和规则，可以理解为将亲和对象之间的亲和规则转换为存储VNF实例的虚拟机之间的亲和规则。例如，若VNF实例1与VNF实例2具有反亲和性，且VNF实例1对应的虚拟机为VM1，VNF实例2对应的虚拟机为VM2，则将VNF实例1与VNF实例2之间的第三亲和规则转换为虚拟机1与虚拟机2之间的第四亲和规则，即使得虚拟机1与虚拟机2之间也具有反亲和性。
第四部分：第一管理单元根据虚拟资源的第四亲和规则为部署目标对象配置虚拟资源。作为示例，当目标对象为VNF实例时，为部署目标对象配置虚拟资源，可以理解为确定已实例化的VNF实例存在于哪个虚拟机上，使用虚拟机上的哪些资源。例如，虚拟资源的第四亲和规则为虚拟机1与虚拟机2 之间具有反亲和性，则根据虚拟机1与虚拟机2之间的反亲和性为部署VNF实例1和VNF实例2分别请求配置虚拟资源。
在本发明实施例中，第二管理单元获取亲和信息，该亲和信息用于配置目标对象与其他子对象之间的亲和性和/或反亲和性，或者用于配置目标对象的子对象与其他子对象之间的亲和性和/或反亲和性；第二管理单元向第一管理单元发送携带该亲和信息的管理请求；第二管理单元根据管理请求中的亲和信息对目标对象进行管理，从而实现对网络业务单元或虚拟网络功能单元的有效管理。进一步的，本发明实施例的方案能够在管理的所有阶段实现网元之间的亲和性和/或反亲和性，并通过多种方式描述网元之间的亲和性和/或反亲和性，使得网元之间的亲和性和/或反亲和性的实现更加灵活。
图3示出了本发明实施例提供的另一种基于亲和信息的管理方法。图3所示的方法中，与图2所示的方法相同或相似的内容可以参考图2有关的详细描述，此处不作赘述。需要说明的是，图3所示的方案可以适用于以下应用场景：OSS/BSS需创建一个NS实例2，基于该场景下的业务管理需求(例如，业务延时、低损耗)，在新建的NS实例2中，要求基于第二虚拟网络功能描述符(可描述为VNFD 2)的实例要与已存在的第一虚拟网络功能实例(可描述为VNF实例1)在同一个物理区域。本发明实施例实施的前提条件是创建该NS实例2的NSD以及相关的VNFD已经由OSS/BSS发送至NFVO，NFVO将该NSD以及相关的VNFD上传至对应的目录中。本发明实施例基于NS生命周期管理中的NS实例化对基于亲和信息的管理方法进行介绍，其它NS生命周期管理与本实施例类似。下面对图3所示的方法进行说明。
在301部分，OSS/BSS获取亲和信息，该亲和信息用于配置目标NS与其他对象之间的亲和性和/或反亲和性。
在一个示例中，该亲和信息还可以用于配置目标NS的子对象VNF单元与其他对象之间的亲和性和/或反亲和性。
在一个示例中，OSS/BSS基于需求考虑，需要实例化一个NS，将该NS作为目标NS。OSS/BSS获取并确定用于配置目标NS与其他对象之间的亲和性和/或反亲和性的亲和信息，或确定用于配置目标NS的子对象VNF单元与其他对象之间的亲和性和/或反亲和性的亲和信息，在本发明实施例中，获取并确定用于目标NS进行实例化所需的亲和信息。
在一个示例中，上述亲和信息可以包括以下至少一种：亲和去激活指示信息；亲和约束信息，亲和约束信息用于指示与目标对象相关的亲和性和/或反 亲和性的约束条件；第二亲和规则，该第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种。其中，上述亲和去激活指示信息、亲和约束信息、第二亲和规则的详细介绍可以参考图2所示方法中的对应描述，此处不作赘述。
在302部分，OSS/BSS向NFVO发送目标NS的实例化请求，该实例化请求携带上述亲和信息。
其中，该实例化请求还可以携带目标NS的描述符标识，即NSD ID。
在一个示例中，OSS/BSS在确定好上述亲和信息的前提下，通过OSS/BSS与NFVO之间的OS-Ma-nfvo接口向NFVO发送目标NS的实例化请求。
在一个示例中，上述亲和信息中的部分或全部也可以是预置在NFVO中的。例如，上述亲和去激活指示信息、第二亲和规则或亲和约束信息中的至少一种预置在NFVO中。
在303部分，NFVO根据目标NS的实例化请求确定目标NS的实例化所需的多个VNF实例需求信息。
在一个示例中，NFVO接收目标NS的实例化请求，并根据目标NSD ID确定目标NS的实例化所需的多个VNF实例需求信息。NFVO根据所述目标NSD ID在网络中查找目标NSD，并对所述目标NSD进行解析，分析所述目标NSD下的多个VNF实例需求信息。一个VNF实例需求信息包括一个VNFD ID以及该VNFD ID对应的部署规格。NFVO或VNFM可根据某个VNF实例需求信息对该VNF进行实例化。
在304部分，NFVO根据亲和信息确定多个VNF实例需求信息中每个VNF实例需求信息的第三亲和规则。
在一个示例中，若亲和信息为上述亲和去激活信息，则NFVO根据该亲和去激活信息确定多个VNF实例需求信息中每个VNF实例需求信息的第三亲和规则。
若亲和信息为上述亲和约束信息，则NFVO解析该亲和约束信息，并根据该亲和约束信息确定所述多个VNF实例需求信息中每个VNF实例需求信息的第三亲和规则。
若亲和信息为上述第二亲和规则，则NFVO根据所述多个VNF实例需求信息中的每个VNF实例需求信息中的VNFD和/或NFV网络架构中与目标NS相关的第一亲和规则和/或上述第二亲和规则分别确定所述每个VNF实例需求信息的第三亲和规则。NFVO在上述第一亲和规则中查找是否存在某个VNF 实例需求信息的亲和性和/或反亲和性，若存在则根据上述第一亲和规则确定该VNF实例需求信息的亲和性和/或反亲和性；若不存在则在上述第二亲和规则中查找并确定该VNF实例需求信息的亲和性和/或反亲和性；若上述第一亲和规则和上述第二亲和规则均无法确定该VNF实例需求信息的亲和性和/或反亲和性，则根据该VNF实例需求信息对应的VNFD确定该VNF实例需求信息的第三亲和规则。若根据上述第一亲和规则确定的某个VNF实例需求信息的第三亲和规则与根据上述第二亲和规则确定的该VNF实例需求信息的第三亲和规则发生冲突，则优先考虑根据上述第二亲和规则确定的该VNF实例需求信息的第三亲和规则，或者请求OSS/BSS决定使用哪个亲和规则。
在305部分，NFVO根据所述每个VNF实例需求信息的第三亲和规则对目标NS进行实例化。
在一个示例中，在确定所述每个VNF实例需求信息的第三亲和规则的情况下，NFVO根据所述每个VNF实例需求信息的第三亲和规则对目标NS进行实例化。
在306部分，NFVO根据每个VNF实例需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则。
在一个示例中，NFVO根据每个VNF实例需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则，例如，NFVO将每个VNF实例需求信息的第三亲和规则转换为对应的虚拟资源的第四亲和规则；又例如，NFVO根据每个VNF实例需求信息的第三亲和规则生成对应的虚拟资源的第四亲和规则；又例如，NFVO根据所述每个VNF实例需求信息的第三亲和规则查找对应的虚拟资源的第四亲和规则。其中，上述虚拟资源可以为虚拟机上的计算资源、网络资源、存储资源等。需要说明的是，同一VNF实例可部署在多个虚拟机上，或者，一个虚拟机可部署多个VNF实例。转换为对应的虚拟资源的第四亲和规则，即转换为虚拟机之间的亲和规则。
在307部分，NFVO向VIM为目标NS的实例化请求配置虚拟资源。
在一个示例中，NFVO根据虚拟资源的第四亲和规则以及所述每个VNF实例需求信息对应的VNFD向VIM为目标NS的实例化请求配置虚拟资源，即请求VIM为实例化的VNF实例分配虚拟机。
在308部分，NFVO向VNFM发送VNF实例化请求，该VNF实例化请求包括每个VNF实例需求信息对应的VNFD ID以及所述每个VNF实例需求信息的第四亲和规则。
在一个示例中，NFVO向VNFM发送VNF实例化请求，由VNFM根据该VNF实例化请求实例化出多个VNF实例，从而实现目标NS的实例化。该VNF实例化请求包括每个VNF实例需求信息对应的VNFD ID以及所述每个VNF实例需求信息的第四亲和规则。
在309部分，VNFM根据每个VNF实例需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则。
在一个示例中，VNFM接收NFVO发送的VNF实例化请求，并根据每个VNF实例需求信息的亲和规则进行VNF实例化，实例化出多个VNF实例。在进行VNF实例化的过程中，VNFM根据所述每个VNF实例需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则，即确定虚拟机之间的亲和规则。
在310部分，VNFM为目标NS的实例化请求配置虚拟资源。
在一个示例中，VNFM根据虚拟资源的第四亲和规则以及所述每个VNF实例需求信息对应的VNFD向VIM发送请求，以为目标NS的实例化请求配置虚拟资源，即请求VIM为实例化的VNF实例分配虚拟机。
需要说明的是，306～307与308～310为两个并行的方案，只需执行其中一个即可，即执行306～307或执行308～310，具体执行哪个方案由NFVO决定，在此不做限定。
在本发明实施例中，以NS实例化的过程为例，通过OSS/BSS与NFVO之间的通信接口传递亲和信息，实现对网络业务单元的有效管理。进一步的，本发明实施例的方案能够在部署阶段和维护阶段都能够实现网元之间的亲和性和/或反亲和性，并且该通信接口可以传递基于VNF实例粒度、NS实例粒度、VNF实例组粒度、VNFD粒度、NSD粒度的亲和信息，使得网元之间的亲和性和/或反亲和性实现更加灵活。
图4示出了本发明实施例提供的又一种基于亲和信息的管理方法。图3所示的方法中，与图2或图3所示的方法相同或相似的内容可以参考图2或图3有关的详细描述，此处不作赘述。需要说明的是，图3所示的方案可以适用于以下应用场景：EM需创建一个VNF实例，基于该场景下的业务管理需求(例如，可靠性)，新建的VNF实例需要与已存在的第一虚拟网络功能示例(可描述为VNF实例1)在不同的物理区域。本发明实施例实施的前提条件是实现该VNF实例对应的VNFD已经由OSS/BSS发送至NFVO，NFVO将该VNFD上传至对应的目录中。本发明实施例基于VNF生命周期管理中的VNF 实例化对基于亲和信息的管理方法进行介绍，其它VNF生命周期管理与本实施例类似。下面对图4所示的方法进行说明。
在401部分，EM获取亲和信息，该亲和信息用于配置目标VNF与其他对象之间的亲和性和/或反亲和性。
在一个示例中，EM基于需求考虑，需要实例化一个VNF，将该VNF作为目标VNF。EM获取并确定用于配置目标VNF与其他对象之间的亲和性和/或反亲和性的亲和信息，在本发明实施例中，获取并确定用于目标VNF进行实例化所需的亲和信息。
在一个示例中，上述亲和信息可以包括以下至少一种：亲和去激活指示信息；亲和约束信息，亲和约束信息用于指示与目标VNF相关的亲和性和/或反亲和性的约束条件；第二亲和规则，该第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种。其中，上述亲和去激活指示信息、亲和约束信息、第二亲和规则的详细介绍可以参考图2所示方法中的对应描述，此处不作赘述。
在402部分，EM向VNFM发送目标VNF的实例化请求，该实例化请求携带上述亲和信息。
其中，该实例化请求还可以携带目标VNF的描述符标识，即VNFD ID。
在一个示例中，EM在确定好上述亲和信息的前提下，通过EM与VNFM之间的Ve-Vnfm-em接口向VNFM发送目标VNF的实例化请求。
在一个示例中，上述亲和信息中的部分或全部也可以是预置在VNFM中的。例如，上述亲和去激活指示信息、第二亲和规则或亲和约束信息中的至少一种预置在VNFM中。
在403部分，VNFM根据目标VNF的实例化请求确定目标VNF的实例需求信息。
在一个示例，VNFM接收目标VNF的实例化请求，并根据目标VNFDID确定目标VNF实例需求信息。VNFM根据目标VNFD ID在网络中查找目标VNFD，并对目标VNFD进行解析。同时VNFM根据目标VNFD查找对应的目标NSD，并查找目标NSD中与目标VNF相关的第一亲和规则。VNFM向NFVO发送查询请求，请求NFVO查找目标NSD中与目标VNF相关的第一亲和规则。
在404部分，VNFM根据亲和信息确定目标VNF实例需求信息的第三亲和规则。
在一个示例中，若亲和信息为上述亲和去激活信息，则VNFM根据该亲和去激活信息确定目标VNF实例需求信息的第三亲和规则。
若亲和信息为上述亲和约束信息，则VNFM解析该亲和约束信息，并根据该亲和约束信息确定目标VNF实例需求信息的第三亲和规则。
若亲和信息为上述第二亲和规则，则VNFM根据目标VNFD和/或所述目标NSD中与目标VNF相关的第一亲和规则和/或上述第二亲和规则确定目标VNF实例需求信息的第三亲和规则。VNFM确定在所述目标NSD中的与目标VNF相关的第一亲和规则中是否存在目标VNF实例需求信息的亲和性和/或反亲和性，若存在则根据第一亲和规则确定目标VNF实例需求信息的亲和性和/或反亲和性；若不存在则在上述第二亲和规则中查找并确定目标VNF实例需求信息的亲和性和/或反亲和性；若第一亲和规则和上述第二亲和规则均无法确定目标VNF实例需求信息的亲和性和/或反亲和性，则根据目标VNFD确定目标VNF实例需求信息的第三亲和规则。若根据第一亲和规则确定的目标VNF实例需求信息的第三亲和规则与根据上述第二亲和规则确定的目标VNF实例需求信息的第三亲和规则发生冲突，则优先考虑根据上述第二亲和规则确定的所述目标VNF实例需求信息的第三亲和规则，或者请求OSS/BSS决定使用哪个亲和规则。
在405部分，VNFM根据目标VNF实例需求信息的第三亲和规则对目标VNF进行实例化。
在一个示例中，在确定目标VNF实例需求信息的第三亲和规则的情况下，VNFM根据目标VNF实例需求信息的第三亲和规则对目标VNF进行实例化，以实例化目标VNF实例。
在406部分，VNFM根据目标VNF实例需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则。
在一个示例中，VNFM根据目标VNF实例需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则，例如，VNFM将目标VNF实例需求信息的第三亲和规则确定对应的虚拟资源的第四亲和规则；又例如，VNFM根据目标VNF实例需求信息的第三亲和规则查找对应的虚拟资源的第四亲和规则。其中，上述虚拟资源可以为虚拟机上的计算资源、网络资源、存储资源等。需要说明的是，同一VNF实例可部署在多个虚拟机上，或者，一个虚拟机可部署多个VNF实例。转换为对应的虚拟资源的第四亲和规则，即转换为虚拟机之间的亲和规则。
在407部分，VNFM为目标VNF的实例化请求配置虚拟资源。
在一个示例中，VNFM根据虚拟资源的第四亲和规则以及目标VNFD向VIM发送请求，以为目标VNF的实例化请求配置虚拟资源，即请求VIM为实例化的目标VNF实例分配虚拟机。
在408部分，VNFM向NFVO发送资源请求，该资源请求包括虚拟资源的第四亲和规则。
在一个示例中，VNFM向NFVO发送资源请求，该资源请求包括虚拟资源的第四亲和规则。在该步骤中，VNFM不直接向VIM请求配置虚拟资源，而是通过NFVO向VIM请求配置虚拟资源。
在409部分，NFVO根据资源请求向VIM为目标VNF的实例化请求配置虚拟资源。
在一个示例中，NFVO接收VNFM发送的资源请求，并根据该资源请求中的虚拟资源的第四亲和规则向VIM为目标VNF的实例化请求配置虚拟资源，即请求VIM为实例化的目标VNF实例分配虚拟机。
需要说明的是，406～407与406、408、409为两个并行的方案，只需执行其中一个即可，即执行406～407或执行406、408、409，具体执行哪个方案由VNFM决定，在此不做限定。
在本发明实施例中，以VNF实例化的过程为例，通过EM与VNFM之间的通信接口传递亲和信息，实现对虚拟网络功能单元的有效管理。进一步的，本发明实施例的方案能够在部署阶段和维护阶段都能够实现网元之间的亲和性和/或反亲和性，并且该通信接口可以传递基于VNF实例粒度、VNF实例组粒度、VNFD粒度的亲和信息，使得网元之间的亲和性和/或反亲和性实现更加灵活。
上述主要从各个网元之间交互的角度对本发明实施例的方案进行了介绍。可以理解的是，各个网元，例如第一管理单元，第二管理单元等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对第一管理单元，第二管理单元等进 行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的模块的情况下，图5A示出了上述实施例中所涉及的第一管理单元的一种可能的结构示意图。第一管理单元500包括：处理模块502和通信模块503。处理模块502用于对第一管理单元的动作进行控制管理，例如，处理模块502用于支持第一管理单元执行图2中的过程203，图3中的过程303、304、305、306、307和308，图4中的过程403、404、405、406、407和408和/或用于本文所描述的技术的其它过程。通信模块503用于支持第一管理单元与第二管理单元或其他网络实体的通信，例如与图1中示出的NFVO单元或VNFM单元等之间的通信。第一管理单元还可以包括存储模块501，用于存储第一管理单元的程序代码和数据。
其中，处理模块502可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块503可以是收发器、收发电路或通信接口等，例如，可以是上文中所述的OS-Ma-nfvo接口或Ve-Vnfm-em接口。存储模块501可以是存储器。
当处理模块502为处理器，通信模块503为收发器，存储模块501为存储器时，本发明实施例所涉及的第一管理单元可以为图5B所示的第一管理单元。
参阅图5B所示，该第一管理单元510包括：处理器512、收发器513、存储器511。可选的，第一管理单元510还可以包括总线514。其中，收发器513、处理器512以及存储器511可以通过总线514相互连接；总线514可以是外设部件互连标准(Peripheral Component Interconnect，简称PCI)总线或扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等。所述总线514可以分为地址总线、数据总线、控制总线等。为便于表示，图 5B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在采用集成的模块的情况下，图6A示出了上述实施例中所涉及的第二管理单元的一种可能的结构示意图。第二管理单元600包括：处理模块602和通信模块603。处理模块602用于对第二管理单元的动作进行控制管理，例如，处理模块602用于支持第二管理单元执行图2中的过程201和202，图3中的过程301和302，图4中的过程401和402和/或用于本文所描述的技术的其它过程。通信模块603用于支持第二管理单元与第一管理单元或其他网络实体的通信，例如与图1中示出的OSS/BSS单元或EM单元等之间的通信。第二管理单元还可以包括存储模块601，用于存储第二管理单元的程序代码和数据。
其中，处理模块602可以是处理器或控制器，例如可以是中央处理器(Central Processing Unit，CPU)，通用处理器，数字信号处理器(Digital Signal Processor，DSP)，专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块603可以是收发器、收发电路或通信接口等，例如，可以是上文中所述的OS-Ma-nfvo接口或Ve-Vnfm-em接口。存储模块601可以是存储器。
当处理模块602为处理器，通信模块603为收发器，存储模块601为存储器时，本发明实施例所涉及的第一管理单元可以为图6B所示的第二管理单元。
参阅图6B所示，该第一管理单元610包括：处理器612、收发器613、存储器611。可选的，第一管理单元610还可以包括总线614。其中，收发器613、处理器612以及存储器611可以通过总线614相互连接；总线614可以是外设部件互连标准总线或扩展工业标准结构总线等。所述总线614可以分为地址总线、数据总线、控制总线等。为便于表示，图6B中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
结合本发明实施例公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程 只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD～ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明实施例的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明实施例的具体实施方式而已，并不用于限定本发明实施例的保护范围，凡在本发明实施例的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明实施例的保护范围之内。

Claims (27)

  1. 一种管理方法，其特征在于，包括：
    第一管理单元接收第二管理单元发送的目标对象的管理请求，所述管理请求携带亲和信息，所述亲和信息用于配置所述目标对象与其他对象之间的亲和性和/或反亲和性，或者用于配置所述目标对象的子对象与其他对象之间的亲和性和/或反亲和性；
    所述第一管理单元根据所述亲和信息对所述目标对象进行管理。
  2. 根据权利要求1所述的方法，其特征在于，所述亲和信息包括以下情形中的至少一种：
    所述亲和信息为亲和去激活指示信息，所述亲和去激活指示信息用于指示所述第一管理单元在对所述目标对象进行管理的过程中忽略与所述目标对象相关的第一亲和规则；
    所述亲和信息为第二亲和规则，所述第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种；
    所述亲和信息为亲和约束信息，所述亲和约束信息用于指示与所述目标对象相关的亲和性和/或反亲和性的约束条件。
  3. 根据权利要求2所述的方法，其特征在于，所述规则指示信息用于指示所述第二亲和规则为亲和性规则和/或反亲和性规则。
  4. 根据权利要求2或3所述的方法，其特征在于，所述亲和对象标识用于标识所述第二亲和规则的作用对象，其中，所述亲和对象标识包括网络业务实例的标识、网络业务描述符的标识、虚拟网络功能实例的标识或虚拟网络功能描述符的标识中的至少一种。
  5. 根据权利要求2至4中任一项所述的方法，其特征在于，所述范围指示信息用于指示所述第二亲和规则的适用范围。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一管理单元根据所述亲和信息对所述目标对象进行管理，包括：
    所述第一管理单元根据所述亲和信息确定管理所述目标对象所需的管理需求信息的第三亲和规则；
    所述第一管理单元根据所述管理需求信息的第三亲和规则对所述目标对象进行部署；
    所述第一管理单元根据所述管理需求信息的第三规则确定对应的虚拟资源的第四亲和规则；
    所述第一管理单元根据所述虚拟资源的第四亲和规则为部署所述目标对象配置虚拟资源。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述目标对象为网络业务单元或虚拟网络功能单元。
  8. 一种管理方法，其特征在于，包括：
    第二管理单元获取亲和信息，所述亲和信息用于配置所述目标对象与其他对象之间的亲和性和/或反亲和性，或者用于配置所述目标对象的子对象与其他对象之间的亲和性和/或反亲和性；
    所述第二管理单元向第一管理单元发送所述目标对象的管理请求，所述管理请求携带所述亲和信息，以使得所述第一管理单元根据所述亲和信息对所述目标对象进行管理。
  9. 根据权利要求8所述的方法，其特征在于，所述亲和信息包括以下情形中的至少一种：
    所述亲和信息为亲和去激活指示信息，所述亲和去激活指示信息用于指示所述第一管理单元在对所述目标对象进行管理的过程中忽略与所述目标对象相关的第一亲和规则；
    所述亲和信息为第二亲和规则，所述第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种；
    所述亲和信息为亲和约束信息，所述亲和约束信息用于指示与所述目标对象相关的亲和性和/或反亲和性的约束条件。
  10. 根据权利要求9所述的方法，其特征在于，所述规则指示信息用于指示所述第二亲和规则为亲和性规则和/或反亲和性规则。
  11. 根据权利要求9或10所述的方法，其特征在于，所述亲和对象标识用于标识所述第二亲和规则的作用对象，其中，所述亲和对象标识包括网络业务实例的标识、网络业务描述符的标识、虚拟网络功能实例的标识或虚拟网络功能描述符的标识中的至少一种。
  12. 根据权利要求9至11中任一项所述的方法，其特征在于，所述范围指示信息用于指示所述第二亲和规则的适用范围。
  13. 根据权利要求8至12中任一项所述的方法，其特征在于，所述目标对象为网络业务单元或虚拟网络功能单元。
  14. 一种第一管理单元，其特征在于，包括：处理模块和通信模块，
    所述处理模块用于通过所述通信模块接收第二管理单元发送的目标对象的管理请求，所述管理请求携带亲和信息，所述亲和信息用于配置所述目标对象与其他对象之间的亲和性和/或反亲和性，或者用于配置所述目标对象的子对象与其他对象之间的亲和性和/或反亲和性；以及用于根据所述亲和信息对所述目标对象进行管理。
  15. 根据权利要求14的第一管理单元，其特征在于，所述亲和信息包括以下情形中的至少一种：
    所述亲和信息为亲和去激活指示信息，所述亲和去激活指示信息用于指示所述第一管理单元在对所述目标对象进行管理的过程中忽略与所述目标对象相关的第一亲和规则；
    所述亲和信息为第二亲和规则，所述第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种；
    所述亲和信息为亲和约束信息，所述亲和约束信息用于指示与所述目标对象相关的亲和性和/或反亲和性的约束条件。
  16. 根据权利要求15所述的第一管理单元，其特征在于，所述规则指示信息用于指示所述第二亲和规则为亲和性规则和/或反亲和性规则。
  17. 根据权利要求15或16所述的第一管理单元，其特征在于，所述亲和对象标识用于标识所述第二亲和规则的作用对象，其中，所述亲和对象标识包括网络业务实例的标识、网络业务描述符的标识、虚拟网络功能实例的标识或虚拟网络功能描述符的标识中的至少一种。
  18. 根据权利要求15至17中任一项所述的第一管理单元，其特征在于，所述范围指示信息用于指示所述第二亲和规则的适用范围。
  19. 根据权利要求14至18中任一项所述的第一管理单元，其特征在于，所述处理模块具体用于根据所述亲和信息确定管理所述目标对象所需的管理需求信息的第三亲和规则；以及根据所述管理需求信息的第三亲和规则对所述目标对象进行部署；以及根据所述管理需求信息的第三规则确定对应的虚拟资源的第四亲和规则；以及根据所述虚拟资源的第四亲和规则为部署所述目标对 象配置虚拟资源。
  20. 根据权利要求14至19中任一项所述第一管理单元，其特征在于，所述目标对象为网络业务单元或虚拟网络功能单元。
  21. 一种第二管理单元，其特征在于，包括：处理模块和通信模块，
    所述处理模块用于获取亲和信息，所述亲和信息用于配置所述目标对象与其他对象之间的亲和性和/或反亲和性，或者用于配置所述目标对象的子对象与其他对象之间的亲和性和/或反亲和性；以及用于通过所述通信模块向第一管理单元发送所述目标对象的管理请求，所述管理请求携带所述亲和信息，以使得所述第一管理单元根据所述亲和信息对所述目标对象进行管理。
  22. 根据权利要求21所述的第二管理单元，其特征在于，所述亲和信息包括以下情形中的至少一种：
    所述亲和信息为亲和去激活指示信息，所述亲和去激活指示信息用于指示所述第一管理单元在对所述目标对象进行管理的过程中忽略与所述目标对象相关的第一亲和规则；
    所述亲和信息为第二亲和规则，所述第二亲和规则包括规则指示信息、亲和对象标识、范围指示信息中的至少一种；
    所述亲和信息为亲和约束信息，所述亲和约束信息用于指示与所述目标对象相关的亲和性和/或反亲和性的约束条件。
  23. 根据权利要求22所述的第二管理单元，其特征在于，所述规则指示信息用于指示所述第二亲和规则为亲和性规则和/或反亲和性规则。
  24. 根据权利要求22或23所述的第二管理单元，其特征在于，所述亲和对象标识用于标识所述第二亲和规则的作用对象，其中，所述亲和对象标识包括网络业务实例的标识、网络业务描述符的标识、虚拟网络功能实例的标识或虚拟网络功能描述符的标识中的至少一种。
  25. 根据权利要求22至24中任一项所述的第二管理单元，其特征在于，所述范围指示信息用于指示所述第二亲和规则的适用范围。
  26. 根据权利要求21至25中任一项所述的第二管理单元，其特征在于，所述目标对象为网络业务单元或虚拟网络功能单元。
  27. 一种管理系统，其特征在于，包括：如权利要求14至20中任一项所述的第一管理单元以及如权利要求21至26中任一项所述的第二管理单元。
PCT/CN2016/078913 2016-04-08 2016-04-08 一种管理方法及装置 WO2017173667A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
CN201680083907.6A CN108886473B (zh) 2016-04-08 2016-04-08 一种管理方法及装置
JP2018552724A JP6680901B2 (ja) 2016-04-08 2016-04-08 管理方法および装置
BR112018070584-5A BR112018070584B1 (pt) 2016-04-08 Metodo de gerenciamento, aparelho orquestrador de virtualização de funções de rede, primeiro aparelho de gerenciamento, sistema de suporte de operações ou sistema de suporte de negócios, segundo aparelho de gerenciamento e meio legível por computador
KR1020187032019A KR102184512B1 (ko) 2016-04-08 2016-04-08 관리 방법 및 디바이스
EP16897601.7A EP3432515B1 (en) 2016-04-08 2016-04-08 Management method and device
PCT/CN2016/078913 WO2017173667A1 (zh) 2016-04-08 2016-04-08 一种管理方法及装置
US16/151,100 US11296945B2 (en) 2016-04-08 2018-10-03 Management method and apparatus
US17/698,169 US20220210019A1 (en) 2016-04-08 2022-03-18 Management Method and Apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/078913 WO2017173667A1 (zh) 2016-04-08 2016-04-08 一种管理方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/151,100 Continuation US11296945B2 (en) 2016-04-08 2018-10-03 Management method and apparatus

Publications (1)

Publication Number Publication Date
WO2017173667A1 true WO2017173667A1 (zh) 2017-10-12

Family

ID=60000837

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/078913 WO2017173667A1 (zh) 2016-04-08 2016-04-08 一种管理方法及装置

Country Status (6)

Country Link
US (2) US11296945B2 (zh)
EP (1) EP3432515B1 (zh)
JP (1) JP6680901B2 (zh)
KR (1) KR102184512B1 (zh)
CN (1) CN108886473B (zh)
WO (1) WO2017173667A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113535388A (zh) * 2021-06-25 2021-10-22 广西综合交通大数据研究院 面向任务的服务功能聚合方法
WO2023030218A1 (zh) * 2021-08-31 2023-03-09 华为技术有限公司 网络业务部署方法、nfvo以及nfv系统

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109213567B (zh) * 2017-06-29 2022-05-13 华为技术有限公司 一种管理vnf实例化的方法和设备
JP2019029946A (ja) * 2017-08-03 2019-02-21 富士通株式会社 通信制御装置、通信制御システム、及び通信制御方法
CN110324164B (zh) * 2018-03-29 2020-10-16 华为技术有限公司 一种网络切片的部署方法及装置
CN111404716B (zh) * 2019-01-02 2022-12-13 中国移动通信有限公司研究院 一种协同告警处理的方法及系统
US11650837B2 (en) * 2019-04-26 2023-05-16 Hewlett Packard Enterprise Development Lp Location-based virtualization workload placement
CN112887121B (zh) * 2019-11-29 2022-08-19 北京华为数字技术有限公司 一种管理网络服务的方法、设备及系统
US11349774B2 (en) * 2019-12-13 2022-05-31 At&T Intellectual Property 1, L.P. Methods, systems and computer readable media for diagnosing network function virtualization performance
CN113918268A (zh) * 2020-07-07 2022-01-11 华为技术有限公司 一种多租户管理方法及装置
CN115879456A (zh) * 2021-09-26 2023-03-31 中兴通讯股份有限公司 资源的拓扑还原方法、装置、服务器和存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110246627A1 (en) * 2010-04-01 2011-10-06 International Business Machines Corporation Data Center Affinity Of Virtual Machines In A Cloud Computing Environment
CN104137482A (zh) * 2014-04-14 2014-11-05 华为技术有限公司 一种云计算架构下的容灾数据中心配置方法及装置
CN104199718A (zh) * 2014-08-22 2014-12-10 上海交通大学 一种基于numa高性能网络缓存资源亲和度的虚拟处理器的调度方法

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7562145B2 (en) * 2003-08-28 2009-07-14 International Business Machines Corporation Application instance level workload distribution affinities
JP6090423B2 (ja) * 2012-03-30 2017-03-08 日本電気株式会社 通信システム、制御装置、通信装置、通信制御方法およびプログラム
US9712402B2 (en) * 2012-10-10 2017-07-18 Alcatel Lucent Method and apparatus for automated deployment of geographically distributed applications within a cloud
US9363192B2 (en) * 2013-10-31 2016-06-07 Vmware, Inc. Automatic remediation in a distributed computer system with multiple clusters of host computers
EP2940968A1 (en) * 2014-04-30 2015-11-04 Hewlett-Packard Development Company, L.P. Network infrastructure management
US9806975B2 (en) * 2014-06-12 2017-10-31 Futurewei Technologies, Inc. Methods and systems for managing capacity in a virtualized network
US9742690B2 (en) * 2014-08-20 2017-08-22 At&T Intellectual Property I, L.P. Load adaptation architecture framework for orchestrating and managing services in a cloud computing system
US9800673B2 (en) * 2014-08-20 2017-10-24 At&T Intellectual Property I, L.P. Service compiler component and service controller for open systems interconnection layer 4 through layer 7 services in a cloud computing system
EP3855681A1 (en) * 2014-09-25 2021-07-28 Apple Inc. Network functions virtualization
EP3040860A1 (en) * 2014-12-29 2016-07-06 NTT DoCoMo, Inc. Resource management in cloud systems
WO2017067598A1 (en) * 2015-10-22 2017-04-27 Nokia Solutions And Networks Oy Security mechanism for communication network including virtual network functions
CN108369529B (zh) * 2015-10-23 2022-04-08 瑞典爱立信有限公司 通过反关联规则为实例分配主机
KR20170056350A (ko) * 2015-11-13 2017-05-23 한국전자통신연구원 Nfv 자원 할당 검증 장치
US10356184B2 (en) * 2016-03-31 2019-07-16 Huawei Technologies Co., Ltd. Systems and methods for service and session continuity in software defined topology management
EP3523923A1 (en) * 2016-10-05 2019-08-14 Convida Wireless, LLC Capability exposure for service instantiation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110246627A1 (en) * 2010-04-01 2011-10-06 International Business Machines Corporation Data Center Affinity Of Virtual Machines In A Cloud Computing Environment
CN104137482A (zh) * 2014-04-14 2014-11-05 华为技术有限公司 一种云计算架构下的容灾数据中心配置方法及装置
CN104199718A (zh) * 2014-08-22 2014-12-10 上海交通大学 一种基于numa高性能网络缓存资源亲和度的虚拟处理器的调度方法

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113535388A (zh) * 2021-06-25 2021-10-22 广西综合交通大数据研究院 面向任务的服务功能聚合方法
CN113535388B (zh) * 2021-06-25 2023-09-29 广西综合交通大数据研究院 面向任务的服务功能聚合方法
WO2023030218A1 (zh) * 2021-08-31 2023-03-09 华为技术有限公司 网络业务部署方法、nfvo以及nfv系统

Also Published As

Publication number Publication date
EP3432515A4 (en) 2019-01-23
EP3432515A1 (en) 2019-01-23
CN108886473A (zh) 2018-11-23
US20190036783A1 (en) 2019-01-31
KR20180132818A (ko) 2018-12-12
US11296945B2 (en) 2022-04-05
JP6680901B2 (ja) 2020-04-15
CN108886473B (zh) 2020-09-11
KR102184512B1 (ko) 2020-11-30
US20220210019A1 (en) 2022-06-30
JP2019511887A (ja) 2019-04-25
BR112018070584A2 (pt) 2019-02-05
EP3432515B1 (en) 2020-05-20

Similar Documents

Publication Publication Date Title
WO2017173667A1 (zh) 一种管理方法及装置
US10917294B2 (en) Network function instance management method and related device
EP3430512B1 (en) Network virtualization of containers in computing systems
US10698717B2 (en) Accelerator virtualization method and apparatus, and centralized resource manager
CN107534579B (zh) 资源管理的系统和方法
CN107431651B (zh) 一种网络服务的生命周期管理方法及设备
US9996371B2 (en) Virtual switching method, related apparatus, and computer system
US11108653B2 (en) Network service management method, related apparatus, and system
WO2017148249A1 (zh) 配置资源的方法及其网络设备
EP3313023A1 (en) Life cycle management method and apparatus
WO2019100266A1 (zh) 移动边缘主机服务通知方法和装置
WO2017161562A1 (zh) 网络功能虚拟化环境下应用的管理方法和装置
CN109995552B (zh) Vnf服务实例化方法及装置
CN107534577B (zh) 一种网络业务实例化的方法及设备
CN109565447A (zh) 网络功能处理方法及相关设备
CN115858103B (zh) 用于开放堆栈架构虚拟机热迁移的方法、设备及介质
WO2018040042A1 (zh) 一种告警信息上报方法及装置
WO2017206092A1 (zh) 一种生命周期管理方法及管理单元
CN114428757A (zh) 一种架构可重构的计算装置及其重构方法
WO2018045540A1 (zh) 一种生命周期管理方法及管理单元
CN111581203A (zh) 信息处理方法、装置及存储介质
US20240036925A1 (en) Lcs sdxi data plane configuration system
US20240036935A1 (en) Lcs sdxi resource ownership system
US20240028373A1 (en) Decoupling ownership responsibilities among users in a telecommunications cloud
BR112018070584B1 (pt) Metodo de gerenciamento, aparelho orquestrador de virtualização de funções de rede, primeiro aparelho de gerenciamento, sistema de suporte de operações ou sistema de suporte de negócios, segundo aparelho de gerenciamento e meio legível por computador

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018552724

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016897601

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018070584

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2016897601

Country of ref document: EP

Effective date: 20181012

ENP Entry into the national phase

Ref document number: 20187032019

Country of ref document: KR

Kind code of ref document: A

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

Ref document number: 16897601

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 112018070584

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20181005