220-250.

Real-time media servers 212 provide multiplexed multimedia streams to meeting participants, such as client devices 220-250. While video and audio streams typically originate at the respective client devices, they are transmitted from the client devices 220-250 to the video conference provider 210 via one or more networks where they are received by the real-time media servers 212. The real-time media servers 212 determine which protocol is optimal based on, for example, proxy settings and the presence of firewalls, etc. For example, the client device might select among UDP, TCP, TLS, or HTTPS for audio and video and UDP for content screen sharing.

The real-time media servers 212 then multiplex the various video and audio streams based on the target client device and communicate multiplexed streams to each client device. For example, the real-time media servers 212 receive audio and video streams from client devices 220-240 and only an audio stream from client device 250. The real-time media servers 212 then multiplex the streams received from devices 230-250 and provide the multiplexed stream to client device 220. The real-time media servers 212 are adaptive, for example, reacting to real-time network and client changes, in how they provide these streams. For example, the real-time media servers 212 may monitor parameters such as a client's bandwidth CPU usage, memory and network I/O as well as network parameters such as packet loss, latency and jitter to determine how to modify the way in which streams are provided.

The client device 220 receives the stream, performs any decryption, decoding, and demultiplexing on the received streams, and then outputs the audio and video using the client device's video and audio devices. In this example, the real-time media servers do not multiplex the video from client device 220 and audio feeds when transmitting streams to client device 220. Instead each client device 220-250 only receives multimedia streams from other client devices 220-250. For telephony devices that lack video capabilities, e.g., client device 250, the real-time media servers 212 only deliver multiplex audio streams. The client device 220 may receive multiple streams for a particular communication, allowing the client device 220 to switch between streams to provide a higher quality of service.

In addition to multiplexing multimedia streams, the real-time media servers 212 may also decrypt incoming multimedia stream in some examples. As discussed above, multimedia streams may be encrypted between the client devices 220-250 and the video conference provider 210. In some such examples, the real-time media servers 212 may decrypt incoming multimedia streams, multiplex the multimedia streams appropriately for the various clients, and encrypt the multiplexed streams for transmission.

As mentioned above with respect to FIG. 1, the video conference provider 210 may provide certain functionality with respect to unencrypted multimedia streams at a user's request. For example, the meeting host may be able to request that the meeting be recorded or that a transcript of the audio streams be prepared, which may then be performed by the real-time media servers 212 using the decrypted multimedia streams, or the recording or transcription functionality may be off-loaded to a dedicated server (or servers), e.g., cloud recording servers, for recording the audio and video streams. In some examples, the video conference provider 210 may allow a meeting participant to notify it of inappropriate behavior or content in a meeting. Such a notification may trigger the real-time media servers to 212 record a portion of the meeting for review by the video conference provider 210. Still other functionality may be implemented to take actions based on the decrypted multimedia streams at the video conference provider, such as monitoring video or audio quality, adjusting or changing media encoding mechanisms, etc.

It should be appreciated that multiple real-time media servers 212 may be involved in communicating data for a single meeting and multimedia streams may be routed through multiple different real-time media servers 212. In addition, the various real-time media servers 212 may not be co-located, but instead may be located at multiple different geographic locations, which may enable high-quality communications between clients that are dispersed over wide geographic areas, such as being located in different countries or on different continents. Further, in some examples, one or more of these servers may be co-located on a client's premises, e.g., at a business or other organization. For example, different geographic regions may each have one or more real-time media servers 212 to enable client devices in the same geographic region to have a high-quality connection into the video conference provider 210 via real-time media servers 212 to send and receive multimedia streams, rather than connecting to a real-time media server located in a different country or on a different continent. The local real-time media servers 212 may then communicate with physically distant servers using high-speed network infrastructure, e.g., internet backbone network(s), that otherwise might not be directly available to client devices 220-250 themselves. Thus, routing multimedia streams may be distributed throughout the video conference provider 210 and across many different real-time media servers 212.

Network services servers 214 provide administrative functionality to enable client devices to create or participate in meetings, send meeting invitations, create or manage user accounts or subscriptions, and other related functionality. Further, these servers may be configured to perform different functionalities or to operate at different levels of a hierarchy, e.g., for specific regions or localities, to manage portions of the video conference provider under a supervisory set of servers. When a client device 220-250 accesses the video conference provider 210, it will typically communicate with one or more network services servers 214 to access their account or to participate in a meeting.

