Second "White Space" Database Completes Test

FCC requests public comment on results of Telcordia system testing

“White space” wireless operation on locally vacant TV channels requires that devices consult a database of users entitled to protection, including broadcast TV stations and some wireless microphones. See a list here. The FCC has authorized ten companies to provide and operate those databases. The second such company, Telcordia Technologies Inc., recently completed a 45-day test that began in December.

The FCC now seeks public input on the Telcordia results, which are posted here. Comments are due on February 16, 2012, and reply comments on February 23.

In the meantime, white space operations were scheduled to begin last week in Wilmington, NC, using a database provided by Telcordia’s competitor, Spectrum Bridge, the first to complete testing.

There are still eight database providers to go. We will keep track so you don’t have to.

FCC Approves First "White Space" Operations

First white space database and end-user devices to begin operation in January in Wilmington, NC.

The FCC has approved the first “white space” database and the first end-user devices to begin operation on January 26, 2012, initially limited to the Wilmington, NC area.

White space devices are supposed to provide Wi-Fi-like services, only better, using locally vacant TV channels. Successful operation will depend on complex databases to help each device identify channels on which it can safely operate, without causing interference to TV stations, radio astronomy, wireless microphones, and several other services entitled to protection. We reported just last month that the first of ten FCC-approved database providers, Spectrum Bridge Inc., had posted the results from a 45-day test of its system. The FCC has now announced its acceptance of that system, and simultaneously, its approval of an end-user white space device that operates in conjunction with the Spectrum Bridge database.

Operators of the various services protected against the devices – see a list here – should make sure their facilities are properly listed in the database.

White space operations will be limited at the outset to the environs of Wilmington, NC. Wilmington was also the city chosen by the FCC a few years back for an early trial of the cut-over from analog to digital TV. We’re not sure why the FCC keeps putting Wilmington’s TV reception at risk. Perhaps the city is an unheralded center for high-tech early adopters. Or the home of someone whom the FCC just doesn’t like.

Another White Space Database Ready to Make Its Debut

Telcordia Tech testing to take off 12/7.

Last September we reported on the fact that one of the nine (oops, make that ten) white space database administrators had announced that its system was ready to have its tires kicked. That 45-day test has since wrapped up, and the Commission has since invited comments on the results. 

And now a second database administrator – Telcordia Technologies, Inc. – has given the word that it, too, is ready for testing . . . or at least it will be, as of December 7. That date will kick off Telcordia’s 45-day test period, during which members of the public are invited to run the Telcordia system through its paces to ensure that it does what it’s supposed to do. (In case you’ve forgotten, all white space database systems are expected to (1) correctly identify channels in the TV band that are available for unlicensed operation, (2) register facilities in that band that are entitled to protection, and (3) afford protection to authorized services and registered facilities as specified in the Commission’s rules.)

You can access the Telcordia system at https://prism.telcordia.com/tvws/home/trial starting December 7 (but not before) and running through January 20, 2012, possibly longer if the Commission determines that an extension is warranted. The Commission encourages the public to take the system for a test drive to make sure that it's doing what it’s supposed to do. Items available for testing include a channel availability calculator, and separate utilities to register: MVPD receive sites; broadcast auxiliary temporary receive sites; fixed TVWS devices; and wireless microphones. Obviously, if any inaccuracies pop up, they should be reported to Telcordia pronto.

Check out our previous posts for more background on the white space database administrator program.

FCC Seeks Comment on "White Space" Database Test

The first of ten database administrators has posted the results of a 45-day test.

We reported back in September about a test of the first database for “white space” devices meant to provide Wi-Fi-like service on unused TV channels. The database – developed by Spectrum Bridge Inc. – is intended to help prevent interference from those devices into TV receivers, wireless microphones, and other authorized users of the bands. The FCC invited public participation in a 45-day online test.

Spectrum Bridge has completed its trials and submitted a “summary report” about it to the Commission. The FCC, in turn, is now requesting public input on the test result and the summary report. The request includes links to the report and three attachments submitted by Spectrum Bridge. We have been unable to access the Spectrum Bridge report and attachments by using the links provided in the FCC’s release. Presumably this is just a slight technical glitch that the FCC will correct.  However, since the Commission’s notice came out just before the start of a three-day weekend, we thought our readers might appreciate some working links to the Spectrum Bridge materials now, to give them something to pore through over the long weekend. Here they are:

The Spectrum Bridge summary report

Attachment 1 – “Dashboard” (statistics concerning traffic to the Spectrum Bridge test site)

Attachment 2 – Registration Records

Attachment 3 – Comments

Attachment 3, in particular, makes for interesting reading. It reflects a number of comments, criticisms and inquiries submitted to Spectrum Bridge during the test, and Spectrum Bridge’s responses. Some of the problems identified in the test are troubling.  For instance, Spectrum Bridge’s database ignored, at least initially, some facilities whose licenses (a) appeared to have expired but (b) were actually still in effect because of pending litigation relative to renewal of the licenses.  But it does appear that Spectrum Bridge was responsive to the problems. We shall see.

