Frame structure for synchronized operation of environmental internet of things devices

By designing fixed resource locations in the frame structure, the problems of high error rate and high power consumption in asynchronous operation of ambient IoT devices are solved, and efficient synchronous operation and long-distance communication are achieved.

CN120642357APending Publication Date: 2025-09-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380092889.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-02-10
Filing Date
2023-12-15
Publication Date
2025-09-12

AI Technical Summary

Technical Problem

Ambient Internet of Things (IoT) devices suffer from high error rates, communication losses, and high power consumption in asynchronous operation, especially when lacking power amplifier support in uplink transmission.

Method used

A frame structure is designed, including the primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH), downlink channel and uplink channel, to ensure that the uplink trigger message resources are in a fixed relative position with respect to the PSS, supporting the synchronous operation of ambient IoT devices and network devices.

Benefits of technology

It achieves efficient synchronous operation of environmental IoT devices, reduces power, computing and communication resource consumption, and supports long-distance, high-density IoT device communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120642357A_ABST
    Figure CN120642357A_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, an environmental Internet of Things (IoT) device may receive configuration information indicating resources associated with an uplink trigger message initiating a communication session between the environmental IoT device and a network device. The environmental IoT device may transmit the uplink trigger message to the network device using the resource associated with the uplink trigger message. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 18 / 167,377, filed on February 10, 2023, entitled “FRAME STRUCTURE FOR SYNCHRONOUS OPERATION OF AN AMBIENT INTERNET-OF-THINGSDEVICE,” and assigned to the assignee of the present application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for frame structures for synchronized operation of ambient IoT devices. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink and uplink communications. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0007] Some aspects described herein relate to a method for wireless communication performed by an ambient Internet of Things (IoT) device. The method may include receiving configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and a network device. The method may include sending the uplink trigger message to the network device using the resources associated with the uplink trigger message.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network device. The method may include sending, to an ambient IoT device, configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and the network device. The method may also include receiving the uplink trigger message from the ambient IoT device using the resources associated with the uplink trigger message.

[0009] Some aspects described herein relate to an ambient IoT device for wireless communication. The ambient IoT device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and a network device. The one or more processors may be configured to send the uplink trigger message to the network device using the resources associated with the uplink trigger message.

[0010] Some aspects described herein relate to a network device for wireless communication. The network device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send, to an ambient IoT device, configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and the network device. The one or more processors may be configured to receive the uplink trigger message from the ambient IoT device using the resources associated with the uplink trigger message.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by an ambient IoT device. The one or more instructions, when executed by one or more processors of the ambient IoT device, may cause the ambient IoT device to: receive configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and a network device; and, when executed by the one or more processors of the ambient IoT device, may cause the ambient IoT device to: send the uplink trigger message to the network device using the resources associated with the uplink trigger message.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing one or more instructions for wireless communication by a network device. The one or more instructions, when executed by one or more processors of the network device, may cause the network device to: send, to an ambient IoT device, configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and the network device. The one or more instructions, when executed by the one or more processors of the network device, may cause the network device to: receive, from the ambient IoT device, an uplink trigger message using the resources associated with the uplink trigger message.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving configuration information indicating resources associated with an uplink trigger message that initiates a communication session between the apparatus and a network device. The apparatus may also include means for sending the uplink trigger message to the network device using the resources associated with the uplink trigger message.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending, to an ambient IoT device, configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and the apparatus. The apparatus may also include means for receiving, from the ambient IoT device, the uplink trigger message using the resources associated with the uplink trigger message.

[0015] The various aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and description, and as illustrated in the accompanying drawings and description.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporated into the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and compositions. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order that the above-mentioned features of the present disclosure may be fully understood, a more particular description of the invention briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). It should be noted, however, that the drawings illustrate only certain typical aspects of the present disclosure and are not therefore to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of physical channels and reference signals in a wireless network according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a synchronization signal hierarchical structure according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example associated with backscatter communication according to the present disclosure.

[0025] Figure 7 is a diagram of an example associated with synchronization operations of ambient Internet of Things (IoT) devices according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example frame structure for synchronization operations of ambient IoT devices according to the present disclosure.

[0027] Figure 9 is a diagram illustrating an example process performed, for example, by an ambient IoT device according to the present disclosure.

[0028] Figure 10 is a diagram illustrating an example process performed, for example, by a network device according to the present disclosure.

[0029] Figure 11 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0030] Figure 12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0031] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. Those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present claims.

[0032] In some cases, ambient Internet of Things (IoT) devices (sometimes referred to as ultra-light IoT devices) may be used to communicate with network devices. An ambient IoT device may be an IoT device that is capable of sending uplink trigger messages and, therefore, may initiate a communication session with the network device from the IoT device side. An ambient IoT device may be associated with uplink transmissions that do not utilize a power amplifier (PA) (e.g., transmissions in the range of 0 dBm to 5 dBm) and have limited transmission capabilities for such uplink transmissions, such as the ability to simply send a preamble transmission to indicate uplink traffic. Such ambient IoT devices may use asynchronous operation, which may result in high error rates, communication losses, and other high power consumption to correct communication errors and / or retransmit lost messages. Therefore, there remains a need to efficiently support synchronous operation of ambient IoT devices.

[0033] Some of the techniques and apparatus described herein enable a frame structure to support synchronous operation of ambient IoT devices. In some aspects, the frame structure may include resources associated with a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH), a downlink channel, an uplink channel, and / or an uplink trigger message. For example, the frame structure may include resources associated with an uplink trigger message that appear at a fixed relative position relative to resources associated with the PSS. In this regard, an ambient IoT device or similar device may obtain network timing from the PSS and use the resources associated with the uplink trigger message to send an uplink trigger message to a network device, which may initiate a communication session between the ambient IoT device and the network device. Therefore, some of the techniques and apparatus described herein enable efficient synchronous operation of ambient IoT devices, thereby reducing power, computing, and communication resource consumption associated with other IoT devices and / or enabling long-distance, high-density IoT device communications.

[0034] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0035] Although various aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G (e.g., 6G) RATs.

[0036] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (illustrated as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (illustrated as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, meaning that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0037] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110, such as a converged network node 110 or a decomposed network node 110, may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, an RU, a CU, a mobility element of a network, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 using any suitable transport network via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks.

[0038] In some examples, network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​network node 110 and / or a network node subsystem serving that coverage area, depending on the context in which the term is used. Network node 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs 120 with service subscriptions. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 associated with the femtocell (e.g., UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macrocell may be referred to as a macro network node. A network node 110 for a picocell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1 In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0039] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with network node 110. In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0040] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110 d (e.g., a relay network node) may communicate with a network node 110 a (e.g., a macro network node) and a UE 120 d to facilitate communications between the network node 110 a and the UE 120 d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0041] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0042] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0043] UEs 120 may be dispersed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0044] Some UEs 120 may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, the processor component (e.g., one or more processors) and the memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0045] Generally speaking, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0046] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0047] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes arises with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0048] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz–24.25 GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation to more than 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz–71 GHz), FR4 (52.6 GHz–114.25 GHz), and FR5 (114.25 GHz–300 GHz). Each of these higher frequency bands falls within the EHF band.

[0049] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a, FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0050] In some aspects, the ambient IoT device described elsewhere herein may correspond to UE 120. Additionally or alternatively, the ambient IoT device may include a communications manager 140. As described in greater detail elsewhere herein, communications manager 140 may: receive configuration information indicating resources associated with an uplink trigger message that initiates a communication session between the ambient IoT device and a network device; and send the uplink trigger message to the network device using the resources associated with the uplink trigger message. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0051] In some aspects, the network device described elsewhere herein may correspond to network node 110. Additionally or alternatively, the network device may include a communications manager 150. As described in greater detail elsewhere herein, communications manager 150 may: send, to an ambient IoT device, configuration information indicating resources associated with an uplink trigger message initiating a communication session between the ambient IoT device and the network device; and receive an uplink trigger message from the ambient IoT device using the resources associated with the uplink trigger message. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

[0052] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0053] Figure 2 2 is a diagram illustrating example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a through 234t, such as T antennas (T ≥ 1). The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R ≥ 1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components, such as one or more CUs or one or more DUs, that facilitate direct communication with the UE 120.

[0054] At network node 110, transmit processor 220 may receive data intended for UE 120 (or a group of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., PSS or SSS). The transmit (TX) multiple-input, multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a through 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or frequency upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a through 234t).

[0055] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use the demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other things, a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0056] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0057] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more groups of antenna elements, and / or one or more antenna arrays, etc. An antenna panel, antenna group, group of antenna elements, and / or antenna array may include one or more antenna elements (within a single housing or multiple housings), a group of coplanar antenna elements, a group of non-coplanar antenna elements, and / or be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0058] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to execute the instructions herein (eg, reference Figures 7 to 12 ) any aspects of any of the methods described.

[0059] At network node 110, uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component (shown as DEMOD) of modem 232), detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240. Network node 110 may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modem 232 of network node 110 may include a modulator and a demodulator. In some examples, network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions herein (e.g., reference 242). Figures 7 to 12 ) any aspects of any of the methods described.

