IP Library › Granted Patent US 12,402,143
Granted Patent B2
US 12,402,143 · App. 18/110,759 · Granted Aug 26, 2025

Interrupted transmission in control channel repetition

Inventors: Ali Cagatay Cirik (Chantilly, VA); Esmael Hejazi Dinan (McLean, VA); Yunjung Yi (Vienna, VA); Hua Zhou (Vienna, VA); Jonghyun Park (Syosset, NY)
Assignee: Ofinno, LLC
H04W72/23H04L1/0038H04L1/0061H04L1/1664H04L1/1671H04L1/1822H04L1/1861H04W24/00
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,402,143
App. No.
18/110,759
Granted
Aug 26, 2025
Kind
B2
Abstract

A wireless device may receive a physical downlink control channel (PDCCH) with first downlink control information (DCI) scheduling an uplink transmission. The wireless device may receive, via at least one PDCCH monitoring occasion of PDCCH monitoring occasions, a repetition of second DCI that indicates cancelation of one or more symbols of the uplink transmission. The wireless device may cancel the one or more symbols of the uplink transmission based on a last symbol of the PDCCH reception with the first DCI being earlier than a starting symbol of the PDCCH monitoring occasions.

Claims (51)

1. 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 a radio resource control (RRC) message comprising one or more configuration parameters, wherein:

the one or more configuration parameters indicate two search space sets for physical downlink control channel (PDCCH) repetition; and

each search space set of the two search space sets is associated with a respective control resource set (coreset) of two coresets;

receive, in one or more first symbols, a PDCCH with first downlink control information (DCI) scheduling an uplink transmission;

receive, via at least one PDCCH monitoring occasion of PDCCH monitoring occasions of PDCCH candidates corresponding to the two search space sets, second DCI that indicates cancelation of one or more symbols of the uplink transmission, wherein the second DCI is being repeated in the PDCCH monitoring occasions; and

cancel, based on a last symbol of the PDCCH reception with the first DCI being earlier than a starting symbol of the PDCCH monitoring occasions, the one or more symbols of the uplink transmission, wherein the last symbol is a latest symbol in time among the one or more first symbols.

2. The wireless device of claim 1 , wherein the two coresets comprise:

a first coreset associated with a first search space set of the two search space sets; and

a second coreset associated with a second search space set of the two search space sets.

3. The wireless device of claim 2 , wherein:

a first duration of the first coreset and a second duration of the second coreset of the two coresets are the same; and

a first number of control channel elements (CCEs) of the first coreset and a second number of CCEs of the second coreset are the same.

4. The wireless device of claim 3 , wherein the PDCCH monitoring occasions are in a slot.

5. The wireless device of claim 4 , wherein the uplink transmission is at least one of:

a physical uplink shared channel (PUSCH) transmission; or

a sounding reference signal (SRS) transmission.

6. The wireless device of claim 5 , wherein the one or more configuration parameters comprise an uplink cancelation parameter for canceling the one or more symbols.

7. The wireless device of claim 6 , wherein the instructions further cause the wireless device to cancel the one or more symbols by not performing the uplink transmission in at least one symbol of the one or more symbols.

8. The wireless device of claim 7 , wherein the instructions further cause the wireless device to monitor, in the PDCCH monitoring occasions, the PDCCH candidates for a DCI format, wherein each repetition of the DCI format has the same payload.

9. The wireless device of claim 8 , wherein the instructions further cause the wireless device to:

receive a PDCCH with third DCI scheduling a second uplink transmission;

receive, via at least one second PDCCH monitoring occasion of second PDCCH monitoring occasions of second PDCCH candidates corresponding to the two search space sets, fourth DCI that indicates cancelation of one or more second symbols of the second uplink transmission; and

not canceling, based on a last symbol of the PDCCH reception with the third DCI not being earlier than a starting symbol of the second PDCCH monitoring occasions, the one or more second symbols of the second uplink transmission.

10. The wireless device of claim 9 , wherein the not cancelling the one or more second symbols of the second uplink transmission comprises performing the second uplink transmission in the one or more second symbols.

11. The wireless device of claim 1 , wherein the instructions further cause the wireless device to:

receive a PDCCH with third DCI scheduling a second uplink transmission;

receive, via at least one second PDCCH monitoring occasion of second PDCCH monitoring occasions of second DCCH candidates corresponding to the two search space sets, fourth DCI that indicates cancelation of one or more second symbols of the second uplink transmission; and

not canceling, based on a last symbol of the PDCCH reception with the third DCI not being earlier than a starting symbol of the second PDCCH monitoring occasions, the one or more second symbols of the second uplink transmission.

12. The wireless device of claim 11 , wherein the not cancelling the one or more second symbols of the second uplink transmission comprises performing the second uplink transmission in the one or more second symbols.

13. The wireless device of claim 12 , wherein the two coresets comprise:

a first coreset associated with a first search space set of the two search space sets; and

a second coreset associated with a second search space set of the two search space sets.

14. The wireless device of claim 13 , wherein:

a first duration of the first coreset and a second duration of the second coreset of the two coresets are the same; and

a first number of control channel elements (CCEs) of the first coreset and a second number of CCEs of the second coreset are the same.

15. The wireless device of claim 14 , wherein the PDCCH monitoring occasions are in a slot.

16. The wireless device of claim 15 , wherein the uplink transmission is at least one of:

a physical uplink shared channel (PUSCH) transmission; or

a sounding reference signal (SRS) transmission.

17. The wireless device of claim 1 , wherein:

a first duration of the first coreset and a second duration of the second coreset of the two coresets are the same; and

a first number of control channel elements (CCEs) of the first coreset and a second number of CCEs of the second coreset are the same.

18. The wireless device of claim 17 , wherein the one or more configuration parameters comprise an uplink cancelation parameter for canceling the one or more symbols.

19. The wireless device of claim 18 , wherein the instructions further cause the wireless device to:

receive a PDCCH with third DCI scheduling a second uplink transmission;

receive, via at least one second PDCCH monitoring occasion of second PDCCH monitoring occasions of second DCCH candidates corresponding to the two search space sets, fourth DCI that indicates cancelation of one or more second symbols of the second uplink transmission; and

not canceling, based on a last symbol of the PDCCH reception with the third DCI not being earlier than a starting symbol of the second PDCCH monitoring occasions, the one or more second symbols of the second uplink transmission.

