WO2025212291A1

WO2025212291A1 - Ambient iot carrier waves and collision handling

Info

Publication number: WO2025212291A1
Application number: PCT/US2025/020873
Authority: WO
Inventors: Gang Xiong; Yi Guo; Dae Won Lee; Debdeep CHATTERJEE
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2024-04-05
Filing date: 2025-03-21
Publication date: 2025-10-09
Anticipated expiration: 2026-10-05

Abstract

Systems and methods are disclosed for Ambient Internet of Things (A- loT) devices that have at most a few hundred pW peak power consumption. Carrier wave (CW) transmission and collision handling for A-IoT applications are described for direct communication between A-IoT devices and base stations and indirect communications in which a reader is used. A user equipment (UE) provides the CW and, in indirect topologies, the same UE or a different UE may be used to transmit signals between the A-IoT device and base station. When scheduled CW and uplink transmissions from the UE overlap, one of the CW or uplink transmission may be predetermined to be canceled while the other is transmitted, or the transmission with a higher assigned priority may be transmitted.

Description

AMBIENT IOT CARRIER WAVES AND COLLISION HANDLING

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63/575,482, filed April 5, 2024, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless networks and wireless communications. Some embodiments relate to carrier wave transmission and collision handling for Ambient Internet of Things (A-IoT).

BACKGROUND

[0003] Mobile communication has evolved significantly from early voice systems to highly sophisticated integrated communication platform. Nextgeneration (NG) wireless communication systems, including 5^th generation (5G) and sixth generation (6G) or new radio (NR) systems, are to provide access to information and sharing of data by various UEs and applications. NR is to be a unified network/system that is to meet vastly different and sometimes conflicting performance dimensions and services driven by different services and applications. As such, the complexity of such communication systems, as well as interactions between elements within a communication system, has increased. In particular, A-IoT devices were introduced to reduce device size and power consumption for a myriad of uses. However, due to the specific limitations of A-IoT devices, coordination is to be enhanced between the A-IoT devices (UE) that transmits a carrier wave signal and the reader that receives the carrier wave signal.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which: [0005] FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.

[0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIGS. 3A and 3B illustrate topologies for A-IoT applications in accordance with some aspects.

[00010] FIG. 4 illustrates the UE as a carrier wave source in deployment topology 1 in accordance with some aspects.

[00011] FIG. 5 illustrates the UE as a carrier wave source in deployment topology 2 in accordance with some aspects.

[00012] FIG. 6 illustrates the UE as another carrier wave source in deployment topology 2 in accordance with some aspects.

[00013] FIG. 7 illustrates a time domain window for carrier wave signal transmission in accordance with some aspects.

DESCRIPTION

[00014] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in or substituted for, those of other embodiments. Embodiments outlined in the claims encompass all available equivalents of those claims.

[00015] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140 A includes 3 GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions. A network function may be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[00016] The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 may be collectively referred to herein as UE 101, and UE 101 may be used to perform one or more of the techniques disclosed herein.

[00017] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3 GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[00018] In some aspects, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[00019] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.

[00020] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and may be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[00021] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).

[00022] The UE 102 is shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[00023] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.

[00024] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes 111 and/or 112 may be a gNB, an eNB, or another type of RAN node.

[00025] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121. [00026] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[00027] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.

[00028] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120. [00029] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123. [00030] In some aspects, the communication network 140 A may be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5GNR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.

[00031] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network/5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF may be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs may be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs may be coupled to each other via Xn interfaces. [00032] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs may be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB may be a master node (MN) and NG-eNB may be a secondary node (SN) in a 5G architecture.

[00033] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 may be in communication with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.

[00034] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 may be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 may be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[00035] The UPF 134 may be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 may be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM may be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[00036] The AF 150 may provide information on the packet flow to the PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[00037] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162B, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B may be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B may be configured to handle the session states in the network, and the E-CSCF may be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B may be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B may be connected to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

[00038] In some aspects, the UDM/HSS 146 may be coupled to an application server 184, which can include a telephony application server (TAS) or another application server (AS) 160B. The AS 160B may be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[00039] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[00040] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G system architectures may be service-based and interaction between network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[00041] In some aspects, as illustrated in FIG. 1C, service-based representations may be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158 A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used. [00042] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein may be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

[00043] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1 A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[00044] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[00045] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general -purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[00046] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[00047] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The non-transitory machine readable medium 222 is a tangible medium. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.

[00048] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.

[00049] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.

[00050] Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[00051] The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.

