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

Abstract

Methods, apparatuses, and computer program products for providing carrier wave generation for ambient internet of things (AIoT) devices. In the context of one method, the method includes providing reception of control information from a network node, where the control information is associated with transmission of a carrier wave to at least an ambient internet of things (AIoT) device, and providing 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 carrier wave node.

Description

Cross-reference to related applications

[0001] This application claims priority to FI application No. 20245389, filed on April 3, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The example embodiments generally relate to techniques for carrier wave generation for Ambient Internet of Things (AIoT) devices, and more specifically to techniques for configuring carrier wave generator entities located outside the AIoT topology. Background Technology

[0003] Some endpoints (such as AIoT devices) may harvest energy for various operations, such as those performed according to active or passive modes. In some cases, endpoints may use energy harvested from radio frequency waves or other forms of energy harvested in various deployment scenarios. Endpoints may operate at relatively low (e.g., ultra-low) power, for example, from 1 microwatt to hundreds of microwatts. For example, an endpoint may include one or more components (e.g., an energy harvester) configured to harvest energy from radio frequency waves, and the output power of the energy harvester may range from one microwatt to tens of microwatts. In another case, an endpoint may include one or more other components (e.g., a solar panel) configured to harvest energy from solar radiation (e.g., ultraviolet (UV), visible light, infrared light), and the output power of the solar panel may be less than milliwatts. In some cases, endpoints configured to harvest energy (e.g., energy harvesting devices) may operate in an active mode, in which the endpoint can use the harvested energy and circuitry (e.g., active circuitry) to transmit signaling. In some other cases, endpoints configured to harvest energy may operate in a passive mode (e.g., tags, devices lacking active transmission circuitry systems), where the endpoint can use backscattering for communication (e.g., transmitting data). Summary of the Invention

[0004] Methods, apparatuses, and computer program products for providing improved carrier wave generation for AIoT devices are disclosed. In this regard, at least one method, apparatus, and computer program product provides for configuring a carrier wave node (e.g., a user equipment (UE)) outside the AIoT topology to generate a carrier wave signal and transmit it to one or more AIoT devices. By providing the configuration of a carrier wave node to generate a carrier wave signal and transmit it to one or more AIoT devices, the method, apparatus, and computer program product can reduce scheduling conflicts at the carrier wave node, such as between scheduled data transmission (or reception) and scheduled carrier wave transmission. In some aspects, by reducing scheduling conflicts, the method, apparatus, and computer program product can provide more efficient communication between the carrier wave node and 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), the at least one memory and the computer program code being configured together with the at least one processor such that the apparatus at least: provides reception of first control information from a network node, wherein the first control information schedules reception of downlink data at the apparatus during a first duration; provides reception of second control information from the network node, wherein the second control information is associated with transmission of carrier waves to at least an Ambient Internet of Things (AIoT) device; and provides transmission of carrier waves to the AIoT device according to the second control information during a second duration.

[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), the at least one memory and the computer program code being configured together with the at least one processor such that the apparatus at least: provides transmission of first control information to a carrier wave node, wherein the first control information schedules reception of downlink data during a first duration; and provides transmission of second control information to a carrier wave node, wherein the second control information schedules transmission of carrier waves to at least an Ambient Internet of Things (AIoT) device during a second duration.

[0007] In at least one example embodiment, a method is provided, the method comprising: providing reception of first control information from a network node, wherein the first control information is scheduled for reception of downlink data at a carrier wave node within a first duration; providing reception of second control information from the network node, wherein the second control information is associated with transmission of carrier waves to at least an Ambient Internet of Things (AIoT) device; and providing transmission of carrier waves to the AIoT device according to the second control information within a second duration.

[0008] In at least one example embodiment, a method is provided, the method comprising: providing first control information to a carrier wave node, wherein the first control information schedules the reception of downlink data during a first duration; and providing second control information to a carrier wave node, wherein the second control information schedules the transmission of carrier waves to at least an Ambient Internet of Things (AIoT) device during 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 includes computer instructions that, when executed by a device, cause the device to: provide reception of first control information from a network node, wherein the first control information schedules reception of downlink data at the device during a first duration; provide 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 transmission of a carrier wave to the AIoT device according to the second control information during a second duration.

[0010] In at least one example embodiment, a non-transitory computer-readable storage medium is provided. The non-transitory computer-readable storage medium includes computer instructions that, when executed by a device, cause the device to: provide transmission of first control information to a carrier wave node, wherein the first control information schedules the reception of downlink data during a first duration; and provide transmission of second control information to the carrier wave node, wherein the second control information schedules the transmission of carrier waves to at least an Ambient Internet of Things (AIoT) device during a second duration.

[0011] In at least one example embodiment, an apparatus is provided comprising components for: providing reception of first control information from a network node, wherein the first control information schedules reception of downlink data at the apparatus during a first duration; providing 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 transmission of a carrier wave to the AIoT device according to the second control information during a second duration.

[0012] In at least one example embodiment, an apparatus is provided comprising components for: providing transmission of first control information to a carrier wave node, wherein the first control information schedules the reception of downlink data during a first duration; and providing transmission of second control information to the carrier wave node, wherein the second control information schedules the transmission of the carrier wave to at least an Ambient Internet of Things (AIoT) device during 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), the at least one memory and the computer program code being configured together with the at least one processor such that the apparatus at least: provides receiving control information from a network node, wherein the control information is associated with transmission of carrier waves to at least an Ambient Internet of Things (AIoT) device; and provides carrier wave transmission to the AIoT device based on the control information at least in part based on the radio resource control (RRC) status 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), the at least one memory and the computer program code being configured together with the at least one processor such that the apparatus at least: provides transmission of first control information to a carrier wave node, wherein the first control information is scheduled for transmission of uplink data via a first carrier at the carrier wave node; and provides transmission of second control information to the carrier wave node, at least in part based on the radio resource control (RRC) status of the carrier wave node, wherein the second control information is associated with transmission of the carrier wave to at least an Ambient Internet of Things (AIoT) device.

[0015] In at least one example embodiment, a method is provided that includes: providing control information received from a network node, wherein the control information is associated with a carrier wave transmission to at least an Ambient Internet of Things (AIoT) device; and providing the carrier wave transmission to the AIoT device based on the control information at least in part on the radio resource control (RRC) status of the carrier wave node.

[0016] In at least one example embodiment, a method is provided comprising: providing transmission of first control information to a carrier wave node, wherein the first control information is scheduled for transmission of uplink data via a first carrier at the carrier wave node; and providing transmission of second control information to the carrier wave node, at least in part based on the radio resource control (RRC) status of the carrier wave node, wherein the second control information is associated with transmission of the 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 includes computer instructions that, when executed by a device, cause the device to: provide the reception of control information from a network node, wherein the control information is associated with the transmission of a carrier wave to at least an Ambient Internet of Things (AIoT) device; and provide the transmission of the carrier wave to the AIoT device based on the control information, at least in part based on the device's Radio Resource Control (RRC) status.

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

