IP Library Granted Patent US 12,199,777
Granted Patent B2
US 12,199,777 · App. 18/375,660 · Granted Jan 14, 2025

URLLC HARQ processes

Inventors: Alireza Babaei (Fairfax, VA); Esmael Hejazi Dinan (McLean, VA); Yunjung Yi (Vienna, VA); Hua Zhou (Vienna, VA); Ali Cagatay Cirik (Chantilly, VA); Kai Xu (Great Falls, VA); Youngwoo Kwak (Woodbury, NY); Hyoungsuk Jeon (Centreville, VA); Nazanin Rastegardoost (McLean, VA)
Assignee: HONOR DEVICE CO., LTD.
H04L1/1812H04L1/1861H04L1/1893H04W72/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,199,777
App. No.
18/375,660
Granted
Jan 14, 2025
Kind
B2
Abstract

A wireless device receives downlink control information (DCI) comprising a first HARQ process identifier and a resource assignment. The first HARQ process identifier indicates a first HARQ process of HARQ processes. The wireless device transmits, using the resource assignment and based on a second HARQ process identifier, a transport block associated with a second HARQ process, of the HARQ processes. The second HARQ process identifier indicates the second HARQ process and is based on the first HARQ process identifier and a HARQ process identifier offset.

Claims (39)

1. A wireless device, comprising:

one or more processors; and

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

receive downlink control information (DCI) comprising a first hybrid automatic repeat request (HARQ) process identifier and a resource assignment, wherein the first HARQ process identifier indicates a first HARQ process of HARQ processes; and

transmit, using the resource assignment and based on a second HARQ process identifier, a transport block associated with a second HARQ process, of the HARQ processes, wherein the second HARQ process identifier:

indicates the second HARQ process; and

is based on the first HARQ process identifier and a HARQ process identifier offset.

2. The wireless device of claim 1 , wherein the second HARQ process identifier is further based on a summation of the first HARQ process identifier and the HARQ process identifier offset.

3. The wireless device of claim 1 , wherein the instructions further cause the wireless device to receive one or more configuration parameters indicating the HARQ processes.

4. The wireless device of claim 3 , wherein the one or more configuration parameters further indicate a parameter of a size of a DCI field, indicating the first HARQ process identifier, of a DCI format, wherein the DCI is based on the DCI format.

5. The wireless device of claim 1 , wherein the instructions further cause the wireless device to receive a second DCI comprising a third HARQ process identifier and a second resource assignment, wherein the third HARQ process identifier indicates the third HARQ process of the HARQ processes, and wherein the second DCI indicates to retransmit the transport block.

6. The wireless device of claim 5 , wherein the instructions further cause the wireless device to retransmit, using the second resource assignment and based on the third HARQ process identifier, the transport block based on the third HARQ process.

7. The wireless device of claim 5 , wherein the second DCI further indicates transmission of the transport block is based on a configured grant resource.

8. The wireless device of claim 1 , wherein the DCI corresponds to a first type of service.

9. The wireless device of claim 8 , wherein the instructions further cause the wireless device to determine the first type of service based on at least one of:

a radio network temporary identifier associated with the DCI;

a format of the DCI; or

a size of the DCI.

10. The wireless device of claim 8 , wherein the first type of service comprises ultra reliable low latency communications.

11. A base station, comprising:

one or more processors; and

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

transmit downlink control information (DCI) comprising a first hybrid automatic repeat request (HARQ) process identifier and a resource assignment, wherein the first HARQ process identifier indicates a first HARQ process of HARQ processes; and

receive, based on the resource assignment and a second HARQ process identifier, a transport block associated with a second HARQ process, of the HARQ processes, wherein the second HARQ process identifier:

indicates the second HARQ process; and

is based on the first HARQ process identifier and a HARQ process identifier offset.

12. The base station of claim 11 , wherein the second HARQ process identifier is further based on a summation of the first HARQ process identifier and the HARQ process identifier offset.

13. The base station of claim 11 , wherein the instructions further cause the base station to transmit one or more configuration parameters indicating the HARQ processes.

14. The base station of claim 13 , wherein the one or more configuration parameters further indicate a parameter of a size of a DCI field, indicating the first HARQ process identifier, of a DCI format, wherein the DCI is based on the DCI format.

15. The base station of claim 11 , wherein the instructions further cause the base station to transmit a second DCI comprising a third HARQ process identifier and a second resource assignment, wherein the third HARQ process identifier indicates the third HARQ process of the HARQ processes, and wherein the second DCI indicates to retransmit the transport block.

16. The base station of claim 15 , wherein the instructions further cause the base station to transmit, using the second resource assignment and based on the third HARQ process identifier, the transport block based on the third HARQ process.

17. The base station of claim 15 , wherein the second DCI further indicates transmission of the transport block is based on a configured grant resource.

18. The base station of claim 11 , wherein the DCI corresponds to a first type of service.

19. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to:

receive downlink control information (DCI) comprising a first hybrid automatic repeat request (HARQ) process identifier and a resource assignment, wherein the first HARQ process identifier indicates a first HARQ process of HARQ processes; and

