Techniques for determining coding tables for encoding in wireless communications

Abstract

Aspects described herein relate to encoding uplink communications based on a coding table, including determining to avoid portions of a coding table that may result in decoding errors or using a modified coding table to improve decoding results. In one aspect, a network can send a configuration to a device indicating whether to use a modified coding table to encode uplink communications.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims priority to Provisional Patent Application No. 63 / 011,798, entitled "TECHNIQUES FOR DETERMINING A CODING TABLE FOR ENCODING IN WIRELESS COMMUNICATIONS," filed April 17, 2020, and U.S. Patent Application No. 17 / 229,361, entitled "TECHNIQUES FOR DETERMINING A CODING TABLE FOR ENCODING IN WIRELESS COMMUNICATIONS," filed April 13, 2021, which are assigned to the assignee of the present application and are expressly incorporated herein by reference for all purposes.

[0002] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to coding of wireless communications. [Background technology]

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasts, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems 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, and single-carrier frequency division multiple access (SC-FDMA) systems.

[0004] These multiple access technologies are being adopted in various telecommunications standards to provide common protocols that enable different wireless devices to communicate on a city, national, regional, or even global scale. For example, fifth-generation (5G) wireless communication technologies (sometimes referred to as 5G New Radio (5G NR)) are envisioned to enhance and support diverse usage scenarios and applications for current mobile network generations. In one aspect, 5G communication technologies can include enhanced mobile broadband that addresses human-centric use cases for accessing multimedia content, services, and data; ultra-reliable-low latency communications (URLLC) with several specifications for latency and reliability; and massive machine-type communications that can enable a very large number of connected devices and the transmission of information that is not affected by relatively small amounts of delay.

[0005] In some wireless communication technologies, such as 5G NR, uplink control information (UCI) is encoded using a Reed-Muller (RM) code based on a coding table. A user equipment (UE) can be configured with the coding table and can determine a submatrix of the coding table for encoding UCI by taking some columns representing payload sizes and some rows representing desired code lengths from the coding table. Summary of the Invention [Means for solving the problem]

[0006] 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 exhaustive overview of all contemplated aspects, nor does it identify key or critical elements of all aspects or delineate 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.

[0007] According to one aspect, an apparatus for wireless communication is provided, including a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the memory and the transceiver, wherein the one or more processors are configured to: receive, from a base station, control information scheduling uplink communication, the control information indicating a payload size and a code length for encoding the uplink communication based on a code; and trigger an error case if the payload size and code length pair is deemed undesirable for performing the encoding.

[0008] In another aspect, an apparatus for wireless communication includes a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the memory and the transceiver. The one or more processors are configured to: receive from a base station a configuration indicating whether to use a modified coding table to encode uplink communications; receive from the base station control information scheduling the uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications; if the configuration indicates using the modified coding table, encode the uplink communications based on the modified coding table based on the payload size and the code length; if the configuration indicates using the unmodified coding table, encode the uplink communications using the unmodified coding table based on the payload size and the code length; and transmit the encoded uplink communications.

[0009] In another aspect, a method for wireless communication is provided that includes receiving, from a base station, control information scheduling uplink communication, the control information indicating a payload size and a code length for encoding the uplink communication based on a code; and triggering an error case if the payload size and code length pair is deemed undesirable for performing the encoding.

[0010] In another aspect, a method for wireless communication is provided that includes receiving, from a base station, a configuration indicating whether to use a modified coding table for encoding uplink communications; receiving, from the base station, control information scheduling the uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications; if the configuration indicates using the modified coding table, encoding the uplink communications based on the modified coding table based on the payload size and the code length; if the configuration indicates using an unmodified coding table, encoding the uplink communications using the unmodified coding table based on the payload size and the code length; and transmitting the encoded uplink communications.

[0011] In a further aspect, an apparatus for wireless communication is provided, including a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors are configured to execute instructions for performing the operations of the methods described herein. In another aspect, an apparatus for wireless communication is provided, including means for performing the operations of the methods described herein. In yet another aspect, a computer-readable medium is provided, including code executable by one or more processors to perform the operations of the methods described herein.

[0012] 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 annexed 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 the various aspects may be employed, and the description is intended to include all such aspects and their equivalents.

[0013] The disclosed aspects are described below with reference to the accompanying drawings, in which like designations refer to like elements, and in which: FIG. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 illustrates an example of a wireless communication system in accordance with various aspects of the present disclosure. [Figure 2] FIG. 1 is a block diagram illustrating an example of a UE, in accordance with various aspects of the present disclosure. [Figure 3] FIG. 2 is a block diagram illustrating an example of a base station, in accordance with various aspects of the present disclosure. [Figure 4] FIG. 1 illustrates an example of a Reed-Muller coding table defined for use in several radio access technologies, in accordance with various aspects of the present disclosure. [Figure 5] 1 is a flowchart illustrating an example of a method for encoding uplink communications by avoiding certain payload size and code length pairs, in accordance with various aspects of the present disclosure. [Figure 6] 1 is a flowchart illustrating an example of a method for encoding uplink communications using a modified coding table, in accordance with various aspects of the present disclosure. [Figure 7] 1 is a flowchart illustrating an example of a method for configuring a user equipment to encode uplink communications using a modified coding table, in accordance with various aspects of the present disclosure. [Figure 8] FIG. 1 is a block diagram illustrating an example of a MIMO communication system including a base station and a UE, in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0015] Various embodiments will now be described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more embodiments. It will be apparent, however, that such embodiments may be practiced without these specific details.

[0016] The described features generally relate to encoding communications based on a coding table. In one example, in fifth generation (5G) New Radio (NR), a coding table used by a user equipment (UE), base station, or other device to encode a communication may have several rows representing payload sizes to be encoded and several columns representing desired code lengths. The device may select a submatrix of the coding table for encoding the communication based on the payload size and desired code length pair. Some coding tables, such as the Reed-Muller (RM) coding table designated for use in encoding uplink control information (UCI) in 5G NR, may have columns with several repeated consecutive values. Thus, for example, some pairs of payload size (also referred to herein as K) and desired code length (also referred to herein as N) may not yield the desired coding results. For example, if a coding table for several K×N submatrices has columns with repeated consecutive values ​​that are similar across multiple columns, this may prevent a device receiving the encoded information from differentiating some of the coded bits. This may lead to unsuccessful decoding of the information. In another example, some pairs of payload size (also referred to herein as K) and desired code length may result in a coding table that has all zeros for certain bits, which may also lead to unsuccessful decoding of the information.

[0017] In aspects described herein, for UCI to be coded, a base station can avoid scheduling a user equipment (UE) with an undesirable (K, N) pair, and / or the UE can consider receiving scheduling with an undesirable (K, N) pair to be an error case. In other aspects described herein, a UE can use a modified coding table having different values ​​for the (K, N) pair from an original, unmodified coding table that is deemed undesirable for coding uplink communications at the UE. In one aspect, the modified coding table can be stored in the UE, configured by the base station, etc., and / or the base station can configure the UE to use the modified coding table instead of the unmodified coding table. In another aspect, the UE can generate the modified coding table based on permuting rows of the unmodified coding table to avoid the presence of the undesirable pair. In another aspect, the UE can encode uplink communications based on the modified coding table by interleaving the coding before performing rate matching if the coding could be generated based on the unmodified coding table. In either case, the base station may also configure the UE with an indication to perform permutation / interleaving, parameters or other instructions for performing permutation / interleaving, etc.

[0018] Aspects described herein provide advantages for encoding wireless communications of substantially any payload size and code length without encountering errors that may arise from a receiving device being unable to distinguish between information bits when receiving the communications, which can improve the throughput of the wireless communications, at least for some pairs of payload size and desired code length.

