I understand the SAS's only job is protecting incumbents and PALs. Having it do what you suggest might not be hard, but it'd have to be programmed and that's another set of code. I am sure there will be lots of ideas like this and I too wonder just how granular management by the SAS will be.
Patrick Leary M 727.501.3735 [cid:[email protected]]<http://mkt2.us/TelrdNet> From: Af [mailto:[email protected]] On Behalf Of Mathew Howard Sent: Wednesday, May 13, 2015 5:19 PM To: af Subject: Re: [AFMUG] FCC 3.5 GHZ and Cambium 450 I wonder if there will be any possibility of trying to request a specific frequency from the SAS, or if it is going to be completely controlled from the SAS side... it seems reasonable that if you're in an area where nothing is in use, there's no reason that it shouldn't allow you to use adjacent channels if you ask, and the radios could be designed to dynamically fall back to a single channel if necessary. On Wed, May 13, 2015 at 12:16 PM, Patrick Leary <[email protected]<mailto:[email protected]>> wrote: As I understand it, the SAS will only be required to "try" to keep those owning two 10 MHz PALs in one census areas contiguous, and even then will not be required to do so. I think it will be tough to do carrier agg in 3.55-3.7 GHz given the new rules, even as a PAL licensee, much less as a GAA user. Further, I'm uncertain of the technical complexity in getting a base station to be have dynamic flexibility in frequency assignment in it carrier aggregation feature. I would suspect such a thing would not be easy to implement -- seems easy enough in a none aggregating set of spectrum or a fixed set of aggregated spectrum, but to have multiple carriers, with each set potentially dynamic AND aggregated? I'm very doubtful. What would be much better is MU-MIMO. That will still give you the doubling of capacity, but enables you to do that within the same 10 or 20 MHz channel. Patrick Leary M 727.501.3735<tel:727.501.3735> [cid:[email protected]]<http://mkt2.us/TelrdNet> From: Af [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Mike Hammett Sent: Saturday, April 18, 2015 9:47 AM To: [email protected]<mailto:[email protected]> Subject: Re: [AFMUG] FCC 3.5 GHZ and Cambium 450 I don't see why you couldn't have 20 MHz. There haven't been technical enough rules put out to know if you can do ABAB. I'm guessing not as the SAS will tell you what frequency to use, but maybe they'll be able to support common systems. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com [Image removed by sender.]<https://www.facebook.com/ICSIL>[Image removed by sender.]<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>[Image removed by sender.]<https://www.linkedin.com/company/intelligent-computing-solutions>[Image removed by sender.]<https://twitter.com/ICSIL> ________________________________ From: "Matt" <[email protected]<mailto:[email protected]>> To: [email protected]<mailto:[email protected]> Sent: Saturday, April 18, 2015 7:42:36 AM Subject: [AFMUG] FCC 3.5 GHZ and Cambium 450 Has anyone heard how the Cambium 450 gear will work with the new 3.5Ghz FCC rules and additional spectrum? Will he still have 20Mhz channels and ABAB capability? How will this all work? ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************ ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************ ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************ ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************
