WO2024099604A1

WO2024099604A1 - Sensing task handover

Info

Publication number: WO2024099604A1
Application number: PCT/EP2023/070509
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-25
Publication date: 2024-05-16

Abstract

Various aspects of the present disclosure relate to a method performed by sensing controller entity comprising: 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 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; 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; and transmitting information associated with the sensing task to enable management of the sensing task by a further sensing controller entity.

Description

SENSING TASK HANDOVER

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to handover of management of a sensing task.

BACKGROUND

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

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

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

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

[0006] Some implementations of the method and apparatuses described herein may further include a base station for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: configure 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 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; receive one or more reports in connection with the sensing task from the at least one sensing node; determine that handover of management of the sensing task is necessary; transmit information associated with the sensing task to enable management of the sensing task by a further base station in place of the base station.

[0007] The base station may receive a sensing task request from an entity and configure the at least one sensing node to perform a sensing task based on reception of the sensing task request. [0008] The processor may be configured to cause the base station to determine that handover of management of the sensing task is necessary based on the one or more reports received from the at least one sensing node.

[0009] The processor may be configured to cause the base station to determine that handover of management of the sensing task is necessary based on a value of at least one performance parameter associated with the sensing task.

[0010] The processor may be configured to cause the base station to determine that handover of management of the sensing task is necessary based on a location of the target.

[0011] The processor may be configured to cause the base station to determine that handover of management of the sensing task is necessary based on a location of one or more of the at least one sensing node.

[0012] The processor may be configured to cause the base station to: attempt to configure one or more further at least one sensing node to perform the sensing task in place of the at least one sensing node; and determine that handover of management of the sensing task is necessary based on a predetermined time period elapsing without successfully configuring at least one further sensing node to perform the sensing task in place of the at least one sensing node.

[0013] The processor may be configured to cause the base station to: attempt to configure one or more further at least one sensing node to perform the sensing task in place of the at least one sensing node; and determine that handover of management of the sensing task is necessary based on a predetermined time number of attempts being reached without successfully configuring at least one further sensing node to perform the sensing task in place of the at least one sensing node.

[0014] The processor may be configured to cause the base station to determine that handover of management of the sensing task is necessary based on detecting a resource shortage or an operational failure.

[0015] The attempt to configure one or more further at least one sensing node may be performed in response to a determination that a sensing node handover is required. [0016] The processor may be configured to cause the base station to determine that handover of management of the sensing task is necessary based on a handover message received from a core network entity configured to perform a sensing function.

[0017] The processor may be configured to cause the base station to identify the further base station to manage the sensing task in response to said determination that handover of management of the sensing task is necessary.

[0018] The processor may be configured to cause the base station to: transmit a request message to the further base station, the request message requesting that the further base station manages the sensing task in place of the base station; receive an acceptance message from the further base station; and identify the further base station based on the acceptance message.

[0019] The further base station may be determined by the base station or indicated to the base station by a network entity performing sensing function as a candidate base station to handle management of the sensing task. The acceptance message may include a value of at least one performance parameter (e.g. supported KPI value(s)) for the sensing task and/or a time pattern of availability of the further base station for the sensing task.

[0020] The processor may be configured to cause the base station to: transmit a request message to a core network entity configured to perform a sensing function, the request message indicating that handover of management of the sensing task is necessary; and receive a response message from the core network entity configured to perform a sensing function.

[0021] The request message may comprise a recommendation of one or more base stations to handle management of the sensing task.

[0022] The response message may comprise information identifying the further base station, and processor is configured to cause the base station to identify the further base station based on the response message.

[0023] The response message may specify the content of the information associated with the sensing task to be transmitted by the base station. [0024] The processor may be configured to cause the base station to transmit the information associated with the sensing task to the further base station.

[0025] The processor may be configured to cause the base station to transmit the information associated with the sensing task to the core network entity configured to perform a sensing function for relaying to the further base station.

[0026] The processor may be configured to cause the base station to inform the at least one sensing node of the handover of management of the sensing task to the further base station.

[0027] Some implementations of the method and apparatuses described herein may further include a method performed by sensing controller entity comprising: 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 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; 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.

[0028] The method may comprise receiving a sensing task request from an entity and the configuring the at least one sensing node to perform a sensing task may be based on reception of the sensing task request.

[0029] The sensing task request may comprise one or more UE identifiers. For example sensing task request may comprise a UE identifier of a UEs acting as a sensing Rx node and/or sensing Tx node, or a sensing information source (e.g., non-3GPP sensor) and/or a UE attached to the target. A candidate sensing controller entity to handle management of the sensing task may be determined by the entity to be the same as the serving gNB of the one or majority of the UEs . The step of determining that handover of management of the sensing task is necessary may be based on when one or a known number/percentage of the UEs in the connected and/or idle state are no longer being served by the serving gNB. [0030] Some implementations of the method and apparatuses described herein may further include a core 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 core network entity to: determine that handover of management of a sensing task is necessary, wherein to perform the sensing task at least one sensing node is configured 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; and transmit information associated with the sensing task to a further core network entity to enable management of the sensing task by the further core network entity in place of the core network entity.

[0031] The core network entity may receive a sensing task request from an entity and configure the at least one sensing node to perform a sensing task based on reception of the sensing task request.

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0033] Figure 2 illustrates an example of a user equipment (UE) 200 in accordance with aspects of the present disclosure.

[0034] Figure 3 illustrates an example of a processor 300 in accordance with aspects of the present disclosure.

[0035] Figure 4 illustrates an example of a network equipment (NE) 400 in accordance with aspects of the present disclosure.

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

[0037] Figure 6 illustrates handover of management of a sensing task from a first sensing controller entity to a second sensing controller entity. [0038] Figure 7 illustrates a signaling flowchart of a sensing controller entity handover procedure in accordance with aspects of the present disclosure.

[0039] Figure 8 illustrates a signaling flowchart of a procedure for handover of management of a sensing task from a base station to a further base station in accordance with aspects of the present disclosure.

[0040] Figure 9 illustrates a signaling flowchart of a further procedure for handover of management of a sensing task from a base station to a further base station in accordance with aspects of the present disclosure.

[0041] Figure 10 illustrate a flowchart of a method performed by a sensing controller entity in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0042] Aspects of the present disclosure advantageously maintain continuity of a sensing service, as a sensing target (e.g. an object and/or a target area) moves into a different location, i.e., different area of interest. In particular, when a sensing measurement process is configured and/or controlled by a sensing controller entity, aspects of the present disclosure relate to how the sensing controller entity selected and associated to a sensing task be updated (modified) or re-selected in order to maintain continuity of a sensing service. We refer herein to a sensing service as a service provided by a communications system (e.g. a 3 GPP system) to perform gathering of sensing data and providing a sensing result to the sensing consumer, e.g. 3rd party application function/server. The sensing service may include sensing operations, which includes the gathering of sensing measurements (e.g. in an access network), sensing measurement processing, creating the sensing data and crating the sensing result.

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

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

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

[0046] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102. [0047] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Intemet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

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

[0049] An NE 102 may support communications with the CN 106, or with another NE

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

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

