Authorization methods for sensing node and sensing service, and apparatus, device and medium

Abstract

The present application relates to the field of sensing. Disclosed are authorization methods for a sensing node and a sensing service, and an apparatus, a device and a medium. The methods comprise: an authorization method for a sensing node, which method comprises acquiring first subscription information of a sensing node, and authorizing the sensing node on the basis of the first subscription information; and an authorization method for a sensing service, which method comprises acquiring second subscription information of a sensing target, and authorizing a sensing service for the sensing target on the basis of the second subscription information. The methods provided in the present application facilitate authorizing a sensing node on the basis of subscription information of the sensing node / a sensing target, which can protect the privacy of the sensing target and the sensing node and avoid an unauthorized device from participating in a sensing process, thus affecting a sensing result or invading the privacy of the sensing target; and a sensing service for the sensing target is authorized, which can avoid an unauthorized entity from acquiring a sensing result, thus invading the privacy of the sensing target.

Description

Perception node and perception service authorization method, device, equipment and medium Technical Field

[0001] The present application relates to the field of perception, and in particular to a method, apparatus, device and medium for authorizing a perception node and a perception service. Background Art

[0002] One of the new technologies proposed by the 3GPP (Third Generation Partnership Project) is to integrate wireless sensing with mobile communications to achieve converged sensing communication services. Using higher frequency bands, wider bandwidths, and larger antenna arrays, the entire communication system can be used as a sensor to achieve high-precision, high-resolution perception.

[0003] For converged perception communication services, the current perception targets have expanded from UE (User Equipment) in the original positioning service to UE, unconnected objects, areas, etc., and the perception information has also expanded from the location information in the original positioning service to environmental characteristics, human monitoring information, etc. How to design the authorization mechanism in perception to ensure the privacy and security of perception targets and perception nodes is an urgent problem that needs to be solved.

[0004] Summary of the Invention

[0005] The present invention provides a method, apparatus, device, and medium for authorizing a sensing node and a sensing service. The technical solution is as follows:

[0006] According to one aspect of the present application, a method for authorizing a sensing node is provided. The method is performed by the authorization entity and includes:

[0007] Obtain the first subscription information of the perception node;

[0008] The perception node is authorized based on the first subscription information.

[0009] According to one aspect of the present application, a method for authorizing a perception node is provided. The method is performed by a perception initiating entity, and the method further includes:

[0010] Providing a first sensory node list to the authorization entity, where the first sensory node list is used to indicate at least one sensory node;

[0011] The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

[0012] According to one aspect of the present application, a method for authorizing a sensing node is provided. The method is performed by a sensing node selection entity, and the method further includes:

[0013] providing a second sensory node list to the authorization entity, where the second sensory node list is used to indicate at least one sensory node;

[0014] The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

[0015] According to one aspect of the present application, a method for authorizing a perception service is provided, the method being performed by an authorization entity and comprising:

[0016] Get the second subscription information of the sensing target;

[0017] Based on the second subscription information, the perception service for the perception target is authorized.

[0018] According to one aspect of the present application, a method for authorizing a perception service is provided, the method being performed by the authorization entity, the method comprising:

[0019] Acquire second subscription information of the sensing target;

[0020] Based on the second subscription information, the perception service for the perception target is authorized.

[0021] According to one aspect of the present application, an authorization method based on an authorization entity is provided, the method being performed by a perception initiating entity, the method comprising:

[0022] The identification of the perception target is provided to the authorization entity, and the authorization entity is used to authorize the perception service for the perception target based on the second subscription information of the perception target.

[0023] According to one aspect of the present application, a perception-based authorization checking method is provided, the method comprising:

[0024] Based on the subscription information of the perceiving UE, an authorization policy of the perceiving UE is generated.

[0025] According to one aspect of the present application, an authorization device is provided, the device comprising:

[0026] An acquisition module, configured to acquire first subscription information of a sensing node;

[0027] The authorization module is used to authorize the perception node based on the first subscription information.

[0028] According to one aspect of the present application, a perception initiation device is provided, the device comprising:

[0029] A module is provided, configured to provide a first sensory node list to an authorization entity, wherein the first sensory node list is configured to indicate at least one sensory node.

[0030] The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

[0031] According to one aspect of the present application, a sensing node selection device is provided, the device comprising:

[0032] providing a module, configured to provide a second sensory node list to the authorization entity, the second sensory node list being configured to indicate at least one sensory node;

[0033] The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

[0034] According to one aspect of the present application, an authorization device is provided, the device comprising:

[0035] An acquisition module, configured to acquire second subscription information of a sensing target;

[0036] The authorization module is used to authorize the perception service for the perception target based on the second subscription information.

[0037] According to one aspect of the present application, a perception initiation device is provided, the device comprising:

[0038] A module is provided, configured to provide an identification of a perception target to an authorization entity, and the authorization entity is configured to authorize a perception service for the perception target based on the second subscription information of the perception target.

[0039] According to one aspect of the present application, a perception-based authorization checking device is provided, the device comprising:

[0040] The generating module is used to generate an authorization policy of the perception terminal UE based on the second subscription information of the perception terminal UE.

[0041] According to one aspect of the present application, a perception device is provided, which includes a processor and a memory, wherein the memory contains at least one program; the perception device is used to execute the at least one program in the memory to implement the above-mentioned authorization method of the perception node, or the authorization method of the perception service, or the authorization check method based on perception.

[0042] According to one aspect of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is used to be executed by a processor to implement the above-mentioned authorization method of the perception node, or the authorization method of the perception service, or the authorization check method based on perception.

[0043] According to one aspect of the present application, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the above-mentioned authorization method of the perception node, or the authorization method of the perception service, or the authorization check method based on perception.

[0044] According to one aspect of the present application, a computer program product or computer program is provided, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned authorization method of the perception node, or the authorization method of the perception service, or the authorization check method based on perception.

[0045] The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

[0046] Authorizing the perception node based on the subscription information of the perception node / perception target can protect the privacy of the perception target and the perception node, prevent unauthorized devices from participating in the perception process, affect the perception results or infringe the privacy of the perception target, and authorize the perception service for the perception target to prevent unauthorized entities from obtaining the perception results and infringing the privacy of the perception target. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0048] FIG1 is a block diagram of a perception system provided by an exemplary embodiment of the present application;

[0049] FIG2 is a schematic diagram of eight possible modes of perception provided in the related art;

[0050] FIG3 is a schematic structural diagram of a mobile communication system for sensing provided by an exemplary embodiment of the present application;

[0051] FIG4 is a schematic structural diagram of a mobile communication system for sensing provided by an exemplary embodiment of the present application;

[0052] FIG5 is a flowchart of a method for authorizing a sensing node provided by an exemplary embodiment of the present application;

[0053] FIG6 is a flowchart of a method for authorizing a sensing node provided by an exemplary embodiment of the present application;

[0054] FIG7 is a flowchart of a method for authorizing a sensing node provided by an exemplary embodiment of the present application;

[0055] FIG8 is a flowchart of a method for authorizing a sensing node provided by an exemplary embodiment of the present application;

[0056] FIG9 is a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application;

[0057] FIG10 is a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application;

[0058] FIG11 is a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application;

[0059] FIG12 is a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application;

[0060] FIG13 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0061] FIG14 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0062] FIG15 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0063] FIG16 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0064] FIG17 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0065] FIG18 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0066] FIG19 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0067] FIG20 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0068] FIG21 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0069] FIG22 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0070] FIG23 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0071] FIG24 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0072] FIG25 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0073] FIG26 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0074] FIG27 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0075] FIG28 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0076] FIG29 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0077] FIG30 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0078] FIG31 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0079] FIG32 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0080] FIG33 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0081] FIG34 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0082] FIG35 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0083] FIG36 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0084] FIG37 is a flowchart of an authorization method provided by an exemplary embodiment of the present application;

[0085] FIG38 is a flowchart of a method for selecting a sensing node provided by an exemplary embodiment of the present application;

[0086] FIG39 is a structural block diagram of an authorization device provided by an exemplary embodiment of the present application;

[0087] FIG40 is a structural block diagram of a perception initiating device provided by an exemplary embodiment of the present application;

[0088] FIG41 is a structural block diagram of a sensing node selection device provided by an exemplary embodiment of the present application;

[0089] FIG42 is a structural block diagram of an authorization device provided by an exemplary embodiment of the present application;

[0090] FIG43 is a structural block diagram of a perception initiating device provided by an exemplary embodiment of the present application;

[0091] FIG44 is a structural block diagram of a perception-based authorization checking device provided by an exemplary embodiment of the present application;

[0092] FIG45 is a structural block diagram of a device for selecting a sensing node provided by an exemplary embodiment of the present application;

[0093] Figure 46 is a structural diagram of a sensing device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0094] To make the objectives, technical solutions, and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail herein, with examples shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are merely examples of devices and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0095] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. It is known to those skilled in the art that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems. The terms used in this disclosure are merely for the purpose of describing specific embodiments and are not intended to limit this disclosure. The singular forms of "a", "said" and "the" used in this disclosure and the appended claims are also intended to include plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0096] It should be understood that although the terms first, second, etc. may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this disclosure, a first value may also be referred to as a second value, and similarly, a second value may also be referred to as a first value. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining."

[0097] Generally, unless otherwise expressly defined herein, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field. Unless expressly stated otherwise, all references to "an element, device, component, device, step, etc." are to be interpreted openly as referring to at least one instance of the element, device, component, device, step, etc. Unless expressly stated otherwise, the steps of any method disclosed herein do not have to be performed in the exact order disclosed.

[0098] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0099] Before introducing the technical solutions of this application, we first introduce and explain some of the background technologies involved in this application. The following related technologies can be combined with the technical solutions of the embodiments of this application as optional solutions, and they all fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0100] Perception refers to the technology that uses radio waves to detect parameters of the physical environment to achieve environmental perception such as target positioning, action recognition, and imaging. Nodes and / or entities involved in perception include but are not limited to:

[0101] Sensing sending node: the sending node of the sensing signal.

[0102] Sensing receiving node: a receiving node that senses the signal.

[0103] Perception nodes: Perception sending nodes and perception receiving nodes are collectively referred to as perception nodes, that is, nodes that perform perception.

[0104] As the spectrum for wireless communications and sensing gradually overlap, integrated communication and sensing technology merges these two functions, leveraging wireless resources to implement sensing. This allows sensing services to be delivered over a wider area using widely deployed cellular networks; joint sensing can be achieved through base stations and multiple terminals, achieving higher sensing accuracy; and sensing functions can be implemented by reusing wireless hardware modules to reduce costs. In short, integrated communication and sensing technology empowers future wireless communications systems with sensing capabilities, providing a foundation for the development of smart transportation, smart cities, smart factories, drones, and other services.

[0105] FIG1 shows a block diagram of a perception system 100 provided by an exemplary embodiment of the present application. The perception system 100 may include: an authorization entity 10 , a perception node selection entity 20 , a perception initiating entity 30 , one or more perception nodes 40 , and a perception target 50 .

[0106] Authorization entity 10 is a node that authorizes the sensing process; it can be a base station, a terminal, or a core network element. In some embodiments, authorization entity 10 is used to authorize sensing initiation entity 30; in some embodiments, authorization entity 10 is used to authorize sensing node 40; in some embodiments, authorization entity 10 is used to authorize both sensing initiation entity 30 and sensing node 40.

[0107] The sensing node selection entity 20 is a communication entity for selecting sensing nodes; it can be a base station, a terminal, or a core network element. In some embodiments, the sensing node selection entity 20 is used to select at least one sensing node 40 to assist in sensing.

[0108] The sensing initiating entity 30 is a communication entity that initiates the sensing service; it can be a base station, a terminal, or a core network element. In some embodiments, the sensing initiating entity 30 initiates a sensing request to the sensing target 50.

[0109] The sensing nodes 40 include sensing sending nodes and sensing receiving nodes; they can include base stations, terminals, IoT devices, or various handheld devices with wireless communication capabilities, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to wireless modems, as well as various forms of user equipment, MSs (Mobile Stations), etc. There are usually multiple sensing nodes 20.

[0110] Perception target 50 is the target object to be perceived, including a user equipment (UE), person, object, or area to be perceived. For example, if the perception application is indoor intrusion monitoring, perception target 50 is an indoor intruder; if the perception application is vehicle speed measurement, perception target 30 is a target vehicle on the road. If the perception application is drone monitoring, perception target 50 is a drone device.

[0111] The authorization entity 10 communicates with the perception node 40 via communication signals. For example, the authorization entity 10 sends an authorization result to the perception node 40 , or the authorization entity 10 sends an authorization result to the perception target 50 , and so on.

[0112] The authorization entity 10, the perception node selection entity 20 and the perception initiation entity 30 communicate with each other through communication signals.

[0113] Perception can be achieved through at least one of eight modes. Figure 2 shows eight possible modes of perception.

[0114] Mode 1: Base station autonomous sensing. In Mode 1, the sensing sending node and the sensing receiving node are the same base station 41. Specifically, base station 41 transmits a sensing signal to sensing target 42. After the sensing signal is reflected by sensing target 42, the same base station 41 receives the reflected signal (i.e., the sensing signal after being reflected by the sensing target).

[0115] Mode 2: Terminal-based self-transmission and self-reception. In Mode 2, the sensing sending node and the sensing receiving node are the same terminal 43. That is, terminal 43 sends a sensing signal to sensing target 44. After the sensing signal is reflected by sensing target 44, the same terminal 43 receives the reflected signal.

[0116] Mode 3: Base station cooperative sensing. In mode 3, the sensing sending node and the sensing receiving node are different base stations. That is, one base station 45 sends a sensing signal to the sensing target 46. After the sensing signal is reflected by the sensing target 46, another base station 47 receives the reflected signal.

[0117] Mode 4: Terminal Collaborative Sensing. In Mode 4, the sensing sending node and the sensing receiving node are different terminals. That is, one terminal 48 sends a sensing signal to a sensing target 49. After the sensing signal is reflected by the sensing target 49, another terminal 50 receives the reflected signal.

[0118] Mode 5: Base station-terminal collaborative sensing. In Mode 5, the sensing sending node is base station 51, and the sensing receiving node is terminal 53. Specifically, base station 51 sends a sensing signal to sensing target 52. After the sensing signal is reflected by sensing target 52, terminal 53 receives the reflected signal.

[0119] Mode 6: Terminal-Base Station Collaborative Sensing. In Mode 6, the sensing sending node is terminal 54, and the sensing receiving node is base station 56. Specifically, terminal 54 sends a sensing signal to sensing target 55. After the sensing signal is reflected by sensing target 55, base station 56 receives the reflected signal.

[0120] Mode 7: The sensing target is the sensing sending node. In Mode 7, the sensing sending node is terminal 57, and the sensing receiving node is base station 58. Because the sensing target (terminal 57) is the sensing sending node, the sensing signal is sent from the sensing sending node (terminal 57) to the sensing receiving node (base station 58) without reflection. Base station 58 can directly receive and interpret the sensing result.

[0121] Mode 8: The sensing target is the sensing receiving node. In Mode 8, the sensing sending node is base station 59, and the sensing receiving node is terminal 60. Since the sensing target (terminal 60) is the sensing receiving node, after receiving the sensing signal, terminal 60 needs to feed back the sensing result to base station 59, so that base station 59 can obtain the sensing result.

[0122] In the eight perception modes shown in Figure 2, there is only a single (for example, in mode one and mode two, a single node is both a perception sending node and a perception receiving node) or a pair (for example, in modes three to eight, the perception sending node and the perception receiving node are different paired nodes) perception node. In wireless communication systems, the number of terminal devices (for example, mobile phones, Internet of Things (IoT) devices, etc.) is large. When there are multiple perception nodes (including perception sending nodes and perception receiving nodes, that is, base stations, mobile phones, IoT devices, etc. that send and / or receive perception signals) around a perception target, the joint participation of multiple perception nodes in perception will be able to improve the accuracy of perception, meet more complex perception service requirements, and provide richer perception services.

[0123] Figure 3 shows a schematic structural diagram of a mobile communication system 200 provided by an exemplary embodiment of the present application. As shown in Figure 3, the mobile communication system 200 may include: UE, RAN (Radio Access Network), Core (Core Network) and DN (Data Network). Among them, UE, RAN and Core are the main components of the architecture. Logically, they can be divided into two parts: user plane and control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data. In Figure 3, the NG2 reference point is located between the RAN control plane and the Core control plane, the NG3 reference point is located between the RAN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the data network.

[0124] UE: The user interface (UE) is the gateway for mobile users to interact with the network. It provides basic computing and storage capabilities, displays service windows to users, and accepts user input. UE uses next-generation air interface technologies to establish signal and data connections with the RAN, transmitting control signals and service data to the mobile network.

