got net?

Kevin Hazzard's Brain Spigot

About the author

Welcome to Kevin Hazzard's blog.
E-mail me Send mail

Recent posts

Recent comments

Authors

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2010

Proprietary Networks for the iPhone and the G1

We've been loyal Verizon Wireless customers for many years. We were GTE Wireless customers back in the day before the name change. But my wife has been wanting an iPhone for many months. She's enamored with the tight integration of the applications and the hardware. She's also a Mac user for the same reason. She finds the huge variety of vendors and configuration options on the PC overwhelming. The Mac simplifies things by limiting the choices. I can understand how she feels. I've been doing Windows development on a MacBook Pro for a few months and I have to say that the OS X experience is comfortable to me now. I still love Windows but running it in a virtual machine on my Mac gives me the best of both worlds.

My wife's business is doing well so she decided to get an iPhone today and make it a pure business expense going forward. She's in love with her iPhone and I'm happy for her. But it irks me that she had to choose AT&T Wireless to be able to switch over to the platform she really wanted. Verizon Wireless has great customer service and their network coverage is just phenomenal. We live in the wilderness between Richmond and Charlottesville, Virginia and wireless Internet service is all we can get out here. Even in the boondocks Verizon's coverage is rock solid: five bars. AT&T Wireless's coverage is OK where we live but not nearly as strong. I like to reward those companies that earn my trust and respect by remaining loyal to them. Just tonight I was trying to solve an issue with an EVDO card that I purchased on EBay and the Verizon Wireless support team was nothing short of amazing in their response to help me. A few months ago something weird happened with the wireless tower near my home and the I got routed to engineers in Dallas who were diagnosing the problem live while I listened. Within an hour a Verizon Wireless truck was on the scene at the local tower. And when they had fixed the problem the engineers in Dallas called me back and had me test the fixes before the workers were allowed to leave the tower. I was simply blown away by the quality of the response. You just don't get that kind of customer service from most companies these days. So you can imagine that I'd have been much happier if we could have added my wife's iPhone to our Verizon Wireless account. AT&T Wireless's service and support may also be wonderful. But Verizon Wireless has earned my respect and I like to be loyal to their brand.

The same goes for Google's Android-based G1 phone operating only on the T-Mobile network. I'd love to try the G1 but the T-Mobile signal where I live is just awful. Until the G1 is available on a more functional network, it's just unavailable to me. Are we so primitive in our networking prowess in 2009 that we have to restrict devices to specific carrier networks? A TCP stack is a TCP stack, right? Building a TCP stack that can use EVDO or EDGE interchangeably shouldn't be a big deal. So is it just that by limiting the carrier choices Apple and Google can better drive consumers through the channels where they can exert more control over features and configuration? The latter is the real driver behind the limitations, I'm sure. Apple is the master of limiting choices to limit complexity after all. I'm also sure that by single sourcing a device as sexy as the iPhone through one carrier, Apple has sweetened it's margins nicely, too.

I shouldn't be complaining, I suppose. I'm all for the freedom of businesses to make the choices that make them as successful as they can be. If it helps AT&T Wireless's, Apple's, T-Mobile's and Google's bottom lines to be proprietary then I honor their proprietary-ness. But consumers like me also place a high value on choice, too. I'm looking forward to the day when any computing or telephony device purchased anywhere in the world will work on any network, anywhere in the world. One network for all. Is my dream fallacious? Perhaps. What's your techno dream?


Categories: Rant
Posted by kevin on Saturday, January 24, 2009 6:02 PM
Permalink | Comments (7) | Post RSSRSS comment feed

Comments

Jonathan Pryor United States

Saturday, January 24, 2009 8:30 PM

Jonathan Pryor

1. Verizon vs. AT&T isn't TCP/IP vs. TCP/IP. It's more like Token Ring vs. TCP/IP -- the underlying wireless technologies are quite different. Verizon (and most cellular companies) use CDMA for the underlying wireless protocol, while AT&T and T-Mobile use GSM, which (coincidentally) is used most everywhere else on the planet.

