The big TV white spaces news this week was the move to establish a white spaces database group comprising Google, Microsoft, Motorola, Dell, Comsearch, NeuStar and HP.
Why all the fuss?
For those not familiar with the concept of ‘white spaces’, this is the term used to describe the unoccupied frequencies in a band. The term ‘TV whitespace’ means the occupied frequencies or slots in the 54-698MHz frequency range used for U.S. TV channels 2 to 51.
The upper end of this frequency range is of particular interest though because:
- The antenna sizes needed to operate in this band are shorter than say, at 60MHz.
- There’s enough available bandwidth between occupied channels to roll out useful broadband type services and create new revenue streams.
- Signals in this frequency range can penetrate buildings and operate over non line-of-sight ranges
In November, 2008, the FCC gave the ok for unlicenced use of the U.S. TV bands subject to a set of rules in the second report and order and memoradam opinion and order document.
These rules included the following requirement for a white space database and a request for a third-party interested in creating and maintaining the database:
All devices, except personal/portable devices operating in client mode, must include a
geolocation capability and provisions to access over the Internet a database of protected radio
services and the locations and channels that may be used by the unlicensed devices at each
location. The unlicensed devices must first access the database to obtain a list of the
permitted channels before operating.
A white spaces database is needed is because the TV bands are used differently across the U.S (and indeed, Ireland and many other countries). For example, occupied TV channels in Virginia may not be in use in California. To minimise the possibility of interference to TV receivers and the unlicenced services, companies will need to find out where the available channels are in the area where the new services are to be deployed.
The creation of this database will not be straightforward. Currently, there is no common database standard for representing how spectrum is being used. Unlicenced devices must check the database before operating, which presents a big challenge of how to build in this requirement in rural deployments. A centralised database is a weakness and a distributed database requires a means of replication and updating.
Tom and I carried out the first look at how TV spectrum is used along a route that brought us from Colorado, through Chicago, and onward to Washington DC. We created a monitoring toolset and database for collecting the spectrum-usage information that allows us to query and visualise the measurement database using Google Maps. After visiting a number of groups and companies along the route, including Illinois Institute of Technology, Motorola, and Shared Spectrum, we discovered that each group has their own database structure (including us). The need for a common database standard and means of extracting information from it was raised by us in our IEEE DySPAN 2008 plenary talk and in our 2008 SDR Forum conference presentation in Washington DC.

To make this work, Google, Microsoft, Motorola, Dell, Comsearch, NeuStar and HP are going to need an independent group of people to coordinate with all the interested parties and ensure the needs of each group is represented in a common white space database standard. As we found from our spectrum measurements roadtrip, information from the FCC license database needs to be supplemented with actual spectrum measurements. This task is immense therefore the database should allow for submitted updates from trusted third parties e.g. university research groups conducting measurement programmes.
Talk to us, I may know the right people who can help.