Method and apparatus for carrier wave generation for ambient internet of things (AIOT) devices

Abstract

Methods, apparatuses, and computer program products that provide for carrier wave generation for ambient internet of things (AIoT) devices. In the context of a method, the method includes providing for reception of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and providing for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a radio resource control (RRC) state of a carrier wave node.

Description

METHOD AND APPARATUS FOR CARRIER WAVE GENERATION FOR AMBIENTINTERNET OF THINGS (AIOT) DEVICESRELATED APPLICATION

[0001] This application claims priority to FI Application No. 20245389 filed April 3, 2024, which is incorporated herein by reference in its entirety.TECHNOLOGICAL FIELD

[0002] An example embodiment relates generally to techniques for carrier wave generation for ambient internet of things (AIoT) devices and, more particularly, to techniques for configuring carrier wave generator entities located outside of AIoT topologies.BACKGROUND

[0003] Some terminals, such as AIoT device, may harvest energy for various operations, such as operations performed in accordance with an active mode or a passive mode. In some cases, a terminal may use energy harvested from radio frequency waves or other forms of energy that may be harvested in various deployment scenario. The terminal may operate with relatively low (e.g., ultra-low) power, for example, ranging from one microwatt to hundreds of microwatts. For instance, the terminal may include one or more components (e.g., an energy harvester) configured for harvesting energy from radio frequency waves, and an output power of the energy harvester may be from one microwatt to tens of microwatts. In another instance, the terminal may include one or more other components (e.g., a solar panel) configured for energy harvesting from solar radiation (e.g., ultraviolet (UV) light, visible light, infrared light), and an output power of the solar panel may be less than a milliwatt. In some cases, a terminal configured to harvest energy (e.g., an energy harvesting device) may operate in an active mode in which the terminal may use harvested energy and a circuit (e.g., an active circuit) to transmit signaling. In some other cases, a terminal configured to harvest energy may operate in a passive mode (e.g., a tag, a device that lacks active transmission circuitry), in which the terminal may use backscattering to communicate (e.g., transmit data).BRIEF SUMMARY

[0004] Methods, apparatuses, and computer program products are disclosed to provide for improved carrier wave generation for AIoT devices. In this regard, at least a method, apparatus, and computer program product provide for configuration of a carrier wave node(e.g., a user equipment (UE)), which is outside of an AIoT topology, to generate and transmit carrier wave signals to one or more AIoT devices. By providing for the configuration of the carrier wave node to generate and transmit carrier wave signals to the one or more AIoT devices, the method, apparatus, and computer program product may provide for reduced scheduling conflicts at the carrier wave node, such as between scheduled data transmissions (or receptions) and scheduled carrier wave transmissions. In some aspects, by reducing scheduling conflicts, the method, apparatus, and computer program product may provide for more efficient communication at the carrier wave node and at the one or more ambient AIoT devices, such as by reducing latency.

[0005] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to provide for reception of first control information from a network node, wherein the first control information schedules reception of downlink data at the apparatus over a first duration; provide for reception of second control information from the network node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and provide for transmission of the carrier wave to the AIoT device over a second duration and in accordance with the second control information.

[0006] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to provide for transmission of first control information to a carrier wave node, wherein the first control information schedules reception of downlink data over a first duration; and provide for transmission of second control information to the carrier wave node, wherein the second control information schedules transmission of a carrier wave to at least an ambient internet of things (AIoT) device over a second duration.

[0007] In at least one example embodiment, a method is provided comprising providing for reception of first control information from a network node, wherein the first control information schedules reception of downlink data at a carrier wave node over a first duration; providing for reception of second control information from the network node, wherein the second control information is associated with transmission of a carrier wave to at least anambient internet of things (AIoT) device; and providing for transmission of the carrier wave to the AIoT device over a second duration, in accordance with the second control information.

[0008] In at least one example embodiment, a method is provided comprising providing for transmission of first control information to a carrier wave node, wherein the first control information schedules reception of downlink data over a first duration; and providing for transmission of second control information to the carrier wave node, wherein the second control information schedules transmission of a carrier wave to at least an ambient internet of things (AIoT) device over a second duration.

[0009] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to provide for reception of first control information from a network node, wherein the first control information schedules reception of downlink data at the apparatus over a first duration; provide for reception of second control information from the network node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and provide for transmission of the carrier wave to the AIoT device over a second duration and in accordance with the second control information.

[0010] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to provide for transmission of first control information to a carrier wave node, wherein the first control information schedules reception of downlink data over a first duration; and provide for transmission of second control information to the carrier wave node, wherein the second control information schedules transmission of a carrier wave to at least an ambient internet of things (AIoT) device over a second duration.

[0011] In at least one example embodiment, an apparatus is provided that comprises means for providing for reception of first control information from a network node, wherein the first control information schedules reception of downlink data at the apparatus over a first duration; providing for reception of second control information from the network node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and providing for transmission of thecarrier wave to the AIoT device over a second duration, in accordance with the second control information.

[0012] In at least one example embodiment, an apparatus is provided that comprises means for providing for transmission of first control information to a carrier wave node, wherein the first control information schedules reception of downlink data over a first duration; and providing for transmission of second control information to the carrier wave node, wherein the second control information schedules transmission of a carrier wave to at least an ambient internet of things (AIoT) device over a second duration.

[0013] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to provide for reception of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and provide for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a radio resource control (RRC) state of the apparatus.

[0014] In at least one example embodiment, an apparatus is provided comprising at least one processor and at least one memory including computer program code (e.g., instructions) with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to provide for transmission of first control information to a carrier wave node, wherein the first control information schedules transmission of uplink data at the carrier wave node via a first carrier; and provide for transmission of second control information to the carrier wave node based at least in part on a radio resource control (RRC) state of the carrier wave node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device.

[0015] In at least one example embodiment, a method is provided comprising providing for reception of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; providing for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a radio resource control (RRC) state of a carrier wave node.

[0016] In at least one example embodiment, a method is provided comprising providing for transmission of first control information to a carrier wave node, wherein the first control information schedules transmission of uplink data at the carrier wave node via a first carrier; and providing for transmission of second control information to the carrier wave node based at least in part on a radio resource control (RRC) state of the carrier wave node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device.

[0017] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to provide for reception of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and provide for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a radio resource control (RRC) state of the apparatus.

[0018] In at least one example embodiment, a non-transitory computer readable storage medium is provided. The non-transitory computer readable storage medium comprises computer instructions that, when executed by an apparatus, cause the apparatus to provide for transmission of first control information to a carrier wave node, wherein the first control information schedules transmission of uplink data at the carrier wave node via a first carrier; and provide for transmission of second control information to the carrier wave node based at least in part on a radio resource control (RRC) state of the carrier wave node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device.

[0019] In at least one example embodiment, an apparatus is provided that comprises means for providing for reception of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and providing for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a radio resource control (RRC) state of the apparatus.

[0020] In at least one example embodiment, an apparatus is provided that comprises means for providing for transmission of first control information to a carrier wave node, wherein the first control information schedules transmission of uplink data at the carrier wavenode via a first carrier; and providing for transmission of second control information to the carrier wave node based at least in part on a radio resource control (RRC) state of the carrier wave node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device.BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Having thus described some example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0022] Figure 1 is a block diagram of an example communication system in which the apparatus of Figure 2 may be deployed;

[0023] Figure 2 is a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present disclosure;

[0024] Figure 3 is a process flow illustrating operations performed, such as within the communication system of Figure 1, to provide for carrier wave generation in accordance with an example embodiment;

[0025] Figure 4 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for carrier wave generation in accordance with an example embodiment;

[0026] Figure 5 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for carrier wave generation in accordance with an example embodiment;

[0027] Figure 6 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for carrier wave generation in accordance with an example embodiment; and

[0028] Figure 7 is a flow chart illustrating operations performed, such as by one example embodiment of the apparatus of Figure 2, in order to provide for carrier wave generation in accordance with an example embodiment.DETAILED DESCRIPTION

[0029] Some embodiments of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the disclosure are shown. Indeed, various embodiments of the disclosure may be embodied in many different forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and / or stored in accordance with embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present disclosure.