[00052] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3 G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel. 19, etc ), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3 G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System/Extended Total Access Communication System (TACSZETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as 3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802.1 lad, IEEE 802. Hay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 Ip or IEEE 802.1 Ibd and other) Vehicle-to- Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802. l ip based DSRC, including ITS-G5 A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety related applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non-safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

[00053] Aspects described herein may be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3 -2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS = Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 - 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Service), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band, but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT -2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc.), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57-64/66 GHz (note: this band has near-global designation for Multi-Gigabit Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme may be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[00054] As above, loT has evolved to encompass diverse applications including smart home applications, smart city applications, and healthcare monitoring applications. In 3 GPP, various connectivity technologies have been tailored to loT applications, particularly Low Power, Wide-Area (LPWA) Technologies such as Narrowband loT (NB-IoT) and LTE-M, which were specified to address the needs of low-power devices, extending battery life and enabling use in remote locations.

[00055] An loT device is distinct from other 5G-enabled devices primarily in its purpose, design, and operational requirements. loT devices are designed to collect, transmit, and act on data, often with minimal human intervention. They are embedded with sensors, software, and connectivity to interact with other devices or systems, enabling automation and data-driven decision-making. Examples include smart home devices, industrial sensors, and wearable health monitors. In contrast, other 5G devices, like smartphones or tablets, are primarily focused on user interaction, high-speed data consumption, and multimedia applications. loT devices typically operate with low power consumption and minimal bandwidth, as they often transmit small amounts of data intermittently. [00056] In more detail, A-IoT devices are a subset of loT devices that have more limited size with no energy storage capability or with limited energy storage that does not involve manual replacement or recharging. In some embodiments, the A-IoT device may be designed to not permit replacement or recharging of the energy source by an end user (without damaging the A-IoT device). The output power of energy harvesters for A-IoT devices may range from about IpW to a few hundred pW. Existing cellular devices may not work well with energy harvesting due to their peak power consumption exceeding lOmW. loT devices and A-IoT devices differ at least in power source and design. loT devices typically rely on batteries or wired power sources for operation, are larger and involve periodic maintenance (such as battery replacement or recharging), and are designed to collect, process, and transmit data, often through direct human interaction or intervention for setup and management. A-IoT devices, on the other hand, harvest energy from ambient sources such as radio waves, light, motion, heat, or other environmental energy forms. This allows A-IoT devices to operate without batteries or with minimal reliance on such energy sources. A-IoT devices are also smaller, lower-cost, and maintenance-free, enabling greater scalability and flexibility in form factors. A- loT devices can be deployed in environments where battery replacement or wired power is impractical. A-IoT devices are designed to operate autonomously in the background, with minimal or no human intervention. A- loT devices collect data from their surroundings, process the data, and respond autonomously to changing conditions in real-time, allowing such devices to be used in applications where automation and adaptability are employed such as asset tracking, smart metering, and environmental monitoring. A-IoT devices encompass a wide range of applications and can be found in various settings. Examples of applications in which A-IoT devices are used include smart thermostats, smart appliances, smart lighting systems, health and wellness applications, environmental sensors, security cameras, voice assistants, smart mirrors, automated blinds and shades, smart parking systems, smart agriculture sensors, and connected cars. [00057] Technologies like LTE-M and NB-IoT are tailored for 5G devices, offering energy efficiency and wide-area coverage. Other 5G devices, such as those used for enhanced mobile broadband (eMBB), use high bandwidth and continuous connectivity to support applications like HD video streaming and virtual reality. loT devices are often deployed in massive numbers, sometimes reaching millions per square kilometer, to monitor and control environments or processes. This scalability is supported by 5G’s Massive Machine-Type Communications (mMTC) capabilities. Other 5G devices, like smartphones, are used individually or in smaller clusters, focusing on personal or enterprise-level connectivity. While some loT applications, such as industrial automation or autonomous vehicles, require ultra-reliable low-latency communication (URLLC), many loT devices operate with less stringent latency requirements. In contrast, other 5G devices, particularly those used for real-time applications like gaming or video conferencing, demand consistently low latency and high reliability. loT devices often integrate with various networks, including satellite, WiFi, and fixed lines, to create a seamless ecosystem. This enables loT devices to adapt to different environments and use cases. Other 5G devices primarily rely on cellular networks for connectivity. In summary, loT devices are specialized for data collection, automation, and scalability, often with low power and bandwidth needs, while other 5G devices focus on high-speed, user-centric applications with greater bandwidth and latency demands.

[00058] However, existing technologies are unable to meet all requirements for target use cases such as asset identification, inventory, and sensing. A-IoT technology may help to open new markets within 3 GPP systems, with connection numbers and device density potentially orders of magnitude higher than existing 3GPP loT technologies.

[00059] A-IoT devices typically have limited size with no energy storage capability or with limited energy storage that does not involve manual replacement or recharging. In some embodiments, the A-IoT device may be designed to not permit replacement or recharging of the energy source by an end user (without damaging the A-IoT device). The output power of energy harvesters for these devices may range from about IpW to a few hundred pW. Existing cellular devices may not work well with energy harvesting due to their peak power consumption exceeding lOmW.

[00060] Different A-IoT device types have been identified for study:

[00061] Device 1 : about 1 pW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10^x ppm (x may be 4 or 5, for example), neither reader to device (R2D) nor device to reader (D2R) amplification in the device. The device’s D2R transmission is backscattered on a carrier wave provided externally. The reader a network entity that serves as an intermediary (intermediate node or reader) between the A-IoT device and the core network. The reader may be, for example, a RAN node such as a gNB, eNB, distributed unit (DU), or transmission reception point (TRP).

[00062] Device 2a: at most a few hundred pW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10^x ppm (x may be 4 or 5, for example), both R2D and/or D2R amplification in the device. The device’s D2R transmission is backscattered on a carrier wave provided externally.

[00063] Device 2b: at most a few hundred pW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10^x ppm (x may be 4 or 5, for example), both R2D and/or D2R amplification in the device. The device’s D2R transmission is generated internally by the device.

[00064] Two topologies are considered for A-IoT applications: topology 1 in which the A-IoT device directly and bidirectionally communicates with a gNB, and topology 2 in which the A-IoT device communicates bidirectionally with an intermediate node or reader (relay, IAB node, UE, repeater, etc.) between the A-IoT device and gNB. In topology 1, the communication between the gNB and the A-IoT device includes A-IoT data and/or signaling. In topology 2, the intermediate node transfers A-IoT data and/or signaling between the gNB and the A-IoT device. The intermediate node transfers A-IoT data and/or signaling between the gNB and the A-IoT device. FIGS. 3A and 3B illustrate topologies for A-IoT applications in accordance with some aspects. Unless otherwise mentioned, the terms “intermediate node”, “UE”, “IAB node” and “relay” are interchangeable as used herein. [00065] For A-IoT applications in deployment topology 1 and 2, a UE may serve as a carrier wave source and transmit the carrier wave signal so that A-IoT device type 1 and 2a may perform backscattering on the transmission of D2R channels/signals. In order to allow the A-IoT device to transmit the D2R channel s/signals in timely manner, the UE that transmits the carrier wave signal and the reader coordinate. In particular, mechanisms on carrier wave transmission and collision handling between carrier wave and other channels/signals.

[00066] Mechanisms on carrier wave transmission

[00067] As mentioned above, for A-IoT applications in deployment topology 1 and 2, a UE may serve as a carrier wave source and transmit the carrier wave signal so that A-IoT device type 1 and 2a may perform backscattering on the transmission of D2R channels/signals. In order to allow the A-IoT device to transmit the D2R channels/signals in timely manner, coordination is used between the UE that transmits the carrier wave signal and the reader.

[00068] In one embodiment, gNB may indicate a UE to serve as a carrier wave (CW) source and to transmit the CW signal in deployment topology 1. In this case, gNB may serve as reader to communicate with A-IoT devices, where gNB transmits reader to device (R2D) channels/signals to A-IoT devices, and receives device to reader (D2R) channels/signals from A-IoT devices. For A-IoT device 1 and 2a, the A-IoT device performs backscattering based on the CW signal transmitted from the UE.

[00069] FIG. 4 illustrates the UE as a CW source in deployment topology

1 in accordance with some aspects. In FIG. 4, the UE serves as a CW source and transmits the CW signal to the A-IoT device. The A-IoT device performs backscattering for the transmission D2R channels/signals based on the CW signal from the UE.

[00070] In addition, for deployment topology 1, a first gNB may transmit the R2D channels/signals to the A-IoT device while a second gNB may receive the D2R channels/signals from the A-IoT device. In this case, when the UE serves as a CW source for CW signal transmission, the UE may receive the indication or configuration for CW signal transmission from either the first or second gNB.

[00071] In another embodiment, in deployment topology 2, a first UE serves as a reader to transmit the R2D channel s/signals to the A-IoT device and receive the D2R channel s/signals from the A-IoT device. In addition, the gNB indicates a second UE to serve as a CW source and to transmit the CW signal to the A-IoT devices. For A-IoT device 1 and 2a, the A-IoT device performs backscattering based on the CW signal transmitted from the second UE. FIG. 5 illustrates the UE as a CW source in deployment topology 2 in accordance with some aspects. In FIG. 5, the first UE serves as the reader and the second UE serves as the CW source. The A-IoT device performs backscattering for the transmission D2R channel s/signals based on the CW signal from the second UE. [00072] Alternatively, in deployment topology 2, a UE serves as a reader to transmit the R2D channel s/signals to the A-IoT device and receive the D2R channel s/signals from the A-IoT device. In addition, the gNB indicates the same UE to serve as a CW source and to transmit the CW signal to the A-IoT devices. For A-IoT device 1 and 2a, the A-IoT device performs backscattering based on the CW signal transmitted from the UE. FIG. 6 illustrates the UE as another CW source in deployment topology 2 in accordance with some aspects. In FIG. 6, the UE serves as both reader and CW source. The A-IoT device performs backscattering for the transmission D2R channel s/signals based on the CW signal from the UE.

[00073] In one embodiment, the UE may report the capability of supporting carrier wave transmission to the gNB. The capability may be a part of the capability of serving as a reader, where the UE can transmit the R2D channel s/signals to the A-IoT devices and receive the D2R channel s/signals from the A-IoT devices. In this case, the gNB may configure or trigger the UE to transmit the CW signal in a periodic, semi-persistent, and/or aperiodic manner. [00074] In one embodiment, the UE may be configured with a resource in the time and frequency domain for periodic CW signal transmission by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling. In particular, one or more following parameters in the time domain may be configured for CW signal transmission: periodicity and slot offset, starting symbol and/or number of symbols in a slot, or number of slots. In some aspects, the parameters may be determined in accordance with the subcarrier spacing for the uplink (UL) bandwidth part (BWP).

[00075] In addition, in the frequency domain, a starting resource element (RE), or a physical resource block (PRB), and/or a number of REs or PRBs may be configured in the frequency domain for CW signal transmission. When multi-tone-based CW signal transmission is configured, a set of frequency resources including a set of starting REs/number of REs or a set of starting PRBs/number of PRBs may be configured for CW signal transmission.

[00076] In some aspects, the resource for periodic CW signal transmission may be configured per BWP. If the CW signal is transmitted in the UL spectrum, the UE transmits the periodic CW signal in the active UL BWP or the initial UL BWP. If the CW signal is transmitted in the DL spectrum, the UE transmits the periodic CW signal in the active DL BWP or the initial DL BWP. [00077] In another embodiment, the UE may be configured with a set of resources in the time and frequency domain for CW signal transmission. In addition, the gNB may activate and release one resource from the set of resources for CW signal transmission based on downlink control information (DCI) or a Media Access Control - Control Element (MAC-CE). In particular, the UE may monitor DCI format 0 0, 0 1, 0 2 with a CRC scrambled by a Radio Network Temporary Identifier (RNTI) for activation and/or release of CW signal transmission. The RNTI may be predefined in the specification or configured by higher layers via RRC signaling.

[00078] The CW resource indication may be included in DCI format 0 0, 0 1 and/or 0 2 to indicate a CW resource from the set of CW resources that is configured for the time and frequency domain for the CW transmission. In some aspects, fields with known states may be defined to indicate the activation and/or deactivation of CW signal transmissions.

[00079] In another embodiment, the UE may be triggered to transmit the CW signal. In particular, a field, e.g., “CW signal request” may be included in the DCI to request the UE to transmit the CW signal. The CW signal request field may be a dedicated field. The DCI format may be the DCI format 0 0, 0 1, 0 2, 1 0, 1 1, and/or 1 2 for scheduling DL and UL transmission, respectively.

[00080] In one option, the UE may monitor the DCI format with a CRC scrambled by a control RNTI (C-RNTI). If the CW signal request is enabled, the UE transmits the CW signal in a time and frequency resource that may be configured by higher layers via RRC signaling.

[00081] In another option, one or more states may be configured for a CW signal request, where each state may correspond to one or more CW signal resource configurations. In this case, when one of the states is indicated in the DCI format, the UE transmits the CW signal in accordance with the indicated CW signal request state. Thus, states of the field(s) other than the known states may be used to indicate which of the CW signal resource configurations to use to transmit the CW signal.

[00082] In another option, a group common DCI may be used to trigger the UE to transmit the CW signal for A-IoT. In some aspects, the UE may monitor a group common DCI format with a CRC scrambled by a RNTI for a CW signal request. In this case, the RNTI may be predefined in the specification or configured by higher layers via RRC signaling. In the group common DCI, the CW signal request for a group of UEs may be included, where the UE determines whether the CW signal is transmitted in accordance with the CW signal request field for the UE in the group common DCI.

[00083] In another embodiment, when the UE transmits the CW signal, CW transmission timing may follow the DL transmission timing as defined in NR. In this case, a timing advance (TA) = 0 is applied for the CW transmission. [00084] In another option, when the UE transmits the CW signal, the CW transmission timing may follow the UL transmission timing as defined in NR. In this case, a TA is applied for the CW transmission.

[00085] In another embodiment, an open loop power control mechanism may apply for CW transmission. Further, power control parameters including alpha and P0 may be configured as part of the resource for CW signal transmission. In this case, the UE may transmit the CW signal in accordance with the configured alpha and P0 and open loop power control mechanism. [00086] Collision handling between carrier wave and other channels/signals

[00087] A number of embodiments may be used to provide collision handling between the carrier wave and other channel s/signals.

[00088] In one embodiment, when the UE transmits the CW signal, the UE is not expected to transmit other uplink channel s/signals in the Uu link (the air interface between the UE and the RAN).

[00089] In another option, if the UE is configured or scheduled to transmit other uplink channel s/signals in the Uu link and a CW signal for A-IoT communication in the same symbol(s), the UE may consider the CW signal as a higher priority and cancel the transmission of other physical uplink channels/signals. In this case, the CW signal transmission may have a higher priority than other uplink physical channels/signals.

[00090] In another embodiment, one or more uplink time domain windows may be configured by higher layers via RRC signaling. Each uplink time domain window may have parameters including starting slot offset, length or duration of a time window, and/or periodicity configured, where the starting slot offset, length, and periodicity are defined in accordance with the subcarrier spacing configured for active the DL and/or UL BWP, respectively.

[00091] During the uplink time domain, the UE may not be expected to transmit other physical uplink channels/signals in the Uu link and the UE only transmits the CW signal for A-IoT communications.

[00092] FIG. 7 illustrates a time domain window for CW signal transmission in accordance with some aspects. In FIG. 7, the starting slot offset and periodicity can be configured for the time window. During the time window, the UE only transmits the CW signal for A-IoT communications and is not expected to transmit other physical uplink channels/signals.

[00093] When more than one uplink time domain window is configured, one uplink time domain window may be activated or deactivated by a MAC-CE. Outside the uplink time domain window, a dropping rule may be defined when CW signal transmission collides with the transmission of other physical uplink channels/signals in the same symbol(s). [00094] In one option, when CW signal transmission collides with other physical uplink channel s/signals in the same symbols, the UE may drop the CW signal and transmit the other physical uplink channels or signals. In addition, the UE may cancel the CW signal in the overlapped symbols. Alternatively, the UE may cancel the entire CW signal.

[00095] In some aspects, other physical UL signals or channels may include Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), or Physical Random Access Channel (PRACH). In another option, when CW signal transmission collides with other physical uplink channel s/signals in the same symbols, the UE may drop the other physical uplink channel s/signals and transmit the CW signal. [00096] In another option, whether to drop the CW signal or other uplink channel s/signals may depend on the priority of the uplink channel s/signals. In one example, when the CW signal collides with other uplink channel s/signals with high priority, the CW signal is dropped and the other uplink channel s/signals are transmitted.

