Telco standards gone, dead and buried

Originally posted on 22Auc12 to IBM Developerworks (13,006 Views)

Further to my last post, it now looks like the WAC is completely dead and buried. One thing that is creating a lot of chatter at the moment though is TelcoML (Telco Markup Language) – there it a lot of discussions about it on the TeleManagement Forum (TMF) community site and while I don’t intend to get in a big discussion about TelcoML, I do want to talk about Telco standards in general. The Telco standards that seem to take hold are the ones with strong engineering background – I am thinking of networking standards  like SS7, INAP, CAMEL, SigTRAN etc, but the Telco standards focussed on the IT domain (like Parlay, ParlayX, OneAPI, ParlayREST and perhaps TelcoML) seem to struggle to get real penetration – sure standards are good – they make it easier and cheaper for Telcos to integrate and introduce new software; they make it easier for ISVs to build software that can be deployed at any telco. So, why don’t they stick? Why do we see a progression of standards that are well designed, have collaboration of  a core set of telcos around the world (I’m thinking the WAC here) yet nothing comes of it.  It we look at Parlay for example, sure CORBA is hard, so I get why it didn’t take off, but ParlayX with web services is easy – pretty much every IDE in the world can build a SOAP request from the WSDL for that web Service – why didn’t it take off?  I’ve spoken to telcos all around the world about ParlayX, but it’s rare to find one that is truly committed to the standard – sure the RFP’s say must have ParlayX, but then after they implement the software (Telecom Web Services Server in IBM’s case) they either continue to offer their previous in house developed interfaces for those network services and don’t use ParlayX or they just don’t follow through with their plans to expose the services externally: why did we bother? ParlayX stagnated for many years with little real adoption from Telcos. Along comes GSMA with OneAPI with the mantra ‘ParlayX web services are too complicated still, lets simplify them and also provide a REST based interface’.  No new services, just the same ones as ParlayX, but simplified. Yes, I responded to a lot of Requests For Proposal (RFP) asking for OneAPI support, but I have not seen one telco that has actually exposed those OneAPI interfaces to 3rd party developers as they originally intended.  So, now, OneAPI doesn;t really exist any more and we have ParlayREST as a replacement.  Will that get any more take up? I don’t think so. The TMF Frameworx seem to have more adoption, but they are the exception to the rule. I am not really sure why Telco standards efforts have such a tough time of it, but I suspect that it comes down to:

  • Lack of long term thinking within telcos – there are often too many tactical requirements to be fulfilled and the long term strategy never gets going (this is like Governments who have a four year terms not being able to get 20 year projects over the line – they’re too worried about getting the day to day things patched up and then getting re-elected)
  • Senior executives in Telcos that truly don’t appreciate the benefits of standardisation –  I am not sure if this is because executives come from a non-technical background or some other reason.

 What to do? I guess I will keep preaching about standards – it is fundamental to IBM’s strategy and operations after all – and keep up with the new ones as they come along.  Lets hope that Telcos start to understand why they should be using standards as much as possible, after all they will make their life easier and their operations cheaper.

WAC Whacked: Telecom-Backed Alliance Merges Into GSMA, Assets Acquired By API Management Service Apigee | TechCrunch

Originally posted on 17Jul12 to IBM Developerworks (9,830 Views)

Apigee, the API management company that was most recently spotted powering that new “print to Walgreens” feature in half a dozen or so mobile applications, is now acquiring the technology assets of WAC, aka the Wholesale Applications Community. WAC, an alliance of global telecom companies, like AT&T, Verizon, Sprint, Deutsche Telecom, China Mobile, Orange, and others (and pegged by TechCrunch writer Jason Kincaid back in 2010 as “a disaster in the making“) was intent on building a platform that would allow mobile developers to build an application once, then run it on any carrier, OS or device. The group also developed network API technology, which is another key piece to today’s acquisition.”

TechCrunch – techcrunch.com/2012/07/17/wac-whacked-telecom-backed-alliance-merges-into-gsma-assets-acquired-by-api-management-service-apigee/

I think this is a really interesting development.  The Wholesale Application Community (WAC) was supposed to give Telcos a way of minimizing the revenue losses to the likes of Apple’s App Store and Google Play.  IBM’s Telecom Solution Lab in France built a demonstration that was shown at Mobile World Congress (MWC) in 2011 demonstration how a Telco’s own app store could incorporate applications from the WAC App store  as well as other app stores within their own combined app store.  I’ve demonstrated this a number of times around the world and the thing that always seemed odd to me is that applications in the WAC App Store could not be native applications (for Android, Blackberry, WinMob or Symbian) but rather, they could ONLY be HTML5 based apps.  That was always going to limit the number of apps that would be in the WAC App store, but since the WAC was announced at WMC 2010, the number of apps in the store has never really taken off.

I’m not sure if this is effectively the end of the road for the WAC, or if it’s just a stop on their journey.   Certainly, the Telcos that I have dealt with that form the core WAC Telco members remain dedicated to the WAC. I guess we’ll have to wait and see what happens.