TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to sensing in a wireless communication network.

BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0003] Wireless sensing technologies aim at acquiring information about a remote object or its environment and its characteristics without physically contacting it. This can be achieved by using a camera or radar. There are also investigations and solutions how communication technologies (e.g. 3GPP specified LTE or NR, but also WLAN) can be utilized for sensing.

[0004] There are also initiatives to enhance the cellular wireless communication systems, e.g. 5GS as specified by 3GPP, to also incorporate the wireless sensing. In other words, beside the traditional communication services, the wireless system can also perform a sensing task and report the result to an application, customer or vertical that is interested in the sensing result. The sensing can be also used internally in the wireless communication system to improve the network performance.

SUMMARY

[0005] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be constmed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0006] Some implementations of the method and apparatuses described herein may further include a network entity for wireless communication, comprising: at least one memory; and [0007] at least one processor coupled with the at least one memory and configured to cause the network entity to: receive a sensing request relating to a sensing task and providing a set of sensing request parameters based on the sensing task; send a sensing preparation request to one or more sensing nodes corresponding to one or more of the sensing request parameters; receive a sensing preparation response from the one or more sensing nodes; and send a sensing configuration request to a first sensing node of the one or more sensing nodes based on the sensing preparation response.

[0008] The at least one processor can be configured to cause the network entity to:

[0009] implement a central sensing function for receiving the sensing request; and [0010] implement one or more serving sensing functions for sending the sensing preparation request, receiving the sensing preparation response, and sending the sensing configuration request. [0011] The set of sensing request parameters may comprise or are derived from one or more of: a target sensing area; a sensing type; and a sensing precision level. For example, the sensing precision level may be indicated by one or more key performance indicators (KPIs).

[0012] The sensing configuration request may comprise one or more sensing configuration parameters and a reporting address being one of a control plane (CP) address and a user plane (UP) address. When the reporting address is the UP address, the at least one processor cam be further configured to cause the network entity to receive a sensing result related to the sensing task from a network node associated with the UP address. Also, when the reporting address is the UP address, the at least one processor can be further configured to cause the network entity to configure a network node associated with the UP address to report a sensing result to another network entity. For example, the sensing result may be sent to a sensing data processing server.

[0013] The at least one processor can be further configured to:

[0014] determine that a second sensing node of the one or more sensing nodes comprises a sensing capability comprising a non-wireless communication sensing type; and [0015] configure the first or second sensing node to send sensing data related to the sensing task to a sensing data processing server.

[0016] Some implementations of the method and apparatuses described herein may further include a method performed by a network entity for wireless communication, comprising: receiving a sensing request relating to a sensing task and providing a set of sensing request parameters based on the sensing task; sending a sensing preparation request to one or more sensing nodes corresponding to one or more of the sensing request parameters; receiving a sensing preparation response from the one or more sensing nodes; and sending a sensing configuration request to a first sensing node of the one or more sensing nodes based on the sensing preparation response.

[0017] The method may further comprise:

[0018] implementing a central sensing function for receiving the sensing request; and [0019] implementing one or more serving sensing functions for sending the sensing preparation request, receiving the sensing preparation response, and sending the sensing configuration request.

[0020] The set of sensing request parameters may comprise or is derived from one or more of: a target sensing area; a sensing type; and a sensing precision level (e.g. KPIs).

[0021] The sensing configuration request may comprise a reporting address being one of a control plane (CP) address and a user plane (UP) address. When the reporting address is the UP address, the method may further comprise receiving a sensing result related to the sensing task from a network node associated with the UP address. When the reporting address is the UP address, the method may further comprise configuring a network node associated with the UP address to report a sensing result to another network entity.

Thereby, the sensing node can bypass the sensing function. The other network entity may send sensing result feedback to the sensing function to indicate completion of the sensing task.

[0022] The method may further comprise: determining that a second sensing node of the one or more sensing nodes comprises a sensing capability comprising a “non-wireless communication” sensing type; and configuring the first or second sensing node to send sensing data related to the sensing task to a sensing data processing server.

[0023] Some implementations of the method and apparatuses described herein may further include a base station for wireless communication, comprising at least one memory; and [0024] at least one processor coupled with the at least one memory and configured to cause the base station to: receive a sensing preparation request related to a sensing task and comprising a set of sensing task parameters based on the sensing task; send a sensing preparation response; receive a sensing configuration request comprising a target sensing area of the sensing task; and perform the sensing task to provide sensing data.

[0025] The sensing configuration request may further comprise a reporting address being one of a control plane (CP) address and a user plane (UP) address, and the at least one processor is further configured to cause the base station to send the sensing data to the reporting address. [0026] The sensing preparation response may comprise a confidence level indicative of a probability of successfully performing the sensing task within the set of task parameters. [0027] The at least one processor can be further configured to cause the base station to: select one or more assisting sensing nodes; configure each of the one or more assisting sensing nodes to perform a sensing measurement related to the sensing task; receive measurement sensing data from the one or more assisting sensing nodes; and process the measurement sensing data to provide the sensing data.

[0028] Some implementations of the method and apparatuses described herein may further include a method performed by a base station for wireless communication, comprising: receiving a sensing preparation request related to a sensing task and comprising a set of sensing task parameters based on the sensing task; sending a sensing preparation response; receiving a sensing configuration request comprising a target sensing area of the sensing task; and performing the sensing task to provide sensing data.

[0029] The step of performing the sensing task may comprise: selecting one or more assisting sensing nodes; configuring each of the one or more assisting sensing nodes to perform a sensing measurement related to the sensing task; receiving measurement sensing data from the one or more assisting sensing nodes; and processing the measurement sensing data to provide the sensing data.

[0030] BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0032] Figure 2 illustrates a schematic diagram of a wireless communication network used for sensing;

[0033] Figure 3 illustrates a network architecture comprising a core network with a sensing function;

[0034] Figure 4 illustrates a signaling flowchart of a sensing process;

[0035] Figure 5 illustrates a network architecture comprising a core network with a sensing function and an access network with a plurality of access network nodes; [0036] Figure 6 illustrates a network architecture an access network with a non-3GPP access network node;

[0037] Figure 7 illustrates a network architecture with a reporting path in the control plane;

[0038] Figure 8 illustrates a network architecture with reporting paths in the user plane;

[0039] Figure 9 illustrates a network architecture with reporting paths in the user plane via a sensing data processing server.

[0040] Figure 10 illustrates a signaling flowchart of a sensing process;

[0041] Figure 11 illustrates an example of a user equipment (UE) 1100 in accordance with aspects of the present disclosure.

[0042] Figure 12 illustrates an example of a processor 1200 in accordance with aspects of the present disclosure.

[0043] Figure 13 illustrates an example of a network equipment (NE) 1300 in accordance with aspects of the present disclosure.

[0044] Figure 14 illustrate a flowcharts of method performed by a NE in accordance with aspects of the present disclosure.

[0045] Figure 15 illustrate a flowcharts of method performed by a NE in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0046] There can be multiple (R)AN nodes engaged with the transmission and/or reception of radio sensing signals for a single sensing task. A problem is how the SF can select the appropriate (R)AN nodes for a particular sensing task and configure such nodes to perform the sensing task. The problem can be described as follows: how to select and configure the (most) appropriate sensing node for a particular sensing task; and how the selected/configured sensing node reports the sensing data.

[0047] The present disclosure can at least partly solve these problem by a sensing preparation procedure. A network entity (e.g. configured to implement a SF) receives a sensing request relating to a sensing task and providing a set of sensing request parameters based on the sensing task. The network entity sends a sensing preparation request to one or more sensing nodes corresponding to one or more of the sensing request parameters, and receives a sensing preparation response from the one or more sensing nodes. Network entity then sends a sensing configuration request to a first sensing node (the selected sensing node) of the one or more sensing nodes based on the sensing preparation response

[0048] The disclosed solution allows for an efficient way of determining and configuring a sensing node for a particular sensing task.

[0049] Aspects of the present disclosure are described in the context of a wireless communications system.

[0050] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0051] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0052] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0053] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Intemet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0054] A UE 104 may be able to support wireless communication directly with other

UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface. [0055] An NE 102 may support communications with the CN 106, or with another NE

102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0056] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0057] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106). [0058] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0059] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., /r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., /r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., /r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., /r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., /r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0060] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration. [0061] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., /r=0, jU=l , /r=2, jU=3, /r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0062] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities. [0063] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing.

