As you may know, if you buy a cell phone today, you have to sign up for a 1 or 2 year contract, and you get a serious discount on the phone, often as much as $200. The stores that sell the phones get paid this subsidy when they sell to you, if you buy from a carrier you just get a discount. The subsidy phones are locked so you can't go and take them to another carrier, though typically you can get them unlocked for a modest fee either by the carrier or unlock shops.
Radio technology has advanced greatly in the last several years, and will advance more. When the FCC opened up the small "useless" band where microwave ovens operate to unlicenced use, it generated the greatest period of innovation in the history of radio. As my friend David Reed often points out, radio waves don't interfere with one another out in the ether. Interference only happens at a receiver, usually due to bad design. I'm going to steal several of David's ideas here and agree with him that a powerful agency founded on the idea that we absolutely must prevent interference is a bad idea.
My overly simple summary of a replacement regime is just this, "Don't be selfish." More broadly, this means, "don't use more spectrum than you need," both at the transmitting and receiving end. I think we could replace the FCC with a court that adjudicates problems of alleged interference. This special court would decide which party was being more selfish, and tell them to mend their ways. Unlike past regimes, the part 15 lesson suggests that sometimes it is the receiver who is being more spectrum selfish.
Here are some examples of using more spectrum than you need:
- Using radio when you could have readily used wires, particularly the internet. This includes mixed mode operations where you need radio at the endpoints, but could have used it just to reach wired nodes that did the long haul over wires.
- Using any more power than you need to reliably reach your receiver. Endpoints should talk back if they can, over wires or radio, so you know how much power you need to reach them.
- Using an omni antenna when you could have used a directional one.
- Using the wrong band -- for example using a band that bounces and goes long distance when you had only short-distance, line of sight needs.
- Using old technology -- for example not frequency hopping to share spectrum when you could have.
- Not being dynamic -- if two transmitters who can't otherwise avoid interfering exist, they should figure out how one of them will fairly switch to a different frequency (if hopping isn't enough.)
As noted, some of these rules apply to the receiver, not just the transmitter. If a receiver uses an omni antenna when they could be directional, they will lose a claim of interference unless the transmitter is also being very selfish. If a receiver isn't smart enough to frequency hop, or tell its transmitter what band or power to use, it could lose.
Since some noise is expected not just from smart transmitters, but from the real world and its ancient devices (microwave ovens included) receivers should be expected to tolerate a little interference. If they're hypersensitive to interference and don't have a good reason for it, it's their fault, not necessarily the source's.
Everybody's got old cell phones, which sit in closets. Why don't the wireless carriers let customers cheaply have two or more phones on the same line. That would mean that when a call came in, both phones would ring (and your landlines if you desire) and you could answer in either place. You could make calls from either phone, though not both at the same time.
It does get hard to be a privacy advocate when it's easy to think of interesting apps that make use of tracking infrastructure. Here's one.
How often have you wanted to talk to somebody in a car next to you on the road? Consider a system where people could register their licence plate(s) with their cell phone account. Then, if they had done this, you could call a special number on your own cell phone, and enter the numeric part of their licence plate.
People are always looking for location aware services for their mobile devices, including local info. But frankly the UIs on small mobile devices often are poor. When you are on a cell phone, voice to a smart person is the interface you often want.
So here's a possible location aware service. Let people register as a "local expert" for various coordinates. That's probably folks who live in a neighbourhood or know it very well. They would then, using a presence system on their own phone or computer, declare when they are available to take calls about that location.
Last week I wrote about how the 800 number you get on the web page should be special and understand your context and how frustrating it is to get an 800 number from the Contact-Us page on a web site and then be taken through a series of menus that are a waste of time for somebody who was just at the web site.
While the best thing to do is to get an eCRM system which connects the user with a session fully informed about what they were doing on the web, that's expensive. However, a few more thoughts have come to me.
When you call most companies today, you get a complex "IVR" (menu with speech or touch-tone commands.) In many cases the IVR offers you a variety of customer service functions which can be done far more easily on the web site. And indeed, the prompts usually tell you to visit the web site to do such things.
However, have we all not shouted, "I am already at your damned web site, I would not be calling you to do those things!"
As most people in the VoIP world know, the FCC mandated that "interconnected" VoIP providers must provide E911 (which means 911 calling with transmission of your location) service to their customers. It is not optional, they can't allow the customer to opt out to save money.
It sounds good on the surface, if there's a phone there you want to be able to reach emergency services with it.
The meaning of interconnected is still being debated. It was mostly aimed at the Vonages of the world. The current definition applies to service that has a phone-like device that can make and receive calls from the PSTN. Most people don't think it applies to PBX phones in homes and offices, though that's not explicit. It doesn't apply to the Skype client on your PC, one hopes, but it could very well apply if you have a more phone like device connecting to Skype, which offers Skype-in and Skype-out services on a pay per use basis and thus is interconnected with the PSTN.
Here's the kicker. There are a variety of companies which will provide E911 connectivity services for VoIP companies. This means you pay them and they will provide a means for you to route your user's calls to the right emergency public service access point, and pass along the address the user registered with the service. Seems like a fine business, but as far as I can tell, all these companies are charging by the customer per month, with fees between $1 and $2 per month.
This puts a lot of constraints on the pricing models of VoIP services. There's a lot of room for innovative business models that include offering limited or trial PSTN connection for free, or per-usage billing with no monthly fees. (All services I know of do the non-PSTN calling for free.) Or services that appear free but are supported by advertising or other means. You've seen that Skype decided to offer free PSTN services for all of 2006. AIM Phoneline offers a free number for incoming calls, as do many others.
Many universities are now setting up to broadcast lectures over their LANs, often in video. Many students simply watch from their rooms, or even watch later. There are many downsides to this (fewer show up in class) but the movement is growing.
Those who know about my phone startup Voxable will know I have far more ambitious goals regarding presence and telephony, but during my recent hospital stay, I thought of a simple subset idea that could make hospital phone systems much better for the patient, namely a way to easily specifiy whether it's a good time to call the patient or not. Something as simple as a toggle switch on the phone, or with standard phones, a couple of magic extensions they can dial to set whether it's good or not.
Since writing in the previous post about an end to all ringing of cellphones through the use of cheap bluetooth enabled vibrating devices in watches, belts, shoes and other wearables, I've been listening to the cacophany of rings in public meetings (even those were people are told to put their phone on vibrate.) One thing I am sure we've all experienced is hearing somebody's ring get louder and louder in a meeting as they fumble to get the phone and open it to press the silence button.
GPS receivers with bluetooth are growing in popularity, and it makes sense. I want my digital camera to have bluetooth as well so it can record where each picture is taken.
But as I was drivng from the airport last night, I realized that my cell phone has location awareness in it (for dialing 911 and location aware apps) and my laptop has bluetooth in it, and mapping software if connected to a GPS -- so why couldn't my cell phone be talking to my laptop to give it my location for the mapping software? Or ideed, why won't it tell a digital camera that info as well?
For some time in my talks on CALEA and VoIP I've pointed out that because the U.S. government is mandating a wiretap backdoor into all telephony equipment, the vendors putting in these backdoors to sell to the U.S. market, and then selling the same backdoors all over the world. Even if you trust the USGov not to run around randomly wiretapping people without warrants, since that would never happen, there are a lot of governments and phone companies in other countries who can't be trusted but whom we're enabling.
Tom Selleck narrates:
Have you ever arranged a wiretap in Las Vegas without leaving your office in Fort Meade?
Or listened in on a mother tucking in her baby from a phone booth, all without the bother of a warrant?
Or data mined the call records of millions of Americans with no oversight?
And the company that will bring it to you... AT&T
A big announcement today from those of us at the EFF regarding the NSA illegal wiretap scandal. We have filed a class-action lawsuit against AT&T because we have reason to believe they have provided the NSA and possibly other agencies with access to not only their lines but also their "Daytona" database, which contains the call and internet records of AT&T customers, and probably the customers of other carriers who outsource database services to Daytona.
Last week I spoke at O'Reilly's Emerging Telephony (ETEL) conference about CALEA and other telecom regulations that are coming to VoIP. CALEA is a law requiring telecom equipment to have digital wiretap hooks, so police (with a warrant, in theory) can come and request a user's audio streams. It's their attempt to bring alligator clips into the digital world.
Well, I am going to get a bluetooth cell phone shortly and so I got a headset and dongle to use on my laptop, where I also make VoIP calls.
I was shocked, flabbergasted to find that the bluetooth headset profile only transmits audio at telephone quality 8khz sampling rate. So even plugged into my laptop for hifi (didn't think I
would ever need to use that term again) recording, it sounds like a telephone, and likewise for
Why? Why? Why?
This week I will be doing some demos of Voxable, my system that combines VoIP, presence and all sorts of cool stuff I won't be writing about in the public blog to create a new user interface for the phone that is both as modern and internet as it can get while also being a reflection of the ancient interface for the phone that was lost.