Backward link coding configuration for environmental internet of things devices

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first wireless device can obtain a signal to be transmitted on a backhaul link to a second wireless device. The first wireless device can encode the signal to be transmitted to the second wireless device using one or more of line coding or channel coding based at least in part on a channel or resource associated with the signal to be transmitted to the second wireless device. The first wireless device can transmit the encoded signal to the second wireless device on the backhaul link. 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 backlink decoding configuration of Ambient Internet of Things (AIoT) devices. 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] Some aspects described herein relate to a method of wireless communication performed by a first wireless device. The method may include obtaining a signal to be transmitted to a second wireless device over a backward link. The method may include encoding the signal to be transmitted to the second wireless device using one or more of line decoding or channel decoding, based at least in part on a channel or resources associated with the signal to be transmitted to the second wireless device. The method may include transmitting the encoded signal to the second wireless device over the backward link.

[0005] Some aspects described herein relate to a first wireless device for wireless communication. The first wireless device may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to acquire a signal to be transmitted to a second wireless device over a backward link. The one or more processors may be configured to encode the signal to be transmitted to the second wireless device, at least in part, based on a channel or resources associated with the signal to be transmitted to the second wireless device, using one or more of line decoding or channel decoding. The one or more processors may be configured to transmit the encoded signal to the second wireless device over the backward link.

[0006] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first wireless device. When executed by one or more processors of the first wireless device, the set of instructions enables the first wireless device to: obtain a signal to be transmitted to a second wireless device over a backward link; encode the signal to be transmitted to the second wireless device, at least in part, based on a channel or resources associated with the signal to be transmitted to the second wireless device, using one or more of line decoding or channel decoding; and transmit the encoded signal to the second wireless device over the backward link.

[0007] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for obtaining a signal to be transmitted to a wireless device over a backlink. The apparatus may include components for encoding the signal to be transmitted to the wireless device, at least in part, based on a channel or resources associated with the signal to be transmitted to the wireless device, using one or more of line decoding or channel decoding. The apparatus may include components for transmitting the encoded signal to the wireless device over the backlink.

[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 communication between an example network node and a user equipment (UE) in a wireless network according to the present disclosure.

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

[0014] Figure 4 This is an illustration of an example of an environmental Internet of Things (AIoT) device that can use backscatter communication and / or energy harvesting, according to the present disclosure.

[0015] Figure 5 This is a diagram illustrating examples of the line decoding technology according to this disclosure and different types of AIoT devices.

[0016] Figures 6A to 6B This is a diagram illustrating an example of a backward link decoding configuration associated with an AIoT device according to this disclosure.

[0017] Figure 7 This is a flowchart illustrating an example process performed, for example, by a first wireless device, according to this disclosure.

[0018] Figure 8This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0019] 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 protection 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 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 practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0020] 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.

[0021] As described in this article, Ambient Internet of Things (AIoT) devices are intelligent devices that operate in the background, seamlessly integrating with the environment to collect data, provide information, or perform specific tasks to enable continuous, context-aware services without requiring direct human-machine interaction. AIoT devices are typically equipped with sensors to collect data from the environment, such as temperature, humidity, light, motion, or sound, and can communicate with other devices or systems to process the collected data and take appropriate actions. For example, AIoT devices may include smart thermostats that automatically adjust temperature, ambient lighting systems that regulate lighting in a room, and / or environmental monitoring devices. Compared to Internet of Things (IoT) devices from previous generations of IoT technologies, such as Narrowband IoT (NB-IoT) devices, Long Term Evolution for Machines (LTE) (LTE-M), and Reduced Capability (RedCap) devices, AIoT devices are generally much smaller and cheaper to manufacture.

[0022] Therefore, AIoT devices typically operate using technologies similar to passive radio frequency identification (RFID) systems, such as energy harvesting and backscatter communication. For example, energy harvesting involves techniques for collecting ambient energy from the surrounding environment and converting it into electrical power that can be used to operate the AIoT device (e.g., without batteries or other energy storage capabilities). In this way, energy harvesting eliminates the need to replace the AIoT device's battery or repeatedly charge it, making AIoT devices more sustainable and reducing maintenance. Furthermore, backscattering is a communication technique that AIoT devices can use to transmit data without consuming significant power and / or having independent carrier signal generation capabilities. For example, instead of generating a carrier signal to send to another device (e.g., a reader device), the AIoT device performing backscattering reflects or modifies existing signals from nearby sources (e.g., signals transmitted by nearby wireless local area network (WLAN) devices, RFID readers, or cell towers) to encode and transmit information, significantly reducing energy consumption compared to traditional active transmission. In this way, by combining energy harvesting with backscattering, AIoT devices can operate with minimal power requirements, which allows them to operate in remote or hard-to-reach locations without regular maintenance.

[0023] However, a challenge posed by backscatter communication in AIoT devices is that devices lacking independent carrier signal generation capabilities may exhibit low clock accuracy and / or low complexity. Therefore, when an AIoT device uses backscatter to transmit signals to a reader device on the backlink, it can use line decoding to encode the signal to assist the reader device in detecting clock errors and / or locating symbol boundaries. For example, line codes (e.g., associated with FM0 line decoding schemes, Miller line decoding schemes, or another suitable scheme) typically have high-level and low-level transitions in each information bit to help the reader device detect clock errors and locate symbol boundaries. In some respects, line decoding is considered not a decoding scheme, but rather falls within the scope of modulation, decode-modulation, or waveform. However, some AIoT device types may have more advanced capabilities, such as energy storage capabilities and / or active radio frequency (RF) components supporting transmission. In such cases, using line decoding may be less necessary, as AIoT devices with active RF components can have more accurate clocks. However, because of the various common channels and / or resources available for backlink transmission, reader devices can receive signals encoded using line codes from AIoT devices performing backscatter communication, and uncoded signals from AIoT devices with active carrier signal generation capabilities. In such cases, the reader device may have to perform blind detection to decode the corresponding signals, which adds complexity.

[0024] Various aspects as a whole relate to backlink decoding configuration for AIoT devices. Some aspects relate more specifically to backlink decoding configurations that AIoT devices can use to encode signals to be transmitted on the backlink to reader devices (e.g., network nodes, user equipment (UEs), integrated access and backhaul (IAB) nodes, smart repeaters, etc.), depending on the channel and / or resources associated with the signal and the device type associated with the AIoT device. For example, as described herein, an AIoT device may be associated with a first device type (e.g., device type A) or a second device type (e.g., device type B) that uses backscattering techniques to transmit signals on the backlink, or an AIoT device may be associated with a third device type (e.g., device type C) that has active RF components for transmission on the backlink. Therefore, AIoT devices associated with the first or second device type (which rely on backscattering) may typically require line decoding to encode signals to be transmitted on the backward link to help the reader detect clock errors and locate symbol boundaries, while AIoT devices associated with the third device type may use channel decoding to encode signals to improve communication range and / or reliability.

[0025] However, there may be situations where AIoT devices associated with a third device type should use line decoding to encode signals to reduce the complexity of the reader device and avoid performing blind detection on the reader device to distinguish line-decoded signals sent by AIoT devices with a first or second device type from uncoded signals sent by AIoT devices with a third device type. Therefore, in some aspects, when an AIoT device is transmitting a signal on a backlink channel or resource that is common to all AIoT device types, the signal can be encoded using line decoding regardless of the device type, and the channel decoder can be optionally configured. Furthermore, when an AIoT device with a first or second device type is transmitting a signal on a backlink channel or resource dedicated to an AIoT device associated with a first or second device type (e.g., using backscattering techniques), the signal can be encoded using line decoding, and the channel decoder can be optionally configured. Alternatively, when an AIoT device of a third device type is dedicated to transmitting signals on a backward link channel or resource associated with the AIoT device of the third device type (e.g., using an active RF component), the signal can be encoded using channel decoding, and the line decoder can be optionally configured. Some aspects described herein also relate to techniques for configuring backward link line decoding and channel decoding options and configurations for AIoT devices based on message type (e.g., whether the signal is a response to a query from a reader device or is transmitted using a resource pool configured by the reader device), and techniques for enabling or disabling backward link decoding for AIoT devices of a third device type based on whether the signal is an in-access signal transmitted during the access process or a post-access signal transmitted after the access process is completed.

