HARQ timelines for TDD-FDD carrier aggregation

US9538565B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9538565-B2
Application numberUS-201414318143-A
CountryUS
Kind codeB2
Filing dateJun 27, 2014
Priority dateSep 26, 2013
Publication dateJan 3, 2017
Grant dateJan 3, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Disclosed embodiments include an end-to-end UE and eNB HARQ protocol design for various TDD-FDD joint operation wireless network configurations. Designs for timing of HARQ feedback in response to PDSCH and PUSCH transmissions (or simply, PDSCH and PUSCH) include both HARQ feedback from a UE, and HARQ feedback from an eNB. The PUSCH HARQ timeline embodiments also include both self-scheduling and cross-carrier scheduling scenarios for PUSCH transmissions. In addition, designs for the cross-carrier scheduling scenarios contemplate an FDD scheduling cell or a TDD scheduling cell.

First claim

Opening claim text (preview).

The invention claimed is: 1. A user equipment (UE) configured for cross-carrier scheduled carrier aggregation, the UE comprising: circuitry configured to: decode a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH) or a physical downlink control channel (PDCCH) in a scheduling cell to obtain information for scheduling physical uplink shared channels (PUSCHs), the PUSCHs including a first PUSCH in the scheduling cell and a second PUSCH in a scheduled cell, the scheduling cell having a first duplex mode, the scheduled cell having a second duplex mode that is different from the first duplex mode; detect from the PHICH, a first HARQ in response to the first PUSCH, in which the first HARQ is detected according to a first predefined HARQ timing corresponding to the first duplex mode; and detect from the PHICH, a second HARQ in response to the second PUSCH, in which the second HARQ is detected according to a second predefined HARQ timing corresponding to the first duplex mode or the second duplex mode, in which, in response to the UE receiving during a subframe index value of n a PDCCH or a PHICH associated with the scheduled cell, the second PUSCH is configured to be transmitted during a subframe index value of n+k, where k≧4 and where k is based on a preconfigured time division duplex (TDD) configuration type. 2. The UE of claim 1 , in which the first duplex mode is a frequency division duplex (FDD) mode and the second duplex mode is a TDD mode. 3. The UE of claim 2 , in which the second predefined HARQ timing corresponds to an FDD mode, in which the second predefined HARQ timing specifies that the second PUSCH transmitted during the subframe index value of n has an associated HARQ message carried in the PHICH during a subframe index value of n+4. 4. The UE of claim 2 , in which the second predefined HARQ timing corresponds to a TDD mode, and in which the second predefined HARQ timing specifies that the second PUSCH transmitted during the subframe index value of n has an associated HARQ message carried in the PHICH during the subframe index value of n+k. 5. The UE of claim 1 , in which the first duplex mode is a TDD mode and the second duplex mode is a frequency division duplex (FDD) mode. 6. The UE of claim 5 , in which the second predefined HARQ timing corresponds to the TDD mode, and in which the second predefined HARQ timing specifies that the second PUSCH transmitted during the subframe index value of n has an associated HARQ message carried in the PHICH during the subframe index value of n+k. 7. A user equipment (UE) configured for cross-carrier scheduled carrier aggregation, the UE comprising: circuitry configured to: decode a physical hybrid automatic repeat request (HARQ) indicator channel (PHICH) or a physical downlink control channel (PDCCH) in a scheduling cell to obtain information for scheduling physical uplink shared channels (PUSCHs), the PUSCHs including a first PUSCH in the scheduling cell and a second PUSCH in a scheduled cell, the scheduling cell having a first duplex mode, the scheduled cell having a second duplex mode that is different from the first duplex mode; detect from the PHICH, a first HARQ in response to the first PUSCH, in which the first HARQ is detected according to a first predefined HARQ timing corresponding to the first duplex mode; and detect from the PHICH, a second HARQ in response to the second PUSCH, in which the second HARQ is detected according to a second predefined HARQ timing that corresponds to a time division duplex (TDD) mode, and in which the second predefined HARQ timing specifies that the second PUSCH transmitted during a subframe index value of n has an associated HARQ message carried in the PHICH during a subframe index value of n+k, where k≧4 and where k is based on a preconfigured TDD configuration type. 8. The UE of claim 7 , in which the first duplex mode is a frequency division duplex (FDD) mode and the second duplex mode is the TDD mode. 9. The UE of claim 8 , in which, in response to the UE receiving during the subframe index value of n a PDCCH or a PHICH associated with the scheduled cell, the second PUSCH is configured to be transmitted during the subframe index value of n+k. 10. The UE of claim 7 , in which the first duplex mode is the TDD mode and the second duplex mode is a frequency division duplex (FDD) mode. 11. The UE of claim 10 , in which, in response to the UE receiving during the subframe index value of n a PDCCH or a PHICH associated with the scheduled cell, the second PUSCH is configured to be transmitted during the subframe index value of n+k. 12. The UE of claim 7 , in which, in response to the UE receiving during the subframe index value of n a PDCCH or a PHICH associated with the scheduled cell, the second PUSCH is configured to be transmitted during the subframe index value of n+k.

Assignees

Inventors

Classifications

  • in the downlink direction of a wireless link, i.e. towards a terminal · CPC title

  • Scheduling and prioritising arrangements · CPC title

  • H04W8/005Primary

    Discovery of network devices, e.g. terminals · CPC title

  • Allocation of pilot signals, i.e. of signals known to the receiver (allocation of control signalling H04L5/0053; use of control signalling H04L5/0091) · CPC title

  • Resources in time domain, e.g. slots or frames · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9538565B2 cover?
Disclosed embodiments include an end-to-end UE and eNB HARQ protocol design for various TDD-FDD joint operation wireless network configurations. Designs for timing of HARQ feedback in response to PDSCH and PUSCH transmissions (or simply, PDSCH and PUSCH) include both HARQ feedback from a UE, and HARQ feedback from an eNB. The PUSCH HARQ timeline embodiments also include both self-scheduling and…
Who is the assignee on this patent?
Intel Ip Corp
What technology area does this patent fall under?
Primary CPC classification H04W8/005. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jan 03 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).