Methods to control intermediate node for aiot devices

Abstract

In accordance with implementations, a wireless system receives a configuration for a Uu uplink and an Ambient Internet of Things (AIoT) link. The wireless system transmits a first signal over a first AIoT channel of the AIoT link based on the configuration. The wireless system receives a second signal over a second AIoT channel of the AIoT link based on the configuration. The second signal is an AIoT uplink signal associated with a carrier wave (CW). The wireless system transmits a third signal over a Uu physical uplink shared channel (PUSCH) based on the configuration and the second signal.

Description

Methods to Control Intermediate Node for AIoT DevicesCROSS-REFERENCE TO RELATED APPLICATIONS[oooi] This patent application claims priority to U.S. Provisional Application No. 63 / 554,722, filed on February 16, 2024, and entitled “Methods to Control Intermediate Node for AIoT Devices,” application of which is hereby incorporated by reference herein as if reproduced in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communications, and, in particular embodiments, to systems and methods for controlling intermediate node for AIoT devices.BACKGROUND

[0003] Within the framework of Release 19 of 3rd Generation Partnership Project (3GPP) is studying new devices, Ambient Internet of Things (loT) devices, aiming at expanding the 5th generation (5G) new radio (NR) device ecosystem. In comparison with a conventional 3GPP cellular loT device (for example, Narrowband loT), Ambient loT (AIoT) devices are not powered by traditional batteries, and have ultra-low complexity and power consumption. Such AIoT devices are characterized by their small form factor and capability to harvest energy sources from the environment such as electromagnetic waves, solar or light, kinetic or vibration, wind, or thermal, among others. Additionally, AIoT devices may be equipped with limited energy storage (e.g., supercapacitors) for storing electric energy harvested from the ambient energy sources. As a result, high maintenance costs and safety hazards due to manually changing or recharging batteries on individual loT devices can be eliminated, leading to an eco-friendly and sustainable technology of the future, reducing the carbon footprint of today ’s supply chain.

[0004] Due to ultra-low powder consumption and complexity requirements, AIoT devices may be passive, which do not contain active radio-frequency transceivers for internal signal generation. Thus, such devices rely on the principle of backscatter communication. AIoT backscatter devices depend on an external carrier (or continuous) wave, which is modulated with the data of the backscatter device before it is reflected.SUMMARY

[0005] Technical advantages are generally achieved, by implementations of this disclosure which describe methods, apparatus, and system. i[ooo6] In accordance with implementations, a wireless system receives a configuration for a Uu uplink and an Ambient Internet of Things (AIoT) link. The w ireless system transmits a first signal over a first AIoT channel of the AIoT link based on the configuration. The wireless system receives a second signal over a second AIoT channel of the AIoT link based on the configuration. The second signal is an AIoT uplink signal associated with a carrier wave (CW). The wireless system transmits a third signal over a Uu physical uplink shared channel (PUSCH) based on the configuration and the second signal.

[0007] In some implementations, the wireless system may transmit the CW to an AIoT device. The second signal may be a backscatter-wave signal of the CW.

[0008] In some implementations, the configuration may be a configured grant that includes at least one of time resources or frequency resources for at least one of the first AIoT channel, the second AIoT channel, the CW, or the Uu PUSCH.

[0009] In some implementations, the configuration may be a configured grant that is activated by a downlink control information (DCI) message. The configuration may further include at least one of a first time offset between the DCI message and the transmitting the first signal over the first AIoT channel or a second time offset between the DCI message and a transmission of the third signal.

[0010] In some implementations, the configuration may include a first periodicity. The wireless system may transmit one or more first signals over the first AIoT channel based on the first periodicity.

[0011] In some implementations, the configuration may include a second periodicity. The wireless system may transmit one or more third signals over the Uu PUSCH based on the second periodicity and the one or more first signals.

[0012] In some implementations, the configuration may include an indication of a CW transmission requirement or availability.

[0013] In some implementations, the configuration may include an indication of CW transmission configuration forw arding over AIoT link. The wireless system may transmit a CW transmission configuration over the first AIoT channel based on the configuration.

[0014] In some implementations, the DCI message may be scrambled by one of a configured schedule CCS) radio network temporary identifier (RNTI) or an AIoT RNTI,

[0015] In some implementations, the wireless system may transmit, to a base station of the wireless system, intermediate node capability information. The intermediate node capability information may indicate at least one of first capability information ofreceiving in a frequency-division duplex (FDD) uplink (UL) band or second capability information of transmitting a CW tone in the FDD UL band.[oot6] In some implementations, an intermediate node of the wireless system may transmit the first capability information. A UE of the wireless system may transmit the second capability information.

[0017] In some implementations, the first capability information and the second capability information may be transmitted a UE of the wireless system.

[0018] In some implementations, the transmitting the first signal, the receiving the second signal, and the transmitting the third signal are performed by a first UE of the wireless system. The transmitting the CW may be performed by a second UE of the wireless system.

[0019] In some implementations, he first UE and the second UE may each receive at least part of the configuration.

[0020] In accordance with implementations, a wireless system receives a configuration for a Uu uplink and an Ambient Internet of Things (AIoT) link from a base station. The wireless system transmits a first signal over a first AIoT channel based on the configuration. The wireless system determines a carrier wave (CW) transmission requirement based on the configuration. The wireless system transmits a CW and receives a second signal over a second AIoT channel based on the configuration. The wireless system transmits a third signal over a Uu physical uplink shared channel (PUSCH) based on the configuration and the second signal.

[0021] In some implementations, the configuration may be a configured grant. In some implementations, the configuration includes at least one of time resources or frequency resources for at least one of the first AIoT channel, the second AIoT channel, the CW, or the Uu PUSCH. In some implementations, the configured grant may be activated by a downlink control information (DCI) message. The configuration may further include a first time offset between the DCI and the transmitting the first signal over the first AIoT channel.

[0022] In some implementations, the configuration may include a first periodicity. The wireless system may transmit one or more first signals over the first AIoT channel based on the first periodicity. In some implementations, the configuration may include a second periodicity. The wireless system may transmit one or more third signals over the Uu PUSCH based on the second periodicity and the one or more first signals.

[0023] In some implementations, the wireless system may determine an indication of a CW transmission availability based on the configuration. The w ireless system may receive the second signal over the second AIoT channel based on an AIoT link configuration.

[0024] In some implementations, the wireless system may determine an indication of a CW transmission availability based on the configuration. The wireless system may transmit a CW transmission configuration over the first AIoT channel based on the configuration. The wireless system may receive the second signal over the second AIoT channel based on the configuration.

[0025] In some implementations, the configuration may be received using any of a radio resource control (RRC) setup message, an RRC reconfiguration message, or a system information message.

[0026] In some implementations, the DCI may be scrambled by one of a configured schedule (CS) radio network temporary identifier (RNTI) or an AIoT RNTI.

[0027] In some implementations, the wireless system may transmit to the base station intermediate node capability information. The intermediate node capability information may indicate at least one of a first capability information of receiving in a frequency-division duplex (FDD) uplink (UL) band or a second capability information of transmitting a CW tone in the FDD UL band. In some implementations, to transmit the intermediate node capability information, an intermediate node of the wireless system may transmit the first capability information, and a UE of the wireless system may transmit the second capability information.

[0028] In some implementations, the wireless system may include a UE. The first capability information and the second capability information are transmitted by the UE. In some implementations, an AIoT device may perform the transmitting the CW. In some implementations, the UE may perform the transmitting the CW.

[0029] In some implementations, a first UE of the wireless system may perform the transmitting the first signal, the receiving the second signal, and the transmitting the third signal. The first UE and a second UE of the wireless system may perform the receiving the configuration. In some implementations, the first UE may perform the transmitting the CW. In some implementations, the second UE may perform the transmitting the CW.

[0030] In some implementations, the wireless system may include a UE. The UE may perform the receiving the configuration. The base station may perform the transmitting the first signal and the receiving the second signal. An AIoT device may perform thetransmitting the second signal. The second signal and the third signal may be the same signal. In some implementations, the UE may perform the transmitting the CW. In some implementations, the UE may transmit the CW in response to the UE detecting the first signal transmitted by the base station. In some implementations, the base station performs the transmitting the CW. In some implementations, the UE and the AIoT device may be the same device.

[0031] In so doing, the techniques described in this disclosure solve technical challenges of controlling intermediate node for AIoT devices by allowing the base station to dynamically configure and manage the intermediate node’s roles through structured signaling procedures and resource allocations. The described techniques prevent interference between multiple intermediate nodes, optimize spectrum usage through time / frequency multiplexing of CWs with regular cellular traffic, and enable flexible switching between monostatic and bistatic operations. Additionally, the described techniques support both periodic and aperiodic transmissions while considering various device capabilities, resulting in improved coverage, reduced signaling overhead, and enhanced overall system efficiency for AIoT deploy ments.BRIEF DESCRIPTION OF THE DRAWINGS

[0032] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0033] FIG. 1 shows an example NR FDD operating band n8 for AIoT systems, in accordance with some implementations;

[0034] FIG. 2 shows an example of Network Topology 1 with an AIoT-enabled gNodeB as the carrier wave source, in accordance with some implementations;

