Tag: white spaces

Wireless Mic Follow Up: Turns Out Public Safety Did Get There First

, , , , , , , , , , , ,

One may logically ask, if I am right about the wireless microphones being such a big problem for public safety, why haven’t the public safety folks complained to the FCC about this?

Answer: turns out they have. But, the public safety folks being quiet and unassuming, failed to make themselves heard.

Allow me to change that. The National Public Safety Telecommunications Council, a federation of public safety associations, sent a letter to Chairman Martin asking that the FCC address the problem of wireless microphones back on June 30, 2008. i.e., about two weeks before I filed. While I wish I could claim that it was the NPSTC letter that inspired me, I had no idea it was out there until today. My conversations with the public safety guys were all informal and off the record. Still, as always when folks remind me I’m not an engineer (or an economist, or technologist, or any of the other topics on which I chose to share my humble layperson’s opinion), I am rather pleased to find a bunch of actual engineers that agree with me.

Mind you, the NPSTC letter asks the FCC to go a heck of a lot further than I have. NPSTC wants wireless microphones kicked out of the entire 700 MHz band. I, OTOH, think lots of folks can productively use the broadcast white spaces. Still, I do feel compelled to point out that wireless microphones do not have nearly the level of intelligence/sophistication being discussed for interference avoidance for the white spaces devices at issue in 04-186. Perhaps we should require wireless microphones to rely on sensing as well, or require that they consult an online database for possible new users in the band, or require them to acknowledge some sort of “permissive beacon.” Perhaps public safety entities like NPSTC should administer the database or beacon, and we should require wireless microphone users to pay for these services.

I mean, after all, we wouldn’t want to let these devices run around loose, would we? Think of the terrible interference that might cause. Unless these devices can meet the same rigorous standards that Shure and others seek to impose on unlicensed devices in 04-186, I don’t see how we can ask NPSTC to abide by circumstances that they feel place our public safety at risk.

Stay tuned . . . .

We File Wireless Microphone Complaint: Shure Says Breaking Law Should Be OK If You Sound Good.

, , , , , , , ,

As regular readers will know, among my many wireless fixations are the use of the broadcast white spaces and the 700 MHz auction. So what happens when I get to combine the two together?

Answer: A 50 page complaint and Petition for Rulemaking, another 175 pages of evidence that Shure and other manufacturers have been marketing wireless microphones in violation of FCC rules, then using the victims of this deceptive marketing scam as “human shields” in the white spaces debate, and a possible road map toward solving the potential for massive interference with new public safety and wireless services operating on the returned UHF bands. As a side benefit, it also provides a route to authorization for the hundreds of thousands (if not millions) of illegal wireless microphones, finds a use for that leftover 5 MHZ band in the AWS-2/AWS-3 proceeding (waste not want not), and potentially changes the debate in the white spaces fight by getting the goddamn fact that the overwhelming majority of wireless microphones are (at the moment) used illegally out in the open so people can have a rational discussion about interference protection.

Oh yeah, and it will require the wireless microphone manufacturers to clean up the mess by exchanging the old, unauthorized equipment for new equipment that doesn’t work on Channels 52-69. I love a plan that only punishes the guilty rather than letting the wireless microphone guys reap yet another windfall by requiring the unauthorized users to pay for their own equipment replacement.

And what was Shure’s response to the complaint? According to the Associated Press, Shure did not deny breaking the law. Instead, they said: “today’s uses of wireless microphones provide a valuable and irreplaceable public good, regardless of the licensing scheme.”

Or, in other words, “yeah, we broke the law — but it doesn’t matter because we will use Broadway and churches as human shields if you try to go after us” (insert international gesture of respect performed with raised middle finger at FCC).

You can see the press release here, and get copies of our complaint/Petition here. (Links to the Exhibits are on the press page.) You can see a bit more analysis from yr hmbl obdn’t below….

Continue reading

Follow Up On Medical Devices: Smarter Devices And Smarter Policy, Not More Bandwidth

