Providing sensing services in cellular communication networks

Abstract

This disclosure provides an example embodiment of a solution for providing sensing services in a cellular communication network. One method includes receiving a request for consent to object sensing from a sensing management function, obtaining identification information identifying the owner of the object or identification information identifying a sensing area used for sensing the object, and, based on the identification information, sending a request for consent to object sensing to a user device associated with the object's owner or an entity associated with the object's owner. The consent request includes information related to object sensing. Based on a response to the consent request received from the user device or entity, the response instructs consent to object sensing, and a response to the request for consent to object sensing is provided to the sensing management function.

Description

Technical Field

[0001] This disclosure relates to sensing services in cellular communication networks and sensing objects using sensing services. Background Technology

[0002] Mobile telecommunications networks or cellular networks (generally referred to as communication networks in this document) enable communication between two or more communication devices, provide communication devices with access to data networks, deliver services provided by third-party applications to communication devices, or provide services provided by communication networks to communication devices.

[0003] Communication networks and devices can operate according to cellular technologies (also known as radio access technologies), such as GSM, UTMS, LTE, LTE-A, and NR. Cellular technologies are standardized by various standards organizations, such as the 3rd Generation Partnership Project (3GPP) or ETSI (European Telecommunications Standards Institute). 3GPP is currently developing standards for fifth-generation cellular technologies (commonly referred to as 5G or NR standards) and sixth-generation cellular technologies (commonly referred to as 6G standards). Communication networks operating according to 5G or NR standards are generally called 5G networks, while communication networks operating according to 6G standards are generally called 6G networks.

[0004] Communication networks (such as 5G or 6G networks) include access networks (such as radio access networks) that can wirelessly communicate with one or more communication devices by sharing the available resources (such as bandwidth, transmission power, etc.) of the access network. Communication networks can also establish reliable and secure connectivity between communication devices and the core network of the communication network via the access network. Communication networks (such as 5G networks) can provide communication devices with enhanced mobile broadband services (such as telephone, video, data, and short message services), ultra-reliable low-latency communication services (such as XR services), or massive machine-type communication services.

[0005] Communication networks may be able to sense objects (e.g., base stations of the communication network and / or user equipment communicating with mobile or cellular networks) and can be configured to detect and track objects (e.g., targets) that are connected to or not connected to the mobile or cellular network. Communication networks that provide sensing services to sense (e.g., detect and track) objects (e.g., targets) raise questions about authorizing sensing services to sense specific objects (e.g., targets) and how sensing services provided by mobile or cellular networks can obtain authorization (e.g., consent) to begin sensing specific objects if the specific object (e.g., target) is not connected to the communication network. Moreover, 3GPP SA1 Release 19 TR / TS[1] introduces requirements related to sensing security and privacy, which require that " When the perceived results and user identifiers are combined for further processing, the 5G system should obtain the user's identity. meaning ".

[0006] Privacy developments related to the perception and / or tracking of objects in communication networks are desirable. Summary of the Invention

[0007] According to one aspect of this disclosure, a method includes receiving a request for consent to object perception from a perception management function, obtaining identification information identifying the owner of the object or identification information identifying a perception area used for perceiving the object, sending a request for consent to perceive the object to a user device associated with the owner of the object or an entity associated with the owner of the object based on the identification information, the consent request including information related to the perception of the object, and based on receiving a response to the consent request from the user device or entity, indicating consent to perceive the object in the response to the consent request, providing the perception management function with the response to the request for consent to object perception, the response to the request for consent to perception indicating consent to object perception.

[0008] Before sending a consent-aware request, a request to discover user equipment in the awareness area can be sent to the network entity, and in response to the request to discover user equipment, a list identifying user equipment in the awareness area is received. Objects are included in the list of identified user equipment, and the consent request is sent based on the received list of user equipment including the objects.

[0009] The request can be sent to a third-party application function.

[0010] This method may include receiving a response from a third-party application function to a request for consent to be object-aware before providing a response to the perception management function to a request for consent to be object-aware.

[0011] Sending based on identification information may include broadcasting a request for consent to be perceived on a broadcast channel. The broadcast may include broadcasting information related to the perception of the object, which may include at least one of consent type, perception area, and perception service.

[0012] The method may include responding to a request for consent from an object and waiting for a predetermined period of time. The response to the consent request may be received from the user device within the predetermined period of time.

[0013] If no response to the consent request is received from the user device within a predetermined time period, a response to the request for consent to object awareness can be provided to the perception management function, indicating that the object owner has not consented to object awareness.

[0014] In response to receiving a rejection of a request for consent to object awareness from a user device, a response to a request for consent to object awareness can be provided to the perception management function, indicating that consent to object awareness has not been provided.

[0015] In response to a rejection of a request for consent to be perceived, the object can be excluded from being perceived.

[0016] If no response to the consent request is received from the user device within a predetermined time period, the method may include providing a response to the perception management function to the request for object perception of consent, indicating the consent-perceiving object.

[0017] A response to a request for consent may include one or more conditions or constraints relating to the consent.

[0018] One or more conditions or constraints may include one or more of the following: an indication of the permitted duration of perception, the permitted area of ​​perception or a sub-area within the area of ​​perception, the permitted precision of perception, the permitted resolution of perception, the characteristics or attributes of the object to be perceived, and modifications to specific characteristics of the object.

[0019] According to another aspect of this disclosure, a consent management entity for a communication network includes at least one processor and at least one memory, the at least one memory storing instructions, wherein the instructions are executable by the at least one processor to cause the consent management entity to perform the above-described methods.

[0020] According to another aspect of this disclosure, an apparatus includes: a consent management function configured to perform the consent management function described above.

[0021] According to another aspect of this disclosure, a consent management entity includes components for performing the above methods.

[0022] According to another aspect of this disclosure, a non-transient computer-readable medium includes instructions stored thereon for execution by at least one processor of a consent management entity to cause the consent management entity to perform the above-described methods.

[0023] According to another aspect of this disclosure, a computer program includes instructions that, when executed by at least one processor of a consent management entity, cause the consent management entity to perform the above-described method.

[0024] According to one aspect of this disclosure, a method performed by a perception management function of a communication network includes receiving a perception service request, the perception service request including information related to a perception object; sending a request for consent to perform object perception to a perception consent management entity; determining whether to initiate object perception based on a response to a consent request received from the perception consent management entity; and sending a response to the perception service request indicating that object perception is not permitted based on the determination that object perception should not be initiated.

[0025] This method may include sending a message to one or more sensing devices to initiate sensing based on determining the object to be sensed.

[0026] According to another aspect of this disclosure, a perception management entity for a communication network includes at least one processor and at least one memory, the at least one memory storing instructions, wherein the instructions are executable by the at least one processor to cause the perception management entity to perform the methods described above.

[0027] According to another aspect of this disclosure, a perception management entity is configured to perform the above method.

[0028] According to another aspect of this disclosure, an apparatus includes a sensing management function configured to perform the above-described method.

[0029] According to another aspect of this disclosure, a non-transient computer-readable medium includes instructions stored thereon for execution by at least one processor of a perception management entity to cause the perception management entity to perform the methods described above.

[0030] According to another aspect of this disclosure, a computer program includes instructions, wherein when executed by at least one processor of a perception management entity, the computer program causes the perception management entity to perform the above-described method.

[0031] According to another aspect of this disclosure, a method includes receiving a broadcast or unicast request for consent to perceive an object, the broadcast or unicast request including information related to the object perception; determining, based on the perception-related information, whether the owner of the object consents to perceive the object; providing a response to the broadcast or unicast request for consent in response to determining that the owner of the object consents to perceive the object, the response indicating that the owner of the object consents to perceive the object; and providing a response to the broadcast or unicast request for consent in response to determining that the owner of the object does not consent to perceive the object, the response indicating that the owner of the object does not consent to perceive the object.

[0032] Information related to object awareness may include one or more of the following: the sensing area, the type of sensing service, the type of the sensing object, the duration of the sensing service, sensing QoS information, and information about the characteristics of the sensing object.

[0033] Information related to object awareness may include the consent type, which indicates the type of consent to object awareness.

[0034] The owner of the object may consent to the perceived object’s response, which may include one or more conditions or constraints on the perception.

[0035] One or more conditions or constraints may include one or more of the following: an indication of the permitted duration of perception, the permitted area of ​​perception or a sub-area within the area of ​​perception, the permitted precision of perception, the permitted resolution of perception, the characteristics or attributes of the object to be perceived, and modifications to specific characteristics of the object.

[0036] The method may also include determining the type of consent requested after receiving a broadcast or unicast request and before providing a response.

[0037] According to another aspect of this disclosure, a user equipment includes at least one processor and at least one memory storing instructions that can be executed by the at least one processor to cause the user equipment to perform the above methods.

[0038] According to another aspect of this disclosure, a non-transient computer-readable medium includes instructions stored thereon for execution by at least one processor of a user device to cause the user device to perform the above-described method.

[0039] According to another aspect of this disclosure, a computer program includes instructions, wherein when executed by at least one processor of a user device, the computer program causes the user device to perform the above-described methods. Attached Figure Description

[0040] Embodiments of this disclosure are now described by way of example only with reference to the accompanying drawings.

[0041] Figure 1 This is a schematic diagram illustrating a communication network according to one aspect of an embodiment.