[0026] 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 backlink decoding applied by an AIoT that transmits signals in the backward direction (e.g., actively or using backscatter) according to the channel and / or resources associated with the transmission capability of the AIoT device and the device type, a uniform design and compatibility for AIoT devices with different capabilities can be achieved. Furthermore, by employing a similar decoding scheme or configuration when the AIoT device is transmitting signals using channels and / or resources that are common to all AIoT device types, the complexity at the reader device can be reduced by avoiding the need for blind detection to distinguish between line-decoded signals transmitted by a backscattering AIoT device and uncoded signals transmitted by an AIoT device with active transmission capability.

[0027] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables different wireless communication devices to communicate at the city, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution program released 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, IoT connectivity and management, and network function virtualization (NFV).

[0028] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, 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 AIoT) 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. Such 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, etc. 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.

[0029] 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 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 UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0030] 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.

[0031] 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.

[0032] 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 be referred to as: 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 the radio access network (RAN).

[0033] 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 protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete protocol stack. For example, and as shown, network node 110 may be an aggregated network node, 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 a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0034] Alternatively, and also as shown, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can implement a 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 IAB networks, in Open Radio Access Networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), 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 individually deployable units.

[0035] Network nodes 110 of 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 those defined by 3GPP). In some examples, DUs may also host one or more low-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 low-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 type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0036] In some aspects, 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.

[0037] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. 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 may 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).

[0038] 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. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0039] In some examples, network node 110 may be, may include, or 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. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "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 downlink control information (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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a 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.

[0044] 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.

[0045] 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 be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0046] 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 collectively referred to as "MTC UEs". An MTC UE 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 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 wireless communication network 100).

[0047] 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, enhanced mobile broadband (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 simplified 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.

[0048] 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 send and receive sidelink communication using 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. 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.

[0049] 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.

[0050] 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).

[0051] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may obtain a signal to be transmitted to a radio device on a backward link; encode the signal to be transmitted to the radio device using one or more of line decoding or channel decoding, at least in part based on the channel or resources associated with the signal to be transmitted to the second radio device; and transmit the encoded signal to the radio device on the backward link. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0052] 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.

[0053] 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.

[0054] 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, a scheduler 246, and / or a communication manager 150, 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 the 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, may perform aspects of the methods, procedures 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.

[0055] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2The 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 2 Any 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.

[0056] 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 first set of processors and the second set of processors can be the same set of processors or can be 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.

[0057] 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)).

[0058] 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 set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0059] 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.

[0060] 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., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive 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.

[0061] 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 for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0062] 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 analog signals (such as those used for transmission or reception via an air interface) to 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.

[0063] 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 execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0064] 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.

[0065] 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, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (such as a data pipeline, data queue, and / or application executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0066] 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.

[0067] 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.

[0068] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or U Uplink 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).

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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).

[0073] 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.

[0074] Figure 3This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed 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 decomposed 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, a UE 120 may be served simultaneously by multiple RU 340s.

[0075] Each component of the disassembled 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.

[0076] 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.

[0077] 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.

[0078] 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 actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0079] 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 employ AI / ML models to perform corrective actions 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).

[0080] 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.

[0081] 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 or perform one or more operations associated with backlink decoding configuration for AIoT devices, 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 or perform one or more operations associated with backlink decoding configuration for AIoT devices, 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 7The operation of process 700 or other processes as described herein. 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 instruction sets (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 instruction set may be made to 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, transformation, or interpretation). Figure 7 The process 700 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.

[0082] In some aspects, UE 120 includes components for obtaining a signal to be transmitted to a radio device on a backlink; components for encoding the signal to be transmitted to the radio device using one or more of line decoding or channel decoding, at least in part, based on a channel or resources associated with the signal to be transmitted to the radio device; and / or components for transmitting the encoded signal to the radio device on the backlink. In some aspects, components for UE 120 to perform the operations described herein may include, for example, one or more of a communication 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.

[0083] 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.

[0084] Figure 4 This is an illustration of example 400 associated with an AIoT device that can use backscatter communication and / or energy harvesting according to this disclosure.

[0085] Some wireless communication devices can be considered IoT devices, such as AIoT devices (sometimes referred to as ultralight IoT devices) or similar IoT devices. IoT technologies can include passive IoT, semi-passive IoT, ultralight IoT, zero-power IoT, low-power IoT, or AIoT, etc. In passive IoT, the terminal (e.g., a passive RFID device, tag, or similar device) may not include a battery or other energy storage capacity, and the terminal can primarily accumulate energy from radio signaling. Additionally, in some cases, the terminal can accumulate solar energy, vibration energy, and / or thermal energy to supplement the accumulated energy from radio signaling. In passive IoT, the communication distance can be up to 30 meters (or longer) to facilitate feasible network coverage over large areas (e.g., 5000 square meters) such as in a warehouse. Furthermore, the power consumption of a passive IoT terminal (e.g., a UE) can be less than 0.1 milliwatts (mW) to support operation without a battery or other energy storage capacity, and the terminal can be relatively small and inexpensive (e.g., compared to other IoT devices, such as NB-IoT, LTE-M, and / or RedCap devices) to facilitate cost-sensitive use cases. The positioning accuracy of passive IoT terminals can be approximately 3 to 5 meters in both the horizontal and vertical directions.

[0086] Passive (or environmental) IoT combined with industrial sensors can be useful, for which battery replacement can be very difficult or undesirable (e.g., for security monitoring or fault detection in smart factories, infrastructure, or environments). Additionally, the characteristics of passive IoT devices, such as low cost, small size, low maintenance, durability, and long lifespan, can facilitate smart logistics and / or warehousing (e.g., combined with automated asset management via RFID tag replacement). Furthermore, passive IoT can be combined with smart home networks for home appliance management, wearable devices (e.g., wearables for medical monitoring of patients that do not require battery replacement), and / or environmental monitoring. To achieve further cost reduction and zero-power communication, wireless networks can utilize a type of passive IoT device known as an "environmental backscatter device" or "backscattering device," which uses backscattering transmission technology similar to passive RFID systems. For example, a passive RFID system typically includes a reader device and a passive RFID tag. The passive RFID tag is a battery-free backscattering device that is initially powered by an RF signal transmitted by the reader device, then decodes the RF signal and backscatters the stored information (e.g., by modulating the incident RF signal via a reflection coefficient switch). More specifically, in typical operation, the passive RFID tag receives electromagnetic waves via an antenna, rectifyes the potential difference of the electromagnetic waves to generate a direct current, which is used to charge a capacitor and power an integrated circuit (IC), demodulates and decodes the received signal, and then uses backscattering technology to transmit the decoded and modulated signal.

[0087] For example, such as Figure 4 As shown, a backscattering device 405 (e.g., a tag, sensor, etc.), which can be an example of a passive IoT device, can employ a simplified hardware design (e.g., including antenna 450, power divider 455, energy harvester 460, IC 465, and microcontroller 470) that excludes radio wave generation circuitry or other carrier signal generation capabilities, enabling the backscattering device 405 to transmit information solely by reflecting (e.g., backscattering) radio waves. Furthermore, Figure 4 The backscattering device 405 shown does not include a battery or other energy storage capability, thus relying on energy harvesting for power. Alternatively, in some cases, the backscattering device 405 may include energy storage capability, in which case the stored energy can be used to amplify the reflected or backscattered signal. In either case, the backscattering device 405 communicates with the reader 408 (e.g., UE 120, network node 110, IAB node, smart repeater, or another network device) by modulating reflected radio signals from RF source 410 (e.g., network node 110, UE 120, or another network device). In some examples, RF source 410 and reader 408 may be the same device and / or may be co-located. For example, in some cases, reader 408 and RF source 410 may be associated with the same network node 110.

