Showing posts sorted by date for query U.S. 5G revenue edge. Sort by relevance Show all posts
Showing posts sorted by date for query U.S. 5G revenue edge. Sort by relevance Show all posts

Monday, April 14, 2025

Telco AI Monetization on the Revenue Front Will be Difficult

Mobile executives these days are talking about ways to monetize artificial intelligence beyond using AI to streamline internal operations. Generally speaking, these fall into three buckets:

  • Personalizing existing services to drive higher revenue, acquisition and retention (quality of service tiers of service, for example)

  • Creating enterprise or business services (private 5G networks with AI-optimized performance,, for example)

  • AI edge computing services for autonomous vehicles, for example


Obviously, those are AI-enhanced extensions of ideas already in currency. But some of us might be quite skeptical that such “AI services” owned by telcos will get much traction. History suggests the difficulty of doing so. How many “at scale” new products beyond voice have telcos managed to create? Text messaging comes to mind. Mobile phone service also was a big success. So is home broadband. 


All those share a common characteristic: they are network services owned directly by the service providers. Generally speaking, other application efforts have not scaled well. 


Mobile service providers have been hoping and proclaiming such new revenue opportunities since at least the time of 3G. But many observers might agree there has been a disconnect between the technical leaps (faster speeds, lower latency, better efficiency) and the ability to turn those into new revenue streams beyond the basic "sell more data" model. 


That is not to say that service providers have had no other ways to add value. Bundling devices, content and other measures have helped increase perceived value beyond the core network features. 


But the core network as a driver of new products and revenue is challenging for a few reasons. 

  • Open networks mostly have replaced closed networks (IP versus PSTN) 

  • Applications are logically separate from network transport (layers)

  • Permissionless app development is the norm (internet is the assumed network transport)

  • Vertical control of the value replaced by horizontal functions (telcos had full-stack control of voice, but only horizontal transport functions for IP-based apps)


As I have argued in the past, modern telcos have a hybrid revenue model. They are full-stack “service” providers for voice and text messaging. But they are horizontal transport providers for most IP apps and services, and sometimes are app providers (owned entertainment video services, for example). 


The point is that most new apps and revenue cases can be built by third parties without telco or mobile operator permission, which also takes transport providers out of the direct revenue chain. 


So I’d argue there is a structural reason why telcos and mobile service providers do not directly benefit from most of the innovation that happens with apps. Think about all the customer engagement with internet-delivered apps and services, compared to service provider voice and messaging. 


In their role as voice and text messaging providers, telcos are “service providers” (they own and control the full stack). For the rest of their business, they are transport or access providers (capacity or internet access such as home broadband), a horizontal value and revenue stream. ISPs get paid to provide “internet access,” not the actual end user apps. 


And that has proven a business challenge for now-obvious reasons. Once upon a time, voice services were partly flat-rate and partly usage-based. In other words, telcos earned money by charging a flat fee for access to the network, and then variable usage based on number, length or distance of voice calls. 


In other words, greater usage meant greater revenue. But flat-rate voice and texting usage subverts the business model, as  most of the revenue-generating services become usage-insensitive. That is the real revolution or disruption for voice and texting. 


In their roles as internet access providers, some efforts have been made to sustain usage-based pricing. Customers can buy “buckets of usage” where there is some relationship between revenue and usage. 


Likewise, fixed network providers have used “speed-based” tiers of service, where higher speeds carry  higher prices. Still, those are largely flat-rate approaches to packaging and pricing. And the long-term issue with flat-rate pricing is that it complicates investment, as potential usage of the network is capped but usage is not.  


So as much as ISPs hate the notion that they are “dumb pipes,” that is precisely what home or business broadband access is. So internet access take rates, subscription volumes and prices are going to drive overall business results, not text messaging, voice or IoT revenues. 


To be sure, we can say that 5G is the first mobile generation that was specifically designed to support internet of things applications, devices and use cases. But that only means the capability to act as a platform for open development and ownership of IoT apps, services and value. And even if some mobile service providers have created app businesses such as auto-related services, that remains a small revenue stream for mobile service providers.  


Recall that IoT services are primarily driven by enterprises and businesses, not consumers. Also, the bulk of enterprise IoT revenue arguably comes from wholesale access connections made available to third-party app or service providers, and does not represent telco-owned apps and services (full stack rather than “access services”). 


Optimistic estimates of telco enterprise IoT revenues might range up to 18 percent, in some cases, though most would consider those ranges too high. 


Region/Group

Total Mobile Services Revenue 