[0064] In the following text, reference is made to sensing nodes, which may be transmission sensing nodes, referred to as a sensing Tx node, or a reception sensing node, referred to a sensing Rx node. A sensing node may be both a Tx node and an Rx node at the same time. When reference is made to a sensing node, it may be a Tx node, an Rx node or a node performing both transmission and reception. Sensing nodes may be any network node, including base stations (for example a gNB), user equipments and non-3GPP sensing devices. [0065] The radio sensing procedure can be used to obtain environment information by the means of: a) Transmission of a sensing signal, e.g., a sensing RS, from a sensing node which could be an access network (AN) node like base station or UE entity. Such a sensing node (e.g. AN node or UE) can be called a sensing transmitter, e.g. sensing Tx node. b) Reception of the reflections/echoes of the transmitted sensing radio signal from the environment by one or more sensing nodes, which could be AN nodes or UEs. Such nodes can be called sensing receivers, e.g. sensing Rx node. The received sensing signals (e.g. reflections, refractions and inferring relevant information from the environment or an object) are called sensing (measurement) data. c) The received sensing data can be processed in the network, e.g. in the RAN or in a Sensing Function (SF) in the core network. Based on this processing a Sensing result can be calculated. The Sensing result can be used by the mobile network itself or can be exposed to a vertical. [0066] One example of object sensing is shown in Figure 2. A base station 201 (e.g. gNB), being a sensing node, transmits a sensing RS signal 202 and also receives the reflections 203 from an object 204, i.e. this is a Sensing Tx/Rx base station. Further, a second base station 205 (e.g. a gNB) and a UE 206 can be further sensing nodes that also receive the reflected Sensing RS 203, and therefore, they can be described as sensing receivers (Sensing Rx).

[0067] The sensing measurement data from the received sensing signal 203 from the three sensing nodes can be processed and combined to provide a sensing result.

[0068] The sensing object can be:

A passive object, e.g. an object which is not registered with the mobile network or cannot report sensing measurements to the network; or

An active object, e.g. the object is equipped with a UE which is capable of receiving the sensing RS and to report the measurement to the network.

[0069] Figure 3 shows a possible network architecture where a network entity implements a sensing function (SF) located in the Core network (CN) and can be connected to multiple other CN network functions. The network architecture 300 comprises network interfaces for sensing NS1 to NS 8 between the SF and other network function (NFs) in the Core network control plane. The architecture further comprises an Access and Mobility Management Function (AMF) connected to the a UE and to the (R)AN via N1 and N2 respectively, a Unified Data Management (UDM) connected to the AMF via the N8 interface. The AMF is connected to the SF via NS1. The SF is further connected to a Network Data Analytics Function (NWDAF), Location Management Function (LMF), Policy Control Function (PCF), Network Exposure Function (NEF) and a User Plane Function (UPF). The NEF is also connected to the PCF via the N5 interface and to an Application Function (AF) via N33. The AF may represent a sensing consumer and may send a sensing request to the SF via the NEF.

[0070] The following terms are used herein:

Sensing service: a service provided by the 3GPP system (e.g. to a 3rd party) to perform gathering of sensing data and providing a sensing result to the sensing consumer, e.g. 3rd party application function/server. The sensing service may include sensing operations, which includes the gathering of sensing measurements (e.g. in the access network), sensing measurement processing, creating the sensing data and crating the sensing result.

Sensing data (or sensing measurement data): data derived from the radio signals (e.g., reflected, refracted, diffracted) or non-radio signals (e.g. video, optical or lidar signals, etc.) impacted by a target sensing object or environment. The target sensing object or environment has been of interest for sensing purposes. The sensing data may be associated with a specific sensing task and may be optionally processed within the network or 5G system.

Sensing result: processed sensing data by the network or 5G system. The sensing result is data which can be provided to a sensing service consumer. The sensing consumer can be part of the 5GS or can be a 3rd party application functions, which has subscribed for the sensing service.

Sensing task: the sensing process/procedure resulting from a sensing request (by a sensing service consumer) for a particular target sensing area and or particular sensing object.

Sensing service area: a service area where sensing services can be provided to perform a sensing task. This includes both indoor and outdoor environments. Sensing target area: an area that needs to be sensed e.g. by obtaining dynamic characteristics of the area for a specific sensing task, which may include moving objects or static objects (e.g., cars, human, animals), from the se the impacted (e.g., reflected, refracted, diffracted) wireless signals.

Sensing group: a set of sensing nodes (e.g. sensing transmitters and sensing receivers) e.g. in a particular location for which sensing measurement data can be collected synchronously.

[0071] Figure 4 illustrates a signaling flowchart of providing a sensing service in accordance with aspects of the present disclosure.

[0072] At step S401, an application function (AF) 451 sends a sensing request to a 5G system (5GS) via the Network Exposure Function (NEF) 452. The sensing request may contain one or more of a sensing task ID (an identifier for the particular request to identify a sensing task), sensing target area, sensing object, various sensing parameters related to the sensing task and others.

[0073] At step S402, the NEF 452 forwards the sensing request to a sensing function (SF) 453. The SF 453 receives the sensing request.

[0074] At step S403, the SF 453 configures two sensing nodes being an access network (AN) node 454 (e.g. a Radio AN node) and a UE 455 to perform sensing measurements. The SF 453, (R)AN node 454 and/or the UE 455 perform the sensing task in the sensing target area 456 within the sensing services area 457 of the (R)AN node. This can be the area configured by the network operator where a sensing service is provided.

[0075] At step S404, the (R)AN node reports to the SF the sensing data, which may be identified by the sensing task ID. The SF may receive one or more sensing data and provide a sensing result.

[0076] At steps S405 and S406, the SF 453 reports to the AF 451 via the NEF 452 the sensing result, which can be identified by the sensing task ID.

[0077] The sensing operation in the core network (CN, e.g. 5GC or EPC) can be performed by a plurality of sensing functions which are distributed in the network. The network can have a network architecture for the sensing service with a hierarchical sensing function architecture (e.g. in the CN) where the sensing functionality is distributed in different NFs performing a sensing task.

[0078] Alternatively or in addition there may also be a hierarchical sensing function architecture in the (R)AN where there might be one or more sensing nodes (e.g. sensing (R)AN nodes) responsible for the sensing task.

[0079] In case of distributed SFs in the CN, in one embodiment the CN comprises a central SF (C-SF), which may receive and store sensing requests from sensing customers (e.g. an AF) and create a sensing context for the sensing request. The sensing request may be associated with a sensing task identifier and for each sensing task the C-SF may perform one or more of the following functions: discovery and selection of one or more serving SF (e.g. S-SF) functionalities which are appropriate to serve the sensing task; aggregating of sensing data (or reports, measurements) received from the configured one or more S-SF(s); creating charging data towards a charging function, e.g. CHF.

[0080] A Serving SF (S-SF, or a secondary SF) functionality may be responsible for the a) establish an association with an AN node supporting sensing and exchange one of (a) the sensing-related capabilities or other information and (b) configuration information with this AN for a specific task. For a configured sensing task the S-SF may perform the following functionality: a) discovery and selection of access network (AN or RAN) node(s) for a specific sensing task. This may include 2 phases of discovery and selection: i. sensing preparative selection of a sensing node (e.g. AN (or RAN) node): including selection of candidate sensing nodes for a sensing task and transmitting a sensing preparation request to the candidate sensing node(s) to gather feedback or input about the potential sensing quality or performance which each candidate sensing node can provide for the particular sensing task (which includes the sensing object). ii. Based on the outcome of i. (sensing preparative selection of sensing node), the SF selects one or more (primary) sensing nodes for the sensing task. b) create/update/delete of sensing task (and corresponding sensing task context) in the selected (primary) sensing node. c) changing of sensing nodes upon Object mobility; d) receiving sensing data (e.g. sensing measurement reports) and optionally processing and aggregating the received sensing data. Transmitting the aggregated sensing data further to the C-SF.

