Capability Invocation Method, Device, Network Node, and Storage Medium

Abstract

The present application discloses a method, apparatus, network node and storage medium for capability invocation. The method includes: a first network node determines, based on at least one set dimension, the capability grading corresponding to a first capability on each of at least two second network nodes; wherein the first capability is deployed on the at least two second network nodes; and a third network node subscribes to and invokes the first capability corresponding to the first capability grading.

Description

Technical Field

[0001] This application relates to the field of network technologies, and in particular, to a method and apparatus for capability invocation, a network node, and a storage medium. Background Art

[0002] With the development and deployment of edge computing, an increasing number of network capabilities are being deployed at the network edge, including wireless positioning capabilities, user identification, bandwidth management capabilities, Radio Network Information Services (RNIS), traffic splitting capabilities, cloud gaming, video encoding and decoding, etc., and these network capabilities are gradually opened for use by the operator's own applications or third-party applications. When an application needs to use a network capability, it needs to submit a capability subscription application to the management platform and can perform capability invocation only after the subscription is completed.

[0003] In related technologies, there is a problem that the invoked network capabilities cannot match the business requirements of the application. Summary of the Invention

[0004] To solve the problems in related technologies, embodiments of this application provide a method and apparatus for capability invocation, a network node, and a storage medium.

[0005] The technical solution of the embodiments of this application is implemented as follows:

[0006] Embodiments of this application provide a method for capability invocation, which is applied to a first network node; the method includes:

[0007] Based on at least one set dimension, determine the capability grading corresponding to a first capability on each of at least two second network nodes; where

[0008] The first capability is deployed on the at least two second network nodes; a third network node subscribes to and invokes the first capability corresponding to the first capability grading.

[0009] Wherein, in one embodiment, when the first capability is a network capability, the at least one set dimension includes at least one of the following:

[0010] The network distance between the corresponding second network node and the wireless side;

[0011] The access capacity of the corresponding second network node for the first capability;

[0012] The response latency of the corresponding second network node for the first capability;

[0013] The performance of the first capability deployed on the corresponding second network node.

[0014] In one embodiment, determining the capability classification corresponding to the first capability on each of at least two second network nodes based on at least one set dimension includes:

[0015] When registering the first capability, determining the capability classification corresponding to the first capability on each of the at least two second network nodes based on the at least one set dimension.

[0016] In one embodiment, the method further includes:

[0017] Sending first information to the third network node and each of the at least two second network nodes; wherein,

[0018] The first information represents the capability classification corresponding to the first capability on each of the at least two second network nodes.

[0019] In one embodiment, the method further includes:

[0020] Saving second information and sending the second information to each of the at least two second network nodes; wherein,

[0021] The second information represents the network capabilities ordered by the third network node and the corresponding ordered capability classifications.

[0022] In one embodiment, the method further includes:

[0023] Receiving a first request from the third network node; the first request is used to request to invoke the first capability;

[0024] After confirming that the third network node has ordered the first capability corresponding to the first capability classification, generating a first list; the first list includes at least one of the at least two second network nodes, and the capability classification corresponding to the first capability on the second network node in the first list is the first capability classification;

[0025] Returning third information to the third network node based on the first list; the third information indicates a second network node in the first list, so that the third network node sends the first request to the second network node indicated by the third information.

[0026] In one embodiment, generating the first list includes:

[0027] Generating the first list based on the distance between the second network node and the third network node.

[0028] In one embodiment, the method further includes:

[0029] Determine the third information based on at least one real-time performance parameter of each second network node in the first list;

[0030] The at least one real-time performance parameter includes at least one of the following:

[0031] Occupancy rate;

[0032] Response latency;

[0033] Uplink rate or downlink rate.

[0034] An embodiment of the present application further provides a capability invocation method, which is applied to any one of at least two second network nodes; a first capability is deployed on each of the at least two second network nodes; the method includes:

[0035] Receive the first information sent by the first network node;

[0036] Determine the corresponding capability level based on the first information; wherein,

[0037] The first information represents the capability level corresponding to the first capability on each of the at least two second network nodes determined by the first network node based on at least one set dimension.

[0038] Wherein, in one embodiment, the method further includes:

[0039] Receive the first request sent by the third network node; the first request is used to request to invoke the first capability;

[0040] Invoke the first capability corresponding to the first capability level for the third network node based on the first request; wherein,

[0041] The first request is sent by the third network node when it confirms that the first capability of the first capability level is deployed on the second network node.

[0042] In one embodiment, the method further includes:

[0043] Receive the second information sent by the first network node; the second information represents the network capabilities subscribed by the third network node and the corresponding capability levels;

[0044] The invoking the first capability corresponding to the first capability level for the third network node based on the first request includes:

[0045] After confirming that the third network node subscribes to the first capability corresponding to the first capability classification based on the second information, call the first capability corresponding to the first capability classification for the third network node based on the first request.

[0046] An embodiment of the present application also provides a capability invocation method, which is applied to a third network node. The method includes:

[0047] Subscribe to the first capability corresponding to the first capability classification from the first network node; where

[0048] The first capability is deployed on at least two second network nodes; the capability classification corresponding to the first capability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension.

[0049] In one embodiment, it further includes:

[0050] Receive the first information sent by the first network node; the first information represents the capability classification corresponding to the first capability on each of the at least two second network nodes;

[0051] Send a first request to the corresponding network node based on the first information; the first request is used to request to invoke the first capability.

[0052] In one embodiment, the sending the first request to the corresponding network node based on the first information includes:

[0053] When the first information indicates that the first capability corresponding to the first capability classification is deployed on the fourth network node, send the first request to the fourth network node; the fourth network node represents the network node accessed by the third network node;

[0054] When the first information indicates that the first capability corresponding to the first capability classification is not deployed on the fourth network node, send the first request to the first network node, receive the third information returned by the first network node, and send the first request to the second network node indicated by the third information; where

[0055] One second network node in the first list is indicated in the third information; the first list includes at least one second network node among the at least two second network nodes, and the capability classification corresponding to the first capability on the second network node in the first list matches the first capability classification.

[0056] An embodiment of the present application also provides a capability invocation device, including:

[0057] A first determination unit, configured to determine, based on at least one set dimension, the ability grading corresponding to the first ability on each of at least two second network nodes; wherein,

[0058] The first ability is deployed on the at least two second network nodes; a third network node subscribes to and invokes the first ability corresponding to the first ability grading.

[0059] An embodiment of the present application further provides an ability invocation device, including:

[0060] A first receiving unit, configured to receive first information sent by a first network node;

[0061] A second determination unit, configured to determine the corresponding ability grading based on the first information; wherein,

[0062] The first ability is deployed on each of at least two second network nodes; the first information represents the ability grading corresponding to the first ability on each of the at least two second network nodes determined by the first network node based on at least one set dimension.

[0063] An embodiment of the present application further provides an ability invocation device, including:

