Network APIs are a game-changer for the telecom, enterprise, and broader tech industry, enabling the monetization of advanced programmable networks like LTE, 5G, and Wi-Fi. A broad ecosystem approach is essential to unlock the full potential of network awareness. Network Equipment Providers (NEPs), Hyperscalers, Communication Platform as a Service (CPaaS) companies, system integrators, and independent software vendors must collaborate to create innovative solutions. Service providers also need to use APIs internally between their own teams and departments and for interaction with other peer operators and CSPs.

We applaud Ericsson’s recent announcement, sharing our belief in an ecosystem – but believe we need to treat deep network control differently to application-layer capabilities such as identity verification.

Shabodi has been at the forefront of this ecosystem approach since its launch in 2020. We’re pleased to see the broader industry moving towards this collaborative direction, with initiatives like 3GPP’s Network Exposure and CAPIF specifications, Linux Forum’s CAMARA project, and GSMA Open Gateway.

In some recent developments, NEPs aim to provide network APIs from various telecom operators to the developer ecosystem via aggregators. However, realizing the true opportunities that network APIs can provide takes more than exposing APIs and providing platforms.

There are important differences between APIs that fit into mainstream applications and user journeys, such as number verification and anti-fraud mechanisms, compared to those that involve awareness and control of “hard” network performance, quality or configuration.

For the first class of APIs, such as Number Verify, or SIM-swap detection, the key features include:

• Aggregation across as many MNOs and MVNOs as possible, to give large coverage of the user base, via a single provider such as a CPaaS company
• Creation of a range of commercial models for APIs, such as per-use, subscription-based or flat-rate
• Enable easy embedding of the capabilities into higher-level applications such as “know your customer” (KYC) or fraud management
• Dealing with national regulations on topics such as privacy and data protection

The second class of Network APIs, including those for Quality-on-Demand and network awareness, have different challenges and opportunities – and may need a different ecosystem and aggregation/abstraction model:

• Empowering service providers/operators to overcome the limitations of NEPs, allowing them to author, catalogue, transform and expose services, as well as address regional and bespoke customer needs.
• Opening up the operator’s networks, previously locked in with specific vendor hardware, while avoiding new lock-ins to specific network service exposure layers.
• Supporting multi-vendor and multi-domain networks in enterprise and consumer environments – for instance, where operators deploy private networks using different vendors to their main national infrastructure, or where indoor networks are run by third parties.
• Flexibility and adaptability to local and regional regulatory and operational constraints, such as different (and often changing) rules on Net Neutrality, or awareness of coverage gaps.
• Enabling developers to utilize capabilities beyond the operator’s mobile networks into real-life enterprise and consumer deployment, where the application relies on all programmable networks including Wi-Fi and even wired networks.

In other words, for hard network APIs, it is at least as important to deal with multiple physical network deployment and management scenarios, as it is to aggregate across multiple national operators. That is especially true for location-specific applications used in enterprise settings. Basic QoD APIs are not enough for controlling real-world networks. 

At Shabodi, we have recognized the complexity and challenges for operators, developers, and enterprises. Our platform was specifically designed to abstract these complexities, and not just expose network APIs but to accelerate adoption by simplifying API integration and application deployment.   

Of course, no one should ignore the importance of educating and inspiring application developers as well. The ecosystem model and loud voice of large organizations can help evangelize the advantages of leveraging network services, demonstrating the value network-aware applications can bring enterprises.

We are proud of the real-world use cases we have developed in partnership with application developers and solution providers across various networking domains and technologies. We are fortunate to be pioneers in the truly open, emerging network-aware world. 

Shabodi NetAware is the industry’s first programmable network platform designed to simplify the development and deployment of network-aware applications. The platform leverages GSMA Open Gateway principles to discover, transform, and expose Network APIs based on CAPIF standards. We have taken NetAware to include API authoring and exposures covering other programmable networks seen in enterprise environments. While the platform supports CAMARA and TMForum standards, the operators using Shabodi NetAware can go beyond to meet the evolving connectivity needs of enterprise requirements in industry verticals such as manufacturing, airports, warehouses, stadiums, etc. It bridges applications and diverse network and equipment infrastructures, enabling seamless interaction, enhancing application performance, and optimizing network utilization.

Shabodi is excited to see Ericsson’s latest announcement on creating a joint venture aggregating network APIs from several telecom operators. This shows the urgency for operators to expose Network APIs to drive monetization and deliver advanced use cases. The announcement gives momentum to the efforts and awareness that Shabodi has been promoting within the industry since its inception in 2020.