[0019] The described features are presented in more detail below with reference to FIGS.

[0020] As used herein, terms such as “component,” “module,” and “system” are intended to include computer-related entities, such as, but not limited to, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer. By way of example, both an application running on a computing device and the computing device may be a component. One or more components may reside within a process and / or thread of execution, and a component may be localized on one computer and / or distributed between two or more computers. In addition, these components may execute from various computer-readable media having various data structures stored thereon. A component may communicate with local and / or remote processes, such as by following a signal carrying one or more data packets, such as data from one component interacting with another component in a local system, a distributed system, and / or over a network such as the Internet.

[0021] The techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system may implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA system may implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). 3GPP® Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above, as well as other systems and radio technologies, including cellular (e.g., LTE) communications over shared radio frequency spectrum bands.However, although the following description describes LTE / LTE-A systems as an example, and LTE terminology is used in much of the following description, the techniques are applicable to applications other than LTE / LTE-A (e.g., to fifth-generation (5G) New Radio (NR) networks or other next-generation communication systems).

[0022] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of the elements described without departing from the scope of the present disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in other examples.

[0023] Various aspects or features will be presented in terms of systems that may include several devices, components, modules, etc. It is to be understood and appreciated that various systems may include additional devices, components, modules, etc. and / or may not include all of the devices, components, modules, etc. described in connection with the figures. Combinations of these approaches may also be used.

[0024] FIG. 1 illustrates an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base station 102 may include a macrocell (high-power cellular base station) and / or a small cell (low-power cellular base station). A macrocell may include a base station. A small cell may include a femtocell, a picocell, and a microcell. In one example, the base station 102 may also include a gNB 180, as described further herein. In one example, some nodes of the wireless communication system may have a modem 240 and a communication component 242 for encoding uplink communications based on determining a coding table and / or based on a payload size and code length pair, according to aspects described herein. Additionally, some nodes may have a modem 340 and a configuration component 342 for configuring the device to encode uplink communications, according to aspects described herein. While the UE 104 is shown as having a modem 240 and communications components 242 and the base station 102 / gNB 180 is shown as having a modem 340 and communications components 342, this is one illustrative example and substantially any node or substantially any type of node may include a modem 240 and communications components 242 and / or a modem 340 and communications components 342 to provide the corresponding functionality described herein.

[0025] A base station 102 configured for 4G LTE (which may be collectively referred to as an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 over a backhaul link 132 (e.g., using an S1 interface). A base station 102 configured for 5G NR (which may be collectively referred to as a Next Generation RAN (NG-RAN)) may interface with the 5G NR Card 190 over a backhaul link 184. In addition to other functions, the base station 102 may perform one or more of the following functions: transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast services (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or the 5GC 190) with each other over backhaul links 134 (e.g., using an X2 interface). The backhaul links 134 may be wired or wireless.

[0026] The base stations 102 may communicate wirelessly with one or more UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolved Node B (eNB) (HeNB) that may serve a restricted group, sometimes referred to as a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also referred to as reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may use spectrum with a bandwidth of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) allocated in carrier aggregation of up to Yx MHz total (e.g., for x component carriers) used for transmission in the DL and / or UL directions. The carriers may be adjacent or non-adjacent to each other. The carrier allocation 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. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0027] In another example, several UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL WWAN spectrum. The D2D communication links 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). The D2D communication may be through various wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0028] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 via a communication link 154 in the 5 GHz unlicensed frequency spectrum. When communicating in the unlicensed frequency spectrum, the STA 152 / AP 150 may perform clear channel assessment (CCA) before communicating to determine if the channel is available.

[0029] The small cell 102' may operate in licensed and / or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum used by the Wi-Fi AP 150. A small cell 102' employing NR in the unlicensed frequency spectrum may extend coverage to and / or increase the capacity of the access network.

[0030] The base station 102, whether a small cell 102′ or a large cell (e.g., a macro base station), may include an eNB, a gNodeB (gNB), or other type of base station. Some base stations, such as the gNB 180, communicate with the UE 104 and may operate in the traditional sub-6 GHz spectrum, at millimeter wave (mmW) frequencies, and / or at sub-mmW frequencies. When the gNB 180 operates at mmW or sub-mmW frequencies, it may be referred to as an mmW base station. Extremely high frequency (EHF) is the RF portion of the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in that band are sometimes referred to as millimeter waves. Sub-mmW has a wavelength of 100 millimeters and can extend up to frequencies of 3 GHz. The very high frequency (SHF) band, also known as centimeter wave, extends between 3 GHz and 30 GHz. Communications using the mmW / sub-mmW radio frequency bands have extremely high path loss and short distances. The mmW base station 180 may utilize beamforming 182 to compensate for the extremely large path loss and short distance to the UE 104. The base station 102 referred to herein may include a gNB 180.

[0031] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are forwarded through the serving gateway 166, which is itself connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP services 176. The IP services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and start MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a particular service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0032] The 5GC 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with an Integrated Data Management (UDM) 196. The AMF 192 may be a control node that handles signaling between the UE 104 and the 5GC 190. In general, the AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be forwarded through the UPF 195. The UPF 195 may provide UE IP address allocation and other functions for one or more UEs. The UPF 195 is connected to IP services 197. The IP services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0033] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or 5GC 190 for the UE 104. Examples of UEs 104 include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). IoT UEs may include machine type communication (MTC) / enhanced MTC (eMTC, also referred to as Category (CAT)-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. In this disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc.The UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0034] In one example, the configuration component 342 can configure the UE 104 with resources for transmitting uplink communications, such as UCI, where the resource configuration can include or be otherwise associated with an indication of a payload size and code length for encoding the uplink communications. In one example, the communication component 242 can receive an indication of the resources and / or receive or determine a corresponding payload size and code length, and then the communication component 242 can determine whether to encode the uplink communications based on the payload size and code length pair. In another example, the communication component 242 can determine whether to use a modified coding table to encode the uplink communications, which can be based on instructions and / or commands or parameters received from the base station 102 via the configuration component 342.

[0035] 2-8, aspects are illustrated with respect to one or more components and one or more methods that may perform the actions or operations described herein, with aspects within dashed lines being optional. While the operations described below in FIGS. 5-7 are presented as being performed in a particular order and / or by example components, it should be understood that the order of actions and the components performing the actions may vary depending on the implementation. Furthermore, it should be understood that the actions, functions, and / or components described below may be performed by a specially programmed processor, a processor executing specially programmed software, or a computer-readable medium, or by any other combination of hardware and / or software components capable of performing the described actions or functions.

[0036] Referring to FIG. 2, one example of an implementation of a UE 104 can include various components, some of which have already been described above and will be further described herein, including components such as one or more processors 212 and memories 216 and transceivers 202 communicating via one or more buses 244, which can operate in conjunction with a modem 240 and / or a communication component 242 for encoding uplink communications based on determining coding tables and / or based on payload size and code length pairs, in accordance with aspects described herein.

[0037] In one aspect, the one or more processors 212 may include the modem 240 and / or may be part of the modem 240 using one or more modem processors. Thus, various functions related to the communications component 242 may be included in the modem 240 and / or the processor 212, and in one aspect may be performed by a single processor, while in other aspects different ones of the functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 212 may include any one or combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with the transceiver 202. In other aspects, some of the features of the one or more processors 212 associated with the communications component 242 and / or the modem 240 may be performed by the transceiver 202.