[0042] Figure 2 This is a schematic diagram illustrating one or more example implementations of a component.

[0043] Figure 3 This is a schematic diagram showing the components of an example user device.

[0044] Figures 4 to 6 This is a flowchart illustrating the method based on the example.

[0045] Figures 7 to 11 It is a diagram showing the operations in the process according to the implementation method. Detailed Implementation

[0046] For simplicity and clarity of illustration, reference numerals may be repeated in the accompanying drawings to indicate corresponding or similar elements. Numerous details are set forth to provide an understanding of the examples described herein. These examples can be practiced without these details. In other instances, well-known methods, processes, and components are not described in detail to avoid confusion with the described examples. This description should not be construed as limiting the scope of the examples described herein.

[0047] This disclosure relates to sensing services provided by a communication network, such as sensing services that provide sensing of a scenario surrounding a communication network entity (e.g., a base station and / or user equipment) configured as a sensing device. The sensing device includes, for example, a device capable of performing one or more of the following: Object detection, location, and / or tracking; Images that form a specific scene or environment; or Identify the characteristics of the discovered objects for identification and / or classification.

[0048] Privacy and determining who should authorize (e.g., consent) the sensing of a specific object by (multiple) sensing devices on a communication network have not been adequately addressed. Authorization is desired for sensing objects connected to the communication network. Additionally, authorization is desired for sensing objects not connected to the communication network. With the increasing density of communication networks and the growing number of user devices communicating with them, identifying the "owner" of an object becomes difficult.

[0049] For connected objects, such as those connected to a communication network, the owner's consent to be aware of the connected object can be obtained by sending a notification to the user equipment (UE) that owns the connected object. The UE user can provide consent for any connected devices that are tracking that user. Another user equipment can also be tracked, but in this case, the device owner receives a request for consent awareness, and the device owner can either consent to or refuse the request.

[0050] For unconnected devices, consent to the sensed object and / or sensed area can be obtained using this disclosure.

[0051] Communication systems that integrate sensing and communication are often referred to as integrated sensing and communication systems. The integrated sensing and communication (ISAC) system described in this paper uses at least some of the same hardware and spectrum resources to potentially achieve relatively high data rate communication and relatively high resolution object detection. For example, this can improve the sensing accuracy of scenes or situations where existing sensing technologies perform poorly (e.g., non-line-of-sight (NLOS) conditions, requirements for high-speed resolution), improve spectral efficiency by sharing communication and sensing spectrum, and / or reduce hardware costs by combining sensing and communication devices / hardware.

[0052] Example scenarios where an Integrated Sensing and Communication (ISAC) system can be used include (but are not limited to) the following: Intrusion detection (e.g., intruder detection in smart homes, pedestrian or animal intrusion detection on highways); Support for autonomous driving (e.g., by providing additional information about objects detected on the road, such as pedestrians, bicycles, or other vehicles, to assist in vehicle handling and navigation, and to determine parking spaces). Support for unmanned aerial vehicle (UAV) flight (e.g., UAV flight trajectory tracking, network-assisted perception to avoid UAV collisions by providing information on objects detected in the air, especially those without communication components to indicate their presence); Support for Automated Guided Vehicles (AGVs) or Autonomous Mobile Robots (AMRs) in factories (e.g., AGV detection and tracking in factories, AMR collision avoidance in smart factories); Environmental and / or weather monitoring (e.g., rainfall, pollution, flooding); Health monitoring (e.g., fall detection, contactless sleep monitoring services); or Extended Reality (XR) applications.

[0053] refer to Figure 1 It illustrates a schematic representation of a communication network 100 accessed by a user equipment (UE) 102 to communicate with an application server 110 hosting third-party application functions 111 via a data network 104. The communication network 100 includes an ISAC system comprising a radio access network (RAN) entity 106 (e.g., a RAN entity of NG-RAN) and a core network 108 (e.g., a 5G core network (5GC)) operating based on fifth-generation radio access technology described in the 3rd Generation Partnership Project (3GPP) standard for new radios.

[0054] Radio Access Network (RAN) entity 106 includes one or more Radio Access Network (RAN) nodes (also called base stations). RAN nodes can provide one or more cells. For example, a cell can be a macro cell, micro cell, femtocell, or picocell. A cell defines the coverage area or service area of ​​the RAN node. RAN nodes can be, for example, Node Bs (NodeBs or NBs), evolved Node Bs (eNodeBs or eNBs), next-generation Node Bs (gNBs), remote radio units (RRUs), remote radio heads (RRHs), relays, integrated access and backhaul (IAB) nodes, and low-power nodes. RAN nodes can be deployed in non-terrestrial network (NTN) equipment, such as satellites (e.g., low Earth orbit (LEO) or geostationary orbit (GEO) satellites), aircraft, or drones, where such NTN equipment forms a non-terrestrial network including ground stations. RAN nodes can also be deployed on the ground, in which case the RAN node can be referred to as a terrestrial network equipment. RANs including terrestrial network equipment are generally referred to as terrestrial networks.

[0055] RAN nodes can have a split architecture, where the functionality of the RAN node (eNB or gNB) is distributed among various entities. A RAN node with a split architecture can include Radio Units (RUs) (also known as Remote Radio Heads (RRHs)), Centralized Units (CUs), and one or more Distributed Units (DUs). DUs can be connected to RUs via fronthaul. DUs can be connected to CUs via midhaul or F1 interfaces. CUs can be connected to the core network (e.g., core network 108) via backhaul. In a RAN node with a split architecture, the operation of the RAN node can be performed by CUs and DUs. One CU can control one or more DUs.

[0056] The RU converts radio signals sent to and from the antenna into digital signals for transmission over the packet network, handles the digital front-end (DFE) and lower PHY layers, and includes digital beamforming functionality. The DU is a logical entity (e.g., software) hosted and running on a server located near the RU. The CU is a logical entity (e.g., software) hosted and running on a server. The CU can be hosted and running on its own server, or on the same server hosting and running the DU near the RU. The DU includes a subset of the RAN node's functionality (e.g., eNB or gNB) depending on the functional breakdown, and the CU includes additional RAN node functionality not included in the DU's functional subset. The DU may include a subset of the RAN node's protocol stack layers, and the CU may include additional layers of the protocol stack not included in the DU's layer subset. For example, in some implementations, the DU may include the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of the RAN node's protocol stack, while the CU may include layers of the RAN node's protocol stack above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Internet Protocol (IP) layer. The operation of DU is controlled by CU.

[0057] The core network 108 has a service-based architecture and includes multiple network functions, including, in particular, Access and Mobility Function (AMF) 112, Application Function (AF) 114, Authentication Server Function (AUSF) 116, Network Exposure Function (NEF) 118, Network Repository Function (NRF) 120, Network Slice Selection Function (NSSF) 122, Policy Control Function (PCF) 124, Session Management Function (SMF) 126, User Plane Function (UPF) 128, and Unified Data Repository (UDM) 130. Other network functions of the core network 108 (such as Network Data Analysis Function (NWDAF) and Bonding Support Function (BSF)) are not illustrated, but will be understood by those skilled in the art. The functionality of the core network's network functions is known to those skilled in the art and therefore will not be described in detail.

[0058] In addition to the network functions referenced above, core network 108 also includes a Sensing Management Function (SeMF) 134 and a Consent Management Function (CMF) 136. SeMF 134 is configured to provide sensing services to sensing service clients (such as UE 102) or one or more RAN entities 106, application functions or servers, or other network functions. CMF 136 is configured to receive information from, for example, SeMF 134 and identify associated processes for obtaining consent for object sensing prior to it.

[0059] CMF 136 can be implemented as a consent management entity. A consent management entity includes a combination of hardware processing circuitry and software (e.g., computer code) or software (e.g., computer code) including machine-readable instructions executable by at least one processor of the hardware processing circuitry. The hardware processing circuitry includes at least one processor and at least one memory. The processor includes any one or a combination of an accelerator, a microprocessor, the core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, a central processing unit, a graphics processing unit, and a tensor processing unit. The memory includes any one or a combination of volatile or non-volatile memory (e.g., flash memory, cache, random access memory (RAM), and / or read-only memory (ROM)). The memory stores machine-readable instructions of the software (e.g., computer code) for execution.

[0060] In the illustrated example, CMF 136 is depicted as a separate entity within the core network. Alternatively, CMF 136 could be part of SeMF or another NF. In yet another alternative, CMF 136 could be part of a third-party or independent entity, such as AF.

[0061] The core network also includes a Location Management Function (LMF), which provides location services for determining the location of user equipment. SeMF can optionally be integrated into the LMF.

[0062] Each network function (NF) of core network 108 provides one or more services to other network functions of the core network via an application programming interface (API). Each NF can also register itself and its supported services (such as services that provide other network functions) with NRF 120 of core network 108. NRF 120 is used by any network function to discover instances of other network functions (or NFs) and services supported by other NFs (such as services provided by other NFs). Any NF can operate to consume (e.g., use) services provided and exposed by another NF. NFs that consume services of another network function are generally referred to as network function service consumers. Network functions that provide and expose one or more of their services are referred to as network function service producers.

