US10581927B2

US10581927B2 - Providing web real-time communications (WebRTC) media services via WebRTC-enabled media servers, and related methods, systems, and computer-readable media

Info

Publication number: US10581927B2
Application number: US14/255,361
Authority: US
Inventors: Joel Ezell; John H. Yoakum
Original assignee: Avaya Inc
Current assignee: Avaya Inc
Priority date: 2014-04-17
Filing date: 2014-04-17
Publication date: 2020-03-03
Also published as: US20150304379A1

Abstract

In one embodiment, a system for providing WebRTC media services comprises a WebRTC-enabled media server including a scripting engine, a WebRTC functionality provider, and a control application programming interface (API). The WebRTC-enabled media server is configured to receive, from a WebRTC application server, a stream establishment application, and to establish, via the stream establishment application, a plurality of WebRTC interactive flows associated with a corresponding plurality of WebRTC clients. The WebRTC-enabled media server is also configured to apply a media service to one or more of the plurality of WebRTC interactive flows to generate one or more media server flows, and provide the media server flows to one or more of the plurality of WebRTC clients. The WebRTC-enabled media server may thus provide functionality via familiar WebRTC control interfaces.

Description

BACKGROUND Field of the Disclosure

The technology of the disclosure relates generally to Web Real-Time Communications (WebRTC) interactive flows.

Technical Background

Web Real-Time Communications (WebRTC) represents an ongoing effort to develop industry standards for integrating real-time communications functionality into web clients, such as web browsers, to enable direct interaction with other web clients. This real-time communications functionality is accessible by web developers via standard markup tags, such as those provided by version 5 of the Hypertext Markup Language (HTML5), and client-side scripting Application Programming Interfaces (APIs) such as JavaScript APIs. More information regarding WebRTC may be found in WebRTC: APIs and RTCWEB Protocols of the HTML5 Real-Time Web,” by Alan B. Johnston and Daniel C. Burnett, 2^ndEdition (2013 Digital Codex LLC), which is incorporated herein in its entirety by reference.

WebRTC provides built-in capabilities for establishing real-time video, audio, and/or data streams in both point-to-point interactive sessions and multi-party interactive sessions. The WebRTC standards are currently under joint development by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF). Information on the current state of WebRTC standards can be found at, e.g., http://www.w3c.org and http://www.ietf.org.

To establish a WebRTC interactive flow (e.g., a real-time video, audio, and/or data exchange), two WebRTC clients may retrieve WebRTC-enabled web applications, such as HTML5/JavaScript web applications, from a WebRTC application server. Through the web applications, the two WebRTC clients then engage in dialogue for initiating a peer connection over which the WebRTC interactive flow will pass. The initiation dialogue may include a media negotiation used to reach an agreement on parameters that define characteristics of the WebRTC interactive flow. Once the initiation dialogue is complete, the WebRTC clients may then establish a direct peer connection with one another, and may begin an exchange of media and/or data packets transporting real-time communications. The peer connection between the WebRTC clients typically employs the Secure Real-time Transport Protocol (SRTP) to transport real-time media flows, and may utilize various other protocols for real-time data interchange.

The WebRTC clients may be connected using a “full mesh” topology, in which each WebRTC client participating in the real-time communications establishes a peer connection with every other participating WebRTC client. In some circumstances, though, a full mesh topology may be prohibitively expensive in terms of network bandwidth and/or computing resources. As an alternative to a full mesh topology, each of the WebRTC clients may connect to a central media server, which mixes and distributes the WebRTC interactive flows to the participating WebRTC clients. The media server may also provide various types of media processing functionality (e.g., inserting announcements into, recording, switching, and/or redirecting WebRTC interactive flows, as non-limiting examples) that are accessible by the WebRTC application. However, conventional media servers typically require developers to be familiar with control interfaces that are based on Session Initiation Protocol (SIP) or other protocols outside the scope of expertise of many WebRTC application developers. As a result, developers may face a steep learning curve, which may present an obstacle to implementation of WebRTC applications utilizing media server functionality.

SUMMARY OF THE DETAILED DESCRIPTION

Embodiments disclosed in the detailed description include providing Web Real-Time Communications (WebRTC) media services via WebRTC-enabled media servers. Related methods, systems, and computer-readable media are also disclosed. In this regard, in one embodiment, a WebRTC-enabled media server provides media services by implementing a standard WebRTC client application programming interface (API). The WebRTC-enabled media server provides a scripting engine, a WebRTC functionality provider, and a control API for accessing a functionality of the WebRTC functionality provider. Together, these elements allow the WebRTC-enabled media server to interact with WebRTC peers, in much the same way as a conventional WebRTC client, while simultaneously providing media server functionality. The WebRTC-enabled media server receives a stream establishment application from a WebRTC application server. The stream establishment application may comprise one or more JavaScript web applications, as a non-limiting example. The WebRTC-enabled media server uses the stream establishment application to establish WebRTC interactive flows with multiple WebRTC clients, and applies a media service to one or more of the WebRTC interactive flows to generate one or more media server flows. The one or more media server flows is then provided to one or more of the WebRTC clients. The media service may be applied to the one or more WebRTC interactive flows in response to media server commands that the WebRTC-enabled media server receives from the WebRTC application server via the control API. The WebRTC-enabled media server may also generate media server events as a result of applying the media service, and may provide the media server events to the WebRTC application server via the control API. In this manner, media processing functionality of the WebRTC-enabled media server may be accessed by the WebRTC application server through the use of interfaces familiar to WebRTC application developers.

