Telepresence Solutions Overview


Published on

Presented at IMTC Telepresence Workshop
June 15, 2010
Jesi, Italy

Presents state of the art in the Telepresence Solutions

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • (a) Point-to-point connections (SIP or H.323) from single stream systems are made to the primary HDX in the room, and use only one screen/camera of the ITP systems (b) When connections are made through an RMX bridge, then the RMX can use all the screens and cameras at each site.  This requires proprietary signaling today. (c) Existing standards already support connections between single stream systems and multiview/ITP systems.
  • Telepresence Solutions Overview

    1. 1. Present Day Telepresence Solutions Patrick Luthi, TANDBERG IMTC Requirements WG Chair
    2. 2. Telepresence systems
    3. 3. Telepresence systems
    4. 4. LifeSize ® Conference 200 ™ Page <ul><ul><li>Four 65+ 1080p30 High Definition TV for video and data sharing </li></ul></ul><ul><ul><li>Three 1080p30 HD cameras providing life-size coverage for 6 individuals </li></ul></ul><ul><ul><li>Touch Panel based Call Control and Directory lookup </li></ul></ul><ul><ul><li>One touch dialing to connect all three codec's simultaneously to the remote Telepresence Room </li></ul></ul><ul><ul><li>Standards based solution providing base level interoperability with similar Telepresence solutions </li></ul></ul><ul><ul><li>Point-to-Point Telepresence plus integration with MCU-based Telepresence solutions </li></ul></ul>Video Only Audio. Video, Data
    5. 5. Video Flow – Between Triple Screen Systems <ul><li>Max 4 Video Streams </li></ul><ul><ul><li>Center, Left and Right Camera = 3 Video streams </li></ul></ul><ul><ul><li>Data Video = 1 Video stream </li></ul></ul><ul><li>All Video Streams share 1 common RTP Connection </li></ul><ul><li>Each Camera stream is sent to the corresponding Display </li></ul><ul><li>Data Video stream is sent to the Projector HDMI Outlet </li></ul><ul><ul><li>Only either Doc Cam or the PC Input would be active at a time </li></ul></ul>Video RTP Session CTS 2 CTS 1 or
    6. 6. Halo Endpoints Halo Collaboration Studio 6-seat purpose-built room Interoperation Via Halo Gateways Halo Collaboration Center 2 or 4-seat drop-in endpoint Halo Meeting Room 6-seat drop-in endpoint Common UI and Access to Central Event Service Halo Webcast Broadcast to Large Audiences from Halo Endpoints
    7. 7. Halo on HVEN Company B Company A Campus 1 Company A Campus 2 Halo Video Exchange Network Tail Circuit Event Services Management Media (Fully Meshed)
    8. 8. Native Interoperability How Polycom Does it HDX 4000 Continuous Presence High Definition HDX or VSX Group Systems TPX 306M TPX 306M RPX 200/400 RMX Other Group Systems Point-to-point dialing H.323/H.320/SIP H.323/H.320/SIP
    9. 9. Current TANDBERG solution basics <ul><li>Three codecs </li></ul><ul><li>Multiple H323 calls </li></ul><ul><li>External control unit which controls all three codecs </li></ul><ul><li>Proprietary solution for signaling left and right codecs </li></ul><ul><li>Uses non-standard userInput messages in H.245 </li></ul>Site A Site B
    10. 10. Pros and Cons for current solution <ul><li>Easy to implement </li></ul><ul><li>Easily extensible </li></ul><ul><li>Few components needed to change </li></ul><ul><li>Good solution for firewall traversal </li></ul><ul><li>General interoperability with non-telepresence systems </li></ul><ul><li>Works very well together with Telepresence-specific MCU </li></ul><ul><li>Proprietary </li></ul><ul><li>Long call setup </li></ul><ul><li>Multiple calls = multiple licenses </li></ul><ul><ul><li>Calls </li></ul></ul><ul><ul><li>Firewall traversal </li></ul></ul><ul><ul><li>Registrations </li></ul></ul><ul><li>Hard to do bandwidth control </li></ul><ul><li>Goes against normal call setup </li></ul><ul><li>Each camera maps to 1 and only 1 output screen. </li></ul>Pros Cons
    11. 11. Some ideas to requirements <ul><li>N audio-streams, M video-streams </li></ul><ul><li>Positional information of those streams </li></ul><ul><li>Generic support for tagging streams </li></ul><ul><li>Maintaining backwards compatibility </li></ul><ul><li>Extremely low call-setup time </li></ul><ul><li>Firewall traversal </li></ul><ul><li>Encryption </li></ul><ul><li>Audio energy level as metadata </li></ul><ul><li>Minimum media type support </li></ul><ul><li>Generic support for capabilities exchange </li></ul><ul><li>Extensibility: </li></ul><ul><ul><li>H.241-like signalling of H.264 capabilities </li></ul></ul><ul><ul><li>H.245 generic types </li></ul></ul><ul><ul><li>Future audio and video codecs </li></ul></ul>N and M are [0,1,2,3,...] N=M=1 <1 second
    12. 12. Thank you