When a client device 220-250 first contacts the video conference provider 210 in this example, it is routed to a network services server 214. The client device may then provide access credentials for a user, e.g., a username and password or single sign-on credentials, to gain authenticated access to the video conference provider 210. This process may involve the network services servers 214 contacting a user identity provider 215 to verify the provided credentials. Once the user's credentials have been accepted, the network services servers 214 may perform administrative functionality, like updating user account information, if the user has an identity with the video conference provider 210, or scheduling a new meeting, by interacting with the network services servers 214.

In some examples, users may access the video conference provider 210 anonymously. When communicating anonymously, a client device 220-250 may communicate with one or more network services servers 214 but only provide information to create or join a meeting, depending on what features the video conference provider allows for anonymous users. For example, an anonymous user may access the video conference provider using client device 220 and provide a meeting ID and passcode. The network services server 214 may use the meeting ID to identify an upcoming or on-going meeting and verify the passcode is correct for the meeting ID. After doing so, the network services servers 214 may then communicate information to the client device 220 to enable the client device 220 to join the meeting and communicate with appropriate real-time media servers 212.

In cases where a user wishes to schedule a meeting, the user (anonymous or authenticated) may select an option to schedule a new meeting and may then select various meeting options, such as the date and time for the meeting, the duration for the meeting, a type of encryption to be used, one or more users to invite, privacy controls (e.g., not allowing anonymous users, preventing screen sharing, manually authorize admission to the meeting, etc.), meeting recording options, etc. The network services servers 214 may then create and store a meeting record for the scheduled meeting. When the scheduled meeting time arrives (or within a threshold period of time in advance), the network services servers 214 may accept requests to join the meeting from various users.

To handle requests to join a meeting, the network services servers 214 may receive meeting information, such as a meeting ID and passcode, from one or more client devices 220-250. The network services servers 214 locate a meeting record corresponding to the provided meeting ID and then confirm whether the scheduled start time for the meeting has arrived, whether the meeting host has started the meeting, and whether the passcode matches the passcode in the meeting record. If the request is made by the host, the network services servers 214 activates the meeting and connects the host to a real-time media server 212 to enable the host to begin sending and receiving multimedia streams.

Once the host has started the meeting, subsequent users requesting access will be admitted to the meeting if the meeting record is located and the passcode matches the passcode supplied by the requesting client device 220-250. In some examples additional access controls may be used as well. But if the network services servers 214 determines to admit the requesting client device 220-250 to the meeting, the network services server 214 identifies a real-time media server 212 to handle multimedia streams to and from the requesting client device 220-250 and provides information to the client device 220-250 to connect to the identified real-time media server 212. Additional client devices 220-250 may be added to the meeting as they request access through the network services servers 214.

After joining a meeting, client devices will send and receive multimedia streams via the real-time media servers 212, but they may also communicate with the network services servers 214 as needed during meetings. For example, if the meeting host leaves the meeting, the network services servers 214 may appoint another user as the new meeting host and assign host administrative privileges to that user. Hosts may have administrative privileges to allow them to manage their meetings, such as by enabling or disabling screen sharing, muting or removing users from the meeting, assigning or moving users to the mainstage or a breakout room if present, recording meetings, etc. Such functionality may be managed by the network services servers 214.

For example, if a host wishes to remove a user from a meeting, they may identify the user and issue a command through a user interface on their client device. The command may be sent to a network services server 214, which may then disconnect the identified user from the corresponding real-time media server 212.

In addition to creating and administering on-going meetings, the network services servers 214 may also be responsible for closing and tearing-down meetings once they have completed. For example, the meeting host may issue a command to end an on-going meeting, which is sent to a network services server 214. The network services server 214 may then remove any remaining participants from the meeting, communicate with one or more real time media servers 212 to stop streaming audio and video for the meeting, and deactivate, e.g., by deleting a corresponding passcode for the meeting from the meeting record, or delete the meeting record(s) corresponding to the meeting. Thus, if a user later attempts to access the meeting, the network services servers 214 may deny the request.

Depending on the functionality provided by the video conference provider, the network services servers 214 may provide additional functionality, such as by providing private meeting capabilities for organizations, special types of meetings (e.g., webinars), etc. Such functionality may be provided according to various examples of video conferencing providers according to this description.