[0051] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0052] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

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

[0054] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0055] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., /r=0, jU=l , /r=2, jU=3, /r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots. [0056] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0057] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., /r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /r=3), which includes 120 kHz subcarrier spacing.

[0058] Figure 2 illustrates an example of a UE 200 in accordance with aspects of the present disclosure. The UE 200 may include a processor 202, a memory 204, a controller 206, and a transceiver 208. The processor 202, the memory 204, the controller 206, or the transceiver 208, 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.

[0059] The processor 202, the memory 204, the controller 206, or the transceiver 208, 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.

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

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

In some implementations, the processor 202 and the memory 204 coupled with the processor 202 may be configured to cause the UE 200 to perform one or more of the functions described herein (e.g., executing, by the processor 202, instructions stored in the memory 204). For example, the processor 202 may support wireless communication at the UE 200 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 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; 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

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

[0063] In some implementations, the UE 200 may include at least one transceiver 208. In some other implementations, the UE 200 may have more than one transceiver 208. The transceiver 208 may represent a wireless transceiver. The transceiver 208 may include one or more receiver chains 210, one or more transmitter chains 212, or a combination thereof.

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

[0065] A transmitter chain 212 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 212 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 212 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 212 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium. [0066] Figure 3 illustrates an example of a processor 300 in accordance with aspects of the present disclosure. The processor 300 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 300 may include a controller 302 configured to perform various operations in accordance with examples as described herein. The processor 300 may optionally include at least one memory 304, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 300 may optionally include one or more arithmetic-logic units (ALUs) 306. 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).

[0067] The processor 300 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 300) 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).

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

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

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

[0071] The memory 304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 300, cause the processor 300 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 302 and/or the processor 300 may be configured to execute computer-readable instructions stored in the memory 304 to cause the processor 300 to perform various functions. For example, the processor 300 and/or the controller 302 may be coupled with or to the memory 304, the processor 300, the controller 302, and the memory 304 may be configured to perform various functions described herein. In some examples, the processor 300 may include multiple processors and the memory 304 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. [0072] The one or more ALUs 306 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 306 may reside within or on a processor chipset (e.g., the processor 300). In some other implementations, the one or more ALUs 306 may reside external to the processor chipset (e.g., the processor 300). One or more ALUs 306 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 306 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 306 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 306 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 306 to handle conditional operations, comparisons, and bitwise operations.

The processor 300 may support wireless communication in accordance with examples as disclosed herein. A sensing controller entity may comprise the processor 300. The processor 300 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 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; 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.

[0073] Figure 4 illustrates an example of a NE 400 in accordance with aspects of the present disclosure. The NE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, the memory 404, the controller 406, or the transceiver 408, 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. [0074] The processor 402, the memory 404, the controller 406, or the transceiver 408, 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.

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

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

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

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

[0079] In some implementations, the NE 400 may include at least one transceiver 408. In some other implementations, the NE 400 may have more than one transceiver 408. The transceiver 408 may represent a wireless transceiver. The transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

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

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

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

[0083] 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, LI measurement types etc. 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”.

[0084] It shall be noted that the Operations, Administration, and Management (0AM) entity 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).

[0085] The sensing nodes transmit and receive sensing signals, which are defined as transmissions on the 3 GPP 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 3 GPP sensing data, requested by the customer, is referred to as a sensing result.

[0086] A sensing controller entity 510,512 is provided to handle the process of selecting and deselecting sensing nodes. The sensing controller 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 510,512 may therefore be any of a RAN node, a CU-gNB, a DU-gNB, a gNB, a core network sensing function, a Location Management Function (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.

[0087] A sensing target may of course be mobile (i. e. its position changes over time), 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.

[0088] 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 the sensing controller entity is provided. The problem is illustrated in Figures 5(a), 5(b) and 5(c).

[0089] 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. [0090] The target object 502, is to be sensed in a target area 504a. The target object 502 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 tl, in the target’s initial position, 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.

[0091] However, the target is moving, and by time t2, as shown in Figure 5(b), the target has moved to a second position. 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 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.

[0092] 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 as shown in Figure 5(b).

[0093] A purpose of the present invention is to provide a mechanism for detection that, in order to perform the sensing task, it is necessary to handover the management of the sensing task to a new sensing controller entity. Figure 5(c) illustrates a further step, namely the handover of the sensing controller entity at time t3. In this scenario, control of the sensing task has been passed to a new sensing controller entity 512.

[0094] Figure 6 illustrates another example scenario 600 for handover. The sensing object 502 located in area 504 and moving in a direction 506 is being sensed by a first set of sensing nodes 660 comprising a plurality of nodes, 602a, 602b, 602c controlled by a first sensing controller entity 510.

[0095] A handover takes place, after which the sensing object 502 is being sensed by a second set of sensing nodes, 650, comprising one or more nodes 652 controlled by a second sensing controller entity 512. 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.

[0096] It can be observed that as the target (in this example, a target object) moves, i.e., it may move away from the coverage area of a firstly selected TRP/gNB-DU/gNB-CU node, while entering the coverage area of new sensing node(s) or equipment. Moreover, the new sensing target area of interest may as well fall in the coverage of a new sensing controller entity 512 (e.g., a sensing controller entity that controls, selects, updates/adjusts and (re- jconfigures the sensing tasks associated to the new target area of interest) while moving away from the coverage area of the firstly associated sensing controller entity 510. A sensing controller entity similarly to other network functions is typically associated with a fixed preconfigured coverage area that is defined in terms of a specified set of cells or Tracking Areas (TAs).

[0097] Figure 7 illustrates a signaling flowchart of a sensing controller entity handover procedure in accordance with aspects of the present disclosure.

[0098] At step S702, a sensing controller entity 510 selects a first set of at least one sensing node 508 to perform a sensing task and transmits sensor node configuration information to the sensing node(s) 508 to perform the sensing task. That is, the sensing controller entity 510 configures the sensing node(s) 508 to perform a sensing task to sense a target 502 in an environment of the sensing node(s) by way of (i) transmission from the sensing node(s) 508 of at least one sensing signal and (ii) reception at the sensing node(s) of at least one sensing signal. In particular, at step S702 the sensing controller entity 510 configures the sensing node(s) 508 to perform sensing signal transmission, sensing signal reception, measurements, and reporting, by way of transmission of the sensor node configuration information to the sensing node(s) 508 at step S702. As noted above, the sensing controller entity 510 may comprise one or more of a UE, a RAN node, a base station e.g. gNB, a core network entity configured to perform a Location Management Function (LMF) (this core network entity is referred herein as “LMF”), and a core network entity configured to perform a sensing function (this core network entity is referred herein as “SF”). As explained above the “target” referred to herein may be an object or an area. [0099] Step S702 may be performed in response to the sensing controller entity 510 receiving a sensing task request. In particular, step S702 may be performed based on information in the sensing task request. The sensing controller entity 510 may receive the sensing task request from another entity. The sensing controller entity 510 may receive the sensing task request from a core network entity e.g. a SF or a LMF. The sensing controller entity 510 may receive the sensing task request directly from a sensing service consumer (e.g., a requesting third party application or third party application server). The sensing consumer can be part of the 5G system (5GS) or can be a 3rd party application functions, which has subscribed for the sensing service. The sensing task request may define one or more of: a description of a sensing task (e.g., detection of an intruder), a type of the sensing target object (e.g., a human), one or more requested sensing performance parameters (i.e. key performance indicators (KPIs) such as those defined in TR 22.837) a sensing target mobility pattern, information about a target area of interest for sensing, and/or capability of sensing nodes.

[0100] One or more of the sensing node(s) 508 are configured to transmit a sensing signal (referred herein to a sensing Tx node), wherein the sensing signal may be a sensing- dedicated reference signal (RS), a channel state information reference signal (CSI-RS), a positioning reference signal (PRS), a demodulation reference signal (DMRS), or a physical data/control channel signal. The sensor node configuration information transmitted to the sensing Tx node(s) may indicate a sensing signal, which may include one or more of: a waveform type, waveform defining parameters, time-frequency resources for transmission of sensing signal, transmission power for the transmission of the sensing signal, sequence generation type/parameters, physical resource mapping of the generated parameters, or a combination thereof.

[0101] One or more of the sensing node(s) 508 are configured to receive a sensing signal (referred herein to a sensing Rx node). As explained above a sensing node 508 may be only a sensing Tx node, only a sensing Rx node, or be both a sensing Tx node and a sensing Rx node). The received signal may be a sensing signal transmitted from one or more of the sensing node(s) 508 that has been impacted (e.g., reflected, refracted, diffracted) by a target. The sensor node configuration information transmitted to the receiving Rx node(s) may include the configuration parameters/indication/description of the transmitted sensing signal (or a subset thereof), one or multiple indications to measure and/or report the Angle of Arrival (AoA), Zenith of Arrival (ZoA), Reference Signal Received Power (RSRP), Reference Signal Received Path Power (RSRPP), doppler shift value, delay/ Time of Flight (ToF)/ Time of Arrival (To A), Reference Signal Time Difference (RSTD), corresponding to a propagation path of a transmitted sensing signal received by a sensing Rx node. In some embodiments, the propagation path of interest for which the above measurements and/or reporting shall be conducted are defined according to a permissibility condition i.e., condition upon which a sensing measurement shall be reported and/or performed, for example, a delay range or an azimuth angular range (according to a global or a local coordinate system known to the sensing Rx node) for which a configured measurement shall be reported or performed/computed.

[0102] The sensor node configuration information may comprise measurement configuration information. The measurement configuration information may specify one or more types of measurement that the sensing node(s) 508 are to perform.

[0103] The sensor node configuration information may comprise reporting configuration information to configure how the sensing node(s) 508 report information to the sensing controller entity 510. The reporting configuration information may specify one or more reporting types and/or reporting occasions. In one example, the sensing Tx node(s) are configured with dedicated time-frequency pattern to indicate to the sensing controller entity 510 a sensing transmission incapability flag/handover request (e.g., at dedicated time occasions of first symbol of each NR subframe). In one example, the sensing Rx node(s) are configured with a dedicated time-frequency pattern to indicate to the sensing controller entity 510 a sensing reception incapability flag/handover request. In some embodiments, the configuration of the sensing node(s) 508 further include a criterion for the sensing node(s) 508 for indication of a 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 sensing Tx or sensing Rx node.

[0104] The sensor node configuration information for a sensing Rx node 508 may comprise a reporting condition (e.g., to trigger a sensing incapability indication by the sensing Rx node). In some embodiments, the reporting condition includes at least one or any combination of: a. A Reference Signal Received Power (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 and the power/energy of other paths satisfying a condition) value. 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 infeasibility of the sensing Rx measurement is determined autonomously by the sensing Rx node. f. Indication of number of detected conditions as described in a-f 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).