2. Since AT&T and T-Mobile use the same wireless protocol, you CAN move phones between the two networks...with some restrictions. For the iPhone, you'd have to jailbreak it first, and you'll lose 3G, but you can still use EDGE-based services for data connectivity, and the phone will still work. The same is true for the T-Mobile G1 Android phone -- you could take an unlocked G1 and run it on AT&T, but you'll lose 3G support. (The reason for this is that T-Mobile and AT&T use different wireless bandwidths for 3G data.)

This is still miles better than Verizon and other CDMA-based cellular providers -- you can't readily move phones between the networks at all.

3. In ~5 years, this won't matter as much, as Verizon has pledged to use 4G for their next generation network (to be deployed in the next 2-5 years). 4G is a GSM-based wireless protocol, so (theoretically) it should be possible to run a 4G iPhone on Verizons network. (Of course, we'll need a 4G iPhone first...) The "big" question will be whether the iPhone will still be locked to AT&T in that timeframe, and whether or not AT&T & Verizon will use compatible wireless bandwidths (i.e. will we avoid the current T-Mobile/AT&T 3G scenario?).

So to answer your question "Are we so primitive in our networking prowess in 2009 that we have to restrict devices to specific carrier networks?" The answer is No. Europe, Asia, and the rest of the world have solved this problem, allowing complete phone portability between networks (with the usual phone tying for the "cheap phones on a 2 year contract" deal we know and love). It's only because the US has (1) multiple incompatible wireless protocols (CDMA vs. GSM), and (2) CDMA has no provisions for phone/network portability that we have any device/network restrictions at all.

Even with GSM companies that tie phones to the network, you can usually unlock the phone after a period of time (except for the iPhone) -- you just need to call up e.g. AT&T and request that they unlock your phone. Then you can go to Europe and purchase a GSM card for cheap local calls...

Kevin Hazzard United States

Sunday, January 25, 2009 9:13 AM

Kevin Hazzard

All good points Jonathan. I know it's not about the overlying protocols. But the overlying protocols should be a thin shim on top of a very portable TCP/IP stack. My real intent (besides ranting) was that Apple would have far better market penetration if they made the iPhone available on all of the networks. The iPhone is sexy enough that it does well in attracting customers to AT&T but the G1 is the one that could really use portability. The T-Mobile network isn't nearly as strong so it seems strange to me that Google opted to tie themselves so closely to one carrier, especially one that's an underdog.

What ever happened to Software Defined Radio? It was all the hype 8 years ago. If all of these devices could adapt their tranceivers dynamically to the radio environment and if we could get the carriers to start acting like infrastructure providers instead of marketing companies...

You get my point. It's an impossible problem, one that government regulation could help solve. But with the way our government has been failing in telecom issues over the past few decades, I'm not sure I want them involved at all. Frown

Jonathan Pryor United States

Sunday, January 25, 2009 11:09 AM

Jonathan Pryor

In an ideal world, abstracting out the network layer would work.  This isn't an ideal world, primarily because of cost: supporting both GSM and CDMA increases costs for testing, validation, and FCC approval (as each phone needs to be tested and approved separately).

