Capability calling method and communication device

Abstract

The invention provides a capability calling method and a communication device, and the method comprises the steps that a first node sends a first request message to a second node, and the first request message is used for requesting the second node to provide a first capability service for the first node; wherein the first capability is a network capability which can be called and used; further, the first node receives an identifier of a transmission channel between the first node and the second node from the third node, and the transmission channel is used for transmitting a capability calling message corresponding to the first capability. By such a method, a capability requester (a first node) and a capability provider (a second node) can transmit a capability call message about a first capability through a transmission channel established by a third node. Through the capability calling method, capability calling can be carried out among various devices in the communication network architecture, so that a capability calling mode in the communication network architecture is more flexible to meet user requirements and industry requirements.

Description

A capability calling method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a capability calling method and a communication device. Background Art

[0002] Devices in a communications network architecture include terminal devices, core network devices, access network devices, and network-external application functions (AFs). Typically, the capability invocation model between devices includes: terminal devices can only act as a capability caller, invoking the capabilities of core network devices; AFs can also only act as a capability caller, invoking the capabilities of core network devices. This capability invocation model is relatively fixed.

[0003] With the continuous development of technologies such as big data and artificial intelligence (AI), the fixed capability call mode between devices in the communication network architecture is increasingly unable to meet user and industry needs.

[0004] Summary of the Invention

[0005] The present application provides a capability calling method and a communication device, so that various devices in a communication network architecture can call each other's capabilities to meet user needs and industry needs.

[0006] In a first aspect, the present application provides a capability calling method, which includes: a first node sends a first request message to a second node, and the first request message is used to request the second node to provide a first capability service for the first node; wherein the first capability is a network capability (or resource) that can be called and used; further, the first node receives an identifier of a transmission channel between the first node and the second node from a third node, and the transmission channel is used to transmit a capability calling message corresponding to the first capability.

[0007] Based on the method described in the first aspect, the capability requester (first node) and the capability provider (second node) can transmit a capability call message regarding the first capability through the transmission channel established by the third node. Through this capability call method, capability calls can be performed between various devices in the communication network architecture, making the capability call mode in the communication network architecture more flexible to meet user and industry needs.

[0008] In a possible implementation, the first node sends a capability invocation message to the third node, where the capability invocation message is used to invoke the first capability of the second node, and the capability invocation message includes an identifier of the transmission channel.

[0009] In a possible implementation, the aforementioned transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

[0010] In one possible implementation, a first node sends a capability discovery request message to a fourth node, where the capability discovery request message is used to discover a first capability; the fourth node is a network device used to manage capabilities. Furthermore, the first node receives a capability discovery response message from the fourth node, where the capability discovery response message is used to indicate successful discovery of the first capability; and based on the capability discovery response message, the first node sends the first request message to the second node. By implementing this possible implementation, the capability requester needs to submit a capability discovery request to the capability management function before invoking the first capability, thereby enabling the capability management function to centrally manage the capabilities and improve the coordination and security of the capability invocation process.

[0011] In one possible implementation, the capability discovery response message also includes token information corresponding to the second node; and the first request message includes token information corresponding to the second node. By implementing this possible implementation, the security of the capability invocation process can be improved through token information.

[0012] In one possible implementation, the first request message also includes information of the first node and first information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0013] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0014] In one possible implementation, the type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

[0015] In a possible implementation, when the type of the first node is a terminal device or an AF, the first node sends the first request message to the second node through the third node.

[0016] In a second aspect, the present application provides a capability invocation method, the method comprising: a second node receiving a first request message from a first node, the first request message being used to request the second node to provide a first capability service for the first node; the first capability being a network capability (or resource) that can be scheduled for use. The second node sends a first response message to a third node (a network device that establishes a transmission channel), the first response message being used to request establishment of a transmission channel between the first node and the second node, the transmission channel being used to transmit the capability invocation message corresponding to the first capability.

[0017] The beneficial effects of the method provided in the second aspect can be found in the description of the beneficial effects of the method in the first aspect, which will not be repeated here.

[0018] In a possible implementation, the second node receives a capability invocation message from the first node through a transmission channel, where the capability invocation message is used to invoke the first capability of the second node.

[0019] In a possible implementation, the transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

[0020] In one possible implementation, a second node sends a second request message to a fourth node, the second request message being used to register a first capability of the second node; the fourth node is a network device for managing capabilities. The second node receives a second response message from the fourth node, the second response message being used to indicate a registration result of the second node for the first capability.

[0021] In one possible implementation, the second node receives a sixth request message from the fourth node, where the sixth request message is used to query whether the second node can provide the first capability service to the first node; the second node sends a sixth response message to the fifth node, where the sixth response message is used to indicate that the second node can provide the first capability service to the first node.

[0022] In a possible implementation, the sixth response message includes token information corresponding to the second node.

[0023] In one possible implementation, the first request message also includes information of the first node and first information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0024] In one possible implementation, the type of the first capability includes one or more of computing capability, data capability, or perception capability.

[0025] In one possible implementation, the type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

[0026] In a possible implementation, the type of the first node is a terminal device or an AF, and the second node receives the first request message from the first node through a third node.

[0027] In a third aspect, the present application provides a capability invocation method, comprising: a third node receiving a first response message from a second node, the first response message being used to request establishment of a transmission channel between the first node and the second node; the transmission channel being used to transmit a capability invocation message corresponding to a first capability; the first capability being a network capability (or resource) that can be scheduled for use. The third node establishes the transmission channel based on the first response message; and sends an identifier of the transmission channel to the first node.

[0028] The beneficial effects of the method provided in the third aspect can be found in the description of the beneficial effects of the method in the first aspect, which will not be repeated here.

[0029] In one possible implementation, a third node receives a capability call message from a first node, where the capability call message is used to call a first capability of a second node, and the capability call message includes an identifier of a transmission channel; the third node sends the capability call message to the second node via the transmission channel indicated by the identifier of the transmission channel.

[0030] In a possible implementation, the transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

[0031] In one possible implementation, the type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

[0032] In one possible implementation, when the type of the first node is a terminal device or AF, the third node receives a first request message from the first node, where the first request message is used to request the second node to provide a service with a first capability for the first node; the third node sends the first request message to the second node.

[0033] In one possible implementation, the first request message includes information of the first node and first information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0034] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0035] In a possible implementation, the first request message further includes token information corresponding to the second node.

[0036] In a fourth aspect, the present application provides a capability registration method, comprising: a fourth node (a network device for managing capabilities) receiving a second request message from a second node, the second request message being used to register a first capability of the second node; the first capability being a network capability (or resource) that can be scheduled for use. The fourth node sends a second response message to the second node, the second response message being used to indicate the second node's registration result of the first capability.

[0037] Based on the capability registration method described in the fourth aspect, each device in the communication network can register its own capabilities with the network device that manages capabilities (i.e., the fourth node), so that the device can provide capabilities to other devices, making the capability call mode in the communication network more flexible to meet user needs and industry needs.

[0038] In one possible implementation, the fourth node sends a third request message to a fifth node (a network device for managing policy information and / or contract information). The third request message is used to authenticate the second node's authority to register a first capability. The fourth node receives a third response message from the fifth node. The third response message is used to indicate whether the second node is allowed to register the first capability. Furthermore, the fourth node sends a second response message to the second node based on the third response message. By implementing this possible implementation, when registering a capability, the second node can enhance the security of the communication network by authenticating the second node's authority to register the capability.

[0039] In a possible implementation, the fourth node sends a second response message to the second node according to local configuration information; the local configuration information includes indication information of whether to accept the second node's registration of the first capability.

[0040] In a possible implementation, the type of the second node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0041] In one possible implementation, when the second node is a terminal device or an AF, the fourth node receives a second request message from the second node via a sixth node, where the sixth node is used to connect the second node to the core network; and the fourth node sends a second response message to the second node via the sixth node. By implementing this possible implementation, the terminal device or AF can also register capabilities, thereby diversifying capability providers and making capability invocation modes in the communication system more flexible.

[0042] In one possible implementation, the second request message includes information of the second node and first information of the first capability; wherein, the information of the second node includes the identifier of the second node or the type of the second node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0043] In one possible implementation, the type of the first capability includes one or more of computing capability, data capability, or perception capability.

[0044] In one possible implementation, the third request message includes information of the second node and second information of the first capability, where the second information of the first capability includes at least one or more of the following: type of the first capability, name of the first capability, and version of the first capability.

[0045] In a possible implementation, if the registration result is registration failure, the second response message further includes a reason value corresponding to the registration failure; or, if the registration result is registration success, the fourth node stores the first capability of the second node.

[0046] In a fifth aspect, the present application provides a capability registration method, comprising: a second node sending a second request message to a fourth node (a network device for managing capabilities), the second request message being used to register a first capability of the second node; the first capability being a network capability (or resource) that can be scheduled for use. The second node receives a second response message from the fourth node, the second response message being used to indicate the second node's registration result for the first capability.

[0047] The beneficial effects of the method provided in the fifth aspect can be found in the description of the beneficial effects of the method in the fourth aspect, which will not be repeated here.

[0048] In a possible implementation, the type of the second node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0049] In one possible implementation, the type of the second node is a terminal device or an AF; in this case, the second node sends a second request message to the first network device through a sixth node, and the sixth node is used to connect the second node to the core network; and the second node receives a second response message from the fourth node through the sixth node.

[0050] In one possible implementation, the second request message includes information of the second node and first information of the first capability; wherein, the information of the second node includes the identifier of the second node or the type of the second node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0051] In one possible implementation, the type of the first capability includes one or more of computing capability, data capability, or perception capability.

[0052] In a possible implementation, the registration result is registration failure, and the second response message further includes a reason value corresponding to the registration failure.

[0053] In a sixth aspect, the present application provides a capability discovery method, comprising: a fourth node (being a network device for managing capabilities) receiving a fourth request message from a first node, the fourth request message being used to request discovery of a first capability; the first capability being a network capability (or resource) that can be scheduled for use; and the fourth node sending a fourth response message to the first node, the fourth response message being used to indicate a discovery result for the first capability.

[0054] Based on the method provided in the sixth aspect, when the first node (capability requester) has the need to call or discover the first capability, the first node can request the fourth node to discover whether there are other devices in the communication network that can provide the first capability, so that the first node can subsequently call the first capability provided by other nodes, thereby increasing the flexibility of the capability calling mode in the communication network.

[0055] In one possible implementation, the fourth node sends a fifth request message to a fifth node (a network device used to manage policy information and / or contract information). The fifth request message is used to authenticate the first node's authority to discover the first capability. The fourth node receives a fifth response message from the fifth node, which indicates whether the first node is allowed to discover the first capability. Based on the fifth response message, the fourth node sends a fourth response message to the first node. By implementing this possible implementation, the first node can only discover the first capability if the fifth node successfully authenticates the first node's authority, thereby improving the security of the node providing the first capability.

[0056] In a possible implementation, the fourth node sends a fourth response message to the first node according to local configuration information; the local configuration information includes indication information of whether to accept the first capability discovered by the first node.

[0057] In a possible implementation, the type of the first node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0058] In one possible implementation, when the type of the first node is a terminal device or AF; the fourth node receives a fourth request message from the first node through a third node, and the third node is used to connect the first node to the core network; and the fourth node sends a fourth response message to the first node through the third node.

[0059] In one possible implementation, the fourth request message includes information of the first node and third information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the third information of the first capability includes one or more of the following information: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

[0060] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0061] In one possible implementation, the fifth request message includes information of the first node and second information of the first capability; wherein the second information of the first capability includes at least one or more of the following: the type of the first capability, the name of the first capability, and the version of the first capability.

[0062] In a possible implementation, the fourth response message indicates that the discovery result for the first capability is capability discovery failure; the fourth response message also includes a reason value corresponding to the capability discovery failure.

[0063] In one possible implementation, the fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes a capability list corresponding to the first capability, and the capability list includes the first information of the first capability; or, the capability list includes multiple nodes providing the first capability and the first information of the first capability corresponding to each node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0064] In one possible implementation, the fourth response message indicates that the discovery result for the first capability is a successful capability discovery. In this case, the fourth node can also determine the second node, and the second node is used to provide the first capability service to the first node; the fourth node sends a sixth request message to the second node, and the sixth request message is used to query whether the second node can provide the first capability service to the first node; the fourth node receives the sixth response message from the second node, and the sixth response message is used to indicate that the second node can provide the first capability service to the first node. By implementing this possible implementation method, when the fourth node determines that the first node can discover the first capability, the fourth node can also determine the capability provider of the first capability for the first node (i.e., the second node), thereby facilitating the first node to call the first capability.

