Communication method, first entity, second entity, communication system, and storage medium

Abstract

The present disclosure relates to a communication method, a first entity, a second entity, a communication system, and a storage medium. The method is applied to a first entity. The method comprises: receiving a resource owner identifier and request information sent by a second entity, wherein the request information is used for requesting to obtain authorization of a resource owner for a third entity; and on the basis of the resource owner identifier and the request information, generating a token for the third entity and / or sending the token for the third entity to the second entity. According to embodiments of the present disclosure, the second entity can obtain the authorization of the resource owner for the third entity in time, thereby improving the sensing communication efficiency.

Description

Communication method, first entity, second entity, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication method, a first entity, a second entity, a communication system, and a storage medium. Background Art

[0002] Wireless sensing technology can acquire sensing data about a target without actually contacting it. This data can be used to analyze the target and obtain relevant information about it. In sensing communication scenarios, the entity initiating the sensing request must obtain authorization from the resource owner.

[0003] Summary of the Invention

[0004] In the perception communication scenario, when the resource owner cannot handle the authorization by itself, the entity used to initiate the perception request cannot obtain the authorization of the resource owner in a timely manner, which is a technical problem that needs to be solved.

[0005] The embodiments of the present disclosure provide a communication method, a first entity, a second entity, a communication system, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a communication method is proposed, which is applied to a first entity, and the method includes: receiving a resource owner identifier and request information sent by a second entity, wherein the request information is used to request authorization from the resource owner for a third entity; based on the resource owner identifier and the request information, generating a token for the third entity and / or sending a token for the third entity to the second entity.

[0007] According to a second aspect of an embodiment of the present disclosure, a communication method is proposed, which is applied to a second entity, and the method includes: sending a resource owner identifier and request information to a first entity, wherein the request information is used to request authorization from the resource owner for a third entity; and receiving a token for the third entity sent by the first entity, wherein the token for the third entity is generated based on the resource owner identifier and the request information.

[0008] According to a third aspect of an embodiment of the present disclosure, a first entity is proposed, comprising: a transceiver module for receiving a resource owner identifier and request information sent by a second entity, wherein the request information is used to request authorization from the resource owner for a third entity; and a processing module for generating a token for the third entity based on the resource owner identifier and the request information and / or sending the token for the third entity to the second entity.

[0009] According to a fourth aspect of an embodiment of the present disclosure, a second entity is proposed, comprising: a transceiver module for sending a resource owner identifier and request information to a first entity, wherein the request information is used to request authorization from the resource owner for a third entity; and receiving a token for the third entity sent by the first entity, wherein the token for the third entity is generated based on the resource owner identifier and the request information.

[0010] According to a fifth aspect of an embodiment of the present disclosure, a first entity is proposed, comprising: one or more processors; wherein the processor is configured to execute the communication method of the first aspect.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a second entity is proposed, comprising: one or more processors; wherein the processor is configured to execute the communication method of the second aspect.

[0012] According to a seventh aspect of an embodiment of the present disclosure, a communication system is proposed, including a network device and a second entity, wherein the first entity is configured to implement the communication method of the first aspect, and the second entity is configured to implement the communication method of the second aspect.

[0013] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes the communication method of the first aspect or the second aspect.

[0014] Through the embodiments of the present disclosure, the second entity sends the resource owner identifier and request information for requesting the resource owner to authorize the third entity to the first entity. The first entity can generate a token for the third entity and / or send a token for the third entity to the second entity based on the resource owner identifier and the request information, so that the second entity can obtain the resource owner's authorization for the third entity in a timely manner, thereby improving the efficiency of perceived communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0016] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0017] FIG2 is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure.

[0018] FIG3A is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0019] FIG3B is a flow chart illustrating a communication method according to an embodiment of the present disclosure.

[0020] FIG4 is a flow chart showing a communication method according to an embodiment of the present disclosure.

[0021] FIG5 is an interactive diagram illustrating a communication method according to an embodiment of the present disclosure.

[0022] FIG6 is an interactive diagram illustrating a communication method according to an embodiment of the present disclosure.

[0023] FIG7A is a schematic structural diagram of the first entity proposed in an embodiment of the present disclosure.

[0024] FIG7B is a schematic structural diagram of the second entity proposed in an embodiment of the present disclosure.

[0025] FIG8A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure.

[0026] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] The embodiments of the present disclosure provide a communication method, a first entity, a second entity, a communication system, and a storage medium.

[0028] In a first aspect, an embodiment of the present disclosure proposes a communication method, which is applied to a first entity, and the method includes: receiving a resource owner identifier and request information sent by a second entity, where the request information is used to request authorization from the resource owner for a third entity; based on the resource owner identifier and the request information, generating a token for the third entity and / or sending a token for the third entity to the second entity.

[0029] In the above embodiment, the second entity sends the resource owner identifier and request information for requesting the resource owner to authorize the third entity to the first entity. The first entity can generate a token for the third entity and / or send a token for the third entity to the second entity based on the resource owner identifier and the request information, so that the second entity can obtain the resource owner's authorization for the third entity in a timely manner, thereby improving the efficiency of perceived communication.

[0030] In combination with some embodiments of the first aspect, in some embodiments, the request information includes an identifier of a third entity; based on the resource owner identifier and the request information, a token for the third entity is generated and / or a token for the third entity is sent to the second entity, including: when the resource owner identifier and the identifier of the third entity meet the first condition, a token for the third entity is generated and / or a token for the third entity is sent to the second entity.

[0031] In the above embodiment, when the resource owner identifier and the identifier of the third entity meet the first condition, a token is generated or sent to the second entity, so that the second entity can obtain the resource owner's authorization when the resource owner cannot handle the authorization by itself.

[0032] In combination with some embodiments of the first aspect, in some embodiments, the resource owner identifier and the identifier of the third entity meet the first condition, including: the resource owner identifier and the identifier of the third entity are the same; or, there is a mapping relationship between the resource owner identifier and the identifier of the third entity.

[0033] In the above embodiment, when the resource owner identifier and the identifier of the third entity are the same, or there is a mapping relationship between the resource owner identifier and the identifier of the third entity, a token is generated or a token is sent to the second entity, so that the second entity can obtain the authorization of the resource owner when the resource owner cannot handle the authorization on its own.

[0034] In combination with some embodiments of the first aspect, in some embodiments, the first entity stores a mapping relationship between the resource owner identifier and the identifier of the third entity.

[0035] In the above embodiment, the mapping relationship between the resource owner identifier and the identifier of the third entity is pre-stored in the first entity, which can improve the efficiency of the first entity in processing authorization.

[0036] In combination with some embodiments of the first aspect, in some embodiments, the request information includes at least one of the following: an identifier of a third entity; perception role information, the perception role information including the identifier of the third entity and / or the perception role corresponding to the identifier of the third entity; an association request of the identification information and the perception result, the association request including the identifier of the third entity; an open request for perception context information, the open request including the identifier of the third entity.

