Monday, June 23, 2008

T-Mobile Expands


Today T-Mobile added the Nokia 6301 and Samsung T339 dual-mode phones to their line-up for the HotSpot @Home service.

With 8 HS@H phones available today, T-Mobile has most of the bases covered. The much anticipated HTC Shadow II will fill in the Windows Mobile 6.1 hole and round out the portfolio for T-Mobile.

Looks like T-Mobile will make good on their goal of adding ten new handsets this year.


Friday, June 20, 2008

iCall: Opportunity or Threat

A couple weeks ago there was news about a new application for the iPhone called iCall. In the clever video demo below, the founders describe iCall as an application for the iPhone which enables users to make calls for free over any Wi-Fi access point. The video how theiCall application works:

  1. User starts call on GSM
  2. User goes into Wi-Fi
  3. Phone detected/attaches to Wi-Fi
  4. iCall application asks the user if they would like to switch the call to Wi-Fi
  5. Phone switches networks

If it sounds a lot like a UMA-based dual-mode handset service, it is. The only difference between iCall and T-Mobile’s HotSpot @Home service is step 4: User intervention.





So, is this an opportunity or a threat for the mobile operator? (Ed note: UMA Today’s position is always from the viewpoint of the mobile operator, UMA is for mobile operators)

There is a threshold for subscribers between ‘actions’ and ‘cost’. At what point does a user change their actions to save on costs? (Ed note: Here in San Jose, it’s when gas hits $4.60/gallon...)

Will users actually stop a call, press a button, and switch it to Wi-Fi to save money?

Or would users rather have a call that automatically switches to Wi-Fi and saves money? If so, then T-Mobile, Rogers, Orange, Cincinnati Bell, Telia and others already have this covered.

Thursday, June 19, 2008

The Connected Home Heats Up

Just in time for summer, there is a lot of activity in making the handset part of the Connected Home.

For those who don’t know, there is a vision of a connected home where devices develop an ad-hoc network and can communicate. Standardizing this has been the domain of UPnP and more recently DLNA.

While there are a growing number of devices (TVs, DVRs, Printers, …) which support Connected Home, the mobile phone has been consistently out of the picture. Now two different approaches are helping to pull the phone into the connection.

First is Nokia with the N95, using Wi-Fi as the transport to communication with other devices in the home.



But clearly there is only a small number of Wi-Fi enabled handsets, and so femtocell vendor ip.Access has put together his clever demonstration on how a 3G phone could be proxied into the connected home through a femtocell.



While there are some questions about how this works, it's a powerful vision of bringing mobile phones into the connected home.

Wednesday, June 18, 2008

The Rush to Support Iu-h

There has been a lot of fervor surrounding the 3GPP's activities to develop a new Home Node B (aka femtocell) standard.

I came across the blog post the other day with the clever title "Supporting Iu-h, why the rush?"

The author has a pretty good take on the situation.

Tuesday, June 17, 2008

RAN Gateway wins again

I have spent some time considering the pros and cons of the new 3GPP HNB femtocell architecture. It’s too early to call it a standard, but for now, the basic building blocks are in place for putting the spec together.

One of the fundamental building blocks of the HNB effort is a ‘RAN Gateway’ style architecture. In this case, the RAN gateway network element sits ‘parallel’ to an RNC or BSC, and connects into the mobile core network via existing, well defined circuit interfaces (Iu-CS) and packet interfaces (Iu-PS).

Operators evaluating femtocells and femto architectures immediately grasped the benefits of using a RAN gateway approach:

  • All existing circuit and packet services are supported through the femtocell access network as they are supported through the macro RAN network. This is because the RAN gateway uses the same service interfaces as the RNC.
  • A ‘RAN’ gateway is located in the RAN, with a clear demark point into the mobile core network. For operators, they did not need to change the MSC or the service core in any dramatic fashion.

For all the rhetoric and posturing around the benefits of SIP and IMS, operators quickly understood that the most pragmatic approach for femtocell service delivery was through a RAN gateway architecture. In fact, one of the things that the proposals from Huawei, NSN, Alcatel/Lucent and Kineto/NEC/Motorola (ie UMA/GAN) all had in common was a RAN gateway.

From a UMA perspective, one important outcome of the HNB specification is a validation of the RAN gateway architecture operators and vendors alike.

UMA/GAN is, of course, the original RAN gateway architecture.

