Frequency hopping in an environmental internet of things system

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a reader can transmit information to a tag based at least in part on symbol level frequency hopping. The reader can receive feedback from the tag in response to the information, where the reader is a user equipment (UE) or a network node. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for frequency hopping in environmental Internet of Things (A-IoT) systems. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0004] In some specific implementations, an apparatus configured for wireless communication includes: one or more memories including processor-executable instructions; and one or more processors configured to execute the processor-executable instructions and cause the apparatus to: transmit information to a tag at least in part based on symbol-level frequency hopping; and receive feedback from the tag in response to the information, wherein the reader is a user equipment (UE) or a network node.

[0005] In some specific implementations, a method of wireless communication performed by a reader includes: transmitting information to a tag based at least in part on symbol-level frequency hopping; and receiving feedback from the tag in response to the information, wherein the reader is a UE or a network node.

[0006] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a reader, cause the reader to: transmit information to a tag at least in part based on symbol-level frequency hopping; and receive feedback from the tag in response to the information, wherein the reader is a UE or a network node.

[0007] In some specific implementations, an apparatus for wireless communication includes: components for transmitting information to a tag at least in part based on symbol-level frequency hopping; and components for receiving feedback from the tag in response to the information, wherein the reader is a UE or a network node.

[0008] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0009] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0010] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

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

[0012] Figure 2 This 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.

[0013] Figure 3This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0014] Figure 4 This is a diagram illustrating an example of RFID according to this disclosure.

[0015] Figure 5 This is a diagram illustrating an example of A-IoT according to this disclosure.

[0016] Figure 6A and Figure 6B This is a diagram illustrating an example of frequency hopping in A-IoT according to this disclosure.

[0017] Figure 7A and Figure 7B This is a diagram illustrating an example of frequency hopping in an A-IoT system according to the present disclosure.

[0018] Figure 8A and Figure 8B This is a diagram illustrating an example of frequency hopping in an A-IoT system according to the present disclosure.

[0019] Figure 9 This is a diagram illustrating an example of frequency hopping in an A-IoT system according to the present disclosure.

[0020] Figure 10 This is a diagram illustrating an example of frequency hopping in an A-IoT system according to the present disclosure.

[0021] Figure 11 This is a diagram illustrating an example process performed, for example, at a reader or a device of a reader, according to this disclosure.

[0022] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure.

[0023] Figure 13 The diagram illustrates an example of a specific implementation of the code and circuitry for a communication device according to this disclosure. Detailed Implementation

[0024] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using those other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0025] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0026] Frequency hopping allows a user equipment (UE) to perform transmissions using different frequencies. When performing transmissions to network nodes or other UEs, the UE can "hop" between frequencies. Frequency hopping provides flexibility for the UE when accessing spectrum resources. Frequency hopping can be associated with various triggering conditions. Frequency hopping can be triggered when a reader or radio frequency (RF) source discovers a nearby tag during initial access. Frequency hopping can be triggered by retransmissions (e.g., from an RF source or from a tag). Frequency hopping can be triggered when blind retransmission is enabled. Frequency hopping can also be triggered when the received (Rx) power in the reader or tag falls below a certain threshold.

[0027] Packet-level frequency hopping can be used to perform transmissions that hop between frequencies at the packet level. Compared to packet-level frequency hopping, symbol-level frequency hopping provides a more granular approach, but Ambient Internet of Things (A-IoT) systems may not be configured to support symbol-level frequency hopping.

[0028] Frequency hopping is involved in various aspects overall. Some aspects concern frequency hopping in A-IoT systems more specifically. In some examples, a reader may send information to a tag based at least in part on symbol-level frequency hopping. The reader may receive feedback from the tag in response to the information. The reader may be a UE or a network node.

[0029] In some examples, the UE may receive control signaling from a network node indicating frequency hopping information associated with the link between the UE and a tag associated with the same A-IoT system. The UE may send signals to the tag based at least in part on the frequency hopping information.

[0030] In some aspects, when the reader is a UE, the UE can receive control signaling indicating frequency hopping related information associated with the link between the UE and a tag associated with the same A-IoT system. The control signaling may be associated with Uu link A-IoT downlink control information (DCI), and the link may be an A-IoT link. Frequency hopping related information may indicate whether frequency hopping is enabled, and frequency hopping may be associated with frequency hopping for forward link (FL) data and / or frequency hopping for backscatter link (BL) data. Frequency hopping related information may indicate the time-domain granularity of frequency hopping. Frequency hopping related information may indicate the frequency hopping mode.

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by configuring the A-IoT system to support symbol-level or segment-level frequency hopping, readers and tags can use the described techniques to communicate with each other using frequency hopping. Frequency hopping at the symbol-level or segment-level can be associated with FL data, FL-CW, and / or BL data. Therefore, readers and tags can support frequency hopping at a relatively fine granular level (e.g., at the symbol level), thereby improving the overall performance of the A-IoT system.

[0032] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0033] As the demand for broadband access increases and as the technologies supported by wireless communication networks evolve, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT (A-IoT)) networks, redcap UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, RF sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0034] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or elements of a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0035] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0036] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0037] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0038] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0039] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations conforming to O-RAN Alliance standards), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0040] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0041] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0042] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell can be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0043] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Various types of network nodes 110 can typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100 compared to other types of network nodes 110. For example, macro network nodes can have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0044] In some examples, network node 110 may be, may include, or may operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. "Downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit DCI (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0045] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UE 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0046] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0047] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0048] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, or may be included in the following: access terminal, another terminal, mobile station, or subscriber unit. UE 120 may be, or may include, 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 smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0049] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0050] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may include, or may be included in, a housing that accommodates components associated with UE 120, including the processing system.

