This post is about communication from application to WebRTC using Web Services. For instance showing advertisements on WebRTC interface before p2p streaming or even during. Advertisements could be an overlay or an multiplexed stream.

WebRTC + Advertisement Engine

HTTP and XML is the basis for Web services. The WebRTC engine, in addition to media stream processing and transmitting , typically requires the support for mixing of streams for different sources. IT would also need the NAT/FW traversal support for media streams.

Approach 1 : Direct Play

Third Party advertisement Engine plays media file containing advertisement directly to the Caller Callee on their browser

Approach 2 : Direct Play

Use Multiplexing to embed the advertisement in the media content of the caller or callee using external media processing

Components of the Advertisement engine that interacts with the WeRTC engine

WSDL / Web Services Description Language. It specifies the location of the service and the operations (or methods) the service exposes.XML-based language for describing Web services.

SOAP / Simple Object Access Protocol. It is an XML based protocol for accessing Web Services and is based on XML

UDDI/ Universal Description, Discovery and Integration. It is a directory service where companies can search for Web services.
UDDI is described in WSDL. It communicates via SOAP

RDF / Resource Description Framework,. It is a framework for describing resources on the web and is written in XML

Logically the Communication Service provider or the platform hosting the WebRTC engine needs ti define the functional split between the WebRTC browser call and the third party webservice with which the WebRTC engine is interacting .

Other usecases of WebRTC with Web services can offer application-components like: currency conversion, weather reports, or even language translation as services.