Comments on the Spectrum Bridge report are due on November 28, 2011, and reply comments on December 5.

First "White Space" Database Ready for Testing

Anyone can visit the test site to try out the white space channel availability calculator, the wireless microphone registration utility, and other functions.

Those long-promised “white space” devices, delivering super-Wi-Fi performance on locally unused TV channels, are moving a small step closer to reality.

The delay in actual availability – initial rules were adopted almost three years ago – results from the fact that these devices must protect several other services from interference. The main mechanism to achieve that protection is a set of databases that list the locations and frequencies of the services entitled to protection. A white space device is supposed to check in with a database for a safe frequency assignment before transmitting. The first of those databases is now ready for testing.

The services that qualify for protection, and which hence must be listed in the databases, are:

  • broadcast television stations (including full power, TV translator, low power TV, and Class A stations);
  • fixed broadcast auxiliary service links;
  • receive sites (and received channels) of TV translator, low power TV and Class A TV stations and multichannel video programming distributors (MVPDs);
  • private land mobile radio service and commercial mobile radio service operations
  • offshore radio telephone service operations;
  • radio astronomy operations at specific sites; and
  • certain wireless microphone operations.

The FCC has approved ten database administrators to keep track of these services. The idea is for each administrator to set up its own separate database. Each of the ten will extract information on protected services from the FCC’s licensing databases, or from the rules (except for some MVPD and wireless microphone information, which must be entered by hand by interested parties). This information need be entered into only one database, which will automatically share that information with the other nine – so that, as a result, all ten reflect the same protected services. Similarly, no matter which of the ten databases a white space device chooses to consult, it should get back the same information on available channels.

That is the theory, at least. Coordinating ten very large, constantly changing databases, each of a different fundamental design, is likely to present problems in practice.

The first of the ten databases is now ready for a 45-day period of public testing. Beginning on September 19, anyone can visit this site to test the white space channel availability calculator, the cable headend and broadcast auxiliary temporary receive site registration utilities, and the wireless microphone registration utility. Unfortunately the all-important sharing function among databases is not yet ready to try out.

Give it a try, and let us know what you find.

White Spaces Update: OMB Signs Off on Information Collections

One small step for white spaces technology . . .

The long-running, slow-paced white spaces proceeding has quietly moved ahead with OMB approval of the “information collection” requirements of Sections 15.713, 15.714, 15.715 and 15.717. Notice of that approval has just been published in the Federal Register. That means that the FCC may implement those requirements, effective now.

But don’t run down to your local Radio Shack looking for miracle white spaces devices just yet. Before the Commission can start to unleash the power of the white spaces, it’s got to settle on a database design. While the Commission has at least identified its initial corps of database managers – originally a nine-member team to which a late-arriving Microsoft was recently added as a tenth – the system which those managers will be charged with implementing is still a work in progress.

Check back here for updates.

And Microsoft Makes Ten

Microsoft decided it, too, wants to be a wireless TV Band Device database administrator.  Well, so do we.

The FCC spent calendar year 2010 studying applications from nine companies that want to be wireless TV Band Device (TVBD) database administrators. The successful applicants will coordinate devices, when they become available, that operate in TV “white space” frequencies. 

Some of the nine applicants, like Google and Comsearch, have enormous expertise in large databases, while some of the others do not.

Last January the FCC, rather than pick winners and losers, simply approved all nine companies that applied.

A few weeks ago Microsoft decided it, too, wants to be a database administrator. Never mind that Microsoft came to this realization 15 months after the application deadline, and three months after the FCC’s decision naming the other nine administrators. Never mind the FCC’s insistence on deadlines in other contexts. (Try sending in your FCC license renewal 15 months after it was due.) Microsoft for some reason gets a pass, not to mention full consideration of its application: the Commission has invited comments on Microsoft’s proposal. “We intend to consider designating Microsoft as a TV bands database administrator,” says the FCC’s public notice.   After all, it continues, Microsoft representatives attended both of the FCC’s database administrator workshops. With a track record like that, why should deadlines matter?

Omitted from the public notice, although possibly a factor in the FCC’s thinking, is that Microsoft, along with a hardware company, demonstrated a TVBD system at the National Association of Broadcasters show in April. The set-up included Microsoft’s prototype white-space database software, which sounds impressive. But the actual operations involved exactly one base station, one client station, and one pretend signal entitled to protection – a far cry from an actual working system in the real world.

Also omitted from the public notice, but probably not a factor in the FCC’s thinking, is Microsoft’s own observation that becoming a database administrator would “enable it to assist its customers in bringing many white spaces applications to market quickly and efficiently.” So what’s good for Microsoft is good for . . . um, Microsoft.

We have no doubt that Microsoft’s qualifications equal or exceed those of at least some of the nine companies selected earlier. Not obvious, though, is that Microsoft’s qualifications are so overwhelming as to justify re-opening the application process after more than a year. Hey, if it’s that easy, we might put in an application ourselves, and make some extra money at home in our spare time. And maybe Microsoft can help us with that long-overdue FCC license renewal.

