IP Library Granted Patent US 12,396,017
Granted Patent B2
US 12,396,017 · App. 18/407,057 · Granted Aug 19, 2025

Communication and data processing in wireless communications

Inventors: Hua Zhou (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Alireza Babaei (Fairfax, VA); Ali Cagatay Cirik (Chantilly, VA); Hyoungsuk Jeon (Centreville, VA); Yunjung Yi (Vienna, VA); Youngwoo Kwak (Woodbury, NY); Kai Xu (Great Falls, VA); Kyungmin Park (Vienna, VA)
Assignee: Ofinno, LLC
H04W72/53H04L1/1819H04L1/1874H04L5/0055H04W72/1263H04W72/23H04W72/56
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,396,017
App. No.
18/407,057
Granted
Aug 19, 2025
Kind
B2
Abstract

Wireless communications may be used to support data processing. A plurality of resources may be indicated for a wireless device to use to communicate and/or process data. Data may be received and processed based on groups of the plurality of resources to be used. For example, the plurality of resources to be used may be associated with different resource groups.

Claims (88)

1. A method comprising:

receiving, by a wireless device and via a channel associated with a first control resource set (CORESET) group, a first message indicating a first scheduled transmission of a first downlink signal;

after receiving the first message, receiving, via a channel associated with a second CORESET group different from the first CORESET group, a second message indicating a second scheduled transmission of a second downlink signal, wherein the second scheduled transmission starts earlier than an end of the first scheduled transmission; and

receiving the first downlink signal and the second downlink signal, wherein the second downlink signal is received earlier than an end of reception of the first downlink signal.

2. The method of claim 1 , wherein the receiving the second downlink signal starts earlier than a start of the receiving the first downlink signal.

3. The method of claim 1 , wherein the receiving the second downlink signal starts earlier than completion of the receiving the first downlink signal.

4. The method of claim 1 , wherein the receiving the second downlink signal is completed prior to a start of the receiving the first downlink signal.

5. The method of claim 1 , wherein completion of the receiving the second downlink signal is later than completion of the receiving the first downlink signal.

6. The method of claim 1 , further comprising:

transmitting a first uplink signal associated with the first downlink signal and a second uplink signal associated with the second downlink signal.

7. The method of claim 6 , wherein the transmitting the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal comprises: based on the first CORESET group and the second CORESET group being different CORESET groups, transmitting a second acknowledgement prior to transmitting a first acknowledgment.

8. The method of claim 6 , wherein the transmitting the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal comprises: based on the first CORESET group and the second CORESET group being different CORESET groups, transmitting a second acknowledgement after transmitting a first acknowledgment.

9. The method of claim 6 , wherein the first uplink signal comprises at least one of:

a first acknowledgment for the first downlink signal; or

a first uplink shared channel signal comprising the first downlink signal.

10. The method of claim 1 , wherein the first CORESET group and the second CORESET group are CORESETs of a same cell.

11. The method of claim 1 , further comprising:

based on the first CORESET group and the second CORESET group being different CORESET groups, processing the first downlink signal after processing the second downlink signal.

12. The method of claim 1 , wherein:

receiving the first downlink signal comprises receiving the first downlink signal based on the first CORESET group and the second CORESET group being different CORESET groups and based on the first message; and

receiving the second downlink signal comprises receiving the second downlink signal based on the first CORESET group and the second CORESET group being different CORESET groups and based on the second message.

13. The method of claim 1 , wherein the receiving the first downlink signal comprises receiving the first downlink signal based on a first CORESET and a third CORESET being in a same CORESET group, the method further comprising:

based on the first CORESET and the third CORESET being in the same CORESET group, dropping a third downlink signal indicated by a third message associated with the third CORESET.

14. The method of claim 13 , wherein the dropping the third downlink signal comprises at least one of:

skipping allocating the third downlink signal to a second hybrid automatic repeat request (HARQ) process;

skipping decoding the third downlink signal; or

skipping generating a third acknowledgement for the third downlink signal.

15. A method comprising:

sending, by a base station and via a channel associated with a first control resource set (CORESET) group, a first message indicating a first scheduled transmission of a first downlink signal;

after sending the first message, sending, via a channel associated with a second CORESET group different from the first CORESET group, a second message indicating a second scheduled transmission of a second downlink signal, wherein the second scheduled transmission starts earlier than an end of the first scheduled transmission; and

sending the first downlink signal and the second downlink signal, wherein the second downlink signal is sent earlier than an end of sending of the first downlink signal.

16. The method of claim 15 , wherein the sending the second downlink signal starts earlier than a start of the sending the first downlink signal.

17. The method of claim 15 , wherein the sending the second downlink signal starts earlier than completion of the sending the first downlink signal.

18. The method of claim 15 , wherein the sending the second downlink signal is completed prior to a start of the sending the first downlink signal.

19. The method of claim 15 , wherein completion of the sending the second downlink signal is later than completion of the sending the first downlink signal.

20. The method of claim 15 , further comprising:

receiving a first uplink signal associated with the first downlink signal and a second uplink signal associated with the second downlink signal.

21. The method of claim 20 , wherein the receiving the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal comprises: based on the first CORESET group and the second CORESET group being different CORESET groups, receiving a second acknowledgement prior to receiving a first acknowledgment.

22. The method of claim 20 , wherein the receiving the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal comprises: based on the first CORESET group and the second CORESET group being different CORESET groups, receiving a second acknowledgement after receiving a first acknowledgment.

23. The method of claim 15 , wherein the first CORESET group and the second CORESET group are CORESETs of a same cell.

24. The method of claim 15 , wherein:

the sending the first downlink signal comprises sending the first downlink signal based on the first CORESET group and the second CORESET group being different CORESET groups and based on the first message; and

the sending the second downlink signal comprises sending the second downlink signal based on the first CORESET group and the second CORESET group being different CORESET groups and based on the second message.

25. 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 channel associated with a first control resource set (CORESET) group, a first message indicating a first scheduled transmission of a first downlink signal;

after receiving the first message, receive, via a channel associated with a second CORESET group different from the first CORESET group, a second message indicating a second scheduled transmission of a second downlink signal, wherein the second scheduled transmission starts earlier than an end of the first scheduled transmission; and

receive the first downlink signal and the second downlink signal, wherein the second downlink signal is received earlier than an end of reception of the first downlink signal.

26. The wireless device of claim 25 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to start receiving the second downlink signal earlier than a start of the receiving the first downlink signal.

27. The wireless device of claim 25 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to start receiving the second downlink signal earlier than completion of the receiving the first downlink signal.

28. The wireless device of claim 25 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to complete receiving the second downlink signal prior to a start of the receiving the first downlink signal.

29. The wireless device of claim 25 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to complete receiving the second downlink signal later than completion of the receiving the first downlink signal.

30. The wireless device of claim 25 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to transmit a first uplink signal associated with the first downlink signal and a second uplink signal associated with the second downlink signal.

31. The wireless device of claim 30 , wherein the instructions, when executed by the one or more processors, cause the wireless device to transmit the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal by transmitting, based on the first CORESET group and the second CORESET group being different CORESET groups, a second acknowledgement prior to transmitting a first acknowledgment.

32. The wireless device of claim 30 , wherein the instructions, when executed by the one or more processors, cause the wireless device to transmit the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal by transmitting, based on the first CORESET group and the second CORESET group being different CORESET groups, a second acknowledgement after transmitting a first acknowledgment.

33. The wireless device of claim 30 , wherein the first uplink signal comprises at least one of:

a first acknowledgment for the first downlink signal; or

a first uplink shared channel signal comprising the first downlink signal.

34. The wireless device of claim 25 , wherein the first CORESET group and the second CORESET group are CORESETs of a same cell.

35. The wireless device of claim 25 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to process, based on the first CORESET group and the second CORESET group being different CORESET groups, the first downlink signal after processing the second downlink signal.

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

receive the first downlink signal based on the first CORESET group and the second CORESET group being in different CORESET groups and based on the first message; and

receive the second downlink signal based on the first CORESET group and the second CORESET group being in different CORESET groups and based on the second message.

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

receive the first downlink signal based on a first CORESET and a third CORESET being in a same CORESET group; and

based on the first CORESET and the third CORESET being in the same CORESET group, drop a third downlink signal indicated by a third message associated with the third CORESET.

38. The wireless device of claim 37 , wherein the instructions, when executed by the one or more processors, cause the wireless device to drop the third downlink signal by performing at least one of:

skipping allocating the third downlink signal to a second hybrid automatic repeat request (HARQ) process;

skipping decoding the third downlink signal; or

skipping generating a third acknowledgement for the third downlink signal.

39. A base station comprising:

one or more processors; and

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

send, via a channel associated with a first control resource set (CORESET) group, a first message indicating a first scheduled transmission of a first downlink signal;

after sending the first message, send, via a channel associated with a second CORESET group different from the first CORESET group, a second message indicating a second scheduled transmission of a second downlink signal, wherein the second scheduled transmission starts earlier than an end of reception of the first scheduled transmission;

send the first downlink signal and the second downlink signal, wherein the second downlink signal is sent earlier than an end of sending the first downlink signal.

40. The base station of claim 39 , wherein the instructions, when executed by the one or more processors, further cause the base station to start sending the second downlink signal earlier than a start of the sending the first downlink signal.

41. The base station of claim 39 , wherein the instructions, when executed by the one or more processors, further cause the base station to start sending the second downlink signal earlier than completion of the sending the first downlink signal.

42. The base station of claim 39 , wherein the instructions, when executed by the one or more processors, further cause the base station to complete sending the second downlink signal prior to a start of the sending the first downlink signal.

43. The base station of claim 39 , wherein the instructions, when executed by the one or more processors, further cause the base station to complete sending the second downlink signal later than completion of the sending the first downlink signal.

44. The base station of claim 39 , wherein the instructions, when executed by the one or more processors, further cause the base station to receive a first uplink signal associated with the first downlink signal and a second uplink signal associated with the second downlink signal.

45. The base station of claim 44 , wherein the instructions, when executed by the one or more processors, cause the base station to receive the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal by receiving, based on the first CORESET group and the second CORESET group being different CORESET groups, a second acknowledgement prior to receiving a first acknowledgment.

46. The base station of claim 44 , wherein the instructions, when executed by the one or more processors, cause the base station to receive the first uplink signal associated with the first downlink signal and the second uplink signal associated with the second downlink signal by receiving, based on the first CORESET group and the second CORESET group being different CORESET groups, a second acknowledgement after receiving a first acknowledgment.

47. The base station of claim 39 , wherein the first CORESET group and the second CORESET group are CORESETs of a same cell.

48. The base station of claim 39 , wherein the instructions that, when executed by the one or more processors, cause the base station to:

send the first downlink signal based on the first CORESET group and the second CORESET group being in different CORESET groups and based on the first message; and

send the second downlink signal based on the first CORESET group and the second CORESET group being in different CORESET groups and based on the second message.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 19, 2024
From: COMCAST CABLE COMMUNICATIONS, LLC
To: OFINNO, LLC
Reel/Frame 069643/0230 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; CIRIK, ALI CAGATAY; JEON, HYOUNGSUK; YI, YUNJUNG; KWAK, YOUNGWOO; XU, KAI; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068762/0021 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; BABAEI, ALIREZA; CIRIK, ALI CAGATAY; JEON, HYOUNGSUK; YI, YUNJUNG; KWAK, YOUNGWOO; XU, KAI; PARK, KYUNGMIN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068762/0036 →
Continuity (4)
Continuation 17939561 · Sep 7, 2022
Continuation 16935648 · Jul 22, 2020
Provisional Application 62877038 · Jul 22, 2019
Related Publication 20240205952A1 · Jun 20, 2024
References Cited (60)
US 20100056079A1 · Onggosanusi et al. · 2010 [cited by applicant]
US 20180279331A1 · Shaheen et al. · 2018 [cited by applicant]
US 20180279353A1 · Shaheen et al. · 2018 [cited by applicant]
US 20180338307A1 · Feng · 2018 [cited by examiner]
US 20190246378A1 · Islam · 2019 [cited by examiner]
US 20200015250A1 · Yang et al. · 2020 [cited by applicant]
US 20200037314A1 · Xiong et al. · 2020 [cited by applicant]
US 20200053748A1 · Hosseini et al. · 2020 [cited by applicant]
US 20200053820A1 · Chin et al. · 2020 [cited by applicant]
US 20200092068A1 · Yang et al. · 2020 [cited by applicant]
US 20200351903A1 · Sarkis et al. · 2020 [cited by applicant]
US 20210014883A1 · Khoshnevisan · 2021 [cited by examiner]
US 20220201697A1 · Yamamoto et al. · 2022 [cited by applicant]
WO 2018204491A1 · 2018 [cited by applicant]
WO 2018228487A1 · 2018 [cited by applicant]
WO 2019031850A1 · 2019 [cited by applicant]
R1-1905833 3GPP TSG-RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Qualcomm Incorporated, Title: Summary of Enhancements to Scheduling/HARQ. [cited by applicant]
R1-1808224 3GPP TSG RAN WG1 Meeting #94, Gothenburg, Sweden, Aug. 20-24, 2018, Source: vivo, Title: Remaining issues on PDCCH. [cited by applicant]
R1-1810486 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: Fraunhofer HHI, Fraunhofer IIS, Title: Scheduling/HARQ Processing Timeline Enhancements for NR URLLC. [cited by applicant]
R1-1810660 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: Nokia, Nokia Shanghai Bell, Title: On the L1 enhancements for NR URLLC. [cited by applicant]
R1-1810670 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Enhancements to scheduling/HARQ/CSI processing timeline for NR URLLC. [cited by applicant]
R1-1810879 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: Samsung, Title: Layer 1 enhancements for URLLC. [cited by applicant]
R1-1811378 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: NTT Docomo, Inc., Title: Layer 1 enhancements for NR URLLC. [cited by applicant]
R1-1811391 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: Institute for Information Industry (III), Title: HARQ-ACK feedback enhancement for URLLC. [cited by applicant]
R1-1811522 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: CAICT, Title: L1 enhancements to support URLLC. [cited by applicant]
R2-1816064 3GPP TSG RAN WG1 Meeting #94bis, Chengdu, China, Oct. 8-12, 2018, Source: RAN2, Title: LS on the search space of cross-carrier scheduling. [cited by applicant]
R1-1812885 3GPP TSG RAN WG1 Meeting #95, Spokane, USA, Nov. 12-16, 2018, Source: CMCC, China Southern Power Grid, Title: Discussion on out-of-order scheduling and HARQ. [cited by applicant]
R1-1813952 3GPP TSG RAN WG1 Meeting #95, Spokane, USA, Nov. 12-16, 2018, Source: RAN2, Title: Reply LS on MIMO layer configuration. [cited by applicant]
R1-1814117 3GPP TSG RAN WG1 Meeting #95, Spokane, USA, Nov. 12-16, 2018, Source: NTT Docomo, Inc., Title: On search space configuration for cross-carrier scheduling. [cited by applicant]
R1-1903535 3GPP TSG-RAN WG1 #96, Athens, Greece, Feb. 25-Mar. 1, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Summary of Wednesday offline discussion on UL/DL intra-UE prioritization/multiplexing. [cited by applicant]
R1-1904237 3GPP TSG-RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Sony, Title: Intra-UE multiplexing/prioritisation under Out-of-Order Scheduling. [cited by applicant]
R1-1905683 3GPP TSG-RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Title: Offline Note on Monday for M-TRP. [cited by applicant]
R1-1905915 3GPP TSG-RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Ericsson, Title: Summary of email discussion [96b-NR-11]. [cited by applicant]
R1-1906060 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Huawei, HiSilicon, Title: Enhancements to scheduling/HARQ. [cited by applicant]
R1- 1906094 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Ericsson, Title: Scheduling/ HARQ Enhancements for NR URLLC. [cited by applicant]
R1-1906149 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: vivo, Title: Enhancement for Scheduling/HARQ. [cited by applicant]
R1-1906214 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: NTT Docomo, Inc., Title: Enhancements to scheduling/HARQ for URLLC. [cited by applicant]
R1-1906330 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: CATT, Title: Discussion on out-of-order scheduling/HARQ. [cited by applicant]
R1- 1906380 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Spreadtrum Communications, Title: Discussion on enhancements to scheduling and HARQ for URLLC. [cited by applicant]
R1-1906412 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: ZTE, Title: On scheduling/ HARQ enhancements for NR URLLC. [cited by applicant]
R1-1906519 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: CMCC, China Southern Power Grid, Title: Discussion on enhancements on scheduling and HARQ. [cited by applicant]
R1-1906568 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: MediaTek Inc., Title: Enhancements to eURLLC scheduling/HARQ. [cited by applicant]
R1-1906667 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: LG Electronics, Title: Enhancements to scheduling/HARQ for NR URLLC. [cited by applicant]
R1-1906754 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Nokia, Nokia Shanghai Bell, Title: Discussion on enhancements to scheduling/HARQ for NR URLLC. [cited by applicant]
R1-1906809 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Intel Corporation, Title: On scheduling/HARQ enhancements for eURLLC. [cited by applicant]
R1-1906843 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Sony, Title: Considerations in scheduling enhancements for eURLLC. [cited by applicant]
R1-1906867 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Panasonic, Title: Discussion on scheduling/HARQ enhancement for URLLC. [cited by applicant]
R1-1906958 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Samsung, Title: On enhancements to scheduling/HARQ for eURLLC. [cited by applicant]
R1-1907195 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: InterDigital Inc., Title: Enhancements to Scheduling/HARQ for eURLLC. [cited by applicant]
R1-1907222 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Sharp, Title: Discussion on enhancements to scheduling/HARQ. [cited by applicant]
R1-1907284 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Qualcomm Incorporated, Title: Enhancements to Scheduling and HARQ for eURLLC. [cited by applicant]
R1-1907350 3GPP TSG RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Institute for Information Industry (III), Title: Discussion on out-of-order scheduling/HARQ. [cited by applicant]
R1-190abcd 3GPP TSG-RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Huawei, HiSilicon, Title: Summary of AI: 7.2.8.2 Enhancements on Multi-TRP/Panel Transmission of Offline Discussion. [cited by applicant]
R1-1907289 3GPP TSG-RAN WG1 Meeting #97, Reno, USA, May 13-17, 2019, Source: Qualcomm Incorporated, Title: Multi-TRP Enhancements. [cited by applicant]
R1-1904313 3GPP TSG RAN WG1 Meeting #96bis, Xi'an, China, Apr. 8-12, 2019, Source: Intel Corporation, Title: On multi-TRP/multi-panel transmission. [cited by applicant]
Nov. 20, 2020—EP Search Report—EP 20187170.4. [cited by applicant]
Dec. 18, 2020—Extended European Search Report—EP 20187137.3. [cited by applicant]
R1-1901917 3GPP TSG RAN WG1 Meeting #96, Athens, Greece, Feb. 25-Mar. 1, 2019, Title: “On intra-UE DL/UL prioritization for NR URLLC”, Source: Nokia et. al, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg%5… [cited by applicant]
May 30, 2022—EP Office Action—EP App. No. 20187137.3. [cited by applicant]
Feb. 9, 2023—EP Office Action—EP App No. 20187170.4. [cited by applicant]