[0105] In one example, the sensor node configuration information for a sensing Rx node 508 may specify that the sensing Rx node 508 is to report to the sensing controller entity 510 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 a predetermined time period (e.g. 50 msecs). [0106] One or more of the sensing node(s) 508 may include a non-3GPP sensor or a node (e.g. a UE or a RAN node) associated with a non-3GPP sensor. The selection and/or configuration of the sensing nodes by sensing controller entity 510 may include selection/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 (azimuth/elevation angular area with respect to a global coordinate system), non- 3GPP sensing data type/format, and/or non-3GPP data resolution/accuracy (bitmap image of 100 by 100 pixels, with 8 bits resolution of each pixel).

[0107] The reporting configuration information may include: a set of time/frequency resources for transmission of the reports transmitted to the sensing controller entity 510, the data type/format for transmission of the report, a criteria for transmission of the reports transmitted to the sensing controller entity 510 (when an object is detected, or when the sensor value/magnitude has changed or fallen below/above a threshold), and/or contextual information to be transmitted by the sensor to the sensing controller entity 510.

[0108] 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 510. In some embodiments, the discovered/identified group of non-3GPP sensors (their ID, their address) are (upon consent of the owner of the 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 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 510 to the sensing service consumer. In some embodiments, upon mobility of a (non-3GPP) sensor and/or upon mobility of a sensing target, the sensing controller entity 510 may determine to discover and/or select a new non-3GPP sensor, de-select a non-3GPP sensor, or a combination thereof. [0109] At step S704, the sensing node(s) 508 perform a sensing measurement process. The sensing measurement process is done via transmission of the sensing signal from one or more sensing Tx nodes and reception of the sensing data (i.e., the measurements of the transmitted sensing signal), by the sensing Rx nodes, according to the received configuration from the sensing controller entity 510. In some embodiments, when sensing Rx and/or sensing Tx nodes are configured with handover specific types of measurement reports, the sensing Tx and/or sensing Rx nodes further perform the handover-specific measurements/determination, according to the received configurations from the sensing controller entity 510. In some embodiments, the handover-specific measurements include determination by a sensing Tx or a sensing Rx node if a handover is necessary from the sensing node, e.g., measurement to determine an indicated criteria for sensing Tx/Rx node incapability.

[0110] At step S706, the sensing controller entity 510 receives one or more reports in connection with the sensing task from the at least one sensing node 508. That is, the sensing controller entity 510 receives at least one report from one or more sensing Tx nodes, and/or receives at least one report from one or more receiving Rx nodes.

[0111] At step S706, the sensing Rx nodes report the obtained sensing measurements and/or sensing Tx nodes report when they detect areas incapable of performing sensing transmission, according to the configuration received from the sensing controller entity 510. In some embodiments, a report includes sensing node handover-specific reports, according to the received configurations by the sensing controller entity 510, wherein a sensing node handover decision of the sensing node is made at the sensing controller entity 510, at least part, based on the received handover-specific report of the sensing (sensing Tx or sensing Rx) node. The handover-specific reports may include a sensing Tx incapability flag/handover request, or a sensing Rx incapability flag/ handover request.

[0112] 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 for which the sensing operation of the node is no longer feasible.

[0113] 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 entity 510, or a combination thereof.

[0114] In one implementation wherein the sensing controller entity 510 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 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 (or 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).

[0115] At step S708, the sensing controller entity 510 determine that handover of management of the sensing task is necessary. That is, the sensing controller entity 510 determines that it is necessary for a further sensing controller entity 512 to take over management of the sensing task from the sensing controller entity 510. In embodiments whereby the sensing controller entity 510 is formed of multiple nodes (e.g., a serving gNB of a sensing task and a SF), the determination performed at step S708 may include a decision to change one or multiple or all of the nodes constituting the sensing controller entity 510. We refer herein to management of a sensing task as comprising one or more of: (i) receiving a sensing task request for sensing information from a service consumer, (ii) determining selection and/or configuration of a sensing operation, including configuration of one or more sensing Tx nodes and one or more sensing Rx node, (iii) collecting 3 GPP sensing data, (iv) performing, configuring or requesting computation of the 3 GPP sensing data to thereby obtain a sensing result; and (v) reporting or exposing the sensing result e.g. to an entity requesting that the sensing take be performed. The sensing controller entity 510 may report/expose the sensing result to the SF.The sensing controller entity 510 may determine that handover of management of the sensing task is necessary in a number of different ways.

[0116] In one example, the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on the reception of the sensing measurement reports received at step S706, i.e., sensing data of the involved sensing Rx nodes and/or report of a sensing Tx node. For example the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on the reception of a report from the sensing node(s) 508 indicating sensing node incapability.

[0117] Alternatively or additionally the sensing controller entity 510 may determine that handover of management of the sensing task is necessary autonomously (e.g. without the sensing measurement reports) for example based on detecting a resource shortage e.g., when the sensing controller entity 510 determines that the available sensing resources, within control of the sensing controller entity 510, are required for other activities with higher priorities. In one example, upon receiving a sensing task request for a second sensing task with a higher priority that a first sensing task (currently being performed), or a communication task request with a higher priority than a sensing task currently being performed, the sensing controller entity 510 may determine that the running sensing task (being performed) may not be further continued/supported due to the assignment of the resources to the higher priority activities, and thereby determines that a handover is necessary for the first sensing task. The sensing controller entity 510 may determine that handover of management of the sensing task is necessary autonomously based on detecting an operational failure. The operational failure may be due to, for example, the detection of a radio operation failure, memory failure or incapability, processing failure or incapability, and/or RF/antenna incapability],

