Industry News Summary – VoLTE, Video-Conferencing and more

Ericsson, Qualcomm make progress on VoLTE
Ericsson and Qualcomm claims to have the world first voice call handover between LTE and WCDMA networks. Read more at Total Telecom.

A Day Made of Glass
Telepresence options wrote an article about the highly successful ‘A Day Made of Glass 2′ video. If you haven’t watched the original yet, see it below:

Videoconferencing at CES
AnandTech wrote about the videoconferencing solutions presented at CES, covering Vidyo and Biscotti.

Enhanced by Zemanta
About the writer: IMTC

IMTC MPEG DASH Webinar – February 16th 2012


Adaptive streaming over HTTP has become the default dominant approach for video distribution.
At the moment, proprietary technologies have been deployed such as as Apple HTTP Live Streaming (HLS), Microsoft Smooth Streaming and Adobe Dynamic Streaming, and the industry has been eager to have a unified standard solution. [Read more...]

About the writer: IMTC

VoLTE Webinar Transcribe


Also Availiable as PDF. [Read more...]

About the writer: IMTC

IMTC BOD Interview – Frédéric Gabin, Ericsson

IMTC Blog is proud to Interview Frédéric Gabin, Standardization Manager at Ericsson, France and IMTC Board of Directors member:

IMTC Blog: Hello Frédéric, Please Tell us about yourself, your positions in Ericsson and past positions.

Mr.Gabin: My name is Frédéric Gabin, I’m French and I live in Paris, France. My role in the Ericsson standardization organization since 2008 is to lead and coordinate the development of Multimedia standards. I started my career as a signal processing research engineer in 1998 and since then was involved in research, system design and standards with both network and mobile terminal vendors.

IMTC Blog: Why did you volunteered to be an IMTC board member?

Mr.Gabin: The IMTC organization has a strong history of making upcoming key multimedia features a reality without which originating standards would look like mere litterature. The board member position gives a direct ability of steering the organization towards the real needs of my company and the industry. I wanted to be part of this.

IMTC Blog: What are your goals as an IMTC board member ?

Mr.Gabin: My goals are to give existing and future AGs visibility and support in their developments by establishing clear directions in agreement with the key industry players.

IMTC Blog: How does IMTC benefit Ericsson?

Mr.Gabin: IMTC benefits Ericsson as well as ST-Ericsson and Sony-Ericsson in that it gives a framework for terminal interop tests of key multimedia services which speeds up deployments and adoption on the market.

IMTC Blog: In your opinion – What are IMTC greatest achievements? what were 2010 greatest achievements?

Mr.Gabin: IMTC greatest achievements in 2010 were that VoLTE F2F test events started February 2-4 (Ericsson AB), Stockholm and October 20-22 (Nokia Siemens Networks), Athens.

IMTC Blog: What are the major goals for IMTC at 2011? What are the major interoperability issues for 2011 (in Ericsson, in the industry as a whole)?

Mr.Gabin: Firstly, with more and more fragmentation in the various multimedia standards and fast pace deployments, for example in streaming services, one major goal for IMTC is to avoid fragmentation itself and focus on the most relevant standards and services. Secondly, the ongoing deployments of LTE networks around the world should drive a focus on VoLTE terminal interoperability undertaken in the IMS AG . This group should grow by involving more operators and device vendors.

We thank Frédéric for his time and dedication.
As always, If your company does IMS, VoLTE – Join IMTC to help shape the future of Telecommunication Interoperability.

Frédéric Gabin can be reached via E-mail: frederic.gabin@ericsson.com or LinkedIN – http://fr.linkedin.com/in/fredericgabin

Frédéric Gabin, Ericsson

Frédéric Gabin, Ericsson

About the writer: Itzhak Wolkowicz

Is there a place for Rich Communication Suite in the mobile future?