[0060] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the may perform one or more techniques associated with the frame structure for synchronous operation of ambient IoT devices, as described in more detail elsewhere herein. In some aspects, the network device described herein is a network node 110, included in a network node 110, or includes Figure 2 Furthermore, in some aspects, the ambient IoT device described herein is a UE 120, is included in a UE 120, or includes Figure 2 One or more components of the UE 120 are shown. The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the may perform or direct e.g. Figure 9 The process of 900 Figure 10 1000 and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 9 The process of 900 Figure 10 The operations of process 1000 and / or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0061] In some aspects, the ambient IoT device includes: means for receiving configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and a network device; and / or means for sending an uplink trigger message to the network device using the resources associated with the uplink trigger message. In some aspects, means for the ambient IoT device to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0062] In some aspects, the network device includes: means for sending configuration information to the ambient IoT device indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and the network device; and / or means for receiving an uplink trigger message from the ambient IoT device using the resources associated with the uplink trigger message. In some aspects, means for the network device to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0063] Although Figure 2 The blocks in FIG. 2 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0064] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0065] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated architecture or a decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also known as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0066] A converged base station (e.g., a converged network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually spread across one or more other network nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among others.

[0067] Base station type operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that can be deployed separately. A disaggregated base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0068] Figure 3 FIG2 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0069] Each of the units (including the CU 310, DU 330, RU 340) and the near-RT RIC 325, the non-RT RIC 315, and the SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more of the other units via the transmission medium. In some examples, each of the units may include a wired interface configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0070] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, among others. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0071] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers, at least in part according to a functional split (such as that defined by 3GPP). In some aspects, the one or more higher PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like. In some aspects, the DU 330 may also host one or more lower PHY layers, such as those implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0072] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0073] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0074] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0075] In some implementations, the non-RT RIC 315 can receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in the near-RT RIC 325. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or through the creation of RAN management policies (such as A1 interface policies).

[0076] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0077] Figure 4 4 is a diagram illustrating an example 400 of physical channels and reference signals in a wireless network according to the present disclosure. Figure 4 As shown in , the downlink channel and the downlink reference signal may carry information from the network node 110 to the UE 120 , and the uplink channel and the uplink reference signal may carry information from the UE 120 to the network node 110 .

[0078] As shown, downlink channels may include, for example, a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, or a PBCH carrying system information. In some aspects, PDSCH communications may be scheduled by PDCCH communications. As further shown, uplink channels may include, for example, a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, or a PRACH for initial network access. In some aspects, UE 120 may send acknowledgement (ACK) or negative acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0079] As further shown, the downlink reference signal may include a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a DMRS, a positioning reference signal (PRS), or a phase tracking reference signal (PTRS), etc. As also shown in the figure, the uplink reference signal may include a sounding reference signal (SRS), a DMRS, or a PTRS, etc.

[0080] The SSB may carry information used for initial network acquisition and synchronization, such as the PSS, SSS, PBCH, and PBCH DMRS. The SSB is sometimes referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the network node 110 may transmit multiple SSBs on multiple corresponding beams, and the SSBs may be used for beam selection. Aspects of the SSB are discussed below with respect to Figure 5 Describe in more detail.

[0081] The CSI-RS may carry information used for downlink channel estimation (e.g., downlink CSI acquisition), which may be used for scheduling, link adaptation, or beam management, among other things. Network node 110 may configure a CSI-RS set for UE 120, and UE 120 may measure the configured CSI-RS set. Based at least in part on the measurements, UE 120 may perform channel estimation and may report channel estimation parameters such as CQI, precoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), rank indicator (RI), or RSRP to network node 110 (e.g., in a CSI report). Network node 110 may use the CSI report to select transmission parameters for downlink communication with UE 120, such as the number of transmission layers (e.g., rank), precoding matrix (e.g., precoder), MCS, or a refined downlink beam (e.g., using a beam refinement process or a beam management process).

[0082] DMRS can carry information used to estimate the radio channel to demodulate the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of DMRS can be specific to the physical channel that the DMRS is used to estimate. DMRS is UE-specific, can be beamformed, can be restricted to scheduled resources (e.g., rather than being sent over a wideband), and can be sent only when necessary. As shown in the figure, DMRS is used for both downlink and uplink communications.

[0083] PTRS can carry information used to compensate for oscillator phase noise. Typically, phase noise increases with increasing oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve phase noise and common phase error (CPE) suppression. As shown in the figure, PTRS is used for both downlink communications (e.g., on the PDSCH) and uplink communications (e.g., on the PUSCH).

[0084] The PRS may carry information used to implement timing or ranging measurements of the UE 120 based on signals transmitted by the network node 110 to improve observed time difference of arrival (OTDOA) positioning performance. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped in a diagonal pattern with a frequency offset and a time offset to avoid collisions with cell-specific reference signals and control channels (e.g., PDCCH). Generally speaking, the PRS may be designed to improve detectability for the UE 120, which may need to detect downlink signals from multiple adjacent network nodes in order to perform OTDOA-based positioning. Therefore, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells) and may report a reference signal time difference (RSTD) based on OTDOA measurements associated with the PRS received from the multiple cells. In some aspects, the network node 110 may then calculate the position of the UE 120 based on the RSTD measurements reported by the UE 120.

[0085] The SRS may carry information used for uplink channel estimation, which may be used for scheduling, link adaptation, precoder selection, or beam management, among other things. Network node 110 may configure one or more SRS resource sets for UE 120, and UE 120 may transmit the SRS on the configured SRS resource sets. The SRS resource sets may have configured uses such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, and so on. Network node 110 may measure the SRS, perform channel estimation based at least in part on these measurement results, and use the SRS measurement results to configure communications with UE 120.

[0086] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0087] Figure 5 5 is a diagram illustrating an example 500 of a synchronization signal (SS) hierarchical structure according to the present disclosure. Figure 5As shown, the SS hierarchy may include an SS burst set 505, which may include multiple SS bursts 510 (shown as SS burst 0 through SS burst N-1, where N is the maximum number of repetitions of the SS burst 510 that may be sent by one or more network nodes). As further shown, each SS burst 510 may include one or more SSBs 515 (shown as SSB 0 through SSB M-1, where M is the maximum number of SSBs 515 that may be carried by the SS burst 510). In some aspects, different SSBs 515 may be beamformed in different manners (e.g., transmitted using different beams) and may be used for cell search, cell acquisition, beam management, and / or beam selection (e.g., as part of an initial network access procedure). The SS burst set 505 may be sent by a wireless node (e.g., network node 110) periodically (such as every X milliseconds), as shown. Figure 5 In some aspects, the SS burst set 505 may have a fixed or dynamic length (which may be Figure 5 In some cases, the SS burst set 505 or SS burst 510 may be referred to as a discovery reference signal (DRS) transmission window or an SSB measurement time configuration (SMTC) window.

[0088] In some aspects, an SSB 515 may include resources that carry a PSS 520, an SSS 525, and / or a PBCH 530. In some aspects, multiple SSBs 515 are included in an SS burst 510 (e.g., utilizing transmission on different beams), and the PSS 520, SSS 525, and / or PBCH 530 may be the same across each SSB 515 of an SS burst 510. In some aspects, a single SSB 515 may be included in an SS burst 510. In some aspects, an SSB 515 may be at least four symbols (e.g., OFDM symbols) in length, with each symbol carrying one or more of: a PSS 520 (e.g., occupying one symbol), an SSS 525 (e.g., occupying one symbol), and / or a PBCH 530 (e.g., occupying two symbols). In some aspects, an SSB 515 may be referred to as an SS / PBCH block.

[0089] In some aspects, the symbols of SSB 515 are continuous, such as Figure 5 . In some aspects, the symbols of the SSB 515 are non-contiguous. Similarly, in some aspects, one or more SSBs 515 of the SS burst 510 may be transmitted in contiguous radio resources (e.g., consecutive symbols) during one or more time slots. Additionally or alternatively, one or more SSBs 515 of the SS burst 510 may be transmitted in non-contiguous radio resources.

[0090] In some aspects, the SS burst 510 may have a burst periodicity, and the SSB 515 of the SS burst 510 may be transmitted by a wireless node (e.g., the network node 110) according to the burst periodicity. In this case, the SSB 515 may repeat during each SS burst 510. In some aspects, the SS burst set 505 may have a burst set periodicity, whereby the SS bursts 510 in the SS burst set 505 are transmitted by the wireless node according to a fixed burst set periodicity. In other words, the SS burst 510 may repeat during each SS burst set 505.

[0091] In some aspects, the SSB 515 may include an SSB index, which may correspond to a beam used to carry the SSB 515. The UE 120 may monitor and / or measure the SSB 515 using different receive (Rx) beams during an initial network access procedure and / or a cell search procedure, etc. Based at least in part on the monitoring and / or measurement, the UE 120 may indicate one or more SSBs 515 having the best signal parameters (e.g., RSRP parameters) to the network node 110 (e.g., directly or via one or more other network nodes). The network node 110 and the UE 120 may use the indicated one or more SSBs 515 to select one or more beams to be used for communication between the network node 110 and the UE 120 (e.g., for a random access channel (RACH) procedure). Additionally or alternatively, the UE 120 may use the SSB 515 and / or the SSB index to determine the cell timing of the cell (e.g., a serving cell) via which the SSB 515 is received.

[0092] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0093] Figure 6 is a diagram illustrating an example 600 associated with backscatter communications according to the present disclosure.

