WO2016126330A1 - Code block cluster level harq - Google Patents
Code block cluster level harq Download PDFInfo
- Publication number
- WO2016126330A1 WO2016126330A1 PCT/US2015/065337 US2015065337W WO2016126330A1 WO 2016126330 A1 WO2016126330 A1 WO 2016126330A1 US 2015065337 W US2015065337 W US 2015065337W WO 2016126330 A1 WO2016126330 A1 WO 2016126330A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- cbc
- redundancy version
- version
- tti
- transport block
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0057—Block codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
- H04L1/0086—Unequal error protection
- H04L1/0089—Unequal error protection in payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1896—ARQ related signaling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0446—Resources in time domain, e.g. slots or frames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0061—Error detection codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
Definitions
- the following relates generally to wireless communication, and more specifically to code block cluster (CBC) level hybrid automatic repeat request (HARQ).
- CBC code block cluster
- HARQ level hybrid automatic repeat request
- Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on.
- These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power).
- 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).
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal frequency division multiple access
- a wireless multiple-access communications system may include a number of base stations, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UEs).
- a base station may communicate with the communication devices on downlink channels (e.g., for transmissions from a base station to a UE) and uplink channels (e.g., for transmissions from a UE to a base station).
- wireless devices may exchange data using Medium Access Control (MAC) layer units known as transport blocks.
- MAC Medium Access Control
- a receiving device may process the transport blocks and send acknowledgement information to the base station regarding their status. If a transport block is corrupt, the transmitting device may retransmit the entire transport block. However, in some instances only a portion of a transport block may be corrupt. Thus, retransmitting entire transport blocks may decrease system performance.
- MAC Medium Access Control
- Wireless devices may exchange data using Medium Access Control (MAC) layer units known as transport blocks.
- the transport blocks may be partitioned into CBCs, each of which may include one or more code blocks.
- a receiving device may attempt to decode a transport block and send acknowledgement (ACK) and negative-acknowledgment (NACK) information to the transmitting device based on the whether each CBC was successfully decoded.
- the transmitting device may retransmit a redundancy version of CBC for each NACK received.
- the transmitting device may group CBCs in segments of a transport block according to redundancy version. In some cases, the transmitting device may send a control message in a control channel which indicates the composition of the transport block.
- a method of communication at a wireless device may include identifying a redundancy version of a first CBC for transmission during a TTI, identifying a version of a second CBC for transmission during the TTI, and transmitting a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- the apparatus may include means for identifying a redundancy version of a first CBC for transmission during a TTI, means for identifying a version of a second CBC for transmission during the TTI, and means for transmitting a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- a further apparatus for communication at a wireless device may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
- the instructions may be executable by the processor to identify a redundancy version of a first CBC for transmission during a TTI, identify a version of a second CBC for transmission during the TTI, and transmit a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- a non-transitory computer-readable medium storing code for communication at a wireless device is described.
- the code may include instructions executable to identify a redundancy version of a first CBC for transmission during a TTI, identify a version of a second CBC for transmission during the TTI, and transmit a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- the version of the second CBC transmitted during the TTI includes a redundancy version or a new version of the second CBC. Additionally or alternatively, some examples may include processes, features, means, or instructions for configuring the transport block based at least in part on a set of redundancy version segments, each redundancy version segment of the set including a subset of CBCs having a same redundancy version.
- Some examples of the method, apparatuses, or non-transitory computer-readable medium described above may further include processes, features, means, or instructions for transmitting a control message for the TTI that includes an indication of which redundancy version segments are included in the transport block. Additionally or alternatively, in some examples, the control message for the TTI includes an indication of a redundancy version associated with each CBC included in the transport block.
- the indication includes four bits corresponding to a combination of redundancy version segments. Additionally or alternatively, in some examples, the control message also includes an ACK/NACK failure indicator.
- Some examples of the method, apparatuses, or non-transitory computer-readable medium described above may further include processes, features, means, or instructions for determining whether an ACK or a NACK was received for a transmitted CBC, and the ACK/NACK failure indicator may be based at least in part on the determination. Additionally or alternatively, some examples may include processes, features, means, or instructions for storing a HARQ state corresponding to a set of transmitted CBCs.
- Some examples of the method, apparatuses, or non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving an ACK/NACK response for the set of transmitted CBCs, and updating the HARQ state based at least in part on the ACK/NACK response. Additionally or alternatively, some examples may include processes, features, means, or instructions for determining that an ACK/NACK response has not been received for the set of transmitted CBCs, and refraining from updating the HARQ state based at least in part on the determination.
- the transmitted transport block includes at least one cyclic redundancy check (CRC) field.
- CRC cyclic redundancy check
- a further method of communication at a wireless device is also described.
- the method may include identifying a redundancy version of a first CBC for reception during a TTI, identifying a version of a second CBC for reception during the TTI, and receiving a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- the apparatus may include means for identifying a redundancy version of a first CBC for reception during a TTI, means for identifying a version of a second CBC for reception during the TTI, and means for receiving a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- a further apparatus for communication at a wireless device may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
- the instructions may be executable by the processor to identify a redundancy version of a first CBC for reception during a TTI, identify a version of a second CBC for reception during the TTI, and receive a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- a non-transitory computer-readable medium storing code for communication at a wireless device is described.
- the code may include instructions executable to identify a redundancy version of a first CBC for reception during a TTI, identify a version of a second CBC for reception during the TTI, and receive a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- the version of the second CBC transmitted during the TTI includes a redundancy version or a new version of the second CBC.
- the transport block may be based at least in part on a set of redundancy version segments, each redundancy version segment of the set including one or more CBCs having a same redundancy version.
- Some examples of the method, apparatuses, or non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving a control message for the TTI that includes an indication of which redundancy version segments are included in the transport block. Additionally or alternatively, in some examples, the indication includes four bits corresponding to a combination of redundancy version segments.
- control message may also include an ACK/NACK failure indicator. Additionally or alternatively, some examples may include processes, features, means, or instructions for storing a HARQ state corresponding to a set of received CBCs.
- Some examples of the method, apparatuses, or non-transitory computer-readable medium described above may further include processes, features, means, or instructions for updating the HARQ state based at least in part on processing a CRC associated with one or more of the set of received CBCs.
- FIG. 1 illustrates an example of a wireless communications system for code block cluster (CBC) level hybrid automatic repeat request (HARQ) in accordance with various aspects of the present disclosure
- FIG. 2 illustrates an example of a wireless communications system for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 3 illustrates an example of a transport block for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 4 illustrates an example of a process flow for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 5 shows a block diagram of a device configured for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 6 shows a block diagram of a device configured for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 7 shows a block diagram of a CBC level HARQ module configured for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 8 illustrates a block diagram of a system including a UE configured for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 9 illustrates a block diagram of a system including a base station configured for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 10 shows a flowchart illustrating a method for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 11 shows a flowchart illustrating a method for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 12 shows a flowchart illustrating a method for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 13 shows a flowchart illustrating a method for CBC level HARQ in accordance with various aspects of the present disclosure
- FIG. 14 shows a flowchart illustrating a method for CBC level HARQ in accordance with various aspects of the present disclosure.
- FIG. 15 shows a flowchart illustrating a method for CBC level HARQ in accordance with various aspects of the present disclosure.
- a transmitting device such as a base station, may communicate control and data to a receiving device user equipment (UE) using Medium Access Control (MAC) layer units known as transport blocks.
- the receiving device may respond with an acknowledgment (ACK) or a negative acknowledgement (NACK).
- transport blocks may be configured with subunits known as code block clusters (CBCs), and an ACK/NACK response may be sent for each CBC.
- CBCs within a transport block may be grouped according to redundancy versions, and additional control information may be transmitted with each transport block indicating which redundancy version segments, which may include subsets of CBCs have a common redundancy version, are present.
- Both the receiving and the transmitting device may maintain a state vector representing the status of each CBC to ensure both devices know which CBCs are to be transmitted or received in a given TTI.
- Increased ACK/NACK granularity may affect uplink (UL) and downlink (DL) control channel messaging, which may be addressed as described below.
- UL uplink
- DL downlink
- sending ACKs/NACKs for CBCs may increase ACK/NACK traffic on the UL; the UL control channel may thus be configured support a larger payload of ACKs/NACKs.
- the DL control channel may benefit from efficient signaling of redundancy versions for each code block in the transport block.
- systems that implement CBC ACKs/NACKs may enjoy just-in-time ACKs/NACKs—e.g., when a base station schedules a UE in a DL burst— and the ACKs/NACKs for the data which was scheduled in previous bursts may be available at the base station.
- the downlink may include a channel which carries data assigned to particular UEs (e.g., the physical downlink shared channel (PDSCH)).
- the data may be packaged in medium access control (MAC) transport blocks.
- MAC medium access control
- the base station may map the transport block data to resource elements (REs) within a resource block (e.g., one resource block may have 84 resource elements) for transmission over the air.
- a transport block may be made up of a number of sub-segments called code blocks.
- a base station may define a transport block by selecting a modulation and coding scheme (MCS) for the transport block, allocating radio resources (e.g., time and frequency) for the transport block, and picking the number of bits to transmit in the transport block.
- MCS modulation and coding scheme
- the number of coded bits may be equal to the number of REs multiplied by the modulation order and rank (e.g., 1000 REs with 64QAM (quadrature amplitude modulation) rank two will result in twelve-thousand coded bits).
- the base station may make such transport block- defining decisions based on outer loop, fairness, and buffer status.
- a base station After a base station transmits transport block data to a UE, the UE may send an acknowledgment (ACK) or negative acknowledgment (NACK) indicating the reception status of the data. For instance, if the data is not correctly received by the UE (e.g., a cyclic redundancy check (CRC) fails) the UE may send a NACK to the base station requesting a retransmission of the data (e.g., a redundancy version of the data).
- code blocks may be grouped together to form code block clusters (CBCs); for instance, a CBC may be an aggregation of one or more code blocks.
- CBCs code block clusters
- a transport block may be made up of a number of CBCs, each of which may have the same or different number of code blocks.
- the CBCs may be the minimum unit of PDSCH that is ACKed.
- a CRC may be performed on a code block, CRC, or transport block, or any combination thereof.
- the base station may partition the transport block into redundancy version (RV) segments.
- RV redundancy version
- a redundancy version represents a number of consecutive times a version of a given code block cluster has been transmitted.
- Each RV segment may contain one or more CBCs with the same redundancy version.
- a transport block may include three RV segments and one segment which carries new data.
- the base station may use a 4 bit mask in the physical downlink control channel (PDCCH).
- the mask may indicate which of the RV segments are present in the current grant. For example, mask with value "0001" may indicate that only new data is present in the transport block, while a value of "1001" may indicate that new data and one of the three RV segments is present.
- a base station may employ an indicator (e.g., a "failsafe" bit) in PDCCH, which may indicate to a UE whether an ACK/NACK for a CBC has been received. For instance, a base station may use the failsafe bit on DL subframe k if an ACK/NACK was received at the base station on subframe k — 1.
- each code block may have a unique 64 bit identification (ID) which is carried in a header.
- the ACKs/NACKs sent by a UE may have a hash of the code block IDs in each CBC, which the base station may use to identify the associated CBC.
- a base station and UE may each keep track of which redundancy version is next to be transmitted/received. For example, the base station and UE may independently maintain a vector which indicates the redundancy version of CBCs currently queued to be sent.
- the UE may update the redundancy version vector (e.g., increase the redundancy version for CBCs) based on the success of decoding PDCCH. For example, the UE may update the redundancy version vector when the PDCCH is successfully decoded, and maintain the current status of the redundancy version vector when the PDCCH is not successfully decoded.
- the base station may update the redundancy vector based on the reception of ACK/NACKs from the UE.
- the base station may update the redundancy version vector. If the base station does not receive an ACK/NACK from the UE, the base station may maintain the current status of the redundancy version vector. The base station may also retransmit the same redundancy versions as before— e.g., the redundancy versions indicated by the redundancy version vector— accompanied by the fail-safe bit to indicate to the UE that the redundancy versions have not changed.
- FIG. 1 illustrates an example of a wireless communications system 100 for CBC level hybrid automatic repeat request HARQ in accordance with various aspects of the present disclosure.
- the wireless communications system 100 includes base stations 105, a user equipment (UE) 1 15, and a core network 130.
- the core network 130 may provide user authentication, access authorization, tracking, internet protocol (IP) connectivity, and other access, routing, or mobility functions.
- the base stations 105 interface with the core network 130 through backhaul links 132 (e.g. , S I, etc.).
- the base stations 105 may perform radio configuration and scheduling for communication with the UEs 1 15, or may operate under the control of a base station controller (not shown).
- the base stations 105 may communicate, either directly or indirectly (e.g., through core network 130), with one another over backhaul links 134 (e.g., XI, etc.), which may be wired or wireless communication links.
- backhaul links 134 e.g., XI, etc.
- the base stations 105 may wirelessly communicate with the UEs 1 15 via one or more base station antennas. Each of the base stations 105 may provide communication coverage for a respective geographic coverage area 1 10.
- base stations 105 may be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNodeB (eNB), Home NodeB, a Home eNodeB, or some other suitable terminology.
- the geographic coverage area 1 10 for a base station 105 may be divided into sectors making up only a portion of the coverage area (not shown).
- the wireless communications system 100 may include base stations 105 of different types (e.g. , macro or small cell base stations). There may be overlapping geographic coverage areas 1 10 for different technologies
- the wireless communications system 100 is a Long Term Evolution (LTE)/LTE-Advanced (LTE-A) network.
- LTE/LTE-A networks the term evolved node B (eNB) may be generally used to describe the base stations 105.
- the wireless communications system 100 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 105 may provide communication coverage for a macro cell, a small cell, or other types of cell.
- 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 generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider.
- a small cell is a lower-powered base station, as compared with a macro cell, that may operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells.
- Small cells may include pico cells, femto cells, and micro cells according to various examples.
- a pico cell for example, may cover a small geographic area and may allow unrestricted access by UEs 115 with service subscriptions with the network provider.
- a femto cell may also cover a small geographic area (e.g., a home) and may provide restricted access by UEs 115 having an association with the femto cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 for users in the home, and the like).
- An e B for a macro cell may be referred to as a macro e B.
- 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.
- An eNB may support one or multiple (e.g., two, three, four, and the like) cells (e.g., component carriers).
- the wireless communications system 100 may support synchronous or asynchronous operation.
- the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time.
- the base stations 105 may have different frame timing, and transmissions from different base stations 105 may not be aligned in time.
- the techniques described herein may be used for either synchronous or asynchronous operations.
- the communication networks may be packet-based networks that operate according to a layered protocol stack and data in the user plane may be based on internet protocol (IP).
- IP internet protocol
- a radio link control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels.
- RLC radio link control
- a medium access control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The transport channels may be in transport blocks at the bottom of the MAC.
- the MAC layer may also use HARQ to provide retransmission at the MAC layer to improve link efficiency.
- the radio resource control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and the base stations 105.
- the RRC protocol layer may also be used for core network 130 support of radio bearers for the user plane data.
- the transport channels may be mapped to physical channels.
- a MAC layer transport block may be mapped to a subframe at the PHY layer.
- the transport block may include a CRC field for error detection at the receiver.
- HARQ may be implemented on a transport block-level basis.
- HARQ may also be implemented according to a finer resolution.
- a transport block may be divided into smaller size data chunks called code blocks, each of which may have a CRC that a UE 115 may use for HARQ.
- the code blocks may be grouped into CBCs, the corruption of which may be monitored using HARQ.
- the size of a code block may be predefined, and in some cases may be limited to a minimum or maximum number of bits.
- the number of bits transferred in a transport block may be based on the modulation and coding scheme (MCS), as well as the number of resource blocks assigned to the UE for which the transport block is intended.
- MCS modulation and coding scheme
- the MAC of a base station 105 may identify or determine a modulation scheme which can be handled by a UE 115 and check the physical resources for availability of resource blocks. Using this information, the MAC of the base station 105 may identify or determine an MCS and the number of resource blocks that can be allocated to the UE 115. In some instances, the MCS and resource allocation may be used to reference a table which gives the transport block size for the subframe. If the transport block size is greater than a maximum code block size, the transport block may be segmented into code blocks. If the transport block is smaller than a minimum code block size, the transport block may be represented by one code block, which may be appended with filler bits to match the minimum code block size.
- the UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile.
- a UE 115 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 115 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, or the like.
- PDA personal digital assistant
- a UE 115 may be able to communicate with various types of base stations and network equipment including macro e Bs, small cell e Bs, relay base stations, and the like.
- the communication links 125 shown in wireless communications system 100 may include uplink (UL) transmissions from a UE 115 to a base station 105, or downlink (DL) transmissions, from a base station 105 to a UE 115.
- the downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions.
- Each communication link 125 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 125 may transmit bidirectional communications using frequency division duplex (FDD) (e.g., using paired spectrum resources) or time division duplex (TDD) operation (e.g., using unpaired spectrum resources).
- FDD frequency division duplex
- TDD time division duplex
- Frame structures may be defined for FDD (e.g., frame structure type 1) and TDD (e.g., frame structure type 2).
- base stations 105 or UEs 115 may include multiple antennas for employing antenna diversity schemes to improve communication quality and reliability between base stations 105 and UEs 115. Additionally or alternatively, base stations 105 or UEs 115 may employ multiple input multiple output (MIMO) techniques that may take advantage of multi-path environments to transmit multiple spatial layers carrying the same or different coded data.
- MIMO multiple input multiple output
- Wireless communications system 100 may support operation on multiple cells or carriers, a feature which may be referred to as carrier aggregation (CA) or multi-carrier operation.
- a carrier may also be referred to as a component carrier (CC), a layer, or the like.
- CC component carrier
- the terms “carrier,” “component carrier,” and “cell” may be used interchangeably herein.
- a UE 115 may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation.
- Carrier aggregation may be used with both FDD and TDD component carriers.
- wireless communications system 100 may utilize enhanced CCs (eCC).
- eCC may be characterized by features, including: flexible bandwidth, variable length TTIs, and modified control channel configuration.
- an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal or non-ideal backhaul link).
- An eCC may also be configured for use in unlicensed spectrum or shared spectrum (where more than one operator is licensed to use the spectrum).
- An eCC characterized by flexible bandwidth may include one or more segments that may be utilized by UEs 115 that are not capable of monitoring the whole bandwidth or prefer to use a limited bandwidth (e.g., to conserve power).
- an eCC may utilize a variable TTI length and symbol duration.
- an eCC may include multiple hierarchical layers associated with the different TTI lengths. For example, TTIs at one hierarchical layer may correspond to uniform 1 ms subframes, whereas in a second layer, variable length TTIs may correspond to bursts of short duration symbol periods. In some cases, a shorter symbol duration may also be associated with increased subcarrier spacing.
- the numerology of resources of the eCC may be different from numerology of another CC, which may employ TTIs defined in a version or release of, for example, a particular LTE standard.
- Flexible bandwidth and variable TTIs may be associated with a modified control channel configuration— e.g., an eCC may utilize an enhanced physical downlink control channel (ePDCCH) for DL control information, which may perform some of the functions of the PDCCH described below.
- control channels of an eCC may utilize frequency division multiplexed (FDM) control channels to accommodate flexible bandwidth or UEs 115 having differing bandwidth capabilities.
- FDM frequency division multiplexed
- Other control channel modifications may include the use of additional control channels— e.g., for eMBMS scheduling or to indicate the length of variable length UL and DL bursts— or control channels transmitted at different intervals.
- An eCC may also include modified or additional HARQ-related control information.
- a UE 115 may employ CBC level HARQ on an eCC.
- Wireless system 100 may implement error detection codes for transmissions to detect accidental changes to raw data.
- a CRC may be used to detect errors during the decoding of received data. Before transmission, the CRC may be derived from the data according to a predetermined calculation. The CRC may then be appended to the data, which is subsequently transmitted. The receiving entity may perform the same calculation and check the result against the CRC bits. If the CRC bits do not match the calculated value, the CRC may be deemed to have failed, and the receiving entity may determine that the data has been corrupted.
- HARQ may be a method of ensuring that data is received correctly over a wireless communication link 125.
- the MAC layer may be responsible for managing the HARQ function, which may be a transport block level automatic retry.
- HARQ may include a combination of error detection (e.g., using a CRC), FEC, and retransmission (e.g., automatic repeat request (ARQ)).
- ARQ automatic repeat request
- HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., signal-to-noise conditions).
- Incremental Redundancy HARQ incorrectly received data may be stored in a buffer and combined with subsequent transmissions to improve the overall likelihood of successfully decoding the data.
- a UE 1 15 may buffer a number of failed CBCs for use with redundancy versions to reconstruct a signal.
- the UE 115 may store the unsuccessfully decoded CBCs in buffers to use in conjunction with redundancy versions in the reconstruction of the data.
- redundancy bits are added to each message prior to transmission. This may be especially useful in poor radio conditions.
- redundancy bits are not added to each transmission, but are retransmitted after the transmitter of the original message receives a NACK indicating a failed attempt to decode the information.
- HARQ may be done in combination between the MAC and the PHY; the PHY may handle retention and re-combination and the MAC may perform management and signaling. For example, when there is a transport block CRC failure, the PHY may indicate the failure to the MAC. Accordingly, the MAC may indicate a NACK, which may prompt a retransmission from the transmitting entity which originally sent the transport block.
- a base station 105 may schedule DL resources using a PDCCH.
- PDCCH may carry downlink control information (DCI) in control channel elements (CCEs), which may consist of nine logically contiguous resource element groups (REGs), where each REG contains 4 resource elements (REs).
- DCI includes information regarding DL scheduling assignments, UL resource grants, transmission scheme, UL power control, HARQ information, modulation and coding scheme (MCS) and other information.
- MCS modulation and coding scheme
- the size and format of the DCI messages can differ depending on the type and amount of information that is carried by the DCI. For example, if spatial multiplexing is supported, the size of the DCI message is large compared to contiguous frequency allocations. Similarly, for a system that employs MIMO, the DCI must include additional signaling information. DCI size and format depend on the amount of information as well as factors such as bandwidth, the number of antenna ports, and duplexing mode.
- PDCCH can carry DCI messages associated with multiple users, and each UE 1 15 may decode the DCI messages that are intended for it.
- each UE 1 15 may be assigned a cell radio network temporary identity (C-RNTI) and CRC bits attached to each DCI may be scrambled based on the C-RNTI.
- C-RNTI cell radio network temporary identity
- a limited set of CCE locations can be specified for DCI associated with a specific UE 1 15.
- a UE 1 15 may attempt to decode DCI by performing a process known as a blind decode, during which search spaces are randomly decoded until the DCI is detected. During a blind decode, the UE 1 15 may attempt to descramble all potential DCI messages using its C-RNTI, and perform a cyclic redundancy check (CRC) to determine whether the attempt was successful.
- CRC cyclic redundancy check
- wireless devices such as a base station 105 and a UE 1 15 may exchange data using MAC layer units known as transport blocks.
- the transport blocks may be partitioned into CBCs, each of which may include one or more code blocks.
- a UE 1 15 may attempt to decode a transport block and send ACK/NACK information to a base station 105 based on the whether each CBC was successfully decoded.
- the base station 105 may retransmit a redundancy version of CBC for each NACK received.
- the base station 105 may group CBCs in segments of a transport block according to redundancy version.
- the base station 105 may send a control message in a control channel which indicates the composition of the transport block.
- FIG. 2 illustrates an example of a wireless communications system 200 for CBC level HARQ in accordance with various aspects of the present disclosure.
- Wireless communications system 200 may include UE 1 15-a, which may be an example of a UE 1 15 described with reference to FIG. 1.
- Wireless communications system 200 may also include a base station 105-a, which may be an example of a base station 105 described with reference to FIG. 1.
- Base station 105-a may transmit control and data to any UE 1 15 within its coverage area 1 10-a via downlink (e.g., downlink 205).
- downlink 205 For instance, base station 105-a may transmit data to UE 1 15-a in a transport block 215, which may be part of downlink 205.
- UE 1 15-a may communicate with base station 105-a via uplink (e.g., uplink 210). For example, UE 1 15-a may indicate the status for portions of transport block 215 via acknowledgments (ACKs) and negative acknowledgments (NACKs) (e.g., ACK/NACKs 220).
- transport block 215 may include multiple CBCs, each of which includes a number of code blocks. The CBCs may be grouped into segments according to the redundancy version (RV) of the CBCs; for example, there may be four RV segments corresponding to four possible RVs, as illustrated in wireless communications system 200. Different transport blocks may have the same or different number of CBCs.
- RV redundancy version
- CRC parity bits may be included with each code block, and, in some cases, for a CBC or for the transport block as a whole.
- the UE 1 15-a may use CRCs to detect errors during the decoding process and transmit ACK/NACKs 220 accordingly.
- UE 1 15-a may send CBC level ACK/NACKs 220, and base station 105-a may transmit redundancy versions of one or more of the CBCs based on the ACK/NACKs 220.
- the retransmitted CBCs may be redundancy versions of CBCs which were NACKed by UE 1 15-a.
- the CBCs may be the minimum unit of PDSCH that is ACK/NACKed.
- UE 1 15-a may transmit a NACK for a CBC if a CRC fails for one or more code blocks in the CBC.
- the CRC failure may occur at the code block level, or at the CBC level. That is, a NACK may be transmitted if code block-level CRC fails, or if a CBC level CRC fails.
- the NACK may serve as an indication to base station 105-a to resend the CBC— e.g., base station 105-a may send a redundancy version of a CBC.
- Additional control information may be transmitted along with each transport block to facilitate the CBC level HARQ.
- base station 105-a may indicate to UE 1 15-a which RV segments are present in a transport block. In some examples, this may take the form a four (4) bit mask included in a PDCCH message. Each bit may be toggled if one or more CBCs in the transport block have a corresponding RV value.
- Another field may be used to indicate whether the transmitting device (e.g., base station 105-a) received the ACK/NACK from a previous transport block. This may enable the transmitting device and the receiving device to maintain synchronized status information for each CBC.
- base station 105-a may retransmit the same data along with the ACK/NACK failure indicator. If UE 1 15-a receives the ACK/NACK failure indicator, it may anticipate the same information again. If UE 1 15-a receives PDCCH and the ACK/NACK failure indicator is absent, it may anticipate new data, or subsequent redundancy versions for CBCs that did not pass the CRC.
- FIG. 3 illustrates an example of a transport block 300 for CBC level HARQ in accordance with various aspects of the present disclosure.
- Transport block 300 may be an example of a transport block sent from a base station 105 to a UE 115, as described with reference to FIG. 2.
- Transport block 300 may include a new data segment 305, a first RV segment 310, a second RV segment 315, and a third RV segment 320.
- An RV segment may include one or several CBCs 325, all of which may have the same redundancy version. In other words, the CBCs that are being re-transmitted for the nth time may be aggregated in an RV segment.
- New data segment 305 may include data which is being sent to a UE 115 from a base station 105 for the first time.
- New data segment 305 may be an RV segment which includes data with redundancy version zero (RV0).
- New data segment 305 may include a number of CBCs (not shown), each of which may include one or more code blocks.
- the UE 115 may decode the code blocks of new data segment 305 and send a CBC level ACK/NACK based on the success of the decoding. For example, if a code block within a CBC fails CRC, the UE may indicate a NACK to the base station 105 indicating the decoding failure.
- First RV segment 310 may include the first retransmissions (e.g., RV1) of CBCs which were incorrectly received during a previous transport block.
- the retransmissions may be the result of NACKs associated with CBCs conveyed by a new data segment 305 during a previous transport block 300.
- First RV segment 310 may include three CBCs, which may be CBCs with the same redundancy version (e.g., redundancy version one).
- the UE 115 may send a NACK for each CBC 325 associated with a failed CRC. In other words, the CBCs 325 may be individually decoded and ACKed/NACKed.
- Second RV segment 315 may convey second redundancy versions (RV2) of CBCs 325 whose first redundancy versions were incorrectly received in a first RV segment 310 of a previous transport block.
- RV segment 315 may include two CBCs 325, which may be redundancy versions of two CBCs whose first redundancy versions conveyed in a previous first RV segment 310 were not correctly received.
- second RV segment 315 may be used to retransmit CBCs 325 which were incorrectly received during both an original transmission and in a subsequent retransmission.
- third RV segment 320 may include CBCs which are on their third round of retransmission (RV3). That is, CBCs 325 may be redundancy version of CBCs 325 which have been incorrectly received in three previous transmissions/retransmissions.
- third RV segment 320 may convey four CBCs 325, which may be the third redundancy versions of their respective CBCs.
- a CBC 325 may be a retransmission of a CBC 325 which failed decoding when conveyed by a previous new data segment 305, first RV segment 310, and second RV segment 315.
- redundancy versions of a transport block CBC may be sent in RV segments until the CBC is properly decoded— e.g., the base station receives an ACK— or the UE experiences a radio link failure (RLF).
- RLF radio link failure
- the first, second, and third redundancy versions of CBCs may be sent using the same or different encoding.
- transport block 300 may include any number of RV segments.
- the RV segments may be of any length— e.g., the RV segments may include any number of CBCs 325.
- the RV segments are the same length; in some examples, the RV segments are different lengths.
- the composition of transport block 300 may be dynamically configurable, and the segments may be present or absent based on the data being sent. For example, if all CBCs 325 conveyed by transport block 300 are successfully received, a subsequent transport block 300 may include only new data segment 305.
- a base station 105 may indicate the configuration of a transport block using a bit mask in a control channel.
- a base station 105 may use a N bit mask on the physical downlink control channel (PDCCH) for an N segment transport block.
- PDCCH physical downlink control channel
- each bit may represent the presence or absence of its respective segment.
- a mask value of "0001" may indicate to a UE 115 that transport block 300 includes only new data segment 305, while a mask value of " 1001" may indicate that transport block 300 includes both new data segment 305 and third RV segment 320.
- a UE 115 may reference the control channel bit mask to determine the configuration of a transport block.
- the control channel may also include a fail-safe bit (e.g., an ACK/NACK failure indicator), which may indicate the reception of an ACK/NACK at the base station 105. For example, if an ACK/NACK is received for subframe k — 1, the base station 105 may indicate the ACK/NACK reception to the UE 115 using the fail-safe bit on subframe k.
- a base station 105 and a UE 1 15 may use an identification scheme to account for which code blocks have been ACKed and which are to be retransmitted. In one scheme, each code block may have a unique identifier (ID) (e.g., 64 bits) which identifies the code block from other code blocks.
- ID unique identifier
- a code block ID may be carried by a code block header, which may be the same length as the ID.
- the UE 1 15 may identify which code blocks have been successfully and unsuccessfully decoded and relay that information to the base station 105.
- the UE 1 15 may include a hash of the code block IDs in the CBC.
- the base station may reference the hash of code block IDs to determine the associated CBC, which the base station may retransmit if the hash was conveyed by a NACK.
- a base station 105 and a UE 1 15 may employ a redundancy version tracking scheme to synchronize the transmissions of CBC redundancy versions.
- a base station 105 and a UE 1 15 each independently maintain a redundancy version state vector that tracks the current redundancy version of each CBC. The vectors may be referenced to determine which CBC redundancy version is next to be transmitted/received.
- a base station 105 may update its vector based on ACK/NACKs from a UE 1 15, and the UE 1 15 may update its vector based on decoding PDCCH.
- a base station 105 may transmit a transport block which includes several RV segments, each with a number of CBC redundancy versions.
- the UE 1 15 may attempt to decode PDCCH. If decoding PDCCH is successful, the UE 1 15 may decode the transport block, update the redundancy version vector accordingly, and send ACK/NACKs as appropriate. Upon reception of the ACK/NACKs, the base station 105 may update the redundancy version vector and transmit redundancy versions accordingly. If decoding PDCCH is unsuccessful, the UE 1 15 may not receive the transport block, update the redundancy version vector, or send ACK/NACKs. Consequently, the base station may not receive ACK/NACKs. Accordingly, the base station may refrain from updating the redundancy version vector and retransmit the same redundancy versions. The base station 105 may send an ACK/NACK failure indicator to the UE 1 15, which may indicate that the previous redundancy versions are being re-transmitted.
- FIG. 4 illustrates an example of a process flow 400 for CBC level HARQ in accordance with various aspects of the present disclosure.
- Process flow 400 may include a UE 1 15-b, which may be an example of a UE 1 15 described above with reference to FIGs. 1- 3.
- Process flow 400 may also include a base station 105-b, which may be an example of a base station 105 described above with reference to FIGs. 1-3.
- the steps of process flow 400 may be performed by any set of wireless devices communicating with CBC level HARQ.
- base station 105-b and UE 115 may identify a HARQ state for one or more CBCs. In some cases, base station 105-b and UE 115-b may store the HARQ state in a memory buffer.
- base station 105-b may identify a redundancy version of a number of CBCs in preparation for transmitting a transport block to UE 115-b. For example, base station 105-b may identify a redundancy version of a first CBC for transmission during a transmission time interval (TTI). Additionally, the base station 105-b may identify a version of a second CBC for transmission during the TTI. Base station 105-b may then configure a transport block for transmission over PDSCH to UE 115-b. In some cases, base station 105-b may configure the transport block based on a set of redundancy version segments, and each redundancy version segment may include a subset of CBCs having a same redundancy version.
- TTI transmission time interval
- base station 105-b may transmit (and UE 115-b may receive) a control message indicating which redundancy version segments are included in the transport block.
- the control message includes an indication of a redundancy version associated with each CBC included in the transport block.
- the indication includes four (4) bits corresponding to the redundancy version segments.
- the control message may also include an ACK/NACK failure indicator. In some instances, the ACK/NACK failure indicator may be based on whether an ACK/NACK response was received for a previously transmitted CBC.
- base station 105-b may transmit (and UE 115-b may receive) a transport block including the redundancy version of the first CBC and the version of the second CBC.
- the transmitted transport block comprises at least one CRC field.
- the version of the second CBC may include a redundancy version or a new version of the second CBC.
- UE 115-b may decode the control message and update (or refrain from updating) a HARQ state based on the information in the control message— e.g., based on a bit mask corresponding to the included RV segments and the ACK/NACK failure indicator.
- UE 1 15-b may decode the first and second CBCs.
- UE 1 15-b may perform a CRC for the received code blocks.
- UE 1 15-b may determine ACK/NACKs for the individual CBCs— e.g. , based on the success of the CRCs.
- UE 1 15-b may transmit (and base station 105-b may receive) ACK/NACKs for the first and second CBCs, and any additional CBCs.
- base station 105-b may update the HARQ state based on the ACK/NACKs. In some cases, base station 105-b may determine that an ACK/NACK response has not been received for the set of transmitted CBCs. Accordingly, base station 105-b may refrain from updating the HARQ state based on the determination.
- FIG. 5 shows a block diagram of a wireless device 500 configured for CBC level HARQ in accordance with various aspects of the present disclosure.
- Wireless device 500 may be an example of aspects of a UE 1 15 or a base station 105 described with reference to FIGs. 1-4.
- Wireless device 500 may include a receiver 505, a CBC level HARQ module 510, or a transmitter 515.
- Wireless device 500 may also include a processor. Each of these components may be in communication with one another.
- the receiver 505 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to CBC level HARQ, etc.). Information may be passed on to the CBC level HARQ module 510, and to other components of wireless device 500.
- the receiver 505 may receive a transport block including the redundancy version of the first CBC and the version of the second CBC during the TTI.
- the receiver 505 may receive a control message for the TTI including an indication of which redundancy version segments are included in the transport block.
- the receiver 505 (of a transmitting device) may receive an ACK/NACK response for the set of transmitted CBCs.
- the CBC level HARQ module 510 may identify a redundancy version of a first CBC for transmission during a TTI and may identify a version of a second CBC for transmission during the TTI.
- the CBC level HARQ module 510 in combination with, e.g. , the transmitter 515, may transmit a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI.
- the CBC level HARQ module 510 in combination with, e.g., the receiver 505, may receive a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI.
- the transmitter 515 may transmit signals received from other components of wireless device 500.
- the transmitter 515 may be collocated with the receiver 505 in a transceiver module.
- the transmitter 515 may include a single antenna, or it may include a several antennas.
- FIG. 6 shows a block diagram of a wireless device 600 for CBC level HARQ in accordance with various aspects of the present disclosure.
- Wireless device 600 may be an example of aspects of a wireless device 500 or a UE 115 or a base station 105 described with reference to FIGs. 1-5.
- Wireless device 600 may include a receiver 505-a, a CBC level HARQ module 510-a, or a transmitter 515-a.
- Wireless device 600 may also include a processor. Each of these components may be in communication with one another.
- the CBC level HARQ module 510-a may also include a redundancy version module 605, and a transport block configuration module 610.
- the receiver 505-a may receive information which may be passed on to CBC level HARQ module 510-a, and to other components of wireless device 600.
- the CBC level HARQ module 510-a may perform the operations described above with reference to FIG. 5.
- the transmitter 515-a may transmit signals received from other components of wireless device 600.
- the redundancy version module 605 may identify a redundancy version of a first CBC for transmission during a TTI, as described above with reference to FIGs. 2-4.
- the redundancy version module 605 may also identify a version of a second CBC for transmission during the TTI.
- the version of the second CBC transmitted during the TTI includes a redundancy version or a new version of the second CBC.
- the redundancy version module 605 may identify a redundancy version of a first CBC for reception during a TTI.
- the redundancy version module 605 may also identify a version of a second CBC for reception during the TTI.
- the version of the second CBC transmitted during the TTI comprises a redundancy version or a new version of the second CBC.
- the transport block configuration module 610 may transmit a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI, as described above with reference to FIGs. 2-4.
- the transport block configuration module 610 may also configure the transport block using several redundancy version segments, such that each redundancy version segment may include a subset of CBCs having a same redundancy version.
- the transport block may thus be based on a set of redundancy version segments, each redundancy version segment of the set including one or more CBCs having a same redundancy version.
- FIG. 7 shows a block diagram 700 of a CBC level HARQ module 510-b which may be a component of a wireless device 500 or a wireless device 600 for CBC level HARQ in accordance with various aspects of the present disclosure.
- the CBC level HARQ module 510-b may be an example of aspects of a CBC level HARQ module 510 described with reference to FIGs. 5-6.
- the CBC level HARQ module 510-b may include a redundancy version module 605-a, and a transport block configuration module 610-a. Each of these modules may perform the functions described above with reference to FIG. 6.
- the CBC level HARQ module 510-b may also include a control message module 705, an ACK/NACK failure module 710, and a HARQ state module 715.
- the various modules of CBC level HARQ module 510-b may be in communication with one another.
- the control message module 705 may transmit a control message for the TTI that includes an indication of which redundancy version segments are included in the transport block, as described above with reference to FIGs. 2-4.
- the control message for the TTI may include an indication of a redundancy version associated with each CBC included in the transport block.
- the indication includes four bits corresponding to a combination of redundancy version segments.
- the control message may also include an ACK/NACK failure indicator.
- the ACK/NACK failure module 710 may configure a control message to include an ACK/NACK failure indicator, as described above with reference to FIGs. 2-4. In some examples, the ACK/NACK failure module 710 may also determine whether an ACK or a NACK was received for a transmitted CBC, and the ACK/NACK failure indicator may be configured according to, and may thus be based on, the determination. [0104] The HARQ state module 715 may store a HARQ state corresponding to several transmitted CBCs, as described above with reference to FIGs. 2-4. The HARQ state module 715 may also update the HARQ state based on the ACK/NACK response.
- the HARQ state module 715 may, for instance, determine that an ACK/NACK response has not been received for the transmitted CBCs. The HARQ state module 715 may also refrain from updating the HARQ state based on the determination. In some cases, the HARQ state module 715 may update the HARQ state based on processing a CRC associated with one or more received CBCs.
- wireless device 500, wireless device 600, or CBC level HARQ module 510-b may each, individually or collectively, be implemented with at least one application specific integrated circuit (ASIC) adapted to perform some or all of the applicable functions in hardware.
- ASIC application specific integrated circuit
- the functions may be performed by one or more other processing units (or cores), on at least one IC.
- other types of integrated circuits may be used (e.g., Structured/Platform ASICs, a field programmable gate array (FPGA), or another semi-custom IC), which may be programmed in any manner known in the art.
- the functions of each unit 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.
- FIG. 8 shows a diagram of a system 800 including a UE configured for CBC level HARQ in accordance with various aspects of the present disclosure.
- System 800 may include UE 1 15-c, which may be an example of a wireless device 500, or a wireless device 600 described above with reference to FIGs. 1-7.
- UE 1 15-c may include a CBC level HARQ module 810, which may be an example of a CBC level HARQ module 510 described with reference to FIGs. 5-7.
- UE 1 15-c may include a CRC module 825.
- UE 1 15-c may also include components for bi-directional voice and data communications including components for transmitting communications and components for receiving communications. For example, UE 1 15-c may communicate bi-directionally with base station 105-c or UE 1 15-d.
- the CRC module 825 may perform a CRC on received code blocks to determine whether each code block has been correctly received.
- a transmitted or received transport block may include at least one CRC field—e.g., associated with code blocks, CBCs, or transport blocks— as described above with reference to FIGs. 2-4.
- UE 1 15-c may also include a processor 805, and memory 815 (including software (SW) 820), a transceiver module 835, and one or more antenna(s) 840, each of which may communicate, directly or indirectly, with one another (e.g. , via buses 845).
- SW software
- the transceiver module 835 may communicate bi-directionally, via the antenna(s) 840 or wired or wireless links, with one or more networks, as described above.
- the transceiver module 835 may communicate bi-directionally with a base station 105 or another UE 1 15.
- the transceiver module 835 may include a modem to modulate the packets and provide the modulated packets to the antenna(s) 840 for transmission, and to demodulate packets received from the antenna(s) 840.
- UE 1 15-e may include a single antenna 840
- UE 1 15-c may also have multiple antennas 840 capable of concurrently transmitting or receiving multiple wireless transmissions.
- the memory 815 may include random access memory (RAM) and read only memory (ROM).
- the memory 815 may store computer-readable, computer-executable software/firmware code 820 including instructions that, when executed, cause the processor 805 to perform various functions described herein (e.g., CBC level HARQ, etc.).
- the software/firmware code 820 may not be directly executable by the processor 805 but cause a computer (e.g. , when compiled and executed) to perform functions described herein.
- the processor 805 may include an intelligent hardware device, (e.g. , a central processing unit (CPU), a microcontroller, an ASIC, etc.)
- FIG. 9 shows a diagram of a system 900 including a base station 105 configured for CBC level HARQ in accordance with various aspects of the present disclosure.
- System 900 may include base station 105-d, which may be an example of a wireless device 600, a CBC level HARQ module 510-b, or a base station 105 described above with reference to FIGs. 1-8.
- Base station 105-d may include a base station CBC level HARQ module 910, which may be an example of a CBC level HARQ module 510 described with reference to FIGs. 5-7.
- Base station 105-d may also include components for bi-directional voice and data communications including components for transmitting communications and components for receiving communications. For example, base station 105-d may communicate bi- directionally with UE 1 15-e or UE 1 15-f.
- base station 105-d may have one or more wired backhaul links.
- Base station 105-d may have a wired backhaul link (e.g., S I interface, etc.) to the core network 130.
- Base station 105-d may also communicate with other base stations 105, such as base station 105-e and base station 105-f via inter-base station backhaul links (e.g., an X2 interface).
- Each of the base stations 105 may communicate with UEs 115 using the same or different wireless communications technologies.
- base station 105-d may communicate with other base stations such as 105-e or 105-f utilizing base station communications module 925.
- base station communications module 925 may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between some of the base stations 105.
- base station 105-d may communicate with other base stations through core network 130.
- base station 105-d may communicate with the core network 130 through network communications module 930.
- the base station 105-d may include a processor 905, memory 915 (including software (SW) 920), transceiver modules 935, and antenna(s) 940, which each may be in communication, directly or indirectly, with one another (e.g., over bus system 945).
- the transceiver modules 935 may be configured to communicate bi-directionally, via the antenna(s) 940, with the UEs 115, which may be multi-mode devices.
- the transceiver module 935 (or other components of the base station 105-d) may also be configured to communicate bi-directionally, via the antennas 940, with one or more other base stations (not shown).
- the transceiver module 935 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 940 for transmission, and to demodulate packets received from the antennas 940.
- the base station 105-d may include multiple transceiver modules 935, each with one or more associated antennas 940.
- the transceiver module may be an example of a combined receiver 505 and transmitter 515 of FIG. 5.
- the memory 915 may include RAM and ROM.
- the memory 915 may also store computer-readable, computer-executable software code 920 containing instructions that are configured to, when executed, cause the processor 905 to perform various functions described herein (e.g., CBC level HARQ , selecting coverage enhancement techniques, call processing, database management, message routing, etc.).
- the software code 920 may not be directly executable by the processor 905 but be configured to cause the computer, e.g., when compiled and executed, to perform functions described herein.
- the processor 905 may include an intelligent hardware device, e.g., a CPU, a microcontroller, an ASIC, etc.
- the processor 905 may include various special purpose processors such as encoders, queue processing modules, base band processors, radio head controllers, digital signal processor (DSPs), and the like.
- the base station communications module 925 may manage communications with other base stations 105.
- the communications management module may include a controller or scheduler for controlling communications with UEs 1 15 in cooperation with other base stations 105.
- the base station communications module 925 may coordinate scheduling for transmissions to UEs 1 15 for various interference mitigation techniques such as beamforming or joint transmission.
- FIG. 10 shows a flowchart illustrating a method 1000 for CBC level HARQ in accordance with various aspects of the present disclosure.
- the operations of method 1000 may be implemented by a wireless device, including a UE 1 15 or a base station 105, or its components, which may include wireless device 500 or wireless device 600, as described with reference to FIGs. 1-9.
- the operations of method 1000 may be performed by the CBC level HARQ module 510 as described with reference to FIGs. 5-8.
- the wireless device may execute a set of codes to control the functional elements to perform the functions described below. Additionally or alternatively, the wireless device may perform aspects the functions described below using special-purpose hardware.
- the wireless device may identify a redundancy version of a first CBC for transmission during a TTI as described above with reference to FIGs. 2-4.
- the operations of block 1005 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may identify a version of a second CBC for transmission during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1010 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may transmit a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1015 may be performed by the transport block configuration module 610 as described above with reference to FIG. 6.
- FIG. 11 shows a flowchart illustrating a method 1 100 for CBC level HARQ in accordance with various aspects of the present disclosure.
- the operations of method 1 100 may be implemented by a wireless device, including a UE 1 15 or a base station 105, or its components, which may include wireless device 500 or wireless device 600, as described with reference to FIGs. 1-9.
- method 1 100 may be performed by the CBC level HARQ module 510 as described with reference to FIGs. 5-8.
- the wireless device may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the wireless device may perform aspects the functions described below using special-purpose hardware.
- the method 1 100 may also incorporate aspects of method 1000 of FIG. 10.
- the wireless device may identify a redundancy version of a first CBC for transmission during a TTI as described above with reference to FIGs. 2-4.
- the operations of block 1 105 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may identify a version of a second CBC for transmission during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1 1 10 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may configure a transport block based at least in part on a set of redundancy version segments, each redundancy version segment of the set including a subset of CBCs having a same redundancy version as described above with reference to FIGs. 2-4.
- the operations of block 1 1 15 may be performed by the transport block configuration module 610 as described above with reference to FIG. 6.
- the wireless device may transmit a control message for the TTI that includes an indication of which redundancy version segments are included in the transport block as described above with reference to FIGs. 2-4.
- the operations of block 1 120 may be performed by the control message module 705 as described above with reference to FIG. 7.
- the wireless device may transmit the transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1 125 may be performed by the transport block configuration module 610 as described above with reference to FIG. 6.
- FIG. 12 shows a flowchart illustrating a method 1200 for CBC level HARQ in accordance with various aspects of the present disclosure.
- the operations of method 1200 may be implemented by a wireless device, including a UE 1 15 or a base station 105, or its components, which may include wireless device 500 or wireless device 600, as described with reference to FIGs. 1-9.
- the operations of method 1200 may be performed by the CBC level HARQ module 510 as described with reference to FIGs. 5-8.
- a wireless device may execute a set of codes to control the functional elements to perform the functions described below. Additionally or alternatively, the wireless device may perform aspects the functions described below using special-purpose hardware.
- the method 1200 may also incorporate aspects of methods 1000 or 1 100 of FIGs. 10 and 1 1.
- the wireless device may identify a redundancy version of a first CBC for transmission during a TTI as described above with reference to FIGs. 2-4.
- the operations of block 1205 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may identify a version of a second CBC for transmission during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1210 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may transmit a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1215 may be performed by the transport block configuration module 610 as described above with reference to FIG. 6.
- the wireless device may store a HARQ state corresponding to a set of transmitted CBCs as described above with reference to FIGs. 2-4.
- the operations of block 1220 may be performed by the HARQ state module 715 as described above with reference to FIG. 7.
- the wireless device may receive an ACK/NACK response for the set of transmitted CBCs as described above with reference to FIGs. 2-4.
- the operations of block 1225 may be performed by the receiver 505 as described above with reference to FIG. 5.
- the wireless device may update the HARQ state based at least in part on the ACK/NACK response as described above with reference to FIGs. 2-4.
- the operations of block 1230 may be performed by the HARQ state module 715 as described above with reference to FIG. 7.
- FIG. 13 shows a flowchart illustrating a method 1300 for CBC level HARQ in accordance with various aspects of the present disclosure.
- the operations of method 1300 may be implemented by a wireless device, including a UE 115 or a base station 105, or its components, which may include wireless device 500 or wireless device 600, as described with reference to FIGs. 1-9.
- the operations of method 1300 may be performed by the CBC level HARQ module 510 as described with reference to FIGs. 5-8.
- a wireless device may execute a set of codes to control the functional elements to perform the functions described below. Additionally or alternatively, the wireless device may perform aspects the functions described below using special-purpose hardware.
- the wireless device may identify a redundancy version of a first CBC for reception during a TTI as described above with reference to FIGs. 2-4.
- the operations of block 1305 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may identify a version of a second CBC for reception during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1310 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may receive a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1315 may be performed by the receiver 505 as described above with reference to FIG. 5.
- FIG. 14 shows a flowchart illustrating a method 1400 for CBC level HARQ in accordance with various aspects of the present disclosure.
- the operations of method 1400 may be implemented by a wireless device, including a UE 115 or a base station 105, or its components, which may include wireless device 500 or wireless device 600, as described with reference to FIGs. 1-9.
- the operations of method 1400 may be performed by the CBC level HARQ module 510 as described with reference to FIGs. 5-8.
- a wireless device may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the wireless device may perform aspects the functions described below using special-purpose hardware.
- the method 1400 may also incorporate aspects of method 1300 of FIGs. 13.
- the wireless device may identify a redundancy version of a first CBC for reception during a TTI as described above with reference to FIGs. 2-4.
- the operations of block 1405 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may identify a version of a second CBC for reception during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1410 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may receive a control message for the TTI that includes an indication of which redundancy version segments are included in the transport block as described above with reference to FIGs. 2-4.
- block 1415 may be performed by the receiver 505 as described above with reference to FIG. 5.
- the wireless device may receive a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI as described above with reference to FIGs. 2-4.
- the transport block is based at least in part on a set of redundancy version segments, each redundancy version segment of the set including one or more CBCs having a same redundancy version.
- the operations of block 1420 may be performed by the receiver 505 as described above with reference to FIG. 5.
- FIG. 15 shows a flowchart illustrating a method 1500 for CBC level HARQ in accordance with various aspects of the present disclosure.
- the operations of method 1500 may be implemented by a wireless device, including a UE 1 15 or a base station 105, or its components, which may include wireless device 500 or wireless device 600, as described with reference to FIGs. 1-9.
- the operations of method 1500 may be performed by the CBC level HARQ module 510 as described with reference to FIGs. 5-8.
- a wireless device may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the wireless device may perform aspects the functions described below using special-purpose hardware.
- the method 1500 may also incorporate aspects of methods 1300 or 1400 of FIGs. 13 and 14.
- the wireless device may identify a redundancy version of a first CBC for reception during a TTI as described above with reference to FIGs. 2-4.
- the operations of block 1505 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may identify a version of a second CBC for reception during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1510 may be performed by the redundancy version module 605 as described above with reference to FIG. 6.
- the wireless device may receive a transport block that includes the redundancy version of the first CBC and the version of the second CBC during the TTI as described above with reference to FIGs. 2-4.
- the operations of block 1515 may be performed by the receiver 505 as described above with reference to FIG. 5.
- the wireless device may store a HARQ state corresponding to a set of received CBCs as described above with reference to FIGs. 2-4.
- the operations of block 1520 may be performed by the HARQ state module 715 as described above with reference to FIG. 7.
- the wireless device may update the HARQ state based at least in part on processing a CRC associated with one or more of the set of received CBCs as described above with reference to FIGs. 2-4.
- the operations of block 1525 may be performed by the HARQ state module 715 as described above with reference to FIG. 7.
- methods 1000, 1100, 1200, 1300, 1400, and 1500 may provide for CBC level HARQ. It should be noted that methods 1000, 1100, 1200, 1300, 1400, and 1500 describe possible implementation, and that the operations and the steps may be rearranged or otherwise modified such that other implementations are possible. In some examples, aspects from two or more of the methods 1000, 1100, 1200, 1300, 1400, and 1500 may be combined. [0148] The detailed description set forth above in connection with the appended drawings describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims.
- exemplary means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.”
- detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
- Information and signals may be represented using any of a variety of different technologies and techniques.
- data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
- a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
- 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).
- the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
- Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
- a non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
- non-transitory computer-readable media can comprise RAM, ROM, electrically erasable programmable read only memory (EEPROM), compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general- purpose or special-purpose computer, or a general-purpose or special-purpose processor.
- RAM random access memory
- ROM read only memory
- EEPROM electrically erasable programmable read only memory
- CD compact disk
- magnetic disk storage or other magnetic storage devices or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures
- any connection is properly termed a computer-readable medium.
- the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
- the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
- Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
- CDMA code division multiple access
- TDMA time division multiple access
- FDMA frequency division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc.
- CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
- IS- 2000 Releases 0 and A are commonly referred to as CDMA2000 IX, IX, etc.
- IS-856 (TIA- 856) is commonly referred to as CDMA2000 lxEV-DO, High Rate Packet Data (HRPD), etc.
- UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
- WCDMA Wideband CDMA
- a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM).
- GSM Global System for Mobile Communications
- An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc.
- UMB Ultra Mobile Broadband
- E-UTRA Evolved UTRA
- Wi-Fi Wi-Fi
- WiMAX IEEE 802.16
- IEEE 802.20 Flash-OFDM
- 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of Universal Mobile Telecommunications System (UMTS) that use E-UTRA.
- UTRA, E-UTRA, UMTS, LTE, LTE-A, and Global System for Mobile communications (GSM) are described in documents from an organization named "3rd Generation Partnership Project” (3 GPP).
- CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
- the techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020177021388A KR101964538B1 (en) | 2015-02-03 | 2015-12-11 | Code block cluster level harq |
CN201580075220.3A CN107210869B (en) | 2015-02-03 | 2015-12-11 | Apparatus and method for communicating at a wireless device |
JP2017540687A JP6563504B2 (en) | 2015-02-03 | 2015-12-11 | Code block cluster level HARQ |
BR112017016647A BR112017016647A2 (en) | 2015-02-03 | 2015-12-11 | code block cluster level harq |
EP15817721.2A EP3254394B1 (en) | 2015-02-03 | 2015-12-11 | Code block cluster level harq |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562111262P | 2015-02-03 | 2015-02-03 | |
US62/111,262 | 2015-02-03 | ||
US14/965,458 | 2015-12-10 | ||
US14/965,458 US9992004B2 (en) | 2015-02-03 | 2015-12-10 | Code block cluster level HARQ |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016126330A1 true WO2016126330A1 (en) | 2016-08-11 |
Family
ID=56554901
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2015/065337 WO2016126330A1 (en) | 2015-02-03 | 2015-12-11 | Code block cluster level harq |
Country Status (7)
Country | Link |
---|---|
US (1) | US9992004B2 (en) |
EP (1) | EP3254394B1 (en) |
JP (1) | JP6563504B2 (en) |
KR (1) | KR101964538B1 (en) |
CN (1) | CN107210869B (en) |
BR (1) | BR112017016647A2 (en) |
WO (1) | WO2016126330A1 (en) |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018053854A1 (en) | 2016-09-26 | 2018-03-29 | Nokia Technologies Oy | Error detection and channel coding of transport blocks |
WO2018054347A1 (en) * | 2016-09-22 | 2018-03-29 | Mediatek Inc. | Improved design for communication systems suffering burst error |
WO2018082661A1 (en) * | 2016-11-04 | 2018-05-11 | 华为技术有限公司 | Data transmission method and apparatus |
WO2018128363A1 (en) * | 2017-01-03 | 2018-07-12 | 엘지전자 주식회사 | Method for retransmitting punctured data and device therefor |
WO2018155820A1 (en) * | 2017-02-24 | 2018-08-30 | 엘지전자 주식회사 | Method for processing data block and method for harq ack/nack feedback |
WO2018175050A1 (en) * | 2017-03-23 | 2018-09-27 | Qualcomm Incorporated | Downlink retransmission under unreliable code block group (cbg) level ack/nack feedback |
WO2018171455A1 (en) * | 2017-03-23 | 2018-09-27 | 华为技术有限公司 | Method and device for sending feedback information |
WO2018203699A1 (en) * | 2017-05-04 | 2018-11-08 | 삼성전자 주식회사 | Method and apparatus for data transmission in wireless cellular communication system |
WO2018201352A1 (en) * | 2017-05-03 | 2018-11-08 | Oppo广东移动通信有限公司 | Data re-transmission control method and related product |
CN108809539A (en) * | 2017-05-04 | 2018-11-13 | 北京展讯高科通信技术有限公司 | Data repeating method and device, computer readable storage medium, transmitter |
KR20180122918A (en) * | 2017-05-04 | 2018-11-14 | 삼성전자주식회사 | Method and apparatus for data transmission in wirelss cellular communication system |
WO2019047232A1 (en) * | 2017-09-11 | 2019-03-14 | Nokia Solutions And Networks Oy | Method and apparatus for uplink transmission |
CN109792322A (en) * | 2016-08-12 | 2019-05-21 | 诺基亚通信公司 | For the fine granularity ACK/NACK feedback of 5G communication system |
WO2019099383A1 (en) * | 2017-11-15 | 2019-05-23 | Sharp Laboratories Of America, Inc. | Procedure, user equipment and base station for code block group based hybrid automatic repeat request process |
TWI670949B (en) * | 2017-05-05 | 2019-09-01 | 大陸商電信科學技術研究院有限公司 | Transmission method, terminal device and base station |
TWI675575B (en) * | 2017-05-05 | 2019-10-21 | 大陸商電信科學技術研究院有限公司 | Data transmission method, terminal and base station |
CN110402555A (en) * | 2017-03-15 | 2019-11-01 | 高通股份有限公司 | It is used for the group indicator of the re-transmission based on code block group in wireless communications |
JP2020504558A (en) * | 2017-01-07 | 2020-02-06 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | Data transmission method and equipment |
EP3484113A4 (en) * | 2016-07-08 | 2020-02-26 | Sharp Kabushiki Kaisha | Base station device, terminal device, communication method, and integrated circuit |
JP2020507266A (en) * | 2017-02-06 | 2020-03-05 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | Method for partial retransmission |
JP2020507238A (en) * | 2016-12-30 | 2020-03-05 | 華為技術有限公司Huawei Technologies Co.,Ltd. | Control information transmitting method and apparatus, and control information receiving method and apparatus |
US10805916B2 (en) | 2017-11-15 | 2020-10-13 | Sharp Laboratories Of America, Inc. | Procedure, user equipment and base station for code block group based hybrid automatic repeat request process |
CN112088509A (en) * | 2018-05-09 | 2020-12-15 | 高通股份有限公司 | Autonomous uplink transmission based on a group of code blocks |
US11705998B2 (en) | 2018-03-16 | 2023-07-18 | Qualcomm Incorporated | Repetition-based transmissions |
Families Citing this family (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11005616B2 (en) * | 2015-12-22 | 2021-05-11 | Sony Corporation | Dynamic coverage enhancement |
EP3398387B1 (en) * | 2015-12-30 | 2023-06-21 | InterDigital Patent Holdings, Inc. | Devices for wireless transmit/receive unit cooperation |
WO2017183896A1 (en) * | 2016-04-22 | 2017-10-26 | 엘지전자 주식회사 | Method for transmitting/receiving harq ack/nack signal in wireless communication system, and device therefor |
WO2018058294A1 (en) | 2016-09-27 | 2018-04-05 | Qualcomm Incorporated | Harq techniques for polar codes |
KR20180047886A (en) | 2016-11-01 | 2018-05-10 | 삼성전자주식회사 | Method and apparatus for data transmission in wirelss cellular communication system |
CN109863809B (en) | 2016-11-01 | 2022-04-08 | Lg电子株式会社 | Method for transmitting dynamically variable-size downlink control information in wireless communication system and apparatus therefor |
US20180145703A1 (en) * | 2016-11-23 | 2018-05-24 | Qualcomm Incorporated | Techniques for using a cyclic redundancy check in conjunction with a low-density parity-check encoding scheme |
CN108111262B (en) | 2016-11-25 | 2022-04-15 | 北京三星通信技术研究有限公司 | Method for hybrid automatic repeat request feedback and retransmission, receiver and transmitter |
US10492184B2 (en) * | 2016-12-09 | 2019-11-26 | Samsung Electronics Co., Ltd. | Multiplexing control information in a physical uplink data channel |
CN110073690B (en) * | 2016-12-14 | 2021-02-26 | Oppo广东移动通信有限公司 | Transmission method and device |
CN108270522B (en) | 2016-12-30 | 2022-04-29 | 中兴通讯股份有限公司 | Method and device for processing confirmation information |
CN115189816A (en) | 2017-01-04 | 2022-10-14 | Idac控股公司 | Receiver feedback in wireless systems |
JP6929945B2 (en) * | 2017-01-15 | 2021-09-01 | エルジー エレクトロニクス インコーポレイティド | A method of transmitting a HARQ-ACK signal in a wireless communication system and a device for that purpose. |
EP3571796A1 (en) | 2017-01-23 | 2019-11-27 | Sony Mobile Communications Inc. | Coverage enhancement and fast acknowledgement |
CN108347311B (en) | 2017-01-25 | 2021-05-11 | 华为技术有限公司 | Method for sending and receiving feedback information, access network equipment and terminal equipment |
CN110431875B (en) * | 2017-02-01 | 2023-04-25 | 株式会社Ntt都科摩 | User terminal and wireless communication method |
CN110915156B (en) * | 2017-02-06 | 2023-04-18 | 苹果公司 | Apparatus, method, and computer-readable storage medium for communication |
KR20180091527A (en) * | 2017-02-07 | 2018-08-16 | 삼성전자주식회사 | Method and apparatus for transmission and reception of control and data in wireless comunication system |
CN106954276B (en) * | 2017-03-07 | 2021-07-09 | 上海华为技术有限公司 | Method, device and system for retransmission scheduling |
JP6833971B2 (en) | 2017-03-08 | 2021-02-24 | エルジー エレクトロニクス インコーポレイティド | Radio signal transmission / reception methods and devices in wireless communication systems |
KR102002159B1 (en) | 2017-03-17 | 2019-07-19 | 엘지전자 주식회사 | Method and apparatus for receiving data performed by a user equipment in a wireless communication system |
US10834631B2 (en) * | 2017-03-23 | 2020-11-10 | Lg Electronics Inc. | Method and device for transmitting acknowledgement information by user equipment in wireless communication system |
WO2018170823A1 (en) * | 2017-03-23 | 2018-09-27 | Motorola Mobility Llc | An indication for harq-ack feedback |
US10567142B2 (en) * | 2017-03-23 | 2020-02-18 | Apple Inc. | Preemption indicators and code-block-group-based retransmission techniques for multiplexing different services on physical layer frames |
US10028210B1 (en) * | 2017-03-23 | 2018-07-17 | At&T Intellectual Property I, L.P. | Encoding and decoding data for group common control channels |
CN107070625A (en) * | 2017-03-24 | 2017-08-18 | 宇龙计算机通信科技(深圳)有限公司 | The distribution method and device of a kind of code block group in transmission block |
US11139923B2 (en) * | 2017-03-24 | 2021-10-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Code block groups for retransmissions in a wireless communication system |
US11171758B2 (en) * | 2017-03-24 | 2021-11-09 | Qualcomm Incorporated | Code block grouping and feedback that support efficient retransmissions |
US10749640B2 (en) | 2017-03-24 | 2020-08-18 | Electronics And Telecommunications Research Institute | Method and apparatus for transmitting and receiving uplink control channel in communication system |
US20180287752A1 (en) * | 2017-03-29 | 2018-10-04 | Kt Corporation | Method and apparatus for configuring transport block to transmit data |
US10389481B2 (en) * | 2017-03-31 | 2019-08-20 | Cavium, Llc | Methods and apparatus for calculating transport block (TB) cyclic redundancy ceck (CRC) values |
KR102283945B1 (en) | 2017-04-03 | 2021-07-30 | 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) | HARQ handling for nodes with variable processing times |
US10727987B2 (en) * | 2017-04-03 | 2020-07-28 | Qualcomm Incorporated | Feedback for codeblock group based transmissions |
US20180316477A1 (en) * | 2017-04-26 | 2018-11-01 | Qualcomm Incorporated | Group acknowledgment and/or negative acknowledgment in wireless communication systems |
WO2018198363A1 (en) * | 2017-04-28 | 2018-11-01 | 富士通株式会社 | Base station device, terminal device, wireless communication system and communication method |
RU2742284C1 (en) * | 2017-05-02 | 2021-02-04 | Нтт Докомо, Инк. | User terminal and method of radio communication |
US10608790B2 (en) | 2017-05-04 | 2020-03-31 | At&T Intellectual Property I, L.P. | Data transmission with code block segmentation for 5G systems |
CN114826490B (en) * | 2017-05-05 | 2024-06-21 | 北京三星通信技术研究有限公司 | Scheduling method, HARQ-ACK feedback method and corresponding equipment |
CN108809534B (en) * | 2017-05-05 | 2022-07-01 | 北京三星通信技术研究有限公司 | Scheduling method, HARQ-ACK feedback method and corresponding equipment |
JP2019004245A (en) * | 2017-06-13 | 2019-01-10 | シャープ株式会社 | Terminal device, base station device, and communication method |
KR102251634B1 (en) | 2017-06-15 | 2021-05-13 | 후지쯔 가부시끼가이샤 | Base station apparatus, terminal apparatus, wireless communication system, and communication method |
KR102366376B1 (en) * | 2017-06-15 | 2022-02-23 | 삼성전자 주식회사 | Method and apparatus for header processing in mac layer |
CN109150419B (en) * | 2017-06-16 | 2021-09-07 | 华为技术有限公司 | Communication method and device thereof |
US10454620B2 (en) | 2017-06-16 | 2019-10-22 | At&T Intellectual Property I, L.P. | Facilitating notifications to indicate failed code block groups in 5G or other next generation networks |
CN107359970A (en) * | 2017-06-16 | 2017-11-17 | 宇龙计算机通信科技(深圳)有限公司 | Hybrid automatic repeat-request feedback method and relevant apparatus |
CN108111263B (en) * | 2017-06-16 | 2023-02-07 | 中兴通讯股份有限公司 | Feedback method and device of confirmation information and receiving method and device of confirmation information |
JP2019004362A (en) * | 2017-06-16 | 2019-01-10 | シャープ株式会社 | Terminal device, base station device, and communication method |
WO2018229657A1 (en) * | 2017-06-16 | 2018-12-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatuses and methods for handling of data radio bearer integrity protection failure in new radio (nr) network |
US10420089B2 (en) | 2017-08-10 | 2019-09-17 | At&T Intellectual Property I, L.P. | Adaptive two-stage downlink control channel structure for code block group based fifth generation (5G) or other next generation systems |
US10554345B2 (en) | 2017-08-10 | 2020-02-04 | At&T Intellectual Property I, L.P. | Indicating retransmitted codeblock groups in 5G wireless communication systems |
WO2019134152A1 (en) | 2018-01-06 | 2019-07-11 | 南通朗恒通信技术有限公司 | Method and device used in communication node of wireless communication |
US11374694B2 (en) * | 2018-01-17 | 2022-06-28 | Qualcomm Incorporated | Transport block size indication for retransmissions in wireless communications |
US10925087B2 (en) * | 2018-03-20 | 2021-02-16 | Qualcomm Incorporated | Methods and apparatuses for communications of a flexible transport block |
BR112020015861A2 (en) * | 2018-08-29 | 2021-03-09 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | WIRELESS COMMUNICATION METHOD, COMMUNICATIONS DEVICE, CHIP AND LEGIBLE STORAGE MEDIA BY COMPUTER |
CA3119325C (en) | 2018-11-27 | 2023-07-04 | XCOM Labs, Inc. | Non-coherent cooperative multiple-input multiple-output communications |
EP3928449A1 (en) | 2019-02-19 | 2021-12-29 | Telefonaktiebolaget LM Ericsson (publ) | Code block header for fast rlc pdu deliveries in 5g nr |
WO2020222446A1 (en) * | 2019-04-29 | 2020-11-05 | 엘지전자 주식회사 | Nack frame for harq operation |
US11083005B2 (en) * | 2019-07-11 | 2021-08-03 | Rohde & Schwarz Gmbh & Co. Kg | Method for reporting scheduling decisions by a communication tester |
CN114175541A (en) * | 2019-07-17 | 2022-03-11 | 上海诺基亚贝尔股份有限公司 | Integrated signaling of HARQ acknowledgements |
WO2021030947A1 (en) * | 2019-08-16 | 2021-02-25 | Qualcomm Incorporated | Bundling and timeline determination for multiple transport blocks scheduled by a single downlink control information message |
US12016027B2 (en) * | 2020-02-25 | 2024-06-18 | Qualcomm Incorporated | Consolidated feedback indication and feedback transmission |
CA3178604A1 (en) | 2020-05-26 | 2021-12-02 | XCOM Labs, Inc. | Interference-aware beamforming |
WO2022093988A1 (en) | 2020-10-30 | 2022-05-05 | XCOM Labs, Inc. | Clustering and/or rate selection in multiple-input multiple-output communication systems |
US11909483B2 (en) * | 2021-09-07 | 2024-02-20 | Qualcomm Incorporated | CSI based on code block segmentation |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009126902A2 (en) * | 2008-04-11 | 2009-10-15 | Interdigital Patent Holdings, Inc. | Methods for transmission time interval bundling in the uplink |
US20100278093A1 (en) * | 2009-05-04 | 2010-11-04 | Industrial Technology Research Institute | Method and Apparatus for Multicast and Broadcast Retransmission in Wireless Communication Systems |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4330767B2 (en) * | 2000-06-26 | 2009-09-16 | 株式会社エヌ・ティ・ティ・ドコモ | Communication method and base station apparatus performing automatic retransmission request |
KR100459557B1 (en) * | 2001-08-23 | 2004-12-03 | 삼성전자주식회사 | Method for allocating hybrid automatic retransmission request channel number for indicating state information of data in high speed downlink packet access communication system |
TW200729815A (en) * | 2005-12-29 | 2007-08-01 | Interdigital Tech Corp | Method and system for implementing H-ARQ-assisted ARQ operation |
US20090077444A1 (en) * | 2007-09-17 | 2009-03-19 | Nokia Corporation | Method and apparatus for providing acknowledgement signaling to support an error control mechanism |
WO2009145474A2 (en) * | 2008-04-02 | 2009-12-03 | 엘지전자주식회사 | Method for conducting harq with a wireless communications system |
WO2010005712A1 (en) * | 2008-06-16 | 2010-01-14 | Interdigital Patent Holdings, Inc. | Enhanced hybrid automatic repeat request for long term evolution |
CA2727948A1 (en) * | 2008-06-19 | 2009-12-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus in a telecommunications network |
JP2010093449A (en) * | 2008-10-06 | 2010-04-22 | Sharp Corp | Transmission device, reception device, communication method, and communication system |
EP2413627A4 (en) | 2009-03-25 | 2015-01-21 | Fujitsu Ltd | Radio communication system, mobile station device, base station device, and radio communication method in the radio communication system |
WO2010113214A1 (en) * | 2009-03-31 | 2010-10-07 | 富士通株式会社 | Communication method, communication system, communication terminal device, and communication base station device |
JP2011003975A (en) * | 2009-06-16 | 2011-01-06 | Sharp Corp | Error correction encoding apparatus and error correction decoding apparatus |
US20130343273A1 (en) * | 2012-06-26 | 2013-12-26 | Qualcomm Incorporated | Enhanced tti bundling with flexible harq merging |
US10791546B2 (en) * | 2014-11-07 | 2020-09-29 | Qualcomm Incorporated | PUCCH for MTC devices |
-
2015
- 2015-12-10 US US14/965,458 patent/US9992004B2/en active Active
- 2015-12-11 KR KR1020177021388A patent/KR101964538B1/en active IP Right Grant
- 2015-12-11 JP JP2017540687A patent/JP6563504B2/en not_active Expired - Fee Related
- 2015-12-11 WO PCT/US2015/065337 patent/WO2016126330A1/en active Application Filing
- 2015-12-11 BR BR112017016647A patent/BR112017016647A2/en not_active IP Right Cessation
- 2015-12-11 CN CN201580075220.3A patent/CN107210869B/en active Active
- 2015-12-11 EP EP15817721.2A patent/EP3254394B1/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009126902A2 (en) * | 2008-04-11 | 2009-10-15 | Interdigital Patent Holdings, Inc. | Methods for transmission time interval bundling in the uplink |
US20100278093A1 (en) * | 2009-05-04 | 2010-11-04 | Industrial Technology Research Institute | Method and Apparatus for Multicast and Broadcast Retransmission in Wireless Communication Systems |
Cited By (61)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3484113A4 (en) * | 2016-07-08 | 2020-02-26 | Sharp Kabushiki Kaisha | Base station device, terminal device, communication method, and integrated circuit |
US11362764B2 (en) | 2016-07-08 | 2022-06-14 | FG Innovation Company Limited | Base station apparatus, terminal apparatus, communication method, and integrated circuit |
CN109792322A (en) * | 2016-08-12 | 2019-05-21 | 诺基亚通信公司 | For the fine granularity ACK/NACK feedback of 5G communication system |
CN109792322B (en) * | 2016-08-12 | 2022-05-24 | 诺基亚通信公司 | Method of communication, computer readable medium and apparatus for communication |
WO2018054347A1 (en) * | 2016-09-22 | 2018-03-29 | Mediatek Inc. | Improved design for communication systems suffering burst error |
CN109792334A (en) * | 2016-09-22 | 2019-05-21 | 联发科技股份有限公司 | By the Curve guide impeller of the communication system of burst error |
CN109804577B (en) * | 2016-09-26 | 2021-09-14 | 诺基亚技术有限公司 | Method and apparatus for error detection and channel coding of transport blocks |
CN109804577A (en) * | 2016-09-26 | 2019-05-24 | 诺基亚技术有限公司 | The error detection and channel coding of transmission block |
US11070315B2 (en) | 2016-09-26 | 2021-07-20 | Nokia Technologies Oy | Error detection and channel coding of transport blocks |
EP3516804A4 (en) * | 2016-09-26 | 2020-05-20 | Nokia Technologies Oy | Error detection and channel coding of transport blocks |
WO2018053854A1 (en) | 2016-09-26 | 2018-03-29 | Nokia Technologies Oy | Error detection and channel coding of transport blocks |
US11533717B2 (en) | 2016-11-04 | 2022-12-20 | Huawei Technologies Co., Ltd. | Data transmission method and apparatus |
US10856286B2 (en) | 2016-11-04 | 2020-12-01 | Huawei Technologies Co., Ltd. | Data transmission method and apparatus |
WO2018082661A1 (en) * | 2016-11-04 | 2018-05-11 | 华为技术有限公司 | Data transmission method and apparatus |
JP2019534647A (en) * | 2016-11-04 | 2019-11-28 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | Data transmission method and data transmission apparatus |
CN108023721A (en) * | 2016-11-04 | 2018-05-11 | 华为技术有限公司 | A kind of data transmission method and device |
CN108023721B (en) * | 2016-11-04 | 2021-02-09 | 华为技术有限公司 | Data transmission method and device |
EP3537644A4 (en) * | 2016-11-04 | 2019-11-20 | Huawei Technologies Co., Ltd. | Data transmission method and apparatus |
JP2020507238A (en) * | 2016-12-30 | 2020-03-05 | 華為技術有限公司Huawei Technologies Co.,Ltd. | Control information transmitting method and apparatus, and control information receiving method and apparatus |
US11012192B2 (en) | 2016-12-30 | 2021-05-18 | Huawei Technologies Co., Ltd. | Control information sending method and apparatus, and control information receiving method and apparatus |
US10897325B2 (en) | 2017-01-03 | 2021-01-19 | Lg Electronics Inc. | Method for retransmitting punctured data and device therefor |
WO2018128363A1 (en) * | 2017-01-03 | 2018-07-12 | 엘지전자 주식회사 | Method for retransmitting punctured data and device therefor |
US10897331B2 (en) | 2017-01-07 | 2021-01-19 | Huawei Technologies Co., Ltd. | Data transmission method and apparatus |
JP2020504558A (en) * | 2017-01-07 | 2020-02-06 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | Data transmission method and equipment |
US11581987B2 (en) | 2017-01-07 | 2023-02-14 | Huawei Technologies Co., Ltd. | Data transmission method and apparatus |
US11283554B2 (en) | 2017-02-06 | 2022-03-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for partial retransmission |
US11838130B2 (en) | 2017-02-06 | 2023-12-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for partial retransmission |
JP2020507266A (en) * | 2017-02-06 | 2020-03-05 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | Method for partial retransmission |
US11290911B2 (en) | 2017-02-24 | 2022-03-29 | Lg Electronics Inc. | Method for processing data block and method for HARQ ACK/NACK feedback |
WO2018155820A1 (en) * | 2017-02-24 | 2018-08-30 | 엘지전자 주식회사 | Method for processing data block and method for harq ack/nack feedback |
CN110402555A (en) * | 2017-03-15 | 2019-11-01 | 高通股份有限公司 | It is used for the group indicator of the re-transmission based on code block group in wireless communications |
CN110402555B (en) * | 2017-03-15 | 2022-01-04 | 高通股份有限公司 | Group indicator for code block group based retransmission in wireless communications |
US12009935B2 (en) | 2017-03-23 | 2024-06-11 | Huawei Technologies Co., Ltd. | Feedback information sending method and device |
CN110447191A (en) * | 2017-03-23 | 2019-11-12 | 高通股份有限公司 | Downlink retransmission under unreliable code block group (CBG) rank ACK/NACK feedback |
US11303396B2 (en) | 2017-03-23 | 2022-04-12 | Huawei Technologies Co., Ltd. | Feedback information sending method and device |
US10484146B2 (en) | 2017-03-23 | 2019-11-19 | Qualcomm Incorporated | Downlink retransmission under unreliable code block group (CBG) level ACK/NACK feedback |
US10999017B2 (en) | 2017-03-23 | 2021-05-04 | Qualcomm Incorporated | Downlink retransmission under unreliable code block group (CBG) level ACK/NACK feedback |
WO2018175050A1 (en) * | 2017-03-23 | 2018-09-27 | Qualcomm Incorporated | Downlink retransmission under unreliable code block group (cbg) level ack/nack feedback |
WO2018171455A1 (en) * | 2017-03-23 | 2018-09-27 | 华为技术有限公司 | Method and device for sending feedback information |
CN110447191B (en) * | 2017-03-23 | 2022-08-12 | 高通股份有限公司 | Downlink retransmission under unreliable block group (CBG) level ACK/NACK feedback |
US11791952B2 (en) | 2017-05-03 | 2023-10-17 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Data re-transmission control method and related product |
AU2017412432B2 (en) * | 2017-05-03 | 2022-07-07 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Data re-transmission control method and related product |
WO2018201352A1 (en) * | 2017-05-03 | 2018-11-08 | Oppo广东移动通信有限公司 | Data re-transmission control method and related product |
RU2736825C1 (en) * | 2017-05-03 | 2020-11-20 | Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. | Data relay control method and related product |
KR20180122918A (en) * | 2017-05-04 | 2018-11-14 | 삼성전자주식회사 | Method and apparatus for data transmission in wirelss cellular communication system |
KR102472160B1 (en) * | 2017-05-04 | 2022-11-30 | 삼성전자 주식회사 | Method and apparatus for data transmission in wirelss cellular communication system |
CN108809539A (en) * | 2017-05-04 | 2018-11-13 | 北京展讯高科通信技术有限公司 | Data repeating method and device, computer readable storage medium, transmitter |
US11223450B2 (en) | 2017-05-04 | 2022-01-11 | Samsung Electronics Co., Ltd | Method and apparatus for data transmission in wireless cellular communication system |
CN108809539B (en) * | 2017-05-04 | 2021-04-27 | 北京紫光展锐通信技术有限公司 | Data retransmission method and device, computer readable storage medium and transmitter |
WO2018203699A1 (en) * | 2017-05-04 | 2018-11-08 | 삼성전자 주식회사 | Method and apparatus for data transmission in wireless cellular communication system |
US11057923B2 (en) | 2017-05-05 | 2021-07-06 | China Academy Of Telecommunications Technology | Transmission method, terminal device and base station |
TWI670949B (en) * | 2017-05-05 | 2019-09-01 | 大陸商電信科學技術研究院有限公司 | Transmission method, terminal device and base station |
US11166284B2 (en) | 2017-05-05 | 2021-11-02 | Datang Mobile Communications Equipment Co., Ltd. | Data transmission method, terminal, and base station |
TWI675575B (en) * | 2017-05-05 | 2019-10-21 | 大陸商電信科學技術研究院有限公司 | Data transmission method, terminal and base station |
WO2019047232A1 (en) * | 2017-09-11 | 2019-03-14 | Nokia Solutions And Networks Oy | Method and apparatus for uplink transmission |
US11394504B2 (en) | 2017-09-11 | 2022-07-19 | Nokia Technologies Oy | Method and apparatus for uplink transmission |
WO2019099383A1 (en) * | 2017-11-15 | 2019-05-23 | Sharp Laboratories Of America, Inc. | Procedure, user equipment and base station for code block group based hybrid automatic repeat request process |
US10805916B2 (en) | 2017-11-15 | 2020-10-13 | Sharp Laboratories Of America, Inc. | Procedure, user equipment and base station for code block group based hybrid automatic repeat request process |
US11705998B2 (en) | 2018-03-16 | 2023-07-18 | Qualcomm Incorporated | Repetition-based transmissions |
US11800516B2 (en) | 2018-05-09 | 2023-10-24 | Qualcomm Incorporated | Code block group-based autonomous uplink transmission |
CN112088509A (en) * | 2018-05-09 | 2020-12-15 | 高通股份有限公司 | Autonomous uplink transmission based on a group of code blocks |
Also Published As
Publication number | Publication date |
---|---|
KR20170115524A (en) | 2017-10-17 |
US20160226643A1 (en) | 2016-08-04 |
JP2018507636A (en) | 2018-03-15 |
EP3254394A1 (en) | 2017-12-13 |
CN107210869B (en) | 2020-08-28 |
US9992004B2 (en) | 2018-06-05 |
BR112017016647A2 (en) | 2018-04-03 |
CN107210869A (en) | 2017-09-26 |
EP3254394B1 (en) | 2022-11-09 |
KR101964538B1 (en) | 2019-04-01 |
JP6563504B2 (en) | 2019-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3254394B1 (en) | Code block cluster level harq | |
US20200322941A1 (en) | Multiple tri-state harq processes | |
US20230040839A1 (en) | Fountain harq for reliable low latency communication | |
CN109417449B (en) | Hybrid automatic repeat request feedback and multiple transmission time interval scheduling | |
US10270579B2 (en) | Efficient ACK/NACK transmission | |
CN110447198B (en) | Downlink and uplink transmissions for high reliability low latency communication systems | |
US10355828B2 (en) | Fast radio link control error recovery with low latency transmissions | |
EP3248319A1 (en) | Event triggered multi-link channel quality measurement and report for mission critical applications | |
WO2016209599A1 (en) | Soft hybrid automatic repeat request |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15817721 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2015817721 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20177021388 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2017540687 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112017016647 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112017016647 Country of ref document: BR Kind code of ref document: A2 Effective date: 20170802 |