The TM Forum today announced 13 new open APIs as part of its ongoing effort to enable telecom operators to expose digital assets as services, without the encumbrance of legacy back-office systems. And this time around, the global standards group is taking a crowdsourcing approach to a process it once tightly managed, with hopes of working much faster.
The Open API program has been in the works for three years but was publicly unveiled last May at TM Forum Live! in Nice, where the original nine service provider backers were on hand. Today, 17 service providers are on board, but the Forum is expecting a couple of hundred to sign on by 2018, with mounting pressure on operators to find new revenue in the digital services realm. (See 9 Global Telcos Back Open APIs Scheme.)
Today’s announcement was part of a broader upgrade to TM Forum ‘s Frameworx standards and best practices that include updates as well to Agile IT and Internet of Things initiatives. Continual upgrades to Frameworx is not a new thing, but the way these Open APIs are being created is different, says Joann O’Brien, vice president of Collaborative R&D at the Forum.
The Open API program itself was born of recognition within the Forum that it needed both shorter lifecycles for its API development and more lightweight REST-based APIs if it was going to help its network operator members more rapidly expose digital assets within their networks, and capture digital services revenues in the process. In the first two years of the program, the TM Forum developed what O’Brien calls “crisply defined APIs like trouble-ticketing and catalog management” covering well-known functions. (See Mapping Open APIs With TM Forum.)
Beginning last summer with its Action Week in Vancouver, the Forum focused on “being able to crowdsource APIs and then govern and manage the scaling up of that effort,” O’Brien tells Light Reading in an interview. “We have put that in place and the APIs that come out this week are the first proof point of that effort.”
That means that any member company can propose an API in a particular space or bring their own management API to the forum as a suggested industry standard.
“They propose it and then it goes through a process to make sure it is not bespoke to that company, but genuinely fit as a generic API that will work for everybody,” she tells Light Reading. “And then we build out the Swagger and the Postman and the other complimenting assets and make it a package, which fundamentally makes it usable.”
For those not fluent in app-speak, Swagger specifies the RESTful contract for a given API including the details of its resources and operations so it can be used in developments and integrated into other assets as well. Postman is a toolchain for API developers to make it easier to document, test, monitor and share APIs.
As part of this process, the TM Forum has its own specs for documenting, describing and defining the API.
“Then we build the reference implementation which is executable, and we also now create what we call an API conformance profile that tells you, for every feature of the API, if it is it mandatory or optional,” O’Brien says. That last step is critical because it informs decisions by operators on how they can modify or extend what they do with that API, while maintaining interoperability.
Keep reading on Light Reading.