[0094] Some wireless communication devices may be considered IoT devices, such as ambient IoT devices (sometimes referred to as ultra-light IoT devices) or similar IoT devices. IoT technologies may include passive IoT (e.g., NR passive IoT for 5G Advanced), semi-passive IoT, ultra-light IoT, or ambient IoT, among others. In passive IoT, a terminal (e.g., a radio frequency identification (RFID) device, tag, or similar device) may not include a battery, and the terminal may accumulate energy from radio signaling. Additionally, the terminal may accumulate solar energy to supplement the accumulated energy from radio signaling. In passive IoT, the communication distance may be up to 30 meters (or longer) to facilitate feasible network coverage of large areas (e.g., 5,000 square meters) such as in a warehouse. In addition, the power consumption of a passive IoT terminal (e.g., UE) may be less than 0.1 milliwatts (mW) to support battery-free operation, and the terminal may be relatively inexpensive to facilitate cost-sensitive use. The positioning accuracy of a passive IoT terminal may be approximately 3 to 5 meters in both the horizontal and vertical directions.

[0095] Passive IoT may be useful in conjunction with industrial sensors for which battery replacement may be very difficult or undesirable (e.g., for safety monitoring or fault detection in smart factories, infrastructure, or environments). Additionally, features of passive IoT devices, such as low cost, small size, maintenance-free, durable, long life, etc., may facilitate smart logistics / warehousing (e.g., in conjunction with automated asset management by replacing RFID tags). Furthermore, passive IoT may be combined with smart home networks for household item management, wearable devices (e.g., wearable devices for medical monitoring where patients do not need battery replacement), and / or environmental monitoring. To achieve further cost reductions and zero-power communications, 5G+ / 6G wireless networks may utilize a type of passive IoT device known as an "ambient backscatter device" or "backscatter device."

[0096] like Figure 6As shown, a backscatter device 605 (e.g., a tag, sensor, etc.), which can be an example of a passive IoT device, can employ a simplified hardware design (e.g., including a power splitter, an energy harvester, and a microcontroller) that does not include a battery, such that the backscatter device 605 relies on energy harvesting for power, and does not include radio wave generation circuitry, such that the backscatter device 605 can transmit information solely by reflecting radio waves. More specifically, the backscatter device 605 communicates with a reader 608 (e.g., a UE 120, a network node 110, or another network device) by modulating a reflected radio signal from an RF source 610 (e.g., a network node 110, a UE 120, or another network device). In some aspects, the RF source 610 and the reader 608 can be the same device or can be co-located. For example, in some cases, the reader 608 and the RF source 610 can be associated with the same network node 110.

[0097] To facilitate communication with backscatter device 605, RF source 610 may transmit an energy harvesting wave to backscatter device 605. The energy harvesting wave may be transmitted for a sufficient duration to achieve a target range communication phase between reader 608 and backscatter device 605. Additionally or alternatively, in some cases, the range between RF source 610 and backscatter device 605 may be limited by a minimum received power, such as -20 decibel milliwatts (dBm), for triggering energy harvesting at backscatter device 605.

[0098] Once energy is sufficiently accumulated at the backscatter device 605, the backscatter device 605 may begin reflecting radio waves radiated onto the backscatter device 605 via the backscatter link 615. For example, the RF source 610 may initiate a communication session (sometimes referred to as a query-response communication) with a query, which may be a modulated envelope of a continuous wave (CW). The backscatter device 605 may respond by backscattering the CW. The communication session may include multiple rounds, such as for contention resolution purposes when multiple backscatter devices respond to the query. The channel between the RF source 610 and the backscatter device 605 of the backscatter link 615 may be aligned with a first backscatter link channel response value (sometimes referred to as a first backscatter link channel coefficient or a first backscatter link gain value) h. BDAs described below, backscatter device 605 may have reflection-on periods and reflection-off periods that follow a pattern based at least in part on the transmission of information bits by backscatter device 605. Reader 608 may detect the reflection pattern of backscatter device 605 and obtain backscatter communication information via backscatter link 615. The channel between reader 608 and backscatter device 605 of backscatter link 615 may be related to a second backscatter link channel response value (sometimes referred to as a second backscatter link channel coefficient or a second backscatter link channel gain value) h. DU Furthermore, the RF source 610 and the reader 608 may communicate (e.g., a reference signal and / or a data signal) via the direct link 620. The channel between the RF source 610 and the reader 608 of the direct link 620 may be associated with a direct link channel response value (sometimes referred to as a direct link channel coefficient or a direct link channel gain value) h BU associated.

[0099] The backscatter device 605 may use an information modulation scheme, such as amplitude shift keying (ASK) modulation or on-off keying (OOK) modulation. For ASK or OOK modulation, the backscatter device 605 may turn on reflection when transmitting an information bit "1" and turn off reflection when transmitting an information bit "0." In backscatter communication, the RF source 610 may transmit a specific radio wave (e.g., a reference signal or a data signal, such as a PDSCH), which may be represented as x(n). The reader 608 may receive the radio wave x(n) directly from the RF source 610 via a direct link 620, and receive the radio wave from the backscatter device 605, which modulates the radio wave and reflects it to the reader 608, via a backscatter link 615. The signal received at the reader 608 via the direct link 620 is represented as h BU (n)x(n), and indicated by reference numeral 625, is the radio wave x(n) transmitted by the RF source 610 multiplied by the direct link channel response value h BU The information bit signal of the backscatter device 605 can be represented as s(n), where s(n)∈{0,1}. Therefore, the signal received at the reader 608 via the backscatter link 615 (denoted as σ f h BD (n)h DU (n)s(n)x(n) and indicated by reference numeral 630) is the signal x(n) sent by the RF source 610 multiplied by the first backscatter link channel response value h BD , the second backscatter link channel response value h DU , the information bit signal s(n) from the backscatter device 605 and the reflection coefficient σ associated with the backscatter device 605 f plus any noise.

