Amazon Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Wednesday, 31 March 2010

The dangers of over-reliance on simplistic metrics

Posted on 23:19 by Unknown
I wrote yesterday about the decreasing relevance of "$ per GB" as a yardstick for revenues or costs in mobile broadband.

Thinking about it, I reckon it's symptomatic of an industry that tends to live by snappy, marketing-friendly soundbites that obscure underlying complexities.

Simple messages are great for headlines, but can lead to wrong decisions if they become too entrenched.

A classic pair of errors in mobile has been the unthinking over-use of two basic metrics:

- Number of subscribers
- ARPU

Subscriber numbers have been simple to measure - largely because they map nicely to SIM card MSISDNs (a phone number to most of us). While they're easy to count, they don't really give a good view of either the actual or potential base of customers. Some people have multiple SIMs, some are shared, while an increasing % go into machines rather than phones. In fact, the whole terminology has skewed business models towards subscription-based types - while non-subscription models (eg transactional) have been downplayed or totally eschewed.

Almost no service business should rely totally on subscription models. Yes, it's a useful *segment* and trends are useful indicators, but it shouldn't be viewed as a pivotal metric.

Worse still is ARPU. More accurately, it's Average Revenue per Subscription, not Per User. Ironically, if it were used properly, it would be more useful.

The fact that I have a £40 per month phone, plus a £15 per month 3G dongle (from a different operator) makes me a £55 a month mobile user. Describing me as two £27 per month subs on average doesn't really help anyone to understand their business.

ARPU is inherently biased towards operators giving large subsidies, then recouped as "revenue" over the contract. Yes, it's possible to do some maths with (ARPU minus acquisition/retention costs) but there's still often too much focus on the headlines.

I remember that 3UK always used to trumpet its high ARPU. Until it realised that this was simply because it didn't *have* any low-tier packages or prepay, so obviously the average was going to look high. Nowadays it has realised how much money it was leaving on the table, and has targeted those segments aggressively, and is about to reach profitability (finally), largely thanks to *lower* ARPU.

A classic example of ARPU-blindness has been the reticence to focus too heavily on M2M services. "What, an extra 10 million subscribers on $5 per month? What will that do to our figures? What will our investors think?" . "But they're vending machines and remote utility meters. They hardly use the network. We'll make $4 on each in profit margin"......

There have been plenty of suggestions about using Average Margin per Subscriber/User and so forth - and certainly, most operators' internal management teams are rather more sophisticated about financial analysis these days.

But nevertheless, the ghost of ARPU lives on. While it might be largely discredited by those who really care and play with spreadsheets deep in the strategy department, it is still measured and watched by observers - and used as a tool by vendors in their marketing. It hasn't really gone away.

Its influence remains disproportionately pervasive.

Another example is handset shipments, which lumps together a $15 GSM phone on an Asian market stall, with a $5000 Vertu in a Dubai shopping mall. There's still a regular refrain that Apple is irrelevant because it ships tens of millions of devices per year, compared to Nokia's half a billion. Only rarely is it mentioned that Nokia's average selling price is €63 while Apple's is perhaps eight times that figure. Or that Apple and RIM account for a hugely disproportionate % of handset industry margins.

It's like claiming that Honda is more important than Toyota, because it sells 13m vehicles a year against 7m. Let's ignore the fact that 10m of them are motobikes. Or that Giant is in the top 5 vehicle manufacturers. Never heard of them? I'm not surprised, as they make bicycles rather than cars - but hey, they all have wheels, yes?

To sum up - raw, headline numbers rarely tell the whole story. Over-focus on them can actually damage a business, and even where management "understands" this, it's still possible to be subconciously swayed.

As I mentioned yesterday, the next oversimplified metric to hit the headlines is "$ per GB". My recommendation is to take it with a pinch of salt - chasing that figure either in terms of revenue or capex/opex costs is likely to be a mistake.

Remember, the best-value way of transporting data, if you just used $ per GB as a metric, would be to drive a truck full of flash memory from A to B. The latency is pretty lousy, though.

(But if someone would like to pay me at 1 cent per GB, for a network that gets mobile data around the UK at a terabit per sec, please get in touch. I reckon a guy on $20 bike from Giant can easily a petabyte of memory cards....)
Read More
Posted in | No comments

Mobile broadband problems - looking beyond the "obvious culprits"

Posted on 06:12 by Unknown
I've written a few times in the past about the "capacity crunch" for mobile broadband, as well as the potential for offloading traffic or policy-managing the network to prioritise certain users or data types.

More recently, I've discussed the role of signalling as an important factor in driving network congestion, especially from smartphones.

But there is a fair amount of uninformed comment about what's causing the problems - it "must" be laptop users downloading HD video or doing P2P filesharing over their 3G dongles, or it "must" be iPhone users using Google Maps and Facebook.

