Your browser is not supported. Please update it.

5 October 2005

Microsoft CS Framework opens telecoms to the .Net programmer

Michael O’Hara is the General Manager, Microsoft Communications Sector, which means that whenever Microsoft sells something to a telco, he’s going to get the credit.

So he will have been getting a lot of credit lately, what with IPTV and Connected Services Framework making a major impact on telco thinking these past few 12 months. And it turns out that O’Hara has a brave new take on how to support Telcos, he wants to partner with them, give them all the software they need for free, and then take a share of their upside revenues. That’s a far cry from the usual Microsoft business model and creates annuity service revenues for Microsoft out of one up front effort.

‘We never really had any special offerings for telcos, so I just used to get credit when telcos bought copies of Windows or Office applications,’ quips O’Hara, ‘but now Microsoft is serious about getting into telcos,’ he says.

In fact it soon becomes clear that Microsoft has set its stall out to be the savior for incumbent telcos that are hard pressed to cope with what the Internet protocol is doing to their business.

The session was supposed to be about Connected Service Framework, a set of server based services that we haven’t tried too hard at Faultline, up until now, to understand. It’s a kind of baby version of IP Multimedia Subsystem (IMS) isn’t it? That’s how Microsoft described it when it was launched.

But the diagram below makes it clear that although it is a framework for connecting services, it’s work is all carried out at the server level. When O’Hara talks about managing a session, he is not talking pure IP, and setting up and tearing down an MPLS tunneling session, but instead is talking about two servers working in co-operation through .Net protocols.

It’s more about SOAP than SIP (Session Initiation Protocol is the basis of the network control functions within IMS while SOAP is one of the key a web services protocols behind .Net).

Certainly there is a lot of overlap with IMS. It has its own Service Framework but this is to provide network services to applications, not to define the communications standards between the applications. It’s a subtle difference and there is room for lots of confusion, but now Microsoft realizes that a diagram that shows CSF asking IMS for network functions is better than a CSF diagram claiming it can do all the advance IP convergence work at the network level and then ending up having to hard code many of the basic network functions for clients.

If a telco installs an IMS it takes away the need to rebuild all of the service functions every time he wants to build a new service for customers. Functions such as authentication, session initiation, service requests, group list management, presence, charging, interoperability and roaming are all handled in a standard way.

The applications logic sits on top of this and O’Hara draws on top of that the connections between the applications, CSF.

Make no mistake, this is a major onslaught into the Telco business to make them utterly dependent upon Microsoft software. But this is what Microsoft does best. It takes a set of software functions and writes them once, and effectively makes them cheap. Imagine the difference between installing CSF and asking IBM Global Services to program a link between a new application and existing applications.

Telcos are moving to triple play using IP, they are driving up broadband deployments and want to offer all kinds of services to offset the rapid erosion of traditional voice revenues. They need to offer new services rapidly over the IP protocol, new content, with new content tools such as DRM and O’Hara thinks that service delivery is going to be the killer application for telcos. If they can get a service off the ground faster than the competition, they will keep customers, simple as that.

O’Hara’s next slide really begins to put over the message. Not only are there a considerable number of potential services that may come out of Microsoft for telcos, but there are an awful lot of Microsoft servers in the picture below.

A server is required to run the CSF services, another to run Xbox Live games services. There are multiple servers in the MSTV service, some for broadcast content, some for middleware and fast channel change services, yet more for Video on Demand. A partnership announced in June with Sylantro introduces the idea of a voice server to link VoIP applications to all the other applications, there are presence servers, copies of Exchange, which in turn relies on Active Directory, and then of course there are other business type services like Sharepoint document management and Netmeeting services, all offered by Telcos and all potentially needing to talk to each other.

What’s the upshot of all of these connected services?

This is where O’Hara, with his mischievously Irish accent, becomes animated and insists on a demonstration, because this is where the service connection comes into its own.

‘Imagine that you are sitting watching TV and your friend in another part of town turns on the TV. A presence application can be set to load when he turns on his TV. Your TV gives you a presence menu right there on the TV and you can use the remote control to create a picture in picture window to see what your friends is watching (assuming he has given you permission to view this at some previous point).

‘Let’s say that it’s racing or some other sport and you both decide to watch together and chat about it either on an instant messenger or you use the Sylantro VoIP server to talk, again with just a point and click of the remote (you also have to find the headset). There are also icons for all the other services that the particular telco has connected to these applications. For instance the two friends can go to an Xbox Live server and begin playing a related game, while still watching the TV program in a window, while still talking.’

O’Hara clearly buys into this vision and thinks that Microsoft can deliver it all, but in the same way, that’s the vision that has been driving the IMS work. Initially this came out of the trials and tribulations of trying to get a mobile phone, which uses one of several switched circuit protocols, to work with landlines and other varieties of mobile phone such as GSM, CDMA, UMTS and all their data variants.

The idea behind IMS is to use the Internet protocol and offer common services for applications to use and to route any conversion work, such as real time conversion of video codecs, to network gateways that can manage real time translation.

The appearance to the customer will be that all phones work together on any network and can use advanced data services in the same way. IMS doesn’t do all the work, but it creates a great basis for building new transnetwork applications.

CSF, as far as we can see is a way of harnessing the power of .Net developers everywhere and giving them the tools to write the rest of the applications straight onto the network.

Of course there remain overlaps with IMS. Is presence dealt with within IMS or on CSF, is billing data collected by IMS and sent directly to a billing application or is it transmitted to Microsoft’s billing partner Amdocs by the CSF server? Well both are possible and there are probably many other management jobs where the two layers are talking backward and forwards and where someone, at implementation, has to decide which of the two layers will manage a particular request.

You may ask if the Microsoft presence server works with other instant messengers other than its own? If not then it’s pretty useless. O’Hara’s examples of sharing services have to happen as global events. The two friends may be in different countries on different IPTV systems, but they may have many of the same functions. They should work together, and that can be facilitated at the SIP level or at the SOAP level, but someone has to facilitate it. Or else we will be heading for a world where Microsoft IPTV customers are in one island that never talks to those implemented in another technology.

CSF was only launched this February with Bell Canada, Celcom Malaysia and British Telecom rolled out as the first to try it. Since then AT&T has adopted it as the foundation of its Service Oriented Architecture, the agreement with Sylantro on VoIP has been struck and the system is being integrated onto CSF by porting the Sylantro VoIP features onto a Microsoft server. The first rollout for this VoIP service will be with Qwest in the US.

The deal with Amdocs was very quiet and a parallel deal has been cut between Alcatel and Amdocs so that IPTV can be billed by Amdocs, but there is now a billing relationship between Microsoft and Amdocs on all of the services that you can connect on CSF.

It would make perfect sense for Microsoft to acquire Amdocs, because they are now so close and Amdocs is porting selected applications onto Microsoft servers.

One thing is clear from this perspective, and that is CSF takes Microsoft closer and closer to both Alcatel and Amdocs. At first we nicknamed this union Walcatel, now it should be WamCatel to include the third partner.

Where once they were only working together on IPTV, it now looks like both Alcatel and Amdocs will bump into their IPTV partner at almost every new application that Telcos take up. This week (see separate story) we find that Alcatel has written its own IPTV applications (MyOwnTV and AmigoTV) on top of Microsoft’s IPTV platform.

And these relationships are set to create the same kind of interdependence that Intel and Microsoft have shared this past 25 years.