Systems and methods for wake-up of zero energy devices using integrated sensing and communicaiton

Abstract

According to certain embodiments, a method (900) by a radio node (102) using Integrated Sensing and Communication, ISAC, for wake-up of Zero Energy Devices, ZEDs (104), includes performing ISAC to sense at least one object (108) and transmitting (902) a wake-up radar transmission (110) to at least one ZED within a proximity of the at least one object. Additionally or alternatively, the radio node receives (904) data associated with sensing of the at least one object.

Description

[0001] SYSTEMS AND METHODS FOR WAKE-UP OF ZERO ENERGY DEVICES USING

[0002] INTEGRATED SENSING AND COMMUNICAITON

[0003] TECHNICAL FIELD

[0004] The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for wake-up of Zero Energy Devices (ZEDs) using Integrated Sensing and Communication (ISAC).

[0005] BACKGROUND

[0006] Unlike traditional devices, ZEDs do not require any batteries or manual charging. To generate power, they harvest energy from the world around them. That ambient energy generally comes from sources like vibration, thermal, photovoltaic, or radio frequency. Vibration could come from traffic movement, a washing machine, or even an earthquake. Thermal energy could come from a radiator, the mug of coffee in your hands, and even your own body warmth. Photovoltaic energy comes from solar cells that capture sunlight, and radio frequency comes from anything that transmits signals, like mobile phones, Wi-Fi, Bluetooth, satellite communications, and radio broadcasts. ZEDs can be spread across a farmer’s field, a factory floor or in our clothes, transmitting lifesaving or business-altering data.

[0007] There are different types of ZEDs. 3GPP TR 38.848 discloses the following example ZEDs:

[0008] • Passive zero-energy loT devices with backscattering capabilities - these are battery -less devices, but they have no energy storage capabilities.

[0009] • Active zero-energy loT devices with energy -harvesting capabilities - these devices have limited energy storage capabilities but do not require manual recharging or replacement. They also manage short periods of ambient energy unavailability. Another benefit of the active devices is that they have much better coverage when compared to passive devices.

[0010] ISAC capabilities have been identified as a feature of future 6thGeneration (6G) systems. There are ISAC use cases applicable to improving the performance of the network itself, but also use cases where the spatial sensing can be offered as a service to users or applications that are external to the network.

[0011] The main advantage of the communication network in terms of future sensing is that most of the infrastructure is already in place with transmit (TX) / receive (RX) nodes, providing full area coverage as well as a good interconnection between nodes, which facilitates a multi-static sensory mesh.

[0012] Depending on the frequency, the resolution of the ISAC sensing image that can be obtained varies. For frequencies around 100 GHz and their typical bandwidths, it is possible to reach below 1 cm, but there are other aspects that have impact on the resolution, like the reflective properties of an object as well as the proximity to other nearby objects and their reflective properties.

[0013] In comparison to a visual image from a camera, a sensing image based on the reflections from the transmitted signals is quite crude, but offers other attractive properties that a camera cannot provide. By measuring the delay of the return echo in the line-of-sight path between the transmitter and the object, the distance to the object can be calculated, and therefore, its position.

[0014] Similarly, by measuring the Doppler shift in the received echo, compared to the transmitted signal, the velocity of the measured object can be calculated. Also, ISAC sensing works in complete darkness as well as ‘see’ in rain or fog, but with somewhat degraded performance.

[0015] There are different methods to activate (wake up) devices that are in sleep mode or battery saving mode. For example, a user can manually activate a device, or use an application to remotely activate a device, or a device may wake up when sufficient energy has been harvested (via vibration, thermal, photovoltaic or radio frequency). As another example, U.S. Patent Publication No. 2014 / 062668-Al discloses an Radio Frequency (RF) tag that includes components that are similar to those in a ZED. The RF tag implements a wake-up signal mechanism that detects an RF pattern used to wake up the microcontroller from a sleep state.

[0016] As another example, U.S. Patent Publication No. 2017 / 097413-Al discloses a radar and uses multiple sensors to increase the precision of the radar. However, the radar does not directly communicate with sensors since a radar is not a communication device and is, thus, hardware limited.

[0017] As yet another example, U.S. Patent Publication No. 2018 / 293885-Al discloses using a Narrowband Internet of Things (loT) network to collect traffic information and radar devices to infer information about traffic. However, it is limited to traffic information only such as, for example, speed and the number of vehicles.

[0018] As still another example, U.S. Patent Publication No. 2021 / 389408-Al discloses distributed sensor network models, use cases, and details of the components of each model to achieve the goal of monitoring, detecting, tracking, and mitigating a target(s) such as a signal, an object, a phenomenon, etc. An independent sensor or a local sensor network may supply data to one or more fusion center(s) that collect(s) data and perform(s) higher logic to enhance system performance. A local sensor network allows independent sensors or other local sensor networks to merge into the local sensor network. A sensor cloud can be formed by multiple local sensor networks and independent sensors. By using different distribution models, the local sensor network can provide protection for various targets like Very Important Personnel (VIP) vehicles, lands, facilities, and cities.

[0019] A modular sensor design allows the sensor to monitor the surrounding environment, detect one or more objects when present in the monitoring zone, recognize, and extract features and information from the object, track multiple objects continuously or discretely, share data with other sensors or servers, store captured data for evidence, collect and process data from other sensors, capture intruder images or videos, mitigate the object's presence in its monitoring zone.

[0020] As yet another example, Patent Application EP 3869228-Al discloses a method and system for edge based sensor controlling in the loT network for event monitoring.

[0021] The method includes selecting an initial set of sensors among a plurality of sensors deployed in the loT network to monitor a Region of Interest (ROI) and provide sensor data for an loT application, wherein the initial set of sensors comprise a combination of active sensors and passive sensors, and wherein the active sensors are selected in accordance with a range criteria and preset power constraint for the loT application. The initial set of sensors are activated such that one or more parameters associated with each of the active sensors are activated in a first mode of operation and each of the active sensors are set to a first set of parameter values when activated in the first mode of operation for detecting a basic event in the ROI. Sensor data is received from the initial set of sensors, and the sensor data is preprocessed by applying time stamps on the sensor data received from each of the initial set of sensors for time synchronizing the sensor data and reducing dimensions of the time stamped sensor data using dimension reduction technique to obtain a reduced dimension sensor data.

[0022] There currently exist certain challenge(s) with these and other systems. For example, as transmission of data is costly in terms of energy, ZED devices should ideally only wake-up for transmission when certain criteria are met. ZEDs can be activated via an over the top (OTT) application, pre-determined settings, or when sufficient energy has been harvested. However, it is a challenge to wake-up a selected number of ZEDs for transmission and sensing optimized for a specific event (avoid interference from multiple ZEDs in an area, etc.).

