TWI693803B - Group acknowledgement/negative acknowledgement and triggering gack/channel state information - Google Patents

Abstract

According to the present disclosure, CSI and/or a plurality of ACKs related to a group of DL data transmissions may be buffered at the UE as a GACK until a DCI trigger is received from the eNB. Once the trigger is received, the UE may transmit the CSI and/or GACK to the eNB. In this way HARQ feedback and/or CSI may be reliably communicated while reducing payload. In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus send, to a UE, data transmissions associated with a first plurality of downlink subframes. In an aspect, the apparatus increments a counter for each data transmission sent to the UE. In a further aspect, the apparatus transmits, to the UE, a first trigger for a first GACK when a counter is greater than or equal to a threshold.

Description

Group confirmation/negative confirmation and trigger group confirmation/negative confirmation/channel status information Cross-reference of related applications

This application claims the rights and interests of "GROUP ACKNOWLEDGEMENT/NEGATIVE ACKNOWLEDGEMENT (GACK) AND TRIGGERING GACK/CHANNEL STATE INFORMATION (CSI)", which was filed on January 27, 2015 in U.S. Provisional Application No. 62/108,487 The entire contents of the provisional application are expressly incorporated by reference.

The present invention relates generally to communication systems and, more specifically, to response/negative response handling and triggering of response/negative responses or channel status information (CSI) reports.

Wireless communication systems are widely deployed to provide various telecommunications services, such as telephone, video, data, messaging, and broadcasting. A typical wireless communication system may use multiple access technologies that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems , Single carrier frequency division multiple access (SC-FDMA) system and time division synchronous code division multiple access (TD-SCDMA) system.

These multiple access technologies have been adopted in various telecommunication standards to provide a common agreement that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunications standard is Long Term Evolution (LTE). LTE is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) action standard announced by the Third Generation Partnership Project (3GPP). LTE is designed to support mobile broadband access using OFDMA on the downlink, SC-FDMA on the uplink, and multiple input multiple output (MIMO) antenna technology, with improved spectrum efficiency, reduced costs, and improved services. However, as the demand for mobile broadband access continues to increase, there is a need for further improvements in LTE technology. These improvements can also be applied to other multiple access technologies and telecommunication standards that use these technologies.

Use in advanced communications that use licensed spectrum (eg, LTE-A) or unlicensed spectrum for listen-to-be-forwarded (LBT) frames (eg, licensed assisted access (LAA) and/or MuLTEfire). Conventional methods for transmitting hybrid automatic repeat request (HARQ) feedback and/or CSI from user equipment (UE) to a base station (eNB) may be unreliable and have an inappropriate payload size.

The following presents a simplified overview of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all expected aspects, and neither intends to identify important or critical elements of all aspects nor to delineate any or all aspects. The sole purpose of this summary is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In advanced communication, using licensed or unlicensed spectrum, downlink (DL) HARQ feedback can be transmitted from the UE to the eNB in a predetermined uplink (UL) subframe. The UE may send the CSI to the eNB in periodic or aperiodic reports. However, if the Clear Channel Assessment (CCA) is not cleared or no UL subframe is available, it may be unreliable to transmit HARQ feedback and/or CSI in this way. In addition, aperiodic CSI reports (A-CSI) can include a large payload, and therefore, sending large A-CSI reports can be unreliable.

In the present invention, CSI and/or multiple acknowledgments/negative acknowledgments (ACK/NACK) related to DL data transmission from a group of eNBs can be buffered at the UE as group acknowledgments/negative acknowledgments (GACK) Until the downlink control information (DCI) trigger procedure is received from the eNB. Once the DCI trigger procedure is received, the UE can transmit CSI and/or GACK to the eNB. In this way, HARQ feedback and/or CSI can be reliably communicated while reducing the payload.

In the aspect of the present invention, a method, a computer-readable medium, and a device are provided. The device may include a base station. In an aspect, the device sends data transmissions associated with the first plurality of downlink subframes to the UE. In another aspect, the device increments the counter for each data transmission sent to the UE that is associated with the first plurality of downlink subframes. In other aspects, when the counter is greater than or equal to the threshold, the device transmits the first trigger procedure for the first GACK to the UE. For example, the first trigger procedure may include a first tag and the first GACK may be an ACK for data transmission received by the UE.

In the aspect of the present invention, a method, a computer-readable medium, and a device are provided. The device may include a UE. The device stores the ACK/NACK of the first group. The ACK/NACK of the first group corresponds to the first data transmission group received in the first plurality of downlink subframes from the base station. In another aspect, the device receives the first trigger procedure for sending the first GACK from the base station. For example, the first trigger procedure may include a first tag. In other aspects, when the first label does not correspond to the UE label, the device transmits the first GACK including at least the ACK/NACK of the first group to the base station.

In the aspect of the present invention, a method, a computer-readable medium, and a device are provided. The device may include a UE. In the aspect, the device generates uplink control information (UCI). For example, UCI may include GACK, rank indicator (RI), and CSI transmission. In another aspect, the device may send a UCI transmission in the LBT sub-frame. For example, the device may generate UCI by separately encoding and multiplexing GACK, RI, and CSI when sending UCI transmissions in the enhanced physical uplink shared channel (ePUSCH). In another example, the device may be When UCI transmissions are sent in the enhanced entity uplink control channel (ePUCCH), GACK, RI, and CSI are jointly encoded to generate UCI.

In order to achieve the aforementioned and related objectives, one or more aspects include the features fully described below and specifically pointed out in the scope of the patent application. The following description and drawings illustrate some illustrative features of one or more aspects in detail. However, these features only indicate a few of the various ways in which the principles of various aspects can be used, and this description is intended to include all such aspects and their equivalents.

100‧‧‧Access network

102‧‧‧ base station

102'‧‧‧Small community

104‧‧‧User equipment

110‧‧‧ Geographically Covered Area

110'‧‧‧ Covered area

120‧‧‧Communication link

132‧‧‧Backhaul link

134‧‧‧ Backhaul link

150‧‧‧Wi-Fi access point

152‧‧‧Wi-Fi station

154‧‧‧Communication link

160‧‧‧Evolved packet core

162‧‧‧ mobile management entity

164‧‧‧ mobile management entity

166‧‧‧Servo gateway

168‧‧‧Multimedia Broadcast Multicast Servo Gateway

170‧‧‧Broadcast Multicast Service Center

172‧‧‧Packet data network gateway

174‧‧‧Home user server

176‧‧‧Internet Protocol Service

198‧‧‧Trigger

200‧‧‧ Downlink frame structure

230‧‧‧ Channel

250‧‧‧ Uplink frame structure

280‧‧‧channel

310‧‧‧eNB

316‧‧‧Transmission processor

318RX‧‧‧Receiver

318TX‧‧‧Transmitter

320‧‧‧ Antenna

350‧‧‧User equipment

352‧‧‧ Antenna

354RX‧‧‧Receiver

354TX‧‧‧Transmitter

356‧‧‧Receiving processor

358‧‧‧ Channel Estimator

359‧‧‧Controller/processor

360‧‧‧Memory

368‧‧‧Transmission processor

370‧‧‧ Receive processor

374‧‧‧ Channel Estimator

375‧‧‧Controller/processor

376‧‧‧Memory

700‧‧‧Picture

702‧‧‧Community

704‧‧‧eNB

706‧‧‧frame

708‧‧‧User equipment

710‧‧‧Data transmission

710'‧‧‧signal

710"‧‧‧signal

712‧‧‧Counter

714‧‧‧Counter

716‧‧‧The first group response/negative response

718‧‧‧Trigger

718'‧‧‧signal

718"‧‧‧signal

720‧‧‧User equipment label

722‧‧‧User equipment label

724‧‧‧Group answer/negative answer

724'‧‧‧signal

724"‧‧‧signal

726‧‧‧ Error detection test

728‧‧‧New eNB tag

730‧‧‧Send

732‧‧‧Enhanced physical downlink shared channel scheduler/transmitter

734‧‧‧Enhanced physical downlink shared channel receiver

736‧‧‧Enhanced physical downlink control channel receiver

738‧‧‧Group answer/negative answer receiver/transmitter

740‧‧‧Enhanced physical uplink control channel transmitter

742‧‧‧HARQsSinceTrig

744‧‧‧ACKsSinceTrig

748‧‧‧ACKsTillTrig

750‧‧‧UETag

752‧‧‧Enhanced physical downlink control channel scheduler/transmitter

754‧‧‧Group answer/negative trigger/receiver

756‧‧‧Enhanced physical uplink control channel receiver

758‧‧‧ Hybrid automatic repeat request manager

760‧‧‧PendingAcksSinceTrig

762‧‧‧PendingACKsTillTrig

764‧‧‧eNBTag

766‧‧‧Information

770‧‧‧Signal

772‧‧‧Signal

774‧‧‧ Group answer/negative answer procedure

776‧‧‧Counter

778‧‧‧Signal

780‧‧‧buffer

800‧‧‧Picture

802‧‧‧frame

802'‧‧‧frame

900‧‧‧Picture

902‧‧‧frame

902'‧‧‧frame

1000‧‧‧Flowchart

1100‧‧‧Flowchart

1200‧‧‧Flowchart

1300‧‧‧Flowchart

1400‧‧‧Data flow chart

1402‧‧‧device

1402'‧‧‧ device

1404‧‧‧Receiving module

1406‧‧‧Monitoring module

1408‧‧‧Error detection module

1410‧‧‧Generation component

1412‧‧‧Reset components

1414‧‧‧Incremental components

1416‧‧‧Avoid components

1418‧‧‧Transmission components

1420‧‧‧Signal

1422‧‧‧Signal

1424‧‧‧Signal

1426‧‧‧Signal

1428‧‧‧Signal

1430‧‧‧Signal

1432‧‧‧Signal

1434‧‧‧Signal

1436‧‧‧Signal

1450‧‧‧User equipment

1500‧‧‧Data flow chart

1504‧‧‧ processor

1506‧‧‧ Computer readable media/memory

1510‧‧‧Transceiver

1520‧‧‧ Antenna

1524‧‧‧Bus

1600‧‧‧Data flow chart

1602‧‧‧ device

1602'‧‧‧ device

1604‧‧‧Receiving module

1606‧‧‧Storage unit

1608‧‧‧Modified components

1610‧‧‧Clear component

1612‧‧‧Transmission components

1614‧‧‧Signal

1616‧‧‧Signal

1618‧‧‧Signal

1620‧‧‧Signal

1622‧‧‧Signal

1650‧‧‧eNB/base station

1700‧‧‧Picture

1704‧‧‧ processor

1706‧‧‧ Computer readable media/memory

1710‧‧‧Transceiver

1720‧‧‧ Antenna

1724‧‧‧Bus

FIG. 1 is a diagram illustrating an example of a wireless communication system and access network.

2A, 2B, 2C, and 2D are diagrams illustrating an LTE example of a DL frame structure, a DL channel in a DL frame structure, a UL frame structure, and a UL channel in a UL frame structure, respectively.

FIG. 3 is a diagram illustrating an example of an evolved Node B (eNB) and user equipment (UE) in an access network.

4A and 4B are the first diagrams illustrating an exemplary embodiment associated with triggering GACK, CSI, and/or UCI.

FIG. 5 is a second diagram for explaining an exemplary embodiment associated with triggering GACK.

FIG. 6 is a third diagram for explaining an exemplary embodiment associated with triggering GACK.

7A, 7B, and 7C are flowcharts 1000 of a method of wireless communication according to various aspects.

8 is a flowchart 1100 of a method of wireless communication according to various aspects.

9 is a flowchart 1200 of a method of wireless communication according to various aspects.

FIG. 10 is a flowchart 1300 of a method of wireless communication according to various aspects.

11 is a conceptual data flow diagram illustrating the data flow between different components/components in an exemplary system.

