Google Shakes Up The Phone System

An FCC letter shows why new phone services like Google Voice must soon trigger a regulatory overhaul.

An innocuous-looking letter from the FCC to Google marks the beginning of the end of the telephone system we have known for the past 130 years.

The old phone system, the one started by A.G. Bell and still in use today, has a dedicated connection between each pair of people talking to each other. Whether plugged in by a switchboard operator, in the early days, or dialed by the user, later on, whether carried by copper wire, microwave radio, satellite signal, or fiber-optic cable, every individual phone conversation has its own separate circuit which is (a) set up for just that one call and (b) taken down when the parties hang up. This is called a “circuit-switched” system.

The FCC has regulated this set-up since 1935. The details evolved over the decades. But the FCC rules, then and now, have always been geared specifically to a circuit-switched system.

One element of these rules recently became controversial. When you place a long-distance call to your Aunt Mildred in Boston, say, you pay the long-distance carrier, and it in turn pays the Boston phone company to accept the call and ring Aunt Mildred’s phone. In telephone-speak, the money changing hands is called an access charge for terminating the call. It is an important source of revenue for local phone companies. If Mildred lives in rural South Succotash, the access charges are higher, because it costs more to run a phone system where the customers are farther apart.

The differences in access charges present an opportunity for abuse. Some companies that generate a lot of inbound long-distance traffic, like conference-call bridges and sex-call services, deliberately locate in rural areas. The incoming calls then generate high access-charge revenues for the local phone company, which may split the take with the conference-call or sex-call provider. The practice is called traffic pumping. For now, at least, it is legal.

The Digital Revolution

Flash forward to the future.  All phone calls are digital. The telephone handset converts the voice signal to a series of 0s and 1s, compresses the bit stream, separates it into “packets,” and gives each packet an address corresponding to the phone at the other end of the call. Traveling through the Internet, re-routed on the fly, the phone-call packets share the wires with packets carrying other people’s phone calls, video, web pages, baby photos, and everything else we send to each other. Among the different “protocols” for setting up and addressing packets, the ones used on the Internet are collectively called “Internet protocol” or IP. The term VoIP refers to the combined technologies for carrying voice over IP – that is, over the Internet.

Most home and office phones are still tied to circuit-switched local telephone systems. But companies like Skype and Vonage offer VoIP service to end users. People who receive their telephone service through a cable company or FIOS also use VoIP, although that fact is often buried deep in the service agreement.

VoIP has important advantages over the circuit-switched phone system. Because voice packets make up only a tiny fraction of the data carried on the Internet, transport is cheap. Calls within the U.S. are usually free; calls to other countries cost just a few cents per minute. Phone numbers need not be tied to location, so a subscriber in Sydney, Australia can have a local New York City phone number, which further lowers costs for calling friends in New York (although a careless pizza order can be expensive).

In contrast to its historically tight regulation of the circuit-switched phone system, the FCC takes a mostly hands-off approach to data services. Its Computer II decision of 1976, well before the public Internet emerged, kept full common carrier regulation over phone lines, even if they also carry data, but forbore from regulating the data. The Internet is squarely in the data category; and true to its word, the FCC left the Internet alone. As broadband emerged, the FCC largely deregulated the facilities that carry it, which left only voice lines under traditional regulation.

The voice vs. data distinction worked well for thirty years. But then came VoIP, which straddles both categories. Early VoIP drew little attention from regulators, being just another novel Internet application that needed special equipment and skills. But the technology soon moved beyond the hobbyists and into the mainstream. A subscriber could place and receive calls using what looked like an ordinary phone, yet bypass most of the phone system. Passing the ultimate test for ease of use, VoIP became popular with many elderly people as an inexpensive way of keeping in touch with far-flung family members.

The FCC, which dislikes ontological questions, had to make a decision: Is VoIP a voice service or non-regulated data service? It depends, was the answer. VoIP that meets the “quacks-like-a-duck” test – that functions as a full substitute for traditional voice service, phone number and all – became subject to many of the same rules as traditional voice: 911 call location, access by disabled users, law enforcement wiretaps, privacy rules, and universal service payments. Yet even quacks-like-a-duck VoIP remains exempt from most common carrier regulation.

The result is two phone systems operating side by side. The old one is ubiquitous and regulated. The new one is used only by some people, though more every day, and is mostly outside FCC regulation. The two interconnect to the extent that VoIP users can place and receive calls to and from ordinary phones. But not to and from everywhere – a point that has now caught the attention of the FCC, and could portend major changes in phone service.

Google Voice Muddies the Waters

