SpectrumTalk has moved!

25th Anniversary of FCC Decision Enabling Wi-Fi and Bluetooth

25th Anniversary of FCC Decision Enabling Wi-Fi and Bluetooth
A series of posts describing how this all came about. (Click on picture above)
Showing posts with label Google. Show all posts
Showing posts with label Google. Show all posts

Wednesday, March 26, 2008



Google Flip-flops on White Space

Google filed a new letter at FCC on 3/21 changing its position on the Docket 04-186 TV white space proposal. After developing a listen-before-talk (LBT) detector, showing pictures of it, and leaving its antenna at the FCC Lab, they have decided to focus on the other two alternatives in the FCC's NPRM to avoid controversy. These alternatives were: geolocation (e.g. GPS) with database lookup and a local beacon to indicate what channels are available in a local area.

Google says,
"Under our own enhanced protection proposal, a TV white space device will not transmit on a channel until it first has received an "all clear" signal for that channel, either directly from a database of licensed transmitters in that area, or from a geo-located device with access to that database. That “permission to transmit” signal (at a maximum power level of 4W EIRP) would be sent on channels the geo-located device already knows are clear of licensed users. Any device without geo-location and database access would not transmit at all, unless and until it has successfully received advance permission from such a device."
If Google thinks this will make the controversy go away, I fear they are naive. While MSTV and NAB has focused on LBT as their main enemy, they have clearly dissed the other alternatives too: "The Notice’s Other Proposed Interference Prevention Techniques Would Be Ineffective" NAB and MSTV Reply Comments at p. 8

And even if the "immovable object" of the broadcasting community gives in to the "irresistible force" a little on the other two options, we then get into a question that has been lurking under the surface since the beginning of this rulemaking: where do you draw the line on the area where white space devices can operate?

MSTV has been cryptically talking about "protected contours" but has never defined that term or given a reference to any FCC rules that define it. In reality, FCC has defined the coverage area of TV stations in various ways for various purposes. Which definition would make MSTV happy? Remember MSTV has already said that there isn't any spectrum available for WSD use in major urban areas using their acceptable conditions. That says something about their thinking and is a hint of what will happen if Google and friends try to reach a negotiated understanding with MSTV.

NAB, however, has already blasted the Google letter/olive branch saying,
"We are pleased that Google now seems to realize that spectrum sensing alone won't protect viewers against interference from unlicensed devices. Unfortunately, simply adding geolocation and beacon sensing does not mean that mobile operation is suddenly feasible. Portable, mobile personal device operation in the same band as TV broadcasting continues to be a guaranteed recipe for producing interference and should not be allowed under any circumstances."
Google also hopes that they can make the wireless microphone problem go away also.
"Further, all TV white space devices would be blocked from transmitting by any wireless microphone beacon in that channel, using signals specifically designed to be easy to reliably detect, and coded to be identifiable to prevent abuse. These beacons should be quite inexpensive, and would be used in conjunction with existing wireless microphones, so there would be no need to replace legacy devices.

In addition, we are proposing a "safe harbor" for wireless microphones in channels 36-38. No TV white space device would be permitted to transmit in these channels. This will also protect medical telemetry devices and radio astronomy services, which are licensed to use channel 37."
Medical telemetry does indeed use "Channel 37" -- which is really a passive radio astronomy band. But this is an agreement FCC worked out, actually I was the one who proposed it, based on the fact that the medical telemetry equipment used is quite expensive, sold only to hospitals, and has a good history of compliance with licensed operation and rules. By contrast, the wireless microphone business is basically a "wild west" of spectrum squatters who are violating criminal laws in doing so and manufacturers who aid and abet this lawlessness. This is the group you want to share with medical telemetry and radio astronomy? Did anyone check if there is even enough capacity on channels 36-38 for broadway shows and live concerts with large numbers of microphones in major urban areas that may have TV stations on channels 35, 36, 38 and/or 39?

I suppose FCC would do anything to avoid making a decision here on spectrum policy and hopes that the Google position will be the basis of consensus. I suspect it will just introduce more controversy.

However, I hope that the ongoing FCC Lab tests will show that WSDs really do work with reasonable protection to the few (and ever decreasing) households that actually receive over-the-air television. As I wrote previously, the wireless mic problems should be addressed by more efficient wireless mic technology (not just ancient FM) and relocation to bands they can share with easier.