[0065] In one possible implementation, the fourth node obtains information about the first node's need to invoke the first capability service and, based on this information, determines a second node. This information includes one or more of the following: the first node's service need for the first capability, the location relevance between the first node and the second node providing the first capability, the load on the second node, or the priority level of the first node in selecting the second node to provide the first capability. By implementing this possible implementation, the capability provider (i.e., the second node) identified by the fourth node for the first node is more closely aligned with the first node's needs.

[0066] In a possible implementation, the sixth response message further includes token information corresponding to the second node, and the fourth response message further includes token information.

[0067] In the seventh aspect, the present application provides a capability discovery method, which includes: a first node sends a fourth request message to a fourth node (a network device for managing capabilities), and the fourth request message is used to request the discovery of a first capability; the first capability is a network capability (or resource) that can be scheduled for use; the first node receives a fourth response message from the fourth node, and the fourth response message is used to indicate the discovery result for the first capability.

[0068] The beneficial effects of the method provided in the seventh aspect can be found in the description of the beneficial effects of the method in the sixth aspect, which will not be repeated here.

[0069] In a possible implementation, the type of the first node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0070] In one possible implementation, when the type of the first node is a terminal device or AF; the first node sends a fourth request message to the fourth node through the third node, and the third node is used to connect the first node to the core network; the first node receives a fourth response message from the fourth node through the third node.

[0071] In one possible implementation, the fourth request message includes information of the first node and third information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the third information of the first capability includes one or more of the following information: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

[0072] In a possible implementation, the fourth response message indicates that the discovery result for the first capability is capability discovery failure; the fourth response message also includes a reason value corresponding to the capability discovery failure.

[0073] In one possible implementation, the fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes a capability list corresponding to the first capability, and the capability list includes the first information of the first capability; or, the capability list includes multiple nodes providing the first capability and the first information of the first capability corresponding to each node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0074] In a possible implementation, the fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes token information corresponding to the second node.

[0075] In an eighth aspect, the present application provides an authorization information maintenance method, which includes: a fifth node (a network device for managing contract information and / or policy information) obtains the node's policy information and / or contract information for a first capability; the first capability is a network capability (or resource) that can be called; the fifth node records the node's policy information and / or contract information for the first capability.

[0076] Based on the method provided in the eighth aspect, the network side can record the node's policy information and contract information for the first capability, thereby facilitating the node's authentication when registering, discovering, and calling the first capability, thereby improving the security of the network side's capability management.

[0077] In a possible implementation, the type of the node is one of the following types: terminal device, access network device, application function AF or network function NF.

[0078] In a possible implementation, the node is a terminal device or an AF. In this case, the fifth node receives policy information and / or subscription information from the node through the third node, and the third node is used to connect the node to the core network.

[0079] In a possible implementation, the fifth node sends a request for obtaining policy information and / or subscription information to the node through the third node.

[0080] In one possible implementation, the node is a node requesting to call the first capability, and the fifth node receives an authentication request message from the third node, where the authentication request message is used to identify the node's authority to call the first capability; the fifth node sends an authentication response message to the third node, where the authentication response message is used to indicate whether the node has the authority to call the first capability.

[0081] In one possible implementation, the authentication request message includes node information and second information of the first capability; wherein, the node information includes the node identifier or the node type; the second information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0082] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0083] In one possible implementation, the node is a node requesting to register a first capability, and the fifth node receives a third request message from the fourth node, where the third request message is used to authenticate the node's authority to register the first capability; the fourth node is a network device used to manage capabilities; the fifth node sends a third response message to the fourth node based on the policy information and / or contract information corresponding to the node, where the third response message is used to indicate whether the node is allowed to register the first capability.

[0084] In one possible implementation, the third request message includes node information and second information of the first capability; wherein, the node information includes the node identifier or the node type; the second information of the first capability includes at least one or more of the following: the type of the first capability, the name of the first capability, and the version of the first capability.

[0085] In one possible implementation, the node is a node requesting to discover a first capability, and the fifth node receives a fifth request message sent from the fourth node, where the fifth request message is used to authenticate the node's authority to discover the first capability; the fifth node sends a fifth response message to the fourth node based on the policy information and / or contract information corresponding to the node, where the fifth response message is used to indicate whether the node is allowed to discover the first capability.

[0086] In one possible implementation, the fifth request message includes information about the node and third information about the first capability; wherein the information about the node includes an identifier of the node or a type of the node; and the third information about the first capability includes at least one or more of the following: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

[0087] In the ninth aspect, the present application provides a communication device, which may be a node (or referred to as a node device, including the first node to the fifth node), or a device in a node, or a device that can be used in combination with a node device. The communication device may also be a chip system, which may execute the methods described in the first to eighth aspects. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units corresponding to the above functions. The unit may be software and / or hardware. The operations and beneficial effects performed by the communication device may refer to the methods and beneficial effects described in the first to eighth aspects above, and the repeated parts will not be repeated.

[0088] In a tenth aspect, the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method executed by the node in the method described in the first aspect to the eighth aspect is executed.

[0089] In the eleventh aspect, the present application provides a communication device, which includes a processor and a memory, the memory being used to store computer-executable instructions; the processor being used to execute the computer-executable instructions stored in the memory, so that the communication device executes the method executed by the node in the method described in aspects 1 to 8.

[0090] In the twelfth aspect, the present application provides a communication device, which includes a processor, a memory and a transceiver, wherein the transceiver is used to receive or send signals; the memory is used to store a computer program; and the processor is used to call the computer program from the memory to execute the method executed by the node in the method described in aspects 1 to 8.

[0091] In the thirteenth aspect, the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive computer execution instructions and transmit them to the processor; the processor runs the computer execution instructions to execute the method executed by the node in the method described in the first aspect to the eighth aspect.

[0092] In a fourteenth aspect, the present application provides a computer-readable storage medium, which is used to store computer-executable instructions. When the computer-executable instructions are executed, the node in the method described in aspects 1 to 8 is executed.

[0093] In a fifteenth aspect, the present application provides a communication device, which includes a function or unit for executing the method described in any one of the first to eighth aspects.

[0094] In a sixteenth aspect, the present application provides a computer program product comprising a computer program, which, when executed, enables the node execution method in the method described in aspects one to eight to be implemented.

[0095] In the seventeenth aspect, the present application provides a communication system, which includes the nodes described in the first to third aspects above (i.e., the first node, the second node, and the third node); or, the communication system includes the nodes of the fourth and fifth aspects above (i.e., the second node and the fourth node); or, the communication system includes the nodes of the sixth and seventh aspects above (i.e., the first node and the fourth node); or, the communication system includes the node of the eighth aspect above (i.e., the fifth node). BRIEF DESCRIPTION OF THE DRAWINGS

[0096] FIG1a is a schematic diagram of a network system architecture provided in an embodiment of the present application;

[0097] FIG1b is a schematic diagram of a core network architecture provided in an embodiment of the present application;

[0098] FIG1c is a schematic diagram of another core network architecture provided in an embodiment of the present application;

[0099] FIG2 is a flow chart of a capability calling method provided in an embodiment of the present application;

[0100] FIG3 is a flow chart of a capability registration method provided in an embodiment of the present application;

[0101] FIG4 is a flow chart of a capability discovery method provided in an embodiment of the present application;

[0102] FIG5 is a flow chart of a method for maintaining authorization information provided in an embodiment of the present application;

[0103] FIG6 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0104] FIG7 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0105] In order to make the purpose, technical solutions and advantages of this application clearer, this application will be further described in detail below with reference to the accompanying drawings.

[0106] The terms "first" and "second" and the like in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of operations or units is not limited to the listed operations or units, but may optionally include operations or units not listed, or may optionally include other operations or units inherent to the process, method, product, or apparatus.

[0107] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0108] In the present application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the corresponding relationship between corresponding objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the corresponding objects before and after are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0109] To better understand the embodiments of the present application, the following first introduces the system architecture involved in the embodiments of the present application:

[0110] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), new radio (NR), the 3rd generation partner project (3GPP) service-based network architecture (SBA), and other fifth generation (5G) communication systems or sixth generation (6G) communication systems and other communication systems evolved after 5G.

[0111] Please refer to Figure 1a, which is a schematic diagram of a network system architecture provided by an embodiment of the present application. As shown in Figure 1a, the terminal device can access the wireless network to obtain the services of the external network (such as the data network (DN)) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other terminal devices. The wireless network includes a (radio) access network ((R)AN) and a core network (CN), wherein the (R)AN (hereinafter described as RAN) is used to access the terminal device to the wireless network, and the CN is used to manage the terminal device and provide a gateway for communicating with the DN. The terminal device, RAN, CN and DN involved in the system architecture in Figure 1a are described in detail below.

[0112] 1. Terminal Equipment

[0113] Terminal devices include devices that provide voice and / or data connectivity to users. For example, a terminal device is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.). The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a vehicle-mounted terminal, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable terminal, etc. The embodiments of the present application do not limit the application scenarios. Terminal devices may also sometimes be referred to as terminals, user equipment (UE), access terminals, vehicle-mounted terminals, industrial control terminals, UE units, UE stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, UE terminals, wireless communication devices, UE agents, or UE devices. Terminals may also be fixed or mobile. It is understood that all or part of the functions of the terminals in this application may also be implemented through software functions running on hardware, or through virtualized functions instantiated on a platform (e.g., a cloud platform).

[0114] 2. RAN

[0115] The RAN may include one or more RAN devices (or access network devices). The interface between the access network device and the terminal device may be a Uu interface (or air interface). Of course, in communications evolved after 5G, the names of these interfaces may remain unchanged or may be replaced by other names, and this application does not limit this.

[0116] Access network equipment is a node or device that connects a terminal device to a wireless network. Examples of access network equipment include, but are not limited to, next generation node B (gNB), evolved node B (eNB), next generation eNB (ng-eNB), wireless backhaul equipment, radio network controller (RNC), node B (NB), home evolved node B (HeNB) or home node B (HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, and equipment that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications in 5G communication systems. It may also include centralized units (C-RAN) in cloud radio access network (C-RAN) systems. unit, CU) and distributed unit (distributed unit, DU), network equipment in non-terrestrial network (NTN) communication systems, that is, can be deployed on high-altitude platforms or satellites, etc., and the embodiments of the present application do not make specific limitations on this.

[0117] 3. CN

[0118] The CN may include one or more CN devices (which may be understood as network element devices or network function (NF)).

[0119] Please refer to Figure 1b, which is a structural diagram of a CN provided by this application. The CN in Figure 1b is a schematic diagram of the CN in the 5G network architecture. The CN shown in Figure 1b includes multiple CN devices: network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management (UDM), application function (AF), network control function (NCF), network slice specific authentication and authorization function (NSSAAF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), user plane function (UPF), service communication proxy (SCP), network slice admission control function (NSACF). Among them:

[0120] The AMF is a control plane function provided by the operator network, responsible for access control and mobility management of terminal devices accessing the operator network, such as mobility status management, allocating temporary user identities, and authenticating and authorizing users.

[0121] SMF is a control plane function provided by the operator network, responsible for managing the protocol data unit (PDU) sessions of terminal devices. A PDU session is a channel for transmitting PDUs. Terminal devices need to transmit PDUs to and from the DN through PDU sessions. The SMF is responsible for establishing, maintaining, and deleting PDU sessions. SMF includes session management (such as session establishment, modification, and release, including tunnel maintenance between the UPF and RAN), UPF selection and control, service and session continuity (SSC) mode selection, roaming, and other session-related functions.

[0122] The PCF is a control plane function provided by the operator, including user subscription data management, policy control, charging policy control, and Quality of Service (QoS) control. It is mainly used to provide PDU session policies to the SMF. Among them, the policies may include charging-related policies, QoS-related policies, and authorization-related policies.

[0123] The UPF is a gateway provided by the operator, serving as the gateway for communication between the operator's network and the DN. The UPF includes user-plane-related functions such as packet routing and transmission, packet inspection, quality of service (QoS) processing, uplink packet inspection, and downlink packet storage.

[0124] The UDM is primarily used to manage user subscription and authentication data, as well as perform authentication credit processing, user identity processing, access authorization, registration / mobility management, subscription management, and short message management. In some embodiments, the UDM may also include a unified data repository (UDR). Alternatively, in other embodiments, the 3GPP SBA of the 5G system may also include a UDR. The UDR is used to provide storage and retrieval for PCF policies, storage and retrieval of open structured data, and storage of user information requested by application functions.