[0064] A subscription unit, configured to subscribe to the first ability corresponding to the first ability grading from the first network node; wherein,

[0065] The first network ability is deployed on at least two second network nodes; the ability grading corresponding to the first network ability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension.

[0066] An embodiment of the present application further provides a first network node, including: a first processor and a first communication interface; wherein,

[0067] The first processor is configured to determine, based on at least one set dimension, the ability grading corresponding to the first ability on each of at least two second network nodes; wherein,

[0068] The first ability is deployed on the at least two second network nodes; a third network node subscribes to and invokes the first ability corresponding to the first ability grading.

[0069] An embodiment of the present application further provides a second network node, including: a second processor and a second communication interface; wherein,

[0070] The second communication interface is configured to receive first information sent by the first network node;

[0071] The second processor is configured to determine a corresponding capability level based on the first information; wherein,

[0072] A first capability is deployed on each of at least two second network nodes; the first information represents the capability level corresponding to the first capability on each of the at least two second network nodes, determined by the first network node based on at least one set dimension.

[0073] An embodiment of the present application further provides a third network node, including: a third processor and a third communication interface; wherein,

[0074] The third communication interface is configured to order the first capability corresponding to the first capability level from the first network node; wherein,

[0075] The first capability is deployed on at least two second network nodes; the capability level corresponding to the first capability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension.

[0076] An embodiment of the present application further provides a first network node, including: a first processor and a first memory for storing a computer program that can run on the processor,

[0077] Wherein, when the first processor is used to run the computer program, it executes the steps of any of the methods on the first network node side.

[0078] An embodiment of the present application further provides a second network node, including: a second processor and a second memory for storing a computer program that can run on the processor,

[0079] Wherein, when the second processor is used to run the computer program, it executes the steps of any of the methods on the second network node side.

[0080] An embodiment of the present application further provides a third network node, including: a third processor and a third memory for storing a computer program that can run on the processor,

[0081] Wherein, when the third processor is used to run the computer program, it executes the steps of any of the methods on the third network node side.

[0082] An embodiment of the present application further provides a storage medium, on which a computer program is stored, characterized in that when the computer program is executed by a processor, it implements the steps of any of the above methods.

[0083] The network capability invocation method, apparatus, network node, and storage medium provided by the embodiments of the present application. Among them, the first capability is deployed on at least two second network nodes. The first network node determines the capability grading corresponding to the first capability on each of the at least two second network nodes based on at least one set dimension; based on the capability grading of the first capability by the first network node, the third network node subscribes to and invokes the first capability corresponding to the first capability grading, thereby realizing differentiated capability subscription and invocation, and ensuring the matching of the invoked capability and the business requirements of the application. Description of the Drawings

[0084] Figure 1 It is a schematic flowchart of a capability invocation method according to an embodiment of the present application;

[0085] Figure 2 It is a schematic flowchart of a network capability registration process according to an application embodiment of the present application;

[0086] Figure 3 It is a schematic flowchart of another capability invocation method according to an embodiment of the present application;

[0087] Figure 4 It is a schematic flowchart of another capability invocation method according to an embodiment of the present application;

[0088] Figure 5 It is a schematic flowchart of a network capability invocation process according to an application embodiment of the present application;

[0089] Figure 6 It is a schematic structural diagram of a capability invocation apparatus according to an embodiment of the present application;

[0090] Figure 7 It is a schematic structural diagram of another capability invocation apparatus according to an embodiment of the present application;

[0091] Figure 8 It is a schematic structural diagram of another capability invocation apparatus according to an embodiment of the present application;

[0092] Figure 9 It is a schematic structural diagram of a first network node according to an embodiment of the present application;

[0093] Figure 10 It is a schematic structural diagram of a second network node according to an embodiment of the present application;

[0094] Figure 11 It is a schematic structural diagram of a third network node according to an embodiment of the present application. Detailed Embodiments

[0095] When an application needs to use network capabilities, the application server needs to submit a capability subscription application to the management platform. Only after the subscription is completed can the capabilities be invoked. With the development and deployment of edge computing, the network capabilities deployed at the network edge are increasing. For the network capabilities deployed at the edge, in related technologies, on the one hand, different applications have different business requirements for the same network capability, but the operator does not consider how to evaluate the performance of the network capability and, based on this, implement capability grading for different business requirements. On the other hand, when providing network capabilities for an application, it is usually based on the distance between the application server and the deployment location of the network capability for proximity matching. Moreover, when the application server switches, it is also based on the principle of proximity matching, and the network capabilities to be invoked are not considered throughout whether they can meet the business requirements of the application. To sum up, there is a problem in related technologies that the invoked network capabilities do not match the business requirements of the application.

[0096] Based on this, the embodiments of the present application provide a capability invocation method, apparatus, network node, and storage medium. Among them, the first capability is deployed on at least two second network nodes. The first network node determines the capability grading corresponding to the first capability on each of the at least two second network nodes based on at least one set dimension. Based on the capability grading of the first capability by the first network node, the third network node subscribes to and invokes the first capability corresponding to the first capability grading, thereby realizing differential capability subscription and invocation and ensuring the matching of the invoked capabilities with the business requirements of the application.

[0097] The following further describes the present application in detail with reference to the accompanying drawings and embodiments. It should be noted that in the embodiments of the present application, the capability can be a network capability deployed by the operator at the network edge, that is, an edge network capability, or a capability deployed by a third-party application at the network edge, such as a face recognition function, etc.

[0098] The embodiments of the present application provide a capability invocation method, which is applied to a first network node. Here, the first network node is a management platform, also known as an edge capability management platform. As Figure 1 shown, the method includes:

[0099] Step 101: Determine the capability grading corresponding to the first capability on each of the at least two second network nodes based on at least one set dimension.

[0100] Among them, the first capability is deployed on the at least two second network nodes; the third network node subscribes to and invokes the first capability corresponding to the first capability grading.

[0101] Exemplarily, the first capability may be network capabilities such as wireless positioning capability, user identification, bandwidth management capability, RNIS, traffic splitting capability, cloud gaming, video encoding and decoding, etc., and may also be functions such as face recognition deployed by third-party applications. The second network node is a network node where the first capability is deployed, usually each mobile edge computing (MEC) platform. In actual applications, the second network node may be each application programming interface (API) gateway (GW) located at the network edge. The first network node, as a management platform for capabilities, determines the capability grading corresponding to the first capability on each second network node. Based on the determined capability grading, the first capability corresponding to different capability gradings can be provided to applications differentially. In this way, when the third network node, i.e., the application server, subscribes to the first capability from the first network node, it can subscribe to the first capability corresponding to the first capability grading according to the capability grading of the first capability and call the first capability corresponding to the first capability grading.

[0102] In one embodiment, when the first capability is a network capability, the at least one set dimension includes at least one of the following:

[0103] The location of the corresponding second network node;

[0104] The access capacity of the corresponding second network node for the first capability;

[0105] The response latency of the corresponding second network node for the first capability;

