NFV resource orchestration method, device, system and storage medium

Abstract

The embodiment of the present application provides a NFV resource orchestration method, device, system and storage medium. In the embodiment of the present application, the resources of the virtual components required by the NFV network element are orchestrated through the API provided by the virtual component to the outside, and in the process of calling the API, after the API call is speed-limited, the orchestration operation for the NFV network element can be initiated on the virtual component through the API, which can ensure the availability and reliability of the virtual component; further, when the API call is speed-limited, the local speed-limiting threshold can be dynamically configured for the API for some NFV network elements, so as to speed-limit the API call in the NFV network element dimension, which can reduce the mutual influence between different NFV network elements when the API call is speed-limited to a certain extent, and at the same time, it can ensure that the call to the API does not exceed its rate limit, which is conducive to ensuring the stability of the NFV orchestration system and improving the service quality and user experience.

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and in particular to a NFV resource orchestration method, device, system and storage medium. Background Art

[0002] Network Function Virtualization (NFV) is a network service virtualization technology. Based on NFV technology, a NFV system can be implemented. The NFV system can build the required NFV network elements for front-end users based on existing virtual components. Among them, the front-end user refers to the demander of the NFV network element.

[0003] Specifically, when the front-end user needs to create a NFV network element or needs to change the resource configuration of an existing NFV network element, the front-end user can submit the resource deployment requirements of the NFV network element to the NFV system through the Application Programming Interface (API) provided by the NFV system. Based on the resource deployment requirements submitted by the front-end user, the NFV system orchestrates the corresponding virtual components through the API provided by the virtual components to build an NFV network element that meets the needs of the front-end user.

[0004] In order to ensure the reliability and availability of virtual components, the NFV system will limit the resource deployment requirements initiated by front-end users. That is, for any virtual component, when the number of resource deployment requirements initiated for the virtual component exceeds the configured threshold within a certain period of time, the NFV system will reject any resource deployment requirements initiated by any front-end user for the virtual component for a period of time, thereby reducing the NFV service quality and user experience. Summary of the invention

[0005] Multiple aspects of the present application provide a NFV resource orchestration method, device, system and storage medium to improve NFV service quality and user experience.

[0006] An embodiment of the present application provides a NFV resource orchestration system, including: a NFV orchestration device and a NFV resource pool, the NFV resource pool including at least one virtual component, and the at least one virtual component is deployed on at least one physical machine; the NFV orchestration device is used to receive a resource deployment requirement for a target NFV network element, and determine a target application program interface API required for orchestrating the target virtual component according to the resource deployment requirement; if there is a pre-configured local speed limit threshold of the target API for the target NFV network element, and it is determined according to the local speed limit threshold that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

[0007] An embodiment of the present application also provides an NFV resource orchestration method, comprising: receiving a resource deployment requirement for a target NFV network element, and determining a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirement; if there is a pre-configured local speed limit threshold for the target API for the target NFV network element, and it is determined according to the local speed limit threshold that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

[0008] An embodiment of the present application also provides a NFV resource orchestration method, including: receiving resource deployment requirements for a target NFV network element, determining a target application program interface API required for orchestrating a target virtual component based on the resource deployment requirements; after rate limiting the current call to the target API, initiating a resource orchestration operation for the target NFV network element on the target virtual component through the target API.

[0009] An embodiment of the present application also provides a NFV resource orchestration device, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program, so as to: receive a resource deployment requirement for a target NFV network element, and determine a target API required for orchestrating a target virtual component according to the resource deployment requirement; if there is a pre-configured local speed limit threshold for the target API for the target NFV network element, and it is determined according to the local speed limit threshold that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

[0010] An embodiment of the present application also provides a NFV resource orchestration device, including: a memory and a processor; the memory is used to store a computer program; the processor is coupled to the memory and is used to execute the computer program, so as to: receive a resource deployment requirement for a target NFV network element, and determine a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirement; after rate limiting the current call of the target API, initiate a resource orchestration operation for the target NFV network element to the target virtual component through the target API.

[0011] The embodiment of the present application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor implements the steps in the NFV resource orchestration method provided in the embodiment of the present application.

[0012] An embodiment of the present application also provides a computer program product, including a computer program / instruction. When the computer program / instruction is executed by a processor, the processor implements the steps in the NFV resource orchestration method provided in the embodiment of the present application.

[0013] In an embodiment of the present application, resources of virtual components required by NFV network elements can be orchestrated through the API provided by the virtual components. During the API calling process, and after the API call is rate-limited, the API is used to initiate an orchestration operation on the NFV network element, thereby ensuring the availability and reliability of the virtual components.

[0014] Further, in the embodiment of the present application, when the API call is speed-limited, a local speed-limiting threshold can be dynamically pre-configured for the API for some NFV network elements, so that the API call is speed-limited in the NFV network element dimension; in view of this, when an API call is initiated for a certain NFV network element, it can be determined whether there is a pre-configured local speed-limiting threshold for the API for the NFV network element, and if so, it is determined whether the current call of the API needs to be speed-limited according to the local speed-limiting threshold; if speed-limiting is required, the current call of the API is speed-limited and then the resource orchestration operation of the virtual component is performed through the API. Among them, speed-limiting the API call from the NFV network element dimension can reduce the mutual influence between different NFV network elements when the API call is speed-limited to a certain extent, and at the same time can ensure that the call to the API does not exceed its rate limit, which is conducive to ensuring the stability of the NFV orchestration system and improving service quality and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0016] Figure 1a A schematic diagram of the structure of an NFV resource orchestration system provided for an exemplary embodiment of the present application;

[0017] Figure 1b A schematic diagram of limiting the speed of a southbound API provided for an exemplary embodiment of the present application;

[0018] Figure 2a A flowchart of a NFV resource orchestration method provided for an exemplary embodiment of the present application;

[0019] Figure 2b A flowchart of another NFV resource orchestration method provided for an exemplary embodiment of the present application;

[0020] Figure 3A schematic diagram of the structure of an NFV resource orchestration device provided for an exemplary embodiment of the present application;

[0021] Figure 4 A schematic diagram of the structure of an NFV resource orchestration device provided in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0023] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0024] Figure 1a The following is a schematic diagram of the structure of a NFV resource orchestration system provided by an exemplary embodiment of the present application. Figure 1a As shown, the system 100 at least includes: a NFV orchestration device 101 and a NFV resource pool 102. The NFV resource pool 102 includes at least one virtual component 104, and these virtual components 104 are deployed on at least one physical machine 105. The NFV orchestration device 101 can be a physical device, such as a desktop computer, a notebook, a tablet computer, a traditional server, a server array, etc., or a virtual device, such as a cloud server, a virtual machine, a container, etc.

