IP Library › Granted Patent US 12,395,925
Granted Patent B2
US 12,395,925 · App. 19/081,449 · Granted Aug 19, 2025

Systems/methods of 5G optimization

Inventors: Peter D. Karabinis (Cary, NC); Dimitrios P. Karabinis (Edmonds, WA)
H04W48/16H04L67/51H04L69/18H04W40/32H04J2211/005H04J2211/006H04L5/0007H04W8/005H04W84/047H04W88/04
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,925
App. No.
19/081,449
Granted
Aug 19, 2025
Kind
B2
Abstract

A plurality of transmit/receive modes is established and is used selectively to communicate responsive to a parameter that is associated with data to be transmitted/received; and wirelessly communicating by using a 5G air interface and by using at least one transmit/receive mode of the plurality of transmit/receive modes. Only one transmit/receive mode is selected and used at any one time to communicate; wherein the transmit/receive mode that is used is selected responsive to said parameter that is associated with data to be transmitted/received. The plurality of transmit modes differ from one another in frequencies, subcarriers, a Fourier transform, an inverse Fourier transform, an antenna configuration, a power level and/or a physical layer of an air interface being used. The plurality of receive modes also differ from one another.

Claims (89)

1. A first device that is configured to perform operations comprising:

establishing a plurality of transmit/receive modes responsive to instructions received from a second device;

communicating with the second device using at least one transmit/receive mode of the plurality of transmit/receive modes;

at any given time, while communicating with the second device, using only one transmit/receive mode of the plurality of transmit/receive modes; and

selecting and using a transmit/receive mode of the plurality of transmit/receive modes responsive to a parameter associated with data that is to be transmitted/received, wherein said parameter comprises a value of data, a size of data, a velocity, a quality-of-service, an interference level, a bit-error-rate, a data rate, a time-of-day, a security/privacy concern, a location of the second device and/or a distance between the first device and the second device,

wherein responsive to said parameter associated with data that is to be transmitted/received, the operations include:

varying a bandwidth;

varying a power level;

varying a physical layer of an air interface;

varying a plurality of subcarriers;

varying frequencies; and

varying a Fourier transform, an inverse Fourier transform and/or an antenna configuration.

2. The first device of claim 1 ,

wherein said plurality of transmit/receive modes comprises three transmit modes that differ from one another in frequencies being used, subcarriers being used, a Fourier transform, an inverse Fourier transform, an antenna configuration, a power level and/or a physical layer of an air interface being used; and

wherein said plurality of transmit/receive modes further comprises three receive modes that differ from one another in frequencies being used, subcarriers being used, a Fourier transform, an inverse Fourier transform, an antenna configuration, a power level and/or a physical layer of an air interface being used.

3. The first device of claim 2 ,

wherein a first transmit mode of the three transmit modes differs from a second transmit mode of the three transmit modes in at least one frequency being used, in at least one subcarrier being used, in an inverse Fourier transform being used, in an antenna configuration being used, in a power level being used and in a physical layer of an air interface being used; and

wherein a first receive mode of the three receive modes differs from a second receive

mode of the three receive modes in at least one frequency being used, in at least one subcarrier being used, in a Fourier transform being used, in an antenna configuration being used, in a power level being used and in a physical layer of an air interface being used.

4. The first device of claim 1 , wherein said communicating with the second device using at least one of the plurality of transmit/receive modes comprises:

concurrently with said communicating with the second device using the at least one of the plurality of transmit/receive modes, communicating with the second device using a transmit/receive mode that is not included in the plurality of transmit/receive modes.

5. The first device of claim 4 , wherein the operations further comprise:

causing a receiver that receives first and second data from respective said at least one transmit/receive mode of the plurality of transmit/receive modes and said transmit/receive mode that is not included in the plurality of transmit/receive modes, to augment/append the first data with the second data.

6. The first device of claim 1 ,

wherein a first transmit mode of the plurality of transmit/receive modes comprises subcarriers of a transmit carrier;

wherein a second transmit mode of the plurality of transmit/receive modes, that differs from the first transmit mode, comprises subcarriers of the transmit carrier;

wherein a first receive mode of the plurality of transmit/receive modes comprises subcarriers of a receive carrier; and

wherein a second receive mode of the plurality of transmit/receive modes, that differs from the first receive mode, comprises subcarriers of the receive carrier.

7. The first device of claim 1 , wherein the operations further comprise:

selectively varying an antenna configuration, a Fourier transform and/or an inverse Fourier transform that is/are associated with said communicating with the second device responsive to said parameter associated with data that is to be transmitted/received.

8. The first device of claim 1 , wherein the operations further comprise:

establishing at least one new transmit/receive mode responsive to: the first device or the second device having changed position, an interference level and/or a quality-of-service concern.

9. The first device of claim 1 , wherein responsive to said selecting, the operations further comprise:

refraining from using a first transmit/receive mode of the plurality of transmit/receive modes; and

using a second transmit/receive mode of the plurality of transmit/receive modes.

10. The first device of claim 9 ,

wherein a bandwidth associated with said second transmit/receive mode differs from a bandwidth associated with said first transmit/receive mode;

wherein a power level associated with said second transmit/receive mode differs from a power level associated with said first transmit/receive mode;

wherein a physical layer of an air interface associated with said second transmit/receive mode differs from a physical layer of an air interface associated with said first transmit/receive mode;

wherein a plurality of subcarriers associated with said second transmit/receive mode differs from a plurality of subcarriers associated with said first transmit/receive mode;