[0118] Alternatively or additionally the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on the prior knowledge of the sensing controller entity 510 of the sensing capability of the involved sensing Tx node(s) and sensing Rx node(s).

[0119] Alternatively or additionally the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on the capability of the sensing controller entity 510.

[0120] Alternatively or additionally the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on a value of at least one performance parameter (e.g. a KPI) associated with the sensing task . For example the sensing controller entity 510 may comparing an estimated or predicted KPI to a desired KPI of the sensing task. The desired KPI may be included in a sensing task request. In some embodiments, the KPI (e.g., accuracy) of a sensing task can be predicted (in advance of completion of the sensing task) or estimated (after a portion of the sensing task has been completed) by the sensing controller entity 510 based on the capability and configuration of the at least one sensing node 508 and based on previously obtained sensing KPI estimates. In one example, the previously obtained sensing KPI estimate includes an estimated KPI of a portion of the sensing task (e.g., when a sensing task is to track position of a target, the KPI may be estimated for the first second of the tracking task and a handover decision may be taken based on the observed KPI of the sensing task during the first second). In another example, the previously obtained sensing KPIs may include an estimate of the KPIs of one or more previously performed/accomplished sensing tasks, and the information of the previously estimated KPIs may be used to estimate or predict the sensing KPI of the current sensing task. Additionally or alternatively, the information of the previously estimated KPIs may be used to trigger a handover if the estimated KPI is below a desired KPI within an indicated margin e.g., a margin of KPI (e.g., estimation error) or during a time period (KPI associated to at least time window duration)).

[0121] Alternatively or additionally the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on a location of the target. For example a location of a sensing target area and/or sensing target mobility pattern (e.g., velocity direction). The location of the target may be estimated based on the sensing measurements performed at step S704 and reported to the sensing controller entity 510 at step S706. The location of the target may be known by receiving this information from a core network entity (e.g. a SF). For example, when a sensing task is to track a UAV along a prior-known trajectory (to check if UAV is properly moving along the route) and hence the route is indicated to the sensing controller entity 510 by the SF, wherein the SF is aware of the route via a sensing consumer request, e.g., via the Network Exposure Function (NEF).

[0122] The sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on a location of the target and location of one or more of the sensing node(s) 508. Taking an example whereby the sensing controller entity 510 is a base station (e.g. a NodeB, an eNB, or a gNB) if a sensing Tx node or a sensing Rx node is a UE, then the base station may obtain the UE location, e.g., via a core network entity configured to implement a Location Management Function (LMF) or a Access and Mobility Management Function (AMF), or directly via the UE. If a sensing Tx node or a sensing Rx node is a gNB TRP, then the location of the TRP is known to the base station and can be further exchanged via X2 interface between the base stations in the wireless communications system. Taking an example whereby the sensing controller entity 510 is a base station (e.g. a NodeB, an eNB, or a gNB), the base station will be associated with a coverage area (defined by the coverage area of all of the sensing node(s) 508 that the base station has access to), and the coverage area is known to the base station. The sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on the location of the target and the coverage area of the base station (e.g. when the target goes outside of the coverage area). The coverage area of the sensing controller entity 510 may be communicated to the base station by a core network entity (e.g. the SF) or by an Operations, Administration, and Management (0AM) entity.

[0123] Alternatively or additionally the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on determining that a second set of at least one sensing node 508 is to be involved in the sensing task in place of the first set of at least one sensing node 508 (i.e. that a sensing node handover is required).

[0124] The sensing controller entity 510 may determine that a sensing node handover is required, attempt to configure one or more further sets of at least one sensing node to perform the sensing task in place of the at least one sensing node; and determine that handover of management of the sensing task is necessary based on: one or both of: (i) a predetermined time period (e.g. 1 sec) elapsing without successfully configuring one of the further sets of at least one sensing node to perform the sensing task in place of the first set of at least one sensing node; and (ii) a predetermined time number of attempts being reached without successfully configuring one of the further sets of at least one sensing node to perform the sensing task in place of the first set of at least one sensing node. For example, the sensing controller entity 510 may determine that handover of management of the sensing task is necessary based on the number of sensing node handovers being initiated or performed exceeding an indicated maximum count of 6 times within an indicated time window of 2 secs.

[0125] In one example, a head/serving gNB node may determine that handover of management of the sensing task is necessary when for the head/serving gNB managing the sensing task, there are no TRPs (or below a certain number or percentage of all TRPs involved in the sensing task) as sensing Tx nodes, sensing Rx nodes or combinations thereof associated to the serving/head gNB.

[0126] In response to determining that handover of management of the sensing task is necessary, at step S710 the sensing controller entity 510 identifies a candidate further sensing controller entity 512 to manage the sensing task. The further sensing controller entity 512 may comprise one or more of a UE, a RAN node, a base station e.g. gNB, a core network entity configured to perform a Location Management Function (LMF), and a SF.

