Patent Description:
Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. 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, and orthogonal frequency-division multiple access (OFDMA) systems, (e.g., a Long Term Evolution (LTE) system, as described in 3GPP TS <NUM> V. <NUM>, or a New Radio (NR) system). A wireless multiple-access communication system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, otherwise known as user equipment (UE) implementing error correction as for example describe din <CIT>. Thereby, channel coding as for example described in 3GPP TS <NUM> V. <NUM> may be employed.

In some wireless communication systems, base stations and UEs may communicate using one or more enhanced component carriers (eCCs). An eCC may be provided in a contention-based radio frequency spectrum band or a contention-free radio frequency spectrum band. A contention-based radio frequency spectrum band is a radio frequency spectrum band for which transmitting devices may contend for access (e.g., a radio frequency spectrum band that is available for unlicensed use, such as Wi-Fi use, or a radio frequency spectrum band that is available for use by multiple operators in an equally shared or prioritized manner). A contention-free radio frequency spectrum band is a radio frequency spectrum band for which transmitting devices may not contend for access because the radio frequency spectrum band is licensed to particular users for particular uses (e.g., a licensed radio frequency spectrum band usable for Long-Term Evolution (LTE) or LTE-Advanced (LTE-A) communications). Because eCCs, LTE/LTE-A component carriers (CCs), and Wi-Fi CCs may share the same radio frequency spectrum band, LTE/LTE-A or Wi-Fi transmission techniques (e.g., encoding techniques) may in some cases be leveraged for eCC transmissions. In other cases, new or different transmission techniques may be better suited for eCC transmissions.

eCCs are being designed for higher data rate transmissions than LTE/LTE-A CCs. LTE/LTE-A transmissions may be encoded using turbo code (TC) encoding. TC encoding is useful in that it supports hybrid automatic repeat request (HARQ) processes, puncturing, and rate matching. TC encoding can be used for eCC transmissions, but tends to increase decoding complexity (e.g., compared to certain other types of encoding, such as LDPCC encoding). The complexity of TC decoding may be further increased under high data rate conditions, as may be used for eCC transmissions. For example, the number of TC decoders deployed in a receiver may need to be increased, to provide satisfactory decoding throughput under high data rate conditions, when using TC encoding for high data rate eCC transmissions. In contrast to LTE/LTE-A transmissions, Wi-Fi transmissions may be encoded using LDPCC encoding. LDPCC encoding may be used for eCC transmissions, and may reduce decoding complexity by an order of magnitude in comparison to TC encoding. When TC encoding is used, a CRC is appended to each codeword for decoding error protection. When LDPCC encoding is used, a CRC is normally not needed, as the code structure provides parity checks for decoding error detection. However, when a LDPCC codeword is short, the parity check provided by the code structure is not reliable enough and there may be residual false alarm events. On the other hand, appending a CRC to a codeword increases data transmission overhead, and the relative increase in overhead can be high if a CRC is appended to a codeword having a payload with a small number of bits. The present disclosure describes a unified code block segmentation that provides a CRC for LDPCC codewords. The CRC for LDPCC codewords may be generated at a code block level, similar to how a CRC is generated for a TC code block. The CRC may correspond to multiple LDPCC codewords.

The invention is defined by the claims, where a method for wireless communication is defined in claim <NUM>, a device for wireless communication is defined in claim <NUM> and a computer-readable medium is defined in claim <NUM>.

In some embodiments of a method as specified in claim <NUM>, each code block associated with the first payload has a code block length that is an integer multiple of an equal codeword length associated with each codeword corresponding to the code block. In some examples, the method may include selecting a code block length of each code block of at least the first payload based on a length of a TC code block, or a LTE/LTE-A code block, used to segment at least the second payload. In some examples, the method may include selecting a length of a TC code block used to segment at least the second payload based at least in part on a length of each code block used to segment at least the first payload.

In some embodiments of a device as specified in claim <NUM>, the device may include means for selecting the encoding type for a payload based at least in part on a characteristic of the payload. In some embodiments, the characteristic may include at least a payload size. In some embodiments, the device may include means for transmitting, for at least one of the payloads, at least one of: an indication of the payload size, or an indication of the transmission data rate, or an indication of the transmission resource size, or an indication of the selected encoding type. In some embodiments, the device may include means for receiving one of an ACK or a NAK for each code block. In some embodiments, the device may include means for receiving a NAK of a code block associated with the first payload, and means for retransmitting a plurality of LDPCC codewords associated with the code block and a CRC associated with the code block. In some embodiments, each codeword associated with a code block of the first payload may have an equal codeword length. In some embodiments, the device may include means for selecting a code block length of each code block associated with at least the first payload to be an integer multiple of the equal codeword length. In some embodiments, the device may include means for combining filler bits with the first payload to maintain the selected code block length. In some embodiments, each code block associated with the first payload may have a code block length that is an integer multiple of an equal codeword length associated with each codeword corresponding to the code block. In some embodiments, the device may include means for selecting a code block length of each code block of at least the first payload based at least in part on a length of a TC code block, or a LTE/LTE-A code block, used to segment at least the second payload. In some embodiments, the device may include means for selecting a length of a TC code block used to segment at least the second payload based at least in part on a length of each code block used to segment at least the first payload.

In some embodiments of a computer-readable medium as specified in claim <NUM>, the code may be executable by the processor to select the encoding type for a payload based at least in part on a characteristic of the payload. In some examples, the code may be executable by the processor to receive one of an ACK or a NAK for each code block.

The foregoing has outlined rather broadly the features and technical advantages of embodiments according to the disclosure in order that the detailed description that follows may be better understood. The conception and specific embodiments disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure.

Further, various components of the same may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components.

Some wireless communication systems (e.g., a Long Term Evolution (LTE) system, or a New Radio (NR) system (<NUM>)) may use eCCs to improve throughput, latency, or reliability of wireless communications. An eCC may be characterized by a short symbol duration, wide tone spacing, short subframe duration, operation in a contention-based radio frequency spectrum band (or in a contention-free radio frequency spectrum band), or wide bandwidth. An eCC may have a relatively wide bandwidth (e.g. <NUM> or <NUM>) as compared to a non-eCC (e.g., an LTE/LTE-A component carrier (CC), Licensed Assisted Access (LAA) CC, or Stand Alone CC in a contention-based radio frequency spectrum band), which may have a relatively smaller bandwidth (e.g. <NUM>). An eCC may include one or more channels (e.g., segments of bandwidth, such as four <NUM> segments of bandwidth).

The present disclosure describes a unified code block segmentation in which a CRC is provided for LDPCC codewords. In some examples, the techniques may be used to encode eCC payloads.

