Speaking Engagements & Private Workshops - Get Dean Bubley to present or chair your event

Need an experienced, provocative & influential telecoms keynote speaker, moderator/chair or workshop facilitator?
To see recent presentations, and discuss Dean Bubley's appearance at a specific event, click here

Sunday, November 16, 2014

Retiring the term “Telco-OTT”. "Digital services" is useless too. Long live “Telco-Apps”



I’ve long railed against the telecoms industry term “OTT”, standing for “over-the-top”. It is pointlessly divisive and arbitrary, and often said in a pejorative fashion, by people who don’t understand what it means and implies. On Twitter, I’ve often called for people using the term OTT in a serious way to be summarily fired for gross incompetence by their employers. (Given that many of the worst offenders are themselves CEOs, this is impractical, unfortunately). I generally prefix it with “so-called”, or use quote-marks, to give it the disrespect it deserves.

“OTT” is used to describe a subset of Internet-based services or applications, which are thought to compete with traditional telecoms services like telephony and SMS, or hoped-for future services, such as IM or video-calling. Skype, Whatsapp, LINE and SnapChat are examples of applications which have earned the despised “OTT” tag, usually uttered by people whose PR and legal departments told them not use stronger epithets. 

None of those companies call themselves "OTT players" any more than a washing-machine manufacturer considers themselves as running over-the-top of the electricity supply. They are simply web or Internet companies, offering communication apps or services. Call them CSPs or some other acronym, if you must. In future, as "OTT" communications capabilities get absorbed into most applications and websites as features, with WebRTC or other APIs, it will be a fairly pointless distinction anyway.

There is also a considerably different interpretation in the content space, where “OTT video” is used to describe channels or streaming platforms such as Hulu and NetFlix or BBC iPlayer, which go direct-to-customer and don’t need to work with normal digital TV aggregators such as cable MSOs or IPTV platforms. There seems to be less animosity in that area among telcos, perhaps because most don't have legacy businesses there.

Some other Internet companies often get lumped into the “OTT” category too, even though their main offerings don’t overlap with typical telecoms service domains. Facebook and Google, for example, often get called OTTs simply because they are seen as a strategic threat to the telecoms industry, so it makes sense to demonise and caricature them as “the other”. Web search, social networking and online advertising are not traditional telecom businesses - they are new and purely Internet-based.

Most other Internet services and applications don’t attract the same opprobrium. Nobody calls Salesforce or Wikipedia or Tinder or a Cisco IP-PBXs & WebEx an “OTT service”, even though they also “use our pipes for free”.

I’ve made the point in the past that if Internet services are “over the top”, then surely telecoms networks are better-called “under the floor”, as that’s where the pipes and plumbing goes. Yet oddly enough, I don’t encounter many telcos proudly declaiming their “UTF” status.

In a nutshell, "OTT" is simply a duplicitous, mealy-mouthed term for "bits of the Internet we don't like". "Dumb pipe" is a dumb term too - networks are neither pipes nor stupid. What "dumb pipe" means, translated from telco-ese, is "please tax the clever people for us, or let us do it instead".

I coined the term “Telco-OTT” in 2011, to describe the growing phenomenon of telecom operators launching their own services that use the public Internet as a platform, rather than their own managed network infrastructure. As well as grabbing attention, it was intended to highlight the hypocrisy - and sometimes outright lies - of many industry executive and observers (and sometimes regulators) when it comes to the Internet

Now, following a tweet from Chad Hart, I've decided to take his advice and kill the term.

Almost all Telcos have so-called OTT offerings, whether in the field of voice/messaging, cloud offers, content/video or even home-automation. These span both fixed and mobile networks, and “pure OTT” standalone applications and “extension” models linked to existing on-net services. Some are in-house developed, others created through partnerships. I identified well over 100 such services in 2011, and there are probably 200+ today.

And of course, every single telecoms company on the planet has its own Internet-based website, gladly using other telcos’ networks as sales, marketing and support channels for both their existing customers, and their rivals' subscribers they hope will switch. Vodafone.com, att.com and kddi.com are all “OTTs” in the broad sense of the word. Of course, all the industry associations and regulators happily make use of the public Internet as well, at the same time as some are trying to limit its reach and scope.

