Configuration, coordination and positioning in the context of backscattering communication

Abstract

A carrier wave transmitter (2101) transits a carrier wave. The carrier wave identifies the carrier wave transmitter. A wireless device (2103) receives the carrier wave and transmits a backscattered version of the carrier wave. The backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter. A first network node (2102) 5 receives the backscattered version of the carrier wave. The first network node determines a position of the wireless device based on the carrier wave transmitter identified by the received backscattered version of the carrier wave, or transmits signaling to a second network node (2104) indicating that a backscattered version of a carrier wave transmitted by the carrier wave transmitter has been received from the wireless device, for the second network node to 0 determine a position of the wireless device.

Description

[0001] CONFIGURATION, COORDINATION AND POSITIONING IN THE CONTEXT OF BACKSCATTERING COMMUNICATION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to the field of communication networks, and more specifically to very low energy Intemet-of-Things (loT) devices that communicate via modulation of received carrier waves that may also provide energy for such devices.

[0004] BACKGROUND

[0005] Internet of Things (loT) describes the network of physical objects — “things” — that are embedded with sensors, software, and other technologies for the purpose of connecting and exchanging data with other devices and systems, for example over the internet. These devices range from ordinary household objects to sophisticated industrial tools. By using technologies such as low-cost computing, wireless communications, cloud computing, big data, and analytics, loT devices can collect and share data with minimal human intervention. With a large number of connected loT devices today, experts are expecting this number to grow significantly .

[0006] In some applications, such as monitoring temperature of foodstuffs, loT devices may have small batteries that are disposable (e.g., organic, compostable), rechargeable, or have very limited capacity. However, the need to change battery and battery lifetime are concerns for applications such as asset tracking and environmental / industrial sensors. For such applications, there has been significant interest in so-called zero-energy loT (ZE-IoT) devices, which do not require battery replacement and often “harvest” energy from the environment.

[0007] In general, ZE-IoT devices can be built in very small form factors - even via printing - and have ultra-low energy consumption fulfilled by energy-harvesting from ambient energy sources and / or by using back-scattering communication (e.g., radio frequency identification (RFID)). That is, instead of relying on a built-in battery to provide energy for communication, ZE-IoT devices harvest this energy from sources such as vibrations, solar radio, radio frequency (RF) emissions, etc. In a technique referred to as “backscattering”, a carrier wave is transmitted to the ZE-IoT device, which reflects back a modulated version of the carrier wave to a reader. In other words, the carrier wave is modulated by the ZE-IoT device and reflected back to the reader. The modulated carrier wave reflected back to the reader may also be referred to as a backscattered version of the carrier wave. The modulation or backscattering may for example be performed by the ZE-IoT device by switching the impedance of its antenna between two different impedance states. The ZE-IoT device may for example also harvest energy from the carrier wave. These harvesting techniques facilitate autonomous operation during the lifetime of ZE-IoT devices without need for manual replacement or charging of a battery.

[0008] Currently the fifth generation (5G) of cellular systems, also referred to as New Radio (NR), is being standardized within the Third-Generation Partnership Project (3GPP). NR is developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device-to-device (D2D), and several other use cases. 5G / NR was first specified in Release 15 (Rel-15) and continues to evolve through subsequent releases.

[0009] At a high level, the 5G System (5GS) consists of an Access Network (AN) and a Core Network (CN). The AN provides user equipment (UEs) connectivity to the CN, e.g., via base stations such as gNBs or ng-eNBs. The 5G CN (also called “5GC”) includes a variety of Network Functions (NF) that provide a wide range of different functionalities such as session management, connection management, charging, authentication, etc.

[0010] 3GPP recently started a study on “Ambient loT”, as further described in 3GPP document RP-222685. The study targets a new loT technology suitable for deployment in a 3GPP network, based on ultra-low complexity devices with ultra-low power consumption for very low-end loT applications. The study is intended to address use cases and scenarios that cannot otherwise be fulfilled based on existing 3 GPP low-power wide-area (LPWA) technology such as narrowband loT (NB-IoT), even with reduced peak transmit (Tx) power. As such, it is expected that the radio interface and protocols for this new loT technology will differ in some ways from existing 3GPP radio access technologies (RATs) such as NR and NB-IoT.

[0011] This 3GPP study will consider passive devices that support backscattering communication and active devices that have independent signal generation capabilities. In terms of energy storage, this 3GPP study will consider battery-less devices with no energy storage capability that are completely dependent on availability of an external source of energy, as well as devices with limited energy storage capability that do not need to be replaced or recharged manually.

[0012] Two different types of backscattering communication are monostatic and bistatic. In monostatic backscattering, the carrier wave transmitter (CWT) that transmits the carrier wave to the loT device and the reader that receives the backscattered version of the carrier wave from the loT device are part of the same device while in bistatic backscattering, the carrier wave transmitter and reader are part of different devices. The bistatic setup is illustrated in Figure 1 where the loT device is represented by a tag. For monostatic backscattering, the coordination between the reader and the carrier wave transmitter is device internal and generally vendor specific. In contrast, the carrier wave transmitter and reader for bistatic backscattering may be provided by different vendors, so a standardized coordination solution is needed to support multi-vendor deployments. Currently, a standardized coordination solution for bistatic backscattering does not exist.

[0013] Further, although it may be important to support positioning for devices in a backscattering communication scenario, given the limited capabilities of passive devices, conventional systems may not provide an appropriate process for supporting positioning of such devices.

[0014] SUMMARY

[0015] An object of embodiments of the present disclosure is to address these and other needs, issues, and / or difficulties related to low-energy loT devices, thereby enabling the otherwise- advantageous deployment of such devices, for example in a 3GPP network (e.g., 5G).

[0016] A first aspect provides embodiments of a method implemented by a first network node. The method comprises receiving, from a wireless device, a backscattered version of a carrier wave transmitted by a carrier wave transmitter. The backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter. The method further comprises determining a position of the wireless device based on the carrier wave transmitter identified by the received backscattered version of the carrier wave, or transmitting signaling to a second network node indicating that a backscattered version of a carrier wave transmitted by the carrier wave transmitter has been received from the wireless device, for the second network node to determine a position of the wireless device.

[0017] Corresponding embodiments of a first network node are also provided.

[0018] A second aspect provides embodiments of a method implemented by a wireless device. The method comprises receiving a carrier wave from a carrier wave transmitter. The carrier wave identifies the carrier wave transmitter. The method comprises transmitting a backscattered version of the carrier wave to a first network node. The backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter.

[0019] Corresponding embodiments of a wireless device are also provided.

[0020] A third aspect provides embodiments of method implemented by a second network node. The method comprises receiving signaling from a first network node indicating that a backscattered version of a carrier wave transmitted by a carrier wave transmitter has been received from a wireless device. The backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter. The method comprises determining a position of the wireless device based on the carrier wave transmitter indicated by the received signaling.

[0021] Corresponding embodiments of a second network node are also provided. Embodiments are also provided for configuration and coordination of carrier wave transmitters and readers (also referred to as reader nodes) in the context of backscattering communication. Such embodiments include embodiments of methods implemented by nodes (for example a carrier wave transmitter, a reader, or a wireless device). Corresponding embodiments of nodes are also provided.

[0022] BRIEF DESCRIPTION OF THE DRAWINGS

[0023] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0024] Figure 1 shows an example of bistatic backscattering used with a passive device;

[0025] Figure 2 shows an example deployment of six (6) CWTs in a cell served by a gNB acting as reader, according to some embodiments of the present disclosure;

[0026] Figure 3 shows the example bistatic backscattering of Figure 1 with various newly defined interfaces, according to some embodiments of the present disclosure;

[0027] Figure 4 illustrates semi-static configuration of a CWT by a gNB via Xn’ interface, according to some embodiments of the present disclosure;

[0028] Figure 5 illustrates dynamic signaling from gNB to CWT via Xn’ interface, according to some embodiments of the present disclosure;

[0029] Figure 6 illustrates semi-static configuration of a tag by a CWT, according to some embodiments of the present disclosure;

[0030] Figure 7 illustrates dynamic signaling from a CWT to a tag, according to some embodiments of the present disclosure;

[0031] Figure 8 illustrates dynamic reporting and signaling from a tag to a reader, according to some embodiments of the present disclosure;

[0032] Figure 9 shows an exemplary method (e.g, procedure) for a reader node, according to various embodiments of the present disclosure;

[0033] Figure 10 shows an exemplary method (e.g, procedure) for a CWT node, according to various embodiments of the present disclosure;

[0034] Figure 11 shows an exemplary method (e.g, procedure) for a device, according to various embodiments of the present disclosure;

[0035] Figure 12 shows a communication system according to various embodiments of the present disclosure;

[0036] Figure 13 shows a UE according to various embodiments of the present disclosure; Figure 14 shows a network node according to various embodiments of the present disclosure;

[0037] Figure 15 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized;

[0038] Figure 16 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0039] Figure 17 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

[0040] Figure 18 is a flowchart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0041] Figure 19 is a flowchart of an exemplary process in a WD according to some embodiments of the present disclosure;

[0042] Figure 20 is a flowchart of an exemplary process in another network node according to some embodiments of the present disclosure;

[0043] FIG. 21 shows an example interface between a network node (e.g., CWT) and another network node (e.g., gNB / reader) according to some embodiments of the present disclosure;

[0044] FIG. 22 is a flowchart of a method implemented by a first network node, according to some embodiments;

[0045] FIG. 23 is a flowchart of a method implemented by a wireless device, according to some embodiments; and

[0046] FIG. 24 is a flowchart of a method implemented by a second network node, according to some embodiments.

[0047] DETAILED DESCRIPTION

[0048] Embodiments briefly summarized above will now be described more fully with reference to the accompanying drawings. These descriptions are provided by way of example to explain the subject matter to those skilled in the art and should not be construed as limiting the scope of the subject matter to only the embodiments described herein. More specifically, examples are provided below that illustrate the operation of various embodiments according to the advantages discussed above.

[0049] In general, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The operations of any methods and / or procedures disclosed herein do not have to be performed in the exact order disclosed, unless an operation is explicitly described as following or preceding another operation and / or where it is implicit that an operation must follow or precede another operation. Any feature of any embodiment disclosed herein can apply to any other disclosed embodiment, as appropriate. Likewise, any advantage of any embodiment described herein can apply to any other disclosed embodiment, as appropriate.

[0050] Furthermore, the following terms are used throughout the description given below:

[0051] • Radio Access Node: As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) that operates to wirelessly transmit and / or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., gNB in a 3GPP 5G / NR network or an enhanced or eNB in a 3 GPP LTE network), base station distributed components (e.g, CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point (TP), a transmission reception point (TRP), a remote radio unit (RRU or RRH), and a relay node.

[0052] • Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), a location management function (LMF), or the like.

[0053] • Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Communicating wirelessly can involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through air. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”. • Radio Node: As used herein, a “radio node” can be either a “radio access node” (or equivalent term) or a “wireless device.”

[0054] • Network Node: As used herein, a “network node” is any node that is either part of the radio access network (e.g., a radio access node or equivalent term) or of the core network (e.g., a core network node discussed above) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or equipment in the cellular communications network, to enable and / or provide wireless access to the wireless device, and / or to perform other functions (e.g, administration) in the cellular communications network.

[0055] • Node: As used herein, the term “node” (without prefix) can be any type of node that can in or with a wireless network (including RAN and / or core network), including a radio access node (or equivalent term), core network node, or wireless device. However, the term “node” may be limited to a particular type (e.g., radio access node) based on its specific characteristics in any given context.

[0056] The above definitions are not meant to be exclusive. In other words, various ones of the above terms may be explained and / or described elsewhere in the present disclosure using the same or similar terminology. Nevertheless, to the extent that such other explanations and / or descriptions conflict with the above definitions, the above definitions should control.

[0057] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is generally used. However, the concepts disclosed herein are not limited to a 3GPP system, and can be applied in any system that can benefit from the concepts, principles, and / or embodiments described herein.

[0058] As briefly mentioned above, a technique commonly used in with ZE-IoT devices is “backs cattering” or “backscattering communications.” In this technique, a carrier wave is transmitted to the ZE-IoT device, which reflects back a modulated version of the carrier wave to a reader. The ZE-IoT device may for example harvest energy from the carrier wave or from other ambient energy sources such as heat, light, or vibrations. The harvested energy is used by the ZE-IoT device to modulate and reflect the carrier wave to the reader. These techniques facilitate autonomous operation during the lifetime of ZE-IoT devices without need for manual replacement or charging of a battery. The most well-known application of backscattering is RFID, in which as passive “tag” modulates information on the carrier wave reflected to the reader.

[0059] Two different types of backscattering communication are monostatic and bistatic. In monostatic backscattering, the carrier wave transmitter and reader are part of the same device while in bistatic backscatering, the carrier wave transmitter and reader are part of different devices. Figure 1 shows an example of bistatic backscattering used with a passive device, also referred to herein as “tag”.

[0060] 3GPP recently started a study on “Ambient loT”, as further described in 3GPP document RP-222685. The study targets a new loT technology suitable for deployment in a 3GPP network, based on ultra-low complexity devices with ultra-low power consumption for very low-end loT applications. The study is intended to address use cases and scenarios that cannot otherwise be fulfilled based on existing 3 GPP low-power wide-area (LPWA) technologies such as narrowband loT (NB-IoT), eMTC, etc. even with reduced peak transmit (Tx) power. As such, it is expected that the radio interface and protocols for this new loT technology will differ in some ways from existing 3GPP radio access technologies (RATs) such as NR and NB-IoT.