<FIG> shows an example of a wireless communication system <NUM>, in accordance with various aspects of the present disclosure. The wireless communication system <NUM> may include base stations <NUM>, UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a LTE (or LTE-Advanced) network, or a New Radio (NR) network. In some cases, wireless communications system <NUM> may support enhanced broadband communications, ultra-reliable (i.e., mission critical) communications, low latency communications, and communications with low-cost and low-complexity devices. The base stations <NUM> may interface with the core network <NUM> through backhaul links <NUM> (e.g., S1, etc.) and may perform radio configuration and scheduling for communication with the UEs <NUM>, or may operate under the control of a base station controller (not shown). In various examples, the base stations <NUM> may communicate, either directly or indirectly (e.g., through core network <NUM>), with each other over backhaul links <NUM> (e.g., X2, etc.), which may be wired or wireless communication links.

The base stations <NUM> may wirelessly communicate with the UEs <NUM> via one or more base station antennas. Each of the base station <NUM> sites may provide communication coverage for a respective geographic coverage area <NUM>. In some examples, a base station <NUM> may be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an evolved NodeB (eNB), a Home NodeB, a Home eNodeB, or some other suitable terminology. The geographic coverage area <NUM> for a base station <NUM> may be divided into sectors (not shown) making up a portion of the coverage area. The wireless communication system <NUM> may include base stations <NUM> of different types (e.g., macro or small cell base stations). There may be overlapping geographic coverage areas <NUM> for different technologies.

In some examples, the wireless communication system <NUM> may include an LTE/LTE-A network and may employ narrowband communication techniques, as described below. In LTE/LTE-A networks, the term eNB may be used to describe the base stations <NUM>. The wireless communication system <NUM> may be a Heterogeneous LTE/LTE-A network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB or base station <NUM> may provide communication coverage for a macro cell, a small cell, or other types of cell. The term "cell" is a 3GPP term that can be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc.) of a carrier or base station, depending on context.

A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell may be a lower-powered base station, as compared with a macro cell that may operate in the same or different (e.g., contention-free, contention-based, etc.) radio frequency spectrum bands as macro cells. A pico cell may cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider. A femto cell also may cover a relatively small geographic area (e.g., a home) and may provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like). An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB or a home eNB.

The wireless communication system <NUM> may support synchronous or asynchronous operation.

The communication networks that may accommodate some of the various disclosed examples may be packet-based networks that operate according to a layered protocol stack. The MAC layer may also use HARQ to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE <NUM> and the base stations <NUM> or core network <NUM> supporting radio bearers for the user plane data. At the Physical (PHY) layer, the transport channels may be mapped to Physical channels.

Time intervals in LTE or NR may be expressed in multiples of a basic time unit (which may be a sampling period of Ts = <NUM>/<NUM>,<NUM>,<NUM> seconds). Time resources may be organized according to radio frames of length of <NUM> (Tf = 307200Ts), which may be identified by a system frame number (SFN) ranging from <NUM> to <NUM>. Each frame may include ten <NUM> subframes numbered from <NUM> to <NUM>. A subframe may be further divided into two. <NUM> slots, each of which contains <NUM> or <NUM> modulation symbol periods (depending on the length of the cyclic prefix prepended to each symbol). Excluding the cyclic prefix, each symbol contains <NUM> sample periods. In some cases the subframe may be the smallest scheduling unit, also known as a TTI. In other cases, a TTI may be shorter than a subframe or may be dynamically selected (e.g., in short TTI bursts or in selected component carriers using short TTIs).

A resource element may consist of one symbol period and one subcarrier (e.g., a <NUM> frequency range). A resource block may contain <NUM> consecutive subcarriers in the frequency domain and, for a normal cyclic prefix in each OFDM symbol, <NUM> consecutive OFDM symbols in the time domain (<NUM> slot), or <NUM> resource elements. The number of bits carried by each resource element may depend on the modulation scheme (the configuration of symbols that may be selected during each symbol period). Thus, the more resource blocks that a UE receives and the higher the modulation scheme, the higher the data rate may be.

The UEs <NUM> may be dispersed throughout the wireless communication system <NUM>, and each UE <NUM> may be stationary or mobile. A UE <NUM> may also include or be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE <NUM> may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a NB-LTE device, a M2M device, a Machine Type Communication (MTC) device, a NB-IoT device or the like. A UE may be able to communicate with various types of base stations and network equipment, including macro eNBs, small cell eNBs, relay base stations, and the like.

The communication links <NUM> shown in wireless communication system <NUM> may include downlink (DL) transmissions, from a base station <NUM> to a UE <NUM>, or uplink (UL) transmissions, from a UE <NUM> to a base station <NUM>. The DL transmissions may also be called forward link transmissions, while the UL transmissions may also be called reverse link transmissions. The communication links <NUM> may include dedicated Physical Uplink Control Channel (PUCCH) resources for narrowband communication, as described in the present disclosure.

In some examples, each communication link <NUM> may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies) modulated according to the various radio technologies described above. Each modulated signal may be sent on a different sub-carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. The communication links <NUM> may transmit bidirectional communications using a frequency division duplexing (FDD) operation (e.g., using paired spectrum resources) or a time division duplexing (TDD) operation (e.g., using unpaired spectrum resources). Frame structures for FDD operation (e.g., frame structure type <NUM>) and TDD operation (e.g., frame structure type <NUM>) may be defined.

In some examples, the wireless communication system <NUM> may support operation over a contention-free radio frequency spectrum band (e.g., a radio frequency spectrum band for which transmitting apparatuses may not contend for access because the radio frequency spectrum band is licensed to particular users for particular uses (e.g., a licensed radio frequency spectrum band usable for LTE/LTE-A communications)) or a contention-based radio frequency spectrum band (e.g., a radio frequency spectrum band for which transmitting apparatuses may contend for access (e.g., a radio frequency spectrum band that is available for unlicensed use, such as Wi-Fi use, a radio frequency spectrum band that is available for use by different radio access technologies, or a radio frequency spectrum band that is available for use by multiple operators in an equally shared or prioritized manner)). Upon winning contention for access to a channel of the contention-based radio frequency spectrum band, a transmitting apparatus (e.g., a base station <NUM> or UE <NUM>) may transmit one or more channel reservation signals (e.g., one or more channel usage beacon signals (CUBS) over the channel. The CUBS may reserve the channel by providing a detectable energy on the channel. The CUBS may also serve to identify the transmitting apparatus or synchronize the transmitting apparatus and a receiving apparatus.

In some cases, the wireless communication system <NUM> may utilize one or more eCCs. An eCC may be characterized by one or more features including: wide bandwidth, short symbol duration, wide tone spacing, smaller transmission time intervals (TTIs), and operation in a contention-based radio frequency spectrum band (or in a contention-free radio frequency spectrum band). In some cases, an eCC may be associated with a carrier aggregation (CA) configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal backhaul link). An eCC may also be configured for use in unlicensed spectrum or shared spectrum (where more than one operator is allowed to use the spectrum). An eCC characterized by wide bandwidth may include one or more segments that may be utilized by UEs <NUM> that are not capable of monitoring the whole bandwidth or prefer to use a limited bandwidth (e.g., to conserve power).

