A capability deployment method, device and edge computing service operation equipment

Abstract

The present invention provides a capability deployment method, device and edge computing business operation equipment, which relates to the field of communication technology. The method includes: receiving capability call information sent by a first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by an edge computing application ECA on the first ECP node; when at least one ECA calls a first capability and the first ECP node does not support the first capability, deploying the first capability on the first ECP node according to a preset strategy. The solution of the present invention solves the problem that the current cross-ECP capability call method may cause a large amount of link bandwidth waste and cannot better meet the user's service quality.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular to a capability deployment method, device, and edge computing service operation equipment. Background Art

[0002] There are two situations for capability calling: one is calling local capabilities, and the other is calling non-local capabilities. When calling the entity capability, you can access the corresponding address of the Application Programming Interface (API) by accessing the local Domain Name System (DNS). When calling non-local capabilities, you can call through cross-node capabilities. For example: the edge computing business operation platform (ECM) provides business management, operation management, resource management, operation and maintenance management and other functions. In addition, it will store the capability distribution information of the entire network to support cross-node capability calling. By requesting the big network DNS to obtain the ECM address and accessing the ECM, the ECM selects the most suitable ECP node according to the address of the edge computing application (ECA) that issues the request, the location of the edge computing platform (ECP) node where the requested API is located, and the load of the ECP node, and redirects the request of the ECA to the target ECP.

[0003] When an ECA on an ECP calls a capability that is not available locally, it needs to call across ECPs. Frequent or large-scale cross-node calls will result in a large waste of link bandwidth and cannot better meet the user's service quality. Summary of the invention

[0004] The purpose of the present invention is to provide a capability deployment method, device and edge computing business operation equipment to solve the problem that the current cross-ECP capability calling method may cause a large amount of link bandwidth waste and cannot better meet the user's service quality.

[0005] To achieve the above object, an embodiment of the present invention provides a capability deployment method, which is applied to an edge computing service operation device, and the method includes:

[0006] Receive capability call information sent by a first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node;

[0007] When at least one ECA invokes a first capability and the first ECP node does not support the first capability, the first capability is deployed on the first ECP node according to a preset policy.

[0008] Optionally, the capability calling information includes at least one of the following:

[0009] an identifier of the first ECP node;

[0010] The identifier of the capability invoked by the ECA;

[0011] ECA application identification;

[0012] The calling time corresponding to the capability called by ECA;

[0013] An indicator of whether the capability called by ECA is successful;

[0014] The number of calls corresponding to the first capability;

[0015] a calling frequency corresponding to the first capability;

[0016] The amount of data to be called.

[0017] Optionally, when the capability call information includes: the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, the deploying the first capability on the first ECP node according to a preset strategy includes:

[0018] When the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold, deploying the first capability on the first ECP node according to a preset policy;

[0019] or,

[0020] In a case where the capability call information includes: the number of calls corresponding to the first capability and the amount of call data, the deploying the first capability on the first ECP node according to a preset strategy includes:

[0021] When the number of calls corresponding to the first capability is greater than a third threshold and the amount of call data is greater than a fourth threshold, the first capability is deployed on the first ECP node according to a preset strategy.

[0022] Optionally, the deploying the first capability on the first ECP node according to a preset policy includes:

[0023] In a case where the first ECP node has a capability image corresponding to the first capability, sending a control signaling to the first ECP node; wherein the control signaling is used to instruct the first ECP node to pull the capability image corresponding to the first capability;

[0024] In a case where the first ECP node does not have a capability image corresponding to the first capability, the capability image or the capability image address corresponding to the first capability is sent to the first ECP node.

[0025] Optionally, when the first ECP node does not have the capability image corresponding to the first capability, sending the capability image or the capability image address corresponding to the first capability to the first ECP node includes:

[0026] If the first ECP node does not have a capability image corresponding to the first capability, determining whether there are sufficient resources to deploy the first capability;

[0027] In a case where there are sufficient resources to deploy the first capability, a capability image or a capability image address corresponding to the first capability is sent to the first ECP node.

[0028] Optionally, in a case where the first ECP node does not have a capability image corresponding to the first capability, sending the capability image or the capability image address corresponding to the first capability to the first ECP node includes:

[0029] If the first ECP node does not have a capability image corresponding to the first capability, calculating a first cost of the first ECP node invoking the first capability across nodes and a second cost of the first ECP node deploying the first capability;

[0030] If the first cost is higher than the second cost, sending the capability image or the capability image address corresponding to the first capability to the first ECP node.

[0031] Optionally, the sending the capability image or the capability image address corresponding to the first capability to the first ECP node includes:

[0032] When the edge computing service operation device has a capability image of the first capability and there is no ECP node having the capability image of the first capability, the edge computing service operation device sends the capability image or the capability image address corresponding to the first capability to the first ECP node;

[0033] In a case where a plurality of second ECP nodes have a capability image of the first capability, determining a target ECP node among the plurality of second ECP nodes that meets a preset condition, and sending the capability image of the first capability to the first ECP node through the target ECP node;