[0088] To facilitate communication between backscattering device 405 and backscattering device 405, RF source 410 may transmit an energy harvesting wave to backscattering device 405. The energy harvesting wave may be transmitted for a sufficient duration to achieve a communication phase within the target range between reader 408 and backscattering device 405. Additionally or alternatively, in some cases, the range between RF source 410 and backscattering device 405 may be limited by a minimum received power, such as -20 dBm, used to trigger energy harvesting at backscattering device 405.

[0089] Once sufficient energy has accumulated at backscattering device 405, backscattering device 405 can begin to reflect (e.g., backscatter) radio waves radiated via backscattering link 415 onto backscattering device 405. For example, RF source 410 can initiate a communication session with a query (sometimes referred to as query-response communication), which can be a modulated envelope of a continuous wave (CW). Backscattering device 405 can respond by backscattering the CW. The communication session can include multiple rounds, such as for contention resolution purposes when multiple backscattering devices respond to a query. The channel between RF source 410 and backscattering device 405 at backscattering link 415 can be compared with a first backscattering link channel response value (sometimes referred to as a first backscattering link channel coefficient or a first backscattering link gain value). hBD Associated with, as described below, the backscattering device 405 may have a reflection on-time and reflection off-time that follow at least in part based on the pattern of information bits transmitted by the backscattering device 405. The reader 408 may detect the reflection pattern of the backscattering device 405 and obtain backscattering communication information via the backscattering link 415. The channel between the reader 408 and the backscattering device 405 of the backscattering link 415 may be correlated with a second backscattering link channel response value (sometimes referred to as a second backscattering link channel coefficient or a second backscattering link channel gain value). hDU Associated with each other. Furthermore, the RF source 410 and reader 408 can communicate (e.g., reference signals and / or data signals) via direct link 420. The channel between the RF source 410 and reader 408 of direct link 420 can be correlated with the direct link channel response value (sometimes referred to as the direct link channel coefficient or direct link channel gain value). hBU Related.

[0090] Backscattering device 405 can use information modulation schemes such as amplitude shift keying (ASK) modulation or on / off keying (OOK) modulation. For ASK or OOK modulation, backscattering device 405 can enable reflection when transmitting an information bit "1" and disable reflection when transmitting an information bit "0". Alternatively, backscattering device 405 can enable reflection when transmitting an information bit "0" and disable reflection when transmitting an information bit "1". In backscatter communication, RF source 410 can transmit specific radio waves (e.g., reference signals or data signals, such as PDSCH), which can be represented as... x(n) Reader 408 can receive the radio waves directly from RF source 410 via direct link 420. x(n) The radio wave is received by the backscattering device 405, which modulates the radio wave and reflects it to the reader 408, via the backscattering link 415. The signal received at the reader 408 via the direct link 420 (indicated by reference numeral 425) is the radio wave transmitted by the RF source 410. x(n) Multiply by the direct link channel response value hBU The product of the product and any signal noise. The information bit signal of the backscattering device 405 can be represented as... s(n) ,in s(n) ∈{0,1}. Therefore, the signal received at reader 408 via backscatter link 415 (indicated by reference numeral 430) is the signal transmitted by RF source 410. x(n) Multiply by the first backscatter link channel response value hBD Second backscatter link channel response value hDU Information bit signal from backscattering device 405 s(n) And the product of the reflection coefficient associated with the backscattering device 405 plus any noise.

[0091] Therefore, the signal received at reader 408 is a superposition of the signal received via direct link 420 and the signal received via backscatter link 415, which can represent y(n) As shown in the attached figure, denoted by label 435. As shown in the figure, when... s(n) When = 0 (indicated by reference numeral 440 in the graph shown at reference numeral 430), the backscattering device 405 can turn off reflection, and therefore the reader 408 receives only the direct link 420 signal. When s(n) When the value is 1 (indicated by reference numeral 445 in the graph shown at reference numeral 430), the backscattering device 405 can activate reflection, and thus the reader 408 receives the superposition of the direct link 420 signal and the backscattered link 415 signal. To receive the information bits transmitted by the backscattering device 405, the reader 408 can first treat the backscattered link 415 signal as interference, at least in part based on the direct link channel response value. h_BU(n) To decode x(n) Then, the reader 408 can detect the presence of the signal component. In some cases, the backscatter device 405 may not maintain the state from communication session to communication session except for the contents stored in the memory of the backscatter device 405, such as the electronic product code (EPC) or similar information associated with the backscatter device 405.

[0092] Some IoT devices can be referred to as semi-passive IoT devices because communication between the reader and the IoT device does not require an energy harvesting waveform as a precondition. For example, a semi-passive IoT device may include a battery or similar energy source that can power the receiver and / or logic circuitry. For such devices, energy harvesting can still be triggered in some cases, such as for long-range communication. In such examples, the rectifier circuitry of a semi-passive IoT device may have a hot start from a battery or other energy source and can therefore be associated with a lower minimum receive power requirement than that of a passive IoT device (e.g., -30 dBm instead of -20 dBm). However, long-range communication may require battery power consumption to incentivize each decoding. More specifically, for long-range communication where the energy harvesting rate is lower than required by the decoding circuitry, such as when the energy harvesting rate is below -30 dBm, a semi-passive IoT device may consume battery power to incentivize each decoding. Therefore, continuous IoT device monitoring (such as for receiving long-range query communications) can lead to excessive battery consumption at the semi-passive IoT device.

[0093] In this regard, passive and semi-passive IoT devices can inherently limit their applications. For example, passive IoT devices (such as backscattering device 405) can be associated with low cost and form factor because no RF chain is required at the IoT device. However, passive IoT devices require an energy harvesting waveform, thus limiting their application to short-range communication. While semi-passive IoT devices eliminate the need for an energy harvesting waveform and / or enable long-range communication, they add cost and complexity because they require a battery or similar power source. Furthermore, because passive and semi-passive IoT devices can be associated with communication sessions initiated by RF source 410, they may inherently limit their use in sensing scenarios or similar latency-critical applications requiring non-periodic business, and the device may not scale well for high IoT density applications. Therefore, in some cases, AIoT devices can be equipped with energy storage capabilities and active RF components to support independent carrier signal generation, which can increase communication range and extend AIoT to other use cases involving communication in wireless networks. However, because AIoT devices may have different capabilities, AIoT devices associated with different device types may use different decoding technologies, which leads to variable designs for different AIoT devices and increased complexity at reader 408.

[0094] 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.

[0095] Figure 5This is an illustration of the line decoding technology according to this disclosure and example 500 of different AIoT device types. For example, in wireless networks (e.g., LTE networks, NR networks, etc.), channel decoding (also known as forward error correction (FEC) or forward error control decoding (FECC)) is typically used to detect and correct bit errors associated with the transmitted signal. Channel decoding is typically performed at both the transmitter and receiver, where the transmitter uses a channel encoder to add extra parity bits to the raw data before modulation. Thus, when the modulated signal carrying the original (information) bits and the extra (parity) bits arrives at the receiver, the receiver uses the channel decoder to detect and correct any errors that may have occurred during transmission due to noise, interference, fading, etc. On the other hand, line decoding is a technique for converting digital bits into a specific waveform that can be transmitted over a communication channel to improve reliability when low-end or low-complexity transmitters are equipped with clocks with low accuracy. For example, as Figure 5 As shown, line decoding technology is typically used in passive communication systems, where passive devices 510 (e.g., RFID tags, passive AIoT devices, semi-passive AIoT devices, or other backscattering devices) are equipped with clocks that have low accuracy.

[0096] More specifically, in RFID systems, AIoT systems, etc., reader device 520 can transmit RF signals to passive device 510 on the forward link, and passive device 510 can transmit RF signals to reader device 520 on the backward link. Line decoding technology can be used to encode digital data onto the RF signals transmitted between passive device 510 and reader device 520 to overcome errors caused by the low-accuracy clock of passive device 510. For example, as described herein, the line code typically has high-level and low-level transitions in each bit to assist reader device 520 in detecting clock errors in passive device 510 and locating symbol boundaries. For example, as shown by reference numeral 530, passive device 510 can use an FMO line decoding scheme to encode the signal to be transmitted to reader device 520, where binary data is represented by the state of the waveform being inverted or not inverted in each bit cycle. For example, as shown by reference numeral 530 in the figure, the FM0 line decoding scheme is associated with a low-to-high or high-to-low inversion at the sign boundary of each bit, with a high-to-low or low-to-high inversion indicating a bit value "0" during the bit period, and no inversion indicating a bit value "1" during the bit period.

