WebRTC Conference
Version 13 (Dan Pascu, 07/07/2017 02:33 pm) → Version 14/59 (Dan Pascu, 07/07/2017 02:39 pm)
h1. SylkServer WebRTC Managed Conference
h2. Design
Two types of conferences are being supported: ad-hoc conferences and moderated conferences.
h3. Ad-hoc conferences
An ad-hoc conference is a conference where all participants have the same status and no one is controlling what other are participants are doing. The participants are rendered in a matrix or up to 3x3 depending of how many participants are in the room. The layout switches automatically for everybody as participants join or leave.
The conference room has a fixed total bitrate configured by the server, that can be specified per room or globally with the max_bitrate setting in webrtcgateway.ini (see below). This bitrate is shared by all participants in the room, meaning that the more participants are in the room, the less bitrate each participant will use for the video stream they send, keeping the total room usage constant to the value configured by max_bitrate. The bitrate adjustment per participant is done automatically by sylkserver as participants join or leave the room, by diving the available bitrate among the number of participants. The end result of this is that each participant will send a fraction of max_bitrate (which is determined by the number of participants in the room) and will always receive a total combined of max_bitrate from all the participants in the room, no matter how many participants are in the room. The formula to compute the bitrate per participant is shown below:
<pre>
participant_send_bitrate = max_bitrate / max(number_of_participants - 1, 1)
</pre>
Using this formula we can make sure that each participant always receives max_bitrate traffic in incoming video streams, independent of the number of participants. The traffic send/received by each party can be expressed like (considering N to be the number of participants and N>1):
<pre>
participant_sent_traffic = max_bitrate / (N - 1)
participant_received_traffic = max_bitrate
sylkserver_sent_traffic = max_bitrate * N (participant_received_traffic * N)
sylkserver_received_traffic = max_bitrate * N / (N - 1) (participant_sent_traffic * N)
</pre>
h3. Moderated conferences
A moderated conference is a conference where a moderator can decide the flow of the conference. The moderator is the first participant to join the conference. The moderator has the ability to see a list with all the participants, can select 1 or 2 of them to be the active speakers and also has the ability to mute other participants (audio and/or video). The moderator can also change the active speakers at any time.
h2. Features
h3. Ad-hoc conference
All participants are rendered in a matrix where each participants has the same size. The conference room has a fixed total bandwidth set by the server, which is divided between the participants, which means the more participants are in the room, the less bandwidth each participant will use keeping the bandwidth usage per conference room constant.
h3. Managed conference
The first participants becomes the manager. He can add/remove mute participants and also decide which one is the active speaker(s).
h2. Configuration
Sylkserver allows the maximum bitrate and video codec to be configured, globally or per room with the following settings in webrtcgateway.ini file:
<pre>
; Maximum video bitrate allowed per sender in a room in bits/s. This value is
; applied to any room that doesn't define its own. The value is any integer
; number between 64000 and 4194304. Default value is 2016000 (~2Mb/s).
; max_bitrate = 2016000
; The video codec to be used by all participants in a room. This value is
; applied to any room that doesn't define its own.
; Possible values are: h264, vp8 and vp9. Default is vp9.
; video_codec = vp9
</pre>
h2. Client support
h2. Measurements
This measurement was done on a Macbook Pro 15" with a 2.3GHz Intel Core I7 CPU, while having 7 participants in the room with each using 336Kb/s. The measurement shows the CPU usage in Firefox with the aforementioned conditions, for the specified video codecs and resolutions which are used by all participants:
<pre>
* H264/VGA - 150% CPU
* H264/HD - 250% CPU
* VP9/VGA - 220% CPU
* VP9/HD - 350% CPU
</pre>
h2. Remaining tasks
* sylkserver: control interface for moderator
* janus: patch to request full frames when a paused video is resumed
h2. Design
Two types of conferences are being supported: ad-hoc conferences and moderated conferences.
h3. Ad-hoc conferences
An ad-hoc conference is a conference where all participants have the same status and no one is controlling what other are participants are doing. The participants are rendered in a matrix or up to 3x3 depending of how many participants are in the room. The layout switches automatically for everybody as participants join or leave.
The conference room has a fixed total bitrate configured by the server, that can be specified per room or globally with the max_bitrate setting in webrtcgateway.ini (see below). This bitrate is shared by all participants in the room, meaning that the more participants are in the room, the less bitrate each participant will use for the video stream they send, keeping the total room usage constant to the value configured by max_bitrate. The bitrate adjustment per participant is done automatically by sylkserver as participants join or leave the room, by diving the available bitrate among the number of participants. The end result of this is that each participant will send a fraction of max_bitrate (which is determined by the number of participants in the room) and will always receive a total combined of max_bitrate from all the participants in the room, no matter how many participants are in the room. The formula to compute the bitrate per participant is shown below:
<pre>
participant_send_bitrate = max_bitrate / max(number_of_participants - 1, 1)
</pre>
Using this formula we can make sure that each participant always receives max_bitrate traffic in incoming video streams, independent of the number of participants. The traffic send/received by each party can be expressed like (considering N to be the number of participants and N>1):
<pre>
participant_sent_traffic = max_bitrate / (N - 1)
participant_received_traffic = max_bitrate
sylkserver_sent_traffic = max_bitrate * N (participant_received_traffic * N)
sylkserver_received_traffic = max_bitrate * N / (N - 1) (participant_sent_traffic * N)
</pre>
h3. Moderated conferences
A moderated conference is a conference where a moderator can decide the flow of the conference. The moderator is the first participant to join the conference. The moderator has the ability to see a list with all the participants, can select 1 or 2 of them to be the active speakers and also has the ability to mute other participants (audio and/or video). The moderator can also change the active speakers at any time.
h2. Features
h3. Ad-hoc conference
All participants are rendered in a matrix where each participants has the same size. The conference room has a fixed total bandwidth set by the server, which is divided between the participants, which means the more participants are in the room, the less bandwidth each participant will use keeping the bandwidth usage per conference room constant.
h3. Managed conference
The first participants becomes the manager. He can add/remove mute participants and also decide which one is the active speaker(s).
h2. Configuration
Sylkserver allows the maximum bitrate and video codec to be configured, globally or per room with the following settings in webrtcgateway.ini file:
<pre>
; Maximum video bitrate allowed per sender in a room in bits/s. This value is
; applied to any room that doesn't define its own. The value is any integer
; number between 64000 and 4194304. Default value is 2016000 (~2Mb/s).
; max_bitrate = 2016000
; The video codec to be used by all participants in a room. This value is
; applied to any room that doesn't define its own.
; Possible values are: h264, vp8 and vp9. Default is vp9.
; video_codec = vp9
</pre>
h2. Client support
h2. Measurements
This measurement was done on a Macbook Pro 15" with a 2.3GHz Intel Core I7 CPU, while having 7 participants in the room with each using 336Kb/s. The measurement shows the CPU usage in Firefox with the aforementioned conditions, for the specified video codecs and resolutions which are used by all participants:
<pre>
* H264/VGA - 150% CPU
* H264/HD - 250% CPU
* VP9/VGA - 220% CPU
* VP9/HD - 350% CPU
</pre>
h2. Remaining tasks
* sylkserver: control interface for moderator
* janus: patch to request full frames when a paused video is resumed