GSMA Open Gateway and CAMARA initiatives

Nokia is pursuing a strategic commitment to leverage the broader B2B digitalization ecosystem and drive new business models that unlock the potential that network APIs can deliver from the perspective of innovation, sustainability, collaboration, and productivity.

By making network programmability monetizable, the company’s flagship API solution, the Network as Code platform with developer portal, gives developers a meaningful way to create enhanced software applications and experiences for their customers while providing operators a viable new pathway to utilize their 5G assets for enterprise and consumer value creation.

Nokia has signed collaboration agreements with almost 20 operators and ecosystem partners in Europe, North and South America, and Asia to use the Network as Code platform since its launch almost one year ago.

The platform has been shaped using technical standards produced through industry initiatives such as the Linux Foundation CAMARA project and the GSMA Open Gateway initiative. It is based on a revenue share model between developers, operators, and Nokia as the platform provider.

Network API standardization: GSMA Open Gateway and CAMARA

Shkumbin Hamiti delves into the advancements achieved through GSMA's Open Gateway and the Linux Foundation/GSMA CAMARA initiatives. Launched in early 2023 and 2022 respectively, these initiatives have garnered extensive industry support, promoting open, collaborative network architectures. Hamiti highlights the critical role of standardized APIs in simplifying access to network functions, the importance of stringent security measures, and the necessity of developer-friendly tools and documentation. He emphasizes the ongoing need for robust customer success programs and flexible monetization models to drive further adoption and innovation in the telecom API landscape.

ADM: Can you talk about the progress we have seen to date, through GSMA's Open Gateway initiative and the Linux Foundation/GSMA CAMARA initiative, in getting operators to take steps to open their networks; what does that progress mean in practical terms?

Hamiti: We have seen important progress with both GSMA's Open Gateway and the CAMARA initiative since they were launched in early 2023 and early 2022, respectively. 

Many dozens of partners have joined both, highlighting strong industry support for more open, collaborative, and scalable network architectures. The numbers continue to rise, and the work of both groupings has really marched forward in a very complementary fashion. 

GSMA, with its focus on standardizing and simplifying access to networking capabilities through APIs, has successfully pushed a unified framework for developers to access network functions to jumpstart innovations and use cases in telecom services.

CAMARA, with a more technical development focus that includes creating standardized APIs, is the engine behind providing the open-source framework and tools imperative to developing and implementing APIs across different networks and platforms.

What all this means is that the conditions are being meaningfully put in place for getting networks on the same page for developers so they can innovate in this space; for delivering new services and better customer experiences. A decade ago, we had nothing of the kind in place.

At Nokia, we see the network API market and this whole arrangement of collaboration and partnership as a mesh ecosystem; one in which operators are working with multiple aggregator partners, including enterprises, simultaneously to reach the developer and solution provider market.

ADM: A lot still has to happen for this renewed network API effort to reach critical mass with operators, enterprises, developers, and hyperscalers. Can you elaborate on what else we need to see to make that happen?

Hamiti: A first point to underscore is that all players in the mesh ecosystem only derive value when network APIs are consumed by developers and solution providers – this is the biggest challenge in the industry today.

Beyond that, we have seen major operators around the world join GSMA Open Gateway and CAMARA alike, and we need to see more, of course. This is about operators building a greater comfort level, understanding what their peers are doing, what progress is made with developers, and how certain challenges are being addressed. 

Security is another dimension. Everyone agrees, including operators and enterprises, that all APIs need stringent security and privacy standards; and GSMA and CAMARA are working diligently here. Ensuring data transmitted through APIs is encrypted with high reliability; having robust authentication mechanisms to verify the identity of API users; complying with global and regional data protection regulations such as the European Union’s GDPR - all these factors and more are critical.

From a developer perspective, we need to ensure we are giving them all the tools they need, ideally in one place through one-stop shopping; facilitating and simplifying developer usage of network APIs; and helping them understand the potential and the opportunity here. 

This means having Software Development Kits (SDKs) tailored to different programming environments to simplify the integration process; easy-to-use developer portals with all the necessary ingredients like detailed API documentation; and Sandbox environments that facilitate developer experimentation. Delivering these tools and ensuring that developers and the whole mesh ecosystem we are developing are aware of them is crucial. 

From a hyperscaler point of view, we all know the importance of these players because of the scale of their cloud infrastructure, innovation capacity, and very large, well-established developer communities. And that is why we see a lot of collaboration taking place between the hyperscalers and all the mesh ecosystem partners in driving network APIs forward. They have an important role to play.

And I think the opportunity speaks for itself. Analysts IDC, for example, recently projected revenues for telecom and network APIs to reach $6.7 billion in 2028, up from just $700 million in 2023; so very substantial growth expected.

ADM: What steps, what approaches should telecom operators be taking to ensure strong buy-in from developers and enterprises for their API offerings?