[0125] The above-mentioned CN devices may also be referred to as network elements or functional network elements. In a 5G communication system, each functional network element may be the name of each functional network element shown in FIG1b. In a communication system evolved after 5G (such as a 6G communication system), each functional network element may still be the name of each functional network element shown in FIG1b, or may have other names. For example, in a 5G communication system, a policy control network element may be a PCF. In a communication system evolved after 5G (such as a 6G communication system), the policy control function may still be a PCF, or may have other names, which is not limited in this application.

[0126] In Figure 1b, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers can be found in the definitions of relevant standard protocols and are not limited here.

[0127] Please refer to Figure 1c, which is a schematic diagram of another CN architecture provided by this application. In Figure 1c, the CN architecture includes CN devices: connection function, capability exposure function, capability governance function, network policy function, and user signing function. Among them:

[0128] The connection function network element is used to provide network connectivity for terminal devices and connect them to the core network. This connection function network element includes functions such as connection management, mobility management, session management, security management, and user plane data forwarding. In other words, terminal devices can work collaboratively with the network through the connection function. Taking the 5G system as an example, this connection function can be network functions such as AMF, SMF, and UPF.

[0129] The capability exposure function is used to provide a network application program interface (API) for application services outside the core network (i.e., AF). In other words, the AF can use the capability exposure function to call the API provided by the NF to affect the parameter configuration of the network. In one possible implementation, the AF can use the capability exposure function to call capabilities provided by other nodes in the network (e.g., terminal devices, access network devices, NFs, other AFs), and can also use the capability exposure function to provide capabilities to other nodes in the network (e.g., terminal devices, access network devices, NFs, other AFs).

[0130] Capability governance function, which is used to manage and control capabilities in the network. For example, the capability governance function can handle the capability registration, acceptance, discovery, application, authorization and other processes from terminal equipment, access network equipment, AF or NF. Among them, NF is an internal network element function in the CN architecture. For example, NF can be AMF, SMF, UPF, PCF, UDM, etc. in the 5G system. It should be noted that in the following text of this application, only one capability governance function is used to schematically illustrate the capability management and control of all capability types, and it cannot be regarded as a specific limitation of this application. That is to say, in one possible implementation method, different capability types may correspond to different capability governance functions. For example, the capability type of computing capability corresponds to the computing capability governance function, the capability type of data capability corresponds to the data capability governance function, the capability type of perception capability corresponds to the perception capability governance function, etc.

[0131] The network policy function is used to provide execution policies for other network functions under various conditions. The network policy function can affect parameters such as access scheduling, quality of service (QoS) coordination, and billing during business processes. In one possible implementation, the execution policy also includes whether to allow capability registration, discovery, application, authorization, invocation, and billing. Taking the 5G system as an example, the network policy function can be a network function such as PCF.

[0132] The user contract function provides user contract data to other network functions to obtain the user's contracted service parameters and security parameters. In one possible implementation, user contract data includes information such as whether capability registration, discovery, application, authorization, invocation, and billing are permitted. Operators can add, delete, and modify contract data through the business support system (BSS) during the user card and number issuance phase or at subsequent stages.

[0133] It should be noted that the capability governance function can be integrated into the 5G network architecture shown in Figure 1b; in one possible implementation, the capability governance function can be added as a new logical network element, or integrated as a logical function into the existing network function in Figure 1b. Exemplarily, the capability governance function can be integrated into the AMF and SMF. The capabilities mentioned in this application (such as the first capability mentioned below) include but are not limited to: computing capabilities (such as federated learning capabilities, AI computing capabilities, basic computing resources, etc.), data capabilities (including but not limited to data storage capabilities, data collection capabilities, data analysis capabilities, and data processing resources, etc.) or perception capabilities (including but not limited to perception signal transmission capabilities, perception signal reception capabilities, perception signal processing capabilities, etc.) One or more. In other words, the capabilities mentioned in this application may also include other network capabilities in addition to the above capabilities. The capabilities mentioned in this application (including the first capability) are network capabilities (which can also be understood as resources) that can be scheduled for use by other nodes (other nodes other than the node with this capability). For example, node 1 has AI computing capabilities. Node 1 can schedule the use of this AI computing capability for business processing, and node 2 can also schedule the use of node 1's AI computing capability for business processing.

[0134] It should be understood that the capability management function mentioned in this application is only an illustrative name and should not be regarded as a specific limitation. In other words, the capability management function may be named differently in other technical solutions other than this application, or may be other communication devices with the same function.

[0135] It should be stated that, 1. The CN structure shown in Figure 1c is only for the purpose of facilitating the understanding of CN, and only takes the example of each functional network element being separately deployed in the CN. In some possible CN structures, the various functional network elements can be integrated and deployed in combination, for example, the capability governance function and the capability exposure function in Figure 1c are integrated into the same functional network element, or the capability exposure function and the connection function in Figure 1c are integrated into the same functional network element, and so on. This application does not make specific restrictions on this. 2. The core network mentioned later in this application may refer to a functional network element in the core network, or it may be the integration of several functional network elements in the core network, or it may be the integration of all functional network elements in the core network. The core network may be the core network in the 5G communication system shown in FIG1b , or the core network shown in FIG1c , or the core network in other possible communication systems (such as an LTE communication system or a communication system evolved after 5G). 3. The above-mentioned network elements or functions may be network elements in a hardware device, or software functions running on dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform). Optionally, the above-mentioned network elements or functions may be implemented by one device, or jointly by multiple devices, or may be a functional module within a device, and the embodiments of the present application do not specifically limit this.

[0136] 4. DN

[0137] DN, also known as packet data network (PDN), is a network located outside the operator network. The operator network can access multiple DNs. Application servers corresponding to various services can be deployed in the DN to provide a variety of possible services for terminal devices.

[0138] Typically, the capability invocation model between devices in a communication network architecture is relatively fixed. Specifically, terminal devices can only act as capability invokers, invoking the capabilities of core network devices; AFs can also only act as capability invokers, invoking the capabilities of core network devices. However, with the continuous development of technologies such as big data and artificial intelligence (AI), this fixed invocation model is increasingly unable to meet user and industry needs.

[0139] This application provides a capability calling method that enables each device in the network architecture to call each other's capabilities to meet user needs and industry needs. The capability calling method and communication device provided by this application are further introduced below with reference to the accompanying drawings:

[0140] Please refer to Figure 2, which is a flow chart of a capability calling method provided in an embodiment of the present application. As shown in Figure 2, the capability calling method includes the following S201 to S204. The execution subject of the method shown in Figure 2 can be the first node (capability requester), the second node (capability provider) and the third node, or the execution subject of the method shown in Figure 2 can be the chip of the first node, the chip of the second node and the chip of the third node. Figure 2 is illustrated by taking the first node, the second node and the third node as the execution subject of the method as an example. Among them:

[0141] S201: A first node sends a first request message to a second node, wherein the first request message is used to request the second node to provide the first node with a service of a first capability, where the first capability is a network capability (or resource) that can be scheduled for use.

[0142] Among them, the type of the first node is one of the following types: terminal device, access network device, AF or NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF. That is to say, in the communication architecture mentioned in this application, various types of nodes call each other's capabilities. In this communication architecture, each node can not only act as a capability provider, but also as a capability caller (or understood as a capability requester). For example, in one case, terminal device 1 can request to call capability 1 of terminal device 2, AF or NF according to business needs; in another case, terminal device 1 can also provide capability 2 services for terminal device 2, AF or NF.

[0143] In one possible implementation, when a first node requests a second node to provide a first capability service for the first node, the first node may also describe its own identity and the characteristics of the first capability. That is, the first request message includes information about the first node and first information about the first capability. The information about the first node includes an identifier or type of the first node; the first information about the first capability includes one or more of the following: the type of the first capability, the name of the first capability, the version of the first capability, the call parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0144] It should be noted that the type of the first capability is used to describe the category to which the first capability belongs. For example, the type of the first capability is one or more capability types such as computing capability, data capability or perception capability. The name of the first capability can be understood as a detailed description of the first capability under the category to which the first capability belongs. For example, the name of the first capability may be computing capability for federated learning. The calling parameters of the first capability include service feature parameters that describe the first capability, such as latency requirement parameters for the first capability. The interface address of the first capability is the calling address corresponding to the first capability provided by the second node. The network identifier corresponding to the first capability is used to indicate a unique interface address of the first capability, such as DNN or the discovery of the first capability interface address within a specific network (such as a core network).

[0145] It should be understood that NFs can directly interact with other NFs in the core network, while terminal devices require connectivity to interact with other devices in the core network, and AFs require capability exposure to interact with other devices in the core network. That is, when the first node is a NF and the second node is also a NF, the first node can send the first request message directly to the second node. When the first node is a terminal device or an AF, the first node can send the first request message to the second node via a third node; the third node is used to connect the first node to the core network. For example, when the first node is a terminal device, the third node performs connectivity; when the first node is an AF, the third node performs capability exposure.

[0146] In one possible implementation, after receiving the first request message from the first node, the third node may also send an authentication request to a fifth node (a network function for storing user subscription information and / or policy information), requesting the fifth node to verify whether the first node has permission to invoke the first capability. If the fifth node verifies that the first node does not have permission to invoke the first capability, the third node sends a message to the first node indicating that the capability invocation failed. If the fifth node verifies that the first node has permission to invoke the first capability, the third node sends the first request message to the second node, requesting the second node to provide the first node with the first capability service.

[0147] That is to say, in this possible implementation, the first node sends a first request message to the third node; the third node sends an authentication request message to the fifth node based on the first request message, and the authentication request message is used to identify the first node's authority to call the first capability; the third node receives an authentication response message from the fifth node, and the authentication response message is used to indicate whether the first node has the authority to call the first capability; when the authentication response message indicates that the first node has the authority to call the first capability, the third node sends the first request message to the second node.

[0148] In one possible implementation, the authentication request message includes information about the capability requester (i.e., the first node) and second information about the first capability. The first node information includes the type of the first node and / or the identifier of the first node; and the second information about the first capability includes one or more of the type of the first capability, the name of the first capability, the version of the first capability, or call parameters of the first capability.

[0149] S202: The second node sends a first response message to a third node, the first response message being used to request establishment of a transmission channel between the first node and the second node, wherein the transmission channel is used to transmit a capability call message corresponding to the first capability, and the third node is a network device for establishing the transmission channel.

[0150] That is, after the second node receives the first request to call the first capability from the first node, the second node requests the third node to establish a transmission channel with the first node. The first response message includes but is not limited to one or more of the following information: the capability name of the first capability, the capability version of the first capability, the calling parameters of the first capability, the token information, the information of the second node or the information of the first node. It should be noted that when the type of the first node or the type of the second node is a terminal device, the third node includes a connection function; when the type of the first node or the type of the second node is AF, the third node includes a capability exposure function; when the type of the first node and the type of the second node are both NF, the third node can be the first node or the second node itself, or it can be other network element functions other than the first node or the second node.

[0151] Among them, the transmission channel includes a transmission link for signaling interaction, and / or a user plane tunnel for user plane data interaction. It should be understood that, 1. The transmission link for signaling interaction is usually a channel for message interaction (such as request messages and response messages, etc.), and the data packets of the transmitted messages will not be very large. That is to say, the transmission link for signaling interaction can provide a transmission channel for control messages when the first node (capability service request node) calls the first capability of the second node (capability service providing node), such as transmitting necessary control information elements (including instructions for starting or ending the capability service, capability duration, etc.). 2. The user plane tunnel for user plane data interaction is usually a data transmission channel when providing the first capability service, and the transmitted data packets are relatively large. For example, when the first capability service is a data governance service, the first node (capability service request node) may need to obtain a large amount of data from the second node (capability service providing node). At this time, the two parties can complete the data transmission by establishing a user plane channel, that is, establishing a user plane communication channel through a third node (such as a control plane network element).

[0152] In a possible implementation, if the first request message includes the token (also known as token) information of the second node, the second node may verify the token information before sending the first response message to the third node. The verification content includes but is not limited to: verifying whether the token information is authentic (i.e., whether it is the token issued by the second node), checking whether the token information is expired (i.e., the token information has a valid time, and detecting whether the token information has exceeded the valid time), etc. If the second node passes the verification of the token information (i.e., the token information is authentic and valid), the second node sends the first response message to the third node. It should be noted that the method for obtaining the token information can be found in the relevant description in Figure 4, which will not be described in detail here.