[0081] The access network (denoted as AN, or (R)AN) performing the sensing operation may be organized in hierarchical manner so that there are one or more primary sensing nodes (e.g. (R)AN nodes) for a sensing task. The primary sensing node(s) is selected by the SF (e.g. S-SF) and it is responsible for the control and coordinate the sensing operation in the access network. The primary sensing node may be responsible to select and configure the sensing transmitters and sensing receivers for a sensing task. The primary sensing node may select a secondary sensing node to assist the sensing radio operations or measurements. The secondary sensing node would report the sensing measurements to the primary sensing node. The primary sensing node may gather the radio measurements for a sensing task and create sensing data to be sent to the CN (or in some instances to a non-CN entity).

[0082] The (primary) sensing node may report the sensing data to the CN via the control plane (CP or via the user plane (UP). The SF in the CN configures the (primary) sensing node whether to report the sensing data via the CP or via the UP. The SF may configure the sensing node with the reporting address, e.g. the IP address of the destination UP sensing functions (e.g. SF-UP) which receives the sensing data.

[0083] Figure 5 shows an example architecture for a sensing architecture including both an Access Network (AN, which can be also referred as Radio Access Network, RAN) and the Core Network 501 (CN, which in case of 5G is referred as 5GC). The sensing functionality in the CN 501 may be deployed either in a single SF, or can be split in hierarchical structure of SFs which are exemplary shown as Central SF (C-SF, or alternatively can be called primary SF or other appropriate name) and Serving SF (S-SF, or alternatively can be called secondary SF or other appropriate name). For each sensing task, which may be requested by an AF, there is one C-SF responsible for the task. The C-SF may select one or more S-SFs to serve the sensing task. For example, when the sensing task includes an area which is part of the serving area of multiple S-SFs, then the C-SF can select multiple S-SFs for the same sensing task.

[0084] Figure 5 also shows an access network (AN) architecture. For example, the AN deploys AN nodes implementing 3 GPP-based radio access technologies (e.g. E-UTRA, NR, etc.), and therefore, the AN nodes are base stations called gNBl and gNB2. The gNBl is assumed to be the primary AN node for a sensing task. In particular, the gNBl is shown in distributed architecture where the central unit (CU) is connected to the 5GC via the N2 interface.

[0085] The gNBl is connected with the CN 501 via the “N2-s” interface similarly to the N2 association between an AN and AMF in the 5GS architecture. The N2-s can be used for various purposes: (a) establish an association between the AN node and the SF (that may include exchange of capabilities of the AN node); (b) exchange of configuration message for a particular sensing task; and/or (c) to transmit the sensing measurement data from the AN node to the SF. The gNBl may further include radio remote units (RRU) like RRU1 and RRU2 which are capable to transmit and receive (a) communication data and (b) sensing radio signals. The RRU1 and RRU2 report the sensing measurements for the sensing task to the gNBl.

[0086] The primary AN node (e.g. gNBl) may discover and select another AN node (e.g. gNB2) to assist the sensing operation for the same sensing task. The gNB2 is called a secondary AN node for the sensing task. The gNBl is connected to the gNB2 via the “Xus’’ interface, which may be similar to the Xn interface with the difference that the Xs interface can carry (or transport) a) configuration data for a sensing task and b) sensing measurement data. For the sensing task operation, the RRU1, RRU2 and RRU3 may be used to perform the sensing measurement. In this example, the gNBl uses RRU1 and RRU2, whereas the gNB2 uses RRU3 for the sensing operation. The RRU1 and RRU2 report the sensing measurements for the sensing task to the gNBl, whereas the RRU3 reports the sensing measurements for the sensing task to the gNB2. The gNB2 forwards the sensing measurements to the gNBl (acting as primary AN node). The gNBl may gather and process the radio measurements for the sensing task from the own RRUs and from the RRUs connected to neighbouring AN nodes. The gNBl may create sensing data for reporting to the CN 501.

[0087] In addition, the gNBl may configure UEs, which are located in the area of the sensing object and capable of the sensing functionality, to transmit or receive sensing signals. The UE is coordinated with the RRUs participating the sensing operation, whereas the coordination and control is performed by the primary gNBl . If the UEs are configured as sensing receiver, the UEs report the sensing measurement to the AN node to which the UEs are connected.

[0088] In the user plane, the gNBl can report the sensing data by using either the N3 interface (or enhanced N3 interface denoted as “N3-s”) or direct IP connectivity to a sensing UP function (e.g. sensing data processing server 502). The purpose of the sensing UP function, also called sensing data processing functionality or sensing server, is to process the sensing data created by the AN and to generate either aggregated sensing data or a sensing result. In one particular example, the sensing server 502 can be useful in case of n3GPP-S-AN node creating e.g. camera data. In such an example, the sensing server 502 may be an image or video processing server which can be configured to process the received data and, for example, identify a specific sensing object. For example, if the sensing server 502 is configured to detect the presence of human or animal in a forbidden area (the forbidden area can be the sensing target area), the AN can provide camera sensing data to the sensing server 502 and the sensing server 502 can identify when a human or animal is present in the forbidden area.

[0089] The aggregated sensing data or a sensing result can be sent either (a) to the SF in the control plane (e.g. C-SF or S-SF) or (b) directly to the sensing consumer (e.g. AF/AS) via a data connection. The sensing data processing functionality can be realized as:

1) A dedicated UPF for sensing data reception, processing and/or reporting may be located in the user plane and configured either by the SF( e.g. S-SF or C-SF) for a sensing task. Such functionality can be represented as SF-UP (sensing function user plane) and may include termination of GTP-U tunnel and processing of sensing data. The SF-UP can be connected via N3 with the AN or via N9 interface with other UPF(s) for the sensing task. The SF acts as SMF to establish a tunnel (e.g. GTP-U tunnel) between the AN node and the SF-UP. Further details are shown in Figure 8; or

2) A dedicated server in the N6-UAN which is responsible to receive and process the sensing data. Further details are shown in Figure 9.

[0090] As shown in Figure 5, The C-SF can be connected to any network function (NF), the AMF, the NEF, the charging function (CHF), Unified Data Repository (UDR), and a User Plane Function (UPF).

[0091] Figure 6 shows an example architecture similar to that of Figure 5, but where the AN is based on non-3GPP sensing technologies. A main difference to the architecture in Figure 5 is that, in the AN, non-3GPP sensing (also referred to as non- wireless communication sensing) technology is used. For example, the n3GPP-S-AN stands for a stand-alone non-3GPP Sensing Access Node and may be any node/entity which may perform sensing of the environment or object using a non-3GPP sensing technology. While both the RRU-S/TRP-S and the n3GPP-S-AN may perform sensing using non-3GPP technology, the RRU-S/TRP-S is part of a 3GPP specified base station (e.g. gNBl, and thus, the RRU-S/TRP-S is not seen by the CN 601 as a stand-alone node) and the n3GPP-S- AN is a standalone node seen as such by the CN 601.