[00097] Examples

[00098] Example 1 is an apparatus of a user equipment (UE), the apparatus comprising a processor that configures the apparatus to: receive, from a 5th generation NodeB (gNB), an indication of a resource in a time and frequency domain for carrier wave (CW) transmission for an Ambient Internet of Things (A-IoT) device; in response to reception of the indication, use the time and frequency domain of the resource to transmit a CW signal for the A-IoT device; and in a topology in which the UE is configured to act as an intermediate node or reader between the A-IoT device and the gNB, receive from the A-IoT device a signal backscattered on the CW signal.

[00099] In Example 2, the subject matter of Example 1 includes, wherein the processor further configures the apparatus to receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal in a topology in which an A-IoT device that receives the CW signal uses the CW signal to communicate directly with the gNB. In Example 3, the subject matter of Examples 1-2 includes, wherein the processor further configures the apparatus to receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal in a topology in which an A-IoT device that receives the CW signal uses the CW signal to communicate with the gNB through a reader by reception of a reader- to-device (R2D) signal and transmission, to the reader using the CW signal, of a device-to-reader (D2R) signal in response to the R2D signal.

[000100] In Example 4, the subject matter of Examples 1-3 includes, wherein the processor further configures the apparatus to: receive, from the gNB, an indication that the UE is to serve as a CW source and information to be transmitted to an A-IoT device; transmit, to the A-IoT device, a reader-to-device (R2D) signal based on the information; receive, from the A-IoT device in response to the R2D signal, a device-to-reader (D2R) signal that contains A-IoT information for transmission to the gNB; and transmit, to the gNB, the A-IoT information received from the A-IoT device.