We have asked Jose M.Recio from Solaiemes to talk about RCS and to shed some more light about his IMTC 2025 presentation (Jose participated in the Triple Play Session and presented RCS examples).
Solaiemes creates communication solutions built upon the RCS features of the IMS standards.
RCS (Rich Communcation Suite) is an industy effort driven by a group of operators, infrastructure and device vendors – Orange, Telecom Italia, Telefonica, TeliaSonera, Ericsson, Nokia Siemens networks, Nokia, Sony Ericsson and Samsung, etc.
The main RCS features are -
Enchaned Phonebook, Messenging and Calls – Sharing of multimedia content, chat and presence that works across devices and operators.
I’ve asked Jose to talk a bit about RCS and his view on the mobile market:

Hi Jose, can you share your thoughts about RCS and how your what your company does in that field?

Jose:  RCS, short for RichCommunicationSuite, it is a coordinated effort, driven by GSMA (the mobile industry association) and backed by the major players to develop a common set of “beyond-SMS-and-voice” basic enablers that are available out of the box in mobile, and work seamlessly across carriers and are also accessible from a PC/broadband client.
Think messaging, video-sharing, etc. available even in cheap handsets, preinstalled and working across carriers. One single use case for doing zillions of things.

Isn’t these features available on many smart-phones?

Jose: Yes, that’s true. But that there are billions of users that are using feature, cheap, phones.
Besides, carrier services are a bit more trusted, especially by businesses.
Being able to choose – would you develop a service that billions can use or an app that only the owners of a given handset running a given software version can access?

And what would be a good example of an application available to all? SMS!
If a user just knows how to send a SMS, he knows how to access millions of “applications”: insult politicians in TV, receive credit cards alerts, buy ringtones, and of course send a SMS to his loved one.  RCS is meant just for that – to create the future mobile applications to be used across all devices – If done properly, RCS allows developers to go beyond SMS, with a richer experience. Many business cases will be discovered. Just leave the ecosystem time to develop.

Are there any devices that support RCS today?

Jose:  The “traditional” Telco ecosystem is fully committed on paper to RCS. Devices: NSN, Sony Ericsson, Samsung, LG… there are Android and prototype iPhone clients. There is also an IOT event per quarter to test interoperability.

For the first time All 3 operators in France, Telefonica and Orange in Spain and all operators in Korea – They all work together in coordinated launches.

Are there any RCS applications currently available or in Beta?

Jose:  That’s where solaiemes is focused: Createing APIs so the innovation powerhouse out there in the net can use RCS for things we can’t even think of. That’s exactly what I presented in the IMTC 2025 presentation – How do you put triple play services in a device/screen where you can’t easily deploy a full software client?  My IMTC presentation contains test cases (http://solaiemes.com/index.php?id=94)

Today, some of the features of mobile devices aren’t inter-operable – 3G video calls and iPhone Facetime – Will RCS applications will be interoperable with high end smartphone applications?

Jose: That’s exactly the point, Many Services do not make sense any more from person-to-person. However they make a lot of sense when you introduce a business process or an application: SMS and video calls are very good examples.
The RCS applications that we see as successful would be the ones linked to business apps or cloud-based/community-based use cases.
Check for example the Twitter example in the previous Link – a user may have a native full twitter client (on high end smartphone, or a PC) or a RCS app (feature/simple devices) – Twitter will be the same for both.
SMS success for consumers and carriers (main source of data revenues) is based on ubiquitous presence of the basic enabler (every mobile phone supports SMS) and common use experience and use case. It doesn’t matter if you send or receive a SMS for voting in a TV program, buy a ringtone, get a notification of a credit card transaction, ect. It’s all the same.
On summery – Carries can either look for the SMS way: Common basic experience, based on a Telco enabler (RCS?), for many services. Or for the App way – try to grab one of the “must have” future few applications.
Based on what happened so far, it seems more reasonable to go for the first one – Carrier intermediating third parties offering services over the enabler.
About the writer: Itzhak Wolkowicz