[0153] S203: The third node establishes a transmission channel according to the first response message.

[0154] After receiving the first response message from the second node, the third node establishes a transmission channel between the first node and the second node.

[0155] The following takes the third node as the connection function and the first node as the terminal device 1 as an example to explain the establishment of a transmission link for signaling interaction and the establishment of a user plane tunnel for user plane data interaction.

[0156] In Example 1, the transmission channel is a transmission link for signaling interaction. The connection function assigns a capability connection identifier (also known as a capability connection ID) to terminal device 1 and updates the user context corresponding to terminal device 1. If the connection function is an access management function or a mobility management function (such as the AMF in a 5G network), the connection function can update the user's capability service usage information in the user's access management or mobility management context.

[0157] Example 2: The transmission channel is a user plane tunnel for user plane data interaction, and the connection function is to establish a user plane tunnel between the first node and the second node. For example, SMF establishes a link between UPF and AF (ie, the second node) for terminal device 1.

[0158] S204: The third node sends the identifier of the transmission channel to the first node.

[0159] In other words, when the transmission channel includes a transmission link for signaling interaction, the third node feeds back the identifier of the transmission link (or capability connection identifier, capability connection ID) to the first node; when the transmission channel includes a user plane tunnel, the third node feeds back the information of the user plane tunnel (for example, the user plane tunnel identifier) ​​to the first node.

[0160] In one embodiment, the first node sends a capability invocation message for invoking the first capability to the third node, the capability invocation message including an identifier of the transmission channel. Further, the third node sends the capability invocation message to the second node via the transmission channel based on the identifier of the transmission channel.

[0161] For example, the identifier of the transmission channel sent by the third node to the first node is capability 100. In this case, the capability call message sent by the first node to the third node carries the identifier of the transmission channel (i.e., capability 100), so that after the third node receives the capability call message, it forwards the capability call message to the capability providing node (i.e., the second node) corresponding to the identifier of the transmission channel (i.e., capability 100).

[0162] It can be seen that by implementing the capability calling method described in Figure 2 of this application, all types of devices in the communication system can act as capability requesters or as capability providers, making the capability calling mode of the communication system more flexible to meet user and industry needs.

[0163] Since in this application, various types of nodes can serve as capability providers for other nodes, the following describes how various types of devices in the communication network register their own capabilities. Please refer to Figure 3, which is a flow chart of a capability registration method provided in an embodiment of the present application. As shown in Figure 3, the capability registration method includes S301 to S302. The execution subject of the method shown in Figure 3 can be the second node (capability provider) and the fourth node (such as the capability governance function), or the execution subject of the method shown in Figure 3 can be the chip of the second node and the chip of the fourth node. Figure 3 is illustrated by taking the second node and the fourth node as the execution subject of the method as an example. Among them:

[0164] S301: A fourth node receives a second request message from a second node, where the second request message is used to register a first capability of the second node, wherein the first capability is a network capability (or resource) that can be scheduled for use.

[0165] The fourth node is a network device for managing capabilities, for example, the fourth node may be the capability management function in Figure 1c. The second node is of one of the following types: terminal device, access network device, AF, or NF.

[0166] In one possible implementation, when the second node requests the fourth node to register the first capability, the second node may also describe its own information and the characteristics of the first capability requested for registration. That is, the second request message includes the information of the second node and the first information of the first capability. The information of the second node includes the identifier of the second node or the type of the second node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, the network identifier corresponding to the first capability, and the security policy of the first capability. The security policy of the first capability includes but is not limited to the discovery strategy for discovering the first capability of the first node, the calling strategy for calling the first capability of the first node, the indication information of whether to perform security negotiation when calling the first capability of the first node, the application strategy for applying to call the first capability, etc.

[0167] It should be understood that NFs can directly interact with other NFs in the core network, while terminal devices require connectivity to interact with other devices in the core network, and AFs require capability exposure to interact with other devices in the core network. In other words, when the second node is a NF, the second node can directly send the second request message to the fourth node. When the second node is a terminal device or an AF, the second node sends the second request message to the fourth node via a sixth node; the sixth node is used to connect the second node to the core network. For example, when the second node is a terminal device, the sixth node performs connectivity; when the second node is an AF, the sixth node performs capability exposure.

[0168] S302: The fourth node sends a second response message to the second node, where the second response message is used to indicate a registration result of the second node for the first capability.

[0169] When the second node is a NF, the fourth node directly sends the second response message to the second node. When the second node is a terminal device or an AF, the fourth node sends the second response message to the second node via a sixth node; wherein the sixth node is used to connect the second node to the core network.

[0170] In one possible embodiment, before the fourth node sends the second response message to the second node, the fourth node may also send a third request message to the fifth node (a network device for managing policy information and / or contract information), and the third request message is used to request authentication of the second node's permission to register the first capability. The third request message includes information about the second node and the second information about the first capability; the second information about the first capability includes at least one or more of the following: the type of the first capability, the name of the first capability, or the version of the first capability. After the fifth node queries and authenticates the second node's permission to register the first capability, the fifth node sends a third response message to the fourth node, and the third response message is used to indicate whether the second node is allowed to register the first capability. Further, the fourth node sends a second response message to the second node based on the third response message.

[0171] That is, in this possible implementation, after receiving the second request message from the second node, the fourth node requests the fifth node (a network function for storing user contract information and / or policy information) to identify whether the second node has the authority to register the first capability. Furthermore, the fourth node sends a second response message to the second node based on the identification result of the fifth node. For example, if the fifth node identifies that the second node does not have the authority to register the first capability, the fourth node sends a second response message to the second node indicating that the registration failed. If the fifth node identifies that the second node has the authority to register the first capability, the fourth node sends a second response message to the second node indicating that the registration was successful.

[0172] In one possible embodiment, the fourth node also sends a second response message to the second node based on the local configuration information, wherein the local configuration information includes indication information on whether to accept the second node's registration of the first capability. If the local configuration information includes indication information on accepting the second node's registration of the first capability, the fourth node sends a second response message to the second node, and the second response message is used to indicate that the registration result of the second node's registration of the first capability is a successful registration. If the local configuration information includes indication information on not accepting the second node's registration of the first capability, the fourth node sends a second response message to the second node, and the second response message is used to indicate that the registration result of the second node's registration of the first capability is a failed registration.

[0173] In one possible implementation, the fourth node may send a second response message to the second node based on the local configuration information and the third response message. That is, after the fourth node receives the second request message, the fourth node may request the fifth node to identify whether the second node has the authority to register the first capability, and also send a second response message to the second node based on the local configuration information. In this case, when the third response message indicates that the second node is allowed to register the first capability (that is, the second node has the authority to register the first capability), and the local configuration information includes an indication of accepting the second node's registration of the first capability, the second response message will indicate to the second node that its registration of the first capability is successful; otherwise, the second response message indicates that the second node has failed to register the first capability.

[0174] In one possible implementation, when the second response message indicates that the registration result of the second node registering the first capability is a registration failure, the second response message may further include a reason value (or indication information) for indicating the reason for the registration failure. For example, the failure reason value is used to indicate the failure type, where failure type 1 means that the local configuration information does not allow the registration of this capability, and failure type 2 means that there is no permission to register this capability. In this case, if the second response message indicates that the registration failed, and the second response message also carries a reason value (or indication information) of failure type 1, then the second response message indicates that the registration failed because the local configuration information does not allow the second node to register the first capability.

[0175] In one possible implementation, if the second response message indicates that the second node's registration of the first capability is successful, the fourth node records the first capability of the second node. For example, if terminal device 1 successfully registers for the federated learning capability, the fourth node records the federated learning capability of terminal device 1 in the capability information table shown in Table 1.

[0176] Table 1

[0177]

[0178] It can be seen that by implementing the capability registration method described in FIG3 , various types of devices can register their own capabilities on the network side so that they can subsequently provide the capabilities to other nodes in the communication system.

[0179] After the second node registers the first capability, how do other nodes in the communication system discover the first capability of the second node; or, before the first node calls the first capability, how does the first node know whether other nodes in the communication system can provide the first capability. Based on this, the present application also provides a capability discovery method, please refer to Figure 4, which is a flow chart of a capability registration method provided by an embodiment of the present application. As shown in Figure 4, the capability registration method includes S401 to S402. The execution subject of the method shown in Figure 4 can be the first node and the fourth node, or the execution subject of the method shown in Figure 4 can be the chip of the first node and the chip of the fourth node. Figure 4 takes the first node and the fourth node as the execution subject of the method as an example for illustration. Among them:

[0180] S401: A first node sends a fourth request message to a fourth node. The fourth request message is used to request discovery of a first capability, where the first capability is a network capability (or resource) that can be scheduled for use.

[0181] It can be understood that when a first node has a demand for a first capability, the first node sends a fourth request message to a fourth node to request whether other nodes (other than the first node) in the communication system can provide the first capability. The fourth node is a capability management function, such as the capability management function in Figure 1c; the first node is one of the following types: terminal device, access network device, AF, or NF.

[0182] In one possible implementation, when the first node requests to discover the first capability, the first node may also describe its own identity and the characteristics of the first capability. That is, the fourth request message includes the information of the first node and the third information of the first capability. Among them, the information of the first node includes the identifier of the first node or the type of the first node; the third information of the first capability includes one or more of the following information: the type of the node providing the first capability (i.e., the expected type of the node providing the first capability), the type of the first capability, the name of the first capability, and the version of the first capability. It should be understood that when the fourth request message includes the type of the node providing the first capability, the fourth node may give priority to the node of the expected type when subsequently querying the node that can provide the first capability for the first node, or when determining the node that can provide the first capability for the first node.

[0183] It should be understood that NFs can directly interact with other NFs in the core network, while terminal devices require connectivity to interact with other devices in the core network, and AFs require capability exposure to interact with other devices in the core network. In other words, when the first node is a NF, the first node can directly send the fourth request message to the fourth node. When the first node is a terminal device or an AF, the first node sends the fourth request message to the fourth node via a third node; the third node is used to connect the first node to the core network. For example, when the first node is a terminal device, the third node performs connectivity; when the first node is an AF, the third node performs capability exposure.

[0184] S402: The fourth node sends a fourth response message to the first node, where the fourth response message is used to indicate a discovery result for the first capability.

[0185] When the first node is a NF, the fourth node directly sends the fourth response message to the first node. When the first node is a terminal device or an AF, the fourth node sends the fourth response message to the first node via a third node; wherein the third node is used to connect the first node to the core network.

[0186] It should be noted that the fourth request message can be a subscription message. That is to say, the fourth request message sent by the first node to the fourth node is not limited to immediately obtaining the service of the first capability, but rather gives a subscription request. For example, when the first node sends a fourth request message to the fourth node to request the discovery of the first capability provided by other nodes, the fourth node finds that no node can currently provide the first capability based on the fourth request message. Then, when a node (such as the second node) subsequently registers the first capability, the fourth node can send a fourth response message to the first node in response to the discovery result of the first capability.

[0187] In one possible embodiment, before the fourth node sends a fourth response message to the first node, the fourth node may also send a fifth request message to the fifth node (for managing policy information and / or contract information), and the fifth request message is used to authenticate the authority of the first node to discover the first capability. The fifth request message includes information about the first node and third information about the first capability; the third information about the first capability includes at least one or more of the following: the type of node providing the first capability, the type of the first capability, the name of the first capability, or the version of the first capability. After the fifth node queries and authenticates the authority of the first node to discover the first capability, the fifth node sends a fifth response message to the fourth node, and the fifth response message is used to indicate whether the first node is allowed to discover the first capability. Further, the fourth node sends a fourth response message to the second node based on the fifth response message.

[0188] That is, in this possible implementation, after the fourth node receives the fourth request message from the first node, it requests the fifth node (a network function for storing user contract information and / or policy information) to identify whether the first node has the authority to discover the first capability. Furthermore, the fourth node sends a fourth response message to the first node based on the identification result of the fifth node. For example, if the first node does not have the authority to discover the first capability after identification by the fifth node, the fourth node sends a fourth response message indicating a capability failure to the first node. If the first node has the authority to discover the first capability after identification by the fifth node, the fourth node sends a fourth response message indicating a successful capability discovery to the first node.

[0189] In one possible embodiment, the fourth node further sends a fourth response message to the first node based on the local configuration information, wherein the local configuration information includes indication information of whether to accept the first node's discovery of the first capability. If the local configuration information includes indication information of accepting the first node's discovery of the first capability, the fourth node sends a fourth response message to the first node, where the fourth response message is used to indicate that the first node successfully discovered the first capability. If the local configuration information includes indication information of not accepting the first node's discovery of the first capability, the fourth node sends a fourth response message to the first node, where the fourth response message is used to indicate that the first node failed to discover the first capability.

