Pages

Pages

Friday, August 30, 2019

Timing is everything: Why telecom industry visions get it wrong


Introduction

One of the things I find most frustrating about technology forecasts and visions – especially in telecoms and mobile – is the lack of awareness of adjacent issues and trends, or consideration of "gotchas" and alternative scenarios.

So for example, when telcos, vendors or policymakers predict what 5G deployment, or network-slicing, or edge-computing or anything else might result in – applications, uptake, revenue opportunities and so on – they often fail to ask two critical questions:
  • Distractions: What are the prerequisites for this to happen? What are the bits of the overall wider system that are forgotten but necessary, to make the headline technology feasible and useful? And when will they be achieved? What's the weakest link in the chain? Is delay inevitable?
  • Disruptions: What else is likely to happen in the meantime, which could undermine the assumptions about demand, supply or value-chain structure? What's going on in adjacent or related sectors? What disruptions can be predicted?

This post has an accompanying podcast, on my SoundCloud:



Internal distractions & pre-requisites

So for example, for 5G to be successful to the degree that many predict (“trillions of $ of extra GDP”, millions of extra jobs etc) there first needs to be:
  • Almost ubiquitous 5G coverage, especially indoors, in sparse rural areas, and in other challenging locations
  • Enough fibre or other backhaul connectivity for the cell-sites
  • Suitable software and hardware platforms to run the virtualised core and other elements
  • Enough physical sites to put antennas, at low-enough costs & with easy-enough planning
  • Many more engineers trained and qualified to do all of the above
  • A decent business case, for instance in remote areas
  • 3GPP release 16 & 17 to be completed, commercialised and deployed, especially for the ultra-low latency & high-reliability applications.
  • Optimisation and operational systems, perhaps based on as-yet-unproven AI
Yet vendors and policymakers often gloss over these "annoying" practicalities. There seems to be an attitude of “oh, they’ll have to make it work somehow”. Well, yes, perhaps they will. But when? And at what cost? What changes does that imply? How will the gaps and limitations be bridged? And what happens if firms go bust while waiting for it all to happen? What other ways to solve problems can users pursue sooner, that don't involve 5G?

A key implication of this is that timing and profitability of massmarket adoption is often much later than expected. While Amara's Law might eventually apply (we tend to overestimate the effect of a technology in the short run and underestimate the effect in the long term), that doesn't mean that early initial adopters and investors make the returns they'd hoped for.



External disruptions and substitutes

Perhaps even more pernicious is the lack of situational awareness about parallel developments elsewhere in the broader tech ecosystem. These undermine both demand (as alternative solutions become viable in place of the hoped-for technology) and supply / operation (by throwing up new complexities and gotchas to deal with). 

These are often not just “what ifs" but “highly likelies” or "dead-on certainties".

So for instance, the visions of network slicing, or edge-computing for 5G (which will really only crystallise into large-scale commercial reality in maybe 4-5 years) will have to contend with a future world where:


  • 5G networks are still patchy. There will still be lots of 4G, 3G and “no G” locations. What happens at the boundaries, and how can you sell QoS only in certain places?
  • There will be a patchwork of “uncontrolled” locations – they might be 5G, but they could be owned by roaming partners, indoor network providers, private localised cellular operators and so on. How will a slice work on a neutral-host's network?
  • An ever-greater number of devices spend an ever-greater amount of time on Wi-Fi – usually connected to someone else’s fixed-line infrastructure and acting as either uncontrolled, or a direct arbitrage path. 
  • Telcos have to cap their energy use and associated CO2 emissions, or source/generate clean power of their own.
  • Wi-Fi 6 will emerge rapidly & is hugely improved for many use-cases, but most 5G predictions only compare against legacy versions
  • Hardware based on "commodity hardware" runs against the current tide of semiconductor fragmentation and specialisation (see recent post, here)
  • Devices will often have VPN connections, or use encryption and obfuscation techniques, which means the network won't be able to infer applications or control traffiic.
  • Users and devices will use multiple connections together, either for arbitrage, aggregation, or more-sophisticated SD-WAN type models.
  • Pricing, billing, customer support and security will be challenging on "federated" 5G or edge-compute networks. Who do you call when your network-slice doesn't deliver as expected - and how can they diagnose and fix the problem?
  • Liability and accountability will become huge issues, especially if 5G or slicing is used for business-critical or life-critical functions. Are your lawyers and insurers prepared? 
  • AI will be used for instant price-comparison, quality monitoring & fault reporting, collective purchasing and even contractual negotiations. "Hey, Siri, mimic my voice and get me the best discount possible with the customer-retention agents"
These are just some basic examples. Once you get into individual verticals, particular geographies or even specific companies, a whole host of other issues start to crop up  - sector regulation, value-chain shifts, government involvement, expectations of 20-30 year tech cycles and so on. Sure, in theory 5G might fit into various industries' own transformation journeys - but they won't design around it.


Conclusions

I find this all very frustrating. So many company boards, strategy departments or lower-level product/service management teams seem to operate on the basis of "all other things being equal..." when the one certainty is that they won't be



So the two sets of factors tend to be multiplicative:
  • Distractions are internal to a new concept, and lead to delays in technology launch, market maturity and revenue.
  • Disruptions are external and often inevitable, but any extra delay increases their range and impact yet further.
It's never possible to predict everything that might get delayed, or every possible disruption from adjacency. But it seems to me that many companies in telecoms don't even bother to try. 

Companies accept the "hype cycle" as inevitable, even if it might be possible to flatten it out.

By coincidence, while writing this post I started reading "Range" by David Epstein (link) which talks about the importance of "analogising widely", and the risks of narrow expertise and superficial analysis, rather than looking for implications of cross-sector / cross-discipline similarities and lessons. 

