WO2024099606A1

WO2024099606A1 - Sensing node handover procedure

Info

Publication number: WO2024099606A1
Application number: PCT/EP2023/071207
Authority: WO
Inventors: Seyedomid TAGHIZADEH MOTLAGH; Konstantinos Samdanis; Genadi Velev; Joachim Löhr; Prateek Basu Mallick
Original assignee: Lenovo (Singapore) Pte. Ltd.
Priority date: 2023-07-10
Filing date: 2023-07-31
Publication date: 2024-05-16

Abstract

Various aspects of the present disclosure relate to 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 from a first entity a request to perform a sensing task, determine a first set of at least one sensing node to perform a sensing task, configure the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of: (i) transmission from the at least one sensing node of at least one sensing signal; and (ii) reception at the at least one sensing node of at least one sensing signal; identify a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task: initiate a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or de-selecting the incapable sensing node; wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task.

Description

SENSING NODE HANDOVER PROCEDURE

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to 3GPP-based radio sensing.

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, sub-frames, 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 construed 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] In some implementations of the method and apparatuses described herein, there is provided, according to a first aspect, 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 from a first entity a request to perform a sensing task, determine a first set of at least one sensing node to perform a sensing task, configure the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of: transmission from one or more of the at least one sensing node of at least one sensing signal; and reception at one or more of the at least one sensing node of at least one sensing signal, identify a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task, initiate a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; orde-selecting the incapable sensing node, wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task.

[0007] In an embodiment, the network entity is further configured to identify the need for a handover operation based on one or more of a capability information of the at least one sensing node, a sensing target area location information and/or mobility pattern, at least one key performance indicator and at least one triggering event, or a combination thereof. [0008] In an embodiment, the network entity is further configured to identify the need for a handover operation is based on a target characteristic, wherein the target characteristic is at least one of: a sensing target area, a sensing target object description or a sensing task information.

[0009] In an embodiment, the triggering event is one or more of a determination of location of the target or determination of a mobility pattern of the target.

[0010] In an embodiment, network entity is further configured to:

(i) receive at least one report in connection with the sensing task from one of the at least one sensing node; and

(ii) identify the need for a handover wherein at least one of the at least one triggering events is the at least one report.

[0011] In an embodiment, the at least one report comprises an incapability indicatorfrom an incapable sensing node ora capability indicator from an additional sensing node, wherein the sensing incapability or capability indication comprises an indication of a sensing task, and a sensing configuration associated with the said sensing task.

[0012] In an embodiment, the incapability indicator and/or the capability indicator of a sensing node provides an indication as to whether the incapability indicator and/or the capability indicator applies to transmission, reception or both.

[0013] In an embodiment, the incapability indicator and/or the capability indicator of a sensing node comprises an indication of one or more capability or incapability types, wherein each capability or incapability type is identified by a respective index of a plurality of indices corresponding to respective types, the indices being stored in a look-up table.

[0014] In an embodiment, the capability type and/or incapability type is one of:

(i) a sensing transmission is not possible at a certain angular direction;

(ii) a battery storage is low,

(i) a sensing target distance has reached an indicated threshold, or

(ii) an indicated criterion for sensing incapability is met.

[0015] In an embodiment, the capability indicator and/or the incapability indicator comprises timing information indicating a start time and a stop time for the respective capability or incapability type for the sensing node.

[0016] In an embodiment, the network entity is further configured to provide configuration information for the at least one sensing node comprising one or more of: (i) timing requirements for reporting of the incapability indicator or the capability indicator;

(ii) time and/or frequency resources for transmitting the incapability and/or capability indicator;

(iii) one or more criteria for determining incapability of a sensing node.

[0017] In an embodiment, the network entity is further configured to supply the one or more selection and/or deselection levels to the sensing nodes by supplying one or more respective indices from a codebook, wherein the respective indices represent pre-defined selection and /or deselection levels stored in the codebook.

[0018] In an embodiment, the network entity is further configured to supply to the sensing node pattern and/or timing information comprising one or more of: a de-selection start time for an indicated de-selection, a time duration for which the indicated de-selection, and a maximum time duration, after which a de-selected sensing node shall perform sensing measurement and report the obtained sensing measurements upon receiving an indication from the network entity.

[0019] In an embodiment, the network entity is further configured to supply to the at least one sensing node a first time information associated with a first de-selection level and a second time-information associated with a second de-selection level.

[0020] In an embodiment, the network entity is further configured to perform de-selection of the at least one sensing node from the first set of sensing nodes, based on a common indication of a sensing target area according to a known coordinate system and a distance compared with a threshold of the sensing node to the indicated target area.

[0021] In an embodiment, the network entity is further configured to communicate to an at least one incapable nodes, when performing deselection of the incapable sensing node, one or more de-selection levels from a plurality of deselection levels, wherein the plurality of deselection levels comprises:

(i) an indication to the at least one incapable sensing node not to further report configured sensing measurements;

(ii) an indication to the at least one incapable sensing node not to transmit the sensing signal;

(iii) an indication to the at least one incapable sensing node that the incapable sensing node may re-use assigned resources for sensing transmission, reception, and measurements for other purposes;

(iv) an indication to the at least one incapable sensing node that the incapable sensing node is not required to retain context information of the sensing task, and the configuration information and parameters of sensing measurement associated to the sensing task;

(v) an indication to the at least one incapable sensing node that the incapable sensing node is required to perform and/or retransmit sensing measurement reports of the sensing task/configuration within an indicated/agreed time latency, upon future indication of the sensing controller entity.

[0022] In an embodiment, the network entity comprises one or more of: a base station, a core network entity or a user equipment, UE, and the at least one sensing node is one or a UE, a radio access network, RAN, node or a non-3GPP sensor.

[0023] According to a second aspect, there is provided a method performed by a sensing controller entity comprising: receiving from a first entity a request to perform a sensing task, determining a first set of at least one sensing node to perform a sensing task, configuring the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of: transmission from one or more of the at least one sensing node of at least one sensing signal; and reception at one or more of the at least one sensing node of at least one sensing signal, identifying a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task: initiating a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or de-selecting the incapable sensing node, wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task.

[0024] According to a third aspect, there is provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive from a first entity a request to perform a sensing task, determine a first set of at least one sensing node to perform a sensing task, configure the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of: transmission from one or more of the at least one sensing node of at least one sensing signal, and reception at one or more of the at least one sensing node of at least one sensing signal, identify a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task: initiate a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or de-selecting the incapable sensing node, wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task.

[0025] According to a fourth aspect, there is provided a sensing node 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 sensing node to: receive configuration instructions from a network entity for a sensing task, sense, based on the configuration instructions, a target in an environment of the sensing node by way of reception at the sensing node of at least one sensing signal, report one or more sensing measurements to the network entity, receive a deselection indication from the network entity; and stop the sensing and measurement reporting in response to the deselection indication.

[0026] In an embodiment, the sensing node is further configured to receive from the network entity one or more incapability criteria determine whether the node is incapable of performing the sensing task based on the at least one sensing measurement and the one or more incapability criteria; and report an incapability indicator to the network entity if the sensing node is determined to be incapable of performing the sensing task based on the incapability criteria.

[0027] According to a fifth aspect, there is provided a sensing node 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 sensing node to: receive configuration instructions from a network entity for a sensing task; transmit from the sensing node at least one sensing signal to a target in an environment of the sensing node, based on the configuration instructions; transmit one or more reports associated with the transmission of the at least one sensing signal; receive a deselection indication from the network entity; and stop the transmission of the at least one sensing signal in response to the de-selection indication.

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 an example of a sensing task implemented in a wireless communications system in accordance with aspects of the present disclosure.

[0030] Figure 3 illustrates an example of a sensing task implemented in a wireless communications system in accordance with aspects of the present disclosure.

[0031] Figure 4 illustrates an example of signaling between network nodes in accordance with aspects of the present disclosure.

[0032] Figures 5a-5c illustrating the result of sensing controller entity handover procedure in accordance with aspects of the present disclosure.

[0033] Figure 6 illustrates handover of a sensing task in accordance with aspects of the present disclosure.

[0034] Figure 7 illustrates a method of handover in accordance in accordance with aspects of the present disclosure.

[0035] Figure 8 illustrates handover of a sensing node in accordance with aspects of the present disclosure.

[0036] Figure 9 illustrates handover of a receiving sensing node in accordance with aspects of the present disclosure.

[0037] Figure 10 illustrates handover of a transmitting sensing node in accordance with aspects of the present disclosure.

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