[0037] In the above embodiment, the request information includes the above content, which can improve the efficiency of the first entity in processing authorization.

[0038] In combination with some embodiments of the first aspect, in some embodiments, the perception role includes at least one of a perception sender and a perception receiver.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: when the resource owner identifier and the identifier of the third entity do not meet the first condition, not authorizing the request information.

[0040] In the above embodiment, when the resource owner identifier and the third entity identifier do not meet the first condition, the request information is not authorized, which can save communication resources.

[0041] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: when the resource owner identifier and the identifier of the third entity do not meet the first condition, sending a failure message to the second entity; wherein the failure message indicates that the request is not authorized or the unauthorized part of the request.

[0042] In the above embodiment, when the resource owner identifier and the identifier of the third entity do not meet the first condition, a failure message is sent to the second entity, so that the second entity receives information that the request is not authorized or the unauthorized part of the request.

[0043] In combination with some embodiments of the first aspect, in some embodiments, the token includes at least one of the following: an identifier of the third entity; perception role information, the perception role information including the identifier of the third entity and / or the perception role corresponding to the identifier of the third entity; an association indication of the identification information and the perception result, the association indication including the identifier of the third entity; an open indication of the perception context information, the open indication including the identifier of the third entity.

[0044] In combination with some embodiments of the first aspect, in some embodiments, before generating a token for the third entity, the method further includes: receiving resource owner credentials sent by the second entity; and authenticating the resource owner based on the resource owner identifier and the resource owner credentials.

[0045] In the above embodiment, the first entity authenticates the resource owner, which can improve the reliability of authorization.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the resource owner identifier and the identifier of the third entity satisfy a first condition, including: the verified resource owner identifier and the identifier of the third entity satisfy the first condition.

[0047] In the above embodiment, by comparing the verified identifier of the resource owner with the identifier of the third entity, the reliability of the authorization can be improved.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the request information includes at least one of the following: perception role information, the perception role information includes the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; an association request for identification information and perception results; and an open request for perception context information.

[0049] In combination with some embodiments of the first aspect, in some embodiments, based on the resource owner identifier and the request information, generating a token for the third entity and / or sending a token for the third entity to the second entity includes: verifying the resource owner identifier; based on the verified resource owner identifier and the request information, generating a token for the third entity and / or sending a token for the third entity to the second entity.

[0050] In combination with some embodiments of the first aspect, in some embodiments, the token includes at least one of the following: a resource owner identifier; perception role information, the perception role information including the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; an indication of the association between the identification information and the perception result; and an indication of the openness of the perception context information.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the resource owner is one of the perception target, the perception target owner, the perception sender and the perception receiver, and the third entity is one of the perception target, the perception target owner, the perception sender and the perception receiver.

[0052] In combination with some embodiments of the first aspect, in some embodiments, the second entity is one of a terminal, a client, an application function, an access network device, and a network function.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the first entity is one of a network open function, a general application programming interface framework core function, and a network storage function.

[0054] In combination with some embodiments of the first aspect, in some embodiments, the resource owner identifier includes at least one of a user permanent identifier SUPI, a hidden user identifier SUCI, an application layer ID, a general public user identifier GPSI, an international mobile subscriber identity IMSI, and an international mobile subscriber number MSISDN, and the identifier of the third entity includes at least one of SUPI, SUCI, application layer ID, GPSI, IMSI, and MSISDN.

[0055] In a second aspect, an embodiment of the present disclosure proposes a communication method, which is applied to a second entity, and the method includes: sending a resource owner identifier and request information to a first entity, where the request information is used to request authorization from the resource owner for a third entity; and receiving a token for the third entity sent by the first entity, where the token for the third entity is generated based on the resource owner identifier and the request information.

[0056] In the above embodiment, the second entity sends the resource owner identifier and request information for requesting the resource owner to authorize the third entity to the first entity. The first entity can generate a token for the third entity and / or send a token for the third entity to the second entity based on the resource owner identifier and the request information, so that the second entity can obtain the resource owner's authorization for the third entity in a timely manner, thereby improving the efficiency of perceived communication.

[0057] In combination with some embodiments of the second aspect, in some embodiments, the request information includes an identifier of the third entity; and the token for the third entity is generated when the resource owner identifier and the identifier of the third entity meet the first condition.

[0058] In combination with some embodiments of the second aspect, in some embodiments, the resource owner identifier and the identifier of the third entity meet the first condition, including: the resource owner identifier and the identifier of the third entity are the same; or, there is a mapping relationship between the resource owner identifier and the identifier of the third entity.

[0059] In combination with some embodiments of the second aspect, in some embodiments, the first entity stores a mapping relationship between the resource owner identifier and the identifier of the third entity.

[0060] In combination with some embodiments of the second aspect, in some embodiments, the request information includes at least one of the following: an identifier of a third entity; perception role information, the perception role information including the identifier of the third entity and / or the perception role corresponding to the identifier of the third entity; an association request of the identification information and the perception result, the association request including the identifier of the third entity; an open request for perception context information, the open request including the identifier of the third entity.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the perception role includes at least one of a perception sender and a perception receiver.

[0062] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a failure message sent by the second entity, the failure message being generated when the resource owner identifier and the identifier of the third entity do not meet the first condition, the failure message indicating that the request is not authorized or the unauthorized part of the request.

[0063] In combination with some embodiments of the second aspect, in some embodiments, the token includes at least one of the following: an identifier of the third entity; perception role information, the perception role information including the identifier of the third entity and / or the perception role corresponding to the identifier of the third entity; an association indication of the identification information and the perception result, the association indication including the identifier of the third entity; an open indication of the perception context information, the open indication including the identifier of the third entity.

[0064] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: sending resource owner credentials to the first entity, where the resource owner credentials are used to authenticate the resource owner.

[0065] In combination with some embodiments of the second aspect, in some embodiments, the resource owner identifier and the identifier of the third entity satisfy a first condition, including: the verified resource owner identifier and the identifier of the third entity satisfy the first condition.

[0066] In combination with some embodiments of the second aspect, in some embodiments, the request information includes at least one of the following: perception role information, the perception role information includes the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; an association request for identification information and perception results; and an open request for perception context information.

[0067] In combination with some embodiments of the second aspect, in some embodiments, based on the resource owner identifier and the request information, generating a token for the third entity and / or sending a token for the third entity to the second entity includes: verifying the resource owner identifier; based on the verified resource owner identifier and the request information, generating a token for the third entity and / or sending a token for the third entity to the second entity.

[0068] In combination with some embodiments of the second aspect, in some embodiments, the token includes at least one of the following: a resource owner identifier; perception role information, the perception role information including the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; an indication of the association between the identification information and the perception result; and an indication of the openness of the perception context information.

