Information processing method, terminal, network device, communication system and storage medium

Abstract

The embodiment of the invention provides an information processing method, a terminal, network equipment, communication information and a storage medium. The information processing method is executed by a first device and comprises the following steps: sending a first request which is a perception-related request; therefore, the first request can be sent to the core network equipment through the third party (such as the first equipment), and the core network equipment can consider that information related to perception is exposed to the first equipment based on the request of the third party equipment.

Description

Information processing method, terminal, network device, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to an information processing method, a terminal, a network device, a communication system, and a storage medium. Background Art

[0002] Wireless sensing technology aims to detect and / or acquire features of distant physical objects without physical contact. The object's sensing data and its surrounding data can be analyzed to extract effective features and / or information about the object.

[0003] Summary of the Invention

[0004] The disclosed embodiments need to solve the problem of a third-party device requesting a core network device for perception-related operations.

[0005] According to a first aspect of an embodiment of the present disclosure, an information processing method is proposed, which is executed by a first device and includes: sending a first request, wherein the first request is a perception-related request.

[0006] According to a second aspect of an embodiment of the present disclosure, an information processing method is proposed, which is executed by a network exposure function (NEF), including: receiving a first request sent by a first device, wherein the first request is a perception-related request.

[0007] According to a third aspect of an embodiment of the present disclosure, an information processing method is proposed, which is performed by a first network function, including: receiving a request, wherein the request is a perception-related request.

[0008] According to a fourth aspect of an embodiment of the present disclosure, an information processing method is proposed, which is performed by a second network function, including: receiving a request, wherein the request is a perception-related request.

[0009] According to a fifth aspect of an embodiment of the present disclosure, an information processing method is proposed, which is performed by Unified Data Management (UDM), including: receiving a request, wherein the request is a perception-related request.

[0010] According to the sixth aspect of an embodiment of the present disclosure, an information processing method is proposed, which is executed by a first terminal, including: receiving a third request sent by a network function, where the third request is used to request fourth information of the first terminal; and sending the fourth information to the network function.

[0011] According to the seventh aspect of the embodiment of the present disclosure, an information processing method is proposed, including: a network device sends a third request to a first terminal, wherein the third request is used to obtain fourth information of the first terminal; and the first terminal sends the fourth information to the network device.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a first device is proposed, including: a first transceiver module, configured to send a first request, wherein the first request is a perception-related request.

[0013] According to a ninth aspect of an embodiment of the present disclosure, a NEF is proposed, comprising: a second transceiver module, configured to receive a first request sent by a first device, wherein the first request is a perception-related request.

[0014] According to a tenth aspect of an embodiment of the present disclosure, a first network function is proposed, including: a third transceiver module, configured to receive a request, wherein the request is a perception-related request.

[0015] According to an eleventh aspect of an embodiment of the present disclosure, a second network function is proposed, including: a fourth transceiver module, configured to receive a request, wherein the request is a perception-related request.

[0016] According to a twelfth aspect of an embodiment of the present disclosure, a UDM is proposed, including: a fifth transceiver module, configured to receive a request, wherein the request is a perception-related request.

[0017] According to the thirteenth aspect of an embodiment of the present disclosure, a first terminal is proposed, comprising: a sixth transceiver module, configured to receive a third request sent by a network function, wherein the third request is used to request fourth information of the first terminal; and send the fourth information to the network function.

[0018] According to the fourteenth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising one or more processors; wherein the above-mentioned communication device is used to execute the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the optional implementation methods of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect and the sixth aspect.

[0019] According to the fifteenth aspect of an embodiment of the present disclosure, a communication system is proposed, including: a first device, an NEF, a first network function, a second network function, a UDM and / or a first terminal; wherein the above-mentioned first device is configured to execute the method described in the optional implementation manner of the first aspect, the above-mentioned NEF is configured to execute the method described in the optional implementation manner of the second aspect, the above-mentioned first network function is configured to execute the method described in the optional implementation manner of the third aspect, the above-mentioned second network function is configured to execute the method described in the optional implementation manner of the fourth aspect, the above-mentioned UDM is configured to execute the method described in the optional implementation manner of the fifth aspect, and / or the above-mentioned first terminal is configured to execute the method described in the optional implementation manner of the sixth aspect.

[0020] According to the sixteenth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the optional implementation of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect and the sixth aspect.

[0021] The disclosed embodiments can enable a third-party device to request a core network device for perception-related operations. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0023] FIG1 is a schematic structural diagram of an information processing system according to an embodiment of the present disclosure.

[0024] FIG2 is an interactive schematic diagram illustrating an information processing method according to an embodiment of the present disclosure.

[0025] FIG3A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0026] FIG3B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0027] FIG4A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0028] FIG4B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0029] FIG4C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0030] FIG5A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0031] FIG5B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0032] FIG5C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0033] FIG6A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0034] FIG6B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0035] FIG6C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0036] FIG7A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0037] FIG7B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0038] FIG7C is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0039] FIG8A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0040] FIG8B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0041] FIG9A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0042] FIG9B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0043] FIG10A is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0044] FIG10B is a flow chart illustrating an information processing method according to an embodiment of the present disclosure.

[0045] FIG11A is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0046] FIG11B is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0047] FIG11C is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0048] FIG11D is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0049] FIG11E is a schematic structural diagram of a network device according to an embodiment of the present disclosure.

[0050] FIG11F is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

[0051] FIG12A is a schematic structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0052] FIG12B is a schematic structural diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0053] The embodiments of the present disclosure provide an information processing method, a terminal, a network device, communication information, and a storage medium.

[0054] In a first aspect, an embodiment of the present disclosure proposes an information processing method, which is executed by a first device, and includes: sending a first request, wherein the first request is a perception-related request.

[0055] In the above embodiment, a first request can be sent to the core network device through a third party (eg, the first device), which is beneficial for the core network device to consider exposing perception-related information to the first device based on the request of the third-party device.

[0056] In combination with some embodiments of the first aspect, in some embodiments, the first request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0057] In the above embodiment, the first request includes at least one first identifier, thereby enabling perception-related authorization for one or more terminals. Furthermore, the first request includes role information corresponding to the first identifier, facilitating confirmation by the core network device of whether the terminal can assume the role indicated in the first request.

[0058] In combination with some embodiments of the first aspect, in some embodiments, sending the first request includes at least one of the following: sending the first request to the NEF; sending the first request to the first network function; sending the first request to the first network function through the NEF; sending the first request to the UDM; and sending the first request to the UDM through the NEF.

[0059] In the above embodiment, the first device sends the first request to each device in the core network through multiple channels.

[0060] In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving first information, wherein the first information includes a perception result and / or second information.

[0061] In the above embodiment, the core network device may be enabled to expose the perception-related information to the third party (eg, the first device) in consideration of the request of the third party.

[0062] In combination with some embodiments of the first aspect, in some embodiments, receiving the first information includes at least one of the following: receiving the first information sent by the NEF; receiving the first information sent by the first network function through the NEF; receiving the first information sent by the first network function; receiving the first information sent by the second network function through the NEF; receiving the first information sent by the UDM; and receiving the first information sent by the UDM through the NEF.

[0063] In the above embodiments, the perception-related information may be provided to the third party in a variety of ways.

[0064] In combination with some embodiments of the first aspect, in some embodiments, the first device includes at least one of the following: (Application Function, AF), a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: Access and Mobility Management Function (AMF), Gateway Mobile Location Center (GMLC), Location Management Function (LMF), and a perception-related network function (Unified Data Management, NF); and / or, the second network function includes at least one of the following: AMF, LMF, and a perception-related network function.

[0065] In the above embodiments, a variety of first devices, first network functions and / or second network functions are provided, which can adapt to more application scenarios.

[0066] In a second aspect, an embodiment of the present disclosure proposes an information processing method, which is executed by an NEF, and includes: receiving a first request sent by a first device, wherein the first request is a perception-related request.

[0067] In combination with some embodiments of the second aspect, in some embodiments, receiving the first request includes: receiving the first request sent by the first device, wherein the first request is a perception-related request.

[0068] In combination with some embodiments of the second aspect, in some embodiments, the first request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0069] In combination with some embodiments of the second aspect, in some embodiments, the method also includes: obtaining third information, wherein the third information is used to indicate at least one of the following: a first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0070] In the above embodiment, the third information can be obtained to facilitate the core network device to accurately determine whether the first terminal is authorized to participate in the perception service, whether it agrees to open (expose) the second information of the first terminal, etc.; it can also facilitate determining whether the first terminal requires privacy verification.

[0071] In combination with some embodiments of the second aspect, in some embodiments, obtaining the third information includes: sending a second request to the UDM, where the second request is used to request the third information; and receiving the third information sent by the UDM.

[0072] In the above embodiment, the third information can be obtained from the UDM, thereby facilitating verification of whether the first terminal is authorized to participate in the sensing service, whether the third information is open, and the like.

[0073] In combination with some embodiments of the second aspect, in some embodiments, the second request includes at least one first identifier.

[0074] In combination with some embodiments of the second aspect, in some embodiments, the method also includes at least one of the following: based on the third information, determining whether the first terminal is authorized to participate in the perception service; based on the third information, determining whether to agree to open the second information of the first terminal; based on the third information, determining whether to agree to the first terminal to assume the role associated with the first request; and based on the third information, determining whether to agree to send a third request to the first terminal.

[0075] In combination with some embodiments of the second aspect, in some embodiments, the method includes at least one of the following: sending a fourth request to the first network function; wherein the fourth request is a perception-related request; the fourth request includes a first identifier and / or role information; sending the fourth request to the second network function; and sending the fourth request to the UDM.

[0076] In combination with some embodiments of the second aspect, in some embodiments, the method includes at least one of the following: based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fourth request to the first network function, wherein the fourth request is a perception-related request; the fourth request includes a first identifier and / or role information; based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fourth request to the second network function; based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fourth request to the UDM; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fourth request to the first network function; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fourth request to the second network function; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fourth request to the UDM; based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fourth request to the first network function; based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fourth request to the second network function; and based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fourth request to the UDM.

[0077] In the above embodiment, when the NEF determines based on the third information that the first terminal is not authorized to participate in the perception service, does not agree to open the second information, and cannot assume the role associated with the first request, it determines not to send perception-related requests to the first network function, the second network function and / or UDM, thereby reducing unnecessary waste of resources and / or power consumption.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: based on the third information, determining to send a response message to the first device, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0079] In the above embodiment, the NEF may send a rejection message of the perception-related request to the first device based on the third information, so that the first device knows whether the perception-related request is successful.

[0080] In combination with some embodiments of the second aspect, in some embodiments, the method further includes: ending the perception-related process based on the third information.

[0081] In the above embodiment, if the third information indicates that the first terminal is not authorized to participate in the perception service, or indicates that it does not agree to open the second information, the NEF can end the perception-related process, thereby reducing unnecessary waste of resources and / or power consumption.

[0082] In combination with some embodiments of the second aspect, in some embodiments, the method also includes at least one of the following: receiving first information sent by a first network function; wherein the first information includes a perception result and / or second information; receiving first information sent by a second network function; and receiving first information sent by a UDM.

[0083] In combination with some embodiments of the second aspect, in some embodiments, the method also includes at least one of the following: when the first terminal is authorized to participate in the perception service, determining whether to agree to open the second information of the first terminal based on the third information; and when the first terminal is authorized to participate in the perception service, determining whether to agree to open the perception results related to the first terminal based on the third information.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the method also includes at least one of the following: determining based on the third information that the second information of the first terminal is agreed to be opened, and sending the second information to the first device; determining based on the third information that the second information of the first terminal is not agreed to be opened, and determining not to send the second information to the first device; determining based on the third information that the perception result related to the first terminal is agreed to be opened, and sending the perception result to the first device; and determining based on the third information that the perception result related to the first terminal is not agreed to be opened, and determining not to send the perception result to the first device.

[0085] In combination with some embodiments of the second aspect, in some embodiments, the first device includes at least one of the following: AF, a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: AMF, GMLC, LMF, and a network function related to perception; and / or, the second network function includes at least one of the following: AMF, LMF, and a network function related to perception.

[0086] In a third aspect, an embodiment of the present disclosure proposes an information processing method, which is performed by a first network function, including: receiving a request, wherein the request is a perception-related request.

[0087] In combination with some embodiments of the third aspect, in some embodiments, the request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0088] In combination with some embodiments of the third aspect, in some embodiments, receiving the request includes at least one of the following: receiving the fourth request sent by the NEF; receiving the first request sent by the first device; and receiving the sixth request sent by the UDM.

[0089] In combination with some embodiments of the third aspect, in some embodiments, the method further includes at least one of the following: executing a perception service related to the first terminal based on the request.

[0090] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: sending a third request to the first terminal, wherein the third request is used to request fourth information; and receiving the fourth information sent by the first terminal.

[0091] In the above embodiment, the network function can obtain the fourth information from the first terminal to facilitate privacy verification of the first terminal.

[0092] In combination with some embodiments of the third aspect, in some embodiments, the fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the perception service; whether it agrees to open the second information of the first terminal; and whether it agrees to assume the role associated with the first request.

[0093] In combination with some embodiments of the third aspect, in some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened; and determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal cannot assume the role associated with the first request.

[0094] In combination with some embodiments of the third aspect, in some embodiments, the method also includes: obtaining third information, wherein the third information is used to indicate at least one of the following: a first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0095] In combination with some embodiments of the third aspect, in some embodiments, obtaining the third information includes: sending a second request to the UDM, where the second request is used to request the third information; and receiving the third information sent by the UDM.

[0096] In combination with some embodiments of the third aspect, in some embodiments, the second request includes at least one first identifier.

[0097] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: executing a perception service related to the first terminal based on the third information.

[0098] In combination with some embodiments of the third aspect, in some embodiments, the method also includes at least one of the following: based on the third information, determining whether the first terminal is authorized to participate in the perception service; based on the third information, determining whether to agree to open the second information of the first terminal; based on the third information, determining whether to agree to the first terminal to assume the role associated with the first request; based on the third information, determining whether privacy verification is required; and based on the third information, determining whether to agree to send a third request to the first terminal.

[0099] In combination with some embodiments of the third aspect, in some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal does not agree to open the second information; determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal cannot assume the role associated with the first request; and executing privacy verification based on the third information indication.

[0100] In combination with some embodiments of the third aspect, in some embodiments, the method includes at least one of the following: sending a fifth request to the second network function; wherein the fifth request is a perception-related request; the fifth request includes a first identifier and / or role information; and sending the fifth request to the UDM.

[0101] In combination with some embodiments of the third aspect, in some embodiments, the method also includes at least one of the following: based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fifth request to the UDM; wherein the fifth request is a perception-related request; the fifth request includes a first identifier and / or role information; based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fifth request to the second network function; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fifth request to the UDM; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fifth request to the second network function; based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fifth request to the UDM; based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fifth request to the second network function.

[0102] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: based on the third information, determining to send a response message to the first device, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0103] In combination with some embodiments of the third aspect, in some embodiments, the method further includes: ending the perception-related process based on the third information.

[0104] In combination with some embodiments of the third aspect, in some embodiments, the method also includes at least one of the following: receiving first information sent by the second network function, wherein the first information includes perception information and / or second information; and receiving first information sent by the UDM.

[0105] In combination with some embodiments of the third aspect, in some embodiments, the method also includes at least one of the following: sending first information to the NEF or the first device; determining based on the third information to agree to open the second information of the first terminal, and sending the second information to the first device or NEF; and determining based on the third information not to agree to open the second information of the first terminal, and determining not to send the second information to the first device or NEF.

[0106] In combination with some embodiments of the third aspect, in some embodiments, the first device includes at least one of the following: AF, a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: AMF, GMLC, LMF, and a network function related to perception; and / or, the second network function includes at least one of the following: AMF, LMF, and a network function related to perception.

[0107] In a fourth aspect, an embodiment of the present disclosure proposes an information processing method, which is executed by a second network function, including: receiving a request, wherein the request is a perception-related request.

[0108] In conjunction with some embodiments of the fourth aspect, in some embodiments, the request is a perception-related request.

[0109] In combination with some embodiments of the fourth aspect, in some embodiments, the request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0110] In combination with some embodiments of the fourth aspect, in some embodiments, it includes at least one of the following: receiving a first request sent by a first device; receiving a fourth request sent by a first network function; receiving a sixth request sent by a UDM.

[0111] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: executing a perception service related to the first terminal based on the request.

[0112] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: sending a third request to the first terminal, wherein the third request is used to request fourth information; and receiving the fourth information sent by the first terminal.

[0113] In combination with some embodiments of the fourth aspect, in some embodiments, the fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the perception service; whether it agrees to open the second information of the first terminal; and whether it agrees to assume the role associated with the first request.

[0114] In combination with some embodiments of the fourth aspect, in some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened; and determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal cannot assume the role associated with the first request.

[0115] In combination with some embodiments of the fourth aspect, in some embodiments, the method also includes: obtaining third information, wherein the third information is used to indicate at least one of the following: at least one first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0116] In combination with some embodiments of the fourth aspect, in some embodiments, obtaining the third information includes: sending a second request to the unified data management (UDM), where the second request is used to request the third information; and receiving the third information sent by the UDM.

[0117] In combination with some embodiments of the fourth aspect, in some embodiments, the second request includes at least one first identifier.

[0118] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: executing a perception service related to the first terminal based on the third information.

[0119] In combination with some embodiments of the fourth aspect, in some embodiments, the method also includes at least one of the following: based on the third information, determining whether the first terminal is authorized to participate in the perception service; based on the third information, determining whether to agree to open the second information of the first terminal; based on the third information, determining whether to agree to open the perception results related to the first terminal; based on the third information, determining whether to agree to the first terminal to assume the role associated with the first request; and based on the third information, determining whether to agree to send a third request to the first terminal.

[0120] In combination with some embodiments of the fourth aspect, in some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal does not agree to open the second information; and determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0121] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: sending a seventh request to the UDM, wherein the seventh request is a perception-related request; and the seventh request includes the first identifier and / or role information.

[0122] In combination with some embodiments of the fourth aspect, in some embodiments, the method also includes at least one of the following: based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the seventh request to the UDM; wherein the seventh request is a request related to perception; the seventh request includes a first identifier and / or role information; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the seventh request to the UDM; and based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the seventh request to the UDM.

[0123] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: based on the third information, determining to send a response message to the first device, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0124] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: ending the perception-related process based on the third information.

[0125] In combination with some embodiments of the fourth aspect, in some embodiments, the method further includes: receiving first information sent by the UDM.

[0126] In combination with some embodiments of the fourth aspect, in some embodiments, the method also includes: determining based on the third information that the second information of the first terminal is agreed to be opened, and sending the second information to the first network function; or, determining based on the third information that the second information of the first terminal is not agreed to be opened, and determining not to send the second information to the first network function.

[0127] In combination with some embodiments of the fourth aspect, in some embodiments, the first device includes at least one of the following: AF, a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: AMF, GMLC, LMF, and a network function related to perception; and / or, the second network function includes at least one of the following: AMF, LMF, and a network function related to perception.