[0034] The second ECP node is an ECP node other than the first ECP node.

[0035] Optionally, determining a target ECP node that meets a preset condition among the plurality of second ECP nodes includes:

[0036] Determine a second ECP node among the plurality of second ECP nodes that is closest to the first ECP node as the target ECP node;

[0037] and / or,

[0038] A second ECP node among the plurality of second ECP nodes having the highest link quality with the first ECP node is determined as the target ECP node.

[0039] To achieve the above object, an embodiment of the present invention further provides a capability deployment device, which is applied to an edge computing service operation device, including:

[0040] A capability call monitoring module is used to receive capability call information sent by a first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node;

[0041] The capability distribution module is used to deploy the first capability on the first ECP node according to a preset policy when at least one ECA calls the first capability and the first ECP node does not support the first capability.

[0042] Optionally, the capability calling information includes at least one of the following:

[0043] an identifier of the first ECP node;

[0044] The identifier of the capability invoked by the ECA;

[0045] ECA application identification;

[0046] The calling time corresponding to the capability called by ECA;

[0047] An indicator of whether the capability called by ECA is successful;

[0048] The number of calls corresponding to the first capability;

[0049] a calling frequency corresponding to the first capability;

[0050] The amount of data to be called.

[0051] Optionally, the capability distribution module includes:

[0052] A first processing submodule, configured to deploy the first capability on the first ECP node according to a preset strategy when the capability call information includes the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, if the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold;

[0053] or,

[0054] The second processing submodule is used for deploying the first capability on the first ECP node according to a preset strategy when the capability call information includes the number of calls corresponding to the first capability and the amount of call data, and when the number of calls corresponding to the first capability is greater than a third threshold and the amount of call data is greater than a fourth threshold.

[0055] Optionally, the capability distribution module includes:

[0056] A first distribution submodule, configured to send a control signaling to the first ECP node when the first ECP node has a capability image corresponding to the first capability; wherein the control signaling is used to instruct the first ECP node to pull the capability image corresponding to the first capability;

[0057] The second distribution submodule is configured to send the capability image or the capability image address corresponding to the first capability to the first ECP node when the first ECP node does not have the capability image corresponding to the first capability.

[0058] Optionally, the second distribution submodule includes:

[0059] a judging unit, configured to judge whether there are sufficient resources to deploy the first capability if the first ECP node does not have a capability image corresponding to the first capability;

[0060] The first distribution unit is configured to send a capability image or a capability image address corresponding to the first capability to the first ECP node when there are sufficient resources to deploy the first capability.

[0061] Optionally, the second distribution submodule includes:

[0062] A calculation unit, configured to calculate a first cost of the first ECP node invoking the first capability across nodes and a second cost of the first ECP node deploying the first capability when the first ECP node does not have a capability image corresponding to the first capability;

[0063] The second distribution unit is configured to send the capability image or the capability image address corresponding to the first capability to the first ECP node if the first cost is higher than the second cost.

[0064] Optionally, the capability distribution module includes:

[0065] A first distribution subunit is configured to, when the edge computing service operation device has a capability image of the first capability and there is no ECP node having the capability image of the first capability, send the capability image or the capability image address corresponding to the first capability to the first ECP node by the edge computing service operation device;

[0066] a second distribution subunit, configured to determine, when a plurality of second ECP nodes have a capability image of the first capability, a target ECP node that meets a preset condition among the plurality of second ECP nodes, and send the capability image of the first capability to the first ECP node through the target ECP node;

[0067] The second ECP node is an ECP node other than the first ECP node.

[0068] Optionally, the second distribution subunit is further used for:

[0069] Determine a second ECP node among the plurality of second ECP nodes that is closest to the first ECP node as the target ECP node;

[0070] and / or,

[0071] A second ECP node among the plurality of second ECP nodes having the highest link quality with the first ECP node is determined as the target ECP node.

[0072] To achieve the above-mentioned object, an embodiment of the present invention provides an edge computing service operation device, including: a transceiver and a processor;

[0073] The transceiver is used to: receive capability call information sent by the first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node;

[0074] The processor is configured to deploy the first capability on the first ECP node according to a preset policy when at least one ECA invokes the first capability and the first ECP node does not support the first capability.

[0075] Optionally, the capability calling information includes at least one of the following:

[0076] an identifier of the first ECP node;

[0077] The identifier of the capability invoked by the ECA;

[0078] ECA application identification;

[0079] The calling time corresponding to the capability called by ECA;

[0080] An indicator of whether the capability called by ECA is successful;

[0081] The number of calls corresponding to the first capability;

[0082] a calling frequency corresponding to the first capability;

[0083] The amount of data to be called.

[0084] Optionally, the processor is configured to: when the capability call information includes: the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, if the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold, deploy the first capability on the first ECP node according to a preset strategy;

[0085] or,

[0086] The processor is used for: when the capability call information includes: the number of calls corresponding to the first capability and the amount of call data, when the number of calls corresponding to the first capability is greater than a third threshold, and the amount of call data is greater than a fourth threshold, deploying the first capability on the first ECP node according to a preset strategy.

