Skip to content
  • Stuff
  • Travel
  • Beverages
  • Support Antipaucity
  • Projects
  • About

antipaucity

fighting the lack of good ideas

lightsquared attacking gps manufacturers

Posted on 13 August 201113 August 2011 By antipaucity No Comments on lightsquared attacking gps manufacturers

The LightSquared situation keeps getting more interesting. InfoWorld has another story on them attacking GPS manufacturers for not being more careful about filtering adjacent frequency bands (per a DoD recommendation from 2008).

LightSquared is at loggerheads with makers and users of GPS (Global Positioning System) over interference between the navigation system and its planned cellular LTE (Long-Term Evolution) network. That network would transmit on frequencies close to those used for GPS. The company has long argued that makers of GPS equipment are to blame for the interference because they don’t use strong enough filters to keep their receivers from searching for signals in LightSquared’s bands. But this is the first time LightSquared has accused the vendors of flouting a specific rule.

The DoD’s GPS Standard Positioning Service Performance Standard called for GPS receivers to filter out transmissions on frequencies adjacent to the GPS band, LightSquared told the FCC in a filing related to the agency’s ongoing consideration of the company’s network proposal. The standard, issued in September 2008, recommends that receivers reject all transmissions on frequencies that are more than 4MHz outside the GPS band, said Jeffrey Carlisle, LightSquared’s executive vice president for regulatory affairs and public policy. That 4MHz buffer is essentially a “guard band” to protect operations on either side, he said.

LightSquared plans eventually to use frequencies adjacent to the GPS band for its LTE network, but after mandatory tests earlier this year showed strong interference in that area, the company said it would start out in a slightly lower-frequency block.

Here’s something that’s a little disturbing, though:

There is no mandatory standard for filtering in GPS receivers, and the FCC does not certify the devices for this

And here:

In addition to the DoD recommendation, the International Telecommunication Union, a United Nations agency, has also warned since 2000 that stronger filtering might be necessary to protect GPS from nearby transmissions

The ‘Coalition to Save Our GPS’ had the following to say:

“GPS receivers incorporate filters that reject transmissions in adjacent bands that are hundreds of millions of times more powerful than those of GPS. What LightSquared is proposing, however, is to transmit signals that are at least one billion times more powerful,” the group said in a statement. “There has never been, nor will there ever be, a filter that can block out signals in an immediately adjacent frequency band that are so much more powerful, nor has LightSquared put forward any credible, independent expert opinion or other evidence that this is possible.”

I’m no expert, but “hundreds of millions” is distinctly not far-off from “one billion” (since one billion is equal to ten hundred million). I also acknowledge not having much domain expertise in radio signals, transmission, etc – but what LightSquared is looking to do seems a lot more useful than worrying about some poorly-built GPS receivers.

The FCC said earlier this week that it would not allow the LTE service to launch unless the interference issue was resolved.

LightSquared has said it is confident the plan will be approved next month.

news, technical, update

Post navigation

Previous Post: light shows
Next Post: new connexions collection available

More Related Articles

cloud computing in easy steps by david crookes books
folding@home – ewok cabaret personal
above the cloud storage cool
haiku appliance cool
putting owncloud 8 on a subdomain instead of a subdirectory on centos 7 technical
updates to connexions modules news
August 2011
S M T W T F S
 123456
78910111213
14151617181920
21222324252627
28293031  
« Jul   Sep »
RSS Error: WP HTTP Error: cURL error 7: Failed to connect to paragraph.cf port 443 after 119 ms: Could not connect to server

Books

  • Debugging and Supporting Software Systems
  • Storage Series

External

  • Backblaze
  • Cirkul
  • Digital Ocean
  • Fundrise
  • Great Big Purple Sign
  • Password Generator
  • PayPal
  • Tech News Channel on Telegram
  • Vultr
  • Wish List

Other Blogs

  • Abiding in Hesed
  • Chris Agocs
  • Eric Hydrick
  • Jay Loden
  • Paragraph
  • skh:tec
  • Tech News Channel on Telegram
  • Veritas Equitas

Profiles

  • LinkedIn
  • Server Fault
  • Stack Overflow
  • Super User
  • Telegram
  • Twitter

Resume

  • LinkedIn
  • Resume (PDF)

Services

  • Datente
  • IP check
  • Password Generator
  • Tech News Channel on Telegram

Support

  • Backblaze
  • Built Bar
  • Cirkul
  • Digital Ocean
  • Donations
  • Fundrise
  • PayPal
  • Robinhood
  • Vultr
  • Wish List

35-questions 48laws adoption automation blog blogging books business career centos cloud community documentation email encryption facebook google history how-to hpsa ifttt linux money networking politics prediction proxy review scifi security social social-media splunk ssl startup storage sun-tzu tutorial twitter virtualization vmware wordpress work writing zombie

Copyright © 2025 antipaucity.

Powered by PressBook Green WordPress theme