CN108713302B

CN108713302B - Method, device and system for transmission acknowledgement control in wireless network

Info

Publication number: CN108713302B
Application number: CN201680082617.XA
Authority: CN
Inventors: 昌文婷; 牛华宁; 朱源; 张羽书; 熊岗; 黄庸瑄; 霍格尔·尤豪斯
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2016-03-25
Filing date: 2016-03-25
Publication date: 2022-03-04
Anticipated expiration: 2036-03-25
Also published as: HK1258372A1; CN108713302A; WO2017161583A1

Abstract

A base station is described herein that may include: a control module to partition a TB into one or more STBs based at least in part on the ACK/NACK parameter and append one or more first level CRC bits to each STB, wherein an STB of the STBs may include one or more code blocks of the TB; and a transceiver for transmitting the TB with the first level CRC bits to the UE. The base station may further include: a transceiver for transmitting a plurality of first code blocks and a first indicator to a UE, and receiving one or more ACK/NACK bits from the UE, wherein the first indicator is also for indicating whether the first code block is a new transport block; and a control module for generating a second indicator to indicate whether the ACK/NACK bit has been successfully received by the base station.

Description

Method, device and system for transmission acknowledgement control in wireless network

Technical Field

Embodiments of the present application relate generally to the field of communications, and more particularly, to transmission acknowledgement control in wireless networks.

Background

In wireless networks (e.g., fifth generation wireless networks), to support wider system bandwidths, high multiple-input multiple-output (MIMO) orders, and/or high modulation orders (e.g., orders for Orthogonal Frequency Division Multiplexing (OFDM)), transport blocks may have larger sizes and/or transport blocks may be divided into multiple sub-transport blocks, which may present challenges for transmission acknowledgement control.

Drawings

Embodiments of the present application are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.

Fig. 1 schematically illustrates a wireless system for transmission acknowledgment control in accordance with various embodiments.

Fig. 2 schematically illustrates an example of a transport block with transmission acknowledgement control, in accordance with various embodiments.

Fig. 3 schematically illustrates a method of appending and transmitting Cyclic Redundancy Check (CRC) bits to a transport block by a transmitter (e.g., an evolved node B) in a wireless system, in accordance with various embodiments.

Fig. 4 schematically illustrates a method of generating and transmitting acknowledgement/negative acknowledgement (ACK/NACK) bits by a receiving side (user equipment) in a wireless system, in accordance with various embodiments.

Fig. 5 schematically illustrates an example of transmission and retransmission combining in a wireless system, in accordance with various embodiments.

Fig. 6 schematically illustrates an example of transmissions and retransmissions under transmission acknowledgement control in a wireless system, in accordance with various embodiments.

Fig. 7 schematically illustrates a method of transmission and retransmission under control of a transmission acknowledgement to be employed by a receiver in a wireless system, in accordance with various embodiments.

Fig. 8 schematically illustrates a method of transmission and retransmission under control of a transmission acknowledgement to be employed by a sender in a wireless system, in accordance with various embodiments.

Fig. 9 schematically illustrates an example system in accordance with various embodiments.

Fig. 10 schematically illustrates an example of a UE device in accordance with various embodiments.

Detailed Description

Illustrative embodiments of the present disclosure include, but are not limited to, methods, systems, and apparatus for transmission acknowledgement control in a wireless network (e.g., a fifth generation wireless network).

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be readily understood by those skilled in the art that some alternative embodiments may be practiced using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be readily understood by those skilled in the art that alternative embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative embodiments.

Further, various operations will be described as multiple discrete operations, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrase "in one embodiment" is used repeatedly. The phrase generally does not refer to the same embodiment; it may refer to the same embodiment. The terms "comprising," "having," and "including" are synonymous, unless the context dictates otherwise. The phrase "A/B" means "A or B". The phrase "A and/or B" means "(A), (B) or (A and B)". The phrase "at least one of A, B and C" means "(A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C)". The phrase "(A) B" means "(B) or (A B)", i.e., A is optional.

Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described without departing from the scope of the embodiments of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly understood that embodiments of the present disclosure are limited only by the claims and the equivalents thereof.

As used herein, the term "module" may refer to, may be part of, or may include the following: an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or a memory (shared, dedicated, or group) that executes one or more software or firmware programs; a combinational logic circuit; and/or other suitable components that provide the described functionality.

Fig. 1 schematically illustrates a wireless system for transmission acknowledgment control in accordance with various embodiments. As shown in fig. 1, the wireless system 100 may include an evolved node b (eNB)101, a User Equipment (UE)201, and/or others, wherein the eNB 101 and the UE 201 may communicate over the wireless system 100 (e.g., a fifth generation wireless network). In some embodiments, the eNB 101 may include: a transceiver 102 for transmitting/receiving information to/from the UE 201; and a control module 103 for controlling transmission acknowledgements at least in part with respect to information transmission between the eNB 101 and the UE. The UE 201 may include: a transceiver 202 for receiving/transmitting information from/to the eNB 101; and a control module 203 for controlling transmission acknowledgements at least in part for information transmission between the UE 201 and the eNB 101.

In some embodiments, the information may include a subframe having at least one Transport Block (TB), one or more Cyclic Redundancy Check (CRC) bits, and/or the like. In other embodiments, the information may include one or more acknowledgement/negative acknowledgement (ACK/NACK) bits indicating that the TB has been successfully/unsuccessfully received, where an ACK may be associated with an acknowledgement of successful reception and a NACK may be associated with a negative acknowledgement of successful reception (i.e., reception is unsuccessful).

In some embodiments, a TB may include a plurality of sub-transport blocks (STBs), where each sub-transport block includes one or more Code Blocks (CBs). The CRC bits may include one or more STB-level CRC bits associated with each STB, which may be used by a recipient (e.g., UE 201 for downlink transmissions or eNB 101 for uplink transmissions) to detect whether a STB was successfully received, and one or more CB-level CRC bits associated with each code block within each STB, which may be used by the recipient to detect whether a code block was successfully received. The TB and CRC attachments may be encoded and concatenated before being sent to the recipient.

In some embodiments, the ACK/NACK bits may include one or more STB-level ACK/NACK bits and one or more CB-level ACK/NACK bits, where each STB-level ACK/NACK bit is associated with each STB and each CB-level ACK/NACK bit is associated with each code block within each STB. More specifically, the STB-level ACK/NACK bits may indicate successful/unsuccessful reception of the associated STB, and the CB-level ACK/NACK bits may indicate successful/unsuccessful reception of the associated code block. The number of code blocks that each STB may include may be determined by the ACK/NACK parameter. For example, the ACK/NACK parameter may indicate the number of STB-level ACK/NACK bits (e.g., parameter N) for successful/unsuccessful reception feedback of the STB_ANCK). As another example, the ACK/NACK parameter may indicate the number of code blocks that one STB level ACK/NACK bit may be bundled (bundle) across TBs (e.g., parameter N_bund.CB)。

With STB-level ACK/NACK bits associated with STBs that include multiple code blocks, the sender (e.g., eNB 101 for downlink transmissions or UE 201 for uplink transmissions) may save time for false detection of each code block within a STB with ACK bits. In addition, if a NACK bit is received, the sender may retransmit the associated STB instead of retransmitting the entire TB, which may help save retransmission overhead. With the CB-level ACK/NACK bits associated with each code block, if a NACK bit is received at an earlier Orthogonal Frequency Division Multiplexing (OFDM) symbol, the sender may retransmit the associated code block instead of retransmitting the entire STB. However, it should be understood that other techniques may implement other embodiments for retransmitting the code block(s) associated with NACK bits. For example, a one-to-one mapping of frequency-time resources to code blocks may be applied such that the code blocks may be retransmitted using the same frequency-time resources as used to transmit the code blocks.

However, it should be understood that other embodiments may implement other techniques for transmission acknowledgment control. For example, code block bundling may not occur across TBs, and thus, a plurality of STB-level CRC bits and/or STB-level ACK/NACK bits may be omitted or replaced with one STB-level CRC bit and/or one STB-level ACK/NACK bit associated with the entire TB. For another example, the CB-level CRC bits and/or the CB-level ACK/NACK bits may be omitted to reduce ACK/NACK overhead.

