Amazon Tech Support

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

Wednesday, 26 October 2011

There needs to be an Alternative Communications Providers Association (ACPA or OTTA) to counterbalance the GSMA

Posted on 15:06 by Unknown
One of the speakers said something really profound at last week's Sonus Connexions event in Miami:

"Skype is now the world's biggest telco". It has more users than China Mobile has subscribers.

And one of the notable outputs from the Rich Communications summit in Munich this week has been the push by mobile operators and the GSMA for RCS-e to be embedded "natively" in mobile phones, so that "It's just there". The operators hope to use their purchasing leverage with the handset OEMs to encourage and cajole them into building RCS-e into the basic handset software/firmware stack - implicitly putting broader IMS capability in with it.

That got me thinking.

The GSMA talks incessantly about its 5 billion+ "community". Never mind the fact that it's no more a community than the 5 billion with electricity - or shoes, for that matter - it's a large number, irrelevant as it is. (And yes, riddled with errors because of multiple SIMs per person). One of the speakers at the event said this mean that RCS-e had the "potential" to reach 5 billion people in future.

I commented at the time that Facebook has similar potential, as it uses not just downloadable smartphone apps, but also Java ME, Facebook Zero (WAP) and even USSD menus. That takes it to a potential 5 billion user reach today, not at some indeterminate point in the future.

But thinking further - if the mobile operators can start trying to mandate "native" capabilities in devices, why can't Facebook as well? Or, indeed, its peers.

Let's imagine for a moment what an Alternative Communications Provider Association might look like, made up of the various non-MNO voice/video/messaging providers. You could even call it OTTA if you wanted a nice logo of an aquatic mammal.

We've got (roughly and non-comprehensively):

Service               Users
Facebook            800m 
QQ (China)         800m
Skype                  600m
MSN                   500m
Sina Weibo         250m
Twitter                200m
Yahoo IM            200m
Renren                 200m
LinkedIn              150m

Orkut                    60m
Nimbuzz               50m
RIM BBM           50m
Google+               50m
Kakao                   25m
Cyworld (Korea)  20m
Viber                     20m
WhatsApp             20m

And then there's Apple's Facetime and iMessage, Google Voice, Kik, enterprise VoIP from Cisco and Avaya, IBM SameTime and many others. So, give or take, about 4.5 billion users collectively. You could also add in various providers of webmail for another 3 billion or so as well. Potentially, you could add in the telco-OTT operations like ON, Comoyo, Bobsled and O2 Connect as well. And yes, there's a lot of overlap in terms of the user base - but then that's also true (albeit to a lesser degree) of SIMs.

So now let's consider what specifications and other activities that ACPA / OTTA could start doing, if it acted collectively like the GSMA. (Obviously with appropriate anti-trust safeguards).

- Define handset standards that give equal priority to 3rd party communications services as the "official" MNO ones
- Define mechanisms that ensure that users can easily install - AND delete - any handset communications apps, including SMS, RCS etc.
- Specify multiple identity and authentication methods for services (leaving the SIM for network registration though, for now).
- Develop an equivalent to the GSMA IPX for interchange / backbone services
- Define methods for VoIP / social network portability
- Act for collective lobbying vs. regulators and governments on issues like Net Neutrality, termination regimes and structural separation
- Examine business models for monetising MNOs that currently deliver their services to users "for free", exploiting their R&D and data centre assets. (Who wants to be a dumb data centre, working equally with all networks?). For example, rev-shares on data roaming fees, which aren't even based on the billing operator's network assets.
- Market the benefits of unlocked "vanilla" handsets without operators' software add-ons
- Develop a shared approach to emergency calls / lawful intercept
- Work with banks or credit organisations to provide alternative sources of handset subsidy/loan
- Defining ways for multiple comms apps to "peacefully coexist" on handsets without software conflicts
- Examine ways to minimise battery drain, for example by using shared notification systems
- Work with network equipment & IT infrastructure providers to develop optimised hardware for data centres, private overlay networks etc

In a way, it surprises me that no such grouping exists already. For all their competitive animosity, I can't believe that Microsoft, Apple, Google and Facebook (and maybe QQ as an outsider) can't work together as effectively as the squabbling telco world - and probably make decisions and take action an order of magnitude faster. Perhaps there have already been secret discussions I'm not aware of, and they concluded that it wasn't necessary given the companies are still ascendant.

But given that the legacy telcos have failed to change their ridiculous "them and us" stance versus their newer peers, it is perhaps now appropriate for these maturing organisations to work to their mutual benefit against a common front.

This is just a starting point - I've literally just thought of this in the last hour or so.

Needless to say, if any of the organisations mentioned would like some analytical insight into this concept, I'd be delighted to assist in any way possible. You can contact me via @disruptivedean or information AT disruptive-analysis DOT com


Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home
View mobile version

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • 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...
  • Apple, embedded SIMs, NFC and mobile payments - some speculation
    I wonder if I've just managed to join up the dots on something rather important: - Recent reports suggest that Apple is intending to use...
  • 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...
  • Is the MID a market?
    MIDs (Mobile Internet Devices) are being pushed by some notebook OEMs and silicon suppliers as the next big convergent handheld category. I...
  • "You can't use my eyeballs for free"
    Let's look forward 10 years. We've all got augmented reality browsers on our handsets, or perhaps our 4G-connected sunglasses. They ...
  • Mobile traffic management - the Inter-technology war begins
    I've been following the proliferation of mobile broadband traffic management technologies for some considerable time now, having publish...
  • 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...
  • 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...

Blog Archive

  • ►  2013 (31)
    • ►  October (2)
    • ►  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)
      • Telcos will find that API payments are a two-way s...
      • There needs to be an Alternative Communications Pr...
      • Implementing native RCSe in devices brings operati...
      • Next few months are do-or-die (or die again) for R...
      • Musings on my next personal phone & contract
      • WiFi neutrality vs. the OMA
      • My suspicions on iPhone delays - chipset integrati...
      • 3GPP gets serious about the Future of Voice beyond...
    • ►  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