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 (e.g. optical camera, thermal camera or night vision camera) or radar alike sensing. 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 (or other sensing consumer) that is interested in the sensing result. The sensing can be also used internally in the wireless communication system (i.e., in the control or management plane) 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 at least one processor coupled with the at least one memory and configured to cause the network entity to: receive registration requests from sensing nodes in a wireless communication network, wherein the registration requests comprise an indication of sensing capability comprising a sensing service area of the sensing node; maintain one or more registers of sensing nodes and their respective sensing capabilities; send a registration response indicating a result of the registration request. The network entity is thereby configured establishes a direct association with the sensing node. The result may be one of positive, negative or a redirection to another network entity.

[0007] The at least one processor can be further configured to cause the network entity to: receive a sensing request related to sensing in a target sensing area; configure one or more sensing nodes on the one or more registers to perform a sensing task, wherein each of the one or more sensing nodes comprises a sensing service area at least partly overlapping the target sensing area; receive and process sensing data related to the sensing task from the one or more sensing nodes to provide a sensing result; and send the sensing result to another network entity. For example, the network entity can send the sensing result to an application function (AF) of the sensing consumer.

[0008] The at least one processor can be configured to cause the network entity to: implement a central sensing function for receiving the sensing request; and implement one or more serving sensing functions for receiving the registration messages and maintaining the one or more registers of sensing nodes.

[0009] The or each serving sensing function can be configured to maintain a respective register of the one or more registers, and to configure one or more sensing nodes in the respective register to perform the sensing task.

[0010] The or each serving sensing function can be configured to send a registration request to a network repository function, wherein the registration request comprises an indication of a sensing capability of the serving sensing function.

[0011] The central sensing function can be configured to, in response to receiving the sensing request, to select one or more serving sensing functions by one of:

[0012] a) querying the repository network function and select one or more serving sensing functions for the sensing task based on the registered sensing capabilities of the one or more serving sensing functions; and

[0013] b) maintaining a local configuration with the serving sensing functions associated with sensing capabilities.

[0014] A first serving sensing function of the one or more serving sensing functions can be configured to: receive a sensing configuration update from a first sensing node in the register of sensing nodes of the first serving sensing function; and determine that the first sensing node has left a sensing registration area; and send a sensing configuration reply comprising a target serving sensing ID.

[0015] The at least one processor can be further configured to cause the network entity to send a configuration update request to the sensing node, wherein the configuration update request comprises one or more of a target serving sensing function address, an indication of sensing task modification, and an indication of sensing task completion. For example, the configuration update request may be a redirection request. [0016] Some implementations of the method and apparatuses described herein may further include a method performed by a network entity, the method comprising receiving a registration request from a sensing node in a wireless communication network, wherein the registration request comprises an indication of sensing capability comprising a sensing service area of the sensing node; entering the sensing node and the indication of sensing capability in a register; receiving a sensing request related to sensing in a target sensing area; configuring the sensing node to perform a sensing task, wherein the sensing service area of the sensing node at least partly overlaps the target sensing area; receiving and processing sensing data related to the sensing task from the sensing node to provide a sensing result; and sending the sensing result to another network entity.

[0017] The method may comprise implementing a central sensing function for receiving the sensing request and sending the sensing result; and implementing a serving sensing function for receiving the registration message and entering the sensing node in the register and for configuring the one or more sensing nodes to perform the sensing task.

[0018] The method may comprise, with the serving sensing function, maintaining the register and configuring one or more sensing nodes in the register to perform the sensing task.

[0019] The method may comprise, with the serving sensing function, sending a registration request to a network repository function, wherein the registration request comprises an indication of a sensing capability of the serving sensing function.

[0020] The method may comprise, with the central sensing function, in response to receiving the sensing request, querying the repository network function and selecting one or more serving sensing functions for the sensing task based on the registered sensing capabilities of the one or more serving sensing functions.

[0021] The method may further comprise, with the serving sensing function, receiving a sensing configuration update from a first sensing node in the register of sensing nodes of the serving sensing function; determining that the first sensing node has left a sensing registration area; and sending a sensing configuration reply comprising a target serving sensing ID. [0022] Some implementations of the method and apparatuses described herein may further include a base station for wireless communication, comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to send a registration request to a sensing function of a network, wherein the sensing request comprises an indication of sensing capability of the base station comprising a sensing service area; receive a registration response from the sensing function; receive a sensing request from the sensing function to perform a sensing task relating to a target sensing area; perform the sensing task to obtain sensing data; and send the sensing data to the sensing function.