[0128] In a fifth aspect, an embodiment of the present disclosure proposes an information processing method, which is executed by Unified Data Management (UDM), including: receiving a request, wherein the request is a perception-related request.

[0129] In combination with some embodiments of the fifth aspect, in some embodiments, the request is a perception-related request.

[0130] In combination with some embodiments of the fifth aspect, in some embodiments, the request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0131] In combination with some embodiments of the fifth aspect, in some embodiments, receiving a request includes at least one of the following: receiving a first request sent by a first device; receiving the first request sent by the first device through a network open function NEF; receiving a second request sent by NEF; receiving a fifth request sent by the first network function; and receiving a seventh request sent by the second network function.

[0132] In combination with some embodiments of the fifth aspect, in some embodiments, the method also includes: receiving through AMF or directly receiving third information sent by the first terminal, wherein the third information is used to indicate at least one of the following: a first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0133] In combination with some embodiments of the fifth aspect, in some embodiments, the method further includes: determining the third information of the first terminal from the third information of at least one terminal based on the first identifier, wherein the terminal includes the first terminal and / or the third terminal.

[0134] In combination with some embodiments of the fifth aspect, in some embodiments, the method includes at least one of the following: sending the third information of the first terminal to the NEF; sending the third information of the first terminal to the first network function; and sending the third information of the first terminal to the second network function.

[0135] In combination with some embodiments of the fifth aspect, in some embodiments, the method also includes at least one of the following: sending a sixth request to the first network function; wherein the sixth request is a perception-related request; and sending the sixth request to the second network function.

[0136] In combination with some embodiments of the fifth aspect, in some embodiments, the method also includes at least one of the following: based on the third information, determining not to send the sixth request to the first network function; wherein the sixth request is a perception-related request; and based on the third information, determining not to send the sixth request to the second network function.

[0137] In combination with some embodiments of the fifth aspect, in some embodiments, the method also includes at least one of the following: sending first information to the first network function; wherein the first information includes the perception result and / or the second information; sending the first information to the second network function; sending the first information to the NEF; sending the first information to the first device through the NEF; and sending the first information to the first device based on determining the agreement to open the first information of the first terminal.

[0138] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first device includes at least one of the following: an AF, a client corresponding to the second terminal, and the first terminal; and / or,

[0139] In combination with some embodiments of the fifth aspect, the first network function includes at least one of the following: AMF, gateway mobile positioning center GMLC, location management function LMF and perception-related network function NF; and / or, the second network function includes at least one of the following: access and mobility management function AMF, LMF and perception-related network function.

[0140] In a sixth aspect, an embodiment of the present disclosure proposes an information processing method, which is executed by a first terminal, including: receiving a third request sent by a network function, where the third request is used to request fourth information of the first terminal; and sending the fourth information to the network function.

[0141] In combination with some embodiments of the sixth aspect, in some embodiments, the third request is used to request fourth information of the first terminal; the method also includes: sending the fourth information to the network function.

[0142] In combination with some embodiments of the sixth aspect, in some embodiments, the first network function or the second network function; wherein the first network function includes: GMLC, LMF and / or a network function NF related to perception; and / or, the second network function includes: AMF, LMF and / or a network function related to perception.

[0143] In combination with some embodiments of the sixth aspect, in some embodiments, the fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the perception service; whether it agrees to open the second information of the first terminal; and whether it agrees to assume the role indicated in the first identifier.

[0144] In combination with some embodiments of the sixth aspect, in some embodiments, the method also includes: sending third information of the first terminal to the UDM or through access to the UDM, wherein the third information is used to indicate at least one of the following: a first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0145] According to the seventh aspect of the embodiment of the present disclosure, an information processing method is proposed, including: a network device sends a third request to a first terminal, wherein the third request is used to obtain fourth information of the first terminal; and the first terminal sends the fourth information to the network device.

[0146] According to an eighth aspect of an embodiment of the present disclosure, a first device is proposed, including: a first transceiver module, configured to send a first request, wherein the first request is a perception-related request.

[0147] According to a ninth aspect of an embodiment of the present disclosure, a NEF is proposed, comprising: a second transceiver module, configured to receive a first request sent by a first device, wherein the first request is a perception-related request.

[0148] According to a tenth aspect of an embodiment of the present disclosure, a first network function is proposed, including: a third transceiver module, configured to receive a request, wherein the request is a perception-related request.

[0149] According to an eleventh aspect of an embodiment of the present disclosure, a second network function is proposed, including: a fourth transceiver module, configured to receive a request, wherein the request is a perception-related request.

[0150] According to a twelfth aspect of an embodiment of the present disclosure, a UDM is proposed, including: a fifth transceiver module, configured to receive a request, wherein the request is a perception-related request.

[0151] According to the thirteenth aspect of an embodiment of the present disclosure, a first terminal is proposed, comprising: a sixth transceiver module, configured to receive a third request sent by a network function, wherein the third request is used to request fourth information of the first terminal; and send the fourth information to the network function.

[0152] According to the fourteenth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising one or more processors; wherein the above-mentioned communication device is used to execute the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the optional implementation methods of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect and the sixth aspect.

[0153] According to the fifteenth aspect of an embodiment of the present disclosure, a communication system is proposed, including: a first device, an NEF, a first network function, a second network function, a UDM and / or a first terminal; wherein the above-mentioned first device is configured to execute the method described in the optional implementation manner of the first aspect, the above-mentioned NEF is configured to execute the method described in the optional implementation manner of the second aspect, the above-mentioned first network function is configured to execute the method described in the optional implementation manner of the third aspect, the above-mentioned second network function is configured to execute the method described in the optional implementation manner of the fourth aspect, the above-mentioned UDM is configured to execute the method described in the optional implementation manner of the fifth aspect, and / or the above-mentioned first terminal is configured to execute the method described in the optional implementation manner of the sixth aspect.

[0154] According to the sixteenth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the optional implementation of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect and the sixth aspect.

[0155] In the seventeenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the optional implementation of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect and the sixth aspect.

[0156] In aspect 18, an embodiment of the present disclosure proposes a computer program which, when running on a computer, enables the computer to execute the information processing method described in aspect 1, aspect 2, aspect 3, aspect 4, aspect 5, aspect 6, or the optional implementation of aspect 1, aspect 2, aspect 3, aspect 4, aspect 5 and aspect 6.

[0157] In the nineteenth aspect, an embodiment of the present disclosure proposes a chip or a chip system; the chip or chip system includes a processing circuit configured to execute the method described in accordance with the above-mentioned first aspect, second aspect, third aspect, fourth aspect, fifth aspect, sixth aspect, or the optional implementation manner of the first aspect, second aspect, third aspect, fourth aspect, fifth aspect and sixth aspect.

[0158] It is understood that the aforementioned network devices, terminals, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects achievable by these devices can be referenced to the beneficial effects of the corresponding methods and will not be further elaborated here.

[0159] The present disclosure provides an information processing method, a network device (e.g., an NEF, a first network function, a second network function, and / or a UDM), a terminal, a communication system, and a storage medium. In some embodiments, the terms information processing method and communication method are interchangeable, the terms information processing device and communication device are interchangeable, and the terms information processing system and communication system are interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0181] FIG1 is a schematic diagram showing the structure of an information processing system 100 according to an embodiment of the present disclosure. As shown in FIG1 , the information processing system 100 may include: a terminal 101 and a network device 102 .

[0182] In some embodiments, the network device 102 may include at least one of an access network device and a core network device.

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