[0125] RAN: Similar to base stations in traditional networks, it is deployed close to UEs and provides network access for authorized users in a specific area. It can transmit user data using tunnels of varying quality based on user level and service requirements. The RAN manages its own resources, utilizing them effectively and providing access services to UEs on demand. It also forwards control signals and user data between the UE and the core network.

[0126] Core: Responsible for maintaining mobile network subscription data, managing mobile network elements, and providing UEs with functions such as session management, mobility management, policy management, and security authentication. It provides network authentication for UEs when they attach; allocates network resources when they request services; updates network resources when they move; provides fast recovery mechanisms when they are idle; and releases network resources when they detach. It also provides data routing for UEs with service data, such as forwarding uplink data to the DN or receiving downlink data from the DN and forwarding it to the RAN for delivery to the UE.

[0127] DN: This is the data network that provides business services to users. Generally, the client is located in the UE, and the server is located in the data network. The data network can be a private network, such as a local area network, or an external network not controlled by the operator, such as the Internet. It can also be a proprietary network jointly deployed by operators, such as for configuring IMS (IP Multimedia Core Network Subsystem) services.

[0128] Figure 4 is a detailed architecture determined based on Figure 3, in which the core network user plane includes UPF (User Plane Function); the core network control plane includes AUSF (Authentication Server Function), AMF (Access and Mobility Management Function), SMF (Session Management Function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (NF Repository Function), UDM (Unified Data Management), PCF (Policy Control Function), SF (Sensing Function), AF (Application Function), and GMSC (Gateway Mobile Sensing Center). The functions of these functional entities are as follows:

[0129] UPF: performs user data packet forwarding according to the routing rules of SMF;

[0130] AUSF: performs security authentication of UE;

[0131] AMF: UE access management and mobility management;

[0132] SMF: UE session management;

[0133] NSSF: selects network slices for UE;

[0134] NEF: Opens network functions to third parties through APIs.

[0135] NRF: Provides storage and selection functions for network function entity information for other network elements;

[0136] UDM: User contract context management;

[0137] PCF: User Policy Management;

[0138] SF: Perception function, responsible for processing perception data and generating perception results;

[0139] AF (located in the data network): user application management;

[0140] GMSC: Responsible for functions related to scene perception.

[0141] In some embodiments, the GMSC may also be referred to as a GMSF (Gateway Mobile Sensing Function).

[0142] In the architecture shown in Figure 4, the N1 interface is the reference point between the UE and the AMF; the N2 interface is the reference point between the RAN and the AMF, and is used for sending NAS (Non-Access Stratum) messages, etc.; the N3 interface is the reference point between the RAN and the UPF, and is used for transmitting user plane data, etc.; the N4 interface is the reference point between the SMF and the UPF, and is used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages; the N6 interface is the reference point between the UPF and the DN, and is used for transmitting user plane data, etc.

[0143] It should be noted that the interface name between the various network elements in Figures 3 and 4 is only an example. The name of the interface in the specific implementation may be other names, and the embodiments of the present application do not specifically limit this. The names of the various network elements (such as SMF, AF, UPF, etc.) included in Figures 3 and 4 are also only examples and do not limit the functions of the network elements themselves. In 5GS and other future networks, the above-mentioned network elements may also have other names, and the embodiments of the present application do not specifically limit this. For example, in a 6G network, some or all of the above-mentioned network elements may use the terminology in 5G, or may use other names, etc., which are uniformly explained here and will not be repeated below. In addition, it should be understood that the name of the message (or signaling) transmitted between the above-mentioned network elements is also only an example and does not constitute any limitation on the function of the message itself.

[0144] This application provides an authorization mechanism for sensing nodes and / or sensing services, which is implemented based on subscription information. Exemplarily, this application includes at least one of the following two aspects:

[0145] Authorize sensing nodes based on their subscription information;

[0146] Authorizes the sensing service for the sensing target based on the sensing target's subscription information.

[0147] 1. Subscription information of the sensing node:

[0148] The subscription information of the sensing node is referred to as the first subscription information. In some embodiments, the first subscription information includes at least one of the following:

[0149] 1) A user of a first subscriber agrees that the first subscriber is associated with the sensing node;

[0150] The first subscribed user is the user associated with the sensing node. For example, if the sensing node is a mobile phone a, the user b of the mobile phone is the subscribed user associated with the mobile phone a.

[0151] 2) A first privacy profile (UE Sensing privacy profile), which is a privacy profile of a sensing node.

[0152] In some embodiments, the first privacy profile can be called a UE-aware privacy profile, a UE privacy profile, a perceived privacy profile, a privacy profile, a UE profile, a UE-aware privacy profile, etc. This application does not limit this.

[0153] In some embodiments, the first privacy profile includes at least one of the following:

[0154] Type of service;

[0155] Supports perceived business types;

[0156] · Perceive the identity of the initiating entity;

[0157] Role type

[0158] Authorized location information.

[0159] The service type is used to indicate the perceived service.

[0160] The service type is related to the sensing content, and different service types exist depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human breathing rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense human posture; the fifth service type is used to sense drones, and so on.

[0161] The Awareness Initiating Entity is the communication entity that initiates the Awareness Service. It is deployed in at least one of the following: an AF, a NF, a Awareness Client, or a UE. The Awareness Initiating Entity's identifier, such as an AF ID, a Awareness Client ID, or a UE ID, is used to identify the entity.

[0162] The role type is used to indicate the role of the sensing node in the sensing process. Exemplarily, the role type includes, but is not limited to, at least one of: sensing sending UE, sensing receiving UE, sensing reference UE, sensing located UE, sensing assistance UE, sensing relay UE, sensing server UE, and sensing node.

[0163] Authorized sensing location information is used to indicate the area information that the sensing node is authorized to sense.

[0164] The above information is all information related to the sensing node.

[0165] 2. Perceive the target's subscription information:

[0166] The subscription information of the sensing target is referred to as the second subscription information. In some embodiments, the sensing target includes at least one of the following:

[0167] Perceived UE;

[0168] First user;

[0169] Perception area.

[0170] 2.1 Perceiving UE subscription information:

[0171] In some embodiments, the sensing target is a sensing UE, and the second subscription information includes at least one of the following:

[0172] 1) User consent of the second subscriber, the second subscriber being associated with the perceiving UE;

[0173] The second subscriber is a user associated with the sensing UE. For example, if the sensing UE is a mobile phone a, the user b of the mobile phone is the second subscriber associated with the mobile phone a.

[0174] 2) A second privacy profile (UE Sensing privacy profile), which is a privacy profile of the UE sensing.

[0175] In some embodiments, the second privacy profile can be called a UE-aware privacy profile, a UE privacy profile, a perceived privacy profile, a privacy profile, a UE profile, a UE-aware privacy profile, etc. This application does not limit this.

[0176] In some embodiments, the second privacy profile includes at least one of the following:

[0177] Type of service;

[0178] The type of business being perceived;

[0179] · Perceive the identity of the initiating entity;

[0180] Perceived privacy identification;

[0181] Privacy type;

[0182] Role type

[0183] ·Perceive location information. Among them:

[0184] The service type is used to indicate the perceived service.

[0185] The service type is related to the sensing content, and different service types exist depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human breathing rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense human posture; the fifth service type is used to sense drones, and so on.

[0186] The Awareness Initiating Entity is the communication entity that initiates the Awareness Service. It is deployed in at least one of the following: an AF, a NF, a Awareness Client, or a UE. The Awareness Initiating Entity's identifier, such as an AF ID, a Awareness Client ID, or a UE ID, is used to identify the entity.

[0187] Sensing Privacy Indication (SPI): This indicator contains at least one of the following three settings: (1) Allowing sensing of a specific UE (i.e., the current UE); (2) Not allowing sensing of a specific UE; (3) Validity period. The validity period refers to the effective time corresponding to (1) or (2). For example, if the indicator contains: Allowing sensing of a specific UE and a validity period, it means that sensing is allowed during the validity period; for another example, if the indicator contains: Not allowing sensing of a specific UE and a validity period, it means that sensing is not allowed during the validity period.

[0188] Privacy type: (1) Permission is allowed without user notification; (2) Permission is allowed with user notification; (3) Permission is allowed with user notification and verification; (4) Valid time for which perception is allowed; (5) Legal geographic location for which perception is allowed. Note: The user here refers to the user associated with the perception UE.

[0189] The role type is used to indicate the role of the sensing UE in the sensing process. Exemplarily, the role type includes but is not limited to: at least one of sensing target UE and sensing UE.

[0190] The sensing location information is used to indicate the area information in which the sensing UE is allowed to be sensed, and includes specific or designated sensing location information.

[0191] The above information is all information related to the perception UE.

[0192] 2.2 Subscription information of the first user:

[0193] In some embodiments, the sensing target is a first user, and the second subscription information includes at least one of the following:

[0194] 1) the first user's identity;

[0195] 2) User consent of the first user;

[0196] 3) A third privacy profile, where the third privacy profile is a privacy profile of the UE associated with the first user.

[0197] In some embodiments, the third privacy profile can be called a UE-aware privacy profile, a UE privacy profile, a perceived privacy profile, a privacy profile, a UE profile, a UE-aware privacy profile, etc. This application does not limit this.

[0198] In some embodiments, the third privacy profile includes at least one of the following:

[0199] Type of service;

[0200] The type of business being perceived;

[0201] · Perceive the identity of the initiating entity;

[0202] Perceived privacy identification;

[0203] Privacy type;

[0204] Role type

[0205] ·Perceive location information. Among them:

[0206] The service type is used to indicate the perceived service.

[0207] The service type is related to the sensing content, and different service types exist depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human breathing rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense human posture; the fifth service type is used to sense drones, and so on.

[0208] The Awareness Initiating Entity is the communication entity that initiates the Awareness Service. It is deployed in at least one of the following: an AF, a NF, a Awareness Client, or a UE. The Awareness Initiating Entity's identifier, such as an AF ID, a Awareness Client ID, or a UE ID, is used to identify the entity.

[0209] Sensing Privacy Indication (SPI): This indicator contains at least one of the following three settings: (1) Perception allowed; (2) Perception not allowed; (3) Validity period. The validity period refers to the effective time corresponding to (1) or (2). For example, if the indicator contains "Perception allowed" and "Validity period", it means that perception is allowed during the validity period; for another example, if the indicator contains "Perception not allowed" and "Validity period", it means that perception is not allowed during the validity period.

[0210] Privacy type: (1) Permission is allowed without user notification; (2) Permission is allowed with user notification; (3) Permission is allowed with user notification and verification; (4) Permission validity period; (5) Permission legal geographic location. Note: The user here refers to the end user being perceived.

[0211] The role type is used to indicate the role of the sensing node in the sensing process. Exemplarily, the role type includes but is not limited to: assisting UE.

[0212] The perceived location information is used to indicate the area information in which the end user is allowed to be perceived, and includes specific or designated perceived location information.

[0213] The above information is all information related to the first user.

[0214] 2.3 Subscription information of sensing area:

[0215] In some embodiments, the sensing target is a sensing area, and the second subscription information includes at least one of the following:

[0216] 1) The identification of the second user;

[0217] 2) The second user agrees to be associated with the perception area. For example, if the perception area is a private area, the second user is the user being perceived within the perception area; for example, if the perception area is a private area, the second user is the owner of the perception area; for example, if the perception area is a public area, the second user is the administrator of the perception area. In some embodiments, if the perception area is a public area, there is no administrator, that is, (1) and (2) are not required.

[0218] 3) Sensing Location Profile, also known as the sensing privacy profile of the sensing area.

[0219] In some embodiments, the perception area profile includes at least one of the following:

[0220] Type of service;

[0221] The type of business being perceived;

[0222] · Perceive the identity of the initiating entity;

[0223] Perceived privacy identification;

[0224] Privacy type. Among them:

[0225] The service type is used to indicate the perceived service.

[0226] The service type is related to the sensing content, and different service types exist depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human breathing rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense human posture; the fifth service type is used to sense drones, and so on.

[0227] The Awareness Initiating Entity is the communication entity that initiates the Awareness Service. It is deployed in at least one of the following: an AF, a NF, a Awareness Client, or a UE. The Awareness Initiating Entity's identifier, such as an AF ID, a Awareness Client ID, or a UE ID, is used to identify the entity.

[0228] Sensing Privacy Indication (SPI): This indicator contains at least one of the following three settings: (1) Perception allowed; (2) Perception not allowed; (3) Validity period. The validity period refers to the effective time corresponding to (1) or (2). For example, if the indicator contains "Perception allowed" and "Validity period", it means that perception is allowed during the validity period; for another example, if the indicator contains "Perception not allowed" and "Validity period", it means that perception is not allowed during the validity period.

[0229] Privacy type: (1) Permission is allowed without user notification; (2) Permission is allowed with user notification; (3) Permission is allowed with user notification and verification; (4) Permission validity period; (5) Permission legal geographic location. Note: The user here refers to the user whose private area is being perceived, or the administrator of the public area.

[0230] The above information is all information related to the perception area.

[0231] Authorization for perception nodes:

[0232] FIG5 shows a flowchart of a method for authorizing a sensing node provided by an exemplary embodiment of the present application, the method being executed by the authorization entity 10 shown in FIG1 . The method includes all or part of the following steps:

[0233] Step 210: Obtain first subscription information of the sensing node;

[0234] Step 220: Authorize the sensing node based on the first subscription information.

[0235] The authorization entity determines whether to authorize the sensing node based on the first subscription information. If the current perception satisfies one or more or all of the information in the first subscription information, the sensing node is authorized; if the current perception does not satisfy one or more or all of the information in the first subscription information, the sensing node is not authorized.

[0236] In some embodiments, the authorization entity authorizes the sensing node if at least one of the following conditions is met:

[0237] This perception obtains the user consent of the first subscriber, who is the user associated with the perception node;

[0238] The service type sensed this time belongs to the service type of the first subscription information;

[0239] The service type sensed this time belongs to the service type supported by the first subscription information;

[0240] The identifier of the sensing initiating entity of this sensing is the same as the identifier of the sensing initiating entity in the first subscription information;

[0241] During this sensing process, the role that the sensing node needs to play belongs to the role type specified in the first subscription information;

[0242] The location or area sensed this time belongs to the location or area authorized for sensing in the first subscription information.

[0243] In some embodiments, the user consent of the first subscriber is stored in the UDM; in some embodiments, the user consent of the first subscriber is obtained through the application layer; in some embodiments, the user consent of the first subscriber comes from the perception initiating entity; in some embodiments, the user consent of the first subscriber is obtained through the connection between the authorization entity and the perception node; in some embodiments, the user consent of the first subscriber is obtained through the connection between the perception node selection entity and the perception node, and the embodiments of the present application are not limited to this.

[0244] In summary, the method provided herein determines whether a sensing node can perform perception based on its first subscription information and, if so, authorizes the sensing node. This determination of whether the sensing node can assist in this perception process fully protects the privacy of the sensing node, while respecting the wishes of the sensing node's subscriber and adhering to a first privacy profile pre-stored in the sensing node.

[0245] Based on different ways of obtaining the first subscription information of the sensing node, the above-mentioned authorization entity implements authorization of the sensing node in a manner including but not limited to at least one of the following three implementations (the order does not represent the superiority or inferiority of the implementation):

[0246] Implementation method 1: based on the first perception node list, obtaining the first subscription information of the perception node;

[0247] Implementation method 2: Based on the second perception node list, obtain the first subscription information of the perception node;

[0248] Implementation method three: When the authorization entity selects an entity for the perception node at the same time, it selects at least one perception node and obtains the first subscription information of the perception node. The following three methods are introduced respectively:

[0249] Implementation method 1:

[0250] FIG6 shows a flowchart of a method for authorizing a sensing node provided by an exemplary embodiment of the present application, the method being performed by the authorization entity shown in FIG1. ​​The method includes all or part of the following steps:

[0251] Step 310: The authorization entity receives a first sensing node list from the sensing initiation entity, where the first sensing node list is used to indicate at least one sensing node;

[0252] The authorization entity is a communication entity used to authorize the sensing node. In some embodiments, the authorization entity is deployed in any one of the AMF, base station, PCF, SF, and GMSC.

[0253] The awareness initiating entity is a communication entity for initiating awareness services. In some embodiments, the awareness initiating entity is deployed in at least one of an AF, a NF, a perception client, and a client UE.

[0254] In some embodiments, when a perception initiating entity initiates a perception request, it sends a first perception node list. This first perception node list is a list of at least one candidate perception node that the perception initiating entity recommends or requests for this perception request. The first perception node list is used to indicate at least one perception node. Exemplarily, the first perception node list carries an identifier of at least one perception node.

[0255] The perception initiating entity directly or indirectly provides the first perception node list to the authorization entity. In some embodiments, the perception initiating entity provides the first perception node list to the authorization entity via one or more core network elements. For example, the perception initiating entity first provides the first perception node list to the UDM, which then provides the first perception node list to the authorization entity.