[0190] In one possible implementation, the fourth node may send a fourth response message to the first node based on the local configuration information and the fifth response message. That is, after the fourth node receives the fourth request message, the fourth node may request the fifth node to identify whether the first node has the authority to discover the first capability, and also send a fourth response message to the first node based on the local configuration information. In this case, when the fifth response message indicates that the first node is allowed to register to discover the first capability (that is, the first node has the authority to discover the first capability), and the local configuration information includes an indication of accepting the first node's discovery of the first capability, the fourth response message will indicate to the first node that it has successfully discovered the first capability; otherwise, the fourth response message indicates that the first node has failed to discover the first capability.

[0191] In one possible implementation, when the fourth response message indicates that the first node failed to discover the first capability, the fourth response message may further include a reason value (or indication information) for indicating the reason for the discovery failure. For example, the failure reason value is used to indicate the failure type, where failure type 1 means that the local configuration information does not allow the discovery of this capability, and failure type 2 means that there is no authority to discover this capability. In this case, if the fourth response message indicates that the registration failed, and the fourth response message also carries a reason value (or indication information) for failure type 1, then the fourth response message indicates that the registration failed because the local configuration information does not allow the first node to discover the first capability.

[0192] In a possible implementation, when the fourth response message indicates that the first node has successfully discovered the first capability, the fourth response message may further include a capability list corresponding to the first capability. The capability list of the first capability includes first information about the first capability; the first information about the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, or the network identifier corresponding to the first capability. Alternatively, the capability list of the first capability includes multiple nodes that can provide the first capability and the first information about the first capability corresponding to each node.

[0193] That is, in this possible implementation, when the fourth response message indicates that the first capability has successfully discovered the first capability, the fourth response message indicates to the first node the characteristic information of the first capability that can be provided by other nodes in the communication system (for example, the version of the first capability that can be provided). Alternatively, the fourth response message may also indicate to the first node the nodes in the communication system that can provide the first capability for the first node, as well as the characteristic information of the first capability that each node can provide.

[0194] In a possible embodiment, when the fourth response message indicates that the first node has successfully discovered the first capability, the fourth response message may also indicate information about the second node that provides the capability to the first node, and the first information about the first capability provided by the second node. That is, when determining that the first node can discover the first capability, the fourth node determines the second node that provides the first capability service to the first node. Further, the fourth node sends a sixth request message (or query request message) to the second node, and the sixth request message is used to query whether the second node can provide the first capability service to the first node. The second node sends a sixth response message to the fourth node, and the sixth response message is used to indicate whether the first capability service can be provided to the first node. When the sixth response message indicates that the second node can provide the first capability service to the first node, the fourth response message may also indicate information about the second node and the first information about the first capability corresponding to the second node.

[0195] Exemplarily, when the first node can discover the first capability, the fourth node queries from the maintained capability information table that the nodes that have registered the first capability include: node 1 and node 2. The fourth node sends a sixth request message to node 1, requesting to provide the first capability for the first node. Further, node 1 can determine whether it can provide the first capability for the first node based on its own situation (processor load, ongoing business needs or upcoming business needs, etc.). When node 1 determines that it can provide the first node with the service of the first capability, node 1 sends a sixth response message (or query response message) to the fourth node. The sixth response message is used to indicate that node 1 can provide the first node with the service of the first capability. Further, the fourth node sends the characteristics of the first capability provided by node 1 (i.e., the first information of the first capability) to the first node, so that the subsequent first node can request to call the first capability of node 1 based on the characteristics of the first capability provided by node 1.

[0196] In one possible implementation, when the second node agrees to provide (or is understood to be able to provide) the first node with the first capability service, the sixth response message sent by the second node to the fourth node also includes the token information corresponding to the second node. Furthermore, the fourth response message sent by the fourth node to the first node may also include the token information. The token information is used by the second node to verify the identity of the first node when the first node subsequently requests to invoke the first capability of the second node. The token information may include the second node's key or validity period, etc.

[0197] The following further describes a manner in which the fourth node determines the second node (a node that provides the first capability service to the first node) from a plurality of nodes that can provide the first capability.

[0198] Method 1: The fourth node obtains the requirement information of the first node to call the first capability, and determines the second node based on the requirement information.

[0199] The demand information includes one or more of the following information: the business demand of the first node for the first capability, the location correlation demand between the first node and the second node providing the first capability, the load condition of the second node or the priority of the first node in selecting the second node providing the first capability.

[0200] It is understood that the service requirements of the first node for the first capability include, but are not limited to, transmission delay requirements when invoking the first capability, packet loss rate requirements when invoking the first capability, and QoS requirements when invoking the first capability. The location correlation requirements between the first node and the second node providing the first capability include, but are not limited to, requirements for the data transmission distance between the first node and the second node (i.e., the node providing the first capability) (e.g., requiring the data transmission distance to be as short as possible) and the number of intermediate nodes between the first and second nodes (e.g., requiring the number of intermediate nodes to be as small as possible). The load of the second node includes, but is not limited to, requirements for the number of nodes served by the second node as a capability provider (e.g., requiring the number of capability requesting nodes simultaneously served by the second node to be less than a certain threshold to ensure the processing performance of the second node) and the processor load of the second node. The priority of the second node selected by the first node to provide the first capability refers to the priority of the node type of the second node that the first node expects to provide the first capability. For example, the priority of the second node required to provide the capability to the first node is, from high to low, NF, access network device, AF, and terminal device.

[0201] It should be noted that the method in which the fourth node obtains the demand information of the first node calling the first capability includes but is not limited to: 1. When requesting to discover the first capability, the first node actively describes the demand for calling the first capability to the fourth node. For example, the fourth request message also carries the demand information of the first node calling the first capability. 2. After the first node requests to discover the first capability, the fourth node sends a demand information acquisition request to the first node to obtain the demand of the first node calling the first capability. 3. The fourth node analyzes the demand information of the first node calling the first capability based on the business characteristics of the first node. 4. The fourth node obtains the demand information of the first node calling the first capability from other nodes (nodes that have a communication connection with the first node).

[0202] Method 2: The fourth node does not obtain the requirement information of the first node to call the first capability, and determines the second node according to a preset criterion.

[0203] The preset criteria can be adjusted according to the application scenario and are not specifically limited in this application. For example, the preset criteria may be specified in the protocol or pre-configured by the operator. The preset criteria include, but are not limited to, transmission resource conservation criteria (for example, requiring as few intermediate nodes as possible between the capability requester and the capability service provider), service optimization criteria (for example, ensuring that the distance between the capability requester and the capability service provider is close to reduce transmission delay), etc.

[0204] For example, the fourth node has the function of obtaining the location information of each node. When node 1 and node 2 can both provide the first capability, the fourth node determines that the distance 1 between node 1 and the first node is less than the distance 2 between node 2 and the first node. In order to improve the service quality of providing the first capability to the first node, the fourth node determines node 1 as the second node.

[0205] Method three: the fourth node obtains the prior information of the first node and determines the second node based on the prior information.

[0206] The prior information includes but is not limited to node type statistics of nodes that have provided capabilities to the first node before the first node sends the fourth request message, business demand statistics of the first node, etc.

[0207] For example, based on prior information about the first node, the fourth node determines that the first node typically obtains capabilities from NF-type nodes. If both Node 1 and Node 2 can provide the first capability to the first node, with Node 1 being NF-type and Node 2 being AF-type, the fourth node can determine, based on this prior information, that Node 1 is the second node to provide the first capability to the first node.

[0208] Through the capability discovery method described in FIG4 , the capability requester can discover the capabilities that other nodes in the communication system can provide according to its own needs, thereby enabling it to flexibly call the capabilities provided by various nodes to meet the needs of the capability requester.

[0209] Next, based on the method described in Figures 2 to 4, the authorization information maintenance process of the node in this application is introduced. Please refer to Figure 5, which is a flow chart of an authorization information maintenance method provided by an embodiment of the present application. As shown in Figure 5, the authorization information maintenance method includes S501 to S502. The execution subject of the method shown in Figure 5 can be the fifth node (a network function for storing user contract information and / or policy information), or the execution subject of the method shown in Figure 5 can be the chip of the fifth node. Figure 5 is illustrated by taking the fifth node as the execution subject of the method as an example. Among them:

[0210] S501: A fifth node obtains policy information and / or contract information of a node for a first capability. The first capability is a network capability (or resource) that can be called.

[0211] That is, the fifth node obtains the policy information and / or subscription information of the node (including the aforementioned first node and second node) for registering, discovering, and calling the first capability. The type of the node is one of the following types: terminal device, access network device, AF, or NF.

[0212] The following describes a manner in which the fifth node obtains the policy information and / or contract information of the node for the first capability.

[0213] Method 1: The fifth node obtains the policy information and / or subscription information of the node for the first capability from the operator side.

[0214] Specifically, the fifth node may obtain the policy information and / or contract information of the node for the first capability from the operator's Basic Service Set (BSS) or Operation Support Systems (OSS).

[0215] For example, taking the node type as a terminal device, when the terminal device is registered on the operator side, the contract of the terminal device records that the terminal device can provide federated learning capabilities, image recognition capabilities, data processing capabilities, etc.

[0216] Method 2: When the node is a terminal device or AF, the node can send policy information and / or subscription information for the first capability to the fifth node through the node that connects the node to the core network (such as the aforementioned third node or sixth node).

[0217] For example, taking the type of the node as a terminal device, the terminal device can sign a new / modify capability service through the interface operation as an example. When the terminal device has the ability to provide federated learning, the terminal device can provide the ability to train AI models for other nodes. In this case, the user can choose to add a federated learning capability (i.e., add new contract information) to the terminal device on the operation interface of the terminal device. Furthermore, the terminal device sends the new contract information to the connection function through the access network device, so that the connection function sends the new contract information to the fifth node. It should be noted that the new contract information can be sent through a non-access stratum (NAS) message, or it can be sent to the connection function through a user-side data packet (for example, the terminal sends it to the SMF through the UPF), and this application does not specifically limit this.

[0218] Method 3: When the node is a terminal device or an AF, the fifth node may send a policy information and / or subscription information acquisition request to the fifth node through the node that connects the node to the core network (e.g., the aforementioned third node or sixth node) to obtain the policy information and / or subscription information for the first capability. Furthermore, the node may send the policy information and / or subscription information for the first capability to the fifth node through the node that connects the node to the core network (e.g., the aforementioned third node or sixth node).

[0219] In one possible implementation, the fifth node receives a user authorization information query request from the fourth node, where the user authorization information query request includes information about the queried node (such as the type of the node or the identifier of the node) and the capability type and capability call parameters of the queried capability. Furthermore, the fifth node sends a policy information and / or subscription information acquisition request to the fifth node via a node that connects the node to the core network (such as the aforementioned third node or sixth node). Furthermore, the node may send policy information and / or subscription information for the first capability to the fifth node via a node that connects the node to the core network (such as the aforementioned third node or sixth node).

[0220] For example, take the type of the node as a terminal device. The fourth node (such as the capability governance function) sends a query to the fifth node (such as the user contract function) for the user contract information of the federated learning capability of the terminal device 1. The fifth node sends a policy information and / or contract information acquisition request about the federated learning capability to the terminal device 1 through the connection function. Furthermore, the user can choose to add a new federated learning capability (i.e., new contract information) to the terminal device 1 through the interface of the terminal device 1. Furthermore, the terminal device sends the new contract information to the fifth node through the connection function, so that the fifth node sends the new contract information to the fourth node.

[0221] S502: The fifth node stores (or is understood to record) the policy information and / or contract information of the node for the first capability.

[0222] The fifth node obtains the policy information and / or contract information of the node for the first capability through method 1, method 2 or method 3 in S501, and stores (or is understood to record) the policy information and / or contract information of the node for the first capability.

[0223] Further, when the fifth node can authenticate the node's authority to call the first capability based on the node's policy information and / or contract information for the first capability, for example, the fifth node in S201 authenticates whether the first node has the authority to call the first capability; or, authenticates the node's authority to register the first capability, for example, the fifth node in S302 authenticates whether the second node has the authority to register the first capability; or, authenticates the node's authority to discover the first capability, for example, the fifth node in S302 authenticates whether the first node has the authority to discover the first capability.