[0023] IS AC has capabilities to detect objects, and the RF energy from IS AC can be used by, for example, ZEDs to harvest some initial energy from radio beams or use energy pulse as a trigger for actions. However, ISAC object detection accuracy is limited, and it is a challenge to determine when / how / where to direct ISAC radio beams towards a selected subset of available ZEDs in, for example, a traffic use case.

[0024] SUMMARY

[0025] To address the foregoing problems with existing solutions, disclosed is systems and methods for utilizing ISAC to address and wake-up a subset of ZEDs based on an event triggered by evaluation of ISAC reflection data.

[0026] According to certain embodiments, a method by a radio node using ISAC for wake-up of ZEDs includes, while performing ISAC to sense at least one object, transmitting a wakeup radar transmission to at least one ZED within a proximity of the at least one object and / or receiving data associated with the at least one object.

[0027] According to certain embodiments, a radio node using ISAC for wake-up of ZEDs is configured to, while performing ISAC to sense at least one object, transmitting a wake-up radar transmission to at least one ZED within a proximity of the at least one object and / or receiving data associated with the at least one object.

[0028] According to certain embodiments, a method by a network server using ISAC for performance-based wake-up of ZEDs includes transmitting a wake-up radar transmission to at least one ZED within a proximity of at least one sensed object or causing the wake-up radar transmission to be transmitted to at least one ZED within the proximity of the at least one sensed object. Additionally or alternatively, the network server receives data associated with the at least one sensed object. According to certain embodiments, a network server for performance-based wake-up of ZEDs is configured to transmit a wake-up radar transmission to at least one ZED within a proximity of at least one sensed object or causing the wake-up radar transmission to be transmitted to at least one ZED within the proximity of the at least one sensed object. Additionally or alternatively, the network server is configured to receive data associated with the at least one sensed object.

[0029] Certain embodiments of the present disclosure may provide one or more technical advantages. For example, certain embodiments may enable a ISAC sensing network node to adaptively acquire additional local ZED sensor data. In this scenario, the term local is in relation to the detected object’s perspective. Another advantage may be that ZED sensor individuals, as well as associated sensor capabilities, may be selected to improve an expected vehicle classification performance and / or to provide a more accurate identification of the vehicle or other unknown object.

[0030] As another example, certain embodiments may provide an advantage of enabling the system to, depending on an identified object (e.g. vehicle), identify, select and ISAC-vise activate said ZED sensors based on their individual capabilities to further acquire data / attributes associated with the identity of the detected object to resolve further details of said object.

[0031] Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

[0032] BRIEF DESCRIPTION OF THE DRAWINGS

[0033] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0034] FIGURES 1A, IB, and 1C illustrate example mono-static, bi-static, and multi-static ISAC systems 10, 40, and 70, respectively;

[0035] FIGURE 2 illustrates an example network architecture for using ISAC to wake-up ZEDs, according to certain embodiments;

[0036] FIGURES 3A, 3B, and 3C illustrate an example method for waking up a subset of ZEDs, according to certain embodiments;

[0037] FIGURE 4 illustrates an example communication system, according to certain embodiments;

[0038] FIGURE 5 illustrates an example UE, according to certain embodiments;

[0039] FIGURE 6 illustrates an example network node, according to certain embodiments;

[0040] FIGURE 7 illustrates a block diagram of a host, according to certain embodiments; FIGURE 8 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

[0041] FIGURE 9 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments; and

[0042] FIGURE 10 illustrates an example method by a network server for using IS AC for performance-based wake-up of ZEDs, according to certain embodiments.

[0043] DETAILED DESCRIPTION

[0044] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in the Appendix.

[0045] As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E-SMLC), etc. The terms network node and radio network node are used interchangeably herein.

[0046] Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.

[0047] The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs.

[0048] The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS / PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal (CRS), Positioning Reference Signal (PRS), etc. RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity (e.g., 20 ms, 40 ms, etc.). The RS may also be aperiodic.

[0049] Each SSB carries New Radio-Primary Synchronization Signal (NR-PSS), New RadioSecondary Synchronization Signal (NR-SSS) and New Radio-Physical Broadcast Channel (NR-PBCH) in four successive symbols. One or multiple Synchronization Signal Blocks (SSBs) are transmitted in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals such as Sounding Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), MTC PDCCH (MPDCCH), Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (E-PDCCH), etc.

[0050] The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, subslot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle, etc.

[0051] According to certain embodiments, systems and methods by a network node utilize ISAC to address and wake-up a subset of ZEDs based on an event triggered by evaluation of ISAC reflection data. Herein, the terms ZED and ZED sensor are used interchangeably. According to certain embodiments, an ISAC network node operates in conjunction with a suite of deployed ZEDs that may have differing capabilities. For example, in certain embodiments, the ISAC network node performs an unsuccessful identification of a targeted physical object. An unsuccessful identification of the targeted physical object may include a scenario where the ISAC network node is not able to identify the physical object at all or is not able to identify the physical object with sufficient accuracy or certainty. Based on the unsuccessful identification, and based on one or more ISAC detection impairment attributes (performance shortcoming), the ISAC network node selects and activates certain individual ZED sensors based on their capabilities to acquire a more accurate classification of the targeted physical object.

[0052] As another example, in certain embodiments, the ISAC network node performs a successful identification of a targeted physical object. Based on that the successful identification, and based on one or more attributes of the identified object, the ISAC network node selects and activates certain individual ZED sensors based on their capabilities to acquire further information associated with the identified object in its current and / or estimated next location.

[0053] FIGURE 1A, IB, and 1C illustrate example mono-static, bi-static, and multi-static ISAC systems 10, 40, and 70, respectively, according to certain embodiments. Specifically, as depicted in each of FIGURES 1A, IB, and 1C, the ISAC systems include at least one ISAC radio node and an object. Specifically, in FIGURE 1A, the ISAC radio node 15 transmits a sensing signal 20 which is reflected off of object 25. In FIGURE 1A, the transmitter and the receiver of the sensing signal 20 are located at a same location (i.e., ISAC radio node 15). Thus, a transmitted signal may interfere with the received signal and inband full duplex functionality is required.

[0054] As depicted in FIGURE IB, the bi-static system 40 includes two ISAC radio nodes 45A and 45B for detecting object 50. As depicted, ISAC radio node 45 A transmits a sensing signal 50, which is deflected by object 55 and received by ISAC radio node 45B. ISAC radio node 45B then performs processing to identify object 55. In this scenario, the transmitter of sensing signal 50 (i.e., ISAC radio node 45A) and the receiver of sensing signal 50 (i.e., ISAC node 45B) are located at different locations.

