Your browser is not supported. Please update it.

17 October 2005

Ericsson leads move to bring Java to IMS, challenging Microsoft

Telecoms has traditionally been a world of closed architectures and specialized programmers but various factors are making it increasingly resemble the enterprise market, with its high level software architectures, web services and the fundamental split between Microsoft .Net and Java. The main factors are the drive towards convergence and all-IP networks, the need to support more sophisticated, data-driven mobile applications; and at the same time to reduce costs by using standardized platforms and tools. Like the large enterprises, the operators are looking to deliver applications as services, and to adopt uniform development frameworks across all platforms, and these trends will be accelerated by the adoption over the coming few years of the IP Multimedia Subsystem (IMS), for provisioning, integrating and delivering IP services from the core network. This puts critical focus on the upper layer software that will make IMS more manageable by automating or simplifying many of its functions. The enterprise suppliers, notably Microsoft and IBM, are bringing their .Net versus Java battle into the telecoms sector, with Microsoft gaining favor among some major converged operators, but IBM leveraging the mobile hardware makers’ commitment to Java to strengthen its own hand.

If IBM and the mobile vendors have their way, Java will take on the role of unifying development and delivery platform for all advanced mobile and converged networks. Last month we saw Nokia taking the lead role in bringing Eclipse, the strongest Java tools framework, to the mobile world. This month, fellow Scandinavian giant Ericsson is to head up an important effort to define IMS services for Java mobile devices, within the Java Community Process, the semi-open mechanism that develops and enhances the software technology.

Ericsson, working with BenQ Mobile (formerly Siemens Mobile), will lead the specification development, claiming that using Java for IMS services will make the creation and deployment of these services simpler and cheaper. The Java Specification Request (JSR-281) will define a high level application programming interface, which will offer services level support for development of IMS applications. JSR-281 will consist of at least three types of functionality ‘ high level IMS core functionality, Push to Talk over Cellular (PoC) services, and group list management services.

This will enable the mass of the Java developer community to be brought to the service of IMS applications, which will be important in creating a strong base of affordable software. J’rgen Lantto, vice president of strategic product management at Ericsson Mobile Platforms, believes high level programming tools and standards are a critical success factor for IMS adoption. “Making IMS capabilities available for the Java developers will allow the wide community of Java application developers to bring interactive multimedia services to the consumers. We expect that this will speed up the commercial launch of IMS by mobile operators and terminal vendors,’ he commented.

Java will also further the cause of making different operators’ IMSs interoperable, if they are adopting similar Java/web services approaches, as well as harnessing the existing dominance of the Sun technology as the primary platform for aggregating and delivering mobile content and services. Most advanced handsets now support Java and even high level content aggregation platforms like Qualcomm’s Brew can handle Java applications, while other important content frameworks ‘ like Nokia’s Preminet ‘ are entirely geared around Java, and will gain in scope and importance in an IMS environment.

Also benefiting from a tight coupling of Java and IMS in major operator deployments will be those Java-oriented companies looking to sell their service delivery platforms (SDPs) as a layer sitting above the IMS. Most important is the Converged Multimedia Services (CMS) platform codeveloped by Nortel and IBM, which combines IMS functions with an IBM service delivery platform. Nortel provides the SIP-based link between the core network and the applications layer, while IBM, using tools like the Java-oriented WebSphere, offers the high level middleware to deploy and integrate the applications easily, without the extensive customized work that would be required to do this in IMS itself. Other vendors, such as Sun, Hewlett Packard and BEA Systems, are working on similar approaches oriented towards Java, though they lack the strength of carrier class partners that IBM can command, with its close ties to Nokia’s Java/Eclipse efforts as well as its Nortel joint venture.

The major alternative to IBM and Java for making IMS a usable reality is, of course, Microsoft .Net, and the software giant is pursuing the all-IP telecoms market relentlessly. Its answer to the IBM-Nortel CMS is its Connected Services Framework (CSF), which can sit above IMS and allow two servers, running different applications, to work in cooperation through .Net protocols and web services. This is 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).

As with other services frameworks, CSF works with IMS (although it can also, like other SDPs, work alone and function as a halfway house to full IMS deployment). It provides network services to applications, rather than defining communications standards between the applications. The IMS takes away the need to rebuild all the service functions every time a telco 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, further up still, the connections between these applications.

This is what Microsoft does best. It takes a set of software functions and writes them once, and effectively makes them cheap, reducing the need to program a link between a new application and existing applications ‘ vital when operators will be looking to deploy new services and applications at the rate of several per month in order to keep customers interested and loyal.

As telcos are moving to triple play using IP, need to offset voice revenue erosion by offering new services and content rapidly, and Microsoft 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. And Microsoft aims to provide the server software underpinning many of those services as well as the connections between them, just as Java will be looking to do. A server is required to run the CSF services, another to run Xbox Live gaming. 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, Exchange (which in turn relies on Active Directory), and then of course there are other business services like Sharepoint document management and Netmeeting services, all offered by telcos and all potentially needing to talk to each other.

And like the Java supporters, Microsoft will have a huge developer community to leverage ‘ something it has done far more successfully in the past than its rivals, with Nokia and others just starting to catch up in terms of sophisticated developer programs and incentives.

The idea behind IMS is to 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. IMS doesn’t do all the work, but it creates a great basis for building new trans-network applications. CSF 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.

As in many other areas of mobile systems, Microsoft’s dilemma will be how far to open up its architecture to rival the openness of Java, but potentially risk revenue for its own server software. It will severely compromise the concept and benefits of IMS if it supports and connects only Microsoft presence servers, IPTV systems and other services, risking a world where a great deal of progress is made ‘ by bodies like the GSMA ‘ towards making IMSs interoperable, only to find that, at the services level, Microsoft customers are marooned on their own island. Increasingly, Microsoft has to derive its power from providing the integration technology for operating systems, applications and servers from all vendors, rather than seeking to create an all-Windows/.Net environment away from the PC world ‘ and from the weight of its developer community. Otherwise, despite the enthusiasm of some converged operators such as BT and Bell Canada, and its key partnership with Alcatel, it will stand little chance of taking a major role in the mobile telco market alongside the growing power of Java.

BOX Nokia’s latest developer programs

Nokia has become highly aware of the need to attract and support developers for its Symbian and Series 60 software platforms. Its latest move is to launch an early access support program, Forum Nokia PRO Symbian Zone, to offer members reduced development time and costs as a result of close cooperation with Nokia and Symbian.

They will receive updates of the latest Symbian OS Library for application developers, a newly developed resource containing the up-to-date Symbian OS API documentation.
Access to the Forum Nokia PRO Symbian Zone is free to Forum Nokia PRO member companies who sign a Symbian Affiliate Program license agreement through the Forum Nokia PRO site with Symbian.