CN105490908A - Method and device for processing occupied conditions of target resource - Google Patents

Method and device for processing occupied conditions of target resource Download PDF

Info

Publication number
CN105490908A
CN105490908A CN201410473174.XA CN201410473174A CN105490908A CN 105490908 A CN105490908 A CN 105490908A CN 201410473174 A CN201410473174 A CN 201410473174A CN 105490908 A CN105490908 A CN 105490908A
Authority
CN
China
Prior art keywords
virtual machine
subsequent use
vnfc
vnf
vnfm
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
CN201410473174.XA
Other languages
Chinese (zh)
Inventor
陶运锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201410473174.XA priority Critical patent/CN105490908A/en
Priority to PCT/CN2015/070805 priority patent/WO2015131671A1/en
Publication of CN105490908A publication Critical patent/CN105490908A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/64Hybrid switching systems
    • H04L12/6418Hybrid transport

Abstract

The invention discloses a method and device for processing occupied conditions of a target resource, and the method comprises the steps: obtaining the occupied condition of the target resource of VNF scale up and/or scale down; and indicting a VIM to build or modify a standby virtual machine corresponding to a VNFC according to the occupied condition of the target resource, wherein the standby virtual machine is used for taking charge of a business carried out by a main virtual machine corresponding to a main VNFC. According to the technical scheme of the invention, the method and device achieve the elegant scale up/scale down, and improve the availability of the VNF.

Description