A shorter symbol duration may be associated with increased subcarrier spacing. A TTI in an eCC may consist of one or multiple symbols. In some cases, the TTI duration (that is, the number of symbols in a TTI) may be variable. A shorter symbol duration is associated with increased subcarrier spacing. A device, such as a UE <NUM> or base station <NUM>, utilizing eCCs may transmit wideband signals (e.g., <NUM>, <NUM>, <NUM>, <NUM>, etc.) at reduced symbol durations (e.g., <NUM> microseconds). A TTI in eCC may consist of one or multiple symbols. In some cases, the TTI duration (that is, the number of symbols in a TTI) may be variable.

In some cases, wireless system <NUM> may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless system <NUM> may employ LTE License Assisted Access (LTE-LAA) or LTE Unlicensed (LTE U) radio access technology or NR technology in an unlicensed band such as the <NUM> Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, wireless devices such as base stations <NUM> and UEs <NUM> may employ listen-before-talk (LBT) procedures to ensure the channel is clear before transmitting data. In some cases, operations in unlicensed bands may be based on a carrier aggregation (CA) configuration in conjunction with component carriers (CCs) operating in a licensed band. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, or both. Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD) or a combination of both.

<FIG> shows a wireless communication system <NUM> in which LTE/LTE-A CCs or eCCs may be deployed under different scenarios using a contention-based radio frequency spectrum band, in accordance with various aspects of the present disclosure. More specifically, <FIG> illustrates examples of a supplemental downlink mode (also referred to as a first licensed assisted access mode), a carrier aggregation mode (also referred to as a second licensed assisted access mode), and a standalone mode, in which LTE/LTE-A and/or eCC OFDM numerology is employed using a contention-based radio frequency spectrum band. The wireless communication system <NUM> may be an example of portions of the wireless communication system <NUM> described with reference to <FIG>. Moreover, a first base station <NUM>-a and a second base station <NUM>-b may be examples of aspects of one or more of the base stations <NUM> described with reference to <FIG>, while a first UE <NUM>-a, a second UE <NUM>-b, and a third UE <NUM>-c may be examples of aspects of one or more of the UEs <NUM> described with reference to <FIG>.

In the example of the supplemental downlink mode (e.g., the first licensed assisted access mode) in the wireless communication system <NUM>, the first base station <NUM>-a may transmit OFDMA waveforms to the first UE <NUM>-a using a downlink channel <NUM>. The downlink channel <NUM> may be associated with a frequency F1 in a contention-based radio frequency spectrum band. The first base station <NUM>-a may transmit OFDMA waveforms to the first UE <NUM>-a using a first bidirectional link <NUM> and may receive SC-FDMA waveforms from the first UE <NUM>-a using the first bidirectional link <NUM>. The first bidirectional link <NUM> may be associated with a frequency F4 in a contention-free radio frequency spectrum band. The downlink channel <NUM> in the contention-based radio frequency spectrum band and the first bidirectional link <NUM> in the contention-free radio frequency spectrum band may operate contemporaneously. The downlink channel <NUM> may provide a downlink capacity offload for the first base station <NUM>-a. In some examples, the downlink channel <NUM> may be used for unicast services (e.g., addressed to one UE) or for multicast services (e.g., addressed to several UEs). This scenario may occur with any service provider (e.g., a mobile network operator (MNO)) that uses a contention-free radio frequency spectrum and needs to relieve some of the traffic or signaling congestion.

In the example of the carrier aggregation mode (e.g., the second licensed assisted access mode) in the wireless communication system <NUM>, the first base station <NUM>-a may transmit OFDMA waveforms to the second UE <NUM>-b using a second bidirectional link <NUM> and may receive OFDMA waveforms, SC-FDMA waveforms, or resource block interleaved FDMA waveforms from the second UE <NUM>-b using the second bidirectional link <NUM>. The second bidirectional link <NUM> may be associated with the frequency F1 in the contention-based radio frequency spectrum band. The first base station <NUM>-a may also transmit OFDMA waveforms to the second UE <NUM>-b using a third bidirectional link <NUM> and may receive SC-FDMA waveforms from the second UE <NUM>-b using the third bidirectional link <NUM>. The third bidirectional link <NUM> may be associated with a frequency F2 in a contention-free radio frequency spectrum band. The second bidirectional link <NUM> may provide a downlink and uplink capacity offload for the first base station <NUM>-a. Like the supplemental downlink mode (e.g., licensed assisted access mode) described above, this scenario may occur with any service provider (e.g., MNO) that uses a contention-free radio frequency spectrum and needs to relieve some of the traffic or signaling congestion.

As described above, one type of service provider that may benefit from the capacity offload offered by using LTE/LTE-A in a contention-based radio frequency spectrum band is a traditional MNO having access rights to an LTE/LTE-A contention-free radio frequency spectrum band. For these service providers, an operational example may include a bootstrapped mode (e.g., supplemental downlink, carrier aggregation) that uses the LTE/LTE-A primary component carrier (PCC) on the contention-free radio frequency spectrum band and at least one secondary component carrier (SCC) on the contention-based radio frequency spectrum band.

In the carrier aggregation mode, data and control may, for example, be communicated in the contention-free radio frequency spectrum band (e.g., via first bidirectional link <NUM> or third bidirectional link <NUM>) while data may, for example, be communicated in the contention-based radio frequency spectrum band (e.g., via second bidirectional link <NUM>). The carrier aggregation mechanisms supported when using a contention-based radio frequency spectrum band may fall under a hybrid frequency division duplexing-time division duplexing (FDD-TDD) carrier aggregation or a TDD-TDD carrier aggregation with different symmetry across component carriers.

In one example of a standalone mode in the wireless communication system <NUM>, the second base station <NUM>-b may transmit OFDMA waveforms to the third UE <NUM>-c using a bidirectional link <NUM> and may receive OFDMA waveforms, SC-FDMA waveforms, or resource block interleaved FDMA waveforms from the third UE <NUM>-c using the bidirectional link <NUM>. The bidirectional link <NUM> may be associated with the frequency F3 in the contention-based radio frequency spectrum band. The standalone mode may be used in non-traditional wireless access scenarios, such as in-stadium access (e.g., unicast, multicast). An example of a type of service provider for this mode of operation may be a stadium owner, cable company, event host, hotel, enterprise, or large corporation that does not have access to a contention-free radio frequency spectrum band.

