IP Library › Granted Patent US 12,231,243
Granted Patent B2
US 12,231,243 · App. 18/174,936 · Granted Feb 18, 2025

Feedback mode indication for coordinated transmission

Inventors: Wei Yang (San Diego, CA); Yi Huang (San Diego, CA); Peter Gaal (San Diego, CA); Wanshi Chen (San Diego, CA); Joseph Binamira Soriaga (San Diego, CA); Gokul Sridharan (Sunnyvale, CA)
Assignee: QUALCOMM Incorporated
H04L1/1812H04L1/0073H04L1/1607H04W76/27
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,231,243
App. No.
18/174,936
Granted
Feb 18, 2025
Kind
B2
Abstract

Certain aspects of the present disclosure provide techniques for wireless communication. The techniques include a method wireless communication by a user equipment including receiving a first physical downlink control channel (PDCCH) from a first transmission reception point (TRP) and a second PDCCH from a second TRP, wherein the first PDCCH and the second PDCCH include the same downlink control information (DCI), selecting a physical uplink control channel (PUCCH) resource for transmitting hybrid automatic repeated request acknowledgment (HARQ-ACK) feedback based on one of the first PDCCH or the second PDCCH, and transmitting a PUCCH that includes the HARQ-ACK feedback using the selected PUCCH resource.

Claims (48)

1. A method for wireless communication by a user equipment (UE), comprising:

receiving a first physical downlink control channel (PDCCH) from a first transmission reception point (TRP) and a second PDCCH from a second TRP, wherein downlink control information (DCI) included in each of the first PDCCH and the second PDCCH is the same;

selecting a physical uplink control channel (PUCCH) resource for transmitting hybrid automatic repeated request acknowledgment (HARQ-ACK) feedback based, in part, on a PDCCH, comprising one of the first PDCCH or the second PDCCH, detected in a last PDCCH monitoring occasion of a plurality of PDCCH monitoring occasions; and

transmitting a PUCCH that includes the HARQ-ACK feedback using the selected PUCCH resource.

2. The method of claim 1 , wherein selecting the PUCCH resource is further based on an index of a starting control channel element (CCE) associated with the PDCCH detected in the last PDCCH monitoring occasion.

3. The method of claim 1 , wherein selecting the PUCCH resource is further based on a search space identifier associated with the first PDCCH or the second PDCCH.

4. The method of claim 1 , wherein the first PDCCH from the first TRP and the second PDCCH from the second TRP comprise a PDCCH repetition.

5. The method of claim 1 , further comprising generating the HARQ-ACK feedback, wherein the HARQ-ACK feedback is associated with both the first PDCCH received from the first TRP and the second PDCCH received from the second TRP.

6. The method of claim 1 , further comprising determining that a first PUCCH transmission for the first TRP and a second PUCCH transmission for the second TRP are scheduled on the selected PUCCH resource.

7. The method of claim 6 , further comprising:

generating first HARQ-ACK feedback for the first PUCCH transmission for the first TRP from a first HARQ-ACK codebook; and

generating second HARQ-ACK feedback for the second PUCCH transmission for the second TRP from a second HARQ-ACK codebook.

8. The method of claim 7 , wherein the first HARQ-ACK codebook is a semi-static codebook of a first size and the second HARQ-ACK codebook is a semi-static codebook of a second size that is different from the first size.

9. The method of claim 7 , further comprising multiplexing a first number of bits of the first HARQ-ACK feedback with a second number of bits of the second HARQ-ACK feedback to obtain multiplexed HARQ-ACK feedback, wherein transmitting the HARQ-ACK feedback comprises transmitting the multiplexed HARQ-ACK feedback, in the PUCCH resource, to at least one of the first TRP or the second TRP.

10. A user equipment (UE), comprising:

one or more processors configured to execute instructions stored on one or more memories and to cause the UE to:

receive a first physical downlink control channel (PDCCH) from a first transmission reception point (TRP) and a second PDCCH from a second TRP, wherein downlink control information (DCI) included in each of the first PDCCH and the second PDCCH is the same;