[0097] Additionally or alternatively, as indicated by reference numeral 540, passive device 510 may use a Miller line decoding scheme to encode the signal to be transmitted to reader device 520. This Miller line decoding scheme has more transitions than FM0, which improves clock recovery. For example, as shown, the Miller line decoding scheme similarly has transitions or inversions within the waveform, where multiple inversions exist within a bit period, and bit values ​​"1" have no inversion or fewer inversions than bit values ​​"0" in the middle of the bit period. Typically, FM0 and Miller line decoding schemes can be used to detect clock errors in passive device 510 (e.g., with frequency tolerances of ±5% to 22% and variations of ±2.5%), enabling collision detection via frequency shift and reducing self-interference in reader device 520. Furthermore, the Miller line decoding scheme can achieve a lower code rate than the FM0 line decoding scheme (e.g., to combat interference and noise) and can provide a larger frequency gap with the carrier relative to the FM0 line decoding scheme. In addition, as described herein, other suitable line decoding schemes can be used to overcome the hardware limitations caused by the low-accuracy clock of the passive device 510, such as bi-phase line decoding (e.g., ensuring a transition at the midpoint of each bit cycle to improve synchronization and error detection) and / or non-return-to-zero (NRZ) level line decoding (e.g., forcing a high level for bit value "1" or a low level for bit value "0"), etc.

[0098] Therefore, one or more line decoding schemes can be used to correct clock errors in passive devices or other devices with inaccurate clocks, to aid in clock error detection and resolve symbol boundaries. For example, line decoding schemes are commonly used in RFID systems and may be useful in AIoT systems where reader devices communicate with passive or semi-passive IoT devices with low-accuracy clocks. However, AIoT systems are not limited to passive and semi-passive IoT devices with low-accuracy clocks, as some more advanced AIoT devices may have more accurate clocks, thus mitigating the need for line codes. For example, in an AIoT system, as indicated by reference numeral 550, the AIoT device may be a passive AIoT device associated with a first AIoT device type (e.g., AIoT device type A), where the passive AIoT device lacks power storage capacity and independent carrier signal generation capability (e.g., it can only perform backscatter transmission). Passive AIoT devices can typically have power consumption in the range of 1 microwatt (μW) to 10 μM and can have complexity similar to UHF RFID tags. Alternatively, reference numeral 550 may correspond to a semi-passive AIoT device associated with a second AIoT device type (e.g., AIoT device type B), wherein the semi-passive AIoT device has energy storage capabilities but lacks independent carrier signal generation capabilities (e.g., it can only perform backscatter transmission, where the stored energy is used to amplify the reflected signal). Semi-passive AIoT devices may have higher or comparable power consumption than passive AIoT devices and typically have higher complexity. Alternatively, as indicated by reference numeral 560, the AIoT device may be an active (high-end) AIoT device associated with a third AIoT device type (e.g., AIoT device type C), wherein the active AIoT device has energy storage capabilities and active RF components for transmission (e.g., it has independent carrier signal generation capabilities and does not need to perform backscatter transmission). Active AIoT devices can have higher power consumption (e.g., from 1 milliwatt (mW) to 10 mW) than passive and semi-passive AIoT devices, and greater complexity than passive and semi-passive AIoT devices but several orders of magnitude lower than NB-IoT devices.

[0099] Therefore, as described herein, whether an AIoT device needs to use line codes when transmitting to a reader device on the backlink typically depends on the complexity of the AIoT device and, specifically, the accuracy of the clock associated with the AIoT device. For example, passive or semi-passive AIoT devices (e.g., associated with AIoT device type A or B) may require the use of line codes (e.g., FM0, Miller, and / or other line codes similar to RFID tags) due to their low clock accuracy. However, active AIoT devices (e.g., associated with AIoT device type C) are typically high-end (e.g., with energy storage and independent carrier signal generation capabilities), thus allowing for a reduced need for line code usage, as they have more accurate clocks to support active RF transmission components. Nevertheless, various common channels and / or resources exist for AIoT devices to communicate on the backlink, including channels and / or resources associated with gaining access to a wireless network (e.g., during random access procedures). For example, if an active AIoT device does not use line decoding during the random access process, the reader device can receive line-decoded signals from passive and / or semi-passive AIoT devices, and also uncoded signals from active AIoT devices. In such cases, the reader device will have to perform blind detection to decode the corresponding signals from passive / semi-passive / active AIoT devices, increasing the complexity of the reader device. Furthermore, this decoding scheme will lead to inhomogeneities between different AIoT device types. In other cases, active AIoT devices can use line decoding to enable the reader device to detect transmission collisions between AIoT devices.

[0100] Various aspects as a whole relate to backlink decoding configurations for AIoT devices. Some aspects relate more specifically to backlink decoding configurations that AIoT devices can use to encode signals to be transmitted on the backlink to reader devices (e.g., network nodes, UEs, IAB nodes, smart repeaters, etc.), depending on the channel and / or resources associated with the signal and the device type associated with the AIoT device. For example, as described herein, an AIoT device may be associated with a first AIoT device type (e.g., a passive AIoT device type or AIoT device type A) or a second AIoT device type (e.g., a semi-passive AIoT device type or AIoT device type B) that transmits signals on the backlink using backscattering techniques, or an AIoT device may be associated with a third AIoT device type (e.g., an active AIoT device type or AIoT device type C) that has active RF components for transmission on the backlink. Therefore, AIoT devices associated with the first or second AIoT device type (which rely on backscattering) may typically require line decoding to encode signals to be transmitted on the backward link to help the reader detect clock errors and locate symbol boundaries, while AIoT devices associated with the third AIoT device type may use channel decoding to encode signals to improve communication range and / or reliability.

[0101] However, there may be situations where AIoT devices associated with active AIoT device types should use line decoding to encode signals to reduce the complexity of the reader device and avoid performing blind detection on the reader device to distinguish line-decoded signals sent by AIoT devices of a first or second AIoT device type from uncoded signals sent by AIoT devices of a third AIoT device type. Therefore, in some aspects, when an AIoT device is transmitting a signal on a backlink channel or resource that is common to all AIoT device types, the signal can be encoded using line decoding regardless of the device type, and the channel decoder can be optionally configured. Furthermore, when an AIoT device of a first or second AIoT device type is transmitting a signal on a backlink channel or resource dedicated to an AIoT device associated with that first or second device type (e.g., using backscattering techniques), the signal can be encoded using line decoding, and the channel decoder can be optionally configured. Alternatively, when an AIoT device of a third AIoT device type is transmitting a signal on a backlink channel or resource associated with an AIoT device of the third device type (e.g., using an active RF component), the signal can be encoded using channel decoding, and a line decoder can be optionally configured. Some aspects described herein also relate to techniques for configuring backlink line decoding and channel decoding options and configurations for AIoT devices based on message type (e.g., whether the signal is a response to a query from a reader device or is transmitted using a resource pool configured by the reader device), and techniques for enabling or disabling backlink decoding for AIoT devices of a third device type based on whether the signal is an in-access signal transmitted during the access process or a post-access signal transmitted after the access process is completed.

[0102] 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.

[0103] Figures 6A to 6B This is a diagram illustrating example 600 associated with a backlink decoding configuration for an AIoT device according to this disclosure. Figures 6A to 6BAs shown, Example 600 includes communication between AIoT device 610 and reader device 620. In some aspects, reader device 620 and AIoT device 610 may be included in a wireless network such as wireless network 100. AIoT device 610 and reader device 620 may communicate via a wireless link, which may include a forward link for reader device 620 to transmit RF signals to AIoT device 610 and a backward link for AIoT device 610 to transmit RF signals to reader device 620. In some aspects, reader device 620 may correspond to a network node, such as an RU or DU associated with a decomposed base station, UE, IAB node, smart repeater, or other suitable wireless device. Furthermore, as described herein, AIoT device 610 may correspond to a passive or semi-passive AIoT device that can only transmit based on the incident RF signal transmitted by reader device 620 using backscattering, or an active AIoT device that can transmit carrier signals independently without relying on the incident RF signal transmitted by reader device 620.