Target resource takies processing method and the device of situation
Technical field
The present invention relates to the communications field, take processing method and the device of situation in particular to a kind of target resource.
Background technology
Virtual (the NetworkFunctionsVirtualization of network function, referred to as NFV) technology refers to legacy network function, as: proxy call conversation control function entity (ProxycallsessioncontrolFunction, referred to as P-CSCF), query call conversation control function entity (InterrogatingcallsessioncontrolFunction, referred to as I-CSCF), service call session control function entity (ServingcallsessioncontrolFunction, referred to as S-CSCF), home subscriber server (HomesubscriberServer, referred to as HSS) and application server (ApplicationServer, referred to as AS) etc. carry out virtual, by virtual network function assembly (VirtualizedNetworkFunctionComponent is referred to as VNFC) is deployed on cloud virtual machine, thus realize the virtual of network function, network function after virtual is called virtual network function (VirtualizedNetworkFunction, referred to as VNF).Following technical advantage can be brought after network function is virtual:
1) network function and hardware decouple, achieves heterogeneous network function, the network function of different producer operates on identical hardware, and operator, when disposing new network function, can reuse easily, protects operator's investment;
2) because network function can operate on general hardware, the speed that operator carries out new business is accelerated;
3) owing to adopting common hardware, buying can reduce costs on a large scale;
4) because network function has elastic telescopic function, network function, because taking resource, improves resource utilization, meanwhile, when load is lower, can closed portion generic server, and so green energy conservation more.
A key function of NFV technology is network function elastic telescopic technology, and the triggering mode of elastic telescopic has following two kinds:
The first, automatically trigger, namely VNF can according to the resource occupation of the load condition dynamic conditioning of self self;
The second, manual triggers, namely user manually can adjust the resource occupation of VNF according to managerial demand.
The adjustment mode of elastic telescopic is also divided into following two kinds:
The first, laterally adjustment, namely adjusted by the mode increased or deletes virtual machine, be referred to as transverse elasticity and stretch (scaleout/scalein);
The second, longitudinally adjustment, the mode namely taking resource by adjusting virtual machine adjusts, and is referred to as longitudinal elasticity flexible (scaleup/scaledown).
Define VNF elastic telescopic flow process in existing ETSI (ETSI) specification, wherein, describe following a few partial content:
(1) the elastic telescopic flow process of Resourse Distribute is performed by the virtual composer of network function (NetworkFunctionsVirtualizationOrchestrator, referred to as NFVO);
Fig. 1 is the VNF elastic telescopic flow chart being performed Resourse Distribute in the ETSI specification according to correlation technique by NFVO.As shown in Figure 1, this flow process can comprise following treatment step:
Step S101: sender (such as OSS) sends elastic telescopic request to NFVO;
Step S102:NFVO carries out legitimacy verification to elastic telescopic request, checks whether this demand meets strategy configuration;
The VNFM that step S103:NFVO finds this VNF corresponding, if this VNF does not have corresponding VNFM, NFVO creates new VNFM;
Step S104:NFVO, before execution knee springing, carries out feasibility verification to elastic telescopic request, and reserved related resource, whole S104 step is for optional, if S104 performs, then must all perform, S104 comprises again following sub-step:
Step S104a:NFVO asks VNFM to carry out feasibility inspection to elastic telescopic request;
Step S104b:VNFM performs any necessary preparation, these work may comprise according to VNF specific restriction amendment/supplement elastic telescopic request enter ginseng;
Step S104c:VNFM returns the elastic telescopic request after renewal to NFVO;
Step S104d:NFVO asks VIM to check availability also these resources reserved of resource (calculating, storage, network);
Step S104e:VIM checks the availability of resource (calculating, storage, network) and reserves these resources;
Step S104f:VIM returns the result of resource reservation to NFVO;
Step S105:NFVO sends elastic telescopic request to VNFM, comprises elastic telescopic data, if step S104 performs, then also comprises resource obligate information;
Step S106:VNFM performs the preparation of any needs: verify elastic telescopic request, parameter verification, may also comprise according to VNF specific restriction amendment/supplement elastic telescopic request enter ginseng;
It is to be noted that this step is consistent with step S104b, if step S104 performs, then skip this step;
Step S107:VNFM replys resource to NFVO and changes response;
Step S108:NFVO sends resource (calculating, storage, network) to VIM and changes request;
Step S109:VIM revises VNF internal network as required;
The step S110:VIM new virtual machine of instantiation link internal network as required;
Step S111:VIM replys resource to NFVO and has changed response;
Step S112:NFVO notifies that VNFM resource has changed;
Step S113:VNFM replys response to NFVO;
Step S114:NFVO is to request elasticity recovery application success response.
(2) manage by VNF the elastic telescopic flow process that (VNFManager, referred to as VNFM) performs Resourse Distribute, wherein this partial content can also specifically be divided into following technology chapter:
1) process of VNF appliance for releasing single;
Fig. 2 stretches flow chart by the VNF automatic elastic of VNFM execution Resourse Distribute in the ETSI specification according to correlation technique.As shown in Figure 2, this flow process can comprise following treatment step:
Step S201:VNFM collects measurement data (application is relevant) from VNF;
Step S202:VNFM detects that system loading exceedes elasticity and stretches threshold value, triggers elasticity and stretches request;
Step S203:VNFM asks NFVO to verify the elasticity request of stretching;
Step S204:NFVO determines that performing elasticity stretches, and according to capacity data storehouse and the VNF masterplate of VNF, calculating elastic stretches the resource (calculate, store, network) of needs, and whether check currently has enough resources;
Step S205:NFVO mandate VNFM carries out elasticity to VNF and stretches;
Step S206:VNFM, according to the instruction of NFVO, sends request to VIM and creates and start VM;
Step S207:VIM instantiation also starts new VM, and replys success response to VNFM;
Step S208:VNFM configures related data on VNF;
Step S209:VNFM stretches success response to NFVO elasticity recovery;
Step S210:VNFM notifies that this VNF capacity of EM changes;
Step S211:NFVO preserves the mapping relations between VNF and VIM resource pool;
Step S212:EM and VNFM upgrades VNF related data;
Step S213:EM configures VNF related application data.
2) process of the VNF appliance for releasing single of being initiated by NE management (Elementmanagement, referred to as EM);
Fig. 3 is that the VNF elasticity that the EM performing Resourse Distribute by VNFM in the ETSI specification according to correlation technique initiates stretches flow chart.As shown in Figure 3, this flow process can comprise following treatment step:
Step S301: manual operator manually performs elasticity and stretches request on EM, or EM stretches request according to detection triggers automatic elastic;
Step S302:EM sends elasticity to VNFM and stretches request;
Step S303:VNFM asks NFVO to verify the elasticity request of stretching;
Step S304:NFVO determines that performing elasticity stretches, and according to capacity data storehouse and the VNF masterplate of VNF, calculating elastic stretches the resource (calculate, store, network) of needs, and whether check currently has enough resources;
Step S305:NFVO mandate VNFM carries out elasticity to VNF and stretches;
Step S306:VNFM, according to the instruction of NFVO, sends request to VIM and creates and start VM;
Step S307:VIM instantiation also starts new VM, and replys success response to VNFM;
Step S308:VNFM configures related data on VNF;
Step S309:VNFM stretches success response to NFVO elasticity recovery;
Step S310:VNFM notifies that this VNF capacity of EM changes;
Step S311:NFVO preserves the mapping relations between VNF and VIM resource pool;
Step S312:M and VNFM upgrades VNF related data;
Step S313:EM configures VNF related application data.
3) process that automatically contracts of VNF;
Fig. 4 is the VNF automatic elastic contracting flow chart being performed Resourse Distribute in the ETSI specification according to correlation technique by VNFM.As shown in Figure 4, the method can comprise following treatment step:
Step S401:VNFM collects measurement data (application is relevant) from VNF;
Step S402:VNFM detects that system loading is lower than elasticity contracting threshold value, triggers elasticity contracting request;
Step S403:VNFM asks NFVO to verify elasticity contracting request;
Step S404:NFVO determines to perform elasticity contracting according to collocation strategy
Step S405:NFVO authorizes VNFM to carry out elasticity contracting to VNF;
Step S406:VNF gracefulness closes VNFC (on ongoing business without impact);
Step S407: when the VNFC (VM) being about to delete is above zero load, VNFM asks VIM to delete VM;
Step S408:VIM deletes VM and notifies VNFM;
Step S409:VNFM notifies that NFVO elasticity shortens merit into;
Step S410:VNFM notifies that EM:VNF cubic elasticity shortens merit into;
Step S411:NFVO upgrades the mapping relations between VNF and VIM resource pool;
Step S412:EM and VNFM upgrades VNF related data.
4) process that the VNF initiated by EM contracts automatically;
Fig. 5 is the VNF elasticity contracting flow chart of initiating according to the EM performing Resourse Distribute by VNFM of correlation technique.As shown in Figure 5, this flow process can comprise following treatment step:
Step S501: manual operator manually performs elasticity contracting request on EM, or EM is according to detection triggers automatic elastic contracting request;
Step S502:EM sends to VNFM and triggers elasticity contracting request;
Step S503:VNFM asks NFVO to verify elasticity contracting request;
Step S504:NFVO determines to perform elasticity contracting according to collocation strategy
Step S505:NFVO authorizes VNFM to carry out elasticity contracting to VNF;
Step S506:VNF gracefulness closes VNFC (on ongoing business without impact);
Step S507: when the VNFC (VM) being about to delete is above zero load, VNFM asks VIM to delete VM;
Step S508:VIM deletes VM and notifies VNFM;
Step S509:VNFM notifies that NFVO elasticity shortens merit into;
Step S510:VNFM notifies that EM:VNF cubic elasticity shortens merit into;
Step S511:NFVO upgrades the mapping relations between VNF and VIM resource pool;
Step S512:EM and VNFM upgrades VNF related data.
It should be noted that, the flow process described in above-mentioned (1) and (2) does not all distinguish scaleout/scalein or scaleup/scaledown.
The generalized flowsheet of what above-mentioned flow process described is elastic telescopic, be applicable to the elastic telescopic of scaleup/scaledown and scaleup/scalein two kinds of modes, but the defect of such scheme is:
When there is the elastic telescopic of scaleup/scaledown mode in VNF,
Do not describe the need of graceful elastic telescopic and how elastic telescopic in Fig. 1;
Do not describe in Fig. 2 and to stretch the need of graceful elasticity and how elasticity is stretched;
Do not describe in Fig. 3 and to stretch the need of graceful elasticity and how elasticity is stretched;
Need the contracting of graceful elasticity although describe in Fig. 4, do not describe how elasticity contracts;
Need graceful elasticity to stretch although describe in Fig. 5, do not describe how elasticity is stretched;
In the application of reality, often require that VNF can graceful elastic telescopic, in order to avoid affect ongoing business, such as: as the P-CSCF of field of telecommunications, I-CSCF, when S-CSCF sends elastic telescopic, telecom operators' General Requirements can not to ongoing calling, registration etc. has an impact, for the elastic telescopic of scaleup/scaledown mode, in the process that VNF elasticity is stretched and/or elasticity contracts, the occupation condition revising virtual machine (VM) is needed (to calculate, store, network), when after the occupation condition amendment that VIM completes VM, need to restart VM just can come into force, and restart VM and must affect ongoing business.
In sum, from current ETSI specification, still not for the detailed settlement project of graceful elastic telescopic.
Summary of the invention
The invention provides processing method and device that a kind of target resource takies situation, at least to solve in correlation technique in the process that VNF elasticity is stretched and/or elasticity contracts, under the occupation condition of amendment VM, cannot not affect the problem of the business of normally carrying out.
According to an aspect of the present invention, the processing method that a kind of target resource takies situation is provided.
The processing method taking situation according to the target resource of the embodiment of the present invention comprises: the target resource obtaining VNFscaleup and/or scaledown takies situation; The virtual machine for subsequent use that situation instruction VIM creates or amendment is corresponding with VNFC for subsequent use is taken according to target resource, wherein, the business that virtual machine for subsequent use is being carried out for taking over the primary virtual machine corresponding with primary VNFC.
Preferably, after taking situation instruction VIM according to target resource and creating virtual machine for subsequent use, also comprise: after virtual machine for subsequent use starts startup, trigger primary virtual machine to virtual machine synchrodata for subsequent use; When determining that the process of synchrodata has entered stable state, trigger primary virtual machine and virtual machine for subsequent use is switched, and after switching operation terminates, delete primary virtual machine.
Preferably, after switching operation terminates, instruction VIM deletes primary virtual machine.
Preferably, after taking situation instruction according to target resource VIM revises virtual machine for subsequent use, also comprise: after virtual machine for subsequent use restarts, detect primary virtual machine and whether enter stable state to the process of virtual machine synchrodata for subsequent use; When determining to enter stable state, trigger primary virtual machine and virtual machine for subsequent use is switched; After the occupation condition of the virtual machine for subsequent use after switching is modified, restart the virtual machine for subsequent use after switching.
Preferably, when determining that the process of synchrodata has entered stable state, notice VNF triggers primary virtual machine and virtual machine for subsequent use is switched, and takes over the current business of carrying out of primary virtual machine by virtual machine for subsequent use.
Preferably, NFVO or VNFM takies situation instruction VIM establishment according to target resource or revises virtual machine for subsequent use.
According to a further aspect in the invention, the processing unit that a kind of target resource takies situation is provided.
The processing unit taking situation according to the target resource of the embodiment of the present invention comprises: acquisition module, takies situation for the target resource obtaining VNFscaleup and/or scaledown; Processing module, for taking the virtual machine for subsequent use that situation instruction VIM creates or amendment is corresponding with VNFC for subsequent use according to target resource, wherein, the business that virtual machine for subsequent use is being carried out for taking over the primary virtual machine corresponding with primary VNFC.
Preferably, said apparatus also comprises: the first trigger module, for start startup at virtual machine for subsequent use after, triggers primary virtual machine to virtual machine synchrodata for subsequent use; Second trigger module, for when determining that the process of synchrodata has entered stable state, triggers primary virtual machine and virtual machine for subsequent use is switched, and after switching operation terminates, deletes primary virtual machine.
Preferably, said apparatus also comprises: detection module, for after virtual machine for subsequent use restarts, detects primary virtual machine and whether enters stable state to the process of virtual machine synchrodata for subsequent use; 3rd trigger module, for when determining to enter stable state, triggers primary virtual machine and virtual machine for subsequent use is switched; Restart module, for after modifying to the occupation condition of the virtual machine for subsequent use after switching, restart the virtual machine for subsequent use after switching.
Preferably, said apparatus is positioned at NFVO or VNFM.
By the embodiment of the present invention, the target resource obtaining VNFscaleup and/or scaledown is adopted to take situation; The virtual machine for subsequent use that situation instruction VIM creates or amendment is corresponding with VNFC for subsequent use is taken according to target resource, wherein, the business that virtual machine for subsequent use is being carried out for taking over the primary virtual machine corresponding with primary VNFC, solve in correlation technique VNF elasticity stretch and/or elasticity contracting process in, the problem of the business of normally carrying out cannot not be affected under the occupation condition of amendment VM, and then achieve graceful scaleup/scaledown, improve the availability of VNF.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Fig. 1 is the VNF elastic telescopic flow chart being performed Resourse Distribute in the ETSI specification according to correlation technique by NFVO;
Fig. 2 stretches flow chart by the VNF automatic elastic of VNFM execution Resourse Distribute in the ETSI specification according to correlation technique;
Fig. 3 is that the VNF elasticity that the EM performing Resourse Distribute by VNFM in the ETSI specification according to correlation technique initiates stretches flow chart;
Fig. 4 is the VNF automatic elastic contracting flow chart being performed Resourse Distribute in the ETSI specification according to correlation technique by VNFM;
Fig. 5 is the VNF elasticity contracting flow chart of initiating according to the EM performing Resourse Distribute by VNFM of correlation technique;
Fig. 6 is the flow chart of the processing method taking situation according to the target resource of the embodiment of the present invention;
Fig. 7 is the VNF elastic telescopic flow chart being performed Resourse Distribute according to the preferred embodiment of the invention by NFVO;
Fig. 8 stretches flow chart by the VNF automatic elastic of VNFM execution Resourse Distribute according to the preferred embodiment of the invention;
Fig. 9 is that the VNF elasticity that the EM performing Resourse Distribute by VNFM according to the preferred embodiment of the invention initiates stretches flow chart;
Figure 10 is the VNF automatic elastic contracting flow chart being performed Resourse Distribute according to the preferred embodiment of the invention by VNFM;
Figure 11 is the VNF elasticity contracting flow chart that the EM performing Resourse Distribute by VNFM according to the preferred embodiment of the invention initiates;
Figure 12 is the structured flowchart of the processing unit taking situation according to the target resource of the embodiment of the present invention;
Figure 13 is that target resource takies the structured flowchart of the processing unit of situation according to the preferred embodiment of the invention.
Embodiment
Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.
Fig. 6 is the flow chart of the processing method taking situation according to the target resource of the embodiment of the present invention.As shown in Figure 1, the processing method that this target resource takies situation can comprise:
Step S602: the target resource obtaining VNFscaleup and/or scaledown takies situation;
Step S604: take the virtual machine for subsequent use that situation instruction VIM creates or amendment is corresponding with VNFC for subsequent use according to target resource, wherein, the business that virtual machine for subsequent use is being carried out for taking over the primary virtual machine corresponding with primary VNFC.
The detailed settlement project for graceful elastic telescopic is lacked in correlation technique.Adopt method as shown in Figure 6, in the process of scaleup/scaledown, NFVO can take situation according to the target resource of VNFscaleup/scaledown and indicate virtual architecture to manage (VirtualizedInfrastructureManager, referred to as VIM) create (being applicable to the situation that dereliction in VNF is standby) or amendment (being applicable to there is active and standby situation in VNF) virtual machine that VNFC for subsequent use is corresponding, owing to there being VNFC adapter business for subsequent use, maintain business without impact or less impact, thus solve in correlation technique VNF elasticity stretch and/or elasticity contracting process in, the problem of the business of normally carrying out cannot not be affected under the occupation condition of amendment VM, and then achieve graceful scaleup/scaledown, improve the availability of VNF.
Preferably, in step S604, after taking situation instruction according to target resource VIM creates virtual machine for subsequent use, following operation can also be comprised:
Step S1: after virtual machine for subsequent use starts startup, trigger primary virtual machine to virtual machine synchrodata for subsequent use;
Step S2: when determining that the process of synchrodata has entered stable state, triggers primary virtual machine and virtual machine for subsequent use is switched, and after switching operation terminates, deletes primary virtual machine.
In a preferred embodiment, inner for VNF VNFC can be divided into two kinds of situations: have active and standby standby with dereliction; The meaning of VNFC for subsequent use is (may be primary VNFC fault, overhaul of the equipments etc.) to take over the business performing primary VNFC as required.Whether VNF has active and standby is describe in the virtual network function descriptor (Virtualnetworkfunctiondescriptor, referred to as VNFD), and whether the VNFC that NFVO and VNFM can perceive VNF by VNFD has active and standby.There is active and standby and dereliction for two kinds of situations for VNF inside VNFC, for the situation that VNF inside VNFC dereliction is standby, active and standby function also can be utilized to reach the object of graceful scaleup and scaledown.Compared with having active and standby situation with the inner VNFC of VNF, first need the VNFC to being about to carry out scaleup/scaledown to create VNFC for subsequent use, the virtual machine that this VNFC for subsequent use is corresponding takies situation according to the target resource of scaleup/scaledown to create.Then start to start virtual machine corresponding to VNFC for subsequent use, trigger virtual machine corresponding to primary VNFC to virtual machine synchrodata for subsequent use (such as: the synchrodata function of live migration of virtual machine), after synchrodata enters stable state, trigger masterslave switchover (such as: the handoff functionality of live migration of virtual machine), after masterslave switchover terminates, delete the virtual machine that former primary VNFC is corresponding, the process of scaleup/scaledown just finishes.In this process, owing to there being VNFC adapter business for subsequent use, maintain on business without impact or less impact, achieve graceful scaleup/scaledown function.
In preferred implementation process, after switching operation terminates, VIM can be indicated to delete primary virtual machine.
For there being active and standby situation in VNF, after masterslave switchover terminates, then graceful scaleup/scaledown just completes, and for the situation that dereliction in VNF is standby, after masterslave switchover terminates, NFVO indicates VIM to delete virtual machine corresponding to new VNFC for subsequent use.
Preferably, in step S604, after taking situation instruction according to target resource VIM revises virtual machine for subsequent use, can also comprise the following steps:
Step S3: after virtual machine for subsequent use restarts, detects primary virtual machine and whether enters stable state to the process of virtual machine synchrodata for subsequent use;
Step S4: when determining to enter stable state, triggers primary virtual machine and virtual machine for subsequent use is switched;
Step S5: after the occupation condition of the virtual machine for subsequent use after switching is modified, restart the virtual machine for subsequent use after switching.
In a preferred embodiment, active and standby situation is had for VNF inside VNFC, this active and standby function can be utilized to reach the object of graceful scaleup and scaledown, namely first take situation according to the target resource of scaleup/scaledown and revise virtual machine corresponding to VNFC for subsequent use and restart virtual machine.After virtual machine activation for subsequent use, primary virtual machine is to dynamic synchronization data for subsequent use, and after synchrodata enters stable state, trigger masterslave switchover, virtual machine for subsequent use becomes primary virtual machine, and primary virtual machine then becomes virtual machine for subsequent use.Then, revise the occupation condition of new virtual machine for subsequent use, restart new virtual machine for subsequent use, the process of scaleup/scaledown just finishes, in this process, owing to there being VNFC adapter business for subsequent use, maintain on business without impact or less impact, achieve graceful scaleup/scaledown function.
In preferred implementation process, when determining that the process of synchrodata has entered stable state, notice VNF triggers primary virtual machine and virtual machine for subsequent use is switched, and takes over the current business of carrying out of primary virtual machine by virtual machine for subsequent use.
After synchrodata enters stable state, NFVO notifies that VNF triggers VNFC masterslave switchover, and taken over the virtual machine business of primary VNFC by the virtual machine of VNFC for subsequent use, former primary VNFC becomes VNFC for subsequent use, and former VNFC for subsequent use becomes primary VNFC.
In preferred implementation process, situation can be taken by NFVO or VNFM according to target resource and indicate VIM create or revise virtual machine for subsequent use.If perform Resourse Distribute by VNFM, then take situation by VNFM according to the target resource of VNFscaleup/scaledown and indicate VIM to create (being applicable to the situation that dereliction in VNF is standby) or amendment (being applicable to there is active and standby situation in VNF) virtual machine that VNFC for subsequent use is corresponding; If perform Resourse Distribute by VNFM, for there being active and standby situation in VNF, after masterslave switchover terminates, then VIM is indicated to delete virtual machine corresponding to new VNFC for subsequent use by VNFM.
Below in conjunction with the preferred implementation shown in Fig. 7 to Figure 11, above-mentioned preferred implementation process is further described.
Fig. 7 is the VNF elastic telescopic flow chart being performed Resourse Distribute according to the preferred embodiment of the invention by NFVO.As shown in Figure 7, this flow process can comprise following treatment step:
Step S701: sender (such as OSS) sends elastic telescopic request to NFVO;
Step S702:NFVO carries out legitimacy verification to elastic telescopic request, checks whether this demand meets strategy configuration;
The VNFM that step S703:NFVO finds this VNF corresponding, if this VNF does not have corresponding VNFM, NFVO creates new VNFM;
Step S704:NFVO, before execution knee springing, carries out feasibility verification to elastic telescopic request, and reserved related resource, whole S704 step is for optional, if S704 performs, then must all perform, S704 comprises again following sub-step:
Step S704a:NFVO asks VNFM to carry out feasibility inspection to elastic telescopic request;
Step S704b:VNFM performs any necessary preparation, these work may comprise according to VNF specific restriction amendment/supplement elastic telescopic request enter ginseng;
Step S704c:VNFM returns the elastic telescopic request after renewal to NFVO;
Step S704d:NFVO asks VIM to check availability also these resources reserved of resource (calculating, storage, network);
Step S704e:VIM checks the availability of resource (calculating, storage, network) and reserves these resources;
Step S704f:VIM returns the result of resource reservation to NFVO;
Step S705:NFVO sends elastic telescopic request to VNFM, comprises elastic telescopic data, if step S704 performs, then also comprises resource obligate information;
Step S706:VNFM performs the preparation of any needs: verify elastic telescopic request, parameter verification, may also comprise according to VNF specific restriction amendment/supplement elastic telescopic request enter ginseng;
It is to be noted that this step is consistent with step S704b, if step S704 performs, then skip this step;
Step S707:VNFM replys resource to NFVO and changes response;
Step S708:VNFM sends the request creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VIM;
Step S709:VIM creates or revises the network of virtual machine association corresponding to VNFC for subsequent use;
Step S710:VIM creates (being applicable to dereliction for VNFC) or revises virtual machine corresponding to (being applicable to active and standby VNFC) VNFC for subsequent use and be associated with network of relation;
Step S711:VIM replys the response creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VNFM;
Step S712: primary VNFC to VNFC synchrodata for subsequent use;
Step S713:VNFM sends the request of VNFC masterslave switchover to VNF;
Step S714: after primary VNFC and VNFC synchrodata for subsequent use enter stable state, VNF control to trigger VNFC masterslave switchover, and when switching successfully, VNF replys the success response of VNFC masterslave switchover to VNFM;
Step S715: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VNFM sends to VIM and deletes virtual machine request corresponding to VNFC for subsequent use;
Step S716: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VIM replys to VNFM and deletes virtual machine response corresponding to VNFC for subsequent use;
Step S717:NFVO notifies that VNFM resource has changed;
Step S718:VNFM replys response to NFVO;
Step S719:NFVO is to request elasticity recovery application success response.
Fig. 8 stretches flow chart by the VNF automatic elastic of VNFM execution Resourse Distribute according to the preferred embodiment of the invention.As shown in Figure 8, this flow process can comprise following treatment step:
Step S801:VNFM collects measurement data (application is relevant) from VNF;
Step S802:VNFM detects that system loading exceedes elasticity and stretches threshold value, triggers elasticity and stretches request;
Step S803:VNFM asks NFVO to verify the elasticity request of stretching;
Step S804:NFVO determines that performing elasticity stretches, and according to capacity data storehouse and the VNF masterplate of VNF, calculating elastic stretches the resource (calculate, store, network) of needs, and whether check currently has enough resources;
Step S805:NFVO mandate VNFM carries out elasticity to VNF and stretches;
Step S806:VNFM sends the request creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VIM;
Step S807:VIM replys the response creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VNFM;
Step S808: primary VNFC to VNFC synchrodata for subsequent use;
Step S809:VNFM sends the request of VNFC masterslave switchover to VNF;
Step S810: after primary VNFC and VNFC synchrodata for subsequent use enter stable state, VNF control to trigger VNFC masterslave switchover, and when switching successfully, VNF replys the success response of VNFC masterslave switchover to VNFM;
Step S811: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VNFM sends to VIM and deletes virtual machine request corresponding to VNFC for subsequent use;
Step S812: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VIM replys to VNFM and deletes virtual machine response corresponding to VNFC for subsequent use;
Step S813:VNFM configures related data on VNF;
Step S814:VNFM stretches success response to NFVO elasticity recovery;
Step S815:VNFM notifies that this VNF capacity of EM changes;
Step S816:NFVO preserves the mapping relations between VNF and VIM resource pool;
Step S817:EM and VNFM upgrades VNF related data;
Step S818:EM configures VNF related application data.
Fig. 9 is that the VNF elasticity that the EM performing Resourse Distribute by VNFM according to the preferred embodiment of the invention initiates stretches flow chart.As shown in Figure 9, this flow process can comprise following treatment step:
Step S901: manual operator manually performs elasticity and stretches request on EM, or EM stretches request according to detection triggers automatic elastic;
Step S902:EM sends elasticity to VNFM and stretches request;
Step S903:VNFM asks NFVO to verify the elasticity request of stretching;
Step S904:NFVO determines that performing elasticity stretches, and according to capacity data storehouse and the VNF masterplate of VNF, calculating elastic stretches the resource (calculate, store, network) of needs, and whether check currently has enough resources;
Step S905:NFVO mandate VNFM carries out elasticity to VNF and stretches;
Step S906:VNFM sends the request creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VIM;
Step S907:VIM replys the response creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VNFM;
Step S908: primary VNFC to VNFC synchrodata for subsequent use;
Step S909:VNFM sends the request of VNFC masterslave switchover to VNF;
Step S910: after primary VNFC and VNFC synchrodata for subsequent use enter stable state, VNF control to trigger VNFC masterslave switchover, and when switching successfully, VNF replys the success response of VNFC masterslave switchover to VNFM;
Step S911: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VNFM sends to VIM and deletes virtual machine request corresponding to VNFC for subsequent use;
Step S912: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VIM replys to VNFM and deletes virtual machine response corresponding to VNFC for subsequent use;
Step S913:VNFM configures related data on VNF;
Step S914:VNFM stretches success response to NFVO elasticity recovery;
Step S915:VNFM notifies that this VNF capacity of EM changes;
Step S916:NFVO preserves the mapping relations between VNF and VIM resource pool;
Step S917:M and VNFM upgrades VNF related data;
Step S918:EM configures VNF related application data.
Figure 10 is the VNF automatic elastic contracting flow chart being performed Resourse Distribute according to the preferred embodiment of the invention by VNFM.As shown in Figure 10, the method can comprise following treatment step:
Step S1001:VNFM collects measurement data (application is relevant) from VNF;
Step S1002:VNFM detects that system loading is lower than elasticity contracting threshold value, triggers elasticity contracting request;
Step S1003:VNFM asks NFVO to verify elasticity contracting request;
Step S1004:NFVO determines to perform elasticity contracting according to collocation strategy
Step S1005:NFVO authorizes VNFM to carry out elasticity contracting to VNF;
Step S1006:VNFM sends the request creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VIM;
Step S1007:VIM replys the response creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VNFM;
Step S1008: primary VNFC to VNFC synchrodata for subsequent use;
Step S1009:VNFM sends the request of VNFC masterslave switchover to VNF;
Step S1010: after primary VNFC and VNFC synchrodata for subsequent use enter stable state, VNF control to trigger VNFC masterslave switchover, and when switching successfully, VNF replys the success response of VNFC masterslave switchover to VNFM;
Step S1011: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VNFM sends to VIM and deletes virtual machine request corresponding to VNFC for subsequent use;
Step S1012: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VIM replys to VNFM and deletes virtual machine response corresponding to VNFC for subsequent use;
Step S1013:VNFM notifies that NFVO elasticity shortens merit into;
Step S1014:VNFM notifies that EM:VNF cubic elasticity shortens merit into;
Step S1015:NFVO upgrades the mapping relations between VNF and VIM resource pool;
Step S1016:EM and VNFM upgrades VNF related data.
Figure 11 is the VNF elasticity contracting flow chart that the EM performing Resourse Distribute by VNFM according to the preferred embodiment of the invention initiates.As shown in figure 11, this flow process can comprise following treatment step:
Step S1101: manual operator manually performs elasticity contracting request on EM, or EM is according to detection triggers automatic elastic contracting request;
Step S1102:EM sends to VNFM and triggers elasticity contracting request;
Step S1103:VNFM asks NFVO to verify elasticity contracting request;
Step S1104:NFVO determines to perform elasticity contracting according to collocation strategy
Step S1105:NFVO authorizes VNFM to carry out elasticity contracting to VNF;
Step S1106:VNFM sends the request creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VIM;
Step S1107:VIM replys the response creating (being applicable to dereliction for VNFC) or amendment (being applicable to active and standby VNFC) VNFC for subsequent use to VNFM;
Step S1108: primary VNFC to VNFC synchrodata for subsequent use;
Step S1109:VNFM sends the request of VNFC masterslave switchover to VNF;
Step S1110: after primary VNFC and VNFC synchrodata for subsequent use enter stable state, VNF control to trigger VNFC masterslave switchover, and when switching successfully, VNF replys the success response of VNFC masterslave switchover to VNFM;
Step S1111: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VNFM sends to VIM and deletes virtual machine request corresponding to VNFC for subsequent use;
Step S1112: for there being active and standby VNFC situation, this step is skipped, for the VNFC situation that dereliction is standby, VIM replys to VNFM and deletes virtual machine response corresponding to VNFC for subsequent use;
Step S1113:VNFM notifies that NFVO elasticity shortens merit into;
Step S1114:VNFM notifies that EM:VNF cubic elasticity shortens merit into;
Step S1115:NFVO upgrades the mapping relations between VNF and VIM resource pool;
Step S1116:EM and VNFM upgrades VNF related data.
Figure 12 is the structured flowchart of the processing unit taking situation according to the target resource of the embodiment of the present invention.As shown in figure 12, the processing unit that this target resource takies situation can comprise: acquisition module 10, takies situation for the target resource obtaining VNFscaleup and/or scaledown; Processing module 20, for taking the virtual machine for subsequent use that situation instruction VIM creates or amendment is corresponding with VNFC for subsequent use according to target resource, wherein, the business that virtual machine for subsequent use is being carried out for taking over the primary virtual machine corresponding with primary VNFC.
Adopt device as shown in figure 12, solve in correlation technique VNF elasticity stretch and/or elasticity contracting process in, under the occupation condition of amendment VM, cannot not affect the problem of the business of normally carrying out, and then achieve graceful scaleup/scaledown, improve the availability of VNF.
In preferred implementation process, said apparatus can be positioned at but be not limited to: NFVO or VNFM.
Preferably, as shown in figure 13, said apparatus can also comprise: the first trigger module 30, for start startup at virtual machine for subsequent use after, triggers primary virtual machine to virtual machine synchrodata for subsequent use; Second trigger module 40, for when determining that the process of synchrodata has entered stable state, triggers primary virtual machine and virtual machine for subsequent use is switched, and after switching operation terminates, deletes primary virtual machine.
Preferably, as shown in figure 13, said apparatus can also comprise: detection module 50, for after virtual machine for subsequent use restarts, detects primary virtual machine and whether enters stable state to the process of virtual machine synchrodata for subsequent use; 3rd trigger module 60, for when determining to enter stable state, triggers primary virtual machine and virtual machine for subsequent use is switched; Restart module 70, for after modifying to the occupation condition of the virtual machine for subsequent use after switching, restart the virtual machine for subsequent use after switching.
From above description, can find out, above embodiments enable following technique effect (it should be noted that these effects are effects that some preferred embodiment can reach): adopt the technical scheme that the embodiment of the present invention provides, in the process of scaleup/scaledown, situation instruction VIM can be taken according to the target resource of VNFscaleup/scaledown and create (being applicable to the situation that dereliction in VNF is standby) or amendment (being applicable to there is active and standby situation in VNF) virtual machine that VNFC for subsequent use is corresponding, solve in correlation technique the problem of the detailed settlement project lacked for graceful elastic telescopic thus, and then achieve graceful scaleup/scaledown, improve the availability of VNF.
Obviously, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, they can be stored and be performed by calculation element in the storage device, and in some cases, step shown or described by can performing with the order be different from herein, or they are made into each integrated circuit modules respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (10)