[000101] In Example 5, the subject matter of Examples 1-4 includes, wherein the processor further configures the apparatus to report, to the gNB, a UE capability to support CW transmission.

[000102] In Example 6, the subject matter of Examples 1-5 includes, wherein the processor configures the apparatus to: transmit CW signals in at least one of a periodic, semi-persistent, or aperiodic manner; and for transmission of the CW signals in the periodic manner, receive time and frequency domain resources for CW signal transmission via higher layers in at least one of: new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling.

[000103] In Example 7, the subject matter of Example 6 includes, wherein the time and frequency domain resources for transmission of the CW signals in the periodic manner are configured per bandwidth part (BWP).

[000104] In Example 8, the subject matter of Examples 1-7 includes, wherein the processor configures the apparatus to: receive, from the gNB, a set of time and frequency domain resources for CW signal transmission; and receive, in one of downlink control information (DCI) or a Media Access Control - Control Element (MAC-CE), an indication of one of activation or release of one of the time and frequency domain resources from the set of time and frequency domain resources.

[000105] In Example 9, the subject matter of Example 8 includes, wherein a dedicated field in the DCI is used to provide the indication.

[000106] In Example 10, the subject matter of Examples 8-9 includes, wherein at least one state of a field in the DCI other than a known states of the field are used to indicate which of the time and frequency domain resources of the set of time and frequency domain resources to use to transmit the CW signal. [000107] In Example 11, the subject matter of Examples 8-10 includes, wherein a group common DCI is used to trigger transmission of the CW signal.

