WO2015131696A1 - 一种虚拟化网络功能管理的方法和装置 - Google Patents

一种虚拟化网络功能管理的方法和装置 Download PDF

Info

Publication number
WO2015131696A1
WO2015131696A1 PCT/CN2015/071338 CN2015071338W WO2015131696A1 WO 2015131696 A1 WO2015131696 A1 WO 2015131696A1 CN 2015071338 W CN2015071338 W CN 2015071338W WO 2015131696 A1 WO2015131696 A1 WO 2015131696A1
Authority
WO
WIPO (PCT)
Prior art keywords
vnfm
pool
managed
vnfs
vnfms
Prior art date
Application number
PCT/CN2015/071338
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 US15/513,452 priority Critical patent/US10511506B2/en
Priority to EP15758107.5A priority patent/EP3200393B1/en
Publication of WO2015131696A1 publication Critical patent/WO2015131696A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • 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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0695—Management of faults, events, alarms or notifications the faulty arrangement being the maintenance, administration or management system
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for virtualized network function management.
  • NFV Network Function Virtualization
  • the network functions are executed in software running on a series of industry standard server hardware.
  • the software here can be installed and uninstalled on different hardware in the network as needed, without installing new hardware devices.
  • NFV ISG Network Functions Virtualisation Industry Specification Group
  • ETSI European Telecommunications Standards Institute
  • NFV-MANO NFV Management and Orchestration
  • NFVO NFV Network Functions Virtualisation Orchestrator
  • VNFM Virtualized Network Function Manager
  • NFVO is responsible for VNF (Virtualized Network Function) and resource management and scheduling in the entire virtualization management platform.
  • VNFM is responsible for VNF lifecycle management.
  • the relationship between NFVO, VNFM, and VNF is shown in Figure 1.
  • the VNFM responsible for VNF lifecycle management has network message interaction with multiple VNFs.
  • the VNFM may be connected.
  • the amount of VNF has a relatively high requirement for the processing performance of VNFM.
  • VNFM is the centralized manager of the virtualized subnet to which it belongs. Once the VNFM fails, the management of the virtual VNF to all VNFs of its virtualized subnet will fail at the same time.
  • VNFM functional entity in the ETSI NFV ISG specification architecture cannot meet the requirements of high performance and high reliability of telecommunication network equipment.
  • the technical problem to be solved by the present invention is to provide a method and apparatus for virtualized network function management, so as to improve the performance and reliability of virtualized network function management.
  • a method for virtualizing network function management comprising:
  • the network function virtualization orchestrator NFVO initializes the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool.
  • the configuration information includes the initial number of VNFMs managed by the VNFM pool, and the VNFM pool management. The maximum number of VNFMs and the maximum number of VNFs managed by each VNFM in the VNFM pool;
  • the NFVO monitors the status of each VNFM in the VNFM pool, and if a VNFM failure is detected, the failed VNFM managed VNF is assigned to one or more normal VNFMs.
  • the maximum number of VNFs managed by each VNFM is the same.
  • the method further includes:
  • the NFVO monitors a state of the VNFM pool
  • the NFVO finds a VNFM with the smallest number of VNFs managed in the VNFM pool
  • the number of VNFs managed by the VNFM is the maximum number of VNFs that are managed by the VNFM
  • the number of VNFMs currently managed by the VNFM Pool is obtained, and the number of VNFMs currently managed is smaller than the maximum number of VNFMs configured by the VNFM Pool. Number, then add a VNFM in the VNFM pool.
  • the maximum number of VNFs managed by each VNFM is the same;
  • the method further includes:
  • the NFVO monitors the number of VNFMs managed by the VNFM pool
  • the VNFM with the largest number of managed VNFs is found. If the number of VNFs managed by the VNFM with the largest number of VNFs managed is smaller than the maximum number of VNFs managed by the VNFM. Half of the number, the VNFM with the smallest number of managed VNFs is taken as the VNFM to be deleted;
  • the VNFM to be deleted is deleted.
  • the network function virtualization orchestrator NFVO initializes the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool, including:
  • the NFVO instantiates each VNFM in the VNFM Pool according to the initial number of VNFMs managed by the VNFM pool, and adds the instantiated VNFM to the VNFM Pool;
  • the method further includes:
  • the instantiated VNF is assigned to one or more normal VNFMs.
  • the NFVO monitors a status of each VNFM in the VNFM pool. If a VNFM failure is detected, the step of assigning each VNF managed by the failed VNFM to one or more normal VNFMs includes: :
  • the NFVO monitors the status of each VNFM in the VNFM pool, and if a VNFM failure is detected, a VNFM is added to the VNFM pool;
  • An apparatus for virtualizing network function management comprising a configuration module, a monitoring module and a processing module, wherein:
  • the configuration module is configured to: initialize the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool; wherein the configuration information includes the initial number of VNFMs managed by the VNFM pool, and the VNFM pool management The maximum number of VNFMs and the maximum number of VNFs managed by each VNFM in the VNFM pool;
  • the monitoring module is configured to: monitor a status of each VNFM in the VNFM pool;
  • the processing module is configured to: if the monitoring module detects a VNFM failure, assign the failed VNFM-managed VNF to one or more normal VNFMs.
  • the maximum number of VNFs managed by each VNFM is the same;
  • the monitoring module is further configured to: monitor a status of the VNFM pool;
  • the processing module is further configured to: find the VNFM with the smallest number of management VNFs in the VNFM pool. If the number of VNFs managed by the VNFM reaches the maximum number of VNFs managed by the VNFM, obtain the number of VNFMs currently managed by the VNFM Pool, if current management If the number of VNFMs is smaller than the maximum number of VNFMs configured by the VNFM Pool, a VNFM is added to the VNFM pool.
  • the maximum number of VNFs managed by each VNFM is the same;
  • the monitoring module is further configured to: monitor a quantity of VNFMs managed by the VNFM pool;
  • the processing module is further configured to: when the number of VNFMs of the current VNFM pool management acquired by the monitoring module is greater than the initial number of VNFMs managed by the VNFM Pool, look for the VNFM with the largest number of managed VNFs, if the managed VNF The number of VNFs managed by the largest VNFM is less than half of the maximum number of VNFs managed by the VNFM, and the VNFM with the smallest number of managed VNFs is taken as the VNFM to be deleted;
  • the processing module is further configured to: perform the following operations on the VNF managed by the VNFM to be deleted: find the VNFM with the smallest number of managed VNFs in all normal VNFMs as the deletion takeover VNFM of the VNF; assign the VNF to the VNF The VNFM is deleted. After all the VNFs managed by the VNFM to be deleted belong to the normal VNFM, the VNFM to be deleted is deleted.
  • the configuration module is configured to manage the pool according to the virtualized network function as follows
  • the configuration information of the VNFM pool is initialized to the VNFM pool:
  • Each VNFM in the VNFM Pool is instantiated according to the initial number of VNFMs managed by the VNFM pool, and the instantiated VNFM is added to the VNFM Pool;
  • the configuration module is further configured to: after the configuration module initializes the VNFM pool, assign the instantiated VNF to one or more normal VNFMs.
  • the processing module is configured to attribute each VNF managed by the failed VNFM to another normal VNFM as follows:
  • the monitoring module monitors the status of each VNFM in the VNFM pool. If a VNFM failure is detected, the processing module adds a VNFM to the VNFM pool.
  • a computer program comprising program instructions that, when executed by a computer, cause the computer to perform any of the methods of virtual network function management described above.
  • the above solution adopts the VNFM Pool.
  • VNFM When a single VNFM fails, only the VNF to which it belongs is affected, and the VNF managed by the VNFM can be automatically migrated to other normal VNFMs, which improves the system reliability of the virtualized network, and the virtualized network function management function
  • the VNF management is shared with each VNFM of the VNFMPool.
  • the number of VNFM instance objects of the VNFM Pool can be increased or deleted accordingly, and the system resource saving effect is achieved at low load, and the high performance is satisfied under overload. Processing capacity requirements.
  • FIG. 2 is a NFVO/VNFM Pool/VNF relationship diagram according to an embodiment of the present invention
  • FIG. 3 is a flowchart of an NFVO initialization VNFM Pool according to Embodiment 1 of the present invention.
  • FIG. 4 is a flowchart of an NFVO instantiation VNF according to Embodiment 2 of the present invention.
  • FIG. 5 is a flowchart of a NFVO operation VNF according to Embodiment 3 of the present invention.
  • FIG. 6 is a flowchart of adding NFVO to VNFM according to Embodiment 4 of the present invention.
  • FIG. 7 is a flowchart of NFVO deletion VNFM according to Embodiment 5 of the present invention.
  • FIG. 8 is a flowchart of processing a failed VNFM according to Embodiment 6 of the present invention.
  • FIG. 9 is a schematic structural diagram of an apparatus for virtualized network function management according to the present invention.
  • the embodiment of the present invention implements a method for implementing the network virtualization function management by using the VNFM Pool.
  • the core idea is to use a VNFM Pool function entity containing multiple VNFMs to implement network virtualization function management functions; VNFM Pool's VNF management functions are automatically assigned to VNFM execution in VNFM Pool; when VNFM When the VNFM of the Pool fails, the VNFM is restored by deleting the VNFM instance object by creating a new VNFM instance object, and the VNF managed VNFM is migrated to other normal VNFM management.
  • the embodiment of the present application provides a method for virtualizing network function management, where the method includes:
  • Step 1 The network function virtualization orchestrator NFVO initializes the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool; the configuration information includes the initial number of VNFMs of the virtualized network function managed by the VNFM pool, and the maximum VNFM managed by the VNFM pool. Number and the maximum number of VNFs managed by each VNFM;
  • the maximum number of VNFMs managed by the VNFM pool is the maximum number of VNFMs that can be managed by the VNFM pool.
  • the maximum number of VNFs managed by the VNFM is the maximum number of VNFs that can be managed by the VNFM.
  • the network function virtualization orchestrator NFVO initializes the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool, and specifically includes: according to the initial number of VNFMs managed by the VNFM pool, the NFVO instantiates each VNFM in the VNFM Pool, Add the instantiated VNFM to the VNFM Pool.
  • the VNF instantiated after the VNFM pool is initialized is attributed to one or more of the VNFMs.
  • Step 2 NFVO monitors the status of each VNFM in the VNFM pool. If the VNFM fails, the VNFs managed by the failed VNFM are assigned to one or more normal VNFMs.
  • This step includes:
  • NFVO monitors the status of each VNFM in the VNFM pool. If a VNFM failure is detected, a VNFM is added to the VNFM pool;
  • the VNFs managed by the failed VNFM are sequentially operated by: finding the VNFM having the smallest number of management VNFs in all the normal VNFMs as the failover takeover VNFM of the above VNF; and assigning the VNF managed by the failed VNFM to the failover takeover VNFM;
  • the failed VNFM After each VNF managed by the failed VNFM belongs to other normal VNFMs, the failed VNFM is deleted.
  • the method further includes:
  • Step 3 NFVO monitors the state of the VNFM pool; the maximum number of VNFs managed by each VNFM is the same; NFVO searches for the VNFM with the smallest number of VNFs managed in the VNFM pool;
  • the number of VNFs managed by the VNFM in the VNFM pool is the maximum number of VNFs managed by the VNFM, the number of VNFMs currently managed by the VNFM Pool is obtained. If the number of VNFMs currently managed is less than the maximum number of VNFMs configured by the VNFM Pool, Then add a VNFM to the VNFM pool.
  • the purpose of this operation is to monitor whether VNFM needs to be increased. For example, the maximum VNF number of VNFM is 10, and the VNFM Pool has 5 VNFMs. When all VNFMs manage 10 VNFs, the above monitoring conditions are met.
  • the maximum number of VNFs managed by each VNFM may also be different. If the maximum number of VNFs managed by each VNFM is different, the monitoring rules adopted according to the maximum number of VNFs managed by each VNFM may be determined according to the specified rules. VNFM.
  • the number of VNFs managed by the newly added VNFM is 0. If the VNF needs to be added, the newly added VNF can be assigned to the newly added VNFM. Of course, if there are other VNFMs that manage the VNF number to 0, they can also belong to other VNFMs. In the actual operation, the newly added VNF may be assigned to the VNFM with the smallest number of VNFs in the current state, or the VNFM to which the VNFM belongs may be selected according to other rules.
  • Step 4 NFVO monitors the number of VNFMs managed by the VNFM pool
  • the VNFM with the largest number of management VNFs is searched. If the number of VNFs managed by the VNFM is less than half of the maximum number of VNFs managed by the VNFM, the VNFM management is performed. The VNFM with the smallest number of VNFs is used as the VNFM to be deleted;
  • VNFs to be deleted from the VNFM management are sequentially performed as follows: the VNFM having the smallest number of management VNFs is found in all the normal VNFMs as the deletion takeover VNFM of the VNF; the VNF is attributed to the deletion takeover VNFM;
  • the VNFM to be deleted is deleted.
  • the VNF to be transferred may be assigned to the same VNFM, or Belong to different VNFM.
  • the corresponding rules can be set according to actual conditions.
  • steps three and four are performed after step one, and there is no limitation between the two steps.
  • the NFVO is responsible for initializing the VNFM Pool, including the following processes:
  • the NFVO obtains the current VNFM Pool configuration information, including the initial VNFM number, the maximum VNFM number, and the maximum VNF number managed by each VNFM, and the VNFM Pool configuration;
  • Steps 102-1, step 102-2, ..., step 102-n NFVO instantiate the VNFM instance object in the VNFM Pool one by one until the number of VNFM instances of the VNFM Pool reaches the initial VNFM number of the VNFM Pool configuration.
  • step 103 the NFVO adds the instantiated VNFM instance object to the VNFM list in the VNFM Pool.
  • the NFVO instantiation VNF specifically includes the following processes:
  • Step 201 NFVO is sorted according to the number of VNFs managed by the VNFM in the VNFM Pool, and allocates a VNFM with the smallest number of VNFs as the VNFM that performs VNF instantiation;
  • Step 202 The NFVO sends an instantiated VNF request message to the allocated VNFM.
  • Step 203 The assigned VNFM receives the instantiated VNF request message, performs VNF instantiation, and the VNFM that is instantiated by the VNF is the VNFM that performs the instantiation of the VNF, and the home VNFM information is saved into the VNF instance object attribute.
  • step 204 the assigned VNFM returns a request to instantiate the VNF reply message.
  • the NFVO operation VNF specifically includes the following processes:
  • Step 301 The NFVO locates the VNFM instance object in the VNFM Pool according to the VNF attribute of the VNF.
  • Step 302 The NFVO sends an operation VNF request message to the VNF home VNFM.
  • Step 303 the VNF home VNFM receives the operation VNF request message, and performs the requested VNF operation.
  • step 304 the home VNFM returns a request to operate the VNF reply message.
  • the NFVO addition VNFM specifically includes the following processes:
  • step 401 the NFVO monitors whether the VNFM pool is overloaded.
  • step 402 the NFVO determines whether the VNFM can be added.
  • the specific method is to obtain the VNFM number of the current VNFM Pool. If the VNFM number of the current VNFM Pool is smaller than the maximum VNFM number configured by the VNFM Pool, perform the following steps, otherwise the process is aborted;
  • Step 403 NFVO creates a new VNFM instance object
  • step 404 NFVO adds the newly created VNFM to the VNFM list of the VNFM Pool.
  • the NFVO delete VNFM specifically includes the following processes:
  • step 501 the NFVO determines whether the VNFM needs to be deleted.
  • the specific method is to obtain the VNFM number of the current VNFM Pool. If the VNFM number of the current VNFM Pool is greater than the initial VNFM number configured by the VNFM Pool, perform the subsequent steps, otherwise the process is aborted;
  • step 502 the NFVO monitors whether the VNFM pool is low-loaded.
  • the specific method is that the VNF number of the VNFM managed by the VNFM is sorted according to the VNFM pool.
  • the VNF number of the VNFM that manages the largest number of VNFs is less than the maximum number of VNFs managed by each VNFM configured by the VNFM Pool. Perform the next steps in half of the process, otherwise the process is aborted;
  • step 503 the NFVO obtains the VNFM to be deleted, and the VNFM is the VNFM that is the smallest VNFM managed by the VNFM.
  • Step 504 The NFVO updates the VNF belonging to the VNFM to be deleted VNFM to other VNFMs, and the specific steps are as follows:
  • Step 504-1 the VNFM of the NFVO to the VNFM Pool is sorted according to the number of VNFs managed by the VNFM, except for the VNFM to be deleted.
  • the VNFM that manages the smallest number of VNFs is allocated as the VNFM that takes over the VNF instance.
  • Step 504-2 the NFVO sends an update VNF home VNFM request message to the VNFM that takes over the VNF instance;
  • Step 504-3 the VNFM receives the update VNF home VNFM request message, and sends an update VNF home VNFM message to the corresponding VNF.
  • Step 504-4 the VNF receives the update VNF home VNFM message, and modifies its own home VNFM attribute.
  • Step 504-5 the VNF returns an update VNF home VNFM response message, and the response message includes current state information of the VNF.
  • Step 504-6 the VNFM receives the update VNF home VNFM response message, and saves the current state information of the VNF.
  • Step 504-7 the VNFM returns an update VNF home VNFM request response message to the NFVO.
  • step 505 the NFVO deletes the VNFM from the VNFM list of the VNFM Pool and deletes the VNFM instance object.
  • the failed VNFM processing specifically includes the following processes:
  • Step 601 NFVO creates a new VNFM instance object and adds it to the VNFM list of the VNFM Pool;
  • Step 602 The NFVO update fails.
  • the VNF managed by the VNFM belongs to the VNFM as another normal VNFM.
  • the specific manner is as follows:
  • step 602-1 the NFVO is disabled according to the VNF number managed by the VNFM, and a VNFM with the smallest number of VNFs is allocated as the VNFM that takes over the VNF instance;
  • Step 602-2 the NFVO sends an update VNF home VNFM request message to the VNFM that takes over the VNF instance.
  • Step 602-3, the VNFM receives the update VNF home VNFM request message, and sends an update VNF home VNFM message to the corresponding VNF.
  • Step 602-4 The VNF receives the update VNF home VNFM message, and modifies its own home VNFM attribute.
  • Step 602-5 The VNF returns an update VNF home VNFM response message, where the response message includes current status information of the VNF.
  • Step 602-6 The VNFM receives the update VNF home VNFM response message, and saves the current state information of the VNF.
  • Step 602-7 the VNFM returns an update VNF home VNFM request response message to the NFVO.
  • step 603 the NFVO deletes the invalid VNFM from the VNFM list of the VNFM Pool, and deletes the invalid VNFM instance object.
  • the embodiment of the invention further provides an apparatus for virtualized network function management, the device comprising:
  • the configuration module is configured to: initialize the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool; the configuration information includes the initial number of VNFMs managed by the VNFM pool, the maximum number of VNFMs, and each VNFM management. The maximum number of VNFs;
  • a monitoring module configured to: monitor, by the NFVO, a state of each VNFM in the VNFM pool;
  • the processing module is configured to: when the monitoring module detects that the VNFM fails, assign the VNF managed by the failed VNFM to the other normal VNFM.
  • the monitoring module is further configured to: the NFVO monitors a load status of the VNFM pool;
  • the processing module is further configured to: when the monitoring module detects that the VNFM pool is overloaded, and determine, according to the configuration information, that a VNFM can be added, adding a VNFM to the VNFM pool; and, when The monitoring module detects that the VNFM pool is under load, and determines that the VNFM needs to be deleted according to the configuration information, and deletes the VNFM in the VNFM pool.
  • the configuration module is configured to initialize the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool:
  • the NFVO instantiates each VNFM in the VNFM Pool, and adds the instantiated VNFM to the VNFM Pool.
  • the processing module is configured to: when the monitoring module detects that the VNFM fails, assigning the VNF managed by the failed VNFM to the other normal VNFM means:
  • the NFVO monitors the state of each VNFM in the VNFM pool, and if the VNFM failure is detected, the VNFM that minimizes the number of VNFs in all normal VNFMs is taken as the takeover VNFM;
  • the VNF managed by the failed VNFM is assigned to the failed takeover VNFM and the failed VNFM is deleted.
  • the processing module is configured to: when the monitoring module detects that the VNFM pool is overloaded, and determines that a VNFM can be added according to the configuration information, adding a VNFM in the VNFM pool refers to:
  • VNFM Finding the VNFM with the smallest number of management VNFs, if the VNF number managed by the VNFM reaches the maximum VNF number managed by the VNFM, the VNFM pool is overloaded;
  • VNFM Pool Obtaining the number of VNFMs currently managed by the VNFM Pool. If the number of currently managed VNFMs is smaller than the maximum number of VNFMs configured by the VNFM Pool, add a VNFM to the VNFM pool.
  • the processing module is configured to: when the monitoring module detects that the VNFM pool is under load, and determines that the VNFM needs to be deleted according to the configuration information, deleting the VNFM in the VNFM pool means:
  • Finding the VNFM with the largest number of VNFs if the number of VNFs managed by the VNFM is less than half of the maximum number of VNFs managed by the VNFM, the VNFM pool is under load;
  • VNFM with the smallest number of VNFM management VNFs is used as the VNFM to be deleted; the takeover VNFM in the current state is obtained, and the VNF managed by the VNFM to be deleted is assigned to the takeover VNFM.
  • the embodiment of the present invention further provides a device for managing virtualized network functions, and the device may be disposed on the network function virtualization orchestrator NFVO, and the device includes:
  • the configuration module 11 is configured to: initialize the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool; and the configuration information includes the initial VNFM managed by the VNFM pool. Number, the maximum number of VNFMs managed by the VNFM pool and the maximum number of VNFs managed by each VNFM;
  • the monitoring module 12 is configured to: monitor the status of each VNFM in the VNFM pool;
  • the processing module 13 is configured to: if the monitoring module 12 detects that the VNFM fails, assign each VNF managed by the failed VNFM to one or more normal VNFMs.
  • the maximum number of VNFs managed by each VNFM is the same;
  • the monitoring module 12 is further configured to: monitor a status of the VNFM pool;
  • the processing module 13 is further configured to: find the VNFM with the smallest number of VNFs in the VNFM pool. If the number of VNFs managed by the VNFM reaches the maximum number of VNFs managed by the VNFM, obtain the number of VNFMs currently managed by the VNFM Pool, if currently managed. If the number of VNFMs is smaller than the maximum number of VNFMs configured in the VNFM Pool, add a VNFM to the VNFM pool.
  • the monitoring module 12 is further configured to: monitor the number of VNFMs managed by the VNFM pool;
  • the processing module 13 is further configured to: when the number of VNFMs managed by the monitoring module is greater than the initial number of VNFMs managed by the VNFM Pool, look for the VNFM with the largest number of VNFs, if the number of VNFs managed by the VNFM is less than VNFM Half of the maximum number of managed VNFs, the VNFM with the smallest VNFM management VNF number is taken as the VNFM to be deleted;
  • the processing module 13 is further configured to: perform the following operations on the VNFs to be deleted by the VNFM: the VNFM with the smallest number of management VNFs is found in all the normal VNFMs as the deletion takeover VNFM of the VNF; and the VNF is attributed to the delete takeover VNFM; It is also set to: when each VNF managed by the VNFM to be deleted belongs to another normal VNFM, the VNFM to be deleted is deleted.
  • the configuration module 11 is configured to initialize the VNFM pool according to the configuration information of the virtualized network function management pool VNFM pool:
  • the NFVO instantiates each VNFM in the VNFM Pool, and adds the instantiated VNFM to the VNFM Pool;
  • the configuration module 11 is further configured to: attribute the instantiated VNF after initializing the VNFM pool Go to one or more VNFMs.
  • the processing module 13 is configured to: if the monitoring module detects that the VNFM fails, assigning each VNF managed by the failed VNFM to another normal VNFM means:
  • NFVO monitors the status of each VNFM in the VNFM pool, and if a VNFM failure is detected, a VNFM is added to the VNFM pool;
  • the failed VNFM After each VNF managed by the failed VNFM belongs to other normal VNFMs, the failed VNFM is deleted.
  • the embodiment of the invention also discloses a computer program, comprising program instructions, which, when executed by a computer, enable the computer to perform any of the above methods of virtualized network function management.
  • the embodiment of the invention also discloses a carrier carrying the computer program.
  • the above solution adopts the VNFM Pool.
  • VNFM VNFM Pool
  • the VNF managed by the VNFM can be automatically migrated to other normal VNFMs, which improves the system reliability of the virtualized network, and the virtualized network function management function
  • the VNF management is distributed to each VNFM of the VNFM Pool.
  • the number of VNFM instance objects of the VNFM Pool can be increased or deleted correspondingly, and the system resource saving effect is achieved at low load, and the high value is satisfied when the load is overloaded. Performance processing capability requirements. Therefore, the present invention has strong industrial applicability.