In another embodiment, a system for providing WebRTC media services includes at least one communications interface and a WebRTC-enabled media server. The WebRTC-enabled media server comprises a scripting engine and a WebRTC functionality provider, and is communicatively coupled to a WebRTC application server and a plurality of WebRTC clients via the at least one communications interface. The WebRTC-enabled media server is configured to provide a control API for accessing a functionality of the WebRTC functionality provider. The WebRTC-enabled media server is also configured to receive, from the WebRTC application server, a stream establishment application. The WebRTC-enabled media server is additionally configured to establish, via the stream establishment application, a plurality of WebRTC interactive flows associated with corresponding ones of the plurality of WebRTC clients. The WebRTC-enabled media server is also configured to apply a media service to one or more of the plurality of WebRTC interactive flows to generate one or more media server flows. The WebRTC-enabled media server is additionally configured to provide the one or more media server flows to one or more of the plurality of WebRTC clients.

In another embodiment, a method for providing WebRTC media services is provided. The method comprises providing, by a WebRTC-enabled media server executing on a computing device, a control API for accessing a functionality of a WebRTC functionality provider of the WebRTC-enabled media server. The method also comprises receiving, by the WebRTC-enabled media server, a stream establishment application from a WebRTC application server. The method further comprises establishing, via the stream establishment application, a plurality of WebRTC interactive flows associated with corresponding ones of a plurality of WebRTC clients. The method also comprises applying a media service to one or more of the plurality of WebRTC interactive flows to generate one or more media server flows. The method additionally comprises providing the one or more media server flows to one or more of the plurality of WebRTC clients.

In another embodiment, a non-transitory computer-readable medium having stored thereon computer-executable instructions to cause a processor to implement a method for providing WebRTC media services is provided. The method implemented by the computer-executable instructions comprises providing, by a WebRTC-enabled media server, a control API for accessing a functionality of a WebRTC functionality provider of the WebRTC-enabled media server. The method implemented by the computer-executable instructions also comprises receiving, by the WebRTC-enabled media server, a stream establishment application from a WebRTC application server. The method implemented by the computer-executable instructions further comprises establishing, via the stream establishment application, a plurality of WebRTC interactive flows associated with corresponding ones of a plurality of WebRTC clients. The method implemented by the computer-executable instructions also comprises applying a media service to one or more of the plurality of WebRTC interactive flows to generate one or more media server flows. The method implemented by the computer-executable instructions additionally comprises providing the one or more media server flows to one or more of the plurality of WebRTC clients.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

FIG. 1 is a conceptual diagram illustrating a Web Real-Time Communications (WebRTC) interactive session between two WebRTC clients using a WebRTC-enabled media server;

FIG. 2 is a flowchart illustrating exemplary operations of the WebRTC-enabled media server of FIG. 1 for providing WebRTC media services;

FIG. 3 is a flowchart illustrating further exemplary operations, in addition to the operations of FIG. 2, for providing WebRTC media services via the WebRTC-enabled media server of FIG. 1;

FIG. 4 is a diagram illustrating exemplary communications flows within an exemplary system including the WebRTC-enabled media server of FIG. 1; and

FIG. 5 is a block diagram of an exemplary processor-based system that may include the WebRTC-enabled media server of FIG. 1.

DETAILED DESCRIPTION

With reference now to the drawing figures, several exemplary embodiments of the present disclosure are described. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

FIG. 1 illustrates an exemplary WebRTC interactive system 10 for providing WebRTC media services via WebRTC-enabled media servers as disclosed herein. In particular, the exemplary WebRTC interactive system 10 provides a WebRTC-enabled media server 12 that executes on a computing device 14. The WebRTC-enabled media server 12 is configured to establish WebRTC interactive sessions with WebRTC peers in a manner similar to a conventional WebRTC client, and is further configured to provide media services to a WebRTC application server 16. As used herein, a “WebRTC interactive session” refers to operations for carrying out a WebRTC offer/answer exchange, establishing a peer connection, and commencing a WebRTC interactive flow between two or more endpoints (e.g., two or more WebRTC clients). A “WebRTC interactive flow,” as disclosed herein, refers to an interactive media flow and/or an interactive data flow that passes between or among two or more endpoints according to the WebRTC standards and protocols known in the art. As non-limiting examples, an interactive media flow constituting a WebRTC interactive flow may comprise a real-time audio stream and/or a real-time video stream, or other real-time media or data streams. Data and/or media comprising a WebRTC interactive flow may be collectively referred to herein as “content.”

For purposes of illustration, a WebRTC interactive flow 18 is shown in FIG. 1 as passing between the computing device 14 and a computing device 20, and a WebRTC interactive flow 22 is shown as passing between the computing device 14 and a computing device 24. It is to be understood that the

computing devices

14, 20, and 24 may all be located within the same public or private network, or may be located within separate, communicatively coupled public or private networks. Some embodiments of the WebRTC interactive system 10 of FIG. 1 may provide that each of the

computing devices