[0023] The registration response may comprises a registration area, and wherein the at least one processor is further configured to send a registration update to the sensing function when leaving the registration area. The at least one processor can be further configured to send a second registration request to a second sensing function when leaving the registration area.

[0024] The registration request may further comprise at least one of an indication if the base station is a primary sensing node or a secondary sensing node, wherein a primary sensing node is configured to manage at least one secondary sensing node to perform a sensing task; an indication of only sensing signal transmission, only sensing signal reception, or duplex sensing signal transmission and reception; a set of sensing groups to which the base station belongs to, wherein entities belonging to a sensing group are registered with the same sensing function; and a type of base station being one of mobile or stationary.

[0025] Some implementations of the method and apparatuses described herein may further include a method performed by a base station. The method comprises sending a registration request to a sensing function of a network, wherein the sensing request comprises an indication of sensing capability of the base station comprising a sensing service area; receiving a registration response from the sensing function; receiving a sensing request from the sensing function to perform a sensing task relating to a target sensing area; performing the sensing task to obtain sensing data; and sending the sensing data to the sensing function. [0026] The registration response may comprise a registration area, and the method may further comprise sending a registration update to the sensing function when the base station leaves the registration area. The method may further comprise sending a second registration request to a second sensing function when leaving the registration area.

[0027] The registration request may further comprises at least one of an indication if the base station is a primary sensing node or a secondary sensing node, wherein a primary sensing node is configured to manage at least one secondary sensing node to perform a sensing task; an indication of only sensing signal transmission, only sensing signal reception, or duplex sensing signal transmission and reception; a set of sensing groups to which the base station belongs to, wherein entities belonging to a sensing group are registered with the same sensing function; and a type of base station being one of mobile or stationary.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0032] Figure 5 illustrates a network architecture comprising a core network, comprising a central sensing function and a serving sensing function, and an access network comprising a plurality of access network nodes;

[0033] Figure 6 illustrates a signaling flowchart of a sensing process;

[0034] Figure 7 illustrates an example of a user equipment (UE) 700 in accordance with aspects of the present disclosure. [0035] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure.

[0036] Figure 9 illustrates an example of a network equipment (NE) 900 in accordance with aspects of the present disclosure.

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

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

DETAILED DESCRIPTION

[0039] In case of large network deployments and many different sensing tasks, it can be a large burden for a single SF to maintain and perform all network sensing tasks.

[0040] Furthermore, if a base station is a transmitter of the sensing signal, how is the base station selected and configured to perform a particular sensing task. The problem can be described as follows: how to distribute a sensing task to a large network deployment; and how to allow the core network to know sensing capabilities of each access network (AN) node.

[0041] The present disclosure at least partly solves these problems by registering sensing nodes with one or more sensing functions (i.e. creating a direct association between the sensing nodes and the sensing function) and maintaining the register with the sensing capabilities of the sensing nodes.

[0042] Benefits of the disclosure may include more efficient distribution and completion of sensing tasks within the wireless communication system. This can allow for cheaper and improved sensing services provided to sensing consumers.

[0043] Aspects of the present disclosure are described in the context of a wireless communications system. [0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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).

[0050] 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.

[0051] 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).

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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., fi=O) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0056] 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.

[0057] 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., /z=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., /z=3 ), which includes 120 kHz subcarrier spacing.

[0058] 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. [0059] 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 or application of the sensing consumer.

[0060] 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).

[0061] 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.

[0062] 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.

[0063] 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 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.

[0064] 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. There may be two kinds of sensing target area: (A) static sensing target area: a pre-defined area that does not move from the sensing transmitter’s perspective; or (B) moving sensing target area: a trusted zone with a target that moves from the sensing transmitter’s perspective.

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.

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

[0066] 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.

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

[0068] 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.

[0069] 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. [0070] 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.

[0071] Network functionality associated with the sensing service can be distributed in different network functions (NFs) wherein each network function can have a specific sensing functionality. This architecture can be described as hierarchical sensing function architecture, where the sensing service functionality is distributed in different NFs. In one particular example, the structure of sensing functionality is organized hierarchically in the CN, e.g. Central Sensing Functions (C-SF, or primary SF or aggregator SF) and Serving SF (S-SF).

[0072] A direct association can be established between the SF in the control plane (CP) and a sensing node (e.g. an AN node) which is capable of performing sensing. An SF can maintain a register of sensing nodes and their respective sensing capabilities. A sensing capable AN node can registers with one or more SFs in the core network. Such association is shown as “N2-s” 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.

[0073] Alternatively, the N2-s association may also traverse via the AMF and use the existing N2 interface. In such case, the protocol data units between the SF and the AN node are encapsulated in (a) the protocol used for exchange between the SF and AMF and (b) the N2 protocol, e.g. NGAP, used between the AMF and AN node.