Referring now to the video room gateway servers 216, these video room gateway servers 216 provide an interface between dedicated video conferencing hardware, such as may be used in dedicated video conferencing rooms. Such video conferencing hardware may include one or more cameras and microphones and a computing device designed to receive video and audio streams from each of the cameras and microphones and connect with the video conference provider 210. For example, the video conferencing hardware may be provided by the video conference provider to one or more of its subscribers, which may provide access credentials to the video conferencing hardware to use to connect to the video conference provider 210.

The video room gateway servers 216 provide specialized authentication and communication with the dedicated video conferencing hardware that may not be available to other client devices 220-230, 250. For example, the video conferencing hardware may register with the video conference provider when it is first installed and the video room gateway may authenticate the video conferencing hardware using such registration as well as information provided to the video room gateway servers 216 when dedicated video conferencing hardware connects to it, such as device ID information, subscriber information, hardware capabilities, hardware version information etc. Upon receiving such information and authenticating the dedicated video conferencing hardware, the video room gateway servers 216 may interact with the network services servers 214 and real-time media servers 212 to allow the video conferencing hardware to create or join meetings hosted by the video conference provider 210.

The telephony gateway servers 218 enable and facilitate telephony devices' participation in meetings hosed by the video conference provider 210. Because telephony devices communicate using the PSTN and not using computer networking protocols, such as TCP/IP, the telephony gateway servers 218 act as an interface that converts between the PSTN and the networking system used by the video conference provider 210.

For example, if a user uses a telephony device to connect to a meeting, they may dial a phone number corresponding to one of the video conference provider's telephony gateway servers 218. The telephony gateway server 218 will answer the call and generate audio messages requesting information from the user, such as a meeting ID and passcode. The user may enter such information using buttons on the telephony device, e.g., by sending dual-tone multi-frequency (“DTMF”) audio signals to the telephony gateway server 218. The telephony gateway server 218 determines the numbers or letters entered by the user and provides the meeting ID and passcode information to the network services servers 214, along with a request to join or start the meeting, generally as described above. Once the telephony client device 250 has been accepted into a meeting, the telephony gateway server 218 is instead joined to the meeting on the telephony device's behalf.

After joining the meeting, the telephony gateway server 218 receives an audio stream from the telephony device and provides it to the corresponding real-time media server 212, and receives audio streams from the real-time media server 212, decodes them, and provides the decoded audio to the telephony device. Thus, the telephony gateway servers 218 operate essentially as client devices, while the telephony device operates largely as an input/output device, e.g., a microphone and speaker, for the corresponding telephony gateway server 218, thereby enabling the user of the telephony device to participate in the meeting despite not using a computing device or video.

It should be appreciated that the components of the video conference provider 210 discussed above are merely examples of such devices and an example architecture. Some video conference providers may provide more or less functionality than described above and may not separate functionality into different types of servers as discussed above. Instead, any suitable servers and network architectures may be used according to different examples.

FIG. 3 depicts an example system 300 for providing instant replay in video conferences. The system 300 shown in FIG. 3 includes a video conference provider 310 and multiple client devices 330 and 340A-N that are connected to the video conference provider 310 via network 320. In this example, the network 320 is the internet; however, any communications network or combination of communications networks may be employed. While system 300 is depicted as including multiple client device 330, 340A-N, it should be appreciated that some systems may not include any client devices at any particular time, and that the number of client devices can change.

To start a video conference, client device 330, a host, connects to the video conference provider 310 and begins a main meeting (“meeting”) at the video conference provider 310, such as by beginning a scheduled meeting, generally as described above with respect to FIGS. 1 and 2. The video conference provider 310 may create and manage the meeting as discussed above with respect to FIGS. 1-2. Any of client devices 330 or 340A-N may start or join additional meetings.

Video conference provider 310 and/or one or more client devices 330 and 340A-N can facilitate instant replay functionality. Instant replay functionality includes obtaining consent from participants in the meeting regarding whether they wish to opt-in to the replay functionality. For any participants who opt-in to the replay functionality, their client devices privately store a limited buffer of recent audio or video data, such as is captured by their camera and microphone. Such an approach maintains the participants' privacy by storing replay data in local buffers on individual client devices. Then, when a replay is requested, the buffer data is accessed and consent obtained, if not already obtained, for example at the start of the meeting. These buffers are not available for other to access, except if a request for replay is sent. To further enhance privacy, the replay buffer may be stored in volatile memory such that if the client device loses power, the replay buffer is deleted.