[0039] Figure 12 illustrates an example of a processor 1200 in accordance with aspects of the present disclosure. [0040] Figure 13 illustrates an example of a network equipment (NE) 1300 in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0041] 3GPP-based sensing provides both a mechanism for improving network performance and an enabler to serve vertical use-cases, wherein radio signals are used to obtain information of the surrounding environment. Information is obtained from the environment by transmission of one or more sensing signals from one or more transmitting sensing node, typically a user equipment, but which may be any network node, and reception of reflections/echoes of the transmitting signal by one or more receiving sensing nodes. The transmitting and receiving nodes may comprise the same node, a pair of nodes, or multiple transmission and reception nodes. At a start of a sensing task, a first set of transmission and reception nodes are selected, which have the capability and the geographic location to perform the sensing task. However, as the sensing task progresses, movement of the target being sensed and/or changes in network conditions may result in a sensing node no longer being capable of performing its previous role in the sensing task. At the same time, the change in conditions and/or location may mean that other sensing nodes not previously involved in the sensing task may be capable of a role in that task.

[0042] The sensing task request may include one or more of a requested sensing information type (presence detection, object classification, velocity information, position information, tracking, etc.), desired sensing key performance indicators, KPI (e.g., resolution, accuracy, latency, etc., according to TR 22.837), a sensing target description (area, object type, object ID (if applicable), etc.), UE ID associated with the sensing task as sensing capable UE/RAN nodes associated to the sensing target area of interest, and a UE ID associated with the sensing task as a UE attached to or close-by the sensing target area of interest.

[0043] The present invention provides a method of implementing a handover procedure, whereby sensing nodes no longer capable of implementing a sensing task may be deselected, and other nodes, previously incapable or less optimally capable, but now capable, are selected for the sensing task. The handover mechanism enables the sensing task to be continued in an efficient manner.

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

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

[0047] 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. [0048] 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 Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

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

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

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

[0052] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an S1 , 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).

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

[0054] 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., /z=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., /z=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., /z=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., /z=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., /z=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /z=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

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

[0056] 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., /z=0, /z=1 , /z=2, /z=3, /z=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., [i =0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

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

[0058] 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., /z=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /z=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /z=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., /z=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /z=3), which includes 120 kHz subcarrier spacing.

[0059] 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. Different nodes being used as sensing nodes is illustrated in Figures 2 and 3.

[0060] Figure 2 is a network diagram illustrating the implementation of a sensing task. A sensing object 204 is being sensed. The scenario shows two base stations, 210a, 210b acting as sensing nodes, one of which, 210a, is just a transmitter, 211a, and one of which, 210b, is performing both transmission, 211 b, and reception, 211c. A further sensing node comprises a user equipment, UE, 208, which is acting as a sensing Rx node, 211d.

[0061] Figure 3 illustrates another example, again with sensing object 204 being sensed. Here, two of the sensing nodes, 308a, 308b, are UEs, with one being a sensing Tx node, 311a, and the other, 308b, performing both transmission, 311 b, and reception, 311c. A further sensing node, 310, is a gNodeB, which is acting as a sensing Rx, 311d.

[0062] The person skilled in the art will appreciate that any combination of sensing nodes is possible, with different numbers of different types of network node being used as sensing Tx nodes, sensing Rx nodes, or with both roles. The invention is not limited to any combination of sensing node types.

[0063] Figure 4 is a signaling diagram illustrating the interaction, 400, of network nodes during a sensing task. A sensing controller entity, 410, provides configuration information, 420, to enable the configuration of the sensing nodes 408a, 408b. Sensing measurements, 430, are taken between the sensing nodes, which are then reported, 440, to the sensing controller entity, 410.

[0064] A sensing service may need to: (i) select a certain combination of Sensing Tx and Sensing Rx nodes that can cover the desired sensing area of interest for the given sensing targets, and (ii) configure the RAN optimization parameters related to the selected Sensing Tx and Sensing Rx nodes, which may include the allocation of time/frequency resources, defining the sensing signals (e.g., RS parameters), beam, L1 measurement types etc. A sensing target may be an object or a target area. A sensing target may be an object or a target area. When the sensing target is an object, the object may be a passive object e.g. an object which is not registered with the mobile network or cannot report sensing measurements to the network (a non-SIM device). For example, the passive object may be a person or a vehicle. In these examples, a UE may be attached to the object or may be inside the object. When the sensing target is an object, the object may be an active object e.g. an object which is registered with the mobile network and can report sensing measurements to the network. When the sensing target is a target area, in one example the target area may be a room of a house for intruder detection e.g., a target area is sensed to detect if and when an external object “appears”.

[0065] It shall be noted that the OAM configures the long-term allocated resources for the purpose of sensing in Sensing Tx and Sensing Rx nodes. These resources are then fine-tuned by configuring specific RAN optimization parameters. When adjusting a sensing service due to mobility (i.e., moving sensing target), nodes may need to be re-selected, and/or RAN optimization parameters need to be updated (e.g., adjusting the beam direction).

[0066] The sensing nodes transmit and receive sensing signals, which are defined as transmissions on the 3GPP radio interface that can be used for sensing purposes. Data, referred to as 3GPP sensing data, is collected from the received sensing signals. This data is derived from 3GPP radio signals impacted (e.g., reflected, refracted, diffracted) by an object or environment of interest for sensing purposes, and may be processed within the 5G system. The process of collecting sensing data is referred to as a sensing measurement process. The outcome, in terms of processed 3GPP sensing data, requested by the customer, is referred to as a sensing result.

[0067] The sensing controller entity (otherwise referred to herein as a network entity) is provided to handle the process of selecting and deselecting sensing nodes. The sensing controller entity (SenseMF) is a logical network function located at a network entity, wherein the network entity may be a single node, such as a base station, a core network node or a user equipment, or the logical network function may be distributed over a number of network nodes. The sensing controller entity may therefore be any of a RAN node, a CU-gNB, a DU- gNB, a gNB, a core network sensing function, an LMF, a selected RAN node, and a UE, or distributed over any combination of these devices. The network entity may therefore refer to a single network node or a plurality of network nodes/devices. In embodiments, the logical function spans across a 5G core network function and a gNB. A network entity appropriately configured may be said implementing the functionality of the sensing controller entity.

[0068] A sensing target may of course be mobile, and the area over which it is sensed may change with time. The set of sensing nodes initially selected for the purpose of the sensing task may become unsatisfactory with time. This may be due to movement or other change in the target, changes in the network environment, or changes at the sensing nodes of the network. In embodiments, the decision that the set of sensing nodes is unsatisfactory may be the result of one or more triggering events, wherein the triggering events may be one or more of receipt of report from a sensing node, the report comprising one or more measurements for the sensing task, a determination of the location of the target, a determination of a mobility pattern for the target, or another event which indicates to the sensing controller entity that one or more nodes may no longer be capable of implementing the sensing task or indicates to the sensing controller entity one or more nodes that are not currently involved in the sensing task may be able to perform all or part of the sensing task.

[0069] In embodiments, the decision that the first set of sensing nodes may be unsatisfactory may also be based on target characteristics wherein the target characteristic may be one or more of a sensing target area, a sensing target object description or a sensing task information, for example, Key Performance Indicators, KPI.

[0070] In embodiments, the target sensing area may be the location area of the mobility pattern of the target area. In embodiments, the sensing target object description may be an object type, an object RCS or an object mobility pattern. In embodiments, the sensing task information may include sensing key performance indicators, KPI, such as those defined in TR 22.837.

[0071] In order to address this problem and thus to maintain continuity of a sensing service, as the sensing target and/or the sensing target area moves into different location, i.e. , different area of interest, a handover procedure is provided. In particular, in the context of radio sensing procedure performed or controlled by a wireless communication network (e.g., 5GS), a handover mechanism for sensing nodes is provided. The problem is illustrated in Figures 5(a), 5(b) and 5(c).

[0072] Figures 5(a), 5(b) and 5(c) illustrate a typical scenario 500 illustrating the result of handover according to the present disclosure. Figure 5(a) illustrates a sensing controller entity, 510, with four sensing nodes, referred to as nodeA 508a, nodeB 508b, nodeC 508c, and nodeD 508d, and a sensing target 502.