In some examples, a transmitting apparatus such as one of the base stations <NUM> described with reference to <FIG> and <FIG>, or one of the UEs <NUM> described with reference to <FIG> and <FIG>, may use a gating interval to gain access to a channel of a contention-based radio frequency spectrum band (e.g., to a physical channel of the contention-based radio frequency spectrum band). In some examples, the gating interval may be synchronous and periodic. For example, the periodic gating interval may be synchronized with at least one boundary of an LTE/LTE-A radio interval. In other examples, the gating interval may be asynchronous. The gating interval may define the application of a contention-based protocol, such as a Listen-Before-Talk (LBT) protocol based on the LBT protocol specified in European Telecommunications Standards Institute (ETSI) (EN <NUM><NUM>). When using a gating interval that defines the application of an LBT protocol, the gating interval may indicate when a transmitting apparatus needs to perform a contention procedure (e.g., an LBT procedure) such as a Clear Channel Assessment (CCA) procedure or an eCCA procedure. The outcome of the CCA procedure or eCCA procedure may indicate to the transmitting apparatus whether a channel of a contention-based radio frequency spectrum band is available or in use for the gating interval (e.g., an LBT radio frame or transmission burst). When a CCA procedure or eCCA procedure indicates the channel is available for a corresponding LBT radio frame or transmission burst (e.g., "clear" for use), the transmitting apparatus may reserve or use the channel of the contention-based radio frequency spectrum band during part or all of the LBT radio frame. When the CCA procedure indicates that the channel is not available (e.g., that the channel is in use or reserved by another transmitting apparatus), the transmitting apparatus may be prevented from using the channel during the LBT radio frame.

Transmissions made in the wireless communication system <NUM> or <NUM> is encoded. In the case of eCC transmissions (and other transmissions), the transmissions is encoded using TC encoding or LDPCC encoding. When using TC encoding, a payload (or transport block) is segmented into multiple code blocks. In some examples, the size of each code block may be less than or equal to <NUM>,<NUM> bits, and a <NUM> bit CRC may be generated for (and added to) each code block. The CRC provides support for a code block level acknowledgement (ACK) or non-acknowledgement (NAK) having a sufficiently low error probability. When using LDPCC encoding (e.g., IEEE Std. 11n LDPCC encoding) in its native form, parity checks can be used to check whether a decoded sequence is a valid codeword. However, the parity checks are short and may not be associated with a sufficiently low error probability (e.g., the error probability may not be equivalent to the error probability associated with TC decoding ACKs/NAKs.

One way to decrease the error probability associated with LDPCC decoding is to generate a CRC per LDPCC codeword. However, the overhead in doing so can be relatively high, as LDPCC codewords can be relatively short. Alternatively, a CRC may generated at a LDPCC code block level. A payload may in some cases be segmented into LDPCC code blocks that are about the same size as TC code blocks (e.g., code blocks that are no longer than <NUM>,<NUM> bits). A LDPCC code block size may be selected such that the overhead of adding a CRC to the code block is sufficiently small (as determined by the application). A LDPCC code block, with CRC, may be further divided into multiple LDPCC codewords. In some examples, the LDPCC codewords may have equal codeword lengths. However, in the case of equal codeword lengths, the allowed set of LDPCC code block lengths may be smaller than the allowed set of TC code block lengths.

Given a CRC per LDPCC code block, LDPCC encoded payloads may be ACK'd/NAK'd at the code block level (e.g., all of the LDPCC codewords corresponding to a LDPCC code block may be ACK'd or NAK'd as a bundle).

<FIG> shows a diagram <NUM> of a payload <NUM> that is segmented into code blocks before the code blocks are encoded using LDPCC encoding, in accordance with various aspects of the present disclosure. The payload <NUM> may be transmitted, for example, by any of the base stations <NUM> or UEs <NUM> described with reference to <FIG> or <FIG>.

When the payload <NUM> is encoded using LDPCC encoding, the payload <NUM> is segmented into a plurality of LDPCC code blocks, including a first code block (CB0), a second code block (CB1), a third code block (CB2), and a fourth code block (CB3). A CRC is then generated for each code block (e.g., a first CRC (CRC0) may be generated for the first code block (CB0), a second CRC (CRC1) is generated for the second code block (CB1), a third CRC (CRC2) is generated for the third code block (CB2), and a fourth CRC (CRC3) is generated for the fourth code block (CB3)). Each LDPCC code block and associated CRC may then be encoded in a plurality of LDPCC codewords (e.g., the first code block (CB0) and first CRC (CRC0) may be encoded in the LDPCC codewords CW00, CW01, and CW02; the second code block (CB1) and second CRC (CRC1) may be encoded in the LDPCC codewords CW10, CW11, and CW12; the third code block (CB2) and third CRC (CRC2) may be encoded in the LDPCC codewords CW20, CW21, and CW22; and the fourth code block (CB3) and fourth CRC (CRC3) may be encoded in the LDPCC codewords CW30, CW31, and CW32).

<FIG> is a flow chart illustrating an example method <NUM> for unified code block segmentation, in accordance with various aspects of the present disclosure. In some examples, the method <NUM> may be performed by a device such as one of the base stations <NUM> or UEs <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> may receive, as input, a transmission data rate (e.g., a modulation and coding scheme (MCS)), a transmission resource size, or a combination thereof.

At block <NUM>, the method <NUM> may include determining a payload size (Npld) of a payload. In some examples, the payload size may be based at least in part on the transmission data rate or the transmission resource size.

At block <NUM>, the method <NUM> includes selecting an encoding type for the payload. The encoding type may be based on the payload size. When the payload size is less than a threshold, a LDPCC encoding type may be selected for the payload, and the method <NUM> may continue at block <NUM>. When the payload size is greater than the threshold, a TC encoding type may be selected for the payload, and the method <NUM> may continue at block <NUM>.

At block <NUM>, the method <NUM> includes segmenting the payload into a plurality of LDPCC code blocks; and at block <NUM>, the method <NUM> includes segmenting the payload into a plurality of TC code blocks. In some examples, a same code block size limit (N<NUM>) may be applied to the segmentation performed at block <NUM> or <NUM>. In some examples, N<NUM>=<NUM>, as in an LTE/LTE-A network. Regardless of whether a payload is segmented into code blocks at block <NUM> or <NUM>, the payload (or transport block (TB)) may be split into a minimum number of code blocks, subject to the N<NUM> code block size limit, if any. Each of the code blocks have a same size. In some examples, filler bits may be combined with the payload to maintain an equal code block length. In some examples, the size of the code blocks used to segment the payload at block <NUM> (and in some cases, at block <NUM>) may be identified from a list of allowed code block sizes.

At block <NUM>, the method <NUM> includes generating a CRC for each of the code blocks received from block <NUM> or <NUM>.

At block <NUM>, the method <NUM> branches to one of blocks <NUM> or <NUM>, depending on the encoding type selected at block <NUM>. When a LDPCC encoding type is selected at block <NUM>, the method <NUM> continues at block <NUM>. When a TC encoding type is selected at block <NUM>, the method <NUM> continues at block <NUM>.

At block <NUM>, the method <NUM> includes encoding each code block and associated CRC in one or more LDPCC codewords. In some examples, each codeword associated with a same code block may be have an equal codeword length, and each code block may be encoded in an integer number of LDPCC codewords (and conversely, each LDPCC code block identified at block <NUM> may be an integer multiple of the equal codeword length).

At block <NUM>, the method <NUM> includes encoding each code block and associated CRC in one or more TC codewords. At block <NUM>, the generated codewords are transmitted.

In some examples of the method <NUM>, a code block length of each code block associated with a LDPCC encoded payload may be selected to be an integer multiple of an equal codeword length. In some examples, the method <NUM> may include combining filler bits with a LDPCC encoded payload to maintain the selected code block length.

In some examples of the method <NUM>, a code block length of each code block of a LDPCC encoded payload may be based at least in part on a length of a TC code block, or a LTE or LTE-A code block, used to segment a TC encoded payload. In some examples, a length of a code block used to segment a TC encoded payload may be selected based at least in part on a length of a code block used to segment a LDPCC encoded payload.

<FIG> shows a diagram <NUM> of a device <NUM> for use in wireless communication, in accordance with various aspects of the present disclosure. The device <NUM> may be an example of aspects of one or more of the base stations <NUM> or UEs <NUM> described with reference to <FIG> or <FIG>. The device <NUM> may also be or include a processor. The device <NUM> may include a receiver <NUM>, a wireless communication manager <NUM>, or a transmitter <NUM>. Each of these components may be in communication with each other.

The components of the device <NUM> may, individually or collectively, be implemented using one or more application-specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In some other examples, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, Field Programmable Gate Array (FPGA), a System-on-Chip (SoC), and/or other types of Semi-Custom ICs), which may be programmed in any manner known in the art. The functions of each component may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.