[0055] As depicted in FIGURE 1C, the multi-static system 70 is similar to the bi-static system but includes multiple receiving ISAC radio nodes. Specifically, the depicted multi-static system 70 includes three ISAC radio nodes 75A, 75B, and 75C. Specifically, ISAC radio node 75A transmits a sensing signal 80, which is deflected by object 85 and is received by ISAC radio node 75B and ISAC radio node 75C. ISAC radio nodes 75B and ISAC radio nodes 75C then perform joint processing to identify object 85. Again, similar to system 50, in this scenario, the transmitter of the sensing signal 80 (i.e., ISAC radio node 75A) and the receivers of the sensing signal 80 (i.e., ISAC node 45B) are located at different locations. Though system 70 is shown as including one transmitting node and two receiving nodes, it is recognized that multi-static system 70 may include any suitable number of transmitting and receiving nodes.

[0056] Where the transmitter of the sensing signal and the receiver(s) of the sensing signal are at different locations, there is no self-interference and, thus, inbound full duplex is not required. However, synchronization is required between transmitting ISAC nodes and receiving ISAC nodes.

[0057] FIGURE 2 illustrates an example network architecture 100 for using ISAC to wake-up ZEDs, according to certain embodiments. The depicted architecture 100 includes multiple ISAC radio nodes 102 A, 102B, and 102C, one or more ZEDs 104, and a network server 106 for detecting object 108. ISAC radio nodes 102 A, 102B, and 102C may include any combination of UEs, gNBs, and / or other network nodes.

[0058] According to certain embodiments, ISAC radio node 102 A operates as an ISAC transmitter and transmits a sensing signal 110, which is deflected by object 108 and received by ISAC radio node 102B. ISAC radio node 102B obtains sensing data based on the received sensing signal and provides the sensing data to network server 106. One or both of ISAC radio node 102B and network server 106 may attempt to identify object 108 based on the sensing data. Depending on the accuracy and / or evaluation of the identification of the object 108, the network server 106 and / or ISAC radio node 102B may determine that a subset of ZEDs 104A should receive a wake-up radar transmission 110 for performing additional sensing.

[0059] As shown in FIGURE 2, network server 106 sends information to ISAC radio node 102C to cause a wake-up radar transmission 110 to be transmitted to the targeted ZEDs 104A. For example, in a particular embodiment, the information transmitted from the network server 106 may identify the targeted ZEDs 104A to receive the wake-up radar transmission 110. In another example embodiment, the information may merely indicate that additional sensing data is needed to identify object 108, and ISAC radio node 102C may identify the targeted ZEDs 104A to receive the wake-up radar transmission 110. In the depicted example, the targeted ZEDs 104A are selected to receive the wake-up radar transmission 110 based on their proximity to object 108. By contrast ZEDs 104B are not selected to receive the wake-up radar transmission 110 based on their location being further from object 108.

[0060] Upon receiving the wake-up radar transmission 110, the targeted ZEDs 104A performing additional sensing operations with respect to object 108 and provide data to the system, accordingly. For example, in a particular embodiment, ZEDs 104A may transmit sensing data to IS AC radio node 102C, which may be processed by IS AC radio node 102C or further transmitted to network server 106 for the further identification of object 108.

[0061] As described herein, in various particular embodiments, the system wakes-up a selected subset of targeted ZEDs 104A for transmission of sensing data related to improved object classification and or for sensing data associated to the area of interest and type of object 108 within the area. ZEDs may harvest energy continuously; however, as described above, the system may select and trigger radio transmission response from a selected subset of ZED(s) 104A by initiating a wake-up radar transmission 110 from the system. For example, a sensing signal may be multiplexed with wake-up commands and transmitted from transmitting ISAC radio node 102C towards respective individual ZEDs 104 A.

[0062] For example, in a particular embodiment, network server 106 analyzes data received by the ISAC sensing. Based on the outcome from the analysis, the network server 206 may send an ini tial / sub sequent ISAC wake-up radar transmission 110 (and / or configuration) to a selected subset of ZEDs 104A in an area of interest.

[0063] In a particular embodiment, for example, the ISAC wake-up radar transmission 110 may include some meta-data such as, for example, one or more ZED identifiers (IDs) and instructions. If, for example, the meta-data includes instruction A and B, then individual ZEDs 104 can be instructed, based on their respective ZED IDs, to perform certain individual task(s).

[0064] Additionally or alternatively, the subset of ZEDs 104 A may be addressed using radio beamforming and are selected based on position in the area of interest, capabilities, etc.

[0065] In a particular embodiment, the ZEDs 104 A are configured to sense and transmit sensor data depending on pre-configured states. For example, the ZEDs 104A may be configured to perform: continuous sensing & transmission when woken up, and / or sensing & transmission of data to assist object classification. In particular embodiments, the wake-up radar transmission 110 may trigger the selected ZEDs 104A to perform certain sensing tasks such as, for example:

[0066] • providing data that assists system to classify an object approaching the area of interest, and / or

[0067] • provide continuous data.

[0068] In a particular embodiment, the network server 106 requests the IS AC radio node 102C to send a “transmi s si on sleep” signal when the data received from the targeted ZEDs 104 A fulfills certain pre-determined criteria.

[0069] It is generally recognized that ISAC "radar RX, TX entities" may be deployed in a same node and / or in separated nodes. In one example scenario, the same ISAC radio node both sends / receives the ISAC signal to determine, for example, that the object 108 is a truck. The same ISAC radio node may also activate the targeted ZEDs 104A in that area. In other scenarios, an ISAC radio node may be separate from the ISAC radio node that sends the wakeup radar transmission 110 to wake up the targeted ZEDs 104A.

[0070] Thus, generally, an example method may be deployed in a traffic infrastructure by a ISAC radio node 102 that operates in conjunction with ZED sensors 104 also deployed in the area. For example, the ISAC radio node 102 may be responsible for detecting / identifying an object, as described above, and / or determining that a performance metric associated with such detecting / identifying of the object is too low. The ISAC radio node 102 then selects, awakens, and / or triggers a subset of ZED sensors 104 in the targeted traffic infrastructure area to acquire additional sensor information. In a particular embodiment, for example, ZED sensors 104 may be selected by ISAC radio node 102 based on their individual capability of providing additional (complementary) information in relation to the ISAC radio node’s (or another ISAC radio nodes’) identification of the object and / or a prediction performance impairment (i.e., type / attribute of shortcoming).

[0071] In a particular embodiment, targeted ZED sensors 104 are selected to improve the ISAC radio node’s objective of, for example, classifying a certain type of vehicle. Thus, in various particular embodiments, the targeted ZED sensors 104 may be selected based on one or more attributes, such as whether the targeted ZED sensors include one or more of the following:

[0072] • an Infrared (IR) / Ultra-violet (UV) frequency / intensity sensor,

[0073] • a thermal sensor, • a vibrational force / intensity / frequency sensor (i.e., Inertial Measurement Unit (IMU) / accelerometer)

[0074] • a size / length measure sensor,

[0075] • a velocity sensor,