[0030] Additionally, as used herein, the term ‘circuitry’ refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and / or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and / or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that use software or firmware for operation even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term ‘circuitry’ also includes an implementation comprising one or more processors and / or portion(s) thereof and accompanying software and / or firmware. As another example, the term ‘circuitry’ as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device (such as a core network apparatus), field programmable gate array, and / or other computing device.

[0031] As illustrated in the example of Figure 1 , a communications system may include one or more ambient loT (AIoT) devices, such as an AIoT device 19. In some embodiments, the AIoT device 19 may be (or otherwise include) a radio frequency identification (RFID) device. An RFID device may also be referred to herein as an RFID tag or, more simply, a tag. Some AIoT devices, such as RFID tags, may be used with (e.g., may operate in accordance with) one or more backscattering technologies. In other words, some AIoT devices may communicate with one or more other devices (e.g., the UE 10, the UE 11, the access node 12) via backscattering. AIoT devices may be deployed in various vertical industries including, but not limited to logistics, manufacture industries, transportation industries, and energy industries. As such, deploying AIoT devices (e.g., passive devices) in both public and private networks may provide one or more benefits to the communicationssystem (e.g., a 5G ecosystem). In some embodiments, AIoT devices may be relatively low (e.g., ultra-low) complexity devices and / or devices with a relatively small terminal size or form factor (e.g., a thickness on the order of mm). Additionally, or alternatively, AIoT devices may be associated with relatively low maintenance (e.g., may be maintenance-free), and may have a relatively long lifecycle. An AIoT device may include a battery-less terminal or a terminal with constrained (e.g., limited) energy storage capability. For example, an AIoT device may store energy via a capacitor.

[0032] As illustrated in the example of Figure 1, the AIoT device 19 may operate in accordance with one or more topologies. In some examples, the AIoT device 19 may operate in accordance with a first topology in which the AIoT device 19 may directly communicate with an access node (e.g., a base station). That is, the AIoT device 19 may directly (unidirectionally or bidirectionally) communicate with one or more base stations in accordance with the first topology. Communication between the access node and the AIoT device 19 may include AIoT data and / or signaling. For example, the AIoT device 19 may receive a signal from the access node and may use the signal to communicate information (e.g., data) to the access node. In some examples, the AIoT device 19 may communicate data via modulating and backscattering a carrier wave signal. For example, the AIoT device 19 may modulate the data over the backscattered signal. The first topology may include a first access node transmitting to the AIoT device and a second access node receiving from the AIoT device.

[0033] In some other examples, as illustrated in Figure 1, the AIoT device 19 may operate in accordance with a second topology in which the AIoT device 19 may communicate with the access node 12 (e.g., a base station) via one or more intermediate nodes. In other words, an intermediate node may transfer information between the access node 12 and the AIoT device 19. An intermediate node may also be referred to herein as an assisting node. In some examples, and the access node 12 (e.g., base station) and / or an intermediate node (e.g., the UE 10 or the UE 11, which may also be referred to as assisting nodes) may be multiple access nodes or multiple intermediate nodes, respectively. The intermediate node may be a relay, IAB node, UE, or repeater (e.g., relay), among other examples of devices that may serve as an intermediate node. The second topology may support monostatic and bistatic communications. In some examples of monostatic communication, the AIoT device 19 may communicate bidirectionally with a single intermediate node (e.g., the UE 10), and the intermediate node may communicate (e.g., directly, and bidirectionally) with the access node12. In some examples, the intermediate node may be physically located in between the AIoT device 19 and the access node 12, thereby extending the range over which the access node 12 may communicate with the AIoT device 19 (relative to communications in accordance with the first topology). In accordance with the monostatic mode, the intermediate node may transfer (e.g., relay, forward) AIoT data and / or signaling between the access node 12 and the AIoT device 19. Additionally, or alternatively, the assisting node 12 may communicate with the AIoT device 19 in accordance with the bistatic mode. For example, the access node 12 may use a bistatic communication mode for communications with the AIoT device 19. In some aspects, one or more links in the one or more topologies may be bidirectional or unidirectional. For example, a link between the AIoT device 19 and the access node 12 may be bidirectional or unidirectional. Additionally, or alternatively, a link between the AIoT device 19 and an intermediate node (e.g., the UE 10 or the UE 11) may be bidirectional or unidirectional. In some aspects, a link between the assess node 12 and the intermediate node may be bidirectional or unidirectional.

[0034] In some aspects, in accordance with the one or more topologies, the AIoT device 19 may be provided with a carrier wave from one or more intermediate nodes, which may be inside or outside of an topology (e.g., the first topology and / or the second topology). For example, the AIoT device 19 may receive a carrier wave from a UE 10, which may be inside of a topology (e.g., the second topology). Additionally, or alternatively, the AIoT device 19 may receive a carrier wave from a UE 11, which may be outside of a topology (e.g., the first topology, the second topology). The mixture of indoor and outdoor placement of such nodes may change based on implementation. As described herein, a carrier wave is a signal (e.g., a wave, a carrier) used by AIoT devices to modulate and backscatter information (e.g., an AIoT reply) to another device (e.g., the access node 12, the UE 11, the UE 10). In some examples, the carrier may is different from an activation signal. For example, an activation signal may activate an AIoT device (e.g., any type of AIoT device, such as a passive, semi-passive, or active AIoT device), while a carrier wave may carry information (e.g., be used for an AIoT transmission) for one or more AIoT devices which cannot actively (e.g., and independently) generate a signal. In other words, a carrier wave may be transformed by an AIoT device (e.g., to include at least an identifier of the AIoT ID) and reflected (e.g., backscattered) to another device, for example, immediately or with a delay, which may be pre-configured by a device (e.g., a device that transmitted the activation signal, which may be referred to as an activator node).

[0035] In some examples, such as examples in which the AIoT device 19 cannot generate (or amplify) backscattered signals, the access node 12 may select an entity (e.g., a UE) for generating a carrier wave for the AIoT device 19. In some such examples, the access node 12 may select the entity (e.g., a carrier wave generator entity) based on a location of the entity relative to the AIoT device 19. In other words, the access node 12 may select an entity that is relatively close (e.g., as close as possible) to the AIoT device 19, such that the entity may transmit the carrier wave at suitable (e.g., high enough) power, and on a suitable carrier frequency, so that the information carried by the backscattered carrier wave (e.g., the AIoT reply) may be successfully decoded by a reader (e.g., the access node 12, another dedicated reader device) within the coverage area of the AIoT device 19. Accordingly, for an AIoT session with the AIoT device 19, the access node 12 may select a carrier wave generator entity for the AIoT device 19 based on the relative proximity of the carrier wave generator entity to the AIoT devicel9. In some examples, selecting a carrier wave generator entity based on relative proximity of the carrier wave generator entity to the AIoT device 19 may increase a likelihood of success of the AIoT session with the AIoT device 19.

[0036] In some such examples, however, the selected carrier wave generator entity may be outside of one or more AIoT topologies. For example, as illustrated in Figure 1, the access node 12 may select the UE 11 as a carrier wave generator entity for the AIoT device 19. When the selected carrier wave generator entity is outside one or more AIoT topologies (e.g., when the selected carrier wave generator entity has not established or been otherwise configured for an AIoT session), the selected carrier wave generator entity is considered not part of the AIoT session, and thus has not been configured (e.g., pre-configured) to assist the AIoT session for an AIoT device (e.g., any of the targeted AIOT devices). In some such examples, there may be ambiguity at the selected carrier wave generator entity as to how the selected carrier wave generator entity (e.g., an NR UE for AIoT device proximity) can be triggered to transmit the carrier wave signal, for example, when said entity is operating in a radio resource control (RRC) inactive state or is actively engaged in other data communications (e.g., UL / DL traffic) or positioning services. In other words, when a carrier wave generator entity is located outside the AIoT network topologies, the carrier wave generator entity has not been pre-configured (e.g., has not yet been configured) to support AIoT sessions for targeted AIoT devices and, as such, the carrier wave generator entity may be unaware as to how the carrier wave generator entity is triggered to transmit a carrier wave signal (e.g., when the carrier wave generator entity is actively engaged in other data). Suchambiguities may reduce a performance of AIoT backscattering, reduce a reliability of communications between the AIoT device 19 and the access node 12 (e.g., due to scheduling conflicts at the carrier wave generator entity), and may lead to increased latency.