Curiously, none of these telco-run Internet and app properties have ever openly suggested paying for QoS on their rivals’ infrastructure, or sponsoring their users’ data consumption. Surely, given Telefonica’s distaste of OTTs (”It's not a level playing field"), it would have proactively sought to recompense its rivals forced to carry traffic from Terra, Tuenti or TuGo, as a good example? One would have also thought that GSMA’s or ETNO’s webmasters would have long ago volunteered to pay for visitors’ traffic, to demonstrate “innovative” broadband business models? Or perhaps Verizon would have sought to accelerate user transactions on Verizon.com, when viewed from an AT&T broadband connection, and pleaded with the FCC to allow it to buy a “fast lane”? 

Oddly, all the CEOs conveniently overlook their own Internet businesses, when it comes to grandstanding in front the FCC or EU or investors, about Net Neutrality and similar issues. 

The bottom-line: ALL telcos are “OTTs”. All of them exploit the Internet, and would complain bitterly if they were prevented from doing so. They’re not as successful in some areas as their rivals, but that’s a separate discussion.

When telecom industry representatives clamour about the lack of “a level playing field”, most are either ignorant, disingenuous, or unwilling to confront the organisational and cultural blockages in their own businesses. Plenty of telcos do launch run “pure OTT” apps and services, in exactly the same fashion as any other firm. That said, other telcos have limitations in areas such as user-data collection and exploitation, and I'd support broader equivalency of laws and rules there, versus Internet players.  It's up for discussion whether data privacy laws should be relaxed on telcos, or tightened on web firms.

Some also have actual – or merely perceived – regulatory hurdles on things like lawful intercept. But they have had 10 years to convince regulators and ministries to be more relaxed on communications areas outside of traditional telephony. Seriously, if an operator launches a karaoke app, are they expected to record hours of terrible singing, and metadata of the music tracks sung for the authorities? Instead, too many operators argue for new rules to be imposed on Internet companies, rather than arguing for relaxing rules on themselves.

The time has now come for me to retire the term "Telco-OTT". It is now in mainstream use, and various vendors and media outlets have come to embrace it more fully. The market has understood that telcos need to have web and mobile apps and services, decoupled from their own networks. WiFi-calling exploits third-party wireless connections. TV-anywhere apps use whatever networks are available. WebRTC services are quite clearly expected to be accessed from any Internet entry point. Many telco SaaS/cloud offers are accessible from anywhere. Numerous operators have VoIP apps intended for expats, travellers and the "diaspora" outside their home market, and away from their controlled and managed home networks.

Continuing with term Telco-OTT now just lends legitimacy to the unvarnished OTT label, and the phony war that is continually perpetuated by vendors and regulators in that regard. I want those that use the term OTT to be accused of blinkered "entitlement", as evidenced by ignorant comments about "OTT stealing revenues". Communications and content provision are open battlegrounds. Nobody is "entitled" to market share, revenues or profits for telecom and Internet services. They are up for competition. And if you offer Internet access to your customers, you should understand and accept the risk that Internet applications will be better/cheaper/cooler than on-net alternatives.

So what to call these services now that "Telco-OTT" is to be consigned to history?

Easy. Let's just call them "Telco Apps" (or Telco-Apps with a hyphen - I'm open to persuasion on the punctuation). Certain things may have to be called Telco Platforms or Telco Enablers, if they are thin delaminated Internet service "slices" rather than full applications.

I'm also calling time on "Digital Services". It's a stupid term as well. Apart from AM/FM radio, I can't think of any analogue communications services. They're all digital, as is the entirety of Internet & telecoms networking. As Alan Quayle often points out, "Digital" hasn't been a useful adjective since it was used to describe Casio watches in the 1970s, or perhaps the replacement of old phone exchanges in the 1980s. Today, "digital" is most often associated with techno-illiterate fools in the marketing and advertising industries, who talk about "digital marketing", or use cringeworthy phrases when you meet them like "Hi, I'm in digital".

So. "Telco-OTT" is dead, "OTT" is for telecom people who don't like the Internet but are too scared & hypocritical to say so as they use it too, and "Digital" is for people who haven't understood the last 50 years of technology. 

Internet companies make apps, websites & Internet services. Telcos exploiting the Internet do the same. Telcos are Internet companies. Call their Internet  activities Telco-Apps, if you need to distinguish them from network-integrated services - although even those will be extended over the Internet anyway. The Internet - and the Web & Apps - has won.

Oh, and make sure you understand the difference between the Internet and the Web, too. Or else, once again, you should be fired for incompetence.

Tuesday, November 11, 2014

5G standardisation requirement: The need to support multiple concurrent network service-providers


There are numerous 5G-requirements/use-cases documents being circulated by mobile vendors, industry bodies and governmental organisations. For example, 4G Americas recently put out a top-level white paper listing a variety of possible user- and network-functional options for consideration, based on the expected devices and user scenarios.

There are some very sensible conclusions – such as limiting the provision of complex mobility functions to those devices or contexts that actually need them. There is no point having complex, expensive and battery-consuming cellular mobility signalling protocols for IoT installations that are at fixed locations, for example. This type of context-smart design, built into the architecture upfront, could massively improve 5G efficiency and flexibility. This is a big shift from the one-size-fits-all approach seen in 3G and 4G design.

But, ultimately, many of the industry-issued papers are trying to reset the future balance of application/context-aware networks, vs. the growing trend towards network-aware applications. Coupled with hoped-for regulatory frameworks that allow more app-specific network operation, the intent is that mobile operators will retain a strategically important role with additional monetisation opportunities.

In an ideal world, both philosophies would co-exist. However, as the current concerns over net neutrality illustrate, there is considerable fear that network operators could abuse their position, especially in markets with limited access competition. There is a risk of oligopolistic operators demanding rents from application or content companies, which are both financially burdensome and act as a brake on innovation, by introducing extra business-process friction.

