IP Library › Granted Patent US 12,261,786
Granted Patent B2
US 12,261,786 · App. 18/371,911 · Granted Mar 25, 2025

Beam-based PDCCH transmission in NR

Inventors: Mahmoud Taherzadeh Boroujeni (San Diego, CA); Oghenekome Oteri (San Diego, CA); Loic Canonne-Velasquez (Dorval, CA); Shahrokh Nayeb Nazar (San Diego, CA); Afshin Haghighat (Ile-Bizard, CA)
Assignee: InterDigital Patent Holdings, Inc.
H04L5/0023H04L5/0094
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,261,786
App. No.
18/371,911
Granted
Mar 25, 2025
Kind
B2
Abstract

Systems, methods and instrumentalities are disclosed for beam-based PDCCH Transmission in NR. Control resource sets may be assigned for multi-beam control transmission. A PDCCH may be transmitted with multiple beams. CCEs may be mapped for multi-beam transmission. DCI may support multi-dimensional transmission with primary and secondary dimensions. Search space may support multi-beam, multi-TRP transmission.

Claims (35)

1. A wireless transmit/receive unit (WTRU), the WTRU comprising:

a processor, the processor configured to:

determine a first set of control channel elements (CCEs) from a plurality of CCEs, wherein the first set of CCEs is associated with a first beam and a first search space (SS), and wherein the first SS is associated with a first control resource set (CORESET);

determine a second set of CCEs from the plurality of CCEs, wherein the second set of CCEs is associated with a second beam and a second SS, and wherein the second SS is associated with a second CORESET;

determine that the first set of CCEs is associated with the second set of CCEs;

receive at least one of a first physical downlink control channel (PDCCH) transmission using the first beam and the first set of CCEs, or a second PDCCH transmission using the second beam and the second set of CCEs; and

decode a downlink control information (DCI) using the at least one of the first PDCCH transmission or the second PDCCH transmission.

2. The WTRU of claim 1 , wherein the processor being configured to determine that the first set of CCEs is associated with the second set of CCEs comprises the processor being configured to determine that the first set of CCEs is associated with the second set of CCEs using the first SS and the second SS.

3. The WTRU of claim 1 , wherein the first set of CCEs is different from the second set of CCEs.

4. The WTRU of claim 1 , wherein the first set of CCEs is further associated with a first quasi co-location (QCL) information, wherein the second set of CCEs is further associated with a second QCL information, and wherein the first QCL information is different from the second QCL information.

5. The WTRU of claim 1 , wherein the first PDCCH transmission and the second PDCCH transmission are associated with a multibeam PDCCH transmission.

6. The WTRU of claim 1 , wherein the processor being configured to receive at least one of the PDCCH transmission using the first beam and the first set of CCEs, or the second PDCCH transmission using the second beam and the second set of CCEs comprises the processor being configured to monitor the first set of CCEs using the first beam and the second set of CCEs using the second beam.

7. The WTRU of claim 1 , wherein the first set of CCEs is further associated with a first set of orthogonal frequency divisional access (OFDM) symbols, wherein the second set of CCEs is further associated with a second set of OFDM symbols, and wherein the first set of OFDM symbols is different from the second set of OFDM symbols.

8. A method performed by a wireless transmit/receive unit (WTRU), the method comprising:

determining a first set of control channel elements (CCEs) from a plurality of CCEs, wherein the first set of CCEs is associated with a first beam and a first search space (SS), and wherein the first SS is associated with a first control resource set (CORESET);

determining a second set of CCEs from the plurality of CCEs, wherein the second set of CCEs is associated with a second beam and a second SS, and wherein the second SS is associated with a second CORESET;

determining that the first set of CCEs is associated with the second set of CCEs;

receiving at least one of a first physical downlink control channel (PDCCH) transmission using the first beam and the first set of CCEs, or a second PDCCH transmission using the second beam and the second set of CCEs; and

decoding a downlink control information (DCI) using the at least one of the first PDCCH transmission or the second PDCCH transmission.

9. The method of claim 8 , wherein determining that the first set of CCEs is associated with the second set of CCEs comprises determining that the first set of CCEs is associated with the second set of CCEs using the first SS and the second SS.

10. The method of claim 8 , wherein the first set of CCEs is different from the second set of CCEs.

11. The method of claim 8 , wherein the first set of CCEs is further associated with a first quasi co-location (QCL) information, wherein the second set of CCEs is further associated with a second QCL information, and wherein the first QCL information is different from the second QCL information.