[0063] In an ISAC system, sensing is performed, for example, by a user equipment or a first radio access network entity (such as a gNB). When the first radio access network entity is configured for sensing operations (e.g., single-site sensing operations), it transmits sensing signals (e.g., RF signals), whereby the first radio access network entity acts as a sensing transmitter. When the first radio access network entity is configured for sensing operations (e.g., single-site sensing operations), it also receives sensing signals (e.g., radio signals), such as those deflected, reflected, or refracted by objects near the first radio access network entity, whereby the first radio access network entity is also considered or acts as a sensing receiver.

[0064] Alternatively, sensing is performed in a bi-site sensing system comprising a first radio access network entity (such as a gNB or UE) and a second radio access network node (such as another gNB or UE). When configured for sensing operations, the first radio access network entity emits sensing signals (e.g., radio signals), thus acting as a sensing transmitter. When the second radio access network entity is configured for sensing operations, it receives sensing signals deflected, reflected, or refracted by objects located near the second radio access network entity, thus acting as a sensing receiver.

[0065] Sensing can be performed in a multi-station sensing system, in which more than one network entity sends sensing signals and / or more than one network entity receives sensing signals.

[0066] In each of the single-site, dual-site, and multi-site sensing systems, sensing measurement data (or sensing data / sensing measurement information) includes data derived from sensing signals (e.g., radio signals) affected by objects in the environment of interest (e.g., reflection, refraction, diffraction) during the performance of sensing operations. Sensing measurement data may optionally be processed via network functions within a communication network, such as 5G and / or 6G systems, servers outside the communication network, application servers connected to the communication network via, for example, a NEF of the communication network, or edge servers (e.g., servers located near wireless communication servers). Sensing outputs include processed sensing data, such as sensing data requested by a sensing service consumer (also called a sensing service client, such as a UE) that provides sensing services including the sensing system's 5G and / or 6G systems.

[0067] Examples of sensing data or sensing measurement information include one or more pieces of information about received or arrived electromagnetic signals. Information about received or arrived electromagnetic signals may optionally include received power, delay, departure angle, angle of arrival, Doppler shift, etc.

[0068] Figure 1 The SeMF 134 shown is used to provide sensing services to sensing service clients in the communication network, such as UE 102, Application Function (AF) 114, or Network Exposure Function (NEF) 118. SeMF 134 is responsible for configuring, coordinating, and enabling network resources, such as RAN entity 106, for sensing operations.

[0069] SeMF 134 is implemented by a combination of hardware processing circuitry and software and / or firmware (including machine-readable instructions executable by the hardware processing circuitry) or software including machine-readable instructions executable by the hardware processing circuitry of a device. The hardware processing circuitry includes at least one processor and at least one memory storing machine-readable instructions executable by the hardware processing circuitry. The processor includes any one or a combination of an accelerator, a microprocessor, the core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, a central processing unit, a graphics processing unit, and a tensor processing unit. The memory includes any one or a combination of volatile or non-volatile memory (e.g., flash memory, cache, random access memory (RAM), and / or read-only memory (ROM)). The memory stores machine-executable instructions of the software and / or firmware for execution by at least one processor of the hardware processing circuitry. The machine-executable instructions can be executed by the hardware processing circuitry to perform actions or operations of the SeMF method described herein.

[0070] SeMF 134 receives perception requests for different types of perception services provided by SeMF 134 from perception service clients of the communication network (such as UE 102, Application Function (AF) 114, or Network Exposure Function (NEF) 118). SeMF 134 also determines the perception method to be performed (e.g., whether to use single-site or multi-site (e.g., dual-site) perception). In addition, SeMF 134 determines one or more RAN entities 106 to participate in the perception operation based on the determined perception method and the perception role of the corresponding RAN entity 106. For example, for each RAN entity in one or more RAN entities 106, SeMF 134 implemented or included in the perception management module 32 is operable to determine the perception configuration, including: perception resource configuration; perception session configuration (e.g., RAN entity that sends perception signals (perception transmitter (Tx role)) and / or RAN entity (or multiple RAN entities) that receives the corresponding perception signals (perception receiver (Rx role))); and perception data reporting configuration.

[0071] SeMF 134 interacts with one or more RAN entities 106 and sends the determined sensing configuration to one or more RAN entities 106 (e.g., during a sensing session establishment process that establishes a session for sensing services, which is generally referred to herein as a sensing session).

[0072] SeMF 134 is configured to determine or compute sensing output upon request. The sensing output may optionally include processed sensing data, for example, requested by a sensing service client. For instance, in one example, the processed sensing data is sensing data processed by SeMF 134. The processed sensing data includes data about objects in the area and / or data about features or about those objects. For example, one or more of the following—object position, velocity, velocity vector, shape, material, and / or size—are data about objects in the area. SeMF 134 is alternatively or additionally configured to provide sensing data received or collected from one or more sensing devices as sensing output. If a sensing service client requests sensing data, SeMF 134 is operable to provide the sensing data to the sensing service client. A sensed service client (also known as a sensed service consumer) is, for example: Application functions (such as being trusted by a Public Land Mobile Network (PLMN)) and requests are received directly from the Perception Service client; Application functions and requests received from the perception service client via NEF 118; UE, such as UE 102; Another network entity, such as the network functions of RAN nodes and / or communication networks, such as the network functions of the core network of communication system 100.

[0073] RAN entity 106 used in sensing includes the base station referenced above, and includes sensing functionality to provide sensing and / or positioning measurements, and to transmit signals for sensing and / or positioning. Optionally, other RAN entities may also be used, such as new network nodes dedicated to sensing purposes or parts of existing network nodes (e.g., positioning reference cells, reconfigurable smart surfaces).

[0074] In some implementations, the RAN entity verifies and implements the sensing configuration received from SeMF 134. RAN entity 106 also performs sensing admission control over sensing resources, transmits (Tx) and / or receives (Rx) (multiple) sensing signals, and updates and / or selects the sensing configuration of RAN entity 106, which is then provided to SeMF 134 and / or other RAN entities (e.g., via the Xn interface). Any RAN entity 106 operating as a sensing receiver receives sensing data according to a sensing data reporting configuration for processing sensing data to derive sensing output, and provides the sensing data to SeMF 134 (with or without processing the sensing data).

[0075] exist Figure 1In the example shown, SeMF 134 is a dedicated network function of core network 108. Alternatively, SeMF is a dedicated network function for one or more RAN entities 106. In some implementations, SeMF (e.g., SeMF functionality) is integrated into existing network functions of the communication network, such as Location Management Function (LMF), which provides location services for user equipment positioning in 5GS. In some implementations, SeMF functionality is distributed across multiple different network functions of the core network or integrated into one or more RAN entities 106. In the example implementation, SeMF 134 can operate as follows: The sensing method (e.g., single-site sensing, dual-site sensing, or multi-site sensing) is determined, and the sensing configuration of the RAN entities identified or selected to participate in the sensing session of the determined sensing method is determined. These determinations are made taking into account a) the requirements included in the sensing service request received from the sensing service client 34 (e.g., the sensing area of ​​the sensing service, the QoS requirements of the sensing service) and b) the static and / or dynamic sensing capabilities of the RAN entities. In the case of single-site sensing, SeMF identifies or selects one or more RAN entities to participate, and determines or generates sensing configurations for one or more RAN entities to configure one or more RAN entities as sensing transmitters (Tx) and sensing receivers (Rx) based on the determined sensing method, and provides the sensing configurations to one or more RAN entities. Alternatively, in the case of dual-site sensing and / or multi-site sensing, one RAN entity is identified or selected as a sensing transmitter and one or more other RAN entities (e.g., BS) are identified or selected as sensing receivers, and sensing configurations for configuring one RAN entity as a sensing transmitter and for configuring one or more other RAN entities (e.g., BS) as sensing receivers are determined or identified. The perception admission control process identifies whether the identified or selected RAN entity has available perception resources (e.g., perception requirements) for the requested perception service and determines the perception resource configuration for the identified or selected RAN entity. Depending on the method or scheme implemented using the selected single-site, dual-site, or multi-site approach, the perception resource configuration includes reference signals and / or pilots and / or user data and control plane resources. The system determines the awareness consent requirement and sends an consent request to CMF 136, which includes awareness-related information such as the type of awareness service, the awareness area, and the type of object to be awareness. SeMF 134 can be configured to wait for a response to the consent request and determine whether to initiate awareness based on that response. Depending on the selected sensing method, a sensing session establishment request is sent to one or more RAN entities to establish a sensing session, including one or more of the following: sensing configuration for each corresponding selected RAN entity, used to configure the corresponding RAN entity as a sensing transmitter and / or sensing receiver; sensing resource configuration; sensing session configuration; sensing data reporting configuration, i.e., whether sensing measurements (sensing data) will be transmitted from the RAN entity (e.g., BS) to the SeMF using control plane-based reporting or user plane (e.g., to or via a dedicated server), and the resources and configuration for reporting; one or more identifiers for the sensing session. Each identifier of the sensing session identifies the sensing session and is generally referred to as the sensing session identifier, and collectively as the sensing session identifiers. Generate a sensing session identifier (ID) for the determined sensing method and assign it to one or more RAN entities participating in the selected sensing session. The sensing session identifier (ID) is used to uniquely identify and coordinate sensing operations between different RAN entities and to send sensing measurements and / or sensing data belonging to the same sensing session from RAN entities (or multiple RAN entities) to SeMF.