[0076] • a load cell capability sensor that issues a voltage measure in response to a loading force,

[0077] • an audio / sound sensor,

[0078] • an image-capturing sensor, and

[0079] • a gas emission (air pollutant) sensor.

[0080] FIGURES 3 A, 3B, and 3C illustrate an example method 200 for waking up a subset of ZEDs, according to certain embodiments. Specifically, FIGURE 3 A relates to steps for using IS AC to detect a targeted physical object. FIGURE 3B relates to steps performed when the initial attempt at identifying the object is successful, and FIGURE 3C relates to steps performed when the initial attempt at identifying the object is unsuccessful. In the illustrated embodiment of FIGURE 3 A, the method begins at step 202 when IS AC is performed to detect an object in an area of interest.

[0081] For example, according to certain embodiments, the network server 106 may use IS AC to detect an object 108 such as an unknown type of vehicle approaching a certain traffic spot. At step 204, an object 108 is detected as approaching the area of interest. At step 206, a network server 106 receives sensing data. In a particular embodiment, the sensing data may be received from an I SAC radio node 102.

[0082] At step 208, the network server 106 assess the sensing data and attempts to identify the object 108. For example, in a particular embodiment, the network server 106 may attempt to identify an object type and / or another attribute associated with the object 108. In a particular embodiment, for example, the network server 106 may determine whether the object 108 is a car of type A or semi-trailer of type B or something else.

[0083] At step 210, the network server 106 determines whether object identification / classification is successful. For example, the network server 106 may determine if an certainty level and / or accuracy level of the identification of the object 108 is greater than a threshold, in a particular embodiment.

[0084] If it is determined that the identification of the object 108 is successful such as where, for example, the certainty level and / or the accuracy level of the identification of the object 108 is greater than a threshold, the method proceeds to FIGURE 3B so that the network server 106 may determine to wake-up at least one ZED 104 for additional sensor data acquisition associated with said object 108. The additional sensing data may increase the accuracy level of the object identification and / or classification. As depicted in FIGURE 3B, at step 212, the network server 106 selects a subset of ZEDs that are most suitable for an area of interest for performing sensing of the object 108. In a particular embodiment, the network server 106 determines which ZEDS 104 are most relevant for sending sensing transmissions based on the type of the object 108 (after ZED feedback) or based on a capability of the ZED(s) for performing a particular sensing task. Thus, in certain embodiments, a subset of ZEDs 104A may be identified for receiving a wake-up radar transmission 110, where such subset of ZEDS 104A are determined to be most relevant for transmissions based on sensing requirements and object type. In a particular embodiment, the subset of ZEDs 104 may be selected based on a capability of the ZEDs 104 for obtaining a particular type of sensing data.

[0085] At step 214, the network server 106 triggers wake-up radar transmission 110 to be transmitted to the selected ZEDs 104A. At step 216, the wake-up radar transmission 110 is received by the targeted ZEDs 104 A, and the targeted ZEDs 104 A start sensing and transmitting sensing data at step 218.

[0086] At step 220, a determination is made as to whether the sensing data from the ZEDs 104A is successfully received by the network server 106. In a particular embodiment, for example, this determination may include evaluating the accuracy of the object identification and / or object classification accuracy and determining whether the accuracy has improved. If the sensing data was successfully received (e.g., the object identification and / or classification has improved), the method returns to step 202 of FIGURE 3 A. Conversely, if the sensing data was not successfully received, the network server 106 assesses the transmission failure and adapts the ISAC procedure, by returning to step 204 of FIGURE 3A for re-selection of additional ZEDs 104 to be requested in next ZED sensor request iteration and repeats the process.

[0087] Returning to step 210 of FIGURE 3 A, if it was determined that object classification was unsuccessful, the method proceeds as illustrated in FIGURE 3C, according to certain embodiments. For example, at step 226, the network server 106 determines that additional sensing data is needed to confirm the object identification and / or object type. At step 228, the network server 106 selects appropriate ZEDs 104 that are most suitable to increase the accuracy of the object identification and / or object type classification.

[0088] At step 230, the network server 106 triggers wake-up radar transmission 110 to be transmitted to the selected ZEDs 104A. At step 232, the wake-up radar transmission 110 is received by the targeted ZEDs 104 A, and the targeted ZEDs 104 A start sensing and transmitting sensing data, at step 234.

[0089] At step 236, a determination is made as to whether the sensing data from the ZEDs 104A is successfully received by the network server 106. If the sensing data was successfully received, the network server 106 analyzes the sensing data, at step 238. to improve object identification and / or area of interest data associated to a certain object type, and the method returns to step 202 of FIGURE 3A. Conversely, if the sensing data was not successfully received, the network server 106 assesses the transmission failure and adapts the ISAC procedure, and the method returns to step 204 of FIGURE 3 A.

[0090] According to certain embodiments, a ISAC radio node 102 may transmit a sensing signal that is multiplexed with wake-up commands towards respective individual ZEDs 104. In a particular embodiment, when sensing data associated with the targeted ZEDs 104A is received at the network, metadata is registered at the radio node or at an external repository. Such metadata may include, for example, one or more of:

[0091] • time stamps,

[0092] • size of the transmitted message,

[0093] • environmental information,

[0094] • ZED identifier,

[0095] • Carrier wave (CW) identifier for backscattered transmissions

[0096] • reader / interrogator / gNB / network identifier,

[0097] • reception power,

[0098] • multipath component,

[0099] • angle of arrival / departure,

[0100] • experienced frequency shifts,

[0101] • experienced frequency drifts,

[0102] • experienced time drifts,

[0103] • and the like. In a particular embodiment, this information is stored and used by a ML model such as, for example, for reinforcement learning, or control-loop, to maximize the probability that a ZED 104 reacts to a wake-up radar transmission 110. For instance, there is no point in sending a wake-up signal to a ZED 104 that has not enough energy to transmit a sensor reading. The network can, for example, infer that a ZED 104 has not enough energy if it does not transmit after one or more wake-up radar transmission 110.

[0104] Accordingly, if a ZED transmission succeeds, the network server 106 stores metadata regarding such transmission. The metadata may be used to fine-tune the ML model, or the control loop. Usually, a successful transmission may not require any change to the ML model, or to the control loop. However, if the ZED transmission fails, the network server 106 stores the relevant metadata regarding the failed transmission. The metadata is fed to the ML model, or control-loop, for additional training so to maximize the probability of successful transmission by the ZED 104. In a particular embodiment, a corrective action can be employed, which can be in the form of, for example, postponing (for some time) one or more ZED transmissions, selecting different or updating the subset of ZEDs 104, etc. Some more examples of correction actions, in various particular embodiments, may include:

[0105] • Sending an RF or harvesting signal to a ZED 104 that failed the transmission so as to allow such ZED 104 to replenish its energy storage and be able to successfully transmit.