In some examples, the receiver <NUM> may include at least one radio frequency (RF) receiver, such as at least one RF receiver operable to receive transmissions over one or more radio frequency spectrum bands. In some examples, the receiver <NUM> may include an array of receive antennas. In some examples, the one or more radio frequency spectrum bands may be used for LTE/LTE-A or eCC communications, as described, for example, with reference to <FIG>. The receiver <NUM> may be used to receive various types of data or control signals (i.e., transmissions) over one or more communication links (or channels) of a wireless communication system, such as one or more communication links (or channels) of the wireless communication system <NUM> or <NUM> described with reference to <FIG> or <FIG>. In some examples, the receiver <NUM> may also or alternatively include one or more wired receivers.

In some examples, the transmitter <NUM> may include at least one RF transmitter, such as at least one RF transmitter operable to transmit over one or more radio frequency spectrum bands. In some examples, the transmitter <NUM> may include an array of transmit antennas. In some examples, the one or more radio frequency spectrum bands may be used for LTE/LTE-A or eCC communications, as described, for example, with reference to <FIG>. The transmitter <NUM> may be used to transmit various types of data or control signals (i.e., transmissions) over one or more communication links (or channels) of a wireless communication system, such as one or more communication links (or channels) of the wireless communication system <NUM> or <NUM> described with reference to <FIG> or <FIG>. In some examples, the transmitter <NUM> may also or alternatively include one or more wired transmitters.

In some examples, the wireless communication manager <NUM> may be used to manage one or more aspects of wireless communication for the device <NUM>. In some examples, part of the wireless communication manager <NUM> may be incorporated into or shared with the receiver <NUM> or the transmitter <NUM>. In some examples, the wireless communication manager <NUM> may include a payload encoding type selector <NUM>, a payload segmenter <NUM>, a CRC generator <NUM>, an encoding manager <NUM>, or a transmission manager <NUM>.

The payload encoding type selector <NUM> may be used to select an encoding type for each payload of a plurality of payloads. The selecting includes selecting a LDPCC encoding type for at least a first payload and selecting a TC encoding type for at least a second payload. The payload segmenter <NUM> may be used to segment each payload into a plurality of code blocks. The CRC generator <NUM> may be used to generate, for each code block, a CRC. The encoding manager <NUM> may be used to encode each code block and associated CRC in one or more codewords of a plurality of codewords. The encoding is based at least in part on the selected encoding type for a payload associated with the code block. The transmission manager <NUM> may be used to transmit the codewords.

<FIG> shows a diagram <NUM> of a wireless communication manager <NUM>-a for use in wireless communication, in accordance with various aspects of the present disclosure. The wireless communication manager <NUM>-a may be an example of aspects of the wireless communication manager <NUM> described with reference to <FIG>.

The components of the wireless communication manager <NUM>-a may, individually or collectively, be implemented using one or more ASICs adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In some other examples, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, FPGAs, a SoC, and/or other types of Semi-Custom ICs), which may be programmed in any manner known in the art. The functions of each component may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.

In some examples, the wireless communication manager <NUM>-a may be used to manage one or more aspects of wireless communication for a base station, UE, or other device, such as one of the base stations <NUM> or UEs <NUM> described with reference to <FIG> or <FIG>, or the device <NUM> described with reference to <FIG>. In some examples, part of the wireless communication manager <NUM>-a may be incorporated into or shared with a receiver or a transmitter (e.g., the receiver <NUM> or the transmitter <NUM> described with reference to <FIG>). In some examples, the wireless communication manager <NUM>-a may include a payload characteristic identifier <NUM>, a payload encoding type selector <NUM>-a, a payload information communicator <NUM>, a payload segmenter <NUM>-a, a CRC generator <NUM>-a, an encoding manager <NUM>-a, a code block length selector <NUM>, a transmission manager <NUM>-a, an ACK/NAK manager <NUM>, or a retransmission manager <NUM>.

The payload characteristic identifier <NUM> may be used to identify one or more characteristics of a plurality of payloads. In some examples, the one or more characteristics may include a payload size. In some examples, a characteristic of a payload may be based solely on the payload. In some examples, a characteristic of a payload may be based on characteristics of a plurality of payloads (e.g., a characteristic of a payload may be an average value or a maximum value).

The payload encoding type selector <NUM>-a may be used to select an encoding type for each payload of a plurality of payloads. The selecting includes selecting a LDPCC encoding type for at least a first payload and selecting a TC encoding type for at least a second payload. In some examples, an encoding type for a payload may be selected based at least in part on a characteristic of the payload, as identified by the payload characteristic identifier <NUM>.

The payload information communicator <NUM> may be used to transmit, for at least one of the payloads, at least one of: an indication of the payload size, an indication of the transmission data rate, an indication of the transmission resource size, or an indication of the selected encoding type.

The payload segmenter <NUM>-a may be used to segment each payload into a plurality of code blocks. The CRC generator <NUM>-a may be used to generate, for each code block, a CRC. The encoding manager <NUM>-a may be used to encode each code block and associated CRC in one or more codewords of a plurality of codewords. The encoding is based at least in part on the selected encoding type for a payload associated with the code block. In some examples, each codeword associated with a code block of the first payload may have an equal codeword length.

The code block length selector <NUM> may be used, in conjunction with the encoding manager <NUM>-a, and in some examples, to select a code block length of each code block associated with at least the first payload to be an integer multiple of the equal codeword length. In some examples, the code block length selector <NUM> may combine filler bits with the first payload, prior to or as part of the encoding performed by the encoding manager <NUM>-a, to maintain the selected code block length. In some examples, each code block associated with the first payload may have a code block length that is an integer multiple of an equal codeword length associated with each codeword corresponding to the code block.