[0037] In some examples, in accordance with one or more techniques for carrier wave generation for AIoT devices, as described herein, the access node 12 may configure the UE11 (e.g., an NR UE which is outside of the first topology and the second topology) to transmit a carrier wave signal for one or more AIoT devices (e.g., the AIoT device 19). For example, such techniques may provide for carrier wave scheduling at a UE (e.g., the UE 11) for AIoT transmissions, along with uplink and / or downlink transmission scheduling at the UE. In some examples, the carrier wave scheduling may be different from activation signal scheduling. Additionally, in some examples, the carrier wave scheduling for UEs located outside one or more AIoT network topologies may be different from carrier wave scheduling for UEs located within one or more AIoT network topologies. For example, the scheduling for UEs located outside of one or more AIoT network topologies (e.g., the first topology, the second topology) may be based on priority.

[0038] For example, the access node 12 may schedule the UE 11 for a downlink (DL) data transmission. In some examples, the access node 12 and / or the UE 11 may determine that the carrier wave has a lower priority than the DL data. In such examples, the UE 11 may be configured to (e.g., the access node 12 may schedule the UE 11 to) delay the carrier wave transmission until finalization of the DL reception. In some other examples, the access node12 and / or the UE 11 may determine that the carrier wave has the same priority as the DL data. In such examples, and based on the UE duplexing capability, the UE 11 may be configured to (e.g., the access node 12 may schedule the UE 11 to) transmit the carrier wave and the DL data concurrently. For example, the carrier wave transmission may be frequencydivision duplexed (FDD) together with the DL data reception (e.g., subject to the UE duplexing capability). In yet some other examples, the access node 12 and / or the UE 11 may determine that the carrier wave has a higher priority than the DL data. In such examples, the UE 11 may be configured to (e.g., the access node 12 may schedule the UE 11 to) delay the DL data transmission, such that the carrier wave transmission precedes the DL data transmission.

[0039] Additionally, or alternatively, the access node 12 may schedule the UE 11 for an uplink (UL) data transmission. In some examples, a first carrier configured (e.g., scheduled) for the UL data transmission and a second carrier configured (e.g., scheduled) for the carrierwave transmission may overlap in frequency (e.g., may be the same carrier or may include one or more overlapping frequencies). In other words, in some examples, the carrier wave may coincide with the UL carrier. Additionally, in some such examples, the access node 12 and / or the UE 11 may determine that the carrier wave has a lower priority than the UL data. In such examples, the UE 11 may be configured to (e.g., the access node 12 may schedule the UE 11 to) delay the carrier wave transmission until the UL transmission is completed. In some other examples, the access node 12 and / or the UE 11 may determine that the carrier wave has the same priority as the UL data. In such examples, if the carrier wave and UL data transmission have different waveforms, the UE 11 may be configured to (e.g., the access node 12 may configure the UE 11 to) interleave the carrier wave transmission with the UL data transmission. For example, the UE 11 may be configured to (e.g., the access node 12 may configure the UE 11 to) puncture the UL data so as to provide available resources for the carrier transmission. Alternatively, in some examples, if the carrier wave and UL data transmission have the same waveform, the UE 11 may be configured to (e.g., the access node 12 may schedule the UE 11 to) piggyback the carrier wave transmission on the UL data transmission. In such examples, the network (e.g., the access node 12) may adjust the UL transmission power at the UE 11. For example, the access node 12 may transmit an indication to the UE 11 to adjust the transmission power (also referred to herein as transmit power) at the UE 11 for the UL data transmission to a transmit power that is suitable for the carrier wave transmission. In some examples, the access node 12 may indicate for the UE 11 to adjust the transmit power to a highest value (e.g., the maximum) between a transmit power associated with the carrier wave signal (e.g., a threshold transmit power for carrier wave signals, a transmit power expected for carrier wave signals) or a transmit power associated with the scheduled UL data transmission.

[0040] In some examples, such as examples in which the first carrier for the UL data transmission and the second carrier for the carrier wave transmission are non-overlapping (e.g., are different carriers), the access node 12 may schedule an UL carrier aggregation transmission at the UE 11 , in which a first component carrier (CC) carriers the UL data and the second CC carries the carrier wave. In some such examples, the access node 12 may assigns multiple (e.g., different) transmit powers to multiple (e.g., different) CCs. For example, the access node 12 may assign different transmit powers to the first CC and the second CC, to increase a likelihood that the uplink data can be successfully received (e.g., and decoded).

[0041] One or more techniques for carrier wave generation for AIoT devices, as described herein, may therefore provide for configuring a UE that is outside of the one or more AIOT topologies to transmit a carrier wave signal for one or more AIOT devices. In some examples, such techniques may provide enhanced coverage for the AIoT device 19 (e.g., for backscattering RFID tags and other types of AIoT devices in the communication system) as well as more efficient communication at carrier wave generation entities (e.g., the UE 11), which may improve efficiencies for loT-type of data transmissions (e.g., by the AIoT device 19).

[0042] The communication system of Figure 1 is also able to communicate with other networks, such as a public switched telephone network or the Internet 16, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 1 by “cloud” 18). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing. 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to- machine (M2M) or Internet of Things (loT) devices or for passengers on board vehicles, or ensuring service availability for critical communications, and future railway / maritime / aeronautical communications. Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (FEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). Each satellite in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node 22 or by a gNB located on-ground or in a satellite. The depicted system is an example of a part of a radio access system in which the communication system of Figure 1 may be deployed and in practice, the system may comprise a plurality of NodeBs, the user devices may have access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the NodeBs or may be a Home nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such asmicro-, femto- or picocells. The NodeBs of Figure 1 may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of NodeBs may be used to provide such a network structure.

[0043] As shown in Figure 1, for example, a communications system may include a plurality of devices configured to communicate via respective channels. In this regard, the user equipment may include a transmitter configured to communicate with a receiver of a base station. Conversely, the base station may include a receiver and a transmitter for communicating with a receiver of the user equipment. By way of example, the communication system may be deployed within a radio access architecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR, 5G). However, the system may be deployed in other applications including within other communication networks, such as a universal mobile telecommunications system (UMTS) radio access network (UTRAN or E-UTRAN), wireless local area network (WLAN or WiFi), worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra- wideband (UWB) technology, sensor networks, mobile ad-hoc networks (MANETs) and Internet Protocol multimedia subsystems (IMS) or any combination thereof. In this regard, Figure 1 depicts an example of a simplified system architecture showing some elements and functional entities (e.g., logical units), whose implementation may differ from what is shown. The connections shown in Figure 1 are logical connections and corresponding physical connections may be different. It is apparent to a person skilled in the art that the system may comprises other functions and structures than those shown in Figure 1. In the radio access architecture of Figure 1, user devices 20 and 21 are configured to be in wireless connection on one or more communication channels in a cell with an access node 22 (such as a NodeB) providing the cell. As used herein, an access node may also be referred to as a network node. The physical link from a user device to a NodeB is called the uplink or reverse link and the physical link from the NodeB to the user device is called the downlink or forward link. It should be appreciated that the NodeBs or their functionalities may be implemented by using any node, host, server, or access point (AP), etc. entity suitable for such a usage.

[0044] A communications system may include more than one NodeB in which case the NodeBs may also be configured to communicate with one another over links, wired orwireless, designed for various purposes. For example, such links may be used for signaling purposes. The NodeB is a computing device configured to control the radio resources of the communication system to which the NodeB may be coupled. The NodeB may also be referred to as a base station, an access point or any other type of interfacing device including a relay station capable of operating in a wired or wireless environment. The NodeB includes or is coupled to transceivers. From the transceivers of the NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to user devices. As such, the transceivers of the NodeB and the transceivers of the user devices may include transmitters and receivers configured to communicate via a channel with the trainable parameters of the transmitters and receivers able to be reconfigured in accordance with an example embodiment. The antenna unit may comprise a plurality of antennas or antenna elements. The NodeB is further connected to core network 15 (CN or next generation core NGC). Depending on the system, the counterpart on the CN side can be a serving gateway (S-GW, routing and forwarding user data packets), packet data network gateway (P-GW), for providing connectivity of user devices (UEs) to external packet data networks, or mobile management entity (MME), etc. The user device (also referred to as user equipment (UE), user terminal, terminal device, etc.) illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a user device may be implemented with a corresponding apparatus, such as a relay node. An example of such a relay node is a layer 3 relay (self-backhauling relay) towards the base station.

