Multilayer coding for uplink transmissions

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit an indication of multi-layer coding (MLC) capability for uplink transmissions. The UE may receive a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 809,691, filed on June 29, 2022, entitled “MULTI-LEVEL CODING FOR UPLINK TRANSMIS SIONS” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for multi-layer coding for uplink transmissions. Background Art

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

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

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

[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: sending an indication of a multi-layer coding (MLC) capability for an uplink transmission. The method may include: receiving a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include: receiving an indication of MLC capability for an uplink transmission. The method may include: sending a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an indication of MLC capabilities for uplink transmissions. The one or more processors may be configured to receive a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capabilities for the uplink transmission.

[0010] Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of MLC capability for an uplink transmission. The one or more processors may be configured to send a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to send an indication of MLC capabilities for uplink transmissions. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capabilities for the uplink transmission.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to receive an indication of MLC capability for uplink transmission. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of MLC capabilities for uplink transmissions. The apparatus may include means for receiving a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capabilities for the uplink transmission.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of MLC capability for an uplink transmission. The apparatus may include means for transmitting a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

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

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

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

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

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

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

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

[0022] Figure 4 is a diagram illustrating an example of a low density parity check decoding procedure according to the present disclosure.

[0023] FIG. 5A to FIG. 5C is a diagram illustrating an example of a multi-layer coding (MLC) procedure according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of an MLC cluster graph according to the present disclosure.

[0025] Figure 7 is a diagram of an example associated with using MLC for uplink transmission according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0028] Fig.10 is a diagram of an example apparatus for wireless communications according to the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] In some aspects, the UE 120 may include a communications manager 140. As described in greater detail elsewhere herein, the communications manager 140 may send an indication of a multi-layer coding (MLC) capability for an uplink transmission; and receive a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0048] In some aspects, the network node 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may receive an indication of MLC capabilities for an uplink transmission; and transmit a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capabilities for the uplink transmission. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

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

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

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

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

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

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

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

[0057] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the UE 120 may perform one or more techniques associated with MLC for uplink transmissions, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 of , and / or the operation of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, the UE 120 includes means for sending an indication of MLC capabilities for uplink transmissions; and / or means for receiving a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of MLC capabilities for the uplink transmissions. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0059] In some aspects, the network node 110 includes means for receiving an indication of MLC capabilities for uplink transmissions; and / or means for sending a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of MLC capabilities for the uplink transmissions. In some aspects, the means for the network node 110 to perform operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0074] Figure 4 is a diagram illustrating an example 400 of a low-density parity-check (LDPC) decoding procedure according to the present disclosure.

[0075] Communications from a transmitting entity (e.g., a UE 120 or a network node 110) to a receiving entity (e.g., another UE 120 and / or another network node 110) may be encoded at least in part based on an error correction code (sometimes referred to as an error correction scheme) so that the receiving entity can determine whether the communication is correctly transmitted (e.g., so that the receiving entity can verify that the communication is not corrupted by noise, etc.) and / or so that the receiving entity can use redundant bits provided by the error correction code, etc. to correct any transmission errors. An example of an error correction code is an LDPC code. Communications may be encoded at least in part based on an LDPC code to provide error detection at the receiving entity. Coding for LDPC may be performed at least in part based on a base graph (e.g., a sparse bipartite graph). The base graph may identify a codeword to be generated from an input data set and / or may identify information to be appended to the input data set to form an LDPC.

[0076] More specifically, if Figure 4 As shown, transmitter 405 may communicate wirelessly with receiver 410. In some cases, transmitter 405 may be one of UE 120 or network node 110, and receiver 410 may be the other of UE 120 and network node 110. Transmitter 405 and receiver 410 may communicate via a wireless network (such as a combined Figure 1100) for wireless communication. When the transmitter 405 sends data to the receiver 410, the transmitter may first encode the data using an error correction code such as an LDPC code. More specifically, as shown by reference numeral 415, the transmitter 405 may process the raw data to be sent to the receiver 410 by feeding the raw data through an LDPC encoder 420 and other signal processing components. The transmitter 405 may perform other signal processing operations (e.g., interleaving, etc.), which are not described in detail for ease of description. Figure 4 4. The LDPC encoder 420 may add error correction bits to the original data based at least in part on the selected base graph and / or at least in part on the target code rate, thereby forming a coded data stream, as shown by reference numeral 425. In some aspects, "code rate" may refer to the number of original data bits divided by the total number of bits in the coded data stream (e.g., the code rate is the proportion of the data stream that is useful or non-redundant), and thus LDPC decoding or similar processes associated with lower code rates provide more error protection than LDPC decoding or similar processes associated with higher code rates, but require additional overhead. The coded data may be sent by the transmitter 405 to the receiver 410 using a RAN, etc., where the coded data is fed through an LDPC decoder 430 (and in some aspects, other signal processing components such as a deinterleaver, etc.) to extract the original data from the coded data, as shown by reference numeral 435.

