It all started when I thought about WiFi calling.
WiFi calling is the relatively simple idea that when I’m at home, where my carrier’s signal doesn’t penetrate, I’m still able to access the Internet on my smartphone using WiFi; therefore, I should also be able to make and receive voice calls. It’s essentially the merging of VOIP with traditional cell phone calling services.
So far, the closest carriers have come is the femtocell - a device that plugs into your home router and acts as a mini cell tower for your home. However, femtocells only make sense when the phones they’re hosting don’t have internet access; that is, dumphones. Femtocells are a relic of the bygone era before the Internet-connected smartphone era ushered in by Apple five years ago with the original iPhone.
The logical next step in the modern world is the ability to access this cell phone calling network over WiFi. The iPhone’s revolution of phones was that is relegated the “phone’s” status from the entire device to just one of many apps. Consider the Motorola RAZR, the last great dumbphone. Sure, it may have had some basic data capabilities, but spend three seconds looking at the phone at you can immediately tell the device was made for calling, and to a lesser extent texting. Even the smartphone of that era, the mighty BlackBerry, was first and foremost a phone. The then-powerful email capabilities were just something that Mike Lazaridis hacked onto a phone in a dumbphone era. The iPhone threw all of this out. It was, first and foremost, a pocket-sized computer. It’s name is somewhat misleading in this regard -- being a phone is just one of the myriad components of the iPhone. It’s no different than the YouTube app, or the copy of Angry Birds you downloaded. It’s an app that happens to use a set of APIs that connect to the carriers’ voice calling services.
Once Skype came to the iPhone, this became clear -- it’s possible to ignore the phone application and use Skype for all calls. There’s even video calling. But wait -- all Skype uses, as an app, is data. Voice and Skype is data. Video on Skype is data. It’s all just data, and it doesn’t matter at all whether that data is routed through a WiFi connection or over EDGE/3G/LTE. Why should the app that routes calls through my carrier’s voice service be any different?
We’re now beyond the concept of WiFi calling. In fact, the scenario I’ve just described is just VOIP, plain and simple. Phones have IP connections, so it follows that they support VOIP. Why attempt to crudely merge VOIP with traditional phone service and call it WiFi calling when it’s just as easy to do away with the traditional phone service entirely? Carriers have been whining for ages about the Great Bandwith Shortage. Everything Over IP is the solution. Consider New York Penn Station. There are dozens of train platforms, and they’re all allocated to a specific train operator. This leads to situations where one train operator is scrambling to manage more trains than he or she has platforms while another train operator has several platforms available and sitting unused. The pre-allocation of the station’s platform resource causes problems in load management. Similarly, pre-allocating certain parts of wireless spectrum to mobile data, and other parts to voice calling, isn’t going to help manage the limited spectrum resource that’s available.
This idea is called going “over the top”. It’s a realization that any and all communication that people would ever want to do with each other -- whether it be through voice, video, webpage, or YouTube -- can be represented as a data packet that’s sent over the Internet. Therefore, it follows that the only connection necessary to anyone is an Internet connection.
Let me paint a picture. Microsoft just bought Skype. So, all Microsoft has to do to create this Internet Communicator is replace the phone app with Skype and sell their Windows Phones as phone-sized tablets with mobile data connections. Skype supports phone numbers for a nominal fee, so everyone would still be able to access everyone else through the traditional phone number system that we’re all accustomed to. And think about it -- Skype supports video. So, instantly Microsoft now has support for video calling between phone numbers, using Skype as the backend. Skype supports IM too -- this would become the phone’s texting/SMS service. Add in a $30/month data plan from your favorite carrier, and boom, a fully featured Internet Communicator phone for a fraction of the price you’re paying your carrier now.
Google could easily do this as well. They already support free calling to the US and Canada from GMail using Google Voice. They support video calling in Google Plus Hangouts (as well as GMail video calls). Google Voice supports SMS, and Google Talk could be integrated in. Instantly, all of Google’s services become integrated on this new device -- the Internet Communicator. Note that Google Voice supports telephone numbers -- so this system, too, would be compatible with the others through the good old telephone number system.
Apple, too, could reach this goal of the Internet Communicator. iMessage is texting, and FaceTime already supports video calls. Audio-only FaceTime and phone number assignment to Apple users are all that separate Apple from the Internet Communicator.
The Internet Communicator works because the age-old interface of phone numbers is preserved. Different services -- Skype, Google Voice, and FaceTime in my examples -- implement this phone number interface to provide communication. Carriers needn’t be left out, either; they would be free to create their own apps that provide this same functionality.
The Internet Communicator is the logical end to the revolution that started with the iPhone, five years ago. It’s within our reach now. Someone’s just got to do it.
WiFi calling is the relatively simple idea that when I’m at home, where my carrier’s signal doesn’t penetrate, I’m still able to access the Internet on my smartphone using WiFi; therefore, I should also be able to make and receive voice calls. It’s essentially the merging of VOIP with traditional cell phone calling services.
So far, the closest carriers have come is the femtocell - a device that plugs into your home router and acts as a mini cell tower for your home. However, femtocells only make sense when the phones they’re hosting don’t have internet access; that is, dumphones. Femtocells are a relic of the bygone era before the Internet-connected smartphone era ushered in by Apple five years ago with the original iPhone.
The logical next step in the modern world is the ability to access this cell phone calling network over WiFi. The iPhone’s revolution of phones was that is relegated the “phone’s” status from the entire device to just one of many apps. Consider the Motorola RAZR, the last great dumbphone. Sure, it may have had some basic data capabilities, but spend three seconds looking at the phone at you can immediately tell the device was made for calling, and to a lesser extent texting. Even the smartphone of that era, the mighty BlackBerry, was first and foremost a phone. The then-powerful email capabilities were just something that Mike Lazaridis hacked onto a phone in a dumbphone era. The iPhone threw all of this out. It was, first and foremost, a pocket-sized computer. It’s name is somewhat misleading in this regard -- being a phone is just one of the myriad components of the iPhone. It’s no different than the YouTube app, or the copy of Angry Birds you downloaded. It’s an app that happens to use a set of APIs that connect to the carriers’ voice calling services.
Once Skype came to the iPhone, this became clear -- it’s possible to ignore the phone application and use Skype for all calls. There’s even video calling. But wait -- all Skype uses, as an app, is data. Voice and Skype is data. Video on Skype is data. It’s all just data, and it doesn’t matter at all whether that data is routed through a WiFi connection or over EDGE/3G/LTE. Why should the app that routes calls through my carrier’s voice service be any different?
We’re now beyond the concept of WiFi calling. In fact, the scenario I’ve just described is just VOIP, plain and simple. Phones have IP connections, so it follows that they support VOIP. Why attempt to crudely merge VOIP with traditional phone service and call it WiFi calling when it’s just as easy to do away with the traditional phone service entirely? Carriers have been whining for ages about the Great Bandwith Shortage. Everything Over IP is the solution. Consider New York Penn Station. There are dozens of train platforms, and they’re all allocated to a specific train operator. This leads to situations where one train operator is scrambling to manage more trains than he or she has platforms while another train operator has several platforms available and sitting unused. The pre-allocation of the station’s platform resource causes problems in load management. Similarly, pre-allocating certain parts of wireless spectrum to mobile data, and other parts to voice calling, isn’t going to help manage the limited spectrum resource that’s available.
This idea is called going “over the top”. It’s a realization that any and all communication that people would ever want to do with each other -- whether it be through voice, video, webpage, or YouTube -- can be represented as a data packet that’s sent over the Internet. Therefore, it follows that the only connection necessary to anyone is an Internet connection.
Let me paint a picture. Microsoft just bought Skype. So, all Microsoft has to do to create this Internet Communicator is replace the phone app with Skype and sell their Windows Phones as phone-sized tablets with mobile data connections. Skype supports phone numbers for a nominal fee, so everyone would still be able to access everyone else through the traditional phone number system that we’re all accustomed to. And think about it -- Skype supports video. So, instantly Microsoft now has support for video calling between phone numbers, using Skype as the backend. Skype supports IM too -- this would become the phone’s texting/SMS service. Add in a $30/month data plan from your favorite carrier, and boom, a fully featured Internet Communicator phone for a fraction of the price you’re paying your carrier now.
Google could easily do this as well. They already support free calling to the US and Canada from GMail using Google Voice. They support video calling in Google Plus Hangouts (as well as GMail video calls). Google Voice supports SMS, and Google Talk could be integrated in. Instantly, all of Google’s services become integrated on this new device -- the Internet Communicator. Note that Google Voice supports telephone numbers -- so this system, too, would be compatible with the others through the good old telephone number system.
Apple, too, could reach this goal of the Internet Communicator. iMessage is texting, and FaceTime already supports video calls. Audio-only FaceTime and phone number assignment to Apple users are all that separate Apple from the Internet Communicator.
The Internet Communicator works because the age-old interface of phone numbers is preserved. Different services -- Skype, Google Voice, and FaceTime in my examples -- implement this phone number interface to provide communication. Carriers needn’t be left out, either; they would be free to create their own apps that provide this same functionality.
The Internet Communicator is the logical end to the revolution that started with the iPhone, five years ago. It’s within our reach now. Someone’s just got to do it.