[0106] The performance of the first capability deployed on the corresponding second network node.

[0107] Among them, the location is the deployment location of the second network node in the network, which can represent the network distance between the second network node and the wireless side; the access capacity and response latency depend on the second network node itself, for example, depending on the performance of the API GW or the resources of the configured edge compute platform (ECP). The performance of the first capability depends on the performance of the first capability deployed on the second network node. For example, there are different requirements for the positioning accuracy of the wireless positioning capability, and the positioning accuracies of the wireless positioning capabilities deployed on different second network nodes are different. Combining the above at least one set dimension, the first network platform can determine the capability grading corresponding to the first capability on each second network node.

[0108] In actual applications, a capability grading function can be added to the first network node. When registering a capability in the management platform, the first network node grades the capability and stores the corresponding grading results.

[0109] Based on this, in one embodiment, determining the capability grading corresponding to the first capability on each of the at least two second network nodes based on at least one set dimension includes:

[0110] When registering the first capability, based on the at least one set dimension, determine the capability grading corresponding to the first capability on each of the at least two second network nodes.

[0111] In one embodiment, the method further includes:

[0112] Sending the first information to the third network node and each of the at least two second network nodes; wherein,

[0113] The first information represents the capability grading corresponding to the first capability on each of the at least two second network nodes.

[0114] In this way, the third network node can initiate a request to the corresponding network node based on the first information to invoke the first capability, and the second network node can determine the capability grading corresponding to the first capability deployed locally at the second network node based on the first information.

[0115] Figure 2 Fig. shows a schematic diagram of the network capability registration process provided by the application embodiment of the present application. Referring to Figure 2 , the process of registering network capabilities includes:

[0116] Step 1: Send a registration request carrying capability information to the edge capability management platform (i.e., the first network node) to request registration of the corresponding network capability.

[0117] Step 2: The edge capability management platform determines the capability grading corresponding to the network capability on each deployed API GW (i.e., the second network node) according to at least one set dimension, and stores the grading information.

[0118] Here, in addition to storing the registration information of the network capability, such as the capability identifier, the edge capability management platform also newly stores the grading information of the network capability.

[0119] Step 3: The edge capability management platform sends a capability registration success message to each API GW, and carries the grading information in the sent capability registration success message.

[0120] Step 4: Each API GW maintains relevant information of the network capability locally based on the sent grading information, including the grading information corresponding to the network capability deployed locally at each API GW.

[0121] Table 1 shows the hierarchical information stored in the first network node. It can be seen from Table 1 that Network Capability 1 is deployed on both API GW1 and APIGW 2, and the deployed Network Capability 1 corresponds to the capability level of Level 1. In addition, Network Capability 2 is also deployed on API GW1, corresponding to the capability level of Level 2.

[0122] Table 1

[0123] Capability Identifier Deployment Location Classification Information Capability 1 API GW1 Level 1 Capability 1 API GW2 Level 1 Capability 2 API GW1 Level 2

[0124] Table 2 shows the hierarchical information stored in API GW 1. This hierarchical information is determined by API GW 1 based on the first information sent by the management platform and is related to the network capabilities deployed on API GW 1, including Network Capability 1 corresponding to the capability level of Level 1 and Network Capability 2 corresponding to the capability level of Level 2 deployed on API GW 1. Moreover, the specific deployment paths of each network capability on API GW 1 are recorded at the corresponding deployment locations.

[0125] Table 2

[0126] Capability Identifier Deployment Location Classification Information Capability 1 API GW 1.xx Level 1 Capability 2 API GW 2.xxx Level 2

[0127] After implementing the hierarchical classification of the first capability, when the third network node subscribes to the first capability, it can specifically subscribe to a capability level of the first capability. At the same time, when the first network node stores the capability subscription record of the third network node, in addition to storing the capability subscribed by the third network node, it also needs to store the capability level subscribed by the third network node, and send this capability subscription record to each of the second network nodes for subsequent capability invocation by the third network node.

[0128] Based on this, in one embodiment, the method further includes:

[0129] Saving the second information and sending the second information to each of the at least two second network nodes; wherein,

[0130] The second information represents the capability subscribed by the third network node and the corresponding subscribed capability level.

[0131] Here, when the first network node or any one of the second network nodes receives a request sent by the third network node for invoking the first capability, it confirms that the third network node has subscribed to the first capability based on the second information, and further confirms the capability level of the first capability subscribed by the third network node based on the second information. On this basis, it invokes the first capability of the corresponding capability level for the third network node.

[0132] Table 3 shows the second information sent by the first network node, from which it can be confirmed that both Application 1 and Application 2 have subscribed to Capability 1 corresponding to Capability Classification 1.

[0133] Table 3

[0134] Application Information Capability Subscription Information Application 1 Capability 1 - Level 1 Application 2 Capability 1 - Level 1

[0135] In one embodiment, the method further includes:

[0136] Receiving a first request from the third network node; the first request is used to request to invoke a first capability;

[0137] After confirming that the third network node has subscribed to the first capability corresponding to the first capability classification, generating a first list; the first list includes at least one of the at least two second network nodes, and the capability classification of the first capability on the second network node in the first list is the first capability classification;

[0138] Returning third information to the third network node based on the first list; the third information indicates one of the second network nodes in the first list, so that the third network node sends the first request to the second network node indicated by the third information.

[0139] When the third network node invokes the first capability, first, based on the first information sent by the first network node, it is confirmed whether the first capability corresponding to the first capability classification is deployed locally, that is, whether the first capability corresponding to the first capability classification is deployed on the API GW accessed by the third network node as an application server. When the first information indicates that the first capability corresponding to the first capability classification is not deployed locally, the third network node sends a first request to the first network node. After the first network node confirms that the third network node has subscribed to the first capability corresponding to the first capability classification based on the second information, it determines the second network node on which the first capability corresponding to the first capability classification is deployed based on the first information, and generates a first list based on the determined second network node.

[0140] In one embodiment, the generating of the first list includes:

[0141] Generating the first list based on the distance between the second network node and the third network node.

[0142] In actual application, when generating the first list, the first network node needs to consider the distance between the second network node and the third network node at the same time, and try to ensure that the distance between the second network node and the third network node in the first list is within a suitable range, so as to more quickly invoke the first capability.

[0143] In one embodiment, the method further includes:

[0144] Determine the third information based on at least one real-time performance parameter of each second network node in the first list;

[0145] The at least one real-time performance parameter includes at least one of the following:

[0146] Occupancy rate;

[0147] Response latency;

[0148] Uplink rate or downlink rate.

[0149] Here, when selecting a second network node for the third network node in the first list, the real-time status information of the second network node is combined. In the case where the provided first capabilities all correspond to the first capability grading, the second network node with the best real-time status is selected to ensure that the selected second network node can provide the optimal first capability for the third network node.

[0150] In practical applications, a corresponding functional module can be deployed on the first network node. This functional module implements the functions of the edge scheduling center, receives the first list from the management platform, obtains the real-time status of each second network node in the first list, and feeds back the obtained real-time status to the management platform.