wherein a set of frequencies associated with said second transmit/receive mode differs from a set of frequencies associated with said first transmit/receive mode; and

wherein a Fourier transform, an inverse Fourier transform and/or an antenna configuration associated with said second transmit/receive mode differ(s) from a respective Fourier transform, an inverse Fourier transform and/or an antenna configuration associated with said first transmit/receive mode.

11. The first device of claim 10 , wherein the set of frequencies associated with said second transmit/receive mode at least partially overlaps with the set of frequencies associated with said first transmit/receive mode.

12. The first device of claim 10 , wherein the physical layer of the air interface associated with said second transmit/receive mode comprises a modulation variant relative to the physical layer of the air interface associated with said first transmit/receive mode.

13. The first device of claim 12 , wherein said modulation variant comprises a Quadrature Amplitude Modulation (QAM) variant.

14. A communications method comprising:

establishing at a first device a plurality of transmit/receive modes responsive to instructions received at the first device from a second device;

communicating with the second device using at least one transmit/receive mode of the plurality of transmit/receive modes;

at any given time, while communicating with the second device, using only one transmit/receive mode of the plurality of transmit/receive modes; and

selecting and using a transmit/receive mode of the plurality of transmit/receive modes responsive to a parameter associated with data that is to be transmitted/received, wherein said parameter comprises a size of data, a velocity, a quality-of-service, an interference level, a bit-error-rate, a data rate, a time-of-day, a value of data, a security/privacy concern, a location of the second device and/or a distance between the first device and the second device,

wherein responsive to said parameter associated with data that is to be transmitted/received, the method includes:

varying a bandwidth;

varying a power level;

varying a physical layer of an air interface;

varying a plurality of subcarriers;

varying frequencies; and

varying a Fourier transform, an inverse Fourier transform and/or an antenna configuration.

15. The communications method of claim 14 ,

wherein said plurality of transmit/receive modes comprises three transmit modes that differ from one another in frequencies being used, subcarriers being used, a Fourier transform, an inverse Fourier transform, an antenna configuration, a power level and/or a physical layer of an air interface being used; and

wherein said plurality of transmit/receive modes further comprises three receive modes that differ from one another in frequencies being used, subcarriers being used, a Fourier transform, an inverse Fourier transform, an antenna configuration, a power level and/or a physical layer of an air interface being used.

16. The communications method of claim 15 ,

wherein a first transmit mode of the three transmit modes differs from a second transmit mode of the three transmit modes in at least one frequency being used, in at least one subcarrier being used, in an inverse Fourier transform being used, in an antenna configuration being used, in a power level being used and in a physical layer of an air interface being used; and

wherein a first receive mode of the three receive modes differs from a second receive mode of the three receive modes in at least one frequency being used, in at least one subcarrier being used, in a Fourier transform being used, in an antenna configuration being used, in a power level being used and in a physical layer of an air interface being used.

17. The communications method of claim 14 , wherein said communicating with the second device using at least one of the plurality of transmit/receive modes comprises:

concurrently with said communicating with the second device using the at least one of the plurality of transmit/receive modes, communicating with the second device using a transmit/receive mode that is not included in the plurality of transmit/receive modes.

18. The communications method of claim 17 , further comprising:

causing a receiver that receives first and second data from respective said at least one transmit/receive mode of the plurality of transmit/receive modes and said transmit/receive mode that is not included in the plurality of transmit/receive modes, to augment/append the first data with the second data.

19. The communications method of claim 14 ,

wherein a first transmit mode of the plurality of transmit/receive modes comprises subcarriers of a transmit carrier;

wherein a second transmit mode of the plurality of transmit/receive modes, that differs from the first transmit mode, comprises subcarriers of the transmit carrier;

wherein a first receive mode of the plurality of transmit/receive modes comprises subcarriers of a receive carrier; and

wherein a second receive mode of the plurality of transmit/receive modes, that differs from the first receive mode, comprises subcarriers of the receive carrier.

20. The communications method of claim 14 , further comprising:

selectively varying an antenna configuration, a Fourier transform and/or an inverse Fourier transform that is/are associated with said communicating with the second device responsive to said parameter associated with data that is to be transmitted/received.

21. The communications method of claim 14 , further comprising:

establishing at least one new transmit/receive mode responsive to: the first device or the second device having changed position, an interference level and/or a quality-of-service concern.

22. The communications method of claim 14 , wherein responsive to said selecting, the method further comprises:

refraining from using a first transmit/receive mode of the plurality of transmit/receive modes; and

using a second transmit/receive mode of the plurality of transmit/receive modes.

23. The communications method of claim 22 ,

wherein a bandwidth associated with said second transmit/receive mode differs from a bandwidth associated with said first transmit/receive mode;

wherein a power level associated with said second transmit/receive mode differs from a power level associated with said first transmit/receive mode;

wherein a physical layer of an air interface associated with said second transmit/receive mode differs from a physical layer of an air interface associated with said first transmit/receive mode;

wherein a plurality of subcarriers associated with said second transmit/receive mode differs from a plurality of subcarriers associated with said first transmit/receive mode;

wherein a set of frequencies associated with said second transmit/receive mode differs from a set of frequencies associated with said first transmit/receive mode; and

wherein a Fourier transform, an inverse Fourier transform and/or an antenna configuration associated with said second transmit/receive mode differ(s) from a respective Fourier transform, an inverse Fourier transform and/or an antenna configuration associated with said first transmit/receive mode.

24. The communications method of claim 23 , wherein the set of frequencies associated with said second transmit/receive mode at least partially overlaps with the set of frequencies associated with said first transmit/receive mode.