20. The wireless device of claim 19 , wherein the not cancelling the one or more second symbols of the second uplink transmission comprises performing the second uplink transmission in the one or more second symbols.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 27, 2023
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; YI, YUNJUNG; ZHOU, HUA; PARK, JONGHYUN
To: OFINNO, LLC
Reel/Frame 063106/0843 →
Continuity (3)
Continuation PCTUS2021053071 · Oct 1, 2021
Provisional Application 63086575 · Oct 1, 2020
Related Publication 20230199787A1 · Jun 22, 2023
References Cited (50)
US 20190246395A1 · Huang et al. · 2019 [cited by applicant]
US 20200008235A1 · Sarkis et al. · 2020 [cited by applicant]
US 20200128558A1 · Lu et al. · 2020 [cited by applicant]
US 20200260391A1 · Zhou et al. · 2020 [cited by applicant]
US 20210029646A1 · Park · 2021 [cited by applicant]
US 20230156738A1 · Gao · 2023 [cited by examiner]
CA 3077014A1 · 2020 [cited by examiner]
EP 3716697A1 · 2020 [cited by applicant]
JP 2019140664A · 2019 [cited by applicant]
WO 2019190265A1 · 2019 [cited by applicant]
WO 2020166045A1 · 2020 [cited by applicant]
3GPP TS 38.212 V16.2.0 (Jun. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding; (Release 16). [cited by applicant]
3GPP TS 38.213 V16.2.0 (Jun. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control; (Release 16). [cited by applicant]
3GPP TS 38.214 V16.2.0 (Jun. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data; (Release 16). [cited by applicant]
3GPP TS 38.300 V16.1.0 (Mar. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2; (Release 16). [cited by applicant]
3GPP TS 38.321 V16.1.0 (Jul. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification; (Release 16). [cited by applicant]
3GPP TS 38.331 V16.1.0 (Jul. 2020); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification; (Release 16). [cited by applicant]
R1-2005285; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Futurewei; Title: Multi-TRP/panel for non-PDSCH; Document for: Discussion/Decision. [cited by applicant]
R1-2005364; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Source: vivo; Title: Discussion on enhancement on PDCCH, PUCCH, PUSCH in MTRP scenario; Agenda Item: 8.1.2.1; Document for: Discussion and Decision. [cited by applicant]
R1-2005455; 3GPP TSG RAN WG1 Meeting #102-e; e-Meeting, Aug. 17-28, 2020; Source: ZTE; Title: Multi-TRP enhancements for PDCCH, PUCCH and PUSCH; Agenda Item: 8.1.2.1; Document for: Discussion and Decision. [cited by applicant]
R1-2005483; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: InterDigital, Inc.; Title: Discussion on Multi-TRP Physical Channel Enhancements; Document for: Discussion and Decision. [cited by applicant]
R1-2005542; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Fujitsu; Title: Enhancements on Multi-TRP for PUCCH and PUSCH; Document for: Discussion. [cited by applicant]
R1-2005561; 3GPP TSG RAN WG1 Meeting #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Sony; Title: Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH; Document for: Discussion and Decision. [cited by applicant]
R1-2005621; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: MediaTek Inc.; Title: Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH; Document for: Discussion and Decision. [cited by applicant]
R1-2005684; 3GPP TSG RAN WG1 Meeting #102e; e-Meeting, Aug. 17-28, 2020; Source: CATT; Title: Discussion on enhancements on multi-TRP/panel for PDCCH, PUCCH and PUSCH; Agenda Item: 8.1.2.1; Document for: Discussion and … [cited by applicant]
R1-2005728; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda item: 8.1.2.1; Source: China Telecom; Title: Discussion on multi-TRP enhancement; Document for: Discussion. [cited by applicant]
R1-2005751; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda item: 8.1.2.1; Source: NEC; Title: Discussion on multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discussion and Decision. [cited by applicant]
R1-2005783; 3GPP TSG RAN WG1 Meeting #102-e; E-meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1—Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Source: Fraunhofer IIS, Fraunhofer HHI; Title: On multi-TRP enhancemen… [cited by applicant]
R1-2005821; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-Aug. 28, 2020; Agenda Item: 8.1.2.1; Source: Lenovo, Motorola Mobility; Title: Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discussion. [cited by applicant]
R1-2005859; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Intel Corporation; Title: Multi-TRP enhancements for PDCCH, PUCCH and PUSCH; Document for: Discussion/Decision. [cited by applicant]
R1-2005984; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Source: OPPO; Title: Enhancements on multi-TRP for PDCCH, PUCCH and PUSCH; Agenda Item: 8.1.2.1; Document for: Discussion and Decision. [cited by applicant]
R1-2006129; 3GPP Tsg Ran WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda item: 8.1.2.1; Source: Samsung; Title: Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discussion and Decision. [cited by applicant]
R1-2006201; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda item: 8.1.2.1; Title: Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Source: CMCC; Document for: Discussion and Decision. [cited by applicant]
R1-2006258; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Spreadtrum Communications; Title: Discussion on enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discuss… [cited by applicant]
R1-2006391; 3GPP TSG RAN WG1 Meeting #102-e; E-meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Huawei, HiSilicon; Title: Enhancements on Multi-TRP for reliability and robustness in Rel-17; Document for: Discuss… [cited by applicant]
R1-2006500; 3GPP TSG-RAN WG1 Meeting #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Apple Inc.; Title: On Multi-TRP Reliability Enhancement; Document for: Discussion/Decision. [cited by applicant]
R1-2006543; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Xiaomi; Title: Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discussion and Decision. [cited by applicant]
R1-2006566; 3GPP TSG RAN WG1 #102; e-Meeting, Aug. 17-28, 2020; Source: Sharp; Title: Enhancement on multi-TRP operation for PDCCH and PUSCH; Agenda Item: 8.1.2.1; Document for: Discussion and Decision. [cited by applicant]
R1-2006597; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda item: 8.1.2.1; Source: LG Electronics; Title: Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discussion and Decision. [cited by applicant]
R1-2006627; 3GPP TSG-RAN WG1#102-e; e-Meeting, Aug. 17-28, 2020; Agenda item:8.1.2.1; Title: Multi-TRP Enhancements for PDCCH, PUCCH and PUSCH; Source: Convida Wireless; Document for: Discussion. [cited by applicant]
R1-2006637; 3GPP TSG-RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Source: Asia Pacific Telecom; Title: Discussion on enhancements on multi-TRP for uplink channels; Agenda item: 8.1.2.1; Document for: Discussion and Deci… [cited by applicant]
R1-2006719; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-Aug. 28, 2020; Source: NTT Docomo, Inc; Title: Discussion on MTRP for reliability; Agenda Item: 8.1.2.3; Document for: Discussion and Decision. [cited by applicant]
R1-2006791; 3GPP TSG-RAN WG1 Meeting #102-e; e-Meeting, Aug. 17-28, 2020; Agenda item: 8.1.2.1; Source: Qualcomm Incorporated; Title: Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discussion/Decisi… [cited by applicant]
R1-2006844; 3GPP TSG RAN WG1 #102 Meeting; e-Meeting, Aug. 17-28, 2020; Agenda item: 8.1.2.1; Source: Nokia, Nokia Shanghai Bell; Title: Enhancements for Multi-TRP URLLC schemes; Document for: Discussion and Decision. [cited by applicant]
R1-2006868; 3GPP TSG RAN WG1 #102-e; e-Meeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: ASUSTeK; Title: Discussion on enhancement on M-TRP; Document for: Discussion and Decision. [cited by applicant]
R1-2006901; 3GPP TSG RAN WG1 Meeting #102-e; E-meeting, Aug. 17-28, 2020; Source: TCL communication; Title: Discussion on multi-TRP/multi-panel transmission; Agenda Item: 8.1.2.1; Document for: Discussion and Decision. [cited by applicant]
R1-2006367; 3GPP TSG-RAN WG1 Meeting #102; eMeeting, Aug. 17-28, 2020; Agenda Item: 8.1.2.1; Source: Ericsson; Title: On PDCCH, PUCCH and PUSCH robustness; Document for: Discussion. [cited by applicant]
International Search Report and Written Opinion of the International Searching authority mailed Mar. 17, 2022, in International Application No. PCT/US2021/053071. [cited by applicant]
Office Action mailed Oct. 14, 2024 in Korean Patent Application No. 2023-7014360. [cited by applicant]
Japanese Office Action mailed Nov. 28, 2024 in JP Patent Application No. 2023-520112. [cited by applicant]
Cited By (1)
US 12,739,718