12. The method of claim 8 , wherein the first PDCCH transmission and the second PDCCH transmission are associated with a multibeam PDCCH transmission.

13. The method of claim 8 , wherein the receiving at least one of the PDCCH transmission using the first beam and the first set of CCEs, or the second PDCCH transmission using the second beam and the second set of CCEs comprises monitoring the first set of CCEs using the first beam and the second set of CCEs using the second beam.

14. The method of claim 8 , wherein the first set of CCEs is further associated with a first set of orthogonal frequency divisional multiple access (OFDM) symbols, wherein the second set of CCEs is further associated with a second set of OFDM symbols, and wherein the first set of OFDM symbols is different from the second set of OFDM symbols.

15. A wireless transmit/receive unit (WTRU) the WTRU comprising:

a processor, the processor configured to:

determine a plurality of control channel elements (CCEs) that are associated with a control resource set (CORESET);

determine a set of CCEs from the plurality of CCEs;

receive a first physical downlink control channel (PDCCH) transmission using a first beam and a second PDCCH transmission using a second beam, wherein the first beam is associated with the set of CCEs, and wherein the second beam is associated with the set of CCEs; and

decode a downlink control information (DCI) using at least one of the first PDCCH transmission or the second PDCCH transmission.

16. The WTRU of claim 15 , wherein the CORESET indicates a first quasi collocated (QCL) information associated with the first beam and indicates a second QCL associated with the second beam.

17. The WTRU of claim 15 , wherein the set of CCEs is associated with a search space.

18. The WTRU of claim 15 , wherein the first PDCCH transmission and the second PDCCH transmission are associated with a multibeam PDCCH transmission.

19. The WTRU of claim 15 , wherein the processor being configured to receive the first PDCCH transmission using the first beam and the second PDCCH transmission using the second beam comprises the processor being configured to monitor the set of CCEs using the first beam and the second beam.