[0019] In at least one example embodiment, an apparatus is provided comprising components for: providing 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 transmission of the carrier wave to the AIoT device based on the control information at least in part on the radio resource control (RRC) status of the apparatus.

[0020] In at least one example embodiment, an apparatus is provided comprising components for: providing transmission of first control information to a carrier wave node, wherein the first control information is scheduled for transmission of uplink data via a first carrier at the carrier wave node; and providing transmission of second control information to the carrier wave node, at least in part based on the radio resource control (RRC) status of the carrier wave node, wherein the second control information is associated with transmission of the carrier wave to at least an Ambient Internet of Things (AIoT) device. Attached Figure Description

[0021] After a general description of some exemplary embodiments of this disclosure, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale. In the drawings:

[0022] Figure 1 It can be deployed in it Figure 2 A block diagram of an example communication system for the device;

[0023] Figure 2 This is a block diagram of an apparatus that can be specifically configured according to exemplary embodiments of the present disclosure;

[0024] Figure 3 The illustration is based on an example embodiment in, for example, Figure 1 The process flow within a communication system that performs operations to provide carrier wave generation;

[0025] Figure 4 The illustration is based on an example embodiment, such as by Figure 2 A flowchart illustrating the operation of an example embodiment of the device to provide carrier wave generation;

[0026] Figure 5 The illustration is based on an example embodiment, such as by Figure 2 A flowchart illustrating the operation of an example embodiment of the device to provide carrier wave generation;

[0027] Figure 6 The illustration is based on an example embodiment, such as by Figure 2 A flowchart illustrating the operation of an example embodiment of the device to provide carrier wave generation;

[0028] Figure 7 The illustration is based on an example embodiment, such as by Figure 2 A flowchart illustrating the operation of an example embodiment of the device to provide carrier wave generation; Detailed Implementation

[0029] Some embodiments of this disclosure will now be described more fully with reference to the accompanying drawings, which illustrate some, but not all, embodiments of this disclosure. In fact, various embodiments of this disclosure may be embodied in many different forms and should not be construed as limited to the embodiments described herein; rather, these embodiments are provided so that this disclosure will meet applicable legal requirements. The same reference numerals consistently refer to the same elements. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data that can be transmitted, received, and / or stored according to embodiments of this disclosure. Therefore, the use of any such terms should not be considered as limiting the spirit and scope of the embodiments of this disclosure.

[0030] Furthermore, as used herein, the term "circuit system" means (a) a purely hardware circuit implementation (e.g., an implementation in an analog circuit system and / or a digital circuit system); (b) a combination of circuitry and (multiple) computer program products, including software and / or firmware instructions stored on one or more computer-readable storage media that work together to cause a device to perform one or more functions described herein; and (c) circuitry that operates using software or firmware even if the software or firmware is not physically present, such as, for example, (multiple) microprocessors or portions thereof. This definition of "circuit system" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit system" also covers implementations comprising one or more processors and / or portions thereof, along with accompanying software and / or firmware. As yet another example, for instance, the term "circuit system" as used herein also includes, for example, baseband integrated circuits or application processor integrated circuits for mobile phones, or similar integrated circuits in servers, cellular network equipment, other network equipment (such as core network equipment), field-programmable gate arrays, and / or other computing devices.

[0031] like Figure 1 As illustrated in the example, the communication system may include one or more Ambient Internet of Things (AIoT) devices, such as AIoT device 19. In some embodiments, AIoT device 19 may be (or otherwise include) a radio frequency identification (RFID) device. RFID devices may also be referred to herein as RFID tags, or more simply as tags. Some AIoT devices (such as RFID tags) may be used in conjunction with one or more backscattering techniques (e.g., may operate according to these techniques). In other words, some AIoT devices may communicate with one or more other devices (e.g., UE 10, UE 11, access node 12) via backscattering. AIoT devices may be deployed in a variety of vertical industries, including but not limited to logistics, manufacturing, transportation, and energy. Therefore, deploying AIoT devices (e.g., passive devices) in both public and private networks can provide one or more benefits to communication systems (e.g., the 5G ecosystem). In some embodiments, AIoT devices may be devices with relatively low (e.g., ultra-low) complexity and / or devices with relatively small terminal size or form factor (e.g., thickness on the order of millimeters). Additionally or alternatively, AIoT devices may be associated with relatively low maintenance (e.g., may be maintenance-free) and may have a relatively long lifespan. AIoT devices can include battery-free terminals or terminals with limited (e.g., limited) energy storage capabilities. For example, AIoT devices can store energy via capacitors.

[0032] like Figure 1 As shown in the examples, AIoT device 19 can operate according to one or more topologies. In some examples, AIoT device 19 can operate according to a first topology in which AIoT device 19 can communicate directly with an access node (e.g., a base station). That is, AIoT device 19 can communicate directly (one-way or two-way) with one or more base stations according to the first topology. Communication between the access node and AIoT device 19 can include AIoT data and / or signaling. For example, AIoT device 19 can receive signals from the access node and can use these signals to transmit information (e.g., data) to the access node. In some examples, AIoT device 19 can transmit data via modulation and backscattering of a carrier wave signal. For example, AIoT device 19 can modulate data onto a backscattered signal. The first topology can include a first access node sending data to the AIoT device and a second access node receiving data from the AIoT device.

[0033] In some other examples, such as Figure 1As shown, AIoT device 19 can operate according to a second topology in which AIoT device 19 can communicate with access node 12 (e.g., a base station) via one or more intermediate nodes. In other words, intermediate nodes can transmit information between access node 12 and AIoT device 19. Intermediate nodes may also be referred to herein as auxiliary nodes. In some examples, access node 12 (e.g., a base station) and / or intermediate nodes (e.g., UE 10 or UE 11, which may also be referred to as auxiliary nodes) can be multiple access nodes or multiple intermediate nodes, respectively. Intermediate nodes can be relays, IAB nodes, UEs, or repeaters (e.g., relays), and other examples of devices that can be used as intermediate nodes. The second topology can support monopolar and bipolar communication. In some examples of monopolar communication, AIoT device 19 can communicate bidirectionally with a single intermediate node (e.g., UE 10), and the intermediate node can communicate with access node 12 (e.g., directly and bidirectionally). In some examples, intermediate nodes may be physically located between AIoT device 19 and access node 12, thereby extending the distance over which access node 12 can communicate with AIoT device 19 (relative to communication according to the first topology). According to a monopolar mode, intermediate nodes may transmit (e.g., relay, forward) AIoT data and / or signaling between access node 12 and AIoT device 19. Alternatively, auxiliary node 12 may communicate with AIoT device 19 according to a bipolar mode. For example, access node 12 may communicate with AIoT device 19 using a bipolar communication mode. In some aspects, one or more links in one or more topologies may be bidirectional or unidirectional. For example, the link between AIoT device 19 and access node 12 may be bidirectional or unidirectional. Alternatively, the link between AIoT device 19 and intermediate nodes (e.g., UE 10 or UE 11) may be bidirectional or unidirectional. In some aspects, the link between evaluation node 12 and intermediate nodes may be bidirectional or unidirectional.

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