[0073] The target object, 502, is to be sensed in a target area 504a. The target object is moving in a direction 506. The four sensing nodes, nodeA 508a, nodeB 508b, nodeC 508c, and nodeD 508d are in the vicinity of the target object. At an initial time t1 , in the target’s initial position, 512a, three of the nodes, nodeA, nodeB and nodeC have the capability of performing the task of sensing the target. These three nodes are therefore selected to perform the sensing task and form a first set of sensing nodes, comprising nodeA, nodeB, and nodeC. However, the target is moving, and by time t2, as shown in Figure 5(b), the target has moved to a second position 512b. The target area, 504b, has also moved. At this point, nodeA is no longer able to perform the sensing task. NodeA may be referred to as an incapable sensing node at this point. NodeD however is now capable of performing the sensing task. NodeD may be referred to as an additional node at this point. An incapable sensing node is a sensing node which is or has become, unable to meet one or more of the criteria for performing the sensing task. This may be due to one or more of: a change in relative geographical location of the sensing node and the target, the mobility pattern of the target, inability of the sensing ndoe to meet a key performance indicator, KPI, the sensing transmission not possible at a certain angular direction; the battery storage/charge level or other available energy of the sensing node being insufficient, the sensing target distance between the sensing node and the target reaching or exceeding an indicated threshold, or that any other an indicated criteria for sensing incapability is met. An additional node is one which is currently not performing a part of the sensing task, i.e. the additional node is not part of the first set. However, the additional sensing node is a node which is identified as being able to perform one or both of transmission or reception for the sensing task. The additional sensing node may be included in a second set of sensing nodes to perform the sensing task after a handover.

[0074] In the new scenario, nodeA, 508a, has been deselected from the set of sensing nodes and an additional node, nodeD, 508d, has been identified as being capable of performing the sensing task and has been selected for the sensing task. A second set of sensing nodes, comprising nodeB, nodeC and nodeD, is therefore formed.

[0075] A purpose of the present invention is to provide a mechanism for detection that a node is no longer capable of performing the sensing task and deselect that sensing node, and to identify a sensing node which has become capable of performing the sensing task, and to select this new sensing node for the sensing task. The result of this deselection and selection process is a second set of sensing nodes, which continues to perform the sensing task after the handover.

[0076] Figure 5c illustrates a further step, namely the handover of the sensing controller entity. In this scenario, control of the sensing task has been passed to a new sensing controller entity, 514.

[0077] Figure 6 illustrates another example scenario, 600, for handover. The sensing object, 602, located in area 604 and moving in a direction, 606, and is being sensed by a first set of sensing nodes 650, comprising a plurality of nodes, 602a, 602b, 602c, 604a, 604b, 606, controlled by a first sensing controller entity, 610a.

[0078] A handover takes place, after which the sensing object, 602, is being sensed by a second set of sensing nodes, 660, comprising a plurality of nodes, 652, 654, 656, controlled by a second sensing controller entity, 610b. As discussed above, a sensing controller entity may comprise a number of different network nodes. The handover of sensing controller entity may involve the handover of all of the constituent nodes, or a subset of them.

[0079] Figure 7 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a sensing controller entity according to an embodiment. In some implementations, the sensing controller may execute a set of instructions to control the function elements of the sensing controller to perform the described functions.

[0080] At step S701 , the sensing controller entity receiving from a first entity a request to perform a sensing task. The first entity may be any network node or device which either belongs to a customer or which has received instruction from a custom, or is another network entity requiring a sensing service.

[0081] In response to the request, the sensing controller entity selects, at step S702, a first set of sensing nodes to perform the sensing task. The selection comprises selection of transmitting sensing nodes and receiving sensing nodes to form a first set of sensing nodes. The selection may comprise a single node which implements both transmission and reception, or a plurality of nodes. The plurality of nodes may comprise sensing nodes which are only transmitting, sensing nodes which are only receiving, or sensing nodes which are performing both functions. The first set may comprise any combination of nodes of each type. The selection may be based on one or more of: capability information of the one or more sensing nodes, key performance indicators for the sensing task, sensing target area, a sensing target object description or a sensing task information, location of the target or determination of a mobility pattern of the target.

[0082] Once the first set of sensing nodes has been selected, at step S703, the sensing controller entity instigates the configuration of the one or more sensing nodes to perform the sensing task. The sensing controller entity sends configuration information to each node such that the nodes are configured to provide transmission of at least one sensing signal and/or reception of at least one sensing signal.

[0083] At step S704, the sensing node entity identifies a need for a handover of at least one sensing node. The identifying comprises identifying at least one of an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task. In an embodiment, this identification may be based on capability information of the at least one sensing node, at least one key performance indicator and at least one triggering event. In embodiments, the capability information may comprise a location of the sensing node, transmission and observation area and angles, a time schedule and a power level. The triggering event may be one or more of: the receipt of a report from a sensing node, a determination of location of the target or determination of a mobility pattern of the target. In an embodiment, the at least one report may comprise an incapability indicator from an incapable sensing node, wherein the incapability indicator comprises an indication of the sensing task, and a sensing configuration associated with the said sensing task. In an embodiment, the incapability indicator may comprise an indication as to whether the incapability indicator applies to transmission, reception or both. In embodiments, the report may comprise a capability indicator from an additional sensing node. As with the incapability indicator, the capability indicator may comprise an indication of the sensing task, a sensing configuration associated with the said sensing task and an an indication as to whether the capability indicator applies to transmission, reception or both.

[0084] At step S705, the handover is initiated, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or deselecting the incapable sensing node. As a result of the selecting and/or deselecting a second set of sensing nodes is formed, S706, to perform the sensing task.

[0085] Upon the reception of the sensing measurement reports from the one or more sensing nodes, the sensing controller entity identify a need to initiate a sensing node handover procedure to update the selection of the sensing nodes, in order to assist the sensing measurement process and to maintain continuity of sensing service. In an embodiment, the sensing configurations may also be adjusted.

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

[0087] In an embodiment, identifying the need for a handover operation is based on capability information of the at least one sensing node, at least one key performance indicator and at least one triggering event.

[0088] In an embodiment, identifying the need for a handover operation is based on a target characteristic, wherein the target characteristic is at least one of: a sensing target area, a sensing target object description or a sensing task information.

[0089] In an embodiment, wherein the triggering event is one or more of a determination of location of the target or determination of a mobility pattern of the target. [0090] In an embodiment, the decision to initiate handover may be based on the prior knowledge of the Sensing Controller Entity of the sensing capability of the involved sensing nodes.

[0091] In some embodiments, the Sensing Controller Entity may identify a need to initiate a sensing node handover procedure to update the selection of the sensing nodes and/or the sensing re-configurations to assist the sensing measurement process, i.e. , collect sensing data, related to a moving sensing target object or target area of interest. This information may be made available to the Sensing Controller Entity from, for example, a sensing task definition, for example, given by the service consumer, including sensing target mobility pattern, information about target area of interest for sensing, capability of sensing nodes, etc..

[0092] Figure 8 is a signaling diagram which illustrates the process of configuration, sensing, and handover, according to an embodiment. For illustrative purposes, the Sensing Controller Entity, 810, is shown as a single node, and only two sensing nodes, one sensing Tx node, 808a and one sensing Rx node, 808b are shown. The person skilled in the art would appreciate that the sensing controller entity may be distributed over a plurality of nodes, and that there may be a plurality of sensing Rx, sensing Tx and sensing nodes both transmitting and receiving.

[0093] After receipt of a request to implement a sensing task (not shown in Figure 8), theSensing Controller Entity selects the sensing Tx and sensing Rx nodes, and configures the sensing signal transmission of the sensing Tx nodes wherein the said sensing signal may be a sensing-dedicated RS, a CSI-RS, PRS, DMRS, or a physical data/control channel. The Sensing Controller Entity configures the sensing reception and measurement of the sensing Rx nodes, and sensing measurement reporting of the sensing Rx nodes.

[0094] In some embodiments, as part of the sensing measurement reporting or as a separate report configuration, the Sensing Controller Entity may select reporting configurations or configure the Sensing Rx and/or sensing Tx nodes with specific measurement types, reporting type and/or reporting occasions regarding the sensing node handover. [0095] In an embodiment, the Sensing Tx is configured with dedicated time-frequency pattern to indicate to the Sensing Controller Entity a sensing Tx incapability flag/handover request (e.g., at dedicated time occasions of first symbol of each NR subframe). In an embodiment, the Sensing Rx is configured with a dedicated time-frequency pattern to indicate to the Sensing Controller Entity a sensing Rx incapability flag/handover request. In some embodiments, the configuration of the sensing Tx/Rx nodes further include a criterion for the Sensing Tx/Rx nodes for indication of the sensing incapability message. In some other embodiments, the determination of sensing incapability of a sensing Tx or a sensing Rx node is done autonomously by the said sensing Tx or sensing Rx node.

