The InformationWeek -- Blogs
Over The Air

Topics:   Mobile

  • Email this page E-mail this page
  • Print this page Print this page
  • Bookmark and Share
  • icon

Learning To Speak The Same Language Of Mobility


Posted by Stephen Wellman, Feb 19, 2007 04:46 PM

I have almost recovered from the insanity that was the 3GSM World Congress last week in Barcelona. Not only did my airline manage to lose my baggage on the flight home, I also caught a nasty case of the flu -- so much for constantly using hand sanitizer and taking large doses of Vitamin C. As I sat down to digest the week that was, I kept thinking about how differently the carrier and the enterprise IT worlds see mobility.


Daniel Taylor over at the Mobile Enterprise Blog has a great article on just this very issue.

Taylor hits the nail on the head:

Device management is but one example. Fixed-mobile convergence. Mobile data network roaming. "Personal" services on "business" devices and vice versa. Each and every time, the carrier service is designed with virtually no insight or knowledge of the way IT departments intend to do the same things.

There are a few examples, like the enterprise-mobile integration of PBX services (Avaya, Tango Networks, and Cisco/Nokia come to mind). But for an example of the lack of enterprise knowledge within the carrier supply chain, there is the OMA DM working group.

A few months ago, a small group within OMA proposed an extremely early-stage idea of putting security credentials onto a management object to be supported by OMA DM. This was a proposal to assemble a proposal -- as in the very beginning of the process for the Secure Element Management Object (SEMO). Within weeks of the initial idea, several very large mobile operators (Cingular and Vodafone to name a few) shot down the proposal, saying that (1) other standards organizations like 3GPP/3GPP2 and ETSI have already created standards to address the intention of the SEMO, and (2) SEMO would actually decrease security by opening the door on what is otherwise a secure exchange between the mobile operator and its customer. The SEMO objection was rapid and valid, because everyone involved in the OMA readily understood the relevant technologies and approaches.

The real issue here is that carriers aren't focused on business customers. It's not their core competency. They're good at selling service and running their networks, not at designing and building complex solutions for business IT networks.

That's why, as Taylor points out, issues such as device management may be new to carriers, but they're old hat to IT departments.

Carriers, start listening to enterprise IT managers. They know what they want and they will tell you, if you take the time to ask them.

« Has Microsoft Patented A Successor To Clippy? | Main | Mobile Users In Beijing Open New Year With 400 Million SMS Messages »



Sign Up Now
For InformationWeek News Alerts




This is a public forum. United Business Media and its affiliates are not responsible for and do not control what is posted herein. United Business Media makes no warranties or guarantees concerning any advice dispensed by its staff members or readers.

Community standards in this comment area do not permit hate language, excessive profanity, or other patently offensive language. Please be aware that all information posted to this comment area becomes the property of United Business Media LLC and may be edited and republished in print or electronic format as outlined in United Business Media's Terms of Service.

Important Note: This comment area is NOT intended for commercial messages or solicitations of business.




 
Mobile Video


Sign Up For The Over The Air Newsletter
Every Friday, our experts and analysts explore the business, strategy, and management issues most important to mobile and wireless technology.

Sign up for our free, weekly newsletter today!

Newsletter Archives


 

  1. Sequential Programming: Like Eating Peas with a Straw.
  2. Biomolecular device using self-assembled DNA nanostructures?
  3. Coreinfo v2.0: A Simple Utility to Understand the Manycore Complexity in Windows


Join The InformationWeek Group On LinkedIn


                           


  1. More Reasons Why Linux Misses The Desktop
  2. Too Much Netbook For Too Litl?
  3. Motorola Explains Why Droid Doesn't Have Multi-Touch
  4. Sprint And T-Mobile Headed The Wrong Direction


  1. Google Computes News Quality
  2. Internet Use Increases Social Connectivity
  3. Review: Motorola Cliq Smartphone
  4. Florida Hospital Dials Up iPhones For Nurses
  5. Full Nelson: A Web Presence Needs Sizzle, My Nizzle
  6. Is Antivirus Software Dead?

 

  Ars Technica
Boing Boing
Channel 9 Forums
CRN Blogs
Dr.Dobb's Portal: Blogs
Engadget
Gizmodo
GrokLaw
  Lifehacker
Schneier on Security
Slashdot
TechCrunch
Techdirt
Techmeme
Valleywag

  DECEMBER 2008
NOVEMBER 2008
OCTOBER 2008
SEPTEMBER 2008
AUGUST 2008
JULY 2008
JUNE 2008
MAY 2008
  APRIL 2008
MARCH 2008
FEBRUARY 2008
JANUARY 2008
DECEMBER 2007
NOVEMBER 2007
OCTOBER 2007
SEPTEMBER 2007