IP Library › Granted Patent US 12,261,803
Granted Patent B2
US 12,261,803 · App. 18/355,686 · Granted Mar 25, 2025

Wireless resource determination and use

Inventors: Ali Cagatay Cirik (Chantilly, VA); Esmael Hejazi Dinan (McLean, VA); Yunjung Yi (Vienna, VA); Hua Zhou (Vienna, VA); Alireza Babaei (Fairfax, VA); Youngwoo Kwak (Woodbury, NY); Kyungmin Park (Vienna, VA)
Assignee: Comcast Cable Communications, LLC
H04L5/0055H04L5/001H04L5/0094H04W28/04H04W72/1268H04W72/23
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,261,803
App. No.
18/355,686
Granted
Mar 25, 2025
Kind
B2
Abstract

Wireless resource determination and use are described. A wireless device may determine to use a resource (e.g., PUCCH resource), indicated by control information (e.g., DCI), for sending an acknowledgement (e.g., HARQ-ACK feedback) of a reception of data (e.g., at least one transport block). The control information may be received in a message of a plurality of messages. The wireless device may select the control information (e.g., for determining the resource) from among other control information in the plurality of messages, based on one or more factors.

Claims (53)

1. A method comprising:

receiving, by a wireless device:

via a first control resource set (CORESET) associated with a first search space set identified by a first search space set index, first downlink control information (DCI); and

via a second CORESET associated with a second search space set identified by a second search space set index, second DCI;

determining a physical uplink control channel (PUCCH) resource based on the first DCI, wherein the first DCI is selected based on the first search space set index being lower than the second search space set index; and

transmitting, via the PUCCH resource, hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to downlink reception scheduled by the first DCI.

2. The method of claim 1 , wherein the HARQ-ACK information further corresponds to downlink reception scheduled by the second DCI.

3. The method of claim 1 , wherein the determining the PUCCH resource based on the first DCI comprises determining the PUCCH resource based on a PUCCH resource indicator field in the first DCI.

4. The method of claim 1 , wherein the first DCI or the second DCI indicates scheduling information for reception of a transport block (TB).

5. The method of claim 1 , wherein:

the receiving the first DCI comprises receiving the first DCI during a first PDCCH monitoring occasion; and

the receiving the second DCI comprises receiving the second DCI during a second PDCCH monitoring occasion.

6. The method of claim 1 , wherein the first DCI and the second DCI indicate an uplink time slot for transmission of the HARQ-ACK information.

7. The method of claim 1 , wherein the first DCI is further selected based on at least one of:

a priority parameter of the first DCI; or

a service type of the first DCI.

8. A wireless device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the wireless device to:

receive:

via a first control resource set (CORESET) associated with a first search space set identified by a first search space set index, first downlink control information (DCI); and

via a second CORESET associated with a second search space set identified by a second search space set index, second DCI;

determine a physical uplink control channel (PUCCH) resource based on the first DCI, wherein the first DCI is selected based on the first search space set index being lower than the second search space set index; and

transmit, via the PUCCH resource, hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to downlink reception scheduled by the first DCI.

9. The wireless device of claim 8 , wherein the HARQ-ACK information further corresponds to downlink reception scheduled by the second DCI.

10. The wireless device of claim 8 , wherein the instructions, when executed by the one or more processors, cause the wireless device to determine the PUCCH resource based on the first DCI by causing determining the PUCCH resource based on a PUCCH resource indicator field in the first DCI.

11. The wireless device of claim 8 , wherein the first DCI or the second DCI indicates scheduling information for reception of a transport block (TB).

12. The wireless device of claim 8 , wherein the instructions, when executed by the one or more processors, cause the wireless device to:

receive the first DCI by causing receiving the first DCI during a first PDCCH monitoring occasion; and

receive the second DCI by causing receiving the second DCI during a second PDCCH monitoring occasion.

13. The wireless device of claim 8 , wherein the first DCI and the second DCI indicate an uplink time slot for transmission of the HARQ-ACK information.

14. The wireless device of claim 8 , wherein the first DCI is further selected based on at least one of:

a priority parameter of the first DCI; or

a service type of the first DCI.

15. A non-transitory computer readable medium storing instructions that, when executed, cause:

receiving, by a wireless device:

via a first control resource set (CORESET) associated with a first search space set identified by a first search space set index, first downlink control information (DCI); and

via a second CORESET associated with a second search space set identified by a second search space set index, second DCI;

determining a physical uplink control channel (PUCCH) resource based on the first DCI, wherein the first DCI is selected based on the first search space set index being lower than the second search space set index; and

transmitting, via the PUCCH resource, hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to downlink reception scheduled by the first DCI.

16. The non-transitory computer readable medium of claim 15 , wherein the HARQ-ACK information further corresponds to downlink reception scheduled by the second DCI.

17. The non-transitory computer readable medium of claim 15 , wherein the instructions, when executed, cause determining the PUCCH resource based on the first DCI by causing determining the PUCCH resource based on a PUCCH resource indicator field in the first DCI.

18. The non-transitory computer readable medium of claim 15 , wherein the first DCI or the second DCI indicates scheduling information for reception of a transport block (TB).

19. The non-transitory computer readable medium of claim 15 , wherein the instructions, when executed, cause:

receiving the first DCI by causing receiving the first DCI during a first PDCCH monitoring occasion; and

receiving the second DCI by causing receiving the second DCI during a second PDCCH monitoring occasion.

20. The non-transitory computer readable medium of claim 15 , wherein the first DCI and the second DCI indicate an uplink time slot for transmission of the HARQ-ACK information.