14, 20, and 24 may be any computing device having network communications capabilities, such as a smartphone, a tablet computer, a dedicated web appliance, a media server, a desktop or server computer, or a purpose-built communications device, as non-limiting examples. The

computing devices

14, 20, and 24 include communications interfaces 26, 28, and 30, respectively, for connecting the

computing devices

14, 20, and 24 to one or more public and/or private networks. In some embodiments, the elements of the

computing devices

14, 20, and 24 may be distributed across more than one

computing device

14, 20, and 24.

The

computing devices

20 and 24 of FIG. 1 include

WebRTC clients

32 and 34, respectively. Each of the

WebRTC clients

32 and 34 may be a WebRTC-enabled web browser application, a dedicated communications application, a mobile application, or an interface-less application, such as a daemon or service application, as non-limiting examples. In this embodiment, the WebRTC client 32 comprises a scripting engine 36 and a WebRTC functionality provider 38. The scripting engine 36 enables client-side applications written in a scripting language, such as JavaScript, to be executed within the WebRTC client 32. The scripting engine 36 also provides an API to facilitate communications with other functionality providers within the WebRTC client 32 and/or the computing device 20, and/or with other web clients, user devices, or web servers. The WebRTC functionality provider 38 implements the protocols, codecs, and APIs necessary to enable real-time communications via WebRTC. The scripting engine 36 and the WebRTC functionality provider 38 are communicatively coupled via a set of defined APIs, as indicated by bidirectional arrow 40. The WebRTC client 34 also includes a scripting engine 42 and a WebRTC functionality provider 44 for providing functionality similar to that of the scripting engine 36 and the WebRTC functionality provider 38, respectively, of the WebRTC client 32. The scripting engine 42 and the WebRTC functionality provider 44 of the WebRTC client 34 are communicatively coupled via a set of defined APIs, as indicated by bidirectional arrow 46.

To establish a WebRTC interactive session, the WebRTC client 32 and the WebRTC client 34 each downloads a WebRTC application 48 from the WebRTC application server 16 (e.g., via Hyper Text Transfer Protocol (HTTP)/Hyper Text Transfer Protocol Secure (HTTPS) connections). In some embodiments, the WebRTC application 48 may comprise an HTML5/JavaScript web application that provides a rich user interface using HTML5, and uses JavaScript to handle user input and to communicate with the WebRTC application server 16. It is to be understood that the WebRTC application 48 may comprise multiple, interoperable WebRTC applications tailored for specific characteristics (such as operating systems and/or platforms) of the

WebRTC clients

32 and 34.

In a typical peer-to-peer architecture, the WebRTC client 32 and the WebRTC client 34 engage in an initiation dialogue (not shown) with one another to negotiate media types and capabilities of the desired WebRTC interactive session. In some embodiments, the initiation dialogue may include a WebRTC offer/answer exchange in which WebRTC session description objects (not shown) are exchanged between the

WebRTC clients

32 and 34 via the WebRTC application server 16. After the initiation dialogue is complete, a WebRTC interactive flow is established directly between the WebRTC client 32 and the WebRTC client 34 via a peer connection. In some embodiments, the WebRTC client 32 and the WebRTC client 34 may each connect to a conventional media server (not shown). The conventional media server may mix and distribute WebRTC interactive flows to the

WebRTC clients

32 and 34, and may provide other media processing functionality such as inserting announcements into, recording, and/or redirecting the WebRTC interactive flows, as non-limiting examples. However, a conventional media server may require developers to be familiar with control interfaces based on protocols (e.g., Session Initiation Protocol (SIP)) that may be outside the scope of expertise of many WebRTC application developers.

In this regard, the WebRTC-enabled media server 12 is provided to establish WebRTC interactive sessions with WebRTC peers in a manner similar to a conventional WebRTC client, and to provide media services to the WebRTC application server 16 using an interface more accessible to WebRTC application developers. The WebRTC-enabled media server 12 provides a scripting engine 50 and a media handling functionality provider 52. The WebRTC-enabled media server 12 also provides a control API 54, through which a functionality of the media handling functionality provider 52 may be accessed and controlled. In some embodiments, the scripting engine 50 and the media handling functionality provider 52 may be communicatively coupled to each other via the control API 54 as indicated by

bidirectional arrows

56 and 58.

The scripting engine 50 of the WebRTC-enabled media server 12 provides functionality corresponding to that of the

scripting engines

36 and 42 of the

WebRTC clients

32 and 34, respectively. The media handling functionality provider 52 includes a WebRTC functionality provider 60, which provides functionality corresponding to that of the

WebRTC functionality providers

38 and 44 of the

WebRTC clients

32 and 34, respectively. The media handling functionality provider 52 also provides media processing functionality similar to that provided by conventional media servers. The control API 54 defines one or more media server commands 62 that the WebRTC-enabled media server 12 may receive from the WebRTC application server 16 to apply media services to WebRTC interactive flows. The control API 54 may further specify one or more media server events 64 that the WebRTC-enabled media server 12 may generate to notify the WebRTC application server 16 of relevant occurrences during or resulting from applying the media services. The control API 54 may comprise a Web-accessible API configured to receive the media server commands 62 from and/or provide the media server events 64 to the WebRTC application server 16. As a non-limiting example, the control API 54 may include a Representational State Transfer (REST) API and/or a JavaScript API. In some embodiments in which the control API 54 comprises a JavaScript API, the control API 54 may receive the media server commands 62 and/or provide the media server events 64 via a media control application 65 executed by the scripting engine 50.