[0035] FIG. 3 shows an example of Network Topology 2 with an AIoT-enabled intermediate node as the carrier wave source, in accordance with some implementations;

[0036] FIG. 4 shows an example of Network Topology 1 with an independent carrier wave source, in accordance w ith some implementations;

[0037] FIG. 5 shows an example of Network Topology 2 with an independent carrier wave source, in accordance with some implementations;

[0038] FIG. 6 show-s an example of in-band time multiplexing of AIoT carrier wave signals, in accordance with some implementations;

[0039] FIG. 7 depicts an example of in-band frequency multiplexing of AIoT carrier wave signal, in accordance with some implementations;

[0040] FIG. 8 depicts an example of hybrid in-band and guard-band frequency multiplexing of AIoT carrier wave signals, in accordance w ith some implementations;

[0041] FIGs. 9A-9C illustrate an example implementation of topology, timing resource allocation, and frequency resource allocation;

[0042] FIG. 10A illustrates an example receiver block diagram of AIoT downlink reception with carrier wave present, in accordance with some implementations;

[0043] FIG. 10B illustrates an example envelope detection spectrum of AIoT downlink reception w ith carrier wave present, in accordance w ith some implementations;

[0044] FIGs. 11A-11C illustrate an example implementation of topology, timing resource allocation, and frequency resource allocation;

[0045] FIGs. 12A-12C illustrate an example implementation of topology, timing resource allocation, and frequency resource allocation;

[0046] FIGs. 13A-13C illustrate an example implementation of topology, timing resource allocation, and frequency resource allocation;

[0047] FIG. 14 illustrates an example signaling flow- supporting AIoT operation under deployment scenario 2 topology 2 with the periodic transmission configuration, in accordance with some implementations;

[0048] FIG. 15 illustrates an example signaling flow supporting AIoT operation under deployment scenario 2 topology 2 with the aperiodic AIoT transmission / reception configuration, in accordance with some implementations;

[0049] FIG. 16 illustrates an example signaling flow supporting AIoT operation under deployment scenario 2 topology 2 considering the AIoT device with internal CW generation capability, in accordance with some implementations;

[0050] FIG. 17 illustrates an example signaling flow- supporting AIoT operation under deployment scenario 1 topology 1 with aperiodic AIoT transmission / reception configuration, in accordance with some implementations;

[0051] FIG. 18 shows a flow chart of a method performed by a wireless system, in accordance with some implementations;

[0052] FIG. 19 illustrates an example communications system, in accordance with some implementations;

[0053] FIG. 20 illustrates an example communication system, in accordance with some implementations;

[0054] FIGs. 21A and 21B illustrate example devices, in accordance w ith some implementations; and

[0055] FIG. 22 shows a block diagram of a computing system, in accordance with some implementations.

[0056] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated. The figures are drawn to clearly illustrate the relevant aspects of the embodiments and are not necessarily drawn to scale.DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0057] AIoT technology enables massive deployment of batteiy-free and low-cost loT devices, which opens a whole new world of use cases and provides added value across the entire supply chain. To date, 3GPP groups AIoT use cases into four broad categories: inventory , sensor, positioning, and command. The inventory and command use cases are selected for studies in Release 19.

[0058] In the 3GPP Release t9 study scope, an AIoT device can connect either directly to a gNode B or indirectly via an intermediate node user equipment (UE). The former network connectivity structure may be referred to as Topology 1 (gNode B <-> AIoT Device), and the latter may be referred to as Topology 2 (gNode B <-> Intermediate Node <-> AIoT). It is worth mentioning that two additional network connectivity topologies are documented, namely Topology 3 (gNode B <-> Assisting Node <-> AIoT Device <-> gNode B), and Topology 4 (UE <-> AIoT Device). Even though Topologies 3 and 4 are considered out of scope in the current release, this disclosure described herein is applicable to all the aforementioned topologies.

[0059] Each AIoT network topology can support one or more deployment scenarios as presented in Table 1 below. 3GPP Release 19 only focuses on Deployment Scenario 1 with Topology 1, and Deployment Scenario 2 with Topology 2 in which the intermediate node is a UE under the network control. This disclosure is also relevant to the other deployment scenarios in addition to Deployment Scenarios 1 and 2.Table 1: AIoT Deployment Scenarios and Topologies[oo6o] The duplex mode refers to the separation of downlink (e.g., gNode B to UE) and uplink (e.g., UE to gNode B) transmission, which in general can be accomplished in the frequency or / and time domain. The frequency-domain and time-domain duplex modes are categorized into Frequency-Division Duplex (FDD) and Time-Division Duplex (TDD), respectively. In FDD, two disjoint carrier frequencies (which are spaced apart by a guard band, also known as duplex spacing) are employed for downlink (DL) and uplink (UL) transmission. On the other hand, TDD uses a single carrier frequency for both the downlink and uplink transmission, which takes place at a different time separated by a guard interval. FDD can enable full -duplex operations while TDD operation may be halfduplex. A scaled-dow n variant of FDD is half-duplex FDD, where the downlink and uplink transmissions are separated in the frequency and time domains.

[0061] 3GPP NR (5G) specifications (e.g., 3GPP TS 38.104) support all the aforementioned duplex modes. In addition, two duplex modes are supported, namely supplemental uplink (SUL) and supplemental downlink (SDL). The spectrum allocation for 5G (or 3GPP NR) systems, which is referred to as New-Radio operating band in the 3GPP technical specification (TS) 38.104, defines which duplex mode to be used for downlink and uplink transmission for each operating band. For example, the duplex mode of the NR operating band n8 (known also as 900) is FDD and TDD for NR operating band n4i (also called TD 2500) in 3GPP TS 38.104. A subset of the NR operating bands belonging to Frequency Range 1 (FR1) along with their duplex mode is presented in Table 2. All the NR operating bands are classified as licensed spectrum except for the operating bands 1146, 1196, and niO2, which are unlicensed spectrum. In addition to the FDD and TDD duplex modes, several operating bands are also defined for SUL. More details can be found in 3GPP TS 38.104.Table 2: 3GPP New-Radio Operating Bands for Frequency Range 1 (Source: 3GPPTS 38.104)

[0062] AS described above, AToT devices are battery-free, which is considered a new generation of ultra-low complexity coupled with ultra-low power consumption. There are significant differences in transceiver capability between AIoT devices and legacy UEs. Because current 5G NR technology was not designed with such devices in mind, and the network deployments have largely been designed to provide service to legacy UEs, intermediate nodes are utilized to enable full sendees for the AIoT devices, as shown by the 4 topologies defined in the 3GPP study item. To enable smooth and efficient operations of the intermediate nodes, the behavior of the intermediate nodes can becontrolled by the base station / network. When multiple intermediate nodes work jointly to meet the needs of the application scenarios, the timing and resources can be coordinated by the base station. Each intermediate node may see its role changes over time. Hence, defining the configurations and signaling for the intermediate nodes are desirable.

[0063] As stated in the 3GPP study item description, AIoT operating frequencies can include the New-Radio licensed paired spectrum within Frequency Range 1. As described below, the NR licensed operating bands for Frequency Range 1 range from 410 MHz to 7125 MHz. FDD operating bands located in the lower frequency (for example, below 2 GHz) are preferred over the higher ones due to lower path loss, resulting in larger coverage (or longer communication distances) of AIoT devices. To this end, FDD operating bands, which offer a good balance between antenna size and path loss, are of interest to AIoT devices. In addition, such FDD operating bands should be available worldwide in order to ensure interoperability for global use of AIoT devices, and suit indoor and outdoor AIoT deployment scenarios. One example of such band is n8.

[0064] In one embodiment, AIoT devices can be defined to support one NR FDD operating band. One such example FDD operating band can be n8, as shown in FIG. 1.

[0065] The uplink frequency range (JUL)L- / UL,H and downlink frequency range (fDL:L~ fDL,n)overwhich the AIoT device can operate may be specified, where fUL Land fUL Hare the lowest and the highest frequencies in the uplink range, and fDLtLand fDL Hare the lowest and the highest frequencies in the downlink. The uplink and downlink frequency range can span one or more NR FDD operating bands. For instance, New- Radio operating bands n8, niq, and n28 can be supported by AIoT devices.

[0066] A carrier wave (CW) is a continuous radio frequency (RF) signal transmitted by an AIoT-enabled gNode B or UE. Such a carrier-wave signal is used to power AIoT devices and can be used to carry downlink information (for example, commands or / and data). For those AIoT devices that are incapable of internally generating a carrier frequency for uplink transmission, these devices communicate through the principle of backscatter; that is, data of these AIoT devices is modulated on to the external incident carrier-wave signal and reradiated (or backscattered). According to the principle of FDD operation, the backscatter-wave signal is sent on the uplink frequency while the external carrier-wave signal is on the downlink frequency. For those AIoT devices without frequency translation / conversion capability, the external carrier-wave signal can be transmitted on the uplink or downlink frequency depending on regional radio regulations, where AIoT devices operate. In certain countries, their radio regulations may allow the backscatter-wave signal to be sent on the downlink frequency, while othercountries prohibit backscatter to take place on the downlink frequency . Similarly, for the external carrier-wave signal transmission on the downlink, regional radio regulations may or may not permit such carrier-wave transmission.