[0076] Consent Management Function (CMF) 136 can operate as follows: Receive consent requests from SeMF 134, which include perception-related information such as the type of perception service, the perception area, and the type of object to be perceived. Determine the appropriate process for obtaining consent before initiating perception. Obtain information identifying the owner of the object or identifying the sensing area used to sense the object, and send a request for consent to sense the object to the user device or entity associated with the object owner. Broadcasting or initiating a request for consent to be perceived on a broadcast channel, or initiating a search for the UE in the perception area without knowing the owner of the object. Consent is determined based on the region of interest used for perception. In cases of emergency awareness, perceived consent can be provided without further consent from the relevant UE or third party. Based on the response to the consent request, specify the data types that may be sent and the perceived validity period.

[0077] Within the context of the same sensing session, one or more single-site sensing operations or one or more multi-site sensing operations can be initiated. Furthermore, the same RAN entity can optionally participate in one or more single-site sensing operations and one or more multi-site sensing operations. Additionally, in some implementations, the RAN entity is identified or selected as a sensing transmitter and configured to transmit sensing signals based on a sensing configuration, and / or identified or selected as a sensing receiver and can be configured to receive sensing signals based on a sensing configuration. Each of the one or more RAN entities 106 in the system is any suitable entity with sensing capabilities (e.g., a dedicated unit or element for receiving sensing signals, a reconfigurable smart surface with integrated sensing capabilities, or for assisting ISAC).

[0078] Each RAN entity 106 can operate as follows: Send a response to the Sensing Session Establishment Request to SeMF. The response includes an indication of acceptance (success) or failure to provide and / or support and / or establish a Sensing Session. The response also includes a reason code indicating the reason for the failure to provide and / or support and / or establish a Sensing Session. After establishing a sensing session, it performs self-configuration based on the received sensing resource configuration and sensing session configuration, and enables the corresponding RAN entity to perform sensing operations. When participating in a sensing session (e.g. identified by a sensing session ID) and configured as or acting as a sensing receiver, the corresponding sensing data (e.g., measurements obtained when the RAN entity performs a sensing operation) is sent to the SeMF. Optionally, perception admission control can be performed, and the perception resources used to transmit or receive perception signals can be determined based on the perception resource configuration received from SeMF.

[0079] Interactions between SeMF 134 and RAN entities (multiple) 106 occur via a direct interface or via AMF 112. AMF 112 uses a non-UE-associated mode to transparently route messages between RAN entities (e.g., access nodes) 106 and SeMF 134 via an interface (e.g., via the NG-C interface). The Next Generation Application Protocol (NGAP) terminated between AMF 112 and RAN entities (e.g., NG-RAN nodes) can be used as a delivery protocol for delivering awareness protocol messages via the NG-C interface.

[0080] In some implementations, admission control is performed by RAN entity 106. SeMF 134 provides RAN entity 106 with information such as the QoS of the requested sensing session, an indication of the requested sensing service type, and sensing requirements of the sensing session (e.g., sensing area, sensing duration, sensing update rate, etc.). This information allows one or more RAN entities to determine the resources required for the sensing session. RAN entities configured as sensing transmitters (having a sensing transmission role, e.g., when SeMF 134 selects RAN entity 106 to participate in a dual-site sensing approach) provide their sensing resource configuration (e.g., sensing signal frequency, bandwidth, timing of sensing signal transmission by RAN entity 106) and / or sensing session configuration to: one or more RAN entities 106 configured as sensing receivers with corresponding sensing sessions via the Xn interface (inter-RAN entity); or to SeMF 134, e.g., via the NG interface; or to AMF 112, e.g., using a mechanism similar to Remote Interference Management (RIM) information transmission.

[0081] Although described herein as one or more RAN entities used in sensing, the methods and processes described are equally applicable to one or more UEs. Such UEs are similarly configured to operate as sensing devices. A UE can be configured to operate as a sensing transmitter or a sensing receiver, or both. Therefore, sensing devices are not limited to RAN entities, and a UE can operate as a sensing transmitter, a sensing receiver, or both.

[0082] Figure 2 The physical and logical components of an example apparatus 200 according to an embodiment of the present disclosure are shown. The apparatus 200 includes one or more network functions of a communication network 100, including, for example, SeMF 134 and / or CMF 136. Although example implementations of apparatus 200 are shown and described below, other apparatuses may be used to implement the examples of SeMF 134 and / or CMF 136 disclosed herein, which may include... Figure 2 The different logical and physical components shown. And, although... Figure 2 A single instance of each logical and / or physical component of device 200 is shown, but Figure 2 Each logical and / or physical component shown may have multiple instances.

[0083] Device 200 includes one or more processors 202, such as a central processing unit (CPU), microprocessor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), application-specific logic circuit system, graphics processing unit (GPU), tensor processing unit, neural processing unit, dedicated artificial intelligence processing unit, hardware accelerator, quantum processor, or any combination thereof. One or more processors 202 may generally be referred to as processor 202 and are collectively referred to as processor 202.

[0084] The device 200 also includes one or more memories 204 (generally referred to as memory 204, and collectively referred to herein as "memory 204"), which may include volatile or non-volatile memory (e.g., flash memory, random access memory (RAM), and / or read-only memory (ROM)). Memory 204 may store machine-executable instructions for execution by at least one of one or more processors 202. For example, machine-executable instructions 206 of the CMF 136 described herein are shown stored in memory 204, which may be executed by at least one of one or more processors 202 to cause the device 200 to perform the operations of the CMF 136 described herein and / or the SeMF 1034 described herein. Memory 204 may store machine-executable instructions for execution by processor 202, such as those referenced above. Figure 1 The machine-executable instructions describe the other network functions of the core network 108.

[0085] In addition to machine-executable instructions 206, memory 204 may also store data, information, rules and / or policies.

[0086] In some examples, device 200 may also include one or more electronic storage units (not shown), such as solid-state drives, hard disk drives, disk drives, and / or optical disk drives. In some examples, one or more datasets and / or modules may be provided by external memory (e.g., an external drive that is wired or wirelessly connected to the computing system), or by transient or non-transient computer-readable media. Examples of non-transient computer-readable media include RAM, ROM, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, CD-ROM, or other portable storage devices. Storage units and / or external memory may be used in conjunction with memory 204 to enable data storage, retrieval, and caching functions of device 200.

[0087] For example, the processor 202 and memory 204 of device 200 can communicate with each other via a communication bus. In some implementations, device 200 is a distributed computing system that includes multiple computing devices (e.g., servers) communicating with each other via a data network, and optionally one or more additional components. In some implementations, the various operations described herein can be performed by different computing devices (e.g., servers) of the distributed computing system. In some implementations, device 100 is a virtual machine provided by the infrastructure (e.g., hypervisor, processor, and memory) of a cloud computing system.

[0088] refer to Figure 3 An example of user equipment 102 is shown. Although Figure 3 A single instance of each physical and / or logical component of user equipment 102 is shown, but user equipment 102 may include... Figure 3 Multiple instances of each physical and / or logical component are shown.

[0089] User equipment 102 can be any device capable of transmitting and receiving radio signals. Non-limiting examples of user equipment include mobile stations (MS), mobile devices (such as mobile phones or so-called 'smartphones'), computers equipped with wireless interface cards or other wireless interface facilities (such as USB dongles), personal digital assistants (PDAs) or tablet computers equipped with wireless communication capabilities, machine-type communication (MTC) devices, Internet of Things (IoT) type communication devices, or any combination of these.

