2 Ways in Which a WebRTC P2P CDN can Assist Internet Radio Stations?

April 30, 2015

WebRTC can fit nicely into interesting use cases. Radio broadcasting is one such use case.

Radio

Two things happened that budged me towards writing this post:

  1. A story about Norway ditching FM radio, going all digital
  2. Sitting for a talk with Hadar Weiss, Co-founder and CEO of Peer5

Radio isn’t a WebRTC P2P CDN use case that I covered yet, so it gets its own post.

For housekeeping purposes before we begin – I am an Advisor at Peer5. One of the reasons I accepted (they are the only one I am advising at the moment) is my interest in things other than video conferencing with WebRTC.

The challenge of Radio stations in the Internet age

Radio stations are moving towards the digital world. Part of it may be replacing broadcast channels from analog ones to digital ones, but a lot of it has to do with streaming over the internet. To do that, just like with the case of video over the internet, the media needs to be broadcasted. In Internet terms, that’s sending a stream to each and every person listening to the station. The more people listening, the more servers and bandwidth will be required.

A common scenario will take a successful radio station into the internet. They will open up a website for the station. Push their scheduling through it, enable forums and open up streaming to the audience. A few of their listeners will decide open up their web browser at work to listen in, keeping the web page open for the whole day.

Life is good.

There are masses of listeners on FM and a couple thousands over the internet. The server streams nicely. Everyone is happy.

One day, the marketing guy of the station has an epiphany – why not have a mobile app for the radio station? They outsource the development of such an app, and put some nice bells and whistles. When the day comes for the launch, they promote the hell out of it running ads on their radio station throughout the day.

The thousands of listeners they had over the internet? They become tens of thousands the next morning.

The server crashes from the load of it all.

True story.

Where WebRTC fits in radio

Where can WebRTC help? With its data channel, having it augment a CDN.

WebRTC in this use case, brings with it some interesting benefits/features:

1. Longer streaming sessions

Listeners stay tuned in to the station for longer periods of time. It happens because the user experience improves due to the use of WebRTC.

The great thing about a radio station is that everyone listens to the same thing. It is “real time” – a slight delay of up to 30 seconds is usually built into it. With regular CDNs and streaming servers, the browsers may experience periods when they pause while buffering incoming data. WebRTC enables reducing the probability of buffering by using prefetching, where the next couple of seconds, or even the next song, are side-loaded from other listeners.

If the radio station halts less, you will not be inclined to leave because of a bad experience.

2. Increased audience size for the same hardware

If you plan on getting more people to your station over the internet, or via your mobile app, you better be prepared. That means making sure you have a big enough operation running with a CDN in place or enough media servers to back up the demand.

WebRTC here can act as an insurance policy and as an optimizer of your server’s capacity. Radio has some interesting characteristics:

  1. Everyone tuning in to the station listen to the same media stream
  2. Many of the listeners are from the same geographic area

Using WebRTC for sideloading streams in P2P instead of directly from the server can offer a x5 increase in capacity. Now instead of supporting 10,000 listeners with your gear, you can support up to 50,000 listeners.

Where is this headed?

So we can gain increased capacity (=reducing our hosting costs) and improve user experience (=reducing buffering incidents). It doesn’t work at all times – it really depends on the technology used by the radio station to deliver their streams over the internet – the more modern the tech being used, the more you can gain by augmenting it with WebRTC.

At the same time, hosting and bandwidth costs are lowering.

Will we see more radio stations heading towards WebRTC to augment their media delivery, or will they continue using their current technologies? Only time will tell.

If you are interested in seeing WebRTC in action for audio, check out Peer5’s audio page.


You may also like

Two years of WebRTC Insights

Two years of WebRTC Insights
Comment

Your email address will not be published. Required fields are marked

  1. As U.S. spectrum gets increasingly crowded coupled with a trend to deregulate government agencies like the FCC, WebRTC for streaming radio content will become more widely used.

  2. Norway’s switching from FM broadcast radio to DAB broadcast radio. So WebRTC isn’t relevant for that.

    P2P has been tried before – by me, among other people – and the main issue is that it needs specific code to receive it. The same goes for WebRTC, I guess, too.

    10,000 listeners is a LOT for an internet radio station, by the way. Most do a fraction of that.

    1. James,

      While not directly connected, there is a move towards digital broadcast. Done over the internet instead of the airwaves means that WebRTC can play a role.

      As for WebRTC – the beauty here is that the specific code being received is taken care of by the browser already with little effort on the broadcaster’s side in changes to his current streaming setup for the internet.

      1. I was expected James to reply here, but since he hasn’t, I’ll paraphrase the discussion we had privately:

        1) Broadcast is totally different to online, so Internet really isn’t broadcast. To get the same economies of scale and so on, you’d need multicast technology – all possible, but few ISPs support it and we’re well outside the realms of what WebRTC can provide, sadly.

        2) I thought that browser support would have a useful impact on radio as well; however not only are there relatively few listeners online, but most of them listen using hardware “internet radios”, like the Pure Evoke Flow or Q2 WiFi Radio – these very much don’t support WebRTC.

  3. I use boombox.online they have many features ad browsers support

    10,000 listeners is a LOT for an internet radio station, by the way. Most do a fraction of that.

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}