As seen in FIG. 1, the WebRTC-enabled media server 12 is configured to receive a stream establishment application 66 from the WebRTC application server 16, as indicated by arrow 68. Some embodiments may provide that the WebRTC-enabled media server 12 also receives the media control application 65 from the WebRTC application server 16, as indicated by arrow 69. The stream establishment application 66 and/or the media control application 65 may each comprise a JavaScript application, as a non-limiting example. In some embodiments, the stream establishment application 66 and/or the media control application 65 are downloaded upon startup of the WebRTC-enabled media server 12, and/or upon association of the WebRTC-enabled media server 12 with the WebRTC application server 16. Some embodiments may provide that a same version of the stream establishment application 66 and/or the media control application 65 may be used by more than one WebRTC application server 16, and/or a custom version of the stream establishment application 66 and/or the media control application 65 may be used by one or more WebRTC application servers 16. The download location for the stream establishment application 66 and/or the media control application 65 may be specified by a value set within the WebRTC-enabled media server 12 prior to or during execution of the WebRTC-enabled media server 12, or may be set by a web service invocation from the WebRTC application server 16.

The stream establishment application 66 provides functionality for establishing the WebRTC interactive flows 18 and 22 between the WebRTC-enabled media server 12 and the

WebRTC clients

32 and 34. In some embodiments, the stream establishment application 66 may also be downloaded from the WebRTC application server 16 by the WebRTC client 32 and the WebRTC client 34 as part of the WebRTC application 48. The stream establishment application 66 downloaded by the

WebRTC clients

32 and 34 and the WebRTC-enabled media server 12 may be the same application across all platforms and devices, or different platform- or device-specific versions of the stream establishment application 66 may be provided. In some embodiments, the stream establishment application 66 may be downloaded by the

WebRTC clients

32 and 34 each time a WebRTC interactive session is to be established.

62 Using the scripting engine 50 and the media handling functionality provider 52, the WebRTC-enabled media server 12 may interact with the

WebRTC clients

32 and 34 to establish the WebRTC interactive flows 18 and 22. In the example of FIG. 1, the stream establishment application 66, downloaded by the

WebRTC clients

32 and 34 as part of the WebRTC application 48, directs the

WebRTC clients

32 and 34 to engage in

initiation dialogues

70 and 72, respectively, with the WebRTC-enabled media server 12. In response to the

initiation dialogues

70 and 72, the scripting engine 50 of the WebRTC-enabled media server 12 employs the stream establishment application 66 to establish the WebRTC interactive flows 18 and 22 with the

respective WebRTC clients

32 and 34. To further facilitate interoperability with the WebRTC application server 16 and the

WebRTC clients

32 and 34, the WebRTC-enabled media server 12 may provide support for standard transport mechanisms (e.g., WebSockets, as a non-limiting example), as well as mechanisms required by WebRTC specifications such as Interactive Connectivity Establishment (ICE), Session Traversal Utilities for Network Address Translation (STUN), and/or Traversal Using Relays around Network Address Translation (TURN).

After the WebRTC interactive flows 18 and 22 are established, the media handling functionality provider 52 of the WebRTC-enabled media server 12 may apply a media service to content of incoming media and/or data streams received from one or more of the WebRTC interactive flows 18 and 22 to generate one or more of outgoing media server flows 74 and 76. In the example of FIG. 1, the media handling functionality provider 52 may be controlled by the WebRTC application server 16 via the control API 54, and/or may be controlled by the media control application 65 executed by the scripting engine 50 of the WebRTC-enabled media server 12. As non-limiting examples, applying the media service may include mixing the WebRTC interactive flows 18 and 22, switching the media server flows 74 and 76, inserting content into one or more of the WebRTC interactive flows 18 and 22, recording one or more of the WebRTC interactive flows 18 and 22, redirecting one or more of the WebRTC interactive flows 18 and 22, performing text-to-speech conversion on one or more of the WebRTC interactive flows 18 and 22, and/or performing speech recognition on one or more of the WebRTC interactive flows 18 and 22.

In some embodiments, operation of the WebRTC functionality provider 60 of the WebRTC-enabled media server 12 may be controlled by the media server command(s) 62 received from the WebRTC application server 16. The media server command(s) 62 may be received via an HTTP request (such as an HTTP GET request) and/or via WebSockets signaling. In some embodiments, the media server command(s) 62 may comprise a REST API invocation received by the control API 54 from the WebRTC application server 16. According to some embodiments, the media server command(s) 62 may comprise a JavaScript API invocation received by the media control application 65 from the WebRTC application server 16 and relayed to the control API 54.

Some embodiments may provide that the WebRTC functionality provider 60 of the WebRTC-enabled media server 12 generates the media server event(s) 64 as a result of applying the media service to the WebRTC interactive flows 18 and 22. For example, the WebRTC-enabled media server 12 may notify the WebRTC application server 16 that an announcement has completed, or that input of dual-tone multi-frequency (DTMF) digits has been detected. The media server event(s) 64 may be sent to the WebRTC application server 16 via an HTTP request (such as an HTTP POST request) or by WebSockets, as non-limiting examples. In some embodiments, the media server event(s) 64 may be provided to the WebRTC application server 16 via a REST API by the control API 54. According to some embodiments, the media server event(s) 64 may be provided to the WebRTC application server 16 via a JavaScript API of the media control application 65.