(Supporting both networks might not be 100% perfect either; I've heard rumors that phones designed with one network in mind don't tend to work as well when "ported" to the other.  Alas, I have no specific details; this is just what I've heard.)

Cost is particularly important for smaller phone manufacturers, such as the OpenMoko.  Even for larger companies such as Apple and RIM, I'm sure these are important issues -- notice that the Blackberry Storm is exclusive to Verizon for bundled deals.

(I'm also not sure that the iPhone needs greatly improved market, as it's already taken 23% of the market:arstechnica.com/.../iphone-ends-year-with-strong-market-share-faces-challenges)

Then there's the benefits of exclusivity -- reportedly Apple got AT&T to agree to a number of changes that AT&T might not have agreed to w/o the exclusivity, such as Visual Voicemail.  Future iPhone push support will supposedly require additional hardware within the network, so if the network provider (e.g. Verizon) doesn't provide the extra hardware then some iPhone features won't be supported.  Exclusivity provides a carrot for Apple to get what they want from AT&T.  Dropping such exclusivity would lose them the carrot, and thus potentially result in a less compelling product (as e.g. AT&T might not otherwise want to do the extra work).

As for Google and T-Mobile, Google hasn't tied themselves to T-Mobile.  They're trying to pull a Microsoft -- they'll provide the operating system (Android) and work with hardware providers for the actual phone.  The G1 is supposed to be the first of many Android phones, and I don't know of any reason that Verizon couldn't be supported (except hardware vendors not wanting to pay the associated costs, mentioned above).

Finally, the software defined radio died because of the government; government can't save it.  It died because it would allow things that governments don't like, e.g. allowing consumer-grade devices to capture military communications.  Most governments don't like that, and unless you somehow restrict the hardware from listening in on the military channels the goverment won't approve.  Alas, such restrictions are anathema to the entire idea of software defined radio.  So at present, the best we're likely to see is software defined radio as an implementation, but the utility/flexibility wouldn't be exposed to "userspace" applications; the restrictions would be "baked" into the firmware.

Justin Etheredge United States

Sunday, January 25, 2009 7:44 PM

Justin Etheredge

If the rumors are to be believed, Apple first went to other phone companies before AT&T with hopes of getting the iPhone off the ground. With the original iPhones Apple had a huge list of demands, including not having to activate the phone is a store, selling the iPhone from an Apple store, the carrier had to integrate the visual voicemail etc... and Apple didn't want any contracts. AT&T was the only company that would relent to Apples demand because they felt like they had the most to gain from the recent Cingular merger. Apple and AT&T signed a 5 year contract, and voila, you have a single company phone. Who knows if all of the rumors were true though, but it sure seems to make sense.

Jonathan Pryor United States

Monday, January 26, 2009 9:56 AM

Jonathan Pryor

That's more or less what I heard.  I hadn't heard about the "no contract" part, and that doesn't even make sense considering that they signed a 5 year contract (unless the contract was for something else?), but I had heard about the various demands including Visual Voicemail.

It's because of demands like that, and cooperation from the phone company, that the iPhone is as compelling as it is.  Apple is likely to continue this further (e.g. the aforementioned "push" functionality).  So making a "generic works with every phone company" phone likely isn't in the cards, as Apple is all about the vertical integration.  This has it's good points and bad points.

But as long as not all customers require the vertical integration, it should be possible to move phones between networks.  And it is -- you can jailbreak the iPhone and run it on T-Mobile, for instance, and overseas networks.  The only loss here is Verizon and other CDMA networks, but even that will (hopefully) disappear with the migration to 4G...

Kevin Hazzard United States

Monday, January 26, 2009 10:30 AM

Kevin Hazzard

Indeed, it appears as though Apple's eye for user experience (not just GUI) has begun to transform the mobile phone market. The process of buying and activating the iPhone was impressive, in a good way. I wonder at which percentage of marketshare will Apple be accused of predatory practices to get as far as they have? I ask that half jokingly. Microsoft has been punished for its hard work by the EU for a decade now.

Vladimir Kelman United States

Saturday, May 02, 2009 2:52 AM

Vladimir Kelman

By the way, although it's expensive, you can buy unlocked "developer" version of Google Phone and make it work in AT&T. I did just that, because I couldn't wait any more. It was easy with a help I got from Android Google group. Android is quite interesting programming environment (with Java or even Scala used for developing custom application). A developer's community there is very active. Look at http://developer.android.com/index.html, developer.android.com/guide/developing/device.html
You'll have to register as Android developer (http://market.android.com/publish/Home) and then you'll be able to buy a phone.

Comments are closed