White Spaces Reminder: Deadline For Registering Distant OTA Receive Sites Fast Approaching

Initial deadline: April 5, 2011

If you’re a TV licensee providing over-the-air feeds to one or more distant translator/LPTV/Class A stations, cable head-ends or satellite local receive sites, heads up. You need to act soon if you want reception of your signal at those sites to be protected from unlicensed devices operating in the TV band. April 5, 2011 is the deadline for TV stations with receive sites more than 80 kilometers beyond their protected contour to seek a waiver of the Commission’s geographic limitation to be able to register such receive locations. Note: this is a one-time-only opportunity.

Back in 2008, when the Commission adopted rules to govern the operation of unlicensed devices in the so-called “TV white spaces”, it sought to protect existing TV operations by establishing a database in which certain locations requiring protection could be registered. While receive locations that happen to be within a TV station’s protected service area were already routinely protected, that wasn’t the case for receive sites serving distant TV translator/LPTV/Class A TV stations, satellite or cable (MVPD) services, all of which deliver the signal to viewers outside the originating station’s protected contour. The Commission decided to protect, within reasonable bounds, the ability of such stations and services to receive programming over-the-air for retransmission.  “Within reasonable bounds” in this context meant within 80 kilometers of the originating TV station’s protected contour. Translator/LPTV/Class A stations and MVPD services with receive sites so located were thus allowed to register their sites in the TV bands device database.

On reconsideration, though, the FCC determined that some MVPD services and translator/LPTV/Class A stations relying on over-the-air reception to obtain and redistribute TV signals are located more than 80 kilometers from the originating TV station’s protected service contour. In order to avoid disruption in those circumstances, the Commission opted to expand the notion of “within reasonable bounds” temporarily: it provided a 90-day opportunity (commencing with the effective date of the rules) for MVPD’s, TV translator, LPTV and Class A TV stations to request a rule waiver to allow them to register their receive locations in the TV bands devices database. This opportunity is available only for locations at which the TV programming is received over-the-air more than 80 kilometers from the originating station’s protected contour.

The initial 90-day waiver request filing period will expire on April 5, 2011. (Facilities that meet the geographic standards but don’t get licensed until later will have 90 days, starting with commencement of operation, to file for a waiver.)

Waiver requests should demonstrate how the operation of an unlicensed device near the relevant receive site would act to disrupt current patterns of television viewing. After a waiver request is received, the FCC will put it out for public comment and then will make a determination as to whether it will be granted.

The Commission has not yet provided any special instructions for the filing of such a waiver request.  Check back here for updates on that score. But absent any such instructions, it would appear that filing through the Secretary’s office with a reference to ET Docket Nos. 02-380 and 04-186 should do the trick. Electronic filing in the dockets might also be a possibility – but, again, the FCC hasn’t given any guidance yet. We’ll post a follow-up on this as developments warrant.

White Space Database Administrator Sweepstakes - Everybody's A Winner! (Except Maybe Affected Spectrum Users)

Nine companies will compete while sharing responsibilities and data.

You know those T-ball games for very young children where everyone is declared a winner and everyone takes home a trophy?

Keep that in mind for a few minutes.

The FCC, as our readers know by now, has authorized wireless TV Band Devices (TVBDs) that will operate in the “white spaces” on the TV frequency map – i.e., on TV channels that have no local TV station. Proponents, who like to call these devices “Wi-Fi on steroids,” claim they will boost the availability of wireless services with extended range, fewer dead spots, and improved speeds, promote rural broadband, aid education and medicine, and further spectrum efficiency. And create jobs. And also clear up that annoying rash.

As a condition of operation, the millions of expected TVBDs will have to avoid causing interference to active TV stations, the many wireless microphones that share the TV band, and certain TV reception sites. To do this, most will consult a complex and changing database that indicates where TVBDs can safely operate. The existence of a database in turn presupposes one or more “database administrators.” Last November, the FCC invited interested parties to submit applications for that role.

Nine companies responded. Some, like Google and Comsearch, have enormous expertise in constructing and maintaining large databases. The qualifications of some others are less obvious.

The FCC made its choice by not making a choice: It approved all nine applicants as database administrators, with the expectation they will compete among themselves for business.

This inclusive non-decision may reflect the FCC’s often-expressed distaste for “picking winners and losers.” Or it might follow from the FCC’s having neglected to state, at the outset, the criteria it would use for selection, an omission that leaves it vulnerable to challenge from the losers. This problem does not arise, of course, if there are no losers.

One applicant and a wireless microphone coalition challenged the impartiality of some other applicants. The FCC responded with a stern injunction against the administrators engaging in anti-competitive practices, and a promise of careful oversight.

Here at CommLawBlog, we have two concerns.

