Posted by: Tom Nolle
BT, Next Generation Networks, next-generation services architecture, standards
Danish carrier TDC is the latest to get into the API program to attempt to secure developer support to expand service features and flexibility, but the offering is still very limited.
The problem with “third-party access” has been as much what is available for access as how to access it. Most of the players, including BT, have exposed a relatively small number of mobile-related features and have used an API that is substantially based on Parlay.
We believe that more modern and “seminal” features have to be exposed and a simpler API used, but the barrier to this is lack of an effective next-generation network (NGN) services architecture. There is no easy way to create or manage composable features, and standards to support the process are stalled despite years of effort.