[0104] like Figure 6A As shown by reference numeral 630 in the accompanying drawings, the AIoT device 610 can obtain signals to be transmitted to the reader device 620 on the backward link. For example, in some aspects, the signals to be transmitted may correspond to signals associated with the access procedure (e.g., a random access preamble) or another suitable signal (e.g., carrying control data, similar to a PUCCH transmission, or carrying a payload and / or data, similar to a PUSCH transmission). As in... Figure 6A As further shown by reference numeral 640 in the accompanying drawings, the AIoT device 610 may encode the signal to be transmitted on the backward link using line decoding and / or channel decoding based on the channel and / or resources associated with the signal and based on the AIoT device type associated with the AIoT device 610. For example, in some aspects, the AIoT device 610 may be associated with an AIoT device type that only supports backscatter transmission, such as a passive AIoT device type (e.g., AIoT device type A, which lacks power storage capacity and independent carrier signal generation capability) or a semi-passive AIoT device type (e.g., AIoT device type B, which has power storage capacity but lacks independent carrier signal generation capability). Alternatively, the AIoT device 610 may be associated with an AIoT device type that supports active transmission (e.g., an active AIoT device type (e.g., AIoT device type C, which has power storage capacity and independent carrier signal generation capability)).

[0105] For example, as indicated by reference numeral 650, AIoT device 610 may employ line decoding (e.g., FMO, Miller, or another suitable line decoding scheme) to encode signals to be transmitted to reader device 620 based at least in part on signals associated with one or more channels or resources that are common to all AIoT device types (e.g., passive, semi-passive, and active AIoT device types). In such cases, as indicated by reference numeral 650, AIoT device 610 may employ line decoding to encode signals to be transmitted to reader device 620, and channel decoding may be optionally configured (e.g., channel decoding (such as convolutional codes) may be configured or employed to encode the signal when it carries data, and channel decoding may be disabled when common backlink channels and / or resources are associated with access to a wireless network). Alternatively, as indicated by reference numeral 652, the AIoT device 610 may encode the signal to be transmitted to the reader device 620 using channel decoding (e.g., an FEC channel decoding scheme) based at least in part on the fact that the AIoT device 610 is associated with an active AIoT device type (e.g., AIoT device type C) and the signal is associated with one or more channels or resources dedicated to the active AIoT device type. Furthermore, in such cases, the AIoT device 610 associated with the active AIoT device type may optionally be configured to use or not use line decoding when transmitting signals associated with one or more channels or resources dedicated to the active AIoT device type. Alternatively, as indicated by reference numeral 654, when AIoT device 610 is associated with a passive or semi-passive AIoT device type (e.g., AIoT device type A or B), AIoT device 610 may always employ line decoding to encode the signal to be sent to reader device 620, and AIoT device 610 associated with a passive or semi-passive AIoT device type may optionally be configured to use or not use channel decoding when sending signals associated with one or more channels or resources dedicated to the passive or semi-passive AIoT device type or one or more channels or resources that are common to all AIoT device types.

[0106] In some respects, as described herein, the line decoding and channel decoding options and configurations for backward link transmissions by the AIoT device 610 can be mapped to the message type associated with the signal to be transmitted on the backward link. For example, as Figure 6BAs shown by reference numeral 660, reader device 620 may send a query to AIoT device 610 (e.g., a message transmitted to AIoT device 610 to trigger a response from AIoT device 610, such as a request for sensor data or other suitable information). In such cases, as shown by reference numeral 662, the signal sent by AIoT device 610 to reader device 620 may be a response to the query. Alternatively, in some aspects, the signal sent by AIoT device 610 to reader device 620 may be sent using one or more resource pools configured by reader device 620 (e.g., a common resource pool for all AIoT device types or a dedicated resource pool for a specific AIoT device type), which may be in response to or independent of any message sent by reader device 620. In some aspects, line decoding may be used to encode the signal to be sent to reader device 620 based on the message being associated with a query or resource pool that is common to all AIoT device types and / or based on the AIoT device 610 being a passive or semi-passive device and the message being associated with a query or resource pool dedicated to passive or semi-passive AIoT device types. Furthermore, in the case where AIoT device 610 is an active AIoT device or a passive or semi-passive AIoT device that supports channel decoding, channel decoding may optionally be used to encode the signal in addition to line decoding (e.g., line decoding may be required when the signal is a response to a common query for all AIoT device types, sent using a common resource pool for all AIoT device types, a response to a query dedicated to passive or semi-passive AIoT device types, and / or sent using a dedicated resource pool for passive or semi-passive AIoT device types, and channel decoding is optional). Alternatively, when AIoT device 610 is an active AIoT device and the signal to be sent to reader device 620 is a response to a query specific to the active AIoT device type and is transmitted using a dedicated resource pool for the active AIoT device type, channel decoding can be used to encode the signal. Furthermore, in some aspects, line decoding can be used to further encode the signal (e.g., when one or more conditions are met, such as to detect user collisions). Therefore, when AIoT device 610 is an active AIoT device and the signal to be sent to reader device 620 is a response to a query specific to the active AIoT device type and is transmitted using a dedicated resource pool for the active AIoT device type, channel decoding can be used to encode the signal, and line decoding can be optionally configured.

[0107] In some respects, as described herein, when the AIoT device 610 is an active AIoT device with energy storage and independent carrier signal generation capabilities, various additional decoding configurations and / or options can be configured. For example, in some respects, when the AIoT device 610 is an active AIoT device, various additional decoding configurations and / or options can be configured depending on whether the signal is an in-access signal (e.g., a signal transmitted during a random access procedure, such as a preamble or payload / data transmitted during a two-step or four-step random access procedure) or a post-access signal (e.g., a signal transmitted after the random access procedure for obtaining access to a wireless network has been completed).

[0108] For example, where all access channels and / or resources are common to all AIoT device types, the AIoT device 610 associated with an active AIoT device type can use line decoding configured in a query that triggers an access request from the reader device 620 to encode the signal to be sent to the reader device 620. In such cases, the query may indicate the line decoding type (e.g., FM0 line decoding scheme, Miller line decoding scheme, or another suitable line decoding scheme) and one or more parameters associated with the configured line decoding type (e.g., when configuring a Miller line decoding scheme, ...). M (Parameter values). Additionally or alternatively, line decoding used for encoding signals may be associated with a default option that AIoT device 610 may use without configuring line decoding in queries from reader device 620. In some aspects, information regarding whether access channels and / or resources are common to all AIoT device types or specific to a particular AIoT device type may be stored by AIoT device 610, configured by reader device 620, and / or indicated in query messages received by AIoT device 610 from reader device 620. Furthermore, similar techniques may be applied where line decoding options and / or configurations are mapped to resource pools that are common to all AIoT device types or specific to a particular AIoT device type.

[0109] Additionally or alternatively, where there are one or more access channels and / or resources common to all AIoT device types and one or more access channels and / or resources dedicated to active AIoT device types, reader device 620 may indicate one or more backlink line configurations of access channels and / or resources common to all AIoT device types in the query that triggers the access request. In such cases, AIoT device 610 may determine whether to employ line decoding indicated in the query or whether to employ only channel decoding based on the access channel and / or resources selected for transmitting the access signal (e.g., line decoding may be used if the access signal is transmitted using channels and / or resources common to all AIoT device types, or channel decoding may be used without line decoding if the access signal is transmitted using channels and / or resources dedicated to active AIoT device types). Additionally or alternatively, reader device 620 may configure backlink line decoding and indicate the AIoT device type in each query message transmitted to AIoT device 610. In such cases, AIoT device 610 may or may not employ backlink line decoding, depending on whether the configuration in the query indicates all AIoT device types or active AIoT device types. Furthermore, similar techniques may be applied where line decoding options and / or configurations are mapped to resource pools that are common to all AIoT device types or dedicated to a specific AIoT device type.

