Jaime from Mimosa here...happy to speak to the software radio related stuff, thanks Chris for mentioning. So we've done a huge amount of experimentation on auto-channel approaches now that we've had a few years to collect data and analyze. Simple answer is it's really different in different environments, and if you're collocating with yourself vs. with other WISPs and gear.
We definitely allow the B5 series to be more aggressive on auto-changes since it's dual-chain, and is in a noisy band, so moving 1 impacted chain while we keep the other up, if it means better throughput, is a nice option IF that's what you want.
To your comment Chris, we definitely will begin to open channel programming via software API for y'all, and more rich monitoring in the API/SNMP info relatively soon (hoping before year end).
When it comes to 5 GHz, I always suggest "exclude before you auto" - we were unique in offering single page spectrum setup and live spectrum analysis to make it easy for you to program where you want the radios to operate. So smarter exclusion based auto can be really nice if you know how to use it well. As you know, we built this all in the radio, but hadn't opened it up externally much other than the UI/browser.
We actually also built in some L2 and beacon discovery smarts to locally detect other radios on the same sync settings to make sure to coordinate so to speak. Frankly speaking, even if the radio wants to make a change, it has no way of knowing if it might impact something else, it just knows what's best for it's own operation without some higher level spectrum management coordination, so some coordination intelligence is a must if you have some spectrum that needs protecting when collocated.
Really the need for auto behaviors is relatively limited to backhaul and unlicensed - most don't want their sector/APs to move unless it's a major event given all the clients connected. On new products like the B24, we really just analyze narrowing channels if things get bad enough, but there's really no other channels to move to, and on licensed products, you have to stick to your licensed channel of course.
On multipoint, for example, the APs collect and analyze spectrum masks from each client, and the primary thing they'll do is allow an individual client to narrow (e.g. from the 80 MHz channel to 20 MHz) in case they see more noise in a part of the channel, poor mans OFDMA, but that functionality becomes very advanced in the 11ax based chip for us in the future.
Lots of new stuff announcing and shipping this week and in Vegas next month, so stay tuned.
We definitely allow the B5 series to be more aggressive on auto-changes since it's dual-chain, and is in a noisy band, so moving 1 impacted chain while we keep the other up, if it means better throughput, is a nice option IF that's what you want.
To your comment Chris, we definitely will begin to open channel programming via software API for y'all, and more rich monitoring in the API/SNMP info relatively soon (hoping before year end).
When it comes to 5 GHz, I always suggest "exclude before you auto" - we were unique in offering single page spectrum setup and live spectrum analysis to make it easy for you to program where you want the radios to operate. So smarter exclusion based auto can be really nice if you know how to use it well. As you know, we built this all in the radio, but hadn't opened it up externally much other than the UI/browser.
We actually also built in some L2 and beacon discovery smarts to locally detect other radios on the same sync settings to make sure to coordinate so to speak. Frankly speaking, even if the radio wants to make a change, it has no way of knowing if it might impact something else, it just knows what's best for it's own operation without some higher level spectrum management coordination, so some coordination intelligence is a must if you have some spectrum that needs protecting when collocated.
Really the need for auto behaviors is relatively limited to backhaul and unlicensed - most don't want their sector/APs to move unless it's a major event given all the clients connected. On new products like the B24, we really just analyze narrowing channels if things get bad enough, but there's really no other channels to move to, and on licensed products, you have to stick to your licensed channel of course.
On multipoint, for example, the APs collect and analyze spectrum masks from each client, and the primary thing they'll do is allow an individual client to narrow (e.g. from the 80 MHz channel to 20 MHz) in case they see more noise in a part of the channel, poor mans OFDMA, but that functionality becomes very advanced in the 11ax based chip for us in the future.
Lots of new stuff announcing and shipping this week and in Vegas next month, so stay tuned.