My view is that these over-simplistic analyses are leading to knee-jerk reactions around capacity upgrades, or stringent policy-management and traffic-shaping installations. Many vendors don't want to (or can't) give a fully-detailed picture of what really causes problems for the network and user experience.

It is in many suppliers' interests to market a neat single-cause and single-solution message - "You need to upgrade to LTE to add more capacity"; "You need PCRFs and charging solutions to limit video"; "You need to upgrade your GGSNs to really big routers" and so on.

The truth is rather more complex. Different situations cause different problems, needing different solutions. Smartphone chipsets playing fast-and-loose with radio standards may cause RNCs to get blocked with signalling traffic. Clusters of users at a new college might overload the local cell's backhaul. A faulty or low-capacity DNS server might limit users' speed of accessing websites. And so on.

Or, as many parts of London are experiencing today, a fire at a BT office might knock out half the local exchanges' ADSL and also the leased-line connections to a bunch of cell towers.

Now, in the long run there certainly will be a need to carefully husband the finite amount of radio resources deployed for mobile broadband. My order-of-magnitude estimates suggest that the macrocellular environment (across all operators, with the latest technology) will struggle to exceed a total of maybe 3Gbit/s per square kilometre, even on a 10-year view. So offload to pico / femto / WiFi will certainly be needed.

But in the meantime, I'm moving to a view that Stage 1 for most operators involves getting a better insight into exactly what is going on with their mobile data networks. Who is using what capacity, in which place, with which device, for how long? And exactly what problems are they - or the network - experiencing?

In recent weeks I've spoken to three suppliers of products that try to analyse the "root cause" ofmobile data congestion [Velocent, Compuware and Theta] and I'm starting to hear a consistent story that "there's more than meets the eye" with regard to network pains.

Some of the outputs can be eye-opening. It may be that a lot of customer complaints about poor data speeds can be traced back to a single cell or aggregation box that is mis-configured. It could be that a particular group of devices are experiencing unusually high problem rates, that may be due to a fault in the protocol stack. It might be that viruses (or anti-virus updates) are responsible for problems. Or it might just be that all the iPhone users are using YouTube too much.

One thing is for certain - the yardstick of "Dollars per gigabyte downloaded" is an extremely blunt tool to measure the profitability of mobile broadband, especially when opex costs around support and retention are included in the equation. There's no value in having a blazing-fast and ultra-cheap network, if users end up spending an extra 4 hours on the phone to customer care, complaining that they can't get access because of flaky software.

Note: The new Disruptive Analysis / Telco 2.0 report on Broadband Business Models is now available. Please email information AT disruptive-analysis DOT com for details.
Read More
Posted in | No comments

Tuesday, 30 March 2010

LTE and offload - a few random questions

Posted on 07:04 by Unknown
A quick series of observations:

1) It is highly likely that LTE will have to be provided (at least in part) by femtocells and/or WiFi access points, rather than being solely transmitted via the macro network. This will be for coverage reasons, especially for 2.6GHz, but also because of the limits of capacity which will be quickly reached in some areas.

2) Given rising traffic volumes, there will also be a strong desire to offload bulk IP traffic direct to the Internet close to the edge of the network, rather than backhauling it all through to the operator core & then out again

3) Voice will in some packetised form on LTE, whether it's VoLTE or VoLGA or Skype or CSFB.