[0025] Among them, the virtual component 104 is the result of software-based network functions, which is a virtual network function unit that can realize a certain network function, and is deployed on the physical machine 105 in the form of a software module. In addition, the physical resources provided by the physical machine 105 can be virtualized to obtain virtual resources, so that the virtual component 104 can be deployed on these virtual resources to achieve the purpose of sharing physical resources. The virtual component 104 can be deployed in the cloud, or it can be deployed or moved to any location in the network as needed. The following is an example of the virtual component 104:

[0026] For example, the virtual component 104 may include but is not limited to: a Virtual Private Cloud (VPC) component, a Cloud Enterprise Network (Cloud Enterprise Network) component, an Elastic Internet Protocol (EIP) component, a virtual machine component, and a load balancing component. Among them, the VPC component is a functional component at the network level, which can establish a logically isolated virtual network space for users on the public cloud to ensure the resource security of users on the public cloud. The Cloud Enterprise Network component is also a functional component at the network level, which can build a private network communication channel between VPCs in different regions and between VPCs and local data centers for users, improve the rapid convergence of the network and the quality and security of cross-network communication through automatic routing distribution and learning, realize the intercommunication of resources across the entire network, and provide users with an Internet environment with enterprise-level scale and communication capabilities. The EIP component is a functional component that can provide users with independent public IP resources, including public IP addresses and public network export bandwidth services. The virtual machine component is a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment, which can provide users with an independent operating environment. The load balancing component is a functional component that can evenly distribute requests sent from the outside to any resource device in a resource device set. The resource device can be a server, GPU, or virtual machine, etc.

[0027] In this embodiment, the virtual component 104 provides an API to the NFV orchestration device 101. For the sake of distinction, the API provided by the virtual component 104 to the NFV orchestration device 101 is recorded as a southbound API, such as Figure 1aAs shown in ; NFV orchestration device 101 can perform resource orchestration on virtual component 104 through the southbound API provided by virtual component 104, thereby providing NFV resource orchestration services to the outside. Among them, the resource orchestration of virtual component 104 by NFV orchestration device 101 refers to the process of performing at least one orchestration operation such as deployment, addition, deletion, modification, query and configuration on virtual component 104 according to NFV resource deployment requirements, so that the virtual component 104 can cooperate with other virtual components 104 or other network resources to realize a certain service. In an optional embodiment, for the same virtual component 104, when the virtual component 104 supports multiple orchestration operations, the virtual component 104 can provide different APIs to NFV orchestration device 101, and each orchestration operation corresponds to one API. In this way, NFV orchestration device 101 can call the corresponding API to perform orchestration operations on virtual component 104 when performing different orchestration operations on virtual component 104. Of course, the same virtual component 104 may also provide a unified API to the outside world, and the NFV orchestration device 101 may perform different orchestration operations on the virtual component 104 through the unified API. Optionally, various orchestration operations may be distinguished by different interface parameters.

[0028] Further, if Figure 1a As shown, the system 100 also includes a front-end user 103, which is a demander of NFV resource orchestration services. Among them, the NFV orchestration device 101 provides NFV resource orchestration services for the front-end user 103, and by performing resource orchestration on the virtual component 104, a NFV network element that meets its service needs can be constructed for the front-end user 103. For example, if the front-end user 103 needs to deploy a live video service in a certain area, the NFV resource orchestration service can be requested from the NFV orchestration device 101, so that the NFV orchestration device 101 can create a NFV network element that can provide live video service for it by orchestrating virtual machine components, VPC components, etc. For another example, if the front-end user 103 needs to deploy a game acceleration service in a certain area, the NFV resource orchestration service can be requested from the NFV orchestration device 101, so that the NFV orchestration device 101 can create a NFV network element that can provide game acceleration service for it by orchestrating virtual machine components, VPC components, load balancing components, etc. It should be noted that, in addition to requesting NFV orchestration device 101 to create a new NFV network element for it, front-end user 103 may also change the resource configuration of an existing NFV network element in actual applications. In this case, it can also request NFV resource orchestration service from NFV orchestration device 101 so that NFV orchestration device 101 can achieve the purpose of changing the resource configuration of the existing NFV network element by re-orchestration of resources.

[0029] In this embodiment, the NFV orchestration device 101 provides an API to the front-end user 103. For the sake of distinction, the API provided by the NFV orchestration device 101 to the front-end user 103 can be recorded as a northbound API, such as Figure 1a As shown in ; when the front-end user 103 needs the NFV orchestration device 101 to provide NFV resource orchestration services for a certain NFV network element, the resource deployment requirements of the NFV network element can be submitted to the NFV orchestration device 101 through the northbound API. For the convenience of description and distinction, the NFV network element here is recorded as the target NFV network element. The resource deployment requirements include some information that can point to which virtual components 104 the target NFV network element needs and information related to the configuration of these virtual components 104, including but not limited to: the functional description of the target NFV network element, service area, network performance requirements and service quality parameters. Based on the resource deployment requirements of the target NFV network element, the NFV orchestration device 101 can determine which virtual component or components 104 need to be orchestrated for the target NFV network element. For ease of description and distinction, the virtual component that needs to be orchestrated for the target NFV network element is recorded as the target virtual component, for example, it can be a VPC component, a virtual machine component or a load balancing component, and the target virtual component can be one or more; similarly, for each target virtual component, the orchestration operation that needs to be performed on the target virtual component is recorded as the target orchestration operation, for example, it can be addition, deletion or modification, and the API required to perform the target orchestration operation on the target virtual component is recorded as the target API. Figure 1a The call of the target API by the NFV orchestration device 101 for the target NFV network element is indicated by a dotted line. The target API belongs to the southbound API mentioned above. It should be noted that if the target virtual component provides different southbound APIs for different orchestration operations, the target API is the southbound API corresponding to the target orchestration operation (such as adding, deleting or modifying); if the target virtual component provides a unified southbound API to the outside, the target API is the unified southbound API, and the interface parameters of the target API may indicate that the target orchestration operation needs to be performed on the target virtual component, rather than other orchestration operations. The following examples are provided:

[0030] For example, the NFV orchestration device 101 determines that a virtual machine component needs to be added to the target NFV network element according to the resource deployment requirements of the front-end user 103 for the target NFV network element. The virtual machine component has three southbound APIs, namely, adding, deleting, and modifying the corresponding southbound API interfaces. The NFV orchestration device 101 can call the southbound API interface corresponding to the adding operation to perform the operation of adding the virtual machine component for the target NFV network element. For another example, the NFV orchestration device 101 determines that a VPC component needs to be deleted for the target NFV network element according to the resource deployment requirements of the front-end user 103 for the target NFV network element. The VPC component has only three southbound APIs, namely, adding, deleting, and modifying the corresponding southbound API interfaces. The NFV orchestration device 101 can call the southbound API interface corresponding to the deleting operation to perform the operation of deleting the VPC component for the target NFV network element.