[0184] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (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 base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

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

[0186] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

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

[0188] In some embodiments, the NEF may be used to expose capabilities of various network functions, the names of which are not limited thereto.

[0189] In some embodiments, the first network function is, for example, GMLC or LMF, but the name is not limited thereto.

[0190] In some embodiments, the second network function is, for example, AMF or LMF, but the name is not limited thereto.

[0191] In some embodiments, UDM may be used for unified management of data, etc., and its name is not limited thereto.

[0192] In some embodiments, the AF may be independent of the core network equipment.

[0193] In some embodiments, the AF may be part of a core network device.

[0194] In some embodiments, the name of AF is not limited thereto.

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

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

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

[0198] In some embodiments, wireless sensing technology may include radar (radio detection and ranging) technology; radar uses radio waves to determine physical distance (or range), angle, and / or instantaneous velocity. Alternatively, wireless sensing technology may also include other sensing technologies, such as non-radio frequency sensing technology; such non-radio frequency sensing technology has been applied to fields such as time-of-flight (ToF) cameras, accelerometers, gyroscopes, and / or lidar.

[0199] In some embodiments, integrated sensing and communication means that the sensing capabilities are provided by the same wireless communication system and base station infrastructure used for communication. Optionally, both the UE and the NR RAN node can act as sensing transmitters and / or sensing receivers in the sensing system.

[0200] In some embodiments, some examples of communication-assisted awareness services are provided:

[0201] Example 1: Real-time environmental monitoring. Real-time environmental monitoring can use wireless signals to reconstruct environmental maps to further improve positioning accuracy and enable environmental applications. For example, real-time monitoring applications may include dynamic 3D maps for driving assistance, pedestrian counting, intrusion detection, and / or traffic detection.

[0202] Example 2: 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. Alternatively, autonomous vehicles / drones should be able to monitor path information, such as selecting a route and / or complying with traffic regulations.

[0203] Example 3: Air pollution monitoring: As air humidity, particulate matter (PM) concentration, and / or carrier frequency change, the quality of the received wireless signal exhibits different attenuation characteristics, which can be used for weather or air quality monitoring.

[0204] Example 4: Indoor healthcare and intrusion detection. Indoor healthcare and intrusion detection can achieve respiratory rate estimation, respiratory depth estimation, apnea detection, vital sign monitoring of the elderly, and / or indoor intrusion detection.

[0205] In some embodiments, the perception of wireless communication channels and / or environments can further improve the performance of wireless communication systems. Optionally, some examples of perception-assisted communication are provided:

[0206] Example 1: Perceiving the UE's location and / or channel environment can narrow the beam scanning range and shorten the beam training time.

[0207] Example 2: Perceiving the UE's position, speed, motion trajectory, and / or channel environment for beam prediction can reduce the overhead of beam measurement and the delay of beam tracking.

[0208] Example 3: Perceiving UE properties and / or channel environment can improve channel estimation performance.

[0209] In some embodiments, in a perception scenario, by providing a UE identity (ID), a third party (e.g., AF, client on the UE) can request the core network to disclose perception results related to or involving a specific UE. In order to facilitate the third party to analyze or process the perception results, it may also be necessary to provide the third party with sensing contextual information. The perception contextual information can be requested by the third party or actively provided by the core network, and may include map information, area information, capture time, UE location and / or UE ID. Such contextual information may be required in cases where the perception results are to be combined with data from other sources outside the communication system. If the UE is identifiable, the UE location information is sensitive and should not be exposed without the UE's consent. The UE ID, especially the permanent UE ID, should not be exposed without the UE's consent. There is currently no existing mechanism that enables the core network to authorize the exposure of sensitive perception contextual information by considering the UE ID provided by a third party.

[0210] Optionally, the UE may be the terminal in the previous embodiment.

[0211] FIG2 is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to an information processing method for an information processing system 100, and the method includes:

[0212] Step S2101A: The first device sends a first request to the NEF.

[0213] In some embodiments, the first device includes at least one of the following: an AF, a second terminal, and a client corresponding to the second terminal. Optionally, the client can be the terminal in the previous embodiment. Optionally, the second terminal is different from the first terminal.

[0214] In some embodiments, the NEF receives a first request sent by a first device.

[0215] In some embodiments, the first request includes at least one first identifier and / or role information corresponding to the first identifier.

[0216] Optionally, the first identifier is one or more; the plurality is two or more.

[0217] Optionally, the first identifier is used to uniquely identify the terminal, or the first identifier is used to indicate the terminal. Exemplarily, the terminal includes the first terminal. Exemplarily, the terminal may include any terminal; for example, the terminal may include the first terminal, the second terminal, and / or the third terminal.

[0218] Optionally, the role information is used to indicate that the terminal is a perception receiver or a perception sender. For example, if the role information is a first value, it is used to indicate that the terminal is a perception receiver; or if the role information is a second value, it is used to indicate that the terminal is a perception sender.

[0219] Optionally, one first identifier corresponds to one role information; the first identifier is used to indicate a terminal, and the role information is used to indicate whether the terminal is a perception receiver or a perception sender.

[0220] Optionally, the first identifier may be any number, index, or character string used to identify the first terminal.

[0221] In some embodiments, the first request is a perception-related request.

[0222] In some embodiments, the first request is used to request a perception result related to the first terminal. Optionally, the perception result related to the first terminal may be a perception result of the first terminal participating in a perception process.

[0223] In some embodiments, the first request is used to request first information of the first terminal.

[0224] In some embodiments, the first request is used for the first network function and / or the second network function to perform the perception service of the first terminal, or the first request is used to trigger the perception service, or the first request is used to trigger the first network function and / or the second network function to perform the perception service of the first terminal.

[0225] Optionally, the first network function may include at least one of the following: GMLC, LMF, and a perception-related network function.

[0226] Optionally, the second network function may include at least one of the following: AMF, LMF, and a perception-related network function.

[0227] Optionally, the name of the network function related to perception is not limited, and it can be, for example, perception network function, perception function, etc.

[0228] Optionally, the sensing service may be any service related to wireless sensing technology, for example, an environment monitoring service, an air monitoring service, a crop monitoring service, a traffic monitoring service, a terminal location monitoring service, a terminal channel and / or beam monitoring service, etc.

[0229] Optionally, the first information includes: perception results and / or second information.

[0230] Optionally, the second information is relevant information about participation in the perception service.

[0231] Optionally, the second information may include at least one of the following: location information of the first terminal, speed of the first terminal, channel parameters of the first terminal, a first identifier of the first terminal, a permanent identifier of the first terminal, various attribute information of the first terminal, and / or various environmental data. Optionally, the environmental data may include various indoor, outdoor, and / or surrounding environmental information, such as air quality information and / or traffic route information. Optionally, the environmental data may include environmental information related to the participation in the sensing service, such as a person's breathing rate and / or breathing depth and / or current time information.

[0232] Optionally, the first identifier of the first terminal may be a Generic Public Subscription Identifier (GPSI) or a Subscription Permanent Identifier (SUPI) of the first terminal.

[0233] Optionally, the name of the first information is not limited, and it can be, for example, perception data, environmental data, etc.

[0234] Optionally, the name of the second information is not limited, and it can be, for example, perception data, environmental data, perception context data, etc.

[0235] In some embodiments, the name of the first request is not limited, and it can be, for example, a perception request, a perception result request, a perception service request, etc.

[0236] Step S2101B: The first device sends a first request to the first network function.

[0237] In some embodiments, the first network function receives a first request sent by the first device.

[0238] Step S2101C: The first device sends a first request to the first network function through the NEF.

[0239] In some embodiments, the first network function receives, through the NEF, a first request sent by the first device.

[0240] Optionally, the first device sends a first request to the NEF; the NEF sends the first request to the first network function.

[0241] Optionally, the first network function receives a first request sent by the NEF, wherein the first request is received by the NEF from the first device.

[0242] Step S2101D: The first device sends a first request to the UDM.

[0243] In some embodiments, the UDM receives a first request sent by a first device.

[0244] Step S2101E: The first device sends a first request to the UDM through the NEF.

[0245] In some embodiments, the UDM receives the first request sent by the first device through the NEF.

[0246] Optionally, the first device sends a first request to the NEF; the NEF sends the first request to the first device.

[0247] Optionally, the UDM receives a first request sent by the NEF, wherein the first request is received by the NEF from the first device.

[0248] In some optional embodiments, the NEF receives a first request sent by the first device; the NEF sends the first request to the first network function, the second network function and / or the UDM.

[0249] In some optional embodiments, the first network function receives the first request sent by the first device and / or NEF; the first network function sends the first request to the second network function and / or UDM.

[0250] In some optional embodiments, the second network function receives the first request sent by the first device, the NEF and / or the first network function; and the second network function sends the first request to the UDM.

[0251] In the disclosed embodiments, when network element A receives information from network element B, the received information may be related information processed by network element A or the original information. For example, when the UDM receives a first request sent by a first device through an NEF, the received information may be the original first request sent by the first device or the first request processed by the NEF, such as a portion of the first request.

[0252] Step S2101F: The first device sends a first request to the second network function. Step S2101F may be optional.

[0253] In some embodiments, the second network function receives the first request sent by the first device.

[0254] Optionally, the first device sends the first request to the second network function through the NEF.

[0255] Optionally, the first device sends the first request to the second network function through the first network function.

[0256] In some embodiments, step S2101 includes the above-mentioned step S2101A, step S2101B, step S2101C, step S2101D, step S2101E / or step S2101F.

[0257] Step S2102A: NEF sends a second request to UDM.

[0258] In some embodiments, the UDM receives the second request sent by the NEF.

[0259] In some embodiments, the second request includes at least one first identification.

[0260] In some embodiments, the second request may include at least one first identifier and / or role information corresponding to the first identifier.

[0261] In some embodiments, the second request is for requesting third information.

[0262] In some embodiments, the name of the second request is not limited, and it can be, for example, a user consent information request.

[0263] In some embodiments, the third information is used to indicate at least one of the following: whether to authorize participation in the perception service, whether to agree to open the first information, whether to agree to open the perception results, whether privacy verification is required, and whether to agree to assume the role associated with the first request.

[0264] In some embodiments, the third information indicates at least one of: whether the first terminal is authorized to participate in the sensing service, whether the first terminal agrees to disclose the first information of the first terminal, whether the first terminal agrees to disclose the sensing result of the first terminal, whether privacy verification is required, and whether the first terminal agrees to assume the role associated with the first request. Optionally, "disclosure" can mean exposure.

[0265] In some embodiments, the role associated with the first request may also be: the role associated with the fourth request, the role associated with the fifth request, or the role associated with the seventh request, etc. The fourth request, the fifth request, or the seventh request, etc. may include a first identifier and role information corresponding to the first identifier. The first identifier may be used to indicate the terminal, and the role information may be used to indicate the role of the terminal (whether it is a perception receiver or a perception sender), so that the role assumed by the terminal (e.g., the first terminal) may be determined through these requests (the first request, the fourth request, or the seventh request, etc.) or the first identifier.

[0266] In some embodiments, the third information is used to indicate the first identifier and / or the role information corresponding to the first identifier; or, the third information includes the first identifier and / or the role information corresponding to the first identifier.

[0267] Optionally, the third information is used to indicate whether the first terminal is allowed to participate in the sensing service. Optionally, the third information is used to indicate whether to agree or refuse to open the first information of the first terminal.

[0268] Optionally, the third information includes at least one of the following: first indication information, second indication information, third indication information, fourth indication information, and fifth indication information. For example, the first indication information is used to indicate whether to authorize participation in the perception service; the second indication information is used to indicate whether to agree to disclose the first information; the third indication information is used to indicate whether to perform privacy verification; the fourth indication information is used to indicate whether to assume the role associated with the first request; and the fifth indication information is used to indicate whether to agree to disclose the perception result.

[0269] Exemplarily, the first indication information and the second indication information may both be one or more bits.

[0270] Exemplarily, the first indication information is a first value, used to indicate that the first terminal authorizes or allows participation in the perception service; or the first indication information is a second value, used to indicate that the first terminal is not authorized or allowed to participate in the perception service. The first value can be "0" or "00", and the second value can be "1" or "11". Exemplarily, the second indication information is a first value, used to indicate consent to open the first information of the first terminal; or the second indication information is a second value, used to indicate disapproval or refusal to open the first information of the first terminal.

[0271] In some embodiments, the name of the third information is not limited, and it can be, for example, user consent information, user consent policy, user authorization information, user authorization policy, etc.

[0272] Step S2102B: The first network function sends a second request to the UDM.

[0273] In some embodiments, the UDM receives a second request sent by the first network function.

[0274] Step S2102C: The second network function sends a second request to the UDM.

[0275] In one embodiment, the UDM receives a second request sent by the second network function.

[0276] In some embodiments, step S2102 includes the above-mentioned step S2102A and / or step S2102B and / or step S2102C.

[0277] Step S2103A: UDM sends the third information to NEF.

[0278] In some embodiments, the NEF receives the third information sent by the UDM.

[0279] In some embodiments, the UDM sends the third information directly to the NEF.

[0280] In some embodiments, the UDM sends the third information to the NEF based on the third information.

[0281] Optionally, the UDM determines, based on the third information of the first terminal, that the first terminal is authorized to participate in the awareness service, and the UDM sends the third information indicating that the first terminal is authorized to participate in the awareness service to the NEF.

[0282] Optionally, the UDM determines, based on the third information of the first terminal, that the first terminal is not authorized to participate in the perception service, and the UDM sends the third information indicating that the first terminal is not authorized to participate in the perception service to the NEF.

[0283] Optionally, the UDM determines to agree to release the first information of the first terminal based on the third information of the first terminal, and the UDM sends the third information to the NEF, where the third information is used to indicate that the first terminal agrees to release the first information of the first terminal.

[0284] Optionally, the UDM determines that it disagrees with or rejects the first information of the first terminal based on the third information of the first terminal, and the UDM sends the third information to the NEF, where the third information is used to indicate disagreement with or rejection of the first information of the first terminal.

[0285] In some optional embodiments, the UMD receives the third information sent by the first terminal. Optionally, the first terminal sends the third information to the UDM.

[0286] Optionally, the UDM directly receives the third information sent by the first terminal. Here, the first terminal may directly send the third information to the UDM.

[0287] Optionally, the UDM receives the third information sent by the first terminal through the AMF. Here, the first terminal sends the third information to the UDM through the AMF. Exemplarily, the first terminal sends the third information to the AMF, and the AMF forwards the third information to the UDM.

[0288] Step S2103B: The UDM sends third information to the first network function.

[0289] In some embodiments, the first network function receives third information sent by the UDM.

[0290] In some embodiments, the UDM may send the third information directly to the first network function.

[0291] In some embodiments, the UDM sends the third information to the first network function based on the third information. Here, the UDM may also send the third information to the first network function based on a determination of the third information.

[0292] Optionally, the UDM determines that the first terminal is authorized to participate in the perception service based on the third information of the first terminal, and the UDM sends the third information indicating that the first terminal is authorized to participate in the perception service to the first network function.

[0293] Optionally, the UDM determines that the first terminal is not authorized to participate in the perception service based on the third information of the first terminal, and the UDM sends the third information indicating that the first terminal is not authorized to participate in the perception service to the first network function.

[0294] Optionally, the UDM determines to agree to open the first information of the first terminal based on the third information of the first terminal, and the UDM sends the third information to the first network function, wherein the third information is used to indicate that the first terminal agrees to open the first information of the first terminal.

[0295] Optionally, the UDM determines to disagree with or reject the first information of the first terminal based on the third information of the first terminal, and the UDM sends the third information to the first network function, where the third information is used to indicate disagreement with or rejection of the first information of the first terminal.

[0296] In some optional embodiments, the first terminal sends the third information to the UDM. Optionally, the UDM receives the third information sent by the first terminal.

[0297] In some optional embodiments, the first terminal sends the third information to the first network function. Optionally, the second network function receives the third information sent by the first terminal.

[0298] In some optional embodiments, the second network function sends the third information to the first network function. Optionally, the first network function receives the third information sent by the second network function.

[0299] In some optional embodiments, the first terminal sends the third information to the first network function. Optionally, the first network function receives the third information sent by the first terminal.

[0300] Optionally, when the terminal sends information to the core network device, the terminal may send the information to the core network device through the access network.

[0301] Step S2103C: The UDM sends third information to the second network function.

[0302] In some embodiments, the second network function receives third information sent by the UDM.

[0303] In some embodiments, the UDM sends the third information directly to the second network function.

[0304] In some embodiments, the UDM sends third information to the second network function based on the third information.

[0305] Optionally, for the specific implementation of the UDM sending the third information to the second network function in step S2103C, refer to the implementation of the UDM sending the third information to the NEF in step S2103A and / or the implementation of the UDM sending the third information to the first network function in step S2103B.

[0306] In some embodiments, step S2103 includes the above-mentioned step S2103A, step S2103B and / or step S2103C.

[0307] In some optional embodiments, the third information sent in step S2103 (including step S2103A, step S2103B, and / or step S2103C) can be the third information of any one or more terminals, or the third information sent in step S2103 (including step S2103A, step S2103B, and / or step S2103C) can be the third information of the first terminal. If the third information is the third information of the first terminal, before sending the third information, the UDM may include: determining the third information of the first terminal from the third information of at least one terminal based on the first identifier, where the terminal includes the first terminal and / or the third terminal.

[0308] Step S2104A: The first network function sends a third request to the first terminal.

[0309] In some embodiments, the first terminal receives a third request sent by the first network function.

[0310] In some embodiments, the third request is for requesting fourth information.

[0311] In some embodiments, the name of the third request is not limited, and it can be, for example, a privacy verification request, a user privacy verification request, etc.

[0312] In some optional embodiments, the first network function determines that privacy verification is required for the first terminal and sends a third request to the first terminal. Exemplarily, the first network function determines that privacy verification is required for the first terminal based on the third information and performs the privacy verification. Performing the privacy verification may include sending the third request to the first terminal to obtain fourth information, and determining, based on the fourth information, whether the first terminal authorizes participation in the sensing service and / or development of the first information.

[0313] In some optional embodiments, the privacy verification may also be performed by the first terminal, and the result of the privacy verification may be sent to the network device (e.g., the first network function and / or the second network function) in the form of fourth information. Exemplarily, the network device sends a request to the first terminal for privacy verification; after performing the privacy verification, the first terminal sends the privacy verification result to the network device in the form of fourth information. Here, the fourth information at least indicates or includes the privacy verification result.

[0314] In some optional embodiments, if the first device is an AF, the third request includes an AF identifier (ID); and / or, if the first device is a terminal, the third request includes a UE ID of the first device; and / or, if the first device is a client on the terminal, the third request includes a client ID;

[0315] In some embodiments, the third request may include at least one of the following: UE information that needs to be disclosed (eg, UE ID and / or UE location, etc.), the UE ID of the first terminal, and role information that the first terminal needs to assume.

[0316] In some embodiments, the fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service, whether it agrees to open the second information of the first terminal, and whether it agrees to assume the role of the first request for association.

[0317] In some embodiments, the name of the fourth information is not limited, and it can be, for example, privacy verification information, privacy verification result, user privacy verification result, etc. The user verification result can be the first information indicating whether to agree to open the first terminal.

[0318] Step S2104B: The second network function sends a third request to the first terminal.

[0319] In some embodiments, the first terminal receives a third request sent by the second network function.

[0320] In some embodiments, step S2104 includes step S2104A and / or step S2104B described above.

[0321] Step S2105A: The first terminal sends fourth information to the first network function.

[0322] In some embodiments, the first network function receives fourth information sent by the first terminal.

[0323] Step S2105B: The first terminal sends fourth information to the second network function.

[0324] In some embodiments, the second network function receives fourth information sent by the first terminal.

[0325] In some embodiments, step S2105 includes the above-mentioned step S2105A and / or step S2105B.

[0326] In step S2106A, the NEF performs a first operation.

[0327] In some embodiments, performing the first operation includes at least one of the following: determining whether the first terminal is authorized to participate in the perception service, determining whether to open the first information of the first terminal, determining whether to open the perception results related to the first terminal, sending a fourth request or not sending the fourth request, sending a response message, and ending the perception-related process.

[0328] In some embodiments, the NEF determines whether the first terminal is authorized to participate in the sensing service based on the third information. Exemplarily, the NEF determines that the first terminal is authorized to participate in the sensing service based on the third information indicating that the first terminal is authorized to participate in the sensing service. Exemplarily, the NEF determines that the first terminal is not authorized to participate in the sensing service based on the third information indicating that the first terminal is not authorized to participate in the sensing service.

[0329] In some embodiments, the NEF determines whether to approve the release of the second information of the first terminal based on the third information. Exemplarily, the NEF determines to approve the release of the second information of the first terminal based on the third information indicating approval of the release of the second information of the first terminal. Exemplarily, the NEF determines to disapprove the release of the second information of the first terminal based on the third information indicating disapproval of the release of the second information of the first terminal.

[0330] In some embodiments, the NEF determines whether to approve the first terminal to assume the role of the first association request based on third information. Exemplarily, the NEF determines that the first terminal is approved to assume the role of the first association request based on the first request in the third information being associated with the first terminal as a perception receiver, and finding out, based on the first identifier, that the role subscribed by the first terminal in the core network is a perception receiver. Exemplarily, the NEF determines that the first terminal is not approved to assume the role of the first association request based on the first request in the third information being associated with the first terminal as a perception receiver, and finding out, based on the first identifier, that the role subscribed by the first terminal in the core network is a perception sender. Exemplarily, the NEF determines that the first terminal is approved to assume the role of the first association request based on the first request in the third information being associated with the first terminal as a perception sender, and finding out, based on the first identifier, that the role subscribed by the first terminal in the core network is a perception sender. Exemplarily, the NEF determines that the first terminal is not approved to assume the role of the first association request based on the first request in the third information being associated with the first terminal as a perception sender, and finding out, based on the first identifier, that the role subscribed by the first terminal in the core network is a perception receiver.

[0331] In some embodiments, the NEF determines whether to approve sending the third request to the first terminal based on the third information. Exemplarily, the NEF determines to approve sending the third request to the first terminal based on the third information indicating that privacy verification is required. Exemplarily, the NEF determines not to approve sending the third request to the first terminal based on the third information indicating that privacy verification is not required.

[0332] In some embodiments, when the NEF determines based on the third information that privacy verification is required, it triggers the first network function or the second network function to perform privacy verification with the first terminal. Exemplarily, the NEF sends a third request to the first network function and / or the second network function; the third request is used to trigger the first network function and / or the second network function to perform privacy verification with the first terminal.

[0333] In some embodiments, the NEF determines whether to agree to open the perception result related to the first terminal based on the third information.

[0334] In some embodiments, the NEF sends the fourth request, or the NEF determines not to send the fourth request. Here, the NEF may directly send the fourth request.

[0335] Optionally, the NEF sends a fourth request to the first network function. Optionally, the first network function receives the fourth request sent by the NEF.

[0336] Optionally, the NEF sends a fourth request to the second network function. Optionally, the second network function receives the fourth request sent by the NEF.

[0337] Optionally, the NEF sends a fourth request to the unified data management (UDM). Optionally, the second network function receives the fourth request sent by the NEF.

[0338] In some embodiments, the NEF determines whether to send the fourth request based on the third information.

[0339] Optionally, based on the third information, indicating that the first terminal is authorized to participate in the perception service, the fourth request is sent to the first network function.

[0340] Optionally, the NEF instructs the first terminal to authorize participation in the perception service based on the third information, and sends a fourth request to the second network function.

[0341] Optionally, the NEF instructs the first terminal to authorize participation in the perception service based on the third information, and sends a fourth request to the UDM.

[0342] Optionally, the NEF instructs the first terminal to agree to open the second information based on the third information, and sends a fourth request to the first network function.

[0343] Optionally, the NEF instructs the first terminal to agree to open the second information based on the third information, and sends a fourth request to the second network function.

[0344] Optionally, the NEF instructs the first terminal to agree to release the second information based on the third information, and sends a fourth request to the UDM.

[0345] Optionally, the NEF indicates that the first terminal can assume the role associated with the first request based on the third information, and sends a fourth request to the first network function.

[0346] Optionally, the NEF indicates that the first terminal can assume the role associated with the first request based on the third information, and sends a fourth request to the second network function.

[0347] Optionally, the NEF indicates that the first terminal can assume the role associated with the first request based on the third information, and sends a fourth request to the UDM.

[0348] Optionally, the NEF indicates to the first terminal not to authorize participation in the perception service based on the third information, and determines not to send the fourth request to the second network function.

[0349] Optionally, the NEF indicates to the first terminal not to authorize participation in the perception service based on the third information, and determines not to send the fourth request to the UDM.

[0350] Optionally, the NEF indicates that the first terminal does not agree to open the second information based on the third information, and determines not to send the fourth request to the first network function.

[0351] Optionally, the NEF indicates that the first terminal does not agree to open the second information based on the third information, and determines not to send the fourth request to the second network function.

[0352] Optionally, the NEF indicates that the first terminal does not agree to release the second information based on the third information, and determines not to send the fourth request to the UDM.

[0353] Optionally, the NEF determines not to send the fourth request to the first network function based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0354] Optionally, the NEF determines not to send the fourth request to the second network function based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0355] Optionally, the NEF determines not to send the fourth request to the UDM based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0356] In some embodiments, the fourth request is a perception-related request. Optionally, the fourth request is the same as the first request. Optionally, the fourth request is different from the first request. Optionally, the fourth request has at least partially the same functionality as the first request and / or carries at least partially the same information.

[0357] In some embodiments, the fourth request includes the first identification and / or role information.

[0358] In some embodiments, the fourth request is used to request a perception result related to the first terminal.

[0359] In some embodiments, the fourth request is used to request first information of the first terminal.

[0360] In some embodiments, the fourth request is used for the first network function and / or the second network function to perform the perception service of the first terminal, or the fourth request is used to trigger the perception service, or the fourth request is used to trigger the first network function and / or the second network function to perform the perception service of the first terminal.

[0361] In some embodiments, the name of the fourth request is not limited, and it can be, for example, a perception request, a perception result request, a perception service request, etc.

[0362] In some embodiments, the NEF determines to send a response message to the first device based on the third information, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0363] In some embodiments, the NEF ends the perception-related process based on the third information.

[0364] Step S2106B: The first network function performs a first operation.

[0365] In some embodiments, executing the first operation includes at least one of the following: executing a perception service related to the first terminal, determining whether the first terminal is authorized to participate in the perception service, determining whether to open the first information of the first terminal, determining whether to open the perception result related to the first terminal, sending a fifth request or not sending the fifth request, sending a response message, and ending the perception-related process.

[0366] In some embodiments, the first network function executes a sensing service related to the first terminal based on the request. Optionally, the request includes at least one of the following: a first request, a fourth request, and a sixth request.

[0367] Optionally, the sixth request is a perception-related request. Optionally, the sixth request is the same as the first request. Optionally, the sixth request is different from the first request. Optionally, the sixth request has at least partially the same functionality as the first request and / or carries at least partially the same information.

[0368] Optionally, the sixth request includes the first identifier and / or role information.

[0369] Optionally, the sixth request is used to request a perception result related to the first terminal.

[0370] Optionally, the sixth request is used to request first information of the first terminal.

[0371] Optionally, the sixth request is used for the first network function and / or the second network function to perform the perception service of the first terminal, or the sixth request is used to trigger the perception service, or the sixth request is used to trigger the first network function and / or the second network function to perform the perception service of the first terminal.

[0372] Optionally, the name of the sixth request is not limited, and it can be, for example, a perception request, a perception result request, a perception service request, etc.

[0373] Optionally, the first network function executes a perception service related to the first terminal based on the first request sent by the first device. Optionally, the first network function executes a perception service related to the first terminal based on a fourth request sent by the NEF. Optionally, the first network function executes a perception service related to the first terminal based on a sixth request sent by the UDM. Here, after receiving the request, the first network function may directly trigger the execution of the perception service related to the first terminal.

[0374] In some embodiments, the first network function determines whether to execute a perception service related to the first terminal based on the fourth information.

[0375] Optionally, the first network function instructs the first terminal to authorize participation in the perception service based on the fourth information, and executes the perception service related to the first terminal.

[0376] Optionally, the first network function agrees to open the second information of the first terminal based on the fourth information indication, and performs the perception service related to the first terminal.

[0377] Optionally, the first network function indicates to the first terminal based on the fourth information that it can assume the role associated with the first request and perform the perception service related to the first terminal.

[0378] Optionally, the first network function indicates to the first terminal based on the fourth information that the first terminal is not authorized to participate in the perception service, and determines not to execute the perception service related to the first terminal.

[0379] Optionally, the first network function determines not to execute the perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened.

[0380] Optionally, the first network function determines not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal cannot assume the role associated with the first request.

[0381] In some embodiments, the first network function determines whether to execute the first terminal-related awareness service based on the third information. Optionally, the first network function executes the first terminal-related awareness service based on the third information.

[0382] Optionally, the first network function instructs the first terminal to authorize participation in the perception service based on the third information, and executes the perception service related to the first terminal.

[0383] Optionally, the first network function agrees to open the second information of the first terminal based on the third information indication, and performs the perception service related to the first terminal.

[0384] Optionally, the first network function indicates to the first terminal based on the third information that it can assume the role associated with the first request and perform the perception service related to the first terminal.

[0385] Optionally, the first network function indicates to the first terminal not to authorize participation in the perception service based on the third information, and determines not to execute the perception service related to the first terminal.

[0386] Optionally, the first network function determines not to execute the perception service related to the first terminal based on the third information indicating that the second information of the first terminal is not agreed to be opened.

[0387] Optionally, the first network function determines not to execute the perception service related to the first terminal based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0388] In some embodiments, the first network function performing the first operation based on the third information may also be similar to the NEF performing the first operation based on the third information; the embodiment of the first network function performing the first operation based on the third information can refer to the embodiment of the NEF performing the first operation based on the third information.

[0389] In some embodiments, the first network function determines whether the first terminal is authorized to participate in the sensing service based on the third information.

[0390] In some embodiments, the first network function determines whether to agree to release the second information of the first terminal based on the third information.

[0391] In some embodiments, the first network function determines whether to approve the first terminal to assume the role of the first association request based on the third information.

[0392] In some embodiments, the first network function determines whether privacy verification is required based on the third information.