In some examples, the code block length selector <NUM> may be used to select a code block length of each code block of at least the first payload based on a length of a TC code block, or a LTE or LTE-A code block, used to segment at least the second payload. In some examples, the code block length selector <NUM> may be used to select a length of a TC code block used to segment at least the second payload based at least in part on a length of each code block used to segment at least the first payload. The code block length(s) may be selected prior to or as part of the encoding performed by the encoding manager <NUM>-a. The transmission manager <NUM>-a may be used to transmit the codewords.

The ACK/NAK manager <NUM> may be used to receive one of an ACK or a NAK for each code block. The retransmission manager <NUM> may be used, when a NAK is received for a code block, to retransmit one or more codewords and CRCs associated with the code block. For example, when a NAK of a code block associated with the first payload is received, the retransmission manager <NUM> may be used to retransmit a plurality of LDPCC codewords associated with the code block and a CRC associated with the code block.

<FIG> shows a diagram <NUM> of a device <NUM> for use in wireless communication, in accordance with various aspects of the present disclosure, which do not fall under the scope of the claimed invention. The device <NUM> may be an example of aspects of one or more of the base stations <NUM> or UEs <NUM> described with reference to <FIG> or <FIG>, or aspects of the device <NUM> described with reference to <FIG>. The device <NUM> may also be or include a processor. The device <NUM> may include a receiver <NUM>, a wireless communication manager <NUM>, or a transmitter <NUM>. Each of these components may be in communication with each other.

The components of the device <NUM> may, individually or collectively, be implemented using one or more ASICs adapted to perform some or all of the applicable functions in hardware. Alternatively, the functions may be performed by one or more other processing units (or cores), on one or more integrated circuits. In some other examples, other types of integrated circuits may be used (e.g., Structured/Platform ASICs, FPGAs, a SoC, and/or other types of Semi-Custom ICs), which may be programmed in any manner known in the art. The functions of each component may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.

In some examples, the receiver <NUM> may include at least one RF receiver, such as at least one RF receiver operable to receive transmissions over one or more radio frequency spectrum bands. In some examples, the receiver <NUM> may include an array of receive antennas. In some examples, the one or more radio frequency spectrum bands may be used for LTE/LTE-A or eCC communications, as described, for example, with reference to <FIG>. The receiver <NUM> may be used to receive various types of data or control signals (i.e., transmissions) over one or more communication links (or channels) of a wireless communication system, such as one or more communication links (or channels) of the wireless communication system <NUM> or <NUM> described with reference to <FIG> or <FIG>. In some examples, the receiver <NUM> may also or alternatively include one or more wired receivers.

In some examples, the wireless communication manager <NUM> may be used to manage one or more aspects of wireless communication for the device <NUM>. In some examples, part of the wireless communication manager <NUM> may be incorporated into or shared with the receiver <NUM> or the transmitter <NUM>. In some examples, the wireless communication manager <NUM> may include a payload reception manager <NUM>, a codeword decoder <NUM>, or an ACK/NAK manager <NUM>.

The payload reception manager <NUM> may be used to receive a plurality of codewords associated with at least a first payload encoded using a LDPCC encoding type and at least a second payload encoded using a TC encoding type. The codeword decoder <NUM> may be used to decode a set of the codewords associated with the first payload and a CRC. The ACK/NAK manager <NUM> may be used to transmit one of an ACK or a NAK for the set of the codewords.

<FIG> shows a diagram <NUM> of a wireless communication manager <NUM>-a for use in wireless communication, in accordance with various aspects of the present disclosure, which do not fall under the claimed invention. The wireless communication manager <NUM>-a may be an example of aspects of the wireless communication manager <NUM> described with reference to <FIG>.

In some examples, the wireless communication manager <NUM>-a may be used to manage one or more aspects of wireless communication for a base station, UE, or other device, such as one of the base stations <NUM> or UEs <NUM> described with reference to <FIG> or <FIG>, or the device <NUM> described with reference to <FIG>. In some examples, part of the wireless communication manager <NUM>-a may be incorporated into or shared with a receiver or a transmitter (e.g., the receiver <NUM> or the transmitter <NUM> described with reference to <FIG>). In some examples, the wireless communication manager <NUM>-a may include a payload reception manager <NUM>-a, a payload encoding type identifier <NUM>, a codeword decoder <NUM>-a, or an ACK/NAK manager <NUM>-a.

The payload reception manager <NUM>-a may be used to receive a plurality of codewords associated with at least a first payload encoded using a LDPCC encoding type and at least a second payload encoded using a TC encoding type.

The payload encoding type identifier <NUM> may be used to receive an indication that the LDPCC encoding type is used to encode the first payload, or receive an indication that the TC encoding type is used to encode the second payload. The payload encoding type identifier <NUM> may additionally or alternatively be used to determine the LDPCC encoding type is used for the first payload, or determine the TC encoding type is used for the second payload, based at least in part on receiving an indication of a payload size, an indication of a transmission data rate, an indication of a transmission resource size, or a combination thereof for the first payload or the second payload.

The codeword decoder <NUM>-a may be used to decode a set of the codewords associated with the first payload and a CRC. The ACK/NAK manager <NUM>-a may be used to transmit one of an ACK or a NAK for the set of the codewords.

<FIG> shows a diagram <NUM> of a base station <NUM>-c (e.g., a base station forming part or all of an eNB) for use in wireless communication, in accordance with various aspects of the present disclosure. In some examples, the base station <NUM>-c may be an example of aspects of one or more of the base stations <NUM> described with reference to <FIG> or <FIG>, or aspects of one or more of device <NUM> or <NUM> described with reference to <FIG> or <FIG>. The base station <NUM>-c may be configured to implement or facilitate at least some of the base station or device features or functions described with reference to <FIG>.

The base station <NUM>-c may include a base station processor <NUM>, a base station memory <NUM>, at least one base station transceiver (represented by base station transceiver(s) <NUM>), at least one base station antenna (represented by base station antenna(s) <NUM>), or a base station wireless communication manager <NUM>. The base station <NUM>-c may also include one or more of a base station communicator <NUM> or a network communicator <NUM>. Each of these components may be in communication with each other, directly or indirectly, over one or more buses <NUM>.

The base station memory <NUM> may include random access memory (RAM) or read-only memory (ROM). The base station memory <NUM> may store computer-readable, computer-executable code <NUM> containing instructions executable by the base station processor <NUM> to perform various functions described herein related to wireless communication, including, for example, selecting an encoding type, from among a LDPCC encoding type and a TC encoding type, for each payload of a plurality of payloads, or receiving a plurality of codewords associated with at least a first payload encoded using a LDPCC encoding type and a second payload encoded using a TC encoding type. Alternatively, the computer-executable code <NUM> may not be directly executable by the base station processor <NUM> but be configured to cause the base station <NUM>-c (e.g., when compiled and executed) to perform various of the functions described herein.