[0031] After determining the target API required for orchestration of the target virtual component, the NFV orchestration device 101 can initiate a resource orchestration operation on the virtual component 104 by calling the target API to build a target NFV network element that meets the needs of the front-end user 103. In this embodiment, in order to ensure the reliability and availability of the virtual component 104, the rate limit can be performed on the southbound API provided to the outside by any virtual component 104, that is, before initiating a resource orchestration operation on the target NFV network element to the target virtual component through the target API, the current call of the target API can be rate-limited, and then the resource orchestration operation on the target NFV network element can be initiated to the target virtual component through the target API.

[0032] Furthermore, in this embodiment, a global speed limit threshold can be configured for the southbound API. Based on the global speed limit threshold, the speed of the southbound API call can be limited from the NFV orchestration device 101 dimension. That is, when the number of calls to the southbound API by the NFV orchestration device 101 within a period of time (that is, the total number of calls to the southbound API initiated for each NFV network element) exceeds the global speed limit threshold, the NFV orchestration device 101 will not be able to initiate a call operation to the corresponding virtual component 104 through the southbound API within the next period of time. During this period, any front-end user 103 will not be able to use the virtual component 104, which will reduce the NFV service quality and user experience. In view of this, in this embodiment, further, for any southbound API provided externally by the virtual component 104, not only a global speed limit threshold is configured for the southbound API, but also a local speed limit threshold is allowed to be dynamically configured for the southbound API for some NFV network elements, wherein the local speed limit threshold is less than the global speed limit threshold; using the local speed limit threshold, the speed of the southbound API call can be individually limited for these NFV network elements from the NFV network element dimension, which can reduce the mutual influence between different NFV network elements when the southbound API call speed limit is limited to a certain extent, and at the same time, it can ensure that the call to the southbound API does not exceed its rate limit, which is conducive to ensuring the stability of the NFV orchestration system and improving the service quality and user experience. The NFV network elements configured with the local speed limit threshold here can be selected parts of the NFV network elements, and can be changed dynamically. For the selection method of these NFV network elements, please refer to the description of the subsequent implementation, which will not be described in detail here.

[0033] Based on the above, before calling the target API to initiate resource orchestration operation on the target virtual component 104, it also includes an operation of determining whether it is necessary to limit the speed of the current call of the target API. Figure 1bAs shown, first, it is determined whether there is a local speed limit threshold configured for the target NFV network element by the pre-configured target API; if so, it can be determined whether it is necessary to limit the speed of the current call of the target API according to the local speed limit threshold. For example, it can be determined whether the number of calls initiated to the target API for the target NFV network element has reached the local speed limit threshold; if so, it is determined that the current call of the target API needs to be speed limited. In an optional embodiment, the local speed limit threshold is defined as the maximum number of calls initiated by the NFV orchestration device 101 to the target API for the target NFV network element within a unit time, recorded as C1, then when the current call to the target API arrives, the number of calls initiated to the target API for the target NFV network element within the current unit time can be accumulated, recorded as C2, if C1≥C2, it is considered that it is not necessary to limit the speed of the current call of the target API for the target NFV network element, if C1<C2, it is considered that it is necessary to limit the speed of the current call of the target API for the target NFV network element. If it is determined according to the local speed limit threshold that the current call of the target API to the target NFV network element needs to be speed-limited, the current call of the target API is speed-limited. For example, the current call of the target API can be delayed for a certain period of time, such as 5ms, 10ms, etc., and the target API is called again after the delay. Or, Figure 1b As shown, when it is determined that the current call to the target API needs to be speed-limited, it can be determined whether to retry the call to the target API. If it is determined to retry, return to the starting position and re-determine whether there is a pre-configured local speed limit threshold for the target API for the target NFV network element and subsequent operations. If it is determined that there is no need to retry the call to the target API, end the call.

[0034] Furthermore, after limiting the speed of the API call to the target NFV network element, the resource orchestration operation for the target NFV network element is initiated for the target virtual component through the API. After gradually completing the orchestration operations for each target virtual component required for the target NFV network element, the target NFV network element required by the front-end user 103 can be obtained, and the target NFV network element is used to provide services for the front-end user 103.

[0035] Further optionally, if Figure 1bAs shown, in the case where there is no local speed limit threshold of the target API for the target NFV network element, or in the case where it is determined that there is no need to limit the speed of the current call of the target API according to the local speed limit threshold of the target API for the target NFV network element, the NFV orchestration device 101 can also determine whether it is necessary to limit the speed of the current call of the target API for the target NFV network element according to the global speed limit threshold of the target API; if it is determined that it is necessary to limit the speed of the current call of the target API according to the global speed limit threshold of the target API, after limiting the speed of the current call of the target API, the target API is used to initiate a resource orchestration operation for the target NFV network element to the target virtual component. Optionally, the total number of calls initiated to the target API can be counted from the dimension of the NFV orchestration device 101, and the total number refers to the total number of calls initiated by the NFV orchestration device 101 to the target API for each NFV network element, and then it is determined whether the total number of calls initiated to the target API for each NFV network element reaches the global speed limit threshold; if so, it is determined that it is necessary to limit the speed of the current call of the target API; otherwise, it is determined that it is not necessary to limit the speed of the current call of the target API. Further optionally, as Figure 1b As shown, when it is determined that there is no need to limit the speed of the current call of the target API according to the global speed limit threshold of the target API, the NFV orchestration device 101 can directly initiate a resource orchestration operation for the target NFV network element to the target virtual component through the target API.

[0036] In this embodiment, for the southbound API provided by any virtual component, local speed limit thresholds can be dynamically configured for some NFV network elements, and there is no limitation on which NFV network elements are configured for the local speed limit thresholds. For example, the local speed limit threshold can be configured for specific NFV network elements, and the specific NFV network elements can be some preset NFV network elements, or network elements that can realize specific network functions, or some NFV network elements specified by the front-end user 103. In addition, some hot NFV network elements can also be selected to configure local speed limit thresholds for the southbound API for these hot NFV network elements. Hot NFV network elements refer to NFV network elements whose number of calls to the southbound API meets the set conditions. The set conditions can require that the number of calls to the southbound API by the NFV network element exceeds the set number threshold within a certain period of time, or require that the frequency of calls to the southbound API by the NFV network element exceeds the configured frequency threshold within a certain period of time, but is not limited to this. The following embodiment will introduce how to configure a local speed limit threshold for the southbound API for the hot NFV network element:

[0037] In this embodiment, a speed limit period is maintained for the southbound API provided by the virtual component 104, and the speed limit period can be 1 second (s), 2s or 5s, which is not limited to this. Each time the NFV orchestration device 101 calls the southbound API of the virtual component, the information of the NFV network element for which the southbound API is called and the information of the southbound API are recorded in the log data. Based on this, the NFV orchestration device 101 can obtain at least one hotspot NFV network element whose number of calls to the southbound API meets the set conditions according to the log data of the southbound API being called in the last N speed limit periods, where N is a positive integer. For example, the NFV network element whose total number of calls to the southbound API in N speed limit periods exceeds the set number threshold can be used as a hotspot NFV network element, and the set number threshold can be 100 times, 150 times or 1,000 times, which is not limited to this.

[0038] Further optionally, an alarm event may be pre-set, and the alarm event is used to trigger the NFV orchestration device 101 to dynamically configure a local speed limit threshold for the hotspot NFV for the southbound API. That is, only when an alarm event occurs for the southbound API, the NFV orchestration device 101 will select a hotspot NFV network element for the southbound API and configure a local speed limit threshold for these hotspot NFV network elements. This embodiment does not limit the alarm event. For example, the alarm event may be a dynamic configuration cycle arrival event. The dynamic configuration cycle is a cycle for the NFV orchestration device 101 to dynamically configure a local speed limit threshold for the hotspot NFV for the southbound API. For example, it may be 5s, 10s or 1 minute (min), etc., and there is no limitation on this. Based on this, whenever the dynamic configuration cycle arrives, the NFV orchestration device 101 will select a hotspot NFV network element for each southbound API according to the log data of each southbound API being called in the last N speed limit cycles, and configure a local speed limit threshold for these hotspot NFV network elements. For another example, the alarm event may also be an event that the total number of calls to the southbound API by the NFV orchestration device 101 within the first time reaches the global speed limit threshold of the southbound API. The length of the first time is not limited here, for example, it can be 1s, 5s or 10s, or it can be one or several speed limit cycles mentioned above. Based on this, the NFV orchestration device 101 can also monitor the total number of calls to each southbound API within the first time. If it is monitored that the total number of calls to a southbound API within the first time exceeds the global speed limit threshold of the southbound API, it means that an alarm event for the southbound API occurs. When the alarm event occurs, the NFV orchestration device 101 can obtain at least one hotspot NFV network element whose number of calls to the southbound API meets the set conditions based on the log data of the southbound API being called in the last N speed limit cycles, and configure local speed limit thresholds for these hotspot NFV network elements.

[0039] Further optionally, for the same southbound API, for each alarm event that occurs, it takes a certain amount of time for the NFV orchestration device 101 to process it. It is possible that before the NFV orchestration device 101 has time to process the current alarm event, the second alarm event comes again. The second alarm event and the first alarm event can be the same alarm event or different alarm events, and there is no limitation on this. If the two alarm events are the same, it is obvious that the NFV orchestration device 101 will waste resources if it processes both alarm events. Based on this, for a southbound API, when an alarm event occurs, the NFV orchestration device 101 can also determine whether the alarm event that occurs this time is the same as the alarm event that occurred last time; if the two alarm events are not the same, or the two alarm events are the same but the alarm event that occurred last time is not processed, it means that the alarm event needs to be processed this time, so the NFV orchestration device 101 executes the operation of obtaining at least one hotspot NFV network element whose number of calls to the southbound API meets the set conditions and configuring the local speed limit threshold for these NFV network elements according to the log data of the southbound API being called within N speed limit cycles. On the contrary, if the two alarm events are the same and the triggering time of the two alarm events does not exceed the set threshold, the alarm event that occurs this time will not be processed; or, if the two alarm events are the same, although the alarm event that occurred last time has been processed, that is, the local speed limit threshold has been configured for the corresponding hotspot NFV network element for the alarm event that occurred last time, and the local speed limit threshold is still in effect, then the alarm event that occurs this time may not be processed, saving processing resources.

[0040] In this embodiment, for any southbound API, after determining that the southbound API corresponds to a hotspot NFV network element, a local speed limit threshold of the southbound API for each hotspot NFV network element can be generated, and the local speed limit threshold of the southbound API for each hotspot NFV network element can be configured.

[0041] In this embodiment, the implementation method of the NFV orchestration device 101 generating the local speed limit threshold for each hotspot NFV network element of the southbound API is not limited. In an optional embodiment, a value less than the global speed limit threshold can be randomly selected as the local speed limit threshold for each hotspot NFV network element, and different hotspot NFV network elements have the same local speed limit threshold. Alternatively, different local speed limit thresholds can be generated for each hotspot NFV network element. In another optional embodiment, the intermediate speed limit value can be determined based on the global speed limit threshold of the southbound API and the number of at least one hotspot NFV network element. For example, if the global speed limit threshold of the southbound API is Q, the number of hotspot NFV network elements is X, and the number of non-hotspot NFV network elements is Y, then the intermediate speed limit value can be determined to be Q*X / (X+Y); for another example, if the global speed limit threshold of the southbound API is Q, Q / M can be directly used as the intermediate speed limit value, M>1, and is a positive integer. After determining the intermediate speed limit value, the intermediate speed limit value can be distributed among at least one hotspot NFV network element to obtain the local speed limit threshold of the southbound API for each hotspot NFV network element. For example, the intermediate speed limit value can be evenly distributed among at least one hotspot NFV network element. If the intermediate speed limit value is Q / M and the number of hotspot NFV network elements is X, then the local speed limit threshold of each hotspot NFV network element is Q / M*X. The intermediate speed limit value can also be unevenly distributed among at least one hotspot NFV network element. For example, if the intermediate speed limit value is H and the number of hotspot NFV network elements is 3, then the local speed limit thresholds allocated to the three hotspot NFV network elements can be H / 6, H / 3, and H / 2, and there is no limitation on this. Since the hotspot NFV network elements share the intermediate speed limit value, the non-hotspot NFV network elements can share the difference between the global speed limit threshold and the intermediate speed limit value. In this way, they do not need to compete with the hotspot NFV network elements for API call resources (mainly the number of API calls), which can reduce the impact of the hotspot NFV network elements on the non-hotspot NFV network elements when calling APIs.

[0042] In this embodiment, the NFV orchestration device 101 can dynamically configure the local speed limit threshold corresponding to the hotspot NFV network element for the southbound API. Of course, as the popularity of the hotspot NFV network element calling the southbound API decreases, the local speed limit threshold corresponding to the hotspot NFV network element can also be dynamically deleted. Based on this, in some optional embodiments of the present application, the NFV orchestration device 101 can continuously monitor the number of calls to the southbound API by at least one hotspot NFV network element; if it is monitored that the number of calls to the southbound API is less than the corresponding local speed limit threshold, and the hotspot NFV network element continues for T speed limit cycles, then the local speed limit threshold of the configured southbound API for the hotspot NFV network element is deleted, and T is a positive integer. Among them, for example, the condition of the local speed limit threshold corresponding to the southbound API can be that the number of calls to the southbound API in the second time is less than G% of the local speed limit threshold, where G% can be 30%, 50% or 75%, etc. Similarly, the length of the second time is not limited here, for example, it can be 1s, 3s, 5s or 10s, or it can be one or several of the speed limit periods mentioned above. It should be noted that the length of the second time can be the same as or different from the length of the first time mentioned above, and there is no limitation on this. The NFV orchestration device 101 can also dynamically delete the local speed limit threshold corresponding to the hotspot NFV network element as the heat of the hotspot NFV network element decreases. In other words, the NFV orchestration device 101 can dynamically adjust the NFV network element with the local speed limit threshold according to the fluctuation of the heat of the NFV network element, so as to realize the dynamic and reasonable on-demand allocation of speed limit threshold resources among different NFV network elements.