[0100] Therefore, the resulting signal received at the reader 608 is the superposition of the signal received via the direct link 620 and the signal received via the backscatter link 615 and can be expressed as y(n), where y(n) = (h Bu (n)+σ f h BD (n)h DU (n)s(n))x(n)+noise. This signal y(n) is shown by reference numeral 635. As shown, when s(n)=0 (indicated by reference numeral 640 in the graph shown at reference numeral 630), the backscatter device 605 can turn off the reflection so that the signal component σ f h BD (n)h DU (n)s(n) is equal to zero, and therefore the reader 608 receives only the direct link 620 signal (eg, y(n) = h BU (n) x (n) + noise). When s(n) = 1 (indicated by reference numeral 645 in the graph shown at reference numeral 630), the backscatter device 605 may turn on reflection so that the signal component σ f h BD (n)h DU (n)s(n) equals σ f h BD (n)h DU (n), and thus the reader 608 receives the superposition of both the direct link 620 signal and the backscatter link 615 signal (eg, y(n) = (h BU (n)+σ f h BD (n)h DU To receive the information bits sent by the backscatter device 605, the reader 608 may first treat the backscatter link 615 signal as interference based at least in part on the direct link channel response value h. BU (n) to decode x(n). The reader 608 can then decode x(n) by subtracting h from y(n). BU (n)x(n) to detect the signal component σ f h BD (n)h DU In some cases, backscatter device 605 may not maintain state from communication session to communication session, other than what is stored in backscatter device 605 memory, such as an Electronic Product Code (EPC) or similar information associated with backscatter device 605.

[0101] Some IoT devices may be referred to as semi-passive IoT devices because communication between the reader and the IoT device does not require an energy-harvesting waveform as a prerequisite. For example, a semi-passive IoT device may include a battery or similar energy source that can power the receiver and / or logic circuitry. For such devices, energy harvesting can still be triggered in some circumstances, such as for long-range communication. In such examples, the rectifier circuit of the IoT device may have a warm start from the battery or other energy source and may therefore be associated with a lower minimum receive power requirement than passive IoT devices (e.g., -30 dBm instead of -20 dBm). However, long-range communication may require battery power consumption to trigger each decode. More specifically, for long-range communications where the energy harvesting rate is lower than the decoding circuitry requirements, such as when the energy harvesting rate is lower than -30 dBm, a semi-passive IoT device may consume battery power to trigger each decode. Consequently, continuous IoT device monitoring (such as for the purpose of receiving long-range inquiry communications) may result in excessive battery drain at the IoT device.

[0102] In this regard, passive and semi-passive IoT devices may be inherently limited to certain applications. For example, passive IoT devices (such as backscatter device 605) may be associated with low cost and form factor because no RF chain is required at the IoT device. However, these devices require energy harvesting waveforms, thereby limiting the application of such passive IoT devices to short-range communications. Although semi-passive IoT devices may eliminate the need for energy harvesting waveforms and / or may enable long-range communications, such devices increase cost and complexity because these devices require the use of batteries or similar energy sources. Furthermore, because passive and semi-passive devices may be associated with communication sessions initiated by an RF source, these devices may be inherently limited to use in sensing scenarios or similar latency-critical applications that require non-periodic traffic, and these devices may not scale well for use in high IoT density applications.

[0103] In some cases, ambient IoT devices (sometimes referred to as ultra-light IoT devices) can be employed to overcome some of the shortcomings of passive and semi-passive IoT devices. Ambient IoT devices can be devices capable of sending uplink triggers, and thus, communication sessions can be initiated from the IoT device side. For example, ambient IoT devices may be associated with uplink transmissions that do not utilize PA (e.g., transmissions in the 0dBm to 5dBm range) and have limited transmission capabilities for such uplink transmissions, such as the ability to simply send a preamble to indicate uplink traffic. However, there remains a need to efficiently support synchronous operation of ambient IoT devices.

[0104] Some of the techniques and apparatus described herein enable a frame structure to support synchronous operation of ambient IoT devices. In some aspects, the frame structure may include resources associated with the PSS, SSS, PBCH, PDCCH / PDSCH, PUCCH / PUSCH and / or uplink trigger messages. For example, the frame structure may include resources associated with the uplink trigger message, which appear at a fixed relative position relative to the resources associated with the PSS. In this regard, the ambient IoT device or similar device may obtain network timing from the PSS and use the resources associated with the uplink trigger message to send an uplink trigger message to the network device, which may initiate a communication session between the ambient IoT device and the network device. Therefore, some of the techniques and apparatus described herein enable efficient synchronous operation of ambient IoT devices, thereby reducing power, computing and communication resource consumption associated with other IoT devices and / or enabling long-distance, high-density IoT device communications.

[0105] As indicated above, Figure 6 are provided as examples. Other examples may be used with respect to Figure 6 The examples described are different.

[0106] Figure 7 7 is a diagram of an example 700 associated with synchronization operations of ambient IoT devices according to the present disclosure. Figure 7 As shown, an ambient IoT device 705 (e.g., backscatter device 605, UE 120, or similar device) can communicate with a network device 710 (e.g., RF source 610, reader 608, network node 110, CU, DU, and / or RU). In some aspects, the ambient IoT device 705 and the network device 710 can be part of a wireless network (e.g., wireless network 100). The ambient IoT device 705 and the network device 710 can be part of a wireless network (e.g., wireless network 100). Figure 7 The illustrated operations have previously established a wireless connection, such as for the purpose of establishing a backscatter link 615 or similar link between the ambient IoT device 705 and the network device 710 .

[0107] As indicated by reference numeral 715, the network device 710 may transmit and the ambient IoT device 705 may receive synchronization or similar information. For example, the network device 710 may transmit a PSS, SSS, and / or information associated with the PBCH. More specifically, the ambient IoT device 705 may ultimately receive configuration information associated with resources used to transmit an uplink trigger message to the network device 710 (described in more detail below in conjunction with reference numeral 720), and the PSS, SSS, and / or PBCH may include timing information or other information for receiving the configuration information. For example, the ambient IoT device 705 may obtain the PSS from the network device 710 and, based at least in part on the timing information indicated by the PSS, receive configuration information indicating resources associated with the uplink trigger message. In some aspects, based at least in part on the timing information obtained from the PSS, the ambient IoT device may determine the location of resources associated with the PBCH, and the PBCH may indicate resources associated with a downlink channel that may include the configuration information. For example, the ambient IoT device 705 may obtain the PSS and, based at least in part on the PSS, determine when to receive the PBCH. The PBCH may, in turn, include information associated with certain system information (e.g., SIBs), and in some aspects, information associated with downlink channels (e.g., PDCCH and / or PDSCH) for use in obtaining configuration information. Thus, the ambient IoT device 705 may receive the PDCCH and / or PDSCH at a location indicated by the system information, which may include configuration information specific to the ambient IoT device 705.

[0108] More specifically, as indicated by reference numeral 720, the network device 710 may send and the ambient IoT device 705 may receive configuration information. In some aspects, the ambient IoT device 705 may receive the configuration information via one or more of RRC signaling, one or more MAC control elements (MAC-CEs), and / or DCI, etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for the ambient IoT device 705 to select (e.g., known to the ambient IoT device 705 and / or previously indicated by the network device 710 or other network devices) and / or explicit configuration information for the ambient IoT device 705 to use to configure the ambient IoT device 705, etc.

[0109] In some aspects, the configuration information may indicate resources associated with the uplink trigger message. For example, the configuration information may indicate Figure 77. An uplink (UL) trigger resource 725 is shown. The resources associated with the uplink trigger message (e.g., the UL trigger resource 725) can be associated with resources that the ambient IoT device 705 can use to initiate a communication session between the ambient IoT device 705 and the network device 710. In some aspects, the resources associated with the uplink trigger message can appear at a fixed location relative to another time slot and / or communication. For example, the resources associated with the uplink trigger message can appear at a fixed relative location relative to resources associated with the PSS, such that when the ambient IoT device 705 has data to send to the network device 710, the ambient IoT device 705 can trigger the communication session by locating the UL trigger resource 725 relative to a known (e.g., pre-configured) location of the PSS. In some aspects, the configuration information may indicate a specific frame structure that includes resources associated with the uplink trigger message and resources associated with other signals and / or messages (such as synchronization signals (e.g., PSS and / or SSS), broadcast and / or system messages (e.g., PBCH), downlink messages (e.g., PDCCH and / or PDSCH), uplink messages (e.g., PUCCH and / or PUSCH), or similar signals and / or messages) that are combined with Figure 8 The example frame structure shown is described in more detail.

[0110] The ambient IoT device 705 can configure itself based at least in part on the configuration information. In some aspects, the ambient IoT device 705 can be configured to perform one or more operations described herein based at least in part on the configuration information.

[0111] As shown at reference numeral 730, ambient IoT device 705 can determine that data is to be sent to network device 710. For example, ambient IoT device 705 can be associated with a sensor or similar application that can be configured to alert network device 710 when a reading satisfies a threshold. Thus, ambient IoT device 705 can determine that data is to be sent to network device 710 based at least in part on a sensor reading satisfying a threshold or similar condition.

[0112] In some aspects, when the ambient IoT device 705 determines that it wants to transmit data to the network device 710, the ambient IoT device 705 may utilize resources associated with the uplink trigger message (e.g., UL trigger resources 725) to send an uplink trigger message to the network device 710. The timing of the ambient IoT device 705 may be synchronized with the network device 710 because the UL trigger resource 725 may be provided at a fixed relative position relative to resources associated with the PSS or other messages, as described above in conjunction with 720. In other words, the timing of the ambient IoT device 705 may be synchronized with the network device 710 because the UL trigger resource 725 may be provided within a frame structure that fixes the relative position of the UL trigger resource 725 relative to other resources and / or signals (e.g., the PSS), as described below in conjunction with Figure 8 In this regard, the ambient IoT device 705 may be configured to send an uplink trigger message at a time when the network device 710 is listening for an uplink trigger message, thereby providing synchronized operation between the ambient IoT device 705 and the network device 710 .

[0113] In some aspects, the uplink trigger message may be associated with a backscatter communication, which may be associated with the above-described combined signal y(n) (represented by Figure 6 In such aspects, the ambient IoT device 705 may be configured to transmit in a manner similar to that described above in conjunction with the reference numeral 635 in FIG. Figure 6 In a similar manner as described, the energy harvesting and / or continuous wave is received from the network device 710, modulated with information bits, and the modulated wave is reflected back to the network device 710. In such aspects, as shown by reference numeral 735, the network device 710 can transmit an energy signal, and the ambient IoT device 705 can receive the energy signal, which can correspond to the radio wave transmitted by the RF source 610 described in conjunction with reference numeral 625. The network device 710 can be configured to periodically transmit the energy signal, such as during each instance of the UL trigger resource 725, so that if the ambient IoT device 705 needs to transmit an uplink trigger message, the ambient IoT device can harvest the energy signal and backscatter the uplink trigger message accordingly.

[0114] As shown by reference numeral 740, the ambient IoT device 705 may send and the network device 710 may receive an uplink trigger message. Figure 7As shown, the ambient IoT device 705 can use resources associated with the uplink trigger message (e.g., UL trigger resources 725) to send an uplink trigger message to the network device 710. The uplink trigger message can be a message sent to the network device 710 that indicates that the ambient IoT device 705 has data to send to the network device 710 and / or otherwise initiates a communication session between the ambient IoT device 705 and the network device 710. Furthermore, in aspects where the ambient IoT device 705 is a backscatter device (e.g., backscatter device 605) and / or where the uplink trigger message is associated with backscatter communication, the uplink trigger message can include a backscatter modulated information signal, similar to that generated by Figure 6 The signal y(n) is shown as reference numeral 635 in FIG.

[0115] In some aspects, the uplink trigger message can be used to initiate a broader communication session between the ambient IoT device 705 and the network device 710. For example, as shown by reference numeral 745, the ambient IoT device 705 can use the uplink trigger message to initiate a communication session in which sensor data or similar data is sent to the network device via a PUSCH or similar channel. In aspects where the ambient IoT device 705 is a backscatter device (e.g., backscatter device 605) and / or utilizes backscatter to communicate with the network device 710, the network device 710 can send multiple energy signals to the ambient IoT device 705 during the communication session, and the ambient IoT device 705 can combine the above Figure 6 The data is backscattered back to the network device 710 in a similar manner as described. In some aspects, a communication session may include multiple rounds, such as for contention resolution purposes when multiple backscatter devices respond to a query. Figure 8 Aspects of example frame structures that may be used to trigger a communication session between the ambient IoT device 705 and the network device 710 are described in further detail.

[0116] As indicated above, Figure 7 are provided as examples. Other examples may be used with respect to Figure 7 The examples described are different.

[0117] Figure 8 8 is a diagram illustrating an example frame structure 800 for synchronization operation of an ambient IoT device according to the present disclosure. The example frame structure 800 can be implemented to facilitate synchronization of an ambient IoT device with a network device (e.g., a reader) (such as the one described above in conjunction with Figure 7 The described environment IoT device 705 and network device 710) communicate with each other.

[0118] In some aspects, the example frame structure 800 may include resources associated with an uplink trigger message (e.g., the frame structure may support in-band uplink triggering) and resources associated with other types of signals and / or messages, such as resources associated with the PSS, SSS, PBCH, PDCCH, PDSCH, PUCCH, and / or PUSCH. In some aspects, the frame structure 800 may include multiple time slots, where one or more time slots are associated with UL trigger resources, PSS, SSS, PBCH, PDCCH, PDSCH, PUCCH, and / or PUSCH. Additionally or alternatively, the one or more time slots may be arranged relative to each other to minimize downlink / uplink switching points. For example, the frame structure 800 may include a PBCH slot 805, a set of one or more downlink slots 810 (shown as downlink slots 810-1 and 810-2) associated with resources associated with a PDCCH and / or PDSCH following the PBCH slot 805, a PSS slot 815 following the set of one or more downlink slots 810, a set of one or more uplink slots 820 (shown as uplink slots 820-1 to 820-5) associated with resources associated with a PUCCH and / or PUSCH following the PSS slot 815, a UL triggering slot 825 following the set of one or more uplink slots 820, and / or an SSS slot 830 following the UL triggering slot 825. This structure may reduce switching gaps provided in the frame structure, such as a switching gap provided between the PSS slot 815 and the first uplink slot 820-1. Additionally or alternatively, the frame structure 800 may also include a guard interval (GI), such as for the purpose of handling inter-symbol interference (ISI) in a multipath environment, which is described in more detail below.

[0119] In some aspects, certain channels may not be required and / or may otherwise be omitted from the frame structure 800. For example, in some aspects, the ambient IoT device 705 may not be configured to receive SSS and / or may otherwise not require SSS. Thus, in some aspects, resources associated with SSS (e.g., SSS slots 830) may be omitted from the frame structure 800. Additionally or alternatively, the specific mix of downlink slots 810 and uplink slots 820 may vary and / or may be indicated to the ambient IoT device 705, such as via a slot format indicator (SFI) indicating the location of the downlink slots 810 and uplink slots 820 within the frame structure 800. In some aspects, while the mix of downlink slots 810 and uplink slots 820 may vary via SF indication, the relative locations of other channels and / or resources (e.g., PBCH slots 805, PSS slots 815, UL trigger slots 825, and / or SSS slots 830) may be fixed.

[0120] In some aspects, the location of the UL trigger slot 825 can be fixed relative to the location of the PSS slot 815. This can permit the ambient IoT device 705 to send an uplink trigger message (e.g., the uplink trigger message described above in conjunction with reference numeral 740) after acquiring timing from the PSS. Additionally or alternatively, the interval between the PSS slot 815 and the UL trigger slot 825 can be of sufficient length to permit the ambient IoT device 705 to decode the PSS. In some aspects, as described above in conjunction with reference numerals 735 and 740, the uplink trigger message can be a backscatter message. Thus, the UL trigger slot 825 can be associated with a resource in which an energy wave and / or a continuous wave is transmitted by the network device 710 and / or a resource in which an uplink trigger message is transmitted by the ambient IoT device 705 by backscattering a continuous wave to the network device 710.

[0121] In some aspects, the duration of each time slot of the frame structure 800 (e.g., the PBCH time slot 805, the downlink time slot 810, the PSS time slot 815, the uplink time slot 820, the UL trigger time slot 825, and / or the SSS time slot 830) can be a multiple of 1 millisecond (ms), such as for the purpose of consistency with NR and / or another wireless communication standard (e.g., the duration of each time slot can be a multiple of 1 ms to meet the in-band / guard band requirements of NR and / or another wireless communication standard). In other words, in some aspects, the frame structure 800 can include a plurality of time slots, wherein the duration of each time slot of the plurality of time slots is equal to the product of an integer and 1 ms.

[0122] In some aspects, frame structure 800 may be associated with single-carrier operation and / or reduced modulation and / or coding compared to other wireless communication frame structures. For example, the frame structure may be associated with envelope tracking in the downlink (e.g., communications sent from network device 710 to ambient IoT device 705) and / or backscatter in the uplink (e.g., communications sent from ambient IoT device 705 to network device 710). Furthermore, in some aspects, frame structure 800 may be associated with relatively simple modulation, such as binary phase-shift keying (BPSK) and / or ASK. In such aspects, the number of bits that can be transmitted in a timeslot may therefore be limited. For example, a 1 ms timeslot with fourteen symbols associated with BPSK only permits fourteen information bits to be transmitted in the timeslot. This may be insufficient to convey certain types of information. For example, the DCI associated with NB-IoT has 23 bits plus a sixteen-bit cyclic redundancy check (CRC), which may be too large to be transmitted in a timeslot consisting of only fourteen symbols using BPSK or similar schemes.

[0123] Thus, the frame structure can be configured to increase the amount of bits that can be transmitted in each time slot. More specifically, the frame structure 800 can be associated with multiple symbols. For example, as shown by reference numeral 835, each time slot of the frame structure 800 (e.g., PBCH time slot 805, PSS time slot 815, UL trigger time slot 825, and / or SSS time slot 830) can be associated with multiple symbols, such as S1 to S2. m In some aspects, the symbol duration of the symbols associated with frame structure 800 can be reduced by a factor y compared to the duration of the symbols associated with a typical NR frame structure so that more symbols (and thus more information) can be included in a time slot. For example, in a typical NR frame structure in which each time slot is associated with fourteen symbols, the symbol duration can be equal to 1 ms divided by the subcarrier spacing (SCS) used for transmission. More specifically, for a 15 kilohertz (kHz) SCS, a typical symbol duration may be approximately 66.67 microseconds (μs) (e.g., 1 ms / 15,000); for a 30 kHz SCS, a typical symbol duration may be approximately 33.33 μs (e.g., 1 ms / 30,000); for a 60 kHz SCS, a typical symbol duration may be approximately 16.67 μs (e.g., 1 ms / 60,000); for a 120 kHz SCS, a typical symbol duration may be approximately 8.33 μs (e.g., 1 ms / 120,000); for a 240 kHz SCS, a typical symbol duration may be approximately 4.17 μs (e.g., 1 ms / 240,000); and so on. In some aspects, the symbols of the frame structure 800 may include each of these typical symbol durations further reduced by a factor y to permit more information bits to be sent in a time slot (e.g., the symbol durations for SCSs of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may be approximately 66.67 μs / y, 33.33 μs / y, 16.67 μs / y, 8.33 μs / y, and 4.17 μs / y, respectively). More generally, the duration of each of the plurality of symbols associated with the frame structure 800 may be equal to 1 ms divided by the product of the SCS used for transmission and an integer (e.g., y), where the integer is greater than one (e.g., symbol duration = 1 ms / (SCS × y), where y > 1).

[0124] As an example, in single-carrier operation in a 180 kHz bandwidth (e.g., a single physical resource block (PRB)), BPSK or double-sideband (DSB)-ASK modulation can potentially support a symbol duration of 1 / 180 ms (e.g., approximately 5.56 μs). Thus, for an SCS of 15 kHz, a factor of 12 (e.g., y=12) can be used. In this regard, up to 180 information bits can be sent in a 1 ms time slot (e.g., the frame structure 800 in this example can support a bit rate of 180 kilobits per second (kbps)). In some aspects, multiple channels can be implemented to increase the bit rate associated with the ambient IoT device 705 and / or the network device 710. For example, the ambient IoT device 705 can use multiple (e.g., 4) 180 kHz channels to increase the bit rate, such as to increase the bit rate to 720 kbps. In some aspects, the factor can be increased for other types of modulation. For example, in the above example (eg, 180 kHz bandwidth), single sideband (SSB)-ASK modulation may support an additional factor of 2.

[0125] In some aspects, such as when the ambient IoT device 705 is used in a multipath environment, the frame structure 800 may include a GI (e.g., the space between symbols being transmitted) to address ISI at the ambient IoT device 705. More specifically, the frame structure 800 may include space between symbol transmissions to reduce or eliminate ISI, which may otherwise be caused when echoes (e.g., reflections) from one symbol interfere with another symbol. In some aspects, the GI may be utilized to increase the time between symbol transmissions to allow echoes from one symbol to sufficiently decay before the next symbol is transmitted. In such aspects, the frame structure 800 may include a similar ratio to the GI found in NR and / or LTE frame structures (e.g., the GI comprises approximately 6.67% of the symbol duration). Returning to the above example of single-carrier operation in an 180 kHz bandwidth with a 15 kHz SCS, if a GI comprising approximately 6.67% of the symbol duration is employed, up to 168 information bits may be transmitted in a 1 ms slot when BPSK, DSB-ASK, or similar modulation is used (e.g., the supported bit rate may be approximately 168 kbps). In such an example, a single slot may be able to support multiple DCIs, EPC payloads (which may be equal to 96 bits plus overhead), or similar communications.

[0126] In some aspects, the frame structure 800 may be associated with an increased slot duration compared to a typical NR frame structure, such as for the purpose of increasing the number of information bits that can be sent in a single slot. For example, as described above, the frame structure 800 may include a plurality of slots (e.g., a PBCH slot 805, a PSS slot 815, a UL trigger slot 825, and / or an SSS slot 830), wherein the duration of each of the plurality of slots is equal to the product of an integer and 1 ms. In some cases, the integer may be greater than one (e.g., the slot duration may be equal to x×1 ms, where x=2, 3, 4, ...) in order to increase the slot duration and, therefore, the number of information bits that can be sent in each slot. Additionally or alternatively, the frame structure 800 may include a mixture of reduced symbol duration and longer slot duration compared to a typical NR frame structure. More specifically, the slot duration may be equal to a first integer greater than one (e.g., x) multiplied by 1 ms, and the symbol duration may be equal to 1 ms divided by the SCS used for transmission multiplied by a second integer greater than one (e.g., y).

[0127] In some aspects, the bit encoding associated with the frame structure 800 can be configured to support self-clocking at the ambient IoT device 705. For example, the frame structure can be associated with a self-coding scheme for downlink communications (e.g., communications transmitted by the network device 710 and received by the ambient IoT device 705). More specifically, certain backscatter devices and / or passive IoT devices can be associated with a pulse interval encoding (PIE) scheme that is associated with variable-length pulses and, therefore, may not be suitable for synchronous operation of the ambient IoT device 705 and / or for use with the frame structure 800 having a fixed time slot length. Accordingly, in some aspects, a Manchester encoding scheme, such as a Manchester L decoding scheme (sometimes referred to as a bi-phase L encoding scheme), can be used for downlink communications to achieve self-clocking at the ambient IoT device 705.

[0128] Additionally or alternatively, frame structure 800 may be associated with a coding scheme for uplink communications that may minimize interference from the network device 710's own continuous wave during decoding of uplink communications (e.g., backscatter messages). More specifically, during decoding of backscatter messages, the reader (e.g., network device 710) may filter the continuous wave generated by the RF source from the backscatter communications, as described above in conjunction with Figure 6As described. In some aspects, the frame structure 800 may be associated with an uplink coding scheme that minimizes interference caused by the continuous wave of the RF source and, therefore, simplifies filtering of the continuous wave during decoding of the backscatter message. For example, the frame structure 800 may be associated with one of a Miller coding scheme (sometimes referred to as a delay coding scheme) or an FMO coding scheme (sometimes referred to as a dual-phase space coding scheme). In some aspects, the frame structure 800 may be associated with multiple coding schemes. For example, downlink communications may be encoded using a Manchester coding scheme, and uplink communications (e.g., an uplink trigger message) may be encoded using a Miller coding scheme or an FMO coding scheme.

[0129] Based at least in part on the above Figure 7 and Figure 8 The described synchronous operation of the ambient IoT devices 705 and / or network devices 710 can conserve computational, power, network, and / or communication resources that would otherwise be consumed by operating in an asynchronous manner. For example, based at least in part on the asynchronous operation of the ambient IoT devices 705 and / or network devices 710, the ambient IoT devices 705 and / or network devices 710 can communicate with reduced error rates, which can conserve computational, power, network, and / or communication resources that would otherwise be consumed by detecting and / or correcting communication errors.

[0130] As indicated above, Figure 8 are provided as examples. Other examples may be used with respect to Figure 8 The examples described are different.

[0131] Figure 9 900 is a diagram illustrating an example process 900 performed, for example, by an ambient IoT device according to the present disclosure. The example process 900 is an example in which an ambient IoT device (eg, ambient IoT device 705) performs operations associated with a frame structure for synchronization operations of ambient IoT devices.

[0132] like Figure 9 As shown, in some aspects, process 900 may include receiving configuration information indicating resources associated with an uplink trigger message that initiates a communication session between an ambient IoT device and a network device (block 910). For example, an ambient IoT device (e.g., using Figure 11 The receiving component 1102 and / or the communication manager 1106 depicted in FIG may receive configuration information indicating resources associated with an uplink trigger message that initiates a communication session between an ambient IoT device and a network device, as described above.

[0133] like Figure 9As further shown in FIG. 1 , in some aspects, process 900 may include using resources associated with the uplink trigger message to send an uplink trigger message to a network device (block 920). For example, an ambient IoT device (e.g., using Figure 11 The sending component 1104 and / or the communication manager 1106 depicted in FIG may use resources associated with the uplink trigger message to send the uplink trigger message to the network device, as described above.

[0134] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0135] In a first aspect, process 900 includes obtaining a PSS from the network device, wherein receiving the configuration information indicating the resource associated with the uplink trigger message is based at least in part on timing information indicated by the PSS.

[0136] In a second aspect, alone or in combination with the first aspect, the resources associated with the uplink trigger message appear at a fixed relative position with respect to resources associated with a primary synchronization signal.

[0137] In a third aspect, alone or in combination with one or more of the first and second aspects, the uplink trigger message is sent by backscattering a continuous wave sent by the network device.

[0138] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the resource associated with the uplink trigger message is associated with a frame structure, and the frame structure also includes resources associated with at least one of the following: PSS, SSS, PBCH, PDCCH, PDSCH, PUCCH or PUSCH.

[0139] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the frame structure includes: a first time slot associated with resources associated with the PBCH, a second time slot associated with resources associated with the PSS, a third time slot associated with resources associated with the uplink trigger message, and a fourth time slot associated with resources associated with the SSS.

[0140] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the frame structure also includes: a first set of one or more time slots associated with resources associated with at least one of the PDCCH or the PDSCH, and a second set of one or more time slots associated with resources associated with at least one of the PUCCH or the PUSCH.

[0141] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, process 900 includes receiving a time slot format indicator indicating the position of the first set of one or more time slots and the second set of one or more time slots within the frame structure.

[0142] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the frame structure comprises a plurality of time slots, and a duration of each of the plurality of time slots is equal to a product of an integer and one millisecond.

[0143] In a ninth aspect, alone or in combination with one or more of aspects 1 to 8, the integer is greater than one.

[0144] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, the frame structure is associated with a plurality of symbols, each of the plurality of symbols having a duration equal to one millisecond divided by a product of a subcarrier spacing used for transmission and an integer greater than one.

[0145] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the frame structure is associated with a plurality of time slots and a plurality of symbols, the duration of each of the plurality of time slots being equal to the product of a first integer greater than one and one millisecond, and the duration of each of the plurality of symbols being equal to one millisecond divided by the product of a subcarrier spacing used for transmission and a second integer greater than one.

[0146] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the frame structure includes a guard interval between symbol transmissions associated with the frame structure.

[0147] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 900 includes receiving a downlink communication from the network device, wherein the downlink communication is encoded using a self-clock encoding scheme.

[0148] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the downlink communication is encoded using a Manchester coding scheme, and the uplink trigger message is encoded using one of a Miller coding scheme or an FMO coding scheme.

[0149] although Figure 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Figure 9 900. In some embodiments, the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 900 may be executed in parallel.

[0150] Figure 10 1 is a diagram illustrating an example process 1000 performed, for example, by a network device according to the present disclosure. Example process 1000 is an example in which a network device (e.g., network device 710) performs operations associated with a frame structure for synchronization operations of ambient IoT devices.

[0151] like Figure 10 As shown, in some aspects, process 1000 may include sending, to an ambient IoT device, configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and the network device (block 1010). For example, the network device (e.g., using Figure 12 The sending component 1204 and / or the communication manager 1206 depicted in FIG may send, to the ambient IoT device, configuration information indicating resources associated with an uplink trigger message that initiates a communication session between the ambient IoT device and the network device, as described above.

[0152] like Figure 10 As further shown, in some aspects, process 1000 may include: using the resource associated with the uplink trigger message to receive the uplink trigger message from the ambient IoT device (block 1020). For example, the network device (e.g., using Figure 12 The depicted receiving component 1202 and / or communication manager 1206) can receive the uplink trigger message from the ambient IoT device using the resource associated with the uplink trigger message, as described above.

[0153] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0154] In a first aspect, process 1000 includes sending a PSS to the ambient IoT device, wherein sending the configuration information indicating the resource associated with the uplink trigger message is based at least in part on timing information indicated by the PSS.

[0155] In a second aspect, alone or in combination with the first aspect, the resources associated with the uplink trigger message appear at a fixed relative position with respect to resources associated with a primary synchronization signal.

[0156] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes sending a continuous wave to the ambient IoT device, wherein the uplink trigger message is received via backscatter communication associated with the continuous wave.

[0157] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the resource associated with the uplink trigger message is associated with a frame structure, and the frame structure also includes resources associated with at least one of the following: PSS, SSS, PBCH, PDCCH, PDSCH, PUCCH or PUSCH.

[0158] In the fifth aspect, alone or in combination with one or more of the first to fourth aspects, the frame structure includes: a first time slot associated with resources associated with the PBCH, a second time slot associated with resources associated with the PSS, a third time slot associated with resources associated with the uplink trigger message, and a fourth time slot associated with resources associated with the SSS.

[0159] In the sixth aspect, alone or in combination with one or more of the first to fifth aspects, the frame structure also includes: a first set of one or more time slots associated with resources associated with at least one of the PDCCH or the PDSCH, and a second set of one or more time slots associated with resources associated with at least one of the PUCCH or the PUSCH.

[0160] In a seventh aspect, alone or in combination with one or more of aspects 1 to 6, process 1000 includes sending a time slot format indicator indicating the position of the first set of one or more time slots and the second set of one or more time slots within the frame structure.

[0161] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the frame structure comprises a plurality of time slots, and a duration of each of the plurality of time slots is equal to a product of an integer and one millisecond.

[0162] In a ninth aspect, alone or in combination with one or more of aspects 1 to 8, the integer is greater than one.

[0163] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, the frame structure is associated with a plurality of symbols, each of the plurality of symbols having a duration equal to one millisecond divided by a product of a subcarrier spacing used for transmission and an integer greater than one.

[0164] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the frame structure is associated with a plurality of time slots and a plurality of symbols, the duration of each of the plurality of time slots being equal to the product of a first integer greater than one and one millisecond, and the duration of each of the plurality of symbols being equal to one millisecond divided by the product of a subcarrier spacing used for transmission and a second integer greater than one.

[0165] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the frame structure includes a guard interval between symbol transmissions.

[0166] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 1000 includes sending a downlink communication to the ambient IoT device, wherein the downlink communication is encoded using a self-clock encoding scheme.

[0167] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the downlink communication is encoded using a Manchester coding scheme, and the uplink trigger message is encoded using one of a Miller coding scheme or an FMO coding scheme.

[0168] although Figure 10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Figure 10 1000. In some embodiments, the process 1000 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in FIG. Additionally or alternatively, two or more blocks of the blocks of process 1000 may be executed in parallel.

[0169] Figure 11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be an ambient IoT device (e.g., ambient IoT device 705), or an ambient IoT device may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102, a sending component 1104, and / or a communication manager 1106, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1106 is in conjunction with Figure 1 The depicted communication manager 140. As shown, the device 1100 can utilize a receiving component 1102 and a sending component 1104 to communicate with another device 1108, such as a UE or a network node such as a CU, DU, RU, or base station.

[0170] In some aspects, the apparatus 1100 may be configured to perform Figures 7 and 8 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more of the processes described herein, such as Figure 9 The process 900. In some aspects, Figure 11 The device 1100 and / or one or more components shown may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Figure 11 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0171] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1108. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include processing the received communications in conjunction with Figure 2 The depicted UE 120 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0172] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1108. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1108. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1108. In some aspects, the transmitting component 1104 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the depicted UE 120. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0173] The communications manager 1106 can support the operation of the receiving component 1102 and / or the sending component 1104. For example, the communications manager 1106 can receive information associated with configuring the receipt of communications by the receiving component 1102 and / or the sending of communications by the sending component 1104. Additionally or alternatively, the communications manager 1106 can generate and / or provide control information to the receiving component 1102 and / or the sending component 1104 to control the receipt and / or sending of communications.

[0174] The receiving component 1102 may receive configuration information indicating resources associated with an uplink trigger message that initiates a communication session between the ambient IoT device and the network device. The sending component 1104 may use the resources associated with the uplink trigger message to send the uplink trigger message to the network device.

[0175] The communications manager 1106 may obtain a PSS from the network device, wherein receiving the configuration information indicating the resource associated with the uplink trigger message is based at least in part on timing information indicated by the PSS.

[0176] Receiving component 1102 can receive a slot format indicator indicating a location of the first set of one or more time slots and the second set of one or more time slots within the frame structure.

[0177] Receiving component 1102 can receive downlink communications from the network device, wherein the downlink communications are encoded using a self-clock encoding scheme.

[0178] Figure 11 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 11 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 11 Two or more components shown may be implemented in a single component, or Figure 11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The illustrated set of components (one or more) may be described as being executable by Figure 11 Another group of components is shown performing one or more functions.

[0179] Figure 12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a network device (e.g., network device 710), or a network device may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202, a sending component 1204, and / or a communication manager 1206, which may communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1206 is a communication manager that is configured to communicate with one another. Figure 1 The described communication manager 150. As shown, the device 1200 can communicate with another device 1208, such as a UE or a network node (such as a CU, DU, RU, or base station), using a receiving component 1202 and a sending component 1204.

[0180] In some aspects, the apparatus 1200 may be configured to perform Figures 7 and 8 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein, such as Figure 10 The process 1000. In some aspects, Figure 12 The device 1200 and / or one or more components shown may include a combination of Figure 2 One or more components of the described network node 110. Additionally or alternatively, Figure 12 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code that are stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0181] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the device 1208. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include processing the received communications in conjunction with Figure 2 The depicted network node 110 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0182] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1208. In some aspects, one or more other components of the apparatus 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the apparatus 1208. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1208. In some aspects, the transmitting component 1204 may include in conjunction with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the depicted network node 110. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0183] The communications manager 1206 can support the operation of the receiving component 1202 and / or the sending component 1204. For example, the communications manager 1206 can receive information associated with configuring the receipt of communications by the receiving component 1202 and / or the sending of communications by the sending component 1204. Additionally or alternatively, the communications manager 1206 can generate and / or provide control information to the receiving component 1202 and / or the sending component 1204 to control the receipt and / or sending of communications.