12 is a diagram illustrating an example of hardware implementation of a device using a processing system.

13 is a conceptual data flow diagram illustrating the data flow between different components/components in an exemplary device.

14 is a diagram illustrating an example of hardware implementation of a device using a processing system.

The detailed description set forth below in conjunction with the drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, those skilled in the art will understand that these concepts can be practiced without such specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring these concepts.

Several aspects of the telecommunications system will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the drawings by various blocks, components, circuits, programs, algorithms, etc. (collectively referred to as "elements"). These components can be implemented using electronic hardware, computer software, or any combination thereof. Whether these components are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element or any combination of elements, can be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems Single chip (SoC), baseband processor, field programmable gate array (FPGA), programmable logic device (PLD), state machine, gate control logic, discrete hardware circuit and configured to perform the invention Other functionalities described for other suitable hardware. One or more processors in the processing system can execute software. Whether it is called software, firmware, middleware, microcode, hardware description language, or other, software should be interpreted broadly to mean instructions, instruction sets, codes, code segments, code, programs, subprograms, software components, Application, software application, software package, routine, subroutine, object, executable file, thread, procedure, function Style.

Therefore, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. The storage medium can be any available medium that can be accessed by the computer. By way of example and not limitation, these computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage , Disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store computer-executable program code in the form of instructions or data structures accessible by the computer.

FIG. 1 is a diagram illustrating an example of a wireless communication system and an access network 100. A wireless communication system (also called a wireless wide area network (WWAN)) includes a base station 102, a UE 104, and an evolved packet core (EPC) 160. The base station 102 may include a giant cell (high-power cellular base station) and/or a small cell (low-power cellular base station). Mega cells include eNB. Small cells include ultra-micro cells, pico cells, and micro cells.

The base station 102 (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) interfaces with the EPC 160 via a backhaul link 132 (eg, S1 interface). Among other functions, the base station 102 can perform one or more of the following functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, and mobility control functions (eg, delivery, dual Connectivity), inter-cell interference coordination, connection establishment and release, load balancing, non-access layer (NAS) message distribution, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast Service (MBMS), user and device tracking, RAN information management (RIM), paging, location and warning message delivery. The base stations 102 can communicate with each other directly or indirectly (eg, through the EPC 160) via the backhaul link 134 (eg, X2 interface). The backhaul link 134 may be wired or wireless.