[0043] In this embodiment, in the case where the alarm event is an event that the total number of calls to the southbound API by the NFV orchestration device 101 within the first time reaches the global speed limit threshold of the southbound API, if the total number of calls to the southbound API by the NFV orchestration device 101 within the first time reaches the global speed limit threshold, an alarm is generated, and it can be considered that the basic component corresponding to the southbound API is in a busy state and the workload is heavy. At this time, the NFV orchestration device 101 can identify the NFV network element that is a hot spot for the API, and generate a local speed limit threshold for the hot NFV network element. The local speed limit threshold can be used to limit the API call speed for the hot NFV network element, reducing the impact on the API call of the non-hot NFV network element. If the total number of calls to the southbound API by the NFV orchestration device 101 within the first time does not reach the global speed limit threshold, the alarm will not be triggered. At this time, it means that the basic component corresponding to the southbound API is relatively not too busy, and the global speed limit threshold can be used to limit the overall speed of the call of the southbound API, so that the NFV orchestration device 101 can call the southbound API as successfully as possible, realize the resource orchestration operation, and ensure the service quality and user experience.

[0044] Figure 2aA flow chart of a NFV resource orchestration method provided by an exemplary embodiment of the present application. Figure 2a As shown, the method includes:

[0045] 201a. Receive resource deployment requirements for a target NFV network element, and determine a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirements;

[0046] 202a. After speed limiting the current call of the target API, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

[0047] In an optional embodiment, speed limiting processing is performed on the current call of the target API, including: obtaining a pre-configured local speed limit threshold of the target API for the target NFV network element; and speed limiting processing is performed on the current call of the target API according to the local speed limit threshold.

[0048] Further optionally, the current call of the target API is speed-limited according to the local speed-limit threshold, including: determining whether the number of calls initiated to the target API by the target NFV network element has reached the local speed-limit threshold; if so, speed-limiting the current call of the target API.

[0049] Further optionally, the method also includes: if the number of calls initiated to the target API for the target NFV network element has not reached the local speed limit threshold, then determining whether the total number of calls initiated to the target API for each NFV network element reaches the global speed limit threshold; if so, limiting the speed of this call to the target API.

[0050] In an optional embodiment, the method further includes: when a preset alarm event for triggering the dynamic configuration of a local speed limit threshold occurs, obtaining at least one hotspot NFV network element whose number of calls to the target API meets the set conditions based on the log data of the target API being called in the most recent N speed limit cycles, where N is a positive integer; generating a local speed limit threshold for the target API for each hotspot NFV network element, and configuring the local speed limit threshold for the target API for each hotspot NFV network element.

[0051] In this embodiment, resources of virtual components required by NFV network elements are orchestrated through the API provided by the virtual components. During the API calling process, after the API call is rate-limited, the API can be used to initiate orchestration operations on the NFV network elements, thereby ensuring the availability and reliability of the virtual components.

[0052] Figure 2b A flow chart of another NFV resource orchestration method provided by an exemplary embodiment of the present application. Figure 2b As shown, the method includes:

[0053] 201b. Receive resource deployment requirements for a target NFV network element, and determine a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirements;

[0054] 202b. If there is a pre-configured local speed limit threshold for the target API for the target NFV network element, and it is determined based on the local speed limit threshold that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

[0055] In an optional embodiment, the method of this embodiment also includes: in the absence of a local speed limit threshold, or in the case where it is determined according to the local speed limit threshold that there is no need to speed limit the current call to the target API, determining whether it is necessary to speed limit the current call to the target API according to the global speed limit threshold of the target API; if it is determined according to the global speed limit threshold that it is necessary to speed limit the current call to the target API, after speed limiting the current call to the target API, initiating a resource orchestration operation for the target NFV network element to the target virtual component through the target API; wherein the local speed limit threshold is less than the global speed limit threshold.

[0056] In an optional embodiment, the method of this embodiment further includes: initiating a resource orchestration operation for the target NFV network element on the target virtual component through the target API when it is determined that there is no need to limit the rate of the current call to the target API.

[0057] Further optionally, determining that the current call of the target API needs to be speed-limited according to the local speed-limit threshold includes: if the number of calls initiated to the target API by the target NFV network element reaches the local speed-limit threshold, determining that the current call of the target API needs to be speed-limited;

[0058] Correspondingly, it is determined that the current call to the target API needs to be speed limited according to the global speed limit threshold, including: if the total number of calls initiated to the target API by each NFV network element reaches the global speed limit threshold, it is determined that the current call to the target API needs to be speed limited.

[0059] In an optional embodiment, the method of this embodiment also includes: when an alarm event set for triggering the dynamic configuration of a local speed limit threshold occurs, obtaining at least one hotspot NFV network element whose number of calls to the target API meets the set conditions based on the log data of the target API being called in the last N speed limit cycles, where N is a positive integer; generating a local speed limit threshold for the target API for each hotspot NFV network element, and configuring the local speed limit threshold for the target API for each hotspot NFV network element.

[0060] In an optional embodiment, a local speed limit threshold of the target API for each hotspot NFV network element is generated, including: determining an intermediate speed limit value according to a global speed limit threshold of the target API and the number of at least one hotspot NFV network element; and distributing the intermediate speed limit value among at least one hotspot NFV network element to obtain a local speed limit threshold of the target API for each hotspot NFV network element.

[0061] In an optional embodiment, the alarm event includes at least one of the following: a dynamic configuration period arrival event, and an event that the total number of calls to the target API reaches a global rate limit threshold of the target API.

[0062] In an optional embodiment, the method of this embodiment also includes: continuously monitoring the number of calls to the target API by at least one hotspot NFV network element; if the number of calls to the target API is monitored to be less than the corresponding local speed limit threshold, and the first hotspot NFV network element continues for T speed limit periods, then the configured local speed limit threshold of the target API for the first hotspot NFV network element is deleted, and T is a positive integer.