[0096] In some embodiments, the selection and/or configuration of the sensing nodes by the Sensing Controller Entity may include selection or discovery of non-3GPP sensors, based on their known or pre-configured sensing capability information (e.g., location, orientation, sensor type (e.g., a camera), observation space (i.e. azimuth/elevation angular area with respect to a global coordinate system), non-3GPP sensing data type/format, non- 3GPP data resolution/accuracy (bitmap image of 100 by 100 pixels, with 8 bits resolution of each pixel)), selection and/or configuration of non-3GPP sensors for reporting of the non- 3GPP sensing measurements/data.

[0097] In some embodiments, the selection and/or configuration may include a set of time/frequency resources for transmission of the said report, the data type/format for transmission of the said report, a criteria for transmission of the said report (when an object is detected, or when the sensor value/magnitude has changed or fallen below/above a threshold), the contextual information to be transmitted by the sensor to the Sensing Controller Entity. In an embodiment, the non-3GPP (and/or 3GPP sensing measurement) reporting further consists of contextual information of a sensing information/data within a report and/or associated to a sensing task. In some embodiments, the contextual information comprises a timing information (indication of start and stop of a reported measurement, time instance/stamp of a reported sensing measurement, sampling rate of a reported measurement etc.), spatial information (e.g., from which angle a sensing target is observed via a camera image, relative ambient light, received to the sensor from sources other than the sensing target, etc.), a threshold and/or an event ID/description according to which the sensing information is reported to the Sensing Controller Entity. In some embodiments, the discovered/identified group of non-3GPP sensors (their ID, their address) are (upon consent of the owner of the said sensor) exposed to a sensing service consumer, facilitating the service consumer (e.g., a 3^rd party application) exchanging (e.g., sensing) information with the said sensor. In some other embodiments, the fused sensing information of the identified non-3GPP sensors and the 3GPP sensing data/measurement processed and combined within the network are exposed by the Sensing Controller Entity to the service consumer. In some embodiments, upon mobility of a (non-3GPP) sensor and/or upon mobility of a sensing target, Sensing Controller Entity may determine to discover and/or select a new non-3GPP sensor, de-select a non-3GPP sensor, or a combination thereof.

[0098] In some embodiments, the discovery and exposure of the UE (association) ID or group of UE (association) IDs or a group UE (association) ID wherein the said UEs are capable of transmitting a 3GPP or non-3GPP sensing data (temperature sensor reading, camera data) to a sensing service consumer (e.g., a trusted or untrusted 3rd party application) is triggered by a request from the said sensing service consumer received (e.g., via the NEF) by the sensing controller entity. In some examples, the UE ID are UE association IDs which are established for the communication of the consumer with one or multiple UEs via the association established through the communication system, and wherein the UEs may not be identifiable by the service consumer by the said UE ID.

[0099] In some examples, the request includes a description of the sensors (location area, e.g., given with a center and a radius, sensor type, e.g., camera, sensor capability (e.g., providing sensing data with a desired format with desired resolution and with desired rate and within a desired latency, wherein the values are described as a minimum desired value or a range of desired value or a capability class/category defined with an index from a codebook) ) to be discovered by the network and exposed to the sensing service consumer.

[0100] In some examples, when a said UE ID is no longer valid, i.e. becomes an incapable sensing node (e.g., no longer matches to the sensor description of the consumer request, e.g., due to moving outside of the area of interest for sensing) and/or when a new sensor is added/discovered according to the sensor description, the sensing controller entity and/or the entity communicating with the consumer, informs the sensing service consumer of the de-selected/invalidated sensor (a UE ID together with incapability indication), a time pattern associated with the said incapability indication (will no longer be valid for duration of A seconds starting after B seconds), a reason for the said incapability (sensor moving outside of the requested region). [0101] In some embodiment, prior to the exposure of the said UE to the service consumer, the sensing controller sends a query message to the discovered candidate UE (wherein an initial set of candidate UEs for discovery to the sensing consumer have been obtained by the sensing controller entity based on the service consumer request and the therein embedded sensor description), wherein the said query may indicate the type of the requested capability, type of the requested sensing data and/or the sensor description, the consumer/application requesting the UE ID, etc. In response to the received query, the communicated UE may provide an accept/reject response, type of the supported sensing capabilities, and the type of information about the said UE that may be exposed to the indicated sensing consumer (if the actual UE ID/number may be shared or a non-identifiable UE ID maybe shared which can be only used by the consumer to communicate to the said UE via the network interface and wherein the UE remains not-identifiable by the exposed UE ID).

[0102] Once the necessary configuration information, 820, is determined, it is sent by the sensing controller entity, 810, to the sensing Tx node, 808a, and the sensing Rx node, 808b.

[0103] After the configuration stage is complete, the sensing process begins, with sensing measurements, 830, being taken by the sensing Rx node, 808r. These measurements are reported to the Sensing Controller Entity, 810.

[0104] The sensing Rx nodes report, 840, the obtained sensing measurements and/or sensing Tx nodes report when they detect that areas incapable of performing sensing transmission, according to the configuration received from the Sensing Controller Entity. In some embodiments, the report includes sensing node Handover-specific reports, according to the received configurations by the Sensing Controller Entity, wherein a sensing node HO decision of the said sensing node is made at the Sensing Controller Entity, at least part, based on the received Handover -specific report of the said sensing (sensing Tx or sensing Rx) node. The Handover-specific reports may include sensing Tx incapability flag/Handover request or sensing Rx incapability flag/ Handover request. In some embodiments, the sensing incapability indication of a sensing Tx/Rx node, further includes a time pattern (e.g., a time duration from which the sensing operation is not feasible for the node) and/or a reason forwhich the sensing operation of the said node is no longer feasible. In some embodiments, any of the handover-specific reports of the sensing Tx/Rx nodes are generated/determined by the sensing Tx/Rx nodes autonomously, or according to the received configuration from the Sensing Controller En, or a combination thereof.

[0105] In some embodiments, the Sensing Controller Entity configures the sensing Tx and/or sensing Rx nodes with time occasions for transmission of sensing handover-specific reports. The sensing Tx and/or Rx nodes may then determine (autonomously, or according to the received criteria for determination of sensing Tx/Rx incapability) the sensing Tx/Rx incapability condition. Upon such determination, the sensing Tx/Rx node shall locate a closest handover-specific reporting occasion. In an embodiment, an alternative is to select an occasion according to an indicated criteria for occasion selection, e.g., a closest occasion after 1 msec or an occasion within 1 msec of detection of sensing Tx/Rx incapability. The period of 1 msec is not limiting, and the person skilled in the art will appreciate that other time periods may be selected.

[0106] In some embodiments, the Sensing Controller Entity determines that a handover is required for one or multiple of a sensing Rx node, sensing Tx node, or a combination thereof, based on the received report of the sensing Tx nodes. These may be, in embodiments, an incapability indication of a sensing Rx node when they detect that are incapable of performing sensing transmission, one or more received report of the sensing Rx nodes, a prior estimate or knowledge of the capability of any of the one or more sensing Tx nodes or sensing Rx nodes. In embodiments, this may include a location, the area that can be sensed by a sensing Rx node, area that can be illuminated by a sensing Tx node, the position and/or mobility pattern of the sensing target or target area, the known radar cross-section or radar cross section related information of a sensing target, or a combination thereof.

[0107] After the determination that a handover is required, 850, a determination, 860, of the required updates to the configurations of the one or more sensing nodes is made. In some embodiments, the Sensing Controller Entity determines a new set of sensing Tx nodes (potentially including all or a subset of the previously active nodes acting as sensing Tx nodes), a new set of sensing Rx nodes (potentially including all or a subset of the previously active nodes acting as sensing Rx nodes), new configurations for sensing Tx and Rx nodes or a combination thereof, wherein the sensing Rx node may be a 3GPP radio sensing signal receiver (for measurement, processing) node, or a non-3GPP sensor, obtaining non-3GPP sensing data, processing non-3GPP sensing data, and reporting the obtained non-3GPP sensing data, or a combination thereof. [0108] Once a determination has been made of the new set of sensing nodes and their respective configurations, this information is sent, 870, to respective sensing nodes of the new set.

[0109] In some embodiments, upon determination of a sensing node handover, the sensing node handover comprises the Sensing Controller Entity configuring one or multiple sensing Rx or Tx nodes for addition to the sensing measurement process (upon selection and/or discovery of the said sensing nodes), for re-selection from the sensing measurement process, for de-activation of the sensing measurement process, for configuration modification (e.g., with an updated configuration or configuration parameters for update of the previous configuration) for a sensing measurement process, or a combination thereof.