select a physical uplink control channel (PUCCH) resource for transmitting hybrid automatic repeated request acknowledgment (HARQ-ACK) feedback based, in part, on a PDCCH, comprising one of the first PDCCH or the second PDCCH, detected in a last PDCCH monitoring occasion of a plurality of PDCCH monitoring occasions; and

transmit a PUCCH that includes the HARQ-ACK feedback using the selected PUCCH resource.

11. The UE of claim 10 , wherein the one or more processors are configured to cause the UE to select the PUCCH resource further based on an index of a starting control channel element (CCE) associated with the PDCCH detected in the last PDCCH monitoring occasion.

12. The UE of claim 10 , wherein the one or more processors are configured to cause the UE to select the PUCCH resource based, in part, on a search space identifier associated with the first PDCCH or the second PDCCH.

13. The UE of claim 10 , wherein the first PDCCH from the first TRP and the second PDCCH from the second TRP comprise a PDCCH repetition.

14. The UE of claim 10 , wherein the one or more processors are further configured to cause the UE to generate the HARQ-ACK feedback, wherein the HARQ-ACK feedback is associated with both the first PDCCH received from the first TRP and the second PDCCH received from the second TRP.

15. The UE of claim 10 , wherein the one or more processors are further configured to cause the UE to determine that a first PUCCH transmission for the first TRP and a second PUCCH transmission for the second TRP are scheduled on the selected PUCCH resource.

16. The UE of claim 15 , wherein the one or more processors are further configured to cause the UE to:

generate first HARQ-ACK feedback for the first PUCCH transmission for the first TRP from a first HARQ-ACK codebook; and

generate second HARQ-ACK feedback for the second PUCCH transmission for the second TRP from a second HARQ-ACK codebook.

17. The UE of claim 16 , wherein the first HARQ-ACK codebook is a semi-static codebook of a first size and the second HARQ-ACK codebook is a semi-static codebook of a second size that is different from the first size.

18. The UE of claim 16 , wherein:

the one or more processors are further configured to cause the UE to multiplex a first number of bits of the first HARQ-ACK feedback with a second number of bits of the second HARQ-ACK feedback to obtain multiplexed HARQ-ACK feedback; and

in order to transmit the HARQ-ACK feedback, the one or more processors are configured to cause the UE to transmit the multiplexed HARQ-ACK feedback, in the PUCCH resource, to at least one of the first TRP or the second TRP.

19. A method for wireless communication by a network entity, comprising:

sending, to a user equipment (UE), a first physical downlink control channel (PDCCH) from a first transmission reception point (TRP) and a second PDCCH from a second TRP, wherein downlink control information (DCI) included in each of the first PDCCH and the second PDCCH is the same; and

receiving, in a physical uplink control channel (PUCCH) resource, a PUCCH that includes hybrid automatic repeated request acknowledgment (HARQ-ACK) feedback, wherein the PUCCH resource is based, in part, on a PDCCH, comprising one of the first PDCCH or the second PDCCH, transmitted in a last PDCCH monitoring occasion of a plurality of PDCCH monitoring occasions.

20. The method of claim 19 , wherein:

the PUCCH resource is further based on an index of a starting control channel element (CCE) associated with the PDCCH transmitted in the last PDCCH monitoring occasion.

21. The method of claim 19 , wherein the PUCCH resource is further based on a search space identifier associated with the first PDCCH or the second PDCCH.

22. The method of claim 19 , wherein the first PDCCH from the first TRP and the second PDCCH from the second TRP comprise a PDCCH repetition.

23. The method of claim 19 , wherein the HARQ-ACK feedback is associated with both the first PDCCH from the first TRP and the second PDCCH from the second TRP.

24. A network entity, comprising:

one or more processors configured to execute instructions stored on one or more memories and to cause the network entity to:

send, to a user equipment (UE), a first physical downlink control channel (PDCCH) from a first transmission reception point (TRP) and a second PDCCH from a second TRP, wherein downlink control information (DCI) included in each of the first PDCCH and the second PDCCH is the same; and