[0077] Although error correction decoding processes such as LDPC decoding can advantageously protect data streams and result in reduced communication error rates, such processes can be associated with large overhead due to the addition of error correction bits to the original data stream and / or require relatively high power consumption at the transmitter 405 and the receiver to encode and decode the original data. For example, in some instances, decoding the channel with an LDPC decoder at the receiver 410 can constitute the largest power consumption operation in the digital chain, accounting for more than 60% of the power consumption used by the modem associated with the receiver 410 in some cases. Error correction decoding processes such as LDPC decoding can consume even more power when implemented for high-frequency communications, such as communications in millimeter wave (e.g., FR2) bands and / or communications in sub-terahertz bands (such as FR4 and beyond FR4). Such high-frequency communications can be associated with relatively large bandwidths and high data / bit rates, resulting in high power consumption associated with LDPC decoding processes, etc. For example, for some sub-terahertz communications, LDPC power consumption can approach 90% of the total power consumption used by the modem associated with the receiver 410. Therefore, transmitter 405 and receiver 410 may forgo LDPC decoding and similar error correction decoding to reduce power consumption, resulting in increased transmission error rates and therefore unreliable communications, or otherwise employ LDPC decoding or similar error correction decoding schemes at the expense of high power consumption and large overhead.

[0078] Some techniques and apparatus described herein implement a robust error correction decoding process for uplink transmissions, such as uplink transmissions in a sub-terahertz band, while providing reduced power consumption at a receiver (e.g., at a network node 110) compared to the LDPC decoding process described above. In some aspects, a UE 120 may utilize multi-layer coding (MLC) for uplink transmissions, such that one layer may be decoded using a first error correction decoding scheme (e.g., LDPC decoding), while another layer may remain undecoded or otherwise be encoded using a second error correction decoding scheme that consumes less power than LDPC decoding, etc. In some aspects, a UE 120 may signal to a network node 110 an indication of whether the UE 120 is capable of using MLC for uplink transmissions, and the network node 110 may configure the UE 120 with a selected MLC scheme based at least in part on the capabilities of the UE 120. Thus, UE 120 and network node 110 may communicate with reduced overhead, reduced error rates, and reduced power consumption, resulting in more reliable wireless communications and an overall more efficient use of power and network resources.

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

[0080] FIG. 5A to FIG. 5C is a diagram illustrating an example 500 of an MLC procedure according to the present disclosure.

[0081] MLC (sometimes referred to as unequal error protection) refers to the process of assigning different component codes to non-overlapping subsets of bits in a data stream. In some aspects, each subset of bits may be referred to as a level. For example, referring to Figure 5A , and as shown in reference numeral 505, the data stream is associated with two component codes (e.g., the data stream is associated with two levels). A first subset of bits (which is the first four bits shown) is associated with a first component code (indicated as "component code 1") and a first level (indicated as "level 1"). A second subset of bits (which is the second four bits shown) is associated with a second component code (indicated as "component code 2") and a second level (indicated as "level 2"). In some aspects, each level is protected using a different error correction code. For example, the first level can be protected using an LDPC decoding scheme, while the second level can remain undecoded, or a simpler error correction code process such as a Reed-Solomon scheme can be used to protect.

[0082] Reference numeral 510 shows a process for encoding data using MLC. The process shown with reference numeral 510 may be performed by a transmitter (e.g., UE 120, network node 110, transmitter 405, etc.). In addition, the process shown by reference numeral 510 is for two layers of MLC, but aspects of the present disclosure are not limited thereto. In some other aspects, more levels (e.g., three or more levels) may be adopted without departing from the scope of the present invention. As shown in K1 and K2, two component data streams are provided to corresponding encoders shown as "encoder-R1" and "encoder-R2", thereby resulting in coded data streams N1 and N2, respectively. In some aspects, one or more of the coded data streams N1 and N2 may undergo additional signal processing before transmission. For example, in the depicted example, the two coded data streams undergo an interleaving process by feeding the coded data streams N1 and N2 to "interleaver 1" and "interleaver 2", respectively. Other signal processing techniques may be performed without departing from the scope of the present disclosure. After the interleaving process, the data streams are combined and fed to a tagging and mapping component, resulting in a multi-layer coded data stream, such as the coded data stream described above in connection with reference numeral 505. The multi-layer coded data stream may then be sent to a receiver via a RAN or the like.