[0184] The sending component 1204 can send configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the ambient IoT device and the network device to the ambient IoT device. The receiving component 1202 can receive the uplink trigger message from the ambient IoT device using the resources associated with the uplink trigger message.

[0185] The sending component 1204 can send a PSS to the ambient IoT device, wherein sending the configuration information indicating the resource associated with the uplink trigger message is based at least in part on timing information indicated by the PSS.

[0186] The transmitting component 1204 can transmit a continuous wave to the ambient IoT device, wherein the uplink trigger message is received via backscatter communication associated with the continuous wave.

[0187] Transmitting component 1204 can transmit a slot format indicator indicating a location of the first set of one or more time slots and the second set of one or more time slots within the frame structure.

[0188] The sending component 1204 can send a downlink communication to the ambient IoT device, wherein the downlink communication is encoded using a self-clock encoding scheme.

[0189] Figure 12 The number and arrangement of components shown are provided as examples. In practice, there may be Figure 12 The components shown may include additional components, fewer components, different components, or components arranged in a different manner than those shown. Figure 12 Two or more components shown may be implemented in a single component, or Figure 12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The illustrated set of components (one or more) may be described as being executable by Figure 12 Another group of components is shown performing one or more functions.

[0190] The following provides an overview of some aspects of the disclosure:

