Sensing methods, entities, communication system and storage medium

Abstract

The present disclosure relates to sensing methods, entities, a communication system and a storage medium. A sensing method comprises: sending a first request to a network exposure function entity, wherein the first request is used for requesting a sensing service, and the first request comprises a token, the token comprising authorization information related to the sensing service. In the present disclosure, a first request is sent to a network exposure function entity in a core network, the first request being used for requesting a sensing service and further comprising authorization information related to the sensing service, thereby laying a foundation for the authorization of a sensing service by means of a token in a core network.

Description

Sensing methods, entities, communication systems, and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to sensing methods, entities, communication systems and storage media. Background Technology

[0002] Wireless sensing technology refers to acquiring information about remote objects and their characteristics without physical contact. It utilizes sensor data from objects and their surrounding environment for analysis to obtain meaningful information about the objects and their features.

[0003] The integration of sensing and communication in related technologies means that sensing capabilities can only be provided by the same wireless communication systems and infrastructure used for communication, which limits the application of sensing capabilities.

[0004] Summary of the Invention

[0005] This disclosure presents sensing methods, entities, communication systems, and storage media.

[0006] In a first aspect, embodiments of this disclosure propose a sensing method, executed by a first entity, the method comprising:

[0007] Send the first request to the network open functionality entity;

[0008] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0009] Secondly, embodiments of this disclosure propose a sensing method, executed by a second entity, the method comprising:

[0010] Send the first request to the first network function entity;

[0011] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0012] Thirdly, embodiments of this disclosure propose a sensing method, executed by a network open function entity, the method comprising:

[0013] Receive the first request sent by the first untrusted entity;

[0014] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0015] Fourthly, embodiments of this disclosure propose a perception method, executed by a first network functional entity, the method comprising:

[0016] Receive the first message sent by the network open function entity;

[0017] The first information includes the second request; the second request is used to request the perception service.

[0018] Fifthly, embodiments of this disclosure propose a perception method, executed by a first network functional entity, the method comprising:

[0019] Receive the first request sent by the second entity;

[0020] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0021] Sixthly, this disclosure proposes a perception method executed by a third network functional entity, which is either a network repository functional entity or a core functional entity of a general API open framework. The method includes:

[0022] Send third information to the first network function entity;

[0023] The third piece of information is either feedback that the token is valid or a public key used to verify the token.

[0024] In a seventh aspect, embodiments of this disclosure provide a first entity, comprising:

[0025] The transceiver module is used to send the first request to the network open function entity;

[0026] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0027] Eighthly, embodiments of this disclosure propose a second entity, comprising:

[0028] The transceiver module is used to send a first request to the first network function entity;

[0029] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0030] Ninthly, embodiments of this disclosure propose a network open function entity, including:

[0031] The transceiver module is used to receive the first request sent by the first entity;

[0032] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0033] In a tenth aspect, embodiments of this disclosure propose a first network functional entity, comprising:

[0034] The transceiver module is used to receive the first information sent by the network open function entity;

[0035] The first information includes the second request; the second request is used to request the perception service.

[0036] Eleventhly, embodiments of this disclosure propose a first network functional entity, including...

[0037] The transceiver module is used to receive the first request sent by the second entity;

[0038] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0039] In a twelfth aspect, embodiments of this disclosure propose a third network functional entity, including:

[0040] The transceiver module is used to send third information to the first network function entity;

[0041] The third piece of information is either feedback that the token is valid or a public key used to verify the token.

[0042] In a thirteenth aspect, embodiments of this disclosure provide a first entity, comprising:

[0043] One or more processors;

[0044] The first entity is used to perform the perception method of any one of the first aspects of the embodiments of this disclosure.

[0045] In a fourteenth aspect, embodiments of this disclosure provide a second entity, comprising:

[0046] One or more processors;

[0047] The second entity is used to perform the perception method of any of the second aspects in the embodiments of this disclosure.

[0048] In a fifteenth aspect, embodiments of this disclosure propose a network open function entity, including:

[0049] One or more processors;

[0050] The network open function entity is used to perform the perception method of any of the third aspects in the embodiments of this disclosure.

[0051] In a sixteenth aspect, embodiments of this disclosure provide a first network functional entity, comprising:

[0052] One or more processors;

[0053] The first network functional entity is used to perform the perception method of any of the fourth aspects in the embodiments of this disclosure.

[0054] In a seventeenth aspect, embodiments of this disclosure provide a first network functional entity, comprising:

[0055] One or more processors;

[0056] The first network functional entity is used to perform the perception method of any of the fifth aspects in the embodiments of this disclosure.

[0057] In an eighteenth aspect, embodiments of this disclosure propose a third network functional entity, including:

[0058] One or more processors;

[0059] The third network functional entity is used to perform the perception method of any of the sixth aspects in the embodiments of this disclosure.

[0060] In a nineteenth aspect, embodiments of this disclosure provide a communication system, including a first entity, a network open function entity, a first network function entity, and a third network function entity; wherein the first entity is configured to implement the method of any one of the first aspects of this disclosure; the network open function entity is configured to implement the sensing method of any one of the third aspects of this disclosure; the first network function entity is configured to implement the sensing method of any one of the fourth aspects of this disclosure; and the third network function entity is configured to implement the sensing method of any one of the sixth aspects of this disclosure.

[0061] In a twentieth aspect, embodiments of this disclosure provide a communication system including a second entity, a first network function entity, and a third network function entity; wherein the second entity is configured to implement the method of any one of the second aspects of embodiments of this disclosure; the first network function entity is configured to implement the sensing method of any one of the fifth aspects of embodiments of this disclosure; and the third network function entity is configured to implement the sensing method of any one of the sixth aspects of embodiments of this disclosure.

[0062] In a twentieth aspect, embodiments of this disclosure provide a storage medium that, when instructions are executed on a communication device, causes the communication device to perform any of the sensing methods described in the embodiments of this disclosure.

[0063] In a twentieth aspect, embodiments of this disclosure provide a program product which is executed by a communication device using any of the sensing methods described in the embodiments of this disclosure. Attached Figure Description

[0064] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0065] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0066] Figure 2A is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure;

[0067] Figure 2B is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure;

[0068] Figure 2C is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure;

[0069] Figure 2D is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure;

[0070] Figure 3 is a flowchart illustrating a sensing method according to an embodiment of the present disclosure;

[0071] Figure 4 is a flowchart illustrating a sensing method according to an embodiment of the present disclosure;

[0072] Figure 5 is a flowchart illustrating a sensing method according to an embodiment of the present disclosure;

[0073] Figure 6A is a schematic flowchart illustrating a sensing method according to an embodiment of the present disclosure;

[0074] Figure 6B is a schematic flowchart illustrating a sensing method according to an embodiment of the present disclosure;

[0075] Figure 7A is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure;

[0076] Figure 7B is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure;

[0077] Figure 8A is a schematic diagram of the structure of the first entity proposed in an embodiment of this disclosure;

[0078] Figure 8B is a schematic diagram of the structure of the second entity proposed in an embodiment of this disclosure;

[0079] Figure 8C is a schematic diagram of the structure of the first network open function entity proposed in the embodiments of this disclosure;

[0080] Figure 8D is a schematic diagram of the structure of the first network functional entity proposed in an embodiment of this disclosure;

[0081] Figure 8E is a schematic diagram of the structure of the first network functional entity proposed in an embodiment of this disclosure;

[0082] Figure 8F is a schematic diagram of the structure of the third network functional entity proposed in an embodiment of this disclosure;

[0083] Figure 9A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0084] Figure 9B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0085] This disclosure presents a communication method, a terminal, a network element, a device, and a storage medium.

[0086] In a first aspect, embodiments of this disclosure propose a sensing method, executed by a first entity, the method comprising:

[0087] Send the first request to the network open functionality entity;

[0088] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0089] This disclosure embodiment lays the foundation for authorizing the perception service in the core network by making a first request to the network open function entity in the core network. The first request is used to request the perception service and also includes authorization information related to the perception service.

[0090] In some embodiments, the type of the first entity is any one of the following:

[0091] Unreliable application functions;

[0092] Untrusted terminals;

[0093] Untrusted perception client.

[0094] The first entity in this embodiment offers greater selectivity in terms of type, thereby expanding the application scope of the perception method.

[0095] In some embodiments, the first request includes at least one of the following:

[0096] The identifier of the requested perceived target;

[0097] The identifier of the target owner of the requested perception;

[0098] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0099] The requested sensing area;

[0100] The perceived time of the request;

[0101] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0102] Requests to open-aware contextual information.

[0103] In some embodiments, the token includes at least one of the following:

[0104] The identification of permitted perceived targets;

[0105] The identifier of the owner of the permitted perception target;

[0106] The identifier of the third terminal and the perception roles that the third terminal is allowed to assume;

[0107] Permissible sensory area;

[0108] Permissible perception time;

[0109] An indication that allows the identification of a fourth terminal to be associated with the sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role;

[0110] Instructions that allow open awareness of contextual information.

[0111] Secondly, embodiments of this disclosure propose a sensing method, executed by a second entity, the method comprising:

[0112] Send the first request to the first network function entity;

[0113] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0114] Send the first request to the first network function entity;

[0115] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0116] In this embodiment of the disclosure, a second entity sends a first request to a first network function entity. The first request is used to request a sensing service. The first request includes a token, which includes sensing-related authorization information, laying the foundation for authorization of sensing services in the core network through the token.

[0117] In some embodiments, the type of the second entity is any one of the following:

[0118] Trusted application functional entities;

[0119] A trusted terminal;

[0120] A trustworthy perception client.

[0121] In some embodiments, the first request includes at least one of the following:

[0122] The identifier of the requested perceived target;

[0123] The identifier of the target owner of the requested perception;

[0124] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0125] The requested sensing area;

[0126] The perceived time of the request;

[0127] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0128] Requests to open-aware contextual information.

[0129] In some embodiments, the token includes at least one of the following:

[0130] The identification of permitted perceived targets;

[0131] The identifier of the owner of the permitted perception target;

[0132] The identifier of the third terminal and the perception roles that the third terminal is allowed to assume;

[0133] Permissible sensory area;

[0134] Permissible perception time;

[0135] An indication that allows the identification of a fourth terminal to be associated with the sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role;

[0136] Instructions that allow open awareness of contextual information.

[0137] Thirdly, embodiments of this disclosure propose a sensing method, executed by a network open function entity, the method comprising:

[0138] Receive the first request sent by the first entity;

[0139] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0140] The network open function entity in this embodiment receives a first request sent by a first entity; since the first request includes a token, it lays the foundation for authorization of perception services in the core network via the token.

[0141] In some embodiments, the first request includes at least one of the following:

[0142] The identifier of the requested perceived target;

[0143] The identifier of the target owner of the requested perception;

[0144] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0145] The requested sensing area;

[0146] The perceived time of the request;

[0147] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0148] Requests to open-aware contextual information.

[0149] In some embodiments, the token includes at least one of the following:

[0150] The identification of permitted perceived targets;

[0151] The identifier of the owner of the permitted perception target;

[0152] The identifier of the third terminal and the perception roles that the third terminal is allowed to assume;

[0153] Permissible sensory area;

[0154] Permissible perception time;

[0155] An indication that allows the identification of a fourth terminal to be associated with the sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role;

[0156] Instructions that allow open awareness of contextual information.

[0157] In some embodiments, the method further includes:

[0158] Send the first message to the first network function entity;

[0159] The first piece of information is any one of the following:

[0160] The second request is used to request the awareness service;

[0161] Second request and first instruction;

[0162] Second request and second instruction;

[0163] The first instruction is used to instruct at least one of the following:

[0164] It is permissible to associate the identifier of a second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0165] Allows for open perception of contextual information;

[0166] The second instruction is used to instruct at least one of the following:

[0167] Refuse to associate the identifier of the second terminal with the perception result;

[0168] Refuse to disclose contextual information.

[0169] In some embodiments, sending the first information to the first network function entity further includes, before:

[0170] The token has been confirmed as a valid token.

[0171] In this embodiment of the disclosure, the first information will only be sent to the first network function entity if the token is determined to be a valid token. If the token is determined to be an invalid token, the process will end, that is, the first information will not be sent to the first network function entity.

[0172] In some embodiments, the second request includes at least one of the following:

[0173] The identifier of the requested perceived target;

[0174] The identifier of the target owner of the requested perception;

[0175] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0176] The requested sensing area;

[0177] The perceived time of the request;

[0178] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0179] Requests to open-aware contextual information.

[0180] In some embodiments, the first information is a second request and a first instruction, and sending the first information to the first network function entity is as follows:

[0181] Simultaneously send the second request and the first instruction to the first network function entity; or

[0182] The second request and the first instruction are sent sequentially to the first network functional entity;

[0183] The first information is the second request and the second instruction. Sending the first information to the first network function entity is as follows:

[0184] Simultaneously send a second request and a second instruction to the first network function entity; or

[0185] The second request and the second instruction are sent to the first network functional entity in sequence.

[0186] In the embodiments of this disclosure, the order in which the second request and the first instruction are sent is not limited, nor is the order in which the second request and the second instruction are sent.

[0187] In some embodiments, the first network function entity is at least one of the following types of enforcement points:

[0188] Select the enforcement point for at least one of the sensing receiver and the sensing sender;

[0189] Determine whether to authorize the mandatory execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role;

[0190] Determine whether to authorize the mandatory execution point that is aware of context information.

[0191] The first network function entity in this embodiment can serve as at least one type of enforcement point, thereby determining whether to authorize the second request based on its own type and in conjunction with the first information.

[0192] Fourthly, embodiments of this disclosure propose a perception method, executed by a first network functional entity, the method comprising:

[0193] Receive the first message sent by the network open function entity;

[0194] The first information includes the second request; the second request is used to request the perception service.

[0195] In some embodiments, the second request includes at least one of the following:

[0196] The identifier of the requested perceived target;

[0197] The identifier of the target owner of the requested perception;

[0198] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0199] The requested sensing area;

[0200] The perceived time of the request;

[0201] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0202] Requests to open-aware contextual information.

[0203] In some embodiments, the first network function entity is at least one of the following types of enforcement points:

[0204] Select the enforcement point for at least one of the sensing receiver and the sensing sender;

[0205] Determine whether to authorize the mandatory execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role;

[0206] Determine whether to authorize the mandatory execution point that is aware of context information.

[0207] In some embodiments, the first information further includes a first indication;

[0208] The first instruction is used to indicate at least one of the following:

[0209] It is permissible to associate the identifier of a second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0210] Allow open awareness of contextual information.

[0211] In some embodiments, the first network function entity is a mandatory execution point for determining whether to authorize the association of the identifier of the second terminal with the perception result;

[0212] The first instruction is used to indicate that the identifier of the second terminal can be associated with the sensing result;

[0213] The method also includes:

[0214] The identifier of the second terminal is linked to the perception result.

[0215] In this embodiment of the disclosure, when the first network function entity is a mandatory execution point for determining whether to authorize the association of the identifier of the second terminal with the perception result, and the first indication is used to indicate that the association of the identifier of the second terminal with the perception result is allowed, then the first network function triggers the association of the identifier of the second terminal with the perception result.

[0216] In some embodiments, triggering the association between the identifier of the second terminal and the perception result includes: triggering the association between the identifier of the second terminal and the perception result without triggering an authorization process for associating the identifier of the second terminal and the perception result. Embodiments of this disclosure can improve the efficiency of associating the identifier of the second terminal with the perception result.

[0217] In some embodiments, the first network function entity is the execution point for determining whether to authorize open awareness context information;

[0218] The first instruction is used to indicate whether open perceptual context information is allowed;

[0219] The method also includes:

[0220] Trigger open-aware context information.

[0221] The first network function entity in this embodiment is a point for determining whether to authorize the execution of open awareness context information, and the first indication is used to indicate that when open awareness context information is allowed, the first network function entity also triggers open awareness context information.

[0222] In some embodiments, open-aware context information includes:

[0223] Trigger the opening of the perception context information without triggering the authorization process for opening the perception context information.

[0224] This embodiment of the disclosure can trigger the opening of the perception context without triggering the authorization process for opening the perception context, thereby improving the efficiency of triggering the opening of the perception context.

[0225] In some embodiments, the first network function entity is a mandatory execution point for determining whether to authorize the association of the identifier of the second terminal with the perception result;

[0226] The first information includes a second instruction, which is used to indicate that the identifier of the second terminal is refused to be associated with the sensing result; the second terminal is at least one of the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal that assumes the sensing role.

[0227] The method also includes at least one of the following:

[0228] It refuses to associate the identifier of the second terminal with the perception result.

[0229] In some embodiments, the first network function entity is a mandatory execution point for determining whether to authorize the association of the identifier of the second terminal with the perception result; the method further includes:

[0230] If no first or second instruction is received, an authorization process is triggered to associate the identifier of the second terminal with the perception result. After the authorization process is completed, the identifier of the second terminal is also associated with the perception result.

[0231] In some embodiments, the first network function entity is a mandatory execution point for determining whether to authorize open awareness context information;

[0232] The first information includes a second instruction, which is used to indicate that open perceptual context information is refused.

[0233] The method also includes:

[0234] Contextual information is not disclosed.

[0235] The first network functional entity in this embodiment of the present disclosure refuses to open the open awareness context information and does not open the awareness context information according to the second instruction.

[0236] In some embodiments, the first network function entity is a mandatory execution point for determining whether to authorize open awareness context information;

[0237] The method also includes:

[0238] If no first or second instruction is received, the authorization process for open sensing context information is triggered. After obtaining authorization for open sensing context information, the open sensing context information is opened.

[0239] In some embodiments, the second request includes the identifier of the first terminal and the perception role requested to be assumed by the first terminal;

[0240] The first network functional entity is the enforcement point for selecting the sensing receiver and the sensing sender;

[0241] The method also includes:

[0242] Based on the identifier of the first terminal in the second request and the role requested to be assumed by the first terminal, the first terminal is determined to assume the perception role.

[0243] In some embodiments, the second request does not include the identifier of the first terminal or the perception role requested to be assumed by the first terminal;

[0244] The first network functional entity is the enforcement point for selecting the sensing receiver and the sensing sender;

[0245] The method also includes:

[0246] Trigger the discovery process of the sensing sender or sensing receiver to identify the sensing sender and sensing receiver.

[0247] In some embodiments, the method further includes:

[0248] Send the first message to the second network function entity.

[0249] If the first network function entity in this embodiment determines that further authorization is required from the second network function entity, the first network function entity may send first information to the second network function entity.

[0250] Fifthly, embodiments of this disclosure propose a perception method, executed by a first network functional entity, the method comprising:

[0251] Receive the first request sent by the second entity;

[0252] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0253] The first network functional entity disclosed herein receives a first request sent by a second entity. The first request is used to request a sensing service. The first request includes a token, which includes authorization information related to the sensing service, laying the foundation for authorization of the sensing service in the core network through the token.

[0254] In some embodiments, the type of the second entity is any one of the following:

[0255] Reliable application functionality;

[0256] A trusted terminal;

[0257] A trustworthy perception client.

[0258] In some embodiments, the first request includes at least one of the following:

[0259] The identifier of the requested perceived target;

[0260] The identifier of the target owner of the requested perception;

[0261] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0262] The requested sensing area;

[0263] The perceived time of the request;

[0264] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0265] Requests to open-aware contextual information.

[0266] In some embodiments, the token includes at least one of the following:

[0267] The identification of permitted perceived targets;

[0268] The identifier of the owner of the permitted perception target;

[0269] The identifier of the third terminal and the perception roles that the third terminal is allowed to assume;

[0270] Permissible sensory area;

[0271] Permissible perception time;

[0272] An indication that allows the identification of a fourth terminal to be associated with the sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role;

[0273] Instructions that allow open awareness of contextual information.

[0274] In some embodiments, the first network function entity is at least one of the following types of execution points:

[0275] Select the enforcement point for at least one of the sensing receiver and the sensing sender;

[0276] Determine whether to authorize the execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role;

[0277] Determine whether to authorize the execution point that is aware of context information.

[0278] In some embodiments, the first network function entity is an execution point that determines whether to authorize associating the identifier of the second terminal with the sensing result; the second terminal is at least one of the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal that assumes the sensing role.

[0279] The method also includes:

[0280] Once the token is confirmed to be valid, it is determined that the identifier of the second terminal is allowed to be associated with the sensing result, thus triggering the association between the identifier of the second terminal and the sensing result.

[0281] In some embodiments, the token does not include an indication that allows the identifier of a fourth terminal to be associated with the sensing result;

[0282] The identifier that triggers the association between the second terminal and the sensing result includes:

[0283] Without triggering the authorization process of associating the identifier of the second terminal with the perception result, the association between the identifier of the second terminal and the perception result is triggered.

[0284] In this embodiment of the disclosure, if the token does not indicate that the identifier of the fourth terminal is allowed to be associated with the perception result, and the second request includes a request to associate the identifier of the second terminal with the perception result, the first network function entity can also determine that the identifier of the second terminal is allowed to be associated with the perception result. At this time, triggering the association of the identifier of the second terminal with the perception result includes: triggering the association of the identifier of the second terminal with the perception result without triggering the authorization process of associating the identifier of the second terminal with the perception result, which can improve the efficiency of association.

[0285] In some embodiments, the first network function entity is an execution point that determines whether to authorize associating the identifier of the second terminal with the sensing result; the second terminal is at least one of the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal that assumes the sensing role.

[0286] The method also includes:

[0287] If the token is confirmed to be valid, and the association between the identifier of the second terminal and the perception result is rejected based on the token, then perform any one of the following steps:

[0288] The identifier of the second terminal is not associated with the perception result;

[0289] The authorization process that associates the identifier and perception result of the second terminal is not triggered.

[0290] In some embodiments, the first network function entity is an execution point that determines whether to authorize the association of the identifier of the second terminal with the perception result;

[0291] The method also includes

[0292] The token is confirmed to be a valid token. The token does not contain an indication that allows the identification of the fourth terminal to be associated with the perception result, triggering the authorization process of associating the identification of the second terminal with the perception result.

[0293] The second terminal is at least one of the following: the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal that assumes the sensing role.

[0294] The fourth terminal is at least one of the following: the terminal corresponding to the permitted sensing target, the terminal of the permitted sensing target owner, and the terminal permitted to assume the sensing role.

[0295] In some embodiments, the first network function entity is the execution point for determining whether to authorize open awareness context information;

[0296] The method also includes:

[0297] Once the token is confirmed to be valid, the access to the perception context information is determined based on the token.

[0298] In some embodiments, open-aware context information includes:

[0299] Without triggering the authorization process of associating the identifier and perception result of the second terminal, the perception context information is made available;

[0300] The second terminal is at least one of the terminal corresponding to the requested sensing target, the terminal of the owner of the requested sensing target, and the first terminal; the first terminal is the terminal that is requested to assume the sensing role.

[0301] In some embodiments, the first network function entity is the execution point for determining whether to authorize open awareness context information;

[0302] The method also includes:

[0303] If the token is determined to be a valid token, the perception context information will be refused to be opened based on the token.

[0304] In some embodiments, the first network function entity is the execution point for determining whether to authorize open awareness context information;

[0305] The method also includes:

[0306] Once the token is determined to be a valid token, and the token does not contain an indication that allows Open Aware Context Information, the authorization process for Open Aware Context Information is triggered.

[0307] In some embodiments, determining a token to be a legitimate token includes at least one of the following:

[0308] Send a token to the third network function entity; confirm the token as a valid token based on the information received from the third network function entity that the token is a valid token;

[0309] The token is verified based on the public key sent by the pre-obtained third network function entity to determine that the token is a legitimate token;