[0256] Step 320: The authorization entity obtains the first subscription information of the sensing node;

[0257] In some embodiments, the UDM stores first subscription information of the sensing nodes, and the authorization entity obtains the first subscription information of one or more or all sensing nodes in the first sensing node list from the UDM.

[0258] The UDM can actively or passively provide the first subscription information of the sensing nodes to the authorized entity. In some embodiments, the UDM sends the first subscription information of the sensing nodes to the authorized entity. For example, the UDM sends the first sensing node list and the first subscription information of each sensing node to the authorized entity simultaneously. In some embodiments, the authorized entity sends the identifier of the sensing node to the UDM, and the authorized entity receives the first subscription information from the UDM.

[0259] In some embodiments, the authorization entity sends an identifier of a sensing node in the first sensing node list to the UDM. The UDM can query the first subscription information of the sensing node using the identifier of the sensing node and feedback the first subscription information of the sensing node to the authorization entity. The authorization entity receives the first subscription information of the sensing node fed back by the UDM.

[0260] In some embodiments, the authorization entity sends the identifiers of all sensing nodes in the first sensing node list to the UDM and requests the subscription information of all sensing nodes at one time. In some embodiments, the authorization entity sends the identifiers of all sensing nodes in the first sensing node list to the UDM multiple times and requests the first subscription information of all sensing nodes multiple times, each time requesting the first subscription information of a portion of the sensing nodes. This is not limited in the embodiments of the present application.

[0261] Step 330: The authorization entity authorizes the sensing node based on the first subscription information.

[0262] For all or part of or each of the sensing nodes in the first sensing node list, the authorization entity determines whether the sensing node can be authorized based on the first subscription information of the sensing node.

[0263] Illustratively, based on the first subscription information of each sensing node, the authorization entity authorizes the sensing node if at least one of the following conditions is met:

[0264] This perception has obtained the consent of the subscriber, who is the user associated with the perception node;

[0265] The service type sensed this time belongs to the service type of the first subscription information;

[0266] The service type sensed this time belongs to the service type supported by the first subscription information;

[0267] The identifier of the sensing initiating entity of this sensing is the same as the identifier of the sensing initiating entity in the first subscription information;

[0268] During this sensing process, the role that the sensing node needs to play belongs to the role type specified in the first subscription information;

[0269] The location or area sensed this time belongs to the location or area authorized for sensing in the first subscription information.

[0270] In summary, the method provided in this application provides a first list of sensor nodes through a sensing initiating node, uses UDM to query the first subscription information of the sensor nodes in the first list of sensor nodes, and authorizes the sensor nodes based on the first subscription information. The first list of sensor nodes is provided by the sensing initiating node.

[0271] It should be noted that step 310 and step 320 can be executed simultaneously, that is, the UDM simultaneously sends the first perception node list and the first subscription information of each perception node in the first perception node list to the authorization entity, which is not limited in this embodiment.

[0272] Implementation method 2:

[0273] FIG7 shows a flowchart of a method for authorizing a sensing node provided by an exemplary embodiment of the present application, the method being performed by the authorization entity shown in FIG1. ​​The method includes all or part of the following steps:

[0274] Step 410: The authorization entity receives a second sensor node list from the sensor node selection entity;

[0275] The sensing node selection entity is a communication entity for selecting sensing nodes. In some embodiments, the sensing node selection entity is deployed in at least one of the SF, AMF, PCF, and AF. For example, the sensing node selection entity is deployed in the AMF and uses the AMF to select the sensing nodes required for this sensing, thereby obtaining a second sensing node list. The second sensing node list includes at least one sensing node.

[0276] In some embodiments, the second sensory node list is a subset of the first sensory node list. Exemplarily, the sensory node selection entity pre-acquires the first sensory node list provided by the sensory initiation entity and selects all or part of the sensory nodes in the first sensory node list as the second sensory node list.

[0277] In some embodiments, the sensing node selection entity selects a second sensing node list based on information about each sensing node and information about the sensing target. The information about each sensing node includes at least one of the location of each sensing node and the first subscription information of each sensing node. The information about the sensing target includes at least one of the location of the sensing target and the first subscription information of the sensing target. Exemplarily, based on the location of the sensing target, the sensing node selection entity selects, from the first sensing node list, sensing nodes that are within a preset distance around the sensing target and meet the role type required for this sensing as the second sensing node list.

[0278] In some embodiments, the information used to select the sensing node may also include at least one of: power information, communication link quality between the sensing node and the sensing target, reference signal measurement results between the sensing node and the sensing target, and the distance between the sensing node and the sensing target. This embodiment does not limit this.

[0279] The sensing node selection entity provides a second sensing node list to the authorization entity. The sensing node selection entity directly or indirectly provides the first sensing node list to the authorization entity. In some embodiments, the sensing node selection entity sends the second sensing node list to the authorization entity. For example, the sensing node selection entity sends a request message to the authorization entity, the request message carrying the second sensing node list. The second sensing node list includes an identifier of at least one sensing node.

[0280] Step 420: The authorization entity obtains the first subscription information of the sensing node;

[0281] In some embodiments, the UDM stores first subscription information of the sensing nodes, and the authorization entity obtains the first subscription information of one or more or all sensing nodes in the second sensing node list from the UDM.

[0282] The UDM can actively or passively provide the authorized entity with the first subscription information of the sensing nodes. In some embodiments, the UDM sends the first subscription information of the sensing nodes to the authorized entity. For example, the UDM simultaneously sends the first sensing node list and the first subscription information of each sensing node in the first sensing node list to the authorized entity. Since the second sensing node list is a subset of the first sensing node list, it is equivalent to obtaining the first subscription information of each sensing node in the second sensing node list. In some embodiments, the authorized entity sends the identifiers of each sensing node in the first / second sensing node list to the UDM, and the authorized entity receives the first subscription information fed back by the UDM.

[0283] In some embodiments, the authorization entity sends an identifier of a sensing node in the second sensing node list to the UDM. The UDM can query the first subscription information of the sensing node using the identifier of the sensing node and feedback the first subscription information of the sensing node to the authorization entity. The authorization entity receives the first subscription information of the sensing node fed back by the UDM.

[0284] In some embodiments, the authorization entity sends the identifiers of all sensing nodes in the second sensing node list to the UDM and requests the first subscription information of all sensing nodes at one time. In some embodiments, the authorization entity sends the identifiers of all sensing nodes in the second sensing node list to the UDM multiple times and requests the first subscription information of all sensing nodes multiple times, each time requesting the first subscription information of a portion of the sensing nodes. This is not limited in the embodiments of the present application.

[0285] It should be noted that, it is not ruled out that in some embodiments, the perception node selection node obtains the first subscription information of the perception node from the UDM, and the perception node selection node sends the second perception node list and the first subscription information of each perception node in the second perception node list to the authorization entity at the same time.

[0286] Step 430: The authorization entity authorizes the sensing node based on the first subscription information;

[0287] For all or part of or each of the sensing nodes in the second sensing node list, the authorization entity determines whether the sensing node can be authorized according to the first subscription information of the sensing node.

[0288] Illustratively, based on the first subscription information of each sensing node, the authorization entity authorizes the sensing node if at least one of the following conditions is met:

[0289] This perception has obtained the consent of the subscriber, who is the user associated with the perception node;

[0290] The service type sensed this time belongs to the service type of the first subscription information;

[0291] The service type sensed this time belongs to the service type supported by the first subscription information;

[0292] The identifier of the sensing initiating entity of this sensing is the same as the identifier of the sensing initiating entity in the first subscription information;

[0293] During this sensing process, the role that the sensing node needs to play belongs to the role type specified in the first subscription information;

[0294] The location or area sensed this time belongs to the location or area authorized for sensing in the first subscription information.

[0295] Step 440: The authorization entity sends the authorization result of at least one sensing node to the sensing node selection entity.

[0296] After authorizing the sensing nodes, the authorization entity sends an authorization result of at least one sensing node to the sensing node selection entity, informing the sensing node selection entity which sensing nodes can be used for this sensing.

[0297] In some embodiments, the authorization entity sends the identifiers of authorized sensor nodes to the sensor node selection entity, while the identifiers of unauthorized sensor nodes do not need to be sent. In some embodiments, the authorization entity sends the identifier of each sensor node in the second sensor node list and indication information indicating whether the sensor node is authorized to the sensor node selection entity. For example, the indication information is represented by 1 bit. If the value is a first value, it indicates authorization; if the value is a second value, it indicates unauthorization. The first value is 1 and the second value is 0; or the first value is 0 and the second value is 1.

[0298] In some embodiments, the sensing node selection entity receives an authorization result of at least one sensing node from an authorization entity.

[0299] In summary, the method provided herein uses a sensing node selection entity to select sensing nodes, obtain a second sensing node list, and authorize the sensing nodes based on the first subscription information of the sensing nodes in the second sensing node list. Because the second sensing node list is selected by the 3GPP system based on auxiliary information such as location, battery level, and communication link quality, perception is more accurate.

[0300] In step 410, the sensing node selection entity providing the second sensing node list to the authorization entity may be implemented as an independent embodiment, for example, implemented separately as a sensing node authorization method.

[0301] In step 440, the sensing node selection entity receives the authorization result of at least one sensing node from the authorization entity, which can be implemented as an independent embodiment, for example, implemented separately as a sensing node authorization method.

[0302] Implementation method three:

[0303] FIG8 shows a flowchart of a method for authorizing a sensing node according to an exemplary embodiment of the present application, the method being performed by the authorization entity shown in FIG1 . The method includes at least one of the following steps:

[0304] Step 510: The authorization entity obtains a first sensing node list from the sensing initiating entity;

[0305] In this embodiment, the authorization entity is also the perception node selection entity, or the authorization entity and the perception node selection entity are deployed in the same node or network element.

[0306] The first sensing node list is a list of at least one candidate sensing node requested or recommended by the sensing initiating entity for this sensing. The first sensing node list is used to indicate at least one sensing node. Exemplarily, the first sensing node list carries an identifier of at least one sensing node.

[0307] The sensing initiating entity directly or indirectly provides the first sensing node list to the authorization entity. In some embodiments, the first sensing node list is sent by the sensing initiating entity to the authorization entity, or the first sensing node list is sent indirectly by the UDM to the authorization entity.

[0308] In some embodiments, the perception initiating entity generates a first perception node list for this perception, and the perception initiating entity sends the first perception node list to the authorization entity, or the perception initiating entity sends the first perception node list to the UDM, and the UDM stores the first perception node list, and the UDM then sends the first perception node list to the authorization entity.

[0309] Step 520: The authorization entity selects at least one sensing node according to the first sensing node list and the location of the sensing target;

[0310] The authorization entity selects at least one sensing node from the first sensing node list according to the location of the sensing target to generate a second sensing node list.

[0311] In some embodiments, the authorization entity selects, from the first perception node list, perception nodes located within a preset distance around the perception target as the second perception node list.

[0312] In some embodiments, the authorization entity selects the second list of sensing nodes based on information about each sensing node and information about a sensing target. The information about each sensing node includes at least one of a location of each sensing node and first subscription information of each sensing node. The information about the sensing target includes at least one of a location of the sensing target and first subscription information of the sensing target.

[0313] In some embodiments, the information used to select the sensing node may also include at least one of: power information, communication link quality between the sensing node and the sensing target, reference signal measurement results between the sensing node and the sensing target, and the distance between the sensing node and the sensing target. This embodiment does not limit this.

[0314] For example, based on the location of the sensing target, the sensing node selection entity selects, from the first sensing node list, sensing nodes that are within a preset distance around the sensing target and that meet the role type required for this sensing, as the second sensing node list. For another example, in the first sensing node list {a, b, c}, sensing node a supports sensing locations within range a1, sensing node b supports sensing locations within range b1, and sensing node c supports sensing locations within range c1. The sensing target is located in range d, which falls within range a1 and range c1 but not range b1. In this case, the authorization entity selects sensing nodes a and c as the sensing nodes for this sensing.

[0315] Step 530: The authorization entity obtains the first subscription information of the sensing node;

[0316] In some embodiments, the UDM stores first subscription information of the sensing nodes, and the authorization entity obtains the first subscription information of one or more or all sensing nodes in the second sensing node list from the UDM.

[0317] The UDM can actively or passively provide the authorized entity with the first subscription information of the sensing nodes. In some embodiments, the UDM sends the first subscription information of the sensing nodes to the authorized entity. For example, the UDM simultaneously sends the first sensing node list and the first subscription information of each sensing node in the first sensing node list to the authorized entity. Since the second sensing node list is a subset of the first sensing node list, it is equivalent to obtaining the first subscription information of each sensing node in the second sensing node list. In some embodiments, the authorized entity sends the identifiers of each sensing node in the first / second sensing node list to the UDM, and the authorized entity receives the first subscription information fed back by the UDM.

[0318] In some embodiments, the authorization entity sends an identifier of a sensing node in the second sensing node list to the UDM. The UDM can query the first subscription information of the sensing node using the identifier of the sensing node and feedback the first subscription information of the sensing node to the authorization entity. The authorization entity receives the first subscription information of the sensing node fed back by the UDM.

[0319] In some embodiments, the authorization entity sends the identifiers of all sensing nodes in the second sensing node list to the UDM, requesting the identifiers of all sensing nodes at once. In some embodiments, the authorization entity sends the identifiers of all sensing nodes in the second sensing node list to the UDM multiple times, requesting the first subscription information of all sensing nodes multiple times, each time requesting the first subscription information of a portion of the sensing nodes. This is not limited in the embodiments of the present application.

[0320] Step 540: The authorization entity authorizes the sensing node based on the first subscription information.

[0321] For all or part of or each of the sensing nodes in the second sensing node list, the authorization entity determines whether the sensing node can be authorized according to the first subscription information of the sensing node.

[0322] Illustratively, based on the first subscription information of each sensing node, the authorization entity authorizes the sensing node if at least one of the following conditions is met:

[0323] This perception has obtained the consent of the subscriber, who is the user associated with the perception node;

[0324] The service type sensed this time belongs to the service type of the first subscription information;

[0325] The service type sensed this time belongs to the service type supported by the first subscription information;

[0326] The identifier of the sensing initiating entity of this sensing is the same as the identifier of the sensing initiating entity in the first subscription information;

[0327] During this sensing process, the role that the sensing node needs to play belongs to the role type specified in the first subscription information;

[0328] The location or area sensed this time belongs to the location or area authorized for sensing in the first subscription information.

[0329] To sum up, in the method provided by the present application, when the authorization entity also serves as the perception node selection entity, the perception node selection entity authorizes at least one perception node on its own after selecting at least one perception node, thereby reducing the number of communications between the perception node selection entity and other entities and saving communication resources between the perception node selection entity and other entities.

[0330] In step 510, the perception initiating entity provides the first perception node list to the authorization entity, which can be implemented as an independent embodiment, such as being implemented separately as a perception node authorization method; in step 510, the UDM sends the first subscription information of the perception node to the authorization entity, which can be implemented as an independent embodiment, such as being implemented separately as a perception node authorization method.

[0331] In step 520, the authorization entity is also the perception node generation entity, and the generation of the second perception node list can be implemented as an independent embodiment, such as being implemented separately as a perception node authorization method; step 520 can be implemented as an independent embodiment, such as being implemented separately as a perception node authorization method.

[0332] Authorization of sensing services for sensing targets:

[0333] FIG9 shows a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application, which is executed by the authorization entity 10 shown in FIG1 . The method includes all or part of the following steps:

[0334] Step 610: Acquire second subscription information of the sensing target;

[0335] Step 620: Authorize the sensing service for the sensing target based on the second subscription information.

[0336] The authorization entity determines whether the perception service for the perception target can be authorized based on the second subscription information. If the current perception satisfies one or more or all of the information in the second subscription information, the perception service for the perception target is authorized; if the current perception does not satisfy one or more or all of the information in the second subscription information, the perception service for the perception target is not authorized.

[0337] In some embodiments, the authorization entity authorizes the sensing service for the sensing target when at least one of the following conditions is met:

[0338] This perception has obtained the user's consent;

[0339] The service type sensed this time belongs to the service type of the second subscription information;

[0340] The service type sensed this time belongs to the service type supported by the second subscription information;

[0341] The identifier of the sensing initiating entity of this sensing is the same as the identifier of the sensing initiating entity in the second subscription information;

[0342] During this sensing process, the role that the sensing target needs to play belongs to the role type specified in the second subscription information;

[0343] The perception privacy flag in the second subscription information indicates that perception is allowed; or the perception privacy flag in the second subscription information indicates that perception is allowed, and the time of this perception is within the valid time;

[0344] This perception notifies the user according to the privacy type in the second subscription information;

