I want to tell you about one great feature of our mesh.
It is based on a relatively little known principle of multilateration (the cousin of trilateration) and is designed to deal with the so called noise (we call it interference).
The experts here already know this, but as it is not that obvious, let me tell you that our APs run Linux, 400 MHz CPU, have about 16MB free memory and most importantly, feature -118 db calibrated receivers with continuous FRQ tuning. Also, each of our APs keep records of its own as well as its neighbours, coordinates in a standard form, and with a resolution of zero point one arc second.
I told you before that we developed a mechanism to deal with the noise – I mean, identify the noise, measure its level, and based on that figure, selecting an alternative channel for our community use. What I did not tell you before is how we do that exactly – in techie talk.
Read on for the missing details…
So, one of our techies decided to write a little (but nevertheless very nifty) piece of code which would look for a time when some idle CPU cycles need to be kept busy and when that happens, the AP would then scan the channel, identify the interference, record it’s MAC address as an identifier, measure it’s signal strength as it is received, put all that data into a small packet and push that small packet back to us, the master ship. And it will do that for every source of interference within the 2.4 GHz – 2.483 GHz spectrum. If there is traffic, it will stay at the channel it is assigned at, and when there is no traffic, it will quickly go and scan all the channels within the spectrum.
Here is the most interesting part. You know that we intend to roll out hundreds of thousands of these APs (for the commercially open minded out there, worth hundreds of millions of rands), literary pepper the urban and semi-urban areas so to have uniform coverage, right?
Again, the same crazy eyed techie came up with the idea that if we run this “interference identification” feature, surely if we correlate the data received from three APs against same MAC address in reverse proportion to the signal strengths using the principle of trilateration we should be able to pin-point the exact location of the interference source to within zero point one arc second (for the not so smart, it is less than a meter). Then, the same techie goes on that after first determining its exact location, and as having the coordinates on record gives as the ability to calculate distance, matching that data against the received signal strength trough a calibrated receiver interface, we should be able to determine the EIRP of the transmitting source.
Now, you can imagine us standing there with our jaws dropped, but this techie does not stop – he continues with these wild plans of us running the EIRP data against the community mesh member data we have and monitoring three things (1) if the EIRP our member emit does fall within the legal limits so to allow us to warn him if he is to inadvertently breach that limit, (2) if the interference comes from external to us source (say WUG or WISP), again, measure and record it’s EIRP and location and perhaps pass that data onto someone who cares about it but does not have his/her own means of measuring EIRP and (3) offer future location-based services to our community members.
You can all imagine, after hearing these wild plans, there was this long silence in our R&D offices. In fact, we were so impressed with this small, insignificant feature of our mesh that we decided to go ahead and implement it. As you can imagine, the said techie was very pleased with himself, as he was given the opportunity to make some good, have some fun and get paid in the process.
Tell me honestly, does not this all sound super-exciting to you all?