In some embodiments, the information may include one or more indicators that may assist the recipient (e.g., eNB 101 for uplink transmissions or UE 201 for downlink transmissions) in updating the recipient data buffer associated with the TB. The indicator may include a reset indicator, an ACK/NACK correct receipt indicator, and/or others. In some embodiments, the reset indicator may indicate whether the transmitted code block associated with the reset indicator is all new transport blocks from the sender (e.g., eNB 101 for downlink transmissions or UE 201 for uplink transmissions). The ACK/NACK bit correct reception indicator may indicate whether the sender correctly receives the ACK/NACK bit from the receiver, wherein the ACK/NACK bit may further indicate whether the code block transmitted in the previous transmission is successfully received by/not successfully received by the receiver.

In some embodiments, the receiver may reset the data buffer to an initial state at least in response to determining that the reset indicator indicates that the transmitted code blocks associated with the reset indicator are all new transport blocks. The reset indicator may be received at least in part in response to a condition in which a hybrid automatic repeat request (HARQ) process is too complex (e.g., too many round trip HARQ processes). In some embodiments, HARQ processes may be used to reliably communicate data between the eNB 101 and the UE 201. The HARQ process may use a stop-and-wait protocol. For example, the sender may send the code block to the receiver. The sender may stop and wait until it receives an ACK/NACK bit from the receiver.

In some embodiments, the recipient may respond, at least in part, to an acknowledgementThe fixed reset indicator indicates that the transmitted code block associated with the reset indicator may have the retransmitted block(s) and that the ACK/NACK bits transmitted from the receiving side have been correctly received to update the data buffer. The data buffer may include: a New Data Indicator (NDI) field to indicate whether an associated code block is a new code block or a retransmitted code block, and/or a Redundancy Version (RV) field to indicate a channel coding combination of the associated code block. In some embodiments, the NDI field and RV field may be updated based on ACK/NACK bits that have been correctly received. For example, the NDI field may be updated from 1 to 0, or from 0 to 1, in response to the ACK bit. The NDI field may remain unchanged in response to the NACK bit. As another example, the RV field may remain unchanged in response to the ACK bit. In response to the NACK bit, the RV may be included₀、RV₂、RV₁And RV₃The RV field is changed in a cyclic manner. This approach may help eliminate the need for the sender to send NDI and RV parameters to the recipient in an uplink/downlink grant and thus result in shorter Downlink Control Information (DCI).

In some embodiments, code blocks with higher retransmission attempts may be transmitted at earlier OFDM symbols on the condition that the code blocks transmitted from the transmitter to the receiver may include new transport blocks and retransmission blocks. For example, a code block with a second retransmission attempt may be transmitted at an earlier OFDM symbol than a code block with a first retransmission attempt. However, it should be understood that other techniques may implement other embodiments for retransmitting code blocks. For example, a one-to-one mapping of frequency-time resources to code blocks may be applied such that the code blocks may be retransmitted using the same frequency-time resources as used to transmit the code blocks.

Further details of transmission acknowledgement control in the wireless system 100 may be explained below with reference to fig. 2-8.

It should be understood that other technologies may implement other embodiments of the wireless system 100 in fig. 1. In some embodiments, wireless system 100 may use various wireless access technologies in addition to the fifth generation wireless technology, such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and/or other wireless access technologies that are compliant with the Institute of Electrical and Electronics Engineers (IEEE)802 system, third generation project partnership (3GPP) system, 3GPP Long Term Evolution (LTE) system, and/or 3GPP2 system.

Fig. 2 schematically illustrates an example of a TB with transmission acknowledgement control, in accordance with various embodiments. As shown in fig. 2, a TB may include a plurality of code blocks, e.g., code blocks 0-9. In some embodiments, the code blocks may be divided into multiple STBs, e.g., STBs 1-4, where each STB includes one or more code blocks. In some embodiments, a recipient of the wireless system 100 (e.g., UE 201 for downlink transmissions, or eNB 101 for uplink transmissions) may generate STB-level ACK/NACK bits indicating whether STBs were/were not successfully received, where each STB-level ACK/NACK bit may be associated with each STB. In some embodiments, the receiver may also generate a plurality of CB-level ACK/NACK bits indicating whether the code blocks are successfully/unsuccessfully received, where each ACK/NACK bit may be associated with each code block. In other embodiments, the recipient may also generate CB-level ACK/NACK bits that are associated with the code block(s) in the STB(s) determined to have not been successfully received (e.g., the STB(s) associated with the NACK bit (s)), rather than all code blocks including the code block in the STB(s) determined to have been successfully received (e.g., the STB(s) associated with the ACK bit (s)).

In some embodiments, taking the TB as shown in fig. 2 as an example, an ACK/NACK parameter (e.g., parameter N) indicating the number of STB-level ACK/NACK bits for STB successful/unsuccessful reception feedback may be used_ANCK) Was determined to be 4. As another example, an ACK/NACK parameter (e.g., parameter N) may be used to indicate the number of code blocks that one STB-level ACK/NACK bit may bundle across TBs_bund.CB) Was determined to be 3.

Fig. 3 schematically illustrates a method of appending and transmitting Cyclic Redundancy Check (CRC) bits to a transport block by a transmitting party (e.g., evolved node b (enb)) in a wireless system 100, in accordance with various embodiments. As shown in fig. 3, in some embodiments, a transceiver or other device of a sender in the wireless system 100 (e.g., the transceiver 102 of the eNB 101 for downlink transmissions, or the transceiver 202 of the UE 201 for uplink transmissions) may divide a TB into multiple STBs in block 301, each STB comprising one or more code blocks. In block 302, a transceiver or other device of the sender may append one or more STB-level CRC bits to multiple STBs, which may help a receiving party (e.g., UE 201 for downlink transmissions or eNB 101 for uplink transmissions) in the wireless system 100 to detect whether each STB is correctly received.

In some embodiments, in block 303, the sender's transceiver or other device may append one or more CB-level CRC bits to each code block within each STB. However, it should be understood that other embodiments may implement other techniques. For example, the CB-level CRC bits may be omitted so that the receiving side may retransmit the STB(s) that were not successfully received (e.g., the STB(s) associated with the NACK bit (s)), regardless of whether the code block(s) within the STB(s) were successfully received. In block 304, the sender's transceiver or other device may encode a TB with CRC bits including STB level CRC bits and CB level CRC bits. In some embodiments, the CB level CRC bits may be omitted. In block 305, a transceiver or other device of the transmitting party may transmit the encoded TB and CRC bits to the receiving party. In some embodiments, the transceiver may implement other techniques such as rate matching, code block concatenation, and/or others, before transmitting.

Fig. 4 schematically illustrates a method of generating and transmitting acknowledgement/negative acknowledgement (ACK/NACK) bits by a receiving party (e.g., user equipment) in the wireless system 100, in accordance with various embodiments. As shown in fig. 4, in some embodiments, a transceiver or other device of a receiving party in the wireless system 100 (e.g., the transceiver 202 of the UE 201 for downlink transmissions or the transceiver 102 of the eNB 101 for uplink transmissions) may receive an encoded TB and CRC bits from a transmitting party in block 401. In block 402, the transceiver or other device of the receiving party may decode the encoded TB and CRC bits and obtain the TB and CRC bits, where the CRC bits may include: one or more STB-level CRC bits associated with each STB, and one or more CB-level CRC bits associated with each code block within each STB. In some embodiments, the CB level CRC bits may be omitted.

