Sunday, 15 July 2012
Why We Need a Standard for the Internet of Things
Posted on 02:48 by Maria Scott
The Internet of things is supposed to connect every aspect of our lives from our homes and cars to the objects we wear and the goods we consume. It’s even connecting ice machines. But one thing the Internet of things lacks is a unifying standard.
Devices will be connected by different radio technologies: Wi-Fi, Bluetooth, ZigBee, and a host of 2G and mobile broadband cellular technologies. There’s really no way of assuring your “thing” will connect to the network or networks available at any given time.
The mobile industry is trying to rectify the problem, at least as it pertains to cellular machine-to-machine (M2M) technologies. The bigger issue of fragmentation among bands and technologies isn’t going to get worked out anytime soon: You’re not going to connect a GSM wristwatch to a CDMA or Wi-Fi network. But often you can’t connect that GSM wristwatch to a GSM network either. Roaming among networks that use the same technology requires not only a business arrangement with each carrier but also a common protocol.
A group of global wireless-standards bodies are trying to tackle that problem. The European Telecommunications Standards Institute (ETSI), the Telecommunications Industry Assn. (TIA), and the Alliance for Telecommunications Industry Solutions (ATIS) in the U.S. are working with their counterparts in Japan, Korea, and China to develop a common “service layer” that can be embedded in every M2M device, making them compatible with M2M application servers hosted by any global operator.
At the end of the day, that means many of the devices in our Internet of things suddenly become untethered from specific networks. That wristwatch could work on AT&T (T) as well as T-Mobile’s GSM network and then connect to Rogers Communications’ (RCI) GSM towers when you fly into Toronto. Shipping containers embedded with M2M modules connect to whatever network is available at any port of call. The same wireless smart meter could be deployed in Kansas City or in Marrakesh without having to completely reconfigure its software.
Roaming among networks is possible today. The problem is those arrangements tend to be ad hoc deals put together by M2M service aggregators like Kore Telematics, which sort out all the underlying carrier deals and manage each network’s various protocols. Some operators have started taking matters into their own hands.
On Tuesday seven major operators—KPN, NTT DoCoMo (DCM), Rogers, SingTel, Telefónica (TEF), Telstra, and Vimpelcom (VIP)—formed an alliance to create a common M2M management platform allowing for the “delivery of a global product with a single SIM, eliminating roaming costs in the countries of participating operators.”
It sounds like a standard, but it’s not quite the same thing. All seven providers use the same M2M management platform supplied by Jasper Wireless, so they are able to bridge their difference through a common vendor. Still, the effort is admirable and could lead to the creation of ad hoc interoperability among a large section of the world’s carriers. Jasper has many other customers besides those seven, including AT&T and América Móvil (AMX).
A good example of a problem such cooperation could solve is the Kindle’s international predicament. Even though Amazon (AMZN) sells the Kindle all over the world it has one “home” network, AT&T. That means any Kindle user either living in or traveling to another country has to pay international download (read: roaming) fees to buy a new book or access a periodical subscription.
It’s fairly ridiculous that a multinational retailer like Amazon can’t support its flagship device internationally without resorting to such single-carrier arrangements. But if Amazon were to broker a deal with this new alliance, the Kindle would find itself at home on whichever of these seven networks it wandered onto.
There’s a possibility the industry will coalesce around a single proprietary technology such as Jasper’s, creating an ad hoc standard much like we see developing in the public-cloud space around Amazon Web Services. But an ad hoc standard isn’t a standard.
What we need is for the industry to get together and sort out a way to make every M2M device carrier- and network-agnostic. A gadget maker should be able to build a device that connects to the Internet of things without a specific carrier, a specific management platform, or a specific application server in mind. The business deals with individual carriers would still need to be sorted out, but first we need to remove the technology barriers. Otherwise we won’t wind up with a single Internet of things but instead many internets, each with its own separate sets of things.
Subscribe to:
Post Comments (Atom)
No Response to "Why We Need a Standard for the Internet of Things"
Leave A Reply