IP Library › Granted Patent US 12,634,040
Granted Patent B2
US 12,634,040 · App. 17/969,854 · Granted May 19, 2026

Frequency hopping in multiple transmission and reception points

Inventors: Ali Cagatay Cirik (Chantilly, VA); Esmael Hejazi Dinan (McLean, VA); Yunjung Yi (Vienna, VA); Hua Zhou (Vienna, VA)
Assignee: Ofinno, LLC
H04L1/08H04B1/7143
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,634,040
App. No.
17/969,854
Granted
May 19, 2026
Kind
B2
Abstract

A wireless device receives one or more configuration parameters indicating a mapping pattern that indicates a cyclical mapping of spatial domain transmission filters to physical uplink shared channel (PUSCH) repetitions. The wireless device receives a downlink control information (DCI) scheduling repetitions of a PUSCH transmission, where the DCI comprises a frequency hopping field set to one and indicates a frequency offset. Based on the frequency hopping field being set to one and the mapping pattern indicating the cyclical mapping, the wireless device sequentially transmits, starting from a first resource block, a first repetition of the PUSCH transmission using a first spatial domain transmission filter and a second repetition using a second spatial domain transmission filter; and sequentially transmits, starting from a second resource block, a third repetition using the first spatial domain transmission filter and a fourth repetition using the second spatial domain transmission filter.

Claims (112)

1 . A method comprising:

receiving, by a wireless device, one or more configuration parameters indicating a mapping pattern that indicates a cyclical mapping of spatial domain transmission filters to physical uplink shared channel (PUSCH) repetitions;

receiving a downlink control information (DCI), on a physical downlink control channel (PDCCH), scheduling repetitions of a PUSCH transmission, wherein the DCI:

comprises a frequency hopping field set to one; and

indicates a frequency offset; and

based on the frequency hopping field being set to one and the mapping pattern indicating the cyclical mapping, transmitting sequentially:

starting from a first resource block:

a first repetition of the PUSCH transmission using a first spatial domain transmission filter determined based on a first transmission configuration indicator (TCI) state; and

a second repetition of the PUSCH transmission using a second spatial domain transmission filter determined based on a second TCI state; and

starting from a second resource block, the second resource block being a frequency-hopped resource block determined based on the first resource block and the frequency offset:

a third repetition of the PUSCH transmission using the first spatial domain transmission filter; and

a fourth repetition of the PUSCH transmission using the second spatial domain transmission filter.

2 . The method of claim 1 , further comprising transmitting:

the first repetition of the PUSCH transmission in a first transmission occasion;

the second repetition of the PUSCH transmission in a second transmission occasion;

the third repetition of the PUSCH transmission in a third transmission occasion; and

the fourth repetition of the PUSCH transmission in a fourth transmission occasion.

3 . The method of claim 1 , wherein the one or more configuration parameters indicate:

a frequency hopping mode for the repetitions of the PUSCH transmission; and

a repetition type for the PUSCH transmission.

4 . The method of claim 3 , wherein the frequency hopping mode is at least one of:

an inter-slot frequency hopping,

an intra-slot frequency hopping, or

an inter-repetition frequency hopping.

5 . The method of claim 3 , wherein the repetition type is at least one of:

a PUSCH repetition Type A; and

a PUSCH repetition Type B.

6 . The method of claim 1 , wherein the one or more configuration parameters indicate:

a first frequency or a first physical resource block; and

a second frequency or a second physical resource block.

7 . The method of claim 6 , wherein the DCI indicates:

a frequency hopping offset among one or more frequency hopping offsets; and

the first frequency or the first physical resource block.

8 . The method of claim 7 , further comprising determining the second frequency or the second physical resource block based on:

the first frequency or the first physical resource block; and

the frequency hopping offset.

9 . The method of claim 6 , wherein:

the PUSCH transmission is for a configured uplink grant; and

the one or more configuration parameters indicate, for the configured uplink grant:

a frequency hopping offset; and

the first frequency or the first physical resource block.

10 . The method of claim 1 , further comprising:

receiving one or more second messages comprising one or more second configuration parameters, wherein the one or more second configuration parameters indicate:

a frequency hopping mode for the repetitions of the PUSCH transmission; and

a sequential mapping pattern indicating mapping of spatial domain transmission filters to the repetitions of the PUSCH transmission sequentially;