[000108] In Example 12, the subject matter of Examples 1-11 includes, wherein at least one of: transmission of the CW signal follows new radio (NR) downlink transmission timing, or an open loop power control mechanism is applied to transmission of the CW signal.

[000109] In Example 13, the subject matter of Examples 1-12 includes, wherein transmission of the CW signal is configured to avoid overlap with transmission of uplink signals between the UE and the gNB.

[000110] In Example 14, the subject matter of Examples 1-13 includes, wherein the processor configures the apparatus to: determine that transmission of the CW signal is scheduled to overlap with transmission of an uplink signal between the UE and the gNB, and in response to a determination that the transmission of the CW signal is scheduled to overlap with the transmission of the uplink signal, cancel the transmission of the uplink signal and transmit the CW signal.

[000111] In Example 15, the subject matter of Examples 1-14 includes, wherein the processor configures the apparatus to: determine that transmission of the CW signal is scheduled to overlap with transmission of an uplink signal between the UE and the gNB, and in response to a determination that the transmission of the CW signal is scheduled to overlap with the transmission of the uplink signal, cancel the transmission of the CW signal and transmit the uplink signal. [000112] In Example 16, the subject matter of Examples 1-15 includes, wherein the processor configures the apparatus to: determine that transmission of the CW signal is scheduled to overlap with transmission of an uplink signal between the UE and the gNB, in response to a determination that the transmission of the CW signal is scheduled to overlap with the transmission of the uplink signal, determine which of the CW signal and the uplink signal has a higher priority, and transmit the CW signal and the uplink signal having the higher priority.

