Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Real-time Transport Protocol
#1

Real-time Transport Protocol

[attachment=635]

Outline of Talk

Multimedia applications requirements
RTP architecture
RTP details
Vic: an application using RTP
Summary: RTP does meet the requirements

RTP Architecture ALF and ILP

Application-level framing:
The application best knows its own needs
May not ask for retransmission, but for lower resolution
Integrated Layer Processing
Tightly coupled layers
Keeps data presentation from being the bottleneck
Gives the app. access to the data ASAP!

RTP: Summary

A very thin protocol
Usually built into application
No hard QoS guarantees
Designed for soft real-time apps
Depends on underlying network
Can run over ATM
Two components:
Media(data) transport: RTP
Control: RTCP

Mixers and Translators

Mixer
Could receive and combine various sources in an effort to reduce bandwidth
Translator
Keeps incoming sources separate
To transform to a lower quality format to broadcast on lower-speed networks
To send through firewalls

Summary

Multimedia applications have much different needs than http or ftp!
RTP meets those needs:
Minimized jitter
Synchronized sources
Dynamic, payload-specific frame length
Adaptation in the face of congestion
Interoperability
Effective use of bandwidth
Support for video-conferencing (multicast, IDs)
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)

Powered By MyBB, © 2002-2024 iAndrew & Melroy van den Berg.