[0061] This 3GPP study will consider passive devices that support backscattering communication and active devices that have independent signal generation capabilities. In terms of energy storage, this 3GPP study will consider battery-less devices with no energy storage capability that are completely dependent on availability of an external source of energy, as well as devices with limited energy storage capability that do not need to be replaced or recharged manually.

[0062] Device categorization based on corresponding characteristics (e.g., energy source, energy storage capability, passive / active transmission, etc.) may be discussed during the study, in relation to relevant use cases. A device’s peak power consumption may be limited by its practical form factor for the intended use cases and in consideration of its energy source. It has been agreed that the study will consider the following types of Ambient loT devices:

[0063] • Device A: No energy storage, no independent signal generation, i.e., backscattering transmission.

[0064] • Device B: Has energy storage, no independent signal generation, i.e., backscattering transmission. Use of stored energy can include amplification for reflected signals.

[0065] • Device C: Has energy storage, has independent signal generation, i.e., active RF component for transmission.

[0066] It is undecided (or for further study) whether to include device function and / or a target maximum power consumption for each device, and / or whether / how to describe what stored energy is used for (other than for Device B, above). It is also undecided whether combinations of these devices will be considered.

[0067] The following are some specific goals of this 3GPP study:

[0068] 1. Identify the suitable deployment scenarios and their characteristics, at least for the use cases / services agreed in SAl’s “Study on Ambient power-enabled internet of Things”, including at least the following aspects: • Indoor / outdoor environment;

[0069] • Base station characteristics, e.g., macro / micro / pico cells-based deployments;

[0070] • Connectivity topologies, including which node(s), e.g., base station, UE, relay, repeater, etc. can communicate with target devices;

[0071] • TDD / FDD, and frequency bands in licensed or unlicensed spectrum;

[0072] • Coexistence with UEs and infrastructure in frequency bands for existing 3GPP technologies; and

[0073] • Device originated and / or device terminated traffic assumption.

[0074] NOTE: There can be more than one deployment scenario identified for a use case, and a deployment scenario may be common to more than one use case.

[0075] NOTE: Where more than one deployment scenario is identified for a use case, the tradeoffs between them should also be studied.

[0076] NOTE: The study shall not prioritize deployment aspects that should be coordinated with SA, e.g., public or private network, with or without CN connection.

[0077] NOTE: A representative use case can be studied for a group of use cases that have similar requirements. Formulate a set of RAN design targets based on the identified deployment scenarios and their characteristics for the relevant use cases, at least including:

[0078] • Power consumption

[0079] • Complexity

[0080] • Coverage

[0081] • Data rate

[0082] • Positioning accuracy

[0083] NOTE: The requirements from SAI on the relevant use cases shall be taken into consideration.

[0084] NOTE: The study shall aim to provide better coverage compared to existing non-3GPP technologies for the relevant use cases.

[0085] NOTE: Other RAN design targets in relation to connection density, mobility, security, latency, reliability etc. may be discussed, if necessary for the relevant use cases.

[0086] NOTE: Detailed definitions of the RAN design targets should be discussed during the study. Compare and assess the feasibility of meeting the design targets for relevant use case on the basis of the deployment scenario(s) appropriate to it, and identify assumptions on required functionality to be supported. NOTE: This is not to require a detailed WG-level of analysis. For monostatic backscattering, the coordination between reader and carrier wave transmitter is device internal and generally vendor specific. In contrast, the carrier wave transmitter and reader for bistatic backscattering may be provided by different vendors, so a standardized coordination solution is needed to support multi-vendor deployments. Currently, a standardized coordination solution for bistatic backscattering does not exist.

[0087] Embodiments of the present disclosure address these and other needs, issues, and / or difficulties by techniques to configure and steer the carrier wave transmitter (CWT) operation in bistatic backscatter communication for passive devices (also referred to as “tags”, e.g., device types A and B from 3GPP study). For example, embodiments facilitate deployment in a 3GPP network where one gNB would act as a reader and be configured to control multiple CWTs. In this manner, embodiments can provide configurability and flexibility for bistatic backscattering communication for passive devices, as well as dynamic control and more advanced functionality. In general, embodiments facilitate deployment of “Ambient loT” in conjunction with 3GPP networks (e.g., 5G).

[0088] In general, the bistatic backscattering communication coverage area is limited by the CWT-to-tag distance due to the passive device’s RF harvesting sensitivity (also referred to as “activation threshold”). Thus, in a fixed network deployment, a required density of CWTs is typically higher than the density of base stations (e.g., gNBs). Figure 2 shows an example deployment of six (6) CWTs in a cell served by a gNB acting as reader, according to some embodiments of the present disclosure.

[0089] In deployments exemplified by Figure 2, existing gNB’s would be reused as readers to support backscattering communication for a passive devices (tags). In embodiments of the present disclosure, the following new communication interfaces are introduced for the support of bistatic backscattering communication:

[0090] • Xn ’ interface is introduced between CWT and the gNB, or more generally between CWT and a backscattering communication control node, which can be located in gNB or elsewhere in the network (NW). The following description is based on it being located in a gNB.

[0091] • Cu interface is introduced between CWT and the device / tag.

[0092] Figure 3 shows the example bistatic backscattering of Figure 1 with these new interfaces, as well as the Uu interface between tag and reader.

[0093] Upon CWT setup, the CWT would be configured by its associated gNB over A ’ interface to operate in the desired manner. In conventional RFID communications, there is no concept of coordination between nodes; the RFID reader acts both as a CWT and reader (in the monostatic case) and any tag within range of the CWT would respond. In other words, the RFID tags cannot therefore distinguish between individual RFID readers.

[0094] Figure 4 illustrates semi-static configuration of a CWT by a gNB via Xn’ interface, e.g., at initial setup, according to some embodiments of the present disclosure. For the integration of backscattering communication into a cellular network, and support of the bistatic case, the following functionality and information would be useful for setup and configuration of the CWT:

[0095] 1. Controlling / parent gNB

[0096] • What: Indicates to CWT which gNB it is associated with and controlled by. Note that typically one gNB would control multiple CWTs in its coverage area if uplink tag-to- reader range is limited, such as shown in Figure 2. The configuration is used to associate the CWT with a gNB; in some embodiments, the gNB keeps CWT contexts for all of its associated CWTs.

[0097] • Why: Needed for initial setup.

[0098] • Applicability: For bistatic setup.

[0099] 2. Reader / gNB identifier

[0100] • What: For CWT to be able to indicate to the tag in which reader coverage area (gNB cell) it is located. Also indicates to CWT which gNB it is associated with and controlled by. o In some embodiments, this is the same as the controlling / parent gNB mentioned above, i.e., only one parent reader / gNB ID is signaled to the CWT. o In other embodiments, a CWT may assist multiple readers / gNBs, such as when the CWT’s coverage area overlaps with more than one reader / gNB cell. Then it may be beneficial if more than one reader / gNB can exert control over the CWT. The associated control signaling does not need to go directly from multiple readers / gNBs to the CWT but can instead go via the parent reader / gNB.

[0101] • Why: Needed for example to support Tracking Area Update (TAU), registration area, or RAN notification area update.

[0102] • Applicability: Useful for both monostatic and bistatic setup.

[0103] 3. CWT identifier:

[0104] • What: gNB assignment of CWT-ID to the CWT. CWT-ID is used for addressing and for inclusion in downlink transmission to devices / tags. In its simplest form, the CWT- ID is unique within the coverage area of a parent reader / gNB. In another embodiment, the CWT-ID could be unique within a larger coverage area, perhaps even globally unique. • Why: To enable that devices / tags can determine in which CWT’s coverage area they are located (this use of CWT identifiers for positioning will be described further below).

[0105] • Applicability: For bistatic setup.

[0106] 4. Carrier wave (CW) configuration

[0107] • What: Configuration which the CWT should apply for sending the carrier wave to devices / tags. Including for example the following parameters: o Carrier wave frequency information, e.g., frequency allocation or frequency offset to be applied. This to allow for frequency reuse with other CWTs to improve capacity. o Transmit power to apply. o CW beam configuration and setup, e.g. number of beams, beam index configuration, beam sweeping configuration, etc. o Time or synchronization information, e.g., time allocation, allowed time resources for CW transmission, time offset or sync info, etc. E.g., for periodic transmission of CW to allow for device / tag access (to support similar functionality as PRACH). Or a time offset for the CWT to apply for all transmissions to ensure uplink transmissions from devices / tags are received with the desired frame timing at the gNB receiver. o Control header format to apply for transmission to devices / tags. A CWT should support a range of control header formats (including using a default one if the indication is absent, or using no control header at all), and in this way gNB could control which control header format the CWT is using. In one implementation, only one control header format is communicated to CWT, and CWT should always apply that. In another implementation, multiple control header formats are communicated to CWT, and CWT can select to use any of these depending on circumstances, e.g., if there is a DL transmission to the device / tag, or if CWT is to trigger a UL transmission from the device / tag. (See details of what the control header can include below under dynamic information). o Configuration of UL and DL time slots / resources, e.g., TDD configuration if applicable.

[0108] • Why: Required unless CW transmission is static and always the same for all CWTs in the network. I.e., to provide flexibility and configurability of CW transmissions. For example, to enable FDMA of backscattering devices / tags for capacity improvement, or to provide “PRACH” like resources for device-initiated UL transmission (see above).

[0109] • Applicability: For bistatic setup.

[0110] In some embodiments, CWT nodes not only transmit CWs but also transmit (or broadcast) DL data to the devices in their respective coverage areas. In such embodiments, the semi-static configuration information provided by the reader / gNB to CWTs can include one or more of the following:

[0111] 1. Downlink transmission configuration

[0112] • What: Configuration to support DL data transmission to passive devices that is applicable for such devices in the CWT coverage area. Note that this refers to the physical layer configuration and the data could be either user-plane or control-plane signaling. This may include one or more of the following parameters: o Time and frequency configuration / resource allocation for downlink transmission. o Transport block sizes (TBS) o Modulation and coding schemes (MCS), etc. o Acknowledgement of uplink transmission (fixed format). o CW charging period / time before DL transmission period. o Reference symbol configuration. o Repetition factor (if applicable). o CWT transmit power for DL data transmission. o DL scrambling configuration. o Configuration of UL and DL timeslots / resources, e.g., TDD configuration if applicable.

[0113] • Why: To be able to support downlink data transmission for bistatic communication case.

[0114] • Applicability: For bistatic setup.

[0115] 2. Broadcast information (system information)

[0116] • What: gNB control of broadcast information (master information block, system information) for CWT to transmit periodically: gNB / cell ID, CWT ID, synchronization signal / information, system frame number and time information, the DL transmission configuration, gNB configuration applied for backscattering communication (in coverage area of gNB, i.e., all CWTs configured to the gNB), CWT configuration applied for backscattering communication (in the CWT coverage area), and any of the information received from gNB which must be made known to devices / tags (see previous bullets and the system info below over Cu interface). o In some embodiments, different CWTs can have different configurations. In other embodiments, the broadcast / system information is the same for all CWTs that are associated with a single gNB, or possibly even for all CWTs over a wider area covered by multiple gNBs. If CWTs are synchronized, single frequency network (SFN) transmission can be used to improve coverage.

[0117] • Why: To allow gNB control of CWT operation and device / tag operation in the CWT coverage area.

[0118] • Applicability: For bistatic setup.

[0119] Figure 5 illustrates dynamic signaling from gNB to CWT via Xn’ interface, according to some embodiments of the present disclosure. After the CWT is setup and configured to work in the desired manner, some information over Xn ’ interface is still required to be able to control the CWT operation upon data transmission to or from the device / tag. That is, control information and commands from gNB to CWT to initiate downlink or uplink transmission to a device / tag. The following dynamic information from gNB to CWT is beneficial to support the case of bistatic backscattering communication:

[0120] 1. Triggering of downlink (DL) transmission

[0121] • What: Triggering of DL data transmission to tag. When CWT receives this command from gNB it will trigger a downlink transmission to a device / tag according to the semistatic configuration it received earlier from gNB (see above) and the information in the dynamic triggering command. The latter can include, e.g., the following: o Dynamic CW configuration

[0122] • Time info: time allocation, start time, time offset, etc. to be applied for CW transmission.

[0123] • Frequency info: frequency allocation, frequency offset, etc. to be applied for CW transmission.

[0124] • CW beam configuration to apply. o Device / tag ID or addressing (e.g., device group ID) to indicate which device / tag the data is for.

[0125] • Dedicated indication, i.e., data to one device / tag.

[0126] • Group indication, i.e., data to a group of devices / tag.

