Presentation

450 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
450
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Presentation

  1. 1. Department of Computer Science & Engineering The Chinese University of Hong Kong Master of Science in Computer Science Virtual Media Center: A Generic Architecture for Distributed Video-On-Demand Services Date: 30 April 2004 Presented by: Lee KaYan,Sunny Supervisor: Prof. Michael R. Lyu 2010/7/15 1
  2. 2. Outline  Motivation  Related Work  Virtual Media Center (VMC) Services  Characteristics  Technologies Used: Web Service and CORBA  System Architecture  Implementation Details  Future Works and Enhancements 2010/7/15 2
  3. 3. Motivation  VOD is a bandwidth demand, the capacity of concurrent users is limited at present network equipment and technologies. A simple and efficiency server selection mechanism is needed  Multimedia technologies such as compression, security and streaming protocol may change in the future. A framework to provide multimedia streaming service with the capability to adapting technologies change is needed  To implement a application called “Virtual Media Center” under this framework 2010/7/15 3
  4. 4. Related Work  Video-on-Demand (VOD) – VOD is a service that allow users to view any video at any time and can use VCR-like functions – Currently, the most popular and cheap technology for VOD is streaming over Internet  Distributed Systems – Common VOD architectures are distributed systems (DVOD) – Distribution can be distributed system components, distributed streaming servers, distributed media content and distributed transmission source (stripping)  Major solutions on DVOD – Replicate strategy for video content – Metrics based streaming server selection – Set-Top box for buffering, caching and decryption 2010/7/15 4
  5. 5. Virtual Media Center (VMC) Services  Video Streaming for VOD  Real-time TV  Real-time Web Cam  Ad hoc streaming  Auto server selection  CORBA API  Web service API 2010/7/15 5
  6. 6. Characteristics  Distributed server architecture  CORBA and Web service interface between server  Integration of heterogeneous streaming technology and system  By pass firewall  Web user interface 2010/7/15 6
  7. 7. Technologies used: Web Service and CORBA  Why CORBA – Middleware for heterogeneous network, computer hardware, operating system and programming language – Best for interface between heterogeneous streaming server among different technology or content provider – Drawback: difficult to pass firewall in distributed environment 2010/7/15 7
  8. 8. Technologies Used: CORBA and Web Service  Why Web service – Can pass firewall – Best for interface between VMC and different content providers – API for Web application – Best for remote administration, monitoring etc. – Provide catalogue to remote Web server 2010/7/15 8
  9. 9. System Architecture Roles in VMC:  System operator  Content Provider VMC Operator  Subscriber Content Provider Content Provider Subscriber 2010/7/15 9
  10. 10. System Architecture Components in VMC:  Web server – provide catalogue of media content to subscriber Web server  Database server – provide information storage  Streaming server – provide multimedia Database server content storage and streaming to subscriber Streaming server 2010/7/15 10
  11. 11. System Architecture Scenario for VOD:  One central Web server for Internet Web server access  Many streaming server distributed in different geographic location for load Streaming server Subscriber Streaming server balancing  Subscribers are scattered in the Internet Subscriber Subscriber Streaming server 2010/7/15 11
  12. 12. System Architecture Scenario for Real-time broadcast:  Use Audio/Video Web server capture device such Web Cam TV Antenna connected to as Web Cam or TV TV turner card turner card  Web Cam or TV turner Streaming server card can directly connected to Streaming server streaming server Subscriber 2010/7/15 12
  13. 13. System Architecture Scenario for Mobile user: VMC Web Service  Remote Web server Streaming server for Mobile device  Consume catalogue from VMC through Remote Web Server Wireless Web service API Access point  Choice best Smartphone streaming server to delivery content by Notebook Remote Web server 3G Device 2010/7/15 13
  14. 14. System Architecture Scenario for ad hoc multimedia streaming: Web Service API  Ad hoc streaming source registration through Web service VMC Web Server API  Mobile user can real- time broadcast through wireless network Streaming server  Suitable for news Notebook broadcast, remote monitoring etc. Web Cam 2010/7/15 14
  15. 15. System Architecture Scenario for local and CORBA remote servers:  CORBA within firewall  Web service outside VMC Web Server firewall  For distributed streaming servers Router Streaming server  For independent Firewall content providers to contribute their own streaming servers Web Service Router Firewall Streaming server 2010/7/15 15
  16. 16. System Architecture Scenario for real-time server selection:  Round-Trip Time (RTT) VMC CPU Utilization, Allocated  Server CPU utilization Bandwidth and Connected Clients  Server allocated bandwidth Streaming server Streaming server  Server connected Round-Trip Time (RTT) information clients RTT Function Call RTT Function Call Subscriber 2010/7/15 16
  17. 17. System Architecture Scenario for RTT Collection:  Optimal – Between subscriber and Collect RTT streaming server VMC periodically – Need subscriber accept mobile code or install RTT client  Less optimal RTT – Between remote Web server and streaming server – Remote Web server should Streaming server Remote Web Server located near subscriber RTT – Remote Web server responsible RTT collect RTT and update to VMC periodically – No mobile code or install RTT client to subscriber – Best solution for mobile RTT subscriber Mobile Subscriber Streaming server Mobile code or RTT 2010/7/15 17 Client Installed
  18. 18. System Architecture A Generic Implementation Architecture 2010/7/15 18
  19. 19. System Architecture Web Service Web Service Client Logical Components SOAP Resources Metrics Resources Monitor (CPU Loading, Allocated Database Server bandwidth and Connected Client) Naming Service CORBA-ORB CORBA-ORB CORBA Server Status Monitor Auidi/Video TV Turner Media RTT Server RTT Client Capture HW Card Archive RTT Metric HTTP Streaming Server Virtual Media Center Streaming Service Web Server Web Service * SOAP HTTP, RTSP, MMS HTTP, HTTPS Remote Web Server * Media Content Media Catalogue Media Streaming Player Catalogue Viewer Client Application * 2010/7/15 Distributed Location * Multiple Instances 19
  20. 20. Implementation Web Service C#.NET SOAP Resources Monitor Resources Metrics (CPU Loading, Allocated bandwidth and Connected Client): Database Server: Service: omniNames Web Services - C#.NET MS SQL Server CORBA Naming CORBA-ORB: CORBA-ORB: Or omniORB omniORB CORBA-VC++7.0 Server Status Monitor: Auidi/Video C#.NET Media Capture TV Turner Archive: HW: Web Card: TVB Remoting Remoting *.WMV RTT Metric .NET .NET Cam HTTP Virtual Media Center: Windows XP Streaming Server: Windows Server 2003 Professional, IIS 6, ASP.NET Streaming Service: Windows Media Service 9 Web Server Web Service and Windows Media Encoder * SOAP HTTP, RTSP, MMS HTTP, HTTPS ASP.NET Mobile * Media Content Media Catalogue Windows Media Player 9 Series IE 6 or Above Client Application: Microsoft Windows * 2010/7/15 20 Distributed Location * Multiple Instances
  21. 21. Implementation Details Database structure in SQL server 2000: 2010/7/15 21
  22. 22. Implementation Details In VMC server:  Web Server – Windows 2003 Server – Internet Information Server 6 – ASP.NET 1.1  Web Service – Visual Studio .NET 2003 C#  VMC Monitor (e.g. Collect RTT, server status etc.) – Visual Studio .NET 2003 C# – .NET Remoting  Database server – SQL server 2000 MSDE version  CORBA Naming Service – omniORB Naming Service  CORBA server object (for streaming server CPU utilization, allocated bandwidth and connected clients update) – omniORB ORB + VS.NET 2002 VC++ 7.0 2010/7/15 22
  23. 23. Implementation Details In Streaming server:  VOD service – Microsoft Windows Media Server 9 – HTTP, MMS and RTSP – Windows Media File format (*.wmv)  Real-time broadcast for TV and Web Cam – Windows Media Encoder  RTT Server – Visual Studio .NET 2003 C# – .NET remoting – Windows service  CPU utilization, allocated bandwidth and connected clients update – CORBA client: omniORB ORB + VS.NET 2002 VC++ 7.0 – Web service client: VS.NET 2003 C# 2010/7/15 23
  24. 24. Implementation Details Remote Web Server: (for Wireless Mobile Device, Pocket PC version)  Web Server – Windows 2003 Server – Internet Information Server 6 – ASP.NET 1.1  Pocket PC requirement – Microsoft Pocket PC 2003 – Windows Media Player 9  Development and testing – Visual Studio .NET 2003 C# – ASP.NET 1.1 Mobile Control – .NET compact framework 1.1 – Pocket PC 2003 Emulator – Pocket PC 2003 Phone Edition Emulator 2010/7/15 24
  25. 25. Implementation Details Programs in VMC server:  omniNames  VMC_impl  VMCMonitor 2010/7/15 25
  26. 26. Implementation Details Programs in streaming server:  WMSMonitor  VSSMonitor  Windows Service 2010/7/15 26
  27. 27. Implementation Details System Monitoring Tool:  S (s.exe) Syntax: s <serverid> [<serverip>] e.g. s 0 (0 means display the run- time information for all servers) 2010/7/15 27
  28. 28. Implementation Details Subscriber Interface: VMC Home Page 2010/7/15 28
  29. 29. Implementation Details Subscriber Interface: Catalogue Page 2010/7/15 29
  30. 30. Implementation Details Subscriber Interface: Catalogue Page - Filter Functions 2010/7/15 30
  31. 31. Implementation Details Subscriber Interface: Select Server Page 2010/7/15 31
  32. 32. Implementation Details Subscriber Interface: VOD Session Page 2010/7/15 32
  33. 33. Advantage and Disadvantage  Advantage – CORBA and Web Service are well defined standard – Independent to individual streaming technologies – Web Interface for multiple devices: PC, mobile notebook, Pocket, Palm, 3G phone or Smart phone etc. – Real-time server selection – RTT independent to any underlying network path selection algorithm and easy to implement  Disadvantage – Subscriber must installed a build in streaming player in Web browser to decode the target streaming – Remote Web server must located nearest to subscriber to obtain the best RTT estimation for subscriber – Streaming quality and concurrent connections are still limited to underlying bandwidth, compression technology and network equipment 2010/7/15 33
  34. 34. Future Works and Enhancements  Implementation – Interoperability between different ORB – Mobile code for RTT client – Native player install in subscriber device – Test remote Web server for mobile device on real device – Publish Web service on UDDI directory  Testing – Stress test on efficiency of RTT, CPU utilization, allocated bandwidth and connected clients – Improvement of concurrent clients capacity on real-time server selection 2010/7/15 34
  35. 35. End of Presentation Thanks ! 2010/7/15 35

×