[0151] Correspondingly, an embodiment of the present application further provides a capability invocation method, which is applied to any one of at least two second network nodes; the first capability is deployed on each of the at least two second network nodes. As Figure 3 shown, the method includes:

[0152] Step 301: Receive the first information sent by the first network node.

[0153] Step 302: Determine the corresponding capability grading based on the first information.

[0154] Wherein, the first information represents the capability grading corresponding to the first capability on each of the at least two second network nodes determined by the first network node based on at least one set dimension.

[0155] Here, the second network node can be each API GW located at the network edge. The first network node, as the management platform of capabilities, determines the capability grading corresponding to the first capability on each second network node. The second network node receives the first information sent by the first network node and determines the capability grading corresponding to the first capability deployed locally on the second network node from it. Based on the determined capability grading, the first capability corresponding to different capability gradings can be provided for the application differently. In this way, when the third network node, i.e., the application server, subscribes to the first capability from the first network node, it can subscribe to the first capability corresponding to the first capability grading according to the capability grading of the first capability and call the first capability corresponding to the first capability grading.

[0156] In one embodiment, the method further includes:

[0157] Receiving a first request sent by the third network node; the first request is used to request to call the first capability;

[0158] Based on the first request, calling the first capability corresponding to the first capability grading for the third network node; wherein,

[0159] The first request is sent by the third network node when it confirms that the first capability of the first capability grading is deployed on the second network node.

[0160] In actual application, when the third network node confirms that the first capability of the first capability grading is deployed on the second network node, it sends a first request to the second network node and calls the first capability corresponding to the first capability grading based on the first request. Here, the second network node that receives the first request can be the network node accessed by the third network node or other second network nodes.

[0161] In one embodiment, the method further includes:

[0162] Receiving second information sent by the first network node; the second information represents the capabilities subscribed by the third network node and the corresponding capability gradings;

[0163] The calling the first capability corresponding to the first capability grading for the third network node based on the first request includes:

[0164] After confirming that the third network node subscribes to the first capability of the first capability grading based on the second information, calling the first capability corresponding to the first capability grading for the third network node based on the first request.

[0165] After receiving a first request sent by a third network node, the second network node, after confirming based on the second information that the third network node subscribes to a first capability corresponding to the first capability classification, invokes, based on the first request, the first capability corresponding to the first capability classification for the third network node.

[0166] Correspondingly, an embodiment of the present application further provides a capability invocation method, which is applied to a third network node. In actual application, the third network node is an application server. As Figure 4 shown, this method includes:

[0167] Step 401: Subscribe to a first capability corresponding to a first capability classification from a first network node.

[0168] Among them, the first capability is deployed on at least two second network nodes; the capability classification corresponding to the first capability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension.

[0169] Exemplarily, the first capability may be network capabilities such as wireless positioning capability, user identification, bandwidth management capability, RNIS, traffic splitting capability, cloud gaming, video encoding and decoding, etc., and may also be functions provided by third-party applications such as face recognition. The second network node is a network node on which the first capability is deployed, usually each MEC platform. In actual application, the second network node may be each API GW located at the network edge. The first network node, as a capability management platform, determines the capability classification corresponding to the first capability on each second network node. Based on the determined capability classification, it can provide the first capability corresponding to different capability classifications for applications differentially. In this way, when the third network node, that is, the application server subscribes to the first capability from the first network node, it can subscribe to the first capability corresponding to the first capability classification according to the capability classification of the first capability and invoke the first capability corresponding to the first capability classification.

[0170] In one embodiment, the method further includes:

[0171] Receiving first information sent by the first network node; the first information represents the capability classification corresponding to the first capability on each of the at least two second network nodes;

[0172] Sending a first request to a corresponding network node based on the first information; the first request is used to request to invoke the first capability.

[0173] When a third network node invokes a first capability, it first determines whether the first capability corresponding to the first capability level is deployed locally based on the first information sent by the first network node, that is, whether the first capability corresponding to the first capability level is deployed on the API GW accessed by the third network node as an application server. When the first information indicates that the first capability corresponding to the first capability level is not deployed locally, the third network node sends a first request to the first network node. After the first network node confirms that the third network node subscribes to the first capability corresponding to the first capability level based on the second information, it determines a second network node that deploys the first capability corresponding to the first capability level based on the first information, and generates a first list based on the determined second network node.

[0174] Based on this, in one embodiment, the sending the first request to the corresponding network node based on the first information includes:

[0175] When the first information indicates that the first capability corresponding to the first capability level is deployed on a fourth network node, sending the first request to the fourth network node; the fourth network node represents a network node that accesses the same local area network as the third network node;

[0176] When the first information indicates that the first capability corresponding to the first capability level is not deployed on the fourth network node, sending the first request to the first network node, receiving the third information returned by the first network node, and sending the first request to the second network node indicated by the third information; wherein,

[0177] One second network node in the first list is indicated in the third information; the first list includes at least one second network node among the at least two second network nodes, and the capability level of the first capability corresponding to the second network node in the first list matches the first capability level.

[0178] In practical applications, when generating the first list, the first network node needs to consider the distance between the second network node and the third network node at the same time, and try to ensure that the distance between the second network node and the third network node appearing in the first list is within a suitable range, so as to call the first capability more quickly. And when selecting a second network node for the third network node in the first list, the real-time status information of the second network node is combined. When the provided first capabilities all correspond to the first capability level, the second network node with the best real-time status is selected to ensure that the selected second network node can provide the optimal first capability for the third network node.

[0179] Figure 5 Shows the schematic diagram of the network capability invocation process provided by the application embodiment of the present application. Refer toFigure 5 , the process of invoking network capabilities includes:

[0180] First, when the first network capability of the first capability level is deployed on the local API GW of the edge application (i.e., the third network node), steps a1 to a3 are executed.

[0181] Step a1: The edge application initiates a capability invocation request to the local API GW.

[0182] Step a2: The local API GW queries the capability subscription record to determine that the edge application has subscribed to the first network capability of the first capability level.

[0183] Step a3: The local API GW returns the capability invocation result to the edge application.

[0184] Second, when the first network capability of the first capability level is not deployed on the local API GW of the edge application (i.e., the third network node), steps b1 to b5 are executed.

[0185] Step b1: The edge application initiates a capability invocation request to the edge capability management platform (i.e., the first network node).

[0186] Step b2: The edge capability management platform combines the capability subscription record and the location of the edge application to generate a qualified first list.

[0187] Step b3: The edge capability management platform sends the first list to the edge capability scheduling center.

[0188] Step b4: The edge capability scheduling center combines the first list and the real-time status of each network node in the first list, and returns the network node with the best real-time status to the edge capability management platform.

[0189] Among them, the edge capability scheduling center can determine the real-time status of each network node by querying the real-time status from each MEC platform in real time.