1. target resource takies a processing method for situation, it is characterized in that, comprising:
Obtain the target resource that virtual network function VNF longitudinal elasticity stretches scaleup and/or elasticity contracting scaledown and take situation;
Taking situation according to described target resource indicates virtual architecture to manage the virtual machine for subsequent use that VIM creates or amendment is corresponding with virtual network function assembly VNFC for subsequent use, wherein, the described virtual machine for subsequent use business of carrying out for taking over the primary virtual machine corresponding with primary VNFC.
2. method according to claim 1, is characterized in that, after the situation that takies according to described target resource indicates the described virtual machine for subsequent use of described VIM establishment, also comprises:
After described virtual machine for subsequent use starts startup, trigger described primary virtual machine to described virtual machine synchrodata for subsequent use;
When determining that the process of synchrodata has entered stable state, trigger described primary virtual machine and described virtual machine for subsequent use is switched, and after switching operation terminates, delete described primary virtual machine.
3. method according to claim 2, is characterized in that, after described switching operation terminates, indicates described VIM to delete described primary virtual machine.
4. method according to claim 1, is characterized in that, after the situation that takies according to described target resource indicates the described virtual machine for subsequent use of described VIM amendment, also comprises:
After described virtual machine for subsequent use restarts, detect described primary virtual machine and whether enter stable state to the process of described virtual machine synchrodata for subsequent use;
When determining to enter described stable state, trigger described primary virtual machine and described virtual machine for subsequent use is switched;
After the occupation condition of the virtual machine for subsequent use after switching is modified, the virtual machine for subsequent use after switching described in restarting.
5. the method according to claim 2 or 4, it is characterized in that, when determining that the process of described synchrodata has entered described stable state, notice VNF triggers described primary virtual machine and described virtual machine for subsequent use is switched, and takes over the current business of carrying out of described primary virtual machine by described virtual machine for subsequent use.
6. method according to claim 1, is characterized in that, network function virtual composer NFVO or virtual network function management VNFM takies situation according to described target resource and indicates described VIM create or revise described virtual machine for subsequent use.
7. target resource takies a processing unit for situation, it is characterized in that, comprising:
Acquisition module, the target resource stretching scaleup and/or elasticity contracting scaledown for obtaining virtual network function VNF longitudinal elasticity takies situation;
Processing module, virtual architecture is indicated to manage the virtual machine for subsequent use that VIM creates or amendment is corresponding with virtual network function assembly VNFC for subsequent use for taking situation according to described target resource, wherein, the described virtual machine for subsequent use business of carrying out for taking over the primary virtual machine corresponding with primary VNFC.
8. device according to claim 7, is characterized in that, described device also comprises:
First trigger module, for start startup at described virtual machine for subsequent use after, triggers described primary virtual machine to described virtual machine synchrodata for subsequent use;
Second trigger module, for when determining that the process of synchrodata has entered stable state, triggers described primary virtual machine and described virtual machine for subsequent use is switched, and after switching operation terminates, deletes described primary virtual machine.
9. device according to claim 7, is characterized in that, described device also comprises:
Detection module, for after described virtual machine for subsequent use restarts, detects described primary virtual machine and whether enters stable state to the process of described virtual machine synchrodata for subsequent use;
3rd trigger module, for when determining to enter described stable state, triggers described primary virtual machine and described virtual machine for subsequent use is switched;
Restart module, for after modifying to the occupation condition of the virtual machine for subsequent use after switching, the virtual machine for subsequent use after switching described in restarting.
10. the device according to any one of claim 7 to 9, is characterized in that, described device is positioned at network function virtual composer NFVO or virtual network function management VNFM.
CN201410473174.XA 2014-09-16 2014-09-16 Method and device for processing occupied conditions of target resource Pending CN105490908A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201410473174.XA CN105490908A (en) 2014-09-16 2014-09-16 Method and device for processing occupied conditions of target resource
PCT/CN2015/070805 WO2015131671A1 (en) 2014-09-16 2015-01-15 Target resource occupancy handling method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410473174.XA CN105490908A (en) 2014-09-16 2014-09-16 Method and device for processing occupied conditions of target resource

