Field of the Disclosure
The technology of the disclosure relates generally to archiving real-time interactive flows.
Technical Background
Various network protocols, such as Web Real-Time Communications (WebRTC) protocol, Session Initiation Protocol (SIP), and H.323, provide capabilities for establishing real-time interactive flows via the Internet and/or a private network, such as an enterprise network. Such real-time interactive flows may include real-time video, audio, and/or data streams exchanged in point-to-point interactive sessions. Endpoints for the real-time interactive flows may be, for example, two or more web browsers and/or other purpose-built applications or communications clients. In this manner, real-time interactive flows facilitate communications and collaboration among users who may be remote from one another.
The use of real-time interactive flows in some environments may require recording of the real-time interactive flows. For instance, enterprise policies may dictate that real-time interactive flows transmitted across an enterprise network be recorded for security, legal, and/or archival purposes. However, recording the real-time interactive flows may be problematic in such environments. Due to the topology of a typical real-time interactive flow session, use of a central media element on the network between the endpoints to record the real-time interactive flow may not be practicable or desirable. As non-limiting examples, the real-time interactive flow may pass directly from one endpoint to the other, thus bypassing the central media element, or the real-time interactive flow may be encrypted and therefore inaccessible to the central media element. Moreover, duplicating, or “forking,” the real-time interactive flow at one endpoint may put an undue burden on network bandwidth for the duplicated real-time interactive flow, or may degrade the quality of the real-time interactive flow.
Embodiments disclosed in the detailed description provide bandwidth-efficient archiving of real-time interactive flows. Related methods, systems, and computer-readable media are also disclosed. In this regard, in one embodiment, a method for archiving a real-time interactive flow is provided. The method comprises receiving, by a computing device (e.g., a purpose-built communications device), a real-time interactive flow. As used herein, a “real-time interactive flow” refers to an interactive media flow and/or an interactive data flow between or among two or more endpoints, comprising a real-time audio stream and/or a real-time video stream or other real-time media or data stream. The method further comprises forking the real-time interactive flow at the computing device as an archival stream. The method also comprises streaming the archival stream from the computing device to an archival repository at an adjustable streaming rate. The method additionally comprises measuring a change in a performance characteristic of the real-time interactive flow. The method further comprises modifying the adjustable streaming rate based on the change in the performance characteristic of the real-time interactive flow. In this manner, a real-time interactive flow may be duplicated in a bandwidth-sensitive fashion while capturing a high-quality archive of the real-time interactive flow.
In another embodiment, a system for archiving a real-time interactive flow is provided. The system comprises at least one communications interface, and an archival repository associated with the at least one communications interface. The system further comprises a computing device associated with the at least one communications interface and comprising an interactive flow functionality provider and an archival streaming agent. The interactive flow functionality provider is configured to receive a real-time interactive flow, and fork the real-time interactive flow to the archival streaming agent as an archival stream. The archival streaming agent is configured to stream the archival stream to the archival repository at an adjustable streaming rate. The archival streaming agent is further configured to measure a change in a performance characteristic of the real-time interactive flow. The archival streaming agent is also configured to modify the adjustable streaming rate based on the change in the performance characteristic of the real-time interactive flow.
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 computing device, a real-time interactive flow. The method implemented by the computer-executable instructions further comprises forking the real-time interactive flow at the computing device as an archival stream. The method implemented by the computer-executable instructions also comprises streaming the archival stream from the computing device to an archival repository at an adjustable streaming rate. The method implemented by the computer-executable instructions additionally comprises measuring a change in a performance characteristic of the real-time interactive flow. The method implemented by the computer-executable instructions further comprises modifying the adjustable streaming rate based on the change in the performance characteristic of the real-time interactive flow.
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 provide bandwidth-efficient archiving of real-time interactive flows. Related methods, systems, and computer-readable media are also disclosed. In this regard, in one embodiment, a method for archiving a real-time interactive flow is provided. The method comprises receiving, by a computing device, a real-time interactive flow. The method further comprises forking the real-time interactive flow at the computing device as an archival stream. The method also comprises streaming the archival stream from the computing device to an archival repository at an adjustable streaming rate. The method additionally comprises measuring a change in a performance characteristic of the real-time interactive flow. The method further comprises modifying the adjustable streaming rate based on the change in the performance characteristic of the real-time interactive flow. In this manner, a real-time interactive flow may be duplicated in a bandwidth-sensitive fashion while capturing a high-quality archive of the real-time interactive flow.
In this regard,
Referring now to
For purposes of illustration, the real-time interactive flow 14 in
The computing devices 18 and 20 of
The archival streaming agent 12 of
As seen in
As the archival stream 30 is being streamed to the archival repository 16, the archival streaming agent 12 measures changes in performance characteristics of the real-time interactive flow 14. As non-limiting examples, the archival streaming agent 12 may measure performance characteristics such as available network bandwidth, data throughput, latency, jitter, and/or error rates for the real-time interactive flow 14. In some embodiments, the archival streaming agent 12 may measure changes in performance characteristics of the real-time interactive flow 14 based on real-time interactive flow performance data (not shown) received from the computing device 18. Some embodiments may provide that the archival streaming agent 12 measures changes in performance characteristics based on performance information communicated to the interactive flow client 22 in the form of protocol messages such as RTP Control Protocol (RTCP) messages.
In some embodiments, the archival streaming agent 12 may measure changes in performance characteristics of the real-time interactive flow 14 by analyzing the network packets constituting the real-time interactive flow 14. If a change in a performance characteristic of the real-time interactive flow 14 is detected, the archival streaming agent 12 may modify the adjustable streaming rate at which the archival stream 30 is being streamed to the archival repository 16 based on the change. For example, if the archival streaming agent 12 measures a degradation in data throughput of the real-time interactive flow 14, the archival streaming agent 12 may decrease the streaming rate of the archival stream 30 to minimize any impact that the archival stream 30 may have on the real-time interactive flow 14.
Modifying the adjustable streaming rate of the archival stream 30 by the archival streaming agent 12 to minimize any impact on the real-time interactive flow 14 may result in the archival stream 30 being streamed to the archival repository 16 at a rate that is less than real-time. Accordingly, some embodiments of the archival streaming agent 12 may provide buffering of the archival stream 30 prior to and/or concurrently with streaming the archival stream 30 to the archival repository 16. In this manner, the archival streaming agent 12 may ensure that a complete archive of the real-time interactive flow 14 is recorded, while remaining appropriately sensitive to network conditions.
The archival streaming agent 12 may also measure changes in network utilization by the computing device 18, and modify the adjustable streaming rate accordingly based on any such changes. In some embodiments, the archival streaming agent 12 may measure changes in network utilization based on network utilization data provided by the computing device 18. For instance, the computing device 18 may provide the archival streaming agent 12 with data relating to current utilization of a download and/or upload capacity of the computing device 18.
While exchanging video, audio, and/or data of the real-time interactive flow 14, users may also share other types of data (e.g., documents, emails, or images) in conjunction with the real-time interactive flow 14. Because streaming of the archival stream 30 may not occur in real-time, it may be desirable to associate the data shared during the real-time interactive flow 14 with specific points in time in the archival stream 30. Accordingly, the archival streaming agent 12 may provide an archival timeline stream 32 that is associated with the archival stream 30, and that is streamed concurrently with the archival stream 30 to the archival repository 16. In some embodiments, the archival timeline stream 32 may be incorporated into the archival stream 30. In this manner, the archival timeline stream 32 may provide a link between data shared during the real-time interactive flow 14 and a corresponding point in time in the archival stream 30.
To illustrate bandwidth-sensitive archiving of an interactive flow passing across an enterprise network,
The computing devices 42 and 46 of
In the example of
As noted above, the interactive communications system 34 includes the enterprise network 44 providing networked computing and communications resources to users within an enterprise. As used herein, an “enterprise” refers to any organization for the purpose of a business venture or other organized activity, private or public. The enterprise network 44 includes an enterprise “demilitarized zone” (DMZ) 58 to secure the enterprise network 44 while permitting both enterprise users and external users access to enterprise resources (not shown) within the enterprise DMZ 58. The enterprise DMZ 58 may include a DMZ policy enforcement point 60. The DMZ policy enforcement point 60 filters or alters network traffic passing through the enterprise DMZ 58 in accordance with enterprise policies. It is to be understood that the enterprise DMZ 58 may include additional elements not illustrated in
In the example of
In
In this regard, the archival streaming agent 36 of
The interactive flow functionality provider 52 receives the real-time interactive flow 38, and forks the contents of the real-time interactive flow 38 to the archival streaming agent 36 as an archival stream 62. The archival stream 62, which is a duplicate of the contents of the real-time interactive flow 38, is then streamed over the enterprise network 44 by the archival streaming agent 36 to the archival repository 40 at an adjustable streaming rate. As discussed above with respect to
As the archival stream 62 is being streamed to the archival repository 40, the archival streaming agent 36 measures changes in performance characteristics of the real-time interactive flow 38. As non-limiting examples, the archival streaming agent 36 may measure performance characteristics such as available network bandwidth, data throughput, latency, jitter, and/or error rates of the real-time interactive flow 38. If a change in a performance characteristic of the real-time interactive flow 38 is detected, the archival streaming agent 36 may modify the adjustable streaming rate at which the archival stream 62 is being streamed to the archival repository 40 based on the change. The archival streaming agent 36 may also measure changes in network utilization by the computing device 42, and modify the adjustable streaming rate accordingly based on any such changes.
Some embodiments may provide that an archival streaming agent is integrated into a network media server to which two or more endpoints connect to participate in a real-time interactive flow. In this regard,
In this example, each of the computing devices 74(1)-74(N) connects to the media server 70 of the computing device 68. The computing devices 68 and 74 may communicate via a public network, such as the Internet, and/or via one or more private networks. The computing devices 68 and 74 of
The interactive flow functionality provider 80 receives the real-time interactive flows 72, and forks the contents or a mix of the contents of the real-time interactive flows 72 to the archival streaming agent 76 as an archival stream 88. The archival stream 88, which is a duplicate of the contents or the mix of contents of the real-time interactive flows 72, is then streamed by the archival streaming agent 76 to the archival repository 78 at an adjustable streaming rate. As discussed above with respect to
As the archival stream 88 is being streamed to the archival repository 78, the archival streaming agent 76 measures changes in performance characteristics of the real-time interactive flows 72. As non-limiting examples, the archival streaming agent 76 may measure performance characteristics such as available network bandwidth, data throughput, latency, jitter, and/or error rates of the real-time interactive flows 72. If a change in a performance characteristic of the real-time interactive flows 72 is detected, the archival streaming agent 76 may modify the adjustable streaming rate at which the archival stream 88 is being streamed to the archival repository 78 based on the change. The archival streaming agent 76 may also measure changes in network utilization by the computing device 68, and modify the adjustable streaming rate accordingly based on any such changes.
To generally describe exemplary operations of the archival streaming agent 12 of
With continuing reference to
The archival streaming agent 12 next measures a change in a performance characteristic of the real-time interactive flow 14 (block 98). The performance characteristic of the real-time interactive flow 14 may include a network bandwidth, a data throughput, a latency, a jitter level, and/or an error rate of the real-time interactive flow 14. Based on the change in the performance characteristic of the real-time interactive flow 14, the archival streaming agent 12 modifies the adjustable streaming rate of the archival stream 30 (block 100). By modifying the adjustable streaming rate of the archival stream 30 based on the change in the performance characteristic, the archival streaming agent 12 minimizes any impact on the real-time interactive flow 14 while still providing a complete archive of the real-time interactive flow 14.
The archival streaming agent 12 then determines whether the real-time interactive flow 14 has terminated (block 102). If not, processing returns to block 98 of
Referring now to
In some embodiments, the archival streaming agent 12 optionally may buffer the archival stream 30 before or concurrently with beginning to stream the archival stream 30 (block 110). By buffering the archival stream 30, the archival streaming agent 12 may ensure that a complete copy of the real-time interactive flow 14 can be made even if network conditions require the archival stream 30 to be streamed at a rate less than real-time. The archival streaming agent 12 may also optionally mark network packets constituting the archival stream 30 as having a low priority (block 112). In some embodiments, this minimizes any impact of the archival stream 30 on other, higher priority network traffic.
The archival streaming agent 12 then streams the archival stream 30 to an archival repository 16 at an adjustable streaming rate (block 114). The archival repository 16 may be one or more computing devices that is accessible via a public or private network, and that is configured to provide persistent storage of data received as part of the archival stream 30. As discussed in greater detail below, streaming the archival stream 30 at an adjustable streaming rate permits the archival streaming agent 12 to modify the streaming rate in response to changes in performance characteristics of the real-time interactive flow 14 and/or changes in network utilization by a computing device.
In some embodiments, users may share other types of data (e.g., documents, emails, and/or images) outside the real-time interactive flow 14 while exchanging video, audio, and/or data of the real-time interactive flow 14. Because streaming of the archival stream 30 may not occur in real-time, it may be desirable in such embodiments to associate the data shared during the real-time interactive flow 14 with specific points in time in the archival stream 30. Accordingly, the archival streaming agent 12 may optionally stream an archival timeline stream 32 to the archival repository 16 concurrently with the archival stream 30 (block 116). Processing then continues at block 118 of
Referring now to
The archival streaming agent 12 next determines a network utilization by the computing device 18 (block 124). Some embodiments may provide that the archival streaming agent 12 may determine network utilization based on network utilization data provided by the computing device 18. The archival streaming agent 12 then determines whether there has been a change in the network utilization since a last determination of the network utilization (block 126). If a change in the network utilization by the computing device 18 is detected at decision block 126, the archival streaming agent 12 modifies the adjustable streaming rate of the archival stream 30 based on the change in the network utilization (block 128). As a non-limiting example, if the archival streaming agent 12 detects an increase in network utilization by the computing device 18, the archival streaming agent 12 may decrease the adjustable streaming rate of the archival stream 30 to minimize network burden. Processing then resumes at block 130. If no change in the measurement of the network utilization is detected at decision block 126, processing continues to block 130 of
The archival streaming agent 12 next determines whether the real-time interactive flow 14 has terminated (block 130). If not, processing resumes at block 118 of
The exemplary computing device 136 includes a processing device or processor 138, a main memory 140 (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 142 (as non-limiting examples, flash memory, static random access memory (SRAM), etc.), which may communicate with each other via a bus 144. Alternatively, the processing device 138 may be connected to the main memory 140 and/or the static memory 142 directly or via some other connectivity means.
The processing device 138 represents one or more processing devices, such as a microprocessor, central processing unit (CPU), or the like. More particularly, the processing device 138 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 a processor implementing a combination of instruction sets. The processing device 138 is configured to execute processing logic in instructions 146 and/or cached instructions 148 for performing the operations and steps discussed herein.
The computing device 136 may further include a communications interface in the form of a network interface device 150. It also may or may not include an input 152 to receive input and selections to be communicated to the computing device 136 when executing the instructions 146, 148. It also may or may not include an output 154, including but not limited to display(s) 156. The display(s) 156 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 computing device 136 may or may not include a data storage device 158 that includes using drive(s) 160 to store the functions described herein in a computer-readable medium 162, on which is stored one or more sets of instructions 164 (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 134, a participant user device, and/or a licensing server, as non-limiting examples. The one or more sets of instructions 164 may also reside, completely or at least partially, within the main memory 140 and/or within the processing device 138 during execution thereof by the computing device 136. The main memory 140 and the processing device 138 also constitute machine-accessible storage media. The instructions 146, 148, and/or 164 may further be transmitted or received over a network 166 via the network interface device 150. The network 166 may be an intra-network or an inter-network.
While the computer-readable medium 162 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 164. 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 146, 148, and/or 164 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, optical and magnetic media, and carrier wave signals.
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 et al. | 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 et al. | Oct 2014 | B1 |
8867731 | Lum et al. | Oct 2014 | B2 |
20020159464 | Lewis | Oct 2002 | A1 |
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 | Oct 2004 | A1 |
20050084082 | Horvitz et al. | Apr 2005 | A1 |
20050177380 | Pritchard et al. | Aug 2005 | A1 |
20060104526 | Gringeler | 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 |
20070078768 | Dawson | Apr 2007 | 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 |
20080133767 | Birrer | Jun 2008 | A1 |
20080162642 | Bachiri et al. | Jul 2008 | A1 |
20080192646 | Song et al. | Aug 2008 | A1 |
20080270541 | Keener | 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 | 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 |
20110246922 | Koenig | Oct 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 |
20120268553 | Talukder | Oct 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 | 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 | 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 et al. | Aug 2014 | A1 |
20140222930 | Gangadharan et al. | Aug 2014 | A1 |
20140223452 | Santhanam et al. | Aug 2014 | A1 |
20140237057 | Khodorenko | Aug 2014 | A1 |
20140241215 | Massover et al. | Aug 2014 | A1 |
20140245143 | Saint-Marc | Aug 2014 | A1 |
20140258822 | Li et al. | Sep 2014 | A1 |
20140269326 | Westin | 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 | Sep 2014 | A1 |
20140282903 | Singh et al. | Sep 2014 | A1 |
20140289420 | Tarricone | Sep 2014 | A1 |
20140324979 | Gao et al. | Oct 2014 | A1 |
20140325078 | Shan et al. | Oct 2014 | A1 |
20140344169 | Phelps et al. | Nov 2014 | A1 |
20140348044 | Narayanan et al. | Nov 2014 | A1 |
20140365676 | Yoakum | Dec 2014 | A1 |
20140379931 | Gaviria | Dec 2014 | A1 |
20150002614 | Zino et al. | 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 et al. | 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 |
---|
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. |
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, dated Sep. 12, 2014, 15 pages. |
Notice of Allowance for U.S. Appl. No. 13/931,968, dated Mar. 23, 2015, 7 pages. |
Final Office Action for U.S. Appl. No. 13/835,913, dated Mar. 26, 2015, 17 pages. |
Final Office Action for U.S. Appl. No. 14/037,440, dated Feb. 11, 2015, 19 pages. |
Non-Final Office Action for U.S. Appl. No. 14/068,839, dated Feb. 20, 2015, 15 pages. |
Johnston, Alan et al., “Taking on WebRTC in an Enterprise,” IEEE Communications Magazine, Apr. 2013, pp. 48-54, vol. 51, Issue 4. |
Search Report for British patent application GB1317121.0 dated Mar. 14, 2014, 3 pages. |
Search Report for British patent application GB1317122.8 dated Mar. 11, 2014, 3 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, dated Apr. 24, 2015, 4 pages. |
Advisory Action for U.S. Appl. No. 14/037,440, dated May 20, 2015, 3 pages. |
Search Report for British Patent Application GB1419338.7, dated Apr. 27, 2015, 4 pages. |
Search Report for British Patent Application GB1419334.6, dated Apr. 28, 2015, 6 pages. |
Notice of Allowance for U.S. Appl. No. 13/944,368, dated Apr. 1, 2015, 8 pages. |
Non-Final Office Action for U.S. Appl. 13/931,967, dated May 5, 2015, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 13/931,970, dated May 7, 2015, 9 pages. |
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 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. |
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. |
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 dated Dec. 30, 2014, 4 pages. |
Search Report for British patent application GB1411580.2 dated Dec. 30, 2014, 4 pages. |
Non-Final Office Action for U.S. Appl. No. 13/931,968, dated Dec. 8, 2014, 6 pages. |
Non-Final Office Action for U.S. Appl. No. 13/835,913, dated Nov. 20, 2014, 15 pages. |
Non-Final Office Action for U.S. Appl. No. 13/803,292, dated Jan. 27, 2015, 13 pages. |
Non-Final Office Action for U.S. Appl. No. 14/050,891, dated Jan. 29, 2015, 9 pages. |
Non-Final Office Action for U.S. Appl. No. 13/955,023, dated Feb. 2, 2015, 12 pages. |
Examination Report for British Patent Application GB1411584.4, dated Aug. 21, 2015, 1 page. |
Examination Report for British Patent Application GB1411580.2, dated Aug. 21, 2015, 1 page. |
Notification of Reasons for Refusal for Japanese Patent Application 2013-201221, dated Aug. 25, 2015, 8 pages. |
Advisory Action for U.S. Appl. No. 13/835,913, dated Jun. 10, 2015, 3 pages. |
Final Office Action for U.S. Appl. No. 13/803,292, dated Jun. 12, 2015, 17 pages. |
Final Office Action and Examiner Initiated Interview Summary for U.S. Appl. No. 14/050,891, dated Jun. 29, 2015, 11 pages. |
Final Office Action for U.S. Appl. No. 13/955,023, dated Jul. 20, 2015, 17 pages. |
Corrected Notice of Allowability for U.S. Appl. No. 13/944,368, dated Jul. 23, 2015, 4 pages. |
Non-Final Office Action for U.S. Appl. No. 14/141,798, dated Jul. 17, 2015, 13 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. |
Extended European Search Report for European Patent Application 15161452.6, dated Jun. 23, 2015, 5 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. |
Non-Final Office Action for U.S. Appl. No. 13/835,913, dated Sep. 3, 2015, 19 pages. |
Non-Final Office Action for U.S. Appl. No. 13/863,662, dated Sep. 25, 2015, 23 pages. |
Advisory Action for U.S. Appl. No. 13/803,292, dated Aug. 21, 2015, 3 pages. |
Non-Final Office Action for U.S. Appl. No. 13/803,292, dated Oct. 9, 2015, 13 pages. |
Advisory Action and Examiner-Initiated Interview Summary for U.S. Appl. No. 14/050,891, dated Sep. 29, 2015, 4 pages. |
Final Office Action for U.S. Appl. No. 14/068,839, dated Sep. 9, 2015, 17 pages. |
Final Office Action for U.S. Appl. No. 13/931,967, dated Aug. 20, 2015, 12 pages. |
Final Office Action for U.S. Appl. No. 13/931,970, dated Aug. 27, 2015, 10 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, dated Feb. 1, 2016, 17 pages. |
Advisory Action and Examiner-Initiated Interview Summary for U.S. Appl. No. 14/068,839, dated Feb. 12, 2016, 4 pages. |
Final Office Action for U.S. Appl. No. 14/141,798, dated Dec. 24, 2015, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 14/174,371, dated Feb. 18, 2016, 18 pages. |
Non-Final Office Action for U.S. Appl. No. 13/931,970, dated Feb. 23, 2016, 11 pages. |
Non-Final Office Action for U.S. Appl. No. 13/955,711, dated Nov. 9, 2015, 10 pages. |
Notice of Allowance for U.S. Appl. No. 14/050,891, dated Nov. 10, 2015, 10 pages. |
Non-Final Office Action for U.S. Appl. No. 13/955,023, dated Dec. 9, 2015, 13 pages. |
Non-Final Office Action for U.S. Appl. No. 14/037,440, dated Oct. 22, 2015, 15 pages. |
Advisory Action for U.S. Appl. No. 13/931,967, dated Nov. 3, 2015, 3 pages. |
Advisory Action for U.S. Appl. No. 13/931,970, dated Nov. 5, 2015, 3 pages. |
Non-Final Office Action for U.S. Appl. No. 14/068,943, dated Dec. 2, 2015, 16 pages. |
Non-Final Office Action for U.S. Appl. No. 14/255,429, dated Nov. 9, 2015, 26 pages. |
Search Report for British Patent Application No. GB1423089.0, dated Jul. 6, 2015, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20140365676 A1 | Dec 2014 | US |