[0083] Now go to Figure 5B, reference numeral 515 shows a process for decoding MLC data (such as the multi-layer encoded data stream described in conjunction with reference numeral 510). The process shown by reference numeral 515 may be performed by a receiver (e.g., UE 120, network node 110, receiver 410, etc.). In addition, the process shown by reference numeral 515 may be referred to as a multi-stage decoding (MSD) process. MSD may include decoding at least one of the MLC layers based at least in part on knowledge (sometimes referred to as partition information) obtained from decoding a previous MLC layer. For example, in a two-level MLC scheme, such as the two-level MLC scheme described in conjunction with reference numerals 505 and 510, layer 2 may be decoded after layer 1 and based at least in part on partition information obtained from decoding layer 1. However, aspects of the present disclosure are not limited to MSD. In some other aspects, the multi-layer encoded data may be decoded according to another decoding process (such as described below in conjunction with Figure 5C The decoding is performed using the Parallel Independent Decoding (PID) process described in more detail.

[0084] In some aspects, the multi-layer coded data stream may be fed to a marking and demapping component associated with each coding level (e.g., Figure 5B In the two-layer example shown in FIG. 1 , a "Marking and Demapping Layer 1" component and a "Marking and Demapping Layer 2" component. The Marking and Demapping Layer 1 component may separate the coded and interleaved stream associated with Layer 1 and feed the stream to a "Deinterleaver 1" for performing a deinterleaving process to arrive at a first coded data stream N1. The first coded data stream N1 may then be provided to a decoder (shown as "Decoder-R1", which in some aspects may correspond to a decoder in conjunction with Figure 4 LDPC decoder 430) is described to arrive at the first component data stream K1.

[0085] As shown by the arrow connecting decoder-R1 to the marking and demapping layer 2 component, in this example, the output of the layer 1 decoder (e.g., the first component data stream K1) can be used as part of the decoding process for the second component data stream K2. More specifically, based at least in part on the first component data stream K1 and the multi-layer coded data stream, the marking and demapping layer 2 component can separate the coded and interleaved stream associated with layer 2 and feed the stream to a "deinterleaver 2" for performing a deinterleaving process to arrive at the second coded data stream N2. The second coded data stream N2 is then provided to a decoder (shown as "decoder-R2", which in some aspects may correspond to a decoder in conjunction with Figure 4 LDPC decoder 430 as described) to arrive at the second component data stream K2.

[0086] like Figure 5CAs shown and indicated by reference numeral 520, during the PID process, the two component data streams K1 and K2 may be decoded in parallel and / or without knowledge obtained from decoding of a previous level. In such aspects, the marking and demapping component described in conjunction with reference numeral 515 may be a single component that separates the two interleaved and coded data streams from the multi-layer coded data stream, as shown. The two interleaved and coded data streams are then decoded in conjunction with the above Figure 5B A similar approach as described is fed in parallel through the deinterleavers (e.g., Deinterleaver 1 and Deinterleaver 2) and decoders (e.g., Decoder-R1 and Decoder-R2). FIG. 5A to FIG. 5C One of the described MLC schemes or a similar MLC scheme may result in reduced overhead and power consumption, such as in combination with Figure 4 This can be referred to as described below Figure 6 and Figure 7 Easier to understand.

[0087] As indicated above, FIG. 5A to FIG. 5C are provided as examples. Other examples can be found in the FIG. 5A to FIG. 5C The examples described are different.

[0088] Figure 6 is a diagram illustrating an example 600 of an MLC cluster map according to the present disclosure.

[0089] Figure 6 The example shown in is associated with two layers of MLC and 16-quadrature amplitude modulation (16-QAM) MCS. However, aspects of the present disclosure are not limited thereto, and in some other aspects, a different number of layers may be utilized and / or a different MCS may be implemented without departing from the scope of the present disclosure. In addition, each cluster point in the cluster diagram is associated with a four-bit string. However, in some other aspects, each cluster point may be associated with more or fewer bits without departing from the scope of the present disclosure. For example, in examples implementing 32-QAM, 64-QAM, 128-QAM, or 256-QAM, each cluster point may be associated with five bits, six bits, seven bits, or eight bits, respectively. In addition, in the depicted example, each MLC layer is associated with two bits per cluster point, but in some other aspects, each MLC layer may be associated with more or fewer bits per cluster point.

[0090] As shown in the figure, each cluster point can be Figure 61, 2, 3, and 4. Each bit string within a cluster point set may be associated by including the same level one bit (e.g., the same first two bits). More specifically, cluster points associated with 0000, 0001, 0010, and 0011 all belong to set 1 (e.g., set 1 corresponds to level 1 of "00"), cluster points associated with 0100, 0101, 0110, and 0111 all belong to set 2 (e.g., set 2 corresponds to level 1 of "01"), cluster points associated with 1000, 1001, 1010, and 1011 all belong to set 3 (e.g., set 3 corresponds to level 1 of "10"), and cluster points associated with 1100, 1101, 1110, and 1111 all belong to set 4 (e.g., set 4 corresponds to level 1 of "11").

[0091] Each cluster point is separated from adjacent cluster points by a distance x or but separated from the nearest cluster point belonging to the same set by a distance of 2x or As shown. This can advantageously allow unequal error correction decoding for various MLC layers. For example, the first two bits (e.g., layer 1) can be protected using LDPC decoding, etc., to reduce or eliminate errors associated with determining which set these bits belong to. Therefore, the receiver can decode layer 1 and determine that the first two bits are 00, 01, 10, or 11, thereby determining the corresponding set of bit strings. That is, once the receiver decodes the first MLC layer, the receiver knows that the associated cluster point must be one of the four cluster points in the corresponding set. More specifically, if the first layer bit is 00, the cluster point must be one of the four cluster points in set 1 (e.g., 0000, 0001, 0010, or 0011). Similarly, if the first level bit is 01, then the cluster point must be one of the four cluster points in set 2 (e.g., 0100, 0101, 0110, or 0111), if the first level bit is 10, then the cluster point must be one of the four cluster points in set 3 (e.g., 1000, 1001, 1010, or 1011), and if the first level bit is 11, then the cluster point must be one of the four cluster points in set 4 (e.g., 1100, 1101, 1110, or 1111). As described, the four cluster points in each set are relatively far away from each other (e.g., each cluster point is separated from an adjacent cluster point belonging to the same set by a distance of 2x or ), and therefore the receiver is less likely to make errors when decoding the second level bits. In other words, when decoding the second level, noise in the signal, etc. is less likely to cause the receiver to select an incorrect constellation point because the constellation points in the set are separated by relatively large distances. Therefore, the second level bits can be protected by less complex error correction schemes (such as Reed-Solomon decoding, etc.) than LDPC decoding, or the second level may even remain undecoded. Therefore, power consumption at the receiver can be reduced because not all bits need to be processed by the LDPC decoder.

[0092] In some aspects, UE 120 may implement MLC for uplink transmissions to reduce power consumption when network node 110 receives and decodes communications. For example, UE 120 may decode at least some of the MLC levels with a simple decoding scheme (e.g., Reed-Solomon decoding, etc.), or otherwise leave at least some of the MLC levels undecoded, in order to reduce power consumption at network node 110 associated with LDPC decoding. Figure 7 Various aspects of implementing MLC for uplink transmissions are described in greater detail.

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

[0094] Figure 7 is a diagram of an example 700 associated with using MLC for uplink transmissions according to the present disclosure. Figure 7 As shown, the network entity 110 can communicate with the UE 120. In some aspects, the network node 110 and the UE 120 can be part of a wireless network (e.g., the wireless network 100). The UE 120 and the network node 110 can be in communication with each other. Figure 7 The operations shown are performed after a wireless connection has been established.

[0095] As indicated by reference numeral 705, UE 120 may send a capability report to network node 110. In some aspects, the capability report may indicate that UE 120 supports MLC for uplink transmission. More specifically, UE 120 may send an indication of MLC capability for uplink transmission to network node 110. In some aspects, the indication of MLC capability for uplink transmission indicates one or more MLC schemes supported by UE 120. For example, UE 120 may indicate that UE 120 supports at least one of an MSD MLC scheme or a PID MLC scheme, as described above in conjunction with Figure 5B and Figure 5CAdditionally or alternatively, the indication of the MLC capability for uplink transmission may indicate the number of supported MLC levels or a similar support parameter. For example, UE 120 may indicate that UE 120 supports two MLC levels, or else supports three or more MLC levels.

[0096] As indicated by reference numeral 710, UE 120 may also send an indication of one or more recommended MLC parameters associated with the MLC scheme to be used for uplink transmissions to network node 110. In some aspects, the indication of one or more recommended MLC parameters associated with the MLC scheme to be used for uplink transmissions may be sent as part of a capability report as described in conjunction with reference numeral 705, while in some other aspects, the indication of one or more recommended MLC parameters associated with the MLC scheme to be used for uplink transmissions may be sent in a message separate from the capability report as described in conjunction with reference numeral 705. For example, in some aspects, the indication of one or more recommended MLC parameters associated with the MLC scheme to be used for uplink transmissions may be associated with a channel state information (CSI) report or similar message sent to network node 110.

[0097] In some aspects, the indication of one or more recommended MLC parameters associated with the MLC scheme to be used for uplink transmissions may indicate a recommended number of bits associated with each MLC level. Figure 6 As described, in the aspect of adopting 16-QAM, UE 120 may recommend that two bits should be associated with each MLC level in two MLC levels. In some other aspects, UE 120 may recommend that more or fewer bits should be associated with each level and / or more than two levels should be utilized. Additionally or alternatively, an indication of one or more recommended MLC parameters associated with an MLC scheme to be used for uplink transmission may indicate a recommended code rate associated with each MLC level in multiple MLC levels. Additionally or alternatively, an indication of one or more recommended MLC parameters associated with an MLC scheme to be used for uplink transmission may indicate a recommended modulation type associated with each MLC level in multiple MLC levels. Additionally or alternatively, an indication of one or more recommended MLC parameters associated with an MLC scheme to be used for uplink transmission may indicate a recommended MLC scheme. For example, UE 120 may recommend LDPC coding for the first MLC level and Reed-Solomon coding for the second level, or the second level should remain uncoded, and / or UE 120 may recommend that MSD should be used or PID should be used.

[0098] In some aspects, one or more recommended MLC parameters may be based at least in part on measurements of a communication channel performed by UE 120, etc. For example, in some aspects, the one or more recommended MLC parameters may be based at least in part on measurements associated with a CSI reference signal (CSI-RS) associated with the same channel. Additionally or alternatively, the one or more recommended MLC parameters may be based at least in part on calculations of decoding probabilities associated with a channel. Additionally or alternatively, the one or more recommended MLC parameters may be based at least in part on a signal-to-noise ratio (SNR) associated with a channel. Additionally or alternatively, the one or more recommended MLC parameters may be based at least in part on a delay spread associated with a channel. Additionally or alternatively, the one or more recommended MLC parameters may be based at least in part on a Doppler shift associated with a channel. Additionally or alternatively, the one or more recommended MLC parameters may be based at least in part on information associated with impairment at a network device (such as impairment at UE 120 due to hand occlusion, line of sight occlusion, etc.).

[0099] As indicated by reference numeral 715, UE 120 may receive configuration information from network node 110. In some aspects, UE 120 may receive the configuration information via one or more of RRC signaling, one or more medium access control (MAC) control elements (MAC-CEs), and / or downlink control information (DCI), etc. In some aspects, the configuration information may include an indication of one or more configuration parameters for selection by UE 120 (e.g., known to UE 120 and / or previously indicated by network node 110 or other network devices) and / or explicit configuration information for UE 120 to use to configure UE 120, etc.

[0100] In some aspects, the configuration information may include a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of MLC capability of the uplink transmission as described in conjunction with reference numeral 705. For example, the selected MLC scheme may be associated with an MSD MLC scheme, a PID MLC scheme, a QAM MLC scheme (such as in conjunction with Figure 6 The selected MLC scheme may be associated with a plurality of MLC levels, such as a 16-QAM scheme or another QAM scheme described herein, an amplitude and phase shift keying (APSK) MCS, etc. In some aspects, the selected MLC scheme may be associated with a plurality of MLC levels, such as a combination of FIG. 5A to FIG. 6 In such aspects, the configuration of the selected MLC scheme may indicate a number of bits associated with each of the plurality of MLC levels. Additionally or alternatively, the configuration of the selected MLC scheme may indicate a code rate associated with each of the plurality of MLC levels.

[0101] Furthermore, in some aspects, the selected MLC scheme can be associated with unequal error correction decoding, such as in combination with Figure 6 That is, the selected MLC scheme may be associated with a plurality of MLC tiers, and the error protection scheme associated with a first MLC tier in the plurality of MLC tiers may be different from the error protection scheme associated with a second MLC tier in the plurality of MLC tiers. For example, the first MLC tier may be associated with LDPC coding, and the second MLC tier may be uncoded or associated with Reed-Solomon coding. In such aspects, the configuration information may indicate corresponding error protection schemes associated with one or more of the MLC tiers.

[0102] UE 120 may configure itself based at least in part on the configuration information. Further, in some aspects, UE 120 may be configured to perform one or more operations described herein based at least in part on the configuration information. For example, as indicated by reference numeral 720, in some aspects, UE 120 may encode uplink communications based at least in part on the selected MLC scheme (e.g., based at least in part on the MLC information indicated by the configuration information). Figure 5A As described, this may include encoding a first MLC level using a first error correction coding scheme (e.g., LDPC coding, etc.), and encoding a second MLC level using a second error correction coding scheme different from the first error correction coding scheme (e.g., Reed-Solomon coding, otherwise the second level remains uncoded).

[0103] As indicated by reference numeral 725, UE 120 may communicate with network node 110 based at least in part on the configuration information described in conjunction with reference numeral 715. For example, UE 120 may transmit encoded uplink communications to network node 110 based at least in part on the selected MLC scheme. In some aspects, UE 120 may communicate with network entity 110 using a high frequency band. More specifically, in some aspects, the uplink transmissions illustrated by reference numeral 725 may be associated with a sub-THz frequency band.

[0104] Based at least in part on UE 120 using an MLC scheme to transmit uplink communications, UE 120 and / or network node 110 may save computational, power, network, and / or communication resources that may have otherwise been consumed by conventional uplink transmission error correction decoding processes (such as LDPC encoding processes and decoding processes). For example, based at least in part on UE 120 implementing MLC for uplink transmissions, thereby enabling certain layers to be decoded with a less complex error correction decoding scheme than LDPC decoding, which would otherwise remain undecoded, UE 120 and network node 110 may communicate with reduced overhead and may encode and decode messages using reduced power consumption, as described.

[0105] As indicated above, Figure 7 are provided as examples. Other examples can be found in relation to Figure 7 The examples described are different.

[0106] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a UE in accordance with the present disclosure. Example process 800 is an example in which a UE (eg, UE 120) performs operations associated with MLC for uplink transmissions.

[0107] like Figure 8 As shown, in some aspects, process 800 may include sending an indication of MLC capability for uplink transmission (block 810). For example, a UE (e.g., using Fig.10 The communications manager 140 and / or transmitting component 1004 depicted in FIG. 1 may transmit an indication of MLC capabilities for uplink transmissions, as described above.

[0108] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include receiving a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on an indication of MLC capability for the uplink transmission (block 820). Fig.10 The communications manager 140 and / or receiving component 1002 depicted in FIG. 1 may receive a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on an indication of MLC capabilities for the uplink transmission, as described above.

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

[0110] In a first aspect, the uplink transmission is associated with a sub-terahertz frequency band.

[0111] In a second aspect, alone or in combination with the first aspect, the indication of the MLC capability sent for the uplink indicates one or more supported MLC schemes.

[0112] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more supported MLC schemes include at least one of a multi-level decoding MLC scheme or a parallel independent decoding MLC scheme.

[0113] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication of the MLC capability sent for the uplink indicates the number of supported MLC levels.

[0114] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the selected MLC scheme is associated with multiple MLC levels, and the configuration of the selected MLC scheme indicates at least one of the number of bits associated with each of the multiple MLC levels or the code rate associated with each of the multiple MLC levels.

[0115] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the selected MLC scheme is associated with multiple MLC levels, and an error protection scheme associated with a first MLC level among the multiple MLC levels is different from an error protection scheme associated with a second MLC level among the multiple MLC levels.

[0116] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the first MLC level is associated with low density parity check coding and the second MLC level is uncoded or associated with Reed-Solomon coding.

[0117] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 800 includes sending an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

[0118] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the one or more recommended MLC parameters include at least one of: a recommended number of bits associated with each of a plurality of MLC levels associated with the selected MLC scheme, a recommended bit rate associated with each of the plurality of MLC levels, a recommended modulation type associated with each of the plurality of MLC levels, or a recommended MLC scheme.

[0119] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, the one or more recommended MLC parameters are based at least in part on at least one of: measurements associated with a channel state information reference signal associated with the same channel, calculations of a decoding probability associated with the channel, a signal-to-noise ratio associated with the channel, a delay spread associated with the channel, a Doppler shift associated with the channel, or information associated with impairment at the UE.

[0120] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the selected MLC scheme is associated with at least one of: a multi-stage decoding MLC scheme, a parallel independent decoding MLC scheme, QAM MCS, or APSK MCS.

[0121] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks of the blocks of process 800 may be performed in parallel.

[0122] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a network node in accordance with the present disclosure. The example process 900 is an example in which a network node (eg, the network node 110) performs operations associated with MLC for uplink transmissions.

[0123] like Fig. 9 As shown in , in some aspects, process 900 may include: receiving an indication of MLC capability for uplink transmission (block 910). For example, a network node (e.g., using Fig.11 The communications manager 150 and / or receiving component 1102 depicted in FIG. 1 may receive an indication of MLC capabilities for uplink transmission, as described above.

[0124] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include sending a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on an indication of MLC capability for the uplink transmission (block 920). For example, a network node (e.g., using Fig.11 The communications manager 150 and / or transmitting component 1104 depicted in FIG. 1 may transmit a configuration of a selected MLC scheme associated with an uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on an indication of MLC capabilities for the uplink transmission, as described above.

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

[0126] In a first aspect, the uplink transmission is associated with a sub-terahertz frequency band.

[0127] In a second aspect, alone or in combination with the first aspect, the indication of the MLC capability sent for the uplink indicates one or more supported MLC schemes.

[0128] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more supported MLC schemes include at least one of a multi-level decoding MLC scheme or a parallel independent decoding MLC scheme.

[0129] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the indication of the MLC capability sent for the uplink indicates the number of supported MLC levels.

[0130] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the selected MLC scheme is associated with multiple MLC levels, and the configuration of the selected MLC scheme indicates at least one of the number of bits associated with each of the multiple MLC levels or the code rate associated with each of the multiple MLC levels.

[0131] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the selected MLC scheme is associated with multiple MLC levels, and an error protection scheme associated with a first MLC level among the multiple MLC levels is different from an error protection scheme associated with a second MLC level among the multiple MLC levels.

[0132] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the first MLC level is associated with low density parity check coding and the second MLC level is uncoded or associated with Reed-Solomon coding.

[0133] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 900 includes receiving an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

[0134] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the one or more recommended MLC parameters include at least one of: a recommended number of bits associated with each of a plurality of MLC levels associated with the selected MLC scheme, a recommended bit rate associated with each of the plurality of MLC levels, a recommended modulation type associated with each of the plurality of MLC levels, or a recommended MLC scheme.

[0135] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, the one or more recommended MLC parameters are based at least in part on at least one of: measurements associated with a channel state information reference signal associated with the same channel, calculations of a decoding probability associated with the channel, a signal-to-noise ratio associated with the channel, a delay spread associated with the channel, a Doppler shift associated with the channel, or information associated with impairments at a network device.

[0136] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the selected MLC scheme is associated with at least one of: a multi-stage decoding MLC scheme, a parallel independent decoding MLC scheme, QAM MCS, or APSK MCS.

[0137] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more of the blocks in the process 900 may be performed in parallel.

[0138] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a UE (e.g., UE 120), or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may use receiving component 1002 and transmitting component 1004 to communicate with another apparatus 1006 (such as a UE, a network node, or another wireless communication device). As further shown, apparatus 1000 may include a communication manager 140. Communication manager 140 may include MLC component 1008, among other things.

[0139] In some aspects, the apparatus 1000 may be configured to perform FIG. 5A to FIG. 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.10 The apparatus 1000 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 One or more components of the described UE 120. Additionally or alternatively, Fig.10 One or more of the components shown in the figure may be combined with Figure 2Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

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

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

[0142] The transmitting component 1004 and / or the MLC component 1008 can transmit an indication of MLC capabilities for uplink transmission. The receiving component 1002 and / or the MLC component 1008 can receive a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of MLC capabilities for the uplink transmission.

[0143] Transmitting component 1004 and / or MLC component 1008 can transmit an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

[0144] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.10 Two or more components shown may be implemented in a single component, or Fig.10 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The component set (one or more components) shown may be described as being executable by Fig.10 Another component shown may be a collection of components that perform one or more functions.

[0145] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a network node (e.g., network node 110), or a network node may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a network node, or another wireless communication device) using receiving component 1102 and sending component 1104. As further shown, apparatus 1100 may include a communication manager 150. Communication manager 150 may include configuration component 1108, etc.

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

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

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

[0149] Receiving component 1102 can receive an indication of MLC capabilities for uplink transmission. Transmitting component 1104 and / or configuring component 1108 can transmit a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of MLC capabilities for the uplink transmission.

[0150] Receiving component 1102 can receive an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

[0151] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The component set (one or more components) shown may be described as being executable by Fig.11 Another component shown may be a collection of components that perform one or more functions.

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

[0153] Aspect 1: A method of wireless communication performed by a UE, the method comprising: sending an indication of MLC capability for uplink transmission; and receiving a configuration of a selected MLC scheme associated with uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

[0154] Aspect 2: The method according to aspect 1, wherein the uplink transmission is associated with a sub-terahertz frequency band.

[0155] Aspect 3: The method according to any one of aspects 1 to 2, wherein the indication of the MLC capability sent for the uplink indicates one or more supported MLC schemes.

[0156] Aspect 4: The method according to aspect 3, wherein the one or more supported MLC schemes include at least one of a multi-stage decoding MLC scheme or a parallel independent decoding MLC scheme.

[0157] Aspect 5: The method according to any one of aspects 1 to 4, wherein the indication of the MLC capability sent for the uplink indicates the number of supported MLC levels.

[0158] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the selected MLC scheme is associated with multiple MLC levels, and wherein the configuration of the selected MLC scheme indicates the number of bits associated with each of the multiple MLC levels and the code rate associated with each of the multiple MLC levels.

[0159] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the selected MLC scheme is associated with multiple MLC levels, and wherein the error protection scheme associated with a first MLC level among the multiple MLC levels is different from the error protection scheme associated with a second MLC level among the multiple MLC levels.

[0160] Aspect 8: The method of aspect 7, wherein the first MLC level is associated with low density parity check coding, and wherein the second MLC level is uncoded or associated with Reed-Solomon coding.

[0161] Aspect 9: The method according to any one of aspects 1 to 8, further comprising: sending an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

[0162] Aspect 10: A method according to Aspect 9, wherein the one or more recommended MLC parameters include at least one of the following: a recommended number of bits associated with each of a plurality of MLC levels associated with the selected MLC scheme, a recommended bit rate associated with each of the plurality of MLC levels, a recommended modulation type associated with each of the plurality of MLC levels, or a recommended MLC scheme.

[0163] Aspect 11: A method according to any one of Aspects 9 to 10, wherein the one or more recommended MLC parameters are based at least in part on at least one of: measurements associated with a channel state information reference signal associated with the same channel, calculations of a decoding probability associated with the channel, a signal-to-noise ratio associated with the channel, a delay spread associated with the channel, a Doppler shift associated with the channel, or information associated with impairment at the UE.

[0164] Aspect 12: The method according to any one of aspects 1 to 11, wherein the selected MLC scheme is associated with at least one of the following: a multi-stage decoding MLC scheme, a parallel independent decoding MLC scheme, QAM MCS, or APSK MCS.

[0165] Aspect 13: A method of wireless communication performed by a network node, the method comprising: receiving an indication of MLC capability for uplink transmission; and sending a configuration of a selected MLC scheme associated with the uplink transmission, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

[0166] Aspect 14: The method of aspect 13, wherein the uplink transmission is associated with a sub-terahertz frequency band.

[0167] Aspect 15: The method according to any one of aspects 13 to 14, wherein the indication of the MLC capability sent for the uplink indicates one or more supported MLC schemes.

[0168] Aspect 16: The method according to aspect 15, wherein the one or more supported MLC schemes include at least one of a multi-stage decoding MLC scheme or a parallel independent decoding MLC scheme.

[0169] Aspect 17: The method according to any one of aspects 13 to 16, wherein the indication of the MLC capability sent for the uplink indicates the number of supported MLC levels.

[0170] Aspect 18: A method according to any one of Aspects 13 to 17, wherein the selected MLC scheme is associated with multiple MLC levels, and wherein the configuration of the selected MLC scheme indicates the number of bits associated with each of the multiple MLC levels and the code rate associated with each of the multiple MLC levels.

[0171] Aspect 19: A method according to any one of Aspects 13 to 18, wherein the selected MLC scheme is associated with multiple MLC levels, and wherein the error protection scheme associated with a first MLC level among the multiple MLC levels is different from the error protection scheme associated with a second MLC level among the multiple MLC levels.

[0172] Aspect 20: The method of aspect 19, wherein the first MLC level is associated with low density parity check coding, and wherein the second MLC level is uncoded or associated with Reed-Solomon coding.

[0173] Aspect 21: The method according to any one of aspects 13 to 20, the method further comprising: receiving an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

[0174] Aspect 22: A method according to Aspect 21, wherein the one or more recommended MLC parameters include at least one of the following: a recommended number of bits associated with each of a plurality of MLC levels associated with the selected MLC scheme, a recommended bit rate associated with each of the plurality of MLC levels, a recommended modulation type associated with each of the plurality of MLC levels, or a recommended MLC scheme.

[0175] Aspect 23: A method according to any one of Aspects 21 to 22, wherein the one or more recommended MLC parameters are based at least in part on at least one of: measurements associated with a channel state information reference signal associated with the same channel, calculations of a decoding probability associated with the channel, a signal-to-noise ratio associated with the channel, a delay spread associated with the channel, a Doppler shift associated with the channel, or information associated with impairments at a network device.

[0176] Aspect 24: The method according to any one of aspects 13 to 23, wherein the selected MLC scheme is associated with at least one of the following: a multi-stage decoding MLC scheme, a parallel independent decoding MLC scheme, QAM MCS, or APSK MCS.

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

[0178] Aspect 26: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 12.

[0179] Aspect 27: 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 12.

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

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

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

[0183] Aspect 31: A device for wireless communication, the device comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 13 to 24.

[0184] Aspect 32: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 13 to 24.

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

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

[0187] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

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

[0189] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

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

[0191] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A may also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending an indication of multi-layer coding (MLC) capability for uplink transmission; and A configuration of a selected MLC scheme associated with an uplink transmission is received, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

2. The apparatus of claim 1, wherein the uplink transmission is associated with a sub-terahertz frequency band.

3. The apparatus of claim 1, wherein the indication of the MLC capability sent for the uplink indicates one or more supported MLC schemes. 4 . The apparatus of claim 3 , wherein the one or more supported MLC schemes include at least one of a multi-stage decoding MLC scheme or a parallel independent decoding MLC scheme.

5. The apparatus of claim 1, wherein the indication of the MLC capability sent for the uplink indicates a number of supported MLC levels.

6. The apparatus of claim 1 , wherein the selected MLC scheme is associated with a plurality of MLC tiers, and wherein the configuration of the selected MLC scheme indicates a number of bits associated with each of the plurality of MLC tiers and a code rate associated with each of the plurality of MLC tiers.

7. The apparatus of claim 1 , wherein the selected MLC scheme is associated with a plurality of MLC tiers, wherein an error protection scheme associated with a first MLC tier of the plurality of MLC tiers is different from an error protection scheme associated with a second MLC tier of the plurality of MLC tiers, wherein the first MLC tier is associated with low-density parity-check coding, and wherein the second MLC tier is uncoded or associated with Reed-Solomon coding.

8. The apparatus of claim 1, wherein the one or more processors are further configured to send an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

9. The apparatus of claim 8, wherein the one or more recommended MLC parameters include at least one of: a recommended number of bits associated with each of a plurality of MLC tiers associated with the selected MLC scheme, a recommended bit rate associated with each of the plurality of MLC levels, a recommended modulation type associated with each of the plurality of MLC levels, or The MLC solution is recommended.

10. The apparatus of claim 8, wherein the one or more recommended MLC parameters are based at least in part on at least one of: measurements associated with a channel state information reference signal associated with the same channel, calculation of a decoding probability associated with the channel, the signal-to-noise ratio associated with the channel, the delay spread associated with the channel, the Doppler shift associated with the channel, or Information associated with impairment at the UE.

11. The apparatus of claim 1 , wherein the selected MLC scheme is associated with at least one of: Multi-level decoding MLC scheme, Parallel independent decoding MLC scheme, Quadrature Amplitude Modulation (QAM) modulation and coding scheme (MCS), or Amplitude and Phase Shift Keying MCS.

12. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving an indication of multi-layer coding (MLC) capability for uplink transmission; and A configuration of a selected MLC scheme associated with an uplink transmission is transmitted, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

13. The apparatus of claim 12, wherein the uplink transmission is associated with a sub-terahertz frequency band.

14. The apparatus of claim 12, wherein the indication of the MLC capability sent for the uplink indicates one or more supported MLC schemes.

15. The apparatus of claim 14, wherein the one or more supported MLC schemes include at least one of a multi-stage decoding MLC scheme or a parallel independent decoding MLC scheme.

16. The apparatus of claim 12, wherein the indication of the MLC capability sent for the uplink indicates a number of supported MLC levels.

17. The apparatus of claim 12, wherein the selected MLC scheme is associated with a plurality of MLC levels, and wherein the configuration of the selected MLC scheme indicates a number of bits associated with each of the plurality of MLC levels and a code rate associated with each of the plurality of MLC levels.

18. The apparatus of claim 12, wherein the selected MLC scheme is associated with a plurality of MLC tiers, wherein an error protection scheme associated with a first MLC tier of the plurality of MLC tiers is different from an error protection scheme associated with a second MLC tier of the plurality of MLC tiers, wherein the first MLC tier is associated with low-density parity-check coding, and wherein the second MLC tier is uncoded or associated with Reed-Solomon coding.

19. The apparatus of claim 12, wherein the one or more processors are further configured to receive an indication of one or more recommended MLC parameters associated with the selected MLC scheme.

20. The apparatus of claim 19, wherein the one or more recommended MLC parameters include at least one of: a recommended number of bits associated with each of a plurality of MLC tiers associated with the selected MLC scheme, a recommended bit rate associated with each of the plurality of MLC levels, a recommended modulation type associated with each of the plurality of MLC levels, or The MLC solution is recommended.

21. The apparatus of claim 19, wherein the one or more recommended MLC parameters are based at least in part on at least one of: measurements associated with a channel state information reference signal associated with the same channel, calculation of a decoding probability associated with the channel, the signal-to-noise ratio associated with the channel, the delay spread associated with the channel, the Doppler shift associated with the channel, or Information associated with impairment at a network device.

22. The apparatus of claim 12, wherein the selected MLC scheme is associated with at least one of: Multi-level decoding MLC scheme, Parallel independent decoding MLC scheme, Quadrature Amplitude Modulation (QAM) modulation and coding scheme (MCS), or Amplitude and Phase Shift Keying MCS.

23. A method of wireless communication performed by a user equipment (UE), the method comprising: sending an indication of multi-layer coding (MLC) capability for uplink transmission; as well as A configuration of a selected MLC scheme associated with an uplink transmission is received, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

24. The method of claim 23, wherein the uplink transmission is associated with a sub-terahertz frequency band.

25. The method of claim 23, wherein the indication of the MLC capability sent for the uplink indicates one or more supported MLC schemes.

26. The method of claim 25, wherein the one or more supported MLC schemes include at least one of a multi-stage decoding MLC scheme or a parallel independent decoding MLC scheme.

27. The method of claim 23, wherein the indication of the MLC capability sent for the uplink indicates a number of supported MLC levels.

28. The method of claim 23, wherein the selected MLC scheme is associated with a plurality of MLC tiers, wherein an error protection scheme associated with a first MLC tier of the plurality of MLC tiers is different from an error protection scheme associated with a second MLC tier of the plurality of MLC tiers, wherein the first MLC tier is associated with low-density parity-check coding, and wherein the second MLC tier is uncoded or associated with Reed-Solomon coding.

29. A method of wireless communication performed by a network node, the method comprising: receiving an indication of multi-layer coding (MLC) capability for uplink transmission; as well as A configuration of a selected MLC scheme associated with an uplink transmission is transmitted, wherein the configuration of the selected MLC scheme is based at least in part on the indication of the MLC capability for the uplink transmission.

30. The method of claim 29, wherein the uplink transmission is associated with a sub-terahertz frequency band.

Images