The huge success of the Internet model has largely been driven by the decoupling of application from network – and virtually no developers appear to wish to go back to the “bad old days” where they had to interact with the underlying infrastructure providers. Most would rather use a generic “vanilla” data connection. Perhaps others will emerge – especially in the IoT arena – that are prepared to pay for “priority” or “QoS”, but as yet there have been no enthusiastic potential customers. There is a notable absence of any lobbying group clamouring “please let us buy some extra QoS”, which suggests the entire concept is network-push rather than application-pull.

There are other stakeholders here too – notably end-users, and their employers, IoT infrastructure owners, families and other affiliated groups. They will wish 5G to be as responsive to their needs as possible – especially in offering flexibility of pricing/quality trade-offs. Furthermore, if networks are allowed to differentially treat (or even block) specific applications or content, then users will still want to be able to access those services through different channels instead.

Disruptive Analysis believes that a possible solution is to design 5G devices and networks with the explicit expectation that users should always have access to at least two completely independent network providers. This would allow users (or devices / OS’s acting as their agents) to arbitrage between different sources and styles of connectivity, as well as providing redundancy should one network experience a problem.

To an extent, this already happens. Most cellular 3G/4G devices also have user-controlled WiFi, which in many locations enables connectivity completely decoupled from the cellular operator’s control. In addition, short-range connections can be made over Bluetooth for certain use-cases, including device-to-device connections. And of course, there are some devices with dual SIMs or even dual radios. However, these are additions added by manufacturers, and work against the cellular industry’s polarised vision of “one device, one network operator”, rather than being designed-in as desirable models upfront.

It is imperative that the current level of user control over networking switching is maintained in the 5G era, and ideally extended considerably. Firstly, extreme care must be taken in any “multi-network” scenario to protect “seams”. There is a huge danger in trusting the concept of “seamlessness”, as often promoted by believers in carrier WiFi technologies like ANDSF, Hotspot 2.0 and Passpoint. While there are instances where automatic handover is useful, there must always remain a user-override and full visibility over which networks are used. This is especially true where one network is in unlicensed bands, as there will be a good chance that a cheaper/better/different network operator is available locally. This is often the case today with WiFi, where many locations are free at the point of use, and private access of utility WiFi (not “offload”) allows users to avoid using data plans, and perhaps avoid any onerous policy-management conditions their cellular provider imposes.

But ideally, this approach would go much further. Explicitly mandating devices to support at least two cellular network providers – where one might be virtual (e.g. with a Soft-SIM or second SIM or other network-authentication mechanism) would introduce extra competition, innovation capabilities and user/app choice at an architectural level. It would encourage networks to compete sincerely on quality and performance, as they would face easier switching. Applications and OS’s would be able to avoid “bad actor” rent-seeking operators by choosing an alternative path – and this in turn would make concepts such as prioritisation more palatable, as it would act to “keep the networks honest”. It would also make the distorting effects of handset subsidies much less tenable – which fits in with a broader move towards cellphone financing plans, rather than direct subsidy and locking.

A related approach is to make sure that device-to-device connections are decoupled from the cellular operator(s) entirely, and not locked-in to the user’s normal data plan. That way, users and their software agents will be able to “route around” over-restrictive or expensive operator controls, by using others’ connections instead. We already see this with portable-hotspot WiFi tethering, but more generalised and user-friendly forms of “social tethering” can be devised. It is quite plausible to imagine “sharing my connection with my Facebook friends”, or perhaps having separate, independent, D2D service providers.

Apple’s SIM card, with its selectable mobile networks, is a good step in the right direction here, but care must be taken to avoid anointing Apple or Google as another single point of network control as well.

A further possibility here is to apply strict Net Neutrality to just one of the connections. That way, the user always has open access to all legal apps and services via the public Internet, but the other connection(s) could support alternative business models, if they prove technically and commercially viable. Indeed, the user might choose to purchase both Internet and non-Internet service connections, and thus allow non-neutral connections to prove their “more innovation and investment” credentials over time.

Overall, 5G requirements and standards should support switchable, multi-network capabilities, using independent service providers, with at least one neutral Internet connection. By mandating this:

  • Users and applications can always exercise choice over network connections and pick “the best tool for the job at hand”
  • Network connections can offer optimisations for specific applications or contexts, potentially getting revenue premiums from end-users, or (conceivably) application providers.
  • Full and open Internet access is always available, but so are other potential “managed” services which can compete directly and fairly. 
  • Innovative solutions involving network bonding, roaming, D2D sharing and other models will be encouraged. We may see the emergence of new classes of secondary network service-providers.
  • WiFi or other unlicensed technologies remain valuable as an “arbitrage layer”. We may see the emergence of unlicensed-band LTE/5G networks run by third parties.
  • Regulators can manage to “square the circle” of guaranteeing both consumer choice, open Internet access and the potential for new mobile broadband business models. 
  • There can be good fits with new MVNO or liberalised-MNC models for network service provision.

All that said, it seems unlikely that the traditional mobile industry will suggest this approach itself, as the usual model tends to view lock-in as preferable to loyalty and choice. It will be important for regulators and other stakeholders (eg Apple which is now a member of NGMN) to push for multi-network capabilities to be recognised as a 5G requirement. This is a critical area, which seems to be overlooked at the moment. 5G needs not just “seams”, but “zips” that allow it to be more open, more versatile, and of greater benefit and value to the user.