I harken back to the early days of dual-mode handsets (DMH). The debate raged: IMS/SIP/VCC vs UMA/GAN. It’s taken 3 years for this to sort itself out in the market. Today, it’s clear that UMA/GAN and the RAN gateway architecture is the (only?) choice.

In the last 12 months, the debate started again, this time for femtocells. But just as quickly, a winner was declared: RAN gateway for HNB (a la GAN).

Friday, June 06, 2008

Softmobile client from Gemalto

A UMA-enabled softmobile client is an application which has been on the drawing board for some time. There has been interest, but it’s been slow in coming.

For those who don’t know, the UMA-enabled softmobile client is a mobile telephony interface application which runs on a laptop and connects to the mobile core network via UMA.

The application is ideal for operators to offer their subscribers another way to use their services, especially when traveling outside the home country. Typically when I travel to Europe, I connect my laptop at the hotel and fire up Skype. But if I were to have a softmobile client from my GSM provider T-Mobile, I could use it instead.

Back at MWC 08, technology supplier Vitendo announced they had developed a UMA-based soft mobile. In addition, Gemalto announced that Orange has selected their UpTEQ Smart Dongle. But the announcement said nothing about UMA.

Now on their web site, the UpTeq Smart Dongle lists support for UMA.

This week, Orange UK announced plans to ratchet up their services and alluded to, among other things, a “…new ‘totally connected’ product line – including laptops, to build on fixed and mobile broadband capabilities”

We’ll have to keep an eye out to see if Orange UK becomes the launch pad for the softmobile application.

Thursday, June 05, 2008

3GPP Selects Femtocell Standard, and it’s not (exactly) UMA/GAN

It was announced by multiple sources this week that 3GPP selected a reference architecture for femtocell-to-core network connectivity. This isn’t the completed standard, but sets the framework for the 3GPP RAN 3 working group to develop a full specification. The plan of record, per the 3GPP, is for the full stage 2 and stage 3 documents to be completed by Dec 2008 (in Release 8).

As has also been point out recently, the existing 3GPP UMA/GAN specification was one of a few architectures being considered as the basis for a formal 3GPP femtocell standard. The net result is that the UMA/GAN standard, as is, was not chosen. Sad but true. In order to reach an industry consensus on a HNB architecture there was a measure of compromise from all the participating companies. That’s the nature of standards: compromise.

However, while the HNB reference architecture is not full UMA/GAN, it adopts a number of key principles first introduced in the 3GPP GAN standard. For example, at the highest level, it follows an access-based (rather than core-based) approach, leveraging the existing Iu-cs/Iu-ps interfaces into the core service network. It also identifies the use of a specific protocol for solving a number of challenges associated with the ad-hoc deployment of devices over the internet.

Frankly, while the UMA community would have been delighted if 3GPP had adopted GAN lock-stock-and barrel (as they say in the US) as the formal femtocell standard, the likelihood has always been low. Fortunately, the agreed femtocell architecture builds on several core principles of GAN, which will help accelerate the market.

ThinkFemtocell has a good breakdown of different elements of the work.

For at least a little while longer, UMA/GAN remains the only 3GPP standard which supports femtocells today...

Wednesday, June 04, 2008

Rogers Launches Pearl 8120

Rogers, the latest UMA-based dual-mode service provider, today launched the RIM Pearl 8120 handset in their portfolio. The UMA Pearl is currently available from Orange and T-Mobile as well. It's good to see Rogers expanding their handset portfolio.

Monday, June 02, 2008

Vodafone Station: Screaming for UMA

As you may have seen, Vodafone announced a new product called “Station”. The original announcement was a bit confusing, but now that the dust has settled, I think it’s becoming clear.

The Station, made by Huawei, is a broadband router/modem. It can use either the integrated ADSL2+ modem or HSPA (via an additional dongle/UBS) for backhaul on the WAN. On the LAN, the Station provides Wi-Fi.

The target is to provide Vodafone subscribers with a broadband WAN connection. The target audience is likely someone using the Voda HSPA network for laptop data access. When at home, the HSPA network may have in-building propagation issues and the throughput/data rate may be low. Enter the Station. Install the Station with your HSPA dongle/USB key near a window to get a strong HSPA signal from the macro network. Then the Station uses Wi-Fi to transmit that signal to the laptop when at home.