, , ,

So I’ve been following up more since initial post yesterday. As a general matter, I recommend interested readers start with this piece from the FDA’s website, followed by the FCC’s Office of Engineering and Technology (OET) FAQ on wireless medical telemetry devices and the digital transition. OET does not see this as likely to cause a big deal because there’s plenty of empty “white spaces” out there after the digital transition and users can adjust their devices as digital televisions come online.

Well, I hope they are right about that, although I’d feel a lot better if someone were responsible for actually keeping track of this and making sure that users get informed. Under the rules, there are notification requirements for when a station goes live with its digital signal so hospitals can make changes. That works as long as folks are paying attention, of course. In any event, in case OET is looking for more work (or someone on the Hill wants to step up), I would suggest that it would be awfully nice to know what the state of the industry is. But I suspect the right place to do that is really the FDA not the FCC, or perhaps the U.S. Department of Health and Human Services.

But there is a broader lesson here. As with wireless microphones and a host of other specific low power applications, the real problem is not capacity. The problem is that we have a legacy system that slices spectrum uses into these discrete little services rather than allowing general low power unlicensed use and using cognitive radios to avoid interference.

Hospitals provide a particularly useful environment for smart devices, because they have so many noisy devices, sensitive devices, and such an expanding need for wireless devices for medical telemetry. Imagine a device that works equally well in all locations of the hospital without putting other systems at risk because it senses and adjusts for its radio frequency environment in a real-time basis. If another doctor starts up a device in a neighboring bed that is noise generator, the device monitoring my patient will move to a clear frequency. Devices and systems could even be tagged for priority, so that a mobile monitor attached to a patient knows that it must give the “right of way” to the cardiac ward systems if they come into conflict.

But more specifically here, there is nothing that existing wireless medical telemetry devices authorized in the band do that could not be replicated more flexibly and at lower cost by authorizing generic low-power white spaces devices. This is essentially the same problem as with wireless microphones. If wireless microphones had never received a special dispensation to function in the broadcast white spaces as a licensed ancillary service, you could replicate these systems with unlicensed white spaces devices. But, like the QWERTY typewriter, they are an embedded technology. And they have a constituency that, quite logically, resists change and argues that it plays an important role that generic devices could not replicate.

We thus have the irony of everybody agreeing there is “plenty of white space” for existing secondary users like wireless microphones and medical telemetry, but supposedly no room for the next generation of devices that could do the job of both technologies and bring us a host of other applications besides. We could cure this with more powerful cognitive radios, but the same natural conservatism by incumbents against any intrusion in “their” spectrum makes any movement in that direction politically difficult (as demonstrated by the FCC terminating two promising proceedings last year).

We therefore have the classic political and collective action result of fixing the wrong problem, at least from a public policy perspective. Rather than expanding wireless use generally, we make the new, more useful generic technology subordinate to the existing stakeholders. It is rather like what would have happened if harness makers and farriers had been able to demand that automobiles must protect their industries before being allowed to share the road with the horse and buggy.

Hardly a new problem or an original observation, I recognize. This has been the lament of spectrum reformers since five minutes after the first licenses were issued and the rest of us got cut off. Still, I keep hoping that this time around we’ll manage to get the right result and not let the embedded old technology trump the next generation of users.

Stay tuned . . . .

Paging Hospital Techies: You Have Bigger Worries Than White Spaces

, , , , ,

CNET has this story about how “Hospital Techies” (notably medical monitor manufacturer GE) are worried that white spaces devices will mess up their medical systems.

Bluntly, “hospital techies” have bigger problems. As the CNET article observes, but lightly passes over, some unknown number of hospitals are using legacy medical monitoring equipment that will stop working after the digital transition. So while the odds of white spaces devices (WSDs) interfering with actual medical equipment on the approved set aside, Channel 37, approaches zero, and WSD interference with legacy equipment is equally unlikely, we may face a total meltdown in poor hospitals of medical monitoring equipment.

