IP Library › Granted Patent US 12,219,568
Granted Patent B2
US 12,219,568 · App. 18/332,093 · Granted Feb 4, 2025

Transmission using a plurality of wireless resources

Inventors: Yunjung Yi (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Jonghyun Park (Syosset, NY); Nazanin Rastegardoost (McLean, VA); Ali Cagatay Cirik (Chantilly, VA); Kai Xu (Herndon, VA); Hua Zhou (Vienna, VA); Hyoungsuk Jeon (Centreville, VA)
Assignee: Comcast Cable Communications, LLC
H04W72/21H04W72/044
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,219,568
App. No.
18/332,093
Granted
Feb 4, 2025
Kind
B2
Abstract

A base station and/or a wireless device may communicate using a plurality of wireless resources. Multiple carriers may be used for a transmission such that portions of the transmission may be transmitted using different carriers. Multiple carrier transmission may be independently configured for each of a plurality of wireless resources.

Claims (47)

1. A method comprising:

receiving, by a wireless device, configuration parameters that indicate a plurality of frequency locations for physical resource blocks (PRBs) of an uplink resource of a cell, wherein the PRBs comprise a first PRB and a second PRB;

sending at least a first portion of an uplink transmission via the first PRB and using a first control resource set (CORESET) pool of the cell; and

sending at least a second portion of the uplink transmission via the second PRB and using a second CORESET pool of the cell.

2. The method of claim 1 , wherein the configuration parameters indicate carrier switching between the sending the at least the first portion of the uplink transmission and the sending the at least the second portion of the uplink transmission.

3. The method of claim 1 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a first frequency location and a frequency offset.

4. The method of claim 1 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a first frequency location and a second frequency location.

5. The method of claim 1 , wherein:

the sending the at least the first portion of the uplink transmission via the first PRB comprises sending only the first portion of the uplink transmission via the first PRB; and

the sending the at least the second portion of the uplink transmission via the second PRB comprises sending only the second portion of the uplink transmission via the second PRB.

6. The method of claim 1 , wherein the sending the at least the first portion of the uplink transmission and the at least the second portion of the uplink transmission comprises sending the at least the first portion of the uplink transmission and the at least the second portion of the uplink transmission via a same slot or via different slots.

7. The method of claim 1 , the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a hopping pattern for the PRBs.

8. The method of claim 1 , wherein:

the uplink resource comprises a physical uplink control channel (PUCCH) resource; and

the uplink transmission comprises uplink control information (UCI).

9. 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 configuration parameters that indicate a plurality of frequency locations for physical resource blocks (PRBs) of an uplink resource of a cell, wherein the PRBs comprise a first PRB and a second PRB;

send at least a first portion of an uplink transmission via the first PRB and using a first control resource set (CORESET) pool of the cell; and

send at least a second portion of the uplink transmission via the second PRB and using a second CORESET pool of the cell.

10. The wireless device of claim 9 , wherein the configuration parameters indicate carrier switching between sending the at least the first portion of the uplink transmission and sending the at least the second portion of the uplink transmission.

11. The wireless device of claim 9 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a first frequency location and a frequency offset.

12. The wireless device of claim 9 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a first frequency location and a second frequency location.

13. The wireless device of claim 9 , wherein the instructions, when executed by the one or more processors, cause the wireless device to:

send the at least the first portion of the uplink transmission via the first PRB by causing sending only the first portion of the uplink transmission via the first PRB; and

send the at least the second portion of the uplink transmission via the second PRB by causing sending only the second portion of the uplink transmission via the second PRB.

14. The wireless device of claim 9 , wherein the instructions, when executed by the one or more processors, cause the wireless device to send the at least the first portion of the uplink transmission and the at least the second portion of the uplink transmission by causing sending the at least the first portion of the uplink transmission and the at least the second portion of the uplink transmission via a same slot or via different slots.

15. The wireless device of claim 9 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a hopping pattern for the PRBs.

16. The wireless device of claim 9 , wherein:

the uplink resource comprises a physical uplink control channel (PUCCH) resource; and

the uplink transmission comprises uplink control information (UCI).

17. A non-transitory computer readable medium storing instructions that, when executed, cause:

receiving, by a wireless device, configuration parameters that indicate a plurality of frequency locations for physical resource blocks (PRBs) of an uplink resource of a cell, wherein the PRBs comprise a first PRB and a second PRB;

sending at least a first portion of an uplink transmission via the first PRB and using a first control resource set (CORESET) pool of the cell; and

sending at least a second portion of the uplink transmission via the second PRB and using a second CORESET pool of the cell.

18. The non-transitory computer readable medium of claim 17 , wherein the configuration parameters indicate carrier switching between the sending the at least the first portion of the uplink transmission and the sending the at least the second portion of the uplink transmission.

19. The non-transitory computer readable medium of claim 17 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a first frequency location and a frequency offset.

20. The non-transitory computer readable medium of claim 17 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a first frequency location and a second frequency location.

21. The non-transitory computer readable medium of claim 17 , wherein the instructions, when executed, cause:

sending the at least the first portion of the uplink transmission via the first PRB by causing sending only the first portion of the uplink transmission via the first PRB; and

sending the at least the second portion of the uplink transmission via the second PRB by causing sending only the second portion of the uplink transmission via the second PRB.

22. The non-transitory computer readable medium of claim 17 , wherein the instructions, when executed, cause sending the at least the first portion of the uplink transmission and the at least the second portion of the uplink transmission by causing sending the at least the first portion of the uplink transmission and the at least the second portion of the uplink transmission via a same slot or via different slots.

23. The non-transitory computer readable medium of claim 17 , wherein the configuration parameters indicating the plurality of frequency locations for the PRBs comprises the configuration parameters indicating a hopping pattern for the PRBs.

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

the uplink resource comprises a physical uplink control channel (PUCCH) resource; and

the uplink transmission comprises uplink control information (UCI).

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2024
From: YI, YUNJUNG; DINAN, ESMAEL HEJAZI; PARK, JONGHYUN; RASTEGARDOOST, NAZANIN; CIRIK, ALI CAGATAY; XU, KAI; ZHOU, HUA; JEON, HYOUNGSUK
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068453/0814 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2024
From: YI, YUNJUNG; DINAN, ESMAEL HEJAZI; PARK, JONGHYUN; RASTEGARDOOST, NAZANIN; CIRIK, ALI CAGATAY; XU, KAI; ZHOU, HUA; JEON, HYOUNGSUK
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068453/0896 →
Continuity (3)
Continuation 17323928 · May 18, 2021
Provisional Application 63026457 · May 18, 2020
Related Publication 20240089972A1 · Mar 14, 2024
References Cited (48)
US 7808883B2 · Green · 2010 [cited by applicant]
US 10313079B2 · Yerramalli et al. · 2019 [cited by applicant]
US 10334450B2 · Bendlin et al. · 2019 [cited by applicant]
US 10411838B2 · Xu et al. · 2019 [cited by applicant]
US 11723032B2 · Yi · 2023 [cited by examiner]
US 20160157218A1 · Nam · 2016 [cited by examiner]
US 20180020360A1 · Yerramalli et al. · 2018 [cited by applicant]
US 20190141698A1 · Kim et al. · 2019 [cited by applicant]
US 20190319823A1 · Akkarakaran et al. · 2019 [cited by applicant]
US 20200100116A1 · Chakraborty et al. · 2020 [cited by applicant]
US 20200367208A1 · Khoshnevisan et al. · 2020 [cited by applicant]
US 20210050955A1 · Park et al. · 2021 [cited by applicant]
US 20220295484A1 · Yi · 2022 [cited by examiner]
US 20220361202A1 · Yi · 2022 [cited by examiner]
CN 101534525B · 2012 [cited by applicant]
EP 3282791A1 · 2018 [cited by applicant]
EP 2678968B1 · 2018 [cited by applicant]
EP 3537818A1 · 2019 [cited by applicant]
EP 3618335A1 · 2020 [cited by applicant]
WO 2019105392A1 · 2019 [cited by applicant]
R1-1814378; 3GPP TSG-RAN WG1 Meeting #95; Spokane, WA, USA; Nov. 12-Nov. 16, 2018; Ericsson, “Combined CR of all essential corrections to 38.211 from RAN 1#94bis and RAN1#95”. [cited by applicant]
Oct. 29, 2021—European Search Report—EP 21174415.6. [cited by applicant]
3GPP TS 38.211 V15.4.0 (Dec. 2018), 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.213 V16.0.0 (Dec. 2019) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for control (Release 16). [cited by applicant]
3GPP TS 38.331 V15.8.0 (Dec. 2019) 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 15). [cited by applicant]
R1-2003282 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Futurewei, Title: Coverage recovery for RedCap. [cited by applicant]
R1-2003291 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Ericsson, Title: Functionality for coverage recovery for RedCap. [cited by applicant]
R1-2003303 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Huawei, HiSilicon, Title: Functionality for coverage recovery. [cited by applicant]
R1-2003343 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Sierra Wireless, Title: Potential techniques for NR coverage enhancements. [cited by applicant]
R1-2003347 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: vivo, Title: Discussion on potential techniques for coverage enhancements. [cited by applicant]
R1-2003646 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Catt, Title: Coverage recovery for reduced capability NR devices. [cited by applicant]
R1-2003651 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Catt, Title: Discussion on the method for coverage enhancement. [cited by applicant]
R1-2003772 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Intel Corporation, Title: On coverage recovery for RedCap NR Ues. [cited by applicant]
R1-2003775 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Intel Corporation, Title: Discussion on potential techniques for NR coverage enhancement. [cited by applicant]
R1-2003835 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: China Telecom, Title: Potential solutions for PUSCH coverage enhancements. [cited by applicant]
R1-2003916 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Samsung, Title: Considerations on potential techniques for coverage enhancement. [cited by applicant]
R1-2003938 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Nomor Research GmbH, Facebook, Title: Potential solutions on coverage enhancement for FR1. [cited by applicant]
R1-2004106 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Oppo, Title: Discussion on functionality for coverage recovery. [cited by applicant]
R1-2004109 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Oppo, Title: The potential solutions to enhance NR coverage. [cited by applicant]
R1-2004180 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Nokia, Nokia Shanghai Bell, Title: Discussion on possible approaches and solutions for NR coverage enhancement. [cited by applicant]
R1-2004195 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Sony, Title: Coverage recovery techniques for reduced capability NR devices. [cited by applicant]
R1-2004198 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Sony, Title: Techniques for NR coverage enhancement. [cited by applicant]
R1-2004250 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Apple Inc., Title: On potential techniques for coverage enhancement. [cited by applicant]
R1-2004253 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Apple Inc., Title: Coverage recovery for reduced capability NR devices. [cited by applicant]
R1-2004254 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Ericsson, Title: Potential areas for coverage enhancement. [cited by applicant]
R1-2004426 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: NTT Docomo, Inc., Title: Potential techniques for coverage enhancements. [cited by applicant]
R1-2004495 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Qualcomm Incorporated, Title: Considerations for coverage recovery of RedCap devices. [cited by applicant]
R1-2004532 3GPP TSG RAN WG1 Meeting #101-e, eMeeting, May 25-Jun. 5, 2020, Source: Xiaomi, Title: Initial discussion on coverage recovery for reduced capability device. [cited by applicant]