[0087] Optionally, the transceiver is used for:

[0088] In a case where the first ECP node has a capability image corresponding to the first capability, sending a control signaling to the first ECP node; wherein the control signaling is used to instruct the first ECP node to pull the capability image corresponding to the first capability;

[0089] In a case where the first ECP node does not have a capability image corresponding to the first capability, the capability image or the capability image address corresponding to the first capability is sent to the first ECP node.

[0090] Optionally, the processor is configured to: if the first ECP node does not have a capability image corresponding to the first capability, determine whether there are sufficient resources to deploy the first capability;

[0091] The transceiver is used to: when there are sufficient resources to deploy the first capability, send the capability image or the capability image address corresponding to the first capability to the first ECP node.

[0092] Optionally, the processor is configured to: when the first ECP node does not have a capability image corresponding to the first capability, calculate a first cost of the first ECP node invoking the first capability across nodes and a second cost of the first ECP node deploying the first capability;

[0093] The transceiver is configured to: if the first cost is higher than the second cost, send a capability image or a capability image address corresponding to the first capability to the first ECP node.

[0094] Optionally, the transceiver is used for:

[0095] When the edge computing service operation device has a capability image of the first capability and there is no ECP node having the capability image of the first capability, sending the capability image or the capability image address corresponding to the first capability to the first ECP node;

[0096] In a case where a plurality of second ECP nodes have a capability image of the first capability, determining a target ECP node among the plurality of second ECP nodes that meets a preset condition, and sending the capability image of the first capability to the first ECP node through the target ECP node;

[0097] The second ECP node is an ECP node other than the first ECP node.

[0098] Optionally, the processor is configured to:

[0099] Determine a second ECP node among the plurality of second ECP nodes that is closest to the first ECP node as the target ECP node;

[0100] and / or,

[0101] A second ECP node among the plurality of second ECP nodes having the highest link quality with the first ECP node is determined as the target ECP node.

[0102] To achieve the above-mentioned purpose, an embodiment of the present invention provides an edge computing business operation device, including: a transceiver, a processor, a memory, and a program or instruction stored on the memory and executable on the processor; when the processor executes the program or instruction, the steps of the capability deployment method described above are implemented.

[0103] To achieve the above objective, an embodiment of the present invention provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the capability deployment method described above are implemented.

[0104] The beneficial effects of the above technical solution of the present invention are as follows:

[0105] The embodiment of the present invention receives capability call information sent by a first edge computing platform ECP node, and when it is determined that at least one ECA on the first ECP node has called a first capability and the first ECP node does not support the first capability, deploys the first capability on the first ECP node according to a preset strategy, so as to avoid the problem that the ECA on the ECP needs to call a capability that is not available locally across the ECP, and that frequent cross-node calls may result in a large amount of link bandwidth waste and cannot better meet the user's service quality, thereby ensuring business quality and saving bandwidth resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0106] Figure 1 A flowchart of a capability deployment method according to an embodiment of the present invention;

[0107] Figure 2 A schematic diagram of the interaction between ECM and ECP nodes according to an embodiment of the present invention;

[0108] Figure 3 A flowchart of capability deployment according to an embodiment of the present invention;

[0109] Figure 4 A block diagram of a capability deployment device according to an embodiment of the present invention;

[0110] Figure 5 This is one of the block diagrams of the edge computing service operation device according to an embodiment of the present invention;

[0111] Figure 6 This is the second block diagram of the edge computing business operation device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0112] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0113] It should be understood that the references to "one embodiment" or "an embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present invention. Therefore, the references to "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0114] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0115] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0116] In the embodiments provided in the present application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0117] like Figure 1 As shown, a capability deployment method of an embodiment of the present invention is applied to an edge computing service operation device ECM, and the method includes:

[0118] Step 11: Receive capability call information sent by the first edge computing platform ECP node.

[0119] The capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node;

[0120] Step 12: When at least one ECA calls a first capability and the first ECP node does not support the first capability, deploy the first capability on the first ECP node according to a preset policy.

[0121] In this embodiment, by receiving capability call information sent by the first edge computing platform ECP node, when it is determined that at least one ECA on the first ECP node has called the first capability and the first ECP node does not support the first capability, the first capability is deployed on the first ECP node according to a preset strategy to avoid the problem that the ECA on the ECP needs to call capabilities that are not available locally across ECPs, resulting in frequent cross-node calls and possible waste of a large amount of link bandwidth and failure to better meet the user's service quality, thereby ensuring business quality and saving bandwidth resources.

[0122] Optionally, the capability calling information includes at least one of the following: an identifier of the first ECP node; an identifier of the capability called by the ECA; an application identifier of the ECA; a calling time corresponding to the capability called by the ECA; an identifier of whether the capability called by the ECA is successful; the number of calls corresponding to the first capability; the calling frequency corresponding to the first capability; and the amount of call data.

[0123] Optionally, when the capability call information includes: the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, the deploying the first capability on the first ECP node according to a preset strategy includes:

[0124] When the number of calls corresponding to the first capability is greater than a first threshold, and the calling frequency corresponding to the first capability is greater than a second threshold, the first capability is deployed on the first ECP node according to a preset policy.

[0125] In this embodiment, by judging the number of capability calls and the calling frequency, in the case where the first capability may be called frequently and multiple times, the first capability can be deployed on the first ECP node according to a preset strategy, thereby avoiding the need for the ECA on the ECP to call a capability that is not available locally across ECPs, and avoiding the problem of frequent cross-node calls and possible waste of a large amount of link bandwidth and failure to better meet the user's service quality, thereby ensuring business quality and saving bandwidth resources.

[0126] Optionally, when the capability call information includes: the number of calls corresponding to the first capability and the call data volume, the deploying the first capability on the first ECP node according to a preset strategy includes:

[0127] When the number of calls corresponding to the first capability is greater than a third threshold and the amount of call data is greater than a fourth threshold, the first capability is deployed on the first ECP node according to a preset strategy.

[0128] In this embodiment, by judging the number of capability calls and the amount of call data, in the case where the first capability may be called multiple times and the amount of call data is large, the first capability can be deployed on the first ECP node according to a preset strategy, thereby avoiding the need for the ECA on the ECP to call capabilities that are not available locally across ECPs, and avoiding the problem of frequent cross-node calls and possible waste of a large amount of link bandwidth and failure to better meet the user's service quality, thereby ensuring business quality and saving bandwidth resources.

[0129] Optionally, the deploying the first capability on the first ECP node according to a preset policy includes:

[0130] In a case where the first ECP node has a capability image corresponding to the first capability, a control signaling is sent to the first ECP node; wherein the control signaling is used to instruct the first ECP node to pull the capability image corresponding to the first capability.

[0131] In a case where the first ECP node does not have a capability image corresponding to the first capability, the capability image or the capability image address corresponding to the first capability is sent to the first ECP node.

[0132] For example: When ECM determines that the calling frequency and calling times of a certain capability at a specified node exceed the threshold, it can trigger the judgment of capability delivery; if it is determined that the node has the capability image corresponding to the capability, the capability image of the node can be directly pulled up by sending control signaling. If it is determined that the node does not have the capability image corresponding to the capability, the capability can be deployed on the first ECP node by sending the capability image corresponding to the capability, thereby avoiding the problem that the ECA on the ECP needs to call capabilities that are not available locally across ECPs, and frequent cross-node calls may cause a large amount of link bandwidth to be wasted and fail to better meet the user's service quality, thereby ensuring business quality and saving bandwidth resources.

[0133] Optionally, when the first ECP node does not have the capability image corresponding to the first capability, sending the capability image or the capability image address corresponding to the first capability to the first ECP node includes:

[0134] In a case where the first ECP node does not have a capability image corresponding to the first capability, determine whether there are sufficient resources to deploy the first capability; and in a case where there are sufficient resources to deploy the first capability, send the capability image or the capability image address corresponding to the first capability to the first ECP node.

[0135] In this embodiment, when it is determined that the ECP node has sufficient resources to deploy the capability, the capability image is sent to the ECP node so that the ECP node deploys the capability, thereby avoiding the problem that the ECA on the ECP needs to call the capability that is not available locally across the ECP, and the frequent cross-node calls that may cause a large amount of link bandwidth waste and fail to better meet the user's service quality, thereby ensuring the service quality and saving bandwidth resources. When it is determined that the ECP node does not have sufficient resources to deploy the capability, the process ends.

[0136] Optionally, in a case where the first ECP node does not have a capability image corresponding to the first capability, sending the capability image or the capability image address corresponding to the first capability to the first ECP node includes:

[0137] In a case where the first ECP node does not have a capability image corresponding to the first capability, a first cost of the first ECP node invoking the first capability across nodes and a second cost of the first ECP node deploying the first capability are calculated; if the first cost is higher than the second cost, a capability image or a capability image address corresponding to the first capability is sent to the first ECP node.

[0138] For example: when the first ECP node does not have the capability image corresponding to the first capability, the deployment cost is calculated; when the cost of cross-node calls > the cost of local deployment, the capability can be deployed locally. The cost calculation depends on factors such as the business model, which can be: bandwidth cost > deployment resource cost: (average data volume * traffic unit price / peak * bandwidth unit price > resource purchase cost), etc.

[0139] Optionally, the sending the capability image or the capability image address corresponding to the first capability to the first ECP node includes:

[0140] When the edge computing service operation device has a capability image of the first capability and there is no ECP node having the capability image of the first capability, the edge computing service operation device sends the capability image or the capability image address corresponding to the first capability to the first ECP node;

[0141] In a case where a plurality of second ECP nodes have a capability image of the first capability, determining a target ECP node among the plurality of second ECP nodes that meets a preset condition, and sending the capability image of the first capability to the first ECP node through the target ECP node;

[0142] The second ECP node is an ECP node other than the first ECP node.