[0191] Aspect 1: A method for wireless communication performed by an ambient IoT device, the method comprising: receiving configuration information indicating resources associated with an uplink trigger message that initiates a communication session between the ambient IoT device and a network device; and using the resources associated with the uplink trigger message to send the uplink trigger message to the network device.

[0192] Aspect 2: The method according to aspect 1 further includes: obtaining a PSS from the network device, wherein receiving the configuration information indicating the resources associated with the uplink trigger message is at least partially based on timing information indicated by the PSS.

[0193] Aspect 3: The method according to any one of aspects 1 to 2, wherein the resources associated with the uplink trigger message appear at a fixed relative position with respect to the resources associated with the primary synchronization signal.

[0194] Aspect 4: The method according to any one of aspects 1 to 3, wherein the uplink trigger message is sent by backscattering a continuous wave sent by the network device.

[0195] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the resources associated with the uplink trigger message are associated with a frame structure, wherein the frame structure also includes resources associated with at least one of the following: PSS, SSS, PBCH, PDCCH, PDSCH, PUCCH or PUSCH.

[0196] Aspect 6: A method according to Aspect 5, wherein the frame structure includes: a first time slot associated with resources associated with the PBCH, a second time slot associated with resources associated with the PSS, a third time slot associated with resources associated with the uplink trigger message, and a fourth time slot associated with resources associated with the SSS.