[0067] The backscatter-wave signal utilizes the uplink frequency. Hence, the AIoT- enabled gNode B assigns an uplink frequency fULtCWto transmit the external carrier-wave signal to the AIoT derice for Topology 1; and for Topology 2, the AIoT-enabled intermediate node is allocated with the uplink frequency fUL,cw for transmitting the external carrier-wave signal as shown in FIG. 2 and FIG. 3, respectively. In both topologies, the frequency of the backscatter wave is fUL:BV. Alternatively, the backscatterwave signal is sent on the downlink frequency fDLiBVand the carrier-wave signal is on the downlink frequency fDLtCw-

[0068] In Topology 2, the traditional gNode B 302 communicates with the AIoT- enabled intermediate node 304 through the normal NR Uu air interface using a pair of downlink and uplink frequencies. It is important to note that the uplink frequency fULwhich is used for intermediate node to gNode B communication may not be the same as the one (i.e., fULtCw) used for transmitting the external carrier-wave signal. Uu air interface (or Uu interface) is an air interface that connects user equipment (UE) and a radio access network (RAN), and Uu link is a link between the UE and the RAN ria Uu air interface. Uu air interface may be used in both LTE and 5G NR.

[0069] The external carrier wave signal can be transmitted by an independent source other than the AloT-enabled gNode B or intermediate node. The example implementations are shown in FIG. 4 and FIG. 5 for Topology 1 and Topology 2, respectively. An independent carrier wave source (e.g., 402 or 502) can be realized by a legacy NR UE. The carrier wave signal may not cariy information for the AIoT device (e.g., 404 or 504). In order to backscatter on the uplink frequency by the AIoT device, the independent source (e.g., 402) can generate the external carrier wave signal on the uplink frequency fUL,cw As such, the backscatter-wave signal is received by the AIoT- enabled gNode B 406 (or other receivers capable of receiving AIoT transmissions) on the intended uplink frequency fUL>BV. The carrier wave signal transmission by the independent source can be configured (or controlled) by the AIoT-enabled gNode B 406 through the legacy NR Uu air interface. That is, the AIoT-enabled gNode B 406 provides the independent source with configuration information such as the time when the independent source begins and stops the external carrier-wave transmission, transmit power, and what uplink carrier-wave frequency fUL.cw to use including bandwidth.

[0070] An AIoT system may operate within an NR operating band, either inside the NR channel bandw idth (also known as in-band) or in the guard band of the NR channel. It may also operate on a standalone frequency band (which is a non-NR operating band), for example, refarmed GSM spectrum. For in-band and guard-band operation, coexistence w ith legacy NR may be needed. Consequently, OFDM numerology of NR can be reused. The amount of NR channel bandwidth allocated for AIoT transmission can be expressed in terms of physical resource blocks (PRBs), and the transmission duration can be defined as an integral number of OFDM symbols.

[0071] In order to support in-band operation and those AIoT devices w ithout channel selectivity (radio-frequency filtering) capability, the external AIoT carrier wave signal can be time or frequency multiplexed w ith legacy NR signal transmissions. In the time-multiplexing case, the external carrier wave signal transmission does not take place at the same time as the legacy NR transmission. The AIoT carrier wave transmission may occupy a portion of the total NR channel bandw idth, and the remaining unused bandwidth is reserved for backscatter-wave signals as illustrated in FIG. 6. Based on the description below, the external carrier wave signal can be sent using an uplink carrier frequency by the AIoT-enabled gNode B (or intermediate node). Here, a portion of the total NR channel bandwidth including one carrier frequency (or multi-carrier frequencies up to an integral number of PRBs in the uplink NR channel bandwidth) is allocated for the external carrier wave transmission. Consequently, the available transmit power can be concentrated within the carrier w ave bandwidth, resulting in higher power density. Alternatively, the external carrier wave signal occupies the total NR transmission bandwidth without any unused bandwidth.

[0072] In the frequency-multiplexing case, the external carrier wave signal is frequency multiplexed with NR signal transmission as depicted in FIG. 7. In order to reduce in-band interference due to NR device transmission on the reception of backscatter-wave signals, sufficient bandwidth (in numbers of physical resource blocks) can be reserved as guard bands between the external carrier-wave signal and the NR signal as shown in FIG. 7. In addition, the reserved bandwidth can be used for the backscatter-wave signal transmission. The amount of reserved bandwidth depends on the amount of powder allocated to the external carrier wave transmission with respect to the transmit power of NR UE, and w hether the AIoT device is capable of channel selectivity.

[0073] Fig. 8 illustrates a hybrid in-band and guard-band multiplexing method, where the external carrier wave signal is frequency multiplexed with NR signal transmission using the frequency on one of the channel edges so that the backscattered-wave transmission utilizes the guard-band frequency. Such a method leads to higher spectrum efficiency as compared to the frequency multiplexing technique. Furthermore, transmission power of carrier wave signal is not constrained by guard-band (unwanted) emissions requirements, which will not cause a reduction in cell coverage.

[0074] Sendees to an AIoT device include the following 3 tasks at least for the low power devices that rely on backscattering for uplink transmission:• Task 1): Transmitting AloT downlink signals to the AIoT device during an AIoT downlink transmission period;• Task 2): Transmitting carrier wave signals to the AIoT device during an AIoT uplink transmission period; and / or• Task 3): Receiving backscattered AIoT uplink transmission from the AIoT device during the AIoT uplink transmission period.

[0075] An intermediate node can perform all 3 tasks (Topology 2), or only Task 1) and 2) (Topology 3 with downlink assist), or only Task 3) (Topology 3 with uplink assist). Alternatively, if Task 2) is performed by an independent carrier wave source outside of the topology, an intermediate node can perform Task 1) and 3) (Topology 2), or only Task 1) or 3) (Topology 3). Additionally, an intermediate node can also only perform Task 2) at least during a limited time period as required by the deployment scenario. Such a case applies to Topology 1 as well, where the intermediate node acts as the independent carrier wave node not included in the topology.

[0076] The transceiver capability utilized by the intermediate node to perform those tasks are the following.• For Task 1), the intermediate node may be capable of transmitting an AIoT downlinksignal in the allocated frequency band, for example, in the UL frequencies of an FDD band.• For Task 2), the intermediate node may be capable of transmitting carrier wave signal in the allocated frequency band, for example, transmitting a single subcarrier tone in the UL frequencies of an FDD band.• For Task 3), the intermediate node may be capable of receiving the backscattered transmission from the device in the allocated frequency band. For example, in the UL frequencies of an FDD band.• For performing Tasks 2) and 3) simultaneously, the intermediate node may be capable of full-duplex operation, i.e., transmitting and receiving over the same frequencies at the same time. This is a complex capability, usually requiring methods to cancel outthe signal from its transmitter at its own receiver. A receiver supporting selfinterference cancellation usually has a lower sensitivity than one without.

[0077] To enable smooth and efficient operation of the intermediate nodes, the behavior of the intermediate nodes may be controlled by the base station / network. Especially when multiple intermediate nodes need to work jointly to meet the needs of the application scenarios, their timing and resources need to be coordinated by the base station. Each intermediate node may know its role changes over time. Hence, the need to define the messages and signaling for the intermediate nodes is desired.

[0078] For example, when 2 intermediate nodes are within each other’s AIoT coverage areas, rather than working independently in a monostatic mode and inadvertently interfering with each other, it is better to coordinate them to work in a bistatic mode. The better receive sensitivity of an intermediate node when it is not performing full-duplex operation can be leveraged to increase the coverage range. In this example, one intermediate node can be configured to be the carrier wave source, and the other intermediate node can be configured as the backscattered transmission receiver. Their roles can be switched over time. In addition, an intermediate node can be the carrier wave source at one frequency and at the same time be the backscattered transmission receiver at another frequency. If the 2 frequencies are sufficiently separated, the task of self-interference cancellation can be more easily performed without sacrificing receiver sensitivity.

[0079] From the base station’s perspective, an intermediate node is a device with a Uu link to communicate with the base station, and with capabilities to support AIoT sen ices. It may be a UE or a network equipment such as network controlled repeater (NCR), an integrated access and backhaul (IAB) node, or a dedicated equipment. In the following description, this disclosure may refer to an intermediate node simply as a UE as an example for ease of explanation. As explained above, the description of the UE described below (e.g., the listening UE or the CW UE) is applicable to other types of the intermediate node, such as a base station, a relay or a repeater. Also in this disclosure, uplink (UL) and downlink (DL) with respect to an AIoT device (e.g., AIoT UL / PUSCH (A-UL) and AIoT DL / PDSCH (A-DL)) may also be referred to as reader-to-device (R2D) and device-to-reader (D2R), respectively. These terms can be used interchangeably in this disclosure.

[0080] For all the embodiments described in the following, it is helpful for the base station to know’ the capabilities of the candidate UEs to be assigned as intermediate nodes performing specific functions. The capabilities are listed according to the tasks that need to be performed by the intermediate node described above. This informationcan be obtained by either the base station querying the candidates or the UEs signaling its capabilities to the base station.

