Communication method, communication apparatus, storage medium, and program product

By forwarding requests from the second node and responses from the third node at the first node, cross-device resource access is achieved, solving the problem in existing technologies where API callers cannot access resources across devices.

WO2026007443A1PCT designated stage Publication Date: 2026-01-08ZTE CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/080505
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-07-02
Filing Date
2025-03-04
Publication Date
2026-01-08

AI Technical Summary

Technical Problem

In existing technologies, API callers on one user device cannot access resources on another user device, thus limiting cross-device resource access.

Method used

By receiving request information from the second node and forwarding it to the third node, and receiving response information from the third node and forwarding it to the second node, cross-device resource access can be achieved.

Benefits of technology

This allows API callers from one user device to access resources on another user device, thus overcoming the limitations of cross-device resource access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025080505_08012026_PF_FP_ABST
    Figure CN2025080505_08012026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present disclosure are a communication method, a communication apparatus, a storage medium, and a program product. The communication method comprises: receiving first request information which is sent by a second node, wherein the first request information is used for requesting a resource of a third node; sending the first request information to the third node; receiving first response information which is sent by the third node with respect to the first request information, wherein the first response information comprises resource grant information, and the resource grant information is used for indicating that the second node is granted access to the resource of the third node; and sending the first response information to the second node.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method, communication apparatus, storage medium, and program product

[0001] The present application claims priority to the Chinese patent application No. 202410882999.0, filed on July 02, 2024, the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present disclosure relates to the technical field of communication, and particularly relates to a communication method, a communication apparatus, a storage medium and a program product. BACKGROUND

[0003] In the 3rd generation partnership project (3GPP) Rel-18, the common application programming interface framework (CAPIF) is enhanced, and a resource owner-aware northbound API access (RNAA) architecture is proposed. When discussing the RNAA architecture in the 3GPP Rel-18, for an API (application programming interface) invoker deployed on a user equipment (UE), only the resources (resources) on the same UE are allowed to be accessed, and the API invoker on one UE is not supported to access the resources on another UE. SUMMARY

[0004] Embodiments of the present disclosure provide a communication method, a communication apparatus, a storage medium and a program product, which are used to realize cross-device resource access.

[0005] In order to achieve the above-mentioned purpose, the technical scheme is adopted as follows.

[0006] In a first aspect, a communication method is provided, applied to a first node. The communication method comprises: receiving first request information sent by a second node, the first request information being used to request to access resources of a third node; sending the first request information to the third node; receiving first response information of the first request information sent by the third node, the first response information comprising resource permission information, the resource permission information being used to indicate that the second node is allowed to access the resources of the third node; and sending the first response information to the second node.

[0007] In a second aspect, a communication method is provided, which is applied to a second node. The communication method comprises: sending, to a first node, first request information, the first request information being used to request access to a resource of a third node; and receiving, from the first node, first response information of the third node to the first request information, the first response information comprising resource permission information, the resource permission information being used to indicate that the second node is allowed to access the resource of the third node.

[0008] In a third aspect, a communication method is provided, which is applied to a third node. The communication method comprises: receiving, from a first node, first request information from a second node, the first request information being used to request access to a resource of the third node; and sending, to the first node, first response information to the first request information, the first response information comprising resource permission information, the resource permission information being used to indicate that the second node is allowed to access the resource of the third node.

[0009] In a fourth aspect, a communication apparatus is provided, which is applied to a first node. The communication apparatus comprises: a receiving unit, configured to receive first request information sent by a second node, the first request information being used to request access to a resource of a third node; and a sending unit, configured to send, to the third node, the first request information. The receiving unit is further configured to receive, from the third node, first response information to the first request information, the first response information comprising resource permission information, the resource permission information being used to indicate that the second node is allowed to access the resource of the third node. The sending unit is further configured to send, to the second node, the first response information.

[0010] In a fifth aspect, a communication apparatus is provided, which is applied to a second node. The communication apparatus comprises: a sending unit, configured to send, to a first node, first request information, the first request information being used to request access to a resource of a third node; and a receiving unit, configured to receive, from the first node, first response information of the third node to the first request information, the first response information comprising resource permission information, the resource permission information being used to indicate that the second node is allowed to access the resource of the third node.

[0011] In a sixth aspect, a communication apparatus is provided, which is applied to a third node. The communication apparatus comprises: a receiving unit, configured to receive, from a first node, first request information from a second node, the first request information being used to request access to a resource of the third node; and a sending unit, configured to send, to the first node, first response information to the first request information, the first response information comprising resource permission information, the resource permission information being used to indicate that the second node is allowed to access the resource of the third node.

[0012] In a seventh aspect, a communication apparatus is provided, which comprises a processor and a memory. The memory is coupled to the processor, and is configured to store instructions executable by the processor. The processor is configured to execute the instructions, so that the communication apparatus implements the method provided in any one of the first aspect to the third aspect.

[0013] In an eighth aspect, a computer-readable storage medium is provided, which stores computer instructions, when the computer instructions are executed on a computer, cause the computer to perform the method provided in any one of the first aspect to the third aspect.

[0014] In a ninth aspect, a computer program product is provided, which contains computer programs, when the computer programs are executed on a computer, cause the computer to perform the method provided in any one of the first aspect to the third aspect.

[0015] In the embodiments of the present disclosure, after the first node receives the first request information sent by the second node for requesting to access the resource of the third node, the first node forwards the first request information to the third node, and after receiving the first response information sent by the third node and containing permission of the second node to access the resource of the third node, the first node forwards the first response information to the second node, so that the second node accesses the resource of the third node based on the first response information. In this way, by forwarding the first request information of the second node to the third node through the first node and forwarding the first response information of the third node to the second node through the first node, the cross-device resource access is realized. BRIEF DESCRIPTION OF DRAWINGS

[0016] The accompanying drawings are included to provide a further understanding of the technical scheme of the present disclosure, and constitute a part of the specification, and are used together with the embodiments of the present disclosure to explain the technical scheme of the present disclosure, and do not constitute a limitation on the technical scheme of the present disclosure.

[0017] FIG. 1 is a structural schematic diagram of a communication system according to an embodiment of the present disclosure.

[0018] FIG. 2 is a flow schematic diagram of a communication method according to an embodiment of the present disclosure.

[0019] FIG. 3 is a flow schematic diagram of another communication method according to an embodiment of the present disclosure.

[0020] FIG. 4 is a flow schematic diagram of still another communication method according to an embodiment of the present disclosure.

[0021] FIG. 5 is a flow schematic diagram of still another communication method according to an embodiment of the present disclosure.

[0022] FIG. 6 is a flow schematic diagram of still another communication method according to an embodiment of the present disclosure.

[0023] FIG. 7 is a flow schematic diagram of still another communication method according to an embodiment of the present disclosure.

[0024] FIG. 8 is a flow schematic diagram of still another communication method according to an embodiment of the present disclosure.

[0025] FIG. 9 is a flow diagram of another communication method according to an embodiment of the present disclosure.

[0026] FIG. 10 is a flow diagram of another communication method according to an embodiment of the present disclosure.

[0027] FIG. 11 is a flow diagram of another communication method according to an embodiment of the present disclosure.