21. The non-transitory computer readable medium of claim 15 , wherein the first DCI is further selected based on at least one of:

a priority parameter of the first DCI; or

a service type of the first DCI.

22. The method of claim 1 , wherein the determining the PUCCH resource based on the first DCI comprises comparing the first search space set index with the second search space set index.

23. The wireless device of claim 8 , wherein the instructions, when executed by the one or more processors, cause the wireless device to determine the PUCCH resource based on the first DCI by causing comparing the first search space set index with the second search space set index.

24. The non-transitory computer readable medium of claim 15 , wherein the instructions, when executed, cause determining the PUCCH resource based on the first DCI by causing comparing the first search space set index with the second search space set index.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 4, 2024
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; YI, YUNJUNG; ZHOU, HUA; BABAEI, ALIREZA; KWAK, YOUNGWOO; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068482/0088 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 4, 2024
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; YI, YUNJUNG; ZHOU, HUA; BABAEI, ALIREZA; KWAK, YOUNGWOO; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068482/0098 →
Continuity (3)
Continuation 16919287 · Jul 2, 2020
Provisional Application 62869642 · Jul 2, 2019
Related Publication 20240089064A1 · Mar 14, 2024
References Cited (49)
US 9615267B2 · Fu et al. · 2017 [cited by applicant]
US 10568081B2 · Papasakellariou · 2020 [cited by applicant]
US 10601567B2 · Marinier et al. · 2020 [cited by applicant]
US 20150223240A1 · Choi · 2015 [cited by examiner]
US 20190342035A1 · Zhang · 2019 [cited by examiner]
US 20190349973A1 · Yang · 2019 [cited by examiner]
US 20200022144A1 · Papasakellariou · 2020 [cited by examiner]
US 20200288482A1 · Yi · 2020 [cited by examiner]
US 20200389871A1 · Wang · 2020 [cited by examiner]
US 20210068142A1 · Park · 2021 [cited by examiner]
US 20210160880A1 · Zhang · 2021 [cited by examiner]
US 20220029750A1 · Matsumura · 2022 [cited by examiner]
NTT Docomo et al: “Remaining issues CA and type1 HARO-ACK codebook”, 3GPP Draft; R1-1807071, 3rd Eneration Partnership Project (3GPP), Mobile Competence Centre ; 650, Route Des Ucioles; F-06921 Sophia-Antipolis Cedex; F… [cited by examiner]
3GPP TS 38.212 V15.5.0 (Mar. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding (Release 15). [cited by applicant]
3GPP TS 38.213 V15.5.0 (Mar. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 15). [cited by applicant]
3GPP TS 38.214 V15.5.0 (Mar. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 15). [cited by applicant]
3GPP TS 38.300 V15.5.0 (Mar. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15). [cited by applicant]
3GPP TS 38.321 V15.5.0 (Mar. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15). [cited by applicant]
3GPP TS 38.331 V15.5.1 (Apr. 2019), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15). [cited by applicant]
R1-19xxxxx 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Feature lead summary #2 on Cross-carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1904112 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: vivo, Title: Cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1904154 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: ZTE Corporation, Title: Discussion on cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1905032 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Qualcomm Incorporated, Title: Cross-slot scheduling power saving techniques. [cited by applicant]
R1-1905154 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: ASUSTek, Title: Cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1905279 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Qualcomm Incorporated, Title: Cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1905756 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Feature lead summary #2 on Cross-carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1906017 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Huawei, HiSilicon, Title: Remaining details for cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1906183 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: vivo, Title: Remaining details for cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1906291 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Oppo, Title: On Cross-carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1906311 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: CATT, Title: Discussion on cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1906359 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Spreadtrum Communications, Title: Discussion on cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1906420 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: ZTE Corporation, Title: Discussion on cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1906527 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: CMCC, Title: Discussion on cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1906827 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Intel Corporation, Title: Discussion on cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1906913 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Samsung, Title: Cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1907065 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Nokia, Title: [96b-NR-09] Email discussion summary on cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1907066 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Feature lead summary on Cross-carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1907068 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Remaining details of cross-carrier scheduling with mixed numerologies. [cited by applicant]
R1-1907304 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Qualcomm Incorporated, Title: Cross-Carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1907331 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Ericsson, Title: Cross-carrier scheduling with different numerologies. [cited by applicant]
R1-1907557 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: KT Corp., Title: On Cross-carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1907759 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Feature lead summary #2 on Cross-carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1907855 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Feature lead summary #3 on Cross-carrier Scheduling with Different Numerologies. [cited by applicant]
R1-1905142 3GPP TSG RAN WG2 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Ericsson, Title: Cross-carrier scheduling with different numerologies. [cited by applicant]
Dec. 1, 2020—European Search Report—20183737.4. [cited by applicant]
R1-1807071, 3GPP TSG RAN WG1 Meeting #93, Busan, Korea, May 21-25, 2018, Source: NTT Docomo, Inc., Title: Remaining Issues CA and type1 HARQ-ACK codebook. [cited by applicant]
R1-1903206, 3GPP TSG RAN WG1 Meeting #96, Athens, Greece, Feb. 25-Mar. 1, 2019, Source: Huawei, HiSilicon, Title: Clarification on HARQ-ACK codebook and PUCCH resource determination. [cited by applicant]
R1-1813114, 3GPP TSG RAN WG1 Meeting #95, Spokane, USA, Nov. 12-16, 2018, Source: Nokia, Nokia Shanghai Bell, Title: On UCI Enhancements for URLLC. [cited by applicant]
Feb. 13, 2023—European Office Action—20183737.4. [cited by applicant]