Open Spectrum: Take It or Lose It
Over at ZDNet, Kevin Werbach suggests a cure for bandwidth blues that looks as subversive and fundamental as both the Internet and Linux. It's called Open Spectrum. Here's how he draws the big picture:
The concept is that wireless frequencies could be shared among many users rather than assigned in exclusive licenses to individual companies. Smart devices subject to rules ensuring that no one player could hog the airwaves would replace networks defined by governments and service providers. Spectrum would be used more efficiently. Bandwidth would be cheaper and more ubiquitous.
We have a taste of this already with WiFi, or 802.11b, which is how most of us connect wirelessly to the Net. But WiFi is just what we've squeezed out of the small wedge of spectrum. Already, Kevin reports, there are 10 million WiFi devices and 4,000 public wireless access points, and they're growing like weeds. You can walk down some streets in San Francisco with a wireless laptop and sense a dozen different base station signals. Some are wireless company intranets. Some are paid public access points (like MobileStar's, which are in many Starbucks cafes, and WayPort's, which are in many airports and hotels). Others are cooperatives serving the public or only their members. Those include NoCatNet (by some O'Reilly folks in Sonoma County, CA), Consume.net in London, SeattleWireless.net and SFLan in San Francisco. But let's face it, these are a few wireless drops in the wired Net's bucket. Geographically, the ratio ought to be the other way around.
To get what's possible here, you have to break loose from the idea that a wireless link has to be nailed down to a specific frequency, and that bandwidth will vary mostly with signal strength. Thanks to spread spectrum technology, many signals can share (or roam among) many frequencies using very low power signals in a given locality. They don't need to crowd each other out or step on each other. Here's how Kevin puts it:
... if the receivers are smart enough, many transmitters can send signals with low power over a wider range of bands and not interfere. The signals are split up into coded chunks that are reassembled on the other end, much as routers manage traffic on the Internet. Everyone in the room can talk at once, as long as they do so quietly. And if you listen carefully, you'll recognize the unique pitch of a friend's voice across the room despite the distance and the large number of simultaneous conversations.
And where would Linux come in? Lots of places, but especially where it gets embedded:
Using smart "software-defined" radios, nodes in unlicensed wireless networks could cooperate actively. Devices can act as repeaters for traffic between nodes. They could dynamically select power levels and coding schemes based on the behavior of other nodes. And they could cooperatively sample and adapt to background noise. Through these mechanisms, which could be encouraged through equipment certification rules, the spectrum would go from a fixed resource to one that expands with additional computing power and technical innovation. New users could actually increase the bandwidth available by contributing to the cooperative intelligence of the network.
So what's keeping us from making this happen? In a word, the Feds. We need enough spectrum to make it work. Toward that end, Kevin has written an Open Letter to the FCC on Spectrum Policy in which he makes a number of specific recommendations, including adoption of the "intelligent radio bill of rights" suggested by Bran Ferren, the former head of R&D for Disney Imagineering.
Kevin, by the way, is a former insider with the FCC, having served as Counsel for New Technology policy there. He also helped make the FCC hip to the Web in the first place, designing the agency's first web site. In law school at Harvard, Kevin was publishing editor of the Law Review (he says he actually enjoyed law school, which is maybe why he went into other work--like writing and pushing out the Net's envelope). These days he's busy driving the Open Spectrum cause as editor of Release 1.0, published by Esther Dyson's EDventure Holdings. Open Spectrum: The Paradise of the Commons is his lead piece in the current issue of the publication.
The big question for me isn't "Can we get behind this?" It's "What can we do?" and "What's being done already that we can support?"
I have a bad feeling about what will happen if we don't. One of Michael Powell's most-quoted lines since he became FCC chairman is "Openness is not always good." On the plus side, this issue isn't about open vs. closed. It's about public vs. private. All we're asking for is some open, public spectral space--just enough to do what we've already done with the Net.
Doc Searls is Senior Editor of Linux Journal.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Interview with Patrick Volkerding
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide