Open Gateway: what's it worth + time for an MVP?
Andrew Collinson
MD, Connective Insight | CPaaSAA Research | New $ by connecting minds | Research, thought leadership, facilitation and strategic advisory. #unthinkable
I spent some of my time at MWC 2024 talking with people about three of the industry’s big “open” initiatives – Open Gateway, Open Digital Architecture (ODA), and Open Radio Access Network (ORAN).
To start off, here are my thoughts about Open Gateway, starting to explore the question of (and arguments about) 'what is it worth to the industry?'. In summary:
I welcome further input on how others see this. Below, I set out the context, the arguments (there are plenty!), the estimates, and why an MVP makes sense.
Context: the Connected Technology industry needs to be more open
These days, I see Telecoms as being part of a much broader industry that I think of as “Connected Technologies”: connectivity, data, automation, AI, etc. I also see it through the lens that the point of all this technology is to help make better use of stakeholders’ resources (money, time, health, carbon, etc. - see the Coordination Age).
All the “Open” initiatives are important because they are all ways to either help the Connected Technologies industry work better or enable other industries. I see them all as “good ideas” and I like and respect all the people I know who are engaged with them. But how are they doing?
Open Gateway: the big push to open up to other industries (and developers)
Open Gateway was the GSMA’s flagship project at MWC 2024, and is broadly another go at standardising telco APIs (you can see the API definitions here). The idea is to allow 3rd parties (e.g. customers, developers) to access telco assets and information easily, so they can use them to build and deliver new offerings.
Example Open Gateway APIs include:
It was heavily backed (47 operators have signed up) and CEO-fronted at MWC 2024, but there are a lot of questions to answer.
I spent some time with the GSMA’s Henry Calvert who runs Open Gateway. He clearly sees that there’s a way to go yet to resolve these questions, plus others about getting telcos to work together to make it all happen.
Clearly as all the announcements showed, Henry and others have been busy getting operators on board.
So: what's it worth?
When we tried to size the multi-sided telco business model opportunity at STL Partners back in about 2010, we came up with a total potential of about $260bn. We caveated that as very much a 'total possible' number relating to a series of assumptions about the telco assets available and the benefits possible from telecoms platforms models in global industries.
To put this time in context, WhatsApp only had 50m users (now 2.8bn), Blackberry still had 43% of the smarthone market, and Amazon's share price was $6.36 (today $178.75). Kudos to my former colleague Chris Barraclough , now CEO STL, who had both the original vision to develop the multi-sided telecoms business model research and the good judgement to firmly caveat the numbers.
13 years later, it looks like McKinsey has come up with a similar ballpark number of $100-300bn in the next 5-7 yeas for the total potential revenue associated with telco APIs.
Most of this comes from "revenue unlocked in other industries" in "connectivity- and edge-computing-related revenue". I haven't been able to find the source analysis for this, so for now I assume that this is an estimate of potential "unlocked" in other vertical plays in the cited industries. Presumably they mean it is extra money spent on things like turbo-boosted connectivity, edge computing rentals to HSPs, and forays into vertical ICT solutions.
McKinsey also say that telcos "would cede as much as two-thirds of the value creation" to other players, based on current market structures, and estimate the APIs themselves as generating $10-30bn for telcos.
I'm not sure why McKinsey thought the telcos would "cede two-thirds" of the $100-300bn, or that 10% of it would be the API take. Perhaps that is locked away in a deep vault requiring many dollars to view, or they've just made some order of magnitude estimates.
I don't really have a problem if so, but I would like to know what sort of estimates these are. Are they 'we spent an afternoon thinking about this' or based on a genuinely deep analysis? I don't think anybody is going to get their cheque book out because an article says "McKinsey says $300bn" but it will make CEOs look, people will talk, and pretty soon that $300bn will become a conversational assumption.
I'm using it here, for example - but I just want to flag this so you keep that in mind!
A storm in a web-broswer near you
There was then a fair old hoo-hah on the back of a classic “meh” post on Linked-In about all this by disruptive Dean Bubley.
Omdia’s Camille Mendler (excellent on most things, especially Enterprise Telco), Ferry C. Grijpink (Mckinsey, a co-author of the $300bn telco API opportunity report) and Alan Quayle (TADHack – essentially Mr Developer) - all worth listening to – all waded in.
To summarise: opinions were somewhat polarised between “there’s a huge opportunity!” and “telcos will never succeed at it like this!”
Will it "move the needle"?
How much of this 'potential' value you believe is relevant to the situation of your company will depend on a lot of different variables, such as what verticals are most active in our markets, how developed they are, and how well your offering serves them - as well as taking into account your view on the realistic total value pot including Dean's and all the other commentaries.
You might also argue that the APIs will enable you to play higher in the value stack, creating new business models and developing other offerings and applications etc. - as per the McKinsey piece and STL's original hypothesis back in 2010.
But for the sake of this thought-experiment, let's take a mid-point figure for the APIs alone, and put it in context as a 'back-of-the-envelope' excercise:
So depending on how Dean-ish you feel today, this estimate means between 0 and 1% growth from direct API revenues, and more if it's particularly pertinent to your markets and you factor in other successful future plays serving the verticals better.
If you go with the MckInsey '$100bn' - perhaps ceding that other two thirds and executing well - that's up to 5% growth overall (but remember this isn't just API revenue - its all the rest of the things you might be able to do).
领英推荐
Is it worth all the hassle?
Now you might think to yourself "is that really worth all the hassle?" - and that is a pertinent question that will doubtless go through a few execs' minds.
I think it is, for the following reasons:
That doesn't mean 'no investment' or 'go slow'. It means move fast, collaborate to reduce risk and improve scale, and be selective - try to focus on bringing something genuinely useful to market fast, together.
How might telcos actually do this?
While the noise at MWC24 was all about how many telcos have signed up, the principle challenge seems to be how many are getting usage, and I haven't seen much data on that so far. It's early days, for sure, but a big critique leveled in the hoo-hah described above is that you need to provide APIs that developers want and find easy to use.
Time to focus on a collaborative MVP?
It's interesting that SIM Swap and Number Verification are the APIs most launched and 'certified' (in the case of SIM Swap). Of all the APIs, they are the most telco-specific - they directly relate to telco attributes (number, SIM). plus they should in theory provide immediate additional value in solving a specific and valuable problem: fraud.
They are also not particularly 5G specific, like the much hyped 'Mobile Quality on Demand' API. From the research I have seen, there are sectors of the market that are interested in the more data-heavy APIs. Broadcasters, for example, quite like the idea of being able to call up additional capacity and speed for upload links. However the bulk of market interest seems to be in the more basic identity and fraud management APIs.
Looking at the thoughts of Rakuten's Not Normal CMO Geoff Hollingworth in this thoughtful post on API strategies (and telcos' past listen-fails), this well informed post on API strategies from STL's Darius Singh, and thinking about what Alan Quayle told me recently about past developer needs (they mostly used operator look-up APIs), I am wondering if the answer on how to make Open Gateway work better might start from one these APIs (or something like them).
Now, I don't know for a fact that developers want either of these APIs most, and that should be tested. But let's assume that one of these is the most generally needed. After all, these are the APIs that more operators have lauched first (which presumes their decisions were led at least in part by customer input).
Wouldn't it now be a good idea to get all operators to focus on launching this same API in a 'lean-development' sprint to create global minimum viable proposition (MVP)? At least then, there should in theory be one valuable API that developers can reliably use across all ecosystems and most markets?
Doing this should pilot the way to develop all the necessary processes and agreements to get all the APIs negotiated and delivered, thereby either prove the concept and make it easier to scale - or show that it simply can't work - for the least effort/investment?
As a really radical thought, why not make it free of charge across the board for a guaranteed agreed period of say three years? That way there would be no obstacles to use, and the industry could prove its value unambiguously. It would also give the industry time to work out if and how to price something like number validation, say, that works across markets. Of course, this might make reaching agreement with all the telcos harder, but it would almost certainly make the proof of value stronger.
None of this should mean that individual operators shouldn't do proofs of concept on other APIs, but rather that collaborative efforts might focus on a minimum viable proposition (MVP) in the near future.
This really is an area for collaborative advantage rather than competitive advantage. These APIs become much more valuable when scaled and working everywhere, so a developer only has to find and incorporate the API once. Second best might sometimes be where they work in a specific geographical market (e.g. so you can say "at least we can verify this number in Germany").
Plus - don't forget these APIs will have competition. Below, for example, is a lazy Google for mobile anti fraud APIs.
Don't be misled by the "Prisoner's Dilemma" - it's a distraction
Back in the 2010s, there was a lot of talk around the Prisoner's Dilemma, which is a classic paradox of whether to collaborate or compete. In the dilemma, prisoners can all win a prize of a shorter sentence by collaborating and refusing to betray their fellows, or an individual prize of an early release by betraying all their fellow prisoners, who then get longer sentences. In most cases, someone goes for the early release deal.
This has often been the case in the intervening years in Telecoms since 2010. We have seen many operator initiatives fail (in APIs, payments, advertising, etc.) because each time, one or other operator lost patience and tried to do it by themselves, usually achieving a spurt in unfettered development, followed by collective failure because there was no market at scale.
"To go fast go alone, to to far, go together" as Vodafone's GCEO Margherita Della Valle put it rather well at MWC.
Hence, in this context the Prisoner's Dilemma is an unhelpful and unrealistic paradigm. Maybe there should be an updated and more realistic version, in which the choice is you can go for the early release and get it briefly, but afterwards everybody gets a life sentence.
Will telcos actually collaborate to succeed?
Back to the real world, I think the scrum around Open Gateway will continue for a while. The only thing will carry it through is commitment, listening to stakeholders, and obviously - ultimately solving all the challenges.
Whether the industry is capable of this is a hard question because it’s not just a technology problem but a stakeholder alignment one too, and they’re much trickier to fix across an industry. And the industry has failed before - although there does seem to be a bit more collective resolve this year.
Though at MWC24, I felt that the narrative was “if we all say it loud enough, it will work!” Given that I think success here rests on listening to the right people and I didn’t see much evidence of that, that didn’t feel quite on track to me.
And I did feel there was quite a lot of noise about the fancier APIs - the gaming boosts, etc., and maybe there will be a market for that. But not if the approach is not scaled so developers can use it easily. It's perhaps understandable that folks want to use the fancy stuff in promos at MWC, especially when so many people are keen to prove that 5G really was worth all the investment. But I don't think that is where the strategic emphasis should be for now, based on the reasoning above.
That doesn’t mean that the right things aren’t happening or won't eventually happen, even though that wasn't what could be seen at MWC24. But the longer it takes, the lower the potential to take the prizes theoretically on offer - whatever they turn out to be!
I think Henry and his colleagues see what is needed. I just hope he’ll get the ongoing backing, commitment - and openness - from the industry needed to get there.
PS My thanks to Disruptive Dean and Charlotte Patrick , Telco AI Research Queen, who respectively raged at and politely guided my earlier drafts, and provided some great additional insights.
*High level industry numbers sourced here.
**GSMA numbers for Feb 2024 here.
Linux Foundation (LF) Edge Akraino Technical Steering Committee (TSC) member, 3GPP written approvals for use of Official Logos for 6G, 5G Advanced, and 5G, 5G PINs/CPNs, 5G Advanced equivalent NPNs/SNPNs New Services,
11 个月Andrew Collinson on the subject of APIs evolvement in Cellular Networks and in particular for 5G, attached below FYI. //Ike A. https://www.dhirubhai.net/posts/ike-alisson-21173_5g-evolvement-of-api-capabilities-activity-7111208600458412032-a3dd?utm_source=share&utm_medium=member_desktop
Linux Foundation (LF) Edge Akraino Technical Steering Committee (TSC) member, 3GPP written approvals for use of Official Logos for 6G, 5G Advanced, and 5G, 5G PINs/CPNs, 5G Advanced equivalent NPNs/SNPNs New Services,
11 个月Andrew Collinson, by any chance, have you seen 1st: Any benchmark/assessment about How the 3GPP standard specified Functional Architecture for Common API Framework for Northbound APIs for the 5GS is "inadequate" and 2nd How is the Open GW Initiative from 2023 different form the GSMA OneAPI Exchange from 2013 (attached link to it below)?//Ike A. https://www.gsma.com/newsroom/press-release/gsma-announces-oneapi-exchange/
Programmable Telecoms / Communications Expert
11 个月Telco 2-sided business model was in fact the 1.005 sided model. https://alanquayle.com/2011/05/the-two-sided-business-model-i/. So rather than focusing on generic labels, like developers and APIs. Let's focus on specific services, number verification, and the customer of that service, an ecommerce company. Here's a supplier of such a service used by many ecommerce customers today, https://www.telesign.com/products/phone-id. Telesign has been at this for nearly 20 years. The eCommerce company wants to ensure the number is valid, the international prefix is correct, and data entered for that account (name and address) is roughly correct. The problem is already solved by many companies that partner with telcos, and deliver a complete solutions compliant with local regulations. The industry is called programmable communications / telecoms. Its mature, tens of billions of dollars, Twilio is an archetype. On SIM swap the carriers need to get their act together as they are the ones doing the swapping at the fraudster's request. I prefer the term Mr Programmable Communications. I've been helping companies in this space for several decades, tadsummit.com. Yes I run hackathons because the industry needs new talent, tadhack.com.
Strategy and business innovation for organizations in Massive Connectivity and Digital Economy markets
11 个月A few immediate thoughts for Andrew Collinson i) Important to contextualize an initial MVP as one of an extensible set of network capabilities and APIs (plan for economies of scope, prepare for new avenues of demand and, signal to the ecosystem that this is not a 'silver-bullet' but an element in a longer-term, growth-oriented roadmap). ii) Developers unlikely to be excited by one API or the prospect of aligning with one or a handful of MNOs however large (so GSMA initiative needs to make more of horizontal platform and 'inverted firm' strategies) iii) Current focus seems to be on consumer-oriented applications with less attention to the different characteristics of APIs for #IoT, where enterprises are likely to be more active because they see the value (operational, supply-chain data-insights, product innovation etc.) that IoT enables. That might push revenue potential above the 1-5% level (which is on par with just the connectivity % associated with the IoT value stack) More context here - https://www.more-with-mobile.com/2024/03/a-300bn-market-for-telco-apis.html
Consultant & Advisor/Telecom Industry Thought Leader/Former Tier 1 Telco Exec/Supply Chain Navigator & Partnership Matchmaker/Buyside Fox turned Sellside Streetfighter/Startups/Spinouts/Investor Advisory/M&A/IET Fellow
11 个月Oh dear. Another go at API exposure of not-so-very-interesting network analytics ??. And “boost button”? Really? That old chestnut?