[0092] The non-3GPP sensing technology can be a camera producing still (or single) images or a stream of video data, or a radar or lidar technology for example. The non 3 GPP access network may also have a primary n3GPP-S-AN (e.g. n3GPP-S-AN#l) and a secondary n3GPP-S-AN (e.g. n3GPP-S-AN#2), which are connected via the Xn-s interface. [0093] Similar to gNBl in Figure 5, in the user plane, the primary n3GPP-S-AN can report the sensing data to by using either the N3 interface (or enhanced N3 interface denoted as “N3-s”) or direct IP connectivity to a sensing UP function (e.g. sensing data processing server 602).

[0094] The sensing task may include the reporting of large amount of sensing (measurement) data from the (R)AN to the CN 601. Several options are described below for the reporting path of the sensing data from the AN to the CN 601 or the sensing consumer (e.g. the AF/AS).

[0095] Figure 7 illustrates a schematic reporting path 701 in the control plane. The SF in the control plane (i.e. SF-CP) may comprise the S-SF and C-SF. The “N2-s” interface between the AN node 702 and the SF-CP may be used for both (A) transmission of control plane sensing information including exchange of capabilities, creation, modification or release or configuration of a sensing task, etc. and (B) transmission of sensing data reports. The “N2-s” interface may use either a single protocol for both (A) and (B), or different protocols can be used for each (A) and (B). If the same protocol is used, then different payload types may be defined for the N2-s messages for case (A) and case (B). The different payload types would allow to apply different QoS handling of the packets over the N2-s interface. The reporting of the sensing data via the CP can be beneficial when the sensing data is not very high and/or not reported in a streaming-like manner. The AN node 702 can pre-process the sensing measurement and create sensing data which is limited in size. When the sensing data comprises a large amount of data or when the sensing data has streaming characteristics (e.g. a camera video stream), then UP transmission may be preferable.

[0096] The AN node 702 can be a base station which may be a 3 GPP access node, e.g. gNB, or a non-3GPP access node, e.g. n3GPP-S-AN. The AN node 702 transmits the sensing data to the SF-CP in the control plane. The SF-CP may further process the sensing data and provide a sensing result. The SF-CP transmits the sensing result to the sensing consumer (e.g. AF/AS) via the NEF.

[0097] Figure 8 illustrates an embodiment where sensing data is reported via the user plane, and wherein the final destination of the sensing data is the SF in the control plane (i.e. SF-CP). The “N2-s” interface is further used for transmission of control or configuration sensing information for the sensing task, e.g. including exchange of capabilities, creation, modification or release or configuration of a sensing task, etc. Similar to the embodiment of Figure 7 described above, the AN sensing node 801 may be a 3GPP access node, e.g. gNB, or a non-3GPP access node, e.g. n3GPP-S-AN. The AN sensing node is configured to transmit the sensing data to the CN 802 in one of the following paths:

[0098] (path A 803, dashed line) The N3 interface may be used to transmit (or report) the sensing data to the CN 802. Using the N3 interface for the sensing data has the advantage that existing QoS mechanisms, e.g. QoS flows, GPT-U header, can be reused. The SF (either the S-SF or C-SF) may configure a corresponding UPF to receive and forward the sensing data, i.e. to configure a PDU Session-like context in the UPF for the sensing data. However, as the user plane data is not to/from a UE, but to/from an infrastructure node (e.g. Sensing AN node 801), the existing N4 interface and the UPF may be modified. For example, the SF can act as SMF to establish a tunnel (e.g. GTP-U tunnel) between the AN node 801 and the UPF (also called SF-UP as it may be a special UPF implementing sensing functionality to process the received sensing data). Alternatively, the SF-CP can request a specific SMF (e.g. SMF-Sensing, or SMF-S) to establish a N3 and/or N9 tunnel between the AN node 801 and the UPF. For each sensing task an independent GTP-U tunnel can be established. For this purpose, the SF-CP may perform the following steps: (1) identify the AN node and the SF-UP which should be involved for the sensing task; (2) send a request message to the SF-UP (and correspondingly receive a reply from the SF-UP with the result of the request) via the N4-s interface to configure the SF-UP for the sensing task by requesting establishment of a session (or tunnel) to the AN node and including sensing task ID, AN node ID, sensing parameters (e.g. type of sensing data to be received like 3 GPP or non-3GPP sensing data, whether to process the sensing data, destination address to forward the sensing data, etc.); (3) send a request message to the AN node (and correspondingly receive a reply from the AN node with the result of the request) via the N2-s interface to configure the AN node for the sensing task by requesting establishment of a session (or tunnel) to the SF-UP node be including the parameters as described in Figure 10 step S1010. Further, the SF can act as receiver of the data received in the UPF. For this purpose, the UPF may need to be modified to forward the received sensing data to the SF (e.g. S-SF or C-SF) via the N4 interface.

[0099] (Path B 804, dash dotted line) The AN sensing node 801 is configured to transmit the sensing data over the IP infrastructure to the sensing data receiver, e.g. SF in the control plane. The AN sensing node 801 can be configured with the destination IP address (or FQDN) of the SF in the control plane. The SF-CP can be configured to receive the sensing data via the data/IP interface.

[0100] After using either Path A 803 or Path B805, after the SF-CP receives sensing data from the UPF or from the AN node 801 through direct IP connectivity, the SF-CP may provide a sensing result. The sensing result is based on the received sensing data, and the CF-CP can transmit this sensing result to the sensing consumer (not shown) via the NEF. This is shown as a double dot dash line between the SF and NEF.

[0101] Figure 9 shows another embodiment comprising a sensing data processing server 901 (also referred to as “sensing server”). The sensing server 901 may be configured to discriminate, handle and process the sensing data for each sensing task separately. For this purpose, the SF-CP may configure the sensing server for a sensing task with sensing task configuration information including one or more of: sensing task ID, a sensing object description, sensing KPIs (or more generally an indication of a sensing precision level such as a KPI), desired sensing result, and reporting address. The SF-CP can send the sensing task configuration information to the sensing server 901 when the SF-CP also configures the (R)AN node 902 for the sensing task (e.g. as described in relation to Figure 10 below). The IP packet payload, which includes the sensing data may also include a sensing task ID, so that the sensing server 901 can associate the received sensing data with the configuration context information created by the SF-CP. The following parameters may be comprised in the sensing task configuration information sent to the sensing sever:

One or more parameters describing the “desired sensing result”, which indicate what has to be detected (e.g. the sensing object description) by the sensing server 901, , a sensing target area and/or requested action like presence or no presence of an object e.g. in summary whether the sensing object is present or not present in the sensing target area. In other words, the desired sensing result may be the “sensing event” which should be determined based on the received sensing data (or measurements). The sensing event may be considered as any of: trigger for sending a sensing result and/or sensing result description.

The parameter “reporting destination address” indicates a destination entity to which the sensing server 901 should report the processed sensing data or sensing result. For example, as shown by the das double dot line, the reporting destination can be at least one of: S-SF, C-SF, NEF, AF address. o Furthermore, when the “reporting destination address” is a NEF or AF address, then the SF-CP can in addition configure the sensing server 901 to also report the sensing output (e.g. the output of the sensing result) to the SF-CP. This can be beneficial for the case that the SF-CP is configured to generate a charging report (e.g. for the particular sensing task) and keep track of the sent sensing results via the NEF and/or AF. In other words, the sensing server 901 may be configured to transmit (a) the sensing result to NEF or AF including the information about the reporting destination address and (b) a sensing report status indication to the SF-CP (e.g. C-SF). So, the sensing server needs to create 2 reporting messages: one with the sensing result sent to NEF/AF and another message with a sensing status (or sensing report status) sent to the SF-CP to keep the record of the sensing results. [0102] The following embodiments described in relation to Figure 10 provide (a) a sensing task configuration in the access network, (R)AN, and (b) a configuration for (R)AN reporting of sensing data. The (R)AN or (R)AN node can be comprised by a 3 GPP specified RAN as described in relation to Figure 5 or a non-3GPP sensing technology as described in relation to Figure 6.

[0103] Figure 10 illustrates a signaling flow chart of a method of providing a sensing service:

[0104] At step S1001, the (R)AN nodes may be configured, e.g. by the 0AM system, to activate or install features related to performing sensing of the environment and/or objects remotely. The (R)AN node registers with the core network (CN), whereby the (R)AN node informs the CN about its sensing capabilities and sensing service area.

[0105] She sensing Access Network (AN) nodes or Radio Access Network (RAN) nodes, referred as sensing (R)AN nodes (R)AN1, (R)AN2 and (R)AN3, may comprise any of the AN nodes from the Figure 5 (e.g. gNBl, gNB2) or from Figure 6 (e.g. n3GPP-S- AN). A Sensing (R)AN node is a node which has sensing functionality, for example comprising sensing measurements, coordinating of sensing measurements in other sensing nodes and/or sensing reporting.

[0106] The S-SF and C-SF may be implemented by a network entity as a single SF. The SF maintains a register of sensing nodes. For example, the SF maintains/stores an entry for each association with the (R)AN node. For each registered (R)AN node, the S-SF may store one or more of a (R)AN node ID, a sensing service area, and sensing capabilities.

[0107] At step SI 002, the sensing consumer, represented by the application function (AF), sends a sensing request to the NEF. The AF may have established an association (e.g. transport and security association) with the NEF in advance and may use this association to send the sensing request to the NEF. The sensing request may comprise one or more of: a sensing task ID (an identifier for the particular request to identify a sensing task), a sensing target area, sensing object description, sensing task KPIs (or more generally an indication of a sensing precision level), one or more sensing object parameters, and a set of sensing parameters related to the sensing task. Further details of the sensing request parameters are described in step SI 003 below, since there is an assumption that the sensing request parameters sent to the NEF are the same as the sensing request parameters received by the SF.

[0108] At step SI 003, the NEF may discover and select an appropriate SF (e.g. C-SF) to perform the sensing task. For this purpose, the NEF may request the NRF to resolve an SF for the particular sensing task, e.g. type of sensing request/task. The C-SF entities would have registered with the NRF and provided its NF type (e.g. C-SF type) and its supported sensing related capabilities (e.g. supported type of sensing request/task). The NEF may be enhanced to store an entry for each C-SF with corresponding sensing capabilities. For example, one selection criteria for C-SF can be the type of sensing task, e.g. sensing task types can be sensing of weather, or sensing of humans, animals, sensing of larger objects (e.g. house, truck, etc).

[0109] After the NEF has selected the SF, (e.g. C-SF) the NEF forwards the sensing request to the SF. For example, an existing service operation can be used or a new service operation can be introduced. In one example, for a new service, the NEF can invoke the Nsf Sensing Create service operation and include the received sensing request (if the sensing request is transmitted transparently to the NEF) and/or received sensing request parameters. The sensing request parameters may include one or more of: sensing task ID: the identifier of the sensing task. This identifier can be external identifier, e.g. used for the communication with external Afs; or an internal identifier, e.g. used to refer to the unique sensing task internally in the network (e.g. 5GS). sensing target area: the area where the sensing has to be performed as described earlier in this disclosure. The sensing target area can be represented in geographical coordinates. sensing task KPIs: these are the key performance indi ctors of the particular sensing task, which can indicate a sensing precision level for example, and may comprise at least one of: o A confidence level [%]: describes the percentage of all the possible measured sensing results that can be expected to include the true sensing result considering the accuracy. An accuracy of positioning estimate by sensing (for a target confidence level, e.g. Horizontal [m] or Vertical [m]): describes the closeness of the measured sensing result (i.e. position) of the target object to its true position value. It can be further derived into a horizontal sensing accuracy - referring to the sensing result error in a 2D reference or horizontal plane, and into a vertical sensing accuracy - referring to the sensing result error on the vertical axis or altitude. An accuracy of velocity estimate by sensing (for a target confidence level) describes the closeness of the measured sensing result (i.e. velocity) of the target object’s velocity to its true velocity. A sensing resolution: describes the minimum difference in the measured magnitude of target objects (e.g. range, velocity) to be allowed to detect objects in different magnitude. A maximum sensing service latency [ms] : time elapsed between the event triggering the determination of the sensing result (e.g. in the AN or in the CN) and the availability of the sensing result at the sensing system interface (e.g. at the exposure interface to the AF). A refreshing rate [s]: the rate at which the sensing result is generated by the sensing system. It is the inverse of the time elapsed between two successive sensing results. The refreshing rate parameter applies to the transmission of the sensing result, whereas the rate of sending the sensing data from the AN to the CN (e.g. step SI 016 in Figure 10) may be different, e.g. more frequent. A missed detection probability [%]: denotes the ratio of missing event to acquire a sensing result over all events during any predetermined period when the 5G system attempts to acquire a sensing result. It applies only to binary sensing results. A false alarm probability [%]: denotes the ratio of detecting an event that does not represent the characteristics of a target object or environment over all events during any predetermined period, when attempting to acquire a sensing result. It may only be applicable to binary sensing results. o A sensing type, such as 3 GPP sensing, non-3GPP sensing, radar based sensing, lidar based sensing, video based sensing, image based sensing, etc. o As well as further parameters. a sensing object description, which may comprise: o An object description by words like ‘human’ or ‘car”; or the size (e.g. in meters) and shape of the object. o A radio-related description, e.g. using the radio cross section (RCS) of the object.

[0110] The sensing request from the AF can contain object description in terms of words and/or size/shape, and the SF can be configured to translate this description to a radio-related description (RCS). The SF may use a database with the data of how various objects described by words or size/shape map to the expected RCS.

[0111] When the AF decides to update or release an already existing sensing task, the service operation towards the SF can be Nsj Sensing Update Delete correspondingly.

[0112] The C-SF may verify whether the sensing request is allowed by performing an authorization with e.g. sensing service subscription data, which may be located in the UDR. [0113] The C-SF may discover and select one or more serving SFs (e.g. S-SFs) to serve the sensing task. The criteria for selection of S-SFs can be based on the sensing capabilities of the S-SFs and may comprise sensing service area and sensing type. For example, when the sensing task includes a sensing target area, the C-SF considers the sensing service area of the available S-SFs, and the C-SF selects such S-SF(s) which at least partly cover the sensing target area. For this purpose, the C-SF may use the NRF services, wherein the S- SFs have registered in advanced with the NRF and provided their sensing capabilities.

[0114] Once one or more S-SFs are selected, the C-SF can transmit a request message to the S-SF to create an association for the sensing task. For example, the C-SF may use the service operation Nsj Sensing Create and include one or more of the sensing task ID, the sensing target area, sensing object description, and other sensing parameters as described above in relation to the sensing request message received by the C-SF.

[0115] At step SI 004, the C-SF and S-SF(s) can provide a sensing context related to the sensing task. For example, the sensing context may include at least one of: a sensing task ID, a sensing target area, one or more sensing task KPIs, a description of the sensing object, asensing result report configuration (e.g. reporting when an event happens, or report periodically), a reporting address (e.g., address of a sensing application server).

[0116] The C-SF may be configured to gather and report sensing charging data for the sensing function to the CHF. The charging data may be based on (a) the created and transmitted sensing results and/or (b) the time duration for the sensing task.

[0117] At step SI 005, the SF (e.g. C-SF) may respond to the AF via the NEF with a confirmation of the sensing request. For example, the C-SF may invoke a

Ns Sensing Create reply service operation including the sensing task ID (as reference ID) and confirmation of the sensing request operation, i.e. whether the sensing request has been accepted (e.g. indicate ‘success’), or whether the sensing has been rejected (e.g. indicate ‘failure’) to the AF.

[0118] In case of failure, the SF may indicate the reason for failure. For example, the SF can be configured to determine that the sensing request as failed if one or more sensing request parameters of the sensing request cannot be met (e.g. if the sensing KPIs cannot be fulfilled, or if the requested sensing accuracy cannot be achieved).

[0119] Similarly, if the AF has requested a modification or deletion of a sensing task in step SI 002, the C-SF replies with the result of the modification or deletion of a sensing task, e.g. by using a NsJ Sensing Update Delete reply service operation.

[0120] At step SI 006, the method comprises preparation messaging for determining an appropriate sensing node. Step SI 006 comprises steps SI 007 and SI 008.

[0121] At step SI 007 the SF (e.g. S-SF) sends sensing preparation requests to the sensing AN nodes. The sensing preparation requests are used to query the (R)AN nodes about the possibility to perform the specific sensing task.

[0122] The S-SF may be configured to first discover one or more candidate sensing nodes, which may be considered to potentially serve the sensing task. The S-SF can then send the sensing preparation request to the one or more candidate sensing nodes. The S-SF may select the candidate sensing nodes based on the stored sensing parameters (e.g. related to the sensing capabilities) for each registered sensing node. For example, the S-SF may consider a (R)AN node’s sensing service area (and/or location) and the (R)AN node’s other sensing capabilities. A sensing node’s sensing capabilities may comprise at least one of: if the node supports operation as primary sensing node or as secondary sensing node, only sensing signal transmission (Tx-only) support, only sensing signal reception (Rx-only) support, or duplex sensing signal transmission and reception (Tx+Rx) support, support of non-3GPP sensing capability and/or 3GPP sensing, supported sensing accuracy or sensing resolution, supported one or more sensing groups, etc.

[0123] In one example, the SF may compare the received target sensing area to the sensing nodes’ sensing service areas. Based on the comparison, the SF may determine which sensing nodes are selected as candidate sensing nodes.

[0124] The S-SF sends a Sensing Preparation request to each of the candidate sensing (R)AN nodes. The Sensing Preparation request can be encapsulated in NGAP message (e.g. as a payload container), or a new NGAP message can be used, or a new protocol between the SF and the sensing (R)AN node can be used. The Sensing Preparation request may include sensing task parameters which may comprise at least one of: a sensing task ID, a sensing target area, one or more sensing task KPIs, a sensing object description. The sensing task preparation KPIs may be derived from the requested sensing task KPIs received in step SI 003, i.e. the sensing task preparation KPIs may be different from the requested sensing task KPIs. For example, the sensing task preparation KPIs may not contain the ‘Max sensing service latency’ or ‘False alarm probability’, but instead may contain other parameters like 'available bandwidth for sensing’ or ‘frequency band for sensing’ etc.

[0125] As shown in Figure 10, the S-SF may determine that the candidate sensing nodes are (R)AN1, (R)AN2 and (R)AN3, and send the sensing preparation request to those candidate sensing nodes. [0126] Alternatively, the S-SF may use the NRF services to discover candidate sensing nodes, if the sensing nodes has registered its static or semi-static sensing capabilities with the NRF and the S-SF is configured to use the NRF for candidate sensing node discovery. [0127] At step SI 008, the (R)AN nodes reply to the S-SF by sending a sensing preparation response. The response may comprise at least one of a (R)AN node ID, a sensing task ID, a result of the request. For example, the result of the request may include the confidence level by which the sensing task preparation KPIs may be fulfilled, or whether the sensing target area can be covered with the requested sensing accuracy. Before sending the response, the sensing (R)AN nodes can perform an internal evaluation whether the sensing task can be performed and whether the sensing task parameters (e.g. sensing KPIs) can be fulfilled.

[0128] Steps SI 009 to SI 013 illustrate a process of sensing node selection and sensing node configuration for the sensing task.

[0129] At step SI 009, the SF (e.g. the S-SFs) performs sensing node selection. Based on the sensing preparation request response received in step SI 008, the SF selects one or more primary/serving sensing (R)AN nodes for the sensing task. Selecting a single primary sensing (R)AN node can have the benefit of maintaining a single N2-s association for a sensing task. However, if the SF can use 3 GPP sensing RAT and non-3GPP sensing sources, then the SF may configure a primary sensing (R)AN node for the 3 GPP RAT and one or more additional N3GPP-S-AN nodes.

[0130] In addition, the S-SF may also consider UEs for assisting the sensing task, the S-SF may consider to select UEs which are in the coverage of the selected primary (R)AN node (i.e. the selected primary (R)AN node is theUE’s serving gNB).

[0131] As shown in Figure 10, the S-SF may determine that (R)AN1 node is the primary sensing (R)AN node for the sensing task.

[0132] At step S1010, the SF (e.g. S-SF) sends to the selected primary sensing (R)AN node (e.g. (R)AN1 node) a sensing configuration. The SF may send the sensing configuration to initiate a sensing operation for the sensing task. For example, the S-SF may transmit an NG-AP message including a Sensing Configuration reate/Update request message. The Sensing Configuration Create/Update request message may comprise at least one of: a sensing task ID, a sensing target area, one or more sensing task configuration KPIs, a sensing object description, an indication of CP or UP reporting, a UP reporting IP address, a reporting mode (including reporting event), one or more candidate assisting sensing nodes.

[0133] The sensing target area, the sensing task configuration KPIs, and sensing object description can comprise the same parameters as those received in step SI 003, but may be also different. In one example the sensing task configuration KPIs may be derived from the requested sensing task KPIs from step SI 003, for example the SF may request the AN to send sensing data with periodicity less than the ‘refreshing rate’ for the sensing result. The sensing object description can be expressed in word description or in size/shape description form; or as radio-related description (e.g. RCS). If the sensing object description is expressed as object description shape, then the sensing (R)AN node can translate the object description shape to a radio-related description (RCS).

[0134] The parameters for CP/UP reporting and UP reporting IP address can be used as follows: The SF (e.g. S-SF) may configure the how the primary sensing node sends/reports the sensing data (e.g. to the CN). The CP/UP reporting parameter indicates whether the sensing node transmits the sending data via the CP or via the UP. When the sensing data is transmitted over the CP, the primary sensing node can use the same transport association as the one used for transmission of the sensing configuration data as described in relation to Figure 7 above. This parameter can be created in the S-SF. The S-SF may determine UP or CP reporting based on the type of the expected sensing data, e.g. if a (R)AN node creates video data (or other non- wireless communication data), then the S-SF may select a UP reporting path with a UP reporting address, e.g. being a video server or other sensing data processing server suitable for the type of sensing data.

[0135] A reporting mode parameter may indicate whether the (R)AN node has to send the sensing data/measurements periodically (e.g. based on a reporting timer, e.g. every minute) or based on an event (e.g. when the sensing measurement and processing has detected a specified sensing event). For the event-based reporting, the SF-CP may also indicate to the sensing node a parameter reporting event which describes the event which may trigger the transmission of the sensing data to the SF-CP. For example, the reporting event can be the detection of presence or (no-presence) of a sensing object (e.g. human or car) in the sensing target area.

[0136] The parameter for candidate assisting sensing nodes may be included when the SF-CP has identified other (e.g. secondary) sensing nodes which may assist the wireless sensing measurements for the sensing task. In one example, the SF-CP can include the (R)AN3 node ID as candidate assisting (R)AN nodes. The candidate assisting (R)AN nodes are identified based on the information received in step SI 008.

[0137] The S-SF derives the above parameters also considering the (R)AN node capability and the expected sensing data amount and the sensing data type.

[0138] The S-SF may delete a sensing task by sending a delete request message, such as a Sensing Configuration Delete request message, to the sensing (R)AN node.

[0139] At step SI 011, the primary sensing (R)AN node receives the sensing request for the sensing task and may determine which RRUs (or TRPs) can be configured to perform the the wireless sensing measurement for the sensing task. For example, as described in relation to Figure 5 above, the primary sensing (R)AN node can determine to use the RRU1, RRU2 for the sensing measurements.

[0140] The primary (R)AN node can discover by internal configuration and processing one or more secondary (R)AN nodes to assist the measurements for the sensing task. Alternatively, the primary (R)AN node can use the received candidate assisting (R)AN nodes information from step SI 010. After selecting the secondary (R)AN nodes, the primary (R)AN node can send a request to the secondary (R)AN nodes with configuration information for the sensing task by using the same or derived information as received in step S1010. For example, the primary sensing (R)AN node can use Xn-like interface to send a sensing request to the (R)AN3 (e.g. gNB2 from the Figure 4) to ask for assistance for the wireless sensing measurement for the sensing task. The (R)AN1 may send a sensing request to the (R)AN3 including one or more of the sensing task ID, transmission beam information (e.g. assuming that RRU1 or RRU2 will be the sensing transmitter), and the transmission or reception (Rx/Tx) role for (R)AN2 node.

[0141] A secondary sensing node can be configured to determine a particular RRU for performing a sensing measurement of the sensing task and may configure that RRU for the sensing task. For example, the (R)AN3 (e.g. gNB2) determines that RRU3 can be used for the sensing task and configures the RRU3 for the sensing task.

[0142] There might be multiple exchanges between the (R)AN1 and (R)AN3 nodes for the configuration of sensing task. There are several options of how the (R)AN3 node can be configured to report the sensing measurements data or the sensing data:

Indirect reporting path: the (R)AN1 node may configure (R)AN3 node to report the sensing measurements or data to the (R)AN1 node. The (R)AN1 node processes the sensing data and sends it to the CN (e.g. via UP or CP).

Direct reporting path: the (R)AN1 node may configure (R)AN3 node to report the sensing measurements or data to the CN directly. In such case, the (R)AN1 node may configure (R)AN3 node with the CP/UP reporting and UP reporting IP address as described in step SI 010.

[0143] The sensing nodes can configure one or more UEs connected to the sensing nodes to perform sensing measurements related to the sensing task. For example, when the (R)AN1 or (R)AN3 nodes select UEs to assist the sensing measurements (e.g. UEs with static or semi-static location), the selected UEs are not known to the CN (e.g. SF). It is the (R)AN1 or (R)AN3 nodes responsibility to select UEs and to configure and reconfigure the UEs for assisting the sensing task.

[0144] At step SI 012, the primary sensing node sends a sensing configuration response to the SF. For example, the (R)AN1 node informs the S-SF about the result of the sensing task configuration in the AN. For example, the (R)AN1 node sends N2-s message (e.g. NGAP message), which may comprise a Sensing Configuration reply. The sensing configuration response may comprise a least the sensing task ID and a configuration result indication. The configuration result indication may comprise the sensing task configuration outcome in the AN and can indicate one of: success, failure, feedback about the configured/established sensing task accuracy, feedback about alternative sensing task KPIs (i.e. different from the sensing task configuration KPIs as per step SI 010) which can be fulfilled. The sensing accuracy may be changed/modified compared to the request in step S1010. The S-SF receives the sensing configuration response from the primary sensing node. [0145] The (R)AN1 or (R)AN3 nodes may also consider to preferably configure fixed UEs to assist the sensing measurements. For example, such UEs may be UEs mounted on houses (e.g. roofs or walls) for fixed-wireless access communication, or in other words such UEs do not change their location and may deliver more reliable sensing measurements. If such UEs however become unavailable after some time (e.g. switched off), or new UEs become available, this may result in changed accuracy/precision of the sensing measurement for the sensing task, and then the AN node may adapt or modify the ‘sensing task configuration KPIs’. The AN node may send a notification to the SF at any later point in order to notify the SF that the configured KPIs for the sensing task has changed, e.g. the sensing confidence may be reduced or increased.

[0146] At step SI 013, the S-SF may send to the C-SF the sensing configuration response from the AN. The S-SF may also store the sensing task configuration result indication as received in step SI 012.

[0147] The SF-CP may also send an indication to the AF about the sensing configuration response and a preliminary sensing task accuracy or with which the KPIs of the sensing task can be fulfilled. The information exposed from the SF-CP to the AF may be the same as received in step SI 012, or may be derived from the information received in step SI 012 (i.e. derived from the sensing configuration response). In one example, the sensing configuration response may contain alternative configured KPIs for the sensing task, wherein the alternative configured KPIs can be derived from the alternative sensing task KPIs received in step SI 012.

[0148] The S-SF can send to the C-SF (as a response in step SI 003 or SI 004) a sensing configuration response message containing the sensing task ID and the preliminary accuracy, i.e. the accuracy of the intended sensing measurements.

[0149] The SF can maintain context for the sensing task, wherein the context may include an association with the AF (and the corresponding the parameters received from the sensing request ins step SI 003) and an association with the serving sensing AN node (e.g. (R)AN1 node including the corresponding parameters received in the sensing configuration reply message ins step S1012). If the SF is implemented as a S-SF and C-SF, then the C-SF maintains the association with the AF and with the selected S-SF, whereas the S-SF maintains the association with the serving sensing AN node and an association with the C- SF. Due to changing location of the sensing object or changing radio conditions, it is possible that the serving AN sensing node may change. In such case, the SF needs to update the sensing task context and update the association with the new serving AN sensing node. [0150] After completing step SI 013, the configuration of the (R)AN for performing the sensing task is completed.

[0151] From step S1014 onwards, an example of how the R(AN) gathers the wireless sensing measurement for the sensing task and how the (R)AN node reports the sensing data (or measurements) to the CN and further to the AF is illustrated.

[0152] At step SI 014, the (R)AN nodes start performing wireless sensing measurement related to the sensing task. The wireless sensing measurement may comprise measurements performed by the (R)AN node itself, by secondary (R)AN nodes, and/or sensing measurement from one or more UEs. The (R)AN nodes may also configure one or more UEs to perform or assist the sensing measurement, e.g. the UE may report radio measurements to the UE’s serving (R)AN nodes. For example, the sensing measurements form the UE may be reported as RRC signalling to the (R)AN node.

[0153] The UE may or may not be configured for sensing measurements for a specific sensing task. In other words, the UE may perform and report sensing measurements to the serving (R)AN node in general, and the serving (R)AN node can separate whether the sensing measurements are related with one sensing task or with another sensing task. For example, the UE may be configured to report the measurements for reflections for two different radio beams. Whether a first radio beam is associated with a first sensing task and a second radio beam is associated with a second sensing task may be known at the (R)AN node but not at the UE .

[0154] At step SI 015, when a (R)AN node is configured as secondary sensing node, then that (R)AN node may (A) report the sensing measurements to the primary sensing node, or (B) provide sensing data and send it to the CN. For example, in case of (A) the (R)AN3 node can utilize the Xn-s interface to report the sensing measurement data to the primary (R)AN 1 node. The signalling message containing such sensing data/measurement can be associated with the task ID, so that the primary sensing node can gather the sensing measurements from other sensing nodes and from UEs which are directly connected to the primary sensing node. In case of (B), the (R)AN3 node may be configured with a reporting UP address for the sensing data.

[0155] At step SI 016, the primary sensing (R)AN node may gather multiple wireless sensing measurements and process them locally. After processing, the primary sensing (R)AN node may create a sensing report for the sensing task, he primary sensing (R)AN node can transmit the sensing report to the CN via the UP or CP as configured in step SI 010. In this embodiment, the sensing report is sent via the CP. The alternative method of reporting via the UP is described in relation to Figure 8 and Figure 9 above.

[0156] The primary sensing (R)AN1 node may use the NGAP protocol towards the SF in the CN and encapsulate the sensing data (or sensing report) as a container or payload in the NGAP protocol. The sensing report may contain at least one of Task ID, sensing data/report (e.g. sensing result, confidence, etc. based on the processed sensing measurements, or pre-processed sensing measurements).

[0157] In one example, if the sensing (R)AN node is non-3GPP, e.g. a video camera, the sensing data can be a single image, a stream of images or video data which are not processed in the (R)AN node. Such sensing data can then be transmitted e.g. via the UP to the CN and the CN processes the sensing data as described in relation to Figure 8 and Figure 9 above.

[0158] The sensing (R)AN node may transmit the sensing either periodically (e.g. based in reporting timer like each minute or so) or based on event (e.g. the even being when the sensing measurement and processing has detected a specified sensing event as per step S1010) according to the configuration in step S1010.

[0159] At step SI 017, the SF (e.g. one or more S-SFs) receive the sensing data associated with a sensing task ID and may apply sensing data processing, e.g. if the sensing data is not processed. If there are more than one S-SFs involved for a sensing task, then the provided sensing result may be a partial sensing result, which indicates that the result may need to be further processing in the C-SF. Alternatively, the S-SF may be the only S-SF assigned to the sensing task, and may then generate a full sensing result. [0160] At step S1018, the S-SF1 sends to the C-SF sensing data. The sensing data may further include or be sent together with a sensing task ID, a sensing result (e.g. a full sensing result or partial sensing result), an indication of the sensing area where the sensing measurement data was gathered, a sensing accuracy, and other parameters. The sensing accuracy may indicate the reliability of the sensing result.

[0161] For example, the S-SF1 may invoke the service operation Nsf Sensing ^Notify report containing the sensing data.

[0162] When the S-SF2 is also configured to perform the sensing task, the S-SF2 also sends sensing data reports to the C-SF.

[0163] At step SI 019, the NEF sends to the AF the result (or sensing data report) received from the SF (e.g. C-SF). For example, the NEF can invoke the service operation Nnef Sense Report including the sensing task ID and the sensing data report (sensing task ID, sensing result, area, etc.).

[0164] A benefit of the illustrated method in Figure 10 is that the SF in the CN can select a serving (e.g. primary) sensing node from plurality of sensing nodes, which can best serve a sensing task. After the selection of the appropriate sensing node, the SF (e.g. S-SF) can configure the selected sensing node with the sensing task and with parameters for the sensing operation like the reporting path (e.g. UP or CP), reporting mode and other parameters, wherein such parameters are based on the sensing nodes capabilities (comprising for example the type of sensing data).

[0165] Another potential benefit of configuring a primary (R)AN node is (a) to “hide” the radio specific sensing measurement and the radio network topology from the SF in the CN; and (b) to have a single N2-s association between the CN and AN for a sensing task. For the sensing data reporting, there is flexibility wherein multiple (R)AN nodes may report the sensing data to the CN.

[0166] Figure 11 illustrates an example of a UE 1100 in accordance with aspects of the present disclosure. The UE 1100 may include a processor 1102, a memory 1104, a controller 1106, and a transceiver 1108. The processor 1102, the memory 1104, the controller 1106, or the transceiver 1108, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0167] The processor 1102, the memory 1104, the controller 1106, or the transceiver

