Polycom DOC2702A User Manual

Page of 1010
Chapter 2-Conference Profiles
Polycom, Inc.
2-13
For instance, an SVC endpoint might want to receive three video streams at different frame 
rates and resolutions, and create a conference layout with the received video streams. Each 
SVC-enabled endpoint sends encoded SVC bit streams to the MCU to relay to the other 
SVC-enabled endpoints in the conference.
The endpoints encode the video in multiple resolutions and decodes the multiple video 
input streams.
For example:
RealPresence mobile client (2) will transmit two resolutions; one that is suited for 
RealPresence Desktop client (3) and a second that is suited for two other endpoints: 
RealPresence Desktop client (4) and (1). 
RealPresence Desktop client (1) transmits two resolutions; one that is suited for 
RealPresence Mobile client (2) and a second that is suited for RealPresence Desktop 
client (4). 
The MCU determines which of the incoming resolutions to send to each endpoint. It does 
not perform any SVC encoding and decoding, or any transcoding of the video streams. The 
RealPresence Collaboration Server functions as the multipoint media relay to the endpoints. 
For voice activated selection of the video streams, the RealPresence Collaboration Server 
determines which of the incoming bit streams to send to each endpoint.
Advantages of SVC Conferencing
SVC increases the scalability of video networks and enables mass desktop video 
deployments. Some of the advantages of SVC conferencing are:
Offers high-resolution video conferencing with low end-to-end latency, improved error 
resiliency and higher system capacities.
Allows the SVC-enabled video endpoints to manage display layouts, supporting 
multiple line rates, resolutions and frame rates.
The RealPresence Collaboration Server functions as a media relay server providing low 
cost production benefits. The RealPresence Collaboration Server reduces bandwidth 
usage by only selecting the necessary video stream to be sent to the endpoints.
Guidelines
SVC conferences are supported only with the following:
RMX systems with MPMx card
CP Licensing
SIP over UDP signaling
SIP over TLS Signaling
Polycom SVC-enabled endpoints (Polycom® RealPresence® Desktop, Polycom® 
RealPresence® Mobile)
Ad Hoc conferencing via Meeting Rooms and ongoing conferences
SVC Only conferences can run on the same MCU as AVC Only conferences. 
All the endpoints participating in a single SVC Only conference must be connected to 
the same media card and cannot be handled by different media cards as the SVC media 
streams cannot be shared between them.
End-to-end latency on a local network (same site), is around 200mSec to ensure AV 
sync (also known as Lip-sync).
Dial-out is not available in SVC Only conference.