[000113] Example 17 is an apparatus of an Ambient Internet of Things (A- loT), the apparatus comprising a processor that configures the apparatus to: receive, from a user equipment (UE), a carrier wave (CW) signal on a resource; and use backscatter of the CW signal to transmit an A-IoT channel or signal to a 5th generation NodeB (gNB).

[000114] In Example 18, the subject matter of Example 17 includes, wherein the processor further configures the apparatus to at least one of: receive a signal directly from the gNB and transmit the A-IoT channel or signal as a response to the signal from the gNB, or receive the signal via a reader-to-device (R2D) signal transmitted by a reader and transmit the response to the reader using a device-to-reader (D2R) signal.

[000115] Example 19 is a computer-readable storage medium that stores instructions for execution by one or more processors of an apparatus of a user equipment (UE), the instructions, when executed, configured to cause the apparatus to: receive, from a 5th generation NodeB (gNB), an indication of a resource in a time and frequency domain for carrier wave (CW) transmission for an Ambient Internet of Things (A-IoT) device; in response to reception of the indication, use the time and frequency domain of the resource to transmit a CW signal for the A-IoT device; and in a topology in which the UE is configured to act as an intermediate node or reader between the A-IoT device and the gNB, receive from the A-IoT device a signal backscattered on the CW signal.