1108, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0168] The processor 1102 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1102 may be configured to operate the memory 1104. In some other implementations, the memory 1104 may be integrated into the processor 1102. The processor 1102 may be configured to execute computer-readable instructions stored in the memory 1104 to cause the UE 1100 to perform various functions of the present disclosure.

[0169] The memory 1104 may include volatile or non-volatile memory. The memory 1104 may store computer-readable, computer-executable code including instructions when executed by the processor 1102 cause the UE 1100 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1104 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0170] In some implementations, the processor 1102 and the memory 1104 coupled with the processor 1102 may be configured to cause the UE 1100 to perform one or more of the functions described herein (e.g., executing, by the processor 1102, instructions stored in the memory 1104). For example, the processor 1102 may support wireless communication at the UE 1100 in accordance with examples as disclosed herein. The UE 1100 may be configured to support a means for performing a sensing measurement. In particular, the UE may receive a sensing measurement request from a sensing node being a (R)AN node and in response transmit and/or receive a sensing signal. When the UE receives a sensing signal it can be configured to report sensing data to the (R)AN node. The sensing data may be the received sensing signal or may be data obtained by processing the received sensing signal.

[0171] The controller 1106 may manage input and output signals for the UE 1100. The controller 1106 may also manage peripherals not integrated into the UE 1100. In some implementations, the controller 1106 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1106 may be implemented as part of the processor 1102.