[0028] FIG. 12 is a block diagram of a communication apparatus according to an embodiment of the present disclosure.

[0029] FIG. 13 is a block diagram of another communication apparatus according to an embodiment of the present disclosure.

[0030] FIG. 14 is a block diagram of another communication apparatus according to an embodiment of the present disclosure.

[0031] FIG. 15 is a block diagram of a communication apparatus according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of protection of the present disclosure.

[0033] Unless otherwise required by context, the term “comprise” and other forms such as “comprises” and “comprising” are to be construed as open, inclusive, meaning that “comprising” means “including, but not limited to.” In the description of the specification, the terms “one embodiment”, “some embodiments”, “exemplary embodiments”, “example”, “specific example” or “some examples” are intended to mean that the specific features, structures, materials or characteristics related to that embodiment or example are included in at least one embodiment or example of the present disclosure. The illustrative representation of the above terms does not necessarily mean the same embodiment or example. In addition, the specific features, structures, materials or characteristics described can be included in any one or more embodiments or examples in any appropriate manner.

[0034] The terms "first", "second", etc. are used only for the purpose of description and should not be understood as indicating or implying relative importance or a specific number of the technical features indicated. Thus, the features described by the terms "first", "second", etc. can explicitly or implicitly include one or more of the features. In the description of the present disclosure, the meaning of "a plurality of" is two or more, unless otherwise specified.

[0035] In the embodiments of the present disclosure, the words "exemplary" or "for example" are used to describe examples, illustrations, or descriptions. Any embodiment or design scheme described in the embodiments of the present disclosure by the words "exemplary" or "for example" should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words "exemplary" or "for example" are used in the specific manner to present the relevant concept.

[0036] In addition, the use of "based on" means open and inclusive, because the process, step, calculation or other action "based on" one or more stated conditions or values can be based on additional conditions or beyond the stated values in practice.

[0037] With the large-scale commercialization of the 5th generation mobile communication technology (5G) network, the business demand for opening the capabilities of the 5G network is emerging. In order to solve the problem of lack of unified standards when opening the network capabilities, avoid inconsistent opening methods between different operators, and reduce the difficulty of application development for third-party service providers, CAPIF is defined in the Rel-15 standard by 3GPP. CAPIF is a general API opening framework, and the main purpose is to provide a unified and standardized interface for service providers and third-party developers in the 5G network, so that service providers and third-party developers can use the capabilities of the 5G network to develop and provide various services. The CAPIF framework includes the following key logical function entities.

[0038] CAPIF core function (CCF): responsible for the authentication and authorization of API invoker, publishing, saving, discovering, etc. of service API.

[0039] API invoker: third-party developer, used to discover service API information and initiate the call of service API.

[0040] API exposing function: responsible for exposing network functions to third-party developers in the form of API.

[0041] API publishing function: managing publishing and maintenance of APIs.

[0042] To ensure that the network can protect the rights and interests of the resource owner while opening capabilities, and provide fine-grained access control, RNAA is introduced in Rel-18 standards. RNAA is a northbound API access mechanism that can identify and take into account the wishes and authorization status of the resource owner, and ensure that the access of third-party applications to network resources is agreed and authorized by the resource owner while opening network capabilities.

[0043] When discussing the RNAA architecture in 3GPP Rel-18, for API invokers deployed on a UE, only access to resources on the same UE is allowed, and access to resources on another UE by API invokers on a UE is not supported. How to implement access to resources on another UE by API invokers on a UE, that is, how to implement cross-device resource access is a problem to be solved urgently.

[0044] Based on this, the embodiment of the disclosure provides a communication method, a communication device, a storage medium and a program product. After the first node receives the first request information sent by the second node for requesting to access the resource of the third node, the first request information is forwarded to the third node, and after receiving the first response information sent by the third node and containing permission for the second node to access the resource of the third node, the first response information is forwarded to the second node, so that the second node accesses the resource of the third node based on the first response information. In this way, by forwarding the first request information to the third node and forwarding the first response information to the second node through the first node, cross-device resource access is realized.

[0045] The scheme of the embodiment of the disclosure will be introduced below in combination with the drawings.

[0046] The technical scheme provided by the embodiment of the disclosure can be applied to various mobile communication networks, for example, a new radio (NR) mobile communication network using 5G, a future mobile communication network (for example, a 6G wireless communication system) or a multi-communication fusion system, etc., and the embodiment of the disclosure does not limit this.

[0047] FIG. 1 shows a structural schematic diagram of a communication system according to an embodiment of the present disclosure. As shown in FIG. 1, the communication system includes, but is not limited to, an API invoker 11, an API invoker 21, a resource owner function (ROF) 22, a CCF 23, an API exposure function 24, an API publication function 25, and an API management function 26.

[0048] As can be seen from FIG. 1, the API invoker 11 and the API invoker 21 belong to different UEs. The CCF 23 has an authorization function. For descriptions of the CCF 23, the API exposure function 24, and the API publication function 25, reference can be made to the descriptions in the above embodiments, which will not be repeated here. The API exposure function can be referred to as AEF, and the API publication function can be referred to as APF.

[0049] In some embodiments, the API management function 26 is configured to ensure the security and compliance of the API and provide API lifecycle management.

[0050] In some embodiments, the CAPIF APIs in FIG. 1 represent a CAPIF API group, and the service APIs represent a service API group. The PLMN trust domain represents a public land mobile network (PLMN) trust domain.

[0051] It should be understood that FIG. 1 is an exemplary structural diagram. The number of devices included in the communication system shown in FIG. 1 is not limited, for example, the number of API invokers is not limited. In addition to the devices shown in FIG. 1, the communication system shown in FIG. 1 can also include other devices, which are not limited.

[0052] Next, as shown in FIG. 2, an embodiment of the present disclosure provides a communication method applied to a first node, which can be the CCF 23 shown in FIG. 1. The communication method can include the following S101 to S104.

[0053] In S101, first request information sent by a second node is received.

[0054] In some embodiments, the second node sends first request information to the first node in a case that the second node needs to access a resource of the third node. The first request information is used to request the resource of the third node. Accordingly, the first node receives the first request information sent by the second node. The second node can be the API invoker 11 in the communication system shown in FIG. 1, and the third node can be the ROF 22 in the communication system shown in FIG. 1. That is, the API invoker on one UE sends permission request information used to request the resource of the resource owner of another UE to the ROF.

[0055] In some embodiments, the second node and the third node are respectively deployed on different UEs.

[0056] In some embodiments, the first request information comprises at least one of the following: an identity of the second node, an identity of a group to which the second node belongs, an identity of a service related to the group to which the second node belongs, an identity of the third node, and requested resource permission information.

[0057] It should be noted that in the embodiments of the present disclosure, the identity is used to uniquely represent a device. For example, the identity of the second node is used to uniquely represent the second node, and can be a name of the second node, etc. The identity can also be replaced by identity information, and the embodiments of the present disclosure do not limit this.

[0058] In some embodiments, the first request information can further comprise at least one of the following: an identity of a terminal to which the second node belongs, and an identity of a terminal to which the third node belongs.

[0059] In some embodiments, the first request information can also have other names, such as resource owner permission request information, etc. The resource permission information can also have other names, such as resource permission related description information, etc., and the embodiments of the present disclosure do not limit this.

