Patent Grant
11799700
The present disclosure relates generally to communication systems, and more particularly, to communication systems with multi-level coded (MLC).
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a first network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. The memory and the at least one processor coupled to the memory may be further configured to generate a first estimate of a first log-likelihood ratio (LLR) associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. The memory and the at least one processor coupled to the memory may be further configured to decode the first set of bits based on the first estimate of the first LLR. The memory and the at least one processor coupled to the memory may be further configured to generate a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. The memory and the at least one processor coupled to the memory may be further configured to decode the second set of bits based on the fourth estimate of the second LLR. In some aspects, the third estimate of the third LLR is based on an exclusive disjunction (XOR) of a first one or more bits in the first set of bits and a second one or more bits in the second set of bits.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmit receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.
In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.
The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI)/machine learning (ML) (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.
In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies).
At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for a UE 104. The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. 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). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz-71 GHz), FR4 (71 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.
With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102/UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
The base station 102 may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU.
The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location/positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the serving base station 102. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position/location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and/or other systems/signals/sensors.
Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
Referring again to
In certain aspects, the base station 102 may include the decoding component 198.
Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU), a central unit (CU), a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and/or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.
As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to transmit information to a second network node. In this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network node.
For normal CP (14 symbols/slot), different numerologies μ0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2μ slots/subframe. The subcarrier spacing may be equal to 2μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing.
A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
As illustrated in
As illustrated in
The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with decoding component 198 of
At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with decoding component 198 of
For higher order modulation, to achieve a larger spectral efficiency (e.g., compared to binary phase shift keying (BPSK), a bit tuple may be mapped onto one constellation/modulation symbol. Phase shift keying (PSK) may refer to a modulation process which conveys data by modulating the phase of a constant frequency reference signal (e.g., a carrier wave). BPSK may also be referred to as 2PSK and may use two phases which are separated by 180° for modulating the signal. Quadrature amplitude modulation (QAM) may utilize both amplitude and phase components to provide a form of modulation. Based on QAM, a signal in which two carriers shifted in phase by 90 degrees (i.e., sine and cosine) may be modulated and combined. The resultant overall signal may include a combination of both in-phase (I) (e.g., cosine waveform) and quadrature (Q) (e.g., sine waveform) carriers and may include both amplitude and phase variations.
Depending on how each bit in the bit tuple are mapped to a constellation point, the reliability of the bits may be different.
MLC or multi-stage coding (MSC) may use separate channel codes on the bits that are mapped to different levels of the constellation points. For example, in the 64QAM example, the last 4 bits (least significant bits (LSBs)) can be jointly encoded with one codeword, and the first two bits (most significant bits (MSBs)) may be encoded with a second codeword, or may be uncoded. An advantage of MLC is that a simple code (or uncode) may be applied on the MSBs, resulting in less encoding/decoding complexity and less computing resource utilization on both the encoder and the decoder. However, at the receiver end, a multi-staging decoding may be employed to decode communications transmitted based on MSC.
LDPC may be a linear error correcting method. A LDPC code may be specified by a parity-check matrix containing mostly 0s and a low density of 1s. The rows of the matrix may represent the equations and the columns represent the bits in the codeword, i.e., code symbols. A LDPC code may be represented by, where the block length may be the number of 1s in each column and may be the number of 1s in each row, holding the following properties: j is the small fixed number of 1's in each column, where j>3, k is the small fixed number of 1's in each row, where k>j. A RS code may be a family of codes where every code is characterized by three parameters: an alphabet size q, a block length n, and a message length k, with k<n≤q. The set of alphabet symbols may be interpreted as a finite field of order q, and thus, q is a prime power.
A result of the first channel coding 504A and a result of the second channel coding 504B may be modulated at modulation 506. After modulation 506, the modulated signal may be transmitted via a channel 508 to a receiver. At the receiver, the receiver may perform a first level demodulation 512A and then a first level decode 514A. For example, the receiver may first demodulate the LSBs and decode the LSBs. A result of the first level decode 514A may be used for a second level demodulation 512B. For example, the decoded LSBs may be feed into the demodulator for re-performing the demodulation of the MSBs. Performance at the receiver may suffer if all of the bits are demodulated at once without further post-processing instead of separate at first level demodulation 512A and second level demodulation 512B. A result of the second level demodulation 512B may be decoded at second level decode 514B. The information bits and CRC bits 516 may be accordingly decoded. However, such type of multi-stage decoding, for some demodulators (e.g., a nonlinear MIMO demodulator), the complexity and computing resource cost of the demodulation may be high. Aspects provided herein provide mechanisms for multi-level/multi-stage demodulation and decoding with a lower complexity and computing resource cost.
Compared with the architecture in
), a second estimate of LLR of b0 (e.g., second estimate of LLR for the bits on level 2 622) may be generated based on: LLRpost(b0)=LLRinitial(b0)+(−1)
LLRinitial(b0⊕b1), where LLRinitial may denote initial LLR estimate and LLRpost may denote LLR estimate after decoding the bits on level 1. The initial estimate of the LLR for level 2, the decoded bits for level 1, and the auxiliary information 612 are used together to generate a more accurate second estimate of LLR for the bits on level 2 622 after the decoded bits for level 1 are known to the network entity 604.
To generate the auxiliary information 612, such as LLRs for b0 XOR b1, consider a 16QAM (which may also be 4-pulse amplitude modulation (4PAM)) example illustrated in
where C0 and C1 denote the subset of constellation points with b0 XOR b1=0 and 1, respectively, and y denotes the received signal (e.g., after proper equalization). As illustrated in
), a second estimate of LLR of b0 (e.g., second estimate of LLR for the bits on level 2 622) may be generated based on: LLRpost(b0)=LLRinitial(b0)+(−1)
LLRinitial(b0⊕b1). The initial estimate of the LLR for level 2, the decoded subset of bits for level 1, and the auxiliary information 612 are used together to generate a more accurate second estimate of LLR for the bits on level 2 622 after the decoded subset of bits for level 1 are known to the network entity 604.
In some aspects, the network entity 604 may generate the auxiliary information 612 as both LLR(b0⊕b2) and LLR(b1⊕b2). After decoding b1 (e.g., at decode bits on level 1 616), the network entity 604 may decode b0 and b1 separately with the following formula: LLRpost(bj)=LLRinitial(bj)+(−1)LLRinitial(bj⊕b2), where j=0 or 1. In other words, different second estimate of LLR for the bits on level 2 622 may be generated for different subsets of bits at level 2 based on different initial estimates of LLR for level 2 for the different subsets of bits at level 2 614, different part of the auxiliary information 612, and the decoded bits on level 1 618.
At 802, the network entity may receive a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. For example, the network entity 604 may receive a communication 606 from a network entity 602 via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. In some aspects, 802 may be performed by decoding component 198.
At 804, the network entity may generate a first estimate of a first LLR associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. For example, the network entity 604 may generate a first estimate of a first LLR (e.g., 610) associated with the first coding level, a second estimate of a second LLR (e.g., 614) associated with the second coding level, and auxiliary information (e.g., 612) including a third estimate of a third LLR based on the first set of bits and the second set of bits. In some aspects, 804 may be performed by decoding component 198. In some aspects, the third estimate of the third LLR is based on an XOR of the first set of bits and the second set of bits. In some aspects, the third estimate of the third LLR is based on an XOR of a first bit in the first set of bits and a second bit in the second set of bits. In some aspects, the third estimate of the third LLR is based on an XOR of a first one or more bits in the first set of bits and a second one or more bits in the second set of bits. In some aspects, the first one or more bits correspond to the first set of bits or a first subset of the first set of bits, and where the second one or more bits correspond to the second set of bits or a second subset of the second subset of bits. In some aspects, the first one or more bits of the first subset of bits and the second one or more bits of the second subset of bits are selected such that the XOR achieve a same value for at least one pair of constellations in which a bit differs. In some aspects, the pair of constellations have a minimum distance among all constellations in a set of modulation constellations associated with the communication. In some aspects, the auxiliary information may include a fifth estimate of a fifth LLR based on the first set of bits and the second set of bits, where the third estimate of the third LLR is based on a first exclusive disjunction of a first one or more bits in the first set of bits and a second one or more bits the second set of bits, and where the fifth estimate of the fifth LLR is based on a second exclusive disjunction of a third one or more bits in the first set of bits and a fourth one or more bits the second set of bits, where the first one or more bits is different from the third one or more bits or the second one or more bits is different from the fourth one or more bits. In some aspects, the auxiliary information is based on a standard log-map or a maximum-log-map based on exclusive disjunction (XOR) of a first one or more bits in the first set of bits and a second one or more bits in the second set of bits.
At 806, the network entity may decode the first set of bits based on the first estimate of the first LLR. For example, the network entity 604 may decode (e.g., 616) the first set of bits based on the first estimate of the first LLR. In some aspects, 806 may be performed by decoding component 198.
At 808, the network entity may generate a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. For example, the network entity 604 may generate (e.g., 620) a fourth estimate of the second LLR (e.g., 622) based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. In some aspects, 808 may be performed by decoding component 198. In some aspects, the fourth estimate of the second LLR is based on a sum of (1) the second estimate of the second LLR and (2) negative one to a power of the decoded first set of bits multiplied by the third estimate of the third LLR.
At 810, the network entity may decode the second set of bits based on the fourth estimate of the second LLR. For example, the network entity 604 may decode (e.g., 624) the second set of bits based on the fourth estimate of the second LLR. In some aspects, 810 may be performed by decoding component 198.
As discussed herein, the decoding component 198 may be configured to receive a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. In some aspects, the decoding component 198 may be further configured to generate a first estimate of a first log-likelihood ratio (LLR) associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. In some aspects, the decoding component 198 may be further configured to decode the first set of bits based on the first estimate of the first LLR. In some aspects, the decoding component 198 may be further configured to generate a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. In some aspects, the decoding component 198 may be further configured to decode the second set of bits based on the fourth estimate of the second LLR. The decoding component 198 may be within the cellular baseband processor 924, the application processor 906, or both the cellular baseband processor 924 and the application processor 906. The decoding component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus 904 may include a variety of components configured for various functions. In one configuration, the apparatus 904, and in particular the cellular baseband processor 924 and/or the application processor 906, includes means for receiving a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. In some aspects, the apparatus 904 may further include means for generating a first estimate of a first LLR associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. In some aspects, the apparatus 904 may further include means for decoding the first set of bits based on the first estimate of the first LLR. In some aspects, the apparatus 904 may further include means for generating a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. In some aspects, the apparatus 904 may further include means for decoding the second set of bits based on the fourth estimate of the second LLR. The means may be the decoding component 198 of the apparatus 904 configured to perform the functions recited by the means. As described herein, the apparatus 904 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the means.
As discussed herein, the decoding component 198 may be configured to receive a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. In some aspects, the decoding component 198 may be further configured to generate a first estimate of a first log-likelihood ratio (LLR) associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. In some aspects, the decoding component 198 may be further configured to decode the first set of bits based on the first estimate of the first LLR. In some aspects, the decoding component 198 may be further configured to generate a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. In some aspects, the decoding component 198 may be further configured to decode the second set of bits based on the fourth estimate of the second LLR. The decoding component 198 may be within one or more processors of one or more of the CU 1010, DU 1030, and the RU 1040. The decoding component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1002 may include a variety of components configured for various functions. In one configuration, the network entity 1002 includes means for means for receiving a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. In some aspects, the network entity 1002 may further include means for generating a first estimate of a first LLR associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. In some aspects, the network entity 1002 may further include means for decoding the first set of bits based on the first estimate of the first LLR. In some aspects, the network entity 1002 may further include means for generating a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. In some aspects, the network entity 1002 may further include means for decoding the second set of bits based on the fourth estimate of the second LLR. The means may be the decoding component 198 of the network entity 1002 configured to perform the functions recited by the means. As described herein, the network entity 1002 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.
As discussed herein, the decoding component 198 may be configured to receive a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. In some aspects, the decoding component 198 may be further configured to generate a first estimate of a first log-likelihood ratio (LLR) associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. In some aspects, the decoding component 198 may be further configured to decode the first set of bits based on the first estimate of the first LLR. In some aspects, the decoding component 198 may be further configured to generate a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. In some aspects, the decoding component 198 may be further configured to decode the second set of bits based on the fourth estimate of the second LLR. The component 198 may be within the processor 1112. The component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1160 may include a variety of components configured for various functions. In one configuration, the network entity 1160 includes means for receiving a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits. In some aspects, the network entity 1160 may further include means for generating a first estimate of a first LLR associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits. In some aspects, the network entity 1160 may further include means for decoding the first set of bits based on the first estimate of the first LLR. In some aspects, the network entity 1160 may further include means for generating a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information. In some aspects, the network entity 1160 may further include means for decoding the second set of bits based on the fourth estimate of the second LLR. The means may be the component 198 of the network entity 1160 configured to perform the functions recited by the means.
It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”
As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
Aspect 1 is a first network entity for communication, including: a memory; and at least one processor coupled to the memory, where the at least one processor is configured to: receive a communication from a second network entity via a channel, where the communication is encoded based on multi-level coding associated with at least a first coding level and a second coding level, and where the first coding level is associated with a first set of bits and the second coding level is associated with a second set of bits; generate a first estimate of a first log-likelihood ratio (LLR) associated with the first coding level, a second estimate of a second LLR associated with the second coding level, and auxiliary information including a third estimate of a third LLR based on the first set of bits and the second set of bits; decode the first set of bits based on the first estimate of the first LLR; generate a fourth estimate of the second LLR based on the decoded first set of bits, the second estimate of the second LLR, and the auxiliary information; and decode the second set of bits based on the fourth estimate of the second LLR.
Aspect 2 is the first network entity of aspect 1, where the third estimate of the third LLR is based on an exclusive disjunction (XOR) of the first set of bits and the second set of bits.
Aspect 3 is the first network entity of any of aspects 1-2, where the third estimate of the third LLR is based on an exclusive disjunction (XOR) of a first bit in the first set of bits and a second bit in the second set of bits.
Aspect 4 is the first network entity of any of aspects 1-3, where the third estimate of the third LLR is based on an exclusive disjunction (XOR) of a first one or more bits in the first set of bits and a second one or more bits in the second set of bits.
Aspect 5 is the first network entity of any of aspects 1-4, where the first one or more bits correspond to the first set of bits or a first subset of the first set of bits, and where the second one or more bits correspond to the second set of bits or a second subset of the second subset of bits.
Aspect 6 is the first network entity of any of aspects 1-5, where the first one or more bits of the first subset of bits and the second one or more bits of the second subset of bits are selected such that the XOR achieve a same value for at least one pair of constellations in which a bit differs.
Aspect 7 is the first network entity of any of aspects 1-6, where the pair of constellations have a minimum distance among all constellations in a set of modulation constellations associated with the communication.
Aspect 8 is the first network entity of any of aspects 1-7, where the auxiliary information includes a fifth estimate of a fifth LLR based on the first set of bits and the second set of bits, where the third estimate of the third LLR is based on a first exclusive disjunction of a first one or more bits in the first set of bits and a second one or more bits the second set of bits, and where the fifth estimate of the fifth LLR is based on a second exclusive disjunction of a third one or more bits in the first set of bits and a fourth one or more bits the second set of bits, where the first one or more bits is different from the third one or more bits or the second one or more bits is different from the fourth one or more bits.
Aspect 9 is the first network entity of any of aspects 1-8, where the fourth estimate of the second LLR is based on a sum of (1) the second estimate of the second LLR and (2) negative one to a power of the decoded first set of bits multiplied by the third estimate of the third LLR.
Aspect 10 is the first network entity of any of aspects 1-9, where the auxiliary information is based on a standard log-map or a maximum-log-map based on exclusive disjunction (XOR) of a first one or more bits in the first set of bits and a second one or more bits in the second set of bits.
Aspect 11 is a method of wireless communication for implementing any of aspects 1 to 10.
Aspect 12 is an apparatus for wireless communication including means for implementing any of aspects 1 to 10.
Aspect 13 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 10.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7860194 | Kim | Dec 2010 | B2 |
| 7885367 | Nishimura | Feb 2011 | B2 |
| 8135082 | Choi | Mar 2012 | B2 |
| 8238488 | Lee | Aug 2012 | B1 |
| 8411806 | Lee | Apr 2013 | B1 |
| 8699607 | Seller | Apr 2014 | B2 |
| 8792594 | Vojcic | Jul 2014 | B2 |
| 8943384 | Sridhara | Jan 2015 | B2 |
| 8958375 | Watson | Feb 2015 | B2 |
| 8989299 | Zhou | Mar 2015 | B2 |
| 9191080 | Yokomakura | Nov 2015 | B2 |
| 9191151 | Luby | Nov 2015 | B2 |
| 9209934 | Luby | Dec 2015 | B2 |
| 9253233 | Luby | Feb 2016 | B2 |
| 9294226 | Luby | Mar 2016 | B2 |
| 9380096 | Luby | Jun 2016 | B2 |
| 9386064 | Luby | Jul 2016 | B2 |
| 9419749 | Luby | Aug 2016 | B2 |
| 9432433 | Luby | Aug 2016 | B2 |
| 9473332 | Bajcsy | Oct 2016 | B2 |
| 9491026 | Murakami | Nov 2016 | B2 |
| 9596447 | Chen | Mar 2017 | B2 |
| 9602802 | Chen | Mar 2017 | B2 |
| 9628536 | Luby | Apr 2017 | B2 |
| 9660763 | Luby | May 2017 | B2 |
| 9692630 | Qi | Jun 2017 | B2 |
| 9876607 | Luby | Jan 2018 | B2 |
| 9917874 | Luby | Mar 2018 | B2 |
| 10135649 | Soriano | Nov 2018 | B2 |
| 10312937 | Loncke | Jun 2019 | B2 |
| 10396819 | Myung | Aug 2019 | B1 |
| 10536196 | Geng | Jan 2020 | B2 |
| 10749633 | Xu | Aug 2020 | B2 |
| 10778371 | Loncke | Sep 2020 | B2 |
| 10855736 | Luby | Dec 2020 | B2 |
| 10868569 | Sadiq | Dec 2020 | B2 |
| 10944517 | Li | Mar 2021 | B2 |
| 10965360 | Schenk | Mar 2021 | B2 |
| 11201775 | Lopez | Dec 2021 | B2 |
| 11218352 | Park | Jan 2022 | B2 |
| 11362769 | Xu | Jun 2022 | B2 |
| 11398936 | Martinez | Jul 2022 | B2 |
| 11411678 | Chen | Aug 2022 | B2 |
| 11469854 | Wu | Oct 2022 | B2 |
| 11477253 | Luby | Oct 2022 | B2 |
| 11621726 | Pan | Apr 2023 | B1 |
| 11646828 | Li | May 2023 | B2 |
| 20080016425 | Khan | Jan 2008 | A1 |
| 20100034323 | Stoye | Feb 2010 | A1 |
| 20100067596 | Park | Mar 2010 | A1 |
| 20100316151 | Fukawa | Dec 2010 | A1 |
| 20140153625 | Vojcic | Jun 2014 | A1 |
| 20140153628 | Vojcic | Jun 2014 | A1 |
| 20150341053 | Kim | Nov 2015 | A1 |
| 20150341054 | Myung | Nov 2015 | A1 |
| 20160344415 | Kim | Nov 2016 | A1 |
| 20160344423 | Kim | Nov 2016 | A1 |
| 20170262334 | Uchikawa | Sep 2017 | A1 |
| 20180069734 | Soriano | Mar 2018 | A1 |
| 20180123734 | Loncke | May 2018 | A1 |
| 20180323804 | Sadiq | Nov 2018 | A1 |
| 20190007255 | Limberg | Jan 2019 | A1 |
| 20190305801 | Kim | Oct 2019 | A1 |
| 20190334755 | Limberg | Oct 2019 | A1 |
| 20210152290 | Li | May 2021 | A1 |
| 20210152412 | Park | May 2021 | A1 |
| 20220312250 | Elshafie | Sep 2022 | A1 |
| 20220353203 | Rico Alvarino | Nov 2022 | A1 |
| 20230084537 | Pan | Mar 2023 | A1 |
