Your browser is not supported. Please update it.

14 June 2006

IBM moves to next gen Service Delivery, targeting IMS

It may not be widely known but IBM is providing the Service Delivery Platform for the AT&T IPTV services and this week showed off a revitalized toolset to analysts at its Austin Texas Telecommunications Solution Lab.

This was effectively the Rational Software toolset, linked to other services such as TiVoli’s security and systems management products and the more recently acquired NetCool service assurance software, all geared up to offer fast to market agile service creation.

Why then was Microsoft not insistent that its Connected Services Framework was used as the basis for the AT&T deployment? According to IBM it was Microsoft itself that insisted at the time that CSF was not ready for prime time, which opened the door for IBM, which believes itself to be clearly in the lead for Service Oriented Architectures and service delivery.

Just last week IBM announced new middleware versions off the back of this project, aimed fairly and squarely at taking this lead in service delivery to more telecommunication operators. It announced IBM Websphere IMS Connector, so that it can control an IMS from the same service definitions as it is using already pre-IIMS, and added both the IBM Websphere Presence Server and IBM Websphere Telecom Web Services Server.

The whole issue of Service Oriented Architecture within networks is to separate out each function that the underlying network can offer, and then offer an abstracted level of these functions in J2EE that can be rapidly re-combined for rapid prototyping, testing, and deploying using web services.

At the moment whenever a telco wants to build a new application it suffers from its old way of doing things and its legacy of separate silos of software. In each service built over the years every job such as service provisioning, billing, customer self help, customer care, order management, inventory, and subscription management functions have all been written from scratch for each new application. Operators have become obsessed with moving everything to IP based services using IMS (IP Multimedia Subsystem) but currently have a spaghetti of service connections, which no-one can unravel in under 18 months to two years and what should be a simple process, spirals into a mammoth undertaking.

‘You can’t talk in years any more when you talk to telcos,’ said David Mangini, Global solution owner, Service Delivery Platforms, ‘you can say 24 months to someone, but never mention years. The network is complicated enough without going to the trouble of implementing IMS. And most networks are going to get more complicated before they get simpler,’ he said.

Which is the entire point of the IMS Connector. IBM hopes that using Rational as the basis for planning, designing, prototyping and implementing new services on a network, it can then seamlessly move them to run on IMS, as operators deploy it. That way it can leverage any services that have been deployed since 2001, when it first introduced its Service Provider Delivery Environment (SPDE pronounced Speedy) and move then straight onto an IMS as operators deploy them, without adding to all that complexity.

‘The Service Delivery Platform (SDP) is separate from the IMS,’ said Mangini. ‘and it can take existing legacy services and merge them into composite services that can underpin a new consumer offering,’ he said.

Already IBM is working on mobile TV deployments with a series of carriers in Europe and is behaving agnostically as far as protocol goes and has partnerships with Qualcomm and Nokia and Crown Castle in mobile TV.

‘Often it’s the use of multiple OSS’s that triggers the need for an operator to move to an automated SDP, and today it’s all about web services, SOA and SIP. When you finally look at what that means to the network, yes it means a lot more servers in the network, and it means many of these are far closer to the consumer, but new services can then be launched in about 90 days,’ claims Mangini.

IBM gave some details of its implementation at AT&T, but was for more forthcoming about its work with Sprint, where it has run the SDP for Sprint’s Business Mobility Framework, a set of services that help enterprise users get to their core applications when they are on the road.