[0224] In summary, the authorization information maintenance method shown in FIG5 can improve the security of the authorization information of various nodes.

[0225] Please refer to Figure 6, which shows a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device shown in Figure 6 can be a node (first node to fifth node), or a device in a node, or a device that can be used in conjunction with a node. The communication device shown in Figure 6 may include a communication unit 601 and a processing unit 602. Specifically, the processing unit 602 is used to process data, which may be data received by the communication unit 601, and the processed data may also be sent by the communication unit 601;

[0226] In one embodiment, the communication device 600 is a first node, a device in the first node, or a device that can be used in conjunction with the first node, wherein:

[0227] Communication unit 601 is used to send a first request message to the second node, where the first request message is used to request the second node to provide a first capability service to the first node; wherein the first capability is a network capability (or resource) that can be called and used; and receive an identifier of a transmission channel between the first node and the second node from a third node, where the transmission channel is used to transmit a capability call message corresponding to the first capability.

[0228] In a possible implementation, the communication unit 601 is configured to send a capability invocation message to the third node, where the capability invocation message is used to invoke the first capability of the second node, and the capability invocation message includes an identifier of the transmission channel.

[0229] In a possible implementation, the transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

[0230] In one possible implementation, communication unit 601 is further configured to send a capability discovery request message to a fourth node, the capability discovery request message being used to discover the first capability; the fourth node is a network device configured to manage capabilities. Communication unit 601 is further configured to receive a capability discovery response message from the fourth node, the capability discovery response message being used to indicate successful discovery of the first capability; and communication unit 601 is further configured to send the first request message to the second node based on the capability discovery response message.

[0231] In one possible implementation, the capability discovery response message also includes token information corresponding to the second node; and the first request message includes token information corresponding to the second node. By implementing this possible implementation, the security of the capability invocation process can be improved through token information.

[0232] In one possible implementation, the first request message also includes information of the first node and first information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0233] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0234] In one possible implementation, the type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

[0235] In a possible implementation, when the type of the first node is a terminal device or an AF, the communication unit 601 is further configured to send the first request message to the second node through the third node.

[0236] In one embodiment, the communication device 600 is a second node, a device in the second node, or a device that can be used in conjunction with the second node, wherein:

[0237] Communication unit 601 is configured to receive a first request message from a first node, requesting a second node to provide the first node with a service of a first capability; the first capability being a network capability (or resource) that can be scheduled for use. Communication unit 601 is further configured to send a first response message to a third node (a network device that establishes a transmission channel), requesting establishment of a transmission channel between the first node and the second node, the transmission channel being used to transmit a capability invocation message corresponding to the first capability.

[0238] In a possible implementation, the communication unit 601 is further configured to receive a capability invocation message from the first node through a transmission channel, where the capability invocation message is used to invoke the first capability of the second node.

[0239] In a possible implementation, the transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

[0240] In one possible implementation, the communication unit 601 is also used to send a second request message to the fourth node, where the second request message is used to register the first capability of the second node; the fourth node is a network device for managing capabilities; the communication unit 601 is also used to receive a second response message from the fourth node, where the second response message is used to indicate the registration result of the second node for the first capability.

[0241] In one possible implementation, the communication unit 601 is also used to receive a sixth request message from the fourth node, where the sixth request message is used to query whether the second node can provide the first capability service to the first node; the communication unit 601 is also used to send a sixth response message to the fifth node, where the sixth response message is used to indicate that the second node can provide the first capability service to the first node.

[0242] In a possible implementation, the sixth response message includes token information corresponding to the second node.

[0243] In one possible implementation, the first request message also includes information of the first node and first information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0244] In one possible implementation, the type of the first capability includes one or more of computing capability, data capability, or perception capability.

[0245] In one possible implementation, the type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

[0246] In a possible implementation, the type of the first node is a terminal device or an AF, and the second node receives the first request message from the first node through a third node.

[0247] In one embodiment, the communication device 600 is a third node, a device in a third node, or a device that can be used in conjunction with a third node, wherein:

[0248] Communication unit 601 is configured to receive a first response message from a second node, the first response message being used to request establishment of a transmission channel between the first and second nodes; the transmission channel being used to transmit a capability invocation message corresponding to a first capability; the first capability being a network capability (or resource) that can be scheduled for use. Processing unit 602 is configured to establish the transmission channel based on the first response message; communication unit 601 is further configured to send an identifier of the transmission channel to the first node.

[0249] In one possible implementation, the communication unit 601 is further used to receive a capability call message from the first node, where the capability call message is used to call the first capability of the second node, and the capability call message includes an identifier of a transmission channel; the communication unit 601 is further used to send the capability call message to the second node through the transmission channel indicated by the identifier of the transmission channel.

[0250] In a possible implementation, the transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

[0251] In one possible implementation, the type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

[0252] In one possible implementation, when the type of the first node is a terminal device or AF, the communication unit 601 is further used to receive a first request message from the first node, where the first request message is used to request the second node to provide a first capability service to the first node; the communication unit 601 is further used to send the first request message to the second node.

[0253] In one possible implementation, the first request message includes information of the first node and first information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0254] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0255] In a possible implementation, the first request message further includes token information corresponding to the second node.

[0256] In one embodiment, the communication device 600 is a fourth node (a network device for managing capabilities), a device in a fourth node, or a device capable of being used in conjunction with a fourth node, wherein:

[0257] The communication unit 601 is further configured to receive a second request message from the second node, the second request message being used to register a first capability of the second node; the first capability being a network capability (or resource) that can be scheduled for use. The communication unit 601 is further configured to send a second response message to the second node, the second response message being used to indicate a registration result of the first capability by the second node.

[0258] In one possible implementation, the communication unit 601 is also used to send a third request message to the fifth node (a network device for managing policy information and / or contract information), and the third request message is used to authenticate the second node's authority to register the first capability; the communication unit 601 is also used to receive a third response message from the fifth node, and the third response message is used to indicate whether the second node is allowed to register the first capability; the communication unit 601 is also used to send a second response message to the second node through the communication unit 601 based on the third response message.

[0259] In a possible implementation, the processing unit 602 is further configured to send a second response message to the second node through the communication unit 601 according to the local configuration information; the local configuration information includes indication information of whether to accept the second node's registration of the first capability.

[0260] In a possible implementation, the type of the second node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0261] In one possible implementation, when the type of the second node is a terminal device or AF; the communication unit 601 is also used to receive a second request message from the second node through a sixth node, and the sixth node is used to connect the second node to the core network; the communication unit 601 is also used to send a second response message to the second node through the sixth node.

[0262] In one possible implementation, the second request message includes information of the second node and first information of the first capability; wherein, the information of the second node includes the identifier of the second node or the type of the second node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0263] In one possible implementation, the type of the first capability includes one or more of computing capability, data capability, or perception capability.

[0264] In one possible implementation, the third request message includes information of the second node and second information of the first capability, where the second information of the first capability includes at least one or more of the following: type of the first capability, name of the first capability, and version of the first capability.

[0265] In one possible implementation, if the registration result is registration failure, the second response message also includes a reason value corresponding to the registration failure; or, if the registration result is registration success, the communication device also includes a storage unit (not shown in the figure), which is used to store the first capability of the second node.

[0266] In one embodiment, the communication device 600 is a second node, a device in the second node, or a device that can be used in conjunction with the second node, wherein:

[0267] Communication unit 601 is configured to send a second request message to a fourth node (a network device for managing capabilities), the second request message being used to register a first capability of the second node; the first capability being a network capability (or resource) that can be scheduled for use. Communication unit 601 is further configured to receive a second response message from the fourth node, the second response message being used to indicate a registration result of the first capability by the second node.

[0268] In a possible implementation, the type of the second node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0269] In one possible implementation, the type of the second node is a terminal device or AF; the communication unit 601 is also used to send a second request message to the first network device through the sixth node, and the sixth node is used to connect the second node to the core network; the communication unit 601 is also used to receive a second response message from the fourth node through the sixth node.

[0270] In one possible implementation, the second request message includes information of the second node and first information of the first capability; wherein, the information of the second node includes the identifier of the second node or the type of the second node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0271] In one possible implementation, the type of the first capability includes one or more of computing capability, data capability, or perception capability.

[0272] In a possible implementation, the registration result is registration failure, and the second response message further includes a reason value corresponding to the registration failure.

[0273] In one embodiment, the communication device 600 is a fourth node (a network device for managing capabilities), a device in a fourth node, or a device capable of being used in conjunction with a fourth node, wherein:

[0274] The communication unit 601 is configured to receive a fourth request message from the first node, the fourth request message being used to request discovery of a first capability; the first capability being a network capability (or resource) that can be scheduled for use. The communication unit 601 is further configured to send a fourth response message to the first node, the fourth response message being used to indicate a discovery result for the first capability.

[0275] In one possible implementation, the communication unit 601 is also used to send a fifth request message to a fifth node (a network device for managing policy information and / or contract information), and the fifth request message is used to authenticate the authority of the first node to discover the first capability; the communication unit 601 is also used to receive a fifth response message from the fifth node, and the fifth response message is used to indicate whether the first node is allowed to discover the first capability; the fourth node sends a fourth response message to the first node based on the fifth response message.

[0276] In a possible implementation, the processing unit 602 is configured to send a fourth response message to the first node through the communication unit 601 according to the local configuration information; the local configuration information includes indication information of whether to accept the first capability discovery by the first node.

[0277] In a possible implementation, the type of the first node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0278] In one possible implementation, when the type of the first node is a terminal device or AF; the fourth node receives a fourth request message from the first node through a third node, and the third node is used to connect the first node to the core network; and the fourth node sends a fourth response message to the first node through the third node.

[0279] In one possible implementation, the fourth request message includes information of the first node and third information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the third information of the first capability includes one or more of the following information: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

[0280] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0281] In one possible implementation, the fifth request message includes information of the first node and second information of the first capability; wherein the second information of the first capability includes at least one or more of the following: the type of the first capability, the name of the first capability, and the version of the first capability.

[0282] In a possible implementation, the fourth response message indicates that the discovery result for the first capability is capability discovery failure; the fourth response message also includes a reason value corresponding to the capability discovery failure.

[0283] In one possible implementation, the fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes a capability list corresponding to the first capability, and the capability list includes the first information of the first capability; or, the capability list includes multiple nodes providing the first capability and the first information of the first capability corresponding to each node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0284] In one possible implementation, the fourth response message indicates that the discovery result for the first capability is successful capability discovery. The processing unit 602 is further configured to determine a second node, the second node being configured to provide the first capability service for the first node; the communication unit 601 is further configured to send a sixth request message to the second node, the sixth request message being configured to query whether the second node can provide the first capability service for the first node; and the communication unit 601 is further configured to receive a sixth response message from the second node, the sixth response message being configured to indicate that the second node can provide the first capability service for the first node.

[0285] In one possible implementation, the communication unit 601 is further used to obtain demand information for the first node to call the first capability service; the processing unit 602 is further used to determine the second node based on the demand information; wherein the demand information includes one or more of the following information: the first node's business demand for the first capability, the location correlation requirement between the first node and the second node providing the first capability, the load condition of the second node, or the priority of the first node in selecting the second node to provide the first capability.

[0286] In a possible implementation, the sixth response message further includes token information corresponding to the second node, and the fourth response message further includes token information.

[0287] In one embodiment, the communication device 600 is a first node, a device in the first node, or a device that can be used in conjunction with the first node, wherein:

[0288] The communication unit 601 is also used to send a fourth request message to a fourth node (a network device for managing capabilities), and the fourth request message is used to request the discovery of a first capability; the first capability is a network capability (or resource) that can be scheduled for use; the communication unit 601 is also used to receive a fourth response message from the fourth node, and the fourth response message is used to indicate the discovery result for the first capability.

[0289] In a possible implementation, the type of the first node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

[0290] In one possible implementation, when the type of the first node is a terminal device or AF; the communication unit 601 is also used to send a fourth request message to the fourth node through the third node, and the third node is used to connect the first node to the core network; the communication unit 601 is also used to receive a fourth response message from the fourth node through the third node.

[0291] In one possible implementation, the fourth request message includes information of the first node and third information of the first capability; wherein, the information of the first node includes the identifier of the first node or the type of the first node; the third information of the first capability includes one or more of the following information: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

[0292] In a possible implementation, the fourth response message indicates that the discovery result for the first capability is capability discovery failure; the fourth response message also includes a reason value corresponding to the capability discovery failure.