Monday, November 10, 2014

Reality-check: some real stats on SMS and voice telephony usage trends

It's very easy to get caught up in "what's next". I spend a lot of time predicting the future of communications: apps/web-embedded voice and video (usually with WebRTC), new forms of enterprise collaboration & conferencing, Internet-based communications services (the ignorants in the industry still call them "OTTs" - they should be fired for incompetence) and so on.

But what is actually happening back in the real-world of good old phone calls and SMSs? We hear a lot about possible revenue declines (or revenue "stolen" by OTTs - ignoramuses again) as well as some bright spots like application-to-person messaging growing. But what about usage? While I disagree with the continued myopic focus on minutes and message volumes for the future, there is no doubting that those metrics still form the basis of many telecom industry mindsets.

I'm moderating a work-stream at TADSummit in Istanbul this week, about innovation in legacy services. While a lot of that concerns value-adds and APIs, some of it is going to look at innovative ways to encourage use of phone calls and SMS/MMS. 

So, bringing this to life a bit, I thought I'd do a quick scan of reported numbers by operators and regulators on what they're actually seeing in terms of usage. It should be noted that there's always definitional complexities here, so comparison between countries might not be perfect. There's some fuzziness in areas like corporate VoIP and SIP-trunking too. However, trends over time should be indicative. I'm also constrained by what I can find quickly & easily in English - which tends to push me towards European regulators, which generally have hard-working stats departments and accessible publications.

First, Ofcom in the UK. In a report published in August 2014
  • SMS/MMS volumes fell 24% in 2013 vs. 2012
  • Total outgoing fixed+mobile voice minutes fell by 3.9% in 2013. Total outgoing fixed voice call volumes fell by 10.7%, while mobile-originated minutes increased by 1.4%. (Interestingly, the mobile growth reversed an earlier decline - perhaps because of the growth of unlimited bundles)
  • 35% of UK adults used VoIP services in Q1 2014

In Spain:
  • Mobile voice minutes grew 11% in the year to Q2'2014. Again, there had been a fall in 2012-2013, but it is now rebounding. Fixed minutes decline 18%, however
  • SMS/MMS volumes in Q2'2014 were down 32% on the previous year, and are now 82% lower than at their peak in Q2'2007

In Germany
  • Fixed minutes declined 3% in 2013, and mobile grew by just 1%. Unlike most countries however, fixed usage is still about 60% higher than mobile, so it is past the point of overall "peak telephony"
  • SMS volumes fell by 37% in 2013 

In France
  • Overall telephony volumes fell 0.5% in Q2'2014 - with 8% growth in mobile not offsetting 11% falls in fixed calls.
  • SMS volumes actually grew 3% year-on-year, unlike most markets. This seems to reflect unlimited-text contract plans, as prepaid SMS volumes fell by 13%
In Sweden
  • Fixed minutes fell 13% & mobile-originated phone calls grew 4% in 2013
  • SMS volumes seem to have fallen in 2013 based on the chart in this report, but the text says the number increased by 13%.
 
In the US
  • Mobile voice minutes grew 14% in 2013
  • SMS volumes fell 13% in 2013
 
Other stats from a brief scan:
  • Canadian SMS/MMS volumes fell 4% in 2013
  • Chinese SMS volumes fell 18% in the period Jan-May 2014 vs. the previous year. Local mobile minutes grew 2.3% in that period, but at a substantially lower rate then the previous year
  • For China Mobile specifically, voice minutes grew 3% in 2013 although average use fell about 5%. SMS fell about 1.5%
  • NTT DoCoMo's overall mobile telephony minutes fell by 5% in FY2013
  • MTN Group (mostly active in Africa) had a 19% increase in voice minutes in 2013
  • SingTel telephony average MoU fell 6% in the year to March 2014, and SMS volume per-subscriber fell 30%
Overall, it seems pretty clear that there are multiple overlapping trends here, often driven by local competitive/pricing issues, as well as some cultural factors.

Firstly, it seems as though prepaid users (on pay-as-you-go plans) are much more likely to switch to Whatsapp, Skype and similar services to directly save money. This makes sense - if you pay per-message, there a direct and clear incentive to look for alternatives. Secondly, markets with all-inclusive telephony and messages seem to see volume usage improve. I suspect that this is partly due to pent-up demand from people who previously saw communications as expensive/variable-cost, and partly because when something is "free" people sometimes use more than they need, to perceive "value" (think buffet food...).

There is also...
...the chance that...
...SMS use switches to IM-style phrases...
:-)

... when users have unlimited messages, especially coupled to a good smartphone-type device with well-threaded and scrollable messaging interface and a decent keypad/touchscreen.

The aggregate numbers of fixed+mobile calls seem to demonstrate that many markets are now past "peak telephony", although they do not capture all the call-equivalent VoIP services around. There does appear to be a clear peak of calling volumes in affluent markets with a lot of post-paid contracts, however. Watching 2014 data will give an indication of whether people really are now "talking less", as certain use-cases get carved off by competing apps or complete substitutes.

