Your browser is not supported. Please update it.

12 December 2005

Cisco sets its IMS platform apart with a healthy dose of scepticism

On paper, Cisco should be one of the vendors to stand to gain most from the advent of the IP Multimedia Subsystem (IMS), given its power in the IP market and the fact that it serves wireless, wireline and cable operators as well as enterprises, and seeks to increase its presence in the large carrier market. But until now, Cisco has been almost alone among the networking majors in staying ambivalent about IMS, the standards-based control architecture for delivering voice, video and data services over converged wired and wireless IP networks to a wide range of end devices from phones to set-top boxes. Now at last it has come out with a full-blown IMS platform, which combined with other moves signifies a renewed assault on the large service providers, especially the cable and mobile operators. But Cisco remains the voice of caution, and while it supports more and more IMS functions, it will differentiate itself by providing a gradual approach that positions IMS as a platform for future new services, without the need to migrate legacy systems any time soon.

Much of the delay in coming to market with real IMS has probably been down to Cisco battling to come up with a workable platform that is saleable in the short term, and addresses the various needs and specifications of the cable, wireless and wireline communities right now, but also has a clear route to full convergence in future. To be fair to the networking giant, this is a difficult balancing act that some vendors have not bothered to address in the first phase, instead launching ‘IMS strategies’ that consist of little more than a few stage one applications and mechanisms ‘ such as push to talk or Unlicensed Mobile Access – cobbled together under a marketing slogan.

Cisco has not felt that the market was ready for a full IMS, believing that the big bang approach would be overly costly and complex and that most operators would make their way to IMS piecemeal. The company chose to rework certain existing products rather than creating a true IMS, a gradual approach that is still evident in the new, more coherent platform, which is designed to support non-IMS and fully standard services. As such, it may have an advantage for certain operator types looking for an early move to IMS, particularly the cable sector, on which Cisco has concentrated many of its recent efforts, targeting those providers’ shifts towards a fully triple play offering with actions such as the acquisition of set-top box and video distribution specialist Scientific Atlanta.

The key to Cisco’s evolving IMS approach is its Call Session Control Platform (CSCP), a family of proxies for SIP (Session Initiation Protocol, the keystone of IMS) that were designed to be aligned architecturally with the IMS Core Session Control Functions (CSCFs ‘ see box). The idea is that Cisco’s own SIP elements would map to standard IMS functions, so that the latter could be introduced relatively simply, and one by one, as the market requires, without major architecture reworking. Therefore operators are promised a lengthy grace period in which they can move at their own speed from current to IMS functions, mixing and matching the two. Cisco has also addressed the issue that the different operator groups have defined variations on IMS, some of which are incompatible. In its pursuit of the multi-network carrier, it has selected to support core IMS functions that are common across the wireless, telephony and cable sectors.

Since even the largest operators are viewing IMS with caution, and not looking to implement the architecture end-to-end until late in the decade, Cisco should find its approach appealing to many carriers, especially in the mid-tier where it has the greatest influence.

The main products at the heart of this architecture are Cisco’s PGW2200 PSTN Gateway ‘ widely used in VoIP networks – its BTS 10200 softswitch, and the CSCP. It also says its MGX 8880 media gateway, which it believes to be the first MPLS-enabled media gateway for wireless, wireline, and cable networks, is now optimized for packet delivery over cable and to support IMS as well as non-IMS applications.

Key to Cisco’s progress in this market will be its strength in VoIP, most commonly the first IP application that operators are looking to deploy over converged wired-wireless networks. The PGW2200 Gateway has, therefore, been reworked so that, when a provider moves to IMS, it can remain in place and take on the function of the Media Gateway Control Function (MGCF), one of the standard elements of the IMS.

Also demonstrating how Cisco has adapted its core products to take on this transitional role from proprietary to IMS, the BTS 10200 softswitch now interoperates with CSCF, the main network policing function in IMS, and can take on a media gateway role within an IMS too.

In effect, then, the Cisco Call Session Control Platform and associated products are being reshaped to become merely Cisco implementations of IMS standards, but with backwards compatibility for existing major users, notable among them Sprint Nextel, which has used the product for two years for SIP-based services such as 3G push to talk.