[0310] Among them, the third network functional entity is either a network warehousing functional entity or a core functional entity of a general API open framework.

[0311] In some embodiments, the method further includes:

[0312] Send the first message to the second network function entity;

[0313] The first piece of information is any one of the following:

[0314] The second request is used to request the awareness service;

[0315] Second request and first instruction;

[0316] Second request and second instruction;

[0317] The first instruction is used to instruct at least one of the following:

[0318] It is permissible to associate the identifier of a second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0319] Allows for open perception of contextual information;

[0320] The second instruction is used to instruct at least one of the following:

[0321] Refuse to associate the identifier of the second terminal with the perception result;

[0322] Refuse to disclose contextual information.

[0323] Sixthly, this disclosure proposes a perception method executed by a third network functional entity, which is either a network repository functional entity or a core functional entity of a general API open framework. The method includes:

[0324] Send third information to the first network function entity;

[0325] The third piece of information is either feedback that the token is valid or a public key used to verify the token.

[0326] In some embodiments, the third information is feedback that the token is a valid token. Sending the third information to the first network function entity includes, prior to:

[0327] Receive a token sent by the first network function entity; the token includes authorization information related to the perception service.

[0328] In a seventh aspect, embodiments of this disclosure provide a first entity, comprising:

[0329] The transceiver module is used to send the first request to the network open function entity;

[0330] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0331] Eighthly, embodiments of this disclosure propose a second entity, comprising:

[0332] The transceiver module is used to send a first request to the first network function entity;

[0333] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0334] Ninthly, embodiments of this disclosure propose a network open function entity, including:

[0335] The transceiver module is used to receive the first request sent by the first entity;

[0336] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0337] In a tenth aspect, embodiments of this disclosure propose a first network functional entity, comprising:

[0338] The transceiver module is used to receive the first information sent by the network open function entity;

[0339] The first information includes the second request; the second request is used to request the perception service.

[0340] Eleventhly, embodiments of this disclosure propose a first network functional entity, including...

[0341] The transceiver module is used to receive the first request sent by the second entity;

[0342] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0343] In a twelfth aspect, embodiments of this disclosure propose a third network functional entity, including:

[0344] The transceiver module is used to send third information to the first network function entity;

[0345] The third piece of information is either feedback that the token is valid or a public key used to verify the token.

[0346] In a thirteenth aspect, embodiments of this disclosure provide a first entity, comprising:

[0347] One or more processors;

[0348] The first network element is used to execute the method of any one of the first aspects in the embodiments of this disclosure.

[0349] In a fourteenth aspect, embodiments of this disclosure provide a second entity, comprising:

[0350] One or more processors;

[0351] The second network element is used to perform the method of any one of the second aspects in the embodiments of this disclosure.

[0352] In a fifteenth aspect, embodiments of this disclosure propose a network open function entity, including:

[0353] One or more processors;

[0354] The third network element is used to execute the communication method of any of the third aspects in the embodiments of this disclosure.

[0355] In a sixteenth aspect, embodiments of this disclosure provide a first network functional entity, comprising:

[0356] One or more processors;

[0357] The AMF network element is used to execute the communication method of any of the fourth aspects in the embodiments of this disclosure.

[0358] In a seventeenth aspect, embodiments of this disclosure provide a first network functional entity, comprising:

[0359] One or more processors;

[0360] The first terminal is used to execute the communication method of any of the fifth aspects in the embodiments of this disclosure.

[0361] In an eighteenth aspect, embodiments of this disclosure propose a third network functional entity, including:

[0362] One or more processors;

[0363] The second terminal is used to execute the communication method of any of the sixth aspects of the embodiments of this disclosure.

[0364] In a nineteenth aspect, embodiments of this disclosure provide a communication system, including a first entity, a network open function entity, a first network function entity, and a third network function entity; wherein the first entity is configured to implement the method of any one of the first aspects of this disclosure; the network open function entity is configured to implement the communication method of any one of the third aspects of this disclosure; the first network function entity is configured to implement the communication method of any one of the fourth aspects of this disclosure; and the third network function entity is configured to implement the communication method of any one of the sixth aspects of this disclosure.

[0365] In a twentieth aspect, embodiments of this disclosure provide a communication system, including a second entity, a first network function entity, and a third network function entity; wherein the second entity is configured to implement the method of any one of the second aspects of embodiments of this disclosure; the first network function entity is configured to implement the communication method of any one of the fifth aspects of embodiments of this disclosure; and the third network function entity is configured to implement the communication method of any one of the sixth aspects of embodiments of this disclosure.

[0366] In a twentieth aspect, embodiments of this disclosure provide a storage medium that, when instructions are executed on a communication device, causes the communication device to perform any of the methods described in the embodiments of this disclosure.

[0367] In a twentieth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the optional implementations of the first, second, third, fourth, fifth, and sixth aspects.

[0368] In a twentieth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the optional implementations of the first, second, third, fourth, fifth, and sixth aspects.

[0369] In a twentieth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the optional implementations of the first, second, third, fourth, fifth, and sixth aspects described above.

[0370] Understandably, the aforementioned entities, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure, laying the foundation for authorization of perception services via tokens in the core network, enabling the core network to verify tokens and allow perception-related authorization information to obtain the authorization information in the token. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0371] This disclosure provides sensing methods, entities, communication systems, and storage media. In some embodiments, terms such as communication method, signal transmission method, and wireless frame transmission method can be used interchangeably, as can terms such as information processing system and communication system.

[0372] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular 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 particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0373] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0374] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0375] In the embodiments of this disclosure, "multiple" refers to two or more.

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

[0377] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0378] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0379] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0380] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0381] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0382] In some embodiments, the terms “greater than,” “less 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 lower than,” and “above” can be used interchangeably, as can the terms “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”.

[0383] In some embodiments, the apparatus and device may be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they may also be understood as "equipment", "device", "circuit", "device", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "body", etc.

[0384] In some embodiments, "access network device (AN device)" and "radio access network device (radio device)" are mentioned.

[0385] The terms "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," "carrier," "component carrier," and "bandwidth part (BWP)" are interchangeable.

[0386] In some embodiments, the terms "terminal", "terminal device", "user equipment", "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", and "client" can be used interchangeably.

[0387] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0388] 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, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0389] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0390] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0391] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0392] In some embodiments, “get,” “obtain,” “get,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, processing and obtaining on their own, or autonomously implementing, among other meanings.

[0393] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0394] In some embodiments, "pre-defined" or "pre-set" can be interpreted as pre-specified in an agreement or the like, or as a device or the like performing a pre-set action.

[0395] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0397] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0398] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a terminal 101, an access network device 102, and a core network device 103.

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

[0400] In some embodiments, the access network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0401] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0402] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0403] In some embodiments, the core network device 103 may be a single device, including a first network element 1031, a second network element 1032, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element 1031, the second network element 1032, the third network element 1033, etc. Network elements may be virtual or physical. The core network may include, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0404] In some embodiments, the first network element 1031 is, for example, a Network Exposure Function (NEF).

[0405] In some embodiments, the second network element 1032 is, for example, a network function (NF).

[0406] In some embodiments, the third network element 1033 is, for example, a Network Repository Function (NRF) or a Common API Framework for 3GPP Northbound APIs Core Function (CCF).

[0407] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0408] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0409] The embodiments disclosed herein 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), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a 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, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0410] 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 an object. Other sensing technologies include non-radio frequency sensors already used in other fields, such as Time-of-Flight (ToF) cameras, accelerometers, gyroscopes, and lidar.

[0411] Integrated sensing and communication in a 3GPP system means that sensing capabilities are provided by the same wireless communication systems and infrastructure used for communication. Furthermore, both the UE and the NR RAN node can be used as sensing transmitters and sensing receivers in a 3GPP-enabled sensing system.

[0412] The embodiments disclosed herein can be applied to the following scenarios:

[0413] Real-time environmental monitoring: Reconstruct environmental maps using wireless signals to further improve positioning accuracy and enable environmental applications, such as a series of real-time monitoring applications, including dynamic 3D maps for driver assistance, pedestrian flow statistics, intrusion detection, and traffic detection.

[0414] Autonomous vehicles / drones: Autonomous vehicle / drone applications share some common functional requirements. For example, autonomous vehicles / drones should support Detect and Avoid (DAA) to avoid obstacles. Simultaneously, autonomous vehicles / drones should be able to monitor path information, such as choosing routes and complying with traffic regulations.

[0415] Air pollution monitoring: The quality of the received wireless signal exhibits different attenuation characteristics as air humidity, air particulate matter concentration, carrier frequency, etc., and can be used for weather or air quality detection.

[0416] Indoor healthcare and intrusion detection. Capable of respiratory rate estimation, respiratory depth estimation, vital sign monitoring in the elderly, and indoor intrusion detection.

[0417] Sensing the wireless communication channel and environment can further improve the performance of the communication system. Some examples of sensor-assisted communication scenarios are as follows:

[0418] The location and channel environment of the sensing terminal are used to narrow the beam scanning range and shorten the beam training time.

[0419] The location, speed, motion trajectory, and channel environment of the sensing terminal are used for beam prediction, reducing the overhead of beam measurement and the latency of beam tracking.

[0420] To improve the performance of channel estimation, we need to understand the attributes of the UE and the channel environment.

[0421] In the perception scenario, this disclosure embodiment considers four types of authorization:

[0422] First, as untrusted entities, such as terminals, clients on terminals, application function (AF) entities, etc., requesters of sensing services need to be authorized to sense targets, such as humans, terminals, buildings, etc.

[0423] Second, an untrusted first entity or / or network needs to obtain authorization from the terminal before it can request the terminal to act as a sensing sender or sensing receiver.

[0424] Third, the network needs to obtain authorization from the terminal in order to associate the terminal's 3GPP user identity with the sensing results.

[0425] Fourth, the network should obtain authorization from the terminal to open up sensing context information, such as terminal identifier, terminal location, etc.

[0426] In this embodiment of the disclosure, a token-based authorization mechanism is deployed to enable untrusted / trusted entities to obtain authorization information. Before triggering the sensing service, the untrusted / trusted entity can obtain a token. Compared to related technologies, the token in this embodiment includes authorization information related to the sensing service, such as permission to associate a 3GPP user identity with the sensing result to determine how to perform the sensing service.

[0427] It should be noted that the relevant technology does not have a mechanism that enables the core network to verify tokens and instruct the perception-related network function entities on how to perform perception services.

[0428] Figure 2A is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure. As shown in Figure 2A, this disclosure relates to a sensing method for a communication system 100, the method comprising:

[0429] S2101, The first entity sends a first request to the network open function entity.

[0430] In some embodiments, the type of the first entity is an untrusted application function (AF), an untrusted terminal, or an untrusted sensing client. An untrusted application function can refer to a third-party application function. An untrusted sensing client can be a sensing client running on an untrusted terminal or an untrusted sensing client running on a trusted terminal. In some embodiments, if the default terminal is untrusted, then the type of the first entity can be a terminal. In some embodiments, if the default sensing client is untrusted, then the type of the first entity can be a sensing client.

[0431] In some embodiments, the first request includes at least one of the following:

[0432] 1) Identification of the requested perceived target;

[0433] 2) The identifier of the owner of the requested perceived target;

[0434] 3) The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0435] 4) The requested sensing area;

[0436] 5) The time it takes to perceive the request;

[0437] 6) A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0438] 7) Requests to open contextual information.

[0439] It should be noted that the type of sensing target in this embodiment of the disclosure can be a terminal, a building, plants or animals, etc., and this embodiment of the disclosure does not impose specific limitations. Taking a building as an example, the owner of the sensing target can be the person responsible for managing the building, such as the building's property management personnel.

[0440] The sensing area in this embodiment can be represented by the geographical coordinates of the sensing area.

[0441] The sensing time in this embodiment of the disclosure can be one or more moments or one or more time periods.

[0442] In some embodiments, the token includes at least one of the following:

[0443] 1) Identification of permitted perceived targets;

[0444] 2) The identification of the owner of the permitted target;