In block 403, the transceiver or other device of the recipient may generate one or more STB-level ACK/NACK bits based at least in part on error detection using the STB-level CRC bits associated with each STB. In some embodiments, each of the STB-level ACK/NACK bits may be associated with each STB, and each STB-level ACK/NACK bit may indicate whether the associated STB was successfully/unsuccessfully received. In block 404, the recipient's transceiver or other device may determine whether any STB-level NACK bits indicating unsuccessful reception with respect to any STB were generated. In block 405, the transceiver or other device of the receiving party may generate one or more CB-level ACK/NACK bits in response to determining that at least one STB-level NACK bit indicating unsuccessful reception of the at least one STB was generated. In some embodiments, CB-level ACK/NACK bits may be generated based at least in part on error detection using CB-level CRC bits associated with each code block within the unsuccessfully received STB, where each CB-level ACK/NACK bit may be associated with each code block and may indicate whether the associated code block was successfully received/unsuccessfully received. In block 406, STB level ACK/NACK bits and CB level ACK/NACK bits may be sent to the sender. In some embodiments, the ACK/NACK bits may be transmitted via a physical ACK/NACK channel or an advanced physical control channel (xPUCCH).

However, in response to determining that the STB-level NACK bit is not generated, the transceiver or other device of the receiving party may not generate a CB-level ACK/NACK bit in block 405 and may transmit the STB-level ACK bit to the transmitting party in block 406.

It should be understood that other embodiments may implement other techniques for the method of fig. 4. For example, more than one STB-level ACK/NACK bit may be generated for each STB, or more than one CB-level ACK/NACK bit may be generated for each code block of an STB that was not successfully received.

Fig. 5 schematically illustrates an example of transmission and retransmission combining in a wireless system 100, in accordance with various embodiments. As shown in fig. 5, in some embodiments, in a first round of transmission, a sender (e.g., eNB 101 for downlink transmission) in the wireless system 100 may send a first TB including a plurality of code blocks to a receiver (e.g., UE 201 for downlink) (S501). For example, as shown in fig. 5, the code block may be represented as

And

wherein

May represent the first code block of the first TB in the first transmission attempt,

may represent the second code block of the first TB in the first transmission attempt,

may represent the third code block of the first TB in the first transmission attempt,

may represent the fourth code block of the first TB in the first transmission attempt.

In some embodiments, the UE 201 may transmit a plurality of ACK/NACK bits to the eNB 101 indicating successful/unsuccessful reception of the code blocks, where each ACK/NACK bit may be associated with each code block (S502). For example, as shown in FIG. 6, ACK ACK NCK NCK may be separately providedRepresenting code blocks in a first round of transmission

And

successful reception and code matching block

And

unsuccessful reception of (2). In response to the ACK/NACK bits, the eNB 101 may transmit a plurality of code blocks in a second round of transmission (S503), wherein the code blocks indicated by the NACK bits as not successfully received are retransmitted to the UE 201. For example, code blocks

And

is retransmitted therein

May represent the third code block of the first TB in the first retransmission attempt,

may represent a fourth code block of the first TB in the first retransmission attempt, wherein a footer ReTx₁A first retransmission attempt may be indicated. In addition, a new code block, e.g. code block, of the second TB

And

may be sent to the UE 201 in a second round of transmission, where

May represent the first code block of the second TB in the first transmission attempt,

may represent a second code block of a second TB in a first transmission attempt. As can be seen from S503, the retransmission code block (e.g.,

and

) And a new transport code block (e.g.,

and

) May be sent together in a second round of transmission, where retransmitted code blocks are sent at earlier OFDM symbols.

In some embodiments, the UE 201 may transmit ACK/NACK bits to the eNB 101 for each code block received in the second round of transmission (S504), where each ACK/NACK bit may be associated with each code block received in the second round of transmission, and each ACK/NACK bit may indicate successful/unsuccessful reception of the relevant code block. For example, NCK ACK NCK ACK may represent code checking blocks

And

unsuccessful reception and code blocks

And

successful reception. In response to the ACK/NACK bits, the eNB 101 may transmit multiple code blocks in a third transmission (S505), where in S504The code blocks indicated by the NACK bits as not successfully received are retransmitted to the UE 201. For example, code blocks

And

can be retransmitted, wherein

May represent the third code block of the first TB in the second retransmission attempt,

may represent the first code block of the second TB in the first retransmission attempt. In addition, a new code block, e.g. code block, of the third TB

And

may be sent to the UE 201 in a third round of transmission, where

May represent the first code block of the third TB in the first transmission attempt,

may represent the second code block of the third TB in the first transmission attempt.

As can be seen from S505, the retransmission code block (e.g.,

and

) And a new transport code block (e.g.,

and

) May be transmitted together in a third round of transmission, where code blocks with higher retransmission attempts are transmitted at earlier OFDM symbols than code blocks with lower retransmission attempts, and retransmission code blocks are transmitted at earlier OFMD symbols than the newly transmitted code blocks. For example, a code block with a second retransmission attempt

Code blocks with more than the first retransmission attempt

Is sent at an earlier OFMD symbol. As another example, retransmission code blocks

And

transport code block that can be newer than others

And

is transmitted at an earlier OFDM symbol.

In some embodiments, the UE 201 may send ACK/NACK bits to the eNB 101 for each code block received in the third round of transmission (S506), where each ACK/NACK bit may be associated with each code block received in the third round of transmission and may indicate successful/unsuccessful reception of the related code block. For example, ACK ACK ACK ACK may represent code checking blocks

And

successful reception.

It should be understood that other embodiments may implement other techniques as the example shown in fig. 5. For example, the ACK/NACK bits may be associated with a STB that includes one or more code blocks across TBs.

Fig. 6 schematically illustrates an example of transmissions and retransmissions under transmission acknowledgement control in a wireless system 100, in accordance with various embodiments. As shown in fig. 6, a transmitting side of the wireless system 100 (e.g., eNB 101 for downlink transmission) may transmit a reset indicator and a plurality of code blocks of a first TB to a receiving side in the wireless system 100 (e.g., UE 201 for downlink transmission (S601)) in a first round of transmission the reset indicator may indicate the transmitted code block (e.g., code block associated with the reset indicator (S601)

And

) Whether all are new transport blocks, wherein a reset indicator 1 may indicate that the code blocks are all new transport blocks and a reset indicator 0 may indicate that at least one of the code blocks is a retransmission block. In some embodiments, a reset indicator representing all new transport blocks may be sent in response to an indication that the HARQ process may be too complex.

In some embodiments, code blocks

In some embodiments, the UE 101 may update the data buffer based at least in part on the reset indicator (S602). The data buffer may also include fields to indicate HARQ status associated with the code blocks, e.g., a New Data Indicator (NDI) field and/or a Redundancy Version (RV) field for each code block. In response to a reset indicator indicating that all code blocks are new transport blocks, the UE 101 may reset the data buffer to an initial state (e.g., all zeros). The receiver may also store the code block in a data buffer. In some embodiments, the UE 201 may transmit one or more ACK/NACK bits to the eNB 101, where each ACK/NACK bit may be associated with each code block received in the first round of transmission and may indicate successful/unsuccessful reception of the associated code block (S603). For example, ACK ACK NCK NCK may represent code checking blocks

And

successful reception and code matching block

And

unsuccessful reception of (2). In some embodiments, a "round of transmission" may represent a transmission of a code block from the eNB 101 to the UE 201 and a transmission of ACK/NACK bits from the UE 201 to the eNB 101 indicating successful/unsuccessful reception of the code block.

In some embodiments, the eNB 101 may determine whether the ACK/NACK bits have been correctly received, and in response to determining that the ACK/NACK bits have been correctly received, transmit a plurality of code blocks to the UE 201 in a second transmission round (e.g.,

and

) And an indicator having a reset indicator and/or an ACK/NACK correct reception indicator (S604). Code blocks may be generated based at least in part on correctly received ACK/NACK bits. For example, the code block associated with the NACK bit (e.g.,

and

) It is possible to transmit code blocks more than the new transmission code block (e.g.,

and

) Is sent in an earlier OFMD symbol, wherein

may represent the fourth code block of the first TB in the first retransmission attempt,

may represent a second code block of a second TB in a first transmission attempt.