[0190] Step b5: The edge capability management platform returns the capability invocation result to the edge application.

[0191] In the embodiments of the present application, the first network node determines, based on at least one set dimension, the capability grading corresponding to the first capability on each of at least two second network nodes; based on the capability grading of the first capability by the first network node, the third network node subscribes to and invokes the first capability corresponding to the first capability grading, thereby realizing differentiated capability subscription and invocation, and ensuring the matching between the invoked capability and the business requirements of the application. Moreover, based on the above capability invocation method, after the application server has switched, it is still possible to invoke, for the application, the capability that meets the business requirements based on the capability grading corresponding to the capability subscribed by the application, realizing refined business guarantee.

[0192] To implement the method in the embodiments of the present application, the embodiments of the present application further provide a capability invocation device, which is disposed on the first network node, as Figure 6 shown, and the device includes:

[0193] A first determination unit 601, configured to determine, based on at least one set dimension, the capability grading corresponding to the first capability on each of at least two second network nodes; wherein,

[0194] The first capability is deployed on the at least two second network nodes; the third network node subscribes to and invokes the first capability corresponding to the first capability grading.

[0195] Wherein, in one embodiment, when the first capability is a network capability, the at least one set dimension includes at least one of the following:

[0196] The location of the corresponding second network node;

[0197] The access capacity of the corresponding second network node for the first capability;

[0198] The response latency of the corresponding second network node for the first capability;

[0199] The performance of the first capability deployed on the corresponding second network node.

[0200] In one embodiment, the first determination unit 601 is specifically configured to:

[0201] When registering the first capability, determine, based on the at least one set dimension, the capability grading corresponding to the first capability on each of the at least two second network nodes.

[0202] In one embodiment, the device further includes:

[0203] A first sending unit, configured to send first information to the third network node and each of the at least two second network nodes; wherein,

[0204] The first information characterizes the capability grading corresponding to the first capability on each of the at least two second network nodes.

[0205] In one embodiment, the apparatus further includes:

[0206] A second sending unit, configured to save second information and send the second information to each of the at least two second network nodes; wherein,

[0207] The second information characterizes the capabilities ordered by the third network node and the corresponding ordered capability grading.

[0208] In one embodiment, the apparatus further includes:

[0209] A second receiving unit, configured to receive a first request from the third network node; the first request is used to request to invoke a first capability;

[0210] A generating unit, configured to generate a first list after confirming that the third network node has ordered a first capability corresponding to the first capability grading; the first list includes at least one of the at least two second network nodes, and the capability grading corresponding to the first capability on the second network node in the first list is the first capability grading;

[0211] A third sending unit, configured to return third information to the third network node based on the first list; the third information indicates one of the second network nodes in the first list, so that the third network node sends the first request to the second network node indicated by the third information.

[0212] In one embodiment, the generating unit is specifically configured to:

[0213] Generate the first list based on the distance between the second network node and the third network node.

[0214] In one embodiment, the apparatus further includes:

[0215] A third determining unit, configured to determine the third information based on at least one real-time performance parameter of each second network node in the first list;

[0216] The at least one real-time performance parameter includes at least one of the following:

[0217] Occupancy rate;

[0218] Response latency;

[0219] Uplink rate or downlink rate.

[0220] In actual application, the first determination unit 601, the generation unit, and the third determination unit may be implemented by a processor in the capability invocation device, and the first sending unit, the second sending unit, the second receiving unit, and the third sending unit may be implemented by a communication interface in the capability invocation device.

[0221] To implement the method on the second network node side in the embodiments of the present application, the embodiments of the present application further provide a capability invocation device, which is disposed on the second network node, as Figure 7 shown. The device includes:

[0222] A first receiving unit 701, configured to receive first information sent by a first network node;

[0223] A second determination unit 702, configured to determine a corresponding capability level based on the first information; where

[0224] a first capability is deployed on each of at least two second network nodes; the first information represents the capability level corresponding to the first capability on each of the at least two second network nodes, determined by the first network node based on at least one set dimension.

[0225] In one embodiment, the device further includes:

[0226] A third receiving unit, configured to receive a first request sent by the third network node; the first request is used to request to invoke the first capability;

[0227] An invocation unit, configured to invoke the first capability corresponding to the first capability level for the third network node based on the first request; where

[0228] the first request is sent by the third network node when it is confirmed that the first capability corresponding to the first capability level is deployed on the second network node.

[0229] In one embodiment, the device further includes:

[0230] A fourth receiving unit, configured to receive second information sent by the first network node; the second information represents the capabilities subscribed by the third network node and the corresponding capability levels;

[0231] The invocation unit is specifically configured to:

[0232] after confirming that the third network node subscribes to the first capability corresponding to the first capability level based on the second information, invoke the first capability corresponding to the first capability level for the third network node based on the first request.

[0233] In actual application, the first receiving unit 701, the third receiving unit, and the fourth receiving unit can be implemented by the communication interface in the capability invocation device; the second determination unit 702 can be implemented by the processor in the capability invocation device, and the invocation unit can be implemented by the processor in the capability invocation device in combination with the communication interface.

[0234] To implement the method on the third network node side in the embodiments of the present application, the embodiments of the present application further provide a capability invocation device, which is set on the third network node, as Figure 8 shown, and the device includes:

[0235] A subscription unit 801, configured to subscribe to a first capability corresponding to a first capability classification from a first network node; wherein,

[0236] The first network capability is deployed on at least two second network nodes; the capability classification corresponding to the first network capability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension.

[0237] Wherein, in one embodiment, the device further includes:

[0238] A fifth receiving unit, configured to receive first information sent by the first network node; the first information represents the capability classification corresponding to the first capability on each of the at least two second network nodes;

[0239] A fourth sending unit, configured to send a first request to a corresponding network node based on the first information; the first request is used to request to invoke the first capability.

[0240] In one embodiment, the fourth sending unit is specifically configured to:

[0241] When the first information indicates that the first capability corresponding to the first capability classification is deployed on a fourth network node, send the first request to the fourth network node; the fourth network node represents a network node that accesses the same local area network as the third network node;

[0242] When the first information indicates that the first capability corresponding to the first capability classification is not deployed on the fourth network node, send the first request to the first network node, receive third information returned by the first network node, and send the first request to the second network node indicated by the third information; wherein,

[0243] One second network node in a first list is indicated in the third information; the first list includes at least one second network node among the at least two second network nodes, and the capability classification corresponding to the first capability on the second network node in the first list matches the first capability classification.

[0244] In practical applications, the ordering unit 801, the fifth receiving unit, and the fourth transmitting unit can be implemented by the communication interface in the capability calling device.

[0245] It should be noted that when the capability calling device provided in the above embodiment performs capability calling, only the division of the above program modules is used for illustration. In practical applications, the above processing can be allocated to different program modules according to needs, that is, the internal structure of the device is divided into different program modules to complete all or part of the above-described processing. In addition, the capability calling device provided in the above embodiment and the embodiment of the capability calling method belong to the same concept. For the specific implementation process, please refer to the method embodiment, which will not be elaborated here.