When requested, replay data can be obtained from the buffers on client devices whose users have opted-in to the replay functionality. In some cases, the video conference provider 310 does not know which devices consented for instant replay and if so, whether a buffer has been enabled on the respective client device. As such, in some cases, the video conference provider 310 obtains this information after a request for an instant replay has been made.

The replay data can be combined into a single replay segment in some cases, such as by resizing and merging video feeds into a single video stream. Though in some cases, replay from each participant can be separately provided to the requesting participant or others within the meeting. In this example, the replay buffers are circular buffers, but any suitable data structure can be used. For instance, a buffer can represent the last minute of conference data and be constantly refreshed as the conference progresses. Examples of replay data include, but are not limited to, video, audio, screensharing, chat messages between participants, diagnostic data (e.g., network info), and/or data representing anything that is shared in the conference.

Various durations and starting points of replay segments are possible. For instance, a segment could be 30 seconds long and include conference data from 30 seconds prior to the point in the conference at which the replay was requested. A segment could be 45 seconds long and start two minutes prior to the point at which replay was requested. Accordingly in some cases, a request for an instant replay can include a duration of the instant replay (e.g., 30 seconds) and/or a starting point (e.g., 1 minute prior or 5 minutes prior).

In a simplified example, client devices 340A-C join a conference hosted by video conference provider 310. At the outset of the conference, each client device 340A-C consents to recording their respective data streams for the instant replay functionality. The client devices 340A-C maintain respective buffers that store conference data corresponding to the respective client device, e.g., shared by or generated by the participant using the respective client device.

Continuing the example, at some point during the conference, client device 340B requests an instant replay by sending the request to the video conference provider 310. In turn, video conference provider 310 transmits individual requests for replay data to each of the client devices that opted-in to the replay functionality, which in this case includes client devices 340A-C. Each client device 340A-C then provides respective replay data, which can include audio, video, or any other conference data, back to the video conference provider 310. In turn, the video conference provider 310 combines the replay data into a combined replay segment that reflects the replay data from all the client devices 340A-C. Then, the instant replay segment can be replayed on one or more of the devices, or within the conference, for all client devices to view. The instant replay segment can also be downloaded (e.g., by a user) or stored for later use or otherwise made available during or after a meeting (e.g., by the conference provider). And while this example involves combining the replay data received from the various client devices 340A-C, in some examples, the video conference provider provides the replay data from the various clients to the requesting client without combining them.

As discussed, client devices that have consented can provide replay data for the instant replay. For instance, if client devices 340A-B join a conference via video conference provider 310, but only client device 340A opts into the instant replay feature, then instant replay of conference data generated by both client devices 340A-B is not possible, because in this case, only client device 340A has opted-in and therefore, only client device 340A maintains a replay buffer for conference data. However, during the conference, the user of client device 340B can request an instant replay. Client device 340B sends a request to the conference provider, which relays the request to the client device 340A. Client device 340A transmits a replay segment back to the video conference provider 310, which in turn, provides the replay segment data to the client device 340B. The user of client device 340B can then play back the segment as desired. But in this example, a user of client device 340A cannot obtain replay data from client device 340B, as client device 340B did not consent and therefore did not maintain a replay buffer.

Other use cases and configurations are possible. In some cases, video conference provider 310 need not be involved in the instant replay. Rather, requests for a replay and segment data can be passed directly from client device to client device.

In some cases, more complex privacy policies can be used such as a global opt-in or opt-out to instant replay for a given device. For example, corporate policies may require the use of replay functionality or may prohibit the use of replay functionality. More fine-grained control may be employed in some examples as well. For example, a corporate replay policy may allow replay of audio or video streams, but not streams of shared content such as presentations or documents. Some examples may prohibit certain persons from enabling replay functionality on their client device, such as executive-level employees, human resources employees, or employees in financial teams. Still other policies may be implemented according to different examples.