The ACK/NACK correct reception indicator may indicate whether the ACK/NACK bit has been correctly received. For example, an ACK/NACK correct reception indicator '1' may indicate that ACK/NACK bits are correctly received, andand an ACK/NACK correct reception indicator "0" may indicate that the ACK/NACK is not correctly received, and vice versa. If the code blocks in the second round of transmission may include code blocks retransmitted in response to the NACK bits (e.g., code blocks)

And

) And the ACK/NACK bit has been correctly received, the eNB 101 may transmit a reset indicator "0" and an ACK/NACK correct reception indicator "1" to the UE 201 in S604.

In some embodiments, the UE 201 may update the data buffer based at least in part on the reset indicator and/or the ACK/NACK correct reception indicator and store the code block received in the second round of transmission in the data buffer (S605). In response to the reset indicator indicating that at least one code block is a retransmission block and the ACK/NACK bits have been correctly received, the UE 201 may update the data buffer to reflect the HARQ status (e.g., the NDI and/or RV fields) of the code blocks received in the second round of transmission. E.g. for code blocks

The NDI field of (i.e., the third code block of the first TB in the first retransmission attempt) may remain unchanged, while the associated RV field may be moved from the RV₀Update to RV₁. For code blocks

The NDI field of (i.e., the fourth code block of the first TB in the first retransmission attempt) may remain unchanged, while the associated RV field may be moved from the RV₀Update to RV₁. For code blocks

The NDI field of (i.e., the first code block of the second TB in the first round of transmission) may remain unchanged, while the associated RV field may be updated to RV₀. For code blocks

The NDI field of (i.e., the second code block of the second TB in the first round of transmission) may remain unchanged, while the associated RV field may be updated to RV₀。

In some embodiments, the UE 201 may transmit one or more ACK/NACK bits to the eNB 101, where each ACK/NACK bit may be associated with each code block received in the second round of transmission and may indicate successful/unsuccessful reception of the associated code block (S606). For example, NCK ACK ACK ACK may represent code checking blocks

Unsuccessful reception and code blocks

And

successful reception.

In some embodiments, the eNB 101 may determine whether the ACK/NACK bits have been correctly received and, in response to determining that the ACK/NACK bits have been correctly received, send the code block in the third round of transmission to the UE 201 (e.g.,

and

) And an indicator having a reset indicator and/or an ACK/NACK correct reception indicator (S607). Code blocks may be generated based at least in part on correctly received ACK/NACK bits. For example, the code block associated with the NACK bit (e.g.,

and

) Is sent in an earlier OFMD symbol, wherein

may represent a second code block of a third TB in a first transmission attempt, and

may represent a third code block of a third TB in the first transmission attempt.

Further, if the code blocks in the third round of transmission may include code blocks retransmitted in response to the NACK bits (e.g., code blocks)

) And the ACK/NACK bit has been correctly received, the eNB 101 may transmit a reset indicator 0 and an ACK/NACK correct reception indicator 1 to the UE 201 in S607.

In some embodiments, the UE 201 may update the data buffer based at least in part on the reset indicator and/or the ACK/NACK correct reception indicator and store the code block received in the third round of transmission in the data buffer (S608). In response to the reset indicator indicating that the at least one code block is a retransmitted block and the ACK/NACK bits have been correctly received, the UE 201 may update the data buffer to reflect the HARQ status (e.g., the NDI and/or RV fields) of the code blocks received in the third round of transmission. E.g. for code blocks

NDI field of (i.e. third code block of first TB in second retransmission attempt)May remain unchanged and the associated RV field may be derived from the RV₁Update to RV₂. For code blocks

The NDI field of (i.e., the first code block of the third TB in the first transmission attempt) may remain unchanged, while the associated RV field may be updated to RV₀. For code blocks

The NDI field of (i.e., the second code block of the third TB in the first round of transmission) may remain unchanged, while the associated RV field may be updated to RV₀. For code blocks

The NDI field of (i.e., the third code block of the third TB in the first round of transmission) may remain unchanged, while the associated RV field may be updated to RV₀。

In some embodiments, the UE 201 may transmit one or more ACK/NACK bits to the eNB 101, where each ACK/NACK bit may be associated with each code block received in the third round of transmission and indicate successful/unsuccessful reception of the associated code block (S608). For example, ACK ACK ACK ACK may indicate successful reception of a code block

And

in some embodiments, the eNB 101 may determine whether the ACK/NACK bits have been correctly received and, in response to determining that the ACK/NACK bits have not been correctly received, send the code block in the fourth transmission to the UE 201 (e.g.,

and

) To be provided withAnd an indicator having a reset indicator and/or an ACK/NACK correct reception indicator (S609). The eNB 101 may also transmit an indicator with a reset indicator and/or an ACK/NACK correct reception indicator to the UE 201 (S610). Since the ACK/NACK bits have not been received correctly, the eNB 101 may retransmit the code blocks associated with the code blocks in the previous transmission round. In other words, the code blocks in the fourth round of transmission are the same as the code blocks in the third round of transmission.

Further, if the ACK/NACK bits are not correctly received and the code blocks in the fourth transmission may include those code blocks retransmitted in response to the ACK/NACK not being correctly received, the eNB 101 may transmit a reset indicator 0 and an ACK/NACK correct reception indicator 0 to the UE 201 in S610.

In some embodiments, in response to the reset indicator indicating that the code block includes a retransmission block and the ACK/NACK correct reception indicator indicating that the ACK/NACK bits are not correctly received, the UE 201 may keep the data buffer unchanged, including the HARQ status and the data block (S611).

Fig. 7 schematically illustrates a method of transmission and retransmission under control of transmission acknowledgements employed by a receiver in the wireless system 100, in accordance with various embodiments. As shown in fig. 7, in some embodiments, in block 701, a receiving side (e.g., UE 201 for a downlink transmission) may receive a plurality of code blocks and indicators from a transmitting side (e.g., eNB 101 for a downlink transmission). The indicator may indicate a reset indicator and/or an ACK/NACK correct reception indicator. The reset indicator may indicate whether the associated code blocks are all new transport blocks or whether at least one of them is a retransmission block. In the case of a complex HARQ state, the reset indicator may indicate that the associated code blocks (e.g., the code blocks received in block 701) are all new transport blocks. The ACK/NACK correct reception indicator may indicate whether the eNB 101 has correctly received the ACK/NACK bit transmitted by the UE 201. In some embodiments, each ACK/NACK bit may be associated with at least one code block and indicate whether the associated code block is successfully/unsuccessfully received. The ACK/NACK correct reception indicator may be omitted if the reset indicator indicates that the associated code block is a new transport block. In other words, the indicator may comprise a reset indicator.

In the case where the code block may include a new transport block and/or a retransmission block, the retransmission block may be transmitted at an earlier OFDM symbol than the new transport block. Further, code blocks with higher retransmission attempts may be transmitted at earlier OFDM symbols than code blocks with lower retransmission attempts.

In block 702, the UE 201 may determine whether the reset indicator indicates that the associated code block is a new transport block. In response to determining that the reset indicator indicates that the associated code block is a new transport block, the UE 201 may reset a data buffer storing HARQ states for the code block to an initial state in block 703. In some embodiments, the data buffer may include a field indicating the HARQ status, such as a New Data Indicator (NDI) field and/or a Redundancy Version (RV) field for each code block. The receiver may also store the code block in a data buffer.

In block 704, the UE 201 may generate ACK/NACK bits based at least in part on error checking of the code block. In some embodiments, each ACK/NACK bit may be associated with at least one code block and may indicate whether the associated code block is successfully/unsuccessfully received. In block 705, the UE 201 may send ACK/NACK bits to the eNB 101.