[0081] In a first example implementation shown in FIG. 9A, two UEs 904 and 906 are used as intermediate nodes to provide services to an AIoT device 902. One UE is named CW UE 904, which performs Task 2) of providing carrier wave signal for the AIoT device 902, while the other is named listening UE 906, which performs Task 1) of transmitting AIoT downlink signals to the AIoT device 902 and Task 3) of receiving the backscattered transmission from the AIoT device. The base station 908 allocates resources for the two UEs 904 and 906. The resource allocation in time and in frequency are shown in FIGs. 9B and 9C, respectively. The listening UE 906 performs Task 1) and Task 3) in a time-division multiplexed manner. In this embodiment, to reduce any signaling and / or processing complexity, the CW UE 904 is transmitting the carrier wave for the entire time allocated, without differentiating between AIoT DL period or AIoT UL period. To avoid interference from the carrier wave to the AIoT DL signal receiving at the AIoT device using a simple RF envelope detector, it is desirable that the frequency resource allocations for AIoT DL and AIoT UL be different. An example allocation is shown in FIG. 9C, where the single tone carrier wave is at the center of the frequency resources allocated for the AIoT UL, and the AIoT DL frequency resource is located away from the AIoT UL frequency resource.

[0082] This interference mitigation strategy is explained in the following. FIG. 10A illustrates the block diagram of an example AIoT device receiver receiving on-off keying (OOK) modulated RF signal using an RF envelope detector. The output of the envelope detector is filtered by 2 low pass filters with different pass bands. Lowpass Filter t’s passband is wide enough to allow the OOK signal through, while Lowpass Filter 2’s passband is narrow enough to only allow direct current (DC) signal through. The comparator compares the two filtered signals to provide a 1 bit digital signal for baseband processing. This detection process removes any DC bias introduced by interference. FIG. 10B show s the RF spectrum of the AIoT DL transmission in the presence of the carrier wave and the baseband spectrum of the signal after envelope detection. The separation between the carrier wave frequency and the AIoT DL signal is shown as IF. The envelope signal contains primarily 3 parts, the self-mixing product of the carrier wave, which is the DC signal, the self-mixing product of the AIoT DL signal, w hich is the desired AIoT DL envelope signal, and the mixing product between the two, which is the RF AIoT DL signal frequency translated to IF and acts as interference. It is clearly shown that if the IF is greater than the bandwidth of the AIoT DL signal, there is no overlap betw een the desired AIoT DL envelope signal and the interfering signal, and the interference signalcan be removed by the Lowpass Filter 1. The effect of the DC bias produced by the carrier wave is mitigated by the Low pass Filter 2 as discussed above. The higher the IF, the easier the Low pass Filter 1 is to implement. However, there is no need for IF to be too high, as it would fragment the allocated frequency resource unnecessarily.

[0083] A second example implementation is illustrated in FIGs. 11A-11C. The topology of the first implementation in FIG. 9A is used, which includes an AIoT device 1102, a CW UE 1104, and a listening UE 1106, and the base station 1108. The timing of the resource utilization is different. In this case, the CW UE 1104 only transmits the carrier wave during the AIoT UL transmission period as shown in FIG. 11B. The frequency resource allocation can also be different. Since there is no interference by the carrier wave in the AIoT DL reception, the AIoT DL frequency allocation can re-use the AIoT UL resource as shown in FIG. 11C.

[0084] The timing for the carrier wave transmission by the CW UE 1104 can be derived in multiple ways as listed below.• Case 1: The AIoT DL / UL slot structure (R2D / D2R slot structure) is configured as part of the resource grant, so the CW UE 1104 knows when to turn on / off CW.• Case 2: The CW UE 1104 may determine the time for AIoT UL reception (D2R reception) by monitoring the AIoT DL transmission of the listening UE 1106.• Case 3: The listening UE 1106 requests CW through the base station 1106, which in turn instructs the CW UE 1104 using downlink control information (DCI) message.

[0085] The resource allocation for AIoT DL / UL is know n ahead of time for Case 1; otherwise, it may result in unused resources being wasted. Case 3 may use much overhead over the Uu link, and result in additional latency . For Case 2, the CW UE 1104 may determine the timing from monitoring the AIoT DL transmissions. The CW UE 1104 has much better reception sensitivity than any AIoT device, therefore receiving and demodulating the AIoT DL transmission would not be a problem. However, the AIoT DL messages can contain sufficient information for the CW UE 1104 to determine when it should transmit the carrier wave. Therefore, the AIoT DL transmission preceding the AIoT UL transmission by the AIoT device may contain the following information:• indication that AIoT UL transmission is expected after the AIoT DL transmission is completed; and / or• the length of time within which the subsequent AIoT UL transmission is expected to be completed.

[0086] A third example implementation is illustrated in FIGs. 12A-12C. In this topology shown in FIG. 12A, the CW UE 1204 performs Tasks 1) and 2), while thelistening UE 1206 only performs Task 3). As shown in FIG. 12B, the CW UE 1204 time multiplexes between AIoT downlink transmission and carrier wave transmission. The frequency resource allocation is the same as in the second example implementation.

[0087] The timing for the reception of backscattered AIoT UL transmission by listening UE 1206 can be derived in multiple ways as listed below.• Case 1: the DL / UL slot structure is configured as part of the resource grant.• Case 2: listening UE may determine the time for AIoT UL reception by detecting the presence of CW or monitoring the DL AIoT transmission by the CW UE.• Case 3: CW UE requests UL reception through BS, which in turn instructs listening UE using DCI messaging.

[0088] Case 1 of the third implementation is identical to Case 1 of the second implementation. Case 3 of the third implementation is similar to Case 3 of the second implementation except that it is the CW UE 1204 signaling the base station 1208 instead of the listening UE 1206. Case 2 of the third implementation is similar to Case 2 in the second implementation, except that additionally the listening UE 1206 can also detect the presence of the carrier wave.

[0089] One difference between this third implementation and the previous first and second implementations is that the AIoT UL information and AIoT DL information reside at different intermediate UEs, they have to close the loop through the Uu links to the gNB, increasing the Uu link overhead.

[0090] In a fourth example implementation, this disclosure considers the AIoT UL transmission and reception simultaneously for multiple AIoT devices. The AIoT DL transmission process can be identical to the previous example embodiments. FIGs. 13A- 13C illustrate this example implementation. In the topology show n in FIG. 13A, two UEs, UE 1304A and UE 1304B can act as the intermediate nodes, and two AIoT devices 1302A and 1302B can perform backscattered UL AIoT transmission at the same time using different frequency resources. For AIoT device 1302A, UE 1304A may act as the CW UE, and UE 1304B may act as the listening UE. For AIoT device 1302B, the roles of the UEs 1304A and 1304B are reversed, as shown in FIG. 13B. The two simultaneous backscattered AIoT transmissions may use different frequency resources as shown in FIG. 13C. The separation in frequency of those frequency resources allows the UEs to perform interference cancellation using simple filters.

[0091] Additional implementations involving only a single intermediate node UE can be derived from the implementations described above.• In one implementation, referring to the second implementation illustrated FIGs. 11A- 11C, the listening UE 1106 and the CW UE 1104 may be combined into a single entity (e.g., the same UE). In this case, the UE performs all 3 Tasks.• In another implementation, referring to the third embodiment illustrated in FIGs. 12A- 12C, the listening UE 1206 functionality can be incorporated into the base station 1208. This implementation supports Topology 3 with downlink assist.• In another implementation, referring to the third embodiment illustrated in FIGs. 12A- 12C, the CW UE 1204 functionality may be incorporated into the base station 1208. This embodiment supports Topology 3 with uplink assist.• In another implementation, referring to the first embodiment illustrated in FIGs. 9A- 9C or the second embodiment illustrated in FIGs. 11A-11C, the listening UE (e.g., UE 906 or 1106) functionality can be incorporated in the base station (e.g., base station 908 or 1108). This implementation supports Topology 1 with explicit control of the carrier wave node.

[0092] Another implementation can be derived that involves high power AIoT devices with the capability to generate carrier wave internally. Referring to FIGs. 9A-9C, the CW UE 904 functionality may be performed by the AIoT device 902 itself. In this case, a subset of the necessary configuration information for CW UE 904 can be sent to the AIoT device 902 through AIoT DL transmissions. Such information may include the frequency resource to be used for the AIoT UL transmission.

[0093] Furthermore, additional implementations without explicitly controlling the carrier wave source can be derived from the implementations described above.• In one implementation, referring the first implementation illustrated in FIGs. 9A-9C, the listening UE 906 and the CW UE 904 may be combined into a single entity (e.g., the same UE) and this single entity only performs Task 1) and Task 3).• In another implementation, referring the third implementation illustrated in FIGs. 12A-12C, the listening UE 1206 functionality may be incorporated into the base station 1208, and the CW UE 1204 only performs Task 1). This implementation supports Topology 3 with downlink assist.• In another implementation, in the third embodiment illustrated in FIGs. 12A-12C, the CW UE 1204 functionality may be incorporated into the base station 1208, and the base station 1208 only performs Task 1) for AIoT service. This implementation supports Topology 3 with uplink assist.