The specific content and format of the media server command(s) 62 and the media server event(s) 64 may be determined by the control API 54 and/or may specified by the media control application 65. In some embodiments, the control API 54 may accept standard WebRTC objects, such as a PeerConnection object, as parameters. The control API 54 may be based on APIs such as Java Specification Request (JSR) 309, as a non-limiting example.

It is to be understood that the WebRTC-enabled media server 12 may provide media services concurrently to multiple WebRTC application servers 16. For example, the WebRTC-enabled media server 12 may receive, and concurrently execute, a unique stream establishment application 66 and/or a unique media control application 65 for each of multiple WebRTC application servers 16. In some embodiments, the WebRTC-enabled media server 12 may provide a separate instance of the scripting engine 50 and/or the media handling functionality provider 52 for each of multiple concurrent WebRTC interactive sessions.

To generally describe exemplary operations of the WebRTC-enabled media server 12 of FIG. 1 for providing WebRTC media services, FIG. 2 is provided. For the sake of clarity, elements of FIG. 1 are referenced in describing FIG. 2. In the example of FIG. 2, operations begin with the WebRTC-enabled media server 12, executing on the computing device 14, providing the control API 54 for accessing a functionality of the WebRTC functionality provider 60 of the WebRTC-enabled media server 12 (block 77). The control API 54 specifies the media server command(s) 62 that may be received from the WebRTC application server 16, as well as the media server event(s) 64 that may be generated by the WebRTC-enabled media server 12. The WebRTC-enabled media server 12 then receives the stream establishment application 66 from the WebRTC application server 16 (block 78). The stream establishment application 66 enables the WebRTC-enabled media server 12 to establish the WebRTC interactive flows 18 and 22 with the

WebRTC clients

32 and 34.

The WebRTC-enabled media server 12 next establishes a plurality of WebRTC interactive flows 18, 22, each of which is associated with a respective one of a plurality of

WebRTC clients

32, 34, via the stream establishment application 66 (block 80). According to some embodiments provided herein, the WebRTC interactive flows 18 and 22 may be established in response to the

initiation dialogues

70 and 72 that are initiated by the

WebRTC clients

32 and 34, respectively, or in response to initiation dialogues (not shown) that are initiated by the WebRTC-enabled media server 12. Some embodiments may provide that the

initiation dialogues

70 and 72 are initiated at the direction of the WebRTC application 48 and/or the WebRTC application server 16.

Once the plurality of WebRTC interactive flows 18, 22 is established, the WebRTC-enabled media server 12 applies a media service to one or more of the plurality of WebRTC interactive flows 18, 22 to generate one or more media server flows 74, 76 (block 82). The media server flows 74, 76 may include data from either or both of the WebRTC interactive flows 18, 22, and/or additional content (such as an announcement) inserted into the WebRTC interactive flows 18, 22 by the WebRTC-enabled media server 12. The WebRTC-enabled media server 12 then provides the one or more media server flows 74, 76 to one or more of the plurality of WebRTC clients 32, 34 (block 84). In this manner, the WebRTC-enabled media server 12 may provide a usable, intuitive interface to WebRTC application developers for providing media functionality to the WebRTC application server 16.

FIG. 3 is a flowchart illustrating optional exemplary operations, in addition to the operations of FIG. 2, for providing WebRTC media services via the WebRTC-enabled media server 12 of FIG. 1. As seen in FIG. 3, the WebRTC-enabled media server 12 may receive, via the control API 54, a media server command 62 from the WebRTC application server 16 (block 86). The media server command 62 may be received via an HTTP request (such as an HTTP GET request) and/or via WebSockets signaling, and may indicate a media service requested by the WebRTC application server 16. In some embodiments, the media server command 62 may be received via a REST API invocation and/or a JavaScript API invocation. The WebRTC-enabled media server 12 may thus apply a media service indicated by the media server command 62 to one or more of the WebRTC interactive flows 18, 22 (block 88).

The WebRTC-enabled media server 12 may also generate a media server event 64 as a result of applying the media service to the one or more of the plurality of WebRTC interactive flows 18, 22 (block 90). For instance, the WebRTC-enabled media server 12 may generate a media server event 64 to notify the WebRTC application server 16 that an announcement has completed, or that input of DTMF digits has been detected. In some embodiments, the media server event 64 may be provided via a REST API and/or a JavaScript API. The WebRTC-enabled media server 12 may then provide the media server event 64 to the WebRTC application server 16 via the control API 54 (block 92).

To illustrate exemplary communications flows during the establishment of a WebRTC interactive session and the provision of media services using the WebRTC-enabled media server 12 of FIG. 1, FIG. 4 is provided. In FIG. 4, the scripting engine 36 and the WebRTC functionality provider 38 of the WebRTC client 32, the WebRTC application server 16, the scripting engine 50, the control API 54, and the WebRTC functionality provider 60 of the WebRTC-enabled media server 12, and the scripting engine 42 and the WebRTC functionality provider 44 of the WebRTC client 34 are each represented by vertical dotted lines. It is to be understood for this example that the WebRTC client 32 and the WebRTC client 34 have each downloaded a WebRTC-enabled application, such as the WebRTC application 48, from the WebRTC application server 16. It is to be further understood that the WebRTC-enabled application downloaded by each of the