Landscapes

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

Abstract

一种虚拟化网络功能管理的方法，所述方法包括：网络功能虚拟化编排器NFVO根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化；所述配置信息包括所述VNFM pool管理的VNFM初始个数、所述VNFM pool管理的VNFM最大个数及各VNFM管理的VNF最大个数；所述NFVO监测所述VNFM pool中各VNFM的状态，若监测到VNFM失效时，则将失效VNFM管理的各VNF归属到一个或多个正常VNFM上。上述方案的通过VNFM Pool，当单个VNFM失效时只影响其归属的VNF，并且失效VNFM管理的VNF能够自动迁移到其他正常的VNFM，提高了虚拟化网络的系统可靠性。

Description

一种虚拟化网络功能管理的方法和装置 技术领域
本发明涉及通讯领域，具体涉及一种虚拟化网络功能管理的方法和装置。
背景技术
NFV(Network Fuction virtualization，网络功能虚拟化)旨在通过研究发展标准IT(Information Technology,信息技术)虚拟化技术，使得许多网络设备类型能够融入到符合行业标准的大量服务器、交换机和存储设备中去，在一系列行业标准服务器硬件上运行的软件中执行网络功能，这里的软件可以根据需要在网络中的不同位置硬件上安装和卸载，不需要安装新的硬件设备。
运营商在ETSI(European Telecommunications Standards Institute，欧洲电信标准化协会)成立了NFV ISG(Network Functions Virtualisation Industry Specification Group，网络功能虚拟化标准工作组)，其研究目标主要是希望通过广泛采用标准化的IT虚拟化技术，采用业界标准的大容量服务器、存储和交换机承载各种各样的网络软件功能，实现软件的灵活加载，实现在数据中心、网络节点和用户端等各个位置灵活的部署配置，从而加快网络部署和调整的速度，降低业务部署的复杂度，提高网络设备的统一化、通用化、适配性等，最终降低网络的固定资产投入和运营成本。
根据ETSI NFV ISG规范要求，在NFV-MANO(NFV Management and Orchestration，网络功能虚拟化管理与协调流程)域定义一套自动化部署规范，实现一套虚拟化应用部署流程和架构。在这个架构中，有两个功能实体:NFVO(NFV Network Functions Virtualisation Orchestrator,网络功能虚拟化编排器)和VNFM(Virtualized Network Function Manager，虚拟化网络功能管理)。NFVO负责整个虚拟化管理平台内的VNF(Virtualized Network Function,虚拟网络功能)和资源的管理和调度，VNFM负责VNF的生命周期管理。
NFVO,VNFM,VNF的关系如图1所示,负责VNF生命周期管理的VNFM与多个VNF有网络消息交互,在电信网络设备实现NFV时VNFM可能连接大 量VNF,对VNFM的处理性能有比较高的要求。更进一步，VNFM是其归属的虚拟化子网的集中管理者，一旦VNFM失效，虚拟化网络对其归属虚拟化子网的全部VNF的管理将同时失效。
综上所述，ETSI NFV ISG规范架构中的VNFM功能实体不能满足电信网络设备高性能,高可靠性的要求。
发明内容
本发明所要解决的技术问题是提供一种虚拟化网络功能管理的方法和装置，以便提高虚拟化网络功能管理的性能和可靠性。
为了解决上述技术问题，采用如下技术方案：
一种虚拟化网络功能管理的方法，所述方法包括：
网络功能虚拟化编排器NFVO根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化；其中，所述配置信息包括所述VNFM pool管理的VNFM初始个数、所述VNFM pool管理的VNFM最大个数和所述VNFM pool中每个VNFM管理的VNF最大个数；
所述NFVO监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，则将该失效的VNFM管理的VNF归属到一个或多个正常的VNFM上。
可选地，每个VNFM管理的VNF最大个数相同
所述方法还包括：
所述NFVO监测所述VNFM pool的状态；
所述NFVO查找所述VNFM pool中管理的VNF数最小的VNFM；
如果该管理的VNF数最小的VNFM管理的VNF数达到VNFM管理的VNF最大个数，则获取所述VNFM Pool当前管理的VNFM数,若当前管理的VNFM数小于所述VNFM Pool配置的VNFM最大个数，则在所述VNFM pool中新增一个VNFM。
可选地，每个VNFM管理的VNF最大个数相同；
所述方法还包括：
所述NFVO监测所述VNFM pool管理的VNFM的数量；
如果当前VNFM pool管理的VNFM个数大于所述VNFM Pool管理的VNFM初始个数，则查找管理的VNF数最大的VNFM，若管理的VNF数最大的VNFM管理的VNF数小于VNFM管理的VNF最大个数的一半，则将管理的VNF数最小的VNFM作为待删除VNFM；
对所述待删除VNFM管理的VNF进行下述操作：在所有正常VNFM中找到管理的VNF数最小的VNFM作为该VNF的删除接管VNFM；将该VNF归属到所述删除接管VNFM；
当所述待删除VNFM管理的所有VNF均归属到正常VNFM后，将所述待删除VNFM删除。
可选地，网络功能虚拟化编排器NFVO根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化的步骤包括：
所述NFVO根据所述VNFM pool管理的VNFM初始个数，对所述VNFM Pool中的每个VNFM进行实例化操作，并将实例化的VNFM加入所述VNFM Pool；
对所述VNFM pool初始化的步骤之后，该方法还包括：
将实例化的VNF归属到一个或多个正常的VNFM上。
可选地，所述NFVO监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，则将该失效的VNFM管理的各VNF归属到一个或多个正常的VNFM上的步骤包括：
所述NFVO监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，在所述VNFM pool中新增一个VNFM；
对该失效的VNFM管理的VNF进行下述操作：在所有正常的VNFM中找到管理的VNF数最小的VNFM作为该VNF的失效接管VNFM；将该VNF归属到所述失效接管VNFM；
当所述失效的VNFM管理的所有VNF均归属到正常的VNFM后，删除该失效的VNFM。
一种虚拟化网络功能管理的装置，所述装置包括配置模块、监测模块和处理模块，其中：
所述配置模块设置成：根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化；其中，所述配置信息包括所述VNFM pool管理的VNFM初始个数、所述VNFM pool管理的VNFM最大个数及所述VNFM pool中每个VNFM管理的VNF最大个数；
所述监测模块设置成：监测所述VNFM pool中每个VNFM的状态；
所述处理模块设置成：若监测模块监测到一VNFM失效时，则将该失效的VNFM管理的VNF归属到一个或多个正常的VNFM上。
可选地，每个VNFM管理的VNF最大个数相同；
所述监测模块还设置成：监测所述VNFM pool的状态；
所述处理模块还设置成：查找VNFM pool中管理VNF数最小的VNFM，如果该VNFM管理的VNF数达到VNFM管理的VNF最大个数，则获取所述VNFM Pool当前管理的VNFM数,若当前管理的VNFM数小于VNFM Pool配置的VNFM最大个数，则在所述VNFM pool中新增一个VNFM。
可选地，每个VNFM管理的VNF最大个数相同；
所述监测模块还设置成：监测所述VNFM pool管理的VNFM的数量；
所述处理模块还设置成：在所述监测模块获取的当前VNFM pool管理的VNFM个数大于所述VNFM Pool管理的VNFM初始个数时，查找管理的VNF数最大的VNFM，若该管理的VNF数最大的VNFM管理的VNF数小于VNFM管理的VNF最大个数的一半，则将管理的VNF数最小的VNFM作为待删除VNFM；
所述处理模块还设置成：对所述待删除VNFM管理的VNF做下述操作：在所有正常VNFM中找到管理的VNF数最小的VNFM作为该VNF的删除接管VNFM；将该VNF归属到所述删除接管VNFM；当所述待删除VNFM管理的所有VNF均归属到正常VNFM后，将所述待删除VNFM删除。
可选地，所述配置模块设置成按照如下方式根据虚拟化网络功能管理池 VNFM pool的配置信息，对所述VNFM pool初始化：
根据所述VNFM pool管理的VNFM初始个数，对所述VNFM Pool中的每个VNFM进行实例化操作，并将实例化的VNFM加入所述VNFM Pool；
所述配置模块还设置成：在所述配置模块对所述VNFM pool初始化后，将实例化的VNF归属到一个或多个正常的VNFM上。
可选地，所述处理模块设置成按照如下方式将失效VNFM管理的各VNF归属到其它正常的VNFM上：
所述监测模块监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，所述处理模块在所述VNFM pool中新增一个VNFM；
对该失效的VNFM管理的VNF进行下述操作：在所有正常的VNFM中找到管理的VNF数最小的VNFM作为该VNF的失效接管VNFM；将该VNF归属到所述失效接管VNFM；
当所述失效的VNFM管理的所有VNF均归属到正常VNFM后，删除该失效的VNFM。
一种计算机程序，包括程序指令，当该程序指令被计算机执行时，使得该计算机可执行上述任意的虚拟化网络功能管理的方法。
一种载有所述的计算机程序的载体。
上述方案通过VNFM Pool，当单个VNFM失效时只影响其归属的VNF,并且失效VNFM管理的VNF能够自动迁移到其他正常的VNFM,提高了虚拟化网络的系统可靠性，虚拟化网络功能管理功能对VNF管理分担到了VNFMPool的各个VNFM上；同时，能够根据负荷处理状态，相应地增加或删除VNFM Pool的VNFM实例对象数,在低负荷时达到了节省系统资源的效果,在超负荷时满足高性能处理能力的要求。
附图概述
图1为相关技术中ETSI NFV ISG规范的NFVO/VNFM/VNF关系图；
图2为本发明实施例中NFVO/VNFM Pool/VNF关系图；
图3为本发明实施例一中的NFVO初始化VNFM Pool流程图；
图4为本发明实施例二中的NFVO实例化VNF流程图；
图5为本发明实施例三中NFVO操作VNF流程图；
图6为本发明实施例四中NFVO增加VNFM流程图；
图7为本发明实施例五中NFVO删除VNFM流程图；
图8为本发明实施例六中失效VNFM处理流程图；
图9为本发明一种虚拟化网络功能管理的装置的结构示意图。
本发明的较佳实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
为解决电信设备实现NFV对网络虚拟化功能管理的高性能，高可靠性的要求,本发明实施例实现了使用了VNFM Pool实现网络虚拟化功能管理的方法。如图2所示，其核心思想为：使用一个包含多个VNFM的VNFM Pool功能实体来实现网络虚拟化功能管理功能；VNFM Pool对VNF的管理功能自动分配到VNFM Pool内的VNFM执行；当VNFM Pool的VNFM失效时,使用创建新VNFM实例对象删除失效VNFM实例对象的方式恢复失效VNFM,失效VNFM管理的VNF迁移到其他正常的VNFM管理。
本申请实施例提供一种虚拟化网络功能管理的方法，所述方法包括：
步骤一、网络功能虚拟化编排器NFVO根据虚拟化网络功能管理池VNFM pool的配置信息，对VNFM pool初始化；配置信息包括VNFM pool管理的虚拟化网络功能VNFM初始个数、VNFM pool管理的VNFM最大个数及各VNFM管理的VNF最大个数；
VNFM pool管理的VNFM最大个数即VNFM pool最多可管理的VNFM个数，VNFM管理的VNF最大个数即VNFM最多可管理的VNF个数。
网络功能虚拟化编排器NFVO根据虚拟化网络功能管理池VNFM pool的配置信息，对VNFM pool初始化具体包括：根据VNFM pool管理的VNFM初始个数，NFVO对VNFM Pool中的各VNFM进行实例化操作，并将实例化的VNFM加入VNFM Pool。对VNFM pool初始化后还将实例化的VNF归属到一个或多个所述VNFM上。
步骤二、NFVO监测所述VNFM pool中各VNFM的状态，若监测到VNFM失效时，则将失效VNFM管理的各VNF归属到一个或多个正常VNFM上
该步骤包括：
NFVO监测VNFM pool中各VNFM的状态，若监测到VNFM失效时，在VNFM pool中新增一个VNFM；
对该失效VNFM管理的各VNF依次进行下述操作：在将所有正常VNFM中找到管理VNF数最小的VNFM作为上述VNF的失效接管VNFM；将所述失效VNFM管理的该VNF归属到所述失效接管VNFM；
当失效VNFM管理的各VNF均归属到其它正常VNFM后，删除该失效VNFM。
进一步，所述方法还包括：
步骤三、NFVO监测所述VNFM pool的状态；各VNFM管理的VNF最大个数相同；NFVO查找VNFM pool中管理的VNF数最小的VNFM；
如果VNFM pool中管理的VNF数最小的VNFM管理的VNF数达到VNFM管理的VNF最大个数，则获取VNFM Pool当前管理的VNFM数,若当前管理的VNFM数小于VNFM Pool配置的VNFM最大个数，则在VNFM pool中新增一个VNFM。
这样操作的目的是监测是否需要增加VNFM,，举例而言，VNFM最大VNF个数是10个,VNFM Pool有5个VNFM,当全部VNFM都管理10个VNF时就满足上述监测条件了。
需要说明的是，各VNFM管理的VNF最大个数也可以不相同。如果各VNFM管理的VNF最大个数不相同，可以根据各VNFM管理的VNF最大个数相同的情况所采取的监测规则，相应的指定规则来判断何时需要新增 VNFM。
通常在VNFM pool中新增一个VNFM后，该新增的VNFM管理的VNF个数为0，此时如果需要新增VNF则可将该新增的实例化VNF归属到该新增的VNFM上。当然如果还存在其它管理VNF数为0的VNFM，也可以归属到其它VNFM上。在实际的操作中可以将新增的VNF归属到当前状态下管理VNF数最小的VNFM上，也可以按照其它规则选择所归属的VNFM。
步骤四、NFVO监测VNFM pool管理的VNFM的数量；
如果当前VNFM pool管理的VNFM个数大于VNFM Pool管理的VNFM初始个数，则查找管理VNF数最大的VNFM，若该VNFM管理的VNF数小于VNFM管理的VNF最大个数的一半，则将VNFM管理VNF数最小的VNFM作为待删除VNFM；
对待删除VNFM管理的各VNF依次进行下述操作：在所有正常VNFM中找到管理VNF数最小的VNFM作为该VNF的删除接管VNFM；将该VNF归属到所述删除接管VNFM；
当待删除VNFM管理的各VNF均归属到其它正常VNFM后，将待删除VNFM删除。
需要说明的是，在将失效VNFM管理的VNF归属到其它正常VNFM上，或者将待删除VNFM管理的VNF归属到其它正常VNFM上时，可以将待转移的VNF归属到相同的VNFM上，也可以归属到不同的VNFM上。同时，对于待转移VNF归属到哪个VNFM上，可以根据实际情况设定相应的规则。
此外，步骤三和四在步骤一后执行，与步骤二之间不限定先后顺序。
下面结合附图和具体实施例对本发明的技术方案的实施作进一步的详细阐述。
实施例一
如图3所示,由NFVO负责初始化VNFM Pool,具体包括以下流程:
步骤101,NFVO获取当前VNFM Pool配置信息,包括初始VNFM数,最大VNFM数,每个VNFM管理的最大VNF数等VNFM Pool配置；
步骤102-1,步骤102-2,…步骤102-n,NFVO逐个实例化VNFM Pool中的VNFM实例对象,直到VNFM Pool的VNFM实例数达到VNFM Pool配置的初始VNFM数。
步骤103,NFVO把实例化的VNFM实例对象加入到VNFM Pool中的VNFM列表。
实施例二
如图4所示,NFVO实例化VNF具体包括以下流程:
步骤201,NFVO按照VNFM Pool中VNFM管理的VNF数大小排序,分配一个管理VNF数最小的VNFM作为执行VNF实例化的VNFM；
步骤202,NFVO向被分配的VNFM发送实例化VNF请求消息；
步骤203,被分配的VNFM接收到实例化VNF请求消息,执行VNF实例化,被实例化VNF的归属VNFM为执行实例化VNF的VNFM,归属VNFM信息保存到VNF实例对象属性中；
步骤204,被分配的VNFM返回请求实例化VNF应答消息。
实施例三
如图5所示,NFVO操作VNF具体包括以下流程:
步骤301,NFVO按照VNF的归属VNFM属性定位到VNFM Pool中VNFM实例对象；
步骤302,NFVO向VNF归属VNFM发送操作VNF请求消息；
步骤303,VNF归属VNFM接收到操作VNF请求消息,执行请求的VNF操作；
步骤304,归属VNFM返回请求操作VNF应答消息。
实施例四
如图6所示,NFVO增加VNFM具体包括以下流程:
步骤401,NFVO监测VNFM Pool是否超负荷,具体方式为按照VNFM Pool中VNFM管理的VNF数大小排序,监测到管理VNF数最小的VNFM的VNF数已经达到了VNFM Pool配置的每个VNFM管理的最大VNFM数时执 行后续步骤，否则流程中止；
步骤402,NFVO确定是否可以新增VNFM,具体方式为获取当前VNFM Pool的VNFM数,如果当前VNFM Pool的VNFM数小于VNFM Pool配置的最大VNFM数,执行后续步骤,否则流程中止；
步骤403,NFVO创建一个新的VNFM实例对象；
步骤404,NFVO把新建VNFM加入到VNFM Pool的VNFM列表中。
实施例五
如图7所示,NFVO删除VNFM具体包括以下流程:
步骤501,NFVO确定是否需要删除VNFM,具体方式为获取当前VNFM Pool的VNFM数,如果当前VNFM Pool的VNFM数大于VNFM Pool配置的初始VNFM数,执行后续步骤,否则流程中止；
步骤502,NFVO监测VNFM Pool是否低负荷,具体方式为按照VNFM Pool中VNFM管理的VNF数大小排序,监测到管理VNF数最大的VNFM的VNF数小于VNFM Pool配置的每个VNFM管理的最大VNF数的一半时执行后续步骤,否则流程中止；
步骤503,NFVO获取需要删除的VNFM,具体方式为按照VNFM Pool中VNFM管理的VNF数大小排序,VNFM管理VNF数最小的VNFM为待删除VNFM；
步骤504,NFVO逐个更新待删除VNFM管理的VNF归属VNFM为其他VNFM,具体方式为以下子步骤:
步骤504-1,NFVO对VNFM Pool的VNFM除待删除VNFM外其他VNFM按照VNFM管理的VNF数大小排序,分配一个管理VNF数最小的VNFM作为接管VNF实例的VNFM；
步骤504-2,NFVO向接管VNF实例的VNFM发送更新VNF归属VNFM请求消息；
步骤504-3,VNFM接收到更新VNF归属VNFM请求消息,向对应VNF发送更新VNF归属VNFM消息；
步骤504-4,VNF收到更新VNF归属VNFM消息,修改自身的归属VNFM属性；
步骤504-5,VNF返回更新VNF归属VNFM应答消息，应答消息中包含VNF当前状态信息；
步骤504-6,VNFM收到更新VNF归属VNFM应答消息,保存该VNF的当前状态信息；
步骤504-7,VNFM向NFVO返回更新VNF归属VNFM请求应答消息；
步骤505，NFVO从VNFM Pool的VNFM列表删除VNFM，同时删除VNFM实例对象。
实施例六
如图8所示,失效VNFM处理具体包括以下流程:
步骤601,NFVO创建一个新的VNFM实例对象，加入到VNFM Pool的VNFM列表中；
步骤602,NFVO更新失效VNFM管理的VNF归属VNFM为其他正常VNFM,具体方式为以下子步骤:
步骤602-1,NFVO除失效VNFM按照VNFM管理的VNF数大小排序,分配一个管理VNF数最小的VNFM作为接管VNF实例的VNFM；
步骤602-2,NFVO向接管VNF实例的VNFM发送更新VNF归属VNFM请求消息；
步骤602-3,VNFM接收到更新VNF归属VNFM请求消息,向对应VNF发送更新VNF归属VNFM消息；
步骤602-4,VNF收到更新VNF归属VNFM消息,修改自身的归属VNFM属性；
步骤602-5,VNF返回更新VNF归属VNFM应答消息，应答消息中包含VNF当前状态信息；
步骤602-6,VNFM收到更新VNF归属VNFM应答消息,保存该VNF的当前状态信息；
步骤602-7,VNFM向NFVO返回更新VNF归属VNFM请求应答消息；
步骤603,NFVO从VNFM Pool的VNFM列表删除失效VNFM，同时删除失效VNFM实例对象。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。
本发明实施例还提供一种虚拟化网络功能管理的装置，所述装置包括：
配置模块，设置成：根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化；所述配置信息包括所述VNFM pool管理的VNFM初始个数,VNFM最大个数以及各VNFM管理的VNF最大个数；
监测模块，设置成：所述NFVO监测所述VNFM pool中各VNFM的状态；
处理模块，设置成：当监测模块监测到VNFM失效时，将失效VNFM管理的VNF归属到其它正常VNFM上。
可选地，
所述监测模块还设置成：所述NFVO监测所述VNFM pool的负荷状态；
所述处理模块还设置成：当所述监测模块监测到所述VNFM pool超负荷时，并根据所述配置信息确定能够新增VNFM，在所述VNFM pool中新增VNFM；以及，当所述监测模块监测到所述VNFM pool低负荷，并根据所述配置信息确定需要删除VNFM，在所述VNFM pool中删除VNFM。
可选地，
所述配置模块设置成：根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化是指：
根据所述VNFM pool管理的VNFM初始个数，所述NFVO对所述VNFM Pool中的各VNFM进行实例化操作，并将实例化的VNFM加入所述VNFM Pool。
可选地，
所述处理模块设置成：当监测模块监测到VNFM失效时，将失效VNFM管理的VNF归属到其它正常VNFM上是指：
所述NFVO监测所述VNFM pool中各VNFM的状态，若监测到VNFM失效时，将所有正常VNFM中管理VNF数最小的VNFM作为接管VNFM；
将所述失效VNFM管理的VNF归属到所述失效接管VNFM，并删除该失效VNFM。
可选地，
所述处理模块设置成：当所述监测模块监测到所述VNFM pool超负荷时，并根据所述配置信息确定能够新增VNFM，在所述VNFM pool中新增VNFM是指：
查找管理VNF数最小的VNFM，如果该VNFM管理的VNF数达到VNFM管理的最大VNF数，则所述VNFM pool超负荷；
获取所述VNFM Pool当前管理的VNFM数,如果当前管理的VNFM数小于VNFM Pool配置的最大VNFM数，则在所述VNFM pool中新增一个VNFM；
所述处理模块设置成：当所述监测模块监测到所述VNFM pool低负荷，并根据所述配置信息确定需要删除VNFM，在所述VNFM pool中删除VNFM是指：
查找管理VNF数最大的VNFM，如果该VNFM管理的VNF数小于VNFM管理的最大VNF数的一半，则所述VNFM pool低负荷；
将VNFM管理VNF数最小的VNFM作为待删除VNFM；获取当前状态下的所述接管VNFM，将所述待删除VNFM管理的VNF归属到所述接管VNFM。
同时，如图9所示，本发明实施例还提供一种虚拟化网络功能管理的装置，该装置可以设置于网络功能虚拟化编排器NFVO上，所述装置包括：
配置模块11，设置成：根据虚拟化网络功能管理池VNFM pool的配置信息，对VNFM pool初始化；配置信息包括VNFM pool管理的VNFM初始个 数、VNFM pool管理的VNFM最大个数及各VNFM管理的VNF最大个数；
监测模块12，设置成：监测VNFM pool中各VNFM的状态；
处理模块13，设置成：若监测模块12监测到VNFM失效时，则将失效VNFM管理的各VNF归属到一个或多个正常VNFM上。
可选地，
各VNFM管理的VNF最大个数相同；
监测模块12还设置成：监测所述VNFM pool的状态；
处理模块13还设置成：查找VNFM pool中管理VNF数最小的VNFM，如果该VNFM管理的VNF数达到VNFM管理的VNF最大个数，则获取所述VNFM Pool当前管理的VNFM数,若当前管理的VNFM数小于VNFM Pool配置的VNFM最大个数，则在VNFM pool中新增一个VNFM。
可选地，
监测模块12还设置成：监测所述VNFM pool管理的VNFM的数量；
处理模块13还设置成：在监测模块获取的当前VNFM pool管理的VNFM个数大于所述VNFM Pool管理的VNFM初始个数时，查找管理VNF数最大的VNFM，若该VNFM管理的VNF数小于VNFM管理的VNF最大个数的一半，则将VNFM管理VNF数最小的VNFM作为待删除VNFM；
处理模块13还设置成：对待删除VNFM管理的各VNF依次做下述操作：在所有正常VNFM中找到管理VNF数最小的VNFM作为该VNF的删除接管VNFM；将该VNF归属到删除接管VNFM；以及还设置成：当待删除VNFM管理的各VNF均归属到其它正常VNFM后，将待删除VNFM删除。
可选地，
配置模块11设置成：根据虚拟化网络功能管理池VNFM pool的配置信息，对VNFM pool初始化是指：
根据VNFM pool管理的VNFM初始个数，所述NFVO对所述VNFM Pool中的各VNFM进行实例化操作，并将实例化的VNFM加入所述VNFM Pool；
配置模块11还设置成：在对VNFM pool初始化后将实例化的VNF归属 到一个或多个VNFM上。
可选地，
处理模块13设置成：若监测模块监测到VNFM失效时，则将失效VNFM管理的各VNF归属到其它正常VNFM上是指：
NFVO监测所述VNFM pool中各VNFM的状态，若监测到VNFM失效时，在VNFM pool中新增一个VNFM；
对该失效VNFM管理的各VNF依次进行下述操作：在所有正常VNFM中找到管理VNF数最小的VNFM作为该VNF的失效接管VNFM；将该VNF归属到所述失效接管VNFM；
当失效VNFM管理的各VNF均归属到其它正常VNFM后，删除该失效VNFM。
本发明实施例还公开了一种计算机程序，包括程序指令，当该程序指令被计算机执行时，使得该计算机可执行上述任意的虚拟化网络功能管理的方法。
本发明实施例还公开了一种载有所述的计算机程序的载体。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现，相应地，上述实施例中的各模块/模块可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本申请不限制于任何特定形式的硬件和软件的结合。
以上所述仅为本申请的优选实施例而已，并不用于限制本申请，对于本领域的技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。
工业实用性
上述方案通过VNFM Pool，当单个VNFM失效时只影响其归属的VNF,并且失效VNFM管理的VNF能够自动迁移到其他正常的VNFM,提高了虚拟化网络的系统可靠性，虚拟化网络功能管理功能对VNF管理分担到了VNFM Pool的各个VNFM上；同时，能够根据负荷处理状态，相应地增加或删除VNFM Pool的VNFM实例对象数,在低负荷时达到了节省系统资源的效果,在超负荷时满足高性能处理能力的要求。因此本发明具有很强的工业实用性。

