VRVS Research Roadmap (Caltech)

1. VRVS Research Roadmap(Caltech)

2. VRVS Deployment and Usage

3. VRVS Reflectors Deployment 78 Reflectors deployed worlwide

4. VRVS Reflectors Deployment 78 reflectors Deployment World wide in 27 Different Countries

5. VRVS registered users and current usage 9461 different Users Registered from104 Countries Taiwan, Greece, Argentina, Russia, Slovakia, etc…

6. Machines and OS • VRVS support different • Operating Systems • according to the need • and the demand of the • final users: • 1st : Windows • 2nd: Linux • 3rd: Macintosh • 4th: Other UNIX

7. Call Details Record (CDR)

8. VRVS R&D

9. VRVS v3.0 (Feb 03), v3.1 (May 03) • Principal characteristics • Centralized database to manage users/meetings • Tunneling between reflectors using one port independently of number of parallel conferences or users connected • Shared desktop and chat connection via the web server • VRVS Reflectors are manually configured and started by an operator • The VRVS network infrastructure configuration is static R R R R Reflectors R R R R R Video + Audio R R R • Principal limitations • Any network break between reflectors needs manual rerouting configuration • Centralized Web server and database is a potential point of failure • Chat and shared desktop network traffic via Web server • No control/monitoring between reflectors and between reflectors and end users. Web Shared Desktop + chat Database

10. VRVS Main Technical Trend Evolution Reflectors • V3.(0,1): • VRVS core infrastructure is statically and manually configured and operated Extend intelligence to the edge V3.(2,x): VRVS core infrastructure is automatically configured and monitored. The core software is self dependant and can take self decision to improve performance/quality without manual intervention • V4.0 and beyond: • This is a Globally Distributed Self Managed End2End Real-time Infrastructure. It provides the best quality/performance possible • Extend the core intelligence to the edge. • Have a full End2End control and monitoring • The self managed infrastructure has a full knowledge of all the critical/sensitive parameters (all network layers, hardware and software at the end nodes, resources allocated and available,..) in order to take adequate decisions(alarms, automatic rerouting of traffic, disconnection, remove/add services,..) • Administrator is fully aware of the operational status via constant feedback (via UI, email, phone,..) from the self managed core software 3.0 3.x 4.0 End users/applications

11. VRVS Reflector functionalities • Dynamic registration to high level directory services • Automatic re-activation of components and services • Automatic and secure code update • Continuous monitoring of network quality (packet loss, jitter, latency) between its peers and its possible peers • Automatic rerouting to obtain the best performance/quality • Automatic Alarm notifications when monitored parameters (system or network) go beyond a preset threshold • Dynamically provides services (video, audio, data,..) that matches the current resources/capabilities to the end users/applications • Provides access to real-time and historical data

12. VRVS Reflector Architecture VRVS Discovery/Registration/Configuration Scheduling service Logging service Admin service SIP/SIMPLE H.323 Others protocols Quality Assurance Services Monitoring Services Video Video Video Audio Audio Audio Data Data Data VRVS Proxy VRVS Router Encryption

13. VRVS v3.2 (Dec 03), v3.x: VRVS Services evolutionGlobally Distributed Self Managed Real-time Infrastructure Lookup Service Register R R R R R R R R Reflector + Monalisa agent Video + Audio R R R R Web Shared Desktop + chat Database

14. Web Web VRVS v4.0 (Oct 04) VRVS Services evolution:Globally Distributed Self Managed End2End Real-time Infrastructure Lookup Services Register R R Reflector + Monalisa agent R R R R R R R R R R End client Video + Audio Shared Desktop + chat Distributed Web servers and Database Logging, Access to Virtual Rooms

15. End users/applications functionalities (1/2) • Dynamic registration to high level directory services • Automatic detection of the system parameters (CPU, Memory,..), hardware components (Audio card, video card, …), services capabilities (video, audio, …), network environment and capabilities (wireless environment, DSL, available bandwidth, …) • Automatic re-activation of components and services • Automatic code update • Continuous monitoring of network quality (packet loss, jitter, latency) to the attached reflector and possible others reflectors • Automatic rerouting to obtain the best performance/quality(The communication between an end node could be rerouted transparently and automatically to an other reflector for performance optimization)

16. End users/applications functionalities (2/2) • Automatic Alarm notifications when monitored parameters (system or network) go beyond a preset threshold. • As example: if Desktop CPU is too high, the system will automatically try to perform the following: • reduce services (video/audio/data/..) running in the machine and inform user of the change • or if no improvement, inform the user of the problem and from where it comes from (if possible) and then propose a solution (ultimately reset the system) • Keep inform the general system administrator • Dynamically gets services (video, audio, data,..) that matches the current resources/capabilities to end users/applications • Provides access to real-time and historical data

17. Why VRVS Unique and advanced Architecture ?

18. Example: Current H.323 architecture (Hub & Spoke) Los Angeles Tokyo MCU MCU ports MCU Gatekeeper New York Conf A Conf B

19. VRVS new and unique architecture (Peer-to-Peer) Los Angeles Tokyo VRVS VRVS VRVS New York VRVS WEB Conf C Conf B Conf A

20. Scalability, Reliability Usability VRVS WEB

21. Schools / Companies Real-time scalable content distribution (VRVS) IP Network layer (VNP, Wireless, QoS,..)

22. VRVS was initially built to provide a relatively low cost system for videoconferencing and remote collaboration over networks for the HENP community Users Requirements • System Easy to Use • Booking, Scheduling, Coordination, Access Control,.. • Full Documentation (Hardware, Software, Procedures, Advice…). No need for an administrator ! • System Easy to Replicate • Accessibility everywhere with IP connectivity (Office, Home, Hotel, Wireless,.) • Minimum requirement: Need an IP connection (with sufficient bandwidth) and a Web Browser.

23. System Features requirements • Unified Video, Audio, Shared Virtual Spaces and Data Applications • Point to Point and Multi-point communication • Multiple Architecture Support: UNIX’s, Linux, Windows95/NT/2K/XP…Macintosh… • Network optimization (Latency, routing, reliability) • Extensible worldwide (several thousand users). • Should work for a variety of multipoint working environments • From the desktop to conference rooms to amphitheatres • Should be highly scalable and reliable

24. Today Current systems and standards are not well adapted for large and disperse collaborations • H.323: • Heritage from ISDN (H.320 standard) • System very complicated to operated (need MCU, Gatekeeper, Gateway…) • Not scalable at all. People are happy when they run a 50 MCU ports What about the millions of desktops ? • Still focus on conference rooms. People currently are migrating their ISDN conference rooms to IP • SIP (Session Initiation Protocol): • The most promising standard. • Driving by the VoIP and Microsoft/Messenger • Still need some real end applications (in particular Video applications)

25. MPEG • MPEG2 encoder/decoder still expensive ( > 10K$) • MPEG4 encoder/decoder very promising but still have licensing issues • No real Multipoint capability • Multicast Based Systems • Still lack of deployment within LAN • Difficult to support and operate widely • Still unreliable for business quality • Not supported by most Commercial ISP • Lack of security