[0393] In some embodiments, the first network function determines whether to agree to send the third request to the first terminal based on the third information.

[0394] In some embodiments, the first network function determines whether to agree to open the perception result related to the first terminal based on the third information.

[0395] In some embodiments, the first network function performs privacy verification based on the third information indication.

[0396] In some embodiments, the first network function sends the fifth request, or the NEF determines not to send the fifth request. Here, the NEF may directly send the fifth request.

[0397] Optionally, the first network function sends a fifth request to the second network function. Optionally, the second network function receives the fifth request sent by the first network function.

[0398] Optionally, the first network function sends a fifth request to the UDM. Optionally, the UDM sends a fifth request to the first network function.

[0399] In some embodiments, the first network function determines whether to send the fifth request based on the third information.

[0400] Optionally, the first network function instructs the first terminal to authorize participation in the perception service based on the third information, and sends a fifth request to the UDM.

[0401] Optionally, the first network function instructs the first terminal to agree to open the second information based on the third information, and sends a fifth request to the UDM.

[0402] Optionally, the first network function indicates that the first terminal can assume the role associated with the first request based on the third information, and sends a fifth request to the UDM.

[0403] Optionally, the first network function indicates to the first terminal not to authorize participation in the perception service based on the third information, and determines not to send the fifth request to the UDM.

[0404] Optionally, the first network function instructs the first terminal not to authorize participation in the perception service based on the third information, and determines not to send the fifth request to the second network function;

[0405] Optionally, the first network function determines not to send the fifth request to the UDM based on the third information indicating that the first terminal does not agree to open the second information.

[0406] Optionally, the first network function indicates that the first terminal does not agree to open the second information based on the third information, and determines not to send the fifth request to the second network function;

[0407] Optionally, the first network function determines not to send the fifth request to the UDM based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0408] Optionally, the first network function determines not to send the fifth request to the second network function based on the third information indicating that the first terminal does not agree to open the second information.

[0409] In some embodiments, the fifth request is a perception-related request. Optionally, the fifth request is the same as the first request. Optionally, the fifth request is different from the first request. Optionally, the fifth request has at least partially the same functionality as the first request and / or carries at least partially the same information.

[0410] In some embodiments, the fifth request includes the first identification and / or role information.

[0411] In some embodiments, the fifth request is used to request a perception result related to the first terminal.

[0412] In some embodiments, the fifth request is used to request first information of the first terminal.

[0413] In some embodiments, the fifth request is used for the first network function and / or the second network function to perform the perception service of the first terminal, or the fifth request is used to trigger the perception service, or the fifth request is used to trigger the first network function and / or the second network function to perform the perception service of the first terminal.

[0414] In some embodiments, the name of the fifth request is not limited, and it can be, for example, a perception request, a perception result request, a perception service request, etc.

[0415] In some embodiments, the first network function determines to send a response message to the first device based on the third information, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0416] In some embodiments, the first network function ends the perception-related process based on the third information.

[0417] Step S2106C: The second network function performs the first operation.

[0418] In some embodiments, executing the first operation includes at least one of the following: executing a perception service related to the first terminal, determining whether the first terminal is authorized to participate in the perception service, determining whether to open the first information of the first terminal, determining whether to open the perception result related to the first terminal, sending the seventh request or not sending the seventh request, sending a response message, and ending the perception-related process.

[0419] In some embodiments, the second network function performing the first operation may also be similar to the second network function performing the first operation; the embodiment of the second network function performing the first operation may refer to the embodiment of the first network function performing the first operation.

[0420] In some embodiments, the second network function performs a sensing service related to the first terminal based on the request. Optionally, the request includes at least one of the following: a first request, a fourth request, and a sixth request.

[0421] Optionally, the second network function executes the perception service related to the first terminal based on the first request sent by the first device. Optionally, the second network function executes the perception service related to the first terminal based on the fourth request sent by the NEF. Optionally, the second network function executes the perception service related to the first terminal based on the sixth request sent by the UDM. Here, after receiving the request, the second network function can directly trigger the execution of the perception service related to the first terminal.

[0422] In some embodiments, the second network function determines whether to execute the awareness service related to the first terminal based on the fourth information.

[0423] Optionally, the second network function instructs the first terminal to authorize participation in the perception service based on the fourth information, and executes the perception service related to the first terminal.

[0424] Optionally, the second network function agrees to open the second information of the first terminal based on the fourth information indication, and performs the perception service related to the first terminal.

[0425] Optionally, the second network function indicates to the first terminal based on the fourth information that it can assume the role associated with the first request and perform the perception service related to the first terminal.

[0426] Optionally, the second network function indicates to the first terminal based on the fourth information that the first terminal is not authorized to participate in the perception service, and determines not to execute the perception service related to the first terminal.

[0427] Optionally, the second network function determines not to execute the perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened.

[0428] Optionally, the second network function determines not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal cannot assume the role associated with the first request.

[0429] In some embodiments, the second network function performs a sensing service related to the first terminal based on the third information. Optionally, the second network function performs a sensing service related to the first terminal based on the third information.

[0430] Optionally, the second network function instructs the first terminal to authorize participation in the perception service based on the third information, and executes the perception service related to the first terminal.

[0431] Optionally, the second network function instructs the first terminal to agree to open the second information based on the third information, and to perform a perception service related to the first terminal.

[0432] Optionally, the second network function indicates to the first terminal based on the third information that it can assume the role associated with the first request and perform the perception service related to the first terminal.

[0433] Optionally, the second network function indicates to the first terminal based on the third information that the first terminal is not authorized to participate in the perception service, and determines not to execute the perception service related to the first terminal.

[0434] Optionally, the second network function indicates to the first terminal based on the third information that the first terminal does not agree to open the second information, and determines not to execute the perception service related to the first terminal.

[0435] Optionally, the second network function determines not to execute the perception service related to the first terminal based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0436] In some embodiments, the second network function determines, based on the third information, whether the first terminal is authorized to participate in the sensing service;

[0437] In some embodiments, the second network function determines whether to agree to release the second information of the first terminal based on the third information;

[0438] In some embodiments, the second network function determines whether to agree to open the perception result related to the first terminal based on the third information;

[0439] In some embodiments, the second network function determines, based on the third information, whether to approve the first terminal to assume the role of the first requested association;

[0440] In some embodiments, the second network function determines whether to agree to send the third request to the first terminal based on the third information.

[0441] In some embodiments, the second network function determines whether to agree to open the perception result related to the first terminal based on the third information.

[0442] In some embodiments, the second network function sends a seventh request to the UDM. Optionally, the UDM receives the seventh request sent by the second network function.

[0443] In some embodiments, the second network function determines whether to send the seventh request based on the third information.

[0444] Optionally, the second network function instructs the first terminal to authorize participation in the perception service based on the third information, and sends a seventh request to the UDM.

[0445] Optionally, the second network function instructs the first terminal to agree to open the second information based on the third information, and sends a seventh request to the UDM.

[0446] Optionally, the second network function indicates that the first terminal can assume the role associated with the first request based on the third information, and sends a seventh request to the UDM.

[0447] Optionally, the second network function indicates to the first terminal not to authorize participation in the perception service based on the third information, and determines not to send the seventh request to the UDM.

[0448] Optionally, the second network function determines not to send the seventh request to the UDM based on the third information indicating that the first terminal does not agree to open the second information.

[0449] Optionally, the second network function determines not to send the seventh request to the UDM based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0450] In some embodiments, the seventh request is a perception-related request. Optionally, the seventh request is the same as the first request. Optionally, the seventh request is different from the first request. Optionally, the seventh request has at least partially the same functionality as the first request and / or carries at least partially the same information.

[0451] In some embodiments, the seventh request includes the first identification and / or role information.

[0452] In some embodiments, the seventh request is used to request a perception result related to the first terminal.

[0453] In some embodiments, the seventh request is used to request first information of the first terminal.

[0454] In some embodiments, the seventh request is used for the first network function and / or the second network function to perform the perception service of the first terminal, or the seventh request is used to trigger the perception service, or the seventh request is used to trigger the first network function and / or the second network function to perform the perception service of the first terminal.

[0455] In some embodiments, the name of the seventh request is not limited, and it can be, for example, a perception request, a perception result request, a perception service request, etc.

[0456] In some embodiments, the second network function determines to send a response message to the first device based on the third information, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0457] In some embodiments, the second network function ends the perception-related process based on the third information.

[0458] In step S2106D, the UDM performs the first operation.

[0459] In some embodiments, performing the first operation includes at least one of: determining third information of the first terminal, and sending or not sending the sixth request.

[0460] In some embodiments, the UDM determines the third information of the first terminal from the third information of at least one terminal based on the first identifier. Optionally, the terminal includes the first terminal and / or the third terminal. The third terminal can be any terminal, a terminal other than the first terminal, or a predetermined terminal.

[0461] In some embodiments, the UDM determines the first information of the first terminal from the first information of at least one terminal based on the first identifier.

[0462] In some embodiments, the UDM sends a sixth request to the first network function and / or the second network function. Optionally, the sixth request is used to trigger the first network function and / or the second network function to perform a sensing service related to the first terminal.

[0463] In some embodiments, the UDM determines whether to send the sixth information based on the third information. Optionally, the UDM determines not to send the sixth request to the first network function and / or the second network function based on the third information.

[0464] In some embodiments, step S2106 includes the above-mentioned step S2106A, step S2106B, step S2106C and / or step S2106D.

[0465] In some optional embodiments, the first terminal sends the first information to the UDM. Optionally, the UDM receives the first information sent by the first terminal.

[0466] Optionally, at least one terminal sends the first information to the UDM, wherein the terminal includes the first terminal and / or at least one third terminal, and the third terminal is a terminal other than the first terminal, or an arbitrary terminal, or a predetermined terminal.

[0467] Optionally, the UDM receives first information sent by at least one terminal.

[0468] In some optional embodiments, the UDM stores at least one terminal and the first information of the terminal in correspondence.

[0469] In some optional embodiments, the UDM stores at least one terminal and the third information of the terminal in correspondence.

[0470] In some optional embodiments, the UDM determines the third information and / or the first information of the first terminal based on the request. Optionally, the request includes a first request sent by the first device, a fourth request sent by the NEF, a fifth request sent by the first network function, and / or a seventh request sent by the second network function.

[0471] Step S2107A: UDM sends the first information to NEF.

[0472] In some embodiments, the NEF receives the first information sent by the UDM.

[0473] In some embodiments, the UDM sends the first information to the NEF based on the third information. Optionally, the UDM sends the first information to the NEF based on the third information indicating that the first information of the first terminal is agreed to be opened.

[0474] Optionally, the UDM determines, based on the third information, that it agrees to open the second information of the first terminal, and sends the second information to the NEF.

[0475] Optionally, the UDM determines, based on the third information, that it does not agree to open the second information of the first terminal, and determines not to send the second information to the first network function.

[0476] Optionally, the UDM determines, based on the third information, that it agrees to open the perception result related to the first terminal, and sends the perception result to the NEF.

[0477] Optionally, the UDM determines, based on the third information, that it does not agree to open the perception result related to the first terminal, and determines not to send the perception result to the first network function.

[0478] In some embodiments, the UDM sends the first information to the second network function; and the second network function sends the first information to the NEF.

[0479] In some embodiments, the UDM sends the first information to the first network function; and the first network function sends the first information to the NEF.

[0480] In some embodiments, the UDM sends the first information to the second network function; the second network function sends the first information to the first network function; and the first network function sends the first information to the NEF.

[0481] Optionally, the second network function directly sends the first information to the first network function.

[0482] Optionally, the second network function determines, based on the third information, that it agrees to open the second information of the first terminal, and sends the second information to the first network function.

[0483] Optionally, the second network function determines, based on the third information, that it does not agree to open the second information of the first terminal, and determines not to send the second information to the first network function.

[0484] Optionally, the first network function sends the first information directly to the NEF or the first device.

[0485] Optionally, the first network function determines, based on the third information, that it agrees to open the second information of the first terminal, and sends the second information to the first device or the NEF.

[0486] Optionally, the first network function determines, based on the third information, that it does not agree to open the second information of the first terminal, and determines not to send the second information to the first device or the NEF.

[0487] Optionally, the NEF sends first information to the first device.

[0488] Optionally, the NEF determines, based on the third information, that it agrees to open the second information of the first terminal, and sends the second information to the first device;

[0489] Optionally, the NEF determines, based on the third information, that it does not agree to open the second information of the first terminal, and determines not to send the second information to the first device.

[0490] In some optional embodiments, when the first terminal is authorized to participate in the sensing service, the NEF determines whether to agree to release the second information of the first terminal based on the third information.

[0491] In some optional embodiments, when the first terminal is authorized to participate in the sensing service, the NEF determines whether to agree to release the sensing result related to the first terminal based on the third information.

[0492] Step S2107B: The UDM sends the first information to the first network function.

[0493] In some embodiments, the first network function receives the first information sent by the UDM.

[0494] In some embodiments, the UDM sends the first information to the first network function based on the third information. Optionally, the UDM sends the first information to the first network function based on the third information indicating consent to open the first information of the first terminal.

[0495] Step S2107C: The UDM sends the first information to the second network function.

[0496] In some embodiments, the second network function receives the first information sent by the UDM.

[0497] In some embodiments, the UDM sends the first information to the second network function based on the third information. Optionally, the UDM determines that the first information of the first terminal is approved to be opened based on the third information, and sends the first information to the second network function.

[0498] Step S2107D: The UDM sends the first information to the first device.

[0499] In some embodiments, the first device receives the first information sent by the UDM.

[0500] In some embodiments, the UDM sends the first information to the first device based on the third information. Alternatively, the UDM determines based on the third information that the first information of the first terminal is approved to be opened, and sends the first information to the first device.

[0501] Step S2107E: The UDM sends the first information to the first device through the NEF.

[0502] In some embodiments, the first device receives the first information sent by the UDM through the NEF.

[0503] In some embodiments, the UDM sends the first information to the first device via the NEF based on the third information. Alternatively, the UDM determines to agree to open the first information of the first terminal based on the third information, and sends the first information to the first device via the NEF.

[0504] In some embodiments, step S2107 includes step S2107A, step S2107B, step S2107C, step S2107D and / or step S2107E.

[0505] In some optional embodiments, the first terminal sends the first information or the second information to the NFE, the first network function, and / or the second network function. Optionally, after the NEF obtains the first information or the second information, it may send the first information or the second information to the first device. Optionally, after the first network function obtains the first information or the second information, it may send the first information or the second information to the NEF and / or the first device. Optionally, after the second network function obtains the first information or the second information, it may send the first information or the second information to the first network function, the NEF, and / or the first device.

[0506] In some optional embodiments, the first terminal sends the first information or the second information to the UDM. The UDM may store the first information or the second information of at least one terminal; the terminal may include the first terminal and / or any terminal. After obtaining the first information or the second information, the UDM may send the first information or the second information to the first network function, the second network function, the NEF, and / or the first device.

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

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

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

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

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

[0512] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment; step S2103 can be implemented as an independent embodiment; step S2104 can be implemented as an independent embodiment; step S2105 can be implemented as an independent embodiment; step S2106 can be implemented as an independent embodiment; step S2107 can be implemented as an independent embodiment; the combination of step S2101 and step S2102 can be implemented as an independent embodiment; the combination of step S2102 and step S2103 can be implemented as an independent embodiment; the combination of step S2101, step S2102 and step S2103 can be implemented as an independent embodiment; step S2104 can be implemented as an independent embodiment; step S2105 can be implemented as an independent embodiment; step S2106 can be implemented as an independent embodiment; step S2107 can be implemented as an independent embodiment; the combination of step S2101 and step S2102 can be implemented as an independent embodiment; the combination of step S2101, step S2102 and step S2103 can be implemented as an independent embodiment; The combination of step 104 and step S2105 can be implemented as an independent embodiment; step S2102 and step S2103 and step S2104 and step S2105 can be implemented as independent embodiments; steps S2101 to step S2105 can be implemented as independent embodiments; step S2105 and step S2106 can be implemented as independent embodiments; step S2106 and step S2107 can be implemented as independent embodiments; step S2105 and step S2106 and step S2107 can be implemented as independent embodiments; step S2101 and step S2107 can be implemented as independent embodiments; steps S2101 to step S2107 can be implemented as independent embodiments.

[0513] In some embodiments, step S2102, step S2103, step S2104, step S2105, step S2106, and step S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0514] In some embodiments, step S2102, step S2103, step S2104, step S2105, and step S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0515] In some embodiments, step S2101, step S2102, step S2103, step S2106, and step S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0516] In some embodiments, step S2101, step S2104, step S2105, step S2106, and step S2107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0517] In the embodiments of the present disclosure, each embodiment can be implemented individually or in combination with each other, and the steps in each embodiment can be distinguished in order.

[0518] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to an information processing method, which is executed by a first device and includes:

[0519] Step S3101, sending a first request.

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

[0521] In some embodiments, the first device sends the first request to the NEF, but is not limited thereto and may also send the first request to other entities.

[0522] Optionally, the first device sends a first request to the first network function.

[0523] Optionally, the first device sends a first request to the UDM.

[0524] Optionally, the first device sends the first request to the first network function through the NEF.

[0525] Optionally, the first device sends the first request to the UDM through the NEF.

[0526] Step S3102, obtaining first information.

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

[0528] In some embodiments, the first device receives the first information sent by the UDM, but is not limited thereto and may also receive the first information sent by other entities.

[0529] In some embodiments, the first device obtains first information specified by the protocol.

[0530] In some embodiments, the first device obtains the first information from an upper layer(s).

[0531] In some embodiments, the first device performs processing to obtain the first information.

[0532] In some embodiments, step S3102 is omitted, and the first device autonomously implements the function indicated by the first information, or the above function is default or by default.

[0533] Optionally, the first device receives first information sent by the NEF.

[0534] Optionally, the first device receives the first information sent by the UDM through the NEF.

[0535] Optionally, the first device receives first information sent by the UDM.

[0536] Optionally, the first device receives first information sent by the first network function.

[0537] Optionally, the first device receives first information sent by the second network function.

[0538] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, or a combination of step S3101 and step S3102 may be implemented as an independent embodiment.

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

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

[0541] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to an information processing method, which is executed by a first device and includes:

[0542] Step S3201, sending a first request.

[0543] The optional implementation of step S3201 can be found in step S2101 in FIG. 2 , or the optional implementation of step S3101 in FIG. 3A , and other related parts in the embodiments involved in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0544] In some embodiments, the first request is a perception-related request.

[0545] In some embodiments, the first request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0546] In some embodiments, sending the first request includes at least one of: sending the first request to the NEF; sending the first request to the first network function; sending the first request to the first network function through the NEF; sending the first request to the UDM; and sending the first request to the UDM through the NEF.

[0547] In some embodiments, the method further includes: receiving first information, wherein the first information includes the perception result and / or the second information.