IoT Connectivity Revenue (Enterprises)

Automotive IoT Apps Share of IoT Revenue

% of Total Revenue from Automotive IoT Apps

Global Average

$1.5 trillion (2025 est.)

10-15% (2025, growing to 20% by 2027)

25-35%

2.5-5.25%

North America (e.g., Verizon)

$468 billion (U.S., 2023, growing 6.6% CAGR)

12-18% (2025 est.)

30-40% (high 5G adoption)

3.6-7.2%

Asia-Pacific (e.g., China Mobile)

$600 billion (2025 est.)

15-20% (strong automotive industry)

35-45% (leader in connected cars)

5.25-9%

Europe (e.g., Deutsche Telekom)

$400 billion (2025 est.)

10-15% (CEE high IoT reliance)

25-35%

2.5-5.25%

Top 10 Mobile Operators

$1 trillion (2025 est.)

12-18% (based on 2.9B IoT connections)

30-40%

3.6-7.2%


Though automotive IoT revenues (again mostly driven by access services) arguably are higher for the largest service providers, their contribution to  total business revenues is arguably close to three percent or so, and so arguably contributing no more than 1.5 percent of total revenues, as consumer services range from 44 percent to 65 percent of total mobile service provider revenues. 


Category

Percentage of Total Revenue

Example products

Services to Consumers

55-65%

Driven by mobile data (33.5% in 2023), voice, and equipment sales; 58% in 2023

Services to Businesses

35-45%

Includes enterprise, public sector, and SMBs; growing at 7.1% CAGR

Business Voice

5-10%

Declining due to VoIP adoption and mobile data preference

Business Internet Access

15-25%

Rising with 5G, IoT (e.g., automotive apps at 2.5-9%), and enterprise demand


The point is that the ability to monetize AI beyond its use for internal automation is likely limited. Changes in the main revenue drivers (consumer and business mobile phone subscriptions and prices) are going to have more impact on revenue and profit outcomes than IoT as a category or automotive IoT in particular.


Thursday, June 20, 2024

How Big a Market for Telco APIs?

At least some estimates of the eventual size of the "telco API" market are likely to be unrealized, just as the earlier unified communications and collaboration market has arguably seen.


That might be true, in part, because telco APIs are intended to allow connectivity service providers a bigger role in the UCC markets, as well as supporting network slicing and monetization of some other network functions.


The unified communications and collaboration market always has been difficult to categorize, to the extent that it includes so many disparate segments. And the same will likely be true fot the telco application programming interface market as well.


UCC traditionally includes video conferencing hardware, subscriptions and service; voice messaging features; premises voice appliances and services and often the connectivity services used by cloud-based UCC apps and services. About the only thing the UCC category has not traditionally included are the value of business voice services sold by telcos. 


UCC Market Estimate By

Market Revenue (USD Billion)

Year

CAGR

Fortune Business Insights

71.26

2023

17.70%

Grand View Research

136.11

2023

17.40%

IDC

64.7 (full year forecast)

2023

8.60%

Mordor Intelligence

145.58

2024

27.80%

Markets and Markets

$76.7 billion

2022

13.00%


The telco API market should include these and other newer features such as 5G network slicing. And high hopes notwithstanding, the telco API market might well wind up being a niche, as UCC has been. 

The perception by traditional connectivity service providers that the various UCC services are niches can be seen in the market share figures for UCC providers of hardware and services. Microsoft's Skype and Cisco Webex are leaders in conferencing. 


Most suppliers of UCC hardware have relatively small share, as do independent providers of UCC services. Also, note that video conferencing represents at least 44 percent of the total UCC market.  