[0106] • Sending a wake-up signal to ZEDs 104 to harvest ambient energy, which is useful for those ZEDs 104 if their energy harvesting circuitry also sleeps in case ZEDs sleeps / shuts.

[0107] • Using specific Carrier Wave (CW) from specific CW emitter. The CW is associated with frequency domain allocation, which exhibits specifics properties related to transmission losses, path losses, drifts, etc. Thus, the choice of CW becomes important based on the use case selection where transmissions have budget for losses or not. Another aspect is that, if CW-based transmissions are used for sensing, then different CW associated with different frequency bands will exhibit different sensing properties, and the use case selection, the correction strategy may influence the choice or selection of CW.

[0108] • Using user-desired frequency shift of Frequency Division Multiplexing (FDM) bands of the backscattering signal. • Using beamform RF or ambient energy (if possible) to accelerate the energy replenishment.

[0109] • Activating or enabling or waking-up the readers / receivers / intermediate nodes / other UEs to intercept or receive the ZED transmissions.

[0110] • Increasing or decreasing transmission reliability based on repetitions, power, MCS, etc.

[0111] • Enabling / activating or disabling / deactivating number of ZEDs to do the same sensing tasks.

[0112] FIGURE 4 shows an example of a communication system 300 in accordance with some embodiments. In the example, the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a radio access network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes, such as network nodes 310a and 310b (one or more of which may be generally referred to as network nodes 310), or any other similar 3rd Generation Partnership Project (3 GPP) access node or non-3GPP access point. The network nodes 310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 312a, 312b, 312c, and 312d (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.

[0113] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 300 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0114] The UEs 312 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 310 and other communication devices. Similarly, the network nodes 310 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 312 and / or with other network nodes or equipment in the telecommunication network 302 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 302.

[0115] In the depicted example, the core network 306 connects the network nodes 310 to one or more hosts, such as host 316. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 306 includes one more core network nodes (e.g., core network node 308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 308. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0116] The host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and / or the telecommunication network 302, and may be operated by the service provider or on behalf of the service provider. The host 316 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0117] As a whole, the communication system 300 of FIGURE 4 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0118] In some examples, the telecommunication network 302 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunications network 302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0119] In some examples, the UEs 312 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0120] In the example, the hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312c and / or 312d) and network nodes (e.g., network node 310b). In some examples, the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 314 may be a broadband router enabling access to the core network 306 for the UEs. As another example, the hub 314 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 310, or by executable code, script, process, or other instructions in the hub 314. As another example, the hub 314 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 314 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0121] The hub 314 may have a constant / persistent or intermittent connection to the network node 310b. The hub 314 may also allow for a different communication scheme and / or schedule between the hub 314 and UEs (e.g., UE 312c and / or 312d), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and / or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to an M2M service provider over the access network 304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 310b. In other embodiments, the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 310b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0122] FIGURE 5 shows a UE 400, which may be an embodiment of the UE 112 of FIGURE 4, in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0123] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0124] The UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, a memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 5. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0125] The processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 410. The processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 402 may include multiple central processing units (CPUs).

[0126] In the example, the input / output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 400. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0127] In some embodiments, the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.

[0128] The memory 410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.

[0129] The memory 410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘ SIM card.’ The memory 410 may allow the UE 400 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.

[0130] The processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0131] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0132] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 412, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0133] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0134] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 400 shown in FIGURE 5.

[0135] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0136] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0137] FIGURE 6 shows a network node 500, which may be an embodiment of the network node 110 of FIGURE 5, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

[0138] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0139] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0140] The network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508. The network node 500 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 500 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 500.

[0141] The processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 500 components, such as the memory 504, to provide network node 500 functionality.

[0142] In some embodiments, the processing circuitry 502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of radio frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the radio frequency (RF) transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

[0143] The memory 504 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 502. The memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and memory 504 is integrated.

[0144] The communication interface 506 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. The communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. Radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502. The radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 520 and / or amplifiers 522. The radio signal may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0145] In certain alternative embodiments, the network node 500 does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

[0146] The antenna 510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.

[0147] The antenna 510, communication interface 506, and / or the processing circuitry 502 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0148] The power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508. As a further example, the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0149] Embodiments of the network node 500 may include additional components beyond those shown in FIGURE 6 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

[0150] FIGURE 7 is a block diagram of a host 600, which may be an embodiment of the host 316 of FIGURE 4, in accordance with various aspects described herein. As used herein, the host 600 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 600 may provide one or more services to one or more UEs.

[0151] The host 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input / output interface 606, a network interface 608, a power source 610, and a memory 612. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as FIGURES 4 and 5, such that the descriptions thereof are generally applicable to the corresponding components of host 600.

[0152] The memory 612 may include one or more computer programs including one or more host application programs 614 and data 616, which may include user data, e.g., data generated by a UE for the host 600 or data generated by the host 600 for a UE. Embodiments of the host 600 may utilize only a subset or all of the components shown. The host application programs 614 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 614 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 600 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 614 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0153] FIGURE 8 is a block diagram illustrating a virtualization environment 700 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0154] Applications 702 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0155] Hardware 704 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 708a and 708b (one or more of which may be generally referred to as VMs 708), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708.

[0156] The VMs 708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0157] In the context of NFV, a VM 708 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 708, and that part of hardware 704 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 708 on top of the hardware 704 and corresponds to the application 702.

[0158] Hardware 704 may be implemented in a standalone network node with generic or specific components. Hardware 704 may implement some functions via virtualization. Alternatively, hardware 704 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 710, which, among others, oversees lifecycle management of applications 702. In some embodiments, hardware 704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 712 which may alternatively be used for communication between hardware nodes and radio units.

[0159] FIGURE 9 illustrates an example method 900 by a radio node 102 using IS AC for wake-up of ZEDs 104, according to certain embodiments. In the illustrated embodiment, the method begins at step 902 when, while performing IS AC to sense at least one object 108, the radio node 102 transmits a wake-up radar transmission 110 to at least one ZED within a proximity of the at least one object. Additionally or alternatively, at step 904, the radio node 102 receives data associated with sensing of the at least one object. In a particular embodiment, radio node 102 may include a gNB, a UE, a CPE, Carrier Wave Transmitter (CWT), or Carrier Wave Emitter (CWE).

[0160] In a particular embodiment, based on the data received from the at least one ZED, the radio node 102 identifies at least one attribute or characteristic of the at least one object 108.

[0161] In a particular embodiment, the radio node 102 transmits, to a network server 106 that is co-located with the radio node, the data received from the at least one ZED 104.

[0162] In a particular embodiment, the radio node 102 transmits, to a network server 106 that is associated with a core network 306, the data received from the at least one ZED 104.