[0035] In some examples, such as those where AIoT device 19 cannot generate (or amplify) a backscattered signal, access node 12 can select an entity (e.g., a UE) to generate a carrier wave for AIoT device 19. In some such examples, access node 12 can select an entity (e.g., a carrier wave generator entity) based on its position relative to AIoT device 19. In other words, access node 12 can select an entity relatively close (e.g., as close as possible) to AIoT device 19 such that the entity can transmit a carrier wave at an appropriate (e.g., sufficiently high) power and a suitable carrier frequency, so that the information carried by the backscattered carrier wave (e.g., an AIoT response) can be successfully decoded by a reader (e.g., access node 12, another dedicated reader device) within the coverage area of ​​AIoT device 19. Therefore, for an AIoT session with AIoT device 19, access node 12 can select the carrier wave generator entity of AIoT device 19 based on the relative proximity of the carrier wave generator entity to AIoT device 19. In some examples, selecting a carrier wave generator entity based on its relative proximity to the AIoT device 19 can increase the likelihood of a successful AIoT session with the AIoT device 19.

[0036] However, in some such examples, the selected carrier wave generator entity may be located outside one or more AIoT topologies. For example, such as Figure 1 As shown, access node 12 can select UE 11 as the carrier wave generator entity for AIoT device 19. When the selected carrier wave generator entity is located outside one or more AIoT topologies (e.g., when the selected carrier wave generator entity has not yet been established or otherwise configured for an AIoT session), the selected carrier wave generator entity is considered not part of the AIoT session and therefore not configured (e.g., pre-configured) to assist the AIoT session of the AIoT device (e.g., any target AIoT device). In some such examples, for example, when the entity is operating in a Radio Resource Control (RRC) inactive state or actively participating in other data communications (e.g., UL / DL services) or location services, there may be ambiguity regarding how the selected carrier wave generator entity (e.g., for NR UEs near the AIoT device) is triggered to transmit carrier wave signals. In other words, when the carrier wave generator entity is located outside the AIoT network topology, it has not yet been pre-configured (e.g., not yet configured) to support the AIoT session of the target AIoT device, and therefore may not know how it was triggered to send carrier wave signals (e.g., when it actively participates in other data). This ambiguity may degrade the performance of AIoT backscatter, reduce the reliability of communication between AIoT device 19 and 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, based on one or more techniques for carrier wave generation for AIoT devices, as described herein, access node 12 can configure UE 11 (e.g., an NR UE outside the first and second topologies) to transmit carrier wave signals for one or more AIoT devices (e.g., AIoT device 19). For example, such techniques can provide carrier wave scheduling for AIoT transmissions at the UE (e.g., UE 11), as well as uplink and / or downlink transmission scheduling at the UE. In some examples, carrier wave scheduling may differ from activation signal scheduling. Furthermore, in some examples, carrier wave scheduling for UEs located outside one or more AIoT network topologies may differ from carrier wave scheduling for UEs located within one or more AIoT network topologies. For example, scheduling for UEs located outside one or more AIoT network topologies (e.g., the first topology, the second topology) may be based on priority.

[0038] For example, access node 12 can schedule UE 11 for downlink (DL) data transmission. In some examples, access node 12 and / or UE 11 can determine that the carrier wave has a lower priority than the DL data. In such examples, UE 11 can be configured (e.g., access node 12 can schedule UE 11 to) delay carrier wave transmission until DL reception is complete. In some other examples, access node 12 and / or UE 11 can determine that the carrier wave has the same priority as the DL data. In such examples, based on UE duplex capability, UE 11 can be configured (e.g., access node 12 can schedule UE 11 to) concurrently transmit the carrier wave and DL data. For example, carrier wave transmission can be frequency division duplexed (FDD) together with DL data reception (e.g., depending on UE duplex capability). In some other examples, access node 12 and / or UE 11 can determine that the carrier wave has a higher priority than the DL data. In such an example, UE 11 can be configured (e.g., access node 12 can schedule UE 11 to) delay DL data transmission, such that carrier wave transmission precedes DL data transmission.

