IP Library Granted Patent US 12,376,131
Granted Patent B2
US 12,376,131 · App. 17/798,707 · Granted Jul 29, 2025

Multi-transmission and reception point (TRP) redundancy and soft combining with reduced latency

Inventors: Magnus Hurd (Stockholm, SE); Ying Sun (Täby, SE); Jianwei Zhang (Solna, SE); Shiwei Gao (Nepean, CA); Siva Muruganathan (Stittsville, CA)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04W72/232H04L1/1887H04L5/0035H04L5/0053
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,376,131
App. No.
17/798,707
Granted
Jul 29, 2025
Kind
B2
Abstract

A method, system and apparatus are disclosed. According to one aspect of the disclosure, a network node configured to communicate with a wireless device is provided. The network node includes processing circuitry configured to: cause a first physical downlink control channel, PDCCH, transmission starting at a first symbol and cause a second PDCCH transmission starting at a second symbol where the first PDCCH transmission is configured to schedule a first physical uplink shared channel, PUSCH, transmission ending at a third symbol for a transport block and the second PDCCH transmission configured to schedule a second PUSCH transmission starting at a fourth symbol for the transport block, where the second symbol occurs before the third symbol, the third symbol occurs later in time than the first symbol and the fourth symbol occurs later in time than that second symbol.

Claims (41)

1. A network node configured to communicate with a wireless device, the network node comprising:

processing circuitry configured to:

cause a first physical downlink control channel (PDCCH) transmission starting at a first symbol; and

cause a second PDCCH transmission starting at a second symbol, the first PDCCH transmission configured to schedule a first physical uplink shared channel (PUSCH) transmission ending at a third symbol for a transport block, the second PDCCH transmission configured to schedule a second PUSCH transmission starting at a fourth symbol for the transport block;

the second symbol occurring before the third symbol;

the third symbol occurring later in time than the first symbol; and

the fourth symbol occurring later in time than the second symbol.

2. The network node of claim 1 , wherein the first symbol occurs one of before and at the same time as the second symbol.

3. The network node of claim 1 , wherein a starting symbol and the third symbol of the first PUSCH transmission precedes the fourth symbol.

4. The network node of claim 1 , wherein the first PUSCH transmission is scheduled in a different slot than a slot where the second PUSCH transmission is scheduled.

5. The network node of claim 1 , wherein the second PUSCH transmission is scheduled to begin in a next symbol after a last symbol of the first PUSCH transmission.

6. The network node of claim 1 , wherein the first PUSCH transmission at least partially overlaps in time with the second PUSCH transmission.

7. The network node of claim 1 , wherein the second PUSCH transmission associated with the second PDCCH transmission is a retransmission of data of the first PUSCH transmission.

8. The network node of claim 1 , wherein the first and second PUSCH transmissions are positioned in a same slot.

9. The network node of claim 1 , wherein the first PDCCH transmission occurs in a first set of symbols; and

the second PDCCH transmission occurs in a second set of symbols.

10. The network node of claim 9 , wherein the first set of symbols one of at least partially overlaps in time and fails to overlap in time with the second set of symbols.

11. The network node of claim 1 , wherein the processing circuitry is further configured to:

configure the wireless device with a first control resource set (CORESET) pool and a second CORESET pool different from the first CORESET pool, each CORESET pool including at least one respective CORESET;

the first PDCCH transmission carrying a first downlink control information (DCI) and being transmitted in a CORESET of the first CORESET pool; and

the second PDCCH transmission carrying a second downlink control information, DCI and being transmitted in a CORESET of the second CORESET pool.

12. The network node of claim 1 , wherein the first PUSCH transmission corresponds to a different redundancy version than a redundancy version of the second PUSCH transmission.

13. The network node of claim 1 , wherein at least one of the first PUSCH transmission and second PUSCH transmission is scheduled by a configured grant.

14. The network node of claim 1 , wherein the first PDCCH transmission includes a first sounding reference signal indicator (SRI) and the second PDCCH transmission includes a second SRI, the first SRI being different from the second SRI.

15. The network node of claim 14 , wherein a spatial relation for the first PUSCH transmission is provided by the first SRI and a spatial relation for the second PUSCH transmission is provided by the second SRI.

16. The network node of claim 15 , wherein the configured grant is configured with a periodicity and a repetition pattern within each period, the repetition pattern indicating whether a PUSCH transmission of the configured grant is associated with one of the first SRI and second SRI.

17. The network node of claim 1 , wherein the first PUSCH transmission is received on a first Transmission and Reception Point (TRP) associated with the first SRI and the second PUSCH transmission is received on a second TRP associated with the second SRI.

18. The network node of claim 1 , wherein the first PUSCH transmission and the second PUSCH transmission are scheduled with a same number of spatial layers.

19. A method implemented by a network node that is configured to communicate with a wireless device, the method comprising:

causing a first physical downlink control channel (PDCCH) transmission starting at a first symbol; and