[0074] Figure 5 shows an example architecture for providing a sensing service and comprising both an Access Network (AN, which can be a Radio Access Network, RAN) and a Core Network 501 (CN, which in case of 5G is referred as 5GC). The sensing functionality may be deployed either in a single SF 502, or can be split in hierarchical structure of SFs which are exemplary shown as a Central SF (C-SF) and Serving SF (S-SF). For each sensing task or set of sensing tasks, which may be requested by an AF (a SF consumer), there can be one C-SF (e.g. pre-configured) 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 a sensing target area which is part of the serving area of multiple S-SFs, then the C-SF can select multiple S-SFs to serve the same sensing task. Similarly, when a sensing task involves sensing objects (which may also be UEs) with high velocity involving a greater geographical area or require sensing that may need to combine different capabilities related to distinct S-SF nodes.

[0075] The Central SF (C-SF) functionality may comprise one or more of the following: a) Storing of the sensing request(s) from an AF and creating a sensing context for a sensing task. b) Discovery and selection of one or more S-SFs which are appropriate to serve a sensing task. For example, the C-SF can select an S-SF based on the location information and/or based on other sensing capability information. c) Receiving sensing measurement data and calculating a sensing result (i.e. processing the received sensing data). d) Aggregating sensing data/reports/measurements received from the reporting entities (e.g. S-SFs, AN nodes and/or UEs) or receiving calculated/obtained sensing results by the S-SF associated with a sensing task. e) Exposing the processed (or obtained) sensing results of a sensing task to the sensing consumer. f) Creating charging data towards a charging function, e.g. CHF.

[0076] The Serving SF (S-SF) functionality may comprise of one or more of the following: a) Receiving a sensing task assigned by the C-SF. b) Establish an association with an AN node supporting sensing and exchange one of (1) the sensing-related capabilities or other information and (2) configuration information with this AN for a specific sensing task and/or (3) obtained sensing information/measurement from the AN of the assigned sensing task. c) The configuration for a sensing task may include the following functionality: i. discovery and selection of (R)AN node(s) for a specific sensing task, e.g., considering the location/geographical information or sensing service area of the RAN nodes or TRPs; ii. create/update/delete of the sensing task in the AN node. iii. changing of (R)AN nodes upon sensing object mobility or modification of the sensing task; iv. aggregating sensing reports (e.g., further process the sensing measurements or generate sensing results or processed sensing measurements etc.) and transmitting the aggregated sensing report to upstream entity (e.g. to the C-SF) or forwarding sensing data to C-SF for processing to generate sensing result.

[0077] Figure 5 also shows an example of an access network (AN) 507. For example, the AN includes a gNBl 508, gNB2 509 and n3GPP-S-AN 510 (described below). gNBl 508 comprises a central unit (CU) 511 connected to the 5GC via a N2 interface.

[0078] gNBl 508 may comprise one or more distributed units (DUs) 512 of which one is shown in the figure. The gNBl 508 further comprises radio remote units (RRU), RRU1 513 and RRU2 514 which are configured to transmit and receive (a) communication data and (b) sensing radio signals. In addition to conventional interfaces in the RAN used for data communication (e.g. Xn, Fl, El, etc.), there may be new interfaces (or enhanced existing interfaces) specifically for the sensing-related information exchange. The sensing- related information exchange may include: (a) sensing task configuration and (b) sensing data transmission. Such new interfaces are exemplary shown as “X-s”. The CU 511 may store the context for a sensing task as requested by the SF 503. Then the CU 511 can decide which RRUs to configure to perform the radio sensing, e.g. whether the RRU acts as sensing transmitter or sensing receiver, or both.

[0079] In one example, the gNBl 508 contains an RRU1 513 entity that may be connected to the DU 512 via a fronthaul interface for data communication and via a “X-s” interface with the CU 511 for the sensing-related information exchange. Which means that the DU 512 may not be involved in the sensing -related information exchange.

[0080] Furthermore, the gNBl 508 may include a RRU which is dedicated for sensing purposes only, i.e. such a RRU does not transmit communication data. Such RRU is shown as RRU-S or Transmit-Receive Point for sensing (TRP-S) 515. The RRU-S/TRP-S 514 may be configured by the CU 511 to perform a specific sensing task task (with determined sensing capabilities) and may report the sensing data directly to the CU 511. The RRU- S/TRP-S 515 may perform sensing in the LTE or NR radio spectrum, but it also may perform the sensing using non-3GPP technologies, i.e. technologies not specified by the 3 GPP standard organization. Such non-3GPP technologies may include camera or radar. [0081] The n3GPP-S-AN 510 is a stand-alone non-3GPP Sensing Access Node and is a sensing node which can be configured to perform sensing of the environment or objects using a non-3GPP technology. While both the RRU-S/TRP-S 515 and the n3GPP-S-AN 510 may perform sensing using non-3GPP technology, the RRU-S/TRP-S 515 is part of a 3GPP specified base station (e.g. gNBl 508, and thus, the RRU-S/TRP-S 515 is not seen by the CN as a stand-alone node) and the n3GPP-S-AN 510 is a standalone node seen as such by the CN. Non-3GPP sensing (e.g. camera sensing) is referred to more generally as nonwireless communication sensing.

