The First IMS AG Face2Face Event is Here
September 25, 2007
It’s about time this happened. We’ve been working for several months now in the IMTC IMS AG for this moment – the first face-to-face interoperability event of our group.
Why is this important?
Up until today, no real IMS testing was done for the client side in any methodical way. Sure, the IMS Forum is doing PlugFest events and the GSMA is also doing some basic interoperability testing for their specification. Nevertheless, there’s no real place where handset vendors and middleware/software providers for handsets can gather around on a regular basis and deal with interoperability. The IMS AG is just that place.
What do we focus on?
We currently deal with Video Share as an IMS service that we are testing, focusing on the client itself. Not what is required on the network side and how billing is done but rather how two mobile clients can call each other, negotiate the parameters they will use for the call and share a video session between each other. We will be moving on to additional client-side service aspects as they develop – we started with Video Share simply because it seems like one of the services of IMS that will be deployed first – I believe AT&T is the first of many operators that will focus on Video Share in the next couple of months.
What do we do?
We talk once a week or two, depending on availability. Companies in the group join a conference call to discuss matters at hand. In these calls we discuss a wide range of topics:
- Drafting out our test case document
- Establishing and discussing liaison connections with other organizations (GSMA, IMS Forum, OMTP and others)
- Scheduling interoperability events
Our goal?
To make sure that once operators decide to deploy services such as Video Share, they will be able to choose any phone vendor they want and be confident of the level of interoperability provided. This means that operators would rather take handsets from vendors who are actually test interoperability in the IMTC IMS AG.
October interoperability event
Our first event is scheduled for October 10-12 this year. RADVISION, my company, is hosting this event along with the 3G-324M AG, which will do their own interoperability testing there.
We are planning to convene after the event and publish the first official test cases document for Video Share from the IMTC. As usual, I am sure we will have some comments to the 3GPP and the GSMA that might require some clarifications or changes to the specifications – that happens when an activity group in the IMTC starts doing interoperability and places a specification under its magnifying glass…
If you do develop communication products, you must know that interoperability is important. What do you do to close this gap of interoperability in your products?
Technorati Tags: IMTC, IMS, IMS Client, Video Share, GSMA, IMS Forum, OMTP, 3GPP, Interoperability, 3G-324M, Tsahi Levent-Levi
.
By Kfir Pravda
Next week, at VON Europe, I will moderate an exciting panel about the influence of IMS on the business of enterprise communication vendors. The panel will take place at the exhibition theater, 12th of June, at 1145. The panel will cover, among other issues:
1. The evolving needs of enterprise customers
2. The way IMS opens the enterprise communication market for operators
3. Business strategies and positioning of different market players
Our panelists include:
Stefan Karapetkov, Sr. Techinal Advisor, Polycom
Edmond Osstyn, Business Development Director, IMS Applications, Alcatel-Lucent
Adi Paz, Sr. Director, Products and Marketing, Radvision
Technorati Tags: IMS, VONEUROPE07, Polycom, Alcatel-Lucent, Radvision, Kfir Pravda, Strategy, Enterprise communication, carriers, operators
.
In my first post on this blog, I started to explain the real difference between real IMS and “IMS-ready” or “IMS-lite”. In the context of SIP, which is what IMS is all about on the client side, this comes down to an exhaustive, daunting list of features. I know, I know… it is not all SIP. You also need IPSec, XCAP and other such curses. Don’t worry, I won’t forget them.
So to be sure I have enough to write about here, and because I feel that we really do need to understand the difference, I’ll be going over this feature list according to subject: compression, security, quality of service, billing, etc.
Because this is going to take some time, I will try to cover one concept in each post – so stay tuned!
I’d like to wish all our Christian readers, a Happy Easter and all our Jewish readers a Happy Passover. And to the rest of you… try not to work too hard while everyone else is celebrating!
What is your client strategy?
March 26, 2007
Whenever I visit customers in Asia Pacific, it always amazes me how different companies that are developing the same product can go about it in so many different ways. OK, maybe not exactly the same product. One handset weighs in at 170 grams and their competitor’s handset at 164 grams. One handset could also have a metallic color, and the other shiny gray. Go figure.
In trying to understand this phenomenon, I came to the conclusion that all these different approaches are a result of a fundamental difference in R&D philosophy.
Let’s assume you are a developer, and you have been given the daunting task of developing a mobile handset. And YES; it should be an IMS handset. The applications you need to support promise you a major headache:
- VoIP calls (audio and video)
- Presence
- IM (Instant Messaging)
- VS (Video Sharing)
- VCC (Voice Call Continuity)
By the time you’re finished, you assume the whole world speaks in “acronym”…
And now for the 50 million dollar question: How would you approach this development task?
Rest assured I won’t let you think too much while reading this post. Take it from me… I’ve seen primarily two kinds of companies – the “top down” kind and the “bottom up” kind.
Essentially, if you need to build an IMS client (that’s a mobile phone that does IP), first and foremost you need a solid SIP IMS implementation. Not your average-Joe “IMS-ready” or “IMS-lite” one. You also need engines for all those fun applications that will enable you to do VoIP calls, presence, etc. And to top it off, you need a user interface that can be stitched into Windows Mobile, Symbian or whatever operating system you’re using.
Illustrating it in a diagram, you get the following result. 
If you are one of those “bottom up” companies, then you believe that infrastructure is the key. You search for the right SIP stack, with all those nasty IMS extensions. You make sure your RTP implementation can handle all those necessary bandwidth and retransmissions for IMS. And you select a good codec vendor that can deliver on the promise of encoding H.264 in CIF resolution using only 80 MIPS (I wish…). Once you have that part figured out, the next step is to look for the engines you need to build your applications!
If you are one of those “top down” companies, you believe that the world is a set of applications you can mix and match… and all is well in the land of computing. You see SIP, RTP and those codecs as commodities. And for you, IMS is just another one of those things that you’ll figure out in the future. So out you go to seek your fortune in the market. You find a slick brochure of engines and applications, and choose what looks nicest. Presto! You have a really cool demo application running that really works. Until you look under the hood or try to plug it into a real network with other users.
In case you haven’t figured it out, I tend to side with the “bottom up” guys. I’ve seen too many projects leave the gate and start out running too fast… just to find out (pretty soon) that they were heading in the wrong direction. And now they are left with a lot of catching up to do.
What kind of company do you work for?