causing a second PDCCH transmission starting at a second symbol, the first PDCCH transmission configured to schedule a first physical uplink shared channel (PUSCH) transmission ending at a third symbol for a transport block, the second PDCCH transmission configured to schedule a second PUSCH transmission starting at a fourth symbol for the transport block;

the second symbol occurring before the third symbol;

the third symbol occurring later in time than the first symbol; and

the fourth symbol occurring later in time than that second symbol.

20. The method of claim 19 , wherein the first symbol occurs one of before and at the same time as the second symbol.

21. The method of claim 19 , wherein a starting symbol and the third symbol of the first PUSCH transmission precedes the fourth symbol.

22. The method of claim 19 , wherein the first PUSCH transmission is scheduled in a different slot than a slot where the second PUSCH transmission is scheduled.

23. The method of claim 19 , wherein the second PUSCH transmission is scheduled to begin in a next symbol after a last symbol of the first PUSCH transmission.

24. The method of claim 19 , wherein the first PUSCH transmission at least partially overlaps in time with the second PUSCH transmission.

25. The method of claim 19 , wherein the second PUSCH transmission associated with the second PDCCH transmission is a retransmission of data of the first PUSCH transmission.

26. The method of claim 19 , wherein the first and second PUSCH transmissions are positioned in a same slot.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 17, 2022
From: HURD, MAGNUS; SUN, YING; ZHANG, JIANWEI; GAO, SHIWEI; MURUGANATHAN, SIVA
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 060835/0980 →
Continuity (2)
Provisional Application 62987119 · Mar 9, 2020
Related Publication 20230125953A1 · Apr 27, 2023
References Cited (32)
US 12089224B2 · Chen · 2024 [cited by examiner]
US 20190320420A1 · Zhang · 2019 [cited by examiner]
US 20200015177A1 · Kim et al. · 2020 [cited by applicant]
US 20200053754A1 · Manolakos · 2020 [cited by examiner]
US 20200153581A1 · Tsai · 2020 [cited by examiner]
US 20200196346A1 · Khoshnevisan · 2020 [cited by examiner]
US 20200204312A1 · Xu · 2020 [cited by examiner]
US 20200228246A1 · Chendamarai Kannan · 2020 [cited by examiner]
US 20200229182A1 · Khoshnevisan · 2020 [cited by examiner]
US 20210014883A1 · Khoshnevisan · 2021 [cited by examiner]
US 20210195600A1 · Khoshnevisan · 2021 [cited by examiner]
US 20210306123A1 · Gao · 2021 [cited by examiner]
US 20220039073A1 · Lee · 2022 [cited by examiner]
US 20220052727A1 · Sun · 2022 [cited by examiner]
US 20220095367A1 · Kim · 2022 [cited by examiner]
US 20220217753A1 · Yokomakura · 2022 [cited by examiner]
US 20220400041A1 · Ling · 2022 [cited by examiner]
US 20230047603A1 · Kim · 2023 [cited by examiner]
US 20230112271A1 · Kim · 2023 [cited by examiner]
CN 110870377A · 2020 [cited by applicant]
EP 3591920A1 · 2020 [cited by applicant]
TW 201947965A · 2019 [cited by applicant]
WO 2019031882A1 · 2019 [cited by applicant]
WO 2019217852A1 · 2019 [cited by applicant]
International Search Report and Written Opinion dated Oct. 27, 2021 for International Application No. PCT/SE2021/050204 filed Mar. 9, 2021; consisting of 17 pages. [cited by applicant]
3GPP TS 38.214 V15.8.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network: NR; Physical layer procedures for data (Release 15); Dec. 2019; consisting of 106 pages. [cited by applicant]
3GPP TSG-RAN WG1 Meeting #99 R1-1913564; Title: Summary #2 of Enhancements to Scheduling/HARQ; Agenda item: 7.2.6.4; Source: Qualcomm Incorporated; Document for: Discussion/Decision; Date and Location: Nov. 18-22, 2019,… [cited by applicant]
3GPP TSG RAN WG1 Meeting #97 Tdoc R1-1906097; Title: On Intra-UE prioritization enablers; Agenda Item: 7.2.6.7; Source: Ericsson; Document for: Discussion, Decision; Date and Location: May 13-17, 2019, Reno, USA; consis… [cited by applicant]
3GPP TS 38.321 V15.8.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 15); Dec. 2019; consisting of 78 pages. [cited by applicant]
3GPP TS 22.104 V16.4.0; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for cyber-physical control applications in vertical domains; Stage 1 (Release 1… [cited by applicant]
3GPP TS 38.213 V16.0.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 16); Dec. 2019; consisting of 146 pages. [cited by applicant]
Taiwanese Notice of Allowance and Search Report dated Dec. 14, 2021 and English machine translation of Notice of Allowance and English translation of Search Report for Taiwanese Application No. 110108361; consisting of … [cited by applicant]