Continuity (6)
Continuation 16609478
Provisional Application 62500645 · May 3, 2017
Provisional Application 62519555 · Jun 14, 2017
Provisional Application 62543087 · Aug 9, 2017
Provisional Application 62599124 · Dec 15, 2017
Related Publication 20240014956A1 · Jan 11, 2024
References Cited (140)
US 8774104B2 · Zeira et al. · 2014 [cited by applicant]
US 9313782B2 · Chen et al. · 2016 [cited by applicant]
US 9473965B2 · Lee et al. · 2016 [cited by applicant]
US 9794913B2 · Lee et al. · 2017 [cited by applicant]
US 9867186B2 · Xu et al. · 2018 [cited by applicant]
US 9918335B2 · Kim et al. · 2018 [cited by applicant]
US 10165582B2 · Papasakellariou · 2018 [cited by applicant]
US 10652876B2 · Seo et al. · 2020 [cited by applicant]
US 10743297B2 · Nazar et al. · 2020 [cited by applicant]
US 11026253B2 · Venugopal · 2021 [cited by examiner]
US 11218271B2 · Xiong et al. · 2022 [cited by applicant]
US 11799600B2 · Boroujeni · 2023 [cited by examiner]
US 20120282936A1 · Gao et al. · 2012 [cited by applicant]
US 20130021994A1 · Ji et al. · 2013 [cited by applicant]
US 20130039284A1 · Marinier et al. · 2013 [cited by applicant]
US 20130039824A1 · Abu-sharkh · 2013 [cited by applicant]
US 20130242882A1 · Blankenship et al. · 2013 [cited by applicant]
US 20140286297A1 · Zhao et al. · 2014 [cited by applicant]
US 20140328295A1 · Ko et al. · 2014 [cited by applicant]
US 20150092646A1 · Tabet et al. · 2015 [cited by applicant]
US 20160113008A1 · Damnjanovic et al. · 2016 [cited by applicant]
US 20160242203A1 · You et al. · 2016 [cited by applicant]
US 20170013626A1 · Nan et al. · 2017 [cited by applicant]
US 20170332359A1 · Tsai et al. · 2017 [cited by applicant]
US 20170353963A1 · Hong et al. · 2017 [cited by applicant]
US 20170359807A1 · Hong et al. · 2017 [cited by applicant]
US 20180198650A1 · Nogami et al. · 2018 [cited by applicant]
US 20180227102A1 · John Wilson et al. · 2018 [cited by applicant]
US 20180227156A1 · Papasakellariou · 2018 [cited by applicant]
US 20180227887A1 · Hakola et al. · 2018 [cited by applicant]
US 20180254853A1 · Jung et al. · 2018 [cited by applicant]
US 20180279135A1 · Hwang et al. · 2018 [cited by applicant]
US 20180279273A1 · Yang et al. · 2018 [cited by applicant]
US 20180324816A1 · Islam et al. · 2018 [cited by applicant]
US 20180368116A1 · Liao et al. · 2018 [cited by applicant]
US 20190020506A1 · Cheng et al. · 2019 [cited by applicant]
US 20190028234A1 · Seo et al. · 2019 [cited by applicant]
US 20190037540A1 · Seo et al. · 2019 [cited by applicant]
US 20190103941A1 · Seo et al. · 2019 [cited by applicant]
US 20190132851A1 · Davydov et al. · 2019 [cited by applicant]
US 20190158205A1 · Sheng et al. · 2019 [cited by applicant]
US 20190173622A1 · Xiong et al. · 2019 [cited by applicant]
US 20190253308A1 · Huang et al. · 2019 [cited by applicant]
US 20190268208A1 · Seo et al. · 2019 [cited by applicant]
US 20190297602A1 · You et al. · 2019 [cited by applicant]
US 20190305867A1 · Tseng et al. · 2019 [cited by applicant]
US 20190335492A1 · Venugopal · 2019 [cited by examiner]
US 20190349960A1 · Li et al. · 2019 [cited by applicant]
US 20200008231A1 · Vilaipornsawai et al. · 2020 [cited by applicant]
US 20200028651A1 · Xu · 2020 [cited by applicant]
US 20200029310A1 · Lee et al. · 2020 [cited by applicant]
US 20200036497A1 · Xu · 2020 [cited by applicant]
US 20200119895A1 · Choi et al. · 2020 [cited by applicant]
US 20200145079A1 · Marinier et al. · 2020 [cited by applicant]
US 20200154295A1 · Lin · 2020 [cited by applicant]
US 20200252957A1 · Cai et al. · 2020 [cited by applicant]
US 20200389847A1 · Deng et al. · 2020 [cited by applicant]
US 20210112533A1 · Tang · 2021 [cited by applicant]
US 20210227572A1 · Miao et al. · 2021 [cited by applicant]
US 20220070909A1 · Takeda et al. · 2022 [cited by applicant]
US 20230217278A1 · Xu et al. · 2023 [cited by applicant]
CN 102395206A · 2012 [cited by applicant]
CN 103326841A · 2013 [cited by applicant]
CN 103650618A · 2014 [cited by applicant]
CN 103828282A · 2014 [cited by applicant]
CN 103916962A · 2014 [cited by applicant]
CN 104081709A · 2014 [cited by applicant]
CN 104823475A · 2015 [cited by applicant]
CN 105162565A · 2015 [cited by applicant]
CN 106888079B · 2021 [cited by applicant]
GB 2568486A · 2019 [cited by applicant]
JP 2016518091A · 2016 [cited by applicant]
RU 2521486C2 · 2014 [cited by applicant]
TW 201342860A · 2013 [cited by applicant]
TW 201709706A · 2017 [cited by applicant]
WO 2009006016A2 · 2009 [cited by applicant]
WO 2009046061A2 · 2009 [cited by applicant]
WO 2009158050A2 · 2009 [cited by applicant]
WO 2011066793A1 · 2011 [cited by applicant]
WO 2013141530A1 · 2013 [cited by applicant]
WO 2014121641A1 · 2014 [cited by applicant]
WO 2016022849A1 · 2016 [cited by applicant]
WO 2017160100A2 · 2017 [cited by applicant]
WO 2017171327A2 · 2017 [cited by applicant]
WO 2017173038A1 · 2017 [cited by applicant]
WO 2018204282A1 · 2018 [cited by applicant]
R1-1700257, , “NR DL Control Channel Structure”, ZTE, ZTE Microelectronics, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, Spokane, USA, Jan. 16-20, 2017, pp. 1-6. [cited by applicant]
R1-1700346, , “On Beam State Reporting”, Intel Corporation, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, Spokane, USA, Jan. 16-20, 2017, pp. 1-6. [cited by applicant]
R1-1704202, , “Search Space Design Considerations”, 3GPP TSG RAN WG1 Meeting #88bis; Huawei, HiSilicon; Spokane, USA, Apr. 3-7, 2017, 4 pages. [cited by applicant]
R1-1704618, , “Search Space Design Consideration for NR PDCCH with BF”, Guangdong OPPO Mobile Telecom, 3GPP TSG RAN WG1 Meeting #88bis, Spokane, Washington, Apr. 3-7, 2017, 8 pages. [cited by applicant]
R1-1704950, , “Search Space Design for NR-PDCCH”, ETRI, 3GPP TSG RAN WG1 #88bis, Spokane, USA, Apr. 3-7, 2017, pp. 1-4. [cited by applicant]
R1-1705583, , “Control Channel Multi-Beam Operation”, 3GPP TSG-RAN WG1 #88bis; Qualcomm Incorporated; Spokane, USA, Apr. 3-7, 2017, 4 pages. [cited by applicant]
R1-1708333, , “On Multi-TRP/Panel Transmission for DL”, InterDigital Inc., 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, 4 pages. [cited by applicant]
R1-1708345, , “Design Considerations for Beam-Based PDCCH”, InterDigital Inc., 3GPP TSG RAN WG1 Meeting #89, Hangzhou, China, May 15-19, 2017, pp. 1-4. [cited by applicant]
R1-1710923, , “DCI Design for Multi-TRP/Panel Transmission for DL”, InterDigital Inc., 3GPP TSG RAN WG1 Meeting NRAH2, Qingdao, China, Jun. 27-30, 2017, 3 pages. [cited by applicant]
R1-1710944, , “On the Impact of Multi-Beam Operation on PDCCH Structure”, InterDigital Inc., 3GPP TSG RAN WG1 NR Ad-Hoc#2, Qingdao, China, Jun. 27-30, 2017, pp. 1-5. [cited by applicant]
TS 36.211 V10.0.0, , “3rd Generation Partnership Project (3GPP)”, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Channels and Modulation (Release 10), D… [cited by applicant]
TS 36.213 V14.2.0, , “3rd Generation Partnership Project (3GPP)”, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Layer Procedures (Release 14), Mar. 201… [cited by applicant]
3rd Generation Partnership Project(3GPP), R1-1705718, “Views on beam management framework”, 3GPP TSG RAN WG1, Meeting #88bis, NTT DOCOMO, Inc. Spokane, USA, Apr. 3-7, 2017, 8 pages. [cited by applicant]
TS 36.211 V15.3.0, , “3rd Generation Partnership Project (3GPP)”, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical channels and modulation (Release 15), S… [cited by applicant]
IEEE Standard for Information technology—Telecommunications and Information Exchange between Systems—Local and Metropolitan Area Networks—Specific Requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physi… [cited by applicant]
IEEE Standard for Information technology—Telecommunications and information exchange between systems Local and metropolitan area networks—Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
IEEE Standard for Information Technology—Telecommunications and Information Exchange between Systems Local and Metropolitan Area Networks—Specific Requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
IEEE Standard for Information technology—Telecommunications and Information Exchange between Systems Local and Metropolitan Area Networks Specific Requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Phys… [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.211 V14.5.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Channels and Modulation, (Release 14), De… [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.211 V14.8.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Channels and Modulation (Release 14), Sep… [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.211 V15.3.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Channels and Modulation, (Release 15), Se… [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.211 V2.0.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Channels and Modulation (Release 8), Sep. … [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.213 V14.4.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Layer Procedures (Release 14), Sep. 2017,… [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.213 V14.8.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical layer procedures (Release 14), Sep. 2018,… [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.213 V15.3.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Layer Procedures, (Release 15), Sep. 2018… [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 36.213 V2.0.0, Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA), Physical Layer Procedures (Release 8), Sep. 2007, p… [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 38.213 V15.3.0, Technical Specification Group Radio Access Network, NR, Physical Layer Procedures for Control (Release 15), Sep. 2018, pp. 1-101. [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 38.331 V15.0.0, Technical Specification Group Radio Access Network NR Radio Resource Control (RRC) Protocol Specification (Release 15), Dec. 2017, pp. 1-188. [cited by applicant]
“3rd Generation Partnership Project (3GPP)”, TS 38.331 V15.3.0, Technical Specification Group Radio Access Network, NR, Radio Resource Control (RRC) protocol specification, (Release 15), Sep. 2018, pp. 1-445. [cited by applicant]
3 [cited by applicant]
3 [cited by applicant]