Publications (1)

Publication Number Publication Date
CN105490908A true CN105490908A (en) 2016-04-13

Family

ID=54054524

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410473174.XA Pending CN105490908A (en) 2014-09-16 2014-09-16 Method and device for processing occupied conditions of target resource

Country Status (2)

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

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107153570A (en) * 2017-04-11 2017-09-12 华为技术有限公司 The number controlling method and device of a kind of virtual machine
WO2017181877A1 (en) * 2016-04-21 2017-10-26 华为技术有限公司 Method and device for allocating virtual resource
WO2018001049A1 (en) * 2016-06-27 2018-01-04 华为技术有限公司 Virtual network function deployment method, device and system adopting network edge computing
CN107566470A (en) * 2017-08-25 2018-01-09 郑州云海信息技术有限公司 The method and apparatus that virtual machine is managed in cloud data system
CN108023749A (en) * 2016-11-03 2018-05-11 华为技术有限公司 Manage the method, apparatus and system of network section
WO2018090677A1 (en) * 2016-11-21 2018-05-24 华为技术有限公司 Processing method, device and system for nf component abnormality

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017054197A1 (en) * 2015-09-30 2017-04-06 华为技术有限公司 Scaling out method, device and system
CN106685784A (en) * 2015-11-05 2017-05-17 中兴通讯股份有限公司 Virtualized network function VNF instance scaling method and VNF instance scaling device
CN106685683A (en) * 2015-11-11 2017-05-17 中兴通讯股份有限公司 Management indication transmitting and VNF automatic telescoping function management method and device
US10158583B2 (en) * 2016-03-17 2018-12-18 Huawei Technologies Co., Ltd. Virtual network function state scaling
CN107277898A (en) * 2016-04-08 2017-10-20 中兴通讯股份有限公司 Virtualize network energy-saving method and device
CN109120555B (en) * 2017-06-26 2022-10-14 中兴通讯股份有限公司 Resource allocation method and system
CN111898868A (en) * 2020-07-06 2020-11-06 上海泛微网络科技股份有限公司 Resource occupation display method and device
CN117009091B (en) * 2023-10-07 2023-12-19 浪潮(山东)计算机科技有限公司 Resource adjustment method, device, equipment and readable storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1763771A1 (en) * 2004-04-22 2007-03-21 Waratek Pty Limited Modified computer architecture with finalization of objects
CN102185774A (en) * 2011-05-10 2011-09-14 中兴通讯股份有限公司 Method, monitor and system for seamless migration of virtual machine
CN102662750A (en) * 2012-03-23 2012-09-12 上海交通大学 Virtual machine resource optimal control method and control system based on elastic virtual machine pool
CN103136030A (en) * 2011-11-24 2013-06-05 鸿富锦精密工业(深圳)有限公司 Virtual machine management system and method

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8612937B2 (en) * 2011-08-25 2013-12-17 International Business Corporation Synchronously debugging a software program using a plurality of virtual machines
CN102708027B (en) * 2012-05-11 2015-08-12 中兴通讯股份有限公司 A kind of method and system avoiding outage of communication device
CN103618627B (en) * 2013-11-27 2017-01-04 华为技术有限公司 A kind of manage the method for virtual machine, Apparatus and system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1763771A1 (en) * 2004-04-22 2007-03-21 Waratek Pty Limited Modified computer architecture with finalization of objects
CN102185774A (en) * 2011-05-10 2011-09-14 中兴通讯股份有限公司 Method, monitor and system for seamless migration of virtual machine
CN103136030A (en) * 2011-11-24 2013-06-05 鸿富锦精密工业(深圳)有限公司 Virtual machine management system and method
CN102662750A (en) * 2012-03-23 2012-09-12 上海交通大学 Virtual machine resource optimal control method and control system based on elastic virtual machine pool

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017181877A1 (en) * 2016-04-21 2017-10-26 华为技术有限公司 Method and device for allocating virtual resource
WO2018001049A1 (en) * 2016-06-27 2018-01-04 华为技术有限公司 Virtual network function deployment method, device and system adopting network edge computing
US11036536B2 (en) 2016-06-27 2021-06-15 Huawei Technologies Co., Ltd. Method, apparatus, and system for deploying virtualized network function using network edge computing
CN108023749A (en) * 2016-11-03 2018-05-11 华为技术有限公司 Manage the method, apparatus and system of network section
WO2018090677A1 (en) * 2016-11-21 2018-05-24 华为技术有限公司 Processing method, device and system for nf component abnormality
US11178000B2 (en) 2016-11-21 2021-11-16 Huawei Technologies Co., Ltd. Method and system for processing NF component exception, and device
CN107153570A (en) * 2017-04-11 2017-09-12 华为技术有限公司 The number controlling method and device of a kind of virtual machine
CN107153570B (en) * 2017-04-11 2020-08-25 华为技术有限公司 Method and device for controlling number of virtual machines
CN107566470A (en) * 2017-08-25 2018-01-09 郑州云海信息技术有限公司 The method and apparatus that virtual machine is managed in cloud data system
CN107566470B (en) * 2017-08-25 2021-01-15 苏州浪潮智能科技有限公司 Method and device for managing virtual machine in cloud data system

