WO2015131671A1 - 目标资源占用情况的处理方法及装置 - Google Patents

目标资源占用情况的处理方法及装置 Download PDF

Info

Publication number
WO2015131671A1
WO2015131671A1 PCT/CN2015/070805 CN2015070805W WO2015131671A1 WO 2015131671 A1 WO2015131671 A1 WO 2015131671A1 CN 2015070805 W CN2015070805 W CN 2015070805W WO 2015131671 A1 WO2015131671 A1 WO 2015131671A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual machine
standby
vnfc
vnf
vnfm
Prior art date
Application number
PCT/CN2015/070805
Other languages
English (en)
French (fr)
Inventor
陶运锋
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2015131671A1 publication Critical patent/WO2015131671A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems
    • H04L12/6418—Hybrid transport

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for processing a target resource occupancy situation.
  • Network Function Virtualization technology refers to the traditional network function, such as Proxy call session control function (P-CSCF), query call session control function entity. (Interrogating call session control function, referred to as I-CSCF), Serving call session control function (S-CSCF), Home subscriber server (HSS) and application server ( Virtualization of the application server (referred to as AS), and the virtualized network function component (VNFC) is deployed on the cloud virtual machine to realize the virtualization of the network function. It is a virtualized network function (VNF). Virtualization of network functions can bring the following technical advantages:
  • the network function has the elastic expansion function, the network function needs to occupy resources and improve the resource utilization. At the same time, when the load is low, some general-purpose servers are closed, so it is more green and energy-saving.
  • NFV Network function elastic scaling
  • the first type automatic triggering, that is, the VNF can dynamically adjust its own resource occupation according to its own load situation;
  • the second type is manually triggered, that is, the user can manually adjust the resource usage of the VNF according to management needs.
  • the first type the horizontal adjustment, that is, the way of adding or deleting a virtual machine, is called scale out/scale in;
  • the second, vertical adjustment that is, by adjusting the way the virtual machine occupies resources, is called scale up/scale down.
  • ETSI European Telecommunication Standardization Association
  • NFVO Network Functions Virtualization Orchestrator
  • FIG. 1 is a VNF elastic expansion flowchart of resource allocation performed by NFVO in the ETSI specification according to the related art. As shown in FIG. 1, the process may include the following processing steps:
  • Step S101 The sender (for example, the OSS) sends an elastic extension request to the NFVO.
  • the sender for example, the OSS
  • Step S102 The NFVO performs a validity check on the elastic scalability request, and checks whether the requirement conforms to the policy configuration.
  • Step S103 NFVO finds the VNFM corresponding to the VNF, and if the VNF does not have a corresponding VNFM, the NFVO creates a new VNFM;
  • Step S104 Before performing the elastic action, the NFVO performs feasibility check on the elastic scalability request and reserves related resources, and the whole step S104 is optional. If S104 is executed, it must be all executed. S104 further includes the following sub-steps:
  • Step S104a The NFVO requests the VNFM to perform a feasibility check on the elastic scalability request
  • Step S104b The VNFM performs any necessary preparation work, which may include modifying/complementing the entry of the elastic scalability request according to the VNF specific restriction;
  • Step S104c The VNFM returns an updated elastic scalability request to the NFVO.
  • Step S104d NFVO requests VIM to check the availability of resources (computing, storage, network) and reserve these resources;
  • Step S104e The VIM checks the availability of resources (computing, storage, network) and reserves these resources;
  • Step S104f The VIM returns the result of the resource reservation to the NFVO;
  • Step S105 The NFVO sends an elastic scaling request to the VNFM, including the elastic scaling data, and if the step S104 has been executed, the resource reservation information is further included;
  • Step S106 The VNFM performs any required preparation work: verifying the elastic scalability request, and performing parameter verification, and may further include modifying or supplementing the input of the elastic expansion request according to the specific limitation of the VNF;
  • step S104b if step S104 has been performed, skip this step;
  • Step S107 The VNFM replies to the NFVO with a resource change response
  • Step S108 NFVO sends a resource (computing, storage, network) change request to the VIM;
  • Step S109 The VIM modifies the VNF internal network as needed
  • Step S110 The VIM instantiates the new virtual machine according to the need and connects to the internal network.
  • Step S111 The VIM returns a resource change completion response to the NFVO;
  • Step S112 NFVO notifies that the VNFM resource change is completed
  • Step S113 The VNFM responds to the NFVO response
  • Step S114 NFVO responds to the request to respond to the flexible application successfully.
  • VNFM The VNF Manager (VNFM, referred to as VNFM) performs the flexible scaling process of resource allocation.
  • VNFM The content of this part can also be specifically divided into the following technical chapters:
  • VNFM is a VNF automatic stretch flow chart for performing resource allocation by the VNFM in the ETSI specification according to the related art. As shown in FIG. 2, the process may include the following processing steps:
  • Step S201 The VNFM collects measurement data from the VNF (application related);
  • Step S202 The VNFM detects that the system load exceeds the elastic extension threshold, triggering the elastic extension request;
  • Step S203 The VNFM requests the NFVO to check the elastic extension request
  • Step S204 The NFVO determines to perform the elastic extension, calculates the resources (computation, storage, and network) required for the elastic extension according to the capacity database of the VNF and the VNF template, and checks whether there are sufficient resources at present;
  • Step S205 The NFVO authorizes the VNFM to flexibly extend the VNF;
  • Step S206 The VNFM sends a request to the VIM to create and start the VM according to the indication of the NFVO.
  • Step S207 The VIM instantiates and starts a new VM, and returns a successful response to the VNFM.
  • Step S208 The VNFM configures related data on the VNF
  • Step S209 the VNFM returns a resilient response to the NFVO;
  • Step S210 The VNFM notifies the EM that the VNF capacity has changed
  • Step S211 NFVO saves a mapping relationship between the VNF and the VIM resource pool
  • Step S212 EM and VNFM update VNF related data
  • Step S213 The EM configures VNF related application data.
  • FIG. 3 is a flow chart of an EM-initiated VNF elasticity extension performed by a VNFM in accordance with the related art ETSI specification. As shown in FIG. 3, the process may include the following processing steps:
  • Step S301 The manual operator manually performs the elastic stretch request on the EM, or the EM triggers the automatic elastic stretch request according to the detection result;
  • Step S302 The EM sends an elastic extension request to the VNFM.
  • Step S303 The VNFM requests the NFVO to check the elastic extension request
  • Step S304 The NFVO determines to perform the elastic extension. According to the capacity database of the VNF and the VNF template, the resources (computation, storage, and network) required for the elastic extension are calculated, and whether there are sufficient resources at present;
  • Step S305 NFVO authorizes the VNFM to elastically extend the VNF
  • Step S306 The VNFM sends a request to the VIM to create and start the VM according to the indication of the NFVO.
  • Step S307 The VIM instantiates and starts a new VM, and returns a successful response to the VNFM.
  • Step S308 The VNFM configures related data on the VNF.
  • Step S309 the VNFM returns a resilient response to the NFVO;
  • Step S310 The VNFM notifies the EM that the VNF capacity has changed
  • Step S311 NFVO saves a mapping relationship between the VNF and the VIM resource pool
  • Step S312 M and VNFM update VNF related data
  • Step S313 The EM configures VNF related application data.
  • VNF automatic elastic contraction flowchart for performing resource allocation by a VNFM in the ETSI specification according to the related art. As shown in FIG. 4, the method may include the following processing steps:
  • Step S401 The VNFM collects measurement data from the VNF (application related);
  • Step S402 The VNFM detects that the system load is lower than the elastic contraction threshold, and triggers the elastic contraction request;
  • Step S403 The VNFM requests the NFVO to check the elastic contraction request
  • Step S404 NFVO decides to perform elastic contraction according to the configuration policy.
  • Step S405 The NFVO authorizes the VNFM to elastically shrink the VNF;
  • Step S406 The VNF gracefully closes the VNFC (no effect on the ongoing service);
  • Step S407 When there is no load on the VNFC (VM) to be deleted, the VNFM requests the VIM to delete the VM;
  • Step S408 The VIM deletes the VM and notifies the VNFM
  • Step S409 The VNFM notifies the NFVO that the elastic contraction is successful
  • Step S410 The VNFM notifies the EM that the VNF capacity is elastically contracted successfully
  • Step S411 NFVO updates the mapping relationship between the VNF and the VIM resource pool
  • Step S412 The EM and the VNFM update the VNF related data.
  • FIG. 5 is an EM-initiated VNF elastic contraction flowchart for performing resource allocation by a VNFM according to the related art. As shown in FIG. 5, the process may include the following processing steps:
  • Step S501 The manual operator manually performs the elastic contraction request on the EM, or the EM triggers the automatic elastic contraction request according to the detection result;
  • Step S502 The EM sends a trigger elastic contract request to the VNFM.
  • Step S503 The VNFM requests the NFVO to check the elastic contraction request
  • Step S504 NFVO decides to perform elastic contraction according to the configuration policy.
  • Step S505 The NFVO authorizes the VNFM to elastically shrink the VNF;
  • Step S506 The VNF gracefully closes the VNFC (no effect on the ongoing service);
  • Step S507 When there is no load on the VNFC (VM) to be deleted, the VNFM requests the VIM to delete the VM;
  • Step S508 The VIM deletes the VM and notifies the VNFM
  • Step S509 the VNFM notifies the NFVO that the elastic contraction is successful
  • Step S510 The VNFM notifies the EM that the VNF capacity is elastically contracted successfully
  • Step S511 NFVO updates the mapping relationship between the VNF and the VIM resource pool
  • Step S512 EM and VNFM update the VNF related data.
  • Figure 1 does not describe whether it requires elegant elastic expansion and how to elastically expand and contract
  • Figure 2 does not describe whether an elegant elastic extension is required and how it is stretched
  • Figure 3 does not describe whether it is necessary to stretch elastically and how to stretch it;
  • FIG. 4 describes the need for elegant elastic shrinkage, it does not describe how to elastically shrink
  • FIG. 5 describes the need for elegant elastic extension, it does not describe how to elastically stretch
  • the VNF is required to be gracefully and flexibly stretched to avoid impact on ongoing services.
  • the telecom operators generally require It is not possible to affect the ongoing call, registration, etc.
  • the virtual machine (VM) resource occupancy needs to be modified (calculation) , storage, network), after the VIM completes the modification of the resource usage of the VM, the VM needs to be restarted to take effect, and restarting the VM necessarily affects the ongoing service.
  • the embodiment of the present invention provides a method and a device for processing a target resource occupation situation, so as to at least solve the problem that the VNF elastic extension and/or elastic contraction in the related art cannot be performed normally under the condition of modifying the resource occupancy of the VM. Business problem.
  • a method of processing a target resource occupancy situation is provided.
  • the method for processing the target resource occupancy situation includes: acquiring a target resource occupancy situation of the VNF scale up and/or the scale down; and instructing the VIM to create or modify the standby virtual machine corresponding to the standby VNFC according to the target resource occupancy situation, where The standby virtual machine is set to take over the ongoing business of the active virtual machine corresponding to the primary VNFC.
  • the method further includes: after the standby virtual machine starts to start, triggering the primary virtual machine to synchronize data with the standby virtual machine; and the process of determining the synchronous data has entered a steady state.
  • the active virtual machine is triggered to be switched with the standby virtual machine, and after the switching operation ends, the active virtual machine is deleted.
  • the VIM is instructed to delete the active virtual machine.
  • the method further includes: after the standby virtual machine is restarted, detecting whether the process of synchronizing the data by the active virtual machine to the standby virtual machine has entered a steady state; After the steady state is entered, the active virtual machine is triggered to perform the switching. The standby virtual machine is restarted after the resource usage of the standby virtual machine is modified.
  • the VNF is notified to trigger the main virtual machine to perform the switching with the standby virtual machine, and the standby virtual machine takes over the current service of the active virtual machine.
  • the NFVO or VNFM instructs the VIM to create or modify the standby virtual machine according to the target resource occupancy.
  • a processing apparatus for a target resource occupancy situation is provided.
  • the processing device for the target resource occupancy situation includes: an obtaining module, configured to acquire a target resource occupancy situation of the VNF scale up and/or scale down; and a processing module configured to instruct the VIM to be created or modified according to the target resource occupancy status.
  • the standby virtual machine corresponding to the standby VNFC wherein the standby virtual machine is set to take over the service being performed by the active virtual machine corresponding to the primary VNFC.
  • the foregoing apparatus further includes: a first triggering module, configured to trigger the primary virtual machine to synchronize data with the standby virtual machine after the standby virtual machine starts to be started; and the second triggering module is configured to enter the process of determining synchronization data In the steady state, the active virtual machine is triggered to perform switching with the standby virtual machine, and after the switching operation ends, the active virtual machine is deleted.
  • a first triggering module configured to trigger the primary virtual machine to synchronize data with the standby virtual machine after the standby virtual machine starts to be started
  • the second triggering module is configured to enter the process of determining synchronization data
  • the active virtual machine is triggered to perform switching with the standby virtual machine, and after the switching operation ends, the active virtual machine is deleted.
  • the foregoing apparatus further includes: a detecting module, configured to: after the standby virtual machine is restarted, detecting whether the process of synchronizing data between the active virtual machine and the standby virtual machine has entered a steady state; and the third triggering module is configured to determine that the When the steady state is entered, the active virtual machine is triggered to perform the switching with the standby virtual machine. After the module is restarted, the backup virtual machine is restarted after the resource usage of the switched standby virtual machine is modified.
  • a detecting module configured to: after the standby virtual machine is restarted, detecting whether the process of synchronizing data between the active virtual machine and the standby virtual machine has entered a steady state
  • the third triggering module is configured to determine that the When the steady state is entered, the active virtual machine is triggered to perform the switching with the standby virtual machine.
  • the backup virtual machine is restarted after the resource usage of the switched standby virtual machine is modified.
  • the above device is located at NFVO or VNFM.
  • the target resource occupancy of the VNF scale up and/or the scale down is obtained; the VIM is created or modified according to the target resource occupation status, and the standby virtual machine is set to take over and
  • the service being developed by the active virtual machine corresponding to the VNFC of the primary VNFC solves the problem that the VNF cannot flexibly affect the normal service in the process of modifying the resource occupancy of the VM in the process of VNF elastic extension and/or elastic contraction.
  • An elegant scale up/scale down is achieved, increasing the usability of the VNF.
  • FIG. 1 is a flowchart of a VNF elastic extension of resource allocation performed by NFVO in an ETSI specification according to the related art
  • VNF 2 is a VNF automatic elastic flow chart of performing resource allocation by a VNFM in an ETSI specification according to the related art
  • FIG. 3 is a flowchart of an EM-initiated VNF elasticity extension performed by a VNFM in accordance with an ETSI specification of the related art
  • VNF automatic elastic reduction flowchart for performing resource allocation by a VNFM in an ETSI specification according to the related art
  • VNFM is an EM-initiated VNF elastic contraction flowchart for performing resource allocation by a VNFM according to the related art
  • FIG. 6 is a flowchart of a method for processing a target resource occupancy situation according to an embodiment of the present invention.
  • FIG. 7 is a flow chart of a VNF elastic scaling performed by NFVO to perform resource allocation according to a preferred embodiment of the present invention
  • VNF 8 is a VNF automatic elastic flow chart of performing resource allocation by a VNFM according to a preferred embodiment of the present invention.
  • FIG. 9 is an EM-initiated VNF resiliency flowchart for performing resource allocation by a VNFM in accordance with a preferred embodiment of the present invention.
  • VNF 10 is a VNF automatic elastic contraction flowchart for performing resource allocation by a VNFM according to a preferred embodiment of the present invention
  • FIG. 11 is an EM-initiated VNF elastic contraction flowchart for performing resource allocation by a VNFM according to a preferred embodiment of the present invention
  • FIG. 12 is a structural block diagram of a processing apparatus for a target resource occupancy situation according to an embodiment of the present invention.
  • FIG. 13 is a structural block diagram of a processing apparatus for a target resource occupancy situation according to a preferred embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for processing a target resource occupancy situation according to an embodiment of the present invention. As shown in FIG. 1, the processing method of the target resource occupation situation may include:
  • Step S602 Acquire a target resource occupation of the VNF scale up and/or scale down;
  • Step S604 Instruct the VIM to create or modify the standby virtual machine corresponding to the standby VNFC according to the target resource occupation status, where the standby virtual machine is set to take over the service being performed by the active virtual machine corresponding to the primary VNFC.
  • the NFVO can be instructed to create a virtualized infrastructure manager (VIM) according to the target resource occupancy of the VNF scale up/scale down ( Applicable to the case where there is no active/standby in the VNF or modified (applicable to the case where there is active/standby in the VNF).
  • VIM virtualized infrastructure manager
  • the virtual machine corresponding to the standby VNFC maintains no impact or minor impact on the service due to the standby VNFC takeover service.
  • step S604 After the VIM is created as the standby virtual machine according to the target resource occupation status, the following operations may also be included in the step S604:
  • Step S1 After the standby virtual machine starts to start, trigger the primary virtual machine to synchronize data with the standby virtual machine;
  • Step S2 In the case that the process of determining the synchronization data has entered a steady state, the active virtual machine is triggered to perform switching with the standby virtual machine, and after the switching operation ends, the active virtual machine is deleted.
  • the VNF internal VNFC can be divided into two cases: active/standby and no active/standby; the meaning of the standby VNFC is that the main VNFC can be replaced as needed (possibly the main VNFC fault, equipment overhaul, etc.). business. Whether the VNF is active or not is described in the Virtual Network Function Descriptor (VNFD). The NFVO and VNFM can sense whether the VNF of the VNF is active or not through the VNFD. For the VNF internal VNFC, there are two situations: active/standby and no active/standby. For the VNF internal VNFC, the active/standby function can also be used to achieve elegant scale up and scale down.
  • VNFD Virtual Network Function Descriptor
  • the internal VNFC of the VNF is active and standby
  • the virtual machine corresponding to the standby VNFC is created according to the target resource occupancy of the scale up/scale down.
  • the virtual machine corresponding to the standby VNFC is started, and the virtual machine corresponding to the active VNFC is triggered to synchronize data with the standby virtual machine (for example, the synchronous data function of the virtual machine hot migration).
  • the active/standby switchover is triggered.
  • the virtual machine hot migration switching function after the active/standby switchover is completed, the virtual machine corresponding to the original active VNFC is deleted, and the process of scale up/scale down is finished.
  • the maintenance due to the backup VNFC takeover service, the maintenance has no impact or less impact on the business, and the elegant scale up/scale down function is realized.
  • the VIM may be instructed to delete the primary virtual machine.
  • the graceful scale up/scale down is completed after the active/standby switchover is completed.
  • the NFVO instructs the VIM to delete the new standby VNFC. virtual machine.
  • step S604 after the VIM is modified according to the target resource occupation status, the following steps may be further included:
  • Step S3 After the standby virtual machine is restarted, it is detected whether the process of synchronizing data between the active virtual machine and the standby virtual machine has entered a steady state;
  • Step S4 triggering the active virtual machine to perform switching with the standby virtual machine if it is determined that the stable state has been entered;
  • Step S5 After modifying the resource occupancy of the switched standby virtual machine, restart the switched standby virtual machine.
  • the active/standby function can be utilized to achieve the purpose of elegant scale up and scale down, that is, the standby VNFC is first modified according to the target resource occupancy of the scale up/scale down. Corresponding virtual machine and restart the virtual machine. After the standby virtual machine is started, the active virtual machine synchronizes data to the standby dynamic. When the synchronous data enters the steady state, the active/standby switchover is triggered, the standby virtual machine becomes the active virtual machine, and the primary virtual machine becomes the standby virtual machine. . Then, the resource occupancy of the new standby virtual machine is modified, and the new standby virtual machine is restarted. The process of scale up/scale down is finished. In this process, because there is a standby VNFC takeover service, the service is not affected or is small. The effect is to achieve an elegant scale up/scale down function.
  • the VNF in a case where the process of determining the synchronization data has entered a steady state, the VNF is notified to trigger the primary virtual machine to perform switching with the standby virtual machine, and the standby virtual machine takes over the current service of the active virtual machine.
  • the NFVO After the synchronous data enters the steady state, the NFVO notifies the VNF to trigger the VNFC active/standby switchover, and the virtual machine of the standby VNFC takes over the virtual machine service of the active VNFC, and the original primary VNFC becomes the standby VNFC, and the original standby VNFC becomes the primary VNFC.
  • the NFVO or VNFM may instruct the VIM to create or modify the standby virtual machine based on the target resource occupancy. If the resource allocation is performed by the VNFM, the VNFM indicates that the VIM is created according to the target resource occupancy of the VNF scale up/scale down (applicable to the case where there is no active/standby in the VNF) or modified (applicable to the case where there is active/standby in the VNF). VNFC corresponding virtual machine; if executed by VNFM For the resource allocation, for the active/standby switchover in the VNF, after the active/standby switchover ends, the VNFM instructs the VIM to delete the virtual machine corresponding to the new standby VNFC.
  • FIG. 7 is a flow chart of a VNF elastic scaling performed by NFVO to perform resource allocation in accordance with a preferred embodiment of the present invention. As shown in FIG. 7, the process may include the following processing steps:
  • Step S701 The sender (for example, the OSS) sends an elastic extension request to the NFVO.
  • the sender for example, the OSS
  • Step S702 The NFVO performs a validity check on the elastic scalability request, and checks whether the requirement conforms to the policy configuration.
  • Step S703 NFVO finds the VNFM corresponding to the VNF, and if the VNF does not have a corresponding VNFM, the NFVO creates a new VNFM;
  • Step S704 Before performing the elastic action, the NFVO performs feasibility check on the elastic scalability request and reserves related resources, and the entire step S704 is optional. If S704 is executed, all must be performed. S704 includes the following sub-steps:
  • Step S704a The NFVO requests the VNFM to perform a feasibility check on the elastic scalability request.
  • Step S704b The VNFM performs any necessary preparation work, which may include modifying/complementing the entry of the elastic scalability request according to the VNF specific restriction;
  • Step S704c The VNFM returns an updated elastic scalability request to the NFVO.
  • Step S704d NFVO requests VIM to check the availability of resources (computing, storage, network) and reserve these resources;
  • Step S704e The VIM checks the availability of resources (computing, storage, network) and reserves these resources;
  • Step S704f The VIM returns the result of the resource reservation to the NFVO.
  • Step S705 The NFVO sends an elastic scaling request to the VNFM, including the elastic scaling data, and if the step S704 has been executed, the resource reservation information is further included;
  • Step S706 The VNFM performs any required preparation work: verifying the elastic scalability request, and performing parameter verification, and may further include modifying or supplementing the input of the elastic expansion request according to the specific limitation of the VNF;
  • step S704b is consistent with step S704b, and if step S704 has been performed, skip this step;
  • Step S707 The VNFM replies to the NFVO with a resource change response
  • Step S708 The VNFM sends a request to the VIM to create (applies to the active/standby VNFC) or modify (applies to the active and standby VNFC) the standby VNFC.
  • Step S709 The VIM creates or modifies a network associated with the virtual machine corresponding to the standby VNFC.
  • Step S710 VIM creation (applicable to no active standby VNFC) or modification (applicable to active/standby VNFC) virtual machine corresponding to the standby VNFC and associated to the relevant network;
  • Step S711 The VIM replies to the VNFM to create (for the active/standby VNFC) or modify (for the active and standby VNFC) the standby VNFC response;
  • Step S712 The primary VNFC synchronizes data with the standby VNFC.
  • Step S713 The VNFM sends a VNFC active/standby switchover request to the VNF.
  • Step S714 After the primary VNFC and the standby VNFC are synchronized to the steady state, the VNF control triggers the active/standby switchover of the VNFC. After the switchover succeeds, the VNF returns a VNFC active/standby switchover success response to the VNFM.
  • Step S715 For the case of the VNFC with the active and the standby, the step is skipped.
  • the VNFM sends a virtual machine request for deleting the standby VNFC to the VIM.
  • Step S716 For the case of the VNFC with the active and standby, this step is skipped.
  • the VIM replies to the VNFM to delete the virtual machine response corresponding to the standby VNFC.
  • Step S717 NFVO notifies that the VNFM resource change is completed
  • Step S718 The VNFM replies to the NFVO response
  • Step S719 The NFVO responds to the request to respond to the flexible application successfully.
  • FIG. 8 is a flow chart of a VNF auto-stretching performed by a VNFM to perform resource allocation in accordance with a preferred embodiment of the present invention. As shown in FIG. 8, the process may include the following processing steps:
  • Step S801 The VNFM collects measurement data from the VNF (application related);
  • Step S802 The VNFM detects that the system load exceeds the elastic extension threshold, and triggers the elastic extension request;
  • Step S803 The VNFM requests the NFVO to check the elastic extension request
  • Step S804 The NFVO determines to perform the elastic extension. According to the capacity database of the VNF and the VNF template, the resources (computation, storage, and network) required for the elastic extension are calculated, and whether there are sufficient resources currently checked;
  • Step S805 NFVO authorizes the VNFM to elastically extend the VNF;
  • Step S806 The VNFM sends a request to the VIM to create (for the active/standby VNFC) or modify (for the active and standby VNFC) the standby VNFC.
  • Step S807 The VIM replies to the VNFM to create (for the active/standby VNFC) or modify (applicable to the active and standby VNFC) the standby VNFC response;
  • Step S808 The primary VNFC synchronizes data with the standby VNFC.
  • Step S809 The VNFM sends a VNFC active/standby switchover request to the VNF.
  • Step S810 After the synchronous data of the primary VNFC and the standby VNFC enters the steady state, the VNF control triggers the active/standby switchover of the VNFC. After the successful switchover, the VNF returns a VNFC active/standby switchover success response to the VNFM.
  • Step S811 For the case of the VNFC with the active and the standby, the step is skipped.
  • the VNFM sends a virtual machine request for deleting the standby VNFC to the VIM.
  • Step S812 This step is skipped for the VNFC in the active/standby mode.
  • the VIM replies to the VNFM to delete the virtual machine response corresponding to the standby VNFC.
  • Step S813 The VNFM configures related data on the VNF
  • Step S814 the VNFM returns a resilient response to the NFVO;
  • Step S815 The VNFM notifies the EM that the VNF capacity has changed
  • Step S816 NFVO saves a mapping relationship between the VNF and the VIM resource pool
  • Step S817 EM and VNFM update VNF related data
  • Step S818 The EM configures VNF related application data.
  • FIG. 9 is an EM-initiated VNF resiliency flow diagram for performing resource allocation by a VNFM in accordance with a preferred embodiment of the present invention. As shown in FIG. 9, the process may include the following processing steps:
  • Step S901 The manual operator manually performs the elastic stretch request on the EM, or the EM triggers the automatic elastic stretch request according to the detection result;
  • Step S902 The EM sends an elastic extension request to the VNFM.
  • Step S903 The VNFM requests the NFVO to check the elastic extension request
  • Step S904 The NFVO determines to perform the elastic extension, calculates the resources (computation, storage, and network) required for the elastic extension according to the capacity database of the VNF and the VNF template, and checks whether there are sufficient resources at present;
  • Step S905 The NFVO authorizes the VNFM to flexibly extend the VNF;
  • Step S906 The VNFM sends a request to the VIM to create (applies to the active/standby VNFC) or modify (applies to the active and standby VNFC) the standby VNFC.
  • Step S907 The VIM replies to the VNFM to create (for the active/standby VNFC) or modify (applicable to the active and standby VNFC) the standby VNFC response;
  • Step S908 The primary VNFC synchronizes data with the standby VNFC.
  • Step S909 The VNFM sends a VNFC active/standby switchover request to the VNF.
  • Step S910 After the synchronous data of the primary VNFC and the standby VNFC enters the steady state, the VNF control triggers the active/standby switchover of the VNFC. After the successful switchover, the VNF returns a VNFC active/standby switchover success response to the VNFM.
  • Step S911 This step is skipped for the VNFC in the active/standby mode.
  • the VNFM sends a virtual machine request to the VIM to delete the standby VNFC.
  • Step S912 For the case of the VNFC with the active and standby, the step is skipped.
  • the VIM replies to the VNFM to delete the virtual machine response corresponding to the standby VNFC.
  • Step S913 The VNFM configures related data on the VNF;
  • Step S914 the VNFM returns a resilient response to the NFVO;
  • Step S915 The VNFM notifies the EM that the VNF capacity has changed
  • Step S916 NFVO saves a mapping relationship between the VNF and the VIM resource pool
  • Step S917 M and VNFM update VNF related data
  • Step S918 The EM configures VNF related application data.
  • VNF VNF automatic elastic contraction flowchart for performing resource allocation by a VNFM in accordance with a preferred embodiment of the present invention. As shown in FIG. 10, the method may include the following processing steps:
  • Step S1001 The VNFM collects measurement data from the VNF (application related);
  • Step S1002 The VNFM detects that the system load is lower than the elastic contraction threshold, and triggers the elastic contraction request;
  • Step S1003 The VNFM requests the NFVO to check the elastic contraction request
  • Step S1004 NFVO decides to perform elastic contraction according to a configuration policy.
  • Step S1005 The NFVO authorizes the VNFM to elastically shrink the VNF;
  • Step S1006 The VNFM sends a request to the VIM to create (for the active/standby VNFC) or modify (for the active and standby VNFC) the standby VNFC.
  • Step S1007 The VIM replies to the VNFM to create (for the active/standby VNFC) or modify (for the active and standby VNFC) the standby VNFC response;
  • Step S1008 The primary VNFC synchronizes data with the standby VNFC.
  • Step S1009 The VNFM sends a VNFC active/standby switchover request to the VNF.
  • Step S1010 After the synchronous data of the primary VNFC and the standby VNFC enters the steady state, the VNF control triggers the active/standby switchover of the VNFC. After the switchover succeeds, the VNF returns a VNFC active/standby switchover success response to the VNFM.
  • Step S1011 For the case of the VNFC with the active and standby, the step is skipped.
  • the VNFM sends a request to the VIM to delete the virtual machine corresponding to the standby VNFC.
  • Step S1012 For the VNFC with active and standby, this step is skipped.
  • the VIM replies to the VNFM to delete the virtual machine response corresponding to the standby VNFC.
  • Step S1013 The VNFM notifies the NFVO that the elastic contraction is successful
  • Step S1014 The VNFM notifies the EM that the VNF capacity is elastically contracted successfully
  • Step S1015 NFVO updates the mapping relationship between the VNF and the VIM resource pool
  • Step S1016 EM and VNFM update VNF related data.
  • FIG. 11 is an EM-initiated VNF elastic contraction flowchart for performing resource allocation by a VNFM in accordance with a preferred embodiment of the present invention. As shown in FIG. 11, the process may include the following processing steps:
  • Step S1101 The manual operator manually performs the elastic contraction request on the EM, or the EM triggers the automatic elastic contraction request according to the detection result;
  • Step S1102 The EM sends a trigger elastic contract request to the VNFM.
  • Step S1103 The VNFM requests the NFVO to check the elastic contraction request
  • Step S1104 NFVO decides to perform elastic contraction according to the configuration policy.
  • Step S1105 NFVO authorizes VNFM to elastically shrink the VNF
  • Step S1106 The VNFM sends a request to the VIM to create (applies to the active/standby VNFC) or modify (applies to the active and standby VNFC) the standby VNFC;
  • Step S1107 The VIM replies to the VNFM to create (for the active/standby VNFC) or modify (for the active and standby VNFC) the standby VNFC response;
  • Step S1108 The primary VNFC synchronizes data with the standby VNFC.
  • Step S1109 The VNFM sends a VNFC active/standby switchover request to the VNF.
  • Step S1110 After the primary VNFC and the standby VNFC are synchronized, the VNF control triggers the active/standby switchover of the VNFC. After the switchover succeeds, the VNF returns a VNFC active/standby switchover success response to the VNFM.
  • Step S1111 This step is skipped for the VNFC in the active/standby mode.
  • the VNFM sends a virtual machine request to the VIM to delete the standby VNFC.
  • Step S1112 For the case of the VNFC with the active and standby, the step is skipped.
  • the VIM replies to the VNFM to delete the virtual machine response corresponding to the standby VNFC.
  • Step S1113 The VNFM notifies the NFVO that the elastic contraction is successful
  • Step S1114 The VNFM notifies the EM that the VNF capacity is elastically contracted successfully
  • Step S1115 NFVO updates the mapping relationship between the VNF and the VIM resource pool
  • Step S1116 The EM and the VNFM update the VNF related data.
  • FIG. 12 is a structural block diagram of a processing apparatus for a target resource occupancy situation according to an embodiment of the present invention.
  • the processing device for the target resource occupancy may include: an obtaining module 10 configured to acquire a target resource occupancy of the VNF scale up and/or scale down; and the processing module 20 configured to indicate according to the target resource occupancy status
  • the VIM creates or modifies a standby virtual machine corresponding to the standby VNFC, where the standby virtual machine is set to take over the ongoing service of the active virtual machine corresponding to the primary VNFC.
  • the device shown in FIG. 12 solves the problem in the related art that the VNF is not elastically stretched and/or elastically contracted, and the service of the VM cannot be modified without affecting the normal service, thereby achieving an elegant scale up. /scale down, improving the usability of the VNF.
  • the above means may be located but not limited to: NFVO or VNFM.
  • the foregoing apparatus may further include: a first triggering module 30, configured to trigger the primary virtual machine to synchronize data with the standby virtual machine after the standby virtual machine starts to be started; and the second triggering module 40 sets In order to determine that the process of synchronizing data has entered a steady state, the active virtual machine is triggered to perform switching with the standby virtual machine, and after the switching operation ends, the active virtual machine is deleted.
  • a first triggering module 30, configured to trigger the primary virtual machine to synchronize data with the standby virtual machine after the standby virtual machine starts to be started
  • the second triggering module 40 sets In order to determine that the process of synchronizing data has entered a steady state, the active virtual machine is triggered to perform switching with the standby virtual machine, and after the switching operation ends, the active virtual machine is deleted.
  • the apparatus may further include: a detecting module 50 configured to detect, after the standby virtual machine is restarted, whether a process of synchronizing data by the active virtual machine to the standby virtual machine has entered a steady state;
  • the triggering module 60 is configured to trigger the main virtual machine to perform the switching with the standby virtual machine if it is determined that the stable state has been entered;
  • the restarting module 70 is configured to modify the resource occupancy of the replaced virtual machine after the switching, Restart the switched standby virtual machine.
  • the above embodiments achieve the following technical effects (it is required that the effects are achievable by some preferred embodiments): using the technical solution provided by the embodiment of the present invention, in the scale
  • the VIM can be created according to the target resource occupancy of the VNF scale up/scale down (applicable to the case where there is no active/standby in the VNF) or modified (applicable to the case where there is active/standby in the VNF).
  • the corresponding virtual machine solves the problem that the related technology lacks a detailed solution for elegant elastic expansion, thereby achieving an elegant scale up/scale down and improving the usability of the VNF.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the method and apparatus for processing a target resource occupancy situation provided by the embodiments of the present invention have the following beneficial effects: in the process of scale up/scale down, the target resource occupancy indication according to the VNF scale up/scale down may be indicated.
  • the VIM creates or modifies the virtual machine corresponding to the standby VNFC, thereby implementing elegant scale up/scale down and improving the availability of the VNF.

Landscapes

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

Abstract

本发明公开了一种目标资源占用情况的处理方法及装置，在上述方法中，获取VNF scale up和/或scale down的目标资源占用情况；根据目标资源占用情况指示VIM创建或者修改与备用VNFC对应的备用虚拟机，其中，备用虚拟机用于接管与主用VNFC对应的主用虚拟机正在开展的业务。根据本发明提供的技术方案，进而实现了优雅scale up/scale down，提高了VNF的可用性。

Description

目标资源占用情况的处理方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种目标资源占用情况的处理方法及装置。
背景技术
网络功能虚拟化(Network Functions Virtualization，简称为NFV)技术指的是将传统网络功能，如：代理呼叫会话控制功能实体(Proxy call session control Function，简称为P-CSCF)，查询呼叫会话控制功能实体(Interrogating call session control Function，简称为I-CSCF)，服务呼叫会话控制功能实体(Serving call session control Function，简称为S-CSCF)，归属用户服务器(Home subscriber Server，简称为HSS)以及应用服务器(Application Server，简称为AS)等进行虚拟化，通过将虚拟化网络功能组件(Virtualized Network Function Component简称为VNFC)部署在云虚拟机上，从而实现网络功能的虚拟化，虚拟化后的网络功能称为虚拟化网络功能(Virtualized Network Function，简称为VNF)。网络功能虚拟化后可以带来如下技术优势：
1)网络功能和硬件解耦，实现了异种网络功能、异厂家的网络功能运行在相同的硬件上，运行商在部署新网络功能时，能够方便地利旧，保护了运营商投资；
2)由于网络功能都能运行在通用的硬件上，加快了运营商开展新业务的速度；
3)由于采用通用硬件，大规模地采购能够降低成本；
4)由于网络功能具有弹性伸缩功能，网络功能因需占用资源，提高了资源利用率，同时，在负荷较低时，会关闭部分通用服务器，所以更加绿色节能。
NFV技术的一个关键功能是网络功能弹性伸缩技术，弹性伸缩的触发方式有以下两种：
第一种、自动触发，即VNF可以根据自身的负荷情况动态调整自身的资源占用；
第二种、手动触发，即用户可以根据管理需要手动调整VNF的资源占用。
弹性伸缩的调整方式也分为以下两种：
第一种、横向调整，即通过增加或删除虚拟机的方式来调整，称之为横向弹性伸缩(scale out/scale in)；
第二种、纵向调整，即通过调整虚拟机占用资源的方式来调整，称之为纵向弹性伸缩(scale up/scale down)。
现有的欧洲电信标准化协会(ETSI)规范中定义了VNF弹性伸缩流程，其中，描述了如下几部分内容：
(1)由网络功能虚拟化编排器(Network Functions Virtualization Orchestrator，简称为NFVO)执行资源分配的弹性伸缩流程；
图1是根据相关技术的ETSI规范中由NFVO执行资源分配的VNF弹性伸缩流程图。如图1所示，该流程可以包括以下处理步骤：
步骤S101：发送者(例如OSS)向NFVO发送弹性伸缩请求；
步骤S102：NFVO对弹性伸缩请求进行合法性校验，检查此需求是否符合策略配置；
步骤S103：NFVO找到本VNF对应的VNFM，如果本VNF没有对应的VNFM，NFVO创建新VNFM；
步骤S104：NFVO在执行弹性动作之前，对弹性伸缩请求进行可行性校验，并预留相关资源，整个S104步为可选，如果S104执行，则必须全部执行，S104又包括如下子步骤：
步骤S104a：NFVO请求VNFM对弹性伸缩请求进行可行性检查；
步骤S104b：VNFM执行任何必须的准备工作，这些工作可能包括根据VNF特定限制修改/补充弹性伸缩请求的入参；
步骤S104c：VNFM向NFVO返回更新后的弹性伸缩请求；
步骤S104d：NFVO请求VIM检查资源(计算、存储、网络)的可用性并预留这些资源；
步骤S104e：VIM检查资源(计算、存储、网络)的可用性并预留这些资源；
步骤S104f：VIM向NFVO返回资源预留的结果；
步骤S105：NFVO向VNFM发送弹性伸缩请求，包括弹性伸缩数据，如果步骤S104已经执行，则还包括资源预留信息；
步骤S106：VNFM执行任何需要的准备工作：对弹性伸缩请求进行校验，参数校验，可能还包括根据VNF特定限制修改/补充弹性伸缩请求的入参；
需要注意的是：该步骤与步骤S104b一致，如果步骤S104已经执行，则跳过此步骤；
步骤S107：VNFM向NFVO回复资源变更响应；
步骤S108：NFVO向VIM发送资源(计算、存储、网络)变更请求；
步骤S109：VIM根据需要修改VNF内部网络；
步骤S110：VIM根据需要实例化新虚拟机并连到内部网络；
步骤S111：VIM向NFVO回复资源变更完成响应；
步骤S112：NFVO通知VNFM资源变更完成；
步骤S113：VNFM向NFVO回复响应；
步骤S114：NFVO向请求回复弹性申请成功响应。
(2)由VNF管理(VNF Manager，简称为VNFM)执行资源分配的弹性伸缩流程，其中该部分内容还可以具体划分为如下技术章节：
1)VNF自动弹的过程；
图2是根据相关技术的ETSI规范中由VNFM执行资源分配的VNF自动弹性伸流程图。如图2所示，该流程可以包括以下处理步骤：
步骤S201：VNFM从VNF收集测量数据(应用相关)；
步骤S202：VNFM检测到系统负荷超过弹性伸阈值，触发弹性伸请求；
步骤S203：VNFM请求NFVO对弹性伸请求进行校验；
步骤S204：NFVO决定执行弹性伸，根据VNF的容量数据库及VNF模版，计算弹性伸需要的资源(计算、存储、网络)，检查当前是否有足够的资源；
步骤S205：NFVO授权VNFM对VNF进行弹性伸；
步骤S206：VNFM根据NFVO的指示，向VIM发送请求创建并启动VM；
步骤S207：VIM实例化并启动新VM，并给VNFM回复成功响应；
步骤S208：VNFM配置VNF上相关数据；
步骤S209：VNFM向NFVO回复弹性伸成功响应；
步骤S210：VNFM通知EM此VNF容量发生变更；
步骤S211：NFVO保存VNF和VIM资源池之间的映射关系；
步骤S212：EM和VNFM更新VNF相关数据；
步骤S213：EM配置VNF相关应用数据。
2)由网元管理(Element management，简称为EM)发起的VNF自动弹的过程；
图3是根据相关技术的ETSI规范中由VNFM执行资源分配的EM发起的VNF弹性伸流程图。如图3所示，该流程可以包括以下处理步骤：
步骤S301：手工操作员在EM上手动执行弹性伸请求，或者EM根据检测结果触发自动弹性伸请求；
步骤S302：EM向VNFM发送弹性伸请求；
步骤S303：VNFM请求NFVO对弹性伸请求进行校验；
步骤S304：NFVO决定执行弹性伸，根据VNF的容量数据库及VNF模版，计算弹性伸需要的资源(计算、存储、网络)，检查当前是否有足够的资源；
步骤S305：NFVO授权VNFM对VNF进行弹性伸；
步骤S306：VNFM根据NFVO的指示，向VIM发送请求创建并启动VM；
步骤S307：VIM实例化并启动新VM，并给VNFM回复成功响应；
步骤S308：VNFM配置VNF上相关数据；
步骤S309：VNFM向NFVO回复弹性伸成功响应；
步骤S310：VNFM通知EM此VNF容量发生变更；
步骤S311：NFVO保存VNF和VIM资源池之间的映射关系；
步骤S312：M和VNFM更新VNF相关数据；
步骤S313：EM配置VNF相关应用数据。
3)VNF自动缩的过程；
图4是根据相关技术的ETSI规范中由VNFM执行资源分配的VNF自动弹性缩流程图。如图4所示，该方法可以包括以下处理步骤：
步骤S401：VNFM从VNF收集测量数据(应用相关)；
步骤S402：VNFM检测到系统负荷低于弹性缩阈值，触发弹性缩请求；
步骤S403：VNFM请求NFVO对弹性缩请求进行校验；
步骤S404：NFVO根据配置策略决定执行弹性缩
步骤S405：NFVO授权VNFM对VNF进行弹性缩；
步骤S406：VNF优雅关闭VNFC(对正在进行的业务无影响)；
步骤S407：当即将删除的VNFC(VM)上无负荷时，VNFM请求VIM删除VM；
步骤S408：VIM删除VM并通知VNFM；
步骤S409：VNFM通知NFVO弹性缩成功；
步骤S410：VNFM通知EM：VNF容量弹性缩成功；
步骤S411：NFVO更新VNF和VIM资源池之间的映射关系；
步骤S412：EM和VNFM更新VNF相关数据。
4)由EM发起的VNF自动缩的过程；
图5是根据相关技术的由VNFM执行资源分配的EM发起的VNF弹性缩流程图。如图5所示，该流程可以包括以下处理步骤：
步骤S501：手工操作员在EM上手动执行弹性缩请求，或者EM根据检测结果触发自动弹性缩请求；
步骤S502：EM向VNFM发送触发弹性缩请求；
步骤S503：VNFM请求NFVO对弹性缩请求进行校验；
步骤S504：NFVO根据配置策略决定执行弹性缩
步骤S505：NFVO授权VNFM对VNF进行弹性缩；
步骤S506：VNF优雅关闭VNFC(对正在进行的业务无影响)；
步骤S507：当即将删除的VNFC(VM)上无负荷时，VNFM请求VIM删除VM；
步骤S508：VIM删除VM并通知VNFM；
步骤S509：VNFM通知NFVO弹性缩成功；
步骤S510：VNFM通知EM：VNF容量弹性缩成功；
步骤S511：NFVO更新VNF和VIM资源池之间的映射关系；
步骤S512：EM和VNFM更新VNF相关数据。
需要说明的是，在上述(1)和(2)中所描述的流程均不区分scale out/scale in还是scale up/scale down。
上述流程描述的是弹性伸缩的通用流程，适用于scale up/scale down和scale up/scale in两种方式的弹性伸缩，然而，上述方案的缺陷在于：
当VNF发生scale up/scale down方式的弹性伸缩时，
图1中没有描述是否需要优雅弹性伸缩及如何弹性伸缩；
图2中没有描述是否需要优雅弹性伸及如何弹性伸；
图3中没有描述是否需要优雅弹性伸及如何弹性伸；
图4中虽然描述了需要优雅弹性缩，但是没有描述如何弹性缩；
图5中虽然描述了需要优雅弹性伸，但是没有描述如何弹性伸；
在实际的应用中，经常要求VNF能够优雅弹性伸缩，以免对正在进行的业务进行影响，例如：当电信领域的P-CSCF、I-CSCF、S-CSCF发送弹性伸缩时，电信运营商一般要求不能对正在进行的呼叫、注册等产生影响，对于scale up/scale down方式的弹性伸缩而言，在VNF弹性伸和/或弹性缩的过程中，需要修改虚拟机(VM)的资源占用情况(计算、存储、网络)，当VIM完成对VM的资源占用情况修改后，需要重新启动VM才能生效，而重新启动VM必然影响正在进行的业务。
综上所述，从目前的ETSI规范来看，尚没有针对优雅弹性伸缩的详细解决方案。
发明内容
本发明实施例提供了一种目标资源占用情况的处理方法及装置，以至少解决相关技术中在VNF弹性伸和/或弹性缩的过程中，无法在修改VM的资源占用情况下不影响正常进行的业务的问题。
根据本发明的一个方面，提供了一种目标资源占用情况的处理方法。
根据本发明实施例的目标资源占用情况的处理方法包括：获取VNF scale up和/或scale down的目标资源占用情况；根据目标资源占用情况指示VIM创建或者修改与备用VNFC对应的备用虚拟机，其中，备用虚拟机设置为接管与主用VNFC对应的主用虚拟机正在开展的业务。
优选地，在根据目标资源占用情况指示VIM创建备用虚拟机之后，还包括：在备用虚拟机开始启动后，触发主用虚拟机向备用虚拟机同步数据；在确定同步数据的过程已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换，并在倒换操作结束后，删除主用虚拟机。
优选地，在倒换操作结束后，指示VIM删除主用虚拟机。
优选地，在根据目标资源占用情况指示VIM修改备用虚拟机之后，还包括：在备用虚拟机重新启动后，检测主用虚拟机向备用虚拟机同步数据的过程是否已经进入稳定状态；在确定已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换；在对倒换后的备用虚拟机的资源占用情况进行修改后，重启倒换后的备用虚拟机。
优选地，在确定同步数据的过程已经进入稳定状态的情况下，通知VNF触发主用虚拟机与备用虚拟机进行倒换，由备用虚拟机接管主用虚拟机当前开展的业务。
优选地，NFVO或VNFM根据目标资源占用情况指示VIM创建或者修改备用虚拟机。
根据本发明的另一方面，提供了一种目标资源占用情况的处理装置。
根据本发明实施例的目标资源占用情况的处理装置包括：获取模块，设置为获取VNF scale up和/或scale down的目标资源占用情况；处理模块，设置为根据目标资源占用情况指示VIM创建或者修改与备用VNFC对应的备用虚拟机，其中，备用虚拟机设置为接管与主用VNFC对应的主用虚拟机正在开展的业务。
优选地，上述装置还包括：第一触发模块，设置为在备用虚拟机开始启动后，触发主用虚拟机向备用虚拟机同步数据；第二触发模块，设置为在确定同步数据的过程已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换，并在倒换操作结束后，删除主用虚拟机。
优选地，上述装置还包括：检测模块，设置为在备用虚拟机重新启动后，检测主用虚拟机向备用虚拟机同步数据的过程是否已经进入稳定状态；第三触发模块，设置为在确定已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换；重启模块，设置为在对倒换后的备用虚拟机的资源占用情况进行修改后，重启倒换后的备用虚拟机。
优选地，上述装置位于NFVO或VNFM。
通过本发明实施例，采用获取VNF scale up和/或scale down的目标资源占用情况；根据目标资源占用情况指示VIM创建或者修改与备用VNFC对应的备用虚拟机，其中，备用虚拟机设置为接管与主用VNFC对应的主用虚拟机正在开展的业务，解决了相关技术中在VNF弹性伸和/或弹性缩的过程中，无法在修改VM的资源占用情况下不影响正常进行的业务的问题，进而实现了优雅scale up/scale down，提高了VNF的可用性。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的ETSI规范中由NFVO执行资源分配的VNF弹性伸缩流程图；
图2是根据相关技术的ETSI规范中由VNFM执行资源分配的VNF自动弹性伸流程图；
图3是根据相关技术的ETSI规范中由VNFM执行资源分配的EM发起的VNF弹性伸流程图；
图4是根据相关技术的ETSI规范中由VNFM执行资源分配的VNF自动弹性缩流程图；
图5是根据相关技术的由VNFM执行资源分配的EM发起的VNF弹性缩流程图；
图6是根据本发明实施例的目标资源占用情况的处理方法的流程图；
图7是根据本发明优选实施例的由NFVO执行资源分配的VNF弹性伸缩流程图；
图8是根据本发明优选实施例的由VNFM执行资源分配的VNF自动弹性伸流程图；
图9是根据本发明优选实施例的由VNFM执行资源分配的EM发起的VNF弹性伸流程图；
图10是根据本发明优选实施例的由VNFM执行资源分配的VNF自动弹性缩流程图；
图11是根据本发明优选实施例的由VNFM执行资源分配的EM发起的VNF弹性缩流程图；
图12是根据本发明实施例的目标资源占用情况的处理装置的结构框图；
图13是根据本发明优选实施例的目标资源占用情况的处理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图6是根据本发明实施例的目标资源占用情况的处理方法的流程图。如图1所示，该目标资源占用情况的处理方法可以包括：
步骤S602：获取VNF scale up和/或scale down的目标资源占用情况；
步骤S604：根据目标资源占用情况指示VIM创建或者修改与备用VNFC对应的备用虚拟机，其中，备用虚拟机设置为接管与主用VNFC对应的主用虚拟机正在开展的业务。
相关技术中缺乏针对优雅弹性伸缩的详细解决方案。采用如图6所示的方法，在scale up/scale down的过程中，NFVO可以根据VNF scale up/scale down的目标资源占用情况指示虚拟化基础架构管理(Virtualized Infrastructure Manager，简称为VIM)创建(适用于VNF内无主备的情况)或者修改(适用于VNF内有主备的情况)备用VNFC对应的虚拟机，由于有备用VNFC接管业务，保持了对业务无影响或较小影响，因而解决了相关技术中在VNF弹性伸和/或弹性缩的过程中，无法在修改VM的资源占用情况下不影响正常进行的业务的问题，进而实现了优雅scale up/scale down，提高了VNF的可用性。
优选地，在步骤S604，根据目标资源占用情况指示VIM创建备用虚拟机之后，还可以包括以下操作：
步骤S1：在备用虚拟机开始启动后，触发主用虚拟机向备用虚拟机同步数据；
步骤S2：在确定同步数据的过程已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换，并在倒换操作结束后，删除主用虚拟机。
在优选实施例中，可以将VNF内部VNFC分成两种情况：有主备和无主备；备用VNFC的意义在于可以根据需要(可能是主用VNFC故障、设备检修等)接替执行主用VNFC的业务。VNF是否有主备是在虚拟化网络功能描述符(Virtual network function descriptor，简称为VNFD)中描述的，NFVO和VNFM可以通过VNFD感知到VNF的VNFC是否有主备。针对VNF内部VNFC有主备和无主备两种情况，对于VNF内部VNFC无主备的情况，也可以利用主备功能来达到优雅scale up和scale down的目的。与VNF内部VNFC有主备的情况相比，首先需要对即将进行scale up/scale down的VNFC创建备用VNFC，此备用VNFC对应的虚拟机是根据scale up/scale down的目标资源占用情况创建的。然后开始启动备用VNFC对应的虚拟机，触发主用VNFC对应的虚拟机向备用虚拟机同步数据(例如：虚拟机热迁移的同步数据功能)，当同步数据进入稳态后，触发主备倒换(例如：虚拟机热迁移的切换功能)，主备倒换结束后，删除原主用VNFC对应的虚拟机，scale up/scale down的过程就结束了。在这个过程中，由于有备用VNFC接管业务，保持了对业务无影响或较小影响，实现了优雅scale up/scale down功能。
在优选实施过程中，在倒换操作结束后，可以指示VIM删除主用虚拟机。
对于VNF内有主备的情况，当主备倒换结束后，则优雅scale up/scale down就已完成，对于VNF内无主备的情况，当主备倒换结束后，NFVO指示VIM删除新备用VNFC对应的虚拟机。
优选地，在步骤S604，根据目标资源占用情况指示VIM修改备用虚拟机之后，还可以包括以下步骤：
步骤S3：在备用虚拟机重新启动后，检测主用虚拟机向备用虚拟机同步数据的过程是否已经进入稳定状态；
步骤S4：在确定已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换；
步骤S5：在对倒换后的备用虚拟机的资源占用情况进行修改后，重启倒换后的备用虚拟机。
在优选实施例中，对于VNF内部VNFC有主备的情况，可以利用这种主备功能来达到优雅scale up和scale down的目的，即首先根据scale up/scale down的目标资源占用情况修改备用VNFC对应的虚拟机并重新启动虚拟机。在备用虚拟机启动后，主用虚拟机向备用动态同步数据，当同步数据进入稳态后，触发主备倒换，备用虚拟机变成主用虚拟机，主用虚拟机则变成备用虚拟机。然后，修改新备用虚拟机的资源占用情况，重启新备用虚拟机，scale up/scale down的过程就结束了，在这个过程中，由于有备用VNFC接管业务，保持了对业务无影响或较小影响，实现了优雅scale up/scale down功能。
在优选实施过程中，在确定同步数据的过程已经进入稳定状态的情况下，通知VNF触发主用虚拟机与备用虚拟机进行倒换，由备用虚拟机接管主用虚拟机当前开展的业务。
当同步数据进入稳态后，NFVO通知VNF触发VNFC主备倒换，由备用VNFC的虚拟机接管主用VNFC的虚拟机业务，原主用VNFC变成备用VNFC，原备用VNFC变成主用VNFC。
在优选实施过程中，可以由NFVO或VNFM根据目标资源占用情况指示VIM创建或者修改备用虚拟机。如果由VNFM执行资源分配，则由VNFM根据VNF scale up/scale down的目标资源占用情况指示VIM创建(适用于VNF内无主备的情况)或者修改(适用于VNF内有主备的情况)备用VNFC对应的虚拟机；如果由VNFM执 行资源分配，对于VNF内有主备的情况，当主备倒换结束后，则由VNFM指示VIM删除新备用VNFC对应的虚拟机。
下面将结合图7至图11所示的优选实施方式对上述优选实施过程作进一步的描述。
图7是根据本发明优选实施例的由NFVO执行资源分配的VNF弹性伸缩流程图。如图7所示，该流程可以包括以下处理步骤：
步骤S701：发送者(例如OSS)向NFVO发送弹性伸缩请求；
步骤S702：NFVO对弹性伸缩请求进行合法性校验，检查此需求是否符合策略配置；
步骤S703：NFVO找到本VNF对应的VNFM，如果本VNF没有对应的VNFM，NFVO创建新VNFM；
步骤S704：NFVO在执行弹性动作之前，对弹性伸缩请求进行可行性校验，并预留相关资源，整个S704步为可选，如果S704执行，则必须全部执行，S704又包括如下子步骤：
步骤S704a：NFVO请求VNFM对弹性伸缩请求进行可行性检查；
步骤S704b：VNFM执行任何必须的准备工作，这些工作可能包括根据VNF特定限制修改/补充弹性伸缩请求的入参；
步骤S704c：VNFM向NFVO返回更新后的弹性伸缩请求；
步骤S704d：NFVO请求VIM检查资源(计算、存储、网络)的可用性并预留这些资源；
步骤S704e：VIM检查资源(计算、存储、网络)的可用性并预留这些资源；
步骤S704f：VIM向NFVO返回资源预留的结果；
步骤S705：NFVO向VNFM发送弹性伸缩请求，包括弹性伸缩数据，如果步骤S704已经执行，则还包括资源预留信息；
步骤S706：VNFM执行任何需要的准备工作：对弹性伸缩请求进行校验，参数校验，可能还包括根据VNF特定限制修改/补充弹性伸缩请求的入参；
需要注意的是：该步骤与步骤S704b一致，如果步骤S704已经执行，则跳过此步骤；
步骤S707：VNFM向NFVO回复资源变更响应；
步骤S708：VNFM向VIM发送创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的请求；
步骤S709：VIM创建或者修改备用VNFC对应的虚拟机关联的网络；
步骤S710：VIM创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC对应的虚拟机并关联到相关网络；
步骤S711：VIM给VNFM回复创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的响应；
步骤S712：主用VNFC向备用VNFC同步数据；
步骤S713：VNFM向VNF发送VNFC主备倒换请求；
步骤S714：当主用VNFC和备用VNFC同步数据进入稳态后，VNF控制触发VNFC主备倒换，当倒换成功后，VNF向VNFM回复VNFC主备倒换成功响应；
步骤S715：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VNFM向VIM发送删除备用VNFC对应的虚拟机请求；
步骤S716：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VIM向VNFM回复删除备用VNFC对应的虚拟机响应；
步骤S717：NFVO通知VNFM资源变更完成；
步骤S718：VNFM向NFVO回复响应；
步骤S719：NFVO向请求回复弹性申请成功响应。
图8是根据本发明优选实施例的由VNFM执行资源分配的VNF自动弹性伸流程图。如图8所示，该流程可以包括以下处理步骤：
步骤S801：VNFM从VNF收集测量数据(应用相关)；
步骤S802：VNFM检测到系统负荷超过弹性伸阈值，触发弹性伸请求；
步骤S803：VNFM请求NFVO对弹性伸请求进行校验；
步骤S804：NFVO决定执行弹性伸，根据VNF的容量数据库及VNF模版，计算弹性伸需要的资源(计算、存储、网络)，检查当前是否有足够的资源；
步骤S805：NFVO授权VNFM对VNF进行弹性伸；
步骤S806：VNFM向VIM发送创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的请求；
步骤S807：VIM给VNFM回复创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的响应；
步骤S808：主用VNFC向备用VNFC同步数据；
步骤S809：VNFM向VNF发送VNFC主备倒换请求；
步骤S810：当主用VNFC和备用VNFC同步数据进入稳态后，VNF控制触发VNFC主备倒换，当倒换成功后，VNF向VNFM回复VNFC主备倒换成功响应；
步骤S811：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VNFM向VIM发送删除备用VNFC对应的虚拟机请求；
步骤S812：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VIM向VNFM回复删除备用VNFC对应的虚拟机响应；
步骤S813：VNFM配置VNF上相关数据；
步骤S814：VNFM向NFVO回复弹性伸成功响应；
步骤S815：VNFM通知EM此VNF容量发生变更；
步骤S816：NFVO保存VNF和VIM资源池之间的映射关系；
步骤S817：EM和VNFM更新VNF相关数据；
步骤S818：EM配置VNF相关应用数据。
图9是根据本发明优选实施例的由VNFM执行资源分配的EM发起的VNF弹性伸流程图。如图9所示，该流程可以包括以下处理步骤：
步骤S901：手工操作员在EM上手动执行弹性伸请求，或者EM根据检测结果触发自动弹性伸请求；
步骤S902：EM向VNFM发送弹性伸请求；
步骤S903：VNFM请求NFVO对弹性伸请求进行校验；
步骤S904：NFVO决定执行弹性伸，根据VNF的容量数据库及VNF模版，计算弹性伸需要的资源(计算、存储、网络)，检查当前是否有足够的资源；
步骤S905：NFVO授权VNFM对VNF进行弹性伸；
步骤S906：VNFM向VIM发送创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的请求；
步骤S907：VIM给VNFM回复创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的响应；
步骤S908：主用VNFC向备用VNFC同步数据；
步骤S909：VNFM向VNF发送VNFC主备倒换请求；
步骤S910：当主用VNFC和备用VNFC同步数据进入稳态后，VNF控制触发VNFC主备倒换，当倒换成功后，VNF向VNFM回复VNFC主备倒换成功响应；
步骤S911：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VNFM向VIM发送删除备用VNFC对应的虚拟机请求；
步骤S912：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VIM向VNFM回复删除备用VNFC对应的虚拟机响应；
步骤S913：VNFM配置VNF上相关数据；
步骤S914：VNFM向NFVO回复弹性伸成功响应；
步骤S915：VNFM通知EM此VNF容量发生变更；
步骤S916：NFVO保存VNF和VIM资源池之间的映射关系；
步骤S917：M和VNFM更新VNF相关数据；
步骤S918：EM配置VNF相关应用数据。
图10是根据本发明优选实施例的由VNFM执行资源分配的VNF自动弹性缩流程图。如图10所示，该方法可以包括以下处理步骤：
步骤S1001：VNFM从VNF收集测量数据(应用相关)；
步骤S1002：VNFM检测到系统负荷低于弹性缩阈值，触发弹性缩请求；
步骤S1003：VNFM请求NFVO对弹性缩请求进行校验；
步骤S1004：NFVO根据配置策略决定执行弹性缩
步骤S1005：NFVO授权VNFM对VNF进行弹性缩；
步骤S1006：VNFM向VIM发送创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的请求；
步骤S1007：VIM给VNFM回复创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的响应；
步骤S1008：主用VNFC向备用VNFC同步数据；
步骤S1009：VNFM向VNF发送VNFC主备倒换请求；
步骤S1010：当主用VNFC和备用VNFC同步数据进入稳态后，VNF控制触发VNFC主备倒换，当倒换成功后，VNF向VNFM回复VNFC主备倒换成功响应；
步骤S1011：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VNFM向VIM发送删除备用VNFC对应的虚拟机请求；
步骤S1012：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VIM向VNFM回复删除备用VNFC对应的虚拟机响应；
步骤S1013：VNFM通知NFVO弹性缩成功；
步骤S1014：VNFM通知EM：VNF容量弹性缩成功；
步骤S1015：NFVO更新VNF和VIM资源池之间的映射关系；
步骤S1016：EM和VNFM更新VNF相关数据。
图11是根据本发明优选实施例的由VNFM执行资源分配的EM发起的VNF弹性缩流程图。如图11所示，该流程可以包括以下处理步骤：
步骤S1101：手工操作员在EM上手动执行弹性缩请求，或者EM根据检测结果触发自动弹性缩请求；
步骤S1102：EM向VNFM发送触发弹性缩请求；
步骤S1103：VNFM请求NFVO对弹性缩请求进行校验；
步骤S1104：NFVO根据配置策略决定执行弹性缩
步骤S1105：NFVO授权VNFM对VNF进行弹性缩；
步骤S1106：VNFM给VIM发送创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的请求；
步骤S1107：VIM给VNFM回复创建(适用于无主备VNFC)或者修改(适用于有主备VNFC)备用VNFC的响应；
步骤S1108：主用VNFC向备用VNFC同步数据；
步骤S1109：VNFM向VNF发送VNFC主备倒换请求；
步骤S1110：当主用VNFC和备用VNFC同步数据进入稳态后，VNF控制触发VNFC主备倒换，当倒换成功后，VNF向VNFM回复VNFC主备倒换成功响应；
步骤S1111：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VNFM向VIM发送删除备用VNFC对应的虚拟机请求；
步骤S1112：对于有主备的VNFC情况，此步骤跳过，对于无主备的VNFC情况，VIM向VNFM回复删除备用VNFC对应的虚拟机响应；
步骤S1113：VNFM通知NFVO弹性缩成功；
步骤S1114：VNFM通知EM：VNF容量弹性缩成功；
步骤S1115：NFVO更新VNF和VIM资源池之间的映射关系；
步骤S1116：EM和VNFM更新VNF相关数据。
图12是根据本发明实施例的目标资源占用情况的处理装置的结构框图。如图12所示，该目标资源占用情况的处理装置可以包括：获取模块10，设置为获取VNF scale up和/或scale down的目标资源占用情况；处理模块20，设置为根据目标资源占用情况指示VIM创建或者修改与备用VNFC对应的备用虚拟机，其中，备用虚拟机设置为接管与主用VNFC对应的主用虚拟机正在开展的业务。
采用如图12所示的装置，解决了相关技术中在VNF弹性伸和/或弹性缩的过程中，无法在修改VM的资源占用情况下不影响正常进行的业务的问题，进而实现了优雅scale up/scale down，提高了VNF的可用性。
在优选实施过程中，上述装置可以位于但不限于：NFVO或VNFM。
优选地，如图13所示，上述装置还可以包括：第一触发模块30，设置为在备用虚拟机开始启动后，触发主用虚拟机向备用虚拟机同步数据；第二触发模块40，设置为在确定同步数据的过程已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换，并在倒换操作结束后，删除主用虚拟机。
优选地，如图13所示，上述装置还可以包括：检测模块50，设置为在备用虚拟机重新启动后，检测主用虚拟机向备用虚拟机同步数据的过程是否已经进入稳定状态；第三触发模块60，设置为在确定已经进入稳定状态的情况下，触发主用虚拟机与备用虚拟机进行倒换；重启模块70，设置为在对倒换后的备用虚拟机的资源占用情况进行修改后，重启倒换后的备用虚拟机。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，在scale up/scale down的过程中，可以根据VNF scale up/scale down的目标资源占用情况指示VIM创建(适用于VNF内无主备的情况)或者修改(适用于VNF内有主备的情况)备用VNFC对应的虚拟机，由此解决了相关技术中缺乏针对优雅弹性伸缩的详细解决方案的问题，进而实现了优雅scale up/scale down，提高了VNF的可用性。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种目标资源占用情况的处理方法及装置具有以下有益效果：在scale up/scale down的过程中，可以根据VNF scale up/scale down的目标资源占用情况指示VIM创建或者修改备用VNFC对应的虚拟机，进而实现了优雅scale up/scale down，提高了VNF的可用性。