Rather than waste time on white spaces, I would say manufacturers like GE Healthcare need to start working with the FCC (and Congress) to engage in a massive education and outreach effort equal to what the FCC has done with the NAB and retailers to educate the public. That means stop selling any legacy equipment, require manufacturers to notify customers that have legacy equipment that it may stop working, and find out how many hospitals are likely to lose medical monitoring equipment after the DTV transition happens. A little funding from Congress to help poor hospitals that can’t afford to upgrade wouldn’t hurt either.

But worrying about white spaces is like worrying about whether a candle will blow over when a brush fire is bearing down you. Unless folks wake up to the danger, we may get seriously burned.

More analysis below . . .

Continue reading

American Radio Relay League v. FCC, Why A Good Case Will Bring Confusion And Bad Results

, , , , , ,

I should be overjoyed with the D.C. Circuit’s latest case: American Radio Relay League v. FCC. First, it affirms the right of the Commission to balance between unlicensed Part 15 users and licensed users, even where operation of Part 15 certified devices/services will cause occasional interference to traditional Sec. 301 licensees. Second, it requires the FCC to publish staff reports on which it relies in their entirety, rather than merely including in the record the parts with which it agrees. Third, it requires the FCC to address proposals by commenters with something more substantive than “well, we’ve always done it this way, so we see no need to change.”

All good news, yes? As a legal matter, absolutely. But as a practical matter, I expect it to slow down movement on the FCC’s white spaces proceeding. Why? Because it was a reversal and a reversal almost always causes the good folks in the Office of Engineering and Technology to go into paralysis for a few months while they try to figure out what the new legal standard is now. That the court actually affirmed the critical part on respecting the FCC’s balance between Part 15 and traditionally licensed services is likely to get lost in the noise — especially as we can expect NAB and other white spaces opponents to dwell on the reversal aspect and ignore what the court actually said. And, in the short term, OET now has to figure out how to issue a report on the WSD testing that conforms to the D.C. Circuit’s standard of disclosure. While I, lawyer and advocate that I am, consider this simply an exercise in “tell the truth and shame the devil,” we can expect that opponents will press their own reading of the case and that OET (and FCC’s Office of General Counsel) will now have the difficult and potentially time consuming task of deciding on the proper interpretation.

So a good case in fact, but more delays while the agency digests its implications.

More below . . . .

Continue reading

White Spaces and the CTIA Game Changer

, , , , , , , , , , , ,

The idea of auctioning the broadcast white spaces, rather than opening them for unlicensed use, is not new. It started out as an NAB “poison pill” back in 2005, when we looked like we might be making progress on getting a pro-white spaces amendment in the DTV transition bill that ultimately became the Digital Tranisition Act of 2005. When the FCC reinvigorated the proceeding in 2006, the NAB managed to get the FCC to put the question of licensed v. unlicensed in the Further Notice. But the NAB doesn’t want any neighbors, either licensed or unlicensed, and has focused its efforts until now on trying to kill the whole idea rather than on trying to promote licensing and auctions rather than unlicensed.

But the idea of licensing the white spaces for cellular or backhaul has gained new life recently, particularly after the 700 MHz auction. Both Verizon’s Steven Zipperstein and analyst Coleman Bazelon recommended this in their testimony at the House Telecom Subcommitte hearing on the 700 MHz auction. That comes on top of a serious filing by CTIA on the benefits of auctioning some of the white space and leaving a smidge so that unlicensed technologies can continue to develop.

We’ve now gone from NAB poison pill to serious issue. The proposal has not yet gained traction, but it does not do to underestimate CTIA and its members because, particularly after the 700 MHz auction, a number of its members really need that spectrum. This has the potential to change the game radically, including shifting alliances as the threat becomes more credible.

Analysis below….

Continue reading

A Fatal Exception Has Occured In Your White Spaces Sensing Device

, , , , , , , , , , ,

It would be funny were it not so easy for NAB to exploit.

