Skip Links

Network World

  • Social Web 
  • Email 
  • Close

Whatever happened to IMS?

The state of IP-Multimedia System technology
Convergence & VoIP Alert By Steve Taylor and Larry Hettick , Network World , 11/14/2007
Steve Taylor
Sign up for this newsletter now!

Today, we’d like to launch a “mini-series” on the state of IP-Multimedia System technology and deployments that will span the next several editions of this newsletter. In the series, we will interview several key players who have a large stake in the success of IMS, including some IMS component suppliers and three carriers who have embraced an IMS strategy for service deployment.

As a prelude, we remind our readers that IMS is an architectural framework for delivering IP multimedia services and applications to users. The initial framework and standards were initially developed by the Third Generation Partnership Project (3GPP), and were first designed to serve GSM-based cellular networks, but the standards have evolved to support wireless LAN, CDMA 2000, and wireline networks.

As an architectural framework, IMS does not specify how applications should be developed; rather the framework is designed to provide a common architecture that lets wireless carriers and wireline carriers interoperate between networks in supporting common applications and services. IMS also relies on Session Initiation Protocol (SIP) to provide session control. IMS has the potential to play a critical role in fixed-mobile convergence (FMC.)

And in the interest of fair journalism and analysis, we also disclose the hypotheses we will test and the pre-dispositions we hold as we launch this series. We believe that, “on paper,” IMS is a great idea. But we think that IMS deployments are rolling along very slowly due to many factors.

First, since IMS relies on SIP for session control and since fewer that two-dozen VoIP features have proven multivendor interoperability we think that one big roadblock to IMS deployments is the lack of agreements on how SIP should be deployed in multivendor equipment.

Second, since IMS must work in a carrier environment, IMS “hooks” for carrier operational support systems (OSS) must be in place for any scalable deployment and we find that IMS support for OSS is minimal at best.

Finally, we hypothesize that wireless carriers and wireline carriers who don’t operate sell both wireless and wireline services may have a vested interest on slow-rolling IMS-based FMC solutions while carriers that do operate both network types may hesitate to give up revenue or to change their existing business models for voice minutes of use.

Partner Content
Foundry Networks

The Foundry Enterprise Advantage

Foundry Networks, Inc. (NASDAQ: FDRY) is a leading provider of high-performance enterprise and service provider switching, routing, security and Web traffic management solutions. Foundry's customers include the world's premier ISPs, metro service providers, and enterprises.

For further information on Foundry Networks please click here.

Leveraging the Advantages
of a Multi-vendor Network Strategy

Today's enterprise network provides more than simply a technology infrastructure. It's an enabler for the enterprise, supporting mission critical applications, creating operational efficiencies and increasing productivity gains. Foundry Networks provides the ideal foundation for a multi-vendor network.

Click here to view whitepaper!

Comments (1)
Login
Forgot your account info?

RE: Whatever happened to IMS?By Brian Savin on November 14, 2007, 10:26 amThis will be an intriguing and, if done well, highly contentious analysis! Look forward to it.

Reply | Read entire comment

View all comments

Add comment
Anonymous comments subject to moderator approval. Register here for member benefits.
Have a NetworkWorld account? Log in here. Register now for a free account.

Videos

rssRss Feed
Save The Date!
What They Are Saying

Investment of a Technology should be 'held off' because there hasn't been enough investment in it yet? Is...- Anonymous

Join the Discussion