[0110] In some embodiments, only one sensing de-selection level is defined for a sensing node. In other some embodiments, the indication a node de-selection may be accompanied with the indication of a de-selection level, wherein the de-selection level indicates the functionalities that a sensing (Tx/Rx) node shall be able to support after deselection from a sensing task, e.g., a de-selection level may define if a sensing Tx/Rx node shall transmit measurement reports, keep the configuration and provisioned resources, be able to resume the sensing measurements and/or reporting process after an indicated/fixed delay (e.g., 2 msecs), or if a sensing Tx/Rx node does not need to maintain the collected measurement, configuration information and resources, and may release the related resources to the associated sensing task. The person skilled in the art would appreciate that 2 ms is an example, and the invention is not limited to any given delay.

[0111] In some embodiments, the said de-selection level is communicated via an index from a codebook, wherein the said codebook comprising different combination of a sensing Tx/Rx node operation/function after de-selection. In one example, an index “1” for a sensing Rx node indicates that the nodes may release its resources associated to an indicated sensing task, and after an indicated time duration. In some other embodiments, the codebook may as well include timing information for one or multiple supported functionalities of a sensing Tx/Rx node. E.g., an index “2” for a sensing Tx node may indicate that the sensing signal transmission is not needed after 2 msecs, however, the sensing configuration and sensing context information shall be preserved by the sensing Tx node such that, upon indication, the said sensing Tx node shall be able to resume transmission of the said sensing signal. [0112] In some embodiments, when a sensing Tx/Rx node (or a non-3GPP sensor node, or a UE/RAN node associated to the said non-3GPP sensor) is de-selected (associated to a sensing task), it is not expected/shall not (in some embodiments, based on an indicated de-selection level) to perform sensing transmission of an associated sensing task/configuration, reception and/or measurement of a sensing signal associated to a sensing task/configuration, reporting of the obtained sensing measurements, maintaining sensing context associated to a sensing task (e.g., configuration parameter, stored previous measurements and related/assisting information of the associated sensing task), or a combination thereof.

[0113] In some embodiments, a de-selection indication to a sensing Tx/Rx node further includes an indication of one or multiple time reference/durations after which the sensing Tx/Rx node is de-selected from a configured operation. In one example, a sensing Rx node is configured with a de-selection from the previously configured sensing measurement task, wherein the de-selection configuration comprises a first time reference from which the sensing Rx node is not required to report back the sensing measurements, and a second time reference after which the sensing Rx node is not required to receive/store/measure the configured received signal, and a third time reference after which the sensing Rx node may release (utilize the said resources for another purpose) its configured sensing resources, the collected sensing measurements and the sensing context information, or a combination thereof.

[0114] Within the relevant embodiments of this disclosure, the term “de-activation” can be interpreted both as de-selection, or as a specific type of a de-selection activity, wherein the sensing node is not required to transmit a sensing signal, receive a sensing signal, transmit sensing report, perform sensing measurement and/or computations, however, the sensing node is expected to maintain the context information (e.g., previously stored measurement, and assisting information), configuration parameters of the configured sensing operation (transmission, reception, measurement and reporting or a combination thereof).

[0115] Figure 9 is a signaling diagram illustrating the handover of a sensing Rx node, according to an embodiment. The scenario involves a Sensing Controller Entity, 910, a source Rx, 908r-1 , a target Rx, 908r-2 and a plurality of other sensing nodes, 9081 , 9081 The person skilled in the art would appreciate that the sensing controller entity may be distributed over a plurality of nodes, and that there may be a plurality of sensing Rx, sensing Tx and sensing nodes both transmitting and receiving.

[0116] As before, the stages of the procedure are the configuration of the sensing nodes, 920, the taking of sensing measurements, 930 and the reporting, 940. A handover decision, 950, may be made, at least in part due to the reporting. These stages are similar to the corresponding stages described above. The sensing measurements (to collect sensing data) are conducted at the sensing Rx and/or Sensing Tx nodes, according to the Sensing Controller Entity configurations and wherein the sensing measurements are collected by the Sensing Controller Entity.

[0117] The Sensing Controller Entity configures the Sensing Tx and Sensing Rx nodes for performing sensing signal transmission, measurements, and reporting. In some embodiments, the reporting configurations of a sensing Rx node includes a reporting condition/event (e.g., to trigger a sensing incapability indication by the sensing Rx node). In some embodiments, the said reporting condition includes at least one or multiple/combination of: a) The Reference Signal Received Power Path, RSRPP, of a path associated with the sensing measurement of the Sensing Rx node falls below an indicated threshold, wherein the threshold is indicated as an absolute (power/energy) value or a relative (power/energy of the path the power/energy of the other paths satisfying a condition). b) One or multiple time durations that an indicated condition shall hold, e.g., a time duration for which the RSRPP of a path (or multiple or sum RSRPP of paths associated to a condition) remains below a threshold. c) A decreasing pattern of a sensing measurement quality metric according to an indicated pattern (e.g., RSRPP of paths associated to the configured sensing tasks are decreasing with an indicated rate of 1 energy/power unit per frame duration or per-measurement). d) Insufficient processing power of the Sensing Rx node for a configured sensing measurement, wherein the insufficient processing power may be determined autonomously by the UE and/or according to an indicated maximum processing time for the UE to generate a requested report and/or to perform a configured measurement. e) Configured Sensing Rx measurements is no longer feasible (may include a time pattern or additional info), wherein the said infeasibility of the Sensing Rx measurement is determined autonomously by the said sensing Rx node. f) Indication of number of detected conditions as described in a-e or a combination thereof as a counter threshold (e.g, the RSRPP of the desired path falls below an indicated threshold and remains such for 1 msec for at least 10 times within the last 10 secs. The person skilled in the art will appreciate that these figures represent just one option and the invention is not limited to any specific time intervals).

[0118] In an embodiment, a Sensing Rx node is indicated to report to the Sensing Controller Entity if the sum RSRPP of the paths associated to the configured sensing task (e.g., according to a permissibility condition of an azimuth and elevation angular range and a Doppler shift range) divided by the sum RSRPP of the paths fulfilling a second permissibility condition (e.g., all paths, or paths within a wider angular range) falls below an indicated threshold, and remains below the threshold for 50 msecs. The person skilled in the art will appreciate that this figure represents just one option and the invention is not limited to any specific time interval.

[0119] In some embodiments, the Sensing Tx and/or Rx nodes send (upon configuration, or upon autonomous determination, or a combination thereof) indication of the sensing capability/incapability associated to a configured sensing task, wherein the capability indication may include an indication that a sensing Tx node or a Sensing Rx node may not continue performing the configured sensing measurements. In some embodiments, the said indication is accompanied with a reference time in the future or in the past from which the incapability is valid/expected, one or multiple reasons for the said incapability, or a combination thereof. In one example, a Sensing Tx node indicates to the Sensing Controller ENtity that the sensing transmission may not be feasible after 1 msec and due to the resource (e.g., power) restrictions. The person skilled in the art will appreciate that this figure represents just one option and the invention is not limited to any specific time interval. The person skilled in the art would appreciate that 1 ms is an example, and the invention is not limited to any given time. In an embodiment, a Sensing Rx node indicates to the Sensing Controller Entity that the sensing measurement may not be feasible due to the expected object distance from the Sensing Rx node location and/or the observed degrading RSRPP of the path associated to the sensing target area. In some embodiments, the capability indication of the sensing Tx and/or Rx nodes is accompanied with a time pattern, for example, sensing Tx/Rx is not feasible from now, or after 1 sec. The person skilled in the art will appreciate that this figure represents just one option and the invention is not limited to any specific time interval. The person skilled in the art would appreciate that 1 ms is an example, and the invention is not limited to any given time.

[0120] In some embodiments, the incapability indication of a sensing Tx or Rx node may be accompanied with a reason indicating blockage of observation of the sensing area (e.g., by an external/non-target object).

[0121] The Sensing Controller Entity determines that a Sensing Rx handover is needed. In some embodiments, the handover decision is made based on the reports of the Sensing Rx nodes, report of the Sensing Tx nodes, Sensing Controller Entity knowledge of the target sensing area location and the Sensing Rx location and sensing capabilities (target areas for which the sensing Rx node may perform Sensing Rx measurements). In one example, a Sensing Rx handover decision is made based on a change in the Sensing Tx node and that the Sensing Rx node is not capable of sensing measurements based on the transmission of the new Sensing Tx node or due to an obstacle placed in between.