[0197] Aspect 7: A method according to Aspect 6, wherein the frame structure further includes: a first set of one or more time slots associated with resources associated with at least one of the PDCCH or the PDSCH, and a second set of one or more time slots associated with resources associated with at least one of the PUCCH or the PUSCH.

[0198] Aspect 8: The method according to aspect 7, further comprising: receiving a slot format indicator indicating the positions of the first set of one or more time slots and the second set of one or more time slots within the frame structure.

[0199] Aspect 9: The method according to any one of aspects 5 to 8, wherein the frame structure comprises a plurality of time slots, and wherein the duration of each time slot in the plurality of time slots is equal to the product of an integer and one millisecond.

[0200] Aspect 10: The method of aspect 9, wherein the integer is greater than one.

[0201] Aspect 11: A method according to any one of Aspects 5 to 10, wherein the frame structure is associated with a plurality of symbols, wherein the duration of each of the plurality of symbols is equal to one millisecond divided by the product of the subcarrier spacing used for transmission and an integer, and wherein the integer is greater than one.

[0202] Aspect 12: A method according to any one of Aspects 5 to 11, wherein the frame structure is associated with a plurality of time slots and a plurality of symbols, wherein the duration of each of the plurality of time slots is equal to the product of a first integer greater than one and one millisecond, and wherein the duration of each of the plurality of symbols is equal to one millisecond divided by the product of a subcarrier spacing used for transmission and a second integer greater than one.

[0203] Aspect 13: The method according to any one of aspects 5 to 12, wherein the frame structure includes a guard interval between symbol transmissions associated with the frame structure.

[0204] Aspect 14: The method according to any one of aspects 1 to 13, further comprising: receiving downlink communications from the network device, wherein the downlink communications are encoded using a self-clock encoding scheme.

[0205] Aspect 15: The method of aspect 14, wherein the downlink communication is encoded using a Manchester coding scheme, and wherein the uplink trigger message is encoded using one of a Miller coding scheme or an FMO coding scheme.

[0206] Aspect 16: A method of wireless communication performed by a network device, the method comprising: sending configuration information indicating resources associated with an uplink trigger message for initiating a communication session between the environmental IoT device and the network device to an environmental IoT device; and receiving the uplink trigger message from the environmental IoT device using the resources associated with the uplink trigger message.

[0207] Aspect 17: The method according to Aspect 16 further includes: sending a PSS to the ambient IoT device, wherein sending the configuration information indicating the resources associated with the uplink trigger message is at least partially based on timing information indicated by the PSS.

[0208] Aspect 18: The method according to any one of aspects 16 to 17, wherein the resources associated with the uplink trigger message appear at a fixed relative position with respect to resources associated with a primary synchronization signal.

[0209] Aspect 19: The method according to any one of aspects 16 to 18, further comprising: sending a continuous wave to the ambient IoT device, wherein the uplink trigger message is received via backscatter communication associated with the continuous wave.

[0210] Aspect 20: A method according to any one of Aspects 16 to 19, wherein the resources associated with the uplink trigger message are associated with a frame structure, wherein the frame structure also includes resources associated with at least one of the following: PSS, SSS, PBCH, PDCCH, PDSCH, PUCCH or PUSCH.