[0039] Alternatively or concurrently, access node 12 may schedule uplink (UL) data transmission for UE 11. In some examples, a first carrier configured (e.g., scheduled) for UL data transmission and a second carrier configured (e.g., scheduled) for carrier wave transmission may overlap in frequency (e.g., they 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. Furthermore, in some such examples, access node 12 and / or UE 11 may determine that the carrier wave has a lower priority than the UL data. In such examples, UE 11 may be configured (e.g., access node 12 may schedule UE 11 to) delay the carrier wave transmission until the UL transmission is complete. In some other examples, access node 12 and / or 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, UE 11 may be configured (e.g., access node 12 may configure UE 11 to) interleave the carrier wave transmission with the UL data transmission. For example, UE 11 can be configured (e.g., access node 12 can configure UE 11 to) punch UL data to provide available resources for carrier transmission. Alternatively, in some examples, if the carrier wave and UL data transmission have the same waveform, UE 11 can be configured (e.g., access node 12 can schedule UE 11 to) carry the carrier wave transmission over the UL data transmission. In such examples, the network (e.g., access node 12) can adjust the UL transmission power at UE 11. For example, access node 12 can send an instruction to UE 11 to adjust the transmission power (also referred to herein as transmit power) at UE 11 for UL data transmission to a transmit power suitable for carrier wave transmission. In some examples, access node 12 can instruct UE 11 to adjust the transmit power to the highest value (e.g., the maximum value) between the transmit power associated with the carrier wave signal (e.g., a threshold transmit power of the carrier wave signal, the expected transmit power of the carrier wave signal) or the transmit power associated with the scheduled UL data transmission.

[0040] In some examples, such as those where the first carrier used for UL data transmission and the second carrier used for carrier wave transmission do not overlap (e.g., are different carriers), access node 12 can schedule UL carrier aggregation transmission at UE 11, where the first component carrier (CC) carries UL data and the second CC carries carrier waves. In some such examples, access node 12 can allocate multiple (e.g., different) transmit powers to multiple (e.g., different) CCs. For example, access node 12 can allocate different transmit powers to the first CC and the second CC to increase the likelihood that uplink data can be successfully received (e.g., and decoded).

[0041] Therefore, as described herein, one or more technologies for carrier wave generation for AIoT devices can provide a UE configured to transmit carrier wave signals for one or more AIoT devices outside of one or more AIoT topologies. In some examples, such technologies can provide enhanced coverage for AIoT device 19 (e.g., for backscattered RFID tags and other types of AIoT devices in a communication system) and more efficient communication at the carrier wave generating entity (e.g., UE 11), which can improve the efficiency of IoT-type data transmission (e.g., performed by AIoT device 19).

[0042] Figure 1 The communication system can also communicate with other networks, such as the public switched telephone network or the Internet, or utilize services provided by them. The communication network can also support the use of cloud services; for example, at least part of the core network operation can function as a cloud service (this is in...). Figure 1 The communication system can also include a central control entity that provides facilities for different operators' networks, such as to cooperate on spectrum sharing. 5G can also utilize satellite communications to enhance or supplement the coverage of 5G services, for example by providing backhaul. Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or passengers on vehicles, or ensuring the service availability of critical communications and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems or low Earth orbit (LEO) satellite systems. Each satellite in a mega-constellation can cover several satellite network entities that create ground cells. Ground cells can be created by ground relay nodes 22 or by gNBs located on the ground or on satellites. The depicted system is in which deployments can be made. Figure 1 This is an example of a radio access system portion of a communication system, and in practice, the system may include multiple NodeBs, user equipment may access multiple radio cells, and the system may also include other devices such as physical layer relay nodes or other network elements. At least one NodeB may be a home nodeB. Furthermore, various different types of radio cells and multiple radio cells can be provided within the geographical area of ​​the radio communication system. Radio cells can be macrocells (or umbrella cells), which are large and small cells, typically with diameters up to tens of kilometers, or smaller cells such as microcells, femtocells, or picocells. Figure 1A NodeB can provide any type of these cells. Cellular radio systems can be implemented as multi-layered networks comprising several types of cells. Typically, in a multi-layered network, one access node provides one or more types of cells, and therefore multiple NodeBs can be used to provide this network structure.

[0043] like Figure 1 As shown, for example, a communication system may include multiple devices configured to communicate via appropriate channels. In this regard, a user equipment may include a transmitter configured to communicate with a receiver at a base station. Conversely, a base station may include a receiver and a transmitter for communicating with a receiver at a user equipment. For example, the communication system may be deployed within a radio access architecture based on Advanced Long Term Evolution (LTE-A) or New Radio (NR, 5G). However, the system may be deployed in other applications, including in other communication networks such as Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN or E-UTRAN), Wireless Local Area Network (WLAN or WiFi), Global Microwave Access Interoperability (WiMAX), Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof. In this regard, Figure 1 An example of a simplified system architecture is depicted, showing some elements and functional entities (e.g., logical units) whose implementations may differ from those shown. Figure 1 The connections shown are logical connections, and their corresponding physical connections may differ. It will be apparent to those skilled in the art that the system may include, except for... Figure 1 Other functions and structures besides those shown. Figure 1 In the radio access architecture, user equipment 20 and 21 are configured to wirelessly connect to an access node 22 (such as a NodeB) providing the cell on one or more communication channels within the cell. As used herein, an access node may also be referred to as a network node. The physical link from the user equipment to the NodeB is referred to as an uplink or reverse link, while the physical link from the NodeB to the user equipment is referred to as a downlink or forward link. It should be understood that a NodeB, or its functionality, can be implemented using any entity suitable for this purpose, such as a node, host, server, or access point (AP).

[0044] The communication system may include more than one NodeB, in which case the NodeBs may also be configured to communicate with each other via wired or wireless links designed for various purposes. For example, such links may be used for signaling purposes. A NodeB is a computing device configured to control the radio resources of the communication system to which the NodeB may be coupled. A NodeB may also be referred to as a base station, access point, or any other type of interface device, including a relay station capable of operating in a wired or wireless environment. A NodeB includes or is coupled to a transceiver. A connection is provided from the NodeB's transceiver to an antenna element that establishes a bidirectional radio link to the user equipment. Therefore, the transceivers of the NodeB and the user equipment may include transmitters and receivers configured to communicate via a channel using trainable parameters of the transmitters and receivers that can be reconfigured according to an example embodiment. The antenna element may include multiple antennas or antenna elements. The NodeB is also 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, which routes and forwards user data packets), a Packet Data Network Gateway (P-GW) that provides connectivity between the User Equipment (UE) and external packet data networks, or a Mobility Management Entity (MME), etc. A User Equipment (also known as a User Equipment (UE), User Terminal, Terminal Equipment, etc.) illustrates a type of device to which resources on the air interface are allocated and assigned, and therefore any features of the User Equipment described herein can be implemented using a corresponding device, such as a relay node. An example of such a relay node is a Layer 3 relay (self-backhaul relay) directed towards a base station.

[0045] User equipment (UE) generally refers to portable computing devices, including wireless mobile communication devices with or without a Subscriber Identity Module (SIM), including but not limited to: mobile stations (mobile phones), smartphones, personal digital assistants (PDAs), cell phones, devices using wireless modems (such as alarm or measuring devices), laptops and / or touchscreen computers, tablets, game consoles, and multimedia devices. It should be understood that UE can also be a virtually exclusive uplink device (e.g., an uplink-only device), an example of which is a camera or camcorder that loads images or video clips onto a network. UE can also be a device capable of operating in an Internet of Things (IoT) network, in which case objects can transmit data over the network without human-to-human or human-to-computer interaction. UE (or, in some embodiments, a Layer 3 relay node) is configured to perform one or more UE functions. UE can also be referred to as a subscriber unit, mobile station, remote terminal, access terminal, user terminal, or user equipment (UE), to name just a few.

[0046] The various techniques described in this article can also be applied to cyber-physical systems (CPS) (systems of collaborative computing elements that control physical entities). CPS enables the realization and utilization of a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects in different locations. Mobile cyber-physical systems are a subcategory of cyber-physical systems where the physical systems under discussion have inherent mobility. Examples of mobile physical systems include mobile robots and electronic products transported by humans or animals.