[0051] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0052] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, eMBB, and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR-Lite UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0053] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communication through a network node 110 acting as an intermediary). As an example, UE 120a can directly send data, control information, or other signaling to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0054] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0055] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0056] In some aspects, the reader (e.g., UE 120 or network node 110) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may transmit information to the tag at least in part based on symbol-level frequency hopping; and receive feedback from the tag in response to the information. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0058] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0059] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, and / or a scheduler 246, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in a transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, performs aspects of the methods, processes, and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0060] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “processor,” “controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0061] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be from the same set of processors or can be from different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0062] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0063] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T A set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the downlink signal set (e.g., ...) together via the corresponding set of antennas 234. T (One downlink signal).

[0064] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0065] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., Rx MIMO processor), and / or further processed by receiver processor 238 to obtain decoded data and / or control information. Receiver processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0066] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0067] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting between analog signals (such as those used for transmission or reception via an air interface) and digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0068] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0069] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0070] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and provide the decoded control information and system information to controller / processor 280.

[0071] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0072] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0073] Modems 254a to 254u can transmit uplink signal sets (e.g., via corresponding sets of antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0074] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0075] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit the cross-polarized signal. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0076] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0077] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

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

[0079] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0080] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be one or more network nodes (such as one or more network nodes 110), may include, or may be included in one or more network nodes. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more disaggregated control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, UE 120 can be served by multiple RU 340s simultaneously.

[0081] Each component in the components of the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0082] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. 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 RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0083] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0084] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0085] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may perform corrective actions using AI / ML models via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0086] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with frequency hopping in an A-IoT system or perform one or more operations associated with frequency hopping in an A-IoT system, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with frequency hopping in an A-IoT system or perform one or more operations associated with frequency hopping in an A-IoT system, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 11 The operation of process 1100 or other processes as described herein. In some aspects, the reader described herein is network node 110, is included in network node 110, or includes... Figure 2 One or more components of the network node shown. In some aspects, the reader described herein is UE 120, included in UE 120, or comprising Figure 2One or more components of the UE 120 shown. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, translation, or interpretation). Figure 11 The process 1100 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0087] In some aspects, the reader (e.g., UE 120 or network node 110) includes components for transmitting information to the tag at least in part based on symbol-level frequency hopping; and / or components for receiving feedback from the tag in response to the information. Components for the reader to perform the operations described herein may include one or more of, for example, a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0088] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0089] Different device types associated with A-IoT can include passive radios, semi-passive radios with energy harvesting and storage, or active radios with energy harvesting and storage. Passive radios can be associated with backscatter communication, no or very small energy storage, RF signals as the energy source, no Tx signal amplification, a range of approximately less than 13 meters to approximately 31 meters, device sensitivity of -20 dBm, power consumption in the microwatt (uW) range, low complexity, passive radio frequency identification (RFID), and interfaces supporting backscatter communication. Semi-passive radios with energy harvesting can be associated with backscatter communication, small energy storage, RF signals as the energy source, no / with Tx signal amplification, a range of approximately less than 22 meters to approximately 61 meters, device sensitivity of -35 dBm, power consumption in the range of 10 uW to 100 uW, medium complexity, semi-passive RFID, and interfaces supporting backscatter communication. Active radios with energy harvesting capabilities can communicate with Tx / Rx, have medium energy storage, use RF signals or solar energy as an energy source, amplify Tx signals, have a range of approximately less than 100 meters to approximately 300 meters, have device sensitivity of -35 / -100 dBm, have power consumption in the range of several hundred uW to 1 mW, have high complexity, active RFID / Bluetooth, and interfaces that support backscatter communication and minimal active communication.

[0090] Figure 4 This is an illustration of example 400 of RFID according to this disclosure.

[0091] like Figure 4 As shown, RFID can be associated with a reader and a tag. The reader can be associated with an antenna. The reader can transmit data to the tag via an FL (Flying Air). The tag can transmit data to the reader via a BL (Browser Air). The tag can be associated with a relatively simple structure, an envelope detector, and a carrier wave (CW) from the reader. The CW from the reader can be associated with electromagnetic (EM) strength, which can vary depending on whether the CW is transmitting data. The backscattered data from the tag can be associated with the EM strength.

[0092] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0093] Figure 5 This is an illustration of Example 500 of A-IoT according to this disclosure.

[0094] As shown by reference numeral 502, in the first zero-power (ZP) IoT scenario, the gNB can communicate with the tag. For example, the gNB can send downlink transmissions to the tag, and the tag can send uplink transmissions to the gNB. As shown by reference numeral 504, in the second ZP IoT scenario, the gNB can communicate with the UE (e.g., in the uplink and / or downlink directions). The UE can be a relay device. The UE can also be used as a reader. The UE can transmit data to the tag via the FL link. The tag can transmit data to the UE via the BL link. The UE-tag interface is not a sidelink interface. In this topology, a gNB-UE-tag configuration can be defined, where the UE can be used as a reader. The tag can be associated with energy harvesting and energy storage.

[0095] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0096] A unified air interface for A-IoT can be designed to enable a first device associated with a first device type. This first device can have a peak power consumption of approximately one uW, energy storage, and up to 1 / 10,000,000 of its capacity. X The initial sampling frequency offset (ppm) is associated with applications that are neither downlink nor uplink, where X These are predefined values. The uplink transmission of the first device can be backscattered on an externally provided carrier. The first device can be associated with 1uW.

[0097] A unified air interface for A-IoT can be designed to enable second devices associated with a second device type. The second device can have peak power consumption of less than or equal to several hundred µW, energy storage, and up to 10... X The initial sampling frequency offset in ppm is associated with both downlink and uplink amplification. The uplink transmission of the second device can be generated internally by the second device. The second device can be associated with 100uW.

[0098] A unified air interface for A-IoT can be designed to enable third devices associated with third device types. These third devices can have peak power consumption of less than or equal to several hundred µW, energy storage, and up to 10 µW. X The initial sampling frequency offset in ppm is associated with both downlink and uplink amplification. The uplink transmission of the third device can be backscattered on an externally provided carrier. The third device can be associated with 100uW.