receiving a second DCI scheduling repetitions of a second PUSCH transmission, wherein the second DCI comprises a second frequency hopping field set to one; and

based on the second frequency hopping field being set to one and the sequential mapping pattern, transmitting sequentially:

a first repetition of the second PUSCH transmission using the first spatial domain transmission filter determined based on the first TCI state starting from a third resource block;

a second repetition of the second PUSCH transmission using the first spatial domain transmission filter determined based on the first TCI state starting from a fourth resource block;

a third repetition of the second PUSCH transmission using the second spatial domain transmission filter determined based on the second TCI state starting from the third resource block; and

a fourth repetition of the second PUSCH transmission using the second spatial domain transmission filter determined based on the second TCI state starting from the fourth resource block.

11 . 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 one or more configuration parameters indicating a mapping pattern that indicates a cyclical mapping of spatial domain transmission filters to physical uplink shared channel (PUSCH) repetitions;

receive a downlink control information (DCI), on a physical downlink control channel (PDCCH), scheduling repetitions of a PUSCH transmission, wherein the DCI:

comprises a frequency hopping field set to one; and

indicates a frequency offset; and

based on the frequency hopping field being set to one and the mapping pattern indicating the cyclical mapping, transmitting sequentially:

starting from a first resource block:

a first repetition of the PUSCH transmission using a first spatial domain transmission filter determined based on a first transmission configuration indicator (TCI) state; and

a second repetition of the PUSCH transmission using a second spatial domain transmission filter determined based on a second TCI state; and

starting from a second resource block, the second resource block being a frequency-hopped resource block determined based on the first resource block and the frequency offset:

a third repetition of the PUSCH transmission using the first spatial domain transmission filter; and

a fourth repetition of the PUSCH transmission using the second spatial domain transmission filter.

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

the first repetition of the PUSCH transmission in a first transmission occasion;

the second repetition of the PUSCH transmission in a second transmission occasion;

the third repetition of the PUSCH transmission in a third transmission occasion; and

the fourth repetition of the PUSCH transmission in a fourth transmission occasion.

13 . The wireless device of claim 11 , wherein the one or more configuration parameters indicate:

a frequency hopping mode for the repetitions of the PUSCH transmission; and

a repetition type for the PUSCH transmission.

14 . The wireless device of claim 13 , wherein the frequency hopping mode is at least one of:

an inter-slot frequency hopping,

an intra-slot frequency hopping, or

an inter-repetition frequency hopping.

15 . The wireless device of claim 13 , wherein the repetition type is at least one of:

a PUSCH repetition Type A; and

a PUSCH repetition Type B.

16 . The wireless device of claim 11 , wherein the one or more configuration parameters indicate:

a first frequency or a first physical resource block; and

a second frequency or a second physical resource block.

17 . The wireless device of claim 16 , wherein the DCI indicates:

a frequency hopping offset among one or more frequency hopping offsets; and

the first frequency or the first physical resource block.

18 . The wireless device of claim 17 , wherein the instructions, when executed by the one or more processors, further cause the wireless device to determine the second frequency or the second physical resource block based on:

the first frequency or the first physical resource block; and

the frequency hopping offset.

19 . The wireless device of claim 16 , wherein:

the PUSCH transmission is for a configured uplink grant; and

the one or more configuration parameters indicate, for the configured uplink grant:

a frequency hopping offset; and

the first frequency or the first physical resource block.

20 . A system comprising:

a base station comprising:

one or more first processors; and

first memory storing first instructions that, when executed by the one or more first processors, cause the base station to transmit one or more configuration parameters; and

a wireless device comprising:

one or more second processors; and

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

receive the one or more configuration parameters indicating a mapping pattern that indicates a cyclical mapping of spatial domain transmission filters to physical uplink shared channel (PUSCH) repetitions;

receive a downlink control information (DCI), on a physical downlink control channel (PDCCH) scheduling repetitions of a PUSCH transmission, wherein the DCI:

comprises a frequency hopping field set to one; and

indicates a frequency offset; and

based on the frequency hopping field being set to one and the mapping pattern indicating the cyclical mapping, transmitting sequentially:

starting from a first resource block:

 a first repetition of the PUSCH transmission using a first spatial domain transmission filter determined based on a first transmission configuration indicator (TCI) state; and

 a second repetition of the PUSCH transmission using a second spatial domain transmission filter determined based on a second TCI state; and