[0548] In some embodiments, receiving the first information includes at least one of the following: receiving the first information sent by the NEF; receiving the first information sent by the first network function through the NEF; receiving the first information sent by the first network function; receiving the first information sent by the second network function through the NEF; receiving the first information sent by the UDM; and receiving the first information sent by the UDM through the NEF.

[0549] In some embodiments, the first device includes at least one of the following: AF, a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: AMF, GMLC, LMF, and a network function related to perception; and / or, the second network function includes at least one of the following: AMF, LMF, and a network function related to perception.

[0550] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 3A , which will not be described in detail here.

[0551] FIG4A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to an information processing method, which is executed by NEF and includes:

[0552] Step S4101, obtain the first request.

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

[0554] In some embodiments, the NEF receives the first request sent by the first device, but is not limited thereto and may also receive the first request sent by other entities.

[0555] In some embodiments, the NEF obtains a first request specified by the protocol.

[0556] In some embodiments, the NEF obtains the first request from upper layer(s).

[0557] In some embodiments, the NEF performs processing to obtain the first request.

[0558] In some embodiments, step S4101 is omitted, and the NEF autonomously implements the function indicated by the first request, or the above function is default or by default.

[0559] Step S4102: Send a second request.

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

[0561] In some embodiments, the NEF sends the second request to the UDM, but is not limited thereto and may also send the second request to other entities.

[0562] Step S4103, obtain third information.

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

[0564] In some embodiments, the NEF receives the third information sent by the UDM, but is not limited thereto and may also receive the third information sent by other entities.

[0565] In some embodiments, the NEF obtains third information specified by the protocol.

[0566] In some embodiments, the NEF obtains the third information from upper layer(s).

[0567] In some embodiments, the NEF performs processing to obtain the third information.

[0568] In some embodiments, step S4103 is omitted, and the NEF autonomously implements the function indicated by the third information, or the above function is default or by default.

[0569] Step S4104, perform the first operation.

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

[0571] Step S4105, obtaining first information.

[0572] The optional implementation of step S4105 can refer to the optional implementation of step S2107A and / or step S2107E in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0573] In some embodiments, the NEF receives the first information sent by the UDM, but is not limited thereto and may also receive the first information sent by other entities.

[0574] In some embodiments, the NEF obtains first information specified by the protocol.

[0575] In some embodiments, the NEF obtains the first information from upper layer(s).

[0576] In some embodiments, the NEF performs processing to obtain the first information.

[0577] In some embodiments, step S4105 is omitted, and the NEF autonomously implements the function indicated by the first information, or the above function is default or by default.

[0578] In some optional embodiments, the NEF sends the first information to the first device.

[0579] In some optional embodiments, the NEF receives first information sent by a first network function, where the first information is obtained by the first network function from the first terminal.

[0580] The information processing method involved in the embodiment of the present disclosure may include at least one of steps S4101 to S4105. For example, step S4101 can be implemented as an independent embodiment, step S4102 can be implemented as an independent embodiment; step S4103 can be implemented as an independent embodiment; step S4104 can be implemented as an independent embodiment; step S4105 can be implemented as an independent embodiment; the combination of step S4101 and step S4102 can be implemented as an independent embodiment; the combination of step S4102 and step S4103 can be implemented as an independent embodiment; the combination of step S4101, step S4102 and step S4103 can be implemented as an independent embodiment; step S4103 and step S4104 can be implemented as independent embodiments; step S4104 and step S4105 can be implemented as independent embodiments; step S4103, step S4104 and step S4105 can be implemented as independent embodiments; steps S4101 to S4105 can be implemented as independent embodiments.

[0581] In some embodiments, step S4102, step S4103, step S4104, and step S4105 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0583] In some embodiments, step S4101, step S4102, step S4103, and step S4105 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0584] FIG4B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to an information processing method, which is executed by NEF and includes:

[0585] Step S4201, receiving a first request.

[0586] The optional implementation of step S4201 can be found in step S2101A and / or step S2101C in Figure 2, or the optional implementation of step S4101 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0587] In some embodiments, receiving the first request includes: receiving the first request sent by the first device, wherein the first request is a perception-related request.

[0588] In some embodiments, the first request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0589] In some embodiments, the method also includes: obtaining third information, wherein the third information is used to indicate at least one of the following: a first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether the second information of the first terminal is agreed to be opened; and whether privacy verification is required.

[0590] In some embodiments, obtaining the third information includes: sending a second request to the unified data management (UDM), where the second request is used to request the third information; and receiving the third information sent by the UDM.

[0591] In some embodiments, the second request includes at least one first identification.

[0592] In some embodiments, the method also includes at least one of the following: based on the third information, determining whether the first terminal is authorized to participate in the perception service; based on the third information, determining whether to agree to open the second information of the first terminal; based on the third information, determining whether to agree to the first terminal to assume the role associated with the first request; and based on the third information, determining whether to agree to send a third request to the first terminal.

[0593] In some embodiments, the NEF triggers the second network function to perform privacy verification with the first terminal based on the third information indicating that privacy verification is required. Exemplarily, the NEF triggers the second network function to send a third request to the first terminal so that the second network function obtains the fourth information of the first terminal.

[0594] In some embodiments, the method includes at least one of: sending a fourth request to the first network function; wherein the fourth request is a perception-related request; the fourth request includes the first identification and / or role information; sending the fourth request to the second network function; and sending the fourth request to the UDM.

[0595] In some embodiments, the method includes at least one of the following: based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fourth request to the first network function, wherein the fourth request is a perception-related request; the fourth request includes a first identifier and / or role information; based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fourth request to the second network function; based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fourth request to the UDM; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fourth request to the first network function; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fourth request to the second network function; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fourth request to the UDM; based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fourth request to the first network function; based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fourth request to the second network function; and based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fourth request to the UDM.

[0596] In some embodiments, the method further includes: determining, based on the third information, to send a response message to the first device, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0597] In some embodiments, the method further includes: ending the perception-related process based on the third information.

[0598] In some embodiments, the method further includes at least one of: receiving first information sent by a first network function; wherein the first information includes a perception result and / or second information; receiving first information sent by a second network function; and receiving first information sent by a UDM.

[0599] In some embodiments, the method also includes at least one of the following: when the first terminal is authorized to participate in the perception service, determining whether to agree to open the second information of the first terminal based on the third information; and when the first terminal is authorized to participate in the perception service, determining whether to agree to open the perception results related to the first terminal based on the third information.

[0600] In some embodiments, the method also includes at least one of the following: determining based on the third information that the second information of the first terminal is agreed to be opened, and sending the second information to the first device; determining based on the third information that the second information of the first terminal is not agreed to be opened, and determining not to send the second information to the first device; determining based on the third information that the perception result related to the first terminal is agreed to be opened, and sending the perception result to the first device; and determining based on the third information that the perception result related to the first terminal is not agreed to be opened, and determining not to send the perception result to the first device.

[0601] In some embodiments, the first device includes at least one of the following: AF, a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: AMF, GMLC, LMF, and a network function related to perception; and / or, the second network function includes at least one of the following: AMF, LMF, and a network function related to perception.

[0602] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0603] FIG4C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4C , the present disclosure embodiment relates to an information processing method, which is executed by NEF and includes:

[0604] Step S4301, perform the first operation.

[0605] The optional implementation of step S4301 can be found in step S2106A in FIG. 2 , or the optional implementation of step S4104 in FIG. 4A , and other related parts in the embodiments involved in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0606] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 4A , which will not be described in detail here.

[0607] FIG5A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG5A , the present disclosure embodiment relates to an information processing method, which is executed by a first network function, and the method includes:

[0608] Step S5101, obtain request.

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

[0610] In some embodiments, the first network function receives a request sent by the first device, but is not limited thereto and may also receive a request sent by other entities.

[0611] In some embodiments, the first network function obtains a request specified by a protocol.

[0612] In some embodiments, the first network function obtains the request from upper layer(s).

[0613] In some embodiments, the first network function performs processing to obtain the request.

[0614] In some embodiments, step S5101 is omitted, and the first network function autonomously implements the function indicated by the request, or the above function is default or by default.

[0615] Optionally, the request may be the first request, the fourth request and / or the sixth request.

[0616] Step S5102: Send a second request.

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

[0618] In some embodiments, the first network function sends the second request to the UDM, but is not limited thereto and may also send the second request to other entities.

[0619] Step S5103, obtain third information.

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

[0621] In some embodiments, the first network function receives the third information sent by the UDM, but is not limited thereto and may also receive the third information sent by other entities.

[0622] In some embodiments, the first network function obtains third information specified by the protocol.

[0623] In some embodiments, the first network function obtains the third information from an upper layer(s).

[0624] In some embodiments, the first network function performs processing to obtain the third information.

[0625] In some embodiments, step S5103 is omitted, and the first network function autonomously implements the function indicated by the third information, or the above function is default or by default.

[0626] Step S5104: Send a third request.

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

[0628] In some embodiments, the first network function sends the third request to the first terminal, but is not limited thereto, and the third request may also be sent to other entities.

[0629] Step S5105, obtain the fourth information.

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

[0631] In some embodiments, the first network function receives the fourth information sent by the first terminal, but is not limited thereto, and may also receive the fourth information sent by other entities.

[0632] In some embodiments, the first network function obtains fourth information specified by the protocol.

[0633] In some embodiments, the first network function obtains the fourth information from an upper layer(s).

[0634] In some embodiments, the first network function performs processing to obtain the fourth information.

[0635] In some embodiments, step S5105 is omitted, and the first network function autonomously implements the function indicated by the fourth information, or the above function is default or by default.

[0636] Step S5106, execute the first operation.

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

[0638] Step S5107, obtain first information.

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

[0640] In some embodiments, the first network function receives the first information sent by the UDM, but is not limited thereto and may also receive the first information sent by other entities.

[0641] In some embodiments, the first network function obtains first information specified by the protocol.

[0642] In some embodiments, the first network function obtains the first information from an upper layer(s).

[0643] In some embodiments, the first network function performs processing to obtain the first information.

[0644] In some embodiments, step S5107 is omitted, the first network function autonomously implements the function indicated by the first information, or the above function is default or by default.

[0645] In some optional embodiments, the first network function receives first information sent by the first terminal.

[0646] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5107. For example, step S5101 can be implemented as an independent embodiment, step S5102 can be implemented as an independent embodiment; step S5103 can be implemented as an independent embodiment; step S5104 can be implemented as an independent embodiment; step S5105 can be implemented as an independent embodiment; step S5106 can be implemented as an independent embodiment; step S5107 can be implemented as an independent embodiment; the combination of step S5101 and step S5102 can be implemented as an independent embodiment; the combination of step S5102 and step S5103 can be implemented as an independent embodiment; the combination of step S5101, step S5102 and step S5103 can be implemented as an independent embodiment; step S5104 can be implemented as an independent embodiment; step S5105 can be implemented as an independent embodiment; step S5106 can be implemented as an independent embodiment; step S5107 can be implemented as an independent embodiment; the combination of step S5101 and step S5102 can be implemented as an independent embodiment; the combination of step S5101, step S5102 and step S5103 can be implemented as an independent embodiment; The combination of step S5104 and step S5105 can be implemented as an independent embodiment; the combination of step S5102 and step S5103 and step S5104 and step S5105 can be implemented as an independent embodiment; steps S5101 to S5105 can be implemented as independent embodiments; step S5105 and step S5106 can be implemented as independent embodiments; step S5106 and step S5107 can be implemented as independent embodiments; step S5105 and step S5106 and step S5107 can be implemented as independent embodiments; step S5101 and step S5107 can be implemented as independent embodiments; steps S5101 to S5107 can be implemented as independent embodiments.

[0647] In some embodiments, step S5102, step S5103, step S5104, step S5105, step S5106, and step S5107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0648] In some embodiments, step S5102, step S5103, step S5104, step S5105, and step S5107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0649] In some embodiments, step S5101, step S5102, step S5103, step S5106, and step S5107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0650] In some embodiments, step S5101, step S5104, step S5105, step S5106, and step S5107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0651] FIG5B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG5B , the embodiment of the present disclosure relates to an information processing method, which is executed by a first network function, and the method includes:

[0652] Step S5201, receive a request.

[0653] The optional implementation of step S5201 can be found in step S2101B in FIG. 2 , or the optional implementation of step S5101 in FIG. 5A , and other related parts in the embodiments involved in FIG. 2 and FIG. 5A , which will not be described in detail here.

[0654] In some embodiments, the request is a perception-related request.

[0655] In some embodiments, the request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0656] In some embodiments, receiving the request includes at least one of: receiving a fourth request sent by the NEF; receiving a first request sent by the first device; and receiving a sixth request sent by the UDM.

[0657] In some embodiments, the method further includes at least one of the following: performing a sensing service related to the first terminal based on the request.

[0658] In some embodiments, the method further includes: sending a third request to the first terminal, wherein the third request is used to request fourth information; and receiving the fourth information sent by the first terminal.

[0659] In some embodiments, the fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service; whether to agree to open the second information of the first terminal; and whether to agree to assume the role of the first request for association.

[0660] In some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened; and determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal cannot assume the role associated with the first request.

[0661] In some embodiments, the method also includes: obtaining third information, wherein the third information is used to indicate at least one of the following: a first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether the second information of the first terminal is agreed to be opened; and whether privacy verification is required.

[0662] In some embodiments, obtaining the third information includes: sending a second request to a unified data management (UDM), where the second request is used to request the third information; and receiving the third information sent by the UDM.

[0663] In some embodiments, the second request includes at least one first identification.

[0664] In some embodiments, the method further includes: performing a perception service related to the first terminal based on the third information.

[0665] In some embodiments, the method also includes at least one of the following: based on the third information, determining whether the first terminal is authorized to participate in the perception service; based on the third information, determining whether to agree to open the second information of the first terminal; based on the third information, determining whether to agree to the first terminal to assume the role associated with the first request; based on the third information, determining whether privacy verification is required; and based on the third information, determining whether to agree to send a third request to the first terminal.

[0666] In some embodiments, the first network function triggers the second network function to perform privacy verification with the first terminal based on the third information indicating that privacy verification is required. Exemplarily, the first network function triggers the second network function to send a third request to the first terminal, so that the second network function obtains the fourth information of the first terminal.

[0667] In some embodiments, the first network function performs privacy verification with the first terminal based on the third information indicating that privacy verification is required.

[0668] In some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal does not agree to open the second information; determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal cannot assume the role associated with the first request; and executing privacy verification based on the third information indication.

[0669] In some embodiments, the method includes at least one of: sending a fifth request to the second network function; wherein the fifth request is a request related to awareness; the fifth request includes the first identification and / or role information; and sending the fifth request to the UDM.

[0670] In some embodiments, the method also includes at least one of the following: based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fifth request to the UDM; wherein the fifth request is a perception-related request; the fifth request includes a first identifier and / or role information; based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fifth request to the second network function; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fifth request to the UDM; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fifth request to the second network function; based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the fifth request to the UDM; and based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the fifth request to the second network function.

[0671] In some embodiments, the method further includes: determining, based on the third information, to send a response message to the first device, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0672] In some embodiments, the method further includes: ending the perception-related process based on the third information.

[0673] In some embodiments, the method further includes at least one of: receiving first information sent by the second network function, wherein the first information includes the perception information and / or the second information; and receiving the first information sent by the UDM.

[0674] In some embodiments, the method also includes at least one of the following: sending first information to the NEF or the first device; determining based on the third information to agree to open the second information of the first terminal, and sending the second information to the first device or NEF; and determining based on the third information not to agree to open the second information of the first terminal, and determining not to send the second information to the first device or NEF.

[0675] In some embodiments, the first device includes at least one of the following: AF, a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: AMF, GMLC, LMF, and a network function related to perception; and / or, the second network function includes at least one of the following: AMF, LMF, and a network function related to perception.

[0676] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 5A , which will not be described in detail here.

[0677] Figure 5C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 5C, the embodiment of the present disclosure relates to an information processing method, which is executed by a first network function, and the method includes:

[0678] Step S5301, perform the first operation.

[0679] The optional implementation of step S5301 can be found in step S2106B in FIG. 2 , or the optional implementation of step S5106 in FIG. 5A , and other related parts in the embodiments involved in FIG. 2 and FIG. 5A , which will not be described in detail here.

[0680] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 5A , which will not be described in detail here.

[0681] FIG6A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG6A , the embodiment of the present disclosure relates to an information processing method, which is executed by a second network function, and the method includes:

[0682] Step S6101, obtain request.

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

[0684] In some embodiments, the second network function receives a request sent by the first device, but is not limited thereto and may also receive a request sent by other entities.

[0685] In some embodiments, the second network function obtains a request specified by a protocol.

[0686] In some embodiments, the second network function obtains the request from upper layer(s).

[0687] In some embodiments, the second network function performs processing resulting in the request.

[0688] In some embodiments, step S5101 is omitted, and the second network function autonomously implements the function indicated by the request, or the above function is default or by default.

[0689] Optionally, the request may be the first request, the fourth request and / or the sixth request.

[0690] Step S6102, sending a second request.

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

[0692] In some embodiments, the second network function sends the second request to the UDM, but is not limited thereto and may also send the second request to other entities.

[0693] Step S6103, obtain third information.

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

[0695] In some embodiments, the second network function receives the third information sent by the UDM, but is not limited thereto and may also receive the third information sent by other entities.

[0696] In some embodiments, the second network function obtains third information specified by the protocol.

[0697] In some embodiments, the second network function obtains the third information from an upper layer(s).

[0698] In some embodiments, the second network function performs processing to obtain the third information.

[0699] In some embodiments, step S6103 is omitted, and the second network function autonomously implements the function indicated by the third information, or the above function is default or by default.

[0700] Step S6104, sending a third request.

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

[0702] In some embodiments, the second network function sends the third request to the first terminal, but is not limited thereto, and the third request may also be sent to other entities.

[0703] Step S6105, obtain the fourth information.

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

[0705] In some embodiments, the second network function receives the fourth information sent by the first terminal, but is not limited thereto, and may also receive the fourth information sent by other entities.

[0706] In some embodiments, the second network function obtains fourth information specified by the protocol.

[0707] In some embodiments, the second network function obtains the fourth information from an upper layer(s).

[0708] In some embodiments, the second network function performs processing to obtain the fourth information.

[0709] In some embodiments, step S6105 is omitted, and the second network function autonomously implements the function indicated by the fourth information, or the above function is default or by default.

[0710] Step S6106, perform the first operation.

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

[0712] Step S6107, obtain first information.

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

[0714] In some embodiments, the second network function receives the first information sent by the UDM, but is not limited thereto and may also receive the first information sent by other entities.

[0715] In some embodiments, the second network function obtains the first information specified by the protocol.

[0716] In some embodiments, the second network function obtains the first information from an upper layer(s).

[0717] In some embodiments, the second network function performs processing to obtain the first information.

[0718] In some embodiments, step S6107 is omitted, and the second network function autonomously implements the function indicated by the first information, or the above function is default or by default.

[0719] In some optional embodiments, the second network function receives the first information sent by the first terminal.