So... there will need to be a mechanism to send VoIP to the operator core, but dump bulk web traffic locally. I guess that could be achieved by using separate APNs (or whatever they're called in LTE-speak).

Or, will it need the new "Selective IP Traffic Offload" standard being worked on by 3GPP?

Or, could you use some sort of dual-radio solution in handsets, sending certain traffic over the macro LTE network (or HSPA), while sending low-value data via WiFi / femto?

Separately... presumably this also means than any VoIP that *does* go via an offload path (femto / WiFi) will need to be tunnelled back to the operator core via some sort of VPN.

So potentially we may see some LTE phones using CS-Fallback over a GAN-type tunnel.....
Read More
Posted in | No comments

Monday, 29 March 2010

Hopefully, we'll be rid of the Twitter obsession soon

Posted on 06:44 by Unknown
I've been a long-term Twitter skeptic.

I think it's value-negative, and of total irrelevance to anyone outside an unholy alliance of geeks, narcissists (politicians, celebrities etc), marketeers, "media" and their drone-like followers. It's mostly used by lazy journalists and broadcasters, as far as I can see.

I highlighted it as one of my "zeros" in my predictions for 2010.

So, it's edifying to see that the "growth" stats are proving my point for me.

The appearance of incredibly annoying floating Twitter buttons on some websites is a sign of desperation - and is hugely counter-productive, as visual spam of that sort is a great way to alienate people.

About time to swap the silly bird logo for a dodo, methinks.

Extinction beckons.
Read More
Posted in | No comments

Network policy management and "corner cases"

Posted on 03:09 by Unknown
I've been speaking to a lot of people about policy management recently, fitting in with the work I'm doing on mobile broadband traffic management, as well as the Business Models aspect of my newly published report on Broadband Access for Telco 2.0.

A lot of what I hear makes sense, at least at a superficial level. Certainly, I can see the argument for using PCRFs to enable innovative tariffing plans, such as offering users higher maximum speeds at different times of day, or using DPI or smarter GGSNs to limit access by children to undesirable sites.

But there's a paradox I see on the horizon. In the past, telcos (fixed and mobile) have been pretty obsessed with corner-cases. "What happens if a user tries to set up a 3-way call while they're switching between cells?", "What happens to calling-line ID when I'm roaming?" and so on. Sometimes this is because of regulatory requirements, sometimes it's because they're worried about the impact on legacy systems not being supported - and sometimes it just seems to be preciousness about some minor complementary service that nobody really cares about.

So what happens with *data* policy management and corner cases? What happens if I'm roaming and the local operator's policy conflicts with my home operator's? Do I get a subset or a superset? The lowest common denominator, or some sort of transparency? Imagine my home operator allows VoIP on its mobile broadband, but limits YouTube viewing to 100MB a month. But the visited network doesn't allow VoIP for its local customers, but also doesn't have the ability to discriminate video traffic - or, perhaps, applies some sort of compression via a proxy. Sure, everything might be backhauled via my home network.... or it might be offloaded locally.

[Side question - what happens to international data roaming traffic on a visited operator that does WiFi offload, provided by a separate managed offload operator?]

In a nutshell, I guess this boils down to "Policy Interoperability". And a need for policy IOT testing, on an ongoing basis. I strongly suspect this won't be as easy an many think.

Whether the "corner case" problems impact the overall use of policy management will probably depend on hard problems around with local regulations and laws, I suspect. But as a customer, will I really be happy with having the most stringent superset of policies applied, if there are multiple operators involved in my providing my connectivity?
Read More
Posted in | No comments

Friday, 26 March 2010

Nokia acquisition of Novarra - fragmentation of optimisation?

Posted on 08:06 by Unknown
Very interesting to see Nokia's acquisition of web/video optimisation & transcoding vendor Novarra, which has been quite widely deployed in operators looking to reduce data traffic sent over mobile networks.

The fascinating thing for me is that it's being pitched as a way to optimise web browsing on low-end Series 40 devices - in other words, it's *not* primarily about reduction in outright traffic levels for operators, which are dominated by laptops & top-end smartphones.

The other stand-out is that the acquisition is by *Nokia* and not NSN.

I've been giving a lot of thought recently to various ways to optimise / compress / offload / policy-manage mobile broadband networks, trying to work out a way of reconciling the different options available to operators.

As part of this, I've been looking at the approaches to transcoding and proxying of web traffic - either in centralised boxes from Novarra or peers like ByteMobile and Flash networks - or by specific client/server implementations like RIM's NOC for BlackBerry Internet traffic, or the Opera Mini platform.

My view is that there will be no "one size fits all" approach to traffic management, and that operators will have to be smart about treating different use cases in different ways. This is less about treating traffic differently on a per-application basis, and more about device/business model/customer scenario segmentation.

My current thinking is that laptop traffic will probably be offloaded close to the edge of the network, especially with WiFi, or femtocells once it's easier to use techniques like SIPTO or Direct Tunnel to avoid congesting the mobile core with traffic that is 99.99% destined for the wider Internet.

Smartphone traffic will be part-offloaded, and part-optimised or policy-planned.

And, based on this acquisition, it increasingly looks like featurephone traffic will be optimised at the application level.

In addition, there are likely to be a range of general capacity improvements and efficiency gains in the RAN, backhaul and elsewhere - dealing both with total traffic volumes and signalling load.

More on this topic to come...
Read More
Posted in | No comments

Non-user revenue models for broadband - excellent example from Vodafone

Posted on 03:46 by Unknown
One of the major themes I explore in the new Telco 2.0 / Disruptive Analysis report on broadband is that of "non-user revenues", otherwise known as two-sided business models.

The basic concept behind a 2SBM is for an operator (fixed or mobile) to use its network and IT platform to derive revenues directly from end-users, and also from various "upstream" companies like advertisers, governments, content providers, application developers and so on.

The idea is that retail broadband revenues will start to flatten - and must be incremented with new advanced wholesale propositions. Some of these will be evolutions of current telco-to-telco wholesale (roaming, interconnect, MVNOs, dark fibre and so on), while others will evolve sale of broadband capacity to "non-users". The Amazon Kindle is a good example of this - it's Amazon paying for the connectivity for book downloads, not the end user through a separate subscription.

One particular opportunity identified in the report is for governments to pay for broadband services (either outright, or for specific capacity / capabilities) on behalf of their citizens. It might be that data connections are bundled into an e-Healthcare service, or perhaps in the context of Smart Grids.

Or, as Vodafone has illustrated this morning, a government agency like a local council or development authority might choose to sponsor fixed or mobile broadband connections for those beyond the "digital divide". In this example, it's unclear whether Voda is providing fully "open Internet" broadband, or a more restricted service just providing access to educational websites. Either way, it's a perfect example of "non-user revenue streams" and highlights the power of two-sided models to add incremental opportunities to an operator's existing maturing propositions.

This type of sponsored broadband is just one of a class of "new wholesale" approaches to selling access. Telco 2.0 / Disruptive Analysis has developed a unique forecast model which suggests that these types of innovative propositions could ultimately account for over 15% of the total broadband access market value globally.

The full dataset, analysis and modelling methodology is featured in the new Fixed & Mobile Broadband Business Models Report, which is now available for purchase.

To inquire, please contact please contact Disruptive Analysis
Read More
Posted in | No comments
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)