[0082] 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).

[0083] For capability info exchange between SF and AN for non-3GPP sensing data type generation/support and processing of non-3GPP sensing data, in some embodiments, the exchange of the SF (S-SF or C-SF) and the AN further comprises capability information of the SF for receiving and/or processing of the non-3GPP sensing measurement data (e.g., type, format, resolution of the non-3GPP sensing data, e.g., indicating if a camera bitmap image of 1024 by 1024 with 8 bits for each pixel is supported by the SF to be received/processed/fused with other measurements etc.), which may be or may be not specified by the 3GPP system, but with a defined association to exchange such capability information. In some other embodiments, the exchange of the SF (S-SF or C-SF) and the AN further comprises capability information of the AN to generate and/or processing of the non-3GPP sensing measurement data (e.g., AN capable of generate camera image data with an indicated format and indicated quality/resolution and/or processing of the non-3GPP sensing data to e.g., extract objects, detect humans, transform a data format to another data format, etc.). In some implementations of the said embodiment, the exact non-3GPP data format types and/or processing capabilities may be or may be not specified by the 3GPP system, but are exchanged with a defined association (between the AN and the SF) to exchange such capability information. [0084] As consequence of one or multiple of the above capability information exchanges between SF and the AN node, the AN node may perform one or multiple of: (A) to generate a non-3GPP sensing data (e.g., capture camera image of a desired sensing area) according to the supported types of the SF; (B) to process a generated non-3GPP sensing data; or (C) communicate to the SF the generated and/or processed non-3GPP data via data or control plane associations.

[0085] In some implementations, the selection of AN communicating with SF the obtained (processed) measurement data is made based on: (A) indicated processing capability of the AN; (B) indicated non-3GPP (or 3 GPP) sensing measurement data types that can be generated by the AN; or (C) SF capability for processing of non -3 GPP (or 3GPP) sensing measurement data types.

[0086] Figure 6 illustrates a signaling flowchart of a process for providing a sensing service in accordance with aspects of the present disclosure.

[0087] At step S601, the (R)AN node can 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 is configured with sensing capabilities. The sensing Access Network (AN) node or Radio Access Network (RAN) node, referred to as (R)AN node, may include any of the AN nodes described in relation to Figure 5 above (e.g. gNBl, gNB2 or n3GPP-S-AN). The Sensing (R)AN node is a node which performs sensing functionality/service including sensing measurements and/or sensing reporting. It may be either a node performing merely sensing service, or a node performing both sensing and communication services. The sensing functionality/service can include sensing measurements (including transmitting and/or receiving of sensing measurement signals) and reporting the sensing data.

