Patent Grant
9749363
This application is related to U.S. patent application Ser. No. 13/863,662 filed on Apr. 16, 2013, entitled “Distributed Applications of Enterprise Policies to Web Real-Time Communications (WebRTC) Interactive Sessions, and Related Methods, Systems, and Computer-Readable Media,” which is hereby incorporated herein by reference in its entirety.
Field of the Disclosure
The technology of the disclosure relates generally to Web Real-Time Communications (WebRTC) interactive sessions.
Technical Background
Web Real-Time Communications (WebRTC) is 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 (2012 Digital Codex LLC), which is incorporated herein by reference in its entirety.
WebRTC provides built-in capabilities for establishing real-time video, audio, and/or data streams in both point-to-point interactive sessions, as well as 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 session (e.g., a real-time video, audio, and/or data exchange), two web clients may retrieve WebRTC-enabled web applications, such as HTML5/JavaScript web applications, from a web application server. Through the web applications, the two web clients then engage in a media negotiation to communicate and reach an agreement on parameters that define characteristics of the WebRTC interactive session. This media negotiation may take the form of a WebRTC “offer/answer” exchange. A WebRTC “offer/answer” exchange typically occurs via a secure network connection such as a Hypertext Transfer Protocol Secure (HTTPS) connection or a Secure WebSockets connection. In an offer/answer exchange, a first web client on a sender device sends an “offer” to a second web client on a recipient device. The offer includes a WebRTC session description object (also referred to as “token”) that specifies media types and capabilities that the first web client supports and prefers for use in the WebRTC interactive session. The second web client then responds with a WebRTC session description object “answer” that indicates which of the offered media types and capabilities are supported and acceptable by the second web client for the WebRTC interactive session. Once the WebRTC offer/answer exchange is concluded, the web clients may then establish a direct “peer connection” with one another, and may begin an exchange of media or data packets transporting real-time communications. The peer connection between the web 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 specific nature of a WebRTC offer/answer exchange may pose a challenge for enterprise networks that wish to apply enterprise-specific policies and/or media features to real-time communications sessions across enterprise network boundaries. For example, an enterprise network may require that enterprise policies, such as WebRTC session restriction policies, be applied, and/or may require that WebRTC sessions be recorded. While many current enterprise networks have an existing engine in place to support other communications protocols (e.g., the Session Initiation Protocol (SIP)), they may require implementation of a separate, parallel engine to support application of enterprise policies to WebRTC interactive sessions. However, implementation of such a parallel engine specifically for WebRTC interactive sessions may prove technically and/or financially burdensome.
Embodiments disclosed in the detailed description include application of enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions using an enterprise Session Initiation Protocol (SIP) engine, and related methods, systems, and computer-readable media. In this regard, in one embodiment, a method for applying enterprise policies to WebRTC interactive sessions using an enterprise SIP engine is disclosed. The method comprises receiving, by a session token converter of an enterprise device within an enterprise network, an incoming WebRTC session description token. The method further comprises generating, by the session token converter, an outgoing SIP request message. The outgoing SIP request message comprises the incoming WebRTC session description token; a return destination of the enterprise device; and an indicator that the outgoing SIP request message originated from an enterprise user. The method further comprises sending, by the session token converter, the outgoing SIP request message to an enterprise SIP engine and applying, by the enterprise SIP engine, one or more enterprise policies based on the outgoing SIP request message. The method further comprises, responsive to applying the one or more enterprise policies, sending an incoming SIP request message to the enterprise device. The method further comprises converting, by the session token converter, the incoming SIP request message into an outgoing WebRTC session description token, and sending the outgoing WebRTC session description token to a target device. In this manner, the session token converter of the enterprise device allows an enterprise network to leverage an existing SIP engine to apply enterprise-specific policies and features to a WebRTC interactive session, without the need for a separate WebRTC engine.
In another embodiment, a system for applying enterprise policies to WebRTC interactive sessions using an enterprise SIP engine is provided. The system comprises at least one communications interface and an enterprise device within an enterprise network associated with the at least one communications interface and comprising a session token converter. The session token converter is configured to receive an incoming WebRTC session description token. The session token converter is further configured to generate an outgoing SIP request message. The outgoing SIP request message comprises the incoming WebRTC session description token; a return destination of the enterprise device; and an indicator that the outgoing SIP request message originated from an enterprise user. The session token converter is further configured to send the outgoing SIP request message to an enterprise SIP engine. The enterprise SIP engine is configured to apply one or more enterprise policies based on the outgoing SIP request message. The enterprise SIP engine is further configured to, responsive to applying the one or more enterprise policies, send an incoming SIP request message to the enterprise device. The session token converter of the enterprise device is further configured to convert the incoming SIP request message into an outgoing WebRTC session description token and send the outgoing WebRTC session description token to a target device.
In another embodiment, a non-transitory computer-readable medium is provided. The non-transitory computer-readable medium has stored thereon computer-executable instructions to cause a processor to implement a method comprising receiving, by a session token converter of an enterprise device within an enterprise network, an incoming WebRTC session description token. The method implemented by the computer-executable instructions further comprises generating, by the session token converter, an outgoing SIP request message. The outgoing SIP request message comprises the incoming WebRTC session description token; a return destination of the enterprise device; and an indicator that the outgoing SIP request message originated from an enterprise user. The method implemented by the computer-executable instructions further comprises sending, by the session token converter, the outgoing SIP request message to an enterprise SIP engine. The method implemented by the computer-executable instructions further comprises applying, by the enterprise SIP engine, one or more enterprise policies based on the outgoing SIP request message. The method implemented by the computer-executable instructions further comprises, responsive to applying the one or more enterprise policies, sending an incoming SIP request message to the enterprise device. The method implemented by the computer-executable instructions further comprises converting, by the session token converter, the incoming SIP request message into an outgoing WebRTC session description token, and sending the outgoing WebRTC session description token to a target device.
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.
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.
Embodiments disclosed in the detailed description include application of enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions using an enterprise Session Initiation Protocol (SIP) engine, and related methods, systems, and computer-readable media. In this regard, in one embodiment, a method for applying enterprise policies to WebRTC interactive sessions using an enterprise SIP engine is disclosed. The method comprises receiving, by a session token converter of an enterprise device within an enterprise network, an incoming WebRTC session description token. The method further comprises generating, by the session token converter, an outgoing SIP request message. The outgoing SIP request message comprises the incoming WebRTC session description token; a return destination of the enterprise device; and an indicator that the outgoing SIP request message originated from an enterprise user. The method further comprises sending, by the session token converter, the outgoing SIP request message to an enterprise SIP engine and applying, by the enterprise SIP engine, one or more enterprise policies based on the outgoing SIP request message. The method further comprises, responsive to applying the one or more enterprise policies, sending an incoming SIP request message to the enterprise device. The method further comprises converting, by the session token converter, the incoming SIP request message into an outgoing WebRTC session description token, and sending the outgoing WebRTC session description token to a target device. In this manner, the session token converter of the enterprise device allows an enterprise network to leverage an existing SIP engine to apply enterprise-specific policies and features to a WebRTC interactive session, without the need for a separate WebRTC engine.
In this regard,
With continuing reference to
Additionally, in some embodiments, the media server 20 may be employed for manipulating and distributing media among WebRTC clients in a multi-party WebRTC session, or among WebRTC clients and non-WebRTC clients in a multi-party communications session. As a non-limiting example, if four (4) WebRTC clients take part in the same multi-party WebRTC session, each WebRTC client may connect to the media server 20, and the media server 20 may function to connect each WebRTC client to the remaining parties in the WebRTC session. The system 10 also includes a Traversal Using Relays around Network Address Translation (NAT) (TURN) server 24 to support communication paths 26 and 28. While
With continuing reference to
With continuing reference to
However, if application of the enterprise policies to the SIP request message does not result in a SIP error code, the enterprise SIP engine 16 may continue to process the SIP request message. As described in more detail below, the enterprise SIP engine 16 and the media server 20 are communicatively coupled, as indicated by bidirectional arrow 44. In this regard, if the requested interactive session involves the use of particular media features, the enterprise SIP engine 16 may send information from the SIP request message to the media server 20. The media server 20 allocates resources for the media features for the interactive session, and sends information, such as port and address details, back to the enterprise SIP engine 16. Finally, the enterprise SIP engine 16 sends the SIP request message, with enterprise policies included, to the session token converter 12.
With continuing reference to
In this regard,
Before discussing the details of the session token converter 12, the establishment of a WebRTC interactive session in the system 48 in
In this embodiment, the enterprise web client 18 comprises the scripting engine 22 and a WebRTC functionality provider 52. As previously described, the scripting engine 22 enables client-side applications written in a scripting language, such as JavaScript, to be executed within the enterprise web client 18. The scripting engine 22 also provides an application programming interface (API) to facilitate communications with other functionality providers within the enterprise web client 18 and/or the enterprise device 50, and/or with other web clients, devices, or web servers. The WebRTC functionality provider 52 implements the protocols, codecs, and APIs necessary to enable real-time interactive sessions via WebRTC. The scripting engine 22 and the WebRTC functionality provider 52 are communicatively coupled via a set of defined APIs, as indicated by bidirectional arrow 54.
External to the enterprise network 14 is the web application server 30, which serves a WebRTC-enabled web application (not shown) to requesting web clients. In some embodiments, the web application server 30 may be a single server, while in some applications the web application server 30 may comprise multiple servers that are communicatively coupled to each other. It is to be understood that the web application server 30 may reside in the enterprise network 14, or may reside within an enterprise network external to the enterprise network 14.
Also external to the enterprise network 14 is an external device 56 executing the external web client 34. The external device 56 may be any computing or communications device having network communications capabilities, such as a smartphone, a tablet computer, a dedicated web appliance, or a desktop computer, as non-limiting examples. The external web client 34 may be a web browser application, a dedicated communications application, or an interface-less application such as a daemon or service application, as non-limiting examples. In this embodiment, the external web client 34 comprises the scripting engine 36 and a WebRTC functionality provider 58, the functionality of which corresponds to the functionality of the scripting engine 22 and the WebRTC functionality provider 52 of the enterprise web client 18, respectively. The scripting engine 36 and the WebRTC functionality provider 58 are communicatively coupled via a set of defined APIs, as indicated by bidirectional arrow 60. It is to be understood that the external web client 34 may reside within an enterprise network external to the enterprise network 14. It is to be further understood that in some embodiments the enterprise device 50 and the external device 56 may both be located within a same public or private network, or may be located within separate, communicatively coupled public or private networks.
The enterprise web client 18 and the external web client 34 then establish secure web connections 62 and 64, respectively, with the web application server 30, and engage in a WebRTC offer/answer exchange. This is accomplished through an exchange of WebRTC session description tokens as indicated by arrows 66 and 68. In some embodiments, the WebRTC session description tokens may comprise Session Description Protocol (SDP) objects exchanged by the enterprise web client 18 and the external web client 34. The exchanged WebRTC session description tokens 66 and 68 are used to determine the media types and capabilities for the desired WebRTC interactive session.
As previously described, the enterprise network 14 in
Once the WebRTC offer/answer exchange is concluded, a WebRTC interactive flow 76 may be established via a secure peer connection 78 between the enterprise web client 18 and the external web client 34. Accordingly, in
It is to be understood that some embodiments may utilize topographies other than the WebRTC “triangle” topography illustrated in
With continuing reference to
To illustrate exemplary communications flows during the establishment of a WebRTC interactive session including the session token converter 12 in
In
With continuing reference to
In some embodiments, applying the enterprise policies may include optionally enabling media features to be used in conjunction with the WebRTC interactive session, such as, for example, recording audio or video. If such media features are to be enabled for the WebRTC interactive session, the enterprise SIP engine 16 sends the incoming WebRTC session description token 82 to the media server 20 (dashed arrow 94). The media server 20 uses the information in the outgoing WebRTC session description token 82 to generate a media WebRTC session description token 96 (box 98). As a non-limiting example, the media WebRTC session description token 96 provides important information, such as details instructing the external device 56 to connect directly to the media server 20 rather than to the enterprise device 50. The media server 20 then sends the media WebRTC session description token 96 to the enterprise SIP engine 16 (dashed arrow 100). The enterprise SIP engine 16 may include the media WebRTC session description token 96 in an incoming SIP request message 102 to be sent to the session token converter 12 (box 104). Additionally, in some embodiments, the media server 20 may be employed for manipulating and distributing media among WebRTC clients in a multi-party WebRTC session. As a non-limiting example, if four WebRTC clients take part in the same multi-party WebRTC session, each WebRTC client may connect to the media server 20, and the media server 20 may function to connect each WebRTC client to the remaining parties in the WebRTC session.
With continuing reference to
To continue illustrating exemplary communications flows during the establishment of a WebRTC interactive session including the session token converter 12 in
With continuing reference to
To describe exemplary operations of the session token converter 12 and the application of enterprise policies to WebRTC interactive sessions using the enterprise SIP engine 16 of
In this manner,
Referring to
The session token converter 12 next generates an outgoing SIP request message 86 (block 150). The outgoing SIP request message 86 may include, as non-limiting examples, the incoming WebRTC session description token 82, a return destination of the enterprise device 50, and/or an indicator that the outgoing SIP request message 86 originated from an enterprise user. The session token converter 12 then sends the outgoing SIP request message 86 to the enterprise SIP engine 16 (block 152). After receiving the outgoing SIP request message 86, the enterprise SIP engine 16 applies one or more enterprise policies based on the outgoing SIP request message 86 (block 154). As previously described, such policies may include origination and/or termination polices, and may be applied by invoking particular applications and/or application sequences within the enterprise SIP engine 16, as non-limiting examples.
Referring to
Referring now to
Referring to
Referring to
Referring to
The exemplary computer system 200 includes a processing device or processor 202, a main memory 204 (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 206 (as non-limiting examples, flash memory, static random access memory (SRAM), etc.), which may communicate with each other via a bus 208. Alternatively, the processing device 202 may be connected to the main memory 204 and/or the static memory 206 directly or via some other connectivity means.
The processing device 202 represents one or more processing devices such as a microprocessor, central processing unit (CPU), or the like. More particularly, the processing device 202 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 202 is configured to execute processing logic in instructions 210 and/or cached instructions 212 for performing the operations and steps discussed herein.
The computer system 200 may further include a communications interface in the form of a network interface device 214. It also may or may not include an input 216 to receive input and selections to be communicated to the computer system 200 when executing instructions. It also may or may not include an output 218, including but not limited to display(s) 220, 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 200 may or may not include a data storage device 222 that includes using drive(s) 224 to store functions herein described in a computer-readable medium 226 on which is stored one or more sets of instructions 228 (e.g., software) embodying any one or more of the methodologies or functions described herein. The one or more instructions 228 may also reside, completely or at least partially, within the main memory 204 and/or within the processing device 202 during execution thereof by the computer system 200, the main memory 204, and the processing device 202 also constituting machine-accessible storage media. The instructions 210, 212, and/or 228 may further be transmitted or received over a network 230 via the network interface device 214. The network 230 can be an intra-network or an inter-network.
While the computer-readable medium 226 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 228. 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 of the embodiments 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.
Application of enterprise policies to WebRTC interactive sessions using an enterprise SIP engine, and related methods, systems, and computer-readable media according to embodiments disclosed herein may be provided in or integrated into any processor-based device. Examples, without limitation, include a set top box, an entertainment unit, a navigation device, a communications device, a fixed location data unit, a mobile location data unit, a mobile phone, a cellular phone, an internet phone, a computer, a portable computer, a desktop computer, a personal digital assistant (PDA), a monitor, a computer monitor, a television, a tuner, a radio, a satellite radio, a music player, a digital music player, a portable music player, a digital video player, a video player, a digital video disc (DVD) player, and a portable digital video player.
Those of skill in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithms described in connection with the embodiments disclosed herein may be implemented as electronic hardware, instructions stored in memory or in another computer-readable medium and executed by a processor or other processing device, or combinations of both. Memory disclosed herein may be any type and size of memory and may be configured to store any type of information desired. To clearly illustrate this interchangeability, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. How such functionality is implemented depends upon the particular application, design choices, and/or design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a processor, a digital signal processor (DSP), an Application Specific Integrated Circuit (ASIC), an field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, as non-limiting examples, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6714967 | Horvitz | Mar 2004 | B1 |
| 7107316 | Brown et al. | Sep 2006 | B2 |
| 7145898 | Elliott | Dec 2006 | B1 |
| 7266591 | Johnston | Sep 2007 | B1 |
| 7379993 | Valdes et al. | May 2008 | B2 |
| 7636348 | Bettis et al. | Dec 2009 | B2 |
| 7730309 | Zimmermann | Jun 2010 | B2 |
| 8015484 | Backer | Sep 2011 | B2 |
| 8250635 | Chari et al. | Aug 2012 | B2 |
| 8300632 | Davis et al. | Oct 2012 | B2 |
| 8467308 | Johnston | Jun 2013 | B2 |
| 8494507 | Tedesco et al. | Jul 2013 | B1 |
| 8601144 | Ryner | Dec 2013 | B1 |
| 8605711 | Sinnreich et al. | Dec 2013 | B1 |
| 8606950 | Glatron et al. | Dec 2013 | B2 |
| 8693392 | Cooper et al. | Apr 2014 | B2 |
| 8695077 | Gerhard | Apr 2014 | B1 |
| 8737596 | Kelley et al. | May 2014 | B2 |
| 8744147 | Torti | Jun 2014 | B2 |
| 8832271 | McCarty | Sep 2014 | B2 |
| 8856236 | Moore et al. | Oct 2014 | B2 |
| 8861692 | Phelps | Oct 2014 | B1 |
| 8867731 | Lum et al. | Oct 2014 | B2 |
| 20020161685 | Dwinnell | Oct 2002 | A1 |
| 20030112766 | Riedel et al. | Jun 2003 | A1 |
| 20030120599 | Agboatwalla et al. | Jun 2003 | A1 |
| 20030131245 | Linderman | Jul 2003 | A1 |
| 20030188193 | Venkataramappa | Oct 2003 | A1 |
| 20040019494 | Ridgeway et al. | Jan 2004 | A1 |
| 20040081173 | Feather | Apr 2004 | A1 |
| 20040093515 | Reeves, Jr. | May 2004 | A1 |
| 20040167984 | Herrmann | Aug 2004 | A1 |
| 20040216173 | Horoszowski et al. | Oct 2004 | A1 |
| 20050084082 | Horvitz et al. | Apr 2005 | A1 |
| 20050177380 | Pritchard et al. | Aug 2005 | A1 |
| 20060104526 | Gringeler et al. | May 2006 | A1 |
| 20060155814 | Bennett et al. | Jul 2006 | A1 |
| 20060159063 | Kumar | Jul 2006 | A1 |
| 20060200855 | Willis | Sep 2006 | A1 |
| 20060230438 | Shappir et al. | Oct 2006 | A1 |
| 20070083929 | Sprosts et al. | Apr 2007 | A1 |
| 20070143408 | Daigle | Jun 2007 | A1 |
| 20070255662 | Tumminaro | Nov 2007 | A1 |
| 20070283423 | Bradley et al. | Dec 2007 | A1 |
| 20080046414 | Haub et al. | Feb 2008 | A1 |
| 20080046457 | Haub et al. | Feb 2008 | A1 |
| 20080046838 | Haub et al. | Feb 2008 | A1 |
| 20080127137 | Becker et al. | May 2008 | A1 |
| 20080162642 | Bachiri et al. | Jul 2008 | A1 |
| 20080192646 | Song et al. | Aug 2008 | A1 |
| 20080270541 | Keener et al. | Oct 2008 | A1 |
| 20090070477 | Baum et al. | Mar 2009 | A1 |
| 20090094684 | Chinnusamy et al. | Apr 2009 | A1 |
| 20090300060 | Beringer et al. | Dec 2009 | A1 |
| 20100011282 | Dollard et al. | Jan 2010 | A1 |
| 20100023519 | Kailash et al. | Jan 2010 | A1 |
| 20100024019 | Backlund | Jan 2010 | A1 |
| 20100037324 | Grant et al. | Feb 2010 | A1 |
| 20100118700 | Blum et al. | May 2010 | A1 |
| 20100246571 | Geppert et al. | Sep 2010 | A1 |
| 20110102930 | Johnston et al. | May 2011 | A1 |
| 20110206013 | Aramoto et al. | Aug 2011 | A1 |
| 20110238862 | Chaturvedi et al. | Sep 2011 | A1 |
| 20120001932 | Burnett et al. | Jan 2012 | A1 |
| 20120079031 | Matthews et al. | Mar 2012 | A1 |
| 20120137231 | Maxfield et al. | May 2012 | A1 |
| 20120158862 | Mosko et al. | Jun 2012 | A1 |
| 20120192086 | Ghods et al. | Jul 2012 | A1 |
| 20130002799 | Mock | Jan 2013 | A1 |
| 20130078972 | Levien et al. | Mar 2013 | A1 |
| 20130091286 | Spencer | Apr 2013 | A1 |
| 20130138829 | Bulava | May 2013 | A1 |
| 20130321340 | Seo et al. | Dec 2013 | A1 |
| 20130325934 | Fausak et al. | Dec 2013 | A1 |
| 20130346329 | Alib-Bulatao et al. | Dec 2013 | A1 |
| 20140013202 | Schlumberger | Jan 2014 | A1 |
| 20140043994 | Bansal et al. | Feb 2014 | A1 |
| 20140095633 | Yoakum | Apr 2014 | A1 |
| 20140095724 | Yoakum et al. | Apr 2014 | A1 |
| 20140095731 | Carey et al. | Apr 2014 | A1 |
| 20140108594 | Siegel et al. | Apr 2014 | A1 |
| 20140126708 | Sayko | May 2014 | A1 |
| 20140126714 | Sayko | May 2014 | A1 |
| 20140126715 | Lum | May 2014 | A1 |
| 20140143823 | Manchester et al. | May 2014 | A1 |
| 20140149512 | Leitch | May 2014 | A1 |
| 20140161237 | Tolksdorf | Jun 2014 | A1 |
| 20140201820 | Li et al. | Jul 2014 | A1 |
| 20140219167 | Santhanam et al. | Aug 2014 | A1 |
| 20140222894 | Gangadharan | Aug 2014 | A1 |
| 20140222930 | Gangadharan | Aug 2014 | A1 |
| 20140223452 | Santhanam et al. | Aug 2014 | A1 |
| 20140237057 | Khodorenko | Aug 2014 | A1 |
| 20140241215 | Massover et al. | Aug 2014 | A1 |
| 20140244235 | Michaelis | Aug 2014 | A1 |
| 20140245143 | Saint-Marc | Aug 2014 | A1 |
| 20140258822 | Li et al. | Sep 2014 | A1 |
| 20140269326 | Westin et al. | Sep 2014 | A1 |
| 20140270104 | O'Connor | Sep 2014 | A1 |
| 20140280734 | Chaturvedi et al. | Sep 2014 | A1 |
| 20140282054 | Yoakum | Sep 2014 | A1 |
| 20140282135 | Segre | Sep 2014 | A1 |
| 20140282399 | Gorelik et al. | Sep 2014 | A1 |
| 20140282765 | Casey et al. | Sep 2014 | A1 |
| 20140282903 | Singh et al. | Sep 2014 | A1 |
| 20140324979 | Gao et al. | Oct 2014 | A1 |
| 20140325078 | Shan | Oct 2014 | A1 |
| 20140344169 | Phelps et al. | Nov 2014 | A1 |
| 20140348044 | Narayanan | Nov 2014 | A1 |
| 20140365676 | Yoakum | Dec 2014 | A1 |
| 20140379931 | Gaviria | Dec 2014 | A1 |
| 20150002614 | Zino | Jan 2015 | A1 |
| 20150002619 | Johnston et al. | Jan 2015 | A1 |
| 20150006610 | Johnston et al. | Jan 2015 | A1 |
| 20150006611 | Johnston et al. | Jan 2015 | A1 |
| 20150026473 | Johnston et al. | Jan 2015 | A1 |
| 20150036690 | Pastro | Feb 2015 | A1 |
| 20150039687 | Waxman et al. | Feb 2015 | A1 |
| 20150039760 | Yoakum | Feb 2015 | A1 |
| 20150052067 | Thiyagarajan et al. | Feb 2015 | A1 |
| 20150180825 | Ren | Jun 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 1615386 | Jan 2006 | EP |
| 2529316 | Dec 2012 | EP |
| 2295747 | Jun 1996 | GB |
| 2468758 | Sep 2010 | GB |
| 2468759 | Sep 2010 | GB |
| 2517833 | Mar 2015 | GB |
| 2002207683 | Jul 2002 | JP |
| 2002374318 | Dec 2002 | JP |
| 2005346556 | Dec 2005 | JP |
| 2006050407 | Feb 2006 | JP |
| 2011504665 | Feb 2011 | JP |
| 2014060008 | Apr 2014 | WO |
| 2014123738 | Aug 2014 | WO |
| 2014190094 | Nov 2014 | WO |
| 2015032277 | Mar 2015 | WO |
| Entry |
|---|
| Andreasen et al., “Session Description Protocol (SDP): Security Descriptions for Media Streams,” Network Working Group, Request for Comments: 4568, Standards Track, The Internet Society, Jul. 2006, 40 pages. |
| Baugher et al., “The Secure Real-time Transport Protocol (SRTP),” Network Working Group, Request for Comments: 3711, Standards Track, The Internet Society, Mar. 2004, 51 pages. |
| Johnston, Alan et al., “Taking on WebRTC in an Enterprise,” IEEE Communications Magazine, Apr. 2013, pp. 48-54, vol. 51, Issue 4. |
| Johnston et al., “WebRTC: APIs and RTCWEB Protocols of the HTML5 Real-Time Web,” (Book), Second Edition, Smashwords Edition, Digital Codex LLC, Jun. 2013, 254 pages. |
| Mahy et al., “Traversal Using Relays around NAT (TURN) : Relay Extensions to Session Traversal Utilities for NAT (STUN),” Internet Engineering Task Force, Request for Comments: 5766, Standards Track, IETF Trust, Apr. 2010, 61 pages. |
| McGrew et al., “Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-Time Transport Protocol (SRTP),” Internet Engineering Task Force, Request for Comments: 5764, Standards Track, IETF Trust, May 2010, 24 pages. |
| Singh, Kundan et al., “Building Communicating Web Applications Leveraging Endpoints and Cloud Resource Service,” Presented at the Sixth International Conference on Cloud Computing, Jun. 28, 2013, Santa Clara, California, IEEE Computer Society, pp. 486-493. |
| Singh, Kundan et al., “Private Overlay of Enterprise Social Data and Interactions in the Public Web Context,” presented at the 9th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing (Collaboratecom), Oct. 20-23, 2013, Austin, Texas, IEEE, 10 pages. |
| Zimmermann et al., “ZRTP: Media Path Key Agreement for Unicast Secure RTP,” Internet Engineering Task Force, Request for Comments: 6189, Informational, IETF Trust, Apr. 2011, 102 pages. |
| Search Report for British patent application GB1317121.0 mailed Mar. 14, 2014, 3 pages. |
| Search Report for British patent application GB1317122.8 mailed Mar. 11, 2014, 3 pages. |
| Berners-Lee, Tim, “Socially Aware Cloud Storage,” Notes on web design, Aug. 17, 2009, http://www.w3.org/DesignIssues/CloudStorage.html, 9 pages. |
| Chandra, Ramesh et al., “Separating Web Applications from User Data Storage with BStore,” presented at the USENIX Conference on Web Application Development, Jun. 2010, Boston, Massachusettes, 13 pages. |
| Davids, Carol et al., “SIP APIs for Voice and Video Communications on the Web,” presented at the International Conference on Principles, Systems and Applications of IP Telecommunications (IPTcomm), Aug. 2011, Chicago, Illinois, 7 pages. |
| Geambasu, Roxana et al., “Organizing and Sharing Distributed Personal Web-Service Data,” presented at the International World Wide Web Conference, Apr. 21-25, 2008, Beijing, China, International World Wide Web Conference Committee, pp. 755-764. |
| Hsu, F. et al., “Secure File System Services for Web 2.0 Applications,” presented at the ACM Cloud Computing Security Workshop, Nov. 13, 2009, Chicago, Illinois, Association for Computing Machinery, 7 pages. |
| Joshi, R., “Data-Oriented Architecture: A Loosley Coupled Real-Time SOA,” Whitepaper, Aug. 2007, Real-Time Innovations, Inc., http://rtcgroup.com/whitepapers/files/RTI—DataOrientedArchitecture—WhitePaper.pdf, 54 pages. |
| Vahdat, Amin et al., “WebFS: A Global Cache Coherent File System,” UC Berkeley, Dec. 1996, retrieved Sep. 16, 2014 from https://www.cs.duke.edu/˜vahdat/webfs/webfs.html, 12 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/037,440, mailed Sep. 12, 2014, 15 pages. |
| Notice of Allowance for U.S. Appl. No. 13/931,968, mailed Mar. 23, 2015, 7 pages. |
| Final Office Action for U.S. Appl. No. 13/835,913, mailed Mar. 26, 2015, 17 pages. |
| Final Office Action for U.S. Appl. No. 14/037,440, mailed Feb. 11, 2015, 19 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/068,839, mailed Feb. 20, 2015, 15 pages. |
| Barth, A. “The Web Origin Concept,” Internet Engineering Task Force (IETF), Request for Comments 6454 (RFC 6454), Dec. 2011, 19 pages, http://www.ietf.org/rfc/rfc6454.txt. |
| Fischl, J. et al., “Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS),” Internet Engineering Task Force (IETF), Request for Comments (RFC) 5763, May 2010, 26 pages. |
| Jesup, R. et al., “DTLS Encapsulation of SCTP Packets for RTCWEB,” IETF: Network Working Group, Internet Draft, Feb. 16, 2013, 6 pages. |
| Johnston, A. et al., “An Origin Attribute for the STUN Protocol,” Internet Engineering Task Force (IETF), Internet-Draft, Jul. 20, 2014, 14 pages, https://tools.ietf.org/html/draft-ietf-tram-stun-origin-00. |
| Rescorla, E., “Security Considerations for RTC-Web,” IETF RTCWEB, Internet Draft, Jan. 22, 2013, 16 pages. |
| Rescorla, E., “WebRTC Security Architecture,” IETF RTCWEB, Internet Draft, Jul. 14, 2013, 30 pages. |
| Corrected Notice of Allowability for U.S. Appl. No. 13/931,968, mailed Apr. 24, 2015, 4 pages. |
| Advisory Action for U.S. Appl. No. 14/037,440, mailed May 20, 2015, 3 pages. |
| Search Report for British Patent Application GB1419338.7, mailed Apr. 27, 2015, 4 pages. |
| Search Report for British Patent Application GB1419334.6, mailed Apr. 28, 2015, 6 pages. |
| Notice of Allowance for U.S. Appl. No. 13/944,368, mailed Apr. 1, 2015, 8 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/931,967, mailed May 5, 2015, 10 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/931,970, mailed May 7, 2015, 9 pages. |
| Bergkvist, Adam et al., “WebRTC 1.0: Real-time Communication Between Browsers,” W3C Working Draft, Feb. 9, 2012, http://www.w3.org/TR/2012/WD-webrtc-20120209/, 42 pages. |
| Notice of Reason for Refusal for Japanese Patent Application 2013-201228, dispatched Jun. 11, 2015, 8 pages. |
| Advisory Action for U.S. Appl. No. 13/835,913, mailed Jun. 10, 2015, 3 pages. |
| Final Office Action for U.S. Appl. No. 13/803,292, mailed Jun. 12, 2015, 17 pages. |
| Final Office Action and Examiner Initiated Interview Summary for U.S. Appl. No. 14/050,891, mailed Jun. 29, 2015, 11 pages. |
| Final Office Action for U.S. Appl. No. 13/955,023, mailed Jul. 20, 2015, 17 pages. |
| Corrected Notice of Allowability for U.S. Appl. No. 13/944,368, mailed Jul. 23, 2015, 4 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/141,798, mailed Jul. 17, 2015, 13 pages. |
| Extended European Search Report for European Patent Application 15161452.6, mailed Jun. 23, 2015, 5 pages. |
| Loreto, Salvatore et al., “Real-Time Communications in the Web: Issues, Achievements, and Ongoing Standardization Efforts,” IEEE Internet Computing, vol. 16, Issue 5, IEEE Computer Society, Oct. 2, 2012, pp. 68-73. |
| Search Report for British patent application GB1411584.4 mailed Dec. 30, 2014, 4 pages. |
| Search Report for British patent application GB1411580.2 mailed Dec. 30, 2014, 4 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/931,968, mailed Dec. 8, 2014, 6 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/835,913, mailed Nov. 20, 2014, 15 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/803,292, mailed Jan. 27, 2015, 13 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/050,891, mailed Jan. 29, 2015, 9 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/955,023, mailed Feb. 2, 2015, 12 pages. |
| Author Unknown, “WebRTC,” WebRTC.org, Date Accessed: Jan. 26, 2016, 4 pages, http://webrtc.org/. |
| Notice of Allowance for U.S. Appl. No. 13/863,662, mailed Feb. 1, 2016, 17 pages. |
| Advisory Action and Examiner-Initiated Interview Summary for U.S. Appl. No. 14/068,839, mailed Feb. 12, 2016, 4 pages. |
| Final Office Action for U.S. Appl. No. 14/141,798, mailed Dec. 24, 2015, 10 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/174,371, mailed Feb. 18, 2016, 18 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/931,970, mailed Feb. 23, 2016, 11 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/955,711, mailed Nov. 9, 2015, 10 pages. |
| Notice of Allowance for U.S. Appl. No. 14/050,891, mailed Nov. 10, 2015, 10 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/955,023, mailed Dec. 9, 2015, 13 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/037,440, mailed Oct. 22, 2015, 15 pages. |
| Advisory Action for U.S. Appl. No. 13/931,967, mailed Nov. 3, 2015, 3 pages. |
| Advisory Action for U.S. Appl. No. 13/931,970, mailed Nov. 5, 2015, 3 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/068,943, mailed Dec. 2, 2015, 16 pages. |
| Search Report for British Patent Application No. GB1423089.0, mailed Jul. 6, 2015, 4 pages. |
| Rodriguez, Pedro et al., “Advanced Videoconferencing Services Based on WebRTC,” IADIS International Conferences Web Based Communities and Social Media 2012 and Collaborative Technologies 2012, Jul. 17-23, 2012, pp. 180-184, http://www.iadisportal.org/wbc-2012-proceedings. |
| Examination Report for British Patent Application GB1411584.4, mailed Aug. 21, 2015, 1 page. |
| Examination Report for British Patent Application GB1411580.2, mailed Aug. 21, 2015, 1 pages. |
| Notification of Reasons for Refusal for Japanese Patent Application 2013-201221, mailed Aug. 25, 2015, 8 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/835,913, mailed Sep. 3, 2015, 19 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/912,520, mailed Sep. 9, 2015, 21 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/863,662, mailed Sep. 25, 2015, 23 pages. |
| Advisory Action for U.S. Appl. No. 13/803,292, mailed Aug. 21, 2015, 3 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/803,292, mailed Oct. 9, 2015, 13 pages. |
| Advisory Action and Examiner-Initiated Interview Summary for U.S. Appl. No. 14/050,891, mailed Sep. 29, 2015, 4 pages. |
| Final Office Action for U.S. Appl. No. 14/068,839, mailed Sep. 9, 2015, 17 pages. |
| Final Office Action for U.S. Appl. No. 13/931,967, mailed Aug. 20, 2015, 12 pages. |
| Final Office Action for U.S. Appl. No. 13/931,970, mailed Aug. 27, 2015, 10 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150304359 A1 | Oct 2015 | US |