WebRTC clients

32 and 34 includes the stream establishment application 66.

As seen in FIG. 4, the scripting engine 50 of the WebRTC-enabled media server 12 first downloads the stream establishment application 66 from the WebRTC application server 16. For embodiments in which the WebRTC application server 16 controls the WebRTC functionality provider 60 via a JavaScript API, the scripting engine 50 may also optionally download the media control application 65 from the WebRTC application server 16. The scripting engine 50 may download the stream establishment application 66 and/or the media control application 65 based on a download location set within the WebRTC-enabled media server 12 prior to or during execution of the WebRTC-enabled media server 12, or set by a web service invocation (not shown) from the WebRTC application server 16.66

The WebRTC-enabled media server 12 then creates an open channel 94 to the WebRTC application server 16, through which the WebRTC application server 16 may request media services. In some embodiments, the open channel 94 may be created using an HTTP request (such as an HTTP GET request), or may be created using WebSockets. It is to be understood that multiple open channels 94 may be maintained by the WebRTC-enabled media server 12, thus enabling multiple concurrent media service requests to be handled.

Next, the establishment of a WebRTC interactive session between the WebRTC client 32 and the WebRTC-enabled media server 12 begins with the scripting engine 36 of the WebRTC client 32 sending a WebRTC session description object to the scripting engine 50 of the WebRTC-enabled media server 12 via an HTTPS connection. In this example, the WebRTC session description object is a Session Description Protocol (SDP) object, and is referred to as SDP Object A (arrow 96). SDP Object A represents the “offer” in a WebRTC offer/answer exchange, and specifies the media types and capabilities that the WebRTC client 32 supports and prefers for use in the WebRTC interactive session. After the scripting engine 50 of the WebRTC-enabled media server 12 receives the SDP Object A from the WebRTC client 32, the scripting engine 50 sends a WebRTC session description object in response, referred to as SDP Object B (arrow 98), via HTTPS to the WebRTC client 32. The SDP Object B in this example represents the “answer” in the WebRTC offer/answer exchange. The WebRTC interactive flow 18 is then established between the WebRTC client 32 and the WebRTC-enabled media server 12. Establishing the WebRTC interactive flow 18 may include “hole punching” to determine the best way to establish direct communications, as well as key negotiations to establish secure connections. It is to be understood that establishing the WebRTC interactive flow 18 may be accomplished through operations of the stream establishment application 66 executed by the scripting engine 50 of the WebRTC-enabled media server 12 and the scripting engine 36 of the WebRTC client 32.

With continuing reference to FIG. 4, a WebRTC interactive session is also established between the WebRTC client 34 and the WebRTC-enabled media server 12. It is to be understood that operations for establishing a WebRTC interactive session between the WebRTC client 34 and the WebRTC-enabled media server 12 may occur before, concurrently with, or after the establishment of the WebRTC interactive flow 18 between the WebRTC client 32 and the WebRTC-enabled media server 12. As seen in FIG. 4, the scripting engine 42 of the WebRTC client 34 sends a WebRTC session description object to the scripting engine 50 of the WebRTC-enabled media server 12 via an HTTPS connection. The WebRTC session description object in this example is a SDP object referred to as SDP Object C (arrow 100), and specifies the media types and capabilities supported and/or preferred for use by the WebRTC client 34. In response to receiving the SDP Object C from the WebRTC client 34, the scripting engine 50 sends a WebRTC session description object, referred to as SDP Object D (arrow 102), via HTTPS to the WebRTC client 34. The SDP Object D represents the “answer” in the WebRTC offer/answer exchange. Based on the offer/answer exchange, the WebRTC interactive flow 22 is then established between the WebRTC client 34 and the WebRTC-enabled media server 12. It is to be understood that establishing the WebRTC interactive flow 22 may be accomplished through operations of the stream establishment application 66 being executed by the scripting engine 50 of the WebRTC-enabled media server 12 and the scripting engine 42 of the WebRTC client 34.

After the WebRTC interactive flows 18 and 22 are established, the WebRTC-enabled media server 12 generates one or more media server flows 74 and 76 by applying media services to one or more of the WebRTC interactive flows 18 and 22, and provides the one or more media server flows 74 and 76 to the

WebRTC clients

32 and 34, respectively. As noted above, applying media services may include mixing the WebRTC interactive flows 18 and 22, switching the media server flows 74 and 76, inserting content into one or more of the WebRTC interactive flows 18 and 22, recording one or more of the WebRTC interactive flows 18 and 22, redirecting one or more of the WebRTC interactive flows 18 and 22, performing text-to-speech conversion on one or more of the WebRTC interactive flows 18 and 22, and/or performing speech recognition on one or more of the WebRTC interactive flows 18 and 22.

In some embodiments, the WebRTC functionality provider 60 may receive the media server command(s) 62 from the WebRTC application server 16 via the control API 54. The media server command(s) 62 may be routed through the media control application 65 executed by the scripting engine 50. In this manner, the WebRTC application server 16 may indicate media services to be applied to the WebRTC interactive flows 18 and/or 22, and thus may selectively control, monitor, and/or modify a content of the media server flows 74 and/or 76 provided to the