[0060] Taking a communication method provided by the present disclosure as an example applied to a vehicle health monitoring service in vehicle fleet management, the second node and the third node can be respectively located on different vehicle terminals, and the resource of the third node requested to be accessed by the second node can be a location of a vehicle where the third node is located, vehicle health data, etc.

[0061] In S102, the first request information is sent to the third node.

[0062] In some embodiments, after receiving the first request information sent by the second node, the first node sends the first request information to the third node, that is, forwards the first request information sent by the second node to the third node, so that the third node determines whether to allow the second node to access the resource of the third node based on the first request information.

[0063] In S103, the first response information sent by the third node for the first request information is received.

[0064] In some embodiments, after receiving the first request information, the third node sends the first response information for the first request information to the first node in a case that it is determined that the second node is allowed to access the resource of the third node. The first response information includes the resource permission information requested by the first request information, and the resource permission information is used to indicate that the second node is allowed to access the resource of the third node. Accordingly, the first node receives the first response information sent by the third node.

[0065] In some embodiments, the first response information further includes at least one of the following: the identity of the third node, the identity of the second node. As an example, the first response information can further include the identity of the terminal to which the third node belongs, the identity of the terminal to which the second node belongs, and the like.

[0066] In S104, the first response information is sent to the second node.

[0067] In this way, the second node accesses the resource of the third node based on the resource permission information in the first response information.

[0068] In the embodiments of the present disclosure, unlike the API invoker of one UE in the related art which can only access the resource of the same UE and cannot access the resource of other UE, the second node sends the first request information for requesting the resource of the third node to the first node, and in a case that the third node allows the second node to access the resource of the third node, the first response information including the resource permission information is sent to the first node, and then the first node sends the first response information to the second node, so as to facilitate the second node to access the resource of the third node based on the first response information. That is, the API invoker on one UE sends the permission request information for requesting the resource of another UE to the CAPIF core function, and in a case that the resource owner of the another UE allows the API invoker to access the resource of the resource owner, the resource owner sends the response information including the resource permission information to the CAPIF core function, and then the CAPIF core function sends the response information to the API invoker, so as to facilitate the API invoker to access the resource of the resource owner based on the response information. In this way, the API invoker of one UE accesses the resource on another UE, that is, the cross-device resource access is realized.

[0069] The above embodiments are described by taking the first node directly sending the first request information to the third node after receiving the first request information as an example. In some embodiments, in order to improve the security of the communication system, after receiving the first request information, the first node verifies the legality of the second node. In the case that the second node is a legal node, the first request information is sent to the third node. In the case that the second node is an illegal node, the first node does not send the first request information to the third node.

[0070] As an example, the first node verifying the legality of the second node can be that the first node obtains group information of a group to which the second node belongs, and then verifies the legality of the second node based on the group information. Obtaining the group information of the group to which the second node belongs can be obtaining group information of a group to which a terminal belonging to the second node belongs.

[0071] In some embodiments, the API invoker and the resource owner function are both registered with the CAPIF core function, and for a specific service, the group management server has established a related group for it, and has allocated a specific group identifier for it, and has specified a member UE list of the group, and has sent the group information to the related member UEs. Based on this, the first node obtaining the group information of the group to which the second node belongs can be that the first node sends group query information for requesting to obtain the group information of the group to which the second node belongs to the group management server. The group query information includes at least one of the following: an identifier of the first node, an identifier of the group to which the second node belongs, and a query type (for example, membership information).

[0072] Then, the group management server sends group information query response information to the first node. The group information query response information includes the group identifier of the group to which the second node belongs and a query result. The query result is the group information of the group to which the second node belongs returned by the group management server based on the query type, such as a group member list. Accordingly, the first node receives the group information query response information sent by the group management server. The group information query response information includes the group information of the group to which the second node belongs.

[0073] As an example, verifying the legality of the second node based on the group information includes: in the case that the group information indicates that the group to which the second node belongs includes the third node, determining that the second node is a legal node; or in the case that the group information indicates that the group to which the second node belongs does not include the third node, determining that the second node is an illegal node.

[0074] It should be understood that, in the case that the group information indicates that the group to which the second node belongs includes the third node, it is represented that the second node and the third node belong to the same group. For example, in the case that the communication method provided by the present disclosure is applied to a vehicle health monitoring service in vehicle fleet management, it is represented that the vehicle to which the second node belongs and the vehicle to which the third node belongs belong to the same vehicle fleet, and it can be determined that the second node is a legal node. In the case that the group information indicates that the group to which the second node belongs does not include the third node, it is represented that the second node and the third node do not belong to the same group, that is, the vehicle to which the second node belongs and the vehicle to which the third node belong do not belong to the same vehicle fleet, and it can be determined that the second node is an illegal node.

[0075] As another example, verifying the legality of the second node includes: in the case that the second node has registered at the first node, determining that the second node is a legal node; or, in the case that the second node has not registered at the first node, determining that the second node is an illegal node.

[0076] It should be understood that a node that has registered in advance at the first node can pass the verification of the first node, that is, is a legal node. Therefore, in the case that the second node has registered at the first node, it is determined that the second node is a legal node that has registered in advance; or, in the case that the second node has not registered at the first node, it is determined that the second node is an illegal node that has not registered in advance.

[0077] In some embodiments, after receiving the first request information sent by the second node, the first node can send second response information to the second node, and the second response information is used to indicate whether the first request information is successfully received. For example, in the case that the first node successfully receives the first request information, the second response information used to indicate that the first request information is successfully received is sent to the second node. For another example, in the case that the first node does not successfully receive the first request information, the second response information used to indicate that the first request information is not successfully received is sent to the second node. The first request information that is not successfully received can be that the first node does not receive the first request information at the time agreed with the second node, or that the first node does not successfully decode the first request information after receiving the first request information, and the embodiments of the present disclosure are not limited in the manner of the first request information that is not successfully received.

[0078] In the case that the second response information is used to indicate that the first request information is not successfully received, after receiving the second response information, the second node can send the first request information to the first node again until the second response information sent by the first node and used to indicate that the first request information is successfully received is received.

[0079] In some embodiments, in order to ensure that the first node can obtain the latest group information, the first node can send a group information subscription request message to the group management server. The group information subscription request message includes at least one of the following: an identifier of the first node, an identifier of the group, and a list of identifiers of groups. After receiving the group information subscription request message sent by the first node, the group management server sends a group information subscription response message to the first node. Correspondingly, the first node receives the group information subscription response message sent by the group management server. The group information subscription response message includes at least one of the following: an identifier of the group, a list of identifiers of groups, and a subscription result. The subscription result is used to indicate whether the subscription is successful.

[0080] In the case where the subscription result indicates that the subscription is successful, after the group information is updated, the group management server sends the updated group information to the first node.

[0081] The above embodiments are described by taking the second node sending the first request information for requesting access to the resource of the third node to the first node as an example. In some embodiments, a fourth node connected to the second node can also pre-acquire the resource permission information of the third node, so that when the second node needs to access the resource of the third node, the second node can access the resource of the third node based on the resource permission information of the third node pre-acquired by the fourth node. Based on this, as shown in FIG. 3, the communication method can further include the following S201 and S202.