[0122] The Sensing Controller Entity identifies new Sensing Rx nodes and requests/configures or adjusts the configuration of the identified Sensing Rx nodes to perform sensing measurements. In some embodiments, the newly-selected/candidate Sensing Rx nodes may indicate their sensing measurement capability, 960, to the Sensing Controller Entity and/or issue a response (positive/negative/negative with reasons) regarding the acceptance of the sensing measurements configurations. In some embodiments, the configuration of the sensing Rx nodes, includes: a. All or subset of the measurements of the previous/other Sensing Rx nodes. b. The current target object or location area and the expected movement pattern/velocity/direction of the sensing target object or target area. c. A relative RSRPP of the one or multiple paths related to the target area (or satisfying a sensing target condition) for sensing with respect to the paths satisfying certain conditions (within a specific angular range or area). d. The pattern of adjustment or modifications of the one or multiple Sensing Rx measurements. e. Positioning information of a sensing Rx node (location, velocity etc., according to a global or known coordinate system). f. Beam information (beam angle or beam width).

[0123] The Sensing Controller Entity indicates to the Sensing Rx nodes (for which the handover decision is made) a Sensing Rx handover indication, 960. A release message, 970, is sent to the sensing Rx to be deselected. In some embodiments, a sensing Rx handover indication may include

(i) De-selection/de-activation of a Sensing Rx measurements (nevertheless, the configured Sensing Rx resources and configurations are maintained by the Sensing Rx node and may be re-activated and re-utilized for future sensing measurements in the future, e.g., upon indication by the Sensing Controller ENtity at a future, or according to a criteria when it is met, wherein the criteria is indicated by the Sensing Controller ENtity).

(ii) De-selection/de-activation of the Sensing Rx measurement reporting (nevertheless, the Sensing Rx node may still continue the sensing measurements, or part of the sensing measurements as configured).

(iii) Release of the resources and de-selection of the Sensing Rx node, wherein the Sensing Rx node no-longer required to perform sensing Rx measurements and the configured resources may be utilized for other purposes.

(iv) The sensing Rx node continues the measurements and reporting but with an at least partially new configuration. In some examples, a new Sensing Rx node may be further added to the already configured sensing Rx measurement nodes.

[0124] In some embodiments, in addition to the de-selection/de-activation of a sensing Rx node and addition of a new sensing Rx node, the Sensing Controller Entity updates the configuration (e.g., transmission power, RS parameters, beam direction/width, etc.) of the other Sensing Tx and/or Sensing Rx nodes (other than the nodes which are newly added or de-selected/de-activated), in order to adjust the sensing measurement setup to satisfy the required sensing KPIs. [0125] After the handover is complete, sensing measurements, 980 are performed based on the new/updated configurations and based on the transmission of sensing signal by the Sensing Tx nodes and reception and measurement of the sensing signal by the Sensing Rx nodes (including the newly added Sensing Rx nodes). Sensing measurements based on the received/updated configurations are reported, 990, to the Sensing Controller Entity.

[0126] Figure 10 is a signaling diagram illustrating the handover of a sensing Tx node, according to an embodiment. The scenario involves a Sensing Controller Entity, 1010, a source Tx, 1008r-1 , a target Tx, 1008r-2 and a plurality of other sensing nodes, 1008r, 1008t. The person skilled in the art would appreciate that the sensing controller entity may be distributed over a plurality of nodes, and that there may be a plurality of sensing Rx, sensing Tx and sensing nodes both transmitting and receiving.

[0127] As before, the stages of the procedure are the configuration of the sensing nodes, 1020, the taking of sensing measurements, 1030 and the reporting, 1040. A handover decision, 1050, may be made, at least in part due to the reporting. These stages are similar to the corresponding stages described above, the sensing measurements (to collect sensing data) are conducted at the sensing Rx and/or Sensing Tx nodes, according to the Sensing Controller Entity configurations and wherein the sensing measurements are collected by the Sensing Controller Entity.

[0128] The Sensing Controller Entity indicates to the Sensing Tx nodes (for which the HO decision is made) a Sensing Rx handover indication, 1060. A release message, 1070, is sent to the sensing Rx to be deselected.

[0129] After the handover is complete, sensing measurements, 1080 are performed based on the new/updated configurations and based on the transmission of sensing signal by the Sensing Tx nodes and reception and measurement of the sensing signal by the Sensing Rx nodes (including the newly added Sensing Rx nodes). Sensing measurements based on the received/updated configurations are reported, 1090, to the Sensing Controller Entity

[0130] In some embodiments, the Sensing Tx node further (upon configuration of Sensing Controller Entity) reports on the capability of the Sensing Tx node for transmission of the sensing signal, e.g., on the expected transmission capability, including transmission power, transmission coverage area and/or angular (azimuth/elevation) support, and the supported beamwidth within the said coverage area. In some embodiments, a sensing Tx node may indicate a Sensing Tx incapable flag to the Sensing Controller ENtity, indicating that the configured sensing Tx operation is not supported. In some embodiments, the Sensing Tx incapable flag further contains a timing information (e.g., the Sensing Tx operation is no longer possible after 100 msec, or a supported comb size or transmission periodicity that differs from the configured one), and/or a reason for incapability (the sensing target object is out of coverage, lack of energy/battery, etc.). In some embodiments, the sensing Tx incapability is determined by the Sensing Tx node autonomously, or according to the received configuration by the Sensing Controller Entity, including a criterion for a sensing Tx incapability determination (when the distance to the sensing target exceeds an indicated threshold, or when the available energy/battery resource is below an indicated threshold). In some embodiments, the reason for Sensing Tx incapability is indicated to the Sensing Controller Entity via an index from a codebook, wherein the codebook includes the reasons for the determined incapability.

[0131] The Sensing Controller Entity determines that a Sensing Tx handover is needed. In some embodiments, the handover decision is made based on the reports of the Sensing Rx nodes, report of the Sensing Tx nodes, the Sensing Controller Entity knowledge of the target sensing area location and the Sensing Tx (and potentially Sensing Rx) nodes’ location and sensing capabilities (target areas for which the sensing Rx node may perform Sensing Rx measurements).

[0132] In one example, a Sensing Tx handover decision is made when multiple of Sensing Rx nodes fails to perform sensing based on the configured sensing signal transmission of the Sensing Tx node, or when one or multiple attempts for recovery of a transmission beam for sensing fails at the sensing Tx node.

[0133] The Sensing Controller Entity identifies new Sensing Tx node(s) and requests/configures the identified Sensing Tx nodes to perform sensing signal transmission. In some embodiments, the newly-selected/candidate Sensing Tx nodes may indicate their capability to the Sensing Controller ENtity and/or issue a response (positive/negative/negative with reasons) to the Sensing Controller ENtity regarding the acceptance of the sensing signal transmission configurations. [0134] The Sensing Controller Entity indicates to the Sensing Tx nodes (for which the handover decision is made) a Sensing Tx handover indication. In some embodiments, a sensing Tx handover indication may include: a. De-selection/de-activation of a Sensing Tx transmissions (nevertheless, the configured Sensing Tx resources and configurations are maintained by the Sensing Tx node and may be re-activated and re-utilized for future sensing measurements, e.g., upon future indication by the Sensing Controller ENtity, upon an indicated distance threshold between the sensing Tx node and the sensing target area, etc.), b. De-selection/de-activation of a sensing Tx node including release of the resources and de-selection of the Sensing Tx node, wherein the Sensing Tx node no-longer required to perform sensing transmissions and the configured resources may be utilized for other purposes

[0135] The sensing Tx node continues the sensing signal transmission (and reporting, if configured) but with an at least partially new configuration (updated RS configuration parameters, transmission power, transmission beam [e.g., beam direction, beam width etc]). In some examples, a new Sensing Tx node may be further added to the already configured sensing Tx measurement nodes.

[0136] In some embodiments, in addition to the de-selection/de-activation of a sensing Tx node and addition of a new sensing Tx node, Sensing Controller ENtity updates configuration of the other Sensing Tx and/or Sensing Rx nodes (other than the nodes which are newly added or de-selected/de-activated), in order to adjust the sensing measurement setup to satisfy the required sensing KPIs. In some embodiments, the said adjustment may include a new configuration, or modification of a subset of the configuration parameters.