[0099] Coverage design objectives may include a maximum distance of 10 to 50 meters for indoor devices. A unified air interface for A-IoT can be used in first and second topologies without RRC status, mobility (e.g., without cell selection / reselection related functions), hybrid automatic repeat request (HARQ), and automatic repeat request (ARQ) (e.g., UE as an intermediate node under network control).

[0100] Figure 6A and Figure 6B This is a diagram illustrating example 600 of frequency hopping in A-IoT according to the present disclosure.

[0101] like Figure 6A As shown by reference numeral 602 in the attached figure, in the first option, the FL and BL single-tone CW can hop together, depending on the RFID solution, packet level, and / or communication session level. Frequency hopping can be associated with a frequency hopping range, which can be in terms of frequency. Frequency hopping can be associated with frequency shift. Frequency hopping can occur over a period of time. Figure 6B As shown by reference numeral 604 in the attached diagram, in the second option, according to the A-IoT solution, FL groups may not change, and only BL monotone CW may change. Figure 6B As shown by reference numeral 606 in the attached figure, in the third option, BL data and BL retransmitted data may hop, while FL data and CW may not hop. In some cases (not shown), FL / BL CW may hop individually, or BL data may hop while FL packets and single-tone CW may not hop. Other options for frequency hopping in A-IoT may be based at least in part on the frequency hopping / non-hopping of FL packets and BL single-tone CW.

[0102] As indicated above, Figure 6A and Figure 6B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6A and Figure 6B The examples described are different.

[0103] Frequency hopping can be associated with various triggering conditions. Frequency hopping can be triggered when the reader / RF source detects a nearby tag during initial access (e.g., RFID-enabled). Frequency hopping can be triggered by retransmissions (e.g., from the RF source or from the tag) because FL / BL acknowledgments (ACK) or negative ACKs (NACKs) or other responses may be missing (e.g., missing for a certain period of time). Frequency hopping can be triggered when blind retransmission is enabled. Frequency hopping can be triggered when the Rx power in the reader or tag falls below a certain threshold. Frequency hopping can be triggered at least in part based on FL data, FL CW, and / or BL data.

[0104] Packet-level frequency hopping can be used to perform frequency hopping at the packet level. Compared to packet-level frequency hopping, symbol-level frequency hopping provides a finer-grained approach, but A-IoT systems may not be configured to support symbol-level frequency hopping. Additionally, the triggering conditions for frequency hopping should rely on error / missing decoding in the FL / BL, but this process may not be configurable for A-IoT systems.

[0105] Among the various aspects of the technologies and apparatus described herein, a reader may transmit information to a tag based at least in part on symbol-level frequency hopping. The reader may receive feedback from the tag in response to the information. The reader may be a UE or a network node.

[0106] In some examples, the UE may receive control signaling from a network node indicating frequency hopping information associated with the link between the UE and a tag associated with the same A-IoT system. The UE may send signals to the tag based at least in part on the frequency hopping information.

[0107] In some aspects, when the reader is a UE, the UE may receive control signaling indicating frequency hopping related information associated with the link between the UE and a tag associated with the same A-IoT system. The control signaling may be associated with the Uu link A-IoT DCI, and the link may be an A-IoT link. Frequency hopping related information may indicate whether frequency hopping is enabled, and frequency hopping may be associated with frequency hopping for FL data and / or frequency hopping for BL data. Frequency hopping related information may indicate the time-domain granularity of frequency hopping. Frequency hopping related information may indicate the frequency hopping mode.

[0108] In some respects, by configuring the A-IoT system to support symbol-level or segment-level frequency hopping, readers and tags can use frequency hopping to communicate with each other. Frequency hopping at the symbol or segment level can be associated with FL data, FL-CW, and / or BL data. Therefore, readers and tags can support frequency hopping at a relatively fine granular level (e.g., at the symbol level), thereby improving the overall performance of the A-IoT system.

[0109] Figure 7A This is a diagram illustrating example 700 associated with frequency hopping in an A-IoT system according to this disclosure. Figure 7A As shown, Example 700 includes communication between a reader (e.g., UE 120 or network node 110) and a tag (e.g., tag 122). In some aspects, the reader and tag may be included in a wireless network such as wireless network 100. The reader and tag may be associated with an A-IoT system.

[0110] As shown by reference numeral 702 in the attached figure, the reader can transmit information to the tag at least in part based on symbol-level frequency hopping. The reader can transmit information such that different symbols or chips of the information can be associated with different frequencies. In this case, the reader and tag in the A-IoT system can support symbol-level or chip-level frequency hopping.

[0111] In some aspects, the reader may be a UE. The reader may receive control signaling from a network node indicating frequency hopping related information associated with the link between the reader and the tag. The control signaling may be associated with a Uu link A-IoT DCI. The link may be an A-IoT link. Frequency hopping related information may indicate whether frequency hopping is enabled. Frequency hopping may be associated with frequency hopping for FL data and / or frequency hopping for BL data. Frequency hopping related information may indicate the frequency hopping time-domain granularity. Frequency hopping related information may indicate the frequency hopping mode. In some aspects, the reader may receive RRC signaling configuring frequency hopping from a network node, wherein the control signaling may enable or disable frequency hopping. In some aspects, the reader may determine whether to enable frequency hopping or a frequency hopping mode based at least in part on the allocation of broadband resources, wherein the control signaling may enable or disable frequency hopping. In some aspects, the reader may send signaling to the tag via a control channel indicating whether frequency hopping is enabled, the frequency hopping mode, or the frequency hopping time-domain granularity, wherein the control channel may be associated with FL or BL.

