Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
RTP Control Protocol
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Scalability in large deployments== In large-scale applications, such as in [[Internet Protocol television]] (IPTV), very long delays (minutes to hours) between RTCP reports may occur, because of the RTCP bandwidth control mechanism required to control congestion (see [[#Protocol functions|Protocol functions]]). Acceptable frequencies are usually less than one per minute. This affords the potential of inappropriate reporting of the relevant statistics by the receiver or causes evaluation by the media sender to be inaccurate relative to the current state of the session. Methods have been introduced to alleviate the problems:<ref>Vít Novotný, Dan Komosný, ''Large-Scale RTCP Feedback Optimization'', Journal of Networks, Vol.3 (3), March 2008</ref> RTCP filtering, RTCP biasing and [[RTCP hierarchical aggregation|hierarchical aggregation]].<ref> [http://www.academypublisher.com/jnw/vol03/no03/jnw03030110.pdf Realtime control protocol and its improvements for Internet Protocol Television]</ref> ===Hierarchical aggregation=== The Hierarchical Aggregation (or also known as RTCP feedback hierarchy) is an optimization of the RTCP feedback model and its aim is to shift the maximum number of users limit further together with [[quality of service]] (QoS) measurement.<ref name=HA1/><ref name=HA2/> The [[RTCP]] [[Bandwidth (computing)|bandwidth]] is constant and takes just 5% of session bandwidth. Therefore, the reporting interval about QoS depends, among others, on a number of session members and for very large sessions it can become very high (minutes or even hours).{{Ref RFC|3550}} However, the acceptable interval is about 10 seconds of reporting. Bigger values would cause time-shifted and very inaccurate reported status about the current session status and any optimization made by the sender could even have a negative effect on network or QoS conditions. The Hierarchical Aggregation is used with [[Source-Specific Multicast]] where only a single source is allowed, i.e. [[IPTV]]. Another type of multicast could be [[Any-Source Multicast]] but it is not so suitable for large-scale applications with huge number of users. {{asof|June 2007}}, only the most modern IPTV systems use Hierarchical aggregation.{{Citation needed|date=March 2009}} === Feedback Target === Feedback Target is a new type of member that has been firstly introduced by the Internet Draft draft-ietf-avt-rtcpssm-13.{{Ref RFC|5760}} The Hierarchical Aggregation method has extended its functionality. The function of this member is to receive Receiver Reports (RR) (see [[RTCP]]) and retransmit summarized RR packets, so-called Receiver Summary Information (RSI){{Ref RFC|5760}} to a sender (in case of single-level hierarchy).
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)