Non si dispone dei permessi necessari per modificare questa pagina, per il seguente motivo:

La funzione richiesta è riservata agli utenti che appartengono al gruppo: Utenti.

È possibile visualizzare e copiare il codice sorgente di questa pagina.

Templates used on this page:

Torna a MultimediaCC.

Congestion Control for Real-time Communication[edit]

Congestion control for Real-Time media communication (Video-conferencing, Voice over IP) over the Internet is currently being addressed in IETF and W3C bodies aiming at standardizing a set of inter-operable protocols and APIs to enable real-time communication between Web browsers. The IETF working group (WG) RTP Media Congestion Avoidance Techniques (RMCAT) has been established in 2012 to propose the standardization of congestion control algorithms using the RTP. We are developing a congestion control algorithm for Web Real-time Communication (WebRTC). The proposed algorithm is used in Google Chrome and Google Hangouts.

Google Faculty Research Award

Smiley face

Google Faculty Award 2014 for designing a congestion control algorithm for real-time communication within the WebRTC framework to enable video conference among Web browsers.

  • Principal investigator: S. Mascolo
  • Title:Congestion Control for Web Real-Time Communication (WebRTC)
  • August 2014
  • Press coverage: Link

A description of the algorithm is provided in the IETF RMACT draft.

Google Congestion Control for WebRTC[edit]

System Architecture

Nowadays, the Internet is rapidly evolving to become an equally efficient platform for multimedia content delivery. Key examples are YouTube, Skype Audio/Video, IPTV, P2P video distribution platforms such as Coolstreaming or Joost, to name few. While YouTube streams videos using the Transmission Control Protocol (TCP), applications that are time-sensitive such as Video Conferencing employ the UDP because they can tolerate small loss percentages but not delays due to TCP recovery of losses via retransmissions. Since the UDP does not implement congestion control, these applications must implement those functionalities at the application layer. In these papers we experimentally evaluate the Google Congestion Control (GCC) which has been proposed in the RMCAT IETF WG. By setting up a controlled testbed, we have evaluated to what extent GCC flows are able to track the available bandwidth, while minimizing queuing delays, and fairly share the bottleneck with other GCC or TCP flows. We have found that the algorithm works as expected when a GCC flow accesses the bottleneck in isolation, whereas it is not able to provide a fair bandwidth utilization when a GCC flow shares the bottleneck with either a GCC or a TCP flow.

Google Congestion Control Architecture

Our experimental investigation has shown that the first version of GCC gets starved when a TCP flow joins the bottleneck (see Fig. below (a)). Moreover, we have found that starvation also occurs when two coexisting GCC flows share a bottleneck (see Fig. below (b) (c)).

Google Congestion Control Fairness Issues

To overcome these issues, we have proposed the adaptive threshold mechanism which sets the threshold used by the over-use detector. More details can be found in the following papers:

Fig. below shows how rate flows dynamics along with one way delay variations are nicely set after the introduction of the adaptive threshold.

Google Congestion Control with adaptive threshold'

Skype Video Congestion Control Responsiveness to Bandwidth Variations[edit]

This paper investigates Skype Video in order to discover at what extent this application is able to throttle its sending rate to match the unpredictable Internet bandwidth while preserving resource for co-existing best-effort TCP traffic.

Skype VoIP Congestion Control[edit]

Skype is the most popular VoIP application with over 250 million userbase spread all over the world. It is important to study how skype reacts to packet losses in order to infer if a huge amount of skype calls can result in a congestion collapse.

Next figures summarize main findings (more can be found in the paper: "An Experimental Investigation of the Congestion Control Used by Skype VoIP" pdf and slides).

Skype implements some mechanism to adapt the input rate to the available bandwidth[edit]

One Skype flow over a square waveform available bandwidth

The figure shows the sending rate, the loss rate and the available bandwidth. It can be noticed that Skype adapts its sending rate when the available bandwidth decreases but this adaptation takes 40s, thus leading to high packet loss rates.

Skype adapts to the available bandwidth very slowly[edit]

For the before mentioned reason Skype is not able to cope with sudden bandwidth variations as it can be seen in the next figure.

One Skype flow over a square waveform available bandwidth (higher frequency than before)

Skype is not TCP friendly[edit]

Skype's response to bandwidth variation is sluggish and leads to unfriendliness with respect to TCP flows.

One Skype flow versus one TCP flow

The Figure above shows that TCP connection suffers a large number of timeouts.

Skype is not able to guarantee fairness either[edit]

Two Skype calls have been placed flowing in the same bottleneck in order to investigate if Skype's congestion control is able to guarantee fairness.

Two Skype flows sharing the same bottleneck

Relevant bibliography[edit]