[0038] The memory 216 may also be configured to store local versions of the data and / or applications 275 used herein, or one or more of the communications component 242 and / or its subcomponents executed by the at least one processor 212. The memory 216 may include any type of computer-readable medium usable by a computer or the at least one processor 212, such as random access memory (RAM), read-only memory (ROM), tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In one aspect, for example, the memory 216 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining the communications component 242 and / or one or more of its subcomponents and / or data associated therewith when the UE 104 operates the at least one processor 212 to execute the communications component 242 and / or one or more of its subcomponents.

[0039] The transceiver 202 may include at least one receiver 206 and at least one transmitter 208. The receiver 206 may include hardware, firmware, and / or software code executable by a processor to receive data, where the code comprises instructions and is stored in a memory (e.g., a computer-readable medium). The receiver 206 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 206 may receive signals transmitted by at least one base station 102. Additionally, the receiver 206 may process such received signals and obtain signal measurements, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 208 may include hardware, firmware, and / or software code executable by a processor to transmit data, where the code comprises instructions and is stored in a memory (e.g., a computer-readable medium). A suitable example of the transmitter 208 may include, but is not limited to, an RF transmitter.

[0040] Additionally, in an aspect, the UE 104 may include an RF front end 288 that may be in operative communication with one or more antennas 265 and a transceiver 202 for receiving and transmitting radio transmissions, e.g., wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 288 may be connected to the one or more antennas 265 and may include one or more low noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals.

[0041] In one aspect, the LNAs 290 can amplify the received signal at a desired power level. In one aspect, each LNA 290 can have a specified minimum and maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular LNA 290 and its specified gain value based on the desired gain value for a particular application.

[0042] Additionally, one or more PAs 298 may be used by the RF front end 288, for example, to amplify a signal for RF output at a desired output power level. In one aspect, each PA 298 may have a specified minimum and maximum gain value. In one aspect, the RF front end 288 may use one or more switches 292 to select a particular PA 298 and its specified gain value based on the desired gain value for a particular application.

[0043] Additionally, one or more filters 296 may be used by the RF front end 288, for example, to filter a received signal to obtain an input RF signal. Similarly, in an aspect, each filter 296 may be used to filter an output from a respective PA 298, for example, to generate an output signal for transmission. In an aspect, each filter 296 may be connected to a particular LNA 290 and / or PA 298. In an aspect, the RF front end 288 may use one or more switches 292 to select a transmit path or a receive path using a specified filter 296, LNA 290, and / or PA 298 based on a configuration specified by the transceiver 202 and / or processor 212.

[0044] Accordingly, the transceiver 202 may be configured to transmit and receive wireless signals through one or more antennas 265 via the RF front end 288. In one aspect, the transceiver may be tuned to operate at a designated frequency such that the UE 104 can communicate with, for example, one or more base stations 102, or one or more cells associated with one or more base stations 102. In one aspect, for example, the modem 240 may configure the transceiver 202 to operate at a designated frequency and power level based on the UE configuration of the UE 104 and the communication protocol used by the modem 240.

[0045] In one aspect, the modem 240 may be a multi-band, multi-mode modem capable of processing digital data and communicating with the transceiver 202 so that the digital data is sent and received using the transceiver 202. In one aspect, the modem 240 may be multi-band and configured to support multiple frequency bands for a particular communication protocol. In one aspect, the modem 240 may be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 240 may control one or more components of the UE 104 (e.g., the RF front end 288, the transceiver 202) to enable transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the modem's mode and the frequency band in use. In another aspect, the modem configuration may be based on UE configuration information associated with the UE 104 provided by the network during cell selection and / or cell reselection.

[0046] In an aspect, the communications component 242 may optionally include an encoding component 252 for encoding uplink communications and / or a coding table determination component 254 for determining or generating a coding table for encoding the uplink communications, according to aspects described herein.

[0047] In one aspect, the processor 212 may correspond to one or more of the processors described with respect to the UE of Figure 8. Similarly, the memory 216 may correspond to the memory described with respect to the UE of Figure 8.

[0048] Referring to FIG. 3, one example of an implementation of a base station 102 (e.g., a base station 102 and / or gNB 180 as described above) may include various components, some of which have already been described above, including components such as one or more processors 312 and memories 316 and transceivers 302 communicating via one or more buses 344, which may operate in conjunction with a modem 340 and a configuration component 342 for configuring the device to encode uplink communications, according to aspects described herein.

[0049] The transceiver 302, receiver 306, transmitter 308, one or more processors 312, memory 316, application 375, bus 344, RF front end 388, LNA 390, switch 392, filter 396, PA 398, and one or more antennas 365 may be the same as or similar to corresponding components of the UE 104, as described above, but may be configured or otherwise programmed for base station operation as opposed to UE operation.

[0050] In one aspect, the processor 312 may correspond to one or more of the processors described with respect to the base station of Figure 8. Similarly, the memory 316 may correspond to the memory described with respect to the base station of Figure 8.

[0051] 4 shows an example of an RM coding table 400 configured in LTE and 5G NR. In one example, an (11,32) code may be used to encode an 11-bit payload into 32 coded bits, and rate matching may be used to shorten / lengthen the 32 bits to any length. However, this RM code may have some issues at high coding rates; that is, for some combinations of payload size K and rate matching length N, where K≦N, the code may not be decoded correctly even at very high signal-to-noise (SNR) ratios. In 5G NR, the UE encodes the UCI code block {c k}of

[0052]

number

[0053] where K is the payload size and M i,k} is a submatrix given in exemplary RM coding table 400. After encoding, the UE can rate-match the code to a desired code length N. As explained above and further described herein, K and N may be indicated by the base station when scheduling resources for transmitting UCI. If N≦32, for example, the UE may select the first N elements from the 32 coded bits, which may correspond to using the first N rows from RM coding table 400 to encode the UCI. If N>32, for example, the UE may cyclically extend the code to length N.

[0054] However, the RM coding table 400 has some identical columns (or column vectors) for some selected submatrices. For example, for K=11 and N=16, the 16 rows of the first column 402 and the first 16 rows of the last column 404 have the same values, which may prevent a receiving device from correctly distinguishing between the first and last information bits when an 11×16 submatrix (or K=11 for substantially all N=1 to 16) is used to encode UCI. Similarly, for example, the sixth column 408 has 10 zeros, which may imply that the sixth bit cannot be correctly decoded for 6≦K≦10 and K≦N≦10. Other problematic (K, N) pairs based on the RM coding table 400 may include (4,4), (5,5), (6,6), (6,7), (6,8), (6,9), (6,10), (7,7), (7,8), (7,9), (7,10), (8,8), (8,9), (8,10), (9,9), (9,10), (10,10), (11,11), (11,12), (11,13), (11,14), (11,15), and (11,16). In one example, in LTE, the base station may not schedule the problematic (K, N) pair on an uplink control channel (e.g., the Physical Uplink Control Channel (PUCCH)), which may be a problem only when UCI is transmitted on an uplink data channel (e.g., the Physical Uplink Shared Channel (PUSCH)). In one example, in 5G NR, the problem may arise for substantially all UCI transmissions.

[0055] 5 illustrates a flowchart of an example method 500 for encoding uplink communications based on determining whether a payload size and code length pair is desirable, according to aspects described herein. In one example, a UE can perform the functions described in method 500 using one or more of the components described in FIGS. 1 and 2.