[0127] • The indication can alternatively also be set to address all devices / tags, e.g., for system information broadcast (see below), paging, device localization, warnings, alerts, etc. o gNB ID o CWT ID o Downlink data payload to be transmitted. o Physical layer parameters to be applied for the DL transmission (either signaled over Xn', i.e., gNB control, or in an alternative implementation determined autonomously by CWT from the earlier signaled allowed set in semi-static information from gNB, i.e., CWT control):

[0128] • Transport block size (determined from the downlink data payload).

[0129] • Modulation and coding scheme.

[0130] • Frequency and time radio resource allocation.

[0131] • Dynamic frequency offset.

[0132] • Acknowledgement of uplink transmission (fixed format).

[0133] • Repetition factor (if applicable).

[0134] In some embodiments, the CWT prepares a control header of fixed format which is transmitted before the flexible data transmission and indicates control information and the physical layer parameters used to the device / tag (see below).

[0135] • Why: For gNB to control and command CWT to initiate a downlink transmission to a device / tag.

[0136] • Applicability: For bistatic setup. Triggering of uplink (UL) transmission

[0137] • What: Triggering of UL data transmission for a device / tag, i.e. carrier wave transmission to the device / tag power it for an uplink transmission to gNB. When CWT receives this command from gNB it will trigger an UL transmission by transmitting a CW to the device / tag according to the semi-static configuration it received earlier from the gNB (see above) and the information in the dynamic triggering command. In some embodiments, the CWT prepares a control header of fixed format which is transmitted before the flexible data transmission and indicates control information and the physical layer parameters used to the device / tag (see below). The information in the dynamic triggering command can include, e.g., the following: o Dynamic CW configuration

[0138] • Time info: time allocation, start time, time offset, etc. to be applied for CW transmission.

[0139] • Frequency info: frequency allocation, frequency offset, etc. to be applied for CW transmission.

[0140] • CW beam configuration to apply. o Device / tag ID or addressing (e.g., device group ID) • To avoid UL transmission from all devices / tags in CWT coverage area.

[0141] • Alternately, can be set to address all devices / tags, e.g., for automatic inventory and similar use cases. o gNB ID o CWT ID o Physical layer parameters to be applied for the UL transmission in the case control header is included with the CW (either as signaled over A ’, i.e., gNB control, or in an alternative implementation determined autonomously by CWT from the earlier signaled allowed set in semi-static information from gNB, i.e., CWT control):

[0142] • Frequency and time radio resource allocation. o Dynamic frequency offset.

[0143] • In alternative implementation with “scheduled uplink transmission”: o Transport block size or “UL grant size” o Modulation and coding scheme.

[0144] • Acknowledgement of downlink transmission (fixed format).

[0145] • Repetition factor (if applicable).

[0146] • Device / tag transmit power.

[0147] • Uplink scrambling configuration.

[0148] • Why: For gNB to control and command CWT to initiate an uplink transmission from device(s) / tag(s).

[0149] • Applicability: For bistatic setup.

[0150] Figure 6 illustrates semi-static configuration of tag by CWT according to some embodiments of the present disclosure. For example, this arrangement can correspond to broadcast system information in conventional 3GPP networks. For a gNB to be able to control device / tag behavior in the CWT (or gNB) coverage area, a CWT can forward some of the semi-static control information from the gNB to the devices / tags. This information can be a longer-term configuration and thus can be signalled as a semi-static configuration to the devices / tags, and may include one or more of the following:

[0151] 3. Broadcast information (system information)

[0152] • What: CWT broadcast of system information (see above): gNB ID, CWT ID, CW configuration applied, the DL transmission configuration, synchronization signal / information (see below), system frame number and time information, the fixed control header configuration (UL & DL), gNB configuration applied for backscattering communication (in coverage area of gNB, i.e., all CWTs configured to the gNB), CWT configuration applied for backs cattering communication (in the CWT coverage area), and any of the information received from gNB which must be made known to devices / tags (see previous bullets and the system info below over Cu interface). o In some embodiments, this can be CWT specific, and different CWTs can have different configurations. In another implementation, the broadcast / system inform is the same for all CWTs that belong to the same gNB (or even wider area). If CWTs are in sync, SFN (single frequency network) transmission can be applied to improve coverage.

[0153] • Why: CWT must provide some configuration parameters to devices / tag to enable gNB to control device / tag operation in the CWT coverage area.

[0154] • Applicability: For bistatic setup.

[0155] 4. Synchronization signal

[0156] • What: In alternative implementation, synchronization signal is required to be obtained by devices / tags more frequently and broadcasted by CWT separately from the other more infrequent broadcast information.

[0157] • Why: If devices / tag need to maintain downlink synchronization in between CW or system information transmissions.

[0158] • Applicability: For bistatic setup.

[0159] Figure 7 illustrates dynamic signaling from CWT to device / tag upon transmission to device / tag, according to some embodiments of the present disclosure. For gNB to be able to control the device / tag behavior in CWT (or gNB) coverage area, a CWT can forward some of the dynamic control information from the gNB to the devices / tags. For example, one or more of the following dynamic information can be signalled to the devices / tags upon data transmission:

[0160] 1. Triggering of DL transmission

[0161] • What: Triggering DL data transmission to device / tag. CWT triggers a downlink transmission to a device / tag over Cu interface according to the semi-static configuration it received earlier from gNB (see above) and the information in the dynamic triggering command. The following information can be included: o Carrier wave o DL data payload to be transmitted. o In some embodiments, the CWT includes a control header of fixed format which is transmitted before the flexible data transmission and indicates some control information and physical layer parameters used to the device / tag (see below).

[0162] • Control parameters (control header): o Device / tag ID or addressing (e.g., device group ID) to indicate which device / tag the data is for.

[0163] ■ Dedicated indication, i.e., data to one device / tag.

[0164] ■ Group indication, i.e., data to a group of devices / tag.

[0165] ■ The indication can alternatively also be set to address all devices / tags, e.g., for system information broadcast (see below), paging, device localization, warnings, alerts, etc. o gNB ID o CWT ID o CW beam index

[0166] • Physical layer parameters (control header): o Transport block size (determined from the downlink data payload). o Modulation and coding scheme. o Frequency and time radio resource allocation, e.g., dynamic frequency offset. o Acknowledgement of uplink transmission (fixed format). o Repetition factor (if applicable).

[0167] • Why: For gNB to, through the CWT, be able to control and initiate a downlink transmission to a device / tag.

[0168] • Applicability: For bistatic setup. Triggering of UL transmission

[0169] • What: Triggering UL data transmission from device / tag. CWT triggers an uplink transmission from a device / tag over Cu interface according to the semi-static configuration it received earlier from gNB (see above) and the information in the dynamic triggering command by sending the CW, and optionally a control header, to the device / tag. The following information can be included: o Carrier wave o In some embodiments, the CWT includes a control header of fixed format which is transmitted before the flexible data transmission and indicates some control information and physical layer parameters used to the device / tag (see below).

[0170] • Control parameters (control header): o Device / tag ID or addressing (e.g., device group ID) to indicate which device / tag the data is for.

[0171] ■ Dedicated indication, i.e., data from one device / tag.

[0172] ■ Group indication, i.e., data from a group of devices / tag. ■ Alternately, set to address all devices / tags, e.g., for automatic inventory and similar use cases. o gNB ID o CWT ID o CW beam index

[0173] • Physical layer parameters (control header): o Frequency and time radio resource allocation, e.g., dynamic frequency offset. o In embodiments with “scheduled uplink transmission”:

[0174] ■ Transport block size or “UL grant size”

[0175] ■ Modulation and coding scheme.

[0176] ■ Transport block size or “UL grant size”

[0177] ■ Modulation and coding scheme. o Acknowledgement of downlink transmission (fixed format). o Repetition factor (if applicable). o Device / tag transmit power. o Uplink scrambling configuration.

[0178] • Why: For gNB to, through the CWT, be able to control and initiate uplink transmission from device / tag.

[0179] • Applicability: For bistatic setup.

[0180] Figure 8 illustrates dynamic reporting and signaling from device / tag to gNB reader, according to some embodiments of the present disclosure. In general, the UL transmission from the device / tag should follow the configuration provided by the CWT via Cu interface (discussed above) and could include the following control information:

[0181] • Device / tag ID

[0182] • CWT ID from which CW was received.

[0183] • CW beam index

[0184] • gNB ID

[0185] In some embodiments, the UL transmission from the device / tag can also include information such as sensor reports, positioning information, downlink signal strength, downlink channel quality, etc.

[0186] The embodiments described above assume that both CW (for the purposes of powering up the tag and backscatter UL transmission) and DL data are transmitted to the device / tag from the CWT. In other embodiments, the CW is transmitted by CWT and the DL data is transmitted by the gNB / reader. In this case, one or more of the semi-static and dynamic control information (e.g., related to DL transmission configuration) do not need to be sent to the CWT from the gNB / reader.

[0187] The CWTs shown in Figures 1-8 and described above do not need to be a network node dedicated for that purpose. For example, the CWT can be a UE (e.g., an NR UE), a relay node, an integrated access backhaul (IAB) node, a repeater, etc. In some of these embodiments, the Xn ’ interface is not by a gNB to configure the CWT. For example, if the CWT is a UE, then the gNB will configure the CWT / UE over the Uu interface.

[0188] For devices that rely on RF power harvesting, one or more predefined frequencies can be configured for the device, which can tune to these frequency(ies) for harvesting RF power to facilitate power up. The predefined frequencies may be common to all devices / tags in a deployment environment (e.g., a warehouse), to a group of devices, or to an individual device. A gNB / reader may have information about these predefined frequencies that the devices will tune to at power-up, and thus can trigger transmission of one or more CWTs on that frequency.

[0189] Once a device has powered up using this harvested energy, the device may need to receive the semi-static broadcast information described above. The broadcast information can be transmitted from the CWT on the same frequency as the predefined frequency, or it can be transmitted in a different frequency. In the case of the broadcast information being transmitted on the same frequency, the signal can be split in time between CW-only transmission and broadcast information transmission. In the case of the broadcast information being transmitted on a different frequency, the device finds the broadcast information frequency by scanning a set of candidate frequencies. Alternatively, there may be a fixed offset or a set of offsets from the predefined frequency where the device can attempt to acquire the broadcast information.

[0190] The device’s power-up procedure described above may be repeated as needed to harvest energy and / or acquire up-to-date configuration information, such as when the device runs out of power and / or when it moves to a coverage area of a different CWT or a different reader / gNB. For example, the device may monitor the broadcast transmission and detect that it has moved to another coverage area by detecting a change in the broadcast transmission.

[0191] In some embodiments, the CWT nodes can be used not only by passive devices / tags but also by active devices that have their own signal generation and do not rely on backscattering. If CWT nodes have been deployed in a network to provide passive devices with signals that can be backscattered, it may be beneficial to also allow active devices to improve their performance by using the CWT nodes as assistance nodes.

[0192] Active devices can receive similar configuration information from the CWT nodes or from the gNB nodes as received by passive devices. Once an active device has been configured, it has knowledge of one or more CWT nodes and can use the signals from the CWT nodes. If an active device is closer to a CWT node than to the closest gNB, the device may receive the signal from the CWT node with better strength or quality compared to the signal from the closest gNB. In some embodiments, one or more CWT nodes at known and / or fixed locations may also serve as additional geographical reference points beside the gNBs. For example, devices may be able to exploit stronger signals and / or additional reference points provided by CWTs for improved positioning performance or improved mobility support.

[0193] The embodiments described above can be further illustrated with reference to Figures 9- 11, which depict exemplary methods (e.g, procedures) for a reader node, a CWT node, and a device, respectively. Put differently, various features of the operations described below correspond to various embodiments described above. The exemplary methods shown in Figures 9-11 can be complementary to each other such that they can be used cooperatively to provide benefits, advantages, and / or solutions to problems described herein. Although the exemplary methods are illustrated in Figures 9-11 by specific blocks in particular orders, the operations corresponding to the blocks can be performed in different orders than shown and can be combined and / or divided into operations having different functionality than shown. Optional blocks and / or operations are indicated by dashed lines.

[0194] More specifically, Figure 9 illustrates an exemplary method (e.g, procedure) for a reader node configured to receive modulated carrier waves (CWs) in a RAN, according to various embodiments of the present disclosure. The exemplary method shown in Figure 9 can be performed by a reader node (e.g., RAN node, gNB, etc.) such as described elsewhere herein.

[0195] The exemplary method includes the operations of block 1010, where the reader node can send one or more of the following control information to a CW transmitter (CWT) node:

[0196] • semi-static control information for the CWT node;

[0197] • semi-static control information for wireless devices that receive CWs transmitted by the CWT node;

[0198] • dynamic control information for the CWT node; and

[0199] • dynamic control information for a first one of the wireless devices.

[0200] The exemplary method also includes the operations of block 1020, where the reader node can receive a CW from the first wireless device. One or more of the following applies:

[0201] • the received CW was transmitted by the CWT node in accordance with the semi-static and / or dynamic control information for the CWT node; and

[0202] • the received CW was modulated by the first wireless device in accordance with the semistatic and / or dynamic control information for wireless devices.

[0203] In some embodiments, the semi-static control information for the CWT node includes one or more of the following: • an indication that that CWT node is associated with and / or controlled by the reader node;

[0204] • an identifier of the reader node;

[0205] • an identifier of the CWT node; and

[0206] • a configuration for CWs transmitted by the CWT node.

[0207] In some of these embodiments, the configuration for CWs transmitted by the CWT node includes one or more of the following:

[0208] • frequency to be used;

[0209] • transmit power to be used;

[0210] • spatial direction and / or beam to be used;

[0211] • timing to be used;

[0212] • uplink / downlink duplexing configuration to be used; and

[0213] • whether to include a control header and if included, control header format.

[0214] In some of these embodiments, the semi-static control information for the CWT node also includes one or more of the following:

[0215] • a configuration for downlink data transmission by the CWT node to wireless devices; and

[0216] • a configuration for broadcasting by the CWT node at least a portion of one or more of the following: the semi-static control information for the CWT node, and the semi-static control information for wireless devices.

[0217] In some of these embodiments, the semi-static control information for the wireless devices includes the following:

[0218] • respective identifiers of one or more wireless devices;

[0219] • a configuration used by the reader node for receiving modulated CWs from wireless devices; and

[0220] • at least a portion of the semi-static control information for the CWT node.

[0221] In some embodiments, the dynamic control information for the CWT node includes one or more of the following:

[0222] • a command to initiate downlink (DL) data transmission by the CWT to the first wireless device;

[0223] • identifiers of one or more of the following: the first wireless device, the CWT node, and the reader node;

[0224] • a configuration for a CW transmission to the first wireless device;

[0225] • physical layer parameters to be used for the DL data transmission to the first wireless device; and

[0226] • the DL data to be transmitted to the first wireless device. In some of these embodiments, the configuration for the CW transmission to the first wireless device includes one or more of the following for the CW transmission: timing information, frequency information, and spatial or beam information. In some of these embodiments, the physical layer parameters to be used for the DL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, and acknowledgement format.

[0227] In some embodiments, the dynamic control information for the CWT node includes one or more of the following:

[0228] • a command to transmit a CW that initiates an uplink (UL) data transmission by the first wireless device; and

[0229] • identifiers of one or more of the following: the first wireless device, the CWT node, and the reader node.

[0230] In some of these embodiments, the dynamic control information for the first wireless device includes one or more of the following:

[0231] • physical layer parameters to be used by the first wireless device for uplink (UL) data transmission to the reader node; and

[0232] • at least a portion of the dynamic control information for the CWT node.

[0233] In some variants of these embodiments, the physical layer parameters to be used by the first wireless device for the UL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, transmit power, scrambling configuration, and acknowledgement format.

[0234] In some variants of these embodiments, the exemplary method can also include the operations of block 1040, where the reader node can receive, from the first wireless device, the UL data transmission in accordance with the physical layer parameters included in the dynamic control information for the first wireless device.

[0235] In some embodiments, the exemplary method can also include the operations of block 1030, where the reader node can demodulate one or more of the following information from the received CW: an identifier of the first wireless device, an identifier of the reader node, an identifier of the CWT node, and an identifier of a beam used by the CWT node to transmit the CW received from the wireless device.

[0236] In some embodiments, the reader node is a RAN node configured to provide wireless access to user equipment (UEs). In some embodiments, the CWT node is one of the following: a second RAN node, a transmission reception point (TRP) of the RAN node, an integrated access backhaul (IAB), a repeater node, and a UE.

[0237] In addition, Figure 10 illustrates an exemplary method (e.g, procedure) for a CWT node configured to operate in a RAN, according to various embodiments of the present disclosure. The exemplary method shown in Figure 10 can be performed by a CWT node (e.g., RAN node, TRP, IAB node, repeater, UE, etc.) such as described elsewhere herein.

[0238] The exemplary method includes the operations of block 1110, where the CWT node can receive one or more of the following control information from a reader node in the RAN:

[0239] • semi-static control information for the CWT node;

[0240] • semi-static control information for wireless devices that receive CWs transmitted by the CWT node;

[0241] • dynamic control information for the CWT node; and

[0242] • dynamic control information for a first one of the wireless devices.

[0243] The exemplary method also include the operations of blocks 1120-1130, where the CWT node can broadcast the semi-static control information for wireless devices and transmit, to the first wireless device, the dynamic control information for the first wireless device. The exemplary method can also include the operations of block 1140, where the CWT node can subsequently transmit a CW to the first wireless device in accordance with the received control information.

[0244] In various embodiments, the semi-static control information for the CWT node can include any of the corresponding content and / or structure described above in relation to the reader node embodiments shown in Figure 9.

[0245] In various embodiments, the semi-static control information for wireless devices can include any of the corresponding content and / or structure described above in relation to the reader node embodiments shown in Figure 9.

[0246] In various embodiments, the dynamic control information for the CWT node can include any of the corresponding content and / or structure described above in relation to the reader node embodiments shown in Figure 9.

[0247] In various embodiments, the dynamic control information for wireless devices can include any of the corresponding content and / or structure described above in relation to the reader node embodiments shown in Figure 9.

[0248] In some embodiments, when the dynamic control information for the CWT node includes a command to initiate DL data transmission by the CWT to the first wireless device and physical layer parameters to be used for the DL data transmission to the first wireless device, such as described above, the exemplary method can also include the operations of block 1150, where the CWT node can transmit the DL data to the first wireless device in accordance with at least the command and the physical layer parameters.

[0249] In some of these embodiments, the dynamic control information for the first wireless device is transmitted in a fixed-format control header that precedes the DL data. In some of these embodiments, the semi-static control information for the CWT node indicates a CW charging period prior to DL data transmissions, and the CW is transmitted in block 1130 for the indicated CW charging period prior to transmitting the DL data to the first wireless device in block 1150.

[0250] In some embodiments, when the dynamic control information for the CWT node includes a command to transmit a CW that initiates an UL data transmission by the first wireless device, transmitting the CW in block 1130 is responsive to the command.

[0251] In some embodiments, the reader node is a RAN node configured to provide wireless access to user equipment (UEs). In some embodiments, the CWT node is one of the following: a second RAN node, a transmission reception point (TRP) of the RAN node, an integrated access backhaul (IAB), a repeater node, and a UE.

[0252] In addition, Figure 11 illustrates an exemplary method (e.g, procedure) for a wireless device configured to receive carrier waves (CWs) in a RAN, according to various embodiments of the present disclosure. The exemplary method shown in Figure 11 can be performed by a wireless device (e.g., tag, passive device, active device, etc.) such as described elsewhere herein.

[0253] The exemplary method includes the operations of block 1210, where the wireless device can receive, as broadcast by a CW transmitter (CWT) node, a semi-static control information for wireless devices that receive CWs transmitted by the CWT node. The exemplary method also includes the operations of block 1230, where the wireless device can receive a CW transmitted by the CWT node and modulate the received CW for reception by a reader node in the RAN, in accordance with the received semi-static control information.

[0254] In some embodiments, one or more of the following is modulated onto the received CW: an identifier of the wireless device, an identifier of the reader node, an identifier of the CWT node, and an identifier of a beam used by the CWT node to transmit the CW received by the wireless device.

[0255] In some embodiments, the semi-static control information for wireless devices includes one or more of the following:

[0256] • respective identifiers of one or more wireless devices, including the wireless device;

[0257] • a configuration used by a reader node in the RAN for receiving modulated CWs from wireless devices; and

[0258] • an indication that that CWT node is associated with and / or controlled by the reader node;

[0259] • an identifier of the reader node; • an identifier of the CWT node; and

[0260] • a configuration for CWs transmitted by the CWT node.

[0261] In various embodiments, the configuration for CWs transmitted by the CWT node can include any of the corresponding content and / or structure described above in relation to the reader node embodiments shown in Figure 9.

[0262] In some embodiments, the semi-static control information for wireless devices also includes a configuration for DL data transmission by the CWT node to wireless devices, and the exemplary method also includes the operations of block 1240, where the wireless device can receive DL data transmitted by the CWT node, in accordance with the configuration for DL data transmission. In some of these embodiments, the semi-static control information indicates a CW charging period prior to DL data transmissions and the CW is received in block 1230 for the indicated CW charging period prior to receiving the DL data in block 1240.

[0263] In some embodiments, the exemplary method can also include the operations of block 1220, where the wireless device can receive, from the CWT node, dynamic control information for the wireless device. In some of these embodiments, the dynamic control information for the first wireless device is received in a fixed-format control header that follows the CW.

[0264] In some of these embodiments, the dynamic control information for the wireless device includes physical layer parameters to be used for a DL data transmission to the first wireless device, and the exemplary method also includes the operations of block 1250, where the wireless device receives the DL data transmission from the CWT node in accordance with the physical layer parameters. Note that the receiving operations of block 1250 can be the same as the receiving operations of block 1240, in case the wireless device uses both semi-static and dynamic control information to receive the DL data.

[0265] In some variants of these embodiments, the physical layer parameters to be used for the DL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, and acknowledgement format.

[0266] In other of these embodiments, the dynamic control information for the first wireless device includes physical layer parameters to be used by the first wireless device for UL data transmission to the reader node, and the exemplary method also includes the operations of block 1260, where the wireless device transmits UL data to the CWT node in accordance with the physical layer parameters. In some variants of these embodiments, transmitting the UL data in block 1260 is responsive to receiving the CW in block 1230.

[0267] In some variants of these embodiments, the physical layer parameters to be used by the first wireless device for the UL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, transmit power, scrambling configuration, and acknowledgement format.

[0268] In some embodiments, the reader node is a RAN node configured to provide wireless access to user equipment (UEs). In some embodiments, the CWT node is one of the following: a second RAN node, a transmission reception point (TRP) of the RAN node, an integrated access backhaul (IAB), a repeater node, and a UE.

[0269] In some embodiments, the wireless device is one of the following: a passive device configured to use energy harvested from the received CW as a power source, or an active device with a power source that is independent of the received CW.

[0270] Other embodiments include reader nodes, CWT nodes, and wireless devices that are configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer-readable media storing computerexecutable instructions that, when executed by processing circuitry, configure such PEMC UEs, PIN AS’s, AUSFs, and interface functions to perform operations corresponding to any of the exemplary methods described herein.

[0271] These and other embodiments described herein can provide configurability and flexibility for bistatic backscattering communication for passive wireless devices, as well as dynamic control and more advanced functionality. More generally, embodiments can facilitate deployment of “Ambient loT” in conjunction with 3GPP networks (e.g., 5G). Although various embodiments are described above in terms of methods, techniques, and / or procedures, the person of ordinary skill will readily comprehend that such methods, techniques, and / or procedures can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc.

[0272] Although various embodiments are described herein above in terms of methods, apparatus, devices, computer-readable medium and receivers, the person of ordinary skill will readily comprehend that such methods can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, etc.

[0273] Figure 12 shows an example of a communication system 1300 in accordance with some embodiments. In this example, communication system 1300 includes a telecommunication network 1302 that includes an access network 1304 (e.g., RAN) and a core network 1306, which includes one or more core network nodes 1308. Access network 1304 includes one or more access network nodes, such as network nodes 1310a-b (one or more of which may be generally referred to as network nodes 1310), or any other similar 3GPP access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, telecommunication network 1302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in telecommunication network 1302 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in telecommunication network 1302, including one or more network nodes 1310 and / or core network nodes 1308.

[0274] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adj ective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. Network nodes 1310 facilitate direct or indirect connection of UEs, such as by connecting UEs 1312a-d (one or more of which may be generally referred to as UEs 1312) to core network 1306 over one or more wireless connections.

[0275] 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, communication system 1300 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. Communication system 1300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

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

[0277] In the depicted example, core network 1306 connects network nodes 1310 to one or more hosts, such as host 1316. 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. Core network 1306 includes one or more core network nodes (e.g., 1308) 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 core network node 1308. 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).