[0445] 3) Identification of the third terminal and the perception roles permitted to be assumed by the third terminal;

[0446] 4) Permissible sensory area;

[0447] 5) Allowable perception time;

[0448] 6) An indication that allows the identification of a fourth terminal to be associated with the perception result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted perception target, the terminal of the owner of the permitted perception target, and the terminal that assumes the perception role.

[0449] 7) Allow instructions to open the context information.

[0450] S2102, The network open function entity sends the first information to the first network function entity.

[0451] In this embodiment of the disclosure, the network open function entity determines that the token is valid, then determines whether to authorize the first request based on the token, and determines the first information based on the determination result.

[0452] In this embodiment of the disclosure, the network open function entity determines whether the token is valid by interacting with a third network function entity.

[0453] The third network function entity in this disclosure can be the Network Repository Function (NRF) or the Common API Framework for 3GPP Northbound APIs Core Function (CAPIF CF). In some embodiments, CAPIF CF can also be abbreviated as CCF.

[0454] In some embodiments, a network open function entity sends a token to a third network function entity. The third network function entity determines whether the token is valid and provides feedback to the network open function entity. The network open function entity then determines whether the token is valid based on the feedback from the third network function entity.

[0455] In some embodiments, the third network function entity sends a verification token to the network open function entity in advance. When the network open function entity compares the verification token with the token in the first request, if the two match, the network open function entity determines that the token is valid.

[0456] In some embodiments, the network open function obtains the public key of a third network entity from the third network entity and uses the public key to determine whether the token is valid.

[0457] In some embodiments, the first request in this application may include only mandatory request items, or it may include optional request items in addition to mandatory request items:

[0458] Mandatory request items may include the identifier of the requested sensing target, the identifier of the owner of the requested sensing target, the identifier of the first terminal, the sensing role to be undertaken by the first terminal, the requested sensing area, the requested sensing time, etc.; optional request items may include requests to associate the identifier of the second terminal with the sensing result, requests to open sensing context information, etc.

[0459] In some embodiments, the token may include only mandatory allowed items, or it may include optional allowed items in addition to mandatory allowed items:

[0460] Mandatory permitted items may include the identifier of the permitted sensing target, the identifier of the permitted sensing target owner, the identifier of the third terminal, the permitted sensing role of the third terminal, the permitted sensing area, the permitted sensing time, etc.; optional permitted items may include instructions to associate the identifier of the fourth terminal with the sensing result, instructions to open the sensing context information, etc.

[0461] After determining that the token is valid, the network open function entity in this embodiment first determines whether the mandatory allowed items in the token conflict with the mandatory request items in the first request. If any mandatory request item conflicts, the network open function entity does not authorize the first request, that is, it no longer sends the first information to the first network function entity. If all mandatory request items do not conflict, the first information is sent.

[0462] In some embodiments, the first network function entity may be a functional entity that is open to sensing services, such as an authentication management function (AMF), a network data analytics function (NWDAF), a gateway mobile location center (GMLC), a location management function (LMF), or a sensing function.

[0463] For example, if the mandatory request item is that the identifier of the requested sensing target is 1, while the corresponding mandatory allowed item is that the identifier of the allowed sensing target is 2, then the mandatory request item is rejected because the identifiers of the allowed and requested sensing targets are inconsistent. As another example, if the mandatory request item is that terminal a is requested to assume the sensing role of a sensing receiver, but the corresponding mandatory allowed item is that terminal a is allowed to assume the sensing role of a sensing sender, then the mandatory request item is rejected because the mandatory and allowed items are inconsistent.

[0464] In addition to the inconsistencies mentioned above, if the required allowed items do not cover the required requested items, the required requested items will also be rejected. For example, if the required requested items are marked as 1 for allowed perception targets, and the required requested items are marked as 1 and 2 for requested perception targets, the required requested items will also be rejected because the required allowed items do not cover the required requested items.

[0465] In some embodiments, after the Network Open Functions entity authorizes the first request, the specific type of the first information is determined based on whether the first request includes optional request items and whether the token includes optional permission items. Specifically:

[0466] 1) If the optional permitted items of the token do not conflict with the optional requested items of the first request, then the first information includes the second request and the first instruction;

[0467] 2) If the optional allowed items of the token conflict with the optional requested items of the first request, then the first information includes the second request and the second instruction;

[0468] 3) If the first request includes optional request items, but there is no corresponding optional allowed item in the token, then the first information includes the second request;

[0469] 4) If the first request does not include optional request items and there are no corresponding optional allowed items in the token, then the first information includes the second request;

[0470] 5) If the first request does not include optional request items, but the token includes optional allowed items, then the first information includes the second request and the first instruction.

[0471] For example, if the token's optional permission item is an indication to allow terminal a to be associated with the sensing result, and the optional request item is a request to associate terminal b with the sensing result, since terminal a and terminal b are two different terminals, the optional permission item and the optional request item conflict. Conversely, if the token's optional permission item is an indication to allow terminal a to be associated with the sensing result, and the optional request item is a request to associate terminal a with the sensing result, the terminal to be associated and the terminal to be associated are the same terminal, so the optional permission item and the optional request item do not conflict.

[0472] For example, if the first request includes a request to associate terminal a with the sensing result, but the token does not contain an indication that any terminal is allowed to associate with the sensing result, it is considered that there is no corresponding optional allowed item in the token, so the first information only includes the second request.

[0473] For example, if the first request does not include a request to associate any terminal with the sensing result, but the token includes an indication that terminal a is allowed to associate with the sensing result, then the first information may include a second request and a first indication, the first indication being used to indicate the indication that terminal a is allowed to associate with the sensing result, that is, to remain consistent with the token.

[0474] The second request in this embodiment is used to request a sensing service. Compared with the first request in the above embodiment, the difference is that the second request does not contain a token. However, it should be noted that the items requested in the second request are consistent with the items requested in the first request. For example, the first request includes three items: the identifier of the requested sensing target, the identifier of the owner of the requested sensing target, the identifier of the first terminal, and the sensing role to be assumed by the first terminal. The second request also includes the above three items.

[0475] The first instruction in this embodiment of the disclosure is used to indicate at least one of the following:

[0476] It is permissible to associate the identifier of a second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0477] Allow open awareness of contextual information.

[0478] The second instruction in this embodiment of the disclosure is used to indicate at least one of the following:

[0479] Refuse to associate the identifier of the second terminal with the perception result;

[0480] Refuse to disclose contextual information.

[0481] It should be noted that when the first information is a second request and a first instruction, the first information sent to the first network function entity is as follows:

[0482] Simultaneously send the second request and the first instruction to the first network function entity; or

[0483] The first network functional entity sends the second request and the first instruction in sequence.

[0484] In other words, when a network open function entity sends a second request and a first instruction to a first network function entity, they can be sent simultaneously or in two separate transactions. This embodiment of the present disclosure does not limit the order in which the second request and the first instruction are sent; the second request can be sent first, or the first instruction can be sent first.

[0485] When the first information is a second request and a second instruction, the first information is sent to the first network function entity as follows:

[0486] Simultaneously send a second request and a second instruction to the first network function entity; or

[0487] The second request and the second instruction are sent to the first network functional entity in sequence.

[0488] Similar to the above embodiments, when the network open function entity sends the second request and the second instruction to the first network function entity, they can be sent simultaneously or in two separate transactions. This disclosure does not limit the order in which the second request and the second instruction are sent; the second request can be sent first or the second instruction can be sent first.

[0489] The first network functional entity in this disclosure embodiment is at least one of the following types of enforcement points:

[0490] 1) Select the enforcement point for at least one of the sensing receiver and the sensing sender;

[0491] 2) Determine whether to authorize the enforcement point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role;

[0492] 3) Determine whether to authorize the mandatory execution point that is aware of context information.

[0493] S2103, The first network function entity determines whether to authorize the second request.

[0494] In some embodiments, if the first network function entity is a mandatory point for determining whether to authorize the association of the identifier of the second terminal with the perception result, and the first indication is used to allow the association of the identifier of the second terminal with the perception result, then the first network function entity triggers the association of the identifier of the second terminal with the perception result.

[0495] In some embodiments, triggering the association between the identifier of the second terminal and the perception result can mean triggering the association between the identifier of the second terminal and the perception result without triggering the authorization process for associating the identifier of the second terminal and the perception result.

[0496] In some embodiments, if the first network function entity is the execution point for determining whether to authorize open-aware context information, and the first indication is used to allow open-aware context information, then the first network function entity triggers open-aware context information.

[0497] In some embodiments, the first network functional entity triggers open awareness context information, which may be done without triggering the authorization process for opening awareness context information.

[0498] In some embodiments, if the first instruction is used to allow the association of the identifier of the second terminal with the perception result, then the first network function entity triggers the association of the identifier of the second terminal with the perception result.

[0499] In some embodiments, triggering the association between the identifier of the second terminal and the perception result can mean triggering the association between the identifier of the second terminal and the perception result without triggering the authorization process for associating the identifier of the second terminal and the perception result.

[0500] In some embodiments, if the first indication is used to allow Open Aware Context Information, then the first network functional entity triggers the Open Aware Context Information.

[0501] In some embodiments, the first network functional entity triggers open awareness context information, which may be done without triggering the authorization process for opening awareness context information.

[0502] It should be noted that since the first network function entity can serve as a type of enforcement point, it can trigger corresponding steps based on the first instruction for each type of enforcement point it serves as. Taking the above embodiment as an example, if the first network function entity serves as both an enforcement point for determining whether to authorize the association of the second terminal's identifier with the perception result and an execution point for determining whether to authorize the opening of the perception context information, and the first instruction is used to instruct the association of the second terminal's identifier with the perception result and the association of the second terminal's identifier with the perception result, then the first network function entity needs to trigger the association of the second terminal's identifier with the perception result on the one hand, and trigger the opening of the perception context information on the other hand.

[0503] In some embodiments, the first network function entity is a mandatory point for determining whether to authorize the association of the identifier of the second terminal with the perception result; the first information includes a second indication, which is used to indicate that the association of the identifier of the second terminal with the perception result is refused, and the first network function entity refuses to associate the identifier of the second terminal with the perception result.

[0504] In some embodiments, if the second indication is used to indicate that the identifier of the second terminal is refused to be associated with the perception result, then the first network function entity refuses to associate the identifier of the second terminal with the perception result.

[0505] In some embodiments, the first network function entity is a mandatory execution point for determining whether to authorize the association of the identifier of the second terminal with the perception result; when the first information only contains the second request and not the first instruction or the second instruction, the first network function entity can also trigger the authorization process of associating the identifier of the second terminal with the perception result, and after the authorization process is completed, trigger the association of the identifier of the second terminal with the perception result.

[0506] In some embodiments, when the first information contains only the second request and no first or second instruction, the first network function entity may also trigger an authorization process to associate the identifier of the second terminal with the perception result. After the authorization process is completed, the identifier of the second terminal is associated with the perception result.

[0507] In some embodiments, the first network function entity is the enforcement point for determining whether to authorize the opening of the awareness context information. The first information includes a second indication, which is used to indicate that the opening of the awareness context information is denied. The method further includes: not opening the awareness context information.

[0508] In some embodiments, the first information includes a second indication for indicating that the perceptual context information is refused to be opened, and the method further includes: not opening the perceptual context information.

[0509] In some embodiments, the first network function entity is the enforcement point for determining whether to authorize open-aware context information; when the first information only contains the second request and not the first or second instruction, the first network function entity can also trigger the authorization process of open-aware context information, and after obtaining authorization of open-aware context information, open-aware context information.

[0510] In some embodiments, when the first information contains only the second request and no first instruction or second instruction, the first network function entity may also trigger the authorization process of the Open Aware Context Information. After obtaining the authorization of the Open Aware Context Information, the Open Aware Context Information is opened.

