A network service expansion exception processing method, device and storage medium
Through NFVO, the NS instance and VNF instance are determined in the NFV system, and the capacity expansion and capacity reduction interface is called to pass exception information, which solves the problem that VNFM cannot accurately delete the exception virtual machine during the capacity reduction operation, and realizes the correct capacity reduction in the exception handling process and business recovery.
Patent Information
- Application Number
- CN202110499272.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-05-08
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2041-05-08
AI Technical Summary
The existing VNFM mechanism cannot simultaneously realize intelligent deletion of virtual machines and accurately deletion of abnormal virtual machines, and cannot distinguish whether NFVO is in a normal operation process or an exception handling process when calling the ScaleVNF interface, resulting in limited efficiency and accuracy of capacity reduction operation.
Determine the NS instance to be operated through NFVO and find the target VNF instance, call the capacity expansion and capacity reduction interface to trigger the capacity reduction operation, and send exception information to VNFM, including virtual machine identification and task identification. After VNFM receives, it performs the capacity reduction task to delete the exception virtual machine , ensure that the virtual machine is correctly deleted during the exception handling process.
It realizes the ability to correctly delete exception virtual machines in the exception handling process, improves the accuracy and efficiency of capacity reduction operations, and ensures that the business returns to the pre-exception state.
Smart Images