The FCC could have decided to manage the database itself. It certainly knows how; it keeps close track of millions of licenses. The FCC opted instead to farm out the work. With one or two administrators, that might have been a labor-saving move. But riding herd on nine of them, some inexperienced, each working with a database built to a different design, might turn out to be more work for the FCC than just doing the job on its own.

The other problem relates to data quality. Each administrator will keep its own database, but all nine must reflect the same underlying reality. Some of the data are slow-moving and should be easy to maintain – TV station contours, for example, and locations of protected TV receive sites, such as cable TV headends and TV translators. Potentially more troublesome, though, will be wireless microphone users’ frequent and changing registrations as they sign up for short-term interference protection at sporting events, political events, concerts, etc. These data will be volatile.

Suppose NBC, say, as part of its planning to cover an event, logs on to its preferred database administrator and registers a few dozen wireless microphones by date, time, place, and TV channel number. That information must be made available to every TVBD in the vicinity of the event, through every database administrator. Accordingly, the administrator receiving the registration must quickly and accurately disseminate it to the other eight, in a form that allows easy incorporation into their own, differently-designed databases. This kind of coordination is hard enough among two or three parties. We wonder whether nine can bring it off reliably.

And those nine will be competitors after the same business. It may become tempting for some to try making the others look bad by feeding them bad (or late) information. Even greater will be the temptation to cut costs by using ill-trained and badly supervised staff. Just as the hygiene of a shared kitchen quickly sinks to the level of the sloppiest person using it, so will the quality of the shared data reflect the least careful administrator.  (Users may appreciate the lower cost . . . at least until they realize that you do, in fact, get what you pay for.) 

To say, “You’re all winners!” is fine for T-ball. But maintaining a large and critical database takes real skill and a large measure of dedication. We may all come to wish the FCC had exercised greater adult authority in making its choices.

Update: White Spaces Rules To Become Effective January 5, 2011*

* but NOT “information collection” rules or, as a practical matter, any white spaces rules dependent on existence of any FCC-blessed white spaces database

As we reported last September the Commission disposed of 17 petitions for reconsideration of its white spaces rules, and thereby set the stage for getting those rules up and running. Or so many folks may have thought. But no job is ever done until the paperwork is wrapped up, and the mere release of the Second Memorandum Opinion and Order didn’t do the trick – such items must first be published in the Federal Register.

That publication has now happened . . . so most – but not all – the white spaces rules are now officially set to take effect on January 5, 2011.

Why not all? Because a number of the rules – specifically, §§15.713, 15.714, 15.715 and 15.717 – involve “information collections” which can’t be implemented before the OMB approves them. So those particular rules are not subject to the January 5 effective date.

But even though we now have an official effective date, we probably won’t be seeing white spaces gear screaming off the shelves and improving all of our lives right away. That’s because the white spaces rules depend in large measure on the existence of a national white spaces database compiled and maintained by a manager . . . and the Commission has yet to sign off on a database system or select a manager. While there have been some indications that progress is being made on those fronts and that we might see some developments real soon, the roll-out of virtually all white spaces devices will, as a practical matter, be on hold until the FCC wraps up the necessary paperwork on that part of the process.

Plans For Gobbling Up TV Spectrum To Be Unveiled Post-Thanksgiving

FCC’s November 30 agenda also includes proposals affecting experimental licenses, short-term spectrum use.

The FCC is preparing itself for an exciting 2011.

Here in the CommLawBlog bunker, we usually wait for things to happen before reporting on them. But the FCC’s recent release of the planned agenda for its November 30 meeting serves up items likely to cause such a huge stir that we all might need a little advance warning.

First is a Notice of Proposed Rulemaking on “TV Spectrum Innovation.” Remember the DTV transition when, among other changes, almost all TV stations switched their channels? The FCC wants to do it again. The shift to DTV freed up 108 MHz of prime spectrum, half of which the FCC auctioned off for $20 billion. It’s hard to argue with that many zeroes, so it’s back to the well for another dip. 

The idea is to take away still more TV spectrum and auction that off, too. In theory, a displaced broadcaster could walk away with some of the auction money and open an aromatherapy boutique, or whatever his/her life’s dream is. Or he/she might double up with another broadcaster on a surviving channel. Although the FCC can authorize the channel sharing itself, sharing the auction money would require action by Congress. (As we have previously reported – here (about S. 3610) or here (about H.R. 5947), or here (about S. 3756) – that legislation is already in the works.) While the FCC has made no secret of its aim to scavenge TV spectrum for broadband use, the precise mechanics have not yet been spelled out. On November 30 we should get a clearer picture of what the FCC has in mind.

We are also interested to see how the expected changes will affect plans for “white space” devices. These, if they ever appear, are supposed to operate in unused TV spectrum, but the FCC’s plans will make that scarce. The wireless microphones used in TV and movie production, among other applications, also use vacant TV channels, and may likewise have less spectrum to work in. The “spectrum domino effect” at work.