[0511] In some embodiments, if the second request includes the identifier of the first terminal and the sensing role requested to be assumed by the first terminal, and the first network function entity is the enforcement point for selecting the sensing receiver and sensing sender, then the first network function entity determines that the first terminal assumes the sensing role based on the identifier of the first terminal and the role requested to be assumed by the first terminal in the second request. For example, if the second request includes a request for terminal a to assume the sensing sender, after receiving the second request, the first network function entity determines that terminal a assumes the sensing sender.

[0512] In some embodiments, if the second request includes an identifier of the first terminal and a sensing role requested from the first terminal, then the first network function entity determines the sensing role assumed by the first terminal based on the identifier of the first terminal and the role requested from the first terminal in the second request. For example, if the second request includes a request for terminal a to assume the role of a sensing sender, the first network function entity determines that terminal a assumes the role of a sensing sender after receiving the second request.

[0513] In some embodiments, if a first network function entity determines that further authorization is required from a second network function entity, the first network function entity may send first information to the second network function entity. It should be understood that the first information sent by the first network function entity to the second network function entity is the same as the first information received by the first network function entity from the network open function entity.

[0514] In some embodiments, the second network function entity may be a functional entity developed for sensing services, such as an Authentication Management Function (AMF), a Network Data Analytics Function (NWDAF), a Gateway Mobile Location Center (GMLC), a Location Management Function (LMF), or a Sensing Function.

[0515] It should be noted that steps S2101, S2102, and S2103 of the present disclosure embodiments can be implemented individually or in any order and combination without contradiction.

[0516] Figure 2B is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure. As shown in Figure 2B, this embodiment of the present disclosure relates to a sensing method for a communication system 100, the method comprising:

[0517] S2201, The second entity sends a first request to the first network function entity.

[0518] In some embodiments, the first network function entity may be a functional entity that is open to sensing services, such as an authentication management function (AMF), a network data analytics function (NWDAF), a gateway mobile location center (GMLC), a location management function (LMF), or a sensing function.

[0519] In some embodiments, the type of the second entity is a trusted application function (AF), a trusted terminal, or a trusted sensing client. In some embodiments, if the default terminal is trusted, then the type of the first entity can be a terminal. In some embodiments, if the default sensing client is trusted, then the type of the first entity can be a sensing client.

[0520] In some embodiments, the first request includes at least one of the following:

[0521] 1) Identification of the requested perceived target;

[0522] 2) The identifier of the owner of the requested perceived target;

[0523] 3) The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0524] 4) The requested sensing area;

[0525] 5) The time it takes to perceive the request;

[0526] 6) A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0527] 7) Requests to open contextual information.

[0528] It should be noted that the type of sensing target in this embodiment of the disclosure can be a terminal, a building, plants or animals, etc., and this embodiment of the disclosure does not impose specific limitations. Taking a building as an example, the owner of the sensing target can be the person responsible for managing the building, such as the building's property management personnel.

[0529] The sensing area in this embodiment can be represented by the geographical coordinates of the sensing area.

[0530] The sensing time in this embodiment of the disclosure can be one or more moments or one or more time periods.

[0531] In some embodiments, the token includes at least one of the following:

[0532] 1) Identification of permitted perceived targets;

[0533] 2) The identification of the owner of the permitted target;

[0534] 3) Identification of the third terminal and the perception roles permitted to be assumed by the third terminal;

[0535] 4) Permissible sensory area;

[0536] 5) Allowable perception time;

[0537] 6) An indication that allows the identification of a fourth terminal to be associated with the perception result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted perception target, the terminal of the owner of the permitted perception target, and the terminal that assumes the perception role.

[0538] 7) Allow instructions to open the context information.

[0539] S2202, The first network function entity and the third network function entity interact to confirm the validity of the token.

[0540] In this embodiment of the disclosure, the first network function entity determines whether the token is valid by interacting with the third network function entity.

[0541] The third network function entity in this disclosure embodiment may be a network warehousing function entity or a core function of a general API open framework.

[0542] In some embodiments, a first network function entity sends a token to a third network function entity, the third network function entity determines whether the token is valid, and provides feedback to a network open function entity on whether the token is valid. The network open function entity then determines whether the token is valid based on the feedback from the third network function entity.

[0543] In some embodiments, a third network function entity sends a verification token to a first network function entity in advance. Then, when the network open function entity compares the verification token with the token in the first request, if the two match, the network open function entity determines that the token is valid.

[0544] In some embodiments, the network open function obtains the public key of a third network entity from the third network entity and uses the public key to determine whether the token is valid.

[0545] In some embodiments, the first request in this application may include only mandatory request items, or it may include optional request items in addition to mandatory request items:

[0546] Mandatory request items may include the identifier of the requested sensing target, the identifier of the owner of the requested sensing target, the identifier of the first terminal, the sensing role to be undertaken by the first terminal, the requested sensing area, the requested sensing time, etc.; optional request items may include requests to associate the identifier of the second terminal with the sensing result, requests to open sensing context information, etc.

[0547] In some embodiments, the token may include only mandatory allowed items, or it may include optional allowed items in addition to mandatory allowed items:

[0548] Mandatory permitted items may include the identifier of the permitted sensing target, the identifier of the permitted sensing target owner, the identifier of the third terminal, the permitted sensing role of the third terminal, the permitted sensing area, the permitted sensing time, etc.; optional permitted items may include instructions to associate the identifier of the fourth terminal with the sensing result, instructions to open the sensing context information, etc.

[0549] S2203, The first network functional entity processes the first request.

[0550] After determining that the token is valid, the first network function entity in this embodiment first determines whether the mandatory allowed items in the token conflict with the mandatory request items in the first request. If any mandatory request item conflicts, the first network function entity does not authorize the first request and ends the process. If all mandatory request items do not conflict, the first network function entity determines whether to authorize the first request based on the token.

[0551] The first network functional entity in this embodiment of the disclosure is at least one of the following types of execution points:

[0552] Select the enforcement point for at least one of the sensing receiver and the sensing sender;

[0553] Determine whether to authorize the execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role;

[0554] Determine whether to authorize the execution point that is aware of context information.

[0555] In some embodiments, the first network function entity is the execution point that determines whether to authorize the association of the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role; the first network function entity determines that it is allowed to associate the identifier of the second terminal with the perception result based on the token, and triggers the association of the identifier of the second terminal with the perception result.

[0556] In some embodiments, the second terminal is at least one of the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal undertaking the sensing role; the first network function entity determines, based on the token, that it is permissible to associate the identifier of the second terminal with the sensing result, and triggers the association of the identifier of the second terminal with the sensing result.

[0557] In some embodiments, the token does not include an indication that allows the identifier of the second terminal to be associated with the perception result. Triggering the association of the identifier of the second terminal with the perception result includes: triggering the association of the identifier of the second terminal with the perception result without triggering an authorization process for associating the identifier of the second terminal with the perception result.

[0558] In some embodiments, triggering the association between the identifier of the second terminal and the perception result can mean triggering the association between the identifier of the second terminal and the perception result without triggering the authorization process for associating the identifier of the second terminal and the perception result.

[0559] In some embodiments, the first network function entity is an execution point for determining whether to authorize associating the identifier of the second terminal with the sensing result. The first network function entity is further configured to determine, based on the token, that it is unacceptable to associate the identifier of the second terminal with the sensing result, and to perform any one of the following steps:

[0560] The identifier of the second terminal is not associated with the perception result;

[0561] The authorization process that associates the identifier and perception result of the second terminal is not triggered.

[0562] In some embodiments, the first network function entity is an execution point for determining whether to authorize the association of the identifier of the second terminal with the perception result; the token does not include an indication that allows the association of the identifier of the fourth terminal with the perception result, and the first network function entity is also used to trigger the authorization process of associating the identifier of the second terminal with the perception result.

[0563] In some embodiments, the token does not include an indication that allows the identifier of the fourth terminal to be associated with the sensing result, and the first network function entity is also used to trigger an authorization process for associating the identifier of the second terminal with the sensing result.

[0564] In some embodiments, the first network function entity is a point for determining whether to authorize the execution of open-aware context information; the first network function entity is also used to determine whether to allow open-aware context information based on a token.

[0565] In some embodiments, the first network function entity is further configured to determine, based on a token, an open-aware context information, which is allowed.

[0566] In some embodiments, opening the perception context information includes: opening the perception context information without triggering an authorization process that associates the identifier of the second terminal with the perception result.

[0567] In some embodiments, the first network function entity is the execution point for determining whether to authorize the opening of the awareness context information; the first network function entity is also used to determine whether to refuse to open the awareness context information and not to open the awareness context information.

[0568] In some embodiments, the first network function entity is further configured to determine whether to deny the opening of the awareness context information using a token. In some embodiments, the first network function entity is the execution point for determining whether to authorize the opening of the awareness context information; the token does not include an indication to allow the opening of the awareness context information, and the first network function entity triggers the authorization process for opening the awareness context information. In some embodiments, the first network function entity may trigger the opening of the awareness context information without triggering the authorization process for opening the awareness context information.

[0569] Based on some embodiments, if the first network function entity determines that further authorization is required from the second network function entity, the first network function entity may send first information to the second network function entity. It should be understood that the first information sent by the first network function entity to the second network function entity is the same as the first information received by the first network function entity from the network open function entity.

[0570] In some embodiments, the second network function entity may be a functional entity that is open to sensing services, such as an Authentication Management Function (AMF), a Network Data Analytics Function (NWDAF), a Gateway Mobile Location Center (GMLC), a Location Management Function (LMF), or a Sensing Function.

[0571] It should be noted that steps S2201, S2202, and S2203 of the present disclosure embodiments can be implemented individually or in any order and combination without contradiction.

[0572] Figure 2C is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure. As shown in Figure 2C, this embodiment of the present disclosure relates to a sensing method for a communication system 100, the method comprising:

[0573] S2301, The first entity sends a first request, including a token, to the network open function entity.

[0574] In some embodiments, the type of the first entity is an untrusted application function, an untrusted terminal, or an untrusted sensing client.

[0575] In some embodiments, the first request is used to request a perception service.

[0576] In some embodiments, the first request includes at least one of the following:

[0577] The identifier of the requested perceived target;

[0578] The identifier of the target owner of the requested perception;

[0579] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0580] The requested sensing area;

[0581] The perceived time of the request;

[0582] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0583] Requests to open-aware contextual information.

[0584] In some embodiments, the token includes authorization information related to the perception service.

[0585] In some embodiments, the token includes at least one of the following:

[0586] The identification of permitted perceived targets;

[0587] The identifier of the owner of the permitted perception target;

[0588] The identifier of the third terminal and the perception roles that the third terminal is allowed to assume;

[0589] Permissible sensory area;

[0590] Permissible perception time;

[0591] An indication that allows the identification of a fourth terminal to be associated with the sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role;

[0592] Instructions that allow open awareness of contextual information.

[0593] S2302, First Authentication Request.

[0594] In some embodiments, the network open function entity verifies the token and verifies the token authentication first request.

[0595] In some embodiments, a network open function entity sends a token to a third network function entity, and the third network function entity sends third information to a first network function entity; the third information is feedback information indicating that the token is a valid token, or public key used to verify the token.

[0596] In some embodiments, the number of network functional entities related to sensing can be one or more. Taking Figure 2C as an example, Figure 2C includes a first network functional entity and a second network functional entity. The first network functional entity and the second network functional entity can be functional entities developed for sensing services, such as AMF, NWDAF, GMLC, LMF, and SF.

[0597] In some embodiments, the second request is used to request a perception service.

[0598] In some embodiments, the second request includes at least one of the following:

[0599] The identifier of the requested perceived target;

[0600] The identifier of the target owner of the requested perception;

[0601] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0602] The requested sensing area;

[0603] The perceived time of the request;

[0604] A request to associate the identifier of the second terminal with the perception result;

[0605] Requests to open-aware contextual information.

[0606] In some embodiments, the indication may be a first indication or a second indication, wherein:

[0607] The first instruction is used to instruct at least one of the following:

[0608] Allows the association of the identifier of the second terminal with the sensing results;