In true Cisco style, the company will also include more and more functionality into its platform, including elements that most other IMS vendors take from specialist third parties ‘ such as the Session Border Control, now embedded into its XR 1200 carrier router.

Also, it will concentrate initially on applications where it has track record and where it feels it has a headstart on other vendors. Particularly targeted in the first phase are voice over broadband, cable triple play, wireless push to talk, and enterprise fixed-mobile convergence, all important early applications for IMS-type systems. Its Service Exchange Solution for IMS consists of Cisco and partner products which map to the IMS specification and support a range of services.

The approach shows how Cisco will look to challenge the major carrier suppliers in the critical IMS market. Cisco, while strong among metro carriers, tends to occupy dark corners of the tier one operators’ systems, overshadowed by the tight account control of the large telco equipment suppliers. Many major carriers look set to procure their IMS platforms from their primary vendors, such as Alcatel or Lucent, but as they move increasingly rapidly towards all-IP, the systems they source from Cisco will inevitably take on greater significance in the overall architecture, and give the supplier an opportunity to seize the role of main IMS provider ‘ something it will clearly be coveting at Sprint Nextel.

The hard work Cisco has put into supporting the cable industry’s peculiar approach to packet data and IMS should also start to reap some dividends, especially when combined with its moves to support multimedia services deliver in other ways, notably with the Scientific Atlanta purchase. Creating an end-to-end triple play system for cablecos to deliver packet-based multimedia services in line with those that will be launched by the telcos and cellcos would be a major selling point and an area where it could leap ahead of many major IMS providers, which despite their headstart have generally been more focused on the 3G and DSL operators.

The road for Cisco, then, is all about realism. Realism about its own chances to compete against the telco specialists ‘ which means identifying operator groups that they have been less focused upon, such as cable. And realism about the customer base’s own investment plans, and the fact that most are cautious, and need to preserve a legacy system, not just in terms of their pre-IP services, but also their semi-IMS first stage platforms.

Cisco is differentiating itself, and bringing a useful dose of honesty to the IMS market, by refusing to label all attempts to deliver multimedia services using packets as fully IMS. This highlights that there is a long and costly road to tread to get to the fully blown standard, and so plays to Cisco’s marketing contention that the important thing is to choose a vendor that allows the customer to move at its own pace and to maintain compatibility with legacy services ‘ and to use IMS as the basis for new services, not to migrate old ones.

It is true that, in the real world, most carriers are deploying applications that are not strictly IMS, but represent a step in that direction ‘ they are multimedia and use IP packets, but they are not real time and often not SIP-based. A good example of the latter is UMA (Unlicensed Mobile Access), which as a 3GPP standard and a method of delivering VoIP over converged wired and wireless networks is often held up as a step towards IMS. Conceptually it may be, but it does not use SIP.

And very few operators are currently deploying applications that support one of the key IMS definitions ‘ the ability to be combined with another application for just an individual session, in order to deliver a tailored combination to a particular user or group (for instance, initiating a voice call from within an IPTV video session so that a viewer can call a friend to comment on a programme).

Marketing-wise, then, it still suits Cisco to present itself as something of an IMS sceptic, albeit one that understands IP like very few others ‘ and by implication to present its competitors as jumping the gun in the market and over-promising. The company’s comments have mellowed but still carry a strong warning not to be taken in by hype. Dr John Waclawsky, a member of Cisco’s senior technical staff and author of many of the company’s most in-depth standpoints on IMS, referred earlier this year to the ‘Stockholm Syndrome’ of IMS. Like hostages who develop a dependent bond with their captors, he argued that operators ran the risk of being ‘held captive’ by IMS hype and then being caught up in the market fervor.

Waclawsky wrote earlier this year in a business review: ‘Recent incidents involving too much system standards attendance have resulted in people being captured by radical ITU-like factions known as the 3GPP or 3GPP2. Captives identify with their captors initially as a defensive mechanism, out of fear of intellectual challenges. Small acts of kindness by the captors, such as granting a secretarial role (often called a ‘chair’) to a captive in a working group are magnified, since finding perspective in a systems standards meeting, just like a hostage situation, is by definition impossible. Rescue attempts are problematic, since the captive could become mentally incapacitated by suddenly being removed from a codependent environment.’