The second item on the November 30 agenda is a proposed change to the experimental licensing rules.  This category of license allows companies, universities, and others to experiment with kinds of radios, often newly developed, that do not comply with the FCC’s detailed technical rules. In fact, most of the wireless gadgets we use every day started life under one of these experimental licenses. The substance of how these licenses work has been largely unchanged for decades. The FCC is considering a facelift to make them more flexible.

Third is a Notice of Inquiry on “opportunistic use” of spectrum. In this context the term has no derogatory connotations, but rather refers to radio technologies that “sniff” the air for temporarily vacant frequencies, and move into them until the rightful owner needs them back. The FCC here continues a sequence of developments that began with software-defined radios in 2001, and continued with cognitive radios in 2005. It also continues a parallel effort, under the general heading “secondary markets,” toward setting up licensing rules that facilitate temporary handovers of spectrum.

By the time of the FCC meeting on November 30, the leftover turkey should be gone, the tryptophan should have worn off, and we should all be ready to work. The FCC will give all of us here plenty to work on.

White Space Wite-Out®

It’s okay; we all make mistakes.

The FCC’s recent order on white space devices, which we reported on here, and followed up on here, had a few glitches. The FCC has now released a longer-than-usual erratum clearing them up.

A Closer Look At Some White Spaces Fine Print

Protection of TV STAs overlooked; Potential protection of LPTV, TV translator, cable, etc. OTA-receive sites expanded

Poring over the fine print of the FCC’s “white spaces” decision we wrote about last week, we have found two issues that merit the attention of TV broadcasters.

White spaces devices, of course, will operate on vacant TV channels and will have to protect TV broadcast stations. Each device will consult a database to determine which TV channels can be safely used at the device’s location. Devices may have to change channels as necessary from time to time to afford the required protection.

Since the selection of vacant channels will be a dynamic process, the FCC wants to make sure that only channels actually in use by TV stations are marked as off-limits. So, for example, channels occupied by unbuilt TV construction permits would be available for white spaces devices, since, being unbuilt (and, thus, inoperative), the TV CPs would not be subject to any actual interference. With that in mind, the new rules provide that the white spaces database need recognize only granted or pending license applications for both full and low power TV stations.

Whoops.  What about Special Temporary Authorizations (STAs)?

STAs are not a rarity. They are routinely issued to, say, stations that suddenly lose their transmitter sites or that suffer equipment damage during a storm. LPTV stations may well need STAs during the process of transitioning from analog to digital operation – a transition that the FCC is proposing to make mandatory. An STA allows the station to continue to operate – possibly from an alternate site or with facilities other than those specified in its license (or license application) – until it can either (a) return to its authorized site/facilities or (b) obtain permanent authority for its modified site/facilities.

The Commission’s failure to include STAs in the white spaces database appears to be a serious slip. Operation pursuant to an STA is Commission-authorized broadcast operation which should be protected from white spaces devices to the same degree as “licensed” operation.  This error seems to us to merit a petition for reconsideration by the TV industry.

The other issue involves TV translators, LPTV stations, cable systems and other multichannel video programming distributors (let’s call them, collectively, “retransmitters”). As might be expected, retransmitters  retransmit other stations’ signals, signals which are generally received by the retransmitter over-the-air. If a white spaces device cranks up near the point at which the retransmitter ordinarily picks up the signal, the retransmitter’s ability to effectively operate is threatened.

The Commission recognizes this problem. In the 2008 version of the white spaces rules, the Commission permitted some (but not all) retransmitters to register their over-the-air receive sites in the white spaces database – but only if those sites were (a) within 80 kilometers (50 miles) of the originating station’s service contour but (b) outside that station’s protected contour. Now, however, at the suggestion of a number of parties the Commission has expanded the area in which receive sites may be registered. That expansion, though, is not gotcha free. 

Under the newly-announced revisions to the rules, all (not just some) retransmitters with over-the-air receive sites more than 80 kilometers from the edge of the received station’s protected service contour may submit waiver requests seeking to have those receive sites registered. The Commission will then issue a public notice soliciting comments on such waiver requests. After reviewing everything that comes in, the Commission will decide on a case-by-case basis whether or not to include each such site in the database.

Existing operators who may wish to take advantage of this potential registration opportunity should be particularly alert. Starting with the effective date of the new rules, such operators will have 90 days in which to submit their waiver requests. (Retransmitters who commence operations in the future will have 90 days from the date on which they start up.) The Commission has not provided a time frame during which its resolution of such requests can be expected.

The effective date of the new rules has not yet been announced, and won’t occur (at the earliest) until 30 days after the new rules have been published in the Federal Register. Additionally, it seems unlikely that the Commission will invite new registrations (or registration waiver requests) until a number of practical questions relating to the white spaces database have been resolved. For example, who will manage the database, how will registrations and the like be submitted, how will the database be implemented? Obviously, there is still much to be done before white spaces devices are likely be unleashed on us all.

FCC Okays White Space Devices

New rules eliminate back-up protection for TV stations and wireless microphones.