[0088] If the sensing (R)AN node uses non-3GP sensing technology (e.g. a sensing sensor using non-3GP sensing technology as shown in Figure 5), such n3GPP-S-AN should be trusted and authorized to provide the sensing data to the CN. For this purpose, the 0AM may configure the n3GPP-S-AN with security credentials to allow secure/trusted connection or association establishment between the n3GPP-S-AN and the CN. Also, the (n3GPP-S-AN should be able authenticate and authorize one or more sensing sensors (e.g. camera, lidar, radar) connected to the n3GPP-S-AN. [0089] At step S602, the S-SF can be configured, e.g. by the 0AM system, with a network function (NF) type to be a S-SF, a unique NF identifier (e.g. unique within the network operator domain), a serving area (e.g. a collection of one or more tracking areas), and other parameters.

[0090] At step S603, the C-SF can be configured, e.g. by the 0AM system, with a network function (NF) type to be a C-SF, a unique NF identifier (e.g. unique within the network operator domain), one or more sensing capabilities, and other parameters.

[0091] The S-SF and C-SF may be implemented as a single SF and in such case the steps S602 and S603 can be performed to such single SF.

[0092] At step S604, the C-SF registers with the Network Repository Function (NRF) indicating its NF type of C-SF and one or more sensing capabilities. The NRF stores an entry for each C-SF with the corresponding parameters. The NRF can send an acknowledgement to the C-SF.

[0093] The C-SF sensing capability may comprise:

[0094] Regarding the control plane (CP) and/or user plane (UP) sensing data reception/transmission, the C-SF may indicate support of CP sensing only, of UP sensing only or of CP+UP sensing.

[0095] Regarding the support of 3GPP radio sensing, the C-SF may indicate support of 3GPP sensing only, of non-3GPP sensing only or of 3GPP+non-3GPP sensing.

[0096] Sensing ID identifies the requested sensing “job” (or sensing type), e.g., “Verify Object Route”, “Detect Object”, “Estimate Object position”, “Estimated Object Velocity”, “Estimate Object mechanical periodicity”, etc.

[0097] Service Area or Area of Interest in terms of a TA, cell IDs, or geographical area represented as a set of ordered coordinates.

[0098] The sensing KPI of sensing service, which may be defined in connection to a sensing area (e.g., cell ID) and/or a sensing service type (e.g., detection and tracking of a human within the supported area A with KPI K).

[0099] The C-SF may indicate whether it is capable of processing sensing data received from the (R)AN node and which type of sensing data can be processed.

[0100] At step S605, the S-SF registers with the NRF indicating its NF type of S-SF, the service area and one or more sensing capabilities. The service area can be identified by a list of tracking areas, list of cells, or a geographical description of the area. The S-SF sensing capability may be one of:

[0101] Regarding the control plane (CP) and/or user plane (UP) sensing data reception/transmission, the S-SF may indicate support of CP sensing only, of UP sensing only or of CP+UP sensing.

[0102] Regarding the support of 3GPP radio sensing, the S-SF may indicate support of 3GPP sensing only, of non-3GPP sensing only or of 3GPP+non-3GPP sensing.

[0103] Sensing ID identifies the requested sensing “job” (or sensing type), e.g., “Verify Object Route”, “Detect Object”, “Estimate Object position”, “Estimated Object Velocity”, “Estimate Object mechanical periodicity”, etc.

[0104] The sensing KPI of sensing service, which may be defined in connection to a sensing area (e.g., cell ID) and/or a sensing type (e.g., detection and tracking of a human within the supported area A with KPI K).

[0105] The S-SF may indicate whether it is capable of processing sensing data received from the (R)AN node and which type of sensing data can be processed. The S-SF may indicate the type of non-3GPP sensing data which it is able to process, e.g. still image processing or video data processing. For example, such S-SFs can be used to be connected to n3GPP-S-ANs.

[0106] The NRF can store an entry for each S-SF with the corresponding parameters. The NRF can send an acknowledgement to the S-SF. Alternatively, step la and step lb can be performed by the 0AM, which can configure the NRF with the C-SF and S-SF sensing capability.

[0107] At step 606, if the (R)AN node is configured (or implemented and activated) to be a Sensing (R)AN node as described in step S601, the Sensing (R)AN node triggers a selection of one or more SFs (e.g. S-SFs) to which an association (e.g. transport network layer association, TNLA) should be established. The Sensing (R)AN node may use one of the following methods for SF selection:

[0108] The 0AM system may (pre-)configure the (R)AN node with a list of SF IDs to which the association needs to be established.

[0109] The (R)AN node may use the NRF service. For example, the (R)AN node may send a request to the NRF to query the SFs with a serving area including the (R)AN node serving area. The NRF would reply with a set of SFs (e.g. S-SFs) which serve the area where the (R)AN node is located.

[0110] In case that the (R)AN node communicates with the SF via the AMF, the (R)AN node may either (a) use an existing N2 transport association with an AMF or (b) select a new AMF supporting sensing functionality communication to which a new N2 transport association is established. Then the sensing (R)AN node can send a registration request to an SF via the N2 interface. Upon reception of the registration request, the AMF may select one or more SFs, e.g. using the NRF services, and the AMF forwards the (R)AN node’s request to the discovered SFs.

[0111] If the Sensing (R)AN node also performs communication service, the (R)AN node also has an N2 association with an AMF and N3 association with a UPF.

[0112] In the figure, the sensing (R)AN node selects a single SF (e.g. S-SF) to register its sensing capabilities in the CN, but in other embodiments, the sensing (R)AN node can register with multiple SFs. For example, this may be the case where there are multiple SFs implemented in a sensing service area.

[0113] At step S607, the Sensing (R)AN node initiates the establishment of a sensing association (also referred to as sensing registration) with the SF in the CN. Such sensing association is used to exchange the sensing capabilities of the (R)AN to the CN. The (R)AN node may use the NG Application Protocol (NGAP) or other protocol to establish a “N2-s“ association (e.g. on top to the transport layer association) with the selected SF. The Sensing (R)AN node may transmits a NG-S SETUP REQUEST message wherein the “NG- S” means that this message is analogous to the NG SETUP REQUEST message sent to establish N2 association with the AMF. For example, the request can be similar to the TNL association setup request for TNL association over the N2 interface with the difference that the request includes parameters identifying that the (R)AN node is capable of sensing and the sensing capabilities. Such a request can be referred as a N2-s association setup request. [0114] This NG-S signalling is a per-node signalling between the Sensing (R)AN node and the SF, i.e. it is a non-UE associated signalling. The NG-S signalling to exchange sensing application-level data needed for the NG-RAN node and the AMF to correctly interoperate on the CP and/or UP interface. [0115] The (R)AN node sends sensing capabilities which are static or semi-static, i.e. those capabilities are not expected to change frequently. The (R)AN node may include at least one of the following sensing-related capability parameters:

AN node ID: the sensing (R)AN node may have a unique ID within the network, sensing service area which may be a collection of one or more cell IDs, tracking area IDs, or a geographical area description. Please note that “cell ID” refers to the cells used for the data communication. A new definition of “cells for sensing” may be introduced wherein the cells are identified by different IDs than the cells for communication and the sensing cells may have different coverage than the communication cells. The sensing service area may be described as: o the point (e.g. geographical coordinates) where the (R)AN node is located and corresponding sensing range (e.g. in meters) and corresponding direction around the (R)AN node. Such sensing service area may be helpful particularly in case when (R)AN node supports non- 3 GPP sensing technology. o The edges of the area, e.g. a square or other form with the coordinates of corners. o There may be different levels of sensing areas, e.g. sensing service area 1 having higher accuracy and sensing service area 2 with lower accuracy. In one simplified example, the sensing area is represented as a list of one or more: exact locations of TRP and a region 1 around the TRP (e.g. a circle, hexagon or irregular form) and a region 2 around the TRP (e.g. a circle, hexagon or irregular form which may be concentric to region 1 ).

AN node location information: it may include the exact geographical location/address of the sensing node or the sensing TRPs. In other words, a single AN node may indicate multiple TRPs locations. sensing capabilities indicating one or more of the following: o whether the (R)AN node supports operation as primary sensing node or as secondary sensing node. A “primary Sensing (R)AN node” means that the (R)AN node may operate as serving node for a sensing task. Alternatively, only the primary sensing nodes can establish an N2-s association with the SF. The primary sensing node can select and configure a secondary sensing node for a particular task. In some examples, the sensing capability information of a (R)AN node (e.g. as a primary or secondary sensing node), includes the sensing KPI of sensing service, which may be defined in connection to a sensing area (e.g., cell ID) and/or a sensing type (e.g., detection and tracking of a human within the supported area A with KPI K). In some examples, the sensing capability information of a (R)AN node (e.g. as a primary or secondary sensing node) may include bandwidth, supported reference signal patterns for sensing, supported measurement types. In some embodiments, the capability information is accompanied with a time pattern (e.g., validity pattern), for which the indicated capability information is valid. Whether the (R)AN node supports only sensing signal transmission (Tx- only), only sensing signal reception (Rx-only), or duplex sensing signal transmission and reception (Tx+Rx). Which sensing technology the (R)AN node supports: e.g. non-3GPP sensing capability or 3 GPP sensing capability. In such case, the (R)AN node supports may further indicate the type of non-3GPP sensing capability, e.g. photo or video camera sensing, lidar or radar sensing, WLAN sensing, etc.

■ Alternatively, or in addition, in case the sensing operation is performed with 3 GPP sensing technology (e.g. using the NR technology also for sensing), the capability may further indicate whether the sensing operation is performed in licensed or unlicensed frequency band. What is the supported sensing accuracy of the (R)AN node. For example, the sensing accuracy may depend on the sensing technology used by the (R)AN node, the frequency, transmission power, etc. This may include also the sensing resolution. o Supported sensing frequency bandwidth, e.g. 20 MHz, 100 MHz, etc. o Supported sensing periodicity, or refreshing rate of the sensing measurements. o Whether the (R)AN node belongs to one or more sensing groups and further details about the sensing group. The sensing group can include beside TRPs also fixed (or semi-fixed) UEs, e.g. mounted on houses or other static objects. This information may include the details of each member of the sensing group, e.g. TRP1 with associated details, TRP2 with associated details, UE1 with associated details, UE2 with associated details, etc., wherein the details may include the exact location, direction and the sensing capabilities of each group member. o Whether the (R)AN node is mobile or stationary. For example, if the (R)AN node is a mobile relay node or Integrated Access and Backhaul (IAB), the (R)AN node indicates that it is mobile. In case of mobile (R)AN node, the SF needs additional input information to know the current location and the current sensing service area of the (R)AN node. o What is the supported reporting path for the sensing data, e.g. whether the AN node supports control plane (CP) transmission or user plane (UP) transmission of the sensing data, or both.

[0116] The sensing (R)AN node may determine whether to notify its capabilities on per AN node basis (i.e. the gNB basis or central unit (CU) basis), or include more granular information like on per TRP or participating sensing UE basis. The sensing (R)AN node may be configured locally to make this determination, or there can be an additional signaling exchange between the sensing (R)AN node and the SF and the SF may indicate to the sensing (R)AN node whether to provide more granular information.

[0117] If the sensing (R)AN node has selected multiple SFs in step S606, the sensing (R)AN node performs step S607 with each of the selected SFs in order to register its sensing capabilities with the CN.

[0118] At step S608 the SF sends to the Sensing (R)AN node a registration response message to the registration request from step 607. In one example, the registration response message may be a NG-S SETUP Response message wherein the message is analogous to the NG SETUP RESPONSE message sent to establish N2 association with the AMF. The SF may include a result indication for the registration (or association establishment) request. The result indication may include a positive result or negative result. In case of negative result, the response message may further comprise at least one of: an appropriate cause for the failed registration (e.g. indicating the reason for the failure like the SF does not support corresponding capabilities to serve the AN node capabilities or AN node type), a release indication or a redirection indication and corresponding target SF ID of an SF which may be more appropriate to serve the sensing (R)AN node.

[0119] If the (R)AN node is mobile, in the response message the SF may configure the

(R)AN node with a sensing registration area where the (R)AN node is considered registered at the SF. If the (R)AN node leaves the sensing registration area, the (R)AN node can be configured to perform an update of its sensing association (or sensing registration update). [0120] The NG-S SETUP Response message may be also used in the sensing (R)AN node as a subscription for notification (from the SF) for any change of sensing capabilities in the (R)AN node. In this case, the (R)AN node will automatically trigger an update procedure to notify the SF about any change in the (R)AN node sensing capabilities. Such update procedure is shown in step S610.

[0121] At step S609 the S-SF maintains a registration of (R)AN nodes. For example, the S-SF stores an entry for each association with the (R)AN node. It means, for each (R)AN node association, the S-SF may store a (R)AN node ID, the sensing service area, and the received sensing capabilities of the node. As a result of the (R)AN nodes registration, the S-SF may identify (or determine) that its capabilities are updated, as the capabilities of the registered (R)AN nodes may implicitly be perceived as S-SF capabilities. Therefore, the S-SF may update its registration with the NRF in order to include its updated capabilities which is similar as the step S605.

[0122] At step S610 the sensing (R)AN node may update an established association with the SF in the CN. The sensing (R)AN node may use the NG-S Configuration Update Request message including the AN node ID and the sensing parameters or capabilities which have been updated. In one example, the message may be called NG-S Configuration update message. [0123] For example, if the sensing (R)AN node is a mobile node, the sensing (R)AN node may send a new location and a corresponding new sensing service area to the SF.

[0124] At step S611 the SF sends to the (R)AN node a response to the NG-S Configuration update message. In one example, the message may be referred to as NG-S Configuration Response message and may include the SF-S node ID, and the result of the sensing capability update. If the result of the update is negative, e.g. the SF determines that it cannot any longer serve the (R)AN node, the SF may include a release indication or a redirection indication and a target SF ID of an SF which may be more appropriate to serve the sensing (R)AN node and possibly including the cause or reason why release or redirection is required.

[0125] If during the update procedure, the sensing (R)AN node is a mobile sensing node and the update message in step S610 indicates an update of the sensing service area, the S-SF may determine that the sensing (R)AN node needs to register with a new SF and the current SF may include release indication and a target SF ID in the response to the sensing (R)AN node.

[0126] At step 612, if the S-SF determines locally that it cannot any longer serve an established sensing association with a sensing (R)AN node (e.g. due to congestion, overload or other reason), the current SF can send to the sensing (R)AN node a NG-S Configuration Update Request message including the SF-S node ID, release indication, release cause and/or target SF ID.

[0127] At step 613, if the sensing (R)AN node determines that an established association with the SF in the CN needs to be released, the sensing (R)AN node may send to the SF an NG-S Release Request message including the AN node ID and the release cause. In one example, the sensing (R)AN node may send either a) a release request message (e.g. NG-S Release Request message), or b) an update/modification message (e.g. NG-S Configuration Update Request message) with a release indication.