[0045] The user device typically refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that a user device may also be a nearly exclusive uplink device (e.g., an uplink-only device), of which an example is a camera or video camera loading images or video clips to a network. A user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without human-to-human or human-to-computer interaction. The user device (or in some embodiments a layer 3 relay node) is configured to perform one or more of userequipment functionalities. The user device may also be called a subscriber unit, mobile station, remote terminal, access terminal, user terminal or user equipment (UE) just to mention but a few names or apparatuses.

[0046] Various techniques described herein may also be applied to a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.

[0047] Although the apparatuses have been depicted as single entities, different units, processors and / or memory units (not all shown in Figure 1) may be implemented. Further, the number of reception and / or transmission antennas of the user devices may naturally vary according to a current implementation. 5G enables using multiple input - multiple output (MIMO) antennas, many more base stations or nodes than LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and employing a variety of radio technologies depending on service needs, use cases and / or spectrum available. 5G mobile communications supports a wide range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors, and real-time control. 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integratable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave). One of the concepts considered to be used in 5G networks is network slicing in which multiple independent and dedicated virtual sub-networks (network instances) may be created within the same infrastructure to run services that have different requirements on latency, reliability, throughput, and mobility.

[0048] The current architecture in LTE networks is fully distributed in the radio and fully centralized in the core network. The low latency applications and services in 5G require bringing the content close to the radio which leads to local break out and multi-access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data acquisition, mobile signature analysis, cooperative distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud / fog computing and grid / mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, and healthcare applications).

[0049] The communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet 16, or utilize services provided by them. The communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 1 by “cloud” 18). The communication system may also comprise a central control entity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.

[0050] Edge cloud may be brought into radio access network (RAN) by utilizing network function virtualization (NVF) and software defined networking (SDN). Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node operations will be distributed among a plurality of servers, nodes, or hosts. Application of cloudRAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU 12) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU 14).

[0051] It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent. Some other technology advancements that may be used are Big Data and all-IP, which may change the way networks are being constructed and managed. 5G (or new radio, NR) networks are being designed to support multiple hierarchies, where MEC servers can be placed between the core and the base station or nodeB (gNB). It should be appreciated that MEC can be applied in 4G networks as well.

[0052] 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (loT) devices or for passengers on board vehicles, or ensuring service availability for critical communications, and future railway / maritime / aeronautical communications. Satellite communication may utilize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hundreds of (nano)satellites are deployed). Each satellite in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells. The on-ground cells may be created through an on-ground relay node 12 or by a gNB located on-ground or in a satellite.

[0053] The depicted system is only an example of a part of a radio access system that may be deployed and in practice, the system may comprise a plurality of NodeBs, the user devices may have an access to a plurality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the NodeBs or may be a Home nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto- or picocells. The NodeBs of Figure 1 may provide any kind of these cells. A cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of NodeBs are required to provide such a network structure.

[0054] For fulfilling the need for improving the deployment and performance of communication systems, the concept of “plug-and-play” NodeBs has been introduced. Typically, a network which is able to use “plug-and-play” Node Bs, includes, in addition to Home NodeBs (HnodeBs), a home node B gateway, or HNB-GW (not shown in Figure 1). AHNB Gateway (HNB-GW), which is typically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.

[0055] One example of an apparatus 20 is depicted in Figure 2. As shown in Figure 2, the apparatus includes, is associated with, or is in communication with processing circuity 22, a memory 24 and a communication interface 26. The processing circuitry may be in communication with the 24 (e.g., a memory device) via a bus for passing information among components of the apparatus. The memory device 24 may be non-transitory and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device 24 may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processing circuitry). The memory device 24 may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present disclosure. For example, the memory device 24 could be configured to buffer input data for processing by the processing circuitry. Additionally, or alternatively, the memory device 24 could be configured to store instructions for execution by the processing circuitry. The apparatus 20 may, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus 20 may be embodied as a chip or chip set. In other words, the apparatus 20 may comprise one or more physical packages (e.g., chips) including materials, components and / or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and / or limitation of electrical interaction for component circuitry included thereon. The apparatus 20 may therefore, in some cases, be configured to implement an embodiment of the present disclosure on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.