[0278] Host 1316 may be under the ownership or control of a service provider other than an operator or provider of access network 1304 and / or telecommunication network 1302, and may be operated by the service provider or on behalf of the service provider. Host 1316 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.

[0279] As a whole, communication system 1300 of Figure 12 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.

[0280] In some examples, telecommunication network 1302 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunication network 1302 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 1302. For example, telecommunication network 1302 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.

[0281] In some examples, UEs 1312 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to access network 1304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1304. 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).

[0282] In the example, hub 1314 communicates with access network 1304 to facilitate indirect communication between one or more UEs (e.g., UE 1312c and / or 1312d) and network nodes (e.g., network node 1310b). In some examples, hub 1314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 1314 may be a broadband router enabling access to core network 1306 for the UEs. As another example, hub 1314 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 1310, or by executable code, script, process, or other instructions in hub 1314. As another example, hub 1314 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, hub 1314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, hub 1314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

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

[0284] Figure 13 shows a UE 1400 in accordance with some embodiments. 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, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by 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.

[0285] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP 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).

[0286] UE 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input / output interface 1406, a power source 1408, a memory 1410, a communication interface 1412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 13. 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.

[0287] Processing circuitry 1402 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 memory 1410. Processing circuitry 1402 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, processing circuitry 1402 may include multiple central processing units (CPUs).

[0288] In the example, input / output interface 1406 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 UE 1400. 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.

[0289] In some embodiments, power source 1408 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. Power source 1408 may further include power circuitry for delivering power from power source 1408 itself, and / or an external power source, to the various parts of UE 1400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 1408. Power circuitry may perform any formatting, converting, or other modification to the power from power source 1408 to make the power suitable for the respective components of UE 1400 to which power is supplied. Memory 1410 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, memory 1410 includes one or more application programs 1414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1416. Memory 1410 may store, for use by UE 1400, any of a variety of various operating systems or combinations of operating systems.

[0290] Memory 1410 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.’ Memory 1410 may allow UE 1400 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 memory 1410, which may be or comprise a device-readable storage medium.

[0291] Processing circuitry 1402 may be configured to communicate with an access network or other network using communication interface 1412. Communication interface 1412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1422. Communication interface 1412 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 1418 and / or a receiver 1420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, transmitter 1418 and receiver 1420 may be coupled to one or more antennas (e.g., antenna 1422) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0292] In the illustrated embodiment, communication functions of communication interface 1412 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0293] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1412, 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).

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

[0295] 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 UE 1400 shown in Figure 13.

[0296] 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 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP 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.

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

[0298] Figure 14 shows a network node 1500 in accordance with some embodiments. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (e.g., radio base stations, Node Bs, eNBs, gNBs), and O-RAN nodes or components of an O-RAN node (e g., O-RU, O-DU, O-CU).

[0299] 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, distributed units (e.g., in an O-RAN access node) 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).

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