[0211] Aspect 21: A method according to Aspect 20, wherein the frame structure includes: a first time slot associated with resources associated with the PBCH, a second time slot associated with resources associated with the PSS, a third time slot associated with resources associated with the uplink trigger message, and a fourth time slot associated with resources associated with the SSS.

[0212] Aspect 22: A method according to Aspect 21, wherein the frame structure further includes: a first set of one or more time slots associated with resources associated with at least one of the PDCCH or the PDSCH, and a second set of one or more time slots associated with resources associated with at least one of the PUCCH or the PUSCH.

[0213] Aspect 23: The method according to aspect 22, further comprising: sending a slot format indicator indicating the positions of the first set of one or more time slots and the second set of one or more time slots within the frame structure.

[0214] Aspect 24: The method of any one of aspects 20 to 23, wherein the frame structure comprises a plurality of time slots, and wherein the duration of each of the plurality of time slots is equal to the product of an integer and one millisecond.

[0215] Aspect 25: The method of aspect 24, wherein the integer is greater than one.

[0216] Aspect 26: A method according to any one of Aspects 20 to 25, wherein the frame structure is associated with a plurality of symbols, wherein the duration of each symbol in the plurality of symbols is equal to one millisecond divided by the product of the subcarrier spacing used for transmission and an integer, and wherein the integer is greater than one.

[0217] Aspect 27: A method according to any one of Aspects 20 to 26, wherein the frame structure is associated with a plurality of time slots and a plurality of symbols, wherein the duration of each of the plurality of time slots is equal to the product of a first integer greater than one and one millisecond, and wherein the duration of each of the plurality of symbols is equal to one millisecond divided by the product of a subcarrier spacing used for transmission and a second integer greater than one.

[0218] Aspect 28: The method of any one of aspects 20 to 27, wherein the frame structure includes a guard interval between symbol transmissions.

[0219] Aspect 29: The method according to any one of aspects 16 to 28, further comprising: sending downlink communications to the ambient IoT device, wherein the downlink communications are encoded using a self-clock encoding scheme.

[0220] Aspect 30: The method of aspect 29, wherein the downlink communication is encoded using a Manchester coding scheme, and wherein the uplink trigger message is encoded using one of a Miller coding scheme or an FMO coding scheme.

[0221] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 30.

[0222] Aspect 32: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 30.

[0223] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 30.

[0224] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 30.

[0225] Aspect 35: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 30.

[0226] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0227] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of different forms of hardware and / or hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, no reference is made herein to specific software code to describe the operation and behavior of the systems and / or methods, as those skilled in the art will appreciate that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0228] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0229] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features can be combined in ways that are not specifically described in the claims and / or disclosed in the specification. The disclosure of the various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items, including a single member. As an example, "at least one of a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other arrangement of a, b, and c).

[0230] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more projects and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "group" and "cluster" are intended to include one or more projects and can be used interchangeably with "one or more". If only want to refer to a project, then use the phrase "only one" or similar terms. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "at least partially based on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A method of wireless communication performed by an ambient Internet of Things (IoT) device, the method comprising: receiving configuration information indicating resources associated with an uplink trigger message initiating a communication session between the ambient IoT device and a network device; as well as The uplink trigger message is sent to the network device using the resources associated with the uplink trigger message.

2. The method according to claim 1, further comprising: A primary synchronization signal (PSS) is obtained from the network device, wherein receiving the configuration information indicating the resources associated with the uplink trigger message is based at least in part on timing information indicated by the PSS.

3. The method of claim 1 , wherein the resources associated with the uplink trigger message appear at a fixed relative position with respect to resources associated with a primary synchronization signal. 4 . The method according to claim 1 , wherein the uplink trigger message is sent by backscattering a continuous wave sent by the network device.

5. The method of claim 1 , wherein the resources associated with the uplink trigger message are associated with a frame structure, wherein the frame structure further comprises resources associated with at least one of: Primary Synchronization Signal (PSS), Secondary synchronization signal (SSS), Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), or Physical Uplink Shared Channel (PUSCH).

6. The method according to claim 5, wherein the frame structure comprises: a first time slot associated with resources associated with the PBCH, a second time slot associated with resources associated with said PSS, a third time slot associated with resources associated with the uplink trigger message, and A fourth time slot associated with resources associated with the SSS.

7. The method according to claim 6, wherein the frame structure further comprises: a first set of one or more time slots associated with resources associated with at least one of the PDCCH or the PDSCH, and A second set of one or more time slots associated with resources associated with at least one of the PUCCH or the PUSCH.

8. The method according to claim 7, further comprising: A slot format indicator is received that indicates a location of the first set of one or more time slots and the second set of one or more time slots within the frame structure.

9. The method of claim 5, wherein the frame structure comprises a plurality of time slots, and wherein the duration of each of the plurality of time slots is equal to a product of an integer and one millisecond.

10. The method of claim 9, wherein the integer is greater than one.

11. The method of claim 5, wherein the frame structure is associated with a plurality of symbols, wherein each of the plurality of symbols has a duration equal to one millisecond divided by a product of a subcarrier spacing used for transmission and an integer, and wherein the integer is greater than one.

12. The method of claim 5 , wherein the frame structure is associated with a plurality of time slots and a plurality of symbols, wherein a duration of each time slot in the plurality of time slots is equal to a product of a first integer greater than one and one millisecond, and wherein a duration of each symbol in the plurality of symbols is equal to one millisecond divided by a product of a subcarrier spacing used for transmission and a second integer greater than one.

13. The method of claim 5, wherein the frame structure includes a guard interval between symbol transmissions associated with the frame structure.

14. The method according to claim 1, further comprising: A downlink communication is received from the network device, wherein the downlink communication is encoded using a self-clock encoding scheme.

15. The method of claim 14, wherein the downlink communication is encoded using a Manchester coding scheme, and wherein the uplink trigger message is encoded using one of a Miller coding scheme or an FMO coding scheme.

16. A method of wireless communication performed by a network device, the method comprising: sending, to an ambient Internet of Things (IoT) device, configuration information indicating resources associated with an uplink trigger message initiating a communication session between the ambient IoT device and the network device; and The uplink trigger message is received from the ambient IoT device using the resource associated with the uplink trigger message.

17. The method according to claim 16, further comprising: A primary synchronization signal (PSS) is sent to the ambient IoT device, wherein sending the configuration information indicating the resources associated with the uplink trigger message is based at least in part on timing information indicated by the PSS.

18. The method of claim 16, wherein the resources associated with the uplink trigger message occur at a fixed relative position with respect to resources associated with a primary synchronization signal.

19. The method according to claim 16, further comprising: A continuous wave is transmitted to the ambient IoT device, wherein the uplink trigger message is received via backscatter communication associated with the continuous wave.

20. The method of claim 16, wherein the resources associated with the uplink trigger message are associated with a frame structure, wherein the frame structure further comprises resources associated with at least one of: Primary Synchronization Signal (PSS), Secondary synchronization signal (SSS), Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), or Physical Uplink Shared Channel (PUSCH).

21. The method of claim 20, wherein the frame structure comprises a plurality of time slots, and wherein the duration of each of the plurality of time slots is equal to a product of an integer and one millisecond.

22. The method of claim 21, wherein the integer is greater than one.

23. The method of claim 20, wherein the frame structure is associated with a plurality of symbols, wherein each symbol in the plurality of symbols has a duration equal to one millisecond divided by a product of a subcarrier spacing used for transmission and an integer, and wherein the integer is greater than one.

24. The method of claim 20, wherein the frame structure is associated with a plurality of time slots and a plurality of symbols, wherein a duration of each time slot in the plurality of time slots is equal to a product of a first integer greater than one and one millisecond, and wherein a duration of each symbol in the plurality of symbols is equal to one millisecond divided by a subcarrier spacing used for transmission and a second integer greater than one.

25. The method of claim 20, wherein the frame structure includes a guard interval between symbol transmissions.

26. An ambient Internet of Things (IoT) device for wireless communication, the ambient Internet of Things (IoT) device comprising: Memory; and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the ambient IoT device to: receiving configuration information indicating resources associated with an uplink trigger message initiating a communication session between the ambient IoT device and a network device; and The uplink trigger message is sent to the network device using the resources associated with the uplink trigger message.

27. An ambient IoT device according to claim 26, wherein the memory further comprises instructions executable by the one or more processors to cause the ambient IoT device to: obtain a primary synchronization signal (PSS) from the network device, wherein receiving the configuration information indicating the resources associated with the uplink trigger message is at least partially based on timing information indicated by the PSS.

28. The ambient IoT device of claim 26, wherein the resources associated with the uplink trigger message appear at a fixed relative position with respect to resources associated with a primary synchronization signal.

29. A network device for wireless communication, the network device comprising: Memory; and one or more processors coupled to the memory, the memory comprising instructions executable by the one or more processors to cause the network device to: sending, to an ambient Internet of Things (IoT) device, configuration information indicating resources associated with an uplink trigger message initiating a communication session between the ambient IoT device and the network device; and The uplink trigger message is received from the ambient IoT device using the resource associated with the uplink trigger message.

30. A network device according to claim 29, wherein the memory further includes instructions that are executable by the one or more processors to cause the network device to: send a primary synchronization signal (PSS) to the ambient IoT device, wherein the configuration information indicating the resources associated with the uplink trigger message is sent at least in part based on timing information indicated by the PSS.