Different buffer storage configurations and the storage of local privacy settings are possible, as explained further with respect to FIG. 4. Operations performed by a conference provider are explained further with respect to FIG. 5. Operations performed by a client device are explained further with respect to FIG. 6. Examples of signal flows between devices are explained further with respect to FIG. 7. An example user interface for requesting instant replay is explained further with respect to FIG. 8.

FIG. 4 depicts an example system 400 for providing instant replay in video conferences. System 400 depicts client devices 440A-N having various buffers and privacy settings. FIG. 4 illustrates examples of buffers that can be present on a client device, e.g., client devices 340A-N, and privacy settings that can be present on a client device and maintained differently relative to other client devices. The buffers are used to store applicable conference data generated by the respective client device. The privacy settings are used to determine whether a device has opted-in or opted-out of instant replay, and/or whether any global privacy policies are in place.

As can be seen, client devices 440A-N can include buffers with different contents and/or privacy settings. The buffers can store replay data such as audio, video, and so forth. Different length buffers are possible. In some cases, an entire conference can be buffered. Buffers can also be encrypted to provide further privacy protection. Buffers can be deleted after the conclusion of a video conference and/or when the video conferencing application is exited.

As depicted, client device 440A includes buffer 450A and privacy settings 480A. Buffer 450A includes audio 460A, video 462A, screen share data 464A, messages 466A, app data 468A, diagnostic data 470A, and other data 472A. But any data that represents a state of the conference during the relevant time period can be stored. Further, video and audio can be stored together, e.g., multiplexed, or stored separately. Screen share data 464A stores data that represents any screen sharing that took place during the time represented by the buffer. App data 468A can include data related to the applications in use during the time represented by the buffer. Diagnostic data 470A can include any kind of data used for diagnostics related to the conference, the instant replay feature, or the client devices. Other data 472A includes any other relevant data. Similarly, client device 340N includes buffer 450N and privacy settings 480N, and so forth.

In some cases, buffering can take place on video conference provider 310. In this case, the video conference provider 310 stores a buffer of conference data for each client device 340A-N that has consented to the replay functionality.

FIG. 5 depicts a flowchart of an example of a method for providing instant replay in video conferences. Method 500 can be implemented by one or more of video conference provider 310, client devices 340A-N, or any other suitable systems.

It should be appreciated that method 500 provides a particular method for instant replay in video conferences. Other sequences of operations may also be performed according to alternative examples. For example, alternative examples may perform the steps outlined above in a different order. Moreover, the individual operations illustrated by method 500 may include multiple sub-operations that may be performed in various sequences as appropriate to the individual operation. Furthermore, additional operations may be added or removed depending on the particular applications. Further, the operations described in method 500 may be performed by different devices.

For example purposes, FIG. 5 is discussed with respect to the devices of FIG. 3. In the example described below, two client devices, client devices 340A-B are present in a conference. In other examples, additional client devices can join the conference.

At block 502, method 500 involves establishing, via a virtual conference provider, a virtual meeting and joining a set of client devices to the virtual meeting, each client device associated with a corresponding participant. For example, referring back to FIG. 3, video conference provider 310 establishes a virtual meeting between client devices 340A-N. Each client device 340A-N is associated with a corresponding participant.

At block 504, method 500 involves receiving, from one or more of the client devices, replay opt-in information for participants in the meeting. At the outset of the meeting, client devices 340A-N can each transmit their respective instant replay opt-in or out-out preferences to video conference provider 310, which can maintain a record of these preferences.

Different methods of obtaining privacy consents are possible. For example, consent can be obtained from client devices prior to a conference commencing or during a conference when a replay is requested. In some cases, the video conference provider 310 and/or client devices 340A-N can determine which client devices were active during the requested replay segment. Then, obtaining consent can be limited to the devices that were active during the requested segment, which simplifies the user experience. Various techniques can be used to make this determination such as analyzing video for movement and/or detection of audio in the audio streams from conference devices.

Consent can be retrieved from a previously stored selection or privacy policy. For instance, a given client device can opt in or opt out of instant replay for all meetings. In some cases, a given device can opt in or opt out of certain meetings based on a type of meeting. For example, a device may have a predetermined opt-in for instant replay of work meetings but not for meetings designated as personal. Similar distinctions could be made for internal meetings versus external meetings. Further, globally applied policies can affect one or more client devices such as restricting recording, requiring recording, or requiring separate consent for each meetings. If consent is granted for recording of meetings, then consent can be automatically granted for instant replay.