[0720] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S6101 to S6107. For example, step S6101 can be implemented as an independent embodiment, step S6102 can be implemented as an independent embodiment; step S6103 can be implemented as an independent embodiment; step S6104 can be implemented as an independent embodiment; step S6105 can be implemented as an independent embodiment; step S6106 can be implemented as an independent embodiment; step S6107 can be implemented as an independent embodiment; the combination of step S6101 and step S6102 can be implemented as an independent embodiment; the combination of step S6102 and step S6103 can be implemented as an independent embodiment; the combination of step S6101, step S6102 and step S6103 can be implemented as an independent embodiment; step S6104 can be implemented as an independent embodiment; step S6105 can be implemented as an independent embodiment; step S6106 can be implemented as an independent embodiment; step S6107 can be implemented as an independent embodiment; the combination of step S6101 and step S6102 can be implemented as an independent embodiment; the combination of step S6101, step S6102 and step S6103 can be implemented as an independent embodiment; The combination of step S6104 and step S6105 can be implemented as an independent embodiment; the combination of step S6102 and step S6103 and step S6104 and step S6105 can be implemented as an independent embodiment; steps S6101 to S6105 can be implemented as independent embodiments; step S6105 and step S6106 can be implemented as independent embodiments; step S6106 and step S6107 can be implemented as independent embodiments; step S6105 and step S6106 and step S6107 can be implemented as independent embodiments; step S6101 and step S6107 can be implemented as independent embodiments; steps S6101 to S6107 can be implemented as independent embodiments.

[0721] In some embodiments, step S6102, step S6103, step S6104, step S6105, step S6106, and step S6107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0722] In some embodiments, step S6102, step S6103, step S6104, step S6105, and step S6107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0723] In some embodiments, step S6101, step S6102, step S6103, step S6106, and step S6107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0724] In some embodiments, step S6101, step S6104, step S6105, step S6106, and step S6107 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0725] FIG6B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG6B , the embodiment of the present disclosure relates to an information processing method, which is executed by a second network function, and the method includes:

[0726] Step S6201, receive a request.

[0727] The optional implementation of step S6201 can be found in step S2101F in FIG. 2 , or the optional implementation of step S6101 in FIG. 6A , and other related parts in the embodiments involved in FIG. 2 and FIG. 6A , which will not be described in detail here.

[0728] In some embodiments, the request is a perception-related request.

[0729] In some embodiments, the request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0730] In some embodiments, the method includes at least one of: receiving a first request sent by a first device; receiving a fourth request sent by a first network function; and receiving a sixth request sent by a UDM.

[0731] In some embodiments, the method further includes: executing a perception service related to the first terminal based on the request.

[0732] In some embodiments, the method further includes: sending a third request to the first terminal, wherein the third request is used to request fourth information; and receiving the fourth information sent by the first terminal.

[0733] In some embodiments, the fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service; whether to agree to open the second information of the first terminal; and whether to agree to assume the role of the first request for association.

[0734] In some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened; and determining not to execute the perception service related to the first terminal based on the fourth information indicating that the first terminal cannot assume the role associated with the first request.

[0735] In some embodiments, the method also includes: obtaining third information, wherein the third information is used to indicate at least one of the following: at least one first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0736] In some embodiments, obtaining the third information includes: sending a second request to a unified data manager (UDM), where the second request is used to request the third information; and receiving the third information sent by the UDM.

[0737] In some embodiments, the second request includes at least one first identification.

[0738] In some embodiments, the method further includes: performing a perception service related to the first terminal based on the third information.

[0739] In some embodiments, the method also includes at least one of the following: based on the third information, determining whether the first terminal is authorized to participate in the perception service; based on the third information, determining whether to agree to open the second information of the first terminal; based on the third information, determining whether to agree to open the perception results related to the first terminal; based on the third information, determining whether to agree to the first terminal to assume the role associated with the first request; and based on the third information, determining whether to agree to send a third request to the first terminal.

[0740] In some embodiments, the method also includes at least one of the following: determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal is not authorized to participate in the perception service; determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal does not agree to open the second information; and determining not to execute the perception service related to the first terminal based on the third information indicating that the first terminal cannot assume the role associated with the first request.

[0741] In some embodiments, the method further includes: sending a seventh request to the UDM, wherein the seventh request is a perception-related request; and the seventh request includes the first identifier and / or role information.

[0742] In some embodiments, the method also includes at least one of the following: based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the seventh request to the UDM; wherein the seventh request is a request related to perception; the seventh request includes the first identification and / or role information; based on the third information indicating that the first terminal does not agree to open the second information, determining not to send the seventh request to the UDM; and based on the third information indicating that the first terminal cannot assume the role associated with the first request, determining not to send the seventh request to the UDM.

[0743] In some embodiments, the method further includes: determining, based on the third information, to send a response message to the first device, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

[0744] In some embodiments, the method further includes: ending the perception-related process based on the third information.

[0745] In some embodiments, the method further includes: receiving first information sent by the UDM.

[0746] In some embodiments, the method further includes: determining based on the third information that the second information of the first terminal is agreed to be opened, and sending the second information to the first network function; or, determining based on the third information that the second information of the first terminal is not agreed to be opened, and determining not to send the second information to the first network function.

[0747] In some embodiments, the first device includes at least one of the following: AF, a client corresponding to the second terminal, and the second terminal; and / or, the first network function includes at least one of the following: AMF, GMLC, LMF, and a network function related to perception; and / or, the second network function includes at least one of the following: AMF, LMF, and a network function related to perception.

[0748] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 6A , which will not be described in detail here.

[0749] FIG6C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG6C , the embodiment of the present disclosure relates to an information processing method, which is executed by a second network function, and the method includes:

[0750] Step S6301, perform the first operation.

[0751] The optional implementation of step S6301 can be found in step S2106C in FIG. 2 , or the optional implementation of step S6106 in FIG. 6A , and other related parts in the embodiments involved in FIG. 2 and FIG. 6A , which will not be described in detail here.

[0752] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 6A , which will not be described in detail here.

[0753] FIG7A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG7A , the present disclosure embodiment relates to an information processing method, which is executed by the UDM, and the method includes:

[0754] Step S7101, obtain request.

[0755] The optional implementation of step S7101 can be found in the optional implementation of step S2101D and / or step S2101E and / or step S2101F in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0756] In some embodiments, the UDM receives a request sent by the first device, but is not limited thereto and may also receive a request sent by other entities.

[0757] In some embodiments, the UDM obtains requests specified by the protocol.

[0758] In some embodiments, the UDM obtains requests from upper layer(s).

[0759] In some embodiments, the UDM performs processing to obtain the request.

[0760] In some embodiments, step S7101 is omitted, and the UDM autonomously implements the function indicated by the request, or the above function is default or by default.

[0761] Optionally, the request is the first request, the fifth request and / or the seventh request.

[0762] Step S7102, obtain the second request.

[0763] The optional implementation of step S7102 can refer to the optional implementation of step S2102A and / or step S2102B and / or step S2102C in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0764] In some embodiments, the UDM receives the second request sent by the NEF, but is not limited thereto and may also receive the second request sent by other entities.

[0765] In some embodiments, the UDM obtains a second request specified by the protocol.

[0766] In some embodiments, the UDM obtains the second request from upper layer(s).

[0767] In some embodiments, the UDM performs processing to obtain the second request.

[0768] In some embodiments, step S7102 is omitted, and the UDM autonomously implements the function indicated by the second request, or the above function is default or by default.

[0769] Optionally, the UDM receives a second request sent by the first network function and / or the second network function.

[0770] Step S7103, sending the third information.

[0771] Optional implementations of step S7103 may refer to the optional implementations of step S2103A, step S2103B and / or step S2103C in FIG2 , and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.

[0772] In some embodiments, the UDM sends the third information to the NEF, but is not limited thereto and may also send the third information to other entities.

[0773] Optionally, the UDM sends third information to the first network function and / or the second network function.

[0774] Step S7104, perform the first operation.

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

[0776] Step S7105, sending the first information.

[0777] The optional implementation of step S7105 can be found in the optional implementation of step S2107A, step S2107B, step S2107C, step S2107D and / or step S2107E in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0778] In some embodiments, the UDM sends the first information to the NEF, but is not limited thereto and may also send the first information to other entities.

[0779] Optionally, the UDM sends the first information to the first network function.

[0780] Optionally, the UDM sends the first information to the second network function.

[0781] Optionally, the UDM sends the first information to the first device.

[0782] In some optional embodiments, before sending the first information, the UDM further includes: acquiring the first information. Exemplarily, the UDM receives the first information sent by the first terminal.

[0783] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S7101 to S7105. For example, step S7101 can be implemented as an independent embodiment, step S7102 can be implemented as an independent embodiment; step S7103 can be implemented as an independent embodiment; step S7104 can be implemented as an independent embodiment; step S7105 can be implemented as an independent embodiment; the combination of step S7101 and step S7105 can be implemented as an independent embodiment; the combination of step S7102 and step S7103 can be implemented as an independent embodiment; the combination of step S7104 and step S7105 can be implemented as an independent embodiment; the combination of step S7104 and step S7105 can be implemented as an independent embodiment; and steps S7101 to S7106 can be implemented as independent embodiments.

[0784] In some embodiments, step S7102, step S7103, step S7104, and step S7105 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0785] In some embodiments, step S7101, step S7104, and step S70105 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0786] In some embodiments, step S7101, step S7102, step S7103, and step S7105 may be optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0787] FIG7B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG7B , the present disclosure embodiment relates to an information processing method, which is executed by the UDM, and the method includes:

[0788] Step S7201, obtain request.

[0789] The optional implementation of step S7201 can be found in step S2101D and / or step S2101E and / or step S2101F in Figure 2, or the optional implementation of step S7101 in Figure 7A, and other related parts in the embodiments involved in Figures 2 and 7A, which will not be repeated here.

[0790] In some embodiments, the request is a perception-related request.

[0791] In some embodiments, the request includes at least one of the following: at least one first identifier and role information corresponding to the first identifier; wherein the first identifier is used to indicate the terminal; and the role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0792] In some embodiments, receiving a request includes at least one of: receiving a first request sent by a first device; receiving the first request sent by the first device through a network open function NEF; receiving a second request sent by the NEF; receiving a fifth request sent by the first network function; and receiving a seventh request sent by the second network function.

[0793] In some embodiments, the method also includes: receiving through AMF or directly receiving third information sent by the first terminal, wherein the third information is used to indicate at least one of the following: a first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0794] In some embodiments, the method further includes: determining third information of the first terminal from third information of at least one terminal based on the first identifier, wherein the terminal includes the first terminal and / or the third terminal.

[0795] In some embodiments, the method includes at least one of: sending the third information of the first terminal to the NEF; sending the third information of the first terminal to the first network function; and sending the third information of the first terminal to the second network function.

[0796] In some embodiments, the method further comprises at least one of: sending a sixth request to the first network function; wherein the sixth request is a perception-related request; and sending the sixth request to the second network function.

[0797] In some embodiments, the method further includes at least one of: determining not to send a sixth request to the first network function based on the third information; wherein the sixth request is a perception-related request; and determining not to send the sixth request to the second network function based on the third information.

[0798] In some embodiments, the method also includes at least one of the following: sending first information to a first network function; wherein the first information includes a perception result and / or second information; sending the first information to a second network function; sending the first information to an NEF; sending the first information to the first device through the NEF; and sending the first information to the first device based on determining that the first information of the first terminal is agreed to be opened.

[0799] In some embodiments, the first device includes at least one of the following: an AF, a client corresponding to the second terminal, and the first terminal; and / or,

[0800] The first network function includes at least one of the following: AMF, gateway mobile positioning center GMLC, location management function LMF and perception-related network function NF; and / or, the second network function includes at least one of the following: access and mobility management function AMF, LMF and perception-related network function.

[0801] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 7A , which will not be described in detail here.

[0802] FIG7C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG7C , the present disclosure embodiment relates to an information processing method, which is executed by the UDM, and the method includes:

[0803] Step S7301, perform the first operation.

[0804] The optional implementation of step S7301 can be found in step S2104D in FIG. 2 , or the optional implementation of step S7104 in FIG. 7A , and other related parts in the embodiments involved in FIG. 2 and FIG. 7A , which will not be described in detail here.

[0805] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 7A , which will not be described in detail here.

[0806] FIG8A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG8A , the present disclosure embodiment relates to an information processing method, which is executed by a first terminal and includes:

[0807] Step S8101, obtain the third request.

[0808] The optional implementation of step S8101 can refer to the optional implementation of the optional embodiment of step S2104A and / or step S2104B in Figure 2, and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0809] In some embodiments, the first terminal receives the third request sent by the second network function, but is not limited thereto and may also receive the third request sent by other entities.

[0810] In some embodiments, the first terminal obtains a third request specified by the protocol.

[0811] In some embodiments, the first terminal obtains the third request from an upper layer(s).

[0812] In some embodiments, the first terminal performs processing to obtain the third request.

[0813] In some embodiments, step S8101 is omitted, the first terminal autonomously implements the function indicated by the third request, or the above function is default or acquiescent.

[0814] Optionally, the first terminal receives a third request sent by the first network function and / or NEF.

[0815] Step S8102, sending the fourth information.

[0816] The optional implementation of step S8102 can refer to the optional implementation of the optional embodiment of step S2105A and / or step S2105B in Figure 2, and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0817] In some embodiments, the first terminal sends the fourth information to the second network function, but is not limited thereto, and the third information may also be sent to other entities.

[0818] Optionally, the first terminal sends third information to the first network function and / or NEF.

[0819] In some optional embodiments, the first terminal sends the first information to the UDM.

[0820] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S8101 and S8102. For example, step S8101 may be implemented as an independent embodiment, step S8102 may be implemented as an independent embodiment, and steps S8101 and S8102 may be implemented as independent embodiments.

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

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

[0823] FIG8B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG8B , the present disclosure embodiment relates to an information processing method, which is executed by a first terminal and includes:

[0824] Step S8201: Receive a third request sent by the network function.

[0825] The optional implementation of step S8201 can refer to the optional embodiment of step S2101B in Figure 2, or the optional implementation of step S8102 in Figure 8A, and other related parts in the embodiments involved in Figures 2 and 8A, which will not be repeated here.

[0826] In some embodiments, the third request is used to request fourth information of the first terminal; the method further includes: sending the fourth information to the network function.

[0827] In some embodiments, the first network function or the second network function; wherein the first network function includes: GMLC, LMF and / or a network function NF related to perception; and / or the second network function includes: AMF, LMF and / or a network function related to perception.

[0828] In some embodiments, the fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service; whether it agrees to open the second information of the first terminal; and whether it agrees to assume the role indicated in the first identifier.

[0829] In some embodiments, the method also includes: sending third information of the first terminal to the UDM or through access to the UDM, wherein the third information is used to indicate at least one of the following: the first identifier; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0830] The above embodiments may be implemented individually or in combination with each other. For optional implementations, please refer to the optional implementations of the steps in FIG. 2 and FIG. 8A , which will not be described in detail here.

[0831] FIG9A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG9A , the embodiment of the present disclosure relates to an information processing method for a communication system, the method comprising:

[0832] Step S9101: The first terminal of the network device sends a third request.

[0833] Optionally, the network device includes a first network function, a second network function and / or NEF, etc.

[0834] The optional implementation method of step S9101 can be found in the optional embodiment of step S2104 in Figure 2, step S4104 in Figure 4A, step S5104 in Figure 5A, step S6104 in Figure 6A, or the optional implementation method of step S8101 in Figure 8A, and other related parts in the embodiments involved in Figures 2, 4A, 5A, 6A, and 8A, which will not be repeated here.

[0835] Step S9102: The first terminal sends fourth information to the network device.

[0836] The optional implementation method of step S9101 can be found in the optional embodiment of step S2105 in Figure 2, step S4105 in Figure 4A, step S5105 in Figure 5A, step S6105 in Figure 6A, or the optional implementation method of step S8102 in Figure 8A, as well as other related parts in the embodiments involved in Figures 2, 4A, 5A, 6A, and 8A, which will not be repeated here.

[0837] In some embodiments, the above method may include the method described in the above-mentioned embodiments of the information processing system 100 side, the first device, the NEF, the first network function, the second network function, the UDM and the first terminal, etc., which will not be repeated here.

[0838] FIG9B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG9B , the method includes:

[0839] Step S9201: The first network device sends a first request to the second network device.

[0840] In some embodiments, the second network device receives the first request sent by the first network device.

[0841] In some embodiments, if the first network device is AF, the second network device is NEF, GMLC, LMF, UDM and / or network functions related to perception; or, if the first network device is a second terminal, the second network device is NEF, GMLC, LMF, UDM and / or network functions related to perception.

[0842] In some embodiments, the first request is a perception-related request.

[0843] In some embodiments, the first request includes at least one first identifier and / or role information corresponding to the first identifier: the first identifier is used to indicate the terminal role information is used to indicate that the terminal is a perception receiver or a perception sender.

[0844] For other contents of this step, please refer to steps 2101A to S2101F in Figure 2, as well as other embodiments mentioned above in this application, which will not be repeated here.

[0845] Step S9202: The second network device sends first information to the first network device.

[0846] In some embodiments, the first network device receives first information sent by the second network device.

[0847] In some embodiments, if the second network device is a UDM, the first network device is an AF, a second terminal, an NEF, an AMF, a GMLC, an LMF, a UDM, and / or a network function related to perception; or, if the second network device is a GLMC, the first network device may be an AF, a second terminal, an NEF, an AMF, an LMF, and / or a network function related to perception; or, if the second network device is an LMF, the first network device may be an AF, a second terminal, an NEF, an AMF, an GMLC, and / or a function related to perception; or, if the second network device is an AMF, The first network device may be AF, a second terminal, NEF, LMF, GMLC and / or a perception-related function; or, if the second network device is a perception-related network function, the first network device may be AF, a second terminal, NEF, AMF, GMLC and / or LMF; or, if the second network device is NEF, the first network device may be AF and / or a second terminal; or, if the second network device is the first terminal, the first network device may be UDM, AF, a second terminal, NEF, GMLC, AMF, LMF and / or a perception-related network function.

[0848] In some embodiments, the first information includes a perception result and / or the second information.

[0849] For other contents of this step, please refer to steps S2107A to S2107E in Figure 2 and other embodiments mentioned above in this application, which will not be repeated here.

[0850] In some optional embodiments, after step S9201 and before step S9202, the method further includes: step S9203 and step S9204.

[0851] Step S9203: The second network device sends a second request to the third network device.

[0852] In some embodiments, the third network device receives the second request sent by the second network device.

[0853] In some embodiments, the second network device is NEF, AMF, GMLC, LMF or a network function related to perception, and the third network device is UDM.

[0854] In some embodiments, the second request is used to request third information. Optionally, the second request includes at least one first identifier.

[0855] For other contents of this step, please refer to steps 2102A to S2102C in Figure 2, as well as other embodiments mentioned above in this application, which will not be repeated here.

[0856] Step S9204: The third network device sends third information to the second network device.