[0609] Allow open awareness of contextual information.

[0610] The second instruction is used to instruct at least one of the following:

[0611] Refuse to associate the identifier of the second terminal with the perception result;

[0612] Refuse to disclose contextual information.

[0613] In some embodiments, the first network function entity is at least one of the following types of enforcement points:

[0614] Select the enforcement point for at least one of the sensing receiver and the sensing sender;

[0615] Determine whether to authorize the mandatory execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role;

[0616] Determine whether to authorize the mandatory execution point that is aware of context information.

[0617] In some embodiments, when the first network function entity is a mandatory execution point for determining whether to authorize the association of the identifier of the second terminal with the perception result, the first network function entity may execute the authorization interaction process in the following ways, depending on the type of the received first information:

[0618] Method 1) The first information is a second request and a first instruction. The first instruction is used to indicate that the identifier of the second terminal is allowed to be associated with the perception result. The first network function entity triggers the association of the identifier of the second terminal with the perception result.

[0619] Method 2) The first information is the second request and the second instruction. The second instruction is used to indicate that the identifier of the second terminal is refused to be associated with the perception result. The first network function entity refuses to associate the identifier of the second terminal with the perception result.

[0620] Method 3) The first information is the second request. The first network function entity triggers the authorization process of associating the identifier of the second terminal with the perception result. After the authorization process is completed, the identifier of the second terminal is associated with the perception result.

[0621] In some embodiments, the first network function entity triggers the association of the identifier of the second terminal with the perception result, which may be done without triggering the authorization process for the association of the identifier of the second terminal with the perception result.

[0622] In some embodiments, when the first network function entity is a mandatory execution point for determining whether to authorize open-aware context information, the first network function entity may execute the authorization interaction process in the following ways, depending on the type of the first information received:

[0623] Method 1) The first information is the second request and the first instruction. The first instruction is used to indicate that open awareness context information is allowed. The first network functional entity triggers the open awareness context information.

[0624] Method 2) The first information is the second request and the second instruction. The second instruction is used to indicate that the perception context information is refused to be opened, and the first network functional entity does not open the perception context information.

[0625] Method 3) The first information is the second request. The first network functional entity triggers the authorization process of the open sensing context information. After obtaining the authorization of the open sensing context information, the open sensing context information is opened.

[0626] In some embodiments, the first network functional entity triggers open awareness context information, which may be done without triggering the authorization process for opening awareness context information.

[0627] In some embodiments, when the first network function entity is at the mandatory execution point for selecting the sensing receiver and the sensing sender, the first network function entity may execute the authorization interaction process in the following ways, depending on the type of the received first information:

[0628] Method 1) The first information is the second request, which includes the identifier of the first terminal and the perception role requested to be assumed by the first terminal. The first network function entity determines the perception role to be assumed by the first terminal based on the identifier of the first terminal and the role requested to be assumed by the first terminal in the second request.

[0629] Method 2) The first information is the second request. The second request does not include the identifier of the first terminal or the sensing role requested by the first terminal. The first network function entity triggers the discovery process of the sensing sender or sensing receiver to determine the sensing sender and sensing receiver.

[0630] S2303a, The network open function entity simultaneously sends a second request and instruction to the network function entity related to the sensing service.

[0631] S2303b-1, The Network Open Functions Entity sends a second request to the Network Functions Entity related to the Sensing Service;

[0632] S2303b-2, The Network Open Functions Entity sends instructions to the Network Functions Entities related to the Sensing Service.

[0633] It should be noted that when a network open function entity sends a second request and instruction to a network function entity related to the sensing service, the network function entity related to the sensing service may return corresponding response information.

[0634] If the second network function entity needs to further execute the authorization interaction process, the first network function entity sends a second request and instruction to the second network function entity.

[0635] It should be noted that when the network open function entity in this embodiment sends the second request and instruction to the network function entity related to the perception service, it can send them simultaneously, as in step S2303a, or send them separately, as in steps S2303b-1 and S2303b-2. When sending them separately, this embodiment does not specifically limit the order of sending the second request and instruction. For example, the instruction can be sent first, followed by the second request.

[0636] S2304, Authorization Interaction.

[0637] The method by which the second network function entity executes the authorization interaction process can refer to the method by which the first network function entity executes the authorization interaction process described above, and will not be repeated in this embodiment.

[0638] S2305, Initiate the sensing process involving the terminal.

[0639] In some embodiments, step S2304 may also be performed after step S2305.

[0640] In some embodiments, if step S2304 is performed by the first network function entity and the second network function entity, then in step S2305, the second network function entity also needs to initiate the sensing process.

[0641] It should be noted that steps S2301, S2302, S2303, S2304 and S2305 of the embodiments of this disclosure can be implemented individually or in any order and combination without contradiction.

[0642] Figure 2D is an interactive schematic diagram of a sensing method according to an embodiment of the present disclosure. As shown in Figure 2D, this embodiment of the present disclosure relates to a sensing method for a communication system 100, the method comprising:

[0643] S2401, The second entity sends a first request, including a token, to the first network function entity.

[0644] In some embodiments, the second entity is of the type of a trusted application function entity, a trusted terminal, or a trusted sensing client.

[0645] In some embodiments, the first network functional entity may be a functional entity developed for sensing services, such as AMF, NWDAF, GMLC, LMF, SF, etc.

[0646] In some embodiments, the first request is used to request a perception service.

[0647] In some embodiments, the token includes authorization information related to the perception service.

[0648] In some embodiments, the first request includes at least one of the following:

[0649] The identifier of the requested perceived target;

[0650] The identifier of the target owner of the requested perception;

[0651] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0652] The requested sensing area;

[0653] The perceived time of the request;

[0654] A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role.

[0655] Requests to open-aware contextual information.

[0656] In some embodiments, the token includes at least one of the following:

[0657] The identification of permitted perceived targets;

[0658] The identifier of the owner of the permitted perception target;

[0659] The identifier of the third terminal and the perception roles that the third terminal is allowed to assume;

[0660] Permissible sensory area;

[0661] Permissible perception time;

[0662] An indication that allows the identification of a fourth terminal to be associated with the sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role;

[0663] Instructions that allow open awareness of contextual information.

[0664] S2402, The first network function entity interacts with the third network function entity to authenticate the first request.

[0665] In some embodiments, the network open function entity verifies the token and verifies the token authentication first request.

[0666] In some embodiments, a network open function entity sends a token to a third network function entity, and the third network function entity sends third information to a first network function entity; the third information is feedback information indicating that the token is a valid token, or public key used to verify the token.

[0667] In some embodiments, the first network function entity is at least one of the following types of enforcement points:

[0668] Select the enforcement point for at least one of the sensing receiver and the sensing sender;

[0669] Determine whether to authorize the execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role;

[0670] Determine whether to authorize the execution point that is aware of context information.

[0671] The first network functional entity will authorize based on its own enforcement point.

[0672] When the first network function entity is the execution point for determining whether to authorize the association of the identifier of the second terminal with the sensing result, and the second terminal is at least one of the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal undertaking the sensing role, and the token is determined to be a valid token, the first network function entity performs the following authorization:

[0673] 1) Based on the token, it is determined that the association between the identifier of the second terminal and the sensing result is permitted, and the association between the identifier of the second terminal and the sensing result is triggered. Further, if the token does not include an indication that the identifier of the fourth terminal is permitted to be associated with the sensing result, the first network function entity or the second network function entity may trigger the association between the identifier of the second terminal and the sensing result without triggering an authorization process for the association between the identifier of the second terminal and the sensing result.

[0674] 2) If the token determines that the association between the identifier of the second terminal and the perception result is refused, then the authorization process of associating the identifier of the second terminal with the perception result or the association between the identifier of the second terminal and the perception result will not be triggered.

[0675] 3) The token does not include an indication that allows the fourth terminal's identifier to be associated with the sensing result, triggering the authorization process of associating the second terminal's identifier with the sensing result.

[0676] When the first network function entity determines whether to authorize the execution point of open-aware context information and determines that the token is a valid token, the first network function entity or the second network function entity performs the following authorization:

[0677] 1) Determine whether to allow access to the perception context information based on the token.

[0678] In some embodiments, opening the perception context information can be done without triggering an authorization process that associates the identifier of the second terminal with the perception result.

[0679] 2) Based on the token, determine whether to refuse to open the perception context information, and not to open the perception context information.

[0680] 3) The token does not include an indication that allows open awareness context information, triggering the authorization process for open awareness context information.

[0681] S2403a, The first network function entity simultaneously sends a second request and instruction to the second network function entity.

[0682] S2403b-1, The first network function entity sends a second request to the second network function entity;

[0683] S2403b-2, The first network function entity sends a second request and instruction to the second network function entity.

[0684] It should be noted that when the first network function entity sends a second request and instruction to the second network function entity, the second network function entity may return corresponding response information.

[0685] It should be noted that if the embodiments of this disclosure require further authorization from the second network function entity, the first network function entity sends a second request and instruction to the second network function entity.

[0686] When the first network function entity in this embodiment sends the second request and instruction to the second network function entity, it can send them simultaneously, as in step S2403a, or send them separately, as in steps S2403b-1 and S2403b-2. When sending them separately, this embodiment does not specifically limit the order of sending the second request and instruction. For example, the instruction can be sent first, followed by the second request.

[0687] In some embodiments, the second request is used to request a perception service.

[0688] In some embodiments, the second request includes at least one of the following:

[0689] The identifier of the requested perceived target;

[0690] The identifier of the target owner of the requested perception;

[0691] The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender.

[0692] The requested sensing area;

[0693] The perceived time of the request;

[0694] A request to associate the identifier of the second terminal with the perception result;

[0695] Requests to open-aware contextual information.

[0696] In some embodiments, the indication may be a first indication or a second indication, wherein:

[0697] The first instruction is used to instruct at least one of the following:

[0698] Allows the association of the identifier of the second terminal with the sensing results;

[0699] Allow open awareness of contextual information.

[0700] The second instruction is used to instruct at least one of the following:

[0701] Refuse to associate the identifier of the second terminal with the perception result;

[0702] Refuse to disclose contextual information.

[0703] S2404, Initiate the sensing process involving the terminal.

[0704] In some embodiments, step S2404 may also be performed after step S2403.

[0705] In some embodiments, if step S2404 is performed by the first network function entity and the second network function entity, then in step S2404, the second network function entity also needs to initiate the perception-related process.

[0706] It should be noted that steps S2401, S2402, S2403, and S2404 of the embodiments of this disclosure can be implemented individually or in any order and combination without contradiction.

[0707] Figure 3 is a flowchart illustrating a sensing method according to an embodiment of the present disclosure. As shown in Figure 3, the method is executed by a first entity and includes:

[0708] S3101, Send the first request.

[0709] In some embodiments, a first network open function entity receives a first request.

[0710] In some embodiments, the first request is used to request a perception service.

[0711] In some embodiments, the first request includes a token, which includes authorization information related to the perception service.

[0712] The optional implementation of step S3101 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0713] Figure 4 is a flowchart illustrating a sensing method according to an embodiment of the present disclosure. As shown in Figure 4, the method is executed by a second entity in this embodiment and includes:

[0714] S4101, send the first request.

[0715] In some embodiments, a first network function entity receives a first request.

[0716] In some embodiments, the first request is used to request a perception service.

[0717] In some embodiments, the first request includes a token, which includes authorization information related to the perception service.

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

[0719] Figure 5 is a flowchart illustrating a sensing method according to an embodiment of the present disclosure. As shown in Figure 5, the method is executed by a network open function entity and includes:

[0720] S5101, Receive the first request.

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

[0722] S5102, Send the first message.

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

[0724] The sensing method involved in the embodiments of this disclosure may include at least one of steps S5101 to S5102. For example, step S5101 may be implemented as a separate embodiment, and step S5102 may be implemented as a separate embodiment, but is not limited thereto.

[0725] In some embodiments, step S5101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0726] In some embodiments, step S5102 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0727] It should be noted that the order of S5101 and S5102 in this embodiment can be arbitrarily changed and freely combined without contradiction.