In some embodiments, in response to determining in block 702 that not all code blocks are new transport blocks, the UE 201 may also determine whether the ACK/NACK correct receipt indicator received from the eNB 101 indicates that the ACK/NACK bits in the previous transmission round have been correctly received (block 706). In response to determining that the ACK/NACK bits have been correctly received in block 707, the UE 201 may update a data buffer for HARQ states associated with the code block based at least in part on the ACK/NACK bits sent in the previous transmission round (e.g., the ACK/NACK bits generated in block 704). For example, the NDI field for the code block determined to be NACK in the previous transmission roundThe RV field of the code block may remain unchanged and may be removed from the RV in response to a first retransmission attempt₀Update to RV₁Updated to RV in response to the second retransmission attempt₂And so on. For another example, the NDI field of a code block determined to be ACK in a previous transmission may be changed from 1 to 0 or from 0 to 1, and the RV field of the code block may remain unchanged or remain zero. For another example, the NDI field and RV field for a new transmission code block may be reset to an initial state, e.g., all zeros. The method may then again pass to block 704 to generate ACK/NACK bits for the code block received in block 701, and transmit the ACK/NACK bits to the eNB 101 in block 705.

In some embodiments, in response to determining in block 706 that the ACK/NACK correct reception indicator indicates that the ACK/NACK bits have not been correctly received, in block 708, the UE 101 may retransmit the ACK/NACK bits in the previous transmission round to the eNB 101.

Fig. 8 schematically illustrates a method of transmission and retransmission under control of transmission acknowledgements employed by a sender in a wireless system 100, in accordance with various embodiments. As shown in fig. 8, in some embodiments, in block 801, a sender of a wireless system 100 (e.g., eNB 101 for a downlink transmission) may send a plurality of start code blocks and start indicators to a receiver of the wireless system 100 (e.g., UE 201 for a downlink transmission). In some embodiments, the eNB 101 may receive ACK/NACK bits associated with the starting code block from the UE 201 in block 802, where each ACK/NACK bit may be associated with each starting code block and may indicate successful/unsuccessful reception of the associated code block. However, it should be understood that other embodiments may implement other techniques as illustrated by block 802 of FIG. 8. For example, the ACK/NACK bits may be associated with more than one code block on a transport block.

In some embodiments, the eNB 101 may determine whether the ACK/NACK bit has been correctly received in block 803. In response to determining that the ACK/NACK bits have been correctly received, the eNB 101 may transmit a subsequent indicator and a plurality of subsequent code blocks to the UE 201 in block 804. The subsequent indicator may include a subsequent reset indicator and/or a subsequent ACK/NACK correct receipt indicator. A subsequent code block is generated based at least in part on the ACK/NACK bits received in block 802, wherein the code block associated with the NACK indicating unsuccessful reception may be retransmitted. In the event that the subsequent code blocks may include new transmission code blocks and/or retransmission code blocks, the retransmission blocks may be transmitted at earlier OFDM symbols than the new transmission blocks. Further, code blocks with higher retransmission attempts may be transmitted at earlier OFDM symbols than code blocks with lower retransmission attempts.

In some embodiments, in response to determining in block 803 that the ACK/NACK bits have not been correctly received, the eNB 101 may transmit in block 805 another plurality of subsequent code blocks and another subsequent indicator to the UE 201. The additional plurality of code blocks may be the same as the code block with which the ACK/NACK bits are associated (e.g., the code block sent in block 801). The another subsequent indicator may include another subsequent reset indicator and another subsequent ACK/NACK correct reception indicator, wherein the another subsequent reset indicator may indicate that the another plurality of subsequent code blocks are retransmission blocks, and the ACK/NACK correct reception indicator may indicate that the ACK/NACK bits are not correctly received.

Fig. 9 schematically illustrates an example system 900 in accordance with various embodiments. In one embodiment, the system 900 may include one or more processors 904, system control logic 908 coupled with at least one of the processor(s) 904, system memory 912 coupled with the system control logic 908, non-volatile memory (NVM)/storage 916 coupled with the system control logic 908, and a network interface 920 coupled with the system control logic 908.

Processor(s) 904 may include one or more single-core or multi-core processors. The processor(s) 904 can include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In embodiments in which system 900 implements eNB 101, processor(s) 904 may be configured to perform one or more of the embodiments as shown in fig. 1-3, 5-6, and 8, in accordance with various embodiments. In an embodiment in which system 900 implements UE 201, processor(s) 904 may be configured to perform one or more embodiments as shown in fig. 1-2 and 4-7 in accordance with various embodiments.

System control logic 908 for one embodiment may include any suitable interface controllers to provide any suitable interface to at least one of the processor(s) 904 and/or to any suitable device or component in communication with system control logic 908.

System control logic 908 for one embodiment may include one or more memory controllers to provide an interface to system memory 912. System memory 912 may be used to load and store data and/or instructions, for example, for system 900. Memory 912 for one embodiment may comprise any suitable volatile memory, such as suitable Dynamic Random Access Memory (DRAM), for example.

For example, NVM/storage 916 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. NVM/storage 916 may include any suitable non-volatile memory, such as flash memory, and/or NVM/storage 916 may include any suitable non-volatile storage device(s), such as one or more Hard Disk Drives (HDDs), one or more Compact Disk (CD) drives, and/or one or more Digital Versatile Disk (DVD) drives.

NVM/storage 916 may include a storage resource that is physically part of a device in which system 900 is installed, or it may be accessible by, but not necessarily part of, the device. For example, the NVM/storage 916 may be accessed over a network via the network interface 920.

In particular, system memory 912 and NVM/storage 916 may include temporary and persistent copies of instructions 924, respectively. The instructions 924 may include instructions that, when executed by at least one of the processor(s) 904, cause the system 900 to implement the methods described with reference to fig. 3-8. In various embodiments, the instructions 924 or hardware, firmware, and/or software components thereof may additionally/alternatively be located in the system control logic 908, the network interface 920, and/or the processor(s) 904.

The network interface 920 may include the transceiver 102 of the eNB 101 or the transceiver 202 of the UE 201 and/or other components as shown in fig. 1 to provide a radio interface for the system 900 to communicate over one or more networks and/or with any other suitable devices. In various embodiments, network interface 920 may be integrated with other components of system 900. For example, the network interface may include a processor in the processor(s) 904, a memory in the system memory 912, a NVM/storage in the NVM/storage 916, and/or a firmware device (not shown) having instructions that, when executed by at least one of the processor(s) 904, cause the system 900 to implement the method as described with reference to fig. 3-8.

Network interface 920 may also include any suitable hardware and/or firmware to provide a multiple-input multiple-output radio interface. Network interface 920 for one embodiment may be, for example, a network adapter, a wireless network adapter, a telephone modem, and/or a wireless modem.

For one embodiment, at least one of the processor(s) 904 may be packaged together with logic for one or more controller(s) of system control logic 908. For one embodiment, at least one of the processor(s) 904 may be packaged together with logic for one or more controller(s) in system control logic 908 to form a System In Package (SiP). For one embodiment, at least one of the processor(s) 904 may be integrated on the same die with logic for one or more controller(s) of system control logic 908. For one embodiment, at least one of the processor(s) 904 may be integrated on the same die with logic for one or more controller(s) of system control logic 908 to form a system on a chip (SoC).

The system 900 may also include input/output (I/O) devices 932. The I/O devices 932 may include: a user interface designed to enable a user to interact with the system 900; a peripheral component interface designed to enable peripheral components to interact with the system 900; and/or sensors designed to determine environmental conditions and/or location information associated with system 900.

In various embodiments, the user interface may include, but is not limited to, a display (e.g., a liquid crystal display, a touch screen display, etc.), a speaker, a microphone, one or more cameras (e.g., still and/or video cameras), a flash (e.g., a light emitting diode flash), and a keyboard.

In various embodiments, the peripheral component interfaces may include, but are not limited to, a non-volatile memory port, an audio jack, and a power interface.

In various embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of the network interface 920 or interact with the network interface 920 to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

In various embodiments, system 900 may be an eNB, such as eNB 101. In various embodiments, system 900 may have more or fewer components, and/or have a different architecture.

Fig. 10 illustrates example components of a UE device 1000 for one embodiment, in accordance with some embodiments. In some embodiments, the UE device 1000 may include application circuitry 1002, baseband circuitry 1004, Radio Frequency (RF) circuitry 1006, Front End Module (FEM) circuitry 1008, and one or more antennas 1010 coupled together at least as shown. In some embodiments, the UE device 1000 may include additional elements, such as memory/storage, a display, a camera, sensors, and/or input/output (I/O) interfaces.