[0293] In one possible implementation, the fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes a capability list corresponding to the first capability, and the capability list includes the first information of the first capability; or, the capability list includes multiple nodes providing the first capability and the first information of the first capability corresponding to each node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0294] In a possible implementation, the fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes token information corresponding to the second node.

[0295] In one embodiment, the communication device 600 is a fifth node (a network device for managing subscription information and / or policy information), a device in the fifth node, or a device capable of being used in conjunction with the fifth node, wherein:

[0296] Communication unit 601 is used to obtain the node's policy information and / or contract information for the first capability; the first capability is a network capability (or resource) that can be called; the communication device also includes a storage unit (not shown in the figure), which is used to record the node's policy information and / or contract information for the first capability.

[0297] In a possible implementation, the type of the node is one of the following types: terminal device, access network device, application function AF or network function NF.

[0298] In a possible implementation, the node is a terminal device or an AF. In this case, the fifth node receives policy information and / or subscription information from the node through the third node, and the third node is used to connect the node to the core network.

[0299] In a possible implementation, the communication unit 601 is further configured to send a policy information and / or subscription information acquisition request to the node through a third node.

[0300] In one possible implementation, the node is a node requesting to call the first capability, and the fifth node receives an authentication request message from the third node, where the authentication request message is used to identify the node's authority to call the first capability; the fifth node sends an authentication response message to the third node, where the authentication response message is used to indicate whether the node has the authority to call the first capability.

[0301] In one possible implementation, the authentication request message includes node information and second information of the first capability; wherein, the node information includes the node identifier or the node type; the second information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

[0302] In one possible implementation, the type of the first capability includes any one of computing capability, data capability, or perception capability.

[0303] In one possible implementation, the node is a node requesting to register a first capability, and the communication unit 601 is further used to receive a third request message from a fourth node, where the third request message is used to authenticate the node's authority to register the first capability; the fourth node is a network device used to manage capabilities; the communication unit 601 is further used to send a third response message to the fourth node based on the policy information and / or contract information corresponding to the node, where the third response message is used to indicate whether the node is allowed to register the first capability.

[0304] In one possible implementation, the third request message includes node information and second information of the first capability; wherein, the node information includes the node identifier or the node type; the second information of the first capability includes at least one or more of the following: the type of the first capability, the name of the first capability, and the version of the first capability.

[0305] In one possible implementation, the node is a node requesting to discover a first capability, and the communication unit 601 is also used to receive a fifth request message sent from a fourth node, where the fifth request message is used to authenticate the node's authority to discover the first capability; the communication unit 601 is also used to send a fifth response message to the fourth node based on the policy information and / or contract information corresponding to the node, where the fifth response message is used to indicate whether the node is allowed to discover the first capability.

[0306] In one possible implementation, the fifth request message includes information about the node and third information about the first capability; wherein the information about the node includes an identifier of the node or a type of the node; and the third information about the first capability includes at least one or more of the following: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

[0307] As shown in Figure 7, a communication device 700 provided in an embodiment of the present application is used to implement the functions of the above-mentioned nodes (one or more of the first to fifth nodes). The device can be a node or a device used in a node. The device used in a node can be a chip system or chip in the node. Among them, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0308] The communication device 700 includes at least one processor 720 for implementing the data processing function of the node in the method provided in the embodiment of the present application. The communication device 700 may also include a communication interface 710 for implementing the transceiver operation of the node in the method provided in the embodiment of the present application. In the embodiment of the present application, the communication interface can be a transceiver, circuit, bus, module or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 710 is used for the device in the communication device 700 to communicate with other devices. The processor 720 uses the communication interface 710 to send and receive data and is used to implement the method described in the above method embodiment.

[0309] The communication device 700 may also include at least one memory 730 for storing program instructions and / or data. The memory 730 is coupled to the processor 720. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, and is used for information exchange between the devices, units, or modules. The processor 720 may operate in conjunction with the memory 730. The processor 720 may execute program instructions stored in the memory 730. At least one of the at least one memory may be included in the processor.

[0310] The specific connection medium between the communication interface 710, processor 720, and memory 730 is not limited in the embodiments of the present application. In Figure 7, the memory 730, processor 720, and communication interface 710 are connected via a bus 740. The bus is represented by a bold line in Figure 7. The connection between other components is only for schematic illustration and is not intended to be limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 7, but this does not mean that there is only one bus or one type of bus.

[0311] When the communication device 700 is specifically a device for a node, for example, when the communication device 700 is specifically a chip or a chip system, the communication interface 710 may output or receive a baseband signal. When the communication device 700 is specifically a node, the communication interface 710 may output or receive a radio frequency signal. In the embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiment of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0312] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, the node execution method in the above method embodiment is implemented.

[0313] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed, the method for node execution in the above method embodiment is implemented.

[0314] The embodiment of the present application further provides a communication system, which includes a first node, a second node, and a third node; or includes a second node and a fourth node; or includes a first node and a fourth node; or includes a fifth node. For example, the communication system includes first to fifth nodes, wherein the first node is used to execute the method executed by the first node in the above method embodiment; the second node is used to execute the method executed by the second node in the above method embodiment; the third node is used to execute the method executed by the third node in the above method embodiment; the fourth node is used to execute the method executed by the fourth node in the above method embodiment; and the fifth node is used to execute the method executed by the fifth node in the above method embodiment.

[0315] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0316] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.

[0317] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A capability calling method, characterized in that: The method is applied to a first node, and includes: Sending a first request message to a second node, where the first request message is used to request the second node to provide a service with a first capability for the first node; the first capability is a network capability that can be scheduled for use; An identifier of a transmission channel between the first node and the second node is received from a third node, where the transmission channel is used to transmit a capability invocation message corresponding to the first capability.

2. The method according to claim 1, characterized in that The method further comprises: A capability invocation message is sent to the third node, where the capability invocation message is used to invoke the first capability of the second node, and the capability invocation message includes an identifier of the transmission channel.

3. The method according to claim 1 or 2, characterized in that The transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Sending a capability discovery request message to a fourth node, where the capability discovery request message is used to discover the first capability; the fourth node is a network device for managing capabilities; receiving a capability discovery response message from the fourth node, where the capability discovery response message is used to indicate successful discovery of the first capability; The sending the first request message to the second node includes: Based on the capability discovery response message, a first request message is sent to the second node.

5. The method according to claim 4, characterized in that: The capability discovery response message further includes token information corresponding to the second node; and the first request message includes token information corresponding to the second node.

6. The method according to any one of claims 1 to 5, characterized in that The first request message further includes information of the first node and first information of the first capability; Among them, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

7. The method according to claim 6, characterized in that The type of the first capability includes any one of computing capability, data capability or perception capability.

8. The method according to any one of claims 1 to 7, characterized in that The type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

9. The method according to claim 8, characterized in that When the type of the first node is a terminal device or an AF, the sending a first request message to the second node includes: A first request message is sent to the second node through the third node.

10. A capability calling method, characterized in that: The method is applied to the second node, and the method includes: receiving a first request message from a first node, wherein the first request message is used to request the second node to provide a service of a first capability for the first node; the first capability is a network capability that can be scheduled for use; A first response message is sent to a third node, where the first response message is used to request establishment of a transmission channel between the first node and the second node, where the transmission channel is used to transmit a capability call message corresponding to the first capability; the third node is a network device that establishes the transmission channel.

11. The method according to claim 10, characterized in that: The method further comprises: A capability invocation message is received from the first node through the transmission channel, where the capability invocation message is used to invoke the first capability of the second node.

12. The method according to claim 10 or 11, characterized in that: The transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

13. The method according to any one of claims 10 to 12, characterized in that: The method further comprises: Sending a second request message to a fourth node, where the second request message is used to register the first capability of the second node; the fourth node is a network device for managing capabilities; A second response message is received from the fourth node, where the second response message is used to indicate a registration result of the first capability by the second node.

14. The method according to claim 13, characterized in that: The method further comprises: receiving a sixth request message from the fourth node, where the sixth request message is used to query whether the second node can provide the first capability service for the first node; A sixth response message is sent to the fifth node, where the sixth response message is used to indicate that the second node can provide the first capability service to the first node.

15. The method according to claim 14, characterized in that: The sixth response message includes token information corresponding to the second node.

16. The method according to any one of claims 10 to 15, characterized in that: The first request message further includes information of the first node and first information of the first capability; Among them, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

17. The method according to claim 16, characterized in that: The type of the first capability includes one or more of computing capability, data capability or perception capability.

18. The method according to any one of claims 10 to 17, characterized in that: The type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

19. The method according to claim 18, characterized in that The type of the first node is a terminal device or an AF, and the receiving a first request message from the first node includes: A first request message from the first node is received through the third node.

20. A capability calling method, characterized in that: The method is applied to the third node, and the method further includes: receiving a first response message from the second node, the first response message being used to request establishment of a transmission channel between the first node and the second node; the transmission channel being used to transmit a capability call message corresponding to a first capability; the first capability being a network capability that can be scheduled for use; establishing the transmission channel according to the first response message; Sending the identifier of the transmission channel to the first node.

21. The method according to claim 20, characterized in that The method further comprises: receiving a capability invocation message from the first node, where the capability invocation message is used to invoke the first capability of the second node, and the capability invocation message includes an identifier of the transmission channel; The capability invoking message is sent to the second node through the transmission channel indicated by the identifier of the transmission channel.

22. The method according to claim 20 or 21, characterized in that The transmission channel includes a transmission link for signaling interaction and / or a user plane tunnel for user plane data interaction.

23. The method according to any one of claims 19 to 22, characterized in that: The type of the first node is one of the following types: terminal device, access network device, application function AF or network function NF; the type of the second node is one of the following types: terminal device, access network device, AF or NF.

24. The method according to claim 23, wherein: When the type of the first node is a terminal device or an AF, the method further includes: receiving a first request message from the first node, where the first request message is used to request the second node to provide the first node with a service of the first capability; Send the first request message to the second node.

25. The method according to claim 24, characterized in that The first request message includes information of the first node and first information of the first capability; Among them, the information of the first node includes the identifier of the first node or the type of the first node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

26. The method according to claim 25, characterized in that The type of the first capability includes any one of computing capability, data capability or perception capability.

27. The method according to any one of claims 24 to 26, characterized in that The first request message also includes token information corresponding to the second node.

28. A capability registration method, characterized in that: The method is applied to a fourth node, where the fourth node is a network device for managing capabilities, and includes: receiving a second request message from a second node, where the second request message is used to register a first capability of the second node; the first capability being a network capability that can be scheduled for use; A second response message is sent to the second node, where the second response message is used to indicate a registration result of the first capability by the second node.

29. The method according to claim 28, characterized in that The method further comprises: Sending a third request message to a fifth node, where the third request message is used to authenticate the authority of the second node to register the first capability, and the fifth node is a network device for managing policy information and / or subscription information; receiving a third response message from the fifth node, where the third response message is used to indicate whether the second node is allowed to register the first capability; The sending a second response message to the second node includes: According to the third response message, a second response message is sent to the second node.

30. The method according to claim 28 or 29, characterized in that The sending a second response message to the second node includes: A second response message is sent to the second node according to local configuration information; the local configuration information includes indication information of whether to accept the second node's registration of the first capability.

31. The method according to any one of claims 28 to 30, characterized in that The type of the second node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

32. The method according to claim 31, wherein: In the case where the type of the second node is a terminal device or an AF; The receiving a second request message from the second node includes: receiving, through a sixth node, a second request message from the second node, the sixth node being configured to connect the second node to a core network; The sending a second response message to the second node includes: A second response message is sent to the second node through the sixth node.

33. The method according to any one of claims 28 to 32, characterized in that The second request message includes information of the second node and first information of the first capability; Among them, the information of the second node includes the identifier of the second node or the type of the second node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

34. The method according to claim 33, wherein: The type of the first capability includes one or more of computing capability, data capability or perception capability.

35. The method according to claim 33 or 34, characterized in that The third request message includes information about the second node and second information about the first capability, where the second information about the first capability includes at least one or more of the following: type of the first capability, name of the first capability, and version of the first capability.

36. The method according to any one of claims 28 to 35, characterized in that If the registration result is registration failure, the second response message also includes a reason value corresponding to the registration failure; Alternatively, if the registration result is successful registration, the method further includes: storing the first capability of the second node.

37. A capability registration method, characterized in that: The method is applied to the second node, and the method includes: Sending a second request message to a fourth node, where the second request message is used to register a first capability of the second node; the first capability is a network capability that can be scheduled for use; and the fourth node is a network device for managing capabilities; A second response message is received from the fourth node, where the second response message is used to indicate a registration result of the first capability by the second node.