[0857] In some embodiments, the second network device receives third information sent by the third network device.

[0858] In some embodiments, when the third network device sends the third information to the second network device, the third network device is a UDM, and the second network device is a NEF, an AMF, a GMLC, a LMF, or a network function related to perception.

[0859] In some embodiments, the third information is used to indicate at least one of the following: the first identifier; the role information corresponding to the first identifier; whether the first terminal is authorized to participate in the perception service; whether to agree to open the second information of the first terminal; and whether privacy verification is required.

[0860] For other contents of this step, please refer to steps S2103A to S2103C in Figure 2, as well as other embodiments mentioned above in this application, which will not be repeated here.

[0861] In some optional embodiments, after step S9203 and before step S9204, the method further includes: step S9205 and step S9206.

[0862] Step S9205: The third network device sends a third request to the fourth network device.

[0863] In some embodiments, the fourth network device receives the third request sent by the third network device.

[0864] In some embodiments, when the third network device sends a third request to the fourth network device, the third network device is NEF, AMF, GMLC, LMF or a network function related to perception, and the third network device is the first terminal.

[0865] In some embodiments, the third request is for requesting fourth information.

[0866] For other contents of this step, please refer to steps S2104A to S2104B in Figure 2, as well as other embodiments mentioned above in this application, which will not be repeated here.

[0867] Step S9206: The fourth network device sends fourth information to the third network device.

[0868] In some embodiments, the third network device receives fourth information sent by the fourth network device.

[0869] In some embodiments, when the fourth network device sends fourth information to the third network device, the fourth network device is the first terminal, the third network device is NEF, AMF, GMLC, LMF or a network function related to perception, and the third network device is the first terminal.

[0870] In some embodiments, it is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service; whether it agrees to open the second information of the first terminal; and whether it agrees to assume the role associated with the first request.

[0871] For other contents of this step, please refer to steps S2105A to S2105B in Figure 2, as well as other embodiments mentioned above in this application, which will not be repeated here.

[0872] It should be noted that the above embodiments can be combined arbitrarily when the solutions themselves are not contradictory, and this application does not list all possible combinations one by one.

[0873] FIG10A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG10A , the embodiment of the present disclosure relates to an information processing method, which includes:

[0874] Step S10101A: The third party sends a perception request to the NEF.

[0875] Optionally, the awareness request includes the UE ID. The NEF obtains the user consent policy from the UDM.

[0876] Optionally, the user consent policy may be the third information in the previous embodiment. Exemplarily, the user consent policy indicates whether the UE is allowed to participate in the sensing service, or whether the UE authorizes the disclosure of UE information. For example, the UE information may include the UE location, UE ID, and / or UE permanent ID.

[0877] Optionally, if the user consent policy indicates that the UE is allowed to participate in the sensing service or is permitted to expose UE information (eg, UE location, UE ID and / or UE permanent ID), the NEF sends a sensing request to the first network function. Otherwise, the NEF rejects the sensing request.

[0878] Alternatively, the third party may be an AF or a client on a UE. Alternatively, the UE may be a terminal; for example, the UE may be the first terminal in the previous embodiment. The third party may be the first device in the previous embodiment. The user consent policy may be the third information in the previous embodiment; the UE information may be the second information in the previous embodiment. The perception request may be the first request in the previous embodiment, etc.

[0879] Step S10101B: The third party sends a perception request to the first network function.

[0880] Optionally, the awareness request includes the UE ID. The first network function obtains the user consent policy from the UDM.

[0881] Step S10101C: The third party sends a perception request to the UDM through the NEF.

[0882] Optionally, both the requests sent by the third party and the NEF include the UE ID.

[0883] In step S10102A, the first network function sends a perception request to the second network function. Optionally, this step corresponds to step S10101A.

[0884] Optionally, if the UE allows participation in the perception service, the first network function sends a perception request to the second network function.

[0885] In step S10102B, the first network function sends a perception request to the second network function. Optionally, this step corresponds to step S10101B.

[0886] Optionally, if the UE allows participation in the perception service, the first network function sends a perception request to the second network function.

[0887] Step S10102C: UDM sends a perception request to the second network function.

[0888] Optionally, if the UE allows participation in the awareness service, the UDM sends an awareness request to the second network function. The UDM may also send user consent policies (user consent policies or user consent information) to the second network function.

[0889] Step S10103: The second network function interacts with the UE to obtain a verification result.

[0890] Optionally, if the user consent policy indicates that the UE needs to perform further privacy verification, the second network function interacts with the UE to obtain a verification result.

[0891] Exemplarily, the second network function should be able to send a privacy verification request to the UE. The privacy verification request may include the AF ID and UE information (eg, UE ID, UE location, and / or UE permanent ID).

[0892] Exemplarily, the UE should be able to send a verification result to the second network function, where the verification result indicates whether the UE permits or denies exposing sensing contextual information (e.g., UE ID, UE location) to the AF.

[0893] Optionally, the privacy verification request may be the third request in the previous embodiment; and the verification result may be the fourth information in the previous embodiment.

[0894] Step S10104A: The first network function obtains a perception result and / or perception context information.

[0895] Step S10104B: The second network function obtains the perception result and / or perception context information.

[0896] Optionally, if the UE agrees to expose sensitive context information, the first network function and / or the second network function obtains the perception result and the perception context information. The perception result and / or the perception context information may be the first information in the previous embodiment; and the perception context information may be the second information in the previous embodiment.

[0897] Step S10105A: NEF sends UE information to a third party.

[0898] Optionally, the NEF further checks the user consent policy before sending (or opening) the perception context information to a third party. If the user consent policy indicates that the UE information (such as UE ID, UE location and / or UE permanent ID) can be opened, the NEF opens the UE information to the third party.

[0899] Step S10105B: The first network function sends UE information to the third party.

[0900] Optionally, before the first network function sends (or discloses) the perception context information to a third party, the first network function further checks the user consent policy. If the user consent policy indicates that the UE information (e.g., UE ID, UE location, and / or UE permanent ID) can be disclosed, the first network function discloses the UE information to the third party.

[0901] Step S10105C: The second network function sends UE information to the third method.

[0902] Optionally, the second network function further checks the user consent policy before sending (or opening) the perception context information to the third party. If the user consent policy indicates that the UE information (e.g., UE ID, UE location, and / or UE permanent ID) can be opened, the second network function opens the UE information to the third party through the first network function.

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

[0904] FIG10B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG10B , the embodiment of the present disclosure relates to an information processing method, which includes:

[0905] Step S10200: NF (Nudm parameter provision update) can subscribe to UDM notification of UE LCS privacy file update.

[0906] Optionally, when a deferred positioning request is in progress, the NF may decide to subscribe to such notification. The UE may be the terminal in the previous embodiment, for example, the first terminal.

[0907] Step S10201: The UE sends a UE location privacy setting request to the AMF.

[0908] Optionally, if the UE has generated or updated a UE location privacy indication, the UE sends a location privacy indication to the AMF via a UE location privacy setting request in an N1 NAS message. Exemplarily, the UE location privacy indication is used to indicate whether the UE's subsequent LCS request is allowed or not. If the UE generates or updates an event reporting expected area and an optional area usage indication based on the UE power state, the UE location privacy setting request includes the event reporting expected area and the area usage indication. The location privacy request may also include a user consent policy regarding whether its perception context information (e.g., UE ID, UE location) can be exposed to a third party.

[0909] Step S10202: AMF calls the Nudm parameter to provide the update (LCS privacy) service operation to UDM.

[0910] Optionally, the Nudm parameter provides an update service operation carrying a UE location privacy indication; the UE location privacy indication is used to perceive contextual information related to the user consent policy and may include an event reporting desired area and an area usage indication. The UDM stores or updates the UE LCS privacy profile in the UDR by calling the Nudr_DM Update (SUPI, Subscription Data) service operation accordingly.

[0911] In step S10203, the AMF responds to the UE with a UE Location Privacy Settings Response in an N1 NAS message.

[0912] In step S10204, the UDM notifies the updated UE LCS privacy profile to a predetermined network function (e.g., AMF, GMLC, NEF and / or perception-related network functions) via a Nudm_SDM_Notification message.

[0913] Step S10205: NF (e.g., AMF, GMLC, NEF and / or perception-related network functions) unsubscribes from UDM notifications of UE LCS privacy profile updates.

[0914] Optionally, for example, if the positioning process is postponed, the UDM notification of subscribing to the UE LCS privacy profile update is cancelled.

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

[0916] The present disclosure relates to an information processing method, which includes:

[0917] In some embodiments, the NEF determines whether the UE is authorized to participate in the sensing service and / or determines whether to open the sensing context information (eg, UE ID and / or UE location) to a third party based on the user consent policy.

[0918] Optionally, the NEF can obtain the user consent policy from the UDM using the UE ID.

[0919] Optionally, the UE ID may be provided by a third party. Optionally, the third party may be the AF, a client on the UE, or the UE.

[0920] Optionally, after obtaining the perception context information, the NEF can further determine whether to agree to open the perception context information (eg, UE ID and / or UE location) to a third party based on a user consent policy.

[0921] Optionally, the NEF should be able to send a request to the UDM to trigger the awareness service. Optionally, the awareness request includes the UE ID.

[0922] Optionally, the awareness request sent from the NEF to the UDM is triggered by a third party (eg, the AF and / or the client / UE on the UE).

[0923] In some embodiments, the first network function determines whether the UE is authorized to participate in the sensing service and / or determines whether to open the sensing context information (eg, UE ID and / or UE location) to a third party based on a user consent policy.

[0924] Optionally, the first network function can obtain the user consent policy from the UDM using the UE ID.

[0925] Optionally, the UE ID may be provided by a third party or NEF. Optionally, the third party may be an AF, a client on the UE, or the UE.

[0926] Optionally, the first network function can trigger the second network function to perform the sensing service.

[0927] Optionally, after obtaining the perception context information, the first network function can further determine whether to agree to open the perception context information (eg, UE ID and / or UE location) to a third party based on a user consent policy.

[0928] In some embodiments, the second network function determines whether the UE is authorized to participate in the sensing service and / or determines whether to open the sensing context information (eg, UE ID and / or UE location) to a third party based on the user consent policy.

[0929] Optionally, the second network function can be triggered by the first network function or UDM to perform the awareness service.

[0930] Optionally, after obtaining the perception context information, the second network function can further determine whether to agree to open the perception context information (eg, UE ID and / or UE location) to a third party based on a user consent policy.

[0931] Optionally, the second network function can obtain the user consent policy from the UDM.

[0932] Optionally, the third party may be an AF, a client on a UE, or a terminal or a UE.

[0933] In some embodiments, the UDM determines whether the UE is authorized to participate in the awareness service and / or determines whether to open awareness context information (eg, UE ID and / or UE location) to a third party based on a user consent policy.

[0934] Alternatively, the UDM can receive the UE ID from a third party directly or through the NEF.

[0935] Optionally, the UDM can locate the corresponding user consent policy based on the UE ID.

[0936] Optionally, the UDM can store the user consent policy sent by the UE through the AMF, where the user consent policy indicates whether the UE authorizes the disclosure of UE information (e.g., UE location, UE ID and / or UE permanent ID).

[0937] Optionally, the UDM can send awareness context information to the first network function, the second network function, the NEF and / or awareness-related network functions.

[0938] Optionally, the UDM can send the user consent policy to the first network function, the second network function, the NEF and / or the awareness-related network function.

[0939] Optionally, the UDM can trigger the first network function or the second network function to perform the awareness service.

[0940] In some embodiments, the UE can send a user consent policy to the UDM. Optionally, the user consent policy indicates whether the UE authorizes sensing and / or whether to open sensing context information (e.g., UE location, UE ID and / or UE permanent ID).

[0941] In some embodiments, a third party can send an awareness request including the UE ID.

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

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

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

[0945] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as 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 to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0946] Figure 11A is a schematic diagram of the structure of a first device 11100 provided in an embodiment of the present disclosure. As shown in Figure 11A, the first device 11100 includes a first transceiver module 11101. In some embodiments, the first transceiver module 11101 is configured to send a first request. Optionally, the first transceiver module 11101 is configured to perform at least one of the sending and / or receiving steps (such as, but not limited to, steps S2101 and / or S2107D and / or S2107E) performed by the first device in any of the above methods, which will not be further described here.

[0947] Figure 11B is a schematic diagram of the structure of an NFE 11200 provided in an embodiment of the present disclosure. As shown in Figure 11B , NFE 11200 includes at least one of a second transceiver module 11201 and a second processing module 11202. Optionally, the second transceiver module 11201 is configured to receive a first request sent by a first device. Optionally, the second transceiver module 11201 is configured to execute at least one of the sending and / or receiving steps (such as, but not limited to, steps S2101A, S2101C, S2102A, S2103A, S2107A, and / or S2107E) performed by the NFE in any of the above methods, which are not described in detail here. Optionally, the second processing module 11202 is configured to execute at least one of the processing steps (such as, but not limited to, steps S2106A) performed by the NFE in any of the above methods, which are not described in detail here.

[0948] Figure 11C is a schematic diagram of the structure of the first network function 11300 provided in an embodiment of the present disclosure. As shown in Figure 11C, the first network function 11300 includes: at least one of a third transceiver module 11301 and a third processing module 11302. The third transceiver module 11301 is configured to receive a request. Optionally, the third transceiver module 11301 is configured to execute at least one of the sending and / or receiving steps (such as step S2101B, step S2102B, step S2103B, step S2104A, step S2105A, and / or step S2107B, but not limited thereto) performed by the first network function in any of the above methods, which are not described in detail here. Optionally, the third processing module 11302 is configured to execute at least one of the processing steps (such as step S2106B, but not limited thereto) performed by the first network function in any of the above methods, which are not described in detail here.

[0949] Figure 11D is a schematic diagram of the structure of the second network function 11400 provided in an embodiment of the present disclosure. As shown in Figure 11D, the second network function 11400 includes: at least one of a fourth transceiver module 11401 and a fourth processing module 11402. The fourth transceiver module 11401 is configured to receive a request. Optionally, the fourth transceiver module 11401 is configured to execute at least one of the sending and / or receiving steps (such as step S2101F, step S2102C, step S2103C, step S2104B, step S2105B, and / or step S2107C, but not limited thereto) performed by the second network function in any of the above methods, which are not described in detail here. Optionally, the fourth processing module 11402 is configured to execute at least one of the processing steps (such as step S2106C, but not limited thereto) performed by the second network function in any of the above methods, which are not described in detail here.

[0950] Figure 11E is a schematic diagram of the structure of the UDM 11500 provided in an embodiment of the present disclosure. As shown in Figure 11E, UDM 11500 includes a fifth transceiver module 11501 and a fifth processing module 11502. The fifth transceiver module 11501 is configured to receive the first request. Optionally, the fifth transceiver module 11501 is configured to execute at least one of the sending and / or receiving steps (such as, but not limited to, steps S2101D, S2101E, S2101F, S2102, S2103, and / or S2107) performed by the UDM in any of the above methods, which are not described in detail here. Optionally, the fifth processing module 11502 is configured to execute at least one of the processing steps (such as, but not limited to, steps S7014) performed by the UDM in any of the above methods, which are not described in detail here.

[0951] Figure 11F is a schematic diagram of the structure of a first terminal 11600 provided in an embodiment of the present disclosure. As shown in Figure 11F, first terminal 11600 includes a sixth transceiver module 11601. The sixth transceiver module 11601 is configured to transmit third information from the first terminal. Optionally, the sixth transceiver module 11601 is configured to perform at least one of the sending and / or receiving steps (such as, but not limited to, steps S2104A, S2104B, S2105A, and / or S2105B) performed by the first terminal in any of the above methods, which will not be further described here.

[0952] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module and the transceiver may be interchangeable. Exemplarily, the first transceiver module includes a first transmitting module and / or a first receiving module. Exemplarily, the second transceiver module includes a second transmitting module and / or a second receiving module.

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

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

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

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

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

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

[0959] 12B is a schematic diagram of the structure of a chip 12200 according to an embodiment of the present disclosure. If the communication device 12100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 12200 shown in FIG12B , but the present disclosure is not limited thereto.

[0960] The chip 12200 includes one or more processors 12201. The chip 12200 is configured to execute any of the above methods.

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

[0962] In some embodiments, the interface circuit 12202 performs at least one of the communication steps (e.g., step S2101, step S2102, step S2103, step S2104, step S2105, and / or step S2107) of the above method. The interface circuit 12202 performing the communication steps (e.g., step S2101, step S2102, step S2103, step S2104, step S2105, and / or step S2107) of the above method, for example, means that the interface circuit 12202 performs data exchange between the processor 12201, chip 12200, memory 12203, or transceiver device. In some embodiments, the processor 12201 performs at least one of the other steps (e.g., step S2103, but not limited thereto).

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

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

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

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

Claims

1. An information processing method, characterized in that: The method is executed by a first device and includes: A first request is sent, wherein the first request is a perception-related request.

2. The method according to claim 1, characterized in that The first request includes at least one of the following: At least one first identifier; wherein the first identifier is used to indicate a terminal; Role information corresponding to the first identifier; wherein the role information is used to indicate that the terminal is a perception receiver or a perception sender.

3. The method according to claim 1 or 2, characterized in that: The sending of the first request includes at least one of the following: Sending the first request to the network open function NEF; Sending the first request to a first network function; sending the first request to the first network function through the NEF; Sending the first request to the unified data management UDM; The first request is sent to the UDM through the NEF.

4. The method according to any one of claims 1 or 2, characterized in that: The method further comprises: First information is received, wherein the first information includes a perception result and / or second information.

5. The method according to claim 4, characterized in that The receiving of the first information includes at least one of the following: receiving the first information sent by the NEF; receiving, by the NEF, the first information sent by the first network function; receiving the first information sent by the first network function; receiving, by the NEF, the first information sent by the second network function; Receiving the first information sent by the UDM; The first information sent by the UDM is received through the NEF.

6. The method according to any one of claims 1 to 5, characterized in that: The first device includes at least one of the following: an application function AF, a client corresponding to the second terminal, and the second terminal; and / or, The first network function includes at least one of the following: an access and mobility management function AMF, a gateway mobile positioning center GMLC, a location management function LMF, and a perception-related network function NF; and / or, The second network function includes at least one of the following: access and mobility management function AMF, LMF and perception-related network functions.

7. An information processing method, characterized in that: Performed by network open functions, including: A first request sent by a first device is received, wherein the first request is a perception-related request.

8. The method according to claim 7, characterized in that The first request includes at least one of the following: At least one first identifier; wherein the first identifier is used to indicate a terminal; Role information corresponding to the first identifier; wherein the role information is used to indicate that the terminal is a perception receiver or a perception sender.

9. The method according to claim 7 or 8, characterized in that: The method further includes: acquiring third information, wherein the third information is used to indicate at least one of the following: First logo; role information corresponding to the first identifier; Whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether privacy verification is required.