[0063] The NFV resource orchestration method provided in the embodiment of the present application orchestrates resources for virtual components required by NFV network elements through the API provided by the virtual components to the outside. In the process of calling the API, after the API call is speed-limited, the orchestration operation for the NFV network element can be initiated for the virtual component through the API, thereby ensuring the availability and reliability of the virtual component. Further, when the API call is speed-limited, a local speed-limiting threshold can be dynamically configured for the API for some NFV network elements, thereby speed-limiting the API call in the NFV network element dimension. In view of this, when an API call is initiated for a certain NFV network element, it can be determined whether there is a pre-configured local speed-limiting threshold for the API for the NFV network element. If so, it is determined whether the current call of the API needs to be speed-limited according to the local speed-limiting threshold. If speed-limiting is required, the current call of the API is speed-limited before the NFV resource orchestration operation is performed through the API. Among them, limiting the speed of API calls from the NFV network element dimension can, to a certain extent, reduce the mutual impact between different NFV network elements when limiting the speed of API calls. At the same time, it can ensure that the calls to the API do not exceed its rate limit, which is conducive to ensuring the stability of the NFV orchestration system and improving service quality and user experience.

[0064] It should be noted that in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or executed in parallel, and the sequence numbers of the operations, such as 201b, 202b, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit the "first" and "second" to be different types.

[0065] Figure 3 A schematic diagram of the structure of a NFV resource orchestration device provided by an exemplary embodiment of the present application. Figure 3 As shown, the device includes: a memory 34 and a processor 35.

[0066] The memory 34 is used to store computer programs and can be configured to store various other data to support operations on the NFV resource orchestration device. Examples of these data include instructions for any application program or method operating on the NFV resource orchestration device.

[0067] The memory 34 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0068] The processor 35 is coupled to the memory 34 and is used to execute the computer program in the memory 34, so as to: receive resource deployment requirements for the target NFV network element, and determine the target application program interface API required for orchestrating the target virtual component according to the resource deployment requirements; if there is a pre-configured local speed limit threshold of the target API for the target NFV network element, and it is determined according to the local speed limit threshold that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

[0069] In an optional embodiment, the processor 35 is also used to: in the absence of a local speed limit threshold, or in the case where it is determined according to the local speed limit threshold that there is no need to speed limit the current call to the target API, determine whether it is necessary to speed limit the current call to the target API according to the global speed limit threshold of the target API; if it is determined according to the global speed limit threshold that it is necessary to speed limit the current call to the target API, after speed limiting the current call to the target API, initiate a resource orchestration operation for the target NFV network element to the target virtual component through the target API; wherein the local speed limit threshold is less than the global speed limit threshold.

[0070] In an optional embodiment, the processor 35 is further configured to: when it is determined that there is no need to limit the rate of the current call to the target API, initiate a resource orchestration operation for the target NFV network element on the target virtual component through the target API.

[0071] In an optional embodiment, the processor 35 is also used for: when an alarm event set for triggering the dynamic configuration of the local speed limit threshold occurs, based on the log data of the target API being called in the last N speed limit cycles, obtaining at least one hotspot NFV network element whose number of calls to the target API meets the set conditions, where N is a positive integer; generating a local speed limit threshold for the target API for each hotspot NFV network element, and configuring the local speed limit threshold for the target API for each hotspot NFV network element.

[0072] In an optional embodiment, when the processor 35 generates the local speed limit threshold of the target API for each hotspot NFV network element, it is specifically used to: determine the intermediate speed limit value according to the global speed limit threshold of the target API and the number of at least one hotspot NFV network element; distribute the intermediate speed limit value among at least one hotspot NFV network element to obtain the local speed limit threshold of the target API for each hotspot NFV network element.

[0073] In an optional embodiment, the alarm event includes at least one of the following: a dynamic configuration period arrival event, and an event that the total number of calls to the target API reaches a global rate limit threshold of the target API.

[0074] In an optional embodiment, the processor 35 is also used to: continuously monitor the number of calls to the target API by at least one hotspot NFV network element; if the number of calls to the target API is monitored to be less than the corresponding local speed limit threshold, and the first hotspot NFV network element continues for T speed limit cycles, then the configured local speed limit threshold of the target API for the first hotspot NFV network element is deleted, and T is a positive integer.

[0075] The NFV resource orchestration device provided in the embodiment of the present application orchestrates resources for virtual components required by NFV network elements through the API provided by the virtual components to the outside. In the process of calling the API, after the API call is speed-limited, the orchestration operation for the NFV network element can be initiated for the virtual component through the API, thereby ensuring the availability and reliability of the virtual component. Further, when the API call is speed-limited, a local speed-limiting threshold can be dynamically configured for the API for some NFV network elements, thereby speed-limiting the API call in the NFV network element dimension. In view of this, when an API call is initiated for a certain NFV network element, it can be determined whether there is a pre-configured local speed-limiting threshold for the API for the NFV network element. If so, it is determined whether the current call of the API needs to be speed-limited according to the local speed-limiting threshold. If speed-limiting is required, the current call of the API is speed-limited before the NFV resource orchestration operation is performed through the API. Among them, limiting the speed of API calls from the NFV network element dimension can, to a certain extent, reduce the mutual impact between different NFV network elements when limiting the speed of API calls. At the same time, it can ensure that the calls to the API do not exceed its rate limit, which is conducive to ensuring the stability of the NFV orchestration system and improving service quality and user experience.

[0076] Further, if Figure 3 As shown, the NFV resource orchestration device also includes: a communication component 36, a display 37, a power component 38, an audio component 39 and other components. Figure 3 Only some components are shown schematically, which does not mean that NFV resource orchestration equipment only includes Figure 3 It should be noted that Figure 3 The components in the dotted box are optional components, not mandatory components, and the specific components depend on the product form of the NFV resource orchestration device.

[0077] Furthermore, the present application also provides a NFV resource orchestration device, which has a structure similar to Figure 3 The implementation structure of the NFV resource orchestration device shown in the figure is the same or similar, and is not shown in the figure again. Figure 3 The main difference between the NFV resource orchestration devices shown is that the functions implemented by the processor executing the computer program in the memory are different, which will be explained in detail below. The NFV resource orchestration device of this embodiment, its processor executes the computer program stored in the memory to:

[0078] Receive resource deployment requirements for the target NFV network element, and determine the target application program interface API required for orchestrating the target virtual component according to the resource deployment requirements; after rate limiting the current call of the target API, initiate a resource orchestration operation for the target NFV network element on the target virtual component through the target API.

[0079] In an optional embodiment, when the processor performs speed limit processing on the current call of the target API, it is specifically used to: obtain a pre-configured local speed limit threshold of the target API for the target NFV network element; and perform speed limit processing on the current call of the target API according to the local speed limit threshold.

[0080] In an optional embodiment, when the processor performs speed limiting processing on the current call of the target API according to the local speed limit threshold, it is specifically used to: determine whether the number of calls initiated by the target NFV network element to the target API has reached the local speed limit threshold; if so, limit the speed of the current call of the target API.