Also Published As

Publication number Publication date
WO2015131671A1 (en) 2015-09-11

Similar Documents

Publication Publication Date Title
CN105490908A (en) Method and device for processing occupied conditions of target resource
CN108605259B (en) Network switching method and related equipment
CN111461296A (en) Data processing method, electronic device and readable storage medium
CN104572178B (en) Electric energy meter embedded software remote differential upgrade method and upgrade-system
CN105843650A (en) Application program management method and device in intelligent terminal
CN102595537B (en) A kind of method of handover network access point, device and terminal
CN110650489B (en) Method and device for managing monitoring events
CN113940037B (en) Resource subscription method, device, computer equipment and storage medium
EP3591896A1 (en) Communication method and device
CN104717377B (en) Scene modes of mobile terminal switching method, device and mobile terminal
CN105634780A (en) Method and device for realizing VNF elastic scaling
CN103384263A (en) Timestamp management method for data synchronization and terminal therefor
CN104426939A (en) Information processing method and electronic equipment
CN106527162A (en) Linkage control method and device based on AllJoyn
CN102298497A (en) Method for inputting character on embedded equipment and system
CN112637819A (en) Service opening method and device in converged network
CN114866570A (en) Information processing method and device, electronic equipment and storage medium
CN108710304B (en) Client operation management method and client
CN110430255A (en) The processing method of service request, system and electronic equipment in distributed type assemblies
CN109788513A (en) Method of data synchronization, system and the controller of edge calculations application
CN115145690B (en) Cluster resource expansion method and device and container cluster management system
CN104267875A (en) Photo mode display method and device
CN113448607A (en) Method and device for firmware upgrading and intelligent household appliance
CN113342370A (en) Configuration updating method and device, electronic equipment and storage medium
WO2017181971A1 (en) Switching method, equipment and system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20160413

RJ01 Rejection of invention patent application after publication