[0143] Optionally, determining a target ECP node that meets a preset condition among the plurality of second ECP nodes includes:

[0144] Determine a second ECP node among the multiple second ECP nodes that is closest to the first ECP node as the target ECP node; and / or determine a second ECP node among the multiple second ECP nodes that has the highest link quality with the first ECP node as the target ECP node.

[0145] For example: if the capability image only exists in the ECM image library, the image is sent from the ECM, the capability image source node is selected, and the capability is deployed (such as image sending, pulling up, and other lightweight communications (Lightweight Communications and Marshalling, LCM)); if the capability image exists in both the ECM and other ECP nodes, the capability image source node is selected (such as determined based on the calculation of link status, latency, etc.), and the capability is deployed (such as image sending, pulling up, and other LCM).

[0146] like Figure 2 As shown in the figure, a schematic diagram of the interaction between ECM and ECP nodes is given; ECM should include modules such as capability call monitoring module and capability deployment module. Among them, the capability call monitoring module is used for: statistics and analysis of call information, trigger scheme for automatic capability deployment, etc. The capability deployment module is used for: trigger scheme configuration, deployment strategy configuration, strategy activation, capability deployment strategy execution (judgment, issuance of deployment instructions, etc.). Each ECP can report capability call information, and ECM has global capability call status, node distribution status and other information.

[0147] Specifically, the ECP reports the capability call information, where the capability call information may include: the identifier of the ECP node; the identifier of the capability called by the ECA; the application identifier of the ECA; the call time corresponding to the capability called by the ECA; the identifier of whether the capability called by the ECA is successful; the number of calls corresponding to the first capability; the call frequency corresponding to the first capability; and the call data volume. For example, the call time can be used to indicate the sending time of the capability image, etc.

[0148] The capability call monitoring module of the ECM monitors the call data of the capability, and triggers the capability deployment judgment process under certain trigger conditions, and sends a capability deployment judgment request. The capability deployment judgment request may include: the node identifier (ID) of the calling node, the capability ID, the call metering information, etc. The capability call metering information includes: ECP node identifier, capability ID, application ID, call time, success / failure identifier, request data flow (including the number of calls, call data volume), etc.

[0149] Among them, the triggering condition for the capability delivery judgment may be: the number of calls> the first threshold and the call frequency> the second threshold, or the number of calls> the third threshold and the call data volume> the fourth threshold.

[0150] ECM determines whether the capability needs to be deployed locally and returns the judgment result: 1) If the local image exists but the capability is not pulled up, only a control signal is needed; 2) If the local image does not exist, it is necessary to determine whether the capability needs to be deployed; in the case where the required image is not available locally, if the capability needs to be deployed, the capability image or capability image address is sent according to the image source node selection principle. If the capability image is sent from ECM, the capability image is transmitted asynchronously. If the capability image is sent from other ECP nodes, the capability image address is returned, and the capability is deployed on the ECP node.

[0151] Specifically, Figure 3 As shown in the figure, the process of determining the execution of capability deployment is as follows:

[0152] Determine whether the local system has the capability to mirror; if so, directly send the mirror instantiation signaling; if not, proceed to resource judgment, that is, determine whether there are sufficient resources for capability deployment; if so, calculate the deployment cost; if not, the process ends.

[0153] When the cost of cross-node calls is greater than the cost of local deployment, the capability can be deployed locally. Cost calculation depends on factors such as the business model, which can be: bandwidth cost > deployment resource cost: (average data volume * traffic unit price / peak value * bandwidth unit price > resource purchase cost).

[0154] When the capability is determined to be deployed locally, select the capability image source node: if only the ECM has the image, it is sent from the ECM; if multiple nodes have the capability image, select the node that is closest and has the best link status to send it.

[0155] For example: ECM determines that the call frequency and number of calls of a certain capability on a specified node exceed the threshold, triggering the capability delivery judgment; discovers that the node has the capability image; and pulls up the image of the node.

[0156] Alternatively, ECM determines that the calling frequency and calling times of a certain capability on the node exceed the threshold, triggering the capability delivery judgment; the node does not have the capability image; determine whether the capability is delivered; if the image only exists in the ECM image library, deliver the image from ECM and select the capability image source node; deploy the capability (image delivery, pull-up, etc. LCM);

[0157] Alternatively, the ECM determines that the calling frequency and calling times of a certain capability on the node exceed the threshold, triggering the capability delivery judgment; the node does not have the capability image; determine whether the capability is delivered; if the image exists on both the ECM and other nodes, select the capability image source node (calculate link status, latency, etc.); deploy the capability (image delivery, pull up, etc. LCM);

[0158] Alternatively, ECM determines that the call frequency and number of calls of a certain capability in the area exceed the threshold, triggering the capability delivery judgment; the area does not have the capability image; determine whether the capability is delivered; select the capability image destination node; if the image exists in both ECM and other nodes, select the capability image source node; deploy the capability (image delivery, pull-up, etc. LCM), etc.

[0159] like Figure 4 As shown, the embodiment of the present invention further provides a capability deployment device 400, which is applied to an edge computing service operation device, including:

[0160] A capability call monitoring module 410 is used to receive capability call information sent by a first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node;

[0161] The capability distribution module 420 is configured to deploy the first capability on the first ECP node according to a preset policy when at least one ECA calls the first capability and the first ECP node does not support the first capability.

[0162] Optionally, the capability calling information includes at least one of the following:

[0163] an identifier of the first ECP node;

[0164] The identifier of the capability invoked by the ECA;

[0165] ECA application identification;

[0166] The calling time corresponding to the capability called by ECA;

[0167] An indicator of whether the capability called by ECA is successful;

[0168] The number of calls corresponding to the first capability;

[0169] a calling frequency corresponding to the first capability;

[0170] The amount of data to be called.

[0171] Optionally, the capability distribution module 420 includes:

[0172] A first processing submodule, configured to deploy the first capability on the first ECP node according to a preset strategy when the capability call information includes the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, if the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold;

[0173] or,

[0174] The second processing submodule is used for deploying the first capability on the first ECP node according to a preset strategy when the capability call information includes the number of calls corresponding to the first capability and the amount of call data, and when the number of calls corresponding to the first capability is greater than a third threshold and the amount of call data is greater than a fourth threshold.

[0175] Optionally, the capability distribution module 420 includes:

[0176] A first distribution submodule, configured to send a control signaling to the first ECP node when the first ECP node has a capability image corresponding to the first capability; wherein the control signaling is used to instruct the first ECP node to pull the capability image corresponding to the first capability;

[0177] The second distribution submodule is configured to send the capability image or the capability image address corresponding to the first capability to the first ECP node when the first ECP node does not have the capability image corresponding to the first capability.

[0178] Optionally, the second distribution submodule includes:

[0179] a judging unit, configured to judge whether there are sufficient resources to deploy the first capability if the first ECP node does not have a capability image corresponding to the first capability;

[0180] The first distribution unit is configured to send a capability image or a capability image address corresponding to the first capability to the first ECP node when there are sufficient resources to deploy the first capability.

[0181] Optionally, the second distribution submodule includes:

[0182] A calculation unit, configured to calculate a first cost of the first ECP node invoking the first capability across nodes and a second cost of the first ECP node deploying the first capability when the first ECP node does not have a capability image corresponding to the first capability;

[0183] The second distribution unit is configured to send the capability image or the capability image address corresponding to the first capability to the first ECP node if the first cost is higher than the second cost.

[0184] Optionally, the capability distribution module 420 includes:

[0185] A first distribution subunit is configured to, when the edge computing service operation device has a capability image of the first capability and there is no ECP node having the capability image of the first capability, send the capability image or the capability image address corresponding to the first capability to the first ECP node by the edge computing service operation device;

[0186] a second distribution subunit, configured to determine, when a plurality of second ECP nodes have a capability image of the first capability, a target ECP node that meets a preset condition among the plurality of second ECP nodes, and send the capability image of the first capability to the first ECP node through the target ECP node;

[0187] The second ECP node is an ECP node other than the first ECP node.

[0188] Optionally, the second distribution subunit is further used for:

[0189] Determine a second ECP node among the plurality of second ECP nodes that is closest to the first ECP node as the target ECP node;

[0190] and / or,

[0191] A second ECP node among the plurality of second ECP nodes having the highest link quality with the first ECP node is determined as the target ECP node.

[0192] The capability deployment device in the embodiment of the present invention can implement each process of the above-mentioned capability deployment method and can achieve the same technical effect. To avoid repetition, it will not be described here.

[0193] like Figure 5 As shown, an edge computing service operation device 500 according to an embodiment of the present invention includes: a transceiver 510 and a processor 520;

[0194] The transceiver 510 is used to: receive capability call information sent by the first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node;

[0195] The processor 520 is configured to deploy the first capability on the first ECP node according to a preset policy when at least one ECA invokes the first capability and the first ECP node does not support the first capability.

[0196] Optionally, the capability calling information includes at least one of the following:

[0197] an identifier of the first ECP node;

[0198] The identifier of the capability invoked by the ECA;

[0199] ECA application identification;

[0200] The calling time corresponding to the capability called by ECA;

[0201] An indicator of whether the capability called by ECA is successful;

[0202] The number of calls corresponding to the first capability;

[0203] a calling frequency corresponding to the first capability;

[0204] The amount of data to be called.

[0205] Optionally, the processor 520 is configured to: when the capability call information includes: the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, when the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold, deploy the first capability on the first ECP node according to a preset strategy;

[0206] or,

[0207] The processor 520 is used for: when the capability call information includes: the number of calls corresponding to the first capability and the amount of call data, when the number of calls corresponding to the first capability is greater than a third threshold, and the amount of call data is greater than a fourth threshold, deploying the first capability on the first ECP node according to a preset strategy.

[0208] Optionally, the transceiver 510 is used for:

[0209] In a case where the first ECP node has a capability image corresponding to the first capability, sending a control signaling to the first ECP node; wherein the control signaling is used to instruct the first ECP node to pull the capability image corresponding to the first capability;