[0081] In an optional embodiment, the processor is also used to: if the number of calls initiated to the target API for the target NFV network element has not reached the local speed limit threshold, then determine whether the total number of calls initiated to the target API for each NFV network element reaches the global speed limit threshold; if so, limit the speed of this call to the target API; the local speed limit threshold is less than the global speed limit threshold.

[0082] In an optional embodiment, the processor is also used to: when a preset alarm event for triggering the dynamic configuration of a local speed limit threshold occurs, obtain at least one hotspot NFV network element whose number of calls to the target API meets the set conditions based on the log data of the target API being called in the last N speed limit cycles, where N is a positive integer; generate a local speed limit threshold for the target API for each hotspot NFV network element, and configure the local speed limit threshold for the target API for each hotspot NFV network element.

[0083] Accordingly, the embodiment of the present application further provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the processor is enabled to implement the above Figure 2a or Figure 2b The steps in the method embodiment are shown.

[0084] Accordingly, the embodiment of the present application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, causes the processor to implement the above Figure 2a or Figure 2b The steps in the method embodiment are shown.

[0085] Figure 4 A schematic diagram of the structure of a NFV resource orchestration device provided by an exemplary embodiment of the present application is shown in FIG. Figure 4 As shown, the device includes: a receiving module 41a, a determining module 42a and an initiating module 43a.

[0086] The receiving module 41a is used to: receive resource deployment requirements for a target NFV network element;

[0087] The determination module 42a is used to: determine the target application program interface API required for orchestrating the target virtual component according to the resource deployment requirements;

[0088] The initiating module 43a is used for: if there is a pre-configured local speed limit threshold of the target API for the target NFV network element, and it is determined according to the local speed limit threshold that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

[0089] In an optional embodiment, the determination module 42a is used to: in the absence of a local speed limit threshold, or in the case where it is determined that there is no need to speed limit the current call to the target API based on the local speed limit threshold, determine whether it is necessary to speed limit the current call to the target API based on the global speed limit threshold of the target API; the initiation module 43a is used to: if it is determined that it is necessary to speed limit the current call to the target API based on the global speed limit threshold, after speed limiting the current call to the target API, initiate a resource orchestration operation for the target NFV network element to the target virtual component through the target API; wherein the local speed limit threshold is less than the global speed limit threshold.

[0090] In an optional embodiment, the initiating module 43a is used to: when it is determined that there is no need to limit the rate of the current call to the target API, initiate a resource orchestration operation for the target NFV network element to the target virtual component through the target API.

[0091] In an optional embodiment, the device also includes: an acquisition module and a generation module; the acquisition module is used to: when a set alarm event for triggering the dynamic configuration of a local speed limit threshold occurs, based on the log data of the target API being called in the last N speed limit cycles, obtain at least one hotspot NFV network element whose number of calls to the target API meets the set conditions, where N is a positive integer; and is used to: generate a local speed limit threshold for the target API for each hotspot NFV network element, and configure the local speed limit threshold for the target API for each hotspot NFV network element.

[0092] In an optional embodiment, when generating the local speed limit threshold of the target API for each hotspot NFV network element, the generation module is specifically used to: determine the intermediate speed limit value according to the global speed limit threshold of the target API and the number of at least one hotspot NFV network element; distribute the intermediate speed limit value among at least one hotspot NFV network element to obtain the local speed limit threshold of the target API for each hotspot NFV network element.

[0093] In an optional embodiment, the alarm event includes at least one of the following: a dynamic configuration period arrival event, and an event that the total number of calls to the target API reaches a global rate limit threshold of the target API.

[0094] In an optional embodiment, the device also includes: a detection module and a deletion module; the detection module is used to: continuously monitor the number of calls to the target API by at least one hotspot NFV network element; the deletion module is used to: if it is monitored that the number of calls to the target API is less than the corresponding local speed limit threshold, and the first hotspot NFV network element continues for T speed limit cycles, then the configured target API is deleted for the local speed limit threshold of the first hotspot NFV network element, where T is a positive integer.

[0095] The NFV resource orchestration device provided in the embodiment of the present application orchestrates resources for virtual components required by NFV network elements through the API provided by the virtual components to the outside. In the process of calling the API, after the API call is speed-limited, the orchestration operation for the NFV network element can be initiated for the virtual component through the API, thereby ensuring the availability and reliability of the virtual component. Further, when the API call is speed-limited, a local speed-limiting threshold can be dynamically configured for the API for some NFV network elements, thereby speed-limiting the API call in the NFV network element dimension. In view of this, when an API call is initiated for a certain NFV network element, it can be determined whether there is a pre-configured local speed-limiting threshold for the API for the NFV network element. If so, it is determined whether the current call of the API needs to be speed-limited according to the local speed-limiting threshold. If speed-limiting is required, the current call of the API is speed-limited before the NFV resource orchestration operation is performed through the API. Among them, limiting the speed of API calls from the NFV network element dimension can, to a certain extent, reduce the mutual impact between different NFV network elements when limiting the speed of API calls. At the same time, it can ensure that the calls to the API do not exceed its rate limit, which is conducive to ensuring the stability of the NFV orchestration system and improving service quality and user experience.

[0096] Above Figure 3 The communication component in is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G / LTE, 5G and other mobile communication networks, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0097] Above Figure 3 The display in the embodiment includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0098] Above Figure 3 The power supply component in the device provides power to various components of the device where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply component is located.

[0099] Above Figure 3 The audio component in can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting an audio signal.

[0100] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0101] The present application is described with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, and the combination of the process and / or box in the flowchart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram.

[0102] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0103] These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0104] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0105] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0106] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0107] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0108] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A network function virtualization NFV resource orchestration system, characterized in that: include: An NFV orchestration device and an NFV resource pool, wherein the NFV resource pool includes at least one virtual component, and the at least one virtual component is deployed on at least one physical machine; The NFV orchestration device is used to receive resource deployment requirements for a target NFV network element, and determine a target application program interface API required for orchestrating a target virtual component based on the resource deployment requirements; if there is a pre-configured local speed limit threshold for the target API for the target NFV network element, and if the number of calls to the target API initiated for the target NFV network element reaches the local speed limit threshold, it is determined that the current call to the target API needs to be speed limited, then after the current call to the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

2. The system according to claim 1, characterized in that The NFV orchestration device is also used for: In the case where the local speed limit threshold does not exist, or in the case where it is determined according to the local speed limit threshold that the current call of the target API does not need to be speed limited, determining whether the current call of the target API needs to be speed limited according to the global speed limit threshold of the target API; If the total number of calls initiated to the target API for each NFV network element reaches the global speed limit threshold, it is determined that the current call to the target API needs to be speed limited. After the current call to the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API; wherein the local speed limit threshold is less than the global speed limit threshold.