[0069] In combination with some embodiments of the second aspect, in some embodiments, the resource owner is one of the perception target, the perception target owner, the perception sender and the perception receiver, and the third entity is one of the perception target, the perception target owner, the perception sender and the perception receiver.

[0070] In combination with some embodiments of the second aspect, in some embodiments, the second entity is one of a terminal, a client, an application function, an access network device, and a network function.

[0071] In combination with some embodiments of the second aspect, in some embodiments, the first entity is one of a network open function, a general application programming interface framework core function, and a network storage function.

[0072] In combination with some embodiments of the second aspect, in some embodiments, the resource owner identifier includes at least one of a user permanent identifier SUPI, a hidden user identifier SUCI, an application layer ID, a general public user identifier GPSI, an international mobile subscriber identity IMSI, and an international mobile subscriber number MSISDN, and the identifier of the third entity includes at least one of SUPI, SUCI, application layer ID, GPSI, IMSI, and MSISDN.

[0073] In a third aspect, an embodiment of the present disclosure proposes a first entity, comprising: a transceiver module for receiving a resource owner identifier and request information sent by a second entity, the request information being used to request authorization from the resource owner for a third entity; a processing module for generating a token for the third entity based on the resource owner identifier and the request information and / or sending a token for the third entity to the second entity.

[0074] In a fourth aspect, an embodiment of the present disclosure proposes a second entity, comprising: a transceiver module, used to send a resource owner identifier and request information to a first entity, wherein the request information is used to request authorization from the resource owner for a third entity; and receive a token for the third entity sent by the first entity, wherein the token for the third entity is generated based on the resource owner identifier and the request information.

[0075] In a fifth aspect, an embodiment of the present disclosure proposes a first entity, comprising: one or more processors; wherein the processor is used to execute the communication method of the first aspect.

[0076] In a sixth aspect, an embodiment of the present disclosure proposes a second entity, comprising: one or more processors; wherein the processor is used to execute the communication method of the second aspect.

[0077] In a seventh aspect, an embodiment of the present disclosure proposes a communication system, comprising a first entity and a second entity, wherein the first entity is configured to implement the communication method of the first aspect, and the second entity is configured to implement the communication method of the second aspect.

[0078] In an eighth aspect, an embodiment of the present disclosure proposes a storage medium storing instructions, wherein the storage medium is characterized in that when the instructions are executed on a communication device, the communication device executes the communication method of the first aspect or the second aspect.

[0079] In a ninth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation manner of the first aspect or the second aspect.

[0080] In a tenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first aspect or the second aspect.

[0081] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first aspect or the second aspect.

[0082] It is understandable that the aforementioned network functions, terminals, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0083] The embodiments of the present disclosure provide a communication method, a first entity, a second entity, a communication system, and a storage medium. In some embodiments, the terms "communication method" and "information processing method," "communication perception method," "perception communication method," and "perception authorization method" are interchangeable, and the terms "information processing system," "communication system," "communication perception information," "perception communication system," and "perception authorization system" are interchangeable.

[0084] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0085] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0086] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0087] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0088] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0089] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0090] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0091] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0092] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0093] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0094] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0095] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0096] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0097] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0098] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0099] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0100] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0101] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0102] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0103] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0104] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0105] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0106] As shown in FIG1 , a communication system 100 includes a first entity 101 and a second entity 102 .

[0107] In some embodiments, the first entity 101 may be an authorization server.

[0108] In some embodiments, the first entity 101 may be one of a Network Exposure Function (NEF), a Common API Framework (CAPIF) core function, and a Network Repository Function (NRF).

[0109] In some embodiments, the second entity 102 may be a perception requesting end for initiating a perception request.

[0110] In some embodiments, the second entity 102 may be one of a terminal (UE), a client, an application function (AF), an access network device, and a network function (NF).

[0111] In some embodiments, the terminal includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0112] In some embodiments, the network function may be a functional network element in a core network device. The core network device may be a device including a first network element, a second network element, etc., or may be multiple devices or a device group, each including all or part of the first network element, the second network element, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0113] In some embodiments, the network function may be a Gateway Mobile Location Centre (GMLC), a Location Management Function (LMF), or a network function specifically developed for the awareness service.

[0114] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0115] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0116] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0117] The disclosed embodiments relate to wireless sensing technology, which can obtain information about a remote sensing target and its characteristics without actually contacting the remote object. By analyzing the sensing data of the sensing target and its surroundings, meaningful information about the sensing target and its characteristics can be obtained. Among them, radar (radio detection and ranging) is a widely used wireless sensing technology that uses radio waves to determine the distance (range), angle or instantaneous linear velocity of the sensing target. Sensing technology can also include non-radio frequency sensors that have been used in other fields, such as time-of-flight (ToF) cameras, accelerometers, gyroscopes and lidars.

[0118] The disclosed embodiments can be applied to 3GPP-supported perception systems. Integrated perception and communication in 3GPP systems means that perception capabilities are provided by the same wireless communication system and infrastructure used for communication. Furthermore, in 3GPP-supported perception systems, both UEs and NR RAN nodes can act as perception senders and / or perception receivers.

[0119] The communication method provided by the embodiments of the present disclosure can be applied to real-time environmental monitoring, autonomous vehicles / unmanned aerial vehicles (UAVs), air pollution monitoring, indoor healthcare, and intrusion detection. Real-time environmental monitoring can use wireless signals to reconstruct environmental maps, further improving positioning accuracy and enabling environmentally-related applications. For example, a range of real-time monitoring applications can be implemented, including dynamic three-dimensional maps for assisted driving, pedestrian flow statistics, intrusion detection, and traffic detection. Autonomous vehicle / UAV applications share some common functional requirements. For example, autonomous vehicles / UAVs should support detect and avoid (DAA) to avoid obstacles. At the same time, autonomous vehicles / UAVs should have the ability to monitor path information, such as route selection and traffic compliance. Air pollution monitoring can use the received wireless information for weather or air quality monitoring, based on the varying attenuation characteristics of the received wireless signal quality as a function of air humidity, particulate matter (PM) concentration, and carrier frequency. Indoor healthcare and intrusion detection can implement respiratory rate estimation, respiratory depth estimation, apnea detection, elderly vital sign monitoring, and indoor intrusion detection.

[0120] The communication method provided by the embodiments of the present disclosure can be applied to perception-assisted communication scenarios. In perception-assisted communication scenarios, the terminal's location and channel environment can be perceived to narrow the beam scanning range and shorten the beam training time. The UE's location, speed, motion trajectory, and channel environment can be perceived to perform beam prediction, reducing the overhead of beam measurement and the delay of beam tracking. The UE's attributes and channel environment can be perceived to improve the performance of channel estimation.

[0121] In perception scenarios, it is important to obtain authorization from the perception target (e.g., person, user, building) or perception target owner (e.g., owner of a building) or terminal.