[0094] In the example implementations illustrated in FIG. 14, a listening UE 1406 receives, at the operation 1411, configuration of an UL and AIoT link configured grantusing any of RRC setup, RRC Reconfiguration, and / or system information messages. The UL and AIoT link configured grant includes one or more of the following parameters: an indication of an RRC configuration only or an RRC configuration and a PDCCH configuration (i.e., a DCI scrambled by, e.g., CS-RNTI or an AIoT specific RNTI) are used to activate the UL and AIoT link configured grant; a first time offset (e.g., Toffi) indicating the time between an activating DCI (PDCCH) message and a first transmission from the listening UE 1406 to the AIoT device 1402 on the AIoT link; a second time offset (e.g., TOff2) indicating the time between an activating DCI (PDCCH) message and a first transmission from the listening UE 1406 to the gNB 1408 on the Uu link; a periodicity (e.g., Tperiod) of transmission for any of the AIoT PDSCH / DL, AIoT PUSCH / UL, and AIoT UL traffic forwarding; a time gap (e.g., TDL-UL) between an AIoT PDSCH / DL transmission and an AIoT PUSCH / UL; a set of frequency resources used for the transmission of any of the CW, AIoT physical downlink shared channel (PDSCH), AIoT PUSCH, and AIoT UL traffic forwarding; and / or an indication of internal or external (i.e., from the listening UE 1406 perspective) CW requirement / availability.

[0095] In an implementation, the listening UE 1406 determines an indication of an RRC and PDCCH configured grant and monitors for a DCI scrambled wdth, for example, a CS-RNTI. At the operation 1412, the listening UE 1406 detects the configured grant activating DCI and initiates an AIoT PDSCH / DL transmission 1421 at the first time offset (e.g., Toffi) and on the allocated frequency resources. On a condition that the listening UE 1406 determines internal requirement of a CW source based on the received configuration (e.g., in the RRC message and / or PDCCH message), the listening UE 1406 initiates CW transmission 1422 w hile monitoring for backscattered AIoT PUSCH / UL 1423 after the configured time gap (e.g., TDL-UL) . Otherwise, on a condition that the listening UE 1406 determines external CW availability, the listening UE 1406 only initiates monitoring for backscattered AIoT PUSCH / UL 1423 after the configured time gap (e.g., TDL-UL). The subsequent listening UE transmissions of AIoT PDSCH / DL 1424 and receptions of backscattered AIoT PUSCH / UL 1425 occurs according to the configured periodicity (e.g., Tperiod). At the operation 1413, the listening UE 1406 initiates forwarding of AIoT UL traffic to the gNB 1408 at the second time offset (e.g., TOff2) and the allocated UL frequency resources. The subsequent forwarding of AIoT UL traffic 1414to the gNB 1408 occurs according to the configured periodicity (e.g., Tperiod) using the allocated UL frequency resources. At the operation 1415, the listening UE 1406 detects the configured grant deactivating DCI and terminates AIoT PDSCH / DL transmission, AIoT PUSCH / UL reception, and AIoT UL traffic forwarding.

[0096] In another implementation, the listening UE 1406 determines an indication of an RRC only configured grant and proceeds in a periodic AIoT PDSCH / DL transmission (e.g., 1421 and 1424), AIoT PUSCH / UL reception (e.g., 1423 and 1425), with or without internal CW transmission based on received RRC configuration, and AIoT UL traffic forwarding (e.g., 1413 and 1414). The listening UE 1406 may terminate the periodic transmission upon reception of any of an RRC Release, RRC reconfiguration, and system information update.

[0097] In another implementation, the AIoT link configuration may include a maximum duration for an AIoT UL transmission which can be included as a parameter in any of the AIoT link configured grant configuration, AIoT PDCCH, and AIoT PDSCH messages.

[0098] The periodicity for AIoT UL traffic forwarding may be configured as multiples of the periodicity for transmissions of AIoT PDSCH / DL and receptions of backscattered AIoT PUSCH / UL. Alternatively, there may be more than one transmission of AIoT PDSCH / DL and reception of backscattered AIoT PUSCH / UL in any configured period.