[0056] In the method 500, at block 502, control information scheduling uplink communications indicating a payload size and a code length may be received from a base station. In one aspect, the communications component 242, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, etc., can receive from the base station the control information scheduling uplink communications indicating a payload size and a code length. For example, the control information may be received from the base station in a resource grant from the base station and may include downlink control information (DCI). In one example, the DCI may be received over a downlink control channel (e.g., a physical downlink control channel (PDCCH)) or a downlink data channel (e.g., a physical downlink shared channel (PDSCH)), etc. For example, the control information may relate to or specify time and / or frequency resources over which the UE 104 will transmit UCI or other uplink communications. For example, the time and / or frequency resources may include a portion of frequency, such as one or more subcarriers over a portion of time, such as one or more symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols, single-carrier frequency division multiplexing (SC-FDM) symbols, etc.), which may include another resource unit defined in a wireless communication technology, such as one or more resource blocks (RBs) defined in 5G NR. Additionally, a resource grant or another signal from the base station may indicate a payload size and code length to use in encoding the uplink communication. In one example, the uplink communication may include UCI for transmission to the base station. Further, as described, the payload size and code length may be used to determine a submatrix of a coding table (e.g., RM coding table 400) to use to encode the uplink communication.

[0057] In the method 500, optionally at block 504, it may be determined whether a payload size and code length pair is undesirable for encoding. In one aspect, the encoding component 252, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, the communication component 242, etc., may determine whether a payload size and code length pair is undesirable for encoding. For example, the encoding component 252 may be configured with information that may indicate or enable the determination of a list of undesirable pairs of payload sizes and code lengths in the configured RM coding table 400 that are undesirable for encoding (e.g., based on the list of pairs described above and / or other pairs that somehow result in undesirable encoding). For example, the list may be stored in the memory 216 of the UE 104. In this regard, for example, a submatrix of the RM coding table 400 indicated by the number of columns K and the number of rows N from the undesirable pairs may be considered rank-deficient. These undesirable pairs may be avoided for purposes of encoding uplink communications. In one example, the base station 102 may have scheduling constraints to avoid scheduling UCI transmissions that result in undesired pairs. For example, for a given payload size K, the base station may avoid scheduling a code length N that results in one of the undesired pairs.

[0058] In method 500, if the pair is undesirable for encoding at block 504, an error case may be triggered at block 506. In one aspect, encoding component 252, in cooperation with, for example, processor 212, memory 216, transceiver 202, communication component 242, etc., can trigger an error case if the pair is undesirable for encoding. For example, this may be based on encoding component 252 determining that the payload size and code length pair is in a list of pairs that are undesirable for decoding. In triggering an error case in this regard, for example, encoding component 252 can avoid encoding uplink communications based on the undesirable pair to prevent decoding errors at the receiver (e.g., at base station 102), as described above.

[0059] In one example, upon triggering an error case at block 506, optionally at block 508, selecting a code for encoding the uplink communication may be refrained from. In an aspect, encoding component 252, in cooperation with, for example, processor 212, memory 216, transceiver 202, communication component 242, etc., may refrain from selecting a code for encoding the uplink communication. For example, encoding component 252 may avoid using (or not use) a code for encoding the uplink communication, or may refrain from encoding the uplink communication altogether.

[0060] Similarly, upon triggering an error case, for example, at block 506, optionally at block 510, an uplink communication may be refrained from being transmitted on the scheduled resources. In an aspect, the communications component 242, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, etc., may refrain from transmitting an uplink communication on the scheduled resources. In this example, the base station 102 may still schedule UCI for transmission using the undesirable pair, but the UE 104 may not transmit UCI if an undesirable (K,N) pair results (thus, for example, the base station 102 does not attempt to decode a communication encoded using the undesirable (K,N) pair).

[0061] In one example, this may apply to both UCI on a PUSCH and UCI on a PUCCH. However, in this example, for UCI on a PUSCH, if the PUSCH includes an uplink shared channel (UL-SCH) (e.g., uplink data), the UE 104 may drop the UCI and transmit the PUSCH. Thus, for example, upon triggering an error case in block 506, even though UCI may not be transmitted, optionally in block 512, uplink data channel communications may still be transmitted on scheduled resources. In one aspect, the communications component 242, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, etc., may transmit uplink data channel communications on scheduled resources (e.g., without transmitting uplink communications corresponding to UCI).

[0062] In method 500, if it is determined at block 504 that no pairs are undesirable for encoding, then uplink communications may optionally be encoded at block 514 based on payload size and code length. In one aspect, encoding component 252, in cooperation with, for example, processor 212, memory 216, transceiver 202, communication component 242, etc., can encode uplink communications based on payload size and code length. As described, for example, encoding component 252 can encode uplink communications based on RM coding table 400 and / or according to the equations described above using columns of payload size K and 32 rows, and then rate-match the encoding by selecting N number of rows (where N<32 (or cyclically extending if N>32)).

[0063] The method 500 may optionally transmit the coded uplink communication at block 516. In one aspect, the coding component 252, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, the communication component 242, etc., may transmit the coded uplink communication on scheduled resources. This may include transmitting the coded uplink communication on time and / or frequency resources scheduled by the base station 102, such as on one or more RBs, as described.

[0064] 6 illustrates a flowchart of an example method 600 for encoding uplink communications based on determining a coding table to use, according to aspects described herein. In one example, a UE may perform the functions described in method 600 using one or more of the components described in FIGS. 1 and 2.

[0065] In method 600, at block 602, a configuration may be received from a base station indicating whether to use a modified coding table or process to encode uplink communications. In one aspect, communication component 242, in cooperation with, for example, processor 212, memory 216, transceiver 202, etc., can receive from the base station the configuration indicating whether to use a modified coding table or process to encode uplink communications. In one example, UE 104 may store (e.g., in memory 216) RM coding table 400 and a modified RM coding table having different values ​​for at least some of the columns that result in undesirable pairs. For example, in the modified (e.g., new) table, at least one of the first, fifth, sixth, or eleventh columns may be modified with a different binary sequence that avoids long strings of zeros or ones at the beginning of the column, as shown at 402, 404, 406, 408 of RM coding table 400 of FIG. 4 .

[0066] In one example, the configuration may indicate a coding table to be used or may be an indication to use one of multiple stored coding tables (e.g., an indicator of whether to use a modified coding table, where not using a modified coding table may implicitly indicate using the original, unmodified coding table, which may be RM coding table 400). For example, the configuration may include radio resource control (RRC) signaling (e.g., from base station 102 to UE 104) to indicate to UE 104 whether a new or old RM coding table should be used to encode the UCI transmission.

[0067] In another example, the configuration may indicate whether to modify a stored coding table to generate a modified coding table. For example, the configuration may indicate whether to permute rows of the coding table or rows of a submatrix generated from the coding table to avoid long strings of 0s or 1s. In one example, the configuration may indicate whether to permute rows of the RM coding table 400. In this example, the configuration may include RRC signaling to cause the base station 102 to indicate to the UE 104 to permute rows of the coding table, and / or one or more parameters for permute rows (e.g., one or more indices indicating which rows to permute), etc. In another example, the configuration may indicate whether to apply an interleaving function to the coded bit string after RM encoding and before rate matching when encoding the bitstream. For example, the interleaving function may perform the permute of coding table rows as described above, but after the initial encoding process using an unmodified coding table (e.g., RM coding table 400). In this example, the configuration may include RRC signaling to cause the base station 102 to indicate to the UE 104 that an interleaving function (e.g., between RM coding and rate matching) is to be used to implement modified coding of uplink communications, and / or one or more parameters for using that function, etc.