[0122] Specifically, before sensing a target, a third party (e.g., a terminal, a client on the terminal, AF) or a network function needs to obtain authorization from the sensing target or the sensing target owner.

[0123] In addition, it is also important to authorize a request for a specific terminal to act as a sensing sender or sensing receiver.

[0124] However, in some cases, the sensing target or the sensing target owner or the UE may not be able to process the authorization by itself. In the case where the sensing target or the sensing target owner or the terminal is unable to process the authorization by itself, the entity used to initiate sensing cannot obtain the authorization of the sensing target or the sensing target owner or the terminal in a timely manner.

[0125] The embodiment of the present disclosure provides a communication method, which receives a resource owner identifier and request information sent by a second entity, wherein the request information is used to request the resource owner to authorize a third entity; based on the resource owner identifier and the request information, a token for the third entity is generated and / or a token for the third entity is sent to the second entity. Based on the communication method provided by the embodiment of the present disclosure, the second entity sends the resource owner identifier and the request information for requesting the resource owner to authorize the third entity to the first entity. The first entity can generate a token for the third entity and / or send a token for the third entity to the second entity based on the resource owner identifier and the request information, so that the second entity can obtain the resource owner's authorization for the third entity in a timely manner, thereby improving the efficiency of perceived communication.

[0126] FIG2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a communication method, and the method includes:

[0127] Step S2101: The second entity sends a resource owner identifier, a resource owner credential, and request information to the first entity.

[0128] In some embodiments, the first entity receives the resource owner credentials, the resource owner credentials, and the request information sent by the second entity.

[0129] In some embodiments, the first entity may be an authorization server.

[0130] In some embodiments, the first entity may be one of a NEF, a CAPIF core function, and a NRF.

[0131] In some embodiments, the second entity may be a perception requesting end for initiating a perception request.

[0132] In some embodiments, the second entity may be one of a terminal, a client, an AF, an access network device, and a NF.

[0133] In some embodiments, the resource owner may be one of a sensing target, a sensing target owner, a sensing sender, and a sensing receiver.

[0134] In some embodiments, the resource owner identification may be, for example, a username.

[0135] In some embodiments, the resource owner credentials may be, for example, a password, a key, a passphrase, a certificate, or the like.

[0136] In some embodiments, the request information is used to request authorization from the resource owner for the third entity.

[0137] In some embodiments, the request information may include at least one of the following:

[0138] the identifier of the third entity;

[0139] Perception role information, the perception role information including an identifier of the third entity and / or a perception role corresponding to the identifier of the third entity;

[0140] a request for associating the identification information with the perception result, the association request including an identification of the third entity;

[0141] An open request for context-aware information, the open request including an identification of a third entity.

[0142] In other embodiments, the request information may include at least one of the following:

[0143] Perception role information, the perception role information including the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver;

[0144] Request for association of identification information and perception results;

[0145] An open request for context-aware information.

[0146] It is understandable that the request information may or may not include the identifier of the third entity. When the request information includes the identifier of the third entity, whether to generate a token can be determined based on whether the identifier of the third entity and the identifier of the resource owner are identical or a mapping relationship exists. When the request information does not include the identifier of the third entity, the identifier of the resource owner can be verified. Once the verification is successful, the contents of the request information are authorized, and the generated token includes the verified identifier of the resource owner and the contents of the request information.

[0147] In some embodiments, the perception role includes at least one of a perception sender and a perception receiver.

[0148] In some embodiments, the third entity may be one of a perception target, a perception target owner, a perception sender, and a perception receiver.

[0149] In some embodiments, the resource owner identifier includes at least one of a Subscription Permanent Identifier (SUPI), a Subscription Concealed Identifier (SUCI), an application layer ID, a Generic Public Subscription Identifier (GPSI), an International Mobile Subscriber Identity (IMSI), and an International Mobile Subscriber Number (MSISDN).

[0150] In some embodiments, the identity of the third entity includes at least one of SUPI, SUCI, application layer ID, GPSI, IMSI and MSISDN.

[0151] In some embodiments, the resource owner and the third entity may be the same, or may have a mapping relationship, for example, the resource owner is the owner of the resource target, and the third entity is the perception target owned by the perception target owner.

[0152] In some embodiments, the request to associate identification information with a perception result refers to a request to associate identification information with a perception result.

[0153] In some embodiments, the request for opening context-aware information refers to a request for opening context-aware information corresponding to a third entity.

[0154] It is understandable that the resource owner identifier, resource owner credential, and request information sent by the second entity to the first entity may be carried in the same request or in different requests, which is not limited in this disclosure.

[0155] In some embodiments, the first entity stores a mapping relationship between the resource owner identifier and the third entity identifier.

[0156] In some embodiments, the resource owner may store the resource owner identifier and the identifier of the corresponding third entity in the first entity, so that the first entity can perform authorization processing according to the resource owner identifier and the identifier of the third entity.

[0157] In some embodiments, the resource owner (eg, the aware target or aware target owner or the UE) may provide the resource owner's username and resource owner credentials to the second entity, and the second entity may send an authorization request on behalf of the resource owner.

[0158] In some embodiments, the second entity may obtain resource owner credentials from the resource owner, and the second entity sends the resource owner credentials obtained from the resource owner to the first entity to request an authorization token from the first entity.

[0159] Step S2102: The first entity authenticates the resource owner based on the resource owner identifier and the resource owner credential.

[0160] In some embodiments, the first entity authenticates the resource owner based on the resource owner identifier and the resource owner credential. After the identity authentication is successful, authorization is performed based on the resource owner identifier and the identifier of the third entity, which can improve the reliability of authorization.

[0161] In the embodiment of the present disclosure, the second entity can obtain the resource owner identifier and resource owner credential of the resource owner. The second entity sends the resource owner identifier and resource owner credential to the first entity, which means that the second entity can request an authorization token from the first entity on behalf of the resource owner.

[0162] In some embodiments, if the first entity successfully authenticates the resource owner based on the resource owner identifier and the resource owner credentials, it means that the second entity can request an authorization token from the first entity on behalf of the resource owner, and requests related to the resource owner sent by the second entity can be approved.

[0163] Step S2103: When the resource owner identifier and the identifier of the third entity meet the first condition, a token for the third entity is generated.

[0164] In some embodiments, when the verified resource owner identity and the identity of the third entity satisfy a first condition, a token for the third entity is generated.

[0165] In some embodiments, the first condition may be that the resource owner identifier and the third entity identifier are identical, or that a mapping relationship exists between the resource owner identifier and the third entity identifier. That is, a token for the third entity is generated when the resource owner identifier and the third entity identifier are identical, or when a mapping relationship exists between the resource owner identifier and the third entity identifier.