[000116] In Example 20, the subject matter of Example 19 includes, wherein the instructions, when executed, configured to cause the apparatus to at least one of: receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal in at least one of: a first topology in which an A-IoT device that receives the CW signal uses the CW signal to communicate directly with the gNB, or a second topology in which the A-IoT device that receives the CW signal uses the CW signal to communicate with the gNB through a reader by reception of a reader-to-device (R2D) signal and transmission, to the reader using the CW signal, of a device-to-reader (D2R) signal in response to the R2D signal, receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal, or receive, from the gNB, the indication that the UE is to serve as the CW source and information to be transmitted to the A-IoT device, transmit, to the A-IoT device, an R2D signal based on the information, receive, from the A-IoT device in response to the R2D signal based on the information, a D2R signal that contains A-IoT information for transmission to the gNB, and transmit, to the gNB, the A-IoT information received from the A-IoT device.

[000117] Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-20.

[000118] Example 22 is an apparatus comprising means to implement of any of Examples 1-20.

[000119] Example 23 is a system to implement of any of Examples 1-20.

[000120] Example 24 is a method to implement of any of Examples 1-20.

[000121] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[000122] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [000123] In this document, the terms "a" or "an" are used, as is common in patent documents, to indicate one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. As indicated herein, although the term “a” is used herein, one or more of the associated elements may be used in different embodiments. For example, the term “a processor” configured to carry out specific operations includes both a single processor configured to carry out all of the operations as well as multiple processors individually configured to carry out some or all of the operations (which may overlap) such that the combination of processors carry out all of the operations. Further, the term “includes” may be considered to be interpreted as “includes at least” the elements that follow. [000124] The Abstract of the Disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it may be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment (UE), the apparatus comprising a processor that configures the apparatus to: receive, from a 5^th generation NodeB (gNB), an indication of a resource in a time and frequency domain for carrier wave (CW) transmission for an Ambient Internet of Things (A-IoT) device; in response to reception of the indication, use the time and frequency domain of the resource to transmit a CW signal for the A-IoT device; and in a topology in which the UE is configured to act as an intermediate node or reader between the A-IoT device and the gNB, receive from the A-IoT device a signal backscattered on the CW signal.

2. The apparatus of claim 1, wherein the processor further configures the apparatus to receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal in a topology in which an A-IoT device that receives the CW signal uses the CW signal to communicate directly with the gNB.

3. The apparatus of claim 1 or 2, wherein the processor further configures the apparatus to receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal in a topology in which an A-IoT device that receives the CW signal uses the CW signal to communicate with the gNB through a reader by reception of a reader-to-device (R2D) signal and transmission, to the reader using the CW signal, of a device-to-reader (D2R) signal in response to the R2D signal.

4. The apparatus of any one of claims 1-3, wherein the processor further configures the apparatus to: receive, from the gNB, an indication that the UE is to serve as a CW source and information to be transmitted to an A-IoT device; transmit, to the A-IoT device, a reader-to-device (R2D) signal based on the information; receive, from the A-IoT device in response to the R2D signal, a device- to-reader (D2R) signal that contains A-IoT information for transmission to the gNB; and transmit, to the gNB, the A-IoT information received from the A-IoT device.

5. The apparatus of any one of claims 1-4, wherein the processor further configures the apparatus to report, to the gNB, a UE capability to support CW transmission.

6. The apparatus of any one of claims 1-5, wherein the processor configures the apparatus to: transmit CW signals in at least one of a periodic, semi-persistent, or aperiodic manner; and for transmission of the CW signals in the periodic manner, receive time and frequency domain resources for CW signal transmission via higher layers in at least one of: new radio (NR) remaining minimum system information (RMSI), NR other system information (OSI), or dedicated radio resource control (RRC) signaling.