[0127] The further sensing controller entity 512 may be determined by the sensing controller entity 510 or indicated to the sensing controller entity 510 by a core network entity (e.g. a SF), as a candidate to manage the sensing task.

[0128] At step S710 the sensing controller entity 510 transmits a handover request message to the candidate sensing controller entity 512, the request message requesting that the candidate sensing controller entity 512 manages the sensing task in place of the sensing controller entity 510.

[0129] At step S712 the sensing controller entity 510 receives a handover request response message from the candidate sensing controller entity 512. In particular, the candidate sensing controller entity 512 accepts or rejects the received handover request message and sends a handover request response message to the sensing controller entity 510, the handover request response message indicating acceptance or rejection of the handover request message.

[0130] Upon reception of a handover request response message indicating acceptance of the handover request message, at step S714 the sensing controller entity 510 transmits information associated with the sensing task to enable management of the sensing task by the further sensing controller entity 512. As shown in Figure 7, the sensing controller entity 510 may transmit the information associated with the sensing task to the further sensing controller entity 512. In some embodiments, the sensing controller entity 510 transmits the information associated with the sensing task to the SF and the SF communicates this information associated with the sensing task to the further sensing controller entity 512.

[0131] The information associated with the sensing task may comprise one or more of: a. a description of the sensing task (e.g., one or more of: a sensing task description/ID, sensing task KPIs, a target area description/ID, target object description/ID, all or subset of the parameters describing a sensing task as indicated by the first entity/SF or sensing service consumer to the SF), b. an estimate of the required radio resources (e.g., estimated required bandwidth, sensing time, transmission power, etc.), c. description and/or configuration of the involved sensing nodes (sensing Tx, Rx nodes, TRPs, UEs, etc.) d. description of the SF connected to the serving gNB (SF ID, address, etc.) e. previous sensing measurements or a compressed version thereof, f. previously obtained sensing information (computed from the obtained sensing measurements) g. mobility pattern of the sensing target/sensing target area (e.g., the previous trajectory of the target movements, history of the object location/position, presence, orientation, etc. according to a known coordinate system by the further sensing controller entity 512 or a global coordinate system),

[0132] At step S716 the sensing controller entity 510 may inform the involved sensing Tx/Rx nodes of the handover event, including an identifier of the further sensing controller entity 510 (or ID of a subset of nodes that are newly selected to form the further sensing controller entity 512) a timing information from which the destination sensing controller entity is the valid sensing controller entity.

[0133] As noted above, one or more nodes may constitute the sensing controller entity 510. In embodiments whereby the sensing controller entity 510 is formed from multiple nodes, the node within the sensing controller entity 510 which are determined to be replaced, or a node of the sensing controller entity 510 that is not de-selected/removed during the handover process may transmit the handover request message at step S710 to a node which is determined to be added to form the candidate sensing controller entity 512.

[0134] As noted above, one or more nodes may constitute the further sensing controller entity 510. The further sensing controller entity 512 may comprise one or more nodes that form the sensing controller entity 510. At least one node forming the further sensing controller entity 512 is different to the one or more nodes forming the sensing controller entity 510.

[0135] In some embodiments, the steps S704 and S706 are repeated based on the configuration of the further sensing controller entity 512.

[0136] In some embodiments, upon the determination that handover of management of the sensing task is necessary at step S708, the sensing controller entity 510 may transmit the handover request message to a third node (e.g., a core network entity) which is not part of the sensing controller entity 510 or the further sensing controller entity 512. Upon reception of the handover request message the third node then determines a further sensing controller entity 512, requests that the further sensing controller entity 512 handles management of the sensing task and further configures the sensing controller entity 510 and further sensing controller entity 512 for the exchange of information associated with the sensing task.

[0137] Figure 8 illustrates a signaling flowchart of a procedure for handover of management of a sensing task from a base station to a further base station. That is, the sensing controller entity 510 is a base station e.g. a source serving gNB and the further sensing controller entity 512 is a further base station e.g. a new serving gNB. In particular, Figure 8 illustrates a Xn-based inter serving gNB handover procedure.

[0138] At step S802, a SF 804 selects a serving gNB, upon reception of a sensing task request and transmits the sensing task request to the source serving gNB 510. The SF 804 transmits the sensing task request to the via a core network entity configured to perform an access and mobility management function (this core network entity is referred herein as “AMF”) 802 As explained above, the sensing task may include one or more of a requested sensing information type (presence detection, object classification, velocity information, position information, tracking, etc.), desired sensing KPI (e.g., desired resolution (of a sensing target position and/or velocity), accuracy (of a sensing target position and/or velocity), missed-detection, false alarm, confidence margin, latency, etc.), 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.

[0139] In some embodiments, the selected gNB is the serving gNB of the UE (indicated with the UE ID) associated with the UE accompanied/attached to the sensing target/target area. In some embodiments, the serving gNB of a sensing task is selected based on the gNB sensing capabilities, and the location of the target. In some embodiments, the SF 804 selects the serving gNB of a sensing task based on sending a request to one or more of candidate serving gNBs for the sensing task wherein the request includes description of the sensing task (e.g., including the service KPIs, target area description, target object description, or a combination thereof), and receiving response from the one or more candidate serving gNBs, wherein the response may include a positive/accept indication, negative/reject indication, the supported sensing/service KPI indication, or a combination thereof.

[0140] In some embodiments, the SF 804 may further select and indicate to the serving gNB one or multiple candidate RAN nodes for sensing operation, one or multiple target serving gNBs (in case of a serving gNB handover of the selected serving gNB). In some embodiments, the serving gNB may or may not take the recommendation of the SF regarding the selection of sensing Tx/Rx nodes for a sensing operation and/or the target serving gNB.

[0141] At step S804, the source serving gNB 510 selects a first set of at least one sensing node 508 to perform a sensing task and transmits sensor node configuration information to the sensing node(s) 508 to perform a sensing task. That is, the selected serving gNB of the sensing task configures the sensing Tx node(s) and sensing Rx node(s) for performing sensing signal transmission, measurements, and reporting. Step S804 corresponds to step S702 described above. [0142] At step S806, the sensing measurements are conducted at the sensing Tx node(s) and sensing Rx node(s), according to the sensor node configuration information. Step S806 corresponds to step S704 described above.

[0143] At step S808, the source serving gNB 510 receives one or more reports in connection with the sensing task from the at least one sensing node 508. That is, the source serving gNB 510 receives at least one report from one or more sensing Tx nodes, and/or receives at least one report from one or more receiving Rx nodes. Step S808 corresponds to step S706 described above. In some embodiments, when a sensing Rx or a sensing Tx node is configured with reporting resources (including time-frequency resources for report message transmission), and wherein the sensing Tx or sensing Rx node is further configured to detect an event, the sensing Tx/Rx node locates a closest time-occasion to the event detection (or a closest occasion with an indicated minimum or an indicated maximum time-difference) and utilizes the occasion for the report transmission.

[0144] At step S810, the source serving gNB 510 determines that handover of management of the sensing task is necessary. That is, the source serving gNB 510 determines that it is necessary for a new serving gNB 512 to take over management of the sensing task from the source serving gNB 510. Step S810 corresponds to step S708 described above.