[0112] In some aspects, an A-IoT packet comprises one or more segments. The reader may insert a preamble or common sequence before each segment, where the preamble length may be configured by the reader or dynamically adjusted by the segment length. The reader may insert a preconfigured guard time between segments and symbols. In some aspects, an A-IoT packet may comprise multiple segments. A first portion of the multiple segments may be associated with frequency hopping, and a second portion of the multiple segments may not be associated with frequency hopping. Alternatively, the multiple segments may be associated with frequency hopping. A first portion of a segment may be associated with a control channel or a preamble, and a second portion of a segment may be associated with a data channel.

[0113] As shown by reference numeral 704 in the attached figure, the reader can receive feedback from the tag in response to the information. The feedback may include ACK to indicate that the tag has successfully received the information. The feedback may include NACK to indicate that the tag has not successfully received the information.

[0114] As indicated above, Figure 7A This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7A The examples described are different.

[0115] Figure 7B This is a diagram illustrating example 710 associated with frequency hopping in an A-IoT system according to this disclosure. Figure 7BAs shown, Example 710 includes communication between a UE (e.g., UE 120, such as a reader), a network node (e.g., network node 110), and a tag (e.g., tag 122). In some aspects, the UE, network node, and tag may be included in a wireless network such as wireless network 100. The UE and tag may be associated with an A-IoT system.

[0116] As shown by reference numeral 712 in the attached figure, the UE can receive a DCI from the network node indicating frequency hopping related information associated with the link between the UE and the tag. The DCI can be a Uu-link A-IoT DCI. The link can be an A-IoT link. The frequency hopping related information indicates whether frequency hopping is enabled. Frequency hopping can be associated with frequency hopping for FL data, frequency hopping for FL-CW, or frequency hopping for BL data. The frequency hopping related information can indicate the time-domain granularity of frequency hopping. The time-domain granularity of frequency hopping can be at the packet level, symbol level, or segment level. The frequency hopping related information can indicate the frequency hopping mode.

[0117] In some aspects, the UE may receive RRC signaling from the network node to configure frequency hopping. The DCI may enable or disable frequency hopping. In some aspects, the UE may determine whether to enable frequency hopping or a frequency hopping mode based at least in part on the allocation of broadband resources from the network node. The DCI may enable or disable frequency hopping. In some aspects, the UE may send signaling via a control channel to the tag indicating whether frequency hopping is enabled, the frequency hopping mode, and / or the time-domain granularity of frequency hopping, wherein the control channel may be associated with FL or BL.

[0118] In some aspects, an A-IoT packet may include one or more segments. The UE may insert a preamble or common sequence before each segment, where the preamble length may be configured by the UE or dynamically adjusted by the segment length. The UE may insert a preconfigured guard time between segments and symbols. In some aspects, an A-IoT packet may include multiple segments. A first portion of the multiple segments may be associated with frequency hopping, and a second portion of the multiple segments may not be associated with frequency hopping. The first portion may be associated with a control channel or a preamble, and the second portion may be associated with a data channel. Alternatively, multiple segments (e.g., all segments) may be associated with frequency hopping.

[0119] In some aspects, frequency hopping (FL) or frequency hopping (BL) can be triggered at least in part based on the absence of BL packets, and frequency hopping can be triggered only after BL packets are no longer missing. In some aspects, frequency hopping can be triggered at least in part based on decoding errors or absences of packets. Decoding errors or absences of packets can be at least in part based on observed packet error rate (PER), bit error rate (BER), or block error rate (BLER). Decoding errors or absences of packets can be at least in part based on a certain number of decoding errors or absences within a given time period. Decoding errors or absences of packets can be at least in part based on a certain number of consecutive decoding errors or absences. In some aspects, frequency hopping can be enabled or disabled at least in part based on the tag energy state and type of the tag.

[0120] In some aspects, DCI can be associated with link granting and uplink granting for a link, and uplink granting can be associated with providing feedback to network nodes. Feedback can be A-IoT feedback. A-IoT feedback can include ACK, NACK, A-IoT scheduling requests, A-IoT buffer status reports, A-IoT link commands, A-IoT link collision probabilities, and / or estimated tag counts.

[0121] As shown by reference numeral 714 in the attached figure, the UE may send signals to the tag based at least in part on frequency hopping related information. When frequency hopping related information indicates that frequency hopping is enabled, the signal may be communicated at least in part based on frequency hopping. The signal may be associated with FL data, FL-CW, or BL data. The signal may be associated with a frequency hopping mode. Frequency hopping may be at the packet level, symbol level, or segment level.

[0122] As indicated above, Figure 7B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7B The examples described are different.

[0123] Figure 8A and Figure 8B This is a diagram illustrating an example 800 associated with frequency hopping in an A-IoT system according to the present disclosure.

[0124] In some aspects, symbol / chip level or segment level frequency hopping can be supported in A-IoT links. IoT packets may include one or more segments. A segment may be associated with multiple symbols. A symbol may contain multiple chips. Symbol / chip level or segment level frequency hopping may be associated with FL packets, BL-CW, or BL data. A preamble (or common sequence) may be inserted before each segment, where the preamble may be generated by the A-IoT device (or reader). The preamble length may be configured or pre-configured by the reader and / or dynamically adjusted by the segment length, FL commands, and / or BL channels / resources. The preamble length and density may depend on the duration of the segment (e.g., shorter preambles can be used for shorter segments to reduce overhead). Different preamble settings can be defined, and different preamble settings can be pre-defined / pre-configured by the reader to the A-IoT device, or different preamble settings can be mapped to FL commands, FL packets, and / or BL channels / resources. Pre-configured protection times can be inserted between symbols or segments, where the protection time can be increased in the time domain.

[0125] like Figure 8A As shown in Figure 802, the symbol-level or segment-level FL in the BL-CW can be used to support frequency-domain phase difference of arrival (PDOA) distance measurement. The reader Tx can send FL packets. FL packets can be A-IoT packets. The reader Rx can receive the BL CW. The BL CW can be associated with multiple segments, and multiple segments can be associated with symbol-level / segment-level frequency hopping. The reader Rx can compare the phase difference in the Rx signal.