[0110] Additionally or alternatively, as indicated by reference numeral 670, when the signal transmitted by AIoT device 610 associated with an active AIoT device type is a preamble (e.g., for access or another purpose), AIoT device 610 may use line decoding to encode the preamble, and may indicate in the preamble whether line decoding is used in subsequent payload / data transmissions following the preamble. For example, as indicated by reference numeral 672, AIoT device 610 may transmit the preamble, and subsequent payload / data transmissions may be discontinuous (or disjointed, or time-separated) relative to the preamble. For example, as shown, the preamble may be encoded using line decoding before transmission, and preamble transmission may indicate whether line decoding is used for one or more payload / data transmissions after the process is complete. Additionally or alternatively, as indicated by reference numeral 674, AIoT device 610 may transmit a preamble that is always paired with a payload / data transmission (e.g., each transmission begins with a preamble). In such cases, the preamble can be encoded using line decoding before transmission, and the preamble transmission can indicate whether the line decoding will be used for payload / data transmission paired with the preamble.

[0111] In some aspects, after the AIoT device 610 associated with an active AIoT device type has completed the access process, various options can be defined to control whether the AIoT device 610 enables line decoding for subsequent backlink transmissions. For example, in some aspects, whether the AIoT device 610 enables backlink decoding after the access process can be based on the access state (e.g., the AIoT device 610 associated with the active AIoT device type does not use backlink decoding until and / or unless a subsequent query message or other event triggers another access request). Alternatively, in some aspects, whether the AIoT device 610 enables backlink decoding after the access process can be based on resources, wherein the AIoT device 610 does not use backlink codes when transmitting in one or more channels or resources dedicated to the active AIoT device type after obtaining access, and uses backlink codes when transmitting in one or more channels or resources that are common to all AIoT device types after obtaining access. Additionally or alternatively, backlink decoding can be enabled or disabled based on indication type, wherein AIoT device 610 does not use backlink decoding (e.g., only channel decoding) to encode signals corresponding to responses to any messages from reader device 620 that are specific to active AIoT device types or specific to AIoT device 610. Alternatively, AIoT device 610 may use backlink decoding to encode signals corresponding to responses to any messages from reader device 620 that are common to all AIoT device types. Additionally or alternatively, backlink decoding can be enabled or disabled based on activation, wherein AIoT device 610 may begin using configured backlink decoding to encode signals sent to reader device 620 (e.g., via multicast messages to all active AIoT devices and / or unicast messages to active AIoT device 610) after receiving backlink decoding activation and configuration from reader device 620. In such cases, AIoT device 610 may continue to use the configured backlink line decoding to encode signals sent to reader device 620 until AIoT device 610 receives a backlink line decoding deactivation message from reader device 620. Additionally or alternatively, backlink line decoding may be enabled or disabled on a per-channel basis. For example, in some aspects, depending on the configuration provided by reader device 620 for each transmission (e.g., via semi-static configuration, similar to RRC or MAC-CE configuration, or via dynamic configuration, such as DCI configuration), AIoT device 610 associated with an active AIoT device type may use backlink line decoding or may use only channel decoding to encode signals sent to reader device 620.

[0112] Furthermore, as described herein, various options can be defined to control whether AIoT device 610, associated with an active AIoT device type, enables channel decoding for subsequent backward link transmission after the access process has been completed. For example, in some aspects, channel decoding can be mutually exclusive with line decoding, so that AIoT device 610 can encode signals using only backward link line decoding or only channel decoding (e.g., because concatenating channel decoding and line decoding may increase decoding complexity at reader device 620, configuring line decoding and channel decoding to be mutually exclusive reduces decoding complexity at reader device 620). Alternatively, in some aspects, channel decoding can always be enabled for active AIoT device 610 after the access process is completed (e.g., when backward link line decoding is used, concatenating channel decoding and line decoding improves error detection and correction performance at the cost of increased decoding complexity at reader device 620). Alternatively, in some aspects, whether to enable channel decoding for the active AIoT device 610 after the access process is completed can be configuration-based, whereby the AIoT device 610, depending on the configuration provided by the reader device 620, encodes the signal to be sent to the reader device 620 using either backward link channel decoding or without channel decoding. For example, when backward link channel decoding is enabled, the decoding scheme can be configured by the reader device 620, or determined by the default option if the reader device 620 is not configured.

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

[0114] Figure 7 This is a diagram illustrating an example process 700 performed, for example, at a first wireless device or a device of the first wireless device, according to this disclosure. Example process 700 is an example of a device or first wireless device (e.g., AIoT device 610) performing operations associated with backlink decoding configuration for the AIoT device.

[0115] like Figure 7 As shown, in some aspects, process 700 may include obtaining a signal to be transmitted to a second wireless device on the backlink (block 710). For example, the first wireless device (e.g., using...) Figure 8 The receiving component 802 and / or communication manager 806 depicted herein can obtain signals to be transmitted to a second wireless device on the backward link, as described above.

[0116] like Figure 7As further shown, in some aspects, process 700 may include encoding the signal to be transmitted to the second wireless device using one or more of line decoding or channel decoding, at least in part, based on the channel or resources associated with the signal to be transmitted to the second wireless device (box 720). For example, the first wireless device (e.g., using...) Figure 8 The communication manager 806 depicted herein may encode the signal to be transmitted to the second wireless device, at least in part, using one or more of line decoding or channel decoding, as described above, based on the channel or resources associated with the signal to be transmitted to the second wireless device.

[0117] like Figure 7 As further shown, in some aspects, process 700 may include transmitting the encoded signal to a second wireless device on the backlink (block 730). For example, the first wireless device (e.g., using...) Figure 8 The described transmitting component 804 and / or communication manager 806 can transmit encoded signals to a second wireless device on a backward link, as described above.

[0118] Process 700 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.

[0119] In the first aspect, the signal is transmitted based on the incoming signal via backscattering in response to the lack of carrier signal generation capability of the first wireless device.

[0120] In a second aspect, either alone or in combination with the first aspect, the signal is encoded in response to the channel or resource associated with the signal corresponding to a dedicated backlink channel or resource for a wireless device having energy storage and carrier signal generation capabilities, and in response to the first wireless device having energy storage and carrier signal generation capabilities, at least using channel decoding.

[0121] In a third aspect, either alone or in combination with one or more of the first and second aspects, the signal is encoded in response to the channel or resource associated with the signal corresponding to a common backlink channel or resource for all wireless devices, at least using line decoding.

[0122] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the signal is encoded at least using line decoding in response to the channel or resource associated with the signal corresponding to a dedicated backlink channel or resource for a wireless device lacking one or more of the power storage or carrier signal generation capabilities.

[0123] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the signal is further encoded using channel decoding based at least in part on one or more parameters received from the second wireless device.

[0124] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the signal is further encoded, at least in part, based on the message type associated with the signal, using one or more of the line decoding or the channel decoding.

[0125] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the signal is encoded in response to the message type corresponding to a common message type for all wireless devices, at least using line decoding.

[0126] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the signal is encoded using at least the line decoding in response to the message type corresponding to a dedicated message type for a wireless device lacking one or more of the power storage or carrier signal generation capabilities, and in response to the first wireless device lacking one or more of the power storage or carrier signal generation capabilities.

[0127] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the signal is encoded at least using channel decoding in response to the message type corresponding to a dedicated message type for a wireless device having energy storage and carrier signal generation capabilities, and in response to the first wireless device having energy storage and carrier signal generation capabilities.

[0128] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the signal is encoded at least in part based on an access request message that corresponds to one or more channels or resources that are common to all wireless device types, using at least the line decoding.

[0129] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 700 includes receiving from the second wireless device a message indicating a backlink line decoding configuration associated with one or more channels or resources that are common to access requests associated with all wireless device types, and the signal is encoded if the signal is transmitted using one or more of those channels or resources that are common to access requests associated with all wireless device types, then the backlink line decoding configuration indicated in the message received from the second wireless device is used, or if the signal is transmitted using one or more of those channels or resources that are dedicated to access requests associated with the type of the first wireless device, then the line decoding is not used.