[0099] In another implementation in FIG. 14, the CW UE 1404 receives, at the operation 1431, configuration of an AIoT link configured grant using any of RRC setup, RRC Reconfiguration, and / or system information messages. The configuration of AIoT link configured grant can be received using the same message used for the listening UE 1406 (e.g., system information). The AIoT link configured grant includes one or more of the following parameters: an indication of an RRC configuration only or an RRC configuration and a PDCCH configuration (i.e., a DCI scrambled by, e.g., CS-RNTI or an AIoT specific RNTI) are used to activate the AIoT link configured grant; a third time offset (e.g., Toff3) indicating the time between an activating DCI (PDCCH) message and a first transmission from the CW UE 1404 to the AIoT device 1402. The third time offset may be indicated explicitly or implicitly (e.g., the sum of the first offset (e.g., Toffl) and the time gap (e.g., TDL-UL); a periodicity of transmission (e.g., Tperiod) for the CW; a set of frequency resources used for the transmission of the CW; and / oran indication of internal or external, i.e., from the listening UE 1406 perspective, CW requirement / availability.

[0100] In an implementation, the CW UE 1404 determines an indication of an RRC and PDCCH configured grant and monitors for a DCI scrambled with, e.g., a CS-RNTI. At the operation 1432, the CW UE 1404 detects the configured grant activating DCI and initiates a CW transmission 1433 at the third time offset (e.g., Toff3) and allocated frequency resources. The subsequent CW UE transmissions (e.g., 1434) of CW occur according to the configured periodicity (e.g., Tperiod). At the operation 1435, the CW UE 1404 detects the configured grant deactivating DCI and terminates CW transmission.

[0101] In another implementation, the CW UE 1404 determines an indication of an RRC only configured grant and proceeds in a periodic CW transmission. The CW UE 1404 may terminate the periodic transmission upon reception of any of an RRC Release, RRC reconfiguration, and system information update.

[0102] In another implementation, the CW UE 1404 continuously transmits the CW, i.e., w ithout the need to monitor and detect the AIoT PDSCH, which can still be triggered by the configured grant activating DCI.

[0103] In another implementation, the AIoT link configuration may include a maximum duration for an AIoT UL transmission w hich can be included as a parameter in the AIoT link configured grant configuration.

[0104] The CW UE 1404 may be the AIoT device 1402 itself when it is capable of internally, i.e., to the AIoT device 1402, generating the carrier wave. Also, the CW UE 1404 may only initiate the procedure upon determination of external, i.e., from listening UE 1406 perspective, CW availability.

[0105] In the example implementations illustrated in FIG. 15, a listening UE 1506 receives, at the operation 1511, configuration of an UL and AIoT link configured grant using any of RRC setup, RRC Reconfiguration, and system information messages. The UL and AIoT link configured grant include one or more of the following parameters: an indication of an RRC configuration only or an RRC configuration and a PDCCH configuration (i.e., a DCI scrambled by, e.g., CS-RNTI or an AIoT specific RNTI) are used to activate the UL and AIoT link configured grant; a second time offset (e.g., TOff2) indicating the time between an activating DCI (PDCCH) message and a first transmission from the listening UE 1506 to gNB 1508 on the Uu link; a periodicity (e.g., Tperiod) of transmission for AIoT UL traffic forwarding;a time gap (e.g., TDL-UL) between an AIoT PDSCH / DL transmission and an AIoT PUSCH / UL; a set of frequency resources used for the transmission of any of the CW, AIoT PDSCH, AIoT PUSCH, and AIoT UL traffic forwarding; and / or an indication of internal or external (i.e., from the listening UE 1506 perspective) CW requirement / availability.

[0106] In an implementation, the listening UE 1506 determines an indication of an RRC and PDCCH configured grant and monitors for a DCI scrambled with, for example, a CS-RNTI. At the operation 1512, the listening UE 1506 detects the configured grant activating DCI and transmits, at the operation 1521, AIoT PDSCH / DL at the allocated / configured frequency resources to the AIoT device 1502. On a condition that the listening UE 1506 determines internal requirement of a CW source based on received configuration (e.g., in the RRC message and / or PDCCH message), the listening UE 1506 performs CW transmission 1522 while monitoring for backscattered AIoT PUSCH / UL 1523 after the configured time gap (e.g., TDL-UL). Otherwise, i.e., on a condition that the listening UE 1506 determines external CW availability, the listening UE 1506 only performs monitoring for backscattered AIoT PUSCH / UL 1523 after the configured time gap (e.g., TDL-UL). At the operation 1513, the listening UE 1506 initiates forwarding of AIoT UL traffic to the gNB 1508 at the second time offset (e.g., T0ff2) using allocated UL frequency resources. The subsequent forwarding of AIoT UL traffic 1525 to the gNB 1508 at the operation 1514 occurs according to the configured periodicity (e.g., Tperiod) over the allocated UL frequency resources. At the operation 1515, the listening UE 1506 detects the configured grant deactivating DCI and terminates AIoT PDSCH / DL transmission, AIoT PUSCH / UL reception, and AIoT UL traffic forwarding.

[0107] In another implementation, the listening UE 1506 determines an indication of an RRC only configured grant and proceeds in an AIoT PDSCH / DL transmission (e.g., 1521 and 1524), AIoT PUSCH / UL reception (e.g., 1523 and 1525) w ith or without internal CW transmission based on received RRC configuration, and periodic AIoT UL traffic forwarding (e.g., 1513 and 1514). The listening UE 1506 may terminate the transmissions upon reception of any of an RRC Release, RRC reconfiguration, and system information update.

[0108] In another implementation, the AIoT link configuration may include a maximum duration for an AIoT UL transmission which can be included as a parameter in any of the AIoT link configured grant configuration, AIoT PDCCH, and AIoT PDSCH messages.

[0109] In another implementation in FIG. 15, a CW UE 1504 receives, at the operation 1531, configuration of an AIoT link configured grant using any of RRC setup, RRC Reconfiguration, and system information messages. The configuration of AIoT link configured grant can be received using the same message used for the listening UE 1506 (e.g., system information). The AIoT link configured grant includes one or more of the following parameters: an indication of an RRC configuration only or an RRC configuration and a PDCCH configuration (i.e., a DCI scrambled by, e.g., CS-RNTI or an AIoT specific RNTI) are used to activate the AIoT link configured grant. a set of frequency resources used for the transmission of the CW and reception of the AIoT PDSCH / DL. a time gap between an AIoT PDSCH / DL transmission and an AIoT PUSCH / UL. An indication of internal or external, i.e., from the listening UE perspective, CW requirement / availability.

[0110] In an implementation, the CW UE 1504 determines an indication of an RRC and PDCCH configured grant and monitors for a DCI scrambled with, e.g., a CS-RNTI. At the operation 1532, the CW UE 1504 detects the configured grant activating DCI and monitors for the AIoT PDSCH / DL 1521 over the configured frequency resources. At the operation 1533, the CW UE 1504 detects an AIoT PDSCH 1521 and initiates a CW transmission at the time gap (e.g., TDL UL) and over the allocated frequency resources. At the operation 1534, the CW UE 1504 detects the configured grant deactivating DCI and terminates CW transmission.

[0111] In another implementation, the CW UE 1504 determines an indication of an RRC only configured grant and proceeds in AIoT PDSCH / DL monitoring and CW transmission based on AIoT PDSCH / DL detection. The CW UE 1504 may terminate the monitoring and transmission upon reception of any of an RRC Release, RRC reconfiguration, and system information update.

[0112] In another implementation, the CW UE 1504 continuously transmits the CW, without the need to monitor and detect the AIoT PDSCH, which can still be triggered by the configured grant activating DCI.

[0113] In another implementation, the AIoT link configuration may include a maximum duration for an AIoT UL transmission which can be included as a parameter in any of the AIoT link configured grant configuration, AIoT PDCCH, and AIoT PDSCH messages.

[0114] The CW UE 1504 may be the AIoT device itself when it is capable of internally, i.e., to the AIoT device, generating the carrier wave. Also, the CW UE may only initiate the procedure upon determination of external, i.e., from listening UE perspective, CW availability’.

[0115] In the example implementations illustrated in FIG. 16, a listening UE 1606 receives, at the operation 1611, configuration of an UL and AIoT link configured grant using any of RRC setup, RRC Reconfiguration, and system information messages. The UL and AIoT link configured grant include one or more of the following parameters: an indication of an RRC configuration only or an RRC configuration and a PDCCH configuration (i.e., a DC1 scrambled by, e.g., CS-RNT1 or an AIoT specific RNTI) are used to activate the UL and AIoT link configured grant; a second time offset (e.g., TOff2) indicating the time between an activating DCI (PDCCH) message and a first transmission from the listening UE 1606 to gNB 1608 on the Uu link; a periodicity (e.g., Tperiod) of transmission for AIoT UL traffic forwarding; a time gap (e.g., TDL-UL) between an AIoT PDSCH / DL transmission and an AIoT PUSCH / UL; a set of frequency resources used for the transmission of any of the CW, AIoT PDSCH, AIoT PUSCH, and AIoT UL traffic forwarding; an indication of internal or external (i.e., from the listening UE 1606 perspective), CW requirement / availability; and / or an indication of CW transmission configuration forwarding over AIoT link.

[0116] In an implementation, the listening UE 1606 determines an indication of an RRC and PDCCH configured grant and monitors for a DCI scrambled with, for example, a CS-RNTI . The listening UE 1606 determines external availability of a CW source with a requirement to forward CW transmission configuration over AIoT link based on received configuration (e.g., in the RRC message and / or PDCCH message). At the operation 1612, the listening UE 1606 detects the configured grant activating DCI. At the operation 1621, the listening UE 1606 transmits CW transmission configuration and AIoT PDSCH / DL over the allocated / configured frequency resources. At the operation 1622, the listening UE 1606 performs monitoring for backscattered AIoT PUSCH / UL after the configured time gap (e.g., TDL-UL). At the operation 1613, the listening UE 1606 initiates forwarding of AIoT UL traffic to the gNB 1608 at the second time offset (e.g., Toff2) over allocated frequency resources. The subsequent forwarding of AIoT UL traffic (e.g., 1614) to the gNB 1608 occurs according to the configured periodicity (e.g., Tperiod) over the allocated frequency resources. At the operation 1615, the listening UE 1606 detects the configuredgrant deactivating DCI and terminates AIoT PDSCH / DL transmission, AIoT PUSCH / UL reception, and AIoT UL traffic forwarding.

[0117] In another implementation, the listening UE 1606 determines an indication of an RRC only configured grant and proceeds in an AIoT PDSCH / DL transmission (e.g., 1621 and 1623), AIoT PUSCH / UL reception (e.g., 1622 and 1624) with or without internal CW transmission based on received RRC configuration, and periodic AIoT UL traffic forwarding (e.g., 1613 and 1614). The UE may terminate the transmissions upon reception of any of an RRC Release, RRC reconfiguration, and system information update.

[0118] In another implementation, the AIoT link configuration may include a maximum duration for an AIoT UL transmission which can be included as a parameter in any of the AIoT link configured grant configuration, AIoT PDCCH, and AIoT PDSCH messages.

[0119] In another implementation in FIG. 16, the AIoT device 1602 receives, at the operation 1621, configuration of CW transmission, including a set of frequency resources and / or a time gap (e.g., TDL-UL), using any of an AIoT PDCCH and AIoT PDSCH transmission over an AIoT downlink from the listening UE 1606. The configuration may also include parameters for the AIoT PUSCH UL transmission including a transmission data rate, a waveform, and / or encoding scheme. At the operation 1622, the AIoT device 1602 transmits an AIoT PUSCH / UL with the internally generated CW at frequency resources based on received configuration from the listening UE 1602.

[0120] In the example implementations illustrated in FIG. 17, a CW UE 1704 receives, at the operation 1711, configuration of an AIoT link configured grant using any of RRC setup, RRC Reconfiguration, and system information messages. The AIoT link configured grant includes one or more of the following parameters: an indication of an RRC configuration only or an RRC configuration and a PDCCH configuration (i.e., a DCI scrambled by, e.g., CS-RNTI or an AIoT specific RNTI), are used to activate the AIoT link configured grant; a set of frequency resources used for the transmission of the CW and reception of the AIoT PDSCH / DL. a time gap (e.g., TDL-UL) between an AIoT PDSCH / DL transmission and an AIoT PUSCH / UL; and / or an indication of internal or external (i.e., from the gNB 1708 perspective), CW requirement / availability.

[0121] In an implementation, the CW UE 1704 determines an indication of an RRC and PDCCH configured grant and monitors for a DCI scrambled with, for example, a CS- RNTI. At the operation 1712, the CW UE 1704 detects the configured grant activating DCI and monitors for the AIoT PDSCH / DL at the configured frequency resources. At the operation 1713, the CW UE 1704 detects an AIoT PDSCH and initiates a CW transmission 1714 at the time gap (e.g., TDL-UL) and allocated frequency resources. At the operation 1717, the CW UE detects the configured grant deactivating DCI and terminates CW transmission.

[0122] In an implementation, the CW UE 1704 determines an indication of an RRC only configured grant and proceeds in AIoT PDSCH / DL monitoring and CW transmission (e.g., 1714 and 1716) based on AIoT PDSCH / DL detection (e.g., 1713 and 1715). The CW UE 1704 may terminate the monitoring and transmission upon reception of any of an RRC Release, RRC reconfiguration, and system information update.

[0123] In an implementation, the CW UE 1704 continuously transmits the CW (i.e., without the need to monitor and detect the AIoT PDSCH), which can still be triggered by the configured grant activating DCI.

[0124] In another technical realization, the AIoT link configuration may include a maximum duration for an AIoT UL transmission which can be included as a parameter in any of the AIoT link configured grant configuration, AIoT PDCCH, and AIoT PDSCH messages.

[0125] The CW UE may be the AIoT device 1702 itself when it is capable of internally(i.e., to the AIoT device) generating the CW. Subsequently, the AIoT link configuration (e.g., the set of frequency resources for CW transmission, the time gap, and / or the indication of internal or external CW requirement / availability) are received by the AIoT device 1702 using any of an AIoT PDCCH and AIoT PDSCH messages over the AIoT link. Also, the CW UE 1704 may only initiate the procedure upon determination of external (i.e., from gNB perspective) CW availability.

[0126] In all the above embodiments, the AIoT PDCCH is a control channel specified for AIoT devices to carry any relevant control information whereas the AIoT PDSCH is a shared channel specified for AIoT to carry' data with the possibility to contain control information (e.g., in the form of a header).

[0127] FIG. 18 shows a flow chart of a method 1800 performed by a wireless system, in accordance with some implementations. The wireless system may include computer- readable code or instructions executing on one or more processors of the wireless system. Coding of the software for carrying out or performing the method 1800 is well within thescope of a person of ordinary skill in the art having regard to the present disclosure. The method 1800 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on at least one non-transitoiy computer-readable medium, such as for example, at least one memory of the wireless system. In some embodiments, the method 1800 may be performed by one or more of units or modules (e.g., an integrated circuit) of the wireless system, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0128] The method 1800 starts at the operation 1802, where the wireless system receives a configuration for a Uu uplink and an Ambient Internet of Things (AIoT) link from a base station. At the operation 1804, the wireless system transmits a first signal over a first AIoT channel based on the configuration. At the operation 1806, the wireless system determines a carrier wave (CW) transmission requirement based on the configuration. At the operation 1808, the wireless system transmits a CW and receives a second signal over a second AIoT channel based on the configuration. At the operation 1810, the wireless system transmits a third signal over a Uu physical uplink shared channel (PUSCH) based on the configuration and the second signal.