[0301] Network node 1500 includes a processing circuitry 1502, a memory 1504, a communication interface 1506, and a power source 1508. Network node 1500 may be composed of multiple physically separate components (e.g., aNodeB 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 network node 1500 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, network node 1500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1504 for different RATs) and some components may be reused (e.g., a same antenna 1510 may be shared by different RATs). Network node 1500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1500, 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 1500.

[0302] The processing circuitry 1502 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 1500 components, such as memory 1504, to provide network node 1500 functionality.

[0303] In some embodiments, the processing circuitry 1502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1502 includes one or more of radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514. In some embodiments, RF transceiver circuitry 1512 and baseband processing circuitry 1514 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 1512 and baseband processing circuitry 1514 may be on the same chip or set of chips, boards, or units. Memory 1504 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 1502. Memory 1504 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 (collected denoted computer program 1504a, which may be in the form of a computer program product) capable of being executed by the processing circuitry 1502 and utilized by network node 1500. Memory 1504 may be used to store any calculations made by the processing circuitry 1502 and / or any data received via communication interface 1506. In some embodiments, the processing circuitry 1502 and memory 1504 is integrated.

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

[0305] In certain alternative embodiments, network node 1500 does not include separate radio front-end circuitry 1518, instead, the processing circuitry 1502 includes radio front-end circuitry and is connected to antenna 1510. Similarly, in some embodiments, all or some of RF transceiver circuitry 1512 is part of communication interface 1506. In still other embodiments, communication interface 1506 includes one or more ports or terminals 1516, radio front-end circuitry 1518, and RF transceiver circuitry 1512, as part of a radio unit (not shown), and communication interface 1506 communicates with baseband processing circuitry 1514, which is part of a digital unit (not shown).

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

[0307] Antenna 1510, communication interface 1506, and / or the processing circuitry 1502 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, antenna 1510, communication interface 1506, and / or the processing circuitry 1502 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.

[0308] Power source 1508 provides power to the various components of network node 1500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1508 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1500 with power for performing the functionality described herein. For example, network node 1500 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 power source 1508. As a further example, power source 1508 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.

[0309] Embodiments of network node 1500 may include additional components beyond those shown in Figure 14 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, network node 1500 may include user interface equipment to allow input of information into network node 1500 and to allow output of information from network node 1500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1500.

[0310] Figure 15 is a block diagram illustrating a virtualization environment 1600 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 1600 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. In some embodiments, the virtualization environment 1600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

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

[0312] Hardware 1604 includes processing circuitry, memory that stores software and / or instructions (collected denoted computer program 1604a, which may be in the form of a computer program product) 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 1606 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1608a and 1608b (one or more of which may be generally referred to as VMs 1608), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. Virtualization layer 1606 may present a virtual operating platform that appears like networking hardware to the VMs 1608.

[0313] VMs 1608 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1606. Different embodiments of the instance of a virtual appliance 1602 may be implemented on one or more of VMs 1608, 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. In the context of NFV, each VM 1608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each VM 1608, and that part of hardware 1604 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 1608 on top of the hardware 1604 and corresponds to the application 1602.

[0314] Hardware 1604 may be implemented in a standalone network node with generic or specific components. Hardware 1604 may implement some functions via virtualization. Alternatively, hardware 1604 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 function 1610, which, among others, oversees lifecycle management of applications 1602. In some embodiments, hardware 1604 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 1612 which may alternatively be used for communication between hardware nodes and radio units.

[0315] The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

[0316] The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and / or electronic devices and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.

[0317] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0318] As described herein, device and / or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and / or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

[0319] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0320] In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). It should be understood, that although these terms (and / or other terms that can be synonymous to one another) can be used synonymously herein, there can be instances when such words can be intended to not be used synonymously.

[0321] Example embodiments Al . A method for a reader node configured to receive modulated carrier waves (CWs) in a radio access network (RAN), the method comprising: sending one or more of the following control information to a CW transmitter (CWT) node: semi-static control information for the CWT node; semi-static control information for wireless devices that receive CWs transmitted by the CWT node; dynamic control information for the CWT node; and dynamic control information for a first one of the wireless devices; receiving a CW from the first wireless device, wherein one or more of the following applies: the received CW was transmitted by the CWT node in accordance with the semistatic and / or dynamic control information for the CWT node; and the received CW was modulated by the first wireless device in accordance with the semi-static and / or dynamic control information for wireless devices.

[0322] A2. The method of embodiment Al, wherein the semi-static control information for the CWT node includes one or more of the following: an indication that that CWT node is associated with and / or controlled by the reader node; an identifier of the reader node; an identifier of the CWT node; and a configuration for CWs transmitted by the CWT node.

[0323] A2a. The method of embodiment A2, wherein the configuration for CWs transmitted by the

[0324] CWT node includes one or more of the following: frequency to be used; transmit power to be used; spatial direction and / or beam to be used; timing to be used; uplink / downlink duplexing configuration to be used; and whether to include a control header and if included, control header format.

[0325] A2b. The method of any of embodiments A2-A2a, wherein the semi-static control information for the CWT node also includes one or more of the following: a configuration for downlink data transmission by the CWT node to wireless devices; and a configuration for broadcasting by the CWT node at least a portion of one or more of the following: the semi-static control information for the CWT node; and the semi-static control information for wireless devices.

[0326] A2c. The method of any of embodiments A2-A2b, wherein the semi-static control information for the wireless devices includes the following: respective identifiers of one or more wireless devices; a configuration used by the reader node for receiving modulated CWs from wireless devices; and at least a portion of the semi-static control information for the CWT node.

[0327] A3. The method of any of embodiments Al-A2c, wherein the dynamic control information for the CWT node includes one or more of the following: a command to initiate downlink (DL) data transmission by the CWT to the first wireless device; identifiers of one or more of the following: the first wireless device, the CWT node, and the reader node; a configuration for a CW transmission to the first wireless device; physical layer parameters to be used for the DL data transmission to the first wireless device; and the DL data to be transmitted to the first wireless device.

[0328] A3a. The method of embodiment A3, wherein one or more of the following applies: the configuration for the CW transmission to the first wireless device includes one or more of the following for the CW transmission: timing information, frequency information, and spatial or beam information; and the physical layer parameters to be used for the DL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, and acknowledgement format. A4. The method of any of embodiments A1-A2, wherein the dynamic control information for the CWT node includes one or more of the following: a command to transmit a CW that initiates an uplink (UL) data transmission by the first wireless device; and identifiers of one or more of the following: the first wireless device, the CWT node, and the reader node.

[0329] A5. The method of any of embodiments A3-A4, wherein the dynamic control information for the first wireless device includes one or more of the following: physical layer parameters to be used by the first wireless device for uplink (UL) data transmission to the reader node; and at least a portion of the dynamic control information for the CWT node.

[0330] A5a. The method of embodiment A5, wherein the physical layer parameters to be used by the first wireless device for the UL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, transmit power, scrambling configuration, and acknowledgement format.

[0331] A6. The method of any of embodiments A5-A5a, further comprising receiving, from the first wireless device, the UL data transmission in accordance with the physical layer parameters included in the dynamic control information for the first wireless device.

[0332] A7. The method of any of embodiments A1-A6, further comprising demodulating one or more of the following information from the received CW: an identifier of the first wireless device, an identifier of the reader node, an identifier of the CWT node, and an identifier of a beam used by the CWT node to transmit the CW received from the wireless device.

[0333] A8. The method of any of embodiments A1-A7, wherein one or more of the following applies: the reader node is a RAN node configured to provide wireless access to user equipment (UEs); and the CWT is one of the following: a second RAN node, a transmission reception point (TRP) of the RAN node, an integrated access backhaul (IAB), a repeater node, and a UE. Bl . A method for a carrier wave transmitter (CWT) node configured to operate in a radio access network (RAN), the method comprising: receiving one or more of the following control information from a reader node in the

[0334] RAN: semi-static control information for the CWT node; semi-static control information for wireless devices that receive CWs transmitted by the CWT node; dynamic control information for the CWT node; and dynamic control information for a first one of the wireless devices; broadcasting the semi-static control information for wireless devices; transmitting, to the first wireless device, the dynamic control information for the first wireless device; and subsequently transmitting a CW to the first wireless device in accordance with the received control information.

[0335] B2. The method of embodiment Bl, wherein the semi-static control information for the CWT node includes one or more of the following: an indication that that CWT node is associated with and / or controlled by the reader node; an identifier of the reader node; an identifier of the CWT node; and a configuration for CWs transmitted by the CWT node.

[0336] B2a. The method of embodiment B2, wherein the configuration for CWs transmitted by the

[0337] CWT node includes one or more of the following: frequency to be used; transmit power to be used; spatial direction and / or beam to be used; timing to be used; uplink / downlink duplexing configuration to be used; and whether to include a control header and if included, control header format.

[0338] B2b. The method of any of embodiments B2-B2a, wherein the semi-static control information for the CWT node also includes one or more of the following: a configuration for downlink (DL) data transmission by the CWT node to wireless devices; and a configuration for broadcasting by the CWT node at least a portion of one or more of the following: the semi-static control information for the CWT node; and the semi-static control information for wireless devices.

[0339] B2c. The method of any of embodiments B2-B2b, wherein the semi-static control information for wireless devices includes the following: respective identifiers of one or more wireless devices; a configuration used by the reader node for receiving modulated CWs from wireless devices; and at least a portion of the semi-static control information for the CWT node.

[0340] B3. The method of any of embodiments Bl-B2c, wherein the dynamic control information for the CWT node includes one or more of the following: a command to initiate downlink (DL) data transmission by the CWT to the first wireless device; identifiers of one or more of the following: the first wireless device, the CWT node, and the reader node; a configuration for a CW transmission to the first wireless device; physical layer parameters to be used for the DL data transmission to the first wireless device; and the DL data to be transmitted to the first wireless device.

[0341] B3a. The method of embodiment B3, further comprising transmitting the DL data to the first wireless device in accordance with at least the command and the physical layer parameters.

[0342] B3b. The method of embodiment B3a, wherein the dynamic control information for the first wireless device is transmitted in a fixed-format control header that precedes the DL data.

[0343] B3c. The method of any of embodiments B3a-B3b, wherein the semi-static control information for the CWT node indicates a CW charging period prior to DL data transmissions, and the CW is transmitted for the indicated CW charging period prior to transmitting the DL data to the first wireless device. B3d. The method of any of embodiments B3-B3c, wherein one or more of the following applies: the configuration for the CW transmission to the first wireless device includes one or more of the following for the CW transmission: timing information, frequency information, and spatial or beam information; and the physical layer parameters to be used for the DL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, and acknowledgement format.

[0344] B4. The method of any of embodiments B1-B2, wherein the dynamic control information for the CWT node includes one or more of the following: a command to transmit a CW that initiates an uplink (UL) data transmission by the first wireless device; and identifiers of one or more of the following: the first wireless device, the CWT node, and the reader node.

[0345] B4a. The method of embodiment B4, wherein transmitting the CW is responsive to the command.

[0346] B5. The method of any of embodiments B3-B4a, wherein the dynamic control information for the first wireless device includes one or more of the following: physical layer parameters to be used by the first wireless device for uplink (UL) data transmission to the reader node; and at least a portion of the dynamic control information for the CWT node.

[0347] B5a. The method of embodiment B5, wherein the physical layer parameters to be used by the first wireless device for the UL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, transmit power, scrambling configuration, and acknowledgement format.

[0348] B6. The method of any of embodiments Bl-B5a, wherein one or more of the following applies: the reader node is a RAN node configured to provide wireless access to user equipment (UEs); and the CWT node is one of the following: a second RAN node, a transmission reception point (TRP) of the RAN node, an integrated access backhaul (IAB), a repeater node, and a UE.

[0349] Cl . A method for a wireless device configured to receive carrier waves (CWs) in a radio access network (RAN), the method comprising: receiving, as broadcast by a CW transmitter (CWT) node, a semi-static control information for wireless devices that receive CWs transmitted by the CWT node; and receiving a CW transmitted by the CWT node and modulating the received CW for reception by a reader node in the RAN, in accordance with the received semistatic control information.

[0350] Cl a. The method of embodiment Cl, wherein one or more of the following is modulated onto the received CW: an identifier of the wireless device, an identifier of the reader node, an identifier of the CWT node, and an identifier of a beam used by the CWT node to transmit the CW received by the wireless device.

[0351] C2. The method of any of embodiments Cl -Cl a, wherein the semi-static control information for wireless devices includes one or more of the following: respective identifiers of one or more wireless devices, including the wireless device; a configuration used by a reader node in the RAN for receiving modulated CWs from wireless devices; and an indication that that CWT node is associated with and / or controlled by the reader node; an identifier of the reader node; an identifier of the CWT node; and a configuration for CWs transmitted by the CWT node.

[0352] C2a. The method of embodiment C2, wherein the configuration for CWs transmitted by the CWT node includes one or more of the following: frequency to be used; transmit power to be used; spatial direction and / or beam to be used; timing to be used; uplink / downlink duplexing configuration to be used; and whether to include a control header and if included, control header format.

[0353] C2b. The method of any of embodiments C2-C2a, wherein: the semi-static control information for wireless devices also includes a configuration for downlink (DL) data transmission by the CWT node to wireless devices; and the method further comprises receiving DL data transmitted by the CWT node, in accordance with at least the configuration for DL data transmission.

[0354] C2c. The method of embodiment C2b, wherein: the semi-static control information indicates a CW charging period prior to DL data transmissions; and the CW is received for the indicated CW charging period prior to receiving the DL data.

[0355] C3. The method of any of embodiments Cl-C2b, further comprising receiving, from the CWT node, dynamic control information for the wireless device.