At block 506, method 500 involves receiving, by the virtual conference provider from a first client device of the set of client devices, a request for a replay segment from a second client device of the set of client devices. Continuing the example, video conference provider 310 receives, from a first client device, client device 340A, a request for the replay segment from the second client device.

At block 508, method 500 involves determining, from the set of client devices, one or more client devices that have opted-in to the instant replay functionality. Continuing the example, client device 340B has opted into the instant replay functionality. Video conference provider 310 can determine that client device 340B has opted in by accessing the record of preferences, as discussed with respect to block 504.

As discussed further herein, consent to participate in the instant replay feature can be can be obtained at one or more points during or before the conference such as before the conference begins, when a party requests an instant replay, and globally, e.g., from a predefined consent previously obtained and stored on a client device or at the conference provider.

At block 510, method 500 involves transmitting, during the virtual meeting and to the one or more client devices that have opted into the replay functionality, the request for the replay segment. Continuing the example, video conference provider 310 transmits the request to a second client device, client device 340B.

If the client device that requested the replay, e.g., client device 340A in this example, is only be interested in a replay from specific devices, then the request for replay is provided only to those specified devices. Advantages to this approach include reducing latency in obtaining the replay.

At block 512, method 500 involves receiving, from the one or more client devices that have opted into the replay functionality, replay segment data from the respective client device, the replay segment data including data recorded by the respective client device during the virtual meeting. Continuing the example, client device 340B obtains the replay segment data from a buffer on client device 340B and transmits the replay segment data to video conference provider 310. Similarly, other client devices that have opted-in transmit replay segment data to the video conference provider 310.

At block 514, method 500 involves transmitting, to the first client device, the replay segment data. Continuing the example, video conference provider 310 transmits the replay segment data to client device 340A. If more client devices are providing segment data, then video conference provider 310 can combine the segment data into a combined segment. As discussed, in some cases, client device 340B could transmit the segment data to client device 340A directly.

FIG. 6 depicts a flowchart of an example of a method 600 for providing instant replay in video conferences. Method 600 can be implemented by client devices 340A-N or by any suitable client devices according to this disclosure.

It should be appreciated that method 600 provides a particular method for instant replay in video conferences. Other sequences of operations may also be performed according to alternative examples. For example, alternative examples may perform the steps outlined above in a different order. Moreover, the individual operations illustrated by method 600 may include multiple sub-operations that may be performed in various sequences as appropriate to the individual operation. Furthermore, additional operations may be added or removed depending on the particular applications. Further, the operations described in method 600 may be performed by different devices.

At block 602, method 600 involves joining, at a first client device and via a server device, a virtual meeting including a set of client devices, each client device associated with a corresponding participant. For example, referring back to FIG. 3, one or more client devices 340A-N join a virtual meeting via video conference provider 310. Consent from participating devices can be obtained prior to the start of the virtual meeting or prior to the respective client device joining the virtual meeting.

At block 604, method 600 involves transmitting, from the first client device and to the server device, a first stream including data captured at the client device. Continuing the example, client device 340A transmits, to the video conference provider 310, the first stream that includes conference data captured at client device 340A. Other client devices 340B-N, if present in the conference, can perform similar operations.

At block 606, method 600 involves transmitting, from the first client device and to the server device, an opt-in to instant replay. Continuing the example, client device 340B transmits, to the video conference provider 310, an opt-in to instant replay. Other client devices 340A and 340C-N can transmit an opt-in preference also, as appropriate. If opt-in is not granted, then method 600 ceases to execute on client device 340B. Execution can continue on other devices that have opted-in.

At block 608, method 600 involves maintaining, in a buffer on the first client device, the captured data. Client device 340A maintains a local buffer that stores conference data such as video and audio. Similarly, other client devices 340B-N, if present in the conference, can maintain buffers as well.

At block 610, method 600 involves receiving, from the server device, a request for a replay segment corresponding to the first stream. A request can include a duration and/or a and starting point of a replay segment. Examples include a segment duration of 1 minute, or a segment starting point of two minutes ago with a length of 30 seconds.

Continuing the example, client device 340A transmits a request for a replay segment to video conference provider 310. Client device 340B then receives the request from video conference provider 310.