transmit, using the resource assignment and based on a second HARQ process identifier, a transport block associated with a second HARQ process, of the HARQ processes, wherein the second HARQ process identifier:

indicates the second HARQ process; and

is based on the first HARQ process identifier and a HARQ process identifier offset.

20. The non-transitory computer-readable medium of claim 19 , wherein the second HARQ process identifier is further based on a summation of the first HARQ process identifier and the HARQ process identifier offset.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 4, 2023
From: OFINNO, LLC
To: HONOR DEVICE CO., LTD.
Reel/Frame 065749/0288 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 18, 2023
From: BABAEI, ALIREZA; DINAN, ESMAEL HEJAZI; YI, YUNJUNG; ZHOU, HUA; CIRIK, ALI CAGATAY; XU, KAI; KWAK, YOUNGWOO; JEON, HYOUNGSUK; RASTEGARDOOST, NAZANIN
To: OFINNO, LLC
Reel/Frame 065266/0568 →
Continuity (4)
Continuation 17970144 · Oct 20, 2022
Continuation 16988746 · Aug 10, 2020
Provisional Application 62886833 · Aug 14, 2019
Related Publication 20240039661A1 · Feb 1, 2024
References Cited (57)
US 20100260130A1 · Earnshaw · 2010 [cited by examiner]
US 20130010720A1 · Lohr et al. · 2013 [cited by applicant]
US 20130121288A1 · Wang et al. · 2013 [cited by applicant]
US 20190045489A1 · He et al. · 2019 [cited by applicant]
US 20200229182A1 · Khoshnevisan · 2020 [cited by examiner]
US 20200266933A1 · Lin · 2020 [cited by applicant]
US 20200313807A1 · Salem · 2020 [cited by examiner]
US 20200413289A1 · Akkarakaran et al. · 2020 [cited by applicant]
US 20210099254A1 · Babaei et al. · 2021 [cited by applicant]
US 20210099257A1 · Joseph et al. · 2021 [cited by applicant]
US 20210204297A1 · Wu et al. · 2021 [cited by applicant]
US 20210227570A1 · Park et al. · 2021 [cited by applicant]
US 20220140954A1 · Kim et al. · 2022 [cited by applicant]
US 20220209924A1 · Yang · 2022 [cited by examiner]
US 20220376844A1 · Muruganathan · 2022 [cited by examiner]
EP 3945692A1 · 2022 [cited by applicant]
EP 4090089A1 · 2022 [cited by examiner]
WO WO2021230644A1 · 2021 [cited by examiner]
WO WO2022255925A1 · 2022 [cited by examiner]
3GPP TSG-RAN WG1 Meeting #97, Reno, Nevada, US, May 13-17, 2019, Tdoc R1-1906091, Agenda item: 7.2.6.1, Source: Ericsson, Title: PDCCH Enhancements for NR URLLC. (Year: 2019). [cited by examiner]
3GPP TS 38.211 V15.6.0 (Jun. 2019); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical channels and modulation; (Release 15). [cited by applicant]
3GPP TS 38.212 V15.6.0 (Jun. 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.6.0 (Jun. 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.6.0 (Jun. 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.6.0 (Jun. 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.6.0 (Jun. 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.6.0 (Jun. 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-190xxxx; 3GPP TSG RAN WG1 Meeting #98; Prague, Czech Rep, Aug. 26-30, 2019; Source: MCC Support; Title: Draft Report of 3GPP TSG RAN WG1 #97 v0.3.0 (Reno, USA, May 13-17, 2019); Document for: Comments. [cited by applicant]
R1-1906633; 3GPP TSG RAN WG1 #97; Reno, Nevada, May 13-May 17, 2019; Agenda Item: 7.2.6.1 Source: China Unicom; Title: PDCCH enhancements for URLLC; Document for: Discussion and decision. [cited by applicant]
R1-1906057; 3GPP TSG RAN WG1 Meeting #97; Reno, USA, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: Huawei, HiSilicon; Title: PDCCH enhancements for URLLC; Document for: Discussion and Decision. [cited by applicant]
R1-1906091; 3GPP TSG RAN WG1 Meeting #97; Reno, Nevada, US, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: Ericsson; Title: PDCCH Enhancements for NR URLLC; Document for: Discussion, Decision. [cited by applicant]
R1-1906146; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Source: vivo; Title: PDCCH enhancements for URLLC; Agenda Item: 7.2.6.1; Document for: Discussion and Decision. [cited by applicant]
R1-1906211; 3GPP TSG RAN WG1 #97; Reno, US, May 13-17, 2019; Source: NTT DOCOMO, INC.; Title: PDCCH enhancements for URLLC; Agenda Item: 7.2.6.1; Document for: Discussion and Decision. [cited by applicant]
R1-1906327; 3GPP TSG RAN WG1 Meeting #97; Reno, USA, May 13-17, 2019; Source: CATT; Title: PDCCH enhancements for URLLC; Agenda Item: 7.2.6.1; Document for: Discussion and Decision. [cited by applicant]
R1-1906357; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Agenda item: 7.2.6.1; Source: Spreadtrum Communications; Title: Discussion on PDCCH enhancements for URLLC; Document for: Discussion and decision. [cited by applicant]
R1-1906409; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Source: ZTE; Title: On PDCCH enhancements for NR URLLC; Agenda item: 7.2.6.1; Document for: Discussion and Decision. [cited by applicant]
R1-1906447; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Source: OPPO; Title: PDCCH enhancement for URLLC; Agenda Item: 7.2.6.1; Document for: Discussion and Decision. [cited by applicant]
R1-1906565; 3GPP TSG RAN WG1 Meeting #97; Reno, USA, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: MediaTek Inc.; Title: PDCCH enhancements for eURLLC; Document for: Discussion and Decision. [cited by applicant]
R1-1906664; 3GPP TSG RAN WG1 #97; Reno, NV, US, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: LG Electronics; Title: PDCCH enhancements for NR URLLC; Document for: Discussion and decision. [cited by applicant]
R1-1906751; 3GPP TSG RAN WG1#97; Reno, Nevada, US, May 13-17, 2019; Agenda item: 7.2.6.1; Source: Nokia, Nokia Shanghai Bell; Title: On PDCCH Enhancements for NR URLLC; Document for: Discussion and Decision. [cited by applicant]
R1-1906806; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Source: Intel Corporation; Title: On PDCCH enhancements for eURLLC; Agenda item: 7.2.6.1; Document for: Discussion and Decision. [cited by applicant]
R1-1906865; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Source: Panasonic; Title: PDCCH enhancements for NR URLLC; Agenda Item: 7.2.6.1; Document for: Discussion. [cited by applicant]
R1-1906955; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Agenda item: 7.2.6.1; Source: Samsung: Title: DL Control for URLLC; Document for: Discussion and Decision. [cited by applicant]
R1-1907110; 3GPP TSG RAN WG1 #97; Reno, USA, Apr. 13-17, 2019; Agenda Item: 7.2.6.1; Source: InterDigital Inc.; Title: On PDCCH Enhancements for eURLLC; Document for: Discussion and Decision. [cited by applicant]
R1-1907168; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Agenda item: 7.2.6.1; Source: AT&T; Title: PDCCH Enhancements for eURLLC; Document for: Discussion/Decision. [cited by applicant]
R1-1907241; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: Motorola Mobility, Lenovo; Title: PDCCH Enhancements for URLLC; Document for: Discussion. [cited by applicant]
R1-1907281; 3GPP TSG RAN WG1 Meeting #97; May 13-17, 2019; Reno, Nevada, U.S.A.; Agenda item: 7.2.6.1; Source: Qualcomm Incorporated; Title: PDCCH Enhancements for eURLLC; Document for: Discussion/Decision. [cited by applicant]
R1-1907354; 3GPP TSG RAN WG1 Meeting #97; Reno, Nevada, US, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: TCL Communication; Title: Ambiguity between PDCCH AL 8 and AL 16; Document for: Discussion and decision. [cited by applicant]
R1-1907384; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Source: WILUS Inc.; Title: On DCI enhancement for NR URLLC; Agenda item: 7.2.6.1; Document for: Discussion/Decision. [cited by applicant]
R1-1907448; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: Sequans; Title: PDCCH enhancements for URLLC; Document for: Discussion and decision. [cited by applicant]
R1-1907663; 3GPP TSG RAN WG1 Meeting #97; Reno, USA, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: Huawei; Title: Summary of 7.2.6.1 PDCCH enhancements; Document for: Discussion and decision. [cited by applicant]
R1-1907763; 3GPP TSG RAN WG1 Meeting #97; Reno, USA, May 13-17, 2019; Agenda Item: 7.2.6.1; Source: Huawei; Title: Summary of Monday offline discussion on PDCCH enhancements; Document for: Discussion and decision. [cited by applicant]
R1-1905953; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Title: Discussion on Scheduling and HARO for NR-U; Source: ZTE, Sanechips; Agenda item: 7.2.2.2.3.; Document for: Discussion and Decision. [cited by applicant]
R1-1900245; 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901; Taipei, Taiwan, Jan. 21-25, 2019; Agenda item: 7.2.2.2.3; Source: Fujitsu; Title: Scheduling/HARO enhancements for NR-U; Document for: Discussion/Decision. [cited by applicant]
R1-1814146; 3GPP TSG RAN WG1 Meeting #95; Spokane, USA, Nov. 12-16, 2018; Agenda item: 7.2.2.4.3; Source: Huawei, HiSilicon; Title: Feature lead Summary of HARO enhancements in N R-U; Document for: Discussion and decisi… [cited by applicant]
R1-1806522; 3GPP TSG RAN WG1 Meeting #93; Busan, Korea, May 21-25, 2018; Source: Intel Corporation; Title: Remaining details on Scheduling and HARO; Agenda item: 7.1.3.3.2.; Document for: Discussion and Decision. [cited by applicant]
R1-1907652; 3GPP TSG RAN WG1 Meeting #97; Reno, USA, May 13-17, 2019; Agenda item: 7.2.2.2.3; Source: Huawei; Title: Feature lead summary of HARQ enhancements for NR-U; Document for: Discussion and Decision. [cited by applicant]