[0082] In S201, the second request information sent by the fourth node is received.

[0083] In some embodiments, in order to facilitate the second node in the process of calling the API, the fourth node can check the resource permission information, and the fourth node can send the second request information to the first node. The second request information is used to request the resource permission information of the third node, that is, to request the resource permission information of the third node required when the second node calls the API. Correspondingly, the first node receives the second request information sent by the fourth node. The fourth node can be the API exposure function 24 in the communication system shown in FIG. 1.

[0084] In some embodiments, the second request information comprises at least one of: an identity of the second node, an identity of a service API (application programming interface) for requesting the resource permission information of the third node, an identity of the third node, an identity of the fourth node. The service API is an external interface provided by an API (application programming interface) exposed function on an API provider. An API invoker can access the resource of a resource owner by invoking the service API, that is, the second node can access the resource of the third node by the service API. Therefore, the second request information can comprise the identity of the service API for requesting the resource permission information of the third node.

[0085] It should be noted that in the related art, the API exposed function hosts the service API, but the API exposed function does not execute the resource permission information of the service API, and the CCF stores the resource permission information corresponding to one or more service APIs.

[0086] In S202, the third response information is sent to the fourth node.

[0087] The third response information comprises the resource permission information of the third node.

[0088] In some embodiments, the third response information can further comprise at least one of: an identity of the second node, an identity of the third node, an identity of the fourth node, an identity of the service API for requesting the resource permission information of the third node.

[0089] In this way, after receiving the third response information, the fourth node can store the resource permission information of the third node in the third response information, and then when the second node needs to invoke the API, the fourth node can check the resource permission information used by the second node when invoking the API based on the resource permission information of the third node stored by the fourth node.

[0090] As an example, the third response information is sent to the fourth node in a case that the fourth node has registered in the first node and the first node stores the resource permission information of the third node. It should be understood that in the case that the fourth node has registered in the first node and the first node stores the resource permission information of the third node, the third response information is sent to the fourth node, which can improve the security of the communication system.

[0091] In some embodiments, the first node sends fourth response information to the fourth node in a case that the fourth node is not registered at the first node or the first node does not store the resource permission information of the third node. The fourth response information includes request failure indication information. The request failure indication information is used to indicate that the request for the resource permission information of the third node fails. Accordingly, the fourth node receives the fourth response information sent by the first node.

[0092] In some embodiments, the fourth response information further includes at least one of the following: an identity of the second node, an identity of a service API used to request the resource permission information of the third node, an identity of the third node, and an identity of the fourth node.

[0093] In some embodiments, the fourth node can obtain authorization information of the fourth node from the first node.

[0094] Based on the embodiment shown in FIG. 3, after receiving the second request information sent by the fourth node for requesting the resource permission information of the third node, the first node sends third response information including the resource permission information of the third node to the fourth node, so that the fourth node can perform the check of the resource permission information when invoking the API.

[0095] The above embodiment shown in FIG. 3 is described by taking the fourth node as an example to request the resource permission information of the third node from the first node. In some embodiments, the first node can monitor whether the resource permission information of the third node stored by the first node is updated, and based on this, referring to FIG. 4, the communication method can further include the following S301 and S302.

[0096] In S301, the updated resource permission information is sent to the fourth node in response to the update of the resource permission information of the third node stored by the first node.

[0097] In some embodiments, in a case that the resource permission information of the third node is updated, the third node sends the updated resource permission information to the first node. The first node sends the updated resource permission information to the fourth node in response to the update of the resource permission information of the third node stored by the first node, so that the cognition of the fourth node and the third node on the resource permission information of the third node is consistent, which helps to improve the stability of the communication system.

[0098] In some embodiments, the first node can further send at least one of the following to the fourth node when or after sending the updated resource permission information to the fourth node: an identity of the second node, an identity of the third node, an identity of the fourth node, etc.

[0099] In S302, the fifth response information sent by the fourth node is received.

[0100] In some embodiments, after the first node sends the updated resource permission information to the fourth node, the fourth node sends fifth response information to the first node. The fifth response information is used to indicate whether the fourth node successfully receives the updated resource permission information. Accordingly, the first node receives the fifth response information sent by the fourth node.

[0101] In some embodiments, the fifth response information includes at least one of the following: indication information indicating whether the updated resource permission information is successfully received, an identifier of the second node, an identifier of the third node, an identifier of the fourth node, and the like.

[0102] As an example, in the case that the fifth response information is used to indicate that the fourth node does not successfully receive the updated resource permission information, the first node sends the updated resource permission information to the fourth node again until the fifth response information sent by the fourth node is received, which is used to indicate that the updated resource permission information is successfully received.

[0103] The above embodiments are described by taking the example that the first node directly sends the updated resource permission information to the fourth node. In some embodiments, the first node can send the updated resource permission information to the fourth node in the case that the third request information sent by the fourth node is received, which is used to request to subscribe to the update of the resource permission information. Based on this, as shown in FIG. 5, before S301, the communication method can further include the following S401 and S402.

[0104] In S401, the third request information sent by the fourth node is received.

[0105] In some embodiments, in order for the fourth node to timely know the update of the resource permission information of the third node, that is, to timely obtain the latest resource permission information, the fourth node sends the third request information to the first node. The third request information is used to request to subscribe to the update of the resource permission information of the third node. Accordingly, the first node receives the third request information sent by the fourth node.

[0106] As an example, the third request information includes at least one of the following: an identifier of the second node, an identifier of the third node, an identifier of the fourth node, and the like.

[0107] In S402, the sixth response information is sent to the fourth node.

[0108] The sixth response information is used to indicate whether the update of the resource permission information is successfully subscribed.

[0109] In some embodiments, in a case where the sixth response information indicates that the update of the resource permission information is successfully subscribed, the first node sends the updated resource permission information to the fourth node in response to the resource permission information of the third node stored by the first node after monitoring that the resource permission information of the third node stored by the first node is updated.

[0110] As an example, the sixth response information includes at least one of the following: indication information for indicating whether the update of the resource permission information is successfully subscribed, an identifier of the second node, an identifier of the third node, an identifier of the fourth node, and the like.

[0111] To ensure that the network can protect the rights and interests of the resource owner while opening the capabilities, and provide fine-grained access control, RNAA is introduced in Rel-18 standard. RNAA is a northbound API access mechanism that can identify and consider the willingness and authorization status of the resource owner, and ensure that the access of the third-party application to the network resource is agreed and authorized by the resource owner while opening the network capabilities. However, in Rel-18, how the resource owner function (ROF) manages (such as updates, revokes, etc.) the resource permission information is not discussed. Based on this, as shown in FIG. 6, the communication method provided by the embodiments of the present disclosure can further include the following S501 and S502.

[0112] In S501, the fourth request information sent by the fifth node is received.

[0113] The fifth node can be the ROF 22 in the communication system shown in FIG. 1. The fourth request information includes the resource permission information, and the fourth request information is used to request the first node to manage the resource permission information.

[0114] In some embodiments, the fourth request information further includes at least one of the following: an identifier of a terminal to which the fifth node belongs, an identifier of the resource permission information, an identifier of the second node, an identifier of the API, and an identifier of the service.