[0345] This perception was verified according to the privacy type in the second subscription information;

[0346] The time of this perception belongs to the valid time of the privacy type of the second subscription information;

[0347] The location or area sensed this time belongs to the location or area authorized for sensing in the second subscription information.

[0348] In summary, the method provided in this application determines whether a perception target can be perceived based on the second subscription information of the perception target. If so, the perception service for the perception target is authorized. This determination of whether a perception target can be perceived fully protects the privacy of the perception target while respecting the wishes of the subscriber of the perception target and adhering to the privacy profile pre-stored in the perception target.

[0349] As mentioned above, the second subscription information includes at least one of user consent and a configuration file. The configuration file is usually provided by the UDM. Depending on how the user consent is obtained, the authorization entity implements the authorization of the perception service for the perception target in the following ways, including but not limited to at least one of the following three ways (the order does not represent the advantages and disadvantages of the implementation methods):

[0350] Implementation method 4: Obtain the second subscription information (user consent and / or configuration file) from the UDM;

[0351] The second subscription information provided by the UDM is at least one of user consent and a profile. The sensing target is a sensing UE, and the profile is a second privacy profile; or the sensing target is a first user, and the profile is a third privacy profile; or the sensing target is a sensing area, and the profile is a sensing area profile.

[0352] Implementation method 5: Obtain the configuration file from the UDM and obtain user consent from the perception initiating entity;

[0353] Implementation method six: Obtain the configuration file from the UDM and obtain user consent from the UE.

[0354] Implementation method four:

[0355] FIG10 shows a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application. The method is executed by the authorization entity 10 shown in FIG1 . The method includes all or part of the following steps:

[0356] Step 710: The authorization entity obtains the second subscription information of the perception target from the UDM;

[0357] The UDM stores the second subscription information of the sensing target. The authorization entity obtains the second subscription information of the sensing target from the UDM.

[0358] The UDM can actively or passively provide the authorized entity with the second subscription information of the sensing target. In some embodiments, the UDM sends the second subscription information of the sensing target to the authorized entity. In some embodiments, the authorized entity sends the identifier of the sensing target to the UDM. The UDM can query the second subscription information based on the identifier of the sensing target and feedback the second subscription information to the authorized entity. The authorized entity receives the second subscription information feedback from the UDM.

[0359] In some embodiments, when there are multiple sensing targets, the authorization entity sends the identifiers of all sensing targets to the UDM and requests the second subscription information of all sensing targets at one time. In some embodiments, the authorization entity sends the identifiers of all sensing targets to the UDM multiple times and requests the second subscription information of all sensing targets multiple times, each time requesting the second subscription information of a portion of the sensing targets. This is not limited in the embodiments of the present application.

[0360] Step 720: The authorization entity authorizes the awareness service for the awareness target based on the second subscription information.

[0361] The authorization entity determines whether the perception service for the perception target can be authorized based on the second subscription information. If the current perception satisfies one or more or all of the information in the second subscription information, the perception service for the perception target is authorized; if the current perception does not satisfy one or more or all of the information in the second subscription information, the perception service for the perception target is not authorized.

[0362] In some embodiments, the authorization entity authorizes the sensing service for the sensing target when at least one of the following conditions is met:

[0363] This perception has obtained the user's consent;

[0364] The service type sensed this time belongs to the service type of the second subscription information;

[0365] The service type sensed this time belongs to the service type supported by the second subscription information;

[0366] The identifier of the sensing initiating entity of this sensing is the same as the identifier of the sensing initiating entity in the second subscription information;

[0367] During this sensing process, the role that the sensing target needs to play belongs to the role type specified in the second subscription information;

[0368] The perception privacy flag in the second subscription information indicates that perception is allowed; or the perception privacy flag in the second subscription information indicates that perception is allowed, and the time of this perception is within the valid time;

[0369] This perception notifies the user according to the privacy type in the second subscription information;

[0370] This perception was verified according to the privacy type in the second subscription information;

[0371] The time of this perception belongs to the valid time of the privacy type of the second subscription information;

[0372] The location or area sensed this time belongs to the location or area authorized for sensing in the second subscription information.

[0373] In summary, the method provided in this embodiment uses the second subscription information of a sensing target to determine whether the sensing target can be sensed. If so, the sensing target is authorized. This determination of whether the sensing target can be sensed this time is performed while respecting the user's wishes associated with the sensing target and adhering to the pre-stored profile of the sensing target, thereby fully protecting the privacy of the sensing target.

[0374] Implementation method five:

[0375] FIG11 shows a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application. The method is executed by the authorization entity 10 shown in FIG1 . The method includes all or part of the following steps:

[0376] Step 810: The authorization entity obtains user consent provided by the perception initiating entity;

[0377] The perception initiating entity may obtain user consent in advance.

[0378] In some embodiments, when the perception target is a perception UE, the perception initiating entity establishes a connection with the perception UE, such as a TLS connection. The perception initiating entity obtains user consent of a second subscribed user associated with the perception UE through the TLS connection. When the perception target is a first user, the perception initiating entity establishes a connection with the user UE, such as a TLS connection. The perception initiating entity obtains user consent of the first user associated with the user UE through the TLS connection. When the perception target is a perception area, the perception initiating entity establishes a connection with the user UE of the second user, such as a TLS connection. The perception initiating entity obtains user consent of the second user through the TLS connection.

[0379] In some embodiments, the awareness initiating entity is deployed in the awareness UE or the user UE, and the awareness initiating entity obtains user consent through the application layer.

[0380] After obtaining user consent, the perception initiating entity provides it to the authorization entity directly or indirectly. In some embodiments, the perception initiating entity establishes a connection with the authorization entity and provides the user consent to the authorization entity through the connection. In some embodiments, the perception initiating entity sends the user consent to one or more core network elements (such as UDM), which then provide the user consent to the authorization entity.

[0381] Step 820: The authorized entity obtains the configuration file of the sensing target from the UDM;

[0382] The UDM stores the configuration files of the sensing targets. The authorized entity obtains the configuration files of the sensing targets from the UDM.

[0383] The UDM can actively or passively provide the authorized entity with a profile of a perceived target. In some embodiments, the UDM sends the profile of the perceived target to the authorized entity. In some embodiments, the authorized entity sends the identifier of the perceived target to the UDM. The UDM can then query the profile using the identifier of the perceived target and provide the profile back to the authorized entity. The authorized entity then receives the profile from the UDM.

[0384] In some embodiments, when there are multiple sensing targets, the authorized entity sends the identifiers of all sensing targets to the UDM and requests the configuration files of all sensing targets at once. In some embodiments, the authorized entity sends the identifiers of all sensing targets to the UDM multiple times and requests the configuration files of all sensing targets multiple times, each time requesting the configuration files of a portion of the sensing targets. This is not limited in the embodiments of the present application.

[0385] In some embodiments, the awareness initiating entity first sends the user consent to the UDM, and the UDM provides the user consent and the configuration file to the authorization entity simultaneously or separately.

[0386] Step 830: The authorization entity authorizes the awareness service for the awareness target based on the user consent and the configuration file.

[0387] The authorization entity determines whether the perception service for the perception target can be authorized based on the user's consent and the configuration file. If the current perception satisfies one or more or all of the information in the second subscription information, the perception service for the perception target is authorized; if the current perception does not satisfy one or more or all of the information in the second subscription information, the perception service for the perception target is not authorized.

[0388] In some embodiments, the authorization entity authorizes the sensing service for the sensing target when at least one of the following conditions is met:

[0389] This perception has obtained the user's consent;

[0390] The service type sensed this time belongs to the service type in the configuration file;

[0391] The service type detected this time is one of the service types supported by the configuration file;

[0392] The ID of the sensing initiating entity for this sensing is the same as the ID of the sensing initiating entity in the configuration file;

[0393] During this sensing process, the role that the sensing target needs to play belongs to the role type in the configuration file;

[0394] The privacy awareness flag in the configuration file indicates that awareness is allowed; or, the privacy awareness flag in the configuration file indicates that awareness is allowed, and the time of this awareness is within the valid time;

[0395] This awareness process notified the user based on the privacy type specified in the configuration file.

[0396] The time of this perception belongs to the valid time of the privacy type of the profile;

[0397] The location or area sensed this time is one of the locations or areas authorized for sensing in the profile.

[0398] To sum up, the method provided in this embodiment and the method provided in this application provide user consent through the perception initiation node. Since in many perception scenarios, the perception initiation node has already obtained the user consent associated with the perception target, there is no need for the authorization entity to obtain the user consent associated with the perception target again, which reduces the communication between the authorization entity and the perception target and improves the authorization efficiency of the perception service.

[0399] Implementation method six:

[0400] FIG12 shows a flowchart of a method for authorizing a perception service provided by an exemplary embodiment of the present application. The method is executed by the authorization entity 10 shown in FIG1 . The method includes all or part of the following steps:

[0401] Step 910: The authorization entity obtains user consent provided by the awareness UE or the user UE;

[0402] In some embodiments, when the sensing target is a sensing UE, the authorization entity establishes a connection, such as a NAS connection, with the sensing UE. The authorization entity obtains user consent from a second subscriber associated with the sensing UE through the NAS connection. When the sensing target is a first subscriber, the authorization entity establishes a connection, such as a NAS connection, with the subscriber UE. The authorization entity obtains user consent from the first subscriber associated with the subscriber UE through the NAS connection. When the sensing target is a sensing area, the authorization entity establishes a connection, such as a NAS connection, with the subscriber UE of a second subscriber. The authorization entity obtains user consent from the second subscriber through the NAS connection.

[0403] In some embodiments, the connection established between the authorization entity and the perception UE may also be a user plane connection, or an application layer-based connection. The specific connection method is related to the selection of the authorization entity, and the embodiments of the present application do not limit this.

[0404] Step 920: The authorized entity obtains the configuration file of the sensing target from the UDM;

[0405] The UDM stores the configuration files of the sensing targets. The authorized entity obtains the configuration files of the sensing targets from the UDM.

[0406] The UDM can actively or passively provide the authorized entity with a profile of a perceived target. In some embodiments, the UDM sends the profile of the perceived target to the authorized entity. In some embodiments, the authorized entity sends the identifier of the perceived target to the UDM. The UDM can then query the profile using the identifier of the perceived target and provide the profile back to the authorized entity. The authorized entity then receives the profile from the UDM.

[0407] In some embodiments, when there are multiple sensing targets, the authorized entity sends the identifiers of all sensing targets to the UDM and requests the configuration files of all sensing targets at once. In some embodiments, the authorized entity sends the identifiers of all sensing targets to the UDM multiple times and requests the configuration files of all sensing targets multiple times, each time requesting the configuration files of a portion of the sensing targets. This is not limited in the embodiments of the present application.

[0408] In some embodiments, the awareness initiating entity first sends the user consent to the UDM, and the UDM provides the user consent and the configuration file to the authorization entity simultaneously or separately.

[0409] Step 930: The authorization entity authorizes the awareness service for the awareness target based on the user consent and the configuration file.

[0410] The authorization entity determines whether the perception service for the perception target can be authorized based on the user's consent and the configuration file. If the current perception satisfies one or more or all of the information in the second subscription information, the perception service for the perception target is authorized; if the current perception does not satisfy one or more or all of the information in the second subscription information, the perception service for the perception target is not authorized.

[0411] In some embodiments, the authorization entity authorizes the sensing service for the sensing target when at least one of the following conditions is met:

[0412] This perception has obtained the user's consent;

[0413] The service type sensed this time belongs to the service type in the configuration file;

[0414] The service type detected this time is one of the service types supported by the configuration file;

[0415] The ID of the sensing initiating entity for this sensing is the same as the ID of the sensing initiating entity in the configuration file;

[0416] During this sensing process, the role that the sensing target needs to play belongs to the role type in the configuration file;

[0417] The privacy awareness flag in the configuration file indicates that awareness is allowed; or, the privacy awareness flag in the configuration file indicates that awareness is allowed, and the time of this awareness is within the valid time;

[0418] This awareness process notified the user based on the privacy type specified in the configuration file.

[0419] The time of this perception belongs to the valid time of the privacy type of the profile;

[0420] The location or area sensed this time is one of the locations or areas authorized for sensing in the profile.

[0421] To sum up, the method provided in this embodiment and the method provided in this application obtain user consent by the authorization node itself, without the need for the perception initiating entity to obtain user consent, thereby reducing the communication between the perception initiating entity and the authorization entity, reducing the communication between the perception initiating entity and the perception target / user UE, and improving the authorization efficiency of the perception service.

[0422] In some embodiments, at the end of the perception phase, the authorization entity or GMSC needs to provide the perception result to the perception initiating entity. In some embodiments, upon obtaining the consent of the user corresponding to the perception target, the perception result is sent to the perception result requester; and / or, in some embodiments, the perception result is sent to the perception result requester, with the perception target information in the perception result being anonymized. In some embodiments, the perception result requester can be the perception initiating entity, another entity, or another network element, and the embodiments of the present application do not limit the perception result requester.

[0423] In some embodiments, the PCF further generates an authorization policy for the sensing terminal UE based on the subscription information of the sensing terminal UE. The authorization policy is used to indicate at least one of the following:

[0424] The first PLMN (Public Land Mobile Network) that allows the sensing UE to use the sensing service;

[0425] • A second PLMN that allows other UEs to use the aware services of the aware UE.

[0426] Since the perception target can be at least one of a perception UE, a first user, and a perception area, and the embodiments of authorization of a perception service for the perception target and authorization of a perception service for the perception target in the above embodiments can also be combined in pairs, the following introduces different combinations of different perception target types and different implementation methods (not all combinations, only some combinations are selected for illustration).

[0427] 1. The sensing target is the UE, and the sensing service is authorized for the sensing target;

[0428] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fifth implementation is as follows:

[0429] FIG13 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. In this embodiment, the GMSC is used to authorize the sensing service for the sensing target. The method includes at least one of the following steps:

[0430] Step 1001: A perception initiating entity establishes a TLS (Transport Layer Security) connection with a perception UE;

[0431] The perception initiating entity is configured to initiate a perception service for the perception UE. In some embodiments, the perception initiating entity obtains an identifier of the perception UE. In some embodiments, the perception initiating entity obtains user consent from the second subscriber, such as the privacy terms before accessing the mobile app.

[0432] Step 1002: Detect service authorization between UE and PCF;

[0433] In some embodiments, the PCF generates and configures an authorization policy to the aware UE by sensing the UE's subscription information.

[0434] In some embodiments, the PCF generates and configures an authorization policy to the aware UE by sensing the second privacy profile of the UE and the user consent that may be provided by the aware initiating entity.

[0435] In some embodiments, the UE declares its role to the network side, for example, the UE declares that it is a perception target UE, and after the PCF checks the second privacy profile of the perception UE, it generates and configures an authorization policy to the perception UE.

[0436] In some embodiments, the UE declares its role to the network side, for example, the UE declares that it is a perception target UE, and after the PCF checks the second privacy profile of the perception UE and the user consent provided by the perception initiating entity, it generates and configures the authorization policy to the perception UE.

[0437] Step 1003: The sensing initiating entity sends a sensing service request (Sensing Service Request) to the GMSC;

[0438] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC.

[0439] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC via the NEF.

[0440] In some embodiments, the sensing service request includes at least: a sensing UE ID. Optionally, it also includes at least one of the following parameters:

[0441] A sense-initiating entity identifier, which is used to indicate the unique identifier of the sense-initiating entity. Each sense-initiating entity has its own corresponding sense-initiating entity identifier.

[0442] Location information, used to indicate the area in which the sensing UE is allowed to be sensed, including specific or designated sensing location information;

[0443] The user of the second subscriber agrees that the second subscriber is associated with the sensing UE; the second subscriber is the user associated with the sensing UE. For example, if the sensing UE is a mobile phone a, the user b of the mobile phone is the second subscriber associated with the mobile phone a;

[0444] Service type: Service type is related to the sensing content and varies depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human respiratory rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense human posture; the fifth service type is used to sense drones, and so on.

[0445] Step 1004: The authorization entity requests the second subscription information from the UDM (Nudm_SDM_GET Request);

[0446] In some embodiments, the request message includes a SUPI (Subscription Permanent Identifier), which is an identifier of the aware UE.

[0447] Step 1005: UDM retrieves the second subscription information;

[0448] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0449] Step 1006: The UDM responds with the second subscription information to the authorization entity (Nudm_SDM_GET Response);

[0450] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0451] Step 1007: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0452] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second subscribed user obtained from the awareness initiating entity.

[0453] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the second privacy profile of the first user obtained from the UDM.

[0454] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second subscribing user obtained from the awareness initiating entity and the second privacy profile of the first user obtained from the UDM.

[0455] Step 1008: The authorized entity sends a sensing information provision request (Namf_Sensing_ProvideSensingInfo Request) to the AMF;