So what is the ADSL2+ modem for? Well presumably it is faster to use the fixed network. And while I’m just speculating, I’ll bet they don’t want people sitting in their homes streaming lots of data over the HSPA network. Therefore, to offload the macro network, it’s better to have users running over a fixed line DSL connection. So users can start with HSPA while their DSL line is being installed.

The last wacky part? The Station comes with an analog voice port (ATA). Apparently when using the HSPA dongle, the station provides voice services over via the circuit voice capabilities of HSPA. And given the dongle has a SIM, this is another phone number/service available.

What I don’t understand is when the user transfers to the fixed line DSL connection, what happens to the analog voice service? With no dongle, there’s no way to associate the Station with the Vodafone mobile core. Hummm…

So why is this screaming for UMA?

First, it’s providing Wi-Fi indoors, clearly idea for a dual-mode handset service, and when the service transitions to the ADSL network, even better. With UMA, Vodafone could have a real ‘home zone’ service.

Second, the ATA ports could simply run UMA for the terminal adaptor function. Now the ports would be live/available to the consumer when connected via HSPA and/or DSL. It wouldn’t matter.

As I was writing this, I found a comment on Om Malik’s blog from someone suggesting there was a big opportunity in Wireless WAN and Wireless LAN. But can they build a femtocell (3G LAN) that uses HSPA for the WAN connection? That seems like a lot of 3G in one box, but maybe it’s on the drawing board somewhere.

Tuesday, May 27, 2008

The 3G iPhone needs "...VoIP like T-Mobile..."

Dear Steve Jobs...

In an open video/letter to Apple, the Street's senior technology correspondent Gary Krakow makes a list of his requirements for the new 3G iPhone.