[0163] In a particular embodiment, while performing IS AC to sense at least one object, the radio node 102 transmits information associated with the sensing of the at least one object 108 to a network server 106. The radio node 102 receives a request for additional information from the network server, and the wake-up radar transmission is transmitted to the at least one ZED 104 based on the request for additional information from the network server 106.

[0164] In a particular embodiment, the information associated with the sensing of the at least one object 108 includes at least one of: information associated with an identification of the at least one object based the IS AC; an indication that identification of the at least one object 108 was successful; an indication that identification of the at least one object 108 was unsuccessful; and an accuracy level or certainty level associated with the identification of the at least one object 108

[0165] In a particular embodiment, the request for the additional information from the network server 106 includes an indication of the at least one ZED 104 to receive the wakeup radar transmission.

[0166] In a particular embodiment, the radio node 102 selects the at least one ZED 104 for receiving the wake-up radar transmission.

[0167] In a particular embodiment, when selecting the at least one ZED 104, the radio node 102 selects a subset of ZEDs 104 A from a set of a plurality of ZEDs within the proximity of the at least one object 108.

[0168] In a particular embodiment, the at least one ZED 104 within the proximity of the at least one object 108 is selected based on a location of the ZED 104 in relation to a location of the at least one object 108.

[0169] In another particular embodiment, the at least one ZED 104 is selected based on a location of the ZED 104 in relation to a location of the at least one object 108. In another particular embodiment, the at least one ZED 104 is selected based on a location of the ZED 104 in relation to an estimated next location of the at least one object 108.

[0170] In still another embodiment, the at least one ZED 104 within the proximity of the at least one object 108 is selected based on a location of ZED 104 in relation to an estimated next location of the at least one object 108.

[0171] In a particular embodiment, the at least one ZED 104 is selected based on at least one attribute and / or capability of the at least one ZED 104.

[0172] In a particular embodiment, the at least one ZED 104 is selected based on at least one of: a type of data that the at least one type of ZED 104 is capable of obtaining and / or measuring; and / or a type of radiation sensor of the at least one ZED 104. For example, the at least one ZED may be selected based on the radiation sensor including one or more of an Infrared and / or Ultraviolet sensor, a thermal sensor, a vibrational sensor, a size and / or length measurement sensor, a velocity sensor, a load cell capability sensor, an audio sensor, an image-capturing sensor, and a gas emission sensor.

[0173] In a particular embodiment, the radio node 102 detects an occurrence of an event, and the at least one ZED 104 is selected based on detecting the occurrence of the event.

[0174] In a particular embodiment, detecting the occurrence of the event includes at least one of: determining that an identification of the at least one object based on the ISAC was successful; determining that an accuracy level associated with the identification of the at least one object based on the ISAC was greater than a threshold amount; and determining that a certainty level or accuracy level associated with the identification of the at least one object based on the ISAC was greater than a threshold amount.

[0175] In a particular embodiment, the at least one ZED 104 is selected based on at least one attribute of the at least one object 108 and / or a type of the at least one object 108.

[0176] In a particular embodiment, detecting the occurrence of the event includes at least one of: determining that an identification of the at least one object 108 based on the ISAC was unsuccessful; determining that an accuracy level associated with the identification of the at least one object based on the Initial Alignment Control (IAC) was less than a threshold amount; and determining that a certainty level or accuracy level associated with the identification of the at least one object based on the ISAC was less than a threshold amount. In a particular embodiment, after receiving the data from the at least one ZED, the radio node 102 performs at least one of: determining that an updated identification of the at least one object 108 based on the data received from the at least one ZED 104 has been unsuccessful; and selecting at least one additional ZED 104 to receive at least one additional wake-up radar transmission.

[0177] In a particular embodiment, determining that the updated identification of the at least one object 108 has been unsuccessful includes determining that an accuracy level or certainty level associated with the updated identification of the at least one object 108 based on the data received from the at least one ZED 104 is less than a threshold amount.

[0178] In a particular embodiment, the data received from the at least one ZED 104 comprises at least one of: a size of the at least one ZED transmission; environmental information associated with the at least one ZED transmission; at least one ZED identifier; at least one carrier wave identifier; at least one identifier associated with at least one of a reader, an interrogator, a gNB, and / or a network; a reception power; a multipath component; an angle of arrival and / or departure associated with the at least one ZED; at least one experienced frequency shift; at least one experienced frequency drift; and at least one experienced time drift.

[0179] In a particular embodiment, the radio node 102 uses the data associated with sensing of the at least one object 108 as input for a machine learning model to improving ZED transmissions by the at least one ZED 104.

[0180] FIGURE 10 illustrates an example method 1000 by a network server 106 for using IS AC for performance-based wake-up of ZEDs 104, according to certain embodiments. In the illustrated embodiment, the method 1000 begins at step 1002 when the network server 106 transmits a wake-up radar transmission to at least one ZED 104 within a proximity of at least one sensed object 108 or causes the wake-up radar transmission 110 to be transmitted to at least one ZED 104 within the proximity of the at least one sensed object 108. Additionally or alternatively, at step 1004, the network server 106 receives data associated with sensing of the at least one sensed object 108.

[0181] In a particular embodiment, based on the data received from the at least one ZED 104, the network server 106 identifies at least one attribute or characteristic of the at least one sensed object 108. In a particular embodiment, the wake-up radar transmission is transmitted to certain selected ZEDs rather than to all ZEDs within proximity of the at least one sensed object 108. In a particular embodiment, the network server 106 sends the wake-up radar transmission 110 directly to the selected ZEDs 104. In another embodiment, the network server 106 may cause the wake-up radar transmission 110 to be send to the selected ZEDs 104 by transmitting an indication to a network node (e.g., gNB, UE, or another radio node) to send the wake-up radar transmission 110 to the selected ZEDs 104.

[0182] In a particular embodiment, when receiving the data from the at least one ZED 104, the network server 106 receives the data via a radio node 102.

[0183] In a particular embodiment, the radio node 102 is co-located with the network server 106.

[0184] In a particular embodiment, the network server 106 is associated with a core network 306.

[0185] In a particular embodiment, the network server 106 receives information associated with the sensing of the at least one sensed object from a radio node 102 and transmits a request for additional information to the radio node 102. The wake-up radar transmission is transmitted to the at least one ZED 104 by the radio node 102 based on the request for additional information from the network server 106.

[0186] In a particular embodiment, the information associated with the sensing of the at least one sensed object 108 includes at least one of: information associated with an identification of the at least one sensed object 108 based the IS AC; an indication that identification of the at least one sensed object 108 was successful; an indication that identification of the at least one sensed object 108 was unsuccessful; and an accuracy level or certainty level associated with the identification of the at least one sensed object 108.

[0187] In a particular embodiment, the request for the additional information from the network server 106 comprises an indication of the at least one ZED 104 to receive the wakeup radar transmission.