Claims (12)

  1. 一种虚拟化网络功能管理的方法，所述方法包括：
    网络功能虚拟化编排器NFVO根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化；其中，所述配置信息包括所述VNFM pool管理的VNFM初始个数、所述VNFM pool管理的VNFM最大个数和所述VNFM pool中每个VNFM管理的VNF最大个数；
    所述NFVO监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，则将该失效的VNFM管理的VNF归属到一个或多个正常的VNFM上。
  2. 如权利要求1所述的虚拟化网络功能管理的方法，其中，
    每个VNFM管理的VNF最大个数相同
    所述方法还包括：
    所述NFVO监测所述VNFM pool的状态；
    所述NFVO查找所述VNFM pool中管理的VNF数最小的VNFM；
    如果该管理的VNF数最小的VNFM管理的VNF数达到VNFM管理的VNF最大个数，则获取所述VNFM Pool当前管理的VNFM数,若当前管理的VNFM数小于所述VNFM Pool配置的VNFM最大个数，则在所述VNFM pool中新增一个VNFM。
  3. 如权利要求1所述的虚拟化网络功能管理的方法，其中，
    每个VNFM管理的VNF最大个数相同；
    所述方法还包括：
    所述NFVO监测所述VNFM pool管理的VNFM的数量；
    如果当前VNFM pool管理的VNFM个数大于所述VNFM Pool管理的VNFM初始个数，则查找管理的VNF数最大的VNFM，若管理的VNF数最大的VNFM管理的VNF数小于VNFM管理的VNF最大个数的一半，则将管理的VNF数最小的VNFM作为待删除VNFM；
    对所述待删除VNFM管理的VNF进行下述操作：在所有正常VNFM中 找到管理的VNF数最小的VNFM作为该VNF的删除接管VNFM；将该VNF归属到所述删除接管VNFM；
    当所述待删除VNFM管理的所有VNF均归属到正常VNFM后，将所述待删除VNFM删除。
  4. 如权利要求3所述的方法，其中，网络功能虚拟化编排器NFVO根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化的步骤包括：
    所述NFVO根据所述VNFM pool管理的VNFM初始个数，对所述VNFM Pool中的每个VNFM进行实例化操作，并将实例化的VNFM加入所述VNFM Pool；
    对所述VNFM pool初始化的步骤之后，该方法还包括：
    将实例化的VNF归属到一个或多个正常的VNFM上。
  5. 如权利要求4所述的虚拟化网络功能管理的方法，其中，所述NFVO监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，则将该失效的VNFM管理的各VNF归属到一个或多个正常的VNFM上的步骤包括：
    所述NFVO监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，在所述VNFM pool中新增一个VNFM；
    对该失效的VNFM管理的VNF进行下述操作：在所有正常的VNFM中找到管理的VNF数最小的VNFM作为该VNF的失效接管VNFM；将该VNF归属到所述失效接管VNFM；
    当所述失效的VNFM管理的所有VNF均归属到正常的VNFM后，删除该失效的VNFM。
  6. 一种虚拟化网络功能管理的装置，所述装置包括配置模块、监测模块和处理模块，其中：
    所述配置模块设置成：根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化；其中，所述配置信息包括所述VNFM pool管理的VNFM初始个数、所述VNFM pool管理的VNFM最大个数及所述 VNFM pool中每个VNFM管理的VNF最大个数；
    所述监测模块设置成：监测所述VNFM pool中每个VNFM的状态；
    所述处理模块设置成：若监测模块监测到一VNFM失效时，则将该失效的VNFM管理的VNF归属到一个或多个正常的VNFM上。
  7. 如权利要求6所述的虚拟化网络功能管理的装置，其中：
    每个VNFM管理的VNF最大个数相同；
    所述监测模块还设置成：监测所述VNFM pool的状态；
    所述处理模块还设置成：查找VNFM pool中管理VNF数最小的VNFM，如果该VNFM管理的VNF数达到VNFM管理的VNF最大个数，则获取所述VNFM Pool当前管理的VNFM数,若当前管理的VNFM数小于VNFM Pool配置的VNFM最大个数，则在所述VNFM pool中新增一个VNFM。
  8. 如权利要求6所述的虚拟化网络功能管理的装置，其中：
    每个VNFM管理的VNF最大个数相同；
    所述监测模块还设置成：监测所述VNFM pool管理的VNFM的数量；
    所述处理模块还设置成：在所述监测模块获取的当前VNFM pool管理的VNFM个数大于所述VNFM Pool管理的VNFM初始个数时，查找管理的VNF数最大的VNFM，若该管理的VNF数最大的VNFM管理的VNF数小于VNFM管理的VNF最大个数的一半，则将管理的VNF数最小的VNFM作为待删除VNFM；
    所述处理模块还设置成：对所述待删除VNFM管理的VNF做下述操作：在所有正常VNFM中找到管理的VNF数最小的VNFM作为该VNF的删除接管VNFM；将该VNF归属到所述删除接管VNFM；当所述待删除VNFM管理的所有VNF均归属到正常VNFM后，将所述待删除VNFM删除。
  9. 如权利要求8所述的虚拟化网络功能管理的装置，其中，所述配置模块设置成按照如下方式根据虚拟化网络功能管理池VNFM pool的配置信息，对所述VNFM pool初始化：
    根据所述VNFM pool管理的VNFM初始个数，对所述VNFM Pool中的 每个VNFM进行实例化操作，并将实例化的VNFM加入所述VNFM Pool；
    所述配置模块还设置成：在所述配置模块对所述VNFM pool初始化后，将实例化的VNF归属到一个或多个正常的VNFM上。
  10. 如权利要求9所述的虚拟化网络功能管理的装置，其中：
    所述处理模块设置成按照如下方式将失效VNFM管理的各VNF归属到其它正常的VNFM上：
    所述监测模块监测所述VNFM pool中每个VNFM的状态，若监测到一VNFM失效时，所述处理模块在所述VNFM pool中新增一个VNFM；
    对该失效的VNFM管理的VNF进行下述操作：在所有正常的VNFM中找到管理的VNF数最小的VNFM作为该VNF的失效接管VNFM；将该VNF归属到所述失效接管VNFM；
    当所述失效的VNFM管理的所有VNF均归属到正常VNFM后，删除该失效的VNFM。
  11. 一种计算机程序，包括程序指令，当该程序指令被计算机执行时，使得该计算机可执行权利要求1-5中任一项所述的虚拟化网络功能管理的方法。
  12. 一种载有如权利要求11所述的计算机程序的载体。