When evaluating new technologies and service concepts, CEOs and CFOs need to rely less on familiar industry echo-chambers and consensus hype, and instead seek out critics who can find hidden assumptions, both internal and external to their plans. This isn't just a negative exercise either - often, a "ranging" exercise throws up unexpected positives and opportunities from adjacency as well risks.



This post has an accompanying audio podcast - click here & please subscribe!

 
Footnote
 
I sometimes get asked to "stress test" ideas and plans, and help companies avoid expensive mistakes, get started on future glitches today, or prepare for and avoid contingencies and unintended consequences. 

Often, that exercise will throw up new opportunities as well. Usually, a collaborative (but candid) group workshop ensures this isn't a blame-game, but a path to smoother growth and innovation. The skills and mindsets can be learned and replicated, too.

If that type of approach sounds interesting, please get in touch with me, either by email (information AT disruptive-analysis DOT com) or via LinkedIn (link).



Wednesday, August 21, 2019

Edge Computing in the Network, or Network deployed at the Edge datacentre?

Warning: totally speculative “what-if” post…. 

Almost everyone assumes that MEC-type edge-computing will be *inside* 5G or converged fixed-mobile infrastructure. The idea is that telcos will host servers deep in their networks, for low-latency 5G NR radio, coupled to micro-datacentres a millisecond or so from a cell tower, or perhaps at a local fixed line exchange / central office. 

Many telcos and their vendors seem to think this could allow the industry to create quasi-AWS distributed cloud services. I've written and spoken about the landscape of edge computing several times (see blog here and podcast here)

But I wonder if we could also see the exact opposite approach. Imagine a small/mid-size datacentre in an urban area as a hub for a localised mobile network. It could have a 4G or 5G base station on the roof, perhaps with links to relay sites in the surrounding area. 

Using CBRS spectrum in the US, or 3.7-3.8GHz in Germany or various of the new UK shared bands, it could cover perhaps a 3-7km radius. As it will have plenty of fibre acceess, it could also run its own cloud-RAN network for its local region or city. 

This could give local businesses direct, one-hop-to-the-cloud connection for sites or mobile IoT. Say a local firm doing drone-as-a-service for site inspections. Or buses for a smart city. No telcos required. Now there are various challenges, like poor outdoor-to-indoor coverage at 3.5GHz. But low-band MVNO deals, WiFi & neutral hosts could help fix that.

The cloud / DC provider would certainly need additional elements, such as a core network, and perhaps a way to issue SIMs/eSIMs. But that's increasingly possible - Amazon, for instance, already hosts various cloud-based core networks from third party vendors, while Google has its own that it uses for Fi and other purposes.

Unlikely? Yes. Disruptive? Certainly.

(If you really want to push this idea, I also suggested over two years ago in this post that Amazon's purchase of Whole Foods gave it a unique urban footprint for mini-DCs. Many of those also have suitable rooftops, as well as plenty of power)

This post was originally published on my LinkedIn page. It has had over 10,000 views and has created a great stream of comments and interactions. Link here.

Tuesday, August 13, 2019

How will voice be delivered on private 4G / 5G & CBRS networks? Private VoLTE?

An area I've seen little discussion about is the intersection of new private 4G / 5G networks, with voice and unified communications, UC. Most debate is about either local IoT (i.e. data) connectivity, or neutral-host / wholesale approaches for in-building or rural coverage.

But where enterprises deploy "pure" private networks aimed at employees or visitors, they are likely to want voice / telephony capabilities, plus more advanced communications capabilities. While this is already done for highly-specialised local cellular deployments for mines, military or maritime, it is much less clear how this could scale to more general enterprise users. 

Many of the existing local-cellular users are also just based on 2G/3G, for which simple circuit-switched infrastructure has been available for years (I had a client supplying softswitches for private voice with pico-cells, as early as 2006).

My view is that UCaaS, cPaaS, cloud telephony, IP-PBX & collaboration solution providers should be looking much more closely at the impact of CBRS, and its international equivalents, providing localised 4G/5G wireless in new spectrum, and neutral-host models. 

It is unclear whether enterprises will want to deploy "private IMS" solutions, cloud-based VoLTE & SMS, or use some simpler forms of wireless-capable VoIP in their own domain. There are various deployment scenarios I can see, each of which will require careful thought & focused strategies: 
  • Transition from two-way radio (eg TETRA) to cellular push to talk
  • Integration of existing UC/UCaaS/PBX with private cellular voice
  • IoT integration of realtime voice/video (for example "speak to an engineer" functions)
  • Fit with conferencing, collaboration & messaging platforms
  • Interoperability / roaming scenarios with public PSTN & mobile calling
  • cPaaS scenarios & APIs tailored for private mobile networks
  • Will private 5G networks using slicing techniques to prioritise QoS for non-3GPP VoIP?
  • For neutral hosts, how will they enable roaming telephony / messaging / other voice & video applications
  • What happens with numbering & identity?
  • Can private cellular work for contact centres?
  • Are there "IMS lite" options for enterprise, that cuts down some of the features and integration seen in telcos?
  • Is this a prime candidate for multi-tenant "VoLTE-as-a-service" cloud propositions?
I'm going to be watching this whole area more closely in coming months, as it seems to be rather overlooked, at least publicly. Given that a number of companies in the UCaaS / cPaaS space also have footholds in CBRS or mobile core networks (eg Amazon, Google, Twilio) it wouldn't surprise me if there's a lot going on beneath the surface here too....

(Please contact me if you're interested in exploring this domain, have existing solutions, or would like to engage me on private advisory work)

#5G, #cloudcommunications, #neutralhost, #UCaaS, #cPaaS, #voice, #collaboration