Waclawsky’s serious point was that the IMS was becoming over complex and unrelated to real needs because of the committee-think of standards bodies. Though its concepts are seven years old already, he argued, it was just gaining additional complications rather than coming to market in a usable form.

‘Even a cursory inspection of the IMS architecture reveals the complexity that results from decomposing every device into its most granular functions and linkages; and
tracking and controlling every user’s behavior and related billing. The proliferation of boxes and protocols, and the state management required for data tracking and control, lead to cognitive overload but little end user value. The IMS is being hyped as a way to reduce the difficulty of integrating new services, when in fact it may do just the opposite. IMS could well inhibit new services integration due to its complexity.’

While Cisco is officially moving away from such arrant scepticism, its assault on the companies that have so far led the IMS race ‘ Lucent, Alcatel, Ericsson and so on ‘ will be based on the same arguments, that this beast must be tamed and simplified if it is ever to deliver real operator benefits, and that Cisco, with its heritage in VoIP and other key areas, is the vendor that understands that issue.

BOX: Elements of the Cisco architecture

The Cisco CSCP (Call Session Control Platform) is the heart of its IMS push. It provides broadband wireline, cable and wireless service providers with a distributed, intelligent SIP-based services environment for delivering multimedia applications and services over their IP-based networks. It acts as the 3GPP-defined Call Session Control Function (CSCF) in the IMS reference architecture.

The CSCP comprises three closely integrated components:
‘ The Cisco CSCP-Service Engine (CSCP-SE) provides several critical functions, including service integration and interaction; SIP message routing; user registration; authorization of service requests; and management of service and subscriber data. The CSCP-SE maps to the Serving CSCF (S-CSCF) in the 3GPP IMS specification. The IMS Service Control (ISC) interface of the CSCP-SE enables IMS-compliant applications
to take advantage of the session routing capabilities of the CSCP.
‘ The Cisco CSCP-Edge Proxy (CSCP-EP) provides the edge adaptation of SIP signaling for diverse access networks, enabling interoperability between multiple access locations and core network services and resources. The CSCP-EP provides user authentication, signalling compression, QoS signaling for access networks, security, STUN for Network Address Translation (NAT)/Firewall traversal and other adaptation functions. The CSCP-EP maps to the Proxy CSCF (P-CSCF) in the 3GPP IMS specification.
‘ The Cisco CSCP-Name Resolution Server (CSCP-NRS) is a SIP server for intercarrier and on-net/off-net routing. The CSCPNRS can be deployed as a cluster of servers for high availability, and can be shared by multiple Points of Presence (POPs). It handles the routing of calls/sessions between carriers as well as between on-net and off-net subscribers. It handles requests from any server in the network that does not have name resolution capability. The CSCP-NRS forwards SIP requests to other sites, whether they are other POPs within the provider’s network, to another SIP network through a Session Border Controller (SBC), or to the public switched telephone network (PSTN) via a media gateway controllers such as the Cisco PGW 2200. The CSCP-NRS is the Cisco implementation of the Interrogating CSCF (I-CSCF) and Border Gateway Control Function (BGCF) in the 3GPP IMS specification.

BOX

Originally defined by the 3GPP standards body (and with a related activity for CDMA operators in 3GPP2), IMS is now being extended to wireline and cable standards as convergence takes off. It provides a SIP-based control layer with open interfaces to the transport layer below and the services layer above, giving operators control over services on a per-session basis, and so far greater flexibility in how data is delivered to each user. It also promises enhanced ability to launch new services quickly and cheaply, and to integrate and reuse different voice, data and video functions to create numerous combinations and so huge numbers of new end user applications.

At its base level, IMS consists of Call Session Control Function (CSCF) software, deployed either on a softswitch MSC or on standalone hardware. Media gateways, a Media Resource Function, and a subscriber database (known as the Home Subscriber Server in 3GPP environments) are also specified.