Commentary

Stephen Wellman
 

I Want My Seamless Mobility

I have heard a lot about seamless mobility -- the dream of universal wireless access where users can roam freely between wireless LANs and cellular networks and back again -- this week at Interop. I keep hearing vendors promise dual-mode access, but when I raise the issue of the pink elephant in the room, the vendors just smile at me and change the subject.

I have heard a lot about seamless mobility -- the dream of universal wireless access where users can roam freely between wireless LANs and cellular networks and back again -- this week at Interop. I keep hearing vendors promise dual-mode access, but when I raise the issue of the pink elephant in the room, the vendors just smile at me and change the subject.It happened, yet again, yesterday when I met with Nokia. They talked up their partnerships with Alcatel-Lucent and Avaya as well as their new deal with Cisco Systems. Nokia promised a new dual-mode phone that would work with technology from these partners. I saw the demo and I was impressed.

But, Nokia could not tell me when they were going to launch a dual-mode phone. They couldn't tell my colleague, Antone Gonsalves, either.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

When Nokia brought the E61 to the U.S. last fall, the new phone didn't have Wi-Fi, rendering it less than optimal. While Nokia promises the future of seamless mobility, they still don't have a device in the U.S. that can live up to the promise.

Then I really pushed Nokia. I asked them what they planned to do to help the U.S. carriers embrace dual-mode access. Then came the smiles.

I personally hope that Nokia will soon announce a working dual-mode device for the U.S. I have been waiting for fixed-mobile convergence to become a reality for the last three years. But given how good the carriers are at delaying this -- and how little enthusiasm they seem to have for dual-mode access -- I don't think I'll bet on it.


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