[0090] User equipment 102 also includes one or more processors 301, one or more memories 302 (collectively referred to as memory 302), and other components or circuit systems 303 for software and hardware-assisted execution of operations configured to be performed by user equipment 102, including access to a radio access network (e.g., Figure 1 The illustrated RAN controls access and communication. Processor 301 is coupled to memory 302. One or more processors 301 may include a central processing unit (CPU), microprocessor, multi-core processor, tensor processing unit (TPU), graphics processing unit (GPU), neural processing unit (NPU), application-specific logic circuit, application-specific integrated circuit, field-programmable gate array (FPGA), dedicated artificial intelligence processing unit, hardware accelerator, quantum processor, or any combination thereof. Memory 302 may include volatile or non-volatile memory (e.g., flash memory, random access memory (RAM), and / or read-only memory (ROM)).

[0091] Processor 301 can be configured to execute software code 308 (e.g., the processor can execute the instructions of software code 308). Execution of software code 308 (or execution of the instructions of the software code) can, for example, cause user equipment 102 to perform one or more operations, including those described herein with respect to… Figure 9 The described operation. Software code 308 can be stored in memory 302.

[0092] User equipment 102 also includes antenna array 304 and transceiver 306 for transmitting radio signals (e.g., radio signals) to and / or receiving radio signals from access nodes of the access network (e.g., radio access network nodes of the RAN) via air interface 307. The radio signals (e.g., radio signals) may carry communications such as voice, email, text messages, multimedia data, and / or machine data. Antenna array 306 may be disposed inside or outside user equipment 102. Antenna array 306 may include one or more antenna elements. Antenna array 306 may be a multiple-input multiple-output (MIMO) antenna.

[0093] The processor 301, at least one memory 302, transceiver 306, and other components or circuitry 303 of user equipment 102 (e.g., a modem) may be provided on a circuit board, in a chipset, or on a system-on-a-chip (SOC). Figure 3 The reference numeral 304 indicates the reference numeral 102. User equipment 102 may optionally include a display device 205, such as a touch-sensitive display device. User equipment 102 also includes a battery (not shown). User equipment 102 may also include a speaker (not shown) and a microphone (not shown). User equipment 102 may also include a Universal Subscriber Identity Module (USIM) (not shown) or an Embedded Subscriber Identity Module (eSIM) (not shown).

[0094] Figure 4This is a flowchart illustrating a method or process according to an example. This method or process is performed by CMF 136. In step 402, CMF 136 receives a request from SeMF 134 to consent to object sensing. The request received from SeMF 134 includes sensing-related information (e.g., the type of sensing service requested) and sensing requirements for the sensing session, including the sensing area and, for example, the sensing duration and the type of object to be sensed. The type of object to be sensed can include any suitable object, such as a vehicle, drone, UAV, person, pedestrian, pet, animal, robot, building, or any other suitable object. Additionally, the sensing-related information may identify the information to be sensed, such as the object's size, movement, speed, or whether the sensing is limited to the sensing area or can be extended, such as continuing to detect moving objects. Additional information may be included, such as the number of sensing entities involved in the sensing, i.e., the number of entities sending and / or receiving sensing signals.

[0095] In 404, CMF 136 obtains identification information about the owner of the object or identification information about the sensing area used to sense the object. In this document, the term "owner" is used to refer to the owner of the object, or alternatively, a responsible stakeholder associated with the object. The owner of the object or the associated UE may be known or registered by CMF 136 or other parts of the core network 108, or obtained by the core network 108. Therefore, CMF 136 obtains identification information either from itself or from the core network 108.

[0096] Alternatively, CMF 136 may initiate a search for the UE in the sensing area in 404, or may initiate a broadcast notification message to identify the owner of the object in the sensing area.

[0097] Optionally, CMF 136 may send a request to Access and Mobility Management Function (AMF) 112 to discover user equipment in the sensing area. In response to the request sent to AMF 112 to discover user equipment, CMF may receive a list identifying user equipment in the sensing area. The list identifying user equipment includes objects and / or UEs that can be associated with objects and / or the sensing area.

[0098] In 406, CMF 136 sends a request for consent to a sensed object. This request may include an indication of the type of consent, i.e., the type of consent used for sensing. The type of consent may be, for example, consent from a UE that is identified as the owner or stakeholder of the object or sensed area. Alternatively, the type of consent may be consent from a UE that has been instructed by the network to provide consent to the sensed object or sensed area, and indicating the reason for the UE's identification, such as the UE being located in or near the area of ​​interest of the object to be tracked. If the UE has already received a broadcast message providing consent to the sensed object or sensed area, the request may indicate that an explicit consent response is required within a defined time period, or it may indicate that only a consent refusal must be provided, otherwise consent is considered received.

[0099] In the example of the known object owner in the perceived area referenced above, CMF 136 sends a request for consent to the perceived object to the UE or a third-party application function responsible for maintaining consent-related information, including, for example, consent or consent conditions, such as the perception type. The consent request includes information related to the perception of the object.

[0100] In examples where the owner is unknown or unregistered, the CMF 136 initiates a UE search or broadcasts a notification message in the target sensing area. The broadcast notification message is a consent request and may include, for example, the consent type indicating the type of object sensing to be performed, the sensing area, the type of object to be sensed, and the sensing service. The broadcast may be a broadcast message after which the CMF 136 waits for consent to proceed with sensing. Alternatively, the broadcast may be a notification to UEs in the sensing area that object sensing will be performed if there is no response to the consent request being rejected.

[0101] In the example where CMF 136 sends a request to AMF 112 to discover user equipment, an consent request is sent based on a list of user equipment whose identifiers include the object.

[0102] The consent request may include additional information, such as the types of data that can be sent, perceived QoS information (such as perceived resolution and / or perceived accuracy), and the validity period of the perceived service.

[0103] Based on the response received from CMF 136 to the consent request, the process continues from 408 to 410 or 412. Based on the response from the user equipment indicating consent to be perceived as an object, the process continues in 410, and CMF 136 provides SeMF 134 with a response to the consent to be perceived as an object. The response to the consent to be perceived request indicates consent to be perceived as an object.

[0104] Based on the indication of disagreement regarding the perceived object, the process continues at 412, and CMF 136 provides SeMF 134 with a response to the request for consent to object perception. The indication of disagreement may be a lack of response or a refusal. In response to receiving a refusal of the request for consent to object perception, the response to the request for consent to object perception sent to SeMF 134 indicates that consent to perception of the object is not provided. CMF 136 may send a response to SeMF 134 that includes indications to exclude the object from perception and / or to provide the perception client with information about the specific object and / or to store information about the specific object.

[0105] As referenced above, a lack of response may indicate a lack of agreement. Referring to the example of CMF 136 initiating a broadcast notification message, CMF 136 may wait for a predetermined period of time in response to a request for consent to be perceived. When a response indicating consent is received from the user equipment within the predetermined period of time, the process continues from 408 to 410. If no response is received from the user equipment within the predetermined period of time, the lack of response can be considered a lack of agreement. Therefore, CMF 136 may send a response to SeMF 134 in 412 to a request for consent-aware management functionality, which includes an indication that the owner of the object has not yet consented to the perceived object.

[0106] Figure 5 This is a flowchart illustrating a method or process according to an example. This method or process is executed by SeMF 134. At 502, a sensing service request is received at SeMF. The sensing service request is a request for a sensing service supported or provided by SeMF 134. The sensing service request includes information related to the sensing service requested by the sensing service client. Example information related to the sensing service included in the sensing service request may include one or more of the following: an indication of the type of sensing service requested, information indicating the sensing requirements of the sensing service, an indication of the quality of service of the sensing service, and information indicating the sensing area, sensing duration, and the type of object to be sensed.

[0107] In 504, SeMF 134 sends a request to CMF 136 to consent to object awareness. The request sent to CMF 136 includes information related to awareness.

[0108] In 506, a response to a request for consent to object awareness is received from CMF 136. As referenced above, the response may be an instruction to provide consent to object awareness, or it may be an instruction not to provide consent, i.e., object awareness is not permitted.

[0109] In 512, object sensing is not initiated based on the determination that consent has not been provided to the sensing object, and a response is provided to the sensing client indicating that object sensing is not allowed.

[0110] Based on this response, it is determined in step 508 whether to begin object sensing. Based on the determination of consent to provide the object for sensing, object sensing can be initiated by sending a message to one or more devices to begin sensing. In step 510, a response is sent to the sensing client, indicating consent to provide the object for sensing.

[0111] SeMF 134 initiates sensing and determines the sensing configuration. Determining the sensing configuration includes selecting a sensing method (e.g., a sensing mode) based at least in part on information related to the sensing service. This selection may include selecting entities and the sensing mode for each entity. For example, the selection may include selecting one of single-site sensing for the sensing service (where a first RAN entity is used to transmit and receive radio signals for sensing) and multi-site sensing (e.g., dual-site sensing) (where one of the selected RAN entities is used to transmit radio signals for sensing, and one or more other selected RAN entities are used to receive radio signals for sensing).

[0112] Based on the determined sensing configuration, sensing configuration information is sent from SeMF 134 to the entities participating in sensing. For example, if single-site sensing is selected, SeMF 134 can send the sensing configuration of a first entity to a first entity used for transmitting and receiving radio signals for sensing. This sensing configuration includes at least one of sensing resource configuration, sensing session configuration, and sensing data reporting configuration. For multi-site (e.g., dual-site) sensing, SeMF 134 can send the sensing configuration of a selected entity to a selected entity used for transmitting radio signals for sensing. This sensing configuration includes at least one of sensing resource configuration, sensing session configuration, and sensing data reporting configuration. Moreover, in the case of multi-site sensing, SeMF 134 can send the sensing configuration for each corresponding other entity used for receiving radio signals. The selected entities may include, for example, RAN nodes or other devices operable to transmit and / or receive sensing signals.

[0113] Figure 6This is a flowchart illustrating a method or process according to an example. This method or process is performed by a UE (such as UE102). In 602, UE102 receives a broadcast request for consent to object perception via a broadcast channel. The broadcast request is one or more broadcast notification messages that include information related to object perception. This information may include information identifying the perception area. This information may also include a consent type, indicating the type of consent used for object perception. One or more broadcast notification messages may be initiated by CMF 136. Alternatively, the request may be a unicast request or multiple unicast requests instead of a broadcast request.

[0114] In step 604, based on information related to object awareness, it is determined whether the object's owner consents to the object's awareness. Consent may be provided in advance by the owner and information stored on the UE, or it may be provided in response to a broadcast notification message. Therefore, the UE identifies the type of consent request process, determines whether to provide consent based on rules and / or interactions with the user, and prepares a response.

[0115] Optionally, the UE can inform the application layer at the UE to display or deliver messages to the owner. Therefore, the owner can take action based on the information received in the consent request message and / or the type of device (e.g., vehicle, UAV, smartphone, etc.). Alternatively or additionally, some actions can be performed autonomously by the UE or interactively by the owner.

[0116] In response to determining in 604 that the owner of the object consents to the perceived object and / or perceived area, a response to the broadcast consent request is provided in 606. This response includes an indication of the owner's consent to the perceived object and / or perceived area.

[0117] Alternatively or additionally, the response may include one or more conditions or constraints on the perception. For example, the response may include an indication of the duration of perception, a perception area or sub-region within that area that allows perception, perception accuracy, perception resolution, features or attributes of the object that allows perception, modification of specific features of the object, and other conditions or constraints.

[0118] In response to determining in 604 that the owner of the object does not consent to the perception of the object and / or the perception area, a response to the broadcast consent request is provided in 608. This response includes an indication that the owner of the object does not consent to the perception of the object and / or the perception area. The response may also indicate the reason for rejecting (i.e., not consenting to) the request. For example, the response may indicate that the UE is not associated with the object, that the area is a private area, or any one or more other reasons.

[0119] Figure 7This is a diagram illustrating the operation of an example process according to an embodiment. The diagram illustrates messages or commands sent during this process between a UE (such as UE 102), the owner or stakeholder of the sensing area or object, a sensing signal receiver 702, a sensing signal transmitter 704, a SeMF 134, a CMF 136, and a sensing service client 706.

[0120] In 710, a sensing service request is sent from the sensing service client 706 to SeMF 134. (See reference...) Figure 5 As indicated, a perception service request is a request for a perception service supported or provided by SeMF 134. A perception service request includes information related to the perception service requested by the perception service client, such as, for example, the target perception area, the type of perception service, the duration of the perception service, the type of object(s) to be perceived, the attributes of the object(s) to be perceived, and the periodicity of the perception.

[0121] In 712, SeMF 134 authenticates and confirms the sensing client 706, which is authorized by the sensing service requested.

[0122] SeMF 134 defines the perception consent requirement in 714. The perception consent requirement may be based on the area to be perceived, the type of object to be perceived, the resolution of the perception, the accuracy of the perception, and the attributes of the perceived object (such as one or more of shape, size, material, and mobility). Based on the consent requirement, SeMF prepares a consent request, including a consent requirement based on the perception service request identifier.

[0123] In 716, a consent request is sent to CMF 136. For example, SeMF 134 sends a consent request to CMF 136 in 716 for an object in a region where sensing is to be performed and consent is required. The consent request includes information related to sensing (e.g., the type of sensing service requested) and sensing requirements for the sensing session (e.g., the sensing region, the sensing duration, and the type of object to be sensed).

[0124] In this example, CMF 136 knows the owner of the object, or that it is stored in memory and accessible to CMF 136. Therefore, in 718, CMF identifies the owner of the object or perceived area based on the information included in the consent request.

[0125] In step 720, CMF 136 sends a request for consent to be perceived by an object to UE 102. In this example, the owner of the object in the perceived area is known, and CMF 136 sends the request for consent to be perceived along with consent-related information to UE 102. The consent-related information includes, for example, consent or consent conditions, such as the type of perceived service. The consent request includes information related to the perception of the object. The consent request may include additional information, such as the data types that can be sent and / or monitored, the duration of the perceived service, perceived QoS information (such as perceived accuracy and / or perceived resolution), and the validity period of the perceived service.

[0126] UE 102 determines its response to the consent request in step 722 based on the information provided along with the consent request. UE 102 may utilize previously provided consent from the owner and information stored on UE 102 to determine its response to the consent request. Alternatively, UE 102 may determine its response to the consent request in step 722 based on interaction with the user. For example, the application layer at the UE may be informed, and a consent request message may be displayed or otherwise delivered to the user, who can then respond to the consent request message.

[0127] Based on the determination in 722, UE 102 sends a response to the consent request to CMF 136 in 724. The response may indicate the consent-aware object, or it may indicate disagreement by rejecting the consent request.

[0128] In 726, CMF 136 provides SeMF 134 with a response to a request for consent to be object-aware. The response to the request for consent to be object-aware may indicate consent to be object-aware, or it may indicate consent not to be provided for object-awareness.

[0129] Based on the response received at SeMF 134 in 726, SeMF 134 determines in 728 whether to initiate sensing. Based on the determination to initiate sensing in 728, SeMF 134 initiates sensing and determines the sensing configuration in 730. As described above, determining the sensing configuration includes selecting a sensing method (e.g., a sensing mode) based at least in part on information related to the sensing service. This selection may include selecting entities and the sensing mode for each entity. For example, the selection may include selecting one of single-station sensing for the sensing service (where a first entity is used to transmit and receive radio signals for sensing) and multi-station sensing (e.g., dual-station sensing) (where one selected entity is used to transmit radio signals for sensing, and one or more other selected entities are used to receive radio signals for sensing).

[0130] Sensing configuration information is sent from SeMF 134 to the participating entities, and sensing operations are performed in 732. Based on the determined sensing configuration, the participating entities include one or more sensing signal receivers 702 and one or more sensing signal transmitters 704. As indicated above, the sensing signal receivers 702 and sensing signal transmitters 704 can be single entities operable to perform single-site sensing.

[0131] In 734, the perception service response is sent from SeMF 134 to the perception client 706. The perception service response may include perception data that has been processed in some way. For example, the perception data may be processed at SeMF 134, and the processed data may be provided to the perception service client in response to the original request from the perception service client.

[0132] The above process is described with reference to the consent of a single object. The process described above, as referenced in references 718 to 724, can be performed on each object in the sensing area, such that an instruction for consent or refusal of consent is received at CMF 136 for each object. CMF 136 can send a response in 726 to SeMF 134, which includes an instruction to exclude one or more objects from the sensing and / or a portion of the sensing area. Therefore, SeMF 134 can begin sensing, but without sensing one or more objects or without sensing a portion of the target sensing area.

[0133] Figure 8 This is a diagram illustrating the operation of a process according to another example of an embodiment. The diagram illustrates messages or commands sent between the UE (such as UE 102), the owner or stakeholder of an object in the sensing area, the sensing signal receiver 802, the sensing signal transmitter 804, the AMF 112, the location management function (LMF) 808, the SeMF 134, the CMF 136, and the sensing service client 806 in the core network during this process.

[0134] In 810, a sensing service request is sent from the sensing service client 806 to the SeMF 134, including information related to the sensing service requested by the sensing service client.

[0135] In 812, SeMF 134 authenticates and confirms the sensing client 806, which is authorized by the sensing service requested.

[0136] SeMF 134 defines the perception consent requirement in 814. The perception consent requirement may be based on one or more of the following: the area to be perceived, the type of object to be perceived, the resolution of the perception, the accuracy of the perception, and the attributes of the perceived object (such as one or more of shape, size, material, and mobility). Based on the consent requirement, SeMF prepares a consent request, including a consent requirement based on the perception service request identifier.

[0137] In 816, a consent request is sent to CMF 136. For example, SeMF 134 sends a consent request to CMF 136 in 816 to conduct perception in an area called the perception area. The consent request includes information related to perception (e.g., the type of perception service requested) and perception requirements for the perception session (e.g., the perception area, the perception duration, and the type of object to be perceived).

[0138] In this example, CMF 136 neither knows the owner of the object nor stores it in memory, and it cannot be accessed by CMF 136. In step 818, CMF 136 verifies that the owner is neither known nor stored at CMF 136. Therefore, the owner is unknown or unregistered at CMF 136. CMF 136 determines the sense area and information including parameters in the request to be sent to Access and Mobility Management Function (AMF) 112 to identify the candidate UE to which the consent request is to be sent.

[0139] In 820, CMF 136 initiates a search for the object owner by sending a request to AMF 112 to discover the UE in the sensing area. The request to discover the UE is a request to obtain the identification information of the UE connected to the RAN node, which provides cell coverage at least part of the sensing area.

[0140] Therefore, in 822, AMF 112 identifies UEs connected to one or more RAN nodes that provide cells covering at least a portion of the sensing area in order to request location information for the UEs to identify the UEs in the sensing area.

[0141] In step 824, AMF 112 may additionally send a location service request to LMF 808, requesting location information of UEs connected to one or more RAN nodes providing coverage of at least part of the sensing area. LMF 808 determines the location of each UE in step 826 and provides that location to AMF 112 in step 828.

[0142] In 830, based on the location of each UE in the UE, AMF 112 can identify the UEs in the sensing area and provide the CMF with a list of UEs in the sensing area. For the purposes of this example, the UEs in the sensing area include UE 102.

[0143] Alternatively, AMF 112 can provide a list of UEs and location information to CMF 136, and CMF 136 can identify UEs in the sensing area, as shown in 832. As indicated, UEs in the sensing area include UE 102. The selection or identification of UEs can also depend on the type of sensing request, the distribution of UEs, and the area where sensing is expected to occur.

[0144] In 834, CMF 136 sends a request to UE 102 for consent to a perceived object, which in this example is UE 102 or associated with UE 102. Figure 8 The processes 834 to 848 illustrated are similar to those referenced in this article. Figure 7 Processes 720 to 734 are described. Therefore, these processes will not be described in detail here.

[0145] The above process is described with reference to perceiving consent from a single UE or object. Processing can be performed on each object in the perception area, such that an indication of consent or rejection is received at CMF 136 for each UE. CMF 136 can send a response to SeMF 134 in 840, which includes an indication to exclude one or more objects or object types from perception or to modify the attributes and QoS (e.g., perception accuracy and / or perception resolution) of the perception session. Therefore, SeMF 134 can initiate perception, but one or more objects are not perceived. Thus, SeMF can decide to cancel perception, or optionally modify perception, such as reducing the perception area.

[0146] In the example above, sensing can begin, but one or more objects may not be detected. SeMF can then cancel sensing or modify sensing. Cancellation or modification of sensing may also occur in other examples described herein.

[0147] Figure 9 This is a diagram illustrating the operation of a process according to another example of an embodiment. The diagram illustrates messages or commands sent between the sensing signal receiver 902, sensing signal transmitter 904, AMF 112, SeMF 134, CMF 136, sensing service client 906, network exposure function (NEF) 118, and third-party application function (AF) 111 during this process.

[0148] In this example, consent to the perceived object is provided through a third party, AF 111, rather than through the owner's UE. Therefore, consent is sought from AF 111, which can... Figure 9 The NEF 118 access is shown. When an object is not owned or managed by a physical entity, a third-party AF 111 can convey consent. For example, a third-party AF 111 can convey consent to track moving objects in controlled public areas such as museums or schools.

[0149] Figure 9 The processes 910 to 916 illustrated are similar to those referenced in this article. Figure 7 Processes 710 to 716 are described. Therefore, these processes will not be described in detail here.

[0150] In this case, CMF 136 identifies a third party, AF 111, in 918 to seek consent for the perceived area.

[0151] In 920, CMF 136 sends a consent request to AF 111 for the object to be sensed. The consent request includes information related to consent, including one or more of the following: sense type, sense area, type of object to be sensed, and validity period of sense service.

[0152] AF 111 determines the response to the consent request in 922 based on the information provided along with the consent request.

[0153] In 924, AF 111 sends a response to the consent request to CMF 136. The response from AF 111 to CMF 136 includes an indication of consent to the perception or an indication of disagreement or refusal of the consent request, the duration of the perception service, the size of the object, and the periodicity of the perception.

[0154] Figure 9 The processes 926 to 934 illustrated are similar to those referenced in this article. Figure 7 Processes 726 to 734 are described. Therefore, these processes will not be described in detail here.

[0155] Figure 10 This is a diagram illustrating operations in a process according to another example of an embodiment. The diagram illustrates messages or commands sent between a UE (such as UE 102), a sensing signal receiver 1002, a sensing signal transmitter 1004, an AMF 112, a SeMF 134, a CMF 136, and a sensing service client 1006 during this process.

[0156] Figure 10The illustration depicts the process of seeking consent when sensing in a private area. The private area may be a controlled or sensitive area, such as a government facility requiring explicit consent. In this example, UE 102 is a UE, or there may be more than one UE, responsible for providing consent or rejection of requests for sensing in the private area.

[0157] Figure 10 The processes 1010 to 1016 illustrated are similar to those referenced in this article. Figure 7 Processes 710 to 716 are described. Therefore, these processes will not be described in detail here.

[0158] In 1018, CMF 136 defines the configuration for a message used for broadcasting, which includes a consent-aware request. In 1020, a message including a consent-aware request is broadcast. This message includes an indication of one or more of the following: the desired consent type (also known as consent type), the awareness area, the awareness mode, the awareness service type, the type of object to be aware of, and any other suitable information.

[0159] CMF 136 can set a timer in 1024 and wait for a predetermined period of time to collect consent responses from each UE.

[0160] In 1022, a broadcast message is received at UE 102, and UE 102 processes the message to determine whether to provide perceived consent based on the information in the broadcast message.

[0161] UE 102 can provide a response to a consent request to CMF 136 in 1026. The response can indicate the consent-aware object, or it can indicate disagreement by rejecting the consent request.

[0162] CMF 136 can use a timer set by CMF 136, and the absence of a response from UE 102 can be interpreted as an indication of disagreement. Therefore, CMF 136 waits a predetermined period for a response to a request for consent. Consent is granted when a response indicating consent is received from the user equipment within the predetermined period. Failure to receive a response from UE 102 within the predetermined period is an indication of disagreement.

[0163] Figure 10 The processes 1028 to 1036 illustrated are similar to those referenced in this article. Figure 7 Processes 726 to 734 are described. Therefore, these processes will not be described in detail here.

[0164] Figure 11This is a diagram illustrating operations in a process according to another example of an embodiment. The diagram illustrates messages or commands sent between a UE (such as UE 102), a sensing signal receiver 1102, a sensing signal transmitter 1104, an AMF 112, a SeMF 134, a CMF 136, and a sensing service client 1106 during this process.

[0165] exist Figure 11 In the example, the target object or perception is located in a public area that is not controlled by the entity or stakeholder.

[0166] Figure 11 The processes 1110 to 1116 illustrated are similar to those referenced in this article. Figure 7 Processes 710 to 716 are described. Therefore, these processes will not be described in detail here.

[0167] In 1118, CMF 136 determines the configuration of a message to be broadcast, which includes a request for consent to awareness. In this example, the consent request is a message indicating that awareness will be performed in the area in the absence of a rejection from the UE. In 1120, a message including the request is broadcast. This message includes the required consent type (also known as consent type), information identifying the awareness area, the awareness mode, the awareness service type, the type of object to be perceived, and any other appropriate information.

[0168] although Figure 11 As not shown, the CMF can set a timer and wait for a predetermined period of time to provide a response request to each UE. However, in this example, the lack of a response is an indication of agreement.

[0169] In 1122, a broadcast message is received at UE 102, and UE 102 processes the message to determine whether to reject the consent-aware request based on the information in the broadcast message.

[0170] In 1124, UE 102 can provide a response to a consent request to CMF 136. The response in this example indicates a refusal of consent-awareness.

[0171] When a response indicating a refusal to consent is received from the user equipment within a predetermined time period, CMF 136 removes the identifier of UE 102 from the sensing operation. Therefore, an object can be sensed, but no identification information is associated with it. Alternatively, the object can be excluded from sensing (e.g., being sensed).

[0172] Figure 11 The processes 1128 to 1136 illustrated are similar to those referenced in this article. Figure 7 Processes 726 to 734 are described. Therefore, these processes will not be described in detail here.

[0173] The functions, processes, and operations described herein may be executed in different orders, or may be executed concurrently with each other, or a combination thereof. Furthermore, one or more of the functions, processes, and operations may be optional or may be combined. It should be understood that... Figures 4 to 6 The flowchart shown and Figures 7 to 11 The process illustrated is merely an example. The various operations and processes depicted can be omitted, rearranged, combined, or a combination of rearrangement and combination.

[0174] Advantageously, even in instances where the object is not connected to a communication network, consent to perceive the object within the communication network can be obtained. Appropriate methods can be determined to obtain perceptual consent, and consent can be obtained based on information, including the area to be perceived.

[0175] The scope of the claims should not be limited to the implementations stated in the examples, but should be given the broadest interpretation consistent with the entire description.

[0176] Example 1. A method comprising: receiving a request for consent to perceive an object from a perception management function; obtaining identification information identifying the owner of the object, or identification information identifying a perception area used to perceive the object; based on the identification information, sending a request for consent to perceive the object to a user device associated with the owner of the object or an entity associated with the owner of the object, the consent request including information related to the perception of the object; based on receiving a response to the consent request from the user device or the entity, the response to the consent request instructing consent to perceive the object, and providing the perception management function with a response to the request for consent to perceive the object, the response to the request for consent to perceive the object instructing consent to perceive the object.

[0177] Example 2. The method according to Example 1 includes: sending a request to a network entity to discover user equipment in a sensing area before sending a consent-aware request; in response to the request to discover user equipment, receiving a list of user equipment identified in the sensing area, wherein objects are included in the list of identified user equipment, and wherein sending the consent request is based on receiving the list of user equipment identified including objects.

[0178] Example 3. According to the method described in Example 1, the request to send a consent-aware object includes sending a request to a third-party application function.

[0179] Example 4. The method according to Example 3 includes receiving a response to a request for consent to perceive an object from a third-party application function before providing a response to the perception management function for a request to perceive an object.

[0180] Example 5. According to the method of Example 1, the request to send a consent-aware object based on identification information includes broadcasting the request to the consent-aware object on a broadcast channel.

[0181] Example 6. The method according to Example 5, wherein broadcasting includes broadcasting information related to the perception of the object, the information related to the perception of the object including at least one of consent type, perception area and perception service.

[0182] Example 7. The method according to Example 6 includes waiting for a predetermined time period for responding to a request from an object that is aware of consent.

[0183] Example 8. The method according to Example 7 includes receiving a response to a consent request from a user device within a predetermined time period.

[0184] Example 9. According to the method of Example 7, wherein if no response to the consent request is received from the user equipment within a predetermined time period, a response to the request for consent to perceive the object is provided to the perception management function, the response indicating that the owner of the object has not consented to the perception of the object.

[0185] Example 10. According to the method of Example 5, wherein in response to receiving a rejection of a request for consent to be perceived from a user equipment, a response to a request for consent to be perceived from an object is provided to the perception management function, the response indicating that consent to be perceived from an object has not been provided.

[0186] Example 11. The method according to Example 10, wherein in response to receiving a rejection of a request for consent to be perceived, the object is excluded from being perceived.

[0187] Example 12. According to the method of Example 7, wherein if no response to the consent request is received from the user equipment within a predetermined time period, a response to a request for consent to be perceived is provided to the perception management function, the response indicating the consent perception object.

[0188] Example 13. The method according to Example 1, wherein the response to a request for consent includes one or more conditions or constraints for the consent.

[0189] Example 14. The method according to Example 13, wherein one or more conditions or constraints include one or more of the following: indication of the allowed duration of perception, the allowed perception area or a sub-region within the perception area, the allowed perception accuracy, the allowed perception resolution, the characteristics or attributes of the object to be perceived, and the modification of specific characteristics of the object.

[0190] Example 15. A consent management entity for a communication network, comprising: at least one processor; at least one memory storing instructions, wherein the instructions are executable by the at least one processor to cause the consent management entity to perform the method according to any one of Examples 1 to 14.

[0191] Example 16. An apparatus comprising: a consent management function configured to perform a method according to any one of Examples 1 to 14.

[0192] Example 17. A consent management entity, including components for performing the method according to any one of Examples 1 to 14.

[0193] Example 18. A non-transient computer-readable medium comprising instructions stored thereon, the instructions being executable by at least one processor of a consent management entity to cause the consent management entity to perform the method according to any one of Examples 1 to 14.

[0194] Example 19. A computer program comprising instructions, wherein when executed by at least one processor of a consent management entity, the computer program causes the consent management entity to perform the method according to any one of Examples 1 to 14.

[0195] Example 20. A method performed by a perception management function of a communication network, the method comprising: receiving a perception service request, the perception service request including information related to a perception object; sending a request to a perception consent management entity for consent to perception of the object; determining, based on a response to a consent request received from the perception consent management entity, whether to initiate perception of the object; and, based on the determination that perception of the object should not be initiated, sending a response to the perception service request, the response indicating that perception of the object is not permitted.

[0196] Example 21. The method according to Example 20 includes sending a message to one or more sensing devices to initiate sensing based on determining the sensing of a starting object.

[0197] Example 22. A sensing management entity for a communication network, comprising: at least one processor; at least one memory storing instructions, wherein the instructions are executable by the at least one processor to cause the sensing management entity to perform the method according to Example 20 or Example 21.

[0198] Example 23. A perception management entity configured to perform the method described according to Example 20 or Example 21.

[0199] Example 24. An apparatus comprising: a sensing management function configured to perform the method according to Example 20 or Example 21.

[0200] Example 25. A non-transient computer-readable medium including instructions stored thereon, the instructions being executable by at least one processor of a perception management entity to cause the perception management entity to perform the method according to Example 20 or Example 21.

[0201] Example 26. A computer program comprising instructions, wherein when executed by at least one processor of a perception management entity, the computer program causes the perception management entity to perform the method according to Example 20 or Example 21.

[0202] Example 27. A method comprising: receiving a broadcast or unicast request for consent to perceive an object, the broadcast or unicast request including information relating to the perception of the object; determining, based on the perception-related information, whether the owner of the object consents to the perception of the object; in response to determining that the owner of the object consents to the perception of the object, providing a response to the broadcast or unicast request for consent, the response indicating that the owner of the object consents to the perception of the object; and in response to determining that the owner of the object does not consent to the perception of the object, providing a response to the broadcast or unicast request for consent, the response indicating that the owner of the object does not consent to the perception of the object.

[0203] Example 28. The method according to Example 27, wherein the information related to the perception of the object includes one or more of the following: the perception area, the type of the perception service, the type of the perception object, the duration of the perception service, the perception QoS information, and information about the characteristics of the perception object.

[0204] Example 29. The method according to Example 27 or Example 28, wherein the information related to the perception of the object includes a consent type indicating the type of consent to the object perception.

[0205] Example 30. The method according to Example 27, wherein instructing the owner of the object to consent to the perceived object's response includes one or more conditions or constraints on the perception.

[0206] Example 31. The method according to Example 30, wherein one or more conditions or constraints include one or more of the following: indication of the allowed duration of perception, the allowed perception area or a sub-region within the perception area, the allowed perception accuracy, the allowed perception resolution, the characteristics or attributes of the allowed object, and the modification of specific characteristics of the object.

[0207] Example 32. The method according to Example 27 includes determining the type of consent requested after receiving a broadcast or unicast request and before providing a response.

[0208] Example 33. A user equipment, comprising: at least one processor; at least one memory storing instructions, wherein the instructions are executable by the at least one processor to cause the user equipment to perform the method according to any one of Examples 27 to 32.

[0209] Example 34. A non-transient computer-readable medium comprising instructions stored thereon, the instructions being executable by at least one processor of a user equipment to cause the user equipment to perform the method according to any one of Examples 27 to 32.

[0210] Example 35. A computer program comprising instructions, wherein when executed by at least one processor of a user equipment, the computer program causes the user equipment to perform the method according to any one of Examples 27 to 32.

Claims

1. A method comprising: Receive a request from the perception management function to consent to object perception; Obtain identification information that identifies the owner of the object, or identification information that identifies the sensing area used to perceive the object; Based on the identification information, a request for consent to be aware of the object is sent to a user device associated with the owner of the object or an entity associated with the owner of the object, the consent request including information related to the perception of the object; Based on the response to the consent request received from the user equipment or the entity, the response to the consent request indicates consent to perceive the object, and the perception management function provides a response to the request to consent to perceive the object, and the response to the request to consent to perceive the object indicates consent to perceive the object.

2. The method according to claim 1, comprising: Before sending the consent-aware request, a request to discover user devices in the awareness area is sent to the network entity; In response to the request to discover a user device, a list of user devices identifying the sensing area is received, wherein the objects are included in the list of identifying user devices, and wherein the consent request is sent based on receiving the list of identifying user devices including the objects.

3. The method of claim 1, wherein sending the request to the consent-aware object includes sending the request to a third-party application function, and The method includes: Before providing the perception management function with a response to the request for consent to perceive the object, the response to the request for consent to perceive the object is received from the third-party application function.

4. The method of claim 1, wherein sending the request to consent to the object based on the identification information includes broadcasting the request to consent to the object on a broadcast channel, and The broadcast includes broadcasting information related to the perception of the object, and the information related to the perception of the object includes at least one of consent type, perception area, and perception service.

5. The method of claim 4, further comprising waiting a predetermined time period for responding to the request of the object that perceives consent. The method includes receiving a response to the consent request from the user equipment within the predetermined time period. If no response to the consent request is received from the user equipment within the predetermined time period, a response to the request for consent to perceive the object is provided to the perception management function, the response indicating that the owner of the object has not consented to perceiving the object. If no response to the consent request is received from the user equipment within the predetermined time period, a response to the request for consent to perceive the object is provided to the perception management function, the response indicating consent to perceive the object.

6. The method of claim 5, wherein in response to receiving a rejection from the user equipment of the request for consent to perceive the object, a response to the perception management function is provided to the perception management function of the request for consent to perceive the object, the response indicating that consent to perceive the object has not been provided, and In response to receiving a rejection of the request to consent to the perception of the object, the object is excluded from being perceived.

7. The method of claim 1, wherein the response to the request for consent to the perception includes one or more conditions or constraints on the perception, and The one or more of the conditions or constraints include one or more of the following: an indication of the allowed duration of perception, a allowed area of ​​perception or a sub-region within the area of ​​perception, an allowed precision of perception, an allowed resolution of perception, a feature or attribute of the object that is allowed to be perceived, or a modification of a specific feature of the object.

8. A method performed by a sensing management function of a communication network, the method comprising: Receive a sensing service request, the sensing service request including information related to the sensing object; Send a request to the perception consent management entity to consent to the perception of the object; Based on the response to the consent request received from the perception consent management entity, it is determined whether to initiate the perception of the object; as well as Based on the determination that the perception of the object will not be initiated, a response to the perception service request is sent, the response indicating that the perception of the object is not permitted, and The method includes sending a message to one or more sensing devices to initiate sensing based on determining that sensing of the object is to begin.

9. A method comprising: Receive a broadcast or unicast request for consent to perceive an object, the broadcast or unicast request including information related to the perception of the object; Based on the information related to the perception, determine whether the owner of the object consents to the perception of the object; In response to determining that the owner of the object agrees to be aware of the object, a response is provided to the broadcast or unicast request for consent, the response indicating that the owner of the object agrees to be aware of the object; In response to determining that the owner of the object does not agree with the perception of the object, a response is provided to a broadcast or unicast request for consent, the response indicating that the owner of the object does not agree with the perception of the object. The information related to the perception of the object includes one or more of the following: perception area, type of perception service, type of perception object, duration of perception service, perception QoS information, and information about the characteristics of the perception object. The information related to the perception of the object includes a consent type indicating the type of consent to the perception of the object, or The method includes determining the type of consent requested after receiving the broadcast or unicast request and before providing the response.

10. The method of claim 9, wherein instructing the owner of the object to consent to the perception of the object includes one or more conditions or constraints on the perception, and, The one or more of the conditions or constraints include one or more of the following: an indication of the allowed duration of perception, a allowed area of ​​perception or a sub-region within the area of ​​perception, an allowed precision of perception, an allowed resolution of perception, a feature or attribute of the object that is allowed to be perceived, or a modification of a specific feature of the object.

Images