The Microsoft prototype shut itself down last week and would not restart. Users familiar with MS products that are scheduled for release, never mind pre-beta versions, will find this so unremarkable as to wonder at the sensation. It goes up there with “Apple denies latest i-rumor.”

Unsurprisingly however, the folks opposed to the use of white spaces (primarily the broadcasters and the wireless microphone folks, with a dash of the cable folks thrown in for good measure), will spin this as the entire technology for sensing if a channel is occupied as “failing.” This ignores the other prototypes of course (Phillips and Google), and ignores the fact that the failure had nothing to do with the sensing (the thing being tested). Finally, of course, it ignores the fact that this is a proof of concept prototype.

The fact is, that the FCC testing shows that “sensing” as a technology works at levels that easily detect operating television channels and even wireless microphones. In fact, it is too bloody sensitive. In a foolish effort to appease the unappeasable, the companies submitting prototypes keep pushing the level of sensitivity to the point where the biggest problem in recent rounds appears to be “false positives.” i.e., it is treating adjacent channels as “occupied.”

As a proof of concept, that should be a success. The testing demonstrates that you can detect signals well below the threshold needed to protect existing licensees. Logically, the next step would be to determine the appropriate level of sensitivity to accurately protect services, set rules, and move on to actual device certification based on a description of a real device.

But that is not how it works in NAB-spin land. Instead, NAB keeps moving the bar and inventing all sorts of new tests for the devices to “fail.” For example, the initial Public Notice called for prototypes for “laboratory testing.” MS and Phillips submitted prototypes that performed 100% in the lab. But then, the MS people did something very foolish, but very typical — they decided their laboratory device was good enough for field testing. No surprise, it did not work as well in the field as in the lab. As this was a laboratory prototype, the failure to perform flawlessly in the field should have been a shrug — it would have been astounding beyond belief if a prototype designed for the lab had worked perfectly the first time in the field. But the fact that the prototype did not work in the field was widely declared a “failure” by NAB, which unsurprisingly gave itself lots of free advertising time to spin the results this way.

So the FCC went to round two, and again the NAB and white spaces opponents have managed to move the bar so they can again declare a “failure.” Back in 2004, when the FCC first proposed opening the white spaces to unlicensed use, it concluded that operation of white spaces devices would not interfere with licensed wireless microphone users. The FCC has never reversed that determination. Unsurprisingly, businesses developing prototypes according to the FCC’s proposed rules have not taken particular care to address wireless microphones. Because the FCC explicitly said “don’t worry about them.”

But suddenly, if the devices can’t accurately sense and detect wireless microphones, they will be “failures.” It doesn’t matter that the devices have proven they can protect wireless microphones. It doesn’t matter that Google has proposed additional ways of protecting wireless microphones besides sensing. As long as NAB can frame what defines “failure” (rest assured, there will never be any successes of NAB gets to call the tune), and can keep changing that definition at will, the political environment will ensure that the actual engineering is irrelevant.

Which is why the companies need to stop trying to placate the NAB by agreeing to an endless series of tests with ever-shifting criteria. And OET needs to write up a report that does what the initial notices promised to do, use the data collected from prototypes to determine if the concept works and, if so, to set appropriate technical standards. The prototypes have proven they can detect signals with a sensitivity better than an actual digital television set or wireless microphone receiver, so the “proof of concept” aspect stands proven. Rather than buy NAB spin, the next step should be to determine what level of sensitivity to set as the standard.

Hopefully, the Office of Engineering and Technology, which is conducting the tests, will not suffer the fate of the Microsoft prototype and shut down under pressure.

Stay tuned . . . .

“The Spring Spectrum Shotgun Wedding Fling” or “Sprint WiMax, the Wily Temptress!”

, , , , ,