[0145] In some embodiments, the determination at step S810 is made based on reception of the sensing measurement reports of the involved sensing Rx nodes and/or report of a sensing Tx node and/or based on the prior knowledge of the serving gNB of the sensing capability of the involved sensing nodes, or upon a handover procedure of a sensing Tx or a sensing Rx node, serving gNB 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), or a combination thereof.

[0146] In some embodiments, the serving gNB handover determination performed at step S810 is made at the SF 804 (e.g., based on received reports sent from the source serving gNB 510 to the SF 804, or the observed quality of the sensing results compared to the expected/required KPIs), and then indicated to the source serving gNB 510 to perform an Xn-based serving gNB handover procedure. That is, the determination that handover of management of the sensing task is necessary may be based on a handover message received from the SF 804.

[0147] In response to determining that handover of management of the sensing task is necessary, at step S812 the source serving gNB 510 identifies a candidate further sensing controller entity 512 to manage the sensing task. In particular, the source serving gNB 510 determines one or multiple candidate target serving gNB 512 (e.g., based on the prior candidate target serving gNBs indicated by the SF and/or based on the estimated/known movement pattern of the sensing object/target area and the position and/or sensing capability of the neighbor gNBs). Step S812 corresponds to step S710 described above. [0148] At step 812 the source serving gNB 510 transmits a handover request message to the one or multiple candidate serving gNBs.

[0149] In some embodiments, the handover request message includes the description of the sensing task (e.g., all or subset of the parameters describing a sensing task, as indicated by the SF or sensing service consumer to the SF, e.g., including sensing service KPIs, sensing target area description, sensing target object description (e.g., object type/radar cross section information), an estimate of the required radio resources (e.g., estimated required bandwidth, sensing time, transmission power, etc.), a time pattern (from what time, subframe, frame, or relative time duration from the request time the role of the target serving gNB shall start), description and/or configuration (or subset of the configuration parameters) of the involved sensing nodes (sensing Tx, Rx TRP nodes, UEs, exact ID or description/number of the involved nodes) etc.

[0150] At step 814 the candidate target serving gNBs 512 respond to the handover request message by way of transmission of a handover request response message to the source serving gNB 510. Each handover request response message may include a positive response, or a negative response, or a conditional positive response, wherein the candidate target serving gNB indicates an acceptable parameter (e.g., a parameter of a sensing task, a supported KPI), or a time pattern for assuming the new role (for which time duration and from when the candidate serving gNB may act as the serving gNB of the associated sensing task), etc. In some embodiments, the source serving gNB 510 may accept a conditional positive response as a positive response, or re-transmit a new request with updated request parameters, or further negotiate with other available gNBs for the selection of a target serving gNB. Step S814 corresponds to step S712 described above.

[0151] In some embodiments, upon reception of the handover request response message (e.g., one or multiple of negative response and/or insufficient service KPIs), the source serving gNB 510 of the sensing task may re-select another candidate target serving gNB 512. Thus upon reception of a handover request response message indicating rejection of the handover request message, the source serving gNB 510 may obtain additional candidate target serving gNB nodes 512 and/or further communicate with one or multiple of the candidate target serving gNBs 512 for the supported sensing task. After failure to obtain a new candidate target serving gNB 512) the source serving gNB 510 may determine an Xn-based inter serving gNB sensing handover incapability/failure.

Alternatively or additionally, after failure to obtain a new candidate target serving gNB 512 the source serving gNB 510 may indicates to the SF an Xn-based inter serving gNB sensing handover incapability/failure.

[0152] Upon reception of a handover request response message indicating acceptance of the handover request message, the source serving gNB 510 selects a candidate serving target gNB 512 to takeover management of the sensing task.

[0153] Upon selection of a target serving gNB 512 of a sensing task, the selected target serving gNB (or an associated ID/address for, e.g., report transfer) may be communicated by the source serving gNB 510 to one or more of the AMF 802, the SF 804 (as illustrated by transmission 816a), and the LMF; and/or the sensing node(s) 508 (as illustrated by transmission 816b) to inform them of the handover event.

[0154] Alternatively or additionally the selected target serving gNB (or an associated ID/address for, e.g., report transfer) may be communicated by the target serving gNB 512 to one or more of the AMF 802, the SF 804, and the LMF; and/or the sensing node(s) 508 to inform them of the handover event.

[0155] Upon reception of a handover request response message indicating acceptance of the handover request message, at step S818 the source serving gNB 510 transmits information associated with the sensing task to the target serving gNB 512 to enable management of the sensing task by the target serving gNB 512. Step S818 corresponds to step S714 described above.

[0156] At step S820 the selected target serving gNB 512 selects a second set of at least one sensing node 508 to perform the sensing task and transmits sensor node configuration information to the sensing node(s) 508 to perform the sensing task. That is, the selected serving gNB of the sensing task configures the sensing Tx node(s) and sensing Rx node(s) for performing sensing signal transmission, measurements, and reporting.

[0157] The second set of at least one sensing node 508 is different to the first set of at least one sensing node 508 but there may be some overlap between the sensing nodes of the first and second sets. The sensing nodes in the second set of at least one sensing node 508 may include one or more sensing nodes in the first set of at least one sensing node 508. The sensing nodes in the second set of at least one sensing node 508 may include all of the sensing nodes in the first set of at least one sensing node 508 and one or more further sensing nodes. The sensing nodes in the second set of at least one sensing node 508 may include none of the sensing nodes in the first set of at least one sensing node 508 (no overlap between the sensing nodes of the first and second sets).

[0158] At step S822 sensing measurements are conducted at the sensing Tx node(s) and sensing Rx node(s) of the second set of at least one sensing node 508, according to the sensor node configuration information in the same manner as described above

[0159] At step S824 the sensing Rx and sensing Tx nodes transmit reports to the target serving gNB 512, according to the received reporting configurations from the target serving gNB 512.

[0160] Figure 9 illustrates a signaling flowchart of a procedure for handover of management of a sensing task from a base station to a further base station. That is, the sensing controller entity 510 is a base station e.g. a source serving gNB and the further sensing controller entity 512 is a further base station e.g. a new/target serving gNB. In particular, Figure 9 illustrates a NGAP-based inter serving gNB handover procedure.

[0161] According to the embodiment shown in Figure 9, the handover procedure includes determining the need for serving gNB handover by the source serving gNB 510, requesting for the serving gNB handover by the source serving gNB 510 to the SF 804, and selection of a new serving gNB 512 by the SF (804).

[0162] Steps S902-S910 correspond to steps S802-S810 shown in Figure 8.

[0163] In response to determining that handover of management of the sensing task is necessary, at step S912 the source serving gNB 510 transmits a handover request message to the SF 804. The handover request message may indicating one or more of the sensing task ID, a timing pattern (from which time the source gNB shall not serve as a serving gNB), a reason that a handover is needed (e.g., supported KPIs) or a combination thereof.