The application circuitry 1002 may include one or more application processors. For example, the application circuitry 1002 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

Baseband circuitry 1004 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 1004 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of RF circuitry 1006 and to generate baseband signals for a transmit signal path of RF circuitry 1006. Baseband processing circuitry 1004 may interface with application circuitry 1002 for the generation and processing of baseband signals and control the operation of RF circuitry 1006. For example, in some embodiments, the baseband circuitry 1004 may include a second generation (2G) baseband processor 1004a, a third (3G) baseband processor 1004b, a fourth generation (4G) baseband processor 1004c, and/or other baseband processor(s) 1004d for other existing generations, generations in development, or generations to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 1004 (e.g., one or more of the baseband processors 1004 a-d) may process various radio control functions that enable communication with one or more radio networks via the RF circuitry 1006. The radio control functions may include, but are not limited to: signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, the modulation/demodulation circuitry of baseband circuitry 1004 may include Fast Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuitry of baseband circuitry 1004 may include convolution, tail-biting convolution, turbo, Viterbi (Viterbi), and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, the baseband circuitry 1004 may include elements of a protocol stack, e.g., elements of an Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, including, for example, Physical (PHY) elements, Medium Access Control (MAC) elements, Radio Link Control (RLC) elements, Packet Data Convergence Protocol (PDCP) elements, and/or Radio Resource Control (RRC) elements. A Central Processing Unit (CPU)1004e of the baseband circuitry 1004 may be configured to run elements of a protocol stack for signaling of the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio Digital Signal Processors (DSPs) 1004 f. The audio DSP(s) 1004f may be or include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, components of the baseband circuitry may be combined in a single chip or a single chipset, or arranged on the same circuit board, as appropriate. In some embodiments, some or all of the constituent components of the baseband circuitry 1004 and the application circuitry 1002 may be implemented together, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 1004 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 1004 may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), Wireless Personal Area Networks (WPANs). Embodiments in which the baseband circuitry 1004 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

The RF circuitry 1006 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1006 may include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. The RF circuitry 1006 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 1008 and provide baseband signals to the baseband circuitry 1004. RF circuitry 1006 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by baseband circuitry 1004 and provide RF output signals to FEM circuitry 1008 for transmission.

In some embodiments, the RF circuitry 1006 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1006 may include a mixer circuit 1006a, an amplifier circuit 1006b, and a filter circuit 1006 c. The transmit signal path of the RF circuitry 1006 may include filter circuitry 1006c and mixer circuitry 1006 a. The RF circuitry 1006 may also include a synthesizer circuit 1006d for synthesizing frequencies for use by the mixer circuits 1006a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1006a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1008 based on a synthesized frequency provided by the synthesizer circuit 1006 d. The amplifier circuit 1006b may be configured to amplify the downconverted signal, and the filter circuit 1006c may be a Low Pass Filter (LPF) or a Band Pass Filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 1004 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not a requirement. In some embodiments, mixer circuit 1006a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1006a of the transmit signal path may be configured to upconvert the input baseband signal based on a synthesis frequency provided by the synthesizer circuitry 1006d to generate an RF output signal for the FEM circuitry 1008. The baseband signal may be provided by baseband circuitry 1004 and may be filtered by filter circuitry 1006 c. The filter circuit 1006c may include a Low Pass Filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, mixer circuit 1006a of the receive signal path and mixer circuit 1006a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and/or quadrature up-conversion, respectively. In some embodiments, the mixer circuit 1006a of the receive signal path and the mixer circuit 1006a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley (Hartley) image rejection). In some embodiments, mixer circuit 1006a of the receive signal path and mixer circuit 1006a of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, mixer circuit 1006a of the receive signal path and mixer circuit 1006a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuitry 1006 may include analog-to-digital converter (ADC) circuitry and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 1004 may include a digital baseband interface to communicate with the RF circuitry 1006.

In some dual-mode embodiments, separate radio IC circuitry may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, synthesizer circuit 1006d may be a fractional-N synthesizer or a fractional-N/N +1 synthesizer, although the scope of embodiments is not limited in this respect as other types of frequency synthesizers may be appropriate. For example, synthesizer circuit 1006d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

The synthesizer circuit 1006d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 1006a of the RF circuit 1006. In some embodiments, the synthesizer circuit 1006d may be a fractional N/N +1 synthesizer.

In some embodiments, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuitry 1004 or the application processor 1002 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application processor 1002.

The synthesizer circuit 1006d of the RF circuit 1006 may include a frequency divider, a Delay Locked Loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual-mode divider (DMD) and the phase accumulator may be a Digital Phase Accumulator (DPA). In some embodiments, the DMD may be configured to divide an input signal by N or N +1 (e.g., carry out based) to provide a fractional division ratio. In some example embodiments, a DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to decompose the VCO period into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this manner, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuit 1006d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with the quadrature generator and divider circuit to generate multiple signals at the carrier frequency having multiple phases that are different from each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuitry 1006 may include an IQ/polarity converter.

FEM circuitry 1008 may include a receive signal path that may include circuitry configured to operate on received RF signals from one or more antennas 1010, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 1006 for further processing. The FEM circuitry 1008 may also include a transmit signal path that may include circuitry configured to amplify signals provided by the RF circuitry 1006 for transmission by one or more of the one or more antennas 1010.

In some embodiments, the FEM circuitry 1008 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a Low Noise Amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 1006). The transmit signal path of the FEM circuitry 1008 may include a Power Amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 1006) and may include one or more filters to generate an RF signal for subsequent transmission (e.g., by one or more of the one or more antennas 1010).

In some embodiments, the UE 1000 includes multiple power saving mechanisms. If the UE 1000 is in RRC _ Connected state (in which the UE 1000 is still Connected to the eNB because it expects to receive traffic very fast), it may enter a state called discontinuous reception mode (DRX) after a period of inactivity. During this state, the device may be powered down for a brief interval of time, thereby saving power.

If there is no data traffic activity for an extended period of time, the UE 1000 may transition to the RRC _ Idle state, in which the UE 1000 disconnects from the network and does not perform operations such as channel quality feedback, handover, and the like. The UE 1000 enters a very low power state, which performs paging, where the UE 1000 wakes up periodically to listen to the network and then powers down again. The device cannot receive data in this state and in order to receive data it must transition back to the RRC _ Connected state.

The additional power-save mode may allow the device to be unavailable to the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device is completely inaccessible to the network and may be completely powered down. Any data transmitted during this period will incur a significant delay and the delay is assumed to be acceptable.

The present disclosure may include various example embodiments disclosed below.

Example 1 may include a base station, which may include: a control module to: dividing a Transport Block (TB) into one or more sub-transport blocks (STBs) based at least in part on an acknowledgement/negative acknowledgement (ACK/NACK) parameter, wherein a STB of the STBs may include one or more code blocks of the TB; and appending one or more first level Cyclic Redundancy Check (CRC) bits to each of the STBs; and a transceiver for transmitting the TB with the first level CRC bits to a User Equipment (UE).

Example 2 may include the subject matter of example 1, and optionally, wherein the control module is further to append one or more second level CRC bits to each of the code blocks; and the transceiver is further configured to transmit the second level CRC bits to the UE.

Example 3 may include the subject matter of any of examples 1-2, and optionally, wherein the ACK/NACK parameter may indicate a number of ACK/NACK bits for successful/unsuccessful reception of feedback by the STB from the UE.

Example 4 may include the subject matter of any of examples 1-3, and optionally, wherein the ACK/NACK parameter may indicate a number of code blocks associated with ACK/NACK bits for successful/unsuccessful reception of feedback by the STB from the UE.

Example 5 may include the subject matter of any of examples 1-4, and optionally, wherein the base station may be an evolved node b (enb).