WebRTC clients

32 and 34. The WebRTC-enabled media server 12 may also generate the media server event(s) 64 in response to applying media services to the WebRTC interactive flows 18 and/or 22. As non-limiting examples, the WebRTC-enabled media server 12 may generate media server event(s) 64 to notify the WebRTC application server 16 that an announcement has completed, or that input of DTMF digits has been detected. The media server event(s) 64 may then be provided to the WebRTC application server 16 by the control API 54. In some embodiments, the media server event(s) 64 may be provided via the media control application 65 executed by the scripting engine 50.

FIG. 5 provides a block diagram representation of a processing system 104 in the exemplary form of an exemplary computer system 106 adapted to execute instructions to perform the functions described herein. In some embodiments, the processing system 104 may execute instructions to perform the functions of the WebRTC-enabled media server 12 of FIG. 1. In this regard, the processing system 104 may comprise the computer system 106, within which a set of instructions for causing the processing system 104 to perform any one or more of the methodologies discussed herein may be executed. The processing system 104 may be connected (as a non-limiting example, networked) to other machines in a local area network (LAN), an intranet, an extranet, or the Internet. The processing system 104 may operate in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. While only a single processing system 104 is illustrated, the terms “controller” and “server” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. The processing system 104 may be a server, a personal computer, a desktop computer, a laptop computer, a personal digital assistant (PDA), a computing pad, a mobile device, or any other device and may represent, as non-limiting examples, a server or a user's computer.

The exemplary computer system 106 includes a processing device or processor 108, a main memory 110 (as non-limiting examples, read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM), etc.), and a static memory 112 (as non-limiting examples, flash memory, static random access memory (SRAM), etc.), which may communicate with each other via a bus 114. Alternatively, the processing device 108 may be connected to the main memory 110 and/or the static memory 112 directly or via some other connectivity means.