[0137] In some embodiments, the Sensing Controller ENtity configuration of the sensing measurement process includes one or multiple of a sensing configuration group, wherein each configuration group includes: a. One or multiple of a Sensing Tx nodes configured by the Sensing Controller ENtity for transmission of a sensing signal. b. One or multiple of a Sensing Rx nodes configured by the Sensing Controller ENtity for reception and measurement and reporting of a sensing signal. c. A sensing group ID identifying the group of respective configured nodes and sensing transmission, reception and reporting configurations.

[0138] According to this embodiment, a sensing configuration group, associated with the said group ID can be activated and de-activated by the Sensing Controller Entity, according to the identified target area of sensing and the suitability of the said configuration group for sensing of the said target area and/or the reports of a sensing configuration group (e.g., from the Sensing Rx nodes of a sensing configuration group associated with the said group ID). The group ID in some embodiments can be the set of sensing Tx/Rx nodes associated, i.e. , pre-configured, with a Sensing Controller Entity considering the coverage area of the Sensing Controller Entity in terms of a set of cells or tracking areas. In other embodiments the group ID can represent a subset of the sensing Tx/Rx nodes associated, i.e., pre-configured, with a Sensing Controller Entity.

[0139] In some embodiments, maximum one sensing configuration group is active at each time. In some other embodiments, multiple sensing configuration groups may be active at the same time wherein the resources for sensing signal transmission, reporting, of multiple groups are multiplexed in time (over different slots, different symbols), or in frequency domain (e.g., different RE, PRBs).

[0140] In some embodiments, one node (e.g., a UE, a TRP) may belong to one sensing configuration group or no sensing configuration group at the same time. In some other embodiments, one node may belong to multiple sensing configuration group at the same time.

[0141] In some embodiments, the configuration of a node of a sensing configuration group may be implemented in multiple steps, wherein at least one step includes common configuration parameters associated to a sensing task (which is common among multiple nodes), and another step includes dedicated configuration parameters of the said sensing task for the said node. In some embodiments, the common configuration parameters of a sensing configuration group comprise: a. Configuration parameters (or a subset thereof) of a sensing signal (including time-frequency resources, sequence generation parameters, physical resource mapping). b. Target sensing object or target sensing area according to a global or a known coordinate system by the group. c. The sensing target assistance information (target size, RCS information, velocity, orientation, direction of movement, etc.). d. The measurement configuration parameters (or a subset thereof common to the group of nodes). e. The sensing measurement process (including transmission and reception/measurement of the sensing signal) activation, deactivation control command. f. A criterion for sensing measurement process activation/deactivation or adjustment of configuration within the group of nodes belonging to the said sensing configuration group (e.g., distance of the target area greater than an indicated distance threshold).

[0142] Common reporting configuration parameters, e.g., type of the measurements, reporting periodicity/density, a common/joint reporting at a shared RE configuration (e.g., wherein the nodes detecting an event, based on an indicated event detection configuration, are configured to transmit a report signal on a shared RE and wherein the generated report signaling of each node is generated based on a common strategy/configuration by each node from the obtained measurements of the said node).

[0143] In some embodiments, the activation/deactivation of a sensing configuration group is done explicitly, via a group common/multi-cast signaling. In some other embodiments, the activation/deactivation of a group is performed individually, e.g., when a sensing Rx node is added/removed from the sensing configuration group via a dedicated signaling/configuration message.

[0144] In some embodiments, the activation/deactivation of a sensing configuration group is done implicitly, based on a previously configured criterion. In some implementations, the Sensing Controller Entity periodically updates and/or adjusts the sensing configuration group with the potential spatial information of a potential sensing target, and a sensing configuration group is activated/de-activated if the indicated center of potential sensing target area is outside of the coverage area of the sensing configuration group and wherein the coverage area of a sensing configuration group is previously indicated to the sensing nodes of the said configuration group.

[0145] In some embodiments, the configuration of the sensing configuration group, the common configuration signaling, group activation/deactivation are done via a multi-cast signaling between the Sensing Controller Entity and the sensing Tx, Rx nodes. When Sensing Tx and Rx nodes (or a subset of nodes within the group) are UEs, the multi-cast signaling, in some implemented, as DCI with CRC scrambled as group common RNTI. In some embodiments, the common configuration/control messages are scrambled/encrypted (in all or in part) by a group common RNTI, encryption key, etc.

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

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

[0148] 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. [0149] 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.

[0150] 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 200 may act as a sensing controller entity and be configured to support a means for configuring at least one sensing node to perform a sensing task to sense a target in an environment of the at least one sensing node by way of (i) transmission from the at least one sensing node of at least one sensing signal and (ii) reception at the at least one sensing node of at least one sensing signal; receiving one or more reports in connection with the sensing task from the at least one sensing node; determining that handover of management of the sensing task is necessary; transmitting information associated with the sensing task to enable management of the sensing task by a further sensing controller entity

[0151] The UE 1100 may also be configured to support a means for receiving configuration instructions from a network entity for a sensing task, sensing, based on the configuration instructions, a target in an environment of the sensing node by way of reception at the sensing node of at least one sensing signal and reporting one or more sensing measurements to the network entity;

[0152] The UE is further configured to report one or more sensing measurements to the network entity station, receive a deselection indication from the network entity and stopping the sensing and measurement reporting in response to a de-selection indication received from the network entity. [0153] In an embodiment, the UE may be further configured to receive from the network entity one or more incapability criteria determine whether the node is incapable of performing the sensing task based on the at least one sensing measurement and the one or more incapability criteria; and report an incapability indicator to the network entity if the sensing node is determined to be incapable of performing the sensing task based on the incapability criteria.

[0154] In another embodiment, the UE may be further configured to act as a transmitter sensing node, being configured to receive configuration instructions from a network entity for a sensing task, transmit from the sensing node at least one sensing signal to a target in an environment of the sensing node, based on the configuration instructions, transmit one or more reports associated with the transmission of the at least one sensing signal, receive a deselection indication from the network entity, and stop the transmission of the at least one sensing signal in response to the de-selection indication.

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

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

[0157] 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. [0158] 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.

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

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

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