[0130] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 700 includes receiving from the second wireless device a message indicating a backward link decoding configuration and indicating a device type, wherein if the device type indicated in the message received from the second wireless device is common to all wireless device types or the device type associated with the first wireless device, the signal is encoded using the backward link decoding configuration indicated in the message.

[0131] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the signal is a preamble encoded using the line decoding, and wherein the preamble indicates whether the line decoding is used for one or more payloads or data transmissions following the preamble.

[0132] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the first wireless device has the capability of energy storage and carrier signal generation, and the signal is transmitted after an access request.

[0133] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the signal is encoded using only a channel code, based at least in part on the fact that the signal is sent before the access request is triggered by the next message from the second wireless device.

[0134] In the sixteenth aspect, the signal is encoded, either alone or in combination with one or more of the first to fifteenth aspects, as follows: decoding is performed using only the channel, based at least in part on the fact that the signal is transmitted using one or more channels or resources dedicated to wireless devices with energy storage and carrier signal generation capabilities; or decoding is performed using both the line and the channel, based at least in part on the fact that the signal is transmitted using one or more channels or resources that are common to all wireless devices.

[0135] In the seventeenth aspect, the signal is encoded, either alone or in combination with one or more of the first to sixteenth aspects, as follows: using only the channel for decoding, based at least in part on the signal responding to a message from the second wireless device that is dedicated to a wireless device with energy storage and carrier signal generation capabilities; or using both line decoding and the channel decoding, based at least in part on the signal responding to a message from the second wireless device that is common to all wireless devices.

[0136] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the signal is encoded using the line decoding, based at least in part on the fact that the signal is sent after the backlink line decoding activation message is received and before the backlink line decoding deactivation message is received.

[0137] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the signal is encoded using line decoding based at least in part on one or more parameters received from the second wireless device.

[0138] In the twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the signal is encoded using only line decoding or only channel decoding.

[0139] In the twenty-first aspect, the signal is encoded using the line decoding and the channel decoding, either alone or in combination with one or more of the first to twentieth aspects.

[0140] In the twenty-second aspect, either alone or in combination with one or more of the first to twenty-first aspects, the signal is encoded using channel decoding based at least in part on one or more parameters received from the second wireless device.

[0141] although Figure 7 An example box of process 700 is shown, but in some respects, process 700 may include... Figure 7 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 700 may be executed in parallel.

[0142] Figure 8 This is a diagram illustrating an example device 800 for wireless communication according to the present disclosure. Device 800 may be an AIoT device, or an AIoT device may include device 800. In some aspects, device 800 includes a receiving component 802, a transmitting component 804, and / or a communication manager 806 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 806 is combined with... Figure 1 The described communication manager 140. As shown, device 800 can communicate with another device 808 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 802 and transmitting component 804.

[0143] In some respects, device 800 can be configured to perform the functions described herein. Figures 6A to 6BOne or more operations described herein. Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 7 The process 700. In some aspects, the apparatus 800 and / or Figure 8 One or more components shown may include combinations Figure 2 One or more components of the described AIoT device. Additionally or alternatively, Figure 8 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.

[0144] Receiver 802 may receive communications from device 808, such as reference signals, control information, data communications, or combinations thereof. Receiver 802 may provide the received communications to one or more other components of device 800. In some aspects, receiver 802 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 800. In some aspects, receiver 802 may include combinations of... Figure 2 The described AIoT device 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.

[0145] Transmitting component 804 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 808. In some aspects, one or more other components of device 800 can generate communications and provide the generated communications to transmitting component 804 for transmission to device 808. In some aspects, transmitting component 804 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signal to device 808. In some aspects, transmitting component 804 may include combinations of... Figure 2The described AIoT device includes 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 804 may co-located with the receive component 802 in one or more transceivers.

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

[0147] The communication manager 806 can obtain the signal to be transmitted to the second wireless device on the backward link. The communication manager 806 can encode the signal to be transmitted to the second wireless device, at least in part, using one or more of line decoding or channel decoding, based on the channel or resources associated with the signal to be transmitted to the second wireless device. The transmitting component 804 can transmit the encoded signal to the second wireless device on the backward link.

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

[0149] The following provides an overview of some aspects of this disclosure.

[0150] Aspect 1: A method of wireless communication performed by a first wireless device, the method comprising: obtaining a signal to be transmitted to a second wireless device on a backward link; encoding the signal to be transmitted to the second wireless device using one or more of line decoding or channel decoding, at least in part based on a channel or resources associated with the signal to be transmitted to the second wireless device; and transmitting the encoded signal to the second wireless device on the backward link.

[0151] Aspect 2: According to the method of aspect 1, wherein the signal is transmitted based on the incoming signal via backscattering in response to the lack of carrier signal generation capability of the first wireless device.

[0152] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the signal is encoded at least using the channel decoding in response to the channel or resource associated with the signal corresponding to a dedicated backlink channel or resource for a wireless device having power storage and carrier signal generation capabilities, and in response to the first wireless device having power storage and carrier signal generation capabilities.

[0153] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the signal is encoded at least using the line decoding in response to the channel or resource associated with the signal corresponding to a common backlink channel or resource for all wireless devices.

[0154] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the signal is encoded at least using the line decoding in response to the channel or resource associated with the signal corresponding to a dedicated backward link channel or resource for a wireless device lacking one or more of the power storage or carrier signal generation capabilities.

[0155] Aspect 6: According to the method of aspect 5, wherein the signal is further encoded using the channel decoding based at least in part on one or more parameters received from the second wireless device.

[0156] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the signal is further encoded, at least in part, using one or more of the line decoding or the channel decoding, based on the message type associated with the signal.

[0157] Aspect 8: According to the method of aspect 7, wherein the signal is encoded in response to the message type corresponding to a common message type for all wireless devices, at least using the line decoding.

[0158] Aspect 9: According to the method of aspect 7, wherein the signal is a dedicated message type corresponding to a wireless device lacking one or more of the power storage or carrier signal generation capabilities, and is encoded using at least the line decoding in response to the first wireless device lacking one or more of the power storage or carrier signal generation capabilities.

[0159] Aspect 10: According to the method of aspect 7, wherein the signal is encoded at least using the channel decoding in response to the message type corresponding to a dedicated message type for a wireless device having energy storage and carrier signal generation capabilities, and in response to the first wireless device having energy storage and carrier signal generation capabilities.

[0160] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the signal is encoded at least in part based on an access request message associated with one or more channels or resources that are common to all wireless device types, using at least the line decoding.

[0161] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: receiving from the second wireless device a message indicating a backlink line decoding configuration associated with one or more channels or resources that are common to access requests associated with all wireless device types, wherein the signal is encoded using the backlink line decoding configuration indicated in the message received from the second wireless device if the signal is transmitted using one or more channels or resources that are common to access requests associated with all wireless device types, or without using the line decoding if the signal is transmitted using one or more channels or resources dedicated to access requests associated with the type of the first wireless device.

[0162] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: receiving from the second wireless device a message indicating a backward link decoding configuration and indicating a device type, wherein the signal is encoded using the backward link decoding configuration indicated in the message if the device type indicated in the message received from the second wireless device is common to all wireless device types or to a device type associated with the first wireless device.

[0163] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the signal is a preamble encoded using the line decoding, and wherein the preamble indicates whether the line decoding is used for one or more payloads or data transmissions following the preamble.

[0164] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the first wireless device has energy storage and carrier signal generation capabilities, and wherein the signal is transmitted after an access request.

[0165] Aspect 16: According to the method of aspect 15, wherein the signal is encoded using only a channel code, based at least in part on the fact that the signal is sent before the access request is triggered by a next message from the second wireless device.

[0166] Aspect 17: The method according to aspect 15, wherein the signal is encoded as follows: using only the channel decoding, based at least in part on the fact that the signal is transmitted using one or more channels or resources dedicated to wireless devices with energy storage and carrier signal generation capabilities; or using the line decoding and the channel decoding, based at least in part on the fact that the signal is transmitted using one or more channels or resources that are common to all wireless devices.