The processing device 108 represents one or more processing devices such as a microprocessor, central processing unit (CPU), or the like. More particularly, the processing device 108 may be a complex instruction set computing (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 108 is configured to execute processing logic in instructions 116 and/or cached instructions 118 for performing the operations and steps discussed herein.

The computer system 106 may further include a communications interface in the form of a network interface device 120. It also may or may not include an input 122 to receive input and selections to be communicated to the computer system 106 when executing the

instructions

116, 118. It also may or may not include an output 124, including but not limited to display(s) 126. The display(s) 126 may be a video display unit (as non-limiting examples, a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device (as a non-limiting example, a keyboard), a cursor control device (as a non-limiting example, a mouse), and/or a touch screen device (as a non-limiting example, a tablet input device or screen).

The computer system 106 may or may not include a data storage device 128 that includes using drive(s) 130 to store the functions described herein in a computer-readable medium 132, on which is stored one or more sets of instructions 134 (e.g., software) embodying any one or more of the methodologies or functions described herein. The functions can include the methods and/or other functions of the processing system 104, a participant user device, and/or a licensing server, as non-limiting examples. The one or more sets of instructions 134 may also reside, completely or at least partially, within the main memory 110 and/or within the processing device 108 during execution thereof by the computer system 106. The main memory 110 and the processing device 108 also constitute machine-accessible storage media. The

instructions

116, 118, and/or 134 may further be transmitted or received over a network 136 via the network interface device 120. The network 136 may be an intra-network or an inter-network.

While the computer-readable medium 132 is shown in an exemplary embodiment to be a single medium, the term “machine-accessible storage medium” should be taken to include a single medium or multiple media (as non-limiting examples, a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions 134. The term “machine-accessible storage medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine, and that cause the machine to perform any one or more of the methodologies disclosed herein. The term “machine-accessible storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.

The embodiments disclosed herein may be embodied in hardware and in instructions that are stored in hardware, and may reside, as non-limiting examples, in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer readable medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). The ASIC may reside in a remote station. In the alternative, the processor and the storage medium may reside as discrete components in a remote station, base station, or server.

It is also noted that the operational steps described in any of the exemplary embodiments herein are described to provide examples and discussion. The operations described may be performed in numerous different sequences other than the illustrated sequences. Furthermore, operations described in a single operational step may actually be performed in a number of different steps. Additionally, one or more operational steps discussed in the exemplary embodiments may be combined. It is to be understood that the operational steps illustrated in the flow chart diagrams may be subject to numerous different modifications as will be readily apparent to one of skill in the art. Those of skill in the art would also understand that information and signals may be represented using any of a variety of different technologies and techniques. As non-limiting examples, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

What is claimed is:

1. A system for providing Web Real-Time Communications (WebRTC) media services, comprising:

at least one communications interface;

a processor; and

a computer readable medium coupled with the processor and comprising processor readable and executable instructions that program the processor to implement a WebRTC-enabled media server comprising a scripting engine, a WebRTC functionality provider, a control application program interface (API) providing an interface between the scripting engine and the WebRTC functionality provider, and a WebRTC client API, the WebRTC-enabled media server communicatively coupled to a WebRTC application server and a plurality of WebRTC clients via the at least one communications interface;

wherein the WebRTC-enabled media server:

receives, from the WebRTC application server, a stream establishment application;

establishes, via execution of the stream establishment application by the scripting engine and through the WebRTC client API, a plurality of WebRTC interactive flows associated with corresponding ones of the plurality of WebRTC clients through a WebRTC initiation dialogue between the stream establishment application of the Web-RTC-enabled media server and each of the plurality of WebRTC clients, wherein the WebRTC-enabled media server interacts through the WebRTC client API with the WebRTC clients as a WebRTC peer and provides media server functionality based on media server commands received from the WebRTC application server through the control API;

applies a media service to one or more of the plurality of WebRTC interactive flows to generate one or more media server flows; and

provides the one or more media server flows to one or more of the plurality of WebRTC clients.

2. The system of claim 1, wherein the WebRTC-enabled media server receives the stream establishment application in response to a Hyper Text Transfer Protocol (HTTP) request or a Web Sockets request, or combinations thereof.

3. The system of claim 1, wherein:

the control API receives a media server command from the WebRTC application server; and

the WebRTC functionality provider applies a media service indicated by the media server command to one or more of the plurality of WebRTC interactive flows.

4. The system of claim 3, wherein the control API receives the media server command via a Representational State Transfer (REST) API invocation or a JavaScript API invocation.

5. The system of claim 1, wherein:

the WebRTC functionality provider generates a media server event responsive to applying the media service to the one or more of the plurality of WebRTC interactive flows; and

the control API provides the media server event to the WebRTC application server.

6. The system of claim 5, wherein the control API provides the media server event via a REST API or a JavaScript API.

7. The system of claim 1, wherein:

the control API comprises a JavaScript API; and

the WebRTC-enabled media server further receives a media control application configured to access the functionality of the WebRTC functionality provider via the control API.

8. A method for providing Web Real-Time Communications (WebRTC) media services, comprising:

providing, by a WebRTC-enabled media server executing on a computing device, a scripting engine, a WebRTC functionality provider, a control application programming interface (API) providing an interface between the scripting engine and the WebRTC functionality provider, and a WebRTC client API;

receiving, by the WebRTC-enabled media server, a stream establishment application from a WebRTC application server;

establishing, via execution of the stream establishment application by the scripting engine and through the WebRTC client API, a plurality of WebRTC interactive flows associated with corresponding ones of a plurality of WebRTC clients through a WebRTC initiation dialogue between the stream establishment application of the Web-RTC-enabled media server and each of the plurality of WebRTC clients, wherein the WebRTC-enabled media server interacts through the WebRTC client API with the WebRTC clients as a WebRTC peer and provides media server functionality based on media server commands received from the WebRTC application server through the control API;

applying a media service to one or more of the plurality of WebRTC interactive flows to generate one or more media server flows; and

providing the one or more media server flows to one or more of the plurality of WebRTC clients.

9. The method of claim 8, wherein receiving the stream establishment application comprises receiving the stream establishment application in response to a Hyper Text Transfer Protocol (HTTP) request or a Web Sockets request, or combinations thereof.

10. The method of claim 8, further comprising:

receiving, via the control API, a media server command from the WebRTC application server; and

applying a media service indicated by the media server command to one or more of the plurality of WebRTC interactive flows.

11. The method of claim 10, wherein receiving the media server command comprises receiving the media server command via a Representational State Transfer (REST) API invocation or a JavaScript API invocation.

12. The method of claim 8, further comprising:

generating a media server event responsive to applying the media service to the one or more of the plurality of WebRTC interactive flows; and

providing, via the control API, the media server event to the WebRTC application server.

13. The method of claim 12, wherein providing the media server event comprises providing the media server event via a REST API or a JavaScript API.

14. The method of claim 8, wherein:

the control API comprises a JavaScript API; and

the method further comprises receiving a media control application configured to access the functionality of the WebRTC functionality provider via the control API.

15. A non-transitory computer-readable medium having stored thereon computer-executable instructions to cause a processor to implement a method for providing Web Real-Time Communications (WebRTC) media services, comprising:

providing, by a WebRTC-enabled media server, a scripting engine, a WebRTC functionality provider, a control application programming interface (API) providing an interface between the scripting engine and the WebRTC functionality provider, and a WebRTC client API;

16. The non-transitory computer-readable medium of claim 15 having stored thereon the computer-executable instructions to cause the processor to implement the method, wherein receiving the stream establishment application comprises receiving the stream establishment application in response to a Hyper Text Transfer Protocol (HTTP) request or a Web Sockets request, or combinations thereof.

17. The non-transitory computer-readable medium of claim 15 having stored thereon the computer-executable instructions to cause the processor to implement the method, further comprising:

18. The non-transitory computer-readable medium of claim 17 having stored thereon the computer-executable instructions to cause the processor to implement the method, wherein receiving the media server command comprises receiving the media server command via a Representational State Transfer (REST) API invocation or a JavaScript API invocation.

19. The non-transitory computer-readable medium of claim 15 having stored thereon the computer-executable instructions to cause the processor to implement the method, further comprising:

20. The non-transitory computer-readable medium of claim 19 having stored thereon the computer-executable instructions to cause the processor to implement the method, wherein providing the media server event comprises providing the media server event via a REST API or a JavaScript API.