starting from a second resource block, the second resource block being a frequency-hopped resource block determined based on the first resource block and the frequency offset:

 a third repetition of the PUSCH transmission using the first spatial domain transmission filter; and

 a fourth repetition of the PUSCH transmission using the second spatial domain transmission filter.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 27, 2022
From: CIRIK, ALI CAGATAY; DINAN, ESMAEL HEJAZI; YI, YUNJUNG; ZHOU, HUA
To: OFINNO, LLC
Reel/Frame 061562/0635 →
Continuity (3)
Continuation PCTUS2021043828 · Jul 30, 2021
Provisional Application 63058820 · Jul 30, 2020
Related Publication 20230041603A1 · Feb 9, 2023
References Cited (49)
US 20190319823A1 · Akkarakaran · 2019 [cited by examiner]
US 20200146034A1 · Bagheri · 2020 [cited by examiner]
US 20210044403A1 · Zhang · 2021 [cited by examiner]
US 20220210824A1 · Ying · 2022 [cited by examiner]
US 20220217760A1 · Iyer · 2022 [cited by examiner]
US 20230031875A1 · Dai · 2023 [cited by examiner]
US 20230059757A1 · Matsumura · 2023 [cited by examiner]
US 20230068475A1 · Yang · 2023 [cited by examiner]
US 20230069690A1 · Takahashi · 2023 [cited by examiner]
US 20230093264A1 · Gao · 2023 [cited by examiner]
US 20230098912A1 · Matsumura · 2023 [cited by examiner]
US 20230353298A1 · Liu · 2023 [cited by examiner]
WO 2018204340A1 · 2018 [cited by applicant]
WO 2021163961A1 · 2021 [cited by applicant]
WO 2021179108A1 · 2021 [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-1811277; 3GPP TSG-RAN WG1 Meeting #94bis; Oct. 8-12, 2018; Chengdu, China; Agenda item: 7.2.8.2; Source: Qualcomm Incorporated; Title: Enhancements on Multi-TRP/Panel Transmission; Document for: Discussion/Decision. [cited by applicant]
R1-1811278; 3GPP TSG-RAN WG1 Meeting #94bis; Chengdu, China, Oct. 8-12, 2018; Agenda item: 7.2.8.3; Source: Qualcomm Incorporated; Title: Enhancements on Multi-beam Operation; Document for: Discussion/Decision. [cited by applicant]
R1-1811348; 3GPP TSG RAN WG1 Meeting #94bis; Chengdu, China, Oct. 8-12, 2018; Source: NTT Docomo, Inc.; Title: Enhancements on multi-TRP/panel transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1812635; 3GPP TSG RAN WG1 Meeting #95; Spokane, USA, Nov. 12-16, 2018; Source: CATT; Title: Multi-TRP/panel transmission enhancement for Rel-16; Agenda Item: 7.2.8.2; Document for: Discussion and decision. [cited by applicant]
R1-1813442; 3GPP TSG-RAN WG1 Meeting #95; Nov. 12-16, 2018; Spokane, WA, USA; Agenda item: 7.2.8.2; Source: Qualcomm Incorporated; Title: Multi-TRP Enhancements; Document for: Discussion/Decision. [cited by applicant]
R1-1900137; 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901; Taipei, Jan. 21-25, 2019; Source: vivo; Title: Discussion on multi PDCCH based multi TRP transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1900339; 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901; Taipei, Jan. 21-25, 2019; Source: CATT; Title: Consideration on multi-TRP/panel transmission; Agenda Item: 7.2.8.2; Document for: Discussion and decision. [cited by applicant]
R1-1900835; 3GPP TSG RAN WG1 Meeting AH 1901; Taipei, Taiwan, Jan. 21-25, 2019; Source: Sharp; Title: Discussion on multi-TRP/panel techniques for URLLC; Agenda Item: 7.2.8.2; Enhancements on Multi-TRP/Panel Transmissio… [cited by applicant]
R1-1900850; 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901; Taipei, Jan. 21-25, 2019; Agenda Item: 7.2.8.6; Source: Huawei, HiSilicon; Title: Reliability/robustness enhancement with multi-TRP/panel/beam for PDCCH/PUSCH/PUCCH; Doc… [cited by applicant]
R1-1900905; 3GPP TSG-RAN WG1 Meeting AH-1901; Jan. 21-25, 2019; Taipei, Taiwan; Agenda item: 7.2.8.2; Source: Qualcomm Incorporated; Title: Multi-TRP Enhancements; Document for: Discussion/Decision. [cited by applicant]
R1-1900978; 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901; Taipei, Jan. 21-25, 2019; Source: NTT Docomo, Inc; Title: Enhancements on multi-TRP/panel transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1901702; 3GPP TSG RAN1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: vivo; Title: Further Discussion on Multi-TRP Transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1902812; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: NTT Docomo, Inc; Title: Enhancements on multi-TRP/panel transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1902926; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.2; Source: CAICT; Title: Discussion on URLLC reliability/robustness enhancement with multi-TRP/panel; Document for: Discussion a… [cited by applicant]
R1-1903101; 3GPP TSG RAN WG1 meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.6; Source: Huawei, HiSilicon; Title: Reliability/robustness enhancement with multi-TRP/panel; Document for: Discussion a… [cited by applicant]
R1-1903983; 3GPP TSG RAN WG1 meeting #96b; Xi'an, China, Apr. 8-12, 2019; Agenda Item: 7.2.8.6; Source: Huawei, HiSilicon; Title: Reliability/robustness enhancement with multi-TRP/panel; Document for: Discussion and Dec… [cited by applicant]
R1-1904020; 3GPP TSG RAN WG1 Meeting #96bis; Xi'an, China, Apr. 8-12, 2019; Source: ZTE; Title: Details and evaluation results on multi-TRP for URLLC; Agenda item: 7.2.8.6; Document for: Discussion and Decision. [cited by applicant]
R1-1905027; 3GPP TSG-RAN WG1 Meeting #96-Bis; Xi'an, China, Apr. 8-12, 2019; Agenda item: 7.2.8.3; Source: Qualcomm Incorporated; Title: Enhancements on Multi-beam Operation; Document for: Discussion/Decision. [cited by applicant]
R1-1906225; 3GPP TSG RAN WG1 #97; Reno, USA, May 13-17, 2019; Source: NTT Docomo, Inc.; Title: Discussion on multi-beam enhancement ; Agenda Item: 7.2.8.3; Document for: Discussion and Decision. [cited by applicant]
R1-1910229; 3GPP TSG RAN WG1 #98bis; Chongqing, China, Oct. 14-20, 2019; Source: vivo; Title: Discussion on remaining issues on multi TRP transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1911209; 3GPP TSG RAN WG1 Meeting #98bis; Chongqing, China, Oct. 14-18, 2019; Source: KDDI; Title: Enhancements on multi-TRP/panel transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1912920; 3GPP TSG RAN WG1 Meeting #99; Reno, USA, Nov. 18-22, 2019; Agenda Item: 7.2.8.5; Source: Huawei, HiSilicon; Title: Other issues on NR eMIMO in R16; Document for: Discussion and Decision. [cited by applicant]
R1-1912968; 3GPP TSG-RAN WG1 Meeting #99; Reno, Nevada, US, Nov. 18-22, 2019; Agenda item: 7.2.8.3; Source: Qualcomm Incorporated; Title: Enhancements on Multi-beam Operation; Document for: Discussion/Decision. [cited by applicant]
R1-1913013; 3GPP TSG RAN WG1 Meeting #99; Reno, USA, Nov. 18-22, 2019; Source: KDDI; Title: Enhancements on multi-TRP/panel transmission; Agenda Item: 7.2.8.2; Document for: Discussion and Decision. [cited by applicant]
R1-1902004; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: CATT Title: On PUSCH enhancements for URLLC; Agenda Item: 7.2.6.1.3; Document for: Discussion and Decision. [cited by applicant]
R1-2000357; 3GPP TSG RAN WG1 #100; e-Meeting, Feb. 24-Mar. 6, 2020; Source: ZTE; Title: Remaining issues on PUSCH enhancements for NR URLLC; Agenda item: 7.2.5.3; Document for: Discussion and Decision. [cited by applicant]
R1-2104655; 3GPP TSG-RAN WG1 Meeting #105-bis-e; e-Meeting, May 10-May 27, 2021; Agenda item: 8.1.2.1 Source: Qualcomm Incorporated; Title: Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH; Document for: Discussion/… [cited by applicant]
International Search Report of the International Searching Authority, mailed Jan. 14, 2022, in International Application No. PCT/US2021/043828. [cited by applicant]