[0356] C3a. The method of embodiment C3, wherein the dynamic control information for the wireless device is received in a fixed-format control header that follows the CW.

[0357] C4. The method of any of embodiments C3-C3a, wherein: the dynamic control information for the wireless device includes physical layer parameters to be used for a DL data transmission to the first wireless device; and the method further comprises receiving the DL data transmission from the CWT node in accordance with the physical layer parameters.

[0358] C4a. The method of embodiment C4, wherein the physical layer parameters to be used for the DL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, and acknowledgement format.

[0359] C5. The method of any of embodiments C3-C3a, wherein: the dynamic control information for the first wireless device includes physical layer parameters to be used by the first wireless device for uplink (UL) data transmission to the reader node; and the method further comprises transmitting UL data to the CWT node in accordance with the physical layer parameters.

[0360] C5a. The method of embodiment C5, wherein transmitting the UL data is responsive to receiving the CW.

[0361] C5b. The method of any of embodiments C5-C5a, wherein the physical layer parameters to be used by the first wireless device for the UL data transmission include one or more of the following: transport block size (TBS), modulation and coding scheme (MCS), resource allocation in time and / or frequency, dynamic frequency offset, repetition factor, transmit power, scrambling configuration, and acknowledgement format.

[0362] C6. The method of any of embodiments Cl-C5b, wherein one or more of the following applies: the reader node is a RAN node configured to provide wireless access to user equipment (UEs); and the CWT is one of the following: a second RAN node, a transmission reception point (TRP) of the RAN node, an integrated access backhaul (IAB), a repeater node, and a UE.

[0363] C7. The method of any of embodiments C1-C6, wherein the wireless device is one of the following: a passive device configured to use energy harvested from the received CW as a power source, or an active device with a power source that is independent of the received CW.

[0364] DI. A reader node configured operate in a radio access network (RAN), the reader node comprising: communication interface circuitry configured to communicate with one or more carrier wave transmitter (CWT) nodes in the RAN, and to receive modulated versions of carrier waves (CWs) transmitted by the one or more CWT nodes; and processing circuitry operably coupled to the communication interface circuitry, whereby the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments A1-A8. D2. A reader node configured receive modulated versions of carrier waves (CWs) transmitted by the one or more CWT nodes in a radio access network (RAN), the reader node being further configured to perform operations corresponding to any of the methods of embodiments A1-A8.

[0365] D3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a reader node configured receive modulated versions of carrier waves (CWs) transmitted by the one or more CWT nodes in a radio access network (RAN), configure the reader node to perform operations corresponding to any of the methods of embodiments A1-A8.

[0366] D4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a processing circuitry of a reader node configured receive modulated versions of carrier waves (CWs) transmitted by the one or more CWT nodes in a radio access network (RAN), configure the reader node to perform operations corresponding to any of the methods of embodiments A1-A8.

[0367] El. A carrier wave transmitter (CWT) node configured to operate in a radio access network (RAN), the CWT node comprising: communication interface circuitry configured to transmit carrier waves (CWs) and to communicate with a reader node in the RAN; and processing circuitry operably coupled to the communication interface circuitry, whereby the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments B1-B6.

[0368] E2. A carrier wave transmitter (CWT) node configured to operate in a radio access network (RAN), the CWT node being further configured to perform operations corresponding to any of the methods of embodiments B1-B6.

[0369] E3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a carrier wave transmitter (CWT) node configured to operate in a radio access network (RAN), configure the CWT node to perform operations corresponding to any of the methods of embodiments B1-B6. E4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a carrier wave transmitter (CWT) node configured to operate in a radio access network (RAN), configure the CWT node to perform operations corresponding to any of the methods of embodiments B1-B6.

[0370] Fl . A wireless device configured to receive carrier waves (CWs) in a radio access network (RAN), comprising: communication interface circuitry configured to receive carrier waves (CWs) and to transmit modulated versions of the received CWs; and processing circuitry operably coupled to the communication interface circuitry, whereby the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments C1-C7.

[0371] F2. A carrier wave transmitter (CWT) node configured to operate in a radio access network (RAN), the CWT node being further configured to perform operations corresponding to any of the methods of embodiments C1-C7.

[0372] F3. The wireless device of any of claims F1-F2, further comprising a power source configured to harvest energy from received CWs and to provide the harvested energy to the communication interface circuitry and the processing circuitry.

[0373] F4. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a wireless device configured to receive carrier waves (CWs) in a radio access network (RAN), configure the wireless device to perform operations corresponding to any of the methods of embodiments C1-C7.

[0374] F5. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a wireless device configured to receive carrier waves (CWs) in a radio access network (RAN), configure the wireless device to perform operations corresponding to any of the methods of embodiments C1-C7.

[0375] Positioning in the context of backscattering communication

[0376] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to determining positioning information associated with wireless devices such as ambient passive devices. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0377] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0378] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0379] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0380] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi -cell / multi cast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), a CWT, a reader node, etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0381] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, a tag, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and / or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device (e.g., a tag) such as, but not limited to a passive Ambient loT device, or a Narrowband loT (NB-IOT) device, etc.

[0382] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0383] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0384] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

[0385] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0386] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in Figure 16 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0387] Also, it is contemplated that a WD 22 can be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0388] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more subnetworks (not shown).

[0389] The communication system of Figure 16 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and / or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0390] A network node 16 is configured to include a network node (NN) management unit 32 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., NN functions. A wireless device 22 is configured to include a WD management unit 34 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., WD functions.

[0391] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to Figure 16. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0392] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

[0393] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54 configured to enable the service provider to observe / monitor / control / transmit to / receive from the network node 16 and or the wireless device 22.

[0394] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0395] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0396] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include NN management unit 32 configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., NN functions.

[0397] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0398] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0399] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0400] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include a WD management unit 34 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., WD functions.

[0401] In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in Figure 17 and independently, the surrounding network topology may be that of Figure 16.

[0402] In Figure 17, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0403] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0404] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0405] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the WD 22.

[0406] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and / or comprises a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the network node 16.

[0407] Although Figures 16 and 17 show various “units” such as NN management unit 32, and WD management unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0408] Some embodiments advantageously provide methods, systems, and apparatuses for determining positioning information associated with ambient passive devices.

[0409] In one or more embodiments, information is included in the carrier wave transmitted from a CWT which is beneficial for the positioning of passive devices. In some embodiments, a CWT identifier (ID) is included in the carrier wave, and a wireless device (e.g., a passive device (Tag)) echoes the CWT ID back to the network and a network node (e.g., a reader) when received. In some other embodiments, a ‘Cell ID’ positioning method is performed for wireless devices (e.g., passive devices) and backs cattering communication.

[0410] Figure 18 is a flowchart of an exemplary process in a network node 16 (e.g., first network node 16). One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the NN management unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60 is configured to receive (Block SI 34), from the WD, signaling associated with a second network node configured as a carrier wave transmitter (CWT), where the signaling includes information usable for determining positioning information at least of the WD, and perform (Block SI 36) one or more actions based on the received signaling.

[0411] In some embodiments, the information includes a CWT identifier (ID).

[0412] In some other embodiments, the method further includes transmitting the CWT ID to the CWT over an Xn’ interface.

[0413] In some embodiments, the method further includes one or more of determining a configuration of the CWT ID for the CWT; determining a configuration to associate the CWT with the first network node; maintaining a list with CWT contexts for each CWT of a plurality of CWTs; requesting and / or determining CWT positioning; and determining a timing offset over an Xn’ interface.

[0414] In some other embodiments, one or more of the first network node 16 is further configured as a reader node, the WD 22 is configured as a passive tag device, the WD 22 is configured for ambient energy harvesting, and the WD 22 is an internet of things device.

[0415] Figure 19 is a flowchart of an exemplary process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the WD management unit 34), processor 86, radio interface 82 and / or communication interface 60. Wireless device 22 such as via processing circuitry 84 and / or processor 86 and / or radio interface 82 is configured to receive (Block S138) first signaling from a second network node, where the first signaling is one of unmodulated and modulated, and transmit (Block S140), to the first network node 16, second signaling based on the first signaling. The second signaling includes information usable for determining positioning information at least of the WD 22.

[0416] In some embodiments, the method further includes one or more of receiving a first unmodulated carrier wave configured to power up the WD 22; receiving an on-off keying (OOK) modulated signal for a time duration (Took), where the OOK modulated signal includes a CWT identifier (ID); demodulating the OOK modulated signal to obtain the CWT ID; after Took has elapsed, receiving a second unmodulated carrier wave; and backs cattering the second unmodulated carrier wave by jointly encoding the CWT ID and a WD ID for the first network node to demodulate the second unmodulated carrier wave to obtain the CWT ID and WD ID.

[0417] In some other embodiments, one or both of the first signaling includes the first unmodulated carrier wave and / or the OOK modulated signal and the second signaling includes the backscattered second unmodulated carrier wave. In some embodiments, the method further includes one or more of receiving a first unmodulated carrier wave configured to power up the WD 22; receiving a first modulated signal that carries a CWT ID, where the first modulated signal has a time duration (Tsignal); backscattering the first modulated signal without encoding any information, where the backscattered first modulated signal being usable by the first network node to obtain the CWT ID; receiving a second unmodulated carrier wave; and backscattering the second unmodulated carrier wave by encoding a WD ID for the first network node to demodulate the second unmodulated carrier wave to obtain the WD ID.

[0418] In some other embodiments, one or both of the first signaling includes the first unmodulated carrier wave and / or the first modulated signal and the second signaling includes the backscattered second unmodulated carrier wave.

[0419] Figure 20 is a flowchart of an exemplary process in a network node 16 (e.g., a second network node 16). One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the NN management unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16 such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60 is configured to transmit (Block S142) first signaling from a second network node. The first signaling is one of unmodulated and modulated. The first signaling is usable by the WD 22 to transmit, to the first network node 16, second signaling based on the first signaling. The second signaling includes information usable for determining positioning information of the WD 22. One or more actions are performed (Block SI 44) based on the first signaling.

[0420] In some embodiments, in the method further includes one or more of transmitting a first unmodulated carrier wave configured to power up the WD 22; transmitting an on-off keying (OOK) modulated signal for a time duration (Took), where the OOK modulated signal includes a CWT identifier (ID); and after Took has elapsed, transmitting a second unmodulated carrier wave usable by the WD 22 to backscatter the second unmodulated carrier wave by jointly encoding the CWT ID and a WD ID.

[0421] In some other embodiments one or both of the first signaling includes the first unmodulated carrier wave and / or the OOK modulated signal and the second signaling includes the backscattered second unmodulated carrier wave.

[0422] In some embodiments, the method further includes one or more of transmitting a first unmodulated carrier wave configured to power up the WD 22; transmitting a first modulated signal that carries a CWT ID, where the first modulated signal has a time duration (Tsignal) and is usable by the WD 22 to backscatter the first modulated signal without encoding any information; and transmitting a second unmodulated carrier wave usable by the WD 22 to encode a WD ID.

[0423] In some other embodiments, one or both of the first signaling includes the first unmodulated carrier wave and / or the first modulated signal and the second signaling includes the backscattered second unmodulated carrier wave.

[0424] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the text below provides details and examples of arrangements for determining positioning information associated with wireless devices such as ambient passive devices.

[0425] In some embodiments, the term reader is used and may be referred to as or be a network node 16 (e.g., a first network node 16). In some other embodiments, the term CWT is used and may be referred to as or be a network node 16 (e.g., a second network node 16). In some embodiments, the term tag is used and may be referred to as or be a wireless device (WD) 22.

[0426] A form of positioning process associated with 3GPP may be referred to as ‘Cell ID’, in which WD positioning becomes known on a cell level, which may be achieved using the paging procedure. For example, WD 22 may be paged in one or more cells, e.g., in the Tracking Area (TA) where the core network knows that the WD 22 may be located. Upon receiving the paging, the WD 22 may start a Random Access procedure and connection setup to inform the network where WD 22 is located.

[0427] For the monostatic backs cattering cases, for ‘Cell ID’ positioning, the network node 16 (e.g., combined reader and CWT) may send out the carrier wave. If the network node 16 receives a response from WDs 22 (e.g., the passive devices (A or B)), network node 16 knows that the corresponding WD 22 is within the coverage of the backscattering communication.

[0428] For the bistatic cases, the bistatic backscattering communication coverage area may be limited by the CWT-to-Tag distance (i.e., a NN to WD distance) due to the WD RF harvesting sensitivity (i.e., activation threshold). For a fixed network deployment, a higher density of CWTs may be used, as illustrated in Figure 2. In this example, network nodes 16 (e.g., gNBs) may be reused as readers to support backscattering communication for WDs 22 (e.g., passive devices (Tags)). In some embodiments, some network nodes 2101 (e.g., such as CWTs) may initially be configured with a ‘CWT ID’, for example over an Xn' interface between CWT and the other network node 2102 (e.g., gNB / reader) as shown in Figure 21. The CWT 2101, when sending the carrier wave, sends an unmodulated signal including control information, e.g., ‘CWT ID’. The wireless device (WD) 2103 (e.g., device / Tag) may include the ‘CWT ID’ in the uplink transmission to the other network node 2102 (e.g., reader / gNB) and its own UE ID, or WD ID. The network (e.g., a network node 2102) may use the CWT ID to determine the WD position (the device / Tag position).