25. The communications method of claim 23 , wherein the physical layer of the air interface associated with said second transmit/receive mode comprises a modulation variant relative to the physical layer of the air interface associated with said first transmit/receive mode.

26. The communications method of claim 25 , wherein said modulation variant comprises a Quadrature Amplitude Modulation (QAM) variant.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 12, 2025
From: KARABINIS, PETER D.
To: ENK WIRELESS, INC.
Reel/Frame 071548/0797 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 12, 2025
From: KARABINIS, DIMITRIOS
To: ENK WIRELESS, INC.
Reel/Frame 071548/0799 →
Continuity (16)
Continuation 19055404 · Feb 17, 2025
Continuation 18955340 · Nov 21, 2024
Continuation 18789534 · Jul 30, 2024
Continuation 18751995 · Jun 24, 2024
Continuation 18594718 · Mar 4, 2024
Continuation 18587798 · Feb 26, 2024
Continuation 18397042 · Dec 27, 2023
Continuation 18467796 · Sep 15, 2023
Continuation 18166830 · Feb 9, 2023
Continuation 17082907 · Oct 28, 2020
Continuation 16781091 · Feb 4, 2020
Division 16385608 · Apr 16, 2019
Division 15868281 · Jan 11, 2018
Provisional Application 62451245 · Jan 27, 2017
Provisional Application 62445929 · Jan 13, 2017
Related Publication 20250212102A1 · Jun 26, 2025
References Cited (296)
US 4631734A · Foschini · 1986 [cited by applicant]
US 6097771A · Foschini · 2000 [cited by applicant]
US 6317466B1 · Foschini et al. · 2001 [cited by applicant]
US 6763073B2 · Foschini et al. · 2004 [cited by applicant]
US 6888809B1 · Foschini et al. · 2005 [cited by applicant]
US 6973843B2 · Shyy et al. · 2005 [cited by applicant]
US 7006795B2 · Foschini et al. · 2006 [cited by applicant]
US 7031699B1 · Andersen · 2006 [cited by applicant]
US 7050510B2 · Foschini et al. · 2006 [cited by applicant]
US 7116722B2 · Foschini et al. · 2006 [cited by applicant]
US 7155229B2 · Dent · 2006 [cited by applicant]
US 7203490B2 · Karabinis et al. · 2007 [cited by applicant]
US 7444170B2 · Karabinis · 2008 [cited by applicant]
US 7831201B2 · Karabinis · 2010 [cited by applicant]
US 7848774B2 · Park · 2010 [cited by applicant]
US 8018907B2 · Kubler et al. · 2011 [cited by applicant]
US 8108004B2 · Karabinis · 2012 [cited by applicant]
US 8170474B2 · Karabinis et al. · 2012 [cited by applicant]
US 8340592B2 · Karabinis · 2012 [cited by applicant]
US 9232406B2 · Karabinis · 2016 [cited by applicant]
US 9264991B1 · Vleugels et al. · 2016 [cited by applicant]
US 9338690B2 · Torsner et al. · 2016 [cited by applicant]
US 10057385B1 · Nguyen et al. · 2018 [cited by applicant]
US 10136470B2 · Cook · 2018 [cited by applicant]
US 10159097B2 · Ji et al. · 2018 [cited by applicant]
US 10181985B1 · Passaglia et al. · 2019 [cited by applicant]
US 10334515B2 · Karabinis · 2019 [cited by applicant]
US 10375730B2 · Kim et al. · 2019 [cited by applicant]
US 10477457B2 · Park et al. · 2019 [cited by applicant]
US 10548068B2 · Lee et al. · 2020 [cited by applicant]
US 10555321B2 · Andou et al. · 2020 [cited by applicant]
US 10595267B2 · Karabinis · 2020 [cited by applicant]
US 10638484B2 · Seo et al. · 2020 [cited by applicant]
US 10749644B2 · Islam et al. · 2020 [cited by applicant]
US 10791562B2 · Ryoo et al. · 2020 [cited by applicant]
US 10856215B2 · Karabinis · 2020 [cited by applicant]
US 10880032B2 · Yi et al. · 2020 [cited by applicant]
US 10893518B2 · Shen et al. · 2021 [cited by applicant]
US 10904830B2 · Yi et al. · 2021 [cited by applicant]
US 10925033B2 · Wang et al. · 2021 [cited by applicant]
US 10944450B2 · Park et al. · 2021 [cited by applicant]
US 10958384B2 · Hwang et al. · 2021 [cited by applicant]
US 10966228B2 · Park et al. · 2021 [cited by applicant]
US 10979265B2 · Yi et al. · 2021 [cited by applicant]
US 11012963B2 · Ren et al. · 2021 [cited by applicant]
US 11026199B2 · Nam et al. · 2021 [cited by applicant]
US 11050599B2 · Zhang et al. · 2021 [cited by applicant]
US 11071172B2 · He et al. · 2021 [cited by applicant]
US 11076365B2 · Kim et al. · 2021 [cited by applicant]
US 11095412B2 · Dou et al. · 2021 [cited by applicant]
US 11139937B2 · Kim et al. · 2021 [cited by applicant]
US 11140640B2 · Tooher et al. · 2021 [cited by applicant]
US 11160051B2 · Park et al. · 2021 [cited by applicant]
US 11219036B2 · Yi et al. · 2022 [cited by applicant]
US 11284439B2 · Yi et al. · 2022 [cited by applicant]
US 11316643B2 · Yang · 2022 [cited by applicant]
US 11317397B2 · Yi et al. · 2022 [cited by applicant]
US 11329779B2 · Qin et al. · 2022 [cited by applicant]
US 11363548B2 · Kim et al. · 2022 [cited by applicant]
US 11419115B2 · Xue et al. · 2022 [cited by applicant]
US 11576165B2 · Ryu et al. · 2023 [cited by applicant]
US 11601872B2 · Karabinis · 2023 [cited by applicant]
US 11658788B2 · Cao et al. · 2023 [cited by applicant]
US 11664942B2 · Chou et al. · 2023 [cited by applicant]
US 11765646B2 · Karabinis · 2023 [cited by applicant]
US 11818703B2 · Yi et al. · 2023 [cited by applicant]
US 11838244B2 · Pelletier et al. · 2023 [cited by applicant]
US 11849445B2 · Ryoo et al. · 2023 [cited by applicant]
US 11877230B2 · Park et al. · 2024 [cited by applicant]
US 11889408B2 · Karabinis · 2024 [cited by applicant]
US 11974217B1 · Karabinis · 2024 [cited by applicant]
US 12015569B2 · Luo et al. · 2024 [cited by applicant]
US 12057981B2 · Park et al. · 2024 [cited by applicant]
US 12069694B2 · Adjakple et al. · 2024 [cited by applicant]
US 12096345B2 · Karabinis et al. · 2024 [cited by applicant]
US 20040181602A1 · Fink · 2004 [cited by applicant]
US 20040264592A1 · Sibecas et al. · 2004 [cited by applicant]
US 20060176271A1 · Polivy et al. · 2006 [cited by applicant]
US 20060226991A1 · Rivas · 2006 [cited by applicant]
US 20070047678A1 · Sibecas et al. · 2007 [cited by applicant]
US 20070256135A1 · Doradla et al. · 2007 [cited by applicant]
US 20080031370A1 · Guey et al. · 2008 [cited by applicant]
US 20080246629A1 · Tsui et al. · 2008 [cited by applicant]
US 20090168730A1 · Baum et al. · 2009 [cited by applicant]
US 20090190926A1 · Charlet et al. · 2009 [cited by applicant]
US 20090224983A1 · Laroia et al. · 2009 [cited by applicant]
US 20090285173A1 · Koorapaty et al. · 2009 [cited by applicant]
US 20100135445A1 · Sari · 2010 [cited by applicant]
US 20100195566A1 · Krishnamurthy et al. · 2010 [cited by applicant]
US 20120170533A1 · Ahn et al. · 2012 [cited by applicant]
US 20120258715A1 · Souissi et al. · 2012 [cited by applicant]
US 20120275378A1 · Lee · 2012 [cited by applicant]
US 20120316414A1 · Greene · 2012 [cited by applicant]
US 20130223294A1 · Karjalainen et al. · 2013 [cited by applicant]
US 20130279614A1 · Walton et al. · 2013 [cited by applicant]
US 20140006496A1 · Dearman et al. · 2014 [cited by applicant]
US 20140010149A1 · Cook · 2014 [cited by applicant]
US 20140029485A1 · Bowman et al. · 2014 [cited by applicant]
US 20140081087A1 · Yu · 2014 [cited by applicant]
US 20140148138A1 · Chou · 2014 [cited by applicant]
US 20140249937A1 · McNally · 2014 [cited by applicant]
US 20140293890A1 · Davydov et al. · 2014 [cited by applicant]
US 20140295766A1 · Matsumoto et al. · 2014 [cited by applicant]
US 20140328313A1 · Merlin et al. · 2014 [cited by applicant]
US 20140355591A1 · Oh et al. · 2014 [cited by applicant]
US 20150004935A1 · Fu · 2015 [cited by applicant]
US 20150054654A1 · Albinali · 2015 [cited by applicant]
US 20150072622A1 · Hwang · 2015 [cited by applicant]
US 20150085737A1 · Han et al. · 2015 [cited by applicant]
US 20150180549A1 · Nagasaki · 2015 [cited by applicant]
US 20150264677A1 · He et al. · 2015 [cited by applicant]
US 20160081064A1 · Kwak et al. · 2016 [cited by applicant]
US 20160087766A1 · Sun et al. · 2016 [cited by applicant]
US 20160219424A1 · Xu · 2016 [cited by applicant]
US 20160269930A1 · Huang et al. · 2016 [cited by applicant]
US 20160286340A1 · Zhu · 2016 [cited by applicant]
US 20170010666A1 · Tanaka et al. · 2017 [cited by applicant]
US 20170126459A1 · Dutronc et al. · 2017 [cited by applicant]
US 20170169693A1 · Obaidi et al. · 2017 [cited by applicant]
US 20170318563A1 · Yang et al. · 2017 [cited by applicant]
US 20170338978A1 · Monsen · 2017 [cited by applicant]
US 20180054724A1 · Cariou et al. · 2018 [cited by applicant]
US 20180077708A1 · Lepp et al. · 2018 [cited by applicant]
US 20180159958A1 · Olive et al. · 2018 [cited by applicant]
US 20180176937A1 · Chen et al. · 2018 [cited by applicant]
US 20180218220A1 · Jung et al. · 2018 [cited by applicant]
US 20180234869A1 · Sirotkin et al. · 2018 [cited by applicant]
US 20190341993A1 · Karabinis · 2019 [cited by applicant]
US 20190342901A1 · Karabinis · 2019 [cited by applicant]
US 20190364558A1 · Kim et al. · 2019 [cited by applicant]
US 20200067513A1 · Dgani et al. · 2020 [cited by applicant]
US 20200074857A1 · Karabinis · 2020 [cited by applicant]
US 20210345263A1 · Tooher et al. · 2021 [cited by applicant]
US 20220039094A1 · Lee et al. · 2022 [cited by applicant]
US 20220095385A1 · Yi et al. · 2022 [cited by applicant]
US 20230118032A1 · Chou et al. · 2023 [cited by applicant]
US 20230171676A1 · Park et al. · 2023 [cited by applicant]
US 20230179341A1 · Marinier et al. · 2023 [cited by applicant]
US 20240023010A1 · Karabinis · 2024 [cited by applicant]
US 20240056276A1 · Pelletier et al. · 2024 [cited by applicant]
US 20240073914A1 · Haghighat et al. · 2024 [cited by applicant]
US 20240138011A1 · Deenoo et al. · 2024 [cited by applicant]
US 20240196314A1 · Karabinis · 2024 [cited by applicant]
US 20240205804A1 · Karabinis · 2024 [cited by applicant]
US 20240205982A1 · Liu et al. · 2024 [cited by applicant]
US 20250088951A1 · Karabinis · 2025 [cited by examiner]
CN 102232828A · 2011 [cited by applicant]
CN 105657717A · 2016 [cited by applicant]
EP 2091218A1 · 2009 [cited by applicant]
EP 2800338A1 · 2014 [cited by applicant]
EP 3520525B1 · 2019 [cited by applicant]
EP 3547591A1 · 2019 [cited by applicant]
EP 3829099A1 · 2021 [cited by applicant]
WO 2010059750A1 · 2010 [cited by applicant]
WO 2015114420A1 · 2015 [cited by applicant]
WO 2016127551A1 · 2016 [cited by applicant]
WO 2018084544A1 · 2018 [cited by applicant]
WO 2018085145A1 · 2018 [cited by applicant]
WO 2018128427A1 · 2018 [cited by applicant]
WO 2018128440A1 · 2018 [cited by applicant]
WO 2018133700A1 · 2018 [cited by applicant]
R1-1610127, “Numerology tradeoff case study,” Agenda Item 8.1.2.1, Source Qualcomm, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 9 pgs. [cited by applicant]
R1-1610129, “Summary of 86-19 discussion on slot structure use cases,” Agenda Item 8.1.2.2, Source Qualcomm Inc., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon Portugal, Oct. 10-14, 2016, 20 pgs. [cited by applicant]
R1-1610130, “Scaled Numerology Control Design for NR,” Agenda Item 8.1.2.2, Source Qualcomm Inc., 3GPP TSG RAN WG1 #86-BIS, Lisbon, Portugal, Oct. 10-14, 2016, 10 pgs. [cited by applicant]
R1-1610131, “NR numerology scaling and alignment,” Agenda Item 8.1.2.2, Source Qualcomm Inc., 3GPP TSG RAN WG1 #86-BIS, Lisbon, Portugal, Oct. 10-14, 2016, 5 pgs. [cited by applicant]
R1-1610156, “Single beam SYNC design,” Agenda Item 8.1.5.1, Source Qualcomm Inc., 3GPP TSG RAN WG1 #86b, Lisbon, Portugal, Sept. 10-14, 2016, 6 pgs. [cited by applicant]
R1-1610286, “Numerology for NR Synchronization Signals,” Agenda Item 8.1.5.1, Source Nokia, Alcatel-Lucent Shanghai Bell, 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1610300, “CP length for NR,” Agenda Item 8.1.2.1, Source Vodafone Group PLC Orange, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1610310, “eMBMS RS Design Considerations,” Agenda Item 7.2.4.2, Source Nokia et al., 3GPP TSG RAN WG1 Meeting #86-bis, Lisbon, Portugal, Oct. 10-14, 2016, 5 pgs. [cited by applicant]
R1-1610426, “Numerology design and link-level simulation results for high speed scenario,” Agenda Item 8.1.2.1, Source ETRI, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 9 pgs. [cited by applicant]
R1-1610500, Slides, “WF on Numerology for forward compatibility,” Agenda Item 8.1.2.1, Source InterDigital et al., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1610503, Slides, “WF on Alignments among different numerologies in frequency domain,” Agenda Item 8.1.2.1, Source LG Electronics, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 3 pgs. [cited by applicant]
R1-1610521, Slides, “WF on Subframe duration,” Agenda Item 8.1.2.1, Source ZTE et al., 3GPP TSG RAN WG1 #86b, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1610558, Slides, “WF on Synchronization Signal for NR initial access,” Agenda Item 8.1.5.1, Source Huawei, HiSilicon, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 11-14, 2016, 3 pgs. [cited by applicant]
R1-1610652, Slides, “WF on symbol level alignment,” Agenda Item 8.1.2.1, Source LG Electronics et al., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1610789, Slides, “WF on Using Scaled Numerology for DL Control,” Agenda Item 8.1.7.1, Source Qualcomm, ZTE, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 5 pgs. [cited by applicant]
R1-1610883, Slides, “WF on Using Scaled Numerology for Control Transmission,” Agenda Item 8.1.7.1, Source Qualcomm et al., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 5 pgs. [cited by applicant]
R1-1610960, Slides, “WF on RACH Preamble,” Agenda Item 8.1.5.2, Source NTT Docomo et al., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 2 pgs. [cited by applicant]
R1-1610999, Slides, “WF on UL Power Control,” Agenda Item 8.1.4.5, Source Huawei et al., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 2 pgs. [cited by applicant]
R1-1611040, “Offline outcome of Thursday afternoon on 8.1.2,” Agenda Item 8.1.2, Source NTT Docomo, Inc., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1611060, “Offline Outcome of Friday Morning,” Agenda Item 8.1.2, Source NTT Docomo, Inc., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 2 pgs. [cited by applicant]
R1-1611655, “Mechanisms of bandwidth adaptation for control and data reception in single-carrier and multi-carrier cases,” Agenda Item 7.1.1, Source Huawei and HiSilicon, 3GPP TSG RAN WG1 Meeting #87, Reno, USA, Nov. 14… [cited by applicant]
R1-1611838, “Discussion on Dynamic Bandwidth Adaptation,” Agenda Item 7.1.4.1, Source LG Electronics, 3GPP TSG RAN WG1 Meeting #87, Reno, USA, Nov. 14-18, 2016, 4 pgs. [cited by applicant]
R1-1612119, “On UE-specific Bandwidth Adaptation for Single Carrier Operation,” Agenda Item 7.1.1, Source MediaTek Inc., 3GPP TSG RAN WG1 Meeting #87, Reno, USA, Nov. 14-18, 2016, 5 pgs. [cited by applicant]
R1-1612315, “Bandwidth adaptation in NR,” Agenda Item 7.1.4.3, Source InterDigital Communications, 3GPP TSG-RAN WG1 #87, Reno, USA, Nov. 14-18, 2016, 5 pgs. [cited by applicant]
R1-1612439, “Bandwidth adaption for UE power saving,” Agenda Item, 7.1.1, Source Samsung, Reno, USA, Nov. 14-18, 2016, 2 pgs. [cited by applicant]
R1-1613218, Slides, Way Forward on UE Bandwidth adaptation in NR, Agenda Item 7.1.4, Source MediaTek et al., 3GPP TSG-RAN WG1 #87, Reno, USA, Nov. 14-18, 2016, 5 pgs. [cited by applicant]
R1-1613663, “LS on UE RF Bandwidth Adaption in NR,” Source RAN WG1, 3GPP TSG-RAN WG1 Meeting #87, Reno, USA, Nov. 14-18, 2016, 1 pg. [cited by applicant]
Sharma et al., “A Review on Bell Labs Layered Space Time Architecture (V-BLAST)” International Journal for Advance Research in Engineering and Technology 2(IV):147-154 (Apr. 2014). [cited by applicant]
T. Kim et al., “Evolution of Power Saving Technologies for 5G New Radio,” in IEEE Access, vol. 8, pp. 198912-198924, 2020, doi: 10.1109/ACCESS.2020.3035186. [cited by applicant]
U.S. Patent and Trademark Office, “Final Office Action,” U.S. Appl. No. 17/082,907, filed Nov. 30, 2022, 10 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 17/081,357, filed Mar. 23, 2022, 6 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 17/082,907, filed Aug. 3, 2022, 11 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 17/165,425, filed Oct. 20, 2022, 7 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 17/659,796, filed Jan. 20, 2023, 6 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/166,830, filed Jun. 23, 2023, 10 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/172,067, filed Dec. 8, 2023, 15 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/172,067, filed Jun. 23, 2023, 6 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/295,820, filed Aug. 14, 2024, 12 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/308,356, filed Dec. 21, 2023, 7 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/308,356, filed Mar. 28, 2024, 9 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/308,471, filed Aug. 14, 2024, 11 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/363,781, filed May 7, 2024, 9 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/363,909, filed Jun. 20, 2024, 7 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/396,894, filed Apr. 9, 2024, 14 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/396,894, filed Feb. 28, 2024, 7 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/467,796, filed Nov. 14, 2023, 16 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/587,798, filed May 7, 2024, 9 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/594,718, filed Apr. 24, 2024, 11 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/751,995, filed Sep. 5, 2024, 16 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Non-Final Office Action,” U.S. Appl. No. 18/789,534, filed Sep. 23, 2024, 11 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” U.S. Appl. No. 18/295,820, filed Sep. 11, 2024, 8 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” U.S. Appl. No. 18/308,471, filed Sep. 11, 2024, 8 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” U.S. Appl. No. 18/397,042, filed Mar. 15, 2024, 10 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fee(s) Due,” U.S. Appl. No. 18/467,796, filed Dec. 13, 2023, 8 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 17/081,357, filed Apr. 19, 2022, 6 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 17/081,357, filed Jan. 6, 2023, 5 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 17/082,907, filed Jan. 6, 2023, 5 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 17/165,425, filed Dec. 7, 2022, 12 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 17/443,710, filed Mar. 30, 2023, 16 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 17/659,796, filed Feb. 9, 2023, 5 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 18/166,830, filed Jul. 26, 2023, 7 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 18/172,067, filed Jan. 24, 2024, 6 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 18/172,067, filed Jul. 25, 2023, 5 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 18/308,356, filed May 8, 2024, 5 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 18/396,894, filed Apr. 30, 2024, 6 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 18/587,798, filed Jun. 27, 2024, 8 pgs. [cited by applicant]
U.S. Patent and Trademark Office, “Notice of Allowance and Fees Due,” U.S. Appl. No. 18/594,718, filed May 21, 2024, 7 pgs. [cited by applicant]
U.S. Appl. No. 62/373,089, filed Aug. 10, 2016. [cited by applicant]
U.S. Appl. No. 62/374,106, filed Aug. 12, 2016. [cited by applicant]
U.S. Appl. No. 62/400,950, filed Sep. 28, 2016. [cited by applicant]
U.S. Appl. No. 62/412,024, filed Oct. 24, 2016. [cited by applicant]
U.S. Appl. No. 62/416,235, filed Nov. 2, 2016. [cited by applicant]
U.S. Appl. No. 62/420,462, filed Nov. 10, 2016. [cited by applicant]
U.S. Appl. No. 62/420,588, filed Nov. 11, 2016. [cited by applicant]
U.S. Appl. No. 62/425,369, filed Nov. 22, 2016 (with English translation). [cited by applicant]
U.S. Appl. No. 62/439,434, filed Dec. 27, 2016. [cited by applicant]
U.S. Appl. No. 62/440,262, filed Dec. 29, 2016. [cited by applicant]
U.S. Appl. No. 62/442,093, filed Jan. 4, 2017. [cited by applicant]
U.S. Appl. No. 62/442,237, filed Jan. 4, 2017. [cited by applicant]
U.S. Appl. No. 62/444,198, filed Jan. 9, 2017. [cited by applicant]
United States Patent and Trademark Office, “Non-Final Office Action”, U.S. Appl. No. 18/955,340, filed Feb. 21, 2025, 8 pgs. [cited by applicant]
Wolniansky et al., “V-BLAST: An Architecture for Realizing Very High Data Rates Over the Rich-Scattering Wireless Channel” 1998 URSI International Symposium on Signals, Systems, and Electronics. Conference Proceedings (… [cited by applicant]
X. Zhu, S. Han, P.-C. Huang, A. K. Mok and D. Chen, “MBStar: A Real-time Communication Protocol for Wireless Body Area Networks,” 2011 23rd Euromicro Conference on Real-Time Systems, Porto, Portugal, 2011, pp. 57-66, do… [cited by applicant]
Zacarias et al., “BLAST Architectures” S-72.333 Postgraduate Course in Radio Communications (6 pages) (2004). [cited by applicant]
U.S. Appl. No. 18/363,781, filed Aug. 2, 2023, Peter D. Karabinis. [cited by applicant]
“5G Radio Access” Ericsson White Paper, Ericsson AB (10 pages) (Apr. 2016). [cited by applicant]
Bandwidth adaptation in NR, Agenda Item 5.1.8, InterDigital Communications, 3GPP TSG RAN WG1 NR Ad-Hoc Meeting, Spokane, USA, Jan. 16-20, 2017, 5 pgs. [cited by applicant]
Bhandari, S.; Moh, S. A Priority-Based Adaptive MAC Protocol for Wireless Body Area Networks. Sensors 2016, 16, 401. https://doi.org/10.3390/s16030401. [cited by applicant]
Foschini et al., “On Limits of Wireless Communications in a Fading Environment when Using Multiple Antennas” Wireless Personal Communications 6:311-335 (1998). [cited by applicant]
Foschini, Gerard J. “Layered Space-Time Architecture for Wireless Communication in a Fading Environment When Using Multi-Element Antennas” Bell Labs Technical Journal 1(2):41-59 (1996). [cited by applicant]
Golden et al., “V-Blast: A High Capacity Space-Time Architecture for the Rich-Scattering Wireless Channel” Bell Laboratories (18 pages) (1998). [cited by applicant]
Gomez, C.; Oller, J.; Paradells, J. Overview and Evaluation of Bluetooth Low Energy: An Emerging Low-Power Wireless Technology. Sensors 2012, 12, 11734-11753. https://doi.org/10.3390/s120911734. [cited by applicant]
Huawei, HiSilicon, Mechanisms of bandwidth adaptation, Agenda Item: 5.1.3, 3GPP TSG RAN WG1 NR Ad Hoc Meeting, R1-1700011, Spokane, USA, Jan. 16-20, 2017, 5 pgs. [cited by applicant]
Intel Corporation, On the bandwidth adaptation for NR, Agenda item: 5.1.3.1, 3GPP TSG-RAN WG1 NR Ad-Hoc Meeting, R1-1700362, Spokane, USA, Jan. 16-20, 2017, 3 pgs. [cited by applicant]
Karabinis, Peter D. “Maximum-Power and Amplitude-Equalizing Algorithms for Phase Control in Space Diversity Combining” The Bell System Technical Journal 62(1):63-89 (Jan. 1983). [cited by applicant]
Laya, A.; Alonso, L.; Alonso-Zarate, J.; Chatzimisios, P.; Reliable Machine-to-Machine Multicast Services with Multi-Radio Cooperative Retransmissions. Mobile Networks and Applications manuscript. Retrieved from https:/… [cited by applicant]
LG Electronics, Further discussion on bandwidth adaptation, 3GPP TSG RAN WG1 Meeting NR-AH1, R1-1700497, Spokane, USA, Jan. 16-20, 2017, 5 pgs. [cited by applicant]
LS on UE RF Bandwidth Adaptation in NR, 3GPP TSG-RAN WG1 Meeting #87, R1-1613663, Reno, USA, Nov. 14-18, 2016, 1 pg. [cited by applicant]
MCC Support, Final Report of 3GPP TSG RAN WG1 #86bis v1.0.0 (Lisbon, Portugal, Oct. 10-14, 2016), 3GPP TSG RAN WG1 Meeting #87, R1-1611081, Reno, USA, Nov. 14-18, 2016, 160 pgs. [cited by applicant]
Mediatek et al., Way Forward on bandwidth adaptation in NR, Agenda item 8.1.2.2, 3GPP TSG-RAN WG1 #86bis Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
Mediatek et al., Way Forward on bandwidth adaptation in NR, Agenda item 8.1.2.2, 3GPP TSG-RAN WG1 #86bis Lisbon, R1-1611041, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
Otto, C.; Milenkovix, A.; Sanders, C.; Jovanov, E.; System Architecture of a Wireless Body Area Sensor Network for Ubiquitous Health Monitoring. Journal of Mobile Multimedia, Vo. 1, No. 4 (2006) 307-326, Retrieved from … [cited by applicant]
R1-1608710, “Frame Structure for Ultra-Low Latency Scheduled-based UL Access,” Agenda Item 8.1.2.2, Source Idaho National Laboratory, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 5 pgs. [cited by applicant]
R1-1608759, “Discussion of NR Numerology,” Agenda Item 8.1.2.1, Source Catt, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 5 pgs. [cited by applicant]
R1-1608783, “NR Numerology Agnostic Synchronization Channel Design,” Agenda Item 8.1.5.1, Source Catt, 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1608807, “TDD frame structure with mixed numerology,” Agenda Item 8.1.2.2, Source Fujitsu, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1608920, “Discussion on numerology of NR,” Agenda Item 8.1.2.1, Source Spreadtrum Communications, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1608961, “Reference numerology for NR,” Agenda Item 8.1.2.1, Source ZTE and ZTE Microelectronics, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 6 pgs. [cited by applicant]
R1-1608963, “About RB grid definition and Handling Inter-numerology Interference in NR,” Agenda Item 8.1.2.1, Source ZTE and ZTE Microelectronics, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 8 p… [cited by applicant]
R1-1609045, “RB grid for mixed numerology,” Agenda Item 8.1.2.1, Source Samsung, 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1609050, “Numerology for URLLC,” Agenda Item 8.1.2.1, Source Samsung, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609112, “Numerology for NR synchronization signal,” Agenda Item 8.1.5.1, Source Samsung, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oc. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609145, “Discussion on numerology multiplexing for supporting different service requirements,” Agenda Item 8.1.2.2, Source NEC, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1609146, “Discussion on numerology of synchronization signals,” Agenda Item 8.1.5.1, Source NEC, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 2 pgs. [cited by applicant]
R1-1609153, “Discussion on PSS.SSS.PBCH in numerology multiplexing,” Agenda Item 8.1.2.1, Source NEC, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 2 pgs. [cited by applicant]
R1-1609265, “Numerology for NR Synchronization Signal,” Agenda Item 8.1.5.1, Source LG Electronics, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 7 pgs. [cited by applicant]
R1-1609273, “Overall structure of DL Control Transmission for NR,” Agenda item 8.1.7.1, Source LG Electronics, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 5 pgs. [cited by applicant]
R1-1609302, “Discussion on High Mobility Numerology and RS Design,” Agenda Item 8.1.2.1, Source CMCC, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609425, “Discussion on UE behavior on mixed numerology carrier,” Agenda Item 8.1.2.1, Source Huawei, HiSilicon, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609428, “Numerology for 70 GHz and above,” Agenda Item 8.1.2.1, Source Huawei, HiSilicon, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 6 pgs. [cited by applicant]
R1-1609503, “NR Reference numerology and time alignment,” Agenda Item 8.1.2.1, Source Intel Corporation, 3GPP TSG RAN WG1 Meeting #86b, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609504, “Slot and mini-slot numerology and alignment,” Agenda Item 8.1.2.1, Source Intel Corporation, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609659, “Guard Band Arrangement Supporting Mixed Numerology,” Agenda Item 8.1.2.1, Source Nokia, Alcatel- Lucent Shanghai Bell, 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609660, “Intra-carrier Sub-band for mixed numerology,” Agenda Item 8.1.2.1, Source Nokia, Alcatel-Lucent Shanghai Bell, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1609676, “MBSFN reference signal design,” Agenda Item AI 7.2.4.2, Source Ericsson, 3GPP TSG WG1 Meeting #86, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1609698, “Remaining numerology related aspects,” Agenda Item 8.1.2.1, Source Panasonic, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1609875, “Numerology for DL synchronization signal in NR,” Agenda Item 8.1.5.1, Source Sharp, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609876, “Numerology for PRACH Preamble in NR,” Agenda Item 8.1.5.2, Source Sharp, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 3 pgs. [cited by applicant]
R1-1609919, “Flexible Frame Structure and Control Signaling for NR,” Agenda Item 8.1.2.2, Source Motorola Mobility, 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1609978, “Design Options for Longer Cyclic Prefix and Link Level Simulation Results,” Agenda Item 7.2.4.1, Source Qualcomm Inc., 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 7 pgs. [cited by applicant]
R1-1609979, “RS Pattern for Longer CP,” Agenda Item 7.2.4.2, Source Qualcomm Inc., 3GPP TSG RAN WG1 #86b, Lisbon, Portugal, Oct. 10-14, 2016, 9 pgs. [cited by applicant]
R1-1610080, “Remaining numerology aspects,” Agenda Item 8.1.2.1, Source NTT Docomo, Inc., 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 4 pgs. [cited by applicant]
R1-1610123, “URLLC numerology and frame structure design,” Agenda Item 8.1.2.1, Source Qualcomm Inc., 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 10 pgs. [cited by applicant]
R1-1610125, “NR RB Size Design: 16 vs 12,” Agenda Item 8.1.2.1, Source Qualcomm Inc., 3GPP TSG RAN WG1 #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 10 pgs. [cited by applicant]
R1-1610126, “Scaled CP vs ECP delay spread Doppler and SNR tradeoff study,” Agenda Item 8.1.2.1, Source Qualcomm, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 10 pgs. [cited by applicant]