[0188] In a particular embodiment, the network server 106 selects the at least one ZED 104 for receiving the wake-up radar transmission.

[0189] In a particular embodiment, selecting the at least one ZED 104 includes selecting a subset of ZEDs from a set of a plurality of ZEDs within the proximity of the at least one sensed object. In a particular embodiment, the at least one ZED 104 within the proximity of the sensed object 108 is selected based on a location of the ZED 104 in relation to a location of the at least one sensed object 108.

[0190] In another particular embodiment, the at least one ZED 104 is selected based on a location of the ZED 104 in relation to a location of the at least one sensed object 108.

[0191] In another particular embodiment, the at least one ZED 104 is selected based on a location of the ZED 104 in relation to an estimated next location of the at least one sensed object 108.

[0192] In still another embodiment, the at least one ZED 104 within the proximity of the at least one sensed object 108 is selected based on a location of ZED 104 in relation to an estimated next location of the at least one sensed object 108.

[0193] In a particular embodiment, the at least one ZED 104 is selected based on at least one attribute and / or capability of the at least one ZED 104.

[0194] In a particular embodiment, the at least one ZED 104 is selected based on at least one of: a type of data that the at least one type of ZED 104 is capable of obtaining and / or measuring; and / or a type of radiation sensor of the at least one ZED 104. For example, the at least one ZED may be selected based on the radiation sensor including one or more of an Infrared and / or Ultraviolet sensor, a thermal sensor, a vibrational sensor, a size and / or length measurement sensor, a velocity sensor, a load cell capability sensor, an audio sensor, an image-capturing sensor, and a gas emission sensor.

[0195] In a particular embodiment, the network server 106 detects an occurrence of an event, and the at least one ZED 1044 is selected based on detecting the occurrence of the event.

[0196] In a particular embodiment, detecting the occurrence of the event includes determining that an identification of the at least one sensed object 108 based on the IS AC was successful; determining that an accuracy level associated with the identification of the at least one sensed object 108 based on the IS AC was greater than a threshold amount; and determining that a certainty level or accuracy level associated with the identification of the at least one sensed object 108 based on the IS AC was greater than a threshold amount.

[0197] In a particular embodiment, the at least one ZED 104 is selected based on at least one attribute of the at least one sensed object 108 and / or a type of the at least one sensed object 108. In a particular embodiment, detecting the occurrence of the event includes at least one of: determining that an identification of the at least one sensed object 108 based on the ISAC was unsuccessful; determining that an accuracy level associated with the identification of the at least one sensed object 108 based on the ISAC was less than a threshold amount; and determining that a certainty level or accuracy level associated with the identification of the at least one sensed object 108 based on the ISAC was less than a threshold amount.

[0198] In a particular embodiment, after receiving the data from the at least one ZED 104, the network server 106 performs at least one of: determining that an updated identification of the at least one sensed object 108 based on the data received from the at least one ZED 104 has been unsuccessful; and selecting at least one additional ZED 104 to receive at least one additional wake-up radar transmission.

[0199] In a particular embodiment, determining that the updated identification of the at least one sensed object 108 has been unsuccessful comprises at least one of: determining that an accuracy level associated with the updated identification of the at least one sensed object 108 based on the data received from the at least one ZED 104 is less than a threshold amount; and determining that a certainty level or accuracy level associated with the updated identification of the at least one sensed object 108 based on the data received from the at least one ZED 104 is less than a threshold amount.

[0200] In a particular embodiment, the data received from the at least one ZED 104 comprises at least one of: a size of the at least one ZED transmission; environmental information associated with the at least one ZED transmission; at least one ZED identifier; at least one carrier wave identifier; at least one identifier associated with at least one of a reader, an interrogator, a gNB, and / or a network; a reception power; a multipath component; an angle of arrival and / or departure associated with the at least one ZED; at least one experienced frequency shift; at least one experienced frequency drift; and at least one experienced time drift.

[0201] In a particular embodiment, the network server 106 uses the data associated with sensing of the at least one object 108 as input for a machine learning model to improving ZED transmissions by the at least one ZED 104.

[0202] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0203] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

Claims

CLAIMS:

1. A method (900) by a radio node (102) using Integrated Sensing and Communication, ISAC, for wake-up of Zero Energy Devices, ZEDs (104), the method comprising: while performing ISAC to sense at least one object (108), transmitting (902) a wakeup radar transmission (110) to at least one ZED within a proximity of the at least one object; and / or receiving (904) data associated with sensing of the at least one object.

2. The method of Claim 1, comprising: based on the data received from the at least one ZED, identifying at least one attribute or characteristic of the object.

3. The method of any one of Claims 1 to 2, transmitting, to a network server (106) that is co-located with the radio node, the data received from the at least one ZED.

4. The method of any one of Claims 1 to 2, transmitting, to a network server (106) that is associated with a core network (306), the data received from the at least one ZED.

5. The method of any one of Claims 1 to 4, wherein while performing ISAC to sense the at least one object, the method comprises: transmitting information associated with the sensing of the at least one object to a network server; and receiving a request for additional information from the network server, and wherein the wake-up radar transmission is transmitted to the at least one ZED based on the request for additional information from the network server.

6. The method of Claim 5, wherein the information associated with the sensing of the at least one object comprises at least one of: information associated with an identification of the at least one obj ect based the ISAC; an indication that identification of the at least one object was successful; an indication that identification of the at least one object was unsuccessful; and an accuracy level associated with the identification of the at least one object.

7. The method of any one of Claims 5 to 6, wherein the request for the additional information from the network server comprises an indication of the at least one ZED to receive the wake-up radar transmission.

8. The method of any one of Claims 1 to 6, comprising: selecting the at least one ZED for receiving the wake-up radar transmission.

9. The method of Claim 8, wherein selecting the at least one ZED comprises selecting a subset of ZEDs from a set of a plurality of ZEDs within the proximity of the at least one object.

10. The method of any one of Claims 8 to 9, wherein the at least one ZED within the proximity of the at least one object is selected based on a location of the ZED in relation to a location of the at least one object.

11. The method of any one of Claims 8 to 10, wherein the at least one ZED is selected based on at least one attribute and / or capability of the at least one ZED.

12. The method of any one of Claims 8 to 11, wherein the at least one ZED is selected based on at least one of: a type of data that the at least one type of ZED is capable of obtaining and / or measuring; and / or a type of radiation sensor of the at least one ZED.

13. The method of any one of Claims 8 to 12, comprising detecting an occurrence of an event, and wherein the at least one ZED is selected based on detecting the occurrence of the event.

14. The method of Claim 13, wherein detecting the occurrence of the event comprises at least one of: determining that an identification of the at least one object based on the IS AC was successful; and determining that an accuracy level associated with the identification of the at least one object based on the IS AC was greater than a threshold amount.

15. The method of Claim 14, wherein the at least one ZED is selected based on at least one attribute of the at least one object and / or a type of the at least one object.