Hamiti: I think generally it’s about taking a holistic approach that combines technical excellence with robust support structures; showing the path forward for monetization; having strong commitments and procedures in place with respect to security, which is particularly important for operators and enterprises. 

More specifically, I am thinking a package of factors such as:

• developer-friendly documentation with easy onboarding guides, tutorials, and sample code for networks to help developers understand and integrate APIs quickly.
• clear and attractive monetization models with flexible plans and offerings; for example, being able to access basic API functionalities for free and having to pay for more advanced features; usage-based pricing for enterprises.
• having in place strong customer success programs, including chat support, dedicated account managers, and training programs, to ensure that developers succeed in delivering value to enterprises, and enterprises recognize the value.

ADM: What are the primary challenges telecom companies face in creating tangible value from their API initiatives?

Hamiti: I think there are multiple and some of these we have already touched on, like security. Operators need to ensure their APIs are secure and rigorously comply with industry standards and government regulations.

Standardization work continues as we speak, and we need to ensure that API protocols and formats are in place; otherwise, you have interoperability issues and, therefore, integration and usability issues across different platforms.

The value proposition, of course, needs to be clear. What problem or problems is ‘X’ API going to solve [which ties into the point I made earlier about the right business and pricing models] and being clear on the monetization strategy are critical to attract developers and enterprises.

Finally, I would say here that I think there is also a mind shift required for all. The network API market is still relatively small. The mesh ecosystem needs to develop skill sets and capabilities, including, as I said earlier, strong customer success programs to drive satisfaction with developers and enterprises.

ADM: What are the most common obstacles developers encounter when integrating with telecom APIs, and how are these being addressed?

Hamiti: I think there are a number of areas where barriers need to be removed.

Take API documentation. There is still ample room to optimize how that process is done to make it clearer, with better details and standardization. And the good thing is that CAMARA continues to make progress here with all the mesh ecosystem partners.

Security and authentication, as I have pointed out already, are another. It is a fine balance between having simplified authentication tools, while achieving rigorous security embedded in these tools.

There are integration issues that require fine-tuning so that APIs work seamlessly within a network environment. For example, there is a need for multiple programming languages when it comes to SDKs to ease integration issues. Greater use of API gateways to manage different APIs and systems is another way of addressing those issues.

I would also reiterate the point about business and pricing models. There needs to be flexibility in the licensing of network APIs; pricing should be multi-tiered to give the mesh ecosystem optionality, “freemium” access, with a tiered approach as you move up the premium scale.

ADM: How can telecom operators better communicate the potential benefits of their APIs to attract a broader developer community?

Hamiti: There are a variety of forms this can take.

Organize workshops and webinars that showcase the capabilities of APIs. Those types of activities promote information sharing, education, and awareness on things like case studies, topical issues such as security; and they just elevate the collaboration ethos among all the various mesh ecosystem partners.

Hackathons are another avenue. We at Nokia have seen success with this activity, and I know our partners have been very appreciative of this work, the relationships and insights that have come out of it, and the opportunity provided to developers to build new, innovative use cases and applications.

Industry event participation is a no-brainer.

More generally, there is a need to making sure our efforts are aligned with other mesh ecosystem partners in go-to-market strategies.

ADM: How do you envision the telecom API landscape evolving over the next year or two; what needs to happen to continue to show ‘success’?

Hamiti: I believe the industry will continue to make significant progress and there are a few reasons for this:

First, financial motivation, and the ROI that operators need to deliver on their massive 5G investments. Operators are very motivated to make changes on their end. 

Second, opportunities. 5G-era networks are rich in capabilities - like improving network quality on demand - that can really make a difference to enterprises and consumers; and in ways that were not possible even five years ago.

Third, technical: 5G-era networks are fundamentally software-based - a step change from how networks were designed years ago - which means they are programmable by nature. We are no longer trying to open up hardware-centric networks that were never designed to be open to programmability. 

And I think those factors reflect the changing mind shift reflected in the partnership and standards work over the past one/two years with GSMA and CAMARA. There is no question we are seeing a new level of openness unlike any other time before. 

But nothing is guaranteed. There are still various issues that need to be ironed out. And, as I said at the start: It is important to understand that all players in the mesh ecosystem only derive value when network APIs are consumed by developers and solution providers – this is the biggest challenge in the industry today.

About Shkumbin Hamiti

Shkumbin is a twenty-five-year Nokia veteran based in Espoo. His distinguished career with Nokia includes successful track record of spearheading, leading, developing and influencing some of most significant developments within the mobile industry. Shkumbin held key technology leadership positions in standardization, ecosystem development, devices, GTM partnerships, and business line management. He is named as inventor in 12 granted patents and author of several technical publications. He is currently heading Nokia’s Network Monetization Platform Business Unit helping industry to unleash the power of 5G networks.