[0167] Aspect 18: According to the method of aspect 15, wherein the signal is encoded as follows: at least in part based on the signal responding to a message from the second wireless device dedicated to a wireless device with energy storage and carrier signal generation capabilities, using only the channel decoding; or at least in part based on the signal responding to a message from the second wireless device that is common to all wireless devices, using both the line decoding and the channel decoding.

[0168] Aspect 19: The method according to aspect 15, wherein the signal is encoded using the line decoding based at least in part on the fact that the signal is sent after receiving the backward link line decoding activation message and before the backward link line decoding deactivation message.

[0169] Aspect 20: According to the method of aspect 15, the signal is encoded using the line decoding based at least in part on one or more parameters received from the second wireless device.

[0170] Aspect 21: The method according to aspect 15, wherein the signal is encoded using only the line decoding or only the channel decoding.

[0171] Aspect 22: According to the method of aspect 15, wherein the signal is encoded using the line decoding and the channel decoding.

[0172] Aspect 23: According to the method of aspect 15, the signal is encoded using the channel decoding based at least in part on one or more parameters received from the second wireless device.

[0173] Aspect 24: 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 23.

[0174] 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 configured to cause the device to perform the method according to one or more of aspects 1 to 23.

[0175] Aspect 26: 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 23.

[0176] Aspect 27: 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 23.

[0177] Aspect 28: 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 23.

[0178] Aspect 29: 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 23.

[0179] Aspect 30: 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 23.

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

[0181] 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.

[0182] 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.

[0183] 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).

[0184] 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 interchangeable with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable 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”.

[0185] 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. A method for wireless communication performed by a first wireless device, the method comprising: Obtain the signal to be transmitted to the second wireless device on the backward link; The signal to be transmitted to the second wireless device is encoded using one or more of line decoding or channel decoding, at least in part, based on the channel or resources associated with the signal to be transmitted to the second wireless device. as well as The encoded signal is transmitted to the second wireless device on the backlink.

2. The method of claim 1, wherein the signal is transmitted based on the incoming signal via backscattering in response to the lack of carrier signal generation capability of the first wireless device.

3. The method of claim 1, wherein the signal is encoded at least using the channel decoding in response to the channel or resource associated with the signal corresponding to a dedicated backward link channel or resource for a wireless device having power storage and carrier signal generation capabilities, and in response to the first wireless device having power storage and carrier signal generation capabilities.

4. The method of claim 1, wherein the signal is encoded at least using the line decoding in response to the channel or resource associated with the signal corresponding to a common backlink channel or resource for all wireless devices.

5. The method of claim 1, wherein the signal is encoded using at least the line decoding in response to the channel or resource associated with the signal corresponding to a dedicated backward link channel or resource for a wireless device lacking one or more of the power storage or carrier signal generation capabilities.

6. The method of claim 5, wherein the signal is further encoded using the channel decoding based at least in part on one or more parameters received from the second wireless device.

7. The method of claim 1, wherein the signal is further encoded, at least in part, using one or more of the line decoding or the channel decoding, based on the message type associated with the signal.

8. The method of claim 7, wherein the signal is encoded in response to the message type corresponding to a common message type for all wireless devices, at least using the line decoding.

9. The method of claim 7, wherein the signal is a dedicated message type corresponding to a wireless device lacking either power storage or carrier signal generation capability, and is encoded using at least the line decoding in response to the first wireless device lacking either power storage or carrier signal generation capability.

10. The method of claim 7, wherein the signal is encoded using at least the channel decoding in response to the message type corresponding to a dedicated message type for a wireless device having power storage and carrier signal generation capabilities, and in response to the first wireless device having power storage and carrier signal generation capabilities.

11. The method of claim 1, wherein the signal is encoded, at least in part, based on an access request message associated with one or more channels or resources that are common to all wireless device types, using at least the line decoding.

12. The method according to claim 1, further comprising: The second wireless device receives a message indicating a backlink line decoding configuration associated with one or more channels or resources that are common to access requests associated with all wireless device types, wherein the signal is encoded in the following ways: In the case where the signal is transmitted using one or more channels or resources that are common to access requests associated with all wireless device types, the backlink line decoding configuration indicated in the message received from the second wireless device is used, or When the signal is transmitted using one or more channels or resources dedicated to an access request associated with the type of the first wireless device, the line decoding is not used.

13. The method according to claim 1, further comprising: The second wireless device receives a message indicating a backward link decoding configuration and indicating a device type, wherein the signal is encoded using the backward link decoding configuration indicated in the message if the device type indicated in the message received from the second wireless device is common to all wireless device types or the device type associated with the first wireless device.

14. The method of claim 1, wherein the signal is a preamble encoded using the line decoding, and wherein the preamble indicates whether the line decoding is used for one or more payloads or data transmissions following the preamble.

15. The method of claim 1, wherein the first wireless device has energy storage and carrier signal generation capabilities, and wherein the signal is transmitted after an access request.

16. The method of claim 15, wherein the signal is encoded using only a channel code, based at least in part on the fact that the signal is sent before the access request is triggered by a next message from the second wireless device.

17. The method of claim 15, wherein the signal is encoded as follows: At least in part, this is based on the fact that the signal is transmitted using one or more channels or resources dedicated to wireless devices with energy storage and carrier signal generation capabilities, using only the channels for decoding, or The line decoding and the channel decoding are used, at least in part, based on the fact that the signal is transmitted using one or more channels or resources that are common to all wireless devices.

18. The method of claim 15, wherein the signal is encoded as follows: At least in part, based on the signal response to a message from the second wireless device dedicated to a wireless device with power storage and carrier signal generation capabilities, using only the channel decoding, or The line decoding and the channel decoding are used at least in part based on the signal response to a message from the second wireless device that is common to all wireless devices.

19. The method of claim 15, wherein the signal is encoded using the line decoding based at least in part on the fact that the signal is sent after receiving the backward link line decoding activation message and before the backward link line decoding deactivation message.

20. The method of claim 15, wherein the signal is encoded using the line decoding based at least in part on one or more parameters received from the second wireless device.

21. The method of claim 15, wherein the signal is encoded using only the line decoding or only the channel decoding.

22. The method of claim 15, wherein the signal is encoded using the line decoding and the channel decoding.

23. The method of claim 15, wherein the signal is encoded using the channel decoding based at least in part on one or more parameters received from the second wireless device.

24. A first wireless device for wireless communication, the first wireless device comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors being configured to cause the first wireless device to: Obtain the signal to be transmitted to the second wireless device on the backward link; The signal to be transmitted to the second wireless device is encoded using one or more of line decoding or channel decoding, at least in part, based on the channel or resources associated with the signal to be transmitted to the second wireless device. as well as The encoded signal is transmitted to the second wireless device on the backlink.

25. The first wireless device of claim 24, wherein the signal is encoded at least using the channel decoding in response to the channel or resource associated with the signal corresponding to a dedicated backlink channel or resource for a wireless device having power storage and carrier signal generation capabilities.

26. The first wireless device of claim 24, wherein the signal is encoded at least using the line decoding in response to the channel or resource associated with the signal corresponding to a common backlink channel or resource for all wireless devices.

27. The first wireless device of claim 24, wherein the signal is encoded using at least the line decoding in response to the channel or resource associated with the signal corresponding to a dedicated backward link channel or resource for a wireless device lacking one or more of the power storage or carrier signal generation capabilities.

28. The first wireless device of claim 27, wherein the signal is further encoded using the channel decoding based at least in part on one or more parameters received from the second wireless device.

29. 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 first wireless device, cause the first wireless device to: Obtain the signal to be transmitted to the second wireless device on the backward link; The signal to be transmitted to the second wireless device is encoded using one or more of line decoding or channel decoding, at least in part, based on the channel or resources associated with the signal to be transmitted to the second wireless device. as well as The encoded signal is transmitted to the second wireless device on the backlink.

30. An apparatus for wireless communication, the apparatus comprising: Components used to acquire signals to be transmitted to wireless devices on the backlink; Components for encoding the signal to be transmitted to the wireless device, at least in part, using one or more of line decoding or channel decoding based on the channel or resources associated with the signal to be transmitted to the wireless device; and Components for transmitting encoded signals to the wireless device on the backlink.

Images