The FCC has ruled on 17 petitions for reconsideration of the TV “white spaces” rules. This action allows unlicensed wireless networks and devices – “Wi-Fi on steroids,” some call them – to operate on locally vacant TV channels, called “white space” frequencies because they show up as white areas on maps of frequency usage. 

The FCC earlier tried to rename the gadgets “TV band devices,” or TVBDs, but the white space nomenclature is hard to shake.

Whatever the name, companies like Google, Microsoft, and Dell Computer are drooling at the prospect. They have told the FCC to expect a lot of hot spots and campus networks, and they are using all the right technical and political buzzwords.   Here in the CommLawBlog bunker, though, we're accustomed to dazzling PowerPoint that never materializes into actual products, so we tend to take a wait-and-see attitude.

The technical problems with white space devices center on avoiding interference to TV stations and the wireless microphones that have long used vacant TV channels. The original plan called for each device both to use geolocation – ascertaining its own position using GPS and consulting a database to find locally vacant channels – and also to “sniff” for TV stations and wireless microphones, a process called spectrum sensing. (The FCC exempted from geolocation certain devices under the control of other devices and, separately, allowed for the possibility of some sensing-only devices.)

The new decision confirms the geolocation requirement, with many critical details still to be fleshed out by the Office of Engineering and Technology. But the FCC has pulled back on sensing. When it tested spectrum sensing technologies several months ago, none of them worked well. This result surprised us, as white space proponents had touted sensing as the ultimate safeguard against interference. In some other universe, the agency might insist the promised technology function properly before it allowed deployment. This universe, though, works differently: the FCC’s spectrum-exploding train will not be de-railed, so they simply dropped the sensing requirement for devices that use geolocation.

Sensing-only devices are still allowed, but only under very rigid technical constraints that will be hard for manufacturers to satisfy. Because database checking will usually be the sole feature for avoiding interference, the FCC promised a rigorous certification procedure to make sure devices handle this function properly. Again, no details.

The FCC struggled, with only limited success, to accommodate users of wireless microphones in broadcasting, theater, movie-making, sporting events, and public gathering places like churches and auditoriums. The FCC will reserve two TV channels in each geographic area for wireless microphones, which it thinks will accommodate 12-16 microphone voice channels. Some parts of the country will also have other channels closed to white space devices and available for wireless microphones. Large productions, though, often use 100 or more. Microphone operators may request to have specific events entered into the white space database, which should (if all goes according to plan, that is) automatically keep white space devices away. Requests to protect unlicensed microphones must show that the channels free of white space devices cannot do the job. These requests will be subject to public comment, which requires 30 days advance notice. Without a database entry, and in the absence of spectrum sensing, the microphones will have no protection against white space devices on the same channel. 

In the end, the FCC believes wireless microphones should move to more efficient digital technology. But it did not address the difficult engineering problems that so far have barred this option.

The question of using vacant TV channels for backhaul links in rural areas is deferred.

Read the FCC’s news release on the decision and the full text of the White Spaces order.

[Blogmeister's Note:  This post has been updated as of 9/24/10 to provide additional information culled from the full text of the Commission's white spaces order.]

FCC Heading For The White Open Spaces

Upcoming Commission meeting may finally give green light to new technology

The FCC has announced that it plans to take up the long-pending white space proceeding at its upcoming September 23 meeting. Since that proceeding has been largely out of the spotlight for the better part of 18 months, it seemed a good idea to remind our readers, and ourselves, of the issues on the table in the white space proceeding and how the Commission has addressed those issues to date.

The white space proceeding started in 2002 with a reasonably straight-forward premise. Every city has dozens of TV channels, with exceptional propagation characteristics, sitting empty. Why not use them for something?  Low-power, unlicensed wireless devices operating on these unused channels – channels dubbed “white spaces” because they show up in white on a frequency map – could be deployed for a variety of uses, thereby increasing the efficient use of the spectrum. What’s not to like?

In theory, the concept looks great. But in practice, potential problems abound.

The primary concern, of course, is interference to other spectrum users. Each unlicensed device constitutes a potential source of interference if its operator happens to turn it on in the wrong place at the wrong time. And because the device is unlicensed, neither the FCC nor the victim of the interference will have any easy way of identifying the source of the interference. 

The white space proceeding has thus been an effort to take advantage of the potential for wide-spread use of low-power, unlicensed devices on TV frequencies while protecting licensed users of those frequencies. Those licensed users include not only TV stations, but also wireless microphone users (a broad universe which includes not only TV and movie producers, but also churches, theaters and live music venues).

Back in 2002 the Commission kicked things off with a Notice of Inquiry relating to the possible use of portions of the TV band for unlicensed use. From that beginning, the Commission released a Notice of Proposed Rulemaking in 2004, which led to a First Report and Order in 2006, and then a Second Report and Order in 2008. The Commission’s deliberations were complicated by the fact that, throughout this time, the TV band was in the process of the digital transition, a process which wasn’t completed for full-power stations until June, 2009.