[0068] In method 600, at block 604, control information scheduling uplink communications or indicating a payload size and code length may be received from a base station. In one aspect, communication component 242, in cooperation with, for example, processor 212, memory 216, transceiver 202, etc., can receive control information scheduling uplink communications or indicating a payload size and code length from a base station. For example, the control information may be received from the base station in a resource grant from the base station and may include DCI received on a downlink control channel (e.g., PDCCH) or a downlink data channel (e.g., PDSCH), etc. Additionally, the resource grant or another signal from the base station can indicate a payload size and code length to use in encoding the uplink communications. In one example, the uplink communications may include UCI to transmit to the base station. Furthermore, as described, the payload size and code length may be used to determine a submatrix of a coding table (e.g., RM coding table 400 or a modified coding table) to use to encode the uplink communications.

[0069] The method 600 may optionally determine, at block 606, whether the configuration indicates using a modified coding table or process. In one aspect, the encoding component 252, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, the communication component 242, etc., may determine whether the configuration indicates using a modified coding table or process. For example, the encoding component 252 may determine this based on received RRC signaling from a base station indicating whether to use a modified coding table or process (e.g., whether to perform one or more intermediate steps during encoding) (e.g., as a stored modified coding table from the memory 216 or as a generated modified coding table).

[0070] In method 600, in one example illustrating using a configuration-modified coding table at block 606, the modified coding table may optionally be obtained at block 608. In one aspect, coding table determination component 254 may obtain the modified coding table in cooperation with, for example, processor 212, memory 216, transceiver 202, communication component 242, etc. As described, the modified coding table may differ from the stored unmodified coding table (e.g., RM coding table 400) by having different values ​​in at least some of the rows to prevent long strings of 0s and 1s that may cause the decoding problems described above. In this regard, the modified coding table may enable full-rank coding to be achieved.

[0071] In one example, upon obtaining the modified coding table at block 608, the modified coding table may optionally be obtained from a memory at block 610. In one aspect, the coding table determination component 254 may, for example, cooperate with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc. to obtain the modified coding table from a memory (e.g., the memory 216). In this regard, for example, the UE 104 may be configured with the modified coding table in the memory 216 (and, for example, an unmodified coding table, such as the RM coding table 400) based on a wireless communication technology standard such as 5G NR. In another example, the UE 104 may receive the modified coding table, or one or more parameters or other information for generating the modified coding table, in configuration from the base station 102.

[0072] In one example, upon obtaining the modified coding table at block 608, the modified coding table may optionally be generated at block 612. In one aspect, the coding table determination component 254 can generate the modified coding table, for example, in cooperation with the processor 212, the memory 216, the transceiver 202, the communication component 242, etc. For example, the coding table determination component 254 can generate the modified coding table based on an unmodified coding table (e.g., the RM coding table 400, which may be stored in the memory 216) in a manner to avoid the use of some values ​​in encoding the uplink communication that may result in a failure to decode the uplink communication, as described. In one example, the coding table determination component 254 can permute rows of the unmodified coding table (e.g., the RM coding table 400) to generate the modified coding table to be used in performing the encoding of the uplink communication.

[0073] For example, if the first row of the coding table determination component 254 is between 1 and 11 and the second row is between 17 and 32, two rows of the RM coding table 400 (or its submatrix) can be swapped. This can at least make it possible to eliminate undesirable (K, N) pairs where K < N. For example, if the coding table determination component 254 swaps row 1 and row 17 in the RM coding table 400, if K < N, it can be easily checked that all submatrices obtained by taking the first N rows and K columns from the modified coding matrix are full rank (for example, rank K). This can imply that all (K, N) pairs where N > K can be decodable at high SNR. In one example, the coding table determination component 254 can similarly swap other single row pairs of the RM coding table 400 to eliminate undesirable (K, N) pairs where K < N, including, as an addition or alternative, row 1 and 18, 1 and 19, 1 and 20, 1 and 27, 1 and 28, 1 and 29, 1 and 30, 2 and 19, 2 and 28, 3 and 19, 3 and 20, 3 and 30, 5 and 19, 5 and 20, 5 and 28, 5 and 29, 6 and 17, 6 and 18, 6 and 19, 6 and 29, 6 and 30, 7 and 17, 7 and 20, 7 and 28, 7 and 29.

[0074] In another example, the coding table determination component 254 can swap two pairs of rows (e.g., change the order of a total of four rows) to eliminate undesirable (K, N) combinations (regardless of whether K < N). For example, if the coding table determination component 254 swaps rows (2, 6) and rows (19, 24) of the RM coding table 400, the resulting coding table can eliminate all undesirable (K, N) combinations. The order of (19, 24) does not have to be specific. For example, swapping rows 2 and 19 and rows 6 and 24, or swapping rows 2 and 24 and rows 6 and 19, can produce results similar to eliminating all undesirable (K, N) combinations of the RM coding table 400. In one example, the coding table determination component 254 can determine which rows to replace or swap based on an indication of row indices in the configuration from the base station 102. In one example, the coding table determination component 254 can similarly swap two pairs of rows of the RM coding table 400, including rows (2, 8) and (19, 23), (2, 8) and (19, 24), (2, 8) and (19, 27), (2, 8) and (19, 29), (2, 8) and (29, 31), (4, 6) and (25, 29), (4, 8) and (19, 23), (4, 8) and (19, 24), (4, 8) and (19, 29) to eliminate undesirable (K, N) in this regard.

[0075] In method 600, optionally at block 614, a submatrix of the modified coding table that is full rank may be generated. In one aspect, the encoding component 252, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, the communication component 242, etc., can generate a submatrix of the modified coding table that is full rank. For example, the encoding component 252 can select a submatrix from the modified coding table for encoding uplink communications, where the submatrix can be full rank based on properties of the modified coding table to avoid having the same coded values ​​for information bits, as described above. Furthermore, as described, the modified coding table can have modified values ​​for some rows and columns that differ from the values ​​in the unmodified coding table if the unmodified coding table is rank-deficient for some combinations of rows and columns (e.g., based on having long strings of 0s or 1s in a column that may result in decoding errors).

[0076] In method 600, at block 616, uplink communications may be encoded based on a modified coding table or a modified coding process based on a payload size and a code length. In one aspect, the encoding component 252, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, the communication component 242, etc., can encode uplink communications based on a modified coding table or a modified coding process based on a payload size and a code length. As described, for example, the encoding component 252 can encode uplink communications based on a modified coding table using payload size K columns and 32 rows, and then rate-match the encoding by selecting N number of rows (where N<32 (or cyclically extending if N>32)). In this regard, columns of the modified coding table used to encode uplink communications using the modified coding table can have different values ​​in corresponding rows to avoid decoding issues. Additionally, as described, the uplink communications being encoded may include UCI.

[0077] In another example, if the configuration indicates use of a modified coding process at block 606, and upon encoding the uplink communication based on the modified coding table or process at block 616, the encoded uplink communication may optionally be interleaved before rate matching at block 618. In one aspect, encoding component 252, in cooperation with, for example, processor 212, memory 216, transceiver 202, communication component 242, etc., may interleave the encoded communication before rate matching as part of the modified coding process or as a way of implementing a modification of the coding table after encoding. For example, as described, interleaving the encoded communication may provide effectively the same output as permuting row values ​​for columns of an unmodified coding table (e.g., to generate, in effect, a modified coding table, as described above) prior to performing rate matching. In this example, encoding component 252 may encode the uplink communication based on an unmodified coding table (e.g., RM coding table 400) using columns of payload size K and 32 rows. Encoding component 252 may then interleave the coded bits from the encoding.