VoIP can do a lot more than just emulate a circuit-switched phone. A service called Google Voice shows some of the possibilities. We described GV in an earlier post: A subscriber receives a new phone number, local in a region of the subscriber’s choosing.  Calling that number rings all the customer’s phones, wherever they are:  office, home, cell, etc.  Different callers can be automatically routed to different phones, or forwarded selectively to still other phones, or fed different voice mail greetings, or given different rings, or blocked altogether.  All the voice mails from all the phones end up in one place, where they can be read in printed form, like emails, or listened to online from anywhere. There are provisions for setting up conference calls, and for recording phone conversations for online storage. And all of this is free.

Except for the final connection to a dialed or forwarded number, the whole thing runs over the Internet.

But although the Internet goes everywhere, Google Voice does not. Complaints from many quarters allege that GV refuses to place or forward calls to certain rural areas. Google has said why: it wants to avoid paying high access charges. Of course, a GV subscriber whose Aunt Mildred lives in South Succotash still has the option of reaching her with an ordinary call over the old system. But GV’s form of discrimination, if true, raises one of those awkward definitional problems that so trouble the FCC. A common carrier is not allowed to pick and choose among call destinations. It must connect wherever the customer dials. A non-common-carrier is not subject to that obligation.

In response to the complaints, the FCC sent a letter to Google that asks two kinds of questions. First is whether and how Google Voice restricts calls to certain phone numbers or groups of numbers. Translation: do you discriminate? Second and third are whether GV charges end users for its services (no), and whether use of GV is by invitation only, as Google claims (yes, although anyone can request an invitation.)

Why do those last two questions matter? The law defines a common carrier service as one that is (1) offered for a fee (2) directly to the public, or to enough people that they effectively constitute the public. If the FCC finds the GV service is “for a fee” and offered to the public (or most of it), then GV is a common carrier service and must connect to anywhere. But that is not a likely outcome. Google no doubt will make a case that the service is truly free of charge, and truly limited in availability. The FCC would then have to agree it is not a common carrier service. The non-discrimination rules would not apply, and GV could decline those South Succotash calls with impunity.

Rewriting the Rules

The problem is, if we care about the future of the phone system, then none of Google’s possible answers yields a good result. The incongruity of shoehorning an IP service into circuit-switched regulation suggests that technology may have outpaced the rules.

Suppose the FCC, against all odds, decides that GV is a common carrier service. It must then require GV to provide rural connections and pay rural access charges. Google’s business model collapses and, with it, any incentive to continue offering the service. The public loses out. 

On the other hand, if GV is held not to be common carriage, then companies like Google can skim off the cheap, easy-to-provide services, and leave the more expensive ones, like rural voice calls, to the traditional regulated phone companies. As urban and suburban customers abandon their old phone service for cheap VoIP, the regulated companies’ revenues will fall. Some of their costs, like system maintenance and universal service fees, will become an increasing percentage of revenues. Local phone rates will climb, driving more users to VoIP alternatives, in a self-reinforcing spiral. That is also a poor outcome.

Unfortunately, the only lasting solution entails an overhaul of the Communications Act. When we last did that, in 1996, it was not fun for anyone, and we’re sure not looking forward to it now. But with the engineers having gotten out ahead of the lawyers, the lawyers have little choice but to catch up.

The rough outlines of a reform are easy to foresee. In the past, Congress and the FCC have eased regulation of services that became subject to competition. In the long-distance market, for example, the AT&T divesture of 1984 and a pro-competitive FCC created dozens of players. (We know exactly how many, because they all used to phone us at dinnertime.) Cell phone service has always been at least minimally competitive, and has never been subject to traditional telephone regulation.

Sooner or later, Congress will have to find that IP-based services like cable-provided VoIP, Skype, and Google Voice are giving local phone companies enough competition to justify some easing of traditional regulation. Rates, including access charges, will become more responsive to market forces. That will make traffic pumping less profitable, but will also give companies like Google Voice less expensive access to more areas of the country. Traditional phone companies will also benefit, in some respects, as they will find it easier to offer innovative services of their own.

But across-the-board deregulation will not do the trick. We still need a “carrier of last resort” to serve the always-expensive rural customers. We still need ways to subsidize service to high-cost areas and low-income subscribers, and to assist hearing- and speech-impaired users. The states, too, have a large role in regulating local telephone service, and may rank various outcomes differently. A largely rural state with a widely-dispersed population may have priorities at odds with those of a more urban state having dense concentrations of sophisticated users.

In short, VoIP and its spin-offs promise better, more flexible, and less expensive phone service. For the time being, though, these benefits will not reach everyone. Circuit-switching, although technologically obsolete, is everywhere, and will remain part of the telephone system for decades to come. The goal is a regulatory system that lets each deliver what it does best, keeping the enormous efficiencies and flexibilities of VoIP without sacrificing the ubiquity of the circuit-switched system.

Getting all the moving parts to mesh correctly will be an enormous undertaking. But we think the tone of the FCC’s letter to Google signals an awareness that the present regulatory scheme will not hold up. Inequities and discrepancies of the kind now presented by Google Voice will only get worse. Occasional patches might keep the current regime working a little longer, but an overhaul is coming due.

