This is the “official” specification term given to the SFU (Selective Forwarding Unit). If you bump into this term, just “rename” it with SFU to put it in the context in which developers think of it 😀

The post SFM (Selective Forwarding Middlebox) appeared first on BlogGeek.me.

At times, the term is used to describe a type of video routing device, while at other times it will be used to indicate the support of routing technology and not a specific device.

An SFU is a media server component capable of receiving multiple media streams and then deciding which of these media streams should be sent to which participants. Its main use is in supporting group calls and live streaming/broadcast scenarios.

SFU performance

WebRTC SFUs are the most common media server architecture today when implementing large group meetings and live streaming services. The reason for that is that it gives the best return on investment. You will find SFU implementations in most video conferencing and group video meeting applications. In audio-only use cases they are a bit less popular, though there are a few that use them in these cases as well.

SFUs don’t process the media but rather route it around. As such, they consume considerably less CPU than their MCU alternative. Their performance relies heavily on network throughput.

When deploying SFU servers, it is recommended to place them as close as possible to the users that need to connect to them, spreading them geographically across the globe.

Technology used in SFUs

Common technologies used with an SFU include:

• Simulcast, enabling receiving multiple video streams at different bitrates and then selectively deciding which to forward to which viewer
• Temporal scalability used to create a video stream that has less dependencies between its frames, enabling dropping the frame rate on the bitstream when forwarding to certain viewers with less available bitrate (or need)
• SVC, used to send a single video stream from senders that has multiple layers in them that enable the SFU to strip some of these layers independently per viewer
• Insertable Streams, used to provide E2EE in group calls so that the SFUs will not have access to the actual media they are processing

The post SFU (Selective Forwarding Unit) appeared first on BlogGeek.me.

An MCU offers the ability to connect multiple participants in a single voice or video session.

MCUs generally implement the mixing architecture and are expensive due to their need for a lot of processing power per session.

The post MCU appeared first on BlogGeek.me.

An SBC is used in the context of VoIP networks to offer many functionalities:

• Security
• NAT traversal
• Interoperability
• Policy enforcement

SBCs were originally created as a temporary solution for NAT traversal and since then grew with functionality, encompassing things that exist in gateways for example.

While SBCs are not necessary in WebRTC, there are use cases and deployments of WebRTC where SBCs may be required.

The post SBC appeared first on BlogGeek.me.

In the context of WebRTC, Gateways are used to connect a WebRTC service to another type of network.

Most WebRTC gateways tend to lean towards connecting WebRTC to SIP and IMS.

WebRTC Gateways almost always need to also transcode voice and video due to the fact that WebRTC’s codecs are different than what exist in other VoIP systems.

The post Gateway appeared first on BlogGeek.me.