[0078] For example, as described above, the encoding component 252 may swap two bits in the encoded bit string (e.g., swap the 1st bit and the 17th bit), which may provide the same result as permuting the 1st and 17th rows of the coding table before encoding, as described above. In another example, as described above, the encoding component 252 may swap two pairs of bits in the encoded bit string (e.g., swap the 2nd bit and the 19th bit, swap the 6th bit and the 24th bit, etc.), which may provide the same result as permuting the 2nd and 19th rows and permuting the 6th and 24th rows of the coding table before encoding, as described above. The encoding component 252 may then perform rate matching to select several bits of the encoding to represent information for each column, where some of the bits may be interleaved as described above. In one example, parameters for performing the interleaving (e.g., the index of the bit in the encoded bit string to be switched, etc.) may be configured in the configuration.

[0079] The method 600 may optionally transmit the coded uplink communication at block 620. In one aspect, the encoding component 252, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, the communication component 242, etc., may transmit the coded uplink communication, coded based on the modified coding table, on scheduled resources. This may include transmitting the coded uplink communication on time and / or frequency resources scheduled by the base station 102, such as on one or more RBs, as described.

[0080] In method 600, if the configuration does not indicate the use of a modified coding table or process at block 606, then optionally at block 622, the uplink communication may be encoded using an unmodified coding table based on the payload size and code length. In one aspect, encoding component 252, in cooperation with, for example, processor 212, memory 216, transceiver 202, communication component 242, etc., can encode the uplink communication using an unmodified coding table based on the payload size and code length. As described, for example, encoding component 252 can encode the uplink communication based on the unmodified coding table using columns of payload size K and 32 rows, and then rate-match the encoding by selecting N number of rows (where N<32 (or cyclically extending if N>32)). Additionally, optionally at block 620, the encoded uplink communication may be transmitted. In one aspect, the encoding component 252, in cooperation with, for example, the processor 212, the memory 216, the transceiver 202, the communication component 242, etc., can transmit, on the scheduled resources, an encoded uplink communication that is encoded based on the unchanged coding table.

[0081] 7 illustrates a flowchart of an example method 700 for configuring user equipment to encode uplink communications based on a coding table according to aspects described herein. In one example, a base station can perform the functions described in method 700 using one or more of the components described in FIGS. 1 and 3.

[0082] In the method 700, at block 702, a configuration may be transmitted to a UE indicating whether to use a modified coding table or process to encode uplink communications. In one aspect, the configuration component 342, in cooperation with, for example, the processor 312, the memory 316, the transceiver 302, etc., can transmit a configuration to a UE (e.g., the UE 104) indicating whether to use a modified coding table or process to encode uplink communications. In one example, as described, the UE 104 can store (e.g., in the memory 216) the RM coding table 400 and a modified RM coding table having different values ​​for at least some of the columns that result in undesirable pairs. For example, in the modified (e.g., new) table, at least one of the first, fifth, sixth, or eleventh columns may be modified with a different binary sequence that avoids long strings of zeros and ones at the beginning of the column, as shown at 402, 404, 406, 408.

[0083] In one example, the configuration may indicate a coding table to be used or may be an indication to use one of multiple stored coding tables (e.g., an indicator of whether to use a modified coding table, where not using a modified coding table may implicitly indicate using the original, unmodified coding table, which may be RM coding table 400). For example, the configuration may include new radio resource control (RRC) signaling (e.g., from base station 102 to UE 104) to indicate to UE 104 whether a new or old RM coding table should be used to encode the UCI transmission.

[0084] In another example, the configuration may indicate whether to modify a stored coding table to generate a modified coding table. For example, the configuration may indicate whether to permute rows of the coding table or rows of a submatrix generated from the coding table to avoid long strings of 0s or 1s. In one example, the configuration may indicate whether to permute one or more rows of the RM coding table 400 (e.g., to avoid long strings of 0s or 1s in at least columns 1, 5, 6, or 11). In this example, the configuration may include RRC signaling to cause the base station 102 to indicate to the UE 104 to permute rows of an unchanged coding table to generate a modified coding table, and / or one or more parameters to use for the permute (e.g., which rows to permute). In another example, the configuration may indicate whether to interleave values ​​of the RM coding (before rate matching) to perform the permute. In this example, the configuration may include RRC signaling to cause the base station 102 to indicate to the UE 104 that an interleaving function is to be used (e.g., between RM coding and rate matching), and / or one or more parameters for using that function (e.g., which bits to interleave), etc.

[0085] In the method 700, at block 704, control information scheduling uplink communications or indicating a payload size and code length may be transmitted to a UE. In one aspect, the component 342, in cooperation with, for example, the processor 312, the memory 316, the transceiver 302, etc., can transmit the control information scheduling uplink communications or indicating a payload size and code length to a UE (e.g., the UE 104). For example, the control information may be transmitted to the UE in a resource grant from a base station and may include DCI received on a downlink control channel (e.g., a PDCCH) or a downlink data channel (e.g., a PDSCH), etc. Additionally, the resource grant or another signal from the base station may indicate a payload size and code length to use in encoding the uplink communications. In one example, the uplink communications may include UCI to transmit to the base station. Furthermore, as described, the payload size and code length may be used to determine a submatrix of a coding table (e.g., the RM coding table 400 or a modified coding table) to use to encode the uplink communications.

[0086] In the method 700, optionally at block 706, an encoded uplink communication may be received from the UE on the resources indicated in the control information. In one aspect, the configuration component 342, in cooperation with, for example, the processor 312, the memory 316, the transceiver 302, etc., may receive the encoded uplink communication from the UE on the resources indicated in the control information. For example, the configuration component 342 may decode the uplink communication and process the communication from the UE (e.g., to obtain control information from the UE 104), which may be based on determining a coding table to be used by the UE 104 in encoding the uplink communication (e.g., whether the RM coding table 400 is used, whether a permuted matrix permuted from the RM coding table 400 is used, whether interleaving is performed, etc.). In this regard, the configuration component 342 may similarly determine configured or stored coding table-based parameters to indicate to the UE 104 to modify the RM coding table 400 for at least some (K, N) pairs.

[0087] FIG. 8 is a block diagram of a MIMO communication system 800 including a base station 102 and a UE 104. The MIMO communication system 800 may represent an aspect of the wireless communication access network 100 described with reference to FIG. 1. The base station 102 may be an example of an aspect of the base station 102 described with reference to FIG. 1. The base station 102 may be equipped with antennas 834 and 835, and the UE 104 may be equipped with antennas 852 and 853. In the MIMO communication system 800, the base station 102 may be capable of sending data simultaneously over multiple communication links. Each communication link may be referred to as a “layer,” and the “rank” of a communication link may indicate the number of layers used for communication. For example, in a 2×2 MIMO communication system in which the base station 102 transmits two “layers,” the rank of the communication link between the base station 102 and the UE 104 is 2.

[0088] At the base station 102, a transmit (Tx) processor 820 may receive data from a data source. The transmit processor 820 may process the data. The transmit processor 820 may also generate control symbols or reference symbols. The transmit MIMO processor 830 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to transmit modulators / demodulators 832 and 833. Each modulator / demodulator 832-833 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 832-833 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a DL signal. In one example, the DL signals from the modulators / demodulators 832 and 833 may be transmitted via antennas 834 and 835, respectively.

[0089] UE 104 may be an example of the aspect of UE 104 described with reference to FIGS. 1-2. In UE 104, UE antennas 852 and 853 may receive DL signals from base station 102 and may provide received signals to modulators / demodulators 854 and 855, respectively. Each modulator / demodulator 854-855 may condition (e.g., filter, amplify, downconvert, and digitize) its respective received signal to obtain input samples. Each modulator / demodulator 854-855 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 856 may obtain the received symbols from modulators / demodulators 854 and 855, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. The receive (Rx) processor 858 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data output, and provide decoded control information to a processor 880 or a memory 882.

