IP Library › Granted Patent US 12,395,860
Granted Patent B2
US 12,395,860 · App. 18/731,771 · Granted Aug 19, 2025

Default spatial relation for physical uplink shared channel transmissions

Inventors: Hua Zhou (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Kyungmin Park (Vienna, VA); Ali Cagatay Cirik (Chantilly, VA); Hyoungsuk Jeon (Centreville, VA); Yunjung Yi (Vienna, VA); Alireza Babaei (Fairfax, VA); Kai Xu (Great Falls, VA)
Assignee: Ofinno, LLC
H04W16/28H04B7/0617H04B7/0626H04L5/0051H04L25/0226H04W56/001H04W72/23H04W74/0833
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,395,860
App. No.
18/731,771
Granted
Aug 19, 2025
Kind
B2
Abstract

A base station may transmit to a wireless device one or more configuration parameters. The one or more configuration parameters indicate: one or more physical uplink control channel (PUCCH) resources, and a default beam is used for physical uplink shared channel (PUSCH) transmissions. The bases station may transmit to the wireless device downlink control information (DCI), with DCI format 0_0, scheduling a PUSCH. The base station may receive from the wireless device, via the PUSCH, a transport block according to a default spatial relation in response to: a DCI format of the DCI being the DCI format 0_0, the configuration parameters indicating that the default beam is used, each PUCCH resource of the one or more PUCCH resources not being configured with a spatial relation, and the wireless device being in a radio resource control (RRC) connected mode.

Claims (65)

1. A method comprising:

receiving, by a wireless device from a base station, one or more configuration parameters indicating:

one or more physical uplink control channel (PUCCH) resources; and

a default beam is used for physical uplink shared channel (PUSCH) transmissions;

receiving downlink control information (DCI), with DCI format 0_0, scheduling a PUSCH; and

transmitting, via the PUSCH, a transport block according to a default spatial relation in response to:

a DCI format of the DCI being the DCI format 0_0;

the one or more configuration parameters indicating that the default beam is used;

each PUCCH resource of the one or more PUCCH resources not being configured with a spatial relation; and

the wireless device being in a radio resource control (RRC) connected mode.

2. The method of claim 1 , wherein the DCI:

comprises an uplink grant for the PUSCH; and

does not comprise spatial relation information for the uplink grant.

3. The method of claim 1 , further comprising transmitting, by the wireless device to the base station, the transport block with a spatial domain transmission filter determined based on the default spatial relation.

4. The method of claim 3 , wherein:

the default spatial relation is determined based on one or more downlink reference signals; and

the one or more downlink references signals are:

one or more channel state information reference signals (CSI-RSs); or

one or more synchronization signal blocks (SSBs).

5. The method of claim 1 , wherein the one or more configured parameters are received in one or more radio resource control (RRC) messages.

6. The method of claim 5 , wherein the wireless device is in RRC connected mode when the one or more RRC messages are received.

7. The method of claim 1 , wherein the one or more configuration parameters further indicate one or more control resource sets (coresets) are quasi co-located with one or more downlink reference signals.

8. A method comprising:

transmitting, by a base station to a wireless device, one or more configuration parameters indicating:

one or more physical uplink control channel (PUCCH) resources; and

a default beam is used for physical uplink shared channel (PUSCH) transmissions;

transmitting, to the wireless device, downlink control information (DCI), with DCI format 0_0, scheduling a PUSCH; and

receive, from the wireless device via the PUSCH, a transport block according to a default spatial relation in response to:

a DCI format of the DCI being the DCI format 0_0;

the one or more configuration parameters indicating that the default beam is used;

each PUCCH resource of the one or more PUCCH resources not being configured with a spatial relation; and

the wireless device being in a radio resource control (RRC) connected mode.

9. The method of claim 8 , wherein the DCI:

comprises an uplink grant for the PUSCH; and

does not comprise spatial relation information for the uplink grant.

10. The method of claim 8 , further comprising the wireless device the transmitting the transport block with a spatial domain transmission filter determined based on the default spatial relation.

11. The method of claim 10 , wherein:

the default spatial relation is determined based on one or more downlink reference signals; and

the one or more downlink references signals are:

one or more channel state information reference signals (CSI-RSs); or

one or more synchronization signal blocks (SSBs).

12. The method of claim 8 , wherein the one or more configuration parameters are transmitted in one or more radio resource control (RRC) messages.

13. The method of claim 12 , wherein the wireless device is in RRC connected mode when the one or more RRC messages are transmitted.

14. The method of claim 8 , wherein the one or more configuration parameters further indicate one or more control resource sets (coresets) are quasi co-located with one or more downlink reference signals.

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

transmit, to a wireless device, one or more configuration parameters indicating:

one or more physical uplink control channel (PUCCH) resources; and

a default beam is used for physical uplink shared channel (PUSCH) transmissions;

transmit, to the wireless device, downlink control information (DCI), with DCI format 0_0, scheduling a PUSCH; and

receive, from the wireless device via the PUSCH, a transport block according to a default spatial relation in response to:

a DCI format of the DCI being the DCI format 0_0;

the one or more configuration parameters indicating that the default beam is used;

each PUCCH resource of the one or more PUCCH resources not being configured with a spatial relation; and

the wireless device being in a radio resource control (RRC) connected mode.

16. The non-transitory computer-readable medium of claim 15 , wherein the DCI:

comprises an uplink grant for the PUSCH; and

does not comprise spatial relation information for the uplink grant.

17. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the wireless device to transmit the transport block with a spatial domain transmission filter determined based on the default spatial relation.

18. The non-transitory computer-readable medium of claim 17 , wherein:

the default spatial relation is determined based on one or more downlink reference signals; and

the one or more downlink references signals are:

one or more channel state information reference signals (CSI-RSs); or

one or more synchronization signal blocks (SSBs).

19. The non-transitory computer-readable medium of claim 15 , wherein the one or more configuration parameters are transmitted in one or more radio resource control (RRC) messages and the one or more configuration parameters further indicate one or more control resource sets (coresets) are quasi co-located with one or more downlink reference signals.

20. The non-transitory computer-readable medium of claim 19 , wherein the wireless device is in RRC connected mode when the one or more RRC messages are transmitted.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 25, 2024
From: ZHOU, HUA; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; CIRIK, ALI CAGATAY; JEON, HYOUNGSUK; YI, YUNJUNG; BABAEI, ALIREZA; XU, KAI
To: OFINNO, LLC
Reel/Frame 068085/0371 →
Continuity (5)
Continuation 18213466 · Jun 23, 2023
Continuation 17479413 · Sep 20, 2021
Continuation 16834019 · Mar 30, 2020
Provisional Application 62825587 · Mar 28, 2019
Related Publication 20240323706A1 · Sep 26, 2024
References Cited (72)
US 11115110B2 · Zhou et al. · 2021 [cited by applicant]
US 11147073B2 · Liou · 2021 [cited by applicant]
US 11324041B2 · Zhou et al. · 2022 [cited by applicant]
US 20190190582A1 · Guo · 2019 [cited by examiner]
US 20190261338A1 · Akkarakaran · 2019 [cited by examiner]
US 20190289588A1 · Akkarakaran et al. · 2019 [cited by applicant]
US 20190312698A1 · Akkarakaran · 2019 [cited by examiner]
US 20190319823A1 · Akkarakaran · 2019 [cited by examiner]
US 20200195334A1 · Zhou · 2020 [cited by examiner]
US 20200196277A1 · Zhou · 2020 [cited by examiner]
US 20200229098A1 · Cheng · 2020 [cited by examiner]
US 20200305168A1 · Liou · 2020 [cited by examiner]
US 20210352665A1 · Kang et al. · 2021 [cited by applicant]
US 20210385668A1 · Kang et al. · 2021 [cited by applicant]
US 20210400649A1 · Kang et al. · 2021 [cited by applicant]
US 20220132326A1 · Wang et al. · 2022 [cited by applicant]
US 20230337014A1 · Zhou · 2023 [cited by examiner]
US 20240323706A1 · Zhou · 2024 [cited by examiner]
WO 2019183125A1 · 2019 [cited by applicant]
WO 2020069075A1 · 2020 [cited by applicant]
3GPP TS 38.212 V15.4.0 (Dec. 2018); 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.4.0 (Dec. 2018); 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.4.0 (Dec. 2018); 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.331 V15.4.0 (Dec. 2018); 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-1805574; 3GPP TSG RAN WG1 Meeting #92b; Sanya, China, Apr. 16-20, 2018; Source: Ericsson; Title: Feature lead summary 2 on beam measurement and reporting; Agenda Item: 7.1.2.2.3; Document for: Discussion and Decision. [cited by applicant]
R1-1901205; 3GPP TSG RAN WG1 Ad-Hoc Meeting 1901; Taipei, Taiwan, Jan. 21-25, 2019; Agenda Item: 7.2.8.6; Source: Ericsson; Title: UL beam selection improvements; Document for: Discussion, Decision. [cited by applicant]
R1-1901568; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, February 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: Huawei, HiSilicon; Title: Enhancements on multi-beam operation; Document for: Discussion and Decision. [cited by applicant]
R1-1901635; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE; Title: Enhancements on multi-beam operation; Agenda Item: 7.2.8.3; Document for: Discussion and Decision. [cited by applicant]
R1-1901639; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE; Title: Additional considerations on beam management for multi-TRP; Agenda item: 7.2.8.6; Document for: Discussion and Decision. [cited by applicant]
R1-1901640; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE; Title: Additional details of latency and overhead reduction for beam management; Agenda item: 7.2.8.6; Document for: Discussion and De… [cited by applicant]
R1-1901641; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE; Title: Details and evaluation on UL simultaneous transmission for multi-panel operation; Agenda Item: 7.2.8.6; Document for: D… [cited by applicant]
R1-1901642; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE; Title: Details and evaluation on L1-SINR measurement and reporting; Agenda Item: 7.2.8.6; Document for: Discussion and Decisio… [cited by applicant]
R1-1901643; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE; Title: Discussion on UL power control for multi-panel operation; Agenda Item: 7.2.8.6; Document for: Discussion and Decision. [cited by applicant]
R1-1901703; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: vivo; Title: Further discussion on Multi-Beam Operation; Agenda Item: 7.2.8.3; Document for: Discussion and Decision. [cited by applicant]
R1-1901779; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE; Title: Discussion on NR Mobility Enhancements in Physical Layer; Agenda Item: 7.2.12.1; Document for: Discussion and Decision. [cited by applicant]
R1-1901790; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: MediaTek Inc.; Title: Enhancements on multi-beam operations; Document for: Discussion. [cited by applicant]
R1-1901904; 3GPP TSG RAN WG1 Meeting # 96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: AT&T; Title: Enhancements on Multi Beam Operation ; Document for: Discussion/Approval. [cited by applicant]
R1-1902020; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: CATT; Title: Enhancements on multi-beam operation; Agenda Item: 7.2.8.3; Document for: Discussion and Decision. [cited by applicant]
R1-1902092; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 7.2.8.3; Source: LG Electronics; Title: Discussion on multi-beam based operations and enhancements; Document for: Discussion a… [cited by applicant]
R1-1902162; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25- Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: Lenovo, Motorola Mobility; Title: Discussion of multi-beam operation; Document for: Discussion. [cited by applicant]
R1-1902184; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: Sony; Title: Enhancements on multi-beam operation; Document for: Discussion. [cited by applicant]
R1-1902249; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb.25-Mar. 1, 2019; Agenda item: 7.2.12; Source: Samsung; Title: Physical Layer Aspects for Mobility Enhancements; Document for: Discussion and decision. [cited by applicant]
R1-1902339; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 7.2.8.3; Source: CMCC; Title: Enhancements on multi-beam operation; Document for: Discussion and Decision. [cited by applicant]
R1-1902408; 3GPP TSG-RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: Asia Pacific Telecom; Title: Enhancements on UL Multi-beam Operation; Agenda item: 7.2.8.3; Document for: Discussion and Decision. [cited by applicant]
R1-1902463; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: Intel Corporation; Title: Physical layer aspects of enhanced mobility; Agenda item: 7.2.12.1; Document for: Discussion and Decision. [cited by applicant]
R1-1902523; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: Panasonic; Title: On enhancements for multi-beam operations for NR MIMO in Rel. 16; Agenda Item: 7.2.8.3; Document for: Discussion. [cited by applicant]
R1-1902528; 3GPP TSG-RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.12.1; Source: Ericsson; Title: Lower-layer mobility enhancements; Document for: Discussion. [cited by applicant]
R1-1902564; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 7.2.8.3; Source: Nokia, Nokia Shanghai Bell; Title: Enhancements on Multi-beam Operation; Document for: Discussion and Decisio… [cited by applicant]
R1-1902615; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: InterDigital, Inc.; Title: Enhancement for Multi-Beam Uplink Operation; Document for: Discussion and Decision. [cited by applicant]
R1-1902630; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 7.2.8.3; Source: China Telecom; Title: Enhancements on multi-beam operation for multi-panel transmission; Document for: Discussion. [cited by applicant]
R1-1902714; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: Spreadtrum Communications; Title: Discussion on multi-beam operation; Document for: Discussion and decision. [cited by applicant]
R1-1902768; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: Apple Inc.; Title: Consideration on beam measurement and reporting enhancement; Document for: Discussion/Decision. [cited by applicant]
R1-1902833; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: Mitsubishi Electric; Title: Views on multi-beam operation; Agenda Item: 7.2.8.3Enhancements on Multi-beam Operation; Document for: … [cited by applicant]
R1-1902866; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: Xiaomi; Title: Enhancements on beam management; Document for: Discussion and Decision. [cited by applicant]
R1-1903024; 3GPP TSG-RAN WG1 Meeting 1901; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 7.2.12.1; Source: Qualcomm Incorporated; Title: On Mobility Enhancements during HO; Document for: Discussion/Decision. [cited by applicant]
R1-1903091; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.6; Source: Huawei, HiSilicon; Title: Panel-based UL beam selection; Document for: Discussion and Decision. [cited by applicant]
R1-1903113; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.12.1; Source: Huawei, HiSilicon; Title: Overview on NR mobility enhancements; Document for: Discussion and decision. [cited by applicant]
R1-1903114; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.12.2; Source: Huawei, HiSilicon; Title: Discussion on scenarios for mobility enhancements; Document for: Discussion and de… [cited by applicant]
R1-1903115; 3GPP TSG RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.12.2; Source: Huawei, HiSilicon; Title: Details on mobility enhancements; Document for: Discussion and decision. [cited by applicant]
R1-1903138; 3GPP TSG RAN WG1 #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 7.2.12.1; Source: Nokia, Nokia Shanghai Bell; Title: On mobility enhancements during cell change; Document for: Discussion and Decisio… [cited by applicant]
R1-1903231; 3GPP TSG-RAN WG1 Meeting #96; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 7.2.8.3; Source: Ericsson; Title: Enhancements to multi-beam operation; Document for: Discussion, Decision. [cited by applicant]
R2-1900280; 3GPP TSG RAN WG2 Meeting #105; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: CATT ; Title: Solutions on Reduction in User Data Interruption for NR; Agenda Item: 11.9.2; Document for: Discussion and Decision. [cited by applicant]
R2-1900363; 3GPP TSG-RAN WG2 Meeting #105; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 11.9.2 ; Source: Qualcomm Incorporated; Title: RACH-Less HO design considerations; WID/SID: NR mobility enhancements; Documen… [cited by applicant]
R2-1900403; 3GPP TSG-RAN WG2#105; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 11.9.2; Source: Ericsson; Title: RACH-less handover in NR; Document for: Discussion, Decision. [cited by applicant]
R2-1900436; 3GPP TSG-RAN WG2 Meeting #105; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 11.9.2; Source: Mediatek Inc.; Title: Solutions to Reduce HO Interruption in NR and LTE; Document for: Discussion, Decision. [cited by applicant]
R2-1900502; 3GPP TSG-RAN WG2 Meeting #105; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: vivo; Title: RACH-less with SSB association; Agenda Item: 11.9.2; Document for: Discussion and Decision. [cited by applicant]
R2-1900607; 3GPP TSG-RAN WG2 Meeting #105; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda item: 11.9.3; Source: Nokia, Nokia Shanghai Bell; Title: RACH-less HO in beam-based system; WID/SID: NR_Mob_enh-Core—Release 16; Do… [cited by applicant]
R2-1900704; 3GPP TSG-RAN WG2#105; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: Huawei, HiSilicon; Title: Discussion on RACH-less solution; Agenda Item: 11.9.2; Document for: Discussion and Decision. [cited by applicant]
R2-1900798; 3GPP TSG-RAN WG2 Meeting #105; Athens, Greece, Feb. 25-Mar. 1, 2019; Source: ZTE Corporation, Sanechips; Title: Discussion on the support of RACH-less HO in NR; Agenda item: 11.9.2; Document for: Discussion … [cited by applicant]
R2-1900991; 3GPP TSG-RAN WG2#105; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 11.9.2; Source: Samsung; Title: On Supporting RACH-less in NR; Document for: Discussion. [cited by applicant]
R2-1901041; 3GPP TSG-RAN WG2 Meeting #105; Athens, Greece, Feb. 25-Mar. 1, 2019; Agenda Item: 11.9.2; Source: ASUSTek; Title: Discussion on RACH-less handover mechanism for NR; Document for: Discussion and Decision. [cited by applicant]
Chang et al.; Default Beam for U; Transmission in Transition Phase; Mediatek; Feb. 23, 2018. [cited by applicant]