Finish 3G bit pipes

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

Posted by Frens Jan Rumph on May 24, 2008
1 Comment
Filed under Telecom
Tagged with Ambient Networks, AMS, IMS, Pricing, QoE, QoS

AMS to the rescue?

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:

• It was formerly referred to as H.325.
• The goal of the AMS project is to create a new multimedia terminal and systems architecture that supports distributed and media rich collaboration environments.
• Presently, the project is in the requirements-gathering phase and is starting to look at possible architectures.
• AMS envisions an environment in which a user has many AMS-enabled devices including portable wireless, home entertainment and computer-based devices and is offered many applications and services that are either peer-to-peer or network-provided.
• AMS is viewed as the successor system to the legacy H.323 and SIP systems.

The objectives of the AMS project are:

• Improve the end user experience
• Enable innovative applications
• Enable mobility
• Enable multimedia
• Make it easy to use
• Improve productivity
• Ease application and service development

Some example applications of the AMS:

• Traditional voice and video
• Whiteboard
• File transfer
• Application sharing
• Text messaging
• Video streaming (e.g., IPTV)
• Gaming
• Multi-user data conferencing
• Streaming audio (e.g., “IP radio”)

The AMS project envisions the following components:

• “container” - This is the device that represents the user to the network (e.g., a desk phone, mobile phone, or softphone application)
• Application Protocol Entities (APEs) - These are the applications that register with the container to provide the user with voice, video, and data collaboration capabilities
• Service Nodes (SNs) - These are the network entities that enable the container to establish communication with a remote entity, facilitate NAT/FW traversal, and provide other network-based services
• Application Servers (AS) - These are elements in the network that provide various services, which might include IPTV,

 My n cents on AMS:

1. The focus of the AMS is more at the edge of the network then one would suspect when reading things such as ’AMS is viewed as the successor system to legacy H.323 and SIP systems.
2. A lot of goals of the AMS project are in line with the goals of the IMS, and IMHO seek to build on the efforts put in the standardisation of the IMS by 3GPP. The project description describes that liasons should be made with IETF, ETSI (TISPAN), 3GPP, 3GPP2 and the IMTC, and that it should draw on the work of OASIS, MPEG, IETF, ISO and IEEE. Lets just hope they do! There’s no point in starting all over again!
3. A lot of goals and the vision of the AMS project are in line with the Ambient Networks project, an EU FP6 research program, perhaps the ITU can learn from that research.
4. The project specifies a lot of Work Items, but NONE on accounting, charging or billing! This would IMHO mean a big gap in the research performed! Unless of course the ITU envisions a world without money or is getting communistic on us
5. I wonder how this relates to DLNA? I’m not an expert on that technology, but I have a hunch that there is a relationship here as well!

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

Posted by Frens Jan Rumph on May 23, 2008
6 Comments
Filed under Standardisation
Tagged with Ambient Networks, AMS, Architecture, H.232, H.325, IMS, ITU, SIP, VoiP