Many of my recent client conversations have been on network APIs, also known as network open APIs. In particular, they want to discuss timelines, challenges, opportunities, use cases, and future market outlook. Similar to what I discussed in my previous blog about 5G network slicing, the reality is not as rosy as one might expect, once again due to the heavy dependency on software development communities outside the telecommunications industry’s reach.
Why are people excited? In principle, network APIs allow carriers to provide network information or invoke network actions using RESTful open APIs, creating a much-welcomed monetization stream for telcos. Its success, however, relies upon a pervasive ecosystem and significant involvement from software developers. Vendors and telcos alike seek to solve for the decade-long shortage of application engineering knowledge within the telco ecosystem. What will be its future? I’ve organized my views across a timeline and major advancements expected in each period.
Short-Term: 1 to 2 years
This period will be mainly about experimentation, with a few point examples appearing in industries such as financial and commerce (e.g., anti-fraud, know-your-customer [KYC], identify verification, etc.). Although many telco-driven alliances trying to promote the ease and scale of consumption will form, a rapport with the software development community won’t be achieved. Software developers won’t include these APIs in their software development lifecycles (SDLCs) yet.
Midterm: 3 to 5 years
The first software alliance promoting adoption is formed. A true evangelization of a network-aware SDLC starts in this phase. An initial adoption is achieved, with the software development community understanding the value stream and starting to use some network APIs. Application design, engineering, and testing efforts are well understood, as well as the potential security and privacy risks. Some network APIs (e.g., quality on demand) won’t be used widely yet due to the parallel development of 5G stand-alone mode (SA) networks and devices with slicing capabilities.
Long-Term: 5+ years
Network APIs become common and play a key role in most application SDLCs. Proliferation of APIs and use cases is expected. A network-aware SDLC is a recognized practice within the software development community. Quality on-demand APIs are consolidated based on ubiquitous 5G SA slicing and roaming availability. Initial experimentation with APIs for 6G networks starts in this period. These APIs will provide new information such as network sensing data to be used by applications.
Do you concur with my view? Have you launched a commercial application using network APIs? I would love to hear your feedback. Need more guidance? Engage with me via an inquiry call by emailing inquiry@forrester.com.
