Presentation is loading. Please wait.

Presentation is loading. Please wait.

Internet multimedia: simplest approach audio, video not streamed: r no, “pipelining,” long delays until playout! r audio or video stored in file r files.

Similar presentations


Presentation on theme: "Internet multimedia: simplest approach audio, video not streamed: r no, “pipelining,” long delays until playout! r audio or video stored in file r files."— Presentation transcript:

1 Internet multimedia: simplest approach audio, video not streamed: r no, “pipelining,” long delays until playout! r audio or video stored in file r files transferred as HTTP object m received in entirety at client m then passed to player

2 Internet multimedia: streaming approach r browser GETs metafile r browser launches player, passing metafile r player contacts server r server streams audio/video to player

3 Streaming from a streaming server r This architecture allows for non-HTTP protocol between server and media player r Can also use UDP instead of TCP.

4 constant bit rate video transmission Cumulative data time variable network delay client video reception constant bit rate video playout at client client playout delay buffered video Streaming Multimedia: Client Buffering r Client-side buffering, playout delay compensate for network-added delay, delay jitter

5 Streaming Multimedia: Client Buffering r Client-side buffering, playout delay compensate for network-added delay, delay jitter buffered video variable fill rate, x(t) constant drain rate, d

6 Streaming Multimedia: UDP or TCP? UDP r server sends at rate appropriate for client (oblivious to network congestion !) m often send rate = encoding rate = constant rate m then, fill rate = constant rate - packet loss r short playout delay (2-5 seconds) to compensate for network delay jitter r error recover: time permitting TCP r send at maximum possible rate under TCP r fill rate fluctuates due to TCP congestion control r larger playout delay: smooth TCP delivery rate r HTTP/TCP passes more easily through firewalls

7 Streaming Multimedia: client rate(s) Q: how to handle different client receive rate capabilities? m 28.8 Kbps dialup m 100Mbps Ethernet A: server stores, transmits multiple copies of video, encoded at different rates 1.5 Mbps encoding 28.8 Kbps encoding

8 User Control of Streaming Media: RTSP HTTP r Does not target multimedia content r No commands for fast forward, etc. RTSP: r Client-server application layer protocol. r For user to control display: rewind, fast forward, pause, resume, repositioning, etc… What it doesn’t do: r does not define how audio/video is encapsulated for streaming over network r does not restrict how streamed media is transported; it can be transported over UDP or TCP r does not specify how the media player buffers audio/video

9

10 RTSP: out of band control FTP uses an “out-of-band” control channel: r A file is transferred over one TCP connection. r Control information (directory changes, file deletion, file renaming, etc.) is sent over a separate TCP connection. r The “out-of-band” and “in- band” channels use different port numbers. RTSP messages are also sent out-of-band: r RTSP control messages use different port numbers than the media stream: out-of-band. m Port 554 r The media stream is considered “in-band”.

11 RTSP Example Scenario: r metafile communicated to web browser r browser launches player r player sets up an RTSP control connection, data connection to streaming server

12 RTSP Operation

13 Real-time interactive applications r PC-2-PC phone m instant messaging services are providing this r PC-2-phone m Dialpad m Net2phone r videoconference with Webcams Going to now look at a PC-2-PC Internet phone example in detail

14 Interactive Multimedia: Internet Phone Introduce Internet Phone by way of an example r speaker’s audio: alternating talk spurts, silent periods. m 64 kbps during talk spurt r pkts generated only during talk spurts m 20 msec chunks at 8 Kbytes/sec: 160 bytes data r application-layer header added to each chunk. r Chunk+header encapsulated into UDP segment. r application sends UDP segment into socket every 20 msec during talkspurt.

15 Internet Phone: Packet Loss and Delay r network loss: IP datagram lost due to network congestion (router buffer overflow) r delay loss: IP datagram arrives too late for playout at receiver m delays: processing, queueing in network; end-system (sender, receiver) delays m typical maximum tolerable delay: 400 ms r loss tolerance: depending on voice encoding, losses concealed, packet loss rates between 1% and 10% can be tolerated.

16 constant bit rate transmission Cumulative data time variable network delay (jitter) client reception constant bit rate playout at client client playout delay buffered data Delay Jitter r Consider the end-to-end delays of two consecutive packets: difference can be more or less than 20 msec


Download ppt "Internet multimedia: simplest approach audio, video not streamed: r no, “pipelining,” long delays until playout! r audio or video stored in file r files."

Similar presentations


Ads by Google