Top of the list: 3G (doesn't that go without saying?)
But #2 on the list: "...a VoIP feature like T-Mobile..."

I think he means UMA!





If there's a problem, here's the link:

http://link.brightcove.com/services/link/bcpid1078966384/bclid1137812485/bctid1564516136

Wednesday, May 21, 2008

Apples and Oranges

I do appreciate the quote in Strategy Analytic’s press release about their latest research on the Enterprise FMC Market. They said “UMA is here to stay”.

But after reading the release about the report, I’m left feeling they are comparing apples and oranges.

"SIP-based services will initially be implemented by large multinationals with the capacity to carry voice traffic on their private MPLS network. Consequently, SIP-based revenues will overtake UMA revenues toward the end of the forecast period. Moreover, Microsoft's UC (Unified Communications) solution, is also likely to see positive uptake as a business solution," commented Andrew Brown, Director for Wireless Enterprise Strategies.

There’s no doubt that enterprises will use SIP for IP telephony. IP-PBXs all run SIP. One of the fundamental advantages is that the calls can be carried between PBXs over the enterprise’s own private networks. But that’s an enterprise solution.

UMA is a technology for mobile operators, not enterprises. Certainly prosumers will use UMA in the enterprise, but IT departments can’t ‘deploy UMA’. And UMA was not designed to be carried through a private network.

So comparing UMA revenues with SIP revenues for Enterprise FMC doesn’t seem to be comparing like services.

There is no doubt that UMA will have an impact on the enterprise market, but it will be an FMS impact, migrating minutes from the fixed network/PBX to the mobile network.



RIM Redux

Following up from yesterday's post, I have now listened to all of Jim Balsillie’s comments during his presentation at RIM’s Capital Markets Day, May 12, 2008, I wanted to offer up some of his quotes.

I’ve tried not to take these comments too far out of context, but basically Mr. Balsillie is bullish on UMA. About 29 minutes into the presentation (slide 24), he talks of their UMA-enabled products:


“The Wi-Fi UMA is going remarkably well.”
“I’m hard pressed to not see this as inevitable, for most if not everyone.”
“This is happening and it’s happening fast”.

In his Q&A section (slide 33), a gentleman from Integral Capital Partners asks:

“Can you comment on the carrier’s adoption, or in some cases, the lack there of, of the UMA option?”

Mr. Balsillie: “I think it’s a fair comment. I think a lot of carriers were keen on it, some were less keen on it. It’s hard to find a carrier that isn’t keen on it now. Some saw it as a threat, I saw it as an enabler, an inevitability. In a sense, it’s hard to find a carrier that isn’t excited about it now. … I think it’s just so compelling and so inevitable. It’s not going to take out the cell phone. It’s a complement.”


I couldn’t agree more.

Monday, May 19, 2008

RIM is BOLD with UMA

RIM’s presentation during their Capital Markets day (May 12, 2008) talked a bit about UMA. In the slide below, they indicate the new Bold device is part of their UMA portfolio. Sounds good to me.


Friday, May 16, 2008

Wi-Fi Battery Life: UMA Wins Again

Last month PC Magazine reviewed the RIM Blackberry 8820. The review was quite positive, but one thing which really jumped out at me was this paragraph (second to last in the article):

One area where the 8820 really excels is in endurance; it beats the Curve 8320, although the 8320's performance isn't shabby. On a cellular talk time rundown test, the 8820 lasted 11 hours and 29 minutes with the Wi-Fi and Bluetooth radios turned off. Over UMA and Wi-Fi, the phone ran for almost 14 hours on the same test. If you're tired of your cell phone's short battery life, this device should be on your short list.

Or as they state in the article:

  • Continuous talk time (cellular): 11 hours 29 minutes
  • Continuous talk time (Wi-Fi): 13 hours 55 minutes

An all too common complain about dual mode phones is that Wi-Fi = poor battery life. Yet in PC Magazine’s own test, talking over Wi-Fi/UMA resulted in a 20% improvement in talk time/performance.

The evidence continues to mount that those issues are a thing of the past. Companies that are serious about Wi-Fi in devices are optimizing the performance to meet and many times exceed the performance of GSM only.

Thursday, May 15, 2008

Sorry Sprint

A very interesting opinion was posted to the GLG site the other day. Samual Greenholtz with Telecom Pragmatics opines that Sprint’s first choice for its home zone service was a dual-mode CDMA/Wi-Fi product. But lacking a DMH standard for CDMA networks, they were forced to settle for their second choice technology: femtocells.

With that, I say “Sorry Sprint”. It’s well known that there is no UMA/GAN for CDMA networks. With a 3GPP2 version of GAN, Sprint would have been free to choose dual-mode handsets, femtocells, terminal adaptors or even softmobile clients to run off their mobile network.

Is there an opportunity here?

Another fixed line operator drops mobile

Yesterday, the Embarq CFO said that the company may drop its wireless service in 2009, handing subscribers back to its MVNO partner Sprint.

Embarq is the spin-out of Sprint’s original fixed line business. As part of the deal, Embarq developed an MVNO relationship with its former parent.

Embarq was one of the first to develop a dual-mode CDMA/Wi-Fi service. The service was announced by former FMC technology provider NewStep Networks.

In the article, Embarq said their original target was for 1 million mobile subscribers, but had achieved just over 100,000. I can only imagine what fraction of those subscribers actually chose the NewStep/FMC service. Suffice it to say, it’s hard for fixed operators to sell mobile services in general, let alone dual-mode services.

I have written in the past about the problems with fixed line operators developing dual-mode services. The problems aren’t technical. It’s possible to make a phone hand-over between fixed and mobile networks.

The problem is that dual-mode services are fundamentally about Fixed-to-Mobile Substitution (FMS). Yet that’s exactly the opposite of what a fixed operator wants. Fixed operators need MFS solutions, or a way to put mobile minutes back onto the fixed network. That is contrary to what consumers expect today.

Dual-mode services from fixed operators are always going to be challenging.

Note: I found a link to this article from another FMC company focused on fixed line operators. I think this company is actually gone now too.

Wednesday, May 14, 2008

A New Thought On Femtocell Pricing

This week, analyst Danny Briere with Telechoice wrote an interesting piece for Telephony Online. The article was titled a rather depressing “Carrier Femtocell Pricing Doomed?”

I don’t think so, and Mr. Briere offers some interesting thoughts on alternative methods of pricing femtocell services. He has two points which I’ll oversimplify here:

  • Separate the ‘coverage’ aspect of a femtocell from the ‘service’

The issue Mr. Briere has with Sprint’s Airave offer is that the consumer is required to purchase both ‘coverage’ and ‘service’ with the femtocell. A consumer wanting improved coverage must spend $50 and pay a recurring fee of $15/month. The same applies to a subscriber just interested in the flat rate calling plan. There’s no ability for Sprint to segment the subscriber benefit.

He contrasts this with T-Mobile’s Wi-Fi-based service where consumers can get ‘coverage’ by simply getting a dual-mode phone, no additional fees apply. Then if a consumer wants the flat rate calling ‘service’, they can spend an extra $10/month.

  • Don’t underestimate subscriber’s ability to pay for something they value (in this case, coverage).

I think the concept of offering the femtocell as a pure consumer product play is creative. If the consumer values coverage, they may be willing to pay to address this issue. The operator may choose to have the consumer pay full price for the femtocell, or elect to subsidize a portion of the femtocell for subscriber retention reasons. But for subscribers who are coverage challenged, this may work.

One could apply the handset subsidy approach. If you want to just by a handset, a consumer pays full price. But if you choose to sign up for a service plan and commitment, then the handset is deeply subsidized.

To be worked out is the secondary/after market usage of a femtocell. Will the consumer be able to use the femtocell with a new mobile provider? In the US, there is an immediate radio issue (GSM vs CDMA) which hampers the issue immediately.

The point is there are many ways to meet consumer need, and the femtocell market is just getting started.

Thursday, May 01, 2008

Fierce Names Top 5 'Converged' Devices

FierceWireless released their list of top ‘converged’ devices. By converged I think they meant dual-mode devices, as each of the five devices on the list had Wi-Fi.

The list was:

  1. BlackBerry 8820
  2. BlackBerry 8320
  3. HTC Mogul
  4. HTC Tilt 8925
  5. iPhone

Interestingly, two of the five are UMA-enabled. Given HTC is rumored to be bringing out UMA-enabled devices shortly, there’s a chance that next year’s list will be 4 out of 5 UMA-enabled.

As for the iPhone supporting UMA, it has been rumored in the past. But UMA in handsets is typically driven by operator requirements. Orange and Rogers both support dual-mode UMA service. Orange and Rogers also both sell the iPhone. Interesting…

PS – credit where credit is due: The image is from Gizmodo. I think choosing Mr. ROGERS to hold the iPhone is brilliant.

PPS – according to Wikipedia, the Mr. Rogers show was first developed in Toronto for CBC, making the reference doubly brilliant.

Friday, April 25, 2008

UMA+LTE: It's all good

Recently there has been a flurry of activity around the next generation Radio Access Network (RAN) technology known at LTE. LTE is the ‘all IP’ access network for mobile service providers. With very high throughput (>100mbps) and very low latency (targeting 5msec), LTE is designed to a be a true wireless broadband access network.

With that in mind, people have started questioning UMA’s role in an LTE environment. While there are a lot issues still in flux (including LTE itself), and much work still to be done, what is clear is that the core drivers behind UMA in a 2G or 3G environment still apply in LTE.

Some people simplistically view UMA as redundant in an LTE environment because they both ‘deliver services over an IP access network.’ This view completely misses the value of UMA in a Home Zone 2.0 (femtocell or dual-mode handset) service deployment.

Operator deploying Home Zone 2.0 services in a 2G or 3G network are doing so for three reasons:

  • Create service zone unique from the macro network with the goal of offering differentiated services/billing based on location.
  • Offload the macro RAN, especially for very high speed, media rich audio and video application.
  • Improve the performance, coverage and throughput rate for mobile data services when indoors/in the home zone.

These same service drivers apply directly, and in some cases are even more relevant, to an LTE RAN:

  • Create a unique service zone (still a competitive advantage)
  • Offload the macro RAN (definitely for the projected data rates)
  • Improve coverage/performance (certainly if LTE is at 2 gHz or higher)

As the market evolves, UMA will continue to evolve as well. Just as UMA started as a 2G technology and evolved to support the 3G/Iu interfaces, UMA will continue to evolve into key solution in an LTE-enabled network.

Thursday, April 24, 2008

Cisco to buy ip.Access? Better to wait...

The industry is buzzing today with the rumor that ip.Access has ‘won’ a contract with AT&T to supply femtocells. The reportedly $500,000,000 contract for 7,000,000 units gives you an ASP of $71.43/unit. Ouch.

What exactly did they win? The right to sell femtocells below cost to AT&T?

Frankly I think it's AT&T that is hoping Cisco buys ip.Access. At least Cisco can afford to lose money on every unit and ‘make it up in volume.’

The article notes that the contract calls for ip.Access to ‘eventually price the units at less than $100 apiece’. If half of the units are sold at $100 each, the other 50% need to be sold at $42.86 to get to an ASP of $71.43. Hummm… that’s probably why the article dryly notes the contract ‘could exceed $500m.’

My advice to Cisco: wait… buy ip.Access out of bankruptcy.

The best way to get costs down in the market: Open standards.