[0126] like Figure 8B As shown in Figure 804, the control channel or preamble can be associated with frequency hopping. The control channel or preamble can be associated with the first segment (S1). The data channel may not be associated with frequency hopping. The data channel can be associated with the second segment (S2). The first and second segments can be associated with A-IoT FL / BL packets. This approach can improve control channel / preamble coverage and detection probability with slightly increased overhead.

[0127] like Figure 8B As shown in Figure 806, multiple segments can be associated with frequency hopping. Instead of buffering and soft-combining the three BL frequency hopping segments (S1, S2, and S3) and decoding them, the reader can perform this process repeatedly, thus reducing the need for an Rx buffer in the reader. These three segments can be associated with A-IoT FL / BL packets. Furthermore, packet-level frequency hopping and symbol-level / segment-level frequency hopping can be combined.

[0128] As indicated above, Figure 8A and Figure 8B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8A and Figure 8BThe examples described are different.

[0129] In some aspects, in a second topology (e.g., the UE as a reader), a DCI such as a Uu link A-IoT DCI may include one or more bits to indicate frequency hopping in the A-IoT link. The DCI may be a new DCI or a reused legacy DCI (e.g., DCI 3.0). The DCI may be sent from a network node to the UE (e.g., the reader). The DCI may indicate whether frequency hopping is enabled. The DCI may indicate frequency hopping in FL data, FL-CW, or BL data. The DCI may indicate the temporal granularity of frequency hopping (e.g., packets, symbols, and / or segments). The temporal granularity of frequency hopping may be implicitly configured by the decoding rate. For example, a table configured or pre-configured to a tag may indicate the code rate and frequency hopping granularity. The DCI may indicate the frequency hopping mode. For example, the DCI may only indicate resources used for the first frequency hopping, and other frequency hopping may be implicitly indicated by the frequency hopping mode.

[0130] In some aspects, A-IoT frequency hopping modes can be configured via RRC signaling. DCI can be used to dynamically enable or disable A-IoT frequency hopping. In some aspects, network nodes can allocate bandwidth resources to the UE. The UE can determine whether to use frequency hopping and / or frequency hopping modes. DCI can be used to dynamically enable or disable A-IoT frequency hopping.

[0131] In some aspects, A-IoT link PHY control can be from UE to tag or from tag to UE. For the first or second topology, A-IoT link PHY control may include one or more bits to indicate frequency hopping in the A-IoT link. A-IoT link PHY control may indicate whether frequency hopping is enabled. A-IoT link PHY control may indicate the frequency hopping mode. A-IoT link PHY control may indicate the time-domain granularity of frequency hopping (e.g., packets, symbols, and / or segments). The PHY control channel may be associated with an FL link or a BL link.

[0132] Figure 9 This is a diagram illustrating example 900 associated with frequency hopping in an A-IoT system according to the present disclosure.

[0133] In some aspects, A-IoT frequency hopping can be triggered by decoding errors or missing packets. FL frequency hopping can be triggered, and / or BL-CW or BL data frequency hopping can be triggered. When a BL packet is missing, both FL and BL frequency hopping can be triggered accordingly. When a BL packet is detected, or when RSSI, RSRP, and / or RSRQ are greater than a threshold, in the case of a decoding error, only BL frequency hopping (e.g., BL-CW and / or BL data frequency hopping) can be triggered. Missing or decoding errors can extend to observed PER, BER, and / or BLER, or a certain number of missing or decoding errors within a given time period, or a certain number of consecutive missing or decoding errors.

[0134] In some respects, the tag's energy state (e.g., the amount of remaining energy) and / or type can be used to determine frequency hopping. The energy state should be greater than or less than a certain threshold. Different frequency hopping numbers or a maximum and minimum number of hops can be determined. Frequency hopping may or may not be associated with different energy states.

[0135] As shown by reference numeral 902 in the attached figure, the UE (reader) may receive BL packets, but BL packets may be associated with decoding errors. The tag (A-IoT device) may successfully receive FL packets. In this case, frequency hopping is not required. As shown by reference numeral 904 in the attached figure, the UE (reader) may not receive BL packets (e.g., BL packets may be missing). The tag (A-IoT device) may or may not receive FL packets. In this case, both FL and BL frequency hopping may be required.

[0136] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0137] Figure 10 This is a diagram illustrating an example 1000 associated with frequency hopping in an A-IoT system according to the present disclosure.

[0138] like Figure 10 As shown, for the second topology (e.g., the UE as a reader), uplink permission can be associated with A-IoT link permission to allow the UE (reader) to provide some kind of feedback to the gNB. The uplink permission can be a Uu uplink permission, which allows the UE to provide feedback to the gNB. The gNB can transmit an A-IoT DCI, which can be associated with both A-IoT link permission and uplink permission.

[0139] In some aspects, one or more bits can be used to indicate the associated time-frequency resources of the PUCCH (e.g., similar to sidelink DCI 3-0, PUCCH resource indicator, and PSFCH to HARQ feedback timing indicator). A-IoT feedback associated with the A-IoT DCI associated with the PUCCH can be ACK / NACK feedback or other feedback, such as A-IoT scheduling requests, A-IoT buffer status reports (BSRs), A-IoT link commands, A-IoT link collision probabilities, and / or estimated tag counts.

[0140] In some aspects, A-IoT feedback may differ from sidelink feedback. In sidelink, a NACK in DCI 3-0 associated with uplink Tx can be triggered by a sidelink Rx NACK or the absence of a NACK. In A-IoT, a NACK in A-IoT DCI associated with uplink Tx can be triggered by an A-IoT BL packet decoding error or absence in the A-IoT BL response packet. A sidelink Rx NACK can be the decoding result of a sidelink Tx packet. An A-IoT BL packet can be an Rx packet. In sidelink, an ACK in PUCCH associated with DCI 3-0 can be triggered by a sidelink Rx ACK (FL decoding successful). In A-IoT, an ACK in PUCCH associated with A-IoT DCI can be triggered by successful A-IoT BL packet decoding. The UE (reader) can not only report ACK / NACK but also indicate to the gNB whether a BL packet was detected.