7. The apparatus of claim 6, wherein the time and frequency domain resources for transmission of the CW signals in the periodic manner are configured per bandwidth part (BWP).

8. The apparatus of any one of claims 1-7, wherein the processor configures the apparatus to: receive, from the gNB, a set of time and frequency domain resources for CW signal transmission; and receive, in one of downlink control information (DCI) or a Media Access Control - Control Element (MAC-CE), an indication of one of activation or release of one of the time and frequency domain resources from the set of time and frequency domain resources.

9. The apparatus of claim 8, wherein a dedicated field in the DCI is used to provide the indication.

10. The apparatus of claim 8 or 9, wherein at least one state of a field in the DCI other than a known states of the field are used to indicate which of the time and frequency domain resources of the set of time and frequency domain resources to use to transmit the CW signal.

11. The apparatus of any one of claims 8-10, wherein a group common DCI is used to trigger transmission of the CW signal.

12. The apparatus of any one of claims 1-11, wherein at least one of: transmission of the CW signal follows new radio (NR) downlink transmission timing, or an open loop power control mechanism is applied to transmission of the CW signal.

13. The apparatus of any one of claims 1-12, wherein transmission of the CW signal is configured to avoid overlap with transmission of uplink signals between the UE and the gNB.

14. The apparatus of any one of claims 1-13, wherein the processor configures the apparatus to: determine that transmission of the CW signal is scheduled to overlap with transmission of an uplink signal between the UE and the gNB, and in response to a determination that the transmission of the CW signal is scheduled to overlap with the transmission of the uplink signal, cancel the transmission of the uplink signal and transmit the CW signal.

15. The apparatus of any one of claims 1-14, wherein the processor configures the apparatus to: determine that transmission of the CW signal is scheduled to overlap with transmission of an uplink signal between the UE and the gNB, and in response to a determination that the transmission of the CW signal is scheduled to overlap with the transmission of the uplink signal, cancel the transmission of the CW signal and transmit the uplink signal.

16. The apparatus of any one of claims 1-15, wherein the processor configures the apparatus to: determine that transmission of the CW signal is scheduled to overlap with transmission of an uplink signal between the UE and the gNB, in response to a determination that the transmission of the CW signal is scheduled to overlap with the transmission of the uplink signal, determine which of the CW signal and the uplink signal has a higher priority, and transmit the CW signal and the uplink signal having the higher priority.

17. An apparatus of an Ambient Internet of Things (A-IoT), the apparatus comprising a processor that configures the apparatus to: receive, from a user equipment (UE), a carrier wave (CW) signal on a resource; and use backscatter of the CW signal to transmit an A-IoT channel or signal to a 5^th generation NodeB (gNB).

18. The apparatus of claim 17, wherein the processor further configures the apparatus to at least one of: receive a signal directly from the gNB and transmit the A-IoT channel or signal as a response to the signal from the gNB, or receive the signal via a reader-to-device (R2D) signal transmitted by a reader and transmit the response to the reader using a device-to-reader (D2R) signal.

19. A computer-readable storage medium that stores instructions for execution by one or more processors of an apparatus of a user equipment (UE), the instructions, when executed, configured to cause the apparatus to: receive, from a 5^th generation NodeB (gNB), an indication of a resource in a time and frequency domain for carrier wave (CW) transmission for an Ambient Internet of Things (A-IoT) device; in response to reception of the indication, use the time and frequency domain of the resource to transmit a CW signal for the A-IoT device; and in a topology in which the UE is configured to act as an intermediate node or reader between the A-IoT device and the gNB, receive from the A-IoT device a signal backscattered on the CW signal.

20. The computer-readable storage medium of claim 19, wherein the instructions, when executed, configured to cause the apparatus to at least one of: receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal in at least one of: a first topology in which an A-IoT device that receives the CW signal uses the CW signal to communicate directly with the gNB, or a second topology in which the A-IoT device that receives the CW signal uses the CW signal to communicate with the gNB through a reader by reception of a reader-to-device (R2D) signal and transmission, to the reader using the CW signal, of a device-to-reader (D2R) signal in response to the R2D signal, receive, from the gNB, an indication that the UE is to serve as a CW source and transmit the CW signal, or receive, from the gNB, the indication that the UE is to serve as the CW source and information to be transmitted to the A-IoT device, transmit, to the A- loT device, an R2D signal based on the information, receive, from the A-IoT device in response to the R2D signal based on the information, a D2R signal that contains A-IoT information for transmission to the gNB, and transmit, to the gNB, the A-IoT information received from the A-IoT device.