Claims (10)

  1. 一种目标资源占用情况的处理方法，包括：
    获取虚拟化网络功能VNF纵向弹性伸scale up和/或弹性缩scale down的目标资源占用情况；
    根据所述目标资源占用情况指示虚拟化基础架构管理VIM创建或者修改与备用虚拟化网络功能组件VNFC对应的备用虚拟机，其中，所述备用虚拟机用于接管与主用VNFC对应的主用虚拟机正在开展的业务。
  2. 根据权利要求1所述的方法，其中，在根据所述目标资源占用情况指示所述VIM创建所述备用虚拟机之后，还包括：
    在所述备用虚拟机开始启动后，触发所述主用虚拟机向所述备用虚拟机同步数据；
    在确定同步数据的过程已经进入稳定状态的情况下，触发所述主用虚拟机与所述备用虚拟机进行倒换，并在倒换操作结束后，删除所述主用虚拟机。
  3. 根据权利要求2所述的方法，其中，在所述倒换操作结束后，指示所述VIM删除所述主用虚拟机。
  4. 根据权利要求1所述的方法，其中，在根据所述目标资源占用情况指示所述VIM修改所述备用虚拟机之后，还包括：
    在所述备用虚拟机重新启动后，检测所述主用虚拟机向所述备用虚拟机同步数据的过程是否已经进入稳定状态；
    在确定已经进入所述稳定状态的情况下，触发所述主用虚拟机与所述备用虚拟机进行倒换；
    在对倒换后的备用虚拟机的资源占用情况进行修改后，重启所述倒换后的备用虚拟机。
  5. 根据权利要求2或4所述的方法，其中，在确定所述同步数据的过程已经进入所述稳定状态的情况下，通知VNF触发所述主用虚拟机与所述备用虚拟机进行倒换，由所述备用虚拟机接管所述主用虚拟机当前开展的业务。
  6. 根据权利要求1所述的方法，其中，网络功能虚拟化编排器NFVO或虚拟化网络功能管理VNFM根据所述目标资源占用情况指示所述VIM创建或者修改所述备用虚拟机。
  7. 一种目标资源占用情况的处理装置，包括：
    获取模块，设置为获取虚拟化网络功能VNF纵向弹性伸scale up和/或弹性缩scale down的目标资源占用情况；
    处理模块，设置为根据所述目标资源占用情况指示虚拟化基础架构管理VIM创建或者修改与备用虚拟化网络功能组件VNFC对应的备用虚拟机，其中，所述备用虚拟机用于接管与主用VNFC对应的主用虚拟机正在开展的业务。
  8. 根据权利要求7所述的装置，其中，所述装置还包括：
    第一触发模块，设置为在所述备用虚拟机开始启动后，触发所述主用虚拟机向所述备用虚拟机同步数据；
    第二触发模块，设置为在确定同步数据的过程已经进入稳定状态的情况下，触发所述主用虚拟机与所述备用虚拟机进行倒换，并在倒换操作结束后，删除所述主用虚拟机。
  9. 根据权利要求7所述的装置，其中，所述装置还包括：
    检测模块，设置为在所述备用虚拟机重新启动后，检测所述主用虚拟机向所述备用虚拟机同步数据的过程是否已经进入稳定状态；
    第三触发模块，设置为在确定已经进入所述稳定状态的情况下，触发所述主用虚拟机与所述备用虚拟机进行倒换；
    重启模块，设置为在对倒换后的备用虚拟机的资源占用情况进行修改后，重启所述倒换后的备用虚拟机。
  10. 根据权利要求7至9任一项所述的装置，其中，所述装置位于网络功能虚拟化编排器NFVO或虚拟化网络功能管理VNFM。