[0166] In the disclosed embodiment, the second entity possesses the resource owner credentials (e.g., a password) provided by the resource owner. Therefore, once the resource owner identifier and resource owner credentials sent by the second entity to the first entity are verified, it indicates that the second entity can request authorization on behalf of the resource owner. The first entity determines whether the resource owner identifier and the identifier of the third entity in the request information are identical, or whether a mapping relationship exists. If the resource owner identifier and the identifier of the third entity in the request information are identical, or a mapping relationship exists, a token for the third entity may be generated or sent.

[0167] For example, if the verified resource owner identifier is A, and the identifier of the third entity included in the request information sent by the second entity is also A, then the request can be authorized or approved.

[0168] In some embodiments, when the request information includes the identifier of the third entity, whether to generate a token can be determined based on whether the identifier of the third entity and the identifier of the resource owner are identical or have a mapping relationship.

[0169] In some embodiments, the token may include at least one of the following:

[0170] the identifier of the third entity;

[0171] Perception role information, the perception role information including an identifier of the third entity and / or a perception role corresponding to the identifier of the third entity;

[0172] an association indication between the identification information and the perception result, the association indication including an identification of the third entity;

[0173] An open indication of the context-aware information, the open indication including an identifier of a third entity.

[0174] In other embodiments, when the request information does not include the identifier of the third entity, the resource owner's identifier may be verified. Once the verification is successful, a token for the third entity is generated based on the verified resource owner's identifier and the request information. In other words, once the resource owner's identifier is successfully verified, the content in the request information can be authorized, and the generated token may include the verified resource owner's identifier and the content in the request information.

[0175] In other embodiments, the token may include at least one of the following:

[0176] Resource owner identifier;

[0177] Perception role information, where the perception role information includes the perception role that the resource owner is requested to assume, and the perception role includes at least one of a perception sender and a perception receiver;

[0178] an indication of the association between identification information and perception results;

[0179] Open indication of context-aware information.

[0180] Among them, the perception role information in the token indicates the perception role that the resource owner agrees to assume; the association indication of the identification information and the perception result in the token indicates that the resource owner agrees to associate the resource owner identification and the perception result; the open indication of the perception context indicates that the resource owner agrees to open the perception context, which includes the resource owner identification.

[0181] For example, if the request information includes perceived role information and the resource owner identifier has been verified, the generated token includes the perceived role information.

[0182] Step S2104: The first entity sends a token for the third entity to the second entity.

[0183] In some embodiments, the second entity receives a token sent by the first entity for the third entity.

[0184] In some embodiments, the first entity sends a token for the third entity to the second entity when the resource owner identification and the identification of the third entity satisfy a first condition.

[0185] It is understandable that steps S2103 and S2104 are optional. When the resource owner identifier and the identifier of the third entity meet the first condition, the first entity may generate a token for the third entity and / or send a token for the third entity to the second entity. In other words, the first entity may generate a token for the third entity; or the first entity may send a token for the third entity to the second entity; or the first entity may both generate a token for the third entity and send a token for the third entity to the second entity.

[0186] In the embodiment of the present disclosure, the first entity generates a token for the third entity, which may indicate that the second entity can know that the first entity generates the token or that the first entity has authorized the request.

[0187] Step S2105: When the resource owner identifier and the third entity identifier do not meet the first condition, the request information is not authorized.

[0188] In some embodiments, the first condition may be that the resource owner identifier and the third entity identifier are identical; or that a mapping relationship exists between the resource owner identifier and the third entity identifier. That is, if the resource owner identifier and the third entity identifier are different and no mapping relationship exists, the authorization process is terminated.

[0189] In an embodiment of the present disclosure, when the resource owner identifier provided by the second entity and the identifier of the third entity in the request information are different and no mapping relationship exists, it means that the second entity cannot request an authorization token for the third entity. Therefore, the first entity may not authorize the request information, for example, it may terminate the authorization process and / or send a failure message to the second entity.

[0190] For example, the verified resource owner identifier is A, the identifier of the third entity included in the request information sent by the second entity is B, and there is no mapping relationship between A and B, then the request will not be authorized.

[0191] Step S2106: The first entity sends a failure message to the second entity.

[0192] In some embodiments, the second entity receives a failure message sent by the first entity.

[0193] In some embodiments, when the resource owner identifier and the identifier of the third entity do not satisfy the first condition, the first entity sends a failure message to the second entity.

[0194] In some embodiments, the failure message indicates that the request was not authorized or a portion of the request was not authorized.

[0195] In an embodiment of the present disclosure, a first entity may send multiple request messages to a second entity, each request message including the identifier of a different third entity; or, the request message sent by the first entity to the second entity includes the identifiers of multiple third entities. The first entity may determine whether the resource owner identifier and the identifier of each third entity meet a first condition, and generate a token for the third entity for each third entity that meets the first condition; for each third entity that does not meet the first condition, the identifier of the third entity that does not meet the first condition may be included in a failure message, that is, the failure message may include the identifier of the unauthorized third entity.

[0196] It is understandable that step S2105 and step S2106 are optional. When the resource owner identifier and the identifier of the third entity do not satisfy the first condition, the first entity terminates the authorization process and / or sends a failure message to the second entity.

[0197] In the communication method provided by the embodiments of the present disclosure, a second entity sends a resource owner identifier and request information for requesting the resource owner to authorize a third entity to a first entity. The first entity can generate a token for the third entity based on the resource owner identifier and the request information and / or send a token for the third entity to the second entity, so that the second entity can obtain the resource owner's authorization for the third entity in a timely manner, thereby improving the efficiency of perceived communication.

[0198] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0199] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0200] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0201] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0202] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0203] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0204] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0205] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2106. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, step S2105 can be implemented as an independent embodiment, and step S2106 can be implemented as an independent embodiment. Steps S2101+S2102 can be implemented as an independent embodiment, steps S2103+S2105 can be implemented as an independent embodiment, steps S2103+S2106 can be implemented as an independent embodiment, steps S2104+S2105 can be implemented as an independent embodiment, and steps S2104+S2106 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0206] In some embodiments, steps S2101 to S2106 can be performed in an interchangeable order or simultaneously. Under no conflicting conditions, each step can be combined arbitrarily and the order of each step can be interchanged arbitrarily, which is not limited in this disclosure.

[0207] In some embodiments, steps S2101 and S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0208] In some embodiments, steps S2103 and S2104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0209] In some embodiments, steps S2105 and S2106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0210] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0211] FIG3A is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a communication method, which includes:

[0212] Step S3101: Obtain resource owner identification, resource owner credentials, and request information.

[0213] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0214] In some embodiments, the first entity receives the resource owner identification, resource owner credentials, and request information sent by the second entity.

[0215] Step S3102: Authenticate the resource owner based on the resource owner identifier and the resource owner credential.

[0216] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0217] In some embodiments, the first entity authenticates the resource owner based on the resource owner identification and the resource owner credentials.

