introduction 1 packet loss recovery for
play

Introduction (1) Packet Loss Recovery for Streaming is growing - PDF document

Introduction (1) Packet Loss Recovery for Streaming is growing Commercial streaming successful (ie Streaming Video RealPlayer and MediaPlayer) but proprietary and inflexible N. Feamster and H. Balakrishnan Use MPEG-4 since open


  1. Introduction (1) Packet Loss Recovery for • Streaming is growing • Commercial streaming successful (ie Streaming Video RealPlayer and MediaPlayer) – but proprietary and inflexible N. Feamster and H. Balakrishnan � Use MPEG-4 since open • Current streaming inflexible MIT – Suboptimal – Want to adapt to current network In Workshop on Packet Video (PV) � Present system that adapts to loss Pittsburg, April 2002 Introduction (2) Outline • MPEG video under loss suffers from propagation of errors (what is this) • Introduction (done) � Fundamental tradeoff between bandwidth • Model (next) efficiency and error resilience • Current FEC approaches effective but • System Architecture • Performance Evaluation – Reduces benefits of compression • Related Work – Tough to get adaptation right • Some say cannot use retransmission for • Conclusions streaming but – Selective retransmission (I-frames) ok • Build model + system – (Also TCP-Friendly using CM, but not focus) Model (Outline) Problem Description • MPEG-4 has three frame • Problem Description (next) types: I, B, P – MPEG-4 – Note, MPEG-4 calls them – Error Propagation “Video Object Planes” but • Packet loss model frames is fine – Experiments • While high compression, suffers from error – Analytic Model propagation • Benefits of Selective Repair � Loss of I-frame packets can affect subsequent frames, too 1

  2. Loss in an I-frame Propagation to Next P-frame PSNR 21.996 PSNR 17.538 Average PSNR versus Loss Rate Model (Outline) • Problem Description (done) – MPEG-4 -“Coastguard” clip – Error Propagation -30 fps • Packet loss model (next) – Experiments – Analytic Model • Benefits of Selective Repair Effects of Loss on Frame Rate Packet Loss Model (with Thresholds) • Assume packet loss degrades quality – True, in general, unless FEC • Assume below PSNR threshold, would discard Degradation holds across – But PSNR doesn’t model perceived quality thresholds – This viewability threshold varies with picture + So will analyze several thresholds + Also, can use other quality metrics – Generally, under 20 db is bad + Loss of 2 8 (about .4%) trouble and needs correction + (See previous figure) 2

  3. Analytic Model (1) Analytic Model (2) • Observed frame rate ƒ = ƒ 0 (1- φ ) – φ is fraction of frames dropped • p is packet loss rate – ƒ 0 is original frame rate (ie- 30 fps) • S I is size of I frame (similar for S B , S P , too) • Assume if any packet lost, frame useless • Where i runs over types I, P and B • P( ƒ i ) can be determined by fraction in stream • F is event that a frame is useless (PSNR below threshold) • ƒ i is event that frame is of type i P needs all previous P (and I) frames N P is number of P frames in GOP Analytic Model (3) Model vs. Measured • Simplify to closed form above Matches lower thresholds • Now, using equations and given Can generalize for n losses (instead of 1) for higher – N P S I S B S P ƒ 0 thresholds • Can determine – ƒ = ƒ 0 (1- φ ) • “Model”. Compare to measured Benefits of Selective Model (Outline) Retransmission • Problem Description (done) – MPEG-4 Recover only I frames – Error Propagation Recover only P frames • Packet loss model (Recover B frames (done) doesn’t help much) – Experiments – Analytic Model • Benefits of Selective Repair (next) 3

  4. Overview of System Outline • Introduction (done) • Model (done) • System Architecture • CM provides TCP-Friendly data rate (next) • Performance Evaluation – Calls back when can send data • Related Work • Data sent over RTP (using UDP) • Conclusions • Control over RTSP (over TCP) • Frames put into Application Data Units (ADU) – 1 per ADU Packet Header Loss Detection and Recovery • Mid-frame – Gaps in ADU using offset plus fragment length • Start-of frame -P used for priority (I-frames) – First offset non-zero - Sequence numbers • End-of-frame (for loss) - Total length – ADU less than reported length -Frames can be more • Complete loss than one packet -Offset for location – Detected by gap in ADU sequence numbers in GOP • Can use priorities to decide upon retransmissions – (Me: which ones is the hard part!) Implementation Postprocessing (Receiver-Based) • Used OpenDivX for MPEG-4 • May still have some missing frames • Used CM previously built for Linux • Simple replacement bad if motion • Used RTSP client-server library – Estimate motion and compensate • Also, extended mplayer for Linux – Call-backs give complete ADU to player – Retransmit all unless canceled by app 4

  5. Setup Outline • Server on P4, 1.5 GHz, Linux 2.2.18 • Introduction • Client on P2, 233 MHz, Linux 2.2.9 (done) • Model • 1.5 Mbps, 50 ms latency, 3% loss (done) • System Architecture (done) – using Dummynet, a WAN emulator • Performance Evaluation • 20 Kbps video at 30 fps (next) • Related Work – Used only 300 frames • Conclusions • For “Internet”, used 200 ms RTT and used Web cross traffic with SURG (traffic emulator) • Added buffering to combat jitter – (Me: how and how much is not specified) Benefits of Selective Reliability Benefits of Selective Reliability (1) (2) - 200 ms RTT - Other PSNRs are similar - Acceptable PSNR 25 - Loss 3% Buffering Requirements Benefits Receiver Postprocessing • Buffer for jitter depends upon variance • Buffer for retrans depends upon RTT • Buffer for quality adaptation (congestion responsiveness) depends upon data rate (R) – O(R) for SQRT (TFRC) -Postprocessing can – O(R 2 ) for AIMD (TCP) also be used with • Dominant factor depends upon RTT to RTT SR (not shown) variance and rate • (Me: no more analysis than above) 5

  6. Related Work (1) Outline • Media Transport • Introduction (done) – RTSP for control [49] • Model (done) – RTP is application level protocol with real-time • System Architecture data properties (timing info + sequence) [48] (done) • Performance Evaluation – RTCP protocol provides reports to sender [40] (done) • Related Work – TFRC [52], CM, RAP[44] (next) • Conclusions + all TCP-Friendly protocols for streaming media Related Work (2) Conclusion • Error and Loss Recovery • Streaming video must account for loss • This paper models loss to explain effects – Survey of techniques [54] • Can use retransmission of important packets – Receiver post-processing [22] for significant gain – Avoid propagation but don’t delay [54] • Describe system to do so based on – Effects of MPEG-4’s built in repair for bit errors [23] extensions of common tools – FEC schemes [9,10,33] – Priority-based packets [39,50,1] Future Work? Future Work (Me) • Wider-range of videos – Motion content – GOPs – Resolution • Alternate measures of quality • Evaluation of buffering 6

Recommend


More recommend