[0115] In S502, the seventh response information is sent to the fifth node in response to the fourth request information.

[0116] The seventh response information is used to indicate whether the management of the resource permission information is successful.

[0117] As an example, after receiving the fourth request information sent by the fifth node, the first node saves and applies the resource permission information in the fourth request information, that is, manages the resource permission information. Then, the first node sends the seventh response information to the fifth node. The seventh response information is used to indicate that the management of the resource permission information is successful.

[0118] Based on the embodiment shown in FIG. 6, the fifth node provides a management method for the ROF to manage the resource permission information by sending the fourth request information to the first node to request the first node to manage the resource permission information.

[0119] In some embodiments, as shown in FIG. 7, after S502, the communication method can further include S601 and S602.

[0120] In S601, the fifth request information sent by the fifth node is received.

[0121] In some embodiments, the fifth node can send the fifth request information to the first node after the modification of the resource permission information, in the case that the fifth response information indicating the success of the management of the resource permission information is received. The fifth request information is used to request the modification of the resource permission information. Accordingly, the first node receives the fifth request information sent by the fifth node.

[0122] As an example, the modification includes adding, deleting or updating.

[0123] Taking the case that the fifth request information is used to request the update of the resource permission information as an example, the fifth request information includes at least one of the following: the identity of the terminal to which the fifth node belongs, the identity of the resource permission information, the updated resource permission information, the identity of the second node, the identity of the API, the identity of the service, etc.

[0124] Taking the case that the fifth request information is used to request the deletion of the resource permission information as an example, the fifth request information includes at least one of the following: the identity of the terminal to which the fifth node belongs, the identity of the resource permission information, the deleted resource permission information, the identity of the second node, the identity of the API, the identity of the service, etc.

[0125] In S602, the modified resource permission information is sent to the second node in response to the fifth request information.

[0126] In some embodiments, after receiving the modified resource permission information, the second node updates the resource permission information used in the API invocation based on the modified resource permission information.

[0127] In this way, after the modification of the resource permission information, the fifth node sends the fifth request information to the first node to request the first node to modify the resource permission information, and then sends the modified resource permission information to the second node after the first node modifies the resource permission information, so that the second node and the fifth node have consistent cognition of the resource permission information, which helps to improve the stability of the communication system.

[0128] In some embodiments, after receiving the fifth request information sent by the fifth node to modify the resource permission information, the first node can send eighth response information to the fifth node. The eighth response information is used to indicate whether the modification of the resource permission information is successful.

[0129] Based on the embodiment shown in FIG. 7, the fifth node initiates the resource permission management request process. Once the process is initiated, the fifth node actively reports to the first node for subsequent updates, revocations, etc. of the resource permission information. Then, the first node sends updated resource permission information to the relevant second node according to the resource permission information update sent by the fifth node, and the second node updates the resource permission information used in the API invocation.

[0130] In some embodiments, as shown in FIG. 8, the embodiment of the present disclosure further provides another communication method applied to the second node. The communication method can include the following S701 and S702.

[0131] In S701, first request information is sent to the first node.

[0132] The first request information is used to request access to the resource of the third node.

[0133] For detailed description of the first request information, reference can be made to the related description in the above-described embodiment shown in FIG. 2, which will not be repeated here.

[0134] In S702, the first response information of the third node to the first request information sent by the first node is received.

[0135] The first response information includes resource permission information. The resource permission information is used to indicate that the second node is allowed to access the resource of the third node. In this way, the second node can access the resource of the third node based on the resource permission information, realizing cross-device resource access.

[0136] The above-described embodiment is described by taking the second node directly sending the first request information to the first node as an example. In some embodiments, in order to improve the security of the communication system, the second node can verify the legality of the third node, and in the case that the third node is a legal node, the second node sends the first request information to the first node.

[0137] As an example, verifying the legality of the third node includes: obtaining group information of a group to which the second node belongs; and verifying the legality of the third node based on the group information.

[0138] For the description of the second node obtaining the group information of the group to which the second node belongs, reference can be made to the description of the first node obtaining the group information of the group to which the second node belongs in the above-described embodiment, which will not be repeated here.

[0139] Based on the group information, the legality of the third node is verified, including: in the case that the group information indicates that the group to which the second node belongs includes the third node, determining that the third node is a legal node; or in the case that the group information indicates that the group to which the second node belongs does not include the third node, determining that the third node is an illegal node.

[0140] In some embodiments, after the second node sends the first request information to the first node, the second node can also receive second response information sent by the first node. The second response information is used to indicate whether the first node successfully receives the first request information. In the case that the second response information indicates that the first node does not successfully receive the first request information, the second node sends the first request information to the first node again until the second response information sent by the first node indicating that the first request information is successfully received is received.

[0141] In some embodiments, the second node can also receive modified resource permission information sent by the first node. After receiving the modified resource permission information sent by the first node, the second node can update the resource permission information used in the API invocation based on the modified resource permission information.

[0142] In some embodiments, as shown in FIG. 9, the embodiments of the present disclosure also provide another communication method applied to a third node. The communication method can include the following S801 and S802.

[0143] In S801, first request information from a second node sent by a first node is received.

[0144] The first request information is used to request access to a resource of the third node.

[0145] In S802, first response information to the first request information is sent to the first node.

[0146] The first response information includes resource permission information, and the resource permission information is used to indicate that the second node is allowed to access the resource of the third node.

[0147] In this way, the second node can access the resource of the third node based on the resource permission information in the first response information, realizing cross-device resource access.

[0148] The above embodiments are described by taking the third node directly sending first response information to the first request information to the first node as an example. In some embodiments, in order to improve the security of the communication system, the third node can verify the legality of the second node. In the case that the second node is a legal node, the first response information to the first request information is sent to the first node.

[0149] As an example, verifying the legality of the second node comprises: obtaining group information of a group to which the third node belongs; and verifying the legality of the second node based on the group information.

[0150] For the description of obtaining, by the third node, the group information of the group to which the third node belongs, reference can be made to the description of obtaining, by the first node, the group information of the group to which the second node belongs in the above-described embodiments, which will not be repeated here.

[0151] Verifying the legality of the second node based on the group information comprises: determining that the second node is a legal node in a case where the group information indicates that the group to which the third node belongs includes the second node; or determining that the second node is an illegal node in a case where the group information indicates that the group to which the third node belongs does not include the second node.

[0152] In some embodiments, as shown in FIG. 10, the embodiments of the present disclosure further provide another communication method, which is applied to a fourth node. The communication method can comprise the following S901 and S902.

[0153] In S901, second request information is sent to the first node.

[0154] The second request information is used to request resource permission information of the third node.

[0155] In S902, third response information sent by the first node is received.

[0156] The third response information comprises the resource permission information of the third node.

[0157] For detailed descriptions of the second request information and the third response information, reference can be made to the corresponding descriptions of the second request information and the third response information in the above-described embodiments, which will not be repeated here.

[0158] In some embodiments, in a case where the fourth node is not registered at the first node, or the first node does not store the resource permission information of the third node, the fourth node receives fourth response information sent by the first node. The fourth response information comprises request failure indication information.

[0159] In some embodiments, the fourth node can further receive updated resource permission information sent by the first node, and in response to the updated resource permission information, send fifth response information to the first node. The fifth response information is used to indicate whether the updated resource permission information is successfully received.