[0210] In a case where the first ECP node does not have a capability image corresponding to the first capability, the capability image or the capability image address corresponding to the first capability is sent to the first ECP node.

[0211] Optionally, the processor 520 is configured to: if the first ECP node does not have a capability image corresponding to the first capability, determine whether there are sufficient resources to deploy the first capability;

[0212] The transceiver 510 is configured to: when there are sufficient resources to deploy the first capability, send the capability image or the capability image address corresponding to the first capability to the first ECP node.

[0213] Optionally, the processor 520 is configured to: when the first ECP node does not have a capability image corresponding to the first capability, calculate a first cost of the first ECP node invoking the first capability across nodes and a second cost of the first ECP node deploying the first capability;

[0214] The transceiver 510 is configured to: if the first cost is higher than the second cost, send a capability image or a capability image address corresponding to the first capability to the first ECP node.

[0215] Optionally, the transceiver 510 is used for:

[0216] When the edge computing service operation device has a capability image of the first capability and there is no ECP node having the capability image of the first capability, sending the capability image or the capability image address corresponding to the first capability to the first ECP node;

[0217] In a case where a plurality of second ECP nodes have a capability image of the first capability, determining a target ECP node among the plurality of second ECP nodes that meets a preset condition, and sending the capability image of the first capability to the first ECP node through the target ECP node;

[0218] The second ECP node is an ECP node other than the first ECP node.

[0219] Optionally, the processor 520 is configured to:

[0220] Determine a second ECP node among the plurality of second ECP nodes that is closest to the first ECP node as the target ECP node;

[0221] and / or,

[0222] A second ECP node among the plurality of second ECP nodes having the highest link quality with the first ECP node is determined as the target ECP node.

[0223] The edge computing business operation device in the embodiment of the present invention can implement each process of the above-mentioned capability deployment method and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0224] An edge computing service operation device according to another embodiment of the present invention is Figure 6As shown, it includes a transceiver 610, a processor 600, a memory 620, and a program or instruction stored in the memory 620 and executable on the processor 600; when the processor 600 executes the program or instruction, the steps in the above-mentioned capability deployment method are implemented, and to avoid repetition, they are not repeated here.

[0225] The transceiver 610 is used to receive and send data under the control of the processor 600 .

[0226] Among them, Figure 6 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 610 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 when performing operations.

[0227] A readable storage medium according to an embodiment of the present invention stores a program or instruction thereon. When the program or instruction is executed by a processor, the steps in the capability deployment method described above are implemented and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0228] The processor is a processor in the edge computing service operation device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0229] It should be further explained that the terminals described in this specification include but are not limited to smart phones, tablet computers, etc., and many of the functional components described are called modules in order to more particularly emphasize the independence of their implementation methods.

[0230] In the embodiment of the present invention, module can be implemented with software so that it can be executed by various types of processors. For example, an executable code module of an identification can include one or more physical or logical blocks of computer instructions, for example, it can be constructed as an object, process or function. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different positions, and when these instructions are logically combined together, it constitutes a module and realizes the specified purpose of the module.

[0231] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed among different programs, and distributed across a plurality of memory devices. Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form. The operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0232] When a module can be implemented by software, considering the level of existing hardware technology, a person skilled in the art can build a corresponding hardware circuit to implement the corresponding function of the module that can be implemented by software without considering the cost. The hardware circuit includes a conventional very large scale integration (VLSI) circuit or gate array and existing semiconductors such as logic chips, transistors, or other discrete components. The module can also be implemented by a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0233] The above exemplary embodiments are described with reference to the accompanying drawings, and many different forms and embodiments are feasible without departing from the spirit and teachings of the present invention. Therefore, the present invention should not be constructed as a limitation of the exemplary embodiments proposed herein. More specifically, these exemplary embodiments are provided so that the present invention will be perfect and complete, and the scope of the present invention will be conveyed to those who are familiar with the technology. In these figures, the component sizes and relative sizes may be exaggerated for clarity. The terms used here are only based on the purpose of describing specific exemplary embodiments and are not intended to be limiting. As used herein, unless the text clearly indicates otherwise, the singular forms "one", "an" and "the" are intended to include these multiple forms. It will be further understood that the terms "including" and / or "comprising" when used in this specification indicate the presence of the features, integers, steps, operations, components and / or components, but do not exclude the presence or increase of one or more other features, integers, steps, operations, components, components and / or their groups. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

[0234] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A capability deployment method, applied to edge computing service operation equipment, characterized in that: The method comprises: Receive capability call information sent by a first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node; When at least one ECA calls a first capability and the first ECP node does not support the first capability, deploying the first capability on the first ECP node according to a preset policy; Wherein, in a case where the capability call information includes: the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, the deploying the first capability on the first ECP node according to a preset strategy includes: When the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold, deploying the first capability on the first ECP node according to a preset policy; or, In a case where the capability call information includes: the number of calls and the amount of call data corresponding to the first capability, the deploying the first capability on the first ECP node according to a preset strategy includes: When the number of calls corresponding to the first capability is greater than a third threshold and the amount of call data is greater than a fourth threshold, the first capability is deployed on the first ECP node according to a preset strategy.