[0218] Step S3103: When the resource owner identifier and the identifier of the third entity meet the first condition, a token for the third entity is generated.

[0219] The optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0220] In some embodiments, the first entity generates a token for the third entity when the resource owner identifier and the identifier of the third entity satisfy a first condition.

[0221] Step S3104: Send a token to the third entity.

[0222] The optional implementation of step S3104 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0223] In some embodiments, the first entity sends a token to the second entity for the third entity.

[0224] In some embodiments, the first entity may generate a token for the third entity and / or send the token for the third entity to the second entity.

[0225] Step S3105: When the resource owner identifier and the third entity identifier do not meet the first condition, the request information is not authorized.

[0226] The optional implementation of step S3105 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0227] In some embodiments, the first entity terminates the authorization process when the resource owner identifier and the identifier of the third entity do not satisfy the first condition.

[0228] Step S3106, sending a failure message.

[0229] The optional implementation of step S3106 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0230] In some embodiments, the first entity sends a failure message to the second entity.

[0231] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3106. For example, step S3101 can be implemented as an independent embodiment, step S3102 can be implemented as an independent embodiment, step S3103 can be implemented as an independent embodiment, step S3104 can be implemented as an independent embodiment, step S3105 can be implemented as an independent embodiment, step S3106 can be implemented as an independent embodiment, steps S3101+S3102 can be implemented as an independent embodiment, steps S3103+S3105 can be implemented as an independent embodiment, steps S3103+S3106 can be implemented as an independent embodiment, steps S3104+S3105 can be implemented as an independent embodiment, and steps S3104+S3106 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0232] In some embodiments, steps S3101 to S3106 can be performed in an interchangeable order or simultaneously. Under no conflicting conditions, each step can be combined arbitrarily and the order of each step can be interchanged arbitrarily, which is not limited in this disclosure.

[0233] In some embodiments, steps S3101 and S3102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0234] In some embodiments, steps S3103 and S3104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0235] In some embodiments, steps S3105 and S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0236] FIG3B is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a communication method, which includes:

[0237] Step S3201: Obtain resource owner identification and request information.

[0238] The optional implementation of step S3201 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0239] In some embodiments, the first entity receives the resource owner identification and request information sent by the second entity.

[0240] Step S3202: Based on the resource owner identifier and the request information, generate a token for the third entity and / or send the token for the third entity to the second entity.

[0241] The optional implementation of step S3202 can refer to the optional implementation of step S2103 and step S2104 in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0242] In some embodiments, the first entity generates a token for the third entity based on the resource owner identifier and the request information and / or sends the token for the third entity to the second entity.

[0243] The communication method involved in the embodiment of the present disclosure may include at least one of steps S3201 and S3202. For example, step S3201 may be implemented as an independent embodiment, and step S3202 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0244] In some embodiments, steps S3201 to S3202 can be performed in an interchangeable order or simultaneously. Under no conflicting conditions, each step can be combined arbitrarily and the order of each step can be interchanged arbitrarily, which is not limited in this disclosure.

[0245] In some embodiments, step S3201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0246] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG4 , the embodiment of the present disclosure relates to a communication method, which includes:

[0247] Step S4101: Send resource owner identification and request information.

[0248] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0249] In some embodiments, the second entity sends the resource owner identification and the request information to the first entity.

[0250] Step S4102: Acquire a token for the third entity.

[0251] The optional implementation of step S4102 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0252] In some embodiments, the second entity receives a token sent by the first entity for the third entity.

[0253] The communication method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4102. For example, step S4101 may be implemented as an independent embodiment, and step S4102 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0254] In some embodiments, steps S4101 and S4102 can be performed in different orders or simultaneously. Under no conflicting conditions, each step can be combined arbitrarily and the order of each step can be changed arbitrarily, which is not limited in this disclosure.

[0255] In some embodiments, step S4101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0256] In some embodiments, step S4102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0257] Figure 5 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 5, the embodiment of the present disclosure relates to a communication method, which includes:

[0258] Step S5101: The second entity sends a resource owner identifier and request information to the first entity.

[0259] The optional implementation of step S5101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0260] Step S5102: The first entity generates a token for the third entity based on the resource owner identifier and the request information and / or sends the token for the third entity to the second entity.

[0261] The optional implementation of step S5102 can refer to the optional implementation of steps S2103 and S2104 in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0262] In some embodiments, steps S5101 to S5102 can be performed in an interchangeable order or simultaneously. Under no conflicting conditions, each step can be combined arbitrarily and the order of each step can be interchanged arbitrarily, which is not limited in this disclosure.

[0263] In some embodiments, the above method may include the methods of the above embodiments of the communication system side, terminal side, network function side, etc., which will not be repeated here.

[0264] Figure 6 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 6, the embodiment of the present disclosure relates to a communication method, which includes:

[0265] Step S6101: The resource owner provides the client with a resource owner identifier and resource owner credentials.

[0266] In some embodiments, the resource owner may be a perception target or a perception target owner or a role owner, for example, the resource owner may be a person.

[0267] In some embodiments, the client may be a third party (such as a terminal (UE), a client on the terminal (client), AF) or an access network device or a network function, etc.

[0268] In some embodiments, the resource owner may provide the client with its resource owner identification and resource owner credentials, wherein the resource owner identification may be a user name and the resource owner credentials may be a password.

[0269] In some embodiments, the resource owner password credentials grant type is suitable for situations where the resource owner has a trust relationship with the client, such as a device operating system or a highly privileged application. This grant type is suitable for clients that can obtain the resource owner's credentials (username and password, typically using an interactive form). It is also used to migrate existing clients that use direct authentication schemes (such as Hypertext Transfer Protocol (HTTP) Basic or Digest authentication) to Open Authorization (OAuth) by converting stored credentials into access tokens.

[0270] In step S6102, the client sends the resource owner identifier and resource owner credentials to the authorization server.

[0271] In some embodiments, the authorization server may be a NEF, a CAPIF core function, or an NRF, among others.

[0272] In some embodiments, the client requests an access token from a token endpoint of the authorization server by including the resource owner receipt credentials received from the resource owner. When making the request, the client authenticates itself with the authorization server.

[0273] In some embodiments, when requesting to sense a specific target or requesting a UE to act as a specific role, the requested scope may include at least one of the following:

[0274] Identification of the sensing target or sensing target owner (e.g., 3GPP subscriber identity);

[0275] Role information (e.g., a UE ID and corresponding role, such as sensing transmitter or sensing receiver);

[0276] A request to associate an identity (e.g., a 3GPP user identity) with a sensing result;

[0277] A request for opening the perception context information may include an identity (eg, a 3GPP user identity).

[0278] Step S6103: The authorization server sends an authorization token to the client.

[0279] In some embodiments, the authorization server authenticates the client and verifies the resource owner credentials, and issues an access token if the client is authorized.