The base station processor <NUM> may include an intelligent hardware device, e.g., a central processing unit (CPU), a microcontroller, an ASIC, etc. The base station processor <NUM> may process information received through the base station transceiver(s) <NUM>, the base station communicator <NUM>, or the network communicator <NUM>. The base station processor <NUM> may also process information to be sent to the transceiver(s) <NUM> for transmission through the antenna(s) <NUM>, to the base station communicator <NUM>, for transmission to one or more other base stations <NUM>-d and <NUM>-e, or to the network communicator <NUM> for transmission to a core network <NUM>-a, which may be an example of one or more aspects of the core network <NUM> described with reference to <FIG>. The base station processor <NUM> may handle, alone or in connection with the base station wireless communication manager <NUM>, various aspects of communicating over (or managing communications over) one or more radio frequency spectrum bands.

The base station transceiver(s) <NUM> may include a modem configured to modulate packets and provide the modulated packets to the base station antenna(s) <NUM> for transmission, and to demodulate packets received from the base station antenna(s) <NUM>. The base station transceiver(s) <NUM> may, in some examples, be implemented as one or more base station transmitters and one or more separate base station receivers. The base station transceiver(s) <NUM> may support communications in the one or more radio frequency spectrum bands. The base station transceiver(s) <NUM> may be configured to communicate bi-directionally, via the antenna(s) <NUM>, with one or more UEs, such as one or more of the UEs <NUM> described with reference to <FIG> or <FIG>, or one or more of device <NUM> or <NUM> described with reference to <FIG> or <FIG>. The base station <NUM>-c may, for example, include multiple base station antennas <NUM> (e.g., an antenna array). The base station <NUM>-c may communicate with the core network <NUM>-a through the network communicator <NUM>. The base station <NUM>-c may also communicate with other base stations, such as the base stations <NUM>-d and <NUM>-e, using the base station communicator <NUM>.

The base station wireless communication manager <NUM> may be configured to program or control some or all of the features or functions described with reference to <FIG> related to wireless communication over one or more radio frequency spectrum bands. The base station wireless communication manager <NUM>, or portions of it, may include a processor, or some or all of the functions of the base station wireless communication manager <NUM> may be performed by the base station processor <NUM> or in connection with the base station processor <NUM>. In some examples, the base station wireless communication manager <NUM> may be an example of the wireless communication manager <NUM> or <NUM> described with reference to <FIG>, <FIG>, <FIG>, or <FIG>.

<FIG> shows a diagram <NUM> of a UE <NUM>-d for use in wireless communication, in accordance with various aspects of the present disclosure. The UE <NUM>-d may have various configurations and may be a wireless communication device, a personal computer (e.g., a laptop computer, a netbook computer, a tablet computer, etc.), a handheld device, a cellular telephone, a smart phone, a cordless phone, a wireless modem, a WLL station, a personal PDA, a DVR, an internet appliance, a gaming console, an e-reader, a narrow-band device, an IoT device, etc. The UE <NUM>-d may, in some examples, have an internal power supply (not shown), such as a small battery, to facilitate mobile or remote operation. In some examples, the UE <NUM>-d may be an example of aspects of one or more of the UEs <NUM> described with reference to <FIG> or <FIG>, or aspects of one or more of device <NUM> or <NUM> described with reference to <FIG> or <FIG>. The UE <NUM>-d may be configured to implement at least some of the UE or device features or functions described with reference to <FIG>.

The UE <NUM>-d may include a UE processor <NUM>, a UE memory <NUM>, at least one UE transceiver (represented by UE transceiver(s) <NUM>), at least one UE antenna (represented by UE antenna(s) <NUM>), or a UE device wireless communication manager <NUM>. Each of these components may be in communication with each other, directly or indirectly, over one or more buses <NUM>.

The UE memory <NUM> may include RAM or ROM. The UE memory <NUM> may store computer-readable, computer-executable code <NUM> containing instructions executable by the UE processor <NUM> to perform various functions described herein related to wireless communication, including, for example, selecting an encoding type, from among a LDPCC encoding type and a TC encoding type, for each payload of a plurality of payloads, or receiving a plurality of codewords associated with at least a first payload encoded using a LDPCC encoding type and a second payload encoded using a TC encoding type. Alternatively, the computer-executable code <NUM> may not be directly executable by the UE processor <NUM> but be configured to cause the UE <NUM>-d (e.g., when compiled and executed) to perform various of the functions described herein.

The UE processor <NUM> may include an intelligent hardware device, e.g., a CPU, a microcontroller, an ASIC, etc. The UE processor <NUM> may process information received through the UE transceiver(s) <NUM> or information to be sent to the UE transceiver(s) <NUM> for transmission through the UE antenna(s) <NUM>. The UE processor <NUM> may handle, alone or in connection with the UE device wireless communication manager <NUM>, various aspects of communicating over (or managing communications over) one or more radio frequency spectrum bands.

The UE transceiver(s) <NUM> may include a modem configured to modulate packets and provide the modulated packets to the UE antenna(s) <NUM> for transmission, and to demodulate packets received from the UE antenna(s) <NUM>. The UE transceiver(s) <NUM> may, in some examples, be implemented as one or more UE transmitters and one or more separate UE receivers. The UE transceiver(s) <NUM> may support communications in the one or more radio frequency spectrum bands. The UE transceiver(s) <NUM> may be configured to communicate bi-directionally, via the UE antenna(s) <NUM>, with one or more base stations or other devices, such as one or more of the base stations <NUM> described with reference to <FIG>, <FIG>, or <FIG>, or one or more of device <NUM> or <NUM> described with reference to <FIG> or <FIG>. While the UE <NUM>-d may include a single UE antenna, there may be examples in which the UE <NUM>-d may include multiple UE antennas <NUM>.

The UE device wireless communication manager <NUM> may be configured to program or control some or all of the features or functions described with reference to <FIG> related to wireless communication over one or more radio frequency spectrum bands. The UE device wireless communication manager <NUM>, or portions of it, may include a processor, or some or all of the functions of the UE device wireless communication manager <NUM> may be performed by the UE processor <NUM> or in connection with the UE processor <NUM>. In some examples, the UE device wireless communication manager <NUM> may be an example of the wireless communication manager <NUM> or <NUM> described with reference to <FIG>, <FIG>, <FIG>, or <FIG>.

<FIG> is a flow chart illustrating an example of a method <NUM> for wireless communication, in accordance with various aspects of the present disclosure. For clarity, the method <NUM> is described below with reference to aspects of the device <NUM> described with reference to <FIG>, or aspects of one or more of the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>. In some examples, the method <NUM> is described below with reference to one or more aspects of the base station wireless communication manager <NUM> described with reference to <FIG>, or with reference to one or more aspects of the UE device wireless communication manager <NUM> described with reference to <FIG>. In some examples, a device (e.g., a base station or UE) may perform one or more of the functions described below using special-purpose hardware.