Popular Posts

  • New Cisco VNI traffic report out
    One of the broadband industry's "bibles" has been published in a 2010 edition . Cisco's "Visual Networking Index...
  • Quick musing on Cloud Computing
    I just heard the phrase "Everything as a Service" during a presentation on Cloud, SaaS and other forms of managed service offering...
  • Pre-MWC notes for analyst relations staff
    OK, it's the time of the year when I get bombarded by emails and phone calls from a million people inviting me to briefings and similar ...
  • Mobile operators' future voice strategies decoded
    Apologies in advance, but this blog post is deliberately a bit of a tease. I'm not going to spell out the answer here, as it's too v...
  • Hosted mobile services in the recession - Caveat Emptor
    I used to work as an equity analyst at an investment bank back in 2000-2001. I remember an unending stream of first generation Application S...
  • Mobile websites
    I am getting increasingly annoyed with mobile versions of websites. I really wish there was a way of configuring handset browsers (I'm ...
  • Challenges in measuring offload volumes
    I suspect we're going to get bombarded with statistics in the next year, along the lines of "Operator X deployed Vendor Y's off...
  • Device-specific data plans and policy management
    There is currently a clear shift among some operators towards device-specific data plans. In many ways, this is not new – 3G modem data fo...
  • Telcos = Google advert affiliates?
    I'm at the IMS conference in Barcelona today. My bulletproof vest has already protected me from a couple of shots from large vendors. It...
  • Mobile broadband traffic - be careful about language
    I am currently writing a Disruptive Analysis research report on mobile broadband traffic management strategies. I have discussed various c...

Blog Archive

  • ▼  2013 (31)
    • ▼  October (2)
      • For telcos, IMS integration should only be a small...
      • Amazon's Mayday may signal its long-awaited WebRTC...
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (6)
    • ►  May (5)
    • ►  April (1)
    • ►  March (3)
    • ►  February (3)
    • ►  January (5)
  • ►  2012 (46)
    • ►  December (5)
    • ►  November (4)
    • ►  October (3)
    • ►  September (2)
    • ►  August (4)
    • ►  July (3)
    • ►  June (1)
    • ►  May (6)
    • ►  April (4)
    • ►  March (1)
    • ►  February (9)
    • ►  January (4)
  • ►  2011 (73)
    • ►  December (4)
    • ►  November (10)
    • ►  October (8)
    • ►  September (6)
    • ►  August (3)
    • ►  July (5)
    • ►  June (7)
    • ►  May (9)
    • ►  April (4)
    • ►  March (7)
    • ►  February (6)
    • ►  January (4)
  • ►  2010 (130)
    • ►  December (4)
    • ►  November (10)
    • ►  October (10)
    • ►  September (6)
    • ►  August (9)
    • ►  July (7)
    • ►  June (19)
    • ►  May (19)
    • ►  April (11)
    • ►  March (18)
    • ►  February (7)
    • ►  January (10)
  • ►  2009 (126)
    • ►  December (4)
    • ►  November (14)
    • ►  October (9)
    • ►  September (8)
    • ►  August (9)
    • ►  July (10)
    • ►  June (21)
    • ►  May (14)
    • ►  April (2)
    • ►  March (11)
    • ►  February (15)
    • ►  January (9)
  • ►  2008 (94)
    • ►  December (24)
    • ►  November (26)
    • ►  October (25)
    • ►  September (19)
Powered by Blogger.

About Me

Unknown
View my complete profile