Scalable real-time videoconferencing over WebRTC

• US 20170359187A1
• Filed: 06/13/2017
• Published: 12/14/2017
• Est. Priority Date: 06/13/2016
• Status: Abandoned Application

• Current Assignee: LogMeIn, Inc.
• Original Assignee: LogMeIn, Inc.
• Inventors: Bettenbuk, Zolten, Luczo, Laszlo
• Application Number:
  US15/620,910
• Publication Number:
  US 20170359187A1
• Time in Patent Office: Days
• CPC Class Codes: H04L 12/1827 Network arrangements for conference optimisation or adaptation
• CPC Class Codes: H04L 65/1108 Web based protocols, e.g. webRTC
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04N 7/147 Communication arrangements, e.g. identifying the communication as a video-communication, intermediate storage of the signals selecting H04Q
• CPC Class Codes: H04N 7/15 Conference systems

Abstract

A WebRTC-compliant media server avoids sharing the SSRCs of passive participants (namely, the video viewers who do not send video) by intercepting feedback packets (issued from the viewers) on the server side, modifying those packets, and then transmitting the modified packets back to the sender such that, when the sender receives these feedback packets, the sender treats the packets as if they were sent by a known SSRC. Preferably, the known SSRC is one that is associated with a single SSRC (e.g., a dummy or surrogate SSRC, or a technical SSRC, in either event that was previously shared with the video sender). The sender knows how to handle these packets and can then send the desired answer to the viewer(s) to maintain the conference stable and operational even as the number of participants grows and exceeds the SSRC peer limitations.

Claims

1. Apparatus, comprising:

a processor;

computer memory holding computer program instructions executed by the processor during a videoconference established among a peer sender, and a plurality of peer viewers that are not senders, the computer program instructions operative to;

intercept WebRTC source identifier feedback packets issued from the plurality of peer viewers; and

in lieu of forwarding the intercepted WebRTC source identifier feedback packets to the peer sender, sending the peer sender feedback packets that appear to originate from a peer already known to the peer sender.

2. The apparatus as described in claim 1 wherein the WebRTC source identifier is a Real-time Transport Protocol (RTP) synchronization source identifier (SSRC).

3. The apparatus as described in claim 1 wherein the plurality of peer viewers exceeds twenty (20) peer viewers.

4. The apparatus as described in claim 1 wherein the plurality of peer viewers exceeds hundreds of peer viewers.

5. The apparatus as described in claim 1 wherein the peer already known to the peer sender has associated therewith a single WebRTC source identifier.

6. A method of videoconferencing among a peer sender, and a plurality of peer viewers that are not senders, comprising:

as a videoconference initiated by the peer sender is on-going, intercepting WebRTC source identifier feedback packets issued from the plurality of peer viewers; and

in lieu of forwarding the intercepted WebRTC source identifier feedback packets to the peer sender, sending the peer sender feedback packets that appear to originate from a surrogate peer already known to the peer sender.

7. The method as described in claim 6 wherein the WebRTC source identifier is a Real-time Transport Protocol (RTP) synchronization source identifier (SSRC).

8. The method as described in claim 6 wherein the plurality of peer viewers exceeds twenty (20) peer viewers.

9. The method as described in claim 6 wherein the plurality of peer viewers exceeds hundreds of peer viewers.

10. The method as described in claim 6 wherein the surrogate peer already known to the peer sender has associated therewith a single WebRTC source identifier.

11. The method as described in claim 6 further including providing the peer sender information identifying the surrogate peer in advance of the videoconference initiation.