[0456] In some embodiments, the awareness information provision request carries a SUPI, which is an identifier of the awareness UE.

[0457] Step 1009: AMF selects SF;

[0458] Step 1010: Perception process;

[0459] In some embodiments, the 5GC and the perception node perform a perception process for the perception UE.

[0460] In some embodiments, the 5GC includes at least one of the following network elements:

[0461] AMF;

[0462] PCF;

[0463] SF.

[0464] Step 1011: AMF sends a sensing information provision response (Namf_Sensing_ProvideSensingInfo Response) to the GMSC;

[0465] The sensing information provision response carries a sensing result obtained based on sensing measurements of one or more sensing nodes.

[0466] Step 1012: GMSC performs a privacy check.

[0467] In some embodiments, the GMSC sends the perception result to the perception initiating entity upon obtaining consent from the user corresponding to the perception UE.

[0468] Step 1013: The GMSC sends a sensing service response (Sensing Service Response) to the sensing initiating entity;

[0469] In some embodiments, the information of the sensing UE in the sensing result is anonymized.

[0470] In some embodiments, step 1001 , step 1012 , and step 1013 are optional.

[0471] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fifth implementation is as follows:

[0472] FIG14 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the sensing service for the sensing target. Unlike FIG13 , this embodiment deletes step 1007 and adds steps 1014 to 1019 between steps 1009 and 1010. The method includes at least one of the following steps:

[0473] Step 1014: The AMF sends a sensing determination request (Nsf_Sensing_DetermineSensing Request) to the GMSC;

[0474] Step 1015: The GMSC requests the UDM for the second subscription information;

[0475] In some embodiments, the request message includes a SUPI, which is an identifier of the aware UE.

[0476] Step 1016: UDM retrieves the second subscription information;

[0477] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0478] Step 1017: UDM responds with the second subscription information to the GMSC;

[0479] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0480] Step 1018: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0481] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second subscribed user obtained from the awareness initiating entity.

[0482] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the second privacy profile of the awareness UE obtained from the UDM.

[0483] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second subscribed user obtained from the awareness initiating entity and the second privacy profile of the awareness UE obtained from the UDM.

[0484] Step 1019: The authorized entity initiates a sensing determination response (Nsf_Sensing_DetermineSensing Response) to the AMF.

[0485] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the AMF, the embodiment of the above implementation mode 5 is as follows:

[0486] FIG15 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the perception service for the perception target. Unlike FIG13 , this embodiment deletes step 1007 and adds steps 1020 to 1023 between steps 1009 and 1010. The method includes at least one of the following steps:

[0487] Step 1020: The authorization entity requests the second subscription information from the UDM;

[0488] In some embodiments, the request message includes a SUPI, which is an identifier of the aware UE.

[0489] Step 1021: UDM retrieves the second subscription information;

[0490] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0491] Step 1022: The UDM responds with the second subscription information to the authorization entity;

[0492] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0493] Step 1023: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0494] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second subscribed user obtained from the awareness initiating entity.

[0495] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the second privacy profile of the awareness UE obtained from the UDM.

[0496] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second subscribed user obtained from the awareness initiating entity and the second privacy profile of the awareness UE obtained from the UDM.

[0497] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the above implementation mode 6 is as follows:

[0498] FIG16 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the perception service for the perception target. Unlike FIG14 , this embodiment deletes step 1007 and adds steps 1024 to 1027 between steps 1008 and 1009. The method includes at least one of the following steps:

[0499] Step 1024: AMF and the perceived UE send a Network Trigger Service Request.

[0500] In some embodiments, the AMF establishes a NAS connection with the aware UE for network communication.

[0501] In some embodiments, the authorized entity, such as GMSC, base station, PCF, SF, etc., may also establish a connection with the aware UE.

[0502] In some embodiments, the PCF establishes a NAS connection with the aware UE for network communication.

[0503] In some embodiments, the GMSC establishes a user plane connection with the aware UE to perform network communication.

[0504] In some embodiments, the base station establishes an access layer connection with the perceptual UE to perform network communication.

[0505] In some embodiments, the SF establishes a user plane or application layer-based connection with the aware UE to perform network communication.

[0506] In some embodiments, the connection established between the authorization entity and the perception UE may also be a user plane connection, or an application layer-based connection. The specific connection method is related to the selection of the authorization entity, and the embodiments of the present application do not limit this.

[0507] Step 1025: The AMF sends a Sensing Notification Invoke Request to the sensing UE.

[0508] In some embodiments, the AMF sends an awareness notification invocation request to the awareness UE via a NAS connection.

[0509] Step 1026: The perceiving UE obtains user consent of the second subscribed user;

[0510] Step 1027: The sensing UE sends a Sensing Notification Invoke Response to the AMF.

[0511] In some embodiments, the aware UE sends an awareness notification invocation response to the AMF via a NAS connection.

[0512] In some embodiments, the connection through which the AMF sends the perception call response can also be a user plane connection, or a connection based on the application layer. The specific connection method is related to the selection of the authorization entity, and the embodiments of the present application are not limited to this.

[0513] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the AMF, the embodiment of the above implementation mode 6 is as follows:

[0514] Figure 17 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the perception service for the perception target. Unlike Figure 15, this embodiment deletes step 1007 and adds steps 1024 to 1027 between steps 1008 and 1009. The specific steps are as shown in the embodiment shown in Figure 16.

[0515] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fourth implementation is as follows:

[0516] FIG18 is a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the perception service for the perception target. Unlike FIG13 , this embodiment expands steps 1005 and 1006, and the method includes at least one of the following steps:

[0517] Step 1005: UDM retrieves the second subscription information;

[0518] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0519] In some embodiments, the UDM retrieves the user consent of the second subscribing user based on the SUPI.

[0520] In some embodiments, the UDM retrieves the second privacy profile of the aware UE and the user consent of the second subscribing user based on the SUPI.

[0521] Step 1006: The UDM responds with the second subscription information to the authorization entity;

[0522] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0523] In some embodiments, the response message includes the SUPI and the user consent of the second subscribing user.

[0524] In some embodiments, the response message includes the SUPI, the user consent of the second subscribing user, and the second privacy profile of the aware UE.

[0525] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fourth implementation is as follows:

[0526] FIG19 is a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the perception service for the perception target. Unlike FIG14 , this embodiment expands steps 1005, 1006, 1016, and 1017, and the method includes at least one of the following steps:

[0527] Step 1005: UDM retrieves the second subscription information;

[0528] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0529] In some embodiments, the UDM retrieves the user consent of the second subscribing user based on the SUPI.

[0530] In some embodiments, the UDM retrieves the second privacy profile of the aware UE and the user consent of the second subscribing user based on the SUPI.

[0531] Step 1006: The UDM responds with the second subscription information to the GMSC;

[0532] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0533] In some embodiments, the response message includes the SUPI and the user consent of the second subscribing user.

[0534] In some embodiments, the response message includes the SUPI, the user consent of the second subscribing user, and the second privacy profile of the aware UE.

[0535] Step 1016: UDM retrieves the second subscription information;

[0536] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0537] In some embodiments, the UDM retrieves the user consent of the second subscribing user based on the SUPI.

[0538] In some embodiments, the UDM retrieves the second privacy profile of the aware UE and the user consent of the second subscribing user based on the SUPI.

[0539] Step 1017: UDM responds with the second subscription information to the GMSC;

[0540] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0541] In some embodiments, the response message includes the SUPI and the user consent of the second subscribing user.

[0542] In some embodiments, the response message includes the SUPI, the user consent of the second subscribing user, and the second privacy profile of the aware UE.

[0543] For the perception initiating entity deployed in AF / NF / perception client / client UE, and the authorization entity deployed in AMF, the embodiment of the above implementation mode 4 is as follows:

[0544] Figure 20 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the perception service for the perception target. Unlike Figure 15, this embodiment expands steps 1005, 1006, 1021, and 1022, and the method includes at least one of the following steps:

[0545] Step 1005: UDM retrieves the second subscription information;

[0546] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0547] In some embodiments, the UDM retrieves the user consent of the second subscribing user based on the SUPI.

[0548] In some embodiments, the UDM retrieves the second privacy profile of the aware UE and the user consent of the second subscribing user based on the SUPI.

[0549] Step 1006: UDM responds to the AMF with the second subscription information.

[0550] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0551] In some embodiments, the response message includes the SUPI and the user consent of the second subscribing user.

[0552] In some embodiments, the response message includes the SUPI, the user consent of the second subscribing user, and the second privacy profile of the aware UE.

[0553] Step 1021: UDM retrieves the second subscription information;

[0554] In some embodiments, the UDM retrieves the second privacy profile of the aware UE based on the SUPI.

[0555] In some embodiments, the UDM retrieves the user consent of the second subscribing user based on the SUPI.

[0556] In some embodiments, the UDM retrieves the second privacy profile of the aware UE and the user consent of the second subscribing user based on the SUPI.

[0557] Step 1022: UDM responds to the AMF with the second subscription information.

[0558] In some embodiments, the response message includes the SUPI and the second privacy profile of the aware UE.

[0559] In some embodiments, the response message includes the SUPI and the user consent of the second subscribing user.

[0560] In some embodiments, the response message includes the SUPI, the user consent of the second subscribing user, and the second privacy profile of the aware UE.

[0561] If the perception initiating entity is deployed on the perception UE, it is considered that the user's consent has been obtained and there is no need to authorize the perception initiating node.

[0562] 2. The sensing target is the first user, and the sensing service is authorized for the sensing target;

[0563] When the sensing target is the first user, it may be necessary to use the UE used by the first user to assist in obtaining the second subscription information.

[0564] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fifth implementation is as follows:

[0565] FIG21 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. In this embodiment, the GMSC is used to authorize the sensing service for the sensing target. The method includes at least one of the following steps:

[0566] Step 1101: The perception initiating entity establishes a TLS connection with the user UE;

[0567] The user UE is a UE associated with the first user.

[0568] A perception initiating entity is configured to initiate a perception service for a first user / user UE. In some embodiments, the perception initiating entity obtains an identifier of the first user / user UE. In some embodiments, the perception initiating entity obtains user consent from the first user, such as the privacy terms before accessing a mobile app.

[0569] Step 1102: Service authorization between the first user / user UE and the PCF;

[0570] In some embodiments, the PCF generates and configures an authorization policy to the user UE through the second subscription information of the first user.

[0571] In some embodiments, the PCF generates and configures an authorization policy to the user UE through the third privacy profile of the first user and the user consent of the first user.

[0572] In some embodiments, the UE declares its role to the network side, for example, the UE declares that it is a perception target UE, and after the PCF checks the UE third privacy profile of the user UE, it generates and configures an authorization policy to the perception UE.

[0573] In some embodiments, the UE declares its role to the network side, for example, the UE declares that it is a perception target UE, and after the PCF checks the third privacy profile of the user UE and the user consent of the first user, it generates and configures the authorization policy to the perception UE.

[0574] Step 1103: The sensing initiating entity sends a sensing service request to the GMSC;

[0575] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC.

[0576] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC via the NEF.

[0577] In some embodiments, the sensing service request includes at least: a first user ID and / or a user UE ID. Optionally, it also includes at least one of the following parameters:

[0578] A sense-initiating entity identifier, which is used to indicate the unique identifier of the sense-initiating entity. Each sense-initiating entity has its own corresponding sense-initiating entity identifier.

[0579] Location information, used to indicate the area in which the UE is allowed to be sensed, including specific or designated sensing location information;

[0580] The user of the first user agrees that the first user is associated with the user UE; for example, the user UE is a UE used by the first user;

[0581] Service type: Service type is related to the sensing content and varies depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human respiratory rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense human posture; the fifth service type is used to sense drones, and so on.

[0582] Step 1104: The authorization entity requests the second subscription information from the UDM;

[0583] In some embodiments, the request message includes a SUPI, which is an identifier of the first user and / or user UE.

[0584] Step 1105: UDM retrieves the second subscription information;

[0585] In some embodiments, the UDM retrieves a third privacy profile of the first user based on the SUPI.

[0586] Step 1106: The UDM responds with the second subscription information to the authorization entity;

[0587] In some embodiments, the response message includes the SUPI and a third privacy profile of the first user.

[0588] Step 1107: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0589] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the first user obtained from the awareness initiating entity.

[0590] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the third privacy profile of the first user obtained from the UDM.

[0591] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the first user obtained from the awareness initiating entity and the third privacy profile of the first user obtained from the UDM.

[0592] Step 1108: The authorized entity sends a request for providing awareness information to the AMF.

[0593] In some embodiments, the awareness information provision request carries a SUPI, where the SUPI is an identifier of the first user ID and / or the user UE.

[0594] Step 1109: AMF selects SF.

[0595] Step 1110: Perception process;

[0596] In some embodiments, the 5GC and the perception node perform a perception process for the user UE.

[0597] In some embodiments, the 5GC includes at least one of the following network elements:

[0598] AMF;

[0599] PCF;

[0600] SF.

[0601] Step 1111: AMF sends a perception information provision response to the GMSC.

[0602] The sensing information provision response carries a sensing result obtained based on sensing measurements of one or more sensing nodes.

[0603] Step 1112: GMSC performs a privacy check;

[0604] In some embodiments, the GMSC sends the perception result to the perception initiating entity after obtaining the user consent of the first user.

[0605] Step 1113: The GMSC sends an awareness service response to the awareness initiating entity.

[0606] In some embodiments, the information of the first user / user UE in the perception result is anonymized.

[0607] In some embodiments, step 1101 , step 1112 , and step 1113 are optional.

[0608] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fifth implementation is as follows:

[0609] FIG22 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the sensing service for the sensing target. Unlike FIG21 , this embodiment deletes step 1107 and adds steps 1114 to 1119 between steps 1109 and 1110. The method includes at least one of the following steps:

[0610] Step 1114: The AMF sends a perception confirmation request to the authorized entity.

[0611] Step 1115: The authorization entity requests the second subscription information from the UDM;

[0612] In some embodiments, the request message includes a SUPI, which is an identifier of the user UE.

[0613] Step 1116: UDM retrieves the second subscription information;

[0614] In some embodiments, the UDM retrieves a third privacy profile of the first user based on the SUPI.

[0615] Step 1117: The UDM responds with the second subscription information to the authorization entity;

[0616] In some embodiments, the response message includes the SUPI and a third privacy profile of the first user.

[0617] Step 1118: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0618] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the first user obtained from the awareness initiating entity.

[0619] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on a third privacy profile of the user UE obtained from the UDM.

[0620] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the first user obtained from the awareness initiating entity and the third privacy profile of the user UE obtained from the UDM.

[0621] Step 1119: The authorized entity initiates a perception determination response to the AMF.

[0622] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the AMF, the embodiment of the above implementation mode 5 is as follows:

[0623] Figure 23 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the perception service for the perception target. Unlike Figure 21, this embodiment deletes step 1107 and adds steps 1120 to 1123 between steps 1109 and 1110. The method includes at least one of the following steps:

[0624] Step 1120: The authorization entity requests the second subscription information from the UDM;

[0625] In some embodiments, the request message includes a SUPI, which is an identifier of the user UE.

[0626] Step 1121: UDM retrieves the second subscription information;

[0627] In some embodiments, the UDM retrieves a third privacy profile of the user UE based on the SUPI.

[0628] Step 1122: The UDM responds with the second subscription information to the authorization entity;

[0629] In some embodiments, the response message includes the SUPI and a third privacy profile of the user UE.

[0630] Step 1123: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0631] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the first user obtained from the awareness initiating entity.

[0632] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on a third privacy profile of the user UE obtained from the UDM.

[0633] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the first user obtained from the awareness initiating entity and the third privacy profile of the user UE obtained from the UDM.

[0634] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the above implementation mode 6 is as follows:

[0635] FIG24 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the perception service for the perception target. Unlike FIG22 , this embodiment deletes step 1107 and adds steps 1124 to 1127 between steps 1108 and 1109. The method includes at least one of the following steps:

[0636] Step 1124: AMF and user UE network trigger service request;

[0637] In some embodiments, the AMF establishes a NAS connection with the user UE for network communication.

[0638] In some embodiments, the authorized entity, such as GMSC, base station, PCF, SF, etc., may also establish a connection with the user UE.

[0639] In some embodiments, the PCF establishes a NAS connection with the aware UE for network communication.

[0640] In some embodiments, the GMSC establishes a user plane connection with the aware UE to perform network communication.

[0641] In some embodiments, the base station establishes an access layer connection with the perceptual UE to perform network communication.

[0642] In some embodiments, the SF establishes a user plane or application layer-based connection with the aware UE to perform network communication.

[0643] In some embodiments, the connection established between the authorization entity and the user UE may also be a user plane connection, or an application layer-based connection. The specific connection method is related to the selection of the authorization entity, and the embodiments of the present application are not limited to this.