[0172] In some implementations, the UE 1100 may include at least one transceiver 1108. In some other implementations, the UE 1100 may have more than one transceiver 1108. The transceiver 1108 may represent a wireless transceiver. The transceiver 1108 may include one or more receiver chains 1110, one or more transmitter chains 1112, or a combination thereof.

[0173] A receiver chain 1110 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1110 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1110 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1110 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1110 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0174] A transmitter chain 1112 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1112 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1112 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1112 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0175] Figure 12 illustrates an example of a processor 1200 in accordance with aspects of the present disclosure. The processor 1200 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 1200 may include a controller 1202 configured to perform various operations in accordance with examples as described herein. The processor 1200 may optionally include at least one memory 1204, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 1200 may optionally include one or more arithmetic-logic units (ALUs) 1206. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0176] The processor 1200 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1200) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0177] The controller 1202 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1200 to cause the processor 1200 to support various operations in accordance with examples as described herein. For example, the controller 1202 may operate as a control unit of the processor 1200, generating control signals that manage the operation of various components of the processor 1200. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0178] The controller 1202 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1204 and determine subsequent instruct! on(s) to be executed to cause the processor 1200 to support various operations in accordance with examples as described herein. The controller 1202 may be configured to track memory address of instructions associated with the memory 1204. The controller 1202 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 1202 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1200 to cause the processor 1200 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 1202 may be configured to manage flow of data within the processor 1200. The controller 1202 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1200.

