Also, today's "IMS R4" — until now an industry secret. Dean Bubley has already picked up on this thought.
At Spring VON, I gave a presentation on what we've learned, so far, in migrating our MyCaller ringback tones application from the Intelligent Network (IN) implementation in use by ~30 operators today, to an "IMS" version that can be deployed in networks that today are nominally based on the 3GPP's IP Multimedia Subsystem (IMS). Martin Geddes encouraged me to write up my talk.
The full article is here. For the impatient, here are the takeaways.
1. It’s very early days for IMS. Today’s “IMS” networks are combinations of SIP infrastructure with 3GPP Release 4 softswitch-controlled voice service.
2. IMS is about connection control, only. Only part of your application has to change. For MyCaller, ~90 percent of the software remains the same.
3. IMS enables multimedia ringback, i.e. video! So there is significant new functionality, versus today’s audio-only ringback.
4. Parallels with Intelligent Network are striking!
5. Most application–specific data remains outside of IMS. In particular, operators do not want to add data fields to their Home Subscriber Server (HSS).
6. Application–specific MRFs make sense. Operators tend to avoid sharing resources between diverse applications. And, for rich media, application–specific MRFs can be more cost-effective.
7. Operators await 3GPP Release 7. At least anecdotally, several operators have suggested that 3GPP Release 7 is the first complete, stable, and consistent version they will fully deploy.
Again, the full article is here.