[0090] The processor 880 may execute stored instructions, in some cases, to instantiate the communications component 242 (see, eg, FIGS. 1 and 2).

[0091] On the uplink (UL), at the UE 104, a transmit processor 864 may receive and process data from a data source. The transmit processor 864 may also generate reference symbols for a reference signal. The symbols from the transmit processor 864 may be precoded by a transmit MIMO processor 866 if applicable, further processed by modulators / demodulators 854 and 855 (e.g., for SC-FDMA, etc.), and transmitted to the base station 102 in accordance with communication parameters received from the base station 102. At the base station 102, UL signals from the UE 104 may be received by antennas 834 and 835, processed by modulators / demodulators 832 and 833, detected by a MIMO detector 836 if applicable, and further processed by a receive processor 838. The receive processor 838 may provide decoded data to a data output and to a processor 840 or a memory 842.

[0092] Processor 840 may execute stored instructions, in some cases, to instantiate components 342 (see, eg, FIGS. 1 and 3).

[0093] The components of the UE 104 may be implemented, individually or collectively, using one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each of the mentioned modules may be a means for performing one or more functions related to the operation of the MIMO communications system 800. Similarly, the components of the base station 102 may be implemented, individually or collectively, using one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Each of the mentioned components may be a means for performing one or more functions related to the operation of the MIMO communications system 800.

[0094] The following aspects are exemplary only, and the aspects may be combined without limitation with aspects of other embodiments or teachings described herein.

[0095] Aspect 1 is a method for wireless communication including receiving, from a base station, control information scheduling uplink communication, the control information indicating a payload size and a code length for encoding the uplink communication based on a code; determining whether a pair of payload size and code length is in a list of undesirable pairs for performing the encoding; and determining an error case if the pair is determined to be in the list of undesirable pairs.

[0096] In example 2, the method of example 1 includes wherein the uplink communication is UCI and the scheduled resource corresponds to an uplink control channel.

[0097] In aspect 3, the method of either aspect 1 or 2 includes refraining from selecting a pair for encoding uplink communications if the pair is determined to be in a list of undesirable pairs.

[0098] In aspect 4, the method of any of aspects 1 to 3 includes refraining from transmitting uplink communications on the scheduled resources if the pair is determined to be in the list of undesirable pairs.

[0099] In aspect 5, the method of aspect 4 includes: the uplink communication is UCI; the scheduled resource corresponds to an uplink data channel; and the method further comprises transmitting the uplink data channel communication on the uplink data channel.

[0100] Aspect 6 is a method for wireless communication including receiving, from a base station, a configuration indicating whether to use a modified coding table for encoding uplink communications; receiving, from the base station, control information scheduling the uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications; if the configuration indicates using the modified coding table, encoding the uplink communications using the modified coding table based on the payload size and code length; and if the configuration indicates using the unmodified coding table, encoding the uplink communications using the unmodified coding table based on the payload size and code length.

[0101] In aspect 7, the method of aspect 6 includes that the step of encoding the uplink communication using the modified coding table includes the steps of generating a submatrix of a first number of columns and a second number of rows from the modified coding table, the submatrix being full rank, the first number of columns corresponding to a payload size, and the second number of rows corresponding to a code length; and encoding the uplink communication based on the submatrix.

[0102] In an embodiment 8, the method of any of embodiments 6 or 7 includes that at least one submatrix of the first number of columns and the second number of rows from the unchanged coding table is rank-deficient.

[0103] In an aspect 9, the method of any of aspects 6 to 8 includes, if the configuration indicates using the modified coding table, obtaining the modified coding table from the memory.

[0104] In aspect 10, the method of any of aspects 6 to 9 includes the modified coding table including at least one column related to payload size that has the same value for all code lengths as the at least one column related to payload size in the unmodified coding table.

[0105] In example 11, the method of example 10 includes the modified coding table including at least one second column related to a second payload size having a different value for at least one of the code lengths as the at least one second column related to the second payload size in the unmodified coding table.

[0106] In example 12, the method of any of examples 6 to 11 includes: encoding the uplink communication using the modified coding table includes permuting rows of the unmodified coding table to generate the modified coding table.

[0107] In example 13, the method of example 12 includes: the configuration indicates one or more parameters for replacing rows of the unmodified coding table to generate the modified coding table; and the replacing rows of the unmodified coding table to generate the modified coding table is based at least in part on the one or more parameters.

[0108] Aspect 14 is a method for wireless communication including receiving, from a base station, a configuration indicating whether to use a modified coding process to encode uplink communications; receiving, from the base station, control information scheduling the uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications; encoding the uplink communications using an unmodified coding table based on the payload size and the code length to generate an encoded bit string; and if the configuration indicates using the modified coding process, interleaving one or more bits of the encoded bit string.

[0109] In aspect 15, the method of aspect 14 includes the configuration indicating one or more bits to interleave.

[0110] In aspect 16, the method of either aspect 14 or 15 includes performing rate matching on the coded bit string once interleaved to generate a rate-matched bit string as a coded uplink communication for transmission.

[0111] Aspect 17 is a method for wireless communication including: transmitting, to a UE, a configuration indicating whether to use a modified coding table for encoding uplink communications; and transmitting, to the UE, control information scheduling the uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications.

[0112] In example 18, the method of example 17 includes that the configuration includes one or more parameters for substituting rows of the unchanged coding table to generate the modified coding table.

[0113] Aspect 19 is a method for wireless communication including receiving, from a base station, control information scheduling uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications based on a code; and triggering an error case if the payload size and code length pair is deemed undesirable for performing the encoding.

[0114] In aspect 20, the method of aspect 19 includes wherein the uplink communication includes UCI and the schedule corresponds to an uplink control channel.

[0115] In aspect 21, the method of any of aspects 19 or 20 includes that the step of triggering an error case includes a step of refraining from selecting a pair for encoding uplink communications if it is determined that the pair is undesirable for performing encoding.

[0116] In aspect 22, the method of any of aspects 19 to 21 includes, wherein the step of triggering an error case includes a step of refraining from transmitting uplink communications on the scheduled resources if it is determined that the pair is undesirable for performing encoding.

[0117] In aspect 23, the method of aspect 22 includes: the uplink communication includes UCI; the scheduled resource corresponds to an uplink data channel; and the method includes transmitting an uplink data channel communication on the uplink data channel.

[0118] In aspect 24, the method of any of aspects 19 to 23 includes that the step of triggering an error case is based at least in part on detecting a pair in a list of undesirable pairs configured for performing the encoding.

[0119] In example 25, the method of example 24 includes the undesirable pairs in the list corresponding to code configurations that include identical column vectors in the coding table.

[0120] In example 26, the method of any of examples 24 or 25 includes, wherein the list of undesirable pairs includes the following pairs of undesirable payload size and undesirable code length values: (4,4), (5,5), (6,6), (6,7), (6,8), (6,9), (6,10), (7,7), (7,8), (7,9), (7,10), (8,8), (8,9), (8,10), (9,9), (9,10), (10,10), (11,11), (11,12), (11,13), (11,14), (11,15), (11,16).

[0121] In aspect 27, the method of any of aspects 19 to 26 includes receiving a configured table of payload sizes and code lengths, where the payload size and code length pairs are indicated in the configured table.

[0122] Aspect 28 is a method for wireless communication including receiving, from a base station, a configuration indicating whether to use a modified coding table for encoding uplink communications; receiving, from the base station, control information scheduling the uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications; if the configuration indicates using the modified coding table, encoding the uplink communications based on the modified coding table based on the payload size and the code length; if the configuration indicates using the unmodified coding table, encoding the uplink communications using the unmodified coding table based on the payload size and the code length; and transmitting the encoded uplink communications.