Was it really only last August that Sprint threw over its cable allies by filing for a messy divorce with Spectrm Co. and ran off giggling with Clearwire and Google for a happy WiMax menage? Ah, what a tempestuous summer of spectrum love was 2007! So full of bright promises and prospects for a wireless third pipe that could genuinely compete with cable or DSL speeds. But with the autumn frost, passions cooled. Like Fantine from Les Miserables, Sprint soon found itself abandoned by its spectrum partners and out on the street on its own — desperately trying to make its way in the cold and uncaring world while posting a loss of $30 Billion, and reduced to chanting the old Israeli spectrum folksong Xhom golly, golly, golly, Xhom golly, golly.

But a possible happy ending for Sprint awaits below . . . .

Continue reading

700 MHz Aftermath: Verizon, AT&T & the $16 Billion Termites.

, , , , , , , , , ,

Imagine you just spent a fortune on some excellent beachfront property, only to discover some termites in the basement. Now imagine that the only way to get rid of the termites involves some toxic chemicals that may arouse the ire of the environmentally conscious locals. What do you do? Learn to live with the termites, or spray and tell your green neighbors to deal?

Oddly, Verizon and AT&T now find themselves in a similar mess — if we substitute “wireless microphones” for “termites.” Verizon and AT&T (As well as a bunch of other folks) just spent a boatload of cash on licenses in the reclaimed analog television spectrum. The FCC has rules in place to migrate the broadcasters — both full power and low power. But — as far as I can tell — no one has plans to migrate the wireless microphone folks, who operate on vacant channels in the band. While in theory wireless microphones are a secondary licensed service and notifying the licensees that channels 52-69 are off limits after the digital conversion, the situation is a little more complicated. As comments filed in white spaces proceeding confirm, wireless microphones are bloody everywhere — with huge numbers of users buying and operating them without licenses.

The NAB and the FCC have turned a blind eye to proliferation of unlicensed wireless microphone use (despite the NAB’s usually firm stand against unauthorized use of “their” spectrum), both because the wireless microphones don’t actually cause any interference with television and because the “unauthorized wireless microphone user community” (which sounds so much better than “pirates”) includes megachurches, Broadway groups, and other warm cuddly folks able to gather political support. Indeed, so great is the political protectzia for the unauthorized wireless microphone user community that the FCC is, apparently, requiring that unlicensed devices in the white spaces have the ability to sense and protect these illegal wireless microphone users. (Hence Google’s recent extension of an olive branch which NAB promptly grabbed and started thwaking Google over the head. D’oh!)

AT&T, Verizon, and the rest of the 700 MHZ auction winners therefore face a bit of a dilemma. They just dropped a bundle on the 700 MHZ, and damned if they want to set precedent by allowing a bunch of illegal squatters to use “their” spectrum. Heck, if they’d thought of it earlier, they’d probably have initiated a rulemaking to migrate the legal users.

In fact, under a fair reading of the rules, if the FCC does nothing, licensed wireless microphone systems may enjoy equal or superior rights to 700 MHz Auction winners. OTOH, no one involved is stupid about the politics, giving an incentive to maintain a low profile. If you don’t mind telling shareholders that the NFL may have superior rights in the spectrum you just paid $16 Billion for.

Meanwhile, for those of us happy to see the NAB and the wireless microphone folks get their comeuppance, while not weeping overmuch for the incumbent wireless winners, one word: SCHWEET.

More below . . . .

Continue reading

Google Makes A White Spaces Concession.

, , , , , , , , , ,

In yet another chapter of “Why Citizens Movements Are Citizen Driven,” I think Google has conceded too much too soon in its letter today to the FCC. Briefly, in an effort to try to head off the persistent claims that the white spaces prototypes have “failed” and to move out of the wireless microphone trap that opponents of white spaces have used so effectively, Google proposes a combination of “beaconing” (give users of wireless microphones a low power gadget that mimics a dtv signal, thus denying use of the vacant channel to any white spaces device (WSD) in the immediate vicinity, as the WSD will interpret the channel as “active”) combined with setting aside channels 36-38 for wireless microphones, and requiring geolocation and a “permission to activate” signal from higher power stationary devices.

For reasons discussed below, I am not happy . . .

Continue reading