[0644] Step 1125: AMF sends an awareness notification call request to the user UE;

[0645] In some embodiments, the AMF sends an awareness notification invocation request to the user UE via a NAS connection.

[0646] Step 1126: The user UE obtains the user consent of the first user;

[0647] Step 1127: The user UE sends an awareness notification call response to the AMF.

[0648] In some embodiments, the user UE sends an awareness notification call response to the AMF through a NAS connection.

[0649] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the AMF, the embodiment of the above implementation mode 6 is as follows:

[0650] Figure 25 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the sensing node and the user UE. Unlike Figure 23, this embodiment deletes step 1107 and adds steps 1124 to 1127 between steps 1108 and 1109. The specific steps are the same as those in the embodiment shown in Figure 24.

[0651] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fourth implementation is as follows:

[0652] FIG26 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the perception service for the perception target. Unlike FIG21 , this embodiment expands steps 1105 and 1106, and the method includes at least one of the following steps:

[0653] Step 1105: UDM retrieves the second subscription information;

[0654] In some embodiments, the UDM retrieves a third privacy profile of the user UE based on the SUPI.

[0655] In some embodiments, the UDM retrieves the user consent of the first user based on the SUPI.

[0656] In some embodiments, the UDM retrieves the third privacy profile of the user UE and the user consent of the first user based on the SUPI.

[0657] Step 1106: The UDM responds with the second subscription information to the authorization entity.

[0658] In some embodiments, the response message includes the SUPI and a third privacy profile of the user UE.

[0659] In some embodiments, the response message includes the SUPI and the user consent of the first user.

[0660] In some embodiments, the response message includes the SUPI, the user consent of the first user, and a third privacy profile of the user UE.

[0661] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fourth implementation is as follows:

[0662] FIG27 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the perception service for the perception target. Unlike FIG22 , this embodiment expands steps 1105, 1106, 1116, and 1117, and the method includes at least one of the following steps:

[0663] Step 1105: UDM retrieves the second subscription information;

[0664] In some embodiments, the UDM retrieves a third privacy profile of the user UE based on the SUPI.

[0665] In some embodiments, the UDM retrieves the user consent of the first user based on the SUPI.

[0666] In some embodiments, the UDM retrieves the third privacy profile of the user UE and the user consent of the first user based on the SUPI.

[0667] Step 1106: The UDM responds with the second subscription information to the GMSC.

[0668] In some embodiments, the response message includes the SUPI and a third privacy profile of the user UE.

[0669] In some embodiments, the response message includes the SUPI and the user consent of the first user.

[0670] In some embodiments, the response message includes the SUPI, the user consent of the first user, and a third privacy profile of the user UE.

[0671] Step 1116: UDM retrieves the second subscription information;

[0672] In some embodiments, the UDM retrieves a third privacy profile of the user UE based on the SUPI.

[0673] In some embodiments, the UDM retrieves the user consent of the first user based on the SUPI.

[0674] In some embodiments, the UDM retrieves the third privacy profile of the user UE and the user consent of the first user based on the SUPI.

[0675] Step 1117: The UDM responds with the second subscription information to the GMSC.

[0676] In some embodiments, the response message includes the SUPI and a third privacy profile of the user UE.

[0677] In some embodiments, the response message includes the SUPI and the user consent of the first user.

[0678] In some embodiments, the response message includes the SUPI, the user consent of the first user, and a third privacy profile of the user UE.

[0679] For the perception initiating entity deployed in AF / NF / perception client / client UE, and the authorization entity deployed in AMF, the embodiment of the above implementation mode 4 is as follows:

[0680] Figure 28 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the perception service for the perception target. Unlike Figure 23, this embodiment expands steps 1105, 1106, 1121, and 1122, and the method includes at least one of the following steps:

[0681] Step 1105: UDM retrieves the second subscription information;

[0682] In some embodiments, the UDM retrieves a third privacy profile of the user UE based on the SUPI.

[0683] In some embodiments, the UDM retrieves the user consent of the first user based on the SUPI.

[0684] In some embodiments, the UDM retrieves the third privacy profile of the user UE and the user consent of the first user based on the SUPI.

[0685] Step 1106: UDM responds to the AMF with the second subscription information.

[0686] In some embodiments, the response message includes the SUPI and a third privacy profile of the user UE.

[0687] In some embodiments, the response message includes the SUPI and the user consent of the first user.

[0688] In some embodiments, the response message includes the SUPI, the user consent of the first user, and a third privacy profile of the user UE.

[0689] Step 1121: UDM retrieves the second subscription information;

[0690] In some embodiments, the UDM retrieves a third privacy profile of the user UE based on the SUPI.

[0691] In some embodiments, the UDM retrieves the user consent of the first user based on the SUPI.

[0692] In some embodiments, the UDM retrieves the third privacy profile of the user UE and the user consent of the first user based on the SUPI.

[0693] Step 1122: UDM responds to the AMF with the second subscription information.

[0694] In some embodiments, the response message includes the SUPI and a third privacy profile of the user UE.

[0695] In some embodiments, the response message includes the SUPI and the user consent of the first user.

[0696] In some embodiments, the response message includes the SUPI, the user consent of the first user, and a third privacy profile of the user UE.

[0697] If the perception initiating entity is deployed on the user UE, it is considered that the user's consent has been obtained and there is no need to authorize the perception initiating node.

[0698] 3. The sensing target is a region, and the sensing service is authorized for the sensing target;

[0699] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the fourth implementation is as follows:

[0700] FIG29 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. In this embodiment, the GMSC is used to authorize the sensing service for the sensing target. The method includes at least one of the following steps:

[0701] Step 1201: The sensing initiating entity sends a sensing service request to the GMSC;

[0702] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC.

[0703] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC via the NEF.

[0704] In some embodiments, the sensing service request includes at least target location information. Optionally, it also includes at least one of the following parameters:

[0705] A sense-initiating entity identifier, which is used to indicate the unique identifier of the sense-initiating entity. Each sense-initiating entity has its own corresponding sense-initiating entity identifier.

[0706] Service type: Service type is related to the sensing content, and different service types exist depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human respiratory rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense the human posture; the fifth service type is used to sense drones, and so on.

[0707] Step 1202: The GMSC requests the UDM to obtain the second subscription information;

[0708] In some embodiments, the request message includes target location information.

[0709] In some embodiments, the request message includes target location information and SUPI, where the SUPI is an identifier of the second user.

[0710] Step 1203: UDM retrieves the second subscription information;

[0711] In some embodiments, the UDM retrieves the awareness zone profile based on the target location information.

[0712] Step 1204: UDM responds with the second subscription information to the GMSC;

[0713] In some embodiments, the response message includes a perception zone profile.

[0714] Step 1205: The GMSC authorizes the sensing service for the sensing target based on the second subscription information.

[0715] In some embodiments, the GMSC authorizes the awareness service for the awareness target according to the awareness area profile.

[0716] In some embodiments, the GMSC determines whether the awareness initiating entity is authorized to perceive the awareness area according to the awareness area profile, and authorizes the awareness service for the awareness target.

[0717] Step 1206: The GMSC sends a request for providing awareness information to the AMF.

[0718] In some embodiments, the request message includes target location information.

[0719] Step 1207: AMF selects a perception network element SF;

[0720] Step 1208: Perception process;

[0721] In some embodiments, the 5GC and the sensing node perform a sensing process for the sensing area.

[0722] In some embodiments, the 5GC is at least one of the following:

[0723] AMF;

[0724] PCF;

[0725] SF.

[0726] Step 1209: AMF provides a response to the GMSC perception information.

[0727] Step 1210: GMSC performs a privacy check;

[0728] In some embodiments, the GMSC sends the sensing result to the sensing initiating entity upon obtaining user consent of the second user;

[0729] Step 1211: The GMSC exposes the perception information to the perception initiating entity.

[0730] In some embodiments, information of the perception area in the perception information is anonymized.

[0731] In some embodiments, step 1210 and step 1211 are optional.

[0732] For the perception initiating entity deployed in AF / NF / perception client / client UE, and the authorization entity deployed in AMF, the embodiment of the above implementation mode 4 is as follows:

[0733] Figure 30 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. In this embodiment, the AMF is used to authorize the perception service for the perception target. Based on the embodiment corresponding to Figure 29, step 1205 is deleted, and step 1212 is added between steps 1207 and 1208.

[0734] Step 1212: The AMF checks whether it has the right to sense the target area.

[0735] In some embodiments, the AMF determines whether the perception initiating entity has the right to perceive the target area based on its own configuration and target location information, and authorizes the perception service for the perception target.

[0736] For the embodiment of the above-mentioned fourth implementation mode in which the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC:

[0737] Figure 31 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. In this embodiment, the GMSC is used to authorize the sensing service for the sensing target. Based on the embodiment corresponding to Figure 29, step 1205 is deleted, and steps 1213 to 1218 are added between steps 1207 and 1208.

[0738] Step 1213: The AMF sends a perception confirmation request to the authorized entity.

[0739] Step 1214: The GMSC requests the UDM for the second subscription information.

[0740] In some embodiments, the target location information is included in the request message.

[0741] Step 1215: UDM retrieves the second subscription information;

[0742] In some embodiments, the UDM retrieves the awareness zone profile based on the target location information.

[0743] Step 1216: UDM responds with the second subscription information to the GMSC;

[0744] In some embodiments, the response message includes a perception zone profile.

[0745] Step 1217: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0746] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the awareness area profile obtained from the UDM.

[0747] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second user obtained from the UDM.

[0748] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the awareness area profile obtained from the UDM and the user consent of the second user.

[0749] Step 1218: The authorized entity initiates a perception determination response to the AMF.

[0750] For the perception initiating entity deployed in AF / NF / perception client / client UE, and the authorization entity deployed in AMF, the embodiment of the above implementation mode 4 is as follows:

[0751] Figure 32 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. In this embodiment, the AMF is used to authorize the perception service for the perception target. Based on the embodiment corresponding to Figure 29, step 1205 is deleted, and steps 1219 to 1222 are added between steps 1207 and 1208.

[0752] Step 1219: AMF requests the second subscription information from the UDM.

[0753] In some embodiments, the request message includes target location information.

[0754] Step 1220: UDM retrieves the second subscription information;

[0755] In some embodiments, the UDM retrieves the awareness zone profile based on the target location information.

[0756] Step 1221: UDM responds to the AMF with the second subscription information.

[0757] In some embodiments, the response message includes a perception zone profile.

[0758] Step 1222: The authorization entity authorizes the sensing service for the sensing target based on the second subscription information;

[0759] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the awareness area profile obtained from the UDM.

[0760] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the user consent of the second user obtained from the UDM.

[0761] In some embodiments, the authorization entity authorizes the awareness service for the awareness target based on the awareness area profile obtained from the UDM and the user consent of the second user.

[0762] If the perception initiating entity is deployed in the perception area, it is considered that the user's consent has been obtained and there is no need to authorize the perception initiating node.

[0763] 4. The sensing target is an object, and the sensing service authorization for the sensing target;

[0764] The sensing target is an object. When authorizing, the authorization entity will refer to the sensing area and authorize the sensing service for the sensing target based on the sensing object profile of the sensing object.

[0765] If the perception initiating entity is deployed on the sensing object, it is considered that the user's consent has been obtained and there is no need to authorize the perception initiating node.

[0766] 5. Authorization for sensing nodes;

[0767] For the case where the perception initiating entity is deployed in the AF / NF / perception client / client UE and the authorization entity is deployed in the GMSC, the embodiment of the above implementation mode 1 is as follows:

[0768] FIG33 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses a GMSC to sense the node. The method includes at least one of the following steps:

[0769] Step 1301: The perception initiating entity establishes a TLS connection with the perception UE;

[0770] A sensing initiating entity is configured to initiate a sensing service for a sensing UE. In some embodiments, when the sensing initiating entity initiates a sensing request, it sends a first sensing node list. The first sensing node list is a list of at least one candidate sensing node selected or recommended by the sensing initiating entity for this sensing request. The first sensing node list indicates at least one sensing node. Exemplarily, the first sensing node list includes an identifier of at least one sensing node.

[0771] The perception initiating entity directly or indirectly provides the first perception node list to the authorization entity. In some embodiments, the perception initiating entity provides the first perception node list to the authorization entity via one or more core network elements. For example, the perception initiating entity first provides the first perception node list to the UDM, which then provides the first perception node list to the authorization entity.

[0772] Step 1302: Sense service authorization between UE and PCF;

[0773] In some embodiments, the PCF generates and configures an authorization policy to the aware UE by sensing the UE's subscription information.

[0774] In some embodiments, the PCF generates and configures an authorization policy to the aware UE by sensing the second privacy profile of the UE and the user consent that may be provided by the aware initiating entity.

[0775] In some embodiments, the UE declares its role to the network side, for example, the UE declares that it is a perception target UE, and after the PCF checks the second privacy profile of the perception UE, it generates and configures an authorization policy to the perception UE.

[0776] In some embodiments, the UE declares its role to the network side, for example, the UE declares that it is a perception target UE, and after the PCF checks the second privacy profile of the perception UE and the user consent provided by the perception initiating entity, it generates and configures the authorization policy to the perception UE.

[0777] Step 1303: The sensing initiating entity sends a sensing service request to the authorizing entity;

[0778] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC.

[0779] In some embodiments, the AF / NF / awareness client / client UE sends an awareness service request to the GMSC via the NEF.

[0780] In some embodiments, the sensing service request includes at least: a first sensing node list. Optionally, it also includes at least one of the following parameters:

[0781] A sense-initiating entity identifier, which is used to indicate the unique identifier of the sense-initiating entity. Each sense-initiating entity has its own corresponding sense-initiating entity identifier.

[0782] Location information, used to indicate the area in which the sensing UE is allowed to be sensed, including specific or designated sensing location information;

[0783] Service type: Service type is related to the sensing content, and different service types exist depending on the sensing content. For example, the first service type is used to sense whether there are moving targets in the environment; the second service type is used to sense the human respiratory rate; the third service type is used to sense the human heart rate; the fourth service type is used to sense the human posture; the fifth service type is used to sense drones, and so on.

[0784] Step 1304: The authorization entity requests the first subscription information from the UDM (Nudm_SDM_GET Request);

[0785] In some embodiments, the request message includes a first sensory node list.

[0786] Step 1305: UDM retrieves the first subscription information;

[0787] In some embodiments, the UDM retrieves a first privacy profile of a sensing node in the first sensing node list based on the first sensing node list.

[0788] In some embodiments, the UDM retrieves, based on the first sensing node list, a user consent of a first subscribed user of a sensing node in the first sensing node list.

[0789] In some embodiments, the UDM retrieves, based on the first list of sensing nodes, a first privacy profile of a sensing node in the first list of sensing nodes and a user consent of a first subscribed user.

[0790] Step 1306: The UDM responds to the authorization entity with the first subscription information (Nudm_SDM_GET Response);

[0791] In some embodiments, the response message includes a first privacy profile of a sensing node in the first sensing node list.

[0792] Step 1307: The authorization entity authorizes the sensing node based on the first subscription information;

[0793] In some embodiments, the authorization entity authorizes the sensing node based on a first privacy profile of the sensing node in a first sensing node list obtained from the UDM.

[0794] Step 1308: The authorized entity sends a request for providing awareness information to the AMF.

[0795] In some embodiments, the perception information provision request carries a first perception node list.

[0796] Step 1309: AMF performs SF selection and sensing node selection;

[0797] In some embodiments, the AMF will select the sensing node based on the location information.

[0798] In some embodiments, the AMF selects at least one sensing node based on the first sensing node list to generate a second sensing node list.

[0799] Step 1310: Perception process;

[0800] In some embodiments, the 5GC and the perception node perform a perception process for the perception UE.

[0801] In some embodiments, the 5GC includes at least one of the following network elements:

[0802] AMF;

[0803] PCF;

[0804] SF.

[0805] Step 1311: AMF sends an awareness information provision response to the GMSC.

[0806] The sensing information provision response carries a sensing result obtained based on sensing measurements of one or more sensing nodes.

[0807] Step 1312: GMSC performs a privacy check;

[0808] In some embodiments, the GMSC sends the perception result to the perception initiating entity upon obtaining consent from the user corresponding to the perception UE.

[0809] Step 1313: The GMSC sends an awareness service response to the awareness initiating entity.

[0810] In some embodiments, the information of the sensing UE in the sensing result is anonymized.

[0811] In some embodiments, step 1312 and step 1313 are optional.

[0812] For the embodiment of the above implementation mode 2, the perception initiating entity is deployed in the AF / NF / perception client / client UE, the authorization entity is deployed in the GMSC, and the perception node selection entity is deployed in the AMF:

[0813] FIG34 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the GMSC to authorize the sensing node. Unlike FIG29 , this embodiment deletes step 1307 and adds steps 1314 to 1319 between steps 1309 and 1310. The method includes at least one of the following steps:

[0814] Step 1314: The AMF sends a perception confirmation request to the authorized entity.

[0815] Step 1315: The authorization entity requests the first subscription information from the UDM;

[0816] In some embodiments, the request message includes a second sensor node list.

[0817] Step 1316: UDM retrieves the first subscription information;

[0818] In some embodiments, the UDM retrieves a first privacy profile of a sensing node in the second sensing node list based on the second sensing node list.

[0819] In some embodiments, the UDM retrieves, based on the second list of sensing nodes, a user consent of a first subscribed user of a sensing node in the second list of sensing nodes.

[0820] In some embodiments, the UDM retrieves, based on the second list of sensing nodes, the first privacy profile of the sensing nodes in the second list of sensing nodes and the user consent of the first subscribed user.

[0821] Step 1317: The UDM responds with the first subscription information to the authorization entity;

[0822] In some embodiments, the response message includes a first privacy profile of a sensing node in the second sensing node list.

[0823] In some embodiments, the response message includes user consent of a first subscribed user of a sensing node in the second sensing node list.

[0824] In some embodiments, the response message includes the first privacy profile of the sensing node in the second sensing node list and the user consent of the first subscribed user.

[0825] Step 1318: The authorization entity authorizes the sensing node based on the first subscription information;

[0826] In some embodiments, the authorization entity authorizes the sensing node based on the first privacy profile of the sensing node in the second sensing node list obtained from the UDM.

[0827] Step 1319: The authorized entity initiates a perception determination response to the AMF.

[0828] The sensing determination response carries a sensing result obtained based on sensing measurements of one or more sensing nodes.

[0829] For the perception initiating entity deployed in AF / NF / perception client / client UE, the authorization entity and perception node selection entity are deployed in AMF, the embodiment of the above implementation mode three:

[0830] Figure 35 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the sensing node. Unlike Figure 29, this embodiment deletes step 1307 and adds steps 1320 to 1323 between steps 1309 and 1310. The method includes at least one of the following steps:

[0831] Step 1320: The authorization entity requests the first subscription information from the UDM;

[0832] In some embodiments, the request message includes a second sensor node list.

[0833] Step 1321: UDM retrieves the first subscription information;

[0834] In some embodiments, the UDM retrieves a first privacy profile of a sensing node in the second sensing node list based on the second sensing node list.

[0835] In some embodiments, the UDM retrieves, based on the second list of sensing nodes, a user consent of a first subscribed user of a sensing node in the second list of sensing nodes.

[0836] In some embodiments, the UDM retrieves, based on the second list of sensing nodes, the first privacy profile of the sensing nodes in the second list of sensing nodes and the user consent of the first subscribed user.

[0837] Step 1322: The UDM responds with the first subscription information to the authorization entity;

[0838] In some embodiments, the response message includes a first privacy profile of a sensing node in the second sensing node list.

[0839] In some embodiments, the response message includes user consent of a first subscribed user of a sensing node in the second sensing node list.

[0840] In some embodiments, the response message includes the first privacy profile of the sensing node in the second sensing node list and the user consent of the first subscribed user.

[0841] Step 1323: The authorization entity authorizes the sensing node based on the first subscription information;

[0842] In some embodiments, the authorization entity authorizes the sensing node based on the first privacy profile of the sensing node in the second sensing node list obtained from the UDM.

[0843] In some embodiments, the authorization entity authorizes the sensing node based on user consent of a first subscribed user of the sensing node in the second sensing node list obtained from the UDM.

[0844] In some embodiments, the authorization entity authorizes the sensing node based on the first privacy profile of the sensing node in the second sensing node list obtained from the UDM and the user consent of the first subscribing user.

[0845] For the case where the perception initiating entity is deployed in the perception UE, the authorization entity is deployed in the GMSC, and the perception node selection entity is deployed in the AMF, the embodiment of the above implementation mode 2 is as follows:

[0846] FIG36 shows a flowchart of an authorization method provided by an exemplary embodiment of the present application. In this embodiment, the GMSC is used to authorize the sensing node. The method includes at least one of the following steps:

[0847] Step 1401: Sense service authorization between UE and PCF;

[0848] In some embodiments, the PCF generates and configures an authorization policy to the aware UE by sensing the UE's subscription information.

[0849] In some embodiments, the PCF generates and configures an authorization policy to the aware UE by sensing the second privacy profile of the UE.

[0850] In some embodiments, the UE declares its role to the network side, for example, the UE declares that it is a perception target UE, and after the PCF checks the second privacy profile of the perception UE, it generates and configures an authorization policy to the perception UE.

[0851] Step 1402: The UE triggers a service request to the AMF.

[0852] Step 1403: The sensing UE initiates a sensing service request to the AMF;

[0853] In some embodiments, the sensing service request includes a first sensing node list. Optionally, it also includes at least one of the following parameters:

[0854] · Perceive the identity of the initiating entity;

[0855] Location information.

[0856] Step 1404: AMF selects a sensing network element SF and performs sensing node selection;

[0857] In some embodiments, the AMF selects a second sensing node list based on the first sensing node list and the location information of the sensing target.

[0858] In some embodiments, the AMF selects a second sensing node list based on the location information of the sensing target.

[0859] Step 1405: The AMF sends a sensor node authorization check request to the authorization entity.

[0860] In some embodiments, the request message includes a second sensory node list.

[0861] In some embodiments, the request message includes a sensor node ID of a sensor node in the second sensor node list.

[0862] Step 1406: The authorization entity requests the first subscription information from the UDM;

[0863] In some embodiments, the GMSC requests the UDM to obtain the first subscription information, and the request message includes a second perception node list.

[0864] Step 1407: UDM retrieves the first subscription information;

[0865] In some embodiments, the UDM retrieves a first privacy profile for a sensing node in the second list of sensing nodes.

[0866] In some embodiments, the UDM retrieves the user consent of the first subscribed user of the sensing node in the second list of sensing nodes.

[0867] In some embodiments, the UDM retrieves the first privacy profile of the sensing node in the second list of sensing nodes and the user consent of the first subscribing user.

[0868] Step 1408: The UDM responds with the first subscription information to the authorization entity;

[0869] In some embodiments, the UDM responds to the authorization entity with the first privacy profile of the sensing node in the second list of sensing nodes.

[0870] In some embodiments, the UDM responds to the authorization entity with user consent of the first subscribed user of the sensing node in the second sensing node list.

[0871] In some embodiments, the UDM responds to the authorization entity with the first privacy profile of the sensing nodes in the second list of sensing nodes and the user consent of the first subscribing user.

[0872] Step 1409: The authorization node authorizes the perception node based on the first subscription information;

[0873] In some embodiments, the authorizing node authorizes at least one sensing node based on a first privacy profile of the sensing node in the second sensing node list.

[0874] In some embodiments, the authorizing node authorizes at least one sensing node based on user consent of a first subscribing user of the sensing node in the second sensing node list.

[0875] In some embodiments, the authorization node authorizes at least one sensing node based on a first privacy profile of the sensing node in the second sensing node list and a user consent of the first subscribing user.

[0876] Step 1410: The authorization entity sends a sensing node authorization check response to the AMF.

[0877] In some embodiments, the authorization entity sends at least one authorized sensing node to the AMF.

[0878] In some embodiments, the response message includes the authorization result.

[0879] Step 1411: The 5GC and the sensing node perform a sensing process for the sensing UE;

[0880] In some embodiments, the 5GC includes at least one of the following:

[0881] AMF;

[0882] PCF;

[0883] SF.

[0884] Step 1412: The AMF provides the sensing result to the GMSC.

[0885] Step 1413: GMSC performs privacy check;

[0886] In some embodiments, the GMSC sends the perception result to the perception result requester upon obtaining consent from the user corresponding to the perception UE.

[0887] Step 1414: The GMSC perception result requester provides the perception result;

[0888] In some embodiments, the information of the aware UE in the awareness information is anonymized.

[0889] Step 1415: The AMF initiates a sensing response to the sensing UE.

[0890] The sensing response carries a sensing result obtained based on sensing measurements of one or more sensing nodes.

[0891] In some embodiments, step 1401 , step 1413 , and step 1414 are optional.

[0892] For the embodiment of the above implementation mode 3, where the perception initiating entity is deployed in the perception UE, and the authorization entity and the perception node selection entity are deployed in the AMF:

[0893] FIG37 is a flowchart of an authorization method provided by an exemplary embodiment of the present application. This embodiment uses the AMF to authorize the sensing node. Unlike FIG32 , this embodiment uses steps 1416 to 1419 instead of steps 1405 to 1410. The method includes at least one of the following steps:

[0894] Step 1416: The authorization entity requests the first subscription information from the UDM;

[0895] In some embodiments, the request message includes a second sensor node list.

[0896] Step 1417: UDM retrieves the first subscription information;

[0897] In some embodiments, the UDM retrieves a first privacy profile of a sensing node in the second sensing node list based on the second sensing node list.

[0898] In some embodiments, the UDM retrieves, based on the second list of sensing nodes, a user consent of a first subscribed user of a sensing node in the second list of sensing nodes.

[0899] In some embodiments, the UDM retrieves, based on the second list of sensing nodes, the first privacy profile of the sensing nodes in the second list of sensing nodes and the user consent of the first subscribed user.

[0900] Step 1418: The UDM responds with the first subscription information to the authorization entity;

[0901] In some embodiments, the response message includes a first privacy profile of a sensing node in the second sensing node list.

[0902] In some embodiments, the response message includes user consent of a first subscribed user of a sensing node in the second sensing node list.

[0903] In some embodiments, the response message includes the first privacy profile of the sensing node in the second sensing node list and the user consent of the first subscribed user.

[0904] Step 1419: The authorization entity authorizes the perception node based on the first subscription information.

[0905] In some embodiments, the authorization entity authorizes the sensing node based on the first privacy profile of the sensing node in the second sensing node list obtained from the UDM.

[0906] In some embodiments, the authorizing node authorizes the sensing node based on user consent of a first subscribing user of the sensing node in the second sensing node list.

[0907] In some embodiments, the authorizing node authorizes the sensing node based on the first privacy profile of the sensing node in the second sensing node list and the user consent of the first subscribing user.

[0908] The above methods 1 to 4 are authorizations for the sensing service for the sensing target, and 5 is authorization for the sensing node. Any of the methods 1 to 4 and any of the methods 5 can be implemented as independent embodiments, and this application does not limit this.

[0909] FIG38 shows a flowchart of a method for selecting a sensing node provided by an exemplary embodiment of the present application. The method includes at least one of the following steps:

[0910] Step 1510: Select at least one sensing node according to the first sensing node list and the location of the sensing target;

[0911] The first perception node list comes from the perception initiating entity or UDM.

[0912] In some embodiments, the first perception node list comes from the perception initiating entity and is the perception nodes that the perception initiating entity believes can assist in completing this perception.

[0913] In some embodiments, the first sensing node list comes from the UDM, and is the sensing nodes stored in the UDM that have been used previously for the same sensing initiating entity and sensing target.

[0914] Step 1520: Generate a second perception node list.

[0915] In some embodiments, the second list of sensing nodes is selected based on information about each sensing node and information about a sensing target. The information about each sensing node includes at least one of a location of each sensing node and first subscription information of each sensing node. The information about the sensing target includes at least one of a location of the sensing target and first subscription information of the sensing target.

[0916] In some embodiments, the information used to select the sensing node may also include at least one of: power information, communication link quality between the sensing node and the sensing target, reference signal measurement results between the sensing node and the sensing target, and the distance between the sensing node and the sensing target. This embodiment does not limit this.

[0917] In some embodiments, a second sensing node list is generated based on the first sensing node list and the location of the sensing target;

[0918] The second perception node list is a subset of the first perception node list.

[0919] In some embodiments, the sensing node selection entity generates a second sensing node list based on the first sensing node list and the location of the sensing target. For example, if the sensing target is located in area a and the first sensing node list is {b, c, d}, and the sensing nodes in area a are sensing nodes b and d, the sensing node selection entity generates a second sensing node list {b, d}.

[0920] In some embodiments, the sensing node selection entity generates a second sensing node list based on the first sensing node list and auxiliary information such as sensing target location, power level, and communication link quality.

[0921] In some embodiments, step 1520 is optional.

[0922] In some embodiments, step 1520 may be implemented as a standalone embodiment.

[0923] FIG39 shows a block diagram of an authorization device according to an exemplary embodiment of the present application. The method includes at least part of the following contents:

[0924] An acquisition module 1610 is configured to acquire first subscription information of a sensing node;

[0925] In some embodiments, the acquisition module 1610 is used to execute at least one of step 210, step 310, step 320, step 410, step 420, step 510, step 520, and step 530 in the above method embodiment.

[0926] In some embodiments, the acquisition module 1610 includes an acquisition sub-module.

[0927] The acquisition submodule is used to obtain the first subscription information of the perception node from the unified data management function UDM.

[0928] In some embodiments, the acquisition submodule is used to execute at least one of step 320, step 420, and step 530 in the above method embodiment.

[0929] In some embodiments, the acquisition submodule includes a sending submodule and a receiving submodule.

[0930] A sending unit, configured to send the identification of the sensing node to the UDM;

[0931] In some embodiments, the sending unit is used to perform at least one of step 320, step 420, and step 530 in the above method embodiment.

[0932] The receiving unit is configured to receive the first subscription information fed back by the UDM.

[0933] In some embodiments, the receiving unit is configured to execute at least one of step 320, step 420, and step 530 in the above method embodiment.

[0934] In some embodiments, a receiving module is also included.

[0935] The receiving module is configured to receive a first sensing node list from a sensing initiating entity, where the first sensing node list is used to indicate at least one sensing node.

[0936] In some embodiments, the receiving module is used to execute at least one of step 310 and step 510 in the above method embodiment.

[0937] In some embodiments, a receiving module is also included.

[0938] The receiving module is configured to receive a second sensory node list from a sensory node selection entity, where the second sensory node list is used to indicate at least one sensory node.

[0939] In some embodiments, the receiving module is configured to execute at least one of step 410 in the above method embodiment.

[0940] In some embodiments, the receiving module further includes a sending submodule.

[0941] The sending submodule is used to send the authorization result of at least one sensing node to the sensing node selection entity.

[0942] In some embodiments, the sending submodule is used to perform at least one step in step 440 in the above method embodiment.

[0943] In some embodiments, a selection module is also included.

[0944] The selection module is used to select at least one sensing node.

[0945] In some embodiments, the selection module is used to perform at least one step in step 520 in the above method embodiment.

[0946] In some embodiments, the selection module further includes a selection submodule.

[0947] A selection submodule, configured to select the at least one sensing node according to the first sensing node list and the location of the sensing target;

[0948] The first sensing node list comes from a sensing initiating entity or UDM.

[0949] In some embodiments, a submodule is selected to perform at least one step in step 520 in the above method embodiment.

[0950] In some embodiments, a sending module is also included.

[0951] The sending module is used to send the perception results to the perception result requester, and the information of the perception target in the perception results is anonymized.

[0952] The authorization module 1620 is used to authorize the perception node based on the first subscription information.

[0953] In some embodiments, the authorization module 1620 is used to execute at least one of step 220, step 330, step 430, and step 540 in the above method embodiment.

[0954] FIG40 shows a structural block diagram of a perception initiation device provided by an exemplary embodiment of the present application. The method includes at least part of the following contents:

[0955] The providing module 1710 is configured to provide a first sensory node list to the authorization entity, where the first sensory node list is used to indicate at least one sensory node.

[0956] The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

[0957] In some embodiments, a module 1710 is provided for performing at least one of the steps 510 in the above method embodiment.

[0958] In some embodiments, the providing module 1710 includes a providing sub-module.

[0959] A submodule is provided for providing the first perception node list to the authorization entity through the UDM.

[0960] In some embodiments, a submodule is provided for performing at least one of step 510 in the above method embodiment.

[0961] FIG41 shows a block diagram of a sensing node selection apparatus provided by an exemplary embodiment of the present application. The method includes at least part of the following contents:

[0962] A providing module 1810 is configured to provide a second sensory node list to an authorization entity, where the second sensory node list is configured to indicate at least one sensory node;

[0963] The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

[0964] In some embodiments, a module 1810 is provided for performing at least one of the steps 410 in the above method embodiment.

[0965] In some embodiments, a generation module is also included.

[0966] A generation module is used to generate a second perception node list.

[0967] In some embodiments, the generation module is used to perform at least one step in step 520 in the above method embodiment.

[0968] In some embodiments, the generation module further includes a generation submodule.

[0969] A generating submodule, configured to generate a second sensing node list based on the first sensing node list and the position of the sensing target;