[0728] Figure 6A is a flowchart illustrating a sensing method according to an embodiment of the present disclosure. As shown in Figure 6A, the method is executed by a first network functional entity and includes:

[0729] S6101, Receive the first information.

[0730] The optional implementation of step S6101 can be referred to the optional implementation of step S2102 in Figure 2A, as well as other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0731] S6102. Determine whether to authorize the second request.

[0732] The optional implementation of step S6102 can be referred to the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0733] The sensing method involved in the embodiments of this disclosure may include at least one of steps S6101 to S6102. For example, step S6101 may be implemented as a separate embodiment, and step S6102 may be implemented as a separate embodiment, but is not limited thereto.

[0734] In some embodiments, step S6101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0735] In some embodiments, step S6102 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0736] It should be noted that the order of S6101 and S6102 in this embodiment can be arbitrarily changed and freely combined without contradiction.

[0737] Figure 6B is a flowchart illustrating a sensing method according to an embodiment of the present disclosure. As shown in Figure 6B, the method is executed by a first network functional entity and includes:

[0738] S6201, Receive the first request.

[0739] The optional implementation of step S6201 can be found in the optional implementation of step S2201 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0740] S6202, The first network function entity and the third network function entity interact to confirm the validity of the token.

[0741] The optional implementation of step S6202 can be referred to the optional implementation of step S2202 in Figure 2B, and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0742] S6203. Determine whether to authorize the first request.

[0743] The optional implementation of step S6203 can be referred to the optional implementation of step S2203 in Figure 2B, and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0744] The sensing method involved in the embodiments of this disclosure may include at least one of steps S6201 to S6203. For example, step S3201 may be implemented as a separate embodiment, step S6202 may be implemented as a separate embodiment, and step S6203 may be implemented as a separate embodiment, but is not limited thereto.

[0745] In some embodiments, step S6201 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0746] In some embodiments, step S6202 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0747] In some embodiments, step S6203 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0748] It should be noted that the order of S6201, S6202 and S6203 in the embodiments of this disclosure can be arbitrarily changed and freely combined without contradiction.

[0749] Figure 7A is a flowchart illustrating a sensing method according to an embodiment of the present disclosure. As shown in Figure 7A, the method is executed by a communication system and includes:

[0750] S7101, The first entity sends a first request to the network open function entity.

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

[0752] S7102, The network open function entity sends the first information to the first network function entity.

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

[0754] S7103, The first network function entity determines whether to authorize the second request.

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

[0756] The sensing method involved in the embodiments of this disclosure may include at least one of steps S7101 to S7103. For example, step S3201 may be implemented as a separate embodiment, step S7102 may be implemented as a separate embodiment, and step S7103 may be implemented as a separate embodiment, but is not limited thereto.

[0757] In some embodiments, step S7101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0758] In some embodiments, step S7102 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0759] In some embodiments, step S7103 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0760] It should be noted that the order of S7101, S7102 and S7103 in the embodiments of this disclosure can be arbitrarily changed and freely combined without contradiction.

[0761] Figure 7B is a flowchart illustrating a sensing method according to an embodiment of the present disclosure. As shown in Figure 7B, the method is executed by a communication system and includes:

[0762] S7201, The second entity sends a first request to the first network function entity.

[0763] The optional implementation of step S7201 can be found in the optional implementation of step S2201 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0764] S7202, The first network function entity and the third network function entity interact to confirm the validity of the token.

[0765] The optional implementation of step S7202 can be referred to the optional implementation of step S2202 in Figure 2B, and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0766] S7203, The first network function entity processes the first request.

[0767] The optional implementation of step S7203 can be referred to the optional implementation of step S2203 in Figure 2B, and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

[0768] The sensing method involved in the embodiments of this disclosure may include at least one of steps S7201 to S7203. For example, step S3201 may be implemented as a separate embodiment, step S7202 may be implemented as a separate embodiment, and step S7203 may be implemented as a separate embodiment, but is not limited thereto.

[0769] In some embodiments, step S7201 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0770] In some embodiments, step S7202 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0771] In some embodiments, step S7203 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0772] It should be noted that the order of S7201, S7202 and S7203 in the embodiments of this disclosure can be arbitrarily changed and freely combined without contradiction.

[0773] This disclosure also provides apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the first network element 1031 in any of the above methods. Another apparatus is provided that includes units or modules for implementing the steps performed by the second network element 1032 in any of the above methods. Yet another apparatus is provided that includes units or modules for implementing the steps performed by the third network element 1033 in any of the above methods.

[0774] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0775] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute 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 relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using 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 configuring the hardware circuit 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. Furthermore, 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), or a Deep Learning Processing Unit (DPU).

[0776] Figure 8A is a structural schematic diagram of the first entity proposed in an embodiment of this disclosure. As shown in Figure 8A, the first entity may include: a transceiver module 8011.

[0777] In some embodiments, the transceiver module 8011 is configured to send a first request to a first network function entity;

[0778] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0779] Figure 8B is a structural schematic diagram of the second entity proposed in an embodiment of this disclosure. As shown in Figure 8B, the second entity may include: a transceiver module 8021.

[0780] In some embodiments, the transceiver module 8021 is configured to send a first request to a first network function entity;

[0781] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0782] Figure 8C is a schematic diagram of the structure of the Network Open Functions entity proposed in an embodiment of this disclosure. As shown in Figure 8C, the Network Open Functions entity may include: a transceiver module 8031.

[0783] In some embodiments, the transceiver module 8031 ​​is configured to receive a first request sent by a first entity;

[0784] The first request is used to request the perception service. The first request includes a token, which includes perception-related authorization information.

[0785] Figure 8D is a schematic diagram of the structure of the first network functional entity proposed in an embodiment of this disclosure. As shown in Figure 8D, the first network functional entity may include: a transceiver module 8041.

[0786] In some embodiments, the transceiver module 8041 is configured to receive first information sent by the Network Open Functions entity;

[0787] The first information includes the second request, which is used to request the perception service.

[0788] Figure 8E is a schematic diagram of the structure of the first network functional entity proposed in an embodiment of this disclosure. As shown in Figure 8E, the first network functional entity may include: a transceiver module 8051.

[0789] In some embodiments, the transceiver module 8051 is configured to receive a first request sent by the Network Open Functions entity;

[0790] The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

[0791] Figure 8F is a structural schematic diagram of the third network functional entity proposed in an embodiment of this disclosure. As shown in Figure 8F, the third network functional entity may include: a transceiver module 8061.

[0792] In some embodiments, the transceiver module 8061 is used to send third information to the first network function entity;

[0793] The third piece of information is either feedback that the token is valid or a public key used to verify the token.

[0794] Figure 9A is a schematic diagram of the structure of the communication device 8100 proposed in an embodiment of this disclosure. The communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), an Internet of Things (IoT) device, a chip, chip system, or processor that supports network devices in implementing any of the above methods, or a chip, chip system, or processor that supports IoT devices in implementing any of the above methods. The communication device 8100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0795] As shown in Figure 9A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 8100 can be used to execute any of the above methods. Optionally, one or more processors 8101 can be used to invoke instructions to cause the communication device 8100 to execute any of the above methods.

[0796] 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 (e.g., step S2101, but not limited thereto) in the above method, such as sending and / or receiving, while the processor 8101 performs at least one of other steps (e.g., step S2102, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

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

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

[0799] Figure 9B is a schematic diagram of the structure of the chip 8200 according to an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the chip 8200 shown in Figure 9B, but it is not limited thereto.

[0800] Chip 8200 includes one or more processors 8201. Chip 8200 is used to perform any of the methods described above.

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

[0802] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2101, but not limited thereto). For example, the interface circuit 8202 performing the communication steps such as sending and / or receiving in the above method means that the interface circuit 8202 performs data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of other steps (e.g., step S2102, but not limited thereto).

[0803] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 8100, cause the communication device 8100 to perform 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 not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0804] This disclosure also provides a program product that, when executed by the communication device 8100, causes the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0805] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A sensing method, characterized in that, Performed by a first entity, the method includes: Send the first request to the network open functionality entity; The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

2. The method according to claim 1, characterized in that, The first entity is of any of the following types: Unreliable application functions; Untrusted terminals; Untrusted perception client.

3. The method according to claim 1 or 2, characterized in that, The first request includes at least one of the following: The identifier of the requested perceived target; The identifier of the target owner of the requested perception; The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender. The requested sensing area; The perceived time of the request; A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. Requests to open-aware contextual information.

4. The method according to any one of claims 1-3, characterized in that, The token includes at least one of the following: The identification of permitted perceived targets; The identifier of the owner of the permitted perceived target; The identifier of the third terminal and the perception role that the third terminal is allowed to assume; Permissible sensory area; Permissible perception time; An indication that allows the identification of a fourth terminal to be associated with a sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role; Instructions that allow open awareness of contextual information.

5. A sensing method, characterized in that, Performed by a second entity, the method includes: Send the first request to the first network function entity; The first request is used to request a perception service, and the first request includes a token, which includes perception-related authorization information.

6. The method according to claim 5, characterized in that, The type of the second entity is any one of the following: Trusted application functional entities; A trusted terminal; A trustworthy perception client.

7. The method according to claim 5 or 6, characterized in that, The first request includes at least one of the following: The identifier of the requested perceived target; The identifier of the target owner of the requested perception; The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender. The requested sensing area; The perceived time of the request; A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. Requests to open-aware contextual information.

8. The method according to any one of claims 5-7, characterized in that, The token includes at least one of the following: The identification of permitted perceived targets; The identifier of the owner of the permitted perception target; The identifier of the third terminal and the perception role that the third terminal is allowed to assume; Permissible sensory area; Permissible perception time; An indication that allows the identification of a fourth terminal to be associated with a sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role; Instructions that allow open awareness of contextual information.

9. A sensing method, performed by a network open function entity, the method comprising: Receive the first request sent by the first entity; The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

10. The method according to claim 9, characterized in that, The first entity is of any of the following types: Unreliable application functions; Untrusted terminals; Untrusted perception client.

11. The method according to claim 9 or 10, characterized in that, The first request includes at least one of the following: The identifier of the requested perceived target; The identifier of the target owner of the requested perception; The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender. The requested sensing area; The perceived time of the request; A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. Requests to open-aware contextual information.

12. The method according to any one of claims 9-11, characterized in that, The token includes at least one of the following: The identification of permitted perceived targets; The identifier of the owner of the permitted perception target; The identifier of the third terminal and the perception role that the third terminal is allowed to assume; Permissible sensory area; Permissible perception time; An indication that allows the identification of a fourth terminal to be associated with a sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role; Instructions that allow open awareness of contextual information.

13. The method according to any one of claims 9-12, characterized in that, It also includes at least one of the following: Send the first message to the first network function entity; The first piece of information is any one of the following: The second request is used to request the perception service; The second request and the first instruction; The second request and the second instruction; The first indication is used to indicate at least one of the following: It is permissible to associate the identifier of a second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role; Allows for open perception of contextual information; The second instruction is used to indicate at least one of the following: The identifier of the second terminal is not associated with the perception result; Refuse to disclose contextual information.

14. The method according to claim 13, characterized in that, The step of sending the first information to the first network functional entity further includes: The token has been determined to be a valid token.

15. The method according to claim 13 or 14, characterized in that, The second request includes at least one of the following: The identifier of the requested perceived target; The identifier of the target owner of the requested perception; The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender. The requested sensing area; The perceived time of the request; A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. Requests to open-aware contextual information.

16. The method according to any one of claims 13-15, characterized in that, The first information is the second request and the first instruction, and sending the first information to the first network function entity is: Simultaneously send the second request and the first instruction to the first network function entity; or The second request and the first instruction are sent sequentially to the first network function entity. The first information is the second request and the second instruction, and sending the first information to the first network function entity is: Simultaneously send the second request and the second instruction to the first network function entity; or The second request and the second instruction are sent sequentially to the first network function entity.