The data sets we don't have are "usage by purpose". Are calls growing longer or shorter? To a greater number of contacts or fewer? From certain locations, or particular applications? For example, maybe there are more long calls (conferences, calls to family etc) but fewer B2C interactions or short "information calls" (eg arranging meetings). The lack of analytical insight into the voice telephony and SMS market make it hard to discern the inner details of the macroscopic trends.

Taking everything together, there appear to be a few general observations that can be made:
  • Not everyone is "bored" with telephony yet, especially in mobile. It's also still not that easy to replace with VoIP on smartphones.
  • SMS is facing both huge pricing pressure and people switching for both price and utility/function reasons. Volumes may not tell the whole story.
  • We have not yet seen a major shift toward in-app / in-context comms for voice communications.
  • More granular detail would be good, as otherwise important trends may get "lost in the noise" as pricing plan changes and other factors swamp and hide the initial stages of market evolution.

Thursday, November 06, 2014

The rise of the Independent Analyst / Expert - The telecoms industry needs industry research diversity

Tomorrow, I'm speaking at the inaugural "Great Telco Debate", run by Chris Lewis and Graham Wilde, and focusing on big-picture strategy issues for network operators. Also on the roster are various other long-time analysts and telecom industry commentators, including people I've known for years such as Pim Bilderbeek, Benoit Felten, Caroline Gabriel and my regular colleague / Twitter protagonist Martin Geddes. Next week, I'm running a track at Alan Quayle's TADSummit event, as well, which is aimed at creating a telecoms application development community.

The common theme here is independence. Chris, Martin, Alan, Caroline, Benoit, Pim and our peers have all worked for larger companies, typically analysis or consulting firms. We now run our own gigs, sometimes on our own, sometimes with partners or associates on a tactical basis. The Great Telco Debate features a host of independent analysts.

All of us are outspoken. In fact, Chris has called his conference company "Outspoken Events". All of us have a track record of being right - not always, not everywhere, but with a far better level of accuracy than many in the analyst industry. (Alan and Martin refuse to be called analysts, in fact - reflecting the dubious quality of some punditry in the telecoms sector).

Yet while organisations like the IIAR give some airtime to those of us lower down the size scale from the behemoths like Gartner and IDC, this recognition and engagement is patchy. Today I'm with Ericsson in Stockholm, with a number of other independent or small-firm peers. Despite my regular criticism of some technologies and strategies, it's a company that seems to appreciate a diversity of opinion. I was speaking at a Metaswitch customer event on Tuesday, another vendor which goes beyond the "big guys". Last week, I took part in some hosted events for groups of investors, organised by my financial-analyst telecom-sector counterparts at Barclays, who like bringing in experts on particular topical themes - in this case, I was discussing Apple's SIM card and its implications.

However, some other vendors, operators, regulators, enterprise end-users and broader ecosystem participants often do not look beyond the largest names, like Gartner, Forrester, IDC, Infonetics, 451/Yankee, Informa, ABI, AnalysysMason and their peers. While I'm not denigrating those companies, they tend to be less contrarian, less prone to risky visions that might prove wrong, and more willing to repeat industry "standard" mantras. Look back at years of hype and hockey-stick curves about RCS, mobile payments, mobile TV, the spurious tabloid-headline "battle vs. the OTTs" and so on. Identify the cheerleaders and the critics.

There have usually been a few small boys pointing out the naked emperors, but only rarely do they come from the large firms. On the other side, few of the bigger houses are adept at spotting or predicting the next thing either, as their structure makes it hard to spot cross-silo trends. My own claimed scalps have included highlighting the potential of small cells, WiFi offload, WebRTC and Telco-OTT before any other analyst. Martin Geddes and I championed "the future of voice" long before it became a trend.

The problem is that much of the "analyst" world is aimed at enterprise IT, where "influence" is all-important and easier to discern and isolate - much of it is directly about buyers choosing between vendors in specific categories of IT. The telecoms part of the analyst business is different, as the buyers are largely themselves in the technology industry as well. The role of standards - which may well be slow to evolve or plain wrongly-focused - is much higher in telecoms and networking, than in enterprise computing, applications and IT. Willingness to criticise standards, as well as companies, is important.