38. The method according to claim 37, characterized in that The type of the second node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

39. The method according to claim 38, wherein: The type of the second node is a terminal device or an AF; The sending the second request message to the fourth node includes: Sending a second request message to the first network device through a sixth node, where the sixth node is used to connect the second node to the core network; The receiving a second response message from the fourth node includes: A second response message from the fourth node is received through the sixth node.

40. The method according to any one of claims 37 to 39, characterized in that The second request message includes information of the second node and first information of the first capability; Among them, the information of the second node includes the identifier of the second node or the type of the second node; the first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

41. The method according to claim 40, wherein: The type of the first capability includes one or more of computing capability, data capability or perception capability.

42. The method according to any one of claims 37 to 41, characterized in that The registration result is registration failure, and the second response message also includes a reason value corresponding to the registration failure.

43. A capability discovery method, characterized in that The method is applied to a fourth node, where the fourth node is a network device for managing capabilities, and includes: receiving a fourth request message from the first node, wherein the fourth request message is used to request discovery of a first capability; the first capability is a network capability that can be scheduled for use; A fourth response message is sent to the first node, where the fourth response message is used to indicate a discovery result for the first capability.

44. The method according to claim 43, wherein: The method further comprises: Sending a fifth request message to a fifth node, where the fifth request message is used to authenticate the authority of the first node to discover the first capability, and the fifth node is a network device for managing policy information and / or subscription information; receiving a fifth response message from the fifth node, where the fifth response message is used to indicate whether the first node is allowed to discover the first capability; The sending a fourth response message to the first node includes: According to the fifth response message, a fourth response message is sent to the first node.

45. The method according to claim 43 or 44, characterized in that The sending a fourth response message to the first node includes: A fourth response message is sent to the first node according to local configuration information; the local configuration information includes indication information of whether to accept discovery of the first capability by the first node.

46. ​​The method according to any one of claims 43 to 45, characterized in that The type of the first node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

47. The method according to claim 46, wherein: In the case where the type of the first node is a terminal device or an AF; The receiving a fourth request message from the first node includes: receiving, through a third node, a fourth request message from the first node, where the third node is used to connect the first node to a core network; The sending a fourth response message to the first node includes: A fourth response message is sent to the first node through the third node.

48. The method according to any one of claims 43 to 47, wherein: The fourth request message includes information of the first node and third information of the first capability; Among them, the information of the first node includes the identifier of the first node or the type of the first node; the third information of the first capability includes one or more of the following information: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

49. The method according to claim 48, characterized in that The type of the first capability includes any one of computing capability, data capability or perception capability.

50. The method according to claim 48 or 49, characterized in that The fifth request message includes information of the first node and second information of the first capability; wherein the second information of the first capability includes at least one or more of the following: the type of the first capability, the name of the first capability, and the version of the first capability.

51. The method according to any one of claims 42 to 50, characterized in that The fourth response message indicates that a discovery result for the first capability is capability discovery failure; the fourth response message also includes a cause value corresponding to the capability discovery failure.

52. The method according to any one of claims 42 to 50, wherein: The fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes a capability list corresponding to the first capability, the capability list including the first information of the first capability; or the capability list includes multiple nodes providing the first capability and the first information of the first capability corresponding to each node; The first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

53. The method according to any one of claims 42 to 50, characterized in that The fourth response message indicates that the discovery result for the first capability is successful capability discovery; the method further includes: Determining a second node, where the second node is configured to provide a service with a first capability for the first node; Sending a sixth request message to the second node, where the sixth request message is used to query whether the second node can provide the first capability service for the first node; A sixth response message is received from the second node, where the sixth response message is used to indicate that the second node can provide the first node with the service of the first capability.

54. The method according to claim 53, wherein: The determining the second node includes: Obtaining demand information of the first node invoking the first capability service; Based on the demand information, determine the second node; wherein the demand information includes one or more of the following information: the business demand of the first node for the first capability, the location correlation requirement of the first node and the second node providing the first capability, the load condition of the second node, or the priority of the first node in selecting the second node to provide the first capability.

55. The method according to claim 53 or 54, characterized in that The sixth response message further includes token information corresponding to the second node, and the fourth response message further includes the token information.

56. A capability discovery method, characterized in that The method is applied to a first node, and includes: Sending a fourth request message to a fourth node, wherein the fourth request message is used to request discovery of a first capability; the first capability is a network capability that can be scheduled for use; and the fourth node is a network device for managing capabilities; A fourth response message is received from the fourth node, where the fourth response message is used to indicate a discovery result for the first capability.

57. The method according to claim 56, wherein: The type of the first node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

58. The method according to claim 57, wherein: In the case where the type of the first node is a terminal device or an AF; The sending the fourth request message to the fourth node includes: sending a fourth request message to a fourth node through a third node, where the third node is used to connect the first node to a core network; The receiving a fourth response message from the fourth node includes: A fourth response message from the fourth node is received through the third node.

59. The method according to any one of claims 56 to 58, wherein: The fourth request message includes information of the first node and third information of the first capability; Among them, the information of the first node includes the identifier of the first node or the type of the first node; the third information of the first capability includes one or more of the following information: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

60. The method according to any one of claims 56 to 59, characterized in that The fourth response message indicates that a discovery result for the first capability is capability discovery failure; the fourth response message also includes a cause value corresponding to the capability discovery failure.

61. The method according to any one of claims 56 to 59, wherein: The fourth response message indicates that the discovery result for the first capability is successful capability discovery; the fourth response message also includes a capability list corresponding to the first capability, the capability list including the first information of the first capability; or the capability list includes multiple nodes providing the first capability and the first information of the first capability corresponding to each node; The first information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

62. The method according to any one of claims 56 to 59, wherein: The fourth response message indicates that the discovery result of the first capability is successful capability discovery; the fourth response message also includes token information corresponding to the second node.

63. A method for maintaining authorization information, characterized in that: The method is applied to a fifth node, where the fifth node is a network device for managing subscription information and / or policy information, and includes: Obtaining policy information and / or contract information of a node for a first capability; the first capability being a callable network capability; The policy information and / or subscription information of the node for the first capability is recorded.

64. The method according to claim 63, wherein: The type of the node is one of the following types: terminal equipment, access network equipment, application function AF or network function NF.

65. The method according to claim 64, wherein: The node is a terminal device or an AF, and acquiring the policy information and / or subscription information of the node for the first capability includes: The policy information and / or subscription information from the node is received through a third node, and the third node is used to connect the node to a core network.

66. The method according to claim 65, characterized in that The method further comprises: A policy information and / or contract information acquisition request is sent to the node through a third node.

67. The method according to claim 65 or 66, characterized in that The node is a node that requests to invoke the first capability, and the method further includes: receiving an authentication request message from a third node, the authentication request message being used to authenticate the authority of the node to invoke the first capability; An authentication response message is sent to the third node, where the authentication response message is used to indicate whether the node has permission to invoke the first capability.

68. The method according to claim 67, characterized in that The authentication request message includes information of the node and second information of the first capability; The node information includes the node identifier or the node type; The second information of the first capability includes one or more of the following information: the type of the first capability, the name of the first capability, the version of the first capability, the calling parameters of the first capability, the interface address of the first capability, and the network identifier corresponding to the first capability.

69. The method according to claim 68, characterized in that The type of the first capability includes any one of computing capability, data capability or perception capability.

70. The method according to any one of claims 63 to 69, wherein: The node is a node requesting to register the first capability, and the method further includes: receiving a third request message from a fourth node, the third request message being used to authenticate the authority of the node to register the first capability; the fourth node being a network device for managing capabilities; Based on the policy information and / or subscription information corresponding to the node, a third response message is sent to the fourth node, where the third response message is used to indicate whether the node is allowed to register the first capability.

71. The method according to claim 70, wherein: The third request message includes information of the node and second information of the first capability; The information of the node includes the identifier of the node or the type of the node; the second information of the first capability includes at least one or more of the following: the type of the first capability, the name of the first capability, and the version of the first capability.

72. The method according to any one of claims 63 to 71, wherein: The node is a node requesting to discover the first capability, and the method further includes: receiving a fifth request message sent from a fourth node, where the fifth request message is used to authenticate the authority of the node to discover the first capability; Based on the policy information and / or subscription information corresponding to the node, a fifth response message is sent to the fourth node, where the fifth response message is used to indicate whether the node is allowed to discover the first capability.

73. The method according to claim 72, characterized in that The fifth request message includes information of the node and third information of the first capability; The information of the node includes the identifier of the node or the type of the node; the third information of the first capability includes at least one or more of the following: the type of the node providing the first capability, the type of the first capability, the name of the first capability, and the version of the first capability.

74. A communication device, characterized in that comprising a processor and a memory, the processor and the memory being coupled, the processor being configured to implement the method according to any one of claims 1 to 9, or the processor being configured to implement the method according to any one of claims 10 to 19, or the processor being configured to implement the method according to any one of claims 20 to 27; or the processor is used to implement the method according to any one of claims 28 to 36, or the processor is used to implement the method according to any one of claims 37 to 42; or the processor is used to implement the method according to any one of claims 43 to 55, or the processor is used to implement the method according to any one of claims 56 to 62; Or the processor is used to implement the method as described in any one of claims 63-73.

75. A communication device, characterized in that comprising a processor and an interface circuit, the interface circuit being configured to receive a signal from a communication device other than the communication device and transmit the signal to the processor or to send the signal from the processor to the communication device other than the communication device, the processor being configured to implement the method according to any one of claims 1 to 9 through a logic circuit or by executing a code instruction, or the processor being configured to implement the method according to any one of claims 10 to 19 through a logic circuit or by executing a code instruction, or the processor being configured to implement the method according to any one of claims 20 to 27 through a logic circuit or by executing a code instruction; or the processor is used to implement the method according to any one of claims 28 to 36 through a logic circuit or by executing a code instruction, or the processor is used to implement the method according to any one of claims 37 to 42 through a logic circuit or by executing a code instruction; or the processor is used to implement the method according to any one of claims 43 to 55 through a logic circuit or by executing a code instruction, or the processor is used to implement the method according to any one of claims 56 to 62 through a logic circuit or by executing a code instruction; Or the processor is used to implement the method as described in any one of claims 63-73 through logic circuits or executing code instructions.

76. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction, which, when executed by the communication device, implements the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 19, or the method according to any one of claims 20 to 27; or implementing the method according to any one of claims 28 to 36, or implementing the method according to any one of claims 37 to 42; or implementing the method according to any one of claims 43 to 55, or implementing the method according to any one of claims 56 to 62; Or implement the method as described in any one of claims 63-73.

77. A computer program product, characterized in that When a computer reads and executes the computer program product, the computer is enabled to perform the method according to any one of claims 1 to 9, or the computer is enabled to perform the method according to any one of claims 10 to 19, or the computer is enabled to perform the method according to any one of claims 20 to 27; or causing a computer to execute the method according to any one of claims 28 to 36, or causing a computer to execute the method according to any one of claims 37 to 42; or causing a computer to execute the method according to any one of claims 43 to 55, or causing a computer to execute the method according to any one of claims 56 to 62; Or causing a computer to execute the method as described in any one of claims 63-73.

78. A communication system, characterized in that comprising a first node, a second node, and a third node; wherein the first node is used to execute the method according to any one of claims 1 to 9, the second node is used to execute the method according to any one of claims 10 to 19, and the third node is used to execute the method according to any one of claims 20 to 27; Alternatively, the method comprises a second node and a fourth node; wherein the fourth node is used to perform the method according to any one of claims 28 to 36, and the second node is used to perform the method according to any one of claims 37 to 42; Alternatively, the method comprises a first node and a fourth node; wherein the fourth node is used to perform the method according to any one of claims 43 to 55, and the first node is used to perform the method according to any one of claims 56 to 62; Alternatively, it includes a fifth node; wherein the fifth node is used to execute the method as described in any one of claims 63-73.

79. A communication device, characterized in that comprising a function or unit for performing the method according to any one of claims 1 to 9, or performing the method according to any one of claims 10 to 19, or performing the method according to any one of claims 20 to 27; or, comprising a function or unit that performs the method according to any one of claims 28 to 36, or performs the method according to any one of claims 37 to 42; or comprising a function or unit that performs the method according to any one of claims 43 to 55, or performs the method according to any one of claims 56 to 62; Or includes a function or unit that performs the method as described in any one of claims 63-73.

Images