16. The method of Claim 13, wherein detecting the occurrence of the event comprises at least one of: determining that an identification of the at least one object based on the IS AC was unsuccessful; anddetermining that an accuracy level associated with the identification of the at least one object based on the IS AC was less than a threshold amount.

17. The method of Claim 16, wherein after receiving the data from the at least one ZED, the method comprises at least one of determining that an updated identification of the at least one object based on the data received from the at least one ZED has been unsuccessful; and selecting at least one additional ZED to receive at least one additional wake-up radar transmission.

18. The method of Claim 17, wherein determining that the updated identification of the at least one object has been unsuccessful comprises: determining that an accuracy level associated with the updated identification of the at least one object based on the data received from the at least one ZED is less than a threshold amount.

19. The method of any one of Claims 1 to 18, wherein the data received from the at least one ZED comprises at least one of a size of the at least one ZED transmission; environmental information associated with the at least one ZED transmission; at least one ZED identifier; at least one carrier wave identifier; at least one identifier associated with at least one of a reader, an interrogator, a gNodeB, and / or a network; a reception power; a multipath component; an angle of arrival and / or departure associated with the at least one ZED; at least one experienced frequency shift; at least one experienced frequency drift; and at least one experienced time drift.

20. The method of any one of Claims 1 to 19, comprising using the data associated with sensing of the at least one object as input for a machine learning model to improving ZED transmissions by the at least one ZED.

21. A method (1000) by network server (106) using Integrated Sensing and Communication, ISAC, for performance-based wake-up of Zero Energy Devices, ZEDs (104), the method comprising: transmitting (1002) a wake-up radar transmission to at least one ZED within a proximity of at least one sensed object (108) or causing the wake-up radar transmission (110) to be transmitted to at least one ZED within the proximity of the at least one sensed object; and / or receiving (1004) data associated with sensing of the at least one object.

22. The method of Claim 21, comprising: based on the data received from the at least one ZED, identifying at least one attribute or characteristic of the at least one sensed object.

23. The method of any one of Claims 21 to 22, wherein receiving the data from the at least one ZED comprises receiving the data via a radio node (102).

24. The method of Claim 23, wherein the radio node is co-located with the network server.

25. The method of any one of Claims 21 to 23, wherein the network server is associated with a core network (306).

26. The method of any one of Claims 21 to 25, comprising: receiving information associated with the sensing of the at least one sensed object from a radio node; and transmitting a request for additional information to the radio node, and wherein the wake-up radar transmission is transmitted to the at least one ZED by the radio node based on the request for additional information from the network server.

27. The method of Claim 26, wherein the information associated with the sensing of the at least one sensed object comprises at least one of: information associated with an identification of the at least one sensed object based the ISAC; an indication that identification of the at least one sensed object was successful; an indication that identification of the at least one sensed object was unsuccessful; andan accuracy level associated with the identification of the at least one sensed object.

28. The method of any one of Claims 26 to 27, wherein the request for the additional information from the network server comprises an indication of the at least one ZED to receive the wake-up radar transmission.

29. The method of any one of Claims 21 to 28, comprising: selecting the at least one ZED for receiving the wake-up radar transmission.

30. The method of Claim 29, wherein selecting the at least one ZED comprises selecting a subset of ZEDs from a set of a plurality of ZEDs within the proximity of the at least one sensed object.

31. The method of any one of Claims 29 to 30, wherein the at least one ZED within the proximity of the at least one sensed object is selected based on a location of the ZED in relation to a location of the at least one sensed object.

32. The method of any one of Claims 29 to 31, wherein the at least one ZED is selected based on at least one attribute and / or capability of the at least one ZED.

33. The method of any one of Claims 29 to 32, wherein the at least one ZED is selected based on at least one of a type of data that the at least one type of ZED is capable of obtaining and / or measuring; and / or a type of radiation sensor of the at least one ZED.

34. The method of any one of Claims 29 to 33, comprising detecting an occurrence of an event, and wherein the at least one ZED is selected based on detecting the occurrence of the event.

35. The method of Claim 34, wherein detecting the occurrence of the event comprises at least one of determining that an identification of the at least one object based on the ISACISAC was successful; and determining that an accuracy level associated with the identification of the at least one sensed object based on the ISACISAC was greater than a threshold amount.

36. The method of Claim 35, wherein the at least one ZED is selected based on at least one attribute of the at least one sensed object and / or a type of the at least one sensed object.

37. The method of Claim 34, wherein detecting the occurrence of the event comprises at least one of: determining that an identification of the at least one sensed object based on the ISACISAC was unsuccessful; and determining that an accuracy level associated with the identification of the at least one sensed object based on the ISACISAC was less than a threshold amount.

38. The method of Claim 37, wherein after receiving the data from the at least one ZED, the method comprises at least one of: determining that an updated identification of the at least one sensed object based on the data received from the at least one ZED has been unsuccessful; and selecting at least one additional ZED to receive at least one additional wake-up radar transmission.

39. The method of Claim 38, wherein determining that the updated identification of the at least one sensed object has been unsuccessful comprises: determining that an accuracy level associated with the updated identification of the at least one sensed object based on the data received from the at least one ZED is less than a threshold amount.

40. The method of any one of Claims 21 to 39, wherein the data received from the at least one ZED comprises at least one of: a size of the at least one ZED transmission; environmental information associated with the at least one ZED transmission; at least one ZED identifier; at least one carrier wave identifier; at least one identifier associated with at least one of a reader, an interrogator, a gNodeB, and / or a network; a reception power; a multipath component; an angle of arrival and / or departure associated with the at least one ZED; at least one experienced frequency shift; at least one experienced frequency drift; and at least one experienced time drift.

41. The method of any one of Claims 21 to 40, comprising using the data associated with sensing of the at least one object as input for a machine learning model to improving ZED transmissions by the at least one ZED.

42. A radio node (102) using Integrated Sensing and Communication, ISAC, for wakeup of Zero Energy Devices, ZEDs (104), the radio node adapted to: while performing ISACISAC to sense at least one object (108), transmit a wake-up radar transmission (110) to at least one ZED within a proximity of the at least one object; and / or receive data associated with sensing of the at least one object.

43. The radio node of Claim 42, adapted to perform any of the methods of Claims 2 to 20.

44. A network server (106) using Integrated Sensing and Communication, ISAC, for performance-based wake-up of Zero Energy Devices, ZEDs (104), the network server adapted to: transmit a wake-up radar transmission (110) to at least one ZED within a proximity of at least one sensed object (108) or cause the wake-up radar transmission to be transmitted to at least one ZED within the proximity of the at least one sensed object; and / or receive data associated with sensing of the at least one sensed object.

45. The network server of Claim 44, adapted to perform any of the methods of Claims 22 to 41.

Images