[0128] Some examples for triggering a release of the sensing association with the SF include:

The sensing capability of the (R)AN node is disabled, e.g. the 0 AM system has reconfigured the sensing (R)AN node to be a communication node only. Due to mobility, the sensing (R)AN node needs to register with a new SF, e.g. the new S-SF is S-SF2, and the sensing association with the old S-SF should be released.

[0129] When the SF receives the request to release the association regarding the sensing capability of the (R)AN node, the SF can remove the (R)AN node from the register of sensing nodes. For example, the SF can remove the entry of this (R)AN node from an internal data base.

[0130] At step S614, similar to step S607, the sensing (R)AN node may send a registration request to a new SF (e.g. to another S-SF).

[0131] At step S615, similar to step S608, the SF responds to the sensing (R)AN node with a registration request response.

[0132] A benefit of the method illustrated in Figure 6 is that a direct association between the sensing (R)AN node and the SF is established. The (R)AN node may register with one or more SFs in the CN and send its sensing capabilities which are static or semistatic. The SF can maintain a transport association with the registered sensing (R)AN nodes and stores the corresponding context per (R)AN node. The (R)AN node context in the SF can comprise the sensing service area of the node and other sensing capabilities.

[0133] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, 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.

[0134] The processor 702, the memory 704, the controller 706, or the transceiver 708, 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. [0135] The processor 702 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 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.