The FCC’s letter may be the first important regulatory step in that process.

AT&T Allows VoIP On iPhone Subscribers' Broadband Channels

Abrupt reversal precedes FCC announcement of network neutrality proposals

Here is one of those little coincidences that make Washington such an interesting place to work.

Regular readers know about the friction among Apple, maker of the iPhone; AT&T, the iPhone’s broadband provider; and Google Voice, a VoIP service (among other things) that seeks to carry the calls of iPhone users.

The iPhone and its close competitors, like the Palm Pre, have two ways to access broadband: a “3G” channel provided by the carrier and paid for as part of the subscriber’s data plan; and Wi-Fi, much like that in a laptop, which of course works only at Wi-Fi-equipped locations. Apple has long allowed VoIP on the iPhone's Wi-Fi link, but never on the 3G channel. This matters to users, because relatively few of the locations where a person might want to place or receive a call have Wi-Fi service. AT&T, in responding to an FCC inquiry, was blunt about why it (and Apple) block VoIP from 3G: VoIP is a much cheaper substitute for minutes of voice service. Its use thus cuts into carrier revenues, including the revenues needed to recover the subsidy that lets Apple price the iPhone at far below its actual cost. Read more here.

But now AT&T has abruptly reversed course.

It will allow VoIP on the iPhone 3G channel after all. If you hear loud cheers from the general direction of Mountain View, CA, that’s the Google folks breaking out the Red Bull. Apple still has not formally approved the Google Voice app, but a big obstacle is now out of the way.

The coincidence? Exactly one day before AT&T’s about face, the FCC announced the date, two weeks from now, on which it will formally propose its network neutrality rules. One of the key factors that precipitated the current surge of interest in network neutrality was a 2007 request from Skype, a VoIP company, asking the FCC to prohibit wireless companies (like AT&T) from blocking VoIP service. So the rules that might eventually be adopted, a year or two from now, may require action along the lines that AT&T took today.

Down here in the bunker we are a little surprised at the news. The wireless carriers have been erecting a protective wall of press releases that say network neutrality rules will bring about the end of technical innovation, social progress, and cheap cell phones. And AT&T’s decision may fundamentally change the economics of wireless phone service. We can expect vigorous marketing of VoIP services to iPhone users. That will probably cause a significant drop in paid-for voice minutes. Will AT&T start charging more for its data plan? Will Apple abandon the subsidy on the iPhone and start charging customers what the phone actually costs? AT&T may have brought us a little closer to a system in which customers have free choice and pay only for what they choose.

Sometimes the FCC can get the results it wants without actually regulating. Sometimes just announcing the date on which it plans to begin to consider regulating is enough.

Apple to FCC: "No Answer" Doesn't Mean "No"

Apple, AT&T answer FCC inquiry about rejection of Google Voice

We reported here on the FCC’s requests to Apple and AT&T, the iPhone maker and service provider, asking why Apple had rejected an iPhone App called Google Voice. This provides access to a range of advanced voice features free of charge, in some instances bypassing services that AT&T charges for. The FCC also wanted to hear Google’s side of the story.

The answers came in several days ago, and we have been mulling them over ever since. (Okay, we did some of our mulling at the beach.)

Apple has not actually rejected Google Voice, it says. But neither has it accepted Google Voice. Rather, Apple continues to study the application.

Over 95% of applications are approved within 14 days of submission, so this one must fall in the other five percent. Most non-approvals occur because the program crashes or fails to function properly, according to Apple, but somehow we doubt Google submitted buggy code. Other submissions are rejected for sexual or violent content, also not a factor here. Apple’s problem with Google Voice, rather, is that the application “appears to alter the iPhone’s distinctive user experience” by, for example, handling voice mail and contact lists differently.

While it makes up its mind, Apple generously invites Google to put the application on other, non-iPhone platforms “and let consumers make their choices.” Apple apparently misses the irony. If it truly favored consumer freedom, it would let customers include Google Voice in their choice of user experiences on the iPhone.

AT&T, for its part, claims no involvement in Apple’s decision (or failure to make one) regarding Google Voice. But AT&T is equally irony-challenged. Much of its response (a) touts the benefits of wireless competition, while (b) defending AT&T’s arguably anticompetitive policy of blocking VoIP services on its broadband network. The response is surprisingly frank about the rationale. VoIP users run up fewer minutes of voice service. AT&T needs the revenues from voice minutes to pay back the subsidy that lets consumers buy the iPhone at an artificially low price, which in turn has attracted many new customers to AT&T’s network (and billings for voice minutes).