Example 6 may include a User Equipment (UE), comprising: a transceiver for receiving a Transport Block (TB) and one or more first level Cyclic Redundancy Check (CRC) bits from a base station, wherein the TB includes one or more sub-transport blocks (STBs), and a STB of the STBs includes one or more code blocks of the TB; and a control module to: one or more first level ACK/NACK bits are generated based at least in part on the first level CRC bits associated with the STB, wherein the transceiver is further operable to transmit the first level ACK/NACK bits to the base station.

Example 7 may include the subject matter of example 6, and optionally, wherein the transceiver may receive one or more second level CRC bits from the base station, wherein the second level CRC bits are associated with the code block.

Example 8 may include the subject matter of any one of examples 6-7, and optionally, wherein the control module is further to: determining that at least one first level NACK bit is generated to indicate unsuccessful reception by at least one of the STBs; generating one or more second level ACK/NACK bits based at least in part on second level CRC bits associated with code blocks within the at least one STB; and wherein the transceiver further transmits the second level ACK/NACK bits to the base station.

Example 9 may include the subject matter of any one of examples 6-8, and optionally, wherein the number of STBs may be determined based at least in part on an acknowledgement/negative acknowledgement (ACK/NACK) parameter.

Example 10 may include the subject matter of any of examples 6-9, and optionally, wherein the ACK/NACK parameter may indicate a number of first level ACK/NACK bits for successful/unsuccessful reception feedback from the STB of the recipient.

Example 11 may include the subject matter of any one of examples 6-10, and optionally, wherein the ACK/NACK parameter may indicate a number of code blocks associated with first-level ACK/NACK bits of the first-level ACK/NACK bits.

Example 12 may include the subject matter of any one of examples 6-11, and optionally, wherein the base station may be an evolved node b (enb).

Example 13 may include a User Equipment (UE), comprising: a transceiver for receiving a plurality of code blocks and an indicator from a base station; and a control module to: resetting a data buffer associated with the code block to an initial state at least partially in response to determining that the indicator indicates that the code block is a new transport block; and updating the data buffer at least in part in response to determining that the indicator indicates that at least one of the code blocks is a retransmission block and that one or more previous acknowledgement/negative acknowledgement (ACK/NACK) bits associated with a plurality of previous code blocks have been correctly received by the base station.

Example 14 may include the subject matter of example 13, and optionally, wherein the control module may generate one or more ACK/NACK bits indicating whether the code block was successfully/unsuccessfully received; and the transceiver is also used to transmit the ACK/NACK bits to the base station.

Example 15 may include the subject matter of any of examples 13-14, and optionally, wherein the control module may hold the data buffer unchanged at least in part in response to determining that the indicator indicates that at least one of the code blocks is a retransmission block and that previous ACK/NACK bits associated with the previous code block were not correctly received by the base station.

Example 16 may include the subject matter of any one of examples 13-15, and optionally, wherein the code block may be identical to the previous code block if the indicator indicates that the previous ACK/NACK bits were not correctly received by the base station.

Example 17 may include the subject matter of any of examples 13-16, and optionally, wherein code blocks with higher retransmission attempts of the code blocks according to any of examples 13-16 may be received at earlier Orthogonal Frequency Division Multiplexing (OFDM) symbols.

Example 18 may include the subject matter of any one of examples 13-17, and optionally, wherein the data buffer comprises a one-bit New Data Indicator (NDI) field to indicate whether a code block of the code blocks is a new code block or a retransmitted code block.

Example 19 may include the subject matter of any one of examples 13-18, and optionally, wherein the data buffer comprises a one-bit Redundancy Version (RV) field to indicate a channel coding combination of the code blocks in the code block.

Example 20 may include the subject matter of any one of examples 13-19, and optionally, wherein the indicator comprises a reset indicator to indicate whether the code block is a new transport block.

Example 21 may include the subject matter of any one of examples 13-20, and optionally, wherein the indicator comprises an ACK/NACK correct receipt indicator to indicate whether the ACK/NACK bit has been correctly received by the base station.

Example 22 may include the subject matter of any one of examples 13-18, and optionally, wherein the base station is an evolved node b (enb).

Example 23 may include a base station comprising: a transceiver to: transmitting a plurality of first code blocks and a first indicator to a User Equipment (UE), wherein the first indicator is further for indicating whether the first code block is a new transport block; and receiving one or more acknowledgement/negative acknowledgement (ACK/NACK) bits from the UE, the one or more ACK/NACK bits indicating whether the first code block has been successfully received by the UE; and a control module for generating a second indicator to indicate whether the ACK/NACK bits have been correctly received by the base station.

Example 24 may include the subject matter of example 23, and optionally, wherein the control module may further generate the plurality of second code blocks at least in part in response to determining that the ACK/NACK has been successfully received by the base station; and the transceiver is further configured to transmit the second code block to the UE.

Example 25 may include the subject matter of any of examples 23-24, and optionally, wherein the second indicator is further to indicate whether at least one of the second code blocks is a retransmission block.

Example 26 may include the subject matter of any of examples 23-25, and optionally, wherein the code block of the first code block with the higher retransmission attempt is transmitted at an earlier Orthogonal Frequency Division Multiplexing (OFDM) symbol.

Example 27 may include the subject matter of any of examples 23-26, and optionally, wherein the transceiver is further to retransmit the first code block at least in part in response to determining that the second indicator indicates that the ACK/NACK bits were not successfully received by the base station.

Example 28 may include the subject matter of any of examples 23-27, and optionally, wherein the first indicator indicating that the first code block is a new transport block is transmitted at least in part in response to determining that a hybrid automatic repeat request (HARQ) process is too complex.

Example 29 may include the subject matter of any one of examples 23-28, and optionally, wherein the base station is an evolved node b (enb).

Example 30 may include a method for use by a base station, comprising: dividing a Transport Block (TB) into one or more sub-transport blocks (STBs) based at least in part on an acknowledgement/negative acknowledgement (ACK/NACK) parameter, wherein a STB of the STBs may include one or more code blocks of the TB; appending one or more first level Cyclic Redundancy Check (CRC) bits to each of the STBs; and transmitting the TB with the first level CRC bits to a User Equipment (UE).

Example 31 may include the subject matter of example 30, and optionally, further comprising: appending one or more second level CRC bits to each of the code blocks; and transmitting the second level CRC bits to the UE.

Example 32 may include the subject matter of any one of examples 30-31, and optionally, wherein the ACK/NACK parameter indicates a number of ACK/NACK bits for successful/unsuccessful reception feedback of the STB from the UE.

Example 33 may include the subject matter of any of examples 30-32, and optionally, wherein the ACK/NACK parameter indicates a number of code blocks associated with ACK/NACK bits for successful/unsuccessful reception of feedback by the STB from the UE.

Example 34 may include the subject matter of any one of examples 30-33, and optionally, wherein the base station is an evolved node b (enb).

Example 35 may include a method for use by a User Equipment (UE), comprising: receiving a Transport Block (TB) and one or more first-level Cyclic Redundancy Check (CRC) bits from a base station, wherein the TB includes one or more sub-transport blocks (STBs), and a STB of the STBs includes one or more code blocks of the TB; generating one or more first level ACK/NACK bits based, at least in part, on first level CRC bits associated with the STB; and transmitting the first stage ACK/NACK bit to the base station.

Example 36 may include the subject matter of example 35, and optionally, further comprising: one or more second level CRC bits are received from the base station, wherein the second level CRC bits are associated with the code block.

Example 37 may include the subject matter of any one of examples 35-36, and optionally, further comprising: determining that at least one first level NACK bit is generated to indicate unsuccessful reception by at least one of the STBs; generating one or more second level ACK/NACK bits based at least in part on second level CRC bits associated with code blocks within the at least one STB; and transmitting the second level ACK/NACK bit to the base station.

Example 38 may include the subject matter of any one of examples 35-37, and optionally, wherein the number of STBs is determined based at least in part on an acknowledgement/negative acknowledgement (ACK/NACK) parameter.

Example 39 may include the subject matter of any one of examples 35-38, and optionally, wherein the ACK/NACK parameter indicates a number of first stage ACK/NACK bits for successful/unsuccessful reception feedback from the STB of the recipient.