My view and aspiration (yes, it's self-serving too) is that companies in the telecoms industry should restrict their industry research budget to a maximum of 50% spend on the generic, "standardised" options from the big analyst houses. The rest - just as with telecoms R&D spend on new technologies, platforms and services - needs to go to innovative and disruptive thinkers, whether that's in the form of traditional research reports, or more workshop/brainstorm forms of engagement and provocation. 

You don't need to agree with us. And you might not want to use our output to give stats for your "rubber-stamp" internal business plans, or press releases hyping the next (failure-inevitable) thing. But you do need true independent thoughts to really catalyse change. Service innovation has largely failed in telecoms - it has been too "consensus" driven, too political, too slow and too rooted in engineering mentality rather than design. You don't often get told painful truths by the larger firms - they tend to pull their punches. "Anti-forecasting" what won't happen is as important as predicting what will - opportunity costs are increasing in the Internet era, so fruitless quests need to be spotted early and abandoned.

To spot opportunities, and painful problems, you need blue-sky thinking and contrarian musing, and practical, real-world advice on creating "the new". You need to spot the second-order problems before the first-order ones are fixed, or else you'll add in years of additional cycles and time-to-market. You need to know when to push back against industry organisations and standards bodies, and when to steer them in particular directions if possible. You need to make sure that your CEO avoids trite sound-bites and questionable statistics. You need someone who'll tell you that correlation and causation are different.

I list below some of the companies that fall into the independent analyst category. These are ones where I know the principles in real life or interact with them online. People who are opinionated, and able to challenge the status quo and consensus view. There are plenty more where I don't know the specific individuals. Some of them compete with me, but I think it's important to recognise the collective wisdom and insight of the independent analyst community, and so I'm happy to name-check them here. 

Indeed, some have very different viewpoints to mine as well - as many battles on Twitter or conference panel sessions will attest. But in my view, that's healthy - when was the last time you saw two representatives of big analyst firms have a proper gloves-off argument about who's right?

Alan Quayle Business & Service Development
bloggeek.me
BWCS
Chris Lewis Insight
Core Analysis
Diffraction Analysis
Geddes Consulting 
Jackdaw Research
Kelcor
Maravedis-Rethink
METISfiles
MZA
Nemertes Research 
PKE Consulting
Rewheel Research 
Strand Consult
Telco 2.0 / STL Partners
Telesperience 

And of course, there's my own company Disruptive Analysis (yes, I know the website is awful.... when I have time I'll sort it...). If you're reading this blog, you probably already know me - I'm called @disruptivedean for a reason.

The bottom line is this: the telecoms industry cannot afford just to read, or hear about, consensus views, from a handful of big firms saying much the same thing. Diversity of opinion, vision, concern and suggestion is paramount. Telcos, vendors and others all need a breadth of inputs. Assigning at least 50% of industry research budget to independent, flexible thinkers is a good metric to aim for, to help attain this. We may not have a collective voice or slick sales and marketing machines - but that's because we don't want to have to feed the machine with generic output.

Monday, October 27, 2014

Microsoft now definitely supporting ORTC / WebRTC

Big news today - Microsoft has officially confirmed that it will be implementing ORTC (Object Realtime Communications) in future versions of IE, and that it will be integrating it with Skype. It's not planning to support WebRTC 1.0 it appears, but that has been pretty clear for a long time. (At least, it's what I've assumed in my own forecasts anyway). ORTC has been labelled as WebRTC 1.1, although it's still not an "official" standard but a "community" enhancement.

Details are still only in outline. The most controversial aspect will be the support of H.264 video codec rather than VP8, although that's hardly surprising given that (a) there has been no agreement on mandatory codecs yet anyway, and (b) VP8 is obviously a very Google-centric technology. Given that Firefox is supporting both, and Apple is definitely an H.264 fan, some will find this annoying but hardly surprising.

My take has long been that a certain level of fragmentation is OK for most WebRTC use-cases and developers. It's a bit of a pain, but it's not the end of the world. Yes, there will be questionmarks about licensing / royalty fees, but if that's picked up by the browser supplier (or third parties like Cisco) that should be tractable. 

I'd expect most of the WebRTC cloud platform providers to support ORTC endpoints - which may mean that the cloud/gateway model of WebRTC gains even more traction vs. pure peer-to-peer use cases. (The cloud approach was growing anyway, as it's the main way to support WebRTC-type voice/video inside iOS and Android apps).

Frankly, the details are important but manageable. We can safely ignore the usual anti-Microsoft brigade's whining about this; Google has worked on the ORTC spec alongside Microsoft and Hookflash, and it is widely (albeit not universally) seen as a good approach, especially as WebRTC 1.0 uses an arcane approach called SDP (a legacy of SIP) to set up connections. 