[0160] In some embodiments, in order to learn the latest resource permission information in time, the fourth node can send third request information to the first node. The third request information is used to request to subscribe to the update of the resource permission information. Then, the fourth node can receive sixth response information sent by the first node. The sixth response information is used to indicate whether the update of the resource permission information is successfully subscribed.

[0161] In some embodiments, as shown in FIG. 11, the embodiments of the present disclosure further provide another communication method applied to a fifth node. The communication method can include the following S1001 and S1002.

[0162] In S1001, fourth request information is sent to the first node.

[0163] The fourth request information includes the resource permission information. The fourth request information is used to request to manage the resource permission information.

[0164] In S1002, seventh response information sent by the first node is received.

[0165] The seventh response information is used to indicate whether the management of the resource permission information is successful.

[0166] Thus, the embodiments of the present disclosure provide a management method for the ROF to manage the resource permission information.

[0167] In some embodiments, in the case that the seventh response information indicates that the management of the resource permission information is successful, after the fifth node determines that the resource permission information is modified, the fifth node sends fifth request information to the first node. The fifth request information is used to request to modify the resource permission information. Then, the fifth node can receive eighth response information sent by the first node. The eighth response information is used to indicate whether the modification of the resource permission information is successful.

[0168] The service enabler architecture layer for verticals (SEAL) architecture in 3GPP is a key component. SEAL defines a method that allows different vertical industries to utilize 5G network services. The design goal of SEAL is to provide a standardized framework that enables third-party services and applications to access 5G networks in a secure and efficient manner. The SEAL architecture includes SEAL clients and SEAL servers on the network. SEAL specifies application plane and signaling plane entities, such as group management, configuration management, location management, identity / key management, network resource management, etc., which can be reused in vertical applications. On the network side, above the SEAL layer is the vertical application layer (VAL), which uses the SEAL layer to complete services. SEAL supports all generic functions, which provide services for VAL that can reuse current functions to build.

[0169] Group management is a key component that allows logical grouping of users or devices for more efficient management and service provision. The group management mechanism in SEAL provides a flexible and scalable way for 5G networks to manage users and services, supporting the diverse application and service needs of 5G networks.

[0170] In some embodiments, in order to realize cross-device resource access, the disclosure embodiments also provide a communication method based on access token. RNAA uses OAuth 2.0 framework authorization based on access token, including the following roles: API invoker has the role of OAuth 2.0 client; CAPIF core function (communication capability framework) has the role of OAuth 2.0 authorization server, that is, provides access tokens for RNAA; API exposing function (application function) has the role of resource server.

[0171] If the API invoker on the group member UE wants to access the resource on another group member UE, the following description will be applied: the access token for RNAA should contain the group ID (identity, identification) of the API invoker, API invoker ID and resource owner ID, the group is the relevant group established by the group management server in SEAL for a specific service, and is allocated a specific group ID, and specifies the member UE list of the group.

[0172] If the API invoker is deployed on a UE, the CCF should check whether the UE is accessing its own resource. If not, the CCF further checks whether the group ID is contained in the access token. If the group ID is contained, the CCF and the group management server confirm whether the API invoker is accessing the resource of other UEs of the same group.

[0173] The above mainly introduces the scheme provided by the present disclosure from the perspective of interaction between nodes. It can be understood that each node, for example, the first node, the second node or the third node, contains a hardware structure and / or a software module for executing each function in order to realize the above functions. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments disclosed herein, the present disclosure can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driven hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present disclosure.

[0174] The embodiments of the present disclosure can divide the functions of the first node, the second node or the third node into function modules according to the above method embodiments. For example, each function module can be divided according to each function, or two or more functions can be integrated into one function module. The above integrated module can be realized in the form of hardware or software. It should be noted that the division of the modules in the embodiments of the present disclosure is illustrative, and is only a logical function division. When actually implemented, there can be another division manner. The following will be described taking the example of dividing each function module according to each function.

[0175] FIG. 12 is a constituent schematic diagram of a communication apparatus according to an embodiment of the present disclosure. As shown in FIG. 12, the communication apparatus 110 includes a receiving unit 1101 and a sending unit 1102.

[0176] The communication apparatus 110 can be the first node or a chip in the first node. When the communication apparatus 110 is used to realize the functions of the first node in the above embodiments, each unit is used to realize the following functions.

[0177] The receiving unit 1101 is configured to receive first request information sent by the second node. The first request information is used to request to access the resource of the third node.

[0178] The sending unit 1102 is configured to send the first request information to the third node.

[0179] The receiving unit 1101 is further configured to receive first response information for the first request information sent by the third node. The first response information comprises resource permission information. The resource permission information is used to indicate that the second node is allowed to access resources of the third node.

[0180] The sending unit 1102 is further configured to send the first response information to the second node.

[0181] In some embodiments, the sending unit 1102 is, for example, configured to: verify the legality of the second node; and send the first request information to the third node in a case where the second node is a legal node.

[0182] In some embodiments, the sending unit 1102 is, for example, configured to: obtain group information of a group to which the second node belongs; and verify the legality of the second node based on the group information.

[0183] In some embodiments, the sending unit 1102 is, for example, configured to: determine that the second node is a legal node in a case where the group information indicates that the group to which the second node belongs comprises the third node; or determine that the second node is an illegal node in a case where the group information indicates that the group to which the second node belongs does not comprise the third node.

[0184] In some embodiments, the sending unit 1102 is, for example, configured to: determine that the second node is a legal node in a case where the second node has registered at the first node; or determine that the second node is an illegal node in a case where the second node has not registered at the first node.

[0185] In some embodiments, the sending unit 1102 is further configured to send second response information to the second node. The second response information is used to indicate whether the first request information is successfully received.

[0186] In some embodiments, the receiving unit 1101 is further configured to receive second request information sent by a fourth node. The second request information is used to request resource permission information of the third node.

[0187] The sending unit 1102 is further configured to send third response information to the fourth node. The third response information comprises the resource permission information of the third node.

[0188] In some embodiments, the sending unit 1102 is, for example, configured to send the third response information to the fourth node in a case where the fourth node has registered at the first node and the first node stores the resource permission information of the third node.

[0189] In some embodiments, the sending unit 1102 is further configured to send fourth response information to the fourth node in a case where the fourth node has not registered at the first node or the first node does not store the resource permission information of the third node. The fourth response information comprises request failure indication information.

[0190] In some embodiments, the sending unit 1102 is further configured to send the updated resource permission information to the fourth node in response to the third node storing the updated resource permission information of the third node;

[0191] The receiving unit 1101 is further configured to receive fifth response information sent by the fourth node. The fifth response information is used to indicate whether the updated resource permission information is successfully received.

[0192] In some embodiments, the receiving unit 1101 is further configured to receive third request information sent by the fourth node. The third request information is used to request to subscribe to the update of the resource permission information.

[0193] The sending unit 1102 is further configured to send sixth response information to the fourth node. The sixth response information is used to indicate whether the update of the resource permission information is successfully subscribed.

[0194] In some embodiments, the receiving unit 1101 is further configured to receive fourth request information sent by the fifth node. The fourth request information includes the resource permission information. The fourth request information is used to request to manage the resource permission information.