[0164] In some embodiments, the handover request message may be transmitted to the SF 804 when the source seving gNB 510 fails to determine a target serving gNB (e.g., when the satisfied sensing KPI is lower than that of the requested service KPIs), or when a target candidate serving gNB is not connected to the source gNB via Xn interface.

[0165] In some embodiments, the source serving gNB 510 includes in the handover request message, additional information for the SF selection of the target serving gNB, e.g., description of a recommended target serving gNB (e.g., one or multiple target gNBs), direction of the movement of the target, required capability of the target gNB, etc.

[0166] At step S914, the SF 804 upon reception of the handover request message by the source serving gNB 510, the SF 804 determines a candidate target serving gNB. This selection may be done based on the recommendation of the source serving gNB, or based on the SF determination based on all or a subset of the procedures described herein.

[0167] At step S916 the SF 804 indicates to the selected target serving gNB 512 the selection (or a request to act as the serving gNB of the associated sensing task). In some embodiments, the target serving gNB 512 further responds to this request with a positive response, or with a conditional positive response including additional information on the acceptable operation parameters or time schedule as serving gNB.

[0168] At step S918, the source serving gNB 510 receives a handover request response message from the SF 804. The handover request response message may comprise one or more of: an indication of acceptance of the handover request, information of the target serving gNB 512, a time pattern according to which the source gNB will no longer be the serving gNB of the sensing task, the type/ content of the context information to be transferred to the target serving gNB, etc.

[0169] In some embodiments, upon reception at the SF 804 of a negative response from the selected target serving gNB 512, the SF 804 of the associated sensing task may re-select another candidate target serving gNB, or (e.g., after failure to obtain a new candidate serving gNB) determine an NGAP -based inter Serving -gNB sensing handover failure. In some embodiments, an SF incapability for a sensing task is determined by the SF upon determination of NGAP-based inter serving-gNB sensing handover failure. In some embodiments, the NGAP-based inter serving-gNB sensing HO failure and/or the SF incapability are indicated to another SF (e.g., an SF acting as a controlling SF or head SF) or reported to the sensing service consumer of a sensing service failure indication, or triggers an SF reselection/SF HO procedure.

[0170] Upon reception of a handover request response message indicating acceptance of the handover request message, at step S920 the source serving gNB 510 transmits information associated with the sensing task to the target serving gNB 512 to enable management of the sensing task by the target serving gNB 512.

[0171] In some embodiments, the information associated with the sensing task (as described herein) is transferred from the source serving gNB 510 to the SF 804 and the SF 804 communicates the information associated with the sensing task to the target serving gNB 512. In some embodiments, the target serving gNB 512 requests the information associated with the sensing task from the source serving gNB 510, wherein the source serving gNB 510 is indicated to the target serving gNB by the SF 804.

[0172] In some embodiments, upon selection of the target serving gNB 512 for the sensing task, the source serving gNB 510 and/or the SF 804 and/or the target serving gNB 512 transmit an address/ID of the target serving gNB to the sensing node(s) 508.

[0173] At step S922 the selected target serving gNB 512 selects a second set of at least one sensing node 508 to perform the sensing task and transmits sensor node configuration information to the sensing node(s) 508 to perform the sensing task. That is, the selected serving gNB of the sensing task configures the sensing Tx node(s) and sensing Rx node(s) for performing sensing signal transmission, measurements, and reporting.

[0174] Upon configuration of the sensing nodes, the sensing operation, including measurements, reporting, and computation of the desired sensing information is performed.

[0175] Whilst Figure 9 has been shown and described above with reference to steps performed by a SF 804, another core network entity such as an AMF 802 or LMF may perform these steps in place of the SF 804.

[0176] Data described as being transmitted/received with reference to one embodiment may also be transmitted/received in another embodiments where a corresponding step is performed.

[0177] Whilst the steps in the signaling flowcharts of Figures 7-9 are described in a particular order, the steps in the signaling flowcharts of Figures 7-9 may be performed in a different order as that shown.

[0178] In some embodiments, when a UE is associated to a sensing task as a sensing UE, as a requesting UE, or as a UE attached to or accompanying the sensing target area of interest, then the serving gNB handover procedure may be triggered by the UE handover (e.g., a UE inter gNB X2 or N2 handover).

[0179] In some embodiments, the serving gNB of the UE is also the serving gNB of the sensing task associated with the UE. In some embodiments, the serving gNB of the UE may be different than the serving gNB of the sensing task associated with the UE, e.g., under the condition that the UE is not in the connected mode. In some embodiments, when multiple UEs are attached to or accompany/present at the sensing target area of interest, the serving gNB of the associated sensing task is determined by a UE which is selected (e.g., a prominent UE, a head UE for the sensing service that the sensing controller entity may communicate to for reporting or measurement of the sensing task) or as the gNB that serves as serving gNB of the connected UEs more than the others (serving the most number of associated UEs, which are in RRC connected and/or RRC idle state for the sensing task). [0180] In some embodiments, the serving gNB HO of a sensing task is triggered by the source serving gNB, when a threshold absolute or relative number of the UEs associated to the sensing task (1 UE or 2 UE or at least 10% of the UEs associated to the sensing task or at least 20% of the UEs associated to the sensing task and in the RRC connected and/or RRC idle state) undergo a HO.

[0181] Figure 10 illustrates a flowchart of a method 1000 performed by a sensing controller entity in accordance with aspects of the present disclosure to handover management of a sensing task to a further sensing controller entity

[0182] At step SI 002 the sensing controller entity configures 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 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.

[0183] At step SI 004 the sensing controller entity receives one or more reports in connection with the sensing task from the at least one sensing node.

[0184] At step SI 006 the sensing controller entity determines that handover of management of the sensing task is necessary.

[0185] At step SI 008 the sensing controller entity transmits information associated with the sensing task to enable management of the sensing task by a further sensing controller entity.

[0186] The operation of the sensing controller entity in method 1000 is described in further detail with reference to the embodiments of Figures 7-9.

[0187] It should be noted that the method 1000 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.

[0188] The operations of the method 1100 may be implemented by a device 200 or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 104 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware. In these embodiments the sensing controller entity is a UE 104.

[0189] In some implementations, the operations of the method 1000 may be implemented by a NE 400 or its components as described herein. In particular, the method 1000 may be implemented by a base station (e.g. a gNB) to handover management of the sensing task to a further base station (e.g. a further gNB).

[0190] In another example the operations of the method 1000 may be performed by a core network entity e.g. a core network entity configured to implement a sensing function (i.e. a SF). It these examples, the SF may not perform steps S1002 and S1004.

[0191] A SF may also implement a method to handover management of the sensing task to a further SF. This is referred to herein as SF reselection, and we describe this in more detail below.

[0192] In the SF reselection embodiment, a serving gNB of a sensing task or of the UE associated to the sensing task indicates a handover decision to the SF 804. In particular the serving gNB may indicate to the SF that handover of management of the sensing task is necessary.

[0193] The serving gNB may indicate to the SF that handover of management of the sensing task is necessary based on triggering of a sensing node handover procedure, triggering or failure of a serving gNB handover procedure, triggering or failure of a handover for a UE associated to the sensing task, or determination of the Serving gNB (or a controller UE) incapability for a sensing task.