17. The method according to any one of claims 13-16, characterized in that, The first network functional entity is at least one of the following types of enforcement points: Select the enforcement point for at least one of the sensing receiver and the sensing sender; Determine whether to authorize the enforcement point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role; Determine whether to authorize the mandatory execution point that is aware of context information.

18. A sensing method, performed by a first network functional entity, the method comprising: Receive the first message sent by the network open function entity; The first information includes a second request, which is used to request a perception service.

19. The method according to claim 18, characterized in that, The second request includes at least one of the following: The identifier of the requested perceived target; The identifier of the target owner of the requested perception; The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender. The requested sensing area; The perceived time of the request; A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. Requests to open-aware contextual information.

20. The method according to claim 18 or 19, characterized in that, The first network functional entity is at least one of the following types of enforcement points: Select the enforcement point for at least one of the sensing receiver and the sensing sender; Determine whether to authorize the mandatory execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role; Determine whether to authorize the mandatory execution point that is aware of context information.

21. The method according to any one of claims 18-20, characterized in that, The first information also includes a first instruction; Wherein, the first indication is used to indicate at least one of the following: It is permissible to associate the identifier of a second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role; Allow open awareness of contextual information.

22. The method according to claim 21, characterized in that, The first network functional entity is a mandatory execution point for determining whether to authorize the association of the second terminal's identifier with the perception result; The first indication is used to indicate that the identifier of the second terminal can be associated with the perception result; The method further includes: The identifier of the second terminal is linked to the perception result.

23. The method according to claim 22, characterized in that, The association between the identifier that triggers the second terminal and the perception result includes: Without triggering the authorization process of associating the identifier of the second terminal with the perception result, the association between the identifier of the second terminal and the perception result is triggered.

24. The method according to claim 21, characterized in that, The first network functional entity is the mandatory execution point for determining whether to authorize the opening of the awareness context information; The first indication is used to indicate that open awareness context information is allowed; The method further includes: Trigger open-aware context information.

25. The method according to claim 24, characterized in that, The triggering open-aware context information includes: Trigger the opening of the perception context information without triggering the authorization process for opening the perception context information.

26. The method according to any one of claims 18-20, characterized in that, The first network functional entity is a mandatory execution point for determining whether to authorize the association of the second terminal's identifier with the perception result; The first information includes a second indication, which is used to indicate that the identifier of the second terminal is refused to be associated with the perception result; The method further includes: The identifier of the second terminal is not associated with the perception result; The second terminal is at least one of the following: the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal that assumes the sensing role.

27. The method according to any one of claims 18-20, characterized in that, The first network functional entity is a mandatory execution point for determining whether to authorize the association of the second terminal's identifier with the perception result; The method further includes: The authorization process of associating the identifier of the second terminal with the perception result is triggered. After the authorization process is completed, the identifier of the second terminal is associated with the perception result.

28. The method according to any one of claims 18-20, characterized in that, The first network functional entity is the mandatory execution point for determining whether to authorize the opening of the awareness context information; The first information includes a second indication, which is used to indicate that the access to the perceived context information is refused; The method further includes: Contextual information is not disclosed.

29. The method according to any one of claims 18-20, characterized in that, The first network functional entity is the mandatory execution point for determining whether to authorize the opening of the awareness context information; The method further includes: Trigger the authorization process for OpenSense context information, and after obtaining authorization for OpenSense context information, openSense context information.

30. The method according to any one of claims 18-29, characterized in that, The second request includes the identifier of the first terminal and the perception role requested to be assumed by the first terminal; The first network functional entity is the enforcement point for selecting the sensing receiver and the sensing sender; The method further includes: Based on the identifier of the first terminal in the second request and the role requested to be assumed by the first terminal, the first terminal is determined to assume the perception role.

31. The method according to any one of claims 18-30, characterized in that, The second request does not include the identifier of the first terminal or the perception role requested to be assumed by the first terminal; The first network functional entity is the enforcement point for selecting the sensing receiver and the sensing sender; The method further includes: Trigger the discovery process of the sensing sender or sensing receiver to identify the sensing sender and sensing receiver.

32. The method according to any one of claims 18-31, characterized in that, Also includes: Send the first information to the second network function entity.

33. A sensing method, performed by a first network functional entity, the method comprising: Receive the first request sent by the second entity; The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

34. The method according to claim 33, characterized in that, The type of the second entity is any one of the following: Reliable application functionality; A trusted terminal; A trustworthy perception client.

35. The method according to claim 33 or 34, characterized in that, The first request includes at least one of the following: The identifier of the requested perceived target; The identifier of the target owner of the requested perception; The identifier of the first terminal and the sensing role requested by the first terminal; the sensing role is either a sensing receiver or a sensing sender. The requested sensing area; The perceived time of the request; A request to associate the identifier of a second terminal with the perception result, wherein the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. Requests to open-aware contextual information.

36. The method according to any one of claims 33-35, characterized in that, The token includes at least one of the following: The identification of permitted perceived targets; The identifier of the owner of the permitted perception target; The identifier of the third terminal and the perception role that the third terminal is allowed to assume; Permissible sensory area; Permissible perception time; An indication that allows the identification of a fourth terminal to be associated with a sensing result, wherein the fourth terminal is at least one of the terminal corresponding to the permitted sensing target, the terminal of the owner of the permitted sensing target, and the terminal that assumes the sensing role; Instructions that allow open awareness of contextual information.

37. The method according to any one of claims 33-36, characterized in that, The first network functional entity is at least one of the following types of enforcement points: Select the enforcement point for at least one of the sensing receiver and the sensing sender; Determine whether to authorize the execution point that associates the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role; Determine whether to authorize the execution point that is aware of context information.

38. The method according to any one of claims 33-37, characterized in that, The first network functional entity is the execution point that determines whether to authorize associating the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. The method further includes: The token is determined to be a valid token. Based on the token, it is determined that it is permissible to associate the identifier of the second terminal with the perception result, and the association between the identifier of the second terminal and the perception result is triggered.

39. [Amended according to Rule 26, 12.04.2024] The method according to claim 38, characterized in that, The token does not include an indication that allows the identifier of a fourth terminal to be associated with the perception result; The association between the identifier that triggers the second terminal and the perception result includes: Without triggering the authorization process of associating the identifier of the second terminal with the perception result, the association between the identifier of the second terminal and the perception result is triggered.

40. The method according to any one of claims 33-37, characterized in that, The first network functional entity is the execution point that determines whether to authorize associating the identifier of the second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role. The method further includes: If the token is determined to be a valid token, and based on the token, it is determined that the association between the identifier of the second terminal and the perception result should be rejected, then any one of the following steps is performed: The association between the identifier and the perception result of the second terminal is not triggered; The authorization process that associates the identifier and perception result of the second terminal is not triggered.

41. The method according to any one of claims 33-37, characterized in that, The first network functional entity is the execution point that determines whether to authorize the association of the second terminal's identifier with the perception result; The method also includes The token is determined to be a valid token, and the token does not include an indication that allows the identifier of the fourth terminal to be associated with the perception result, triggering the authorization process of associating the identifier of the second terminal with the perception result; The second terminal is at least one of the following: the terminal corresponding to the requested sensing target, the terminal corresponding to the owner of the requested sensing target, and the terminal that assumes the sensing role. The fourth terminal is at least one of the following: the terminal corresponding to the permitted sensing target, the terminal of the permitted sensing target owner, and the terminal permitted to assume a sensing role.

42. The method according to any one of claims 33-37, characterized in that, The first network functional entity is the execution point for determining whether to authorize the opening of the awareness context information; The method further includes: The token is determined to be a valid token. Based on the token, it is determined whether to allow access to the perception context information.

43. The method according to claim 42, characterized in that, The open-aware context information includes: Without triggering the authorization process of associating the identifier and perception result of the second terminal, the perception context information is made available; Wherein, the second terminal is at least one of the terminal corresponding to the requested sensing target, the terminal of the owner of the requested sensing target, and the first terminal; the first terminal is the terminal that is requested to assume the sensing role.

44. The method according to any one of claims 33-37, characterized in that, The first network functional entity is the execution point for determining whether to authorize the opening of the awareness context information; The method further includes: If the token is determined to be a valid token, then based on the token, it is determined that the perception context information will not be opened.

45. The method according to any one of claims 33-37, characterized in that, The first network functional entity is the execution point for determining whether to authorize the opening of the awareness context information; The method further includes: If the token is determined to be a valid token and does not include an indication that allows Open Aware Context Information, the authorization process for Open Aware Context Information is triggered.

46. ​​The method according to any one of claims 38-45, characterized in that, Determining that the token is a legitimate token includes at least one of the following: Send the token to the third network function entity; determine the token as a valid token based on the information received from the third network function entity that the token is a valid token; The token is verified based on the public key sent by the third network function entity obtained in advance, and the token is determined to be a legitimate token. The third network functional entity is either a network warehousing functional entity or a core functional entity of a general API open framework.

47. The method according to any one of claims 33-46, characterized in that, Also includes: Send the first message to the second network function entity; The first piece of information is any one of the following: The second request is used to request the perception service; The second request and the first instruction; The second request and the second instruction; The first indication is used to indicate at least one of the following: It is permissible to associate the identifier of a second terminal with the perception result; the second terminal is at least one of the terminal corresponding to the requested perception target, the terminal corresponding to the owner of the requested perception target, and the terminal that assumes the perception role; Allows for open perception of contextual information; The second instruction is used to indicate at least one of the following: The identifier of the second terminal is not associated with the perception result; Refuse to disclose contextual information.

48. A sensing method, characterized in that, The method is executed by a third network functional entity, which is either a network repository functional entity or a core functional entity of a general API open framework. Send third information to the first network function entity; The third piece of information is either feedback information indicating that the token is a valid token, or a public key used to verify the token.

49. The method according to claim 48, characterized in that, The third information is feedback that the token is a valid token. Before sending the third information to the first network function entity, the process further includes: Receive a token sent by the first network function entity; the token includes authorization information related to the perception service.

50. A first entity, characterized in that, include: The transceiver module is used to send the first request to the network open function entity; The first request is used to request a perception service, and the first request includes a token, which includes perception-related authorization information.

51. A second entity, characterized in that, include: The transceiver module is used to send a first request to the first network function entity; The first request is used to request a perception service, and the first request includes a token, which includes perception-related authorization information.

52. A network open function entity, characterized in that, include: The transceiver module is used to receive the first request sent by the first entity; The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

53. A first network functional entity, characterized in that, include: The transceiver module is used to receive the first information sent by the network open function entity; The first information includes a second request, which is used to request a perception service.

54. A first network functional entity, characterized in that, include: The transceiver module is used to receive the first request sent by the second entity; The first request is used to request the perception service, and the first request includes a token, which includes authorization information related to the perception service.

55. A third network functional entity, characterized in that, include: The transceiver module is used to send third information to the first network function entity; The third piece of information is either feedback information indicating that the token is a valid token, or a public key used to verify the token.

56. A first entity, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 1 to 4.

57. A second entity, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 5 to 8.

58. A network open function entity, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 9 to 17.

59. A first network functional entity, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 18 to 32.

60. A first network functional entity, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 33 to 47.

61. A third network functional entity, characterized in that, include: One or more processors; The processor is used to execute the method according to any one of claims 48 to 49.

62. A communication system, characterized in that, include: A first entity, used to implement the method described in any one of claims 1-4; A network open functional entity for implementing the method of any one of claims 9-17; A first network functional entity is used to implement the method of any one of claims 18-32; A third network functional entity is used to implement the method of any one of claims 48-49.

63. A communication system, characterized in that, include: A second entity is used to implement the method described in any one of claims 5-8; A first network functional entity is used to implement the method of any one of claims 33-47; A third network functional entity is used to implement the method of any one of claims 48-49.

64. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1-49.

65. A program product, characterized in that, When the program product is executed by a communication device, it implements the method described in any one of claims 1-49.

Images