[0056] The processing circuitry 22 may be embodied in a number of different ways. For example, the processing circuitry 22 may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit(MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processing circuitry 22 may include one or more processing cores configured to perform independently. A multi-core processing circuitry may enable multiprocessing within a single physical package. Additionally, or alternatively, the processing circuitry 22 may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and / or multithreading. In an example embodiment, the processing circuitry 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processing circuitry. Alternatively, or additionally, the processing circuitry 22 may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processing circuitry 22 may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processing circuitry 22 is embodied as an ASIC, FPGA or the like, the processing circuitry may be specifically configured hardware for conducting the operations described herein.Alternatively, as another example, when the processing circuitry 22 is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processing circuitry 22 may be a processor of a specific device (e.g., an image or video processing system) configured to employ an embodiment of the present disclosure by further configuration of the processing circuitry 22 by instructions for performing the algorithms and / or operations described herein. The processing circuitry 22 may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processing circuitry.

[0057] The communication interface 26 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and / or transmit data, including media content in the form of video or image files, one or more audio tracks or the like. In this regard, the communication interface 26 may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communications with a wireless communication network. Additionally, or alternatively, the communication interface 26 may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communication interface 26may alternatively or also support wired communication. As such, for example, the communication interface 26 may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms. The apparatus 20 may be (or be included in) one or more types of devices, such as an access node (e.g., a base station), a UE, and / or an AIoT device.

[0058] In one example embodiment, the access node 22 may include the apparatus 20. For example, the access node 22 may include one or more components (e.g., the processing circuity 22, the memory 24, the communication interface 26) configured to support one or more techniques for carrier wave generation for AIoT devices, as described herein. In another example embodiment, the UE 11 (or the UE 10) may include the apparatus 20. For example, the UE 11 may include one or more components (e.g., the processing circuity 22, the memory 24, the communication interface 26) configured to support one or more techniques for carrier wave generation for AIoT devices, as described herein. In yet another example embodiment, the AIoT device 19 may include the apparatus 20. For example, the AIoT 19 may include one or more components (e.g., the processing circuity 22, the memory 24, the communication interface 26) configured to support one or more techniques for carrier wave generation for AIoT devices, as described herein.

[0059] Figure 3 is a process flow illustrating operations performed, such as within the communication system of Figure 1, to configure UEs for carrier wave generation in accordance with an example embodiment. For example, the process flow illustrates some respective operations performed at the UE 11 (e.g., a selected carrier wave generation entity) and the access node 12. One or more operations performed at the UE 11 and the access node 12 may be performed in a different order than the example order shown. Additionally, or alternatively, one or more operations performed at the UE 11 and the access node 12 may be omitted and / or one or more other operations may be added.

[0060] In the example of Figure 3, the UE 11 UE may be outside of an AIoT topology. Accordingly, in some examples, the UE 11 may not be considered part of (e.g., may not be pre-configured for) an AIoT session. In accordance with one or more techniques of the present disclosure, the access node 12 may configure the UE 11 for transmission of a carrier wave. That is, the UE 11 may receive, from the access node 12 (e.g., a gNB), a configuration associated with carrier wave transmissions for one or more AIoT devices. In other words, in accordance with the present disclosure, the access node 12 may configure the UE 11 totransmit a carrier wave signal for one or more AIOT devices. The UE 11 may perform one or more carrier wave transmissions for the one or more AIoT devices using the received configuration. For example, the UE 11 may use the received configuration to perform one or more carrier wave transmissions based on the RRC state of the UE 11 , a duplexing capability of the UE 11 (e.g., whether the UE 11 includes frequency division duplex (FDD) capabilities or otherwise supports full-duplex communications), scheduling of UL or DL transmission by the UE, traffic constraints of the UE 11 , and / or power constraints of the UE 11.

[0061] In some examples, at step 30, the access node 12 may assess DL and / or UL activity at the UE 11. For example, the access node 12 may determine one or more traffic constraints of the UE 11 (e.g., UL and / or DL needs of the target UE itself). In some examples, the access node 12 may determine an amount of UL and / or DL data to be transmitted to or from, respectively, the UE 11. Additionally, or alternatively, the access node 12 may assess DL and / or UL activity associated with one or more other UEs.

[0062] In some examples, at step 32, the access node 32 may select the UE 11 as a carrier wave (CW) generator for one or more AIoT devices. In some examples, the access node 32 may select the UE 11 as the carrier wave generator based on location of the UE 11 relative to the one or more AIoT devices. In other words, the access node 32 may select the UE 11 as the carrier wave generator based on the relative proximity of the UE 11 to the one or more AIoT devices. Additionally, or alternatively, the access node 32 may select (e.g., and configure) the UE 11 to be a carrier wave generator based on the traffic constraints of the UE 11 , the FDD capabilities of the UE 11 , and / or power constraints of the UE 11.

[0063] In some examples, at step 34, the access node 12 may assess an availability of resources for the carrier wave (e.g., for one or more carrier wave transmissions), for example, compared to an availability of resources for UL and / or DL data (e.g., for one or more UL and / or DL data transmissions). The access node 12 may schedule one or more UL and / or DL data transmissions for the UE 11 (e.g., via first control information, such as downlink control information (DCI), a medium access control-control element (MAC-CE), or RRC message), and may determine an availability of resources for the carrier wave transmission(s), as well as for the scheduled UL and / or DL data transmission(s). In some examples, the first control information may be indicative of a carrier frequency (e.g., the first carrier) for the data transmission, a waveform type associated with the data transmission, a bandwidth associated with the data transmission, a transmit power associated with the data transmission, a durationassociated with the data transmission (e.g., the first duration), and / or a subframe index of a starting subframe of the data transmission.

[0064] At step 36, the UE 11 may be in an RRC connected state (e.g., may have established an RRC connection with the access node 12, such that the UE 11 may operate in an RRC connected state). Additionally, in some such examples, the UE 11 may be scheduled for DL data reception. For example, the access node 12 may have scheduled a DL data transmission for the UE 11 (e.g., via the first control information, such as via DO, a MAC- CE, or RRC message). In other words, step 36 may be representative of an example in which the UE 11 is in an RRC connected state and is scheduled for DL data reception. In some examples, the first control information may indicate one or more time and frequency resources for reception of the DL data. For example, the first control information may indicate a first carrier via which the UE 11 may receive the DL data and may also indicate a first duration over which the UE 11 may receive the DL data. In such examples, at step 36, the access node 12 may determine a first priority associated with the carrier wave and a second priority associated with the downlink data (e.g., the scheduled downlink data transmission).

[0065] In some examples, at step 36, the access node 12 may determine that the carrier wave has a lower priority than the DL data (e.g., the first priority is lower than the second priority). In such examples, the access node 12 may configure the UE 11 (e.g., via second control information, such as DCI, a MAC-CE, or RRC message) with a delay for the carrier wave transmission, such that the UE 11 may transmit the carrier wave after finalization of the DL reception. In other words, the access node 12 may schedule the carrier wave transmission at the UE 11 , such that the carrier wave transmission is delayed until the DL reception is completed. That is, if the carrier wave has lower priority than the DL data, the access node 12 may schedule the carrier wave transmission to be after DL reception. The UE 12 may receive the second control information (configuring the carrier wave transmission) from the access node while operating in the connected state. The second control information may be associated with transmission of a carrier wave to at least one AIoT device. In some examples, the access node 11 may configure the UE 11 via a DL control channel (e.g., via the second control information) to switch carriers, for example from the first (downlink) carrier associated with the DL data signal to a second (uplink) carrier associated with the carrier wave transmission, and to initiate a carrier wave transmission.

[0066] In some such examples, the second control information may indicate one or more parameters associated with the carrier wave. The one or more parameters may include a carrier frequency for the carrier wave (e.g., the second carrier), a waveform type for the carrier wave (e.g., whether the carrier wave is a single tone-sine wave, multi-tone-OFDM wave), a bandwidth associated with the carrier wave, a transmit power associated with the carrier wave, and / or a second duration over which the UE 11 may transmit the carrier wave. Additionally, in some examples, the second control information may indicate a starting subframe for the carrier wave transmission (e.g., a starting subframe of the second duration). In some examples, the access node 12 may indicate the starting subframe via a first delay (e.g., a first offset), which may correspond to a difference between the starting subframe of the carrier wave transmission and the last received (e.g., a most recently received) DL subframe. In other words, the carrier wave transmission may be configured to start at a subframe index, which is equal to the first offset plus the last DL subframe index (e.g., the subframe index corresponding to an ending subframe of the downlink transmission). In some examples, control information (e.g., the second control information) may indicate, to the UE 11, a value of the first offset. That is, in some examples, the value of the offset may be configured by the access node 12 via the second control signaling. The UE 11 may apply the first offset (and finish the DL data reception) and switch to the carrier wave transmission. In some examples, the UE 11 may determine (e.g., based on being configured with an offset relative to the ending subframe of the DL data reception) that the carrier wave signal is defined with a lower priority than the DL data signal.

[0067] In some other examples, at step 36, the access node 12 may determine that the carrier wave has the same priority as the DL data (e.g., the first priority is the same as the second priority). In such examples, the access node 12 may configure the UE 11 (e.g., via the second control information) to transmit the carrier wave signal while concurrently receiving the DL data. In other words, the access node 12 may configure the carrier wave transmission (e.g., via the second control information), such that the carrier wave transmission is FDD scheduled together with the DL reception. That is, if the carrier wave has the same priority as the DL data, the access node 12 may schedule the UE 12 to receive the DL data and may schedule the carrier wave transmission during the DL reception. In some examples, such configuring of the carrier wave transmission may be subject to the UE duplexing capability. In other words, in an FDD scenario, the UE 11 may continue the DL reception while transmitting the carrier wave signal (e.g., in UL spectrum). In some such examples, whileoperating in an RRC connected state, the UE 11 may be configured by the access node 12 (e.g., via a DL control channel, via the second control information) to continue the DL reception and start the carrier wave transmission.

[0068] In some such examples, the second control information may indicate the one or more parameters associated with the carrier wave. Additionally, in some examples, the second control information may indicate the starting subframe for the carrier wave transmission (e.g., the starting subframe of the second duration). In some examples, the access node 12 may indicate the starting subframe via a second delay (e.g., a second offset), which may correspond to a difference between the starting subframe of the carrier wave transmission and the starting subframe of DL data transmission. In other words, the carrier wave transmission may be configured to start at a subframe index, which is equal to the first DL subframe index (e.g., the subframe index corresponding to a starting subframe of the downlink transmission) plus the second offset. In some examples, control information (e.g., the second control information) may indicate a value of the second offset. That is, in some examples, the value of the second offset may be configured by the access node 12 via the second control signaling. The UE 11 may apply the second offset and transmit the carrier wave while continuing the DL data reception. In some examples, the UE 11 may determine (e.g., based on the configuration) that the carrier wave signal is defined with the same priority as the DL data signal.

[0069] In yet some other examples, at step 36, the access node 12 may determine that the carrier wave has a higher priority than the DL (e.g., the first priority is lower than the second priority). In such examples, the access node 12 may configure the UE 11 (e.g., via second control information) with a delay for the carrier wave transmission, such that the UE 11 may transmit the carrier wave before the DL reception. In other words, the access node 12 may schedule the carrier wave transmission at the UE 11 , such that the carrier wave transmission precedes the DL data reception. That is, if the carrier wave has higher priority than the DL data, the access node 12 may delay the DL data and schedule the carrier wave transmission before the DL reception. For example, the UE 12 may receive the second control information from the access node 12 while operating in the connected state, and the second control information may be associated with transmission of a carrier wave to at least an AIoT device. In other words, the access node 11 may configure the UE 11 via a DL control channel (e.g., via the second control information) to initiate a carrier wave transmission and to switchcarriers (e.g., from the uplink carrier associated with the carrier wave transmission to the downlink carrier associated with the DL data signal).

[0070] In some such examples, the second control information may indicate the one or more parameters associated with the carrier wave. Additionally, in some examples, the second control information may indicate the starting subframe for the carrier wave transmission (e.g., the starting subframe of the second duration). In some examples, the access node 12 may indicate the starting subframe via a third delay (e.g., a third offset), which may correspond to a difference between the ending subframe of the carrier wave transmission and the starting subframe of DL data transmission. In other words, the carrier wave transmission is configured to start at a subframe index, which is equal to the first DL subframe index (e.g., the subframe index corresponding to a starting subframe of the downlink transmission) minus the third offset. In some examples, control information (e.g., the second control information) may indicate, to the UE 11 , a value of the third offset. That is, in some examples, the value of the third offset may be configured by the access node 12 via the second control signaling. Accordingly, the UE 11 may apply the third offset (and finish the carrier wave transmission) and switch to the DL data reception. In some examples, the UE 11 may determine (e.g., based on being configured with an offset relative to the starting subframe of the DL data reception) that the carrier wave signal is defined with a higher priority than the DL data signal. As illustrated in step 36, the carrier wave transmission and DL reception are configured in relation to their respective priorities, which may prevent conflicting actions at the UE 11, and reduce a likelihood of Uu delays (e.g., unexpected Uu delays).

[0071] At step 38, the UE 11 may operate in an RRC connected state. Additionally, in some such examples, the UE 11 may be scheduled for UL data transmission. For example, the access node 12 may schedule an UL data transmission for the UE 11 (e.g., via the first control information). In other words, step 38 may be representative of an example in which the UE 11 is in an RRC connected state and is scheduled for UL data transmission. The first control information may indicate one or more time and frequency resources for transmission of the UL data. For example, the first control information may indicate a first carrier via which the UE 11 may transmit the UL data and may also indicate a first duration over which the UE 11 may transmit the UL data. In such examples, at step 38, the access node 12 may determine a first priority associated with the carrier wave and a second priority associated with the uplink data (e.g., the scheduled uplink data transmission). Additionally, the accessnode 12 may configure the UE 11 for the carrier wave transmission (e.g., based on the determined priorities). For example, the access node 12 may transmit the second control information to the UE 11, which may indicate the one or more parameters associated with the carrier wave.

[0072] In some examples, the UE 11 may receive the first control information before the second control information, after the second control information, or with the second control information (e.g., via a same downlink control message). In other words, the configuration of the UL data and the carrier wave may be done in any order, or at the same time, and how the UE 11 transmits the UL data and the carrier wave (e.g., whether one after the other or concurrently, which order to transmit), depends on the respective configuration parameters (e.g., the parameters associated with the carrier wave, the parameters associated with the UL data).

[0073] In some examples, the second control information may indicate for the UE 11 to use a second carrier (e.g., a carrier frequency) that is overlaps with the first carrier. In other words, the UE may be scheduled for an UL data transmission in a first carrier that coincides with (e.g., is the same carrier as) the second carrier configured for the carrier wave.

[0074] In some such examples, at step 38, the access node 12 may determine that the carrier wave has a lower priority than the UL data. In such examples, the access node 12 may configure the UE 11 to finish the scheduled UL transmission and to switch carriers (e.g., from the first carrier to the second carrier, which may be overlapping in frequency) for the carrier wave transmission. In other words, the carrier wave transmission may be delayed until the UL transmission is completed. That is, if the carrier wave has a lower priority than the UL data, the access node 12 may schedule the carrier wave transmission to be after the UL transmission.

[0075] In some other examples, at step 38, the access node 12 may determine that the carrier wave has the same priority as the UL data. Additionally, in such an example, the access node 12 may determine that the carrier wave waveform and UL waveforms are different. In such examples, the access node 12 may configure the UE 11 to interleave the UL data and carrier wave transmissions (e.g., to puncture the UL data transmission to free up resources for the carrier wave transmission). In other words, the UE 11 may interleave the scheduled UL with the carrier wave transmission (e.g., by puncturing some of the resources allocated for the UL data and replacing the punctured resources with the carrier wave signal). In some examples, the UE 11 may puncture the UL resources based on the allocatedbandwidth (e.g., based on whether the bandwidth allows for such puncturing). That is, if the carrier has the same priority as the UL data and the carrier wave waveform is different from the UL data waveform, the UE 11 may interleave resources (in time and / or frequency) allocated for the UL transmission and replace the resources with the carrier wave transmission.

[0076] In yet some other examples, at step 38, the access node 12 may determine that the carrier wave has the same priority as the UL data and that the carrier wave waveform is the same as the UL data waveform. In such examples, the access node 12 may configure the UE 11 to reuse the UL data transmission for the carrier wave signal (e.g., may configure the carrier wave to piggyback on the UL transmission). In some such examples, reusing the UL transmission for the carrier wave transmission may depend on whether one or more carrier wave signal characteristics are found in (e.g., are common to) the UL signal components that are being reused (e.g., a transmit chain, a waveform, transmit power). Additionally, in some such examples, the access node 12 may reconfigure (and adjust) the UL transmit power at the UE 11 to a highest value (e.g., the maximum) between a first transmit power associated with (e.g., expected for) the carrier wave signal and a second transmit power associated with the scheduled UL data transmission. In other words, the UE 11 may concurrently perform the scheduled UL transmission but may change the UL transmit power so that the UL transmission can be reused for the carrier wave transmission. That is, if the carrier wave has the same priority as the UL data and the carrier waveform is the same as the UL waveform, the UE 11 may reuse the UL transmission to act as the carrier wave transmission and may increase (e.g., boost) the transmit power. In some examples, the UE 11 may use (e.g., reuse) the UL transmission (e.g., the uplink waveform, the uplink signal) as the carrier waveform after transmission of the UL data.

[0077] For some examples in which the UE 11 is in an RRC connected state and is scheduled for UL data transmission, the UE 11 may be configured by the access node 12 via a DL control channel (e.g., the second control information) to start a carrier wave transmission either during or after the UL data transmission. The carrier wave transmission configuration (e.g., the second control information) from the access node 12 may include one or more of the following: the carrier frequency for the UL carrier wave (e.g., the second carrier or a carrier offset with respect to the UL data transmission), the carrier wave waveform type (e.g., whether the carrier wave is single tone-sine wave, multi-tone-OFDM), the bandwidth for the carrier wave, the transmit power for the carrier wave, the duration ofthe carrier wave transmission, and / or the starting subframe of the carrier wave transmission (e.g., as an offset with respect to the starting subframe of the UL data transmission or the ending subframe of the UL transmission). As illustrated in step 38, the carrier wave transmission and UL transmission are configured in relation to their respective priorities, which may prevent conflicting actions at the UE 11 , as well as reduce a likelihood of unexpected access link (Uu) delays.

[0078] In some examples, at step 40, the second control information may indicate for the UE 11 to use a second carrier (e.g., a carrier frequency) that is non-overlapping in frequency with the first carrier. In other words, the UE 11 may be scheduled for an UL data transmission in a first carrier that does not coincide with (e.g., is a different carrier from) the second carrier configured for the carrier wave transmission. In such examples, the access node 12 may configure the UE 11 to perform UL carrier aggregation, in which one UL component carrier (e.g., a first component carrier (CC) configured for carrier aggregation at the UE) carries the UL data traffic and another component carrier (e.g., a second component carrier configured for carrier aggregation at the UE) carriers the carrier wave for the AIoT device. In other words, if the CW carrier does not coincide with the UL carrier, the access node 12 may schedule an UL carrier aggregation transmission at the UE 11, in which the first component carrier carriers the UL and the second component carrier carries the carrier wave. In such examples, the access node 12 may assign different transmit powers for the different component carriers, for example, to increase a likelihood that the UL data will be successfully received. That is, if the UE is scheduled for an UL transmission in a different carrier than the carrier wave, the access node 12 may schedule uplink carrier aggregation (e.g., using multiple component carriers) for the UL data and carrier wave transmissions with an uplink power distribution across the different component carriers.

[0079] In some examples, the UE 11 may be in an RRC inactive. In such examples, the UE 11 may be configured with a carrier wave transmission without transitioning to an RRC connected state. In such examples, the UE 11 may perform an UL SDT (small data transmission) transmission carrying the carrier wave signal.

[0080] In one example embodiment, the UE11 may be scheduled for DL data reception, and may also be scheduled for a carrier wave transmission in an UL carrier (e.g., the carrier wave is scheduled for transmission in an UL carrier). In such an example embodiment, the UE 11 may also be configured with a reception gap, during which the UE 11 may switch from a receive chain to a transmit chain (e.g., to the configured UL component carrier),generate the carrier wave signal (as per the configuration) and transmit the carrier wave signal in the UL component carrier, switch from the transmit chain back to the receive chain, and resume DL reception (e.g., if a subsequent DL data transmission is scheduled).

[0081] In another example embodiment, the UE 11 may be scheduled for UL transmission, and may also be scheduled for a carrier wave transmission in a DL carrier (e.g., the carrier wave is scheduled for transmission in a DL carrier). In such an example embodiment, the UE 11 may be configured with a transmission gap during which the UE 11 may switch components carriers (e.g., from the UL component carrier to the DL component carrier), generate the carrier wave, transmit the carrier wave in the DL component carrier, and switch back to the UL component carrier.

[0082] In yet another example embodiment, the UE may be scheduled for UL transmission with carrier aggregation between an UL data transmission and the carrier wave transmission. In such an example embodiment, the UE 11 may generate the UL data signal using a first base band chain, generate the carrier wave signal using a second (e.g., separate) base based chain, upconvert the UL data signal to a first component carrier and the carrier wave signal to a second component carrier, aggregate the first and second component carriers, apply the respective transmit power configured for the first component carrier and the second component carrier, and transmit the uplink data signal and the carrier wave signal using carrier aggregation.

[0083] Referring now to Figure 4, some operations performed in order to provide for carrier wave generation for the apparatus 20 (e.g., the UE 11), in one example embodiment, are depicted. As shown in Figure 4, the apparatus 20 is configured to receive a configuration (e.g., control information, such as via a downlink control channel) for a carrier wave transmission for one or more AIoT devices, where the apparatus 20 is outside of an AIoT topology. Additionally, the apparatus 20 is configured to perform the carrier wave transmission for the one or more AIoT devices using the received configuration, based on the RRC state of the UE, the duplexing capability of the UE, and / or scheduling of UL or DL transmission by the UE. In some examples, the apparatus may be configured to receive the configuration (e.g., associated with carrier wave transmission for one or more AIoT devices) while in an RRC connected state and after being scheduled for a DL data transmission. In such examples, using the received configuration, the apparatus 20 may be configured to perform the carrier wave transmission for the one or more AIoT devices before the scheduledDL transmission, after the scheduled DL transmission, or together with the scheduled DL transmission in FDD.

[0084] As shown in block 42 of Figure 4, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for reception of first control information from a network node, such as the access node 12. The first control information schedules reception of downlink data at the apparatus 20 over a first duration.

[0085] In some examples, as shown in block 44 of Figure 4, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for reception of second control information from the network node (e.g., the access node 12). The second control information is associated with transmission of a carrier wave to at least an AIoT device.

[0086] In some examples, the apparatus 20 may include means for providing for reception of the first control information before the second control information, after the second control information, or with the second control information (e.g., via a same downlink control message). In other words, the configuration of the DL data and the carrier wave may be done in any order, or at the same time, and how the apparatus 20 provides for the transmission of the DL data and the carrier wave (e.g., whether one after the other or concurrently, which order to transmit), depends on the configuration parameters.

[0087] As shown in block 46 of Figure 4, the apparatus 20 also include means (e.g., the processing circuitry 22, the communication interface 26) for providing for transmission of the carrier wave to the AIoT device over a second duration and in accordance with the second control information.

[0088] Referring now to Figure 5, some operations performed in order to provide for carrier wave generation for the apparatus 20 (e.g., the access node 12), in one example embodiment, are depicted. As shown in Figure 5, the apparatus 20 is configured to transmit a configuration (e.g., control information, such as via a downlink control channel) to a UE (e.g., carrier wave node) for a carrier wave transmission for one or more AIoT devices, where the carrier wave node is outside of an AIoT topology. In some examples, the apparatus 20 is configured to transmit the configuration (e.g., associated with carrier wave transmission for one or more AIoT devices) in accordance with an RRC connection between the carrier wave node and the apparatus 20, for example, after scheduling the carrier wave node for DL transmission. In such examples, the configuration may indicate for the carrier wave node to perform the carrier wave transmission for the one or more AIoT devices before the scheduledDL transmission, after the scheduled DL transmission, or together with the scheduled DL transmission in FDD.

[0089] As shown in block 50 of Figure 5, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for transmission of first control information to a carrier wave node, wherein the first control information schedules reception of downlink data over a first duration.

[0090] In some examples, as shown in block 52 of Figure 5, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for transmission of second control information to the carrier wave node, wherein the second control information schedules transmission of a carrier wave to at least an AIoT device over a second duration.

[0091] Referring now to Figure 6, some operations performed in order to provide for carrier wave generation for the apparatus 20 (e.g., the UE 11, a carrier wave node), in one example embodiment, are depicted. As shown in Figure 6, the apparatus 20 is configured to receive a configuration (e.g., control information, such as via a downlink control channel) for a carrier wave transmission for one or more AIoT devices, where the apparatus 20 is outside of an AIoT topology. Additionally, the apparatus 20 is configured to perform the carrier wave transmission for the one or more AIoT devices using the received configuration, based on the RRC state of the UE, the duplexing capability of the UE, and / or scheduling of UL or DL transmission by the UE. In some examples, the apparatus may be configured to receive the configuration (e.g., associated with carrier wave transmission for one or more AIoT devices) while in an RRC connected state and after being scheduled for an UL data transmission.Additionally, or alternatively, the apparatus 20 may be configured to receive the configuration via an RRC connection release message, for example, before transitioning from the RRC connected state to an RRC inactive state. In such examples, the configuration may indicate for the apparatus to transmit the carrier wave using an SDT. In some examples, the RRC connection release message (e.g., the configuration indicated via the connection release message), may include a resource allocation for the SDT associated with the carrier wave. Thus, using the received configuration, the apparatus 20 may be configured to perform the carrier wave transmission (e.g., the STD transmission carrying the carrier way) for the one or more AIoT devices while operating in an RRC inactive state (e.g., and using the resource allocation).

[0092] As shown in block 60 of Figure 6, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for reception, at a user equipment (UE), of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an AIoT device, and wherein the UE is outside of an AIoT topology that is associated with the network node and the AIoT device.

[0093] In some examples, as shown in block 62 of Figure 6, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a RRC state of the UE.

[0094] Referring now to Figure 7, some operations performed in order to provide for carrier wave generation for the apparatus 20 (e.g., the access node 12), in one example embodiment, are depicted. As shown in Figure 7, the apparatus 20 is configured to transmit a configuration (e.g., control information, such as via a downlink control channel) to a UE (e.g., the UE 11, a carrier wave node) for a carrier wave transmission for one or more AIoT devices, where the UE is outside of an AIoT topology. In some examples, the apparatus 20 is configured to transmit the configuration (e.g., associated with carrier wave transmission for one or more AIoT devices) in accordance with an RRC connection between the UE and the apparatus 20, for example, after scheduling the UE for UL transmission. In such examples, the configuration may indicate for the UE to perform the carrier wave transmission for the one or more AIoT devices before the scheduled DL transmission, after the scheduled DL transmission, or together with the scheduled DL transmission in FDD. In some other examples, the apparatus may transmit the configuration via an RRC connection release message. In such an example, the configuration may include a resource allocation for the UE to transmit the carrier wave via an STD transmission while operating in an RRC inactive state.

[0095] As shown in block 70 of Figure 7, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing for transmission of first control information to a user equipment (UE), wherein the first control information schedules transmission of uplink data at the UE (e.g., the UE 11, a carrier wave node) via a first carrier.

[0096] In some examples, as shown in block 72 of Figure 7, the apparatus 20 includes means (e.g., the processing circuitry 22, the communication interface 26), for providing fortransmission of second control information to the UE based at least in part on a radio resource control (RRC) state of the UE, wherein the second control information is associated with transmission of a carrier wave to at least an AIoT device and is based at least in part on the UE being outside of an AIoT topology that is associated with a network node and the AIoT device.

[0097] As described above, methods, apparatuses, and computer program products are disclosed to provide for improved carrier wave generation for AIoT devices. In this regard, a method, apparatus, and computer program product are configured to provide for the reception, by an AIoT device, of an activation signal that includes a test sequence, and provide for the transmission, by the AIoT device, of a backscattered signal that includes backscattering of the activation signal. By providing for the reception of the activation signal with the test sequence and the transmission of the corresponding backscattered signal, the method, apparatus, and computer program product may provide for improved carrier wave generation for the AIoT device. In some aspects, improved carrier wave generation may lead to data being communicated with the AIoT device more effectively and with reduced interference, such that the data may be interpreted (e.g., decoded), in a more accurate manner. Moreover, by providing for improved carrier wave generation for the AIoT device, data may be transmitted to (or received from) the AIoT device, over wider ranges.

[0098] Figures 4-7 illustrate flowcharts depicting methods according to an example embodiment of the present disclosure. It will be understood that each block of the flowcharts and combination of blocks in the flowcharts may be implemented by various means, such as hardware, firmware, processor, circuitry, and / or other communication devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory 24 of an apparatus 20 employing an embodiment of the present disclosure and executed by a processor 22. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (for example, hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readablememory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer- implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks. Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions. Many modifications and other embodiments of the disclosure set forth herein will come to mind to one skilled in the art to which the disclosure pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe some example embodiments in the context of some example combinations of elements and / or functions, it should be appreciated that different combinations of elements and / or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense and not for purposes of limitation.

Claims

What is claimed is:

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: provide for reception of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and provide for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a radio resource control (RRC) state of the apparatus.

2. An apparatus according to Claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for reception of first control information from the network node, wherein the first control information schedules transmission of uplink data via a first carrier, and wherein the control information schedules transmission of the carrier wave via the first carrier or a second carrier based at least in part on the apparatus operating in an RRC connected state.

3. An apparatus according to Claim 2, wherein, to provide for transmission of the carrier wave, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: after transmission of the uplink data via the first carrier in accordance with the first control information, provide for transmission of the carrier wave via the first carrier in accordance with the control information.

4. An apparatus according to Claim 3, wherein providing for transmission of the carrier wave after transmission of the uplink data is based at least in part on a first priority associated with the carrier wave being lower than a second priority associated with the uplink data.

5. An apparatus according to Claim 2, wherein, to provide for transmission of the carrier wave, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: concurrently with the transmission of the uplink data via the first carrier, provide for transmission of the carrier wave via the second carrier in accordance with the control information, wherein the first carrier and the second carrier comprise component carriers configured at the apparatus for carrier aggregation.

6. An apparatus according to Claim 5, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for reception of a first indication of a first transmit power associated with the first carrier, wherein providing for transmission of the uplink data via the first carrier is in accordance with the first transmit power; and provide for reception of a second indication of a second transmit power associated with the second carrier, wherein providing for transmission of the carrier wave via the second carrier is in accordance with the second transmit power.

7. An apparatus according to Claim 6, wherein: the first transmit power satisfies a first threshold transmit power associated with transmission of the uplink data; and the second transmit power satisfies a second threshold transmit power associated with transmission of the carrier wave.

8. An apparatus according to Claim 2, wherein, to provide for transmission of the carrier wave, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: after the transmission of the uplink data via the first carrier in accordance with a first transmit power, provide for transmission of the carrier wave via the first carrier in accordance with the first transmit power based at least in part on the first transmit power satisfying a threshold transmit power associated with transmission of carrier waves for AIoT devices.

9. An apparatus according to Claim 8, wherein providing for transmission of the carrier wave via the first carrier is based at least in part on a first priority associated with thecarrier wave being the same as a second priority associated with the uplink data and is based at least in part on a first waveform associated with the carrier wave being the same as a second waveform associated with the uplink data.

10. An apparatus according to Claim 8, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for reception of an indication to adjust a transmit power at the apparatus from a second transmit power to the first transmit power, wherein providing for transmission of the uplink data in accordance with the first transmit power is based at least in part on the indication.

11. An apparatus according to Claim 8, wherein the first transmit power corresponds to a highest transmit power among the following: a second transmit power associated with the carrier wave and a third transmit power associated with the uplink data.

12. An apparatus according to Claim 2, wherein, to provide for transmission of the carrier wave, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: concurrently provide for transmission of the following: the uplink data over a first portion of frequency-domain resources associated with the first carrier, and the carrier wave via a second portion of the frequency-domain resources associated with the first carrier.

13. An apparatus according to Claim 12, wherein providing for transmission of the carrier wave via the second portion of the frequency-domain resources is based at least in part on puncturing of the second portion of the frequency-domain resources.

14. An apparatus according to Claim 12, wherein providing for transmission of the carrier wave via the second portion of the frequency-domain resources is based at least in part on the following: a first priority associated with the carrier wave being the same as a second priority associated with the uplink data, and a first waveform associated with the carrier wave being different from a second waveform associated with the uplink data.

15. An apparatus according to Claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for reception of an RRC connection release message from the network node while operating in an RRC connected state, wherein the RRC connection release message is indicative of a resource allocation for a small data transmission associated with the carrier wave; and provide for a transition from the RRC connected state to an RRC inactive state based at least in part on the RRC connection release message, wherein, to provide for transmission of the carrier wave, the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: provide for the small data transmission in accordance with the resource allocation while operating in the RRC inactive state, wherein the small data transmission comprises the carrier wave based at least in part on the apparatus operating in the RRC inactive state.

16. An apparatus according to Claim 1, wherein the control information is indicative of at least one of the following: a frequency associated with the carrier wave, a waveform type associated with the carrier wave, a bandwidth associated with the carrier wave, a transmit power associated with transmission of the carrier wave, a duration associated with transmission of the carrier wave, or a subframe index corresponding to a starting subframe for transmission of the carrier wave.

17. An apparatus according to Claim 1, wherein the control information is based at least in part on at least one of the following: a priority associated with the carrier wave, one or more traffic constraints associated with the apparatus, or one or more transmit power constraints associated with the apparatus.

18. An apparatus according to Claim 1, wherein the apparatus comprises a user equipment (UE), and wherein the UE is outside of an AIoT topology that is associated with the network node and the AIoT device.

19. An apparatus comprising:at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: provide for transmission of first control information to a carrier wave node, wherein the first control information schedules transmission of uplink data at the carrier wave node via a first carrier; and provide for transmission of second control information to the carrier wave node based at least in part on a radio resource control (RRC) state of the carrier wave node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device.

20. An apparatus according to Claim 19, wherein the second control information schedules transmission of the carrier wave using the first carrier or a second carrier based at least in part on an RRC connection between the carrier wave node and the apparatus.

21. An apparatus according to Claim 19, wherein the second control information is indicative of at least one of the following: a frequency associated with the carrier wave, a waveform type associated with the carrier wave, a bandwidth associated with the carrier wave, a transmit power associated with the transmission of the carrier wave, a duration associated with the transmission of the carrier wave, or a subframe index corresponding to a starting subframe for transmission of the carrier wave.

22. An apparatus according to Claim 19, wherein the second control information is based at least in part on at least one of the following: a priority associated with the carrier wave, one or more traffic constraints associated with the carrier wave node, or one or more transmit power constraints associated with the carrier wave node.

23. An apparatus according to claim 19, wherein the carrier wave node comprises a user equipment (UE).

24. A method comprising:providing for reception of control information from a network node, wherein the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device; and providing for transmission of the carrier wave to the AIoT device in accordance with the control information and based at least in part on a radio resource control (RRC) state of a carrier wave node.

25. A method comprising: providing for transmission of first control information to a carrier wave node, wherein the first control information schedules transmission of uplink data at the carrier wave node via a first carrier; and providing for transmission of second control information to the carrier wave node based at least in part on a radio resource control (RRC) state of the carrier wave node, wherein the second control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device.

Images