Commentary

Stephen Wellman
 

Learning To Speak The Same Language Of Mobility

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.

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:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

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.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links