[0162] The controller 1202 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1204 and determine subsequent instruction(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.

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

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

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

[0166] 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 configuring at least one sensing node to perform a sensing task to sense a target in an environment of the at least one sensing node by way of (i) transmission from the at least one sensing node of at least one sensing signal and (ii) reception at the at least one sensing node of at least one sensing signal, obtaining one or more reports in connection with the sensing task from the at least one sensing node; determining that handover of management of the sensing task is necessary, and outputting information associated with the sensing task to enable management of the sensing task by a further sensing controller entity in place of the sensing controller entity.

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

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

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

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

[0171] 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 from a first entity a request to perform a sensing task, determining a first set of at least one sensing node to perform a sensing task, configuring the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of: a. transmission from the at least one sensing node of at least one sensing signal; and b. reception at the at least one sensing node of at least one sensing signal, identifying a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task, initiating a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or de-selecting the incapable sensing node, wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task.

[0172] In an embodiment, the network entity is further configured to identify the need for a handover operation based on one or more of a capability information of the at least one sensing node, a sensing target area location information and/or mobility pattern, at least one key performance indicator and at least one triggering event, or a combination thereof.

[0173] In an embodiment, the network entity is further configured to identify the need for a handover operation is based on a target characteristic, wherein the target characteristic is at least one of: a sensing target area, a sensing target object description or a sensing task information.

[0174] In an embodiment, the triggering event is one or more of a determination of location of the target or determination of a mobility pattern of the target.

[0175] In an embodiment, network entity is further configured to: a. receive at least one report in connection with the sensing task from one of the at least one sensing node; and b. identify the need for a handover wherein at least one of the at least one triggering events is the at least one report.

[0176] In an embodiment, the at least one report comprises an incapability indicatorfrom an incapable sensing node ora capability indicatorfrom an additional sensing node, wherein the sensing incapability or capability indication comprises an indication of a sensing task, and a sensing configuration associated with the said sensing task. [0177] In an embodiment, the incapability indicator and/or the capability indicator of a sensing node comprises an indication of one or more capability or incapability types, wherein each capability or incapability type is identified by a respective index of a plurality of indices corresponding to respective types, the indices being stored in a look-up table.

[0178] In an embodiment, the capability type and/or incapability type is one of:

(i) a sensing transmission is not possible at a certain angular direction;

(ii) a battery storage is low,

(i) a sensing target distance has reached an indicated threshold, or (iv) an indicated criteria for sensing incapability is met.

[0179] In an embodiment, the capability indication and/or the incapability indicator comprises timing information indicating a start time and a stop time for the respective capability or incapability type for the sensing node.

[0180] In an embodiment, the network entity is further configured to provide configuration information for the at least one sensing node comprising one or more of: a. timing requirements for reporting of the incapability indicator or the capability indicator; b. time and/or frequency resources for transmitting the incapability and/or capability indicator; c. one or more criteria for determining incapability of a sensing node.

[0181] In an embodiment, the network entity is further configured to supply one or more selection and/or deselection thresholds for determination of capability or incapability to the at least one sensing node.

[0182] In an embodiment, the network entity is further configured to supply the one or more selection and/or deselection thresholds to the sensing nodes by supplying one or more respective indices from a codebook, wherein the respective indices represent pre-defined selection and /or deselection thresholds stored in the codebook.

[0183] In an embodiment, the network entity is further configured to supply to the sensing node pattern and/or timing information comprising one or more of: a de-selection start time for an indicated de-selection, a time duration for which the indicated de-selection, and a maximum time duration, after which a de-selected sensing node shall perform sensing measurement and report the obtained sensing measurements upon receiving an indication from the network entity. [0184] In an embodiment, the network entity is further configured to supply to the at least one sensing node a first time information associated with a first de-selection level and a second time-information associated with a second de-selection level.

[0185] In an embodiment, the network entity is further configured to perform de-selection of the at least one sensing node based on a common indication (among plurality of the sensing nodes) of a sensing target area according to a known coordinate system and a distance compared with a threshold of the sensing node to the indicated target area.

[0186] In an embodiment, the network entity comprises one or more of: a base station, a core network entity or a user equipment, UE, and the at least one sensing node is one or a UE, a radio access network, RAN, node or a non-3GPP sensor.

[0187] The NE 400 may act as a sensing controller entity and be configured to support a means for configuring at least one sensing node to perform a sensing task to sense a target in an environment of the at least one sensing node by way of (i) transmission from the at least one sensing node of at least one sensing signal and (ii) reception at the at least one sensing node of at least one sensing signal; receiving one or more reports in connection with the sensing task from the at least one sensing node; determining that handover of management of the sensing task is necessary; transmitting information associated with the sensing task to enable management of the sensing task by a further sensing controller entity.

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

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

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

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

Claims

CLAIMS 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 from a first entity a request to perform a sensing task; determine a first set of at least one sensing node to perform a sensing task; configure the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of:

(i) transmission from one or more of the at least one sensing node of at least one sensing signal; and

(ii) reception at one or more of the at least one sensing node of at least one sensing signal; identify a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node, which is not a member of the first set, to be added to the sensing task: initiate a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or de-selecting the incapable sensing node; wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task. The network entity according to claim 1 , further configured to identify the need for a handover operation based on one or more of a capability information of the at least one sensing node, a sensing target area location information and/or mobility pattern, at least one key performance indicator and at least one triggering event, or a combination thereof. The network entity according to claim 2, further configured to identify the need for a handover operation is based on a target characteristic, wherein the target characteristic is at least one of: a sensing target area, a sensing target object description or a sensing task information. The network entity according to claim 2 or claim 3, wherein the triggering event is one or more of a determination of location of the target or determination of a mobility pattern of the target. The network entity according to any of claims 2 to 4, wherein network entity is further configured to:

(ii) identify the need for a handover wherein at least one of the at least one triggering events is the at least one report. The network entity according to claim 5, wherein the at least one report comprises an incapability indicator from an incapable sensing node or a capability indicator from an additional sensing node, wherein the sensing incapability or capability indicator comprises an indication of a sensing task, and a sensing configuration associated with the said sensing task. The network entity according to claim 6, wherein the incapability indicator and/or the capability indicator of a sensing node provides an indication as to whether the incapability indicator and/or the capability indicator applies to transmission, reception or both. The network entity according to claim 6 or claim 7, wherein the incapability indicator and/or the capability indicator of a sensing node comprises an indication of one or more capability or incapability types, wherein each capability or incapability type is identified by a respective index of a plurality of indices corresponding to respective types, the indices being stored in a look-up table, and, wherein, optionally, the capability type and/or incapability type is one or more of:

(i) an indication that sensing transmission is not possible at a certain angular direction;

(ii) an indication that battery storage and/or charge is low,

(iii) an indication that a sensing target distance has reached an indicated threshold, or

(iv) an indicated criterion for sensing incapability is met. The network entity according to any of claims 6 to 8, wherein the capability indicator and/or the incapability indicator comprises timing information indicating a start time and a stop time for the respective capability or incapability type for the sensing node. The network entity according to any of claims 6 to 9, further configured to provide configuration information for the at least one sensing node comprising one or more of: a. timing requirements for reporting of the incapability indicator or the capability indicator; b. time and/or frequency resources for transmitting the incapability and/or capability report; c. one or more criteria for determining incapability of a sensing node. The network entity according to claim 10, further configured to supply the one or more selection and/or deselection levels to the sensing nodes by supplying one or more respective indices from a codebook, wherein the respective indices represent pre-defined selection and /or deselection levels stored in the codebook. The network entity according to any preceding claim, further configured to supply to the sensing node pattern and/or timing information comprising one or more of: a. a de-selection start time for an indicated de-selection; b. a time duration for which the indicated de-selection; and c. a maximum time duration, after which a de-selected sensing node shall perform sensing measurement and report the obtained sensing measurements, upon receiving an indication from the network entity. The network entity according to any of claim 11 or claim 12, further configured to supply to the at least one sensing node a first time information associated with a first de-selection level and a second time-information associated with a second de-selection level. The network entity according to any of claims 11 to 13, further configured to perform de-selection of the at least one sensing node, from the first set of sensing nodes, based on a common indication of a sensing target area according to a known coordinate system and a distance compared with a threshold of the sensing node to the indicated target area. The network entity according to any preceding claim, wherein the network entity comprises one or more of: a base station, a core network entity or a user equipment, UE, and the at least one sensing node is one or a UE, a radio access network, RAN, node or a non-3GPP sensor. The network entity according to any preceding claim, further configured to communicate to an at least one incapable nodes, when performing deselection of the incapable sensing node, one or more de-selection levels from a plurality of deselection levels, wherein the plurality of deselection levels comprises: a. an indication to the at least one incapable sensing node not to further report configured sensing measurements; b. an indication to the at least one incapable sensing node not to transmit the sensing signal; c. an indication to the at least one incapable sensing node that the incapable sensing node may re-use assigned resources for sensing transmission, reception, and measurements for other purposes; d. an indication to the at least one incapable sensing node that the incapable sensing node is not required to retain context information of the sensing task, and the configuration information and parameters of sensing measurement associated to the sensing task; e. an indication to the at least one incapable sensing node that the incapable sensing node is required to perform and/or re-transmit sensing measurement reports of the sensing task/configuration within an indicated/agreed time latency, upon future indication of the sensing controller entity. ethod performed by a sensing controller entity comprising: receiving from a first entity a request to perform a sensing task; determining a first set of at least one sensing node to perform a sensing task; configuring the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of:

(ii) reception at one or more of the at least one sensing node of at least one sensing signal; identifying a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task: initiating a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or de-selecting the incapable sensing node; wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task. rocessor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive from a first entity a request to perform a sensing task; determine a first set of at least one sensing node to perform a sensing task; configure the at least one sensing node to perform the sensing task to sense a target in an environment of the at least one sensing node by way of:

(ii) reception at one or more of the at least one sensing node of at least one sensing signal; identify a need for a handover operation of at least one sensing node, wherein the identifying comprises identifying at least one of: an incapable sensing node which is unable to perform the sensing task, or an additional sensing node which is not a member of the first set to be added to the sensing task: initiate a handover, wherein the handover comprises at least one of: selecting and configuring for the sensing task the additional sensing node; or de-selecting the incapable sensing node; wherein the selecting and/or deselecting provides a second set of sensing nodes to perform the sensing task.

19. A sensing node 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 sensing node to: receive configuration instructions from a network entity for a sensing task; sense, based on the configuration instructions, a target in an environment of the sensing node by way of reception at the sensing node of at least one sensing signal; report one or more sensing measurements to the network entity; receive a deselection indication from the network entity; and stop the sensing and measurement reporting in response to the deselection indication. sensing node of claim 19, further configured to: receive from the network entity one or more incapability criteria; determine whether the node is incapable of performing the sensing task based on the at least one sensing measurement and the one or more incapability criteria; and report an incapability indicator to the network entity if the sensing node is determined to be incapable of performing the sensing task based on the incapability criteria.