[0141] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0142] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, at a reader or a device of a reader, according to this disclosure. Example process 1100 is an example in which a device or reader (e.g., UE 120 or network node 110) performs operations associated with frequency hopping in an A-IoT system.

[0143] like Figure 11 As shown, in some aspects, process 1100 may include sending information to the tag at least in part based on symbol-level frequency hopping (box 1110). For example, a reader (e.g., using...) Figure 12 The receiving component 1202 and / or communication manager 1206 depicted herein can transmit information to the tag at least in part based on symbol-level frequency hopping, as described above.

[0144] like Figure 11 As further shown, in some aspects, process 1100 may include receiving feedback from a tag in response to information, wherein the reader is a UE or a network node (box 1120). For example, the reader (e.g., using...) Figure 12 The receiving component 1202, transmitting component 1204, and / or communication manager 1206 depicted herein can receive feedback from the tag in response to information, wherein the reader is a UE or a network node, as described above.

[0145] Process 1100 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 in this document.

[0146] In the first aspect, the reader is a UE, and process 1100 includes receiving control signaling indicating frequency hopping information associated with the link between the UE and a tag associated with the A-IoT system.

[0147] In the second aspect, either alone or in combination with the first aspect, control signaling is associated with the Uu link A-IoT DCI, and the link is an A-IoT link.

[0148] In the third aspect, either alone or in combination with one or more of the first and second aspects, frequency hopping related information indicates whether frequency hopping is enabled, and frequency hopping is associated with one or more of the following: frequency hopping for FL data or frequency hopping for BL data.

[0149] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, frequency hopping related information indicates the time-domain granularity of frequency hopping.

[0150] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, frequency hopping related information indicates the frequency hopping mode.

[0151] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the reader is a UE, and the process 1100 includes receiving RRC signaling for configuring frequency hopping, wherein the control signaling enables or disables frequency hopping.

[0152] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the reader is a UE, and the process 1100 includes determining whether frequency hopping or frequency hopping mode is enabled based at least in part on the allocation of broadband resources, wherein control signaling enables or disables frequency hopping.

[0153] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the reader is a UE, and the process 1100 includes sending signaling via a control channel to the tag indicating one or more of the following: whether frequency hopping is enabled, frequency hopping mode, or frequency hopping time-domain granularity, wherein the control channel is associated with the FL or the backscatter link BL.

[0154] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the A-IoT packet includes one or more segments, and the aspect further includes inserting a preamble or common sequence before each segment, wherein the preamble length is configured by the reader or dynamically adjusted by the segment length.

[0155] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the A-IoT packet includes one or more segments, and the aspect also includes inserting a pre-configured protection time between the segments and symbols.

[0156] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the A-IoT packet includes multiple segments, wherein: a first portion of the multiple segments is associated with frequency hopping, and a second portion of the multiple segments is not associated with frequency hopping, or the multiple segments are associated with frequency hopping.

[0157] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the first part is associated with a control channel or a preamble, and the second part is associated with a data channel.

[0158] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, one or more of the FL frequency hopping or BL frequency hopping is triggered at least in part based on the absence of BL packets, and BL frequency hopping is triggered only after BL packets are no longer missing.

[0159] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, frequency hopping is triggered at least in part based on a decoding error or missing packet, and at least one of the following conditions exists: the decoding error or missing packet is at least in part based on the observed packet error rate, bit error rate, or block error rate; the decoding error or missing packet is at least in part based on the number of decoding errors or missing packets within a given time period; or the decoding error or missing packet is at least in part based on a certain number of consecutive decoding errors or missing packets.

[0160] In the fifteenth aspect, frequency hopping is enabled or disabled, either alone or in combination with one or more of the first to fourteenth aspects, based at least in part on the tag energy state and type of the tag.

[0161] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, the reader is a UE, the control signaling is associated with link granting and uplink granting for a link, and the uplink granting is associated with providing feedback.

[0162] In the seventeenth aspect, the feedback is A-IoT feedback, either alone or in combination with one or more of the first to sixteenth aspects, and the A-IoT feedback includes one or more of the following: acknowledgment, negative acknowledgment, A-IoT scheduling request, A-IoT buffer status report, A-IoT link command, A-IoT link collision probability, or estimated number of tags.

[0163] although Figure 11An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted herein are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1100 may be executed in parallel.

[0164] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a UE, or a UE may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can 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 combined with... Figure 1 The described communication manager 140. As shown, 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 receiving component 1202 and transmitting component 1204.

[0165] In some respects, device 1200 can be configured to perform the functions described herein in conjunction with Figure 7. Figure 8A , Figure 8B , Figure 9 and Figure 10 One or more operations as described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein (such as...). Figure 11 The process 1100) or a combination thereof. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0166] Receiver 1202 may receive communications from device 1208, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1200. In some aspects, receiver 1202 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0167] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, 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 device 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in one or more transceivers.

[0168] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the reception of communications by the receiving component 1202 and / or the transmission of communications by the transmitting component 1204. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the reception and / or transmission of communications.

[0169] The receiving component 1202 can transmit information to the tag at least in part based on symbol-level frequency hopping. The receiving component 1202 can receive feedback from the tag in response to the information.

[0170] Figure 12The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown is executable and described as being composed of Figure 12 Another set of components shown performs one or more functions.

[0171] Figure 13 This is a diagram illustrating an example of a specific implementation of the code and circuitry for a communication device 1300 according to this disclosure. The communication device 1300 may be a UE, or a UE may include the communication device 1300.

