Implementation of Scalable Media Streaming ServerClient

1
Implementation of Scalable Media Streaming
Server/Client

• B.Tech project
• Under the supervision of
• Prof Anirban Mahanti

2
Introduction

• Multimedia networking application explosive
  growth
• Examples streaming video, IP telephony,
  teleconferencing, interactive games and much
  more.
• Service requirements
• Highly sensitive to end-to-end delay
• Jitter sensitive
• Loss - tolerant

3
Introduction (cont..)

• Audio/Video streaming popular application and
  significant consumer of network bandwidth.
• Key Factors
• Rapid decrease in the cost of Disk storage.
• Improvement in Internet infrastructure cable
  modem, caching and CDNs, new QoS-oriented
  protocols
• Enormous pent-up demand for high-quality video on
  demand

4
Audio/Veideo streaming

• Key Features
• Stored Media prerecorded, stored at server
• user may pause, rewind
  or
• fast-forward
• Streaming begins playout while receiving
• no entire file download
• Continuous playout progress according to
  original
• timing of
  recording

5
Hurdles for Multimedia in Todays Network

• Internet best-effort service IP protocol
• Limitations
• Packet Loss
• End-to-end delay
• Packet jitter
• Handled at application level
• Delay playback
• Timestamp
• Sequence numbers

6
Solution?

• Multicast sending a packet from one sender to
  multiple receivers with a single send operation.
• Ways
• One-to-all unicast
• Application-level multicast
• Explicit multicast

7
Few Multicast Techniques for Video-On-Demand

• Patching.
• Bandwidth Skimming.
• Optimized Periodic Broadcast

8
Patching

• Set of channels
• Regular Multicast/ Patching Unicast
• Reduced response latency
• Buffer space required at client
• Optimal for Moderate request arrival rate
• No improvement for very low request arrival rate.

9
Patching
Regular Stream
Patching Stream
Position in Media Stream
T0
T1
T2
Time
10
Darwin Streaming Server

• Darwin Streaming server Transmits Audio or Video
  Streams on Client requests.
• Delivers live as well as On-Demand Media.
• Supports both unicast and multicast
• Supports following protocols
• RTSP over TCP
• RTP over UDP
• RTP over Apples Reliable UDP
• RTSP/RTP in HTTP

11
Server Architecture

• Consists of core server which acts as an
  interface between network clients and server
  modules.
• Largely Asynchronous.
• Use modules to respond to the client requests and
  complete different tasks.
• Three types of modules
• Content Managing Modules.
• Server Support Modules.
• Access Control Modules.

12
Server Architecture
13
Requirements for modules

• A main routine, which the server calls when it
  starts up to initialize the QTSS stub library
  with your module
• A dispatch routine, which the server uses when it
  calls the module for a specific purpose

14
Module Roles

• Provide modules with a well-defined state for
  performing certain types of processing.
• Server may pass to the module one or more QTSS
  object depending on the role.

15
Goals of the Project

• To implement a On-Demand Media Streaming Server
  using latest techniques on the Darwin Programming
  Interface employing the features
• Reduced latency
• Scalability
• To do the performance analysis of server/client

16
Work Done so far

• Studied Multicasting Routing
• Multicast address, multicast group, socket
  programming
• IGMP
• Multicasting routing protocols DVMRP, PIM
• Studied streaming protocols
• RTSP
• RTP
• RTCP

17
Work Done so far (Contd.)

• Studied some latest techniques for streaming
  media namely Patching, Bandwidth Skimming and
  Optimized Periodic Broadcast.
• Implemented some sample multicast servers/clients
  which send the fragments of the file in a cyclic
  order.

18
Work done so far (contd)

• Studied the architecture of the DSS and figured
  out how we can use its Programming Interface to
  implement Patching.
• Patching Module Requirements
• Platform Linux
• Streaming Technique Patching
• Programming Interface Darwin Streaming Server
• Language C
• Specification
• A dynamic module
• Content-Managing-Module .

19
Work done so far (contd)

• Written the code Routines
• Main called by server at startup to initialize
  the library with the module
• Dispatch used by server for specific purpose
  when it calls the module
• Written code for Roles
• Register role - roles supported by the module
  are registered to the server
• Initialize role performs tasks that initialize
  the module

20
Future Goals

• Implementation of the remaining roles of the
  Patching Module.
• Performance analysis of the Darwin Streaming
  Server.
• Performance analysis of Server with Patching
  enabled.

21
References

• Anirban Mahanti, Derek Eager, Mary Vernon, and
  David Sundaram-Stukel, "Scalable On-demand Media
  Streaming with Packet Loss Recovery", IEEE/ACM
  Transactions on Networking, Vol. 11, No. 2, April
  2003, pp. 195-209.
• K. A. Hua, Y. Cai, and S. Sheu, Patching A
  Multicast Technique for True Video-On-Demand
  Services, Proc. ACM Multimedia 98, Bristol,
  U.K., Sept. 1998.
• D. L. Eager, M. K. Vernon, and J. Zahorjan,
  Bandwidth Skimming A Technique
  forCost-Effective Video-on-Demand, Proc. MMCN
  00, San Jose, CA, Jan. 2000.
• Computer Networking, A Top-Down Approach
  Featuring the Internet, James F. Kurose Keith W.
  Ross
• Quick Time Streaming Server Administrators
  Guide
• QuickTime Streaming Server Modules Programming
  Guide
• http//developer.apple.com/opensource/server/strea
  ming/index.html
• http//wiki.gandi.net/en/hosting/usinglinux/tutori
  als/fedora/darwinstreaming
• http//lists.apple.com/mailman/listinfo/streaming-
  server-dev.

22

• Thanking You!