ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

WebRTC with Multiple Connections

Updated on May 16, 2014
SIP WebRTC
SIP WebRTC

WebRTC Architectures

Although it has yet to be standardized, WebRTC is being utilized by developers to provide simple RTC applications within apps on the web. Nevertheless WebRTC has the potential to power innovative solutions in other areas such as e-learning, interactive customer support etc. For example, a team of 5 or 6 people may want to collaborate on an office project or a school may want to broadcast a guest lecture to hundreds of students.

The above use cases involve multiple media streams being distributed to multiple endpoints. WebRTC was designed as a standards-based solution for peer to peer communication and it is not easy to scale video chats beyond two participants. However, service providers and business organizations have several alternatives when identifying a suitable architecture for multi-party WebRTC services. Some of them are:

Mesh Architecture

This is the simplest solution and involves the creation of multiple media streams in a mesh configuration connecting every endpoint. If a video call involves 3 participants, then three separate one-to-one data streams will be necessary. The mesh topology works very well when the number of endpoints is low. It is popular with service providers because it does not require setting up expensive infrastructure. On the other hand, bandwidth requirements will be quite high and mobile devices may not be able to handle the processing load.

Mixer Solution

This approach is analogous to the traditional server client network architecture. Enterprises can provision a central element which maintains individual media streams with each endpoint thus relieving the burden from mobile devices or legacy hardware. This solution has been used successfully in the past for multi-conference calls and the central element is often referred to as Multipoint Control Unit (MCU). The MCU handles transcoding, stream forwarding and is able to push different media streams with appropriate resolution as per the capabilities of the receiving device. Some service providers such as TokBox provide MCU capabilities in the cloud so that developers can take advantage of multiparty features without much set up.

Router Approach

Although it is not yet commonly used, routers are an inexpensive and scalable approach for multiparty services. A centrally located router receives media streams from every endpoint and sends out a corresponding stream to every other device. The router does not transcode media and usually only does packet inspection and forwarding.

Enterprises considering the use of WebRTC and signaling API for many-to-many or one-to-many services will need to assemble the necessary infrastructure and service providers are actively developing software to meet the needs of their clients.

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)