At block <NUM>, the method <NUM> includes selecting an encoding type for each payload of a plurality of payloads. The selecting includes selecting a LDPCC encoding type for at least a first payload and selecting a TC encoding type for at least a second payload. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the payload encoding type selector <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> includes segmenting each payload into a plurality of code blocks. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the payload segmenter <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> includes generating, for each code block, a CRC. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the CRC generator <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> includes encoding each code block and associated CRC in one or more codewords of a plurality of codewords. The encoding is based at least in part on the selected encoding type for a payload associated with the code block. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the encoding manager <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> includes transmitting the codewords. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the transmission manager <NUM> described with reference to <FIG> or <FIG>.

<FIG> is a flow chart illustrating an example of a method <NUM> for wireless communication, in accordance with various aspects of the present disclosure. For clarity, the method <NUM> is described below with reference to aspects of the device <NUM> described with reference to <FIG>, or aspects of one or more of the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>. In some examples, the method <NUM> is described below with reference to one or more aspects of the base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>. In some examples, a device (e.g., a base station or UE) may perform one or more of the functions described below using special-purpose hardware.

At block <NUM>, the method <NUM> may include identifying one or more characteristics of a plurality of payloads. In some examples, the one or more characteristics may include a payload size. In some examples, a characteristic of a payload may be based solely on the payload. In some examples, a characteristic of a payload may be based on characteristics of a plurality of payloads (e.g., a characteristic of a payload may be an average value or a maximum value). The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the payload characteristic identifier <NUM> described with reference to <FIG>.

At block <NUM>, the method <NUM> includes selecting an encoding type for each payload of the plurality of payloads. The selecting includes selecting a LDPCC encoding type for at least a first payload and selecting a TC encoding type for at least a second payload. In some examples, an encoding type for a payload may be selected based at least in part on a characteristic of the payload, as identified at block <NUM>. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the payload encoding type selector <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> may include transmitting, for at least one of the payloads, at least one of: an indication of the payload size, an indication of the transmission data rate, an indication of the transmission resource size, or an indication of the selected encoding type. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the payload information communicator <NUM> described with reference to <FIG>.

At block <NUM>, the method <NUM> includes encoding each code block and associated CRC in one or more codewords of a plurality of codewords. The encoding is based at least in part on the selected encoding type for a payload associated with the code block. In some examples of the method <NUM>, each codeword associated with a code block of the first payload may have an equal codeword length. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the encoding manager <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> may include receiving one of an ACK or a NAK for each code block. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the ACK/NAK manager <NUM> described with reference to <FIG>.

At block <NUM>, and when a NAK is received for a code block, the method <NUM> may include retransmitting one or more codewords and CRCs associated with the code block. For example, when a NAK of a code block associated with the first payload is received, the method <NUM> may include retransmitting a plurality of LDPCC codewords associated with the code block and a CRC associated with the code block. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the retransmission manager <NUM> described with reference to <FIG>.

In some examples, the method <NUM> may include selecting a code block length of each code block associated with at least the first payload to be an integer multiple of the equal codeword length. In some examples, the method <NUM> may include combining filler bits with the first payload, prior to or as part of the operation(s) at block <NUM>, to maintain the selected code block length. In some examples, each code block associated with the first payload may have a code block length that is an integer multiple of an equal codeword length associated with each codeword corresponding to the code block.

In some examples, the method <NUM> may include selecting a code block length of each code block of at least the first payload based at least in part on a length of a TC code block, or a LTE or LTE-A code block, used to segment at least the second payload. The code block length may be selected prior to or as part of the operation(s) at block <NUM>.

In some examples, the method <NUM> may include selecting a length of a TC code block used to segment at least the second payload based at least in part on a length of each code block used to segment at least the first payload. The length of the TC code block may be selected prior to or as part of the operation(s) at block <NUM>.

<FIG> is a flow chart illustrating an example of a method <NUM> for wireless communication, in accordance with various aspects of the present disclosure, which do not fall under the scope of the claimed invention. For clarity, the method <NUM> is described below with reference to aspects of the device <NUM> described with reference to <FIG>, or aspects of one or more of the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>. In some examples, the method <NUM> is described below with reference to one or more aspects of the base station wireless communication manager <NUM> described with reference to <FIG>, or with reference to one or more aspects of the UE device wireless communication manager <NUM> described with reference to <FIG>. In some examples, a device (e.g., a base station or UE) may perform one or more of the functions described below using special-purpose hardware.

At block <NUM>, the method <NUM> may include receiving a plurality of codewords associated with at least a first payload encoded using a LDPCC encoding type and at least a second payload encoded using a TC encoding type. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the payload reception manager <NUM> or <NUM>-a described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> may include decoding a set of the codewords associated with the first payload and a CRC. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the codeword decoder <NUM> described with reference to <FIG> or <FIG>.

At block <NUM>, the method <NUM> may include transmitting one of an ACK or a NAK for the set of the codewords. The operation(s) at block <NUM> may be performed using the wireless communication manager <NUM>, <NUM>-a, <NUM>, or <NUM>-a described with reference to <FIG>, <FIG>, <FIG>, or <FIG>, or base station wireless communication manager <NUM> described with reference to <FIG>, or UE device wireless communication manager <NUM> described with reference to <FIG>, or the ACK/NAK manager <NUM> described with reference to <FIG> or <FIG>.

In some examples, the method <NUM> may include receiving an indication that the LDPCC encoding type is used to encode the first payload, or receiving an indication that the TC encoding type is used to encode the second payload. Alternatively, the method <NUM> may include determining the LDPCC encoding type is used for the first payload, or determining the TC encoding type is used for the second payload, based at least in part on receiving an indication of a payload size, an indication of a transmission data rate, an indication of a transmission resource size, or a combination thereof for the first payload or the second payload.

It should be noted that the methods <NUM>, <NUM>, and <NUM> provide examples of methods for wireless communication, and that the operations of the method <NUM>, <NUM>, or <NUM> may be rearranged or otherwise modified.

The detailed description set forth above in connection with the appended drawings describes examples and does not represent all of the examples that may be implemented or that are within the scope of the claims. The terms "example" and "exemplary," when used in this description, mean "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A 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.

Also, as used herein, including in the claims, "or" as used in a list of items (for example, a list of items prefaced by a phrase such as "at least one of" or "one or more of") indicates a disjunctive list such that, for example, a list of "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).

Claim 1:
A method for wireless communication, comprising:
selecting (<NUM>) an encoding type for each payload of a plurality of payloads, the selecting comprising selecting a low density parity check code, LDPCC, encoding type for at least a first payload and selecting a turbo code, TC, encoding type for at least a second payload;
segmenting (<NUM>) each payload into a plurality of code blocks having a same code block size;
generating, (<NUM>) for each code block, a cyclic redundancy check, CRC;
encoding (<NUM>) each code block and associated CRC in one or more codewords of a plurality of codewords, the encoding based at least in part on the selected encoding type for a payload associated with the code block; and
transmitting (<NUM>) the codewords.