[0280] In some embodiments, the rules for performing authorization related to the perception target / perception target owner / role information / association request / open request may include at least one of the following:

[0281] Assuming that the resource owner has registered the association information of its corresponding perception target / perception target owner / UE on the authorization server, if the authenticated resource owner identifier is the same as the identifier related to the perception target / perception target owner / role information / association request / open request within the requested scope, or the authenticated resource owner identifier (i.e., the resource owner's user name) and the identity identifier in the request (i.e., perception target identifier, perception target owner identifier) ​​have a mapping relationship, then the association and open permission indication information is added to the token.

[0282] If the resource owner identifier is different from the identifiers associated with the perceived target / perceived target owner / role information / association request / open request within the requested scope, and there is no mapping between the authenticated resource owner identifier (i.e., the resource owner's username) and the identity identifiers in the request (i.e., the perceived target identifier and the perceived target owner identifier), the authorization server does not authorize the request or sends a failure message to the client. The failure message indicates whether the request was not authorized or which part of the request was not authorized.

[0283] The communication method involved in the embodiments of the present disclosure may include at least one of steps S6101 to S6103. In the embodiments of the present disclosure, any one of steps S6101 to S6103 can be implemented independently. For example, step S6101 can be implemented as an independent embodiment, step S6102 can be implemented as an independent embodiment, and step S6103 can be implemented as an independent embodiment, but the present disclosure is not limited thereto.

[0284] In some embodiments, steps S6101 to S6103 can be performed in an interchangeable order or simultaneously. Under no conflicting conditions, each step can be combined arbitrarily and the order of each step can be interchanged arbitrarily, which is not limited in this disclosure.

[0285] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0286] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0287] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0288] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0289] Figure 7A is a schematic diagram of the structure of the first entity proposed in an embodiment of the present disclosure. As shown in Figure 7A, the first entity 7100 may include: a transceiver module 7101 and a processing module 7102. In some embodiments, the transceiver module 7101 is used to receive the resource owner identifier and request information sent by the second entity, and the request information is used to request the resource owner to authorize the third entity; the processing module 7102 is used to generate a token for the third entity and / or send a token for the third entity to the second entity based on the resource owner identifier and the request information. Optionally, the transceiver module is used to execute at least one of the steps (such as steps S2101 and S2104, but not limited thereto) of the processing performed by the first entity in any of the above methods, and the processing module is used to execute at least one of the steps (such as steps S2102 and S2103, but not limited thereto) of the processing performed by the first entity in any of the above methods, which will not be repeated here.

[0290] FIG7B is a schematic diagram of the structure of the second entity proposed in an embodiment of the present disclosure. As shown in FIG7B , the second entity 7200 may include: a transceiver module 7201. In some embodiments, the transceiver module 7201 is used to send a resource owner identifier and request information to the first entity, wherein the request information is used to request authorization from the resource owner for a third entity; and receive a token for the third entity sent by the first entity, wherein the token for the third entity is generated based on the resource owner identifier and the request information (e.g., step S2101, step S2104, but not limited thereto). Details are omitted here.

[0291] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0292] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0293] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 8100 is used to perform any of the above methods. Optionally, one or more processors 8101 are used to call instructions to enable the communication device 8100 to perform any of the above methods.

[0294] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101 and step S2103, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step S2102 and step S2104, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface may be interchangeable, the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be interchangeable, and the terms receiver, receiving unit, receiver, and receiving circuit may be interchangeable.

[0295] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Alternatively, all or part of the memories 8103 may be located outside the communication device 8100. In alternative embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memories 8103 and may be configured to receive data from the memories 8103 or other devices, or to send data to the memories 8103 or other devices. For example, the interface circuits 8104 may read data stored in the memories 8103 and send the data to the processor 8101.

[0296] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0297] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0298] The chip 8200 includes one or more processors 8201. The chip 8200 is configured to execute any of the above methods.

[0299] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Alternatively, all or part of memory 8203 may be located external to chip 8200. Optionally, interface circuit 8202 is connected to memory 8203 and may be used to receive data from memory 8203 or other devices, or may be used to send data to memory 8203 or other devices. For example, interface circuit 8202 may read data stored in memory 8203 and send the data to processor 8201.

[0300] In some embodiments, the interface circuit 8202 performs at least one of the communication steps (e.g., step S2101 and step S2103, but not limited thereto) of the aforementioned method. The interface circuit 8202 performing the communication steps (e.g., step S2101 and step S2103, but not limited thereto) of the aforementioned method means, for example, that the interface circuit 8202 performs data exchange between the processor 8201, chip 8200, memory 8203, or transceiver device. In some embodiments, the processor 8201 performs at least one of the other steps (e.g., step S2102 and step S2104, but not limited thereto).

[0301] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0302] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 8100, the communication device 8100 is caused to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0303] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0304] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, characterized in that: Applied to a first entity, the method comprises: receiving a resource owner identifier and request information sent by the second entity, wherein the request information is used to request authorization from the resource owner for the third entity; Based on the resource owner identifier and the request information, a token for the third entity is generated and / or the token for the third entity is sent to the second entity.

2. The method according to claim 1, characterized in that The request information includes an identifier of the third entity; Generating a token for the third entity and / or sending the token for the third entity to the second entity based on the resource owner identifier and the request information includes: When the resource owner identifier and the identifier of the third entity meet a first condition, a token for the third entity is generated and / or the token for the third entity is sent to the second entity.

3. The method according to claim 2, characterized in that The resource owner identifier and the third entity identifier satisfy a first condition, including: The resource owner identifier is the same as the identifier of the third entity; or, a mapping relationship exists between the resource owner identifier and the identifier of the third entity.

4. The method according to claim 3, characterized in that The first entity stores a mapping relationship between the resource owner identifier and the identifier of the third entity.

5. The method according to claim 2, characterized in that The request information includes at least one of the following: the identifier of the third entity; Perception role information, the perception role information including an identifier of a third entity and / or a perception role corresponding to the identifier of the third entity; a request for associating the identification information with the perception result, the association request including an identification of the third entity; An open request for context-aware information, the open request including an identification of a third entity.

6. The method according to claim 5, characterized in that The perception role includes at least one of a perception sender and a perception receiver.

7. The method according to claim 2, characterized in that The method further comprises: When the resource owner identifier and the identifier of the third entity do not satisfy the first condition, the request information is not authorized.

8. The method according to claim 2, characterized in that The method further comprises: When the resource owner identifier and the identifier of the third entity do not satisfy the first condition, sending a failure message to the second entity; The failure message indicates that the request is not authorized or the unauthorized portion of the request.

9. The method according to claim 2, characterized in that The token includes at least one of the following: an identifier of the third entity; Perception role information, the perception role information including an identifier of a third entity and / or a perception role corresponding to the identifier of the third entity; an association indication between the identification information and the perception result, the association indication including an identification of the third entity; An open indication of the context-aware information, the open indication including an identification of a third entity.