[0129] In some implementations, the configuration may be a configured grant. In some implementations, the configuration includes at least one of time resources or frequency resources for at least one of the first AIoT channel, the second AIoT channel, the CW, or the Uu PUSCH. In some implementations, the configured grant may be activated by a downlink control information (DCI) message. The configuration may further include a first time offset between the DCI and the transmitting the first signal over the first AIoT channel.

[0130] In some implementations, the configuration may include a first periodicity. The wireless system may transmit one or more first signals over the first AIoT channel based on the first periodicity. In some implementations, the configuration may include a second periodicity. The wireless system may transmit one or more third signals over the Uu PUSCH based on the second periodicity and the one or more first signals.

[0131] In some implementations, the wireless system may determine an indication of a CW transmission availability based on the configuration. The wireless system may receive the second signal over the second AIoT channel based on an AIoT link configuration.

[0132] In some implementations, the wireless system may determine an indication of a CW transmission availability based on the configuration. The w ireless system may transmit a CW transmission configuration over the first AIoT channel based on the configuration. The w ireless system may receive the second signal over the second AIoT channel based on the configuration.

[0133] In some implementations, the configuration may be received using any of a radio resource control (RRC) setup message, an RRC reconfiguration message, or a system information message.

[0134] In some implementations, the DCI may be scrambled by one of a configured schedule (CS) radio network temporary identifier (RNTI) or an AIoT RNTI.

[0135] In some implementations, the wireless system may transmit to the base station intermediate node capability information. The intermediate node capability information may indicate at least one of a first capability information of receiving in a frequency-division duplex (FDD) uplink (UL) band or a second capability information of transmitting a CW tone in the FDD UL band. In some implementations, to transmit the intermediate node capability information, an intermediate node of the wireless system may transmit the first capability information, and a UE of the wireless system may transmit the second capability information.

[0136] In some implementations, the wireless system may include a UE. The first capability information and the second capability information are transmitted by the UE. In some implementations, an AIoT device may perform the transmitting the CW. In some implementations, the UE may perform the transmitting the CW.

[0137] In some implementations, a first UE of the wireless system may perform the transmitting the first signal, the receiving the second signal, and the transmitting the third signal. The first UE and a second UE of the wireless system may perform the receiving the configuration. In some implementations, the first UE may perform the transmitting the CW. In some implementations, the second UE may perform the transmitting the CW.

[0138] In some implementations, the wireless system may include a UE. The UE may perform the receiving the configuration. The base station may perform the transmitting the first signal and the recehing the second signal. An AIoT device may perform the transmitting the second signal. The second signal and the third signal may be the same signal. In some implementations, the UE may perform the transmitting the CW. In some implementations, the UE may transmit the CW in response to the UE detecting the first signal transmitted by the base station. In some implementations, the base stationperforms the transmitting the CW. In some implementations, the UE and the AIoT device may be the same device.

[0139] This disclosure incorporates the following by reference in their entireties.[1] 3GPP RP -234058, New SID: Study on solutions for AIoT (Internet of Things) in NR, Huawei, Dec 2023.[2] 3GPP TR 38.848, Study on AIoT (Internet of Things) in RAN, Release 18, 2023.

[0140] FIG. 19 illustrates an example communications system 1900. Communications system 1900 includes an access node 1910 serving user equipments (UEs) with coverage 1901, such as UEs 1920. In a first operating mode, communications to and from a UE passes through access node 1910 with a coverage area 1901. The access node 1910 is connected to a backhaul network 1915 for connecting to the internet, operations and management, and so forth. In a second operating mode, communications to and from a UE do not pass through access node 1910, however, access node 1910 typically allocates resources used by the UE to communicate when specific conditions are met. Communications between a pair of UEs 1920 can use a sidelink connection (shown as two separate one-way connections 1925). In FIG. 19, the sideline communication is occurring between two UEs operating inside of coverage area 1901. However, sidelink communications, in general, can occur when UEs 1920 are both outside coverage area 1901, both inside coverage area 1901, or one inside and the other outside coverage area 1901. Communication between a UE and access node pair occur over uni -directional communication links, where the communication links between the UE and the access node are referred to as uplinks 1930, and the communication links between the access node and UE is referred to as dow nlinks 1935.

[0141] Access nodes may also be commonly referred to as Node Bs, evolved Node Bs (eNBs), next generation (NG) Node Bs (gNBs), master eNBs (MeNBs), secondary eNBs (SeNBs), master gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on, while UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like. Access nodes may provide wireless access in accordance w ith one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE- A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na / b / g / n / ac / ad / ax / ay / be, etc. While it is understood that communications systems may employ multiple access nodes capable ofcommunicating w ith a number of UEs, only one access node and two UEs are illustrated for simplicity.

[0142] FIG. 20 illustrates an example communication system 2000. In general, the system 2000 enables multiple w ireless or wired users to transmit and receive data and other content. The system 2000 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non-orthogonal multiple access (NOMA).

[0143] In this example, the communication system 2000 includes electronic devices (ED) 2oioa-2oioc, radio access networks (RANs) 2020a-2020b, a core network 2030, a public switched telephone network (PSTN) 2040, the Internet 2050, and other networks 2060. While certain numbers of these components or elements are shown in FIG. 20, any number of these components or elements may be included in the system 2000.

[0144] The EDs 2oioa-2oioc are configured to operate or communicate in the system 2000. For example, the EDs 2oioa-2oioc are configured to transmit or receive via wireless or w ired communication channels. Each ED 2oioa-2oioc represents any suitable end user device and may include such devices (or may be referred to) as a user equipment or device (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, or consumer electronics device.

[0145] The RANs 2020a-2020b here include base stations 2070a-2070b, respectively. Each base station 2070a-2070b is configured to wirelessly interface with one or more of the EDs 2otoa-2otoc to enable access to the core network 2030, the PSTN 2040, the Internet 2050, or the other netw orks 2060. For example, the base stations 2070a-2070b may include (or be) one or more of several well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNB), a Next Generation (NG) NodeB (gNB), a gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. The EDs 2otoa-2otoc are configured to interface and communicate with the Internet 2050 and may access the core network 2030, the PSTN 2040, or the other networks 2060.

[0146] In the embodiment shown in FIG. 20, the base station 2070a forms part of the RAN 2020a, which may include other base stations, elements, or devices. Also, the base station 2070b forms part of the RAN 2020b, w hich may include other base stations,elements, or devices. Each base station 2070a-2070b operates to transmit or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell.” In some embodiments, multiple-input multiple-output (MIMO) technology may be employed having multiple transceivers for each cell.

[0147] The base stations 2070a-2070b communicate with one or more of the EDs 2oioa-2oioc over one or more air interfaces 2090 using wireless communication links. The air interfaces 2090 may utilize any suitable radio access technology.

[0148] It is contemplated that the system 2000 may use multiple channel access functionality, including such schemes as described above. In particular embodiments, the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be utilized.

[0149] The RANs 2020a-2020b are in communication with the core network 2030 to provide the EDs 2oioa-2otoc with voice, data, application, Voice over Internet Protocol (VoIP), or other services. Understandably, the RANs 2020a-2020b or the core network 2030 may be in direct or indirect communication with one or more other RANs (not shown). The core network 2030 may also serve as a gateway access for other networks (such as the PSTN 2040, the Internet 2050, and the other networks 2060). In addition, some or all of the EDs 2oioa-2otoc may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition thereto), the EDs may communicate via wired communication channels to a service provider or switch (not shown), and to the Internet 2050.

[0150] Although FIG. 20 illustrates one example of a communication system, various changes may be made to FIG. 20. For example, the communication system 2000 could include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0151] FIGs. 21A and 21B illustrate example devices that may implement the methods and teachings according to this disclosure. In particular, FIG. 21A illustrates an example ED 2110, and FIG. 21B illustrates an example base station 2170. These components could be used in the system 2000 or in any other suitable system.