PCT/CN2015/070805 2014-09-16 2015-01-15 目标资源占用情况的处理方法及装置 WO2015131671A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410473174.X 2014-09-16
CN201410473174.XA CN105490908A (zh) 2014-09-16 2014-09-16 目标资源占用情况的处理方法及装置

Publications (1)

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

Family

ID=54054524

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/070805 WO2015131671A1 (zh) 2014-09-16 2015-01-15 目标资源占用情况的处理方法及装置

Country Status (2)

Country Link
CN (1) CN105490908A (zh)
WO (1) WO2015131671A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017054197A1 (zh) * 2015-09-30 2017-04-06 华为技术有限公司 一种扩展联动的方法、装置及系统
CN106685784A (zh) * 2015-11-05 2017-05-17 中兴通讯股份有限公司 虚拟化网络功能vnf实例的伸缩方法及装置
WO2017080499A1 (zh) * 2015-11-11 2017-05-18 中兴通讯股份有限公司 管理指示发送、vnf自动伸缩功能的管理方法及装置
WO2017156858A1 (en) * 2016-03-17 2017-09-21 Huawei Technologies Co., Ltd. Virtual network function state scaling
WO2017173901A1 (zh) * 2016-04-08 2017-10-12 中兴通讯股份有限公司 虚拟化网络节能方法、装置及计算机存储介质
CN109120555A (zh) * 2017-06-26 2019-01-01 中兴通讯股份有限公司 一种资源分配方法及系统
CN111898868A (zh) * 2020-07-06 2020-11-06 上海泛微网络科技股份有限公司 一种资源占用显示的方法及装置
CN117009091A (zh) * 2023-10-07 2023-11-07 浪潮(山东)计算机科技有限公司 一种资源调整方法、装置、设备及可读存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105955824B (zh) * 2016-04-21 2019-07-19 华为技术有限公司 一种虚拟资源配置方法以及装置
CN105975330B (zh) * 2016-06-27 2019-06-18 华为技术有限公司 一种网络边缘计算的虚拟网络功能部署方法、装置和系统
CN108023749A (zh) * 2016-11-03 2018-05-11 华为技术有限公司 管理网络切片的方法、设备和系统
WO2018090386A1 (zh) 2016-11-21 2018-05-24 华为技术有限公司 一种nf组件异常的处理方法、设备及系统
CN107153570B (zh) * 2017-04-11 2020-08-25 华为技术有限公司 一种虚拟机的数量控制方法及装置
CN107566470B (zh) * 2017-08-25 2021-01-15 苏州浪潮智能科技有限公司 云数据系统中管理虚拟机的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102708027A (zh) * 2012-05-11 2012-10-03 中兴通讯股份有限公司 一种避免通信设备运行中断的方法及系统
US20130055206A1 (en) * 2011-08-25 2013-02-28 International Business Machines Corporation Synchronously Debugging A Software Program Using A Plurality Of Virtual Machines
CN103136030A (zh) * 2011-11-24 2013-06-05 鸿富锦精密工业（深圳）有限公司 虚拟机管理系统及方法
CN103618627A (zh) * 2013-11-27 2014-03-05 华为技术有限公司 一种管理虚拟机的方法、装置及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1763773A4 (en) * 2004-04-22 2008-12-17 Waratek Pty Ltd MULTIPLE COMPUTER ARCHITECTURE WITH SYNCHRONIZATION
CN102185774A (zh) * 2011-05-10 2011-09-14 中兴通讯股份有限公司 虚拟机无缝迁移的方法、管理器及系统
CN102662750A (zh) * 2012-03-23 2012-09-12 上海交通大学 基于弹性虚拟机池的虚拟机资源优化控制方法及其系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130055206A1 (en) * 2011-08-25 2013-02-28 International Business Machines Corporation Synchronously Debugging A Software Program Using A Plurality Of Virtual Machines
CN103136030A (zh) * 2011-11-24 2013-06-05 鸿富锦精密工业（深圳）有限公司 虚拟机管理系统及方法
CN102708027A (zh) * 2012-05-11 2012-10-03 中兴通讯股份有限公司 一种避免通信设备运行中断的方法及系统
CN103618627A (zh) * 2013-11-27 2014-03-05 华为技术有限公司 一种管理虚拟机的方法、装置及系统

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017054197A1 (zh) * 2015-09-30 2017-04-06 华为技术有限公司 一种扩展联动的方法、装置及系统
US10764132B2 (en) 2015-09-30 2020-09-01 Huawei Technologies Co., Ltd. Scale-out association method and apparatus, and system
CN106685784A (zh) * 2015-11-05 2017-05-17 中兴通讯股份有限公司 虚拟化网络功能vnf实例的伸缩方法及装置
WO2017080499A1 (zh) * 2015-11-11 2017-05-18 中兴通讯股份有限公司 管理指示发送、vnf自动伸缩功能的管理方法及装置
WO2017156858A1 (en) * 2016-03-17 2017-09-21 Huawei Technologies Co., Ltd. Virtual network function state scaling
US10158583B2 (en) 2016-03-17 2018-12-18 Huawei Technologies Co., Ltd. Virtual network function state scaling
WO2017173901A1 (zh) * 2016-04-08 2017-10-12 中兴通讯股份有限公司 虚拟化网络节能方法、装置及计算机存储介质
CN109120555A (zh) * 2017-06-26 2019-01-01 中兴通讯股份有限公司 一种资源分配方法及系统
CN109120555B (zh) * 2017-06-26 2022-10-14 中兴通讯股份有限公司 一种资源分配方法及系统
CN111898868A (zh) * 2020-07-06 2020-11-06 上海泛微网络科技股份有限公司 一种资源占用显示的方法及装置
CN117009091A (zh) * 2023-10-07 2023-11-07 浪潮(山东)计算机科技有限公司 一种资源调整方法、装置、设备及可读存储介质
CN117009091B (zh) * 2023-10-07 2023-12-19 浪潮(山东)计算机科技有限公司 一种资源调整方法、装置、设备及可读存储介质