3. The system according to claim 2, characterized in that The NFV orchestration device is also used for: When it is determined that there is no need to limit the speed of the current call of the target API, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

4. The system according to any one of claims 1 to 3, characterized in that: The NFV orchestration device is also used for: When a preset alarm event for triggering the dynamic configuration of a local speed limit threshold occurs, obtaining at least one hotspot NFV network element whose number of calls to the target API meets a set condition according to log data of the target API being called in the most recent N speed limit cycles, where N is a positive integer; Generate a local speed limit threshold of the target API for each hotspot NFV network element, and configure the local speed limit threshold of the target API for each hotspot NFV network element.

5. The system according to claim 4, characterized in that When generating the local rate limit threshold, the NFV orchestration device is specifically used to: Determine an intermediate rate limit value according to the global rate limit threshold of the target API and the number of the at least one hotspot NFV network element; The intermediate rate limit value is distributed among the at least one hotspot NFV network element to obtain a local rate limit threshold value of the target API for each hotspot NFV network element.

6. The system according to claim 4, characterized in that The alarm event includes at least one of the following: a dynamic configuration period arrival event, and an event that the total number of calls to the target API reaches a global rate limit threshold of the target API.

7. The system according to claim 4, characterized in that The NFV orchestration device is also used for: Determine whether the alarm event that occurred this time is the same as the alarm event that occurred last time; If two alarm events are the same and the previous alarm event has been processed, the current alarm event will not be processed.

8. The system according to claim 4, characterized in that The NFV orchestration device is also used for: Continuously monitoring the number of calls to the target API by the at least one hotspot NFV network element; If it is monitored that the number of calls to the target API is less than the corresponding local speed limit threshold and the first hotspot NFV network element continues for T speed limit cycles, the local speed limit threshold of the configured target API for the first hotspot NFV network element will be deleted, and T is a positive integer.

9. A network function virtualization NFV resource orchestration method, characterized in that: include: Receiving a resource deployment requirement for a target NFV network element, and determining a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirement; If there is a pre-configured local speed limit threshold for the target API for the target NFV network element, and if the number of calls initiated to the target API for the target NFV network element reaches the local speed limit threshold, it is determined that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

10. The method according to claim 9, characterized in that Also includes: In the case where the local speed limit threshold does not exist, or in the case where it is determined according to the local speed limit threshold that the current call of the target API does not need to be speed limited, determining whether the current call of the target API needs to be speed limited according to the global speed limit threshold of the target API; If the total number of calls initiated to the target API for each NFV network element reaches the global speed limit threshold, it is determined that the current call to the target API needs to be speed limited. After the current call to the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API; wherein the local speed limit threshold is less than the global speed limit threshold.

11. The method according to claim 10, characterized in that Also includes: When it is determined that there is no need to limit the speed of the current call of the target API, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

12. The method according to any one of claims 9 to 11, characterized in that: Also includes: When a preset alarm event for triggering the dynamic configuration of a local speed limit threshold occurs, obtaining at least one hotspot NFV network element whose number of calls to the target API meets a set condition according to log data of the target API being called in the most recent N speed limit cycles, where N is a positive integer; Generate a local speed limit threshold of the target API for each hotspot NFV network element, and configure the local speed limit threshold of the target API for each hotspot NFV network element.

13. The method according to claim 12, characterized in that Generating the local rate limit threshold of the target API for each hotspot NFV network element includes: Determine an intermediate rate limit value according to the global rate limit threshold of the target API and the number of the at least one hotspot NFV network element; The intermediate rate limit value is distributed among the at least one hotspot NFV network element to obtain a local rate limit threshold value of the target API for each hotspot NFV network element.

14. The method according to claim 12, characterized in that The alarm event includes at least one of the following: a dynamic configuration period arrival event, and an event that the total number of calls to the target API reaches a global rate limit threshold of the target API.

15. The method according to claim 12, characterized in that Also includes: Continuously monitoring the number of calls to the target API by the at least one hotspot NFV network element; If it is monitored that the number of calls to the target API is less than the corresponding local speed limit threshold and the first hotspot NFV network element continues for T speed limit cycles, the local speed limit threshold of the configured target API for the first hotspot NFV network element will be deleted, and T is a positive integer.

16. A network function virtualization NFV resource orchestration method, characterized in that: include: Receiving a resource deployment requirement for a target NFV network element, and determining a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirement; Obtaining a pre-configured local speed limit threshold of the target API for the target NFV network element; if the number of calls initiated to the target API by the target NFV network element reaches the local speed limit threshold, speed limiting the current call of the target API; After speed limiting processing is performed on this call of the target API, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

17. The method according to claim 16, characterized in that Also includes: If the number of calls initiated to the target API by the target NFV network element has not reached the local speed limit threshold, then determine whether the total number of calls initiated to the target API by each NFV network element has reached the global speed limit threshold; If yes, limit the speed of this call to the target API; The local speed limit threshold is smaller than the global speed limit threshold.

18. The method according to any one of claims 16-17, characterized in that: Also includes: When a preset alarm event for triggering the dynamic configuration of a local speed limit threshold occurs, obtaining at least one hotspot NFV network element whose number of calls to the target API meets a set condition according to log data of the target API being called in the most recent N speed limit cycles, where N is a positive integer; Generate a local speed limit threshold of the target API for each hotspot NFV network element, and configure the local speed limit threshold of the target API for each hotspot NFV network element.

19. A network function virtualization NFV resource orchestration device, characterized in that: include: Memory and processor; The memory is used to store computer programs; The processor, coupled to the memory, is configured to execute the computer program to: Receiving a resource deployment requirement for a target NFV network element, and determining a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirement; If there is a pre-configured local speed limit threshold for the target API for the target NFV network element, and if the number of calls initiated to the target API for the target NFV network element reaches the local speed limit threshold, it is determined that the current call of the target API needs to be speed limited, then after the current call of the target API is speed limited, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

20. A network function virtualization NFV resource orchestration device, characterized in that: include: Memory and processor; The memory is used to store computer programs; The processor, coupled to the memory, is configured to execute the computer program to: Receiving a resource deployment requirement for a target NFV network element, and determining a target application program interface API required for orchestrating a target virtual component according to the resource deployment requirement; Obtaining a pre-configured local speed limit threshold of the target API for the target NFV network element; if the number of calls initiated to the target API by the target NFV network element reaches the local speed limit threshold, speed limiting the current call of the target API; After speed limiting processing is performed on this call of the target API, a resource orchestration operation for the target NFV network element is initiated on the target virtual component through the target API.

21. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is caused to implement the steps in the method according to any one of claims 9 to 18.

22. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the processor is caused to implement the steps in the method according to any one of claims 9 to 18.

Images