[0179] The memory 1204 may include one or more caches (e.g., memory local to or included in the processor 1200 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 1204 may reside within or on a processor chipset (e.g., local to the processor 1200). In some other implementations, the memory 1204 may reside external to the processor chipset (e.g., remote to the processor 1200).

[0180] The memory 1204 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1200, cause the processor 1200 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 1202 and/or the processor 1200 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the processor 1200 to perform various functions. For example, the processor 1200 and/or the controller 1202 may be coupled with or to the memory 1204, the processor 1200, the controller 1202, and the memory 1204 may be configured to perform various functions described herein. In some examples, the processor 1200 may include multiple processors and the memory 1204 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0181] The one or more ALUs 1206 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 1206 may reside within or on a processor chipset (e.g., the processor 1200). In some other implementations, the one or more ALUs 1206 may reside external to the processor chipset (e.g., the processor 1200). One or more ALUs 1206 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 1206 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 1206 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1206 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 1206 to handle conditional operations, comparisons, and bitwise operations. The processor 1200 may support wireless communication in accordance with examples as disclosed herein. The processor 1200 may be configured to or operable to support a means for obtaining a sensing request relating to a sensing task and providing a set of sensing request parameters based on the sensing task, providing a sensing preparation request to one or more sensing nodes corresponding to one or more of the sensing request parameters, obtaining a sensing preparation response from the one or more sensing nodes, and providing a sensing configuration request to a first sensing node of the one or more sensing nodes based on the sensing preparation response. [0182] In another embodiment, the processor 800 is comprised by a base station and may be configured to or operable to support means for obtaining a sensing preparation request related to a sensing task and comprising a set of sensing task parameters based on the sensing task, providing a sensing preparation response,

