Desktop Videoconferencing Ready For Wide Use

New technology puts desktop videoconferencing in reach for most enterprises.

Phil Hippensteel

January 18, 2012

6 Min Read
Network Computing logo

Get our report
"Desktop Videoconferencing: Ready for Its Close-Up",
free with registration

>> See all our Reports <<

Desktop videoconferencing has the potential to play a more significant role in collaboration and unified communications thanks to the growing popularity of the H.264 SVC (Scalable Video Coding) codec and compression technology, which makes high-definition videoconferencing over the Internet feasible for business use.

For the 34% of the 463 business technology professionals responding to our May 2011 InformationWeek Desktop Videoconferencing Survey who have desktop videoconferencing in place, and for the additional 10% who told us they planned to deploy within 12 months, the appeal of desktop videoconferencing is simple: improving employee and customer collaboration while reducing travel costs. We also see desktop videoconferencing used extensively for training and corporate communications. Still, desktop videoconferencing deployment lags significantly behind conference room-based videoconferencing--78% of our respondents have conference room systems in place now, despite the fact that they're more expensive and complex. Rooms need to be scheduled, call setup often requires a knowledgeable administrator, cameras are expensive, and multiparty calls require scheduling a bridge.

Where IT is focused on desktop videoconferencing, it's concentrating on PCs--96% of respondents run or will run desktop videoconferencing on Windows. In a distant second place, 39% of respondents run or will run desktop videoconferencing on iPads.

That makes sense because Microsoft has doubled down on desktop video. Its Lync Server 2010 offers the ability to set up desktop videoconferencing, and the company recently closed its $8.6 billion acquisition of Skype, the popular Internet-based videoconferencing service. Beyond Microsoft, nearly every vendor selling a collaboration product or engaged in enterprise telecom, from Avaya to Vidyo, is focused on desktop videoconferencing. With these systems and H.264 SVC, high-quality conferences are possible with nothing but a typical broadband connection, a notebook PC, and a relatively inexpensive webcam.

Think a conference over the Internet automatically equals jitter? Not so; these newer systems may not use less bandwidth, but they do use bandwidth much more effectively, a critical factor. And it's all about the codec.

Why is your company evaluating desktop videoconferencing?

Phil Hippensteel teaches infomration systems at Penn State University. Write to us at [email protected].H.264 Evolves For The Internet

In a point-to-point videoconference, the key components are the display device, camera, microphone--and the codec. The codec handles the analog-to-digital conversion, compression, and packetization of digital audio and video streams. It also sends and receives the packets. In the past, videoconferencing systems used codecs from the H.320 line of standards, such as H.262. They worked well on dedicated circuits such as T1s; however, quality was definitely an issue over the public Internet. Packets carrying video are extremely time-sensitive because a single frame of video may be represented by hundreds of packets, which can arrive erratically if there's any congestion and queuing in the network routers. This variable arrival time, called jitter, requires a receive buffer to smooth out the video. With H.264 AVC, also known as MPEG-4 Part 10, the industry believed it had the answer to delivering video via IP to varied endpoints. With profiles that allowed bandwidths from 56 Kbps on up to 27 Mbps, vendors thought they could handle everything from mobile clients to broadcast studio cameras.

But one big problem remained: packet loss.

With H.264 AVC compression, even loss rates of just 1% to 2% had a devastating effect on video quality. That's because it often takes a hundred or more packets to represent a single video frame. In MPEG compression, only about every 12th frame, called a key or index frame, actually contains enough information to decode an entire picture. The remaining 11 frames are derived from information in the key frame. If some of the packets for the key frame are lost, the reconstruction of the key frame is affected, as is that of the next 11 frames.

Vendors scrambled to find a way to conceal errors. The resulting solutions generally involved a form of forward-error correction (FEC). In these techniques, a few extra bits were added to the payload to allow the receiver to accumulate an error-correction code. In video FEC, the sending station splits the code and transmits it by placing 1 or 2 bits in each byte or block of data. The problem then became, extra bits means extra bandwidth. And getting enough packets accumulated means additional delay. So while FEC techniques generally work, they come at a cost.

About a decade ago, a small group of vendors decided to take a different approach. By adding an extension to the H.264 standard, they proposed SVC. In this technique, the original video stream is divided into three substreams. The base stream provides enough information to enable the receiving system to present an acceptable low-resolution image. It is protected by aggressive error protection, and in most cases, this stream will be delivered even if the network is suffering 3% or more packet loss.

A second stream contains the information to raise the presentation to the level of standard definition and has minimal loss protection. The third stream is the data necessary to present an HD video experience; it has little or no error protection. This three-pronged system works because most of our networks have loss only for very short periods of time, say 10 to 20 milliseconds. When a limited amount of loss occurs, the receiver is presented with a lower-resolution image. These periods tend to be so brief that the typical user doesn't even perceive them.

SVC is important enough that vendors including Avaya, HP, LifeSize, Polycom, Radvision, and Vidyo have delivered, or have announced their intention to deliver, products based on the standard. Companies that have a large embedded base of H.264 AVC systems will need to use gateways to integrate the newer SVC systems. This gateway is most often a hardware device, although some vendors implement it in software by adding it to the server that acts as the call setup device.

We anticipate gradually escalating adoption of desktop videoconferencing based on H.264 SVC as the market becomes aware of its capabilities and compelling price points. As with VoIP and telephony in 2000, few thought the Internet could be used to connect video devices for high-quality conferencing. Now that it is feasible, adoption should spread quickly.

How important is it for your corporate system to support these platforms?

InformationWeek: Jan. 30, 2012 Issue

InformationWeek: Jan. 30, 2012 Issue

Download a free PDF of InformationWeek magazine
(registration required)

Stay informed! Sign up to get expert advice and insight delivered direct to your inbox
More Insights