[0246] Based on the hardware implementation of the above program modules, and in order to implement the method on the first network node side of the embodiments of the present application, the embodiments of the present application further provide a first network node, as Figure 9 shown, the first network node 900 includes:

[0247] A first communication interface 901 capable of interacting with other network nodes;

[0248] A first processor 902 is connected to the first communication interface 901 to implement information interaction with other network nodes. When running a computer program, it is used to execute the method provided by one or more technical solutions on the first network node side. The computer program is stored on the first memory 903.

[0249] Specifically, the first processor 902 is used to determine, based on at least one set dimension, the capability level corresponding to the first capability on each of at least two second network nodes; where

[0250] The first capability is deployed on the at least two second network nodes; the third network node orders and calls the first capability corresponding to the first capability level.

[0251] Wherein, in one embodiment, the at least one set dimension includes at least one of the following:

[0252] The location of the corresponding second network node;

[0253] The access capacity of the corresponding second network node to the first capability;

[0254] The response delay of the corresponding second network node to the first capability;

[0255] The performance of the first capability deployed on the corresponding second network node.

[0256] In one embodiment, the first processor 902 is specifically used for:

[0257] When registering the first capability, based on the at least one set dimension, determine the capability level corresponding to the first capability on each of the at least two second network nodes.

[0258] In one embodiment, the first communication interface 901 is used for:

[0259] Send the first information to the third network node and each of the at least two second network nodes; wherein,

[0260] The first information represents the capability level corresponding to the first capability on each of the at least two second network nodes.

[0261] In one embodiment, the first processor 902 is used to save the second information;

[0262] The first communication interface 901 is used for:

[0263] Send the second information to each of the at least two second network nodes; wherein,

[0264] The second information represents the capabilities ordered by the third network node and the corresponding ordered capability levels.

[0265] In one embodiment, the first communication interface 901 is used for:

[0266] Receive a first request from the third network node; the first request is used to request to invoke the first capability;

[0267] The first processor 902 is further used for: after confirming that the third network node subscribes to the first capability corresponding to the first capability level, generate a first list; the first list includes at least one of the at least two second network nodes, and the capability level corresponding to the first capability on the second network node in the first list is the first capability level;

[0268] The first communication interface 901 is further used for: based on the first list, return third information to the third network node; the third information indicates one of the second network nodes in the first list, so that the third network node sends the first request to the second network node indicated by the third information.

[0269] In one embodiment, the first processor 902 generates the first list, including:

[0270] Generate the first list based on the distance between the second network node and the third network node.

[0271] In one embodiment, the first processor 902 is further configured to:

[0272] Determine the third information based on at least one real-time performance parameter of each second network node in the first list;

[0273] The at least one real-time performance parameter includes at least one of the following:

[0274] Occupancy rate;

[0275] Response latency;

[0276] Uplink rate or downlink rate.

[0277] It should be noted that the specific processing procedures of the first processor 902 and the first communication interface 901 can be understood with reference to the above method.

[0278] Of course, in actual application, each component in the first network node 900 is coupled together through the bus system 904. It can be understood that the bus system 904 is used to implement the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 9 All kinds of buses are labeled as the bus system 904.

[0279] The first memory 903 in the embodiment of the present application is used to store various types of data to support the operation of the first network node 900. Examples of these data include: any computer program for operating on the first network node 900.

[0280] The method disclosed in the embodiment of the present application above can be applied to or implemented by the first processor 902. The first processor 902 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuit in hardware or instructions in software form in the first processor 902. The above first processor 902 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 902 can implement or execute each method, step, and logic block diagram disclosed in the embodiment of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as being executed and completed by the hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and this storage medium is located in the first memory 903. The first processor 902 reads the information in the first memory 903 and combines its hardware to complete the steps of the foregoing method.

[0281] In an exemplary embodiment, the first network node 900 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontroller units (MCUs), microprocessors, or other electronic components for executing the foregoing method.

[0282] Based on the hardware implementation of the above program module, and in order to implement the method on the second network node side in the embodiment of the present application, the embodiment of the present application also provides a second network node, as Figure 10 shown. The second network node 1000 includes:

[0283] A second communication interface 1001 capable of interacting with other network nodes for information;

[0284] A second processor 1002, connected to the second communication interface 1001 to enable information interaction with other network nodes, is configured to execute the methods provided by one or more of the above-mentioned technical solutions on the second network node side when running a computer program. The computer program is stored on a second memory 1003.

[0285] Specifically, the second communication interface 1001 is configured to receive first information sent by a first network node;

[0286] The second processor is configured to determine a corresponding capability level based on the first information; wherein,

[0287] A first capability is deployed on each of at least two second network nodes; the first information represents the capability level corresponding to the first capability on each of the at least two second network nodes determined by the first network node based on at least one set dimension.

[0288] Wherein, in one embodiment, the second communication interface 1001 is further configured to: receive a first request sent by a third network node; the first request is used to request to invoke the first capability;

[0289] The second communication interface 1001 is further configured to: invoke the first capability corresponding to the first capability level for the third network node based on the first request; wherein,

[0290] The first request is sent by the third network node when it is confirmed that the first capability of the first capability level is deployed on the second network node.

[0291] In one embodiment, the second communication interface 1001 is further configured to:

[0292] Receive second information sent by the first network node; the second information represents the capabilities subscribed by the third network node and the corresponding capability levels;

[0293] After confirming that the third network node subscribes to the first capability corresponding to the first capability level based on the second information, invoke the first capability corresponding to the first capability level for the third network node based on the first request.

[0294] It should be noted that: The specific processing procedures of the second processor 1002 and the second communication interface 1001 can be understood with reference to the above methods.

[0295] Of course, in practical applications, the various components in the second network node 1000 are coupled together through the bus system 1004. It can be understood that the bus system 1004 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 10 all kinds of buses are labeled as the bus system 1004.

[0296] The second memory 1003 in the embodiments of the present application is used to store various types of data to support the operation of the second network node 1000. Examples of these data include: any computer program for operating on the second network node 1000.

[0297] The method disclosed in the above embodiments of the present application can be applied to or implemented by the second processor 1002. The second processor 1002 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the second processor 1002 or by instructions in the form of software. The above-mentioned second processor 1002 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1002 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and this storage medium is located in the second memory 1003. The second processor 1002 reads the information in the second memory 1003 and combines its hardware to complete the steps of the foregoing method.

[0298] In an exemplary embodiment, the second network node 1000 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components for executing the foregoing method.

[0299] Based on the above hardware implementation of the program module, and in order to implement the method on the third network node side in the embodiments of the present application, the embodiments of the present application also provide a third network node, as Figure 11 shown. The third network node 1100 includes:

[0300] A third communication interface 1101 capable of interacting with other network nodes;