[0123] In aspect 29, the method of aspect 28 includes that the step of encoding the uplink communication based on the modified coding table includes the steps of generating a submatrix of a first number of columns and a second number of rows from the modified coding table, the submatrix being full rank, the first number of columns corresponding to a payload size, and the second number of rows corresponding to a code length; and encoding the uplink communication based on the submatrix.

[0124] In embodiment 30, the method of any of embodiments 28 or 29 includes that at least one submatrix of the first number of columns and the second number of rows from the unchanged coding table is rank-deficient.

[0125] In aspect 31, the method of any of aspects 28 to 30 includes, if the configuration indicates using the modified coding table, obtaining the modified coding table from the memory.

[0126] In aspect 32, the method of any of aspects 28 to 31 includes the modified coding table including at least one column related to payload size that has the same value for all code lengths as the at least one column related to payload size in the unmodified coding table.

[0127] In aspect 33, the method of aspect 32 includes the modified coding table including at least one second column related to a second payload size having a different value for at least one of the code lengths as the at least one second column related to the second payload size in the unmodified coding table.

[0128] In aspect 34, the method of any of aspects 28 to 33 includes that encoding the uplink communication based on the modified coding table includes permuting rows of the unmodified coding table to generate the modified coding table.

[0129] In aspect 35, the method of aspect 34 includes: the configuration indicates one or more parameters for replacing rows of the unmodified coding table to generate the modified coding table; and the replacing rows of the unmodified coding table to generate the modified coding table is based at least in part on the one or more parameters.

[0130] In aspect 36, the method of any of aspects 28 to 35 includes that encoding the uplink communication based on the modified coding table includes encoding the uplink communication using an unmodified coding table based on a payload size and a code length to generate an encoded bit string, and interleaving one or more bits of the encoded bit string.

[0131] In aspect 37, the method of aspect 36 includes the configuration indicating one or more bits to interleave.

[0132] In aspect 38, the method of either aspect 36 or 37 includes performing rate matching on the coded bit string once interleaved to generate a rate-matched bit string as a coded uplink communication for transmission.

[0133]

[0023] Aspect 39 is an apparatus for wireless communication including a transceiver, a memory configured to store instructions, and one or more processors communicatively coupled to the memory and the transceiver, wherein the one or more processors are configured to perform one or more of the methods of any of aspects 1 to 38.

[0134]

[0039] Aspect 40 is an apparatus for wireless communication, including means for performing one or more of the methods of any of aspects 1-38.

[0135] Aspect 41 is a computer-readable medium including code executable by one or more processors for wireless communication, the code including code for performing one or more of the methods of any of aspects 1 to 38.

[0136] The above detailed description set forth above with reference to the accompanying drawings describes examples and does not represent the only examples that may be implemented or fall within the scope of the claims. The term "example," as used herein, means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0137] Information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer-executable code or instructions stored on a computer-readable medium, or any combination thereof.

[0138] The various example blocks and components described in connection with the disclosure herein may be implemented or performed using specially programmed devices such as, but not limited to, processors, digital signal processors (DSPs), ASICs, field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A specially programmed processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0139] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a non-transitory computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope and spirit of this disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a specially programmed processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations. Furthermore, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless otherwise specified or clear from the context, for example, a phrase "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, for example, the phrase "X employs A or B" is satisfied by any of the following examples: X employs A, X employs B, or X employs both A and B. Also, as used herein, including in the claims, "or" used in a list of items ending with "at least one of" indicates a disjunctive list, such as, for example, the list "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0140] Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0141] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications of the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Furthermore, although elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. In addition, all or a portion of any aspect and / or embodiment may be utilized with all or a portion of any other aspect and / or embodiment, unless otherwise stated. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0142] 102 Base station 104UE 180 gNB 202 Transceiver 212 processors 216 memory 240 modem 242 Communication Components 244 Bus 252 Coding Components 254 Coding Table Determination Components 302 Transceiver 312 processors 316 memory 340 modem 342 Components 344 Bus 400 RM coding table 402 First Column 404 Last Column 408 Column 6 500 ways 600 ways 700 methods

Claims

1. 1. An apparatus for wireless communication, comprising: means for receiving, from a base station, control information scheduling uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications based on a code; means for triggering an error case if the payload size and code length pair is deemed to be an undesirable pair for performing the encoding; and Equipped with the undesirable pairs correspond to code configurations in a coding table that result in decoding errors due to inability to distinguish information bits; Triggering the error case includes refraining from transmitting the uplink communication on scheduled resources. Device.

2. 10. The apparatus of claim 1, wherein the uplink communication includes uplink control information (UCI), and the schedule corresponds to an uplink control channel.

3. 10. The apparatus of claim 1, wherein the uplink communication includes uplink control information (UCI), the scheduled resources correspond to an uplink data channel, and further comprising: means for transmitting an uplink data channel communication on the uplink data channel.

4. The apparatus of claim 1 , further comprising: means for triggering the error case based at least in part on detecting the pair in a list of undesirable pairs configured to perform the encoding.

5. The undesirable pairs in the list correspond to code configurations in a coding table that include identical column vectors, or 5. The apparatus of claim 4, wherein the list of undesirable pairs includes the following pairs of undesirable payload size and undesirable code length values: (4,4), (5,5), (6,6), (6,7), (6,8), (6,9), (6,10), (7,7), (7,8), (7,9), (7,10), (8,8), (8,9), (8,10), (9,9), (9,10), (10,10), (11,11), (11,12), (11,13), (11,14), (11,15), and (11,16).

6. The apparatus of claim 1 , further comprising: means for receiving a configured table of payload sizes and code lengths, wherein the pairs of the payload sizes and the code lengths are indicated in the configured table.

7. 1. A method performed by an apparatus for wireless communication, comprising: receiving, from a base station, control information scheduling uplink communications, the control information indicating a payload size and a code length for encoding the uplink communications based on a code; triggering an error case if the payload size and code length pair is deemed to be an undesirable pair for performing the encoding; Equipped with the undesirable pairs correspond to code configurations in a coding table that result in decoding errors due to inability to distinguish information bits; Triggering the error case includes refraining from transmitting the uplink communication on scheduled resources. method.

8. The method of claim 7, wherein the uplink communication includes uplink control information (UCI) and the schedule corresponds to an uplink control channel.

9. The method of claim 8, wherein the uplink communication includes uplink control information (UCI), and the scheduled resources correspond to an uplink data channel; The method of claim 7 , further comprising transmitting an uplink data channel communication on the uplink data channel.

10. The method of claim 7, further comprising a step of triggering the error case based at least in part on detecting the pair in a list of undesirable pairs configured to perform the encoding.

11. The undesirable pairs in the list correspond to code configurations in a coding table that include identical column vectors, or 11. The method of claim 10, wherein the list of undesirable pairs includes the following pairs of undesirable payload size and undesirable code length values: (4,4), (5,5), (6,6), (6,7), (6,8), (6,9), (6,10), (7,7), (7,8), (7,9), (7,10), (8,8), (8,9), (8,10), (9,9), (9,10), (10,10), (11,11), (11,12), (11,13), (11,14), (11,15), and (11,16).

12. The method according to claim 1, further comprising the step of receiving a configured table of payload sizes and code lengths; The method of claim 7 , wherein the pair of the payload size and the code length is indicated in the configured table.

13. A computer program comprising instructions for carrying out the method of any one of claims 7 to 12 when executed by a processor of a device.

Images