PCT/CN2015/071338 2014-09-22 2015-01-22 一种虚拟化网络功能管理的方法和装置 WO2015131696A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/513,452 US10511506B2 (en) 2014-09-22 2015-01-22 Method and device for managing virtualized network function
EP15758107.5A EP3200393B1 (en) 2014-09-22 2015-01-22 Method and device for virtual network function management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410487818.0A CN105429776B (zh) 2014-09-22 2014-09-22 一种虚拟化网络功能管理的方法和系统
CN201410487818.0 2014-09-22

Publications (1)

Publication Number Publication Date
WO2015131696A1 true WO2015131696A1 (zh) 2015-09-11

Family

ID=54054544

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/071338 WO2015131696A1 (zh) 2014-09-22 2015-01-22 一种虚拟化网络功能管理的方法和装置

Country Status (4)

Country Link
US (1) US10511506B2 (zh)
EP (1) EP3200393B1 (zh)
CN (1) CN105429776B (zh)
WO (1) WO2015131696A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20170043966A (ko) * 2015-10-14 2017-04-24 한국전자통신연구원 Nfv 시스템 및 vnfm 연동 방법
WO2017107098A1 (zh) * 2015-12-23 2017-06-29 华为技术有限公司 虚拟网络功能vnf的参数配置方法、装置和系统
WO2017148326A1 (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 一种资源管理方法和装置
WO2019012485A1 (en) * 2017-07-14 2019-01-17 Telefonaktiebolaget Lm Ericsson (Publ) METHOD FOR PLACING VNF MANAGERS IN LARGE-SCALE AND DISTRIBUTED NFV SYSTEMS
US20190109762A1 (en) * 2016-03-15 2019-04-11 Nokia Solutions And Networks Oy Conflict resolution in network virtualization scenarios
US10277687B2 (en) 2015-11-16 2019-04-30 At&T Intellectual Property I, L.P. Master service orchestration of virtual networking functions
EP3582453A4 (en) * 2017-02-01 2020-04-01 Nec Corporation ADMINISTRATIVE SYSTEM, ADMINISTRATIVE DEVICE, ADMINISTRATIVE PROCEDURE AND PROGRAM

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10027535B1 (en) * 2013-09-27 2018-07-17 Juniper Networks, Inc. Systems and methods for managing device configurations at various levels of abstraction
US10116514B1 (en) * 2015-03-30 2018-10-30 Amdocs Development Limited System, method and computer program for deploying an orchestration layer for a network based on network function virtualization (NFV)
US20170302531A1 (en) * 2014-09-30 2017-10-19 Hewlett Packard Enterprise Development Lp Topology based management with compliance policies
EP3223456B1 (en) 2016-03-24 2018-12-19 Alcatel Lucent Method for migration of virtual network function
EP3413511B1 (en) * 2016-04-27 2020-11-04 Huawei Technologies Co., Ltd. Vnfm determining method and network function virtualization orchestrator
CN107786352B (zh) * 2016-08-24 2022-04-15 中兴通讯股份有限公司 一种管理网络功能虚拟化管理编排实体的方法和装置
CN109391483A (zh) * 2017-08-04 2019-02-26 中国电信股份有限公司 网络实例化方法、网络功能虚拟化编排器和系统
CN107682185A (zh) * 2017-09-26 2018-02-09 中国联合网络通信集团有限公司 Mano管理方法及装置
JP6973300B2 (ja) * 2018-06-04 2021-11-24 日本電信電話株式会社 サービスチェイン設計装置、サービスチェイン設計方法、および、サービスチェイン設計プログラム
US10880370B2 (en) 2018-11-27 2020-12-29 At&T Intellectual Property I, L.P. Virtual network manager system
WO2021121595A1 (en) * 2019-12-19 2021-06-24 Telefonaktiebolaget Lm Ericsson (Publ) Discovering an instance of a virtual network function
CA3196912A1 (en) * 2020-10-28 2022-05-05 Ping Zhou Methods and apparatuses for instantiation of ns or vnf

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101183984A (zh) * 2007-12-14 2008-05-21 华为技术有限公司 网管系统、管理方法及设备
US20100054132A1 (en) * 2008-08-26 2010-03-04 Fujitsu Limited Communication apparatus and method for terminating a maintenance message
CN102204187A (zh) * 2011-04-28 2011-09-28 华为技术有限公司 一种虚拟网络迁移方法、相关装置以及系统
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6609213B1 (en) * 2000-08-10 2003-08-19 Dell Products, L.P. Cluster-based system and method of recovery from server failures
US9319282B2 (en) * 2005-02-28 2016-04-19 Microsoft Technology Licensing, Llc Discovering and monitoring server clusters
US7607129B2 (en) * 2005-04-07 2009-10-20 International Business Machines Corporation Method and apparatus for using virtual machine technology for managing parallel communicating applications
US8141075B1 (en) * 2006-05-08 2012-03-20 Vmware, Inc. Rule engine for virtualized desktop allocation system
US20150180748A1 (en) * 2013-12-20 2015-06-25 Futurewei Technologies Inc. METHOD AND APPARATUS OF WebRTC MEDIA CONTROL
US10594619B2 (en) * 2014-06-23 2020-03-17 Oracle International Corporation System and method for supporting configuration of dynamic clusters in a multitenant application server environment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101183984A (zh) * 2007-12-14 2008-05-21 华为技术有限公司 网管系统、管理方法及设备
US20100054132A1 (en) * 2008-08-26 2010-03-04 Fujitsu Limited Communication apparatus and method for terminating a maintenance message
CN102204187A (zh) * 2011-04-28 2011-09-28 华为技术有限公司 一种虚拟网络迁移方法、相关装置以及系统
CN104050045A (zh) * 2014-06-27 2014-09-17 华为技术有限公司 基于磁盘io的虚拟资源分配方法及装置

Non-Patent Citations (1)

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

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102021342B1 (ko) * 2015-10-14 2019-09-16 한국전자통신연구원 Nfv 시스템 및 vnfm 연동 방법
KR20170043966A (ko) * 2015-10-14 2017-04-24 한국전자통신연구원 Nfv 시스템 및 vnfm 연동 방법
US11128719B2 (en) 2015-11-16 2021-09-21 At&T Intellectual Property I, L.P. Master service orchestration of virtual networking functions
US10277687B2 (en) 2015-11-16 2019-04-30 At&T Intellectual Property I, L.P. Master service orchestration of virtual networking functions
WO2017107098A1 (zh) * 2015-12-23 2017-06-29 华为技术有限公司 虚拟网络功能vnf的参数配置方法、装置和系统
WO2017148326A1 (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 一种资源管理方法和装置
US20190109762A1 (en) * 2016-03-15 2019-04-11 Nokia Solutions And Networks Oy Conflict resolution in network virtualization scenarios
US11570044B2 (en) * 2016-03-15 2023-01-31 Nokia Solutions And Networks Oy Conflict resolution in network virtualization scenarios
US12119988B2 (en) 2016-03-15 2024-10-15 Nokia Solutions And Networks Oy Conflict resolution in network virtualization scenarios
EP3582453A4 (en) * 2017-02-01 2020-04-01 Nec Corporation ADMINISTRATIVE SYSTEM, ADMINISTRATIVE DEVICE, ADMINISTRATIVE PROCEDURE AND PROGRAM
US11397605B2 (en) 2017-02-01 2022-07-26 Nec Corporation Management system, management apparatus, management method, and program
WO2019012485A1 (en) * 2017-07-14 2019-01-17 Telefonaktiebolaget Lm Ericsson (Publ) METHOD FOR PLACING VNF MANAGERS IN LARGE-SCALE AND DISTRIBUTED NFV SYSTEMS
US11032135B2 (en) 2017-07-14 2021-06-08 Telefonaktiebolaget Lm Ericsson (Publ) Method for VNF managers placement in large-scale and distributed NFV systems

Also Published As

Publication number Publication date
US10511506B2 (en) 2019-12-17
US20170302543A1 (en) 2017-10-19
EP3200393A4 (en) 2017-09-06
CN105429776B (zh) 2020-06-09
EP3200393A1 (en) 2017-08-02
CN105429776A (zh) 2016-03-23
EP3200393B1 (en) 2018-12-26

Similar Documents

Publication Publication Date Title
WO2015131696A1 (zh) 一种虚拟化网络功能管理的方法和装置
US12020055B2 (en) VNF service instantiation method and apparatus
US10701139B2 (en) Life cycle management method and apparatus
US10713071B2 (en) Method and apparatus for network function virtualization
CN107924383B (zh) 用于网络功能虚拟化资源管理的系统和方法
CN105376303B (zh) 一种Docker实现系统及其通信方法
CN104410672B (zh) 网络功能虚拟化应用升级的方法、转发业务的方法及装置
US20190089588A1 (en) Network function instance management method and related device
US11070541B2 (en) Certificate management method and apparatus in network functions virtualization architecture
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
CN107005426B (zh) 一种虚拟网络功能的生命周期管理方法及装置
WO2020011214A1 (zh) 管理虚拟化资源的方法和装置
US10681003B2 (en) Rebalancing internet protocol (IP) addresses using distributed IP management
CN109428764B (zh) 虚拟网络功能的实例化方法
WO2018137520A1 (zh) 一种业务恢复方法及装置
CN103595801A (zh) 一种云计算系统及其虚拟机实时监控方法
WO2016183832A1 (zh) 一种网络业务实例化的方法及设备
CN113918268A (zh) 一种多租户管理方法及装置
CN109960579B (zh) 一种调整业务容器的方法及装置
CN110855739B (zh) 一种基于容器技术的异地及异构资源统一管理方法及系统
CN116724543A (zh) 容器集群的管理方法和装置
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
CN112889247B (zh) Vnf服务实例化方法及装置
CN111581203A (zh) 信息处理方法、装置及存储介质
EP3893438B1 (en) Vnf service instantiation method and device

Legal Events

Date Code Title Description
REEP Request for entry into the european phase

Ref document number: 2015758107

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015758107

Country of ref document: EP

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

Ref document number: 15758107

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15513452

Country of ref document: US