Here’s an idea: a wireless network that offers its users maximum choice, and charges only for services actually selected and delivered. No limitations on handset applications; no handset “subsidies” recovered through excessive monthly charges. The wired phone system once had carrier-imposed equipment subsidies and service restrictions. Their removal by the FCC triggered the current telecommunications revolution and helped to produce the Internet. Maybe it’s time to try the same approach for wireless services as well.

Google’s response to the FCC on Google Voice might be interesting and helpful, but we will never know. Except for a glowing account of the advantages of Google Voice and Android, a Google-supported operating system for wireless phones, public copies of the response are heavily redacted, especially as to communications between Google and Apple about getting Google Voice approved. Again, the irony is hard to miss. Google has the legal right to redact information that it thinks might unfairly help its competitors. But as a company that has long championed openness on the Internet, it might have been more open with information that affects not only Google and Apple, but all of us interested in making the best use of communications resources.

FCC Examines Exclusion of Google Voice from iPhones

Letters sent to Apple, AT&T in expansion of “network neutrality” inquiry

The FCC recently expanded its “network neutrality” inquiries into an ongoing contretemps among three giants of consumer technology: Google, Apple, and AT&T. The dispute follows Apple’s disallowing Google Voice service on its iPhone handsets, possibly at the request of AT&T, the carrier having exclusive rights to the iPhone.

Network neutrality is the idea that communications customers, such as Internet and cell phone subscribers, should be able to use all lawful services and hardware without interference from the provider. It sounds simple enough, but in practice the issues get a little complicated. See here and here and here. Back in 2005, the FCC enunciated four “principles” of network neutrality, but has not adopted actual rules on the subject.

Wireless phone providers have traditionally favored the opposite of neutrality: a “closed” model in which the same company supplies over-the-air service, sells the handsets, and picks the services users can access. If you obtain cell phone service through one of the major carriers – Sprint, AT&T, Verizon, or T-Mobile – you probably bought your phone from them, too. And if you use the phone for on-line banking and certain other lucrative services, chances are the company you’re dealing with pays the carrier for the privilege of having your business.

The FCC has two proceedings underway that could eventually challenge this kind of arrangement.

One started with a petition from Skype, which provides free or inexpensive phone service over the Internet.  Most wireless carriers do not allow access to Skype over their handsets, because the customer could call via Skype instead of running up expensive minutes. The other proceeding began with a group of small rural cell companies asking the FCC to ban exclusive arrangements for handsets. Because such deals limit the most desirable handsets to the majors, the small carriers lose business to customers who want the latest in hardware. So far, though, the FCC has only invited public comment on these requests, with no hint as to whether it might act.

The newest wrinkle comes out of Apple’s decision against Google Voice.

Broadly speaking, Google Voice brings phone service into the Internet Age. A subscriber receives a new phone number, local in any region of the subscriber’s choosing. Calling that number rings all the customer’s phones, wherever they are: office, home, cell, etc. Different callers can be automatically routed to different phones, or forwarded selectively to still other phones, or fed different voice mail greetings, or given different rings, or blocked altogether. All the voice mails from all the phones end up in one place, where they can be read in printed form, like emails, or listened to online from anywhere. There are provisions for setting up conference calls, and for recording phone conversations for online storage. Parallel features cover SMS messaging.

And calling anywhere in the United States is free.

Apple rejected Google’s application to sell Google Voice through the App Store, the only legal source of iPhone software. And Apple revoked previous App Store approvals for third-party software intended to work with Google Voice. Early speculation supposed that Apple had acted at the request of AT&T, whose network uses the iPhone, but press reports say that AT&T has denied any involvement. Apple’s motivation for stirring up its customers remains unknown.

Now the FCC has sent letters to all three companies: Google, Apple, and AT&T, asking Apple and AT&T which one of them made the decision to bar Google Voice, and why, and whether Apple and AT&T offer competing applications. The letter to Google asks for details on how Google Voice works, and for a summary of the discussions with Apple and AT&T.

What the FCC will do with this information is not clear. Also not clear is whether it will even get the information. Or whether it has the authority to ask. Back in the 1976 Computer II proceeding, the FCC relinquished jurisdiction over information flowing through communications systems. It would regulate the lines, it then decided, but not the bits and bytes moving over them. (In the broadband environment, it has since deregulated even the lines.) With only limited exceptions for certain forms of VoIP , the FCC has indeed kept its hands off Internet applications. Apple and AT&T have to concede the FCC’s authority over wireless voice service, and may even acknowledge some control over handsets, but may well argue that Computer II put optional software applications beyond Commission reach.

For those of us who enjoy corporate conflict as a spectator sport – over-muscled, over-equipped gladiators struggling in the arena – the Google-Apple-AT&T spat is a welcome addition to the long-running Google-Microsoft and Apple-Microsoft events. “The enemy of my enemy is my friend,” the saying goes. But now the two biggest enemies of Microsoft have become enemies themselves.

Pass the popcorn, and keep your scorecard ready.