The base station 102 can communicate with the UE 104 in a wireless manner. Each of the base stations 102 can provide communication coverage for respective geographic coverage areas 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more giant base stations 102. A network including both small cells and mega cells can be called a heterogeneous network. The heterogeneous network may also include a Home Evolution Node B (eNB) (HeNB), which may serve a restricted group called a closed user group (CSG). The communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also known as reverse link) transmission from the UE 104 to the base station 102 and/or from the base station 102 to the UE 104 Downlink (DL) (also known as forward link) transmission. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmission diversity. The communication link may be through one or more carriers. The base station 102/UE 104 can use a frequency spectrum of up to Y MHz (eg, 5MHz, 10MHz, 15MHz, 20MHz) per carrier, which is allocated to up to a total of Yx MHz ( x component carriers) for transmission in each direction ) Carrier summary. The carriers may or may not be adjacent to each other. For DL and UL, the allocation of carriers may be asymmetric (eg, the carriers allocated for DL may be more or less than those allocated for UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be called a primary cell (PCell) and the secondary component carrier may be called a secondary cell (SCell).

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

The small cell 102' may operate in a licensed frequency spectrum and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may use LTE and use the same 5GHz unlicensed frequency spectrum as the Wi-Fi AP 150. Using a small cell 102' of LTE in an unlicensed frequency spectrum can increase the coverage of the access network and/or increase the capacity of the access network. LTE in unlicensed spectrum can be called unlicensed LTE (LTE-U), licensed assisted access (LAA) or MuLTEfire.

The EPC 160 may include a mobile management entity (MME) 162, other MME 164, a server gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and packet data Network (PDN) gateway 172. The MME 162 can communicate with the home subscriber server (HSS) 174. The MME 162 is a control node that handles communication between the UE 104 and the EPC 160. In general, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the servo gateway 166, which is itself connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP service 176. The IP service 176 may include the Internet, Intranet, IP Multimedia Subsystem (IMS), PS Streaming Service (PSS), and/or other IP services. BM-SC 170 can provide functions for MBMS user service provisioning and delivery. BM-SC 170 can be used as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS bearer services within the Public Land Mobile Network (PLMN), and can be used for scheduled MBMS transmission. The MBMS gateway 168 can be used to distribute MBMS traffic to base stations 102 that belong to the Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts specific services, and can be responsible for session management (start/stop) and collect information about eMBMS. Billing information.

The base station can also be called Node B, Evolved Node B (eNB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS) Or some other suitable term. The base station 102 provides the access point for the UE 104 to the EPC 160. Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio Player (for example, MP3 player), camera, game console, tablet computer, smart device, wearable device or any other similar functional device. UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile Device, wireless device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, user terminal or a certain Other suitable terms.

Referring again to FIG. 1, in some aspects, the UE 104 may be configured to transmit GACK, CSI, and/or UCI to the base station 102 when the trigger procedure (198) is received.

2A is a diagram 200 illustrating an example of a DL frame structure in LTE. 2B is a diagram 230 illustrating an example of channels within the DL frame structure in LTE. 2C is a diagram 250 illustrating an example of a UL frame structure in LTE. FIG. 2D is a diagram 280 illustrating an example of channels within the UL frame structure in LTE. Other wireless communication technologies may have different frame structures and/or different channels. In LTE, the frame (10 ms) can be divided into 10 subframes of the same size. Each sub-frame may include two consecutive time slots. The resource grid can be used to represent two time slots, each time slot including one or more time parallel resource blocks (RBs) (also called physical RBs (PRBs)). The resource grid is divided into multiple resource elements (RE). In LTE, for the normal cyclic first code, RB contains 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain (for DL, OFDM symbols; for UL, SC-FDMA symbols), total 84 REs. For the extended cyclic first code, the RB contains 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include a cell-specific reference signal (CRS) (sometimes referred to as a common RS), a UE-specific reference signal (UE-RS), and a channel state information reference signal (CSI-RS). Figure 2A illustrates the CRS for antenna ports ₀ , ₁ , ₂ , and 3 (indicated as R ₀ , R ₁ , R ₂ and R _{3, respectively} ), the UE-RS for antenna port 5 (indicated as R ₅ ) and CSI-RS (indicated as R) at antenna port 15 FIG. 2B illustrates an example of various channels in the DL sub-frame of the frame. The physical control format indicator channel (PCFICH) is in symbol 0 of slot 0, and carries a physical downlink control channel (PDCCH) indicating 1, 2 or 3 symbols (Figure 2B illustrates a PDCCH occupying 3 symbols) Control Format Indicator (CFI). The PDCCH carries DCI within one or more control channel elements (CCEs). Each CCE includes nine RE groups (REGs). Each REG includes four consecutive REs in an OFDM symbol. The UE may be configured with a UE-specific enhanced PDCCH (ePDCCH) that also carries DCI. The ePDCCH may have 2, 4, or 8 RB pairs (FIG. 2B shows two RB pairs, and each subset includes one RB pair). Physical Hybrid Automatic Repeat Request (ARQ) (HARQ) indicator channel (PHICH) is also in symbol 0 of slot 0 and carries a HARQ indicator indicating HARQ ACK/NACK feedback based on physical uplink shared channel (PUSCH) (HI). The primary synchronization channel (PSCH) is in symbol 6 of time slot 0 in subframes 0 and 5 of the frame, and carries the main synchronization signal (PSS) used by the UE to determine the subframe timing and physical layer identification code. The secondary synchronization channel (SSCH) is in symbol 5 of slot 0 in subframes 0 and 5 of the frame and carries the secondary synchronization signal (SSS) used by the UE to determine the physical layer cell ID group number . Based on the physical layer identification code and the physical layer cell identification code group number, the UE can determine the physical cell identifier (PCI). Based on PCI, the UE can determine the location of the aforementioned DL-RS. The physical broadcast channel (PBCH) is in the symbols 0, 1, 2, and 3 of the time slot 1 of the sub-frame 0 of the frame, and carries the main information block (MIB). The MIB provides the number of RBs in the DL system bandwidth, PHICH configuration, and system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information and paging messages such as system information blocks (SIB) that are not transmitted by the PBCH.

As illustrated in FIG. 2C, some of the REs carry demodulated reference signals (DM-RS) for channel estimation at the eNB. In addition, the UE may transmit a sounding reference signal (SRS) in the last symbol of the subframe. The SRS may have a comb tooth structure, and the UE may transmit the SRS on one of the comb teeth. SRS can be used by eNB for channel quality estimation to achieve frequency-dependent scheduling on UL. FIG. 2D illustrates examples of various channels in the UL subframe of the frame. The physical random access channel (PRACH) can be located in one or more sub-frames within the frame based on the PRACH configuration. PRACH can include six consecutive RB pairs in the subframe. PRACH allows the UE to perform initial system access and achieve UL synchronization. Physical uplink control channel (PUCCH) bit On the edge of the UL system bandwidth. PUCCH carries UCI, such as scheduling request, channel quality indicator (CQI), precoding matrix indicator (PMI), RI and HARQ ACK/NACK feedback. PUSCH carries data and can additionally be used to carry buffer status reports (BSR), power headroom reports (PHR) and/or UCI.

FIG. 3 is a block diagram of an eNB 310 communicating with a UE 350 in an access network. In the DL, the IP packet from the EPC 160 can be provided to the controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data aggregation protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with: broadcast of system information (eg, MIB, SIB), RRC connection control (eg, RRC connection paging, RRC connection establishment, RRC connection modification, and RRC Connection release), inter-radio access technology (RAT) mobility and measurement configuration for UE measurement reports; and header compression/decompression, security (encryption, decryption, integrity protection, integrity verification) PDCP layer functionality associated with delivery support functions; RLC layer functionality associated with: transmission of upper layer packet data units (PDUs), error correction via ARQ, and RLC service data unit (SDU) strings Access, segmentation and reassembly, re-segmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with: mapping between logical channels and transport channels, multiplexing MAC SDU To the transport block (TB), the MAC SDU is demultiplexed from the TB, scheduling information report, error correction through HARQ, priority handling, and logical channel prioritization.

The transmission (TX) processor 316 and the reception (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 including the physical (PHY) layer may include error detection of the transmission channel, forward error correction (FEC) encoding/decoding of the transmission channel, interleaving, rate matching, mapping onto the physical channel, modulation/decoding of the physical channel Modulation and MIMO antenna processing. The TX processor 316 is based on various modulation schemes (eg, binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M phase shift keying (M-PSK), M quadrature amplitude modulation (M- QAM)) while Dispose of the mapping to the signal cluster. The encoded and modulated symbols are then split into parallel streams. Each stream is then mapped to OFDM subcarriers, multiplexed with reference signals (eg, pilots) in the time and/or frequency domain, and then combined using inverse fast Fourier transform (IFFT) to produce a carrier The physical channel of the time-domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. The channel estimate from the channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimate may be derived from the reference signal and/or channel status feedback transmitted by the UE 350. Each spatial stream is then provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate the RF carrier by means of a separate spatial stream for transmission.

At the UE 350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. TX processor 368 and RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for UE 350, the spatial streams can be combined by RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate stream of OFDM symbols for each subcarrier of the OFDM signal. The symbol and reference signal on each subcarrier are recovered and demodulated by determining the most likely signal cluster point transmitted by the eNB 310. These soft decisions may be based on channel estimates calculated by channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the eNB 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In UL, the controller/processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for use ACK and/or NACK protocol error detection to support HARQ operations.

Similar to the functionality described in conjunction with DL transmission by eNB 310, controller/processor 359 provides RRC layer functionality associated with system information (eg, MIB, SIB) acquisition, RRC connection, and measurement reports; and PDCP layer functionality associated with header compression/decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with: transmission of upper layer PDUs, through ARQ Error correction, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with: between logical channels and transport channels Mapping, multiplexing MAC SDU to TB, demultiplexing MAC SDU from TB, scheduling information report, error correction via HARQ, priority handling and logical channel prioritization.

The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the eNB 310 can be used by the TX processor 368 to select the appropriate coding and modulation scheme and facilitate spatial processing. The spatial streams generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX can modulate the RF carrier for transmission via a separate spatial stream.

UL transmissions are processed at the eNB 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives signals through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier, and provides the information to the RX processor 370.

The controller/processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In UL, the controller/processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packet from the controller/processor 375 can be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

4A and 4B are diagrams 700 for explaining an exemplary embodiment. As illustrated in FIG. 4A, the eNB 704 located in the cell 702 may have a plurality of DL sub-frames (e.g., 0, 1, 2, 3, and/or within one or more frames 706 (see also FIG. 2) 4) In the first group, the data transmission 710 is sent to the UE 708. For example, one or more frames 706 and/or 706' may be radio frames used in licensed spectrum communication or LBT frames used in unlicensed spectrum communication. In an exemplary embodiment, referring to FIG. 4B, the data transmission 710 may be sent by the enhanced physical downlink shared channel (ePDSCH) scheduler/transmitter 732 in the eNB 704 and received by the ePDSCH receiver 734 in the UE 708. For each data transmission 710 received from eNB 704, signal 710" can be sent from ePDSCH receiver 734 to buffer 780. The uplink resources used by UE 708 to transmit GACK 724 can be configured during RRC connection establishment. For example, for a group of UEs, each UE in the group receives a group radio network temporary identifier (G-RNTI) and an index within the group (eg, {0,1,...}). PUCCH resources and/or ePUCCH resources in sub-frames (eg, LBT frames) can be configured for each UE based on an index (eg, {0,1,...}). In unlicensed spectrum, PUCCH may More bits need to be carried to accommodate GACK, CSI, short BSR, etc. Therefore, the design of LTE is enhanced to carry more bits, which is called ePUCCH.

The UE group grant may be sent in a DCI format that has not been decided (for example, hereinafter referred to as DCI format n ) for group triggering. For example, n may be an integer greater than or equal to 1. In this example, the UE 708 may monitor the ePDSCH in the DL subframe of the G-RNTI that has four subframes earlier than the ePUCCH configured to transmit GACK 724. The frame format can be inferred from the enhanced physical frame format indicator channel (ePFFICH). For example, the FS1 value of ePFFICH can be associated with the FDD format, the FS2 value of ePFFICH can be associated with the TDD format, and the FS3 value of ePFFICH can be associated with the unlicensed spectrum.

The trigger procedure 718 received in the DCI format n may include the resource bitmap and data required to perform the GACK procedure at the UE 708. The resource bitmap may be large enough to include the CSI trigger procedure, GACK trigger procedure, and GACK label for each UE in the group. For example, the trigger procedure 718 received in the DCI format n may include a 3-bit UE-specific message, where for a given UE, a 3-bit value: for the CSI trigger, locate at bit 3* i , for the GACK trigger It is located at bit (3* i +1), and is located at bit (3** i +2) for GACK tags, where i can be the index of the UE in the group. The ePUCCH resource configured to send GACK 724 for a given UE can be configured based on the number of UEs in the group whose index number precedes the given UE. The trigger 718 may be a UE-specific trigger sent in a UL grant (eg, in this case, GACK may be sent via ePUSCH) or a DL grant (eg, in this case, GACK may be sent via ePUCCH). In an unlicensed spectrum, PUSCH resources can be split into interleaving groups of non-contiguous RBs to meet bandwidth requirements. Therefore, ePUSCH is a PUSCH with an interleaved structure for frequency resources.

Referring to FIG. 4B, in one aspect, eNB 704 may initialize counter 776 so that eNBTag is equal to 0 and all pending ACK strings are set to 0. For each data transmission 710 (eg, Tx) on the HARQ procedure ( k ), the eNB 704 may send a signal 710' to increment the counter 776 so that the bit k of PendingAcksSinceTrig 760 is incremented by one. If the eNB 704 determines that the weight of PendingACK is greater than or equal to TrigThres, it can send a signal 778 to the GACK trigger/receiver 754, which sends a signal 718' to the ePDCCH scheduler/transmitter 752 to transmit the trigger Procedure 718. The eNB 704 may transmit a trigger procedure 718, modify PendingACKsTillTrig to be equal to PendingACK, modify PendingACKsSinceTrig to be equal to 0, and monitor the corresponding ePUCCH (or ePUSCH for DCI format 0) resources for GACK 724. In one aspect, the trigger procedure 718 may be received by the ePDCCH receiver 736 at the UE 708, and the signal 718" may be sent to the GACK receiver/transmitter 738, the GACK receiver/transmitter GACK 724 is generated by sending and/or receiving signal 772 from buffer 780, which buffers HARQsSinceTrig 742, ACKsSinceTrig 744, ACKsTillTrig 748, and/or UETag 750.

Next, the GACK receiver/transmitter 738 may send the signal 724' to the ePUCCH transmission 740, the ePUCCH transmitter transmits the GACK 724 to the eNB 704, where the GACK 724 may be received at the ePUCCH receiver 756. Once GACK 724 is received, ePUCCH receiver 756 can send signal 724" to GACK trigger/receiver 754, which can clear PendingACKsTillTrig 762 and flip eNBTag by sending signal 778 to counter 776 764 (for example, from "0" to "1"). The GACK trigger/receiver 754 can also send a signal 770 to the HARQ manager 758, which can send information 766 related to the received GACK 742 to the ePDSCH scheduler/transmitter 732. If GACK 724 is not received, eNB 704 may send a new trigger procedure. The eNB 704 may choose to schedule new data on the pending HARQ process. Some exemplary GACK procedures 774 are illustrated in the dashed box in FIG. 4B.

In an exemplary embodiment, UE 708 may initialize UETag equal to 1 and set all ACK strings to 0 strings. UE 708 can infer from ePFFICH (for example, it transmits the DL/UL configuration and can be part of the downlink channel using beacon sequence (D-CUBS)) and trigger 718 messages sent from eNB 704 to send GACK 724 EPUCCH position. When the UE 708 receives the trigger program 718, the UE 708 may determine whether UETag is equal to the GACK trigger program tag bit. If UETag is equal to the GACK trigger tag bit, the UE 708 may determine that the previous GACK was not received properly by the eNB 704. Therefore, the new GACK can be formed using both ACKsTillTrig and ACKsSinceTrig, where ACKsSinceTrig is selected to prevent the same HARQ procedure from appearing before and after the trigger procedure. The UE 708 may move the sent GACK to ACKsTillTrig (eg, effectively increment ACKsTillTrig by ACKsSinceTrig) and reset ACKsSinceTrig. However, if the UETag is not equal to the GACK trigger tag bit, the UE 708 may determine that the previous GACK was successful or that this is the first GACK trigger. Here, a new GACK can be formed using ACKsSinceTrig. The UE 708 may modify ACKsTillTrig to be equal to the number of ACK/NACKs in GACK and set ACKsSinceTrig to be equal to 0, which resets ACKsSinceTrig. The UE 708 can flip the UETag so that it matches the eNBTag, which can ensure that GACK triggers in other failure conditions The program tag bit is synchronized with UETag 704. In one aspect, one or more of the UETag and/or GACK trigger procedure bit tags may be any integer and/or counter to achieve the same result.

According to an exemplary method, eNB 704 may increment counter 712 for each data transmission 710 sent to UE 708 in the DL subframe, and UE 708 may buffer ACK/NACK 716 for the first group of data transmission 710 . For example, the UE 708 may buffer the first group of ACK/NACK 716 in the first memory location. When the counter 712 reaches or exceeds the threshold (eg, after a predetermined number of data transmissions 710 have been sent to the UE 708), the eNB 704 may clear the counter 714 and transmit the trigger procedure 718 to the UE 708. In one aspect, the trigger procedure 718 may be used for the GACK 724, which includes the first group of ACK/NACK 716 buffered by the UE 708. In an aspect, the trigger procedure 718 for GACK 724 may include an eNB tag, and the trigger procedure 718 may be transmitted in a predetermined DL subframe (eg, PDCCH subframe). The eNB tag may include a value (for example, "0" or "1"). When receiving the trigger procedure 718, the UE determines whether the eNB tag corresponds to and/or matches the UE tag 720. In another aspect, the trigger program 718 can be used for UCI.

If the eNB tag does not correspond to the UE tag 720, the UE 708 may determine that the trigger procedure 718 including the eNB tag is the first trigger procedure received in the GACK procedure, or the previous GACK (eg, sub-frame 6 in the frame 706) GACK) is successfully received by eNB 704 and passed the error detection test. In other words, when the eNB tag does not correspond to the UE tag 720, the UE 708 may transmit a GACK 724 (for example, a GACK transmitted in the UL subframe 6 of the frame 706'), the GACK includes the frame corresponding to the eNB 704 in the frame ACK/NACK 716 of the first group of data transmissions 710 sent in DL subframes 0, 1 and 2 in 706' and in DL subframes 3 and 4 in frame 706. In this first scenario, and as discussed below with respect to FIG. 5, the UE 708 modifies the UE label 722 to correspond to the eNB label.

However, when the eNB tag corresponds to the UE tag, the UE 708 determines that the previous GACK (eg, the GACK transmitted in the UL subframe 6 of the frame 706) was not successfully received by the eNB 704 And/or failed the error detection test. In this case, the UE 708 may transmit a GACK 724 (eg, GACK transmitted in the UL subframe 6 of the frame 706'), the GACK including subframes 0, 1, and 2 in the frame 706' and The first group of ACK/NACK 716 associated with the data transmission sent in sub-frames 3 and 4 in frame 706, and related to the previous data transmission sent in sub-frames 0, 1, and 2 in frame 706 The second group of ACK/NACK. In this second scenario, and as discussed below with respect to FIG. 6, the UE 708 does not need to modify its UE label 722 to correspond to the eNB label included in the trigger procedure, and thus can avoid modifying the UE label 722.

In the first scenario or the second scenario, the UE 708 can move the buffered group of ACK/NACK 716 from the first memory location to the second memory location. In this way, if the GACK 724 is not properly received and/or fails the error detection test 726, the UE 708 may retransmit the first group's ACK/NACK along with the second group's ACK/NACK in the next GACK 724 ACK/NACK 716.

In addition, the UE 708 may include in the GACK a cyclic redundancy check (CRC) that can be used by the eNB 704 for the error detection test 726. In an exemplary embodiment, the DL subframe (eg, PDCCH or ePDCCH) through which the trigger procedure 718 is transmitted may determine the UL subframe (eg, PUCCH or ePUCCH) used by the UE 708 to transmit the GACK 724. Assuming that GACK 724 is transmitted in the fourth subframe after the DL subframe including the trigger procedure 718, then under the condition that the trigger procedure 718 is transmitted by the eNB 704 in the DL subframe 2, the UE 708 can be in the same signal GACK 724 is transmitted in UL subframe 6 of the frame. The RRC sublayer can be configured to use specific resources in the DL subframe of the trigger procedure 718 and specific resources in the UL subframe of GACK 724. In another aspect, the trigger procedure 718 transmitted by the eNB 704 may include a bitmap (not shown in FIGS. 4A and 4B) intended for the UE group, and each UE 708 may process the bitmap to It is determined that the uplink resources to be used in response to the trigger procedure 718 are to be used.

In an aspect, the UE 708 can monitor specific resources in the DL subframe for the trigger 718, and the eNB 704 can monitor specific resources in the UL subframe for GACK 724. When Upon receiving GACK 724, eNB 704 may perform an error detection test 726 on GACK 724. For example, the CRC included in GACK 724 can be used by eNB 704 to perform error detection test 726. If the GACK 724 passes the error detection test 726, the eNB 704 may generate a new eNB tag 728 to be included in the subsequent trigger procedure, which will indicate to the UE 708 that the GACK 724 is received and passes the error detection test 726. However, if the GACK 724 is not received by the eNB 704 or if the GACK 724 is received but fails the error detection test 726, the eNB 704 can avoid generating a new eNB tag 728. Alternatively, the same eNB tag may be included in the subsequent trigger procedure, which may indicate to the UE 708 that the previously transmitted GACK 724 was not received or failed the error detection test 726.

Alternatively, the eNB 704 has a new to be included in the subsequent trigger procedure to the UE 708 under the condition that the eNB 704 determines that the group 716 of ACK/NACK in the unreceived or defective GACK 724 is unnecessary The flexibility of the eNB tag 728. As appropriate, the eNB 704 may transmit the ACK to the UE 708 when the GACK 724 passes the error detection test 726, and the NACK to the UE 708 when the GACK 724 is not received or fails the error detection test 726.

The trigger procedure 718 may cause a false alarm at the UE 708. If the GACK 724 transmitted by the UE 708 includes a 16-bit CRC, the false alarm chance of the GACK trigger procedure is about 1/65K LBT frame, that is, one false alarm every 650 seconds. The UE-side result of the GACK triggering procedure false alarm may include the UE 708 operating on the assumption that the previous GACK succeeded, and therefore discarding the old ACK/NACK. However, the UE behavior can be corrected after the next successful GACK. In the case of false alarms, a cluster of RLC sublayer interventions (eg, RLC ARQ) can correct the false alarms.

Alternatively, by increasing the CRC included in the GACK 724 to 24 bits, or causing the eNB 704 to send ACK/NACK to the UE 708 associated with the GACK tag, the false alarm rate can be reduced. For example, assume that eNB 704 sends a group trigger procedure for group 1, UE1 in group 1 does not get the trigger procedure and/or fails the CCA, and UE2 in group 2 has With a false alarm that triggers the procedure and transmits GACK, the eNB 704 can decode the GACK as if it were from UE1. Here, UE2 may synchronize with eNB 704 after the next successful GACK. Otherwise, this may cause a cluster of RLC sublayer interventions (eg, RLC ARQ). By including a 16-bit CRC in the GACK, the false alarm rate can also be reduced. The UE 708 may follow the eNB 704 the next time the UETag does not match the GACK trigger program tag. This may cause infrequent RLC retransmission/replication of the cluster via, for example, RLC ARQ.

In an exemplary embodiment, the UE 708 may send a GACK 724, which may be correctly received by the eNB 704. In one aspect, the eNB 704 may send the ACK for the GACK 724 to the UE 708 as a GACK trigger procedure tag. This may cause the UE 708 to send 730 a new GACK 724 to the eNB 704. In one scenario, the eNB 704 may monitor the GACK 724, and when the GACK 724 is received, the GACK 724 may fail the error detection test (eg, the CRC fails the check). Here, if the eNB 704 sends an ACK for the previously received GACK, the eNB 704 may be unable to distinguish between the case where the trigger procedure is not received by the UE 708 and the case where the CCA fails. For example, the eNB 704 may not be able to determine whether the UE 708 did not receive the trigger procedure 718 or whether the CCA failed and therefore the UE 708 did not transmit the GACK 724. At this moment, the eNB 704 may repeat the trigger procedure 718, or the eNB 704 may decide not to send the repeated GACK trigger procedure. Otherwise, UE 708 may consider the latest GACK successful. In order to make this determination, the eNB 704 may need to restore logic (eg, from the RLC sublayer) to handle this confusion.

GACK 724 transmission can be sent independently or in combination with A-CSI. For independent GACK 724 transmission, the payload can be determined by N _HARQ × L bits, where N _HARQ is the number of HARQ procedures, and L is the number of codewords (for example, under the condition of using 2×2 MIMO, L = 2) . The UE 708 may use some ACK integration to reduce the payload, for example, the integration across codewords. For A-CSI transmission, the complete payload may include RI bits, CQI bits, and/or PMI bits. For transmission in ePUSCH, GACK, RI and A-CSI can be coded and multiplexed separately. Here, resource element allocation can be changed to increase diversity to prevent bursty interference. For example, different ACK/NACK mappings can be used to obtain time diversity. The way to perform null TB assignment may be to change the limit of the number of scheduled RBs. For LTE-U based on interleaving, the minimum number of RBs may be 10. Therefore, under the condition that the number of interleaving is 1 (for example, 10 RBs), the null value TB size may be signaled.

In transmission in ePUCCH, UCI may be jointly coded (for example, by means of CRC addition). However, the payload can be zero-filled or not. In one aspect, the payload can be zero-filled (eg, with the help of parity bits) to have the same size for different RI values. The above situation may be necessary because the UE 708 can transmit RI and PMI/CQI at the same time. The transmission power at the UE 708 can be determined from the number of bits without padding/co-location. In another aspect, the payload may not be zero-filled, and the eNB 704 may have to perform blind decoding for multiple different possible payload sizes.

FIG. 5 is a second diagram 800 for explaining an exemplary embodiment. As discussed above, the eNB may send the data transmission to the UE in DL sub-frames (eg, 0, 1, 2, 3, and/or 4) in one or more frames 802 and/or 802'. The UE may send transmissions to the eNB in UL subframes (eg, 6, 7, and 8) in one or more frames 802 and/or 802'. As also discussed above, the UE may buffer a group of ACK/NACK associated with the data transmission from the eNB until the trigger procedure is received. As shown in FIG. 5, the eNB may transmit a first trigger procedure for the first GACK (eg, in sub-frame 2 of frame 802), the first GACK includes the DL sub-frame for use in frame 802 ACK/NACK of the first group of data transmissions sent in frames 0, 1, and 2. The ACK/NACK of the first group may be buffered at the UE as Pending UEACK. In this example, the eNB tag included in the first trigger procedure has the value "0". Assume that the UE determines that the UE tag has a value of "1" and therefore does not correspond to the value of "0" of the eNB tag included in the first trigger procedure. The UE transmits the first GACK to the eNB in the UL sub-frame 6 of the frame 802. The first GACK includes a first group of ACK/NACK (eg, Pending UEACK) associated with the data transmissions sent in DL subframes 0, 1, and 2 in frame 802. In this example, when transmitting the first GACK, the UE may modify The value of the UE tag corresponds to or matches the value of the eNB tag received in the first trigger procedure. That is, the value of the UE tag can be modified from "1" to "0". The modified UE label may be included in the first GACK for reference by the eNB as appropriate. In addition, the UE may buffer the ACK/NACK of the first group as SentUEACK. In this example, the first GACK is received at the eNB and passes the error detection test. Therefore, the eNB may modify the eNB tag so that the eNB tag no longer corresponds to the UE tag. For example, the value of the eNB tag can be modified from "0" to "1".

In this example, the eNB sends the second trigger procedure to the UE in sub-frame 2 of frame 802'. The second trigger procedure is used for the second GACK. The second GACK includes the ACK/NACK of the second group. The ACK/NACK of the second group is buffered by the UE as PendingUEACK for the DL sub in the frame 802. Data transmission in frames 3 and 4 and DL sub-frames 0, 1 and 2 in frame 802'. It is assumed that the second trigger procedure includes the modified eNB tag value "1", and the UE determines that the UE tag has a value "0" that does not correspond to the eNB tag value "1". This indicates to the UE that the first GACK was received and passed the error detection test. Therefore, the UE may clear PendingUEACK as appropriate. In addition, the UE may transmit the second GACK in the UL sub-frame 6 of the frame 802'. The second GACK includes Pending UEACK for DL subframes 3 and 4 in frame 802 and DL subframes 0, 1, and 2 in frame 802'. Once again, when transmitting the second GACK, the UE modifies the value of the UE tag to "1" to correspond or match the value of the eNB tag received in the second trigger procedure. The modified value of the UE tag may be included in the second GACK for reference by the eNB as appropriate. In addition, the UE may buffer PendingUEACK as SentUEACK. In this way, as long as each triggered GACK is received by the eNB and passes the error detection test, the exemplary procedure can continue.

FIG. 6 is a third diagram 900 for explaining an exemplary embodiment. As discussed above, the eNB may send the data transmission to the UE in DL sub-frames (eg, 0, 1, 2, 3, and/or 4) in one or more frames 902 and/or 902'. The UE may send transmissions to the eNB in UL subframes (eg, 6, 7, and 8) in one or more frames 902 and/or 902'. As also discussed above, The UE may buffer a group of ACK/NACK associated with the data transmission from the eNB until the trigger procedure is received. As shown in FIG. 6, the eNB may transmit the first trigger procedure for the first GACK (for example, in sub-frame 2 of frame 902), the first GACK includes the DL sub-frame for use in frame 902 ACK/NACK of the first group of data transmissions sent in frames 0, 1, and 2. The ACK/NACK of the first group may be buffered at the UE as Pending UEACK. In this example, the eNB tag included in the first trigger procedure has the value "0". Assume that the UE determines that the UE tag has a value of "1" as appropriate, and therefore does not correspond to the value of "0" of the eNB tag included in the first trigger procedure. The UE may transmit the first GACK to the eNB in the UL subframe 6 of the frame 902. The first GACK includes the first group of ACK/NACK (eg, Pending UEACK) associated with the data transmissions sent in DL subframes 0, 1, and 2 in frame 902. In this example, when transmitting the first GACK, the UE modifies the value of the UE tag to correspond or match the value of the eNB tag received in the first trigger procedure. That is, the value of the UE tag can be modified from "1" to "0". The modified UE label may be included in the first GACK for reference by the eNB as appropriate. In addition, the UE may buffer PendingUEACK as SentUEACK. In this example, it is assumed that the first GACK is not received by the eNB or fails the error detection test. Therefore, the eNB does not modify the eNB label and the eNB label transmitted in the second trigger procedure may correspond to the UE label. For example, the value of the eNB tag remains "0".

In this example, since the first GACK is not properly received by the eNB, the second trigger procedure with the eNB value "0" is transmitted to the UE in the sub-frame 2 of the frame 902'. The second trigger procedure is for the second GACK, which includes the DL subframes 3 and 4 in frame 902 and the DL subframes 0, 1, and 2 in frame 902'. The ACK/NACK of the second group of data transmission (eg, buffered by the UE as Pending UEACK), and the ACK/NACK of the first group (eg, now buffered by the UE as SentUEACK). In this example, when receiving the second trigger procedure, the UE determines that the UE tag has a value "0" corresponding to the eNB tag value "0". This indicates to the UE that the first GACK is not properly received by the eNB. Therefore, the UE transmits a second GACK, which includes data for transmission in the DL sub-frames 3 and 4 in the frame 902 and the DL sub-frames 0, 1, and 2 in the frame 902' PendingUEACK, and SentUEACK for data transmission sent in DL subframes 0, 1, and 2 in frame 902. The second GACK is transmitted in UL subframe 6 of frame 902'. Here, the UE does not modify the "0" value of the UE tag because it has corresponded or matched the value of the eNB tag value "0" received in the second trigger procedure. The unmodified value of the UE tag may be included in the second GACK for reference by the eNB as appropriate. In addition, the UE can now buffer the ACK/NACK of the second group as SentUEACK, so that both the ACK/NACK of the first group and the ACK/NACK of the second group are buffered as SentUEACK. In this way, the exemplary procedures can provide redundancy to ensure that all GACKs are properly received and decoded by the eNB.

7A to 7C are flowcharts 1000 of a method of wireless communication according to various aspects. This method may be performed by a base station/eNB (such as eNB 704). It should be understood that the operations indicated by dotted lines represent optional operations in various aspects of the present invention.

As shown in FIG. 7A, in step 1002, the eNB sends a data transmission associated with the first plurality of downlink subframes to the UE. For example, referring to FIG. 4A, an eNB 704 located in a cell 702 may have a plurality of DL sub-frames within one or more frames 706 and/or 706' (eg, 0, 1, 2, 3, and/or 4) In the first group, the data transmission 710 is sent to the UE 708. For example, one or more frames 706 and/or 706' may be a radio frame used in LTE-A communication or an LBT frame used in LTE-U communication.

In step 1004, the eNB increments the counter for each data transmission sent to the UE that is associated with the first plurality of downlink subframes. For example, referring to FIG. 4A, the eNB 704 increments the counter 712 for each data transmission 710 sent to the UE 708 in the DL subframe.

In step 1006, when the counter is greater than or equal to the threshold, the eNB transmits the first trigger procedure for the first GACK to the UE. The first trigger program may include the first label and the first A GACK may include a response to data transmission received by the UE. For example, referring to FIG. 4A, when the counter 712 reaches or exceeds the threshold (eg, after a predetermined number of data transmissions 710 have been sent to the UE 708), the eNB 704 transmits the trigger procedure 718 to the UE 708. In one aspect, the trigger procedure 718 may be used for the GACK 724 that includes the first group of ACK/NACK 716 buffered by the UE 708. In an aspect, the trigger procedure 718 for GACK 724 includes the eNB tag, and the trigger procedure 718 can be transmitted in a predetermined DL subframe (eg, PDCCH subframe). The eNB tag may include a value (for example, "0" or "1").

In step 1008, when transmitting the first trigger procedure, the eNB may reset the counter. For example, referring to FIG. 4B, once the GACK trigger procedure is received at the UE 708, the GACK receiver/transmitter 738 may send a signal 724' to the ePUCCH transmitter 740, which transmits the GACK 724 to the eNB 704 At the eNB 704, the GACK 724 may be received at the ePUCCH receiver 756.

In step 1010, the eNB may monitor subsequent subframes for the first GACK from the UE. For example, referring to FIG. 4A, when the counter 712 reaches or exceeds the threshold (eg, after a predetermined number of data transmissions 710 have been sent to the UE 708), the eNB 704 clears the counter 714.

In step 1012, the eNB may determine whether the first GACK is received in the subsequent subframe. If it is determined that the first GACK is received, the method moves to FIG. 7B. Alternatively, if it is determined that the first GACK is not received, the method moves to FIG. 7C.

As shown in FIG. 7B, in step 1014, the eNB may receive the first GACK from the UE. The received first GACK may include a first group of ACK/NACK associated with the first plurality of downlink subframes. For example, referring to FIG. 4A, when GACK 724 is received at eNB 704, eNB 704 may clear PendingACKsTillTrig and flip eNBTag (eg, from "0" to "1"). GACK 724 may include one or more of the first group of ACK/NACK 716 and/or the second group of ACK/NACK buffered by UE 708.

In step 1016, the eNB may perform an error detection test on the received first GACK. For example, referring to FIG. 4A, when GACK 724 is received, eNB 704 may perform an error detection test 726 on GACK 724. For example, the CRC included in GACK 724 can be used to perform error detection test 726 by eNB 704.

In step 1018, the eNB may determine whether the first GACK passes the error detection test. If it is determined that the first GACK passes the error detection test, the method moves to step 1020. Alternatively, if it is determined that the first GACK has failed the error detection test, the method moves to step 1022.

If the first GACK passes the error detection test, in step 1020, the eNB may transmit the ACK to the UE when the received first GACK passes the error detection test. For example, referring to FIG. 4A, the eNB 704 may transmit the ACK to the UE 708 when the GACK 724 passes the error detection test 726.

In step 1024, the eNB may generate a second label. For example, referring to FIG. 4A, if GACK 724 passes error detection test 726, eNB 704 may generate a new eNB tag 728 to be included in the subsequent trigger procedure, which will indicate to UE 708 that GACK 724 was received And passed the error detection test 726.

In step 1026, the eNB may send the data transmission to the UE in the second plurality of sub-frames. For example, referring to FIG. 4A, an eNB 704 located in a cell 702 may have a plurality of DL sub-frames within one or more frames 706 and/or 706' (eg, 0, 1, 2, 3, and/or 4) In the first group, the data transmission 710 is sent to the UE 708. For example, one or more frames 706 and/or 706' may be a radio frame used in LTE-A communication or an LBT frame used in LTE-U communication.

In step 1028, the eNB may increment the counter for each data transmission sent to the UE in the second plurality of sub-frames. For example, referring to FIG. 4A, the eNB 704 increments the counter 712 for each data transmission 710 sent to the UE 708 in the DL subframe.

In step 1030, when the counter is equal to or greater than the threshold, the eNB may use the The second trigger procedure of the second GACK is transmitted to the UE. The second GACK may include a second tag and the second GACK may acknowledge the data transmission received by the UE in the second plurality of sub-frames. For example, referring to FIG. 4A, if GACK 724 passes error detection test 726, eNB 704 may generate a new eNB tag 728 to be included in the subsequent trigger procedure, which will indicate to UE 708 that GACK 724 was received And passed the error detection test 726.

Alternatively, if the first GACK fails the error detection test, in step 1022, the eNB may transmit the NACK to the UE when the received first GACK fails the error detection test. For example, referring to FIG. 4A, the eNB 704 may transmit a NACK to the UE 708 when the GACK 724 is not received or fails the error detection test 726.

In step 1032, the eNB may transmit the second trigger procedure for the second GACK to the UE. For example, the second trigger procedure may include the first tag.

In step 1034, the eNB may receive the second GACK from the UE. The second GACK may include a first group of ACK/NACK associated with the first plurality of downlink subframes and a second group of ACK/NACK associated with the second plurality of downlink subframes. For example, referring to FIG. 4A, when GACK 724 is received at eNB 704, eNB 704 may clear PendingACKsTillTrig and flip eNBTag (eg, from "0" to "1"). GACK 724 may include one or more of the first group of ACK/NACK 716 and/or the second group of ACK/NACK buffered by UE 708.

In step 1036, the eNB may avoid sending the second trigger procedure for the second GACK when the received first GACK fails the error detection test. For example, referring to FIG. 4A, the eNB 704 may not be able to determine whether the UE 708 did not receive the trigger procedure 718 or whether the CRC failed and therefore the UE 708 does not transmit the GACK 724. At this moment, the eNB 704 may repeat the trigger procedure 718, or the eNB 704 may decide not to send the repeated GACK trigger procedure. To make a decision, the eNB 704 may need to restore logic (eg, from the RLC sublayer) to handle this confusion.

If it is determined at step 1012 that the first GACK has not been received, it is as shown in FIG. 7C As shown, in step 1038, the eNB may transmit the second trigger procedure for the second GACK to the UE when the first GACK from the UE is not received. Here, the second trigger program includes the first tag. For example, referring to FIG. 4A, if the eNB 704 does not receive the first GACK from the UE 708, the eNB 704 can now repeat the trigger procedure 718, or the eNB 704 can determine not to send the repeated GACK trigger procedure. To make a decision, the eNB 704 may need to restore logic (eg, from the RLC sublayer) to handle this confusion.

In step 1040, the eNB may receive the second GACK from the UE. The second GACK may include a first group of ACK/NACK associated with the first plurality of sub-frames and a second group of ACK/NACK associated with the second plurality of sub-frames. For example, referring to FIG. 4A, when GACK 724 is received at eNB 704, eNB 704 may clear PendingACKsTillTrig and flip eNBTag (eg, from "0" to "1"). GACK 724 may include one or more of the first group of ACK/NACK 716 and/or the second group of ACK/NACK buffered by UE 708.

In step 1042, the eNB may avoid sending the second trigger procedure for the second GACK when the first GACK is not received. For example, referring to FIG. 4A, if the eNB 704 does not receive the first GACK from the UE 708, the eNB 704 can now repeat the trigger procedure 718, or the eNB 704 can determine not to send the repeated GACK trigger procedure. To make a decision, the eNB 704 may need to restore logic (eg, from the RLC sublayer) to handle this confusion.

8 is a flowchart 1100 of a method of wireless communication according to various aspects. The method may be performed by a UE/mobile station (such as UE 708). It should be understood that the operations indicated by dotted lines represent optional operations in various aspects of the present invention.

In step 1102, the UE stores the ACK/NACK of the first group corresponding to the data transmission of the first group received in the first plurality of downlink subframes from the base station. For example, referring to FIG. 4A, the UE 708 may buffer the ACK/NACK 716 of the first group for the data transmission 710 from the eNB 704.

In step 1104, the UE receives the first from the base station for sending the first group GACK Trigger the program. The first trigger program may include a first tag. For example, referring to FIG. 4A, the eNB 704 transmits the trigger procedure 718 to the UE 708. In one aspect, the trigger procedure 718 is used for the group GACK 724, which includes the first group ACK/NACK 716 buffered by the UE 708. In an aspect, the trigger procedure 718 for GACK 724 includes an eNB tag, and the trigger procedure 718 can be received by the UE 708 in a predetermined DL subframe (eg, PDCCH subframe). The eNB tag may include a value (for example, "0" or "1").

In step 1106, when the first label does not correspond to the UE label, the UE transmits the first GACK including the ACK/NACK of at least the first group to the base station. The first GACK may include a cyclic redundancy check.

In step 1108, the UE may modify the UE label to correspond to the first label. For example, referring to FIG. 4A, when the trigger procedure 718 is received by the UE 708, the UE 708 may transmit the ACK/NACK 716 of the first group and/or the ACK/NACK of the second group that may include the buffer by the UE 708 GACK 724 of one or more of them.

In step 1110, the UE may receive the second trigger procedure for the second GACK from the base station. The second trigger program may include a second tag. For example, referring to FIG. 4A, if GACK 724 passes error detection test 726, eNB 704 may generate a new eNB tag 728 to be included in the subsequent trigger procedure, which will indicate to UE 708 that GACK 724 was received And passed the error detection test 726.

In step 1112, the UE may determine whether the second tag matches the UE bit tag. If the second tag matches the UE bit tag, the method moves to step 1118. Alternatively, if the second label does not match the UE bit label, the method moves to step 1114.

For example, if the second label does not match the UE bit label, in step 1114, the UE may transmit the second GACK including the ACK/NACK of the second group to the second group when the second label does not match the UE bit label. Base station. For example, referring to FIG. 4A, when the trigger procedure 718 is received by the UE 708, the UE 708 may transmit the ACK/NACK 716 of the first group and/or the ACK/NACK of the second group that may include the buffer by the UE 708 GACK for one or more of 724.

In step 1116, the UE may clear the ACK/NACK of the first group when receiving the second trigger procedure. For example, referring to FIG. 4A, it is assumed that the second trigger procedure includes a modified eNB tag value "1", and the UE determines that the UE tag has a value "0" that does not correspond to the eNB tag value "1". This indicates to the UE that the first GACK was received and passed the error detection test. Therefore, the UE may clear PendingUEACK as appropriate.

Alternatively, if the second tag matches the UE bit tag, at step 1118, the UE may avoid transmitting the second GACK when the second tag matches the UE bit tag. For example, referring to FIG. 4A, the UE 708 can move the ACK/NACK 716 of the buffered group from the first memory location to the second memory location. In this way, if the GACK 724 is not properly received and/or fails the error detection test 726, the UE 708 may retransmit the first group's ACK/NACK along with the second group's ACK/NACK in the next GACK 724 ACK/NACK 716.

9 is a flowchart 1200 of a method of wireless communication according to various aspects. The method may be performed by a UE/mobile station (such as UE 708).

In step 1202, the UE generates UCI including GACK, RI and CSI. For example, referring to FIG. 4A, for A-CSI transmission from UE 708, the full payload may include RI bits, CQI bits, and/or PMI bits. For transmission in ePUSCH, GACK, RI and A-CSI can be coded and multiplexed separately. Here, resource element allocation can be changed to increase diversity to prevent bursty interference. For example, different ACK/NACK mappings can be used to obtain time diversity. The way to perform null TB assignment may be to change the limit of the number of scheduled RBs. For LTE-U based on interleaving, the minimum number of RBs may be 10. Therefore, under the condition that the number of interleaving is 1 or 10 RB, the null value TB size can be signaled.

In step 1204, the UE sends a UCI transmission in the LBT sub-frame. When the UCI transmission is GACK transmission, the payload of the UCI transmission sent by the UE may include several HARQ procedures and several codewords. When UCI transmission is CSI transmission, the payload of UCI transmission sent by the UE may include two or more jointly encoded RI bits, CQI bits and PMI bit. For example, referring to FIG. 4A, for A-CSI transmission from UE 708, the full payload may include RI bits, CQI bits, and/or PMI bits. For transmission in ePUSCH, GACK, RI and A-CSI can be coded and multiplexed separately. Here, resource element allocation can be changed to increase diversity to prevent bursty interference. For example, different ACK/NACK mappings can be used to obtain time diversity. The way to perform null TB assignment may be to change the limit of the number of scheduled RBs. For LTE-U based on interleaving, the minimum number of RBs may be 10. Therefore, under the condition that the number of interleaving is 1 (for example, 10RB), the null value TB size may be signaled.

FIG. 10 is a flowchart 1300 of a method of wireless communication according to various aspects. The method may be performed by a UE/mobile station (such as UE 708). It should be understood that operations indicated by dotted lines indicate optional operations for various aspects of the present invention.

In step 1302, the UE may receive the trigger procedure for UCI in the LBT frame. For example, referring to FIG. 4A, the eNB 704 transmits the trigger procedure 718 to the UE 708. In one aspect, the trigger program 718 can be used for UCI.

In step 1304, the UE sends a UCI transmission on the PUCCH. The payload of the UCI transmission sent by the UE may include two or more jointly encoded GACK bits, CSI bits, RI bits, CQI bits, and PMI bits. For example, referring to FIG. 4A, for A-CSI transmission from UE 708, the full payload may include RI bits, CQI bits, and/or PMI bits. For transmission in ePUSCH, GACK, RI and A-CSI can be coded and multiplexed separately. Here, resource element allocation can be changed to increase diversity to prevent bursty interference. For example, different ACK/NACK mappings can be used to obtain time diversity. The way to perform null TB assignment may be to change the limit of the number of scheduled RBs. For LTE-U based on interleaving, the minimum number of RBs may be 10. Therefore, under the condition that the number of interleaving is 1 (for example, 10 RBs), the null value TB size may be signaled.

FIG. 11 is a conceptual data flow diagram 1400 illustrating the data flow between different components/components in the exemplary device 1402. The device may include an eNB. The device includes a receiving component 1404, which The receiving component may receive UL data transmission, the first GACK and/or the second GACK from the UE 1450. In one aspect, the received first GACK may include a first group of ACK/NACK associated with the first plurality of downlink subframes. In the second aspect, the second GACK may include a first group of ACK/NACKs associated with the first plurality of downlink sub-frames and a second group of groups associated with the second plurality of downlink sub-frames ACK/NACK of the group. The receiving component 1404 may send the signal 1420 associated with the DL data transmission to the monitoring component 1406.

The monitoring component 1406 may monitor subsequent subframes for the first GACK from the UE 1450 based on the GACK trigger procedure transmitted by the transmission component 1418 and the UL transmission received from the UE 1450. If the first GACK is not received in the subsequent sub-frame, the monitoring component 1406 may send the signal 1430 to the avoiding component 1416. If a GACK is received in the subsequent sub-frame, the monitoring component 1406 may send the signal 1422 to the error detection component 1408.

The error detection component 1408 can perform an error detection test on the received first GACK. If the GACK fails the error detection test, the error detection component 1408 may send the signal 1432 to the avoidance component 1416. When the received first GACK fails the error detection test, the avoidance component 1416 may send a signal 1434 instructing the transmission component 1418 to avoid sending the second trigger procedure for the second GACK. For example, the second trigger procedure may include the first tag. In addition, when the first GACK is not received, the signal 1434 may instruct the avoidance component 1418 to avoid sending the second trigger procedure for the second GACK. For example, the second trigger procedure may include the first tag. When the GACK passes the error detection test, the signal 1424 can be sent from the error detection component 1408 to the generation component 1410. When the received first GACK passes the error detection test, the generating component 1410 can generate the second tag. The signal 1436 including information related to the second tag may be sent to the transmission component 1418 for inclusion in the subsequent GACK trigger procedure.

The transmission component 1418 may send the following items to the UE 1450: data transmission associated with the first plurality of downlink subframes, a first trigger procedure for the first GACK (count When the counter is greater than or equal to the threshold), ACK (when the received first GACK passes the error detection test), NACK (when the received first GACK fails the error detection test), the second plural number Data transmission in the frame, the second trigger procedure for the second GACK (when the counter is equal to or greater than the threshold), the second trigger procedure for the second GACK (when the received first GACK fails) Detection test) and/or the second trigger procedure for the second GACK (when the first GACK from the UE 1450 is not received). For example, the first trigger procedure sent by the transmission component 1418 may include a first tag and the first GACK is a response to the data transmission received by the UE. In another example, the second trigger procedure sent by the transmission component 1418 may include a second tag and the second GACK response is transmitted by the UE in the second plurality of subframes. In other examples, the second trigger procedure sent by the transmission component 1418 may include the first tag.

For each DL data transmission sent to UE 1450, transmission component 1418 may send signal 1428 to increment component 1414. The incrementing component 1414 may increment the counter for each data transmission sent to the UE 1450 associated with the first plurality of downlink subframes, and for each data transmission sent to the UE 1450 in the second plurality of subframes Increment the counter. When the GACK trigger procedure is sent to the UE 1450, a signal 1426 may be sent to the reset component 1412. When transmitting the first trigger program, the reset component 1412 can reset the counter.

The device may include additional components for each of the blocks that execute the algorithm in the aforementioned flowcharts of FIGS. 7A-7C. As such, each block in the aforementioned flowcharts of FIGS. 7A-7C may be executed by components, and the device may include one or more of their components. The components may be one or more hardware components specially configured to implement the described program/algorithm, implemented by a processor configured to execute the described program/algorithm, and stored on a computer-readable medium Internal for processor implementation, or some combination thereof.

FIG. 12 is a diagram 1500 illustrating an example of hardware implementation of a device 1402' using a processing system 1514. The processing system 1514 can utilize the bus architecture (usually represented by the bus 1524) to Implementation. Depending on the specific application of the processing system 1514 and the overall design constraints, the bus 1524 may include any number of interconnecting buses and bridges. The bus 1524 links various circuits including: one or more processors and/or hardware components (represented by the processor 1504), components 1404, 1406, 1408, 1410, 1412, 1414, 1416 and 1418 and computer-readable media/memory 1506. The bus 1524 may also be linked to various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described further.

The processing system 1514 can be coupled to the transceiver 1510. The transceiver 1510 is coupled to one or more antennas 1520. The transceiver 1510 provides means for communicating with various other devices via transmission media. The transceiver 1510 receives signals from one or more antennas 1520, extracts information from the received signals and provides the extracted information to the processing system 1514 (specifically, the receiving component 1404). In addition, the transceiver 1510 receives information from the processing system 1514 (specifically, the transmission component 1418), and based on the received information, generates a signal to be applied to one or more antennas 1520. The processing system 1514 includes a processor 1504 coupled to a computer-readable medium/memory 1506. The processor 1504 is responsible for general processing, including executing the software stored on the computer-readable medium/memory 1506. The software, when executed by the processor 1504, causes the processing system 1514 to perform the various functions described above for any particular device. The computer-readable medium/memory 1506 can also be used to store data manipulated by the processor 1504 when executing software. The processing system 1514 further includes at least one of components 1404, 1406, 1408, 1410, 1412, 1414, 1416, and 1418. The component may be a software component executed in the processor 1504, resident/stored in the computer-readable medium/memory 1506, coupled to one or more hardware components of the processor 1504, or some combination thereof. Processing system 1514 may be a component of eNB 310 and may include memory 376 and/or at least one of TX processor 316, RX processor 370, and controller/processor 375.

In one configuration, the device 1402/1402' for wireless communication includes means for transmitting data transmissions associated with the first plurality of downlink subframes to the UE. In another In one aspect, the device 1402/1402' for wireless communication includes means for incrementing the counter for each data transmission sent to the UE associated with the first plurality of downlink subframes. In other aspects, the device 1402/1402' for wireless communication includes means for transmitting the first trigger procedure for the first GACK to the UE when the counter is greater than or equal to the threshold. For example, the first trigger procedure may include a first tag, and the first GACK is a response to the data transmission received by the UE. Furthermore, the device 1402/1402' for wireless communication may further include means for resetting the counter when transmitting the first trigger procedure. In addition, the device 1402/1402' may include means for monitoring subsequent subframes for the first GACK from the UE. In addition, the device 1402/1402' for wireless communication may include means for receiving the first GACK from the UE. For example, the received first GACK may include the first group of ACK/NACK associated with the first plurality of downlink subframes. In addition, the device 1402/1402' for wireless communication may include means for performing an error detection test on the received first GACK. In addition, the device 1402/1402' for wireless communication may include means for transmitting the ACK to the UE when the received first GACK passes the error detection test. In another aspect, the device 1402/1402' for wireless communication may include means for transmitting NACK to the UE when the received first GACK fails the error detection test. In other aspects, the device 1402/1402' for wireless communication may include means for generating a second label when the received first GACK passes the error detection test. In another aspect, the device 1402/1402' for wireless communication may include means for transmitting data transmission to the UE in the second plurality of sub-frames. In another aspect, the device 1402/1402' for wireless communication may include means for incrementing the counter for each data transmission sent to the UE in the second plurality of sub-frames. In addition, the device 1402/1402' for wireless communication may include means for transmitting the second trigger procedure for the second GACK to the UE when the counter is equal to or greater than the threshold. For example, the second trigger procedure may include a second tag and the second GACK response is transmitted by the UE in the second plurality of subframes. Further, the device for wireless communication 1402/1402' may include means for transmitting the second trigger procedure for the second GACK to the UE when the received first GACK fails the error detection test. For example, the second trigger procedure may include the first tag. In other aspects, the device 1402/1402' for wireless communication may include means for receiving the second GACK from the UE. For example, the second GACK may include a first group of ACK/NACKs associated with the first plurality of downlink subframes and a second group of ACKs associated with the second plurality of downlink subframes /NACK. Furthermore, the device 1402/1402' for wireless communication may include means for avoiding sending the second trigger procedure for the second GACK when the received first GACK fails the error detection test. For example, the second trigger procedure may include the first tag. In addition, the device 1402/1402' for wireless communication may include means for transmitting the second trigger procedure for the second GACK to the UE when the first GACK from the UE is not received. For example, the second trigger procedure includes the first tag. Furthermore, the device 1402/1402' for wireless communication may include means for avoiding sending the second trigger procedure for the second GACK when the first GACK is not received. For example, the second trigger procedure includes the first tag. The aforementioned components may be one or more of the aforementioned components of the device 1402 and/or the processing system 1514 of the device 1402' configured to perform the functions recited by the aforementioned components. As described above, the processing system 1514 may include a TX processor 316, an RX processor 370, and a controller/processor 375. As such, in a configuration, the aforementioned component may be a TX processor 316, an RX processor 370, and a controller/processor 375 configured to perform the functions stated by the aforementioned component.

It should be understood that the specific order or hierarchy of blocks in the disclosed procedures/flowcharts are illustrative of exemplary methods. Based on design preferences, it should be understood that the specific order or hierarchy of blocks in the process/flowchart can be reconfigured. In addition, some blocks may be combined or omitted. The attached method request items present elements of various blocks in a sample order, and are not intended to be limited to the specific order or hierarchy presented.

FIG. 13 illustrates the data flow between different components/assemblies in the exemplary device 1602. Conceptual data flow chart 1600. The device may include a UE. The device includes a receiving component 1604 that receives one or more DL data transmissions from the eNB 1650, a first trigger procedure for sending a first GACK, a second trigger procedure for sending a second GACK, and/or for LBT The triggering procedure of UCI in the message frame. In one aspect, the first trigger program may include a first tag. In another aspect, the second trigger program may include a second tag.

The receiving component 1604 can send a signal 1614 related to DL data transmission to the storage component 1606. The storage component 1606 can store the ACK/NACK of the first group corresponding to the first group of data transmissions received in the first plurality of downlink subframes from the eNB 1650. The receiving component 1604 can also send a signal 1616 to the clearing component 1610, which includes information related to the eNB trigger procedure tag received in the GACK trigger procedure from the eNB 1650.

The clearing component 1610 can clear the ACK/NACK of the first group when receiving the second trigger procedure from the base station 1650. When the GACK trigger is received at the receiving component 1604, the signal 1614 sent to the storage component 1606 can include information related to the GACK trigger, and the storage component 1606 can send the signal 1618 to the transmission component 1612. Upon receiving the GACK trigger procedure, the receiving component 1604 can send a signal 1620 to the modifying component 1608. The modification component 1608 may modify the UE label to correspond to the first label and send a signal 1622 to the transmission component 1612 associated with the modified UE label corresponding to the first label. The transmission component 1612 may send one or more of the following to the eNB 1650: UCI transmission in the LBT subframe, UCI transmission on the PUCCH, and the first GACK (including the ACK/NACK of the first group at least) When the first label does not correspond to the UE label), the second GACK including the ACK/NACK of the second group (when the second label does not match the UE bit label) and/or the ACK/NACK and the first group One or more of the ACK/NACK of the two groups (when the first label is equal to the UE label). In addition, if the ACK/NACK of the first group and the ACK/NACK of the second group correspond to the same HARQ process, the transmission component 1612 may transmit the ACK/NACK of the first group in the first GACK.

The device may include additional components that perform each of the blocks of the algorithm in the aforementioned flowcharts of FIGS. 8-10. As such, each block in the aforementioned flowcharts of FIGS. 8-10 may be executed by components and the device may include one or more of their components. The components may be one or more hardware components specially configured to implement the described program/algorithm, implemented by a processor configured to execute the described program/algorithm, and stored on a computer-readable medium Internal for processor implementation, or some combination thereof.

14 is a diagram 1700 illustrating an example of a hardware implementation of a device 1602' using a processing system 1714. The processing system 1714 may be implemented by means of a bus architecture (usually represented by the bus 1724). Depending on the specific application of the processing system 1714 and the overall design constraints, the bus 1724 may include any number of interconnecting buses and bridges. The bus 1724 links various circuits including the following: one or more processors and/or hardware components (represented by the processor 1704), components 1604, 1606, 1608, 1610, and 1612 and computer-readable Media/Memory 1706. The bus 1724 may also be linked to various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described further.

The processing system 1714 may be coupled to the transceiver 1710. The transceiver 1710 is coupled to one or more antennas 1720. The transceiver 1710 provides means for communicating with various other devices via transmission media. The transceiver 1710 receives signals from one or more antennas 1720, extracts information from the received signals and provides the extracted information to the processing system 1714 (specifically, the receiving component 1604). In addition, the transceiver 1710 receives information from the processing system 1714 (specifically, the transmission component 1612), and based on the received information, generates a signal to be applied to one or more antennas 1720. The processing system 1714 includes a processor 1704 coupled to a computer-readable medium/memory 1706. The processor 1704 is responsible for general processing, including executing software stored on the computer-readable medium/memory 1706. The software, when executed by the processor 1704, causes the processing system 1714 to perform the various functions described above for any particular device. The computer-readable medium/memory 1706 can also be used to store data manipulated by the processor 1704 when executing software. Place The management system 1714 further includes at least one of components 1604, 1606, 1608, 1610, and 1612. The component may be a software component executed in the processor 1704, resident/stored in the computer-readable medium/memory 1706, coupled to one or more hardware components of the processor 1704, or some combination thereof. Processing system 1714 may be a component of UE 350 and may include at least one of memory 360 and/or TX processor 368, RX processor 356, and controller/processor 359.

In one configuration, the device 1602/1602' for wireless communication includes a first for storing data transmissions corresponding to the first group received in the first plurality of downlink subframes from the base station ACK/NACK component of the group. In one aspect, the device 1602/1602' for wireless communication includes means for receiving a first trigger procedure for sending a first GACK from a base station. For example, the first trigger procedure may include a first tag for transmitting a first GACK including at least a first group of ACK/NACK to the base station when the first tag does not correspond to the UE tag. In another aspect, the device 1602/1602' for wireless communication may include means for modifying the UE tag to correspond to the first tag when transmitting the first GACK to the base station, for receiving from the base station A component of the second trigger procedure of the second GACK. For example, the second trigger procedure may include a second tag. In other aspects, the device 1602/1602' for wireless communication may include a second GACK for transmitting the second group of ACK/NACK to the base station when the second label does not match the UE bit label member. Furthermore, the device 1602/1602' for wireless communication may include means for clearing the ACK/NACK of the first group when the second trigger procedure is received. In addition, the device 1602/1602' for wireless communication may include means for transmitting one or more of ACK/NACK of the first group and ACK/NACK of the second group to the first group when the first label is equal to the UE label Base station components. In addition, the device 1602/1602' for wireless communication may include transmitting the first GACK in the first GACK under the condition that the ACK/NACK of the first group and the ACK/NACK of the second group correspond to the same HARQ process ACK/NACK component of the group. In another aspect, the device 1602/1602' for wireless communication may include means for sending UCI transmissions in the LBT sub-frame. For example, in the UCI transmission system GACK transmission At the time of transmission, the payload of UCI transmission may include several HARQ programs and several codewords. In another example, when UCI transmission is CSI transmission, the payload of UCI transmission may include two or more jointly encoded RI bits, CQI bits, and PMI bits. In one aspect, the device 1602/1602' for wireless communication may include means for sending UCI transmissions on the PUCCH. For example, the payload of a UCI transmission includes two or more jointly encoded GACK bits, CSI bits, RI bits, CQI bits, and PMI bits. In one aspect, the device 1602/1602' for wireless communication may include components for generating UCI, which includes GACK, RI, and CSI transmission. In other aspects, the device 1602/1602' for wireless communication may include means for sending UCI transmissions in the LBT sub-frame. The aforementioned components may be one or more of the aforementioned components of the device 1602 and/or the processing system 1714 of the device 1602' configured to perform the functions recited by the aforementioned components. As described above, the processing system 1714 may include a TX processor 368, an RX processor 356, and a controller/processor 359. As such, in a configuration, the aforementioned component may be a TX processor 368, an RX processor 356, and a controller/processor 359 configured to perform the functions stated by the aforementioned component.

The previous description is provided to enable those skilled in the art to practice the various aspects described herein. Those skilled in the art will easily understand the various modifications of these aspects, and the general principles defined in this article can be applied to other aspects. Therefore, the scope of patent application is not intended to be limited to what is shown in this article, but is intended to be given to all categories consistent with the scope of language patent application, where reference to an element in the singular form is not intended to mean "one and Only one" (unless expressly stated so), but "one or more". The word "exemplary" is used herein to mean "used as an example, instance, or description." Any aspect described herein as "exemplary" is not necessarily interpreted as better or more advantageous than other aspects. Unless expressly stated otherwise, the term "some" refers to one or more. Such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one of A, B and C" The combination of "or more" and "A, B, C or any combination thereof" includes Any combination of A, B, and/or C, and may include multiple A, multiple B, or multiple C. Specifically, such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "A, B, and C The combination of "one or more of C" and "A, B, C or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C or A and B and C, any of these combinations may contain one or more members of A, B or C. All structural and functional equivalents of elements in various aspects known to those skilled in the art or later to be known throughout the invention are hereby incorporated by reference and are intended to be covered by the patent include. In addition, regardless of whether any content disclosed in this article is explicitly stated in the scope of the patent application, this disclosure is not intended to be dedicated to the public. The expressions "module", "institution", "component", "device" and the like are not substitutes for the expression "component". As such, unless the component is explicitly stated using the phrase "component used for", any requested component should not be interpreted as component plus function.

1000‧‧‧Flowchart

Claims (56)

A method of wireless communication, comprising: transmitting data transmissions associated with a first plurality of downlink sub-frames to a user equipment (UE); for the first plurality of downlink sub-frames sent to the UE Each data transmission associated with the frame increments a counter; and when the counter is greater than or equal to a threshold, a first trigger procedure for a first group acknowledgement/negative acknowledgement (GACK) is transmitted to the UE, where the first trigger procedure includes a first tag and the first GACK is a response to the data transmissions received by the UE, and any of the data transmissions associated with the data transmissions from the UE are being received The first trigger procedure is transmitted before the acknowledgement/negative acknowledgement (ACK/NACK). The method of claim 1, further comprising: resetting the counter when transmitting the first trigger program. The method of claim 2, further comprising: monitoring a subsequent sub-frame for the first GACK from the UE. The method of claim 3, further comprising: receiving the first GACK from the UE, wherein the received first GACK includes a response of a first group associated with the first plurality of downlink subframes /Negative acknowledgement (ACK/NACK); and perform an error detection test on the first GACK received. The method of claim 4, further comprising: when the received first GACK passes the error detection test, transmitting an acknowledgement (ACK) to the UE; and when the received first GACK fails the pass When the error detection test, will be negative Acknowledgement (NACK) is transmitted to the UE. The method of claim 4, wherein when the received first GACK passes the error detection test, the method further includes: generating a second label. The method of claim 6, further comprising: sending data transmissions to the UE in the second plurality of sub-frames; incrementing the counter for each data transmission sent to the UE in the second plurality of sub-frames ; And when the counter is equal to or greater than the threshold value, a second trigger procedure for a second GACK is transmitted to the UE, where the second trigger procedure includes the second tag and the second GACK response is sent by the The data transmission received by the UE in the second plurality of sub-frames. The method of claim 4, wherein when the received first GACK fails the error detection test, the method further includes: transmitting a second trigger procedure for a second GACK to the UE, wherein the The second trigger procedure includes the first tag; and receiving the second GACK from the UE, where the second GACK includes the ACK/NACK of the first group associated with the first plurality of downlink subframes and A second group of ACK/NACK associated with the second plurality of downlink subframes. The method of claim 4, further comprising: avoiding sending a second trigger procedure for a second GACK when the received first GACK fails the error detection test, wherein the second trigger procedure includes the The first label. The method of claim 4, further comprising: transmitting a second trigger procedure for a second GACK to the UE when the first GACK from the UE is not received, wherein the second trigger procedure includes the the first Label; and receiving the second GACK from the UE, wherein the second GACK includes the first group of ACK/NACK and the second plurality of downlink sub-frames associated with the first plurality of downlink sub-frames A second group of ACK/NACK associated with the frame. The method of claim 3, further comprising: avoiding sending a second trigger procedure for a second GACK when the first GACK is not received, wherein the second trigger procedure includes the first tag. A method of wireless communication, comprising: storing a response/negative response of a first group corresponding to a first group of data transmission received in a first plurality of downlink subframes from a base station ( ACK/NACK); receiving a first trigger procedure for sending a first group response/negative response (GACK) from the base station, wherein the first trigger procedure includes a first tag; and the first tag When it does not correspond to a user equipment (UE) tag, a first GACK including at least the ACK/NACK of the first group is transmitted to the base station, where the reception is associated with the data transmissions from the UE The first trigger procedure is transmitted before any response/negative response (ACK/NACK). The method of claim 12, wherein when transmitting the first GACK to the base station, the method further includes: modifying the UE label to correspond to the first label. The method of claim 13, further comprising: receiving a second trigger procedure for a second GACK from the base station, wherein the second trigger procedure includes a second tag; and when the second tag does not match the When the UE tags, a second GACK including an ACK/NACK of a second group is transmitted to the base station. The method of claim 14 further includes: When the second trigger procedure is received, the ACK/NACK of the first group is cleared. The method of claim 12, wherein the first GACK includes a cyclic redundancy check. The method of claim 12, wherein the transmitting the first GACK includes: when the first label is equal to the UE label, one of the first group of ACK/NACK and a second group of ACK/NACK Or more transmission to the base station. The method of claim 17, wherein the ACK/NACK of the second group corresponds to data transmission of a second group received in the second plurality of downlink subframes, and wherein if the first group ACK/NACK and ACK/NACK of the second group correspond to the same hybrid automatic repeat request (HARQ) procedure, and only the ACK/NACK of the first group is transmitted in the first GACK. An apparatus for wireless communication, comprising: means for transmitting data transmission associated with the first plurality of downlink subframes to a user equipment (UE); and for transmitting to the UE Each data transmission associated with the first plurality of downlink subframes increments a counter; and is used for a first group answer/negative answer when the counter is greater than or equal to a threshold (GACK) A first trigger procedure is transmitted to the component of the UE, wherein the first trigger procedure includes a first tag and the first GACK is a response to the data transmission received by the UE, and The first trigger procedure is transmitted before receiving any acknowledgement/negative acknowledgement (ACK/NACK) associated with the data transmissions from the UE. The device of claim 19, further comprising: means for resetting the counter when transmitting the first trigger program. The apparatus of claim 20, further comprising: means for monitoring a subsequent subframe for the first GACK from the UE. The apparatus of claim 21, further comprising: means for receiving the first GACK from the UE, wherein the received first GACK includes a first associated with the first plurality of downlink subframes Acknowledgement/negative acknowledgement (ACK/NACK) of the group; and means for performing an error detection test on the received first GACK. The device of claim 22, further comprising: means for transmitting an acknowledgement (ACK) to the UE when the received first GACK passes the error detection test; and When a GACK fails the error detection test, a negative acknowledgement (NACK) is transmitted to the component of the UE. The device of claim 22, wherein when the received first GACK passes the error detection test, the method further includes: a component for generating a second label. The device of claim 24, further comprising: means for sending data transmission to the UE in the second plurality of sub-frames; for each of the data sent to the UE in the second plurality of sub-frames Means for incrementing the counter by data transmission; and means for transmitting a second trigger procedure for a second GACK to the UE when the counter is equal to or greater than the threshold, wherein the second trigger procedure includes The second tag and the second GACK response are transmitted by the UE in the second plurality of sub-frames. The device of claim 22, wherein when the received first GACK fails the error detection test, the method further includes: transmitting a second trigger procedure for a second GACK to the UE Component, wherein the second trigger procedure includes the first tag; and a component for receiving the second GACK from the UE, wherein the second GACK includes The ACK/NACK of the first group associated with the first plurality of downlink subframes and the ACK/NACK of a second group associated with the second plurality of downlink subframes. The device of claim 22, further comprising: means for avoiding sending a second trigger procedure for a second GACK when the received first GACK fails the error detection test, wherein the second The trigger program contains the first label. The device of claim 21, further comprising: means for transmitting a second trigger procedure for a second GACK to the UE when the first GACK from the UE is not received, wherein the second The trigger procedure includes the first tag; and means for receiving the second GACK from the UE, wherein the second GACK includes the ACK/ of the first group associated with the first plurality of downlink subframes NACK and a second group of ACK/NACK associated with the second plurality of downlink subframes. The device of claim 21, further comprising: means for avoiding sending a second trigger procedure for a second GACK when the first GACK is not received, wherein the second trigger procedure includes the first tag . An apparatus for wireless communication includes: a first group of responses corresponding to a first group of data transmissions received in a first plurality of downlink subframes from a base station /Negative acknowledgement (ACK/NACK) component; a component for receiving a first trigger procedure for sending a first group response/negative response (GACK) from the base station, wherein the first trigger procedure includes a First label; and A component for transmitting a first GACK including at least an ACK/NACK of the first group to the base station when the first label does not correspond to a user equipment (UE) label, wherein The first trigger procedure is received before any acknowledgement/negative acknowledgement (ACK/NACK) associated with a group of data transmissions. The apparatus of claim 30, wherein when transmitting the first GACK to the base station, the apparatus further includes: means for modifying the UE label to correspond to the first label. The device of claim 31, further comprising: means for receiving a second trigger procedure for a second GACK from the base station, wherein the second trigger procedure includes a second tag; and When the second label does not match the UE label, a second GACK including a second group of ACK/NACK is transmitted to the base station component. The device of claim 32, further comprising: means for clearing the ACK/NACK of the first group when the second trigger procedure is received. The apparatus of claim 30, wherein the first GACK includes a cyclic redundancy check. The apparatus of claim 30, wherein the means for transmitting the first GACK includes ACK/NACK for the first group and ACK/ for a second group when the first label is equal to the UE label One or more of the NACKs are transmitted to the component of the base station. The device of claim 35, wherein the ACK/NACK of the second group corresponds to data transmission of a second group received in the second plurality of downlink subframes, and wherein if the first group ACK/NACK and ACK/NACK of the second group correspond to the same hybrid automatic repeat request (HARQ) procedure, the device further includes ACK/NACK for transmitting only the first group in the first GACK Of building blocks. A device for wireless communication, comprising: a memory; and at least one processor coupled to the memory and configured to: transmit data associated with the first plurality of downlink subframes Sent to a user equipment (UE); incrementing a counter for each data transmission sent to the UE associated with the first plurality of downlink subframes; and when the counter is greater than or equal to a threshold Transmits a first trigger procedure for a first group response/negative acknowledgement (GACK) to the UE, where the first trigger procedure includes a first tag and the first GACK is received by the UE One of the data transmission acknowledgments, and the first trigger procedure is transmitted before any acknowledgment/negative acknowledgement (ACK/NACK) associated with the data transmissions from the UE is received. The apparatus of claim 37, wherein the at least one processor is further configured to reset the counter when transmitting the first trigger program. The apparatus of claim 38, wherein the at least one processor is further configured to monitor a subsequent sub-frame for the first GACK from the UE. The device of claim 39, wherein the at least one processor is further configured to: receive the first GACK from the UE, wherein the received first GACK includes associated with the first plurality of downlink subframes One of the first group's acknowledgement/negative acknowledgement (ACK/NACK); and perform an error detection test on the received first GACK. The apparatus of claim 40, wherein the at least one processor is further configured to: transmit an acknowledgement (ACK) to the UE when the received first GACK passes the error detection test; and upon receiving If the first GACK fails the error detection test, it will be denied The NACK is transmitted to the UE. The device of claim 40, wherein the at least one processor is configured to generate a second tag when the received first GACK passes the error detection test. The device of claim 42, wherein the at least one processor is further configured to: send the data transmission to the UE in the second plurality of sub-frames; for the device sent to the UE in the second plurality of sub-frames Each data transmission increments the counter; and when the counter is equal to or greater than the threshold, a second trigger procedure for a second GACK is transmitted to the UE, where the second trigger procedure includes the second tag And the second GACK response is transmitted by the UE in the second plurality of sub-frames. The device of claim 40, wherein when the received first GACK fails the error detection test, the at least one processor is configured to: transmit a second trigger procedure for a second GACK to The UE, wherein the second trigger procedure includes the first tag; and the second GACK is received from the UE, wherein the second GACK includes the first group associated with the first plurality of downlink subframes ACK/NACK and a second group of ACK/NACK associated with the second plurality of downlink subframes. The device of claim 40, wherein the at least one processor is further configured to avoid sending a second trigger procedure for a second GACK when the received first GACK fails the error detection test, The second trigger program includes the first label. The apparatus of claim 39, wherein the at least one processor is further configured to: transmit a second trigger procedure for a second GACK to the UE when the first GACK from the UE is not received, Wherein the second trigger procedure includes the first label; and Receiving the second GACK from the UE, wherein the second GACK includes the ACK/NACK of the first group associated with the first plurality of downlink sub-frames and the second plurality of downlink sub-frames ACK/NACK of a second group. The device of claim 39, wherein the at least one processor is further configured to avoid sending a second trigger procedure for a second GACK when the first GACK is not received, wherein the second trigger procedure includes The first label. A device for wireless communication, including: a memory; and at least one processor coupled to the memory and configured to: store a plurality of downlink sub-corresponding to a first from a base station A first group of acknowledgments/negative acknowledgments (ACK/NACK) received from the first group of data transmission; received from the base station for sending a first group of acknowledgments/negative acknowledgments (GACK) A first trigger procedure, wherein the first trigger procedure includes a first tag; and when the first tag does not correspond to a user equipment (UE) tag, it will include at least the ACK/NACK of the first group A first GACK is transmitted to the base station, wherein the first trigger procedure is received before transmitting any acknowledgment/negative acknowledgement (ACK/NACK) associated with the data transmission of the first group. The apparatus of claim 48, wherein when transmitting the first GACK to the base station, the at least one processor is configured to: modify the UE label to correspond to the first label. The device of claim 49, wherein the at least one processor is further configured to: receive a second trigger procedure for a second GACK from the base station, wherein the second trigger procedure includes a second tag; and When the second label does not match the UE label, a second GACK including an ACK/NACK of a second group is transmitted to the base station. The device of claim 50, wherein the at least one processor is further configured to clear the ACK/NACK of the first group when the second trigger procedure is received. The apparatus of claim 48, wherein the first GACK includes a cyclic redundancy check. The device of claim 48, wherein the at least one processor is further configured to ACK/NACK the first group and ACK/NACK the second group when the first label is equal to the UE label One or more of them are transmitted to the base station to transmit the first GACK. The device of claim 53, wherein the ACK/NACK of the second group corresponds to data transmission of a second group received in the second plurality of downlink subframes, and wherein if the first group ACK/NACK and ACK/NACK of the second group correspond to the same hybrid automatic repeat request (HARQ) procedure, then the at least one processor is further configured to transmit only the first group in the first GACK ACK/NACK. A computer-readable medium storing computer-executable program code for wireless communication, including program code for the following operations: transmitting data transmission associated with the first plurality of downlink sub-frames to a user equipment (UE); for each data transmission associated with the first plurality of downlink subframes sent to the UE, a counter is incremented; and when the counter is greater than or equal to a threshold, it will be used for a first A first trigger procedure of a group response/negative acknowledgement (GACK) is transmitted to the UE, wherein the first trigger procedure includes a first tag and the first GACK is one of the data transmissions received by the UE Acknowledgement, and transmit the first trigger procedure before receiving any acknowledgement/negative acknowledgement (ACK/NACK) associated with the data transmissions from the UE. A computer-readable medium that stores computer-executable programs for wireless communication Code, including program code for the following operations: storing a response/negation of a first group corresponding to a first group of data transmissions received in the first plurality of downlink subframes from a base station Acknowledge (ACK/NACK); receive a first trigger procedure for sending a first group response/negative acknowledgement (GACK) from the base station, where the first trigger procedure includes a first tag; and in the first When a label does not correspond to a user equipment (UE) label, a first GACK including at least the ACK/NACK of the first group is transmitted to the base station, where the transmission is related to the data transmission of the first group The first trigger procedure is received before any response/negative response (ACK/NACK).

Images