[0429] In some embodiments, the CWT position is determined and communicated to the network node 2102 configured as a gNB / reader (over the Xn' interface). In some other embodiments, such as for a fixed CWT deployment, this may be done at CWT initiation and setup, since the CWT node 2101 is stationary. In some embodiments, where also mobile CWTs are supported, the CWT 2101 would determine its position upon sending out the carrier wave with the ‘CWT_ID’ and report it over Xn' interface to the network node 2102 configured as gNB / reader. Similar to the fixed CWT case, the network would, upon receiving uplink reporting from the device / Tag, be able to determine that WD 2103 is located at up to the max CWT-Tag coverage distance supported from the reported position of the CWT 2101. In this example, the network node 2102 configured as the gNB / reader may be in control of the functionality or be responsible for the following:

[0430] • Configuration of ‘CWT ID’ for the CWT;

[0431] • Configuration to associate the CWT with a gNB / reader, keeping a list with CWT contexts for all the CWTs;

[0432] • Request and / or determination of CWT positioning; and / or

[0433] • Timing offset over Xn’ interface (e.g., included in one or more components of network node 16).

[0434] In some embodiments, a network node 2104for backs cattering communication control is introduced. The network node 2104may be located elsewhere in the network, e.g. in the core network 14, or collocated with a gNB, etc.

[0435] In the case the network node 2104 (e.g., control node) is located in the core network (CN) (or in a RAN registration area), CWTs would not be associated to a gNB / reader. That is, the CN control node 2104 may send a request to a group of CWTs 2101 that it has configured to attempt to determine the position of a WD 2103 (device / Tag). If the WD 2103 is within the coverage area of any of the addressed CWTs 2101, the WD 2103 would respond in uplink, including its own UE ID and the CWT ID of the CWT 2101 it received the carrier wave from. If received by the network node 2102 configured as a reader, the network node 2102 may forward this information to a CN backscattering control node 2104, which could then determine in which CWT coverage area the WD 2103 is located. In some other embodiments, if the uplink signal is read by multiple readers 2102, there may be multiple reports at the CN backscattering control node 2104 reporting the same CWT position for the device / Tag. In some embodiments, the network node 2102 configured as the reader is a mobile node. The network node 2102 may have to request the position of a CWT from a CN node storing the CWTs configured in the network or tracking area.

[0436] Example solution #1

[0437] In a scenario with dedicated CWT (i.e., when CWT and reader are non-collocated), CWT is expected to transmit a sinusoid (i.e., signal, sinusoidal signal, etc.) without any amplitude or phase modulation. Embodiments are not limited to the dedicated CWT case but can be applied to other cases where reader and CWT are co-located, either in a monostatic setup or bi-static setup.

[0438] In some embodiments, where network node 2101 configured as CWT generates modulation schemes, the CWT ID may be transmitted as follows:

[0439] • Step 1 : A network node 2101 configured as CWT transmits an unmodulated CW (CW1) which powers up the WD 22 (for example a passive tag).

[0440] • Step 2: After CW1, network node 2101 configured as CWT transmits an on-off keying (OOK) modulated signal for a time duration denoted by Took (in ms or seconds). The OOK signal can be generated by turning CWT on and off within the Took duration, according to the CWT ID. The WD 2103 may demodulate the OOK signal to get the CWT ID.

[0441] • Step 3: after Took duration, the CWT transmits another unmodulated CW (CW2). WD 2103 backscatters CW2 by jointly encoding the CWT ID as well as the UE ID (or group ID). Then, the network node 2102 configured as gNB / reader demodulates the backscattered signal to get the CWT ID and UE ID.

[0442] The above procedure may be applicable for a WD 2103 (for example of the type referred to as Device A in the terminology of 3GPP Ambient loT). In some cases, the procedure may also be applicable for other WDs 2103 (for example of the types referred to as Device B and Device C in the terminology of 3GPP Ambient loT), such as cases where the other WDs 2103 rely on RF energy harvesting.

[0443] The duration Took in Step 2 can be fixed (predefined) or can be adapted based on the deployment scenario. For example, if passive WDs are deployed in a large factory, the numbers of CWTs needed to cover the entire area may be higher than in less complex implementations. Consequently, the number of CWT IDs may be higher as well. For a smaller factory, the number of CWT IDs may be limited. Therefore, the number of bits needed to convey CWT ID may be different based on the requirements of the factory.

[0444] In one embodiment, depending on the number of bits used to convey CWT ID, the Took duration can be increased or decreased. In a related embodiment, the network node 2102 configured as gNB / reader is in control of setting the Took, which may be transmitted to the CWT over the Xn' interface.

[0445] In another embodiment, OOK-modulation in Step 2 can used with other modulation schemes, such as amplitude-shift keying (ASK), frequency shift keying (FSK), phase shift keying (PSK), etc.

[0446] In the procedure for legacy electronic product code (EPC) generation 2 (Gen-2) ultra- high frequency (UHF) RFID protocol, preamble and command may be transmitted to the WD (tag) between CW1 and CW2. Unlike Solution #1, there is no transmission and backs cattering of a CWT ID.

[0447] Example solution #2

[0448] In some embodiments, the WD 2103 does not have / know or has not received the CWT ID. That is, WD 2103 does not need to necessarily demodulate the signal generated by the CWT 2101 in Step 2 above. In this case, the procedure may be as follows:

[0449] • Step 1: Network node 2101 configured as CWT transmits an unmodulated CW (CW1) which powers up the WD 2103 (for example a passive tag).

[0450] • Step 2: After CW1, the network node 2101 configured as CWT transmits a modulated signal that carries the CWT ID. The duration of the signal is denoted by Tsignal. In some embodiments, WD 2103 (tag) does not demodulate this signal but reflects (backscatters) the signal without encoding any information. Network node 2102 configured as the gNB / reader may demodulate the signal to get the CWT ID.

[0451] The modulated signal transmitted by the CWT 2101 may be based on OOK or can be even more advanced modulation schemes with wider bandwidth. In a nonlimiting example, only the network node / reader 2102, e.g., gNB / reader, demodulates the signal, but not WD 2103 (the gNB / reader may have significantly higher processing capability and power availability than WD 2103).

[0452] • Step 3: After Tsignal, the CWT 2101 transmits another unmodulated CW (CW2). The WD / tag 2103 backscatters CW2 by encoding the UE ID (or group ID). Then, the gNB / reader 2012 demodulates the backscattered signal to get the UE_ID.

[0453] In the procedure above, Step 2 and Step 3 can be interchanged, in which case, network node 2102 configured as gNB / reader gets the UE ID in the second step and CWT ID in the third step. Also other modulation other than OOK can be applied. A difference from the above embodiments may be that WD 2103 is unaware of the CWT ID and simply reflects is back to the network node 2102 configured as gNB / reader. The Tsignal duration may be communicated from the network node 2102 configured as gNB / reader to the network node 2101 configured as CWT over, e.g., the Xn' interface.

[0454] One embodiment of Solution #2 may include one or more of the following steps:

[0455] • Step 1 : a legacy WD 22 (e.g., NR or LTE WD 22) transmits CW1, i.e. it acts as a CWT 2101. The transmission of CW1 is triggered by the network node 2102 configured as gNB / reader over Uu-interface, e.g., using legacy procedure in triggering the WD 22 to transmit Random Access preamble, sounding reference signal (SRS), etc. CW1 power ups the 2103.

[0456] • Step 2: After transmission of CW1, the legacy WD 22 transmits modulated signals. The WD 2103 backscatters the signal without encoding any information on its own. The network node 2102 configured as gNB / reader demodulates the signal. o In this case, the modulated signals transmitted by legacy WD 22 can be quadrature amplitude modulation (QAM) and / or PSK-modulated signals carrying ID of the legacy WD 22 and its position information, or it can be reference signals (e.g., SRS, PRACH) that can be used by the network node 2102 configured as gNB / reader to position the legacy WD 22. o After demodulating the signal, the network node 2102 configured as gNB / reader knows the legacy WD 22 (and its position) near which the WD 2103 (tag) is located.

[0457] • Step 3: After transmission of modulated signals, the legacy WD 22 transmits CW2. The other WD 2103 (tag) backscatters CW2 by encoding its tag ID.

[0458] CW1 and CW2 in the above realization can be unmodulated CWs or can be legacy uplink (UL) signals supported by the WD 22, e.g. random access preamble, or SRS.

[0459] Example solution #3

[0460] In one embodiment, Step 1 in Solution #1 and Solution #2 can be skipped. In this case, the WD 2103 can power up using the modulated signals transmitted in Step 2 (e.g., no need for separate CW1 for powering up the device).

[0461] In another embodiment, Step 2 in Solution #2 can be skipped. In this case, there is a predefined time slot in which a particular CWT 2101 transmits CW1 and / or CW2, or alternatively, the network node 2102 configured as gNB / reader triggers a particular CWT 2101 to transmit CW1 and / or CW2. When the gNB / reader 2102 receives UE ID in Step 3, the network node 2102 configured as gNB / reader may also implicitly knows which CWT 2101 the WD 2103 (tag) is near to.

[0462] As described above, a first network node (such as the network node 2102) may perform a method 2200 as illustrated in Figure 22. The method 2200 the method comprises receiving 2201, from a wireless device (such as the wireless device 2103), a backscattered version of a carrier wave transmitted by a carrier wave transmitter (such as the carrier wave transmitted 2101). The backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter. The method 2200 further comprises determining 2202 a position of the wireless device based on the carrier wave transmitter identified by the received backscattered version of the carrier wave, or transmitting 2203 signaling to a second network node (such as the network node 2104) indicating that a backscattered version of a carrier wave transmitted by the carrier wave transmitter has been received from the wireless device, for the second network node to determine a position of the wireless device.

[0463] The method 2200 may for example comprise receiving signaling indicating a position of the carrier wave transmitter, wherein the position of the wireless device is determined based on the position of the carrier wave transmitter.

[0464] The method 2200 may for example comprise signaling an identifier to the carrier wave transmitter to be used by the carrier wave transmitter to identify itself in the carrier wave transmitted by the carrier wave transmitter.

[0465] In the method 2200, the backscattered version of the carrier wave may for example identify the carrier wave transmitter by a carrier wave transmitter identifier modulated into the backscattered version of the carrier wave, or by a timing of the backscattered version of the carrier wave.

[0466] In the method 2200, the backscattered version of the carrier wave may for example identify the wireless device by a wireless device identifier modulated into the backscattered version of the carrier wave.

[0467] As described above, a wireless device (such as the wireless device 2103) may perform a method 2300 as illustrated in Figure 23. The method 2300 comprises receiving 2301 a carrier wave from a carrier wave transmitter 2101. The carrier wave identifies the carrier wave transmitter. The method 2300 comprises transmitting 2302 a backscattered version of the carrier wave to a first network node (such as the network node 2102). The backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter.

[0468] In the method 2300, the carrier wave may for example identify the carrier wave transmitter by a carrier wave transmitter identifier modulated into the carrier wave, or by a timing of the carrier wave.

[0469] In the method 2300, the backscattered version of the carrier wave may for example identify the carrier wave transmitter by a carrier wave transmitter identifier modulated into the backscattered version of the carrier wave, or by a timing of the backscattered version of the carrier wave. In the method 2300, the backscattered version of the carrier wave may for example identify the wireless device by a wireless device identifier modulated into the backscattered version of the carrier wave.

[0470] The method 2300 may for example comprise demodulating a first portion of the received carrier wave to obtain a carrier wave identifier identifying the carrier wave transmitter, and modulating a second portion of the received carrier wave to convey, in the backscattered version of the carrier wave, the carrier wave identifier and a device identifier identifying the wireless device.

[0471] In the method 2300, the received carrier wave may for example comprise a first portion in which a carrier wave identifier identifying the carrier wave transmitter has been modulated. The method 2300 may for example comprise backscattering the first portion of the carrier wave to the first network node, thereby forwarding the carrier wave identifier to the first network node in the backscattered version of the carrier wave, and modulating a second portion of the received carrier wave to convey, in the backscattered version of the carrier wave, a device identifier identifying the wireless device. The first portion of the carrier wave may for example be backscattered by the wireless device to the first network node without encoding any additional information in the first portion.

[0472] In the method 2300, the received carrier wave may for example comprise a third portion, located before the first and second portions, for powering up the wireless device.

[0473] In the method 2300, the second portion of the received carrier wave may for example be an unmodulated carrier wave.

[0474] In the method 2300, the carrier wave identifier may for example be conveyed in the first portion of the received carrier wave by on-off keying (OOK), or amplitude-shift keying (ASK), or frequency shift keying (FSK), or phase shift keying (PSK).

[0475] As described above, a second network node (such as the network node 2104) may perform a method 2400 as illustrated in Figure 24. The method 2400 comprises receiving 2401 signaling from a first network node (such as the network node 2102) indicating that a backscattered version of a carrier wave transmitted by a carrier wave transmitter (such as the carrier wave transmitter 2101) has been received from a wireless device (such as the wireless device 2103). The backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter. The method 2400 comprises determining 2402 a position of the wireless device based on the carrier wave transmitter indicated by the received signaling.

[0476] The method 2400 may for example comprise receiving signaling indicating a position of the carrier wave transmitter. The position of the wireless device may for example be determined based on the position of the carrier wave transmitter. The method 2400 may for example comprise signaling an identifier to the carrier wave transmitter to be used by the carrier wave transmitter to identify itself in the carrier wave transmitted by the carrier wave transmitter.

[0477] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0478] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0479] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0480] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0481] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0482] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0483] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0484] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings and following nonlimiting example embodiments.