[0195] The sending unit 1102 is further configured to send seventh response information to the fifth node in response to the fourth request information. The seventh response information is used to indicate whether the management of the resource permission information is successful.

[0196] In some embodiments, the receiving unit 1101 is further configured to receive fifth request information sent by the fifth node. The fifth request information is used to request to modify the resource permission information.

[0197] The sending unit 1102 is further configured to send the modified resource permission information to the second node in response to the fifth request information.

[0198] In some embodiments, the sending unit 1102 is further configured to send eighth response information to the fifth node. The eighth response information is used to indicate whether the modification of the resource permission information is successful.

[0199] FIG. 13 is a constituent schematic diagram of another communication apparatus according to embodiments of the present disclosure. As shown in FIG. 13, the communication apparatus 120 includes a sending unit 1201 and a receiving unit 1202.

[0200] The communication apparatus 120 can be the second node or a chip in the second node. When the communication apparatus 120 is used to implement the functions of the second node in the above embodiments, each unit is configured to implement the following functions.

[0201] The sending unit 1201 is configured to send first request information to the first node. The first request information is used to request to access the resource of the third node.

[0202] The receiving unit 1202 is configured to receive first response information from a third node to the first request information sent by a first node. The first response information comprises resource permission information. The resource permission information is used to indicate that the second node is allowed to access resources of the third node.

[0203] In some embodiments, the sending unit 1201 is configured to, for example, verify the legality of the third node; and send the first request information to the first node in a case where the third node is a legal node.

[0204] In some embodiments, the sending unit 1201 is configured to, for example, acquire group information of a group to which the second node belongs; and verify the legality of the third node based on the group information.

[0205] In some embodiments, the sending unit 1201 is configured to, for example, determine that the third node is a legal node in a case where the group information indicates that the group to which the second node belongs comprises the third node; or determine that the third node is an illegal node in a case where the group information indicates that the group to which the second node belongs does not comprise the third node.

[0206] In some embodiments, the receiving unit 1202 is further configured to receive second response information sent by the first node. The second response information is used to indicate whether the first request information is successfully received.

[0207] In some embodiments, the receiving unit 1202 is further configured to receive modified resource permission information sent by the first node.

[0208] FIG. 14 is a constituent schematic diagram of another communication apparatus according to an embodiment of the present disclosure. As shown in FIG. 14, the communication apparatus 130 comprises a receiving unit 1301 and a sending unit 1302.

[0209] The communication apparatus 130 can be the third node or a chip in the third node. When the communication apparatus 130 is used to implement the functions of the third node in the above-described embodiments, each unit is configured to implement the following functions.

[0210] The receiving unit 1301 is configured to receive first request information from a second node sent by a first node. The first request information is used to request to access resources of the third node.

[0211] The sending unit 1302 is configured to send first response information to the first request information to the first node. The first response information comprises resource permission information. The resource permission information is used to indicate that the second node is allowed to access resources of the third node.

[0212] In some embodiments, the sending unit 1302 is configured to, for example: verify the legality of the second node; and send, to the first node, first response information for the first request information in a case where the second node is a legal node.

[0213] In some embodiments, the sending unit 1302 is configured to, for example: obtain group information of a group to which the third node belongs; and verify the legality of the second node based on the group information.

[0214] In some embodiments, the sending unit 1302 is configured to, for example: determine that the second node is a legal node in a case where the group information indicates that the group to which the third node belongs includes the second node; or determine that the second node is an illegal node in a case where the group information indicates that the group to which the third node belongs does not include the second node.

[0215] It should be noted that the units in FIGS. 12-14 can also be referred to as modules, for example, the sending unit can be referred to as a sending module. In addition, in the embodiments shown in FIGS. 12-14, the names of the various units can also be different from those shown in the figures, for example, the sending unit can also be referred to as a communication unit, and the receiving unit can also be referred to as a communication unit.

[0216] If each unit in FIGS. 12-14 is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present disclosure or the part that contributes to the related art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the embodiments of the present disclosure. The storage medium storing the computer software product includes a universal serial bus flash disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0217] In a case where the communication apparatuses 110-130 implement the functions of the integrated modules described above in the form of hardware, the embodiments of the present disclosure provide a structural diagram of a communication apparatus. As shown in FIG. 15, the communication apparatus 140 includes a processor 1402, a communication interface 1403, and a bus 1404. In some embodiments, the communication apparatus 140 can further include a memory 1401.

[0218] The processor 1402 can be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic device, transistor logic, hardware components, or any combination thereof, which can implement or execute the various exemplary logical blocks, modules, and circuits described in connection with the embodiments of the present disclosure. The processor 1402 can also be a combination of computing components, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.

[0219] The communication interface 1403 is configured to connect with other devices through a communication network. The communication network can be an Ethernet, a wireless access network, a wireless local area network (WLAN), and the like.

[0220] The memory 1401 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium, or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.

[0221] As an implementation manner, the memory 1401 can exist independently of the processor 1402, and the memory 1401 can be connected with the processor 1402 through the bus 1404, and used to store instructions or program codes. When the processor 1402 invokes and executes the instructions or program codes stored in the memory 1401, the communication method provided by the embodiments of the present disclosure can be implemented.

[0222] In another implementation manner, the memory 1401 can also be integrated with the processor 1402.

[0223] The bus 1404 can be an extended industry standard architecture (EISA) bus, a proprietary bus, or the like. The bus 1404 can be divided into an address bus, a data bus, a control bus, or the like. For ease of representation, only one thick line is shown in FIG. 15, but this does not mean that there is only one bus or only one type of bus.

[0224] Through the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional modules is exemplified, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the first node, the second node, or the third node is divided into different functional modules to complete all or part of the functions described above.

[0225] The embodiments of the present disclosure further provide a computer readable storage medium (for example, a non-transitory computer readable storage medium). All or part of the processes in the above method embodiments can be instructed by computer instructions or programs to complete related hardware, and the programs can be stored in the above computer readable storage medium. When the programs are executed, the processes of the above method embodiments can be included. The above computer readable storage medium can also be an external storage device of the above first node, second node, or third node. For example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, and the like equipped on the above first node, second node, or third node. Further, the above computer readable storage medium can include both an internal storage unit of the above first node, second node, or third node and an external storage device. The above computer readable storage medium is used to store the above computer programs and other programs and data required by the above first node, second node, or third node. The above computer readable storage medium can also be used to temporarily store data that has been output or will be output.

[0226] The embodiments of the present disclosure further provide a computer program product containing a computer program. When the computer program product runs on a computer, it makes the computer execute any one of the communication methods provided in the above embodiments.

[0227] Although the present disclosure has been described in connection with certain embodiments, it will be understood that the application is capable of further modifications and that this application is intended to cover any variations or alterations that fall within the scope of the present disclosure. Accordingly, the specification and drawings are to be regarded as illustrative in nature and not as restrictive. It should be understood that various modifications and changes can be aimed at the application without departing from the spirit and scope of the application. It is therefore intended that the present disclosure not be limited to the particular disclosure herein disclosed but that it can be one in which changes can be made without departing from the scope of the present disclosure as defined by the appended claims and their equivalents.