[0194] In response to receiving the indication that handover of management of the sensing task is necessary, the SF may (i)determine that it is necessary to select a new SF for a sensing task, (ii) select a new SF (a candidate target SF) for the sensing task, (iii) transmit a request to the selected new SF requesting that the selected new SF acts as the SF for the sensing task, (iv) receive a response from the candidate target SF, and (iv) transfer information associated with the sensing task to the candidate target SF. [0195] Whilst the above refers to the re-selection of a SF, the sensing controller entity performing the method 1000 may instead be a network entity configured to implement a function other than a sensing function. For example, the sensing controller entity performing the method 1000 may instead be a network entity configured to implement a Location Management Function (LMF).

[0196] In any of the embodiments described above upon determination that a sensing task KPIs may not be fulfilled by one or more of: the serving gNB of the sensing task, the SF, the sensing controller entity, the infeasibility of the sensing task KPI may be indicated to the sensing service consumer. In some embodiments upon such a determination that a sensing task KPI may not be fulfilled, the sensing operation with an alternate (e.g., reduced) KPI is continued (e.g., by the SF, serving gNB of a sensing task). In some embodiments, the sensing service consumer is further notified from the alternate KPI of the sensing service (e.g., including a sensing task ID, a time pattern for which the reduced KPIs hold, etc.)

[0197] In some embodiments, a sensing UE (or multiple sensing UEs) are associated with a sensing task, wherein the sensing UEs have an association with the SF (e.g., through AMF) for the exchange of 3GPP and/or non-3GPP sensing measurements. In some embodiments, the SF associated with the UE is also the SF of the sensing task. In some embodiments, the SF re-selection of the sensing task is triggered, and/or the target SF is determined, based on the SF re-selection of the sensing UE node.

[0198] It will be appreciated from the above that in the embodiments described above, data is received by the sensing Rx nodes, transmitted by the sensing Rx nodes, received by the sensing Tx nodes, transmitted by the sensing Tx nodes, transmitted and/or received by the sensing controller entity, or any combination thereof.

[0199] This data transfer may be implemented via the UL, DL or SL physical data and/or control channels defined within the communication network, e.g., NR PBCH, PDSCH, PDCCH, PUSCH, PUCCH, PSBCH, PSCCH, PSSCH, wherein the sensing Rx and/or the sensing Tx node is a UE. [0200] This data transfer may be implemented via a logical interface between the SF and the Sensing nodes, as part of the LPP or as modified/enhanced LPP message framework for sensing or as an interface defined for sensing message exchanges over the N1 interface between the SF and a UE, wherein the sensing Tx and/or sensing Rx node is a UE.

[0201] This data transfer may be implemented via a logical interface between the sensing controller entity and the Sensing nodes, as part of the NRPPa (or modified/enhanced NRPPa message framework for sensing) or as an interface defined over the NGAP interface, wherein the sensing Tx and/or sensing Rx node is a TRP of RAN and the sensing controller entity is a core network function (SF, LMF, etc,)

[0202] This data transfer may be implemented via a logical interface between the sensing controller entity and the Sensing nodes wherein the sensing controller entity is a serving gNB of a sensing task and the sensing node is a UE or a TRP of RAN. In some examples, the interface utilizes (at least in part) the X2 interface between the associated gNB of the sensing node and the serving gNB of the sensing task.

[0203] 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

1. A base station for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: configure 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 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; receive one or more reports in connection with the sensing task from the at least one sensing node; determine that handover of management of the sensing task is necessary; transmit information associated with the sensing task to enable management of the sensing task by a further base station in place of the base station.

2. The base station of claim 1, wherein the processor is configured to cause the base station to determine that handover of management of the sensing task is necessary based on the one or more reports received from the at least one sensing node.

3. The base station of claim 1 or 2, wherein the processor is configured to cause the base station to determine that handover of management of the sensing task is necessary based on a value of at least one performance parameter associated with the sensing task.

4. The base station of any of claims 1 to 3, wherein the processor is configured to cause the base station to determine that handover of management of the sensing task is necessary based on a location of the target.

5. The base station of claim 4, wherein the processor is configured to cause the base station to determine that handover of management of the sensing task is necessary based on a location of one or more of the at least one sensing node.

6. The base station of any preceding claim, wherein the processor is configured to cause the base station to: attempt to configure one or more further at least one sensing node to perform the sensing task in place of the at least one sensing node; and determine that handover of management of the sensing task is necessary based on: a predetermined time period elapsing without successfully configuring at least one further sensing node to perform the sensing task in place of the at least one sensing node; or a predetermined time number of attempts being reached without successfully configuring at least one further sensing node to perform the sensing task in place of the at least one sensing node.

7. The base station of any preceding claim, wherein the processor is configured to cause the base station to determine that handover of management of the sensing task is necessary based on detecting a resource shortage or an operational failure..

8. The base station of any preceding claim, wherein the processor is configured to cause the base station to determine that handover of management of the sensing task is necessary based on a handover message received from a core network entity configured to perform a sensing function.

9. The base station of any preceding claim, wherein the processor is configured to cause the base station to identify the further base station to manage the sensing task in response to said determination that handover of management of the sensing task is necessary.

10. The base station of claim 9, wherein the processor is configured to cause the base station to: transmit a request message to the further base station, the request message requesting that the further base station manages the sensing task in place of the base station; receive an acceptance message from the further base station; and identify the further base station based on the acceptance message.

11. The base station of claim 9, wherein the processor is configured to cause the base station to: transmit a request message to a core network entity configured to perform a sensing function, the request message indicating that handover of management of the sensing task is necessary; and receive a response message from the core network entity configured to perform a sensing function.

12. The base station of claim 11, wherein the request message comprises a recommendation of one or more base stations to handle management of the sensing task.

13. The base station of claim 11 or 12, wherein the response message comprises information identifying the further base station, and processor is configured to cause the base station to identify the further base station based on the response message.

14. The base station of claim 13, wherein the response message specifies the content of the information associated with the sensing task to be transmitted by the base station.

15. The base station of claim 13 or 14, wherein the processor is configured to cause the base station to transmit the information associated with the sensing task to the further base station.

16. The base station of claim 11 or 12, wherein the processor is configured to cause the base station to transmit the information associated with the sensing task to the core network entity configured to perform a sensing function for relaying to the further base station.

17. The base station of any preceding claim, wherein the processor is configured to cause the base station to inform the at least one sensing node of the handover of management of the sensing task to the further base station.

18. A method performed by sensing controller entity comprising: 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 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; 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; and transmitting information associated with the sensing task to enable management of the sensing task by a further sensing controller entity.

19. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: configure 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 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; obtain one or more reports in connection with the sensing task from the at least one sensing node; determine that handover of management of the sensing task is necessary; and output information associated with the sensing task to enable management of the sensing task by a further sensing controller entity in place of a sensing controller entity.

20. A core 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 core network entity to: determine that handover of management of a sensing task is necessary, wherein to perform the sensing task at least one sensing node is configured 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; and transmit information associated with the sensing task to a further core network entity to enable management of the sensing task by the further core network entity in place of the core network entity.