[0172] The communication device 1300 includes a processing system 1302 coupled to a transceiver 1308 (e.g., a transmitter and / or receiver, and which may include a single transceiver or multiple transceivers capable of performing various operations described herein). The transceiver 1308 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1300 via an antenna 1310. The processing system 1302 may be configured to perform processing functions for the communication device 1300, including processing signals received by the communication device 1300 and / or to be transmitted by the communication device.

[0173] Processing system 1302 includes one or more processors 1320. In various aspects, the one or more processors 1320 may include one or more of a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and / or a controller / processor 280, as per [reference to...]. Figure 2 As described. One or more processors 1320 are coupled to computer-readable medium / memory 1330 via bus 1306. In various aspects, computer-readable medium / memory 1330 may include one or more memories, such as memory 282, as described above. Figure 2 As described. In some aspects, the computer-readable medium / memory 1330 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by one or more processors 1320, cause one or more processors 1320 to perform actions related to... Figure 11The process 1100 described herein or any aspect thereof. It should be noted that references to a processor performing the functions of communication device 1300 may include one or more processors performing the functions of communication device 1300. It should also be noted that references to one or more processors performing multiple functions may include a first processor performing a first function among multiple functions and a second processor performing a second function among multiple functions.

[0174] like Figure 13 As shown, the communication device 1300 may include circuitry (circuit 1335) for transmitting information to tags, at least in part, based on symbol-level frequency hopping.

[0175] like Figure 13 As shown, the communication device 1300 may include code (code 1340) stored in a computer-readable medium / memory 1330 for transmitting information to a tag, at least in part based on symbol-level frequency hopping.

[0176] like Figure 13 As shown, the communication device 1300 may include circuitry (circuit 1345) for receiving feedback from the tag in response to information.

[0177] like Figure 13 As shown, the communication device 1300 may include code (code 1350) stored in a computer-readable medium / memory 1330 for receiving feedback from the tag in response to information.

[0178] The various components of the communication device 1300 can provide for performing tasks related to... Figure 11 The described process 1100 or any components related thereto. For example, components for transmitting, conveying, or outputting for transmission may include the transceiver 254 and / or antenna 252 of UE 120, and / or Figure 13 The communication device 1300 includes a transceiver 1308 and an antenna 1310. Components for receiving or acquiring data may include a transceiver 254 and / or an antenna 252 of the UE 120, and / or... Figure 13 The transceiver 1308 and antenna 1310 of the communication device 1300.

[0179] Figure 13 This is provided as an example. Other examples can be combined with it. Figure 13 The examples described are different.

[0180] The following provides an overview of some aspects of this disclosure:

[0181] Aspect 1: A method of wireless communication performed by a reader, the method comprising: transmitting information to a tag at least in part based on symbol-level frequency hopping; and receiving feedback from the tag in response to the information, wherein the reader is a user equipment (UE) or a network node.

[0182] Aspect 2: According to the method of aspect 1, wherein the reader is the UE, and the method further includes: receiving control signaling indicating frequency hopping related information associated with a link between the UE and a tag associated with an ambient Internet of Things (A-IoT) system.

[0183] Aspect 3: According to the method of aspect 2, wherein the control signaling is associated with Uu link A-IoT downlink control information (DCI), and the link is an A-IoT link.

[0184] Aspect 4: According to the method of aspect 2, wherein the frequency hopping related information indicates whether frequency hopping is enabled, and the frequency hopping is associated with one or more of the following: frequency hopping for forward link (FL) data or frequency hopping for backscatter link (BL) data.

[0185] Aspect 5: According to the method of aspect 2, wherein the frequency hopping related information indicates the frequency hopping time-domain granularity.

[0186] Aspect 6: According to the method of aspect 2, wherein the frequency hopping related information indicates the frequency hopping mode.

[0187] Aspect 7: The method according to aspect 2, wherein the reader is the UE, and the method further includes: receiving radio resource control (RRC) signaling for configuring frequency hopping, wherein the control signaling enables or disables the frequency hopping.

[0188] Aspect 8: The method according to aspect 2, wherein the reader is the UE, and the method further includes: determining whether to enable frequency hopping or frequency hopping mode based at least in part on the allocation of broadband resources, wherein the control signaling enables or disables the frequency hopping.

[0189] Aspect 9: The method according to Aspect 2, wherein the reader is the UE, the control signaling is associated with link grant and uplink grant for the link, and the uplink grant is associated with providing feedback.

[0190] Aspect 10: According to the method of aspect 9, the feedback is A-IoT feedback, and the A-IoT feedback includes one or more of the following: acknowledgment, negative acknowledgment, A-IoT scheduling request, A-IoT buffer status report, A-IoT link command, A-IoT link collision probability, or estimated number of tags.

[0191] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the reader is the UE, and the method further comprises: sending signaling to the tag via a control channel indicating one or more of the following: whether frequency hopping is enabled, frequency hopping mode, or frequency hopping time-domain granularity, wherein the control channel is associated with a forward link (FL) or a backscatter link (BL).

[0192] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the A-IoT packet comprises one or more segments, and the method further comprises: inserting a preamble or common sequence before each segment, wherein the preamble length is configured by the reader or dynamically adjusted by the segment length.

[0193] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the A-IoT packet comprises one or more segments, and the method further comprises: inserting a pre-configured protection time between the segments and symbols.

[0194] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the A-IoT packet includes a plurality of segments, wherein a first portion of the plurality of segments is associated with frequency hopping, and a second portion of the plurality of segments is not associated with frequency hopping, or the plurality of segments are associated with frequency hopping.

[0195] Aspect 15: The method according to aspect 14, wherein the first portion is associated with a control channel or a preamble, and the second portion is associated with a data channel.