[0228] Although the present disclosure has been described in connection with specific features thereof, it will be understood that various modifications and variations can be made without departing from the spirit and scope of the application. Accordingly, it should be understood that the present disclosure is intended to cover all modifications and variations of this application within the scope of the appended claims and their equivalents. It is therefore intended that the present disclosure not be limited to the particular disclosure herein disclosed but that it can be one in which changes can be made without departing from the scope of the present disclosure as defined by the appended claims and their equivalents.

[0229] The above, only for the specific implementation of the present disclosure, but the scope of protection of the present disclosure is not limited to this, any in the technical range of the present disclosure disclosed changes or replacement, should be covered within the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be subject to the scope of protection of the claims.

Claims

1. A communication method applied to a first node, comprising: receiving first request information sent by a second node, the first request information being used for requesting access to a resource of a third node; sending the first request information to the third node; receiving first response information sent by the third node for the first request information, the first response information comprising resource permission information, the resource permission information being used for indicating that the second node is allowed to access the resource of the third node; sending the first response information to the second node.

2. The method of claim 1, wherein, The sending of the first request information to the third node comprises: verifying legality of the second node; in a case where the second node is a legal node, sending the first request information to the third node.

3. The method of claim 2, wherein, The verification of the legality of the second node comprises: obtaining group information of a group to which the second node belongs; based on the group information, verifying the legality of the second node.

4. The method of claim 3, wherein, The verification of the legality of the second node based on the group information comprises: in a case where the group information indicates that the group to which the second node belongs comprises the third node, determining that the second node is a legal node; or in a case where the group information indicates that the group to which the second node belongs does not comprise the third node, determining that the second node is an illegal node.

5. The method of claim 2, wherein, The verification of the legality of the second node comprises: in a case where the second node has been registered at the first node, determining that the second node is a legal node; or in a case where the second node has not been registered at the first node, determining that the second node is an illegal node.

6. The method of claim 1, wherein, The first request information comprises at least one of the following: an identifier of the second node, an identifier of the group to which the second node belongs, an identifier of a service related to the group to which the second node belongs, an identifier of the third node, requested resource permission information.

7. The method of claim 1, wherein, The first response information further comprises at least one of the following: an identifier of the third node, an identifier of the second node. 8.The method of claim 1, further comprising: sending second response information to the second node, the second response information being used for indicating whether the first request information is successfully received. 9.The method of claim 1, further comprising: receiving second request information sent by a fourth node, the second request information being used for requesting resource permission information of the third node; sending third response information to the fourth node, the third response information comprising the resource permission information of the third node.

10. The method of claim 9, wherein, The sending of the third response information to the fourth node comprises: in a case where the fourth node has been registered at the first node and the first node stores the resource permission information of the third node, sending the third response information to the fourth node. 11.The method of claim 9, further comprising: in a case where the fourth node has not been registered at the first node or the first node does not store the resource permission information of the third node, sending fourth response information to the fourth node, the fourth response information comprising request failure indication information.

12. The method of claim 9, wherein, The second request information comprises at least one of the following: an identity of the second node, an identity of a service application programming interface requesting resource permission information of the third node, an identity of the third node, an identity of the fourth node.

13. The method of claim 9, wherein, The third response information further comprises at least one of the following: an identity of the second node, an identity of the third node, an identity of the fourth node, an identity of a service application programming interface requesting resource permission information of the third node.

14. The method of claim 1, further comprising: sending updated resource permission information to a fourth node in response to the first node storing the updated resource permission information of the third node; receiving fifth response information sent by the fourth node, the fifth response information indicating whether the updated resource permission information is successfully received.

15. The method of claim 14, further comprising: receiving third request information sent by the fourth node, the third request information requesting to subscribe to updates of the resource permission information; sending sixth response information to the fourth node, the sixth response information indicating whether the subscription to the updates of the resource permission information is successful.

16. The method of claim 1, further comprising: receiving fourth request information sent by a fifth node, the fourth request information comprising resource permission information, the fourth request information requesting to manage the resource permission information; sending seventh response information to the fifth node in response to the fourth request information, the seventh response information indicating whether the management of the resource permission information is successful.

17. The method of claim 16, further comprising: receiving fifth request information sent by the fifth node, the fifth request information requesting to modify the resource permission information; sending modified resource permission information to the second node in response to the fifth request information.

18. The method of claim 17, further comprising: sending eighth response information to the fifth node, the eighth response information indicating whether the modification of the resource permission information is successful.

19. A communication method applied to a second node, comprising: sending first request information to a first node, the first request information requesting to access resources of a third node; receiving first response information sent by the first node, the first response information comprising resource permission information, the resource permission information indicating that the second node is allowed to access the resources of the third node.

20. The method of claim 19, wherein, The sending of the first request information to the first node comprises: verifying the legality of the third node; in a case where the third node is a legal node, sending the first request information to the first node.

21. The method of claim 20, wherein, The verifying of the legality of the third node comprises: obtaining group information of a group to which the second node belongs; based on the group information, verifying the legality of the third node.

22. The method of claim 21, wherein, The verifying of the legality of the third node based on the group information comprises: In a case where the group information indicates that the group to which the second node belongs includes the third node, determining that the third node is a legitimate node; or In a case where the group information indicates that the group to which the second node belongs does not include the third node, determining that the third node is an illegitimate node.

23. The method of claim 19, further comprising: receiving second response information sent by the first node, the second response information being used to indicate whether the first request information is successfully received.

24. The method of claim 19, further comprising: receiving modified resource permission information sent by the first node.

25. A communication method applied to a third node, comprising: receiving first request information from a second node sent by a first node, the first request information being used to request access to a resource of the third node; sending first response information to the first node for the first request information, the first response information including resource permission information, the resource permission information being used to indicate that the second node is allowed to access the resource of the third node.

26. The method of claim 25, wherein, The sending of the first response information to the first node for the first request information comprises: verifying legitimacy of the second node; in a case where the second node is a legitimate node, sending the first response information to the first node for the first request information.

27. The method of claim 26, wherein, The verifying of the legitimacy of the second node comprises: obtaining group information of a group to which the third node belongs; based on the group information, verifying the legitimacy of the second node.

28. The method of claim 27, wherein, The verifying of the legitimacy of the second node based on the group information comprises: in a case where the group information indicates that the group to which the third node belongs includes the second node, determining that the second node is a legitimate node; or in a case where the group information indicates that the group to which the third node belongs does not include the second node, determining that the second node is an illegitimate node.

29. A communications device comprising: a memory and a processor; wherein the memory is coupled with the processor; the memory is configured to store instructions executable by the processor; and the processor is configured to execute the instructions to perform the method according to any one of claims 1 to 28.

30. A computer readable storage medium, wherein, The computer readable storage medium has stored thereon computer instructions, which when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 28.

31. A computer program product, wherein, The computer program product contains computer instructions, which when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 28.

Citation Information

Patent Citations

  • API (Application Program Interface) security calling method, device and equipment and computer storage medium

    CN114117401A

  • Communication method and communication device

    CN117641358A

  • Methods, systems, and computer readable media for health checking involving common application programming interface framework

    US20230229539A1

  • Secure user consent data notification

    WO2023144774A1