[0047] Although these devices have been described as a single entity, different units, processors, and / or memory units can be implemented. Figure 1 (Not all are shown). Furthermore, the number of receive and / or transmit antennas for user equipment can vary naturally depending on current implementation. 5G enables the use of multiple-input multiple-output (MIMO) antennas, far more base stations or nodes than LTE (the so-called small cell concept), including macro sites operating in cooperation with smaller sites, and various radio technologies depending on service requirements, use cases, and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications, including vehicle safety, different sensors, and real-time control. 5G is expected to have multiple radio interfaces, namely sub-6GHz, cmWave, and mmWave, and can also be integrated with existing legacy radio access technologies such as LTE. At least in the early stages, integration with LTE can be implemented as a system where macro coverage is provided by LTE, and 5G radio interface access is obtained from small cells via aggregation to LTE. In other words, 5G plans support both inter-RAT (Radio Interface Accessibility, such as LTE-5G) and inter-RI (Radio Interface Accessibility, such as sub-6GHz-cmWave, sub-6GHz-cmWave, mmWave) interoperability. One concept considered for use in 5G networks is network slicing, where multiple independent and dedicated virtual subnets (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0048] The current architecture in LTE networks is entirely distributed across radios and entirely centralized in the core network. Low-latency applications and services in 5G require content to be closer to the radio, leading to local bursts and multiple access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach leverages resources that may not have continuous network connectivity, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for hosting applications and services. It also enables the storage and processing of content near cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networks and processing (which can also be categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, cloudlets, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (IoT) (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 can also communicate with other networks (such as the public switched telephone network or the Internet16) or utilize services provided by them. The communication network can also support the use of cloud services; for example, at least a portion of the core network operation can be performed as a cloud service (this is in...). Figure 1 (Described by “Cloud” 18). The communication system may also include a central control entity that provides facilities for cooperation between different operators’ networks, such as in spectrum sharing.

[0050] Edge cloud can be introduced into the radio access network (RAN) by leveraging Network Functions Virtualization (NVF) and Software-Defined Networking (SDN). Using edge cloud allows access node operations to be performed, at least partially, in servers, hosts, or nodes operatively coupled to remote radio heads or base stations, including radio components. Node operations can also be distributed across multiple servers, nodes, or hosts. The application of cloud RAN architecture enables real-time RAN functions to be executed on the RAN side (in the distributed unit DU 12), while non-real-time functions can be executed in a centralized manner (in the centralized unit CU 14).

[0051] It should also be understood that the workload distribution between core network operations and base station operations may differ from, or even not exist, in LTE. Other technological advancements that can be utilized include big data and all-IP, which can transform how networks are built and managed. 5G (or New Radio) networks are designed to support multi-layered architectures, where MEC servers can be placed between the core and base stations or nodeBs (gNBs). It should be understood that MEC can also be applied to 4G networks.

[0052] 5G can also leverage satellite communications to enhance or supplement the coverage of 5G services, for example, by providing backhaul. Possible use cases include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or vehicular passengers, or ensuring the availability of critical communications and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems, as well as low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite in a mega-constellation can cover several satellite network entities that create a ground cell. Ground cells can be created via ground relay nodes or by gNBs located on the ground or in satellites.

[0053] The system depicted is merely an example of a portion of a deployable radio access system, and in practice, the system may include multiple NodeBs, user equipment may access multiple radio cells, and the system may also include other devices such as physical layer relay nodes or other network elements. At least one of the NodeBs may be a home nodeB. Furthermore, multiple different types of radio cells and multiple radio cells may be provided in the geographical area of ​​the radio communication system. Radio cells may be macrocells (or umbrella cells) (which are large and small cells), typically having diameters of up to tens of kilometers, or smaller cells such as microcells, femtocells, or picocells. Figure 1 A NodeB can provide any type of these cells. Cellular radio systems can be implemented as multi-layer networks comprising several types of cells. Typically, in a multi-layer network, one access node provides one or more types of cells, and therefore multiple NodeBs are required to provide this network structure.

[0054] To meet the needs of improving communication system deployment and performance, the concept of "plug-and-play" NodeBs was introduced. Typically, in addition to the Home Node B (HnodeB), networks capable of using "plug-and-play" NodeBs also include Home Node B gateways or HNB-GWs (Host NodeB Gateways). Figure 1 (Not shown in the image). HNB gateways (HNB-GWs), typically installed within carrier networks, can aggregate traffic from a large number of HNBs back to the core network.

[0055] Figure 2 An example of device 20 is depicted in the image. Figure 2As shown, the device includes a processing circuitry system 22, a memory 24, and a communication interface 26 associated with or communicating with it. The processing circuitry system may communicate with the memory 24 (e.g., a memory device) via a bus for transferring information between components of the device. 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) that includes gates configured to store data (e.g., bits) that can be retrieved by a machine (e.g., a computing device such as a processing circuitry system). The memory device 24 may be configured to store information, data, content, applications, instructions, etc., so that the device can perform various functions according to exemplary embodiments of this disclosure. For example, the memory device 24 may be configured to buffer input data for processing by the processing circuitry system. Additionally or alternatively, the memory device 24 may be configured to store instructions for execution by the processing circuitry system. In some embodiments, the device 20 may be embodied in various computing devices as described above. However, in some embodiments, the device 20 may be embodied as a chip or chipset. In other words, device 20 may include one or more physical packages (e.g., chips), including materials, components, and / or wires on structural components (e.g., substrates). The structural components may provide physical strength, dimensional conservation, and / or electrical interaction constraints for the component circuitry systems included thereon. Therefore, in some cases, device 20 may be configured to implement embodiments of this disclosure on a single chip or as a single "system-on-a-chip." Thus, in some cases, a chip or chipset may constitute components for performing one or more operations to provide the functions described herein.

[0056] The processing circuitry system 22 can be embodied in a variety of different ways. For example, the processing circuitry system 22 can be embodied as one or more of various hardware processing components, such as a coprocessor, microprocessor, controller, data signal processor (DSP), processing element with or without an accompanying DSP, or various other circuitry systems including integrated circuits, such as, for example, ASIC (Application-Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), microcontroller unit (MCU), hardware accelerator, application-specific computer chip, etc. Therefore, in some embodiments, the processing circuitry system 22 may include one or more processing cores configured to execute independently. A multi-core processing circuitry system can implement multiple processing within a single physical package. Additionally or alternatively, the processing circuitry system 22 may include one or more processors configured via a bus to enable independent execution, pipelined, and / or multi-threaded instructions. In one example embodiment, the processing circuitry system 22 may be configured to execute instructions stored in memory device 24 or otherwise accessible by the processing circuitry system. Alternatively or additionally, the processing circuitry system 22 may be configured to perform hard-coded functions. Therefore, whether configured via hardware or software methods, or through a combination thereof, the processing circuitry 22 can represent an entity (e.g., physically embodied in a circuitry) capable of performing operations according to embodiments of this disclosure simultaneously in a corresponding configuration. Thus, for example, when the processing circuitry 22 is embodied as an ASIC, FPGA, etc., the processing circuitry 22 can be hardware specifically configured to perform the operations described herein. Alternatively, as another example, when the processing circuitry 22 is embodied as an instruction executor, the instructions can 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 can be a processor of a particular device (e.g., an image or video processing system) configured to employ embodiments of this disclosure by further configuring the processing circuitry 22 with instructions that perform the algorithms and / or operations described herein. The processing circuitry 22 may include a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of the processing circuitry 22.

[0057] Communication interface 26 can be any component, such as a device or circuit system embodied in hardware or a combination of hardware and software, configured to receive and / or transmit data, including media content in the form of video or image files, one or more audio tracks, etc. In this regard, for example, communication interface 26 may include antennas (or antennas) and supporting hardware and / or software for enabling communication with a wireless communication network. Additionally or alternatively, communication interface 26 may include circuitry for interacting with the antenna(s) to enable signal transmission via the antenna(s) or processing of signals received via the antenna(s). In some environments, communication interface 26 may alternatively or additionally support wired communication. Thus, for example, 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. Device 20 may be (or included therein) one or more types of devices, such as access nodes (e.g., base stations), UEs, and / or AIoT devices.

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

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

[0060] exist Figure 3 In the example, UE 11 may be located outside the AIoT topology. Therefore, in some examples, UE 11 may not be considered part of the AIoT session (e.g., it may not be pre-configured). According to one or more techniques of this disclosure, access node 12 can configure UE 11 for carrier wave transmission. That is, UE 11 can receive configuration associated with carrier wave transmission for one or more AIoT devices from access node 12 (e.g., gNB). In other words, according to this disclosure, access node 12 can configure UE 11 to transmit carrier wave signals for one or more AIoT devices. UE 11 can use the received configuration to perform one or more carrier wave transmissions for one or more AIoT devices. For example, UE 11 can use the received configuration to perform one or more carrier wave transmissions based on: UE 11's RRC state, UE 11's duplex capability (e.g., whether UE 11 includes frequency division duplex (FDD) capability or otherwise supports full-duplex communication), scheduling of UL or DL ​​transmissions performed by the UE, UE's service constraints, and / or UE 11's power constraints.

[0061] In some examples, in step 30, access node 12 may evaluate DL and / or UL activities at UE 11. For example, access node 12 may determine one or more service constraints of UE 11 (e.g., UL and / or DL ​​requirements of the target UE itself). In some examples, access node 12 may determine the amount of UL and / or DL ​​data to be sent to or from UE 11, respectively. Additionally or alternatively, access node 12 may evaluate DL and / or UL activities associated with one or more other UEs.

[0062] In some examples, in step 32, access node 32 may select UE 11 as a carrier wave (CW) generator for one or more AIoT devices. In some examples, access node 32 may select UE 11 as a carrier wave generator based on the location of UE 11 relative to one or more AIoT devices. In other words, access node 32 may select UE 11 as a carrier wave generator based on the relative proximity of UE 11 to one or more AIoT devices. Alternatively or additionally, access node 32 may select (e.g., configure) UE 11 as a carrier wave generator based on UE 11's service constraints, UE 11's FDD capability, and / or UE 11's power constraints.

[0063] In some examples, in step 34, access node 12 may assess the resource availability of carrier waves (e.g., for one or more carrier wave transmissions), for example, by comparing it with the resource availability of UL and / or DL ​​data (e.g., one or more UL and / or DL ​​data transmissions). Access node 12 may schedule one or more UL and / or DL ​​data transmissions for UE 11 (e.g., via first control information, such as downlink control information (DCI), media access control element (MAC-CE), or RRC message), and may determine the resource availability of the carrier wave transmission(s) and the scheduled UL and / or DL ​​data transmission(s). In some examples, the first control information may indicate the carrier frequency (e.g., a first carrier) used for data transmission, the waveform type associated with data transmission, the bandwidth associated with data transmission, the transmit power associated with data transmission, the duration associated with data transmission (e.g., a first duration), and / or the subframe index of the starting subframe for data transmission.

[0064] In step 36, UE 11 may be in an RRC connected state (e.g., it may have already established an RRC connection with access node 12, allowing UE 11 to operate in an RRC connected state). Furthermore, in some such examples, UE 11 may be scheduled for DL ​​data reception. For example, access node 12 may have already scheduled DL data transmission for UE 11 (e.g., via first control information, such as via DCI, MAC-CE, or RRC messages). In other words, step 36 may represent an example where UE 11 is in an RRC connected state and scheduled for DL ​​data reception. In some examples, the first control information may indicate one or more time and frequency resources for DL ​​data reception. For example, the first control information may indicate a first carrier via which UE 11 can receive DL data, and may also indicate a first duration during which UE 11 can receive DL data. In such examples, in step 36, access node 12 may determine a first priority associated with the carrier wave and a second priority associated with downlink data (e.g., scheduled downlink data transmission).

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

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

[0067] In some other examples, in step 36, access node 12 can 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, access node 12 can configure UE 11 (e.g., via second control information) to transmit the carrier wave signal while concurrently receiving DL data. In other words, access node 12 can configure carrier wave transmission (e.g., via second control information) such that carrier wave transmission is scheduled for FDD along with DL reception. That is, if the carrier wave has the same priority as the DL data, access node 12 can schedule UE 12 to receive DL data and can schedule carrier wave transmission during DL reception. In some examples, this configuration of carrier wave transmission can be affected by UE duplex capability. In other words, in an FDD scenario, UE 11 can continue DL reception (e.g., in the UL spectrum) while transmitting the carrier wave signal. In some such examples, when operating in RRC connected state, UE 11 can be configured by access node 12 (e.g., via the DL control channel, via second control information) to continue DL reception and begin carrier wave transmission.

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

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

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

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

[0072] In some examples, UE 11 may receive the first control information before, after, or together with the second control information (e.g., via the same downlink control message). In other words, the configuration of UL data and carrier waves can be performed in any order or simultaneously, and how UE 11 transmits UL data and carrier waves (e.g., one after another or concurrently, and what the transmission order is) depends on the corresponding configuration parameters (e.g., parameters associated with the carrier waves, parameters associated with the UL data).

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

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

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

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

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

[0078] In some examples, in step 40, the second control information may instruct UE 11 to use a second carrier whose frequency does not overlap with the first carrier (e.g., carrier frequency). In other words, UE 11 can be scheduled for UL data transmission on a first carrier that is inconsistent with (e.g., a different carrier) the second carrier configured for carrier wave transmission. In such an example, access node 12 can configure UE 11 to perform UL carrier aggregation, where one UL component carrier (e.g., the first component carrier (CC) configured for carrier aggregation at the UE) carries UL data services, while another component carrier (e.g., the second component carrier configured for carrier aggregation at the UE) carries the carrier wave of AIoT devices. In other words, if the CW carrier is inconsistent with the UL carrier, access node 12 can schedule UL carrier aggregation transmission at UE 11, where the first component carrier carries UL and the second component carrier carries the carrier wave. In such an example, access node 12 can allocate different transmit powers to different component carriers, for example, to increase the likelihood of successful UL data reception. In other words, if the UE is scheduled for UL transmission on a carrier different from the carrier wave, the access node 12 can schedule uplink carrier aggregation (e.g., using multiple component carriers) for UL data and carrier wave transmission, with uplink power allocation across different component carriers.

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

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

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

[0082] In another example embodiment, the UE can be scheduled for UL transmission, with carrier aggregation between UL data transmission and carrier wave transmission. In this example embodiment, the UE 11 can generate a UL data signal using a first baseband chain, generate a carrier wave signal using a second (e.g., a separate) baseband chain, upconvert the UL data signal to a first component carrier, upconvert the carrier wave signal to a second component carrier, aggregate the first and second component carriers, apply the corresponding transmit power configured for the first and second component carriers, and transmit the uplink data signal and the carrier wave signal using carrier aggregation.

[0083] Now for reference Figure 4 This describes some operations performed to provide carrier wave generation for device 20 (e.g., UE 11) in an example embodiment. Figure 4As shown, device 20 is configured to receive carrier wave transmission configurations (e.g., control information, such as via a downlink control channel) for one or more AIoT devices, wherein device 20 is outside the AIoT topology. Furthermore, device 20 is configured to perform carrier wave transmissions for one or more AIoT devices using the received configurations based on the UE's RRC state, the UE's duplex capability, and / or scheduling by the UE's UL or DL ​​transmissions. In some examples, the device may be configured to receive configurations (e.g., configurations associated with carrier wave transmissions for one or more AIoT devices) while in an RRC connected state and after being scheduled for DL ​​data transmission. In such examples, using the received configurations, device 20 may be configured to perform carrier wave transmissions for one or more AIoT devices: before, after, or together with scheduled DL transmissions in FDD.

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

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

[0086] In some examples, device 20 may include components for providing reception of the first control information before, after, or together with the second control information (e.g., via the same downlink control message). In other words, the configuration of DL data and carrier waves can be performed in any order or simultaneously, and how device 20 provides the transmission of DL data and carrier waves (e.g., one after another or concurrently, and what the transmission order is) depends on the configuration parameters.

[0087] like Figure 4 As shown in block 46, device 20 also includes components (e.g., processing circuitry 22, communication interface 26) for providing a carrier wave to the AIoT device according to the second control information during a second duration.

[0088] Now for reference Figure 5 This describes some operations performed in an example embodiment to provide carrier wave generation for device 20 (e.g., access node 12). Figure 5As shown, device 20 is configured to send configuration (e.g., control information, such as via a downlink control channel) for carrier wave transmission of one or more AIoT devices to a UE (e.g., a carrier wave node), wherein the carrier wave node is outside the AIoT topology. In some examples, device 20 is configured to send configuration (e.g., configuration associated with carrier wave transmission of one or more AIoT devices) based on the RRC connection between the carrier wave node and device 20, for example, after scheduling the carrier wave node to perform a DL transmission. In such examples, the configuration may instruct the carrier wave node to perform carrier wave transmission for one or more AIoT devices in the FDD before, after, or together with the scheduled DL transmission.

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

[0090] In some examples, such as Figure 5 As shown in block 52, device 20 includes components (e.g., processing circuitry 22, communication interface 26) for providing transmission of second control information to carrier wave nodes, wherein the second control information schedules the transmission of carrier waves to at least AIoT devices during a second duration.

[0091] Now for reference Figure 6 This describes some operations performed in an example embodiment to provide carrier wave generation for device 20 (e.g., UE 11, carrier wave node). Figure 6As shown, device 20 is configured to receive configurations (e.g., control information, such as via a downlink control channel) for carrier wave transmissions from one or more AIoT devices, wherein device 20 is outside the AIoT topology. Furthermore, device 20 is configured to perform carrier wave transmissions for one or more AIoT devices using the received configurations, based on the UE's RRC state, the UE's duplex capability, and / or the scheduling of UL or DL ​​transmissions performed by the UE. In some examples, the device may be configured to receive configurations (e.g., configurations associated with carrier wave transmissions from one or more AIoT devices) while in an RRC connected state and after being scheduled for UL data transmission. Alternatively or additionally, device 20 may be configured to receive configurations via an RRC connection release message, for example, before transitioning from an RRC connected state to an RRC inactive state. In such examples, the configuration may instruct the device to transmit carrier waves using an SDT. In some examples, the RRC connection release message (e.g., configurations indicated via a connection release message) may include resource allocation for the SDT associated with the carrier wave. Therefore, using the received configuration, device 20 can be configured to perform carrier wave transmission (e.g., STD transmission carrying a carrier) for one or more AIoT devices while operating in an RRC inactive state (e.g., and using resource allocation).

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

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

[0094] Now for reference Figure 7 This describes some operations performed in an example embodiment to provide carrier wave generation for device 20 (e.g., access node 12). Figure 7As shown, device 20 is configured to send a configuration (e.g., control information, such as via a downlink control channel) for carrier wave transmission of one or more AIoT devices to a UE (e.g., UE 11, a carrier wave node), where the UE is outside the AIoT topology. In some examples, device 20 is configured to send the configuration (e.g., configuration associated with carrier wave transmission of one or more AIoT devices) based on the RRC connection between the UE and device 20, for example, after scheduling a UL transmission for the UE. In such an example, the configuration may instruct the UE to perform carrier wave transmission of one or more AIoT devices in FDD before, after, or together with a scheduled DL transmission. In some other examples, the device may send the configuration via an RRC connection release message. In such an example, the configuration may include resource allocation for transmitting carrier waves via STD transmission when the UE is operating in an RRC inactive state.

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

[0096] In some examples, such as Figure 7 As shown in block 72, apparatus 20 includes components (e.g., processing circuitry 22, communication interface 26) for providing transmission of second control information to the UE based at least in part on the UE's Radio Resource Control (RRC) state, 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 located outside the AIoT topology associated with network nodes and AIoT devices.

[0097] As described above, a method, apparatus, and computer program product for providing improved carrier wave generation for AIoT devices are disclosed. In this regard, a method, apparatus, and computer program product are configured to: provide an activation signal including a test sequence received by the AIoT device, and provide a backscattered signal including the backscattered activation signal transmitted by the AIoT device. By providing 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 can provide improved carrier wave generation for AIoT devices. In some aspects, improved carrier wave generation may result in more efficient data communication with AIoT devices and reduced interference, thereby allowing for more accurate interpretation (e.g., decoding) of the data. Furthermore, by providing improved carrier wave generation for AIoT devices, data can be sent to (or received from) AIoT devices over a wider range.

[0098] Figures 4-7A flowchart depicting a method according to an exemplary embodiment of the present disclosure is illustrated. It should be understood that each block of the flowchart and combinations of blocks in the flowchart can be implemented in various ways, such as hardware, firmware, processors, circuit systems, and / or other communication devices associated with the execution of software including one or more computer program instructions. For example, one or more of the processes described above can be implemented by computer program instructions. In this regard, computer program instructions embodying the processes described above can be stored in memory 24 of apparatus 20 employing embodiments of the present disclosure and executed by processor 22. As will be understood, any such computer program instructions can be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine such that the resulting computer or other programmable device performs the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable storage medium that can instruct a computer or other programmable device to operate in a particular manner, such that the instructions stored in the computer programmable memory produce an article of art whose execution implements the functions specified in the flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable device to cause a series of operations to be performed on the computer or other programmable device, thereby producing a computer-implemented process such that the instructions executing in the computer or other programmable device provide operations for implementing the functions specified in the flowchart blocks. Therefore, the blocks of the flowchart support combinations of components for performing a specified function and combinations of operations for performing the specified function. It will also be understood that one or more blocks of the flowchart, and combinations of blocks in the flowchart, can be implemented by a dedicated hardware-based computer system or a combination of dedicated hardware and computer instructions to perform the specified function. Many modifications and other embodiments disclosed herein will come to mind for those skilled in the art to which this disclosure pertains, taking advantage of the teachings presented in the foregoing description and the associated drawings. Therefore, it should be understood that this disclosure is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Furthermore, although some exemplary embodiments have been described in the foregoing description and associated drawings in the context of some example combinations of elements and / or functions, it should be understood that alternative embodiments may provide different combinations of elements and / or functions without departing from the scope of the appended claims. In this regard, for example, combinations of elements and / or functions different from those explicitly described above, as described in some of the appended claims, may also be contemplated. Although specific terms are used herein, they are used in a general and descriptive sense and not for limiting purposes.

Claims

1. An apparatus comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: Provides the reception of control information from network nodes, wherein the control information is associated with the transmission of carrier waves to at least Ambient Internet of Things (AIoT) devices; and Provides the transmission of the carrier wave to the AIoT device based on the control information and at least in part on the radio resource control (RRC) status of the device.

2. The apparatus of claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: Provides reception of first control information from the network node, wherein the first control information schedules the transmission of uplink data via a first carrier, and wherein the control information schedules the transmission of the carrier wave via the first carrier or a second carrier based at least in part on the operation of the device in RRC connected state.

3. The apparatus of claim 2, wherein, in order to provide 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 transmitting the uplink data via the first carrier according to the first control information, transmission of the carrier wave via the first carrier according to the control information is provided.

4. The apparatus of claim 3, wherein the transmission of the carrier wave is provided after the transmission of the uplink data, at least in part based on: a first priority associated with the carrier wave being lower than a second priority associated with the uplink data.

5. The apparatus of claim 2, wherein, in order to provide 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: In conjunction with the transmission of the uplink data via the first carrier, the transmission of the carrier wave via the second carrier is provided according to the control information, wherein the first carrier and the second carrier include component carriers configured at the device for carrier aggregation.

6. The apparatus of claim 5, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: The reception provides a first indication of a first transmit power associated with the first carrier, wherein the transmission of uplink data via the first carrier is performed according to the first transmit power; and The reception provides a second indication of a second transmit power associated with the second carrier, wherein the transmission of the carrier wave via the second carrier is performed according to the second transmit power.

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

8. The apparatus of claim 2, wherein, in order to provide 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 according to the first transmission power, the transmission of the carrier wave according to the first transmission power is provided at least in part based on the first transmission power satisfying a threshold transmission power associated with the transmission of the carrier wave for the AIoT device.

9. The apparatus of claim 8, wherein providing transmission of the carrier wave via the first carrier is based at least in part on: a first priority associated with the carrier wave being the same as a second priority associated with the uplink data, and 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. The apparatus of claim 8, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: The device provides reception of an instruction to adjust the transmit power at the device from a second transmit power to a first transmit power, wherein the transmission of the uplink data according to the first transmit power is provided at least in part based on the instruction.

11. The apparatus of claim 8, wherein the first transmission power corresponds to the highest of the following: a second transmission power associated with the carrier wave, and a third transmission power associated with the uplink data.

12. The apparatus of claim 2, wherein, in order to provide 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: Concurrent provision: The transmission of uplink data on the first portion of the frequency domain resources associated with the first carrier, and Transmission of the carrier wave via a second portion of the frequency domain resources associated with the first carrier.

13. The apparatus of claim 12, wherein providing transmission of the carrier wave via the second portion of the frequency domain resource is at least partially based on: puncturing the second portion of the frequency domain resource.

14. The apparatus of claim 12, wherein providing transmission of the carrier wave via the second portion of the frequency domain resources is based at least in part on: 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. The apparatus of claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, cause the apparatus to: Provides the ability to receive an RRC connection release message from the network node while operating in an RRC connected state, wherein the RRC connection release message indicates: resource allocation for small data transmission associated with the carrier wave; and Provides a transition from the RRC connected state to the RRC inactive state based at least in part on the RRC connection release message, wherein, in order to provide the 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: Provides the small data transfer performed according to the resource allocation while operating in the RRC inactive state, wherein the small data transfer includes: At least in part based on the carrier wave of the device operating in the RRC inactive state.

16. The apparatus of claim 1, wherein the control information indicates 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 transmission 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 the transmission of the carrier wave.

17. The apparatus of 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 service constraints associated with the apparatus, or one or more transmit power constraints associated with the apparatus.

18. The apparatus of claim 1, wherein the apparatus includes a user equipment (UE), and wherein the UE is outside the AIoT topology associated with the network node and the AIoT device.

19. An apparatus comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the device to at least: Provides transmission of first control information to a carrier wave node, wherein the first control information is scheduled for transmission of uplink data via a first carrier at the carrier wave node; and Provides transmission of second control information to the carrier wave node based at least in part on the radio resource control (RRC) status of the carrier wave node, wherein the second control information is associated with the transmission of the carrier wave to at least an ambient Internet of Things (AIoT) device.

20. The apparatus of claim 19, wherein the second control information is used at least in part to schedule the transmission of the carrier wave using the first carrier or the second carrier based on the RRC connection between the carrier wave node and the apparatus.

21. The apparatus of claim 19, wherein the second control information indicates 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 transmission 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 the transmission of the carrier wave.

22. The apparatus of 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 service constraints associated with the carrier wave node, or one or more transmit power constraints associated with the carrier wave node.

23. The apparatus of claim 19, wherein the carrier wave node comprises a user equipment (UE).

24. A method comprising: Provides the reception of control information from network nodes, wherein the control information is associated with the transmission of carrier waves to at least Ambient Internet of Things (AIoT) devices; as well as Provides transmission of the carrier wave to the AIoT device based on the control information and at least in part on the radio resource control (RRC) status of the carrier wave node.

25. A method comprising: Provide the transmission of first control information to the carrier wave node, wherein the first control information is scheduled for transmission of uplink data via a first carrier at the carrier wave node; as well as Provides transmission of second control information to the carrier wave node based at least in part on the radio resource control (RRC) status of the carrier wave node, wherein the second control information is associated with the transmission of the carrier wave to at least an ambient Internet of Things (AIoT) device.

Images