Meanwhile, a range of white space gadgets – now renamed “television band devices” (TVBDs) – was being developed by various proponents eager to get in on the ground floor of what many perceive to be a singular opportunity to create vast new and lucrative markets. In 2007, and again in 2008, the Commission tested out a number of prototype TVBDs in the field and in its lab. The goal was to see whether the devices could provide protection against interference.

The FCC advanced two basic approaches to interference protection. In one, the TVBD is capable of: (a) accurately identifying its own location (through GPS technology); and (b) cross-checking that location against a database of existing licensed spectrum users in that area. That cross-check process would preclude use of any frequency already licensed for use within a certain area. In the second approach, the TVBD is equipped with sensing capability allowing it to “sniff out” other uses of the TV band and automatically switch channels to avoid interference to such other uses.

Through several rounds of testing – testing which did not necessarily duplicate all real-world conditions – the “sniff out” technology did not fare particularly well. Still, the FCC concluded that the results demonstrated a “proof of concept”. In 2008 it adopted rules to authorize TVBDs under certain conditions. (As my colleague Mitchell Lazarus observed at the time, the Wright Brothers at Kitty Hawk also demonstrated the feasibility of powered, heavier-than-air, flight as a “proof of concept”, but it still took 30 more years for the check-in lines to form at O’Hare.)

The 2008 rules did not give an unequivocal green light to TVBDs, however. The rules imposed three constraints:

  • Operation is flatly prohibited on certain channels, and in certain areas, and on some channels in some areas.
  • Every TVBD must know where it is, and have a current list of open channels for that location, or else it must operate under the direct control of a TVBD having that information. (Manufacturers can bypass this rule by undertaking extra procedures; see below).
  • Every TVBD must sense the spectrum for incumbents on the channel it is using.

The details were stringent. Device locations, for example, must be determined to within 50 meters, a requirement that only GPS can fulfill today. The catalog of available channels must be updated at least daily. Sensing must achieve a detection level of -114 dBm, equivalent to 0.004 trillionths of a watt – yet even this sensitivity could miss TV signals that are viewable with a good outdoor antenna.

Under the rules, TVBDs must be certified by the FCC before they can be marketed. To protect incumbent users of the TV band from millions of interference-causing renegade TVBDs, the Commission added extraordinary steps to the usual certification process. First, the manufacturer must test the device itself. Next, the Commission re-runs the tests, both in its lab and then again on the mean streets of America. Finally, the Commission seeks public comment on the TVBDs’ test results.  Only after the successful conclusion of this stringent certification process would the Commission permit the importation and sale of any TVBD.

While the rules were technically adopted in 2008, they have not, for the most part, yet taken effect.   Approval by the Office of Management and Budget is necessary before crucial elements of the new rules can be implemented. (Those crucial elements include the rules concerning the database of occupied channels and the procedures for approving sensing-only devices.) Also, to the extent that the protection system requires the existence of a comprehensive, accurate, frequently-updated database which TVBDs may check against, TVBDs can’t be rolled out until that database is in place. To date, that database is still on the drawing boards. (The Commission did invite proposals for the design and maintenance of such a database in November, 2009.)

Also, the Commission still has to resolve issues raised in 17 petitions seeking reconsideration of the 2008 rules. The petitioners include:

  • broadcast-related interests who seek a return to square one, arguing that the record does not support any unlicensed devices on TV channels;
  • LPTV stations that lack needed protection for still-ongoing analog operations;
  • petitioners objecting to a great many specific technical rules, including emission limits, separation requirements, sensing levels, power levels for first-adjacent channels, special procedures for sensing-only devices, and fixed base station heights, among others;
  • cable satellite TV providers that claim inadequate protection for headends and cable-ready TV sets; and
  • those presenting other issues: real-time operation of the database that catalogs available TV channels; database information security and registration requirements; pending negotiations with the Mexican government; rejected proposals, such as licensed use of white space frequencies; and too many more to list here.

Additionally, an appeal of the rules is pending in the U.S. Court of Appeals for the D.C. Circuit, although that has been held in abeyance while the FCC works through the reconsiderations and database development.

So when the Commission rolls up its sleeves to tackle the white space proceeding at its September 23 meeting, it will theoretically be trying to (a) resolve the pending petitions for reconsideration and (b) get the database set up. 

While those are already complex problems, they are further complicated by the brooding omnipresence that casts its shadow on everything the Commission does these days: the National Broadband Plan (NBP). The NBP expressly recommended that the Commission move forward with the white-spaces proceeding. That makes sense, since the NBP is all about increasing the efficient use of spectrum while encouraging technological innovation. 

But the NBP also entails the possibility – if not substantial likelihood – that the FCC may reallocate up to 120 MHz of TV spectrum for broadband use. That in turn would require “repacking” of the remaining TV spectrum by moving existing TV stations from the reallocated spectrum to channels in the remaining TV band. The repacking process would almost certainly increase congestion in the TV band, which could reduce available white space and thus complicate the roll-out of white space devices.