[0136] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 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.

[0137] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein. The UE 700 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.

[0138] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702. [0139] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0140] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 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 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0141] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 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 712 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 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0142] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. 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).

[0143] The processor 800 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 800) 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).

[0144] The controller 802 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 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

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

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

[0147] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 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 802 and/or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and/or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 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.

[0148] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800). In some other implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800). One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 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 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

[0149] The processor 800 may support wireless communication in accordance with examples as disclosed herein. The processor 800 may be configured to or operable to support a means for receiving registration requests from sensing nodes in a wireless communication network, wherein the registration requests comprise an indication of sensing capability comprising a sensing service area of the sensing node, and maintaining one or more registers of sensing nodes and their respective sensing capabilities.

[0150] In another embodiment, the processor 800 is comprised by a base station and may be configured to or operable to support means for sending a registration request to a sensing function of a network (the sensing function may be a CN function and may be implemented by a network entity), wherein the sensing request comprises an indication of sensing capability of the base station comprising a sensing service area, receiving a registration response from the sensing function, receiving a sensing request from the sensing function to perform a sensing task relating to a target sensing area, performing the sensing task to obtain sensing data, and sending the sensing data to the sensing function.

[0151] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, 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.

[0152] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g.,

SUBSTITUTE SHEET (RULE 26) 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.