10. The method according to claim 2, characterized in that Before generating a token for the third entity, the method further includes: receiving the resource owner credentials sent by the second entity; The resource owner is authenticated based on the resource owner identification and the resource owner credentials.

11. The method according to claim 10, characterized in that The resource owner identifier and the identifier of the third entity satisfy a first condition, including: the verified resource owner identifier and the identifier of the third entity satisfy the first condition.

12. The method according to claim 1, characterized in that The request information includes at least one of the following: Perception role information, the perception role information including the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; Request for association of identification information and perception results; An open request for context-aware information.

13. The method according to claim 12, characterized in that Generating a token for the third entity and / or sending the token for the third entity to the second entity based on the resource owner identifier and the request information includes: Verifying the resource owner identifier; Based on the verified resource owner identifier and the request information, a token for the third entity is generated and / or the token for the third entity is sent to the second entity.

14. The method according to claim 13, characterized in that The token includes at least one of the following: Resource owner identifier; Perception role information, the perception role information including the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; an indication of the association between identification information and perception results; Open indication of context-aware information.

15. The method according to any one of claims 1 to 14, characterized in that The resource owner is one of a sensing target, a sensing target owner, a sensing sender and a sensing receiver, and the third entity is one of a sensing target, a sensing target owner, a sensing sender and a sensing receiver.

16. The method according to any one of claims 1 to 14, characterized in that The second entity is one of a terminal, a client, an application function, an access network device and a network function.

17. The method according to any one of claims 1 to 14, characterized in that The first entity is one of a network open function, a general application programming interface framework core function, and a network storage function.

18. The method according to any one of claims 1 to 14, characterized in that The resource owner identifier includes at least one of a user permanent identifier SUPI, a hidden user identifier SUCI, an application layer ID, a general public user identifier GPSI, an international mobile subscriber identity IMSI, and an international mobile subscriber number MSISDN, and the identifier of the third entity includes at least one of SUPI, SUCI, application layer ID, GPSI, IMSI, and MSISDN.

19. A communication method, characterized in that: Applied to the second entity, the method comprises: Sending a resource owner identifier and request information to the first entity, where the request information is used to request authorization from the resource owner for the third entity; A token for the third entity sent by the first entity is received, where the token for the third entity is generated based on the resource owner identifier and the request information.

20. The method according to claim 19, wherein The request information includes an identifier of the third entity; The token for the third entity is generated when the resource owner identifier and the identifier of the third entity meet a first condition.

21. The method according to claim 20, characterized in that The resource owner identifier and the third entity identifier satisfy a first condition, including: The resource owner identifier is the same as the identifier of the third entity; or, a mapping relationship exists between the resource owner identifier and the identifier of the third entity.

22. The method according to claim 21, characterized in that The first entity stores a mapping relationship between the resource owner identifier and the identifier of the third entity.

23. The method according to claim 20, characterized in that The request information includes at least one of the following: the identifier of the third entity; Perception role information, the perception role information including an identifier of a third entity and / or a perception role corresponding to the identifier of the third entity; a request for associating the identification information with the perception result, the association request including an identification of the third entity; An open request for context-aware information, the open request including an identification of a third entity.

24. The method according to claim 23, wherein The perception role includes at least one of a perception sender and a perception receiver.

25. The method according to claim 19, wherein The method further comprises: A failure message is received from the second entity, where the failure message is generated when the resource owner identifier and the identifier of the third entity do not satisfy a first condition, and the failure message indicates that the request is not authorized or an unauthorized portion of the request.

26. The method according to claim 20, wherein The token includes at least one of the following: an identifier of the third entity; Perception role information, the perception role information including an identifier of a third entity and / or a perception role corresponding to the identifier of the third entity; an association indication between the identification information and the perception result, the association indication including an identification of the third entity; An open indication of the context-aware information, the open indication including an identification of a third entity.

27. The method according to claim 20, characterized in that The method further comprises: A resource owner credential is sent to the first entity, the resource owner credential being used to authenticate the resource owner.

28. The method according to claim 27, characterized in that The resource owner identifier and the identifier of the third entity satisfy a first condition, including: the verified resource owner identifier and the identifier of the third entity satisfy the first condition.

29. The method according to claim 19, wherein The request information includes at least one of the following: Perception role information, the perception role information including the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; Request for association of identification information and perception results; An open request for context-aware information.

30. The method according to claim 29, wherein The token is generated based on the verified resource owner identification and the request information.

31. The method according to claim 30, wherein The token includes at least one of the following: Resource owner identifier; Perception role information, the perception role information including the perception role requested to be assumed by the resource owner, the perception role including at least one of a perception sender and a perception receiver; an indication of the association between identification information and perception results; Open indication of context-aware information.

32. The method according to any one of claims 19 to 31, characterized in that The resource owner is one of a sensing target, a sensing target owner, a sensing sender and a sensing receiver, and the third entity is one of a sensing target, a sensing target owner, a sensing sender and a sensing receiver.

33. The method according to any one of claims 19 to 31, characterized in that The second entity is one of a terminal, a client, an application function, an access network device and a network function.

34. The method according to any one of claims 19 to 31, characterized in that The first entity is one of a network open function, a general application programming interface framework core function, and a network storage function.

35. The method according to any one of claims 19 to 31, characterized in that The resource owner identifier includes at least one of a user permanent identifier SUPI, a hidden user identifier SUCI, an application layer ID, a general public user identifier GPSI, an international mobile subscriber identity IMSI, and an international mobile subscriber number MSISDN, and the identifier of the third entity includes at least one of SUPI, SUCI, application layer ID, GPSI, IMSI, and MSISDN.

36. A first entity, characterized in that include: a transceiver module, configured to receive a resource owner identifier and request information sent by a second entity, wherein the request information is used to request authorization from the resource owner for a third entity; A processing module is configured to generate a token for the third entity and / or send the token for the third entity to the second entity based on the resource owner identifier and the request information.

37. A second entity, characterized in that: include: a transceiver module, configured to send a resource owner identifier and request information to the first entity, wherein the request information is used to request authorization from the resource owner for the third entity; A token for the third entity sent by the first entity is received, where the token for the third entity is generated based on the resource owner identifier and the request information.

38. A first entity, characterized in that include: one or more processors; The first entity is configured to execute the communication method according to any one of claims 1 to 18.

39. A second entity, characterized in that: include: one or more processors; The second entity is configured to execute the communication method according to any one of claims 19 to 35.

40. A communication system, characterized in that: The method comprises a first entity and a second entity, wherein the first entity is configured to implement the communication method according to any one of claims 1 to 18, and the second entity is configured to implement the communication method according to any one of claims 19 to 35.

41. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1 to 18 or the communication method according to any one of claims 19 to 35.

Images