Also Published As

Publication number Publication date
CN105490908A (zh) 2016-04-13

Similar Documents

Publication Publication Date Title
WO2015131671A1 (zh) 目标资源占用情况的处理方法及装置
CN109831500B (zh) Kubernetes集群中配置文件与Pod的同步方法
CN107209710B (zh) 节点系统、服务器设备、缩放控制方法和程序
KR101939075B1 (ko) 시스템, 가상화 제어 장치, 가상화 제어 장치의 제어 방법 및 프로그램
JP6450835B2 (ja) エネルギーセービング制御方法、管理サーバ及びネットワークデバイス
CN111800285B (zh) 实例迁移方法和装置以及电子设备
KR20190020073A (ko) 가속 자원 처리 방법 및 장치, 및 네트워크 기능 가상화 시스템
CN109495202A (zh) 一种时间同步方法及装置
CN106790092A (zh) 远程过程调用服务端控制系统及方法
CN107967140A (zh) 软件修改的发起方法、发布元数据的方法及装置
WO2023071999A1 (zh) 一种用户匹配方法、装置、设备及存储介质
WO2015014152A1 (zh) 一种访问共享内存的方法和装置
CN107786360A (zh) 网络功能虚拟化管理方法及装置
CN107704550A (zh) 文件迁移方法、装置以及计算机可读存储介质
JP2024524248A (ja) 電気車両充電管理及びクライアントデバイス
CN108984334A (zh) 用于管理会话的方法和设备
CN114124697A (zh) 一种网络切换方法、网络切换装置及存储介质
CN106462421B (zh) 电信设备以及用于更新电信设备中的软件的方法
CN114579185B (zh) 用于迁移应用的方法、电子设备和计算机程序产品
CN110461015A (zh) 一种进行网络切换的方法及设备
KR20110070465A (ko) 단말 간 세션이동시 세션이동이 가능한 단말정보를 제공하는 대상단말 정보 제공장치 및 방법
JP2018112898A (ja) 制御装置および制御方法
EP4009167A1 (en) Instantiated request generation method, interface virtual machine configuration method, nfvo, and vim
CN111818526B (zh) 一种数据同步方法及装置
CN112839068B (zh) 一种采用nfv部件部署的网络节点的管理方法及装置

Legal Events

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

Ref document number: 15758953

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15758953

Country of ref document: EP

Kind code of ref document: A1