=============

Related post by Sascha Meinrath

Sunday, January 20, 2008












White Space Device Testing
to Start at FCC Lab



A January 17th FCC public notice announced the beginning of the next round of testing of prototype white space devices (WSDs) on January 24 at 10 AM and will continue "4 to 6 weeks". the testing will be "conducted openly and transparently" although few details were given about procedures in the published test plan.

The notice indicated that devices from Adaptrum, Microsoft, Motorola and Philips would be tested but was ambiguous about whether late entries would be allowed. Google is thought to have a device also so we will see if they show up and will be allowed to participate with others.

Other unanswered questions about the testing include: What is the last date, if any, that developers can change the software in their prototypes? When can the developers show FCC staff how to operate the devices? FCC staff has informally told developers what type of data they want from the devices during test, e.g. a comma separated variable (CSV) list of yes/no detections for 30 consecutive trials at a given power level. Have all developers been told the same set of requirements?

So the restaurant business near the FCC Lab should pick up for the next few weeks. Hope they plow the parking lot for the expected guests. See you there!

Friday, December 07, 2007


Google white space device prototype

Busy Week of White Space Action


It's been a busy week here in Washington, my home town. Down at the lab of our local communications commission there have been all sorts of visitors, like Magi at Xmas time, bearing gifts or promises of gifts. Fortunately, unlike the advocates of the status quo for large affluent TV broadcasters who skirt the Commission's ex parte rules with apparent impunity, these visitors believe in and act in the letter and spirit of transparency. Thus there is a paper trail where we can follow the action.

Actually, a little earlier on November 16 Motorola came by with the first recent present. Motorola described it as follows
"(It) uses geo-location database that is augmented by sensing algorithms to determine which TV White Space channels are available for use. The device also can be configured to perform testing of the DTV sensing algorithms but is not a normal operational mode of the device."
No pictures were included, but I saw the device at the Lab and it is rack mounted in an 18" high rack.

On December 4, Google dropped by.
(The) Google representatives demonstrated broadband spectrum sensing technologies that reliably detect DTV signals well below the noise floor. The broadband DTV sync signals gave reliable power level estimates, even when the pilot is deeply faded, removing the need for large margins. preliminary figures from the initial phase of the testing support an average sensitivity of -120 dBm.
The picture at the top of this post was included in their submission to FCC.

Then on December 5, Adaptrum, Inc , a client of mine, dropped by with its unit.


Dr. Haiyun Tang of Adaptrum and Steve Jones of FCC Laboratory with Adaptrum White Space Device (WSD) at delivery to FCC for testing,

Adaptrum said in its filing
The Adaptrum device is different from others that have been discussed on the public record in that it is not based frequency domain processing and threshold detection of DTV pilot tone power. Rather, it uses the whole 6 MHz of the DTV signal and contains a time domain matched filter. This greatly increased bandwidth permits greater sensitivity than pilot tone detectors.
Note that the Google and Adaptrum filings were made almost simultaneously and that both systems appear to use the same type of time domain processing.

Also on December 5, my former boss, Ed Thomas, met FCC downtown on behalf of both Microsoft and Philips. The filing says

During this meeting, Mr. Thomas made arrangements for Microsoft and Philips to submit devices to OET for the next round of white space prototype testing, and the parties discussed white space testing logistics, including potential dates for laboratory and field tests.
Are Microsoft and Philips now combining forces and working on a common device? The letter is ambiguous so we will see.

FCC staff reports that the "8th Floor" has now said that all submitted devices will be tested in parallel and publicly with observers from the interested public - please don't throw peanuts at the FCC staff. This apparently includes both bench tests and field tests. A problem appears to be how to find homes to test these in where an unlimited number of observers can wander in and out. Stay tuned.

Thursday, November 08, 2007





Google, Android and
47 CFR 2.944:

The Legacy of Myopic Rulemaking