receive, in a physical uplink control channel (PUCCH) resource, a PUCCH that includes hybrid automatic repeated request acknowledgment (HARQ-ACK) feedback, wherein the PUCCH resource is based, in part, on a PDCCH, comprising one of the first PDCCH or the second PDCCH, transmitted in a last PDCCH monitoring occasion of a plurality of PDCCH monitoring occasions.

25. The network entity of claim 24 , wherein:

the PUCCH resource is further based on an index of a starting control channel element (CCE) associated with the PDCCH transmitted in the last PDCCH monitoring occasion.

26. The network entity of claim 24 , wherein the PUCCH resource is further based on a search space identifier associated with the first PDCCH or the second PDCCH.

27. The network entity of claim 24 , wherein the first PDCCH from the first TRP and the second PDCCH from the second TRP comprise a PDCCH repetition.

28. The network entity of claim 24 , wherein the HARQ-ACK feedback is associated with both the first PDCCH from the first TRP and the second PDCCH from the second TRP.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 27, 2023
From: YANG, WEI; HUANG, YI; GAAL, PETER; CHEN, WANSHI; SORIAGA, JOSEPH BINAMIRA; SRIDHARAN, GOKUL
To: QUALCOMM INCORPORATED
Reel/Frame 062810/0390 →
Continuity (4)
Continuation 17657791 · Apr 4, 2022
Continuation 16523911 · Jul 26, 2019
Provisional Application 62711157 · Jul 27, 2018
Related Publication 20230231659A1 · Jul 20, 2023
References Cited (67)
US 9515758B2 · Choi · 2016 [cited by examiner]
US 9537614B2 · Liang et al. · 2017 [cited by applicant]
US 9554299B2 · Seo et al. · 2017 [cited by applicant]
US 9763151B2 · Kim et al. · 2017 [cited by applicant]
US 9888493B2 · Park et al. · 2018 [cited by applicant]
US 10735146B2 · Wang et al. · 2020 [cited by applicant]
US 10925047B2 · Islam et al. · 2021 [cited by applicant]
US RE48606E · Papasakellariou · 2021 [cited by examiner]
US 11296827B2 · Yang et al. · 2022 [cited by applicant]
US 20080310338A1 · Charpenter et al. · 2008 [cited by applicant]
US 20110267995A1 · Li et al. · 2011 [cited by applicant]
US 20120026935A1 · Park et al. · 2012 [cited by applicant]
US 20120314671A1 · Noh et al. · 2012 [cited by applicant]
US 20120320805A1 · Yang et al. · 2012 [cited by applicant]
US 20130039349A1 · Ebrahimi Tazeh Mahalleh et al. · 2013 [cited by applicant]
US 20130208691A1 · Yang · 2013 [cited by examiner]
US 20130294369A1 · Dinan et al. · 2013 [cited by applicant]
US 20130336214A1 · Sayana et al. · 2013 [cited by applicant]
US 20140241323A1 · Park et al. · 2014 [cited by applicant]
US 20150085714A1 · Liang et al. · 2015 [cited by applicant]
US 20150181571A1 · Park · 2015 [cited by examiner]
US 20150381252A1 · Kang et al. · 2015 [cited by applicant]
US 20150381254A1 · Liang · 2015 [cited by applicant]
US 20160105882A1 · Park et al. · 2016 [cited by applicant]
US 20160119947A1 · Park et al. · 2016 [cited by applicant]
US 20160204924A1 · Li et al. · 2016 [cited by applicant]
US 20160345199A1 · Nogami et al. · 2016 [cited by applicant]
US 20170134140A1 · Park · 2017 [cited by applicant]
US 20170272219A1 · Park et al. · 2017 [cited by applicant]
US 20170272220A1 · Chen et al. · 2017 [cited by applicant]
US 20180020444A1 · Lee et al. · 2018 [cited by applicant]
US 20180034612A1 · Lin et al. · 2018 [cited by applicant]
US 20180176943A1 · Takeda · 2018 [cited by examiner]
US 20190081750A1 · Yang et al. · 2019 [cited by applicant]
US 20190132893A1 · Lu et al. · 2019 [cited by applicant]
US 20190158205A1 · Sheng · 2019 [cited by examiner]
US 20190215044A1 · Noh et al. · 2019 [cited by applicant]
US 20190246378A1 · Islam et al. · 2019 [cited by applicant]
US 20190319751A1 · Chen et al. · 2019 [cited by applicant]
US 20190342905A1 · Ren et al. · 2019 [cited by applicant]
US 20190373577A1 · Agiwal · 2019 [cited by examiner]
US 20190393994A1 · Liang et al. · 2019 [cited by applicant]
US 20200015200A1 · Vilaipornsawai · 2020 [cited by examiner]
US 20200036480A1 · Yang et al. · 2020 [cited by applicant]
US 20200154467A1 · Gong · 2020 [cited by examiner]
US 20200178332A1 · Sharma et al. · 2020 [cited by applicant]
US 20200260475A1 · Yoshimura · 2020 [cited by examiner]
US 20200296704A1 · Vilaipornsawai · 2020 [cited by examiner]
US 20200304248A1 · Lunttila et al. · 2020 [cited by applicant]
US 20210092732A1 · Lee · 2021 [cited by examiner]
US 20210259004A1 · Takeda · 2021 [cited by examiner]
US 20220303060A1 · Yang et al. · 2022 [cited by applicant]
US 20220394715A1 · Papasakellariou · 2022 [cited by examiner]
CN 104380787A · 2015 [cited by applicant]
EP 2624494A2 · 2013 [cited by applicant]
WO 2017168039A1 · 2017 [cited by applicant]
ASUSTEK: “Discussion on Multi-TRP DL Transmission”, 3GPP TSG RAN WG1 Meeting NR#3, 3GPP Draft, R1-1716546, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Ant… [cited by examiner]
NTT Docomo, Inc: “DUUL Scheduling and HARQ Management”, 3GPP TSG RAN WG1 Meeting 90bis, 3GPP Draft, R1-1718217, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophi… [cited by examiner]
ASUSTEK: “Discussion on Multi-TRP DL Transmission”, 3GPP TSG RAN WG1 Meeting NR#3, 3GPP Draft, R1-1716546, Discussion on Multi-TRP DL Transmission, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 65… [cited by applicant]
AT&T: “Remaining Details on Supporting Multi-TRP Transmission and Reception”, 3GPP Draft, R1-1716165, 3GPP TSG RAN WG1 Meeting NR#3, RemainingDetails on Supporting Multi-TRP Transmission and Reception, 3rd Generatio… [cited by applicant]
Ericsson: “On Multi-TRP and Multi-Panel Transmission,” 3GPP Draft, 3GPP TSG-RAN WG1 #89, R1-1708673, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipolis… [cited by applicant]
Huawei, et al., “Discussion on the Multi-TRP/Panel Transmission in NR”, 3GPP TSG RAN WG1 Meeting #93, R1-1807130, May 25, 2018, 7 Pages. [cited by applicant]
Huawei, et al., “Solution and TP for Multi-TRP PDCCH Transmission”, 3GPP Draft, 3GPP TSG RAN WG 1 Ad Hoc Meeting, R1-1800824, 3GPP TSG RAN WG1 Ad Hoc Meeting, 3rd Generation Partnership Project (3GPP), Mobile Competence… [cited by applicant]
Interdigital Inc: “NR-PDCCH Design for Multi-TRP Transmission,” 3GPP Draft; R1-1716465, 3GPP TSG RAN WG1 Meeting NR#3, NR-PDCCH Design for Multi-TRP Transmission, 3rd Generation Partnership Project (3GPP), Mobile Compet… [cited by applicant]
International Preliminary Report on Patentability—PCT/US2019/043816, The International Bureau of WIPO—Geneva, Switzerland, Feb. 11, 2021. [cited by applicant]
International Search Report and Written Opinion—PCT/US2019/043816—ISA/EPO—Oct. 28, 2019. [cited by applicant]
NTT Docomo, Inc: “DL/UL Scheduling and HARQ Management”, 3GPP TSG RAN WG1 Meeting 90bis, 3GPP Draft, R1-1718217, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Soph… [cited by applicant]
Cited By (1)
US 12,634,726