One reason the UCC category exists at all is because each of the constituent revenue components are relatively modest. Note also that some UCC functions (messaging, voice mail, conferencing) are provided by apps and services not generally tracked in the UCC bucket, often because they do not represent “for fee” apps (Facebook Messenger and other messaging apps such as WhatsApp, Apple Facetime, Google Meet and email apps, for example. 


Firm

Market Share

Source/Year

Microsoft

21.8%

Statista (Q4 2023)

Cisco

15.2%

Statista (Q4 2023)

Zoom

7.1%

Statista (Q4 2023)

RingCentral

5.5%

Statista (Q4 2023)

Avaya

4.2%

Mordor Intelligence (2024 est.)

Mitel

3.1%

Mordor Intelligence (2024 est.)

Polycom (Plantronics)

2.8%

Mordor Intelligence (2024 est.)

NEC

2.5%

Mordor Intelligence (2024 est.)

GoToConnect

2.3%

Mordor Intelligence (2024 est.)

8x8

1.9%

Mordor Intelligence (2024 est.)

3CX

1.5%

Mordor Intelligence (2024 est.)


So now we hear about telco application programming interfaces (APIs) as a possible growth market. And the relationship between telco APIs and UCC is that the most-logical near-term revenue sources for telco APIs are apps and services that use UCC features (messaging, voice, videoconferencing). 


To be sure, many hope for new additional API instances and markets for elements of the 5G mobile network experience; network slicing or other elements of the 5G experience that can be supplied by the 5G core and access networks. 


And that is where the more-optimistic forecasts for telco API-related revenue seem to rely. That assumes developers will see value in licensing access to network features related to bandwidth consistency, latency or other network-derived features. 


And some of us might suggest that those values and possible markets are going to develop more slowly than some seem to expect. Even allowing for some shifts of market share among current providers, and faster “core” UCC market growth than we have seen in recent decades, most of the forecast growth would necessarily have to come from new API markets related to private networks or network features, plus the spending on infrastructure to support the use of telco APIs. 


At a high level, there always are alternate ways to solve an engineering problem, such as latency performance or computing cost. Basically, one can substitute bandwidth for processing (remote data center processing, for example) or processing for bandwidth (edge computing or on-the-device computing, for example). 


Study

Overall UCC Market Size

Segments

Forecast Period

Verified Market Research

$222.99 Billion by 2030

Deployment Model, Platform, Application, Region

2024-2030 CAGR 17.7%

MarketsandMarkets

$141.6 Billion by 2027

Component, Deployment Mode, Organization Size, Vertical, Region

2022-2027 CAGR 13.0%

Mordor Intelligence

$496.30 Billion by 2029

Deployment Type, Type, End-User Industry, Region

2024-2029 CAGR 27.8%

Straits Research (cited by Mordor)

$1,171.63 Billion by 2032

Not specified

2024-2032 CAGR 20.4%

STL Partners (cited)

$20+ Billion by 2028

Mobile Network APIs

-

Market.us

$1,459.5 Billion by 2033

Not specified

2024-2033 CAGR 18.1%

And the point is that there are many ways to solve a latency, bandwidth or processing problem. Telco APIs are one way to solve such problems, but there are alternatives that do not require use of telco APIs. 


And as a way of gaining market share in the traditional UCC market, telco APIs might be one way, but not the only way, to participate. Ericsson simply bought Vonage, for example, to gain capabilities of creating voice, messaging or communication solutions for any app. 


Acquisitions might be one way to gain share faster than creating standards and products using telco APIs. And the issue of market potential (total addressable market) would still remain. The reason telcos generally did not want to be PBX suppliers was always that the market was sub-scale for them. Those same issues apply to new cloud-based UCC solutions that essentially replace business phone and conferencing systems as well. 


Approach

Description

Advantages

Disadvantages

Telco APIs

Leverage network APIs from telecom providers to access capabilities like quality of service, network slicing, location services etc.

Can guarantee bandwidth, low latency, and prioritize critical traffic over public networks

Requires integration with telco platforms and potential costs for premium services

Edge Computing

Process data and run applications closer to the source/user on edge nodes instead of centralized cloud

Reduces latency and bandwidth needs by bringing compute closer to the edge

Requires deploying and managing distributed edge infrastructure

On-Device Computing

Perform processing and decision-making directly on the user's device (e.g. mobile phone, IoT device)

Minimizes latency and bandwidth needs by avoiding network round trips

Limited by device compute capabilities and battery life constraints

Private Networks

Deploy dedicated private cellular or wireless networks for specific use cases or environments

Offers predictable performance, security, and control over the network

Requires significant upfront investment in private network infrastructure

Content Delivery Networks (CDNs)

Distribute content and services across a global network of edge servers closer to users

Improves performance by caching content at the edge and reducing latency

Primarily optimized for content delivery rather than real-time applications

Peer-to-Peer Networks

Establish direct connections between devices or nodes without relying on centralized servers

Reduces bandwidth needs and latency by avoiding server hops

Complexity in managing peer discovery, connectivity, and security

Network Optimization

Techniques like compression, caching, load balancing to improve utilization of available bandwidth

Can enhance performance without additional infrastructure

Optimizations have practical limits based on network conditions


The issue is that at least some forecasts of potential telco API markets seem excessively optimistic.   


On the Use and Misuse of Principles, Theorems and Concepts

When financial commentators compile lists of "potential black swans," they misunderstand the concept. As explained by Taleb Nasim ...