[0183] obtaining a sensing configuration request comprising a target sensing area of the sensing task, and processing the sensing task to provide sensing data.

[0184] Figure 13 illustrates an example of a NE 1300 in accordance with aspects of the present disclosure. The NE 1300 may include a processor 1302, a memory 1304, a controller 1306, and a transceiver 1308. The processor 1302, the memory 1304, the controller 1306, or the transceiver 1308, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0185] The processor 1302, the memory 1304, the controller 1306, or the transceiver 1308, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0186] The processor 1302 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1302 may be configured to operate the memory 1304. In some other implementations, the memory 1304 may be integrated into the processor 1302. The processor 1302 may be configured to execute computer-readable instructions stored in the memory 1304 to cause the NE 1300 to perform various functions of the present disclosure.

[0187] The memory 1304 may include volatile or non-volatile memory. The memory 1304 may store computer-readable, computer-executable code including instructions when executed by the processor 1302 cause the NE 1300 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1304 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0188] In some implementations, the processor 1302 and the memory 1304 coupled with the processor 1302 may be configured to cause the NE 1300 to perform one or more of the functions described herein (e.g., executing, by the processor 1302, instructions stored in the memory 1304). For example, the processor 1302 may support wireless communication at the NE 1300 in accordance with examples as disclosed herein. The NE 1300 may be configured to support a means for receiving a sensing request relating to a sensing task and providing a set of sensing request parameters based on the sensing task, sending a sensing preparation request to one or more sensing nodes corresponding to one or more of the sensing request parameters, receiving a sensing preparation response from the one or more sensing nodes, and sending a sensing configuration request to a first sensing node of the one or more sensing nodes based on the sensing preparation response. The NE 900 may be configured to implement a sensing function (SF) which may comprise a central sensing function (C-SF) and one or more serving sensing functions (S-SFs). The SF may be comprised by a CN.

[0189] In another embodiment the NE 900 is a sensing node being a base station, wherein the NE 900 may be configured to support a means for receiving a sensing preparation request related to a sensing task and comprising a set of sensing task parameters based on the sensing task, sending a sensing preparation response, receiving a sensing configuration request comprising a target sensing area of the sensing task, and performing the sensing task to provide sensing data

[0190] The controller 1306 may manage input and output signals for the NE 1300. The controller 1306 may also manage peripherals not integrated into the NE 1300. In some implementations, the controller 1306 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1306 may be implemented as part of the processor 1302.

[0191] In some implementations, the NE 1300 may include at least one transceiver 1308. In some other implementations, the NE 1300 may have more than one transceiver 1308. The transceiver 1308 may represent a wireless transceiver. The transceiver 1308 may include one or more receiver chains 1310, one or more transmitter chains 1312, or a combination thereof.

[0192] A receiver chain 1310 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1310 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1310 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1310 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 1310 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0193] A transmitter chain 1312 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1312 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1312 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 1312 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0194] Figure 14 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0195] At 1402, the method may include receiving a sensing request relating to a sensing task and providing a set of sensing request parameters based on the sensing task. The operations of 1402may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a NE as described with reference to Figure 13.

[0196] At 1404, the method may include sending a sensing preparation request to one or more sensing nodes corresponding to one or more of the sensing request parameters. The operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a NE as described with reference to Figure 13.

[0197] At 1406, the method may include receiving a sensing preparation response from the one or more sensing nodes .The operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1406 may be performed by a NE as described with reference to Figure 13.

[0198] At 1408, the method may sending a sensing configuration request to a first sensing node of the one or more sensing nodes based on the sensing preparation response. The operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1406 may be performed by a NE as described with reference to Figure 13.

[0199] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0200] Figure 15 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions. [0201] At 1502, the method may include receiving a sensing preparation request related to a sensing task and comprising a set of sensing task parameters based on the sensing task. The operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a NE as described with reference to Figure 13.

[0202] At 1504, the method may include sending a sensing preparation response. The operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a NE as described with reference to Figure 13.

[0203] At 1506, the method may include receiving a sensing configuration request comprising a target sensing area of the sensing task. The operations of 1506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1506 may be performed by a NE as described with reference to Figure 13.

[0204] At 1508, the method may include performing the sensing task to provide sensing data. The operations of 1508 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1508 may be performed by a NE as described with reference to Figure 13.

[0205] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0206] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.