10. The method according to claim 9, characterized in that The obtaining of the third information comprises: Sending a second request to the unified data management (UDM), wherein the second request is used to request the third information; Receive the third information sent by the UDM.

11. The method according to claim 10, characterized in that The second request includes at least one first identifier.

12. The method according to any one of claims 9 to 11, characterized in that: The method further comprises at least one of the following: Based on the third information, determining whether the first terminal is authorized to participate in the sensing service; Based on the third information, determining whether to agree to open the second information of the first terminal; Based on the third information, determining whether to approve the first terminal to assume the role of the first request for association; Based on the third information, it is determined whether to agree to send a third request to the first terminal.

13. The method according to any one of claims 9 to 12, characterized in that: The method comprises at least one of the following: Sending a fourth request to the first network function; wherein the fourth request is a request related to perception; the fourth request includes the first identifier and / or role information; sending a fourth request to the second network function; The fourth request is sent to the unified data management (UDM).

14. The method according to any one of claims 9 to 13, characterized in that: The method comprises at least one of the following: Based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send the fourth request to the first network function, wherein the fourth request is a request related to perception; the fourth request includes the first identifier and / or role information; Based on the third information indicating that the first terminal is not authorized to participate in the perception service, determine not to send the fourth request to the second network function; Based on the third information indicating that the first terminal is not authorized to participate in the sensing service, determining not to send the fourth request to the UDM; Based on the third information indicating that the first terminal does not agree to open the second information, determine not to send the fourth request to the first network function; Based on the third information indicating that the first terminal does not agree to open the second information, determine not to send the fourth request to the second network function; Based on the third information indicating that the first terminal does not agree to release the second information, determine not to send the fourth request to the UDM; Based on the third information indicating that the first terminal cannot assume the role associated with the first request, determine not to send the fourth request to the first network function; Based on the third information indicating that the first terminal cannot assume the role associated with the first request, determine not to send the fourth request to the second network function; Based on the third information indicating that the first terminal cannot assume the role associated with the first request, it is determined not to send the fourth request to the UDM.

15. The method according to any one of claims 9 to 14, characterized in that: The method further includes: based on the third information, determining to send a response message to the first device, wherein the response message is used to indicate a rejection of the perception-related request or a failure of the perception-related request.

16. The method according to any one of claims 9 to 15, characterized in that The method also includes: ending the perception-related process based on the third information.

17. The method according to any one of claims 13 to 16, characterized in that: The method further comprises at least one of the following: Receiving first information sent by a first network function; wherein the first information includes a perception result and / or second information; receiving first information sent by a second network function; Receive the first information sent by the UDM.

18. The method according to any one of claims 9 to 17, characterized in that The method further comprises at least one of the following: In the case where the first terminal is authorized to participate in the sensing service, determining whether to agree to open the second information of the first terminal based on the third information; In the case where the first terminal is authorized to participate in the perception service, it is determined based on the third information whether to agree to open the perception results related to the first terminal.

19. The method according to claim 18, characterized in that The method further comprises at least one of the following: Determine, based on the third information, that the second information of the first terminal is agreed to be opened, and send the second information to the first device; Determine based on the third information that the second information of the first terminal is not agreed to be released, and determine not to send the second information to the first device; Determine, based on the third information, that the perception result of the first terminal is agreed to be opened, and send the perception result to the first device; Based on the third information, it is determined that the perception result of the first terminal is not agreed to be opened, and it is determined not to send the perception result to the first device.

20. The method according to any one of claims 7 to 17, characterized in that The first device includes at least one of the following: an application function AF, a client corresponding to the second terminal, and the second terminal; and / or, The first network function includes at least one of: an access and mobility management function AMF, a gateway mobile positioning center GMLC, a location management function LMF, and a perception-related network function NF; and / or, The second network function includes at least one of the following: an access and mobility management function AMF, a location management function LMF, and a perception-related network function.

21. An information processing method, characterized in that: The method is performed by a first network function, including: A request is received, wherein the request is a perception-related request.

22. The method according to claim 21, characterized in that The request includes at least one of the following: At least one first identifier; wherein the first identifier is used to indicate a terminal; Role information corresponding to the first identifier; wherein the role information is used to indicate that the terminal is a perception receiver or a perception sender.

23. The method according to claim 21 or 22, characterized in that The receiving request includes at least one of the following: receiving a fourth request sent by the network opening function NEF; receiving a first request sent by a first device; Receive the sixth request sent by the UDM.

24. The method according to any one of claims 21 to 23, characterized in that The method further comprises at least one of the following: Based on the request, a perception service related to the first terminal is performed.

25. The method according to any one of claims 21 to 23, characterized in that The method further comprises: Sending a third request to the first terminal, wherein the third request is used to request fourth information; The fourth information sent by the first terminal is received.

26. The method according to claim 25, characterized in that The fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether to agree to assume the role associated with the first request.

27. The method according to any one of claims 25 to 26, characterized in that The method further comprises at least one of the following: Based on the fourth information indicating that the first terminal is not authorized to participate in the perception service, determining not to execute the perception service related to the first terminal; Determine not to execute a perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened; Based on the fourth information indicating that the first terminal cannot assume the role of the first request association, it is determined not to execute the perception service related to the first terminal.

28. The method according to any one of claims 21 to 23, characterized in that The method further includes: acquiring third information, wherein the third information is used to indicate at least one of the following: First logo; role information corresponding to the first identifier; Whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether privacy verification is required.

29. The method according to claim 28, characterized in that The obtaining of the third information includes: Sending a second request to the unified data management (UDM), wherein the second request is used to request the third information; Receive the third information sent by the UDM.

30. The method according to claim 29, characterized in that The second request includes at least one first identifier.

31. The method according to any one of claims 28 to 30, characterized in that The method further includes: executing a perception service related to the first terminal based on third information.

32. The method according to any one of claims 28 to 30, characterized in that The method further comprises at least one of the following: Based on the third information, determining whether the first terminal is authorized to participate in the sensing service; Based on the third information, determining whether to agree to open the second information of the first terminal; Based on the third information, determining whether to approve the first terminal to assume the role of the first request for association; Based on the third information, determining whether privacy verification is required; Based on the third information, it is determined whether to agree to send a third request to the first terminal.

33. The method according to claim 32, characterized in that The method further comprises at least one of the following: Indicating that the first terminal is not authorized to participate in the perception service based on the third information, determining not to execute the perception service related to the first terminal; Indicating that the first terminal does not agree to open the second information based on the third information, determining not to execute the perception service related to the first terminal; Based on the third information indicating that the first terminal cannot assume the role requested for association, determining not to perform a perception service related to the first terminal; Based on the third information instruction, privacy verification is performed.

34. The method according to any one of claims 21 to 33, characterized in that The method comprises at least one of the following: Sending a fifth request to the second network function; wherein the fifth request is a request related to perception; the fifth request includes the first identifier and / or role information; The fifth request is sent to the unified data management (UDM).

35. The method according to any one of claims 28 to 33, characterized in that The method further comprises at least one of the following: Based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send a fifth request to the UDM; wherein the fifth request is a request related to perception; and the fifth request includes a first identifier and / or role information; Based on the third information indicating that the first terminal is not authorized to participate in the perception service, determine not to send the fifth request to the second network function; Based on the third information indicating that the first terminal does not agree to open the second information, determine not to send the fifth request to the UDM; Based on the third information indicating that the first terminal does not agree to open the second information, determine not to send the fifth request to the second network function; Based on the third information indicating that the first terminal cannot assume the role associated with the first request, determine not to send the fifth request to the UDM; Based on the third information indicating that the first terminal cannot assume the role associated with the first request, it is determined not to send the fifth request to the second network function.

36. The method according to any one of claims 28 to 35, characterized in that The method further comprises: Based on the third information, determine to send a response message to the first device, wherein the response message is used to indicate that the request related to the perception is rejected or the request related to the perception fails.

37. The method according to any one of claims 28 to 36, characterized in that The method further comprises: Based on the third information, the perception-related process is terminated.

38. The method according to any one of claims 21 to 37, characterized in that The method further comprises at least one of the following: receiving first information sent by a second network function, wherein the first information includes perception information and / or second information; The first information sent by the UDM is received.

39. The method according to claim 38, characterized in that The method further comprises at least one of the following: Sending the first information to the NEF or the first device; Determine, based on the third information, that the second information of the first terminal is agreed to be opened, and send the second information to the first device or the NEF; Based on the third information, it is determined that the second information of the first terminal is not agreed to be released, and it is determined not to send the second information to the first device or the NEF.

40. The method according to any one of claims 21 to 39, characterized in that The first device includes at least one of the following: an application function AF, a client corresponding to the second terminal, and the second terminal; and / or, The first network function includes at least one of the following: an access and mobility management function AMF, a gateway mobile positioning center GMLC, a location management function LMF, and a perception-related network function NF; and / or, The second network function includes at least one of the following: access and mobility management function AMF, LMF and perception-related network functions.

41. An information processing method, characterized in that: Executed by a second network function, the method includes: A request is received, wherein the request is a perception-related request.

42. The method according to claim 41, characterized in that The request includes at least one of the following: At least one first identifier; wherein the first identifier is used to indicate a terminal; Role information corresponding to the first identifier; wherein the role information is used to indicate that the terminal is a perception receiver or a perception sender.

43. The method according to claim 41 or 42, characterized in that The receiving request includes at least one of the following: receiving a first request sent by a first device; receiving a fourth request sent by the first network function; Receive the sixth request sent by the unified data management UDM.

44. The method according to any one of claims 41 to 43, characterized in that The method further comprises: Based on the request, a perception service related to the first terminal is performed.

45. The method according to any one of claims 41 to 43, characterized in that The method further comprises: Sending a third request to the first terminal, wherein the third request is used to request fourth information; The fourth information sent by the first terminal is received.

46. ​​The method according to claim 45, characterized in that The fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether to agree to assume the role associated with the first request.

47. The method according to any one of claims 45 to 46, characterized in that The method further comprises at least one of the following: Based on the fourth information indicating that the first terminal is not authorized to participate in the perception service, determining not to execute the perception service related to the first terminal; Determine not to execute a perception service related to the first terminal based on the fourth information indicating that the second information of the first terminal is not agreed to be opened; Based on the fourth information indicating that the first terminal cannot assume the role of the first request association, it is determined not to execute the perception service related to the first terminal.

48. The method according to any one of claims 41 to 43, characterized in that The method further includes: acquiring third information, wherein the third information is used to indicate at least one of the following: at least one first identifier; role information corresponding to the first identifier; Whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether privacy verification is required.

49. The method according to claim 48, characterized in that The obtaining of the third information includes: Sending a second request to the unified data management (UDM), wherein the second request is used to request the third information; Receive the third information sent by the UDM.

50. The method according to claim 49, characterized in that The second request includes at least one first identifier.

51. The method according to any one of claims 48 to 50, characterized in that The method further includes: executing a perception service related to the first terminal based on third information.

52. The method according to any one of claims 48 to 50, characterized in that The method further comprises at least one of the following: Based on the third information, determining whether the first terminal is authorized to participate in the sensing service; Based on the third information, determining whether to agree to open the second information of the first terminal; Based on the third information, determining whether to agree to open the perception result related to the first terminal; Based on the third information, determining whether to approve the first terminal to assume the role of the first request for association; Based on the third information, it is determined whether to agree to send a third request to the first terminal.

53. The method according to claim 52, characterized in that The method further comprises at least one of the following: Indicating that the first terminal is not authorized to participate in the perception service based on the third information, determining not to execute the perception service related to the first terminal; Indicating that the first terminal does not agree to open the second information based on the third information, determining not to execute the perception service related to the first terminal; Based on the third information indicating that the first terminal cannot assume the role associated with the first request, it is determined not to execute the perception service related to the first terminal.

54. The method according to any one of claims 41 to 43, characterized in that The method further comprises: A seventh request is sent to the UDM, wherein the seventh request is a perception-related request; and the seventh request includes the first identifier and / or role information.

55. The method according to any one of claims 48 to 53, characterized in that The method further comprises at least one of the following: Based on the third information indicating that the first terminal is not authorized to participate in the perception service, determining not to send a seventh request to the UDM; wherein the seventh request is a request related to perception; the seventh request includes the first identifier and / or role information; Based on the third information indicating that the first terminal does not agree to open the second information, determine not to send the seventh request to the UDM; Based on the third information indicating that the first terminal cannot assume the role associated with the first request, it is determined not to send the seventh request to the UDM.

56. The method according to any one of claims 48 to 55, characterized in that The method further comprises: Based on the third information, determine to send a response message to the first device, wherein the response message is used to indicate that the request related to the perception is rejected or the request related to the perception fails.

57. The method according to any one of claims 48 to 56, characterized in that The method further comprises: Based on the third information, the perception-related process is terminated.

58. The method according to any one of claims 41 to 57, characterized in that The method further includes: receiving first information sent by the UDM.

59. The method according to claim 58, characterized in that The method also Includes one of the following: Determine, based on the third information, that second information of the first terminal is agreed to be opened, and send the second information to the first network function; Based on the third information, it is determined that the second information of the first terminal is not agreed to be released, and it is determined not to send the second information to the first network function.

60. The method according to any one of claims 41 to 59, characterized in that The first device includes at least one of the following: an application function AF, a client corresponding to the second terminal, and the second terminal; and / or, The first network function includes at least one of the following: an access and mobility management function AMF, a gateway mobile positioning center GMLC, a location management function LMF, and a perception-related network function NF; and / or, The second network function includes at least one of the following: access and mobility management function AMF, LMF and perception-related network functions.

61. An information processing method, characterized in that: Executed by Unified Data Management (UDM), including: A request is received, wherein the request is a perception-related request.

62. The method according to claim 61, characterized in that The request includes at least one of the following: At least one first identifier; wherein the first identifier is used to indicate a terminal; Role information corresponding to the first identifier; wherein the role information is used to indicate that the terminal is a perception receiver or a perception sender.

63. The method according to claim 61 or 62, characterized in that The receiving request includes at least one of the following: receiving a first request sent by a first device; Receiving, through a network open function NEF, the first request sent by the first device; receiving a second request sent by the network opening function NEF; receiving a fifth request sent by the first network function; A seventh request sent by the second network function is received.

64. The method according to any one of claims 61 to 63, characterized in that The method further comprises: The third information sent by the first terminal is received through the access and mobility management function AMF or directly received, wherein the third information is used to indicate at least one of the following: First logo; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether privacy verification is required.

65. The method according to any one of claims 62 to 64, characterized in that The method further comprises: Based on the first identifier, the third information of the first terminal is determined from the third information of at least one terminal, wherein the terminals include the first terminal and / or the third terminal.

66. The method according to any one of claims 62 to 65, characterized in that The method comprises at least one of the following: Sending third information of the first terminal to the NEF; Sending the third information of the first terminal to the first network function; The third information of the first terminal is sent to the second network function.

67. The method according to any one of claims 62 to 66, characterized in that The method further comprises at least one of the following: Sending a sixth request to the first network function; wherein the sixth request is a request related to perception; The sixth request is sent to the second network function.

68. The method according to any one of claims 64 to 66, characterized in that The method further comprises at least one of the following: Based on the third information, determining not to send a sixth request to the first network function; wherein the sixth request is a request related to perception; Based on the third information, it is determined not to send the sixth request to the second network function.

69. The method according to any one of claims 61 to 68, characterized in that The method further comprises at least one of the following: Sending first information to the first network function; wherein the first information includes the perception result and / or the second information; sending the first information to a second network function; Sending the first information to NEF; Sending the first information to the first device through the NEF; Based on determining that the first information of the first terminal is agreed to be opened, the first information is sent to the first device.

70. The method according to any one of claims 61 to 69, characterized in that The first device includes at least one of the following: an application function AF, a client corresponding to the second terminal, and the first terminal; and / or, The first network function includes at least one of the following: an access and mobility management function AMF, a gateway mobile positioning center GMLC, a location management function LMF, and a perception-related network function NF; and / or, The second network function includes at least one of the following: access and mobility management function AMF, LMF and perception-related network functions.

71. An information processing method, characterized in that: The method is executed by the first terminal and includes: receiving a third request sent by the network function, wherein the third request is used to request fourth information of the first terminal; The fourth information is sent to the network function.

72. The method according to claim 71, characterized in that The network function includes: a first network function or a second network function; wherein the first network function includes: a gateway mobile positioning center GMLC, a location management function LMF and / or a perception-related network function NF; and / or the second network function includes: an access and mobility management function AMF, LMF and / or a perception-related network function.

73. The method according to any one of claims 71 to 72, characterized in that The fourth information is used to indicate at least one of the following: whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether you agree to assume the role indicated in the first identification.

74. The method according to any one of claims 71 to 73, characterized in that The method further comprises: Sending third information of the first terminal to a unified data management function UDM or to the UDM through an access and mobility management function AMF, wherein the third information is used to indicate at least one of the following: First logo; role information corresponding to the first identifier; whether the first terminal is authorized to participate in the sensing service; Whether to agree to open the second information of the first terminal; Whether privacy verification is required.

75. An information processing method, characterized in that: The method comprises: The network device sends a third request to the first terminal, wherein the third request is used to obtain fourth information of the first terminal; The first terminal sends the fourth information to the network device.

76. A first device, characterized in that include: The first transceiver module is configured to send a first request, wherein the first request is a perception-related request.

77. A network open function NEF, characterized in that: include: The second transceiver module is configured to receive a first request sent by a first device, wherein the first request is a perception-related request.

78. A first network function, characterized in that include: The third transceiver module is configured to receive a request, wherein the request is a perception-related request.

79. A second network function, characterized in that include: The fourth transceiver module is configured to receive a request, wherein the request is a perception-related request.

80. A unified data management (UDM), characterized in that: include: The fifth transceiver module is configured to receive a request, wherein the request is a perception-related request.

81. A first terminal, characterized in that: include: a sixth transceiver module, configured to receive a third request sent by the network function, wherein the third request is used to request fourth information of the first terminal; The fourth information is sent to the network function.

82. A communication device, characterized in that: include: one or more processors; The communication device is used to execute the information processing method described in any one of claims 1 to 6, or claims 7 to 20, or claims 21 to 40, or claims 41 to 60, or claims 61 to 70, or claims 71 to 74, or claim 75.

83. A communication system, characterized in that: include: A first device, a network open function NEF, a first network function, a second network function, a unified data management UDM and a first terminal; wherein the first device is configured to implement the information processing method described in any one of claims 1 to 6, the NEF is configured to implement the information processing method described in any one of claims 7 to 20, the first network function is configured to implement the information processing method described in any one of claims 21 to 40, the second network function is configured to implement the information processing method described in any one of claims 41 to 60, the UDM is configured to execute the information processing method described in any one of claims 61 to 70, and the first terminal is configured to execute the information processing method described in any one of claims 71 to 74.

84. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the information processing method described in any one of claims 1 to 6, or claims 7 to 20, or claims 21 to 40, or claims 41 to 60, or claims 61 to 70, or claims 71 to 74, or claim 75.

Images