Example 40 may include the subject matter of any one of examples 35-39, and optionally, wherein the ACK/NACK parameter indicates a number of code blocks associated with first-level ACK/NACK bits of the first-level ACK/NACK bits.

Example 41 may include the subject matter of any one of examples 35-40, and optionally, wherein the base station is an evolved node b (enb).

Example 42 may include a method for use by a User Equipment (UE), comprising: receiving a plurality of code blocks and an indicator from a base station; resetting a data buffer associated with the code block to an initial state at least partially in response to determining that the indicator indicates that the code block is a new transport block; and updating the data buffer at least in part in response to determining that the indicator indicates that at least one of the code blocks is a retransmission block and that one or more previous acknowledgement/negative acknowledgement (ACK/NACK) bits associated with a plurality of previous code blocks have been correctly received by the base station.

Example 43 may include the subject matter of example 42, and optionally, further comprising: generating one or more ACK/NACK bits indicating whether the code block is successfully received/unsuccessfully received; and transmitting the ACK/NACK bit to the base station.

Example 44 may include the subject matter of any one of examples 42-43, and optionally, further comprising: the data buffer is maintained, at least in part, in response to determining that the indicator indicates that at least one of the code blocks is a retransmission block and that previous ACK/NACK bits associated with the previous code block were not correctly received by the base station.

Example 45 may include the subject matter of any one of examples 42-44, and optionally, wherein the code block is identical to the previous code block if the indicator indicates that the previous ACK/NACK bits were not correctly received by the base station.

Example 46 may include the subject matter of any of examples 42-45, and optionally, wherein code blocks with higher retransmission attempts of the code blocks may be received at earlier Orthogonal Frequency Division Multiplexing (OFDM) symbols.

Example 47 may include the subject matter of any one of examples 42-46, and optionally, wherein the data buffer comprises a one-bit New Data Indicator (NDI) field to indicate whether a code block of the code blocks is a new code block or a retransmitted code block.

Example 48 may include the subject matter of any one of examples 42-47, and optionally, wherein the data buffer comprises a one-bit Redundancy Version (RV) field to indicate a channel coding combination of the code blocks in the code block.

Example 49 may include the subject matter of any one of examples 42-48, and optionally, wherein the indicator comprises a reset indicator to indicate whether the code block is a new transport block.

Example 50 may include the subject matter of any one of examples 42-49, and optionally, wherein the indicator comprises an ACK/NACK correct receipt indicator to indicate whether the ACK/NACK bit has been correctly received by the base station.

Example 51 may include the subject matter of any one of examples 42-50, and optionally, the base station is an evolved node b (enb).

Example 52 may include a method for use by a base station, comprising: transmitting a plurality of first code blocks and a first indicator to a User Equipment (UE), wherein the first indicator is further for indicating whether the first code block is a new transport block; receiving one or more acknowledgement/negative acknowledgement (ACK/NACK) bits from the UE, the one or more ACK/NACK bits indicating whether the first code block has been successfully received by the UE; and generating a second indicator to indicate whether the ACK/NACK bit has been correctly received by the base station.

Example 53 may include the subject matter of example 52, and optionally, further comprising: generating a plurality of second code blocks at least partially in response to determining that the ACK/NACK has been successfully received by the base station; and transmitting the second code block to the UE.

Example 54 may include the subject matter of any of examples 52-53, and optionally, wherein the second indicator is further to indicate whether at least one of the second code blocks is a retransmission block.

Example 55 may include the subject matter of any of examples 52-54, and optionally, wherein the code block of the first code block with the higher retransmission attempt is transmitted at an earlier Orthogonal Frequency Division Multiplexing (OFDM) symbol.

Example 56 may include the subject matter of any one of examples 52-55, and optionally, further comprising: retransmitting the first code block at least in part in response to determining that the second indicator indicates that the ACK/NACK bits were not successfully received by the base station.

Example 57 may include the subject matter of any of examples 52-56, and optionally, wherein the first indicator indicating that the first code block is a new transport block is transmitted at least in part in response to determining that a hybrid automatic repeat request (HARQ) process is too complex.

Example 58 may include the subject matter of any one of examples 52-57, and optionally, wherein the base station is an evolved node b (enb).

Example 59 may include a computer-readable storage medium storing instructions for execution by a processor to perform operations of a UE or a base station, the instructions when executed by the processor to perform any of the operations described above in any combination.

Example 60 may include an apparatus for a UE or a base station, comprising means for performing any of the operations described above in any combination.

Although certain embodiments have been illustrated and described herein for purposes of description, various alternative and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly understood that the embodiments described herein are limited only by the claims and the equivalents thereof.

Claims

1. A User Equipment (UE), comprising:

a transceiver for receiving a plurality of code blocks and an indicator from a base station; and

a control module to:

resetting a data buffer associated with the code block to an initial state, at least in part in response to determining that the indicator indicates that the code block is a new transport block; and

updating the data buffer at least in part in response to determining that the indicator indicates that at least one of the code blocks is a retransmission block and that one or more previous acknowledgement/negative acknowledgement (ACK/NACK) bits associated with a plurality of previous code blocks have been correctly received by the base station.

2. The UE of claim 1, wherein the control module is further to generate one or more ACK/NACK bits indicating whether the code block was successfully/unsuccessfully received; and the transceiver is further configured to transmit the ACK/NACK bits to the base station.

3. The UE of claim 1 or 2, wherein the control module is further to: maintaining the data buffer unchanged at least in part in response to determining that the indicator indicates that at least one of the code blocks is a retransmission block and that previous ACK/NACK bits associated with the previous code block were not correctly received by the base station.

4. The UE of claim 3, wherein the code block is the same as the previous code block if the indicator indicates that the previous ACK/NACK bit was not correctly received by the base station.

5. The UE of any of claims 1-4, wherein a code block of the code blocks with a higher retransmission attempt is received at an earlier Orthogonal Frequency Division Multiplexing (OFDM) symbol.

6. The UE of any of claims 1-5, wherein the data buffer includes a one-bit New Data Indicator (NDI) field to indicate whether a code block of the code blocks is a new code block or a retransmitted code block.

7. The UE of any of claims 1-6, wherein the data buffer comprises a one-bit Redundancy Version (RV) field to indicate a channel coding combination for a code block of the code blocks.

8. The UE of any of claims 1-7, wherein the indicator comprises a reset indicator to indicate whether the code block is a new transport block.

9. The UE of any of claims 1-8, wherein the indicator comprises an ACK/NACK correct receipt indicator to indicate whether the ACK/NACK bit has been correctly received by the base station.

10. A base station, comprising:

a transceiver to: transmitting a plurality of first code blocks and a first indicator to a User Equipment (UE) to cause the UE to reset a data buffer associated with the first code block to an initial state in response to the first indicator, wherein the first indicator is further to indicate whether the first code block is a new transport block; and receiving one or more acknowledgement/negative acknowledgement (ACK/NACK) bits from the UE, the one or more ACK/NACK bits indicating whether the first code block has been successfully received by the UE; and

a control module to generate a second indicator to indicate whether the ACK/NACK bits have been correctly received by the base station, such that the UE updates the data buffer in response to the second indicator.

11. The base station of claim 10, wherein the control module is further to generate a plurality of second code blocks at least partially in response to determining that the ACK/NACK has been successfully received by the base station; and the transceiver is further configured to transmit the second code block to the UE.

12. The base station of claim 11, wherein the second indicator is further to indicate whether at least one of the second code blocks is a retransmitted block.

13. The base station according to any of claims 10-12, wherein the code block of the first code blocks with higher retransmission attempts is transmitted at an earlier Orthogonal Frequency Division Multiplexing (OFDM) symbol.

14. The base station of any of claims 10-13, wherein the transceiver is further to retransmit the first code block at least in part in response to determining that the second indicator indicates that the ACK/NACK bits were not successfully received by the base station.

15. The base station of any of claims 10-14, wherein the first indicator indicating that the first code block is a new transport block is transmitted at least in part in response to determining that a hybrid automatic repeat request (HARQ) process is too complex.