Capability invocation method, device, network node, and storage medium
The capability invocation method addresses the mismatch between network capabilities and application needs by determining a hierarchy based on positional, capacity, and performance parameters, ensuring aligned and appropriate capability invocation.
Patent Information
- Application Number
- JP2023543443
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-01-20
- Filing Date
- 2022-01-20
- Publication Date
- 2024-11-11
- Estimated Expiration
- 2042-01-20
AI Technical Summary
Existing network capabilities deployed at the edge do not match the service needs of applications, leading to mismatches between invoked capabilities and application requirements.
A capability invocation method that determines a hierarchy for network capabilities based on parameters such as position, access capacity, response delay, and performance, allowing for differentiated capability subscription and invocation that aligns with application needs.
Ensures that invoked capabilities match the service needs of applications, providing consistent and appropriate network functionality.
Smart Images

Figure 0007580618000004 
Figure 0007580618000005 
Figure 0007580618000006
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This disclosure is filed based on and claims priority to a Chinese patent application having application number 202110076181.6 and filing date on January 20, 2021, the entire contents of which are incorporated herein by reference.
[0002] The present disclosure relates to the field of network technology, and in particular to a capability invocation method, device, network node, and storage medium. [Background technology]
[0003] With the development and deployment of edge computing, the network capabilities deployed at the network edge are increasing, including radio positioning capabilities, user identifiers, bandwidth management capabilities, Radio Network Information Services (RNIS), shunt capabilities, cloud gaming, video codecs, etc. These network capabilities are gradually opened up to operator-specific applications or third-party applications. When an application needs to use a network capability, it needs to submit a capability subscription request to the management platform, and after the subscription is completed, it can make a capability call.
[0004] In the related art, there exists a problem that the called network capabilities and the service needs of the application do not match. Summary of the Invention [Problem to be solved by the invention]
[0005] SUMMARY OF THE DISCLOSURE The embodiments of the present disclosure provide a capability invocation method, an apparatus, a network node, and a storage medium to solve problems in the related art. [Means for solving the problem]
[0006] The technical solutions according to the embodiments of the present disclosure are realized as follows:
[0007] An embodiment of the present disclosure provides a capability invocation method for a first network node, the method comprising: Determining a capability hierarchy corresponding to the first capability at each second network node of the at least two second network nodes based on the at least one parameter.
[0008] Here, in one embodiment, when the first capability is a network capability, the at least one parameter is: a corresponding network distance between the second network node and the wireless side; and a corresponding access capacity of the second network node to the first capability; and a corresponding response delay of the second network node to the first capability; and and a corresponding performance of the first capability located in the second network node.
[0009] In one embodiment, determining a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes based on the at least one parameter comprises: When registering with the first capability, determining a capability hierarchy corresponding to the first capability at each second network node of the at least two second network nodes based on the at least one parameter.
[0010] In one embodiment, the method further comprises: transmitting first information to a third network node and to each second network node of the at least two second network nodes; Here, the first information represents a capability hierarchy corresponding to a first capability at each second network node among the at least two second network nodes, and the third network node represents a network node that subscribes to and invokes the first capability.
[0011] In one embodiment, the method further comprises: storing second information and transmitting the second information to each second network node of the at least two second network nodes; Here, the second information represents network capabilities subscribed to by the third network node and a corresponding subscribed capability hierarchy.
[0012] In one embodiment, the method further comprises: receiving a first request from a third network node, the first request being used to request invocation of a first capability; generating a first list after determining that the third network node subscribes to a first capability corresponding to the first capability tier, the first list including at least one second network node among the at least two second network nodes, and a capability tier corresponding to the first capability at the second network node in the first list being the first capability tier; and returning third information to the third network node based on the first list, the third information including instructing a second network node in the first list to cause the third network node to send the first request to a second network node indicated by the third information.
[0013] In one embodiment, generating the first list comprises: generating the first list based on distances between second network nodes and the third network nodes;
[0014] In one embodiment, the method further comprises: 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 is Occupancy rate and Response delay and and at least one of an uplink rate or a downlink rate.
[0015] The embodiment of the present disclosure further provides a capability invoking method, which is applied to any one second network node of at least two second network nodes, Each second network node of the at least two second network nodes is configured with a first capability, and the method further comprises: receiving first information transmitted from a first network node; determining a corresponding competency tier based on the first information; Here, the first information represents a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes, determined by the first network node based on at least one parameter.
[0016] wherein, in one embodiment, the method further comprises: receiving a first request transmitted from a third network node, the first request being used to request invocation of a first capability; and invoking a first capability corresponding to the first capability hierarchical layer for the third network node based on the first request; Here, the first request is transmitted when the third network node confirms that a first capability of the first capability hierarchy is configured in the second network node.
[0017] In one embodiment, the method further comprises: receiving second information transmitted from the first network node; the second information represents network capabilities and corresponding capability tiers subscribed to by the third network node; Invoking a first capability corresponding to the first capability hierarchical for the third network node based on the first request includes: and after determining based on the second information that the third network node subscribes to a first capability corresponding to the first capability hierarchical layer, invoking a first capability corresponding to the first capability hierarchical layer for the third network node based on the first request.
[0018] An embodiment of the present disclosure further provides a capability invoking method for a third network node, the method comprising: subscribing to a first network node a first capability corresponding to a first capability hierarchical level; wherein the first capability is configured in at least two second network nodes; A capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes is determined by the first network node based on at least one parameter.
[0019] wherein, in one embodiment, the method further comprises: receiving first information transmitted from the first network node, the first information representing a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes; Sending a first request to a corresponding network node based on the first information, the first request being used to request invocation of a first capability.
[0020] In one embodiment, sending a first request to a corresponding network node based on the first information comprises: sending the first request to a fourth network node when the first information indicates that a first capability corresponding to the first capability hierarchy is deployed in the fourth network node, the fourth network node indicating a network node accessed by the third network node; if the first information indicates that a first capability corresponding to the first capability hierarchy is not deployed in a fourth network node, sending the first request to the first network node, receiving third information returned from the first network node, and sending the first request to a second network node indicated by the third information; Here, the third information indicates one second network node in a first list, the first list includes at least one second network node among the at least two second network nodes, and a capability hierarchy corresponding to a first capability at a second network node in the first list matches the first capability hierarchy.
[0021] An embodiment of the present disclosure further provides a capability invocation device, the capability invocation device comprising: The network includes a first determining unit configured to determine a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes based on the at least one parameter.
[0022] An embodiment of the present disclosure further provides a capability invocation device, the capability invocation device comprising: a first receiving unit configured to receive first information transmitted from a first network node; a second determination unit configured to determine a corresponding capability tier based on the first information; wherein each second network node of the at least two second network nodes is configured with a first capability; The first information represents a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes, the capability hierarchy being determined by the first network node based on at least one parameter.
[0023] An embodiment of the present disclosure further provides a capability invocation device, the capability invocation device comprising: a subscribing unit configured to subscribe to a first capability corresponding to a first capability hierarchical level to a first network node; Here, the first network capability is configured in at least two second network nodes, and a capability hierarchy corresponding to the first network capability in each of the at least two second network nodes is determined by the first network node based on at least one parameter.
[0024] An embodiment of the present disclosure further provides a first network node, comprising: a first processor and a first communication interface; Here, the first processor is configured to determine a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes based on at least one parameter.
[0025] An embodiment of the present disclosure further provides a second network node, the second network node comprising: a second processor and a second communication interface; wherein the second communication interface is configured to receive first information transmitted from a first network node; the second processor is configured to determine a corresponding capability tier based on the first information; wherein each second network node of the at least two second network nodes is configured with a first capability; The first information represents a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes, the capability hierarchy being determined by the first network node based on at least one parameter.
[0026] An embodiment of the present disclosure further provides a third network node, the third network node comprising: a third processor and a third communication interface; wherein the third communication interface is configured to subscribe to a first capability corresponding to a first capability hierarchy to the first network node; wherein the first capability is configured in at least two second network nodes; A capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes is determined by the first network node based on at least one parameter.
[0027] An embodiment of the present disclosure further provides a first network node, comprising: A first processor and a first memory adapted to store a computer program executable by the processor; Here, the first processor is configured to execute any of the steps of the method on the first network node side when executing the computer program.
[0028] An embodiment of the present disclosure further provides a second network node, the second network node comprising: a second processor and a second memory adapted to store a computer program executable by the processor; Here, the second processor is configured to execute any of the steps of the method on the second network node side when executing the computer program.
[0029] An embodiment of the present disclosure further provides a third network node, the third network node comprising: a third processor and a third memory adapted to store a computer program executable by the processor; Here, the third processor is configured to perform any of the steps of the method on the third network node side when executing the computer program.
[0030] An embodiment of the present disclosure further provides a storage medium having a computer program stored thereon, the computer program implementing the steps of any of the methods described above when executed by a processor. Effect of the Invention
[0031] According to a network capability invocation method, device, network node, and storage medium of an embodiment of the present disclosure, a first capability is configured in at least two second network nodes, and the first network node determines a capability hierarchy corresponding to the first capability in each of the at least two second network nodes based on at least one parameter, and based on the capability hierarchy for the first capability of the first network node, a third network node can subscribe to and invoke the first capability corresponding to the first capability hierarchy, thus realizing subscription and invocation of differentiated capabilities and ensuring consistency between the invoked capabilities and the service needs of an application. [Brief description of the drawings]
[0032] [Figure 1] FIG. 2 is a schematic diagram of a capability invocation method flow according to an embodiment of the present disclosure. [Diagram 2] FIG. 13 is a schematic diagram of a network capability registration flow according to an application embodiment of the present disclosure. [Diagram 3] 13 is a schematic diagram of another capability invocation method flow according to an embodiment of the present disclosure. [Figure 4] 13 is a schematic diagram of another capability invocation method flow according to an embodiment of the present disclosure. [Diagram 5] FIG. 2 is a schematic diagram of a network capability call flow according to an application embodiment of the present disclosure. [Figure 6] FIG. 2 is a schematic diagram of a capability calling device configuration according to an embodiment of the present disclosure. [Figure 7] FIG. 13 is a schematic diagram of another capability invocation device configuration according to an embodiment of the present disclosure. [Figure 8] FIG. 13 is a schematic diagram of another capability invocation device configuration according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is a schematic diagram of a first network node structure according to an embodiment of the present disclosure. [Figure 10] FIG. 2 is a schematic diagram of a second network node structure according to an embodiment of the present disclosure. [Figure 11] FIG. 13 is a schematic diagram of a third network node structure according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0033] When an application needs to use a network function, the application server needs to submit a capability subscription request to the management platform, and a capability call can be made after the subscription is completed. With the development and deployment of edge computing, the number of network capabilities deployed at the network edge is increasing. Regarding the network capabilities deployed at the edge, the related technology does not consider how operators perform performance evaluation on network capabilities and then realize capability classification for different business needs, even though the service needs of different applications for the same network capabilities are different. Meanwhile, when providing network capabilities to an application, proximity matching is generally performed based on the distance between the application server and the deployment location of the network capabilities, and even when the application server is switched, it is not considered from beginning to end whether the called network capabilities can meet the business needs of the application based on the principle of proximity matching. Based on the above, the related technology has a problem that the called network capabilities and the service needs of the application do not match.
[0034] Based on this, embodiments of the present disclosure provide a capability invocation method, an apparatus, a network node, and a storage medium, in which a first capability is configured in at least two second network nodes, the first network node determines a capability hierarchy corresponding to the first capability in each of the at least two second network nodes based on at least one parameter, and based on the capability hierarchy for the first capability of the first network node, a third network node can subscribe to and invoke the first capability corresponding to the first capability hierarchy, thus realizing subscription and invocation of differentiated capabilities and ensuring consistency between the invoked capabilities and the service needs of an application.
[0035] The present disclosure will be described in more detail below with reference to the accompanying drawings and examples. Note that in the embodiments of the present disclosure, the capability may be a network capability deployed at the network edge by an operator, i.e., an edge network capability, or a capability deployed at the network edge by a third party application, such as a face recognition function.
[0036] The embodiment of the present disclosure provides a capability invocation method for a first network node, where the first network node is a management platform, also called an edge capability management platform or an edge capability open management platform. As shown in FIG. 1, the method includes the following step 101:
[0037] In step 101, a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes is determined based on at least one parameter.
[0038] Here, a first capability is configured in the at least two second network nodes, and a third network node subscribes to and invokes the first capability corresponding to the first capability hierarchy.
[0039] Exemplarily, the first capability may be a network capability such as radio positioning capability, user identifier, bandwidth management capability, RNIS, shunt capability, cloud gaming, video codec, etc., or a function such as face recognition by a third-party application. The second network node is a network node where the first capability is located, and is generally a multi-access edge computing (MEC) platform. In practical application, the second network node may be an application programming interface (API) gateway (GW) located at a network edge. The first network node, as a capability management platform, determines a capability tier corresponding to the first capability at each second network node, and after determining the capability tier, can differentiate and provide the first capability corresponding to different capability tiers to the application. In this way, when the third network node, i.e., the application server, subscribes to the first capability corresponding to the first capability tier based on the capability tier of the first capability, and can call the first capability corresponding to the first capability tier.
[0040] In one embodiment, when the first capability is a network capability, the at least one parameter is: a corresponding location of a second network node; and a corresponding access capacity of the second network node to the first capability; and a corresponding response delay of the second network node to the first capability; and and a corresponding performance of the first capability located in the second network node.
[0041] Here, the location, i.e., the deployment location of the second network node in the network, can represent the network distance between the second network node and the wireless side, and the access capacity and response delay depend on the second network node itself, for example, on the performance of the API GW or the deployed edge computing platform (ECP, Edge Compute Platform) resources. The performance of the first capability depends on the performance of the first capability deployed in the second network node, for example, the wireless positioning capability has a differentiation requirement for positioning accuracy, and the positioning accuracy of the wireless positioning capability deployed in different second network nodes is different. Based on at least one of the above parameters, the first network platform can determine a capability hierarchy corresponding to the first capability in each second network node.
[0042] In practical application, a capability layering function can be added to the first network node, and when a capability is registered in the management platform, the first network node layers the capability and stores the corresponding layering result.
[0043] Based on this, in one embodiment, determining a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes based on the at least one parameter comprises: When registering with the first capability, determining a capability hierarchy corresponding to the first capability at each second network node of the at least two second network nodes based on the at least one parameter.
[0044] In one embodiment, the method further comprises: transmitting first information to a third network node and to each second network node of the at least two second network nodes; Here, the first information represents a capability hierarchy corresponding to a first capability at each second network node among the at least two second network nodes, and the third network node represents a network node that subscribes to and invokes the first capability.
[0045] In this way, the third network node can initiate a request to a corresponding network node to invoke the first capability based on the first information, and the second network node can determine a capability hierarchy corresponding to the first capability locally deployed in the second network node based on the first information.
[0046] FIG. 2 is a schematic diagram of a network capability registration flow according to an embodiment of the present disclosure. As shown in FIG. 2, the process of registering network capabilities includes the following steps 1 to 4.
[0047] In step 1, a registration request accompanied with capability information is initiated to an edge capability open management platform (ie, a first network node) to request registration of corresponding network capability.
[0048] In step 2, the edge capability open management platform determines a capability hierarchy corresponding to the network capability in each deployed API GW (i.e., the second network node) based on at least one parameter, and stores the hierarchical information.
[0049] Here, in addition to storing registration information of network capabilities, the edge capability open management platform also adds hierarchical information that stores network capabilities, for example, not only capability identifiers. In step 3, the edge capability open management platform sends capability registration success information to each API GW, and hierarchical information is attached to the sent capability registration success information.
[0050] In step 4, each API GW maintains relevant information of network capabilities locally in each API GW based on the transmitted hierarchical information, and the hierarchical information corresponding to the network capabilities locally configured in each API GW is included.
[0051] Table 1 shows the hierarchical information stored in the first network node. From Table 1, it can be seen that API GW 1 and API GW 2 are both configured with network capability 1, and the configured network capability 1 corresponds to a 1-level capability hierarchy, and that API GW 1 is further configured with network capability 2, and network capability 2 corresponds to a 2-level capability hierarchy.
[0052] [Table 1]
[0053] Table 2 shows the hierarchical information stored in API GW 1, which is determined by API GW 1 based on the first information sent from the management platform, which is associated with the network capabilities deployed in API GW 1, includes network capability 1 corresponding to the 1-level capability hierarchy and network capability 2 corresponding to the 2-level capability hierarchy, which are deployed in API GW 1, and the specific deployment path of each network capability in API GW 1 is recorded in the corresponding deployment position.
[0054] [Table 2]
[0055] After realizing the capability hierarchization of the first capability, when the third network node subscribes to the first capability, it can specifically subscribe to one capability hierarchical 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 hierarchical level subscribed by the third network node, and send the capability subscription record to each second network node, thereby facilitating the capability call in the subsequent third network node.
[0056] Based on this, in one embodiment, the method further comprises: storing second information and transmitting the second information to each second network node of the at least two second network nodes; Here, the second information represents capabilities subscribed to by the third network node and a corresponding subscribed capability hierarchy.
[0057] Here, when the first network node or any one of the second network nodes receives a request for invoking a first capability sent from a third network node, it can confirm that the third network node subscribes to the first capability based on the second information, and further confirm a capability hierarchy of the first capability correspondingly subscribed to by the third network node based on the second information, and based thereon, invoke the first capability corresponding to the capability hierarchy for the third network node.
[0058] Table 3 shows the second information sent from the first network node, based on which it can be determined that application 1 and application 2 both subscribe to capability 1 corresponding to capability tier 1.
[0059] [Table 3]
[0060] In one embodiment, the method further comprises: receiving a first request from the third network node, the first request being used to request invocation of a first capability; generating a first list after determining that the third network node subscribes to a first capability corresponding to the first capability tier, the first list including at least one second network node among the at least two second network nodes, and a capability tier corresponding to the first capability at the second network node in the first list being the first capability tier; and returning third information to the third network node based on the first list, the third information including instructing a second network node in the first list to cause the third network node to send the first request to a second network node indicated by the third information.
[0061] When the third network node calls the first capability, the third network node first checks whether the first capability corresponding to the first capability hierarchy is locally arranged based on the first information sent from the first network node, that is, checks whether the first capability corresponding to the first capability hierarchy is arranged in the API GW accessed when the third network node is an application server. If the first information indicates that the first capability corresponding to the first capability hierarchy is not locally arranged, the third network node sends a first request to the first network node, and the first network node checks based on the second information that the third network node subscribes to the first capability corresponding to the first capability hierarchy, and then determines a second network node in which the first capability corresponding to the first capability hierarchy is arranged based on the first information, and generates a first list based on the determined second network node.
[0062] In one embodiment, generating the first list comprises: generating the first list based on distances between second network nodes and the third network nodes;
[0063] In practical application, when generating the first list, the first network node needs to simultaneously consider the distance between the second network node and the third network node, and ensure as much as possible that the distance between the second network node and the third network node appearing in the first list is within an appropriate range, so as to facilitate more quickly invoking the first capability.
[0064] In one embodiment, the method further comprises: 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 is Occupancy rate and Response delay and and at least one of an uplink rate or a downlink rate.
[0065] Here, when selecting a second network node for the third network node from the first list, real-time state information of the second network nodes is combined, and if the provided first capabilities all correspond to the first capability hierarchy, the second network node with the optimal real-time state is selected, ensuring that the selected second network node can provide optimal first capabilities to the third network node.
[0066] In practical application, by disposing a corresponding functional module in a first network node, the functional module can realize the function of an edge scheduling center, receive a first list from a management platform, obtain the real-time status of each second network node in the first list, and feed back the obtained real-time status to the management platform.
[0067] Accordingly, the embodiment of the present disclosure further provides a capability invocation method, which is applied to any one of at least two second network nodes, and a first capability is configured in each of the at least two second network nodes. As shown in FIG. 3, the method includes the following steps 301 to 302.
[0068] In step 301, first information transmitted from a first network node is received.
[0069] In step 302, a corresponding capability hierarchy is determined based on the first information.
[0070] Here, the first information represents a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes, determined by the first network node based on at least one parameter.
[0071] Here, the second network node may be each API GW located at the network edge. The first network node, as a capability management platform, determines a capability hierarchy corresponding to the first capability at each second network node. The second network node receives the first information transmitted from the first network node, and determines a capability hierarchy corresponding to the first capability locally deployed in the second network node based on the first information. After determining the capability hierarchy, the first capabilities corresponding to different capability hierarchies can be differentiated and provided to the application, and thus, when the third network node, i.e., the application server, subscribes to the first capability corresponding to the first capability hierarchy based on the capability hierarchy of the first capability, and can invoke the first capability corresponding to the first capability hierarchy when subscribing to the first network node.
[0072] In one embodiment, the method further comprises: receiving a first request transmitted from the third network node, the first request being used to request invocation of a first capability; and invoking a first capability corresponding to the first capability hierarchical layer for the third network node based on the first request; Here, the first request is transmitted when the third network node confirms that a first capability of the first capability hierarchy is configured in the second network node.
[0073] In practical application, when the third network node determines that the second network node has a first capability corresponding to the first capability hierarchy, the third network node sends a first request to the second network node and invokes the first capability corresponding to the first capability hierarchy according to the first request, where the second network node receiving the first request may be a network node accessed by the third network node or another second network node.
[0074] In one embodiment, the method further comprises: receiving second information transmitted from the first network node, the second information indicating capabilities and corresponding capability tiers subscribed to by a third network node; Invoking a first capability corresponding to the first capability hierarchical for the third network node based on the first request includes: and after determining based on the second information that the third network node subscribes to a first capability corresponding to the first capability hierarchical layer, invoking a first capability corresponding to the first capability hierarchical layer for the third network node based on the first request.
[0075] When the second network node receives a first request sent from a third network node, the second network node confirms, based on the second information, that the third network node subscribes to a first capability corresponding to the first capability hierarchical layer, and then invokes, based on the first request, a first capability corresponding to the first capability hierarchical layer for the third network node.
[0076] Accordingly, the embodiment of the present disclosure further provides a capability invocation method for applying to a third network node, and in practical application, the third network node is an application server. As shown in FIG 4, the method includes the following step 401:
[0077] In step 401, a first capability corresponding to a first capability hierarchy is subscribed to a first network node. wherein the first capability is configured in at least two second network nodes; A capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes is determined by the first network node based on at least one parameter.
[0078] Exemplarily, the first capability may be a network capability such as radio positioning capability, user identifier, bandwidth management capability, RNIS, shunt capability, cloud gaming, video codec, etc., or a function such as face recognition by a third party application. The second network node is a network node where the first capability is located, and is generally each MEC platform, and in practical 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 a capability hierarchy corresponding to the first capability at each second network node, and after determining the capability hierarchy, can differentiate and provide the first capability corresponding to different capability hierarchies to the application. In this way, when the third network node, i.e., the application server, subscribes to the first capability corresponding to the first capability hierarchy based on the capability hierarchy of the first capability, and can call the first capability corresponding to the first capability hierarchy when subscribing to the first network node.
[0079] In one embodiment, the method further comprises: receiving first information transmitted from the first network node, the first information representing a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes; Sending a first request to a corresponding network node based on the first information, the first request being used to request invocation of a first capability.
[0080] When the third network node calls the first capability, the third network node first checks whether the first capability corresponding to the first capability hierarchy is locally arranged based on the first information sent from the first network node, that is, checks whether the first capability corresponding to the first capability hierarchy is arranged in the API GW accessed when the third network node is an application server. If the first information indicates that the first capability corresponding to the first capability hierarchy is not locally arranged, the third network node sends a first request to the first network node, and the first network node checks based on the second information that the third network node subscribes to the first capability corresponding to the first capability hierarchy, and then determines a second network node in which the first capability corresponding to the first capability hierarchy is arranged based on the first information, and generates a first list based on the determined second network node.
[0081] Based thereon, in one embodiment, sending a first request to a corresponding network node based on the first information includes: sending the first request to a fourth network node when the first information indicates that a first capability corresponding to the first capability hierarchy is deployed in the fourth network node, the fourth network node indicating a network node accessing the same local area network as the third network node; if the first information indicates that a first capability corresponding to the first capability hierarchy is not deployed in a fourth network node, sending the first request to the first network node, receiving third information returned from the first network node, and sending the first request to a second network node indicated by the third information; Here, the third information indicates one second network node in a first list, the first list includes at least one second network node among the at least two second network nodes, and a capability hierarchy corresponding to a first capability at a second network node in the first list matches the first capability hierarchy.
[0082] In practical application, when generating the first list, the first network node needs to simultaneously consider the distance between the second network node and the third network node, and ensure as much as possible 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 facilitate the first capability to be called up more quickly. And when selecting a second network node for the third network node from the first list, the real-time state information of the second network node is combined, and if the provided first capabilities all correspond to the first capability hierarchy, the second network node with the optimal real-time state is selected, and it is ensured that the selected second network node can provide the optimal first capability to the third network node.
[0083] 5 is a schematic diagram of a network capability invocation flow according to an application embodiment of the present disclosure. As shown in FIG. 5, the network capability invocation process is as follows:
[0084] First, when the first network capability of the first capability hierarchy is arranged in the local API GW of the edge application (ie, the third network node), steps a1 to a3 are executed. In step a1, an edge application initiates a capability invocation request to a local API GW.
[0085] In step a2, the local API GW queries the capability subscription record to determine a first network capability of a first capability hierarchy of the edge application broadband network.
[0086] In step a3, the local API GW returns the capability invocation result to the edge application.
[0087] Next, if the first network capability of the first capability layer is not configured in the local API GW of the edge application (ie, the third network node), steps b1 to b5 are executed. In step b1, an edge application initiates a capability invocation request to an edge capability open management platform (ie, a first network node).
[0088] In step b2, the edge capability open management platform combines the capability subscription record and the location of the edge application to generate a first list that meets the conditions.
[0089] In step b3, the edge capability open management platform sends the first list to the edge capability scheduling center.
[0090] In step b4, the edge capacity scheduling center combines the first list and the real-time state of each network node in the first list, and returns the network node with the most optimal real-time state to the edge capacity management platform.
[0091] Here, the edge capability scheduling center can determine the real-time status of each network node by querying the real-time status of each MEC platform in real time.
[0092] In step b5, the edge capability management platform returns the capability invocation result to the edge application.
[0093] In the embodiment of the present disclosure, the first network node determines a capability hierarchy corresponding to a first capability in each of the at least two second network nodes based on at least one parameter, and the third network node can subscribe to and invoke the first capability corresponding to the first capability hierarchy based on the capability hierarchy of the first network node, thus realizing the subscription and invocation of differentiated capabilities and ensuring the consistency between the invoked capability and the service needs of the application. And, based on the above capability invocation method, even after the application server is switched, the capability that matches the service needs for the application can be invoked based on the capability hierarchy corresponding to the capability subscribed by the application, thereby realizing precise service guarantee.
[0094] To realize the method of the embodiment of the present disclosure, the embodiment of the present disclosure further provides a capability invoking device provided in the first network node, and the device includes a first determining unit 601, as shown in FIG.
[0095] The first determining unit 601 is configured to determine, based on the at least one parameter, a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes.
[0096] Here, in one embodiment, when the first capability is a network capability, the at least one parameter is: a corresponding location of a second network node; and a corresponding access capacity of the second network node to the first capability; and a corresponding response delay of the second network node to the first capability; and and a corresponding performance of the first capability located in the second network node.
[0097] In one embodiment, the first determining unit 601 specifically comprises: When enrolling in a first capability, the device is configured to determine a capability tier corresponding to the first capability at each second network node of the at least two second network nodes based on the at least one parameter.
[0098] In one embodiment, the apparatus further comprises: a first transmitting unit configured to transmit first information to a third network node and to each second network node of the at least two second network nodes; Here, the first information represents a capability hierarchy corresponding to a first capability at each second network node among the at least two second network nodes, and the third network node represents a network node that subscribes to and invokes the first capability.
[0099] In one embodiment, the apparatus further comprises: a second transmitting unit configured to store second information and transmit the second information to each second network node of the at least two second network nodes; Here, the second information represents capabilities subscribed to by the third network node and a corresponding subscribed capability hierarchy.
[0100] In one embodiment, the apparatus further comprises: a second receiving unit configured to receive a first request of a third network node, the first request being used to request invocation of a first capability; a generating unit configured to generate a first list after determining that the third network node subscribes to a first capability corresponding to the first capability hierarchical, the first list including at least one second network node of the at least two second network nodes, and a capability hierarchical corresponding to a first capability at the second network node in the first list being the first capability hierarchical; and a third transmitting unit configured to return third information to the third network node based on the first list, the third information instructing one second network node in the first list such that the third network node transmits the first request to a second network node indicated by the third information.
[0101] In one embodiment, the generating unit specifically comprises: The first list is configured to generate the first list based on a distance between the second network node and the third network node.
[0102] In one embodiment, the apparatus further comprises: 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; The at least one real-time performance parameter is Occupancy rate and Response delay and and at least one of an uplink rate or a downlink rate.
[0103] In practical application, the first determination unit 601, the generation unit and the third determination unit may be realized by a processor in the capability calling device, and the first transmitting unit, the second transmitting unit, the second receiving unit and the third transmitting unit may be realized by a communication interface in the capability calling device.
[0104] To realize the method on the second network node side according to the embodiment of the present disclosure, the embodiment of the present disclosure further provides a capability invocation device provided in the second network node, and as shown in FIG. 7, the device includes a first receiving unit 701 and a second determining unit 702.
[0105] The first receiving unit 701 is configured to receive first information transmitted from a first network node; The second determining unit 702 is configured to determine a corresponding capability tier based on the first information; wherein each second network node of the at least two second network nodes is configured with a first capability; The first information represents a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes, the capability hierarchy being determined by the first network node based on at least one parameter.
[0106] Here, in one embodiment, the device further comprises: a third receiving unit configured to receive a first request transmitted from a third network node, the first request being used to request invocation of a first capability; an invoking unit configured to invoke a first capability corresponding to the first capability hierarchical layer for the third network node based on the first request; Here, the first request is transmitted when the third network node confirms that a first capability of the first capability hierarchy is configured in the second network node.
[0107] In one embodiment, the apparatus further comprises: a fourth receiving unit configured to receive second information transmitted from the first network node; The second information represents capabilities and corresponding capability hierarchies subscribed to by the third network node.
[0108] The calling unit specifically includes: and configured to, after determining based on the second information that the third network node subscribes to a first capability corresponding to the first capability hierarchical layer, invoke, for the third network node, a first capability corresponding to the first capability hierarchical layer based on the first request.
[0109] In practical application, the first receiving unit 701, the third receiving unit and the fourth receiving unit may be realized by a communication interface in the capability calling device, the second determining unit 702 may be realized by a processor in the capability calling device, and the calling unit may be realized by a combination of the processor and the communication interface in the capability calling device.
[0110] To realize the method on the third network node side according to the embodiment of the present disclosure, the embodiment of the present disclosure further provides a capability invocation device provided in the third network node, and as shown in FIG. 8, the device includes a subscription unit 801.
[0111] The subscribing unit 801 is configured to subscribe to a first capability corresponding to a first capability hierarchy to a first network node; Here, the first network capability is configured in at least two second network nodes, and a capability hierarchy corresponding to the first network capability in each of the at least two second network nodes is determined by the first network node based on at least one parameter.
[0112] wherein, in one embodiment, the apparatus further comprises: a fifth receiving unit configured to receive first information transmitted from the first network node, the first information representing a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes; and a fourth transmitting unit configured to transmit a first request to a corresponding network node based on the first information, the first request being used to request invocation of a first capability.
[0113] In one embodiment, the fourth sending unit specifically comprises: sending the first request to a fourth network node when the first information indicates that a first capability corresponding to the first capability hierarchy is deployed in the fourth network node, the fourth network node indicating a network node accessing the same local area network as the third network node; if the first information indicates that a first capability corresponding to the first capability hierarchy is not deployed in a fourth network node, sending the first request to the first network node, receiving third information returned from the first network node, and sending the first request to a second network node indicated by the third information; Here, the third information indicates one second network node in a first list, the first list includes at least one second network node among the at least two second network nodes, and a capability hierarchy corresponding to a first capability at a second network node in the first list matches the first capability hierarchy.
[0114] In practical application, the subscribing unit 801, the fifth receiving unit and the fourth sending unit may be realized by a communication interface in a capability invoking device.
[0115] In addition, when the capability calling device according to the above embodiment performs capability calling, only the division of each of the above program modules is taken as an example for explanation, and in actual application, the above processing can be assigned to different program modules to complete as necessary, that is, the internal structure of the device is divided into different program modules to complete all or part of the above processing. In addition, the capability calling device according to the above embodiment and the capability calling method embodiment belong to the same concept, and the specific implementation process can be referred to in detail in the method embodiment, and the description will be omitted here.
[0116] Based on the hardware realization of the above program modules, in order to realize the first network node side method related to the embodiment of the present disclosure, the embodiment of the present disclosure further provides a first network node, and as shown in FIG. 9, the first network node 900 includes a first communication interface 901 and a first processor 902.
[0117] The first communication interface 901 can perform information interaction with other network nodes.
[0118] The first processor 902 is connected to the first communication interface 901 to realize information interaction with other network nodes, and is configured to execute the method according to one or more technical solutions on the first network node side when executing a computer program. The computer program is stored in the first memory 903.
[0119] Specifically, the first processor 902 is configured to determine, based on at least one parameter, a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes.
[0120] Here, in one embodiment, the at least one parameter is: a corresponding location of a second network node; and a corresponding access capacity of the second network node to the first capability; and a corresponding response delay of the second network node to the first capability; and and a corresponding performance of the first capability located in the second network node.
[0121] In one embodiment, the first processor 902 specifically: When enrolling in a first capability, the device is configured to determine a capability tier corresponding to the first capability at each second network node of the at least two second network nodes based on the at least one parameter.
[0122] In one embodiment, the first communication interface 901 is configured to transmit first information to a third network node and to each second network node of the at least two second network nodes; Here, the first information represents a capability hierarchy corresponding to a first capability at each second network node among the at least two second network nodes, and the third network node represents a network node that subscribes to and invokes the first capability.
[0123] In one embodiment, the first processor 902 is configured to store second information; The first communication interface 901 is configured to transmit second information to each second network node of the at least two second network nodes; Here, the second information represents capabilities subscribed to by the third network node and a corresponding subscribed capability hierarchy.
[0124] In one embodiment, the first communication interface 901 is A first request is configured to receive from a third network node, the first request being used to request invocation of a first capability.
[0125] The first processor 902 further comprises: configured to generate a first list after confirming that the third network node subscribes to a first capability corresponding to the first capability hierarchical, the first list including at least one second network node among the at least two second network nodes, and a capability hierarchical corresponding to the first capability at the second network node in the first list is the first capability hierarchical.
[0126] The first communication interface 901 further includes: and configured to return third information to the third network node based on the first list, the third information instructing one second network node in the first list such that the third network node transmits the first request to a second network node indicated by the third information.
[0127] In one embodiment, the first processor 902 generating the first list comprises: generating the first list based on distances between second network nodes and the third network nodes;
[0128] In one embodiment, the first processor 902 further comprises: configured to determine 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 is Occupancy rate and Response delay and and at least one of an uplink rate or a downlink rate.
[0129] It should be noted that the specific processing steps of the first processor 902 and the first communication interface 901 can be understood with reference to the above method.
[0130] Of course, in practical applications, each component in the first network node 900 may be coupled via a bus system 904. The bus system 904 is configured to realize connection communication between these components. In addition to a data bus, the bus system 904 further includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are referred to as the bus system 904 in FIG. 9.
[0131] The first memory 903 in embodiments of the present disclosure is configured to store various types of data to support the operation of the first network node 900. Examples of such data include any computer programs configured to operate on the first network node 900.
[0132] The method according to the embodiment of the present disclosure may be applied to or realized by the first processor 902. The first processor 902 may be an integrated circuit chip having a signal processing capability. In the implementation process, each step of the method may be executed by an integrated logic circuit of hardware or an instruction in the form of software in the first processor 902. The first processor 902 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The first processor 902 may implement or execute each method, step, and logic block diagram described in the embodiment of the present disclosure. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method described in the embodiment of the present disclosure may be combined and directly embodied as being executed and completed by a hardware decode processor, or as being executed and completed by a combination of hardware and software modules in the decode processor. The software module may be located in a storage medium, which is located in the first memory 903, and the first processor 902 reads the information in the first memory 903 and combines with its hardware to complete the steps of the above-mentioned method.
[0133] In an example 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, Micro Controller Units (MCUs), microprocessors, or other electronic components to perform the methods described above.
[0134] Based on the hardware realization of the above program modules, in order to realize the method on the second network node side of the embodiment of the present disclosure, the embodiment of the present disclosure further provides a second network node, and as shown in FIG. 10, the second network node 1000 includes a second communication interface 1001 and a second processor 1002.
[0135] The second communication interface 1001 can perform information interaction with other network nodes.
[0136] The second processor 1002 is connected to the second communication interface 1001 to realize information interaction with other network nodes, and is configured to execute the method according to one or more technical solutions on the second network node side when executing a computer program. The computer program is stored in the second memory 1003.
[0137] Specifically, the second communication interface 1001 is configured to receive first information transmitted from a first network node; the second processor is configured to determine a corresponding capability tier based on the first information; wherein each second network node of the at least two second network nodes is configured with a first capability; The first information represents a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes, the capability hierarchy being determined by the first network node based on at least one parameter.
[0138] Wherein, in one embodiment, the second communication interface 1001 is further configured to receive a first request sent from the third network node, the first request being used to request invocation of a first capability; the second communication interface 1001 is further configured to invoke a first capability corresponding to the first capability hierarchical for the third network node based on the first request; Here, the first request is transmitted when the third network node confirms that a first capability of the first capability hierarchy is configured in the second network node.
[0139] In one embodiment, the second communication interface 1001 further comprises: receiving second information transmitted from the first network node, the second information indicating capabilities and corresponding capability tiers subscribed to by a third network node; and after confirming based on the second information that the third network node subscribes to a first capability corresponding to the first capability hierarchical layer, invoking a first capability corresponding to the first capability hierarchical layer for the third network node based on the first request.
[0140] It should be noted that the specific processing steps of the second processor 1002 and the second communication interface 1001 can be understood with reference to the above method.
[0141] Of course, in practical applications, each component in the second network node 1000 may be coupled via a bus system 1004. The bus system 1004 is configured to realize connection communication between these components. In addition to a data bus, the bus system 1004 further includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are referred to as the bus system 1004 in FIG. 10.
[0142] The second memory 1003 in embodiments of the present disclosure is configured to store various types of data to support the operation of the second network node 1000. Examples of such data include any computer programs configured to operate on the second network node 1000.
[0143] The method according to the embodiment of the present disclosure may be applied to or implemented by the second processor 1002. The second processor 1002 may be an integrated circuit chip having a signal processing capability. In the implementation process, each step of the method may be executed by an integrated logic circuit of hardware or an instruction in the form of software in the second processor 1002. The second processor 1002 may be a general-purpose processor, a DSP, or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The second processor 1002 may implement or execute each method, step, and logic block diagram described in the embodiment of the present disclosure. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method described in the embodiment of the present disclosure may be combined and directly embodied as being executed and completed by a hardware decode processor, or as being executed and completed by a combination of hardware and software modules in the decode processor. The software module may be located in a storage medium, which is located in a second memory 1003, and the second processor 1002 reads the information in the second memory 1003 and combines with its hardware to complete the steps of the above-mentioned method.
[0144] 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 to perform the methods described above.
[0145] Based on the hardware realization of the above program modules, in order to realize the method on the third network node side of the embodiment of the present disclosure, the embodiment of the present disclosure further provides a third network node, and as shown in FIG. 11, the third network node 1100 includes a third communication interface 1101 and a third processor 1102.
[0146] The third communication interface 1101 can perform information interaction with other network nodes.
[0147] The third processor 1102 is connected to the third communication interface 1101 to realize information interaction with other network nodes, and is configured to execute the method according to one or more technical solutions on the third network node side when executing a computer program. The computer program is stored in the third memory 1103.
[0148] Specifically, the third communication interface 1101 is configured to subscribe to a first capability corresponding to a first capability hierarchy to a first network node; wherein the first capability is configured in at least two second network nodes; A capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes is determined by the first network node based on at least one parameter.
[0149] Here, in one embodiment, the third communication interface 1101 further includes: receiving first information transmitted from the first network node, the first information representing a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes; The method is configured to: send a first request to a corresponding network node based on the first information, the first request being used to request invocation of a first capability.
[0150] In one embodiment, the third communication interface 1101 specifically includes: sending the first request to a fourth network node when the first information indicates that a first capability corresponding to the first capability hierarchy is deployed in the fourth network node, the fourth network node indicating a network node accessing the same local area network as the third network node; if the first information indicates that a first capability corresponding to the first capability hierarchy is not deployed in a fourth network node, sending the first request to the first network node, receiving third information returned from the first network node, and sending the first request to a second network node indicated by the third information; Here, the third information indicates one second network node in a first list, the first list includes at least one second network node among the at least two second network nodes, and a capability hierarchy corresponding to a first capability at a second network node in the first list matches the first capability hierarchy.
[0151] Of course, in practical applications, each component in the third network node 1100 may be coupled via a bus system 1104. The bus system 1104 is configured to realize connection communication between these components. In addition to a data bus, the bus system 1104 further includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, various buses are referred to as the bus system 1104 in FIG. 11 .
[0152] The third memory 1103 in the embodiments of the present disclosure is configured to store various types of data to support the operation of the third network node 1100. Examples of these data include any computer programs configured to operate on the third network node 1100.
[0153] The method according to the embodiment of the present disclosure may be applied to or realized by the third processor 1102. The third processor 1102 may be an integrated circuit chip having a signal processing capability. In the implementation process, each step of the method may be executed by an integrated logic circuit of hardware or an instruction in the form of software in the third processor 1102. The third processor 1102 may be a general-purpose processor, a DSP, or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The third processor 1102 may implement or execute each method, step, and logic block diagram described in the embodiment of the present disclosure. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method described in the embodiment of the present disclosure may be combined and directly embodied as being executed and completed by a hardware decode processor, or as being executed and completed by a combination of hardware and software modules in the decode processor. The software module may be located in a storage medium, which is located in a third memory 1103, and the third processor 1102 reads the information in the third memory 1103 and combines with its hardware to complete the steps of the above-mentioned method.
[0154] In an exemplary embodiment, the third network node 1100 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the methods described above.
[0155] In addition, the memory (first memory 903, second memory 1003, third memory 1103) of the embodiment of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Here, the non-volatile memory may 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 magnetic random access memory (FRAM, ferromagnetic random access memory), a flash memory, a magnetic surface memory, an optical disk, or a read only optical disk (CD-ROM, Compact Disc Read-Only Memory). The magnetic surface memory may be a magnetic disk memory or a magnetic tape memory. The volatile memory may be a random access memory (RAM, Random Access Memory) used as an external cache.By way of example and not limitation, many forms of RAM are available, including, for example, static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), SyncLink dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). The memory described in the embodiments of this disclosure is intended to include, but is not limited to, these and any other suitable types of memory.
[0156] In an exemplary embodiment, the embodiment of the present disclosure further provides a storage medium, i.e., a computer storage medium, which is specifically a computer readable storage medium, and includes, for example, a first memory 903 storing a computer program, which can be executed by the first processor 902 of the first network node 900 to complete the steps of the first network node side method described above. Also includes, for example, a second memory 1003 storing a computer program, which can be executed by the second processor 1002 of the second network node 1000 to complete the steps of the first network node side method described above. Also includes, for example, a third memory 1103 storing a computer program, which can be executed by the third processor 1102 of the third network node 1100 to complete the steps of the third network node side method described above. The computer readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.
[0157] Note that "first," "second," etc. do not necessarily denote a particular order or priority but are used to distinguish between similar objects.
[0158] In addition, the technical solutions described in the embodiments of the present disclosure may be arbitrarily combined if they do not conflict with each other.
[0159] The above are merely preferred embodiments of the present disclosure, and are not intended to limit the scope of protection of the present disclosure. [Explanation of symbols]
[0160] 601 First Decision Unit 701 First receiving unit 702 2nd Decision Unit 801 subscription units 900 First Network Node 901 First communication interface 902 First Processor 903 First Memory 904 Bus System 1000 Second Network Node 1001 Second communication interface 1002 Second processor 1003 Second Memory 1004 Bus System 1100 3rd Network Node 1101 3rd communication interface 1102 Third Processor 1103 3rd Memory 1104 Bus System
Claims
1. 1. A capability invocation method for a first network node, comprising: The method comprises: determining a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes based on the at least one parameter; The method further comprises: transmitting first information to a third network node and to each second network node of the at least two second network nodes; A capability invocation method, wherein the first information represents a capability hierarchy corresponding to a first capability at each second network node among the at least two second network nodes, and the third network node represents a network node that subscribes to and invokes the first capability.
2. If the first capability is a network capability, the at least one parameter is: a corresponding network distance between the second network node and the wireless side; and a corresponding access capacity for the first capability of the second network node; and a corresponding response delay of the second network node to the first capability; and and a corresponding capability of the first capability located in the second network node. The method of claim 1.
3. Determining a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes based on the at least one parameter includes: determining a capability tier corresponding to the first capability at each second network node of the at least two second network nodes based on the at least one parameter when registering with the first capability. The method according to claim 1 or 2.
4. The method further comprises: storing second information and transmitting the second information to each second network node of the at least two second network nodes; Here, the second information represents network capabilities subscribed to by the third network node and a corresponding subscribed capability hierarchy. The method of claim 1.
5. The method further comprises: receiving a first request from a third network node, the first request being used to request invocation of a first capability; generating a first list after determining that the third network node subscribes to a first capability corresponding to a first capability tier, the first list including at least one second network node of the at least two second network nodes, and a capability tier corresponding to the first capability at the second network node in the first list being the first capability tier; and returning third information to the third network node based on the first list, the third information including instructing a second network node in the first list such that the third network node transmits the first request to a second network node indicated by the third information. The method of claim 1.
6. Generating the first list comprises: generating the first list based on distances between second network nodes and the third network nodes. The method according to claim 5.
7. The method further comprises: 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 is Occupancy rate and Response delay and and at least one of an uplink rate or a downlink rate. The method according to claim 5.
8. A capability invocation method applied to any one second network node of at least two second network nodes, comprising: Each second network node of the at least two second network nodes is configured with a first capability, and the method further comprises: receiving first information transmitted from a first network node; determining a corresponding competency tier based on the first information; A capability invocation method, wherein the first information represents a capability hierarchy corresponding to a first capability at each second network node among the at least two second network nodes, determined by the first network node based on at least one parameter.
9. The method further comprises: receiving a first request transmitted from a third network node, the first request being used to request invocation of a first capability; invoking a first capability corresponding to a first capability hierarchical level for the third network node based on the first request; Here, the first request is transmitted when the third network node confirms that the second network node is configured with a first capability of the first capability hierarchy. The method according to claim 8.
10. The method further comprises: receiving second information transmitted from the first network node; the second information represents network capabilities and corresponding capability tiers subscribed to by the third network node; Invoking a first capability corresponding to a first capability hierarchical layer for the third network node based on the first request includes: and after determining based on the second information that the third network node subscribes to a first capability corresponding to the first capability tier, invoking a first capability corresponding to the first capability tier for the third network node based on the first request.
10. The method of claim 9.
11. A capability invocation method for a third network node, the method comprising: subscribing to a first network node a first capability corresponding to a first capability tier; wherein the first capability is configured in at least two second network nodes; a capability hierarchy corresponding to a first capability at each of the at least two second network nodes is determined by the first network node based on at least one parameter; The method further comprises: receiving first information transmitted from the first network node, the first information representing a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes; A capability invocation method comprising: sending a first request to a corresponding network node based on the first information, the first request being used to request invocation of a first capability.
12. A capability calling device, a first determining unit configured to determine a capability tier corresponding to a first capability at each second network node of the at least two second network nodes based on the at least one parameter; The apparatus further comprises: a first transmitting unit configured to transmit first information to a third network node and to each second network node of the at least two second network nodes; Here, the first information represents a capability hierarchy corresponding to a first capability at each second network node among the at least two second network nodes, and the third network node represents a network node that subscribes to and invokes the first capability, a capability invocation device.
13. A capability calling device, a first receiving unit configured to receive first information transmitted from a first network node; a second determination unit configured to determine a corresponding competency tier based on the first information; wherein each second network node of the at least two second network nodes is configured with a first capability; A capability invocation device, wherein the first information represents a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes, the capability hierarchy being determined by the first network node based on at least one parameter.
14. A capability calling device, a subscribing unit configured to subscribe to a first capability corresponding to a first capability tier to a first network node; wherein the first capability is configured in at least two second network nodes; a capability hierarchy corresponding to a first capability at each of the at least two second network nodes is determined by the first network node based on at least one parameter; The apparatus further comprises: a fifth receiving unit configured to receive first information transmitted from the first network node, the first information representing a capability hierarchy corresponding to a first capability at each second network node of the at least two second network nodes; A capability invocation device comprising: a fourth transmitting unit configured to transmit a first request to a corresponding network node based on the first information, the first request being used to request the invocation of a first capability.
Citation Information
Patent Citations
Service management method and related device
US20200358673A1