This week Google announced Android and the Open Handset Alliance. Android is "a complete platform that will give mobile operators, handset manufacturers, and developers everything they need to build innovative devices, software and services." On November 6, 2007 Chairman Martin made the following statement:
I was pleased to hear the announcement by the Open Handset Alliance of the plans to introduce an open platform for mobile devices. As I noted when we adopted open network rules for our upcoming spectrum auction, I continue to believe that more openness—at the network, device, or application level—helps foster innovation and enhances consumers’ freedom and choice in purchasing wireless service.
So it looks like Android will have smooth sailing through FCC. But there is a problem there that got overlooked in everyone's enthusiasm: FCC has had 2 rulemakings on software defined radios (SDR) in recent years, Dockets 00-47 and 03-108. Both of these rulemakings dealt with a topic closely related to the Google announcement: how do you regulate transmitters that can change performance after approval with the addition of new software. Unfortunately, both rulemakings became "feel good" exercises to tell major industry forces FCC was supportive and both had decisions that were rushed to completion to "honor" the departing heads of OET. Not enough attention was paid to the long term implications of the specific rules that were adopted.

Let me make it clear, I think SDR is one of the greatest advancements in radio technology in recent history and along with its cousin, cognitive radio, has the promise to increase spectrum utilization and make new services available to the public. But if poorly regulated it could open Pandora's box to antisocial manufacturers who are not household names or members of major trade associations but are government by the same rules. Such manufacturers, often based in Asia, would love to get a competitive advantage on legitimate manufacturers by offering "features" such as increased power and more "frequency agility", e.g. use of improper bands such as public safety bands that have low average occupancy. In addition there is a growing interest in certain circles about selling various types of cellular jammers. CTIA is getting so annoyed about this that it have petitioned FCC for a declaratory ruling. While a "strict interpretation" of today's SDR rules would prevent the sale of transmitters that could be reprogrammed into being jammers, a "flexible" enough interpretation that is open enough to give Android a green light under existing rules probably facilitates new routes for legal sale of jammers even if CTIA gets the declaratory ruling it wants.

As a result of the 2 rulemakings SDRs are now defined in 47 CFR 2.1 as
A radio that includes a transmitter in which the operating parameters
of frequency range, modulation type or maximum output power
(either radiated or conducted), or the circumstances under
which the transmitter operates in accordance with Commission rules, can
be altered by making a change in software without making any changes to
hardware components that affect the radio frequency emissions
Then 47 CFR 2.944 gives these requirements
(a) Manufacturers must take steps to ensure that only software that has been approved with a software defined radio can be loaded into the radio. The software must not allow the user to operate the transmitter with operating frequencies, output power, modulation types or other radio frequency parameters outside those that were approved. Manufacturers may use means including, but not limited to the use of a private network that allows only authenticated users to download software, electronic signatures in software or coding in hardware that is decoded by software to verify that new software can be legally loaded into a device to meet these requirements and must describe the methods in their application for equipment authorization.

(b) Any radio in which the software is designed or expected to be modified by a party other than the manufacturer and would affect the operating parameters of frequency range, modulation type or maximum output power (either radiated or conducted), or the circumstances under which the transmitter operates in accordance with Commission rules, must comply with the requirements in paragraph (a) of this section and must be certified as a software defined radio.

(c) Applications for certification of software defined radios must include a high level operational description or flow diagram of the software that controls the radio frequency operating parameters.

Are any of these requirements in direct conflict with the Android "vision"? Probably not. But also sorts of understandings between the Android community and FCC will be needed, especially if Android becomes "open source". And since we are a "nation of laws, not a nation of men", these will then have to apply to all radio makers, not just the major firms with friends on the 8th floor. This is where there is a potential for chaos.

If I was back at FCC, I would start reviewing the SDR policy with respect to open source Android and try to come up with a supportive and clear policy structure that allows it but blocks sleazy manufacturers who seek to make antisocial transmitters capable of interfering with public safety and other key services.

If the Commission's Technological Advisory Council was really alive - not just a meaningless circular link on the FCC's cluttered home page - this would be a good task to give it. But the TAC seems to be on life support or dead since it hasn't met since 7/20/06 and its last scheduled meeting on 10/25/06 was mysteriously canceled 2 days before the meeting.

So I suspect that FCC will just give Google and Android a blank check to do whatever they want and will ignore the long term implications of the same rule interpretations in the hands of less ethical companies. But if FCC want to take the long term view, it should start thinking now about long term changes to the SDR rules that enable legitimate systems such as Android but block SDRs as a possible back door route to antisocial systems such as jammers.





Subscribe in a reader