There is much at stake in the highly technical, highly contentious white space proceeding. The Commission has thus far struggled to strike a workable balance between protection of incumbent licensees and the desire to unleash innovative TVBD services. Presumably that struggle continues.   Just among ourselves, we think it might even continue beyond the September 23 meeting.

Get Out Your Crayons and Glue Stick: It's Design-a-Database Time

Regular readers know that the FCC adopted rules to allow new, unlicensed, wireless devices to operate in unused channels of the broadcast television spectrum just over a year ago. This was an exciting development for wireless broadband access and content providers, but incumbent users (such as television broadcasters and wireless microphone operators) worried about interference. Therefore, the FCC required that white space devices – which it calls “TV band devices” – must prevent interference by having both spectrum-sensing capability and also geo-location capability with access to a database of licensed users. The idea is that a device will: (a) access a database; (b) let the data base know where the device happens to be located;  and (c) receive a list of available frequencies for that location.  As an additional safeguard, devices will also detect other users and drop off their frequencies.  A separate and more stringent procedure will authorize “sensing only” devices that lack geo-location.

Obviously, establishing a database is a crucial step in the process of designing and testing these new devices because they must be able to interface with it.  Accordingly, on November 25, 2009, the FCC’s Office of Engineering and Technology issued a Public Notice “inviting proposals from entities seeking to be designated TV band database managers.”  

This is in part a creative design competition: the FCC specifies only that each design must include “basic functional architecture . . . a data repository, a data registration process, and a query process.” Beyond that, prospective database managers are limited only by the scope of their imaginations and the number of pipe cleaners they can grab off the craft table.

Each applicant must provide: 

  • A demonstration of sufficient technical expertise;
  • A demonstration of a viable business plan;
  • The scope of the database functions it plans to perform;
  • If the plan involves multiple databases, a description of how data will be synchronized;
  • If the plan involves multiple entities, information on other involved entities and their business relationship with the applicant; and
  • A description of the methods (e.g., interfaces, protocols) to be used by devices to communicate with the database, including any security measures.

Proposals must be submitted by January 4, 2010. They will presumably be made available for review by the public soon thereafter, because the Commission has also invited comments (due February 3, 2010) and replies (due February 18, 2010) on the proposals. Sharpen those crayons, because we expect that neatness will count.

Welcome to the White Spaces - No License? No Problem!

 FCC opens TV band to unlicensed devices

The FCC has voted to allow unlicensed devices to use "white spaces" in the TV band for wireless broadband. Preliminarily, only devices that determine available channels based on geolocation and a database of existing users will be authorized, but procedures have been put in place to allow future approval of devices that choose available channels based on only signal-sensing.

This is a preliminary report based on listening to the discussion at the FCC meeting and review of the public notice issued by the Commission following its meeting. The actual report and order may reflect edits made after the meeting and so may not be exactly the same as this description.

Both fixed location and personal portable transmitters will be permitted. Fixed devices will be allowed to use higher power than portable devices. Portable devices must have automatic power control that reduces operating power to the minimum required to link successfully to a base station or other portable device with which it communicates.

Initially, both fixed and portable devices must rely on geolocation and a database of existing users. Portable devices that do not themselves incorporate geolocation and a user database may not operate unless they establish a link with, and are assigned a channel by, a base station that does use geolocation and a database. Both broadcast stations and venues where large numbers of wireless microphones are in use may be registered in the database. All white space devices must also incorporate spectrum-sensing, which is intended to avoid interference to other wireless microphones and broadcast signals that may not be registered in the database.

Fixed devices will be registered in a database. Portable devices will not be registered. No provision was made for any licensed devices, including backhaul point-to-point links in rural areas, but a notice of inquiry will be issued to explore higher powered rural operations.

Operation near cable television head-ends will be restricted. Other than that, all TV channels in the range 2-51 will be open to these new devices. VHF channels were not withheld, nor were Channels 14-20, which are used for public safety operations in major cities.

In the future, the FCC will allow unlicensed devices that select operating channels based on only spectrum-sensing. These devices must be tested and certified by the FCC Laboratory before marketing and must prove that they avoid interference to existing operations. Applications for equipment certification will be placed in public notice. In what appears to be a first for the FCC, the testing of these devices will be open to the public, and public comment on test results will be permitted.

The commissioners did not all agree that devices that only sense existing spectrum use are ready for mass marketing at this time. At least one also felt that white space devices would not be able to operate successfully at all in the largest cities. 

Some commissioners stressed that white space devices would remain secondary to television broadcast services, but it is not clear at this point that the intent of some white space proponents to achieve stronger spectrum rights was completely rejected.

While prospective manufacturers of white space devices assured the FCC that it was in their self-interest to avoid interference, the FCC did not establish any expedited procedures for dealing with interference complaints, nor did it provide for recall of defective products and forfeitures for causing interference.

It is not clear what will happen now other than almost certain skirmishes as white space hardware is submitted for FCC Laboratory testing. Dealing with any problems that arise will be left to a Commission that will almost surely have a new chairman and perhaps other new commissioners.