[0301] A third processor 1102, connected to the third communication interface 1101 to enable information interaction with other network nodes, is used to execute the method provided by one or more of the above technical solutions on the third network node side when running a computer program. The computer program is stored on the third memory 1103.

[0302] Specifically, the third communication interface 1101 is used to order a first capability corresponding to a first capability classification from a first network node; wherein,

[0303] The first capability is deployed on at least two second network nodes; the capability classification corresponding to the first capability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension.

[0304] Wherein, in one embodiment, the third communication interface 1101 is further used for:

[0305] Receiving first information sent by the first network node; the first information represents the capability classification corresponding to the first capability on each of the at least two second network nodes;

[0306] Sending a first request to a corresponding network node based on the first information; the first request is used to request to invoke the first capability.

[0307] In one embodiment, the third communication interface 1101 is specifically used for:

[0308] When the first information indicates that a first capability corresponding to the first capability classification is deployed on a fourth network node, sending the first request to the fourth network node; the fourth network node represents a network node that accesses the same local area network as the third network node;

[0309] When the first information indicates that a first capability corresponding to the first capability classification is not deployed on the fourth network node, sending the first request to the first network node, receiving third information returned by the first network node, and sending the first request to the second network node indicated by the third information; wherein,

[0310] One second network node in a first list is indicated in the third information; the first list includes at least one second network node among the at least two second network nodes, and the capability classification corresponding to the first capability on the second network node in the first list matches the first capability classification.

[0311] Of course, in practical applications, the various components in the third network node 1100 are coupled together through a bus system 1104. It can be understood that the bus system 1104 is used to implement the connection and communication between these components. In addition to the data bus, the bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 11 all kinds of buses are labeled as the bus system 1104.

[0312] The third memory 1103 in the embodiment of the present application is used to store various types of data to support the operation of the third network node 1100. Examples of such data include: any computer program for operating on the third network node 1100.

[0313] The method disclosed in the above embodiment of the present application can be applied to or implemented by the third processor 1102. The third processor 1102 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method can be completed by the integrated logic circuit in the hardware of the third processor 1102 or instructions in software form. The above-mentioned third processor 1102 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The third processor 1102 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. Combining the steps of the method disclosed in the embodiments of the present application, it can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, and this storage medium is located in the third memory 1103. The third processor 1102 reads the information in the third memory 1103 and combines its hardware to complete the steps of the foregoing method.

[0314] In an exemplary embodiment, the third network node 1100 can be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components for executing the foregoing method.

[0315] It can be understood that the memories (the first memory 903, the second memory 1003, and the third memory 1103) in the embodiments of the present application can be volatile memories or non-volatile memories, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory), an electrically erasable programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), a ferromagnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM, Random Access Memory), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as a static random access memory (SRAM, Static Random Access Memory), a synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory), a dynamic random access memory (DRAM, Dynamic Random Access Memory), a synchronous dynamic random access memory (SDRAM, Synchronous Dynamic Random Access Memory), a double data rate synchronous dynamic random access memory (DDR SDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), an enhanced synchronous dynamic random access memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), a synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and a direct rambus random access memory (DRRAM, Direct Rambus Random Access Memory).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0316] In an exemplary embodiment, the embodiments of this application also provide a storage medium, specifically a computer storage medium, more specifically a computer-readable storage medium. For example, it includes a first memory 903 that stores a computer program, and the above computer program can be executed by a first processor 902 of a first network node 900 to complete the steps described in the foregoing method on the first network node side. Another example is a second memory 1003 that stores a computer program, and the above computer program can be executed by a second processor 1002 of a second network node 1000 to complete the steps described in the foregoing method on the first network node side. Another example is a third memory 1103 that stores a computer program, and the above computer program can be executed by a third processor 1102 of a third network node 1100 to complete the steps described in the foregoing method on the third network node side. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0317] It should be noted that: "first", "second", etc. are used to distinguish similar objects and do not necessarily have to describe a specific order or sequence.

[0318] In addition, the technical solutions described in the embodiments of this application can be arbitrarily combined without conflict.

[0319] The above is only a preferred embodiment of this application and is not intended to limit the protection scope of this application.

Claims

1. A method for invoking an ability, characterized in that, Applied to a first network node; the method includes: Based on at least one set dimension, determining the ability grading corresponding to the first ability on each of at least two second network nodes; wherein, the first ability is deployed on the at least two second network nodes; a third network node subscribes to and invokes the first ability corresponding to the first ability grading. Receiving a first request from the third network node; the first request is used to request to invoke the first ability. After confirming that the third network node subscribes to the first ability corresponding to the first ability grading, generating a first list; the first list includes at least one of the at least two second network nodes, and the ability grading corresponding to the first ability on the second network node in the first list is the first ability grading. Returning third information to the third network node based on the first list; the third information indicates one of the second network nodes in the first list, so that the third network node sends the first request to the second network node indicated by the third information.

2. The method according to claim 1, characterized in that When the first ability is a network ability, the at least one set dimension includes at least one of the following: The network distance between the corresponding second network node and the radio side; The access capacity of the corresponding second network node for the first ability; The response delay of the corresponding second network node for the first ability; The performance of the first ability deployed on the corresponding second network node.

3. The method according to claim 1 or 2, characterized in that, The determining the ability grading corresponding to the first ability on each of at least two second network nodes based on at least one set dimension includes: When registering the first ability, determining the ability grading corresponding to the first ability on each of the at least two second network nodes based on the at least one set dimension.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Sending first information to the third network node and each of the at least two second network nodes; wherein, The first information represents the ability grading corresponding to the first ability on each of the at least two second network nodes.

5. The method according to claim 1, characterized in that The method further includes: Saving second information and sending the second information to each of the at least two second network nodes; wherein, The second information represents the network ability subscribed by the third network node and the corresponding subscribed ability grading.

6. The method according to claim 1, wherein The generating the first list includes: Generating the first list based on the distance between the second network node and the third network node.

7. The method according to claim 1, characterized in that, The method further includes: Determining the third information based on at least one real-time performance parameter of each second network node in the first list; The at least one real-time performance parameter includes at least one of the following: Occupancy rate; Response delay; Uplink rate or downlink rate.