[0196] Aspect 16: The method according to any one of Aspects 1 to 15, wherein one or more of forward link (FL) frequency hopping or backscatter link (BL) frequency hopping is triggered at least in part based on the absence of BL packets, and only the BL frequency hopping is triggered after the BL packets are no longer missing.

[0197] Aspect 17: The method according to any one of Aspects 1 to 16, wherein frequency hopping is triggered at least in part based on a decoding error or missing packet, and at least one of the following conditions exists: the decoding error or missing packet is at least in part based on an observed packet error rate, bit error rate, or block error rate; the decoding error or missing packet is at least in part based on a certain number of decoding errors or missing packets within a given time period; or the decoding error or missing packet is at least in part based on a certain number of consecutive decoding errors or missing packets.

[0198] Aspect 18: The method according to any one of Aspects 1 to 17, wherein frequency hopping is enabled or disabled at least in part based on the tag energy state and type of the tag.

[0199] Aspect 19: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 18.

[0200] Aspect 20: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 18.

[0201] Aspect 21: 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 18.

[0202] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 18.

[0203] Aspect 23: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 18.

[0204] Aspect 24: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 18.

[0205] Aspect 25: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 18.

[0206] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0207] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0208] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0209] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: 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 of the same element (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 ordering of a, b, and c).

[0210] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0211] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and One or more processors, the one or more processors being configured to execute processor-executable instructions and cause the device to: Information is sent to tags, at least in part, based on symbol-level frequency hopping; as well as The device receives feedback in response to the information from the tag, wherein the device is associated with a reader, and the reader is a user equipment (UE) or a network node.

2. The apparatus of claim 1, wherein the reader is the UE, and the one or more processors configured to execute processor-executable instructions cause the apparatus to: Receive control signaling indicating frequency hopping information associated with the link between the UE and a tag associated with the Internet of Things in the same environment (A-IoT) system.

3. The apparatus of claim 2, wherein the control signaling is associated with Uu link A-IoT downlink control information (DCI), and the link is an A-IoT link.

4. The apparatus of claim 2, wherein the frequency hopping related information indicates whether frequency hopping is enabled, and the frequency hopping is associated with one or more of the following: frequency hopping for forward link (FL) data or frequency hopping for backscatter link (BL) data.

5. The apparatus of claim 2, wherein the frequency hopping related information indicates the frequency hopping time-domain granularity.

6. The apparatus of claim 2, wherein the frequency hopping related information indicates a frequency hopping mode.

7. The apparatus of claim 2, wherein the reader is the UE, and the one or more processors configured to execute processor-executable instructions cause the apparatus to: Receive radio resource control (RRC) signaling to configure frequency hopping, wherein the control signaling enables or disables the frequency hopping.

8. The apparatus of claim 2, wherein the reader is the UE, and the one or more processors configured to execute processor-executable instructions cause the apparatus to: Whether to enable frequency hopping or frequency hopping mode is determined at least in part based on the allocation of broadband resources, wherein the control signaling enables or disables the frequency hopping.

9. The apparatus of claim 2, wherein the reader is the UE, the control signaling is associated with link grant and uplink grant for the link, and the uplink grant is associated with providing feedback.

10. The apparatus of claim 9, wherein the feedback is A-IoT feedback, and the A-IoT feedback includes one or more of the following: acknowledgment, negative acknowledgment, A-IoT scheduling request, A-IoT buffer status report, A-IoT link command, A-IoT link collision probability, or estimated number of tags.

11. The apparatus of claim 1, wherein the reader is the UE, and the one or more processors configured to execute processor-executable instructions cause the apparatus to: The control channel sends a signal to the tag indicating one or more of the following: whether frequency hopping is enabled, frequency hopping mode, or frequency hopping time-domain granularity, wherein the control channel is associated with a forward link (FL) or a backscatter link (BL).

12. The apparatus of claim 1, wherein the A-IoT packet comprises one or more segments, and the one or more processors configured to execute processor-executable instructions cause the apparatus to: A preamble or common sequence is inserted before each segment, wherein the length of the preamble is configured by the reader or dynamically adjusted by the segment length.

13. The apparatus of claim 1, wherein the A-IoT packet comprises one or more segments, and the one or more processors configured to execute processor-executable instructions cause the apparatus to: Insert pre-configured protection time between segments and symbols.

14. The apparatus of claim 1, wherein the A-IoT packet comprises a plurality of segments, wherein: The first portion of the plurality of segments is associated with frequency hopping, and the second portion of the plurality of segments is not associated with frequency hopping, or The multiple segments are associated with frequency hopping.

15. The apparatus of claim 14, wherein the first portion is associated with a control channel or a preamble, and the second portion is associated with a data channel.

16. The apparatus of claim 1, wherein one or more of the forward link (FL) frequency hopping or backscatter link (BL) frequency hopping are triggered at least in part based on the absence of BL packets, and the BL frequency hopping is triggered only after the BL packets are no longer missing.

17. The apparatus of claim 1, wherein frequency hopping is triggered at least in part based on a decoding error or missing packet, and at least one of the following conditions exists: The decoding error or the missing data in the group is based at least in part on the observed group error rate, bit error rate or block error rate; The decoding errors or omissions in the group are at least partially based on a certain number of decoding errors or omissions within a given time period; or The decoding errors or omissions in the group are at least in part based on a certain number of consecutive decoding errors or omissions.

18. The apparatus of claim 1, wherein frequency hopping is enabled or disabled at least in part based on the tag energy state and type of the tag.

19. A method for wireless communication performed by a reader, the method comprising: Information is sent to tags, at least in part, based on symbol-level frequency hopping; as well as The reader receives feedback in response to the information from the tag, wherein the reader is a user equipment (UE) or a network node.

20. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions, which, when executed by one or more processors of the reader, cause the reader to: Information is sent to tags, at least in part, based on symbol-level frequency hopping; as well as The reader receives feedback in response to the information from the tag, wherein the reader is a user equipment (UE) or a network node.

Images