There are still unanswered questions, which should hopefully get clarified in due course:
  • Will ORTC pop up in IE12 or IE13 first? Will it initially be launched in beta, and under what conditions?
  • Will ORTC support DataChannel properly?
  • What happens with Lync? How does that fit into the ORTC/IE landscape?
  • Might Microsoft support VP8 in a future release, anyway? Or does that depend on how the market evolves?
  • When will ORTC make its way into Windows Phone, and how?
  • Will Microsoft use its Azure cloud platform to offer WebRTC as some form of managed service to developers?
  • What toolkits and support will Microsoft offer to developers for ORTC?
  • Will we see WebRTC/ORTC support in Dynamics CRM, X-Box or other Microsoft properties?
  • Does this limit the scope for 3rd-party IE WebRTC plug-ins (eg Temasys') or does it legitimise them, as a way of getting RTC capability into IE11 and below?

The bottom line is that this is a good day for the "democratisation of voice and video communications" - one way or another, most browsers from mid-2015 onward will be able to support embedded communications directly into websites. Given the various cloud platforms and plug-ins available to smooth the path for developers, this is yet another sign that WebRTC (including ORTC) is proceeding along the right path.

I'm maintaining my view that there will be upwards of 2 billion active individual users of WebRTC by 2019 - a large proportion of the overall Internet and smartphone app user-base. For more details about use-cases, strategic analysis of Microsoft's & Apple's roles, see my full report published recently. Purchasing details are here.

Telecoms service innovation & differentiation - The car model-year approach

Over the next few weeks, I'm speaking at various conferences and events that cover telecom service innovation, including TADSummit and The Great Telco Debate. There will be considerable discussion on whether (and how) telecom operators can compete in the services domain, both amongst themselves and with Internet peers.

One of the things which baffles me about the telecom industry is the constant focus on standardised applications and services. There is no other industry in the world which has hundreds of companies manufacturing identical, commodity products which have zero shipping costs. Where the cost and time of developing, or deploying, those products is measured in years - and where the process involves immense bureaucracy and compromise.

For most telcos, differentiation manifests in network (eg coverage, speed), or billing/charging of standardised components, particularly access to the Internet. Fixed and cable operators often have a greater range of unique options, because they are able to negotiate content deals, and exploit set-top boxes as a delivery mechanism and anchor-point for innovation. 

Mobile operators, however, still mostly compete on minutes/messages/data allowances, perhaps with some bundled-in content, and partner WiFi access. Some plans might "innovate" with pricing for Internet access, using zero-rating. 

But few operators have interesting and unique "own brand" services in their bundles. Telefonica has TUGo, its WiFi-access OTT VoIP app. Orange has its Deezer music service and Libon messaging app. Verizon has cloud storage and exclusive sports content.

While these types of things are important, they are generally the product of huge development efforts - large teams of people, big budgets, and development cycles measured in years.

What is missing is any way of creating smaller, unique "surprise and delight" services for bundles, which could capture customers' imagination, and gain extra market share or customer loyalty. 

I don't see operators thinking along the lines of "What could we do with 5 people, 3 months and less than $1m budget?" or even "What could we do with 100 teams of 5 people, 3 months each and $100m budget?".

My view is that the telecoms industry needs to start acting more like the car industry. 

It's not a direct analogy, but consider that most cars have a "model year" approach. The 2015 version of the Ford Whatever is very similar to the 2014 one. But it's got new headlights, an extra airbag, redesigned mirrors, coloured stitching on the seats and 10 other tweaks. It's essentially the same price, but it's had various changes made. This differentiates it from older models (encouraging upgrades) and from its rivals. Hopefully, it will gain the manufacturer a few % points of extra market share, and a few % points of extra margin.

In that scenario, the product manager has to work out how to add in the maximum number of new features that make a difference to customers, for the minimum extra design and tooling cost. They probably have a long-list of possible options, which gets whittled down to those which offer the best "bang for the buck". Some will be big changes - a new engine, perhaps - while others will be minor cosmetic evolutions. There's also a longer 5-6 year cycle of doing complete re-designs. The next "G", to use a telecom analogy.

A similar approach should occur in telecoms. By all means work on big strategic service innovations like cloud storage offers. But telcos should also be looking at creating and deploying new and cool extra services rapidly with small teams, or with partners. They need good ways of "on-boarding" such services - and perhaps deploying them to existing customers in a similar fashion to a handset/browser OS update.

This should happen at the level of customer segments, in a similar fashion to the car industry. Telcos could have plans or sub-brands for specific groups: music-lovers, teenagers, sports fans, home-workers, seniors and so on. Or the segments could align with regions - a Londoner plan, perhaps - or techno-psychological, like an Early Adopter Plan.

Within each plan would be standardised elements like phone calls and SMS, plus an appropriately-dimensioned mobile data offering. Then would be bundled content or partner apps. But then there could be unique, cheaply-developed and unique services, that could evolve and be added-to over time.

So for example, the Music-Lovers' plan might include Spotify in year one, but then add in a karaoke app, plus a free introductory online music or DJing lesson & discounted extra tuition. Perhaps  there could be a competition among subscribers, so once a month one lucky winner got an hour-long videoconference with a pop star. 

The alert among my readers will have noted that all these involve two-way realtime communications of some sort - precisely the sorts of apps that WebRTC can help bring to reality in weeks, given a suitable team. But that's just one of the rapid service-development tools available - internal and external APIs from the telco platform or external providers, web and app development frameworks, cloud-based hosting and so forth will all help. 

The key thing here is the management and process. There needs to be acceptance that the 5-person team works on the basis of optimising the time/price/performance variables independently. They're not forced to use internal APIs, infrastructure and service elements, but can if they choose. There's no forced mandate to use QoS or interoperate with IMS or the phone system. They can use the telco infrastructure, or they can host on Amazon if it makes more sense and saves money and time. They are free to use open-source or rebrand 3rd-party white-label products, take a DevOps approach and launch fast with minimal corporate scrutiny. They can add in OTT-style messaging or voice/video. They can use carrier billing, credit card or even Bitcoin - whatever makes most sense. The management can force the internal legal team to have 24-hour turnarounds. There needs to be an acceptance of glitches, and a good way to update / bug-fix if necessary.

It becomes the brand manager or product manager's job to do the overall bundle "design", in a similar fashion to the 2015 model-year car. It has to be cohesive as a proposition, but it also has to launch on time and to cost. Things which are too complex, costly or delayed may get canned - but because there are a dozen other new things, that's no huge loss.

Here's a random selection of potential differentiating service offers which telcos could/should offer in some of their bundles. The challenge should be "How can we get one or more of these in the bundle in 3-6 months, from a standing start?"

  • Mobile Karaoke app (between subscribers, or mobile-to-desktop)
  • Realtime sentiment analysis of calls - is the person speaking really angry, or just pretending?
  • Crowdsourced WiFi help function - "who knows how to log onto the Internet at Starbucks on Baker Street?"
  • Swipe-to-screen, pushing a web-page or image from a phone to the user's TV
  • A fan app, allowing people liking the same band or movie to send messages to each other, or set up a call
  • A concierge app for hoteliers to suggest visitors download, including zero-rated or sponsored roaming calls to the hotel guest-services desk
None of the above are "scientific". They're all just things I've thought up in a few minutes in a cafe. But telcos ought to be able to come up with 100 of these, which map to their market and customer base (using, ahem, external consultants if needed), and filter them quickly down to 10 or 20 of the most attractive, relevant, and easy-to-implement.

It is this type of grass-roots service innovation process that will make a difference - not years-long industry industry initiatives to get to a clunky lowest-common denominator that nobody will use. But it will require a software mindset, a good platform for on-boarding (and updating/removing) new services, and a lot of "air cover" to make sure new offers don't get mired in corporate wrangling. If the internal API team's proposition is that good, the new app development team will choose it. If not, they'll look elsewhere - and should not face problems for doing so. Speed and pragatism - a startup mentality - need to overrule the conservative approach to standards and network controls.

The 2015 and 2016 service plans should be subtly different from the 2014 one, in lots of small ways, which enhance the overall telecom model-year design beyond the sum or the parts.

Wednesday, October 22, 2014

WebRTC Delamination: shifting vendor roles, and recent moves from Ericsson, Temasys, Cisco, Tokbox & Mozilla

One of the major themes I address in my current research on voice and video / WebRTC trends is one I call "delamination". It's the opposite of vertical integration - the carving out of thin, narrow layers of services or products, in areas where companies have particular skill, focus or market reach.

It might be provision of a particular bit of client-side software, an effective hosted TURN server, an "enabler" of some kind, a particular security or authentication element, an especially-scalable virtualised network function, testing or analytical product, and so forth.

In a design-led approach to communications, this means that developers have both "raw ingredients" to create their own "recipes", as well as broad array of partly-prepared and pre-processed garnishes and side-dishes.

To continue the food analogy, if you really like salads, you can:

  • Plant & grow your own lettuces & make your own salad
  • Plant your lettuces but pay someone else to cultivate them
  • Buy lettuces from a farmer at the farm
  • Buy lettuces transported to a local market
  • Buy lettuces from your supermarket
  • Buy lettuce leaves from your supermarket
  • Buy chopped & prepared salad from your supermarket
  • Buy salad in a restaurant
  • Share someone else's salad
  • Watch someone else eating salad on YouTube
  • Subscribe to the Salad Channel
A similar approach is now applying to WebRTC (and to voice/video capabilities more generally). Developers - and these include intermediate developers like in-house groups at vendors and telcos - have a whole array of choices. They can build applications and services from scratch, use commercial or open-source software elements, host software internally or in the cloud - or use a third-party platform, and so on.




(This is one of the reasons it's so hard to answer the question "what's the $ market size for WebRTC?" - you can define it at any level you like, and there's potential for rampant double-counting if you include the whole value chain).

Now all this is nice in theory... but is it actually happening, and at "industrial scale"?

A few recent developments suggest that it is, indeed happening in a very meaningful sense:

  • Platform provider Temasys has announced a commercial version of its WebRTC plug-ins for IE and Safari browsers, with extra "enterprise-grade" support, intended for major software developers wanting to do full-scale deployments to business users.
  • Mozilla is working with WebRTC platform provider Tokbox to embed communications capabilities directly into the browser as "Firefox Hello". Its platform has hundreds of millions of users.
  • Cisco has open-sourced its H.264 implementation for use in WebRTC applications, and it too has been adopted in Firefox.
  • Ericsson has open-sourced its Bowser browser and OpenWebRTC client framework. This is really important both in terms of "big company delamination", and because it involves a rare step outside the telco/IMS domain for Ericsson with WebRTC. (Differentiating it from rivals ALU, Huawei & Nokia Networks, from which I've only heard about IMS use-cases for WebRTC)
  • Apparently, Ericsson's OpenWebRTC also uses Cisco H.264 (thanks Victor!)
[Disclosures - many companies quoted here are Disruptive Analysis clients for research and/or advisory work]

There are plenty of other examples too, but I'm highlighting these to illustrate that the concept is now becoming mainstream, and not just by small developers but also accepted and perpetuated by major players. This is likely to further accelerate market development - and also highlights the need for telcos and enterprise vendors to occasionally swallow their pride and use 3rd-party software or services where it makes sense. Only the very largest and most aggressive companies will be able to develop everything in-house, without using at least one other provider's platform. And for telcos, a vendor IMS box is not, on its own, a complete platform.