8. A method for invoking an ability, characterized in that, Applied to any one of at least two second network nodes; Each of the at least two second network nodes deploys a first ability; the method includes: Receiving first information sent by a first network node; Determine the corresponding ability level based on the first information; wherein, the first information represents the ability level corresponding to the first ability on each of the at least two second network nodes determined by the first network node based on at least one set dimension; Receive the second information sent by the first network node; the second information represents the network capabilities ordered by the third network node and the corresponding ability levels; Receive the first request sent by the third network node; the first request is used to request to invoke the first ability; After confirming that the third network node has ordered the first ability corresponding to the first ability level based on the second information, invoke the first ability corresponding to the first ability level for the third network node based on the first request; wherein, the first request is sent by the third network node when it is confirmed that the first ability of the first ability level is deployed on the second network node; 9. A method for invoking an ability, characterized in that, Applied to the third network node, the method includes: Order the first ability corresponding to the first ability level from the first network node; wherein, the first ability is deployed on at least two second network nodes; the ability level corresponding to the first ability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension; Receive the first information sent by the first network node; the first information represents the ability level corresponding to the first ability on each of the at least two second network nodes; When the first information indicates that the first ability of the first ability level is deployed on the fourth network node, send the first request to the fourth network node; the fourth network node represents the network node accessed by the third network node; When the first information indicates that the first ability of the first ability level is not deployed on the fourth network node, send the first request to the first network node, receive the third information returned by the first network node, and send the first request to the second network node indicated by the third information; wherein, One second network node in the first list is indicated in the third information; the first list includes at least one second network node among the at least two second network nodes, and the ability level corresponding to the first ability on the second network node in the first list matches the first ability level; the first request is used to request to invoke the first ability.

10. An ability calling device, characterized in that, Includes: The first determination unit is used to determine the ability level corresponding to the first ability on each of the at least two second network nodes based on at least one set dimension; wherein, The first ability is deployed on the at least two second network nodes; the third network node orders and invokes the first ability corresponding to the first ability level; The second receiving unit is used to receive the first request of the third network node; the first request is used to request to invoke the first ability; A generating unit, configured to generate a first list after confirming that the third network node subscribes to a first capability corresponding to the first capability classification; the first list includes at least one of the at least two second network nodes, and the capability classification corresponding to the first capability on the second network node in the first list is the first capability classification; A third sending unit, configured to return third information to the third network node based on the first list; the third information indicates one of the second network nodes in the first list, so that the third network node sends the first request to the second network node indicated by the third information.

11. An ability invocation device, characterized in that, Comprising: A first receiving unit, configured to receive first information sent by a first network node; A second determining unit, configured to determine a corresponding capability classification based on the first information; wherein, the first capability is deployed on each of the at least two second network nodes; the first information represents the capability classification corresponding to the first capability on each of the at least two second network nodes determined by the first network node based on at least one set dimension; A third receiving unit, configured to receive a first request sent by a third network node; the first request is used to request to invoke the first capability; An invoking unit, configured to, after confirming that the third network node subscribes to a first capability corresponding to the first capability classification based on second information, invoke the first capability corresponding to the first capability classification for the third network node based on the first request; wherein, the first request is sent by the third network node when it is confirmed that the first capability of the first capability classification is deployed on the second network node; A fourth receiving unit, configured to receive second information sent by the first network node; the second information represents the network capabilities subscribed by the third network node and the corresponding capability classifications.

12. An ability invocation device, characterized in that, Comprising: A subscribing unit, configured to subscribe to a first capability corresponding to the first capability classification from the first network node; wherein, the first capability is deployed on at least two second network nodes; the capability classification corresponding to the first capability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension; A fifth receiving unit, configured to receive first information sent by the first network node; the first information represents the capability classification corresponding to the first capability on each of the at least two second network nodes; A fourth sending unit, configured to send a first request to the fourth network node when the first information indicates that a first capability corresponding to the first capability classification is deployed on the fourth network node; the fourth network node represents a network node accessed by the third network node; when the first information indicates that a first capability corresponding to the first capability classification is not deployed on the fourth network node, send the first request to the first network node, receive third information returned by the first network node, and send the first request to a second network node indicated by the third information; wherein, one second network node in a first list is indicated in the third information; the first list includes at least one second network node among the at least two second network nodes, and the capability classification corresponding to the first capability on the second network node in the first list matches the first capability classification; the first request is used to request to invoke the first capability.

13. A first network node, characterized in that, Comprising: A first processor and a first communication interface; wherein, The first processor is configured to determine, based on at least one set dimension, the capability classification corresponding to the first capability on each of at least two second network nodes; wherein, the first capability is deployed on the at least two second network nodes; the third network node subscribes to and invokes the first capability corresponding to the first capability classification; after confirming that the third network node subscribes to the first capability corresponding to the first capability classification, generate a first list; the first list includes at least one second network node among the at least two second network nodes, and the capability classification corresponding to the first capability on the second network node in the first list is the first capability classification; The first communication interface is configured to receive a first request from the third network node; the first request is used to request to invoke the first capability; and, based on the first list, return third information to the third network node; one second network node in the first list is indicated in the third information, so that the third network node sends the first request to the second network node indicated by the third information.

14. A second network node, characterized in that, Comprising: A second processor and a second communication interface; wherein, The second communication interface is configured to receive first information sent by the first network node; receive second information sent by the first network node; the second information represents the network capabilities subscribed by the third network node and the corresponding capability classifications; receive the first request sent by the third network node; the first request is used to request to invoke the first capability; and, after confirming, based on the second information, that the third network node subscribes to the first capability corresponding to the first capability classification, invoke the first capability corresponding to the first capability classification for the third network node based on the first request; wherein, the first request is sent by the third network node when it is confirmed that the first capability corresponding to the first capability classification is deployed on the second network node. The second processor is configured to determine the corresponding capability classification based on the first information; wherein, A first capability is deployed on each of at least two second network nodes; the first information represents the capability grading corresponding to the first capability on each of the at least two second network nodes, which is determined by the first network node based on at least one set dimension.

15. A third network node, characterized in that, Comprising: A third processor and a third communication interface; wherein, The third communication interface is configured to subscribe to the first capability corresponding to the first capability grading from the first network node; wherein, the first capability is deployed on at least two second network nodes; the capability grading corresponding to the first capability on each of the at least two second network nodes is determined by the first network node based on at least one set dimension; receive the first information sent by the first network node; the first information represents the capability grading corresponding to the first capability on each of the at least two second network nodes; when the first information represents that the first capability corresponding to the first capability grading is deployed on a fourth network node, send a first request to the fourth network node; the fourth network node represents the network node accessed by the third network node; and, when the first information represents that the first capability corresponding to the first capability grading is not deployed on the fourth network node, send the first request to the first network node, receive the third information returned by the first network node, and send the first request to the second network node indicated by the third information; wherein, one second network node in a first list is indicated in the third information; the first list includes at least one second network node among the at least two second network nodes, and the capability grading corresponding to the first capability on the second network node in the first list matches the first capability grading; the first request is used to request to invoke the first capability.

16. A first network node, characterized in that, Comprising: A first processor and a first memory for storing a computer program that can run on the processor, wherein, when the first processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 7.

17. A second network node, characterized in that, Comprising: A second processor and a second memory for storing a computer program that can run on the processor, wherein, when the second processor is used to run the computer program, it executes the steps of the method according to claim 8.

18. A third network node, characterized in that, Comprising: A third processor and a third memory for storing a computer program that can run on the processor, wherein, when the third processor is used to run the computer program, it executes the steps of the method according to claim 9.

19. A storage medium, on which a computer program is stored, characterized in that, When the computer program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 7, or implements the steps of the method according to claim 8, or implements the steps of the method according to claim 9.

Images