2. The capability deployment method according to claim 1, characterized in that: The capability call information includes at least one of the following: an identifier of the first ECP node; The identifier of the capability invoked by the ECA; ECA application identification; The calling time corresponding to the capability called by ECA; An indicator of whether the capability called by ECA is successful; The number of calls corresponding to the first capability; a calling frequency corresponding to the first capability; The amount of data to be called.

3. The capability deployment method according to claim 1, characterized in that: The deploying the first capability on the first ECP node according to a preset strategy includes: In a case where the first ECP node has a capability image corresponding to the first capability, sending a control signaling to the first ECP node; wherein the control signaling is used to instruct the first ECP node to pull the capability image corresponding to the first capability; In a case where the first ECP node does not have a capability image corresponding to the first capability, the capability image or the capability image address corresponding to the first capability is sent to the first ECP node.

4. The capability deployment method according to claim 3, characterized in that: The sending the capability image or the capability image address corresponding to the first capability to the first ECP node when the first ECP node does not have the capability image corresponding to the first capability includes: If the first ECP node does not have a capability image corresponding to the first capability, determining whether there are sufficient resources to deploy the first capability; In a case where there are sufficient resources to deploy the first capability, a capability image or a capability image address corresponding to the first capability is sent to the first ECP node.

5. The capability deployment method according to claim 3, characterized in that: The step of sending the capability image or the capability image address corresponding to the first capability to the first ECP node when the first ECP node does not have the capability image corresponding to the first capability includes: If the first ECP node does not have a capability image corresponding to the first capability, calculating a first cost of the first ECP node invoking the first capability across nodes and a second cost of the first ECP node deploying the first capability; If the first cost is higher than the second cost, sending the capability image or the capability image address corresponding to the first capability to the first ECP node.

6. The capability deployment method according to any one of claims 3 to 5, characterized in that: The sending the capability image or the capability image address corresponding to the first capability to the first ECP node includes: When the edge computing service operation device has a capability image of the first capability and there is no ECP node having the capability image of the first capability, the edge computing service operation device sends the capability image or the capability image address corresponding to the first capability to the first ECP node; In a case where a plurality of second ECP nodes have a capability image of the first capability, determining a target ECP node among the plurality of second ECP nodes that meets a preset condition, and sending the capability image of the first capability or the capability image address to the first ECP node through the target ECP node; The second ECP node is an ECP node other than the first ECP node.

7. The capability deployment method according to claim 6, characterized in that: Determining a target ECP node that meets a preset condition among the plurality of second ECP nodes includes: Determine a second ECP node among the plurality of second ECP nodes that is closest to the first ECP node as the target ECP node; and / or, A second ECP node among the plurality of second ECP nodes having the highest link quality with the first ECP node is determined as the target ECP node.

8. A capability deployment device, applied to edge computing service operation equipment, characterized in that: include: A capability call monitoring module is used to receive capability call information sent by a first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node; a capability distribution module, configured to deploy the first capability on the first ECP node according to a preset policy when at least one ECA calls the first capability and the first ECP node does not support the first capability; Wherein, the capability distribution module includes: A first processing submodule, configured to deploy the first capability on the first ECP node according to a preset strategy when the capability call information includes the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, if the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold; or, The second processing submodule is used for deploying the first capability on the first ECP node according to a preset strategy when the capability call information includes the number of calls and the amount of call data corresponding to the first capability, and when the number of calls corresponding to the first capability is greater than a third threshold and the amount of call data is greater than a fourth threshold.

9. An edge computing service operation device, characterized in that: include: transceivers and processors; The transceiver is used to: receive capability call information sent by the first edge computing platform ECP node; wherein the capability call information is used to indicate relevant information of the capability called by the edge computing application ECA on the first ECP node; The processor is configured to deploy the first capability on the first ECP node according to a preset policy when at least one ECA calls the first capability and the first ECP node does not support the first capability; The processor is configured to: when the capability call information includes the number of calls corresponding to the first capability and the call frequency corresponding to the first capability, when the number of calls corresponding to the first capability is greater than a first threshold, and the call frequency corresponding to the first capability is greater than a second threshold, deploy the first capability on the first ECP node according to a preset strategy; or, The processor is used for: when the capability call information includes: the number of calls and the amount of call data corresponding to the first capability, when the number of calls corresponding to the first capability is greater than a third threshold, and the amount of call data is greater than a fourth threshold, deploying the first capability on the first ECP node according to a preset strategy.

10. An edge computing service operation device, comprising: A transceiver, a processor, a memory, and a program or instruction stored in the memory and executable on the processor; characterized in that when the processor executes the program or instruction, the steps of the capability deployment method as described in any one of claims 1 to 7 are implemented.

11. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or instruction is executed by a processor, the steps of the capability deployment method according to any one of claims 1 to 7 are implemented.

Images