Tsahi Levent-Levi posted an article on VoiP Survivor about the AMS and its (lack of) relation with the IMS. Furthermore he talks about the innovative nature of the AMS, expressing his hope that the AMS will not be based on stitching and patching of existing protocols. Finally he comments that: “There are those who believe that IMS is a network designed to make money, while AMS is a network designed to provide services to users”. I hope he doesn’t mean that I form part of the former group, although I’m afraid that …
AMS may possibly bring something new and fresh, I really like the focus on the service/application. Especially the idea of cooperation between end-user devices, the Jini vision comes alive again. As for the comparison between AMS and IMS, since AMS is still in its infancy it is indeed hard to compare the two. But they do overlap! And I think that therefore alone they should be compared, over and over and over. Too much money and time has been invested in SIP, XCAP and such that the overlap can not be ignored.
Also I have my fingers crossed that it stays really free of too much vendor influences. A completely academic standardisation probably wouldn’t be the best of ideas either, since a standard is for a big part meant for industrial use. A balance in this is required, in order for a standard to be successfully adopted.
As for the charging and billing stuff, it is perhaps not the sexiest thing to talk about. But if companies are investing in the development of new technology, and are putting large amounts of money in the day-to-day management and operations of services that are using that technology, someone will need to pay for that. The IP backbone and operator networks don’t run and power themselves. And phones and such still don’t grow of trees.
I’m not saying here that business models might not change, think for instance of sponsorship and such. I also think that a customer is certainly willing to pay for what he perceives as value (instead of distance times duration)!
Furthermore if technologies/networks/services are to be monetized, you should see charging, billing and settlement as an opportunity to further increase the customer experience! For instance: a customer is surely wont mind hearing that he/she received something for free, where he/she normally pays for. So why let him/her know at the end of the month on the bill, instead of immediately after or even during service usage!
To end my ramble on charging/billing: there are too many examples of projects where the order handling, provisioning, billing and other non-service customer-facing processes came last, but hugely impacted on the success of a product! Operators usually get more media attention when they screw up with their bills then when they run a cool new services.
Concluding: I applaud and follow with great anticipation any developments that push the state-of-the-art in new (multimedia) services! Be it research or industry standardisation. I however don’t expect a big-bang of mind-blowing unseen services and a customer value that has yet to be seen before.
Frens Jan Rumph
Interesting post from the CTO of NMS Communications on a study from the University of Helsinki, Finland on the usage of 3G in Finland, his analysis: ‘3G’s biggest success is as a dumb pipe‘ and we don’t need IMS, GSM over SIGTRAN over IP with an IP/MPLS core network will suffice. Dean Bubley also posted on this on his Disruptive Wireless blog. Dean raises the question: ‘is it really worth bothering about all that complex QoS, prioritisation, differential pricing, IMS etc for the remaining 5%?‘ These discussions are all based on a presentation of Antero Kivi (pdf).
Yes, it might be a bit shocking, perhaps not suprising, it probably was not the vision of 3G initiators years and years ago. But, I disagree that we just need ‘plain old’ IP access for internet with some GSM and SMS stuff on top. Sure, the days of walled gardens and the traditional one-sided telco business models are over. I won’t argue against that, and this is probably a good indication that it is.
But we will need QoS and prioritisation since some services simply have different requirements on the communications network then others and that has a tremendous effect on the QoE (Quality of Experience), which in turn is (IMHO) an important aspect of some of todays and a lot of tomorrows services. We will also need differential pricing. Flat fee will not last for ever, nor will services with a business model purely based on advertising. Perhaps we will see third-party based sponsorships in the near future, which will require differential pricing. And the IMS is an enabler for this. Especially if you combine that with the vision of research projects such as Ambient Networks and the Advanced Multimedia System. The future will tell if telco’s will become/stay bit pipes, I’d say that there are loads of opportunities to being more then that!
Frens Jan Rumph
I read an article yesterday titled AMS to the rescue, posted on VoiP Survivor. And to be honest, I was a bit shocked and puzzled. It talks about the Advanced Multimedia System which is currently being standardised by the ITU (in study group 16).
I was a bit shocked because the advances made by AMS (as described in the article) sounded like it would have a lot of overlap with the IP Multimedia System, which is being standardised for the last 8 years or so? Continuing to read the article I became a bit puzzled, since the article didn’t even mention the IMS, let alone making a comparision or describing their relationship. Furthermore, do we really need rescuing? Is this a signal from the ITU that we’re heading the wrong way with our current developments (e.g. the IMS)? This called for a little digging
Some facts on the Advanced Multimedia System:
The objectives of the AMS project are:
Some example applications of the AMS:
The AMS project envisions the following components:
My n cents on AMS:
For further information ake look at this project overview presentation (pdf) from Packetizer, it provides a nice overview of the project. Or check out the AMS project description (pdf).
Frens Jan Rumph