[0152] As shown in FIG. 21A, the ED 2110 includes at least one processing unit 2100. The processing unit 2100 implements various processing operations of the ED 2110. For example, the processing unit 2100 could perform signal coding, data processing, power control, input / output processing, or any other functionality enabling the ED 2110 to operate in the system 2000. The processing unit 2100 also supports the methods andteachings described in more detail above. Each processing unit 2100 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 2100 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0153] The ED 2110 also includes at least one transceiver 2102. The transceiver 2102 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 2104. The transceiver 2102 is also configured to demodulate data or other content received by the at least one antenna 2104. Each transceiver 2102 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received w irelessly or by wire. Each antenna 2104 includes any suitable structure for transmitting or receiving wireless or w ired signals. One or multiple transceivers 2102 could be used in the ED 2110, and one or multiple antennas 2104 could be used in the ED 2110. Although shown as a single functional unit, a transceiver 2102 could also be implemented using at least one transmitter and at least one separate receiver.

[0154] The ED 2110 further includes one or more input / output devices 2106 or interfaces (such as a wired interface to the Internet 2050). The input / output devices 2106 facilitate interaction with a user or other devices (network communications) in the network. Each input / output device 2106 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0155] In addition, the ED 2110 includes at least one memory72108. The memory72to8 stores instructions and data used, generated, or collected by the ED 2ito. For example, the memory 2108 could store software or firmware instructions executed by the processing unit(s) 2 too and data used to reduce or eliminate interference in incoming signals. Each memory 2108 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and the like.

[0156] As shown in FIG. 2tB, the base station 2170 includes at least one processing unit 2150, at least one transceiver 2152, which includes functionality for a transmitter and a receiver, one or more antennas 2156, at least one memory72158, and one or more input / output devices or interfaces 2t66. A scheduler, which w ould be understood by one skilled in the art, is coupled to the processing unit 2150. The scheduler could be included within or operated separately from the base station 2170. The processing unit 2150implements various processing operations of the base station 2170, such as signal coding, data processing, power control, input / output processing, or any other functionality. The processing unit 2150 can also support the methods and teachings described in more detail above. Each processing unit 2150 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 2150 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0157] Each transceiver 2152 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 2152 further includes any suitable structure for processing signals received wirelessly or by wire from one or more EDs or other devices. Although shown combined as a transceiver 2152, a transmitter and a receiver could be separate components. Each antenna 2156 includes any suitable structure for transmitting or receiving wireless or w ired signals. While a common antenna 2156 is shown here as being coupled to the transceiver 2152, one or more antennas 2156 could be coupled to the transceiv er(s) 2152, allowing separate antennas 2156 to be coupled to the transmitter and the receiver if equipped as separate components. Each memory' 2158 includes any suitable volatile or non-volatile storage and retrieval device(s). Each input / output device 2166 facilitates interaction with a user or other devices (network communications) in the network. Each input / output device 2166 includes any suitable structure for providing information to or receiving / providing information from a user, including network interface communications.

[0158] FIG. 22 is a block diagram of a computing system 2200 that may be used for implementing the devices and methods disclosed herein. For example, the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vary from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 2200 includes a processing unit 2202. The processing unit includes a central processing unit (CPU) 2214, memory72208, and may7further include a mass storage device 2204, a video adapter 2210, and an I / O interface 2212 connected to a bus 2220.

[0159] The bus 2220 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 2214 may comprise any type of electronic data processor. The memory 2208 maycomprise any type of non-transitory system memory such as static random access memoiy (SRAM), dynamic random access memory’ (DRAM), synchronous DRAM (SDRAM), read-only memory’ (ROM), or a combination thereof. In an embodiment, the memoiy’ 2208 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.

[0160] The mass storage 2204 may comprise any type of non-transitoiy storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 2220. The mass storage 2204 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.

[0161] The video adapter 2210 and the I / O interface 2212 provide interfaces to couple external input and output devices to the processing unit 2202. As illustrated, examples of input and output devices include a display 2218 coupled to the video adapter 2210 and a mouse, keyboard, or printer 2216 coupled to the I / O interface 2212. Other devices may be coupled to the processing unit 2202, and additional or fewer interface cards may be utilized. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide an interface for an external device.

[0162] The processing unit 2202 also includes one or more network interfaces 2206, which may comprise wired links, such as an Ethernet cable, or wireless links to access nodes or different networks. The network interfaces 2206 allow the processing unit 2202 to communicate with remote units via the networks. For example, the network interfaces 2206 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In an embodiment, the processing unit 2202 is coupled to a local-area network 2222 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.

[0163] It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a performing unit or module, a generating unit or module, an obtaining unit or module, a setting unit or module, an adjusting unit or module, an increasing unit or module, a decreasing unit or module, a determining unit or module, a modifying unit or module, a reducing unit or module, a removing unit or module, or a selecting unit or module. The respective units or modules may be hardware, softw are, or a combination thereof. For instance, one or moreof the units or modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0164] Although the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Claims

What is Claimed is:

1. A method implemented in a wireless system, comprising: receiving a configuration for a Uu uplink and an Ambient Internet of Things (AIoT) link; transmitting a first signal over a first AIoT channel of the AIoT link based on the configuration; receiving a second signal over a second AIoT channel of the AIoT link based on the configuration, the second signal being an AIoT uplink signal associated with a carrier wave (CW); and transmitting a third signal over a Uu physical uplink shared channel (PUSCH) based on the configuration and the second signal.

2. The method of claim 1, further comprising: transmitting the CW to an AIoT device, wherein the second signal is a backscatter-wave signal of the CW.

3. The method of claim 1 or 2, wherein the configuration is a configured grant that includes at least one of time resources or frequency resources for at least one of the first AIoT channel, the second AIoT channel, the CW, or the Uu PUSCH.

4. The method of claim 1 or 2, wherein the configuration is a configured grant that is activated by a downlink control information (DCI) message, and the configuration further includes at least one of a first time offset between the DCI message and the transmitting the first signal over the first AIoT channel or a second time offset between the DCI message and a transmission of the third signal.

5. The method of any of claims 1-4, wherein the configuration includes a first periodicity, the method further comprising: transmitting one or more first signals over the first AIoT channel based on the first periodicity.

6. The method of any of claims 1-5, wherein the configuration includes a second periodicity, the method further comprises: transmitting one or more third signals over the Uu PUSCH based on the second periodicity and the one or more first signals.

7. The method of any of claims 1-6, wherein the configuration includes an indication of a CW transmission requirement or availability.

8. The method of claim 7, wherein the configuration includes an indication of CW transmission configuration forwarding over AIoT link, the method further comprises:transmitting a CW transmission configuration over the first AIoT channel based on the configuration.

9. The method of claim 4, wherein the DCI message is scrambled by one of a configured schedule (CS) radio network temporary identifier (RNTI) or an AIoT RNTI.

10. The method of any of claims 1-9, further comprising: transmitting, to a base station of the wireless system, intermediate node capability information, the intermediate node capability information indicating at least one of first capability information of receiving in a frequency-division duplex (FDD) uplink (UL) band or second capability information of transmitting a CW tone in the FDD UL band.

11. The method of claim 10, the transmitting the intermediate node capability information comprising: transmitting, by an intermediate node of the wireless system, the first capability information; and transmitting, by a user equipment (UE) of the wireless system, the second capability information.

12. The method of claim 10, w herein the first capability information and the second capability information are transmitted a UE of the wireless system.

13. The method of any of claims 2-12, wherein the transmitting the first signal, the receiving the second signal, and the transmitting the third signal are performed by a first UE of the wireless system; and the transmitting the CW is performed by a second UE of the wireless system.

14. The method of claim 13, wherein the first UE and the second UE each receives at least part of the configuration.

15. A wireless system, comprising: a base station configured to transmit a first configuration for a Uu uplink and an Ambient Internet of Things (AIoT) link; a first node configured operatively coupled between the base station and one or more AIoT devices and configured to: receive the first configuration from the base station; transmit a first signal over a first AIoT channel of the AIoT link based on the first configuration; receive a second signal over a second AIoT channel of the AIoT link based on the first configuration, the second signal being an AIoT uplink signal associated with a carrier wave (CW); andtransmit, to the base station, a third signal over a Uu physical uplink shared channel (PUSCH) based on the first configuration and the second signal.

16. The wireless system of claim 15, wherein the wireless system further comprises a second node configured to receive a second configuration of the CW from the base station and transmit the CW to the one or more AIoT devices based on the second configuration of the CW, w herein the second configuration comprises at least one of time resources or frequency resources for the CW.

17. The wireless system of claim 16, wherein the second configuration is a configured grant that is activated by a downlink control information (DCI) message, and the second configuration further includes at least one of a first time offset between the DCI message and the transmitting the first signal over the first AIoT channel or a second time offset between the DCI message and a transmission of the third signal.

18. The wireless system of claim 16 or 17, wherein the second configuration includes at least one of an indication of a CW transmission requirement or availability, or an indication of CW transmission configuration forwarding over AIoT link.

19. The wireless system of claim 15, wherein the first configuration comprises at least one of time resources or frequency resources for the CW, the first node is further configured to transmit the CW to the one or more AIoT devices according to the at least one of time resources or frequency resources for the CW.

20. An apparatus, comprising: at least one processor; and at least one non-transitoiy computer readable storage medium storing programming, the programming including instructions that, when executed by the at least one processor, cause the apparatus to perform a method according to any of claims 1-14.

21. At least one non-transitoiy computer-readable medium having instructions stored thereon that, when executed by a processor, cause the wireless system to perform a method according to any of claims 1-14.

Images