[0485] Further example embodiments: Embodiment G1. A first network node configured to communicate with a wireless device (WD), the first network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: receive, from the WD, signaling associated with a second network node configured as a carrier wave transmitter (CWT), the signaling comprising information usable for determining positioning information at least of the WD; and perform one or more actions based on the received signaling.

[0486] Embodiment G2. The first network node of Embodiment G1 , wherein the information includes a CWT identifier (ID).

[0487] Embodiment G3. The first network node of Embodiment G2, the first network node is further configured to: transmit the CWT ID to the CWT over an Xn’ interface.

[0488] Embodiment G4. The first network node of any one of Embodiments Gl- G3, the first network node is further configured to one or more of: determine a configuration of the CWT ID for the CWT; determine a configuration to associate the CWT with the first network node; maintain a list with CWT contexts for each CWT of a plurality of CWTs; request and / or determine CWT positioning; and determine a timing offset over an Xn’ interface.

[0489] Embodiment G5. The first network node of any one of Embodiments G1-G4, wherein one or more of: the first network node is further configured as a reader node; the WD is configured as a passive tag device; the WD is configured for ambient energy harvesting; and the WD is an internet of things device.

[0490] Embodiment Hl . A method implemented in a first network node configured to communicate with a wireless device (WD), the method comprising: receiving, from the WD, signaling associated with a second network node configured as a carrier wave transmitter (CWT), the signaling comprising information usable for determining positioning information at least of the WD; performing one or more actions based on the received signaling.

[0491] Embodiment H2. The method of Embodiment Hl, wherein the information includes a CWT identifier (ID).

[0492] Embodiment H3. The method of Embodiment H2, the method further includes: transmitting the CWT ID to the CWT over an Xn’ interface.

[0493] Embodiment H4. The method of any one of Embodiments Hl- H3, the method further includes one or more of: determining a configuration of the CWT ID for the CWT; determining a configuration to associate the CWT with the first network node; maintaining a list with CWT contexts for each CWT of a plurality of CWTs; requesting and / or determining CWT positioning; and determining a timing offset over an Xn’ interface.

[0494] Embodiment H5. The method of any one of Embodiments H1-H4, wherein one or more of: the first network node is further configured as a reader node; the WD is configured as a passive tag device; the WD is configured for ambient energy harvesting; and the WD is an internet of things device.

[0495] Embodiment 11. A wireless device (WD) configured to communicate with a first network node and a second network node, the second network node being configured as carrier wave transmitter (CWT), the WD configured to, and / or comprising a radio interface and / or processing circuitry configured to: receive first signaling from the second network node, the first signaling being one of unmodulated and modulated; and transmit, to the first network node, second signaling based on the first signaling, the second signaling including information usable for determining positioning information at least of the WD.

[0496] Embodiment 12. The WD of Embodiment 11, wherein the WD is further configured to one or more of: receive a first unmodulated carrier wave configured to power up the WD; receive an on-off keying (OOK) modulated signal for a time duration (Took), the OOK modulated signal including a CWT identifier (ID); demodulate the OOK modulated signal to obtain the CWT ID; after Took has elapsed, receive a second unmodulated carrier wave; and backscatter the second unmodulated carrier wave by jointly encoding the CWT ID and a WD ID for the first network node to demodulate the second unmodulated carrier wave to obtain the CWT ID and WD ID.

[0497] Embodiment 13. The WD of Embodiment 12, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the OOK modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

[0498] Embodiment 14. The WD of Embodiment II, wherein the WD is further configured to one or more of: receive a first unmodulated carrier wave configured to power up the WD; receive a first modulated signal that carries a CWT ID, the first modulated signal having a time duration (Tsignal); backscatter the first modulated signal without encoding any information, the backscattered first modulated signal being usable by the first network node to obtain the CWT ID; receive a second unmodulated carrier wave; and backscatter the second unmodulated carrier wave by encoding a WD ID for the first network node to demodulate the second unmodulated carrier wave to obtain the WD ID.

[0499] Embodiment 15. The WD of Embodiment 14, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the first modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

[0500] Embodiment JI . A method implemented in wireless device (WD) configured to communicate with a first network node and a second network node, the second network node being configured as carrier wave transmitter (CWT), the method comprising: receiving first signaling from the second network node, the first signaling being one of unmodulated and modulated; and transmitting, to the first network node, second signaling based on the first signaling, the second signaling including information usable for determining positioning information at least of the WD.

[0501] Embodiment J2. The method of Embodiment J 1 , wherein the method further includes one or more of: receiving a first unmodulated carrier wave configured to power up the WD; receiving an on-off keying (OOK) modulated signal for a time duration (Took), the OOK modulated signal including a CWT identifier (ID); demodulating the OOK modulated signal to obtain the CWT ID; after Took has elapsed, receiving a second unmodulated carrier wave; and backscattering the second unmodulated carrier wave by jointly encoding the CWT ID and a WD ID for the first network node to demodulate the second unmodulated carrier wave to obtain the CWT ID and WD ID.

[0502] Embodiment J3. The method of Embodiment J2, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the OOK modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

[0503] Embodiment J4. The method of Embodiment JI, wherein the method further includes one or more of: receiving a first unmodulated carrier wave configured to power up the WD; receiving a first modulated signal that carries a CWT ID, the first modulated signal having a time duration (Tsignal); backscattering the first modulated signal without encoding any information, the backscattered first modulated signal being usable by the first network node to obtain the CWT ID; receiving a second unmodulated carrier wave; and backscattering the second unmodulated carrier wave by encoding a WD ID for the first network node to demodulate the second unmodulated carrier wave to obtain the WD ID.

[0504] Embodiment J5. The method of Embodiment J4, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the first modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

[0505] Embodiment KI. A second network node configured as a carrier wave transmitter (CWT) and to communicate with a wireless device (WD), the second network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to: transmit first signaling from a second network node, the first signaling being one of unmodulated and modulated, the first signaling being usable by the WD to transmit, to the first network node, second signaling based on the first signaling, the second signaling including information usable for determining positioning information of the WD; and perform one or more actions based on the first signaling.

[0506] Embodiment K2. The second network node of Embodiment KI, wherein the second network node is further configured to one or more of: transmit a first unmodulated carrier wave configured to power up the WD; transmit an on-off keying (OOK) modulated signal for a time duration (Took), the OOK modulated signal including a CWT identifier (ID); and after Took has elapsed, transmit a second unmodulated carrier wave usable by the WD to backscatter the second unmodulated carrier wave by jointly encoding the CWT ID and a WD ID.

[0507] Embodiment K3. The second network node of Embodiment K2, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the OOK modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

[0508] Embodiment K4. The second network node of Embodiment KI, wherein the second network node is further configured to one or more of: transmit a first unmodulated carrier wave configured to power up the WD; transmit a first modulated signal that carries a CWT ID, the first modulated signal having a time duration (Tsignal) and being usable by the WD to backscatter the first modulated signal without encoding any information; and transmit a second unmodulated carrier wave usable by the WD to encode a WD ID. Embodiment K5. The second network node of Embodiment K4, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the first modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

[0509] Embodiment LI. A method in a second network node configured as a carrier wave transmitter (CWT) and to communicate with a wireless device (WD), the method comprising: transmitting first signaling from a second network node, the first signaling being one of unmodulated and modulated, the first signaling being usable by the WD to transmit, to the first network node, second signaling based on the first signaling, the second signaling including information usable for determining positioning information of the WD ; and performing one or more actions based on the first signaling.

[0510] Embodiment L2. The method of Embodiment LI, wherein the method further includes to one or more of: transmitting a first unmodulated carrier wave configured to power up the WD; transmitting an on-off keying (OOK) modulated signal for a time duration (Took), the OOK modulated signal including a CWT identifier (ID); and after Took has elapsed, transmitting a second unmodulated carrier wave usable by the WD to backscatter the second unmodulated carrier wave by jointly encoding the CWT ID and a WD ID.

[0511] Embodiment L3. The method of Embodiment L2, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the OOK modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

[0512] Embodiment L4. The method of Embodiment LI, wherein the method further includes one or more of: transmitting a first unmodulated carrier wave configured to power up the WD; transmitting a first modulated signal that carries a CWT ID, the first modulated signal having a time duration (Tsignal) and being usable by the WD to backscatter the first modulated signal without encoding any information; and transmitting a second unmodulated carrier wave usable by the WD to encode a WD ID. Embodiment L5. The method of Embodiment L4, wherein one or both of: the first signaling includes the first unmodulated carrier wave and / or the first modulated signal; and the second signaling includes the backscattered second unmodulated carrier wave.

Claims

CLAIMS1. A method (2200) implemented by a first network node (2102), the method comprising: receiving (2201), from a wireless device (2103), a backscattered version of a carrier wave transmitted by a carrier wave transmitter (2101), wherein the backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter, the method further comprising: determining (2202) a position of the wireless device based on the carrier wave transmitter identified by the received backscattered version of the carrier wave; or transmitting (2203) signaling to a second network node (2104) indicating that a backscattered version of a carrier wave transmitted by the carrier wave transmitter has been received from the wireless device, for the second network node to determine a position of the wireless device.

2. The method of claim 1 , further comprising: receiving signaling indicating a position of the carrier wave transmitter, wherein the position of the wireless device is determined based on the position of the carrier wave transmitter.

3. The method of any of the preceding claims, further comprising: signaling an identifier to the carrier wave transmitter to be used by the carrier wave transmitter to identify itself in the carrier wave transmitted by the carrier wave transmitter.

4. The method of any of the preceding claims, wherein the backscattered version of the carrier wave identifies the carrier wave transmitter by: a carrier wave transmitter identifier modulated into the backscattered version of the carrier wave; or a timing of the backscattered version of the carrier wave.

5. The method of any of the preceding claims, wherein the backscattered version of the carrier wave identifies the wireless device by: a wireless device identifier modulated into the backscattered version of the carrier wave.

6. The method of any of the preceding claims, wherein: the first network node is a base station; and / or the second network node is a core network node; and / or the wireless device is configured for ambient energy harvesting; and / or the carrier wave transmitter is stationary or mobile.

7. A method (2300) implemented by a wireless device (2103), the method comprising: receiving (2301) a carrier wave from a carrier wave transmitter (2101), wherein the carrier wave identifies the carrier wave transmitter; and transmitting (2302) a backscattered version of the carrier wave to a first network node (2102), wherein the backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter.

8. The method of claim 7, wherein the carrier wave identifies the carrier wave transmitter by: a carrier wave transmitter identifier modulated into the carrier wave; or a timing of the carrier wave.

9. The method of any of claims 7-8, wherein the backscattered version of the carrier wave identifies the carrier wave transmitter by: a carrier wave transmitter identifier modulated into the backscattered version of the carrier wave; or a timing of the backscattered version of the carrier wave.

10. The method of any of claims 7-9, wherein the backscattered version of the carrier wave identifies the wireless device by: a wireless device identifier modulated into the backscattered version of the carrier wave.

11. The method of any of claims 7-10, wherein the method comprises: demodulating a first portion of the received carrier wave to obtain a carrier wave identifier identifying the carrier wave transmitter; and modulating a second portion of the received carrier wave to convey, in the backscattered version of the carrier wave, the carrier wave identifier and a device identifier identifying the wireless device.

12. The method of any of claims 7-10, wherein the received carrier wave comprises a first portion in which a carrier wave identifier identifying the carrier wave transmitter has been modulated, wherein the method comprises: backscattering the first portion of the carrier wave to the first network node, thereby forwarding the carrier wave identifier to the first network node in the backscattered version of the carrier wave; and modulating a second portion of the received carrier wave to convey, in the backscattered version of the carrier wave, a device identifier identifying the wireless device.

13. The method of claim 12, wherein the first portion of the carrier wave is backscattered by the wireless device to the first network node without encoding any additional information in the first portion.

14. The method of any of claims 11-13, wherein the received carrier wave comprises a third portion, located before the first and second portions, for powering up the wireless device.

15. The method of any of claims 11-14, wherein the second portion of the received carrier wave is an unmodulated carrier wave.

16. The method of any of claims 11-15, wherein the carrier wave identifier is conveyed in the first portion of the received carrier wave by on-off keying (OOK), or amplitude-shift keying (ASK), or frequency shift keying (FSK), or phase shift keying (PSK).

17. A method (2400) implemented by a second network node (2104), the method comprising: receiving (2401) signaling from a first network node (2102) indicating that a backscattered version of a carrier wave transmitted by a carrier wave transmitter (2101) has been received from a wireless device (2103), wherein the backscattered version of the carrier wave identifies the wireless device and the carrier wave transmitter; and determining (2402) a position of the wireless device based on the carrier wave transmitter indicated by the received signaling.

18. The method of claim 17, further comprising: receiving signaling indicating a position of the carrier wave transmitter, wherein the position of the wireless device is determined based on the position of the carrier wave transmitter.

19. The method of any of claims 17-18, further comprising: signaling an identifier to the carrier wave transmitter to be used by the carrier wave transmitter to identify itself in the carrier wave transmitted by the carrier wave transmitter.

20. A first network node (2102) configured to perform the method of any of claims 1-6.

21. A first network node (2102) comprising a radio interface and processing circuitry configured to perform the method of any of claims 1-6.

22. A wireless device (2103) configured to perform the method of any of claims 7-16.

23. A wireless device (2103) comprising a radio interface and processing circuitry configured to perform the method of any of claims 7-1624. A second network node (2104) configured to perform the method of any of claims 17-19.

25. A second network node (2104) comprising a radio interface and processing circuitry configured to perform the method of any of claims 17-19.

Images