[0970] The first perception node list comes from the perception initiating entity or the UDM, and the second perception node list is a subset of the first perception node list.

[0971] In some embodiments, a submodule is generated to perform at least one step in step 520 in the above method embodiment.

[0972] In some embodiments, a receiving module is also included.

[0973] The receiving module is configured to receive an authorization result from at least one sensing node of the authorization entity.

[0974] In some embodiments, the receiving module is configured to execute at least one of step 440 in the above method embodiment.

[0975] FIG42 shows a block diagram of an authorization device according to an exemplary embodiment of the present application. The method includes at least part of the following contents:

[0976] An acquisition module 1910 is configured to acquire second subscription information of a sensing target;

[0977] In some embodiments, the acquisition module 1910 is used to execute at least one of step 610, step 710, step 810, step 820, step 910, and step 920 in the above method embodiment.

[0978] In some embodiments, the acquisition module 1910 includes an acquisition sub-module.

[0979] The acquisition submodule is used to obtain the second subscription information of the perception target from the UDM.

[0980] In some embodiments, the acquisition submodule is used to execute at least one of step 710, step 820, and step 920 in the above method embodiment.

[0981] In some embodiments, the acquisition submodule includes a sending unit and a receiving unit.

[0982] A sending unit, used for sending the identification of the sensing target to the UDM;

[0983] In some embodiments, the sending unit is used to perform at least one of step 710, step 820, and step 920 in the above method embodiment.

[0984] The receiving unit is configured to receive the second subscription information fed back by the UDM.

[0985] In some embodiments, the receiving unit is configured to execute at least one of step 710 in the above method embodiment.

[0986] In some embodiments, an acquisition module and a sending module are also included.

[0987] The acquisition module is used to send the perception result to the perception result requester when the user consent corresponding to the perception target is obtained.

[0988] The sending module is used to send the perception results to the perception result requester, and the information of the perception target in the perception results is anonymized.

[0989] The authorization module 1920 is configured to authorize the perception service for the perception target based on the second subscription information.

[0990] In some embodiments, the authorization module 1920 is configured to execute at least one of step 620, step 720, step 830, and step 930 in the above method embodiment;

[0991] FIG43 shows a structural block diagram of a perception initiation device provided by an exemplary embodiment of the present application. The method includes at least part of the following contents:

[0992] The providing module 2010 is configured to provide an identification of a perception target to an authorization entity, and the authorization entity is configured to authorize the perception service for the perception target based on the second subscription information of the perception target.

[0993] In some embodiments, a module 2010 is provided for performing at least one of step 710, step 820, and step 920 in the above method embodiment;

[0994] FIG44 shows a block diagram of a perception-based authorization checking device according to an exemplary embodiment of the present application. The method includes at least part of the following contents:

[0995] The generating module 2110 is configured to generate an authorization policy for the perceiving UE based on the subscription information of the perceiving UE.

[0996] FIG45 shows a block diagram of a device for selecting a sensing node according to an exemplary embodiment of the present application. The method includes at least part of the following contents:

[0997] The selection module 2210 selects at least one sensing node according to the first sensing node list and the location of the sensing target;

[0998] In some embodiments, the selection module 2210 is configured to execute at least one of step 410, step 520, and step 1510 in the above method embodiment;

[0999] The generation module 2220 generates a second perception node list.

[1000] In some embodiments, the generating module 2220 is configured to execute at least one of step 410, step 520, and step 1520 in the above method embodiment;

[1001] The sequence of steps in the above method embodiments does not constitute a timing limitation between the above modules.

[1002] It should be noted that the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions. In actual applications, the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[1003] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[1004] FIG46 shows a schematic diagram of the structure of a sensing device provided by an embodiment of the present application. The sensing device may include: a processor 2301 , a receiver 2302 , a transmitter 2303 , a memory 2304 , and a bus 2305 .

[1005] The processor 2301 includes one or more processing cores. The processor 2301 executes various functional applications and information processing by running software programs and modules.

[1006] The receiver 2302 and the transmitter 2303 may be implemented as a transceiver, which may be a communication chip.

[1007] The memory 2304 is connected to the processor 2301 via a bus 2305; in some embodiments, the processor 2301 can be implemented as a first IC chip, and the processor 2301 and the memory 2304 can be jointly implemented as a second IC chip; the first chip or the second chip can be an application specific integrated circuit (ASIC) chip.

[1008] The memory 2304 can be used to store at least one computer program, and the processor 2301 is used to execute the at least one computer program to implement the various steps performed by the perception system in the above method embodiment.

[1009] In addition, the memory 2304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: random-access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid-state storage technology, compact disc read-only memory (CD-ROM), high-density digital video disc (DVD) or other optical storage, tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

[1010] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and the computer program is used to be executed by a processor of a multi-link device to implement the above-mentioned authorization method of the perception node, or the authorization method of the perception service, or the authorization check method based on perception.

[1011] Optionally, the computer-readable storage medium may include: Read-Only Memory (ROM), Random-Access Memory (RAM), Solid State Drives (SSD), or an optical disk, etc. Among them, the random access memory may include Resistance Random Access Memory (ReRAM) and Dynamic Random Access Memory (DRAM).

[1012] An embodiment of the present application also provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip runs on a multi-link device, it is used to implement the above-mentioned authorization method of the perception node, or the authorization method of the perception service, or the authorization check method based on perception.

[1013] An embodiment of the present application also provides a computer program product or computer program, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the multi-link device reads and executes the computer instructions from the computer-readable storage medium to implement the above-mentioned authorization method of the perception node, or the authorization method of the perception service, or the authorization check method based on perception.

[1014] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[1015] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[1016] In this document, "plurality" refers to two or more. "And / or" describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates an "or" relationship between the associated objects.

[1017] In addition, the step numbers described in this document only illustrate a possible execution order between the steps. In some other embodiments, the above steps may not be executed in the order of the numbers, such as two steps with different numbers are executed at the same time, or two steps with different numbers are executed in the opposite order of the diagram. The embodiments of the present application are not limited to this.

[1018] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[1019] The above description is merely an exemplary embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for authorizing a sensing node, characterized in that: The method is performed by an authorized entity, and comprises: Acquire first subscription information of the sensing node; The perception node is authorized based on the first subscription information.

2. The method according to claim 1, characterized in that The obtaining the first subscription information of the sensing node includes: The first subscription information of the perception node is obtained from a unified data management function UDM.

3. The method according to claim 2, characterized in that The acquiring the first subscription information of the sensing node from the UDM includes: Sending the identification of the sensing node to the UDM; Receive the first subscription information fed back by the UDM.

4. The method according to claim 1, characterized in that: The method further comprises: A first sensor node list is received from a sensor initiating entity, where the first sensor node list is used to indicate at least one sensor node.

5. The method according to claim 4, characterized in that The perception initiating entity is deployed in at least one of an application function AF, a network function NF, a perception client, and a client UE.

6. The method according to claim 1, characterized in that The method further comprises: A second sensory node list is received from a sensory node selection entity, where the second sensory node list is used to indicate at least one sensory node.

7. The method according to claim 6, characterized in that The method further comprises: Sending the authorization result of the at least one sensing node to the sensing node selection entity.

8. The method according to claim 7, characterized in that The perception node selection entity is deployed in at least one of the service function SF, the access and mobility management function AMF, the policy control function PCF, and the application function AF.

9. The method according to claim 1, characterized in that: The authorization entity is also a perception node selection entity, and the method further includes: Select at least one sensor node.

10. The method according to claim 9, characterized in that The selecting at least one sensing node comprises: Selecting the at least one sensing node according to the first sensing node list and the position of the sensing target; The first perception node list comes from a perception initiating entity or a unified data management function UDM.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: The perception result is sent to the perception result requester, and the information of the perception target in the perception result is anonymized.

12. The method according to any one of claims 1 to 10, characterized in that: The authorization entity is deployed in any one of AMF, base station, PCF, SF, and mobile gateway perception center GMSC.

13. The method according to any one of claims 1 to 10, characterized in that: The first subscription information of the sensing node includes at least one of the following: A user consent of a first subscribed user, wherein the first subscribed user is associated with the sensing node; First Privacy Profile.

14. The method according to claim 13, characterized in that The first privacy profile includes at least one of the following: Type of service; Supports perceived business types; Perceive the identity of the initiating entity; Type of role; Authorization-aware location information.

15. A method for authorizing a sensing node, characterized in that: The method is performed by a perception initiating entity, and the method further comprises: Providing a first sensory node list to an authorization entity, wherein the first sensory node list is used to indicate at least one sensory node; The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

16. The method according to claim 15, characterized in that The providing the first perception node list to the authorization entity comprises: The first perception node list is provided to the authorization entity through a unified data management function UDM.

17. The method according to claim 15, characterized in that The authorization entity is deployed in any one of the access and mobility management function AMF, the base station, the policy control function PCF, the service function SF, and the mobile gateway perception center GMSC.

18. The method according to claim 15, characterized in that The perception initiating entity is deployed in at least one of AF, network function NF, perception client, and client UE.

19. The method according to any one of claims 15 to 18, characterized in that: The first subscription information includes at least one of the following: A user consent of a first subscribed user, wherein the first subscribed user is associated with the sensing node; First Privacy Profile.

20. The method according to claim 19, characterized in that The first privacy profile includes at least one of the following: Type of service; Supports perceived business types; Perceive the identity of the initiating entity; Type of role; Authorization-aware location information.

21. A method for authorizing a sensing node, characterized in that: The method is performed by a sensing node selection entity, and the method further comprises: providing a second sensory node list to the authorization entity, wherein the second sensory node list is used to indicate at least one sensory node; The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

22. The method according to claim 21, characterized in that The method further comprises: Generate the second perception node list.

23. The method according to claim 22, characterized in that The generating the second perception node list comprises: Generate the second sensing node list according to the first sensing node list and the position of the sensing target; The first perception node list comes from a perception initiating entity or a unified data management function UDM, and the second perception node list is a subset of the first perception node list.

24. The method according to claim 21, characterized in that The method further comprises: An authorization result of the at least one sensing node from the authorization entity is received.

25. The method according to any one of claims 21 to 24, characterized in that: The first subscription information includes at least one of the following: A user consent of a first subscribed user, wherein the first subscribed user is associated with the sensing node; First Privacy Profile.

26. The method according to claim 25, characterized in that The first privacy profile includes at least one of the following: Type of service; Supports perceived business types; Perceive the identity of the initiating entity; Type of role; Authorization-aware location information.

27. A method for authorizing a perception service, characterized in that: The method is performed by an authorized entity, and comprises: Get the second subscription information of the sensing target; Based on the second subscription information, the perception service for the perception target is authorized.

28. The method according to claim 27, characterized in that The acquiring the second subscription information of the sensing target includes: The second subscription information of the perception target is obtained from a unified data management function UDM.

29. The method according to claim 28, characterized in that The acquiring the second subscription information of the sensing target from the UDM includes: Sending an identification of the sensing target to the UDM; Receive the second subscription information fed back by the UDM.

30. The method according to any one of claims 27 to 29, characterized in that: The method further comprises: When obtaining consent from a user corresponding to the perception target, sending the perception result to a perception result requester; and / or, The perception result is sent to the perception result requester, and the information of the perception target in the perception result is anonymized.

31. The method according to any one of claims 27 to 29, characterized in that: The authorization entity is deployed in any one of the access and mobility management function AMF, the base station, the policy control function PCF, the service function SF, and the mobile gateway perception center GMSC.

32. The method according to any one of claims 27 to 29, characterized in that: The sensing target includes at least one of the following: Perceive UE; First user; Perception area.

33. The method according to claim 32, characterized in that The sensing target is the sensing UE; The second subscription information includes at least one of the following: a user consent of a second subscribed user, wherein the second subscribed user is associated with the aware UE; Second privacy profile.

34. The method according to claim 33, characterized in that The second privacy profile includes at least one of the following: Type of service; The type of business being perceived; Perceive the identity of the initiating entity; Perceived privacy identification; Privacy type; Type of role; Sense location information.

35. The method according to claim 32, characterized in that The perceived target is the first user; The second subscription information includes at least one of the following: an identifier of the first user; User consent of the first user; Third Privacy Profile.

36. The method according to claim 33, characterized in that The third privacy profile includes at least one of the following: Type of service; The type of business being perceived; Perceive the identity of the initiating entity; Perceived privacy identification; Privacy type; Type of role; Sense location information.

37. The method according to claim 32, characterized in that The sensing target is the sensing area; The second subscription information includes at least one of the following: an identifier of the second user; a user of the second user agrees that the second user is associated with the perception area; Awareness zone profile.

38. The method according to claim 37, characterized in that The perception area configuration file includes at least one of the following: Type of service; The type of business being perceived; Perceive the identity of the initiating entity; Perceived privacy identification; Privacy type.

39. The method according to any one of claims 33 to 38, characterized in that The user consent is obtained through the application layer; or, The user consent is obtained by the connection between the authorization entity and the sensing target.

40. A method for authorizing a perception service, characterized in that: The method is performed by the perception initiating entity, and the method includes: The identification of the perception target is provided to the authorization entity, and the authorization entity is used to authorize the perception service for the perception target based on the second subscription information of the perception target.

41. The method according to claim 40, characterized in that The second subscription information includes: user consent corresponding to the perception target; the method further includes: Obtaining the user's consent; The user consent is provided to the authorization entity.

42. The method according to claim 41, characterized in that Providing the user consent to the authorized entity includes: The user consent is provided to the authorization entity through a unified data management function UDM.

43. The method according to any one of claims 40 to 41, characterized in that The sensing target includes at least one of the following: Perceive UE; First user; Perception area.

44. A perception-based authorization checking method, characterized in that: The method comprises: Based on the second subscription information of the perception terminal device UE, an authorization policy for the perception UE is generated.

45. The method according to claim 44, characterized in that The second subscription information includes at least one of the following: a user consent of a second subscribed user, wherein the second subscribed user is associated with the aware UE; Second privacy profile.

46. ​​The method according to claim 45, characterized in that The second privacy profile includes at least one of the following: Type of service; The type of business being perceived; Perceive the identity of the initiating entity; Perceived privacy identification; Privacy type; Type of role; Sense location information.

47. The method according to any one of claims 44 to 46, characterized in that The authorization policy is used to indicate at least one of the following: A first public land mobile network PLMN allowing the sensing UE to use sensing services; Allowing other UEs to use the second PLMN of the aware service for the aware UE.

48. An authorization device, characterized in that: The device comprises: An acquisition module, used for acquiring first subscription information of a sensing node; An authorization module is used to authorize the perception node based on the first subscription information.

49. A perception initiation device, characterized in that: The device comprises: A providing module is used to provide a first sensory node list to an authorization entity, wherein the first sensory node list is used to indicate at least one sensory node; The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

50. A sensing node selection device, characterized in that: The device comprises: Providing a module, configured to provide a second sensory node list to the authorization entity, the second sensory node list being configured to indicate at least one sensory node; The authorization entity is used to authorize the perception node based on the first subscription information of the perception node.

51. An authorization device, characterized in that: The device comprises: An acquisition module, used for acquiring second subscription information of a sensing target; The authorization module is used to authorize the perception service for the perception target based on the second subscription information.

52. A perception initiation device, characterized in that: The device comprises: A module is provided, which is used to provide an identification of a perception target to an authorization entity, and the authorization entity is used to authorize a perception service for the perception target based on second subscription information of the perception target.

53. A perception-based authorization checking device, characterized in that: The device comprises: The generation module is used to generate an authorization policy for the perception terminal device UE based on the second subscription information of the perception terminal device UE.

54. A sensing device, characterized in that The perception device includes a processor and a memory, and the memory contains at least one program; the perception device is used to execute the at least one program in the memory to implement the authorization method of the perception node described in any one of claims 1 to 26, or the authorization method of the perception service described in any one of claims 27 to 43, or the perception-based authorization check method described in any one of claims 44 to 47.

55. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which is used to be executed by a processor to implement the authorization method of the perception node described in any one of claims 1 to 26, or the authorization method of the perception service described in any one of claims 27 to 43, or the perception-based authorization check method described in any one of claims 44 to 47.

56. A chip, characterized in that: The chip includes programmable logic circuits and / or program instructions, which, when running, are used to implement the authorization method for the perception node described in any one of claims 1 to 26, or the authorization method for the perception service described in any one of claims 27 to 43, or the perception-based authorization check method described in any one of claims 44 to 47.

57. A computer program product or a computer program, characterized in that The computer program product or computer program includes computer instructions, which are stored in a computer-readable storage medium. The processor reads and executes the computer instructions from the computer-readable storage medium to implement the authorization method for the perception node described in any one of claims 1 to 26, or the authorization method for the perception service described in any one of claims 27 to 43, or the perception-based authorization check method described in any one of claims 44 to 47.

Images