[0153] The processor 902 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 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.

[0154] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 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.

[0155] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein. The NE 900 may be configured to support a means for receiving registration requests from sensing nodes in a wireless communication network, wherein the registration requests comprise an indication of sensing capability comprising a sensing service area of the sensing node, maintaining one or more registers of sensing nodes and their respective sensing capabilities, and sending a registration response indication a result of the registration. 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. [0156] 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 sending a registration request to a sensing function of a network, wherein the sensing request comprises an indication of sensing capability of the base station comprising a sensing service area, receiving a registration response from the sensing function, receiving a sensing request from the sensing function to perform a sensing task relating to a target sensing area, performing the sensing task to obtain sensing data; and sending the sensing data to the sensing function.

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

[0158] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

[0159] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 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 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0160] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 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 912 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 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

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

[0162] At 1002, the method may include receiving a registration request from a sensing node in a wireless communication network, wherein the registration request comprises an indication of sensing capability comprising a sensing service area of the sensing node The operations of step 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a NE as described with reference to Figure 9.

[0163] At 1004, the method may include entering the sensing node and the indication of sensing capability in a register. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a NE as described with reference to Figure 9.

[0164] At 1006, the method may include sending a registration response indicating a result of the registration. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed by a NE as described with reference to Figure 9. [0165] 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.

[0166] Figure 11 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.

[0167] At 1102, the method may include sending a registration request to a sensing function of a network, wherein the sensing request comprises an indication of sensing capability of the base station comprising a sensing service area. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 9.

[0168] At 1104, the method may include receiving a registration response from the sensing function. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a NE as described with reference to Figure 9.

[0169] At 1106, the method may include receiving a sensing request from the sensing function to perform a sensing task relating to a target sensing area. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed by a NE as described with reference to Figure 9.

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

[0171] At 1110, the method may include sending the sensing data to the sensing function. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 110 may be performed by a NE as described with reference to Figure 9.

[0172] 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.

[0173] 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.