Figure CN115314389B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to wireless communication technology, and in particular to a method, device and storage medium for handling network service expansion exceptions. Background Art
[0002] Traditional network equipment manufacturers customize equipment based on specific specifications and specific technical requirements. The equipment maintenance and update process is relatively complicated, and the operating cost of business promotion is high. In order to reduce the complexity and cost of network deployment and business promotion, the decoupling of software and hardware based on a general hardware platform can effectively reduce the cost of equipment upgrades and accelerate the deployment of new services. Network Function Virtualization (NFV) was proposed based on the above background.
[0003] Network Function Virtualization (NFV) implements the core cloud management functions through the Management and Orchestration (MANO) system and the network management system (including: Operations Support System (OSS) and Operation and Maintenance Center (OMC)).
[0004] Specifically, in actual applications, the capacity expansion and contraction of virtual resources can be achieved according to demand. However, when an abnormality occurs during the capacity expansion and contraction, the virtual resources cannot be accurately managed. Summary of the invention
[0005] In view of this, the main purpose of the present invention is to provide a method, device and storage medium for handling network service expansion exceptions.
[0006] To achieve the above object, the technical solution of the present invention is achieved as follows:
[0007] An embodiment of the present invention provides a method for handling network service expansion exceptions, which is applied to a network function virtualization orchestrator (NFVO). The method includes:
[0008] Determine a network service (NS) instance to be operated, and search for at least one target virtualized network function (VNF) instance involved in executing the NS expansion task by the NS instance;
[0009] For each of the target VNF instances in the at least one target VNF instance, triggering a scaling operation by calling a scaling interface;
[0010] The capacity reduction operation at least includes: sending the exception information of the corresponding target VNF instance to the virtualized network function manager (VNFM); the exception information is received by the VNFM and the capacity reduction task is performed based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF capacity expansion task involved in the corresponding target VNF instance and / or the VNF capacity expansion task identifier involved in the corresponding target VNF instance.
[0011] In the above scheme, the abnormal information includes: the virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance;
[0012] The sending the abnormal information of the corresponding target VNF instance to the VNFM includes:
[0013] Write the virtual machine identifier corresponding to the target VNF expansion task into the virtual machine VM table;
[0014] Sending the VM table to VNFM;
[0015] The VM table is one of the parameters carried by the expansion and contraction interface.
[0016] In the above scheme, the parameters carried by the expansion and contraction interface include: a task identifier, which represents the VNF expansion task identifier involved in the target VNF instance on which the corresponding rollback operation acts.
[0017] In the above scheme, the abnormal information includes: the VNF expansion task identifier involved in the corresponding target VNF instance;
[0018] The sending the abnormal information of the corresponding target VNF instance to the VNFM includes:
[0019] Writing the VNF capacity expansion task identifier involved in the target VNF instance into the parameters of the capacity expansion and contraction interface;
[0020] The parameters of the expansion and contraction interface are sent to the VNFM.
[0021] An embodiment of the present invention provides a method for handling network service expansion exceptions, which is applied to VNFM. The method includes:
[0022] Get the exception information of the target VNF instance;
[0023] Execute a capacity reduction task based on the abnormal information of the target VNF instance;
[0024] The abnormal information is the virtual machine identifier corresponding to the VNF capacity expansion task involved in the target VNF instance informed by NFVO to VNFM and / or the VNF capacity expansion task identifier involved in the target VNF instance.
[0025] In the above solution, the obtaining of abnormal information of the target VNF instance includes: receiving a VM table from the NFVO;
[0026] Accordingly, the performing of the scaling-down task based on the abnormal information of the target VNF instance includes:
[0027] Determine the virtual machine identifier corresponding to the target VNF expansion task according to the VM table;
[0028] Delete the virtual machine corresponding to the virtual machine identifier corresponding to the target VNF expansion task.
[0029] In the above scheme, the obtaining of abnormal information of the target VNF instance includes: reading the parameters of the expansion and contraction interface, and determining the VNF expansion task identifier involved in the target VNF instance;
[0030] Accordingly, the performing of the scaling-down task based on the abnormal information of the target VNF instance includes:
[0031] Determine a virtual machine corresponding to the VNF capacity expansion task according to the VNF capacity expansion task identifier;
[0032] Delete the virtual machine corresponding to the VNF expansion task.
[0033] The embodiment of the present invention provides a network service expansion exception processing device, which is applied to NFVO. The device includes: a first processing module and a second processing module; wherein:
[0034] The first processing module is used to determine the NS instance to be operated, and search for at least one target VNF instance involved in the NS instance performing the NS expansion task;
[0035] The second processing module is used to trigger a scaling operation for each of the target VNF instances in the at least one target VNF instance by calling a scaling interface;
[0036] The scaling-in operation at least includes: sending the exception information of the corresponding target VNF instance to VNFM; the VNFM receives the exception information and executes the scaling-in task based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance and / or the VNF expansion task identifier involved in the corresponding target VNF instance.
[0037] In the above scheme, the abnormal information includes: the virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance;
[0038] The second processing module is used to write the virtual machine identifier corresponding to the target VNF expansion task into a virtual machine VM table;
[0039] Sending the VM table to VNFM;
[0040] The VM table is one of the parameters carried by the expansion and contraction interface.
[0041] In the above scheme, the parameters carried by the expansion and contraction interface include: a task identifier, which represents the VNF expansion task identifier involved in the target VNF instance on which the corresponding rollback operation acts.
[0042] In the above scheme, the abnormal information includes: the VNF expansion task identifier involved in the corresponding target VNF instance;
[0043] The second processing module is used to write the VNF expansion task identifier involved in the target VNF instance into the parameters of the expansion and contraction interface;
[0044] The parameters of the expansion and contraction interface are sent to the VNFM.
[0045] The embodiment of the present invention provides a network service expansion exception processing device, which is applied to VNFM. The device includes: a third processing module and a fourth processing module; wherein:
[0046] The third processing module is used to obtain abnormal information of the target VNF instance;
[0047] The fourth processing module is used to perform a capacity reduction task based on the abnormal information of the target VNF instance;
[0048] The abnormal information is the virtual machine identifier corresponding to the VNF capacity expansion task involved in the target VNF instance informed by NFVO to VNFM and / or the VNF capacity expansion task identifier involved in the target VNF instance.
[0049] In the above solution, the obtaining of abnormal information of the target VNF instance includes: receiving a VM table from the NFVO;
[0050] Correspondingly, the fourth processing module is used to determine the virtual machine identifier corresponding to the target VNF expansion task according to the VM table;
[0051] Delete the virtual machine corresponding to the virtual machine identifier corresponding to the target VNF expansion task.
[0052] In the above scheme, the third processing module is used to read the parameters of the expansion and contraction interface to determine the VNF expansion task identifier involved in the target VNF instance;
[0053] Correspondingly, the fourth processing module is used to determine the virtual machine corresponding to the VNF capacity expansion task according to the VNF capacity expansion task identifier;
[0054] Delete the virtual machine corresponding to the VNF expansion task.
[0055] An embodiment of the present invention provides a network service expansion exception handling device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the network service expansion exception handling method on the NFVO side are implemented; or,
[0056] When the processor executes the program, the steps of the network service expansion exception handling method on the VNFM side are implemented.
[0057] The embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the network service expansion exception handling method on the NFVO side are implemented; or,
[0058] When the computer program is executed by the processor, the steps of the network service expansion exception handling method on the VNFM side are implemented.
[0059] The network service expansion exception processing method, device and storage medium provided by the embodiment of the present invention, NFVO determines the NS instance to be operated, searches for at least one target VNF instance involved in the NS expansion task performed by the NS instance; for each of the at least one target VNF instance, triggers the shrinking operation by calling the expansion and shrinking interface; the shrinking operation at least includes: sending the exception information of the corresponding target VNF instance to VNFM; the exception information is received by the VNFM and the shrinking task is performed based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance and / or the VNF expansion task identifier involved in the corresponding target VNF instance; accordingly, the exception information of the target VNF instance is obtained; the shrinking task is performed based on the exception information of the target VNF instance; wherein the exception information is the virtual machine identifier corresponding to the VNF expansion task involved in the target VNF instance and / or the VNF expansion task identifier involved in the target VNF instance informed by the NFVO to the VNFM. In this way, VNFM is guaranteed to correctly delete abnormal virtual machines during the exception handling process. BRIEF DESCRIPTION OF THE DRAWINGS
[0060] Figure 1 It is a structural diagram of a core network cloud platform system;
[0061] Figure 2 A schematic diagram of NS / VNF logical processing;
[0062] Figure 3 A schematic diagram of a NS life cycle task operation state transition;
[0063] Figure 4 A schematic diagram of a VNFM processing mechanism;
[0064] Figure 5 A flowchart of a method for handling network service expansion exceptions provided by an embodiment of the present invention;
[0065] Figure 6 A flowchart of another method for handling network service expansion exceptions provided by an embodiment of the present invention;
[0066] Figure 7 A flowchart of a first method for handling network service capacity expansion exceptions provided by an embodiment of the present invention;
[0067] Figure 8 A schematic diagram of a flow chart of a second method for handling network service expansion exceptions provided by an embodiment of the present invention;
[0068] Fig. 9A schematic diagram of the structure of a network service expansion exception handling device provided by an embodiment of the present invention;
[0069] Fig.10 A schematic diagram of the structure of another network service expansion exception handling device provided by an embodiment of the present invention;
[0070] Fig.11 A schematic diagram of the structure of another network service expansion exception handling device provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0071] Before further describing the present invention in detail with reference to the embodiments, the related art will be described first.
[0072] Figure 1 is a schematic diagram of a core cloud platform system architecture; Figure 1 As shown, NFV implements the core cloud management function by MANO system and network management system (OSS, OMC). MANO system was proposed by European Telecommunications Standards Institute (ETSI). MANO includes three major components: Network Function Virtualization Orchestrator (NFVO), Virtualized Network Function Manager (VNFM), and Virtualized Infrastructure Manager (VIM). Its main functions include life cycle management of network elements, creation of images required for network elements, management of templates and software required for network elements, allocation and management of network resources, etc. Among them,
[0073] NFVO: Responsible for unified resource scheduling, creating VNF automatic expansion and contraction policies, and providing VNF instantiation specification configuration parameters.
[0074] VNFM: Responsible for VNF lifecycle management, such as parsing and processing virtualized network function descriptors (VNFDs), initializing VNF instances, and scaling VNFs.
[0075] VIM: responsible for the scheduling and management of hardware resources and virtualization resources.
[0076] OMC: Responsible for the management of VNF fault, configuration, accounting, performance and security (FCAPS) related information.
[0077] After the introduction of software defined network (SDN), virtual resources are deployed in the form of network service (NS). Each NS instance contains one or more virtualized network function (VNF) instances, as well as virtual links (VL) and network connectivity resources required for communication and interaction between VNF instances.
[0078] After NFVO selects a NS instance and triggers the NS lifecycle operation, an NS job identifier (NSJob ID) will be generated on NFVO. During the operation, NFVO will take each VNF instance in the NS instance as a unit, call the interface between NFVO and VNFM (remembered as Or-Vnfm) for each VNF instance, and perform lifecycle operations on each VNF instance; at the same time, NFVO will call the interface between NFVO and VIM (remembered as Or-Vi) to create VL and network connectivity resources between VNF instances. Figure 2 The following is a schematic diagram of NS / VNF logical processing.
[0079] Figure 3 It is a schematic diagram of the state transition of NS life cycle task operation; Figure 3 As described above, if an error occurs during the instantiation / scaling / update / termination of an NS instance, the job status changes from the Processing state to the Failed_temp state. During this task phase, NFVO can choose to trigger a rollback of the operation task.
[0080] After the rollback task starts, the Job status changes from Failed_temp to Rolling_back.
[0081] If the rollback operation is successful, the Job status changes from the Rolling_back state to the Rolled_back state;
[0082] If the rollback operation fails, the Job status changes from the Rolling_back state to the Failed_temp state.
[0083] In the related art, the rollback operation processing mechanism of NS expansion (i.e., adding VM to VNF instance) is as follows:
[0084] 1) If NFVO does not obtain the Job ID returned by VNFM, after triggering the rollback operation, NFVO modifies the NS instance lifecycle management status;
[0085] 2) If NFVO has obtained the Job ID returned by VNFM, based on the Job ID, NFVO calls the NFVO-VNFM interface (GetJobStatus) to obtain the corresponding task status recorded on VNFM;
[0086] a) If the VNF task status is Completed, after the rollback operation is triggered: NFVO refreshes the task status record stored on NFVO based on the VNF task status record obtained. NFVO calls the ScaleVNF interface to scale down the VNF instance to the resource status before the operation.
[0087] b) If the VNF task status is Failed, manually delete the resources created before the VNF expansion failed, restore the VNF instance to the state before the expansion, and adjust the VNF instance status on NFVO and VNFM to Active. After the rollback operation is triggered: NFVO refreshes the task status record stored on NFVO based on the VNF task status record obtained, and modifies the NS instance lifecycle management status.
[0088] c) If the VNF task status is Rolled_back, after the rollback operation is triggered: NFVO refreshes the task status record stored on NFVO according to the obtained VNF task status record, and modifies the NS instance lifecycle management status.
[0089] d) If the VNF task status is Processing or Rolling_back, after the rollback operation is triggered: NFVO refreshes the task status record stored on NFVO based on the acquired VNF task status record, changes the NS instance lifecycle management task status to Processing, waits for the relevant VNF instance lifecycle management task status in the NS instance to enter the final state (Completed, Failed or Rolled_back), and then performs relevant operations according to the processing flow from a) to c).
[0090] The above ScaleVNF interface is described as follows:
[0091] 1) Interface access method: PUT / v3 / vnfs / {vnfInstanceID} / scale
[0092] 2) Application Programming Interface (API) parameters, as shown in Table 1 below:
[0093]
[0094]
[0095] Table 1
[0096] The above solution has the following problems:
[0097] Problem 1: The existing VNFM mechanism cannot simultaneously meet the requirements of “intelligently deleting virtual machines” and “accurately deleting virtual machines with abnormal creation”.
[0098] In the NS instance expansion process, when the VNF virtual resources (computing, storage, and network resources) have been created, but the VL and network connectivity resources have failed to be created, the NS instance task status will change from Processing to Failed_temp. Since the VNF virtual resources have been created, the VNF task status is Completed. If the operator triggers the rollback button on the NFVO interface at this time, NFVO will call the ScaleVNF interface to scale down the VNF instance and reduce the number of VMs in the VNF instance.
[0099] In the existing rollback mechanism, since the specific information of the virtual machines involved in the NS expansion operation task is not recorded on NFVO, the VMList parameter will not be sent when NFVO calls the ScaleVNF interface. The reduction operation task is completed autonomously by VNFM through a specific mechanism.
[0100] In the normal VNF / NS scaling down (reducing VM) operation process, the operator can select the VNF instance in the NFVO interface to trigger the scaling down operation. From the perspective of simplifying the complexity of the operation and maintenance personnel's work, when the scaling down operation is triggered, the operation and maintenance personnel do not need to manually select the virtual machine to be deleted. When NFVO calls the ScaleVNF interface again, it also does not send the VMList related parameters. The scaling down operation task is also completed autonomously by VNFM through a specific mechanism.
[0101] In the above two scenarios, when NFVO calls the ScaleVNF interface to trigger the scaling-in operation, it does not need to send the VMList parameter, and the scaling-in operation tasks are all completed by VNFM based on a specific processing mechanism.
[0102] Common VNFM processing mechanisms include:
[0103] Mechanism 1: Based on the service load rate (CPU occupancy rate) of the VMs in the VNF instance, VNFM selects the VM with the lowest service load rate and deletes it to achieve capacity reduction.
[0104] Mechanism 2: Based on the order in which VMs are created in the VNF instance, VNFM deletes VMs in order from the back to the front to achieve the task of scaling down the VNF instance.
[0105] Combination Figure 4 It can be found that the VNFM processing mechanism has the following problems:
[0106] Problem with Mechanism 1: There may be some successfully created virtual machines in the VNF instance, that is, the virtual resources and network configurations are all created, but the business load is 0 during a certain period of time. For VMs whose virtual resources have been created but whose network connectivity configurations have not been successfully created, their business load is also 0. The purpose of the rollback operation is to restore the usage of virtual resources to the situation before the expansion operation was triggered. Therefore, VNFM needs to ensure that the VMs that were not created in this abnormal operation are deleted in the reduction operation task. However, this method cannot guarantee that the VMs deleted by VNFM are necessarily the VMs that were not created in this abnormal task.
[0107] The problem with mechanism 2: The reverse order deletion mechanism can ensure that the deleted VM must be the VM involved in the abnormal operation task. However, in the normal operation process, VNFM cannot intelligently delete the VM with the lowest load rate based on the business load to ensure that the business is as unaffected as possible.
[0108] Problem 2: VNFM cannot distinguish whether the operation of NFVO calling the ScaleVNF interface is in the "normal operation process" or the "exception handling process";
[0109] Based on the parameters contained in the existing ScaleVNF interface, VNFM cannot distinguish whether the NFVO is in the exception handling process or the normal operation process when calling the ScaleVNF interface. Since the "normal operation process" and "exceptional handling process" require different VNFM autonomous processing mechanisms, VNFM needs to be able to identify which process the ScaleVNF interface call operation is in.
[0110] Based on this, the method provided by the embodiment of the present invention is that NFVO determines the NS instance to be operated, searches for at least one target VNF instance involved in the NS instance executing the NS expansion task; for each of the at least one target VNF instance, triggers the shrinking operation by calling the expansion and shrinking interface; the shrinking operation at least includes: sending the exception information of the corresponding target VNF instance to VNFM; the exception information is received by the VNFM and the shrinking task is executed based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance and / or the VNF expansion task identifier involved in the corresponding target VNF instance; accordingly, the exception information of the target VNF instance is obtained; the shrinking task is executed based on the exception information of the target VNF instance; wherein the exception information is the virtual machine identifier corresponding to the VNF expansion task involved in the target VNF instance and / or the VNF expansion task identifier involved in the target VNF instance informed by NFVO to VNFM.
[0111] The present invention will be further described in detail below in conjunction with the embodiments.
[0112] Figure 5 A flowchart of a method for handling network service capacity expansion exceptions provided by an embodiment of the present invention; Figure 5 As shown, the network service expansion exception handling method is applied to NFVO, and the method includes:
[0113] Step 501: determine the NS instance to be operated, and search for at least one target VNF instance involved in the NS capacity expansion task performed by the NS instance;
[0114] Step 502: For each of the target VNF instances in the at least one target VNF instance, trigger a scaling operation by calling a scaling interface;
[0115] The scaling-down operation at least includes: sending the exception information of the corresponding target VNF instance to the VNFM; the VNFM receives the exception information and performs the scaling-down task based on the exception information;
[0116] The exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF capacity expansion task involved in the corresponding target VNF instance and / or the VNF capacity expansion task identifier involved in the corresponding target VNF instance.
[0117] In one embodiment, the determining the NS instance to be operated includes: determining the NS instance to be operated based on a selection instruction.
[0118] Specifically, before triggering the rollback operation, the operation and maintenance personnel can manually eliminate the connection failure of the relevant modules to ensure that the components of the MANO system can communicate normally; then, the operator can make a selection through the human-computer interaction interface of NFVO, and NFVO generates a selection instruction based on the selection result to determine the corresponding NS instance to be operated.
[0119] An NS instance may include one or more VNF instances, as well as the virtual links (VL) and network connectivity resources required for communication and interaction between VNF instances.
[0120] In one embodiment, searching for at least one target VNF instance involved in the NS instance executing the NS capacity expansion task includes:
[0121] Based on the information in the first VNF task information record table, search for the VNF expansion tasks and corresponding virtual machine identifiers involved in the NS instance executing the NS expansion tasks.
[0122] The VNF expansion task involved in the NS expansion task executed by the NS instance is the target VNF instance.
[0123] Here, when the number of VNF instances included in the NS instance is one, it is only necessary to determine whether the unique VNF instance is involved in the NS expansion task, that is, whether the VNF instance adds a virtual machine when the NS expansion task is executed;
[0124] When the NS instance includes multiple VNF instances, it is necessary to determine whether each VNF instance involves the NS expansion task, that is, whether each VNF instance adds a virtual machine when the NS expansion task is executed; the VNF instance to which the virtual machine is added when the NS expansion task is executed is used as the target VNF instance.
[0125] Specifically, the NFVO stores a first VNF task information record table to record NS / VNF operation task information and realize comprehensive recording of task operation information. The first VNF task information record table is shown in Table 2 below;
[0126]
[0127] Table 2
[0128] In Table 2, the VNF Job ID is used to represent the unique identifier of the VNF task contained in the NS task; based on the VNFJob ID, the VNF expansion task involved in the NS expansion task executed by the NS instance is searched.
[0129] In one embodiment, the abnormal information includes: a virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance;
[0130] The sending the abnormal information of the corresponding target VNF instance to the VNFM includes:
[0131] Write the virtual machine identifier corresponding to the target VNF expansion task into the VM table (VMList);
[0132] The VM table is sent to the VNFM.
[0133] The VMList is one of the parameters carried by the capacity expansion and contraction interface (ScaleVNF interface).
[0134] In one embodiment, the parameters carried by the capacity expansion and contraction interface (ScaleVNF interface) include: a task identifier, wherein the task identifier represents the identifier of the VNF capacity expansion task involved in the target VNF instance on which the corresponding rollback operation acts.
[0135] Specifically, the abnormal information includes: a VNF expansion task identifier involved in the corresponding target VNF instance;
[0136] The sending the abnormal information of the corresponding target VNF instance to the VNFM includes:
[0137] Writing the VNF capacity expansion task identifier involved in the target VNF instance into the parameters of the capacity expansion and contraction interface;
[0138] The parameters of the expansion and contraction interface are sent to the VNFM.
[0139] Specifically, the expansion and contraction interface may carry the parameter: task identifier (RelatedJobID), NFVO may write the VNF expansion task identifier involved in the target VNF instance into the parameters of the expansion and contraction interface, and VNFM determines the identifier of the VNF expansion task (abnormal task) involved in the target VNF instance on which the corresponding rollback operation acts through the parameters of the expansion and contraction interface.
[0140] Table 3 is a parameter table of a scaling interface provided by an embodiment of the present invention; that is, in actual application, the ScaleVNF interface includes parameters: RelatedJobID; VNFM can determine whether the interface call is in the "normal operation process" or the "abnormal processing process" based on the RelatedJobID. If it is in the normal operation process, VNFM can intelligently delete the VM based on the business load of the VM in the VNF instance (determined based on VMList).
[0141]
[0142]
[0143] Table 3
[0144] Among them, the parameter RelatedJobID represents the identifier of the VNF expansion task (abnormal task) involved in the target VNF instance on which the rollback operation acts.
[0145] If the RelatedJobID parameter is filled in when NFVO calls this interface, it means that NFVO calls the ScaleVNF interface in the exception handling process. VNFM can delete the VM related to the task based on the task ID and complete the rollback operation task;
[0146] If the VMList parameter is not filled in and the RelatedJobID parameter is filled in when NFVO calls this interface, it means that NFVO calls the ScaleVNF interface in the exception handling process. VNFM can call the VIM northbound interface in indirect mode based on the abnormal task identifier, delete the VM related to the task, and complete the rollback operation task;
[0147] If the VMList parameter is not filled in and the RelatedJobID parameter is not filled in when NFVO calls this interface, it means that NFVO calls the ScaleVNF interface in the normal operation process. VNFM can call the VIM northbound interface in indirect mode according to the business load of each virtual machine in the VNF instance to intelligently delete the VM;
[0148] If the VMList parameter is already filled in when NFVO calls this interface, the RelatedJobID parameter does not need to be filled in; VNFM can call the VIM northbound interface in indirect mode based on the VM instance information in VMList to delete the related VM.
[0149] Through the parameters in the ScaleVNF interface and the method provided in the embodiment of the present invention, it can be ensured that VNFM can intelligently delete VMs in the normal operation process to achieve NS / VNF scaling; it can also be ensured that VNFM can correctly delete abnormal VMs in the exception handling process to achieve NS rollback.
[0150] Figure 6 A flowchart of another method for handling network service expansion exceptions provided by an embodiment of the present invention; Figure 6 As shown, the method is applied to VNFM; the method includes:
[0151] Step 601: Obtain exception information of the target VNF instance;
[0152] Step 602: Execute a capacity reduction task based on the abnormal information of the target VNF instance;
[0153] The abnormal information is the virtual machine identifier corresponding to the VNF capacity expansion task involved in the target VNF instance informed by NFVO to VNFM and / or the VNF capacity expansion task identifier involved in the target VNF instance.
[0154] In one embodiment, the obtaining of abnormal information of the target VNF instance includes: receiving a VM list (VMList) from the NFVO;
[0155] Accordingly, the performing of the scaling-down task based on the abnormal information of the target VNF instance includes:
[0156] Determine the virtual machine identifier corresponding to the target VNF expansion task according to the VM table;
[0157] Delete the virtual machine corresponding to the virtual machine identifier corresponding to the target VNF expansion task.
[0158] Here, the VMList is one of the parameters carried by the capacity expansion and contraction interface (ScaleVNF interface).
[0159] In one embodiment, the obtaining of abnormal information of the target VNF instance includes: reading parameters of the expansion and contraction interface to determine a VNF expansion task identifier involved in the target VNF instance;
[0160] Accordingly, the performing of the scaling-down task based on the abnormal information of the target VNF instance includes:
[0161] Determine a virtual machine corresponding to the VNF capacity expansion task according to the VNF capacity expansion task identifier;
[0162] Delete the virtual machine corresponding to the VNF expansion task.
[0163] Specifically, VNFM stores a second VNF task information record table to record NS / VNF operation task information and realize comprehensive recording of task operation information. The second VNF task information record table is shown in Table 4 below;
[0164]
[0165] Table 4
[0166] When applied, the VNF Job ID in Table 4 is queried according to the VNF capacity expansion task identifier to determine the corresponding VM UID, that is, the identifier of the virtual machine corresponding to the VNF capacity expansion task identifier.
[0167] Thus, the virtual machine is deleted according to the identifier of the virtual machine corresponding to the VNF expansion task identifier.
[0168] The embodiments of the present invention provide two methods for handling network service expansion exceptions.
[0169] Method 1: After the rollback operation is triggered, NFVO calls the ScaleVNF interface and fills in the VMList parameter based on the information in the first VNF task information record table. VNFM deletes the relevant VM based on the VMList parameter to complete the rollback operation.
[0170] Method 2: After the rollback operation is triggered, NFVO calls the ScaleVNF interface and fills in the RelatedJobID based on the information in the first VNF task information record table, without filling in the VMList parameter; VNFM deletes the related VM based on the information in the stored VNF task information record table to complete the rollback operation.
[0171] Figure 7 A flowchart of a method for handling network service capacity expansion exceptions provided in an embodiment of the present invention; Figure 7 As shown, the method includes:
[0172] Step 701: Select an NS instance and trigger the NS expansion (increase the number of VNF instance VMs) operation.
[0173] Step 702, the NS instance lifecycle management state is in Manual_scaling, and the NS instance lifecycle task management state is in Processing;
[0174] Here, NFVO stores the first VNF task information record table, and NFVO can fill in the VMList parameter when calling C6: ScaleVNF interface.
[0175] The first VNF task information record table (NFVO) is stored on NFVO, and the information written includes: recording NS / VNF instance operation task information, NS / VNF instance information and specific virtual machine information, etc. The above information is written in the NS expansion (increasing the number of VMs in VNF) operation process.
[0176] Step 703: VL and network connectivity resource creation fails, and the NS instance lifecycle operation task state changes to Failed_temp;
[0177] Specifically, when the NS expansion operation has completed the creation of virtual resources, but the creation of VL and network connectivity resources has failed, the NS instance life operation task status changes to Failed_temp, and a rollback operation can be triggered at this time.
[0178] Step 704: Select an NS instance in an abnormal state, trigger an NS rollback operation, and change the NS instance lifecycle task state to Rolling_back;
[0179] Before triggering the rollback operation, the operation and maintenance personnel need to manually eliminate the connection failures of related modules to ensure that the various components of the MANO system can communicate normally.
[0180] Then, the operator can select the NS instance on the NFVO interface to trigger the rollback operation; that is, NFVO provides a human-computer interaction interface, and the operator can select the NS instance through the human-computer interaction interface.
[0181] Step 705: The NFVO searches for the relevant VNF expansion task and the virtual machine identifier based on the first VNF task information record table;
[0182] Step 706: NFVO calls the ScaleVNF interface, writes the VMList parameter, and sends it to the VNFM.
[0183] Step 707: VNFM triggers a scaling-down operation of the VNF instance based on the VMList parameter.
[0184] Step 708: Determine whether all involved VNF instances have triggered the scaling-down task. If so, return to step 706; otherwise, proceed to step 709.
[0185] To further explain the above steps 705-708, NFVO uses VNF instances as units and calls the ScaleVNF interface to trigger the scaling-down operation on the corresponding VNF instances. The process is as follows:
[0186] Based on the information in the first VNF task information record table, NFVO searches for the VNF expansion task and the corresponding virtual machine ID involved in the NS expansion task. NFVO obtains the virtual machine ID to be deleted, writes it into the VMList parameter, and sends it to VNFM.
[0187] Correspondingly, VNFM triggers the scaling-down operation of the VNF instance based on the VMList parameters.
[0188] Repeat the above steps until all involved VNF instances have triggered the scaling-down task; VNFM completes the scaling-down operation tasks of each VNF instance involved in the NS rollback and deletes the corresponding virtual machine.
[0189] Step 709: The NS rollback operation is completed, and the virtual resource usage is restored to the state before the operation.
[0190] Figure 8 A flowchart of a second method for handling network service capacity expansion exceptions provided by an embodiment of the present invention; Figure 8 As shown, the method includes:
[0191] Step 801: Select an NS instance and trigger the NS expansion (increase the number of VNF instance VMs) operation;
[0192] Step 802: The NS instance lifecycle management state is in Manual_scaling, and the NS instance lifecycle task management state is in Processing;
[0193] Here, NFVO stores the first VNF task information record table, and VNFM stores the second VNF task information record table; when NFVO calls the ScaleVNF interface, it sends the RelatedJobID parameter;
[0194] The first VNF task information record table stored on the NFVO records NS / VNF instance operation task information, NS / VNF instance information, and specific virtual machine information, etc. The above information is written in the NS expansion (increasing the number of VMs in the VNF) operation process;
[0195] The second VNF task information record table stored on the VNFM records VNF instance task operation information and virtual machine information, etc.; the above information is written in the NS expansion (increasing the number of VMs in the VNF) operation process.
[0196] Step 803: VL and network connectivity resource creation fails, and the NS instance lifecycle operation task state changes to Failed_temp;
[0197] Specifically, when the NS expansion operation has completed the creation of virtual resources, but the creation of VL and network connectivity resources has failed, the NS instance life operation task status changes to Failed_temp, and a rollback operation can be triggered at this time.
[0198] Step 804: Select an NS instance in an abnormal state, trigger an NS rollback operation, and change the NS instance lifecycle task state to Rolling_back;
[0199] Before triggering the rollback operation, the operation and maintenance personnel need to manually eliminate the connection failures of related modules to ensure that the various components of the MANO system can communicate normally.
[0200] Then, the operator can select the NS instance on the NFVO interface to trigger the rollback operation; that is, NFVO can provide a human-computer interaction interface, and the operator can select the NS instance through the human-computer interaction interface.
[0201] Step 805: The NFVO searches for related VNF instances and VNF expansion tasks based on the first VNF task information record table.
[0202] Step 806: NFVO calls the ScaleVNF interface, writes the relatedJobID parameter, and sends it to VNFM.
[0203] Step 807: VNFM triggers the scaling down operation of the VNF instance based on the relatedJoblD parameter.
[0204] Step 808: Determine whether all involved VNF instances have triggered the scaling-down task. If not, return to step 806. If yes, proceed to step 809.
[0205] To further explain the above steps 805-808, NFVO uses VNF instances as units and calls the ScaleVNF interface to trigger the scaling-down operation for the corresponding VNF instances. The specific process is as follows:
[0206] Based on the information in the first VNF task information record table, NFVO searches for the VNF instance and VNF expansion task (VNF Job ID) involved in this NS expansion task; NFVO calls the ScaleVNF interface, writes the found VNF Job ID into the RelatedJobID parameter, and sends it to VNFM;
[0207] Correspondingly, VNFM triggers the scaling-down operation task of the VNF instance based on the RelatedJobID parameter and deletes the corresponding virtual machine in the task.
[0208] Repeat the above process until all involved VNF instances have triggered the scaling-down task. VNFM completes the scaling-down operation tasks of each VNF instance involved in the NS rollback and deletes the corresponding virtual machine.
[0209] Step 809: The NS rollback operation is completed, and the virtual resource usage is restored to the state before the operation.
[0210] For the above methods 1 and 2, it should be noted that in the normal operation process, when NFVO calls the ScaleVNF interface to trigger the scaling-down operation for the specified VNF instance, there is no need to send the RelatedJobID parameter or the VMList parameter. VNFM intelligently deletes the VM according to the business load of each VM in the VNF instance to ensure that the business is not affected.
[0211] Fig. 9 A schematic diagram of a network service expansion exception handling device provided by an embodiment of the present invention; Fig. 9 As shown, applied to NFVO, the device includes: a first processing module and a second processing module; wherein,
[0212] The first processing module is used to determine the NS instance to be operated, and search for at least one target VNF instance involved in the NS instance performing the NS expansion task;
[0213] The second processing module is used to trigger a scaling operation for each of the target VNF instances in the at least one target VNF instance by calling a scaling interface;
[0214] The scaling-in operation at least includes: sending the exception information of the corresponding target VNF instance to VNFM; the VNFM receives the exception information and executes the scaling-in task based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance and / or the VNF expansion task identifier involved in the corresponding target VNF instance.
[0215] Specifically, the abnormal information includes: a virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance;
[0216] The second processing module is used to write the virtual machine identifier corresponding to the target VNF expansion task into a virtual machine VM table;
[0217] Sending the VM table to VNFM;
[0218] The VM table is one of the parameters carried by the expansion and contraction interface.
[0219] Specifically, the parameters carried by the expansion and contraction interface include: a task identifier, which represents the identifier of the VNF expansion task involved in the target VNF instance on which the corresponding rollback operation acts.
[0220] The abnormal information includes: a VNF expansion task identifier involved in the corresponding target VNF instance;
[0221] The second processing module is used to write the VNF expansion task identifier involved in the target VNF instance into the parameters of the expansion and contraction interface;
[0222] The parameters of the expansion and contraction interface are sent to the VNFM.
[0223] It should be noted that: the network service expansion exception handling device provided in the above embodiment only uses the division of the above program modules as an example when implementing the corresponding network service expansion exception handling method on the first network device side. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the network device is divided into different program modules to complete all or part of the processing described above. In addition, the device provided in the above embodiment and the embodiment of the corresponding method belong to the same concept, and its specific implementation process is detailed in the method embodiment, which will not be repeated here.
[0224] Fig.10A schematic diagram of the structure of another network service expansion exception handling device provided by an embodiment of the present invention; Fig.10 As shown, applied to VNFM, the device includes: a third processing module and a fourth processing module; wherein,
[0225] The third processing module is used to obtain abnormal information of the target VNF instance;
[0226] The fourth processing module is used to perform a capacity reduction task based on the abnormal information of the target VNF instance;
[0227] The abnormal information is the virtual machine identifier corresponding to the VNF capacity expansion task involved in the target VNF instance informed by NFVO to VNFM and / or the VNF capacity expansion task identifier involved in the target VNF instance.
[0228] Specifically, the obtaining of abnormal information of the target VNF instance includes: receiving a VM table from the NFVO;
[0229] Correspondingly, the fourth processing module is used to determine the virtual machine identifier corresponding to the target VNF expansion task according to the VM table;
[0230] Delete the virtual machine corresponding to the virtual machine identifier corresponding to the target VNF expansion task.
[0231] Specifically, the third processing module is used to read the parameters of the expansion and contraction interface to determine the VNF expansion task identifier involved in the target VNF instance;
[0232] Correspondingly, the fourth processing module is used to determine the virtual machine corresponding to the VNF capacity expansion task according to the VNF capacity expansion task identifier;
[0233] Delete the virtual machine corresponding to the VNF expansion task.
[0234] It should be noted that: the network service expansion exception handling device provided in the above embodiment only uses the division of the above program modules as an example when implementing the corresponding network service expansion exception handling method on the second network device side. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the network device is divided into different program modules to complete all or part of the processing described above. In addition, the device provided in the above embodiment and the embodiment of the corresponding method belong to the same concept, and its specific implementation process is detailed in the method embodiment, which will not be repeated here.
[0235] Fig.11 A schematic diagram of the structure of another network service expansion exception handling device provided by an embodiment of the present invention; Fig.11As shown, the device 110 includes: a processor 1101 and a memory 1102 for storing a computer program that can be run on the processor; wherein,
[0236] When the device is applied to NFVO, the processor 1101 is used to run the computer program to perform the following: determine the NS instance to be operated, and search for at least one target VNF instance involved in the NS instance executing the NS expansion task; for each of the at least one target VNF instance, trigger the shrinking operation by calling the expansion and shrinking interface; the shrinking operation at least includes: sending the exception information of the corresponding target VNF instance to VNFM; the VNFM receives the exception information and executes the shrinking task based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance and / or the VNF expansion task identifier involved in the corresponding target VNF instance. Specifically, the NFVO can execute as follows: Figure 5 The method shown, and Figure 5 The method embodiments shown belong to the same concept, and their specific implementation processes are detailed in the method embodiments, which will not be repeated here.
[0237] When the device is applied to VNFM, the processor 1101 is used to execute the following when running the computer program: obtaining the abnormal information of the target VNF instance; executing the capacity reduction task based on the abnormal information of the target VNF instance; wherein the abnormal information is the virtual machine identifier corresponding to the VNF capacity expansion task involved in the target VNF instance informed by NFVO to VNFM and / or the VNF capacity expansion task identifier involved in the target VNF instance. Specifically, the VNFM can execute the following: Figure 6 The method shown, and Figure 6 The method embodiments shown belong to the same concept, and their specific implementation processes are detailed in the method embodiments, which will not be repeated here.
[0238] In actual application, the device 110 may also include: at least one network interface 1103. The various components in the network service expansion exception handling device 110 are coupled together through a bus system 1104. It can be understood that the bus system 1104 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.11 In the figure, various buses are marked as bus system 1104. There may be at least one processor 1101. The network interface 1103 is used for wired or wireless communication between the network service expansion exception handling device 110 and other devices.
[0239] The memory 1102 in the embodiment of the present invention is used to store various types of data to support the operation of the network service expansion exception handling device 110.
[0240] The method disclosed in the above embodiment of the present invention can be applied to the processor 1101, or implemented by the processor 1101. The processor 1101 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 1101 or the instruction in the form of software. The above processor 1101 may be a general processor, a digital signal processor (DSP, DiGital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 1101 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present invention, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 1102. The processor 1101 reads the information in the memory 1102 and completes the steps of the above method in combination with its hardware.
[0241] In an exemplary embodiment, the network service expansion exception handling device 110 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to execute the aforementioned method.
[0242] An embodiment of the present invention also provides a computer-readable storage medium having a computer program stored thereon; when the computer-readable storage medium is applied to NFVO, when the computer program is executed by the processor, the following is performed: determining the NS instance to be operated, searching for at least one target VNF instance involved in the NS capacity expansion task performed by the NS instance; for each of the at least one target VNF instance, triggering a capacity expansion and contraction operation by calling an expansion and contraction interface; the capacity reduction operation at least includes: sending the exception information of the corresponding target VNF instance to the VNFM; the exception information is received by the VNFM and the capacity reduction task is performed based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF capacity expansion task involved in the corresponding target VNF instance and / or the VNF capacity expansion task identifier involved in the corresponding target VNF instance. Specifically, the computer-readable storage medium can be executed as follows: Figure 5 The method shown, and Figure 5 The network service expansion exception handling method embodiments shown belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.
[0243] When the computer-readable storage medium is applied to the second network device, the computer program is executed by the processor to: obtain the abnormal information of the target VNF instance; execute the reduction task based on the abnormal information of the target VNF instance; wherein the abnormal information is the virtual machine identifier corresponding to the VNF expansion task involved in the target VNF instance informed by the NFVO to the VNFM and / or the VNF expansion task identifier involved in the target VNF instance. Specifically, the computer-readable storage medium can execute the following Figure 6 The method shown, and Figure 6 The network service expansion exception handling method embodiments shown belong to the same concept, and the specific implementation process is detailed in the method embodiments, which will not be repeated here.
[0244] In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.
[0245] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0246] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.
[0247] A person skilled in the art can understand that: all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), disks or optical disks, etc. Various media that can store program codes.
[0248] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.
[0249] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0250] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.
[0251] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
Claims
1. A method for handling network service expansion exceptions, characterized in that: Applied to a network function virtualization orchestrator NFVO, the method comprises: Determine a network service NS instance to be operated, and search for at least one target virtualized network function VNF instance involved in executing the NS capacity expansion task by the NS instance; For each of the target VNF instances in the at least one target VNF instance, triggering a scaling operation by calling a scaling interface; The capacity reduction operation at least includes: sending the exception information of the corresponding target VNF instance to the virtualized network function manager VNFM; the exception information is received by the VNFM and the capacity reduction task is performed based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF capacity expansion task involved in the corresponding target VNF instance and / or the VNF capacity expansion task identifier involved in the corresponding target VNF instance; The searching for at least one target VNF instance involved in the NS instance executing the NS capacity expansion task includes: Based on the information in the first VNF task information recording table, searching for the VNF capacity expansion task and the corresponding virtual machine identifier involved in the NS instance executing the NS capacity expansion task; the first VNF task information recording table is used to record NS or VNF operation task information; The VNF expansion task involved in the NS expansion task executed by the NS instance is determined as the target VNF instance.
2. The method according to claim 1, characterized in that The abnormal information includes: a virtual machine identifier corresponding to the VNF expansion task involved in the corresponding target VNF instance; The sending the abnormal information of the corresponding target VNF instance to the VNFM includes: Write the virtual machine ID corresponding to the target VNF expansion task into the virtual machine VM table; Sending the VM table to VNFM; The VM table is one of the parameters carried by the expansion and contraction interface.
3. The method according to claim 1, characterized in that: The parameters carried by the expansion and contraction interface include: a task identifier, which represents the VNF expansion task identifier involved in the target VNF instance on which the corresponding rollback operation acts.
4. The method according to claim 3, characterized in that The abnormal information includes: a VNF expansion task identifier involved in the corresponding target VNF instance; The sending the abnormal information of the corresponding target VNF instance to the VNFM includes: Writing the VNF capacity expansion task identifier involved in the target VNF instance into the parameters of the capacity expansion and contraction interface; The parameters of the expansion and contraction interface are sent to the VNFM.
5. A method for handling network service expansion exceptions, characterized in that: Applied to VNFM, the method comprises: Get the exception information of the target VNF instance; Execute a capacity reduction task based on the abnormal information of the target VNF instance; Among them, the abnormal information is the virtual machine identifier corresponding to the VNF expansion task involved in the target VNF instance informed by NFVO to VNFM and / or the VNF expansion task identifier involved in the target VNF instance; the target VNF instance is the VNF expansion task involved in the NS expansion task performed by the NS instance, and the VNF expansion task involved in the NS expansion task performed by the NS instance and the corresponding virtual machine identifier are obtained by the NFVO based on the information in the first VNF task information recording table; the first VNF task information recording table is used to record NS or VNF operation task information.
6. The method according to claim 5, characterized in that The obtaining of abnormal information of the target VNF instance includes: receiving a VM table from the NFVO; Accordingly, the performing of the scaling-down task based on the abnormal information of the target VNF instance includes: Determine the virtual machine identifier corresponding to the target VNF expansion task according to the VM table; Delete the virtual machine corresponding to the virtual machine ID corresponding to the target VNF expansion task.
7. The method according to claim 5, characterized in that The obtaining of abnormal information of the target VNF instance includes: reading parameters of the expansion and contraction interface, and determining a VNF expansion task identifier involved in the target VNF instance; Accordingly, the performing of the scaling-down task based on the abnormal information of the target VNF instance includes: Determine a virtual machine corresponding to the VNF capacity expansion task according to the VNF capacity expansion task identifier; Delete the virtual machine corresponding to the VNF expansion task.
8. A network service expansion exception handling device, characterized in that: Applied to NFVO, the device comprises: a first processing module and a second processing module; wherein, The first processing module is used to determine the NS instance to be operated, and search for at least one target VNF instance involved in the NS instance performing the NS expansion task; The second processing module is used to trigger a scaling operation for each of the target VNF instances in the at least one target VNF instance by calling a scaling interface; The scaling-in operation at least includes: sending the exception information of the corresponding target VNF instance to the VNFM; the VNFM receives the exception information and executes the scaling-in task based on the exception information; wherein the exception information is used to inform the VNFM of the virtual machine identifier corresponding to the VNF capacity expansion task involved in the corresponding target VNF instance and / or the VNF capacity expansion task identifier involved in the corresponding target VNF instance; The first processing module is specifically used to search for the VNF expansion task and the corresponding virtual machine identifier involved in the NS instance executing the NS expansion task based on the information in the first VNF task information recording table; the first VNF task information recording table is used to record NS or VNF operation task information; and the VNF expansion task involved in the NS instance executing the NS expansion task is determined as the target VNF instance.
9. A network service expansion exception handling device, characterized in that: Applied to VNFM, the device comprises: a third processing module and a fourth processing module; wherein, The third processing module is used to obtain abnormal information of the target VNF instance; The fourth processing module is used to perform a capacity reduction task based on the abnormal information of the target VNF instance; Among them, the abnormal information is the virtual machine identifier corresponding to the VNF expansion task involved in the target VNF instance informed by NFVO to VNFM and / or the VNF expansion task identifier involved in the target VNF instance; the target VNF instance is the VNF expansion task involved in the NS expansion task performed by the NS instance, and the VNF expansion task involved in the NS expansion task performed by the NS instance and the corresponding virtual machine identifier are obtained by the NFVO based on the information in the first VNF task information recording table; the first VNF task information recording table is used to record NS or VNF operation task information.
10. A network service expansion exception handling device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the method according to any one of claims 1 to 4 are implemented; or, When the processor executes the program, the steps of the method according to any one of claims 5 to 7 are implemented.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 4 are implemented; or, when the computer program is executed by a processor, the steps of the method described in any one of claims 5 to 7 are implemented.
Citation Information
Patent Citations
Method and system for dynamic expansion of logical volume based on logical volume manager (LVM)
CN106168885A
VNF capacity expansion and shrinkage method, device and equipment
CN110213064A
Method and device for processing resources in VNFM and computer storage medium
CN110868309A
Instance request generation method, interface virtual machine configuration method, NFVO and VIM
CN112748982A
Apparatus and method for managing and orchestrating network function virtualization
KR1020180040991A
